On Thu, Nov 14, 2019 at 08:05:34AM -0800, Christopher Wood wrote:
> The only comment that was not integrated was the desire to use the hint
> to express not only a count, but also a bit indicating whether or not
> clients will accept a ticket if the server needs to send one (e.g., if its
> STEK is
On Sat, Nov 16, 2019 at 05:05:46AM -0500, Viktor Dukhovni wrote:
> On Thu, Nov 14, 2019 at 08:05:34AM -0800, Christopher Wood wrote:
>
> > The only comment that was not integrated was the desire to use the hint
> > to express not only a count, but also a bit indicating whether or not
> > clients w
On Sat, Nov 16, 2019 at 02:38:55AM -0800, Benjamin Kaduk wrote:
> > The -03 draft added a sentence suggesting that clients should ask for
> > just
> > one ticket on resumption, but I would like to suggest that this logic
> > belongs in the server.
>
> We should probably be emphasizin
On 16/11/2019 11:04, Viktor Dukhovni wrote:
>> We should probably be emphasizing that *all* policy belongs on the server,
>> and
>> we are just defining a signal for the client to convey some information as
>> input
>> to the server's decision. In that mindset I'm not sure that the "subtract
>>
On Sat, Nov 16, 2019 at 04:38:17PM +, Jeremy Harris wrote:
> > Do you have an alternative suggestion?
>
> The obvious encoding to me would be to reserve the all-bits-set value
> to mean "client wants no tickets", all-bits-clear to mean "client
> prefers to reuse tickets", anything else meanin
On Sat, Nov 16, 2019 at 04:06:17PM -0500, Viktor Dukhovni wrote:
> On Sat, Nov 16, 2019 at 04:38:17PM +, Jeremy Harris wrote:
>
> > > Do you have an alternative suggestion?
> >
> > The obvious encoding to me would be to reserve the all-bits-set value
> > to mean "client wants no tickets", all
On Sat, Nov 16, 2019 at 03:59:53PM -0800, Benjamin Kaduk wrote:
> > That also works, effectively treat 0xff as "-1", but all other
> > values as non-negative, with 0 a request for re-use. An isomorphic
> > encoding, but without the "-1".
>
> [Jeremy had a more eloquent description of the vague s
Issues
--
* tlswg/draft-ietf-tls-esni (+1/-1/💬1)
1 issues created:
- Removing ESNI RRType Considerations (by mrsylerpowers)
https://github.com/tlswg/draft-ietf-tls-esni/issues/202
1 issues received 1 new comments:
- #188 "HKDF-Extract(0, Z)" (1 by sayrer)
https://github.com/tls
