After the first decade: IASA Retrospective
draft-daigle-iasa-retrospective-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
Stream (None)
Intended RFC status (None)
Formats plain text 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                                     L. Daigle, Ed.
Internet-Draft                              Thinking Cat Enterprises LLC
Intended status: Informational                          October 31, 2016
Expires: May 4, 2017

               After the first decade: IASA Retrospective
                   draft-daigle-iasa-retrospective-00

Abstract

   The IETF Administrative Support Activity was formally established and
   undertaken as a project of the Internet Society in 2005.  In the
   following 10+ years, the IETF has grown and changed, as have the
   responsibilities that fall to the IASA.

   This document reflects on some of those changes and the implications
   within the IASA structure, providing some areas for further
   discussion to consider evolvingthe IASA and the IETF/ISOC
   relationship.

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 May 4, 2017.

Copyright Notice

   Copyright (c) 2016 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

Daigle                     Expires May 4, 2017                  [Page 1]
Internet-Draft             IASA Retrospective               October 2016

   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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Evolution of IASA breadth . . . . . . . . . . . . . . . . . .   3
     3.1.  IASA coverage in 2005 . . . . . . . . . . . . . . . . . .   3
     3.2.  IASA coverage in 2016 . . . . . . . . . . . . . . . . . .   4
   4.  Evolution of Internet Society Partnership . . . . . . . . . .   6
   5.  Issues and Potential Next Steps for the IASA structure  . . .   6
   6.  Closing remarks . . . . . . . . . . . . . . . . . . . . . . .   9
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   9
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Terminology

   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 [RFC2119].

2.  Introduction

   A special Introduction to the -00 version of this draft: When
   completed, this document will achieve the stated goal of capturing
   reflections on the evolution of the IASA.  Right now, it is the first
   draft written by one person with a few peoples' (thoughtful, and
   appreciated) input.  Gaps are inevitable.  Misrepresentations are not
   intended.  Further constructive comments are welcome.

   In April 2005, BCP 101 ([RFC4071]) was published, formally creating
   the IETF Administrative Support Activity (IASA).  At the end of an
   intense community discussion, the IASA was formed as an activity
   housed within the Internet Society (ISOC), and BCP 101 defined the
   roles of the IETF Administrative Oversight Committee (IAOC), and the
   IETF Administrative Directory (IAD).  Together, these roles have
   defined responsibilities for IETF's fiscal and administrative
   support.

   With the newly established IASA, the IETF was in a position to
   formalize several activities that had been undertaken by other
   organizations, on behalf of the IETF.  This allowed the IETF take
   responsibility of those operations.  Through the 10+ years since the
   inception of IASA, the operations and responsibilities have, however,
   grown and requirements have evolved.  Nor has the world stood still
Show full document text