rfc1862.txt

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

   The group noted that there have been difficulties in scheduling joint
   working group meetings and recommends that there be a clearly defined
   process inside the IETF to facilitate scheduling such meetings.

6. Conclusions and Recommendations

   The workshop provided an opportunity for ongoing conversations about
   the architecture to continue and also provided space for focused
   examination of some issues and for some new voices and experience
   from other areas of Internet growth to participate in the
   architectural process.





McCahill, et al              Informational                     [Page 22]

RFC 1862                  IAB Workshop Report              November 1995


   Part of the conclusion of the workshop is a set of recommendations to
   the IESG and IETF community.

   Recommendations on research/implementation directions:

   1. Caching and replication are important and overlooked pieces of
   Internet middleware. We should do something about it as soon as
   possible, perhaps by defining an architecture and service model for
   common implementation.

   2. Within the 'wholesale' layer, i.e. within the layer which provides
   a consistent view of the information resources available on the
   Internet, the first services that should be provided are:

        * Object retrieval,

        * Name resolution,

        * Caching and replication.

   3. There would be quick payoff if the raw materials layer, i.e. the
   layer in which information resources are physically transmitted to
   computers, could provide the following services:

        * Connectivity

        * Bandwidth, latency, and reliability or  a service envelope

        * Security constraints on communication and transactions

   4. Develop security modules usable by the implementors of information
   clients and servers - reusable across many different, heterogeneous
   applications and platforms

Recommendations to the IESG, IETF, and IANA

   1. Numbers that are formally defined and kept in documents in
   distributed information systems (for instance, Assigned Numbers)
   should be available in some kind of database for use by applications.

   2. Develop and communicate a security model usable by designers of
   information applications - current models are not considered usable
   or are not widely accepted on the Internet.

   3. RFC authors should be given advice on how security considerations
   need to be written. The IESG security area should prepare guidelines
   for writing security considerations.




McCahill, et al              Informational                     [Page 23]

RFC 1862                  IAB Workshop Report              November 1995


   4. Proposed Standards should not be accepted by the IESG unless they
   really consider security. This will require recommendations 2 and 3
   to be implemented first.

   5. Make clear what security services you can expect from the lower
   layers.

   6. Make sure that the key distribution infrastructure is reviewed for
   usability by information applications.

   7. There needs to be a process inside the IETF for scheduling a joint
   meeting between two working groups - for example, so that the key
   distribution WG can meet jointly with IIIR.






































McCahill, et al              Informational                     [Page 24]

RFC 1862                  IAB Workshop Report              November 1995


APPENDIX A - Workshop Organization

   The workshop was held at MCI's facility in Tyson Corners, Virginia.
   The workshop organizers and attendees wish to thank MCI for the use
   of their facilities to host the workshop.

   All attendees met in joint session for the first half of October 12.
   They then split into three groups. The first group considered the
   "distributed database" problem which has arisen over and over again
   in the design of parts of the Internet. The two other groups met to
   consider a list of issues pertaining to the information
   infrastructure. The groups ran independently until the morning of
   October 14, when they met again in joint session.

   The following people attended the workshop:

   Abel Weinrib            [e-mail]

   Barry Leiner            [e-mail]

   Cecilia Preston         [e-mail]

   Chris Weider            [e-mail]

   Christian Huitema       [e-mail]

   Cliff Lynch             [e-mail]

   Clifford Neuman         [e-mail]

   Dan LaLiberte           [e-mail]

   Dave Sincoskie          [e-mail]

   Elise Gerich            [e-mail]

   Erik Huizer             [e-mail]

   Jill Foster             [e-mail]

   John Curran             [e-mail]

   John Klensin            [e-mail]

   John Romkey             [e-mail]

   Joyce Reynolds          [e-mail]




McCahill, et al              Informational                     [Page 25]

RFC 1862                  IAB Workshop Report              November 1995


   Karen Sollins           [e-mail]

   Larry Masinter          [e-mail]

   Lixia Zhang             [e-mail]

   Mark McCahill           [e-mail]

   Michael Mealling        [e-mail]

   Mitchell Charity        [e-mail]

   Mike Schwartz           [e-mail]

   Mike St. Johns          [e-mail]

   Mitra                   [e-mail]

   Paul Mockapetris        [e-mail]

   Steve Crocker           [e-mail]

   Tim Berners-Lee         [e-mail]

   Ton Verschuren          [e-mail]

   Yakov Rekhter           [e-mail]

Security Considerations

   This memo discusses certain aspects of security and the information
   infrastructure. It contains general recommendations about security
   enhancements required by information applications on the Internet.


















McCahill, et al              Informational                     [Page 26]

RFC 1862                  IAB Workshop Report              November 1995


Authors' Addresses

   Mark McCahill
   University of Minnesota
   room 190 Shepherd Labs
   100 Union Street SE
   Minneapolis, MN 55455
   EMail: [e-mail]


   John Romkey [Editor]
   1770 Massachusetts Ave. #331
   Cambridge, MA  02140
   EMail: [e-mail]


   Michael F.  Schwartz
   Department of Computer Science
   University of Colorado
   Boulder, CO 80309-0430
   EMail: [e-mail]


   Karen Sollins
   MIT Laboratory for Computer Science
   545 Technology Square
   Cambridge, MA 02139-1986
   EMail: [e-mail]


   Ton Verschuren
   SURFNet
   P.O. Box 19035
   3501 DA Utrecht
   The Netherlands
   EMail: [e-mail]


   Chris Weider
   Bunyip Information Systems
   310 St. Catherine St. West
   Suite 300
   Montreal, PQ H2A 2X1
   CANADA
   EMail: [e-mail]






McCahill, et al              Informational                     [Page 27]