Re: [dtn-interest] dLife New Release: draft-moreira-dlife-01

[Anders Lindgren <[e-mail]>]

Hi Paolo,

I for one fully support taking on dLife as a DTNRG draft, and I look
forward to working together with you to try to get it through the
whole process a bit quicker than what was the case for PRoPHET. :)

I also still think that creating a common routing framework as
discussed before would be very beneficial, and I believe that Elwyn
and Avri are also still interested in this. I've been very busy with
other projects since the Mountain View meeting, but your timeplan of
having a -00 version of such a framework ready for the March meeting
seems very reasonable, so let's work towards that.

/Anders

On Tue, Oct 23, 2012 at 11:48 AM, Paulo Mendes
<[e-mail]> wrote:
> Dear all
>
> After having submitting version -00 in July we just released version -01 of
> the dLife routing protocol yesterday.
>
> Major differences are:
> - Definition of EID Dictionary and the correspondent TLV
> - Redefinition of ACK TLV
> - Further specification of Hello procedure and information exchange phases
> - Implementation over DTN2 and Bytewalla DTN devices (November - start of
> the evaluation process)
> - Creation of a Bluetooth convergence layer.
>
>
> Although this item will not be discussed in Atlanta I would like to raise
> oflline discussion to:
> - Have the draft approved as DTNRG draft
> - Understand if there is still interest from the DTNRG to draft a generic
> routing framework that would be used by any routing protocol.
>
> I would appreciate some feedback on this matter in order to organize our
> work until the Orlando meeting in March 2013, where we plan to submit
> another version of dLife, already with a full implementation and test-bed
> evaluation.
>
> *IF* there is still interest in drafting a generic routing framework (which
> makes all the sense IMO), we are available to contribute to have version -00
> read for Orlando.. This in case we would release the first DTNRG version of
> dLife already derived from the generic routing framework.
>
>
> Info about dLife version 01:
>
> Filename:  draft-moreira-dlife
> Revision:  01
> Title:  Opportunistic Routing based on Users Daily Life Routine
> Creation date:  2012-10-22
> WG ID:  Individual Submission
> Number of pages: 52
> URL:
> http://www.ietf.org/internet-drafts/draft-moreira-dlife-01.txt
> Status:          http://datatracker.ietf.org/doc/draft-moreira-dlife
> Htmlized:        http://tools.ietf.org/html/draft-moreira-dlife-01
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-moreira-dlife-01
>
> Abstract:
>   This document is written in the context of the Delay Tolerant
>   Networking Research Group and will be presented for reviewing by that
>   group. This document defines dLife, an opportunistic routing protocol
>   that takes advantage of time-evolving social structures. dLife
>   belongs to the family of social-aware opportunistic routing protocols
>   for intermittently connected networks. dLife operates based on a
>   representation of the dynamics of social structures as a weighted
>   contact graph, where the weights (i.e., social strengths) express how
>   long a pair of nodes is in contact over different period of times. It
>   considers two complementary utility functions: Time-Evolving Contact
>   Duration (TECD) that captures the evolution of social interaction
>   among pairs of users in the same daily period of time, over
>   consecutive days; and TECD Importance (TECDi) that captures the
>   evolution of user's importance, based on its node degree and the
>   social strength towards its neighbors, in different periods of time.
>   It is intended for use in wireless networks where there is no
>   guarantee that a fully connected path between any source -
>   destination pair exists at any time, a scenario where traditional
>   routing protocols are unable to deliver bundles. Such networks can be
>   sparse mesh, in which case intermittent connectivity is due to lack
>   of physical connections, or dense mesh, in which case intermittent
>   connectivity may be due to high interference or shadowing. In any
>   case, intermittent connectivity can also be due to the availability
>   of devices (e.g., unavailable due to power saving rules). The
>   document presents an architectural overview followed by the protocol
>   specification.
>
>
> Cheers
> Paulo
>
>
> On Oct 15, 2012, at 3:03 PM, Joerg Ott wrote:
>
> Folks,
>
> we have our agenda slot in Atlanta (Thu, 17:30 - 18:30).
>
> Our priority will be any open discussions of the documents
> we are supposed to finish:
>
> draft-irtf-dtnrg-dgram-clayer-00
> draft-irtf-dtnrg-tcp-clayer-04
> draft-sims-dtnrg-bpmib-02
> draft-dtnrg-ltp-cbhe-registries-03
>
> We have received reviews for the first three and we have an
> updated document for TCPCL following the review.  We need
> minor updates for the DGRAM CL and the MIB.
>
> Please try to provide those updates by the I-D submission deadline
> in a week from now.
>
> We intend to spend as much time as necessary to finish those
> and submit them for publication right after the IETF.
>
> Please drop us a note for further agenda slot requests if we
> have spare time in the end.
>
> Thanks,
> Jörg
> _______________________________________________
> dtn-interest mailing list
> [e-mail]
> https://www.irtf.org/mailman/listinfo/dtn-interest
>
>
> -------------------------------------------------------------
> Paulo Mendes, Ph.D
> Scientific Director for Innovation of the Research Unit in Informatics
> Systems and Technologies (SITI)
> Director of the Ph.D program on Informatics - New Media and Pervasive
> Systems (NEMPS)
> Secretary of the ACM SIGCOMM Chapter - Portugal
> University Lusofona, Portugal
> [e-mail]
> http://siti.ulusofona.pt/~pmendes
> Tel.: [phone] Fax: [phone]
>
>
> _______________________________________________
> dtn-interest mailing list
> [e-mail]
> https://www.irtf.org/mailman/listinfo/dtn-interest
>