Re: [Anima] ANIMA-WG: pls chime in: early allocation for otherName code points (draft-ietf-anima-autonomic-control-plane)

"Fries, Steffen" <steffen.fries@siemens.com> Fri, 03 July 2020 08:53 UTC

Return-Path: <steffen.fries@siemens.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90AD13A0ADC; Fri, 3 Jul 2020 01:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 ZaD4jVsxgSH9; Fri, 3 Jul 2020 01:53:14 -0700 (PDT)
Received: from gw-eagle1.siemens.com (gw-eagle1.siemens.com [194.138.20.72]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24A8F3A0AD8; Fri, 3 Jul 2020 01:53:14 -0700 (PDT)
Received: from mail1.dc4ca.siemens.de (mail1.dc4ca.siemens.de [139.25.224.78]) by gw-eagle1.siemens.com (Postfix) with ESMTPS id 536B64F0053; Fri, 3 Jul 2020 10:53:12 +0200 (CEST)
Received: from DEMCHDC89ZA.ad011.siemens.net (demchdc89za.ad011.siemens.net [139.25.226.105]) by mail1.dc4ca.siemens.de (Postfix) with ESMTPS id 011A0157C2F3A; Fri, 3 Jul 2020 10:53:10 +0200 (CEST)
Received: from DEMCHDC8A1A.ad011.siemens.net (139.25.226.107) by DEMCHDC89ZA.ad011.siemens.net (139.25.226.105) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Fri, 3 Jul 2020 10:53:10 +0200
Received: from DEMCHDC8A1A.ad011.siemens.net ([139.25.226.107]) by DEMCHDC8A1A.ad011.siemens.net ([139.25.226.107]) with mapi id 15.01.1979.003; Fri, 3 Jul 2020 10:53:10 +0200
From: "Fries, Steffen" <steffen.fries@siemens.com>
To: Toerless Eckert <tte@cs.fau.de>, "anima@ietf.org" <anima@ietf.org>
CC: "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "Rob Wilton (rwilton)" <rwilton@cisco.com>, "housley@vigilsec.com" <housley@vigilsec.com>
Thread-Topic: [Anima] ANIMA-WG: pls chime in: early allocation for otherName code points (draft-ietf-anima-autonomic-control-plane)
Thread-Index: AQHWUHTLWqNXoLGQ9kirevsjZmJYvqj1i/2g
Date: Fri, 3 Jul 2020 08:53:10 +0000
Message-ID: <c77c9966be17425bb12813a4fe7527c6@siemens.com>
References: <20200702132922.GA11404@faui48f.informatik.uni-erlangen.de>
In-Reply-To: <20200702132922.GA11404@faui48f.informatik.uni-erlangen.de>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [144.145.220.66]
x-tm-snts-smtp: 622BE8CDDD860C5B4BDEA66DE7DDE97E698F7E96F9C2D89045652DD09AA37AC92000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/OOTa5x1PPP5PUO5pGT-ztlGoPIU>
Subject: Re: [Anima] ANIMA-WG: pls chime in: early allocation for otherName code points (draft-ietf-anima-autonomic-control-plane)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jul 2020 08:53:16 -0000

+1 

I consider going with otherNames for the ACP domain the safe way. Taking interactions with existing infrastructures into account may lead to potential misinterpretations of using other fields as the discussion has shown. Having a distinct allocation is more clear. 

Best regards
Steffen

> -----Original Message-----
> From: Anima <anima-bounces@ietf.org> On Behalf Of Toerless Eckert
> Sent: Donnerstag, 2. Juli 2020 15:29
> To: anima@ietf.org
> Cc: anima-chairs@ietf.org; Rob Wilton (rwilton) <rwilton@cisco.com>om>;
> housley@vigilsec.com
> Subject: [Anima] ANIMA-WG: pls chime in: early allocation for otherName
> code points (draft-ietf-anima-autonomic-control-plane)
> 
> Dear WG (ACP author head/hat on)
> 
> ACP Revision -26 introduced a new otherName / AcpNodeName encoding
> for the ACP Domain Information (now call AcpNodeName / acp-node-name).
> Michael Richardson (and potentially other) implementors would like to
> update implementation to use this new encoding for interop testing, which
> requires allocation of two IANA code points (technically i think only one is
> required for the implementation, but the toolchain would require both if i
> understand it correctly).
> 
> The early allocation process RFC7120 requires to vet the community for
> interest in the early allocation, so pls. chime in with a +1, or if you must a -1
> and explanation.
> 
> I'll do a +1 from the authors side.
> 
> The remaining requirements of RFC7120 for early allocations are AFAIK met.
> 
> Thanks!
>     Toerless
> 
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima