The MPLS WG Archive

["Thomas D. Nadeau" <tnadeau@cisco.com>]

At 01:40 PM 4/7/2003 -0700, Mike MacFaden wrote:
>On Sat, Apr 05, 2003 at 04:23:12PM +0200, Wijnen, Bert (Bert) wrote:
> >Mike, the problem is that they want to use the TeHopAddressAS
> >in the TeHopAddress objects, and those are of type OCTET STRING,
> >so the one from RFC3291 cannot be used.
> >
> >Maybe 3291bis should also add a OCTET-STRING based AsNumber?
>
>I see. Then I suggest it would be best if all the different
>TCs that represent an AS number (integer, string, ...)
>were in one place with the same semantic definition then
>spread out among various technology specific mib modules.
>
>If that can't be done for whatever reason, then this TC should
>reference the more formal definition in 3291.

         I like the reference option.

         --tom


> >>
> >>   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))
>
>
>Regards
>Mike MacFaden


http://www.elsevier-international.com/catalogue/title.cfm?ISBN=155860751X