URN Namespace for ETSI Documents
draft-mahesh-etsi-urn-05
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2019-02-25
|
05 | (System) | RFC Editor state changed to AUTH48-DONE from AUTH48 |
2019-01-29
|
05 | Ignas Bagdonas | Changed consensus to Yes from Unknown |
2018-12-19
|
05 | (System) | RFC Editor state changed to AUTH48 from RFC-EDITOR |
2018-11-27
|
05 | (System) | IANA Action state changed to RFC-Ed-Ack from Waiting on RFC Editor |
2018-11-26
|
05 | (System) | RFC Editor state changed to RFC-EDITOR from IANA |
2018-11-26
|
05 | (System) | IANA Action state changed to Waiting on RFC Editor from Waiting on Authors |
2018-11-26
|
05 | (System) | IANA Action state changed to Waiting on Authors from In Progress |
2018-11-20
|
05 | (System) | RFC Editor state changed to IANA from RFC-EDITOR |
2018-11-20
|
05 | (System) | RFC Editor state changed to RFC-EDITOR from EDIT |
2018-11-20
|
05 | (System) | IANA Action state changed to In Progress |
2018-11-20
|
05 | (System) | RFC Editor state changed to EDIT |
2018-11-20
|
05 | (System) | IESG state changed to RFC Ed Queue from Approved-announcement sent |
2018-11-20
|
05 | (System) | Announcement was received by RFC Editor |
2018-11-20
|
05 | Amy Vezza | IESG state changed to Approved-announcement sent from Approved-announcement to be sent |
2018-11-20
|
05 | Amy Vezza | IESG has approved the document |
2018-11-20
|
05 | Amy Vezza | Closed "Approve" ballot |
2018-11-20
|
05 | Amy Vezza | Ballot approval text was generated |
2018-11-20
|
05 | Ignas Bagdonas | IESG state changed to Approved-announcement to be sent from IESG Evaluation::AD Followup |
2018-11-16
|
05 | Mahesh Jethanandani | New version available: draft-mahesh-etsi-urn-05.txt |
2018-11-16
|
05 | (System) | New version approved |
2018-11-16
|
05 | (System) | Request for posting confirmation emailed to previous authors: Miguel Ortega , Mahesh Jethanandani |
2018-11-16
|
05 | Mahesh Jethanandani | Uploaded new revision |
2018-11-16
|
04 | Alexey Melnikov | [Ballot comment] Thank you for addressing my DISCUSS. |
2018-11-16
|
04 | Alexey Melnikov | [Ballot Position Update] Position for Alexey Melnikov has been changed to No Objection from Discuss |
2018-10-22
|
04 | (System) | Sub state has been changed to AD Followup from Revised ID Needed |
2018-10-22
|
04 | (System) | IANA Review state changed to Version Changed - Review Needed from IANA - Not OK |
2018-10-22
|
04 | Mahesh Jethanandani | New version available: draft-mahesh-etsi-urn-04.txt |
2018-10-22
|
04 | (System) | New version approved |
2018-10-22
|
04 | (System) | Request for posting confirmation emailed to previous authors: Miguel Ortega , Mahesh Jethanandani |
2018-10-22
|
04 | Mahesh Jethanandani | Uploaded new revision |
2018-09-27
|
03 | Cindy Morgan | IESG state changed to IESG Evaluation::Revised I-D Needed from IESG Evaluation |
2018-09-27
|
03 | Benjamin Kaduk | [Ballot comment] A lot of good points have already been raised by other ADs, so I'll try to not belabor them. The "Purpose" starting with … [Ballot comment] A lot of good points have already been raised by other ADs, so I'll try to not belabor them. The "Purpose" starting with "[t]o begin with" is slightly jarring to read. I understand that the initial trigger for this NID is for YANG modules, and it can of course subsequently be used for other purposes, and we need to acknowledge both these facts. It might be less jarring to me in the other order, something like "a general-purpose delegation for use by ETSI when unique URNs are needed. Intended applications include, but are not limited to, YANG modules". In "Identifier uniqueness considerations": Maybe something like "allow for use of experimental type values in specific, documented, subtrees, for testing purposes only" would be more clear about the scope of potential conflicts? In "Security and Privacy: If an namespace is URN-equivalent to another namespace used by the device, as per the rules specified in Section 3.1 of URNs [RFC8141], Section 6.1 of URI Generic Syntax [RFC3986], and the lexical rules specified in this document, the request is rejected. What are "the device" and "the request" in this context? |
2018-09-27
|
03 | Benjamin Kaduk | [Ballot Position Update] New position, No Objection, has been recorded for Benjamin Kaduk |
2018-09-27
|
03 | Martin Vigoureux | [Ballot comment] Hello, I second Mirja's question noting that 8141 allows for a fast track procedure for "Standards Development Organizations, Scientific Societies, and Similar Bodies" … [Ballot comment] Hello, I second Mirja's question noting that 8141 allows for a fast track procedure for "Standards Development Organizations, Scientific Societies, and Similar Bodies" -m |
2018-09-27
|
03 | Martin Vigoureux | [Ballot Position Update] New position, No Objection, has been recorded for Martin Vigoureux |
2018-09-26
|
03 | Suresh Krishnan | [Ballot Position Update] New position, No Objection, has been recorded for Suresh Krishnan |
2018-09-26
|
03 | Terry Manderson | [Ballot Position Update] New position, No Objection, has been recorded for Terry Manderson |
2018-09-26
|
03 | Ben Campbell | [Ballot Position Update] New position, No Objection, has been recorded for Ben Campbell |
2018-09-26
|
03 | Alvaro Retana | [Ballot Position Update] New position, No Objection, has been recorded for Alvaro Retana |
2018-09-25
|
03 | Deborah Brungard | [Ballot Position Update] New position, No Objection, has been recorded for Deborah Brungard |
2018-09-25
|
03 | Alissa Cooper | [Ballot comment] Why does this document not have a document shepherd? I guess technically this is allowed but I'm curious about the justification for it … [Ballot comment] Why does this document not have a document shepherd? I guess technically this is allowed but I'm curious about the justification for it I'm also interested in the answer to Mirja's question. |
2018-09-25
|
03 | Alissa Cooper | [Ballot Position Update] New position, No Objection, has been recorded for Alissa Cooper |
2018-09-25
|
03 | Alexey Melnikov | [Ballot discuss] This document is generally fine, but I would like to clarify a few things before recommending its approval as an RFC: In Section … [Ballot discuss] This document is generally fine, but I would like to clarify a few things before recommending its approval as an RFC: In Section 2: Identifier persistence considerations: ETSI will update the ETSI URN Namespace (EUN) registry to document the registered resources that will use the "etsi" NID. URN namespace registrations should not contain forward looking statements and should describe the process that is expected to be used. You already included . Is it where these registered resources will be mentioned? If yes, point to this web page. Process of identifier assignment: Assignment of a URN from the ETSI namespace will be documented as part of the ETSI URN Namespace (EUN) registry. I think already covers this, so please reword this not to use future tense. Security and Privacy: If an namespace is URN-equivalent to another namespace used by the device, as per the rules specified in Section 3.1 of URNs [RFC8141], Section 6.1 of URI Generic Syntax [RFC3986], and the lexical rules specified in this document, the request is rejected. I am not sure how URN equivalence is related to security. Can you elaborate? |
2018-09-25
|
03 | Alexey Melnikov | [Ballot comment] In Section 2: Purpose: To begin with, the URN requested in this document will be used by ETSI for allocation of … [Ballot comment] In Section 2: Purpose: To begin with, the URN requested in this document will be used by ETSI for allocation of namespaces to be used by YANG modules, that are developed by the organization. These namespaces are globally unique. The URN will be used in public networks by devices used to configure and manage resources in the network. It is these devices that will enforce the uniqueness of the namespaces by using the namespace and the XPath associated with the managed node in the network, when accessing a resource. The last sentence: I am not sure how devices will enforce uniqueness of the namespaces. Can you elaborate? |
2018-09-25
|
03 | Alexey Melnikov | [Ballot Position Update] New position, Discuss, has been recorded for Alexey Melnikov |
2018-09-24
|
03 | Adam Roach | [Ballot comment] I-D Nits reports: -- Obsolete informational reference (is this intentional?): RFC 5246 (Obsoleted by RFC 8446) This registration seems … [Ballot comment] I-D Nits reports: -- Obsolete informational reference (is this intentional?): RFC 5246 (Obsoleted by RFC 8446) This registration seems fine to me, although the phrasing in this document makes it seem as if the registration is only for YANG. Given that this is a delegation of a subtree to ETSI for whatever purposes make sense for their uses, I would recommend text in here that indicates that the subtree can be used for non-YANG purposes as well, at ETSI's discretion. |
2018-09-24
|
03 | Adam Roach | [Ballot Position Update] New position, No Objection, has been recorded for Adam Roach |
2018-09-23
|
03 | Warren Kumari | [Ballot Position Update] New position, No Objection, has been recorded for Warren Kumari |
2018-09-19
|
03 | Mirja Kühlewind | [Ballot comment] This is all fine with me but one question to the AD: Why is this RFC needed? Registration policy for "Uniform Resource Names … [Ballot comment] This is all fine with me but one question to the AD: Why is this RFC needed? Registration policy for "Uniform Resource Names (URN) Namespaces" is Expert Review (or there is actuually an own section in rfc8141 for SDOs). |
2018-09-19
|
03 | Mirja Kühlewind | Ballot comment text updated for Mirja Kühlewind |
2018-09-19
|
03 | Mirja Kühlewind | [Ballot Position Update] New position, No Objection, has been recorded for Mirja Kühlewind |
2018-09-11
|
03 | Ignas Bagdonas | IESG state changed to IESG Evaluation from Waiting for AD Go-Ahead |
2018-09-11
|
03 | Ignas Bagdonas | IESG state changed to Waiting for AD Go-Ahead from Waiting for Writeup |
2018-09-11
|
03 | Amy Vezza | Placed on agenda for telechat - 2018-09-27 |
2018-09-11
|
03 | Ignas Bagdonas | Ballot has been issued |
2018-09-11
|
03 | Ignas Bagdonas | [Ballot Position Update] New position, Yes, has been recorded for Ignas Bagdonas |
2018-09-11
|
03 | Ignas Bagdonas | Created "Approve" ballot |
2018-09-11
|
03 | Ignas Bagdonas | Ballot writeup was changed |
2018-08-11
|
03 | (System) | IESG state changed to Waiting for Writeup from In Last Call |
2018-08-10
|
03 | (System) | IANA Review state changed to IANA - Not OK from IANA - Review Needed |
2018-08-10
|
03 | Sabrina Tanamal | (Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs: The IANA Functions Operator has completed its review of draft-mahesh-etsi-urn-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-mahesh-etsi-urn-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. In the Formal URN Namespaces registry on the Uniform Resource Names (URN) Namespaces registry page located at: https://www.iana.org/assignments/urn-namespaces/ a single, new URN Namespace is to be registerd as follows: URN Namespace: etsi Template: Reference: [ RFC-to-be ] NOTE: We're asking the ISEG-designated experts to confirm that this registration is OK. Expert review will need to be completed before your document can be approved for publication as an RFC. 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 |
2018-08-02
|
03 | Tero Kivinen | Request for Last Call review by SECDIR Completed: Has Issues. Reviewer: Chris Lonvick. |
2018-07-19
|
03 | Tero Kivinen | Request for Last Call review by SECDIR is assigned to Chris Lonvick |
2018-07-19
|
03 | Tero Kivinen | Request for Last Call review by SECDIR is assigned to Chris Lonvick |
2018-07-17
|
03 | Gunter Van de Velde | Request for Last Call review by OPSDIR is assigned to Jon Mitchell |
2018-07-17
|
03 | Gunter Van de Velde | Request for Last Call review by OPSDIR is assigned to Jon Mitchell |
2018-07-14
|
03 | Cindy Morgan | IANA Review state changed to IANA - Review Needed |
2018-07-14
|
03 | Cindy Morgan | The following Last Call announcement was sent out (ends 2018-08-11): From: The IESG To: IETF-Announce CC: ibagdona@gmail.com, draft-mahesh-etsi-urn@ietf.org Reply-To: ietf@ietf.org Sender: Subject: Last Call: … The following Last Call announcement was sent out (ends 2018-08-11): From: The IESG To: IETF-Announce CC: ibagdona@gmail.com, draft-mahesh-etsi-urn@ietf.org Reply-To: ietf@ietf.org Sender: Subject: Last Call: (URN Namespace for ETSI Documents) to Informational RFC The IESG has received a request from an individual submitter to consider the following document: - 'URN Namespace for ETSI Documents' as Informational RFC 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 ietf@ietf.org mailing lists by 2018-08-11. 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 describes the Namespace Identifier (NID) 'etsi' for Uniform Resource Names (URNs) used to identify resources published by European Telecommunications Standards Institute (http://etsi.org). ETSI specifies and manages resources that utilize this URN identification model. Management activities for these and other resources types are handled by the manager of the ETSI Protocol Naming and Numbering Service (PNNS). The file can be obtained via https://datatracker.ietf.org/doc/draft-mahesh-etsi-urn/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-mahesh-etsi-urn/ballot/ No IPR declarations have been submitted directly on this I-D. |
2018-07-14
|
03 | Cindy Morgan | IESG state changed to In Last Call from Last Call Requested |
2018-07-14
|
03 | Ignas Bagdonas | Last call was requested |
2018-07-14
|
03 | Ignas Bagdonas | Last call announcement was generated |
2018-07-14
|
03 | Ignas Bagdonas | Ballot approval text was generated |
2018-07-14
|
03 | Ignas Bagdonas | Ballot writeup was generated |
2018-07-14
|
03 | Ignas Bagdonas | IESG state changed to Last Call Requested from AD Evaluation |
2018-07-14
|
03 | Ignas Bagdonas | IESG state changed to AD Evaluation from Publication Requested |
2018-06-08
|
03 | Mahesh Jethanandani | New version available: draft-mahesh-etsi-urn-03.txt |
2018-06-08
|
03 | (System) | New version approved |
2018-06-08
|
03 | (System) | Request for posting confirmation emailed to previous authors: Miguel Ortega , Mahesh Jethanandani |
2018-06-08
|
03 | Mahesh Jethanandani | Uploaded new revision |
2018-06-07
|
02 | Mahesh Jethanandani | New version available: draft-mahesh-etsi-urn-02.txt |
2018-06-07
|
02 | (System) | New version approved |
2018-06-07
|
02 | (System) | Request for posting confirmation emailed to previous authors: Miguel Ortega , Mahesh Jethanandani |
2018-06-07
|
02 | Mahesh Jethanandani | Uploaded new revision |
2018-06-07
|
01 | Stewart Bryant | Request for Telechat review by GENART Completed: Ready. Reviewer: Stewart Bryant. Sent review to list. |
2018-06-06
|
01 | Cindy Morgan | Removed from agenda for telechat |
2018-05-31
|
01 | Jean Mahoney | Request for Telechat review by GENART is assigned to Stewart Bryant |
2018-05-31
|
01 | Jean Mahoney | Request for Telechat review by GENART is assigned to Stewart Bryant |
2018-05-31
|
01 | Ignas Bagdonas | Placed on agenda for telechat - 2018-06-07 |
2018-05-31
|
01 | Ignas Bagdonas | Note added 'This is to add ETSI namespace identifier, specifically targeting YANG model development by ETSI.' |
2018-05-31
|
01 | Ignas Bagdonas | IESG process started in state Publication Requested |
2018-05-25
|
01 | Mahesh Jethanandani | New version available: draft-mahesh-etsi-urn-01.txt |
2018-05-25
|
01 | (System) | New version approved |
2018-05-25
|
01 | (System) | Request for posting confirmation emailed to previous authors: Miguel Ortega , Mahesh Jethanandani |
2018-05-25
|
01 | Mahesh Jethanandani | Uploaded new revision |
2018-05-24
|
00 | Ignas Bagdonas | Stream changed to IETF from None |
2018-05-24
|
00 | Ignas Bagdonas | Shepherding AD changed to Ignas Bagdonas |
2018-05-24
|
00 | Ignas Bagdonas | Intended Status changed to Informational from None |
2018-05-17
|
00 | Mahesh Jethanandani | New version available: draft-mahesh-etsi-urn-00.txt |
2018-05-17
|
00 | (System) | New version approved |
2018-05-17
|
00 | Mahesh Jethanandani | Request for posting confirmation emailed to submitter and authors: Miguel Ortega , Mahesh Jethanandani |
2018-05-17
|
00 | Mahesh Jethanandani | Uploaded new revision |