- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 11 Feb 2010 18:40:01 +0100
- To: Paul Cotton <Paul.Cotton@microsoft.com>
- CC: Mark Nottingham <mnot@mnot.net>, Maciej Stachowiak <mjs@apple.com>, Jonas Sicking <jonas@sicking.cc>, Larry Masinter <masinter@adobe.com>, Henri Sivonen <hsivonen@iki.fi>, "public-html@w3.org" <public-html@w3.org>
Julian Reschke wrote: > Paul Cotton wrote: >> What is the status of this requested change? >> >> When will >> http://www.mnot.net/drafts/draft-nottingham-http-link-header-07.txt be >> updated? >> >> /paulc >> ... > > draft-nottingham-http-link-header is in (2nd) IETF Last Call, ending > February 17. Mark is likely to submit a new draft once LC is over. > > Best regards, Julian > > PS: for tracking the process, you may find > <https://datatracker.ietf.org/idtracker/draft-nottingham-http-link-header/> > helpful. I was asked to provide some more detail about the process until the IANA registry will be operational. 1) IETF Last Call needs to end (Feb 17, see <http://www.ietf.org/ibin/c5i?mid=6&rid=49&k1=934&k2=7387>) 2) I *assume* that Mark will want to submit a new Internet Draft then, and then request publication. 3) The draft will then be added to the agenda for an upcoming IESG telco (bi-weekly). In the best case, no issues will come up and the IESG will approve it. 4) Once it's approved it gets into the RFC Editor's publication queue, at which point IANA will execute whatever it's being asked for. So, optimally, the registry could be there in five weeks from now. Realistically, I'd expect it to take longer. Best regards, Julian
Received on Thursday, 11 February 2010 17:40:49 UTC