Re: [Unbearable] Sec- prefixing the TTRP headers

Nick Harper <> Fri, 28 July 2017 21:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 126E712EC11 for <>; Fri, 28 Jul 2017 14:21:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Status: No, score=-2.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bfjslVx1aMdT for <>; Fri, 28 Jul 2017 14:21:51 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4010:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DDC21132186 for <>; Fri, 28 Jul 2017 14:21:50 -0700 (PDT)
Received: by with SMTP id y15so95737575lfd.5 for <>; Fri, 28 Jul 2017 14:21:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=23WSnXkO92vBtgPOIyz2yiSEfv8+GGMvAE0tcM2/iLs=; b=Zz6FieE+updhIxdcEhnjaJyZJpOUbhigN9ktJ3Rj7gRwNw5c2PWxALW1yGnSGkuoHr bGnTDyBecpYVCM/vvQoHJH7JRSB0p+EBJfJQ6WYTFpjndB5U2XyXUdgK7IuX3es/AfH3 LCJxz3RrBbgGK0dCSnJcY+X9HsSJxy9b4QDi2RJUdWM5TR9Jc0x13SJob9YbA0urB43a 3pIuCdwjhk4y0eNfzIeLbgUOY3/l9LbJok1uPm63n111ZijC3OAHkiiC+vsh9tp7/MjV s1/7bdv/uQByb3x9qnMDFySxXZf0wp46jLXF2CLaNN3DHwNEqW1od2Dq1VXnGwlUkDdv 7Wlg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=23WSnXkO92vBtgPOIyz2yiSEfv8+GGMvAE0tcM2/iLs=; b=O4ljFkJMXsPU6fUBNP1mN5c4j6BHsyOZhviCh0gUoRi7f3yE+STh9/T0DgbFN9BSZh tiuihjnNHZ17mCAOa9uL4gKSd6Zpph4P/N2ycxPtAkL2jkBfWQdQoKLH+g1NH3L7wPNM 611xuaBksVGa4ONzzCCNfmiNN7iDZxA8PytGaGdXHJrqGvI6QrXsheAlG/eMkxd+/gqH irpQMquCTwM1CHBxpX7TwS6D3FX0ZTPq4p8pMzhWCT+HkKbEOQzGThRzsrEENiAhjKFL 5n9culA7CZkcR+o2u+75nTqxy4r5jzf/mZIlCYjZjxln4YmyoqiGrXuBi54d5ql/0GTH ju0Q==
X-Gm-Message-State: AIVw113+p6UX3nr4ainsBT8fi4+yj8iQ5clLb1kAZheR8YszTuwyKaZq 1eenDIcYV6gxjslCAEVK71lItZxZLTXY
X-Received: by with SMTP id u189mr3550815lja.110.1501276908883; Fri, 28 Jul 2017 14:21:48 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Fri, 28 Jul 2017 14:21:28 -0700 (PDT)
In-Reply-To: <>
References: <>
From: Nick Harper <>
Date: Fri, 28 Jul 2017 14:21:28 -0700
Message-ID: <>
To: Brian Campbell <>
Cc: IETF Tokbind WG <>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
Subject: Re: [Unbearable] Sec- prefixing the TTRP headers
X-Mailman-Version: 2.1.22
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.\"" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 28 Jul 2017 21:21:53 -0000

That sounds like a good idea to add the Sec- prefix.

On Fri, Jul 28, 2017 at 2:14 PM, Brian Campbell
<> wrote:
> My sense in the Prague meeting was that the was pretty good consensus that
> the Sec- prefix should be used for the headers defined in -tokbind-ttrp.
> That make them "Sec-Provided-Token-Binding-ID" and
> "Sec-Referred-Token-Binding-ID". So, unless there's feedback on the list
> here that there's not consensus for it, I'll make that change in the next
> revision.
> CONFIDENTIALITY NOTICE: This email may contain confidential and privileged
> material for the sole use of the intended recipient(s). Any review, use,
> distribution or disclosure by others is strictly prohibited.  If you have
> received this communication in error, please notify the sender immediately
> by e-mail and delete the message and any file attachments from your
> computer. Thank you.
> _______________________________________________
> Unbearable mailing list