IETF Logo Mail Archive

Re: [DNSOP] A conversational description of sentinel.

joel jaeggli <joelja@bogus.com> Tue, 06 February 2018 16:22 UTC

Return-Path: <joelja@bogus.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 23A9412E878 for <dnsop@ietfa.amsl.com>; Tue, 6 Feb 2018 08:22:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01, 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 9Rs3yenWoFJ1 for <dnsop@ietfa.amsl.com>; Tue, 6 Feb 2018 08:22:00 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 662C612E873 for <dnsop@ietf.org>; Tue, 6 Feb 2018 08:22:00 -0800 (PST)
Received: from MBP.local ([IPv6:2620:11a:c081:20:bd85:ba9e:7eba:e9b5]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id w16GLxdE051902 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Tue, 6 Feb 2018 16:21:59 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2620:11a:c081:20:bd85:ba9e:7eba:e9b5] claimed to be MBP.local
To: Paul Hoffman <paul.hoffman@vpnc.org>, Petr Špaček <petr.spacek@nic.cz>
Cc: dnsop@ietf.org
References: <CAHw9_iKnD4WtTKyof=nm4ChmDZ5mAPqA7a_-m1t_Lauugf4Uow@mail.gmail.com> <D5D013D4-1EAD-434B-863A-29CB1BBEF4E4@vpnc.org> <496EFA88-BA70-460B-BFB2-69B2C7BC905D@apnic.net> <4540A279-4A37-4245-AE61-BEE5342E3F72@vpnc.org> <20180202075530.Horde.UWaxe9eenZ7PyxWYFHCFGdN@andreasschulze.de> <e8ac7bd0-26e6-cf97-e2ef-0ead50dc18ce@nic.cz> <88E7D27C-048E-44CB-B317-C892EA603D31@isc.org> <0c2a4a38-49d7-2b46-1ac8-1dda0812e217@nic.cz> <CAHw9_iJ6yL12OaGW5+fm8M3YUkrj46CvC2-ob7Xrc5HEaA_Z1Q@mail.gmail.com> <f9861a96-a930-bd08-7cf5-5c6b003f706e@nic.cz> <24C74B01-FC08-41CD-BB16-FD122F9EB61A@apnic.net> <alpine.DEB.2.11.1802051246230.30577@grey.csi.cam.ac.uk> <FDFE42D8-B805-4336-A9A5-B81F416B3251@apnic.net> <D07FE583-06F7-436D-97EF-4747B815AD3F@vpnc.org> <20180206094215.Horde.m4xt1lsOwvQ28hAbN1r_Tg4@andreasschulze.de> <alpine.DEB.2.11.1802061221510.30577@grey.csi.cam.ac.uk> <2ffeba22-5cf1-4eb0-b45c-fefb7cf1d8f7@nic.cz> <CBB24E6D-D20D-42CC-95D3-82A37C26BC31@vpnc.org>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <56a96979-0198-9903-684e-5b64247aa164@bogus.com>
Date: Tue, 06 Feb 2018 08:21:54 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CBB24E6D-D20D-42CC-95D3-82A37C26BC31@vpnc.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/tKGGBCfhTbFwMbnUr5Got_cA8tE>
Subject: Re: [DNSOP] A conversational description of sentinel.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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, 06 Feb 2018 16:22:02 -0000


On 2/6/18 8:13 AM, Paul Hoffman wrote:
> On 6 Feb 2018, at 8:04, Petr Špaček wrote:
>
>> On 6.2.2018 13:22, Tony Finch wrote:
>>> A. Schulze <sca@andreasschulze.de> wrote:
>>>>
>>>> Yes, "kskroll-sentinel-is-ta-NNNN" is more descriptive and specific.
>>>> I also prefer that longer variant.
>>>
>>> Yes, more friendly for web searches if someone is wondering about weird
>>> queries.
>>
>> Bonus points if we can get a number reserved by RFC editor, it would
>> allow us to use name like
>> test-rfc0000-is-ta-NNNN
>> test-rfc0000-not-ta-NNNN
>>
>> That would be super awesome.
>
> ...and super-unlikely, given the history of the RFC Series.
>
>> Is something like RFC number pre-allocation possible?
Not really, nor is specifying them. Allocation is the domain of the RFC
editor and occurs once they enter the editor queue. until then they're
just internet drafts.
 
Naming something properly can with specific instructions be done at the
time of editing. as for example is done with IANA instructions,
references and so on... That's pretty much the opposite of early allocation.
> Sometimes (rarely), after Working Group Last Call. That's why I
> suggested "kskroll-sentinel" since those words are in the WG draft
> name, and will probably appear in the IETF Datatracker forever.
>
> --Paul Hoffman
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

v2.23.0 | Report a Bug | By Email