Hi James,

It might be useful to have some wording on the limitations of using a
response
to carry a Resource-Priority header in a response.

Specifically, a UAS can not use a response to carry the
Resource-Priority
in cases where the Resource-Priority "absolutely has" to be delivered to
the 
UAC. It is therefore only useable for cases where a forking proxy 
may discard the response (i.e., forward another instead) without
breaking
anything. In other words,you need to think about HEFP before using this
draft.

In some scenarios, this is probably the desired behavior.

In other scenarios, it may not acceptable. So instead, for those
scenarios,
the terminating side would have to send a new request with a
Resource-Priority 
instead of using a response.



> -----Original Message-----
> From: James M. Polk [mailto:[EMAIL PROTECTED] 
> Sent: Saturday, June 16, 2007 14:14
> To: [email protected]
> Subject: [Sip] New draft modifying RFC 4412 for Responses
> 
> SIP WG
> 
> Here is a new ID I've written because of implementation 
> considerations to allow a SIP Resource-Priority header (RPH) 
> in responses, which RFC 4412 currently disallows, assuming 
> only that stateful devices will use RPH.  There have been 
> many requests to have this "only stateful devices" 
> restriction relaxed, in certain scenarios.  This ID does 
> this, and proposes how IANA is changed accordingly wrt RPH.  
> This ID does nothing else.
> 
> Comments are appreciated.
> 
> >A New Internet-Draft is available from the on-line Internet-Drafts 
> >directories.
> >
> >         Title           : Allowing SIP Resource Priority Header in 
> > SIP Responses
> >         Author(s)       : J. Polk
> >         Filename        : draft-polk-sip-rph-in-responses-00.txt
> >         Pages           : 6
> >         Date            : 2007-6-15
> >
> >    The Session Initiation Protocol (SIP) Resource Priority Header
> >    (RPH), in its current form, is ignored in SIP responses. 
>  This was a
> >    design choice during RFC 4412's development. This is now 
> considered
> >    a bad design choice in certain scenarios.  This document corrects
> >    RFC 4412's communications model by optionally allowing a 
> SIP server
> >    or user agent client to process the Resource-Priority Header in a
> >    response.
> >
> >A URL for this Internet-Draft is:
> >http://www.ietf.org/internet-drafts/draft-polk-sip-rph-in-res
> ponses-00.
> >txt
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> [EMAIL PROTECTED] for questions on current sip 
> Use [EMAIL PROTECTED] for new developments on the application of sip
> 


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip

Reply via email to