Re: Last Call: Adding a fragment identifier to the text/csv media type(see <draft-hausenblas-csv-fragment-06.txt>)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I find the security considerations in this registration rather weak.
What might have sufficed in 2005 seems to me inadequate for 2013.  I
would expect a clearer statement of what are or are not considered
threats or attacks and what mitigations there then are for them.

Tom Petch

----- Original Message -----
From: "The IESG" <iesg@xxxxxxxx>
To: "IETF Announcement List" <ietf-announce@xxxxxxxx>
Cc: <iana@xxxxxxxx>
Sent: Thursday, October 10, 2013 7:50 PM

The IESG has received a request to update the IANA registration of
the text/csv media type, adding an optional fragment identifier.
The request comes from a document in the Independent stream, and the
IESG is the change controller for the text/csv media type.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@xxxxxxxx mailing lists by 2013-10-24. Exceptionally, comments may
be sent to iesg@xxxxxxxx instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

The document making the request can be obtained via
http://datatracker.ietf.org/doc/draft-hausenblas-csv-fragment/






[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]