idnits 2.17.1 draft-iab-rfc7991bis-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 seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 17, 2018) is 2011 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 1966, 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 7749 (Obsoleted by RFC 7991) Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 9 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 17, 2018 5 Intended status: Informational 6 Expires: April 20, 2019 8 The "xml2rfc" version 3 Vocabulary 9 draft-iab-rfc7991bis-00 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 earlier v3 grammar described 17 in RFC 7991, which in turn obsoleted the v2 grammar in RFC 7749. 19 Editorial Note (To be removed by RFC Editor) 21 Discussion of this draft takes place on the xml2rfc-dev@ietf.org 22 mailing list, 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 April 20, 2019. 42 Copyright Notice 44 Copyright (c) 2018 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 . . . . . . . . . . 5 62 1.3. Differences from RFC 7991 in This Document . . . . . . . 6 63 1.4. Differences from v2 to v3 . . . . . . . . . . . . . . . . 6 64 1.4.1. New Elements in v3 . . . . . . . . . . . . . . . . . 6 65 1.4.2. New Attributes for Existing Elements . . . . . . . . 7 66 1.4.3. Elements and Attributes Deprecated from v2 . . . . . 8 67 1.4.4. Additional Changes from v2 . . . . . . . . . . . . . 9 68 1.5. Syntax Notation . . . . . . . . . . . . . . . . . . . . . 10 69 2. Elements . . . . . . . . . . . . . . . . . . . . . . . . . . 10 70 2.1. . . . . . . . . . . . . . . . . . . . . . . . 11 71 2.2.
. . . . . . . . . . . . . . . . . . . . . . . . 11 72 2.3. . . . . . . . . . . . . . . . . . . . . . . 12 73 2.4. . . . . . . . . . . . . . . . . . . . . . . . . . 13 74 2.5. . . . . . . . . . . . . . . . . . . . . . . . . 13 75 2.6.