…on uses algorithm identifiers in the namespace that were originally coined in [ RFC6931 ]. RFC 6931 associates these identifiers with specific algorithms. Implementations of this specification MUST be fully interoperable with the algorithms specified in RFC6931 ], but MAY compute…
…on uses algorithm identifiers in the namespace that were originally coined in [ RFC6931 ]. RFC 6931 associates these identifiers with specific algorithms. Implementations of this specification MUST be fully interoperable with the algorithms specified in RFC6931 ], but MAY compute…
…how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6931 . Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisio…
…oc" column augmented with a reference to this RFC (for example, "2.6.4" means "[RFC6931], Section 2.6.4"). New entries, including new Types, will be added based on Expert Review [RFC5226]. Criterion for inclusion are (1) documentation sufficient for interoperability of the algori…
…006/12/xmlc14n11# [CANON11] Notes: As explained in Appendix B of draft-eastlake-rfc6931bis-xmlsec-uris: [RFC6931] included two bad URIs as shown below. "{Bad}" in the indexes (Sections 4.1 and 4.2) indicates such a bad value. Implementations SHOULD only generate the correct URI b…
…006/12/xmlc14n11# [CANON11] Notes: As explained in Appendix B of draft-eastlake-rfc6931bis-xmlsec-uris: [RFC6931] included two bad URIs as shown below. "{Bad}" in the indexes (Sections 4.1 and 4.2) indicates such a bad value. Implementations SHOULD only generate the correct URI b…