55Network Working Group G. Harris, Ed.
66Internet-Draft
77Intended status: Standards Track M. Richardson
8- Expires: 23 April 2026 Sandelman
9- 20 October 2025
8+ Expires: 25 April 2026 Sandelman
9+ 22 October 2025
1010
1111
1212 Link-Layer Types for PCAP-related Capture File Formats
@@ -48,7 +48,7 @@ Status of This Memo
4848 time. It is inappropriate to use Internet-Drafts as reference
4949 material or to cite them other than as "work in progress."
5050
51- This Internet-Draft will expire on 23 April 2026.
51+ This Internet-Draft will expire on 25 April 2026.
5252
5353Copyright Notice
5454
@@ -67,18 +67,17 @@ Copyright Notice
6767Table of Contents
6868
6969 1. Introduction
70- 2. Terminology
71- 3. IANA Considerations
72- 3.1. PCAP Registry
73- 3.2. LinkType Registry
74- 3.2.1. Initial Values
75- 3.2.2. Guidance for Registration
76- 4. Security Considerations
77- 5. Contributors
78- 6. Acknowledgments
79- 7. References
80- 7.1. Normative References
81- 7.2. Informative References
70+ 2. IANA Considerations
71+ 2.1. PCAP Registry
72+ 2.2. LinkType Registry
73+ 2.2.1. Initial Values
74+ 2.2.2. Guidance for Registration
75+ 3. Security Considerations
76+ 4. Contributors
77+ 5. Acknowledgments
78+ 6. References
79+ 6.1. Normative References
80+ 6.2. Informative References
8281 Authors' Addresses
8382
84831. Introduction
@@ -103,25 +102,17 @@ Table of Contents
103102 establishing the IANA Considerations by which other uses of the PCAP-
104103 related formats may register new LinkType values.
105104
106- 2. Terminology
105+ 2. IANA Considerations
107106
108- The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
109- "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
110- "OPTIONAL" in this document are to be interpreted as described in
111- BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
112- capitals, as shown here.
113-
114- 3. IANA Considerations
115-
116- 3.1. PCAP Registry
107+ 2.1. PCAP Registry
117108
118109 IANA is requested to create a new registry group entitled "The PCAP
119110 Registry".
120111
121- 3 .2. LinkType Registry
112+ 2 .2. LinkType Registry
122113
123114 IANA is also requested to create a registry entitled "PCAP-related
124- LinkType List" under The PCAP registry group (Section 3 .1).
115+ LinkType List" under The PCAP registry group (Section 2 .1).
125116
126117 The registry has the following structure:
127118
@@ -146,7 +137,7 @@ Table of Contents
146137 * Values from 65001 to 65535 are reserved for Experimental Use
147138 (Section 4.2 of [RFC8126]).
148139
149- The initial version of the registry is provided in Section 3 .2.1. In
140+ The initial version of the registry is provided in Section 2 .2.1. In
150141 each case here, the reference should be set to [TCPDUMP] and the RFC
151142 number to be assigned to this document, which is not repeated each
152143 time.
@@ -175,7 +166,7 @@ Table of Contents
175166 values for some of them are operating system specific, and are
176167 thus not subject to standardization.
177168
178- 3 .2.1. Initial Values
169+ 2 .2.1. Initial Values
179170
180171 This is the initial table for the registry:
181172
@@ -1191,7 +1182,7 @@ Table of Contents
11911182 Description DECT-2020 New Radio (NR) MAC layer
11921183 Reference [LINKTYPE_DECT_NR]
11931184
1194- 3 .2.2. Guidance for Registration
1185+ 2 .2.2. Guidance for Registration
11951186
11961187 When processing a request for an allocation, the requester will be
11971188 asked to provide a specification at a stable URL. There is no
@@ -1211,7 +1202,7 @@ Table of Contents
12111202 subject to a security classification. The minimal requirement is to
12121203 provide a contact person for that link type.
12131204
1214- 4 . Security Considerations
1205+ 3 . Security Considerations
12151206
12161207 This document describes the IANA registration rules for the LinkType
12171208 encapsulations. PCAP-related packet file formats use this value to
@@ -1229,7 +1220,7 @@ Table of Contents
12291220 interpreting the packets need to carefully scrutinize all attempts to
12301221 read data from a capture.
12311222
1232- 5 . Contributors
1223+ 4 . Contributors
12331224
12341225 PCAP has been developed over three and half decades by a variety of
12351226 developers, including: Bill Fenner, Denis Ovsienko, Francois-Xavier
@@ -1240,31 +1231,22 @@ Table of Contents
12401231 PCAP was originally created at LBL by Steve McCanne, Craig Leres, and
12411232 Van Jacobson.
12421233
1243- 6 . Acknowledgments
1234+ 5 . Acknowledgments
12441235
12451236 The authors wish to thank: Michael Tuexen, Mohamed Boucadair, Carsten
12461237 Bormann, Henk Birkholtz, and Robert Wilton their invaluable comments
12471238 and encouragement.
12481239
1249- 7. References
1250-
1251- 7.1. Normative References
1252-
1253- [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
1254- Requirement Levels", BCP 14, RFC 2119,
1255- DOI 10.17487/RFC2119, March 1997,
1256- <https://www.rfc-editor.org/rfc/rfc2119>.
1240+ 6. References
12571241
1258- [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
1259- 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
1260- May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.
1242+ 6.1. Normative References
12611243
12621244 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
12631245 Writing an IANA Considerations Section in RFCs", BCP 26,
12641246 RFC 8126, DOI 10.17487/RFC8126, June 2017,
12651247 <https://www.rfc-editor.org/rfc/rfc8126>.
12661248
1267- 7 .2. Informative References
1249+ 6 .2. Informative References
12681250
12691251 [TCPDUMP] "LINK-LAYER HEADER TYPES",
12701252 <https://www.tcpdump.org/linktypes.html>.
0 commit comments