idnits 2.17.1 draft-ietf-l3vpn-tc-mib-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 18. -- Found old boilerplate from RFC 3978, Section 5.5 on line 265. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 236. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 243. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 249. ** The document seems to lack an RFC 3978 Section 5.4 (updated by RFC 4748) Copyright Line. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to 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 Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (April 2005) is 6922 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) No issues found here. Summary: 4 errors (**), 0 flaws (~~), 1 warning (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT Benson Schliesser 2 draft-ietf-l3vpn-tc-mib-06.txt SAVVIS Communications 3 Expires: October 2005 4 Thomas D. Nadeau 5 Cisco Systems, Inc. 7 April 2005 9 Definition of Textual Conventions for 10 Virtual Private Network (VPN) Management 12 Status of this Memo 14 By submitting this Internet-Draft, each author represents that 15 any applicable patent or other IPR claims of which he or she is 16 aware have been or will be disclosed, and any of which he or she 17 becomes aware will be disclosed, in accordance with Section 6 of 18 BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that other 22 groups may also distribute working documents as Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/1id-abstracts.html 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 Abstract 37 This document describes Textual Conventions used for managing 38 Virtual Private Networks (VPNs). 40 Table of Contents 42 1. Introduction .............................................. 43 1.1 Conventions Used in This Document ......................... 44 2. The Internet-Standard Management Framework ................ 45 3. VPN-TC-STD-MIB ............................................ 47 3.1 Description ............................................... 48 3.2 Definitions ............................................... 49 4. Security Considerations ................................... 50 5. References ................................................ 51 5.1 Normative References ...................................... 52 5.2 Informative References .................................... 53 6. Authors Addresses ......................................... 54 7. Intellectual Property Considerations ...................... 55 8. Full Copyright Statement .................................. 56 9. IANA Considerations for VPN-TC-STD-MIB..................... 58 1. Introduction 60 This memo defines a portion of the Management Information Base (MIB) 61 for use with network management protocols in the Internet community. 62 In particular, it defines Textual Conventions used in VPNs and IETF 63 VPN-related MIBs. 65 1.1 Conventions Used in This Document 67 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 68 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 69 this document are to be interpreted as described in RFC-2119 70 [RFC2119]. 72 2. 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]. 78 Managed objects are accessed via a virtual information store, termed 79 the Management Information Base or MIB. MIB objects are generally 80 accessed through the Simple Network Management Protocol (SNMP). 81 Objects in the MIB are defined using the mechanisms defined in the 82 Structure of Management Information (SMI). This memo specifies a 83 MIB module that is compliant to the SMIv2, which is described in 84 STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, 85 RFC 2580 [RFC2580]. 87 3. VPN-TC-STD-MIB 89 3.1 Description 91 The VPN-TC-STD-MIB defines a Textual Convention for the Global VPN 92 Identifier, or VPN-ID, as specified in [RFC2685]. The purpose of a 93 VPN-ID is to uniquely identify a VPN. It MUST be 7 octets in length, 94 and SHOULD be comprised of a 3 octet Organizationally Unique 95 Identifier (OUI) which uniquely identifies the VPN Authority, 96 followed by a 4 octet value assigned by the VPN Authority that 97 uniquely identifies the VPN within the context of the OUI. 99 3.2 Definitions 101 VPN-TC-STD-MIB DEFINITIONS ::= BEGIN 103 IMPORTS 104 MODULE-IDENTITY, mib-2 105 FROM SNMPv2-SMI 107 TEXTUAL-CONVENTION 108 FROM SNMPv2-TC; 110 vpnTcMIB MODULE-IDENTITY 111 LAST-UPDATED "200504011200Z" -- 01 April 2005 12:00:00 GMT 112 ORGANIZATION 113 "Layer 3 Virtual Private Networks (L3VPN) Working Group." 114 CONTACT-INFO 115 "Benson Schliesser 116 bensons@savvis.net 118 Thomas D. Nadeau 119 tnadeau@cisco.com 121 This TC MIB is a product of the PPVPN 122 http://www.ietf.org/html.charters/ppvpn-charter.html 123 and subsequently the L3VPN 124 http://www.ietf.org/html.charters/l3vpn-charter.html 125 working groups. 127 Comments and discussion should be directed to l3vpn@ietf.org" 128 DESCRIPTION 129 "This MIB contains TCs for VPNs. 131 Copyright (C) The Internet Society (2004). This version 132 of this MIB module is part of RFC yyyy; see the RFC 133 itself for full legal notices." 134 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 135 -- Revision history. 136 REVISION "200504011200Z" -- 01 April 2005 12:00:00 GMT 137 DESCRIPTION "Initial version, published as RFC yyyy." 138 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 139 ::= { mib-2 XXX } 140 -- RFC Ed.: replace XXX with IANA-assigned number & remove this note 142 -- definition of textual conventions 143 VPNId ::= TEXTUAL-CONVENTION 144 STATUS current 145 DESCRIPTION 146 "The purpose of a VPN-ID is to uniquely identify a VPN. 147 The Global VPN Identifier format is: 148 3 octet VPN Authority, Organizationally Unique Identifier 149 followed by 4 octet VPN index identifying VPN according 150 to OUI" 151 REFERENCE 152 "Fox, B. and Gleeson, B., 'Virtual Private Networks 153 Identifier', RFC 2685, September 1999." 154 SYNTAX OCTET STRING (SIZE (7)) 156 VPNIdOrZero ::= TEXTUAL-CONVENTION 157 STATUS current 158 DESCRIPTION 159 "This textual convention is an extension of the 160 VPNId textual convention which defines non-zero-length 161 OCTET STRING to identify a physical entity. This extension 162 permits the additional value of a zero-length OCTET STRING. 163 The semantics of the value zero-length OCTET STRING are 164 object-specific and must therefore be defined 165 as part of the description of any object which uses this 166 syntax. Examples of the usage of this extension are 167 situations where none or all VPN IDs need to be 168 referenced." 169 SYNTAX OCTET STRING (SIZE (0 | 7)) 171 END 173 4. Security Considerations 175 This memo defines textual conventions and object identities 176 for use in VPN MIB modules. Security issues for these MIB 177 modules are addressed in the memos defining those modules. 179 5. References 181 5.1 Normative References 183 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 184 Requirement Levels", BCP 14, RFC 2119, March 1997. 186 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 187 Rose, M. and S. Waldbusser, "Structure of Management 188 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 189 1999. 191 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 192 Rose, M. and S. Waldbusser, "Textual Conventions for 193 SMIv2", STD 58, RFC 2579, April 1999. 195 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 196 Rose, M. and S. Waldbusser, "Conformance Statements for 197 SMIv2", STD 58, RFC 2580, April 1999. 199 5.2 Informative References 201 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 202 "Introduction and Applicability Statements for 203 Internet-Standard Management Framework", RFC 3410, 204 December 2002. 206 [RFC2685] Fox, B. and Gleeson, B., "Virtual Private Networks 207 Identifier", RFC 2685, September 1999. 209 6. Authors' Addresses 211 Benson Schliesser 212 SAVVIS Communications 213 1 Savvis Parkway 214 Saint Louis, MO 63017 215 USA 216 Phone: +1-314-628-7036 217 Email: bensons@savvis.net 219 Thomas D. Nadeau 220 Cisco Systems, Inc. 221 300 Beaverbrook Drive 222 Boxborough, MA 223 USA 224 Phone: +1-978-936-1470 225 Email: tnadeau@cisco.com 227 7. Intellectual Property Considerations 229 The IETF takes no position regarding the validity or scope of any 230 Intellectual Property Rights or other rights that might be claimed to 231 pertain to the implementation or use of the technology described in 232 this document or the extent to which any license under such rights 233 might or might not be available; nor does it represent that it has 234 made any independent effort to identify any such rights. Information 235 on the procedures with respect to rights in RFC documents can be 236 found in BCP 78 and BCP 79. 238 Copies of IPR disclosures made to the IETF Secretariat and any 239 assurances of licenses to be made available, or the result of an 240 attempt made to obtain a general license or permission for the use of 241 such proprietary rights by implementers or users of this 242 specification can be obtained from the IETF on-line IPR repository at 243 http://www.ietf.org/ipr. 245 The IETF invites any interested party to bring to its attention any 246 copyrights, patents or patent applications, or other proprietary 247 rights that may cover technology that may be required to implement 248 this standard. Please address the information to the IETF at ietf- 249 ipr@ietf.org. 251 8. Full Copyright Statement 253 Copyright (C) The Internet Society (2005). This document is 254 subject to the rights, licenses and restrictions contained in BCP 255 78, and except as set forth therein, the authors retain all their 256 rights. 258 This document and the information contained herein are provided 259 on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 260 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND 261 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, 262 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 263 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 264 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 265 PARTICULAR PURPOSE. 267 9. IANA Considerations for VPN-TC-STD-MIB 269 The IANA is requested to assign { mib-2 XXX } to the 270 VPN-TC-STD-MIB module specified in this document.