idnits 2.17.1 draft-netconf-rfc4743-rfc4744-to-historic-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 draft header indicates that this document obsoletes RFC4743/4744, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 06, 2012) is 4221 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 netconf B. Wijnen 3 Internet-Draft September 06, 2012 4 Obsoletes: 4743/4744 (if approved) 5 Intended status: Informational 6 Expires: March 10, 2013 8 RFC4743 and RFC4744 to Historic status 9 draft-netconf-rfc4743-rfc4744-to-historic-00 11 Abstract 13 This document moves RFC4743 (Using NETCONF over the Simple Object 14 Access Protocol (SOAP)) and RFC4744 (Using the NETCONF Protocol over 15 the Blocks Extensible Exchange Protocol (BEEP)) to HISTORIC status to 16 reflect the fact that those two documents have shown very little (if 17 any) implementations and deployment. Furthermore, no-one in the 18 NETCONF WG is interested or volunteering to work on them anymore. 20 Status of this Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on March 10, 2013. 37 Copyright Notice 39 Copyright (c) 2012 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 2. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 3 56 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 57 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 58 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 5.1. Normative References . . . . . . . . . . . . . . . . . . . 3 60 5.2. Informative References . . . . . . . . . . . . . . . . . . 3 61 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 1. Introduction 65 This document moves RFC 4743 [RFC4743] and RFC 4744 [RFC4744] to 66 HISTORIC status in accordance with RFC 2026 [RFC2026]. These two 67 documents have seen very little (if any) implementations or 68 deployment, and none of the initial proponents are active in the 69 NETCONF space anymore. No-one (else) in the WG is interested or 70 willing to pick up responsibility for these documents. 72 If these 2 documents were to be kept current, then changes might be 73 needed for compatibility with the current version of NETCONF 1.1. 75 In the WG nobody gave a positive response when asked who is using it 76 or wants to keep it. 78 2. Acknowledgements 80 Thanks to the original editors/authors of RFC4743 and RFC4744. At 81 the time that those RFCs were written, these NETCONF transports 82 seemed to be attractive. 84 3. IANA Considerations 86 This memo includes no request to IANA. 88 4. Security Considerations 90 This draft introduces no new security considerations. 92 5. References 94 5.1. Normative References 96 [RFC4743] Goddard, T., "Using NETCONF over the Simple Object Access 97 Protocol (SOAP)", RFC 4743, December 2006. 99 [RFC4744] Lear, E. and K. Crozier, "Using the NETCONF Protocol over 100 the Blocks Extensible Exchange Protocol (BEEP)", RFC 4744, 101 December 2006. 103 5.2. Informative References 105 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 106 3", BCP 9, RFC 2026, October 1996. 108 Author's Address 110 Bert Wijnen 111 Schagen 33 112 Linschoten, 3461 GL 113 Netherlands 115 Phone: +31 348-407-775 116 Email: bertietf@bwijnen.net