RFC 2643 on Cabletron's SecureFast VLAN Operational Model

RFC Editor <rfc-ed@ISI.EDU> Wed, 04 August 1999 20:24 UTC

Message-Id: <199908041958.MAA28754@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2643 on Cabletron's SecureFast VLAN Operational Model
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 04 Aug 1999 12:58:51 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


      RFC 2643:

        Title:	    Cabletron's SecureFast VLAN Operational Model 
                    Version 1.8
        Author(s):  D. Ruffen, T. Len, J. Yanacek
        Status:     Informational
	Date:       August 1999
        Mailbox:    ruffen@ctron.com, len@ctron.com, jyanacek@ctron.com
        Pages:      60
        Characters: 121786
	Updates:    
        I-D Tag:    draft-rfced-info-cabletron-vlan-00.txt


        URL:        ftp://ftp.isi.edu/in-notes/rfc2643.txt


Cabletron's SecureFast VLAN (SFVLAN) product implements a
distributed connection-oriented switching protocol that provides
fast forwarding of data packets at the MAC layer.  The product
uses the concept of virtual LANs (VLANs) to determine the validity
of call connection requests and to scope the broadcast of certain
flooded messages.

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/rfc2643.txt"><ftp://ftp.isi.edu/in-notes/rfc2643.txt>

RFC 2643 on Cabletron's SecureFast VLAN Operation… RFC Editor