Re: [dtn] Convergence Layer Adapter - Endpoint IDs (CLA-EID)
Brian Sipos <BSipos@rkf-eng.com> Fri, 06 December 2019 13:43 UTC
Return-Path: <BSipos@rkf-eng.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 C1C74120814 for <dtn@ietfa.amsl.com>; Fri, 6 Dec 2019 05:43:03 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=rkfeng.onmicrosoft.com
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 71K3w8dJ4sBr for <dtn@ietfa.amsl.com>; Fri, 6 Dec 2019 05:43:01 -0800 (PST)
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (mail-eopbgr680043.outbound.protection.outlook.com [40.107.68.43]) (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 34818120804 for <dtn@ietf.org>; Fri, 6 Dec 2019 05:43:01 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Dvelh4R/CQKiFfOjL5Pwsb8a7OnaZSOy0GFE+t+R00Q99DnezLP8cKGDjyXcb2gWG1/SZRaRKDAZ2S7vPBGuXU5baPGG6bqxnpfMFORXXO5uhbCUgFX8fxefTqAHGkMq/29NlMRP3CIl6XYR/SMDA4BizBD0Yh+hDxuuwJtvKjiSMwVhd0ijsm2KM+RTBYbOrtPpjeHIqvpTqtBTxzTdbBcaXlPEKgvrRq0mQ5U6Cj1fGi3GtrfB9P6e4D9DHFTFLUwn8NB1qIrU0o8BcAGejOom6u1gE3ZbnrEx0n40W03rPKqZOBQHZMeuiIdeKKclJDwNqVUx/9zXlXpWosGpug==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=cKnfqg6liGwrEapUHkFocmCAvfcc/1FnZtLEe8NKfqk=; b=e4pMBwaVDtTu9QBZtQtH8Rg4VAGabPnBVQIn90Jo4wVSQirWZwqAozdqynQDibDG0+uHDQTiHrZP3Q70L2H5UWnoaIWBcKkchZ7S36vN6Hdi/hrq7waXHrlncwPeK/Iy+4RcaOhy7g9fNANx76ipVESl98H5qGrm4Q22iu9oSr07yx9mavHJO43cxzesyS40uHNpWg04MihxZhmTzGoJIpqtteR1DlWpUWxYjmJWFfkGT8EdK15+SWu/4bFyM23kKYJPGv4JDGbhzJmbNex8OssF+e+DFif6j/NZ17OF8CbRiy8SsMRR6MyJS6GeIkF/+hOFwwKKQxEXAb/8EAJ2Pw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=rkf-eng.com; dmarc=pass action=none header.from=rkf-eng.com; dkim=pass header.d=rkf-eng.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rkfeng.onmicrosoft.com; s=selector2-rkfeng-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=cKnfqg6liGwrEapUHkFocmCAvfcc/1FnZtLEe8NKfqk=; b=LGkskMTAxaaYw0izv82xx3NkRwooNLSuhUUAADKde65HX5Ic60HedFBDDj30M8ybvyY8pUWqWsbx8n0jeHW+T51Mu34uCygCNLmSQdnqVu+EXZxPVEnZ0t1f5SAi6MACGhUA19gYtWv0zYmD+/9tCBl/8TVg5aEYrXONL9DoykQ=
Received: from MN2PR13MB3520.namprd13.prod.outlook.com (10.255.238.221) by MN2PR13MB3552.namprd13.prod.outlook.com (10.255.239.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2538.4; Fri, 6 Dec 2019 13:42:52 +0000
Received: from MN2PR13MB3520.namprd13.prod.outlook.com ([fe80::5048:62dd:60d9:94b9]) by MN2PR13MB3520.namprd13.prod.outlook.com ([fe80::5048:62dd:60d9:94b9%7]) with mapi id 15.20.2538.005; Fri, 6 Dec 2019 13:42:52 +0000
From: Brian Sipos <BSipos@rkf-eng.com>
To: Loiseau lucien <loiseau.lucien@gmail.com>, "dtn@ietf.org" <dtn@ietf.org>
Thread-Topic: [dtn] Convergence Layer Adapter - Endpoint IDs (CLA-EID)
Thread-Index: AQHVqO7NEXBX/7bO8E2F/196E5IzQKenBgkb
Date: Fri, 06 Dec 2019 13:42:52 +0000
Message-ID: <MN2PR13MB3520794027C9E2B33D8CB0A49F430@MN2PR13MB3520.namprd13.prod.outlook.com>
References: <CANoKrvY2RMm447-OXzKWr5ngVFwpgXw-LbH0PU6LiYDxQUdYDA@mail.gmail.com>
In-Reply-To: <CANoKrvY2RMm447-OXzKWr5ngVFwpgXw-LbH0PU6LiYDxQUdYDA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=BSipos@rkf-eng.com;
x-originating-ip: [173.8.22.181]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3337424d-e64a-4389-23fa-08d77a52313f
x-ms-traffictypediagnostic: MN2PR13MB3552:
x-microsoft-antispam-prvs: <MN2PR13MB35526D5CA15674266C762B139F5F0@MN2PR13MB3552.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0243E5FD68
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(39830400003)(376002)(136003)(346002)(366004)(199004)(189003)(53754006)(52536014)(74316002)(6506007)(81166006)(66446008)(5660300002)(53546011)(86362001)(102836004)(66476007)(186003)(966005)(64756008)(2906002)(316002)(7696005)(26005)(508600001)(54896002)(9686003)(8676002)(66556008)(110136005)(81156014)(80792005)(15974865002)(76176011)(99286004)(55016002)(66946007)(71190400001)(76116006)(19627405001)(71200400001)(33656002)(8936002)(229853002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR13MB3552; H:MN2PR13MB3520.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: rkf-eng.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: SvmZ1lSvimMIH2SsxYZEn1V3WVOHziQH+B07Q1VIv2Pl7Z7dyexPED/4WIv3ev33KNwFle4l4XkLTYvvSa+dHJTXaZ/OjwEZMPQSAKSQ3vwFXQLSlmvP3AguTCHOQfLKOCFR+S2Y2daJN/SMbO4+Rg6lk/mINCw1ir0mFI/RE/6WJsU28SUmRZF5M3j47N5imHgCcSa9yNoWPBKRyfPZ7sb247XrpNxY9hBN2ENEVYfQoMKqa5YxrkQh47BSTTwkxPBXds/GHbAIU4Rvqd5urzzcvcxYAAuK6TvKv+JWg5VIWTB35RWO5Ep7Y/evGuAxLMbtvpVY5tjGNc+fPc9HnSUvc5ZCtHHpsTFzB3TwuMdPI0AZg+cn6zwUq3K976LJw+LXdoq6lUhuVs4T+/Rpxeu4WIdwUPpMAWZkAEEeIpNXiaCPUrPT06fQ8c83BIWIlsEgMbFEWl00QZVPf4EkxsZQCOu0eUJKH6SXTo6do2LbN+22oK6bUGcLI7AdHzFLjdARG+j9oDXU8t0hq6T9ajaUkKQqDQCW+q0mwAz+0e8=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR13MB3520794027C9E2B33D8CB0A49F430MN2PR13MB3520namp_"
MIME-Version: 1.0
X-OriginatorOrg: rkf-eng.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 3337424d-e64a-4389-23fa-08d77a52313f
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Dec 2019 13:42:52.7163 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4ed8b15b-911f-42bc-8524-d89148858535
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: mf8FEZz/DKDpDxApIK7ZnD3ZKr2RWVIsxga+j1YQVgadaZh3GeEDbcBxaBKeWHxXtOIvYe8f73zCPshv2N92Ng==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR13MB3552
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/Bzio9SoBkgzqQySx-1UnxMkPhx0>
Subject: Re: [dtn] Convergence Layer Adapter - Endpoint IDs (CLA-EID)
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: Fri, 06 Dec 2019 13:43:04 -0000
Lucien, I do see value in registration of CLA identifiers. One of the deficiencies I see with the IPND draft is that its notion of what is a CLA service [1] is quite ambiguous. It implies that "TCP" means "DTN TCPCL" and isn't exactly clear about what protocol version is used (all of the CLAs are cited from that draft as Informative References). It's a good notional start but I would love to take a crack at tightening up, modernizing, and security-enhancing the IPND protocol. A question to the WG related to CLA identifiers is: do we want the CLA registry to be maintained as text (similar to the URN namespace registry) or using integer namespaces as IPND, BPv7, and BPv6/CBHE do, or as a combination of "text name" and "integer label" as COSE [2] does for its parameters. [1] https://tools.ietf.org/html/draft-irtf-dtnrg-ipnd-03#section-2.6.3 [2] https://www.iana.org/assignments/cose/cose.xhtml#header-parameters CBOR Object Signing and Encryption (COSE)<https://www.iana.org/assignments/cose/cose.xhtml#header-parameters> CBOR Object Signing and Encryption (COSE) Created 2017-01-11 Last Updated 2019-08-20 Available Formats XML HTML Plain text. Registries included below. COSE Header Parameters www.iana.org CBOR Object Signing and Encryption (COSE)<https://www.iana.org/assignments/cose/> CBOR Object Signing and Encryption (COSE) Created 2017-01-11 Last Updated 2019-08-20 Available Formats XML HTML Plain text. Registries included below. COSE Header Parameters www.iana.org ________________________________ From: dtn <dtn-bounces@ietf.org> on behalf of Loiseau lucien <loiseau.lucien@gmail.com> Sent: Monday, December 2, 2019 03:59 To: dtn@ietf.org <dtn@ietf.org> Subject: [dtn] Convergence Layer Adapter - Endpoint IDs (CLA-EID) Hi all, last year I wrote a draft regarding the introduction of an EID format that would be specific to convergence layer adapters that I called IID (Interface IDentier): https://tools.ietf.org/html/draft-loiseau-dtn-cla-eid-00 The purpose was to have a generic EID format that would carry enough semantic so as to allow routing protocol and automatic connection scheduling to operate in a way that is not implementation specific. My use cases was the ability to maintain a link-local EID routing table as well as automatically initiating TCP connection for certain destination upon the reception of some bundles. The draft expired in May but I would be happy to take your comments and submit a new one with a better wording, please have a look! Best Regards, Lucien Loiseau
- [dtn] Convergence Layer Adapter - Endpoint IDs (C… Loiseau lucien
- Re: [dtn] Convergence Layer Adapter - Endpoint ID… Brian Sipos
- Re: [dtn] Convergence Layer Adapter - Endpoint ID… Loiseau lucien
- Re: [dtn] Convergence Layer Adapter - Endpoint ID… Brian Sipos