IETF Logo Mail Archive

Re: [EAI] Rechartering

Shawn Steele <Shawn.Steele@microsoft.com> Fri, 24 July 2009 04:54 UTC

Return-Path: <Shawn.Steele@microsoft.com>
X-Original-To: ima@core3.amsl.com
Delivered-To: ima@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C74A3A691C for <ima@core3.amsl.com>; Thu, 23 Jul 2009 21:54:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.389
X-Spam-Level:
X-Spam-Status: No, score=-9.389 tagged_above=-999 required=5 tests=[AWL=1.210, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 nrr8AhCQ8weP for <ima@core3.amsl.com>; Thu, 23 Jul 2009 21:54:39 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 66F4B3A68DB for <ima@ietf.org>; Thu, 23 Jul 2009 21:54:39 -0700 (PDT)
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.99.4; Thu, 23 Jul 2009 21:52:53 -0700
Received: from tk5ex14mbxc105.redmond.corp.microsoft.com ([169.254.2.179]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi; Thu, 23 Jul 2009 21:52:53 -0700
From: Shawn Steele <Shawn.Steele@microsoft.com>
To: YAO Jiankang <yaojk@cnnic.cn>, John C Klensin <klensin@jck.com>, Harald Alvestrand <harald@alvestrand.no>
Thread-Topic: [EAI] Rechartering
Thread-Index: AQHKBv5CbMAbFBG94EaF4/MwRhfNZ5B6JnbwgAOnXACABQIwX4ABVhyN
Date: Fri, 24 Jul 2009 04:48:56 +0000
Message-ID: <CAD7705D4A93814F97D3EF00790AF0B315FDF9D6@tk5ex14mbxc105.redmond.corp.microsoft.com>
References: <mailman.13830.1247508102.4936.ima@ietf.org><CAD7705D4A93814F97D3EF00790AF0B315FA6650@tk5ex14mbxc105.redmond.corp.microsoft.com><4A5BABF8.4080900@isode.com><CAD7705D4A93814F97D3EF00790AF0B315FA6AAF@tk5ex14mbxc105.redmond.corp.microsoft.com><4A60AA0B.4000106@alvestrand.no><CAD7705D4A93814F97D3EF00790AF0B315FCA179@TK5EX14MBXC104.redmond.corp.microsoft.com>, <EA9664FBEBEB7127550C3D30@[192.168.1.110]> <448158382.31213@cnnic.cn>, <01fe01ca0b6e$dc14f6f0$236ff1da@whatisfuture>
In-Reply-To: <01fe01ca0b6e$dc14f6f0$236ff1da@whatisfuture>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ima@ietf.org" <ima@ietf.org>
Subject: Re: [EAI] Rechartering
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jul 2009 04:54:40 -0000

> As Xiaodong has already pointed out it, China's standards will be full
> compatible with IETF EAI WG RFCs. we will also follow the downgrade
> rfc. Actually, many chinese care for the downgrade issue very much.

I think that'll "work", however the current RFCs are EXPERIMENTAL, not STANDARD.  So any future RFCs need not be compatible with the experimental RFCs.  Should that (IMO very bad thing) happen, then the Chinese standard and the IETF standards would diverge :(

I think it would be "safest" if the IETF RFCs were updated to standards first, then the Chinese standards follow those, however I don't believe that'll happen in practice.  Then the IETF will have to choose to either just turn the experimental RFCs into real standards with minimal changes to conform to the defacto Chinese standard, or to deviate from the Chinese standard and break what might already be implimented.

- Shawn

v2.29.0 | Report a Bug | By Email | System Status