Re: Last Call: <draft-cotton-rfc4020bis-01.txt> (Early IANA Allocation ofStandards Track Code Points) to Best Current Practice
t.p. <daedulus@btconnect.com> Thu, 29 August 2013 14:42 UTC
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B11621E805A for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 07:42:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.521
X-Spam-Level:
X-Spam-Status: No, score=-3.521 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ei5cu9fjupwz for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 07:42:30 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe005.messaging.microsoft.com [216.32.181.185]) by ietfa.amsl.com (Postfix) with ESMTP id 7D4DD11E8117 for <ietf@ietf.org>; Thu, 29 Aug 2013 07:42:25 -0700 (PDT)
Received: from mail11-ch1-R.bigfish.com (10.43.68.236) by CH1EHSOBE002.bigfish.com (10.43.70.52) with Microsoft SMTP Server id 14.1.225.22; Thu, 29 Aug 2013 14:42:24 +0000
Received: from mail11-ch1 (localhost [127.0.0.1]) by mail11-ch1-R.bigfish.com (Postfix) with ESMTP id 47751340370; Thu, 29 Aug 2013 14:42:24 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.254.181; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0711HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -15
X-BigFish: PS-15(zz9371I542I1432I1418Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL17326ah186068h8275dh1de097hz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail11-ch1 (localhost.localdomain [127.0.0.1]) by mail11-ch1 (MessageSwitch) id 1377787342421187_26607; Thu, 29 Aug 2013 14:42:22 +0000 (UTC)
Received: from CH1EHSMHS029.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.236]) by mail11-ch1.bigfish.com (Postfix) with ESMTP id 6392F1C0075; Thu, 29 Aug 2013 14:42:22 +0000 (UTC)
Received: from DBXPRD0711HT004.eurprd07.prod.outlook.com (157.56.254.181) by CH1EHSMHS029.bigfish.com (10.43.70.29) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 29 Aug 2013 14:42:18 +0000
Received: from DBXPRD0611HT003.eurprd06.prod.outlook.com (157.56.254.85) by pod51017.outlook.com (10.255.178.37) with Microsoft SMTP Server (TLS) id 14.16.353.4; Thu, 29 Aug 2013 14:41:53 +0000
Message-ID: <005a01cea4c5$c9d030a0$4001a8c0@gateway.2wire.net>
From: "t.p." <daedulus@btconnect.com>
To: ietf@ietf.org
References: <20130827215216.30701.52572.idtracker@ietfa.amsl.com>
Subject: Re: Last Call: <draft-cotton-rfc4020bis-01.txt> (Early IANA Allocation ofStandards Track Code Points) to Best Current Practice
Date: Thu, 29 Aug 2013 15:39:32 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.254.85]
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 29 Aug 2013 14:42:36 -0000
This I-D uses the term 'deprecated' without defining it nor is the term defined in "IANA Considerations" [RFC5226] " (It does however already appear in the IANA Registry). I am familiar with the SMI definition but that seems not quite right for this context; some of the IANA uses of this have been there for decades and are unlikely ever to be removed. I think that this I-D needs a definition and, since I have seen disagreement on WG Lists as to what the term means, I think that that definition should be agree on the ietf list before this I-D is approved by the IESG. Tom Petch ----- Original Message ----- From: "The IESG" <iesg-secretary@ietf.org> To: "IETF-Announce" <ietf-announce@ietf.org> Sent: Tuesday, August 27, 2013 10:52 PM > > The IESG has received a request from an individual submitter to consider > the following document: > - 'Early IANA Allocation of Standards Track Code Points' > <draft-cotton-rfc4020bis-01.txt> as Best Current Practice > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send substantive comments to the > ietf@ietf.org mailing lists by 2013-09-24. Exceptionally, comments may be > sent to iesg@ietf.org instead. In either case, please retain the > beginning of the Subject line to allow automated sorting. > > Abstract > > This memo describes the process for early allocation of code points > by IANA from registries for which "Specification Required", "RFC > Required", "IETF Review", or "Standards Action" policies apply. This > process can be used to alleviate the problem where code point > allocation is needed to facilitate desired or required implementation > and deployment experience prior to publication of an RFC that would > normally trigger code point allocation. > > This document obsoletes RFC 4020. > > The file can be obtained via > http://datatracker.ietf.org/doc/draft-cotton-rfc4020bis/ > > IESG discussion can be tracked via > http://datatracker.ietf.org/doc/draft-cotton-rfc4020bis/ballot/ > > > No IPR declarations have been submitted directly on this I-D. >