One document matched: draft-ietf-trade-iotp-v1.0-dsig-01.txt
Differences from draft-ietf-trade-iotp-v1.0-dsig-00.txt
TRADE Working Group Kent Davidson
INTERNET-DRAFT Differential
Yoshiai Kawatsura
Hitachi
Expires: February 2000 August 1999
Digital Signatures for the Internet Open Trading Protocol (IOTP)
------- ---------- --- --- -------- ---- ------- -------- ------
Status of This Document
This draft, file name draft-ietf-trade-iotp-v1.0-dsig-01.txt, is a
part of the Internet Open Trading Protocol Specification version 1.0,
and is intended to become an Informational RFC. Distribution of this
document is unlimited. Comments should be sent to the TRADE working
group mailing list <ietf-trade@elistx.com>.
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months. Internet-Drafts may be updated, replaced, or obsoleted by
other documents at any time. It is not appropriate to use Internet-
Drafts as reference material or to cite them other than as a
``working draft'' or ``work in progress.''
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Abstract
A syntax and procedures are described for the computation and
verification of digital signatures for use within Version 1.0 of the
Internet Open Trading Protocol (IOTP).
K. Davidson, Y. Kawatsura [Page 1]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
Table of Contents
Status of This Document....................................1
Abstract...................................................1
Table of Contents..........................................2
1. Introduction............................................3
2. Objective and Requirements..............................3
3. Signature Basics........................................4
3.1 Signature Element......................................4
3.2 Digest Element.........................................4
3.3 Originator and Recipient Information Elements..........5
3.4 Algorithm Element......................................6
4. Detailed Signature Syntax...............................6
4.1 Uniform Resource Names.................................6
4.2 IOTPSignatures.........................................6
4.3 Signature Component....................................7
4.3.1 Signature............................................7
4.3.2 Manifest.............................................8
4.3.3 Algorithm............................................9
4.3.4 Digest...............................................9
4.3.5 Attribute...........................................10
4.3.6 OriginatorInfo......................................11
4.3.7 RecipientInfo.......................................11
4.3.8 Parameter...........................................12
4.4 Certificate Component.................................13
4.4.1 Certificate.........................................13
4.4.2 IssuerAndSerialNumber...............................14
4.5 Common Components.....................................14
4.5.1 Value...............................................14
4.5.2 Locator.............................................15
5. Supported Algorithms...................................15
5.1 Digest Algorithms.....................................16
5.1.1 DOM-HASH............................................16
5.1.2 SHA1................................................16
5.1.3 MD5.................................................17
5.2 Signature Algorithms..................................17
5.2.1 DSA.................................................17
5.2.2 HMAC................................................17
5.2.3 RSA.................................................17
6. Examples...............................................17
7. Signature DTD..........................................19
8. Security Considerations................................22
9. References.............................................22
9. Author's Addresses.....................................23
Expiration and File Name..................................23
K. Davidson, Y. Kawatsura [Page 2]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
1. Introduction
The Internet Open Trading Protocol (IOTP) provides a payment system
independent interoperable framework for Internet commerce as
documented in [RFC xxx, draft-ietf-trade-iotp-v1.0-protocol-*.txt].
All IOTP messages are XML documents. XML, the Extensible Markup
Language [XML], is a syntactical standard promulgated by the World
Wide Web Consortium. XML is intended primarily for structuring data
exchanged and served over the World Wide Web.
Although IOTP assumes that any payment system used with it provides
its own security, there are numerous cases where IOTP requires
authentication and integrity services for portions of the XML
messages it specifies.
2. Objective and Requirements
This document covers how digital signatures may be used with XML
documents to provide authentication and tamper-proof protocol
messages specifically for Version 1.0 of the IOTP protocol. The
reader should recognize that an effort towards general XML digital
signatures exists but is unlikely to produce its final result in time
for IOTP Version 1.0. Future versions of IOTP will probably just
adopt by reference the results of this general XML digital signature
effort.
The objective of this document is to propose syntax and procedures
for the computation and verification of digital signatures applicable
to Version 1.0 IOTP protocol messages, providing for:
-- Authentication of IOTP transactions
-- Provide a means by which an IOTP message may be made "tamper-
proof", or detection of tampering is made evident
-- Describe a set of available digest and signature algorithms at
least one of which is mandatory to implement for interoperability
-- Easily integrate within the IOTP 1.0 Specification
-- Provide lightweight signatures with minimal redundancy
-- Allow a signed portions of IOTP message to be "forwarded" to
another trading roles with different signature algorithms than the
original recipient
K. Davidson, Y. Kawatsura [Page 3]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
3. Signature Basics
3.1 Signature Element
This specification consists primarily of the definition of an XML
element known as the Signature element. This element consists of two
sub-elements. The first one is a set of authenticated attributes,
known as the signature Manifest, which comprises such things as a
unique reference to the resources being authenticated and an
indication of the keying material and algorithms being used. The
second sub-element consists of the digital signature value.
<Signature>
<Manifest>
(resource information block)
(originator information block)
(recipient information block)
(other attributes)
(signature algorithms information block)
</Manifest>
<Value encoding 'encoding scheme'>
(encoded signature value)
<Value>
</Signature>
The digital signature is not computed directly from the pieces of
information to be authenticated. Instead, the digital signature is
computed from a set of authenticated attributes (the Manifest), which
include references to, and a digests of, those pieces of information.
The authentication is therefore "indirect".
3.2 Digest Element
The Digest element consists of a unique and unambiguous reference to
the XML resources being authenticated. It is constructed of a locator
and the digest value data itself. The Digest algorithm is referred to
indirectly via a DigestAlgorithmRef, so that Digest algorithms may be
shared by multiple resources.
<Digest DigestAlgorithmRef 'D.1'>
<Locator href 'resource locator'/>
<Value>
(Digest value)
</Value>
</Digest>
K. Davidson, Y. Kawatsura [Page 4]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
The resource locator is implemented as a simple XML Link [XLink].
This not only provides a unique addressing scheme for internal and
external resources, but also facilitates authentication of composite
documents.
3.3 Originator and Recipient Information Elements
The purpose of the Originator and Recipient information elements is
providing identification and keying material for these respective
parties.
<OriginatorInfo>
(identification information block)
(keying material information block)
</OriginatorInfo>
<RecipientInfo>
(identification information block)
(keying material information block)
</RecipientInfo>
The actual content of these two elements depends on the
authentication scheme being used and the existence or non-existence
of a prior relationship between the parties. In some circumstances,
it may be quite difficult to distinguish between identification and
keying material information. A unique reference to a digital
certificate provides for both. This may also stand true for an
account number when a prior relationship exists between the parties.
The Originator information element is mandatory. Depending on the
existence or non-existence of a prior relationship with the
recipient, this block either refers to a public credential such as a
digital certificate or displays a unique identifier known by the
recipient.
The Recipient information element may be used when a document
contains multiple signature information blocks, each being intended
for a particular recipient. A unique reference in the Recipient
information block helps the recipients identify their respective
Signature information block.
The Recipient information element may also be used when determination
of the authentication key consists of a combination of keying
material provided by both parties. This would be the case, for
example, when establishing a key by means of Diffie Hellman
[Schneier] Key Exchange algorithm.
K. Davidson, Y. Kawatsura [Page 5]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
3.4 Algorithm Element
The Algorithm element is a generalised place to place any type of
algorithm used within the signed IOTP message. The Algorithm may be a
Signature algorithm or a Digest algorithm. Each algorithm contains
parameters specific to the algorithm used.
<Algorithm type 'digest'" id='12'>
(algorithm information block)
</Algorithm>
Algorithms are required to contain an ID which allows for indirect
reference to them from other places in the XML signature.
4. Detailed Signature Syntax
4.1 Uniform Resource Names
To prevent potential name conflicts in the definition of the numerous
type qualifiers considered herein, this specification uses Uniform
Resource Names [RFC 2141].
4.2 IOTPSignatures
The IOTPSignatures element is the top-level element in an IOTP
signature block. It consists of a collection of Signature elements,
and an optional set of Certificates.
<!ELEMENT IOTPSignatures (Signature+, Certificate*) >
<!ATTLIST IOTPSignatures
id ID #IMPLIED >
Content Description
Signature: A collection of Signature elements.
Certificate: Zero or more certificates used for signing
Attributes Description
ID: Element identifier that may be used to referencing the entire
Signature element from a Resource element when implementing
endorsement.
K. Davidson, Y. Kawatsura [Page 6]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
4.3 Signature Component
4.3.1 Signature
The Signature element constitutes the majority of this specification.
It is comprised of two sub-elements. The first one is a set of
attributes, known as the Manifest, which actually constitutes the
authenticated part of the document. The second sub-element consists
of the signature value or values.
The Value element contained within the Signature element is the
encoded form of the signature of the Manifest element, and thus
provides the verification of the Manifest.
The process for generating the signed value is a multi-step process,
involving a canonicalization algorithm, a digest algorithm, and a
signature algorithm.
First, the Manifest is canonicalized with an algorithm specified
within the Algorithm element of the Manifest. The canonicalized form
removes any inconsistencies in white space introduced by XML parsing
engines.
This canonicalized form is then converted into a digest form which
uniquely identifies the canoicalized document. Any slight
modification in the original document will result in a very different
digest value.
Finally, the digest is then signed using a public-key algorithm which
digitally stamps the digest with the certificate of the signer. The
final signed digest is the value which is stored within the
Signature's Value element.
<!ELEMENT Signature (Manifest, Value+) >
<!ATTLIST Signature
ID ID #IMPLIED >
Content Description
Manifest: A set of attributes that actually constitutes the
authenticated part of the document.
Value: One or more encodings of signature values. Multiple values
allow for a multiple algorithms to be supported within a single
signature block.
Attributes Description
K. Davidson, Y. Kawatsura [Page 7]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
ID: Element identifier that may be used to referencing the Signature
element from a Resource element when implementing endorsement.
4.3.2 Manifest
The Manifest element consists of a collection of attributes that
specify such things as as references to the resources being
authenticated and an indication of the keying material and algorithms
to be used.
<!ELEMENT Manifest
( Algorithm+,
Digest+,
Attribute*,
OriginatorInfo,
RecipientInfo+,
)
<!ATTLIST Manifest
LocatorHRefBase CDATA #IMPLIED
>
Content Description
Algorithm: A list of algorithms used for signing, digest computation,
and canonicalization.
Digest: A list of digests of resources to be authentication and
signed.
Attribute: Optional element that consists of a collection of
complementary attributes to be authenticated.
OriginatorInfo: Element that provides identification and keying
material information related to the originator.
RecipientInfo: Optional element that provides identification and
keying material information related to the recipient.
Attributes Description
LocatorHrefBase: The LocatorHrefBase provides a similar construct to
the HTML HREFBASE attribute and implicitly sets all relative URL
references within the Manifest to be relative to the HrefBase. For
example, the IOTP Manifest may contain:
<Manifest
LocatorHrefBase='iotp:globally-unique-tid#'>
K. Davidson, Y. Kawatsura [Page 8]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
And subsequent Locators may be:
<Locator href='C.9'>
An implementation should concatenate the two locator references to
create the entire URL.
4.3.3 Algorithm
This specification uses an Algorithm data type which indicates many
different types of algoirithms. The Algorithm element allows for
specification of sub-algorithms as parameters of the primary
algorithm. This is performed via a parameter within the algorithm
that provides a reference to another Algorithm. An example of this is
shown in the Parameter section.
<!ELEMENT Algorithm (Parameter*) >
<!ATTLIST Algorithm
id ID #REQUIRED
type (digest|signature) #IMPLIED
name NMTOKEN #REQUIRED >
Content Description
Parameter: The contents of an Algorithm element consists of an
optional collection of Parameter elements which are specified on a
per algorithm basis.
Attributes Description
id: The ID of the algorithm is used by the Digest and RecipientInfo
to refer to the signing or digest algorithm used.
type: The type of algorithm, either a digest or signature. This is
implied by the element to which the algorithm is referred. That is,
if the DigestAlgorithmRef refers to an algorithm, it is implicit by
reference that the targetted algorithm is a digest.
name: The type of the algorithm expressed as a Uniform Resource
Name.
4.3.4 Digest
The Digest element consists of the fingerprint of a given resource.
This element is constructed of two sub-elements. This first one
indicates the algorithm to be used for computation of the
K. Davidson, Y. Kawatsura [Page 9]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
fingerprint. The second element consists of the fingerprint value.
<!ELEMENT Digest (Locator, Value) >
<!ATTLIST Digest
DigestAlgorithmRef IDREF #REQUIRED
>
Content Description
Locator: Contains a "HREF" or URL locator for the resource to be
fingerprinted. References to IOTP messages.
Value: Encoding of the fingerprint value.
Attributes Description
DigestAlgorithmRef: ID Reference of algorithm used for computation of
the digest.
4.3.5 Attribute
The Attribute element consists of a complementary piece of
information, which shall be included in the authenticated part of the
document. This element has been defined primarily for enabling some
level of customization in the signature element. This is the area
where a specific IOTP implementation may include custom attributes
which must be authenticated directly. An Attribute element consists
of a value, a type, and a criticality.
At this time, no IOTP specific attributes are specified.
<!ELEMENT Attribute ( ANY ) >
<!ATTLIST Attribute
type NMTOKEN #REQUIRED
critical ( true | false ) #REQUIRED
>
Content Description
ANY: The actual value of an attribute depends solely upon its type.
Attributes Description
type: Type of the attribute.
critical: Boolean value that indicates if the attribute is critical
(true) or not (false). A recipient shall reject a signature that
contains a critical attribute that he does not recognise. However, an
K. Davidson, Y. Kawatsura [Page 10]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
unrecognised non-critical attribute may be ignored.
4.3.6 OriginatorInfo
The OriginatorInfo element is used for providing identification and
keying material information for the originator.
<!ELEMENT OriginatorInfo ANY >
<!ATTLIST OriginatorInfo
OriginatorRef NMTOKEN #IMPLIED
>
Content Description
ANY: Identification and keying material information may consist of
ANY construct. Such a definition allows the adoption of
application-specific schemes.
Attributes Description
OriginatorRef: A reference to the IOTP Org ID of the originating
signer.
4.3.7 RecipientInfo
The RecipientInfo element is used for providing identification and
keying material information for the recipient. This element is used
either for enabling recognition of a Signature element by a given
recipient or when determination of the authentication key consists of
the combination of keying material provided by both the recipient and
the originator.
The RecipientInfo attributes provide a centralized location where
signatures, algorithms, and certificates intended for a particular
recipient are specified.
The signature certificate reference ID MUST point to a certificate
object.
K. Davidson, Y. Kawatsura [Page 11]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
<!ELEMENT RecipientInfo ANY >
<!ATTLIST RecipientInfo
SignatureAlgorithmRef IDREF #REQUIRED
SignatureValueRef IDREF #IMPLIED
SignatureCertRef IDREF #IMPLIED
RecipientRefs NMTOKENS #IMPLIED
>
Content Description
ANY: Identification and keying material information may consist of
ANY construct.
Attributes Description
SignatureAlgorithmRef: A reference to the signature algorithm used to
sign the SignatureValueRef intended for this recipient. The signature
algorithm reference ID MUST point to a signature algorithm within the
Manifest.
SignatureValueRef: A reference to the signature value for this
recipient. The signature value reference ID MUST point to a value
structure directly included within a Manifest. This reference can be
omitted if the application can specify the digest value.
SignatureCertRef: A reference to the certificate used to sign the
Value pointed to by the SignatureValueRef. This reference can be
omitted if the application can identify the certificate.
RecipientRefs: A list of references to the IOTP Org ID of the
recipients this signature is intended for.
4.3.8 Parameter
A Parameter element provides the value of a particular algorithm
parameter, whose name and format have been specified for the
algorithm considered.
<!ELEMENT Parameter ANY >
<!ATTLIST Parameter
type CDATA #REQUIRED
>
For IOTP 1.0, the following parameter type is standardized:
"AlgorithmRef".
An AlgorithmRef contains an ID of a "sub-Algorithm" used when
computing a sequence of algorithms. For example, a signature
K. Davidson, Y. Kawatsura [Page 12]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
algorithm actually signs a digest algorithm. To specify a chain of
algorithms used to compute a signature, AlgorithmRef parameter types
are used in the following manner:
<Algorithm ID A1 type 'digest' name 'urn:ibm:dom-hash'>
<Parameter type 'AlgorithmRef'>A2</Parameter>
</Algorithm>
<Algorithm ID A2 type 'digest' name 'urn:fips:sha1'>
</Algorithm>
<Algorithm ID A3 type 'signature' name 'urn:ibm:hmac'>
<Parameter type 'AlgorithmRef'>A1</Parameter>
</Algorithm>
Content Description
ANY: The contents of a Parameter element consists of ANY valid
construct, which is specified on a per algorithm per parameter basis.
Attributes Description
type: The type of the parameter expressed as a free form string,
whose value is specified on a per algorithm basis.
4.4 Certificate Component
4.4.1 Certificate
The Certificate element may be used for either providing the value of
a digital certificate or specifying a location from where it may be
retrieved.
<!ELEMENT Certificate
( IssuerAndSerialNumber,
( Value | Locator ) )
>
<!ATTLIST Certificate
id ID #IMPLIED
type NMTOKEN #REQUIRED >
Content Description
IssuerAndSerialNumber: Unique identifier of this certificate. This
element has been made mandatory is order to prevent unnecessary
decoding during validation of a certificate chain. This feature also
helps certificates caching, especially when the value is not directly
provided.
K. Davidson, Y. Kawatsura [Page 13]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
Value: Encoding of the certificate value. The actual value to be
encoded depends upon the type of the certificate.
Locator: XML link element that could be used for retrieving a copy of
the digital certificate. The actual value being returned by means of
this locator depends upon the security protocol being used.
Attributes Description
type: Type of the digital certificate. This attribute is specified
as a Universal Resource Name, as indicated in the "Supported
Algorithms" section.
4.4.2 IssuerAndSerialNumber
The IssuerAndSerialNumber element identifies a certificate, and
thereby an entity and a public key, by the name of the certificate
issuer and an issuer-specific certificate identification.
<!ELEMENT IssuerAndSerialNumber EMPTY >
<!ATTLIST IssuerAndSerialNumber
issuer CDATA #REQUIRED
number CDATA #REQUIRED >
Attributes Description
issuer: Name of the issuing certification authority.
number: Issuer-specific certificate identification.
4.5 Common Components
4.5.1 Value
A value contains the "raw" data of a signature or digest algorithm,
usually in a base-64 encoded form. See [RFC 2045] for algorithm used
to base-64 encode data.
<!ELEMENT Value ( #PCDATA ) >
<!ATTLIST Value
id ID #IMPLIED
encoding (base64|none) #IMPLIED 'base64'
K. Davidson, Y. Kawatsura [Page 14]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
>
Content Description
PCDATA: Content value after adequate encoding.
Attributes Description
encoding: This attribute specifies the decoding scheme to be
employed for recovering the original byte stream from the content of
the element. This document recognises the following two schemes:
none: the content has not been subject to any particular encoding.
This does not preclude however the use of native XML encoding such as
CDATA section or XML escaping.
base64: The content has been encoded by means of the base64 encoding
scheme.
4.5.2 Locator
The Locator element consists of simple XML link [XLink]. This
element allows unambiguous reference to a resource or fragment of a
resource.
<!ELEMENT Locator EMPTY>
<!ATTLIST Locator
xml:link CDATA #FIXED 'simple'
href CDATA #REQUIRED >
Attributes Description
xml:link: Required XML link attribute that specifies the nature of
the link (simple in this case).
href: Locator value that may contains either a URI [RFC 2396], a
fragment identifier, or both.
5. Supported Algorithms
The IOTP specification 1.0 requires the implementation of the DOM-
HASH, SHA1, MD5, DSA, and HMAC algorithms to provide a compliant
implementation of IOTP 1.0. Implementation of RSA is also
recommended.
K. Davidson, Y. Kawatsura [Page 15]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
5.1 Digest Algorithms
This specification contemplates two types of digest algorithms, both
of which provide a digest string as a result:
Surface string digest algorithms
These algorithms do not have any particular knowledge about the
content being digested and operate on the raw content value. Changes
in the surface string of a given content affect directly the value of
the digest being produced.
Canonical digest algorithms
These algorithms have been tailored for a particular content type and
produce a digest value that depends upon the core semantics of such
content. Changes limited to the surface string of a given content do
not affect the value of the digest being produced.
5.1.1 DOM-HASH
XML canonical digest algorithm proposed by IBM Tokyo Research
Laboratory. This algorithm operates on the DOM representation of the
document and provides an unambiguous means for recursive computation
of the hash value of the nodes that constitute the DOM tree.
The DOM-HASH algorithm requires a single parameter, which shall
consist of a surface string digest algorithm such as SHA1.
The DOM-HASH URN used for this specification is "urn:ibm:dom-hash".
Example
<Algorithm name='urn:ibm:dom-hash' type='digest'>
</Algorithm>
5.1.2 SHA1
Surface string digest algorithm designed by the US government for use
with the Digital Signature Standard. This algorithm produces a 160-
bit hash value.
This algorithm does not require any parameter.
The SHA1 URN used for this specification is "urn:fips:sha1".
K. Davidson, Y. Kawatsura [Page 16]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
5.1.3 MD5
The MD5 Algorithm was invented by RSA Data Securities and is similar
to its predecessors, MD2 and MD4, but faster and simpler than MD2
while stronger than MD4. [RFC 1321]
The MD5 Algorithm takes no parameters.
The MD5 URN used for this specification is "urn:rsa:md5".
5.2 Signature Algorithms
This specification uses the terminology of 'digital signature' for
qualifying indifferently digital signature and message authentication
codes. Thus, the signature algorithms contemplated herein include
public key digital signature algorithms such as DSA and message
authentication codes such as HMAC [RFC 2104].
5.2.1 DSA
The DSA URN used in this specification is "urn:fips:dsa".
5.2.2 HMAC
See [RFC 2104]
The HMAC URN used in this specification is is "urn:ibm:hmac".
5.2.3 RSA
The RSA URN used in this specification is "urn:rsa:rsa".
6. Examples
The following is an example signed IOTP message:
<IotpMessage>
<TransRefBlk ID='M.1'>
<TransId
K. Davidson, Y. Kawatsura [Page 17]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
ID='M.2'
version='1.0'
IOtpTransID='19990809215923@www.iotp.org'
IOtpTransType='BaselinePurchase'
TransTimeStamp='1999-08-09T12:58:40.000Z+9'>
</TransId>
<MsgId xml:lang='en' SoftwareID='Iotp wallet version 1.0'>
</MsgId>
</TransRefBlk>
<IOTPSignatures>
<Signature>
<Manifest LocatorHrefBase='iotp:'>
<Algorithm name='urn:sha1' type='digest' id='P.3'>
</Algorithm>
<Algorithm name='urn:rsa' type='signature' ID='P.4'>
<Parameter type AlgorithmRef>P.5</Parameter>
</Algorithm>
<Algorithm name='urn:dom-hash' type='digest' id='P.5'>
<Parameter type='AlgorithmRef'>P.3</Parameter>
</Algorithm>
<Digest DigestAlgorithmRef='P.6'>
<Locator href='P.1'/>
<Value>
xsqsfasDys2h44u4ehJDe54he5j4dJYTJ
</Value>
</Digest>
<OriginatorInfo
<IssuerAndSerialNumber
issuer='o=Iotp Ltd., c=US'
number='12345678987654'/>
</OriginatorInfo>
<RecipientInfo
SignatureAlgorithmRef='P.4'
</RecipientInfo>
</Manifest>
<Value>
9dj28fjakA9sked0Ks01k2d7a0kgmf9dk19lf63kkDSs0
</Value>
</Signature>
<Certificate type='urn:X500:X509v3'>
<IssuerAndSerialNumber
issuer='o=GlobeSet Inc., c=US'
number='123456789102356'/>
<Value>
xsqsfasDys2h44u4ehJDe54he5j4dJYTJ=
</Value>
</Certificate>
</IOTPSignatures>
<PayExchBlk ID='P.1'>
<PaySchemeData
K. Davidson, Y. Kawatsura [Page 18]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
ID='P.2'
PaymentRef='M.5'
ContentSoftwareId='abcdefg'>
<PackagedContent Name='FirstPiece'>
snroasdfnas934k
</PackagedContent>
</PaySchemeData>
</PayExchBlk>
</IotpMessage>
7. Signature DTD
<!--
******************************************************
* IOTP SIGNATURES BLOCK DEFINITION *
******************************************************
-->
<!ELEMENT IOTPSignatures (Signature+ ,Certificate*) >
<!ATTLIST IOTPSignatures
ID ID #IMPLIED
>
<!--
******************************************************
* IOTP SIGNATURE COMPONENT DEFINITION *
******************************************************
-->
<!ELEMENT Signature (Manifest, Value+) >
<!ATTLIST Signature
ID ID #IMPLIED
>
<!ELEMENT Manifest
( Algorithm+,
Digest+,
Attribute*,
OriginatorInfo,
RecipientInfo+
)
>
<!ATTLIST Manifest
LocatorHRefBase CDATA #IMPLIED
>
K. Davidson, Y. Kawatsura [Page 19]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
<!ELEMENT Algorithm (Parameter*) >
<!ATTLIST Algorithm
id ID #REQUIRED
type (digest|signature) #IMPLIED
name NMTOKEN #REQUIRED
>
<!ELEMENT Digest (Locator, Value) >
<!ATTLIST Digest
DigestAlgorithmRef IDREF #REQUIRED
>
<!ELEMENT Attribute ( ANY ) >
<!ATTLIST Attribute
type NMTOKEN #REQUIRED
critical ( true | false ) #REQUIRED
>
<!ELEMENT OriginatorInfo ANY >
<!ATTLIST OriginatorInfo
OriginatorRef NMTOKEN #IMPLIED
>
<!ELEMENT RecipientInfo ANY >
<!ATTLIST RecipientInfo
SignatureAlgorithmRef IDREF #REQUIRED
SignatureValueRef IDREF #IMPLIED
SignatureCertRef IDREF #IMPLIED
RecipientRefs NMTOKENS #IMPLIED
>
<!ELEMENT Parameter ANY >
<!ATTLIST Parameter
type CDATA #REQUIRED
>
<!--
******************************************************
* IOTP CERTIFICATE COMPONENT DEFINITION *
******************************************************
-->
<!ELEMENT Certificate
( IssuerAndSerialNumber, ( Value | Locator ) )
>
<!ATTLIST Certificate
ID ID #IMPLIED
type NMTOKEN #REQUIRED
>
K. Davidson, Y. Kawatsura [Page 20]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
<!ELEMENT IssuerAndSerialNumber EMPTY >
<!ATTLIST IssuerAndSerialNumber
issuer CDATA #REQUIRED
number CDATA #REQUIRED
>
<!--
******************************************************
* IOTP SHARED COMPONENT DEFINITION *
******************************************************
-->
<!ELEMENT Value ( #PCDATA ) >
<!ATTLIST Value
id ID #IMPLIED
encoding (base64|none) #IMPLIED 'base64'
>
<!ELEMENT Locator EMPTY>
<!ATTLIST Locator
xml:link CDATA #FIXED 'simple'
href CDATA #REQUIRED
>
K. Davidson, Y. Kawatsura [Page 21]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
8. Security Considerations
This entire document concerns the IOTP v1 protocol signature element
which is used for authentication. See the Security Considerations
section of [RFC xxxx] "Interenet Open Trading Protocol - IOTP,
Version 1.0".
9. References
[RFC 1321] - R. Rivest, "The MD5 Message-Digest Algorithm", April
1992.
[RFC 2045]- N. Freed & N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message Bodies",
November 1996.
[RFC 2046] - N. Freed & N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part Two: Media Types", November 1996.
[RFC 2104] - H. Krawczyk, M. Bellare, R. Canetti, "HMAC: Keyed-
Hashing for Message Authentication", February 1997.
[RFC 2141] - R. Moats, "URN Syntax", May 1997.
[RFC 2396] - T. Berners-Lee, R. Fielding, L. Masinter, "Uniform
Resource Identifiers (URI): Generic Syntax", August 1998.
[RFC xxxx] - D. Burdett, "Interenet Open Trading Protocol - IOTP,
Version 1.0", August 1999. (currently draft-ietf-trade-iotp-v1.0-
protcool-*.txt)
[Schneier] - Bruce Schneier, "Applied Cryptography: Protocols,
Algorithms, and Source Code in C", 1996, John Wiley and Sons
[XLink] - Eve Maler, Steve DeRose, "XML Linking Language (XLink)",
<http://www.w3.org/TR/1998/WD-xlink-19980303>
[XML] - Tim Bray, Jean Paoli, C. M. Sperber-McQueen, "Extensible
Markup Language (XML) 1.0", <http://www.w3.org/TR/1998/REC-xml-
19980210>
K. Davidson, Y. Kawatsura [Page 22]
INTERNET-DRAFT Digital Signatures for IOTP August 1999
9. Author's Addresses
This document is based on work originally done on general XML digital
signatures by Richard Brown at GlobeSet, Inc. <rdbrown@GlobeSet.com>
but has been narrowed and changed.
The authors of this document are:
Kent M. Davidson
Differential, Inc.
440 Clyde Ave.
Mountain View, CA 94043 USA
email: kent@differential.com
Yoshiaki Kawatsura
Hitachi, Ltd.
890 Kashimada Saiwai Kawasaki,
Kanagawa 2118567 Japan
email: kawatura@bisd.hitachi.co.jp
Contributors to the design of the IOTP DTD include, in alphabetic
order:
David Burdett, Mondex
Andrew Drapp, Hitachi
Donald Eastlake 3rd, IBM
Expiration and File Name
This draft expires February 2000.
Its file name is draft-ietf-trade-iotp-v1.0-dsig-01.txt.
K. Davidson, Y. Kawatsura [Page 23]
| PAFTECH AB 2003-2026 | 2026-04-24 03:27:51 |