Ok, then I´ll add a sentence in the Introduction section pointing to the Definitions of Terms of RFC6830
Albert On Thu, Oct 2, 2014 at 2:03 AM, Joel M. Halpern <[email protected]> wrote: > While it is not a strict rule, it is usually better to point to a definition > rather than copy it, and much better to point to it rather than to copy and > modify it. > > Yours, > Joel > > > On 10/1/14, 7:48 PM, Albert Cabellos wrote: >> >> Hi Fabio >> >> Thanks for your comments, please find below our answers: >> >> On Fri, Sep 26, 2014 at 2:28 AM, Fabio Maino <[email protected]> >> wrote: >>> >>> >>> Albert, Damien, this is a very good document, that I think fits >>> very well with the charter requirements. I like that you keep it >>> short, dry, and to the point. >>> >>> From a structure perspective, I don't see a Definition of Terms >>> section. Maybe you could point to RFC6830 definitions, or copy >>> those needed in this document (XEID is possibly the only term that >>> is not already in RFC6830 glossary). I like that you didn't use new >>> terminology. >>> >> >> Find below a proposed "Definitions of Terms", We have used a >> simplified version of RFC6830,RFC6832,RFC6833 definitions, we don´t >> need so much detail and this way the text is lighter and easier to >> understand: _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
