Re: [apps-discuss] Fwd: I-D Action: draft-yevstifeyev-ftp-uri-scheme-04.txt

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Sat, 16 July 2011 07:58 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CB0921F8606 for <apps-discuss@ietfa.amsl.com>; Sat, 16 Jul 2011 00:58:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.753
X-Spam-Level:
X-Spam-Status: No, score=-99.753 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z1TGEjQg-mwA for <apps-discuss@ietfa.amsl.com>; Sat, 16 Jul 2011 00:58:18 -0700 (PDT)
Received: from acintmta01.acbb.aoyama.ac.jp (acintmta01.acbb.aoyama.ac.jp [133.2.20.33]) by ietfa.amsl.com (Postfix) with ESMTP id 58CDF21F85FF for <apps-discuss@ietf.org>; Sat, 16 Jul 2011 00:58:17 -0700 (PDT)
Received: from acmse01.acbb.aoyama.ac.jp ([133.2.20.226]) by acintmta01.acbb.aoyama.ac.jp (secret/secret) with SMTP id p6G7w9Ci009462 for <apps-discuss@ietf.org>; Sat, 16 Jul 2011 16:58:09 +0900
Received: from (unknown [133.2.206.133]) by acmse01.acbb.aoyama.ac.jp with smtp id 5ed6_bb39_58bbe570_af81_11e0_a569_001d096c5b62; Sat, 16 Jul 2011 16:58:09 +0900
Received: from [IPv6:::1] ([133.2.210.5]:33730) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S152F106> for <apps-discuss@ietf.org> from <duerst@it.aoyama.ac.jp>; Sat, 16 Jul 2011 16:58:11 +0900
Message-ID: <4E214464.7060208@it.aoyama.ac.jp>
Date: Sat, 16 Jul 2011 16:57:24 +0900
From: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
References: <4E15C895.6020701@gmail.com> <4E1B3270.40601@gmail.com> <CAHhFybpG-eoLb0uQ-JR9k7r1-NUohihXWS+w4Vsznpx=zYbGYA@mail.gmail.com> <4E1E62AB.2070608@gmail.com> <CAHhFyboH+EfdBzNTZtr9T9VNmUh6=psx2uBsS7Pc-HYmdWL65g@mail.gmail.com> <4E1FB79D.1020603@gmail.com> <4E1FBBC2.4070303@it.aoyama.ac.jp> <CAHhFybrOZYFXD5MasMx5ThxdnT36nLmXy+3ho-VrjaygQMA9zQ@mail.gmail.com>
In-Reply-To: <CAHhFybrOZYFXD5MasMx5ThxdnT36nLmXy+3ho-VrjaygQMA9zQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Apps-discuss list <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Fwd: I-D Action: draft-yevstifeyev-ftp-uri-scheme-04.txt
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jul 2011 07:58:19 -0000

On 2011/07/16 10:24, Frank Ellermann wrote:
> On 15 July 2011 06:02, "Martin J. Dürst" wrote:
>
>> Please read the text after the
>>     reserved    = gen-delims / sub-delims
>> ABNF rule in RFC 3986.
>
> Okay, but it doesn't explain the "lost"<national>  in RFC 1738:
>   national = "{" | "}" | "|" | "\" | "^" | "~" | "[" | "]" | "`"

At that time, various versions of ISO 646 were still in use (or at least 
feared to still be in use) which would have meant that these codepoints 
would have shown up as different glyphs in some environments (e.g. 
äöüÄÖÜß in the German version of ISO 646). As time moved on, this kind 
of concern grew smaller and smaller.


> This "forbidden" set was later reduced to<unwise>  in RFC 2396:
>   unwise   = "{" | "}" | "|" | "\" | "^" | "[" | "]" | "`"
>
> Skipping RFC 2732 introducing IPv6 literals using "[" and "]"
> RFC 3986 does not explain that some unencoded US-ASCII char.s
> are never permitted in URIs: "{" | "}" | "|" | "\" | "^" | "`"

Well, yes, it's the spec for URIs, not for "what's not allowed in URIs".


> And the "new" unencoded<gen-delims>  "[" / "]" are only allowed
> for "IPvNot4" literals in the<host>  part of the<authority>,
> no matter what any specific URI schemes such as RFC 6068 or
> specific fragment specifications such as RFC 5147 might wish.

That "[" / "]" can only be used for IPv6 addresses and the like is 
definitely somewhat inconsistent. If there ever were an update of RFC 
3986, I can imagine that to be changed (but that's only a guess).

> Unrelated, it is rather annoying that the IE and Chrome folks
> have not yet implemented RFC 5147, this nice feature should
> take the proverbial "five minutes" for a developer.

Does that mean that it's implemented in Firefox and Opera? That would be 
great to hear. For Chrome, you could submit a bug or patch to webkit, I 
guess.

Regards,    Martin.