An Example of Using XML for an Internet Draft

Internet-Draft	XML Example	September 2014
Smith & Jones	Expires 15 March 2015	[Page]

Abstract

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.¶

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 5 March 2015. ¶

Copyright Notice

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. ¶

1. Introduction

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 to Section 2, and one to Figure 1, both of which appear later in the document.¶

1.1. Terminology

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].¶

2. The Protocol Being Described

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.¶

The IETF web site is quite nice, isn't it? Unlike other web sites, it doesn't use gratuitous vertical space.¶

3. Basic Lists

Bulleted lists are good for items that are not ordered: ¶

This is the first item.¶
This is the second item. Here comes a sub-list:¶
- This is the first sub-item.¶
- This is the second sub-item¶
  
  and some more detail on the second sub-item.¶
This is the item after the sub-list.¶

Numbered lists are good for items that are ordered: ¶

This is the first item.¶
This is the second item. Here comes a sub-list, but with letters: ¶
1. This is the first sub-item.¶
2. This is the second sub-item¶
This is the item after the sub-list.¶

And an example of hanging indent. ¶

Trees: These are bigger plants
Lichen: These are smaller plants

And the always-interesting "format" for lists. ¶

--1--: An element that gets a funny bullet.¶

4. Figures

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.

Figure 1: This could be haiku

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¶

5. Tables

The following is a table example.¶

These are sometimes called "inert" gasses.¶

Table 1: 'The Noble Gases'
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.¶

Table 2
Time	Mood
Morning	Happy!
Afternoon	Happy!
Evening	Somber

9. References

9.1. Normative References

[RFC2119]: Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997 , <https://www.rfc-editor.org/info/rfc2119>.

9.2. Informative References

[RED]: Floyd, S. and V. Jacobson, "Random Early Detection (RED) gateways for Congestion Avoidance", IEEE/ACM Transactions on Networking 1(4) 397--413, August 1993 , <http://www.aciri.org/floyd/papers/early.pdf>.
[RFC6949]: Flanagan, H. and N. Brownlee, "RFC Series Format Requirements and Future Development", RFC 6949, May 2013 , <https://www.rfc-editor.org/info/rfc6949>. This is a primary reference work.

Index

I ¶

I ¶
- Introduction¶
  
  Introduction ¶
  - verbiage¶