Joe's assertion is wrong. The IETF is not the place where new transport protocols are developed. Transport is recognised as an underresourced area; David Harrington's "Thoughts from a past experimental Nomcom selection for TSV Area Director" http://www.ietf.org/mail-archive/web/ietf/current/msg77880.html discusses that, but did not at any point mention new protocols. The IETF has no time for them, as it's too busy maintaining and finetuning and documenting the existing ones.
First deploy, then tell the IETF about it, and let the IETF put the documentation into the preferred 1970s ASCII format. draft-ietf-http-v10-spec-00 being the classic case in point, written up several years after global web domination. Setting up httpbis to tweak http, after spdy et al were developed outside the IETF and proven successful, is where the IETF is at - and httpbis isn't even in the transport area, despite http increasingly looking like a transport and protocol hourglass waist. The IETF should be grateful that Google wants to tell it about a new transport protocol that it has deployed worldwide. Demanding that it be written up as an internet-draft beforehand is unreasonable, and arguably a waste of effort. imho. Lloyd Wood http://sat-net.com/L.Wood/ ________________________________________ From: tsv-area-boun...@ietf.org [tsv-area-boun...@ietf.org] On Behalf Of Joe Touch [to...@isi.edu] Sent: 05 July 2013 01:37 To: Mikael Abrahamsson Cc: tsv-area@ietf.org Subject: Re: Draft agenda for the IETF-87 TSV Area meeting uploaded A link to a draft would be useful. A slot should not be granted if there isn't a draft. Joe On 7/4/2013 8:10 AM, Mikael Abrahamsson wrote: > On Thu, 4 Jul 2013, ietfdbh wrote: > >> Hi, >> >> What is QUIC? Is there a draft? > > https://docs.google.com/document/d/1RNHkx_VvKWyWg6Lr8SZ-saqsQx7rFV-ev2jRFUoVD34/preview?sle=true > > http://blog.chromium.org/2013/06/experimenting-with-quic.html > http://en.wikipedia.org/wiki/QUIC >
