Hi Spencer, thank you for reading so carefully the document.
We certainly can expand the EID acronym in the title. We will also go over the document again trying to fix all english nits (BTW thanks for your suggestions). ciao L. > On 15 Feb 2016, at 18:07, Spencer Dawkins <[email protected]> > wrote: > > Spencer Dawkins has entered the following ballot position for > draft-ietf-lisp-eid-block-12: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html > for more information about IESG DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-lisp-eid-block/ > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Could you expand EID as EID Endpoint IDentifier in the document title? > > I'm seeing text that's fairly clear, but could use a native English > speaker pass. For example, > > Transition Mechanism: The existence of a LISP specific EID block may > prove useful in transition scenarios. A non-LISP domain would > ask an allocation in the LISP EID block and use it to deploy > ^^^ "ask for"? or "request"? > LISP in its network. Such allocation will not be announced in > ^^^^ "Such an"? or "This"? > the BGP routing infrastructure (cf., Section 4). This approach > will avoid non-LISP domains to fragment their already allocated > ^^^ "fragmenting previously allocated non-LISP > address > space in non-LISP domains"? > non-LISP addressing space, which may lead to BGP routing table > inflation since it may (rightfully) be announced in the BGP > ^^^^^^^^^^ "correctly"? > routing infrastructure. > > _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
