Re: [tcpdump-workers] [pcap-ng-format] comments/edits on pcapng
[...] >So it sounds as if we can assign a number before the RFC is issued for a new >block type/link type/option code/etc., and update the registry when an I-D is >issued or updated or an RFC is issued. > >> But, it can also just be a link to http://www.company.com/technote/foo.html, >> or it can, as it says now, say, "Used by Company XYZ for Proprietary FOO" > >So presumably somebody who wants a link type would go to > >http://www.iana.org/form/protocol-assignment > >and request one. > >So does a Designated Expert for a registry get to edit whatever underlying >file or database is used to generate pages for the registry in question? I.e., >what would the Designated Expert do when adding a new block type/link >type/option/etc.? Is there a repository to which they're granted access and to >which they do a commit/push/whatever with the update? Is it a database for >which there's some Web interface to publish updates? > >Or does the Designated Expert send a request to somebody at the IANA, who >updates the file/database/whatever? > >I assume the actual underlying mechanism that implements the Protocol >Assignment registry pages is documented *somewhere*. "RFC Required" is just one possible policy and it is not expected to be the best policy for every case. RFC 5226 provides a good explanation of all the options (and is well worth its 20 pages of text overall), in its terms the practice currently established on tcpdump-workers@ is between "Expert Review" and "Specification Required" (the time available for review and requestor's motivation seeming to make the difference). Maybe it would make sense to declare "Expert Review" with a condition that requests without a specification are lowest priority? -- Denis Ovsienko ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] request for a DLT for ISO14443
On Nov 9, 2015, at 12:29 PM, Martin Kaiser wrote: > I would like to request a DLT for ISO14443. > > ISO14443 is a set of standards defining the communication protocols > between a contactless smartcard and a card reader. There are some > commercially available log tools for capturing such traffic. I've assigned 264 for LINKTYPE_ISO_14443/DLT_ISO_14443. > I created a webpage at > > http://www.kaiser.cx/pcap-iso14443.html > > that describes the data following the pcap header. You might want to update it to indicate that this can appear in both pcap and pcapng files, and perhaps just say that the packet time stamp must be seconds and fractions of a second since January 1, 1970, 00:00:00 UTC (not committing to it having microsecond resolution or to the time stamp having separate second and fraction-of-a-second fields; both pcap and pcapng can support, for example, nanosecond resolution, and pcapng time stamps are 64-bit fractions-of-a-second counts). You might also want to do the same for your DVB-CI page at http://www.kaiser.cx/pcap-dvbci.html. > This page can be > linked from http://www.tcpdump.org/linktypes.html. It should show up on the tcpdump.org website within 24 hours, I think. ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
