RFC 2253 -> RFC 4514

• From: Thomas Roessler <tlr@w3.org>
• Date: Tue, 26 Jun 2007 08:24:16 -0700
• To: public-xmlsec-maintwg@w3.org
• Message-ID: <20070626152416.GH3529@raktajino.does-not-exist.org>

Per ACTION-59, I'm to summarize the rationale for changing the
reference from RFC 2253 to RFC 4514.

- RFC 4514 supersedes RFC 2253.
- RFC 4514 fixes the obvious bug in the RFC 2253 grammar.
- RFC 4514 gives implementations slightly more leeway in how they
  encode a string, making the augmented rules consistent with the
  normative text of the spec.
- RFC 4514 also clarifies the conformance interactions between
  sections 2.4 and 3.
  
On the generating side, RFC 4514 may slightly relax some conformance
conditions, to the point that the additional processing actually
exercises degrees of freedom as opposed to overriding a choice makes.

On the consuming side, RFC 4514 ensures consistency, but doesn't
seem to lead to any other conformance-affecting changees.

-- 
Thomas Roessler, W3C  <tlr@w3.org>

Received on Tuesday, 26 June 2007 15:24:22 UTC