W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2016

rs parameter in encrypted content coding

From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 9 Dec 2016 03:29:39 +0900
Message-ID: <CABkgnnXvgDO1kZyUi5sHSBaDn2P-VuWNCD-7xn4jkVLBAG9hOA@mail.gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>, "Manger, James H" <James.H.Manger@team.telstra.com>
James opened this:

https://github.com/httpwg/http-extensions/issues/274

I'm close to pushing a new version based on what we discussed at the
meeting.  This would seem to be an open issue.  Here are the choices:

1. what we have now, rs = record without authentication tag
2. what James suggests rs includes auth tag
3. something else

My original hope was to avoid having any potential values that were
invalid, but we already got there with padding (rs=0,1,2 are all
invalid).

Personally, I don't find the lack of generality to be problematic, but
I agree that the choice is a little arbitrary.  I'd be interested in
hearing what other people think.
Received on Thursday, 8 December 2016 18:30:17 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 8 December 2016 18:30:24 UTC