Re: [TLS] TLS@IETF101 Agenda Posted

nalini elkins <nalini.elkins@e-dco.com> Tue, 13 March 2018 19:20 UTC

Return-Path: <nalini.elkins@e-dco.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 A5571129C56 for <tls@ietfa.amsl.com>; Tue, 13 Mar 2018 12:20:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=e-dco-com.20150623.gappssmtp.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 UrQ1dBMJeQnn for <tls@ietfa.amsl.com>; Tue, 13 Mar 2018 12:20:01 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (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 7B27312426E for <tls@ietf.org>; Tue, 13 Mar 2018 12:20:01 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id m22so1408110iob.12 for <tls@ietf.org>; Tue, 13 Mar 2018 12:20:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=e-dco-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3OEeTDTNlA13ybJSbo+rdRu7WZ8QjuHrNMmlkPRzoHE=; b=d18WtdJFF+7/ZdVkJfCFDvqXcbI5gC4RFl71c/vvV9yFe4rY2+xIC9UXKVf+HRcYoY 7mTlrBBy8MpZZi90iaBwre3z3/8uazXbthWnOlu/zrQpQJiq229kM3LzCdqiD9sxFR7D ltTsCe1HihUw+nsH2lM9yX5zmIptVshTbvnfCh0rEaBmeTL4ERgUHcVraePVCc6qkPTt Vm8r7k6BezWPuz94Db4HCrnA3zol+QtVPuFtftc4Qp0iN68gnelFouICd8roH2YLOXj9 3E/3tTHOfwpC/qbx/xZaVvfeu6Ffblg4eR0bfa4paLZitf7br/4Jb8P+Xpo8GapRTtQB jF6A==
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; bh=3OEeTDTNlA13ybJSbo+rdRu7WZ8QjuHrNMmlkPRzoHE=; b=jMUq0QCHPx5XQK94kOPo3s1NLrzciLvl7YPN/G9B2D35+DzrvQcRg9qVCaFdf3uKqp 5LSDeCmWAaM/v05LZ14b/wNyQfRWB51WCBGn6HKdQMoqlST1OO8t1NldPSlTEteGKRe9 H9OdFAoKcY2APOlJlVZOvr7jc0mC6qlWFcKcMudcsgSH12RCk8bTblO63DonzgOzSbji h2CkzEBOHSlpUFo3jgetLuSYEdq4KJWg+x5d9snBmHkBHzdtxR+zc297VcTEIMupdQ8Q R7hRoc/bYDg7Iez11CnDOXclh/D1gFBWBok4+soQ9aTlpv8Ji2LsIfd8gBNWva0C6Ggr nGZw==
X-Gm-Message-State: AElRT7HGnmrbijZxBkuKIVXDlaIz170ozFJB9HtOJLBjGVsEnXhlp7IQ cKc6F267wQ6XwCX/qFdxmjVBQ+X1XbsAjOmtgKjXgw==
X-Google-Smtp-Source: AG47ELuiTMkHSB2gBqjOfFEozOm1g20nSCwKzClrmBmu/4suM90ryKaCdGr5oaijHKF4eB31xNIchNnbOkbK104SX3Q=
X-Received: by 10.107.201.142 with SMTP id z136mr2146122iof.122.1520968800719; Tue, 13 Mar 2018 12:20:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.2.29.138 with HTTP; Tue, 13 Mar 2018 12:20:00 -0700 (PDT)
In-Reply-To: <76AFDFDF-3384-48CD-9F4F-066FACE88E5A@akamai.com>
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>
From: nalini elkins <nalini.elkins@e-dco.com>
Date: Tue, 13 Mar 2018 12:20:00 -0700
Message-ID: <CAPsNn2X4eTwaYN08tQbJUd8N=cNikQt-LAWyhoCfhYjOG7VsWw@mail.gmail.com>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: Richard Barnes <rlb@ipv.sx>, "<tls@ietf.org>" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0b9ee414ed6405675025be"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/Qx5eep_pmVG3HvWe_GvBqmBUYIw>
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 19:20:04 -0000

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