Re: [dtn-security] Security implementation in Prophet rouing

s.shukla@iitp.ac.in Wed, 02 November 2011 11:19 UTC

Return-Path: <s.shukla@iitp.ac.in>
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 9F5361F0C8E for <dtn-security@ietfa.amsl.com>; Wed, 2 Nov 2011 04:19:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.799
X-Spam-Level:
X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_102=0.6, J_CHICKENPOX_56=0.6, J_CHICKENPOX_72=0.6]
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 agUNsjlZT1yS for <dtn-security@ietfa.amsl.com>; Wed, 2 Nov 2011 04:19:55 -0700 (PDT)
Received: from magadh.iitp.ac.in (magadh.iitp.ac.in [210.212.18.211]) by ietfa.amsl.com (Postfix) with ESMTP id 532AC1F0C91 for <dtn-security@irtf.org>; Wed, 2 Nov 2011 04:19:54 -0700 (PDT)
Received: from ashoka.iitp.ac.in (ashoka.iitp.ac.in [172.16.1.11] (may be forged)) by magadh.iitp.ac.in (8.14.2/8.14.2) with ESMTP id pA2BeUv5027295; Wed, 2 Nov 2011 17:10:31 +0530
Received: from [172.16.1.11] (localhost.localdomain [127.0.0.1]) by ashoka.iitp.ac.in (Postfix) with ESMTP id 5F9B67D625E; Wed, 2 Nov 2011 16:50:35 +0530 (IST)
Received: from 172.16.1.4 (SquirrelMail authenticated user s.shukla) by 172.16.1.11 with HTTP; Wed, 2 Nov 2011 16:50:35 +0530
Message-ID: <75e4cb2820331747c270a9fbc401a787.squirrel@172.16.1.11>
In-Reply-To: <CABL3tr5yAhBQwDzNao-6rLBpY45YCvH_vBVvWxuGHjKd3AxhrA@mail.gmail.com>
References: <CABL3tr5yAhBQwDzNao-6rLBpY45YCvH_vBVvWxuGHjKd3AxhrA@mail.gmail.com>
Date: Wed, 2 Nov 2011 16:50:35 +0530
From: s.shukla@iitp.ac.in
To: "Hao Zhuang" <daniel.hao.zhuang@gmail.com>
User-Agent: SquirrelMail/
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: by amavisd-new
Cc: Xuelin Xiong <xuelin@kth.se>, dtn-security@irtf.org, herve.ntareme@gamil.com, Anitha Kathirvel <anithak@kth.se>
Subject: Re: [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 11:19:55 -0000

Hi Daniel,
I am novice in this area but somthing strike on my mind so I want to share
it with you, Prophet works on history of encounters(so whenever source
node encounter relay it will store its public key for future reference).
In case destination is not available in history of encounters then source
will use second property of prophet i.e transitivity for 1 hop encryption.
I hope my suggestions is correct and useful for you... :)

best/
Shailendra.



> 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
> _______________________________________________
> dtn-security mailing list
> dtn-security@irtf.org
> https://www.irtf.org/mailman/listinfo/dtn-security
>


###################################################
// Double the Pride,Double the Fall //