iri issue tracker
2011-12-14 00:35:44 UTC
#70: RFC 2119 language in Section 3.1 of 4395bis
Changes (by masinter@…):
* status: new => closed
* resolution: => fixed
Comment:
Based on the discussion at IETF82, the following changes
< is costly; some parts of URI/IRI processing may be scheme-
dependent,
---
207,209c207,211
< New URI/IRI schemes SHOULD have clear utility to the broad
< Internet community, beyond that available with already
registered URI/IRI
< schemes.
---
-------------------------+---------------------
Reporter: evnikita2@… | Owner:
Type: defect | Status: closed
Priority: major | Milestone:
Component: 4395bis | Version:
Severity: - | Resolution: fixed
Keywords: |
-------------------------+---------------------
Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/70#comment:4>
iri <http://tools.ietf.org/wg/iri/>
Changes (by masinter@…):
* status: new => closed
* resolution: => fixed
Comment:
Based on the discussion at IETF82, the following changes
< is costly; some parts of URI/IRI processing may be scheme-
dependent,
---
may be costly; some parts of URI/IRI processing may be scheme-
dependent,207,209c207,211
< New URI/IRI schemes SHOULD have clear utility to the broad
< Internet community, beyond that available with already
registered URI/IRI
< schemes.
---
New schemes should have utility to the
Internet community beyond that available with already
registeredInternet community beyond that available with already
schemes. The registration document SHOULD discuss the utility
of the scheme being registered.
--of the scheme being registered.
-------------------------+---------------------
Reporter: evnikita2@… | Owner:
Type: defect | Status: closed
Priority: major | Milestone:
Component: 4395bis | Version:
Severity: - | Resolution: fixed
Keywords: |
-------------------------+---------------------
Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/70#comment:4>
iri <http://tools.ietf.org/wg/iri/>