The 'mailto' URI Scheme
RFC 6068
Yes
(Alexey Melnikov)
No Objection
(Adrian Farrel)
(Dan Romascanu)
(Gonzalo Camarillo)
(Jari Arkko)
(Ralph Droms)
(Ron Bonica)
(Russ Housley)
(Stewart Bryant)
Note: This ballot was opened for revision 10 and is now closed.
Alexey Melnikov Former IESG member
Yes
Yes
()
Unknown
Peter Saint-Andre Former IESG member
Yes
Yes
(2010-05-03)
Unknown
Please expand acronyms on first use; examples of unexpanded acronyms include "IDNA", "HTML", "XML", and "SMTP". Please check the document for "URL" instead of "URI" (for example, in Section 2 can be found the text "depending on the context where the URL is used"). In Section 4, is "MAY" meant instead of "may" in the following sentence? In cases where the source of an URI is well known, and/or specific header fields are limited to specific well-known values, other header fields may be considered safe, too.
Adrian Farrel Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Dan Romascanu Former IESG member
No Objection
No Objection
()
Unknown
Gonzalo Camarillo Former IESG member
No Objection
No Objection
()
Unknown
Jari Arkko Former IESG member
No Objection
No Objection
()
Unknown
Ralph Droms Former IESG member
No Objection
No Objection
()
Unknown
Robert Sparks Former IESG member
No Objection
No Objection
(2010-05-05)
Unknown
These comments are very minor, but if you are touching the text for some other reason, please consider addressing them: There are a few SHOULD/SHOULD NOT statements that would benefit from support or further explanation of the consequences of violating them. Perhaps some of them would be better restated without using 2119 language? Is it possible to say why the <mailto:addr1@an.example?to=addr2@an.example> form is NOT RECOMMENDED? Why isn't "SHOULD be treated as especially suspect" not "MUST be ignored"? (I'm not suggesting that text change, I'm asking if the document could call out when it might make sense to ignore that SHOULD. "Programs manipulating 'mailto' URIs SHOULD take great care to..." might be better restructured as advice to implementers without using the 2119 word.
Ron Bonica Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
()
Unknown
Sean Turner Former IESG member
(was Discuss)
No Objection
No Objection
(2010-05-06)
Unknown
#1) Sec 5: Don't you mean encrypted as opposed to encoded in the following sentence: If the messages are not encoded, they can also be read at any of those sites.
Stewart Bryant Former IESG member
No Objection
No Objection
()
Unknown