[IPP] Fwd: [saag] TLS WG report from IETF104
Ira McDonald via ipp <ipp@pwg.org> Wed, 27 March 2019 18:53 UTC
Return-Path: <ipp-bounces@pwg.org>
X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com
Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC884120368 for <ietfarch-ipp-archive@ietfa.amsl.com>; Wed, 27 Mar 2019 11:53:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" 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 kUBFEOQGfJ_u for <ietfarch-ipp-archive@ietfa.amsl.com>; Wed, 27 Mar 2019 11:53:30 -0700 (PDT)
Received: from www.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id B9E58120364 for <ipp-archive2@ietf.org>; Wed, 27 Mar 2019 11:53:30 -0700 (PDT)
Received: by www.pwg.org (Postfix, from userid 1002) id 250FF3F9B; Wed, 27 Mar 2019 18:53:30 +0000 (UTC)
Received: from www.pwg.org (localhost [IPv6:::1]) by www.pwg.org (Postfix) with ESMTP id 1A0E326DC; Wed, 27 Mar 2019 18:53:25 +0000 (UTC)
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by www.pwg.org (Postfix, from userid 1002) id A18D22689; Wed, 27 Mar 2019 18:53:23 +0000 (UTC)
Received: from mail-yw1-xc33.google.com (mail-yw1-xc33.google.com [IPv6:2607:f8b0:4864:20::c33]) by www.pwg.org (Postfix) with ESMTPS id AF50E2689 for <ipp@pwg.org>; Wed, 27 Mar 2019 18:53:22 +0000 (UTC)
Received: by mail-yw1-xc33.google.com with SMTP id w66so946490ywd.4 for <ipp@pwg.org>; Wed, 27 Mar 2019 11:53:22 -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; bh=mAK/GIKHk9YwsbQlTIPxE22dE9b7VYiRhmwL51fyzm8=; b=KLnVXFBWUSTaRd2iaR01w5Iq1S/s3cdsHOoaR+3ZCD56eTzT1qybfQgvhjVwgxsxaH 7rj2N3iOzRvupArasYVAAVnWwm9O7M+whO8Gmv8VmSF3TD7tNfwFJoCNnIGLjSnOp/zR ZrTukDIOwPmo512s+oazrhSj5zjoKL+bPZ6UE2ZIi04A1nulnwcroAz2njVLH107BMED eMvCX7FRBrbGl4rKRv2w4DJvdQVVe0qbAcYK/4I9srFMk5X+Mm28tkexYR9ppDFEu1iA pWNpkJWwS4OxFhUyiLLVH93mqi64q4hU+YtutrS0o8F8aiCNrC6uupzj2n/gC2EyJxso seRQ==
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; bh=mAK/GIKHk9YwsbQlTIPxE22dE9b7VYiRhmwL51fyzm8=; b=GMCv+qhCGvDioz/QFvlzW378ARUw6MDTWJAVTBtxgUlKvUevFEo+5nFxHze5c4Mi4n 0l2P4HTQr9w3JVtha/ZSZjGWgYOrKOEm3UguLRM/9X1E2St2b0C8FzuAxaMUh9RDNmUP CAZn5Az6AmEqpfDom6u6zBGZJSQM99kCf6Bm9v8LLmeChddHQcbo+/fc6I9XIUGqPMu5 zuS1u7P8MLJ9fdQhdo55L6W7Y3l2M35OT/L6O3yG0Tj9sYdRZBHjElzhIxo7Qgbmc350 PA9Q8nbRqCXIgjq6tY1i6ccJ0rW6GUdx5BfD9D9vJzf7qeOcrOC/JrR6N5Zjy5XhQz0E Y+YQ==
X-Gm-Message-State: APjAAAV294Z40soFPZiIGD+kp3XNssm+RRYDkQCbkCcuGaDHzeHf4qg1 dtoHoJNVXKyrF9QaER9ZgAQ/p9i6WGnso+BXy1A=
X-Google-Smtp-Source: APXvYqxHWJAO7Fz7+I3LAUJarjq39egRt/sXcdOyBCEW8tUutYamrE9GumextoxxmJSqoAEObPLPggKUOKC7TjX7SVM=
X-Received: by 2002:a25:e686:: with SMTP id d128mr31172736ybh.193.1553712802038; Wed, 27 Mar 2019 11:53:22 -0700 (PDT)
MIME-Version: 1.0
References: <CAO8oSXm1baYvtMLckdcWnKoRcWGqSiNyaCXjQNY4RuBwvPMAmw@mail.gmail.com>
In-Reply-To: <CAO8oSXm1baYvtMLckdcWnKoRcWGqSiNyaCXjQNY4RuBwvPMAmw@mail.gmail.com>
Date: Wed, 27 Mar 2019 14:53:10 -0400
Message-ID: <CAN40gStR9wW1G_4v_H_YgOCuupLMVux2fE3UHjVujSS1B+1KXg@mail.gmail.com>
To: hcd_tc@collaborate.ccusersforum.org, "ipp@pwg.org" <ipp@pwg.org>, Ira McDonald <blueroofmusic@gmail.com>
Subject: [IPP] Fwd: [saag] TLS WG report from IETF104
X-BeenThere: ipp@pwg.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum <ipp.pwg.org>
List-Unsubscribe: <https://www.pwg.org/mailman/options/ipp>, <mailto:ipp-request@pwg.org?subject=unsubscribe>
List-Archive: <http://www.pwg.org/pipermail/ipp/>
List-Post: <mailto:ipp@pwg.org>
List-Help: <mailto:ipp-request@pwg.org?subject=help>
List-Subscribe: <https://www.pwg.org/mailman/listinfo/ipp>, <mailto:ipp-request@pwg.org?subject=subscribe>
From: Ira McDonald via ipp <ipp@pwg.org>
Reply-To: Ira McDonald <blueroofmusic@gmail.com>
Content-Type: multipart/mixed; boundary="===============5753119028504526520=="
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>
FYI ---------- Forwarded message --------- From: Christopher Wood <christopherwood07@gmail.com> Date: Wed, Mar 27, 2019 at 2:15 PM Subject: [saag] TLS WG report To: <saag@ietf.org> TLS met on Monday and Tuesday. Several documents are ready for submission to the IESG. The WG is prepared to address comments when they come. draft-ietf-tls-dtls13-30 is nearly complete with a few issues to address. Initial interop between Mint and NSS was completed prior to the meeting, with mbedTLS support coming soon. The document will not go through another WGLC once interop is complete and issues are resolved. draft-ietf-tls-subcerts is ready for WGLC having received formal analysis since its last update. draft-ietf-tls-oldversions-deprecate is also ready for WGLC after deprecating DTLS 1.0 in addition to TLS 1.0 and 1.1. The WG discussed draft-ietf-tls-certificate-compression and the outstanding issue regarding how to include the compressed certificate in the transcript. Participants signalled disinterest in changing the current draft. Authors will write up the changes and chairs will begin the WGLC process. draft-ietf-tls-tls13-cert-with-extern-psk will likely be ready for WGLC with experimental status after more review. There are no implementations nor formal analysis for the design. The WG discussed updates to draft-ietf-tls-esni, including an initial multi-CDN solution and improved robustness. Participants raised concerns about the current solution’s operational impacts and unknown edge cases. Representative ESNI clients also expressed the desire to minimize performance regressions for any solution. Authors will work with members in the DNS community for additional feedback going forward, though not block on that feedback. draft-sy-tls-resumption-group and draft-wood-tls-external-psk-importer have rough consensus to adopt as WG items. Chairs will confirm on the list. The WG discussed draft-kinnear-tls-client-net-address and general NAT detection use cases. Concerns around client usage of address information were raised. Authors will continue engaging on the list for further discussion. Draft-tschofenig-tls-cwt was also presented with no time for comments or questions. The WG also discussed draft-sullivan-tls-opaque as a way to add OPAQUE to TLS 1.3. Concerns around PAKE usefulness and lack of formal analysis were raised. This PAKE will also be discussed in the CRFG. draft-stebila-tls-hybrid-design discussed a framework for supporting multiple key exchange algorithms in TLS 1.3. Participants signaled an interest in choosing one design general that minimizes complexity instead of surveying different design decisions. Concerns about immaturity of the field of key exchange combiners were raised. The WG also discussed draft-wang-tls-raw-public-key-with-ibc. This document will not be adopted, and the authors will request codepoint allocations from the designated experts. Draft-belyavskiy-fakesni was discussed. Participants raised concerns about the proposed approach and its efficacy when compared to the attacks listed in draft-ietf-tls-sni-encryption. _______________________________________________ saag mailing list saag@ietf.org https://www.ietf.org/mailman/listinfo/saag
_______________________________________________ ipp mailing list ipp@pwg.org https://www.pwg.org/mailman/listinfo/ipp
- [IPP] Fwd: [saag] TLS WG report from IETF104 Ira McDonald via ipp