RFC 5517 on Cisco Systems' Private VLANs: Scalable Security in a Multi-Client Environment

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

        RFC 5517

        Title:      Cisco Systems' Private VLANs: Scalable 
                    Security in a Multi-Client Environment 
        Author:     S. HomChaudhuri, M. Foschiano
        Status:     Informational
        Date:       February 2010
        Mailbox:    sanjibhc@gmail.com, 
                    foschia@cisco.com
        Pages:      12
        Characters: 28405
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-sanjib-private-vlan-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5517.txt

This document describes a mechanism to achieve device isolation
through the application of special Layer 2 forwarding constraints.
Such a mechanism allows end devices to share the same IP subnet while
being Layer 2 isolated, which in turn allows network designers to
employ larger subnets and so reduce the address management overhead.

Some of the numerous deployment scenarios of the aforementioned
mechanism (which range from data center designs to
Ethernet-to-the-home-basement networks) are mentioned in the following text
to exemplify the mechanism's possible usages; however, this document
is not intended to cover all such deployment scenarios nor delve into their
details.  This document is not an Internet Standards Track specification; it 
is published for informational purposes.

INFORMATIONAL: 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC