Re: [Sip] [sipcore] [Technical Errata Reported] RFC3261 (2910)

Robert Sparks <rjsparks@nostrum.com> Wed, 03 August 2011 15:46 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: sip@ietfa.amsl.com
Delivered-To: sip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B78121F8BD7; Wed, 3 Aug 2011 08:46:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.45
X-Spam-Level:
X-Spam-Status: No, score=-102.45 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yxy-HRPihiXt; Wed, 3 Aug 2011 08:46:02 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 354C021F8BBD; Wed, 3 Aug 2011 08:46:01 -0700 (PDT)
Received: from dn3-177.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p73Fk9Il028341 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 3 Aug 2011 10:46:10 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <CALiegf=1=ZqEcs0kE=Y+ykrcd9miPDSN=mzP99-EWytVXdXMwA@mail.gmail.com>
Date: Wed, 3 Aug 2011 10:46:10 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <9B06B312-4BCF-499D-979F-33D8E70DAD5A@nostrum.com>
References: <20110802145359.C9DEE98C50D@rfc-editor.org> <DC49588FF3643F43B3A2A8F6F0A625F0284638642A@mailbox1.acmepacket.com> <69373B11-F46D-4F88-B4A8-BF56A8EC2624@nostrum.com> <CALiegf=1=ZqEcs0kE=Y+ykrcd9miPDSN=mzP99-EWytVXdXMwA@mail.gmail.com>
To: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: "sip@ietf.org List" <sip@ietf.org>, "SIPCORE \(Session Initiation Protocol Core\) WG" <sipcore@ietf.org>
Subject: Re: [Sip] [sipcore] [Technical Errata Reported] RFC3261 (2910)
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 15:46:03 -0000

(removing the rfc-editor and trimming the distribution to the lists)

On Aug 2, 2011, at 5:24 PM, Iñaki Baz Castillo wrote:

> 2011/8/2 Robert Sparks <rjsparks@nostrum.com>om>:
>> Further, they're only going to make sense for 1xx that is sent using 100rel.
> 
> This has been discussed in sip-implementors, and that assertion seems
> incorrect. As I've reported in the errata:
> 
> 
> Section 12.1: "Dialogs are created through the generation of
> non-failure responses to requests with specific methods. Within this
> specification, only 2xx and 101-199 responses with a To tag, where the
> request was INVITE, will establish a dialog."
> 
> Section 12.1.1: "When a UAS responds to a request with a response that
> establishes a dialog (such as a 2xx to INVITE), the UAS MUST copy all
> Record-Route header field values from the request into the response
> [...]. The UAS MUST add a Contact header field to the response."
> 
> So it's clear that a 1xx response to an INVITE creates a dialog and
> then it MUST contain a Contact header and mirrored Record-Route
> headers, *regardless* the usage of 100rel.
> 
> Am I wrong? if so, why?

Not wrong, just incomplete. This will create an (early) dialog at the UAS.
It may or may not create a dialog at the UAC without 100rel since the
message may never get to the UAC. Where I said "make sense" above,
it might have been better if I had said "be useful".

> 
> Regards.
> 
> 
> -- 
> Iñaki Baz Castillo
> <ibc@aliax.net>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore