Return-Path: 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 6C69D1296F4 for ; Fri, 20 Jan 2017 10:02:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.899 X-Spam-Level: X-Spam-Status: No, score=-5.899 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_LOW=-0.7, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 WEgYsBOyPDRS for ; Fri, 20 Jan 2017 10:02:18 -0800 (PST) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (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 03314129536 for ; Fri, 20 Jan 2017 10:02:17 -0800 (PST) Received: by mail-it0-x233.google.com with SMTP id 203so25318658ith.0 for ; Fri, 20 Jan 2017 10:02:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=4mjxvz0VYFdZ7XrYGHimgPqi2+12Dnr8ctD5kiccvjE=; b=ISr53nlte+HLwWOTZAAFMmCkT0fB1GxRldwQ3+P80V01ji2fdR6ujixFYTod0vgQg6 sp41py8F9dH2wjz5cy5Z8RjmrB2OuCsiwkfRXsVmtY73UNcgx7jli/oxAMRvXKxsRV7f ANTiL08+HDPNIsJpN7wakLyENObsdHn9a76LOXjeVb4zSD33AXeokrZcMw4UDrbVTztL P6l+WIIrcC+1Eh5fL/kfq0d4Pgv8V0ICYodm4FaRFh4KccS3pvUyjiGQbHXiHrmJAgja pCH2WsEJZx0rxYIk21wceGerNNb3E9LDyYRzLpzyBbixGoJ7HDtqW68MCiX9ow7pabYc TvkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=4mjxvz0VYFdZ7XrYGHimgPqi2+12Dnr8ctD5kiccvjE=; b=afO9hJRsEoCfa+Us4ytygrw9AqkGoEWHNbzhxrbOeUeUckq2V8RfjS1DLpYIuebzik ik6w4EMsckyyJ2CmbbO0oftlNG1r7/Q/gR417EuJdiji7kHqF0CbfWwDWuaalVLlMfTF +kLD1BUvwliBs1hG18ju545Y74Ax1gzfbEAATFB5HsjOJJVLerG7GD8DfVDr30VH85XY UqybQGoh8wIybyTQWelEe6EMrXf1uZ3zUxdGlOfMhHkaHBP5uQhk3YRoxfpiOXcGIgLC C6D5/ydcRcy44tG7mhSwGjAb0yfjExgx01WCnALJx7maciOGncQxz7HBmWy8gI3Fkeo9 UyGg== X-Gm-Message-State: AIkVDXKPHr2pHpRYM5gnDKOmyaRosRxPZD/+E+YorFQbfWlzQwqomzrlRQwP0iQ37eW+Vm31SZIK12jU4c0Y7q4h X-Received: by 10.36.130.66 with SMTP id t63mr4840193itd.90.1484935337021; Fri, 20 Jan 2017 10:02:17 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.24.204 with HTTP; Fri, 20 Jan 2017 10:02:16 -0800 (PST) In-Reply-To: References: From: Vinod Anupam Date: Fri, 20 Jan 2017 10:02:16 -0800 Message-ID: To: Bill Cox Content-Type: multipart/alternative; boundary=94eb2c088ee247aeba05468a73ef Archived-At: Cc: Tokbind WG , token-binding-team Subject: Re: [Unbearable] Token binding version (0, 10) support is global on google servers X-BeenThere: unbearable@ietf.org X-Mailman-Version: 2.1.17 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, 20 Jan 2017 18:02:20 -0000 --94eb2c088ee247aeba05468a73ef Content-Type: text/plain; charset=UTF-8 On Fri, Jan 20, 2017 at 4:29 AM, Bill Cox wrote: > I'm seeing 5.7K token binding headers per second at the moment, about 5K/s > sending both channel-ID and token binding (probably chrome), and about > 700/s with just token binding (probably not chrome). > Based on information in our logs, the requests with just token binding headers are primarily from Edge. cheers, -Anupam > Bill > > -- > You received this message because you are subscribed to the Google Groups > "token-binding-team" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to token-binding-team+unsubscribe@google.com. > To post to this group, send email to token-binding-team@google.com. > To view this discussion on the web visit https://groups.google.com/a/ > google.com/d/msgid/token-binding-team/CAH9QtQHiMNKTWkExDduH%3DhuCzs% > 3DyVW%2BE7YM3Wnoh0DoeYUe08A%40mail.gmail.com > > . > --94eb2c088ee247aeba05468a73ef Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Fri, Jan 20, 2017 at 4:29 AM, Bill Cox <waywardgeek@google.com= > wrote:
I'm seeing 5.7K token binding headers per second at t= he moment, about 5K/s sending both channel-ID and token binding (probably c= hrome), and about 700/s with just token binding (probably not chrome).

Based on information in our logs, the req= uests with just token binding headers are primarily from Edge.
cheers,
-Anupam


Bill

--
You received this message because you are subscribed to the Google Groups &= quot;token-binding-team" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to token-binding-team+unsubscribe@google.com.
To post to this group, send email to token-binding-team@google.com.
To view this discussion on the web visit https://groups.google.com/a/google.com/d= /msgid/token-binding-team/CAH9QtQHiMNKTWkExDduH%3DhuCzs%3DyV= W%2BE7YM3Wnoh0DoeYUe08A%40mail.gmail.com.

--94eb2c088ee247aeba05468a73ef--