Hi, Acee, and thanks for the response. >>-- Section 2 -- >>There is no explanation of the "length" field in the OSPFv2 Extended >>Prefix Opaque LSA. I guess it's the total size, in bytes, of all the TLV >>data that follows, including any alignment bytes. But you should make >>that clear. > > The LSA header length, as defined in RFC 2328, is pretty standard. > However, this can be succinctly clarified. How about? > > The LSA “Length” field [RFC2328] represents the total length (in octets) > of the Opaque LSA including the LSA header and all TLVs (including > padding).
That sounds good to me. And if you really think it's sufficiently well known already as not to need that, I'm OK with it as it is. Thanks for considering the comment. >>A question here (I'm not hoping for any particular answer, just asking >>the question): When you say "an IETF specification", I take that to mean >>an RFC in the IETF stream, which can be Standards Track *or* >>Informational *or* Experimental. Is that what you want? > > Yes. I’d like to leave this open. I’d hope we’d do the right thing when > the time comes to assign this space. OK; quite fine. Carry on.... Barry _______________________________________________ OSPF mailing list OSPF@ietf.org https://www.ietf.org/mailman/listinfo/ospf
