IETF Logo Mail Archive

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

David Meyer <dmm@1-4-5.net> Tue, 01 December 2015 22:56 UTC

Return-Path: <dmm@1-4-5.net>
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 0D4C91ACEC7 for <grow@ietfa.amsl.com>; Tue, 1 Dec 2015 14:56:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] 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 oShI-ZacNWnP for <grow@ietfa.amsl.com>; Tue, 1 Dec 2015 14:56:03 -0800 (PST)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (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 4B4C81A21B6 for <grow@ietf.org>; Tue, 1 Dec 2015 14:56:03 -0800 (PST)
Received: by oixx65 with SMTP id x65so13972475oix.0 for <grow@ietf.org>; Tue, 01 Dec 2015 14:56:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1-4-5-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jcsKDpWrAYPC8FzUISFyTrgfv+y/wqBltqghG+kSf0U=; b=IUvtzyBJdyzUmFJpjv1AiKkbY3U7Eh49ME+n/46QWl3SUgoPgQKW1hTo2WjhToda5i sr7UdooCN4srXQ7cfgHj6NHp0NusdTM9Kn1ZRFJcckke3NrpQwvQBvS42N3Tf4HKmZIj 2Mn3e6ktKDdxvcfi/rGqkMrhiygk+tp70jyYrN8R/0CpgeuXT088mCklOF/5Pln3bGjV KT6R0oAZEE3Zuw2uE7R1wspVqFC9BXhsE7yKsxvFrXKyPC7sfxWLPN0jpbWXrBdX11Gm Rh5oqWa0Yr2w/Znx0UYy9PeuOAYhNe2ABMwVdMuWm8JKNECmcef7vgdlHrmCSXn1BYds 92HA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=jcsKDpWrAYPC8FzUISFyTrgfv+y/wqBltqghG+kSf0U=; b=bOiDetX56tzZi176/S2qCftSi651PAkw0Rr2W2xRxW8NFJ6TOie5ZbeZ73tED4U64l aIQDY4B7V5cuufzRmuG0eTBHZYomS4gxR2YJFaFfO3OdOLwohFcaU3O43aaK/w71rVnJ ButxwcIVwi9OKzKT9dQBKwnQfIijJb1mm5zYKBIp/kCQVXNAlpZgvVDEJRxu4tb20Q0d qHHP6XV4m3PRz82uENIo9QP705eCKTaEi4EGmCgoJ/7QJRmhwEYQJ31y5eXSHr0NOKxp C8JWynQ+b/VxmNi1KJ0bC4uUI9AftDIDj7XW3rDBuZifxzMUO/GyVaAscPCu6c9n0+Jo A0qw==
X-Gm-Message-State: ALoCoQmm6i6lJ28lEzhGCA0oexKE7FMbdjVS5snLYfayx6K1hp2TPp3cX5hFm7c/snHa1C4cNYrk
MIME-Version: 1.0
X-Received: by 10.202.72.132 with SMTP id v126mr48974821oia.84.1449010562684; Tue, 01 Dec 2015 14:56:02 -0800 (PST)
Received: by 10.202.214.77 with HTTP; Tue, 1 Dec 2015 14:56:02 -0800 (PST)
X-Originating-IP: [2001:468:d01:9c::80df:9cfd]
In-Reply-To: <20151201221216.984AB180207@rfc-editor.org>
References: <20151201221216.984AB180207@rfc-editor.org>
Date: Tue, 01 Dec 2015 14:56:02 -0800
Message-ID: <CAHiKxWhyS-+g7hWx4amOwn=qDd5ancwmGH4-FsBrSkkTyLNwwg@mail.gmail.com>
From: David Meyer <dmm@1-4-5.net>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: multipart/alternative; boundary="001a113dc40edd71000525de0f97"
Archived-At: <http://mailarchive.ietf.org/arch/msg/grow/9rFifXMti2fSser1vVBIaAEJ97g>
Cc: grow@ietf.org, wt@penguintechs.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: Tue, 01 Dec 2015 22:56:05 -0000

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