Re: [dispatch] Fwd: [Technical Errata Reported] RFC7315 (4540)

Paul Kyzivat <pkyzivat@alum.mit.edu> Fri, 20 November 2015 15:35 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4FC61B2A41 for <dispatch@ietfa.amsl.com>; Fri, 20 Nov 2015 07:35:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FXeq9hZaspDQ for <dispatch@ietfa.amsl.com>; Fri, 20 Nov 2015 07:35:06 -0800 (PST)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55A8C1B2A40 for <dispatch@ietf.org>; Fri, 20 Nov 2015 07:35:06 -0800 (PST)
Received: from resomta-ch2-16v.sys.comcast.net ([69.252.207.112]) by resqmta-ch2-10v.sys.comcast.net with comcast id jraj1r0032S2Q5R01rb525; Fri, 20 Nov 2015 15:35:05 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-16v.sys.comcast.net with comcast id jrb51r0013KdFy101rb5yX; Fri, 20 Nov 2015 15:35:05 +0000
To: dispatch@ietf.org
References: <20151120052258.5F6D2180205@rfc-editor.org> <1B9066A1-5130-44D2-B2CB-D869111ECC86@nostrum.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <564F3DA8.4010806@alum.mit.edu>
Date: Fri, 20 Nov 2015 10:35:04 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <1B9066A1-5130-44D2-B2CB-D869111ECC86@nostrum.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1448033705; bh=o2T17qtdd7c+53CdP6F/s1awTn+gWGC0wHpSeU4A9E0=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=iBXh22xMnTfma3fTSX8cQGy7eiGrUqluN3ZTEJPKpm63iY+BFOQ1dzdxEvtgZJnkz gDHdPLk5Vin+wq0QdNLJSlktkfNRi2UgJVfnNJUQK5F2nenEbvAoMczt8awMRCNiFS 9t/wOTiyMMIc78FfB0tqtyPjI/UkVHxuUo1vVt0kDaNDB8TRNcSpAahHqPzlks5SPs NMql8TlmHSZlzDb9khpwyKe6y2ZAIseoGJIca0IbTkxWsGIPuwSKvAmXYku23ze6t1 Abn1vS+i4AsyWgexuUxSRhFZTZ7jOg8D6XHG6bQnMOq4+/HFOeRSudJgSe7mEBB73M 7S2WF6+fIftbQ==
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/y1RgafoJ7-5Yk7bKyCMRgXgFOJs>
Subject: Re: [dispatch] Fwd: [Technical Errata Reported] RFC7315 (4540)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Nov 2015 15:35:08 -0000

On 11/20/15 10:07 AM, Ben Campbell wrote:
> Hi,
>
> Do others agree with this errata report?

IIUC, 7315 has revised the usage so that the optionality of the URI is 
no longer needed. But the current definition still *works* with 7315. 
(The feature being proposed for removal won't be used.) So I don't see 
that there is an error to fix. The "fix" will mean that implementations 
using 3455 could fail to interoperate with implementations using 7315.

ISTM it would be better to leave the syntax unchanged, but add text 
indicating that use with an empty URI is deprecated, but should be 
accepted for backward compatibility.

	Thanks,
	Paul

> Thanks!
>
> Ben.
>
> Forwarded message:
>
>> From: RFC Errata System <rfc-editor@rfc-editor.org>
>> To: r.jesske@telekom.de, drage@alcatel-lucent.com,
>> christer.holmberg@ericsson.com, iesg@ietf.org
>> Cc: dongo.yi@lge.com, rfc-editor@rfc-editor.org
>> Subject: [Technical Errata Reported] RFC7315 (4540)
>> Date: Thu, 19 Nov 2015 21:22:58 -0800 (PST)
>>
>> The following errata report has been submitted for RFC7315,
>> "Private Header (P-Header) Extensions to the Session Initiation
>> Protocol (SIP) for the 3GPP".
>>
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=7315&eid=4540
>>
>> --------------------------------------
>> Type: Technical
>> Reported by: Dongo Yi <dongo.yi@lge.com>
>>
>> Section: 5.1
>>
>> Original Text
>> -------------
>> 5.1. P-Associated-URI Header Syntax
>>
>>
>> The syntax of the P-Associated-URI header field is described as
>> follows:
>>
>>       P-Associated-URI       = \\"P-Associated-URI\\" HCOLON
>>                                [p-aso-uri-spec]
>>                                *(COMMA p-aso-uri-spec)
>>       p-aso-uri-spec         = name-addr *(SEMI ai-param)
>>       ai-param               = generic-param
>>
>>
>> Corrected Text
>> --------------
>> 5.1. P-Associated-URI Header Syntax
>>
>>
>> The syntax of the P-Associated-URI header field is described as
>> follows:
>>
>>       P-Associated-URI       = \\"P-Associated-URI\\" HCOLON
>>                                (p-aso-uri-spec)
>>                                *(COMMA p-aso-uri-spec)
>>       p-aso-uri-spec         = name-addr *(SEMI ai-param)
>>       ai-param               = generic-param
>>
>>
>> Notes
>> -----
>> P-Associated-URI cannot include an empty header value (which was able
>> to be included according to RFC 3455)
>>
>> - Background.
>>
>> The policy of P-Associated-URI has been updated from RFC 3455.
>> RFC 3455 : 4.1.2.2 Procedures at the registrar
>> ...
>> In case the address-of-record under registration does not have any
>> other SIP or SIPS URIs associated, the registrar MUST include an
>> empty P-Associated-URI header value.
>>
>>
>> RFC 7315 : 4.1.2.2 Procedures at the Registrar
>> ...
>> If the address-of-record under registration does not have any
>> associated URIs, the P-Associated-URI header field SHALL NOT be
>> included.
>> ...
>>
>> Moreover, we can say RFC 3455 has same errata based on this analysis.
>>
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". If necessary, please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party (IESG)
>> can log in to change the status and edit the report, if necessary.
>>
>> --------------------------------------
>> RFC7315 (draft-drage-sipping-rfc3455bis-14)
>> --------------------------------------
>> Title               : Private Header (P-Header) Extensions to the
>> Session Initiation Protocol (SIP) for the 3GPP
>> Publication Date    : July 2014
>> Author(s)           : R. Jesske, K. Drage, C. Holmberg
>> Category            : INFORMATIONAL
>> Source              : IETF - NON WORKING GROUP
>> Area                : N/A
>> Stream              : IETF
>> Verifying Party     : IESG
>>
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>