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

Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com> Sat, 16 July 2011 01:25 UTC

Return-Path: <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
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 11B8D21F8783 for <apps-discuss@ietfa.amsl.com>; Fri, 15 Jul 2011 18:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.863
X-Spam-Level:
X-Spam-Status: No, score=-102.863 tagged_above=-999 required=5 tests=[AWL=-0.064, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, 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 V8jUmSEV775G for <apps-discuss@ietfa.amsl.com>; Fri, 15 Jul 2011 18:25:15 -0700 (PDT)
Received: from mail-pz0-f52.google.com (mail-pz0-f52.google.com [209.85.210.52]) by ietfa.amsl.com (Postfix) with ESMTP id 8C7E421F8781 for <apps-discuss@ietf.org>; Fri, 15 Jul 2011 18:25:15 -0700 (PDT)
Received: by pzd13 with SMTP id 13so2427554pzd.39 for <apps-discuss@ietf.org>; Fri, 15 Jul 2011 18:25:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=yjbe5Joto2/3V7ItnLw/xAS8p75wB459pqcxXcLfB78=; b=k9UVWkcJX5Qkerg4OEtUbvoPe8PpdQXs98BLmyWZK/7ClfakQ6LfpXm9vDgzhNJ+V0 B+wPHmMcxBPE7QLuUXzaJFjDasKgIu7qEo5Ou97ENzoxJp1U7Q+lytQZuAVeLqfJPgw2 Z1Em7LxwyzU1Iu0CjpemXRstUQFv6t5veVBPA=
Received: by 10.142.214.8 with SMTP id m8mr1905596wfg.351.1310779515095; Fri, 15 Jul 2011 18:25:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.88.9 with HTTP; Fri, 15 Jul 2011 18:24:55 -0700 (PDT)
In-Reply-To: <4E1FBBC2.4070303@it.aoyama.ac.jp>
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>
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Sat, 16 Jul 2011 03:24:55 +0200
Message-ID: <CAHhFybrOZYFXD5MasMx5ThxdnT36nLmXy+3ho-VrjaygQMA9zQ@mail.gmail.com>
To: =?ISO-8859-1?Q?Martin_J=2E_D=FCrst?= <duerst@it.aoyama.ac.jp>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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 01:25:16 -0000

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 = "{" | "}" | "|" | "\" | "^" | "~" | "[" | "]" | "`"
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: "{" | "}" | "|" | "\" | "^" | "`"

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.

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.

-Frank