Re: [Teas] inclusion of references in protocol feature configuration configuration

FWIW, this used to show up as an issue in MIB modules as well. A Description
clause or a Reference clause would mention another document (such as an RFC) but
would not include it as a square bracket reference (because, importantly, the
module may be extracted as a standalone thing and so can't have a citation style
reference). That meant that some documents that are important are not properly
referenced.

The way we solved this in MIB modules was to include a short note in the text
immediately before the module saying "The module that follows makes reference to
the following documents: [ref1], [ref2], ..."

Adrian

> -----Original Message-----
> From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Lou Berger
> Sent: 10 November 2017 15:29
> To: draft-ietf-teas-yang-rsvp-te@ietf.org; draft-ietf-teas-yang-rsvp@ietf.org;
> draft-ietf-teas-yang-te@ietf.org
> Cc: teas@ietf.org
> Subject: [Teas] inclusion of references in protocol feature configuration
> configuration
> 
> Hi,
> 	In reviewing the the yang-te, rsvp and rsvp=te modules I noticed that
> references aren't included in most config groupings/nodes.  Given the
> number of RFCs used to define the mechanisms covered by these modules I
> think it's important to include a reference to the RFC that defines the
> feature/information element covered in the model. I suspect this
> comments is also applicable to other modules.
> 
> Thanks,
> Lou
> 
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas