IANA considerations and expert review across different streams (was Re: [IAB] Call for comment: <draft-iab-rfc5741bis-01> (On RFC Streams, Headers, and Boilerplates))
Robert Sparks <rjsparks@nostrum.com> Wed, 27 January 2016 19:25 UTC
Return-Path: <rjsparks@nostrum.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 D84DD1B2B9D; Wed, 27 Jan 2016 11:25:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 E4A9iP1gQh31; Wed, 27 Jan 2016 11:25:36 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 B29181B2FFA; Wed, 27 Jan 2016 11:25:36 -0800 (PST)
Received: from unnumerable.local (pool-173-57-158-165.dllstx.fios.verizon.net [173.57.158.165]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u0RJPY6Y088624 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=OK); Wed, 27 Jan 2016 13:25:35 -0600 (CST) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host pool-173-57-158-165.dllstx.fios.verizon.net [173.57.158.165] claimed to be unnumerable.local
Subject: IANA considerations and expert review across different streams (was Re: [IAB] Call for comment: <draft-iab-rfc5741bis-01> (On RFC Streams, Headers, and Boilerplates))
To: Graham Klyne <gk@ninebynine.org>, ietf@ietf.org, iab@iab.org
References: <20151216174741.5946.14928.idtracker@ietfa.amsl.com> <5671FB0F.9010105@ninebynine.org>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <56A919AF.8010201@nostrum.com>
Date: Wed, 27 Jan 2016 13:25:35 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <5671FB0F.9010105@ninebynine.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Auyvj2R2WMY0eMhtu5VI-fyXRgg>
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: Wed, 27 Jan 2016 19:25:39 -0000
Hi Graham - You raise some good points to discuss, but this particular document isn't the place to capture the results of the conversation. There have been a few other comments on ietf general related to the expert review infrastructure in particular that would be good to pull into the discussion. While your primary suggestion crosses streams, I think it would be good to have the IESG staring at this closely too. RjS On 12/16/15 6:00 PM, Graham Klyne wrote: > On 16/12/2015 17:47, IAB Executive Administrative Manager wrote: >> This is an announcement of an IETF-wide Call for Comment on >> draft-iab-rfc5741bis-01. >> >> The document is being considered for publication as an Informational RFC >> within the IAB stream, and is available for inspection here: >> https://datatracker.ietf.org/doc/draft-iab-rfc5741bis/ >> >> The Call for Comment will last until 2016-01-13. Please send comments to >> iab@iab.org. >> >> >> Abstract >> >> RFC documents contain a number of fixed elements such as the title >> page header, standard boilerplates and copyright/IPR statements. >> This document describes them and introduces some updates to reflect >> current usage and requirements of RFC publication. In particular, >> this updated structure is intended to communicate clearly the source >> of RFC creation and review. This document obsoletes RFC 5741, >> moving >> detailed content to an IAB web page and preparing for more flexible >> output formats. > > I welcome this attempt to clarify the status of RFCs that are > published by differing routes. The point of my comment here is to ask > if it might be appropriate to extend the clarification provided to > include the effect of IANA considerations actions in RFCs from various > streams (that request registrations that are commonly associated with > standards actions). > > My comments here derive from reflection of my role as designated IANA > reviewer for URI-scheme and message header field name registries, > administered under guidance of [RFC7595] and [RFC3864] respectively. > > Both the IANA URI scheme registry [1] and the message header registry > [2] have allowance for *provisional* and *permanent* registrations, > with the intent that provisional registrations are permitted with low > overhead so that useful information about work in progress is easily > made available at a well-known location, and permanent registrations > are subject to a degree of review and practice that developers should > feel comfortable to use them in their implementation of > Internet-facing applications. > > There have been a small number of cases in which an ISE RFC > publication has requested a permanent registration (where the small > number here is 2 or 3). > > In at least one case, I felt that the lack of IETF review and/or > widespread implementation meant that permanent registration was not > appropriate, but the specifics of the guiding RFC did not make this an > obviously correct decision, and I felt I needed to request wider > support for my view. > > In at least one other case, despite the lack of formal review, I felt > the process followed, discussion that had taken place and apparent > scope of implementation meant that request for permanent registration > was appropriate, but again I felt the need to solicit support for this > view. > > My general concern here is that the status of IANA actions in ISE > stream publications is sometimes unclear, and use of the ISE track for > RFC publication might be used as an end run-around the expected review > process that is commonly associated with some registrations. In > hindsight, [RFC3864] (section 2.1) should explicitly indicate > IETF-stream informational RFC publication, but at the time this was > written, IIRC, independent publications were still usually last-called > in the IETF. > > You might reasonably say that the purpose of expert review is to deal > with edge cases like the ones I mention, and I'm OK with that. But > I'm also aware that it is important for decisions and processes to be > as transparent as possible: if review decisions can appear to be > arbitrary or unexpected then registrations may be discouraged and the > purpose of the registries undermined. > > Thanks. > > #g > -- > > [1] http://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml > > [2] http://www.iana.org/assignments/message-headers/message-headers.xhtml > > [RFC7595] http://tools.ietf.org/html/rfc7595 > > [RFC3864] http://tools.ietf.org/html/rfc3864 > >
- Re: Call for comment: <draft-iab-rfc5741bis-01> (… Graham Klyne
- IANA considerations and expert review across diff… Robert Sparks
- Re: IANA considerations and expert review across … Graham Klyne