[GTER] [rfc-editor at rfc-editor.org: RFC 3386 on Network Hierarchy and Multilayer Survivability]

[Rafael R Obelheiro]

----- Forwarded message from rfc-editor at rfc-editor.org -----

Date: Fri, 08 Nov 2002 15:45:26 -0800
From: rfc-editor at rfc-editor.org
Subject: RFC 3386 on Network Hierarchy and Multilayer Survivability
To: IETF-Announce: ;
Cc: rfc-editor at rfc-editor.org, te-wg at ops.ietf.org


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


        RFC 3386

        Title:      Network Hierarchy and Multilayer Survivability
        Author(s):  W. Lai, Ed., D. McDysan, Ed.
        Status:     Informational
        Date:       November 2002
        Mailbox:    wlai at att.com, dave.mcdysan at wcom.com
        Pages:      27
        Characters: 65345
        Updates/Obsoletes/SeeAlso:  None
                         
        I-D Tag:    draft-ietf-tewg-restore-hierarchy-01.txt

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


This document presents a proposal of the near-term and
practical requirements for network survivability and hierarchy
in current service provider environments.

This document is a product of the Internet Traffic Engineering Working
Group of the IETF.

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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

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

        To: rfc-info at 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 at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR at 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.



----- End forwarded message -----