[dtn-security] Security implementation in Prophet rouing
Hao Zhuang <daniel.hao.zhuang@gmail.com> Wed, 02 November 2011 10:44 UTC
Return-Path: <daniel.hao.zhuang@gmail.com>
X-Original-To: dtn-security@ietfa.amsl.com
Delivered-To: dtn-security@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 513EA11E815E for <dtn-security@ietfa.amsl.com>; Wed, 2 Nov 2011 03:44:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.996
X-Spam-Level:
X-Spam-Status: No, score=-2.996 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_72=0.6, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_LOW=-1, WEIRD_PORT=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id amZMTOaKPMKj for <dtn-security@ietfa.amsl.com>; Wed, 2 Nov 2011 03:44:49 -0700 (PDT)
Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by ietfa.amsl.com (Postfix) with ESMTP id AF19621F8C0A for <dtn-security@irtf.org>; Wed, 2 Nov 2011 03:44:47 -0700 (PDT)
Received: by qyc1 with SMTP id 1so1377721qyc.13 for <dtn-security@irtf.org>; Wed, 02 Nov 2011 03:44:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=JZAeXaLDQ/3IQt4gr1Gjpq5L1mwptu8A3qr96D0Gizg=; b=xblEe4NgJF77ZilEKkjQhZn/jY8Ed3Pb21oi9GzT9ZMOycd8xniqBEChKtV9h1jEuI CC8Rf29n/AnQn83QyYq3eh9qOAuHBRv+uqezz0c6UdnoL7OxiU6lBN6wCCttA5ziyk4q gWHF1Z/tpiCRfPuXFhnxf3twrdG0a+fGgHMz0=
MIME-Version: 1.0
Received: by 10.182.41.69 with SMTP id d5mr760479obl.47.1320230685981; Wed, 02 Nov 2011 03:44:45 -0700 (PDT)
Received: by 10.182.145.99 with HTTP; Wed, 2 Nov 2011 03:44:45 -0700 (PDT)
Date: Wed, 02 Nov 2011 11:44:45 +0100
Message-ID: <CABL3tr5yAhBQwDzNao-6rLBpY45YCvH_vBVvWxuGHjKd3AxhrA@mail.gmail.com>
From: Hao Zhuang <daniel.hao.zhuang@gmail.com>
To: dtn-security@irtf.org
Content-Type: multipart/alternative; boundary="f46d0444e96b0f3b2404b0be29a3"
X-Mailman-Approved-At: Wed, 02 Nov 2011 03:56:27 -0700
Cc: Anitha Kathirvel <anithak@kth.se>, herve.ntareme@gamil.com, Xuelin Xiong <xuelin@kth.se>
Subject: [dtn-security] Security implementation in Prophet rouing
X-BeenThere: dtn-security@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Security." <dtn-security.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/dtn-security>, <mailto:dtn-security-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/dtn-security>
List-Post: <mailto:dtn-security@irtf.org>
List-Help: <mailto:dtn-security-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/dtn-security>, <mailto:dtn-security-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Nov 2011 10:46:26 -0000
Hi all,
We are going to transport the security implementation from* static routing*to
*Prophet routing*. In static routing, keystore files are imported to each
device and dtn software can find the correct destination's public key to
encrypt the symmetric key before sending the bundles. However, in
Propheting routing, how to get the right public key from the destination?
In static routing, dtn configure file
************************************************************************************
<tns:LinksSetting>
<!-- Setup your links here -->
<tns:Link id="village_tcp_link" conv_layer_type="tcp" dest="
192.168.1.2:4556" type="ONDEMAND"/>
<tns:Link id="city_tcp_link" conv_layer_type="tcp" dest="
192.168.2.3:4556" type="ONDEMAND"/>
<tns:Link id="androidLaptop_tcp_link" conv_layer_type="tcp" dest="
192.168.2.25:4556" type="ONDEMAND"/>
<tns:Link id="androidLaptop_tcp_link_viaVillage" conv_layer_type="tcp"
dest="192.168.1.25:4556" type="ONDEMAND"/>
<tns:Link id="tattoo_tcp_link" conv_layer_type="tcp" dest="
192.168.1.29:4556" type="ONDEMAND"/>
</tns:LinksSetting>
<!-- Routes Section -->
<tns:RoutesSetting *router_type="static"* local_eid="dtn://
nexus.bytewalla.com"> * // it can get the right destination public keys*
<!-- Setup your routes here -->
<tns:Route dest="dtn://village.bytewalla.com/*"
link_id="village_tcp_link"/>
<tns:Route dest="dtn://city.bytewalla.com/*" link_id="city_tcp_link"/>
<tns:Route dest="dtn://android.bytewalla.com/*"
link_id="androidLaptop_tcp_link_viaVillage"/>
<tns:Route dest="dtn://tattoo.bytewalla.com/*"
link_id="tattoo_tcp_link"/>
</tns:RoutesSetting>
************************************************************************************
*Now, in dynamic routing, the configure file is below*
************************************************************************************
<!-- Links Section -->
<tns:LinksSetting>
<!-- Setup your links here --> * //nothing
in the link section*
</tns:LinksSetting>
<!-- Routes Section -->
<tns:RoutesSetting *router_type="prophet"* P_encounter="0.5"
* //this is based on prophet routing*
P_encounter_first="0.25" delta="0.01" alpha="0.5" beta="0.9" K="1"
queuing="Fifo">
<!-- Setup your routes here -->
</tns:RoutesSetting>
<tns:DiscoveriesSetting>
<!-- Setup your Discovery here -->
<tns:Discovery id="ipdisc0" address_family="ip"
port="9556"></tns:Discovery>
<tns:Announce interface_id="tcp0" discovery_id="ipdisc0"
conv_layer_type="tcp"></tns:Announce>
</tns:DiscoveriesSetting>
************************************************************************************
Is there any idea on key transport under the environment of* prophet routing
*?
Thank you for your time.
Sincerely,
Hao