idnits 2.17.1 draft-chisholm-netconf-monitoring-00.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 15. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 408. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 419. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 426. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 432. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. 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.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year == Line 295 has weird spacing: '...hat the conte...' == Line 306 has weird spacing: '... it has n...' == 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.) -- The document date (February 25, 2007) is 6267 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) == Unused Reference: 'NETCONF-EVENT' is defined on line 353, but no explicit reference was found in the text == Unused Reference: 'RFC2026' is defined on line 358, but no explicit reference was found in the text == Unused Reference: 'RFC2223' is defined on line 364, but no explicit reference was found in the text ** Obsolete normative reference: RFC 4741 (ref. 'NETCONF') (Obsoleted by RFC 6241) -- No information found for draft-ietf-netconf-notifications - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'NETCONF-EVENT' ** Obsolete normative reference: RFC 2223 (Obsoleted by RFC 7322) -- Possible downref: Non-RFC (?) normative reference: ref. 'XML' Summary: 4 errors (**), 0 flaws (~~), 7 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group S. Chisholm 2 Internet-Draft Nortel 3 Intended status: Standards Track H. Trevino 4 Expires: August 29, 2007 Cisco 5 February 25, 2007 7 NETCONF Monitoring Schema 8 draft-chisholm-netconf-monitoring-00.txt 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on August 29, 2007. 35 Copyright Notice 37 Copyright (C) The IETF Trust (2007). 39 Abstract 41 This document defines Netconf content via XML Schema to be used to 42 monitor the Netconf protocol. It provides information about Netconf 43 sessions and subscriptions. 45 Table of Contents 47 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 48 1.1. Definition of Terms . . . . . . . . . . . . . . . . . . . 3 49 1.2. XML Schema to Monitor Netconf . . . . . . . . . . . . . . 4 50 2. Security Considerations . . . . . . . . . . . . . . . . . . . 9 51 3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 52 4. Normative References . . . . . . . . . . . . . . . . . . . . . 11 53 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 54 Intellectual Property and Copyright Statements . . . . . . . . . . 13 56 1. Introduction 58 [NETCONF] can be conceptually partitioned into four layers: 60 Layer Example 61 +-------------+ +----------------------------------------+ 62 | Content | | Configuration data | 63 +-------------+ +----------------------------------------+ 64 | | 65 +-------------+ +-------------------------------------------+ 66 | Operations | | , | 67 +-------------+ +-------------------------------------------+ 68 | | | 69 +-------------+ +-----------------------------+ | 70 | RPC | | , | | 71 +-------------+ +-----------------------------+ | 72 | | | 73 +-------------+ +------------------------------------------+ 74 | Transport | | BEEP, SSH, SSL, console | 75 | Protocol | | | 76 +-------------+ +------------------------------------------+ 78 This document defines Netconf content via [XML Schema] to be used to 79 monitor the Netconf protocol. It provides information about Netconf 80 sessions and subscriptions. 82 Figure 1 84 1.1. Definition of Terms 86 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 87 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 88 document are to be interpreted as described in [RFC2119]. 90 Element: An [XML] Element. 92 Managed Object: A collection of one of more Elements that define an 93 abstract thing of interest. 95 Subscription: A concept related to the delivery of notifications (if 96 any to send) involving destination and selection of notifications. 97 It is bound to the lifetime of a session. 99 Operation: This term is used to refer to NETCONF protocol 100 operations. Specifically within this document, operation refers 101 to NETCONF protocol operations defined in support of NETCONF 102 notifications. 104 1.2. XML Schema to Monitor Netconf 106 115 116 117 NetConf Monitoring Schema. 118 All elements in this Schema are read-only. 119 120 122 124 128 129 130 132 133 134 135 List of NETCONF capabilities supported 136 by this device. 137 138 139 140 141 144 145 146 148 149 150 151 List of NETCONF sessions currently 152 active on this device. 153 154 155 156 157 161 162 163 165 166 167 168 List of NETCONF configuration datastores (e.g. running, 169 startup, candidate) supported on this device and related 170 information. 171 172 173 174 175 177 178 179 181 182 183 184 List of NETCONF notification subscriptions 185 active on this device and related information. 186 187 188 189 190 193 194 195 197 198 199 201 203 204 205 206 207 208 209 211 212 213 214 215 216 218 219 220 221 An indication of whether a resource is locked or unlocked. 222 If locked, additional information about the locking such as 223 user and time stamp is provided. 224 225 226 227 228 229 230 231 232 233 234 235 237 238 239 The session ID of the session that has locked this resource. 240 241 243 244 246 247 248 The date and time of when the resource was locked. 249 If the resource is currently unlocked, this element 250 will not be present. 251 252 253 254 255 257 258 259 260 Information about Netconf Notification Subscriptions. 261 262 263 264 266 267 268 The session id associated with this 269 subscription. 270 271 272 274 276 277 278 The stream associated with this subscription. 279 280 281 283 285 286 287 The filters associated with this subscription. 288 289 290 291 292 293 294 The named profile associated with this 295 subscription. Note that the contents of the 296 named profile may have changed since it was 297 last applied. 298 299 300 302 303 304 305 The last time this subscription was modified. If 306 it has not been modified since creation, this is 307 the time of subscription creation. 308 309 310 312 314 315 316 A count of event notifications sent along 317 this connection since the subscription was 318 created. 319 320 321 323 324 325 326 327 328 330 331 333 335 2. Security Considerations 337 The information in this Schema provides information about Netconf 338 system that could be used to aid an attack on that system. Care 339 should be taken to restrict access to this information as 340 appropriate. 342 3. Acknowledgements 344 Thanks to the Netconf working group for providing a much earlier 345 draft of Schema to manage Netconf and Netconf Notifications that were 346 cannibalized to produce this draft. 348 4. Normative References 350 [NETCONF] Enns, R., "NETCONF Configuration Protocol", RFC 4741, 351 February 2006. 353 [NETCONF-EVENT] 354 Chisholm, S. and H. Trevino, "NETCONF Event 355 Notifications", ID draft-ietf-netconf-notifications-06, 356 February 2007. 358 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 359 3", RFC 2026, BCP 9, October 1996. 361 [RFC2119] Bradner, s., "Key words for RFCs to Indicate Requirements 362 Levels", RFC 2119, March 1997. 364 [RFC2223] Postel, J. and J. Reynolds, "Instructions to RFC Authors", 365 RFC 2223, October 1997. 367 [XML] World Wide Web Consortium, "Extensible Markup Language 368 (XML) 1.0", W3C XML, February 1998, 369 . 371 [XML Schema] 372 Fallside, D. and P. Walmsley, "XML Schema Part 0: Primer 373 Second Edition", W3C XML Schema, October 2004. 375 Authors' Addresses 377 Sharon Chisholm 378 Nortel 379 3500 Carling Ave 380 Nepean, Ontario K2H 8E9 381 Canada 383 Email: schishol@nortel.com 385 Hector Trevino 386 Cisco 387 Suite 400 388 9155 E. Nichols Ave 389 Englewood, CO 80112 390 USA 392 Email: htrevino@cisco.com 394 Full Copyright Statement 396 Copyright (C) The IETF Trust (2007). 398 This document is subject to the rights, licenses and restrictions 399 contained in BCP 78, and except as set forth therein, the authors 400 retain all their rights. 402 This document and the information contained herein are provided on an 403 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 404 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 405 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 406 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 407 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 408 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 410 Intellectual Property 412 The IETF takes no position regarding the validity or scope of any 413 Intellectual Property Rights or other rights that might be claimed to 414 pertain to the implementation or use of the technology described in 415 this document or the extent to which any license under such rights 416 might or might not be available; nor does it represent that it has 417 made any independent effort to identify any such rights. Information 418 on the procedures with respect to rights in RFC documents can be 419 found in BCP 78 and BCP 79. 421 Copies of IPR disclosures made to the IETF Secretariat and any 422 assurances of licenses to be made available, or the result of an 423 attempt made to obtain a general license or permission for the use of 424 such proprietary rights by implementers or users of this 425 specification can be obtained from the IETF on-line IPR repository at 426 http://www.ietf.org/ipr. 428 The IETF invites any interested party to bring to its attention any 429 copyrights, patents or patent applications, or other proprietary 430 rights that may cover technology that may be required to implement 431 this standard. Please address the information to the IETF at 432 ietf-ipr@ietf.org. 434 Acknowledgment 436 Funding for the RFC Editor function is provided by the IETF 437 Administrative Support Activity (IASA).