Last Call: draft-farrel-rtg-common-bnf-07
Sam Hartman <hartmans-ietf@mit.edu> Thu, 22 January 2009 17:13 UTC
Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D151B28C1B8; Thu, 22 Jan 2009 09:13:32 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F4E028C1B8 for <ietf@core3.amsl.com>; Thu, 22 Jan 2009 09:13:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.246
X-Spam-Level:
X-Spam-Status: No, score=-2.246 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 mjTTaTu6iPV7 for <ietf@core3.amsl.com>; Thu, 22 Jan 2009 09:13:30 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) by core3.amsl.com (Postfix) with ESMTP id 5AFFC3A695B for <ietf@ietf.org>; Thu, 22 Jan 2009 09:13:30 -0800 (PST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 3B967451D; Thu, 22 Jan 2009 12:13:12 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: ietf@ietf.org
Subject: Last Call: draft-farrel-rtg-common-bnf-07
Date: Thu, 22 Jan 2009 12:13:12 -0500
Message-ID: <tslprifz2l3.fsf@live.mit.edu>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Cc: draft-farrel-rtg-common-bnf@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org This draft specifies the BNF varient used in RSVP and related
protocols. The authors correctly indicate that converting these BNF specifications to use ABNF or some other already documented BNF form would be a lot of work. So, I agree that we should document this BNF varient. However I believe that this document could benefit from an applicability statement describing when this reduced varient is appropriate. Examples of cases where this seems appropriate include when extending RSVP or related protocols; when designing a new protocol that shares messages, objects or mind-share with RSVP; or if this BNF varient has already been in use for the protocol. Much of the text discussing this is in the document, but I think it would be better phrased as an applicability statement. _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Last Call: draft-farrel-rtg-common-bnf-07 Sam Hartman
- Re: Last Call: draft-farrel-rtg-common-bnf-07 Adrian Farrel