<Working Group Name>		
Internet Draft	<Initial. Lastname>	
Document: draft-ietf-wgname-docname-00.txt	<Affiliation>	
Expires: October 2002	April 2002	

<Title>

Status of this Memo

All Internet-Drafts must begin with ONE of the following three statements: 
This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026 []. 

This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026 except that the right to produce derivative works is not granted. 

This document is an Internet-Draft and is NOT offered in accordance with Section 10 of RFC2026, and the author does not provide the IETF with any rights other than to publish as an Internet-Draft 
Any submission which does not include one (and only one) of the above three statements will be returned to the submitter. The IETF Secretariat will NOT add this text.

The following verbatim statement must follow the optional opening sentence:
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups.  Note that      other groups may also distribute working documents as Internet-Drafts.

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

The list of current Internet-Drafts can be accessed at
     http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
     http://www.ietf.org/shadow.html.

For potential updates to the above required-text see:
http://www.ietf.org/ietf/1id-guidelines.txt

Abstract

<Type your abstract here.> 

Conventions used in this document

<Add any conventions that you use in your document here.  Common conventions are listed below.>

In examples, "C:" and "S:" indicate lines sent by the client and server respectively.
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 RFC-2119 [].

Table of Contents

1. <Section 1 heading as appropriate>
1.1 <Sub-section 1.1 heading as appropriate>
2. <Section 2 heading as appropriate>
2.1 <Sub-section 2.1 heading as appropriate>
3. <Section 3 heading as appropriate>
4. <Section 4 heading as appropriate>
5. Formal Syntax
Security Considerations
References
Acknowledgments
Author's Addresses

1.	<Section 1 heading as appropriate>

<Text for this section>

1.1	<Sub-section 1.1 heading as appropriate>

<Text for this section>

2.	<Section 2 heading as appropriate>

<Text for this section>

2.1	<Sub-section 2.1 heading as appropriate>

<Text for this section>

3.	<Section 3 heading as appropriate>

<Text for this section>

4.	<Section 4 heading as appropriate>

<Text for this section>

5.	Formal Syntax

< Commonly used grammar is BNF grammar defined in RFC-2234.  Suggested wording.>

The following syntax specification uses the augmented Backus-Naur Form (BNF) as described in RFC-2234 [].

<Define your formal syntax here.>

Security Considerations

<Every draft MUST have a security section.>

References

< Your references will be listed here. View "Page Layout" if they are not currently visible. >

Acknowledgments

<Add any acknowledgements>

Author's Addresses

<Firstname> <Lastname>
<Affiliation>
<Address>
Phone: <optional>
Email: <Your email address>