Using Third Party Services for IETF Work
draft-nottingham-wugh-services-00
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-03-09
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group M. Nottingham
Internet-Draft March 10, 2017
Intended status: Best Current Practice
Expires: September 11, 2017
Using Third Party Services for IETF Work
draft-nottingham-wugh-services-00
Abstract
Some IETF Working Groups use third-party tools to manage their work,
in addition to or instead of those that the Secretariat and Tools
team provide. This document specifies requirements regarding their
use.
Note to Readers
The issues list for this draft can be found at
https://github.com/mnot/I-D/labels/wugh-services .
The most recent (often, unpublished) draft is at
https://mnot.github.io/I-D/wugh-services/ .
Recent changes are listed at https://github.com/mnot/I-D/commits/gh-
pages/wugh-services .
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 September 11, 2017.
Nottingham Expires September 11, 2017 [Page 1]
Internet-Draft 3rd Party Services to the IETF March 2017
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Notational Conventions . . . . . . . . . . . . . . . . . 3
2. Requirements for Third-Party Tools . . . . . . . . . . . . . 3
2.1. Rough Consensus To Use . . . . . . . . . . . . . . . . . 3
2.2. Equal Access . . . . . . . . . . . . . . . . . . . . . . 3
2.3. Clear Procedure . . . . . . . . . . . . . . . . . . . . . 4
2.4. Notification . . . . . . . . . . . . . . . . . . . . . . 5
2.5. Neutrality . . . . . . . . . . . . . . . . . . . . . . . 5
2.6. Recoverability . . . . . . . . . . . . . . . . . . . . . 5
2.7. Administrative Access . . . . . . . . . . . . . . . . . . 6
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
5. Normative References . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
Some IETF Working Groups use third-party tools to manage their work,
in addition to or instead of those that the Secretariat and Tools
team provide.
For example, GitHub https://github.com/ is currently used by a number
of active Working Groups to manage their drafts; as a distributed
version control system, it has several attractive features, including
broad understanding and use among developers, a refined user
experience, and issue tracking facilities.
Working Groups are encouraged to use the best tools that work for
them, in a manner that best suits the work; the IETF does not benefit
from locking its work practices into a one-size-fits-all set of
tools.
Nottingham Expires September 11, 2017 [Page 2]
Internet-Draft 3rd Party Services to the IETF March 2017
However, use of tools controlled by third parties can cause issues if
not carefully considered. To preserve the integrity of the IETF
process when they are used, Section 2 outlines requirements for such
uses.
1.1. Notational Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text