rfc2802.txt

中、英文RFC文档大全打包下载完全版 .

         </Certificate>
      </IotpSignatures>
      <PayExchBlk ID='P.1'>
          <PaySchemeData
              ID='P.2'
              PaymentRef='M.5'
              ContentSoftwareId='abcdefg'>
                  <PackagedContent Name='FirstPiece'>
                       snroasdfnas934k



Davidson & Kawatsura         Informational                     [Page 22]

RFC 2802              Digital Signatures for IOTP             April 2000


                  </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
   >

   <!ELEMENT Algorithm (Parameter*) >
   <!ATTLIST Algorithm
           ID                     ID                #REQUIRED
           type            (digest|signature)      #IMPLIED
           name                  NMTOKEN           #REQUIRED
   >



Davidson & Kawatsura         Informational                     [Page 23]

RFC 2802              Digital Signatures for IOTP             April 2000


   <!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 KeyIdentifier EMPTY>
   <!ATTLIST KeyIdentifier
           value                    CDATA           #REQUIRED
   >

   <!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
   >



Davidson & Kawatsura         Informational                     [Page 24]

RFC 2802              Digital Signatures for IOTP             April 2000


   <!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      'base64'
   >

   <!ELEMENT Locator EMPTY>
   <!ATTLIST Locator
           xml:link        CDATA         #FIXED        'simple'
           href            CDATA         #REQUIRED
   >

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 2801] "Internet Open Trading Protocol - IOTP, Version
   1.0".






















Davidson & Kawatsura         Informational                     [Page 25]

RFC 2802              Digital Signatures for IOTP             April 2000


References

   [DSA]        Federal Information Processing Standards Publication
                FIPS PUB 186, "Digital Signature Standard(DSS)", 1994,
                <http://csrc.nist.gov>

   [IEEE P1363] IEEE P1363, "Standard Specifications for Public-Key
                Cryptography", Work in Progress, 1997,
                <http://stdsbbs.ieee.org/>

   [PV]         Preneel, B. and P. van Oorschot, "Building fast MACs
                from hash functions", Advances in Cryptology --
                CRYPTO'95 Proceedings, Lecture Notes in Computer
                Science, Springer-Verlag Vol.963, 1995, pp. 1-14.

   [RFC 1321]   Rivest, R., "The MD5 Message-Digest Algorithm", RFC
                1321, April 1992.

   [RFC 2045]   Freed, N. and N. Borenstein, "Multipurpose Internet Mail
                Extensions (MIME) Part One: Format of Internet Message
                Bodies", RFC 2045, November 1996.

   [RFC 2046]   Freed N. and N. Borenstein, "Multipurpose Internet Mail
                Extensions (MIME) Part Two: Media Types", RFC 2046,
                November 1996.

   [RFC 2104]   Krawczyk, H., Bellare, M. and R. Canetti, "HMAC: Keyed-
                Hashing for Message Authentication", RFC 2104, February
                1997.

   [RFC 2141]   Moats, R., "URN Syntax", RFC 2141, May 1997.

   [RFC 2253]   Wahl, W., Kille, S. and T. Howes, "Lightweight Directory
                Access Protocol (v3): UTF-8 String Representation of
                Distinguished Names", RFC 2253, December 1997.

   [RFC 2396]   Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
                Resource Identifiers (URI): Generic Syntax", RFC 2396,
                August 1998.

   [RFC 2437]   Kaliski, B. and J. Staddon, "PKCS #1: RSA Cryptography
                Specifications, Version 2.0", RFC 2437, October 1998.

   [RFC 2801]   Burdett, D., "Internet Open Trading Protocol - IOTP,
                Version 1.0", RFC 2801, April 2000.

   [RFC 2803]   Maruyama, H., Tamura, K. and N. Uramot, "Digest Values
                for DOM (DOMHASH)", RFC 2803, April 2000.



Davidson & Kawatsura         Informational                     [Page 26]

RFC 2802              Digital Signatures for IOTP             April 2000


   [Schneier]   Bruce Schneier, "Applied Cryptography: Protocols,
                Algorithms, and Source Code in C", 1996, John Wiley and
                Sons

   [SHA1]       NIST FIPS PUB 180-1, "Secure Hash Standard," National
                Institute of Standards and Technology, U.S. Department
                of Commerce, April 1995.

   [X.509]      ITU-T Recommendation X.509 (1997 E), "Information
                Technology - Open Systems Interconnection - The
                Directory:  Authentication Framework", June 1997.

   [X9.30]      ASC X9 Secretariat: American Bankers Association,
                "American National Standard for Financial Services -
                Public Key Cryptography Using Irreversible Algorithms
                for the Financial Services Industry - Part 1: The
                Digital Signature Algorithm(DSA)", 1995.

   [X9.62]      ASC X9 Secretariat: American Bankers
                Association,"American National Standard for Financial
                Services - Public Key Cryptography Using Irreversible
                Algorithms for the Financial Services Industry - The
                Elliptic Curve Digital Signature Algorithm (ECDSA)",
                Work in Progress, 1997.

   [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>




















Davidson & Kawatsura         Informational                     [Page 27]

RFC 2802              Digital Signatures for IOTP             April 2000


Authors' Addresses

   The authors of this document are:

   Kent M. Davidson
   Differential, Inc.
   440 Clyde Ave.
   Mountain View, CA 94043 USA

   EMail: [e-mail]


   Yoshiaki Kawatsura
   Hitachi, Ltd.
   890-12 Kashimada Saiwai Kawasaki,
   Kanagawa 2128567 Japan

   EMail: [e-mail]

































Davidson & Kawatsura         Informational                     [Page 28]

RFC 2802              Digital Signatures for IOTP             April 2000


Full Copyright Statement

   Copyright (C) The Internet Society (2000).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Davidson & Kawatsura         Informational                     [Page 29]