Vendor attributes in TE LSAs

Udo Neustadter <neustadter@TROPICNETWORKS.COM> Tue, 27 May 2003 13:29 UTC

Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11022 for <ospf-archive@LISTS.IETF.ORG>; Tue, 27 May 2003 09:29:31 -0400 (EDT)
Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <13.009E64B9@cherry.ease.lsoft.com>; Tue, 27 May 2003 9:29:31 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 43797562 for OSPF@PEACH.EASE.LSOFT.COM; Tue, 27 May 2003 09:29:30 -0400
Received: from 209.119.0.100 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Tue, 27 May 2003 09:19:30 -0400
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <22.009E65D6@cherry.ease.lsoft.com>; Tue, 27 May 2003 9:19:29 -0400
Received: from 209.202.99.50 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Tue, 27 May 2003 09:19:29 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Thread-Topic: Vendor attributes in TE LSAs
Thread-Index: AcMkUpoR9ApzCbnqScOXd84yz5YGfA==
Message-ID: <83040F98B407E6428FEC18AC720F5D73200F09@exchange.tropicnetworks.com>
Date: Tue, 27 May 2003 09:19:28 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Udo Neustadter <neustadter@TROPICNETWORKS.COM>
Subject: Vendor attributes in TE LSAs
Comments: To: ospf@discuss.microsoft.com
Comments: cc: ccamp@ops.ietf.org
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA11022

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