- From: iri issue tracker <trac+iri@trac.tools.ietf.org>
- Date: Wed, 14 Dec 2011 01:51:52 -0000
- To: draft-ietf-iri-4395bis-irireg@tools.ietf.org, masinter@adobe.com
- Cc: public-iri@w3.org
#107: Clarify requirement for security considerations
Comment (by masinter@…):
checking before submitting draft, I wound up rewriting this as:
The scheme definition SHOULD include a clear Security
Considerations
(<xref target='secguide'/>) or explain why a full security
analysis is not available (e.g., in a third-party
scheme registration).
--
----------------------------+----------------------------------------------
Reporter: dthaler@… | Owner: draft-ietf-iri-4395bis-irireg@…
Type: defect | Status: closed
Priority: major | Milestone:
Component: 4395bis-irireg | Version:
Severity: Active WG | Resolution: fixed
Document |
Keywords: |
----------------------------+----------------------------------------------
Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/107#comment:2>
iri <http://tools.ietf.org/wg/iri/>
Received on Wednesday, 14 December 2011 01:54:53 UTC