Re: [dnssd] Solicit feedback on the problems of DNS for Cloud Resources described by the draft-ietf-rtgwg-net2cloud-problem-statement

David Schinazi <dschinazi.ietf@gmail.com> Tue, 11 February 2020 20:37 UTC

Return-Path: <dschinazi.ietf@gmail.com>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0782120B40; Tue, 11 Feb 2020 12:37:46 -0800 (PST)
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 D6cDtDEAYB1g; Tue, 11 Feb 2020 12:37:43 -0800 (PST)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 85D59120B35; Tue, 11 Feb 2020 12:37:42 -0800 (PST)
Received: by mail-lf1-x135.google.com with SMTP id 203so7987911lfa.12; Tue, 11 Feb 2020 12:37:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hMdwqYdhc1Zyi9hREW4QOkJ81CxQW6d3TaxQq4kABtE=; b=H9gfb/5Asayk7tUTRU45a3f6SgYlvEMDQBQ9NeTyt6Febnw7YIKAc9FGCG5gm30DlX aaq2mvACXceWosd4lY2RPeZl+u6m5k95lUqYYcaZnxzvympm+oNrLmysoP9RtLVY/54J jrkhCjmesHCierCWlkTFwxoTyudVg0IBFeped8hbhoR6Ysbj5yq+VecrMCLMfgWsxS18 dbLLNmd9dSJMzsnCV5mtkWMLHkoqxmPmfeHmquzoS/4BZ7gzy5ukuvCwLqQdAbsYbxEM rrOtrsvTrMXKOYeU96yg7LsLvITreUC5j7P5mSYX606XLyF2FPizcnznFEEhLT/P8+Wz f1nA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hMdwqYdhc1Zyi9hREW4QOkJ81CxQW6d3TaxQq4kABtE=; b=pa4ZEa0wgetIbcsfleD6Z5KdPLfKMGBHbfKnHapKLDrIs9ME8JhQ3HP6cX0S8TQMxa 9bgZPfB6UK6huMUxAbsN3+2jOFNHrhdiv/Z6xJJiWu+bJvFiAqTiN/b/67wXhxQSizKU r5ekQwTba4PyiKZLhm+RcF6QmbWckU/BPmIkHaYjL+9BO1D2cwdj7i0c2q5Ak4V+qxvf f53/mNLo+53tdnnF0Ix0/b7mMsf0xoOWbdlYhqGDPhcbPUYQ6Z2TWiK+3gePYhadyM81 F+2T06hoUevcq9uq9Ru0I7J8E1YE+OJmFtmy4Kthcwi+ACcdSk0kes+hFI+hap8rw+Sc uOsQ==
X-Gm-Message-State: APjAAAXuuchpCEuDC0Duxx/qCl/vTg6TIjrkQ+3VRBFyudS5afEiJ/st Aly1cncRdFwNELOORqldehAn79fTI5FopyBob8VTEB9K
X-Google-Smtp-Source: APXvYqwL9Q8fTJ1Kj4HxegiVKjAaKdkBw88RMAFesppPSSjXrAp8uVVhIWvl77xDNirXH65Fbvx5FCKkj9dziF9x1O4=
X-Received: by 2002:a19:5f05:: with SMTP id t5mr4650152lfb.149.1581453460546; Tue, 11 Feb 2020 12:37:40 -0800 (PST)
MIME-Version: 1.0
References: <BN6PR1301MB2083B6F88FDE9A0A4EA2384985180@BN6PR1301MB2083.namprd13.prod.outlook.com>
In-Reply-To: <BN6PR1301MB2083B6F88FDE9A0A4EA2384985180@BN6PR1301MB2083.namprd13.prod.outlook.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Tue, 11 Feb 2020 12:37:29 -0800
Message-ID: <CAPDSy+6GTg8WB=0RBYfk4ATD1ckybLB2j2Xsn1PQcyd3TOjjhg@mail.gmail.com>
To: Linda Dunbar <linda.dunbar@futurewei.com>
Cc: "dnssd@ietf.org" <dnssd@ietf.org>, RTGWG <rtgwg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bea7e4059e52d31d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/4C7FUnLIFVhttc3IJyJJdkOH9GU>
Subject: Re: [dnssd] Solicit feedback on the problems of DNS for Cloud Resources described by the draft-ietf-rtgwg-net2cloud-problem-statement
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Feb 2020 20:37:47 -0000

Hi Linda,

I think you may have the wrong IETF list.
DNSSD is about DNS Service Discovery (RFC 6763),
not general-purpose DNS. I think you want dnsop@ietf.org

David

On Tue, Feb 11, 2020 at 11:28 AM Linda Dunbar <linda.dunbar@futurewei.com>
wrote:

> DNS experts,
>
>
>
>
> https://datatracker.ietf.org/doc/draft-ietf-rtgwg-net2cloud-problem-statement/
> describes the problems that enterprises face today when interconnecting
> their branch offices with dynamic workloads in third party data centers
> (a..k.a. Cloud DCs).
>
> There can be many problems associated with network connecting to or among
> Clouds, many of which probably are out of the IETF scope. The objective of
> this document is to identify some of the problems that need additional work
> in IETF Routing area. Other problems are out of the scope of this document.
>
>
>
> During IETF 106, we received comments that the document should cover the
> problems associated with DNS service by different Cloud Operators for
> Enterprise to utilize Cloud Resources even though DNS is not within the
> scope of IETF routing area.  We greatly appreciate DNS experts to provide
> comments to our description.
>
>
>
>
> 3.4 DNS for Cloud Resources
>
> DNS name resolution is essential for on-premises and cloud-based
> resources. For customers with hybrid workloads, which include on-premises
> and cloud-based resources, extra steps are necessary to configure DNS to
> work seamlessly across both environments.
>
> Cloud operators have their own DNS to resolve resources within their Cloud
> DCs and to well-known public domains. Cloud’s DNS can be configured to
> forward queries to customer managed authoritative DNS servers hosted
> on-premises, and to respond to DNS queries forwarded by on-premises DNS
> servers.
>
> For enterprises utilizing Cloud services by different cloud operators, it
> is necessary to establish policies and rules on how/where to forward DNS
> queries to. When applications in one Cloud need to communication with
> applications hosted in another Cloud, there could be DNS queries from one
> Cloud DC being forwarded to the enterprise’s on premise DNS, which in turn
> be forwarded to the DNS service in another Cloud. Needless to say,
> configuration can be complex depending on the application communication
> patterns.
>
>
>
>
>
> Thank you very much.
>
>
>
> Linda Dunbar
> _______________________________________________
> dnssd mailing list
> dnssd@ietf.org
> https://www.ietf.org/mailman/listinfo/dnssd
>