Abstract:
Encryption of Ethernet/IEEE 802.3 packet data units (PDUs) at the edge of the enterprise network, in such a way as to support resilient Virtual Private LAN Services (VPLS) network designs. The Ethernet traffic is securely tunneled within encrypted Ethernet tunnels from the edge to the edge of the enterprise network. The encrypted Ethernet traffic is also tunneled within Multi-Protocol Layer Switching (MPLS) tunnels from the edge to the edge of the service provider network. The enterprise network thus manages its own Ethernet site-to-site Virtual Private Network (VPN). The service provider thus independently manages its own MPLS network. The result provides a VPLS or Layer 2 MPLS VPN to the enterprise; the enterprise Ethernet encrypted network can thus be considered as an overlay to the MPLS service provider network.

Description:
BACKGROUND OF THE INVENTION 
       [0001]    1. Field of the Invention 
         [0002]    The present invention relates generally to enterprise networks, and, more particularly, to encryption over enterprise networks. 
         [0003]    2. Description of the Prior Art 
         [0004]    The present invention relates to how enterprise networks can secure their Ethernet packet data units (PDUs) using Ethernet encryption when that Ethernet traffic is transported over resilient Multi-Protocol Layer Switching (MPLS) Layer 2 Virtual Private Networks (VPNs), also called Virtual Private Line Services (VPLS). 
         [0005]    Enterprise networks have been connecting their sites distributed over a metro area network (MAN) provided to them by their service providers and using VPLS as defined through a number of Internet drafts and Request For Comments (RFCs) in the IETF Layer 2 VPN working group. Enterprise networks have been using those provider provisioned MPLS networks with different network resiliency scenarios, where Customer Edge (CE) routers can be redundant and/or service Providers Edge (PE) routers can also be redundant. 
         [0006]    Problems with the Prior Art: 
         [0007]    Virtual Private LAN Services or Layer 2 MPLS VPNs: 
         [0008]    Service providers have been supplying VPLS VPNs to their commercial enterprise customers using their MPLS metro networks. Enterprise networks are connected to their service provider networks through their edge routers called Customer Edge (CE) routers. Service providers offer the MPLS VPN through their Provider Edge (PE) routers. 
         [0009]    VPLS are presently defined through multiple Internet drafts and RFCs in the Layer 2 VPN working group of the IETF (L2VPN). 
         [0010]    VPLS provides connectivity between geographically dispersed enterprise sites across an MPLS metro network, as if they were connected using a LAN. VPLS can be seen as if the MPLS metro network operates as a switch or a bridge. 
         [0011]    VPLS emulates the various LANs services over an MPLS transport network and creates a Layer 2 broadcast domain basically through a dynamic Ethernet learning bridge model. 
         [0012]    Ethernet frames are carried over a pseudo-wire (PW) which provides an MPLS point-to-point Layer 2 tunnel between two service providers&#39; PEs. PW uses the encapsulation mechanism defined in the RFC 4448 to emulate the Ethernet service. The encapsulation provides two label layers: one for the emulated Ethernet service, and another one for the MPLS underlying tunnel. 
         [0013]    Broadcast and multicast are two important LANs services used for Ethernet corporate networks but are not supported by MPLS. VPLS extends the encapsulation defined in RFC 4448 for transporting Ethernet and VLANs traffic across multiple sites that belong to the same enterprise by providing in particular broadcast and multicast capabilities. This requires MAC address learning and aging on a per LSP basis, packet replication across LSPs for multicast and broadcast traffic and for flooding of unknown unicast destination traffic. 
         [0014]    Two network protocols are presently used by service providers to provide VPLS services and presently investigated by the IETF: the Label Distribution Protocol (LDP) or the Border Gateway Protocol (BGP). 
         [0015]    Deploying Resilient VPLS Networks: 
         [0016]    Being a critical infrastructure between remote sites, a VPLS network must be designed to ensure resilient network operations. Resiliency at the Layer 2 is provided through redundant paths which deployments ensure protection of the Ethernet traffic and restoration of the VPLS service. 
         [0017]    In order to ensure resilient network operations, enterprise customers can multi-home their site traffic over two CEs to the service provider network. Similarly, in order to ensure resilient network operations, service providers can route the enterprise traffic over two PEs located into the same point of presence (POP) or across multiple POPs. 
         [0018]    Additionally, enterprise customers can choose to use the services of two or more service providers, therefore ensuring that their CEs communicate to different PEs belonging to different service provider networks. 
         [0019]    Encrypting the Ethernet Traffic: 
         [0020]    The IEEE is presently defining a standard IEEE 802.1 AE Media Access Control Security (MACSec) for encrypting Ethernet frames. However, the present scope of the standard is limited to “hop-by-hop” security, and not “end-to-end” as it is the case for IP Security (IPSec) for securing IP traffic, as defined in the RFC 2401. IPSec encrypts IP application data from end-to-end at Layer 3. For key management, 802.1 AE requires a new standard still in development IEEE 802.1 af Media Access Control (MAC) Key Security. 
         [0021]    Following is a working alternative to IEEE 802.1 AE and 802.1 af for Ethernet encryption that we are calling Ethernet Encapsulation Security Payload (EESP), which enables Ethernet encryption from end-to-end between two remote CEs belonging to the same enterprise network. Key management is based on the Internet Key Exchange (IKE) protocol, as defined in the RFC 2409 as it is the case for IPSec. 
         [0022]    EESP provides data origin authentication and data integrity for the entire Ethernet packet for both the header and the payload. EESP also provides confidentiality for the Ethernet payload. 
         [0023]    Encryption is performed using the Advanced Encryption Standard (AES)-256 Cipher Block Chaining (CBC) algorithm while authentication is provided using the Secure Hash Algorithm (SHA)-1 algorithm. Encryption keys can be negotiated using IKE, or entered manually. 
         [0024]    Manual keys are generally not used because of the configuration challenges and re-key requirements to implement them in large networks. For those reasons, IKE is normally used for key exchange. However, IKE is based on a secure connection only established between two policy enforcement points (PEPs), and a resulting key negotiation being completed between those two PEPs. As a result, the connection-oriented nature of IKE has a few drawbacks. 
         [0025]    If the traffic needs to be sent and/or received through multiple paths, as would be the case in a mesh or resilient network, there is no single pair of points that can be identified to perform key negotiation and no single PEP that can be selected as the ultimate destination in the tunnel header. 
       SUMMARY OF THE INVENTION 
       [0026]    A first aspect of the present invention is to provide a method for operating on a data packet to provide an enterprise networking environment over a service provider network, including the steps of: 
         [0027]    providing a customer edge (CE) router function, located within the enterprise network, operable for providing the data packet; 
         [0028]    a Policy Enforcement Point (PEP) function, operable for:
       applying an Ethernet encryption protocol to the data packet; and   applying a security association policy to the data packet;       
 
         [0031]    a provider edge router function, located within the service provider network, operable for: 
         [0032]    applying an MPLS protocol to the data packet to provide a Virtual Private LAN Network (VPLS) service to the enterprise; and 
         [0033]    forwarding the data packet according to the MAC learning and aging functions provided by the VPLS service. 
         [0034]    Another aspect of the present invention is to provide an apparatus for operating on a data packet to provide an enterprise networking environment over a service provider network, including: 
         [0035]    a customer edge (CE) router function, located within the enterprise network, for:
       providing the data packet;       
 
         [0037]    a Policy Enforcement Point (PEP) function, for:
       applying an Ethernet encryption protocol to the data packet; and   applying a security association policy to the data packet;       
 
         [0040]    a provider edge router function, located within the service provider network, for: 
         [0041]    applying an MPLS protocol to the data packet to provide a Virtual Private LAN Network (VPLS) service to the enterprise; and forwarding the data packet according to the MAC learning and aging functions provided by the VPLS service. 
         [0042]    With the present state of the art, there is no way to enable redundant mesh network designs for enterprise networks when encrypting Ethernet traffic from point-to-point either with IKE or with any other key management mechanism negotiated between two parties. 
         [0043]    Point-to-point key negotiation does not allow the design of the MPLS VPN network to be point-to-multipoint, one CE connected to multiple PEPs, or multipoint-to-multipoint, multiple CEs connected to multiple PEPs. 
         [0044]    The present invention gives precedence to the encryption of Ethernet PDUs at the edge of the enterprise network for resilient VPLS VPN network designs. All Ethernet traffic from the enterprise network is protected using Ethernet Encapsulation Security Payload between the distributed enterprise sites over the MPLS network provided by the service provider. The enterprise network manages its own Ethernet encrypted site-to-site VPN. The service provider independently manages its MPLS network, providing a VPLS VPN or Layer 2 MPLS VPN to the enterprise. The enterprise Ethernet encrypted network can thus be seen as an overlay to the MPLS service provider network. 
         [0045]    The enterprise network can have a redundant MPLS VPN network provided by one or multiple service providers and the enterprise network can be redundant as well. Because the enterprise Ethernet encrypted network can be seen as an overlay network to the MPLS network, both the Ethernet encrypted network and the MPLS network can operate independently. The Ethernet traffic is securely tunneled within encrypted tunnels from the edge to the edge of the enterprise network. The Ethernet encrypted traffic is also tunneled within MPLS tunnels from the edge to the edge of the service provider network. 
         [0046]    Network Overlay of Security Policies and Encryption Keys to the Data Plane: 
         [0047]    By dividing the generation and distribution of security policies and encryption keys into separate components and combining them in new ways across multiple devices, the fundamental connection-oriented approach of point-to-point key negotiation can be changed while maintaining most of its present features and all of its security capabilities. This approach can solve the present point-to-point protocol limitations for security policies and encryption keys to completely secure network traffic over resilient networks and in particular point-to-multipoint and multipoint-to-multipoint networks. 
         [0048]    This new three-layer approach to the deployment of Ethernet encryption includes the following functional components: 
         [0049]    PEP: The PEP devices still exist in the network to protect traffic, but rather than exchanging keys on a one-to-one basis with other PEPs, they receive their security associations (SAs) externally from a centralized entity (KAP). 
         [0050]    Key Authority Point (KAP): According to the security policies, the KAP generates SAs and encryption keys, and then distributes them to the PEP units and peer KAP devices. 
         [0051]    Management and Policy Server (MAP): The MAP generates the security policies and distributes them to the KAP servers. 
         [0052]    The result is that common keys can be used by multiple PEP devices for data transmission over multiple paths in a resilient network. 
         [0053]    Generation and Distribution of Security Policies and Encryption Keys 
         [0054]    Implementing this three-layer approach, PEPs are deployed between the remote enterprise VPN sites that need secure tunnels. 
         [0055]    Each PEP is associated with an Ethernet LAN. A policy will be defined for each LAN associated with each PEP protecting those Ethernet networks. 
         [0056]    The KAP can be configured with the policies from the MAP, and can distribute those policies and SAs to the PEPs. The KAP can generate a single outbound key for each PEP policy and its associated network and distribute it securely to the PEP, as well as its peers. For those remote peer PEPs, that key can become the inbound key. Each PEP network then receives the same key per policy from the KAP. PEPs then encrypt the Ethernet traffic using EESP from network to network. Inbound keys, for encrypting the traffic, and outbound keys, for decrypting the traffic, are the same 
         [0057]    Additional information about the details of the generation and distribution of security policies and encryption keys are incorporated by the following co-pending U.S. Patent Applications, all of which are assigned to CiperOptics, Inc., the assignee of the present application, and all of which are hereby incorporated by reference in their entirety: 
         [0058]    U.S. Provisional Patent Application No. 60/756,765 entitled SECURING NETWORK TRAFFIC USING DISTRIBUTED KEY GENERATION AND DISSEMINATION OVER SECURE TUNNELS, filed Jan. 6, 2006, which describes how an IP header of an outgoing packet is copied into an outer header of an IPsec tunnel mode packet; 
         [0059]    U.S. Provisional Patent Application No. 60/813,766 entitled SECURING NETWORK TRAFFIC BY DISTRIBUTING POLICIES IN A HIERARCHY OVER SECURE TUNNELS, filed Jun. 14, 2006, which describes how to distribute security policies using tunnels; and 
         [0060]    U.S. Provisional Patent Application No. X entitled SECURITY ENCAPSULATION OF ETHERNET FRAMES, filed Y, 2006, which describes how to encrypt Ethernet frames. 
         [0061]    Data Protection Implementation over the VPLS Network: 
         [0062]    The Ethernet data protection network is an overlay to the MPLS Layer 2 VPN redundant network, so no change is required to the service provider MPLS network. Enterprise traffic from CE to CE is protected. The original Ethernet header is in the clear and only the end-user data payload is encrypted using Ethernet encryption. This enables the enterprise customer to leverage the service provider service level agreements (SLAs) and network operations management capabilities. 
         [0063]    The MAP provides polices for each network to communicate through the MPLS network and protect traffic between CE sites. The KAP provides a single key for each PEP of the MPLS VPN and distributes it securely to all PEPs. That key will be used both for encrypting inbound traffic and decrypting outbound traffic between the PEPs. No clear policy will be needed in that case since the traffic path between the sites over the VPLS network is determined by the CE routers at Layer 3. Additionally, the KAP can be redundant to insure resilient key generation and distribution. 
         [0064]    Thus, the present invention provides for encryption of Ethernet/IEEE 802.3 packet data units (PDUs) at the edge of the enterprise network, in such a way as to support resilient Virtual Private LAN Services (VPLS) network designs. 
         [0065]    These and other aspects of the present invention will become apparent to those skilled in the art after a reading of the following description of the preferred embodiment when considered with the drawings, as they support the claimed invention. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0066]    The foregoing will be apparent from the following descriptions of the invention, as illustrated in the accompanying drawings. The drawings are not necessarily to scale, instead emphasis is placed upon illustrating embodiments of the present invention. 
           [0067]      FIG. 1  illustrates a use case of an enterprise network with four remote sites connected over an MPLS network provided by one or multiple service providers and providing a VPLS service to the enterprise. 
           [0068]      FIG. 2  describes the various network resiliency scenarios possible between CEs and PEs for an enterprise network and its service providers. 
           [0069]      FIG. 3  describes the proposed Ethernet encryption approach using AES-256 for encryption and SHA-1 for authentication. 
           [0070]      FIG. 4  describes the set-up of the Ethernet encrypted tunnels and SAs for two networks, network A and network B, between two PEPs and when those PEPs are redundant, network C being redundant to network A and network D being redundant to network B. 
           [0071]      FIG. 5  describes the network overlay of the management and control plane to the data plane for the generation of the security policies and encryption keys. 
           [0072]      FIG. 6  describes how a KAP with the security policies defined by the MAP generates each key for each PEP of the enterprise site. 
           [0073]      FIG. 7  details the network design of the remote enterprise sites with their associated PEPs connected to the service provider MPLS network. 
       
    
    
     DETAILED DESCRIPTION 
       [0074]    In the following description, like reference characters designate like or corresponding parts throughout the several views. Also in the following description, it is to be understood that such terms as “forward,” “rearward,” “front,” “back,” “right,” “left,” “upwardly,” “downwardly,” and the like are words of convenience and are not to be construed as limiting terms. 
         [0075]    The present invention provides systems and methods for for operating on a data packet to provide an enterprise networking environment over a service provider network, including: a customer edge (CE) router function, located within the enterprise network, operable for providing the data packet; 
         [0076]    a Policy Enforcement Point (PEP) function, operable for:
       applying an Ethernet encryption protocol to the data packet; and   applying a security association policy to the data packet;       
 
         [0079]    a provider edge router function, located within the service provider network, operable for: applying an MPLS protocol to the data packet to provide a Virtual Private LAN Network (VPLS) service to the enterprise; and forwarding the data packet according to the MAC learning and aging functions provided by the VPLS service. 
         [0080]    Referring now to the drawings in general, the illustrations are for the purpose of describing a preferred embodiment of the invention and are not intended to limit the invention thereto. As best seen in  FIG. 1 , a typical use case of an enterprise network  100  is illustrated. That enterprise network  100  has four remote sites located in four different cities over the San Francisco metro area: Menlo Park, Calif.  110 - 1 , San Francisco, Calif.  110 - 2 , Sausalito, Calif.  110 - 3  and Berkeley, Calif.  110 - 4 . 
         [0081]    Each site  110  might include a number of users  120 , datacenters  130  and/or storage area networks  140 . Sites can be considered as fairly large considering their number of subnets and as hubs to smaller branch offices that are not represented in this figure. 
         [0082]    Each site  110  is called a VPN site and runs an IP network over an Ethernet network. Each VPN site is connected to one or more service provider MPLS networks  150 , providing a VPLS VPN. The VPLS implements an encapsulation of the Ethernet service provided over the MPLS network as defined in RFC 4448 and uses either LDP or BGP to provide the distribution of the MPLS labels that emulates the Ethernet bridge as defined in the Internet drafts and RFCs in the Layer 2 VPN working group of the IETF (L2VPN). 
         [0083]    Each site  110  wants to protect its Ethernet over the service provider networks  150  using a Layer 2 Ethernet encryption mechanism. To that end, each site edge router called a CE is connected to a PEP  170  that provides Ethernet encryption and decryption of Ethernet PDUs. That PEP  170  can be external to the CE  160  or integrated to it as a blade. 
         [0084]    The Ethernet traffic for the enterprise is of high value to its business and therefore must be encrypted. But besides encryption, in order to provide that traffic reliably between each site, the enterprise also needs to provide a resilient network. 
         [0085]    Three case scenarios are possible for a resilient network, as represented in  FIG. 2 ; the CE at each site  110  can be redundant; the service provider edge routers called PEs inside the MPLS network  150  can be redundant; or, the PE can belong to one or more service providers. 
         [0086]    The minimum resiliency scenario is two PEs  180 . The maximum resiliency scenario involves multiple CEs  160  and multiple PEs  180  belonging to multiple service providers. 
         [0087]      FIG. 3  illustrates the encryption of the Ethernet packet. Encryption is performed using the Advanced Encryption Standard (AES)—256 Cipher Block Chaining (CBC) algorithm while authentication is provided using the Secure Hash Algorithm (SHA) −1 algorithm. 
         [0088]    The encapsulation mode uses the original Ethernet header as the header for the encapsulated packet. The shaded area in the figure identifies the portion of the packet that is encrypted. Encryption keys can be negotiated using IKE, or entered manually. 
         [0089]    IKE or any other point-to-point key negotiation protocol can only operate between two endpoints. In other words, IKE is a connection-oriented protocol between two endpoints. IKE phase I provides authentication and a secure channel between the two endpoints and IKE phase II negotiates the SAs between the two endpoints. 
         [0090]    Encrypting Ethernet PDUs with any point-to-point key negotiation protocol for key generation does not allow the network design to be redundant. In other words, IKE cannot be used between four PEPs at the same time, if the traffic is redundant between each pair of PEPs, as illustrated in  FIG. 4 . IKE can certainly be used between network A and network B in  FIG. 4 . But IKE cannot be used at the same time between (network A, network C) and (network B, network D). 
         [0091]    One way to encrypt traffic between two redundant networks (network A, network C) and (network B, network D), as in  FIG. 4 , would be to establish the same SAs for each pair of PEPs  170 . The same security policies and encryption keys would be used between each pair of PEPs  170 . 
         [0092]    This can lead to the solution provided in  FIG. 5 , where security policies and encryption keys overlay the data plane for the encryption. In other words, the management and control plane  202  does not coexist with the data plane  204 . One layer provides the security policies that can be viewed as the management plane and another layer provides the encryption keys that can be viewed as the control plane. Encryption keys are generated according to the security policies. 
         [0093]    In the illustrated architecture, the device providing the security policy is called a Management Authority Point (MAP)  200 , whereas the device providing the encryption keys is called a Key Authority Point (KAP)  210 . 
         [0094]    The MAP  200  interfaces to the KAP  210 , which interfaces itself to the PEPs  170 . 
         [0095]    The KAP  210  can be redundant. All policies and keys shall be securely stored and distributed. Policies for re-key should be enabled, and each node (MAP, KAP and PEP) should be securely authenticated and authorized to accomplish its function. 
         [0096]    Applying the concepts developed in  FIG. 5  leads to  FIG. 6 , which describes a preferred implementation of key exchanges between multiple PEPs  170  that enables the encryption of the Ethernet traffic. 
         [0097]    In  FIG. 6 , the primary PEP  170 - 1  located at the Menlo Park VPN site  110 - 1 , will receive its outbound encryption key “k1” from the KAP  210 . The KAP  210  itself would generate k 1 . The Menlo Park PEP  170 - 1  uses that key to encrypt its traffic. That key is also used by the PEPs ( 170 - 2 ,  170 - 3 ,  170 - 4 ) located at other sites  110  as inbound keys for traffic coming from the Menlo Park PEP  170 - 1 . The KAP  210  thus also distributes k 1  to the PEPs ( 170 - 2 ,  170 - 3 ,  170 - 4 ) located at the San Francisco, Sausalito and Berkeley sites ( 110 - 2 ,  110 - 3 ,  110 - 4 , respectively). 
         [0098]    When a redundant or secondary PEP  170 - 1 - r  is used at the Menlo Park site  110 - 1 , the same security policy and encryption keys will apply both to the primary PEP  170 - 1  and secondary PEP  170 - 1 - r.    
         [0099]    The encryption key k 1  is used by all PEPs as both an inbound, to encrypt the Ethernet traffic, and outbound key to decrypt the Ethernet traffic. 
         [0100]    Applying the concepts of  FIG. 6 , with the resiliency scenarios defined in  FIG. 2  to the use case illustrated in  FIG. 1 , gives an overall solution as illustrated in  FIG. 7 . 
         [0101]    For example, the MAP  200  and KAP  210  are located in the San Francisco site  110 - 2  and provide policy and key generation and distribution for the four sites. Each site ( 110 - 1 ,  110 - 2 ,  110 - 3 ,  110 - 4 ) has a redundant PEP ( 120 - 1 - r,    120 - 2 - r,    120 - 3 - r,    120 - 4 - r ). The MAP  200  needs to create only one policy and key, and four mesh Ethernet encryption tunnels. 
         [0102]    Encryption of each site&#39;s Ethernet VPN traffic at a PEP  120  is tunneled into the VPLS tunnel. In other words, Ethernet tunnels are themselves tunneled within the enterprise network. And, VPLS tunnels are themselves tunneled within the service provider LSP tunnels. 
         [0103]    Therefore, Layer 2 frames have the following format: 
         [0104]    Tunnel LSP Label (VPLS Label Original Ethernet Header Encrypted Ethernet Payload) 
         [0105]    LSP and VPLS labels are in the clear. The VPLS label is the label for the enterprise VPLS VPN. The LSP label is the label for the MPLS service provider network to carry its customers&#39; VPLS VPNs. 
         [0106]    The initial Ethernet header is preserved and in the clear. The Ethernet payload is the encryption of the Ethernet frame payload from the CE  160 . 
         [0107]    This approach enables the enterprise customer to leverage the service provider service level agreements (SLAs) and network operations management capabilities. 
         [0108]    Certain modifications and improvements will occur to those skilled in the art upon a reading of the foregoing description. The above mentioned embodiments and examples are provided to serve the purpose of clarifying the aspects of the invention and it will be apparent to one skilled in the art that they do not serve to limit the scope of the invention. All modifications and improvements, including changes in form and details, have been deleted herein for the sake of conciseness and readability but are properly within the scope of the following claims.