[Idr] [Errata Held for Document Update] RFC6793 (4538)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 23 November 2015 18:58 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8BEE1ACDD6; Mon, 23 Nov 2015 10:58:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.487
X-Spam-Level:
X-Spam-Status: No, score=-107.487 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 LxFIcFbq475b; Mon, 23 Nov 2015 10:58:15 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 639431ACDC1; Mon, 23 Nov 2015 10:58:15 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 24D9918000D; Mon, 23 Nov 2015 10:56:41 -0800 (PST)
To: warren@kumari.net, quaizar.vohra@gmail.com, enkechen@cisco.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20151123185641.24D9918000D@rfc-editor.org>
Date: Mon, 23 Nov 2015 10:56:41 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/3h20GR6Bqdc1rmW7_BX0MPYy8Ik>
Cc: rfc-editor@rfc-editor.org, iesg@ietf.org, idr@ietf.org
Subject: [Idr] [Errata Held for Document Update] RFC6793 (4538)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Nov 2015 18:58:17 -0000

The following errata report has been held for document update 
for RFC6793, "BGP Support for Four-Octet Autonomous System (AS) Number Space". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6793&eid=4538

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Warren Kumari <warren@kumari.net>
Date Reported: 2015-11-19
Held by: Alvaro Retana (IESG)

Section: 8

Original Text
-------------
If the BGP4-MIB [RFC4273] is supported, there are no additional
manageability concerns that arise from the use of four-octet AS
numbers, since the InetAutonomousSystemNumber textual convention
[RFC4001] is defined as Unsigned32.

Corrected Text
--------------
If the BGP4-MIBv2 [draft-ietf-idr-bgp4-mibv2] is supported, there are 
no additional manageability concerns that arise from the use of 
four-octet AS numbers, since the InetAutonomousSystemNumber 
textual convention [RFC4001] is defined as Unsigned32.

Notes
-----
I do not have corrected text. RFC4273 does not use InetAutonomousSystemNumber for AS numbers:
bgpPeerRemoteAs OBJECT-TYPE
            SYNTAX     Integer32 (0..65535)
            MAX-ACCESS read-only
            STATUS     current
            DESCRIPTION
                    \\\\\\\\\\\\\\\\"The remote autonomous system number received in
                     the BGP OPEN message.\\\\\\\\\\\\\\\\"
            REFERENCE
                    \\\\\\\\\\\\\\\\"RFC 4271, Section 4.2.\\\\\\\\\\\\\\\\"
            ::= { bgpPeerEntry 9 }

This uses \\\\\\\\\\\\\\\\"Integer32 (0...65535)\\\\\\\\\\\\\\\\" (note, Integer, not Unsigned Int). 
It is unclear to me how to fix this, I know some folk are simply treating it as a UInt32.

=====
The report is correct, rfc4273 can\\'t support 4-byte ASNs.

After consulting with the authors and the WG, it seems like the correct reference should have been 
draft-ietf-idr-bgp4-mibv2 (BGP4 MIBv2).   Besides the corrected text above, an Informative Reference should be added to draft-ietf-idr-bgp4-mibv2.

--------------------------------------
RFC6793 (draft-ietf-idr-rfc4893bis-07)
--------------------------------------
Title               : BGP Support for Four-Octet Autonomous System (AS) Number Space
Publication Date    : December 2012
Author(s)           : Q. Vohra, E. Chen
Category            : PROPOSED STANDARD
Source              : Inter-Domain Routing
Area                : Routing
Stream              : IETF
Verifying Party     : IESG