RE: [XCON] CPCP requirements to support IMS
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [XCON] CPCP requirements to support IMS
Agreed - that is the whole point of contact. You initiate a request
with a generalized location and get pointed to a specific location for
subsequent requests. This fits perfectly.
Chris.
>-----Original Message-----
>From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
>Sent: 04 December 2003 16:23
>To: 'Marjou Xavier'; xcon@ietf.org
>Subject: RE: [XCON] CPCP requirements to support IMS
>
>Look at how 3XX responses are handled in RFC3261
>The Contact header has the URI for the client to use.
>
>Brian
>
>> -----Original Message-----
>> From: Marjou Xavier [mailto:xavier.marjou@siemens.com]
>> Sent: Thursday, December 04, 2003 11:13 AM
>> To: xcon@ietf.org
>> Subject: RE: [XCON] CPCP requirements to support IMS
>>
>>
>> > You send an INVITE to the conference factory uri,
>> > and it returns a Contact which is a conference uri.
>>
>> Although I understand the need for this for an ad-hoc
>> conference, is it really inline with SIP to return a
>> specialized Contact header in a response to an INVITE message?
>>
>> In my opinion, returning a specialized Contact header is only
>> possible during the REGISTER step. (However, I agree I did
>> not find this explicitly written in 3261)
>>
>> Xavier
>>
>>
>>
>>
>>
>> _______________________________________________
>> XCON mailing list
>> XCON@ietf.org
>> https://www1.ietf.org/mailman/listinfo/xcon
>>
>
>_______________________________________________
>XCON mailing list
>XCON@ietf.org
>https://www1.ietf.org/mailman/listinfo/xcon
>
>_______________________________________________________________________
_
>This email has been scanned for all viruses by the MessageLabs Email
>Security System. For more information on a proactive email security
>service working around the clock, around the globe, visit
>http://www.messagelabs.com
>_______________________________________________________________________
_
________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security
service working around the clock, around the globe, visit
http://www.messagelabs.com
________________________________________________________________________
_______________________________________________
XCON mailing list
XCON@ietf.org
https://www1.ietf.org/mailman/listinfo/xcon
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.