A new Request for Comments is now available in online RFC libraries.


        RFC 1636:

        Title:      Report of IAB Workshop on Security in the Internet
                    Architecture - February 8-10, 1994
        Author:     R. Braden, D. Clark, S. Crocker & C. Huitema     
        Mailbox:    Braden@ISI.EDU, ddc@lcs.mit.edu, crocker@tis.com,
                    Christian.Huitema@MIRSA.INRIA.FR 
        Pages:      52
        Characters: 130,761
        Update/Obsoletes:  none


This document is a report on an Internet architecture workshop,
initiated by the IAB and held at USC Information Sciences Institute on
February 8-10, 1994.  This workshop generally focused on security
issues in the Internet architecture.

This document should be regarded as a set of working notes containing
ideas about security that were developed by Internet experts in a
broad spectrum of areas, including routing, mobility, realtime
service, and provider requirements, as well as security.  It contains
some significant diversity of opinions on some important issues.  This
memo is offered as one input in the process of developing viable
security mechanisms and procedures for the Internet.

This memo provides information for the Internet community.  This
memo does not specify an Internet standard of any kind.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute