Re: [OSPF] Poll for WG Adoption of "draft-acee-ospfv3-lsa-extend"

    I strongly support this work.
    IMO we need the same work to be done with OSPFv2. Shall it be part 
of this document or work on its own is a separate question.
    Number of I-Ds submitted against OSPFv2 shows that this version of 
the protocol is still being actively worked on and in medium term many 
extensions will have to be simultaneously proposed for v2 and v3. Having 
Extendable LSAs in both protocol versions would greatly simplify 
standardization and development of such extensions.

    I have a few notes on current draft but I do not want to hijack this 
thread for technical discussion and better send another email.

Thanks,

Anton


On 09/16/2013 02:24 PM, Acee Lindem wrote:
> This version includes changes in support of backward compatibility. Speaking as both a WG chair and author, this document is essential to OSPFv3 protocol extension. Please indicate your support or objections by September 30th, 2013.
> Thanks,
> Acee
>
> On Sep 10, 2013, at 5:54 PM, <internet-drafts@ietf.org>
>   <internet-drafts@ietf.org> wrote:
>
>> A new version of I-D, draft-acee-ospfv3-lsa-extend-02.txt
>> has been successfully submitted by Acee Lindem and posted to the
>> IETF repository.
>>
>> Filename:	 draft-acee-ospfv3-lsa-extend
>> Revision:	 02
>> Title:		 OSPFv3 LSA Extendibility
>> Creation date:	 2013-09-10
>> Group:		 Individual Submission
>> Number of pages: 29
>> URL:             http://www.ietf.org/internet-drafts/draft-acee-ospfv3-lsa-extend-02.txt
>> Status:          http://datatracker.ietf.org/doc/draft-acee-ospfv3-lsa-extend
>> Htmlized:        http://tools.ietf.org/html/draft-acee-ospfv3-lsa-extend-02
>> Diff:            http://www.ietf.org/rfcdiff?url2=draft-acee-ospfv3-lsa-extend-02
>>
>> Abstract:
>>    OSPFv3 requires functional extension beyond what can readily be done
>>    with the fixed-format Link State Advertisement (LSA) as described in
>>    RFC 5340.  Without LSA extension, attributes associated with OSPFv3
>>    links and advertised IPv6 prefixes must be advertised in separate
>>    LSAs and correlated to the fixed-format LSA.  This document extends
>>    the LSA format by allowing the optional inclusion of Type-Length-
>>    Value (TLV) tuples in the LSAs.  Backward compatibility mechanisms
>>    are also described.
>>
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
>>
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf