IAB@iab.org mailing list closed, yet asks for comments?

Doug Royer <douglasroyer@gmail.com> Thu, 11 February 2016 22:10 UTC

Return-Path: <douglasroyer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 615521B3B33 for <ietf@ietfa.amsl.com>; Thu, 11 Feb 2016 14:10:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id siNJnuX08XUz for <ietf@ietfa.amsl.com>; Thu, 11 Feb 2016 14:10:30 -0800 (PST)
Received: from mail-pf0-x22e.google.com (mail-pf0-x22e.google.com [IPv6:2607:f8b0:400e:c00::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32EA31B3006 for <ietf@ietf.org>; Thu, 11 Feb 2016 14:10:30 -0800 (PST)
Received: by mail-pf0-x22e.google.com with SMTP id q63so36081234pfb.0 for <ietf@ietf.org>; Thu, 11 Feb 2016 14:10:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-type; bh=SogoSxvJ9tMoCxNEbgqGwvDnonsXh0ht+aLDva1SKNA=; b=ygXSlDOiej/NR8TNyKwa9k40fSrr87dwukDmlU7q2oDdfder/r3vSNtRu9CxA3eRpv VsK0i72xmxywJZ8+GwNYG/0ufiTgNLk/ZL6t5KHf8GeiTgQHmJmNdZwQ5E7ScC1tM0q2 dGxxOVUacsocaKDzyqAPBzLZUiHrsofpnd7tA1Ww7g8MCPDOVnizp4mO844b+6Mtz6/F R3PnAUQUCtjnJwt6OXU0A0UmlummqnPSy1OZQ3iM2nQMem268P3gC/42IGMcQdWyUB+c aQX7CD+iB1YaP0ZMZMujp7fAhHBiQaco6NiNpFFPtyyvdxIdmYUBFyw4E3/XQnWuH/O1 Q60w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type; bh=SogoSxvJ9tMoCxNEbgqGwvDnonsXh0ht+aLDva1SKNA=; b=kLFUQbEpv3sezrRIq6IbP1yZB+LciQhSlcpa6xPnMEoT86tIZov38FG6U1yJHUd0+s dpBbF7kkmolV3jHhOsrDaer9YjjR2CxQvwiOvn/ksZJmXpYjjHISOvq12Wosoh9BnQgb 1yx0f1l+W2hGl/vYk6kfQIDpB/YfinwYTl6k8WdGtiHbhWvKA7BB8XDHGUgkUb7Rx/KC gVIclXVsdVWh+GKe2xgIvjuaga98BCQP/RF79g2XVM0kpEX5mgBItSEIIl1fymNNVJLd Lp+SH7Qlz3QItOLJSx/GKhLrkMfdoCC/sYa5RiyuUj+xOhzRasJujNQrquZVmag39C80 2yYw==
X-Gm-Message-State: AG10YOQ1LMIv/o+yTTVOPOW7oosK9XW7h9tUHK7aiz8gXOujhuE/uTnoFRyriVSIHLbuXA==
X-Received: by with SMTP id e88mr69250245pfb.62.1455228629819; Thu, 11 Feb 2016 14:10:29 -0800 (PST)
Received: from [] ([]) by smtp.googlemail.com with ESMTPSA id f12sm14468403pfd.87.2016. (version=TLSv1/SSLv3 cipher=OTHER); Thu, 11 Feb 2016 14:10:29 -0800 (PST)
Subject: IAB@iab.org mailing list closed, yet asks for comments?
To: iab-owner@iab.org, iab@iab.org, ietf@ietf.org
References: <mailman.0.1455225768.17992.iab@iab.org>
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <56BD06D3.7020404@gmail.com>
Date: Thu, 11 Feb 2016 15:10:27 -0700
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <mailman.0.1455225768.17992.iab@iab.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms040504070400080007020905"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/q5HkYEN4AwtuTPsbnhMkzcSjmMo>
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:10:34 -0000

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",

2. The underlying vocabulary

- - - Hoffman, P., "The 'XML2RFC' version 3 Vocabulary",

3. The outputs

- - - Hildebrand, J. and P. Hoffman, "HyperText Markup
   Language Request For Comments Format”,

- - - Flanagan, H., "Requirements for Plain Text RFCs",

- - - Hansen, T., Masinter, L., and M. Hardy, "PDF for
   an RFC Series Output Document Format”,

- - - Brownlee, N., "SVG Drawings for RFCs: SVG 1.2 RFC",

4. Generalized requirements

- - - Flanagan, H., "The Use of Non-ASCII Characters in RFCs",

- - - Flanagan, H., “CSS Requirements for RFCs”,

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",

- - - Hoffman, P. and T. Hansen, "Examples of the ‘XML2RFC'
   Version 2 and 3 Vocabularies”,

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)