IETF Logo Mail Archive

Re: [DNSOP] Call for Adoptions: draft-lhotka-dnsop-iana-class-type-yang

Joe Abley <jabley@hopcount.ca> Fri, 11 October 2019 14:03 UTC

Return-Path: <jabley@hopcount.ca>
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 BC94F120090 for <dnsop@ietfa.amsl.com>; Fri, 11 Oct 2019 07:03:28 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 yHo_zmEMpywe for <dnsop@ietfa.amsl.com>; Fri, 11 Oct 2019 07:03:27 -0700 (PDT)
Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (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 1BCC0120073 for <dnsop@ietf.org>; Fri, 11 Oct 2019 07:03:27 -0700 (PDT)
Received: by mail-io1-xd31.google.com with SMTP id a1so21747323ioc.6 for <dnsop@ietf.org>; Fri, 11 Oct 2019 07:03:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0mT6cEZSL3bvlymQxPGQT4hTU/bOeUYQhTlxqg0c6DY=; b=cNfdqKZpjiN5DH8VnF6lfrpBdYH+xl63ZQXXirgvOlALzJ4NxDrPd8ikTGeipQEGzV ecJwVeAZBMrt4TBWEOEa2N2JnGwxVHEwPmwLoypEKM4zbRNYZ5GAncOdhlkww8GIpa2w Vcqa6PUkn2XPgcgggxAHn9urdC8zBi+dfXTPs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0mT6cEZSL3bvlymQxPGQT4hTU/bOeUYQhTlxqg0c6DY=; b=cSb04TRlSjCatPBHYkSnWo1e/sY8m38/VSoY+bjjqVW+Bmu9phUBTDt1YI7XheJrXM SFOTotdURcdkYzZLMoaKy+4swGMlldbvZmN8k7yREBR5Jds3r2jvuAP+aiEzGWXVdoJi PVtJh46XWwybR++k8gLd3N/f+uo4/OzoCqwG6b3yHkLn+TUkO5hSdi8A+hkT4K9pGYmp yBTzjKQDZg2a172lx4C+Ge2B1gdxXX/1tQdgqDG7GYIdMsYmdUg1Wp2/PCWN+P9biBhh ohGb4+P5nR3kI5657uLkc0SFOy+xbq36qZWlg/HOLG5LAUGvukF6aSRIE25Vm6rU3PVv nu3Q==
X-Gm-Message-State: APjAAAVy2K3Netpm0J9n4tFplkTfB7YxP/kf6UqbKYRMkY7sZ761i6tC 9+Q7vNUKwTv8gfD1WxcasHKa44CIYvGKbeV+
X-Google-Smtp-Source: APXvYqyMhpUOA+WFbt4NZ/fX/p6XjduBrzWRJCYWHQkt+s0A5ILrmSl8I6v962ECQYgvGQPJ/1szBg==
X-Received: by 2002:a5e:cb0a:: with SMTP id p10mr17236171iom.148.1570802606283; Fri, 11 Oct 2019 07:03:26 -0700 (PDT)
Received: from ?IPv6:2607:f2c0:e786:128f:a550:f3e:535c:f2d5? ([2607:f2c0:e786:128f:a550:f3e:535c:f2d5]) by smtp.gmail.com with ESMTPSA id f12sm5826139iob.58.2019.10.11.07.03.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 11 Oct 2019 07:03:25 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3594.4.19\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <alpine.LRH.2.21.1910100951010.10011@bofh.nohats.ca>
Date: Fri, 11 Oct 2019 10:03:23 -0400
Cc: Ladislav Lhotka <lhotka@nic.cz>, DNSOP WG <dnsop@ietf.org>, iesg@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <1FE6DB94-C839-4087-9838-0F7A2EF42B2A@hopcount.ca>
References: <820fe3a1-9d54-15c1-8194-8a607bdf6a31@NLnetLabs.nl> <87sgqy2azd.fsf@nic.cz> <920E9418-4440-46F6-87B7-68CF8B03C408@gmx.net> <C66220A931BC4753B6818DAF898AE2E8@T1650> <426d8bf2-cf28-11f6-4435-08fcaa37e7f5@NLnetLabs.nl> <alpine.LRH.2.21.1910071329420.19930@bofh.nohats.ca> <0A5478B0-BC32-46AA-A915-ABC026D247CA@gmx.net> <CA+nkc8BjHrCF7PO_0RKETcLWhNDDA2M66antFE=xusHcdsVHhA@mail.gmail.com> <93dba67e7c86fe1679f9ca534740c93e7af1eabf.camel@nic.cz> <alpine.LRH.2.21.1910091628450.11081@bofh.nohats.ca> <874l0hrr9c.fsf@nic.cz> <alpine.LRH.2.21.1910100951010.10011@bofh.nohats.ca>
To: Paul Wouters <paul@nohats.ca>
X-Mailer: Apple Mail (2.3594.4.19)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/s-2ZuL_O4XKknMOaAfiL-KLX0Kk>
Subject: Re: [DNSOP] Call for Adoptions: draft-lhotka-dnsop-iana-class-type-yang
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: Fri, 11 Oct 2019 14:03:29 -0000

On 10 Oct 2019, at 09:55, Paul Wouters <paul@nohats.ca> wrote:

> On Thu, 10 Oct 2019, Ladislav Lhotka wrote:
> 
>> They should not actually be reading the RFC but get the latest revision of the module from this page:
>> 
>> https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml
> 
> You are asking for text to go into an RFC, which you then say they
> (implementors) should not read. Clearly then the text should not go
> into the RFC.

I'm not sure I fully understand the concern, here.

When a document instructs the IANA to create a registry, those instructions contain the initial rows that should seed the registry along with directions about how the registry is to be maintained following creation. Is this document fundamentally different from that?

Has anybody actually asked PTI what they think the best way of doing this would be?


Joe

v2.23.0 | Report a Bug | By Email