Re: Examples needed of IANA values in -bis documents

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Mon, 30 November 2009 06:43 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: wgchairs@core3.amsl.com
Delivered-To: wgchairs@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 52C303A698D for <wgchairs@core3.amsl.com>; Sun, 29 Nov 2009 22:43:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.248
X-Spam-Level:
X-Spam-Status: No, score=-1.248 tagged_above=-999 required=5 tests=[AWL=-1.458, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3]
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 6JRWRL3Neria for <wgchairs@core3.amsl.com>; Sun, 29 Nov 2009 22:43:25 -0800 (PST)
Received: from scmailgw02.scop.aoyama.ac.jp (scmailgw02.scop.aoyama.ac.jp [133.2.251.42]) by core3.amsl.com (Postfix) with ESMTP id 8232E3A6855 for <wgchairs@ietf.org>; Sun, 29 Nov 2009 22:43:25 -0800 (PST)
Received: from scmse01.scbb.aoyama.ac.jp (scmse01.scbb.aoyama.ac.jp [133.2.253.158]) by scmailgw02.scop.aoyama.ac.jp (secret/secret) with SMTP id nAU6h7dA015574 for <wgchairs@ietf.org>; Mon, 30 Nov 2009 15:43:07 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 025b_9e33d57e_dd7b_11de_a0f2_001d096c566a; Mon, 30 Nov 2009 15:43:07 +0900
Received: from [IPv6:::1] ([133.2.210.1]:47949) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S1281D20> for <wgchairs@ietf.org> from <duerst@it.aoyama.ac.jp>; Mon, 30 Nov 2009 15:39:29 +0900
Message-ID: <4B136962.2010505@it.aoyama.ac.jp>
Date: Mon, 30 Nov 2009 15:42:42 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.1) Gecko/20090902 Eudora/3.0b3
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Examples needed of IANA values in -bis documents
References: <p06240842c738da2fabdf@[10.20.30.158]>
In-Reply-To: <p06240842c738da2fabdf@[10.20.30.158]>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Nov 2009 06:43:27 -0000

Hello Paul,

The LTRU WG's main job (as the name says: Language Tag Registry Update) 
was to update data in the IANA registry (two times, under two different 
charters).

The updates happened via Internet-Drafts. We separated the 'protocol' 
aspects (going to RFC as is) from the registry update data (going to IANA).

We were very concerned about people looking at a future RFC (frozen) 
rather than the IANA registry (actively updated). Therefore, the RFC 
Editor was instructed to remove the bulk of the 'registry update' draft 
before publishing it to an RFC.

See http://tools.ietf.org/html/draft-ietf-ltru-4645bis-10 (close to 1000 
pages) vs. http://tools.ietf.org/html/rfc5645 (11 pages) for the most 
recent charter.

For the first charter, see 
http://tools.ietf.org/html/draft-ietf-ltru-initial-06 (118 pages) vs. 
http://tools.ietf.org/html/rfc4645 (7 pages).

In the first round, it took quite a bit of time to work this out, but I 
don't think anybody involved has any reasons to regret this aspect of 
our work, I think overall, it worked really well. As a consequence, none 
of the people involved had to spend unproductive time telling others 
"well, the RFC is incomplete/irrelevant, the IANA registry is what counts".

Regards,   Martin.


On 2009/11/30 11:17, Paul Hoffman wrote:
> Greetings again. Yaron and I have an interesting situation in the IPsecME WG, and we are looking for historical experience from other WGs that might relate to it. We are doing a -bis revision to IKEv2 (RFC 4306). RFC 4306 contains many tables with values that were used to fill in the IANA IKEv2 registry. Our -bis document has carried those tables forward, but we have gotten some questions about what the tables mean given that the IANA registry now has additional entries added after RFC 4306 was published.
>
> Some folks would like to see the values removed from the -bis document and statements added that developers should see the IANA registry. Some folks would like to leave the tables as they were. Some folks would like to see the tables left in and updated to match the current registry.
>
> Yaron and I would like to find WGs that have already faced this issue and find out what you did, and whether it was considered a good idea afterward. We are *not* looking for more opinions; we have plenty of those already. What would be most useful to our WG is examples of what has happened in the IETF in the past. Thanks in advance!
>
> --Paul Hoffman, Director
> --VPN Consortium
>

-- 
#-# Martin J. Dürst, Professor, Aoyama Gakuin University
#-# http://www.sw.it.aoyama.ac.jp   mailto:duerst@it.aoyama.ac.jp