Re: [perpass] draft-grothoff-iesg-special-use-p2p-names-00

Stephane Bortzmeyer <bortzmeyer@nic.fr> Tue, 19 November 2013 09:59 UTC

Return-Path: <bortzmeyer@nic.fr>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F28B1AD8F6 for <perpass@ietfa.amsl.com>; Tue, 19 Nov 2013 01:59:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.075
X-Spam-Level:
X-Spam-Status: No, score=-2.075 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.525] 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 QXPzvEfhA0gs for <perpass@ietfa.amsl.com>; Tue, 19 Nov 2013 01:59:22 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) by ietfa.amsl.com (Postfix) with ESMTP id 5E3831AD8F0 for <perpass@ietf.org>; Tue, 19 Nov 2013 01:59:22 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 0970B28019F; Tue, 19 Nov 2013 10:59:15 +0100 (CET)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id 02B87280129; Tue, 19 Nov 2013 10:59:15 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay2.nic.fr (Postfix) with ESMTP id 01517B3800C; Tue, 19 Nov 2013 10:58:45 +0100 (CET)
Date: Tue, 19 Nov 2013 10:58:44 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: SM <sm@resistor.net>
Message-ID: <20131119095844.GA12744@nic.fr>
References: <6.2.5.6.2.20131114043212.0cb4b710@elandnews.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <6.2.5.6.2.20131114043212.0cb4b710@elandnews.com>
X-Operating-System: Debian GNU/Linux 7.2
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Christian Grothoff <christian@grothoff.org>, "Hellekin O. Wolf" <hellekin@gnu.org>, perpass@ietf.org, Matthias Wachs <wachs@net.in.tum.de>, Jacob Appelbaum <jacob@appelbaum.net>
Subject: Re: [perpass] draft-grothoff-iesg-special-use-p2p-names-00
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 09:59:24 -0000

On Thu, Nov 14, 2013 at 04:48:26AM -0800,
 SM <sm@resistor.net> wrote 
 a message of 18 lines which said:

> The intended status is "IESG Approval".  I read the usual IETF
> documentation.  I could not find any mention of an IESG Approval
> document specification.

RFC 5226      

IESG Approval - New assignments may be approved by the IESG.
            Although there is no requirement that the request be
            documented in an RFC, the IESG has discretion to request
            documents or other supporting materials on a case-by-case
            basis.

            IESG Approval is not intended to be used often or as a
            "common case"; indeed, it has seldom been used in practice
            during the period RFC 2434 was in effect.  Rather, it is
            intended to be available in conjunction with other policies
            as a fall-back mechanism in the case where one of the other
            allowable approval mechanisms cannot be employed in a timely
            fashion or for some other compelling reason.  IESG Approval
            is not intended to circumvent the public review processes
            implied by other policies that could have been employed for
            a particular assignment.  IESG Approval would be
            appropriate, however, in cases where expediency is desired
            and there is strong consensus for making the assignment
            (e.g., WG consensus).