RE: Proposed IESG statement on referencing documents behind a paywall

["Black, David" <[e-mail]>]

+1 - I vaguely recall doing something similar to what Suresh did on IEEE 1588 for some storage standards needed by iSCSI, FCIP and the like back when I was a chair of the IP Storage working group.

This paywall reference situation seems somewhat analogous to downrefs, and hence the proposed measures strike me as reasonable.

Thanks, --David

> -----Original Message-----
> From: WGChairs <[e-mail]> On Behalf Of Stewart Bryant
> Sent: Friday, June 14, 2019 7:13 AM
> To: Suresh Krishnan; [e-mail]
> Subject: Re: Proposed IESG statement on referencing documents behind a
> paywall
> 
> 
> [EXTERNAL EMAIL]
> 
> 
> 
> On 12/06/2019 23:00, Suresh Krishnan wrote:
> > *** START TEXT ***
> >
> > As described in Section 7.1 of RFC 2026, RFCs may have normative
> > references on external standards.
> >
> > In some cases, however, those references are themselves not generally
> > available (for instance, they might be accessible only after paying
> > a fee). This can interfere both with the ability of implementers
> > to implement the protocol as well as with the ability of the IETF
> > community to review it.
> >
> > In such cases:
> >
> > 1. The WG MUST be explicitly informed of any such normative reference
> >   and the WG MUST reach consensus that it is acceptable. The
> >   document shepherd MUST include this information in the shepherd
> >   writeup.
> >
> > 2. The reference MUST be explicitly noted as part of the IETF Last
> >   Call. If such a note is omitted, the last call MUST be repeated
> >   after including it.
> 
> 3. Where the reference has been made available to the WG for the
> purposes of their work, this fact, together with details of how
> reviewers can gain access to the reference for the purposes of their
> review MUST also be provided as part of IETF Last Call.
> 
> - Stewart
> 
> 
> >
> > *** END TEXT ***