I looked at the new document, and at least on a quick read, I think most of the IETF tracker issues still apply. I updated https://www.w3.org/Bugs/Public/show_bug.cgi?id=19746 , please review.
From: [email protected] [mailto:[email protected]] On Behalf Of Gordon P. Hemsley Sent: Monday, November 05, 2012 12:00 PM To: Larry Masinter Cc: Tobias Gondrom; [email protected]; [email protected] Subject: Re: mime sniffing Larry, Tobias, et al., That's correct; I do not intend to work on this document through the IETF. I think the potentially fluid nature of the material would be better served as a living WHATWG standard than a frozen RFC. I would recommend that websec drop it as a deliverable. With that being said, I am of course willing to listen and respond to any concerns that websec or any other IETF groups have with the document as it currently stands. I've essentially completed my rewrite of the old document, which you are welcome to review: http://mimesniff.spec.whatwg.org/ As for the existing issues in the websec tracker, it is unclear to me which of those remain relevant in the new version of the document. In order to make it easier for me to address those concerns, I ask that they be refiled in the WHATWG Bugzilla component and updated to reflect the current document: https://www.w3.org/Bugs/Public/enter_bug.cgi?product=WHATWG&component=MIME As for a meeting this week, it's not clear to me whether there would be a benefit beyond what could be done online. (I would prefer discussion be archived on the WHATWG mailing list.) However, I am still convinceable, so long as it does not result on any out-of-pocket expenses on my part. Regards, Gordon On Thu, Nov 1, 2012 at 11:39 AM, Larry Masinter <[email protected]<mailto:[email protected]>> wrote: Sorry if there was some confusion. It was reported Adam Barth http://lists.w3.org/Archives/Public/uri/2012Oct/0022.html has walked away from working on IETF and the work moved to WHATWG. So I don't think Gordon plans to work in IETF, but on the other hand, the issues shouldn't be ignored just because the venue has changed. However, I also see http://tools.ietf.org/wg/websec/ still lists draft-ietf-websec-mime-sniff (although as "Expired") so perhaps the websec group hasn't officially dropped the document. > -----Original Message----- > From: Tobias Gondrom > [mailto:[email protected]<mailto:[email protected]>] > Sent: Thursday, November 01, 2012 2:41 PM > To: Larry Masinter; [email protected]<mailto:[email protected]> > Cc: [email protected]<mailto:[email protected]>; > [email protected]<mailto:[email protected]> > Subject: Re: mime sniffing > > Gordon, > > if you live in ATL, it may make sense to attend the websec meeting and > make your suggestions, including possibly for websec to drop the doc and > discuss the draft issues. > If you would want to attend the websec meeting on Thursday afternoon, > you would need a day pass for the conference. > > Alternative, Lary and I (and other interested parties) could meet with > you informally in or around the conference hotel (in which case you > won't need a day pass), preferably before Thursday, so we can integrate > results of our conversation into the wg briefing. > > Best regards, > > Tobias > (co-chair of websec) > > Ps.: cc to Yoav and Alexey my co-chairs > > > On 01/11/12 09:33, Larry Masinter wrote: > > You don't have to be affiliated with a company or organization to > > participate in > the IETF -- just subscribe to the mailing list. > > > > You do have to register to participate in the meeting, but perhaps we can > > just > meet informally, or perhaps we can get you a one-day pass. > > > >> It would be helpful to me if you could monitor the rewrite and resolve > >> any IETF issues that may have been implicitly taken care of during the > >> rewrite. After that, we can discuss the remaining issues further, > >> preferably on IRC or the WHATWG mailing list, or in individual > >> Bugzilla bugs. > > It would be helpful if you could look at the issues -- I can go through > > them with > you -- but so far the edits I've seen don't come close to addressing the > issues > raised before Adam walked away. > > > > > > Larry > > > > > >> -----Original Message----- > >> From: [email protected]<mailto:[email protected]> > >> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of > >> Gordon P. Hemsley > >> Sent: Tuesday, October 30, 2012 7:08 PM > >> To: Larry Masinter > >> Subject: Re: mime sniffing > >> > >> Hey Larry, > >> > >> I am not affiliated with the W3C or IETF in any official capacity, so > >> I won't be attending any of the conferences this year. (I am also not > >> a representative of any organization or company, as I am unemployed.) > >> It is theoretically possible that I could meet with you in Atlanta > >> next week, simply because I live in the area, but I'm not sure that > >> will be necessary. > >> > >> I am in the process of rewriting the mimesniff spec to be more > >> straightforward, and I hope to have that done by the end of this week > >> (though I'm not making any promises). I'll make an announcement to the > >> WHATWG mailing list once I've completed my first pass, but you can > >> follow @mimesniff on Twitter to get information about each commit I > >> make in the process. > >> > >> It would be helpful to me if you could monitor the rewrite and resolve > >> any IETF issues that may have been implicitly taken care of during the > >> rewrite. After that, we can discuss the remaining issues further, > >> preferably on IRC or the WHATWG mailing list, or in individual > >> Bugzilla bugs. > >> > >> Regards, > >> Gordon > >> > >> On Tue, Oct 30, 2012 at 3:45 AM, Larry Masinter > >> <[email protected]<mailto:[email protected]>> > wrote: > >>> if you're working on MIME sniffing now and want to talk about the IETF > tracker > >> issues, find me this week in Lyon or next in Atlanta. > >> > >> > >> -- > >> Gordon P. Hemsley > >> [email protected]<mailto:[email protected]> > >> http://gphemsley.org/ • http://gphemsley.org/blog/ -- Gordon P. Hemsley [email protected]<mailto:[email protected]> http://gphemsley.org/ • http://gphemsley.org/blog/
