MIME-Version: 1.0
References: <MWHPR1301MB2096E56F2D64346B8FD2085B85F00@MWHPR1301MB2096.namprd13.prod.outlook.com>
In-Reply-To: <MWHPR1301MB2096E56F2D64346B8FD2085B85F00@MWHPR1301MB2096.namprd13.prod.outlook.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 23 Mar 2020 20:27:34 +0100
Message-ID: <CAOj+MMH=oXPOt3ozQvEHkGv6kjh6XdPRfnBDVX9Uxzcvw1pfjQ@mail.gmail.com>
To: Linda Dunbar <linda.dunbar@futurewei.com>
Cc: Huaimo Chen <huaimo.chen@futurewei.com>, "idr@ietf.org" <idr@ietf.org>, 
 "bess@ietf.org" <bess@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003b549d05a18aa126"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/QbmjdVogO1vKlt_htDzyeN2afQM>
Subject: Re: [Idr] Seeking feedback of draft-dunbar-idr-sdwan-port-safi
 using SDWAN SAFI to encode SDWAN Instance ID in the NLRI
Precedence: list

--0000000000003b549d05a18aa126
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Linda,

I think you are mixing data plane and control plane.

In SDWAN data plane is of no issue as you are interconnecting sites in a
given VPN over mesh of secure tunnels.

You are asking how to keep control plane separate between VPN instances.
This is precisely what RFC4364 does already and RT import/export is used to
indicate the instance which given set of reachability belongs. Why to
reinvent the wheel and do something new just for the heck of it :) ?

To be original you can at best invent a different name to Route target(s)
carried in the SAFI 128 but let's keep the mechanism the same. That would
be my suggestion.

Kind regards,
R.

PS. While this is obvious for some many folks are still confused. RFC4364
does not need to run over MPLS data plane. It can run over IPSec or over
DTLS or over UDP/IP just fine.

On Mon, Mar 23, 2020 at 6:47 PM Linda Dunbar <linda.dunbar@futurewei.com>
wrote:

> IDR experts:
>
>
>
> SDWAN is an overlay network arching over multiple types of networks. A
> SDWAN edge node may need to map client traffic to different SDWAN network
> instances (or segmentations).
>
> It might not be feasible to use the AS number in the BGP message to
> differentiate the SDWAN network instances as multiple SDWAN instances may
> share the same AS number.
>
>
>
> We would like to hear feedback from IDR group on using similar method as
>  Binding MPLS Labels to Address Prefixes [RFC8277] to bind SDWAN Instance
> ID to  prefixes.
>
>
>
> When  MPLS VPN SAFI (=3D128) is present, MPLS label is carried by NLRI
> [RFC8277] as:
>
>
>
>       0                   1                   2                   3
>
>       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
>
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>      |    Length     |                 Label                 |Rsrv |S|
>
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>      |                          Prefix                               ~
>
>      ~                                                               |
>
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>
>                        Figure 2: NLRI with One Label
>
>
>
> We would like to  propose the SDWAN Instance ID being encoded in the Labe=
l
> field as follows when SDWAN SAFI (=3D74 allocated by IANA) is used,:
>
>
>
>       0                   1                   2                   3
>
>       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
>
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>      |    Length     |      SDWAN Instance ID (Label)        |Rsrv |S|
>
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>      |                          Prefix                               ~
>
>      ~                                                               |
>
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>
>                         NLRI with SDWAN Instance ID.
>
>
>
> Greatly appreciate any comments or other suggestions..
>
>
>
> Thank you,
>
> Linda Dunbar
>
>
>
> *From:* Huaimo Chen <huaimo.chen@futurewei.com>
> *Sent:* Monday, March 23, 2020 9:14 AM
> *To:* Linda Dunbar <linda.dunbar@futurewei.com>; idr@ietf.org
> *Cc:* bess@ietf.org
> *Subject:* Re: [Idr] FW: Is there any problem of using Private AS as
> "Identifier" to differentiate SD-WAN Segmentation for
> draft-dunbar-bess-bgp-sdwan-usage?
>
>
>
> Hi Linda,
>
>
>
>     It seems that using another SAFI is a possible solution.
>
>
>
> Best Regards,
>
> Huaimo
> ------------------------------
>
> *From:* Linda Dunbar <linda.dunbar@futurewei.com>
> *Sent:* Friday, March 20, 2020 12:54 AM
> *To:* Huaimo Chen <huaimo.chen@futurewei.com>; idr@ietf.org <idr@ietf.org=
>
> *Cc:* bess@ietf.org <bess@ietf.org>
> *Subject:* RE: [Idr] FW: Is there any problem of using Private AS as
> "Identifier" to differentiate SD-WAN Segmentation for
> draft-dunbar-bess-bgp-sdwan-usage?
>
>
>
> Huaimo,
>
>
>
> Thank you very much for the suggestion.
>
> Do you mean using the similar approach as VPN Label carried by NLRI Path
> Attribute [RFC8277] for SDWAN Segmentation Identifier?
>
> If yes, the UPDATE message should not use the MPLS VPN SAFI (=3D128) to
> avoid confusion, right?
>
>
>
> Linda
>
>
>
> *From:* Huaimo Chen <huaimo.chen@futurewei.com>
> *Sent:* Thursday, March 19, 2020 6:45 PM
> *To:* Linda Dunbar <linda.dunbar@futurewei.com>; idr@ietf.org
> *Cc:* bess@ietf.org
> *Subject:* Re: [Idr] FW: Is there any problem of using Private AS as
> "Identifier" to differentiate SD-WAN Segmentation for
> draft-dunbar-bess-bgp-sdwan-usage?
>
>
>
> Hi Linda,
>
>
>
>     It seems that a label may be used as an "Identifier" to differentiate
> SD-WAN Segmentation.
>
>
>
> Best Regards,
>
> Huaimo
> ------------------------------
>
> *From:* Idr <idr-bounces@ietf.org> on behalf of Linda Dunbar <
> linda.dunbar@futurewei.com>
> *Sent:* Thursday, March 19, 2020 1:22 PM
> *To:* idr@ietf.org <idr@ietf.org>
> *Cc:* bess@ietf.org <bess@ietf.org>
> *Subject:* [Idr] FW: Is there any problem of using Private AS as
> "Identifier" to differentiate SD-WAN Segmentation for
> draft-dunbar-bess-bgp-sdwan-usage?
>
>
>
> BGP Experts,
>
>
>
> Do you know if  there is any problem of using  Private AS as  "Identifier=
"
> to differentiate SD-WAN Segmentation? Here is the discussion in BESS WG.
> Want to get IDR WG feedbacks for this question.
>
>
>
> Thank you.
>
> Linda
>
>
>
> *From:* Linda Dunbar
> *Sent:* Thursday, March 19, 2020 11:54 AM
> *To:* Najem, Basil <basil.najem@bell.ca>; bess@ietf.org
> *Cc:* draft-dunbar-bess-bgp-sdwan-usage@ietf.org
> *Subject:* Is there any problem of using Private AS as "Identifier" to
> differentiate SD-WAN Segmentation for draft-dunbar-bess-bgp-sdwan-usage?
>
>
>
> Based on Basil=E2=80=99s comment on needing an identifier to differentiat=
e SDWAN
> instances, I added a section to  draft-dunbar-bess-bgp-sdwan-usage . Want
> to hear people=E2=80=99s feedback.
>
>
> 3.1    Requirements 3.1.1Supporting Multiple SDWAN Segmentations
>
> The term =E2=80=9Cnetwork segmentation=E2=80=9D is used extensively in SD=
WAN deployment.
> In general (and in this document), the =E2=80=9CNetwork Segmentation=E2=
=80=9D is referring
> to the process of dividing the network into logical sub-networks using
> isolation techniques on a forwarding device such as a switch, router, or
> firewall. For a homogeneous network, such as MPLS VPN or Layer 2 network,
> VRF or VLAN are used to separate network segments.
>
> As SDWAN is an overlay network arching over multiple types of networks, i=
t
> is important to have distinct identifiers to differentiate SDWAN network
> instances (or segmentations). When different SDWAN network segments do no=
t
> have their own assigned AS numbers, a very easy way is to use Private AS
> numbers, in the range of 64512 to 65535, to differentiate different SDWAN
> segmentations.. When using BGP to control the SDWAN networks, the Private
> AS numbers are carried by the BGP UPDATE messages to their corresponding
> RRs.
>
>
>
> Greatly appreciate any feedback on this description.
>
>
>
> Is there any scenario that Private AS cannot be used?
>
>
>
> Thank you very much.
>
>
>
> Linda Dunbar
>
>
>
> *From:* Najem, Basil <basil.najem@bell.ca>
> *Sent:* Friday, February 7, 2020 3:02 PM
> *To:* Linda Dunbar <linda.dunbar@futurewei.com>; bess@ietf.org
> *Cc:* draft-dunbar-bess-bgp-sdwan-usage@ietf.org
> *Subject:* RE: solicit feedback on draft-dunbar-bess-bgp-sdwan-usage
> description of using BGP UPDATE messages to achieve SD-WAN Application
> Based Segmentation
>
>
>
>
>
>
>
> Hi Linda;
>
>
>
> The SD-WAN Segment is part of the SD-WAN fabric; in other words, there
> could be more than one Segment over a single underlay depending on the
> design and the business requirements.
>
>
>
> Each Segment represents a single and an isolated L3 domain; therefore, I
> suggested that we may need to include the Segment ID in the BGP update
> messages in order to identify and build the routing the table for each
> Segment (based on the Segment ID).
>
>
>
> Hope this helps.
>
>
>
> Regards;
>
>
>
> Basil
>
>
>
>
>
> *From:* Linda Dunbar <linda.dunbar@futurewei.com>
> *Sent:* February-03-20 10:40 AM
> *To:* Najem, Basil <basil.najem@bell.ca>; bess@ietf.org
> *Cc:* draft-dunbar-bess-bgp-sdwan-usage@ietf.org
> *Subject:* [EXT]RE: solicit feedback on draft-dunbar-bess-bgp-sdwan-usage
> description of using BGP UPDATE messages to achieve SD-WAN Application
> Based Segmentation
>
>
>
> Basil,
>
>
>
> Thank you very much for the comments.
>
> Your suggested wording change will be incorporated in the next revision.
>
>
>
> As for your suggestion of Segment and Segment ID of a SDWAN node (to be
> included in the BGP UPDATE), does the =E2=80=9CSegment=E2=80=9D mean the =
different
> Underlay?
>
> In the figure below, C-PE1 has 3 WAN ports: 2 to MPLS network and 1 to
> Public Internet.
>
> Do you mean C-PE1 has 3 WAN =E2=80=9Csegments=E2=80=9D?
>
> If not, can you elaborate more?
>
>
>
>
>
>
>
> Thanks, Linda
>
>
>
> *From:* Najem, Basil <basil.najem@bell.ca>
> *Sent:* Sunday, February 02, 2020 5:48 PM
> *To:* Linda Dunbar <linda.dunbar@futurewei.com>; bess@ietf.org
> *Cc:* draft-dunbar-bess-bgp-sdwan-usage@ietf.org
> *Subject:* RE: solicit feedback on draft-dunbar-bess-bgp-sdwan-usage
> description of using BGP UPDATE messages to achieve SD-WAN Application
> Based Segmentation
>
>
>
>
>
> Hello Linda;
>
>
>
> I haven=E2=80=99t gone through the entire document; however, I have the f=
ollowing
> quick comments
>
>
>
>    1. Regarding the following paragraph:
>
>
>
> 1.       Augment of transport, which refers to utilizing overlay paths
> over different underlay networks. Very often there are multiple parallel
> overlay paths between any two SDWAN edges, some of which are private
> networks over which traffic can traverse without encryption, others requi=
re
> encryption, e.g. over untrusted public networks.
>
>
>
> The traffic that traverses the privet networks can be either encrypted or
> unecrypted (in other words, the assumption that the traffic is NOT
> encrypted is not always correct). I would change the parpagaph to the
> following (for clarity):
>
>
>
> 1.       Augment of transport, which refers to utilizing overlay paths
> over different underlay networks. Very often there are multiple parallel
> overlay paths between any two SDWAN edges, some of which are private
> networks over which traffic can traverse with or without encryption,
> others require encryption, e.g. over untrusted public networks.
>
>
>
>
>
>    1. Another thing that we need to discuss is the Segment ID; each
>    Segment (at the SD-WAN Edge) MUST have an ID. The SD-WAN Policy will m=
ap
>    the Application Flow to the Segment. Since the Segment is a =E2=80=9Cr=
outing
>    domain=E2=80=9D, the BGP update will be exchanged with the memebers of=
 a particular
>    Segment.
>
>
>
> As such: Should we include the Segment ID as an attribute in the BGP
> update messages? Perhaps we need to further discuss this in details.
>
>
>
> Any feedback is welcomed and it=E2=80=99s highly appreciated.
>
>
>
> Regards;
>
>
>
> Basil
>
>
>
>
>
> *From:* Linda Dunbar <linda.dunbar@futurewei.com>
> *Sent:* January-31-20 5:17 PM
> *To:* bess@ietf.org
> *Cc:* draft-dunbar-bess-bgp-sdwan-usage@ietf.org
> *Subject:* [EXT]solicit feedback on draft-dunbar-bess-bgp-sdwan-usage
> description of using BGP UPDATE messages to achieve SD-WAN Application
> Based Segmentation
>
>
>
> BESS participants:
>
>
>
> =E2=80=9CSDWAN=E2=80=9D networks is characterized by:
>
> 1.       Augment of transport, which refers to utilizing overlay paths
> over different underlay networks. Very often there are multiple parallel
> overlay paths between any two SDWAN edges, some of which are private
> networks over which traffic can traverse without encryption, others requi=
re
> encryption, e.g. over untrusted public networks.
>
> 2.       Enable direct Internet access from remote sites, instead hauling
> all traffic to Corporate HQ for centralized policy control.
>
> 3.       Some traffic are routed based on application IDs instead of
> based on destination IP addresses.
>
>
>
>
>
> https://datatracker.ietf.org/doc/draft-dunbar-bess-bgp-sdwan-usage/
> <https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fdata=
tracker.ietf.org%2Fdoc%2Fdraft-dunbar-bess-bgp-sdwan-usage%2F&data=3D02%7C0=
1%7Clinda.dunbar%40futurewei.com%7C99acf950b82f4213da7f08d7cf34789d%7C0fee8=
ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637205696587614498&sdata=3D0MdUmWEie3=
Fd4y3UCVJ4HBdY0oxiBY4xiTK5%2FiMaAkQ%3D&reserved=3D0>
> describes examples of using BGP UPDATE messages to achieve the SDWAN
> Application Based Segmentation,  assuming that the applications are
> assigned with unique IP addresses.
>
> In the Figure below, the following BGP Updates can be advertised to ensur=
e
> that Payment Application only communicates with the Payment Gateway:
>
>
>
>
>
> BGP UPDATE #1 from C-PE2 to RR for the RED P2P topology (only propagated
> to Payment GW node:
>
> -        MP-NLRI Path Attribute:
>
>    - 30.1.1.x/24
>
> -        Tunnel Encap Path Attribute
>
>    - IPsec Attributes for PaymentGW ->C-PE2
>
>
>
> BGP UPDATE #2 from C-PE2 to RR for the routes to be reached by Purple:
>
> -        MP-NLRI Path Attribute:
>
>    - 10.1.x.x
>          - 12.4.x.x
>
> -        TunnelEncap Path Attribute:
>
>    - Any node to C-PE2
>
>
>
>
>
> Your feedback is greatly appreciated.
>
>
>
> Thank you very much.
>
>
>
> Linda Dunbar
> ------------------------------
>
> *External Email:** Please use caution when opening links and attachments
> / **Courriel externe:** Soyez prudent avec les liens et documents joints =
*
> ------------------------------
>
> *External Email:** Please use caution when opening links and attachments
> / **Courriel externe:** Soyez prudent avec les liens et documents joints =
*
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>

--0000000000003b549d05a18aa126
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Linda,<div><br></div><div>I think you are mixing data p=
lane and control plane.=C2=A0</div><div><br></div><div>In SDWAN=C2=A0data p=
lane is of no issue as you are interconnecting sites in a given VPN over me=
sh of secure tunnels.=C2=A0</div><div><br></div><div>You are asking how to =
keep control plane separate=C2=A0between VPN instances. This is precisely w=
hat RFC4364 does already and RT import/export is used to indicate the insta=
nce which given set of reachability belongs. Why to reinvent the wheel and =
do something new just for the heck of it :) ?=C2=A0</div><div><br></div><di=
v>To be original you can at best invent=C2=A0a different name to Route targ=
et(s) carried in the SAFI 128 but let&#39;s keep the mechanism=C2=A0the sam=
e. That would be my suggestion.</div><div><br></div><div>Kind regards,</div=
><div>R.</div><div><br></div><div>PS. While this is obvious for some many f=
olks are still confused. RFC4364 does not need to run over MPLS data plane.=
 It can run over IPSec or over DTLS or over UDP/IP just fine.=C2=A0</div></=
div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On=
 Mon, Mar 23, 2020 at 6:47 PM Linda Dunbar &lt;<a href=3D"mailto:linda.dunb=
ar@futurewei.com">linda.dunbar@futurewei.com</a>&gt; wrote:<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US">
<div>
<p class=3D"MsoNormal">IDR experts:<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">SDWAN is an overlay network arching over multiple ty=
pes of networks. A SDWAN edge node may need to map client traffic to differ=
ent SDWAN network instances (or segmentations).<u></u><u></u></p>
<p class=3D"MsoNormal">It might not be feasible to use the AS number in the=
 BGP message to differentiate the SDWAN network instances as multiple SDWAN=
 instances may share the same AS number.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">We would like to hear feedback from IDR group on usi=
ng similar method as =C2=A0Binding MPLS Labels to Address Prefixes [RFC8277=
] to bind SDWAN Instance ID to =C2=A0prefixes.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">When =C2=A0MPLS VPN SAFI (=3D128) is present, MPLS l=
abel is carried by NLRI [RFC8277] as:<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border:1pt solid rgb(204,204,204);padding:8pt;background:rgb(=
255,253,245)">
<p class=3D"MsoNormal" style=3D"margin-bottom:7.9pt;background:rgb(255,253,=
245);word-break:break-all;border:none;padding:0in">
<span style=3D"font-size:10.5pt;font-family:&quot;Courier New&quot;;color:b=
lack">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 1=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 2=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 3<u><=
/u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:7.9pt;background:rgb(255,253,=
245);word-break:break-all;border:none;padding:0in">
<span style=3D"font-size:10.5pt;font-family:&quot;Courier New&quot;;color:b=
lack">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 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<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:7.9pt;background:rgb(255,253,=
245);word-break:break-all;border:none;padding:0in">
<span style=3D"font-size:10.5pt;font-family:&quot;Courier New&quot;;color:b=
lack">=C2=A0=C2=A0=C2=A0=C2=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+-+-+-+<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:7.9pt;background:rgb(255,253,=
245);word-break:break-all;border:none;padding:0in">
<span style=3D"font-size:10.5pt;font-family:&quot;Courier New&quot;;color:b=
lack">=C2=A0=C2=A0=C2=A0=C2=A0 |=C2=A0=C2=A0=C2=A0 Length=C2=A0=C2=A0=C2=A0=
=C2=A0 |=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Label=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |Rsrv |S|<u></u><=
u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:7.9pt;background:rgb(255,253,=
245);word-break:break-all;border:none;padding:0in">
<span style=3D"font-size:10.5pt;font-family:&quot;Courier New&quot;;color:b=
lack">=C2=A0=C2=A0=C2=A0=C2=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+-+-+-+<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:7.9pt;background:rgb(255,253,=
245);word-break:break-all;border:none;padding:0in">
<span style=3D"font-size:10.5pt;font-family:&quot;Courier New&quot;;color:b=
lack">=C2=A0=C2=A0=C2=A0=C2=A0 |=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Prefix=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
~<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:7.9pt;background:rgb(255,253,=
245);word-break:break-all;border:none;padding:0in">
<span style=3D"font-size:10.5pt;font-family:&quot;Courier New&quot;;color:b=
lack">=C2=A0=C2=A0=C2=A0=C2=A0 ~=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:7.9pt;background:rgb(255,253,=
245);word-break:break-all;border:none;padding:0in">
<span style=3D"font-size:10.5pt;font-family:&quot;Courier New&quot;;color:b=
lack">=C2=A0=C2=A0=C2=A0=C2=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+-+-+-+<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:7.9pt;background:rgb(255,253,=
245);word-break:break-all;border:none;padding:0in">
<span style=3D"font-size:10.5pt;font-family:&quot;Courier New&quot;;color:b=
lack"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:7.9pt;background:rgb(255,253,=
245);word-break:break-all;border:none;padding:0in">
<span style=3D"font-size:10.5pt;font-family:&quot;Courier New&quot;;color:b=
lack">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Figure 2: N=
LRI with One Label<u></u><u></u></span></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">We would like to =C2=A0propose the SDWAN Instance ID=
 being encoded in the Label field as follows when SDWAN SAFI (=3D74 allocat=
ed by IANA) is used,:<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 1=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 2=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 3<u></u><u>=
</u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 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<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0 |=C2=A0=C2=A0=C2=A0 Length=C2=A0=C2=A0=C2=A0=C2=A0=
 |=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 SDWAN Instance ID (Label)=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 |Rsrv |S|<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0 |=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 Prefix=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ~<u></u>=
<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0 ~=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0|<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;">=
=C2=A0=C2=A0=C2=A0=C2=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+<u></u><u></u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 =C2=A0NLRI with SDWAN Instance ID. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Greatly appreciate any comments or other suggestions=
.. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Thank you,<u></u><u></u></p>
<p class=3D"MsoNormal">Linda Dunbar<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Huaimo Chen &lt;<a href=3D"mailto:huaim=
o.chen@futurewei.com" target=3D"_blank">huaimo.chen@futurewei.com</a>&gt; <=
br>
<b>Sent:</b> Monday, March 23, 2020 9:14 AM<br>
<b>To:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" t=
arget=3D"_blank">linda.dunbar@futurewei.com</a>&gt;; <a href=3D"mailto:idr@=
ietf.org" target=3D"_blank">idr@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:bess@ietf.org" target=3D"_blank">bess@ietf.org=
</a><br>
<b>Subject:</b> Re: [Idr] FW: Is there any problem of using Private AS as &=
quot;Identifier&quot; to differentiate SD-WAN Segmentation for draft-dunbar=
-bess-bgp-sdwan-usage?<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt;color:black">Hi Linda,=
<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt;color:black"><u></u>=
=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt;color:black">=C2=A0 =
=C2=A0 It seems that using another SAFI is a possible solution.<u></u><u></=
u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt;color:black"><u></u>=
=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt;color:black">Best Rega=
rds,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt;color:black">Huaimo<u>=
</u><u></u></span></p>
</div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"98%" align=3D"center">
</div>
<div id=3D"gmail-m_4680921541555540591divRplyFwdMsg">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From:</span></b><span=
 style=3D"color:black"> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@fut=
urewei.com" target=3D"_blank">linda.dunbar@futurewei.com</a>&gt;<br>
<b>Sent:</b> Friday, March 20, 2020 12:54 AM<br>
<b>To:</b> Huaimo Chen &lt;<a href=3D"mailto:huaimo.chen@futurewei.com" tar=
get=3D"_blank">huaimo.chen@futurewei.com</a>&gt;;
<a href=3D"mailto:idr@ietf.org" target=3D"_blank">idr@ietf.org</a> &lt;<a h=
ref=3D"mailto:idr@ietf.org" target=3D"_blank">idr@ietf.org</a>&gt;<br>
<b>Cc:</b> <a href=3D"mailto:bess@ietf.org" target=3D"_blank">bess@ietf.org=
</a> &lt;<a href=3D"mailto:bess@ietf.org" target=3D"_blank">bess@ietf.org</=
a>&gt;<br>
<b>Subject:</b> RE: [Idr] FW: Is there any problem of using Private AS as &=
quot;Identifier&quot; to differentiate SD-WAN Segmentation for draft-dunbar=
-bess-bgp-sdwan-usage?</span>
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p>Huaimo, <u></u><u></u></p>
<p>=C2=A0<u></u><u></u></p>
<p>Thank you very much for the suggestion. <u></u><u></u></p>
<p>Do you mean using the similar approach as VPN Label carried by NLRI Path=
 Attribute [RFC8277] for SDWAN Segmentation Identifier?<u></u><u></u></p>
<p>If yes, the UPDATE message should not use the MPLS VPN SAFI (=3D128) to =
avoid confusion, right?
<u></u><u></u></p>
<p>=C2=A0<u></u><u></u></p>
<p>Linda<u></u><u></u></p>
<p>=C2=A0<u></u><u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p><b>From:</b> Huaimo Chen &lt;<a href=3D"mailto:huaimo.chen@futurewei.com=
" target=3D"_blank">huaimo.chen@futurewei.com</a>&gt;
<br>
<b>Sent:</b> Thursday, March 19, 2020 6:45 PM<br>
<b>To:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" t=
arget=3D"_blank">linda.dunbar@futurewei.com</a>&gt;;
<a href=3D"mailto:idr@ietf.org" target=3D"_blank">idr@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:bess@ietf.org" target=3D"_blank">bess@ietf.org=
</a><br>
<b>Subject:</b> Re: [Idr] FW: Is there any problem of using Private AS as &=
quot;Identifier&quot; to differentiate SD-WAN Segmentation for draft-dunbar=
-bess-bgp-sdwan-usage?<u></u><u></u></p>
</div>
</div>
<p>=C2=A0<u></u><u></u></p>
<div>
<p><span style=3D"font-size:12pt;color:black">Hi Linda,</span><u></u><u></u=
></p>
</div>
<div>
<p><span style=3D"font-size:12pt;color:black">=C2=A0</span><u></u><u></u></=
p>
</div>
<div>
<p><span style=3D"font-size:12pt;color:black">=C2=A0 =C2=A0 It seems that a=
 label may be used as an=C2=A0&quot;Identifier&quot; to differentiate SD-WA=
N Segmentation.</span><u></u><u></u></p>
</div>
<div>
<p><span style=3D"font-size:12pt;color:black">=C2=A0</span><u></u><u></u></=
p>
</div>
<div>
<div>
<p><span style=3D"font-size:12pt;color:black">Best Regards,</span><u></u><u=
></u></p>
</div>
<div>
<p><span style=3D"font-size:12pt;color:black">Huaimo</span><u></u><u></u></=
p>
</div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"98%" align=3D"center">
</div>
<div id=3D"gmail-m_4680921541555540591x_divRplyFwdMsg">
<p><b><span style=3D"color:black">From:</span></b><span style=3D"color:blac=
k"> Idr &lt;<a href=3D"mailto:idr-bounces@ietf.org" target=3D"_blank">idr-b=
ounces@ietf.org</a>&gt; on behalf of Linda Dunbar &lt;<a href=3D"mailto:lin=
da.dunbar@futurewei.com" target=3D"_blank">linda.dunbar@futurewei.com</a>&g=
t;<br>
<b>Sent:</b> Thursday, March 19, 2020 1:22 PM<br>
<b>To:</b> <a href=3D"mailto:idr@ietf.org" target=3D"_blank">idr@ietf.org</=
a> &lt;<a href=3D"mailto:idr@ietf.org" target=3D"_blank">idr@ietf.org</a>&g=
t;<br>
<b>Cc:</b> <a href=3D"mailto:bess@ietf.org" target=3D"_blank">bess@ietf.org=
</a> &lt;<a href=3D"mailto:bess@ietf.org" target=3D"_blank">bess@ietf.org</=
a>&gt;<br>
<b>Subject:</b> [Idr] FW: Is there any problem of using Private AS as &quot=
;Identifier&quot; to differentiate SD-WAN Segmentation for draft-dunbar-bes=
s-bgp-sdwan-usage?</span>
<u></u><u></u></p>
<div>
<p>=C2=A0<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p>BGP Experts, <u></u><u></u></p>
<p>=C2=A0<u></u><u></u></p>
<p>Do you know if =C2=A0there is any problem of using=C2=A0 Private AS as=
=C2=A0 &quot;Identifier&quot; to differentiate SD-WAN Segmentation? Here is=
 the discussion in BESS WG. Want to get IDR WG feedbacks for this question.
<u></u><u></u></p>
<p>=C2=A0<u></u><u></u></p>
<p>Thank you. <u></u><u></u></p>
<p>Linda<u></u><u></u></p>
<p>=C2=A0<u></u><u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p><b>From:</b> Linda Dunbar <br>
<b>Sent:</b> Thursday, March 19, 2020 11:54 AM<br>
<b>To:</b> Najem, Basil &lt;<a href=3D"mailto:basil.najem@bell.ca" target=
=3D"_blank">basil.najem@bell.ca</a>&gt;;
<a href=3D"mailto:bess@ietf.org" target=3D"_blank">bess@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:draft-dunbar-bess-bgp-sdwan-usage@ietf.org" ta=
rget=3D"_blank">draft-dunbar-bess-bgp-sdwan-usage@ietf.org</a><br>
<b>Subject:</b> Is there any problem of using Private AS as &quot;Identifie=
r&quot; to differentiate SD-WAN Segmentation for draft-dunbar-bess-bgp-sdwa=
n-usage?<u></u><u></u></p>
</div>
</div>
<p>=C2=A0<u></u><u></u></p>
<p>Based on Basil=E2=80=99s comment on needing an identifier to differentia=
te SDWAN instances, I added a section to =C2=A0draft-dunbar-bess-bgp-sdwan-=
usage . Want to hear people=E2=80=99s feedback.
<u></u><u></u></p>
<p>=C2=A0<u></u><u></u></p>
<h2 style=3D"margin-right:0in;margin-bottom:12pt;margin-left:45pt;line-heig=
ht:12pt;break-after:avoid">
<a name=3D"m_4680921541555540591_x_x__Toc31377653"><span style=3D"font-size=
:12pt;font-family:&quot;Courier New&quot;;font-weight:normal">3.1</span></a=
><span></span><span style=3D"font-size:7pt;font-family:&quot;Times New Roma=
n&quot;,serif;font-weight:normal">=C2=A0=C2=A0=C2=A0
</span><span style=3D"font-size:12pt;font-family:&quot;Courier New&quot;;fo=
nt-weight:normal">Requirements</span><u></u><u></u></h2>
<h3 style=3D"margin-right:0in;margin-bottom:12pt;margin-left:0.75in;line-he=
ight:12pt;break-after:avoid">
<span style=3D"font-size:12pt;font-family:&quot;Courier New&quot;;font-weig=
ht:normal">3.1.1Supporting Multiple SDWAN Segmentations</span><u></u><u></u=
></h3>
<p>The term =E2=80=9Cnetwork segmentation=E2=80=9D is used extensively in S=
DWAN deployment. In general (and in this document), the =E2=80=9CNetwork Se=
gmentation=E2=80=9D is referring to the process of dividing the network int=
o logical sub-networks using isolation techniques
 on a forwarding device such as a switch, router, or firewall. For a homoge=
neous network, such as MPLS VPN or Layer 2 network, VRF or VLAN are used to=
 separate network segments.
<u></u><u></u></p>
<p>As SDWAN is an overlay network arching over multiple types of networks, =
it is important to have distinct identifiers to differentiate SDWAN network=
 instances (or segmentations). When different SDWAN network segments do not=
 have their
 own assigned AS numbers, a very easy way is to use Private AS numbers, in =
the range of 64512 to 65535, to differentiate different SDWAN segmentations=
.. When using BGP to control the SDWAN networks, the Private AS numbers are=
 carried by the BGP UPDATE messages
 to their corresponding RRs.<u></u><u></u></p>
<p>=C2=A0<u></u><u></u></p>
<p>Greatly appreciate any feedback on this description. <u></u>
<u></u></p>
<p>=C2=A0<u></u><u></u></p>
<p>Is there any scenario that Private AS cannot be used? <u></u>
<u></u></p>
<p>=C2=A0<u></u><u></u></p>
<p>Thank you very much. <u></u><u></u></p>
<p>=C2=A0<u></u><u></u></p>
<p>Linda Dunbar<u></u><u></u></p>
<p>=C2=A0<u></u><u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p><b>From:</b> Najem, Basil &lt;<a href=3D"mailto:basil.najem@bell.ca" tar=
get=3D"_blank">basil.najem@bell.ca</a>&gt;
<br>
<b>Sent:</b> Friday, February 7, 2020 3:02 PM<br>
<b>To:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" t=
arget=3D"_blank">linda.dunbar@futurewei.com</a>&gt;;
<a href=3D"mailto:bess@ietf.org" target=3D"_blank">bess@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:draft-dunbar-bess-bgp-sdwan-usage@ietf.org" ta=
rget=3D"_blank">draft-dunbar-bess-bgp-sdwan-usage@ietf.org</a><br>
<b>Subject:</b> RE: solicit feedback on draft-dunbar-bess-bgp-sdwan-usage d=
escription of using BGP UPDATE messages to achieve SD-WAN Application Based=
 Segmentation
<u></u><u></u></p>
</div>
</div>
<p>=C2=A0<u></u><u></u></p>
<p><span lang=3D"EN-CA" style=3D"color:rgb(31,73,125)">=C2=A0</span><u></u>=
<u></u></p>
<p><span lang=3D"EN-CA" style=3D"color:rgb(31,73,125)">=C2=A0</span><u></u>=
<u></u></p>
<div>
<p><span lang=3D"EN-CA" style=3D"color:rgb(31,73,125)">Hi Linda;</span><u><=
/u><u></u></p>
<p><span lang=3D"EN-CA" style=3D"color:rgb(31,73,125)">=C2=A0</span><u></u>=
<u></u></p>
<p><span lang=3D"EN-CA" style=3D"color:rgb(31,73,125)">The SD-WAN Segment i=
s part of the SD-WAN fabric; in other words, there could be more than one S=
egment over a single underlay depending on the design and the business requ=
irements.</span><u></u><u></u></p>
<p><span lang=3D"EN-CA" style=3D"color:rgb(31,73,125)">=C2=A0</span><u></u>=
<u></u></p>
<p><span lang=3D"EN-CA" style=3D"color:rgb(31,73,125)">Each Segment represe=
nts a single and an isolated L3 domain; therefore, I suggested that we may =
need to include the Segment ID in the BGP update messages in order to ident=
ify and build the routing
 the table for each Segment (based on the Segment ID).</span><u></u><u></u>=
</p>
<p><span lang=3D"EN-CA" style=3D"color:rgb(31,73,125)">=C2=A0</span><u></u>=
<u></u></p>
<p><span lang=3D"EN-CA" style=3D"color:rgb(31,73,125)">Hope this helps.</sp=
an><u></u><u></u></p>
<p><span lang=3D"EN-CA" style=3D"color:rgb(31,73,125)">=C2=A0</span><u></u>=
<u></u></p>
<p><span lang=3D"EN-CA" style=3D"color:rgb(31,73,125)">Regards;</span><u></=
u><u></u></p>
<p><span lang=3D"EN-CA" style=3D"color:rgb(31,73,125)">=C2=A0</span><u></u>=
<u></u></p>
<p><span lang=3D"EN-CA" style=3D"color:rgb(31,73,125)">Basil</span><u></u><=
u></u></p>
<p><span style=3D"color:rgb(31,73,125)">=C2=A0</span><u></u><u></u></p>
</div>
<p><span lang=3D"EN-CA" style=3D"color:rgb(31,73,125)">=C2=A0</span><u></u>=
<u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p><b>From:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.c=
om" target=3D"_blank">linda.dunbar@futurewei.com</a>&gt;
<br>
<b>Sent:</b> February-03-20 10:40 AM<br>
<b>To:</b> Najem, Basil &lt;<a href=3D"mailto:basil.najem@bell.ca" target=
=3D"_blank">basil.najem@bell.ca</a>&gt;;
<a href=3D"mailto:bess@ietf.org" target=3D"_blank">bess@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:draft-dunbar-bess-bgp-sdwan-usage@ietf.org" ta=
rget=3D"_blank">draft-dunbar-bess-bgp-sdwan-usage@ietf.org</a><br>
<b>Subject:</b> [EXT]RE: solicit feedback on draft-dunbar-bess-bgp-sdwan-us=
age description of using BGP UPDATE messages to achieve SD-WAN Application =
Based Segmentation
<u></u><u></u></p>
</div>
</div>
<p><span lang=3D"EN-CA">=C2=A0</span><u></u><u></u></p>
<p>Basil, <u></u><u></u></p>
<p>=C2=A0<u></u><u></u></p>
<p>Thank you very much for the comments. <u></u><u></u></p>
<p>Your suggested wording change will be incorporated in the next revision.
<u></u><u></u></p>
<p>=C2=A0<u></u><u></u></p>
<p>As for your suggestion of Segment and Segment ID of a SDWAN node (to be =
included in the BGP UPDATE), does the =E2=80=9CSegment=E2=80=9D mean the di=
fferent Underlay?
<u></u><u></u></p>
<p>In the figure below, C-PE1 has 3 WAN ports: 2 to MPLS network and 1 to P=
ublic Internet.
<u></u><u></u></p>
<p>Do you mean C-PE1 has 3 WAN =E2=80=9Csegments=E2=80=9D? <u></u><u></u></=
p>
<p>If not, can you elaborate more? <u></u><u></u></p>
<p>=C2=A0<u></u><u></u></p>
<p><img border=3D"0" width=3D"390" height=3D"305" style=3D"width: 4.0625in;=
 height: 3.177in;" id=3D"gmail-m_4680921541555540591x_x__x005f_x0000_i1041"=
><u></u><u></u></p>
<p>=C2=A0<u></u><u></u></p>
<p>=C2=A0<u></u><u></u></p>
<p>Thanks, Linda<u></u><u></u></p>
<p>=C2=A0<u></u><u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p><b>From:</b> Najem, Basil &lt;<a href=3D"mailto:basil.najem@bell.ca" tar=
get=3D"_blank">basil.najem@bell.ca</a>&gt;
<br>
<b>Sent:</b> Sunday, February 02, 2020 5:48 PM<br>
<b>To:</b> Linda Dunbar &lt;<a href=3D"mailto:linda.dunbar@futurewei.com" t=
arget=3D"_blank">linda.dunbar@futurewei.com</a>&gt;;
<a href=3D"mailto:bess@ietf.org" target=3D"_blank">bess@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:draft-dunbar-bess-bgp-sdwan-usage@ietf.org" ta=
rget=3D"_blank">draft-dunbar-bess-bgp-sdwan-usage@ietf.org</a><br>
<b>Subject:</b> RE: solicit feedback on draft-dunbar-bess-bgp-sdwan-usage d=
escription of using BGP UPDATE messages to achieve SD-WAN Application Based=
 Segmentation
<u></u><u></u></p>
</div>
</div>
<p>=C2=A0<u></u><u></u></p>
<p><span lang=3D"EN-CA" style=3D"color:rgb(31,73,125)">=C2=A0</span><u></u>=
<u></u></p>
<div>
<p><span lang=3D"EN-CA" style=3D"color:rgb(31,73,125)">Hello Linda;</span><=
u></u><u></u></p>
<p><span lang=3D"EN-CA" style=3D"color:rgb(31,73,125)">=C2=A0</span><u></u>=
<u></u></p>
<p><span lang=3D"EN-CA" style=3D"color:rgb(31,73,125)">I haven=E2=80=99t go=
ne through the entire document; however, I have the following quick comment=
s</span><u></u><u></u></p>
<p><span lang=3D"EN-CA" style=3D"color:rgb(31,73,125)">=C2=A0</span><u></u>=
<u></u></p>
<ol style=3D"margin-top:0in" start=3D"1" type=3D"A">
<li style=3D"color:rgb(31,73,125);margin-top:0in;margin-bottom:0.0001pt">
<span lang=3D"EN-CA">Regarding the following paragraph:</span><u></u><u></u=
></li></ol>
<p style=3D"margin:0in 0in 0.0001pt"><span lang=3D"EN-CA" style=3D"color:rg=
b(31,73,125)">=C2=A0</span><u></u><u></u></p>
<p style=3D"margin-right:0in;margin-left:0.75in;margin-bottom:0.0001pt">
1.<span style=3D"font-size:7pt;font-family:&quot;Times New Roman&quot;,seri=
f">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 </span>
<span style=3D"font-family:&quot;Courier New&quot;">Augment of transport, w=
hich refers to utilizing overlay paths over different underlay networks. Ve=
ry often there are multiple parallel overlay paths between any two SDWAN ed=
ges, some of which are private networks over
 which traffic can traverse without encryption, others require encryption, =
e.g. over untrusted public networks.
</span><u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt"><span style=3D"font-size:12pt;font-fam=
ily:Arial,sans-serif;color:rgb(31,73,125)">=C2=A0</span><u></u><u></u></p>
<p style=3D"margin-right:0in;margin-left:0.5in;margin-bottom:0.0001pt">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif;color:rgb(31,73,=
125)">The traffic that traverses the privet networks can be either encrypte=
d or unecrypted (in other words, the assumption that the traffic is NOT enc=
rypted is not always correct). I would
 change the parpagaph to the following (for clarity):</span><u></u><u></u><=
/p>
<p style=3D"margin:0in 0in 0.0001pt"><span style=3D"font-size:12pt;font-fam=
ily:Arial,sans-serif;color:rgb(31,73,125)">=C2=A0</span><u></u><u></u></p>
<p style=3D"margin-right:0in;margin-left:0.75in;margin-bottom:0.0001pt">
1.<span style=3D"font-size:7pt;font-family:&quot;Times New Roman&quot;,seri=
f">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 </span>
<span style=3D"font-family:&quot;Courier New&quot;">Augment of transport, w=
hich refers to utilizing overlay paths over different underlay networks. Ve=
ry often there are multiple parallel overlay paths between any two SDWAN ed=
ges, some of which are private networks over
 which traffic can traverse <span style=3D"color:red">with or </span>withou=
t encryption, others require encryption, e.g. over untrusted public network=
s.
</span><u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt"><span style=3D"font-size:12pt;font-fam=
ily:Arial,sans-serif;color:rgb(31,73,125)">=C2=A0</span><u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt"><span style=3D"font-size:12pt;font-fam=
ily:Arial,sans-serif;color:rgb(31,73,125)">=C2=A0</span><u></u><u></u></p>
<ol style=3D"margin-top:0in" start=3D"2" type=3D"A">
<li style=3D"color:rgb(31,73,125);margin-top:0in;margin-bottom:0.0001pt">
<span style=3D"font-size:12pt;font-family:Arial,sans-serif">Another thing t=
hat we need to discuss is the Segment ID; each Segment (at the SD-WAN Edge)=
 MUST have an ID. The SD-WAN Policy will map the Application Flow to the Se=
gment. Since the Segment is a
 =E2=80=9Crouting domain=E2=80=9D, the BGP update will be exchanged with th=
e memebers of a particular Segment.
</span><u></u><u></u></li></ol>
<p style=3D"margin-left:0.5in"><span style=3D"font-size:12pt;font-family:Ar=
ial,sans-serif;color:rgb(31,73,125)">=C2=A0</span><u></u><u></u></p>
<p style=3D"margin-left:0.5in"><span style=3D"font-size:12pt;font-family:Ar=
ial,sans-serif;color:rgb(31,73,125);background:yellow">As such: Should we i=
nclude the Segment ID as an attribute in the BGP update messages? Perhaps w=
e need to further
 discuss this in details.</span><u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt"><span style=3D"font-size:12pt;font-fam=
ily:Arial,sans-serif;color:rgb(31,73,125)">=C2=A0</span><u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt"><span style=3D"font-size:12pt;font-fam=
ily:Arial,sans-serif;color:rgb(31,73,125)">Any feedback is welcomed and it=
=E2=80=99s highly appreciated.</span><u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt"><span style=3D"font-size:12pt;font-fam=
ily:Arial,sans-serif;color:rgb(31,73,125)">=C2=A0</span><u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt"><span style=3D"font-size:12pt;font-fam=
ily:Arial,sans-serif;color:rgb(31,73,125)">Regards;</span><u></u><u></u></p=
>
<p style=3D"margin:0in 0in 0.0001pt"><span style=3D"font-size:12pt;font-fam=
ily:Arial,sans-serif;color:rgb(31,73,125)">=C2=A0</span><u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt"><span style=3D"font-size:12pt;font-fam=
ily:Arial,sans-serif;color:rgb(31,73,125)">Basil</span><u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt"><span style=3D"color:rgb(31,73,125)">=
=C2=A0</span><u></u><u></u></p>
</div>
<p style=3D"margin:0in 0in 0.0001pt"><span lang=3D"EN-CA" style=3D"color:rg=
b(31,73,125)">=C2=A0</span><u></u><u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p style=3D"margin:0in 0in 0.0001pt"><b>From:</b> Linda Dunbar &lt;<a href=
=3D"mailto:linda.dunbar@futurewei.com" target=3D"_blank">linda.dunbar@futur=
ewei.com</a>&gt;
<br>
<b>Sent:</b> January-31-20 5:17 PM<br>
<b>To:</b> <a href=3D"mailto:bess@ietf.org" target=3D"_blank">bess@ietf.org=
</a><br>
<b>Cc:</b> <a href=3D"mailto:draft-dunbar-bess-bgp-sdwan-usage@ietf.org" ta=
rget=3D"_blank">draft-dunbar-bess-bgp-sdwan-usage@ietf.org</a><br>
<b>Subject:</b> [EXT]solicit feedback on draft-dunbar-bess-bgp-sdwan-usage =
description of using BGP UPDATE messages to achieve SD-WAN Application Base=
d Segmentation
<u></u><u></u></p>
</div>
</div>
<p style=3D"margin:0in 0in 0.0001pt"><span lang=3D"EN-CA">=C2=A0</span><u><=
/u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt">BESS participants:<u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt">=C2=A0<u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt">=E2=80=9CSDWAN=E2=80=9D networks is ch=
aracterized by:
<u></u><u></u></p>
<p style=3D"margin-right:0in;margin-left:0.75in;margin-bottom:0.0001pt">
1.<span style=3D"font-size:7pt;font-family:&quot;Times New Roman&quot;,seri=
f">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 </span>
<span style=3D"font-family:&quot;Courier New&quot;">Augment of transport, w=
hich refers to utilizing overlay paths over different underlay networks. Ve=
ry often there are multiple parallel overlay paths between any two SDWAN ed=
ges, some of which are private networks over
 which traffic can traverse without encryption, others require encryption, =
e.g. over untrusted public networks.
</span><u></u><u></u></p>
<p style=3D"margin-right:0in;margin-left:0.75in;margin-bottom:0.0001pt">
2.<span style=3D"font-size:7pt;font-family:&quot;Times New Roman&quot;,seri=
f">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 </span>
<span style=3D"font-family:&quot;Courier New&quot;">Enable direct Internet =
access from remote sites, instead hauling all traffic to Corporate HQ for c=
entralized policy control.
</span><u></u><u></u></p>
<p style=3D"margin-right:0in;margin-left:0.75in;margin-bottom:0.0001pt">
3.<span style=3D"font-size:7pt;font-family:&quot;Times New Roman&quot;,seri=
f">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 </span>
<span style=3D"font-family:&quot;Courier New&quot;">Some traffic are routed=
 based on application IDs instead of based on destination IP addresses.
</span><u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt">=C2=A0<u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt">=C2=A0<u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt"><a href=3D"https://nam11.safelinks.pro=
tection.outlook.com/?url=3Dhttps%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft=
-dunbar-bess-bgp-sdwan-usage%2F&amp;data=3D02%7C01%7Clinda.dunbar%40futurew=
ei.com%7C99acf950b82f4213da7f08d7cf34789d%7C0fee8ff2a3b240189c753a1d5591fed=
c%7C1%7C0%7C637205696587614498&amp;sdata=3D0MdUmWEie3Fd4y3UCVJ4HBdY0oxiBY4x=
iTK5%2FiMaAkQ%3D&amp;reserved=3D0" target=3D"_blank">https://datatracker.ie=
tf.org/doc/draft-dunbar-bess-bgp-sdwan-usage/</a>
 describes examples of using BGP UPDATE messages to achieve the SDWAN Appli=
cation Based Segmentation, =C2=A0assuming that the applications are assigne=
d with unique IP addresses.<u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt">In the Figure below, the following BGP=
 Updates can be advertised to ensure that Payment Application only communic=
ates with the Payment Gateway:<u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt">=C2=A0<u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt"><img border=3D"0" width=3D"538" height=
=3D"218" style=3D"width: 5.6041in; height: 2.2708in;" id=3D"gmail-m_4680921=
541555540591x_x__x005f_x0000_i1042"><u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt">=C2=A0<u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt">BGP UPDATE #1 from C-PE2 to RR for the=
 RED P2P topology (only propagated to Payment GW node:<u></u><u></u></p>
<p style=3D"margin-right:0in;margin-left:62.65pt;margin-bottom:0.0001pt">
<span style=3D"font-family:&quot;Times New Roman&quot;,serif">-</span><span=
 style=3D"font-size:7pt;font-family:&quot;Times New Roman&quot;,serif">=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span><span style=3D"color:black">MP-NLRI Path Attribute: </span><u></u><u=
></u></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<ul style=3D"margin-top:0in" type=3D"disc">
<ul style=3D"margin-top:0in" type=3D"disc">
<li style=3D"color:black;margin-top:0in;margin-bottom:0.0001pt">
30.1.1.x/24<u></u><u></u></li></ul>
</ul>
</ul>
<p style=3D"margin-right:0in;margin-left:62.65pt;margin-bottom:0.0001pt">
<span style=3D"font-family:&quot;Times New Roman&quot;,serif">-</span><span=
 style=3D"font-size:7pt;font-family:&quot;Times New Roman&quot;,serif">=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span><span style=3D"color:black">Tunnel Encap Path Attribute</span><u></u=
><u></u></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<ul style=3D"margin-top:0in" type=3D"disc">
<ul style=3D"margin-top:0in" type=3D"disc">
<li style=3D"color:black;margin-top:0in;margin-bottom:0.0001pt">
IPsec Attributes for PaymentGW -&gt;C-PE2<u></u><u></u></li></ul>
</ul>
</ul>
<p style=3D"margin-right:0in;margin-left:134.65pt;margin-bottom:0.0001pt">
<span style=3D"font-size:10.5pt">=C2=A0</span><u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt">BGP UPDATE #2 from C-PE2 to RR for the=
 routes to be reached by Purple:<u></u><u></u></p>
<p style=3D"margin-right:0in;margin-left:62.65pt;margin-bottom:0.0001pt">
<span style=3D"font-family:&quot;Times New Roman&quot;,serif">-</span><span=
 style=3D"font-size:7pt;font-family:&quot;Times New Roman&quot;,serif">=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span><span style=3D"color:black">MP-NLRI Path Attribute:</span><u></u><u>=
</u></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<ul style=3D"margin-top:0in" type=3D"disc">
<ul style=3D"margin-top:0in" type=3D"disc">
<li style=3D"margin-top:0in;margin-bottom:0.0001pt">
<span style=3D"color:black">10.1.x.x</span><u></u><u></u></li><li style=3D"=
margin-top:0in;margin-bottom:0.0001pt">
<span style=3D"color:black">12.4.x.x</span><u></u><u></u></li></ul>
</ul>
</ul>
<p style=3D"margin-right:0in;margin-left:62.65pt;margin-bottom:0.0001pt">
<span style=3D"font-family:&quot;Times New Roman&quot;,serif;color:black">-=
</span><span style=3D"font-size:7pt;font-family:&quot;Times New Roman&quot;=
,serif;color:black">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
</span><span style=3D"color:black">TunnelEncap Path Attribute:</span><u></u=
><u></u></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<ul style=3D"margin-top:0in" type=3D"disc">
<ul style=3D"margin-top:0in" type=3D"disc">
<li style=3D"color:black;margin-top:0in;margin-bottom:0.0001pt">
Any node to C-PE2<u></u><u></u></li></ul>
</ul>
</ul>
<p style=3D"margin:0in 0in 0.0001pt">=C2=A0<u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt">=C2=A0<u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt">Your feedback is greatly appreciated.
<u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt">=C2=A0<u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt">Thank you very much.
<u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt">=C2=A0<u></u><u></u></p>
<p style=3D"margin:0in 0in 0.0001pt">Linda Dunbar<u></u><u></u></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-size:12pt;font-family:&quot;Times New Roman&quot;,serif">
<hr size=3D"1" width=3D"100%" align=3D"center">
</span></div>
<p style=3D"margin:0in 0in 0.0001pt"><strong><i><span style=3D"font-size:9p=
t;font-family:Calibri,sans-serif;color:blue">External Email:</span></i></st=
rong><em><span style=3D"font-size:9pt;font-family:Calibri,sans-serif;color:=
blue">
 Please use caution when opening links and attachments / </span></em><stron=
g><i><span style=3D"font-size:9pt;font-family:Calibri,sans-serif;color:blue=
">Courriel externe:</span></i></strong><em><span style=3D"font-size:9pt;fon=
t-family:Calibri,sans-serif;color:blue">
 Soyez prudent avec les liens et documents joints </span></em><u></u><u></u=
></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-size:12pt;font-family:&quot;Times New Roman&quot;,serif">
<hr size=3D"1" width=3D"100%" align=3D"center">
</span></div>
<p style=3D"margin:0in 0in 0.0001pt"><strong><i><span style=3D"font-size:9p=
t;font-family:Calibri,sans-serif;color:blue">External Email:</span></i></st=
rong><em><span style=3D"font-size:9pt;font-family:Calibri,sans-serif;color:=
blue">
 Please use caution when opening links and attachments / </span></em><stron=
g><i><span style=3D"font-size:9pt;font-family:Calibri,sans-serif;color:blue=
">Courriel externe:</span></i></strong><em><span style=3D"font-size:9pt;fon=
t-family:Calibri,sans-serif;color:blue">
 Soyez prudent avec les liens et documents joints </span></em><u></u><u></u=
></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>

_______________________________________________<br>
Idr mailing list<br>
<a href=3D"mailto:Idr@ietf.org" target=3D"_blank">Idr@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/idr" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/idr</a><br>
</blockquote></div>

--0000000000003b549d05a18aa126--