rfc2552.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

5.5.7.  Alerting Extension Module

   The Alerting Extension Module specifies the protocols to notify
   Customers about changes that can be interesting for them.

   This Extension Module requires the support of the following
   technologies:

   - Internet e-mail, based on SMTP protocol [8],
     and mail data formats specified in RFC 822 [9].
     The Broker should be able to generate and send e-mail messages.
   - SMS (Short Message Service), specified in [19].

   +-----------------------------------------------------+
   | Alerting Extension Module                           |
   +-----------+-----------------------------------------+
   | Alerting  | Internet e-mail [SMTP,RFC822] (sender), |
   |           | SMS                                     |
   +-----------+-----------------------------------------+

5.5.8.  Customer Discovery Extension Module

   The Customer Discovery Extension Module allows Z39.50 clients to use
   the service of the GAIA Broker.

   This Extension Module requires the Broker to support the server part
   of the Z39.50 protocol, as defined in [5].  The following subset of
   the protocol is required:

   - Init, Search, and Present services
   - GRS-1 record syntax

   Z39.50 protocol PDUs should be carried using TCP/IP network
   protocols.

   +----------------------------------------------------+
   | Discovery Extension Module                         |
   +------------------------+---------------------------+
   | Searching,             | Z39.50 (server)           |
   | Locating               |                           |
   +------------------------+---------------------------+

5.6.  Interface Modules

   For the purpose of conformance, all interfaces between FUMs and FUs,
   specified by the GAIA Standard, are grouped into GAIA Interface
   Modules.  These modules are recommended to be supported by a GAIA
   Broker, but they are not mandatory.  A Broker can choose a subset of



Blinov, et al.                                                 [Page 25]

RFC 2552                          GAIA                        April 1999


   Interface Modules that are more important in its area of operation,
   and implement interfaces defined in these modules.

   A full specification of the Functional Unit interfaces is presented
   in the GAIA Standard [1].

   The following table defines Interface Modules and specifies which
   interfaces have to be supported in each of them.

   +--------------------+------------------------------------+
   | Interface Module   | Interfaces that are required to be |
   |                    | supported in this module           |
   +--------------------+------------------------------------+
   | Search             | Search FU interface                |
   | Locate             | Locate FU interface                |
   | Order              | Order FU interface                 |
   | Discrete Delivery  | Discrete Delivery FU interface     |
   | Stream Delivery    | Stream Delivery FU interface       |
   | Customer           | Customer FU interface              |
   | Alerting           | Alerting FU interface              |
   | Directory Services | Directory Services FU interface    |
   | Authentication     | Authentication FU interface        |
   | Payment            | Payment FU interface               |
   +--------------------+------------------------------------+

6.  Acknowledgement

   We wish to express our gratitude to all members of the GAIA
   Consortium for a very lively discussion and their valuable direct and
   indirect input in the design process of the GAIA Standard.

7.  Security Considerations

   Security issues related to the electronic brokerage are discussed in
   Sections 2.1.4, 2.3 and 5.4.5.

8.  References

   [1]  GAIA Consortium, Deliverable 0403, "GAIA Standard (Final)",
        December 1998, see also <http://www.syspace.co.uk/GAIA/>.

   [2]  Object Management Group, "CORBA 2.0 Specification", July 1996,
        See <ftp://ftp.omg.org/pub/docs/formal/97-02-25.pdf>.

   [3]  Fielding, R., Gettys, J., Mogul, J., Frystyk, H. and T.
        Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC
        2068, January 1997.




Blinov, et al.                                                 [Page 26]

RFC 2552                          GAIA                        April 1999


   [4]  Berners-Lee, T. and D. Connolly, "Hypertext Markup Language -
        2.0", RFC 1866, November 1995.

   [5]  ANSI/NISO Z39.50-1995 or ISO 23950 "Information Retrieval:
        Application Service Definition and Protocol Specification".

   [6]  ISO 10161:1997 "Information and documentation -- Open Systems
        Interconnection -- Interlibrary Loan Application Protocol
        Specification".

   [7]  Postel, J. and J. Reynolds, "File Transfer Protocol", STD 9, RFC
        959, October 1985.

   [8]  Postel, J., "Simple Mail Transfer Protocol", STD 10, RFC 821,
        August 1982.

   [9]  Crocker, D., "Standard for the format of ARPA Internet text
        messages", STD 11, RFC 822, August 1982.

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

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

        Moore, K., "MIME (Multipurpose Internet Mail Extensions) Part
        Three: Message Header Extensions for Non-ASCII Text", RFC 2047,
        November 1996.

        Freed, N., Klensin, J., and J. Postel, "Multipurpose Internet
        Mail Extensions (MIME) Part Four: Registration Procedures", RFC
        2048, November 1996.

        Freed, N., and N. Borenstein, "Multipurpose Internet Mail
        Extensions (MIME) Part Five: Conformance Criteria and Examples",
        RFC 2049, November 1996.

   [11] ISO/IEC IS 13818 "Information technology -- Coding of moving
        pictures and associated audio information"

        Part 1: Systems
        Part 2: Video
        Part 3: Audio
        Part 4: Conformance testing
        Part 5: Software simulation




Blinov, et al.                                                 [Page 27]

RFC 2552                          GAIA                        April 1999


   [12] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson,
        "RTP: A Transport Protocol for Real-Time Applications", RFC
        1889, January 1996.

   [13] Hoffman, D., Fernando, G., Goyal, V. and M. Civanlar, "RTP
        Payload Format for MPEG1/MPEG2 Video", RFC 2250, January 1998.

   [14] Freier, A., Karlton, P. and P. Kocher, "The SSL Protocol -
        Version 3.0", Work in Progress, Transport Layer Security Working
        Group, November 1996, See
        <http://home.netscape.com/eng/ssl3/index.html>.

   [15] PKCS #7: Cryptographic Message Syntax Standard.  Version 1.5,
        November 1993.

   [16] Linn, J., "Generic Security Service Application Program
        Interface", RFC 1508, Geer Zolot Associate, September 1993.

   [17] Public-Key Infrastructure (X.509) IETF Working Group,
        <http://www.ietf.org/html.charters/pkix-charter.html>, July 98.

   [18] "SET Secure Electronic Transaction Specification", Version 1.0,
        MasterCard and Visa, May 97.

   [19] Digital Cellular Telecommunications System (Phase 2+): Technical
        Realization of the Short Message Service (SMS) Point-to-Point
        (PP) (GSM 3.40).  Version 5.2.0.  European Telecommunications
        Standards Institute.  May 1996.























Blinov, et al.                                                 [Page 28]

RFC 2552                          GAIA                        April 1999


9.  Authors' Addresses

   Mikhail Blinov
   Computer Science Department
   University College Dublin
   Belfield, Dublin 4, Ireland

   Phone: [phone]
   Fax:   [phone]
   EMail: [e-mail]


   Mikhail Bessonov
   Computer Science Department
   University College Dublin
   Belfield, Dublin 4, Ireland

   Phone: [phone]
   Fax:   [phone]
   EMail: [e-mail]


   Ciaran Clissmann
   Computer Science Department
   University College Dublin
   Belfield, Dublin 4, Ireland

   Phone: [phone]
   Fax:   [phone]
   EMail: [e-mail]





















Blinov, et al.                                                 [Page 29]

RFC 2552                          GAIA                        April 1999


10.  Full Copyright Statement

   Copyright (C) The Internet Society (1999).  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.
























Blinov, et al.                                                 [Page 30]