Subject: [NSIS] RE: qos-nslp-00

From: "Geib, Ruediger" <[email-masked]>
Date: Wed, 24 Sep 2003 13:26:26 +0200

Hi Sven,

maybe we have different concepts of what a session ID identifies. 
To me it identifies the flow of packets for which you request a 
service by NSIS signaling. I think that is exactly what you use 
the RSN for in the case of refreshes.
What is your definition of session ID?

Regards, Rüdiger

||- Retransmitted "Reservation Sequence Numbers"
||  serve as a Session ID. Why aren't
||  the tradeoffs and benefits of combining both
||  functions discussed?
||
||Sven>> We took special care not to use the RSN for anything else but
||ensuring that QoS NSLP message reordering could be detected.
||They have nothing to do with any session ID at the NTLP. Afaik, it is
||an open issue how NTLP sessions will relate to NSLP message exchanges.
|
|[Rudi]: Section 4.2 introduces a summary refresh using the RSN to
|identify a reservation. This isn't related to reordering.
|
|Sven>> It is used in the summary refresh, but this is purely a QoS NSLP
|matter that is unrelated to the session ID. Note that we see 
|the summary refresh with RSN as a minimal case but that other objects
|or parameters may be part of it.

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