Re: [dispatch] [sipcore] [Technical Errata Reported] RFC7315 (4474)

"Ben Campbell" <ben@nostrum.com> Wed, 30 September 2015 14:31 UTC

Return-Path: <ben@nostrum.com>
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 64AEF1A8784; Wed, 30 Sep 2015 07:31:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 56_YWPIVxlRK; Wed, 30 Sep 2015 07:31:04 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AF481A8789; Wed, 30 Sep 2015 07:31:04 -0700 (PDT)
Received: from [10.0.1.23] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id t8UEUx17062426 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 30 Sep 2015 09:30:59 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.23]
From: Ben Campbell <ben@nostrum.com>
To: SIPCORE <sipcore@ietf.org>, DISPATCH list <dispatch@ietf.org>
Date: Wed, 30 Sep 2015 09:31:00 -0500
Message-ID: <4E205A3B-F608-48D3-9DA5-D2220A97D953@nostrum.com>
In-Reply-To: <56031836.3080407@nostrum.com>
References: <7594FB04B1934943A5C02806D1A2204B37AC0CF1@ESESSMB209.ericsson.se> <AFF32CE1-BE38-4D4A-9D31-BE86B6748150@nostrum.com> <3308F2DE-08F1-46A0-BC01-2445627BAD53@iii.ca> <56031836.3080407@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.2r5141)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/zs01Bf-1_8Uay9uAWiV3fkkMtkI>
Cc: Cullen Jennings <fluffy@iii.ca>
Subject: Re: [dispatch] [sipcore] [Technical Errata Reported] RFC7315 (4474)
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: Wed, 30 Sep 2015 14:31:06 -0000

(+sipcore, dispatch)
(as individual)

I just realized this discussion did not include the sipcore or dispatch 
lists, and probably should.

Recap: Christer proposed an errata (4474) to RFC 7315. It proposes the 
following change:

> Section 5.4 says:
>
> extension-access-info  = gen-value
>
> It should say:
>
> extension-access-info  = generic-param

The generic-param construction allows the NAME = VALUE syntax as in the 
TS 24.229 extension Jean mentioned below.

Keeping in mind the RFC in question was for 3GPP: Is anyone aware of 
implementations of 7315 that would be broken by this? From Jean's 
example, it looks like 3GPP had already assumed generic-param.

Ben.

On 23 Sep 2015, at 16:23, A. Jean Mahoney wrote:

> FWIW - TS 24.229, which defines the values for access-info, considers 
> extension-access-info to be a generic-param, and not a gen-value as 
> specified RFC7315. 3GPP has defined one extension so far (7.2A.4):
>
>
> daylight-saving-time = "daylight-saving-time" EQUAL quoted-string
>
> TS 124 229 - V12.9.0 - Digital cellular telecommunications system
> (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE;
> IP multimedia call control protocol based on Session Initiation
> Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP
> TS 24.229 version 12.9.0 Release 12) The daylight-saving-time is an
> instance of generic-param from the current extension-access-info
> component of the P- Access-Network-Info header field defined in RFC
> 7315 [52].
>
>
> Jean
>
>
>
> On 9/23/15 3:47 PM, Cullen Jennings wrote:
>> I can see that it might have been better if it had been done this way 
>> Christer is proposing but I don't see how you can change it now. This 
>> change would break existing parsers that checked this. That does not 
>> seem like an errata level thing to me.
>>
>>
>>> On Sep 21, 2015, at 10:30 AM, Ben Campbell <ben@nostrum.com> wrote:
>>>
>>> sipcore and dispatch chairs:
>>>
>>> Do you have any concerns about accepting Christer's errata? (I note 
>>> RFC 7315 was an orphaned sipping draft progressed as AD sponsored.)
>>>
>>> Ben.
>>>
>>> Forwarded message:
>>>
>>>> From: Christer Holmberg <christer.holmberg@ericsson.com>
>>>> To: Ben Campbell <ben@nostrum.com>
>>>> Cc: sipcore@ietf.org <sipcore@ietf.org>
>>>> Subject: Re: [sipcore] [Technical Errata Reported] RFC7315 (4474)
>>>> Date: Mon, 21 Sep 2015 10:26:26 +0000
>>>>
>>>> Any news on this?
>>>>
>>>> Regards,
>>>>
>>>> Christer
>>>>
>>>> From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of 
>>>> Christer Holmberg
>>>> Sent: 14. syyskuuta 2015 23:24
>>>> To: Ben Campbell
>>>> Cc: sipcore@ietf.org
>>>> Subject: Re: [sipcore] [Technical Errata Reported] RFC7315 (4474)
>>>>
>>>> Hi Ben,
>>>>
>>>> I am pretty sure generic-param was the original intention. The 
>>>> majority of all existing value follow the generic-param syntax, and 
>>>> I can't think of any reason why new values would not follow the 
>>>> same syntax. That is how it works for other header fields too.
>>>>
>>>> I think this is due to a mistake, where someone thought that 
>>>> extension-access-info  represents the actual parameter name, and 
>>>> therefor only a value (gen-value) is needed. But, 
>>>> extension-access-info represents the whole rule (name AND value), 
>>>> why generic-param is needed :)
>>>>
>>>> Regards,
>>>>
>>>> Christer
>>>>
>>>> Sent from my Windows Phone
>>>> ________________________________
>>>> From: Ben Campbell<mailto:ben@nostrum.com>
>>>> Sent: ‎14/‎09/‎2015 21:31
>>>> To: Christer Holmberg<mailto:christer.holmberg@ericsson.com>
>>>> Cc: sipcore@ietf.org<mailto:sipcore@ietf.org>
>>>> Subject: Re: [sipcore] [Technical Errata Reported] RFC7315 (4474)
>>>> Hi Christer,
>>>>
>>>> Is it your understanding that the use of generic-param was the 
>>>> actual
>>>> intention at the time 7315 was published? Or was gen-value the 
>>>> original
>>>> intention, but we now think that it should have been generic-param?
>>>>
>>>> Thanks!
>>>>
>>>> Ben.
>>>>
>>>> On 14 Sep 2015, at 6:22, Christer Holmberg wrote:
>>>>
>>>>> FYI,
>>>>>
>>>>> I've now submitted the errata.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Christer
>>>>>
>>>>> -----Original Message-----
>>>>> From: RFC Errata System [mailto:rfc-editor@rfc-editor.org]
>>>>> Sent: 14. syyskuuta 2015 14:21
>>>>> To: r.jesske@telekom.de<mailto:r.jesske@telekom.de>; 
>>>>> drage@alcatel-lucent.com<mailto:drage@alcatel-lucent.com>; 
>>>>> Christer Holmberg;
>>>>> iesg@ietf.org<mailto:iesg@ietf.org>
>>>>> Cc: Christer Holmberg; 
>>>>> rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>
>>>>> Subject: [Technical Errata Reported] RFC7315 (4474)
>>>>>
>>>>> 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=4474
>>>>>
>>>>> --------------------------------------
>>>>> Type: Technical
>>>>> Reported by: Christer Holmberg 
>>>>> <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>>
>>>>>
>>>>> Section: 5.4
>>>>>
>>>>> Original Text
>>>>> -------------
>>>>> extension-access-info  = gen-value
>>>>>
>>>>> Corrected Text
>>>>> --------------
>>>>> extension-access-info  = generic-param
>>>>>
>>>>> Notes
>>>>> -----
>>>>> Most of the pre-defined access-info values are following the
>>>>> generic-param syntax. New access-info values (extensions) should 
>>>>> also
>>>>> be allowed to follow the generic-param syntax, in order to allow 
>>>>> both
>>>>> for a name and value of the extension.
>>>>>
>>>>> 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
>>>>>
>>>>> _______________________________________________
>>>>> sipcore mailing list
>>>>> sipcore@ietf.org<mailto:sipcore@ietf.org>
>>>>> https://www.ietf.org/mailman/listinfo/sipcore
>>>> _______________________________________________
>>>> sipcore mailing list
>>>> sipcore@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/sipcore