RFC 3871 on Operational Security Requirements for Large Internet Service Provider (ISP) IP Network Infrastructure

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

        RFC 3871

        Title:      Operational Security Requirements for Large
                    Internet Service Provider (ISP) IP Network
                    Infrastructure
        Author(s):  G. Jones, Ed.
        Status:     Informational
        Date:       September 2004
        Mailbox:    gmj3871@pobox.com
        Pages:      81
        Characters: 151101
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-jones-opsec-06.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3871.txt

This document defines a list of operational security requirements for
the infrastructure of large Internet Service Provider (ISP) IP
networks (routers and switches).  A framework is defined for
specifying "profiles", which are collections of requirements
applicable to certain network topology contexts (all, core-only,
edge-only...).  The goal is to provide network operators a clear,
concise way of communicating their security requirements to vendors.

This memo provides information for the Internet community.  It 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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  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@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.