1DLT and LINKTYPE allocation 2=========================== 3 4DLT_ types live in pcap/dlt.h. They can be requested by the community on a 5First-Come First-Served basis [i.e. https://tools.ietf.org/html/rfc8126#section-4.4 ] 6(Although libpcap is not at this time an IETF specification, there have been 7some as yet-incomplete efforts to do this). 8 9The Tcpdump Group prefers to link to an open specification on the new DLT_ 10type, but they are available for closed, proprietary projects as well. 11In that case, a stable email address suffices so that someone who finds 12an unknown DLT_ type can investigate. 13We prefer to give out unambiguous numbers, and we try to do it as quickly 14as possible, but DLT_USERx is available while you wait. 15 16Note that DLT_ types are, in theory, private to the capture mechanism and can 17in some cases be operating system specific, and so a second set of values, 18LINKTYPE_ is allocated for actually writing to pcap files. As much as 19possible going forward, the DLT_ and LINKTYPE_ value are identical, however, 20this was not always the case. See pcap-common.c. 21 22The LINKTYPE_ values are not exported, but are in pcap-common.c only. 23 24DEVELOPER NOTES 25--------------- 26 27When allocating a new DLT_ value, a corresponding value needs to be 28added to pcap-common.c. 29It is not necessary to copy the comments from dlt.h to pcap-common.c. 30