[dispatch] Possible IPR or DKIM key hashes in DNS
Jim Fenton <fenton@bluepopcorn.net> Tue, 28 March 2017 03:02 UTC
Return-Path: <fenton@bluepopcorn.net>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83F09127058 for <dispatch@ietfa.amsl.com>; Mon, 27 Mar 2017 20:02:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, LOTS_OF_MONEY=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net
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 EW0sGEfvGuKU for <dispatch@ietfa.amsl.com>; Mon, 27 Mar 2017 20:02:54 -0700 (PDT)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3A131292AE for <dispatch@ietf.org>; Mon, 27 Mar 2017 20:02:54 -0700 (PDT)
Received: from dhcp-b9c8.meeting.ietf.org (dhcp-b9c8.meeting.ietf.org [31.133.185.200]) (authenticated bits=0) by v2.bluepopcorn.net (8.14.4/8.14.4/Debian-8+deb8u1) with ESMTP id v2S32q3G010763 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <dispatch@ietf.org>; Mon, 27 Mar 2017 20:02:54 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bluepopcorn.net; s=supersize; t=1490670174; bh=pP01PPIk5qyf+I6cOf+SjRwMEbMR3+WdkHUkBSVxDrk=; h=To:From:Subject:Date; b=K/EuSSEyqXyVw2OjwwKo2rVmq3Bi2xDiGbgexGQnMswpRT2ZDiD/mRO02MhJssaqZ OB7r81wTuXhTaAEnMzGMhC5PyrLxRyjs6QxItCQU1egOi1iyAyBUkj7/wt5Evheg8S fZOt9l4kB6TwMLQ/5SG7/nstWAnB2ZvCGMWs++lw=
To: dispatch@ietf.org
From: Jim Fenton <fenton@bluepopcorn.net>
Message-ID: <b8e4dec4-ebda-a4cd-74c7-3b37d0536426@bluepopcorn.net>
Date: Mon, 27 Mar 2017 20:02:51 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/3DOEHTlGXZdtjqU9PQuk6JTTD0o>
Subject: [dispatch] Possible IPR or DKIM key hashes in DNS
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Mar 2017 03:02:56 -0000
In this morning's DISPATCH meeting, I didn't intend to scare people away from the idea of putting key hashes in DNS, just to point out that there is a possibly relevant patent. It is: https://www.google.com/patents/US7437558 Hopefully that isn't a problem. -Jim