Re: [Tls-reg-review] Request to register 3 values in TLS ExtensionType Values registry

I suppose we got a reluctant nod from the community.

> On 13 Jun 2020, at 16:11, Salz, Rich <rsalz@akamai.com> wrote:
> 
> Go for it.
>  
> From: Yoav Nir <ynir.ietf@gmail.com>
> Date: Friday, June 12, 2020 at 3:44 PM
> To: Rich Salz <rsalz@akamai.com>
> Cc: "tls-reg-review@ietf.org" <tls-reg-review@ietf.org>
> Subject: Re: [Tls-reg-review] Request to register 3 values in TLS ExtensionType Values registry
>  
> I tend to agree, although that leads me to question the value of what we’re doing here.
>  
> Anyway, I think this is going to lead to yelling, so we might as well get in front of it. I’d like to post a message to the TLS mailing list before we instruct IANA to assign values.
>  
> Objections?
>  
> Yoav
>  
> 
> 
>> On 11 Jun 2020, at 19:29, Salz, Rich <rsalz@akamai.com <mailto:rsalz@akamai.com>> wrote:
>>  
>> Yes, this is where interceptible TLS went after we discarded it.
>>  
>> I don’t think we get a moral vote, tho.
>>  
>> From: Yoav Nir <ynir.ietf@gmail.com <mailto:ynir.ietf@gmail.com>>
>> Date: Thursday, June 11, 2020 at 12:23 PM
>> To: "tls-reg-review@ietf.org <mailto:tls-reg-review@ietf.org>" <tls-reg-review@ietf.org <mailto:tls-reg-review@ietf.org>>
>> Subject: Re: [Tls-reg-review] Request to register 3 values in TLS ExtensionType Values registry
>>  
>> So a protocol for the endpoints to talk to the middle-box and allow it read, read+delete, or read+delete+write access to the data stream?
>>  
>> I think we’ve yelled at people who brought this kind of thing to the IETF in the past.
>>  
>> Does this count as “mostly harmless” because they just want an extension number, not an RFC number?
>>  
>>  
>> 
>> 
>> 
>>> On 11 Jun 2020, at 10:59, Miguel Angel Reina Ortega <MiguelAngel.ReinaOrtega@etsi.org <mailto:MiguelAngel.ReinaOrtega@etsi.org>> wrote:
>>>  
>>> Dear TLS ExtensionType Values Registry Experts,
>>>  
>>> ETSI TC CYBER has developed a Technical Specification TS 103 523-2 "Transport Layer Middlebox Security Protocol (TLMSP)" specifying a protocol to enable secure transparent communication sessions between network endpoints with one or more middleboxes between these endpoints, using data encryption and integrity protection, as well as authentication of the identity of the endpoints and the identity of any middlebox present. The Middlebox Security Protocol builds on TLS 1.2.
>>>  
>>> ETSI TC CYBER is about to approve the final draft TS 103 523-2 for publication and then requests the registration of 3 TLS ExtensionType Values as defined in the final draft TS 103 523-2 available athttps://docbox.etsi.org/CYBER/CYBER/Open/Latest_Drafts/CYBER-0027-2v020-TLMSP-Transport-Layer-Middlebox-Security-Protocol.pdf <https://urldefense.proofpoint.com/v2/url?u=https-3A__docbox.etsi.org_CYBER_CYBER_Open_Latest-5FDrafts_CYBER-2D0027-2D2v020-2DTLMSP-2DTransport-2DLayer-2DMiddlebox-2DSecurity-2DProtocol.pdf&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=4LM0GbR0h9Fvx86FtsKI-w&m=GjSQtH4oNcSoW9gjQc3NeYlpnrqE2zr8mclZf37nr1A&s=qCl0DYOmf9Uc-Y3Rj5hJpWz3Xq4-ge_D1GFn2zOREWY&e=>.
>>> The 3 extensions are defined in the following clauses: 
>>>      * clause 4.3.5 extension named TLSMP 
>>>      * clause C.2.3 extensions named TLMSP_proxying and TLMSP_delegate
>>>      * IANA considerations in annex I
>>>  
>>> Please, note that we will be able to provide the final URL of the published TS only after its publication.
>>>  
>>> Best regards.
>>>  
>>> -----------------------------------------------------------------------------------------------------------------
>>> Miguel Angel Reina Ortega – Testing Expert
>>> Centre for Testing and Interoperability (CTI)
>>> ETSI ● www.etsi.org <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.etsi.org_&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=4LM0GbR0h9Fvx86FtsKI-w&m=GjSQtH4oNcSoW9gjQc3NeYlpnrqE2zr8mclZf37nr1A&s=GhLs_FLSmA-osQ0cKbcT5kqmBsljznhTtIDuG7xtD1k&e=> ● miguelangel.reinaortega@etsi.org <mailto:miguelangel.reinaortega@etsi.org>
>>> Phone: +33 (0)4 92 94 43 49 ● Mobile: +33 (0)6 76 73 60 99
>>>  
>>> This email may contain confidential information and is intended for
>>> the use of the addressee only. Any unauthorized use may be unlawful.
>>> If you receive this email by mistake, please advise the sender
>>> immediately by using the reply facility in your email software.
>>> Thank you for your co-operation.
>>>  
>>> _______________________________________________
>>> tls-reg-review mailing list
>>> tls-reg-review@ietf.org <mailto:tls-reg-review@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/tls-reg-review <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_tls-2Dreg-2Dreview&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=4LM0GbR0h9Fvx86FtsKI-w&m=GjSQtH4oNcSoW9gjQc3NeYlpnrqE2zr8mclZf37nr1A&s=LnFG7aJJ4aJxaWIHASh9HIFTPgnsq62YSGZwB9dNIzY&e=>