idnits 2.17.1 draft-ietf-rmonmib-pi-ipv6-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: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Missing reference section? 'RFC2026' on line 263 looks like a reference -- Missing reference section? 'RFC3410' on line 285 looks like a reference -- Missing reference section? 'RFC2578' on line 246 looks like a reference -- Missing reference section? 'RFC2579' on line 250 looks like a reference -- Missing reference section? 'RFC2580' on line 254 looks like a reference -- Missing reference section? 'RFC2119' on line 266 looks like a reference -- Missing reference section? 'RFC2896' on line 278 looks like a reference -- Missing reference section? 'RFC2895' on line 258 looks like a reference -- Missing reference section? 'RFC3032' on line 281 looks like a reference -- Missing reference section? 'RFC2460' on line 269 looks like a reference -- Missing reference section? 'RFC2473' on line 275 looks like a reference -- Missing reference section? 'RFC2463' on line 272 looks like a reference Summary: 5 errors (**), 0 flaws (~~), 2 warnings (==), 14 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft E. Stephan 2 France Telecom R&D 3 J. Palet 4 Consulintel 5 draft-ietf-rmonmib-pi-ipv6-01.txt November, 2003 6 Category: Informational 8 RMON Protocol Identifiers for IPv6 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of Section 10 of RFC 2026 [RFC2026]. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that other 17 groups may also distribute working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet- Drafts as reference 21 material or to cite them other than as "work in progress." 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt. 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 Abstract 31 This memo defines basic protocol identifiers for IP version 6 and sub 32 IP protocols. 34 Table of Contents 36 1. The Internet-Standard Management Framework..................2 37 2. Terms.......................................................2 38 3. Overview....................................................2 39 4. Relationship to the Remote Network Monitoring MIB...........2 40 5. MPLS layer protocol identifiers.............................2 41 6. IPv6 Protocols..............................................3 42 7. Intellectual Property.......................................5 43 8. Normative References........................................5 44 9. Informative References......................................6 45 10. Security Considerations.....................................6 46 11. Authors' Addresses..........................................6 47 12. Full Copyright Statement....................................7 49 1. The Internet-Standard Management Framework 51 For a detailed overview of the documents that describe the current 52 Internet-Standard Management Framework, please refer to section 7 of 53 RFC 3410 [RFC3410]. Managed objects are accessed via a virtual 54 information store, termed the Management Information Base or MIB. 55 MIB objects are generally accessed through the Simple Network 56 Management Protocol (SNMP). Objects in the MIB are defined using the 57 mechanisms defined in the Structure of Management Information (SMI). 58 This memo specifies a MIB module that is compliant to the SMIv2, 59 which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 60 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 62 2. Terms 64 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 65 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 66 document are to be interpreted as described in BCP 14, RFC 2119 67 [RFC2119]. 69 3. Overview 71 This memo defines basic protocol identifiers for IP version 6 and sub 72 IP protocols. 74 The "Remote Network Monitoring MIB Protocol Identifier Macros" 75 [RFC2896], defines various protocol identifiers. The syntax of the 76 protocol identifier descriptor is defined in the RMON Protocol 77 Identifier Reference [RFC2895]. The reader should be familiar with 78 these documents. 80 The intend of this document is not to adapt each protocol identifier 81 defined in the RFC 2895 and in the RFC 2896 to IP version 6, but to 82 define protocol identifiers for IP version 6 protocols and for sub IP 83 protocols. 85 4. Relationship to the Remote Network Monitoring MIB 87 RMON MIB implementations use protocol identifiers to describe 88 unambiguous capabilities in protocolDirTable entries. 90 5. MPLS layer protocol identifiers 92 There is a need to define protocol identifiers for MPLS to provide 93 unambiguous names to distinguish a trunk from a LSP, an IPv4 LSP from 94 an IPv6 one. 96 -- MPLS unicast 97 mplsu PROTOCOL-IDENTIFIER 98 PARAMETERS { } 99 ATTRIBUTES { } 100 DESCRIPTION 101 "MPLS Label Stack Encoding." 102 CHILDREN 103 "Children of MPLS are not systematically identifiable. " 104 REFERENCE 105 "RFC 3032, MPLS Label Stack Encoding [RFC3032]." 106 ::= { 107 ether2 0x8847, -- RFC 3032 section 5 108 snap 0x8847, 109 802-1Q 0x8847, 110 ppp 0x0281, 111 } 113 -- MPLS multicast 115 mplsm PROTOCOL-IDENTIFIER 116 PARAMETERS { } 117 ATTRIBUTES { } 118 DESCRIPTION 119 "MPLS Label Stack Encoding." 120 CHILDREN 121 "Children of MPLS are not systematically identifiable." 122 REFERENCE 123 "RFC 3032, MPLS Label Stack Encoding [RFC3032]." 124 ::= { 125 ether2 0x8848, -- RFC 3032 section 5 126 snap 0x8848, 127 802-1Q 0x8848, 128 ppp 0x0283, 129 } 131 6. IPv6 Protocols 133 ip6 PROTOCOL-IDENTIFIER 134 PARAMETERS {} 135 ATTRIBUTES {} 136 DESCRIPTION 137 "The protocol identifiers for the Internet Protocol, Version 6 138 [RFC2460]." 139 CHILDREN 140 "Children of 'ip6' are selected by the value in the Protocol 141 field (one octet), as defined in the PROTOCOL NUMBERS table 142 within the Assigned Numbers Document. 144 The value of the Protocol field is encoded in an octet string as 145 [ 0.0.0.a ], where 'a' is the protocol field. 147 Children of 'ip6' are encoded as [ 0.0.0.a ], and named as 'ip6 148 a' where 'a' is the protocol field value. For example, a 149 protocolDirID-fragment value of: 150 0.0.0.1.0.0.0.41.0.0.0.58 152 defines an encapsulation of IPv6-ICMP (ether2.ip6.icmp6)" 153 ADDRESS-FORMAT 154 "16 octets of the IPv6 address, in network byte order. Each ip 155 packet contains two addresses, the source address and the 156 destination address." 157 DECODING 158 "Note: ether2.ip.ipip6.udp is a different protocolDirID than 159 ether2.ip6.udp, as identified in the protocolDirTable. As such, 160 two different local protocol index values will be assigned by 161 the agent. E.g. (full INDEX values shown): 162 ether2.ip.ipip6.udp = 163 16.0.0.0.1.0.0.8.0.0.0.0.41.0.0.0.17.4.0.0.0.0 164 ether2.ip6.udp = 165 12.0.0.0.1.0.0.0.41.0.0.0.17.3.0.0.0 " 166 REFERENCE 168 "RFC 2460 [RFC2460] defines the Internet Protocol version 6; The 169 following URL defines the authoritative repository for the 170 PROTOCOL NUMBERS Table: 172 ftp://ftp.isi.edu/in-notes/iana/assignments/protocol-numbers" 173 ::= { 174 ether2 0x86DD, 175 802-1Q 0x86DD, 176 mplsu 41, 177 mplsm 41 178 } 180 ipip6 PROTOCOL-IDENTIFIER 181 PARAMETERS { } 182 ATTRIBUTES { 184 } 185 DESCRIPTION 186 "IPv6 in IPv4 Tunneling" 187 CHILDREN 188 "Children of 'ipip6' are selected and encoded in the same manner 189 as children of ip6." 190 ADDRESS-FORMAT 191 "The 'ipip6' address format is the same as the IPv6 address 192 format." 193 DECODING 194 "Note: ether2.ip.ipip6.udp is a different protocolDirID than 195 ether2.ip6.udp, as identified in the protocolDirTable. As such, 196 two different local protocol index values will be assigned by 197 the agent. E.g. (full INDEX values shown): 198 ether2.ip.ipip6.udp = 199 16.0.0.0.1.0.0.8.0.0.0.0.41.0.0.0.17.4.0.0.0.0 200 ether2.ip6.udp = 201 12.0.0.0.1.0.0.0.41.0.0.0.17.3.0.0.0 " 202 REFERENCE 203 "RFC 2473 [RFC2473] defines Generic Packet Tunneling in IPv6 204 Specification." 205 ::= { 206 ip 41 207 } 209 icmp6 PROTOCOL-IDENTIFIER 210 PARAMETERS { } 211 ATTRIBUTES { } 212 DESCRIPTION 213 "Internet Message Control Protocol for IP Version 6" 214 REFERENCE 215 "RFC 2463 [RFC2463] Internet Control Message Protocol (ICMPv6) 216 for the Internet Protocol Version 6 (IPv6) Specification " 217 ::= { 218 ip6 58, 219 ipip6 58 220 } 222 7. Intellectual Property 224 The IETF takes no position regarding the validity or scope of any 225 intellectual property or other rights that might be claimed to 226 pertain to the implementation or use of the technology described in 227 this document or the extent to which any license under such rights 228 might or might not be available; neither does it represent that it 229 has made any effort to identify any such rights. Information on the 230 IETF's procedures with respect to rights in standards-track and 231 standards-related documentation can be found in BCP-11. Copies of 232 claims of rights made available for publication and any assurances of 233 licenses to be made available, or the result of an attempt made to 234 obtain a general license or permission for the use of such 235 proprietary rights by implementors or users of this specification can 236 be obtained from the IETF Secretariat. 238 The IETF invites any interested party to bring to its attention any 239 copyrights, patents or patent applications, or other proprietary 240 rights which may cover technology that may be required to practice 241 this standard. Please address the information to the IETF Executive 242 Director. 244 8. Normative References 246 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 247 Rose, M. and S. Waldbusser, "Structure of Management Information 248 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 250 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 251 Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 252 58, RFC 2579, April 1999. 254 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 255 Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", 256 STD 58, RFC 2580, April 1999. 258 [RFC2895] Bierman, A., Bucci, C. and R. Iddon, "Remote Network 259 Monitoring MIB Protocol Identifiers", RFC 2895, August 2000. 261 9. Informative References 263 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 264 3", BCP 9, RFC 2026, October 1996. 266 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 267 Requirement Levels", BCP 14, RFC 2119, March 1997. 269 [RFC2460] Deering, S and R. Hinden, " Internet Protocol, Version 6 270 (IPv6) Specification", RFC 2460, December 1998. 272 [RFC2463] Conta, A. and S. Deering, "ICMP for the Internet Protocol 273 Version 6 (IPv6)", RFC 2463, December 1998. 275 [RFC2473] Conta, A. and S. Deering, "Generic Packet Tunneling in IPv6 276 Specification", RFC 2473, December 1998. 278 [RFC2896] Bierman, A., Bucci, C. and R. Iddon, "Remote Network 279 Monitoring MIB Protocol Identifier Macros", RFC 2896, August 2000. 281 [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., 282 Farinacci, D., Li, T. and A. Conta, "MPLS Label Stack Encoding", 283 RFC 3032, January 2001. 285 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 286 "Introduction and Applicability Statements for Internet-Standard 287 Management Framework", RFC 3410, December 2002. 289 10. Security Considerations 291 This memo does not specify metrics implementation nor measurements 292 implementation, so it does not directly affect the security of the 293 Internet nor of applications that run on the Internet. However, usage 294 of protocol identifiers to describe measurement configurations must 295 be mindful of security and privacy concerns. 297 11. Authors' Addresses 298 Emile Stephan 299 France Telecom R & D 300 2 avenue Pierre Marzin 301 F-22307 Lannion cedex 303 Phone: +33 2 96 05 11 11 304 Fax: +33 2 96 05 18 52 305 Email: emile.stephan@francetelecom.com 307 Jordi Palet 308 Consulintel, IPv6 R&D 309 San Jose Artesano, 1 310 E-28108 - Alcobendas 311 Madrid, Spain 313 Phone: +34 91 151 81 99 314 Fax: +34 91 151 81 98 315 Email: jordi.palet@consulintel.es 317 12. Full Copyright Statement 319 Copyright (C) The Internet Society (2003). All Rights Reserved. 321 This document and translations of it may be copied and furnished to 322 others, and derivative works that comment on or otherwise explain it 323 or assist its implementation may be prepared, copied, published and 324 distributed, in whole or in part, without restriction of any kind, 325 provided that the above copyright notice and this paragraph are 326 included on all such copies and derivative works. However, this 327 document itself may not be modified in any way, such as by removing 328 the copyright notice or references to the Internet Society or other 329 Internet organizations, except as needed for the purpose of 330 developing Internet standards in which case the procedures for 331 copyrights defined in the Internet Standards process must be 332 followed, or as required to translate it into languages other than 333 English. 335 The limited permissions granted above are perpetual and will not be 336 revoked by the Internet Society or its successors or assigns. 338 This document and the information contained herein is provided on an 339 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 340 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 341 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 342 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 343 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.