[dtn] CLA-specific endpoint identifier
Loiseau lucien <loiseau.lucien@gmail.com> Sat, 15 September 2018 08:21 UTC
Return-Path: <loiseau.lucien@gmail.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 B774D130E72 for <dtn@ietfa.amsl.com>; Sat, 15 Sep 2018 01:21:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 (2048-bit key) header.d=gmail.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 mDHiGkswQ0aO for <dtn@ietfa.amsl.com>; Sat, 15 Sep 2018 01:21:36 -0700 (PDT)
Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83DE01271FF for <dtn@ietf.org>; Sat, 15 Sep 2018 01:21:36 -0700 (PDT)
Received: by mail-qt0-x22e.google.com with SMTP id o15-v6so10933458qtk.6 for <dtn@ietf.org>; Sat, 15 Sep 2018 01:21:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=pXiwJHF7KJiuhkklrh7a5QvERcVGta1+MRwu1DmpCDA=; b=V3nw4d7MEcm+2JxirW5bgkSdEyo2e4HnfWyp/94nG9H6oTFrEeBkzr8ZDYVyUc2Uok D67TnWkerCOTw+VP77kL2guggUBUUheEEJzkeDeiFxJxvhfrIb6NzNIp9cYMHEyPgg0N qKFQST3yzYZjoCho2DgfUbNg5uMSFuWU1m+Ng3c+zkoIbyyafT7rbnl4TTzKO4aTs7Jd bOnPBX9iE9OVHQrnJcZhmNRi22tAOOszn5W88QyT/QfaUpwoQAbeR3UO6VfCl7XJ/tzT xuHs4sBqLik1o3f3OTSPmP2EdWghtpxCrI+ZidrpXOvsrpIL2vvWjGoRVLbCtB3GByq+ PLng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=pXiwJHF7KJiuhkklrh7a5QvERcVGta1+MRwu1DmpCDA=; b=SyFLj0aQoDBQrF7PdDDGWURfv6XaaKdcjjZG1KLi8ucVY6uBa+avLiRz2OQdlyyHi3 eZ28efEpts257ZokvLeU8FU7NrRGyuLCUYpYFpF7355pq8vvhAxfHOwCKRO0GyWwPbuj n23yfOIb/gOS2Rrrjn1z+80wSmdwND7o1FJBb19X4zLXTXTqMxiZ3ebR6Oof4QwkeKry ZTNVebOUdpuyjfFCL3Vg8booNO4hAMfA2xI1OQuai/GA7rm45ygt2SXQF14CyfnVxs5x 3oKTlCgw7UmFKvd0gixVNcEbWu00yp7ANJBfe9VBqKzuf+SWB5XkK9RL/qmK/FEambes zpHg==
X-Gm-Message-State: APzg51AfysHR67BWMB8iFfMulEy5em7QH7Dh6P5hl0fpdXpuhZn81xCW Fp9hjZlSAKbbPx4Jrca12NO95kwqpIcPS6QpLTMWiEJn
X-Google-Smtp-Source: ANB0VdZSuocY5EhfE76TS5bGySXVbhc7Qp0vuDk7GH7fe7Ix23pg40Ble3xblWfQY/fx9U3VG3bvOl5rgMSoW40YwXk=
X-Received: by 2002:a0c:8d8e:: with SMTP id t14-v6mr11473184qvb.32.1536999695402; Sat, 15 Sep 2018 01:21:35 -0700 (PDT)
MIME-Version: 1.0
From: Loiseau lucien <loiseau.lucien@gmail.com>
Date: Sat, 15 Sep 2018 10:21:24 +0200
Message-ID: <CANoKrvY8_e323gxFcGjOdM_v+hzuToUX_NRp-yGznJn_-tELRA@mail.gmail.com>
To: dtn@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/ArNigymUa6zUm2GmWBOnFK1A4TY>
Subject: [dtn] CLA-specific endpoint identifier
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: Sat, 15 Sep 2018 08:21:39 -0000
Hi, I was wondering if there has been any update on effort to standardise the dtn URI scheme: https://tools.ietf.org/html/draft-irtf-dtnrg-dtn-uri-scheme-00 On a related matter, It would make sense to have a link-specific EID to identify a dtn node based on its specific dtn interfaces such as: tcp4://1.2.3.4,4556 or tcp6://fe80::c4ff:5678:1234:ffb8,4556 Since every link-local EID would be CLA-specific, could we create a new scheme "cla" with value 3 whose scheme-specific part would have relevance to the convergence-layer managing this interface. The 'cla' scheme could follow the following format: cla:<CLA-NAME>:<CLA-SPECIFIC-PART> So the two previous example would be for instance: cla:tcpclv4:tcp4:1.2.3.4,4556 cla:stcp:tcp4:1.2.3.4,4557 cla:stcp:tcp6:fe80::c4ff:5678:1234:ffb8,4556 What do you think ? Lucien Lead Mesh Networking Scientist @ RightMesh
- [dtn] CLA-specific endpoint identifier Loiseau lucien