From kfall@qti.qualcomm.com Fri Nov 2 13:20:03 2012 Return-Path: X-Original-To: dtn-interest@ietfa.amsl.com Delivered-To: dtn-interest@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8110C1F0C7E for ; Fri, 2 Nov 2012 13:20:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SqUjZfkJYn88 for ; Fri, 2 Nov 2012 13:20:03 -0700 (PDT) Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id C20511F0C6A for ; Fri, 2 Nov 2012 13:20:02 -0700 (PDT) X-IronPort-AV: E=McAfee;i="5400,1158,6884"; a="3890193" Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth02.qualcomm.com with ESMTP; 02 Nov 2012 12:57:07 -0700 X-IronPort-AV: E=Sophos;i="4.80,701,1344236400"; d="scan'208,217";a="1170126" Received: from nasanexhc03.na.qualcomm.com ([172.30.48.26]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 02 Nov 2012 13:20:01 -0700 Received: from NASANEXD01E.na.qualcomm.com ([169.254.5.59]) by NASANEXHC03.na.qualcomm.com ([172.30.48.26]) with mapi id 14.02.0318.001; Fri, 2 Nov 2012 13:20:01 -0700 From: "Fall, Kevin" To: "dtn-interest@irtf.org" Thread-Topic: talk about delay tolerant Thread-Index: AQHNuTdvFS4Bq4FJ7ES9bWq0M1H26Q== Date: Fri, 2 Nov 2012 20:20:00 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.45.230.6] Content-Type: multipart/alternative; boundary="_000_BB72E60F7A18154A9B1352D1DF6FEE571E26A438NASANEXD01Enaqu_" MIME-Version: 1.0 Subject: [dtn-interest] talk about delay tolerant X-BeenThere: dtn-interest@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2012 20:20:03 -0000 --_000_BB72E60F7A18154A9B1352D1DF6FEE571E26A438NASANEXD01Enaqu_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable http://www.bbc.co.uk/news/uk-20164591 --_000_BB72E60F7A18154A9B1352D1DF6FEE571E26A438NASANEXD01Enaqu_ Content-Type: text/html; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable --_000_BB72E60F7A18154A9B1352D1DF6FEE571E26A438NASANEXD01Enaqu_-- From dilipmailieee@gmail.com Fri Nov 2 14:22:51 2012 Return-Path: X-Original-To: dtn-interest@ietfa.amsl.com Delivered-To: dtn-interest@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F107211E80DE for ; Fri, 2 Nov 2012 14:22:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5K3h4bXOosXH for ; Fri, 2 Nov 2012 14:22:50 -0700 (PDT) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by ietfa.amsl.com (Postfix) with ESMTP id 15BA511E80D2 for ; Fri, 2 Nov 2012 14:22:50 -0700 (PDT) Received: by mail-oa0-f54.google.com with SMTP id n9so5131501oag.13 for ; Fri, 02 Nov 2012 14:22:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=gnxF1rEqFnsdhOKLtN5U/noZnO0upVk+Oc2HymZXQWE=; b=loUiFXBjrkKvS7eMxv/v0Ukjx5448FveBenCepocd885Kril3oYnokyC0efd5Cdr7L JFvU9GrkX5KRCEo+pD6WM64BqT1getIC53jUeZuP6UqIYOO6iOmzrTNxvEt7hwBRIY1d EJBDvu4jQq+3YsfYa7osY2cYUQRlFSl/YT4XFOPt28t1L7W3tI+MGmUoKZPDD5e1zGPt TYUfgcpDV8fONlOKB+BcgxFHNUeU/GvNcKvV3/pbeHl9qCHUqbDjS5J62Wert9uRxaZK XX1s4mGKTZKI+5Ckfvqt3C4Vu5CpK2S4//b5rqF+7TfQC7QH32CjS1zQKs7S+JvFbxmt H41g== MIME-Version: 1.0 Received: by 10.60.26.136 with SMTP id l8mr2429467oeg.52.1351891369546; Fri, 02 Nov 2012 14:22:49 -0700 (PDT) Received: by 10.182.45.168 with HTTP; Fri, 2 Nov 2012 14:22:49 -0700 (PDT) In-Reply-To: References: Date: Fri, 2 Nov 2012 14:22:49 -0700 Message-ID: From: Dilip Krishnaswamy To: "Fall, Kevin" Content-Type: text/plain; charset=ISO-8859-1 Cc: "dtn-interest@irtf.org" Subject: Re: [dtn-interest] talk about delay tolerant X-BeenThere: dtn-interest@irtf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: dilip@ieee.org List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2012 21:22:51 -0000 Delay tolerant buffering for 70 years? Perhaps the bundle lifetime was erroneously set to 100 years! On Fri, Nov 2, 2012 at 1:20 PM, Fall, Kevin wrote: > http://www.bbc.co.uk/news/uk-20164591 > > _______________________________________________ > dtn-interest mailing list > dtn-interest@irtf.org > https://www.irtf.org/mailman/listinfo/dtn-interest > From kfall@qti.qualcomm.com Wed Nov 7 11:49:00 2012 Return-Path: X-Original-To: dtn-interest@ietfa.amsl.com Delivered-To: dtn-interest@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F4E821F8B71 for ; Wed, 7 Nov 2012 11:49:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a0SJGZYMeGKF for ; Wed, 7 Nov 2012 11:48:58 -0800 (PST) Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id 62E4321F8B5D for ; Wed, 7 Nov 2012 11:48:58 -0800 (PST) X-IronPort-AV: E=McAfee;i="5400,1158,6888"; a="4917201" Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth02.qualcomm.com with ESMTP; 07 Nov 2012 11:25:32 -0800 X-IronPort-AV: E=Sophos;i="4.80,731,1344236400"; d="scan'208,217";a="1369738" Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 07 Nov 2012 11:48:57 -0800 Received: from NASANEXD01E.na.qualcomm.com ([169.254.5.59]) by nasanexhc08.na.qualcomm.com ([172.30.39.7]) with mapi id 14.02.0318.001; Wed, 7 Nov 2012 11:48:57 -0800 From: "Fall, Kevin" To: "dtn-interest@irtf.org" Thread-Topic: [icnrg] slides I presented (comparing ICN and DTN) Thread-Index: AQHNvSBK10AMXK4mh0yhncqx+G9InJfettCA Date: Wed, 7 Nov 2012 19:48:56 +0000 Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [199.106.115.132] Content-Type: multipart/alternative; boundary="_000_BB72E60F7A18154A9B1352D1DF6FEE571E26AC34NASANEXD01Enaqu_" MIME-Version: 1.0 Subject: [dtn-interest] FW: [icnrg] slides I presented (comparing ICN and DTN) X-BeenThere: dtn-interest@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Nov 2012 19:49:00 -0000 --_000_BB72E60F7A18154A9B1352D1DF6FEE571E26AC34NASANEXD01Enaqu_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I just sent this to the ICNRG list, and here it is for this list... -K From: , Kevin > Date: Wednesday, November 7, 2012 12:44 PM PST To: "icnrg@irtf.org" > Subject: [icnrg] slides I presented (comparing ICN and DTN) This seems to come up from time to time, so for those of you interested her= e is a link to some slides I gave recently on comparing DTN and ICN: http://kfall.net/ucbpage/talks/lcn-icn-dtn-keynote.pdf regards, - K --_000_BB72E60F7A18154A9B1352D1DF6FEE571E26AC34NASANEXD01Enaqu_ Content-Type: text/html; charset="us-ascii" Content-ID: <89F34FED199FF241A3233C670886B475@qualcomm.com> Content-Transfer-Encoding: quoted-printable
I just sent this to the ICNRG list, and here it is for this list... -K=

From: <Fall>, Kevin <kfall@qti.qualcomm.com>
Date: Wednesday, November 7, 2012 1= 2:44 PM PST
To: "icnrg@irtf.org" <icn= rg@irtf.org>
Subject: [icnrg] slides I presented= (comparing ICN and DTN)


This seems to come up from time to time, so for those of you intereste= d here is a link to some slides I gave recently on comparing DTN and ICN:


regards,
- K
--_000_BB72E60F7A18154A9B1352D1DF6FEE571E26AC34NASANEXD01Enaqu_-- From chiara.boldrini@iit.cnr.it Thu Nov 8 07:00:07 2012 Return-Path: X-Original-To: dtn-interest@ietfa.amsl.com Delivered-To: dtn-interest@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5871A21F8B4B for ; Thu, 8 Nov 2012 07:00:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.419 X-Spam-Level: X-Spam-Status: No, score=-0.419 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XyEHFzdlaW6w for ; Thu, 8 Nov 2012 07:00:05 -0800 (PST) Received: from turig1.iit.cnr.it (turig1.iit.cnr.it [146.48.98.71]) by ietfa.amsl.com (Postfix) with ESMTP id 2F91921F8B57 for ; Thu, 8 Nov 2012 07:00:03 -0800 (PST) Received: by turig1.iit.cnr.it (Postfix, from userid 1002) id B5206A086; Thu, 8 Nov 2012 16:00:01 +0100 (CET) Date: Thu, 08 Nov 2012 16:00:01 +0100 From: Chiara Boldrini To: dtn-interest@irtf.org Message-ID: <509bc8f1.QOUh8pHVJWgVZu+G%chiara.boldrini@iit.cnr.it> User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [dtn-interest] IEEE PerCom 2013 - Demo Session X-BeenThere: dtn-interest@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 15:00:07 -0000 PerCom Demo 2013 at PerCom'13 http://www.percom.org 18-22 March 2013, San Diego, USA The IEEE Pervasive Computing and Communication (PerCom) conference, entering its 11th year, is a premier scholarly venue in the areas of pervasive computing and communications. The PerCom Demo Session offers high-quality demonstrations of all things pervasive from academia and industry. Demos demonstrating working systems, innovative applications, groundbreaking ideas, and novel concepts related to PerCom are welcome. Demos from industrial researchers as well as demos from academia with a significant relevance to industry are particularly encouraged. A "Best Demo Award" will be presented based on research value, originality, and presentation. Submission Guidelines: * The demo proposals will be peer-reviewed. The evaluation criteria include: (1) extent and significance of the research contribution; (2) relevance to PerCom; (3) potential impact on the audience; (4) quality of the proposed implementation; (5) presentation quality. * Prospective contributors are expected to turn in a demo proposal in the form of a short technical paper (no more than 3 pages) using the PerCom templates. The short paper must illustrate the research contribution of the demo, the practical setup, and the technical requirements. Short demo papers will be included in the PerCom proceedings. * Demo proposals must be submitted through EDAS (https://edas.info/N13027?c=13027). The correct reception of each individual submission will be explicitly acknowledged by the demo co-chairs. * At least one author of each accepted demo proposal is required to register and present their demo at the conference. Topics include (but are not limited to): * Innovative pervasive computing applications * Adaptive and autonomic computing * Mobile/Wireless computing systems and services * Energy-efficient and green pervasive computing * Ad hoc networks for pervasive communications * Pervasive opportunistic applications * Enabling technologies for pervasive systems * Positioning and tracking technologies * Sensors and RFIDs in pervasive systems * Multimodal sensing and context applications * Smart devices and intelligent environments * Trust, security and privacy issues * User interface, interaction in pervasive systems * Pervasive computing aspects of social networking * Virtual immersive communications * Wearable computers * Standards and interfaces for pervasive computing * Context-aware computing Important Dates: Submission Deadline: November 15, 2012 Acceptance notification: January 7, 2013 Camera-ready deadline: January 25, 2013 Conference dates: March 18-22, 2013 (PerCom 2013) PerCom 2013 Demo Co-Chairs: Dipanjan Chakraborty, Ph.D (cdipanjan@in.ibm.com) Telecom Research Innovation Center IBM Research - India Lab Xun Luo, Ph.D (xunl@qti.qualcomm.com) Office of the Chief Scientist Research and Development Qualcomm Research San Diego, California, USA Eli Bozorgzadeh (eli@ics.uci.edu) University of California, Irvine, California, USA Questions, comments, or concerns? Please drop an e-mail to the Demo Co-Chairs. From ahennes1@gmail.com Thu Nov 8 11:57:10 2012 Return-Path: X-Original-To: dtn-interest@ietfa.amsl.com Delivered-To: dtn-interest@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C03C121F878C for ; Thu, 8 Nov 2012 11:57:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.977 X-Spam-Level: X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cLDeSREo4Hfj for ; Thu, 8 Nov 2012 11:57:08 -0800 (PST) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by ietfa.amsl.com (Postfix) with ESMTP id 00E3B21F872E for ; Thu, 8 Nov 2012 11:57:07 -0800 (PST) Received: by mail-ie0-f182.google.com with SMTP id k10so6260902iea.13 for ; Thu, 08 Nov 2012 11:57:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=e91JxUANSWkk5fiG/hl1Jj9BUtGLv4jJXYlFOR2EBuc=; b=bFuKyif4EFtMd5QMZWu6VBn0Epa3SNdzDpT2UaB86nXARRbaJ2SQKcfFK4jgwyrkcC xranHo+aYa8R9DIeeCel6A0EHuN875QiU21RQPH4A9Qgk/WWa2LbVs+DnEkDMj2zVCjY OYeWXmXn/MBNkuQNkB/zEpA2r+eXIjh9trjRgKt2M5iF1HLrw9v9v0winJiDb2/BUI2D rSOPq+9NEoCnsGaPXM4Rr90KTxAdpM++etubQ71j3/9a9OZd3z92oq6IceM5lrwlw3cP zynXAm8oJpx4l7a7yZ10VwTVdGU8FUxvzpHuFGagUTGKT9HMNlJda1JjSRRhpdxThF83 QvZA== MIME-Version: 1.0 Received: by 10.42.110.130 with SMTP id q2mr8142386icp.53.1352404626304; Thu, 08 Nov 2012 11:57:06 -0800 (PST) Sender: ahennes1@gmail.com Received: by 10.231.49.10 with HTTP; Thu, 8 Nov 2012 11:57:06 -0800 (PST) Date: Thu, 8 Nov 2012 14:57:06 -0500 X-Google-Sender-Auth: GhhFiuskgzstcgbu6FN2hQxe8Vo Message-ID: From: Angela Hennessy To: dtn-interest@irtf.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [dtn-interest] IP Neighbor Discovery draft available for review X-BeenThere: dtn-interest@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 20:03:33 -0000 We would like to announce a new draft describing DTN IP Neighbor Dsicovery, which is available at: http://www.ietf.org/internet-drafts/draft-irtf-dtnrg-ipnd-02.txt Any comments or questions would be greatly appreciated. Thanks, Angela From kfall@qti.qualcomm.com Thu Nov 8 12:57:39 2012 Return-Path: X-Original-To: dtn-interest@ietfa.amsl.com Delivered-To: dtn-interest@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2C4521F8A0C for ; Thu, 8 Nov 2012 12:57:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eXOzNliiqJzP for ; Thu, 8 Nov 2012 12:57:39 -0800 (PST) Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 5DD6521F898E for ; Thu, 8 Nov 2012 12:57:39 -0800 (PST) X-IronPort-AV: E=McAfee;i="5400,1158,6890"; a="5433766" Received: from ironmsg01-lv.qualcomm.com ([10.47.202.180]) by sabertooth01.qualcomm.com with ESMTP; 08 Nov 2012 12:43:00 -0800 X-IronPort-AV: E=Sophos;i="4.80,739,1344236400"; d="scan'208";a="1416418" Received: from nasanexhc03.na.qualcomm.com ([172.30.48.26]) by ironmsg01-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 08 Nov 2012 12:57:36 -0800 Received: from NASANEXD01E.na.qualcomm.com ([169.254.5.59]) by NASANEXHC03.na.qualcomm.com ([172.30.48.26]) with mapi id 14.02.0318.001; Thu, 8 Nov 2012 12:57:30 -0800 From: "Fall, Kevin" To: Angela Hennessy , "dtn-interest@irtf.org" Thread-Topic: [dtn-interest] IP Neighbor Discovery draft available for review Thread-Index: AQHNveyatTPYsZ0ELEiGPLVOR1QOUZfgWq4A Date: Thu, 8 Nov 2012 20:57:29 +0000 Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [199.106.115.132] Content-Type: text/plain; charset="us-ascii" Content-ID: <2F8FFAF316C2CA42AC3D3DCEAA8B68B7@qualcomm.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dtn-interest] IP Neighbor Discovery draft available for review X-BeenThere: dtn-interest@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 20:57:39 -0000 There's currently activity in IETF to extend mDNS (Boujour). It just met on Tue as a BOF. (agenda here: https://datatracker.ietf.org/meeting/85/agenda/mdnsext/) Since IPND is targeted for IP anyhow, is there a significant deficiency in using (say, an evolved) mDNS? - K On 11/8/12 11:57 AM PST, "Angela Hennessy" wrote: >We would like to announce a new draft describing DTN IP Neighbor >Dsicovery, which is available at: > >http://www.ietf.org/internet-drafts/draft-irtf-dtnrg-ipnd-02.txt > >Any comments or questions would be greatly appreciated. > >Thanks, >Angela >_______________________________________________ >dtn-interest mailing list >dtn-interest@irtf.org >https://www.irtf.org/mailman/listinfo/dtn-interest From wes@mti-systems.com Thu Nov 8 13:13:56 2012 Return-Path: X-Original-To: dtn-interest@ietfa.amsl.com Delivered-To: dtn-interest@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72FE621F8738 for ; Thu, 8 Nov 2012 13:13:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.42 X-Spam-Level: X-Spam-Status: No, score=-2.42 tagged_above=-999 required=5 tests=[AWL=0.179, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JRgxqud4gFPf for ; Thu, 8 Nov 2012 13:13:52 -0800 (PST) Received: from atl4mhob06.myregisteredsite.com (atl4mhob06.myregisteredsite.com [209.17.115.44]) by ietfa.amsl.com (Postfix) with ESMTP id 25F5521F85AE for ; Thu, 8 Nov 2012 13:13:44 -0800 (PST) Received: from mailpod.hostingplatform.com (mail.networksolutionsemail.com [205.178.146.50]) by atl4mhob06.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id qA8LDhZd030398 for ; Thu, 8 Nov 2012 16:13:43 -0500 Received: (qmail 11970 invoked by uid 0); 8 Nov 2012 21:13:42 -0000 Received: from unknown (HELO ?10.11.0.198?) (wes@mti-systems.com@46.21.99.29) by 0 with ESMTPA; 8 Nov 2012 21:13:42 -0000 Message-ID: <509C2075.70706@mti-systems.com> Date: Thu, 08 Nov 2012 16:13:25 -0500 From: Wesley Eddy Organization: MTI Systems User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: Angela Hennessy , dtn-interest@irtf.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dtn-interest] IP Neighbor Discovery draft available for review X-BeenThere: dtn-interest@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 21:13:56 -0000 On 11/8/2012 2:57 PM, Angela Hennessy wrote: > We would like to announce a new draft describing DTN IP Neighbor > Dsicovery, which is available at: > > http://www.ietf.org/internet-drafts/draft-irtf-dtnrg-ipnd-02.txt > > Any comments or questions would be greatly appreciated. > The approach is great for DTNs that are overlaid on IP networks. Many moons ago, some of us proposed a mechanism that was independent of the underlay, and could be used to indicate predicted future contacts, contact durations, etc. http://tools.ietf.org/html/draft-wyllie-dtnrg-badisc-01 This was implemented in DTN2, and tested to limited extent. In my opinion, that approach is superior, though I was an author, so may carry a bias. It would be good in the group to think about what the real needs and desirable properties for a discovery protocol are. -- Wes Eddy MTI Systems From kfall@qti.qualcomm.com Thu Nov 8 13:23:55 2012 Return-Path: X-Original-To: dtn-interest@ietfa.amsl.com Delivered-To: dtn-interest@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 645F221F89D0 for ; Thu, 8 Nov 2012 13:23:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CFWBo52ErFVL for ; Thu, 8 Nov 2012 13:23:54 -0800 (PST) Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id C7CD021F8944 for ; Thu, 8 Nov 2012 13:23:54 -0800 (PST) X-IronPort-AV: E=McAfee;i="5400,1158,6890"; a="5435347" Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by sabertooth02.qualcomm.com with ESMTP; 08 Nov 2012 13:00:16 -0800 X-IronPort-AV: E=Sophos;i="4.80,739,1344236400"; d="scan'208";a="362998833" Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 08 Nov 2012 13:23:48 -0800 Received: from NASANEXD01E.na.qualcomm.com ([169.254.5.59]) by nasanexhc08.na.qualcomm.com ([172.30.39.7]) with mapi id 14.02.0318.001; Thu, 8 Nov 2012 13:23:48 -0800 From: "Fall, Kevin" To: Wesley Eddy , Angela Hennessy , "dtn-interest@irtf.org" Thread-Topic: [dtn-interest] IP Neighbor Discovery draft available for review Thread-Index: AQHNveyatTPYsZ0ELEiGPLVOR1QOUZfg9gqA//9sAYA= Date: Thu, 8 Nov 2012 21:23:47 +0000 Message-ID: In-Reply-To: <509C2075.70706@mti-systems.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [199.106.115.132] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dtn-interest] IP Neighbor Discovery draft available for review X-BeenThere: dtn-interest@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 21:23:55 -0000 Just to pile on a little... We also worked on this draft: http://tools.ietf.org/id/draft-mcmahon-dtnrg-dtn-edp-00.txt which was not underlay-specific [and has since expired, regrettably]. Honestly I would like to see one bundle-layer discovery protocol that maps to underlying ones. (which might be Boujour, LLMNR, Alljoyn, whatever). - K On 11/8/12 1:13 PM PST, "Wesley Eddy" wrote: >On 11/8/2012 2:57 PM, Angela Hennessy wrote: >> We would like to announce a new draft describing DTN IP Neighbor >> Dsicovery, which is available at: >>=20 >> http://www.ietf.org/internet-drafts/draft-irtf-dtnrg-ipnd-02.txt >>=20 >> Any comments or questions would be greatly appreciated. >>=20 > > >The approach is great for DTNs that are overlaid on IP networks. > >Many moons ago, some of us proposed a mechanism that was >independent of the underlay, and could be used to indicate >predicted future contacts, contact durations, etc. >http://tools.ietf.org/html/draft-wyllie-dtnrg-badisc-01 > >This was implemented in DTN2, and tested to limited extent. > >In my opinion, that approach is superior, though I was an >author, so may carry a bias. > >It would be good in the group to think about what the real needs >and desirable properties for a discovery protocol are. > >--=20 >Wes Eddy >MTI Systems >_______________________________________________ >dtn-interest mailing list >dtn-interest@irtf.org >https://www.irtf.org/mailman/listinfo/dtn-interest From kfall@qti.qualcomm.com Fri Nov 9 09:33:57 2012 Return-Path: X-Original-To: dtn-interest@ietfa.amsl.com Delivered-To: dtn-interest@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A27FE21F8771 for ; Fri, 9 Nov 2012 09:33:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4RZh8pM2M+HD for ; Fri, 9 Nov 2012 09:33:57 -0800 (PST) Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id E58DD21F8760 for ; Fri, 9 Nov 2012 09:33:56 -0800 (PST) X-IronPort-AV: E=McAfee;i="5400,1158,6891"; a="5692451" Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by sabertooth01.qualcomm.com with ESMTP; 09 Nov 2012 09:19:14 -0800 X-IronPort-AV: E=Sophos;i="4.80,746,1344236400"; d="scan'208,217";a="363628307" Received: from nasanexhc14.na.qualcomm.com ([172.30.48.23]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 09 Nov 2012 09:33:55 -0800 Received: from NASANEXD01E.na.qualcomm.com ([169.254.5.59]) by nasanexhc14.na.qualcomm.com ([172.30.48.23]) with mapi id 14.02.0318.001; Fri, 9 Nov 2012 09:33:55 -0800 From: "Fall, Kevin" To: "dtn-interest@irtf.org" Thread-Topic: some comments on draft-zinky-dtnrg-erasure-coding-extension Thread-Index: AQHNvqBjgO4/+L0wNU2SSEVahbr81w== Date: Fri, 9 Nov 2012 17:33:54 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [199.106.115.132] Content-Type: multipart/alternative; boundary="_000_BB72E60F7A18154A9B1352D1DF6FEE571E26B296NASANEXD01Enaqu_" MIME-Version: 1.0 Subject: [dtn-interest] some comments on draft-zinky-dtnrg-erasure-coding-extension X-BeenThere: dtn-interest@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2012 17:33:57 -0000 --_000_BB72E60F7A18154A9B1352D1DF6FEE571E26B296NASANEXD01Enaqu_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I was reading this over yesterday. Here are some notes I made... this document really defines a new, different architecture that see= ms to use DTN as a sort of transport mechanism underneath yet it also seems to liberally make changes in a variety of bits an= d pieces of the existing structure, protocols and even architecture I initially expected the EC framework to be at a CL. The document needs a layering diagram in any case. I have concerns about the idea of typed data transfer (requiring IA= NA) in addition to Handling Instructions (due to complexity) specific to EC: What about ALC (RFC5775) and LCT (RFC5651)? or FLUTE (RFC6726)? ALC combines Layered Coding Transport (LCT) building block [RFC5651] FEC building block [RFC5052] multiple rate congestion control building block [RFC2357] while those are sort of IP-specific, can't their frameworks be re-us= ed here? why change the name of source symbol to Chunk? why change FEC Payload ID to "Encoding Vector" saying the encoding data is the "same length as the chuks": same as they ARE the chunks? Encoding set: why does it have to be a set of LINEAR equations? Wh= at if you have some other type of code? "some informtaion is put in the bundle primary block, such as the D= ata Object Transfer Specification" "Handling specification" - does this conflict with priority? I find 3.1 sort of backward. It says you have: data object -> encodings -> bundles I'd have expected this framework as a CL as thus: data object -> bundles -> encoded bundles Requirements in 3.1: divide into equal sized blocks, and assign UUI= D (ordering is required! -> what does this really imply) "The transfer spec cross cuts multiple layers by adding parameters = to the bundle header, extension blocks and Data Object's internal metadata= ".. uh ho. There is a new (big) concept of typed data (data objects and transf= er specifications) Feedback messages - are these more general? "Early research suggests" (sect 6.4) - reference? --_000_BB72E60F7A18154A9B1352D1DF6FEE571E26B296NASANEXD01Enaqu_ Content-Type: text/html; charset="us-ascii" Content-ID: <7CCB5C4CDE125D47B83187D3615B4F57@qualcomm.com> Content-Transfer-Encoding: quoted-printable
I was reading this over yesterday.  Here are some notes I made...=

        this document really defines a new, differ= ent architecture that seems
        to use DTN as a sort of transport mechanis= m underneath

        yet it also seems to liberally make change= s in a variety of bits and
        pieces of the existing structure, protocol= s and even architecture

        I initially expected the EC framework to b= e at a CL.  The document
        needs a layering diagram in any case.

        I have concerns about the idea of typed da= ta transfer (requiring IANA)
        in addition to Handling Instructions (due = to complexity)

        specific to EC:

        What about ALC (RFC5775) and LCT (RFC5651)= ?  or FLUTE (RFC6726)?
        ALC combines
                Layered Coding= Transport (LCT) building block [RFC5651]
                FEC building b= lock [RFC5052]
                multiple rate = congestion control building block [RFC2357]

       while those are sort of IP-specific, can't = their frameworks be re-used here?

        why change the name of source symbol to Ch= unk?
        why change FEC Payload ID to "Encodin= g Vector"
        saying the encoding data is the "same= length as the chuks": same as
                they ARE the c= hunks?
        Encoding set: why does it have to be a set= of LINEAR equations?  What if you have some other type of code?
        "some informtaion is put in the bundl= e primary block, such as the Data Object
        Transfer Specification"

        "Handling specification" - does = this conflict with priority?

        I find 3.1 sort of backward.  It says= you have:

        data object -> encodings -> bundles<= /div>

        I'd have expected this framework as a CL a= s thus:

        data object -> bundles -> encoded bu= ndles

        Requirements in 3.1: divide into equal siz= ed blocks, and assign UUID
        (ordering is required! -> what does thi= s really imply)

        "The transfer spec cross cuts multipl= e layers by adding parameters to the
        bundle header, extension blocks and Data O= bject's internal metadata".. uh ho.

        There is a new (big) concept of typed data= (data objects and transfer
        specifications)


        Feedback messages - are these more general= ?

        "Early research suggests" (sect = 6.4) - reference?

--_000_BB72E60F7A18154A9B1352D1DF6FEE571E26B296NASANEXD01Enaqu_-- From Fred.L.Templin@boeing.com Fri Nov 9 13:53:12 2012 Return-Path: X-Original-To: dtn-interest@ietfa.amsl.com Delivered-To: dtn-interest@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1258621F86F1 for ; Fri, 9 Nov 2012 13:53:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.157 X-Spam-Level: X-Spam-Status: No, score=-2.157 tagged_above=-999 required=5 tests=[AWL=-0.357, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YrlL+vLr19FE for ; Fri, 9 Nov 2012 13:53:11 -0800 (PST) Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id A3CA721F86DD for ; Fri, 9 Nov 2012 13:53:10 -0800 (PST) Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id qA9LrAIh012262 for ; Fri, 9 Nov 2012 13:53:10 -0800 Received: from XCH-NWHT-06.nw.nos.boeing.com (xch-nwht-06.nw.nos.boeing.com [130.247.25.110]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id qA9Lr9ga012234 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK) for ; Fri, 9 Nov 2012 13:53:09 -0800 Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-06.nw.nos.boeing.com ([130.247.25.110]) with mapi; Fri, 9 Nov 2012 13:53:09 -0800 From: "Templin, Fred L" To: "dtn-interest@irtf.org" Date: Fri, 9 Nov 2012 13:53:08 -0800 Thread-Topic: MTU considerations for 'draft-irtf-dtnrg-dgram-clayer-00' Thread-Index: AQHNvqBjgO4/+L0wNU2SSEVahbr815fh9D/g Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-TM-AS-MML: No Subject: [dtn-interest] MTU considerations for 'draft-irtf-dtnrg-dgram-clayer-00' X-BeenThere: dtn-interest@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2012 21:53:12 -0000 At the DTNRG meeting yesterday, I mentioned MTU considerations for UDP and DCCP convergence layers. Here are my suggestions for updates to the document: Thanks - Fred fred.l.templin@boeing.com 1) Section 3.1, rewrite as follows: "The Bundle Protocol allows bundles with sizes limited only by node resource constraints. In IPv4, the maximum size of a UDP datagram is nearly 64KB. In IPv6, when using jumbograms [RFC2675], UDP datagrams can be up to 4GB in size [RFC2147]. It is well understood that sending large IP datagrams that must be fragmented by the network has enormous efficiency penalties [Kent88]. Recent studies have also shown that undetected data corruption can result from sending IP fragments at high data rates [RFC4963], and that IP fragments are sometimes unconditionally discarded by the network [Attacks]. The Bundle Protocol specification provides a bundle fragmentation concept [RFC5050] that allows a large bundle to be divided into bundle fragments. If the Bundle Protocol is being encapsulated in DCCP or UDP, it therefore SHOULD create each fragment of sufficiently small size that it can then be encapsulated into a datagram that will not need to be fragmented at the IP layer." 2) Add a new Section 3.1.3 as follows: "3.1.3. Path MTU Determination for DCCP and UDP IP Path MTU Discovery [RFC1191][RFC1981] depends on the deterministic delivery of ICMP Packet Too Big (PTB) messages from routers in the network. However, studies have shown that these messages are frequently discarded by the network resulting in a condition known as a black hole [RFC2923][WAND][SIGCOMM]. A new means of path MTU determination that can operate in the absence of PTB messages has therefore been specified [RFC4821]. The UDP and DCCP bundle protocol CLs can determine an appropriate MTU by employing the positive feedback probing method specified in [RFC4821]= . In this process, the CL selects an initial segment size that is certain to traverse the path without loss due to an MTU restriction (e.g., 512 bytes for IPv4 or (1280-(UDP and IP header sizes)) bytes for IPv6). The CL can thereafter send probe messages of larger sizes (e.g., 1500 bytes, 4K bytes, 8K bytes, etc.) to elicit a response from the CL destination. If the CL receives a response, it can advance its segment size to the largest successful probe size. If the CL subsequently receives an ICMP PTB message, or if the path to the destination appears to be failing, it can again reduce the segment size. In this process, the CL MUST set the Don't Fragment flag in the IPv4 header to 1." 3) Add the following citations: [Attacks] Atlasis, A., "Attacking IPv6 Implementation Using Fragmentation", March 2012. [WAND] Luckie, M., Cho, K., and B. Owens, "Inferring and Debugging Path MTU Discovery Failures", October 2005 [SIGCOMM] Luckie, M. and B. Stasiewicz, "Measuring Path MTU Discovery Behavior", November 2010. From simon.perreault@viagenie.ca Sat Nov 10 08:13:42 2012 Return-Path: X-Original-To: dtn-interest@ietfa.amsl.com Delivered-To: dtn-interest@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FEB021F8482 for ; Sat, 10 Nov 2012 08:13:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.2 X-Spam-Level: X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[AWL=-0.399, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KJ8u-4DJ5D8b for ; Sat, 10 Nov 2012 08:13:41 -0800 (PST) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id A004A21F847F for ; Sat, 10 Nov 2012 08:13:41 -0800 (PST) Received: from porto.nomis80.org (85-169-39-219.rev.numericable.fr [85.169.39.219]) by jazz.viagenie.ca (Postfix) with ESMTPSA id DEF0E45BD0 for ; Sat, 10 Nov 2012 11:13:40 -0500 (EST) Message-ID: <509E7D33.7070000@viagenie.ca> Date: Sat, 10 Nov 2012 17:13:39 +0100 From: Simon Perreault User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121016 Thunderbird/16.0.1 MIME-Version: 1.0 To: dtn-interest@irtf.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [dtn-interest] MTU considerations for 'draft-irtf-dtnrg-dgram-clayer-00' X-BeenThere: dtn-interest@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 16:13:42 -0000 +1 Simon Le 2012-11-09 22:53, Templin, Fred L a écrit : > At the DTNRG meeting yesterday, I mentioned MTU considerations for > UDP and DCCP convergence layers. Here are my suggestions for updates > to the document: > > Thanks - Fred > fred.l.templin@boeing.com > > 1) Section 3.1, rewrite as follows: > > "The Bundle Protocol allows bundles with sizes limited only by node > resource constraints. In IPv4, the maximum size of a UDP datagram is > nearly 64KB. In IPv6, when using jumbograms [RFC2675], UDP datagrams > can be up to 4GB in size [RFC2147]. It is well understood that > sending large IP datagrams that must be fragmented by the network has > enormous efficiency penalties [Kent88]. Recent studies have also shown > that undetected data corruption can result from sending IP fragments > at high data rates [RFC4963], and that IP fragments are sometimes > unconditionally discarded by the network [Attacks]. > > The Bundle Protocol specification provides a bundle fragmentation > concept [RFC5050] that allows a large bundle to be divided into bundle > fragments. If the Bundle Protocol is being encapsulated in DCCP or UDP, > it therefore SHOULD create each fragment of sufficiently small size > that it can then be encapsulated into a datagram that will not need > to be fragmented at the IP layer." > > 2) Add a new Section 3.1.3 as follows: > > "3.1.3. Path MTU Determination for DCCP and UDP > > IP Path MTU Discovery [RFC1191][RFC1981] depends on the deterministic > delivery of ICMP Packet Too Big (PTB) messages from routers in the > network. However, studies have shown that these messages are frequently > discarded by the network resulting in a condition known as a black hole > [RFC2923][WAND][SIGCOMM]. A new means of path MTU determination that can > operate in the absence of PTB messages has therefore been specified > [RFC4821]. > > The UDP and DCCP bundle protocol CLs can determine an appropriate MTU > by employing the positive feedback probing method specified in [RFC4821]. > In this process, the CL selects an initial segment size that is certain > to traverse the path without loss due to an MTU restriction (e.g., 512 > bytes for IPv4 or (1280-(UDP and IP header sizes)) bytes for IPv6). The > CL can thereafter send probe messages of larger sizes (e.g., 1500 bytes, > 4K bytes, 8K bytes, etc.) to elicit a response from the CL destination. > If the CL receives a response, it can advance its segment size to the > largest successful probe size. If the CL subsequently receives an ICMP > PTB message, or if the path to the destination appears to be failing, > it can again reduce the segment size. > > In this process, the CL MUST set the Don't Fragment flag in the IPv4 > header to 1." > > 3) Add the following citations: > > [Attacks] Atlasis, A., "Attacking IPv6 Implementation Using > Fragmentation", March 2012. > > [WAND] Luckie, M., Cho, K., and B. Owens, "Inferring and > Debugging Path MTU Discovery Failures", October 2005 > > [SIGCOMM] Luckie, M. and B. Stasiewicz, "Measuring Path MTU > Discovery Behavior", November 2010. > > _______________________________________________ > dtn-interest mailing list > dtn-interest@irtf.org > https://www.irtf.org/mailman/listinfo/dtn-interest > -- DTN made easy, lean, and smart --> http://postellation.viagenie.ca NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca STUN/TURN server --> http://numb.viagenie.ca From scott.c.burleigh@jpl.nasa.gov Thu Nov 15 16:51:11 2012 Return-Path: X-Original-To: dtn-interest@ietfa.amsl.com Delivered-To: dtn-interest@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD64521F85B3 for ; Thu, 15 Nov 2012 16:51:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.598 X-Spam-Level: X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GaeizOHzJphp for ; Thu, 15 Nov 2012 16:51:10 -0800 (PST) Received: from mail.jpl.nasa.gov (mailhost.jpl.nasa.gov [128.149.139.106]) by ietfa.amsl.com (Postfix) with ESMTP id 5A99A1F0C49 for ; Thu, 15 Nov 2012 16:51:10 -0800 (PST) Received: from mail.jpl.nasa.gov (ap-ehub-sp02.jpl.nasa.gov [128.149.137.149]) by smtp.jpl.nasa.gov (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id qAG0p54Y029322 (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits) verified NO); Thu, 15 Nov 2012 16:51:05 -0800 Received: from AP-EMBX-SP40.RES.AD.JPL ([169.254.7.61]) by ap-ehub-sp02.RES.AD.JPL ([fe80::dd85:7b07:1e36:7e3c%15]) with mapi id 14.02.0318.001; Thu, 15 Nov 2012 16:51:05 -0800 From: "Burleigh, Scott C (313B)" To: "ion-users@ocp.ohiou.edu" , "ion-dtn-support@lists.sourceforge.net" , "dtn-interest@irtf.org" Thread-Topic: ION 3.1.0 Thread-Index: Ac3DksYzOB6AQy/nSumie1PVdQ0dDg== Date: Fri, 16 Nov 2012 00:51:03 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [128.149.137.113] Content-Type: multipart/alternative; boundary="_000_A5BEAD028815CB40A32A5669CF737C3B0F9E685Dapembxsp40RESAD_" MIME-Version: 1.0 X-Source-Sender: scott.c.burleigh@jpl.nasa.gov X-AUTH: Authorized Subject: [dtn-interest] ION 3.1.0 X-BeenThere: dtn-interest@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2012 00:51:12 -0000 --_000_A5BEAD028815CB40A32A5669CF737C3B0F9E685Dapembxsp40RESAD_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi. I've just posted version 3.1.0 of ION to SourceForge (https://sourcefo= rge.net/projects/ion-dtn/). ION 3.1.0 is mostly just bug fixes and perform= ance tweaks, but it does include a simple implementation of CBHE-compatible= bundle multicast that conforms to the spec in http://datatracker.ietf.org/= doc/draft-burleigh-dtnrg-imc/; there's a minimal demo of multicast bundle s= treaming in the "demos" directory. Scott --_000_A5BEAD028815CB40A32A5669CF737C3B0F9E685Dapembxsp40RESAD_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi.  I’ve j= ust posted version 3.1.0 of ION to SourceForge (https://sourceforge.net/projects/ion-dtn/).&= nbsp; ION 3.1.0 is mostly just bug fixes and performance tweaks, but it does include a simple implementation of CBHE-compatible bun= dle multicast that conforms to the spec in http:= //datatracker.ietf.org/doc/draft-burleigh-dtnrg-imc/; there’s a m= inimal demo of multicast bundle streaming in the “demos” direct= ory.

 

Scott

--_000_A5BEAD028815CB40A32A5669CF737C3B0F9E685Dapembxsp40RESAD_-- From chiara.boldrini@iit.cnr.it Mon Nov 19 07:00:04 2012 Return-Path: X-Original-To: dtn-interest@ietfa.amsl.com Delivered-To: dtn-interest@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71DA221F8686 for ; Mon, 19 Nov 2012 07:00:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.101 X-Spam-Level: X-Spam-Status: No, score=0.101 tagged_above=-999 required=5 tests=[AWL=-0.780, BAYES_50=0.001, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xlGhRjIXMeJm for ; Mon, 19 Nov 2012 07:00:03 -0800 (PST) Received: from turig1.iit.cnr.it (turig1.iit.cnr.it [146.48.98.71]) by ietfa.amsl.com (Postfix) with ESMTP id 396B821F8683 for ; Mon, 19 Nov 2012 07:00:02 -0800 (PST) Received: by turig1.iit.cnr.it (Postfix, from userid 1002) id 828343C815D; Mon, 19 Nov 2012 16:00:01 +0100 (CET) Date: Mon, 19 Nov 2012 16:00:01 +0100 From: Chiara Boldrini To: dtn-interest@irtf.org Message-ID: <50aa4971.aWbZ+ZrbSYAUAa+W%chiara.boldrini@iit.cnr.it> User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: [dtn-interest] IEEE PerCom 2013 Demo Session *** Deadline Extended to Nov 29 *** X-BeenThere: dtn-interest@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 15:00:04 -0000 PerCom Demo 2013 at PerCom'13 http://www.percom.org 18-22 March 2013, San Diego, USA The IEEE Pervasive Computing and Communication (PerCom) conference, ent= ering its 11th year, is a premier scholarly venue in the areas of perva= sive computing and communications. The PerCom Demo Session offers high-= quality demonstrations of all things pervasive from academia and indust= ry. Demos demonstrating working systems, innovative applications, groun= dbreaking ideas, and novel concepts related to PerCom are welcome. Demo= s from industrial researchers as well as demos from academia with a sig= nificant relevance to industry are particularly encouraged. A "Best Demo Award" will be presented based on research value, original= ity, and presentation. Submission Guidelines: *=09The demo proposals will be peer-reviewed. The evaluation criteria i= nclude: (1) extent and significance of the research contribution; (2) r= elevance to PerCom; (3) potential impact on the audience; (4) quality o= f the proposed implementation; (5) presentation quality. *=09Prospective contributors are expected to turn in a demo proposal in= the form of a short technical paper (no more than 3 pages) using the P= erCom templates. The short paper must illustrate the research contribut= ion of the demo, the practical setup, and the technical requirements. S= hort demo papers will be included in the PerCom proceedings. *=09 Demo proposals must be submitted through EDAS (https://edas.info/N= 13027?c=3D13027). The correct reception of each individual submission w= ill be explicitly acknowledged by the demo co-chairs. *=09At least one author of each accepted demo proposal is required to r= egister and present their demo at the conference.=20 Topics include (but are not limited to): *=09Innovative pervasive computing applications *=09Adaptive and autonomic computing *=09Mobile/Wireless computing systems and services *=09Energy-efficient and green pervasive computing *=09Ad hoc networks for pervasive communications *=09Pervasive opportunistic applications *=09Enabling technologies for pervasive systems *=09Positioning and tracking technologies *=09Sensors and RFIDs in pervasive systems *=09Multimodal sensing and context applications *=09Smart devices and intelligent environments *=09Trust, security and privacy issues *=09User interface, interaction in pervasive systems *=09Pervasive computing aspects of social networking *=09Virtual immersive communications *=09Wearable computers *=09Standards and interfaces for pervasive computing *=09Context-aware computing=20 Important Dates: Submission Deadline: November 29, 2012 (extended deadline) Acceptance notification: January 7, 2013 Camera-ready deadline: January 25, 2013 Conference dates: March 18-22, 2013 (PerCom 2013)=20 PerCom 2013 Demo Co-Chairs: Dipanjan Chakraborty, Ph.D (cdipanjan@in.ibm.com) Telecom Research Innovation Center IBM Research - India Lab Xun Luo, Ph.D (xunl@qti.qualcomm.com) Office of the Chief Scientist Research and Development Qualcomm Research=20 San Diego, California, USA Eli Bozorgzadeh (eli@ics.uci.edu) University of California, Irvine, California, USA Questions, comments, or concerns? Please drop an e-mail to the Demo Co-= Chairs.= From valerio.arnaboldi@iit.cnr.it Tue Nov 20 02:24:33 2012 Return-Path: X-Original-To: dtn-interest@ietfa.amsl.com Delivered-To: dtn-interest@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0043121F8703 for ; Tue, 20 Nov 2012 02:24:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.719 X-Spam-Level: X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id USQ4USoswcTq for ; Tue, 20 Nov 2012 02:24:32 -0800 (PST) Received: from irina.iit.cnr.it (irina-lan.iit.cnr.it [146.48.96.79]) by ietfa.amsl.com (Postfix) with ESMTP id 7D82821F8702 for ; Tue, 20 Nov 2012 02:24:32 -0800 (PST) Received: by irina.iit.cnr.it (Postfix, from userid 1001) id 72E643D81AA; Tue, 20 Nov 2012 11:24:01 +0100 (CET) Date: Tue, 20 Nov 2012 11:24:01 +0100 From: Valerio Arnaboldi To: dtn-interest@irtf.org Message-ID: <50ab5a41.+v4IjYA7NLQ8zYWf%valerio.arnaboldi@iit.cnr.it> User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: [dtn-interest] CFP: ComCom Special Issue on Opportunistic Networking X-BeenThere: dtn-interest@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 10:24:33 -0000 *** Our Sincere Apologies if you receive multiple copies of this messag= e *** -----------------------------------------------------------------------= --------- CALL FOR PAPERS Elsevier - Computer Communications Journal Special Issue on Opportunistic Networking Submission Deadline: February 10, 2013 -----------------------------------------------------------------------= --------- The widespread availability of mobile portable devices enriched with a = variety of sensing capabilities, coupled with the impelling need of com= munication anytime and anywhere, has rapidly raised the interest toward= s new approaches to communications between users. Opportunistic network= s are an instance of the delay tolerant paradigm applied to networks ma= de up of users' portable devices (such as smartphones and tablets). As = such, they are able to cope with challenged network conditions that are= often present in real life, such as high node mobility, variable conne= ctivity, and disconnections, which would impair communications in tradi= tional Mobile Ad Hoc Networks. In this scenario, user mobility becomes = one of the main drivers to enable message delivery. In fact, according = to the store-carry-and-forward paradigm, user devices store messages an= d carry them around while they move in the network, exchanging them upo= n encounter with other nodes, and eventually delivering them to their d= estination or to interested users. This new communication paradigm enab= les legacy applications in challenged scenarios, as well as it paves th= e way to innovative solutions. While opportunistic networks initially r= eceived attention to support communication where an infrastructure is n= ot available (for disaster recovery or in rural areas), nowadays a numb= er of applications can be envisaged ranging from content sharing, throu= gh mobile social networking, to participatory and urban sensing. All th= ese applications rely on data forwarding amongst devices. As a consequ= ence, two aspects become relevant, that is, the need for mechanisms gua= ranteeing trusted and secure communications while preserving users' pri= vacy (in the absence of infrastructure and sometimes even end-to-end co= nnectivity), and incentive mechanisms able to boost the participation i= n the network. This Special Issue of Computer Communications seeks contributions pushi= ng the state of the art in Opportunistic Networking. Topics of interest= include (but are not limited to) the following: - Mobility measurements and models, mobility trace analysis - Measurements, models, and analysis for user behaviors on mobile devic= es =20 - Unicast and multicast routing - Transport, congestion control, and reliability issues - Content dissemination, content caching, service composition, opportun= istic computing - Trust, security & privacy in opportunistic forwarding, incentive mech= anisms, reputation systems, and key management - Application support and middleware for opportunistic networks - New applications and services relying on opportunistic networking - Systems and experience for real-world deployments Schedule -------- Submission deadline: February 10, 2013 Author notification: May 24, 2013 Revised paper due: June 30, 2013 Final author notification: September 16, 2013 Publication: TBD Guest Editors ------------- Chiara Boldrini, IIT-CNR, Italy Kyunghan Lee, Ulsan National Institute of Science and Technology (UNIST= ), Korea Melek Onen, EURECOM, France Joerg Ott, Aalto University, Finland Elena Pagani, Universita' degli Studi di Milano, Italy Instructions for submission --------------------------- Manuscripts must not have been previously published nor currently under= review by other journals or conferences. If the paper was published in= a conference, the submitted manuscript should be a substantial extensi= on of the conference paper. In this case, authors are also required to = submit their published conference articles and a summary document expla= ining the enhancements made in the journal version. Papers must be submitted through the Computer Communications website at= http://ees.elsevier.com/comcom, where guidelines for manuscript prepar= ation can also be found. To ensure that all manuscripts are correctly i= dentified for consideration by the Special Issue, the authors should se= lect "Special Issue: Opp-Net" when they reach the "Article Type" step i= n the submission process. For further information, please contact the guest editors at comcomsi_oppnet@iit.cnr.it From schildt@ibr.cs.tu-bs.de Thu Nov 22 06:54:27 2012 Return-Path: X-Original-To: dtn-interest@ietfa.amsl.com Delivered-To: dtn-interest@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA71E21F8565 for ; Thu, 22 Nov 2012 06:54:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pqd2Q84ERM5w for ; Thu, 22 Nov 2012 06:54:26 -0800 (PST) Received: from salvator.ibr.cs.tu-bs.de (salvator.ibr.cs.tu-bs.de [IPv6:2001:638:602:1181:21a:64ff:fed3:6c8c]) by ietfa.amsl.com (Postfix) with ESMTP id 7151921F856F for ; Thu, 22 Nov 2012 06:54:25 -0800 (PST) Received: from [IPv6:2001:638:602:1181:40fe:f441:b5c8:a8bc] (unknown [IPv6:2001:638:602:1181:40fe:f441:b5c8:a8bc]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: schildt@ibr.cs.tu-bs.de) by salvator.ibr.cs.tu-bs.de (Postfix) with ESMTPSA id 8E07B13E5E; Thu, 22 Nov 2012 15:54:16 +0100 (CET) Message-ID: <50AE3C97.9060706@ibr.cs.tu-bs.de> Date: Thu, 22 Nov 2012 15:54:15 +0100 From: Sebastian Schildt User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Wesley Eddy , ahennes1@math.umd.edu, dtn-interest@irtf.org References: <509C2075.70706@mti-systems.com> In-Reply-To: <509C2075.70706@mti-systems.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: clamav-milter 0.97.3 at salvator X-Virus-Status: Clean Subject: Re: [dtn-interest] IP Neighbor Discovery draft available for review X-BeenThere: dtn-interest@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Nov 2012 14:54:27 -0000 On 11/08/2012 10:13 PM, Wesley Eddy wrote: > The approach is great for DTNs that are overlaid on IP networks. Many > moons ago, some of us proposed a mechanism that was independent of the > underlay, and could be used to indicate predicted future contacts, > contact durations, etc. > http://tools.ietf.org/html/draft-wyllie-dtnrg-badisc-01 This was > implemented in DTN2, and tested to limited extent. In my opinion, that > approach is superior, though I was an author, so may carry a bias. It > would be good in the group to think about what the real needs and > desirable properties for a discovery protocol are. In our opinion one great thing about IPND (we used the old draft specification http://tools.ietf.org/html/draft-irtf-dtnrg-ipnd-01 in our implementations) is, that despite its name it is not really IP specific. The general frame format can be used on top of any transport adding suitable entries in the services block. In fact µDTN (http://www.ibr.cs.tu-bs.de/projects/mudtn/) includes some support for IPND, even though it runs on sensor nodes using IEEE 802.15.4 without any IP stack. Maybe the current draft should be reworded a little bit to make clear that its scope can be extended beyond IP towards any transport/medium supporting local broadcasts. Sebastian From chiara.boldrini@iit.cnr.it Mon Nov 26 07:00:05 2012 Return-Path: X-Original-To: dtn-interest@ietfa.amsl.com Delivered-To: dtn-interest@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D029A21F857E for ; Mon, 26 Nov 2012 07:00:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.881 X-Spam-Level: X-Spam-Status: No, score=0.881 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wuIKAHriaUma for ; Mon, 26 Nov 2012 07:00:04 -0800 (PST) Received: from turig1.iit.cnr.it (turig1.iit.cnr.it [146.48.98.71]) by ietfa.amsl.com (Postfix) with ESMTP id B2F6E21F8450 for ; Mon, 26 Nov 2012 07:00:03 -0800 (PST) Received: by turig1.iit.cnr.it (Postfix, from userid 1002) id 275C23C815D; Mon, 26 Nov 2012 16:00:02 +0100 (CET) Date: Mon, 26 Nov 2012 16:00:02 +0100 From: Chiara Boldrini To: dtn-interest@irtf.org Message-ID: <50b383f2.G47WKtDCgq6/M6K7%chiara.boldrini@iit.cnr.it> User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [dtn-interest] IEEE PerCom 2013 - CFP for Affiliated Events and Workshops X-BeenThere: dtn-interest@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Nov 2012 15:00:05 -0000 *** Our Sincere Apologies if you receive multiple copies of this message *** -------------------------------------------------------------------------------- CONSOLIDATED CALL FOR PAPERS FOR AFFILIATED EVENTS AND WORKSHOPS Eleventh IEEE International Conference on Pervasive Computing and Communications PerCom 2013 (http//www.percom.org/) San Diego USA, March 18 - 22, 2013 -------------------------------------------------------------------------------- PerCom is the premier scholarly venue in the areas of pervasive computing and communications. Detailed information about the scope of events, paper submission process, etc. can be obtained at http://www.percom.org/ and also the URLs given below. ################################################################################ PhD Forum: The Sixth Annual Ph.D. Forum on Pervasive Computing and Communications The Ph.D. Forum will provide an opportunity for Ph.D. students to present their dissertation research, including work in progress, to the pervasive computing and communication community. The Forum will be organized as a combined one-day workshop prior to the PerCom conference and a poster session during the main conference to encourage interaction between Ph.D. students and researchers from academia, industry, and government. URL: http://www.percom.org/ Paper Submission Deadline: December 15, 2012 (Paper Registration: November 30, 2012) ################################################################################ Demos: PerCom'13 Demo 2013 The Demo session aims to provide high-quality demonstrations of all things pervasive from academia and industry. Demos demonstrating working systems, innovative applications, groundbreaking ideas, and novel concepts related to PerCom are welcome. URL: http://www.percom.org/ Demo Submission Deadline: November 29, 2012 ################################################################################ C3: Workshop on Cognitive Computing and Communications This international workshop aims to bring researchers together to exchange ideas on the applications of cognitive computing and communications (C3) for designing smart pervasive systems. URL: http://feihu.eng.ua.edu/PerCom_C3.html Paper Submission Deadline: December 10, 2012 ################################################################################ IQ2S: Workshop on Information Quality and Quality of Service for Pervasive Computing The objective of this workshop is to provide a forum to exchange ideas, present results, share experience, and enhance collaborations among researchers, professionals, and application developers in various aspects of Quality of Service (QoS) and Quality of Information (QoI) in wireless sensor networks for pervasive computing. URL: http://www.iq2s.org/ Paper Submission Deadline: December 10, 2012 ################################################################################ MP2P: Workshop on Mobile Peer-to-Peer Computing The main goal of the workshop is to gather scientists from areas such as networking, information dissemination, databases, and security to foster collaboration and sparkle discussion on various aspects of mobile P2P. URL: http://mpclab.ce.ncu.edu.tw/mp2p2013/ Paper Submission Deadline: November 30, 2012 ################################################################################ MUCS: Workshop on Managing Ubiquitous Communications and Services The MUCS workshop provides a forum for researchers and practitioners to explore the theoretic, technological and organizational challenges of managing ubiquitous communications and services, and to present advances in management techniques and technologies, for pervasive computing and smart space applications. URL: http://ubiquitous-management.org/mucs/2013/index.php Paper Submission Deadline: December 9, 2012 ################################################################################ PerNEM: Workshop on Pervasive Networks for Emergency Management This workshop focuses on pervasive networked sensing and decision making, both wired and wireless, geared towards emergency management. URL: http://san.ee.ic.ac.uk/pernem2013/ Paper Submission Deadline: November 26, 2012 ################################################################################ SEnAml: Workshop on Smart Environments and Ambient Intelligence This workshop seeks to provide a cross-disciplinary approach to smartization, through a multi-sided view of the current research accomplished at different technological layers: sensors, software, data fusion and services. URL: http://www.grpss.ssr.upm.es/senami2013/ Paper Submission Deadline: November 30, 2012 ################################################################################