Re: [forces] [Editorial Errata Reported] RFC5812 (5656)

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 13 March 2019 21:35 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: forces@ietfa.amsl.com
Delivered-To: forces@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDF0913120E for <forces@ietfa.amsl.com>; Wed, 13 Mar 2019 14:35:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 I_gygw_R_3Og for <forces@ietfa.amsl.com>; Wed, 13 Mar 2019 14:34:59 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6278713120D for <forces@ietf.org>; Wed, 13 Mar 2019 14:34:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 44KQ9H0dD3zQmYM; Wed, 13 Mar 2019 14:34:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1552512899; bh=L9EddF2JWsemFYdSXGmVMjv0qLnkZi8vC4llkKq6YeU=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=WVU/BI6iP7hiAGQqgyDjxSRUoWQOyOtQPQg8BgR9xIPHCGNWQMShmXgCWKkMfYXRU Es558RH2Bm4HaV4oBGFXhnPiOjQRKIrTHp4BiTMCbEM6wXgaq6gNScgcEqhvdKIpKr QtD9nrgCPxU5gLazqT+3B5RJtFHNib/mg4NfS7MM=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 44KQ9F6FlyzQmYF; Wed, 13 Mar 2019 14:34:57 -0700 (PDT)
To: RFC Errata System <rfc-editor@rfc-editor.org>, hadi@mojatatu.com, db3546@att.com, aretana.ietf@gmail.com, martin.vigoureux@nokia.com, damascene.joachimpillai@verizon.com
Cc: nmalykh@ieee.org, forces@ietf.org
References: <20190313212612.2DC73B80DBB@rfc-editor.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <12d6c203-e44f-4a88-8936-fd21c12d6931@joelhalpern.com>
Date: Wed, 13 Mar 2019 17:34:56 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.5.3
MIME-Version: 1.0
In-Reply-To: <20190313212612.2DC73B80DBB@rfc-editor.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/forces/P4PtAlybM7OG44IrkPPVv-lO7J8>
Subject: Re: [forces] [Editorial Errata Reported] RFC5812 (5656)
X-BeenThere: forces@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: ForCES WG mailing list <forces.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/forces>, <mailto:forces-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/forces/>
List-Post: <mailto:forces@ietf.org>
List-Help: <mailto:forces-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/forces>, <mailto:forces-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2019 21:35:08 -0000

Oops.  Looks like he is correct.
Yours,
Joel

On 3/13/19 5:26 PM, RFC Errata System wrote:
> The following errata report has been submitted for RFC5812,
> "Forwarding and Control Element Separation (ForCES) Forwarding Element Model".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata/eid5656
> 
> --------------------------------------
> Type: Editorial
> Reported by: Nikolai Malykh <nmalykh@ieee.org>
> 
> Section: 4.8.6
> 
> Original Text
> -------------
>                  <synopsis>
>                    the path to the component target
>                    each 4 octets is read as one path element,
>                    using the path construction in the ForCES protocol,
>                    [2].
>                  </synopsis>
> 
> 
> Corrected Text
> --------------
>                  <synopsis>
>                    the path to the component target
>                    each 4 octets is read as one path element,
>                    using the path construction in the ForCES protocol,
>                    [RFC5810].
>                  </synopsis>
> 
> 
> Notes
> -----
> Incorrect reference
> 
> 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.
> 
> --------------------------------------
> RFC5812 (draft-ietf-forces-model-16)
> --------------------------------------
> Title               : Forwarding and Control Element Separation (ForCES) Forwarding Element Model
> Publication Date    : March 2010
> Author(s)           : J. Halpern, J. Hadi Salim
> Category            : PROPOSED STANDARD
> Source              : Forwarding and Control Element Separation
> Area                : Routing
> Stream              : IETF
> Verifying Party     : IESG
>