RFC 3619 on Extreme Networks' Ethernet Automatic Protection Switching (EAPS) Version 1

rfc-editor@rfc-editor.org Tue, 28 October 2003 08:53 UTC

Message-Id: <200310280058.h9S0wjf20661@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3619 on Extreme Networks' Ethernet Automatic Protection Switching (EAPS) Version 1
Cc: rfc-editor@rfc-editor.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 27 Oct 2003 16:58:45 -0800
Sender: owner-ietf-announce@ietf.org
Precedence: bulk

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


        RFC 3619

        Title:      Extreme Networks' Ethernet Automatic Protection
                    Switching (EAPS) Version 1
        Author(s):  S. Shah, M. Yip
        Status:     Informational
        Date:       October 2003
        Mailbox:    sshah@extremenetworks.com, my@extremenetworks.com
        Pages:      7
        Characters: 14440
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-shah-extreme-eaps-03.txt

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


This document describes the Ethernet Automatic Protection
Switching (EAPS) (tm) technology invented by Extreme Networks to
increase the availability and robustness of Ethernet rings.  An
Ethernet ring built using EAPS can have resilience comparable to
that provided by SONET rings, at a lower cost and with fewer
constraints (e.g., ring size).

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.echo 
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.

ftp://ftp.isi.edu/in-notes/rfc3619.txt"><ftp://ftp.isi.edu/in-notes/rfc3619.txt>

RFC 3619 on Extreme Networks' Ethernet Automatic … rfc-editor