On Aug 12, 2024, at 1:29 PM, Joe Clarke (jclarke) 
<jclarke=40cisco....@dmarc.ietf.org> wrote:

>  For now, please review this document and provide all feedback on the list.

There are some link-layer types whose description is either:

1) insufficiently detailed, e.g. LINKTYPE_WIHART, which has a description on 
the source site for these descriptions, https://www.tcpdump.org/linktypes.html;

2) too long, e.g LINKTYPE_BLUETOOTH_HCI_H4 and LINKTYPE_USB_LINUX;

and possibly some that are both too long and still insufficiently detailed.

I've fixed some of them in the latest draft, such as LINKTYPE_NULL, which now 
has a quick description that points to a more detailed description, currently 
on the tcpdump.org Web site, but there are several more for which I'm 
developing fixes.

We could remove all of the ones with either insufficiently detailed or too-long 
descriptions, marking them as reserved, and add them later in future I-Ds/RFCs, 
to speed up the process of getting the registry created.

In either case, I'd prefer not to have those entries be in the RFC in their 
current form, whether we fix them or remove them and add them back in another 
I-D/RFC.

On that topic, is there a site that should be used to host the long 
descriptions of link-layer types that are currently hosted on tcpdump.org, such 
as the GitHub repository for these I-Ds, or that repository's GitHub Pages 
site?  We're currently hosting them, but I don't know whether another site 
would be more appropriate.
_______________________________________________
OPSAWG mailing list -- opsawg@ietf.org
To unsubscribe send an email to opsawg-le...@ietf.org

Reply via email to