[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[NSIS] QoS NSLP: RSN + tear down



Hi all,

I now have the QoS NSLP spec updated with the recent comments. One issue 
remains, that I'd like a confirmation before sending out to you for review 
v. "13-pre2".

Issue: RSN + tear down

We have earlier decided that RSNs would not be interpreted when tearing 
down a reservation. However, we actually need to interpret them, otherwise 
the path change mechanism currently specified will not work (see my 
previous email about the mobility work today).

Thus, I propose that when a node receives a tearing RESERVE, it MUST 
interpret and compare the RSN in the message to the stored RSN. 

1. If the RSN values match, the QNE MUST perform the tear down and send 
   out a tearing RESERVE with the RSN object.

2. If the received RSN is greater than the stored RSN, the QNE MUST 
   perform the tear down, and send out a tearing RESERVE with the received 
   greater RSN value.

3. If the received RSN is less than the stored RSN, the QNE MUST silently 
   drop the tearing RESERVE, and not perform any tear down, nor send out 
   any tearing RESERVE.



Jukka


_______________________________________________
nsis mailing list
nsis at ietf.org
https://www1.ietf.org/mailman/listinfo/nsis