[Iasa20] RFC 8712 on The IETF-ISOC Relationship

rfc-editor@rfc-editor.org Thu, 27 February 2020 18:17 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 704513A041C; Thu, 27 Feb 2020 10:17:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O2-vB398VQZh; Thu, 27 Feb 2020 10:17:06 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 260FF3A03F7; Thu, 27 Feb 2020 10:17:06 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id E7036F40711; Thu, 27 Feb 2020 10:16:51 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, iasa20@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200227181651.E7036F40711@rfc-editor.org>
Date: Thu, 27 Feb 2020 10:16:51 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/djJvll9xTw0KbVXFqdftGa09v98>
Subject: [Iasa20] =?utf-8?q?RFC_8712_on_The_IETF-ISOC_Relationship?=
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: =?iso-8859-1?q?Discussions_relating_to_reorganising_the_IETF_administrative_structures_in_the_so_called_=93IASA_2=2E0=94_project=2E?= <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2020 18:17:07 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8712

        Title:      The IETF-ISOC Relationship 
        Author:     G. Camarillo,
                    J. Livingood
        Status:     Informational
        Stream:     IETF
        Date:       February 2020
        Mailbox:    gonzalo.camarillo@ericsson.com, 
                    Jason_Livingood@comcast.com
        Pages:      8
        Obsoletes:  RFC 2031

        I-D Tag:    draft-ietf-iasa2-rfc2031bis-08.txt

        URL:        https://www.rfc-editor.org/info/rfc8712

        DOI:        10.17487/RFC8712

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.

This document is a product of the IETF Administrative Support Activity 2 Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC