<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.6.39 (Ruby 3.0.2) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-sheng-idr-gw-exchange-in-sd-wan-00" category="std" consensus="true" submissionType="IETF" xml:lang="en" version="3">
  <!-- xml2rfc v2v3 conversion 3.17.4 -->
  <front>
    <title abbrev="Gateway Info Exchange in SDWAN">Corresponding Gateway Exchange in Multi-segment SD-WAN</title>
    <seriesInfo name="Internet-Draft" value="draft-sheng-idr-gw-exchange-in-sd-wan-00"/>
    <author initials="C." surname="Sheng" fullname="Cheng Sheng">
      <organization>Huawei</organization>
      <address>
        <postal>
          <street>Beiqing Road</street>
          <city>Beijing</city>
        </postal>
        <email>shengcheng@huawei.com</email>
      </address>
    </author>
    <author initials="H." surname="Shi" fullname="Hang Shi" role="editor">
      <organization>Huawei</organization>
      <address>
        <postal>
          <street>Beiqing Road</street>
          <city>Beijing</city>
          <country>China</country>
        </postal>
        <email>shihang9@huawei.com</email>
      </address>
    </author>
    <author initials="L." surname="Dunbar" fullname="Linda Dunbar">
      <organization>Futurewei</organization>
      <address>
        <email>linda.dunbar@futurewei.com</email>
      </address>
    </author>
    <date year="2023" month="July" day="25"/>
    <area>Routing</area>
    <workgroup>Inter-Domain Routing</workgroup>
    <keyword>Multi-segment SD-WAN</keyword>
    <abstract>
      <?line 45?>

<t>The document describes the control plane enhancement for multi-segment SD-WAN to exchange the corresponding GW information between edges.</t>
    </abstract>
  </front>
  <middle>
    <?line 49?>

<section anchor="intro">
      <name>Introduction</name>
      <t>To interconnect geographically faraway branches or SASE resources, multi-segment SD-WAN is often deployed via cloud backbone<xref target="I-D.draft-dmk-rtgwg-multisegment-sdwan"/>. As shown in <xref target="Scenario"/>, CPE 1 and CPE 2 are connected to the nearest Cloud GW in different regions. For the traffic from CPE 1 to CPE 2, the CPE 1 will encapsulate the address of the egress GW(GW3) and destination CPE(CPE2) in the dataplane(see <xref section="5.2" sectionFormat="of" target="I-D.draft-dmk-rtgwg-multisegment-sdwan"/>). To accomplish that, CPE needs to know their peers' corresponding GW addresses. This document proposes an control plane enhancement based on <xref target="I-D.draft-ietf-idr-sdwan-edge-discovery"/> to exchange the corresponding GW address between CPEs.</t>
      <figure anchor="Scenario">
        <name>Multi-segment SD-WAN</name>
        <artwork><![CDATA[
  (^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^)
  (            Region2             )
  (            +-----+             )
  (            | GW2 |             )
  (            +-----+             )
  (           /       \            )
  (          /  Cloud  \           )
  (         /  Backbone \          )
  ( Region1/             \Region3  )
  ( +-----+               +-----+  )
  ( | GW1 |---------------| GW3 |  )
  ( +--+--+               +--+--+  )
  (^^^^|^^^^^^^^^^^^^^^^^^^^^|^^^^^)
       |                     |   
    +--+--+               +--+--+ 
    |CPE 1|               |CPE 2|
    +-----+               +-----+
]]></artwork>
      </figure>
    </section>
    <section anchor="requirements-language">
      <name>Requirements Language</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

</section>
    <section anchor="corresponding-gw-sub-tlv">
      <name>Corresponding GW Sub-TLV</name>
      <t>Corresponding GW Sub-TLV within the Hybrid Underlay Tunnel UPDATE indicates the address of the corresponding GW. 
The following is the structure of the Corresponding GW Sub-TLV:</t>
      <artwork><![CDATA[
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Type=TBD2 (C-GW  subTLV)     |  Length (2 Octets)            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Corresponding GW Addr Family  | Address                       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ (variable)                    +
   ~                                                               ~
   |             Corresponding GW Address                          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>This document does not introduce any new security considerations.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>TBD.</t>
    </section>
  </middle>
  <back>
    <references>
      <name>Normative References</name>
      <reference anchor="I-D.draft-dmk-rtgwg-multisegment-sdwan">
        <front>
          <title>Multi-segment SD-WAN via Cloud DCs</title>
          <author fullname="Kausik Majumdar" initials="K." surname="Majumdar">
            <organization>Microsoft</organization>
          </author>
          <author fullname="Linda Dunbar" initials="L." surname="Dunbar">
            <organization>Futurewei</organization>
          </author>
          <author fullname="Venkit Kasiviswanathan" initials="V." surname="Kasiviswanathan">
            <organization>Arista</organization>
          </author>
          <author fullname="Ashok Ramchandra" initials="A." surname="Ramchandra">
            <organization>Microsoft</organization>
          </author>
          <date day="31" month="May" year="2023"/>
          <abstract>
            <t>   The document describes the methods to optimize the stitching of
   multiple SD-WAN segments on transit nodes across Cloud DCs.

            </t>
          </abstract>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-dmk-rtgwg-multisegment-sdwan-00"/>
      </reference>
      <reference anchor="I-D.draft-ietf-idr-sdwan-edge-discovery">
        <front>
          <title>BGP UPDATE for SD-WAN Edge Discovery</title>
          <author fullname="Linda Dunbar" initials="L." surname="Dunbar">
            <organization>Futurewei</organization>
          </author>
          <author fullname="Susan Hares" initials="S." surname="Hares">
            <organization>Hickory Hill Consulting</organization>
          </author>
          <author fullname="Robert Raszuk" initials="R." surname="Raszuk">
            <organization>Arrcus</organization>
          </author>
          <author fullname="Kausik Majumdar" initials="K." surname="Majumdar">
            <organization>Microsoft</organization>
          </author>
          <author fullname="Gyan Mishra" initials="G. S." surname="Mishra">
            <organization>Verizon</organization>
          </author>
          <author fullname="Venkit Kasiviswanathan" initials="V." surname="Kasiviswanathan">
            <organization>Arista</organization>
          </author>
          <date day="23" month="June" year="2023"/>
          <abstract>
            <t>   The document describes the encoding of BGP UPDATE messages for the
   SD-WAN edge node property discovery.

   In the context of this document, BGP Route Reflector (RR) is the
   component of the SD-WAN Controller that receives the BGP UPDATE from
   SD-WAN edges and in turns propagates the information to the intended
   peers that are authorized to communicate via the SD-WAN overlay
   network.

            </t>
          </abstract>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-ietf-idr-sdwan-edge-discovery-10"/>
      </reference>
      <reference anchor="RFC2119">
        <front>
          <title>Key words for use in RFCs to Indicate Requirement Levels</title>
          <author fullname="S. Bradner" initials="S." surname="Bradner"/>
          <date month="March" year="1997"/>
          <abstract>
            <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="2119"/>
        <seriesInfo name="DOI" value="10.17487/RFC2119"/>
      </reference>
      <reference anchor="RFC8174">
        <front>
          <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
          <author fullname="B. Leiba" initials="B." surname="Leiba"/>
          <date month="May" year="2017"/>
          <abstract>
            <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
          </abstract>
        </front>
        <seriesInfo name="BCP" value="14"/>
        <seriesInfo name="RFC" value="8174"/>
        <seriesInfo name="DOI" value="10.17487/RFC8174"/>
      </reference>
    </references>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA61X6XLbNhD+z6fYKj9q14Yi0U4Ta3JUluTYM/JRS64n07Qd
kAQp1BTAAKAV1cez9Fn6ZF2AoizadOJOClsSsFwsvj2xJIR42lAR/UFTKVgH
jMqZF1LDEqnmHdAm8nQeTLnWXIrxPEOWg8F4z+OZcsza+K3WTsv3UiqSDjDh
eYabFNl6UimmMykiLhJ4jyJndA6Dz+EEORlwAYd5ajjRLJkyYWDUJ+fdI48G
gWKXneWGAxHLyq5R37JFMhR0isdEisaG6AkTCeGRIsmMsAU34YLoiMyoIK2W
JwMtU2aY7nh5FlE3eQZ20gG/5fukZf+BEEcDriHmacoieybNjZxSw0OapnMI
5vB5mvoqDoHHIKSBhF9azalitAONU5kb1LnhzaS6SJTMMyQeCMMU6aMYlLfk
8C5mHQ+A1NvCw3MnUiEHQSYuNFq1CSOrK64L/Xt2taRJlVDB/0KoUnRgP6cz
xpGsjWLMdGCX8U/WG6eSRkgOuZk74p/c7WYILkWnW2Gh/fpp4iQ0QzldwbBv
MfAlgn3qAPDHj1/K5dYvOxWpoKSNFhZxI9XToYYyF8ZGaG/CBUVwUKIbNqGf
i4CqJcAhFxG9I1ZB7uUmV6yCM7X8zcjx/xSXzx1czyMYIDRAlDQ0njeeMMBQ
zJ3XIqZDxQOmwSA5lAhQppBhZjBMDFQ9ZI4vlgqmNf4GI6GM3YWISgqdo4K4
d+qQQ8DMjDGBlkuYbhbApjyKUuZhXB/Yw6M8dKxXz7hd3iBeiTIwEBGcYCEG
LpOJotlkEdkxVdQmXaAQ7AQVQaSj7mgACEPmKmR6sx45ZouMDaKJWJbKOWbN
JacQpjKPIKDhRYDF5erquwPSbxYJG00viDLJLCFO3kIcpitm681NE7oaw0XO
hM2+q6tRyARVXN7cbELvZABtwJLlZj5g0sFCHTwWTWgtJxiStYGeQ+AsBxGP
Y6YsaMUSNItuwh7qZ9nRm3HMQ4iVnC4OQEFO/qZjKGgzLAjoyZBmOk9tkbCP
aBThUVZ/t2SJW70/X3t/vrXucGJcYLYXXkNBa/jx1y0iy4/FhroQWdOMWVVZ
4bMXTd+KfKrF1puAvqUhBmmWcj1B2dQUxhKMRdrqcyHkzJ7JFWSMKf39wwBb
KIMBBeMJOnUZ25mSmUQ6KvSFyA6oRh/YiFv1NWcmdrXZYSU2YEnEdSgvmZrf
3Hw97EsTlyGPWtmIv729xaRd+/0rY90ywco4de73V0nwgGmD2LHxZaZrROfj
9zdLer74/fgFJuQpwrnCVWVCnt1Fuq1yFUyF3u3nsDo+FtStkqkO7YoOBZPV
uw3XpDosdctaYylpo1bSxp0k65/rWq9dL33nxjXUDUv1KlJrz3Is1y6H78tx
VP+6FPK46i7arjrwrKxFAK7RedOou7obWGuxCp+yTzlXLjc0DDHAc5qw4ta4
YHPA/gAzs3F4Nho3NotfODp289PBz2cHp4O+nY/2u8PhcuItOEb7x2fD/t3s
bmfv+PBwcNQvNiMVKiSvcdj9gE9sZWocn4wPjo+6w0ZRjlYz3tZVzMyAFTdG
ppitr1R75TXnOqPd3sk/f7e3bcKf7vX8dnsHE7pYvGq/3MbFDBuJ4jQp8Iop
lpjmc49mGZZp119hXcWqyg1N8YahZe2fYLnGPP/hV2uZ3zrwOgiz9vbbBcEq
XCGWNqsQnc0eUh5sLoxYQ6o5ZmnNCv2epat4ux8q69LuK8TX77DvYEDar969
dcHTu18GR3lAxsNfPO+xJ3hBoQ+Le2V/HigewZmImErxSh/neEWmcHbS744H
aPOI2y5f111h9+tvE1zExjJN5cySeLENmyBsMLA7Kjc+hqtT1mqAFl6jPmzB
NryAH+ElvIKd/0LzXEJ+459XVA77NvNmvNv3Ya1HECzgiw6CXS8ryxAbYDOB
NR+OsbUwer1SN/5HJA/M1kV/wB6dcswXfN5duKd+PA0JrF1i0aJBytbrhDgk
t4+c8NRxuzDsyqhV7XFdnqzOVw1r4w1zCLupXOGrAwIRmmMquC5M2xK8Wusi
iZlgX+T4om3GnBBz7JxmoEsJYUVC0zXZ3aPuQ8m7/UU3bhtf71989LlTYg8A
AA==

-->

</rfc>
