Re: [IAB] IAB@iab.org mailing list closed, yet asks for comments?

Russ Housley <housley@vigilsec.com> Thu, 11 February 2016 22:30 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDF691B3B88 for <ietf@ietfa.amsl.com>; Thu, 11 Feb 2016 14:30:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SgcrwAZf7u-E for <ietf@ietfa.amsl.com>; Thu, 11 Feb 2016 14:30:43 -0800 (PST)
Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id 522831B3B84 for <ietf@ietf.org>; Thu, 11 Feb 2016 14:30:43 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 7C6079A400C; Thu, 11 Feb 2016 17:30:42 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id s+932DE6eEae; Thu, 11 Feb 2016 17:29:23 -0500 (EST)
Received: from [192.168.2.104] (pool-108-51-128-219.washdc.fios.verizon.net [108.51.128.219]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 7BDED9A4001; Thu, 11 Feb 2016 17:30:30 -0500 (EST)
Subject: Re: [IAB] IAB@iab.org mailing list closed, yet asks for comments?
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=windows-1252
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <56BD06D3.7020404@gmail.com>
Date: Thu, 11 Feb 2016 17:30:30 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C4F6B4C9-62CA-4C9F-9969-FD71CC9AC244@vigilsec.com>
References: <mailman.0.1455225768.17992.iab@iab.org> <56BD06D3.7020404@gmail.com>
To: Doug Royer <douglasroyer@gmail.com>
X-Mailer: Apple Mail (2.1085)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/B0K4YsxtPM0ZVm341gTQsAJMPzw>
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2016 22:30:47 -0000

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@iab.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@iab.org.
> 
> "...Please send comments to iab@iab.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@iab.org>
>> To: "IETF Announcement List" <ietf-announce@ietf.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@iab.org. For comments on individual drafts, please include the
> relevant document filename in the subject line.
> 
> 
> -- 
> 
> Doug Royer - (http://DougRoyer.US)
> DouglasRoyer@gmail.com
> 714-989-6135
>