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

Carsten Bormann <cabo@tzi.org> Tue, 11 September 2018 22:12 UTC

Return-Path: <cabo@tzi.org>
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 2C4B4130F39; Tue, 11 Sep 2018 15:12:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 4RNWolKzaKZw; Tue, 11 Sep 2018 15:12:35 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 03FAA130F1F; Tue, 11 Sep 2018 15:12:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id w8BMCWud020122; Wed, 12 Sep 2018 00:12:32 +0200 (CEST)
Received: from [192.168.217.102] (p54A6C24D.dip0.t-ipconnect.de [84.166.194.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 428zg36ln6zDXZc; Wed, 12 Sep 2018 00:12:31 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <17342.1536697549@localhost>
Date: Wed, 12 Sep 2018 00:12:30 +0200
Cc: anima@ietf.org
X-Mao-Original-Outgoing-Id: 558396748.855919-352811b253da707d51afed5bfaf58864
Content-Transfer-Encoding: quoted-printable
Message-Id: <622CDA79-7BE4-4A71-BFF7-0C80F63A1556@tzi.org>
References: <17342.1536697549@localhost>
To: Core <core@ietf.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/NWlb1jtLORHloS7AJPaC3mozd50>
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: Tue, 11 Sep 2018 22:12:37 -0000

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.

Grüße, Carsten