IETF Logo Mail Archive

Re: [GROW] [Technical Errata Reported] RFC4384 (4550)

Christopher Morrow <christopher.morrow@gmail.com> Thu, 03 December 2015 02:19 UTC

Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0778A1B2B0F for <grow@ietfa.amsl.com>; Wed, 2 Dec 2015 18:19:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 Ibh5wPo-QCDk for <grow@ietfa.amsl.com>; Wed, 2 Dec 2015 18:19:45 -0800 (PST)
Received: from mail-yk0-x22c.google.com (mail-yk0-x22c.google.com [IPv6:2607:f8b0:4002:c07::22c]) (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 430481ACD87 for <grow@ietf.org>; Wed, 2 Dec 2015 18:19:45 -0800 (PST)
Received: by ykba77 with SMTP id a77so70224955ykb.2 for <grow@ietf.org>; Wed, 02 Dec 2015 18:19:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dRlEfmaU+V74QHRfTlsr3HPtg++w0/LFBbWbmfnuFrs=; b=for0NnMTxRgF2oDVzD/dqSFBZL/PaUihd1EeHTDmNZmjOaj0pIb+x8ULWuS4zeibaT E2dciAsKi3KoR9CPupZBvLb/Ggrldi5VAoL7ASsQ6UE0zlHtOtx4Iwjiqm3Rj7i1l/Wt bVOgsE/kr/ecOtf/OqzsAL7pVCoRtUqIBmsae+S6ZwMR1NxKLIoAyFHkAgLDsg+HkAfS gfK25BAOSehcwGvUZrKpo/li/3/eWohWAy6kQqDJsrR3XWdxmsKXMyismb+cafL9U53o ZGQrSH7tGHM62yQZmBdV58hn3Jo2huhayoyzWiKAQNYiEctUYBpSyUw6AytDrMxYPOw2 riPQ==
MIME-Version: 1.0
X-Received: by 10.129.76.200 with SMTP id z191mr5455555ywa.247.1449109184537; Wed, 02 Dec 2015 18:19:44 -0800 (PST)
Received: by 10.129.99.9 with HTTP; Wed, 2 Dec 2015 18:19:44 -0800 (PST)
In-Reply-To: <CAB_jBhhV6bTQ3i8vhgWm3y9PyBO3XP8JbY3DEf0fWGP1o3+5qA@mail.gmail.com>
References: <20151201221216.984AB180207@rfc-editor.org> <CAHiKxWhyS-+g7hWx4amOwn=qDd5ancwmGH4-FsBrSkkTyLNwwg@mail.gmail.com> <CAB_jBhhV6bTQ3i8vhgWm3y9PyBO3XP8JbY3DEf0fWGP1o3+5qA@mail.gmail.com>
Date: Wed, 02 Dec 2015 21:19:44 -0500
Message-ID: <CAL9jLabShS5EUX4=VriDWY+z++9h27+7BfSsXLFCkQck_up_ig@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: Warren Turkal <wt@penguintechs.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/grow/E3PJ4UFdz-juV_yQpck9AqV6g4Y>
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, David Meyer <dmm@1-4-5.net>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [GROW] [Technical Errata Reported] RFC4384 (4550)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Dec 2015 02:19:47 -0000

seems ok to me to call it that.

On Tue, Dec 1, 2015 at 5:59 PM, Warren Turkal <wt@penguintechs.org> wrote:
> Was it proper to classify this at technical errata? I wasn't sure about
> that.
>
> Thanks,
> wt
>
> On Tue, Dec 1, 2015 at 2:56 PM, David Meyer <dmm@1-4-5.net> wrote:
>>
>> Definitely a good catch. --dmm
>>
>> On Tue, Dec 1, 2015 at 2:12 PM, RFC Errata System
>> <rfc-editor@rfc-editor.org> wrote:
>>>
>>> The following errata report has been submitted for RFC4384,
>>> "BGP Communities for Data Collection".
>>>
>>> --------------------------------------
>>> You may review the report below and at:
>>> http://www.rfc-editor.org/errata_search.php?rfc=4384&eid=4550
>>>
>>> --------------------------------------
>>> Type: Technical
>>> Reported by: Warren Turkal <wt@penguintechs.org>
>>>
>>> Section: 4.1
>>>
>>> Original Text
>>> -------------
>>> The chart at the bottom of 4.1:
>>>
>>>       0                   1                   2                   3
>>>       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>      |      0x00     |      0x0008   |           0x2A7C              |
>>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>      |      0x00     |      0x00     |           0x10F2              |
>>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>
>>> Corrected Text
>>> --------------
>>>       0                   1                   2                   3
>>>       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>      |      0x00     |      0x08     |           0x2A7C              |
>>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>      |      0x00     |      0x00     |           0x10F2              |
>>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>
>>> Notes
>>> -----
>>> The second group has a hex value that looks like two octets:
>>> \\"0x0008\\". If I am interpreting the chart, extended community RFCs, and
>>> the extended community IANA registry correctly, the second group should be a
>>> single octet (i.e. \\"0x08\\").
>>>
>>> Also, the same error is in the Section 4.2 chart as well.
>>>
>>> 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.
>>>
>>> --------------------------------------
>>> RFC4384 (draft-ietf-grow-collection-communities-06)
>>> --------------------------------------
>>> Title               : BGP Communities for Data Collection
>>> Publication Date    : February 2006
>>> Author(s)           : D. Meyer
>>> Category            : BEST CURRENT PRACTICE
>>> Source              : Global Routing Operations
>>> Area                : Operations and Management
>>> Stream              : IETF
>>> Verifying Party     : IESG
>>>
>>
>

v2.23.0 | Report a Bug | By Email