Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-01.txt

Erik Nygren <erik+ietf@nygren.org> Tue, 14 July 2020 14:13 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 7049D3A07A5 for <dnsop@ietfa.amsl.com>; Tue, 14 Jul 2020 07:13:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 82DatOJZC7iu for <dnsop@ietfa.amsl.com>; Tue, 14 Jul 2020 07:13:39 -0700 (PDT)
Received: from mail-wr1-f53.google.com (mail-wr1-f53.google.com [209.85.221.53]) (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 421383A07A2 for <dnsop@ietf.org>; Tue, 14 Jul 2020 07:13:39 -0700 (PDT)
Received: by mail-wr1-f53.google.com with SMTP id z2so21909088wrp.2 for <dnsop@ietf.org>; Tue, 14 Jul 2020 07:13:39 -0700 (PDT)
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=zjVgeqx1R+E5r/PY40wt3GY75iOU6XFnZ9NHDuyf4D4=; b=fuo7crkPBHhsAFHsnFlLbWJFCbcztr8uhPg2a2KnIrOq3M339Vny+wOAkPKwVm28Uv qQIWu1HhoHPPM8TvFCj6d9A2eUG46SsnupzDdqKgKSPdXr+qd5QhIg98zZAuy8eXCrTp aMih6w9s5w6ITqBfQLJNTO1wq8oeVX+goG+KqyLnLAKUHSTK25zdRLE0/peuHklYru7H p11obGBlVDdaH8ukM3KRHOQn7HXZh3yLn5IN1LBjeGqscnXfspcjyFYIv0Jg4BcnkU5h IfJjYS3WBZYU/YUpP/ZQd0LxJlLaoqFeeTRHWNt6gJLeNzgt4YXIXECkSpBQi72/ABoT KSEw==
X-Gm-Message-State: AOAM533EB+s/1qXMvg0sKm0fCRVye1z/X83h9HmB4An2oI0AuLuRLjif 2ca+5+2HZleUU19USjDFH+Pgb3UTNwpMBLpfwNg=
X-Google-Smtp-Source: ABdhPJwBK2ygc3z27hrAhNamZxEs2NFEV2vQM2q2DQY+a7oUsN831qiCiX89yOnUGwmKL/nrteJHQoj/erGVjF4yjCs=
X-Received: by 2002:a5d:458a:: with SMTP id p10mr5838311wrq.184.1594736017544; Tue, 14 Jul 2020 07:13:37 -0700 (PDT)
MIME-Version: 1.0
References: <159467255037.715.11891218110803113785@ietfa.amsl.com> <F9BB7255-82D7-402C-9FB1-BA4EEB359B58@isc.org>
In-Reply-To: <F9BB7255-82D7-402C-9FB1-BA4EEB359B58@isc.org>
From: Erik Nygren <erik+ietf@nygren.org>
Date: Tue, 14 Jul 2020 10:13:26 -0400
Message-ID: <CAKC-DJh06YdihSstbj_cf_0PfiK=e=3sPAwR9oBDKYDi_jCZFw@mail.gmail.com>
To: Mark Andrews <marka@isc.org>
Cc: dnsop WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d61a2705aa6769a7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/-Ey2guncHzbyoNIp7ydkS2v_-nE>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-01.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, 14 Jul 2020 14:13:42 -0000

Would this be better as a SHOULD NOT?  Or just better to remove this,
or replace with non-normative txt?
Opened: https://github.com/MikeBishop/dns-alt-svc/issues/221

On Mon, Jul 13, 2020 at 8:03 PM Mark Andrews <marka@isc.org> wrote:

> Section 2.4.1.  AliasMode paragraph 2.  Why have "MUST NOT" here?
>
>
>    The primary purpose of AliasMode is to allow aliasing at the zone
>    apex, where CNAME is not allowed.  In AliasMode, TargetName MUST be
>    the name of a domain that has SVCB, AAAA, or A records.  It MUST NOT
>    be equal to the owner name, as this would cause a loop.
>
> Nameservers and clients need to detect loops regardless of the number of
> records that form the loop.  All this does is force vendors to write
> additional
> code to detect this one sub-case of a loop.  These are also the only RR
> types
> that need to have their owner names available to parse them.
>
> Mark
>
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742              INTERNET: marka@isc.org
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>