IETF Logo Mail Archive

Re: [TLS] TLS@IETF101 Agenda Posted

Darin Pettis <dpp.edco@gmail.com> Tue, 13 March 2018 22:08 UTC

Return-Path: <dpp.edco@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 9A46E129C6B for <tls@ietfa.amsl.com>; Tue, 13 Mar 2018 15:08:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 pxQmDbcyT26Q for <tls@ietfa.amsl.com>; Tue, 13 Mar 2018 15:07:58 -0700 (PDT)
Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::22d]) (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 546E4124D68 for <tls@ietf.org>; Tue, 13 Mar 2018 15:07:58 -0700 (PDT)
Received: by mail-vk0-x22d.google.com with SMTP id l123so781312vke.8 for <tls@ietf.org>; Tue, 13 Mar 2018 15:07:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5m1GKs2kmFEdeq4YM+d2Evedd//01D2eBXoC2rV0qec=; b=g9kjkZd0K0OUovnWk0mxlgRTbsXdkFbLPnmTT9vPYtAXKg7pRCXgwy/xRs+DEE7ydh YQYzy5/GX5GqCVR4cqyaD7zJhNLTEj9gNtmNlBNueb9dKFn0ob6NIFj6ZEBRmFKRVDLs 6Z8sRErDXAFw0xi6PF62+3pS+7gk2VWzDVCdYlK6wYKuwmEQb0WSX1vMWKRND7f8vaQV XnHjxNG5qx96F4MLOgBjlHyG4mmzXOURoa87AH+A3HBCeeZEVqBnmUVtgRFdCsopW41Y wkXhIvqxLSp40LHqKA2KW0SkDQ1ZktCixrLt9i+oZ34NxRLJJv8i90T2na1xBjLUaS5x wdqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5m1GKs2kmFEdeq4YM+d2Evedd//01D2eBXoC2rV0qec=; b=fFi7HJ4cAX1bbb9Dzi5qb9GsU4Ukew01A9uFTjf2JDGJewMXjDghgzE+QdZYnQ1DrE 5FGcBbpwoH3TQNi3c3vDqalRuGLx8JMcysw26rD3WRzvvq3oIwqcmRZPUyolwT2CT0uy nbOm25XkpulTYOZqNkD+fQGc/4EHDu33P/B3VtfNrEPDlqDewmoOPBlCrBymuXch/0pf AubSFAt0Lik9F9z/jKZxubL9u/qLNZ2n49gW+qbBf2GKX/GP3Zlp9klr/l78wkyRFE9B rFGxoAnDSPjajisyVkIYjO856xU6asN1SbsLOsvUbLJDz8fndePKbnbX2TMek4/RnuHt 60ow==
X-Gm-Message-State: AElRT7HbMuk4X1huSwfGmXvWrWnqYZsgOsX4lvZWe+UJlD1dQIZtdZm6 8JXFiCjAmQ4zjvkv3A9Lp3F8Lx0aIvXpY4Kdrw8=
X-Google-Smtp-Source: AG47ELtgxR+ge3xSrL/3F+7OxUYD03IjdLOY4LK0LoYn6Ffs2CnpOZagzz3lvA0A1Tb9F1STrlS3A5hc5LN4LfE7dAs=
X-Received: by 10.31.80.71 with SMTP id e68mr1760994vkb.77.1520978877498; Tue, 13 Mar 2018 15:07:57 -0700 (PDT)
MIME-Version: 1.0
References: <6140B7A6-A1C7-44BC-9C65-9BE0D5E1B580@sn3rd.com> <986797a7-81b0-7874-5f39-afe83c86635b@cs.tcd.ie> <CAOgPGoBYc7O+qmjM-ptkRkE6mRsOYgc5O7Wu9pm3drFp3TVa6Q@mail.gmail.com> <d7dfdc1a-2c96-fd88-df1b-3167fe0f804b@cs.tcd.ie> <CAHbuEH7E8MhFcMt2GSngSrGxN=6bU6LD49foPC-mdoUZboH_0Q@mail.gmail.com> <1a024320-c674-6f75-ccc4-d27b75e3d017@nomountain.net> <2ed0gc.p5dcxd.31eoyz-qmf@mercury.scss.tcd.ie> <d7ec110f-2a0b-cf97-94a3-eeb5594d8c24@cs.tcd.ie> <CAAF6GDcaG7nousyQ6wotEg4dW8PFuXi=riH2702eZZn2fwfLQw@mail.gmail.com> <CAPsNn2XCNtqZaQM6Bg8uoMZRJE+qQakEwvw8Cn9fBm-5H+Xn_A@mail.gmail.com> <3F8142DE-EADB-4AB9-A204-7D87ACDCD3E3@akamai.com> <CAPsNn2VE_7+rWT0fp9rrVnZrgcY7ORLWTee+kf_Av1dqm4CiDQ@mail.gmail.com> <CB55AABB-8937-4F6B-B5AC-B6F262F08A4F@akamai.com> <CAPsNn2U_xG28Tumo3oRkQ+6=BHzgv-6YtgNSpwvhdFFRWc7EQQ@mail.gmail.com> <60905506-354D-4A12-80EB-984029385F7F@akamai.com> <CAPsNn2WNs7OoYToUJ7J1-aKKpxvV5ms8HbuOcF6KCpQpgaz8RQ@mail.gmail.com> <CAL02cgQVait=px0sQ73D3pxYuyhdRi_depwp0mrjvot3opECLQ@mail.gmail.com> <CAPsNn2VMw2HmOGX1BfXTanOkg34OSRorYY8FB=qpsbOfkaeGeA@mail.gmail.com> <76AFDFDF-3384-48CD-9F4F-066FACE88E5A@akamai.com> <CAPsNn2X4eTwaYN08tQbJUd8N=cNikQt-LAWyhoCfhYjOG7VsWw@mail.gmail.com>
In-Reply-To: <CAPsNn2X4eTwaYN08tQbJUd8N=cNikQt-LAWyhoCfhYjOG7VsWw@mail.gmail.com>
From: Darin Pettis <dpp.edco@gmail.com>
Date: Tue, 13 Mar 2018 22:07:47 +0000
Message-ID: <CAPBBiVQD7_J1npeY5j8+B-gAk8w=BS1dKZpntEpaeEaUSRo4YA@mail.gmail.com>
To: nalini elkins <nalini.elkins@e-dco.com>
Cc: "<tls@ietf.org>" <tls@ietf.org>, "Salz, Rich" <rsalz@akamai.com>
Content-Type: multipart/alternative; boundary="001a114e302ab4489a0567527d7a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/3-88v49pZIp_IdzoWedGB83h08g>
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: Tue, 13 Mar 2018 22:08:01 -0000

Richard Barnes and Rich Salz,
Thank you for the kind words.   They are much appreciated!  Best of luck to
Rich with the health concerns too.

It’s been an interesting journey with a lot of great folks.  Will reply to
the issues later as I need to head out at the moment.

-Darin


On Tue, Mar 13, 2018 at 2:20 PM nalini elkins <nalini.elkins@e-dco.com>
wrote:

> All,
>
> The time has gotten away from me.   I have to leave for the airport. I am
> taking my daughter to London & need to get us all packed & out of the house.
>
> I will write respond to all at length either from the airport or in London.
>
> Rich, so sorry about your health issues.  My best wishes for a full and
> complete recovery.
>
> Nalini
>
> On Tue, Mar 13, 2018 at 10:39 AM, Salz, Rich <rsalz@akamai.com> wrote:
>
>>
>>    - I am happy to set up an informal session where all can meet and
>>    talk quietly.   Not everyone will be there on Sunday but maybe Monday
>>    breakfast or during a break?  Just let me know if you are interested & we
>>    can make intros.
>>
>>
>>
>> I won’t be there (health issues), but I’ve already turned down such
>> private invites before.
>>
>>
>>
>> Standing up in front of a WG and talking about unpopular topics is hard.
>> As Richard said, kudo’s to USBank (and a BCBS org) for doing so.  But if
>> you’re not willing to do the hard work, then you don’t get to have the IETF
>> address your concerns.
>>
>>
>>
>> I remember saying before that I firmly believe that the main, and
>> unstated, reason for wanting an IETF RFC on this is so that would-be
>> customers can point to vendors and ask for a common solution at a lower
>> price because the ability is now commoditized.  With all due respect to the
>> people involved, I believe that is still the case.
>>
>>
>>
>> I have heard concerns that it is necessary to have a “speedy” solution.
>> Again, I strongly disagree with this. The standard organizations haven’t
>> even made TLS 1.0 illegal yet, as I said last time.  What makes you think
>> that something is needed in under five years?  I asked that question
>> before, too.
>>
>>
>>
>>
>>
>
>
>
> --
> Thanks,
> Nalini Elkins
> President
> Enterprise Data Center Operators
> www.e-dco.com
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>

v2.23.0 | Report a Bug | By Email