Skip to main content

Updated Registration Rules for URI.ARPA
RFC 8958

Revision differences

Document history

Date Rev. By Action
2020-12-02
04 (System)
Received changes through RFC Editor sync (created alias RFC 8958, changed title to 'Updated Registration Rules for URI.ARPA', changed abstract to 'This document …
Received changes through RFC Editor sync (created alias RFC 8958, changed title to 'Updated Registration Rules for URI.ARPA', changed abstract to 'This document updates RFC 3405 by removing references to the IETF tree from the procedures for requesting that a URI scheme be inserted into the URI.ARPA zone.', changed standardization level to Best Current Practice, changed state to RFC, added RFC published event at 2020-12-02, changed IESG state to RFC Published, created updates relation between draft-hardie-dispatch-rfc3405-update and RFC 3405)
2020-12-02
04 (System) RFC published
2020-12-01
04 (System) RFC Editor state changed to <a href="http://www.rfc-editor.org/auth48/rfc8958">AUTH48-DONE</a> from AUTH48
2020-11-19
04 (System) RFC Editor state changed to <a href="http://www.rfc-editor.org/auth48/rfc8958">AUTH48</a> from RFC-EDITOR
2020-11-10
04 (System) RFC Editor state changed to RFC-EDITOR from EDIT
2020-10-28
04 (System) IANA Action state changed to RFC-Ed-Ack from Waiting on RFC Editor
2020-10-28
04 (System) IANA Action state changed to Waiting on RFC Editor from In Progress
2020-10-28
04 (System) IANA Action state changed to In Progress from Waiting on Authors
2020-10-28
04 (System) IANA Action state changed to Waiting on Authors from In Progress
2020-10-27
04 (System) IANA Action state changed to In Progress from Waiting on Authors
2020-10-27
04 (System) IANA Action state changed to Waiting on Authors from In Progress
2020-10-15
04 (System) RFC Editor state changed to EDIT
2020-10-15
04 (System) IESG state changed to RFC Ed Queue from Approved-announcement sent
2020-10-15
04 (System) Announcement was received by RFC Editor
2020-10-15
04 (System) IANA Action state changed to In Progress
2020-10-15
04 Cindy Morgan IESG state changed to Approved-announcement sent from Approved-announcement to be sent
2020-10-15
04 Cindy Morgan IESG has approved the document
2020-10-15
04 Cindy Morgan Closed "Approve" ballot
2020-10-15
04 Cindy Morgan Ballot approval text was generated
2020-10-15
04 Barry Leiba IESG state changed to Approved-announcement to be sent from Approved-announcement to be sent::AD Followup
2020-10-15
04 Ted Hardie New version available: draft-hardie-dispatch-rfc3405-update-04.txt
2020-10-15
04 (System) New version accepted (logged-in submitter: Ted Hardie)
2020-10-15
04 Ted Hardie Uploaded new revision
2020-10-08
03 Cindy Morgan IESG state changed to Approved-announcement to be sent::AD Followup from IESG Evaluation
2020-10-08
03 Martin Vigoureux [Ballot Position Update] New position, No Objection, has been recorded for Martin Vigoureux
2020-10-07
03 Alissa Cooper
[Ballot comment]
It seems the comment from the Gen-ART review was not addressed:

"1.  Introduction

  Part five of the Dynamic Delegation Discovery System (DDDS), …
[Ballot comment]
It seems the comment from the Gen-ART review was not addressed:

"1.  Introduction

  Part five of the Dynamic Delegation Discovery System (DDDS), RFC 3405
  [RFC3405], describes the registration procedures for assignments in
  URI.ARPA.  The document requires that registrations be in the "IETF
  tree" of URI registrations.  The use of URI scheme name trees was
  defined in RFC 2717 [RFC2717] but discontinued by RFC 4395 [RFC4395].
  Since the use of trees was discontinued, there is no way in the
  current process set out in BCP 35 [RFC7595] to meet the requirement."

This is indeed a nit, but I'd prefer s/the requirement/the above requirement/.
The current text did make me briefly think "Which requirement?".
2020-10-07
03 Alissa Cooper [Ballot Position Update] New position, Yes, has been recorded for Alissa Cooper
2020-10-06
03 Benjamin Kaduk
[Ballot comment]
Section 1

I suggest mentioning somehow in the prose that RFC 4395 was obsoleted by
RFC 7595, to establish the last link …
[Ballot comment]
Section 1

I suggest mentioning somehow in the prose that RFC 4395 was obsoleted by
RFC 7595, to establish the last link in the chain leading to "the
current process"; in the current form the RFC 7595 reference seems to
lack any preceding motivation.

(I also agree with the Gen-ART reviewer that spelling out "the
requirement" more explicitly would be helpful; that suggestion seems to
have gotten lost in the ensuing thread.)
2020-10-06
03 Benjamin Kaduk [Ballot Position Update] New position, No Objection, has been recorded for Benjamin Kaduk
2020-10-05
03 Warren Kumari [Ballot Position Update] New position, No Objection, has been recorded for Warren Kumari
2020-10-05
03 Alvaro Retana [Ballot Position Update] New position, No Objection, has been recorded for Alvaro Retana
2020-10-05
03 Roman Danyliw [Ballot Position Update] New position, No Objection, has been recorded for Roman Danyliw
2020-10-04
03 Éric Vyncke [Ballot Position Update] New position, No Objection, has been recorded for Éric Vyncke
2020-10-04
03 Erik Kline [Ballot Position Update] New position, No Objection, has been recorded for Erik Kline
2020-10-02
03 Deborah Brungard [Ballot Position Update] New position, No Objection, has been recorded for Deborah Brungard
2020-09-30
03 Martin Duke [Ballot Position Update] New position, No Objection, has been recorded for Martin Duke
2020-09-30
03 Robert Wilton [Ballot Position Update] New position, No Objection, has been recorded for Robert Wilton
2020-09-24
03 Murray Kucherawy [Ballot Position Update] New position, Yes, has been recorded for Murray Kucherawy
2020-09-24
03 Cindy Morgan Placed on agenda for telechat - 2020-10-08
2020-09-24
03 Barry Leiba Ballot has been issued
2020-09-24
03 Barry Leiba [Ballot Position Update] New position, Yes, has been recorded for Barry Leiba
2020-09-24
03 Barry Leiba Created "Approve" ballot
2020-09-24
03 Barry Leiba IESG state changed to IESG Evaluation from Waiting for AD Go-Ahead
2020-09-24
03 (System) IESG state changed to Waiting for AD Go-Ahead from In Last Call
2020-09-22
03 Sabrina Tanamal IANA Review state changed to IANA OK - Actions Needed from IANA - Not OK
2020-09-22
03 (System) IANA Review state changed to IANA - Not OK from IANA - Review Needed
2020-09-22
03 Sabrina Tanamal
(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Functions Operator has completed its review of draft-hardie-dispatch-rfc3405-update-03. If any part of this review is inaccurate, please let …
(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Functions Operator has completed its review of draft-hardie-dispatch-rfc3405-update-03. If any part of this review is inaccurate, please let us know.

The IANA Functions Operator understands that, upon approval of this document, there is a single action which we must complete.

IANA understands that the rules for registration in the .uri.arpa zone were established by RFC3405. That document says:

"In order to be inserted into the URI.ARPA zone, the subsequent URI scheme MUST be registered under the IETF URI tree. The requirements for this tree are specified in BCP35."

IANA understands that [ RFC-to-be ] removes this normative requirement and that the new requirement is:

"All registrations in URI.ARPA MUST now be for schemes which are permanent registrations, as they are described in BCP 35."

On the .ARPA Zone Management page located at:

https://www.iana.org/domains/arpa

IANA Question --> RFC3405 is listed as the reference for the .uri.arpa zone. Upon approval of this document, should this reference be replaced with [ RFC-to-be ] or should this document be added as an additional reference?

The IANA Functions Operator understands that this is the only action required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is meant only to confirm the list of actions that will be performed.

Thank you,

Sabrina Tanamal
Senior IANA Services Specialist
2020-09-08
03 Nancy Cam-Winget Request for Last Call review by SECDIR Completed: Ready. Reviewer: Nancy Cam-Winget. Sent review to list.
2020-09-03
03 Tero Kivinen Request for Last Call review by SECDIR is assigned to Nancy Cam-Winget
2020-09-03
03 Tero Kivinen Request for Last Call review by SECDIR is assigned to Nancy Cam-Winget
2020-09-03
03 Gunter Van de Velde Request for Last Call review by OPSDIR is assigned to Joel Jaeggli
2020-09-03
03 Gunter Van de Velde Request for Last Call review by OPSDIR is assigned to Joel Jaeggli
2020-08-31
03 Brian Carpenter Request for Last Call review by GENART Completed: Ready. Reviewer: Brian Carpenter. Sent review to list.
2020-08-27
03 Jean Mahoney Request for Last Call review by GENART is assigned to Brian Carpenter
2020-08-27
03 Jean Mahoney Request for Last Call review by GENART is assigned to Brian Carpenter
2020-08-27
03 Cindy Morgan IANA Review state changed to IANA - Review Needed
2020-08-27
03 Cindy Morgan
The following Last Call announcement was sent out (ends 2020-09-24):<br><br>From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
CC: barryleiba@gmail.com, draft-hardie-dispatch-rfc3405-update@ietf.org, …
The following Last Call announcement was sent out (ends 2020-09-24):<br><br>From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
CC: barryleiba@gmail.com, draft-hardie-dispatch-rfc3405-update@ietf.org, dispatch@ietf.org, spencerdawkins.ietf@gmail.com
Reply-To: last-call@ietf.org
Sender: <iesg-secretary@ietf.org>
Subject: Last Call: <draft-hardie-dispatch-rfc3405-update-03.txt> (Updated registration rules for URI.ARPA) to Best Current Practice


The IESG has received a request from an individual submitter to consider the
following document: - 'Updated registration rules for URI.ARPA'
  <draft-hardie-dispatch-rfc3405-update-03.txt> as Best Current Practice

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2020-09-24. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


  This document updates RFC 3405 by removing references to the IETF
  tree from the procedures for requesting that a URI scheme be inserted
  into the uri.arpa zone.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-hardie-dispatch-rfc3405-update/



No IPR declarations have been submitted directly on this I-D.




2020-08-27
03 Cindy Morgan IESG state changed to In Last Call from Last Call Requested
2020-08-27
03 Barry Leiba Ballot writeup was changed
2020-08-27
03 Barry Leiba Last call was requested
2020-08-27
03 Barry Leiba Last call announcement was generated
2020-08-27
03 Barry Leiba Ballot approval text was generated
2020-08-27
03 Barry Leiba Ballot writeup was generated
2020-08-27
03 Barry Leiba IESG state changed to Last Call Requested from AD Evaluation
2020-08-27
03 Barry Leiba IESG state changed to AD Evaluation from Publication Requested
2020-08-26
03 Spencer Dawkins
1. Summary:

  The document shepherd is Spencer Dawkins. The responsible Area Director is Barry Leiba.

  This document removes the normative requirement from RFC …
1. Summary:

  The document shepherd is Spencer Dawkins. The responsible Area Director is Barry Leiba.

  This document removes the normative requirement from RFC 3405 for
  registrations in URI.ARPA to be from the IETF URI Tree.

  This document will be published as a Best Current Practice, since it updates BCP 35.

2. Review and Consensus

  This draft was Dispatched at IETF 108, to be AD sponsored, and Barry Leiba agreed
  to sponsor it. The conversation in Dispatch was broadly supportive, although
  Dispatch did not adopt the draft or call for working group consensus on it, so it will
  receive a four-week IETF Last Call as per BCP 9.

3. Intellectual Property

  The author has confirmed that he knows of no IPR that applies to this draft.

4. Other Points

  ID Nits reports a few informational references to obsoleted RFCs:

  -- Obsolete informational reference (is this intentional?): RFC 2717
    (Obsoleted by RFC 4395)

  -- Obsolete informational reference (is this intentional?): RFC 4395
    (Obsoleted by RFC 7595)

  Both of these references are intentional, because the draft is referencing
  the RFCs that got us into the current situation.
2020-08-26
03 Ted Hardie New version available: draft-hardie-dispatch-rfc3405-update-03.txt
2020-08-26
03 (System) New version approved
2020-08-26
03 (System) Request for posting confirmation emailed to previous authors: Ted Hardie <ted.ietf@gmail.com>
2020-08-26
03 Ted Hardie Uploaded new revision
2020-08-25
02 Spencer Dawkins
1. Summary:

  The document shepherd is Spencer Dawkins. The responsible Area Director is Barry Leiba.

  This document removes the normative requirement from RFC …
1. Summary:

  The document shepherd is Spencer Dawkins. The responsible Area Director is Barry Leiba.

  This document removes the normative requirement from RFC 3405 for
  registrations in URI.ARPA to be from the IETF URI Tree.

  This document will be published as a Best Current Practice, since it updates BCP 35.

2. Review and Consensus

  This draft was Dispatched at IETF 108, to be AD sponsored, and Barry Leiba agreed
  to sponsor it. The conversation in Dispatch was broadly supportive, although
  Dispatch did not adopt the draft or call for consensus on it, and it will receive
  a four-week IETF Last Call as per BCP 9.

3. Intellectual Property

  The author has confirmed that he knows of no IPR that applies to this draft.

4. Other Points

  ID Nits reports some things that should be cleared up before Last Call. The
  shepherd will work these details with the author.
2020-08-19
02 Barry Leiba Notification list changed to spencerdawkins.ietf@gmail.com, dispatch@ietf.org from spencerdawkins.ietf@gmail.com, dispatch@ietf.org, Spencer Dawkins <spencerdawkins.ietf@gmail.com>
2020-08-19
02 Barry Leiba Changed consensus to Yes from Unknown
2020-08-19
02 Barry Leiba Notification list changed to spencerdawkins.ietf@gmail.com, dispatch@ietf.org, Spencer Dawkins <spencerdawkins.ietf@gmail.com> from spencerdawkins.ietf@gmail.com, dispatch@ietf.org
2020-08-19
02 Barry Leiba Document shepherd changed to Spencer Dawkins
2020-08-19
02 Barry Leiba Assigned to Applications and Real-Time Area
2020-08-19
02 Barry Leiba State Change Notice email list changed to spencerdawkins.ietf@gmail.com, dispatch@ietf.org
2020-08-19
02 Barry Leiba Responsible AD changed to Barry Leiba
2020-08-19
02 Barry Leiba Intended Status changed to Best Current Practice
2020-08-19
02 Barry Leiba IESG process started in state Publication Requested
2020-08-19
02 Barry Leiba Stream changed to IETF from None
2020-08-05
02 Ted Hardie New version available: draft-hardie-dispatch-rfc3405-update-02.txt
2020-08-05
02 (System) New version approved
2020-08-05
02 (System) Request for posting confirmation emailed to previous authors: Ted Hardie <ted.ietf@gmail.com>
2020-08-05
02 Ted Hardie Uploaded new revision
2020-07-26
01 Ben Campbell Added to session: IETF-108: dispatch  Mon-1100
2020-05-31
01 Ted Hardie New version available: draft-hardie-dispatch-rfc3405-update-01.txt
2020-05-31
01 (System) New version approved
2020-05-31
01 (System) Request for posting confirmation emailed to previous authors: Ted Hardie <ted.ietf@gmail.com>
2020-05-31
01 Ted Hardie Uploaded new revision
2020-05-29
00 Ted Hardie New version available: draft-hardie-dispatch-rfc3405-update-00.txt
2020-05-29
00 (System) New version approved
2020-05-29
00 Ted Hardie Request for posting confirmation emailed  to submitter and authors: Ted Hardie <ted.ietf@gmail.com>
2020-05-29
00 Ted Hardie Uploaded new revision