[dtn] Interoperability context and/or COSE
Rick Taylor <rick@tropicalstormsoftware.com> Mon, 27 July 2020 13:09 UTC
Return-Path: <rick@tropicalstormsoftware.com>
X-Original-To: dtn@ietfa.amsl.com
Delivered-To: dtn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27C633A1970 for <dtn@ietfa.amsl.com>; Mon, 27 Jul 2020 06:09:00 -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, SPF_HELO_NONE=0.001, SPF_PASS=-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 Pj47XbRBgFJD for <dtn@ietfa.amsl.com>; Mon, 27 Jul 2020 06:08:57 -0700 (PDT)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29C2B3A0E09 for <dtn@ietf.org>; Mon, 27 Jul 2020 06:08:57 -0700 (PDT)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::48e4:acbb:6065:8168]) by tss-server1.home.tropicalstormsoftware.com ([fe80::48e4:acbb:6065:8168%16]) with mapi id 14.03.0487.000; Mon, 27 Jul 2020 14:08:55 +0100
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: "dtn@ietf.org" <dtn@ietf.org>
Thread-Topic: Interoperability context and/or COSE
Thread-Index: AdZkEeMZqu6vOtMCSnKosmLr2UJpeA==
Date: Mon, 27 Jul 2020 13:08:54 +0000
Message-ID: <38A5475DE83986499AEACD2CFAFC3F9801F585E9FA@tss-server1.home.tropicalstormsoftware.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2a02:1648:4000:120:7d32:c34a:6930:e9fd]
Content-Type: multipart/alternative; boundary="_000_38A5475DE83986499AEACD2CFAFC3F9801F585E9FAtssserver1hom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/et5kYgp8J-_PX400nXn2zPR3wW4>
Subject: [dtn] Interoperability context and/or COSE
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <dtn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtn>, <mailto:dtn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn/>
List-Post: <mailto:dtn@ietf.org>
List-Help: <mailto:dtn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtn>, <mailto:dtn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2020 13:09:00 -0000
Hi All, At IETF-108 a question was raised as whether the existing BPSec interoperability security context should be useable in environments beyond interoperability-testing. A second question was raised: whether the COSE security context would actually make a good replacement for the BPSec interoperability security context draft. The chairs are interested in discovering WG consensus on the following topics: 1. Should BPsec-interop be updated to be 'production grade'? 2. Should the COSE security context be adopted as a WG document? 3. Should the COSE security context replace the BPSec-interop document? Cheers, Rick & Marc
- [dtn] Interoperability context and/or COSE Rick Taylor
- Re: [dtn] Interoperability context and/or COSE Mehmet Adalier
- Re: [dtn] Interoperability context and/or COSE Birrane, Edward J.
- Re: [dtn] Interoperability context and/or COSE Brian Sipos