Re: liason & the 5 priorities

> If priority and preemption can be accomplished at the admission level
> (SIP and/or microflow RSVP level) then it may be that policing and the
> existing EF is sufficient.  Its only where insufficient bandwidth is
> allocated and carved into categories and adaptive elastic services are
> carried is something like AF needed.  None of the above existing
> examples fit the latter category.  It would be nice though if one more
> first responder needed to communicate that flow was not blocked but
> service quality for some dropped to a more efficient but slightly less
> clear audio compression.  Currently that is not possible in any of the
> above deployments (afaik).

true.  one effort that may compliment what you are looking for is a  
draft being advanced in TSVWG, involving a proposed extension to  
RSVP.  In the following draft, the appendix presents several  
potential modes of operation, one of which focuses on carefully  
engineered capacity.
http://www.ietf.org/internet-drafts/draft-lefaucheur-emergency- 
rsvp-02.txt

there is also a new BoF titled Pre-Congestion Notification (PCN)  
scheduled for San Diego that also touches on what you bring up in  
your last sentence above.  The BoF stems from several related drafts  
discussed in TSVWG including the architecture draft of:

http://www.ietf.org/internet-drafts/draft-briscoe-tsvwg-cl- 
architecture-03.txt
(a cast of thousands :)

along with a problem statement that has been discussed on the PCN list
http://www.ietf.org/internet-drafts/draft-chan-pcn-problem- 
statement-00.txt
with updated issues list leading to the meeting
http://standards.nortel.com/pcn/ProblemStatementDraftIssuesList.txt

PCN mailing list: https://www1.ietf.org/mailman/listinfo/pcn

-ken