Re: [netmod] [Anima] revising RFC8366 -- Re: BRSKI-AE enum issue -> empty, but what's he encoding ?

"Fries, Steffen" <steffen.fries@siemens.com> Wed, 30 June 2021 12:38 UTC

Return-Path: <steffen.fries@siemens.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12C973A1B12; Wed, 30 Jun 2021 05:38:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.898
X-Spam-Level:
X-Spam-Status: No, score=-6.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 6DXXMWn9Ry_Q; Wed, 30 Jun 2021 05:38:31 -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 AB0413A1B10; Wed, 30 Jun 2021 05:38:31 -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 669264F032D; Wed, 30 Jun 2021 14:38:23 +0200 (CEST)
Received: from DEMCHDC8A2A.ad011.siemens.net (demchdc8a2a.ad011.siemens.net [139.25.226.108]) by mail1.dc4ca.siemens.de (Postfix) with ESMTPS id 74BEA1A4AF14F; Wed, 30 Jun 2021 14:38:21 +0200 (CEST)
Received: from DEMCHDC89XA.ad011.siemens.net (139.25.226.103) by DEMCHDC8A2A.ad011.siemens.net (139.25.226.108) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.14; Wed, 30 Jun 2021 14:38:20 +0200
Received: from DEMCHDC89XA.ad011.siemens.net ([139.25.226.103]) by DEMCHDC89XA.ad011.siemens.net ([139.25.226.103]) with mapi id 15.01.2176.014; Wed, 30 Jun 2021 14:38:20 +0200
From: "Fries, Steffen" <steffen.fries@siemens.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "Rob Wilton (rwilton)" <rwilton@cisco.com>, "anima@ietf.org" <anima@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
CC: Toerless Eckert <tte@cs.fau.de>, Kent Watsen <kent+ietf@watsen.net>
Thread-Topic: [Anima] revising RFC8366 -- Re: BRSKI-AE enum issue -> empty, but what's he encoding ?
Thread-Index: AQHXbUgLTh6qzCTiOUi87TrW2ebB4KssfkVA
Date: Wed, 30 Jun 2021 12:38:20 +0000
Message-ID: <b36e56b3970c4908af0d1cb00d08504c@siemens.com>
References: <20210625190512.GB30200@faui48e.informatik.uni-erlangen.de> <5025.1624653668@localhost> <DM4PR11MB5438EE27158CDEAF63F89C97B5039@DM4PR11MB5438.namprd11.prod.outlook.com> <27560.1625013411@localhost>
In-Reply-To: <27560.1625013411@localhost>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Enabled=true; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SetDate=2021-06-30T12:38:19Z; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Method=Standard; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Name=restricted-default; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SiteId=38ae3bcd-9579-4fd4-adda-b42e1495d55a; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ActionId=96855855-ca3d-4f28-901b-68576cfadb6f; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ContentBits=0
document_confidentiality: Restricted
x-originating-ip: [144.145.220.66]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/OdEu9L4Y4GoYlhv5M3o7XonoxWk>
Subject: Re: [netmod] [Anima] revising RFC8366 -- Re: BRSKI-AE enum issue -> empty, but what's he encoding ?
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jun 2021 12:38:36 -0000

Hi Michael, 

> -----Original Message-----
> From: Michael Richardson <mcr+ietf@sandelman.ca>
> Sent: Mittwoch, 30. Juni 2021 02:37


> I thought I wrote a really nice ASCII art version of what documents inherit from
> RFC8366.  I can't find it in my outbox... I wonder if I nuked the draft by mistake.
> 
> The short of it:
> RFC8366 -> RFC8995 (voucher-request)
>         -> constrained-voucher (voucher-request, voucher)
>         -> brski-async-enroll (voucher-request)
Would it make sense to also state the voucher for BRSKI-AE as it also uses the voucher and tries to argue for a new assertion type (agent-proximity)?

>         -> jose-voucher (voucher, voucher-request)

Regards
Steffen



> 
> and my question was a bit about how we manage all their things inherited.
> It's really the classic CS multiple inheritance problem.
> 
> {A Cat is an Mammal
>  A Cat is an Four-legged creature
>  A Cat is Nocturnal.}