text:
US 20080172497 A1 Abstract MPLS networks offering PW or VPLS services may be interconnected with Ethernet networks implemented according to 802.1ah or 802.1Qay. The MPLS network may be a core and offer services to the Ethernet access networks, or vise-versa. Additionally, a mixture of different types of access networks may be interconnected by an MPLS core or an Ethernet core. Both network interworking and service interworking are provided. OAM fault detection may be implemented via maintenance entities extending across the network or end to end depending on the combination of networks and services offered by the networks.
Claims(20) 1. A network including an Ethernet network and a plurality of MPLS networks interconnected by the Ethernet network, the Ethernet network providing a plurality of paths established to interconnect pairs of MPLS networks, wherein Ethernet encapsulated LSP frames received from one of the MPLS networks at an ingress to the Ethernet network are mapped onto the paths at the ingress to the Ethernet network according to classification identifiers associated with the Ethernet encapsulated LSP frames.
2. The network of
3. The network of
4. The network of
5. The network of
6. The network of
7. The network of
8. The network of
9. The network of
10. A network including an MPLS network and a plurality of Ethernet networks interconnected by the said MPLS network, the MPLS network having a plurality of Paths established to interconnect pairs of the Ethernet networks, wherein Ethernet frames received from one of the Ethernet networks at an ingress to the MPLS network are mapped to be forwarded across the MPLS network according to classification identifiers associated with the Ethernet frames.
11. The network of
12. The network of
13. The network of
14. The network of
15. The network of
16. The network of
17. The network of
18. The network of
19. The network of
20. The network of
Description This application claims the benefit of and priority from U.S. Provisional Patent Application No. 60/880,816 filed Jan. 17, 2007 entitled PBB/PBT MPLS INTERWORKING, the content of which is hereby incorporated herein by reference. 1. Field of the Invention The present invention relates to communication networks and, more particularly, to a method and apparatus for interworking Ethernet and MPLS networks. 2. Description of the Related Art The various network elements on the communication network communicate with each other using predefined sets of rules, referred to herein as protocols. Different protocols are used to govern different aspects of the communication, such as how signals should be formed for transmission between network elements, various aspects of what the protocol data units should look like, how packets should be handled or routed through the network by the network elements, and how information associated with routing information should be exchanged between the network elements. Ethernet is a well known networking protocol that has been defined by the Institute of Electrical and Electronics Engineers (IEEE) as standard 802.1. Conventionally, Ethernet has been used to implement networks in enterprises such as businesses and campuses, and other technologies have been used to transport network traffic over longer distances. As the Ethernet standards have evolved over time, Ethernet has become more viable as a long distance transport technology as well. The original Ethernet standard allowed a source address (SA) and Destination Address (DA) to be specified. Over time, several additional fields have been added to allow other values to be designated with respect to a particular Ethernet frame. The original Ethernet frame format specified by IEEE 802.1 includes a source address (C-SA) and a destination address (C-DA). IEEE 802.1Q added a Customer VLAN tag (C-Tag) which includes an Ethertype, TCI information, and customer VLAN ID. IEEE 802.1ad added a provider VLAN tag (S-Tag), which also includes an Ethertype, TCI information, and subscriber VLAN ID. The C-Tag allows the customer to specify a VLAN, while the S-Tag allows the service provider to specify a VLAN on the service provider's network for the frame. These tags also allow the customer and subscriber to specify other aspects which are not relevant to an understanding of the contribution disclosed herein. When a network is implemented using 802.1ad it may be referred to as Q in Q encapsulation or Provider Bridging (PB). A domain implemented using this Ethernet standard will be referred to as a Provider Bridging (PB) domain. The Ethernet standard has evolved to also allow for a second encapsulation process to take place as specified in IEEE 802.1ah. Specifically, an ingress network element to a service provider's network may encapsulate the original Ethernet frame with an outer MAC header including a destination address on the service provider's network (B-DA), a source address on the service provider's network (B-SA), a VLAN ID (B-VID) and a service instance tag (I-SID). The combination of customer MAC addresses C-SA and C-DA with the I-SID are commonly referred to as the I-Tag. A domain implemented using this Ethernet standard will be referred to as a Provider Backbone Bridging (PBB) domain. There are also two other Ethernet standards that have been developed or which are in the process of being developed that may be used in one or more of the domains. Specifically, IEEE 802.1Qay specifies a way for the network elements to switch traffic based on the B-DA and B-VID rather than just forwarding the traffic according to the B-DA. The header of the frames forwarded on an Ethernet network established using this technology is not changed, but the manner in which the information is used is changed to allow forwarding to take place in a different manner. A network domain that forward traffic using this forwarding paradigm will be referred to as Provider Backbone Trunking (PBT). In IEEE 802.1Qay, PBT is commonly referred to as Provider Backbone Bridges-Traffic Engineering (PBB-TE). Thus, the term PBT will be used herein to refer to a network implemented according to this standard. PBB, PB, and the original Ethernet standard use a spanning tree protocol to determine which links should be used to broadcast traffic on the network and which links should be used to forward unicast traffic on the network. To overcome some of the shortcomings of using spanning trees, another Ethernet control plane is in the process of being developed as IEEE 802.1 aq, in which a shortest path routing protocol such as Intermediate System to Intermediate System (IS-IS) or Open Shortest Path First (OSPF) is used in the control plane to establish forwarding paths through the network. Traffic on the domain may then be forwarded based on the B-DA and B-VID in a manner similar to PBT, but from a control perspective a shortest path routing protocol is used instead of a spanning tree to define routes through the network. A domain implemented in this manner will be referred to herein as a Provider Link State Bridging (PLSB) domain. PLSB is described in greater detail in U.S. patent Ser. No. 11/537,775, filed Oct. 2, 2006, entitled �Provider Link State Bridging,� the content of which is hereby incorporated herein by reference. Since PLSB refers to the control plane, it may be used to control forwarding of packets while allowing encapsulation of the packets using PB, PBB, or PBT as described above. MPLS is another commonly used networking protocol. MPLS specifies a way in which a label switched path may be established through a network. When a packet is received at an MPLS Label Edge Router (LER) the LER will determine the destination LER for the packet, attach a label to the packet, and forward the packet to a first Label Switch Router (LSR) on the path to the destination LER. The LSR will strip the label from the packet, look up the label to determine the next label to be applied to the packet and the next hop for the path, and forward the packet onward to the next hop. This proceeds hop by hop across the network to cause the packet to be forwarded across the Label Switched Path (LSP) through the MPLS network. The LSP connects a pair of nodes on the MPLS Network. Since more than one customer may need to transmit traffic between the pair of endpoints, it is desirable to allow multiple customers to share one LSP rather than creating a new LSP for each customer. In MPLS, this is accomplished through the use of Pseudowires. Pseudowires allow traffic for different VLANs to be tagged with a service label, so that traffic from multiple customers, VPNs, etc., can use a common LSP and be differentiated by the egress LER. A service that utilizes a pseudowire will be referred to as a Virtual Private Wire Service (VPWS). In addition to pseudowires, a branching mechanism was developed for MPLS that will allow a given packet that is received at a label switch router (LSR) to be duplicated and passed out of more than one forwarder. A service that utilizes this feature of an MPLS network will be referred to as a Virtual Private LAN Service (VPLS). VPLS uses pseudowires to set up the paths through the network but allows the paths defined by the pseudowires to branch to emulate a Local Area Network (LAN). VPLS uses the signaling protocol described in draft-ietf-12vpn-signaling-08.txt and IETF RFC 4447 to set up pseudowires. The content of each of these protocols is hereby incorporated herein by reference. RFC 4447 introduces the concept of an Attachment Group Identifier (AGI) that may be conceptualized as a VPN identifier or VLAN identifier. The AGI specifies a logical group of forwarders at the egress node, rather than a particular individual forwarder. When implemented in this manner, an attachment circuit associated with a particular VPLS or pseudowire is constructed to include the Attachment Group Identifier (AGI) that identifies the group of forwarders, and an Attachment Individual Identifier (All) that identifies a particular forwarder within the group. In operation, the MPLS network will establish label switched paths through the network using a Label Distribution Protocol (LDP). As part of this process, the LDP will allow the Label Edge Routers (LERs) to exchange AGI/AII pairs that will allow the network to setup the dataplane for the pseudowires. This will set up the forwarders at the nodes to cause the packets to be forward in a specified manner. When a frame arrives at the ingress LER, the ingress LER will check the signaled value of AGI/AII pairs with local information and apply a service label as well as a tunnel label. The tunnel label will be used to forward the frame along the LSP through the MPLS network, while the service label will be used by the egress node to obtain the context of the pseudowire at the egress so that the frame may be sent to the correct set of forwarders. The forwarders will then be used to forward the traffic to the correct customerNVPN as the traffic exits the MPLS network. The AGI/AII pairs are thus used in the signaling phase of establishing the VPLS service by the ingress/egress LERs to coordinate how frames should be handled at the egress to cause the frames to be forwarded to the correct customers. To monitor how a network is operating, such as to perform fault detection, fault isolation, fault confirmation, and other types of fault detection and remediation, an operator may want to send Operation, Administration, and Maintenance (OAM) service frames across the network. Different OAM flows may be used to monitor different aspects or segments of a connection on the network. For example, an OAM flow may be used end-to-end across the network, may be used to monitor the connection within a particular domain, or may be used to monitor other aspects of the connection on the network. A particular OAM flow will be referred to herein as a Management Entity (ME). By monitoring a particular ME the network manager may determine whether connectivity exists across that portion of the network, and if connectivity does not exist, may enable the network manager to isolate the fault on the network. When Ethernet networks and MPLS networks are required to connect together, a network manager may need to be able to define Maintenance Entities across a combined MPLS/Ethernet network As discussed above, both Ethernet networks and MPLS networks have implemented features that will allow traffic from different VLANs to be identified, and which will also allow traffic associated with particular service instances within a VLAN to be identified. When the networks are interconnected, it would be advantageous to allow interworking to occur, either at the network level or service level, so that particular services may be offered end-to-end across the interconnected network. Additionally, from a management perspective, it would be advantageous to enable OAM Maintenance Entities to be defined to monitor aspects of the MPLS/Ethernet network. MPLS networks offering PW or VPLS services may be interconnected with Ethernet networks implemented according to 802.1ah or 802.1Qay. The MPLS network may be a core and offer services to the Ethernet access networks, or vise-versa. Additionally, a mixture of different types of access networks may be interconnected by an MPLS core or an Ethernet core. Where service frames are to be mapped from an ingress Ethernet network to an egress Ethernet network across an MPLS network, the VLAN ID value will be set to correspond to a PW through the MPLS core to reach the particular egress Ethernet network. Where the MPLS core implements VPLS, the destination address may be selected to allow the Ethernet network to select the correct VPLS instance. Where an Ethernet core is used, the Ethernet core may select a tunnel based on the pseudowire label associated with the service frame or based on the B-VID, I-SID, or B-VID and B-DA associated with the service frame. Aspects of the present invention are pointed out with particularity in the appended claims. The present invention is illustrated by way of example in the following drawings in which like references indicate similar elements. The following drawings disclose various embodiments of the present invention for purposes of illustration only and are not intended to limit the scope of the invention. For purposes of clarity, not every component may be labeled in every figure. In the figures: The following detailed description sets forth numerous specific details to provide a thorough understanding of the invention. However, those skilled in the art will appreciate that the invention may be practiced without these specific details. In other instances, well-known methods, procedures, components, protocols, algorithms, and circuits have not been described in detail so as not to obscure the invention. When an Ethernet network and an MPLS network are interconnected, the two networks will pass protocol data units between each other. Depending on how the networks are connected, service instances on one network may be translated to service instances on the other network. A system that interconnects networks of different types in this manner will be referred to herein as �service interworking.� Service interworking implies that a handoff to another domain is such that the other domain identifies its service instance (e.g. PW/VPLS) from service frames, translates service frames to its service instance, and transports them. Transformation of service frames is expected inside the other domain in this case. In an Ethernet/MPLS context, service interworking may occur in various ways. For example, service interworking may occur where the MPLS network identifies its service instance such as PW or VPLS from the I-SID or other service identifier in use on the Ethernet network. Another way of interconnecting two domains is for the two domains to encapsulate service frames for transport without transforming the service frames. An interconnection of this nature will be referred to herein as network interworking. In an Ethernet to MPLS context, Network Interworking may occur in various ways. For example, network interworking may occur where the MPLS network identifies its service instance such as PW or VPLS from the VLAN ID in use on the Ethernet network. There are many interworking cases that are possible, due to the myriad different types of Ethernet and the several different ways in which an MPLS network may be instantiated. Several ways of interworking MPLS and Ethernet networks are set forth below. Since there is a large deployed base of MPLS networking gear, an emphasis on selecting ways to interwork MPLS and Ethernet networks has been provided that will minimize the amount of modification required on the MPLS networking gear. The metro networks may be implemented using MPLS and the core network may be implemented using Ethernet, as shown in Additionally, two or more of the metro networks may be implemented using a common control plane, so that the two metro networks are to be considered to be one logical network. Interworking another network with the common metro networks may need to take into account the fact that the two metro networks are implemented using a common control plane so that flows of data may be commonly implemented by the metro networks without alteration by the intervening core network. Thus, many different network scenarios are possible and, depending on the particular implementation, the manner in which the networks are interworked may vary as well. In The metro network 14 in The core network in the embodiment of In the example shown in In the embodiment shown in In a scenario such as the one shown in Accordingly, from a network interworking standpoint, the PBT domain requires the MPLS domains to use virtual links (i.e. VLANs) such that an MPLS node only uses a virtual link such that it is dedicated for a single peer MPLS domain only. By causing a particular MPLS domains to use a different VLAN value or set of VLAN values for each of the other MPLS domains, the ingress nodes on the PBT core may map the VLAN values to PBT trunks in the PBT core to cause the frames to be forwarded to the correct MPLS domain. Thus, for example, assume that VLAN 1 was used by MPLS domain X for traffic intended for MPLS domain Y, and that VLAN 2 was used by MPLS domain X for traffic intended for MPLS domain Z. By using a different VLAN ID for each of the destination MPLS domains, the ingress node on the PBT core may select a trunk to carry the traffic to either MPLS domain Y or MPLS domain Z by looking at the VLAN ID associated with the frame. Where different PBT trunks are required to have different traffic engineering requirements, more than one PBT trunk may be implemented between the same set of metros. Thus, optionally, a set of VLAN values may be used to designate a set of PBT trunks extending between the pair of metros. If the MPLS domains are not able to implement virtual interfaces, i.e. implement different VLAN IDs for different destination MPLS domains, then a PBB core network should be used instead of a PBT core network. Alternatively, the S-PEs may use different ports (physical interface) for each metro such that the PE is able to map traffic to different PBT trunks to different metros based on the ingress physical interface. If the networks shown in In the Example shown in The PEs offer PBT trunks, such that frames entering the PBT network either carry tags that are dedicated to connection a MPLS domain with only a single other domain (i.e. dedicated virtual interfaces as described above) or carry the S-PE's DA with a common tag. The PE will map frames received from the S-PE to a PBT trunk based on the tag associated with the frame, or uses the VLAN and DA to identify the PBT trunk. For resiliency and loop avoidance, the PEs may establish both primary and backup trunks. A packet may be provided with a particular quality of service in the MPLS network. For example, the access switch U-PE or MPLS access switch (N-PE) may set the LSP Exp bits in the MPLS header to indicate a particular class of service. To allow the Ethernet network to afford the same quality of service to the packet as it traverses the core network, it may be desirable to map the LSP Exp bits to the B-Tag p-bits in the Ethernet header. The p-bits are three bits specified in the B-Tag which are defined by IEEE 802.1p to be used to indicate a quality of service. Optionally the p-bits associated with the Ethernet header that is applied to the packet as it traverses the PBT network may be set to provide a quality of service akin to that associated with the packet in the MPLS network. As shown in In the example shown in In addition to the LSP label and PW label, the N-PE will assign a link layer Ethernet header (transport header 506) that will be used by the network element to forward the packet toward the next hop on the MPLS network. Each hop on the MPLS network will remove the transport header, read the LSP label, swap the LSP label with a new LSP label, and forward the packet toward the next hop on the MPLS network. The manner in which the MPLS network operates is not intended to deviate from standard practice. When the S-PE receives the packet it will perform a label swap as normal and forward the packet over the LSP that passes through the PBT core network. The PE, upon receipt of the packet, will determine the PBT trunk to be used to carry the packet as described in greater detail above. For example, the PE may read the B-DA associated with the transport header or the B-VID contained in the B-TAG to determine the PBT trunk to be used to carry the packet across the PBT core network. The PE will then encapsulate the packet with a header 508 that will be used to transport the packet across the PBT core network. The header, may be a standard 802.1ah PBB encapsulation header that will be used to transport the packet across the PBT trunk on the PBT core network. When the packet is received at the egress from the PBT network, the PE will strip off the header 508 and forward the packet to the S-PE3. The S-PE 3 will strip off the transport header 506, read the LSP label, and forward the packet toward N-PE4. Where the LSP over the PBT core and the LSP over the MPLS access network Y are different LSPs, the S-PE3 will map the packet from one LSP to the next before forwarding the packet toward the LPS on MPLS access network Y. From a resiliency standpoint, the PBT network may implement primary and backup PBT trunks, so that the PBT trunks may be considered resilient. The MPLS domain can run its own resilient PWs, which are transparent to the PBT core. The nature of the interconnect determines the level of visibility and impact of any failure. The solution described herein, in connection with The PEs offer E-LAN service connectivity across the PBB core. E-Line may be considered a special case of point-to-point E-LAN connectivity across the PBB core. Frames entering the PBB network carry the S-PE's DA and possibly a tag. PEs offer E-LAN service corresponding to the tag. One example of the tag that may be used in connection with this is the B-VID contained in the B-Tag. When a packet arrives at the PE, the PE will use the B-VID and B-DA (indicating S-PE DA) from the transport header 606 to identify a service instance associated with the packet, and then encapsulate the packet for transport across a PBB tunnel through the PBB core network. As mentioned above with respect to the PBT core network, when a PE receives a packet it may be desirable to map the LSP Exp bits to the B-tag p-bits. This mapping is advantageous as both the EXP bit field and the p-bit field are three bits long, so that each accommodates 8 classes of service. The PBB network may implement either a spanning tree or a link state protocol to control the PBB network. For example, it is common for PBB networks to implement a spanning tree protocol to implement resiliency and loop avoidance. Alternatively, a link state protocol such as OSPF or IS-IS may be used to control the network and provide resiliency and loop avoidance. When the packet is received at the S-PE the S-PE will either forward the packet along the LSP onto the PBB network (where the LSP exists end-to-end between the N-PEs) or will translate the LSP from an LSP segment on the MPLS access network to an LSP that extends across the PBB core network. Similarly, the PW label may remain the same on the various LSP segments or may be translated by the S-PE if the packet is put onto a new LSP segment at the S-PE. The S-PE will then apply a link header to transport the packet to PE1. From the S-PE standpoint, regardless of whether the LSP extends from end-to-end or there are multiple LSP segments, the next hop on the LSP as seen by the S-PE on the first MPLS network is the S-PE on the second MPLS network. For example, on the path shown in From a resiliency standpoint, the PBB tunnels are resilient assuming that the PBB core is running either xSTP or a link state protocol on the control plane. Similarly, the MPLS domain can run its own resilient PWs which are transparent to the PBB core. The nature of the interconnect between the MPLS networks and the PBB core will determine the level of visibility and impact of a failure on the network. One benefit of using a PBB core to interconnect multiple MPLS domains is that the PEs on the PBB core are transparent to the PW labels. Stated another way, the MPLS network is not aware of the PBB core and can implement PWs that span across the PBB core without requiring modification to the manner in which the S-PEs operate. Additionally, the PEs on the PBB core are not required to operate differently but rather can implement normal forwarding behavior and use the VID and DA of the transport header applied to incoming packets to identify the I-SID and PBB tunnel to be used to transport the packet across the PBB network. Like the previous example, however, the PE will add a 22 byte header to each frame of the packet which increases the overhead associated with transmitting the packet across the PBB network. Depending on the nature of the traffic this may or may not be a concern. Additionally, the PBB network is still required to implement one or more spanning tree instances or a link state protocol to avoid loop formation and for resiliency. The previous two examples, shown in To implement VPLS services, the N-PEs will establish a mesh of PWs interconnecting all of the N-PEs with all of the S-PEs. The S-PEs will also support spokes to all other S-PEs on all other metros. When the N-PE receives a packet, it will encapsulate the frame with a PW label and LSP label and forward the packet across the PW to the S-PE. The S-PE replicates the frame at handoff, if the service instance spans more than one remote metro, and forwards multiple copies of the frame across the PWs to each of the S-PEs on each of the remote metros. The PEs on the PBB/PBT network offer E-LINE/E-LAN service for connectivity across the PBB/PBT core. Frames entering the PBT/PBB core have a link level transport header including the DA of the intended S-PE on the remote metro network. The transport header may also include a VLAN ID or other tag. The PE uses the VLAN or the VLAN and MAC (DA) to identify the service instance in the PBB/PBT network that should be used to transport the packet across the PBB/PBT network. The PE will encapsulate the packet in a PBB/PBT tunnel (using the PBB encapsulation process of 802.1 ah, as described above in greater detail) and forward the packet across the network. Thus, the interworking between PBB/PBT networks and the MPLS network may be implemented, from a PE standpoint, in the same manner regardless of whether the MPLS network is offering a PW service or VPLS service. Within the MPLS networks, a reservation protocol such as RSVP may be run to implement redundant spokes between each pair of metros. RSVP allows traffic engineered paths to be established through a network. Hence, RSVP may be used to create two separate paths between each pair of N-PE/SPE to allow for redundant paths to be created within the MPLS networks. The resilient paths within the metro are transparent to the PBB/PBT core. As a summary, when a PBB or PBT network is implemented as the core network, and MPLS networks are used to implement the metro networks, the PE must recognize Ethernet frames encapsulating the MPLS payload from the MPLS networks. The PE may use the VLAN or the VLAN and DA from the transport header applied by the S-PE to map the packets to appropriate PBB or PBT tunnels through the network. Where the SPEs are able to implement VLAN sets containing one or more VLAN per remote metro, the PE may identify the PBB/PBT tunnel from the VLAN and map the packets to the appropriate PBB/PBT tunnel according to the VLAN. Where the SPEs are not able to implement one VLAN per remote metro, the PE may use the DA along with the VLAN to map the packets to the appropriate PBB/PBT tunnel. Optionally, the PE may also map the LSP EXP bits to PBB/PBT tunnel p-bits to allow the same quality of service features to be provided end-to-end across the MPLS/PBB/MPLS or MPLS/PBT/MPLS network. When a PBB/PBT trunk fails, an alarm indication signal (AIS) may be transmitted toward the MPLS domain on a per-VLAN basis. This will allow the alarm indication signal to be propagated to the MPLS domain on the virtualized links to enable the MPLS domain to failover traffic to a backup path. By implementing AIS signaling from the PBB/PBT domain to the MPLS domain, the MPLS domain is not required to run end-to-end maintenance entities over the PBB/PBT domain, and may thus treat the PBB/PBT tunnels as a link. Implementation of this feature would require the S-PEs to be configured to implement Ethernet OAM signaling to allow the S-PEs to interpreted receipt of an AIS as a failure indication rather than a generic Ethernet frame. Accordingly, implementation of this feature may require modification of the S-PE to enable it to be implemented on the network. From a network interworking perspective, the Ethernet domain would consider the MPLS domain as a server domain and would not peer with it. Ethernet domain nodes would peer on either side of the MPLS domain. The Ethernet domain would transmit and receive Ethernet encapsulated frames containing native payload. Optionally, the S-PE nodes may transmit PW encapsulated frames. MSEs on the MPLS domain would receive Ethernet frames which would need to be mapped to PW or VPLS service instances. If the MPLS domain implements PW service, interworking can be accomplished by requiring the Ethernet domains to use correct B-VIDs to identify egress Metro domains, since the MSE is not able to map B-MAC addresses into PWs. Where the MPLS domain implements VPLS service, the MSE similarly determines the VPLS service instance based on the B-VID in the case of network interworking. Where the networks are to be interworked at the service level, the Ethernet domain will consider the MPSL domain as a peer domain. The Ethernet domain transmits and receive Ethernet encapsulated frames. The MPLS domain receives Ethernet frames and de-encapsulates the frames to have visibility to the native service payload. Accordingly, service interworking requires the Ethernet domain to support PW signaling, unless static configurations are allowed at the edge of the domains. The PE offers either a port-based E-line or a tagged E-line service. A port-based E-line service encapsulates all frames received on a particular port as a particular service instance. Tagged E-line service, by contrast, encapsulates frames received with a particular VLAN set, including one or more VLAN IDs, into a particular service instance for transmission over the PBT network. The PE will then encapsulate the frames into a PBT trunk for transmission across the PBT network. The I-SID is end-to-end unique across the combined Metro domains and, hence, the I-SID may be used end to end to identify the service instance associated with the frame. According to an embodiment of the invention, the B-VIDs assigned to frames are allocated as belonging to a particular metro pair. Thus, in The MPLS core provides PW instances interconnecting each pair of metros. A PW instance is created per PBT B-VID PW instances can provide the same traffic profile as the PBT trunks, which allows the same QoS to be implemented in the core network as in the metro networks. For example, as shown in According to an embodiment, the MPLS core implements a PW for each PBT VID. The S-PE does not need to maintain any additional mappings and forwards regular PBT frames to the MPLS core. For each metro, each PBT B-VID is allocated such that it connects to a single other metro. Within the MPLS core PWs are implemented between each metro such that traffic may be mapped according to the PBT B-VID to a PW in the MPLS core. When the frame is received at the PE, the PE will perform PBB encapsulation specified in 802.1ah to add an I-SID, Ethertype, B-TAG, Ethertype, B-SA and B-DA. The B-SA is the MAC address of the PE that received the frame from the customer, and the B-DA is the destination MAC address of the PE on the PBT domain. According to an embodiment, the B-TAG may be selected to include a B-VID that specifies the destination Metro network where the destination network element is located. Selecting the B-VID corresponding to the destination network allows the MPLS network to select a PW for the frame for use in transporting the frame across the MPLS network. The PE will perform the PBB encapsulation and forward the frame across a PBT tunnel to the S-PE, which will forward the frame to the MSE on the edge of the MPLS network. The MSE will read the B-VID and use the B-VID to select a PW for the frame. The MSE will then attach a PW label and LSP label and forward the frame across the MPLS network. The MSE may also apply a further link-layer Ethernet header to the frame which will be stripped and replaced at each hop through the network. When the PE receives the packet, it will strip off the customer header 1106 and add a provider header 1108. The provider header 1108 includes a B-TAG (which includes a B-VID), an Ethertype, and the provider source and destination MAC Address (B-SA and B-DA). The B-VID will be selected in this embodiment, as with the last embodiment, to identify the egress Metro network that contains the destination network element. The ingress PE on the PBT network will then forward the frame across a PBT trunk to the S-PE. The S-PE will forward the frame to the MSE, which will use the B-VID 1110 to identify the PW, and attach a PW label 1112 and LSP label 1114 to the packet. The MSE will then forward the packet across the LSP to the destination metro network. Alternatively, where the MPLS network is implementing VPLS, the MPLS network would implement a VPLS per B-VID, and make forwarding decisions based on B-DA. The egress MSE will strip the PW and LSP labels off the packet and forward the packet to the S-PE of the egress metro. The Egress metro will forward the packet across the PBT trunk in the PBT network to the destination. From an OAM standpoint, PBT trunk OAM maintenance entities may be monitored on an end-to-end basis. When a PBT trunk fails, the head-end can switch the services, represented by I-SIDs onto backup PBT trunks. When a PW fails, the MSE can notify via AIS on the PBT trunk, if the MSE supports Ethernet OAM. One of the advantages of interworking PBT metro networks with an MPLS network are that the S-PEs are not required to introduce modifications into the data path to implement the handoff to the MPLS network. Additionally, the S-PEs do not need to maintain visibility to the I-SIDs or individual service instances. End-to-end trunk level OAM is possible and is independent of the MPLS core. Additionally, end-to-end service level OAM is also possible. On the other hand, the end-to-end PBT OAM does not scale well. The metros are also not autonomous, and need to have visibility into each other's address space. OAM scaling issues, e.g. via AIS, can be addressed but require Ethernet OAM support in the MSEs. Additionally, when the MPLS network is implementing VPLS, a MSE Virtual Switch Instance (VSI) is required on a per-port basis, and the MSE will make forwarding decisions based on the B-DA. In the previous description it was assumed that the S-PE would forward the packets from the PBT network to the MPLS network without performing B-VID translation. It is possible to implement a mapping at the S-PE that would allow B-VIDs to be translated so that the B-VID in use on the PBT network is not the same as the B-VID used on the MPLS network. This has implications with connectivity fault management, however, the reverse VLAN ID may be carried in the CFM payload. Thus, if the S-PE is performing B-VID translation, the mapping would need to take place within the CFM payload or another mechanism would need to be implemented to cause the correct B-VID for the reverse path to be carried in the CFM payload. The PBT networks may be part of the same domain or, alternatively may be separate domains. Where the PBT networks are separate domains, for example if PBT metro X and PBT metro Y implement separate control planes, then the PBT trunk segments will not extend end-to-end across the network. Rather, the S-PEs will maintain a mapping on a per-ISID basis to map traffic between trunk segments. For example, as shown in When the S-PE receives the frame it will determine the PBT segment across the MPLS core. As with the example discussed above, each metro allocates B-VIDs such that a particular B-VID is used only to connect to one other metro. The S-PE maintains a mapping of PBT segments and maps the traffic to the next PBT segment. The B-VID used for the segment is selected such that the B-VID will cause the frame to be forwarded across the MPLS core to the correct metro. When the MSE receives the frame, it will read the B-VID and place the frame onto a LSP/PW through the core to the correct metro by assigning a PW label and LSP label. The egress MSE will strip off the PW and LSP labels and forward the frame to the S-PE on the metro. The S-PE will either perform a second mapping to map the frame to a PBT trunk within the second metro or will directly forward the frame onto the trunk within the metro. This second option may exist where the PBT trunk segment extends from the second metro across the MPLS core. Where the frame is mapped to different trunk segments, the PBB header or portions of the PBB header such as the B-DA and B-SA, B-VID, and I-SID may be changed so that these values are unique within each PBT tunnel. For resiliency, PE pairs maintain primary and secondary trunks, which are monitored via connectivity check messages. The S-PE at the edge of each metro provides the interworking function. It is I-SID aware and maintains, on a per-I-SID basis, a mapping between trunk segments that extend over the PBT metro and the MPLS core. The mapping is maintained in both directions so that the S-PE is able to map frames from a PBT trunk on the metro to a PBT trunk on the core, and conversely from a trunk on the core to a trunk on the metro. The S-PE thus provides a UNI functionality to map frames to trunks on the PBT network. The MSEs will map frames to PWs on a per-B-VID basis, so that the S-PE is not required to modify the format of the frames when passed to the MSEs. Alternatively, the S-PE may offer PW UNI to participate in PW signaling and apply PW labels to frames before they are forwarded onto the MPLS core. Encapsulation of frames with different PBT domains interconnected with an MPLS core is the same as the encapsulation process described above in connection with a unitary PBT domain extending across an MPLS core. However, since the S-PEs are mapping between PBT tunnels, the destination address of the packet on each segment will be set to be the terminating device on that segment. Thus, for example in Each PBE trunk segment is monitored on an end-to-end basis by an OAM Maintenance Entity (ME). As shown in If a full mesh interconnect is in use (see If a dual homed interconnect is used, as shown in Some of the advantages associated with interworking split PBT metro domains with an MPLS core are that the S-PE is not required to introduce any modifications to the data path. Thus, a normal S-PE should be able to be used to implement an interworking of this nature. Additionally, OAM scaling issues are not severe, and end-to-end service level monitoring is possible. The metros are also able to remain autonomous without visibility into each other's address space, while a full mesh of connectivity between metros may be implemented across the MPLS core. On the other hand, S-PEs are required to be I-SID (service instance) aware. The S-PEs need to change PBT trunks for I-SID flows and the S-PEs need to be configured to map I-SIDs to PBT trunks in the Metro and over the core. End-to-end trunk level OAM is not possible, and requires notification at the I-SID level. If the customer is implementing OAM as well, and is not using S-tagged or C-tagged frames, or if the customer S-Tag or C-Tag is removed during the 802.1ah encapsulation process, then the ME level space may need to be split so that both the customer and the provider may use the same ME level space. In the previous example, the S-PE was described as mapping PBT trunks on a per-I-SID basis. Optionally, where the I-SID is not end-to-end unique, the S-PE may also map I-SIDs so that different I-SID values may be used for the same flow in each of the trunk segments. In this instance, the S-PE would receive a frame, read the I-SID to determine the next PBT trunk segment, and also use the I-SID to determine the I-SID to be used as a service identifier on the next PBT trunk segment. Similarly, the S-PE may map PW labels between domains, for example where PW over PBT is being implemented (see It is also possible to implement PBB metros interconnected via an MPLS core. In this embodiment, the Ethernet access switch (U-PE) hands off Ethernet frames to the metro access switch (PE). The PE uses the VLAN ID (VID) to identify the service instance (I-SID). The PE encapsulates the frame in a PBB tunnel and ships it across the PBB network. The I-SID is end-to-end unique. The B-VID and multicast address assignments that are used to create one or more PBB tunnels may be implemented via traffic engineering. Resiliency is provided by redundant interconnects and by running xSTP across a single domain joining the several metros. The MPLS core provides a VPLS service instance per B-VID that it is exposed to, and forwards traffic based on the B-DA. When offering VPLS, the MSE will provide bridged Virtual Switch Instance (VSI) (not per port VSI) such that it can switch between different ports. When replication needs to occur across the WAN, the MSE does so similar to VPLS. The S-PE is not required to maintain a special mapping in this case. Additional details associated with PBB metros and an VPLS core are contained in U.S. patent application Ser. No. 11/540,023, entitled Method And Apparatus For Transporting Ethernet Services, filed Sep. 30, 2006, the content of which is hereby incorporated herein by reference. In a network including PBB metros and an MPLS core, the PBB tunnels can be monitored on an end-to-end basis. When an S-PE or MSE or NNI or link within a metro fails, the spanning tree in use on the metro or the link state protocol (where the Ethernet metro is a link state protocol controlled Ethernet network) can address the failure via redundant paths. If the failure leads to network segmentation, the PBB tunnel monitoring will be able to detects this, however rectification of the problem and restoration would require manual intervention. Where failure occurs in the MPLS core, the MPLS network may have no way to signal to the xSTP instance in the metro that the failure has occurred. Thus, the xSTP will not be able to initiate restoration/reconvergence for an unacceptably long period of time or may have an unacceptable detection time. To mitigate this, a monitoring domain may be implemented at the S-PEs to allow the S-PEs to implement a PBB segment Maintenance Entity (ME) across the segment of the PBB tunnel that extends across the MPLS core network. If a PBB segment ME indicates failure, the S-PE should trigger xSTP convergence. Since the failure in the MPLS domain may not be propagated into the PBB network, when the connectivity fault management (CFM) being run across the PBB segment between the S-PEs (which spans the MPLS domain) indicates a failure in the MPLS domain, the S-PEs should initiate xSTP convergence assuming a failure on the PBB segment. This allows the network to reconverge quickly upon detection of a failure in the MPLS network to allow a new set of PBB tunnels to be established that can span the MPLS network and avoid the failed tunnel. The S-PE is not required to be modified to enable PBB networks to interconnect with MPLS core network and thus can implement an NNI handoff to the MPLS core network. The S-PEs do not need to maintain visibility to the I-SIDs or to individual service instances. A full mesh of WAN connectivity may be implemented in the MPLS core network between all pairs of metros. Additionally, end-to-end service level monitoring is possible as is segment monitoring across the MPLS core. However, since the PBB networks are implemented as a single large metro domain, running a single xSTP spanning instance or link state protocol instance, the large domain may make multicast domain difficult to manage. Additionally, the metros are not autonomous and, thus, need to have visibility into each other's address space. The metros are also required to implement some form of loop avoidance technique, such as xSTP. By using a different physical interface on the S-PE for each destination metro, the MSE can implement a PW service instance on a per-port basis. Alternatively, the MSE may implement a PW service instance on a per-B-VID basis. The S-PE implements the equivalent of a Virtual Switch Instance, since the S-PE is responsible for replicating frames to multiple ports or outputting the frame using multiple B-VIDs. Thus, the MSE will receive the frame multiple times (once for each destination Metro) and map the frames to PWs through the MPLS core to the destination metros. Where a link state protocol is in use on the PBB network, the S-PE may view different interfaces as regular bridged ports and may use inherent bridge replication. Resiliency, in this instance, may be provided by implementing redundant interconnects from the S-PE to the MPLS network and running a common link state protocol instance across the several PBB networks. From an encapsulation perspective, the service frame (which may or may not contain the C-Tag and S-Tag) will be encapsulated using 802.1ah by PE2. Since the various PBB metros are implementing a common control plane, PE will have visibility into PBB metro Y's address space and may create a provider MAC header that includes the MAC address of PE4 as the destination MAC address (DA=PE4). Thus, the 802.1ah MAC header need not be changed as the frame traverses the network. When the frame is passed to the MSE at the ingress to the MPLS core network, the MSE will map the frame based on the port on the S-PE over which it was sourced, or based on the B-VID, and apply a PW label and an LSP label to transport the frame across the MPLS network. From a resiliency standpoint, the PBB tunnels can be monitored on an end-to-end basis. when an S-PE, MSE, NNI, or link within the metro fails, the link state protocol being run on the PBB metro may address the failure in a normal manner (i.e. via a redundant PBB tunnel). If the failure leads to network segmentation, the failure will be detected by the end-to-end Maintenance Entity, but correction will require manual intervention. If a failure occurs in the MPLS core, the MPLS network may not be able to signal the failure to the PBB metro networks. This may result in the PBB networks being unable to initiate reconvergence/restoration within an acceptable period of time. Accordingly, the S-PEs may implement a PBB segment ME across the MPLS core to allow the S-PEs to detect a failure within the MPLS network. Upon detection of a fault on the PBB segment ME extending between the S-PEs across the MPLS core, the S-PEs may initiate xSTP reconvergence or link state protocol reconvergence to allow the PBB network to route traffic around the failure. Thus, if the PBB segment ME indicates failure, the link state protocol should be notified to trigger convergence. This allows reconvergence to be initiated without explicit notification of the failure from the MPLS network to the PBB networks. The S-PE does not require modification to the data path to implement handoffs to the MPLS network. The S-PEs also are not required to maintain visibility to the I-SID or individual service instances. A full mesh of connectivity between metros may be implemented in the MPLS core, and end-to-end service level monitoring is possible. On the other-hand, implementing one big metro domain across the several metro networks means that the multicast domain is concomitantly large and, hence, difficult to manage. Metros are also not autonomous, and need to have visibility into each other's address space. A loop avoidance technique, such as reverse path forwarding check implemented in connection with a link state protocol such as Open Shortest Path First (OSPF) or Intermediate System to Intermediate System (IS-IS) is also required. In addition to implementing the PBB metros as one domain, it is possible to run different xSTP or link state protocol control instances in each of the PBB metros to allow the metros to be independent. Where split PBB metros are interconnected across an MPLS domain, the PBB metros will implement PBB tunnels between the PEs and S-PEs. The I-SID in this case may be end-to-end unique or may be metro-specific. Resiliency is provided by redundant interconnects between the PBB metros and the PLSB core, and by running xSTP within each domain�i.e. each PBB metro runs its own xSTP instance. The MPLS core provides VPLS service instance per B-VID that it is exposed to. B-VLAN IDs are allocated based on per-connectivity required across metros. Thus, if there are five metros, 24 VPLS instances will be required to interconnect the metros (10 connecting each metro pair, 9 connecting 3 each, 4 connecting 4 each, and 1 connecting all of the metros). When a frame is received at the PE in metro X it will be encapsulated using 802.1 ah and mapped to a PBB tunnel within metro X. If the C-DA of the frame that is received by the PE is unknown to the PE, the PE will map the frame to a multicast MAC DA in the B-VID tunnel (PBB tunnel). The S-PE terminates the B-VID tunnel, and maps the B-VID tunnel across the WAN, which means that the S-PE maintains a mapping between I-SID or C-DA and corresponding B-VID tunnel and B-DA for use in across the MPLS core in a manner similar to the mapping maintained by the PE. Additionally, the receiving S-PE will map the received frame to a B-VID tunnel across Metro Y. Within the MPLS core, the MSE treats the frames like regular Ethernet frames. Since the MPLS core has implemented VPLS service instances on a per-B-VID basis, the MSE will map the frame using the B-VID to a VPLS service instance and forward it across the MPLS network. The Ethernet frames will be received by one or more egress metros to be forwarded onto those metro networks. Thus, in this embodiment, the S-PE maintains a mapping of I-SID and C-DA to B-VID and B-MAC in both directions. The S-PEs also run xSTP or a link state protocol in the control plane and in the MPLS WAN using distinct V-LAN space. The S-PE will also correlate failures between the Metro and MPLS core domains to block/unblock forwarding states depending on the state of the networks. From a resiliency standpoint, the PBB domain will be able to detect and correct for failures that occur within the PBB domain. The MPLS domain may have no way of signaling failures that occur in the MPLS core, however. Thus, the S-PEs may implement OAM maintenance entities across the core to detect for failure in the MPLS core and initiate reconvergence in the PBB network upon detection of a failure on the PBB segment maintenance entity. Since the PBB domains are separate domains, the S-PE is required to map flows between PBB tunnels. Accordingly, the S-PE will map flows from one PBB tunnel to the other PBB tunnel based on the I-SID or the C-DA. Thus, the S-PE maintains a mapping to enable it to perform the mapping between I-SID and target PBB Tunnels. The S-PE may also translate other values, such as B-VID, to allow for independent B-VID management in different domains. Similarly, the S-PE may maintain a table of ingress multicast DA and egress multicast DA to allow for translation of multicast DA between domains. This may be particular useful where the metro domain allocates multicast DAs using an algorithm different than that used by the core PLSB domain, i.e. when the core uses an I-SID unique multicast DA. The S-PE is also required to support control xSTP instances, which allows the S-PE to block data forwarding for particular sets of VIDs. Split PBB domains may be implemented and interconnected by an MPLS network providing PW service, where the S-PEs are not configured to perform B-VID translation. In this instance, the S-PEs would run a control instance such as xSTP or a link state protocol, to enable the S-PEs to implement a common control plane. This allows the S-PEs to block data forwarding for particular sets of B-VIDs. In this embodiment, the S-PE will switch flows from PBB NNI to PBB NNI based on I-SID. The S-PE will thus maintain a mapping of I-SIDs to PBB tunnels and maintain a table of ingress multicast DA and egress multicast DA to allow translation of multicast DA between tunnels. This is needed where the metro domain allocates multicast DA using an algorithm that is different than the algorithm used by the core domain, which uses I-SID unique multicast DAs. Optionally, the S-PE may allow B-VID translation between tunnels so that independent management of B-VID may occur in the different domains. For resiliency, the S-PE should implement segment PBB tunnel maintenance entities to detect faults on the MPLS network, and trigger xSTP or link state protocol reconvergence upon detection of a failure. Additionally, the S-PE may allow for I-SID translation between PBB tunnels to allow for independent management of I-SIDs in different domains. Implementing split PBB domains reduces the size of the xSTP or link state protocol domains, which makes the domains more manageable from a control standpoint. Additionally, the metros are autonomous, so that they do not need to have visibility into each other's address space except at the S-PE. A full mesh of connectivity may be supported in the core network between each pairs of metros. Additionally, end-to-end service level monitoring is possible. However, the S-PEs are required to be I-SID aware and C-MAC aware. The S-PE needs to provide a mapping between PBB tunnels and B-MACs based on the I-SID and C-MAC. It also requires coordination of failures within different instances of xSTP or link state routing protocol at the S-PE. The solution also requires the use of some loop avoidance technique, such as implementation of xSTP or link state routing protocol in the control plane. In the embodiment shown in An end-to-end PW may be established manually via a network management plane or via signaling in the control plane. If MS-PW signaling is used, then the PE and N-PE would serve as terminating PEs (T-PEs) and the S-PE and MS-PE would serve as switching PEs (S-PEs). Optionally the MSE can also act as an S-PE. When the S-PE receives the packet, it will remove the MAC header and use the PW label to map the packet to a PBT trunk across the MPLS core. The S-PE thus maintains a mapping between PBT trunks in either direction based on PW label. The MPLS core will provide VPLS instances for each B-VID that it is exposed to, which would thus not require the metro to make any modifications to frames across the NNI. Thus, the B-VID of the PBT trunk across the MPLS core may be selected according to the VPLS instance that is to be used to transport the packet to one or more destination metros. When the MPLS metro receives the packet, the MS-PE on the MPLS metro (MS-PE3 in From a resiliency standpoint, each PBT trunk may be monitored on an end-to-end basis by implementing a PBT trunk maintenance entity. In the MPLS domain the path may be monitored via an MPLS LSP maintenance entity. The end-to-end service may also be monitored using a PW Virtual Circuit Connection Verification (VCCV) or via MS-PW OAM. Advantageously, no modifications are required to the data path at handoff. Additionally, the PWs that are required to be set up in the MPLS core scale on the order of O(n), where n is the number of Metros connected to the MPLS core. Also, a full mesh of connectivity may be implemented between the metros. The metros are autonomous, and thus do not need to have visibility into each other's address space. Additionally, end-to-end service level monitoring is possible. On the other hand, S-PEs are PW label (service instance) aware. In addition to PBT trunk configurations, S-PEs need to be configured to map PW labels to the PBT trunks in both directions (into the PBT metro and into the MPLS core). End-to-end trunk level OAM is not possible, and requires notification at the PW level. The MS-PE will also be required to support a static PW UNI, if MS-PW signaling is not used. In summary, the S-PEs switch flows from PBT-NNI to PBT-NNI (between PBT Trunks) based on the PW label (where PW over PBT is used in the PBT network). The PE and S-PE also support VCCV OAM on the PW to monitor the service on an end-to-end basis. When the S-PE detects a failure of a PBT trunk, it will determine the PWs affected by the failure and generate an Alarm Indication Signal (AIS) at the PW level on the corresponding PBT trunk. Optionally, trunks may be implemented as PBT trunk groups for monitoring purposes. The S-PE may implement several additional features to reduce the amount of interdependence between the domains. For example, the S-PE may allow PW label translation between PBT trunks, to allow for independent management of I-SIDs in the different domains. Additionally, the S-PE may implement B-VID translation between PBT trunks and may also implement DA translation between PBT trunks. This solution requires the MS-PE to support a static PW UNI. In the scenario shown in End-to-end PWs may be established by manual provisioning at the management plane or by PW signaling in the control plane. If MS-PW signaling is used, then the PE and N-PE would serve as terminating PEs and the S-PE and MS-PE would serve as switching PEs (S-PEs). The MSE may also act as a switching PE if desired. The S-PE will remove the PBT trunk MAC header and apply a link level MAC header and forward the packet to the MSE. The MSE will strip off the link MAC header, read the PW label, and apply a LSP label to forward the packet across the MPLS network. The egress MSE will remove the LSP label, read the PW label, and apply a link level MAC header to forward the packet to the MPLS metro Y. The MS-PE will remove the link level MAC header, read the PW label, and apply a LSP label to forward the packet across the MPLS metro network Y. The egress N-PE will remove the PW label and forward the packet to the U-PE. From a resiliency standpoint, each PBT trunk ME may be monitored on an end-to-end basis in each domain. In the MPLS domain, the trunk may be monitored by monitoring the MPLS LSP. The end-to-end service may also be monitored by using a PW Virtual Circuit Connectivity Verification and MS-PW OAM. The scenario has similar advantages/disadvantages as the scenario described above with respect to In the previous two scenarios, it was assumed that the PW was maintained end-to-end. Optionally, the PW may be switched (mapped) at one or more locations along the end-to-end path to enable the domains to remain independent. For example, the S-PE may map PW labels in addition to mapping packets to/from PBT tunnels on a PW basis. This allows different PWs to be used in the PBB/PBT metro X than are used in the MPLS core. Similarly, the MSE may map PWs to allow different PW labels to be used in the interconnect than are used in the MPLS core. Likewise, the MS-PE may map PW labels to allow different PW labels to be used in the MPLS metro Y than are used in the MPLS core. Thus, many different mappings may occur depending on which nodes on the network are configured to map parameters for the packet as the packet is passed along a path on the network. The network elements described above, such as the PE and S-PE, as well as the MSE and N-PE, are all conventional network elements. The network elements are programmed, however, or have hardware implementations, that will enable them to perform the functions described above to place traffic on tunnels through the network and to switch traffic from tunnel segments. Similarly, the network elements include software, hardware, and/or firmware that will enable the network elements to participate in OAM maintenance entities and other OAM flows to enable appropriate monitoring to occur as described in greater detail above. Thus, the invention is not limited to any particular hardware implementation as many different network element hardware platforms have been created over the years and are likely to be created in the future as network elements continue to evolve. Thus, it will be apparent to a skilled artisan that all logic described herein can be embodied using discrete components, integrated circuitry such as an Application Specific Integrated Circuit (ASIC), programmable logic used in conjunction with a programmable logic device such as a Field Programmable Gate Array (FPGA) or microprocessor, or any other device including any combination thereof. Programmable logic can be fixed temporarily or permanently in a tangible medium such as a read-only memory chip, a computer memory, a disk, or other storage medium. Programmable logic can also be fixed in a computer data signal embodied in a carrier wave, allowing the programmable logic to be transmitted over an interface such as a computer bus or communication network. All such embodiments are intended to fall within the scope of the present invention. It should be understood that various changes and modifications of the embodiments shown in the drawings and described in the specification may be made within the spirit and scope of the present invention. Accordingly, it is intended that all matter contained in the above description and shown in the accompanying drawings be interpreted in an illustrative and not in a limiting sense. The invention is limited only as defined in the following claims and the equivalents thereto. Patent Citations
Referenced by
Legal Events
Rotate |


text:
Adjacent Areas
< The Pool Wall | Red Wall >
Beyond the pool is the attractive and popular sheet of rock of Gingerbread Slab. This is good spot for a first crack at leading so it is often a bit crowded.
Route (click for voting and user comments) | Symbols | Grade | |
1 |
Once Pegged Wall 10m. The well-hammered thin cracks in the left wall of the groove, moving onto the left arete to gain the top. 10 user comments | 1 Stars Crimpy | VS 5a |
2 |
Morning Glory 10m. The line of old peg holes up the centre of the wall feels a bit artificial, though not as much as it used to do! 1 user comment | Crimpy | E2 5c |
3 |
Limpopo Groove 10m. The angular corner above the "grey, green, greasy, waters" has good gear, a tricky central section and a steep finale. 1 user comment | 1 Stars | VS 4b |
4 |
Gingerbread 10m. The left arete of the slab has decent runners at half-height; so dont risk falling off the last moves! 11 user comments | 1 Stars Fluttery | VS 4b |
5 |
Meringue 10m. The thin crack just to the right is delicate above half-height, micro-Friends just about protect the final crucial moves. 18 user comments | 1 Stars Fluttery | HVS 5a |
6 |
Eclair 10m. A tasty thin slab with polished holds and no gear. 9 user comments | Fluttery | E1 5b |
7 |
Vanilla Slice 10m. More thin slab climbing but this time a touch harder and just as polished, although at least it has some (admittedly poor... 6 user comments | Technical Fluttery | E1 5c |
8 |
Snail Crack 10/16m. The first continuous crack leads up steps to steeper moves and ledges on the left. Meander up easier rock to finish. 4 user comments | 1 Stars | VD |
9 |
Nailsbane 10/16m. This crack system leans to the left and is followed until it is possible to exit left as for the previous climb. 3 user comments | 1 Stars | VD |
10 |
Tyrone 18m. Climb the crack to its end then the steep wall on good but spaced holds. Finish direct up the curving crack or, easier,... 16 user comments | 1 Stars Pumpy | VS 4c |
11 |
Nova 18m. Climb either crack in the right-hand side of the slab (the right-hand one is easier) to a short jamming crack; up this to... 6 user comments | 1 Stars Pumpy | HS 4b |

subset: commoncrawl


text:
Product Description
Available while supplies last.
This stealth flask by P & P Imports is part of the GoPong collection.
Booze Belly Stealth Flask
The Booze Belly allows you to bring your favorite beverage into sporting events, concerts, festivals or any other event. Simply fill the bladder through the fill spout, strap it around your waist and dispense the beverage through the pour spout!
- 750ml capacity
- Always obey all local drinking laws
Coordinating Items
Items in this collection
$17.34Your total:
Add to Cart
Questions & Answers
There are no questions from the community yet
Customer Reviews
This product has no customer reviews yet
Write an online review and be the first to share your thoughts with other customers
Write an online review and be the first to share your thoughts with other customers
Tag This Product
A tag is a keyword assigned to a product which helps describe the item and allows it to be found by other customers
Add a new tag:
Separate multiple tags with commas
What's this?Additional Details
Mfr Part # | |
Sku | |
Group # | 1837363 |
Category | Bar Tools - 2735 |
Style | - 0 |
Sales Rank | 53 |
Your Recently Viewed Items
You have no recently viewed items. After viewing product detail pages or search results, look here to find an easy way to navigate back to products you are interested in.
Your Recommended Items
You currently have no recommended items. Browse a few more items to give us an idea of what you like.
©1999 - 2015
Copyright notice | Site Map | By using this site you agree to our Terms & Conditions of Use and Privacy Statement


text:
Welcome to Silvers Construction Inc!The Silvers Construction team offers building services to clients who value professional quality. With over 30 years of experience, our professionals work directly with clients to ensure that your new home or renovation will continually provide the highest satisfaction for years to come.
Whether adding a deck, rennovating a kitchen, or starting anew, Silvers Construction's quality custom builders ensure that our clients get the most out of their homes! We now offer drafting and design services which allow our clients to experience the highest quality service in custom homes from the first consultation to move-in day! Contact Us today to increase the value of your home! |
Our Story"Four Generations of Quality Home Builders"
Read More Inside Core Values |
Services |
Testimonials |
Contact UsSilvers Construction Inc.
229 Pine Meadow Dr. Travelers Rest, SC (864) 834-3505 firstname.lastname@example.com |


text:
Yea Skate 3 and Skate 2 have locked game saves.
I wanted to back up my save file and start skating from the beginning, but don't want to lose it all if I change my mind.
8:58 pm
i bought gt5 and probally got 50 hours in the game. the game rocks i love it on the most part.
two things i dont like is only some of the cars have the in the car view i wish all of them did. i can live with that though.
maby some day they could add all of the in car view as a add on that would be great lol. well the other thing i dont like
is the locked save game file. come on man are you kidding me what are they thinking about when they decided to lock this up?
all the hours ive played this game will be lost if my system crashes. i dont know if i even want to play it anymore because it
takes so long to build up your money to buy all the cars you need to win or just have for your collection . now i dont feel like
racing hurndreds of hours of my life when a crash will delete them forever. i'm very dissapointed in gt5 and psn for allowing this to go on
come on man unlock this non sence so we can enjoy are very costly games forever not for the life of my ps3
Most Users Ever Online: 349
Currently Online:
10 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Member Stats:
Guest Posters: 199
Members: 15888
Moderators: 0
Admins: 5
Forum Stats:
Groups: 5
Forums: 23
Topics: 1003
Posts: 8874
Newest Members: seinbeans
Administrators: Tosh: 979, Jay: 536, Ceidz: 172, EdEN: 816, Tosh: 56


text:
Does not appear to beSubmitted by SurfCityTom on Fri, 09/28/2012 - 10:00am.
the other; but I did not perform a complete title search. My amazement, candidly, was the Invest site with his Honor & Mr. Thompson both appearing. As I stated earlier, if they were compensated in any fashion, I think they have crossed the line. »
Reply |


text:
CMES Outreach Announces another Spring Break in Egypt!
Posted: October 8, 2010
Participants in the Spring Break in Egypt 2010 program at the Temple of Luxor.
The Center for Middle Eastern Studies at the University of Texas at Austin will conduct a ten-day tour of Egypt over spring break 2011 designed especially for K-12 educators.
The tour will include visits to Cairo, Egypt's capital and the largest city in the Arab world, and sites of contemporary and historic importance like Saqqara, site of the world's first multi-story structure; the Giza Pyramids and the Sphinx; the Egyptian Museum; the thousand year old Islamic core of the city, a UNESCO World Heritage Site; and the recently opened al-Azhar Park. The tour will also include a 3-night Nile Cruise in Upper Egypt between Aswan and Luxor that will visit such sites as the Aswan High Dam, the award-winning Nubian Museum, the temples of Philae and Kom Ombo, the Valley of the Kings, and the temples of Luxor and Karnak.
You will be accompanied by representatives from the University of Texas with extensive experience in Egypt, who will offer lectures and commentary on what you're seeing and doing. Tours and day trips in Cairo will be led by local academics and experts in "Cairology," who will lend their expertise to your experience in this thousand-year-old city. We will also spend down time in local parks and neighborhoods affording you the chance to interact with Egyptians in their own environment and have experiences not afforded to the casual tourist.
Space is limited, and preference will be given to those who teach world cultures, history, and geography. Participants may bring a non-teaching companion, however, we cannot accept children under 18 due to insurance and liability reasons. The Center for Middle Eastern Studies is a licensed provider of Continuing Education Units (CEUs) by the State Board of Educator Recertification, and will award professional development hours for the program.
The per-person cost for this program is $3,100. This includes:
- Round-trip airfare to Cairo and internal flights within Egypt (see "airfare" under Terms and Conditions")
- Local transportation
- Double accommodations within Egypt
- Breakfast and lunch daily; most dinners
- Tour guide fees and gratuities
- Site entry fees
The fee does not include:
- Passport and visa fees
- Independent travel, transportation, sightseeing or meals outside of group activities
- Spending money for souvenirs, personal purchases, telecommunications and Intetnet, etc.
- Health insurance, pre-departure check-ups and inoculations
- Travel insurance
Reservations and a deposit of $1,500 are due by December 31, with the balance due by January 31. Please note that we may stop taking reservations sooner if the program fills up—the 2010 program, for instance, filled up several weeks before the deadline.
Download the Program Brochure and Reservation Form here. (Adobe Acrobat PDF - 1 MB. Mac users: the "save" function may not work in the Preview application--for best results, make sure the document is open in Acrobat Reader).
For more information, download the program brochure (above) or contact Christopher Rose at firstname.lastname@example.com or (512) 471-3582.


text:
Welcome, skip to the content.
Official site for Melbourne, Victoria, Australia
Tour operated by: Sunraysia Flying School
Address: Mildura Airport, Mildura, Victoria 3500
Mobile: 0429 221 787
Email: email@example.com: sunraysiaflyingschool.com.au
Mildura City Flight is an economical flight over Mildura with Sunraysia Flying School. This short flight will put Mildura and district in perspective with a birds eye view of the Murray River. Contact Sunraysia Flying School for further details.
Mildura Airport
Disabled access available on request, please notify at time of booking
Sunraysia Flying School is a flying training and pilot training organisation that also operates scenic flights and charters from their base in Mildura, North West of Victoria on the border of New South Wales.Being based at the edge of the outback allows Sunraysia Flying School to provide groups and individuals with the opportunity to see areas of Australia rarely accessed by most people. Sunraysia Flying School can take you to such breathtaking locations as Lake Eyre, Menindee Lakes, Wilpena Pound and Mungo National Park. Packages can be tailored to suit your needs, or if you simply wish to charter an aircraft to a location of your choice, please call the office.
Select all | Unselect all


text:
Here's your poster, wiseguy. Show it off to your friends on Facebook or Twitter by using the links to the right. Or maybe you want to create a poster for someone else in your crime ring or browse our Rogue's Gallery.
The WETA Guide spotlights the special places and happenings in the Greater Washington area. For both the newcomer and the long-time resident, this television series is a great introduction to the region's many highlights.
Learn more →Questions on how to listen to Classical WETA 90.9 FM or VivaLaVoce online? Problems connecting to the stream? Let us help!
Learn more →Where should you go for the most important meal of the day? Explore two dozen delicious suggestions throughout the Capital region.
Watch video →Curious George uses George's insatiable curiosity as a way of acquainting preschoolers with key concepts in math, science and engineering.
When to watch on WETA Television →Inspired by the film Latino Americans, we decided to seek out a local perspective on the Latino experience in our community with our weta.org Digital Extras. Luis Araya immigrated to Arlington, Virginia from Bolivia in 1966, when very few Latinos lived in the county. He reflects on the changes he has seen over the years and the influence of Latinos in Arlington today.
Watch now →Enjoy this step through time charting WETA's history from its founding in the 1950s as an educational television station, the addition of a public radio station, and evolution into a major national producer for PBS.
See timeline →


text:
- March 02, 2015
02 Mar'15
Docker orchestration tools address scalability
A trio of Docker orchestration tools gives users a means to manage at scale and a native alternative to third-party software already filling the void.
- February 23, 2015
23 Feb'15
IBM guns for the hybrid cloud market -- again
IBM is going after the hybrid computing market -- again -- but this time it is armed for bear. Will IT pros actually take notice?
- February 18, 2015
18 Feb'15
Open source central to Pivotal big data strategy
Pivotal's big data tools are being open sourced, as the company tries to gain traction in a market where transparency and portability are paramount.
- February 17, 2015
17 Feb'15
New cloud testing tools cut app development time, costs
There's a confluence between cloud and mobile testing and support for it in the cloud because of the ability to create production environments without the need and configuration costs of on-premises infrastructure.
- February 16, 2015
16 Feb'15
Time for IT to rein in cloud computing control
Developers have enjoyed an era of 'free cloud love,' with unlimited public cloud access. But nothing lasts forever, as IT looks to rein in the cloud.
- February 04, 2015
04 Feb'15
VMware cloud updates reinforce the hybrid mantra
The latest additions to the VMware cloud offerings include improved networking and OpenStack compatibility to bolster its hybrid strategy.
- February 02, 2015
02 Feb'15
Cisco's cloud networking play targets hybrid cloud shops
Cisco's cloud networking strategy continues to focus on its strengths with a new bundled suite for automation and a shift in licensing.
- February 02, 2015
02 Feb'15
VMware vCloud Air users get Google cloud services
VMware vCloud Air users will get four key Google Cloud Platform features as part of a symbiotic deal between the two cloud service providers.
- January 30, 2015
30 Jan'15
Private Docker repositories add to Google containers push
Private Docker repositories are available through the Google Container Registry -- a move to help secure and deploy private container images.
- January 28, 2015
28 Jan'15
Federal market slowly ramps up cloud computing adoption
U.S. federal agencies have been slow to adopt cloud due to security concerns, budget constraints and other factors. But that might change soon.


text:
Monthly Archives: July 2013
Gator Boys S04E01 – Team Xesion
165 Views0 Comments0 Likes
In the season premiere, the guys go back to Florida, but first attempt to catch several large gators, and teach the Mississippi crew how to wrestle the reptiles. Meanwhile, Paul gets stuck underwater trying to pull...
The Call (2013) Full Movie
226 Views0 Comments0 Likes
When a veteran 911 operator takes a life-altering call from a teenage girl who has just been abducted, she realizes that she must confront a killer from her past in order to save the girl's life.
TuTorial Download Streaming At Xesiontube
273 Views4 Comments0 Likes
How To Download From http://www.xesiontube.net/1- Choose movie for your download Example The Wolverine Camrip 2013 Full Movie This video cannot to play because many user watch this movie. U can wait or choose another ...
Frankensteins Army (2013)
228 Views0 Comments0 Likes
Toward the end of World War II, Russian soldiers pushing into eastern Germany stumble across a secret Nazi lab, one that has unearthed and begun experimenting with the journal of one Dr. Victor Frankenstein. The sc...
Magic Magic (2013) Full Movie
331 Views0 Comments0 Likes
In remote Chile, a vacationing young woman begins to mentally unravel; meanwhile, her friends ignore her claim until it's too late.
El mariachi (1992) Full Movie
291 Views2 Comments0 Likes
A traveling mariachi is mistaken for a murderous criminal and must hide from a gang bent on killing him.
Star Wars: Episode III – Revenge of the Sith (2005) Full Movie
425 Views0 Comments0 Likes
After three years of fighting in the Clone Wars, Anakin Skywalker falls prey to the Sith Lord's lies and makes an enemy of the Jedi and those he loves, concluding his journey to the Dark Side. ...


text:
9 Fall Crafts and Fall Decorating Ideas
Bonus: Get our newsletter & special offers for free. We will not share or sell your email address. View our Privacy Policy
Zip Tie Leaf Earrings
By: Mich L. in L.A.
Want a funky way to dress up your wardrobe for Fall? These Zip Tie Leaf Earrings are such a clever idea, and so easy to make too! You can create your own pair even if you have little to no jewelry making skills, that's how simple they are! Learn how to make these fun craft earrings for Autumn by checking out this tutorial.
Estimated Cost: Under $10
Time to complete: Under an hour
Primary Technique: Jewelry Making
Difficulty Level: Easy
This project is on our list of 15 Fall Craft Ideas: Free Fall Craft Projects and Tutorials
Tags / Related Topics
Your Recently Viewed Projects
Love these projects? Get MORE delivered to your Inbox – FREE Click Here!
Something worth saving?
- SAVE your favorite projects
- ADD personal reminder notes
- QUICKLY reference your projects
Free eBooks
- 10 Free Flower Tutorials: How to Make Fabric Flowers, Flowers from Paper, and More
- 10 Mason Jar Crafts: DIY Home Decor and Handmade Gifts in a Jar
- DIY Wedding Ideas: 14 Wedding Crafts, DIY Wedding Gifts, and More
- Handmade Wreaths for All Seasons: 14 Wreath Tutorials
- Happy Birthday to You: 8 Handmade Birthday Cards, Birthday Crafts, and Birthday Activities
- Happy St. Patrick's Day! 12 St. Patrick's Day Crafts for Kids and Adults
- Valentines Day Ideas: 10 Heart Crafts and Cute Valentines Day Crafts
Our Newest Projects & Articles
- Simple Beaded Cross Craft
- Felt Jesus Finger Puppet
- Salt Dough Resurrection Scene
- Stunning Beaded Easter Cross
- Adorable Easter Egg Zipper Pouch
- Seriously Cute Yarn Easter Baskets
- Candy Box Punch Board
- Gift Bag Punch Board
- How to Make a Pallet Garden
- Spring Fling Butterfly Wall Art


text:
Apple to pay $450M to settle class action over e-book price fixing
updated 01:46 pm EDT, Wed July 16, 2014
Will solve complaints made in 33 states and territories
Apple has agreed to pay $450 million to settle a class-action lawsuit over e-book price fixing, brought against it by states and consumers, according to New York's Attorney General, Eric Schneiderman. The payment will settle allegations made in 33 states and territories, including New York. Schneiderman says that of the total amount, up to $400 million could reach consumers, depending on whether Apple wins its appeal.
A settlement was initially announced last month, but no terms were disclosed at the time. Even now, the deal must be approved by US District Judge Denise Cote. If Cote decides against it, the court will have retry liability, although the settlement terms allow for a smaller recovery of $50 million. In what could be a clever tactic, the deal is structured so that Apple would pay nothing if it's ruled in its appeal that the company didn't break antitrust laws.
The lawsuit accused Apple of conspiring with five major publishers to inflate e-book prices. At the same time as the company launched the iBookstore in 2010, the publishers switched to an agency model forcing companies like Amazon -- which was selling mainstream Kindle titles for average of $10 -- to raise their prices to at least those established by Apple. It and the publishers were initially targeted for investigation by the US government, but the publishers settled quickly, leaving Apple as the only party resisting. The company has so far failed to win in civil or government e-book rulings, but is appealing the case to get an opinion from judges other than Cote, who has made all the rulings thus far.


text:
Latest Auckland Salsa and Zumba News:
Persian's Popular Singers Kamran & Hooman plus Latin Floor Shows performing Live
February 19th, 2015
Persian's Popular Singers Kamran & Hooman are performing Live in Auckland this Sunday
22 February 2015 plus, also performing live:
- Las Vegas Latin Show
- Brazilian Glamour Samba Dancers
- New Zealand Salsa Champions
Tickets: $70:00
Location: ASB Showgrounds (Logan Campbell Centre)
Date: 22 February 2015
Doors Open: 8:00pm
Please like our page on Facebook for more info : facebook.com/PersianNZEntertainment
Info: 0212676299 – 0224004500
Salsa on the Island with Coco & Friends (Waiheke)
February 18th, 2015
Salsa con Coco are travelling from Auckland to Waiheke Island to:
* Hold a Salsa Class
* Dance on the Beach
* Visit a Vineyard – Obsidian (Optional Extra)
* Sample a Spanish Lunch at Casita Miro (Optional Extra)
We would like to invite you to join us for
Our Big Day Out : Island Style.
Waiheke Islanders : $5:00 for the Salsa Class
We will be travelling by Ferry to Waiheke Island.
Cost: $25.00 which includes your ferry fare plus the Salsa Class. Ferry leaves from Pier 3 Downtown Auckland
Ferry can be booked by clicking on the link http://www.sealink.co.nz/waiheke
Booking Details
Pier 3 to Matiatia return
Leave Saturday 21 February 2015 10:45am
Return Saturday 21 February 2015 6:30pm
Banda Latina at Jellicoe Park Onehunga – this Sunday 18.01.15
January 15th, 2015
Banda Latina will be performing live @ Jellicoe Park Onehunga this Sunday Afternoon (18.01.15)
Pack a Picnic Tea and come and Join us for an afternoon of dancing and listening to a great selection (Bachata / Salsa / Merengue / Cha Cha and more) of Latin music performed by Top Salsa Band : Banda Latina.
To get everyone up and dancing there will also be a Free Dance Class run by N.Z. Champion Salsa & Bachata Coach and Performer Jorge (Coco) Sequeiros
Part of the Auckland Council Free Music in Parks Series
Location: Jellicoe Park, 131 Trafalgar Street, Onehunga
Date: 18 January 2015
Time: 2:00pm to 5:00pm
For further details please contact:
Coco (0212) 472572 email@example.com
Pam (0274) 454594 email@example.com
6 Week Bachata Block Course
January 3rd, 2015
We will be holding a 6 Week Bachata Block Course which will be taught by current N.Z. National Bachata Champion Jorge (Coco) Sequeiros
Course content will include:
* Basics & Turns
* Leading & Following Techniques
* Styling
* Flashy moves and Bachata poses
No Partner Necessary – Beginners Welcome
Free Trial: Monday 02/02/15 – 7:00pm
Course Start Date: Monday 02/02/15
Course Start Time: 7:00pm
Location: Trinity Hall, 400 New North Road, Kingsland
Total Course Cost: $50:00
Payment can be made by depositing $50:00 into:
Salsa con Coco BNZ account 02 0157 0021862 001 include Name and Bachata Course as Reference
2015 Salsa con Coco Classes
January 3rd, 2015
Salsa con Coco Highlights for 2014
January 1st, 2015
2014 has been an exciting and challenging year for Salsa con Coco. Here are just some of the highlights from our year.
We "Launched" the first of our Luxury Launch Events with everyone enjoying participating in "Maritime Salsa" with the added bonus of tours around the viaduct and Wynyard Quarter on the smaller launch.
We also launched the first of our Bachata Block Courses which proved very popular with a huge turnout of keen Bachateros ready to learn among other things some Flashy Moves & Bachata Poses from National Champions Coco & Vyara.
Coco & Vyara proved once again that they are New Zealand's Best Bachata & Salsa Performance Dancers by winning 1st Place in both
Professional Bachata Couples & Professional Salsa Couples at the 2014 N.Z. Salsa Open. Plus with a String of Successful & Award Winning Performance Teams coming out of The Salsa con Coco Stable they have also proved their outstanding success as Coaches including coaching the current Bachata & Salsa Performance Team.
December 2014 we ran the first of our B.S.R. (Bachata / Salsa/ Rueda) on the Beach events which was enjoyed by all including Mission Bay Beach goers who took full advantage of the free impromptu "show".
Coco & Team Salsa con Coco would like to thank everyone who has supported our school and team in 2014 and wish each and everyone of you a very Happy New Year for 2015


text:
Book this hotel and collect nights after your stay
On the beach in Puerto Vallarta (South Hotel Zone), Sunset Plaza Beach Resort & Spa is close to Teatro Vallarta, Malecon, and Camarones Beach. Additional attractions near this spa resort include Cruise Ship Terminal and Caballito.
Resort Features.
All-inclusive and room-only rates are available at this resort. All-inclusive rates include meals and beverages at onsite restaurants. Charges may apply for dining at some restaurants, special dinners and dishes, some beverages, and other amenities.
Sunset Plaza Beach Resort & Spa has a full-service spa, 3 outdoor swimming pools, a health club, and a children's pool. Complimentary wireless Internet access is available in public areas. Dining options at this beach resort include a restaurant, a coffee shop/café, and a poolside bar. The staff can provide concierge services, tour/ticket assistance, and wedding services. Additional amenities at this Art Deco resort include a children's club, spa services, and multilingual staff. Complimentary self parking is available onsite for guests. The property may provide extended parking privileges to guests after check-out (surcharge). This is a smoke-free property.
Rooms open to balconies. The 106 air-conditioned guestrooms at Sunset Plaza Beach Resort & Spa include iPod docking stations and laptop-compatible safes. Beds have Select Comfort mattresses, Egyptian cotton sheets, and down comforters. Pillow menus are available. Guests can use the in-room complimentary wireless high-speed Internet access. Rooms are equipped with LCD TVs with premium cable channels and DVD players. All accommodations provide desks and phones. Bathrooms offer showers, bathrobes, designer toiletries, and hair dryers. All units feature minibars, coffee/tea makers, and complimentary bottled water. Additional amenities include slippers and irons/ironing boards. In addition, housekeeping is offered daily and amenities available on request include hypo-allergenic bedding.
Only registered guests are allowed in the guestrooms.
Parking height restrictions apply.
The charges below are included in the total price displayed:
Taking the kids? |
Food and drink |
Things to do |
Services |
Facilities |
Accessibility |
Home comforts |
Sleep well |
Things to enjoy |
Freshen up |
Be entertained |
Stay connected |
Food and drink |
More |
Only registered guests are allowed in the guestrooms.
Parking height restrictions apply.
The charges below are included in the total price displayed:
We have included all charges provided to us by this hotel. However, charges can vary, for example, based on length of stay or the room you book.


text:
As anyone who's played The Warriors can attest, it's neither a simple adaptation of the 1979 cult film nor a simple brawler. Putting players in charge of a roving group of young toughs, it gives you the freedom to stalk New York's neighborhoods at your own pace, stealing and smashing whatever's handy as you bash through the city's street gangs.
The Warriors' Coney Island stomping grounds are particularly well fleshed-out, and if you've finished the story - or just don't feel like following it - you'll find plenty to do just wandering Coney's streets. With the release of the PSP version only a few days away as of this writing, we've put together a last-minute look at a few of the ways you'll be able to get into trouble between missions.


text:
Big Path Capital is pleased to host the Impact Capitalism Summit on April 21-22, 2015 at the Union League Club of Chicago.
The Summit is an excellent forum to develop relationships, to gain insight into successful strategies across industry segments and to learn from leaders who are mainstreaming impact investing. A new model of value creation is emerging deploying capital in strategies that leverage the inherent link between natural, social and financial capital.
Over 300 family offices, asset managers, and fund managers representing over $150 Bn in investable assets will explore the current state and trends of this dynamic sector.
The Impact Capitalism Summit will feature a variety of industry leaders with panel discussions on specific asset classes including private equity, public equity, private debt, public debt and direct deals. Presenters, LP's, and strategic partners will also be able to schedule targeted, one-on-one breakout sessions. The conference provides a rich environment for learning and business development opportunities.
Executives from fund managers across asset classes will showcase their businesses to an audience of more than 250 prospective financial, institutional and strategic investors.
Fund Presentations: Public and private fund managers will present overviews of their respective businesses regarding impact and return, followed by sector-specific panel sessions.
Panel Discussions: There will be a topical, in-depth panel discussing the current state of specific asset classes including private equity, public equity, private debt, public debt and direct deals. Panel members will include family office principals, wealth advisors, and fund managers.
Impact Investing across asset classes is moving into the mainstream. Explore the data:
Impact Investing 2.0: The Way Forward
JP Morgan's: "Impact Investing to grow to $400 billion to nearly $1 trillion over the next 10 years"...
World Economic Forum: "Impact Investing moving from the Margins to the Mainstream"...
Sonen Report: "Impact outperforms, traditional asset allocation strategies"...
Generation Investment Management: "Sustainable companies outperformed a similar matched group of companies"...
Trillium Asset Management: "A Framework for Creating Social and Environmental Impact Across Asset Classes "...
Sponsorships & 2014 Event Report (PDF) |
Presented By: |
2015 Speakers2014's ConferenceThe conference in April 2014 was a landmark event attracting 250 participants from family offices, foundations, global wealth investment firms, investment advisors, fund managers, government, companies and service providers representing one of the largest gatherings of investable assets focused on Impact Investing in the world. It was the first national gathering to take a portfolio approach to Impact Investing focused on institutional investors deploying capital across asset classes for return and impact. Given overwhelming response from the participants from this year's conference, we are excited about what 2015 holds. 2014 Summit Photos |
TIGER 21 is the nation's premier peer-to-peer Media Sponsors:Past Initiatives:Registration Fees$995 early bird until January 31 |


text:
4 dance moves to master before the spring fling
This sweetie sure knows how to make a girl swoon
Dear Carol: Help! I'm the annoying friend
The 2015 RDMA Nonimations are here
February Sleepover Giveaway: Week 4 winners!
How to wear 2015's hottest spring colors
The best BB creams for your end-of-winter skin woes
What your bad breath could really mean
Thoughts on our Feb/March issue? We wanna hear 'em!
Tinker Bell and the Legend of the NeverBeast Character Voices
More Friends = More Fun
GL Tweets !
10 HOURS AGO 7 stylish ways to brighten your spring wardrobe: http://t.co/QVdBlYCsst
13 HOURS AGO 10 signs you're basicallllly Squidward Tenticles 😑http://t.co/zAcDxzkk9TT
14 HOURS AGO Super exciting news for #Jessie fans: http://t.co/wfO1CXlJyg
sponsored links
Check these out, too...
With a contemporary spin, Glee does justice in its tribute to the timeless love story that generations are bound to appreciate. We took a listen to the full soundtrack and here's what we think:
"Hopelessly Devoted To You"
Those hopelessly devoted to Blaine will fall even more head over heels after hearing this solo about love and heartbreak. The charming melody and relatable lyrics are sure to leave you lovesick.
"Born To Hand Jive"
Turn up the volume and practice those moves—there's sure to be a great dance number featuring the whole Glee cast for this upbeat song.
"Greased Lightning"
If you're not already getting your groove on, this Glease staple song will get your feet tapping and head bobbing. Go ahead, we dare you to stay still through this number.
"Look At Me I'm Sandra Dee"
This sweet and edgy track takes us to sleepover silliness with Glee gals Kitty, Sugar, Brittany, Tina and Unique. Put on your PJs and join the fun by belting out this tune with your besties.
"Beauty School Drop Out"
Blaine's gorgeous voice is highlighted by dazzling background vocals in this vintage-y jam. With lines that make us laugh and lyrics that repeat "go back to high school," this tune is sure to make you smile.
"Look At Me I'm Sandra Dee (Reprise)"
Marley gets a solo in this soft—but powerful—song about kicking insecurity to the curb. Her voice reigns strong throughout the short ballad that pledges a new start.
"There Are Worse Things I Can Do"
Kate Hudson's character, Cassandra, returns to lend her vocals along with Santana and Unique, who take turns showcasing their voices in this bad girl tune.
"You're The One That I Want"
This upbeat favorite just screams karaoke with the gang. You'll love Glee's go at this!
"Summer Nights"
The Glee gang gets into "Summer Nights" nostalgia about a beach-time romance. It boasts those fave summer nights with conflicting stories that make this song a he said/she said classic.
Be sure to check out Glee: The Music Presents Glease soundtrack now and then tune in to the special Glease episode next Thursday, Nov. 15, at 9 p.m. ET/PT on FOX.
What's your favorite Grease song? Blog about it, babes.
POSTED IN entertainment, television, Glee, review, music reviews, music
Score a set of swoon-worthy reads in our "Books We're Crushing On" giveaway. Enter HERE!
Get swept up in a magical romance this V-Day
Fall under the spell of Dearest, the newest book in the Woodcutter Sisters series. CLICK HERE to swan dive into the supernatural!


text:
Coghlan's Flexible Light
0 reviews
4-star: 0
3-star: 0
2-star: 0
1-star: 0
4-star: 0
3-star: 0
2-star: 0
1-star: 0
Weight |
2 1/4 oz / 64 g with 2 AA batteries |
Manufacturer's Description
Visit Coghlan's's Flexible Light page.
Retailers' Descriptions
Here's what other sites are saying:
3 flexible neck, Sturdy plastic clip, Positive rotary on/off switch, uses 2 AA batteries (not included), Weighs 2.25 oz. w/batteries
- Ramsey Outdoor
Hands free light where you want it in camp, car, or on the trail. 3 in. flexible neck, sturdy plastic clip, positive rotary on/off switch. Uses 2 'AA' batteries, not included. Wt. 2 1/2 oz.
- Campmor
Coghlan's Flexible Light
previously retailed for:
The Coghlan's Flexible Light is not available from the stores we monitor. It was last seen November 21, 2014 at Ramsey Outdoor.
If you're looking for a new flashlight, check out the best reviewed current models.