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

Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com> Sat, 16 July 2011 08:50 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 6D96721F85E5 for <apps-discuss@ietfa.amsl.com>; Sat, 16 Jul 2011 01:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.882
X-Spam-Level:
X-Spam-Status: No, score=-102.882 tagged_above=-999 required=5 tests=[AWL=-0.083, 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 b-6Q1BF55sER for <apps-discuss@ietfa.amsl.com>; Sat, 16 Jul 2011 01:50:23 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by ietfa.amsl.com (Postfix) with ESMTP id A498721F85AA for <apps-discuss@ietf.org>; Sat, 16 Jul 2011 01:50:23 -0700 (PDT)
Received: by pvh18 with SMTP id 18so2539715pvh.31 for <apps-discuss@ietf.org>; Sat, 16 Jul 2011 01:50:23 -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=SQaap4TMFxZEGcUQ7osytq+FIV35ZPLocUoRHTa33pI=; b=EtdGRrEpUOkPUlMTq5t/ZTTZ89NsXqP1/JsjOpJMhCTrwNxRTaPzMG+kxdW0kPF/ye 6GAh8YDG7tyD/dd4ji1xeVu7ZLdSaeVhZ5Bl7PfArgM41ScBXN592aVHH6xTb5sdMpzr LMyvbcWBDCJXBoLcbTiv7T+zAVL4krYfHx2y4=
Received: by 10.142.234.8 with SMTP id g8mr2118536wfh.180.1310806223196; Sat, 16 Jul 2011 01:50:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.88.9 with HTTP; Sat, 16 Jul 2011 01:50:03 -0700 (PDT)
In-Reply-To: <4E214464.7060208@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> <CAHhFybrOZYFXD5MasMx5ThxdnT36nLmXy+3ho-VrjaygQMA9zQ@mail.gmail.com> <4E214464.7060208@it.aoyama.ac.jp>
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Sat, 16 Jul 2011 10:50:03 +0200
Message-ID: <CAHhFybqygsy9W_T=ymPvTSnY3oMqpEZbavXTTjfTTS32vUtEZQ@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 08:50:24 -0000

On 16 July 2011 09:57, "Martin J. Dürst" wrote:

>> 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".

Okay - but not very helpful for folks trying to "upgrade" older
spec.s based on RFC 1738 to something based on RFC 3986/3987, or for
developers trying to filter completely bogus URIs.

The older RFCs had a nice <uric> rule for this purpose.  My list
above was incomplete, I forgot (at least) "<" / ">" / SP / DQUOTE

> 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).

For the pseudo-<path> in news://server/message-ID URIs that was
an obstacle.  But now I'm curious, there is no <path> in mailto:,
and that could allow square brackets in mailto: IPv6 literals...

Yes, RFC 6068 explicitly allows "[" ... "]" in a <domain>, good.

 [about RFC 5147]
> Does that mean that it's implemented in Firefox and Opera?

FF5 test with <http://www.postel.org/ien/txt/ien111.txt#line=1483>

No, sorry.  No opera on my box, that will be my last resort if I'm
ever annoyed with IE + Chrome + FF at the same time.  But I read
AvK's blog, just in case.

> For Chrome, you could submit a bug or patch to webkit, I guess.

Chromium issue 77024, waiting for "confirmation" since March.  For
IE9 a very complete issue report was closed as "not reproducible",
and I concluded that the IE9+ developers are not too interested
in contributions from IE9+ users.

-Frank