RE: [Sip] doubt regarding early session in sip RFC 3959/3960

"Brett Tate" <brett@broadsoft.com> Mon, 07 January 2008 23:41 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 1JC1bS-00078P-E2; Mon, 07 Jan 2008 18:41:58 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JC1bQ-00078J-VU for sip-confirm+ok@megatron.ietf.org; Mon, 07 Jan 2008 18:41:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JC1bQ-00078B-Ls for sip@ietf.org; Mon, 07 Jan 2008 18:41:56 -0500
Received: from out002.iad.hostedmail.net ([209.225.56.24]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JC1bQ-00037o-Fp for sip@ietf.org; Mon, 07 Jan 2008 18:41:56 -0500
Received: from ATL1VEXC020.usdom003.tco.tc ([10.158.7.31]) by out002.iad.hostedmail.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 7 Jan 2008 18:41:55 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] doubt regarding early session in sip RFC 3959/3960
Date: Mon, 7 Jan 2008 18:41:54 -0500
Message-ID: <BBE61D1553D8A34F812FF87377B2935F02238F19@ATL1VEXC020.usdom003.tco.tc>
In-Reply-To: <OFD303BB99.002BFDAA-ON652573C2.00236733-E52573C2.0023F69F@aricent.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] doubt regarding early session in sip RFC 3959/3960
Thread-Index: AchLdqxoNNipL/PQQ0yJ5enqwGBudgGCTuMQ
From: "Brett Tate" <brett@broadsoft.com>
To: <Ranjith.V@aricent.com>, <sip@ietf.org>
X-OriginalArrivalTime: 07 Jan 2008 23:41:55.0720 (UTC) FILETIME=[E3130080:01C85186]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: Gonzalo.Camarillo@ericsson.com
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

> UAS is expecting " early-answer " in PRACK from 
> the UAC, what will happen if UAC does not 
> support "100rel" (RFC 3262). 

RFC 3959 section 4 indicates that early-session must follow the
offer/answer model.  Thus an early-session cannot be setup by indicating
an offer within 18x when 100rel is not being used.


> And RFC 3959 is not mandating the "100rel" extension 
> at UA for the same. Can anyone give an example of  
> early session flow in case of  UAC is not 
> supporting "100rel". (UPDATE..?) 
	
It is generically discussed within rfc3959 section 4.  

UPDATE and rfc3311 are not specifically discussed with rfc3959.  I'm not
sure if this was an oversight or because maybe UPDATE currently defined
to "modify" a session instead of "establish" a session.


_______________________________________________
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