Subject: [NSIS] qos-nslp-00

From: "Geib, Ruediger" <[email-masked]>
Date: Tue, 23 Sep 2003 15:08:55 +0200

Hi Sven,

Chapter 7 tells the reader that the draft-nsis-qos-nslp-00 is rather drafty yet. Some issues I've identified:

- The rather flexible NSLP defined by the document 
  more seems to be a generic NSLP than a QoS NSLP.
- Chapter 7.1 misses "security" as a refinement 
  required for this version. I doubt it's a good 
  idea to define a protocol and worry about 
  security afterwards.
- Retransmitted "Reservation Sequence Numbers" 
  serve as a Session ID. Why aren't 
  the tradeoffs and benefits of combining both 
  functions discussed?
- A table listing the maximum per session state 
  maintenance requirements is missing. 
- Error messages don't remove state but they may 
  trigger state removal (see 4.5). Besides an 
  notify message, a Reservation/Tear may travel 
  in parallel. What's the benefit of this solution?
- 2.7 and 6.2 seem to specify NTLP functionalities.

A general comment (not related to this draft):
The Interface between NTLP and NSLP doesn't seem to be defined well. NSLP may need some IP and local topology information (e.g. incoming and outgoing IF). It should be clearly defined where it gets it from.

Regards, Rüdiger

Rüdiger Geib
T-Systems
Systems Integration
Senior Expert, Technologiezentrum
Am Kavalleriesand 3, 64295 Darmstadt
Germany
Fon: +49 6151 832138
http://www.t-systems.com

_______________________________________________
nsis mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/nsis