Open Participation Principle regarding Remote Registration Fee
draft-ietf-shmoo-remote-fee-01

Network Working Group                                         P. Hoffman
Internet-Draft                                            VPN Consortium
Obsoletes: 2629 (if approved)                             April 19, 2014
Intended status: Standards Track
Expires: October 21, 2014

                   The 'XML2RFC' version 3 Vocabulary
                        draft-hoffman-xml2rfc-05

Abstract

   This document defines the 'XML2RFC' version 3 vocabulary; an XML-
   based language used for writing RFCs and Internet-Drafts.  It is
   heavily derived from the version 2 vocabulary that is also under
   discussion.

Editorial Note (To be removed by RFC Editor)

   Discussion of this draft takes place on the rfc-interest mailing list
   (rfc-interest@rfc-editor.org), which has its home page at
   <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 21, 2014.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of

Hoffman                 Expires October 21, 2014                [Page 1]
Internet-Draft                  XML2RFCv3                     April 2014

   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5
     1.1.  Design Criteria for the Changes in v3  . . . . . . . . . .  5
     1.2.  Differences from v2 to v3  . . . . . . . . . . . . . . . .  6
       1.2.1.  New Elements in v3 . . . . . . . . . . . . . . . . . .  6
       1.2.2.  New Attributes for Existing Elements . . . . . . . . .  7
       1.2.3.  Elements and Attributes Deprecated from v2 . . . . . .  7
       1.2.4.  Additional Changes from v2 . . . . . . . . . . . . . .  8
     1.3.  Syntax Notation  . . . . . . . . . . . . . . . . . . . . .  9
   2.  Elements . . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     2.1.  <abstract> . . . . . . . . . . . . . . . . . . . . . . . .  9
     2.2.  <address>  . . . . . . . . . . . . . . . . . . . . . . . .  9
     2.3.  <annotation> . . . . . . . . . . . . . . . . . . . . . . . 10
     2.4.  <area> . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     2.5.  <artwork>  . . . . . . . . . . . . . . . . . . . . . . . . 11
     2.6.  <aside>  . . . . . . . . . . . . . . . . . . . . . . . . . 13
     2.7.  <author> . . . . . . . . . . . . . . . . . . . . . . . . . 14
     2.8.  <b>  . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
     2.9.  <back> . . . . . . . . . . . . . . . . . . . . . . . . . . 16
     2.10. <blockquote> . . . . . . . . . . . . . . . . . . . . . . . 16
     2.11. <c>  . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
     2.12. <city> . . . . . . . . . . . . . . . . . . . . . . . . . . 18
     2.13. <code> . . . . . . . . . . . . . . . . . . . . . . . . . . 18
     2.14. <country>  . . . . . . . . . . . . . . . . . . . . . . . . 18
     2.15. <cref> . . . . . . . . . . . . . . . . . . . . . . . . . . 18
     2.16. <date> . . . . . . . . . . . . . . . . . . . . . . . . . . 19
     2.17. <dd> . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
     2.18. <displayreference> . . . . . . . . . . . . . . . . . . . . 21
     2.19. <dl> . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
     2.20. <dt> . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
     2.21. <em> . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
     2.22. <email>  . . . . . . . . . . . . . . . . . . . . . . . . . 24
     2.23. <eref> . . . . . . . . . . . . . . . . . . . . . . . . . . 24
     2.24. <facsimile>  . . . . . . . . . . . . . . . . . . . . . . . 24
     2.25. <figure> . . . . . . . . . . . . . . . . . . . . . . . . . 25
     2.26. <format> . . . . . . . . . . . . . . . . . . . . . . . . . 27
     2.27. <front>  . . . . . . . . . . . . . . . . . . . . . . . . . 27
     2.28. <i>  . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
     2.29. <iref> . . . . . . . . . . . . . . . . . . . . . . . . . . 28
     2.30. <keyword>  . . . . . . . . . . . . . . . . . . . . . . . . 29

Hoffman                 Expires October 21, 2014                [Page 2]
Internet-Draft                  XML2RFCv3                     April 2014

     2.31. <li> . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
     2.32. <list> . . . . . . . . . . . . . . . . . . . . . . . . . . 30
     2.33. <middle> . . . . . . . . . . . . . . . . . . . . . . . . . 31
     2.34. <note> . . . . . . . . . . . . . . . . . . . . . . . . . . 31
     2.35. <ol> . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
     2.36. <organization> . . . . . . . . . . . . . . . . . . . . . . 33
     2.37. <phone>  . . . . . . . . . . . . . . . . . . . . . . . . . 33
     2.38. <postal> . . . . . . . . . . . . . . . . . . . . . . . . . 34
     2.39. <postalLine> . . . . . . . . . . . . . . . . . . . . . . . 34
     2.40. <postamble>  . . . . . . . . . . . . . . . . . . . . . . . 35
     2.41. <preamble> . . . . . . . . . . . . . . . . . . . . . . . . 35
     2.42. <refcontent> . . . . . . . . . . . . . . . . . . . . . . . 36
     2.43. <reference>  . . . . . . . . . . . . . . . . . . . . . . . 37
     2.44. <references> . . . . . . . . . . . . . . . . . . . . . . . 38
     2.45. <region> . . . . . . . . . . . . . . . . . . . . . . . . . 38
     2.46. <rfc>  . . . . . . . . . . . . . . . . . . . . . . . . . . 38
     2.47. <section>  . . . . . . . . . . . . . . . . . . . . . . . . 43
     2.48. <seriesInfo> . . . . . . . . . . . . . . . . . . . . . . . 45
     2.49. <sourcecode> . . . . . . . . . . . . . . . . . . . . . . . 45
     2.50. <spanx>  . . . . . . . . . . . . . . . . . . . . . . . . . 47
     2.51. <street> . . . . . . . . . . . . . . . . . . . . . . . . . 47
     2.52. <strong> . . . . . . . . . . . . . . . . . . . . . . . . . 48
     2.53. <t>  . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
     2.54. <texttable>  . . . . . . . . . . . . . . . . . . . . . . . 49
     2.55. <title>  . . . . . . . . . . . . . . . . . . . . . . . . . 51
     2.56. <titleelement> . . . . . . . . . . . . . . . . . . . . . . 52
     2.57. <tt> . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
     2.58. <ttcol>  . . . . . . . . . . . . . . . . . . . . . . . . . 53
     2.59. <ul> . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
     2.60. <uri>  . . . . . . . . . . . . . . . . . . . . . . . . . . 54
     2.61. <vspace> . . . . . . . . . . . . . . . . . . . . . . . . . 55
     2.62. <workgroup>  . . . . . . . . . . . . . . . . . . . . . . . 55
     2.63. <xref> . . . . . . . . . . . . . . . . . . . . . . . . . . 55
   3.  Special Unicode Code Points  . . . . . . . . . . . . . . . . . 58
   4.  Internationalization Considerations  . . . . . . . . . . . . . 59
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . . 59
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 60
     6.1.  Internet Media Type Registration . . . . . . . . . . . . . 60
   7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 61
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 61
     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 61
     8.2.  Informative References . . . . . . . . . . . . . . . . . . 61
   Appendix A.  Front Page Generation . . . . . . . . . . . . . . . . 63
     A.1.  The /rfc/@category Attribute . . . . . . . . . . . . . . . 63
     A.2.  The /rfc/@ipr Attribute  . . . . . . . . . . . . . . . . . 64
       A.2.1.  Current Values: '*trust200902' . . . . . . . . . . . . 64
       A.2.2.  Historic Values  . . . . . . . . . . . . . . . . . . . 66
   Appendix B.  The v3 Format and Processors  . . . . . . . . . . . . 66

Hoffman                 Expires October 21, 2014                [Page 3]
Internet-Draft                  XML2RFCv3                     April 2014

     B.1.  Including External Text  . . . . . . . . . . . . . . . . . 68
     B.2.  The RFC Processor  . . . . . . . . . . . . . . . . . . . . 69
     B.3.  The Draft Processor  . . . . . . . . . . . . . . . . . . . 69
     B.4.  Processor Instructions . . . . . . . . . . . . . . . . . . 70
   Appendix C.  Relax NG Schema . . . . . . . . . . . . . . . . . . . 70
   Appendix D.  Schema Differences from v2  . . . . . . . . . . . . . 80
   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Hoffman                 Expires October 21, 2014                [Page 4]
Internet-Draft                  XML2RFCv3                     April 2014

1.  Introduction

   This document describes version 3 ('v3') of the 'XML2RFC' vocabulary;
   an XML-based language ('Extensible Markup Language', [XML]) used for
   writing RFCs ([RFCSTYLE]) and Internet-Drafts ([IDGUIDE]).

   This document obsoletes the version ("v2") vocabulary [XML2RFCv2],
   which contains the extended language definition.  That document in
   turn obsoletes the original version ("v1") [RFC2629].  This document
   directly copies the material from [XML2RFCv2] where possible; as that
   document makes its way toward RFC publication, this document will
   incorporate as many of the changes as possible. [[anchor2: More needs
   to be said here about what "obsoletes" means in this case.]]

   The v3 format will be used as part of the new RFC series described in
   [RFC6949].  The new series will have multiple formats: the canonical
   document will be in XML using the v3 format described here, and many
   non-canonical formats (such as HTML and text) will be generated as
   well.  The generation of these non-canonical formats means that there
   will be much more emphasis put on the processor that handles the XML.
   Features of the expected processor are described in Appendix B.

   Note that the vocabulary contains certain constructs that might not
   affect the rendering of the final text; however, they can provide
   useful data for other uses (such index generation, populating a
   keyword database, or syntax checks).

   The following is a hopefully-complete list of all the technical
   changes between [XML2RFCv2] and this document, as welll as the design
   criteria for those changes.  Note that the list is for the current
   version of this document only.  There are additional changes that are
   expected to the v3 vocabulary that are being discussed.  Also note
   that changes to the design choices for the differences are also
   expected.

1.1.  Design Criteria for the Changes in v3

   The design criteria of the changes from v2 to v3 are:

   o  The intention is that starting and editing a v3 document will be
      easier than for a v2 document.

   o  There will be good v2-to-v3 conversion tools for when an author
      wants to change versions.

   o  There are no current plans to make v3 XML the required submission
      format for drafts or RFCs.  That might happen eventually, but it
      is likely to be years away.

Hoffman                 Expires October 21, 2014                [Page 5]
Internet-Draft                  XML2RFCv3                     April 2014

   There is a desire to keep as much of the v2 grammar as makes sense
   within the above design criteria and not to make gratuitous changes
   to the v2 grammar.  Another way to say this is "we would rather
   encourage backward compatibility but not be constrained by it".
   Still, the goal of starting and editing a v3 document being easier
   than for a v2 document is more important than backwards compatibility
   with v2, given the latter two design criteria.

   v3 is upwards compatible with v2, meaning that a v2 document is meant
   to be a valid v3 document as well.  However, some features of v2 are
   deprecated in v3 in favor of new elements.  Deprecated features are
   described in [XML2RFCv2].

   The canonical RFCs will not have any markup that uses a deprecated
   feature.  The processor described in Appendix B will have a "convert
   with warnings" mode that will convert a v2 document to a v3 document
   that converts deprecated features wherever possible, issuing warnings
   for where it cannot convert.  The processor will also have a "strict"
   mode that will issue errors if any deprecated features are in the
   input.

1.2.  Differences from v2 to v3

   The format changes in v3 are listed in the following subsections.

1.2.1.  New Elements in v3

   o  Add <dl>, <ul>, and <ol> as new ways to make lists.  This is a
      significant change from v2 in that the child under these elements
      is <li>, not <t>. <li> has a model of either containing one or
      more <t> elements, or containing the flowing text normally found
      in <t>.

   o  Add <strong>, <b>, <em>, <i>, and <tt> for character formatting.

   o  Add <aside> for incidental text that will be indented when
      displayed.

   o  Add <sourcecode> to differentiate from <artwork>.

   o  Add <blockquote> to indicate a quotation as in a paragraph-like
      format.

   o  Add <titleelement> to sections, figures, and texttables to allow
      character formatting (fixed-width font) in their titles, and to
      allow references.

Hoffman                 Expires October 21, 2014                [Page 6]
Internet-Draft                  XML2RFCv3                     April 2014

   o  Add <postalLine>, free text that represents one line of the
      address.

   o  Add <displayreference> to allow display of more mneumonic anchor
      names for automatically-included references.

   o  Add <refcontent> to allow better control of text in a reference.

1.2.2.  New Attributes for Existing Elements

   o  Add "sortRefs", "symRefs&Kuehlewind, et al.      Expires 19 November 2021                [Page 4]
Internet-Draft        Open Participation Principle              May 2021

   Aggregated data on the number and percentage of free registrations
   used should be published, as this will permit analysis of the use and
   change in use over time of the free registration option without
   revealing personal information.  However, as long as the number of
   paid registrations stays stable and retains the projected needed
   income, an increase in use of free registrations should not
   necessarily be taken as a sign of misuse but rather a sign of
   increased interest and success for the open participation principle.
   If the number of paid registrations, however, decreases, this can
   still also have various reasons other than misuse, such as
   restrictions on travel to physical meetings due to cost savings or
   environmental reasons, general cost savings and lesser focus on
   standardization work, or simply lost of business interest.  These are
   risks that can impact the sustainability of the IETF independent of
   the free registration option due to its dependency on meetings fees
   to cross-finance other costs.

5.  Acknowledgments

   Thanks to everybody involved in the shmoo working group discussion,
   esepcially Brian Carpenter, Jason Livingood, and Charles Eckel for
   proposing concrete improvements and and their in-depth reviews.

6.  Normative References

   [RFC3935]  Alvestrand, H., "A Mission Statement for the IETF",
              BCP 95, RFC 3935, DOI 10.17487/RFC3935, October 2004,
              <https://www.rfc-editor.org/info/rfc3935>.

Authors' Addresses

   Mirja Kuehlewind
   Ericsson

   Email: mirja.kuehlewind@ericsson.com

   Jon Reed
   Akamai

   Email: jreed@akamai.com

   Rich Salz
   Akamai

   Email: rsalz@akamai.com

Kuehlewind, et al.      Expires 19 November 2021                [Page 5]