New Non-WG Mailing List: keyassure -- Key Assurance With DNSSEC

IETF Secretariat <ietf-secretariat@ietf.org> Tue, 17 August 2010 18:36 UTC

Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id CF0433A6807; Tue, 17 Aug 2010 11:36:02 -0700 (PDT)
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: New Non-WG Mailing List: keyassure -- Key Assurance With DNSSEC
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20100817183602.CF0433A6807@core3.amsl.com>
Date: Tue, 17 Aug 2010 11:36:02 -0700 (PDT)
Cc: ondrej.sury@nic.cz, keyassure@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Aug 2010 18:36:03 -0000

A new IETF non-working group email list has been created.

List address: keyassure@ietf.org
Archive:
http://www.ietf.org/mail-archive/web/keyassure/current/maillist.html
To subscribe: https://www.ietf.org/mailman/listinfo/keyassure

Description: This list is for discussion relating to using
DNSSEC-protected DNS queries to get greater assurance for keys and
certificates that are passed in existing IETF protocols. The main idea is
that a relying party can get additional information about a domain name to
eliminate the need for using a certificate in a protocol, to eliminate the
need for sending certificates in the protocol if they are optional, and/or
to assure that the certificate given in a protocol is associated with the
domain name used by the application. In all three cases, the
application associates the key or key fingerprint securely retrieved from
the DNS with the domain name that was used in the DNS query. 

For additional information, please contact the list administrators.