Opened 8 years ago

Closed 8 years ago

#97 closed enhancement (invalid)

Provisional schemes de-asssignment

Reported by: evnikita2@… Owned by:
Priority: major Milestone:
Component: 4395bis Version:
Severity: - Keywords:
Cc: evnikita2@…

Description

From http://lists.w3.org/Archives/Public/public-iri/2011Aug/0044.html:


URI/IRI schemes de-assignment. The issue was raised by Frank
Ellermann on uri-review list recently; it is that particular
provisionally-registered schemes can be de-assigned by their
registrants. RFC 4395 says nothing about this; so I suppose 4395bis
will have something to say. (BTW, this feature may be useful for 'afs'
URI scheme, which has "hung" in the undefined state from 1994, time of
publication of RFC 1738).

Change History (1)

comment:1 Changed 8 years ago by masinter@…

  • Resolution set to invalid
  • Status changed from new to closed

RFC 4395 has an explicit process for transitioning to "Historical", so the statement "RFC 4395 says nothing about this" is confusing.

Frank's email to the uri-review list
http://www.ietf.org/mail-archive/web/uri-review/current/msg01530.html
says "IESG (the transition from a "provisional" to "historical" status is
not covered by BCP 35 section 5.3"

but this doesn't seem to be the case,
5.3. Change Control
Transition from 'permanent' to 'historical' status requires IESG

approval. Transition from 'provisional' to 'historical' may be
requested by anyone authorized to update the provisional
registration.

Please clarify and re-open if you can elaborate.

Note: See TracTickets for help on using tickets.