Re: XLink 1.1: Security Considerations

* Norman Walsh wrote:
>/ Bjoern Hoehrmann <> was heard to say:
>| lacks a section on
>| security considerations. Please include a proper discussion about
>| security and privacy issues in the document, including which issues
>| are considered out of scope of the draft and why. RFC 3552 provides
>| useful guidelines for this, specifically, the document should conform
>| to the requirements in section 5 of that document.
>It's not clear what issues you are concerned about. Would something
>along the lines of the notes in the HTML Recommendation satisfy you?
>  Processing XLink elements may cause URIs to be dereferenced
>  automatically or in response to user input. In this case, the
>  security issues of [RFC1738], section 6, should be considered.

No, RFC 1738 is obviously very outdated, I would instead expect that the
security considerations of RFC 3987 apply, a clear description on which
considerations are out of scope, which are in scope, implications of
user agents implementing e.g. XLink and XHTML where the same link might
go to multiple destinations, probably that UTR #36 applies, that XLink
in XML documents is subject to the security considerations of XML and
XML media types where applicable, and so on, depending on what is con-
sidered in scope and out of scope. It might of course be possible that
some of the items above are considered out of scope, but certainly not
all of them.
Björn Höhrmann · ·
Weinh. Str. 22 · Telefon: +49(0)621/4309674 ·
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · 

Received on Tuesday, 26 July 2005 21:15:31 UTC