Internet-Draft HTML RFC December 2016
Hildebrand Expires May 11, 2017 [Page]
RFC-Interest Pseudo Working Group
ɟ. H̭ildebrand (J. Hildebrand), Ed.
Čisco Śystems, Inc. (Cisco Systems, Inc.)
H. Flanagan, Ed.
RFC Editor

HyperText Markup Language Request For Comments Format


This document defines the HTML format that will be rendered from the canonical XML format for an RFC. The HTML output will include a default CSS to enable page layout.

Abstracts can have multiple <t>'s

Editorial Note

This note is to be removed before publishing as an RFC.

Discussion of this draft takes place on the rfc-interest mailing list (, which has its home page at

Editorial Note

This note is to be removed before publishing as an RFC.

A term
A def

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

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 2017-05-11.

Table of Contents

1. Introduction


1.1. Sub Section About Monospace Fonts

sub section paragraph

1.1.1. Sub-sub Section

sub section paragraph Sub-sub-sub Section

sub section paragraph Sub-sub-sub Section 2

sub section paragraph

moar paragraph

1.2. Sub Section 3

Fourscore and sevenyears ago, our fathers brought forth on this continent, a new nation, conceived in Liberty, and dedicated to the proposition that all men are created equal.

Now we are engaged in a great civil war, testing whether that nation, or any nation so conceived and so dedicated, can long endure. We are met on a great battle-field of that war. We have come to dedicate a portion of that field, as a final resting place for those who here gave their lives that that nation might live. It is altogether fitting and proper that we SHOULD do this.

Abraham Lincoln
This is a shorter blockquote example

Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur? Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?

1.3. Sub Section 4

sub section paragraph 4

This paragraph has a uninteresting commentaryemIETF erefstrongsub'supttSection 2—Paul.

2. top

A real section, with an anchor

H1 H2

One is the loneliest number that you'll ever do

Two can be as bad as one
It's the loneliest number since the number one.
Remember to do that comment.



This one covers two whole columns.

This one covers two whole rows.

Another thing
And another thing!

Second paragraph

  1. now


  2. ordered
    1. before
    2. A nested li
    3. And a reference to 2
  1. A dozen or so.
  2. Now, with bakers. It's all about [Bibble].
  1. after bakers, before meanings
  2. there are meaningless bakers
  1. who bake
  2. bread with meaning
  1. The meaning of life.
  2. The after-meaning of the after-life
  1. Get up every morning with a smile on your face
  2. Show the world all the love in your heart
  1. Upper case
  2. Above 26
  1. Wheels on a big rig
  2. Exercitation nisi quis in laborum ipsum esse excepteur culpa. Et pariatur anim labore pariatur qui adipisicing consequat quis. Occaecat fugiat ad mollit ipsum occaecat aliqua consectetur. Esse proident qui amet quis dolore consectetur proident sunt ipsum exercitation veniam exercitation amet. Nostrud exercitation magna officia incididunt deserunt incididunt eiusmod veniam esse minim non. Mollit non ad consectetur adipisicing nisi ex consequat qui proident officia laboris duis adipisicing. Velit commodo aliqua occaecat consequat nostrud anim ad ut. Quis aute eu culpa dolore ut esse ea est elit occaecat. In cupidatat ea ipsum est fugiat ad pariatur nulla.

This should be centered:

artwork does not
   have to be part of a figure.
                            --0xEE cummings
texting goes

This should be pushed right:

Just a step to the right
< hello, world >
        \   ^__^
         \  (oo)\_______
            (__)\       )\/\
                ||----w |
                ||     ||
Figure 1. It figures
Figure 2. Inline with <svg> element
Figure 3. Inline with XInclude (right)
Figure 4. SVG as a data: URI
Figure 5. Inline with <src> attribute (center)
Figure 6. Inline with local <src> attribute

Artwork can also be outside a figure. Here are two.

IETF logo
00000000  20 5f 5f 5f 5f 5f 5f 5f  5f 5f 5f 5f 5f 5f 5f 20  | ______________ |
00000010  0a 3c 20 68 65 6c 6c 6f  2c 20 77 6f 72 6c 64 20  |.< hello, world |
00000020  3e 0a 20 2d 2d 2d 2d 2d  2d 2d 2d 2d 2d 2d 2d 2d  |>. -------------|
00000030  2d 20 0a 20 20 20 20 20  20 20 20 5c 20 20 20 5e  |- .        \   ^|
00000040  5f 5f 5e 0a 20 20 20 20  20 20 20 20 20 5c 20 20  |__^.         \  |
00000050  28 6f 6f 29 5c 5f 5f 5f  5f 5f 5f 5f 0a 20 20 20  |(oo)\_______.   |
00000060  20 20 20 20 20 20 20 20  20 28 5f 5f 29 5c 20 20  |         (__)\  |
00000070  20 20 20 20 20 29 5c 2f  5c 0a 20 20 20 20 20 20  |     )\/\.      |
00000080  20 20 20 20 20 20 20 20  20 20 7c 7c 2d 2d 2d 2d  |          ||----|
00000090  77 20 7c 0a 20 20 20 20  20 20 20 20 20 20 20 20  |w |.            |
000000a0  20 20 20 20 7c 7c 20 20  20 20 20 7c 7c 0a        |    ||     ||.|

2.1. foo


Not fine
Sad weepy
Ugh. Really ugh.

What ever. I guess I should have an ordered list here:

  1. Won!
  2. Too!
#include <stdio.h>

int main(void)
    printf("hello, world\n");
    return 0;
Figure 7. This is a figure


This is an example of a single ABNF file split across several inline blocks. It should be recoverable with xmllint --xpath '//sourcecode[@name="yang.abnf"]/text()' test.x.xml.

module-stmt         = optsep module-keyword sep identifier-arg-str
                     "{" stmtsep
                     "}" optsep

Some text

submodule-stmt      = optsep submodule-keyword sep identifier-arg-str

Some text

                     "{" stmtsep
                     "}" optsep

Some text

module-header-stmts = ;; these stmts can appear in any order
                     [yang-version-stmt stmtsep]
                      namespace-stmt stmtsep
                      prefix-stmt stmtsep

Some text

submodule-header-stmts =
                     ;; these stmts can appear in any order
                     [yang-version-stmt stmtsep]
                      belongs-to-stmt stmtsep

Some text

meta-stmts          = ;; these stmts can appear in any order
                     [organization-stmt stmtsep]
                     [contact-stmt stmtsep]
                     [description-stmt stmtsep]
                     [reference-stmt stmtsep]

2.3. Python

Trying some Python code

def foo():
  print("hello, world!")

2.4. Long lines

This is gibberish: aklsdjalskjd aslkdj asldkj aslkdja sldkjasdklajd alkdjasdlkj dalkjd lajks dlkasjdaskjd asdlkjasd lkjds

2.5. With src

  "name": "draft-hildebrand-html-rfc",
  "version": "1.0.0",
  "description": "Tools for building xml2rfcv3 docs",
  "main": "index.js",
  "directories": {
    "example": "examples"
  "dependencies": {
    "bluebird": "3.3",
    "express": "4.13",
    "jade": "1.11",
    "libxmljs": "0.18",
    "resolve": "1.1",
    "rfc-preptool": "latest",
    "romanize": "0.1",
    "through2": "2.0",
    "vinyl-fs": "2.4",
    "xmljade": "latest"
  "devDependencies": {},
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  "repository": {
    "type": "git",
    "url": ""
  "author": "",
  "license": "BSD-2-Clause",
  "bugs": {
    "url": ""
  "homepage": ""

Some docs might talk about svg, and need examples thereof:

<svg width="100" height="100" xmlns="">
  <circle cx="50" cy="50" r="40"
          stroke="black" fill="white"

3. IANA Considerations


4. References

4.1. Normative References

Federal Agency on Technical Regulating and Metrology, "Information technology. Cryptographic data security. Signature and verification processes of [electronic] digital signature", GOST R34.10-2012, , (In Russian), <>.
Государственный стандарт Российской Федерации, "Информационная технология. Криптографическая защита информации. Процессы формирования и проверки электронной цифровой подписи", GOST R34.10-2012, , (In Russian), <>.
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP14, RFC2119, DOI10.17487/RFC2119, , <>.

4.2. Informative References

One, N., Bibble protocol spec, BibbleSpecs12-4444, , <>.
One, N., Bibble protocol spec, BibbleSpècs12-4444, , <>.
No One, No Two, and No Three, "Bibble use cases", BibbleSpecs12-4479, DOI10.17487/RFC2119, <>.
One, Ñ., Two, Ñ., and Ñ. Three, "Bi̬bble use cases", BibbleSpècs12-4479, DOI10.17487/RFC2119, <>.
Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Transport over TCP", STD69, RFC5734, DOI10.17487/RFC5734, , <>.
Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", STD69, RFC5730, DOI10.17487/RFC5730, , <>.
Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Domain Name Mapping", STD69, RFC5731, DOI10.17487/RFC5731, , <>.
Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Host Mapping", STD69, RFC5732, DOI10.17487/RFC5732, , <>.
Hollenbeck, S., "Extensible Provisioning Protocol (EPP) Contact Mapping", STD69, RFC5733, DOI10.17487/RFC5733, , <>.
Phillips, A. and M. Davis, "Tags for Identifying Languages", BCP47, RFC5646, , <>.
Flanagan, H. and N. Brownlee, "RFC Series Format Requirements and Future Development", RFC6949, DOI10.17487/RFC6949, , <>.

Appendix A. Doing things in appendices

This is where you would put an appendix

Appendix A.1. Sub-appendix

Have parts, too

And more parts

Appendix B. Another appendix

This one is just as useless, but started with a title attribute



Authors' Addresses

Joe Hildebrand (editor)
Cisco Systems, Inc.
1 Main Street
Suite 1
DenverCO 80202
Phone: +1-720-555-1212 VOICE
Fax: +1-303-555-1212 fax
URI: <>
Alternate contact information:
ɟöe H̭ildebrand (editor)
Čisco Śystems, Inc.
1 Main Street
Suite 1
DzenverCO 80202
Phone: +1-720-555-1212 VOICE
Fax: +1-303-555-1212 fax
URI: <>

Heather Flanagan (editor)
RFC Editor
Where the
Streets have no name
Prepared: Rendered: