[Tsvwg] draft-ietf-tsvwg-admitted-realtime-dscp-05

["Hannes Tschofenig" <[e-mail]>]

By coincident I ran into the following draft: 
http://tools.ietf.org/html/draft-ietf-tsvwg-admitted-realtime-dscp-05

Section 2.3 says: 

"
   On the point of what protocols and procedures are required for
   authentication, authorization, and capacity admission, we note that
   clear standards do not at this time exist for bandwidth brokers, NSIS
   has not at this time been finalized and in any event is limited to
   unicast sessions, and that RSVP has been standardized and has the
   relevant services.  We therefore recommend the use of RSVP at the
   UNI.  Procedures at the NNI are business matters to be discussed
   between the relevant networks, and are recommended but not required.
"

and the IANA consideration section says:

"
   This traffic class requires the use of capacity admission such as
   RSVP services together with AAA services at the User/Network
   Interface (UNI); the use of such services at the NNI is at the option
   of the interconnected networks.
"

The text (to me) sounds like that this DSCP essentially requires RSVP to be
implemented in order to get this to work. This is IMHO not correct. 

To give you one other example of a standardized mechanism that would do the
job: Rx/Gx (3GPP)

Ciao
Hannes