[iri] #47: Practical length limits on IRIs or components thereoff

[iri issue tracker]

#47: Practical length limits on IRIs or components thereoff


Comment (by masinter@…):

I remember we had a long discussion about this, but don't remember any
recommendation to do anything about imposing a limit.

Perhaps something of the form "This document does not specify any limits
on length of IRIs or any components of them. Generators of IRIs should be
aware of the potential length limits downstream processors might have for
IRIs, parsed IRI components, and the results of translation to parsed URI
components or reconstructed URIs.

Leaving open for now.
--
----------------------+------------------
Reporter: duerst@… | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: 3987bis | Version:
Severity: - | Resolution:
Keywords: |
----------------------+------------------

Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/47#comment:1>
iri <http://tools.ietf.org/wg/iri/>

[Chris Weber]

Post by iri issue tracker
I remember we had a long discussion about this, but don't remember any
recommendation to do anything about imposing a limit.
Perhaps something of the form "This document does not specify any limits
on length of IRIs or any components of them. Generators of IRIs should be
aware of the potential length limits downstream processors might have for
IRIs, parsed IRI components, and the results of translation to parsed URI
components or reconstructed URIs.

That's my understanding too - it would be totally arbitrary to place a
length limit on IRIs or components. You could include an example with
your statement, something like - e.g. some Web browsers and Web servers
have length limitations, which even differ between them.

Best regards,
Chris Weber

[Peter Saint-Andre]

Post by Chris Weber

Post by iri issue tracker
I remember we had a long discussion about this, but don't remember any
recommendation to do anything about imposing a limit.
Perhaps something of the form "This document does not specify any limits
on length of IRIs or any components of them. Generators of IRIs should be
aware of the potential length limits downstream processors might have for
IRIs, parsed IRI components, and the results of translation to parsed URI
components or reconstructed URIs.

That's my understanding too - it would be totally arbitrary to place a
length limit on IRIs or components. You could include an example with
your statement, something like - e.g. some Web browsers and Web servers
have length limitations, which even differ between them.

<hat type='individual'/>

Yes, I think some informational text along those lines might be helpful.

Peter

[iri issue tracker]

#47: Practical length limits on IRIs or components thereoff

Changes (by masinter@…):

* owner: => masinter@…
--
----------------------+-------------------------
Reporter: duerst@… | Owner: masinter@…
Type: defect | Status: new
Priority: major | Milestone:
Component: 3987bis | Version:
Severity: - | Resolution:
Keywords: |
----------------------+-------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/47#comment:2>
iri <http://tools.ietf.org/wg/iri/>