idnits 2.17.1 draft-ietf-rmonmib-pi-ipv6-04.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 page length should not exceed 58 lines per page, but there was 10 longer pages, the longest (page 7) being 72 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 10 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 25 instances of too long lines in the document, the longest one being 14 characters in excess of 72. == 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.) -- The document date (May 24, 2004) is 7277 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC2021' is defined on line 293, but no explicit reference was found in the text == Unused Reference: 'RFC2026' is defined on line 297, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2460 (Obsoleted by RFC 8200) ** Obsolete normative reference: RFC 2463 (Obsoleted by RFC 4443) -- Obsolete informational reference (is this intentional?): RFC 2021 (Obsoleted by RFC 4502) Summary: 4 errors (**), 0 flaws (~~), 6 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group E. Stephan 3 Internet-Draft France Telecom R&D 4 Category: Informational J. Palet 5 Expires: November 22, 2004 Consulintel 6 May 24, 2004 8 Remote Network Monitoring (RMON) Protocol Identifiers for IPv6 and 9 Multi Protocol Label Switching (MPLS) 10 draft-ietf-rmonmib-pi-ipv6-04.txt 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC2026. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that other 19 groups may also distribute working documents as Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at http:// 27 www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on November 22, 2004. 34 Copyright Notice 36 Copyright (C) The Internet Society (2004). All Rights Reserved. 38 Abstract 40 This memo defines additional (to those in RFC2896) protocol 41 identifier examples for IP version 6 and MPLS protocols. These can be 42 used to produce valid protocolDirTable INDEX encodings, as defined by 43 the Remote Network Monitoring MIB (Management Information Base) 44 Version 2 (RFC2021) and the RMON Protocol Identifier Reference 45 (RFC2895). 47 This document contains additional (to those in RFC2896) protocol 48 identifier macros for well-known protocols. A conformant 49 implementation of the RMON-2 MIB (RFC2021) can be accomplished 50 without the use of these protocol identifiers, and accordingly, this 51 document does not specify any IETF standard. It is published to 52 encourage better interoperability between RMON-2 agent 53 implementations, by providing RMON related IPv6 and MPLS protocol 54 information. 56 Table of Contents 58 1. The Internet-Standard Management Framework . . . . . . . . . . 3 59 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 3. Relationship to the Remote Network Monitoring MIB . . . . . . 3 61 4. MPLS layer protocol identifiers . . . . . . . . . . . . . . . 3 62 5. IPv6 Protocols . . . . . . . . . . . . . . . . . . . . . . . . 4 63 6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 64 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 65 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 66 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 67 9.1 Normative References . . . . . . . . . . . . . . . . . . . . 7 68 9.2 Informative References . . . . . . . . . . . . . . . . . . . 7 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 8 70 Intellectual Property and Copyright Statements . . . . . . . . 9 72 1. The Internet-Standard Management Framework 74 For a detailed overview of the documents that describe the current 75 Internet-Standard Management Framework, please refer to section 7 of 76 RFC 3410 [RFC3410]. Managed objects are accessed via a virtual 77 information store, termed the Management Information Base or MIB. MIB 78 objects are generally accessed through the Simple Network Management 79 Protocol (SNMP). Objects in the MIB are defined using the mechanisms 80 defined in the Structure of Management Information (SMI). This memo 81 specifies a MIB module that is compliant to the SMIv2, which is 82 described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] 83 and STD 58, RFC 2580 [RFC2580]. 85 2. Overview 87 This memo defines basic protocol identifiers for IP version 6 and 88 MPLS protocols. 90 The "Remote Network Monitoring MIB Protocol Identifier Macros" 91 [RFC2896], defines various protocol identifiers. The syntax of the 92 protocol identifier descriptor is defined in the RMON Protocol 93 Identifier Reference [RFC2895]. The reader should be familiar with 94 these documents. 96 The intent of this document is not to adapt each protocol identifier 97 defined in the RFC 2895 and in the RFC 2896 to IP version 6, but to 98 define protocol identifiers for IP version 6 protocols and for MPLS 99 protocol. 101 3. Relationship to the Remote Network Monitoring MIB 103 RMON MIB implementations use protocol identifiers to describe 104 unambiguous capabilities in protocolDirTable entries. 106 4. MPLS layer protocol identifiers 108 This section defines protocol identifiers for MPLS with unambiguous 109 names to distinguish MPLS Unicast from MPLS Multicast. 111 -- MPLS unicast 113 mplsu PROTOCOL-IDENTIFIER 114 PARAMETERS { } 115 ATTRIBUTES { } 116 DESCRIPTION 117 "MPLS Label Stack Encoding." 119 CHILDREN 120 "Children of MPLS are not systematically identifiable. " 121 REFERENCE 122 "RFC 3032, MPLS Label Stack Encoding [RFC3032]." 123 ::= { 124 ether2 0x8847, -- RFC 3032 section 5 125 snap 0x8847, 126 802-1Q 0x8847, 127 ppp 0x0281, -- RFC 3032 section 4.3 128 } 130 -- MPLS multicast 132 mplsm PROTOCOL-IDENTIFIER 133 PARAMETERS { } 134 ATTRIBUTES { } 135 DESCRIPTION 136 "MPLS Label Stack Encoding." 137 CHILDREN 138 "Children of MPLS are not systematically identifiable." 139 REFERENCE 140 "RFC 3032, MPLS Label Stack Encoding [RFC3032]." 141 ::= { 142 ether2 0x8848, -- RFC 3032 section 5 143 snap 0x8848, 144 802-1Q 0x8848, 145 ppp 0x0283, -- RFC 3032 section 4.3 146 } 148 5. IPv6 Protocols 150 ip6 PROTOCOL-IDENTIFIER 151 PARAMETERS {} 152 ATTRIBUTES {} 153 DESCRIPTION 154 "The protocol identifiers for the Internet Protocol, Version 6 156 [RFC2460]." 157 CHILDREN 158 "Children of 'ip6' are selected by the value in the Protocol 159 field (one octet), as defined in the PROTOCOL NUMBERS table 160 within the Assigned Numbers Document. 162 The value of the Protocol field is encoded in an octet string as 163 [ 0.0.0.a ], where 'a' is the protocol field. 164 Children of 'ip6' are encoded as [ 0.0.0.a ], and named as 'ip6 165 a' where 'a' is the protocol field value. For example, a 166 protocolDirID-fragment value of: 167 0.0.0.1.0.0.0.41.0.0.0.58 169 defines an encapsulation of IPv6-ICMP (ether2.ip6.icmp6)" 170 ADDRESS-FORMAT 171 "16 octets of the IPv6 address, in network byte order. Each ip 172 packet contains two addresses, the source address and the 173 destination address." 174 DECODING 175 "Note: ether2.ip.ipip6.udp is a different protocolDirID than 176 ether2.ip6.udp, as identified in the protocolDirTable. As such, 177 two different local protocol index values will be assigned by 178 the agent. E.g. (full INDEX values shown): 179 ether2.ip.ipip6.udp = 180 16.0.0.0.1.0.0.8.0.0.0.0.41.0.0.0.17.4.0.0.0.0 181 ether2.ip6.udp = 182 12.0.0.0.1.0.0.0.41.0.0.0.17.3.0.0.0 " 183 REFERENCE 185 "RFC 2460 [RFC2460] defines the Internet Protocol version 6; The 186 following URL defines the authoritative repository for the 187 PROTOCOL NUMBERS Table: 189 http://www.iana.org/assignments/protocol-numbers" 190 ::= { 191 ether2 0x86DD, 192 802-1Q 0x86DD, 193 mplsu 41, 194 mplsm 41 195 } 197 ipip6 PROTOCOL-IDENTIFIER 198 PARAMETERS { } 199 ATTRIBUTES { 201 } 202 DESCRIPTION 203 "IPv6 in IPv4 Tunneling" 205 CHILDREN 206 "Children of 'ipip6' are selected and encoded in the same manner 207 as children of ip6." 208 ADDRESS-FORMAT 209 "The 'ipip6' address format is the same as the IPv6 address 210 format." 211 DECODING 212 "Note: ether2.ip.ipip6.udp is a different protocolDirID than 213 ether2.ip6.udp, as identified in the protocolDirTable. As such, 214 two different local protocol index values will be assigned by 215 the agent. E.g. (full INDEX values shown): 216 ether2.ip.ipip6.udp = 217 16.0.0.0.1.0.0.8.0.0.0.0.41.0.0.0.17.4.0.0.0.0 218 ether2.ip6.udp = 219 12.0.0.0.1.0.0.0.41.0.0.0.17.3.0.0.0 " 220 REFERENCE 221 "RFC 2473 [RFC2473] defines Generic Packet Tunneling in IPv6 222 Specification." 223 ::= { 224 ip 41 225 } 227 icmp6 PROTOCOL-IDENTIFIER 228 PARAMETERS { } 229 ATTRIBUTES { } 230 DESCRIPTION 231 "Internet Message Control Protocol for IP Version 6" 232 REFERENCE 233 "RFC 2463 [RFC2463] Internet Control Message Protocol (ICMPv6) 234 for the Internet Protocol Version 6 (IPv6) Specification " 235 ::= { 236 ip6 58, 237 ipip6 58 238 } 240 6. Security Considerations 242 This document contains textual descriptions of well-known networking 243 protocols, not the definition of any networking behavior. As such, 244 no security considerations are raised by its publication. 246 7. Acknowledgments 248 The authors would like to acknowledge the European Commission support 249 in the co-funding of the 6QM project, where this work is being 250 developed. 252 8. IANA Considerations 254 There are no IANA considerations for this document. 256 9. References 258 9.1 Normative References 260 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 261 (IPv6) Specification", RFC 2460, December 1998. 263 [RFC2463] Conta, A. and S. Deering, "Internet Control Message 264 Protocol (ICMPv6) for the Internet Protocol Version 6 265 (IPv6) Specification", RFC 2463, December 1998. 267 [RFC2473] Conta, A. and S. Deering, "Generic Packet Tunneling in 268 IPv6 Specification", RFC 2473, December 1998. 270 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 271 McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of 272 Management Information Version 2 (SMIv2)", STD 58, RFC 273 2578, April 1999. 275 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 276 McCloghrie, K., Rose, M. and S. Waldbusser, "Textual 277 Conventions for SMIv2", STD 58, RFC 2579, April 1999. 279 [RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder, 280 "Conformance Statements for SMIv2", STD 58, RFC 2580, 281 April 1999. 283 [RFC2895] Bierman, A., Bucci, C. and R. Iddon, "Remote Network 284 Monitoring MIB Protocol Identifier Reference", RFC 2895, 285 August 2000. 287 [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., 288 Farinacci, D., Li, T. and A. Conta, "MPLS Label Stack 289 Encoding", RFC 3032, January 2001. 291 9.2 Informative References 293 [RFC2021] Waldbusser, S., "Remote Network Monitoring Management 294 Information Base Version 2 using SMIv2", RFC 2021, January 295 1997. 297 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 298 3", BCP 9, RFC 2026, October 1996. 300 [RFC2896] Bierman, A., Bucci, C. and R. Iddon, "Remote Network 301 Monitoring MIB Protocol Identifier Macros", RFC 2896, 302 August 2000. 304 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 305 "Introduction and Applicability Statements for 306 Internet-Standard Management Framework", RFC 3410, 307 December 2002. 309 Authors' Addresses 311 Stephan Emile 312 France Telecom R & D 313 2 avenue Pierre Marzin 314 Lannion, F-22307 316 Fax: +33 2 96 05 18 52 317 EMail: emile.stephan@francetelecom.com 319 Jordi Palet 320 Consulintel, IPv6 R&D 321 San Jose Artesano, 1 322 Alcobendas, Madrid, Spain E-28108 324 Fax: +34 91 151 81 98 325 EMail: jordi.palet@consulintel.es 327 Intellectual Property Statement 329 The IETF takes no position regarding the validity or scope of any 330 intellectual property or other rights that might be claimed to 331 pertain to the implementation or use of the technology described in 332 this document or the extent to which any license under such rights 333 might or might not be available; neither does it represent that it 334 has made any effort to identify any such rights. Information on the 335 IETF's procedures with respect to rights in standards-track and 336 standards-related documentation can be found in BCP-11. Copies of 337 claims of rights made available for publication and any assurances of 338 licenses to be made available, or the result of an attempt made to 339 obtain a general license or permission for the use of such 340 proprietary rights by implementors or users of this specification can 341 be obtained from the IETF Secretariat. 343 The IETF invites any interested party to bring to its attention any 344 copyrights, patents or patent applications, or other proprietary 345 rights which may cover technology that may be required to practice 346 this standard. Please address the information to the IETF Executive 347 Director. 349 Full Copyright Statement 351 Copyright (C) The Internet Society (2004). All Rights Reserved. 353 This document and translations of it may be copied and furnished to 354 others, and derivative works that comment on or otherwise explain it 355 or assist in its implementation may be prepared, copied, published 356 and distributed, in whole or in part, without restriction of any 357 kind, provided that the above copyright notice and this paragraph are 358 included on all such copies and derivative works. However, this 359 document itself may not be modified in any way, such as by removing 360 the copyright notice or references to the Internet Society or other 361 Internet organizations, except as needed for the purpose of 362 developing Internet standards in which case the procedures for 363 copyrights defined in the Internet Standards process must be 364 followed, or as required to translate it into languages other than 365 English. 367 The limited permissions granted above are perpetual and will not be 368 revoked by the Internet Society or its successors or assignees. 370 This document and the information contained herein is provided on an 371 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 372 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 373 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 374 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 375 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 377 Acknowledgment 379 Funding for the RFC Editor function is currently provided by the 380 Internet Society.