Re: [Doh] [FYI] How Comcast Handles DNS Information

Rob Sayre <sayrer@gmail.com> Mon, 30 September 2019 13:02 UTC

Return-Path: <sayrer@gmail.com>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92D2E120236 for <doh@ietfa.amsl.com>; Mon, 30 Sep 2019 06:02:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 aDxX_jYBuHrI for <doh@ietfa.amsl.com>; Mon, 30 Sep 2019 06:02:54 -0700 (PDT)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 858A2120288 for <doh@ietf.org>; Mon, 30 Sep 2019 06:02:54 -0700 (PDT)
Received: by mail-io1-xd2b.google.com with SMTP id q1so38079021ion.1 for <doh@ietf.org>; Mon, 30 Sep 2019 06:02:54 -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:cc; bh=6lHttitkbdkHA1GK9DARUfHoA6EOszJY+M1S5K0yBCY=; b=rig8yty52bNWC3nIa0EeeyPazusFsS52Kko2t3dHXMWOAHvqg+8zDdsl5v1FmFrDgz p1C9G3KSL1KBoDNZbKK1t1I/xyVdGjlfFgIU/c/vL9byWiMdPcxFozzXOiZwFzSa+DZ7 mawcG8alZFJY24Mt+tDcJyYDsPzZr4/fFrI0CxJkvVn5UOzitDmvMVWXz/LI9CesLGuB ZxoCK4U4Y/6lQi6Zw2P0wAoKjS6zUk0hvmUsD6A32ZcWiBOrIAypTqGXM66D/3wxAp04 /79QhzkZaJG/B8YbcYi015vu6X0jibHs+hMdCTUr7ToaCKXn8lWeaA0PbvYyJxZueuZ1 KLSg==
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:cc; bh=6lHttitkbdkHA1GK9DARUfHoA6EOszJY+M1S5K0yBCY=; b=AnjqeHaKMCvHNkjd1clTsuGHHGHdAHeRp781tGQ3GclNCLdrk5TS/59lcHD07JABod r/eKEQ82imY9cb2xdnQCpX2drFgF7GhYnBqvVDXe3MhwzZSM+xSEqQlkv/BSP3C7lWIu FrOm6DM4NFqqQ4xMiloxImJe9OxpxJU/qsqrkph+VnPOHG6zDJdJrrOtWKdkQfsE0DqM P0+rv+G7D1LQP+prG/hfs8OzhG5Rm2/ibi2QzyIhYzNkCTIgnqDWCzRcwPJSiE0b376+ thtsX8+ttXqJC3ioJkzblaRcicP3mhMBwEvLYlWuEf8VPObG+x2k+vJV9PuwrHA6BDEa YLmA==
X-Gm-Message-State: APjAAAUPe5cLAfN/g08W6bBMe1PSFugFevzo0bkzX7b69suNVumhlzE4 mRgOTLc+XBa1WUqC7FNw8u5LsS3bK+Sld4IQ3HDsDKakBGRrbw==
X-Google-Smtp-Source: APXvYqymB9RDfsH6w+ssUcdzmWup8gu45X1TWxl8l5N0Kih+m8U4q0Uzy+Gsm0uH12y4lRhEjjx9mzkPE0i+DRUiRow=
X-Received: by 2002:a92:9:: with SMTP id 9mr20604707ila.49.1569848572817; Mon, 30 Sep 2019 06:02:52 -0700 (PDT)
MIME-Version: 1.0
From: Rob Sayre <sayrer@gmail.com>
Date: Mon, 30 Sep 2019 20:02:41 +0700
Message-ID: <CAChr6Sz7uLn5dt9qq8nCVMnRkXS5aNbgB5MGkzPV6UXjasHoEA@mail.gmail.com>
To: DoH WG <doh@ietf.org>
Cc: "Livingood, Jason" <Jason_Livingood@comcast.com>
Content-Type: multipart/alternative; boundary="00000000000088b83f0593c4da01"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/PTQQs9_8ujx3rBzy84qdMONsRb4>
Subject: Re: [Doh] [FYI] How Comcast Handles DNS Information
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Sep 2019 13:02:57 -0000

On Wed, 22 May 2019 14:09 UTC, <Jason_Livingood@comcast.com>; wrote:
"I thought I’d take a moment here to confirm Comcast’s position on these
issues. ...[snip] ...our longstanding policy regarding customer DNS queries
is simple: we do not track customers’ DNS data, sell it, or use it for
advertising or marketing."
https://mailarchive.ietf.org/arch/msg/doh/wulCGoLcriQBnybFOo2ub6RBP_w

Hi,

I went to look for a privacy policy that matched the policy stated in this
message. The only policy I found seems to contradict it:

https://www.xfinity.com/corporate/customers/policies/customerprivacy#to-provide-recommendations-and-deliver-relevant-advertising-and-marketing

Am I looking in the wrong place? Perhaps there is a DNS-specific policy
somewhere?

thanks,
Rob