| Internet-Draft | XML Example | September 2014 |
| Smith & Jones | Expires 15 March 2015 | [Page] |
This is an example of an abstract. It is a short paragraph that gives an overview of the document in order to help the reader determine whether or not they are interested in reading further.¶
This isn't a real RFC, just an example.¶
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 athttp://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 5 March 2015.¶
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 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.¶
This is the first paragraph of the introduction to this document. This introduction is probably much shorter than it would be for a real Internet Draft.¶
Something to note about this paragraph is that it has a pointer toSection 2, and one toFigure 1, both of which appear later in the document.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in[RFC2119].¶
This is a reference to[RFC6949]. Actually, the reference itself is not all that interesting, but the way that the reference is incorporated is. Note that the inclusion of RFC 2119 was done at the top of the XML, while the information for RFC 6949 is done directly in the references section.¶
TheIETF web site isquitenice,isn't it? Unlike other web sites, it doesn't use gratuitous vertical space.¶
Bulleted lists are good for items that are not ordered:¶
This is the second item. Here comes a sub-list:¶
Numbered lists are good for items that are ordered:¶
This is the second item. Here comes a sub-list, but with letters:¶
And an example of hanging indent.¶
And the always-interesting "format" for lists.¶
The following is a figure with a caption. Also, it uses the ampersand (&) and less than (<) characters in the example text.¶
The ampersand (&) and less than (<) are two characters that need escaping.
Here are two short figures with no titles and with odd alignment.¶
This might appear in the center.¶
This might appear right-aligned.¶
Here is a figure that is actually pulled from somewhere else. Remember to check whether that file still exists.cs¶
The following is a table example.¶
These are sometimes called "inert" gasses.¶
| Name | Symbol | Atomic Number |
|---|---|---|
| Helium | He | 2 |
| Neon | Ne | 10 |
| Argon | Ar | 18 |
| Krypton | Kr | 36 |
| Xenon | Xe | 54 |
| Radon | Rn | 86 |
Source: Chemistry 101¶
The following is a right-aligned table with "full" (but not "all") lines between cells.¶
| Time | Mood |
|---|---|
| Morning | Happy! |
| Afternoon | Happy! |
| Evening | Somber |
None.¶
There are no security considerations for an imaginary Internet Draft.¶
Some of the things included in this draft came from Elwyn Davies' templates.¶