The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2003-Apr> msg00093



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

Last Call MPLS-TC-MIB #6

  • From: Mike MacFaden <mrm@riverstonenet.com>
  • Date: Mon, 7 Apr 2003 13:40:33 -0700
  • Cc: "Thomas D. Nadeau" <tnadeau@cisco.com>, jcucchiara@artel.com, cheenu@paramanet.com, arun@force10networks.com, hans@ipunplugged.com, kireeti@juniper.net, mpls@UU.NET
  • User-Agent: Mutt/1.2.5i

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. 

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