Re: [TLS] PR#634: Registry for TLS protocol version ID

2016-10-18 Thread Joseph Salowey
It doesn't look like we have enough consensus to adopt this proposal. Thanks, J On Sun, Oct 16, 2016 at 6:03 PM, Eric Rescorla wrote: > Chairs: Can you advise on the disposition of this? > > -Ekr > > > On Wed, Oct 12, 2016 at 6:10 PM, Martin Thomson >

Re: [TLS] PR#634: Registry for TLS protocol version ID

2016-10-16 Thread Eric Rescorla
Chairs: Can you advise on the disposition of this? -Ekr On Wed, Oct 12, 2016 at 6:10 PM, Martin Thomson wrote: > On 13 October 2016 at 12:07, Eric Rescorla wrote: > > I assume you would prefer hex, i.e., 0x0303? > > Yeah, that would be nice: it's

Re: [TLS] PR#634: Registry for TLS protocol version ID

2016-10-12 Thread Martin Thomson
On 13 October 2016 at 12:07, Eric Rescorla wrote: > I assume you would prefer hex, i.e., 0x0303? Yeah, that would be nice: it's recognizably the same as the old one that way. ___ TLS mailing list TLS@ietf.org

Re: [TLS] PR#634: Registry for TLS protocol version ID

2016-10-12 Thread Eric Rescorla
On Wed, Oct 12, 2016 at 5:55 PM, Martin Thomson wrote: > On 13 October 2016 at 10:00, Eric Rescorla wrote: > > I would prefer we not merge this PR. > > I concur, though I would prefer if we stopped using the strange { 3, 3 > } notation for versions, it's

Re: [TLS] PR#634: Registry for TLS protocol version ID

2016-10-12 Thread Martin Thomson
On 13 October 2016 at 11:59, Dave Garrett wrote: > One added feature we get with this registry definition is a range of > codepoints for private experimental use. Formal definition might not be > strictly needed here, though it shouldn't hurt. The same can be achieved

Re: [TLS] PR#634: Registry for TLS protocol version ID

2016-10-12 Thread Dave Garrett
On Wednesday, October 12, 2016 07:00:34 pm Eric Rescorla wrote: > This PR involves two changes: > > 1. Attaching the term "ID" to version and defining new enum code points. > 2. Creating a registry > > The first of these seems obfuscatory and unhelpful. The second just seems > unnecessary. Other

Re: [TLS] PR#634: Registry for TLS protocol version ID

2016-10-12 Thread Martin Thomson
On 13 October 2016 at 10:00, Eric Rescorla wrote: > I would prefer we not merge this PR. I concur, though I would prefer if we stopped using the strange { 3, 3 } notation for versions, it's not useful and it implies a significance to the separation that just doesn't exist*. [*]

Re: [TLS] PR#634: Registry for TLS protocol version ID

2016-10-12 Thread Eric Rescorla
On Wed, Oct 12, 2016 at 3:26 PM, Sean Turner wrote: > Al, > > David Garrett has generated PR#634 (https://github.com/tlswg/ > tls13-spec/pull/634) to "explicitly [rename] the protocol version fields > as IDs and defines a registry for all values, as they're really just >

Re: [TLS] PR#634: Registry for TLS protocol version ID

2016-10-12 Thread Salz, Rich
> David Garrett has generated PR#634 (https://github.com/tlswg/tls13- > spec/pull/634) +1 ___ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls