[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [idn] I-D ACTION:draft-ietf-idn-idna-08.txt

To: vint cerf <vinton.g.cerf@wcom.com>
Subject: Re: [idn] I-D ACTION:draft-ietf-idn-idna-08.txt
From: "Eric A. Hall" <ehall@ehsco.com>
Date: Thu, 30 May 2002 11:04:42 -0500
Cc: John C Klensin <klensin@jck.com>, IETF idn working group <idn@ops.ietf.org>
References: <20020529235947.GC382@nicemice.net> <20020529235947.GC382@nicemice.net> <5.0.2.1.2.20020530073209.066d8b50@shoe.reston.mci.net>

vint cerf wrote:
> 
> what has been the practice in implementations of the various
> referenced RFCs? John's interpretation or Robert's?
> 
> or has the apparent ambiguity also shown up in working
> implementations?

Whenever any ambiguity appears, it is at the UI level, and as a violation
of RFC 2181 (not allowing the use of eight-bit codes when creating an RR).

All of the servers I have looked at treat eight-bit codes as opaque data,
in accordance with the spec.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/

References:
- Re: [idn] I-D ACTION:draft-ietf-idn-idna-08.txt
  - From: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>
- Re: [idn] I-D ACTION:draft-ietf-idn-idna-08.txt
  - From: vint cerf <vinton.g.cerf@wcom.com>

Prev by Date: Re: [idn] I-D ACTION:draft-ietf-idn-idna-08.txt
Next by Date: [idn] Re: :Re: Last Call: Preparation of Internationalized Strings ('strin
Previous by thread: Re: [idn] I-D ACTION:draft-ietf-idn-idna-08.txt
Next by thread: Re: [idn] I-D ACTION:draft-ietf-idn-idna-08.txt
Index(es):
- Date
- Thread