The MPLS WG Archive

[Mike MacFaden <mrm@riverstonenet.com>]

On Thu, Apr 03, 2003 at 11:05:52AM -0500, Thomas D. Nadeau wrote:
>>6) TeHopAddressAS will most likely be a duplicate of
>>whatever Jeffrey Haas does on the updates to the BGP mib modules.
>>Should probably consult on this before we end up with TWO TCs
>>that can be used to represent a 2 or 4 byte ASN.
>
>         The current state of these objects were as strongly
>suggested by Bert and after numerous iterations including
>the review from Atlanta. I hesitate to change them further unless
>there is a serious flaw that you can identify. On the issue of
>consistency with the BGP TCs, if the BGP guys want to reference
>our TC,  then that is cool but we are not in a position at this
>point to wait around to see what they want to do before we
>change these TCs.

The new BGP MIB module draft-ietf-idr-bgp4-mibv2-03.txt uses
the following TC from *RFC 3291* 

InetAutonomousSystemNumber ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "Represents an autonomous system number which identifies an
         Autonomous System (AS). An AS is a set of routers under a
         single technical administration, using an interior gateway
         protocol and common metrics to route packets within the AS,
         and using an exterior gateway protocol to route packets to
         other ASs'. IANA maintains the AS number space and has
         delegated large parts to the regional registries.
 
         Autonomous system numbers are currently limited to 16 bits
         (0..65535). There is however work in progress to enlarge the
         autonomous system number space to 32 bits. This textual
         convention therefore uses an Unsigned32 value without a
         range restriction in order to support a larger autonomous
         system number space."
    REFERENCE  "RFC 1771, RFC 1930"
    SYNTAX      Unsigned32
 

versus

  TeHopAddressAS ::= TEXTUAL-CONVENTION
             STATUS      current
             DESCRIPTION
                "Represents a two or four octet AS number.
                 The AS number is represented in network byte
                 order (MSB first).  A two-octet AS number has
                 the two MSB octets set to zero."
             SYNTAX      OCTET STRING (SIZE (4))
 

I contend you can remove TeHopAddressAS. 

InetAutonomousSystemNumber
a) Is much better described 
b) Is easily imported from an existing RFC (bgp mib modules use it)

Thanks,
Mike MacFaden