idnits 2.17.1 draft-ietf-rmonmib-pi-ipv6-03.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 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 normative reference: RFC 2460 (Obsoleted by RFC 8200) ** Obsolete normative reference: RFC 2463 (Obsoleted by RFC 4443) Summary: 5 errors (**), 0 flaws (~~), 2 warnings (==), 2 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-03.txt March, 2004 7 Category: Informational 9 RMON Protocol Identifiers for IPv6 and MPLS 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 33 MPLS protocols. 35 Table of Contents 37 1. The Internet-Standard Management Framework..................2 38 2. Overview....................................................2 39 3. Relationship to the Remote Network Monitoring MIB...........2 40 4. MPLS layer protocol identifiers.............................2 41 5. IPv6 Protocols..............................................3 42 6. Intellectual Property.......................................5 43 7. Normative References........................................5 44 8. Informative References......................................6 45 9. Security Considerations.....................................6 46 10. Authors' Addresses..........................................6 47 11. 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. Overview 64 This memo defines basic protocol identifiers for IP version 6 and 65 MPLS protocols. 67 The "Remote Network Monitoring MIB Protocol Identifier Macros" 68 [RFC2896], defines various protocol identifiers. The syntax of the 69 protocol identifier descriptor is defined in the RMON Protocol 70 Identifier Reference [RFC2895]. The reader should be familiar with 71 these documents. 73 The intent of this document is not to adapt each protocol identifier 74 defined in the RFC 2895 and in the RFC 2896 to IP version 6, but to 75 define protocol identifiers for IP version 6 protocols and for MPLS 76 protocol. 78 3. Relationship to the Remote Network Monitoring MIB 80 RMON MIB implementations use protocol identifiers to describe 81 unambiguous capabilities in protocolDirTable entries. 83 4. MPLS layer protocol identifiers 85 This section defines protocol identifiers for MPLS with unambiguous 86 names to distinguish MPLS Unicast from MPLS Multicast. 88 -- MPLS unicast 89 mplsu PROTOCOL-IDENTIFIER 90 PARAMETERS { } 91 ATTRIBUTES { } 92 DESCRIPTION 93 "MPLS Label Stack Encoding." 95 CHILDREN 96 "Children of MPLS are not systematically identifiable. " 97 REFERENCE 98 "RFC 3032, MPLS Label Stack Encoding [RFC3032]." 99 ::= { 100 ether2 0x8847, -- RFC 3032 section 5 101 snap 0x8847, 102 802-1Q 0x8847, 103 ppp 0x0281, -- RFC 3032 section 4.3 104 } 106 -- MPLS multicast 108 mplsm PROTOCOL-IDENTIFIER 109 PARAMETERS { } 110 ATTRIBUTES { } 111 DESCRIPTION 112 "MPLS Label Stack Encoding." 113 CHILDREN 114 "Children of MPLS are not systematically identifiable." 115 REFERENCE 116 "RFC 3032, MPLS Label Stack Encoding [RFC3032]." 117 ::= { 118 ether2 0x8848, -- RFC 3032 section 5 119 snap 0x8848, 120 802-1Q 0x8848, 121 ppp 0x0283, -- RFC 3032 section 4.3 122 } 124 5. IPv6 Protocols 126 ip6 PROTOCOL-IDENTIFIER 127 PARAMETERS {} 128 ATTRIBUTES {} 129 DESCRIPTION 130 "The protocol identifiers for the Internet Protocol, Version 6 131 [RFC2460]." 132 CHILDREN 133 "Children of 'ip6' are selected by the value in the Protocol 134 field (one octet), as defined in the PROTOCOL NUMBERS table 135 within the Assigned Numbers Document. 137 The value of the Protocol field is encoded in an octet string as 138 [ 0.0.0.a ], where 'a' is the protocol field. 140 Children of 'ip6' are encoded as [ 0.0.0.a ], and named as 'ip6 141 a' where 'a' is the protocol field value. For example, a 142 protocolDirID-fragment value of: 143 0.0.0.1.0.0.0.41.0.0.0.58 145 defines an encapsulation of IPv6-ICMP (ether2.ip6.icmp6)" 146 ADDRESS-FORMAT 147 "16 octets of the IPv6 address, in network byte order. Each ip 148 packet contains two addresses, the source address and the 149 destination address." 150 DECODING 151 "Note: ether2.ip.ipip6.udp is a different protocolDirID than 152 ether2.ip6.udp, as identified in the protocolDirTable. As such, 153 two different local protocol index values will be assigned by 154 the agent. E.g. (full INDEX values shown): 155 ether2.ip.ipip6.udp = 156 16.0.0.0.1.0.0.8.0.0.0.0.41.0.0.0.17.4.0.0.0.0 157 ether2.ip6.udp = 158 12.0.0.0.1.0.0.0.41.0.0.0.17.3.0.0.0 " 159 REFERENCE 161 "RFC 2460 [RFC2460] defines the Internet Protocol version 6; The 162 following URL defines the authoritative repository for the 163 PROTOCOL NUMBERS Table: 165 http://www.iana.org/assignments/protocol-numbers" 166 ::= { 167 ether2 0x86DD, 168 802-1Q 0x86DD, 169 mplsu 41, 170 mplsm 41 171 } 173 ipip6 PROTOCOL-IDENTIFIER 174 PARAMETERS { } 175 ATTRIBUTES { 177 } 178 DESCRIPTION 179 "IPv6 in IPv4 Tunneling" 180 CHILDREN 181 "Children of 'ipip6' are selected and encoded in the same manner 182 as children of ip6." 183 ADDRESS-FORMAT 184 "The 'ipip6' address format is the same as the IPv6 address 185 format." 186 DECODING 187 "Note: ether2.ip.ipip6.udp is a different protocolDirID than 188 ether2.ip6.udp, as identified in the protocolDirTable. As such, 189 two different local protocol index values will be assigned by 190 the agent. E.g. (full INDEX values shown): 191 ether2.ip.ipip6.udp = 192 16.0.0.0.1.0.0.8.0.0.0.0.41.0.0.0.17.4.0.0.0.0 193 ether2.ip6.udp = 194 12.0.0.0.1.0.0.0.41.0.0.0.17.3.0.0.0 " 195 REFERENCE 196 "RFC 2473 [RFC2473] defines Generic Packet Tunneling in IPv6 197 Specification." 198 ::= { 199 ip 41 200 } 202 icmp6 PROTOCOL-IDENTIFIER 203 PARAMETERS { } 204 ATTRIBUTES { } 205 DESCRIPTION 206 "Internet Message Control Protocol for IP Version 6" 207 REFERENCE 208 "RFC 2463 [RFC2463] Internet Control Message Protocol (ICMPv6) 209 for the Internet Protocol Version 6 (IPv6) Specification " 210 ::= { 211 ip6 58, 212 ipip6 58 213 } 215 6. Intellectual Property 217 The IETF takes no position regarding the validity or scope of any 218 intellectual property or other rights that might be claimed to 219 pertain to the implementation or use of the technology described in 220 this document or the extent to which any license under such rights 221 might or might not be available; neither does it represent that it 222 has made any effort to identify any such rights. Information on the 223 IETF's procedures with respect to rights in standards-track and 224 standards-related documentation can be found in BCP-11. Copies of 225 claims of rights made available for publication and any assurances of 226 licenses to be made available, or the result of an attempt made to 227 obtain a general license or permission for the use of such 228 proprietary rights by implementors or users of this specification can 229 be obtained from the IETF Secretariat. 231 The IETF invites any interested party to bring to its attention any 232 copyrights, patents or patent applications, or other proprietary 233 rights which may cover technology that may be required to practice 234 this standard. Please address the information to the IETF Executive 235 Director. 237 7. Normative References 239 [RFC2460] Deering, S and R. Hinden, " Internet Protocol, Version 6 240 (IPv6) Specification", RFC 2460, December 1998. 242 [RFC2463] Conta, A. and S. Deering, "ICMP for the Internet Protocol 243 Version 6 (IPv6)", RFC 2463, December 1998. 245 [RFC2473] Conta, A. and S. Deering, "Generic Packet Tunneling in IPv6 246 Specification", RFC 2473, December 1998. 248 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 249 Rose, M. and S. Waldbusser, "Structure of Management Information 250 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 252 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 253 Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 254 58, RFC 2579, April 1999. 256 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 257 Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", 258 STD 58, RFC 2580, April 1999. 260 [RFC2895] Bierman, A., Bucci, C. and R. Iddon, "Remote Network 261 Monitoring MIB Protocol Identifiers", RFC 2895, August 2000. 263 [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., 264 Farinacci, D., Li, T. and A. Conta, "MPLS Label Stack Encoding", 265 RFC 3032, January 2001. 267 8. Informative References 269 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 270 3", BCP 9, RFC 2026, October 1996. 272 [RFC2896] Bierman, A., Bucci, C. and R. Iddon, "Remote Network 273 Monitoring MIB Protocol Identifier Macros", RFC 2896, August 2000. 275 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 276 "Introduction and Applicability Statements for Internet-Standard 277 Management Framework", RFC 3410, December 2002. 279 9. Security Considerations 281 This document contains textual descriptions of well-known networking 282 protocols, not the definition of any networking behavior. As such, 283 no security considerations are raised by its publication. 285 10. Authors' Addresses 287 Emile Stephan 288 France Telecom R & D 289 2 avenue Pierre Marzin 290 F-22307 Lannion cedex 291 Phone: +33 2 96 05 11 11 292 Fax: +33 2 96 05 18 52 293 Email: emile.stephan@francetelecom.com 295 Jordi Palet 296 Consulintel, IPv6 R&D 297 San Jose Artesano, 1 298 E-28108 - Alcobendas 299 Madrid, Spain 301 Phone: +34 91 151 81 99 302 Fax: +34 91 151 81 98 303 Email: jordi.palet@consulintel.es 305 11. Full Copyright Statement 307 Copyright (C) The Internet Society (2003). All Rights Reserved. 309 This document and translations of it may be copied and furnished to 310 others, and derivative works that comment on or otherwise explain it 311 or assist its implementation may be prepared, copied, published and 312 distributed, in whole or in part, without restriction of any kind, 313 provided that the above copyright notice and this paragraph are 314 included on all such copies and derivative works. However, this 315 document itself may not be modified in any way, such as by removing 316 the copyright notice or references to the Internet Society or other 317 Internet organizations, except as needed for the purpose of 318 developing Internet standards in which case the procedures for 319 copyrights defined in the Internet Standards process must be 320 followed, or as required to translate it into languages other than 321 English. 323 The limited permissions granted above are perpetual and will not be 324 revoked by the Internet Society or its successors or assigns. 326 This document and the information contained herein is provided on an 327 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 328 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 329 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 330 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 331 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 333 Acknowledgement 335 The authors would like to acknowledge the European Commission support 336 in the co-funding of the 6QM project, where this work is being 337 developed.