The IETF XML Registry
draft-mealling-iana-xmlns-registry-05
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2012-08-22
|
05 | (System) | post-migration administrative database adjustment to the No Objection position for Bert Wijnen |
2003-08-27
|
05 | Natalia Syracuse | State Changes to RFC Ed Queue from Approved-announcement sent by Natalia Syracuse |
2003-08-26
|
05 | Amy Vezza | IESG state changed to Approved-announcement sent |
2003-08-26
|
05 | Amy Vezza | IESG has approved the document |
2003-08-26
|
05 | Amy Vezza | Closed "Approve" ballot |
2003-08-26
|
05 | Amy Vezza | State Changes to Approved-announcement to be sent from IESG Evaluation::AD Followup by Amy Vezza |
2003-08-22
|
05 | Ted Hardie | Still waiting to clear Russ's discuss, but all others are clear |
2003-08-11
|
05 | Michael Lee | Removed from agenda for telechat - 2003-08-07 by Michael Lee |
2003-08-07
|
05 | Amy Vezza | State Changes to IESG Evaluation::AD Followup from IESG Evaluation::Revised ID Needed by Amy Vezza |
2003-08-04
|
05 | (System) | [Ballot Position Update] Position for Russ Housley has been changed to Discuss from No Record |
2003-08-04
|
05 | (System) | [Ballot Position Update] New position, No Objection, has been recorded for Jon Peterson |
2003-08-04
|
05 | (System) | [Ballot Position Update] New position, Yes, has been recorded for Ted Hardie |
2003-08-04
|
05 | (System) | [Ballot Position Update] New position, No Objection, has been recorded for Alex Zinin |
2003-08-04
|
05 | (System) | [Ballot Position Update] New position, No Objection, has been recorded for Bill Fenner |
2003-08-04
|
05 | (System) | [Ballot Position Update] New position, No Objection, has been recorded for Ned Freed |
2003-08-04
|
05 | (System) | [Ballot Position Update] Position for Steven Bellovin has been changed to Discuss from No Record |
2003-08-04
|
05 | (System) | [Ballot Position Update] Position for Bert Wijnen has been changed to No Objection from No Record |
2003-08-04
|
05 | (System) | [Ballot Position Update] New position, Discuss, has been recorded for Thomas Narten |
2003-08-04
|
05 | (System) | [Ballot Position Update] New position, No Objection, has been recorded for Allison Mankin |
2003-08-04
|
05 | (System) | [Ballot Position Update] New position, No Objection, has been recorded for Randy Bush |
2003-08-04
|
05 | (System) | [Ballot Position Update] New position, No Objection, has been recorded for Harald Alvestrand |
2003-08-04
|
05 | Russ Housley | [Ballot discuss] The document does not have a Security Considerations section. |
2003-08-04
|
05 | Steven Bellovin | [Ballot discuss] No "Security Considerations" section. |
2003-08-04
|
05 | (System) | Ballot has been issued |
2003-08-04
|
05 | Bert Wijnen | [Ballot discuss] - Section 2.1 states: NOTE: in order for a URN of this type to be assigned, the item being registered MUST have been … [Ballot discuss] - Section 2.1 states: NOTE: in order for a URN of this type to be assigned, the item being registered MUST have been through the IETF concensus process. Practically this means it must be documented in an RFC. Given the confusion we have seen over what "IETF consensus" means, do we want to keep the above or maybe define it better? - Under publicid on page 2 it says: In the case where a PUBLIC Identifier is also a URI it is possible for the SYSTEM Identifier to contain the same URI but this behavior is not recommended unless its side effects are well known. I think the intention is: "unless its side effect are well known and understood to not cause any unacceptable harm" or some such, no? Question: - Sect 3, Registration Process explains how an XML file is being stored. It does not talk at all about if or if so how such an XML file will be validated to have correct syntax. Given the experiens with MIB modules, I would hope that IANA gets a tool to verify that such XML syntax is correct before a file gets accepted. Should the document say something about that? NITS: - Page 3 under schema: 'urn:ietf:params:xml:schema:<id>'. probably should be: 'urn:ietf:params:xml:schema:'. |
2003-08-04
|
05 | Bert Wijnen | Created "Approve" ballot |
2003-08-04
|
05 | (System) | Ballot writeup text was added |
2003-08-04
|
05 | (System) | Last call text was added |
2003-08-04
|
05 | (System) | Ballot approval text was added |
2003-08-01
|
05 | Michael Lee | Placed on agenda for telechat - 2003-08-07 by Michael Lee |
2003-06-18
|
05 | (System) | New version available: draft-mealling-iana-xmlns-registry-05.txt |
2003-05-13
|
05 | Ted Hardie | State Changes to IESG Evaluation :: Revised ID Needed from IESG Evaluation by Hardie, Ted |
2003-04-22
|
05 | Jacqueline Hargest | State Changes to IESG Evaluation from Waiting for AD Go-Ahead by Hargest, Jacqueline |
2003-04-22
|
05 | Jacqueline Hargest | State Changes to Waiting for AD Go-Ahead from In Last Call by Hargest, Jacqueline |
2003-04-02
|
05 | Jacqueline Hargest | State Changes to In Last Call from Last Call Requested by Hargest, Jacqueline |
2003-04-02
|
05 | Jacqueline Hargest | Status date has been changed to 2003-5-2 from 2002-02-17 |
2003-04-02
|
05 | (System) | Last call sent |
2003-03-25
|
05 | Ted Hardie | Intended Status has been changed to BCP from Informational |
2003-03-25
|
05 | Ted Hardie | State Changes to Last Call Requested from AD Evaluation by Hardie, Ted |
2003-03-24
|
05 | Ted Hardie | Shepherding AD has been changed to Hardie, Ted from Faltstrom, Patrik |
2002-10-18
|
05 | Patrik Fältström | Michael explains the issues from Keith (should stay PRIVATE for IESG): Keith had two objections: 1) he has a problem with using URIs as identifiers … Michael explains the issues from Keith (should stay PRIVATE for IESG): Keith had two objections: 1) he has a problem with using URIs as identifiers for attribute names in all circumstances. This means there would be no URI at all for denoting protocol parameters within the IANA. At some point in the discussion he simply stated that those that use URIs for such things shouldn't be accomodated at all. When asked about the fact that XML itself uses URIs in this way his response was "so, that doesn't mean the IETF has to encourage them to do that". My response to that is that the IETF itself in various working groups is using this very concept as an interoperable way of denoting schema, attribute names, object identifiers, etc. Its proven to be useful, interoperable and scalable. If the IETF were to refuse this document based on that reasoning then we would have to forbid any use of XML in the IETF and basically sever ties with the W3C. 2) He didn't agree with the URNs containing human readable text. This goes back to the URN discussion we had eons ago about using meaningful NIDs and allowing anyone to put whatever their scheme wanted into the opaque string portion. He asserted and lost the argument for limiting URNs to hexadecimal values in order to make it impossible to embed anything in the URN that might be construed as having semantics. There is concensus from just about everyone except Keith that this reasoning would cause anything based on URNs to fail simply becuase the barrier to entry for any compatible namespace would be to high to warrant use. If the world were perfect and everyone did what we told them then we might be able to get them to use semantically free identifiers but that's just not going to be the possible. Keith has lost this battle before and has been the lone hold out. Is that sufficient? |
2002-10-18
|
05 | Patrik Fältström | by paf |
2002-07-02
|
04 | (System) | New version available: draft-mealling-iana-xmlns-registry-04.txt |
2002-03-08
|
05 | Harald Alvestrand | Feb 21 telechat asked for this to be updated by author, then Last Called for BCP. "Approved" is wrong state. |
2002-03-08
|
05 | Harald Alvestrand | State Changes to New Version Needed (WG/Author) from Approved … State Changes to New Version Needed (WG/Author) from Approved by Harald Alvestrand |
2001-11-29
|
03 | (System) | New version available: draft-mealling-iana-xmlns-registry-03.txt |
2001-08-29
|
02 | (System) | New version available: draft-mealling-iana-xmlns-registry-02.txt |
2001-06-27
|
01 | (System) | New version available: draft-mealling-iana-xmlns-registry-01.txt |
2000-11-21
|
00 | (System) | New version available: draft-mealling-iana-xmlns-registry-00.txt |