- From: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
- Date: Thu, 10 Jul 2014 21:32:32 +0900
- To: "K.Morgan@iaea.org" <K.Morgan@iaea.org>
- Cc: ynir.ietf@gmail.com, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
- Message-ID: <CAPyZ6=L0x9dPAvqDV1HrKXGrY5e87=XHqNcx2Xww7yHAJ2Teyg@mail.gmail.com>
On Thu, Jul 10, 2014 at 8:00 PM, <K.Morgan@iaea.org> wrote: > Hi Yoav- > > On Thursday,10 July 2014 12:47, ynir.ietf@gmail.com wrote: > > Is that for every frame, or just when a large frame size has been > advertised? > > I guess the former, but then we're increasing every frame by 2 bytes for > the > > same of those 0.02% No? > > Our proposal (Greg et al) already had the extra 2 bytes from the > beginning, see the first e-mail (from Greg) in this thread [1]. I simply > extended the reserved bits from 1 to 8 to appease concerns by Roberto and > others that too many bits is too big of a foot gun, but simultaneously > allows future revs of the protocol to *easily* extend the frame length > field if necessary. > > If reserved bits are for future use for larger frame size, why not reserve 16 bits for now? It makes a foot gun even less likely. I heard that many said that 16 bits length is enough for today. With 16 bits available (2 bits extra from h2-13's 14 bits), we can say good bye to CONTINUATION. This solves #549 and #550 (and possibly #551 for < 64KB, but I think it is enough). Extra 16 reserved bits is a possible solution of #553. Best regards, Tatsuhiro Tsujikawa > Our proposal (Greg et al) is *not* just about getting rid of CONTINUATION > frames for the 0.02%. Again, see the first e-mail (from Greg) in this > thread [1] for a _detailed_ analysis of the benefits of this proposal. > It's probably better to comment directly on sections of that e-mail if you > have concerns. > > Thanks. > > -keith > > > [1] http://lists.w3.org/Archives/Public/ietf-http-wg/2014JulSep/0427.html > > This email message is intended only for the use of the named recipient. > Information contained in this email message and its attachments may be > privileged, confidential and protected from disclosure. If you are not the > intended recipient, please do not read, copy, use or disclose this > communication to others. Also please notify the sender by replying to this > message and then delete it from your system. > >
Received on Thursday, 10 July 2014 12:33:19 UTC