Network Working Group K. Sarcar
Request for Comments: 3827 Sun Microsystems, Inc.
Category: Informational June 2004
Additional Snoop Datalink Types
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright (C) The Internet Society (2004).
The snoop file format provides a way to store and exchange datalink
layer packet traces. This document describes extensions to this file
format to support new media.
[RFC1761] defines the snoop file format used to store captured
network packets for tools that capture, display, and interpret
network traffic. The file format specifies a header containing the
Datalink Type field that identifies the network's datalink type.
This document defines new values for this field, as well as an IANA
registry for future datalink types.
2. New Datalink Types
In addition to the Datalink Type codes listed in [RFC1761], this
document defines the following type codes for the corresponding
Datalink Type Code
Fibre Channel 16
ATM Classical IP 18
IP over Infiniband 26
The IP over Infiniband packet format is described in [IPoIB].
Sarcar Informational [Page 1]RFC 3827 Additional Snoop Datalink Types June 20043. IANA Considerations
This document created a new IANA registry named "Snoop Datalink
Types" to hold the various possible 32-bit (4 octet) snoop datalink
types. This new registry holds the values previously defined in
[RFC1761] and tabulated below:
Datalink Type Code
IEEE 802.3 0
IEEE 802.4 Token Bus 1
IEEE 802.5 Token Ring 2
IEEE 802.6 Metro Net 3
Character Synchronous 6
IBM Channel-to-Channel 7
Additionally, the new registry also holds the values defined above in
section 2 of this document.
All new allocations and assignments to this registry starting from
code 27 will follow the First Come First Served policy outlined in
[BCP0026]. Type codes up to 26 not defined by this section of the
document (10-15 and 19-25) are considered reserved.
4. Security Considerations
The addition of new datalink type codes to the existing file format
poses no known security risks.
The author would like to thank Jim Carlson, Brent Callaghan, and Bill
Strahm for meticulously reviewing this document.
6. References6.1. Normative References
[RFC1761] Callaghan, B. and R. Gilligan, "Snoop Version 2 Packet
Capture File Format", RFC 1761, February 1995.
Sarcar Informational [Page 2]RFC 3827 Additional Snoop Datalink Types June 2004
[BCP0026] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434,
6.2. Informative References
[IPoIB] Kashyap, V. and H.K. Chu, "IP encapsulation and address
resolution over InfiniBand networks", Work in Progress,
7. Author's Address
Sun Microsystems, Inc.
14 Network Circle
Bldg 14, MPK14-333
Menlo Park, CA 94025
Sarcar Informational [Page 3]RFC 3827 Additional Snoop Datalink Types June 20048. Full Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an