Re: [OSPF] Barry Leiba's No Objection on draft-ietf-ospf-ospfv3-autoconfig-12: (with COMMENT)
Barry Leiba <barryleiba@computer.org> Mon, 26 January 2015 14:24 UTC
Return-Path: <barryleiba@gmail.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36C7B1A884B; Mon, 26 Jan 2015 06:24:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
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 SlpZPv0EH7he; Mon, 26 Jan 2015 06:24:43 -0800 (PST)
Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F065A1A8849; Mon, 26 Jan 2015 06:24:42 -0800 (PST)
Received: by mail-lb0-f173.google.com with SMTP id p9so7812204lbv.4; Mon, 26 Jan 2015 06:24:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=eaSJdNxTJZ0BwvL4Zi5zotIOs/VzTB3ffg2iq8czHIo=; b=B4YbdyBFlaK18xuDu6xDcG2pg8tfD0K5C2PNLVKpm62xsqqv7k9D16EGHtOS2wVgVr +iH6Y6ONHirx024UJe78AVdpwX9M+o+cCgjjU2ObDkd7HM7RRHJJcSqo5sxSyuIPLiVi Yj4BsQZWYY0+pXhwWNE3HoQRAUBQPtFMci/iWtayWU1J/O+gXFMel2Dezdflw1JJdKjM YfdmGZ7wAsvhhMuVbthviWctGPBpsV/CaaN/mlgLeCCcUDY3vRjvrDdj0RuihdpZZGJA rE7kBkl6A3ovSphpKma6Iuyz848P1YqMHpKjJgSQZtRhb70L+ZpGVo/7dg0VfYlV85Wi aYsg==
MIME-Version: 1.0
X-Received: by 10.112.85.11 with SMTP id d11mr21385633lbz.100.1422282281535; Mon, 26 Jan 2015 06:24:41 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.152.127.168 with HTTP; Mon, 26 Jan 2015 06:24:41 -0800 (PST)
In-Reply-To: <86AB738D-7428-4DA3-9E2C-D8D1D6CE53F2@piuha.net>
References: <20150126113942.22176.94.idtracker@ietfa.amsl.com> <D0EBAFED.C41D%acee@cisco.com> <CALaySJ+f9sQ5LbhFeWhpsx=40LFMrgmNYHd6bya5Ki_2cr9zZA@mail.gmail.com> <86AB738D-7428-4DA3-9E2C-D8D1D6CE53F2@piuha.net>
Date: Mon, 26 Jan 2015 09:24:41 -0500
X-Google-Sender-Auth: rPYVlHhVLFIG9E9vXP49gxuBgzk
Message-ID: <CALaySJJn+B0vN9E+nT7kK8JwmuptqekEPVmjhh+EhStF9n46Pw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset="ISO-8859-1"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ospf/54iyWLROw0xuJPtKoMUnmJ75yiU>
Cc: "ospf-chairs@tools.ietf.org" <ospf-chairs@tools.ietf.org>, "ospf@ietf.org" <ospf@ietf.org>, Ing-Wher Chen <ing-wher.chen@ericsson.com>, The IESG <iesg@ietf.org>, "draft-ietf-ospf-ospfv3-autoconfig.all@tools.ietf.org" <draft-ietf-ospf-ospfv3-autoconfig.all@tools.ietf.org>
Subject: Re: [OSPF] Barry Leiba's No Objection on draft-ietf-ospf-ospfv3-autoconfig-12: (with COMMENT)
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 14:24:44 -0000
>> Indeed. But we'd like to avoid having people make requests to the >> IESG when they should have done it with I-Ds and IETF Review. So it'd >> be nice (non-blocking nice) to have something that explains (very, >> very briefly) when going directly to the IESG is appropriate. > > I think we've been using this format (IETF review or IESG approval) > for quite a long time. I think the guidance for when things are > appropriate is more important for things like expert review. In this > case the IESG is expected to be able to tell applicants to go for IETF > review where needed. Most of the time the IESG review acts as a safety > valve anyway; we can sometimes approve an allocation from another SDO, > for instance, if it makes sense, etc, or an experimental value instead > of standards track one. > > If you want more words, I'd prefer "IETF Review or, under exceptional > circumstances, IESG Approval". I'm open to other words. And I'm open to whatever you think is best, which is why I stressed "non-blocking nice". If you think it's not important to expand on this, I accept that answer, with thanks for considering my comment. b
- [OSPF] Barry Leiba's No Objection on draft-ietf-o… Barry Leiba
- Re: [OSPF] Barry Leiba's No Objection on draft-ie… Acee Lindem (acee)
- Re: [OSPF] Barry Leiba's No Objection on draft-ie… Barry Leiba
- Re: [OSPF] Barry Leiba's No Objection on draft-ie… Jari Arkko
- Re: [OSPF] Barry Leiba's No Objection on draft-ie… Barry Leiba
- Re: [OSPF] Barry Leiba's No Objection on draft-ie… Jari Arkko