Re: [DNSOP] I-D Action: draft-ietf-dnsop-iana-class-type-yang-00.txt

Bob Harold <rharolde@umich.edu> Thu, 16 January 2020 14:58 UTC

Return-Path: <rharolde@umich.edu>
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 71AE012008D for <dnsop@ietfa.amsl.com>; Thu, 16 Jan 2020 06:58:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umich.edu
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 E8sly2dmL1PI for <dnsop@ietfa.amsl.com>; Thu, 16 Jan 2020 06:57:58 -0800 (PST)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (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 9BB56120043 for <dnsop@ietf.org>; Thu, 16 Jan 2020 06:57:58 -0800 (PST)
Received: by mail-lf1-x12a.google.com with SMTP id l18so15725563lfc.1 for <dnsop@ietf.org>; Thu, 16 Jan 2020 06:57:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xVWH/VAaf7FM4yo1YsE3ttmWkJA1ZjBrSjgXoADgNc0=; b=WB1qPuR+VYCHrwRzw/pZUxQLEmpQ60VcU0lwB/ukqQ4iKuDSb6VJ9G7H9FTjn+Juld RlEtmhU2sgJULdJRJesLamo+AvGPu0oyg8dLOfWvEqzVjvUDZdPiKO/dEvRLfXNDa0+P DZmzwTGiFKiiFv3J7KrlOgxV9K0iyGRlrYSpSd7U90rxjtNwnI9YIMjP1AYSQZ/0BoF+ aU0yPnmIZ4+V8i79+btGR4rR319MNxfTLl/3vdINIMECQ4yb6SKCvDQgspb3OWPgFrkf QiVKwqMkAxEZnPl7e57kbEH5LWKVjJoF0/Mogtmm3GXb9dwZngzViqAnQ6SkUbEg5GMM 0I9w==
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=xVWH/VAaf7FM4yo1YsE3ttmWkJA1ZjBrSjgXoADgNc0=; b=pJ22yyBvMpXjdUdEpo3K1ihb709Vs+RW4ZczkBrlQQgNRWbopjKnK+gmY090BTkSpR /iUaXciL3ui9ACZKZmbwNsjO8jg9VM5EAOeULmVOlhCEJUOQrQr5XEfkzTE0Co26hvWX o8cCCVqu2iU3+NTb03J4etFWM2/BwDfaSLb4Ym4ykfqjcFtO1yX3YxoUE4bcT5fDBg24 H7U3AqjQAjF6w3EtqYjpVPDKcxeXDWaQVoW3bcHr5bWRpOTBVOWgxdt5mCdMxFAVMJ8s 3kViuKqK2O0CA6JXbag+pRHgkqEX60uIyrPx7jA82gOWhg6pcf9rnel8NJL3aF2Ywykk b18Q==
X-Gm-Message-State: APjAAAVfHnNFiv5nyEHT26TifMK+5mowqQ1XkyGyEBEV+2vWocq2Ozsu 8erLiMg4GEVdZ8M0cjXECHmZnoIfyAoIG9t7gshgrw==
X-Google-Smtp-Source: APXvYqy1E+/lU6Yj8sRuwAYirfxUh3s9gAiTrRSoG87fQhP6OWTyEFNOr1ec3/H4ZNQFypwrmcAiKVvmOKTwcKjxGoA=
X-Received: by 2002:ac2:53bb:: with SMTP id j27mr2421135lfh.39.1579186676639; Thu, 16 Jan 2020 06:57:56 -0800 (PST)
MIME-Version: 1.0
References: <157658758575.26391.17025511136538671205@ietfa.amsl.com> <e0a3830345ac21ac900555090f450ebcaeedf0f6.camel@nic.cz> <alpine.LRH.2.21.1912171052570.9646@bofh.nohats.ca> <0f388b564d16fb913b04629002a2880fc51637fe.camel@nic.cz> <65BE6342-880A-4A38-8A99-9FE469A6292C@gmx.net>
In-Reply-To: <65BE6342-880A-4A38-8A99-9FE469A6292C@gmx.net>
From: Bob Harold <rharolde@umich.edu>
Date: Thu, 16 Jan 2020 09:57:45 -0500
Message-ID: <CA+nkc8AbM88Qhxr_NqzEsKkWHTtgQirNxOv9_6rd8j6BSi428w@mail.gmail.com>
To: Normen Kowalewski <nbkowalewski@gmx.net>
Cc: Ladislav Lhotka <lhotka@nic.cz>, Paul Wouters <paul@nohats.ca>, dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e5c3e6059c430c91"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/-xjWqa1-D8HeQPTDyCQjH2FEQJw>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-iana-class-type-yang-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: Thu, 16 Jan 2020 14:58:04 -0000

On Thu, Jan 16, 2020 at 4:32 AM Normen Kowalewski <nbkowalewski@gmx.net>
wrote:

> Paul, Lada,
>
>
> On the comment for the wording in the line after the example in  3
> <https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-iana-class-type-yang-00#section-3>.
> YANG Design Considerations
>
>      typedef dns-class-name {
>        type enumeration {
>          enum IN {
>            value 1;
>            description
>              "Internet (IN)";
>            reference
>              "RFC 1035 <https://datatracker.ietf.org/doc/html/rfc1035>";
>          }
>          ...
>        }
>      }
>
>    The other type, "rr-type-name", is exactly analogical.
>
>
> Maybe we could use the wording
>
>    The definitions for the other basic type, "rr-type-name” are derived in analogy to this structure, except that the IANA registry "Resource Record (RR) TYPEs” is the respective underlying data source.
>
>
> BR, Normen
>
>
> The other type, "rr-type-name", is exactly analogical.
>
> I'm not sure if "analogical" is a common word to use and might be a bit
> confusing to non-native speakers like me. I'm also confused about
> "exactly analogical". What would inexactly analogical be? :)
>
>
> Being another non-native speaker, I am open to suggestions
>
>
>
"analogous" is a more common form of the word, and could be used.  Or a
synonym like "parallel" or "similarly".

-- 
Bob Harold