[SIPForum-discussion] "maddr" parameter usage in SIP

[Robert Sparks]

19.1.1 is where you'll find the meat:

         (talking about URI components):

         The maddr parameter indicates the server address to be
          contacted for this user, overriding any address derived from
          the host field.  When an maddr parameter is present, the port
          and transport components of the URI apply to the address
          indicated in the maddr parameter value.  [4] describes the
          proper interpretation of the transport, maddr, and hostport in
          order to obtain the destination address, port, and transport
          for sending a request.

          The maddr field has been used as a simple form of loose source
          routing.  It allows a URI to specify a proxy that must be
          traversed en-route to the destination.  Continuing to use the
          maddr parameter this way is strongly discouraged (the
          mechanisms that enable it are deprecated).  Implementations
          should instead use the Route mechanism described in this
          document, establishing a pre-existing route set if necessary
          (see Section 8.1.1.1).  This provides a full URI to describe
          the node to be traversed.

In any case, 3261 is your only source for inspiration on using this  
parameter.

RjS

On Jul 19, 2007, at 5:02 AM, mark lee wrote:

> Hi,all:
> In RFC3261 section 18.1.1, "maddr" is used when the request is  
> multicasted but "maddr" parameter in Request-URI is unclear in the  
> meaning, and how to use it? does it have other use cases except  
> this one?
>
> Thanks
> Gogofly
>
>
> 抢注雅虎免费邮箱3.5G容量，20M附件！
> _______________________________________________
> This is the SIP Forum discussion mailing list
> TO UNSUBSCRIBE, or edit your delivery options, please visit http:// 
> sipforum.org/mailman/listinfo/discussion
> Post to the list at discussion at sipforum.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20070723/fe786a74/attachment-0002.html>