draft-ietf-l2vpn-vpls-bgp-02.txt   draft-ietf-l2vpn-vpls-bgp-03.txt 
Network Working Group K. Kompella (Editor) Network Working Group K. Kompella (Editor)
Internet Draft Y. Rekhter (Editor) Internet Draft Y. Rekhter (Editor)
Category: Standards Track Juniper Networks Category: Standards Track Juniper Networks
Expires: November 2004 May 2004 Expires: July 2005 January 2005
draft-ietf-l2vpn-vpls-bgp-02.txt draft-ietf-l2vpn-vpls-bgp-03.txt
Virtual Private LAN Service Virtual Private LAN Service
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
or will be disclosed, and any of which I become aware will be
disclosed, in accordance with RFC 3668.
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
skipping to change at page 1, line 34 skipping to change at page 1, line 39
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2005). All Rights Reserved.
Abstract Abstract
Virtual Private LAN Service (VPLS), also known as Transparent LAN Virtual Private LAN Service (VPLS), also known as Transparent LAN
Service, and Virtual Private Switched Network service, is a useful Service, and Virtual Private Switched Network service, is a useful
Service Provider offering. The service offered is a Layer 2 Virtual Service Provider offering. The service offered is a Layer 2 Virtual
Private Network (VPN); however, in the case of VPLS, the customers in Private Network (VPN); however, in the case of VPLS, the customers in
the VPN are connected by a multipoint network, in contrast to the the VPN are connected by a multipoint network, in contrast to the
usual Layer 2 VPNs, which are point-to-point in nature. usual Layer 2 VPNs, which are point-to-point in nature.
skipping to change at page 8, line 28 skipping to change at page 8, line 41
| Label Base (3 octets) | | Label Base (3 octets) |
+------------------------------------+ +------------------------------------+
3.2.2. Signaling PE Capabilities 3.2.2. Signaling PE Capabilities
The Encaps Type and Control Flags are encoded in an extended The Encaps Type and Control Flags are encoded in an extended
attribute. The community type also is used in L2 VPNs [3]. attribute. The community type also is used in L2 VPNs [3].
The Encaps Type for VPLS is 19. The Encaps Type for VPLS is 19.
Figure 4: Control Flags Bit Vector
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
| MBZ |P|Q|F|C|S| (MBZ = MUST Be Zero)
+-+-+-+-+-+-+-+-+
Figure 3: layer2-info extended community Figure 3: layer2-info extended community
+------------------------------------+ +------------------------------------+
| Extended community type (2 octets) | | Extended community type (2 octets) |
+------------------------------------+ +------------------------------------+
| Encaps Type (1 octet) | | Encaps Type (1 octet) |
+------------------------------------+ +------------------------------------+
| Control Flags (1 octet) | | Control Flags (1 octet) |
+------------------------------------+ +------------------------------------+
| Layer-2 MTU (2 octet) | | Layer-2 MTU (2 octet) |
+------------------------------------+ +------------------------------------+
| Reserved (2 octets) | | Reserved (2 octets) |
+------------------------------------+ +------------------------------------+
Figure 4: Control Flags Bit Vector
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
| MBZ |P|Q|F|C|S| (MBZ = MUST Be Zero)
+-+-+-+-+-+-+-+-+
With reference to Figure 4, the following bits are defined; the MBZ With reference to Figure 4, the following bits are defined; the MBZ
bits MUST be set to zero. bits MUST be set to zero.
Name Meaning Name Meaning
P If set to 1, then the PE will strip the outermost VLAN P If set to 1, then the PE will strip the outermost VLAN
tag from the customer frame on ingress, and push a tag from the customer frame on ingress, and push a
VLAN tag on egress. If set to 0, the customer frame VLAN tag on egress. If set to 0, the customer frame
is left unchanged. is left unchanged.
Q Reserved. Q Reserved.
F If set to 1 (0), the PE is (not) capable of flooding. F If set to 1 (0), the PE is (not) capable of flooding.
skipping to change at page 18, line 29 skipping to change at page 19, line 7
be obtained from the IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
Full Copyright Notice Full Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
This document and translations of it may be copied and furnished to except as set forth therein, the authors retain all their rights.
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgement
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/