Draft: draft-ietf-lamps-documentsigning-eku

Commentary: This PR contains corrections to more accurate expression . This PR does not contains modification related to backwards compatibility and interoperability . 
 Thanks Sean I approved all above modifications .
RFC5280 specifies several extended key usages for X.509 certificates.
This document defines a general purpose document signing extended key
usage for X.509 public key certificates which restricts the usage of
the certificates for document signing.
RFC5280 specifies several extended key usages for X.509 certificates.
In addition, several extended key usage had been addedRFC7299 as
public OID under the IANA repository.  While usage of any extended
key usage is bad practice for publicly trusted certificates, there
are no public and general extended key usage explicitly assigned for
Document Signing certificates.  The current practice is to use id-kp-
emailProtection, id-kp-codeSigning or vendor defined Object ID for
general document signing purposes.
RFC5280 specifies several extended key usages for X.509 certificates.
This document defines a general purpose document signing extended key
usage for X.509 public key certificates which specifies the usage of
the certificates for document signing.
RFC5280 specifies several extended key purpose identifiers for X.509
certificates.  In addition, several extended key purpose identifiers
were addedRFC7299 as public OIDs under the IANA PKIX Extended key
purpose identifiers arc.  While usage of the any extended key usage
value is bad practice for publicly trusted certificates, there is no
public and general extended key purpose identifier explicitly
assigned for Document Signing certificates.  The current practice is
to use id-kp-emailProtection, id-kp-codeSigning or vendor defined
Object IDs for general document signing purposes.
This document defines a general Document Signing extended key usage.
This document defines a general Document Signing extended key purpose
identifier.
This specification defines the KeyPurposeId id-kp-documentSigning.
Inclusion of this KeyPurposeId in a certificate indicates that the
use of any Subject names in the certificate is restricted to use by a
document signing.
Term of "Document Sign" in this document is digitally sign contents
that are consumed by humans.  To be more precise, contents are
intended to be shown to human with printable or displayable form by
means of services or software, rather than processed by machines.
This specification defines the KeyPurposeId id-kp-documentSigning.
Inclusion of this KeyPurposeId in a certificate indicates that the
use of the certified public key is allowed to be used for verifying
the signature on a document.
Term of "Document Sign" in this document is digitally signes contents
that are consumed by humans.  To be more precise, contents are
intended to be shown to human with printable or displayable form by
means of services or software, rather than processed by machines.
This specification defines the KeyPurposeId id-kp-documentSigning.
Inclusion of this KeyPurposeId in a certificate indicates that the
use of any Subject names in the certificate is restricted to use by a
document signing service or a software (along with any usages allowed
by other EKU values).
This specification defines the KeyPurposeId id-kp-documentSigning.
Inclusion of this KeyPurposeId in a certificate indicates that the
Subject named in the certificate signed the document content, and the
associated keys can be used by a document signing service or a
software for authentication, message integrity, and non-repudiation
of origin (using digital signatures, along with any usages allowed by
other EKU values).
The procedure is intended to permit or prohibit presence of a certain
EKU or complete absence of EKUs.  It is outside the scope of this
document, but the relying party can permit or prohibit conbinations
of EKU.  A consideration on prohibiting combination of EKUs is
described in the security consideration section of this document.
The procedure is intended to permit or prohibit presence of a certain
EKU or complete absence of EKUs.  It is outside the scope of this
document, but the relying party can permit or prohibit combinations
of EKU.  A consideration on prohibiting combinations of EKUs is
described in the security consideration section of this document.
When a single software has capability to process various data
formats, the software may choose to make the excluded and permitted
decisions separately in accordance with the format it is handling
(e.g. text, pdf, etc).
When a single software has the capability to process various data
formats, the software may choose to make the excluded and permitted
decisions separately in accordance with the format it is handling
(e.g. text, pdf, etc).
The usage of id-kp-documentSigning EKU intends to prevent id-kp-
emailProtection from being used for none-email purposes and id-kp-
codeSigning used to sign objects other than binary codes.  This EKU
does not introduce new security risks but instead reduces existing
security risks by providing means to separate other EKUs used for
communication protocols namely, TLS or S/MIME etc. in order to
minimize the risk of cross protocol attacks.
To reduce the risk of specific cross protocol attacks, the relying
party or relying party software may additionaly prohibit use of
specific combination of EKUs.
While a specific protocol or signing scheme may choose to come up
with their own EKU, some may not have significant motive or resource
to set up and manage thier own EKU.  This general document signing
EKU may be used as a stop gap for those that intend to set up their
own EKU or those who do not intend to set up an EKU but still would
like to distinguish from other usage.
The usage of id-kp-documentSigning EKU is to provide an alternative
to id-kp-emailProtection being used for non-email purposes and id-kp-
codeSigning being used to sign objects other than binary code.  This
EKU does not introduce new security risks but instead reduces
existing security risks by providing means to separate other EKUs
used for communication protocols namely, TLS or S/MIME etc. in order
to minimize the risk of cross protocol attacks.
To reduce the risk of specific cross protocol attacks, the relying
party or relying party software may additionally prohibit use of
specific combination of EKUs.
While a specific protocol or signing scheme may choose to come up
with their own EKU, some may not have significant motive or resources
to set up and manage their own EKU.  This general document signing
EKU may be used as a stop gap for those that intend to set up their
own EKU or those who do not intend to set up an EKU but still would
like to distinguish document signing from other usages.