Call for Comment: <draft-ietf-iasa2-rfc6220bis-03> (Defining the Role and Function of IETF Protocol Parameter Registry Operators)

IAB Executive Administrative Manager <execd@iab.org> Wed, 21 August 2019 18:19 UTC

Return-Path: <execd@iab.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E68DC120E4F for <ietf-announce@ietf.org>; Wed, 21 Aug 2019 11:19:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IAB Executive Administrative Manager <execd@iab.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: Call for Comment: <draft-ietf-iasa2-rfc6220bis-03> (Defining the Role and Function of IETF Protocol Parameter Registry Operators)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.100.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: architecture-discuss@ietf.org, iab@iab.org
Message-ID: <156641157393.25789.13597724381522897325.idtracker@ietfa.amsl.com>
Date: Wed, 21 Aug 2019 11:19:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/yTI6paDYhhlIH6Bk0VlQ4BYGo0U>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2019 18:19:39 -0000

This is an announcement of an IETF-wide Call for Comment on 
draft-ietf-iasa2-rfc6220bis-03.

The document is being considered for publication as an Informational RFC 
within the IAB stream, and is available for inspection at:
<https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc6220bis/>

The Call for Comment will last until 2019-09-18. Please send comments to
architecture-discuss@ietf.org and iab@iab.org.

Abstract

   Many Internet Engineering Task Force (IETF) protocols make use of
   commonly defined values that are passed in messages or packets.  To
   ensure consistent interpretation of these values between independent
   implementations, there is a need to ensure that the values and
   associated semantic intent are uniquely defined.  The IETF uses
   registry functions to record assigned protocol parameter values and
   their associated semantic intentions.  For each IETF protocol
   parameter, it is current practice for the IETF to delegate the role
   of Protocol Parameter Registry Operator to a nominated entity.  This
   document provides a description of, and the requirements for, these
   delegated functions.

[Cover Note]

   [The IASA2 WG asks the IAB to publish this replacement for RFC 6220.
   This document is changed for alignment with the new structure for the
   IETF Administrative Support Activity (IASA). ]