One document matched: draft-fuxh-pce-boundary-explicit-control-framework-00.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="no"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" docName="draft-fuxh-pce-boundary-explicit-control-framework-00" ipr="trust200902">
<front>
<title abbrev="Framework for Region Boundary Control">
A Framework for Explicit Control of Region Boundary in PCE-Based Inter-Layer Architecture
</title>
<author fullname="Xihua Fu" initials="X" surname="Fu">
<organization>ZTE Corporation</organization>
<address>
<postal>
<street>West District,ZTE Plaza,No.10,Tangyan South Road,Gaoxin District</street>
<city>Xi An</city>
<code>710065</code>
<country>P.R.China</country>
</postal>
<phone>+8613798412242</phone>
<email>fu.xihua@zte.com.cn</email>
<uri>http://wwwen.zte.com.cn/</uri>
</address>
</author>
<author fullname="Xuefeng Lin" initials="X" surname="Lin">
<organization>ZTE Corporation</organization>
<address>
<postal>
<street>12F,ZTE Plaza,No.19,Huayuan East Road,Haidian District</street>
<city>Beijing</city>
<code>100191</code>
<country>P.R.China</country>
</postal>
<phone>+8615901011821</phone>
<email>lin.xuefeng@zte.com.cn</email>
<uri>http://www.zte.com.cn/</uri>
</address>
</author>
<author fullname="Gang Xie" initials="G" surname="Xie">
<organization>ZTE Corporation</organization>
<address>
<postal>
<street>12F,ZTE Plaza,No.19,Huayuan East Road,Haidian District</street>
<city>Beijing</city>
<code>100191</code>
<country>P.R.China</country>
</postal>
<phone>+8613691280432</phone>
<email>xie.gang@zte.com.cn</email>
</address>
</author>
<date year="2010"/>
<area>Routing</area>
<workgroup>Network Working Group</workgroup>
<keyword>Explicit Control</keyword>
<keyword>Region Boundary</keyword>
<keyword>Inter-Layer</keyword>
<keyword>PCE</keyword>
<abstract>
<t>This document defines the framework for explicit control of region boundary in PCE-based inter-layer architecture.</t>
</abstract>
<note title="Conventions Used In This Document">
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <xref target="RFC2119">RFC 2119</xref>.
</t>
</note>
</front>
<middle>
<section title="Introduction">
<t>PCE can determine regions' boundaries. Without cooperating with VNTM or policy configuration, a intermediate LSR has to determine regions' boundaries by using the IGP database and ERO as described in [RFC4206] in order to trigger the lower layer signaling. A centralized routing and distributed signaling application is foreseen in the PCE architecture. Without any or enough TED within the intermediate LSR, it could not determine regions' boundaries during the signaling.</t>
<t>This document defines the framework for explicit control of region boundary in PCE-based inter-layer architecture.</t>
</section>
<section title="Explicit Control of Region Boundary">
<t>PCE can determine regions' boundaries. After PCE compute an end-to-end paths across multi-layer, multi-layer EROs must be carried in PCRep and Path message in terms of RFC5623. In order to explicit control of regions' boundaries, a new object (ERBO- Explicit Region Boundary Object) could be introduced to be carried in PCRep and Path message. Regions' boundaries should be carried in ERBO. [draft-fuxh-ccamp-region-boundary-explicit-control-rsvp-ext-00] defines the RSVP-TE signaling extension for explicit control of region boundary during the signaling procedure. [draft-fuxh-pce-region-boundary-explicit-control-pcep-ext-00] deinfes the PCEP protocol extension for explicit control of region boundary in PCE-based inter-layer architecture.</t>
</section>
<section title="Explicit Control Model of Region Boundary">
<section title="Explicit Region Control in Single PCE Inter-Layer">
<t>The process of creating a LSP from H1 to H6 is as follows:
<list style="numbers">
<t>H1 sends a route request to PCE,and PCE responses to H1 with ERO = {H1,H2,L3,L4,H5, H6} and ERBO = {H2,H5}.</t>
<t>H1 Sends Path to H2 with ERO = {H2,L3,L4,H5,H6} and ERBO = {H2, H5}.</t>
<t>After H2 receivs the Path message, H2 confirm that it is the initiator of lower layer LSP in terms of the ERBO, and extracts the complete route of the lower layer LSP in terms of the other end of the region.</t>
<t>Then H2 starts the creation of lower layer LSP, the route is H2,L3,L4,H5.</t>
<t>After the creation of the lower layer LSP, the Higher-Layer LSP's creation is to be continued. And the ERO and ERBO in the Path message is cut out.</t>
</list>
</t>
<figure>
<artwork align="center">
<![CDATA[
-----
| PCE |
-----
^ |
| 2:PCRep
| | (ERO) (ERBO)
| | ---- ----
| | | H1 | | H2 |
| | ---- ----
| | | H2 | | H5 |
| | ---- ----
| | | L3 |
| | ----
| | | L4 |
| | ----
| | | H5 |
| | ----
| | | H6 |
| | ----
| |
1:PCReq |
| v
----- ----- ----- -----
| LSR |--| LSR |................| LSR |--| LSR |
| H1 | | H2 | | H5 | | H6 |
----- -----\ /----- -----
\----- -----/
| LSR |--| LSR |
| L3 | | L4 |
----- -----
---------------> --------------->
3:Path 4:Path
(ERO) (ERBO) (ERO)
---- ---- ----
| H2 | | H2 | | H2 |
---- ---- ----
| L3 | | H5 |
---- ----
| L4 |
----
| H5 |
----
| H6 |
----]]>
</artwork>
</figure>
</section>
<section title="Explicit Region Control in Multiple PCE Inter-Layer">
<t>The process of creating a LSP from H1 to H10 is as follows:
<list style="numbers">
<t>H1 sends a route request to PCE Ho. PCE Ho computes a multi-layer path with inter-communication with PCE Lo, and responses to H1 with ERO = {H1,H2,L3,M1,M2,L4,H5,H6,L7,L8,H9,H10} and ERBO ={H2,H5,L3,L4,H6,H9}.</t>
<t>H1 Sends Path to H2 with ERO = {H2,L3,M1,M2,L4,H5,H6,L7,L8,H9,H10}, ERBO = {H2,H5,L3,L4,H6,H9}</t>
<t>After H2 receives the Path, H2 is to create lower layer LSP with ERO = {H2,L3,M1,M2,L4,H5}.</t>
<t>H2 Sends Path to L3 with ERO = {L3,M1,M2,L4,H5} and ERBO = {L3,L4}.</t>
<t>After L3 receives the Path, L3 is to create lower layer LSP with ERO = {L3,M1,M2,L4}.</t>
<t>L3 Sends Path to M1 with ERO = {M1,M2,L4} and ERBO = NULL.</t>
<t>After the creation of the lower layer LSP between L3 and L4, L3 continues to send Path to L4 with ERO = {L4,H5} and ERBO = NULL.</t>
<t>After the creation of the lower layer LSP between H2 and H5, H2 continues to send Path to H5 with ERO = {H5,H6,L7,L8,H9,H10} and ERBO = {H6,H9}.</t>
<t>After H6 receives the Path, H6 create the lower layer LSP with ERO = {H6,L7,L8,H9} and ERBO = NULL.</t>
<t>After the creation of the lower layer LSP between H6 and H9, the higher layer LSP's creation is to be continued. </t>
</list>
</t>
<figure>
<artwork align="center">
<![CDATA[
-----
| PCE |
| Hi | <----------------------
----- |
^ | |
| | |
| | |
| | |
| | |
| v |
----- ----- | ----- ----- ----- -----
| LSR |--| LSR |.............|...............| LSR |--| LSR | .............| LSR |--| LSR |
| H1 | | H2 | v | H5 | | H6 | | H9 | | H10 |
----- -----\ ----- /----- -----\ /----- -----
| | PCE | | | |
| | Lo | | | |
| ----- | | |
\----- -----/ \----- -----/
| LSR |................| LSR | | LSR |..| LSR |
| L3 | | L4 | | L7 | | L8 |
-----\ /----- ----- -----
| |
| |
| |
\----- -----/
| LSR |..| LSR |
| M1 | | M2 |
----- -----]]>
</artwork>
</figure>
<t>The process of creating a LSP from H1 to H10 is as follows:
<list style="numbers">
<t>H1 sends a route request to PCE Ho. PCE Ho computes a multi-layer path without inter-communication with PCE Lo, and responses to H1 with ERO = {H1,H2,M3,M8,H9,H10} and ERBO ={H2,H9}.</t>
<t>H1 Sends Path to H2 with ERO = {H2,M3,M8,H9,H10} and ERBO = {H2,H9}.</t>
<t>After H2 receives the Path, H2 is to create lower layer LSP with ERO = {H2,M3,M8,H9}.</t>
<t>H2 Sends Path to M3,with ERO = {M3,M8,H9} and ERBO = NULL.</t>
<t>M3 consults the PCE Lo with responsibility for the lower-layers network. PCE Lo computes the route to expand the loose hop route (i.e., M3 and M8) in the higher-layer LSP and responses to M3 with ERO = {M3,L4,L5,L6,L7,M8}, ERBO ={L4,L7}.</t>
<t>M3 Sends Path to L4, with ERO = {L4,L5,L6,L7,M8}, ERBO = {L4,L7}.</t>
<t>L4 Sends Path to L5, with ERO = {L5,L6,L7} and ERBO = NULL.</t>
<t>After the creation of the lower layer LSP between L4 and L7, L4 continues to send Path to L7 with ERO = {L7,M8} and ERBO = NULL.</t>
<t>After the creation of the lower layer LSP between M3 and M8, M3 continues to send Path to M8 with ERO = {M8,H9} and ERBO = NULL.</t>
<t>After the creation of the lower layer LSP between H2 and H9, H2 continues to send Path to H9 with ERO = {H9,H10} and ERBO = NUL.</t>
</list>
</t>
<figure>
<artwork align="center">
<![CDATA[
-----
| PCE |
| Hi |
-----
^ |
| |
| |
| |
| |
| v
----- ----- ----- -----
| LSR |--| LSR |..........................................| LSR |--| LSR |
| H1 | | H2 | | H9 | | H10 |
----- -----\ /----- -----
| |
| |
| |
\----- -----/
| LSR |............................ | LSR |
| M3 |<------------- | M8 |
-----\ | /-----
| v |
| ----- |
| | PCE | |
| | Lo | |
| ----- |
\----- -----/
| LSR |...............| LSR |
| L4 | | L7 |
-----\ /-----
| |
| |
| |
\----- -----/
| LSR |..| LSR |
| L4 | | L7 |
----- -----]]>
</artwork>
</figure>
</section>
</section>
<section title="Protocol Extension Requirements for Explicit Control of Region Boundary">
<t>A requirements for PCRep (RFC5440) extensions to support explicit control of region boundary is foreseen. A requirements for Path (RFC3473) extensions to support explicit control of region boundary is also foreseen. A new object could be introduced in PCRep and Path message. The format of new object is the same as an ERO. [draft-fuxh-pce-region-boundary-explicit-control-pcep-ext-00] deinfes the PCEP protocol extension for explicit control of region boundary in PCE-based inter-layer architecture.</t>
</section>
<section title="Security Considerations">
<t>TBD</t>
</section>
<section title="IANA Considerations">
<t>TBD</t>
</section>
</middle>
<back>
<references title="Normative References">
<?rfc include='reference.RFC.2119'?>
<?rfc include='reference.RFC.4206'?>
</references>
<references title="Informative References">
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 08:54:42 |