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

Jeff Tantsura <jefftant.ietf@gmail.com> Sat, 15 December 2018 08:55 UTC

Return-Path: <jefftant.ietf@gmail.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 896DA12426E for <rtgwg@ietfa.amsl.com>; Sat, 15 Dec 2018 00:55:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 fnIkVyhinJ2r for <rtgwg@ietfa.amsl.com>; Sat, 15 Dec 2018 00:55:02 -0800 (PST)
Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E117912426A for <rtgwg@ietf.org>; Sat, 15 Dec 2018 00:55:01 -0800 (PST)
Received: by mail-wr1-x42f.google.com with SMTP id u4so6585541wrp.3 for <rtgwg@ietf.org>; Sat, 15 Dec 2018 00:55:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7dH8VNFZTAXXfBihIoeJJ5gZMGCgSfH/ciiFWpCZLT0=; b=QhppKue1IKMnoPPKZzK/dvvggyBLrF9EWtjVGsgVL2aoWFVttQEIbJjBrOxIHcClgV H43Ydqgaekt75lBp5Ihc//EdTYdZ43rsDowiS5PXQ9SO8G+LRuvUq+go38FcPu6IL2v5 1YtCCL+JTu0/1wbfrco5/RrIq4V3GgAeCnivTug5Dzskl4LD3YQjEm/gvjm/7tUpxqQ0 vJN166LKWqbuzC6hN2oG1AapaP3ow2PE6TVyHAyDDl2KqEWnswFplCeJgGIunW+5osom tNb6AEmsrLRPmsdGqKhn5UXAM6kM5AQWsM4hSUcTCk7i2mEINmfOJm3c3M2piU2XWuhp INkw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7dH8VNFZTAXXfBihIoeJJ5gZMGCgSfH/ciiFWpCZLT0=; b=INC5CYXEIiUwXZEjhIExAM6REGmcbCcLWmcRN66cvXTWLgKZ4+Sqvp9WyiVMpFpCM2 zNT3k1/4dpCTYXYaFGnKthNjSkokja84A+NkxMz1T8ycVNYYsngevb13An76b7OGu1TQ dWRV9GD41YS3ubpFauU38IUzo6WSklX/lM0f0ygO5HceeoZV1DjoUBU6xAnnnnoqn4X2 mp6KlFWTXdhisgk/MdyPUDKz4fumSfBqJbYuPDGnnhETYSRcZNROQn0F6oYc4tSsy+jy c1IrN3KJ0lpVjurOLrsIhGLvPiPgu1SU3ArEOluzBThp4/cDEgUodY4DTyZbyYF1WA4x HBUg==
X-Gm-Message-State: AA+aEWYAtWB+X9Z6+A0GOPbSyxylEit70e81wI4HMiTWZco+WVm7T1pB WFvs1hQa6Fg2xK2gmIisAILdddKrcLk=
X-Google-Smtp-Source: AFSGD/VN2ZP+Ld5YmhQxc4wSiv9UMmxfS0cbNyP4BZLOwXQrQgukdIUyqmmVbTcpM6vbaM9b6KG8Ag==
X-Received: by 2002:a05:6000:12c4:: with SMTP id l4mr4806447wrx.134.1544864100092; Sat, 15 Dec 2018 00:55:00 -0800 (PST)
Received: from [10.0.0.5] ([87.71.76.120]) by smtp.gmail.com with ESMTPSA id 126sm11756345wmx.26.2018.12.15.00.54.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 15 Dec 2018 00:54:59 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
Subject: Re: Ready for RTGwg WG adoption call for draft-dm-net2cloud-problem-statement & Gap analysis
From: Jeff Tantsura <jefftant.ietf@gmail.com>
X-Mailer: iPhone Mail (16C50)
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B2166F0@sjceml521-mbs.china.huawei.com>
Date: Sat, 15 Dec 2018 10:54:57 +0200
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>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F983118A-794F-4867-91F1-CA7EF3B7BCA8@gmail.com>
References: <4A95BA014132FF49AE685FAB4B9F17F66B2166F0@sjceml521-mbs.china.huawei.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/T1TDv_fZkOSDdBULHmWeTg1nRTA>
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: Sat, 15 Dec 2018 08:55:04 -0000

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> 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] 
> Sent: Friday, December 14, 2018 6:12 PM
> To: Linda Dunbar <linda.dunbar@huawei.com>; Christian Jacquenet <christian.jacquenet@orange.com>; Linda Dunbar <linda.dunbar@huawei.com>; Andrew Malis <agmalis@gmail.com>; Andrew G. Malis <agmalis@gmail.com>; Mehmet Toy <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
>