[Add] 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: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E8593A0E26 for <add@ietfa.amsl.com>; Tue, 4 Aug 2020 10:54:10 -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 VvYtfB0nq7Wm for <add@ietfa.amsl.com>; Tue, 4 Aug 2020 10:54:08 -0700 (PDT)
Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (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 49F9A3A0E27 for <add@ietf.org>; Tue, 4 Aug 2020 10:54:08 -0700 (PDT)
Received: by mail-wm1-x334.google.com with SMTP id 3so3783702wmi.1 for <add@ietf.org>; Tue, 04 Aug 2020 10:54:08 -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=8thCiUOxG3iFi5gWRvV86lnS2U1LZB95zZvJl2JIsqs=; b=YI2pJsjz/XpIE1dFHwz9O0KOmi035Yb5USgvo21Y50utz6cLEueFXcZJQ9G+JG+UVJ b0FN/H+poCsDefxukwcBrYvp7OxMaK7IIzWqdZhQnA2ql73ZIWjfgRXTJj7gfEN9+jSF N7lwI+SXUR4vMVi0VWyqqCQmpLKHMGXoXogfD6x1KXUoF/7xB/f5G3Lmlf3GOO4S016n 9wEcw3oxIkpi8dBtk2Zz3m78xQk5kf/3DI3378Z8mBOR8LcVkJw6FZEOUCkrTGO+nMIt JGTgUNRFp7PbTBOGhFbzqBYoy4r6zhNRpFOqqQnwQol7KCTR/zdYwVHih29LSsYodGEc XHLg==
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=8thCiUOxG3iFi5gWRvV86lnS2U1LZB95zZvJl2JIsqs=; b=TwqnY9d72+gGuUlJGmWojyMnxsFlhwFXv5n0dkshrmcrX0MIr9DfkLNXzE4x0RH2PU J9838hAtBfE4cZLmyu4AHyL7BsBdBj/LmAVuZa8FcIBtzIAqLGnzybVHVYTB3XMmQOcm 4gKsJRMDuKqR5ZYkNMgr1fM/55whtXbALymdUw2Enm3v7G6rH8Mc41Z6y36uWR01O74x BP8Lz6R0styTg0UUWlqe6w20wg6DwDwALCMBv0he3GMYpwauwFici2zbJvEgcuI5Pcj7 4lSjXZHDX5Pe3tKdkwUTWsbYsjXFKTI9LmmLG4Mu1twwp2NhEfS6fOZbg86hXJTDfX7L jd1A==
X-Gm-Message-State: AOAM532KtxtmyZHS3PwVFiaTzANU7Zo94Y8ndGFYaYMxvvGKKV1Q63xR CAWhYJKT8rTN2OQ4q8GkjNMKoj82OQeK9U9HdvjCvX6GnN8=
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="000000000000047e6905ac10f113"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/jm9vqhguvN48oLV8oJfbzGrv23w>
Subject: [Add] Fwd: New Version Notification for draft-schwartz-svcb-dns-00.txt
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-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
- [Add] Fwd: New Version Notification for draft-sch… Ben Schwartz
- Re: [Add] New Version Notification for draft-schw… Ben Schwartz
- Re: [Add] Fwd: New Version Notification for draft… Steffen Nurpmeso
- Re: [Add] Fwd: New Version Notification for draft… Steffen Nurpmeso
- Re: [Add] Fwd: New Version Notification for draft… Ben Schwartz
- Re: [Add] Fwd: New Version Notification for draft… Steffen Nurpmeso
- Re: [Add] New Version Notification for draft-schw… Eric Orth
- Re: [Add] New Version Notification for draft-schw… Ben Schwartz
- [Add] DNS URI scheme (was SVCB for DNS) Martin Thomson
- Re: [Add] New Version Notification for draft-schw… Eric Orth
- Re: [Add] DNS URI scheme (was SVCB for DNS) Ben Schwartz
- Re: [Add] New Version Notification for draft-schw… Ben Schwartz
- Re: [Add] DNS URI scheme (was SVCB for DNS) Tommy Pauly
- Re: [Add] DNS URI scheme (was SVCB for DNS) Eric Orth
- Re: [Add] DNS URI scheme (was SVCB for DNS) Ted Hardie
- Re: [Add] DNS URI scheme (was SVCB for DNS) Martin Thomson
- Re: [Add] DNS URI scheme (was SVCB for DNS) Ted Hardie
- Re: [Add] DNS URI scheme (was SVCB for DNS) Christian Huitema
- Re: [Add] DNS URI scheme (was SVCB for DNS) Ted Hardie