Subject: Minor Update to the MPLS-TC-STD-MIB, draft-ietf-mpls-tc-mib-09b.t xt is attached.

From: Joan Cucchiara x302 <[email-masked]>
Date: Fri, 17 Oct 2003 09:55:39 -0400

Hi Folks,

Co-authors have discussed the IESG comments 
off-line a bit, and this is how we answered them.

DESCRIPTION Clauses for 
TeHopAddressType and TeHopAddress TCs have been updated.

Diff between version 9 and 9b for the TeHopAddressType:
=======================================================
816c816
<                  lspid(5)     An LSP ID for CR-LDP Tunnels
---
>                  lspid(5)     An LSP ID for TE Tunnels
836,838c836,839
<                  if an attempt to change a TeHopAddressType object
<                  would, for example, lead to an undefined
<                  TeHopAddress value.  In particular,
---
>                  if an attempt to change a TeHopAddressType
>                  object would, for example, lead to an
>                  undefined TeHopAddress value that is
>                  not defined herein.  In particular,
840,842c841,842
<                  must be changed together if the address type
<                  changes (e.g. from ipv6(2) to ipv4(1))."
<              REFERENCE
---
>                  must be changed together if the address
>                  type changes (e.g. from ipv6(2) to ipv4(1))."
845c845

Diff between version 9 and 9b for the TeHopAddress:
=====================================================
869c870,886
<                 "Denotes a generic Tunnel hop address.
---
>                 "Denotes a generic Tunnel hop address,
>                  that is, the address of a node which
>                  an LSP traverses, including the source
>                  and destination nodes.  An address may be
>                  very concrete, for example, an IPv4 host
>                  address (i.e., with prefix length 32);
>                  if this IPv4 address is an interface
>                  address, then that particular interface
>                  must be traversed.  An address may also
>                  specify an 'abstract node', for example,
>                  an IPv4 address with prefix length
>                  less than 32, in which case, the LSP
>                  can traverse any node whose address
>                  falls in that range.  An address may
>                  also specify an Autonomous System (AS),
>                  in which  case the LSP can traverse any
>                  node that falls within that AS.

Please email comments to the list for these changes only.

   thanks,
    Joan