Re: [NSIS] Draft-ietf-nsis-ntlp: Late change of IANA consideration section

Thomas Narten <narten@us.ibm.com> Wed, 03 February 2010 14:50 UTC

Return-Path: <narten@us.ibm.com>
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C340E3A6A15; Wed, 3 Feb 2010 06:50:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level:
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 tMHNfF-dueGV; Wed, 3 Feb 2010 06:50:00 -0800 (PST)
Received: from e2.ny.us.ibm.com (e2.ny.us.ibm.com [32.97.182.142]) by core3.amsl.com (Postfix) with ESMTP id E51893A68A7; Wed, 3 Feb 2010 06:49:59 -0800 (PST)
Received: from d01relay07.pok.ibm.com (d01relay07.pok.ibm.com [9.56.227.147]) by e2.ny.us.ibm.com (8.14.3/8.13.1) with ESMTP id o13EbDaG026613; Wed, 3 Feb 2010 09:37:13 -0500
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay07.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id o13EkmaB1933330; Wed, 3 Feb 2010 09:46:48 -0500
Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVout) with ESMTP id o13EkmbW028020; Wed, 3 Feb 2010 09:46:48 -0500
Received: from cichlid.raleigh.ibm.com (sig-9-49-146-246.mts.ibm.com [9.49.146.246]) by d01av01.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVin) with ESMTP id o13EklZ0027879 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Feb 2010 09:46:48 -0500
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.3/8.12.5) with ESMTP id o13Ekknw017361; Wed, 3 Feb 2010 09:46:46 -0500
Message-Id: <201002031446.o13Ekknw017361@cichlid.raleigh.ibm.com>
To: Jari Arkko <jari.arkko@piuha.net>
In-reply-to: <4B69886E.4080606@piuha.net>
References: <4B694DC4.7060705@ericsson.com> <201002031355.o13Dt0ij008848@cichlid.raleigh.ibm.com> <4B69886E.4080606@piuha.net>
Comments: In-reply-to Jari Arkko <jari.arkko@piuha.net> message dated "Wed, 03 Feb 2010 16:30:06 +0200."
Date: Wed, 03 Feb 2010 09:46:46 -0500
From: Thomas Narten <narten@us.ibm.com>
Cc: ietf <ietf@ietf.org>, NSIS <nsis@ietf.org>
Subject: Re: [NSIS] Draft-ietf-nsis-ntlp: Late change of IANA consideration section
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nsis>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2010 14:50:00 -0000

> I do not understand this either, but I'll note that draft-ietf-nsis-ntlp 
> has a ton of Standards Action IANA rules. It does not make sense to have 
> such rules in a spec that itself is going for Experimental.

Well, this problem stems from the fact that the IETF produces all
sorts of  "mini-documents", and the appropriate status for individual
"mini-documents" is often fairly specific (e.g., BCP vs. Standards
vs. info, etc.).

But we often put them all in one document and don't worry so much
about whether the overall category of document is right for each
individual "mini-document" within the document.

I.e., one could argue that all IANA considerations should be BCPs (and
they usually are when they are standalone), but we don't ask standards
track documents to move the IANA considerations to a separate document
just to make all our categories look clean... (and for good reason!)

Thomas