From mellon@fugue.com Thu Oct 26 06:05:50 2023 Return-Path: X-Original-To: alto@ietfa.amsl.com Delivered-To: alto@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE1F9C14CE4A for ; Thu, 26 Oct 2023 06:05:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.908 X-Spam-Level: X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20230601.gappssmtp.com Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 96pYdCbMj9yB for ; Thu, 26 Oct 2023 06:05:49 -0700 (PDT) Received: from mail-qv1-xf30.google.com (mail-qv1-xf30.google.com [IPv6:2607:f8b0:4864:20::f30]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7228C151524 for ; Thu, 26 Oct 2023 06:05:49 -0700 (PDT) Received: by mail-qv1-xf30.google.com with SMTP id 6a1803df08f44-66cfd874520so5883886d6.2 for ; Thu, 26 Oct 2023 06:05:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20230601.gappssmtp.com; s=20230601; t=1698325548; x=1698930348; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=5ZkUs8Y+8yPACa9NwHxg/zwQ4okO38Y8Zjhq7pad/Uk=; b=NgNj43Ju0ceMvBFT6Gd7R0DvcJBfOs33V97FBeUvGO9ZCmCYU8DdtfAno8UEiOXlZS PeCa7ANxhuHdqjZA1Ufer+c/CoYbQF50/4LMiUb1HFAQtgEsgzDdy6Cwj1StM+sZjo0r ut0s0WjUwGPBRK0e8tCkEh+LOO4KKHuyq8kuPGryJaTauHkjq5b4xkCvVwKq6BGX5n+m 8LA8U64yCFWFrHimbYGt2VVVJmn2AjU+zkUFy5Bpxz4EQR5sCvt2PMioprQlWZDU5uOe IoDc0T+as1n2xmOYlupG6IfRoanHHprVboOvvYGlf6DCYqXFaGn7tzY/xKZRfYiUojZh rlJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698325548; x=1698930348; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=5ZkUs8Y+8yPACa9NwHxg/zwQ4okO38Y8Zjhq7pad/Uk=; b=hgOshFdDLFug99WZfDtkdGHpayVnbAvY7Tgc3/dJYCxND9rjXqwDPAp8/YTCMKpCr8 o3woe4s3fmCe6aVROl2lbTIvCtV60MUj3ebJjGTiQYxqdUu3o35waQZVDxxewvbPiICy lchBn3ngXYkglERQ1ahTz4bH2hPuKvp4eJLlOQ3p3PtfvEZNVw7GANvw/W4wNM0j1ah0 wXASKtyrfUWTI2u+AOv+fIOCu6rTTDDRQF+dvOy6EkigFPBG/WvbNQmMLP1J19n5vgAR xXU0ZMV4IBa18eDgwQSMePZ6h6TwQ029nEOdszLmkgeyv5jKmbgtUUx9T1ZrOc2XdnT2 1UHQ== X-Gm-Message-State: AOJu0YzyKFOctOYfWfwzsWfbjP2LCp99OuMMCGCDF9smyvVzpNY+U9AB PttD4y4hP2ac+Ist6ywrjZGlIaF32CqKTyEBWQxX/A== X-Google-Smtp-Source: AGHT+IF4gKfqr3SP3UQvWXyes8unFn198SCSryy1CvDxsrVhFz9yL3vBE2vhlV+a+I4dN5Ume+3jzwFEsWaSwwCMOhM= X-Received: by 2002:a05:6214:f61:b0:66d:8524:ebf0 with SMTP id iy1-20020a0562140f6100b0066d8524ebf0mr20771408qvb.15.1698325548588; Thu, 26 Oct 2023 06:05:48 -0700 (PDT) MIME-Version: 1.0 References: <169808661546.45653.348035276258481740@ietfa.amsl.com> In-Reply-To: From: Ted Lemon Date: Thu, 26 Oct 2023 15:05:12 +0200 Message-ID: To: Jensen Zhang Cc: dnsdir@ietf.org, alto@ietf.org, draft-ietf-alto-oam-yang.all@ietf.org, last-call@ietf.org Content-Type: multipart/alternative; boundary="0000000000000975a906089e3b5d" Archived-At: Subject: Re: [alto] Dnsdir telechat review of draft-ietf-alto-oam-yang-15 X-BeenThere: alto@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Oct 2023 13:05:50 -0000 --0000000000000975a906089e3b5d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Okay, so in fact both forms of the NAPTR value are going to be used as a DNS owner name. Either the owner name will be generated as an IN-ADDR string based on the ip address, or it is represented literally? If so, it would certainly make sense to say that explicitly to help the reader connect that to what is said in the RFC you're referencing. Although as I said earlier, I am not prepared to insist on this=E2=80=94you have to decid= e whether you think I'm confused because I'm not an SME, and everyone who reads this will be an SME, or whether in fact it would be helpful to add some clarifying text. From your perspective, what I'm proposing you say might actually be more confusing than not saying it, since I'm using DNS terminology which may not be known to someone who's an ALTO SME. --0000000000000975a906089e3b5d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Okay, so in fact both forms of the NAPTR value are going t= o be used as a DNS owner name. Either the owner name will be generated as a= n IN-ADDR string based on the ip address, or it is represented literally? I= f so, it would certainly make sense to say that explicitly to help the read= er connect that to what is said in the RFC you're referencing. Although= as I said earlier, I am not prepared to insist on this=E2=80=94you have to= decide whether you think I'm confused because I'm not an SME, and = everyone who reads this will be an SME, or whether in fact it would be help= ful to add some clarifying text. From your perspective, what I'm propos= ing you say might actually be more confusing than not saying it, since I= 9;m using DNS terminology which may not be known to someone who's an AL= TO SME.
--0000000000000975a906089e3b5d--