draftietftsvwgrsvpemergency04 txt RSVP Extensions for Emergency Services Francois

The Issue • Three different document –dime-qos-parameters –nsis-qspec, –tsvwg-emergency-rsvp • need to convey an

The Proposal (RPH-Priority) • tsvwg-emergency-rsvp includes IANA request to provide numerical registry for RPH

The Proposal (Admission Priority) • nsis-qspec, dime-qos-parameters and tsvwg-emergency-rsvp will all: üonly indicate that

Status üProposal agreed by co-authors of three I-Ds and co-chairs of three WGs üProposal

Slides: 5

draft-ietf-tsvwg-rsvp-emergency-04. txt RSVP Extensions for Emergency Services Francois Le Faucheur - flefauch@cisco. com Francois Le Faucheur, James Polk, Cisco Systems IETF 70/TSVWG: RSVP Extensions for Emergency Ken Carlberg G 11 1

The Issue • Three different document –dime-qos-parameters –nsis-qspec, –tsvwg-emergency-rsvp • need to convey an overlapping set of Qo. S parameters –RPH-Priority –Admission Priority • currently do that in an inconsistent manner IETF 70/TSVWG: RSVP Extensions for Emergency 2

The Proposal (RPH-Priority) • tsvwg-emergency-rsvp includes IANA request to provide numerical registry for RPH priority via extending existing RPH registry • nsis-qspec, dime-qos-parameters and tsvwg-emergency-rsvp all point to this registry IETF 70/TSVWG: RSVP Extensions for Emergency 3

The Proposal (Admission Priority) • nsis-qspec, dime-qos-parameters and tsvwg-emergency-rsvp will all: üonly indicate that "higher value means higher priority üno attempt to define what specific values should be used for what. üadd a statement clarifying that a given Admission Priority is to be encoded with the same value in each of the three protocol spec IETF 70/TSVWG: RSVP Extensions for Emergency 4

Status üProposal agreed by co-authors of three I-Ds and co-chairs of three WGs üProposal posted on 3 WG lists for comments üdraft-tsvwg-emergency-rsvp-04. txt already in line with the proposal IETF 70/TSVWG: RSVP Extensions for Emergency 5