Re: [Sip] Contact header in 1xx responses/updates remote target ornot?

"Jeroen van Bemmel" <jbemmel@zonnet.nl> Sat, 26 May 2007 10:53 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hrttl-0001zS-C1; Sat, 26 May 2007 06:53:25 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Hrttk-0001zK-Iz for sip-confirm+ok@megatron.ietf.org; Sat, 26 May 2007 06:53:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hrttk-0001zC-9N for sip@ietf.org; Sat, 26 May 2007 06:53:24 -0400
Received: from smtp1.versatel.nl ([62.58.50.88]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hrtti-0000Tn-R9 for sip@ietf.org; Sat, 26 May 2007 06:53:24 -0400
Received: (qmail 28502 invoked by uid 0); 26 May 2007 10:54:37 -0000
Received: from ip198-11-212-87.adsl2.versatel.nl (HELO BEMBUSTER) ([87.212.11.198]) (envelope-sender <jbemmel@zonnet.nl>) by smtp1.versatel.nl (qmail-ldap-1.03) with SMTP for < >; 26 May 2007 10:54:37 -0000
Message-ID: <000601c79f83$d1f401b0$0601a8c0@BEMBUSTER>
From: Jeroen van Bemmel <jbemmel@zonnet.nl>
To: sip@ietf.org, Dale.Worley@comcast.net
References: <4656BDFE.7020006@zesium.com> <200705260454.l4Q4sYOV027172@dragon.ariadne.com>
Subject: Re: [Sip] Contact header in 1xx responses/updates remote target ornot?
Date: Sat, 26 May 2007 12:51:31 +0200
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc:
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

Dale,

Not sure if I read your comment right, but RFC3261 12.2.1.2 says

When a UAC receives a 2xx response to a target refresh request, it
   MUST replace the dialog's remote target URI with the URI from the
   Contact header field in that response, if present.
It does not say anything about 1xx responses here though...Regards,Jeroen
Dale.Worley@comcast.net wrote:
>   From: Nina Garaca <nina.garaca@zesium.com>
> 
>   Q1:  Should I expect that these responses have a Contact header?
> 
> As Paul says, if it didn't have a Contact header, it couldn't
> establish a dialog.
> 
>   Q2:  If they do so, should the remote target of the dialog be
>   refreshed by that Contact at the side that has received that 1xx
>   response and should the remote target of the dialog be refreshed by
>   the Contact in the INVITE request at the side that has received
> that INVITE? 
> 
> Responses are not "target refresh requests", so they don't change the
> target address at their end of the dialog.  But of course, the
> responses to the dialog-initiating request establish the initial
> target address.
> 
>   Q3: If not, should the remote target of the dialog be refreshed by
>   the Contact in the INVITE request
>       at the side that has received that INVITE and has sent dialog
>   establishing 1xx response?
> 
> RFC 3261 section 12.2:
> 
>   INVITE, the only target refresh request defined is re-INVITE (see
>   Section 14).  Other extensions may define different target refresh
>   requests for dialogs established in other ways.
> 
> Dale
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org 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 sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip