Re: [Unbearable] IPR for draft-ietf-tokbind-https

John Bradley <> Tue, 26 September 2017 07:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E79321321D8 for <>; Tue, 26 Sep 2017 00:02:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 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, SPF_PASS=-0.001, URIBL_BLOCKED=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 TkkIPJ0nigKb for <>; Tue, 26 Sep 2017 00:02:46 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4001:c0b::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1BF4B132620 for <>; Tue, 26 Sep 2017 00:02:45 -0700 (PDT)
Received: by with SMTP id m123so1932501ita.3 for <>; Tue, 26 Sep 2017 00:02:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=message-id:mime-version:to:cc:from:subject:date:importance :in-reply-to:references; bh=CI4hojbrM8yrteiwV/l0V66Op5jCpOlaP9d4ZBODwkU=; b=XrIFZFUymQPVBdVrTGycqKU+cg5awXv0s+R1nzH/oy4gCc20XW8BveZA5+xc5UADVo ICYCyne89+Lb7CxM87Vb6fKhO0nWbp+1y4Izk+khJs2HgBZ9yyXTCNze+z3jb7TBhQVa RWAAHBFBpj/MoSOqzZc74zrc1o3XwFWBCj+2q60PON2UKdrIxiyrJRhcjMpt1JOtpJdN s5HsBlbx0w4+on85mB6aEZ+Pufr8ld4vOIFIZ07zocP6Kev0B5LPciQaE0Q10u7LeosP Ojqg0wyfkOupMjMa9wJhSYbM+AB0S9n4LQEeUFtVgZLS5mrwl8eO2WZK82ANipXGa76R DDtg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:message-id:mime-version:to:cc:from:subject:date :importance:in-reply-to:references; bh=CI4hojbrM8yrteiwV/l0V66Op5jCpOlaP9d4ZBODwkU=; b=KwnGaapQ90gOCZ53DJDbb+cSlP/+bPn3Ll/0Pt/ZDYB9JiAAZab80ocTxchp9ZgVFu B/xFdrFaDH36WqvntWflmxXFhmGinNYS5K1L5u5Jr0Gznqunh+lDmeBWWSRFOVqdotil AZCXJMBsTB6h609lxJqWl9FfiiE0imiYWJx3K79hFtKW0oXKJRn/W5qC2xVWQBDeZUql HT8hnLnkke5Gwqs8O/n9RvsKeYEMH91BbvMdPW8mCy35iHZZz4Nv1KmQOqx1D+tDzW+s 4FiAV0wtEeUirIr5XNbe39qmmuS32rJ80iGkU4oJKhPDR/FeSbAbYUhqysTNI0OA1iIb 11Hw==
X-Gm-Message-State: AHPjjUhsbs1xiKisCIIcOrNwIgyyhTqdizuMdawwa97Wqbl3SCjJgUNH fcEgY4/Iye+wS1E72X+ofIczEqmxcSk=
X-Google-Smtp-Source: AOwi7QB/zWMmfAtB8MTX+GPuMq0XoFdTzaVH28/O+WMvpknnJ/eWuCMc35MiaD3X+VqBC85GIG12FQ==
X-Received: by with SMTP id v5mr4475849ith.24.1506409363873; Tue, 26 Sep 2017 00:02:43 -0700 (PDT)
Received: from ?IPv6:::ffff: ([]) by with ESMTPSA id y6sm4086261ioy.54.2017. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 26 Sep 2017 00:02:42 -0700 (PDT)
Message-ID: <>
MIME-Version: 1.0
To: IETF TokBind WG <>
Cc: "" <>, Nick Harper <>
From: John Bradley <>
Date: Tue, 26 Sep 2017 00:02:41 -0700
Importance: normal
X-Priority: 3
In-Reply-To: <>
References: <>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="94eb2c034f520e5336055a124330"
Archived-At: <>
Subject: Re: [Unbearable] IPR for draft-ietf-tokbind-https
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: Tue, 26 Sep 2017 07:02:48 -0000

Nick I don’t have your IPR declaration.  Can you reply to the list.

John B.

Sent from Mail for Windows 10

From: John Bradley
Sent: Sunday, June 18, 2017 6:27 PM
To: IETF TokBind WG
Subject: IPR for draft-ietf-tokbind-https

I am working on the shepherd writeup for the Token Binding over HTTP document:

One item in the template requires me to indicate whether each document
author has confirmed that any and all appropriate IPR disclosures
required for full conformance with the provisions of BCP 78 and BCP 79
have already been filed.

Could each of you please confirm?

   Magnus Nystroem
   Microsoft Corp.


   Dirk Balfanz (editor)
   Google Inc.


   Adam Langley
   Google Inc.


   Jeff Hodges