Subject: Re: [SIP] Record-Route and maddr

From: Sean Olson <[email-masked]>
Date: Wed, 26 Jul 2000 08:46:13 -0500 (CDT)

> From [email-masked]  Wed Jul 26 04:26:53 2000
> Delivered-To: [email-masked]
> Date: Wed, 26 Jul 2000 10:23:12 +0100
> From: Neil Deason <[email-masked]>
> Organization: Ubiquity Software Corporation Limited
> X-Mailer: Mozilla 4.51 [en] (WinNT; I)
> X-Accept-Language: en
> MIME-Version: 1.0
> To: Jonathan Rosenberg <[email-masked]>
> Cc: [email-masked]
> Subject: Re: [SIP] Record-Route and maddr
> Content-Transfer-Encoding: 7bit
> Sender: [email-masked]
> X-Mailman-Version: 1.1
> List-Id: IETF SIP Mailing List <sip.lists.bell-labs.com>
> X-BeenThere: [email-masked]
> 
> Jonathan Rosenberg wrote:
> > 
> > Neil Deason wrote:
> > >
> > > Jonathan Rosenberg wrote:
> > > >
> > > > Neil Deason wrote:
> > > > >
> > > > > >
> > > > > > If you put an IP address into the maddr parameter, yes, the port number
> > > > > > will need to be there if its not 5060. If you put a domain name, you

> At this point, and pre-IETF/Bakeoff, perhaps it is also 
> worth re-raising the issue of a proxy being able to add 
> something into the Record-Route to indicate call state. 
> This was discussed at the 4th bakeoff but it was pointed 
> out using a rr-extension is no use as a proxy wouldn't get 
> it back via the Route header as this gets stripped off. If 
> there is a real desire to achieve this perhaps something 
> added in the name-addr part could work as the proxy should 
> get this as part of the incoming Request-URI?

It was also suggested at the last bakeoff that the Record-route
(and any extensions) should be kept intact and copied verbatim into
the Route header ... but that has obviously changed. 

It would be nice to see the State: header extension proposed by the
DCS group used for this purpose rather than inventing a new 
mechanism. Comments?

--
Sean Olson <[email-masked]>

_______________________________________________
SIP mailing list
[email-masked]
http://lists.bell-labs.com/mailman/listinfo/sip