The IETF-ISOC Relationship
RFC 8712

Document Type RFC - Informational (February 2020; No errata)
Obsoletes RFC 2031
Authors Gonzalo Camarillo  , Jason Livingood 
Last updated 2020-02-27
Stream Internent Engineering Task Force (IETF)
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Jon Peterson
Shepherd write-up Show (last changed 2019-03-22)
IESG IESG state RFC 8712 (Informational)
Action Holders
Consensus Boilerplate Yes
Telechat date
Responsible AD Alissa Cooper
IESG note RFC Editor note:

There's a typo in Section 2: "and continued to be" should be "and continues to be"
Send notices to Jon Peterson <>
IANA IANA review state IANA OK - No Actions Needed
IANA action state No IANA Actions

Internet Engineering Task Force (IETF)                      G. Camarillo
Request for Comments: 8712                                      Ericsson
Obsoletes: 2031                                             J. Livingood
Category: Informational                                          Comcast
ISSN: 2070-1721                                            February 2020

                       The IETF-ISOC Relationship


   This document summarizes the Internet Engineering Task Force (IETF) -
   Internet Society (ISOC) relationship, following a major revision to
   the structure of the IETF Administrative Support Activity (IASA) in
   2018.  The IASA was revised under a new "IASA 2.0" structure by the
   IASA2 Working Group, which changed the IETF's administrative, legal,
   and financial structure.  As a result, it also changed the
   relationship between the IETF and ISOC, which made it necessary to
   revise RFC 2031.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are candidates for any level of Internet
   Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at

Copyright Notice

   Copyright (c) 2020 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
   ( 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 and History
   2.  Philosophical Relationship with ISOC
   3.  Main Division of Responsibilities between IETF and ISOC
   4.  ISOC's Role in the IETF Standards Process
   5.  The IETF's Role in ISOC
   6.  Legal Relationship with ISOC
   7.  Financial and Administrative Relationship with ISOC
   8.  IANA Considerations
   9.  Security Considerations
   10. Privacy Considerations
   11. References
     11.1.  Normative References
     11.2.  Informative References
   Authors' Addresses

1.  Introduction and History

   The Internet Society provides a corporate home for the administrative
   entity that supports the Internet Engineering Task Force (IETF), the
   Internet Architecture Board (IAB), and the Internet Research Task
   Force (IRTF), and supports the work of these groups through a variety
   of programs.

   The Internet Engineering Task Force (IETF) is the body that is
   responsible for the development and maintenance of the Internet
   Standards.  The IETF is primarily a volunteer organization.  Its
   driving force is a group of dedicated, high-quality engineers from
   all over the world.  In a structure of working groups, these
   engineers exchange ideas and experience, and through discussion and
   collaboration (both electronically and face-to-face), they strive to
   achieve rough consensus and implement the standards through running

   The growth of the Internet over several decades has also led to the
   growth of the IETF.  More and more people, organizations, and
   companies rely on Internet Standards.  Nontechnical issues, such as
   legal, administrative, and financial issues had long been an
   undesirable but unavoidable part of the IETF.  To address these
   issues, the IETF established the Poised95 Working Group in 1995.  Its
   goal was to structure and document the IETF processes in order to
   maximize the flexibility and freedom of IETF engineers so that they
   could work in the way the IETF had always been most successful and to
   honor the IETF credo: "Rough consensus and running code".

   The Poised95 Working Group concluded that the Internet Society
   (ISOC), which was formed in 1992, was the best organization to handle
   all of these legal, administrative, and financial tasks on behalf of,
   and in close cooperation with, the IETF.  This led to documenting
   things such as the IETF standards process [RFC2026], the IETF
   organizational structure [RFC2028], the IETF Nominating Committee
   (NomCom) procedures [RFC2027], and the IETF-ISOC relationship

   As time passed and operational experience accumulated, additional
Show full document text