Re: Vendor attributes in TE LSAs - (Sent first reply prematurely)
Acee Lindem <acee@REDBACK.COM> Wed, 28 May 2003 18:08 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 OAA14248 for <ospf-archive@LISTS.IETF.ORG>; Wed, 28 May 2003 14:08:45 -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 <1.009E9FF9@cherry.ease.lsoft.com>; Wed, 28 May 2003 14:08:44 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 43955123 for OSPF@PEACH.EASE.LSOFT.COM; Wed, 28 May 2003 14:08:42 -0400
Received: from 24.93.67.82 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Wed, 28 May 2003 14:08:32 -0400
Received: from redback.com (rdu26-55-006.nc.rr.com [66.26.55.6]) by ms-smtp-01.southeast.rr.com (8.12.5/8.12.2) with ESMTP id h4SI3Esb012021 for <OSPF@PEACH.EASE.LSOFT.COM>; Wed, 28 May 2003 14:03:14 -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: <E7E13AAF2F3ED41197C100508BD6A328DD4343@india_exch.corp.mot.com> <3ED4BAF6.3000804@redback.com> <3ED4C31B.3040007@xebeo.com> <3ED4C640.5010704@redback.com> <3ED4E06B.9060008@xebeo.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID: <3ED4FAB6.3080600@redback.com>
Date: Wed, 28 May 2003 14:06:46 -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 - (Sent first reply prematurely)
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit
Tony Przygienda wrote: > Acee Lindem wrote: > > >>Tony Przygienda wrote: >> >> >>>Acee Lindem wrote: >>> >>> >>> >>>>isn't any) 2) Scalability (LSA contents, size, and refresh frequency >>>>are >>>>unknown) and 3) Deployment - Debugging a multi-vendor network with many >>>>different vendor specific LSAs will be difficult. >>> >>> >>> >>>ok, but then from experience, they will _just_ take the TLVs they need >>>without >>>letting you know. Suit yourself ;-) >> >> >>Maybe so - but at least this activity won't be sanctioned by the OSPF WG. > > > this is just a semantic or maybe semiotic split-of-hairs IMHO. OSPF-WG > or any > other WG-approval is not a consumer brand and does nothing for the vendor, > espeically if he's pursuiting a proprietary value-add-on in the protocol. > > >> >>Perhaps the IANA allocation of TLVs and Sub-TLVs needs to be at the front >>end of the process rather than the backend. > > > yes, but is easier for vendors to grab an 'experimental' OUI (which is a > no-time-involved > process) and once they figured > out what it does for them and care about interoperability, ask for an > 'official' sub-TLV. > It will be a well-understood process by both vendors AND their > customers. Customers > will understand that an 'experimental' gives them no guarantee as to > itneroperability as > Ran very clearly formulated and has been put down in the > isis-experimental draft. > Otherwise they'll ask you for a sub-TLV or probaly not even that (since > it needs time, so > they > just grab any number that looks free) > and of course not tell you what it does. Difference against just > semantical IMHO > and in terms of > reality the output is the same I'd be prefer an experimental range of TLVs that are allocated from IANA for specific experimental purposes rather than a single TLV giving carte blanche to advertise anything in OSPF. I'm less cynical that the output will be the same. Hopefully, if an experimental TE application is commerically viable it will evolve into a standard. > > thanks > > -- tony > -- Acee
- Re: Vendor attributes in TE LSAs - (Sent first re… Acee Lindem
- Re: Vendor attributes in TE LSAs - (Sent first re… Manral, Vishwas
- Re: Vendor attributes in TE LSAs - (Sent first re… Acee Lindem
- Re: Vendor attributes in TE LSAs - (Sent first re… Jeff Parker
- Re: Vendor attributes in TE LSAs - (Sent first re… Tony Przygienda
- Re: Vendor attributes in TE LSAs - (Sent first re… Acee Lindem
- Re: Vendor attributes in TE LSAs - (Sent first re… Tony Przygienda
- Re: Vendor attributes in TE LSAs - (Sent first re… Acee Lindem