[Nsi-wg] NSA functional components v2.3

[John Vollbrecht]

Hi Chin -- I think this is getting very good.  One comment is that  
just as you have a topology and path finding module, I think there  
should be something similar for the service plane - perhaps an NSA map  
- as well as a NSA Lookup.   The NSA map is essentially a service  
plane topology.

John


On Dec 2, 2009, at 11:53 AM, Chin Guok wrote:

> Hi Radek, Guy,
>
> I agree with all the comments you guys have brought up.  I'll make  
> another
> pass at the document to clarify the points that have been brought  
> up.  I'm
> going to be busy potentially for the rest of the week, so you may  
> not see
> it till early next week.
>
> - Chin
>
> --On December 2, 2009 4:35:56 PM +0000 Guy Roberts <Guy.Roberts at dante.net 
> >
> wrote:
>
>> Radek,
>>
>> Here is my interpretation - see comments in-line.
>>
>> Guy
>>
>> -----Original Message-----
>> From: Radek Krzywania [mailto:radek.krzywania at man.poznan.pl]
>> Sent: 02 December 2009 11:23
>> To: 'Chin Guok'; 'NSI WG'
>> Subject: Re: [Nsi-wg] NSA functional components v2.3
>>
>> Hi Chin, all,
>> I have a few comments to the document provided:
>>
>> -  Topology module - it's not clear for me if that's inter- or
>> intra-domain or both. IMHO we should care only for inter-domain  
>> here. As
>> NSI is dedicated to multidomain, let's leave single domain stuff to  
>> third
>> parties software (via Local Resouce Manager).
>> [GR] Agreed - inter-domain pathfinding is assumed - perhaps this  
>> needs to
>> be more clearly stated.
>>
>>
>> - NSA Lookup - I thought that NSA lookup will just gave the contact
>> information (e.g. service address) of particular NSAs. The  
>> description
>> makes me a little bit confused, as it claims to "determine the  
>> control
>> plane connectivity of NSAs". This is somehow pathfinder/topology
>> responsibility IMHO.
>> [GR] I think this should be as you say a service to find the URL of  
>> the
>> web service.
>>
>> - Path Finding - in AutoBAHN there are two levels of pathfinding -  
>> inter-
>> and intra-domain. I suppose this is inter-domain, but it's not  
>> explicitly
>> mentioned. The difference is not only the area of operations (intra/ 
>> inter)
>> but also the topology view (abstracted global vs. technology specific
>> local) [GR] yes, inter-domain.  Domain internal path finding is not
>> relevant here.
>>
>> - Local Resource Manager - I consider this only as an interface to  
>> third
>> party domain mangers. Is that correct?
>> [GR] right.
>>
>> - Notifications - is this kind of notification broker or just a  
>> module to
>> send/receive information?
>> [GR] I think notification broker - this is not well defined yet.
>>
>> Best regards
>> Radek
>>
>>
>>> -----Original Message-----
>>> From: nsi-wg-bounces at ogf.org [mailto:nsi-wg-bounces at ogf.org] On  
>>> Behalf
>>> Of Chin Guok
>>> Sent: Tuesday, December 01, 2009 1:00 AM
>>> To: NSI WG
>>> Subject: [Nsi-wg] NSA functional components v2.3
>>>
>>> Hi all,
>>>
>>> I've revised the document based on our last discussion.
>>>
>>> Please feel free to comment and make edits.  Please also keep in  
>>> mind
>>> that the contents of this document should only serve as supporting  
>>> text
>>> for the NSI architecture document and is not meant to detail the NSA
>>> architecture (which would be a separate document).
>>>
>>> Thanks.
>>>
>>> - Chin
>>
>> _______________________________________________
>> nsi-wg mailing list
>> nsi-wg at ogf.org
>> http://www.ogf.org/mailman/listinfo/nsi-wg
>
>
>
>
> _______________________________________________
> nsi-wg mailing list
> nsi-wg at ogf.org
> http://www.ogf.org/mailman/listinfo/nsi-wg