ࡱ > !` Z R bjbj\\ . > > : # jb jb jb jb jb jb jb ~b N N N 8 \ ~b E n B ȝ ¤ ¤ ¤ 4 $ h x jb jb jb ¤ ¤ ' ' ' & jb ¤ jb ¤ ' ' ' t jb jb ¤ + ֮N N : 0 E W x t x jb ' ϳ X E ~b D b D c ~b b c ~b ~b ~b jb jb jb jb jb jb
draft-ietf-wgname-docname-00.txt
INFO (REMOVE): Version 2.0 J. Touch February 12, 2007
INFO (REMOVE): Lines in RED are instructions for the author and *MUST* be removed completely.
INFO (REMOVE): Lines in YELLOW are placeholders and *MUST* be replaced by the author. Boilerplate is shown in BLUE and should not be omitted. Boilerplate shown in GREEN is included by choice.
INFO (REMOVE): Update the Intended status in the header as needed.
Status of this Memo
By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79.
INFO (REMOVE): Choose at most ONE of the following and omit others (see BCP 78 for explanation):
This document may not be modified, and derivative works of it may not be created.
This document may not be modified, and derivative works of it may not be created, other than to extract section XX as-is for separate use.
This document may not be modified, and derivative works of it may not be created, except to publish it as an RFC and to translate it into languages other than English.
This document may not be modified, and derivative works of it may not be created, except to publish it as an RFC and to translate it into languages other than English, other than to extract section XX as-is for separate use.
INFO (REMOVE): The following single line may be included on I-Ds only:
This document may only be posted in an Internet-Draft.
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
This Internet-Draft will expire on IF SAVEDATE \@ "M" \* MERGEFORMAT 2 = 1 July IF SAVEDATE \@ "M" \* MERGEFORMAT \* MERGEFORMAT 2 = 2 August IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 3 September IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 4 October IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 5 November IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 6 December IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 7 January IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 8 February IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 9 March IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 10 April IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 11 May IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 12 June "Fail" \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT August \* MERGEFORMAT August DATE \@ "d," 12, IF SAVEDATE \@ "M" \* MERGEFORMAT 2 < 7 SAVEDATE \@ "YYYY" \* MERGEFORMAT 2007 IF SAVEDATE \@ "M" \* MERGEFORMAT 12 > 6 = SAVEDATE \@ "YYYY" \* MERGEFORMAT 2006 + 1 \* MERGEFORMAT 2007 "Fail" \* MERGEFORMAT \* MERGEFORMAT 2007 \* MERGEFORMAT 2007.
Copyright Notice
Copyright (C) The IETF Trust ( SAVEDATE \@ "yyyy" \* MERGEFORMAT 2007).
Abstract
Conventions used in this document
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 REF _Ref86333103 \w \h \* MERGEFORMAT [1].
Table of Contents
TOC \o \h \z \u HYPERLINK \l "_Toc159054101" 1. Introduction PAGEREF _Toc159054101 \h 3
HYPERLINK \l "_Toc159054102" 1.1. PAGEREF _Toc159054102 \h 5
HYPERLINK \l "_Toc159054103" 2. PAGEREF _Toc159054103 \h 5
HYPERLINK \l "_Toc159054104" 2.1. PAGEREF _Toc159054104 \h 5
HYPERLINK \l "_Toc159054105" 2.1.1. PAGEREF _Toc159054105 \h 5
HYPERLINK \l "_Toc159054106" 2.1.2. PAGEREF _Toc159054106 \h 6
HYPERLINK \l "_Toc159054107" 2.1.2.1. <2.1.2.1 (L4)> PAGEREF _Toc159054107 \h 6
HYPERLINK \l "_Toc159054108" 2.1.2.1.1. <(L5)> PAGEREF _Toc159054108 \h 6
HYPERLINK \l "_Toc159054109" 2.1.2.1.1.1. <(L6)> PAGEREF _Toc159054109 \h 6
HYPERLINK \l "_Toc159054110" 2.1.2.1.1.1.1. <(L7)> PAGEREF _Toc159054110 \h 6
HYPERLINK \l "_Toc159054111" 2.1.2.1.1.1.1.1. <(L8)> PAGEREF _Toc159054111 \h 6
HYPERLINK \l "_Toc159054112" 2.1.2.1.1.1.1.1.1. <(L9)> PAGEREF _Toc159054112 \h 6
HYPERLINK \l "_Toc159054113" 3. PAGEREF _Toc159054113 \h 6
HYPERLINK \l "_Toc159054114" 4. PAGEREF _Toc159054114 \h 6
HYPERLINK \l "_Toc159054115" 5. Formal Syntax PAGEREF _Toc159054115 \h 6
HYPERLINK \l "_Toc159054116" 6. Security Considerations PAGEREF _Toc159054116 \h 7
HYPERLINK \l "_Toc159054117" 7. IANA Considerations PAGEREF _Toc159054117 \h 7
HYPERLINK \l "_Toc159054118" 8. Conclusions PAGEREF _Toc159054118 \h 7
HYPERLINK \l "_Toc159054119" 9. Acknowledgments PAGEREF _Toc159054119 \h 7
HYPERLINK \l "_Toc159054120" APPENDIX A: First Appendix PAGEREF _Toc159054120 \h 8
HYPERLINK \l "_Toc159054121" A.1. First Header level 1 PAGEREF _Toc159054121 \h 8
HYPERLINK \l "_Toc159054122" A.2. Second Header level 1 PAGEREF _Toc159054122 \h 8
HYPERLINK \l "_Toc159054123" A.2.1. H2 PAGEREF _Toc159054123 \h 8
HYPERLINK \l "_Toc159054124" A.2.1.1. H3 PAGEREF _Toc159054124 \h 8
HYPERLINK \l "_Toc159054125" A.2.1.1.1. H4 PAGEREF _Toc159054125 \h 8
HYPERLINK \l "_Toc159054126" A.2.1.1.1.1. H5 PAGEREF _Toc159054126 \h 8
HYPERLINK \l "_Toc159054127" 10. References PAGEREF _Toc159054127 \h 9
HYPERLINK \l "_Toc159054128" 10.1. Normative References PAGEREF _Toc159054128 \h 9
HYPERLINK \l "_Toc159054129" 10.2. Informative References PAGEREF _Toc159054129 \h 9
HYPERLINK \l "_Toc159054130" Author's Addresses PAGEREF _Toc159054130 \h 10
HYPERLINK \l "_Toc159054131" Intellectual Property Statement PAGEREF _Toc159054131 \h 10
HYPERLINK \l "_Toc159054132" Disclaimer of Validity PAGEREF _Toc159054132 \h 10
Introduction
If MIB/PIB items are included, each must include one of the following disclaimers (the latter if IANA maintains the MIB):
Copyright (C) The IETF Trust ( SAVEDATE \@ "yyyy" \* MERGEFORMAT 2007). This version of this MIB module is part of RFC XXXX; see the RFC itself for full legal notices.
Copyright (C) The IETF Trust ( SAVEDATE \@ "yyyy" \* MERGEFORMAT 2007). The initial version of this MIB module was published in RFC XXXX; for full legal notices see the RFC itself. Supplementary information may be available at: http://www.ietf.org/copyrights/ianamib.html.
Unnumbered list:
item 1 and this one wraps to the next line, eventually, to show how subsequent lines are indented
item 2
item 3
Numbered list:
item 1
item 2
item 3
Numbered list:
item 1 - right click, modify bullets and numbering to "restart" numbering for the first paragraph of a new list, like this one
item 2
item 3
And this is an ASCII figure:
Draw me in "RFC ASCII figure"
+------------------------------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+------------------------------------------------+
Add a caption as here.
<2.1.2.1 (L4)>
<(L5)>
<(L6)>
<(L7)>
<(L8)>
<(L9)>
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 REF _Ref86156304 \r \h [2].
Security Considerations
INFO (REMOVE): Every draft MUST have a security section.
IANA Considerations
INFO (REMOVE): Every draft MUST have an IANA section, although it may be removed prior to publication by the RFC Editor if null.
Conclusions
Acknowledgments
INFO (REMOVE): The author of this template would appreciate if you would keep the following line in your final IDs and RFCs:
This document was prepared using 2-Word-v2.0.template.dot.
First Appendix
INFO (REMOVE): Starts on a new page. These are optional.
INFO (REMOVE): Careful with headers in appendices - they won't renumber when moved in/out levels in outline mode. Only Headers 1-9 do that trick, as used in the body of the RFC!
First Header level 1
Text
Second Header level 1
Text
H2
Text
H3
Text
H4
Text
H5
Text
References
INFO (REMOVE): Manually insert a page break before this section if after appendices
INFO (REMOVE): Authors can use either the auto-numbered references OR the named references; typically, these would not be mixed in a single document. This template includes both examples for illustration of the two variations.
Normative References
INFO (REMOVE): Normative refs are references to standards documents **required** to understand this doc. These are usually Standards-track and BCP RFCs, or external (IEEE, ANSI, etc.) standards, but may include other publications.
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
Crocker, D. and Overell, P.(Editors), "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, Internet Mail Consortium and Demon Internet Ltd., November 1997.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2234] Crocker, D. and Overell, P.(Editors), "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, Internet Mail Consortium and Demon Internet Ltd., November 1997.
Informative References
INFO (REMOVE): Informative refs are those that are not standards or standards not required to understand this doc. These are usually informative RFCs, internet-drafts (avoid if possible), and other external documents.
Faber, T., Touch, J. and W. Yue, "The TIME-WAIT state in TCP and Its Effect on Busy Servers", Proc. Infocom 1999 pp. 1573-1583.
[Fab1999] Faber, T., Touch, J. and W. Yue, "The TIME-WAIT state in TCP and Its Effect on Busy Servers", Proc. Infocom 1999 pp. 1573-1583.
Author's Addresses
Phone:
Email:
Phone:
Email:
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietfipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The IETF Trust ( SAVEDATE \@ "yyyy" \* MERGEFORMAT 2007).
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the Internet Society.
Internet-Draft SAVEDATE \@ "MMMM yyyy" \* MERGEFORMAT February 2007
Expires IF SAVEDATE \@ "M" \* MERGEFORMAT 2 = 1 July IF SAVEDATE \@ "M" \* MERGEFORMAT \* MERGEFORMAT 2 = 2 August IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 3 September IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 4 October IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 5 November IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 6 December IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 7 January IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 8 February IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 9 March IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 10 April IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 11 May IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 12 June "Fail" \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT August \* MERGEFORMAT August DATE \@ "d," 12, IF SAVEDATE \@ "M" \* MERGEFORMAT 2 < 7 SAVEDATE \@ "YYYY" \* MERGEFORMAT 2007 IF SAVEDATE \@ "M" \* MERGEFORMAT 12 > 6 = SAVEDATE \@ "YYYY" \* MERGEFORMAT 2006 + 1 \* MERGEFORMAT 2007 "Fail" \* MERGEFORMAT \* MERGEFORMAT 2007 \* MERGEFORMAT 2007 [Page PAGE 11]
Internet Draft
Intended status: DATE \@ "MMMM d, yyyy" February 12, 2007
Expires: IF SAVEDATE \@ "M" \* MERGEFORMAT 2 = 1 July IF SAVEDATE \@ "M" \* MERGEFORMAT \* MERGEFORMAT 2 = 2 August IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 3 September IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 4 October IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 5 November IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 6 December IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 7 January IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 8 February IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 9 March IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 10 April IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 11 May IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 12 June "Fail" \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT August \* MERGEFORMAT August IF SAVEDATE \@ "M" \* MERGEFORMAT 2 < 7 SAVEDATE \@ "YYYY" \* MERGEFORMAT 2007 IF SAVEDATE \@ "M" \* MERGEFORMAT 12 > 6 = SAVEDATE \@ "YYYY" \* MERGEFORMAT 2006 + 1 \* MERGEFORMAT 2007 "Fail" \* MERGEFORMAT \* MERGEFORMAT 2007 \* MERGEFORMAT 2007
Expires IF SAVEDATE \@ "M" \* MERGEFORMAT 2 = 1 July IF SAVEDATE \@ "M" \* MERGEFORMAT \* MERGEFORMAT 2 = 2 August IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 3 September IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 4 October IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 5 November IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 6 December IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 7 January IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 8 February IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 9 March IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 10 April IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 11 May IF SAVEDATE \@ "M" \* MERGEFORMAT 12 = 12 June "Fail" \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT June \* MERGEFORMAT August \* MERGEFORMAT August DATE \@ "d," 12, IF SAVEDATE \@ "M" \* MERGEFORMAT 2 < 7 SAVEDATE \@ "YYYY" \* MERGEFORMAT 2007 IF SAVEDATE \@ "M" \* MERGEFORMAT 12 > 6 = SAVEDATE \@ "YYYY" \* MERGEFORMAT 2006 + 1 \* MERGEFORMAT 2007 "Fail" \* MERGEFORMAT \* MERGEFORMAT 2007 \* MERGEFORMAT 2007 [Page PAGE 1]
" * ; F G H P Q T \ ^ _ d e f w * ? T
B _ ` ĿĿķ粷筨{vqv *h *hP hP hP *h,uc hP hoo *h^ hoo *hD# hD# *hD# *hs *h,uc *hp^ *h0 *h~5 hU7 *hqE *h *h~5 hBX
*h~5 ^J *h~5 h[0 ^J *h<