[DNSOP] Fwd: New Version Notification for draft-schwartz-svcb-dns-00.txt
Ben Schwartz <bemasc@google.com> Tue, 04 August 2020 17:54 UTC
Return-Path: <bemasc@google.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B38D13A0E2E for <dnsop@ietfa.amsl.com>; Tue, 4 Aug 2020 10:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level:
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 HR2AO7eLlS_z for <dnsop@ietfa.amsl.com>; Tue, 4 Aug 2020 10:54:08 -0700 (PDT)
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (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 0BB043A0E26 for <dnsop@ietf.org>; Tue, 4 Aug 2020 10:54:07 -0700 (PDT)
Received: by mail-wm1-x332.google.com with SMTP id d190so3470333wmd.4 for <dnsop@ietf.org>; Tue, 04 Aug 2020 10:54:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=OEIYYAYqJqOr3K5GzaQTV8klnFQ37jf0OWT21d2jNLY=; b=Sypw1Ni2oRfYS1vcTT4GRHn7thy28BiiOfJp3ZY4cnLLsrsG1Ieo110T3AufdNEYqL p1Fm3mi3KtsVTj71CNMf/DUHxLskxxflIzRv30/M0wOVx9TrJ3CFEbt8i9kl/Z6ekwlu p3OiKhC7n8DbtZuIJpXzgrPu2pHPm0U1gHRo9rRke5v40FcAtYEQaAuBj3oCeCazJ9li bfCnL4ahM1CjyHiF4UME5nhcosOHA1AYFTf6W9hZDkVRvq0uDH4/hwBrF6Ipe7JLnBY7 qSV4pvUYvvr/dr34mrA6KviA6wkzeRantgg6KMSnBvlTXxnrdqe2zPzwJKh+T5JPVxc3 aHTg==
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; bh=OEIYYAYqJqOr3K5GzaQTV8klnFQ37jf0OWT21d2jNLY=; b=UumGfq7TaZwvVtLRqBJDbWLUdT/8jSQVyWEuudP7z1+m2xiEZOeeezvzhP3ZDWwmQ1 B7LbVkNHQoZcO9EIzzzZ1eeNlhf7yxE0nL8PJWBBaMOJEdXWM6zyMb0/lLIS2JPQ3MIq 7ZsNA6OU1oNWYKY+i+LNhaEiDWMMU438npI049Tw0DIcBEqUvQokvSoONtbs9pAibp/T x3qeYQwPpNQSy0e6MiDnSTn5ucxV9RpOD6hdxL+f9wBMgs8ndSKOWZmO84XkiKxnN7yN pXJtjxv8jmHXFRaUy9WzXgy7SjrdIT+8a2GuAh0Kv+P9UwnxM3glRPDAJTZRzCW4MXl3 X8Bw==
X-Gm-Message-State: AOAM532TIj7KtlTzVVhTjzCnnOEWnNDGJDaxwi3ca0sDeBDtD3obdXP5 4yiOSQAJ8PlOxKeOFG1CCIfj9sEmS1DpzyauUhfK5w==
X-Google-Smtp-Source: ABdhPJyNKvbGcP4F1Cr4EZKmEocKOwHLXzFE/bRJRY2W/KDU3HE1MXnd1X30yBxwg4bewZsuOxEzQHKO2RCggDMsvmc=
X-Received: by 2002:a1c:49c6:: with SMTP id w189mr4786475wma.97.1596563646141; Tue, 04 Aug 2020 10:54:06 -0700 (PDT)
MIME-Version: 1.0
References: <159656272783.7072.6229544475907348131@ietfa.amsl.com>
In-Reply-To: <159656272783.7072.6229544475907348131@ietfa.amsl.com>
From: Ben Schwartz <bemasc@google.com>
Date: Tue, 04 Aug 2020 13:53:54 -0400
Message-ID: <CAHbrMsDtFNDB5TDz=HNejVi_RMbq_8Q6=o6iW_gyDr=ggZjyNA@mail.gmail.com>
To: ADD Mailing list <add@ietf.org>, DNS Privacy Working Group <dns-privacy@ietf.org>, dnsop <dnsop@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="00000000000004655905ac10f1ed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/wYoi3YUMLREBOH0jWe-rIugbRvw>
Subject: [DNSOP] Fwd: New Version Notification for draft-schwartz-svcb-dns-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Aug 2020 17:54:10 -0000
Hi ADD and DPRIVE, I've noticed three recent drafts that propose to use the SVCB format: draft-mglt-add-rdp, draft-tapril-ns2, and draft-pauly-add-resolver-discovery. These drafts, across multiple working groups, consider distinct use cases and architectures, but they all propose using SVCB (in very different ways) to convey information about a DNS server that supports encrypted transport. In the interest of harmonizing these proposals, creating a solid foundation, and separating concerns, I've written a short draft that specifies _only_ a minimal SVCB mapping for DNS URIs*, and does not address any specific use case. I hope this draft can enable each of these proposals to focus more on their goals, and worry less about the SVCB encoding. (It also serves as an interesting test of the SVCB design.) Please review, Ben Schwartz *SVCB is based on URIs like https://, so for a DNS mapping we start with dns:// URIs. ---------- Forwarded message --------- From: <internet-drafts@ietf.org> Date: Tue, Aug 4, 2020 at 1:38 PM Subject: New Version Notification for draft-schwartz-svcb-dns-00.txt To: Benjamin Schwartz <bemasc@google.com> A new version of I-D, draft-schwartz-svcb-dns-00.txt has been successfully submitted by Benjamin Schwartz and posted to the IETF repository. Name: draft-schwartz-svcb-dns Revision: 00 Title: Service Binding Mapping for DNS URIs Document date: 2020-08-04 Group: Individual Submission Pages: 8 URL: https://www.ietf.org/internet-drafts/draft-schwartz-svcb-dns-00.txt Status: https://datatracker.ietf.org/doc/draft-schwartz-svcb-dns/ Htmlized: https://tools.ietf.org/html/draft-schwartz-svcb-dns-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-schwartz-svcb-dns Abstract: The SVCB DNS record type expresses a bound collection of endpoint metadata, for use when establishing a connection to a named service. DNS itself can be such a service, when the server is identified by a hostname in a "dns:" URI. This document provides the SVCB mapping for name-based DNS URIs, allowing DNS servers to indicate support for new transport protocols. 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
- [DNSOP] Fwd: New Version Notification for draft-s… Ben Schwartz
- Re: [DNSOP] New Version Notification for draft-sc… Ben Schwartz