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

[Linda Dunbar <[e-mail]>]

Jeff, 

Thanks for the suggestion. It is a good idea. 

Linda

-----Original Message-----
From: Jeff Tantsura [mailto:[e-mail]] 
Sent: Saturday, December 15, 2018 2:55 AM
To: Linda Dunbar <[e-mail]>
Cc: RTGWG <[e-mail]>; Andrew G. Malis <[e-mail]>; JACQUENET Christian IMT/OLN <[e-mail]>; Mehmet Toy ([e-mail]) <[e-mail]>
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 <[e-mail]> 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: [e-mail] [mailto:[e-mail]] 
> Sent: Friday, December 14, 2018 6:12 PM
> To: Linda Dunbar <[e-mail]>; Christian Jacquenet <[e-mail]>; Linda Dunbar <[e-mail]>; Andrew Malis <[e-mail]>; Andrew G. Malis <[e-mail]>; Mehmet Toy <[e-mail]>
> 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
>