RE: I-D ACTION:draft-ash-mpls-dste-bcmodel-max-alloc-resv-00.txt

["Ash, Gerald R (Jerry), ALASO" <gash@att.com>]

Neil,
 
> What assumptions (if any) are you making about a given
> application/customer's ability to class-hop?  That is, potential to change
> class types (maybe at will?) based on current/past QoS experience and
> charging regime.

Interesting question.  I don't think any of the default BC models being discussed (Russian Doll, Maximum Allocation, or Maximum Allocation with Reservation) make any assumption on class-hop.  More generally, I don't believe we have a requirement for class-hop capability in the default BC model.

Questions to list:

1. do we need a requirement for class-hop capability in the default BC model?
2. if so, what would be the necessary protocol mechanisms to make class-hop possible?

Thanks,
Jerry