Subject: [fdt] Fwd: New Version Notification for draft-mcquistin-augmented-ascii-diagrams-02.txt

From: Stephen McQuistin <[email-masked]>
Date: Tue, 4 Feb 2020 17:03:44 +0000

Hi all,

We’ve submitted an update to our draft, to add text for the following:
	- there is a trade-off between expressiveness allowed by a protocol description language, and the safety, computability, and security of the parser code generated for the protocols described; and
	- that any protocol description language should allow for protocols to develop and evolve across multiple documents.

Comments and questions welcome.

Thanks,

Stephen

> Begin forwarded message:
> 
> From: [email-masked]
> Subject: New Version Notification for draft-mcquistin-augmented-ascii-diagrams-02.txt
> Date: 4 February 2020 at 16:39:46 GMT
> To: "Colin Perkins" <[email-masked]>, "Stephen McQuistin" <[email-masked]>, "Vivian Band" <[email-masked]>
> 
> 
> A new version of I-D, draft-mcquistin-augmented-ascii-diagrams-02.txt
> has been successfully submitted by Stephen McQuistin and posted to the
> IETF repository.
> 
> Name:		draft-mcquistin-augmented-ascii-diagrams
> Revision:	02
> Title:		Describing Protocol Data Units with Augmented Packet Header Diagrams
> Document date:	2020-02-04
> Group:		Individual Submission
> Pages:		19
> URL:            https://www.ietf.org/internet-drafts/draft-mcquistin-augmented-ascii-diagrams-02.txt
> Status:         https://datatracker.ietf.org/doc/draft-mcquistin-augmented-ascii-diagrams/
> Htmlized:       https://tools.ietf.org/html/draft-mcquistin-augmented-ascii-diagrams-02
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-mcquistin-augmented-ascii-diagrams
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-mcquistin-augmented-ascii-diagrams-02
> 
> Abstract:
>   This document describes a machine-readable format for specifying the
>   syntax of protocol data units within a protocol specification.  This
>   format is comprised of a consistently formatted packet header
>   diagram, followed by structured explanatory text.  It is designed to
>   maintain human readability while enabling support for automated
>   parser generation from the specification document.  This document is
>   itself an example of how the format can be used.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
>