Skip to main content

Additional XML Security Uniform Resource Identifiers (URIs)
draft-eastlake-rfc6931bis-xmlsec-uris-27

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>, draft-eastlake-rfc6931bis-xmlsec-uris@ietf.org, rdd@cert.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Additional XML Security Uniform Resource Identifiers (URIs)' to Proposed Standard (draft-eastlake-rfc6931bis-xmlsec-uris-27.txt)

The IESG has approved the following document:
- 'Additional XML Security Uniform Resource Identifiers (URIs)'
  (draft-eastlake-rfc6931bis-xmlsec-uris-27.txt) as Proposed Standard

This document has been reviewed in the IETF but is not the product of an IETF
Working Group.

The IESG contact person is Roman Danyliw.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-eastlake-rfc6931bis-xmlsec-uris/


Ballot Text

Technical Summary

   This document updates and corrects the IANA "XML Security URIs"
   registry that lists URIs intended for use with XML digital
   signatures, encryption, canonicalization, and key management.  These
   URIs identify algorithms and types of information.  This document
   also updates, corrects three errata against, and obsoletes RFC 6931.

Working Group Summary

This document is AD sponsored.  There were no controversies related to it's review.

In addition to the additional algorithm identifiers, the associated registry collecting these identifiers was changed from expert review (per RFC6931) to specification required (in this -bis) since the described procedures to the expert was equivalent to specification required.

Document Quality

As to implementations, XML signatures, encryption, etc. is a mature technology.  This document refreshes the permitted algorithms.

Development and review of this document was done in partnership and coordination with W3C which leads the standardize of XML.  Review came from W3C and was requested on SAAG before the IETF LC.

The responsible AD reviewed the resolution of all published W3C URIs.  Most correctly resolve.  W3C has explicitly confirmed these will be comprehensively addressed after RFC publication.

Personnel

There was no document shepherd.
Roman Danyliw is the Responsible AD.

RFC Editor Note