Hello IETF Community,
Several people have recently asked me what the policy is for creating or
modifying IANA registries using documents in the Independent Submissions
Stream, and from time to time a document in the stream requests allocation
of a code point from an existing registry.
This document is an attempt to describe how I will act (as Independent
Submissions Editor) when I am asked to publish such documents.
I would very much appreciate comments and thoughts.
Best,
Adrian
--
Adrian Farrel (ISE),
rfc-ise@xxxxxxxxxxxxxx
-----Original Message-----
From: I-D-Announce <i-d-announce-bounces@xxxxxxxx> On Behalf Of
internet-drafts@xxxxxxxx
Sent: 13 August 2019 12:24
To: i-d-announce@xxxxxxxx
Subject: I-D Action: draft-ise-iana-policy-00.txt
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
Title : How Requests for IANA Action Will be Handled on
the Independent Stream
Author : Adrian Farrel
Filename : draft-ise-iana-policy-00.txt
Pages : 5
Date : 2019-08-13
Abstract:
The Internet Assigned Numbers Authority (IANA) maintains registries
to track codepoints used by protocols defined by the IETF and
documented in RFCs developed on the IETF Stream.
The Independent Submissions Stream is another source of documents
that can be published as RFCs. This stream is under the care of the
Independent Submissions Editor (ISE).
This document updates RFC 4846 by describing how the current ISE will
handle documents in the Independent Submissions Stream that request
actions from the IANA. Nothing in this document changes existing
IANA registries and their allocation policies.
The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ise-iana-policy/
There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ise-iana-policy-00
https://datatracker.ietf.org/doc/html/draft-ise-iana-policy-00
