Re: Vendor attributes in TE LSAs

["Manral, Vishwas" <[e-mail]>]

Hi Udo,

The draft looks pretty straight forward and simple.

A similar draft exists in IS-IS
http://www.ietf.org/internet-drafts/draft-ietf-isis-experimental-tlv-00.txt
, and instead of "SMI Network management enterprise code for the vendor or
organization" uses "a valid IEEE assigned OUI as the first three bytes of
the value of the TLV."

I do not know the tradeoffs but if possible we could use the same value too.
Maybe someone could point out the tradeoffs if any.

Besides I guess Section 5(if the same mechanism is used in TLV's) and
Section 6 of the ISIS draft wold be valid here too.

Thanks,
Vishwas

-----Original Message-----
From: Udo Neustadter [mailto:[e-mail]]
Sent: Tuesday, May 27, 2003 6:49 PM
To: [e-mail]
Subject: Vendor attributes in TE LSAs


Hi all,

I am working on a GMPLS implementation, and part of my problem is the
addition of company specific data to the TE LSAs. The Internet-Draft
http://www.ietf.org/internet-drafts/draft-udo-ospf-vendatt-00.txt
proposes an interoperable way to solve the following two issues:
  1. Companies that already applied with IANA for an SMI Network
management enterprise code do not need to re-apply for sub-TLV values
from the pool of numbers reserved for private use
  2. Allows private attributes/data to be embedded in the TE router LSA
(the one TE LSA that contains the router address TLV).

I would like for the draft to be considered part of this working group.
This work is an extension to the work done in
http://www.ietf.org/internet-drafts/draft-katz-yeung-ospf-traffic-09.txt
and
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-ospf-gmpls-extensio
ns-09.txt.

Thanks in advance for your support.

Udo