[Unbearable] Suggestions for TTRP

Martin Thomson <martin.thomson@gmail.com> Fri, 20 July 2018 17:20 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: unbearable@ietfa.amsl.com
Delivered-To: unbearable@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACC6113117E for <unbearable@ietfa.amsl.com>; Fri, 20 Jul 2018 10:20:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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] 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 VXKkwn220LTF for <unbearable@ietfa.amsl.com>; Fri, 20 Jul 2018 10:20:56 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (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 3AC1D130FB7 for <unbearable@ietf.org>; Fri, 20 Jul 2018 10:20:56 -0700 (PDT)
Received: by mail-oi0-x229.google.com with SMTP id 13-v6so22667367ois.1 for <unbearable@ietf.org>; Fri, 20 Jul 2018 10:20:56 -0700 (PDT)
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=ZJprd3cr5BwvbSZ1oZ0CHMmy2wbd8sW81WP/wGfHLSQ=; b=Rsii+PIrd2fQOAC4XmDcr5JopbvqYTb3dwg1lr3gY+OgnqSSUYX9MUIjZxWE8ZAOPo UOUAiMR8lS7fnu8iQfTxyd4LZA6nVzU7XbYbhivOxH5ldObgDdruOi4l7+HstZUmgH+S 2iyIhF9z8YKYKNC1nTVQatuY/IzW8C46AGMLwTUEq8no+JLKVPEkzFPdAnw/T8YrxHZF lenIcjM2RLZNBZjlbpgpIArJibYnLwK2GQ5GVS7hJzPlrhnC+zhZbEjHiszeVejxGPnD AhkGreqibAlIR0NYfYPz8ldM7webB6dEZspgI91xrCBwd2TzSMhuiXmi+WlL7OX1RlIt cxyA==
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=ZJprd3cr5BwvbSZ1oZ0CHMmy2wbd8sW81WP/wGfHLSQ=; b=V5bTox6+qMKn/QELNF8T8o/oYNiL3A4Z0ZSSXjBmCc/rnebi8QFD09UrcMH30GkPFZ NmMNujGxNN+P7XYohY+kQlV2YJ6OW5fKZCAWp+iDnodz5CPxqKGuXhqxZEtAF8fCoGEn 99M0EBGFyR8LI8h6gaVVMtzlkPCwqEBpt+SimWJX1+rF3ypbr+di+4hOJNEeu3Lvp4xi 2Vi4vUeEce0y0VgcodVh6srFk6wHKxhsYtmr1mMu1Y10xemisoF2x0W34l1YU0pw1qhZ loRe1kU/WKsJcaRgYb7jGAFrn6Gctry/limMBtkmxYJUZACOd7WcdcaJ06kA82bMGD8p tkwA==
X-Gm-Message-State: AOUpUlE/LTbY3frfvkgu/7PtqJ6Fhapkmuj3VFiCDDyDhTDaJohDDF3G i8Pa59Lilrj/CDb0pkamuOfRLkjWVgUYGrMZ1NWWSu9Q
X-Google-Smtp-Source: AAOMgpcMHX0PWmyCp9+V3BK+Qq1XUkX29+B1sFjEprpKF8YkrjQ0BS2uhu1HYT/bj6uQYxSoE8c0aLWRyI4HCtMNHpg=
X-Received: by 2002:aca:b208:: with SMTP id b8-v6mr2868520oif.144.1532107255256; Fri, 20 Jul 2018 10:20:55 -0700 (PDT)
MIME-Version: 1.0
From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 20 Jul 2018 13:20:45 -0400
Message-ID: <CABkgnnUtEk0C155tK4br3sL2a2QTqM7jpnuqO2+K-GgCjgfWFg@mail.gmail.com>
To: IETF Tokbind WG <unbearable@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/unbearable/7as549-iGTP1S-PLeLh3NBtak_A>
Subject: [Unbearable] Suggestions for TTRP
X-BeenThere: unbearable@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "\"This list is for discussion of proposals for doing better than bearer tokens \(e.g. HTTP cookies, OAuth tokens etc.\) for web applications. The specific goal is chartering a WG focused on preventing security token export and replay attacks.\"" <unbearable.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/unbearable>, <mailto:unbearable-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/unbearable/>
List-Post: <mailto:unbearable@ietf.org>
List-Help: <mailto:unbearable-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/unbearable>, <mailto:unbearable-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2018 17:21:05 -0000

My comments about authentication were misguided because I somehow
missed that the section entitled "HTTP Headers" was in fact about
authentication.

My suggestion: move the TLS versions section to a new top-level
section and make the contents of the HTTP Headers section the entirety
of the security considerations.  The TLS versions text isn't really a
security consideration and having a more targetted security
considerations section would be clearer.  (Also, it avoids having an
empty top-level section).