Internet-Draft Xml2rfc Vocabulary V3 Elements July 2018
Author, et al. Expires January 13, 2019 [Page]
Workgroup:
Network Working Group
Obsoletes:
1234, 5678, 9012, 3456, 7890 (if approved)
Published:
Intended Status:
Informational
Expires:
Authors:
A. Author
רוני אבן (R. Even)
וואווי (Huawei)
田中花子 様 (H. Tanaka)
N. Org
B. Aventure
Université de Liège
International Association for Cryptologic Research
A. Lindgren

Xml2rfc Vocabulary V3 Elements
Combined Test File

Abstract

This is the abstract.

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 https://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 January 13, 2019.

Table of Contents

1. RFC 2119 key words

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

2. Citations

This section contains a bunch of citations, in order to test citation formats and also in order to refer to each of the entries in the Section 18.

Citations of References:

Citations of References with explicit text:

Citations of multiple Sections in References, using sectionFormat="bare":

Citations of multiple Sections in References, using text and sectionFormat="bare":

References to Abstract, with explicit text:

References to Abstract:

References to Sections, with explicit text:

References to Sections:

References to Appendix:

References to Comments:

This comment is to be cited.

These references should be present: [RFC5652] [RFC2634] [RFC5035] [RFC2045] [RFC2046] [RFC2047] [RFC2049] [RFC4289] [RFC6838]

3. Unordered list with sub-elements

4. Ordered list with sub-elements

  1. Ordered list, first bullet. Indent="6".
  2. Ordered list, second bullet. Indent="6". Text only. Octavio fuit, cum illam severitatem in eo non arbitrantur. erunt etiam, et ii quidem eruditi Graecis litteris, contemnentes Latinas, qui se plane Graecum dici velit, ut a Scaevola est praetore salutatus Athenis Albucius. In physicis plurimum posuit. ea scientia et verborum vis et natura orationis et consequentium repugnantiumve ratio potest perspici.
  1. Ordered list, third bullet, element t. Quid? si nos non interpretum fungimur munere, sed tuemur ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem. Extremum autem esse bonorum eum voluptate vivere. Sic faciam igitur, inquit: unam rem explicabo, eamque maximam, de physicis alias, et quidem locis pluribus.

            Ordered list, third bullet, second element:
            +-------------------------------------------+
            |                                           |
            |                  Artwork                  |
            |                                           |
            +-------------------------------------------+
    
    Ordered list, third bullet, third element: Definition list, element dt.

    Element dd. Nisi mihi Phaedrum, inquam, tu mentitum aut Zenonem misisti.
    Ordered list, third bullet, fourth element:
                        Figure
                            Figure
                               Figure
    
    Figure 2: Some figure name
    1. Ordered list, third bullet, fifth element: Ordered list, element li. Text only.
    2. Ordered list, third bullet, fifth element: Ordered list, element t. Nam cum ad me de virtute misisti. Quae est enim contra Cyrenaicos satis acute, nihil ad iucunde vivendum reperiri posse, quod coniunctione tali sit aptius. Quae etsi mihi nullo modo nec divelli nec distrahi possint, sic de iustitia iudicandum est, quae non modo non impediri rationem amicitiae, si summum bonum diceret, primum in eo essent.

                      # Ordered list, third bullet, sixth element
                      A = 1;
    
    • Ordered list, third bullet, seventh element: Unordered list, element li. Text only.
    • Element t. Atque ut odia, invidiae, despicationes adversantur voluptatibus, sic amicitiae non posse iucunde vivi, nisi sapienter, honeste iusteque vivatur, nec sapienter, honeste, iuste, nisi iucunde. Democritea dicit perpauca mutans, sed ita, ut ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem. See Appendix A, Section 3.1 of [I-D.levkowetz-xml2rfc-v3-implementation-notes] and also Appendix A.1 of Key Words Case Ambiguity [RFC8174] / Key Words Case Ambiguity [RFC8174], Appendix A.1 / Key Words Case Ambiguity [RFC8174] (Appendix A.1).

  2. 4.1
    Sublist with '%p' parent counter element in the list counter, item one
    4.2
    Item two.
    4.3
    Item three.

5. Definition list with sub-elements

Term 1
Definition list, first bullet.
Term 2
Definition list, second bullet. Text only. Octavio fuit, cum illam severitatem in eo non arbitrantur. erunt etiam, et ii quidem eruditi Graecis litteris, contemnentes Latinas, qui se plane Graecum dici velit, ut a Scaevola est praetore salutatus Athenis Albucius. In physicis plurimum posuit. ea scientia et verborum vis et natura orationis et consequentium repugnantiumve ratio potest perspici.
Term 3

Definition list, third bullet, element t. Quid? si nos non interpretum fungimur munere, sed tuemur ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem. Extremum autem esse bonorum eum voluptate vivere. Sic faciam igitur, inquit: unam rem explicabo, eamque maximam, de physicis alias, et quidem locis pluribus.

        Definition list, third bullet, second element:
        +-------------------------------------------+
        |                                           |
        |                  Artwork                  |
        |                                           |
        +-------------------------------------------+
Definition list, third bullet, third element: Definition list, element dt.

Element dd. Nisi mihi Phaedrum, inquam, tu mentitum aut Zenonem misisti.
Definition list, third bullet, fourth element:
                    Figure
                        Figure
                           Figure
Figure 3: Some figure name
  1. Definition list, third bullet, fifth element: Ordered list, element li. Text only.
  2. Definition list, third bullet, fifth element: Ordered list, element t. Nam cum ad me de virtute misisti. Quae est enim contra Cyrenaicos satis acute, nihil ad iucunde vivendum reperiri posse, quod coniunctione tali sit aptius. Quae etsi mihi nullo modo nec divelli nec distrahi possint, sic de iustitia iudicandum est, quae non modo non impediri rationem amicitiae, si summum bonum diceret, primum in eo essent.

    • UL within OL within DL, item one
    • UL within OL within DL, item two
    • UL within OL within DL, empty="true"; item one
    • UL within OL within DL, empty="true"; item two
    • UL within OL within DL, bare="true"; item one
    • UL within OL within DL, bare="true"; item two
                  # Definition list, third bullet, sixth element
                  A = 1;
  • Definition list, third bullet, seventh element: Unordered list, element li. Text only.
  • Element t. Atque ut odia, invidiae, despicationes adversantur voluptatibus, sic amicitiae non posse iucunde vivi, nisi sapienter, honeste iusteque vivatur, nec sapienter, honeste, iuste, nisi iucunde. Democritea dicit perpauca mutans, sed ita, ut ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem.

Definition list, third bullet, eight element, t. Quid? si nos non interpretum fungimur munere, sed tuemur ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem. Extremum autem esse bonorum eum voluptate vivere. Sic faciam igitur, inquit: unam rem explicabo, eamque maximam, de physicis alias, et quidem locis pluribus.

Definition list, third bullet, ninth element, t. Quid? si nos non interpretum fungimur munere, sed tuemur ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem. Extremum autem esse bonorum eum voluptate vivere. Sic faciam igitur, inquit: unam rem explicabo, eamque maximam, de physicis alias, et quidem locis pluribus.

6. Table

      +-----+-----+-----------+
      |     |     |           |
      +-----+-----+-----+-----+
      |     |     |     |     |
      +=====+=====+=====+=====+
      |     |     |     |     |
      +-----+-----+-----+-----+
      |     |                 |
      +     +-----+-----+-----+
      |     |     |     |     |
      +     +     +-----+-----+
      |     |     |           |
      +-----+     +-----+-----+
      |     |     |     |     |
      +=====+=====+=====+=====+
      |     |     |     |     |
      +-----+-----+-----+-----+
Table 1: Header, footer, colspan and rowspan
Default alignment
A B C D
1 2 3 4
Long text in a single cell b1 c1 d1
Long text in a 3-cell column.
Quid igitur est? Inquit; audire enim cupio, quid non probes eius, a quo dissentias.
Long text in a 3-cell row.
Quid enim est a Cyrenaicisque melius liberiusque defenditur, tamen eius modi tempora incidunt, ut labore et dolore disputandum putant.
Another 3-cell column. c3 d3
x
a5 c5 d5
aa bb cc dd
Table 2: Aligned left
One Two
Alpha Beta
Table 3: Aligned center
One Two
Alpha Beta
Table 4: Aligned right
One Two
Alpha Beta

A really tight table where left padding cannot be applied as it would throw the left-alignment of the text off.

Table 5
Method Definition ptype property Value Status Version
dnswl RFC 8904 dns zone

DNSWL publicly accessible query root domain

active 1
dnswl RFC 8904 policy ip

type A response received (or a quoted, comma-separated list thereof)

active 1
dnswl RFC 8904 policy txt type TXT query response active 1
dnswl RFC 8904 dns sec one of "yes" for DNSSEC authenticated data, "no" for not signed, or "na" for not applicable active 1

7. Unicode Literals

7.1. Single Characters

Expansion "num":

Example XML:

Use the character
  <u format="num">Δ</u>.

expands to:

Use the character U+0394.

Expansion "name":

Example XML:

Use the character <u format="name-num">Δ</u>.

expands to:

Use the character GREEK CAPITAL LETTER DELTA (U+0394).

Expansion "num-lit":

Example XML:

Use the character <u format="num-lit">Δ</u>.

expands to:

Use the character U+0394 ("Δ").

Expansion "num-name":

Example XML:

Use the <u format="{num} character ({name})">Δ</u>.

expands to:

Use the U+0394 character (GREEK CAPITAL LETTER DELTA).

  • Tab: U+0009 (U+0009)
  • Char(128): U+0080 (U+0080)
Expansion "num-lit-name":

Example XML:

Use the character <u format="num-lit-name">Δ</u>.

expands to:

Use the character U+0394 ("Δ", GREEK CAPITAL LETTER DELTA).

Expansion "num-name-lit":

Example XML:

Use the character <u format="num-name-lit">Δ</u>.

expands to:

Use the character U+0394 (GREEK CAPITAL LETTER DELTA, "Δ").

Expansion "ascii-lit-num":

Example XML:

Use the character
  <u ascii="Delta" format="ascii-lit-num" ascii="Delta">Δ</u>.

expands to:

Use the character "Delta" ("Δ", U+0394).

Expansion "lit-name-num":

Example XML:

Use the <u format="{lit} character ({name}, {num})">Δ</u>.

expands to:

Use the "Δ" character (GREEK CAPITAL LETTER DELTA, U+0394)

Expansion "lit-num":

Example XML:

Use the <u format="{lit} character ({num})">Δ</u>.

expands to:

Use the "Δ" character (U+0394).

7.2. Character Strings

Expansion "num-lit":

Example XML:

For example, the characters
  <u ascii="STPETER" format="num-lit">ᏚᎢᎵᎬᎢᎬᏒ</u>
from the Cherokee block look similar to the ASCII characters
"STPETER".

expands to:

For example, the characters U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2 ("ᏚᎢᎵᎬᎢᎬᏒ") from the Cherokee block look similar to the ASCII characters "STPETER".

Expansion "num-name":

Example XML:

For example, the characters
  <u ascii="STPETER" format="num-name">ᏚᎢᎵᎬᎢᎬᏒ</u>
from the Cherokee block look similar to the ASCII characters
"STPETER".

expands to:

For example, the characters U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2 (CHEROKEE LETTER DU, CHEROKEE LETTER I, CHEROKEE LETTER LI, CHEROKEE LETTER GV, CHEROKEE LETTER I, CHEROKEE LETTER GV, CHEROKEE LETTER SV) from the Cherokee block look similar to the ASCII characters "STPETER".

Expansion "num-lit-name":

Example XML:

For example, the characters
  <u ascii="STPETER" format="num-lit-name">ᏚᎢᎵᎬᎢᎬᏒ</u>
from the Cherokee block look similar to the ASCII characters
"STPETER".

expands to:

For example, the characters U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2 ("ᏚᎢᎵᎬᎢᎬᏒ", CHEROKEE LETTER DU, CHEROKEE LETTER I, CHEROKEE LETTER LI, CHEROKEE LETTER GV, CHEROKEE LETTER I, CHEROKEE LETTER GV, CHEROKEE LETTER SV) from the Cherokee block look similar to the ASCII characters "STPETER".

Expansion "num-name-lit":

Example XML:

For example, the characters
  <u ascii="STPETER" format="num-name-lit">ᏚᎢᎵᎬᎢᎬᏒ</u>
from the Cherokee block look similar to the ASCII characters
"STPETER".

expands to:

For example, the characters U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2 (CHEROKEE LETTER DU, CHEROKEE LETTER I, CHEROKEE LETTER LI, CHEROKEE LETTER GV, CHEROKEE LETTER I, CHEROKEE LETTER GV, CHEROKEE LETTER SV, "ᏚᎢᎵᎬᎢᎬᏒ") from the Cherokee block look similar to the ASCII characters "STPETER".

Expansion "ascii-lit-num":

Example XML:

For example, the characters
  <u ascii="STPETER" format="ascii-lit-num">ᏚᎢᎵᎬᎢᎬᏒ</u>
from the Cherokee block look similar to the ASCII characters
"STPETER".

expands to:

For example, the characters "STPETER" ("ᏚᎢᎵᎬᎢᎬᏒ", U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2) from the Cherokee block look similar to the ASCII characters "STPETER".

Expansion "lit-name-num":

Example XML:

For example, the
  <u ascii="STPETER" format="{lit}
     characters ({name}, {num})">ᏚᎢᎵᎬᎢᎬᏒ</u>
from the Cherokee block look similar to the ASCII characters
"STPETER".

expands to:

For example, the "ᏚᎢᎵᎬᎢᎬᏒ" characters (CHEROKEE LETTER DU, CHEROKEE LETTER I, CHEROKEE LETTER LI, CHEROKEE LETTER GV, CHEROKEE LETTER I, CHEROKEE LETTER GV, CHEROKEE LETTER SV, U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2) from the Cherokee block look similar to the ASCII characters "STPETER".

Expansion "lit-num":

Example XML:

For example, the
  <u ascii="STPETER" format="{lit} characters ({num})">ᏚᎢᎵᎬᎢᎬᏒ</u>
from the Cherokee block look similar to the ASCII characters
"STPETER".

expands to:

For example, the "ᏚᎢᎵᎬᎢᎬᏒ" characters (U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2) from the Cherokee block look similar to the ASCII characters "STPETER".

8. Irregular date specifications

You can now use date ranges like "2002-2003" (See [DATE-RANGE]) and fuzzy dates such as "Spring 1814" (See [FUZZY-DATE]) by omitting the year/month/day attributes of <date>, and instead provide text content.

9. Aside, Word Joiner, and Break

Regular: Nam ut tortor ut dui fermentum viverra. Quisque sed aliquam enim. Pellentesque vestibulum risus sed ligula eleifend commodo. Sed vel lacus id mauris dapibus lobortis. Suspendisse quis pellentesque nisl, vitae pulvinar felis. Ut at hendrerit odio. Morbi non sem non ligula posuere ultrices.

Definition list with aside in <dd>

10. Section title test 1

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

11. Section level h2

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

11.1. Section level h3

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

11.1.1. Section level h4

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

11.1.1.1. Section level h5

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

11.1.1.1.1. Section level h6

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

12. Eref brackets

13. Sourcecode indentation

Source code as-is:

while true ; do
    case "$1" in
        -h| --help)     usage; exit;;   # Show this help
        -v| --verbose)  VERBOSE=1;;     # Be more talkative
        -V| --version)  version; exit;; # Show program version
        --)             shift; break;;
    esac
    shift
done

Source code within a figure:

for opt, value in opts:
    if   opt in ["-h", "--help"]: # Output this help, then exit
        print __doc__ % locals()
        sys.exit(1)
    elif opt in ["-v", "--version"]: # Output version information
        print program, version
        sys.exit(0)
    elif opt in ["-V", "--verbose"]: # Output version information
        opt_verbose = True
Figure 4: Sourcecode within figure

14. Tables inside lists

Step 1:

(This example is excerpted from pre-RFC8677) Indent="9"

At nSFF1, the following nNLM is assumed:

Table 6: nNLM at nSFF1
SPI SI Next Hop(s) Transport Encapsulation (TE)
10 255 192.0.2.1 VXLAN-gpe
10 254 198.51.100.10 GRE
10 253 www.example.com HTTP
10 252 www.example2.com HTTP
40 251 198.51.100.15 GRE
50 200 01:23:45:67:89:ab Ethernet
15 212 Null (end of path) None
This is an arbitrary term:

And this is some text with a table.

Table 7
Head 1 Head 2 Head 3
Cell A1 Cell A2 Cell A3
Cell B1 Cell B2 Cell B3
Cell C1 Cell C2 Cell C3
Head 10 Head 20 Head 30
Cell A10 Cell A20 Cell A30
Cell B10 Empty Cell:

15. Wide artwork

0        1         2         3         4         5         6         7
123456789012345678901234567890123456789012345678901234567890123456789012

16. Sup and sub

Sup
Text with superscript2
Sup
Simple superscript expressions: x-1 y+3.0 z3.2a
Sup
More simple superscript expressions: x1.2 yn0
Sup
Parenthetical expressions in superscript: x(n+1) y-(k-1) z(_c)
Sup
Compound superscript expressions: xx+y y_c za.0
Sup
One word superscript or two words superscript
Sup
Text with sub inside superscriptx2
Sub
Text with subscript2
Sub
Simple subscript expressions: x-1 y+3.0 z3.2a
Sub
More simple subscript expressions: x1.2 yn0
Sub
Parenthetical expressions in subscript: x(n+1) y-(k-1) z(_c)
Sub
Compound subscript expressions: xx+y y_c za.0
Sub
One word subscript or two words subscript
Sub
Text with super inside subscriptx2

Unnumbered section

Regular paragraph. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut pharetra neque vulputate dolor elementum sodales. Maecenas maximus elit sit amet pretium facilisis. Vivamus pulvinar, quam nec eleifend ultricies, nisi elit rhoncus risus, in commodo mi leo in lorem.

Indented paragraph. Indent="5". Aenean ornare elit at urna molestie fermentum. Donec erat purus, vestibulum in venenatis tempor, feugiat nec neque. Fusce luctus sem neque, id venenatis turpis vulputate nec. Nulla tincidunt pretium ex fringilla posuere. Cras quis massa neque.

  1. Indent="5". Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut pharetra neque vulputate dolor elementum sodales.
  2. Item 2

References

Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[RFC7997]
Flanagan, H., Ed., "The Use of Non-ASCII Characters in RFCs", IAB, RFC 7997, DOI 10.17487/RFC7997, , <https://www.rfc-editor.org/info/rfc7997>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.

Informative References

CMS References

[I-D.levkowetz-xml2rfc-v3-implementation-notes]
Levkowetz, H., "Implementation notes for RFC7991,", Work in Progress, Internet-Draft, draft-levkowetz-xml2rfc-v3-implementation-notes-13, , <https://www.ietf.org/archive/id/draft-levkowetz-xml2rfc-v3-implementation-notes-13.txt>.
[RFC5083]
Housley, R., "Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content Type", RFC 5083, DOI 10.17487/RFC5083, , <https://www.rfc-editor.org/info/rfc5083>.
[RFC5652]
Housley, R., "Cryptographic Message Syntax (CMS)", STD 70, RFC 5652, DOI 10.17487/RFC5652, , <https://www.rfc-editor.org/info/rfc5652>.

ESS References

[RFC2634]
Hoffman, P., Ed., "Enhanced Security Services for S/MIME", RFC 2634, DOI 10.17487/RFC2634, , <https://www.rfc-editor.org/info/rfc2634>.
[RFC5035]
Schaad, J., "Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility", RFC 5035, DOI 10.17487/RFC5035, , <https://www.rfc-editor.org/info/rfc5035>.

MIME-SPEC References

[RFC2045]
Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, DOI 10.17487/RFC2045, , <https://www.rfc-editor.org/info/rfc2045>.
[RFC2046]
Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, DOI 10.17487/RFC2046, , <https://www.rfc-editor.org/info/rfc2046>.
[RFC2047]
Moore, K., "MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047, DOI 10.17487/RFC2047, , <https://www.rfc-editor.org/info/rfc2047>.
[RFC2049]
Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples", RFC 2049, DOI 10.17487/RFC2049, , <https://www.rfc-editor.org/info/rfc2049>.
[RFC4289]
Freed, N. and J. Klensin, "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures", BCP 13, RFC 4289, DOI 10.17487/RFC4289, , <https://www.rfc-editor.org/info/rfc4289>.
[RFC6838]
Freed, N., Klensin, J., and T. Hansen, "Media Type Specifications and Registration Procedures", BCP 13, RFC 6838, DOI 10.17487/RFC6838, , <https://www.rfc-editor.org/info/rfc6838>.

Other References

[AUTHORS]
Πυθαγόρας ὁ Σάμιος (Samos, P. O.), Doe, J., Bergström, A., and J. Doe, "Lots of authors", RFC 7539, DOI 10.17487/RFC7539, , <https://www.rfc-editor.org/rfc/rfc7539>.
[DATE-RANGE]
Moe, J., "Document with date range", 2002-2003.
[FUZZY-DATE]
Mae, J., "Document with fuzzy date", Second quarter 2010.
[GEDICHTE]
Heine, H., "Dreiunddreißig Gedichte", .
[NO-DATE]
Mae, N., "Document — with no date", Advances in Cryptology - AACC Edition pp. 235-265.
[REPUBLIC]
Πλάτων (Plato), "Πολιτεία" ("The Republic"), 375 BC.
[RFC0952]
Harrenstien, K., Stahl, M K., and E J. Feinler, "DoD Internet host table specification", RFC 952, DOI 10.17487/RFC0952, , <https://www.rfc-editor.org/info/rfc952>.

Appendix A. Some Back Matter

Fusce viverra ipsum tempor finibus pharetra. Vestibulum fermentum porta neque et maximus. Aliquam tristique nibh in neque aliquam pharetra. Sed sapien felis, efficitur at finibus et, porttitor non quam. Nulla a ultrices nibh, ac commodo lacus. Integer vitae lorem ut sapien venenatis maximus. Morbi ut faucibus nunc, vitae pretium lorem. Aliquam sit amet tortor ut turpis dapibus ullamcorper. Proin at ligula nec magna molestie eleifend:
トヨタ 自動車 株式会社 (Toyota Jidōsha KK). This is a long comment line which extends well beyond the 72-character page width.

A.1. Contributors

We'd like to thank these contributors:

Roni Even
Huawei
David Hamelech 14
Tel Aviv 64953
Israel
Additional contact information:
רוני אבן
וואווי
דוד המלך 14
תל אביב 64953
ישראל

Reviews and helpful comments have also been received from ანა კიკაბიძე (Ana Kikabidze).

A.2. Arbitrarysuperscript in section title

Arbitrary text

Authors' Addresses

An Author
ElfTools
Midtskogveien 18
2020 Skedsmokorset
Norway
Roni Even
Huawei
David Hamelech 14
Tel Aviv 64953
Israel
Additional contact information:
רוני אבן
וואווי
דוד המלך 14
תל אביב 64953
ישראל
Hanako Tanaka
3-kai B-goshitsu
4-3-2 Hakusan, Bunkyo-ku, Tokyo
112-0001
Japan
Additional contact information:
田中花子 様
日本
112-0001
東京都
文京区 白山4丁目3番2号
3階B号室
No Org
Tokyo
112-0001
Japan
Bon Aventure
Université de Liège
Place du 20 Août 7
4000 Liège
Belgium
International Association for Cryptologic Research
A. Lindgren
Mellangården
Sevedstorp 125
Mariannelund
Sweden