Re: [IAB] IAB(_at_)iab(_dot_)org mailing list closed, yet asks for comme

Your note came though just fine on the IAB mail list.  Perhaps you also CCed or 
BCCed a list restricted posting rights.

Russ


On Feb 11, 2016, at 5:10 PM, Doug Royer wrote:

> iab(_at_)iab(_dot_)org is a closed list for members only. So why are they 
> asking
> for comments on IETF lists?
>
> Its a bit confusing, a post to the ietf-announce mailing list called for
> comments to be sent to: iab(_at_)iab(_dot_)org.
>
> "...Please send comments to iab(_at_)iab(_dot_)org. For comments on individual
>   drafts, please include the relevant document filename in the subject
>   line. ...."
>
> What's the point of the request if we can't participate in the
> discussion or know if their are points to reply to?
>
>
> (Copy of original email below...)
>
> > From: IAB Executive Administrative Manager <execd(_at_)iab(_dot_)org>
> > To: "IETF Announcement List" <ietf-announce(_at_)ietf(_dot_)org>
> This is an announcement of an IETF-wide Call for Comment on
> the RFC Format Drafts. These documents are being considered for
> publication as Informational RFCs within the IAB stream.  The suggested
> reading order is:
>
> 1. The big picture
>
> - - - Flanagan, H., "RFC Format Framework",
>   http://datatracker.ietf.org/doc/draft-iab-rfc-framework/
>
> 2. The underlying vocabulary
>
> - - - Hoffman, P., "The 'XML2RFC' version 3 Vocabulary",
>    https://datatracker.ietf.org/doc/draft-iab-xml2rfc/
>
> 3. The outputs
>
> - - - Hildebrand, J. and P. Hoffman, "HyperText Markup
>   Language Request For Comments Format”,
>   https://datatracker.ietf.org/doc/draft-iab-html-rfc/
>
> - - - Flanagan, H., "Requirements for Plain Text RFCs",
>   https://datatracker.ietf.org/doc/draft-iab-rfc-plaintext/
>
> - - - Hansen, T., Masinter, L., and M. Hardy, "PDF for
>   an RFC Series Output Document Format”,
>   https://datatracker.ietf.org/doc/draft-iab-rfc-use-of-pdf/
>
> - - - Brownlee, N., "SVG Drawings for RFCs: SVG 1.2 RFC",
>   https://datatracker.ietf.org/doc/draft-iab-svg-rfc/
>
> 4. Generalized requirements
>
> - - - Flanagan, H., "The Use of Non-ASCII Characters in RFCs",
>   https://www.ietf.org/id/draft-iab-rfc-nonascii-00.pdf
>
> - - - Flanagan, H., “CSS Requirements for RFCs”,
>   https://datatracker.ietf.org/doc/draft-iab-rfc-css/
>
> 5. Workflow and tools (note that the examples draft will
>   not become an RFC, but is necessary for the project)
>
> - - - Hildebrand, J. and P. Hoffman, "RFC v3 Prep Tool Description",
>   https://datatracker.ietf.org/doc/draft-iab-rfcv3-preptool/
>
> - - - Hoffman, P. and T. Hansen, "Examples of the ‘XML2RFC'
>   Version 2 and 3 Vocabularies”,
>   http://datatracker.ietf.org/doc/draft-hoffman-rfcexamples/
>
> 6. The Statements of Work
>
> - - - http://www.nostrum.com/~rjsparks/rfced/
>
> The Call for Comment will last until 2016-03-10. Please send comments to
> iab(_at_)iab(_dot_)org. For comments on individual drafts, please include the
> relevant document filename in the subject line.
>
>
> -- 
>
> Doug Royer - (http://DougRoyer.US)
> DouglasRoyer(_at_)gmail(_dot_)com
> 714-989-6135