Loa, One small nit with your review - renaming a draft because the WG name changed resets the numbering to -00, so the next revision will be draft-ietf-bess-virtual-subnet-00. However, the replaced-by information in the datatracker will make the progression clear.
Cheers, Andy On Sat, May 23, 2015 at 7:52 AM, Loa Andersson <[email protected]> wrote: > Authors, wg and chairs, > > I've read this document and think it is useful, and that we are almost > ready to request publication. > > A couple of nits > > 0. The nits tool gives errors on 54 lines that are too long > > 1. The file name is still draft-ietf-l3vpn-virtual-subnet-03, while > updating after wglc is should be posted as draft-ietf-bess-virtual- > subnet-03. > > 2. The document has 7 authors, please make sure that all of them meets > the criterium that the RFC Editor sent out some weeks ago. > > "The intent of the author list in the document header and the Authors > Addresses space in an RFC is to indicate who is responsible for the > technical content of the document." > > 3. Does "across" in the abstract mean "within" or "between"? > > 4. The concept "L3VPN-based" is used at a number of places ... > > 5. The nits tool give warnings of "26 instances of lines with > non-RFC5735-compliant IPv4 addresses". > > 6. First paragraph on page 12 says "both ingress and egress PE routers > MUST NOT decrement the TTL", > The meaning is unclear, can one of them do it or neither? > > 7. Do we need to consider IPv6? > > Other than this I think this very useful document is ready to be > progressed. > > /Loa > > > -- > > > Loa Andersson email: [email protected] > Senior MPLS Expert [email protected] > Huawei Technologies (consultant) phone: +46 739 81 21 64 > > _______________________________________________ > BESS mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/bess >
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
