Re: [Idr] Call for IETF104 IDR agenda items

Linda Dunbar <linda.dunbar@huawei.com> Wed, 06 March 2019 23:27 UTC

Return-Path: <linda.dunbar@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A07521310D4; Wed, 6 Mar 2019 15:27:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jE7TIKuIeNDg; Wed, 6 Mar 2019 15:27:12 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F40C01310C2; Wed, 6 Mar 2019 15:27:09 -0800 (PST)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id B7D0E5FB6FF595F73C76; Wed, 6 Mar 2019 23:27:06 +0000 (GMT)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 6 Mar 2019 23:27:06 +0000
Received: from SJCEML521-MBS.china.huawei.com ([169.254.2.29]) by SJCEML701-CHM.china.huawei.com ([169.254.3.135]) with mapi id 14.03.0415.000; Wed, 6 Mar 2019 15:26:55 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>, "idr@ietf.org" <idr@ietf.org>
CC: "idr-chairs@ietf.org" <idr-chairs@ietf.org>
Thread-Topic: Call for IETF104 IDR agenda items
Thread-Index: AdTP+9uvO5Kq9lSxQCmMt3WjYm1/3gEdYQBQ
Date: Wed, 06 Mar 2019 23:26:54 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B2EA188@sjceml521-mbs.china.huawei.com>
References: <76CD132C3ADEF848BD84D028D243C927C347EBD0@NKGEML515-MBX.china.huawei.com>
In-Reply-To: <76CD132C3ADEF848BD84D028D243C927C347EBD0@NKGEML515-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.84]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F66B2EA188sjceml521mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/2ZYjDN5F2rWeJ5Ak6Vzyt1cRfPY>
Subject: Re: [Idr] Call for IETF104 IDR agenda items
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Mar 2019 23:27:15 -0000

IDR Chairs and Jimmy,

We would like a 10 minutes slot to present using BGP to advertise properties of a SD-WAN edge node WAN ports that face untrusted networks, such as the public internet:
https://datatracker.ietf.org/doc/draft-dunbar-idr-sdwan-port-safi/

Presenter: Linda Dunbar
Prefer: Monday afternoon IDR slot.

Abstract
The document specifies a new BGP NLRI and SAFI for advertising properties of a SD-WAN edge node WAN ports that face untrusted networks, such as the public internet. Those WAN ports may get assigned IP addresses from the Internet Service Providers (ISPs), may get assigned dynamic IP addresses via DHCP, or may have private addresses (e.g. inside third party Cloud DCs). Packets sent over those SDWAN WAN ports might need to be encrypted (depending on the user policies) or need to go through NAT. SD-WAN edge need to propagate those WAN ports properties to its SDWAN controller, which propagates to the authorized peers and manage the IPsec SAs among those peers for encrypting traffic via the untrusted networks.
BGP Route Reflectors (RR) are proposed as points of combination for this information in order to allow scaling of the SDWAN.

Thank you very much.
Linda Dunbar


From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Dongjie (Jimmy)
Sent: Friday, March 01, 2019 1:28 AM
To: idr@ietf.org
Cc: idr-chairs@ietf.org
Subject: [Idr] Call for IETF104 IDR agenda items

Dear all,

The agenda of IETF 104 has been published. IDR will meet twice, the first session is on Monday Afternoon (16:10-18:10), the second session is on Thursday Morning (10:50-12:20).

Please send any IDR agenda items you have to me and CC the chairs. Please include the name of the person who will be presenting, and the estimate time you'll need (including Q/A). You may also indicate which session you would prefer.

If you plan to make a presentation, please keep in mind the IDR tradition, "no Internet Draft - no time slot". You should also plan to send your slides to me and CC the chairs no later than 24 hours prior to the IDR meeting, though earlier is better. If we don't have your slides by the deadline, you may lose your slot. Please number your slides for the benefit of remote attendees. By default your slides will be converted to PDF and presented from the PDF. If you need to use any fancy builds or transitions, please make sure to arrange this with us in advance. Thanks.

And potential presenters, please take a look at the checklist for presenting at IDR:
https://trac.tools.ietf.org/wg/idr/trac/wiki/Checklist%20for%20presenting%20at%20an%20IDR%20meeting

Best regards,
Jie