idnits 2.17.1 draft-iab-xml2rfc-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- -- The document has an IETF Trust Provisions (28 Dec 2009) Section 6.c(i) Publication Limitation clause. -- The document has an IETF Trust Provisions (28 Dec 2009) Section 6.c(ii) Publication Limitation clause. If this document is intended for submission to the IESG for publication, this constitutes an error. 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 a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 866: '...bcp14>The packet MUST be dropped.' and '' lines. Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'April1' is mentioned on line 1949, but not defined -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) -- Obsolete informational reference (is this intentional?): RFC 3667 (Obsoleted by RFC 3978) -- Obsolete informational reference (is this intentional?): RFC 3978 (Obsoleted by RFC 5378) -- Obsolete informational reference (is this intentional?): RFC 5741 (Obsoleted by RFC 7841) -- Obsolete informational reference (is this intentional?): RFC 7749 (Obsoleted by RFC 7991) Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group P. Hoffman 3 Internet-Draft ICANN 4 Obsoletes: 7749 (if approved) February 10, 2016 5 Intended status: Informational 6 Expires: August 13, 2016 8 The "xml2rfc" version 3 Vocabulary 9 draft-iab-xml2rfc-03 11 Abstract 13 This document defines the "xml2rfc" version 3 vocabulary: an XML- 14 based language used for writing RFCs and Internet-Drafts. It is 15 heavily derived from the version 2 vocabulary that is also under 16 discussion. This document obsoletes the v2 grammar described in RFC 17 2629 and its followup, RFC 7749. 19 Editorial Note (To be removed by RFC Editor) 21 Discussion of this draft takes place on the rfc-interest mailing list 22 (rfc-interest@rfc-editor.org), which has its home page at 23 . 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on August 13, 2016. 42 Copyright Notice 44 Copyright (c) 2016 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5 60 1.1. Expected Updates to the Specification . . . . . . . . . . 5 61 1.2. Design Criteria for the Changes in v3 . . . . . . . . . . 6 62 1.3. Differences from v2 to v3 . . . . . . . . . . . . . . . . 6 63 1.3.1. New Elements in v3 . . . . . . . . . . . . . . . . . 6 64 1.3.2. New Attributes for Existing Elements . . . . . . . . 7 65 1.3.3. Elements and Attributes Deprecated from v2 . . . . . 8 66 1.3.4. Additional Changes from v2 . . . . . . . . . . . . . 9 67 1.4. Syntax Notation . . . . . . . . . . . . . . . . . . . . . 10 68 2. Elements . . . . . . . . . . . . . . . . . . . . . . . . . . 10 69 2.1. . . . . . . . . . . . . . . . . . . . . . . . 11 70 2.2.
. . . . . . . . . . . . . . . . . . . . . . . . 11 71 2.3. . . . . . . . . . . . . . . . . . . . . . . 12 72 2.4. . . . . . . . . . . . . . . . . . . . . . . . . . 13 73 2.5. . . . . . . . . . . . . . . . . . . . . . . . . 13 74 2.6.