Hi Doug, Your message to the IAB list was initially put into moderation, but it was sent to the IAB list. In this case, there was about a 20 minute delay between you sending the message, and me releasing it from moderation. The practice on the IAB list is that messages from people who haven't sent to that list before are moderated at first (to reduce spam), but are then added to the whitelist when the message is released from moderation. Your request to subscribe to the IAB list was rejected, because the membership of that list is restricted to the IAB. I apologize if the rejection message from Mailman made that more confusing than it needed to be. That said, anyone can send messages to the IAB list (though their initial message to the list will have to wait for moderation). Best regards, Cindy Cindy Morgan / IAB Executive Administrative Manager 48377 Fremont Blvd., Suite 117 / Fremont CA 94538 T: +1.510.492.4085 / F: +1.510.492.4001 / https://www.iab.org ---------- Managed by Association Management Solutions (AMS); Forum Management, Meeting and Event Planning Website: http://www.amsl.com > On Feb 11, 2016, at 2:10 PM, Doug Royer <douglasroyer@xxxxxxxxx> wrote: > > > iab@xxxxxxx 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@xxxxxxx. > > "...Please send comments to iab@xxxxxxx. 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@xxxxxxx> >> To: "IETF Announcement List" <ietf-announce@xxxxxxxx> > > 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@xxxxxxx. For comments on individual drafts, please include the > relevant document filename in the subject line. > > > -- > > Doug Royer - (http://DougRoyer.US) > DouglasRoyer@xxxxxxxxx > 714-989-6135 >