Re: [sipcore] [Editorial Errata Reported] RFC5954 (4929)

"Ben Campbell" <ben@nostrum.com> Wed, 08 February 2017 20:04 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42C68129461 for <sipcore@ietfa.amsl.com>; Wed, 8 Feb 2017 12:04:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 t8JAQ9kUNq6q for <sipcore@ietfa.amsl.com>; Wed, 8 Feb 2017 12:04:51 -0800 (PST)
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 C77E912940D for <sipcore@ietf.org>; Wed, 8 Feb 2017 12:04:51 -0800 (PST)
Received: from [10.0.1.39] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v18K4ehX043879 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 8 Feb 2017 14:04:41 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.39]
From: Ben Campbell <ben@nostrum.com>
To: SIPCORE <sipcore@ietf.org>
Date: Wed, 08 Feb 2017 14:04:40 -0600
Message-ID: <F700A4A6-6272-4CA8-9BA2-F67E1D095EBB@nostrum.com>
In-Reply-To: <CAOHm=4vwpyHvC=gs92isXiizYxnMnvHFj0nxKoR4BT6hrT9rAw@mail.gmail.com>
References: <20170208141231.5CEC7B81BE7@rfc-editor.org> <1bd7af57-4504-7bf0-2cae-9067ef356e8c@gmail.com> <CAOHm=4vwpyHvC=gs92isXiizYxnMnvHFj0nxKoR4BT6hrT9rAw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_B0975324-BFAD-4453-A0FA-059BF6ECE71B_="
Embedded-HTML: [{"HTML":[539, 3563], "plain":[143, 2569], "uuid":"8A1BACC5-4E3B-4FF7-814A-30D54B1D6DEF"}]
X-Mailer: MailMate (1.9.6r5344)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/dYxHy85Gr4lgIxBT6KRwCXXMem0>
Cc: aamelnikov@fastmail.fm, alissa@cooperw.in, Keith Drage <drage@alcatel-lucent.com>, Dean Willis <dean.willis@softarmor.com>, david@minix3.org, Brian E Carpenter <brian.e.carpenter@gmail.com>, vkg@bell-labs.com
Subject: Re: [sipcore] [Editorial Errata Reported] RFC5954 (4929)
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 20:04:54 -0000

(+sipcore, -RFC editor)

Does anyone see this as too urgent to hold for document update?

Ben.

On 8 Feb 2017, at 13:43, Dean Willis wrote:

> I agree with Brian on both points.
>
> Yield does not mean surrender...
>
> On Feb 8, 2017 13:13, "Brian E Carpenter" 
> <brian.e.carpenter@gmail.com>
> wrote:
>
>> Well spotted, that's a silly mistake indeed.
>>
>> BTW I think the phrase "yield to" is wrong too. It should be
>> either "yield" or "lead to".
>>
>> Regards
>>    Brian Carpenter
>>
>> On 09/02/2017 03:12, RFC Errata System wrote:
>>> The following errata report has been submitted for RFC5954,
>>> "Essential Correction for IPv6 ABNF and URI Comparison in RFC 3261".
>>>
>>> --------------------------------------
>>> You may review the report below and at:
>>> http://www.rfc-editor.org/errata_search.php?rfc=5954&eid=4929
>>>
>>> --------------------------------------
>>> Type: Editorial
>>> Reported by: David van Moolenbroek <david@minix3.org>
>>>
>>> Section: 3.1
>>>
>>> Original Text
>>> -------------
>>>    Because the <hexpart> production rule is defined such that two of 
>>> its
>>>    alternatives already include the "::" token, this may yield to 
>>> the
>>>    faulty construction of an IPv6-mapped IPv4 address with an extra
>>>    colon when expanding those alternatives.
>>>
>>> Corrected Text
>>> --------------
>>>    Because the <hexpart> production rule is defined such that two of 
>>> its
>>>    alternatives already include the "::" token, this may yield to 
>>> the
>>>    faulty construction of an IPv4-mapped IPv6 address with an extra
>>>    colon when expanding those alternatives.
>>>
>>> Notes
>>> -----
>>> The text refers to an IPv6 address, and thus should use the proper 
>>> term
>> "IPv4-mapped IPv6 address," in line with the section title, the rest 
>> of the
>> document, and (in particular) RFC 4291.
>>>
>>> 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
>>> can log in to change the status and edit the report, if necessary.
>>>
>>> --------------------------------------
>>> RFC5954 (draft-ietf-sip-ipv6-abnf-fix-05)
>>> --------------------------------------
>>> Title               : Essential Correction for IPv6 ABNF and URI
>> Comparison in RFC 3261
>>> Publication Date    : August 2010
>>> Author(s)           : V. Gurbani, Ed., B. Carpenter, Ed., B. Tate, 
>>> Ed.
>>> Category            : PROPOSED STANDARD
>>> Source              : Session Initiation Protocol
>>> Area                : Real-time Applications and Infrastructure
>>> Stream              : IETF
>>> Verifying Party     : IESG
>>>
>>