[IPFIX] shepherd writeup for text-adt draft (this time WITH the writeup)

Nevil Brownlee <[email protected]> Tue, 03 Dec 2013 11:41:59 +1300

Newsgroups	gmane.ietf.ipfix
Message-ID	<[email protected]>

Oops, here it is again, with the writeup attached!
Sorry about that, Nevil


Hi Benoit:

Here's the writeup for Brian Trammell's text-adt draft.

Cheers, Nevil

-- 
---------------------------------------------------------------------
  Nevil Brownlee                          Computer Science Department
  Phone: +64 9 373 7599 x88941             The University of Auckland
  FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand
_______________________________________________

_______________________________________________
IPFIX mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipfix

shepherd-ipfix-text-adt.txt (text/plain, 1.7 KB)

Write-up for:
  draft-trammell-ipfix-text-adt-03.txt
  Textual Representation of IPFIX Abstract Data Types

=== 1. Summary ===

Document shepherd: Nevil Brownlee
Responsible Area Director: Benoit Claise

This document is Informational, AD-sponsored by Benoit Claise.

This document defines UTF-8 representations for IPFIX abstract data
types, to support interoperable usage of the IPFIX Information
Elements with protocols based on textual encodings.

It describes a set of "canonical textual encodings for the IPFIX
abstract data types would allow this set of Information Elements to be
used for applications that use JSON or XML, and for these applications
to interoperate with IPFIX applications at the Information Element
definition level."

=== 2. Review and Consensus ===

This draft's -00 version was published in November 2012; at that
time the WG was busy with its chartered work items.  It was discussed
on the IPFIX list, and at later IPFIX meetings; it has been successively
improved since.

At the WG meeting in Vancouver (November 2013), there was clear consensus
that it should become an AD-sponsored document before the IPFIX WG closes.

=== 3. Intellectual Property ===

No IPR disclosures have been made directly on this draft, IPR
on it has not been discussed in the WG.

The author has stated that there are no IPR disclosures for it, 
nor could there be any.

=== 4. Other Points ===

This document has no downward references, and no IANA Considerations.

The ID-nits checker complains about it using RFC 2119 capitalisation
without citing 2119; I think that since it is Informational, that usage
is OK.

Overall, I believe that this draft is ready for publication as an RFC.

==== . ====