Re: Move forward with scoped literal URI format?

Zefram <zefram@fysh.org> Tue, 29 March 2005 18:26 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09417 for <ipv6-web-archive@ietf.org>; Tue, 29 Mar 2005 13:26:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DGLX1-0002Sc-Bx for ipv6-web-archive@ietf.org; Tue, 29 Mar 2005 13:33:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DGLMY-0005E8-0h; Tue, 29 Mar 2005 13:22:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DGLMW-0005E3-Kd for ipv6@megatron.ietf.org; Tue, 29 Mar 2005 13:22:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09066 for <ipv6@ietf.org>; Tue, 29 Mar 2005 13:22:43 -0500 (EST)
Received: from fysh.org ([83.170.75.51] helo=bowl.fysh.org ident=mail) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DGLTE-0002I6-Cy for ipv6@ietf.org; Tue, 29 Mar 2005 13:29:45 -0500
Received: from zefram by bowl.fysh.org with local (Exim 3.35 #1 (Debian)) id 1DGLMO-00027Y-00 for <ipv6@ietf.org>; Tue, 29 Mar 2005 19:22:40 +0100
Date: Tue, 29 Mar 2005 19:22:40 +0100
From: Zefram <zefram@fysh.org>
To: ipv6@ietf.org
Message-ID: <20050329182240.GA6565@fysh.org>
References: <200503290220.j2T2KJ8u007856@bright.research.att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <200503290220.j2T2KJ8u007856@bright.research.att.com>
User-Agent: Mutt/1.3.28i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Subject: Re: Move forward with scoped literal URI format?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab

Bill Fenner wrote:
>Any other input?

I agree with your analysis: proceed using "_" or some other innocuous
character; do not do anything that requires a change to the established
URI syntax.  I specifically reject the cut&paste argument in favour
of using unencoded "%": this is a sufficiently rare situation that
convenience really doesn't matter.

On the choice of innocuous character I have no strong opinion.  "_"
seems fine.  I note that ";" would be harmonious with existing syntax
elsewhere in URIs.  Almost any punctuation character looks OK, however.
Letters "g" to "z" (either case) are the only technically possible
characters that are really bad choices.

-zefram

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------