[Ietf-message-headers] Re: HTTP header registration question

"Frank Ellermann" <nobody@xyzzy.claranet.de> Sat, 29 September 2007 10:50 UTC

Return-path: <ietf-message-headers-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IbZuC-0002J9-DI; Sat, 29 Sep 2007 06:50:40 -0400
Received: from ietf-message-headers by megatron.ietf.org with local (Exim 4.43) id 1IbZuB-0002Iy-B9 for ietf-message-headers-confirm+ok@megatron.ietf.org; Sat, 29 Sep 2007 06:50:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IbZuB-0002I5-1R for ietf-message-headers@lists.ietf.org; Sat, 29 Sep 2007 06:50:39 -0400
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IbZu1-0006mO-Ou for ietf-message-headers@lists.ietf.org; Sat, 29 Sep 2007 06:50:35 -0400
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IbZtc-0007W2-RA for ietf-message-headers@lists.ietf.org; Sat, 29 Sep 2007 10:50:04 +0000
Received: from 1cust117.tnt1.hbg2.deu.da.uu.net ([149.225.10.117]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf-message-headers@lists.ietf.org>; Sat, 29 Sep 2007 10:50:04 +0000
Received: from nobody by 1cust117.tnt1.hbg2.deu.da.uu.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf-message-headers@lists.ietf.org>; Sat, 29 Sep 2007 10:50:04 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ietf-message-headers@lists.ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Sat, 29 Sep 2007 12:49:17 +0200
Organization: http://purl.net/xyzzy
Lines: 17
Message-ID: <fdlak2$dd7$1@sea.gmane.org>
References: <op.tza9zqen64w2qv@annevk-t60.oslo.opera.com><6.0.0.20.2.20070928194301.0383ab30@localhost><op.tzc2vw0i64w2qv@annevk-t60.oslo.opera.com><fdj4u5$q45$1@sea.gmane.org> <op.tzetzn2l64w2qv@annevk-t60.oslo.opera.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: 1cust117.tnt1.hbg2.deu.da.uu.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1807
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc:
Subject: [Ietf-message-headers] Re: HTTP header registration question
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
Errors-To: ietf-message-headers-bounces@ietf.org

Anne van Kesteren wrote:
 
> Would using ireg-name be appropriate?

If you'd want IRIs excluding domain-literals.

But your draft is about HTTP, isn't it ?
For HTTP you need URIs, or RFC 3986 reg-name,
not RFC 3987 ireg-name.  

An HTTP header uses Latin-1.  You could say
that clients are supposed to translate an
ireg-name into a reg-name as explained in
RFC 3987 3.1, that would be IDNA punycode,
not simply percent-encoded UTF-8.

 Frank



_______________________________________________
Ietf-message-headers mailing list
Ietf-message-headers@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-message-headers