Hi,
On Jul 5, 2013, at 2:37, Joe Touch to...@isi.edu wrote:
A slot should not be granted if there isn't a draft.
when Magnus and me started TSVAREA, the intent was that it be an information
dissemination session, and that IDs were not going to be published through
TSVAREA. (We have TSVWG for
Thanks - the area vs wg distinction makes sense.
Joe
On Jul 6, 2013, at 3:00 PM, Eggert, Lars l...@netapp.com wrote:
Hi,
On Jul 5, 2013, at 2:37, Joe Touch to...@isi.edu wrote:
A slot should not be granted if there isn't a draft.
when Magnus and me started TSVAREA, the intent was that
s/drone/someone/
set autocorrect=false
:-)
On Jul 6, 2013, at 4:03 PM, Joe Touch to...@isi.edu wrote:
On Jul 6, 2013, at 12:15 PM, l.w...@surrey.ac.uk wrote:
First deploy, then tell the IETF about it, and let the IETF put the
documentation into
the preferred 1970s ASCII format.
Well, that's the wrong sequence, too. IANA can allocate numbers at draft stage
long before RFC - as it did for Saratoga http://saratoga.sf.net
But even your sequence says 'tell the IETF', not 'participate in an IETF WG
with all the drones'.
Since QUIC is already deployed worldwide, I am
On 7/6/2013 5:52 PM, l.w...@surrey.ac.uk wrote:
IETF transport focuses on maintaining its existing standards; that's
my point. It's not really set up for experimental work not directly
related to those standards.
I'm not really sure how TSV could be setup any better to do this type
of