tsvwg-2----Page:5
1 2 3 4 5
|
Next Steps Get Feedback Reflect discussion on list with John Drake add text on why we want to get sender notification in presence of Receiver Proxy but not in presence of regular receiver Add text on how RSVP-TE already does something extremely similar (ie send PathErr with CAC Reject error code in case of CAC failure). Explain why RSVP-TE generates PathErr from midpoint while this is not applicable here Submit/discuss on the list a candidate optional Phase 2 solution which ensures that: the notification is sent directly to the sender by the failure point (instead of sent by the receiver proxy), which would provide faster sender notification and reduce the RSVP signaling burden on the network this sort of notification is only sent to senders which are capable&willing to do something with it (i.e. synchronize with application signaling) and only sent in case the receiver is not capable&willing to do the synchronization (e.g. receiver proxy). Add text for Security Considerations section |