Last Call: draft-farrel-rtg-common-bnf-07

From: Sam Hartman <hartmans-ietf at mit.edu>
To: ietf at ietf.org
Cc: draft-farrel-rtg-common-bnf at tools.ietf.org
Date: Thu, 22 Jan 2009 12:13:12 -0500

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 at ietf.org
https://www.ietf.org/mailman/listinfo/ietf

Follow-Ups:
- Re: Last Call: draft-farrel-rtg-common-bnf-07
  - From: Adrian Farrel

Prev by Date: Editors vs Authors vs Contributors, was: ANNOUNCEMENT: The IETF Trustees invite your review and comments on a proposed Work-Around to the Pre-5378 Problem
Next by Date: Re: Editors vs Authors vs Contributors, was: ANNOUNCEMENT: The IETF Trustees invite your review and comments on a proposed Work-Around to the Pre-5378 Problem
Previous by thread: Re: Last Call: draft-farrel-rtg-common-bnf (Reduced Backus-Naur Form (RBNF) A Syntax Used in Various Protocol Specifications) to Proposed Standard
Next by thread: Re: Last Call: draft-farrel-rtg-common-bnf-07
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Last Call: draft-farrel-rtg-common-bnf-07

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.