Skip to main content

VLAN Aggregation for Efficient IP Address Allocation

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3069.
Authors Barry A. Dykes , Danny R. McPherson
Last updated 2020-01-21 (Latest revision 2001-01-15)
RFC stream Legacy stream
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 3069 (Informational)
Telechat date (None)
Responsible AD (None)
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3069

        Title:      VLAN Aggregation for Efficient IP Address
        Author(s):  D. McPherson, B. Dykes
        Status:     Informational
        Date:       February 2001
        Pages:      7
        Characters: 14891
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-mcpherson-vlan-ipagg-02.txt


This document introduces the concept of Virtual Local Area Network
(VLAN) aggregation as it relates to IPv4 address allocation.
A mechanism is described by which hosts that reside in the same
physical switched infrastructure, but separate virtual broadcast
domains, are addressed from the same IPv4 subnet and share a common
default gateway IP address, thereby removing the requirement of a
dedicated IP subnet for each virtual Local Area Network (LAN) or
Metropolitan Area Network (MAN).
Employing such a mechanism significantly decreases IPv4 address
consumption in virtual LANs and MANs.  It may also ease
administration of IPv4 addresses within the network.

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

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.