Re: Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP

Russ Housley <housley@vigilsec.com> Thu, 13 November 2008 17:41 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5982528C0E3; Thu, 13 Nov 2008 09:41:58 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5DE083A69BA for <ietf@core3.amsl.com>; Thu, 13 Nov 2008 09:41:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.819
X-Spam-Level:
X-Spam-Status: No, score=-101.819 tagged_above=-999 required=5 tests=[AWL=-0.019, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z59deoO6A7Ut for <ietf@core3.amsl.com>; Thu, 13 Nov 2008 09:41:56 -0800 (PST)
Received: from woodstock.binhost.com (woodstock.binhost.com [8.8.40.152]) by core3.amsl.com (Postfix) with SMTP id 755783A69AB for <ietf@ietf.org>; Thu, 13 Nov 2008 09:41:56 -0800 (PST)
Received: (qmail 7348 invoked by uid 0); 13 Nov 2008 17:41:51 -0000
Received: from unknown (HELO THINKPADR52.vigilsec.com) (96.255.143.189) by woodstock.binhost.com with SMTP; 13 Nov 2008 17:41:51 -0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 13 Nov 2008 12:41:53 -0500
To: SM <sm@resistor.net>
From: Russ Housley <housley@vigilsec.com>
Subject: Re: Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP
In-Reply-To: <6.2.5.6.2.20081113014508.028f3758@resistor.net>
References: <20081021150200.5A1833A6B44@core3.amsl.com> <917F6DFA1F45621CB238A4FA@[172.16.0.21]> <20081110162001.BFE403A683E@core3.amsl.com> <6.2.5.6.2.20081113014508.028f3758@resistor.net>
Mime-Version: 1.0
Message-Id: <20081113174156.755783A69AB@core3.amsl.com>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

>>To make them all parallel in structure, the first numbered item in 
>>section 3 becomes: "1. The IESG finds no conflict between this 
>>document and IETF work."
>>
>>In RFC 3932, these numbered items (except the first one, which is 
>>the same until the modification above) begin "The IESG 
>>thinks"  During pre-Last-Call-review, I received feedback that "The 
>>IESG finds" was a better.  Now, you propose "The IESG 
>>believes".    I do believe that the current wording is better than 
>>the original.  I'm willing to change it to something else if there 
>>is consensus to do so.  What do other reviewers find/think/believe/prefer?
>
>In a different message, John mentioned ""has concluded".  That 
>sounds better as the numbered items are about conclusions 
>reached.  My second preference would be "The IESG believes".

I am happy with "has concluded".  The numbered list is changed as follows:

    The IESG review of these Independent Stream and IRTF Stream documents
    reach one of the following five types of conclusions.

    1. The IESG has concluded that there is no conflict between this
       document and IETF work.

    2. The IESG has concluded that this work is related to IETF work done
       in WG <X>, but this relationship does not prevent publishing.

    3. The IESG has concluded that publication is potentially harmful to
       the IETF work done in WG <X> and recommends not publishing the
       document at this time.

    4. The IESG has concluded that this document violates IETF procedures
       for <X> and should therefore not be published without IETF review
       and IESG approval.

    5. The IESG has concluded that this document extends an IETF protocol
       in a way that requires IETF review and should therefore not be
       published without IETF review and IESG approval.

Russ 

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf