>>>>> "Barry" == Barry Leiba <barryleiba@xxxxxxxxxxxx> writes:
>> More substantively, I fail to understand how this specification
>> proposes to create a class of "reserved" about: URIs when the
>> about: scheme seems to be internal information to an
>> application. I think the Security Considerations section doesn't
>> address any of that, and probably ought to, particularly in light
>> of the proposal to add text that users ought not to depend on
>> "standard" behaviour.
Barry> Yes... I'm actually very confused about the point of this
Barry> document. It's documenting a URI scheme that's used ONLY
Barry> internally, and, therefore, has no interoperability
Barry> requirements. As best I can tell, the issue here is to let
It does. It's an RFC1918-type use, and for the same reason we had to
document those networks, we have to document this URI.
This document prevents someone else from creating "about:" scheme which
is NOT internal.
--
] He who is tired of Weird Al is tired of life! | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] mcr@xxxxxxxxxxxxxxxxxxxxxx http://www.sandelman.ottawa.on.ca/ |device driver[
Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
then sign the petition.
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf