Re: An RFC from the IAB
Steve Bellovin <smb@research.att.com> Sat, 23 March 1996 03:04 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06311; 22 Mar 96 22:04 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06307; 22 Mar 96 22:04 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa15624; 22 Mar 96 22:04 EST
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06300; 22 Mar 96 22:04 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06296; 22 Mar 96 22:04 EST
Received: from ns.research.att.com by CNRI.Reston.VA.US id aa15618; 22 Mar 96 22:04 EST
Received: from research.att.com by ns; Fri Mar 22 22:01:38 EST 1996
Received: from smb.research.att.com by research; Fri Mar 22 21:57:55 EST 1996
Received: from smb.research.att.com (smb@localhost) by smb.research.att.com (8.6.12/8.6.10) with ESMTP id SAA00993; Fri, 22 Mar 1996 18:35:14 -0500
Message-Id: <199603222335.SAA00993@smb.research.att.com>
X-Authentication-Warning: smb.research.att.com: smb owned process doing -bs
To: Brian Carpenter CERN-CN <brian@dxcoms.cern.ch>
cc: rfc-editor@isi.edu, iab@isi.edu, iesg <iesg@CNRI.Reston.VA.US>
Subject: Re: An RFC from the IAB
Date: Fri, 22 Mar 1996 18:30:13 -0500
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Steve Bellovin <smb@research.att.com>
These two requirements are rather contradictory... (There's been some discussion on the bind-workers mailing list about this, since there have been some security problems due to folks putting line delimiters into PTR records. So there's some need to check for syntactic purity in the DNS implementations, per RFC 952 and 1123. But what's a ``letter'' in Unicode? What is upper case in Hebrew or Kanji?) Mind you, I have no problem with the paragraphs being published more or less as is. Is there something we can say at this point to acknowledge the issue? 4.3 Public (i.e. widely visible) names should be in case-independent ASCII. Specifically, this refers to DNS names, and to protocol elements that are transmitted in text format. 5.4 Designs should be fully international, with support for localisation (adaptation to local character sets). In particular, there should be a uniform approach to character set tagging for information content.
- An RFC from the IAB Brian Carpenter CERN-CN
- Re: An RFC from the IAB Jeffrey I. Schiller
- Re: An RFC from the IAB Steve Bellovin
- Re: An RFC from the IAB Robert Elz
- Re: An RFC from the IAB Robert Elz
- Re: An RFC from the IAB Brian Carpenter CERN-CN
- Re: An RFC from the IAB rfc-ed