An Architecture for DNS-Bound Client and Sender Identities
draft-ietf-dance-architecture-10

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, dance-chairs@ietf.org, dance@ietf.org, draft-ietf-dance-architecture@ietf.org, paul.wouters@aiven.io, rfc-editor@rfc-editor.org, wjhns1@hardakers.net
Subject: Document Action: 'An Architecture for DNS-Bound Client and Sender Identities' to Informational RFC (draft-ietf-dance-architecture-10.txt)

The IESG has approved the following document:
- 'An Architecture for DNS-Bound Client and Sender Identities'
  (draft-ietf-dance-architecture-10.txt) as Informational RFC

This document is the product of the DANE Authentication for Network Clients
Everywhere Working Group.

The IESG contact persons are Paul Wouters and Deb Cooley.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dance-architecture/

Ballot Text

Technical Summary

   This architecture document defines terminology, interaction, and
   authentication patterns, related to the use of DANE DNS records for
   TLS client and messaging peer identity, within the context of
   existing object security and TLS-based protocols.

Working Group Summary

   Was there anything in the WG process that is worth noting?
   For example, was there controversy about particular points 
   or were there decisions where the consensus was
   particularly rough? 

Document Quality

   Are there existing implementations of the protocol?  Have a 
   significant number of vendors indicated their plan to
   implement the specification?  Are there any reviewers that
   merit special mention as having done a thorough review,
   e.g., one that resulted in important changes or a
   conclusion that the document had no substantive issues?  If
   there was a MIB Doctor, Media Type, or other Expert Review,
   what was its course (briefly)?  In the case of a Media Type
   Review, on what date was the request posted?

Personnel

   The Document Shepherd for this document is Wes Hardaker. The Responsible
   Area Director is Paul Wouters.

IANA Note

  (Insert IANA Note here or remove section)

RFC Editor Note