idnits 2.17.1 draft-iab-xml2rfc-v3-bis-00.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 draft header indicates that this document obsoletes RFC7991, but the abstract doesn't seem to directly say this. It does mention RFC7991 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (October 2, 2018) is 2004 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'April1' is mentioned on line 1956, but not defined -- 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 7749 (Obsoleted by RFC 7991) Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 8 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: 7991 (if approved) October 2, 2018 5 Intended status: Informational 6 Expires: April 5, 2019 8 The "xml2rfc" Version 3 Vocabulary 9 draft-iab-xml2rfc-v3-bis-00 11 Abstract 13 This document defines the "xml2rfc" version 3 vocabulary: an XML- 14 based language used for writing RFCs and Internet-Drafts. When 15 published as an RFC, it will obsolete RFC 7991. 17 Discussion of this document is taking place on the xml2rfc-dev 18 mailing list. See 19 for more 20 information about the mailing list. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on April 5, 2019. 39 Copyright Notice 41 Copyright (c) 2018 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5 54 1.1. Differences from RFC 7991 . . . . . . . . . . . . . . . . 5 55 1.2. Expected Updates to the Specification . . . . . . . . . . 5 56 1.3. Design Criteria for the Changes in v3 . . . . . . . . . . 5 57 1.4. Differences from v2 to v3 . . . . . . . . . . . . . . . . 6 58 1.4.1. New Elements in v3 . . . . . . . . . . . . . . . . . 6 59 1.4.2. New Attributes for Existing Elements . . . . . . . . 7 60 1.4.3. Elements and Attributes Deprecated from v2 . . . . . 8 61 1.4.4. Additional Changes from v2 . . . . . . . . . . . . . 9 62 1.5. Syntax Notation . . . . . . . . . . . . . . . . . . . . . 10 63 2. Elements . . . . . . . . . . . . . . . . . . . . . . . . . . 10 64 2.1. . . . . . . . . . . . . . . . . . . . . . . . 11 65 2.2.
. . . . . . . . . . . . . . . . . . . . . . . . 11 66 2.3. . . . . . . . . . . . . . . . . . . . . . . 12 67 2.4. . . . . . . . . . . . . . . . . . . . . . . . . . 12 68 2.5. . . . . . . . . . . . . . . . . . . . . . . . . 13 69 2.6.