RE: Ready for RTGwg WG adoption call for draft-dm-net2cloud-problem-statement & Gap analysis

Linda Dunbar <linda.dunbar@huawei.com> Mon, 14 January 2019 22:20 UTC

Return-Path: <linda.dunbar@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50BFB1313D9 for <rtgwg@ietfa.amsl.com>; Mon, 14 Jan 2019 14:20:49 -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 aFOU3aSNuhtB for <rtgwg@ietfa.amsl.com>; Mon, 14 Jan 2019 14:20:47 -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 BF7631313D6 for <rtgwg@ietf.org>; Mon, 14 Jan 2019 14:20:46 -0800 (PST)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 76A9428D6D9A98CF3DE6 for <rtgwg@ietf.org>; Mon, 14 Jan 2019 22:20:44 +0000 (GMT)
Received: from SJCEML702-CHM.china.huawei.com (10.208.112.38) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 14 Jan 2019 22:20:43 +0000
Received: from SJCEML521-MBS.china.huawei.com ([169.254.2.237]) by SJCEML702-CHM.china.huawei.com ([169.254.4.203]) with mapi id 14.03.0415.000; Mon, 14 Jan 2019 14:20:40 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Jeff Tantsura <jefftant.ietf@gmail.com>, Chris Bowers <chrisbowers.ietf@gmail.com>
CC: RTGWG <rtgwg@ietf.org>, "Andrew G. Malis" <agmalis@gmail.com>, JACQUENET Christian IMT/OLN <christian.jacquenet@orange.com>, "Mehmet Toy (mehmet.toy@verizon.com)" <mehmet.toy@verizon.com>
Subject: RE: Ready for RTGwg WG adoption call for draft-dm-net2cloud-problem-statement & Gap analysis
Thread-Topic: Ready for RTGwg WG adoption call for draft-dm-net2cloud-problem-statement & Gap analysis
Thread-Index: AQHUlFPkHyCCXlhMZE+L2PuO7eW3jaWvgA8g
Date: Mon, 14 Jan 2019 22:20:39 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66B23EC77@sjceml521-mbs.china.huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F66B2166F0@sjceml521-mbs.china.huawei.com> <F983118A-794F-4867-91F1-CA7EF3B7BCA8@gmail.com>
In-Reply-To: <F983118A-794F-4867-91F1-CA7EF3B7BCA8@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.97]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F66B23EC77sjceml521mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/nJRlH--rvd-nV30sWfWmvuU0Uhc>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2019 22:20:49 -0000

Jeff and Chris,

Can you start the RTGwg WG Adoption call for the following two drafts?

https://datatracker.ietf.org/doc/draft-dm-net2cloud-problem-statement/
         This document describes the problems of enterprises face today in
         connecting their branch offices to dynamic workloads in third party
         data centers (a.k.a. Cloud DCs).

         It examines some of the approaches for interconnecting workloads &
         applications hosted in cloud DCs with enterprises' on-premises DCs &
         branch offices. This document also describes some of the (network)
         problems that many enterprises face when they have workloads &
         applications & data split among hybrid data centers, especially for
         those enterprises with multiple sites that are already
         interconnected by VPNs (e.g. MPLS L2VPN/L3VPN) and leased lines.

         Current operational problems in the field are examined to determine
         whether there is a need for enhancements to existing protocols or
         whether a new protocol is necessary to solve them.

https://datatracker.ietf.org/doc/draft-dm-net2cloud-gap-analysis/
      This document analyzes the technological gaps when using SD-WAN to
         interconnect workloads & apps hosted in various locations,
         especially cloud data centers when the network service providers do
         not have or have limited physical infrastructure to reach the
         locations [Net2Cloud-problem].



Thank you very much.

Linda

-----Original Message-----
From: Jeff Tantsura [mailto:jefftant.ietf@gmail.com]
Sent: Saturday, December 15, 2018 2:55 AM
To: Linda Dunbar <linda.dunbar@huawei.com>
Cc: RTGWG <rtgwg@ietf.org>; Andrew G. Malis <agmalis@gmail.com>; JACQUENET Christian IMT/OLN <christian.jacquenet@orange.com>; Mehmet Toy (mehmet.toy@verizon.com) <mehmet.toy@verizon.com>
Subject: Re: Ready for RTGwg WG adoption call for draft-dm-net2cloud-problem-statement & Gap analysis

Hi Linda,

First of all - thanks for updating the drafts!

I think starting the wg adoption call 2nd week of January would be right time, since many folks are already on holidays and I’d really like the drafts to be well reviewed.

Regards,
Jeff

> On Dec 15, 2018, at 02:18, Linda Dunbar <linda.dunbar@huawei.com<mailto:linda.dunbar@huawei.com>> wrote:
>
> Jeff and Chris,
>
> We have made some changes based on the IETF103 discussion.
> We think the drafts are ready for WG adoption call.
> Since there is only one week left before Christmas, is it better to start the adoption call now and extend to the New Year? Or start after the New Year?
> https://datatracker.ietf.org/doc/draft-dm-net2cloud-problem-statement/
>
> https://datatracker.ietf.org/doc/draft-dm-net2cloud-gap-analysis/
>
> Thanks, Linda
>
> -----Original Message-----
> From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> [mailto:internet-drafts@ietf.org]
> Sent: Friday, December 14, 2018 6:12 PM
> To: Linda Dunbar <linda.dunbar@huawei.com<mailto:linda.dunbar@huawei.com>>; Christian Jacquenet <christian.jacquenet@orange.com<mailto:christian.jacquenet@orange.com>>; Linda Dunbar <linda.dunbar@huawei.com<mailto:linda.dunbar@huawei.com>>; Andrew Malis <agmalis@gmail.com<mailto:agmalis@gmail.com>>; Andrew G. Malis <agmalis@gmail.com<mailto:agmalis@gmail.com>>; Mehmet Toy <mehmet.toy@verizon.com<mailto:mehmet.toy@verizon.com>>
> Subject: New Version Notification for draft-dm-net2cloud-problem-statement-04.txt
>
>
> A new version of I-D, draft-dm-net2cloud-problem-statement-04.txt
> has been successfully submitted by Linda Dunbar and posted to the IETF repository.
>
> Name:        draft-dm-net2cloud-problem-statement
> Revision:    04
> Title:        Seamless Interconnect Underlay to Cloud Overlay Problem Statement
> Document date:    2018-12-11
> Group:        Individual Submission
> Pages:        18
> URL:            https://www.ietf.org/internet-drafts/draft-dm-net2cloud-problem-statement-04.txt
> Status:         https://datatracker.ietf.org/doc/draft-dm-net2cloud-problem-statement/
> Htmlized:       https://tools.ietf.org/html/draft-dm-net2cloud-problem-statement-04
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-dm-net2cloud-problem-statement
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-dm-net2cloud-problem-statement-04
>
> Abstract:
>   This document describes the problems of enterprises face today in
>   connecting their branch offices to dynamic workloads in third party
>   data centers (a.k.a. Cloud DCs).
>
>   It examines some of the approaches for interconnecting workloads &
>   applications hosted in cloud DCs with enterprises' on-premises DCs &
>   branch offices. This document also describes some of the (network)
>   problems that many enterprises face when they have workloads &
>   applications & data split among hybrid data centers, especially for
>   those enterprises with multiple sites that are already
>   interconnected by VPNs (e.g. MPLS L2VPN/L3VPN) and leased lines.
>
>   Current operational problems in the field are examined to determine
>   whether there is a need for enhancements to existing protocols or
>   whether a new protocol is necessary to solve them.
>
>
>
>
> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>