Re: [apps-discuss] draft-yevstifeyev-abnf-separated-lists-01.txt

Mykyta Yevstifeyev <evnikita2@gmail.com> Tue, 07 December 2010 11:04 UTC

Return-Path: <evnikita2@gmail.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 471683A6966 for <apps-discuss@core3.amsl.com>; Tue, 7 Dec 2010 03:04:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.843
X-Spam-Level:
X-Spam-Status: No, score=-3.843 tagged_above=-999 required=5 tests=[AWL=-0.244, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6sJVOqL2Oyfl for <apps-discuss@core3.amsl.com>; Tue, 7 Dec 2010 03:04:04 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id 635AC3A6949 for <apps-discuss@ietf.org>; Tue, 7 Dec 2010 03:04:04 -0800 (PST)
Received: by yxt33 with SMTP id 33so3307534yxt.31 for <apps-discuss@ietf.org>; Tue, 07 Dec 2010 03:05:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=ezzGUxZgWj4J3el6WFLDdW37S7FW37ss1YJoIUXZAYg=; b=PxmBfhdszX4hHXk3Mh33fkTaUnX/ul5xRHVoclzo2FDl6W5iFmpKl4JBV0pQ7UBnrf F9U4y4C/ZruVpe7MEgMsYRge3fdBXA9h3r9AUhnuEt3XI9d5P5Rx/eEgBdWriEhJlUI2 ZYYxy4jwV5ojN87+QyniKaIMqP3H3bZcMmkLg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=pukvLTExJdopKwVAQvMPd9pkugLBVBezsuUG+34k42pcaI4+kHwi8gs2m5J+1YlMcR e9St6F16Gfdw4DR20m6zfaxjo+w8hmKrV1lppPA4IluFrGa+vSyM4I3zZUPPcqMGxChI JqAkdmalEpcgv/Cb+aYSX7m6JajsZAHL8wKDM=
MIME-Version: 1.0
Received: by 10.150.158.15 with SMTP id g15mr1699237ybe.57.1291719929365; Tue, 07 Dec 2010 03:05:29 -0800 (PST)
Received: by 10.150.52.19 with HTTP; Tue, 7 Dec 2010 03:05:29 -0800 (PST)
In-Reply-To: <4CFDF3BB.30101@gmx.de>
References: <4CFC4694.5070408@att.com> <AANLkTimX4B3WTYaPS5mj+GjcNYYvKf3MpB8SB0TwA_dm@mail.gmail.com> <4CFCF71C.4050908@att.com> <4CFD0B37.7010601@gmail.com> <4CFD1238.4090902@gmail.com> <AANLkTinxjDqLus-+b1bMOxQMEgmiF4KfJeTCyN7yOsdf@mail.gmail.com> <AANLkTi=YDrLapDLEsw0561wZkZd8MmQ9vtJ1dtvqH+vX@mail.gmail.com> <4CFDF3BB.30101@gmx.de>
Date: Tue, 07 Dec 2010 13:05:29 +0200
Message-ID: <AANLkTi=wt+mSzcRmUS4K5WHOmWjbJiNNLawrrpDDgOpR@mail.gmail.com>
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Barry Leiba <barryleiba@computer.org>, Dave CROCKER <dcrocker@bbiw.net>, apps-discuss@ietf.org
Subject: Re: [apps-discuss] draft-yevstifeyev-abnf-separated-lists-01.txt
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 07 Dec 2010 11:04:05 -0000

Hello all,

I think I'll published the revised draft today with the folloeing constr:

n^(a)m = *LWS element <n-1>*<m-1>(*LWS a *LWS element)

like used in the HttpBIS WG draft. So this constr. will be available
on the ABNF spec.

2010/12/7, Julian Reschke <julian.reschke@gmx.de>:
> On 07.12.2010 08:41, Mykyta Yevstifeyev wrote:
>> ...
>>> I agree with Tony that if you can't include examples of how we should
>>> have had this before, it'll be hard to convince the community and the
>>> IESG that it's needed now.  We can always come up with things that
>>> *might* be useful, but part of the challenge is keeping the language
>>> as simple as possible (and no simpler).
>>>
>> The construction will be used while definig the HTTP headers which
>> contain the list of element. Now I am thinking about some other
>> examples.
>> ...
>
> If your use case is to specify new HTTP headers, I'd recommend that you
> stick with the RFC 2616 syntax (because you want to inherit the rules
> for implied LWS anyway).
LWS rule can simply be copied to rge specification of discussed construction.
>
> If you can wait for HTTPbis, you can use RFC 5234 syntax with # as an
> extension as defined by HTTPbis.
Yes, I agree but I want to put this rule but improved to RFC5234 as it
doe *not* have this rule. And what means "If you can wait for HTTPbis
..."
>
> Best regards, Julian
>
All the best,
Mykyta Yevstifeyev