RFC 4554: Use of VLANs for IPv4-IPv6 Coexistence in Enterprise Networks
In plain English — editorial summary, not part of the RFC
Ethernet VLANs are quite commonly used in enterprise networks for the purposes of traffic segregation. This document describes how such VLANs can be readily used to deploy IPv6 networking in an enterprise, which focuses on the scenario of early deployment prior to availability of IPv6-capable switch-router equipment. In this method, IPv6 may be routed in parallel with the existing IPv4 in the enterprise and delivered at Layer 2 via VLAN technology. The IPv6 connectivity to the enterprise may or may not enter the site via the same physical link. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4554
- Published
- June 2006
- Authors
- T. Chown
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4560Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup OperationsCurrent
June 2006
- RFC 4547Event Notification Management Information Base for Data over Cable Service Interface Specifications (DOCSIS)-Compliant Cable Modems and Cable Modem Termination SystemsUpdated
June 2006
- RFC 4546Radio Frequency (RF) Interface Management Information Base for Data over Cable Service Interface Specifications (DOCSIS) 2.0 Compliant RF InterfacesUpdated
June 2006
- RFC 4564Objectives for Control and Provisioning of Wireless Access Points (CAPWAP)Current
July 2006
- RFC 4565Evaluation of Candidate Control and Provisioning of Wireless Access Points (CAPWAP) ProtocolsCurrent
July 2006
- RFC 4502Remote Network Monitoring Management Information Base Version 2Current
May 2006
- RFC 4608Source-Specific Protocol Independent Multicast in 232/8Current
August 2006
- RFC 4609Protocol Independent Multicast - Sparse Mode (PIM-SM) Multicast Routing Security Issues and EnhancementsCurrent
October 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?