Method for establishing segment routing for IPv6 tunnel
AssigneeHuawei Technologies Co., Ltd.
InventorsMahendra Singh Negi, Prejeeth Kaladharan, Wumin Huang
Life of this patent
Estimating the term…
Abstract
A method for establishing a segment routing (SR) tunnel based on an Internet Protocol version 6 (IPv6) data plane using a Path Computation Element Communication Protocol (PCEP) includes generating, by a path computation element (PCE), a first PCEP message, wherein the first PCEP message comprises indicating information and segment identifier (SID), and wherein the indicating information indicates that the SID is an IPv6 prefix of a node in a tunnel; receiving, by a first path computation client (PCC), the first PCEP message from the PCE; and establishing, by the first PCC, a Segment Routing over IPv6 (SRv6) tunnel from the first PCC to a second PCC.
Claims22
A method implemented by a path computation element (PCE) and comprising:
- receiving, from a path computation client (PCC), a first Path Computation Element Communication Protocol (PCEP) message comprising a first Segment Routing over Internet Protocol version 6 (SRv6) capability type-length-value (TLV) indicating that the PCC supports SRv6;
- sending, to the PCC, a second PCEP message comprising a second SRv6 capability TLV indicating that the PCE supports SRv6;
- and
- sending, to the PCC, a third PCEP message comprising an explicit route object (ERO),
- wherein the ERO comprises an SRv6-ERO subobject, and
- wherein the SRv6-ERO subobject comprises an SRv6 segment identifier (SID).
A method implemented by a path computation client (PCC) and comprising:
- sending, to a path computation element (PCE), a first Path Computation Element Communication Protocol (PCEP) message comprising a first Segment Routing over Internet Protocol version 6 (SRv6) capability type-length-value (TLV) indicating that the PCC supports SRv6;
- receiving, from the PCE, a second PCEP message comprising a second SRv6 capability TLV indicating that the PCE supports SRv6;
- and
- receiving, from the PCE, a third PCEP message comprising an explicit route object (ERO),
- wherein the ERO comprises an SRv6-ERO subobject, and
- wherein the SRv6-ERO subobject comprises an SRv6 segment identifier (SID).
A path computation element (PCE) comprising:
- a memory configured to store instructions;
- and
- one or more processors coupled to the memory and configured to execute the instructions to cause the PCE to:
- receive, from a first path computation client (PCC), a first Path Computation Element Communication Protocol (PCEP) message comprising a first Segment Routing over Internet Protocol version 6 (SRv6) capability type-length-value (TLV) indicating that the PCC supports SRv6;
- send, to the PCC, a second PCEP message comprising a second SRv6 capability TLV indicating that the PCE supports SRv6;
- and
- send, to the PCC, a third PCEP message comprising an explicit route object (ERO),
- wherein the ERO comprises an SRv6-ERO subobject, and
- wherein the SRv6-ERO subobject comprises a first SRv6 segment identifier (SID).
A path computation client (PCC) comprising:
- a memory configured to store instructions;
- and
- one or more processors coupled to the memory and configured to execute the instructions to cause the PCC to:
- send, to a path computation element (PCE), a first Path Computation Element Communication Protocol (PCEP) message comprising a first Segment Routing over Internet Protocol version 6 (SRv6) capability type-length-value (TLV) indicating that the PCC supports SRv6;
- receive, from the PCE, a second PCEP message comprising a second SRv6 capability TLV indicating that the PCE supports SRv6;
- and
- receive, from the PCE, a third PCEP message comprising an explicit route object (ERO),
- wherein the ERO comprises an SRv6-ERO subobject, and
- wherein the SRv6-ERO subobject comprises a first SRv6 segment identifier (SID).
Dependencies are inferred from the claim text.