IETF Logo Mail Archive

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

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Fri, 15 July 2011 04:03 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 84EC011E8070 for <apps-discuss@ietfa.amsl.com>; Thu, 14 Jul 2011 21:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.73
X-Spam-Level:
X-Spam-Status: No, score=-99.73 tagged_above=-999 required=5 tests=[AWL=0.060, 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 ryRxlgrdGjF7 for <apps-discuss@ietfa.amsl.com>; Thu, 14 Jul 2011 21:03:04 -0700 (PDT)
Received: from acintmta02.acbb.aoyama.ac.jp (acintmta02.acbb.aoyama.ac.jp [133.2.20.34]) by ietfa.amsl.com (Postfix) with ESMTP id C1AE011E8077 for <apps-discuss@ietf.org>; Thu, 14 Jul 2011 21:03:03 -0700 (PDT)
Received: from acmse01.acbb.aoyama.ac.jp ([133.2.20.226]) by acintmta02.acbb.aoyama.ac.jp (secret/secret) with SMTP id p6F42r2w004221 for <apps-discuss@ietf.org>; Fri, 15 Jul 2011 13:02:53 +0900
Received: from (unknown [133.2.206.133]) by acmse01.acbb.aoyama.ac.jp with smtp id 23c5_2580_50497820_ae97_11e0_9574_001d096c5b62; Fri, 15 Jul 2011 13:02:53 +0900
Received: from [IPv6:::1] ([133.2.210.5]:39685) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S152E6DF> for <apps-discuss@ietf.org> from <duerst@it.aoyama.ac.jp>; Fri, 15 Jul 2011 13:02:56 +0900
Message-ID: <4E1FBBC2.4070303@it.aoyama.ac.jp>
Date: Fri, 15 Jul 2011 13:02:10 +0900
From: "\"Martin J. Dürst\"" <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: Mykyta Yevstifeyev <evnikita2@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>
In-Reply-To: <4E1FB79D.1020603@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Fri, 15 Jul 2011 04:03:04 -0000

Hello Mykyta,

On 2011/07/15 12:44, Mykyta Yevstifeyev wrote:
> 15.07.2011 2:44, Frank Ellermann wrote:

>> That allows an unencoded '@' in the<path>, not the '@' you are
>> interested in while trying to skip any<userinfo>@.
>>
>> query = *( pchar / "/" / "?" )
>>
>> Ditto, unencoded '@' in the<query> (section 3.4, page 24).
>>
>> fragment = *( pchar / "/" / "?" )
>>
>> Ditto, unencoded '@' in the<fragment> (section 3.5, page 24).

> I see what you mean. I'll correct the expression as you proposed.
> However, I actually don't understand why "@" is either in <gen-delims>,
> which is in <reserved> and doesn't allow it to be present in queries and
> fragments, and in <pchar>, which is OK with this?

It has to do with the fact that some software components processing URIs 
and their componests have no scheme-specific knowledge, whereas others 
do. Please read the text after the
     reserved    = gen-delims / sub-delims
ABNF rule in RFC 3986.

Regards,    Martin.

v2.23.0 | Report a Bug | By Email