The IESG has approved the following document:
- 'Link-Layer Types for PCAP-related Capture File Formats'
  (draft-ietf-opsawg-pcaplinktype-17.txt) as Informational RFC

This document is the product of the Operations and Management Area Working
Group.

The IESG contact persons are Mahesh Jethanandani and Mohamed Boucadair.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-pcaplinktype/




Technical Summary

   This document describes a set of PCAP-related LinkType values and
   creates an IANA registry for those values.

Working Group Summary

   Was there anything in the WG process that is worth noting?
   For example, was there controversy about particular points 
   or were there decisions where the consensus was
   particularly rough? 

>From the Shepherd's report:

There have been some discussions on this, but in general the WG wasn't very
active.  That said, there was no dissent to publish this.  One thing that was
brought up is perhaps maintaining this registry outside of IANA (.e.g, GitHub),
but keeping it outside the IETF process for those "needs specification" items
is not ideal.

Document Quality

   Are there existing implementations of the protocol?  Have a 
   significant number of vendors indicated their plan to
   implement the specification?  Are there any reviewers that
   merit special mention as having done a thorough review,
   e.g., one that resulted in important changes or a
   conclusion that the document had no substantive issues?  If
   there was a MIB Doctor, Media Type, or other Expert Review,
   what was its course (briefly)?  In the case of a Media Type
   Review, on what date was the request posted?

Personnel

   The Document Shepherd for this document is Joe Clarke. The Responsible
   Area Director is Mahesh Jethanandani.

IANA Note

  IANA is requested to create a new registry group entitled "The PCAP Registry".



_______________________________________________
OPSAWG mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to