Re: comments on draft-ietf-l3vpn-ppvpn-mcast-reqts-03

[Thomas Morin <thomas.morin at rd.francetelecom.com>]

Hi folks,

Pekka Savola:
> >> Appendix A.  Requirements summary
> >>
> >> ==> I'd consider removing this, because these should be extractable from the
> >> body of the document, and these could get out of date easily if the editors
> >> are not really, really careful.  Recent xml2rfc includes support for some
> >> degree of autogeneration of these using xref format=title  (see RFC 3871 appendix A for
> >> example)
> >
> 
> > Well, this was suggested by a reviewer, and I think it can be useful.
> > I am open to other inputs, it is true that is requires particular
> > care... its somehow a matter of benefit/risk trade-off.
> >
> > (the feature you quote is interesting indeed, but looks only useful with
> > one requirement item per sub-section, and subsection title chosen to
> > match there use in the resulting summary...)
> 
> I'm OK with leaving it in if that's what the WG thinks is appropriate. 
> However, the document is already pretty long, and any means to reduce 
> the length should be considered.

Anyone opinion on this is welcome...
I can live without the burden of updating this "Requirements summary"
section, but I would also understand if people that find it useful ask
for keeping it: raise your voice if you are one of them.

-Thomas