Re: [sipcore] About RFC3911(Join header)'s potential error: //Join header in REFER?

[[e-mail]]

> As far as I know, there are no explicit restrictions.
> 
> One could, however, ask whether it's allowed to include headers that
> are not to be used in the triggered INVITE, but in later associated 
requests.

RFC3261 section 19.1.5

An implementation MUST include any provided transport, maddr, ttl, or
   user parameter in the Request-URI of the formed request.  If the URI
   contains a method parameter, its value MUST be used as the method of
   the request.  The method parameter MUST NOT be placed in the
   Request-URI.  Unknown URI parameters MUST be placed in the message's
   Request-URI.

   An implementation SHOULD treat the presence of any headers or body
   parts in the URI as a desire to include them in the message, and
   choose to honor the request on a per-component basis.

An implementation SHOULD NOT honor these obviously dangerous header
   fields: From, Call-ID, CSeq, Via, and Record-Route.

>From the above text, it seams that the rules for embedded headers is not 
as emphatic as transport, maddr, ttl and user parameter. So, I suggest 
that one specific embedded headers could have a specific usage guidelines, 
especially these headers with dangerous header fields.

I'd like to point out that I am not going to say that people's 
understanding of embedded headers(for pure audio usage) is not correct.

> You CAN also embed SDP information.

Are there any defined rules for such embedded SDP information? If there 
are, could you show me.

Thanks,

Gao


--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.