WO2020029976A1 - Vpn跨域的实现方法、装置和边界节点 - Google Patents

Vpn跨域的实现方法、装置和边界节点 Download PDF

Info

Publication number
WO2020029976A1
WO2020029976A1 PCT/CN2019/099512 CN2019099512W WO2020029976A1 WO 2020029976 A1 WO2020029976 A1 WO 2020029976A1 CN 2019099512 W CN2019099512 W CN 2019099512W WO 2020029976 A1 WO2020029976 A1 WO 2020029976A1
Authority
WO
WIPO (PCT)
Prior art keywords
vpn
sid
node
label
forwarding
Prior art date
Application number
PCT/CN2019/099512
Other languages
English (en)
French (fr)
Inventor
彭少富
金飞蔡
汤海华
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US17/264,976 priority Critical patent/US11936552B2/en
Priority to EP19846514.8A priority patent/EP3836490B1/en
Publication of WO2020029976A1 publication Critical patent/WO2020029976A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/34—Source routing

Definitions

  • This disclosure relates to, but is not limited to, the field of data communications.
  • Segment routing technology enables a node to specify its forwarding path for a specific message, and Instead of forwarding according to the general shortest path, by attaching information related to the Segment List (SID) in the message, there is no need to maintain the status information of each path on the intermediate node .
  • SID Segment List
  • SRv6 IPv6 Segmentation Routing
  • SRH Segment Routing Routing Header
  • L2VPN Layer, Virtual Private Network, Layer 2 Virtual Private Network
  • EVPN Ethernet, Virtual Private Network, Ether Virtual Private Network
  • L3VPN Layer 3 Virtual Private Networks
  • the corresponding VPN instance information is given in the local SID entry corresponding to the END.DT type SID
  • the guidance message is directly given in the local SID entry corresponding to the END.DX type SID. Information forwarded to the corresponding link.
  • BGP notification message contains the VPN SID to support the mechanism for VPN services to be carried on SRv6, referred to as VPN overover.
  • SRv6 is similar to the traditional VPN over MPLS (Multi-Protocol Label Switching). The key difference is that the VPN SID is used instead of the VPN label.
  • SRv6 In actual network deployment, such as voice services within the operator, and VPN private line services for enterprise customers, they often span multiple AS (Autonomous System, autonomous system) or IGP (Interior, Gateway, Protocol) areas. How VPN effectively spans multiple ASs (or IGP areas) is also a problem that SRv6 needs to pay attention to and solve.
  • the domain that it crosses can be a domain that has been upgraded to support SRv6 capabilities (called an SRv6 domain), or it can Upgrade SRv6 capabilities in traditional MPLS domains.
  • An embodiment of the present disclosure provides a method for implementing a virtual private network (VPN) across domains, including: a border node receives a notification message carrying VPN routing information sent by a first node to a second node; wherein the border node supports IPv6 Segment routing (SRv6) capability, where the first node and the second node belong to different domains respectively; the border node allocates VPN identification information for the VPN route corresponding to the VPN routing information, which is carried in the announcement message The VPN identification information sends the announcement message to the second node; wherein the VPN identification information includes at least one of a VPN segment identification (SID) and a VPN label.
  • SID VPN segment identification
  • An embodiment of the present disclosure also provides a device for implementing a virtual private network (VPN) across domains, which is applied to a border node that supports IPv6 segment routing (SRv6) capabilities, and includes a receiving module configured to receive a first node to a second node.
  • a notification message sent by a node carrying VPN routing information; wherein the first node and the second node belong to different domains respectively; an allocation module configured to allocate VPN identification information to a VPN route corresponding to the VPN routing information, in The announcement message carries the VPN identification information, and sends the announcement message to the second node; wherein the VPN identification information includes at least one of a VPN segment identifier (SID) and a VPN label.
  • SID VPN segment identifier
  • An embodiment of the present disclosure also provides a boundary node, which supports IPv6 Segmented Routing (SRv6) capability, including: a processor; a memory configured to store the processor-executable instructions; and configured to be based on the processing
  • SRv6 Segmented Routing SRv6 capability
  • the processor is configured to perform the following operations: control the transmission device to receive a notification message carrying VPN routing information sent by a first node to a second node; wherein, the processor The first node and the second node belong to different domains respectively; assign VPN identification information to the VPN route corresponding to the VPN routing information, carry the VPN identification information in the announcement message, and send the announcement message to all The second node; wherein the VPN identification information includes at least one of a VPN segment identification (SID) and a VPN label.
  • SID VPN segment identification
  • An embodiment of the present disclosure also provides a computer-readable storage medium storing computer-executable instructions, where the computer-executable instructions are used to perform any method described herein.
  • FIG. 1 is a flowchart of a method for implementing a VPN across domains according to an embodiment of the present disclosure.
  • FIG. 2 is a flowchart of a method for implementing a VPN across domains according to another embodiment of the present disclosure.
  • FIG. 3 is a schematic diagram of a device for implementing VPN cross-domain according to an embodiment of the present disclosure.
  • FIG. 4 is a network topology diagram of the first application example.
  • Fig. 5 is a network topology diagram of application examples two and three.
  • FIG. 6 is a network topology diagram of the fourth application example.
  • FIG. 7 is a network topology diagram of the fifth application example.
  • FIG. 8 is a schematic structural diagram of a boundary node according to an embodiment of the present disclosure.
  • Option-A needs to be configured with a Virtual Router Forwarding (VRF) instance on the ASBR (Autonomous System Boundary Router) or ABR (Area Border Router).
  • VRF Virtual Router Forwarding
  • ASBR Autonomous System Boundary Router
  • ABR Area Border Router
  • ASBR or ABR
  • ASBR or ABR
  • the present disclosure particularly proposes a method, a device, and a border node for implementing a VPN across domains, which substantially avoids one or more of the problems caused by the limitations and disadvantages of the related technology.
  • the option-B cross-domain solution can be made to support VPN over SRv6.
  • a border node connecting a domain and a domain that has been upgraded to support SRv6 capability, it is configured to have the ability to assign a VPN SID.
  • This capability refers to the VPN route that the border node will advertise to other nodes that it receives.
  • a VPN SID can be assigned and the VPN SID can be included in the notification message. Create a corresponding local SID forwarding entry for the VPN SID on the border node.
  • the FUNCTION is a new type, which means that the incoming SRv6 SID is exchanged for the outgoing SRv6 SID or MPLS label. If the border node also supports MPLS, the ability to allocate VPN labels is retained.
  • the border node advertises the VPN routes advertised to it by other nodes to other MPLS-only nodes, it allocates VPN labels and
  • the announcement message contains the VPN label.
  • the label operation is to switch the inbound MPLS label to the outbound SRv6 SID or MPLS label. .
  • the method for implementing VPN across domains in the embodiment of the present disclosure may include the following steps 101 and 102.
  • step 101 the border node receives a notification message carrying VPN routing information sent by the first node to the second node.
  • the border node supports IPv6 segment routing (SRv6) capability, and the first node and the second node belong to different domains, respectively.
  • SRv6 IPv6 segment routing
  • the border node may be an ASBR or an ABR.
  • the notification message may use but is not limited to BGP.
  • the notification message may include, but is not limited to, at least one of a notification message of a Layer 3 virtual private network, a notification message of an Ethernet virtual private network, and a notification message of a Layer 2 virtual private network.
  • the method before step 101, further includes: configuring the border node to have a capability of allocating a VPN SID.
  • This capability means that when an ASBR (or ABR) node advertises a VPN route advertised to it by another node (that is, the first node) to another node that has the SRv6 capability (that is, the second node), it can assign a VPN SID and The VPN SID is included in the announcement message.
  • ASBR or ABR
  • the border node assigns VPN identification information to a VPN route corresponding to the VPN routing information, carries the VPN identification information in the announcement message, and sends the announcement message to the second node; wherein
  • the VPN identification information includes at least one of a VPN segment identification SID and a VPN label.
  • the border node allocates VPN identification information according to the capabilities of the second node.
  • the capability of the second node refers to whether it supports SRv6 capability or MPLS capability.
  • the second node only supports SRv6 capability, and the border node allocates one of the following as VPN identification information: a valid VPN SID; a valid VPN SID and an invalid VPN label.
  • the invalid VPN label can be set to implicit empty label 3 or other values indicating invalidity.
  • the second node supports both SRv6 capability and MPLS capability
  • the border node allocates one of the following as the VPN identification information according to the configuration policy: a valid VPN SID and a valid VPN label (the border node Support both SRv6 capability and MPLS capability); valid VPN SID and invalid VPN label; valid VPN label and invalid VPN SID (the border node supports both SRv6 capability and MPLS capability); effective VPN SID; effective VPN label.
  • the second node only supports MPLS capabilities, and the border node allocates one of the following as VPN identification information: a valid VPN label; a valid VPN label and an invalid VPN SID.
  • the border node supports both SRv6 capability and MPLS capability.
  • VPN SID refers to valid VPN SID
  • a VPN label refers to a valid VPN label
  • the method may include:
  • VPN identification information includes a VPN SID:
  • step 103 the border node creates a corresponding local SID forwarding entry for the assigned VPN SID, and the border node sets the forwarding behavior of the local SID forwarding entry including exchanging the incoming SRv6 SID to the outgoing SRv6 SID or MPLS label.
  • the FUNCTION (function) of the local SID forwarding entry is a new type, which means that the incoming SRv6 SID is exchanged for the outgoing SRv6 SID or MPLS label.
  • the forwarding behavior of the local SID forwarding entry is set.
  • the border node setting the forwarding behavior of the local SID forwarding entry according to the received VPN identification information carried in the announcement message may include the following three cases.
  • the notification message received by the border node carrying VPN routing information contains only a valid VPN SID, and the border node sets the forwarding behavior of the local SID forwarding entry to exchange the incoming SRv6 SID into Outgoing SRv6 SID.
  • the advertisement message carrying the VPN routing information received by the border node only contains a valid VPN label, and the border node sets the forwarding behavior of the local SID forwarding entry to exchange the incoming SRv6 SID into Outbound MPLS label.
  • the notification message carrying the VPN routing information received by the border node includes a valid VPN SID and a valid VPN label, and the border node sets a forwarding behavior of the local SID forwarding entry according to a configuration policy.
  • the border node may set the forwarding behavior of the local SID forwarding entry according to the configuration policy to exchange the incoming SRv6 SID with the outgoing SRv6 SID or MPLS label.
  • the method may further include: flooding, by the border node, the routing information including the VPN SID to the IGP area to which the border node belongs.
  • the border node floods the IGP area to which the border node belongs through IGP to include the routing information of the VPN SID.
  • the routing information including the VPN SID may be a VPN SID resource pool.
  • the local SID forwarding entry created by the border node includes outbound member forwarding information, and the outbound member forwarding information includes an identifier of a next hop node and a VPN SID or VPN label.
  • the forwarding behavior of the local SID forwarding entry is to exchange the incoming SRv6 SID to the outgoing SRv6 SID, and the next hop node corresponds to the VPN SID; the forwarding behavior of the local SID forwarding entry is to incoming The SRv6 SID is exchanged into an outgoing MPLS label, and the next hop node corresponds to a VPN label.
  • the local SID forwarding entry may include ECMP (Equal-Cost, Multipath, Routing, Equal Routing) forwarding information or FRR (Fast Reroute, fast rerouting) forwarding information.
  • the forwarding information is generated according to the outbound member forwarding information.
  • the method may further include: Step 104, the border node receives a message sent by the second node to the first node, and finds the local SID forwarding hit according to the destination address carried in the message.
  • the posting item is forwarded according to the forwarding behavior of the hit local SID forwarding entry and the VPN SID or VPN label corresponding to the next hop node.
  • the border node searches the public network routing table for the local SID forwarding entry that was hit according to the destination address carried in the packet.
  • the forwarding behavior of the local SID forwarding entry is to exchange the incoming SRv6 SID to the outgoing SRv6 SID, and the border node changes the destination address of the message to the next hop
  • the VPN SID corresponding to the node forwards the message to the next hop node.
  • the forwarding behavior of the local SID forwarding entry is to exchange the incoming SRv6 SID with an outgoing MPLS label
  • the border node removes the IPv6 packet header of the packet, and encapsulates the MPLS label , Setting a top-level label of the message to a VPN label corresponding to the next-hop node, and forwarding the message to the next-hop node.
  • the border node removes the IPv6 packet header of the message and replaces the IPv6 packet with an MPLS label to encapsulate the IPv6 packet into an MPLS packet, and sets the top-level label of the packet to all packets.
  • the VPN label corresponding to the next hop node is directly forwarded to the next hop node.
  • the border node creates a corresponding ILM (In-label Mapping) forwarding entry for the assigned VPN label, and the border node sets a label operation of the ILM forwarding entry to include inbound MPLS. Labels are switched to outgoing SRv6 SIDs or MPLS labels.
  • ILM In-label Mapping
  • the border node may set the label operation of the ILM forwarding entry according to the received VPN identification information carried in the announcement message, which may include the following three cases.
  • the advertisement message carrying the VPN routing information received by the border node only contains a valid VPN SID, and the border node sets the label operation of the ILM forwarding entry to switch the incoming MPLS label to the outgoing direction SRv6 SID.
  • the advertisement message carrying the VPN routing information received by the border node only contains a valid VPN label, and the border node sets the label operation of the ILM forwarding entry to switch the incoming MPLS label to the outgoing direction. MPLS label.
  • the notification message carrying the VPN routing information received by the border node includes a valid VPN SID and a valid VPN label, and the border node sets a label operation of the ILM forwarding entry according to a configuration policy.
  • the border node may set a label operation of the ILM forwarding entry according to a configuration policy to exchange an incoming MPLS label with an outgoing SRv6 SID or MPLS label.
  • the ILM forwarding entry created by the border node includes outbound member forwarding information, and the outbound member forwarding information includes an identifier of a next hop node and a VPN SID or VPN corresponding to the next hop node. label.
  • the label operation of the ILM forwarding entry is to exchange the incoming MPLS label with an outgoing SRv6 SID, and the next hop node corresponds to the VPN SID; the label operation of the ILM forwarding entry is to switch the incoming MPLS The label is switched to an outgoing MPLS label, and the next hop node corresponds to a VPN label.
  • the ILM forwarding entry may include ECMP forwarding information or FRR forwarding information, and ECMP forwarding information or FRR forwarding information is generated according to the outbound member forwarding information.
  • the method may further include: Step 106, the border node receives a message sent by the second node to the first node, and searches for a hit ILM forwarding table according to a top label of the message. Entry according to the label operation of the hit ILM forwarding entry and the VPN SID or VPN label corresponding to the next hop node for forwarding.
  • the label operation of the ILM forwarding entry is to exchange the incoming MPLS label with the outgoing SRv6 SID, the border node pops the top label of the packet, and encapsulates the IPv6 packet header. Change the destination address of the message to the VPN SID corresponding to the next hop node, and forward the message to the next hop node.
  • the border node pops the top label of the packet, encapsulates the IPv6 packet header, changes the MPLS packet into an IPv6 packet, and changes the destination address of the packet to the next hop.
  • the VPN SID corresponding to the node uses the VPN SID corresponding to the next-hop node to look up the routing information in the routing table and forwards the information to the next-hop node.
  • the label operation of the ILM forwarding entry is to exchange the incoming MPLS label with the outgoing MPLS label, and the border node changes the top-level label of the message to the next-hop node.
  • the corresponding VPN label forwards the message to the next hop node.
  • the SRv6 technology VPN cross-domain gap is made up, and VPN packets can be transmitted across multiple SRv6 domains and across heterogeneous networks composed of SRv6 domains and MPLS domains.
  • an embodiment of the present disclosure further provides a device for implementing VPN cross-domain, which is applied to a border node that connects at least one domain and supports IPv6 segmented routing SRv6 capability, and includes a receiving module 31 configured to receive a first A notification message sent by a node to a second node carrying VPN routing information; wherein the first node and the second node belong to different domains respectively; and an allocation module 32 is configured to allocate a VPN route corresponding to the VPN routing information VPN identification information, which carries the VPN identification information in the announcement message, and sends the announcement message to the second node; wherein the VPN identification information includes at least one of a VPN segment identifier SID and a VPN label One.
  • the boundary node includes at least one of the following: ASBR and ABR.
  • the apparatus further includes a configuration module configured to configure the border node to have a capability of allocating a VPN SID.
  • the allocation module 32 is configured to allocate VPN identification information according to the capabilities of the second node.
  • the second node only supports SRv6 capability, and the allocation module 32 is configured to allocate one of the following as VPN identification information: a valid VPN SID; a valid VPN SID and an invalid VPN label.
  • the second node supports both SRv6 capability and multiprotocol label switching MPLS capability
  • the distribution module 32 is configured to allocate one of the following as VPN identification information according to a configuration policy: a valid VPN SID and a valid VPN label; valid VPN SID and invalid VPN label; valid VPN label and invalid VPN SID; valid VPN SID; valid VPN label.
  • the second node only supports MPLS capabilities, and the allocation module 32 is configured to allocate one of the following as VPN identification information: a valid VPN label; a valid VPN label and an invalid VPN SID.
  • the apparatus further includes a first creation module configured to create a corresponding local SID forwarding entry for the assigned VPN SID when the VPN identification information includes a VPN SID, and set the local SID forwarding table
  • the item's forwarding behavior includes switching the incoming SRv6 SID to the outgoing SRv6 SID or MPLS label.
  • the first creating module is configured to execute at least one of the following: the notification message carrying the VPN routing information received by the receiving module contains only a valid VPN SID, and the local SID forwarding table is set The forwarding behavior of the entry is to exchange the incoming SRv6 SID with the outgoing SRv6 SID; the notification message received by the receiving module that contains the VPN routing information contains only a valid VPN label, and the local SID forwarding entry is set The forwarding behavior is to switch the incoming SRv6 SID into the outgoing MPLS label; the notification message received by the receiving module that carries the VPN routing information contains a valid VPN SID and a valid VPN label, and is set according to the configuration policy. The forwarding behavior of the local SID forwarding entry is described.
  • the apparatus further includes: a flooding module configured to flood the routing information containing the VPN SID to the corresponding IGP area through an internal gateway protocol (IGP).
  • IGP internal gateway protocol
  • the created local SID forwarding entry includes outbound member forwarding information
  • the outbound member forwarding information includes an identifier of a next hop node and a VPN SID or VPN label corresponding to the next hop node .
  • the apparatus further includes: a first message forwarding module configured to receive a message sent by the second node to the first node, and find a local SID that is hit according to a destination address carried in the message The forwarding entry is forwarded according to the forwarding behavior of the hit local SID forwarding entry and the VPN SID or VPN label corresponding to the next hop node.
  • a first message forwarding module configured to receive a message sent by the second node to the first node, and find a local SID that is hit according to a destination address carried in the message The forwarding entry is forwarded according to the forwarding behavior of the hit local SID forwarding entry and the VPN SID or VPN label corresponding to the next hop node.
  • the first message forwarding module is configured to perform at least one of the following: the forwarding behavior of the local SID forwarding entry is to exchange the incoming SRv6 SID to the outgoing SRv6 SID, and The destination address of the message is changed to the VPN SID corresponding to the next hop node, and the message is forwarded to the next hop node; the forwarding behavior of the local SID forwarding entry is to exchange the incoming SRv6 SID The outgoing MPLS label, remove the IPv6 packet header of the packet, encapsulate the MPLS label, set the top label of the packet to the VPN label corresponding to the next hop node, and forward the packet to The next hop node.
  • the apparatus further includes a second creation module configured to create a corresponding in-label mapping (ILM) forwarding entry for the assigned VPN label when the VPN identification information includes a VPN label, and set the The label operation of the ILM forwarding entry includes switching the incoming MPLS label to the outgoing SRv6 SID or MPLS label.
  • ILM in-label mapping
  • the second creation module is configured to execute at least one of the following: the advertisement message carrying the VPN routing information received by the receiving module contains only a valid VPN SID, and the setting is performed.
  • the label operation of the ILM forwarding entry is to switch the incoming MPLS label to the outgoing SRv6 SID; the notification message received by the receiving module that contains the VPN routing information contains only a valid VPN label, and the ILM forwarding is set
  • the labeling operation of the published item is to exchange the incoming MPLS label with the outgoing MPLS label; the advertisement message carrying the VPN routing information received by the receiving module includes a valid VPN SID and a valid VPN label, according to the configuration policy Set a label operation for the ILM forwarding entry.
  • the ILM forwarding entry created by the second creating module includes outbound member forwarding information, and the outbound member forwarding information includes an identifier of a next hop node and a VPN SID corresponding to the next hop node Or VPN tags.
  • the apparatus further includes: a second message forwarding module configured to receive a message sent by the second node to the first node, and find a hit ILM relay according to a top-level label of the message.
  • the posting item is operated according to the label of the hit ILM forwarding entry and the VPN SID or VPN label corresponding to the next hop node.
  • the second message forwarding module is configured to perform at least one of the following: the label operation of the ILM forwarding entry is to exchange an incoming MPLS label with an outgoing SRv6 SID, and exchange the message The top label of the message pops up, encapsulates the IPv6 message header, changes the destination address of the message to the VPN SID corresponding to the next hop node, and forwards the message to the next hop node; the ILM The labeling operation of the forwarding entry is to exchange the incoming MPLS label with the outgoing MPLS label, change the top label of the message to the VPN label corresponding to the next hop node, and forward the message to the Next hop node.
  • the SRv6 technology VPN cross-domain gap is made up, and VPN packets can be transmitted across multiple SRv6 domains and across heterogeneous networks composed of SRv6 domains and MPLS domains.
  • CE1 and CE2 belonging to the same L3VPN customer need to communicate across AS1 and AS2, and both AS1 and AS2 have been upgraded to support SRv6 capabilities.
  • CE1 and CE2 are both IPv4 customers (CE is an IPv6 customer is completely similar).
  • PE1 and PE2 are assigned to END.DX4 VPN SIDs of CE1 and CE2 customers, respectively, and are distributed with VPNv4 (VPN-IPv4 address family). (See RFC4364) Route Advertisement.
  • PE2 assigns an END.DX4 VPN SID to CE2 customers (the VPN SID is an IPv6 address, recorded as sid_dx4_ce2), and the FUNCTION of the local SID forwarding entry maintained by sid_dx4_ce2 on PE2 is the FUNCTION of the decapsulated IPv6 header and the corresponding IPv4 Link forwarding.
  • an SRv6 SID resource pool for local allocation of SIDs can be maintained.
  • the SRv6 SID resource pool is actually an IPv6 prefix (prefix), which is recorded as prefix_srv6_sid_pool_pe2.
  • sid_dx4_ce2 is routable.
  • PE2 floods prefix_srv6_sid_pool_pe2 to the IGP area to which PE2 belongs through IGP.
  • This application example uses CE1 to access CE2 as an example to describe the corresponding routing advertisement and data forwarding process, including the following steps 401 to 410.
  • an MP-IBGP neighbor is established between PE2 and ASBR2.
  • PE2 advertises an IPv4 private network route learned from CE2 (such as the loopback route of CE2 itself as prefix_ce2) to ASBR2 through BGP.
  • the VPNv4 route (denoted as vpnv4_prefix_ce2) carries the aforementioned sid_dx4_ce2 in the BGP advertisement message.
  • ASBR2 is configured to have the ability to assign a VPN SID.
  • ASBR2 receives the VPNv4 route advertised by PE2 (that is, vpnv4_prefix_ce2), it locally assigns a VPNSID to the vpnv4_prefix_ce2 (the VPNSID is an IPv6 address and is recorded as sid_br_100 ).
  • PE2 Similar to PE2, in order to facilitate the above-mentioned VPN SID allocation, ASBR2 can maintain an SRv6 SID resource pool for local allocation of SIDs, recorded as prefix_srv6_sid_pool_asbr2, and floods the IGP area to which ASBR2 belongs through IGP.
  • the FUNCTION of the local SID forwarding entry maintained by ASBR2 for sid_br_100 is to exchange the incoming SRv6 SID with the outgoing SRv6 SID or MPLS label.
  • the entry contains only one BGP next hop PE2 and its related sid_dx4_ce2.
  • ASBR2 will learn prefix_srv6_sid_pool_PE2 through IGP flooding.
  • an MP-EBGP neighbor is established between ASBR2 and ASBR1.
  • ASBR2 continues to advertise the VPNv4 route (that is, vpnv4_prefix_ce2) advertised by PE2 to ASBR1, carries the above sid_br_100 in the BGP advertisement message, and changes the next hop of BGP to itself.
  • the MP-EBGP session between ASBR1 and ASBR2 is generally established based on the IP address of the interface of the direct link between them, so the BGP next hop here is actually the IP address of the interface of the link between ASBR2 and ASBR1. From the perspective of ASBR1, this is a directly connected IP address.
  • ASBR1 is configured to have the ability to assign a VPN SID.
  • VPNv4 route that is, vpnv4_prefix_ce2
  • ASBR1 receives the VPNv4 route (that is, vpnv4_prefix_ce2) advertised by ASBR2, it locally assigns a VPNSID to the vpnv4_prefix_ce2 (the VPNSID is an IPv6 address and is recorded as sid_br_200 ).
  • ASBR1 can maintain an SRv6 SID resource pool for local allocation of SIDs, recorded as prefix_srv6_sid_pool_asbr1, and floods the IGP area to which ASBR1 belongs through IGP.
  • the FUNCTION of the local SID forwarding entry maintained by ASBR1 for sid_br_200 is to switch the incoming SRv6 SID to the outgoing SRv6 SID or MPLS label.
  • the entry contains only one BGP next hop ASBR2 (as described above, this is a direct connection IP address) and its associated sid_br_100.
  • step 405 an MP-IBGP neighbor relationship is established between ASBR1 and PE1.
  • ASBR1 continues to advertise the VPNv4 route (that is, vpnv4_prefix_ce2) advertised by ASBR2 to PE1, and carries the above sid_br_200 in the BGP advertisement message, and changes the next hop of BGP to itself. .
  • PE1 imports the VPNv4 route into the corresponding local VRF routing table according to the BGP Route Target policy, and establishes a private network routing entry prefix_ce2. Contains a BGP next hop ASBR1 and its related sid_br_200.
  • PE1 will learn prefix_srv6_sid_pool_asbr1 through IGP flooding.
  • step 407 when the IPv4 packet from CE1 accessing CE2 reaches PE1, it searches the corresponding VRF routing table according to the destination IP address of the packet and hits the private network routing table prefix_ce2 to encapsulate the outer IPv6 header and the destination in the IPv6 header.
  • the address can be directly set to sid_br_200, and then sid_br_200 is used to find the prefix_srv6_sid_pool_asbr1 in the public network routing table.
  • the packet will be forwarded to ASBR1 along the shortest path of IGP (or TE (Traffic Engineering) path).
  • step 408 when the IPv6 packet arrives at ASBR1, it searches for a corresponding local SID forwarding entry in the public network routing table according to the destination IP address (sid_br_200) of the packet. Because the FUNCTION of the local SID forwarding entry is the incoming The SRv6 SID exchange is the outgoing SRv6 SID or MPLS label, and the entry contains only a BGP next hop ASBR2 (as described above, this is a directly connected IP address) and its related sid_br_100, so the After the destination IP address is changed to sid_br_100, it is sent directly to the directly connected next hop ASBR2. (Because the BGP next hop address is a directly connected IP address, there is no need to look up the routing table for sid_br_100 to obtain the forwarding information).
  • step 409 when the IPv6 packet arrives at ASBR2, the corresponding local SID forwarding entry is found in the public network routing table according to the destination IP address (sid_br_100) of the packet. Because the FUNCTION of the local SID forwarding entry is the incoming The SRv6 SID exchange is the outgoing SRv6 SID or MPLS label, and the entry contains only a BGP next hop PE2 and its related sid_dx4_ce2, so after changing the destination IP address of the IPv6 packet to sid_dx4_ce2, take sid_dx4_ce2 on the public network The routing table looks for prefix_srv6_sid_pool_pe2, and the packet will be forwarded to PE2 along the shortest path (or TE path) of the IGP.
  • step 410 when the IPv6 packet arrives at PE2, it searches for a corresponding local SID forwarding entry in the public network routing table according to the destination IP address of the packet (sid_dx4_ce2). Because the FUNCTION of the local SID forwarding entry is the decapsulation IPv6 After the header is forwarded to the corresponding IPv4 link (that is, END.DX4), the IPv6 header is removed and forwarded to CE2.
  • the routing advertisement involved in accessing CE1 from CE2 is similar to the data forwarding process, and is not repeated here.
  • This application example is basically the same as Application Example 1. As shown in Figure 5, the difference is that AS1 has been upgraded to support SRv6 capabilities, while AS2 still only supports MPLS capabilities. Assume that PE1 allocates an END.DX4 VPN SID (denoted as sid_dx4_ce1) to CE1 customers and maintains the corresponding local SID forwarding entries. PE1 also maintains an SRv6 SID resource pool (denoted as prefix_srv6_sid_pool_pe1) and sends IGP to the IGP area to which PE1 belongs. Flooding.
  • END.DX4 VPN SID denotes an END.DX4 VPN SID (denoted as sid_dx4_ce1) to CE1 customers and maintains the corresponding local SID forwarding entries.
  • PE1 also maintains an SRv6 SID resource pool (denoted as prefix_srv6_sid_pool_pe1) and sends IGP to the IGP area to which PE1 belongs.
  • This application example first uses CE1 to access CE2 as an example to describe the corresponding routing advertisement and data forwarding process, including the following steps 501 to 510.
  • an MP-IBGP neighbor is established between PE2 and ASBR2.
  • PE2 advertises an IPv4 private network route learned from CE2 (such as the loopback route of CE2 itself as prefix_ce2) to advertise the corresponding VPNv4 route to ASBR2 through BGP ( It is denoted as vpnv4_prefix_ce2), and a VPN label (labeled as label_ce2) is carried in the BGP advertisement message.
  • PE2 creates a corresponding ILM entry for label_ce2. The label operation given in the entry is forwarded to CE2 after the label is popped.
  • step 502 after receiving the VPNv4 route (that is, vpnv4_prefix_ce2) advertised by PE2, ASBR2 locally allocates a VPN label (labeled as label_br_100) for vpnv4_prefix_ce2, and establishes a corresponding ILM entry for label_br_100.
  • the entry contains only one BGP entry. One hop of PE2 and its associated label_ce2.
  • an MP-EBGP neighbor is established between ASBR2 and ASBR1.
  • ASBR2 continues to advertise the VPNv4 route (that is, vpnv4_prefix_ce2) advertised by PE2 to ASBR1, carries the above label_br_100 in the BGP notification message, and changes the next hop of BGP to itself.
  • the MP-EBGP session between ASBR1 and ASBR2 is generally established based on the IP address of the interface of the direct link between them, so the BGP next hop here is actually the IP address of the interface of the link between ASBR2 and ASBR1. From the perspective of ASBR1, this is a directly connected IP address.
  • ASBR1 is configured to have the ability to assign a VPN SID.
  • ASBR1 receives the VPNv4 route (that is, vpnv4_prefix_ce2) advertised by ASBR2, it locally assigns a VPNSID to the vpnv4_prefix_ce2 (the VPNSID is an IPv6 address and is recorded as sid_br_200 ).
  • an SRv6 SID resource pool for local allocation of SIDs can be maintained, recorded as prefix_srv6_sid_pool_asbr1, and flooded to the IGP area to which ASBR1 belongs through IGP.
  • the FUNCTION of the local SID forwarding entry maintained by ASBR1 for sid_br_200 is to switch the incoming SRv6 SID to the outgoing SRv6 SID or MPLS label.
  • the entry contains only one BGP next hop ASBR2 (as described above, this is a direct connection IP address) and its associated label_br_100.
  • step 505 an MP-IBGP neighbor is established between ASBR1 and PE1.
  • ASBR1 continues to advertise the VPNv4 route (that is, vpnv4_prefix_ce2) advertised by ASBR2 to PE1, and carries the above sid_br_200 in the BGP advertisement message, and changes the next hop of BGP to itself. .
  • step 506 when PE1 receives the VPNv4 route advertised by ASBR1 (that is, vpnv4_prefix_ce2), it imports the VPNv4 route into the corresponding local VRF routing table according to the BGP Route Target policy, and establishes a private network routing entry prefix_ce2.
  • the entry contains only one BGP next hop ASBR1 and its related sid_br_200.
  • PE1 will learn prefix_srv6_sid_pool_asbr1 through IGP flooding.
  • step 507 when the IPv4 packet from CE1 accessing CE2 reaches PE1, it searches the corresponding VRF routing table according to the destination IP address of the packet and hits the private network routing table prefix_ce2 to encapsulate the outer IPv6 header and the destination in the IPv6 header.
  • the address can be directly set to sid_br_200, and then sid_br_200 is used to find the prefix_srv6_sid_pool_asbr1 in the public network routing table.
  • the packet will be forwarded to ASBR1 along the shortest path (or TE path) of the IGP.
  • step 508 when the IPv6 packet arrives at ASBR1, it searches for a corresponding local SID forwarding entry in the public network routing table according to the destination IP address (sid_br_200) of the packet. Since the FUNCTION of the local SID forwarding entry is the incoming destination, The SRv6 SID is switched to the outgoing SRv6 SID or MPLS label, and the entry contains only a BGP next hop ASBR2 (as described above, this is a directly connected IP address) and its related label_br_100, so the IPv6 packet header After being stripped, it is replaced with MPLS label encapsulation, which becomes an MPLS packet.
  • the top label of the packet is set to label_br_100, and then sent directly to the directly connected next hop ASBR2. (Note that because the BGP next hop address is a directly connected IP address, So there is no need to iteratively search for forwarding information).
  • step 509 after the above MPLS packet reaches ASBR2, ASBR2 searches for ILM according to the label top_label_br_100 of the packet, exchanges the label to label_ce2, and then traverses the public network tunnel to PE2.
  • step 510 after the packet reaches PE2, the public network tunnel is terminated, and the ILM is searched for according to the label label_ce2 on the top layer of the packet. After the label pops up, it is forwarded to CE2.
  • routing advertisement and data forwarding process involved in accessing CE1 from CE2 is described, including the following steps 601 to 609.
  • an MP-IBGP neighbor is established between PE1 and ASBR1.
  • PE1 advertises an IPv4 private network route learned from CE1 (such as the loopback route of CE1 itself as prefix_ce1) to advertise the corresponding VPNv4 route to ASBR1 through BGP ( Recorded as vpnv4_prefix_ce1), the sid_dx4_ce1 is carried in the BGP advertisement message.
  • ASBR1 is configured to have the ability to assign a VPN SID.
  • VPNv4 route that is, vpnv4_prefix_ce1
  • ASBR1 receives the VPNv4 route (that is, vpnv4_prefix_ce1) advertised by PE1, it locally assigns a VPN SID to the vpnv4_prefix_ce1.
  • ASBR1 also has MPLS capabilities. It can also allocate a VPN label (labeled as label_br_300) to vpnv4_prefix_ce1 locally.
  • the label operation of the ILM entry maintained by ASBR1 for label_br_300 is to switch the incoming MPLS label to the outgoing SRv6 SID or MPLS label.
  • the entry contains only one BGP next hop PE1 and its related sid_dx4_ce1.
  • ASBR1 will learn prefix_srv6_sid_pool_PE1 through IGP flooding.
  • an MP-EBGP neighbor is established between ASBR1 and ASBR2.
  • ASBR1 continues to advertise the VPNv4 route (that is, vpnv4_prefix_ce1) advertised by PE1 to ASBR2, carries the above label_br_300 in the BGP notification message, and changes the next hop of BGP to itself.
  • the MP-EBGP session between ASBR1 and ASBR2 is generally established based on the IP address of the interface of the direct link between them, so the BGP next hop here is actually the IP address of the interface of the link between ASBR1 and ASBR2. From the perspective of ASBR2, this is a directly connected IP address.
  • step 604 after receiving the VPNv4 route (that is, vpnv4_prefix_ce1) advertised by ASBR1, ASBR2 locally allocates a VPN label (labeled as label_br_400) to the vpnv4_prefix_ce2, and maintains the corresponding ILM entry.
  • a VPN label label (labeled as label_br_400)
  • step 605 after receiving the VPNv4 route (that is, vpnv4_prefix_ce1) advertised by ASBR2, PE2 imports the VPNv4 route into the corresponding local VRF routing table according to the BGP Route Target policy, and establishes a private network routing entry prefix_ce1. Contains a BGP next hop ASBR2 and its associated label_br_400.
  • step 606 when the IPv4 packet from CE2 accessing CE1 reaches PE2, it searches the corresponding VRF routing table according to the destination IP address of the packet, hits the private network routing table prefix_ce1, encapsulates the VPN label (label_br_400), and traverses the public network tunnel. To ASBR2.
  • step 607 when the packet reaches ASBR2, the public network tunnel is terminated.
  • the ILM entry is found according to the top label label_br_400 of the packet, and the label is switched to 3label_br_300 and then forwarded to ASBR1.
  • step 608 when the packet reaches ASBR1, the ILM entry is found according to the top label label_br_300 of the packet.
  • the label operation is to exchange the incoming MPLS label with the outgoing SRv6 SID or MPLS label.
  • the entry contains only one BGP.
  • the top label label_br_300 of the message is popped up, and the IPv6 header is re-encapsulated into an IPv6 message.
  • the destination address of the message is filled in as sid_dx4_ce1, and sid_dx4_ce1 is found in the public network routing table to hit prefix_srv6_sid_pool_pe1. (Or TE path) forward to PE1.
  • step 609 when the IPv6 packet arrives at PE1, it searches for a corresponding local SID forwarding entry in the public network routing table according to the destination IP address of the packet (sid_dx4_ce1). Because the FUNCTION of the local SID forwarding entry is the decapsulation IPv6 After the header is forwarded to the corresponding IPv4 link (that is, END.DX4), the IPv6 header is removed and forwarded to CE1.
  • CE1 and CE2 belonging to the same L3VPN customer need to communicate across IGP area 1, IGP area 2, and IGP area 3. Both IGP area 1 and IGP area 2 have been upgraded to support SRv6 capabilities, but IGP area 3 still only supports MPLS.
  • CE1 and CE2 are both IPv4 customers, and CE2 is dual-homed to PE2 and PE3.
  • PE1 and PE2 assign CE1 and CE2 customers with END.DX4 VPN SIDs respectively and advertise them with VPNv4 routes.
  • PE1 assigns an END.DX4 VPN SID (denoted as sid_dx4_ce1) to CE1 customers, and the SRv6 SID resource pool maintained is recorded as prefix_srv6_sid_pool_pe1 and flooded in IGP area 1.
  • PE2 is assigned to CE2 customer END .DX4 VPN SID (recorded as sid_dx4_ce2), SRv6 SID resource pool maintained is recorded as prefix_srv6_sid_pool_pe2 and flooded in IGP area 2.
  • step 701 PE2 announces vpnv4_prefix_ce2 to the ABR through MP-IBGP, and carries sid_dx4_ce2 in the BGP advertisement message; PE2 maintains the corresponding local SID forwarding entry for sid_dx4_ce2.
  • step 702 PE3 announces vpnv4_prefix_ce2 to the ABR through MP-IBGP, and carries label_ce2 in the BGP advertisement message; PE3 maintains the corresponding ILM entry for label_ce2.
  • the ABR is configured to have the ability to allocate a VPN SID.
  • the ABR receives the VPNv4 route (that is, vpnv4_prefix_ce2) advertised by PE2 or PE3, it locally allocates a VPN SID (denoted as sid_br_100) to the vpnv4_prefix_ce2.
  • the SRv6 SID resource pool maintained by the ABR is recorded as prefix_srv6_sid_pool_abr, and flooded to the IGP area to which the ABR belongs through IGP.
  • the FUNCTION of the local SID forwarding entry maintained by ABR for sid_br_100 is to exchange the incoming SRv6 SID to the outgoing SRv6 SID or MPLS label.
  • the entry contains two outgoing member forwarding information: one is BGP next hop PE2 and its related Sid_dx4_ce2; the other is BGP next hop PE3 and its associated label_ce2. These two outbound forwarding messages can form ECMP or FRR.
  • ABR will learn prefix_srv6_sid_pool_PE2 through IGP flooding. .
  • the ABR continues to advertise vpnv4_prefix_ce2 to PE1 through MP-IBGP, and sid_br_100 is carried in the BGP advertisement message.
  • PE1 After receiving the VPNv4 route (that is, vpnv4_prefix_ce2) advertised by the ABR, PE1 establishes a private network routing entry prefix_ce2, which contains only a BGP next hop ABR and its related sid_br_100.
  • PE1 will learn prefix_srv6_sid_pool_abr through IGP flooding.
  • step 705 when the IPv4 packet from CE1 accessing CE2 reaches PE1, the outer IPv6 header is encapsulated.
  • the destination address in the IPv6 header can be directly set to sid_br_100, and the packet will be forwarded to the ABR along the IGP shortest path (or TE path). .
  • step 706 when the IPv6 packet arrives at the ABR, the corresponding local SID forwarding entry is found in the public network routing table according to the destination IP address (sid_br_100) of the packet. Since the FUNCTION of the local SID forwarding entry is the incoming The SRv6 SID exchange for the outgoing SRv6 SID or MPLS label, and the entry contains two outbound member forwarding information, then: if forwarding to the first member, the destination IP address of the IPv6 packet is modified to sid_dx4_ce2 to find the routing table Forward to the PE2 along the shortest path (or TE path) of the IGP; if you remove the IPv6 header and re-MPLS encapsulation when forwarding to the second member, press the label_ce2 label and traverse the public network tunnel to PE3.
  • step 707 after the aforementioned IPv6 packet reaches PE2, it finds and hits the local SID forwarding entry related to sid_dx_ce2, decapsulates the IPv6 header, and forwards it to CE2.
  • step 708 after the MPLS packet arrives at PE3, it searches for and hits the ILM entry related to label_ce2, bounces the top label label_ce2, and forwards it to CE2.
  • This application example is basically the same as Application Example 4. As shown in Figure 7, only IGP area 2 has been upgraded to support SRv6 capabilities, but IGP area 1 and IGP area 3 still only support MPLS. This application example is different from other application examples in that the ILM entries maintained on the ABR node contain ECMP (or FRR) forwarding information. The steps are briefly described below as steps 801 to 808.
  • PE2 announces vpnv4_prefix_ce2 to ABR through MP-IBGP, and carries sid_dx4_ce2 in the BGP advertisement message; PE2 maintains the corresponding local SID forwarding entry for sid_dx4_ce2.
  • PE3 announces vpnv4_prefix_ce2 to the ABR through MP-IBGP, and carries a label_ce2 in the BGP advertisement message; PE3 maintains a corresponding ILM entry for label_ce2.
  • the ABR is configured to have the ability to assign a VPN SID.
  • the ABR receives the VPNv4 route (that is, vpnv4_prefix_ce2) advertised by PE2 or PE3, it locally allocates a VPN SID to vpnv4_prefix_ce2.
  • ABR also has MPLS capabilities. It can also assign a VPN label (labeled as label_br_100) to vpnv4_prefix_ce2.
  • the label operation of the ILM entry maintained by ABR for label_br_100 is to exchange the incoming MPLS label with an outgoing SRv6 SID or MPLS label.
  • the entry contains two outgoing members to forward information: one is BGP next hop PE2 and its related sid_dx4_ce2; the other is BGP next hop PE3 and its related label_ce2. These two outbound forwarding messages can form ECMP or FRR.
  • ABR will learn prefix_srv6_sid_pool_PE2 through IGP flooding. .
  • the ABR continues to advertise vpnv4_prefix_ce2 to PE1 through MP-IBGP, and carries label_br_100 in the BGP notification message.
  • PE1 After receiving the VPNv4 route (that is, vpnv4_prefix_ce2) advertised by the ABR, PE1 establishes a private network routing entry prefix_ce2, which contains only a BGP next hop ABR and its associated label_br_100.
  • step 805 when the IPv4 packet from CE1 accessing CE2 reaches PE1, the MPLS label stack is encapsulated, and the underlying label is label_br_100, and the public network tunnel is passed to the ABR.
  • step 806 when the packet reaches the ABR, the public network tunnel is terminated.
  • the label top_label_br_100 of the packet the corresponding ILM entry is found and matched. Since the label operation of the ILM entry is to switch the incoming MPLS label to the outgoing SRv6 SID or MPLS label, and the entry contains two outbound members, then: if forwarding to the first member, pop the label label_br_100, then re-encapsulate the IPv6 header, set the destination IP address of the IPv6 packet to sid_dx4_ce2, and then The routing table is searched and forwarded to PE2 along the shortest path (or TE path) of the IGP; if it is forwarded to the second member, the label label_br_100 is exchanged for the label label_ce2, and then it passes through the public network tunnel to PE3.
  • step 807 after the aforementioned IPv6 packet reaches PE2, it finds and hits the local SID forwarding entry related to sid_dx_ce2, decapsulates the IPv6 header, and forwards it to CE2.
  • step 808 after the MPLS packet arrives at PE3, it searches for and hits the ILM entry related to label_ce2, bounces the top label label_ce2, and forwards it to CE2.
  • This application example is for EVPN cross-domain. It is completely similar to the aforementioned L3VPN cross-domain application example. The difference is that the types of routes advertised through BGP are different, and the processing on ASBR (or ABR) nodes is completely similar.
  • CE1 and CE2 establish a point-to-point connection through PE1 and PE2.
  • ASBR2 can receive Ethernet Auto-discoveryRoute (Type-1) from PE2.
  • Type 1) Route advertisement and it contains a valid SRv6 VPN SID (for example, FUNCTION is END.DX2, recorded as sid_dx2_pe2), ASBR2 is configured with the ability to assign VPN SID, then it can re-assign a new VPN for the above VPN routes SID (recorded as sid_dx2_asbr2), ASBR2 continues to advertise the VPN route to ASBR1 and changes the next hop to itself, which contains the newly assigned VPN SID (sid_dx2_asbr2) for ASBR2.
  • ASBR1 is also configured with the ability to assign a VPN SID.
  • a new VPN SID (denoted as sid_dx2_asbr1) is reassigned for the VPN route received from ASBR2, and ASBR1 continues to advertise the VPN route to PE1 and modify the next hop as Itself, which contains the newly assigned VPN SID (sid_dx2_asbr1) for ASBR1.
  • the FUNCTIONs of the local SID forwarding entries created on ASBR1 and ASBR2 for their newly allocated VPN SIDs are both inbound SRv6 SIDs and outbound SRv6 SIDs or MPLS labels.
  • ASBR1 When subsequent packets are forwarded from CE1 to CE2, ASBR1 will receive IPv6 packets with a destination IP of sid_dx2_asbr1, and will hit the corresponding local SID forwarding entry. ASBR1 then exchanges the destination IP of the IPv6 packet to sid_dx2_asbr2 The message continues to be forwarded to ASBR2; similarly, after receiving the message, ASBR2 will exchange the destination IP of the message to sid_dx2_pe2 and continue to forward it to PE2 along the shortest path (or TE path). The specific process is not repeated here.
  • the ABR can receive MAC / IP Advertisement Route (Type-2) from PE2, and it contains a valid SRv6 VPN. SID.
  • ABR can also receive the same NLRI (Network Layer Reachability Information) key value MAC / IP Advertisement Route (Type-2) routing advertisement from PE3 and it contains a valid MPLS label. Then the ABR can locally allocate the corresponding VPN SID or VPN label, and create the corresponding local SID forwarding entry or ILM entry. The entry contains two outbound members that form ECMP (or FRR).
  • the corresponding local The FUNCTION of the SID is to exchange the incoming SRv6 SID to the outgoing SRv6 SID or MPLS label
  • the corresponding ILM label operation is to exchange the incoming MPLS label to the outgoing SRv6 SID or MPLS label. The specific process is not repeated here.
  • EVPN also defines IP prefix (Type-5) (IP prefix routing-type 5) to support L3VPN services.
  • IP prefix routing-type 5 IP prefix routing-type 5
  • RFC4761 defines a BGP, VPLS, and NLRI routing type, which is used to advertise PW-related labels.
  • BGP Long Term Evolution
  • VPLS Virtual Private LAN Service
  • NLRI Network Address Translation
  • an embodiment of the present disclosure further provides a boundary node.
  • the boundary node supports an IPv6 segment routing (SRv6) capability and includes: a processor 81; and a memory 82 configured to store the processor-executable instructions.
  • a transmission device 83 configured to perform information transmission and reception communication according to the control of the processor; wherein the processor 81 is configured to perform the following operation: control the transmission device 83 to receive a carrying VPN sent by a first node to a second node An announcement message of routing information; wherein the first node and the second node belong to different domains respectively; assign VPN identification information to a VPN route corresponding to the VPN routing information, and carry the VPN identification in the announcement message Information, sending the announcement message to the second node; wherein the VPN identification information includes at least one of a VPN segment identification SID and a VPN label.
  • An embodiment of the present disclosure further provides a computer-readable storage medium storing computer-executable instructions, where the computer-executable instructions are used to perform any method described herein.
  • computer storage medium includes volatile and non-volatile implemented in any method or technology used to store information such as computer-readable instructions, data structures, program modules or other data.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or may Any other medium used to store desired information and which can be accessed by a computer.
  • a communication medium typically contains computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供了VPN跨域的实现方法、装置和边界节点，边界节点接收第一节点向第二节点发送的携带VPN路由信息的通告消息；其中，边界节点支持IPv6分段路由SRv6能力，第一节点和第二节点分别归属于不同的域；边界节点为VPN路由信息对应的VPN路由分配VPN标识信息，在通告消息中携带VPN标识信息，将通告消息发送至第二节点；其中，VPN标识信息包括VPN分段标识SID和VPN标签中的至少之一。

Description

VPN跨域的实现方法、装置和边界节点 技术领域
本公开涉及但不限于数据通信领域。
背景技术
在有关路由技术的标准中，draft-ietf-spring-segment-routing-15描述了分段路由(Segment Routing)的架构，分段路由技术使得一个节点可以为特定的报文指定其转发路径，而不是按一般的最短路径转发，通过在报文中附加由SID(Segment ID，分段标识)组成的分段列表(Segment List)相关的信息，不需要在中间节点上维护每条路径的状态信息。
draft-filsfils-spring-srv6-network-programming-04描述了如何将分段路由应用于IPv6(Internet Protocol Version 6，互联网协议版本6)转发平面，也即SRv6(IPv6 Segment Routing，IPv6分段路由)，通过在IPv6报文头中插入一个路由扩展头SRH(Segment Routing Header，分段路由头)，在SRH中包含了由IPv6地址列表表示的Segment List，报文的目的地址将逐段的被更新，完成逐段转发。该草案中定义了一些具有不同功能(Function)的SRv6 SID，其中针对VPN(Virtual Private Network，虚拟私有网络)场景的SRv6 SID(或简称为VPN SID)有END.DT和END.DX两大类型，这两大类型针对L2VPN(Layer 2 Virtual Private Network，二层虚拟私有网络)、EVPN(Ethernet Virtual Private Network，以太虚拟私有网络)、L3VPN(Layer 3 Virtual Private Networks，三层虚拟私有网络)又细分出多个子类型。一般来说，END.DT类型的SID对应的本地(local)SID表项中给出了相应的VPN实例信息，而END.DX类型的SID对应的本地SID表项中会直接给出指导报文向相应的链路转发的信息。
draft-dawra-idr-srv6-vpn-02描述了如何扩展BGP(Border Gateway Protocol，边界网关协议)，在BGP通告消息中包含VPN SID 以支持VPN业务承载在SRv6之上的机制，简称为VPN over SRv6，与传统的VPN over MPLS(Multi-Protocol Label Switching，多协议标签交换)类似，关键区别是采用VPN SID替代VPN label。
在实际网络部署中，如运营商内部的语音业务，企业客户的VPN专线业务，往往都是跨越多个AS(Autonomous System，自治系统)或IGP(Interior Gateway Protocol，内部网关协议)区域(area)，VPN如何有效跨越多个AS(或IGP区域)，也是VPN over SRv6需要关注和解决的问题，所跨越的域可以是已经升级支持了SRv6能力的域(称为SRv6域)，也可以是未升级SRv6能力的传统的MPLS域。
发明内容
本公开实施例提供了一种虚拟私有网络(VPN)跨域的实现方法，包括：边界节点接收第一节点向第二节点发送的携带VPN路由信息的通告消息；其中，所述边界节点支持IPv6分段路由(SRv6)能力，所述第一节点和第二节点分别归属于不同的域；所述边界节点为所述VPN路由信息对应的VPN路由分配VPN标识信息，在所述通告消息中携带所述VPN标识信息，将所述通告消息发送至所述第二节点；其中，所述VPN标识信息包括VPN分段标识(SID)和VPN标签中的至少之一。
本公开实施例还提供了一种虚拟私有网络(VPN)跨域的实现装置，应用于支持IPv6分段路由(SRv6)能力的边界节点，包括：接收模块，配置为接收第一节点向第二节点发送的携带VPN路由信息的通告消息；其中，所述第一节点和第二节点分别归属于不同的域；分配模块，配置为为所述VPN路由信息对应的VPN路由分配VPN标识信息，在所述通告消息中携带所述VPN标识信息，将所述通告消息发送至所述第二节点；其中，所述VPN标识信息包括VPN分段标识(SID)和VPN标签中的至少之一。
本公开实施例还提供了一种边界节点，所述边界节点支持IPv6分段路由(SRv6)能力，包括：处理器；配置为存储所述处理器可执行指令的存储器；配置为根据所述处理器的控制进行信息收发通信的 传输装置；其中，所述处理器配置为执行以下操作：控制所述传输装置接收第一节点向第二节点发送的携带VPN路由信息的通告消息；其中，所述第一节点和第二节点分别归属于不同的域；为所述VPN路由信息对应的VPN路由分配VPN标识信息，在所述通告消息中携带所述VPN标识信息，将所述通告消息发送至所述第二节点；其中，所述VPN标识信息包括VPN分段标识(SID)和VPN标签中的至少之一。
本公开实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行本文所述的任一方法。
附图说明
附图用来提供对本公开技术方案的进一步理解，并且构成说明书的一部分，与本公开的实施例一起用于解释本公开的技术方案，并不构成对本公开技术方案的限制。
图1为本公开实施例的VPN跨域的实现方法的流程图。
图2为本公开另一实施例的VPN跨域的实现方法的流程图。
图3为本公开实施例的VPN跨域的实现装置的示意图。
图4是应用实例一的网络拓扑图。
图5是应用实例二、三的网络拓扑图。
图6是应用实例四的网络拓扑图。
图7是应用实例五的网络拓扑图。
图8是本公开实施例边界节点的结构示意图。
具体实施方式
下文中将结合附图对本公开的实施例进行详细说明。需要说明的是，在不冲突的情况下，本公开中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
传统的VPN over MPLS提出了三种典型的VPN跨域方案，分别 称之为opt ion-A、option-B、option-C，它们可类似应用于VPN over SRv6。但是这三种方案中：option-A需要在ASBR(Autonomous System Boundary Router，自治系统边界路由器)或ABR(Area Border Router，区域边界路由器)上配置VRF(Virtual Routing Forwarding，虚拟路由转发)实例，仅适用于VPN数量较少的情况；option-C则较难用于VPN跨SRv6域和MPLS域组成的异构网络的情况，因为处于SRv6域的PE(Provider Edge，运营商边缘)设备和处于MPLS域的PE设备需具备相同的能力，比如均需支持VPN标签(label)的操作或均需支持VPN SID的操作，另外ASBR(或ABR)还要升级支持异构网络的粘连；仅option-B适合网络平滑演进的要求，仅需针对ASBR(或ABR)升级支持异构网络的粘连。
但是，option-B跨域方案并不能有效支持VPN over SRv6。
因此，本公开特别提出一种VPN跨域的实现方法、装置和边界节点，其实质上避免了由于相关技术的局限和缺点所导致的问题中的一个或多个。根据本公开的实施例，可以使option-B跨域方案支持VPN over SRv6。
在本公开实施例中，在连接域与域的已升级支持SRv6能力的边界节点上，配置其具有分配VPN SID的能力，该能力是指边界节点将收到的其它节点向它通告的VPN路由向另外的具有SRv6能力的节点通告时，可以分配VPN SID并在通告消息中包含该VPN SID。在该边界节点上为该VPN SID创建对应的本地SID转发表项，其FUNCTION为新增类型，表示将入向的SRv6 SID交换成出向的SRv6 SID或MPLS标签。如果该边界节点还支持MPLS，则保留分配VPN标签的能力，是指该边界节点将收到的其它节点向它通告的VPN路由向另外的仅具有MPLS能力的节点通告时，分配VPN标签并在通告消息中包含该VPN标签。在该ASBR(或ABR)节点上为该VPN标签创建对应的ILM(In-label Mapping，入标签映射)转发表项，其标签操作为将入向的MPLS标签交换成出向的SRv6 SID或者MPLS标签。
如图1所示，本公开实施例的VPN跨域的实现方法，可以包括如下步骤101和102。
在步骤101，边界节点接收第一节点向第二节点发送的携带VPN路由信息的通告消息。
这里，所述边界节点支持IPv6分段路由(SRv6)能力，所述第一节点和第二节点分别归属于不同的域。
这里，所述边界节点可以是ASBR，也可以是ABR。
例如，所述通告消息可以采用但不限于BGP。
例如，所述通告消息可以包括但不限于三层虚拟私有网络的通告消息、以太虚拟私有网络的通告消息和二层虚拟私有网络的通告消息中的至少之一。
在一实施例中，步骤101之前，所述方法还包括：配置所述边界节点具有分配VPN SID的能力。
该能力是指ASBR(或ABR)节点将收到的其它节点(即第一节点)向它通告的VPN路由向另外的具有SRv6能力的节点(即第二节点)通告时，可以分配VPN SID并在通告消息中包含该VPN SID。
在步骤102，所述边界节点为所述VPN路由信息对应的VPN路由分配VPN标识信息，在所述通告消息中携带所述VPN标识信息，将所述通告消息发送至所述第二节点；其中，所述VPN标识信息包括VPN分段标识SID和VPN标签中的至少之一。
在一实施例中，所述边界节点根据所述第二节点的能力，分配VPN标识信息。
所述第二节点的能力是指：是否支持SRv6能力或支持MPLS能力。
其中，是否支持SRv6能力或支持MPLS能力可分为以下三种情况。
在第一种情况下，所述第二节点仅支持SRv6能力，所述边界节点分配如下之一作为VPN标识信息：有效的VPN SID；有效的VPN SID和无效的VPN标签。举例来说，无效的VPN标签可以设置为隐式空标签3或者其它表示无效的值。
在第二种情况下，所述第二节点同时支持SRv6能力和MPLS能力，所述边界节点根据配置策略分配如下之一作为VPN标识信息：有 效的VPN SID和有效的VPN标签(所述边界节点同时支持SRv6能力和MPLS能力)；有效的VPN SID和无效的VPN标签；有效的VPN标签和无效的VPN SID(所述边界节点同时支持SRv6能力和MPLS能力)；有效的VPN SID；有效的VPN标签。
在第三种情况下，所述第二节点仅支持MPLS能力，所述边界节点分配如下之一作为VPN标识信息：有效的VPN标签；有效的VPN标签和无效的VPN SID。
这种情况下，所述边界节点同时支持SRv6能力和MPLS能力。
需要说明的是，上述有效的VPN SID和有效的VPN标签是为了与无效的VPN标签和无效的VPN标签进行对比而强调说明，在本文中，如无特别说明，VPN SID指有效的VPN SID、VPN标签指有效的VPN标签。
如图2所示，在一实施例中，步骤102之后，根据所述边界节点分配VPN标识信息的不同，所述方法可包括：
一、所述VPN标识信息包括VPN SID时：
步骤103，所述边界节点为分配的VPN SID创建对应的本地SID转发表项，所述边界节点设置所述本地SID转发表项的转发行为包括将入向的SRv6 SID交换成出向的SRv6 SID或MPLS标签。
这里，所述本地SID转发表项的FUNCTION(功能)为新增类型，表示将入向的SRv6 SID交换成出向的SRv6 SID或MPLS标签。通过设置该FUNCTION，设置所述本地SID转发表项的转发行为。
这里，所述边界节点根据接收到的所述通告消息携带的VPN标识信息，设置所述本地SID转发表项的转发行为，可包括如下三种情况。
1、所述边界节点接收到的所述携带VPN路由信息的通告消息中仅包含有效的VPN SID，所述边界节点设置所述本地SID转发表项的转发行为为将入向的SRv6 SID交换成出向的SRv6 SID。
2、所述边界节点接收到的所述携带VPN路由信息的通告消息中仅包含有效的VPN标签，所述边界节点设置所述本地SID转发表项的转发行为为将入向的SRv6 SID交换成出向的MPLS标签。
3、所述边界节点接收到的所述携带VPN路由信息的通告消息中包含有效的VPN SID和有效的VPN标签，所述边界节点根据配置策略设置所述本地SID转发表项的转发行为。
在这种情况下，所述边界节点可以根据配置策略设置所述本地SID转发表项的转发行为为将入向的SRv6 SID交换成出向的SRv6 SID或MPLS标签。
在一实施例中，所述方法还可以包括：所述边界节点通过IGP向所属的IGP区域泛洪包含所述VPN SID的路由信息。
这里，为了网络内其它节点对所述边界节点分配的VPN SID可路由，所述边界节点通过IGP向其所属的IGP区域泛洪包含上述VPN SID的路由信息。所述包含上述VPN SID的路由信息可以是VPN SID资源池。
在一实施例中，所述边界节点创建的本地SID转发表项中包括出向成员转发信息，所述出向成员转发信息包括下一跳节点的标识，以及所述下一跳节点对应的VPN SID或VPN标签。
这里，所述本地SID转发表项的转发行为为将入向的SRv6 SID交换成出向的SRv6 SID，所述下一跳节点对应VPN SID；所述本地SID转发表项的转发行为为将入向的SRv6 SID交换成出向的MPLS标签，所述下一跳节点对应VPN标签。
在一实施例中，所述本地SID转发表项可以包括ECMP(Equal-Cost Multipath Rout ing，等价路由)转发信息或FRR(Fast Reroute，快速重路由)转发信息，所述ECMP转发信息或FRR转发信息根据所述出向成员转发信息生成。
在一实施例中，所述方法还可以包括：步骤104，所述边界节点接收第二节点向第一节点发送的报文，根据所述报文中携带的目的地址，查找命中的本地SID转发表项，按照所述命中的本地SID转发表项的转发行为，以及所述下一跳节点对应的VPN SID或VPN标签进行转发。
这里，当报文到达所述边界节点时，所述边界节点根据所述报文中携带的目的地址，在公网路由表中查找命中的本地SID转发表项。
针对转发行为不同，可分为如下两种情况。
在第一种情况下，所述本地SID转发表项的转发行为为将入向的SRv6 SID交换成出向的SRv6 SID，所述边界节点将所述报文的目的地址改为所述下一跳节点对应的VPN SID，将所述报文转发至所述下一跳节点。
在第二种情况下，所述本地SID转发表项的转发行为为将入向的SRv6 SID交换成出向的MPLS标签，所述边界节点将所述报文的IPv6报文头去掉，封装MPLS标签，将所述报文的顶层标签设置为所述下一跳节点对应的VPN标签，将所述报文转发至所述下一跳节点。
在本步骤中，所述边界节点将所述报文的IPv6报文头去掉，换成MPLS标签封装，从而将该IPv6报文变成MPLS报文，将所述报文的顶层标签设置为所述下一跳节点对应的VPN标签，直接将所述报文转发至所述下一跳节点。
二、所述VPN标识信息包括VPN标签时：
步骤105，所述边界节点为分配的VPN标签创建对应的ILM(In-label Mapping，入标签映射)转发表项，所述边界节点设置所述ILM转发表项的标签操作包括将入向的MPLS标签交换成出向的SRv6 SID或者MPLS标签。
这里，所述边界节点根据接收到的所述通告消息携带的VPN标识信息，设置所述ILM转发表项的标签操作，可包括如下三种情况。
1、所述边界节点接收到的所述携带VPN路由信息的通告消息中仅包含有效的VPN SID，所述边界节点设置所述ILM转发表项的标签操作为将入向的MPLS标签交换成出向的SRv6 SID。
2、所述边界节点接收到的所述携带VPN路由信息的通告消息中仅包含有效的VPN标签，所述边界节点设置所述ILM转发表项的标签操作为将入向的MPLS标签交换成出向的MPLS标签。
3、所述边界节点接收到的所述携带VPN路由信息的通告消息中包含有效的VPN SID和有效的VPN标签，所述边界节点根据配置策略设置所述ILM转发表项的标签操作。
在这种情况下，所述边界节点可以根据配置策略设置所述ILM 转发表项的标签操作为将入向的MPLS标签交换成出向的SRv6 SID或MPLS标签。
在一实施例中，所述边界节点创建的ILM转发表项中包括出向成员转发信息，所述出向成员转发信息包括下一跳节点的标识，以及所述下一跳节点对应的VPN SID或VPN标签。
这里，所述ILM转发表项的标签操作为将入向的MPLS标签交换成出向的SRv6 SID，所述下一跳节点对应VPN SID；所述ILM转发表项的标签操作为将入向的MPLS标签交换成出向的MPLS标签，所述下一跳节点对应VPN标签。
在一实施例中，所述ILM转发表项可以包括ECMP转发信息或FRR转发信息，ECMP转发信息或FRR转发信息根据所述出向成员转发信息生成。
在一实施例中，所述方法还可以包括：步骤106，所述边界节点接收所述第二节点向第一节点发送的报文，根据所述报文的顶层标签，查找命中的ILM转发表项，按照所述命中的ILM转发表项的标签操作，以及所述下一跳节点对应的VPN SID或VPN标签进行转发。
针对标签操作不同，可分为如下两种情况。
在第一种情况下，所述ILM转发表项的标签操作为将入向的MPLS标签交换成出向的SRv6 SID，所述边界节点将所述报文的顶层标签弹出，封装IPv6报文头，将所述报文的目的地址改为所述下一跳节点对应的VPN SID，将所述报文转发至所述下一跳节点。
在本步骤中，所述边界节点将所述报文的顶层标签弹出，封装IPv6报文头，将MPLS报文变成IPv6报文，将所述报文的目的地址改为所述下一跳节点对应的VPN SID，使用所述下一跳节点对应的VPN SID在路由表中查找命中的路由信息，向所述下一跳节点转发。
在第二种情况下，所述ILM转发表项的标签操作为将入向的MPLS标签交换成出向的MPLS标签，所述边界节点将所述报文的顶层标签改为所述下一跳节点对应的VPN标签，将所述报文转发至所述下一跳节点。
通过本公开实施例，弥补了SRv6技术的VPN跨域空白，可以实 现VPN报文跨越多个SRv6域以及跨越SRv6域和MPLS域组成的异构网络进行传递。
如图3所示，本公开实施例还提出一种VPN跨域的实现装置，应用于连接至少一个域并支持IPv6分段路由SRv6能力的边界节点，包括：接收模块31，配置为接收第一节点向第二节点发送的携带VPN路由信息的通告消息；其中，所述第一节点和第二节点分别归属于不同的域；分配模块32，配置为为所述VPN路由信息对应的VPN路由分配VPN标识信息，在所述通告消息中携带所述VPN标识信息，将所述通告消息发送至所述第二节点；其中，所述VPN标识信息包括VPN分段标识SID和VPN标签中的至少之一。
在一实施例中，所述边界节点包括如下至少之一：ASBR和ABR。
在一实施例中，所述装置还包括：配置模块，配置为配置所述边界节点具有分配VPN SID的能力。
在一实施例中，所述分配模块32，配置为：根据所述第二节点的能力，分配VPN标识信息。
在一实施例中，所述第二节点仅支持SRv6能力，所述分配模块32，配置为分配如下之一作为VPN标识信息：有效的VPN SID；有效的VPN SID和无效的VPN标签。
在一实施例中，所述第二节点同时支持SRv6能力和多协议标签交换MPLS能力，所述分配模块32，配置为根据配置策略分配如下之一作为VPN标识信息：有效的VPN SID和有效的VPN标签；有效的VPN SID和无效的VPN标签；有效的VPN标签和无效的VPN SID；有效的VPN SID；有效的VPN标签。
在一实施例中，所述第二节点仅支持MPLS能力，所述分配模块32，配置为分配如下之一作为VPN标识信息：有效的VPN标签；有效的VPN标签和无效的VPN SID。
在一实施例中，所述装置还包括：第一创建模块，配置为所述VPN标识信息包括VPN SID时，为分配的VPN SID创建对应的本地SID转发表项，设置所述本地SID转发表项的转发行为包括将入向的SRv6  SID交换成出向的SRv6 SID或MPLS标签。
在一实施例中，第一创建模块，配置为执行如下至少之一：所述接收模块接收到的所述携带VPN路由信息的通告消息中仅包含有效的VPN SID，设置所述本地SID转发表项的转发行为为将入向的SRv6 SID交换成出向的SRv6 SID；所述接收模块接收到的所述携带VPN路由信息的通告消息中仅包含有效的VPN标签，设置所述本地SID转发表项的转发行为为将入向的SRv6 SID交换成出向的MPLS标签；所述接收模块接收到的所述携带VPN路由信息的通告消息中包含有效的VPN SID和有效的VPN标签，根据配置策略设置所述本地SID转发表项的转发行为。
在一实施例中，所述装置还包括：泛洪模块，配置为通过内部网关协议(IGP)向所属的IGP区域泛洪包含所述VPN SID的路由信息。
在一实施例中，所述创建的本地SID转发表项中包括出向成员转发信息，所述出向成员转发信息包括下一跳节点的标识，以及所述下一跳节点对应的VPN SID或VPN标签。
在一实施例中，所述装置还包括：第一报文转发模块，配置为接收第二节点向第一节点发送的报文，根据所述报文中携带的目的地址，查找命中的本地SID转发表项，按照所述命中的本地SID转发表项的转发行为，以及所述下一跳节点对应的VPN SID或VPN标签进行转发。
在一实施例中，所述第一报文转发模块，配置为执行如下至少之一：所述本地SID转发表项的转发行为为将入向的SRv6 SID交换成出向的SRv6 SID，将所述报文的目的地址改为所述下一跳节点对应的VPN SID，将所述报文转发至所述下一跳节点；所述本地SID转发表项的转发行为为将入向的SRv6 SID交换成出向的MPLS标签，将所述报文的IPv6报文头去掉，封装MPLS标签，将所述报文的顶层标签设置为所述下一跳节点对应的VPN标签，将所述报文转发至所述下一跳节点。
在一实施例中，所述装置还包括：第二创建模块，配置为所述 VPN标识信息包括VPN标签时，为分配的VPN标签创建对应的入标签映射(ILM)转发表项，设置所述ILM转发表项的标签操作包括将入向的MPLS标签交换成出向的SRv6 SID或者MPLS标签。
在一实施例中，所述第二创建模块，配置为执行如下中的至少之一：所述接收模块接收到的所述携带VPN路由信息的通告消息中仅包含有效的VPN SID，设置所述ILM转发表项的标签操作为将入向的MPLS标签交换成出向的SRv6 SID；所述接收模块接收到的所述携带VPN路由信息的通告消息中仅包含有效的VPN标签，设置所述ILM转发表项的标签操作为将入向的MPLS标签交换成出向的MPLS标签；所述接收模块接收到的所述携带VPN路由信息的通告消息中包含有效的VPN SID和有效的VPN标签，根据配置策略设置所述ILM转发表项的标签操作。
在一实施例中，所述第二创建模块创建的ILM转发表项中包括出向成员转发信息，所述出向成员转发信息包括下一跳节点的标识，以及所述下一跳节点对应的VPN SID或VPN标签。
在一实施例中，所述装置还包括：第二报文转发模块，配置为接收所述第二节点向第一节点发送的报文，根据所述报文的顶层标签，查找命中的ILM转发表项，按照所述命中的ILM转发表项的标签操作，以及所述下一跳节点对应的VPN SID或VPN标签进行转发。
在一实施例中，所述第二报文转发模块，配置为执行如下至少之一：所述ILM转发表项的标签操作为将入向的MPLS标签交换成出向的SRv6 SID，将所述报文的顶层标签弹出，封装IPv6报文头，将所述报文的目的地址改为所述下一跳节点对应的VPN SID，将所述报文转发至所述下一跳节点；所述ILM转发表项的标签操作为将入向的MPLS标签交换成出向的MPLS标签，将所述报文的顶层标签改为所述下一跳节点对应的VPN标签，将所述报文转发至所述下一跳节点。
通过本公开实施例，弥补了SRv6技术的VPN跨域空白，可以实现VPN报文跨越多个SRv6域以及跨越SRv6域和MPLS域组成的异构网络进行传递。
下面以几个应用实例进行说明。
应用实例一
如图4所示，属于相同L3VPN客户的CE1和CE2需要跨越AS1和AS2连通，AS1和AS2均已升级支持SRv6能力。CE1和CE2均为IPv4客户(CE为IPv6客户是完全类似的)，本应用实例中假设PE1和PE2分别为CE1和CE2客户分配END.DX4类型的VPN SID并随VPNv4(VPN-IPv4 address family，见RFC4364)路由通告。比如PE2为CE2客户分配END.DX4类型的VPN SID(该VPN SID是一个IPv6地址，记为sid_dx4_ce2)，PE2上为sid_dx4_ce2维护的本地SID转发表项的FUNCTION为解封装IPv6头后向相应的IPv4链路转发。PE2上为了便于分配上述VPN SID，可以维护一个用于本地分配SID的SRv6 SID资源池，该SRv6 SID资源池实际上是一个IPv6 prefix(前缀)，记为prefix_srv6_sid_pool_pe2，为了AS2内其它节点能对上述sid_dx4_ce2可路由，PE2将prefix_srv6_sid_pool_pe2通过IGP向PE2所属的IGP区域(area)泛洪。
本应用实例中以从CE1访问CE2为例描述相应的路由通告与数据转发流程，包括如下步骤401至410。
在步骤401，PE2与ASBR2之间建立MP-IBGP邻居，PE2把从CE2学到的某条IPv4私网路由(比如CE2自身的loopback(环回)路由，记为prefix_ce2)通过BGP向ASBR2通告相应的VPNv4路由(记为vpnv4_prefix_ce2)，在BGP通告消息中携带上述sid_dx4_ce2。
在步骤402，ASBR2上配置打开具有分配VPN SID的能力，当ASBR2收到PE2通告的VPNv4路由(即vpnv4_prefix_ce2)后，本地为该vpnv4_prefix_ce2分配一个VPN SID(该VPN SID是一个IPv6地址，记为sid_br_100)。与PE2类似，ASBR2上为了便于分配上述VPN SID，可以维护一个用于本地分配SID的SRv6 SID资源池，记为prefix_srv6_sid_pool_asbr2，并通过IGP向ASBR2所属的IGP区域泛洪。
ASBR2为sid_br_100维护的本地SID转发表项的FUNCTION为将入向的SRv6 SID交换为出向的SRv6 SID或者MPLS标签，表项中只 包含一个BGP下一跳PE2及其相关的sid_dx4_ce2。
另外ASBR2还会通过IGP泛洪学习到prefix_srv6_sid_pool_PE2。
在步骤403，ASBR2与ASBR1之间建立MP-EBGP邻居，ASBR2把PE2向它通告的VPNv4路由(即vpnv4_prefix_ce2)继续向ASBR1通告，在BGP通告消息中携带上述sid_br_100，并改变BGP下一跳为自身(ASBR1和ASBR2之间的MP-EBGP会话一般基于它们之间的直连链路的接口IP地址建连，所以此处的BGP下一跳实际上是ASBR2连接ASBR1的链路的接口IP地址，从ASBR1来看，这是一个直连的IP地址。)。
在步骤404，ASBR1上配置打开具有分配VPN SID的能力，当ASBR1收到ASBR2通告的VPNv4路由(即vpnv4_prefix_ce2)后，本地为该vpnv4_prefix_ce2分配一个VPN SID(该VPN SID是一个IPv6地址，记为sid_br_200)。与ASBR2类似，ASBR1上为了便于分配上述VPN SID，可以维护一个用于本地分配SID的SRv6 SID资源池，记为prefix_srv6_sid_pool_asbr1，并通过IGP向ASBR1所属的IGP区域泛洪。
ASBR1为sid_br_200维护的本地SID转发表项的FUNCTION为将入向的SRv6 SID交换为出向的SRv6 SID或者MPLS标签，表项中只包含一个BGP下一跳ASBR2(如前所述这是一个直连IP地址)及其相关的sid_br_100。
在步骤405，ASBR1与PE1之间建立MP-IBGP邻居，ASBR1把ASBR2向它通告的VPNv4路由(即vpnv4_prefix_ce2)继续向PE1通告，在BGP通告消息中携带上述sid_br_200，并改变BGP下一跳为自身。
在步骤406，当PE1收到ASBR1通告的VPNv4路由(即vpnv4_prefix_ce2)后，根据BGP Route Target策略将该VPNv4路由导入到本地相应的VRF路由表中，建立私网路由表项prefix_ce2，表项中只包含一个BGP下一跳ASBR1及其相关的sid_br_200。
另外PE1还会通过IGP泛洪学习到prefix_srv6_sid_pool_asbr1。
在步骤407，当CE1访问CE2的IPv4报文到达PE1时，根据报文目的IP地址在相应的VRF路由表中查找命中上述私网路由表项prefix_ce2，封装外层IPv6头，IPv6头中的目的地址可直接设置为sid_br_200，然后拿sid_br_200在公网路由表中查找命中prefix_srv6_sid_pool_asbr1，报文将沿IGP最短路径(或TE(Traffic Engineering，流量工程)路径)向ASBR1转发。
在步骤408，上述IPv6报文到达ASBR1时，根据报文目的IP地址(sid_br_200)在公网路由表中查找命中相应的本地SID转发表项，由于该本地SID转发表项的FUNCTION为将入向的SRv6 SID交换为出向的SRv6 SID或者MPLS标签，且表项中只包含一个BGP下一跳ASBR2(如前所述这是一个直连IP地址)及其相关的sid_br_100，所以将IPv6报文的目的IP地址修改为sid_br_100后直接向直连下一跳ASBR2发送(这里因为BGP下一跳地址是直连IP地址，所以无需再拿sid_br_100查找路由表获取转发信息)。
在步骤409，上述IPv6报文到达ASBR2时，根据报文目的IP地址(sid_br_100)在公网路由表中查找命中相应的本地SID转发表项，由于该本地SID转发表项的FUNCTION为将入向的SRv6 SID交换为出向的SRv6 SID或者MPLS标签，且表项中只包含一个BGP下一跳PE2及其相关的sid_dx4_ce2，所以将IPv6报文的目的IP地址修改为sid_dx4_ce2后，拿sid_dx4_ce2在公网路由表中查找命中prefix_srv6_sid_pool_pe2，报文将沿IGP最短路径(或TE路径)向PE2转发。
在步骤410，上述IPv6报文到达PE2时，根据报文目的IP地址(sid_dx4_ce2)在公网路由表中查找命中相应的本地SID转发表项，由于该本地SID转发表项的FUNCTION为解封装IPv6头后向相应的IPv4链路转发(即END.DX4)，则移除IPv6头后向CE2转发。
从CE2访问CE1涉及到的路由通告与数据转发流程是类似的，不再赘述。
应用实例二
本应用实例与应用实例一基本相同，如图5所示，区别是AS1已升级支持SRv6能力，AS2仍仅支持MPLS能力。假设PE1为CE1客户分配END.DX4类型的VPN SID(记为sid_dx4_ce1)并维护相应的本地SID转发表项，PE1上也维护SRv6 SID资源池(记为prefix_srv6_sid_pool_pe1)并通过IGP向PE1所属的IGP区域泛洪。
本应用实例中先以从CE1访问CE2为例描述相应的路由通告与数据转发流程，包括如下步骤501至510。
在步骤501，PE2与ASBR2之间建立MP-IBGP邻居，PE2把从CE2学到的某条IPv4私网路由(比如CE2自身的loopback路由，记为prefix_ce2)通过BGP向ASBR2通告相应的VPNv4路由(记为vpnv4_prefix_ce2)，在BGP通告消息中携带VPN标签(记为label_ce2)。PE2为label_ce2建立相应的ILM表项，表项中给出的标签操作为弹掉标签后向CE2转发。
在步骤502，ASBR2收到PE2通告的VPNv4路由(即vpnv4_prefix_ce2)后，本地为该vpnv4_prefix_ce2分配一个VPN标签(记为label_br_100)，并为label_br_100建立相应的ILM表项，表项中只包含一个BGP下一跳PE2及其相关的label_ce2。
在步骤503，ASBR2与ASBR1之间建立MP-EBGP邻居，ASBR2把PE2向它通告的VPNv4路由(即vpnv4_prefix_ce2)继续向ASBR1通告，在BGP通告消息中携带上述label_br_100，并改变BGP下一跳为自身(ASBR1和ASBR2之间的MP-EBGP会话一般基于它们之间的直连链路的接口IP地址建连，所以此处的BGP下一跳实际上是ASBR2连接ASBR1的链路的接口IP地址，从ASBR1来看，这是一个直连的IP地址。)。
在步骤504，ASBR1上配置打开具有分配VPN SID的能力，当ASBR1收到ASBR2通告的VPNv4路由(即vpnv4_prefix_ce2)后，本地为该vpnv4_prefix_ce2分配一个VPN SID(该VPN SID是一个IPv6地址，记为sid_br_200)。ASBR1上为了便于分配上述VPN SID，可以维护一个用于本地分配SID的SRv6 SID资源池，记为prefix_srv6_sid_pool_asbr1，并通过IGP向ASBR1所属的IGP区域 泛洪。
ASBR1为sid_br_200维护的本地SID转发表项的FUNCTION为将入向的SRv6 SID交换为出向的SRv6 SID或者MPLS标签，表项中只包含一个BGP下一跳ASBR2(如前所述这是一个直连IP地址)及其相关的label_br_100。
在步骤505，ASBR1与PE1之间建立MP-IBGP邻居，ASBR1把ASBR2向它通告的VPNv4路由(即vpnv4_prefix_ce2)继续向PE1通告，在BGP通告消息中携带上述sid_br_200，并改变BGP下一跳为自身。
在步骤506，当PE1收到ASBR1通告的VPNv4路由(即vpnv4_prefix_ce2)后，根据BGP Route Target(路由目标)策略将该VPNv4路由导入到本地相应的VRF路由表中，建立私网路由表项prefix_ce2，表项中只包含一个BGP下一跳ASBR1及其相关的sid_br_200。
另外PE1还会通过IGP泛洪学习到prefix_srv6_sid_pool_asbr1。
在步骤507，当CE1访问CE2的IPv4报文到达PE1时，根据报文目的IP地址在相应的VRF路由表中查找命中上述私网路由表项prefix_ce2，封装外层IPv6头，IPv6头中的目的地址可直接设置为sid_br_200，然后拿sid_br_200在公网路由表中查找命中prefix_srv6_sid_pool_asbr1，报文将沿IGP最短路径(或TE路径)向ASBR1转发。
在步骤508，上述IPv6报文到达ASBR1时，根据报文目的IP地址(sid_br_200)在公网路由表中查找命中相应的本地SID转发表项，由于该本地SID转发表项的FUNCTION为将入向的SRv6 SID交换为出向的SRv6 SID或者MPLS标签，且表项中只包含一个BGP下一跳ASBR2(如前所述这是一个直连IP地址)及其相关的label_br_100，所以将IPv6报文头剥除后换成MPLS标签封装，变成一个MPLS报文，报文的顶层标签设置为label_br_100，然后直接向直连下一跳ASBR2发送(注意这里因为BGP下一跳地址是直连IP地址，所以无需再去迭代查找转发信息)。
在步骤509，上述MPLS报文到达ASBR2后，ASBR2根据报文顶层标签label_br_100查找ILM，将标签交换成label_ce2后穿越公网隧道至PE2。
在步骤510，报文到达PE2后，公网隧道终结，根据报文顶层标签label_ce2查找ILM，标签弹出后向CE2转发。
应用实例三
仍然如图5所示，描述从CE2访问CE1涉及到的路由通告与数据转发流程，包括如下步骤601至609。
在步骤601，PE1与ASBR1之间建立MP-IBGP邻居，PE1把从CE1学到的某条IPv4私网路由(比如CE1自身的loopback路由，记为prefix_ce1)通过BGP向ASBR1通告相应的VPNv4路由(记为vpnv4_prefix_ce1)，在BGP通告消息中携带上述sid_dx4_ce1。
在步骤602，ASBR1上配置打开具有分配VPN SID的能力，当ASBR1收到PE1通告的VPNv4路由(即vpnv4_prefix_ce1)后，本地为该vpnv4_prefix_ce1分配一个VPN SID。另外，ASBR1也具备MPLS能力，它还可为vpnv4_prefix_ce1本地分配一个VPN标签(记为label_br_300)。
ASBR1为label_br_300维护的ILM表项的标签操作为将入向的MPLS标签交换为出向的SRv6 SID或者MPLS标签，表项中只包含一个BGP下一跳PE1及其相关的sid_dx4_ce1。
另外ASBR1还会通过IGP泛洪学习到prefix_srv6_sid_pool_PE1。
在步骤603，ASBR1与ASBR2之间建立MP-EBGP邻居，ASBR1把PE1向它通告的VPNv4路由(即vpnv4_prefix_ce1)继续向ASBR2通告，在BGP通告消息中携带上述label_br_300，并改变BGP下一跳为自身(ASBR1和ASBR2之间的MP-EBGP会话一般基于它们之间的直连链路的接口IP地址建连，所以此处的BGP下一跳实际上是ASBR1连接ASBR2的链路的接口IP地址，从ASBR2来看，这是一个直连的IP地址。)。
在步骤604，ASBR2收到ASBR1通告的VPNv4路由(即vpnv4_prefix_ce1)后，本地为该vpnv4_prefix_ce2分配一个VPN标签(记为label_br_400)，并维护相应的ILM表项。继续向PE2通告该路由，在BGP通告消息中携带上述sid_br_400，并改变BGP下一跳为自身。
在步骤605，当PE2收到ASBR2通告的VPNv4路由(即vpnv4_prefix_ce1)后，根据BGP Route Target策略将该VPNv4路由导入到本地相应的VRF路由表中，建立私网路由表项prefix_ce1，表项中只包含一个BGP下一跳ASBR2及其相关的label_br_400。
在步骤606，当CE2访问CE1的IPv4报文到达PE2时，根据报文目的IP地址在相应的VRF路由表中查找命中上述私网路由表项prefix_ce1，封装VPN标签(label_br_400)后穿越公网隧道至ASBR2。
在步骤607，报文到达ASBR2时，公网隧道终结，根据报文的顶层标签label_br_400查找ILM表项，标签交换为3label_br_300后向ASBR1转发。
在步骤608，报文到达ASBR1时，根据报文的顶层标签label_br_300查找到ILM表项，其标签操作为将入向的MPLS标签交换为出向的SRv6 SID或者MPLS标签，表项中只包含一个BGP下一跳PE1及其相关的sid_dx4_ce1。于是将报文的顶层标签label_br_300弹出，重新封装IPv6头，变成一个IPv6报文，报文的目的地址填写为sid_dx4_ce1，拿sid_dx4_ce1在公网路由表中查找命中prefix_srv6_sid_pool_pe1，报文将沿IGP最短路径(或TE路径)向PE1转发。
在步骤609，上述IPv6报文到达PE1时，根据报文目的IP地址(sid_dx4_ce1)在公网路由表中查找命中相应的本地SID转发表项，由于该本地SID转发表项的FUNCTION为解封装IPv6头后向相应的IPv4链路转发(即END.DX4)，则移除IPv6头后向CE1转发。
应用实例四
如图6所示，属于相同L3VPN客户的CE1和CE2需要跨越IGP区 域1、IGP区域2以及IGP区域3连通，IGP区域1和IGP区域2均已升级支持SRv6能力，但IGP区域3仍只支持MPLS。CE1和CE2均为IPv4客户，CE2双归至PE2和PE3。本应用实例中假设PE1和PE2分别为CE1和CE2客户分配END.DX4类型的VPN SID并随VPNv4路由通告。与前面的应用实例类似，比如PE1为CE1客户分配END.DX4类型的VPN SID(记为sid_dx4_ce1)，维护的SRv6 SID资源池记为prefix_srv6_sid_pool_pe1并在IGP区域1内泛洪；PE2为CE2客户分配END.DX4类型的VPN SID(记为sid_dx4_ce2)，维护的SRv6 SID资源池记为prefix_srv6_sid_pool_pe2并在IGP区域2内泛洪。
本应用实例的处理流程与前述应用实例是类似的，不同的地方是ABR节点上为VPN SID维护的本地SID转发表项中会包含ECMP(或FRR)转发信息。步骤简述如下步骤701至708。
在步骤701，PE2通过MP-IBGP向ABR通告vpnv4_prefix_ce2，在BGP通告消息中携带sid_dx4_ce2；PE2为sid_dx4_ce2维护相应的本地SID转发表项。
在步骤702，PE3通过MP-IBGP向ABR通告vpnv4_prefix_ce2，在BGP通告消息中携带label_ce2；PE3为label_ce2维护相应的ILM表项。
在步骤703，ABR上配置打开具有分配VPN SID的能力，当ABR收到PE2或PE3通告的VPNv4路由(即vpnv4_prefix_ce2)后，本地为该vpnv4_prefix_ce2分配一个VPN SID(记为sid_br_100)。ABR维护的SRv6 SID资源池记为prefix_srv6_sid_pool_abr，并通过IGP向ABR所属的IGP区域泛洪。
ABR为sid_br_100维护的本地SID转发表项的FUNCTION为将入向的SRv6 SID交换为出向的SRv6 SID或者MPLS标签，表项中包含两个出向成员转发信息：一个是BGP下一跳PE2及其相关的sid_dx4_ce2；另一个是BGP下一跳PE3及其相关的label_ce2。这两条出向转发信息可形成ECMP或FRR。
另外ABR还会通过IGP泛洪学习到prefix_srv6_sid_pool_PE2。。
ABR通过MP-IBGP继续向PE1通告vpnv4_prefix_ce2，在BGP 通告消息中携带sid_br_100。
在步骤704，PE1收到ABR通告的VPNv4路由(即vpnv4_prefix_ce2)后，建立私网路由表项prefix_ce2，表项中只包含一个BGP下一跳ABR及其相关的sid_br_100。
另外PE1还会通过IGP泛洪学习到prefix_srv6_sid_pool_abr。
在步骤705，当CE1访问CE2的IPv4报文到达PE1时，将封装外层IPv6头，IPv6头中的目的地址可直接设置为sid_br_100，报文将沿IGP最短路径(或TE路径)向ABR转发。
在步骤706，上述IPv6报文到达ABR时，根据报文目的IP地址(sid_br_100)在公网路由表中查找命中相应的本地SID转发表项，由于该本地SID转发表项的FUNCTION为将入向的SRv6 SID交换为出向的SRv6 SID或者MPLS标签，且表项中包含两个出向成员转发信息，则：如果向第一个成员转发时将IPv6报文的目的IP地址修改为sid_dx4_ce2后查找路由表沿IGP最短路径(或TE路径)向PE2转发；如果向第二个成员转发时移除IPv6头然后重新MPLS封装，压入label_ce2标签后穿越公网隧道至PE3。
在步骤707，上述IPv6报文到达PE2后，查找并命中sid_dx_ce2相关的本地SID转发表项，解封装IPv6头后向CE2转发。
在步骤708，上述MPLS报文到达PE3后，查找并命中label_ce2相关的ILM表项，弹掉顶层标签label_ce2后向CE2转发。
应用实例五
本应用实例与应用实例四基本相同，如图7所示，仅IGP区域2已升级支持SRv6能力，但IGP区域1和IGP区域3仍只支持MPLS。本应用实例与其它应用实例不同的地方是ABR节点上维护的ILM表项中会包含ECMP(或FRR)转发信息。步骤简述如下步骤801至808。
在步骤801，PE2通过MP-IBGP向ABR通告vpnv4_prefix_ce2，在BGP通告消息中携带sid_dx4_ce2；PE2为sid_dx4_ce2维护相应的本地SID转发表项。
在步骤802，PE3通过MP-IBGP向ABR通告vpnv4_prefix_ce2， 在BGP通告消息中携带label_ce2；PE3为label_ce2维护相应的ILM表项。
在步骤803，ABR上配置打开具有分配VPN SID的能力，当ABR收到PE2或PE3通告的VPNv4路由(即vpnv4_prefix_ce2)后，本地为vpnv4_prefix_ce2分配一个VPN SID。另外ABR也具有MPLS能力，它还可以为vpnv4_prefix_ce2分配一个VPN标签(记为label_br_100)。
ABR为label_br_100维护的ILM表项的标签操作为将入向的MPLS标签交换为出向的SRv6 SID或者MPLS标签，表项中包含两个出向成员转发信息：一个是BGP下一跳PE2及其相关的sid_dx4_ce2；另一个是BGP下一跳PE3及其相关的label_ce2。这两条出向转发信息可形成ECMP或FRR。
另外ABR还会通过IGP泛洪学习到prefix_srv6_sid_pool_PE2。。
ABR通过MP-IBGP继续向PE1通告vpnv4_prefix_ce2，在BGP通告消息中携带label_br_100。
在步骤804，PE1收到ABR通告的VPNv4路由(即vpnv4_prefix_ce2)后，建立私网路由表项prefix_ce2，表项中只包含一个BGP下一跳ABR及其相关的label_br_100。
在步骤805，当CE1访问CE2的IPv4报文到达PE1时，将封装MPLS标签栈，底层标签为label_br_100，穿越公网隧道至ABR。
在步骤806，报文到达ABR时，公网隧道终结，根据报文顶层标签label_br_100，查找并命中相应的ILM表项，由于ILM表项的标签操作为将入向的MPLS标签交换为出向的SRv6 SID或者MPLS标签，且表项中包含两个出向成员转发信息，则：如果向第一个成员转发，将标签label_br_100弹出，然后重新封装IPv6头，IPv6报文的目的IP地址设置为sid_dx4_ce2，然后查找路由表沿IGP最短路径(或TE路径)向PE2转发；如果向第二个成员转发，将标签label_br_100交换成标签label_ce2，然后穿越公网隧道至PE3。
在步骤807，上述IPv6报文到达PE2后，查找并命中sid_dx_ce2相关的本地SID转发表项，解封装IPv6头后向CE2转发。
在步骤808，上述MPLS报文到达PE3后，查找并命中label_ce2相关的ILM表项，弹掉顶层标签label_ce2后向CE2转发。
应用实例六
本应用实例是针对EVPN的跨域，与前述L3VPN的跨域应用实例是完全类似的，区别是通过BGP通告的路由类型不同，而在ASBR(或ABR)节点上的处理完全类似。
比如图4中，是点到点的跨域，CE1和CE2通过PE1和PE2建立点到点的连接，ASBR2可从PE2收到Ethernet Auto-discovery Route(Type-1)(以太网自动发现路由-类型1)路由通告且其中包含有有效的SRv6 VPN SID(比如FUNCTION为END.DX2，记为sid_dx2_pe2)，ASBR2上配置具有分配VPN SID的能力，则它可以针对上述VPN路由重新分配一个新的VPN SID(记为sid_dx2_asbr2)，ASBR2将上述VPN路由继续向ASBR1通告并修改下一跳为自身，其中包含ASBR2为之新分配的VPN SID(sid_dx2_asbr2)。类似的，ASBR1上也配置具有分配VPN SID的能力，针对上述从ASBR2收到的VPN路由重新分配一个新的VPN SID(记为sid_dx2_asbr1)，ASBR1继续向PE1通告上述VPN路由并修改下一跳为自身，其中包含ASBR1为之新分配的VPN SID(sid_dx2_asbr1)。ASBR1和ASBR2上为各自新分配的VPN SID创建的本地SID转发表项的FUNCTION均为将入向的SRv6 SID交换为出向的SRv6 SID或MPLS标签。后续从CE1至CE2的报文转发时，ASBR1上将会收到IPv6报文且其目的IP为sid_dx2_asbr1，将会命中相应的本地SID转发表项，ASBR1于是将IPv6报文的目的IP交换为sid_dx2_asbr2，报文继续向ASBR2转发；类似的，ASBR2收到报文后会将报文的目的IP交换为sid_dx2_pe2，继续沿最短路径(或TE路径)向PE2转发。具体流程不再赘述。
比如图6中，是点到多点的跨域，ABR可从PE2收到MAC/IP Advertisement Route(Type-2)(MAC/IP发布路由-类型2)路由通告且其中包含有有效的SRv6 VPN SID，另外ABR还可从PE3也收到同样NLRI(Network Layer Reachability Information，网络层可达 性信息)键值的MAC/IP Advertisement Route(Type-2)路由通告且其中包含有有效的MPLS标签，则ABR上可本地分配相应的VPN SID或VPN标签，创建相应的本地SID转发表项或ILM表项，表项中包含两条形成ECMP(或FRR)的出向成员转发信息，此时相应的本地SID的FUNCTION为将入向的SRv6 SID交换为出向的SRv6 SID或MPLS标签，相应的ILM的标签操作为将入向的MPLS标签交换为出向的SRv6 SID或MPLS标签。具体流程不再赘述。
另外EVPN也定义了IP prefix route(Type-5)(IP前缀路由-类型5)以支持L3VPN业务，此时也同样可使用本公开实施例的跨域方案，具体不再赘述。
应用实例七
传统的建立PW(Pseudo-Wire，伪线路)方式的L2VPN，比如RFC4761定义了BGP VPLS NLRI路由类型，用于通告PW相关的标签。虽然当前draft-dawra-idr-srv6-vpn-02并未描述如何扩展RFC4761以支持在BGP VPLS(Virtual Private Lan Service，虚拟专用局域网业务)NLRI中携带SRv6 SID，但这种扩展是完全可行的。当BGP VPLS NLRI中也能支持携带SRv6 SID信息时，那么也同样可应用本公开实施例所描述的跨域方案，与前述应用实例相比，除了通告的路由类型不一样以外，其它完全类似，不再赘述。
如图8所示，本公开实施例还提供一种边界节点，所述边界节点支持IPv6分段路由(SRv6)能力，包括：处理器81；配置为存储所述处理器可执行指令的存储器82；配置为根据所述处理器的控制进行信息收发通信的传输装置83；其中，所述处理器81配置为执行以下操作：控制所述传输装置83接收第一节点向第二节点发送的携带VPN路由信息的通告消息；其中，所述第一节点和第二节点分别归属于不同的域；为所述VPN路由信息对应的VPN路由分配VPN标识信息，在所述通告消息中携带所述VPN标识信息，将所述通告消息发送至所述第二节点；其中，所述VPN标识信息包括VPN分段标识SID 和VPN标签中的至少之一。
本公开实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行本文所述的任一方法。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
可以理解的是，以上实施方式仅仅是为了说明本公开的原理而采用的示例性实施方式，然而本公开并不局限于此。对于本领域内的普通技术人员而言，在不脱离本公开的精神和实质的情况下，可以做出各种变型和改进，这些变型和改进也视为本公开的保护范围。

Claims (26)

  1. 一种虚拟私有网络(VPN)跨域的实现方法，包括：
    边界节点接收第一节点向第二节点发送的携带VPN路由信息的通告消息；其中，所述边界节点支持IPv6分段路由(SRv6)能力，所述第一节点和第二节点分别归属于不同的域；
    所述边界节点为所述VPN路由信息对应的VPN路由分配VPN标识信息，在所述通告消息中携带所述VPN标识信息，将所述通告消息发送至所述第二节点；其中，所述VPN标识信息包括VPN分段标识(SID)和VPN标签中的至少之一。
  2. 如权利要求1所述的方法，其中，所述边界节点接收第一节点向第二节点发送的携带VPN路由信息的通告消息之前，所述方法还包括：
    配置所述边界节点具有分配VPN SID的能力。
  3. 如权利要求1所述的方法，其中，所述边界节点为所述VPN路由信息对应的VPN路由分配VPN标识信息，包括：
    所述边界节点根据所述第二节点的能力，分配VPN标识信息。
  4. 如权利要求3所述的方法，其中，所述边界节点根据所述第二节点的能力，分配VPN标识信息，包括：
    响应于所述第二节点仅支持SRv6能力，所述边界节点分配如下之一作为VPN标识信息：
    有效的VPN SID；
    有效的VPN SID和无效的VPN标签。
  5. 如权利要求3所述的方法，其中，所述边界节点根据所述第二节点的能力，分配VPN标识信息，包括：
    响应于所述第二节点同时支持SRv6能力和多协议标签交换 (MPLS)能力，所述边界节点根据配置策略分配如下之一作为VPN标识信息：
    有效的VPN SID和有效的VPN标签；
    有效的VPN SID和无效的VPN标签；
    有效的VPN标签和无效的VPN SID；
    有效的VPN SID；
    有效的VPN标签。
  6. 如权利要求3所述的方法，其中，所述边界节点根据所述第二节点的能力，分配VPN标识信息，包括：
    响应于所述第二节点仅支持MPLS能力，所述边界节点分配如下之一作为VPN标识信息：
    有效的VPN标签；
    有效的VPN标签和无效的VPN SID。
  7. 如权利要求1所述的方法，其中，响应于所述VPN标识信息包括VPN SID，所述边界节点为所述VPN路由信息对应的VPN路由分配VPN标识信息之后，所述方法还包括：
    所述边界节点为分配的VPN SID创建对应的本地SID转发表项，所述边界节点设置所述本地SID转发表项的转发行为包括将入向的SRv6 SID交换成出向的SRv6 SID或MPLS标签。
  8. 如权利要求7所述的方法，其中，所述边界节点为分配的VPN SID创建对应的本地SID转发表项，所述边界节点设置所述本地SID转发表项的转发行为包括将入向的SRv6 SID交换成出向的SRv6 SID或MPLS标签，包括如下中的至少之一：
    响应于所述边界节点接收到的所述携带VPN路由信息的通告消息中仅包含有效的VPN SID，所述边界节点设置所述本地SID转发表项的转发行为为将入向的SRv6 SID交换成出向的SRv6 SID；
    响应于所述边界节点接收到的所述携带VPN路由信息的通告消 息中仅包含有效的VPN标签，所述边界节点设置所述本地SID转发表项的转发行为为将入向的SRv6 SID交换成出向的MPLS标签；
    响应于所述边界节点接收到的所述携带VPN路由信息的通告消息中包含有效的VPN SID和有效的VPN标签，所述边界节点根据配置策略设置所述本地SID转发表项的转发行为。
  9. 如权利要求7所述的方法，其中，所述边界节点为所述VPN路由信息对应的VPN路由分配VPN标识信息之后，还包括：
    所述边界节点通过内部网关协议(IGP)向所属的IGP区域泛洪包含所述VPN SID的路由信息。
  10. 如权利要求7所述的方法，其中，
    所述边界节点创建的本地SID转发表项中包括出向成员转发信息，所述出向成员转发信息包括下一跳节点的标识，以及所述下一跳节点对应的VPN SID或VPN标签。
  11. 如权利要求10所述的方法，其中，
    所述边界节点创建的本地SID转发表项中包括根据所述出向成员转发信息生成的等价路由(ECMP)转发信息或快速重路由(FRR)转发信息。
  12. 如权利要求10所述的方法，其中，所述边界节点为所述VPN路由信息对应的VPN路由分配VPN标识信息，在所述通告消息中携带所述VPN标识信息，将所述通告消息发送至所述第二节点之后，所述方法还包括：
    所述边界节点接收第二节点向第一节点发送的报文，根据所述报文中携带的目的地址，查找命中的本地SID转发表项，按照所述命中的本地SID转发表项的转发行为，以及所述下一跳节点对应的VPN SID或VPN标签进行转发。
  13. 如权利要求12所述的方法，其中，所述按照所述命中的本地SID转发表项中的转发行为，以及所述下一跳节点对应的VPN SID或VPN标签进行转发，包括如下中的至少之一：
    所述本地SID转发表项的转发行为为将入向的SRv6 SID交换成出向的SRv6 SID，所述边界节点将所述报文的目的地址改为所述下一跳节点对应的VPN SID，将所述报文转发至所述下一跳节点；
    所述本地SID转发表项的转发行为为将入向的SRv6 SID交换成出向的MPLS标签，所述边界节点将所述报文的IPv6报文头去掉，封装MPLS标签，将所述报文的顶层标签设置为所述下一跳节点对应的VPN标签，将所述报文转发至所述下一跳节点。
  14. 如权利要求1所述的方法，其中，所述VPN标识信息包括VPN标签时，所述边界节点为所述VPN路由信息对应的VPN路由分配VPN标识信息之后，所述方法还包括：
    所述边界节点为分配的VPN标签创建对应的入标签映射(ILM)转发表项，所述边界节点设置所述ILM转发表项的标签操作包括将入向的MPLS标签交换成出向的SRv6 SID或者MPLS标签。
  15. 如权利要求14所述的方法，其中，所述边界节点为分配的VPN标签创建对应的ILM转发表项，所述边界节点设置所述ILM转发表项的标签操作包括将入向的MPLS标签交换成出向的SRv6 SID或者MPLS标签，包括如下中的至少之一：
    所述边界节点接收到的所述携带VPN路由信息的通告消息中仅包含有效的VPN SID，所述边界节点设置所述ILM转发表项的标签操作为将入向的MPLS标签交换成出向的SRv6 SID；
    所述边界节点接收到的所述携带VPN路由信息的通告消息中仅包含有效的VPN标签，所述边界节点设置所述ILM转发表项的标签操作为将入向的MPLS标签交换成出向的MPLS标签；
    所述边界节点接收到的所述携带VPN路由信息的通告消息中包含有效的VPN SID和有效的VPN标签，所述边界节点根据配置策略设 置所述ILM转发表项的标签操作。
  16. 如权利要求14所述的方法，其中，
    所述边界节点创建的ILM转发表项中包括出向成员转发信息，所述出向成员转发信息包括下一跳节点的标识，以及所述下一跳节点对应的VPN SID或VPN标签。
  17. 如权利要求16所述的方法，其中，
    所述边界节点创建的ILM转发表项中包括根据所述出向成员转发信息生成的ECMP转发信息或FRR转发信息。
  18. 如权利要求16所述的方法，其中，所述边界节点为所述VPN路由信息对应的VPN路由分配VPN标识信息，在所述通告消息中携带所述VPN标识信息，将所述通告消息发送至所述第二节点之后，所述方法还包括：
    所述边界节点接收所述第二节点向第一节点发送的报文，根据所述报文的顶层标签，查找命中的ILM转发表项，按照所述命中的ILM转发表项的标签操作，以及所述下一跳节点对应的VPN SID或VPN标签进行转发。
  19. 如权利要求18所述的方法，其中，所述按照所述命中的ILM转发表项中的标签操作，以及所述下一跳节点对应的VPN SID或VPN标签进行转发，包括如下中的至少之一：
    所述ILM转发表项的标签操作为将入向的MPLS标签交换成出向的SRv6 SID，所述边界节点将所述报文的顶层标签弹出，封装IPv6报文头，将所述报文的目的地址改为所述下一跳节点对应的VPN SID，将所述报文转发至所述下一跳节点；
    所述ILM转发表项的标签操作为将入向的MPLS标签交换成出向的MPLS标签，所述边界节点将所述报文的顶层标签改为所述下一跳节点对应的VPN标签，将所述报文转发至所述下一跳节点。
  20. 如权利要求1至19中任意一项所述的方法，其中，
    所述边界节点包括如下至少之一：自治系统边界路由器(ASBR)和区域边界路由器(ABR)。
  21. 如权利要求1至19中任意一项所述的方法，其中，
    所述携带VPN路由信息的通告消息包括三层虚拟私有网络的通告消息、以太虚拟私有网络的通告消息和二层虚拟私有网络的通告消息中的至少之一。
  22. 一种虚拟私有网络(VPN)跨域的实现装置，应用于支持IPv6分段路由(SRv6)能力的边界节点，包括：
    接收模块，配置为接收第一节点向第二节点发送的携带VPN路由信息的通告消息；其中，所述第一节点和第二节点分别归属于不同的域；
    分配模块，配置为为所述VPN路由信息对应的VPN路由分配VPN标识信息，在所述通告消息中携带所述VPN标识信息，将所述通告消息发送至所述第二节点；其中，所述VPN标识信息包括VPN分段标识(SID)和VPN标签中的至少之一。
  23. 如权利要求22所述的装置，还包括：
    第一创建模块，配置为为分配的VPN SID创建对应的本地SID转发表项，设置所述本地SID转发表项的转发行为包括将入向的SRv6 SID交换成出向的SRv6 SID或多协议标签交换(MPLS)标签。
  24. 如权利要求22所述的装置，还包括：
    第二创建模块，配置为为分配的VPN标签创建对应的入标签映射(ILM)转发表项，设置所述ILM转发表项的标签操作包括将入向的MPLS标签交换成出向的SRv6 SID或者MPLS标签。
  25. 一种边界节点，所述边界节点支持IPv6分段路由(SRv6)能力，包括：
    处理器；
    配置为存储所述处理器可执行指令的存储器；
    配置为根据所述处理器的控制进行信息收发通信的传输装置；
    其中，所述处理器配置为执行以下操作：
    控制所述传输装置接收第一节点向第二节点发送的携带虚拟私有网络(VPN)路由信息的通告消息；其中，所述第一节点和第二节点分别归属于不同的域；
    为所述VPN路由信息对应的VPN路由分配VPN标识信息，在所述通告消息中携带所述VPN标识信息，将所述通告消息发送至所述第二节点；其中，所述VPN标识信息包括VPN分段标识(SID)和VPN标签中的至少之一。
  26. 一种计算机可读存储介质，其上存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1至19中任意一项所述的方法。
PCT/CN2019/099512 2018-08-07 2019-08-06 Vpn跨域的实现方法、装置和边界节点 WO2020029976A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US17/264,976 US11936552B2 (en) 2018-08-07 2019-08-06 Method and device for implementing VPN cross-domain, and border node
EP19846514.8A EP3836490B1 (en) 2018-08-07 2019-08-06 Vpn cross-domain implementation method, device, and border node

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810893131.5A CN110830352B (zh) 2018-08-07 2018-08-07 一种vpn跨域的实现方法、装置和边界节点
CN201810893131.5 2018-08-07

Publications (1)

Publication Number Publication Date
WO2020029976A1 true WO2020029976A1 (zh) 2020-02-13

Family

ID=69413412

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/099512 WO2020029976A1 (zh) 2018-08-07 2019-08-06 Vpn跨域的实现方法、装置和边界节点

Country Status (4)

Country Link
US (1) US11936552B2 (zh)
EP (1) EP3836490B1 (zh)
CN (1) CN110830352B (zh)
WO (1) WO2020029976A1 (zh)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112511424A (zh) * 2020-05-15 2021-03-16 中兴通讯股份有限公司 转发和转发报文的方法、头节点、转发节点、存储介质
US11012350B2 (en) * 2019-07-16 2021-05-18 Cisco Technology, Inc. Network interworking with no cross-domain state
CN113992558A (zh) * 2021-10-26 2022-01-28 新华三信息安全技术有限公司 路由发布的方法、装置、电子设备及介质
CN114157531A (zh) * 2020-08-18 2022-03-08 华为技术有限公司 传输虚拟专用网的段标识vpn sid的方法、装置和网络设备
EP3979572A1 (en) * 2020-09-30 2022-04-06 Huawei Technologies Co., Ltd. Route processing method and network device
EP4191964A4 (en) * 2020-08-18 2024-02-21 Huawei Technologies Co., Ltd. VIRTUAL PRIVATE NETWORK SEGMENT IDENTIFICATION (VPN SID) TRANSMISSION METHOD AND DEVICE, AND NETWORK DEVICE
EP4297346A4 (en) * 2021-03-19 2024-08-21 Huawei Tech Co Ltd TRAFFIC CONTROL METHOD AND RELATED DEVICE
US12126531B2 (en) 2020-09-30 2024-10-22 Huawei Technologies Co., Ltd. Route processing method and network device

Families Citing this family (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113438160B (zh) * 2020-03-23 2024-05-31 中兴通讯股份有限公司 路由方法、路由装置及计算机可读存储介质
US11233733B2 (en) * 2020-03-26 2022-01-25 Verizon Patent And Licensing Inc. Systems and methods for SR-MPLS to SRv6 interworking
CN112511995B (zh) * 2020-03-30 2024-04-26 中兴通讯股份有限公司 消息交互方法、装置、设备和存储介质
CN111464439B (zh) * 2020-03-31 2022-04-01 新华三信息安全技术有限公司 段标识发布方法和装置
CN113765789A (zh) * 2020-06-04 2021-12-07 中兴通讯股份有限公司 信息处理方法、节点及计算机可读存储介质
CN112511418A (zh) * 2020-06-22 2021-03-16 中兴通讯股份有限公司 报文指示方法、装置、设备和存储介质
CN114124776A (zh) * 2020-08-25 2022-03-01 中兴通讯股份有限公司 信息处理方法、网络控制器、节点及计算机可读存储介质
CN112511423A (zh) * 2020-09-03 2021-03-16 中兴通讯股份有限公司 报文处理方法、边界设备和计算机可读介质
US11611506B2 (en) * 2020-10-09 2023-03-21 Juniper Networks, Inc. Processing a flow at the egress node in segment routing
CN114650248B (zh) * 2020-12-02 2023-07-18 中国电信股份有限公司 路由信息的处理方法、系统和自治系统边界路由器
CN114650256A (zh) * 2020-12-17 2022-06-21 中兴通讯股份有限公司 报文处理方法、节点及计算机可读存储介质
CN115225427B (zh) * 2021-04-20 2024-05-17 华为技术有限公司 一种传输数据报文的方法和装置
CN115589382A (zh) * 2021-06-23 2023-01-10 华为技术有限公司 一种报文传输的方法及相关设备
CN115550252A (zh) * 2021-06-29 2022-12-30 华为技术有限公司 路由发布和转发报文的方法、装置、设备和存储介质
CN113872866B (zh) * 2021-09-28 2023-04-07 中国电信股份有限公司 报文转发方法、系统以及存储介质
CN115914093A (zh) * 2021-09-30 2023-04-04 中兴通讯股份有限公司 虚拟专用网络业务标识的分配方法、报文处理方法及装置
CN116112416A (zh) * 2021-11-11 2023-05-12 中兴通讯股份有限公司 报文转发方法、电子设备及存储介质
CN114205187B (zh) * 2021-12-02 2023-08-08 中盈优创资讯科技有限公司 一种适用于OptionC跨域的MPLS-VPN的端到端路径计算方法及装置
CN116264589A (zh) * 2021-12-13 2023-06-16 华为技术有限公司 一种报文传输方法及装置
CN114389996B (zh) * 2022-01-04 2023-06-09 烽火通信科技股份有限公司 一种基于资源的多拓扑环境下SRv6 SID分配的方法及装置
CN114513388B (zh) * 2022-01-17 2023-09-15 新华三技术有限公司 一种路由更新方法及装置
CN114448881B (zh) * 2022-02-25 2023-06-09 烽火通信科技股份有限公司 一种跨sr mpls与srv6域互操作通信的方法和系统
US11575596B1 (en) * 2022-03-07 2023-02-07 Ciena Corporation Identifying an ingress router of a flow in inter-AS VPN option-C networks with visibility in one AS
CN114679405B (zh) * 2022-04-12 2023-07-25 烽火通信科技股份有限公司 SRv6报文转发方法、存储介质、电子设备及装置
CN115412512B (zh) * 2022-10-31 2023-03-24 浙江九州云信息科技有限公司 一种基于IPv6的多云跨网互通方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1968178A (zh) * 2006-11-02 2007-05-23 杭州华为三康技术有限公司 Lsp的建立方法
CN105049350A (zh) * 2014-04-17 2015-11-11 思科技术公司 分段路由-出口对等工程（sp-epe）
CN105323176A (zh) * 2014-06-20 2016-02-10 中兴通讯股份有限公司 地址信息的发布方法及装置
CN106789619A (zh) * 2015-11-24 2017-05-31 华为技术有限公司 一种确定映射服务器的方法，路由节点及自治系统
WO2017141079A1 (en) * 2016-02-15 2017-08-24 Telefonaktiebolaget Lm Ericsson (Publ) Is-is extensions for flexible path stitching and selection for traffic transiting segment routing and mpls networks

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ITRM20130571A1 (it) * 2013-10-17 2015-04-18 Cisco Tech Inc Protezione di un nodo di bordo scalabile utilizzante instradamento di segmenti
US10412019B2 (en) * 2015-07-06 2019-09-10 Futurewei Technologies, Inc. Path computation element central controllers (PCECCs) for network services
US10506083B2 (en) * 2017-06-27 2019-12-10 Cisco Technology, Inc. Segment routing gateway storing segment routing encapsulating header used in encapsulating and forwarding of returned native packet

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1968178A (zh) * 2006-11-02 2007-05-23 杭州华为三康技术有限公司 Lsp的建立方法
CN105049350A (zh) * 2014-04-17 2015-11-11 思科技术公司 分段路由-出口对等工程（sp-epe）
CN105323176A (zh) * 2014-06-20 2016-02-10 中兴通讯股份有限公司 地址信息的发布方法及装置
CN106789619A (zh) * 2015-11-24 2017-05-31 华为技术有限公司 一种确定映射服务器的方法，路由节点及自治系统
WO2017141079A1 (en) * 2016-02-15 2017-08-24 Telefonaktiebolaget Lm Ericsson (Publ) Is-is extensions for flexible path stitching and selection for traffic transiting segment routing and mpls networks

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3836490A4 *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11012350B2 (en) * 2019-07-16 2021-05-18 Cisco Technology, Inc. Network interworking with no cross-domain state
CN112511424A (zh) * 2020-05-15 2021-03-16 中兴通讯股份有限公司 转发和转发报文的方法、头节点、转发节点、存储介质
CN114157531A (zh) * 2020-08-18 2022-03-08 华为技术有限公司 传输虚拟专用网的段标识vpn sid的方法、装置和网络设备
EP4191964A4 (en) * 2020-08-18 2024-02-21 Huawei Technologies Co., Ltd. VIRTUAL PRIVATE NETWORK SEGMENT IDENTIFICATION (VPN SID) TRANSMISSION METHOD AND DEVICE, AND NETWORK DEVICE
EP3979572A1 (en) * 2020-09-30 2022-04-06 Huawei Technologies Co., Ltd. Route processing method and network device
US12126531B2 (en) 2020-09-30 2024-10-22 Huawei Technologies Co., Ltd. Route processing method and network device
EP4297346A4 (en) * 2021-03-19 2024-08-21 Huawei Tech Co Ltd TRAFFIC CONTROL METHOD AND RELATED DEVICE
CN113992558A (zh) * 2021-10-26 2022-01-28 新华三信息安全技术有限公司 路由发布的方法、装置、电子设备及介质

Also Published As

Publication number Publication date
EP3836490A1 (en) 2021-06-16
EP3836490B1 (en) 2024-04-03
CN110830352B (zh) 2022-09-23
US11936552B2 (en) 2024-03-19
US20210328906A1 (en) 2021-10-21
EP3836490A4 (en) 2021-10-27
CN110830352A (zh) 2020-02-21

Similar Documents

Publication Publication Date Title
WO2020029976A1 (zh) Vpn跨域的实现方法、装置和边界节点
US11700198B2 (en) Transmission control method, node, network system and storage medium
US10237163B2 (en) Static route advertisement
CN111865796B (zh) 用于网络业务的路径计算单元中央控制器（pcecc）
WO2020156105A1 (zh) 数据转发方法及相关装置
US10484203B2 (en) Method for implementing communication between NVO3 network and MPLS network, and apparatus
JP5237391B2 (ja) リンク状態プロトコル制御型イーサネット・ネットワーク上でのｖｐｎの実装
WO2018166252A1 (zh) Evpn报文处理方法、设备及系统
WO2018166253A1 (zh) Evpn报文处理方法、设备及系统
US8259564B1 (en) Egress protection for label switched paths
EP2926507B1 (en) Methods and routers for connectivity setup between provider edge routers
EP3905609A1 (en) Service data forwarding method, network device, and network system
US9860169B1 (en) Neighbor resolution for remote EVPN hosts in IPV6 EVPN environment
WO2008098493A1 (fr) Procédé d'agrégation de routes, procédé de réacheminement de messages et routeur de frontière de système autonome
WO2019205836A1 (zh) 一种数据报文转发的方法及装置
WO2013139270A1 (zh) 实现三层虚拟专用网络的方法、设备及系统
CN102469010B (zh) 一种分配mpls标签的方法和网络设备
US20180309594A1 (en) Systems and Methods for Creating an Integrated Layer 2-Layer 3 Hybrid VPN Network
WO2020142875A1 (zh) 路由发布的方法、设备和系统
WO2021017590A1 (zh) 一种实现dci三层通信的方法、系统及第一gw
CN113726653A (zh) 报文处理方法及装置
WO2023051179A1 (zh) 边界网关协议路由的接收、发送方法及装置和存储介质
WO2024007762A1 (zh) 一种路由发布方法、通信方法及装置
Sajassi et al. Internet Engineering Task Force (IETF) J. Rabadan, Ed. Request for Comments: 8388 S. Palislamovic Category: Informational W. Henderickx
Rabadan et al. Usage and Applicability of BGP MPLS-Based Ethernet VPN

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19846514

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019846514

Country of ref document: EP

Effective date: 20210309