[TLS] comment on draft-ietf-tls-subcerts

Rob Sayre <sayrer@gmail.com> Mon, 04 November 2019 22:13 UTC

Return-Path: <sayrer@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 E8442120928 for <tls@ietfa.amsl.com>; Mon, 4 Nov 2019 14:13:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 WK5C-zFpF3ao for <tls@ietfa.amsl.com>; Mon, 4 Nov 2019 14:13:56 -0800 (PST)
Received: from mail-il1-x132.google.com (mail-il1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (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 E1C01120AD8 for <tls@ietf.org>; Mon, 4 Nov 2019 14:13:55 -0800 (PST)
Received: by mail-il1-x132.google.com with SMTP id m5so7193692ilq.0 for <tls@ietf.org>; Mon, 04 Nov 2019 14:13:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=hc6uR+hhhulw0E3yRw+Iw6owo2i0wKl2f377MKmgIIE=; b=uymYxANAqb8SnkKYMoKXBJ5NCp1iITaLkXtstf+E2jRo4+5qkJ1a2kxtPzuE7VfatT Y5x/CCtN8G+iJp25cYjWmXJ/JFDw/6Fun3rTRdwsRZlLgHi6VHAW8KWIN7zyDfXEQXs6 dO5ZfMd6TtIVLTdYXU5KZfqUxuVMrbdVB6uuw8agPNtkDQUPfiDaGIPtFDHxoVIAG5GK oHIfgqXlCRdMnDyar8YEiq2xQioYp8KnkvpuwPUsC7Yal0AJN3p+hRGDH096T03oF8F6 umRm8hGGgR1AMrZOoEa4N7DFtHXx/fDV3uxyqogNGRRnBylLpdZ2J+mAKWylpa7hRKeq BmjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=hc6uR+hhhulw0E3yRw+Iw6owo2i0wKl2f377MKmgIIE=; b=Qd6a/SUWy0M5yne8ELuCUNugcNXQd6TQeXZpkKpRWtLYF//Cn8wvFOrS9aPDvSa/id Yly6/2j1DVBZvt11M2XjZOKHkfvzTPmvnt+Uw8V7EsWYl0TGN2faMMfeFaWZgnnzrfwt UVZhsy5hLRR5Ib4IC0h68NIRDSZDQC75zRFVOT8ikde+SwSONQ7hge0PYMiAtR9bq7HW zl/lC5ebLxES5qcdPZpbO8oVf70sj13W9kzu2rSURvLvdnCYOf/s3M7OqiekI3ji6vR3 hROmJKyUwUKhLPkxH8r9LOdCs68JCRHKjm25WQ9c2XqOH6wedj/hRWU+vqTQghR4U3w6 MZhA==
X-Gm-Message-State: APjAAAU2B4aEBDhboaB4Q4t48qs+Ccq/gU2FpeSzOFdGMfWGXOmg9dWD GQZ3++iFUWShZSUY1qFvnIBSlS+niqfXxyS1qjwBJ9fP4Lg=
X-Google-Smtp-Source: APXvYqxbUX7eBrfQRdu6ngcySpi85m5hYcRzzNQ/pFKzdCO5xaHUcpOE41vnK+ZQdEoOeCg9T2aNLv1I6/MTR4LTBNE=
X-Received: by 2002:a92:3a88:: with SMTP id i8mr14359324ilf.254.1572905634538; Mon, 04 Nov 2019 14:13:54 -0800 (PST)
MIME-Version: 1.0
From: Rob Sayre <sayrer@gmail.com>
Date: Mon, 4 Nov 2019 14:13:43 -0800
Message-ID: <CAChr6Sw9tYpT_iTW0Y_FM406oGFK1vjB82WgUykQp=MZxroz3w@mail.gmail.com>
To: "TLS@ietf.org" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009ca9aa05968ca181"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/rYVCQgAMRcZpUqQABvpjg9tRDtY>
Subject: [TLS] comment on draft-ietf-tls-subcerts
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 04 Nov 2019 22:14:02 -0000

Hi,

I left a comment wondering how this draft might interact with security
issues in the network layer, like the various kinds of BGP hijacking.

https://github.com/tlswg/tls-subcerts/issues/42

That's not to say this draft is the place to fix those problems, but it
seems like it could make them more difficult to detect in some ways. I was
surprised not to see this issue at least mentioned in the Security
Considerations section.

If I'm wrong to suspect this is a concern, it might be helpful to note why
that is.

thanks,
Rob