Network Working Group S. Bradner
Internet-Draft Harvard University
October 2004
Sample ISD for the IETF Standards Process
<draft-ietf-newtrk-sample-isd-stdproc-00.txt>
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 RFC 3668.
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
Abstract
This is a sample Internet Standards Documentation (ISD) for the IETF
Standards Process. This document follows the model proposed in
draft-ietf-newtrk-isd-repurposing-isd-00.
Copyright Notice
Copyright (C) The Internet Society. (2004)
1. Introduction
This is a sample Internet Standards Documentation (ISD) for the IETF
Standards Process. This document follows the model proposed in
draft-ietf-newtrk-isd-repurposing-isd-00. This sample is written as
if the ISD process started being used in 1993 so to show a possible
history feature.
Bradner [Page 1]
Internet-Draft ISD for IETF Standards Process October 2004
2. ISD for the Internet standards Process
IETF Internet Standards Documentation
Name of ISD: ISD xxxx: The IETF Internet Standards Process
Last update: 17-Oct-2004
Maintainer: IESG
A: Abstract
This ISD documents the process currently used by the Internet
community for the standardization of protocols and procedures. The
Internet Standards process is an activity of the Internet Society
that is organized and managed on behalf of the Internet community by
the Internet Architecture Board (IAB) and the Internet Engineering
Steering Group (IESG).
B: Documents making up the Standard
RFC 2026
The Internet Standards Process -- Revision 3, S. Bradner (Ed.),
October 1996. (Status: BCP)
The Internet Standards Process described in this document is
concerned with all protocols, procedures, and conventions that are
used in or by the Internet, whether or not they are part of the
TCP/IP protocol suite. In the case of protocols developed and/or
standardized by non-Internet organizations, however, the Internet
Standards Process normally applies to the application of the
protocol or procedure in the Internet context, not to the
specification of the protocol itself.
The goals of the Internet Standards Process are:
o technical excellence;
o prior implementation and testing;
o clear, concise, and easily understood documentation;
o openness and fairness; and
o timeliness.
The procedures described in this document are designed to be fair,
open, and objective; to reflect existing (proven) practice; and
to be flexible.
The community needs this document because it spells out the way we
develop standards, the steps along the way, and the ways
disagreements and intellectual property rights are handled. [note
in draft - text from 9 Jul 96 Protocol Action announcement]
After 2026 had been used in the IETF for a number of years it
became clear that the intellectual property rights (IPR) section
(Section 10) was confusing because it mixed up patent rights,
Bradner [Page 2]
Internet-Draft ISD for IETF Standards Process October 2004
copyrights and trademarks without making the different rules for
the different types of rights clear. In addition the
understanding of what constituted a contribution to the IETF
evolved. Because of this two new RFCs were developed (RFC 3667
and RFC 3668) to clarify the IPR issues.
RFC 3667
IETF Rights in Contributions, S. Bradner (Ed.), February 2004.
(Status: BCP)
This document (with RFC 3668) replaces section 10 of RFC 2026, and
provides a much more detailed description of the considerations
regarding intellectual property that need to be taken into account
when working in the IETF.
Particular attention is paid to copyright issues and issues
concerning requirements for implementation, such as patent
licensing. [note in draft - text adopted from 03 Nov 2003 Protocol
Action announcement]
RFC 3668
Intellectual Property Rights in IETF Technology, S. Bradner (Ed.),
February 2004. (Status: BCP)
This document (with RFC 3667) replaces section 10 of RFC 2026, and
provides a much more detailed description of the considerations
regarding intellectual property that need to be taken into account
when working in the IETF.
Particular attention is paid to copyright issues and issues
concerning requirements for implementation, such as patent
licensing. [note in draft - text adopted from 03 Nov 2003 Protocol
Action announcement]
C: Additional Relevant Documents
RFC 3668
Guidelines for Working Groups on Intellectual Property Issues, S.
Brim, February 2004. (Status: Informational)
The "Guidelines" document relates useful experience gathered when
working with IPR issues in the IETF. [note in draft - text from 03
Nov 2003 Protocol Action announcement]
D: Extensions to the Standard
RFC 3932
The IESG and RFC Editor Documents: Procedures, H. Alvestrand,
October 2004. (Status: BCP)
This document describes the IESG's procedures for handling
documents submitted for RFC publication via the RFC Editor,
subsequent to the changes proposed by the IESG at the Seoul IETF,
March 2004. [note in draft - text from 27 Jul 2004 Protocol Action
announcement]
Bradner [Page 3]
Internet-Draft ISD for IETF Standards Process October 2004
E: Related ISDs
ISD XXXX IETF Working Group Processes
This ISD describes the IETF working group processes.
ISD XXXX IETF Mailing List Processes
This ISD describes the basic rules for IETF mailing lists.
F: Experimental Extensions
Internet Draft draft-klensin-process-july14
A model for IETF Process Experiments, J. Klensin, S. Dawkins
(Status: approved by the IESG)
This document proposes a way to change IETF processes that
provides notice to the community (via Last Call), a permanent
record (via RFCs) and a reasonable expectation that the process
changes will be evaluated for whether they worked or not, and
rolled back if they did not work. [note in draft - text from the
26 Jul 2004 Protocol Action announcement]
G: Obsolete Documents
RFC 1871
Addendum to RFC 1602 -- Variance Procedure, J. Postel. November
1995.
This RFC described a modification to the IETF procedures to allow
an escape from a situation where the existing procedures are not
working or do not seem to apply. This is a modification to the
procedures of RFC 1602 and 1603. This RFC was created to deal
with, among other things, an IPR deadlock concerning the PPP
compression control protocol. (See RFC 1915.)
RFC 1602
The Internet Standards Process -- Revision 2, Internet
Architecture Board, Internet Engineering Steering Group. March
1994
This RFC updated the description of the IETF Internet Standards
Process to more clearly define the IETF's intellectual property
related rules.
RFC 1310
The Internet Standards Process. L. Chapin. March 1992.
This RFC was the first description of the IETF Internet Standards
Process published in a stand alone RFC. It is now obsolete.
RFC 1200
IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, J.
Postel, Editor, April 1991
This document includes a description of the stages of the IETF
Internet Standards Process. It is now obsolete.
Bradner [Page 4]
Internet-Draft ISD for IETF Standards Process October 2004
RFC 1140
IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, J.
Postel, Editor, May 1990
This document includes a description of the stages of the IETF
Internet Standards Process. It is now obsolete.
RFC 1100
IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, April
1989
This document includes a description of the stages of the IETF
Internet Standards Process. It is now obsolete.
RFC 1083 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board,
December 1988
This document includes a description of the stages of the IETF
Internet Standards Process. It is now obsolete.
===================================================================
H: Historical Record
IETF Internet Standards Documentation
Name of ISD: ISD xxxx: The IETF Internet Standards Process
Last update: Oct-1996
Maintainer: IESG
A: Abstract
This ISD documents the process currently used by the Internet
community for the standardization of protocols and procedures. The
Internet Standards process is an activity of the Internet Society
that is organized and managed on behalf of the Internet community by
the Internet Architecture Board (IAB) and the Internet Engineering
Steering Group (IESG).
B: Documents making up the Standard
RFC 2026
The Internet Standards Process -- Revision 3, S. Bradner (Ed.),
October 1996. (Status: BCP)
The Internet Standards Process -- Revision 3, S. Bradner (Ed.),
October 1996. (Status: BCP)
The Internet Standards Process described in this document is
concerned with all protocols, procedures, and conventions that are
used in or by the Internet, whether or not they are part of the
TCP/IP protocol suite. In the case of protocols developed and/or
standardized by non-Internet organizations, however, the Internet
Standards Process normally applies to the application of the
protocol or procedure in the Internet context, not to the
specification of the protocol itself.
Bradner [Page 5]
Internet-Draft ISD for IETF Standards Process October 2004
The goals of the Internet Standards Process are:
o technical excellence;
o prior implementation and testing;
o clear, concise, and easily understood documentation;
o openness and fairness; and
o timeliness.
The procedures described in this document are designed to be fair,
open, and objective; to reflect existing (proven) practice; and
to be flexible.
The community needs this document because it spells out the way we
develop standards, the steps along the way, and the ways
disagreements and intellectual property rights are handled. [note
in draft - text from 9 Jul 96 Protocol Action announcement]
C: Additional Relevant Documents
none
D: Extensions to the Standard
none
E: Related ISDs
none
F: Experimental Extensions
none
G: Obsolete Documents
RFC 1871
Addendum to RFC 1602 -- Variance Procedure, J. Postel. November
1995.
This RFC described a modification to the IETF procedures to allow
an escape from a situation where the existing procedures are not
working or do not seem to apply. This is a modification to the
procedures of RFC 1602 and 1603. This RFC was created to deal
with, among other things, an IPR deadlock concerning the PPP
compression control protocol. (See RFC 1915.) [note in draft - I
could not find the Protocol Action announcement for this document]
RFC 1602
The Internet Standards Process -- Revision 2, Internet
Architecture Board, Internet Engineering Steering Group. March
1994
This RFC updated the description of the IETF Internet Standards
Process to more clearly define the IETF's intellectual property
related rules.
Bradner [Page 6]
Internet-Draft ISD for IETF Standards Process October 2004
RFC 1310
The Internet Standards Process. L. Chapin. March 1992.
This RFC was the first description of the IETF Internet Standards
Process published in a stand alone RFC. It is now obsolete.
RFC 1200
IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, J.
Postel, Editor, April 1991
This document includes a description of the stages of the IETF
Internet Standards Process. It is now obsolete.
RFC 1140
IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, J.
Postel, Editor, May 1990
This document includes a description of the stages of the IETF
Internet Standards Process. It is now obsolete.
RFC 1100
IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, April
1989
This document includes a description of the stages of the IETF
Internet Standards Process. It is now obsolete.
RFC 1083 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board,
December 1988
This document includes a description of the stages of the IETF
Internet Standards Process. It is now obsolete.
===================================================================
H: Historical Record
IETF Internet Standards Documentation
Name of ISD: ISD xxxx: The IETF Internet Standards Process
Last update: Nov 1995
Maintainer: IESG
A: Abstract
This ISD documents the process currently used by the Internet
community for the standardization of protocols and procedures. The
Internet Standards process is an activity of the Internet Society
that is organized and managed on behalf of the Internet community by
the Internet Architecture Board (IAB) and the Internet Engineering
Steering Group (IESG).
B: Documents making up the Standard
RFC 1602
The Internet Standards Process -- Revision 2, Internet
Bradner [Page 7]
Internet-Draft ISD for IETF Standards Process October 2004
Architecture Board, Internet Engineering Steering Group. March
1994
This describes the IETF Internet Standards Process.
C: Additional Relevant Documents
none
D: Extensions to the Standard
RFC 1871
Addendum to RFC 1602 -- Variance Procedure, J. Postel. November
1995.
This RFC describes a modification to the IETF procedures to allow
an escape from a situation where the existing procedures are not
working or do not seem to apply. This is a modification to the
procedures of RFC 1602 and 1603. This RFC was created to deal
with, among other things, an IPR deadlock concerning the PPP
compression control protocol. (See RFC 1915.)
E: Related ISDs
none
F: Experimental Extensions
none
G: Obsolete Documents
RFC 1310
The Internet Standards Process. L. Chapin. March 1992.
This RFC was the first description of the IETF Internet Standards
Process published in a stand alone RFC. It is now obsolete.
RFC 1200
IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, J.
Postel, Editor, April 1991
This document includes a description of the stages of the IETF
Internet Standards Process. It is now obsolete.
RFC 1140
IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, J.
Postel, Editor, May 1990
This document includes a description of the stages of the IETF
Internet Standards Process. It is now obsolete.
RFC 1100
IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, April
1989
This document includes a description of the stages of the IETF
Internet Standards Process. It is now obsolete.
Bradner [Page 8]
Internet-Draft ISD for IETF Standards Process October 2004
RFC 1083 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board,
December 1988
This document includes a description of the stages of the IETF
Internet Standards Process. It is now obsolete.
===================================================================
H: Historical Record
IETF Internet Standards Documentation
Name of ISD: ISD xxxx: The IETF Internet Standards Process
Last update: March 1994
Maintainer: IESG
A: Abstract
This ISD documents the process currently used by the Internet
community for the standardization of protocols and procedures. The
Internet Standards process is an activity of the Internet Society
that is organized and managed on behalf of the Internet community by
the Internet Architecture Board (IAB) and the Internet Engineering
Steering Group (IESG).
B: Documents making up the Standard
RFC 1602
The Internet Standards Process -- Revision 2, Internet
Architecture Board, Internet Engineering Steering Group. March
1994
This describes the IETF Internet Standards Process.
C: Additional Relevant Documents
none
D: Extensions to the Standard
none
E: Related ISDs
none
F: Experimental Extensions
none
G: Obsolete Documents
RFC 1310
The Internet Standards Process. L. Chapin. March 1992.
This RFC was the first description of the IETF Internet Standards
Process published in a stand alone RFC. It is now obsolete.
RFC 1200
Bradner [Page 9]
Internet-Draft ISD for IETF Standards Process October 2004
IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, J.
Postel, Editor, April 1991
This document includes a description of the stages of the IETF
Internet Standards Process. It is now obsolete.
RFC 1140
IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, J.
Postel, Editor, May 1990
This document includes a description of the stages of the IETF
Internet Standards Process. It is now obsolete.
RFC 1100
IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, April
1989
This document includes a description of the stages of the IETF
Internet Standards Process. It is now obsolete.
RFC 1083 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board,
December 1988
This document includes a description of the stages of the IETF
Internet Standards Process. It is now obsolete.
9. Security Considerations
ISDs would not have a security considerations section
10. References
ISDs would not have a references section since the whole document is
a references section
12. Editor's Address
Scott Bradner
Harvard University
29 Oxford St.
Cambridge MA, 02138
Phone: +1 617 495 3864
EMail: sob@harvard.edu
13. Full copyright statement
Copyright (C) The Internet Society (2004). 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.
This document and the information contained herein are provided on an
Bradner [Page 10]
Internet-Draft ISD for IETF Standards Process October 2004
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY 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.
Intellectual Property
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 ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Bradner [Page 11]
