Re: Getting started on NSIS extensibilty draft

Hi all, 

I also read the document and it looks pretty good. Easy to read and
understand. 

Only a few minor comments: 

"
   The SID is not meaningful by itself, but is rather used together with
   the NSLP identifier (NSLPID) and the Message Routing Information
   (MRI).  This 3-tuple is used by GIST to index and manage the
   signaling flows.
"

In a previous paragraph you say that the SID is used for mobility because no
IP address is used. I believe this has to be clarified how this statement
and the other one from the previous paragraph fits together. 


"
   o  Path-coupled signaling only: GIST transports messages towards an
      identified unicast data flow destination based on the signaling
      application request, and does not directly support path-decoupled
      signaling, e.g., QoS signaling to a bandwidth broker.  The
      framework also supports a "Loose-End" message routing method used
      to discover GIST nodes with particular properties in the direction
      of a given address, for example the NAT/FW NSLP uses this method
      to discover a NAT along the upstream data path.
"


I would say "Current MRM focus on Path-coupled Signaling". 

"
No support for QoS architectures based on bandwidth
   brokers is currently included.
"

You might need a reference here. Not everyone might be aware of what a
bandwidth broker actually is. 


Section 8, extending the protocols. Section 8.1 is too generic and RFC 2119
language is not useful in this document. I would replace this section with
more details on how GIST, the NATFW NSLP and the QoS NSLP are extended.


Btw, this document cannot be completed before the normative references
become RFCs. 

Ciao
Hannes

>-----Original Message-----
>From: [email protected] [mailto:[email protected]] On 
>Behalf Of Georgios Karagiannis
>Sent: 23 February, 2009 14:06
>To: 'Jukka MJ Manner'; 'NSIS Working Group'
>Subject: Re: [NSIS] Getting started on NSIS extensibilty draft
>
>Hi Jukka
>
>I have read the  NSIS extensibilty draft and I think that it 
>is good enough to go through a WGLC.
>
>I will provide detailed comments during the WGLC!
>
>Best regards,
>Georgios
>
>
>> -----Original Message-----
>> From: [email protected] [mailto:[email protected]] On Behalf 
>> Of Jukka MJ Manner
>> Sent: vrijdag 20 februari 2009 13:02
>> To: NSIS Working Group
>> Subject: Re: [NSIS] Getting started on NSIS extensibilty draft
>> 
>> 
>> Dear all,
>> 
>> We would really need feedback to this draft to finalize it. I would 
>> like to issue a WGLC very soon, thus, one round of comments would be 
>> good to have before that.
>> 
>> Alternatively, we can also issue a WGLC now, and discuss the 
>comments 
>> in SF. Still, I'd rather see one round of comments before a WGLC.
>> 
>> Regards,
>> Jukka
>> 
>> On Wed, 4 Feb 2009, Elwyn Davies wrote:
>> 
>> > Hi, Magnus.
>> > 
>> > At the last IETF you offered to provide me some guidance 
>on the way 
>> > forward with this document.
>> > 
>> > Since as I understand it, the IESG wants to see this
>> document at the
>> > same time as GIST this is urgent.
>> > 
>> > The only suggestion I have stemming from comments at the
>> meeting is to
>> > 'separate the rules and guidelines.'
>> > 
>> > Any input gratefully received.
>> > In the meantime I will try to make a 'null' update just to
>> change the
>> > title.
>> > 
>> > Regards,
>> > Elwyn
>> > 
>> > Martin Stiemerling wrote:
>> > > The new file name should basically read this way
>> (copy'n'paste error):
>> > > draft-ietf-nsis-ext-00.txt.
>> > >
>> > > Thanks to Hannes for pointing this
>> > >
>> > >  Martin
>> > >
>> > > [email protected]
>> > >
>> > > NEC Laboratories Europe - Network Research Division NEC Europe 
>> > > Limited | Registered Office: NEC House, 1 Victoria Road,
>> London W3
>> > > 6BL | Registered in England 2832014
>> > >
>> > >   
>> > >> -----Original Message-----
>> > >> From: [email protected] [mailto:[email protected]] On 
>> > >> Behalf Of Martin Stiemerling
>> > >> Sent: Monday, January 26, 2009 3:05 PM
>> > >> To: [email protected]
>> > >> Subject: [NSIS] Getting started on NSIS extensibilty draft
>> > >>
>> > >> Dear all,
>> > >>
>> > >> We have a draft to be completed urgently :)
>> > >>
>> > >> Using and Extending the NSIS Protocol Family
>> draft-nsis-ext-02.txt
>> > >>
>> > >> http://tools.ietf.org/html/draft-nsis-ext-02
>> > >>
>> > >>
>> > >> First thing to do is changing the file name to
>> draft-ietf-nsis-ext-
>> > >> 02.txt.
>> > >>
>> > >> Please review it and send your comments.
>> > >>
>> > >>  Martin
>> > >>
>> > >>
>> > >> [email protected]
>> > >>
>> > >> NEC Laboratories Europe - Network Research Division NEC Europe 
>> > >> Limited | Registered Office: NEC House, 1 Victoria Road,
>> London W3
>> > >> 6BL | Registered in England 2832014
>> > >>
>> > >> _______________________________________________
>> > >> nsis mailing list
>> > >> [email protected]
>> > >> https://www.ietf.org/mailman/listinfo/nsis
>> > >>     
>> > > _______________________________________________
>> > > nsis mailing list
>> > > [email protected]
>> > > https://www.ietf.org/mailman/listinfo/nsis
>> > >
>> > >   
>> > _______________________________________________
>> > nsis mailing list
>> > [email protected]
>> > https://www.ietf.org/mailman/listinfo/nsis
>> > 
>> _______________________________________________
>> nsis mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/nsis
>> 
>
>
>_______________________________________________
>nsis mailing list
>[email protected]
>https://www.ietf.org/mailman/listinfo/nsis
>