[bess] [Errata Rejected] RFC7543 (4402)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 15 April 2016 18:43 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F19812E03C; Fri, 15 Apr 2016 11:43:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.898
X-Spam-Level:
X-Spam-Status: No, score=-107.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=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 MWktK1XTItW8; Fri, 15 Apr 2016 11:43:09 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 467EA12DEDA; Fri, 15 Apr 2016 11:43:09 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 369F118000B; Fri, 15 Apr 2016 11:42:50 -0700 (PDT)
To: rbonica@juniper.net, hj2387@att.com, luay.jalil@verizon.com, rbonica@juniper.net, keyupate@cisco.com, lucy.yong@huawei.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20160415184250.369F118000B@rfc-editor.org>
Date: Fri, 15 Apr 2016 11:42:50 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/bess/UgP-OJRdfW1Cu07TW2IqnbKw5W4>
X-Mailman-Approved-At: Fri, 15 Apr 2016 11:44:37 -0700
Cc: aretana@cisco.com, iesg@ietf.org, bess@ietf.org, rfc-editor@rfc-editor.org
Subject: [bess] [Errata Rejected] RFC7543 (4402)
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Apr 2016 18:43:11 -0000
The following errata report has been rejected for RFC7543, "Covering Prefixes Outbound Route Filter for BGP-4". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=7543&eid=4402 -------------------------------------- Status: Rejected Type: Technical Reported by: Ron Bonica <rbonica@juniper.net> Date Reported: 2015-06-26 Rejected by: Alvaro Retana (IESG) Section: 7 Original Text ------------- +------------------------------------------------+---------------+ | Registry | Code Point | +------------------------------------------------+---------------+ | BGP Outbound Route Filtering (ORF) Types | CP-ORF (65) | | Transitive Opaque Extended Community Sub-Types | CP-ORF (0x03) | +------------------------------------------------+---------------+ Corrected Text -------------- +------------------------------------------------+---------------+ | Registry | Code Point | +------------------------------------------------+---------------+ | BGP Outbound Route Filtering (ORF) Types | CP-ORF (65) | | Transitive Opaque Extended Community Sub-Types | CP-ORF (0x03) | | Capability Codes | CP-ORF (72) | +------------------------------------------------+---------------+ Notes ----- In the original text, we forgot to mention the value of the BGP capability code. --VERIFIER NOTES-- RFC 5291 describes The Outbound Route Filter (ORF) Capability for BGP. According to RFC 5291, when two BGP speakers initiate a session between one another and they intend to exchange ORFs of any type, they must advertise the ORF capability. The ORF capability is registered with a value of 3 in the IANA BGP Capability Code Registry. The ORF capability also includes a list of ORF types that the BGP speaker can send and/or receive. IANA also maintains a BGP Outbound Route Filtering (ORF) Types registry. RFC 7543 describes a new ORF type, called the Covering Prefix ORF (CP-ORF). RFC 7543 should conform to generic ORF procedures defined in RFC 5291. Specifically, when two BGP speakers initiate a session between one another and they intend to exchange CP-ORFs, they must advertise the ORF capability (value 3). The ORF capability must include CP-ORF (value 65) in the ORF type list. -------------------------------------- RFC7543 (draft-ietf-bess-orf-covering-prefixes-06) -------------------------------------- Title : Covering Prefixes Outbound Route Filter for BGP-4 Publication Date : May 2015 Author(s) : H. Jeng, L. Jalil, R. Bonica, K. Patel, L. Yong Category : PROPOSED STANDARD Source : BGP Enabled Services Area : Routing Stream : IETF Verifying Party : IESG
- [bess] [Technical Errata Reported] RFC7543 (4402) RFC Errata System
- [bess] [Errata Verified] RFC7543 (4402) RFC Errata System
- [bess] [Errata Rejected] RFC7543 (4402) RFC Errata System