IETF Logo Mail Archive

Re: [nfsv4] work items to complete rfc3530bis (what are they?)

Nicolas Williams <Nicolas.Williams@sun.com> Wed, 31 March 2010 17:51 UTC

Return-Path: <Nicolas.Williams@sun.com>
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A5ED13A67D7 for <nfsv4@core3.amsl.com>; Wed, 31 Mar 2010 10:51:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.198
X-Spam-Level:
X-Spam-Status: No, score=-5.198 tagged_above=-999 required=5 tests=[AWL=0.270, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
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 hJuU8y-FF6si for <nfsv4@core3.amsl.com>; Wed, 31 Mar 2010 10:51:37 -0700 (PDT)
Received: from acsinet11.oracle.com (acsinet11.oracle.com [141.146.126.233]) by core3.amsl.com (Postfix) with ESMTP id AA1433A6817 for <nfsv4@ietf.org>; Wed, 31 Mar 2010 10:51:37 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by acsinet11.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o2VHppKS017068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 31 Mar 2010 17:51:53 GMT
Received: from acsmt354.oracle.com (acsmt354.oracle.com [141.146.40.154]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o2VFnSEU002115; Wed, 31 Mar 2010 17:51:50 GMT
Received: from abhmt017.oracle.com by acsmt355.oracle.com with ESMTP id 134756131270057839; Wed, 31 Mar 2010 10:50:39 -0700
Received: from Sun.COM (/129.153.128.104) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 31 Mar 2010 10:50:39 -0700
Date: Wed, 31 Mar 2010 12:50:32 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Black_David@emc.com
Message-ID: <20100331175032.GO4225@Sun.COM>
References: <20100330223502.GB21244@Sun.COM> <20100330224425.GA18810@fieldses.org> <20100330224913.GC21244@Sun.COM> <1269989661.10906.1.camel@localhost.localdomain> <20100330230250.GF21244@Sun.COM> <1269990565.10906.6.camel@localhost.localdomain> <20100330231828.GC4225@Sun.COM> <DB6FE7BD-6984-422B-920B-5411F00A7A01@gmail.com> <20100330232929.GD4225@Sun.COM> <C2D311A6F086424F99E385949ECFEBCB021F24B9@CORPUSMX80B.corp.emc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <C2D311A6F086424F99E385949ECFEBCB021F24B9@CORPUSMX80B.corp.emc.com>
User-Agent: Mutt/1.5.20 (2010-03-02)
X-Source-IP: acsmt354.oracle.com [141.146.40.154]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090202.4BB38BB7.00F0,ss=1,fgs=0
Cc: bfields@fieldses.org, trond.myklebust@fys.uio.no, Thomas.Haynes@sun.com, nfsv4@ietf.org
Subject: Re: [nfsv4] work items to complete rfc3530bis (what are they?)
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nfsv4>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Mar 2010 17:51:38 -0000

On Tue, Mar 30, 2010 at 08:56:59PM -0400, Black_David@emc.com wrote:
> > Search the RFC DB for "IDN" and "IDNA" and "Internationalized Domain
> Names".
> 
> It gets worse ...  Anyone who believes they understand how Unicode works
> in IDN needs to go look @ the proceedings of the newprep BOF in Anaheim.
> There are IDN changes coming (approved Internet-Drafts that are not yet
> published as RFCs).

All of these IDNAbis I-Ds are on the RFC-Editor queue right now:

 - draft-ietf-idnabis-protocol-18
 - draft-ietf-idnabis-rationale-17
 - draft-ietf-idnabis-defs-13
 - draft-ietf-idnabis-bidi-07
 - draft-ietf-idnabis-mappings-05
 - draft-ietf-idnabis-tables-09

https://datatracker.ietf.org/doc/draft-ietf-idnabis-protocol/
https://datatracker.ietf.org/doc/.../

The Newprep BoF isn't relevant to the IDNAbis work, but it is
potentially relevant to any protocol that uses stringprep profiles for
anything other than a domainname slot (that includes NFSv4).

IDNAbis doesn't radically change IDNA, at least not in ways that matter
to NFSv4.  There's still A-labels and U-labels (new terminology) and
IDN-aware and IDN-unaware domainname slots, and we still need to decide
whether NFSv4 domainname slots are IDN-aware or not.

Nico
--

v2.23.0 | Report a Bug | By Email