IETF Logo Mail Archive

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

Christopher Morrow <christopher.morrow@gmail.com> Tue, 01 December 2015 22:49 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 83BD81AD34D for <grow@ietfa.amsl.com>; Tue, 1 Dec 2015 14:49:56 -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 JJLBUYofdqZ2 for <grow@ietfa.amsl.com>; Tue, 1 Dec 2015 14:49:52 -0800 (PST)
Received: from mail-yk0-x22b.google.com (mail-yk0-x22b.google.com [IPv6:2607:f8b0:4002:c07::22b]) (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 859A31AD352 for <grow@ietf.org>; Tue, 1 Dec 2015 14:49:41 -0800 (PST)
Received: by ykba77 with SMTP id a77so26287944ykb.2 for <grow@ietf.org>; Tue, 01 Dec 2015 14:49:41 -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=zhgO7a1C81/+0qOTuD7SjIj58JjjV3sXv349njGMEA4=; b=ZF+423a9KMQhRnJkGSiQdHUYhFZM/nNtjY22CcCEyNqqoV3SqspF6fuZqsTm7gzN0S /Cd1Oa+ibR/XKPJbi+0jVBnLgmSDeL2AaW1BJAHvB4wTF7WVdTiwPAt9kr8g2QfxCFsx hsc34WuIY1BS5O8W2Xe7iACReKYFRQj+EV9DvQd3jhDqlrgRnn9WFkMwdd1ML1HYyZmL JReZmZ3sDA2cb/ts6ywQg5igLc3EOTOAhGJkwFRrHv9knAtWrEaQkNLrlLYbphaTr8Ch fnKUtDT3USdrl3Cy5ebf0UHi4YBI5PDLnTdmtSNWDAiOmTZFRfhxrnJpOdpHEJDUCBEw +ooA==
MIME-Version: 1.0
X-Received: by 10.129.32.213 with SMTP id g204mr61318628ywg.234.1449010180854; Tue, 01 Dec 2015 14:49:40 -0800 (PST)
Received: by 10.129.99.9 with HTTP; Tue, 1 Dec 2015 14:49:40 -0800 (PST)
In-Reply-To: <20151201221216.984AB180207@rfc-editor.org>
References: <20151201221216.984AB180207@rfc-editor.org>
Date: Tue, 01 Dec 2015 17:49:40 -0500
Message-ID: <CAL9jLabTpG_Aq7S7qS3K-sMD4R3G9ieEUxUXDjwmKVNydORY2Q@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/grow/fnGKnQI-aoP3c1nBmaZzok4Tmck>
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, wt@penguintechs.org, "Dave Meyer (hosted)" <dmm@1-4-5.net>
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: Tue, 01 Dec 2015 22:49:56 -0000

(not an author but) seems like a good  catch.

On Tue, Dec 1, 2015 at 5: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