idnits 2.17.1 draft-sarcar-snoop-new-types-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 3 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 4 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 162 has weird spacing: '...for the purpo...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 2003) is 7467 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Downref: Normative reference to an Informational RFC: RFC 1761 ** Obsolete normative reference: RFC 2434 (ref. 'BCP0026') (Obsoleted by RFC 5226) == Outdated reference: A later version (-09) exists of draft-ietf-ipoib-ip-over-infiniband-04 Summary: 3 errors (**), 0 flaws (~~), 6 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Kanoj Sarcar 2 INTERNET-DRAFT Sun Microsystems, Inc. 3 Expires May 2004 November 2003 5 Additional Snoop Datalink Types 6 8 Status of this Memo 10 This document is an Internet-Draft and is subject to all provisions 11 of Section 10 of RFC2026. 13 Internet-Drafts are working documents of the Internet Engineering 14 Task Force (IETF), its areas, and its working groups. Note that 15 other groups may also distribute working documents as 16 Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six 19 months and may be updated, replaced, or obsoleted by other 20 documents at any time. It is inappropriate to use Internet- 21 Drafts as reference material or to cite them other than as 22 "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/1id-abstracts.html 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html 30 Abstract 32 The snoop file format provides a way to store and exchange 33 datalink layer packet traces. This document describes extensions 34 to this file format to support new media. 36 1. Introduction 38 [RFC1761] defines the snoop file format used to store captured 39 network packets for tools that capture, display and interpret 40 network traffic. The file format specifies a header containing 41 the Datalink Type field that identifies the network's datalink 42 type. This document defines new values for this field, as 43 well as an IANA registry for future datalink types. 45 2. New Datalink Types 47 In addition to the Datalink Type codes listed in [RFC1761], this 48 document defines the following type codes for the corresponding 49 media: 51 Datalink Type Code 52 ------------- ---- 54 Fibre Channel 16 55 ATM 17 56 ATM Classical IP 18 57 IP over Infiniband 26 59 The IP over Infiniband packet format is described in [IPoIB]. 61 3. IANA Considerations 63 This document creates a new IANA registry named "Snoop Datalink 64 Types" to hold the various possible 32-bit (4 octet) snoop datalink 65 types. This new registry will hold the values previously defined in 66 [RFC1761] and tabulated below: 68 Datalink Type Code 69 ------------- ---- 71 IEEE 802.3 0 72 IEEE 802.4 Token Bus 1 73 IEEE 802.5 Token Ring 2 74 IEEE 802.6 Metro Net 3 75 Ethernet 4 76 HDLC 5 77 Character Synchronous 6 78 IBM Channel-to-Channel 7 79 FDDI 8 80 Other 9 82 Additionally, the new registry will also hold the values defined 83 above in section 2 of this document. 85 All new allocations and assignments to this registry starting 86 from code 27 will follow the First Come First Served policy 87 outlined in [BCP0026]. Type codes upto 26 not defined by this 88 section of the document (10-15 and 19-25) are considered reserved. 90 4. Security Considerations 92 The addition of new datalink type codes to the existing file format 93 poses no known security risks. 95 5. Acknowledgements 97 The author would like to thank Jim Carlson, Brent Callaghan and 98 Bill Strahm for meticulously reviewing this draft. 100 6. References 102 6.1. Normative References 104 [RFC1761] B. Callaghan, R. Gilligan, "Snoop Version 2 Packet Capture 105 File Format", RFC 1761, February 1995. 107 [BCP0026] T. Narten, H. Alvestrand, "Guidelines for Writing an IANA 108 Considerations Section in RFCs", RFC 2434, October 1998. 110 6.2. Informative References 112 [IPoIB] V. Kashyap, H.K.Jerry Chu, "IP encapsulation and address 113 resolution over InfiniBand networks", 114 draft-ietf-ipoib-ip-over-infiniband-04.txt, April, 2003. 116 7. Author's Address 118 Kanoj Sarcar 119 Sun Microsystems, Inc. 120 14 Network Circle 121 Bldg 14, MPK14-333 122 Menlo Park, CA 94025 124 Phone: 1-650-786-4785 125 Email: kanoj.sarcar@sun.com 127 8. Intellectual Property Statement 129 The IETF takes no position regarding the validity or scope of any 130 intellectual property or other rights that might be claimed to 131 pertain to the implementation or use of the technology described in 132 this document or the extent to which any license under such rights 133 might or might not be available; neither does it represent that it 134 has made any effort to identify any such rights. Information on the 135 IETF's procedures with respect to rights in standards-track and 136 standards-related documentation can be found in BCP-11. Copies of 137 claims of rights made available for publication and any assurances of 138 licenses to be made available, or the result of an attempt made to 139 obtain a general license or permission for the use of such 140 proprietary rights by implementors or users of this specification can 141 be obtained from the IETF Secretariat. 143 The IETF invites any interested party to bring to its attention any 144 copyrights, patents or patent applications, or other proprietary 145 rights which may cover technology that may be required to practice 146 this standard. Please address the information to the IETF Executive 147 Director. 149 9. Full Copyright Statement 151 Copyright (C) The Internet Society (2003). All Rights Reserved. 153 This document and translations of it may be copied and 154 furnished to others, and derivative works that comment on or 155 otherwise explain it or assist in its implmentation may be 156 prepared, copied, published and distributed, in whole or in 157 part, without restriction of any kind, provided that the above 158 copyright notice and this paragraph are included on all such 159 copies and derivative works. However, this document itself may 160 not be modified in any way, such as by removing the copyright 161 notice or references to the Internet Society or other Internet 162 organizations, except as needed for the purpose of developing 163 Internet standards in which case the procedures for copyrights 164 defined in the Internet Standards process must be followed, or 165 as required to translate it into languages other than English. 167 The limited permissions granted above are perpetual and will 168 not be revoked by the Internet Society or its successors or 169 assigns. 171 This document and the information contained herein is provided 172 on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 173 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 174 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE 175 OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY 176 IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 177 PARTICULAR PURPOSE.