One document matched: draft-carpenter-renum-needs-work-04.xml
<?xml version="1.0"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<!-- This is built from a template for a generic Internet Draft. Suggestions for
improvement welcome - write to Brian Carpenter, brc @ zurich.ibm.com -->
<?rfc toc="yes"?> <!-- You want a table of contents -->
<!-- ?rfc symrefs="yes" ?--> <!-- Uncomment this if you want symbolic labels for references -->
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?> <!-- This sorts the references -->
<?rfc iprnotified="no" ?> <!-- Change to "yes" if someone has disclosed IPR for the draft -->
<?rfc compact="yes"?>
<!-- You need one entry like the following for each RFC referenced -->
<!ENTITY RFC2629 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2629'>
<!ENTITY RFC2026 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2026'>
<!ENTITY RFC1311 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.1311'>
<!ENTITY RFC3967 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3967'>
<!ENTITY RFC3933 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3933'>
<!ENTITY RFC3934 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3934'>
<!ENTITY RFC3978 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3978'>
<!ENTITY RFC3669 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3669'>
<!ENTITY RFC3932 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3932'>
<!ENTITY RFC3979 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3979'>
<!ENTITY RFC2028 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2028'>
<!ENTITY RFC2031 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2031'>
<!ENTITY RFC3677 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3677'>
<!ENTITY RFC3233 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3233'>
<!ENTITY RFC3935 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3935'>
<!ENTITY RFC2418 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2418'>
<!ENTITY RFC2438 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2438'>
<!ENTITY RFC3710 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3710'>
<!ENTITY RFC2850 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2850'>
<!ENTITY RFC4052 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4052'>
<!ENTITY RFC4053 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4053'>
<!ENTITY RFC3777 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3777'>
<!ENTITY RFC3005 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3005'>
<!ENTITY RFC3184 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3184'>
<!ENTITY RFC3683 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3683'>
<!ENTITY RFC2434 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2434'>
<!ENTITY RFC4071 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4071'>
<!ENTITY RFC4371 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4371'>
<!ENTITY RFC3160 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3160'>
<!ENTITY RFC2223 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2223'>
<!ENTITY RFC2860 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2860'>
<!ENTITY RFC4333 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4333'>
<!ENTITY RFC1264 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.1264'>
<!ENTITY RFC2360 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2360'>
<!ENTITY RFC3552 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3552'>
<!ENTITY DRAFT-tao SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.hoffman-taobis.xml">
<!ENTITY DRAFT-disc SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.iesg-discuss-criteria.xml">
iab-liaison-guidelines
<!ENTITY DRAFT-iabl SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.iab-liaison-guidelines.xml">
<!-- This defines the specific filename and version number of your draft (and inserts the appropriate IETF boilerplate -->
<rfc ipr="full3978" docName="draft-carpenter-procdoc-roadmap-05">
<!-- From here on code by example -->
<front>
<title abbrev="IETF Process: Informal Guide">The IETF Process: an Informal Guide</title>
<author initials="B. E." surname="Carpenter (ed)" fullname="Brian Carpenter (ed)">
<organization abbrev="IBM">IBM</organization>
<address>
<postal>
<street>8 Chemin de Blandonnet</street>
<country>Switzerland</country>
<code></code>
<region></region>
<city>1214 Vernier</city>
</postal>
<email>brc@zurich.ibm.com</email>
</address>
</author>
<date month="August" year="2006" />
<area>General</area>
<workgroup>Network Working Group</workgroup>
<abstract>
<t>This document is an informal guide to various IETF process documents,
intended both to assist IETF participants and
to support possible discussions about process reform. </t>
</abstract>
</front>
<middle>
<section anchor="intro" title="Introduction">
<t>BCP 9 <xref target="RFC2026"/> has been the basis for the IETF standards process for many years. However, many other process documents exist, some of which are partial updates to BCP 9. This situation is confusing and would ideally be resolved by a clear set of interlocking documents. The present document suggests a structured way of looking at the existing documents. </t>
<t>It is difficult to linearise a complicated and interlocked process.
This document presents a roadmap in one
particular order, but that is not intended to imply priority or importance,
and it cannot capture all interactions between components.</t>
</section>
<section anchor="outline" title="Outline of roadmap">
<t> For readability of what follows, this section simply lists the process document structure.
The following section repeats this structure with explanatory text and references.</t>
<t></t>
<list>
<t>Modifying the process</t>
<t>General description of workflow in the IETF</t>
<t>Definition of standards track and related document types</t>
<list>
<t>Specifications</t>
<t>Information</t>
</list>
<t>Intellectual Property</t>
<list>
<t>Rights in Contributions</t>
<t>Rights in Technology</t>
<t>Trademarks</t>
</list>
<t>Review and approval process</t>
<list>
<t>Criteria for review</t>
<t>Criteria for approval</t>
<list>
<t>Appeal process</t>
</list>
</list>
<t>Bodies involved in the process</t>
<list>
<t>WG procedures</t>
<t>IESG</t>
<t>Review panel TBD</t>
<t>IAB</t>
<list>
<t>Liaison management</t>
</list>
<t>Nomcom</t>
</list>
<t>Conduct of participants</t>
<t>Publication process</t>
<list>
<t>Requirements</t>
<t>Format and mechanics for drafts</t>
<t>Format and mechanics for archival publications</t>
<t>Direct submissions to RFC Editor</t>
</list>
<t>Registration process</t>
<list>
<t>Requirements</t>
<t>Guidelines for authors</t>
<t>Assignment criteria</t>
<t>Format and mechanics</t>
</list>
<t>Administration</t>
</list>
</section>
<section anchor="details" title="Details of guide">
<t>Note 1: RFC numbers have been used rather than BCP numbers,
for convenient lookup. Most of the cited RFCs are BCPs. Of course, many
of them may need updating.</t>
<t>Note 2: Early drafts of this document included references to drafts proposing changes
to the standards process. These have been removed to make this document a more stable
reference.</t>
<t></t>
<list style="symbols">
<t>Modifying the process
<vspace/>Formally, IETF processes are described in Best Current Practices
(BCPs) published as RFCs. <xref target="RFC2026"/> defines how BCPs
are discussed and approved. A general description of how the IETF modifies its own
processes does not exist, but probably should. An experimental
procedure is described in <xref target="RFC3933"/> (also see
http://www.ietf.org/IESG/content/experiments.html).
</t>
<t>General description of workflow in the IETF
<vspace/>This document does not exist, although
the Tao (<xref target="RFC3160"/>,
to be replaced by <xref target="I-D.hoffman-taobis"/>)
offers contains most of it informally:
<vspace/>How ideas for new work enter the IETF, reach a BOF, enter IAB or IRTF
discussion, and possibly become material for a new or existing WG. How WGs are
chartered - the Area Director's role. How specific proposals become
drafts and flow through
the development, review and approval process. <vspace blankLines="1" /></t>
<t>Definition of standards track and related document types.
<vspace/>This material is currently embedded in <xref target="RFC2026"/>.
Additional requirements for routing protocols are currently defined in
<xref target="RFC1264"/>.
The newtrk
WG was chartered to revise the standards track - multiple
proposals have been floated, but no conclusions have been reached. </t>
<list style="symbols">
<t>Specifications
<vspace/>This material is currently embedded in
<xref target="RFC2026"/>, covering
standards track, BCP and Experimental documents.
The STD (standard) designation is documented in <xref target="RFC1311"/>.
A variance procedure for
down-level normative references is in <xref target="RFC3967"/>.
A specific process for advancing MIB documents is in
<xref target="RFC2438"/>.</t>
<t>Information
<vspace/>This material is currently embedded in
<xref target="RFC2026"/>, covering
Informational and Historic documents. A distinction between obsolete
and deprecated documents is not currently made.</t>
</list>
<t>Intellectual Property</t>
<list style="symbols">
<t>Rights in Contributions
<vspace/><xref target="RFC3978"/></t>
<t>Rights in Technology
<xref target="RFC3979"/> (Guidelines,
<xref target="RFC3669"/>) </t>
<t>Trademarks
<vspace/><xref target="RFC3978"/></t>
<t>IETF Trust <xref target="RFC4371"/><vspace blankLines="1" /></t>
</list>
<t>Review and approval process
<vspace/>This material is currently embedded in <xref target="RFC2026"/>. </t>
<list style="symbols">
<t>Criteria for review
<vspace/>Various review teams exist in different IETF Areas,
with their own technical criteria. For the General Area, see
http://www.alvestrand.no/ietf/gen/art/review-guidelines.html </t>
<t>Criteria for approval
<vspace/>Material on current IESG practice can be found in
<xref target="I-D.iesg-discuss-criteria"/></t>
<list style="symbols">
<t>Appeal process
<vspace/>This material is currently embedded in <xref target="RFC2026"/>.
<vspace blankLines="1" /></t>
</list>
</list>
<t>Bodies involved in the process
<vspace/>Bodies involved <xref target="RFC2028"/>;
Defining the IETF <xref target="RFC3233"/>;
Mission Statement <xref target="RFC3935"/>.</t>
<list style="symbols">
<t>WG procedures
<xref target="RFC2418"/></t>
<t>IESG
<xref target="RFC3710"/></t>
<t>IAB
<xref target="RFC2850"/></t>
<list style="symbols">
<t>Liaison management
<vspace/><xref target="RFC4052"/>, <xref target="RFC4053"/>,
draft-iab-liaison-guidelines</t>
</list>
<t>Nomcom
<xref target="RFC3777"/> ,
draft-klensin-nomcom-term </t>
<t>Relationship to ISOC
<vspace/><xref target="RFC2031"/>,
<xref target="RFC3677"/> <vspace blankLines="1" /></t>
</list>
<t>Conduct of participants
<vspace/><xref target="RFC3005"/>, <xref target="RFC3184"/>,
<xref target="RFC3683"/>, <xref target="RFC3934"/>,
and also discussed in <xref target="RFC2418"/>
and in the Tao (<xref target="RFC3160"/>, draft-hoffman-taobis). <vspace blankLines="1" /></t>
<t>Publication process</t>
<list style="symbols">
<t>Requirements
<vspace/>This is the subject of the techspec BOFs at IETF 64 and 65.
See draft-mankin-pub-req.</t>
<t>Format and mechanics for drafts
<vspace/>http://www.ietf.org/ietf/1id-guidelines.html</t>
<t>Format and mechanics for archival publications
<vspace/>See draft-hoffman-rfc-author-guide for a minimalist version,
or draft-rfc-editor-rfc2223bis for a version including other topics.
<xref target="RFC2223"/> is the
published version today. Those writing standards will find the following
especially useful: <xref target="RFC2360"/>,
<xref target="RFC2434"/>, <xref target="RFC3552"/>.</t>
<t>Direct submissions to RFC Editor
<xref target="RFC3932"/><vspace blankLines="1" /></t>
</list>
<t>Registration process</t>
<list style="symbols">
<t>Requirements
<xref target="RFC2860"/> </t>
<t>Guidelines for authors
<vspace/><xref target="RFC2434"/>, draft-narten-iana-considerations-rfc2434bis</t>
<t>Assignment criteria
<vspace/>draft-klensin-iana-reg-policy</t>
<t>Format and mechanics
<vspace/>Case by case at IANA web site. <vspace blankLines="1" /></t>
</list>
<t>Administration
<vspace/><xref target="RFC4071"/>,
<xref target="RFC4371"/>,
<xref target="RFC4333"/>,
draft-alvestrand-subpoena </t>
</list>
</section>
<section anchor="security" title="Security Considerations">
<t>This document has no security implications for the Internet.</t>
</section>
<section anchor="iana" title="IANA Considerations">
<t>This document requires no action by the IANA. However, it does mention how IANA's
registration functions are documented.</t>
</section>
<section anchor="acknowledgement" title="Acknowledgements">
<t>Useful comments on this document were made by: Harald Alvestrand, Scott Bradner,
Spencer Dawkins, Leslie Daigle, John Klensin, and others.
</t>
<t>This document was produced using the xml2rfc tool <xref target="RFC2629"/>.</t>
</section>
<section anchor ="changes" title="Change log [RFC Editor: please remove this section]">
<t>draft-carpenter-procdoc-roadmap-05: removed references to
open drafts, renamed as Guide, 2006-08-02</t>
<t>draft-carpenter-procdoc-roadmap-04: minor additions, tuned Abstract
and Introduction, 2006-02-20</t>
<t>draft-carpenter-procdoc-roadmap-03: minor additions, 2005-12-20</t>
<t>draft-carpenter-procdoc-roadmap-02: minor additions, 2005-10-11</t>
<t>draft-carpenter-procdoc-roadmap-01: minor additions, 2005-09-20</t>
<t>draft-carpenter-procdoc-roadmap-00: original version, 2005-08-22</t>
</section>
</middle>
<back>
<references title="Normative References">
&RFC2026;
&RFC2028;
&RFC2360;
&RFC2418;
&RFC2434;
&RFC2438;
&RFC2850;
&RFC3005;
&RFC3184;
&RFC3233;
&RFC3552;
&RFC3677;
&RFC3683;
&RFC3777;
&RFC3932;
&RFC3933;
&RFC3934;
&RFC3935;
&RFC3967;
&RFC3978;
&RFC3979;
&RFC4052;
&RFC4053;
&RFC4071;
&RFC4333;
&RFC4371;
</references>
<references title="Informative References">
&RFC1264;
&RFC1311;
&RFC2031;
&RFC2223;
&RFC2629;
&RFC2860;
&RFC3160;
&RFC3669;
&RFC3710;
&DRAFT-tao;
&DRAFT-disc;
&DRAFT-iabl;
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 06:43:24 |