James M. Polk | 28 Sep 2006 20:51
Picon
Favicon

Re: proposed charter 5 priority levels

At 01:29 AM 9/28/2006 -0400, Curtis Villamizar wrote:

>In message <6.2.1.2.0.20060927173433.0323abd0 <at> ihmail.ih.lucent.com>
>John Rosenberg writes:
>
>It's been mentioned that both RSVP and NSIS can carry both SIp priority and
>DSCP.

RSVP does not carry a SIP RPH text based namespace or priority-value, and 
NSIS (I believe) does not carry a RPH namespace in text, just a registered 
equivalent of the priority-value

<snip>

> > Thanks,
> >
> > John
>
>
>I'm not sure why the above example is special.  An RSVP PATH message
>and RESV response (passed back from the IP egress) should precede any
>SIP control traffic

SIP messages are always first, prior to any RSVP or NSIS messages, how else 
would a called party know what bandwidth to request in the RESV?

It also doesn't make a lot of sense sending a NSIS REQUEST message 
reserving resources if the called party isn't going to accept the call (for 
whatever reason).  This would be a waste of BW, and could case existing 
calls to be preempted unnecessarily.
(Continue reading)


Gmane