XML Key Management Specification (XKMS) Issues List

XKMS WG Chair(s):

Stephen Farrell < stephen.farrell@baltimore.ie >

Shivaram Mysore < shivaram.mysore@sun.com >

XKMS Editor(s):

Phillip Hallam-Baker < pbaker@verisign.com >

Merlin Hughes < merlin@baltimore.ie >

Issues List Maintainer(s):

Phillip Hallam-Baker < pbaker@verisign.com  >

Mike Just < mike.just@entrust.com >

This page enumerates outstanding issues on the XML Key Management Specification. The source of an issue need not be its first instance; it also might reference a cogent description or WG poll. Also, this document may not capture editorial tweaks and errors that were easily and quickly remedied.

This page will contain two tables.  Outstanding issues are recorded in the first table. They are typed as either Editorial (including typos and small clarifications), Clarification (where significant explanatory text is required) or Major.  In some cases, a volunteer has been identified, but in case not, then implementation of the proposed resolution is left to the specification editor(s).  Once an issue has been resolved (meaning that a resolution satisfactory to the group is agreed and has been included in the latest version of the specification), the issue is moved to the `Resolved Issues' table.  The issue index number is maintained to allow for consistent referencing.

New issues, and the resolution of issues should be reported to the XKMS mailing list. Before doing so, ensure that the issue is not already covered by an issue either in the "Outstanding Issues" table (in which case, a new issue need not be entered) or in the "Resolved Issues" table (in which case a new outstanding issue should be created, as opposed to moved from resolved to outstanding).  In addition, for newly discovered issues, the discoverer should identify an related issues that may already be cited in either table below.

Outstanding Issues

Last Minute Issues

Examples Issues

Additional Issues Just added, mostly clarification requests at specified paragraph