IETF Logo Mail Archive

Re: [IAB] IAB Call for review

Russ Housley <housley@vigilsec.com> Tue, 27 May 2014 14:14 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 59C751A03C6 for <ietf@ietfa.amsl.com>; Tue, 27 May 2014 07:14:56 -0700 (PDT)
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=unavailable
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 A1eVhJe7qIsS for <ietf@ietfa.amsl.com>; Tue, 27 May 2014 07:14:54 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 5F9511A011D for <ietf@ietf.org>; Tue, 27 May 2014 07:14:54 -0700 (PDT)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 2E09D9A419E; Tue, 27 May 2014 10:14:41 -0400 (EDT)
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 kZiKvtj8ic5a; Tue, 27 May 2014 10:14:20 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-144-77.washdc.fios.verizon.net [96.255.144.77]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 2C22E9A419C; Tue, 27 May 2014 10:14:20 -0400 (EDT)
Subject: Re: [IAB] IAB Call for review
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset="us-ascii"
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <6.2.5.6.2.20140524151438.0c3e6f10@resistor.net>
Date: Tue, 27 May 2014 10:14:08 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <21C1D36E-71B9-4223-9FA9-D66C19333725@vigilsec.com>
References: <C4DCDDAC-C2C9-4F10-BF19-BDFEBC28CB46@iab.org> <6.2.5.6.2.20140131000347.0b2edab0@resistor.net> <6.2.5.6.2.20140524151438.0c3e6f10@resistor.net>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dWHAzvONjf3UDbDl_bz0p4JM-EA
Cc: iab@iab.org, 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: <http://www.ietf.org/mail-archive/web/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: Tue, 27 May 2014 14:14:56 -0000

SM:

Please see RFC 4845. IAB Stream RFCs are seen as documents that speak 'for the IAB'.

Note that Step 5 in Section 3 says that the IAB Chair will call for comments. Then, comments received are considered for integration into the document.  The IAB shall determine whether the document is ready for publication based on the comments received, or whether another round of document editing and, optionally, a further call for input is required.

In practice, any significant feedback, beyond nits, is brought to the IAB for discussion.

Hope this helps.

Russ


On May 24, 2014, at 6:26 PM, S Moonesamy wrote:

> Hello,
> 
> I submitted comments about draft-iab-filtering-considerations-06 on January 31 in response to a Call for review from the IAB [1].  The Call for review ended on February 26.  There hasn't been any message about the comments which were submitted.
> 
> Could the IAB please enlighten me about how the IAB Call for review works?
> 
> Thanks,
> S. Moonesamy
> 
> 1. http://www.ietf.org/mail-archive/web/ietf-announce/current/msg12390.html
>

v2.23.0 | Report a Bug | By Email