quick question on draft-ietf-rtgwg-net2cloud-problem-statement-00

Alia Atlas <akatlas@gmail.com> Sun, 02 June 2019 20:59 UTC

Return-Path: <akatlas@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 3849612008A for <rtgwg@ietfa.amsl.com>; Sun, 2 Jun 2019 13:59:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 Zm2TJ5z6O2VD for <rtgwg@ietfa.amsl.com>; Sun, 2 Jun 2019 13:59:33 -0700 (PDT)
Received: from mail-oi1-x22d.google.com (mail-oi1-x22d.google.com [IPv6:2607:f8b0:4864:20::22d]) (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 56ABF120086 for <rtgwg@ietf.org>; Sun, 2 Jun 2019 13:59:33 -0700 (PDT)
Received: by mail-oi1-x22d.google.com with SMTP id u64so11453523oib.1 for <rtgwg@ietf.org>; Sun, 02 Jun 2019 13:59:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=r+/glRPkkvkD62Ld2SWJgciRB0KsAlnAzu9BkSlqQqA=; b=bF6txBy9+RfWBoRb+Lt1y1ivjb8zp/1HLZoiZNIlYw5OuhUuLBTqWc9k1TMnOIy+dt EG265awOh94zB0FavNjV+WOVwf0zBgGq9WEQVREeQkC7Hg1Z46UzzJGalFHOFNvaG4yN jzDlAaaDxzSWiw1wkMGPaHl8nsLA7+g8VWkkh019x43AorEfIusNOr9/nHO3EbIF6O/b kEGPGxVZ/8Y8qPP/EHOaXvmCOZcyjO9SQN8qErHGAiJuVWD6Ecl+i63+ZdPPQ+EBuTGf AQhWGHxiWxcPB0ZRwROf7gGCG5eeZFawtxKJmYG4pNrPIU68oLqp1JCcivBQ7eseyLqG YIwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=r+/glRPkkvkD62Ld2SWJgciRB0KsAlnAzu9BkSlqQqA=; b=tJuY9gRAsycBm4Ep601YiTYAx9ChmwHhO3AgMQA3YowKrYSYMThkV1nObx8InX3IqL k2wTSKD5MWClKCtkJxoHiQtgEA/rA4i/RfS9+/DIicNsJTbzldIL+FDBY273CXWrNdgh Nd6DPoEvJNWQS1Kdrx5xDfaQgH0yhBXrtPVSdLn4VltE7eFv4izA8/elpWXG0lsi/QN4 lOd66wqS0Jlyx08zZFCRZ/SHUsXJdb1jFJK22TzVpQwDQJYYHFDFLxP3WSIiwhQVejpz KJQD+9EV1bUOnMp5UJwI3XGStUU8a0gva4NN6Zm5B9Z7VNORsDSSCf/3sY6hpmISq12Y 5NtQ==
X-Gm-Message-State: APjAAAWIulp3KIAtbmF4Eh4QH9vIMSmZSGncgTrDKmZyq0tzqlaNQl6y TRC29ZVCISY+LYqSxvZS3RAmxy2tZyA1qNBxDy4=
X-Google-Smtp-Source: APXvYqyi8hfDIh1I1aPm9XipMcJIi3MVLLvifjlDqqqE/U2t2SsSxGfBpj2CPfYDKTpTR97sEIsqoDN5A/0h9CI/R5w=
X-Received: by 2002:a54:4f13:: with SMTP id e19mr5874043oiy.128.1559509171340; Sun, 02 Jun 2019 13:59:31 -0700 (PDT)
MIME-Version: 1.0
From: Alia Atlas <akatlas@gmail.com>
Date: Sun, 02 Jun 2019 16:59:18 -0400
Message-ID: <CAG4d1rfSOr=EpTm5sDQ_FHK8r-ZNtvZXQdAtshp4tT324RgpBA@mail.gmail.com>
Subject: quick question on draft-ietf-rtgwg-net2cloud-problem-statement-00
To: "Andrew G. Malis" <agmalis@gmail.com>, Linda Dunbar <ldunbar@huawei.com>, JACQUENET Christian IMT/OLN <Christian.jacquenet@orange.com>, mehmet.toy@verizon.com
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002e8bb6058a5d862f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/vSuwxf5gORj-adnMdXfCOImMY0k>
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: Sun, 02 Jun 2019 20:59:35 -0000

Hi Linda, Andy, Christian, and Mehmet,

I finally took a quick read through both the problem-statement and
gap-analysis drafts
for net2cloud.  The problem-statement one is very clear and well-written.

I do have a quick question about this bullet point.

" - Many cloud DCs use an overlay to connect their gateways to the
        workloads located inside the DC. There has not been any
        standard to address the interworking between the Cloud Overlay
        and the enterprise' existing underlay networks."

Can you clarify what need you see for the interworking?  Currently, BGP is
just
used for exchanging routes and liveness.  I didn't see anything
specifically called out.

The drafts also touch only briefly on the direct interconnect.  Is that
because you see the connectivity provided by the MPLS VPN provider to be a
better fit into the SD-WAN use-case?

Regards,
Alia