Re: [Pals] [Editorial Errata Reported] RFC4664 (5644)

Stewart Bryant <stewart.bryant@gmail.com> Wed, 27 February 2019 17:12 UTC

Return-Path: <stewart.bryant@gmail.com>
X-Original-To: pals@ietfa.amsl.com
Delivered-To: pals@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 664A8130FBF; Wed, 27 Feb 2019 09:12:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 xUz3I_F7VKlw; Wed, 27 Feb 2019 09:12:12 -0800 (PST)
Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) (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 706891289FA; Wed, 27 Feb 2019 09:12:11 -0800 (PST)
Received: by mail-wm1-x32c.google.com with SMTP id n19so6572112wmi.1; Wed, 27 Feb 2019 09:12:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=kEyDX/vY1M42Xme/1HcewIeSyQPV6uVQmYj9BthtKF8=; b=XMJB+fxy9neziz6XVgSzJah5Yq0wUpZMrGlEoBx9hRfdvgkVBj3uV2PdntLznpb+VT FQG1A3YlMOSMJrRZNnLywwdXhcIVu60IxTxcAkgtTQUaffeEMc7+3uqjBAH9lj9U8Sy8 tNmtC+rs9YhJDctwwgGh8yDAcWVnS2bnYeoNQhQYUFQcsEOibMU4VIghDEWCTiRhdnmK 9g5kIUjRQB6yScshL0xRPvyqSIJmr4z7hOC72t3Nu/GfXA6pgDdPmndjMmIfYHZRK9Ih +uZFE8LObAe0iQqsZMScOXNTRUOw6ikXkFvnhuusrRdzQlJJ+uQWwPXJeC34W7PlNalE OTEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=kEyDX/vY1M42Xme/1HcewIeSyQPV6uVQmYj9BthtKF8=; b=s1k04uo/k3ZMbcvn1O+vPOi3xyNUY1wvw+5wNDNEvgasTm+1LSA3F5mfRwE8H6ZOkE 3xv6MmX7WVLQzqvC24tOC6XSbMjzWgWTKJZ8gKwvw/InX9XxoaLGWya6FZXLYhLTEmJP fA6ba1by/jZ/6p5UKtARuggA6WKJvnctgRjoAJRMEnUJrTjSPTmaApH9sEKL25nF6mdb I1WowGMLnQ8neGHi5l6Tf8JPLyD4o5dsgpHbe//xCmrEh269h6WcA9Ok/lK7jlPGAQoy d0DsT5sBIHFIuTaeq55G2ICTyIDtr83RgCE6isPsYr6DLi+PjD2F25tVGKcX6noFPmqt vf8g==
X-Gm-Message-State: AHQUAuae3JQhDQmFMpuDURXCek4DeHmGKKo5QxHuGPLgJDBMUSGHPjLC fjkqoyqazjfAji9YV6JbhGI=
X-Google-Smtp-Source: APXvYqxhgeTUe6y42vN/5l/7io4UB8cJhcmm6kU+CWYiuaLsbUFcGlfCSgrl/OcxtAHKQjEW5mudDg==
X-Received: by 2002:a1c:7a03:: with SMTP id v3mr182166wmc.59.1551287529719; Wed, 27 Feb 2019 09:12:09 -0800 (PST)
Received: from [192.168.178.22] ([62.3.64.16]) by smtp.gmail.com with ESMTPSA id d2sm16412441wrq.94.2019.02.27.09.12.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 27 Feb 2019 09:12:08 -0800 (PST)
To: "Andrew G. Malis" <agmalis@gmail.com>, RFC Errata System <rfc-editor@rfc-editor.org>
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "Giles Heron (giheron)" <giheron@cisco.com>, "BRUNGARD, DEBORAH A (ATTLABS)" <db3546@att.com>, nmalykh@ieee.org, Nabil Bitar <nbitar40@gmail.com>, pals@ietf.org, Loa Andersson <loa@pi.nu>, suresh@kaloom.com, Eric C Rosen <erosen@juniper.net>, terry.manderson@icann.org
References: <20190225140314.77DB0B81C75@rfc-editor.org> <CAA=duU3OSh4akoU50_kat2_A54ix85RnRhtKsrv1jp8oxnBXWA@mail.gmail.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <b7319609-7ebd-0715-42b7-377339841f7c@gmail.com>
Date: Wed, 27 Feb 2019 17:12:07 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <CAA=duU3OSh4akoU50_kat2_A54ix85RnRhtKsrv1jp8oxnBXWA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------C2399025D7820D251608C5D8"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/y7ndSXhm7_iMhTyNpG9ntXAcNwE>
Subject: Re: [Pals] [Editorial Errata Reported] RFC4664 (5644)
X-BeenThere: pals@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Pseudowire And LDP-enabled Services dicussion list." <pals.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pals>, <mailto:pals-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pals/>
List-Post: <mailto:pals@ietf.org>
List-Help: <mailto:pals-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pals>, <mailto:pals-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2019 17:12:14 -0000

Yes, but not for anything beyond editorial, fix in next revision.

No one will make an implementation error and the RFC is nearly 13 years 
and this has not been picked up before.

- Stewart


On 25/02/2019 19:13, Andrew G. Malis wrote:
> I agree with this errata; in addition, I would recommend changing the 
> word "allocate" to "allocating".
>
> Cheers,
> Andy
>
>
> On Mon, Feb 25, 2019 at 9:03 AM RFC Errata System 
> <rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org>> wrote:
>
>     The following errata report has been submitted for RFC4664,
>     "Framework for Layer 2 Virtual Private Networks (L2VPNs)".
>
>     --------------------------------------
>     You may review the report below and at:
>     http://www.rfc-editor.org/errata/eid5644
>
>     --------------------------------------
>     Type: Editorial
>     Reported by: Nikolai Malykh <nmalykh@ieee.org
>     <mailto:nmalykh@ieee.org>>
>
>     Section: 3.4.3
>
>     Original Text
>     -------------
>        Relative to the VPLS there are three different possibilities for
>        allocate functions to a device in such a position in the provider
>        network:
>
>
>     Corrected Text
>     --------------
>        Relative to the VPLS there are two different possibilities for
>        allocate functions to a device in such a position in the provider
>        network:
>
>
>     Notes
>     -----
>
>
>     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.
>
>     --------------------------------------
>     RFC4664 (draft-ietf-l2vpn-l2-framework-05)
>     --------------------------------------
>     Title               : Framework for Layer 2 Virtual Private
>     Networks (L2VPNs)
>     Publication Date    : September 2006
>     Author(s)           : L. Andersson, Ed., E. Rosen, Ed.
>     Category            : INFORMATIONAL
>     Source              : Layer 2 Virtual Private Networks INT
>     Area                : Internet
>     Stream              : IETF
>     Verifying Party     : IESG
>
>
> _______________________________________________
> Pals mailing list
> Pals@ietf.org
> https://www.ietf.org/mailman/listinfo/pals