[Idr] [Technical Errata Reported] RFC6793 (4538)

[RFC Errata System <[e-mail]>]

The following errata report has been submitted 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

--------------------------------------
Type: Technical
Reported by: Warren Kumari <[e-mail]>

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
--------------


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.

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. 

--------------------------------------
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