Re: Vendor attributes in TE LSAs

Acee Lindem <acee@REDBACK.COM> Wed, 28 May 2003 04:20 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 AAA18883 for <ospf-archive@LISTS.IETF.ORG>; Wed, 28 May 2003 00:20:40 -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 <8.009E806D@cherry.ease.lsoft.com>; Wed, 28 May 2003 0:20:41 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 43895296 for OSPF@PEACH.EASE.LSOFT.COM; Wed, 28 May 2003 00:20:38 -0400
Received: from 24.93.67.82 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Wed, 28 May 2003 00:20:38 -0400
Received: from redback.com (rdu162-235-058.nc.rr.com [24.162.235.58]) by ms-smtp-01.southeast.rr.com (8.12.5/8.12.2) with ESMTP id h4S4FNsb026636 for <OSPF@PEACH.EASE.LSOFT.COM>; Wed, 28 May 2003 00:15:23 -0400 (EDT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <83040F98B407E6428FEC18AC720F5D73200F09@exchange.tropicnetworks.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID: <3ED438B5.1070000@redback.com>
Date: Wed, 28 May 2003 00:19:01 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: Vendor attributes in TE LSAs
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Udo,

I don't support this enhancement since it essentially removes any


Udo Neustadter wrote:
> 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
>


--
Acee