Re: [TLS] TLS@IETF101 Agenda Posted

Artyom Gavrichenkov <ximaera@gmail.com> Fri, 09 March 2018 05:52 UTC

Return-Path: <ximaera@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4962E126DEE for <tls@ietfa.amsl.com>; Thu, 8 Mar 2018 21:52:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I5Eaozk9tdhJ for <tls@ietfa.amsl.com>; Thu, 8 Mar 2018 21:52:37 -0800 (PST)
Received: from mail-ua0-x22e.google.com (mail-ua0-x22e.google.com [IPv6:2607:f8b0:400c:c08::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E1361242EA for <tls@ietf.org>; Thu, 8 Mar 2018 21:52:37 -0800 (PST)
Received: by mail-ua0-x22e.google.com with SMTP id j15so1529430uan.3 for <tls@ietf.org>; Thu, 08 Mar 2018 21:52:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=DF437aSqx+NcKHUAyteSOvrMq8ViYb5X0AHs4V9bimM=; b=VeGIdQ26/u7ntj98LanSvFS58o07CvgwxGd9To/xlxZ9ZnoC9J3tjbaYMrfrR4KC7c mK5nUBO4ElYpCLDGhhZd+W1fZDtE3n80ti/62XY/ghUd450j3txSN92aSx2LCj+M7ZTq bxZdwnH52YEZWMGzZI2qecu8EMLXRWlog0hXNa3eSzWenAL6SWVyjXmnW31VFj+d+3L6 TLwSShw80zRCVkXzuov0Rt8BXcMerb90NWOucJE51/0W8s7bBANvRJmndfw4XuP15np6 OVTw3XMayksEYrKSjs6qVAZL978VzzRtEKDAaXGmpxGKp/H+XUre2DYws74xOkPF8joV zLRA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=DF437aSqx+NcKHUAyteSOvrMq8ViYb5X0AHs4V9bimM=; b=qGPq0N75OGYfcy3Zf59XnydS59HlW1+I7ds3yNtsNAv3I9CqSa/MdlYxllQnuVcR4p tkukeg5yXBNVV6fMbXazpT7E0e1CbHU5tMyRhAkby8hhD1B/se50DBgaej7eJ9mT5dUT 1CLOOBq+0ku+UN0uieFFb7gikPATinC6q+bET9OgLIsL4/TA/v/UQ63f/1ibIuBgMC5r NmnrYkumN8SaJxCEHDQ5hlIhoXgIhhAnAXYIVu4q3HL5AKbC/W4WfHdEMFDqHcqPyw4M DwB8tqpOnXJNPDJY3fUC5tChRwrqaLrKh7ubg005IDG1CWHa1h89c3EB+orcVj1ptP52 th1Q==
X-Gm-Message-State: APf1xPCf1Mc6+WntHO+wuGWeL+R5E2h0NZDi66h13n5+blNrz16HViSk ztpuZMeuwL76ycQxT0rktNeTMfNEYOixsn4q3veu1GBX
X-Google-Smtp-Source: AG47ELuwEB7dV3Qt57WLlv8iDH9Qxj/7Yma2EOu1tvw/bBkQ8Ct891bw+RWg/uauntQ8XusreNlErgKf+olfLKFPidI=
X-Received: by 10.176.17.233 with SMTP id q41mr21552441uac.79.1520574755711; Thu, 08 Mar 2018 21:52:35 -0800 (PST)
MIME-Version: 1.0
Received: by 10.159.57.76 with HTTP; Thu, 8 Mar 2018 21:52:15 -0800 (PST)
In-Reply-To: <CAPBBiVT9oe0y5vMiUSh3dy_=goA1k=23mf6DRfxXqx_vq2Ccsg@mail.gmail.com>
References: <6140B7A6-A1C7-44BC-9C65-9BE0D5E1B580@sn3rd.com> <986797a7-81b0-7874-5f39-afe83c86635b@cs.tcd.ie> <CALZ3u+ZUCDLiWkK1Z6sBG_+zZ8Ff+9cDxdkVY+msRtjyNGntKg@mail.gmail.com> <CAPBBiVT9oe0y5vMiUSh3dy_=goA1k=23mf6DRfxXqx_vq2Ccsg@mail.gmail.com>
From: Artyom Gavrichenkov <ximaera@gmail.com>
Date: Fri, 9 Mar 2018 08:52:15 +0300
Message-ID: <CALZ3u+a=QOuTKu1RGLA_tTAKB0PGTWOtC2hDMSrUUwUg=Kb0bA@mail.gmail.com>
To: Darin Pettis <dpp.edco@gmail.com>
Cc: "<tls@ietf.org>" <tls@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/Zip5U2OPWzNb9Oon4Oyv1ysooAs>
Subject: Re: [TLS] TLS@IETF101 Agenda Posted
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2018 05:52:39 -0000

Hi Darin,

I just asked for clarification whether it's on a TLS WG agenda for London.
I'm not quite sure this is a right thread to discuss the contents of that draft.
(In fact, I'm pretty sire it isn't.)

| Artyom Gavrichenkov
| gpg: 2deb 97b1 0a3c 151d b67f 1ee5 00e7 94bc 4d08 9191
| mailto: ximaera@gmail.com
| fb: ximaera
| telegram: xima_era
| skype: xima_era
| tel. no: +7 916 515 49 58


On Fri, Mar 9, 2018 at 2:39 AM, Darin Pettis <dpp.edco@gmail.com>; wrote:
> Artyom,
> Thanks for mentioning the ID and you are right that draft Fenter is the
> supporting problem description.
>
> The reason it was written was to help folks understand why legitimate
> internal out-of-band decryption is still needed on data once it reaches its
> destination and that there isn’t a viable alternative that we are aware of.
> Especially not in-line MitM decryption.  It just doesn’t scale.  The draft
> lists the legitimate internal requirements and speaks to the facts around
> some of the suggestions that have been offered.
>
>  It’s a good read and we are happy to answer questions in advance as needed.
>
> Darin
>
> On Thu, Mar 8, 2018 at 4:11 PM Artyom Gavrichenkov <ximaera@gmail.com>;
> wrote:
>>
>> Hi Sean, Joe,
>>
>> WG also has this at its disposal:
>> https://tools.ietf.org/html/draft-fenter-tls-decryption-00
>> Will that be discussed along with draft-rhrd-tls-tls13-visibility?
>> Those two seem to be rather connected/dependant on each other.
>>
>> | Artyom Gavrichenkov
>> | gpg: 2deb 97b1 0a3c 151d b67f 1ee5 00e7 94bc 4d08 9191
>> | mailto: ximaera@gmail.com
>> | fb: ximaera
>> | telegram: xima_era
>> | skype: xima_era
>> | tel. no: +7 916 515 49 58
>>
>>
>> On Thu, Mar 8, 2018 at 12:21 PM, Stephen Farrell
>> <stephen.farrell@cs.tcd.ie>; wrote:
>> >
>> > Hi Sean, Joe,
>> >
>> > On 08/03/18 16:20, Sean Turner wrote:
>> >> I’ve posted the draft agendas:
>> >>
>> >> Monday:
>> >>
>> >> https://datatracker.ietf.org/meeting/101/materials/agenda-101-tls-sessb
>> >
>> > That includes:
>> > "
>> > TLS Vizability - Russ & Chairs - 30min
>> >  - 10min draft - Russ
>> >   https://datatracker.ietf.org/doc/draft-rhrd-tls-tls13-visibility/
>> >  - 10min discussion - Chairs
>> >  - 10min wrap-up - Chairs
>> > "
>> >
>> > Consider this as an objection to that agenda item
>> > being given any time. I also have some questions
>> > below.
>> >
>> > This topic was discussed at length in Prague with a
>> > very clear lack of consensus to consider any work in
>> > that space, despite there being quite a few fans of
>> > doing such work in the room that day. I don't see
>> > that anything has changed in the meantime.
>> >
>> > Russ' draft was discussed on the list last year, also
>> > with (ISTM) no consensus at all to do any work in
>> > that space. (While you didn't make a consensus call,
>> > am I wrong?) The -01 version is not significantly
>> > different from what was discussed on the list so I
>> > see no need for any presentation nor discussion time.
>> >
>> > Given the above, on what basis are meeting attendees
>> > being asked to waste yet more f2f time on this topic?
>> >
>> > And why is another want-it/hate-it exercise useful?
>> >
>> > As chairs, are you going to continually allow the same
>> > topic to be raised, in the face of a very clear lack
>> > of consensus to do anything in this space? If not,
>> > then what's the plan for ending this?
>> >
>> > Thanks,
>> > S.
>> >
>> > PS: I also strongly object to the "visibility" euphemism,
>> > and while that's partly a comment on the draft, it would
>> > also IMO be a significant error to pose any questions to
>> > the WG based on that euphemism.
>> >
>> >
>> > _______________________________________________
>> > TLS mailing list
>> > TLS@ietf.org
>> > https://www.ietf.org/mailman/listinfo/tls
>> >
>>
>> _______________________________________________
>> TLS mailing list
>> TLS@ietf.org
>> https://www.ietf.org/mailman/listinfo/tls