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