Re: [DNSOP] status of the aname and svcb/httpsvc drafts
Erik Nygren <erik+ietf@nygren.org> Wed, 19 February 2020 23:39 UTC
Return-Path: <nygren@gmail.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 73CA0120820 for <dnsop@ietfa.amsl.com>; Wed, 19 Feb 2020 15:39:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level:
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 6_aw9rEVBlo9 for <dnsop@ietfa.amsl.com>; Wed, 19 Feb 2020 15:39:41 -0800 (PST)
Received: from mail-wr1-f43.google.com (mail-wr1-f43.google.com [209.85.221.43]) (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 6B0C8120241 for <DNSOP@ietf.org>; Wed, 19 Feb 2020 15:39:41 -0800 (PST)
Received: by mail-wr1-f43.google.com with SMTP id e8so2581167wrm.5 for <DNSOP@ietf.org>; Wed, 19 Feb 2020 15:39:41 -0800 (PST)
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=YMnYazTKL0hXMcyxJW4NCiG7IdeItNjb9WhogBfSdlo=; b=q2q0x8DJKBS/OduKoJdbasXahCYnJNfhfjKyTN45URC8JO2OppyK283NpKUuz3+kgW 4KYirrZ/D9Ww2E3a7YRHDxWSWRgLd2GozLTTv02MxwhMkWhRjFrlC3zGlESjoetAYhoT AiQ9/lAD8VNBv8Bm/iw6FvC4PR7u1t1ThaLHPC48uQ2siwXMzd1bk0D04Ac4LBTuFjCl 7g+p5Jhyx6wp36gmWUD6vGM0IOcidRl6PhHieD4d2XZlqJYyoXYUhdml3Enq1j7N/RCJ 6c78xpkcaGjQf0vcj3x27o4cUk/bYJuYmqFbQAV2h2mQWrimQPWmEy9cHVFUWjdCdoS+ O+uA==
X-Gm-Message-State: APjAAAV4AEYOrorH+8RJnNcekHOAE8/q3k5VbQGbuh5Z7k1prPayodZr pBdnt9mU7cFrV+nReB6p6mCD66te+hzjV50ByCc=
X-Google-Smtp-Source: APXvYqzqEGKtWmJqW9RMMLWusQgbwqhM+6rtk0LopZyJy1zP9a8tJw+3NyNWHq/X6q8shqQdlaz1IFuJ7YOU+L9+/Is=
X-Received: by 2002:adf:e686:: with SMTP id r6mr38849707wrm.177.1582155579693; Wed, 19 Feb 2020 15:39:39 -0800 (PST)
MIME-Version: 1.0
References: <b34f1b0d-fa65-23d4-1b2b-761b965a2aae@knipp.de> <CAG8jCEzO7zrfL5G5CzdJ=c5wipJgqqHfyeA-a3-QjquoyPYgvg@mail.gmail.com> <CAChr6SzqHnXszpEiW083NmtQAnvF8EKKvccUe9EHfjSUiAypjg@mail.gmail.com> <60DC6316-18C2-45F0-A848-CC7514309086@apple.com> <CAHw9_iJr_Zf=+gdHTmBeUuOjMFguZiktGMh1ow8k=CFnb5sSsw@mail.gmail.com>
In-Reply-To: <CAHw9_iJr_Zf=+gdHTmBeUuOjMFguZiktGMh1ow8k=CFnb5sSsw@mail.gmail.com>
From: Erik Nygren <erik+ietf@nygren.org>
Date: Wed, 19 Feb 2020 18:39:28 -0500
Message-ID: <CAKC-DJgLEaRhsLW6iSO4372zbiZXcuW=uFY9O1ETZ9WvMfLsNQ@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
Cc: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>, Olli Vanhoja <olli.vanhoja@gmail.com>, dnsop WG <DNSOP@ietf.org>, Klaus Malorny <Klaus.Malorny@knipp.de>, Rob Sayre <sayrer@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000004ea08a059ef64d89"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/n_biTgtl6kbp_yQqrh6AGIADMbY>
Subject: Re: [DNSOP] status of the aname and svcb/httpsvc drafts
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: Wed, 19 Feb 2020 23:39:44 -0000
Good idea. Created a PR: https://github.com/MikeBishop/dns-alt-svc/pull/110 But yes, we're actively working through issues on SVCB with the hope of publishing a new version shortly, and would certainly like to discuss in Vancouver. Erik On Wed, Feb 19, 2020 at 4:13 PM Warren Kumari <warren@kumari.net> wrote: > On Thu, Feb 20, 2020 at 6:13 AM Tommy Pauly > <tpauly=40apple.com@dmarc.ietf.org> wrote: > > > > > > > > On Feb 18, 2020, at 6:15 PM, Rob Sayre <sayrer@gmail.com> wrote: > > > > On Tue, Feb 18, 2020 at 8:17 AM Olli Vanhoja <olli.vanhoja@gmail.com> > wrote: > >> > >> > >> SVCB is active almost every day of the week in GitHub. > > > > > > If someone wanted to follow this work, which GitHub repo is relevant? > > > > I found this one: https://github.com/MikeBishop/dns-alt-svc > > > > But I'm not sure that's the right one. > > > > > > Yes, that is the correct GitHub. > > Could I suggest adding something like: > [ RFC Editor - please remove before publication. This document is being > collaborated on in Github at: > https://github.com/MikeBishop/dns-alt-svc. The most > recent version of the document, open issues, etc should all be > available here. The authors (gratefully) accept pull requests.] > > to the abstract - that way, people reading the draft know where submit > PRs, etc. > W > > > > > > > Thanks, > > Tommy > > > > > > thanks, > > Rob > > > > _______________________________________________ > > DNSOP mailing list > > DNSOP@ietf.org > > https://www.ietf.org/mailman/listinfo/dnsop > > > > > > _______________________________________________ > > DNSOP mailing list > > DNSOP@ietf.org > > https://www.ietf.org/mailman/listinfo/dnsop > > > > -- > I don't think the execution is relevant when it was obviously a bad > idea in the first place. > This is like putting rabid weasels in your pants, and later expressing > regret at having chosen those particular rabid weasels and that pair > of pants. > ---maf > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop >
- [DNSOP] status of the aname and svcb/httpsvc draf… Klaus Malorny
- Re: [DNSOP] status of the aname and svcb/httpsvc … Olli Vanhoja
- Re: [DNSOP] status of the aname and svcb/httpsvc … Eric Orth
- Re: [DNSOP] status of the aname and svcb/httpsvc … Tommy Pauly
- Re: [DNSOP] status of the aname and svcb/httpsvc … Rob Sayre
- Re: [DNSOP] status of the aname and svcb/httpsvc … Tommy Pauly
- Re: [DNSOP] status of the aname and svcb/httpsvc … Warren Kumari
- Re: [DNSOP] status of the aname and svcb/httpsvc … Erik Kline
- Re: [DNSOP] status of the aname and svcb/httpsvc … Erik Nygren
- Re: [DNSOP] status of the aname and svcb/httpsvc … Matthijs Mekking
- Re: [DNSOP] status of the aname and svcb/httpsvc … Klaus Malorny
- Re: [DNSOP] status of the aname and svcb/httpsvc … Shane Kerr
- Re: [DNSOP] status of the aname and svcb/httpsvc … Matthijs Mekking
- Re: [DNSOP] status of the aname and svcb/httpsvc … Evan Hunt
- Re: [DNSOP] status of the aname and svcb/httpsvc … Paul Vixie
- Re: [DNSOP] status of the aname and svcb/httpsvc … Benno Overeinder
- Re: [DNSOP] status of the aname and svcb/httpsvc … Klaus Malorny
- Re: [DNSOP] status of the aname and svcb/httpsvc … Vladimír Čunát
- Re: [DNSOP] status of the aname and svcb/httpsvc … Dan York
- Re: [DNSOP] status of the aname and svcb/httpsvc … Klaus Malorny
- Re: [DNSOP] status of the aname and svcb/httpsvc … Tim Wicinski
- Re: [DNSOP] status of the aname and svcb/httpsvc … Vladimír Čunát
- Re: [DNSOP] status of the aname and svcb/httpsvc … Klaus Malorny
- Re: [DNSOP] status of the aname and svcb/httpsvc … Vladimír Čunát
- Re: [DNSOP] status of the aname and svcb/httpsvc … Erik Nygren
- Re: [DNSOP] status of the aname and svcb/httpsvc … Ben Schwartz
- Re: [DNSOP] status of the aname and svcb/httpsvc … Brian Dickson
- Re: [DNSOP] status of the aname and svcb/httpsvc … Tony Finch
- Re: [DNSOP] status of the aname and svcb/httpsvc … Brian Dickson
- Re: [DNSOP] status of the aname and svcb/httpsvc … Bob Harold
- Re: [DNSOP] status of the aname and svcb/httpsvc … Tony Finch
- Re: [DNSOP] status of the aname and svcb/httpsvc … Andrew M. Hettinger
- Re: [DNSOP] status of the aname and svcb/httpsvc … Joe Abley
- Re: [DNSOP] status of the aname and svcb/httpsvc … Joe Abley
- Re: [DNSOP] status of the aname and svcb/httpsvc … Vladimír Čunát
- Re: [DNSOP] status of the aname and svcb/httpsvc … Tony Finch
- Re: [DNSOP] status of the aname and svcb/httpsvc … Evan Hunt
- Re: [DNSOP] status of the aname and svcb/httpsvc … Olli Vanhoja
- Re: [DNSOP] status of the aname and svcb/httpsvc … Lanlan Pan
- Re: [DNSOP] status of the aname and svcb/httpsvc … Paul Vixie
- Re: [DNSOP] status of the aname and svcb/httpsvc … Erik Nygren
- Re: [DNSOP] status of the aname and svcb/httpsvc … Andrew M. Hettinger
- Re: [DNSOP] status of the aname and svcb/httpsvc … Dan York
- Re: [DNSOP] status of the aname and svcb/httpsvc … Joe Abley
- Re: [DNSOP] status of the aname and svcb/httpsvc … Lanlan Pan
- Re: [DNSOP] status of the aname and svcb/httpsvc … Vladimír Čunát
- Re: [DNSOP] status of the aname and svcb/httpsvc … Vladimír Čunát
- Re: [DNSOP] status of the aname and svcb/httpsvc … Tony Finch
- Re: [DNSOP] status of the aname and svcb/httpsvc … Anthony Eden
- Re: [DNSOP] status of the aname and svcb/httpsvc … Matthijs Mekking
- Re: [DNSOP] [External] status of the aname and sv… Andrew M. Hettinger
- Re: [DNSOP] status of the aname and svcb/httpsvc … Tim Wicinski
- Re: [DNSOP] status of the aname and svcb/httpsvc … Tony Finch