Re: [core] [Anima] documenting SID usage in IETF specification

Peter van der Stok <stokcons@bbhmail.nl> Wed, 12 September 2018 15:15 UTC

Return-Path: <stokcons@bbhmail.nl>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C104130E1E; Wed, 12 Sep 2018 08:15:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] 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 wz1EkYKutbW8; Wed, 12 Sep 2018 08:15:27 -0700 (PDT)
Received: from smtprelay.hostedemail.com (smtprelay0249.hostedemail.com [216.40.44.249]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83C89130E43; Wed, 12 Sep 2018 08:15:27 -0700 (PDT)
Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay03.hostedemail.com (Postfix) with ESMTP id 6BB8183777EE; Wed, 12 Sep 2018 15:15:26 +0000 (UTC)
X-Session-Marker: 73746F6B636F6E73406262686D61696C2E6E6C
X-Spam-Summary: 2, -10, 0, , d41d8cd98f00b204, stokcons@bbhmail.nl, :::::::, RULES_HIT:41:72:152:355:379:582:599:800:960:962:967:973:983:988:989:1152:1189:1208:1212:1221:1260:1313:1314:1345:1431:1436:1437:1516:1517:1518:1535:1543:1575:1588:1589:1592:1594:1711:1730:1776:1792:2068:2069:2198:2199:2525:2528:2553:2557:2559:2567:2570:2682:2685:2693:2703:2741:2827:2859:2933:2937:2939:2942:2945:2947:2951:2954:3022:3148:3354:3622:3642:3743:3769:3865:3866:3867:3868:3870:3871:3873:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4118:4250:4321:4860:5007:6117:6119:6261:7875:7903:8603:9010:9025:9177:10004:10346:10400:11658:12379:12740:13139:13161:13229:13237, 0, RBL:error, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:fn, MSBL:0, DNSBL:neutral, Custom_rules:0:0:0, LFtime:34, LUA_SUMMARY:none
X-HE-Tag: teeth68_2f751d4fa7043
X-Filterd-Recvd-Size: 7728
Received: from mail.bbhmail.nl (imap-ext [216.40.42.5]) (Authenticated sender: webmail@stokcons@bbhmail.nl) by omf10.hostedemail.com (Postfix) with ESMTPA; Wed, 12 Sep 2018 15:15:26 +0000 (UTC)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_9802736c5b204041a9a69ea98371528f"
Date: Wed, 12 Sep 2018 17:15:25 +0200
From: Peter van der Stok <stokcons@bbhmail.nl>
To: Andy Bierman <andy@yumaworks.com>
Cc: Carsten Bormann <cabo@tzi.org>, anima@ietf.org, Core <core@ietf.org>
Organization: vanderstok consultancy
Reply-To: consultancy@vanderstok.org
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <CABCOCHTrjYZmK4e+L7pj=V=sWxg97jw2AFGen2PFe7ceBrB7bg@mail.gmail.com>
References: <17342.1536697549@localhost> <622CDA79-7BE4-4A71-BFF7-0C80F63A1556@tzi.org> <CABCOCHTrjYZmK4e+L7pj=V=sWxg97jw2AFGen2PFe7ceBrB7bg@mail.gmail.com>
Message-ID: <50f58c78b6825ce1cdbc33ea852c3145@bbhmail.nl>
X-Sender: stokcons@bbhmail.nl
User-Agent: Roundcube Webmail/1.2.7
X-Originating-IP: [90.0.216.32]
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/_qnwYb75F1O_nuCR9f_9dfMBJFM>
Subject: Re: [core] [Anima] documenting SID usage in IETF specification
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Sep 2018 15:15:30 -0000

Hi all,

The numbering of the SIDs in our case should be as stable as possible
after publication as RFC.
A permanent assignment of the numbers, like the content-format numbers,
would be very much appreciated.
Using the same already allocated numbers for other RFCs would be quite
disastrous.

Maintenance of (part of) the comi.space by a organisation like IANA
could be a possibility.

Peter
Andy Bierman schreef op 2018-09-12 01:32:

> On Tue, Sep 11, 2018 at 3:12 PM, Carsten Bormann <cabo@tzi.org> wrote:
> 
>> On Sep 11, 2018, at 22:25, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
>>> 
>>> SHOULD ietf-core-sid say something about this?
>> 
>> Yes, we should have a common way of handling SID allocations in RFCs.
>> 
>> draft-ietf-core-sid sounds like a natural way to place this, but what goes into what document is often a question of who has time to write something at a particular point in time.  So let's discuss this with the authors.
>> 
>> In any case, this probably should stay at the level of a suggestion more than prescribing a normative way of doing things -- the conventions we use for this may evolve faster than the rest of the technical content of draft-ietf-core-sid.
> 
> You probably want to make a clear distinction between Internet Drafts with volatile SID assignments 
> and RFCs with permanent SID assignments. 
> 
> Do you want early implementation (of modules using SID)  to be as painful as possible or as seamless as possible? 
> Renumbering SID assignments may be extremely disruptive to actual deployments. 
> Correctness of a SID file within a source document is not the same thing as correctness of all SID files 
> across an entire administrative domain. 
> 
> I agree the administration of SID assignments is out of scope for CORE WG but punting 
> the problem to vendors or operators will not be good enough. 
> 
>> Grüße, Carsten
> 
> Andy 
> 
>> _______________________________________________
>> core mailing list
>> core@ietf.org
>> https://www.ietf.org/mailman/listinfo/core [1]
> 
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima
 

Links:
------
[1] https://www.ietf.org/mailman/listinfo/core