Securely Available Credentials (SACRED) - Credential Server Framework
draft-ietf-sacred-framework-07

[Ballot discuss]
Discuss on draft-ietf-sacred-framework-06:

Section 5.1.4 says: "Although credential confidentiality is one of many factors required to support non-repudiation, ..."  This is misleading.  Authentication and integrity are prerequisite for non-repudiation.  Confidentiality of the credential is necessary to achieve authentication.  All of this has to do with the application context in whihc the credential is used, not the SACRED protocol.  Thus, it is not justification for "no requirements upon the SACRED protocol itself to support non-repudiation."  I agree that SACRED protocol does not need to support non-repudiation.  I do not accept this justification.

[Ballot comment]
Comments on draft-ietf-sacred-framework-06:

  In section 5.2.2, plaease make three changes:
    - Change "x.509" to "X.509"
    - Change "trusted SACRED roots" to "SACRED trust anchors"
    - Change "roots from other applications" to "trust anchors from other applications"

  Please change the title of section 5.2.4 to "Denial of Service."

Comments on draft-ietf-sacred-protocol-bss-08:

  Throughout the document, please change "privacy" to "confidentiality."

  In section 1, please change "(confidentiality, authentication, etc.)" to "(integrity, authentication, and confidentiality)."

[Ballot discuss]
Section 5.1.4 says: "Although credential confidentiality is one of many factors required to support non-repudiation, ..."  This is misleading.  Authentication and integrity are prerequisite for non-repudiation.  Confidentiality of the credential is necessary to achieve authentication.  All of this has to do with the application context in whihc the credential is used, not the SACRED protocol.  Thus, it is not justification for "no requirements upon the SACRED protocol itself to support non-repudiation."  I agree that SACRED protocol does not need to support non-repudiation.  I do not accept this justification.