Re: [Unbearable] IPR for HTTPS Token Binding with TLS Terminating Reverse Proxies

Brian Campbell <> Thu, 08 November 2018 07:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 46381130EC6 for <>; Wed, 7 Nov 2018 23:45:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 08eFZCQKhgR1 for <>; Wed, 7 Nov 2018 23:45:23 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::12b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 692CC130F19 for <>; Wed, 7 Nov 2018 23:45:21 -0800 (PST)
Received: by with SMTP id w7-v6so336438itd.1 for <>; Wed, 07 Nov 2018 23:45:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gmail; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gG+B6b5sxWJNH/3et8h6LAI6YA4OF9DfJutteeRlPGI=; b=M6L4ljbe/arP9Ue73w3bVADGg8d6EHB7JZJIksa/qQ+pnqRfTebcdNlshTZp7YDhaT FGtzvJik1IregLIHF0wAQJuPKz7ttEos8RysII7AzYyByt1ED7PoreowFJqc40XDD5nX w/lHJ9y8U0EzGGEvleYBPOhVTdTsVPqjRvJLg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gG+B6b5sxWJNH/3et8h6LAI6YA4OF9DfJutteeRlPGI=; b=a3KMkyBrt1SwMAnpQntwiFdVT2eBx+NGjZONB4bh84NpuoiqwV4rEd54wfuJKMsHAL JeJjjZwtHA9iOQqAlcY83vLA36qjGpT0af/zq9lYxiu7ThkBEr3yyLWZ2/efVhDSkfFw wuB3sfGPjxinKyi9ngseX4ei+aYjeRtqL216/OQhZK+umbmvWtB55d3FgqXPj8vSroii 3vTIFcOZTzSc2PrVBo8eR0I6HuDJOYSuPqfFOytQwQm800D6Nm20eSnfTN37e49dQwBp wDCnj7rgUxbSzp62VOxu5hTlizlFDrIoUzFkJONrn8D+HbyBSPRxJ5PGaGPv+U+I3qUX jHjA==
X-Gm-Message-State: AGRZ1gJaezvk6Rn/JzM4EQVPayV/Y9ujZlQPRPS+O2JvGkySyCX8q/cV OQ71F5OtEyUrT7qtrNcyl7kpEIaKfvopy1M5f//aRS3KInjGWCIwmhLgYxTz9F8gkQkBjv8t4bE HaedCm0jBL7nBYHXAGxX+Uwze/rqR
X-Google-Smtp-Source: AJdET5cxXFc5pKTvh8QWZDfj5kpzlDP+0zJtYzcb22agurKEAE9zq6yAMHONjHbFFikAfXeeXeUXJcdg0t2l5i2RjO0=
X-Received: by 2002:a24:bcc1:: with SMTP id n184-v6mr165241ite.174.1541663120608; Wed, 07 Nov 2018 23:45:20 -0800 (PST)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Brian Campbell <>
Date: Wed, 7 Nov 2018 23:44:54 -0800
Message-ID: <>
To: John Bradley <>
Cc: IETF Tokbind WG <>
Content-Type: multipart/alternative; boundary="000000000000aaf2dc057a226a9d"
Archived-At: <>
Subject: Re: [Unbearable] IPR for HTTPS Token Binding with TLS Terminating Reverse Proxies
X-Mailman-Version: 2.1.29
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: Thu, 08 Nov 2018 07:45:27 -0000

Confirmed. I am not aware of any IPR that pertain to the HTTPS Token
Binding with TLS Terminating Reverse Proxies document.

On Wed, Nov 7, 2018 at 11:38 PM John Bradley <> wrote:

> I am working on the shepherd writeup for HTTPS Token Binding with TLS
> Terminating Reverse Proxies 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. Brian can you please confirm?

_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._