- From: iri issue tracker <trac+iri@trac.tools.ietf.org>
- Date: Thu, 17 Nov 2011 02:15:56 -0000
- To: draft-ietf-iri-4395bis-irireg@tools.ietf.org, dthaler@microsoft.com
- Cc: public-iri@w3.org
#107: Clarify requirement for security considerations
Section 4 (Guidelines for Provisional URI/IRI Scheme Registration) allows
registration by third parties (even if not
on behalf of those who created the scheme). While many of the required
pieces of information are "SHOULD"s, it says:
"A valid Security Considerations section, as required by Section 6
of [RFC5226]."
If the third party does not have access to the spec (e.g., because it's
owned by an SDO or company without an open spec), the third party may not
be able to write a "valid" security considerations section. I ran into
this personally.
Need to either make it a SHOULD, or else clarify what is needed in a
"valid" section.
--
-----------------------------+---------------------------------------------
Reporter: dthaler@… | Owner: draft-ietf-iri-4395bis-irireg@…
Type: defect | Status: new
Priority: major | Milestone:
Component: 4395bis-irireg | Version:
Severity: Active WG | Keywords:
Document |
-----------------------------+---------------------------------------------
Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/107>
iri <http://tools.ietf.org/wg/iri/>
Received on Thursday, 17 November 2011 02:16:38 UTC