From mip4-bounces@ietf.org Mon Oct 02 10:34:03 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUOrh-0001cS-JN; Mon, 02 Oct 2006 10:33:53 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GTaED-0006fP-D4 for mip4@ietf.org; Sat, 30 Sep 2006 04:29:45 -0400 Received: from smtp102.biz.mail.re2.yahoo.com ([68.142.229.216]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GTaE7-0000Bz-Fz for mip4@ietf.org; Sat, 30 Sep 2006 04:29:45 -0400 Received: (qmail 96109 invoked from network); 30 Sep 2006 08:29:38 -0000 Received: from unknown (HELO YEOBS) (boonsain.yeo@sensimesh.com@218.186.172.126 with login) by smtp102.biz.mail.re2.yahoo.com with SMTP; 30 Sep 2006 08:29:37 -0000 Message-ID: <004201c6e46a$874c03d0$8001a8c0@YEOBS> From: "Boon Sain YEO" To: Date: Sat, 30 Sep 2006 16:29:10 +0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Spam-Score: 0.2 (/) X-Scan-Signature: cdb443e3957ca9b4c5b55e78cfcf4b26 X-Mailman-Approved-At: Mon, 02 Oct 2006 10:33:52 -0400 Cc: Subject: [Mip4] WCNC 2007 deadeline Fast Approaching X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1091424653==" Errors-To: mip4-bounces@ietf.org This is a multi-part message in MIME format. --===============1091424653== Content-Type: multipart/alternative; boundary="----=_NextPart_000_003F_01C6E4AD.8EB5EBC0" This is a multi-part message in MIME format. ------=_NextPart_000_003F_01C6E4AD.8EB5EBC0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable (Apologies for multiple copies received) Final Call for Papers: 3 October 2006!!! IEEE Wireless Communications & Networking Conference (WCNC 2007) 11 =96 15 March 2007 /Hong Kong Make sure you are a part of the first WCNC conference outside North = America =96 held in Asia=92s world city, Hong Kong , China , The WCNC is = the one of the world=92s foremost international technical conference for = engineers and researchers at the forefront of development and deployment = of wireless technologies.=20 IMPORTANT DATES Full paper submissions: 3 October 2006 =20 Notification of acceptance: 8 December 2006 Camera ready submission: 5 January 2007 ORGANIZATION General Chairs Technical = Program Chair Khaled B. Letaief, Chih-Lin I Ross D. Murch For more WCNC 2007 details & updates please visit: = http://www.ieee-wcnc.org To unsubscribe from this IEEE Communications Society WCNC 2005 CFP = mailing list=20 send a blank email message to wcnccfp-remove@comsoc.org.=20 You can also request removal by mail. Please send a note with your email = address=20 and the list name (wcnccfp@comsoc.org) to=20 ComSoc List Removal - IT=20 3 Park Avenue, 17th Floor=20 New York, NY 10016 USA ------=_NextPart_000_003F_01C6E4AD.8EB5EBC0 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
(Apologies for multiple copies=20 received)
3D""

Final=20 Call for Papers:      3 October=20 2006!!!

IEEE=20 Wireless Communications & Networking Conference (WCNC=20 2007)
11 =96 15 = March 2007=20 /Hong=20 Kong
Make=20 sure you are a part of the first WCNC conference outside North America = =96 held in=20 Asia=92s world city, Hong = Kong=20 , China = ,=20 The WCNC is the one of the world=92s foremost international technical = conference=20 for engineers and researchers at the forefront of development and = deployment of=20 wireless technologies.
IMPORTANT=20 DATES
Full paper=20 submissions:             =20        3 October 2006    =20  
Notification of acceptance:         =20        8 December 2006
Camera = ready=20 submission:           &= nbsp;=20    5 January 2007

ORGANIZATION

General=20 Chairs            =20             =    =20             =    =20 Technical Program Chair
Khaled B. Letaief, Chih-Lin=20 I            =          =20   Ross D. Murch

For=20 more WCNC 2007 details & updates=20 please=20 visit: =20 http://www.ieee-wcnc.org

 





To=20 unsubscribe from this IEEE Communications Society WCNC 2005 CFP mailing = list=20
send a blank email message to wcnccfp-remove@comsoc.org.

You = can=20 also request removal by mail. Please send a note with your email address =
and=20 the list name (wcnccfp@comsoc.org) to

ComSoc List Removal - IT =
3=20 Park Avenue, 17th Floor
New York, NY 10016 USA ------=_NextPart_000_003F_01C6E4AD.8EB5EBC0-- --===============1091424653== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ --===============1091424653==-- From mip4-bounces@ietf.org Mon Oct 02 10:34:21 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUOs9-0001lM-2j; Mon, 02 Oct 2006 10:34:21 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GU7su-0008K5-Qs; Sun, 01 Oct 2006 16:26:00 -0400 Received: from [2001:12f0:201:1:202:e3ff:fe0f:b8d] (helo=mailman.ufsc.br) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GU7rM-00039Y-8i; Sun, 01 Oct 2006 16:26:00 -0400 Received: from localhost (localhost [127.0.0.1]) by mailman.ufsc.br (Postfix) with ESMTP id A8E5A7DC9F; Sun, 1 Oct 2006 17:21:34 -0300 (BRT) Received: from mailman.ufsc.br ([127.0.0.1]) by localhost (mailman.ufsc.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08297-02; Sun, 1 Oct 2006 17:21:34 -0300 (BRT) Received: from mailman.ufsc.br (mailman.ufsc.br [150.162.1.5]) by mailman.ufsc.br (Postfix) with ESMTP id D135F7DB2E; Sun, 1 Oct 2006 17:20:21 -0300 (BRT) X-Original-To: researchers@mailman.ufsc.br Delivered-To: researchers@mailman.ufsc.br Received: from localhost (localhost [127.0.0.1]) by mailman.ufsc.br (Postfix) with ESMTP id AD6557DAC3 for ; Sun, 1 Oct 2006 17:20:11 -0300 (BRT) Received: from mailman.ufsc.br ([127.0.0.1]) by localhost (mailman.ufsc.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08072-03 for ; Sun, 1 Oct 2006 17:20:07 -0300 (BRT) Received: from rot.barddal.br (44054.static.fln.virtua.com.br [200.174.44.54]) by mailman.ufsc.br (Postfix) with ESMTP id 08A887DA96 for ; Sun, 1 Oct 2006 17:20:01 -0300 (BRT) Received: from mi0f9a3e303b4e (201-25-232-82.fnsce703.dsl.brasiltelecom.net.br [201.25.232.82]) (authenticated bits=0) by rot.barddal.br (8.13.1/8.13.1) with ESMTP id k91KKEja018710; Sun, 1 Oct 2006 20:20:17 GMT Message-ID: <047a01c6e597$24a05eb0$4000a8c0@mi0f9a3e303b4e> From: "Profa Mirela Sechi Moretti Annoni Notare" To: Date: Sun, 1 Oct 2006 17:21:00 -0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Antivirus: avast! (VPS 0639-4, 29/09/2006), Outbound message X-Antivirus-Status: Clean X-barddal-MailScanner-Information: Please contact the ISP for more information X-barddal-MailScanner: Found to be clean X-barddal-MailScanner-SpamCheck: spam, SpamAssassin (not cached, escore=7.593, requerido 6, BAYES_00 -2.60, HELO_DYNAMIC_IPADDR 4.40, RCVD_IN_DSBL 3.81, RCVD_IN_SORBS_DUL 1.99) X-barddal-MailScanner-SpamScore: sssssss X-barddal-MailScanner-From: mirela@barddal.br X-Virus-Scanned: by amavisd-new at mailman.ufsc.br X-BeenThere: researchers@mailman.ufsc.br X-Mailman-Version: 2.1.5 Precedence: list X-Virus-Scanned: by amavisd-new at mailman.ufsc.br Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.1 (/) X-Scan-Signature: 4b66a1e94d7d92973ece9e5da449ff80 X-Mailman-Approved-At: Mon, 02 Oct 2006 10:34:19 -0400 Cc: Subject: [Mip4] [Researchers] {Spam?} I2TS'2006 - 5th International Information and Telecommunication Technologies Symposium X-BeenThere: mip4@ietf.org List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org CALL FOR PAPERS I2TS'2006 - 5th International Information and Telecommunication Technolog= ies=20 Symposium Cuiab=E1, Mato Grosso, Brazil, December 06-08, 2006 The International Information and Telecommunication Technologies Symposiu= m=20 (I2TS'2006) at Cuiab=E1 city,in the paradisiac Pantanal (South Amazonia), Brazil. I2TS'2006 serves as an international forum for people from academia,indus= try=20 and research labs, for presenting recent results in information and telecommunication=20 technologies research and applications. I2TS'2006 includes Technical Sessions, Tool Sessions, Poster Sessions and= =20 Mini-coursers. SUBMISSION GUIDELINES Authors are encouraged to submit both theoretical and practical results o= f=20 significance. Demonstration of new tools/applications are welcome. The papers should be submitted in electronic form (PDF only) by JEMS system (Brazilian EDAS) at https://submissoes.sbc.org.br/i2ts2006= . The length of the papers are as follows: Full papers: 8 pages (IEEE Two Column Format) Short papers: 4 pages (IEEE Two Column Format) - research in progress Posters and Tools: 2 pages (IEEE Two COlumn Format) See Instruction for Authors in the web page. The English papers will be published in hard copy and CD-ROM; the portuguese papers will be published in CD-ROM only (same ISBN). Best papers will be invited to submit extended version to IEEE-R9=20 LatinAmerica and RESI magazines. Relevant topics include, but are not limited to: TELECOMMUNICATION AND WIRELESS NETWORKS - Wireless Sensor Networks - Mobile Ad Hoc Networks - MANETs - Wireless Multimedia - Telecommunication Technology - Optical Networks and Switching - Wireless WANs, LANs and PANs (Personal Area Networks) - Quality of Service - Mobile wireless network Planning, Management, Control and Monitoring - Security and Privacy - Applications and Case Studies COMPUTER NETWORKS, REAL TIME AND DISTRIBUTED SYSTEMS - Real-Time and Multimedia Systems - Parallel and Distributed Systems - Distributed and Mobile Computing - Distributed Algorithms and Architectures - Distributed Operating Systems - Distributed Data Management - Computer Networks - P2P and Overlay networks - Quality of Service - Network Planning, Management, Control and Monitoring - Security and Privacy - Applications and Case Studies DISTRIBUTED SIMULATIONS, UBIQUITOUS COMPUTING AND INFORMATION TECHNOLOGY - Large Scale Distributed Interactive Simulation - Ubiquitous Computing (architectures, systems, human-computer interactio= n) - Context aware computing - Web-Based Systems (architectures, programming models, tools etc) - Semantic web and ontologies - Embedded Systems - Criminal in the Internet and Electronic Justice - Tools for Computational Forensic - Applications and Case Studies - Collaborative Virtual Environments (Synchronization, Extensibility, Persistency, Interoperability,=20 Scalability, Adaptability, Security) TOOL SESSIONS and POSTER SESSIONS Authors are encouraged to submit papers describing tools suitable for=20 on-line demonstration. Standard microcomputers will be available for tool sessions. The tool and poster papers will undergo a regular review process and will be published in the conference proceedings in a dedicated tool a= nd=20 poster sessions, respectively. MINI-COURSES Proposals for half-day or full-day MiniCourses are solicited on timely=20 topics related to the above areas. The proposal must include description and short-biographies. IMPORTANT DATES Paper/Poster/ToolMiniCourses Submission Deadline: October 15th, 2006 Authors Notification: November 18th, 2006 Camera Ready/Paper Registration: November 25th, 2006 Sponsored by: UFSC-INE - Federal University of Santa Catarina UNIVAG - Varzea Grande University BARDDAL - Barddal University CEFET-MT - Federal Technical Center IEEE-R9 - IEEE Region9 - LatinAmerica GENERAL CO-CHAIRS Azzedine Boukerche - University of Ottawa - Canada Jo=E3o Bosco Mangueira Sobral - UFSC - Brazil TECHNICAL PROGRAM COMMITTEE CO-CHAIRS Antonio Alfredo F. Loureiro - UFMG - Brazil Mirela Sechi Moretti Annoni Notare - Barddal University - Brazil PROGRAM COMMITTEE Abbas, Claudia Barenco - UnB - Brazil Aguiar, Einstein Lemos de - UFMT - Brazil Almulla, Mohammed - Kuwait University - Kuwait Araujo, Regina Borges - UFSCar - Brazil Benyoucef, Morad - University of Ottawa - Canada Breunig, Adriano - CEFET-MT - Brazil Bononi, Luciano - University of Bologna - Italy Boukerche, Azzedine - University of Ottawa - Canada Calamoneri, Tiziana - University of Rome "La Sapienza" - Italy Camargo, Jo=E3o Batista - USP - Brazil Castro, Julio Cesar Hern=E1ndez - Universidad Carlos III - Spain Correa, Ghilson Ramalho - CEFET-MT - Brazil Correa, Pedro Luiz Pizzigatti - USP - Brazil Cruz, Fernando Augusto da Silva - UFSC - Brazil Dantas, Mario Ant=F4nio Ribeiro - INE/UFSC - Brazil Gondim, Paulo Roberto de Lira - UnB - Brazil Fortes, Renata Pontin M. - ICMC/USP - Brazil Filho, Bartolomeu Uch=F4a - EEL/UFSC, Brazil Greve, Fab=EDola Gon=E7alves Pereira - UFBA - Brazil Guardia, H=E9lio Crestana - UFSCar - Brazil Ionescu, Dan - University of Ottawa - Canada Jardini, Jos=E9 Antonio - USP - Brazil Karatza, Helen - University of Thessaloniki - Greece Kurt, Akif - Istanbul University - Turkey Martinez, Jeimy Jos=E9 Cano - Uniandes - Col=F4mbia Martins, Ronan Marcelo - CEFET-MT - Brasil Mateus, Geraldo Robson - DCC/UFMG - Brazil Mello, Rodrigo Fernandes - ICMC/USP - Brazil Melo, Alba Cristina Magalh=E3es Alves - UnB Brazil Min, Geyong - University of Bradford - UK Moreira, Edson dos Santos - ICMC/USP - Brazil Narasimhan, Lakshmi - University of Newcastle - Australia Nikoleletseas, Sotiris E. - Computer Technology Institute - Greece Notare, Mirela Sechi Moretti Annoni - Barddal University - Brazil Oliveira, Ruy - CEFET-MT - Brazil Ould-Khaoua, Mohamed M. - University of Glasgow - UK Pacheco, Roberto - UFSC - Brazil Paris, Jehan-Fran=E7ois - University of Houston - USA Penna, Manoel Camillo de Oliveira Neto - PUC/PR - Brazil Pizzolato, Ednaldo Briganti - UFSCar - Brazil Puttini, Ricardo Staciarini - UnB - Brazil Riso, Bernardo Gon=E7alves - UFSC - Brazil Rocha, Carlos Aurelio Faria da - EEL/UFSC - Brazil Silva, Jorge S=E1 - DEI/UC - Portugal Sklavos, Nicolas - Technological Educational Institute of Messolonghi -=20 Greece Sobral, Jo=E3o Bosco Mangueira - UFSC - Brazil Souza, Patr=EDcia Cristiane de - UFMT - Brazil Souza Jr., Rafael Tim=F3teo - UnB - Brazil Trevelin, Luis Carlos - USCar - Brazil Villalba, Luis Javier Garc=EDa - Universidad Complutense de Madrid - Spai= n Wangham, Michelle - Barddal - Brazil Zomaya, Albert - University of Sydney - Australia ORGANIZING COMMITTEE Lucas Guardalben - PPGCC-UFSC - Brazil Joelson de Alencar Degaspari - PPGCC-UFSC - Brazil Claudio Jos=E9 Biazus - PPGCC-UFSC - Brazil Igor Vinicius Mussoi de Lima - PPGCC-UFSC - Brazil Mario Pereira Guitte -UNIVAG - Brazil Rosana Ravache - UNIVAG - Brazil M=E1rcia Ribeiro - UNIVAG - Brazil Kenji Kido - UNIVAG - Brazil Koga, Miguel - UNEMAT - Brazil LOCAL ARRANGEMENT CHAIR Fernando Marcos Bonnemasou Moreira de Castilho - UNIVAG - Brazil PUBLICITY COMMITTEE Francisco J. A. de Aquino, EEL-UFSC - Brazil Cristiano Maciel - IC-UFF/RJ - Brazil Renato Bobsin Machado - UNIOESTE/PR - Brazil Jo=E3o Paulo Delgado Preti - CEFET/MT - Brazil Metuzalen Gon=E7alves Silva - UNEMAT - Brazil Robson Gomes de Melo - UNEMAT - Brazil ADVISORY BOARD COMMITTEE Azzedine Boukerche - University of Ottawa - Canada Antonio Alfredo F. Loureiro - UFMG - Brazil Bernardo Gon=E7alves Riso - UFSC - Brazil Manoel Camillo de Oliveira Penna Neto - PUC/PR - Brazil STEERING COMMITTEE CO-CHAIRS Azzedine Boukerche - University of Ottawa - Canada Mirela Sechi Moretti Annoni Notare - Barddal University - Brazil FURTHER INFORMATION For additional information, please send an e-mail to Prof. Mirela Secchi Annoni Moretti Notare (mirela@barddal.br) or Prof. Prof. Jo=E3o Bosco Mangueira Sobral (bosco@inf.ufsc.br) Updated conference announcement and information are accessible at the symposium home page at www.inf.ufsc.br/i2ts2006. --------------------------------------------------------------=20 --=20 Esta mensagem foi verificada pelo sistema de antiv=EDrus e acredita-se estar livre de perigo. _______________________________________________ Researchers mailing list Researchers@mailman.ufsc.br http://mailman.ufsc.br/mailman/listinfo/researchers -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Thu Oct 05 11:27:53 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVV8T-00010u-5e; Thu, 05 Oct 2006 11:27:45 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVF4U-0000bG-AW; Wed, 04 Oct 2006 18:18:34 -0400 Received: from demokritos1.cytanet.com.cy ([195.14.130.225]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVF4L-0007WY-O2; Wed, 04 Oct 2006 18:18:34 -0400 Received: from [192.168.0.101] (unknown [87.228.217.49]) by demokritos1.cytanet.com.cy (Postfix) with ESMTP id 8EF3247F67; Thu, 5 Oct 2006 01:18:02 +0300 (EEST) From: Christos Panayiotou To: Christosp@ucy.ac.cy Content-Type: text/plain Organization: University of Cyprus Date: Thu, 05 Oct 2006 01:21:43 +0300 Message-Id: <1160000504.7826.96.camel@ECELP09> Mime-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: 7bit X-Virus-Scanned: By virus scanner at Cytanet X-Spam-Score: 1.8 (+) X-Scan-Signature: b22590c27682ace61775ee7b453b40d3 X-Mailman-Approved-At: Thu, 05 Oct 2006 11:27:44 -0400 Cc: Subject: [Mip4] WiOpt'07 Deadline Extension X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org WiOpt07: Call for Papers 5th Intl. Symposium on Modeling and Optimization in Mobile, Ad Hoc, and Wireless Networks http://www.wiopt.org April 16-20, 2007, Limassol, Cyprus ****New Submission Deadline is October 16, 2006 **** Scope of the Symposium =================================== The design of wireless networks offers challenges not present in fixed networks: both the offered traffic and the network capacity depend on the mobility of the nodes. The designs should not only be functioning correctly, they are also expected to optimize the performance with respect to many criteria, such as energy efficiency, quality of service, and capacity utilization. This symposium intends to bring together researchers and practitioners working on optimization of wireless network design and operations. It welcomes different perspectives, including performance analysis, protocol design, wireless communication, and optimization theory. Contributions to this conference should improve the state-of-the-art in design, analysis, dimensioning and operations of wireless network by providing insights into theoretical aspects as well as providing practical methods and tools. All forms of wireless networks are of interest: from cellular wide-area and local-area networks to dense and sparse ad-hoc networks; domain specific vehicular, public-transport and personal-area networks as well as application-specific sensor networks. Topics of interest include, but are not limited to: +++++++++++++++++++++++++++++++++++++++++++++++++++ ** Modeling of mobility and its influence on systems performance ** Approaches to dynamic spectrum allocation ** Interference control for unlicensed spectral bands ** Effective techniques for simulation of large wireless networks ** Delay and disruption tolerant wireless communication ** Fundamental performance limits ** Analysis and modeling based on measurements ** Protocol design for optimal system performance ** Pricing and incentives in mobile and ad-hoc networks ** Security and co-operation models and analysis ** Optimization techniques for performance, scalability and manageability ** Energy efficiency in mobile and sensor networks ** Measures of quality with associated performance evaluation Submissions ============ Papers should be submitted as extended abstracts of up to 8 pages with single column format and one-and-a-half line spacing, and contain sufficient information to allow for a detailed review. Papers should be submitted in pdf or ps format (see the conference website www.wiopt.org for details). The final manuscript will be 10 pages in double column format. The proceedings will be published by IEEE and accepted papers will be available online via the IEEE website. Adjunct Workshops ================== Several one-day workshops will accompany the main WiOpt Symposium: *** WiNMee/WiTNeMo 2007 : International Workshop on Wireless Network Measurements *** RAWNET 2007 : Resource Allocation in Wireless Networks *** SPASWIN 2007: Spatial Stochastic Models for Wireless Networks *** CONCOM 2007 : Control over Communication Channels *** WNC3 2007 : Wireless Networks: Communication, Cooperation and Competition Important Dates =============== Submission deadline: October 16, 2006 Notification of acceptance: December 18, 2007 Camera-ready copy: January 19, 2007 Steering Committee ================== Imrich Chlamtac, CREATE-NET Italy Eitan Altman, INRIA, France Tamer Basar, UIUC,USA Jon Crowcroft, Cambridge Univ, UK Anthony Ephremides, Univ. of Maryland, USA Daniele Miorandi, CREATE-NET, Italy Organizing Committee ==================== General Chair: *Leandros Tassiullas, Univ. of Thessally, Greece Technical Program Co-Chairs *Leonidas Georgiadis, Aristotle Univ. Greece *Gunnar Karlsson, KTH, Stockholm, Sweden General Vice Chair *Andreas Pitsillides, University of Cyprus Local Arrangements Chair *Stavros Toumpis, University of Cyprus Finance Chair *Karen Decker, ICST Workshops Chair *C. D. Charalambous, University of Cyprus Publicity Chair *Christos Panayiotou, University of Cyprus Conference Coordinator *Zsuzsanna Lanyi-Kaszab, ICST Sponsorship =========== Wiopt'07 is co-sponsored by Create-net, ICST, IFIP TC6.3, IEEE Information Theory, Control and Communications Societies (approval pending) -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Mon Oct 09 09:50:45 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GWvWn-0003xG-NW; Mon, 09 Oct 2006 09:50:45 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVxwP-0002bt-As for mip4@ietf.org; Fri, 06 Oct 2006 18:13:13 -0400 Received: from smtp1.utdallas.edu ([129.110.10.12]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVxwO-0003WE-26 for mip4@ietf.org; Fri, 06 Oct 2006 18:13:13 -0400 Received: from [129.110.90.20] (canavar.utdallas.edu [129.110.90.20]) by smtp1.utdallas.edu (Postfix) with ESMTP id C33BD388F8C for ; Fri, 6 Oct 2006 17:13:11 -0500 (CDT) Message-ID: <4526D4F7.9030100@utdallas.edu> Date: Fri, 06 Oct 2006 17:13:11 -0500 From: Kamil Sarac User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: mip4@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 X-Mailman-Approved-At: Mon, 09 Oct 2006 09:50:44 -0400 Subject: [Mip4] Call for participation for IEEE ICNP 2006 conference X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org (This message is sent to multiple lists. Our apologies if you receive multiple copies of it.) Dear Colleagues, Please note that the early registration deadline and the deadline for hotel reservations at a discounted rate are October 13, 2006 (only 7 days left!). ===================================================================== Call For Participation 14th IEEE International Conference on Network Protocols http://www.ieee-icnp.org/2006 Santa Barbara, California, USA November 12-15, 2006 Sponsored by: IEEE (Computer Society), NSF CISE/CNS, HP, Microsoft, University of California--Santa Barbara Important Dates =============== Early Registration and Hotel Block Deadlines: October 13, 2006 Student Travel Award Application Deadline: September 29, 2006 Minority Faculty Travel Award Application Deadline: September 29, 2006 Highlights of ICNP 2006 ======================= * Keynote talk by Dr. Wei Zhao, Division Director of Computer and Network Systems (CNS) at the National Science Foundation, and Senior Associate Vice President for Research at Texas A&M University, "Challenges and Opportunities of IT Education and Research" * Presentations of technical papers in nine sessions + P2P Applications + Network Security + Routing of Wireless Networks + Protocol Design and Routing + Security Issues + Wireless and Sensor Networks + File Sharing and Overlay Networks + BGP and Traffic Engineering + Wireless Networks The details of the full technical program can be viewed at: http://www.ieee-icnp.org/2006/program.html * The Second Workshop on Secure Network Protocols (NPSec). See: http://www.ics.uci.edu/NPSec-06/ * Student work-in-progress poster session. See: http://www.ieee-icnp.org/2006/poster.html ===================================================================== -- Kamil Sarac Assistant Professor Department of Computer Science The University of Texas at Dallas Richardson, TX 75083-0688 Phone: (972) 883 2337 Fax: (972) 883 2349 Email: ksarac@utdallas.edu Web: www.utdallas.edu/~ksarac -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Tue Oct 10 01:23:02 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXA4d-00087n-2w; Tue, 10 Oct 2006 01:22:39 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXA4a-000868-V1 for mip4@ietf.org; Tue, 10 Oct 2006 01:22:36 -0400 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXA4X-0004at-6Y for mip4@ietf.org; Tue, 10 Oct 2006 01:22:36 -0400 Received: from c2-vpn07.isi.edu (c2-vpn07.isi.edu [128.9.176.224]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id k9A5LZ6l015740 for ; Mon, 9 Oct 2006 22:21:35 -0700 (PDT) From: Wei Ye To: mip4@ietf.org Content-Type: text/plain; charset=UTF-8 Date: Mon, 09 Oct 2006 22:21:36 -0700 Message-Id: <1160457697.2864.16.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 (2.6.3-1.fc5.5) X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: weiye@isi.edu Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by boreas.isi.edu id k9A5LZ6l015740 X-Spam-Score: 0.6 (/) X-Scan-Signature: af2aae76ea468dc53420d9ba52ca6045 Subject: [Mip4] ACM SenSys'06 call for participation X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Our apologies if you have received multiple copies. --------------- The cut-off date for ACM SenSys 2006 hotels is extended to=20 *Friday October 13*. Rooms are now only available at the=20 conference rates at:=20 The Hotel Boulderado http://www.boulderado.com/ The Boulderado is located next to the Perl Street walking mall=20 in the heart of Boulder. Rate: $129/night Address: 2115 13th Street Boulder, CO, USA 80302 Tel:800.433.4344 303.442.4344 The St Julien Hotel http://www.stjulien.com/ The St Julien is located next to the Pearl Street walking mall in=20 the heart of Boulder; the hotel has a view of the Flatiron Mountains. Rate: $185/night Address: 900 Walnut Street Boulder, CO, USA 80302-6899 Tel: 720.406.9696 877.303.0900 --------------- ACM SenSys 2006 - Call for Participation The 4th ACM Conference on Embedded Networked Sensor Systems http://sensys.acm.org/2006/ Boulder, Colorado, USA October 31 - November 3, 2006 In the short period since its inception in Los Angeles in 2003, SenSys has risen to become the leading forum for reporting on new, exciting, and technically important research in the field of sensor networks. Please note that the cut off dates for the conference hotels and early registration are September 29 and October 30, respectively. This year we have a stellar conference for you that includes: * A keynote by David Carlson Director, International Polar Year Program Office, and formally, Director of the Atmospheric Technology Division of the US National Centre for Atmospheric Research (NCAR). * 24 technical papers * 29 Sensor network demos * 19 Posters - representing early results and work-in-progress * 2 one day workshops on emerging and important new topics in sensor networks. The workshops will be held the day prior to the main technical program + First Workshop on World-Sensor-Web: Mobile Device Centric Sensory Networks and Applications http://www.sensorplanet.org/wsw2006/ + First Workshop on Distributed Smart Cameras http://www.iti.tugraz.at/dsc06/ Registration is now open: http://www.regonline.com/Checkin.asp?EventId=3D97157 Important Dates: Cut off date for reduced hotel rates is *September 29, 2006* Cut off date for early registration is *October 30, 2006* Please book and register today to guarantee the best rates. One behalf of the whole organizing team we very much look forward to seeing you at SenSys in Boulder! Best regards, Andrew T. Campbell SenSys 2006 General Chair Thanks to our sponsors: ACM SIGCOMM, SIGMOBILE, SIGARCH, SIGOPS, SIGMETRICS, SIGBED NSF, NCAR, ISTS, Crossbow, Intel, Microsoft Research, Moteiv, Nokia Below you'll find the technical program. Please go to http://sensys.acm.org/2006/ for more information. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D **Technical Program, Demos, and Posters** =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Wednesday, November 1 08:15-08:30 Opening announcements 08:30-10:00 Keynote David Carlson Director, International Polar Year Program Office 10:00-10:30 Break 10:30-12:00 Operating Systems t-kernel: Providing Reliable OS Support to Wireless Sensor Networks Lin Gu, John A. Stankovic (University of Virginia) Run-time Dynamic Linking for Reprogramming Wireless Sensor Networks Adam Dunkels, Niclas Finne, Joakim Eriksson, Thiemo Voigt (Swedish Institute of Computer Science) Protothreads: Simplifying Event-Driven Programming of Memory- Constrained Embedded Systems Adam Dunkels, Oliver Schmidt, Thiemo Voigt (Swedish Institute of Computer Science), Muneeb Ali (TU Delft) 12:00-13:30 Lunch 13:30-14:30 Sensing Capturing High-Frequency Phenomena Using a Bandwidth-Limited Sensor Network Ben Greenstein, Christopher Mar, Alex Pesterev, Shahin Farshchi, Eddie Kohler, Jack Judy, Deborah Estrin (UCLA) Virtual High-resolution for Sensor Networks Aman Kansal, William J. Kaiser, Gregory J. Pottie, Mani B. Srivastava (UCLA) and Gaurav Sukhatme (USC) 14:30-15:00 Break 15:00 -16:30 Routing and Dissemination RBP: Robust Broadcast Propagation in Wireless Networks Fred Stann (Amgen), John Heidemann, Rajesh Shroff, Muhammad Zaki Murtaza (USC/ISI) Interest Dissemination with Directional Antenna for Wireless Sensor Networks with Mobile Sinks Yihong Wu, Xiaobo Chen, Lin Zhang, Zhisheng Niu (Tsinghua University) Lazy Cross-Link Removal for Geographic Routing Young-Jin Kim, Ramesh Govindan (USC), Brad Karp (University Colledge London), Scott Shenker (UCB) **19.00 Banquet at the Walnut Brewery Boulder's Original Brew Pub 1123 Walnut Street** Thursday, November 2 09:00-10:00 Configuration StarDust: A Flexible Architecture for Passive Localization in Wireless Sensor Networks Radu Stoleru, Pascal Vicaire, Tian He, John A. Stankovic (University of Virginia) The Design and Implementation of a Self-Calibrating Distributed Acoustic Sensing Platform Lewis Girod (MIT/CSAIL), Martin Lukac, Vlad Trifa, Deborah Estrin (UCLA) 10:00-10:30 Break 10:30-11:30 In-network Processing Target Tracking with Binary Proximity Sensors: Fundamental Limits, Minimal Descriptions, and Algorithms Nisheeth Shrivastava, Raghuraman Mudumbai, Upamanyu Madhow, Subhash Suri (UCSB) Data Compression Algorithms for Energy-Constrained Devices in Delay Tolerant Networks Christopher M. Sadler, Margaret Martonosi (Princeton University) 11:30-13:00 Lunch 13:00-14:30 Radio Propagation and Transport Datalink Streaming in Wireless Sensor Networks Raghu K. Ganti, Praveen Jayachandran, Tarek F. Abdelzaher, and Haiyun Luo (UIUC) ATPC: Adaptive Transmission Power Control for Wireless Sensor Shan Lin (University of Virginia), Tian He (University of Minnesota), Jingbin Zhang, Gang Zhou, Lin Gu, John A. Stankovic (University of Virginia) Experimental Study of Concurrent Transmission in Wireless Sensor Networks Dongjin Son, Bhaskar Krishnamachari (USC), John Heidemann (USC/ISI) 14:30-15:00 Break 15:00-16:30 Storage and Abstractions Abstractions for Safe Concurrent Programming in Networked Embedded Systems William P. McCartney, Nigamanth Sridhar (Cleveland State University) Scalable Data Aggregation for Dynamic Events in Sensor Networks Kai-Wei Fan, Sha Liu, Prasun Sinha (The Ohio State University) An Energy-Optimized Object Storage System for Memory-Constrained Sensor Devices Gaurav Mathur, Peter Desnoyers, Deepak Ganesan, Prashant Shenoy (University of Massachusetts, Amherst) 16:30-20:00 Demonstration and poster session List of accepted demonstrations and posters http://sensys.acm.org/2006/demo_poster.html 20:00-21:00 TinyOS Alliance BoF Friday, November 3 08:30-10:00 Architecture CarTel: A Distributed Mobile Sensor Computing System Bret Hull, Vladimir Bychkovsky, Yang Zhang, Kevin Chen, Michel Goraczko, Allen Miu, Eugene Shih, Hari Balakrishnan, Samuel Madden (MIT/CSAIL) MELETE: Supporting Concurrent Applications in Wireless Sensor Networks Yang Yu, Loren Rittle (Motorola Labs), Jason LeBrun (UCD), Vartika Bhandari (UIUC) The Tenet Architecture for Tiered Sensor Networks Omprakash Gnawali (USC), Ben Greenstein (UCLA), Ki-Young Jang (USC), August Joki (UCLA), Jeongyeup Paek, Marcos Vieira (USC), Deborah Estrin (UCLA), Ramesh Govindan (USC), Eddie Kohler (UCLA) 10:00-10:30 Break 10:30-12:00 Media Access Control Funneling-MAC: A Localized, Sink-Oriented MAC for Boosting Fidelity in Sensor Networks Gahng-Seop Ahn (Columbia University), Emiliano Miluzzo, Andrew T. Campbell (Dartmouth College), Se Gi Hong (Columbia University), Francesca Cuomo (University of Rome "La Sapienza") X-MAC: A Short Preamble MAC Protocol for Duty-Cycled Wireless Sensor Networks Michael Buettner, Gary V. Yee, Eric Anderson, Richard Han (University of Colorado, Boulder) Ultra-Low Duty Cycle MAC with Scheduled Channel Polling Wei Ye, Fabio Silva, John Heidemann (USC/ISI) 12:00-12:15 Best Talk Award and Closing =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ***************DEMOS********************* =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D SignetLab: Deployable Sensor Network Testbed and Management Tool Riccardo Crepaldi, Albert F Harris III, Alberto Scarpa, Andrea Zanella, Michele Zorzi (University of Padova) An Eventual Consistent Wireless Light Control System Jeonghoon Kang (Korea Electronics Technology Institute), Alec Woo (Arch Rock), Junejae Yoo, Myunghyun Yoon (Korea Electronics Technology Institute) Data Analysis Tools for Sensor-Based Science Stuart Ozer (Microsoft Research), Alex Szalay (Johns Hopkins University), Jim Gray (Microsoft Research), Andreas Terzis, Razvan Musaloiu-E., Katalin Szlavecz, Josh Cogan, Randal Burns (Johns Hopkins University) Data Collection in Delay Tolerant Mobile Sensor Networks using SCAR Cecilia Mascolo, Mirco Musolesi, Bence Pasztor (University College London) cCAM: Ultra Compact, High Data-Rate Wireless Sensor Node with a Miniature Camera Chulsung Park, Pai H. Chou (UCI) Using Grid Technologies to Optimise a Wireless Sensor Network for Flood Management Danny Hughes, Phil Greenwood, Geoff Coulson, Gordon Blair, Barry Porter, Paul Grace, Florian Pappenberger, Paul Smith, Keith Beven (Lancaster University) A Funneling-MAC for High Performance Data Collection in Sensor Networks Gahng-Seop Ahn (Columbia University) Emiliano Miluzzo, Andrew T. Campbell (Dartmouth College) A Storage-centric Camera Sensor Network Gaurav Mathur, Paul Chukiu, Peter Desnoyers, Deepak Ganesan, Prashant Shenoy (University of Massachusetts) Real-Time Volcanic Earthquake Localization Geoffrey Werner-Allen, Patrick Swieskowski, Matt Welsh (Harvard University) Low Power, Low Cost, Wireless Camera Sensor Nodes For Human Detection Jason Schlessman, Jaechang Shim, Ikdong Kim, Yun Cheol Baek, Wayne Wolf (Princeton University) A Unified Architecture for Flexible Radio Power Management in Wireless Sensor Networks Kevin Klues, Guoliang Xing, Chenyang Lu (Washington University) A Self-Calibrating Distributed Acoustic Sensing Platform Lewis D Girod (MIT/CSAIL), Martin Lukac (UCLA), Vladimir Trifa (EPFL), Deborah Estrin (UCLA) A Virtualizing OS Kernel for Wireless Sensor Networks Lin Gu, John A Stankovic (University of Virginia) Flexible Hardware/Software Platform for Tracking Applications Junaid Ansari, Jos=C3=83=C2=A9 S=C3=83=C2=A1nchez, Marina Petrova, Janne = Riihij=C3=83=C2=A4rvi, Ossi Raivio, Krisakorn Rerkrai, Chirstine Jardak, Frank Oldewurtel, Mathias Wellens, Lili Wu, Petri M=C3=83=C2=A4h=C3=83=C2=B6nen (RWTH Aachen Univer= sity) Simple Sensor Syndiciation Michael Colagrosso, Wade Simmons, Marianne Graham (Colorado School of Mines) Responsive and Energy-Efficient Sensor Networking for Real Time Location Tracking Henoc Agbota, Mike Hazas (Lancaster University) Demonstrating Distributed Signal Strength Location Estimation Neal Patwari (University of Utah), Alfred O. Hero (University of Michigan) Sensing and Reproducing the Shapes of 3D Objects Using Claytronics Padmanabhan Pillai, Jason Campbell (Intel Research Pittsburgh) Cascades: An Extensible Heterogeneous Sensor Networking Framework Phillip Sitbon, Nirupama Bulusu, Wu-Chi Feng (Portland State University) LiteOS - A Lightweight Operating System for C++ Software Development in Sensor Networks Qing Cao, Tarek Abdelzaher (UIUC) GRAIL: General Real-Time Adaptable Indoor Localization Yingying Chen (Rutgers University), Eiman Elnahrawy (Kordinate LLC), John-Austen Francisco, Konstantinos Kleisouris (Rutgers University), Xiaoyan Li (Lafayette College), Hongyi Xue (Rutgers University), Richard P. Martin (Rutgers University and Kordinate LLC) A Hierarchical Location Directory Service Across Sensor and IP Networks Sangeeta Bhattacharya, Chien-Liang Fok, Chenyang Lu, Gruia-Catalin Roman (Washington University) Software Radio Implementation of Short-range Wireless Standards for Sensor Networking Thomas Schmid, Tad Dreier, Mani B. Srivastava (UCLA) The CarTel Mobile Sensor Computing System Vladimir L Bychkovsky, Kevin Chen, Michel Goraczko, Hongyi Hu, Bret W Hull, Allen K Miu, Eugene I Shih, Yang Zhang (MIT) TOSDev: A Rapid Development Environment for TinyOS William P McCartney, Nigamanth Sridhar (Cleveland State University) Step-wise Context Extraction in AoK Mule System Yuichi Uehara, Masato Mori, Nayuta Ishii (Tokyo Denki University), Yoh Shiraishi (The University of Tokyo) Yoshito Tobe (Tokyo Denki University) SensorMap: A Web Site for Sensors World-Wide Suman Nath, Jie Liu, Jessica Miller, Feng Zhao (Microsoft Research), Andre Santanche (UNICAMP) Mobility Centric Campus Area Sensor Network for Locality Specific Applications Mukundan Sridharan, Anish Arora, Rajiv Ramnath, Emre Ertin (The Ohio State University) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ***************Posters******************* =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Routing and Processing Multiple Aggregate Queries in Sensor Networks Niki Trigoni, Alexandre Guitton, Antonios Skordylis (University of London) Rateless Codes for Data Dissemination in Sensor Networks Andrew Hagedorn, David Starobinski, Ari Trachtenberg (Boston University) AMSecure: Secure Link-Layer Communication in TinyOS for IEEE 802.15.4- based Wireless Sensor Networks Anthony D Wood, John A Stankovic (University of Virginia) Virtual Sensing Range Emiliano Miluzzo, Nicholas D Lane, Andrew T Campbell (Dartmouth College) uScan: A Lightweight Two-Tier Global Sensing CoverageDesign Yu Gu, Tian He (University of Minnesota) SkiScape Sensing Shane B. Eisenman (Columbia University), Andrew T. Campbell (Dartmouth College) Channel Surfing: Defending WirelessSensor Networks from Jamming and Interference Wenyuan Xu, Wade Trappe, Yanyong Zhang (Rutgers University) Energy Adaptation Techniques to Optimize Data Delivery in Store-and- Forward Sensor Networks Pei Zhang, Margaret Martonosi (Princeton Unviersity) A Distributed Reliable Data Transport Strategy for Event Based Wireless Sensor Networks Yuyan Xue, Byrav Ramamurthy, Ying Lu (University of Nebraska - Lincoln) Lowering Radio Duty Cycle Through Temperature Compensated Timing Joakim Arfvidsson, Eric Park, Philip Levis (Stanford University) Collaborative Scheduling of Event Types and Allocation of Rates for Wireless Sensor Nodes with Multiple Sensing Units Hidayet Ozgur Sanli, Hasan Cam (Arizona State University) Kaizen: Improving Sensor Network Operating Systems James Horey, Jean-Charles Tournier, Arthur B Maccabe (University of New Mexico) Achieving Realistic Sensing Area Modeling Joengmin Hwang, Tian He, Yongdae Kim (University of Minnesota) Is Data-Centric Storage and Querying Scalable? Joon Ahn, Bhaskar Krishnamachari (USC) Understanding the Causes of Packet Delivery Success and Failure in Dense Wireless Sensor Networks Kannan Srinivasan (Stanford University), Prabal Dutta, Arsalan Tavakoli (UCB), Philip Levis (Stanford University) WaveScope: A Signal-Oriented Data Stream Management System Lewis Girod, Kyle Jamieson, Yuan Mei, Ryan Newton, Stanislav Rost, Arvind Thiagarajan, Hari Balakrishnan, Samuel Madden (MIT/CSAIL) Comprehensive Monitoring of CO2 Sequestration in Subalpine Forest Ecosystems and its Relation to Global Warming Lynette L. Laffea, Russ K. Monson, Ryan Manning, Ashly Glasser, Richard Han (University of Colorado, Boulder), Steve Oncley, Jielun Sun, Sean Burns, Steve Semmer, John Militzer (NCAR) TINX A Tiny Index Design for Flash Memory on Wireless Sensor Devices Ajay Mani, Manjunath B Rajashekhar, Philip Levis (Stanford University) Wireless Sensor Networks for Structural Health Monitoring Sukun Kim, Shamim Pakzad, David Culler, James Demmel, Gregory Fenves, Steve Glaser (UCB), Martin Turon (Crossbow) -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Tue Oct 10 15:57:13 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXNiv-0004RH-1a; Tue, 10 Oct 2006 15:57:09 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXN99-0006mK-2j for mip4@ietf.org; Tue, 10 Oct 2006 15:20:11 -0400 Received: from dynamo.ecn.purdue.edu ([128.46.200.24]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXN95-00049R-N1 for mip4@ietf.org; Tue, 10 Oct 2006 15:20:11 -0400 Received: from [10.80.19.254] ([216.154.205.203]) (authenticated bits=0) by dynamo.ecn.purdue.edu (8.13.6/8.13.6) with ESMTP id k9AJJxA5005565 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Tue, 10 Oct 2006 15:20:05 -0400 (EDT) Message-ID: <452BF267.60104@ecn.purdue.edu> Date: Tue, 10 Oct 2006 15:20:07 -0400 From: Vijay Raghunathan User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: mip4@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned-ECN: by amavisd-new X-ECN-Spam-Status: No X-Spam-Score: 0.0 (/) X-Scan-Signature: d16ce744298aacf98517bc7c108bd198 X-Mailman-Approved-At: Tue, 10 Oct 2006 15:57:06 -0400 Subject: [Mip4] IEEE SECON 2007: Call for papers X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org ** Apologies if you receive multiple copies of this call for papers ** ======================================================================== CALL FOR PAPERS IEEE SECON 2007 The Fourth IEEE Communications Society Conference on Sensor, Mesh and Ad Hoc Communications and Networks http://www.ieee-secon.org/2007/ Merged with IEEE International Workshop on Wireless Ad-hoc & Sensor Networks (IWWAN) San Diego, California, USA June 18-21, 2007 ======================================================================== The fourth annual IEEE SECON conference will provide a unique forum to exchange ideas, techniques, and applications, discuss best practices, raise awareness, and share experiences among researchers, practitioners, standard developers and policy makers in the field of sensor, ad-hoc, and mesh networks and systems. IEEE SECON grew out of IEEE INFOCOM in 2004, in order to create an event that focused on the important and exciting topics of sensor, mesh and ad-hoc communications and networks. This year, SECON has been merged with the IEEE International Workshop on Wireless Ad-hoc and Sensor Networks (IWWAN). Original technical papers that address the communications, networking, applications, systems and algorithmic aspects of mesh and sensor networks, as well as those that describe practical deployment and implementation experiences are solicited for presentation at the conference and publication in the conference proceedings. Papers presenting novel contributions in such disciplines as communications, networking protocols and architectures, algorithms, embedded systems, middleware and information management, and novel applications are solicited. PAPERS: Full papers describing original, previously unpublished research work, experimental efforts, practical experiences, and industrial and commercial developments in sensor, ad-hoc, and mesh communications and networks are solicited. Authors are particularly encouraged to submit papers that have a deep focus on a specific discipline, are stimulated by the synergistic interaction of diverse disciplines, or describe practical application of technology to real-world problems. Submitted papers should not be concurrently under review at any another workshop, symposium, conference, or journal. Specific topics of interest include, but are not limited to: * Architectures and protocols to support wireless communication, localization, time synchronization, routing, data dissemination, and other distributed services in heterogeneous, large-scale, distributed mesh and sensor networks. * Algorithms and theories for management, supervisory control, and monitoring of distributed ad-hoc networks, and techniques for the interpretation and use of sensor data in decision-making processes. * Theories and models on fundamental information and communication aspects of wireless mesh and sensor networks. * Mechanisms for authenticated, secure communication and data dissemination in sensor and mesh networks. * Algorithms and protocols to support quality of service in mesh and sensor networks, including admission control, resource allocation and fairness, and capacity planning. * Performance measurement and modeling techniques for large-scale distributed ad-hoc and sensor networks and their evaluation. * Integration of sensors into engineered systems, including techniques for exploiting on-sensor renewable power sources, mechanisms for online self-calibration and self-testing, and schemes to maximize accuracy and minimize false alarms. * Hardware platforms and testbeds incorporating multiple sensors, embedded processors, actuators, and wireless interfaces. * Software architectures, middleware, and tools for mesh and sensor network applications development, deployment, and management. * Practical implementations, case-studies, and real-world experiences in designing and deploying large scale ad-hoc, mesh, and sensor network applications. POSTERS, DEMOS, AND EXHIBITS: SECON will also include poster/demo sessions that provide an interactive forum to present work in progress, showcase real system implementations, highlight industrial/commercial developments, and discuss key research challenges in the fields of sensor, mesh, and ad-hoc networks. Details about the poster and demo submission procedure will soon be available on the conference web site. PAPER SUBMISSION INSTRUCTIONS: Paper submissions will be handled electronically through the EDAS web based system. Details about the submission process including formatting instructions and templates will be available soon at the conference website located at http://www.ieee-secon.org/2007/. Accepted papers will be published in the conference proceedings and will be archived on IEEE Xplore. IEEE Communications Society policy mandates that all accepted SECON 2007 papers must have at least one associated registration at the regular rate. For authors co-authoring multiple papers, one regular registration is valid for up to three papers. IMPORTANT DATES: Paper registration: November 30, 2006 (by 11:59pm PST) Full paper submission: December 7, 2006 (by 11:59pm PST) Decision notification: February 26, 2007 Camera ready paper due: March 22, 2007 CONFERENCE ORGANIZING COMMITTEE: GENERAL CHAIR: Rene Cruz, UC San Diego (cruz@ece.ucsd.edu) VICE-CHAIR: Wendi Heinzelman, U. Rochester (wheinzel@ece.rochester.edu) TECHNICAL PROGRAM CO-CHAIRS: Kevin Almeroth, UC Santa Barbara (almeroth@cs.ucsb.edu) Robin Kravets, UIUC (rhk@cs.uiuc.edu) PUBLICITY CHAIR: Vijay Raghunathan, Purdue University LOCAL ARRANGEMENTS CHAIR: Curt Schurgers, UC San Diego PANELS CHAIR: Wenye Wang, NC State University WEB CHAIR: Navid Ehsan, UC San Diego STANDING COMMITTEE: Fred Bauer, PacketHop (fred@fredbauer.com) - Chair Harvey Freeman, Booz Allen Hamilton Sung-Ju Lee, HP Labs Prasant Mohapatra, University of California, Davis TECHNICAL PROGRAM COMMITTEE: To Be Announced ======================================================================== -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Tue Oct 10 19:24:29 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXQxU-0005hw-Vp; Tue, 10 Oct 2006 19:24:24 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXQxS-0005ha-AB; Tue, 10 Oct 2006 19:24:22 -0400 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXQxQ-0004cH-Uq; Tue, 10 Oct 2006 19:24:22 -0400 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k9ANOKF0002864; Tue, 10 Oct 2006 16:24:20 -0700 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k9ANOKUi002863; Tue, 10 Oct 2006 16:24:20 -0700 Date: Tue, 10 Oct 2006 16:24:20 -0700 Message-Id: <200610102324.k9ANOKUi002863@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 Cc: mip4@ietf.org, rfc-editor@rfc-editor.org Subject: [Mip4] RFC 4636 on Foreign Agent Error Extension for Mobile IPv4 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4636 Title: Foreign Agent Error Extension for Mobile IPv4 Author: C. Perkins Status: Standards Track Date: October 2006 Mailbox: charles.perkins@nokia.com Pages: 6 Characters: 11663 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mip4-faerr-02.txt URL: http://www.rfc-editor.org/rfc/rfc4636.txt This document specifies a new extension for use by Foreign Agents operating Mobile IP for IPv4. Currently, a foreign agent cannot supply status information without destroying the ability for a mobile node to verify authentication data supplied by the home agent. The new extension solves this problem by making a better place for the foreign agent to provide its status information to the mobile node. [STANDARDS TRACK] This document is a product of the Mobility for IPv4 Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Thu Oct 12 14:00:47 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY4rO-0004iE-Vn; Thu, 12 Oct 2006 14:00:46 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY4rO-0004i9-Eu for mip4@ietf.org; Thu, 12 Oct 2006 14:00:46 -0400 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY4rN-0000Yg-1y for mip4@ietf.org; Thu, 12 Oct 2006 14:00:46 -0400 Received: from wee.isi.edu (wee.isi.edu [128.9.168.112]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id k9CI0A2d015511 for ; Thu, 12 Oct 2006 11:00:10 -0700 (PDT) From: Wei Ye To: mip4@ietf.org Content-Type: text/plain; charset=UTF-8 Date: Thu, 12 Oct 2006 11:00:10 -0700 Message-Id: <1160676010.22612.44.camel@wee.isi.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 (2.6.3-1.fc5.5) X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: weiye@isi.edu Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by boreas.isi.edu id k9CI0A2d015511 X-Spam-Score: 0.0 (/) X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3 Subject: [Mip4] Call for participation: Workshop on World-Sensor-Web X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Our apologies if you have received multiple copies. --------------- WSW'2006 Workshop Program First Workshop on World-Sensor-Web: Mobile Device Centric Sensory =20 Networks and Applications Held in conjunction with ACM SenSys 2006 October 31, 2006 Boulder, Colorado, USA http://www.sensorplanet.org/wsw2006/ The global use of mobile phones on a scale never seen before enables =20 the development of new types of application scenarios. Furthermore, a =20 mobile device centric approach to large-scale sensory networks =20 provides a challenging platform for research purposes. Additionally, =20 connecting sensory networks to the Internet creates endless =20 opportunities for applications and services, new emerging models of =20 operation. The workshop aims to address these aspects, beside traditional =20 sensory network topics such as power management, communication =20 issues, topology management, distributed architectures, peer-to-peer =20 scenarios, etc. Demonstrations and initial ideas are welcome as well. Online Registration: http://www.regonline.com/Checkin.asp?EventId=3D97157 WORKSHOP CO-ORGANIZERS Henry Tirri, Nokia Research Center, Helsinki, Finland Barbara Heikkinen, Nokia Research Center, Helsinki, Finland Boda P=C3=A9ter, Nokia Research Center, Helsinki, Finland TECHNICAL PROGRAM COMMITTEE Joe Paradiso, MIT Media Laboratory, Cambridge, MA, USA Deborah Estrin, UCLA, Los Angeles, CA, USA Gaetano Borriello, University of Washington, Seattle, WA, USA Philippe Bonnet, University of Copenhagen, Copenhagen, Denmark Sam Madden, MIT CSAIL, Cambridge, USA Jukka Salminen, Nokia Research Center, Helsinki, Finland Dirk Trossen, Nokia Research Center, Helsinki, Finland Mika Klementtinen, Nokia Research Center, Helsinki, Finland Provisional WORKSHOP SCHEDULE 8:30-9:00am Registration 9:00-9:05am Welcome Position papers (20 min each followed by a 15 minutes discussion) 9:05-10:00am Participatory sensing Jeff Burke (UCLA) MetroSense Project: People-Centric Sensing at Scale Shane B. Eisenman =20 (Columbia University) Short papers (15 min each, discussion in the end of the session) 10:00am-12:00pm Relevance Metrics for Coverage Extension Using Community Collected =20 Cell-Phone Camera Imagery Aman Kansal (Microsoft) Challenges in Building a Portal for Sensors World-Wide Suman Nath (Microsoft) Indoor Positioning with a WLAN Access Point List on a Mobile Device Marion Hermersdorf (Nokia Research Center) Discussion 12:00-1:45pm Lunch 1:45-2:45pm Panel: "Grand challanges of mobile device-centric wireless sensor =20 networks" Participants: tba Short Papers (15 min each) 2:45-4:45pm Sensing in Rich Bluetooth Environments Jukka Perki=C3=B6 (HIIT / Nokia Research Center) Hash-based Secure Sensor Network Programming Method without Public =20 Key Cryptography Sokjoon Lee (Electronics and Telecommunications Research Institute, =20 Korea) Energy-Efficient Single-Hop Clustering in Mobile Wireless Sensor =20 Networks Chen Canfeng (Nokia Research Center) (3:30-4:00pm Coffee break) 4:45-6:00pm Locality Helps Sleep Scheduling Jukka Suomela (Helsinki University) The Case for Mobile Devices in Environmental Observing systems Sameer Tilak (UC San Diego) SensorPlanet update: the first islands Boda P=C3=A9ter P=C3=A1l (Nokia Research Center) Discussions, Follow-up, Closing the Workshop -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Thu Oct 12 14:05:57 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY4wP-0007ZT-6N; Thu, 12 Oct 2006 14:05:57 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY4wN-0007ZK-77 for mip4@ietf.org; Thu, 12 Oct 2006 14:05:55 -0400 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY4wL-0003LJ-Na for mip4@ietf.org; Thu, 12 Oct 2006 14:05:55 -0400 Received: from wee.isi.edu (wee.isi.edu [128.9.168.112]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id k9CI5HVX017113 for ; Thu, 12 Oct 2006 11:05:17 -0700 (PDT) From: Wei Ye To: mip4@ietf.org Content-Type: text/plain; charset=UTF-8 Date: Thu, 12 Oct 2006 11:05:17 -0700 Message-Id: <1160676317.22612.65.camel@wee.isi.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 (2.6.3-1.fc5.5) X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: weiye@isi.edu Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by boreas.isi.edu id k9CI5HVX017113 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576 Subject: [Mip4] Call for participation: Workshop on Distributed Smart Cameras X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Our apologies if you have received multiple copies. --------------- Workshop on Distributed Smart Cameras (DSC 2006) Program Held in conjunction with ACM SenSys 2006 October 31, 2006 Boulder, CO, USA http://www.iti.tugraz.at/dsc06/program.html Distributed smart cameras combine two concepts: physically =20 distributed cameras and distributed computing. Distributed smart =20 cameras are examples of high-performance multimedia sensor networks. =20 This area brings together researchers in image processing, sensor =20 networks, and embedded system architecture. Several groups are now working on distributed smart cameras, but =20 generally pursuing them in different research communities. This =20 meeting is the first event to bring together all the research groups =20 working on this problem Online Registration: http://www.regonline.com/Checkin.asp?EventId=3D97157 Workshop Co-Chairs B. Rinner, Graz University of Technology, Austria W. Wolf, Princeton University, USA Program Committee F. Berry, Univ. Clermont-Ferrand, France S. Bhattacharyya, U. Maryland, USA (email) M. Bove, MIT Media Lab, USA H. Garn, ARCS, Austria C. Guestrin, CMU, USA R. Kleihorst, Philips Research, The Netherlands X. Koutsoukos, Vanderbilt U., USA C. Regazzoni, Univ. Genova, Italy M. Srivastava, UCLA, USA W. Strasser, Univ. T=C3=BCbingen, Germany Program 08:30 - 09:00 Registration 09:00 - 09:15 Welcome 09:15 - 10:30 Session 1: Architectures Paul Nadrag, Antoine Manzanera, Nicolas Burrus Smart retina as a contour-based visual interface Stephan Hengstler, Hamid Aghajan A Smart Camera Mote Architecture for Distributed Intelligent =20 Surveillance Terrance E. Boult, R.C. Johnson, Tracy Pietre, R. Woodworth, Tao Zhang A Decade of Networked Intelligent Video Surveillance Richard Kleihorst, Ben Schueler, Alexander Danilin, Marc Heijligers SMART CAMERA MOTE WITH HIGH PERFORMANCE VISION SYSTEM Erik Ljung, Erik Simmons, Alexander Danilin, Richard Kleihorst, Ben =20 Schueler 802.15.4 Powered Distributed Wireless Smart Cameras Network Cintia B. Margi, Xiaoye Lu, Gefan Zhang, Roberto Manduchi, Katia =20 Obraczka Meerkats: A Power-Aware, Self-Managing Wireless Camera Network for =20 Wide Area Monitoring Pushkar Sambhoos, Ahmad Bilal, Richard Han, Tom Lookabaugh, Jane =20 Mulligan WeebleVideo \u2013 Wide Angle Field-of-View Video Sensor Networks 10:30 - 11:00 Coffee Break 11:00 - 12:15 Session 2: Localization & Calibration A.O. Ercan, A. El Gamal, L.J. Guibas Camera Network Node Selection for Target Localization in the Presence =20 of Occlusions Gurminder Singh and Mathias K=C3=B6lsch Resource Aggregation in Smart Sensor Systems Camillo J. Taylor, Babak Shirmohammadi Self Localizing Smart Camera Networks and their Applications to 3D =20 Modeling Dilip Sundarraj, Phillip B. Gibbons, Padmanabhan S. Pillai Ensuring Spatio-Temporal Consistency in Distributed Networks of Smart =20 Cameras John Jannotti, Jie Mao Distributed Calibration of Smart Cameras 12:15 - 14:00 Lunch Break 14:00 - 15:30 Session 3: Services Faisal Qureshi, Demetri Terzopoulos Virtual Vision and Smart Camera Networks Erik Simmons, Erik Ljung, Richard Kleihorst Distributed Vision with Multiple Uncalibrated Smart Cameras Johnny Park, Priya C. Bhat and Avinash C. Kak A Look-up Table Based Approach for Solving the Camera Selection =20 Problem in Large Camera Networks Mohammad Rahimi, Shaun Ahmadian, David Zats, Rafael Laufer, Deborah =20 Estrin Magic of Numbers in Network of Wireless Image Sensors Cheng-Yao Chen, Wayne Wolf An Activity Model of Distributed Smart Cameras Andreas Savvides, Eugenio Culurciello, Yiannis Aloimonos Demo presentation 15:30 - 16:00 Coffee Break 16:00 - 17:30 Session 4: Applications Thomas Haenselmann, Marcel Busse, Stephan Kopf, Thomas King, Wolfgang =20 Effelsberg Image Fusion from uncalibrated Video Sensor Arrays M. Quaritsch, M. Kreuzthaler, B. Rinner, B. Strobl Decentralized Object Tracking in a Network of Embedded Smart Cameras Arezou Keshavarz, Ali Maleki Tabar, Hamid Aghajan Distributed Vision-Based Reasoning for Smart Home Care Chen Wu, Hamid Aghajan Collaborative Gesture Analysis in Multi-Camera Networks Chung-Ching Chang, Hamid Aghajan Collaborative Face Orientation Detection in Wireless Image Sensor =20 Networks Vincent Jeanne, Francois-Xavier Jegaden, Richard Kleihorst, Alexander =20 Danilin, Ben Schueler REAL-TIME FACE DETECTION ON A \u201cDUAL-SENSOR\u201d SMART CAMERA USING SMOOTH =20 EDGES TECHNIQUE Ikdong Kim, Jaechang Shim, Jason Schlessman, Wayne Wolf Remote Wireless Face Recognition Employing ZigBee Adam Williams, Dan Xie, Shichao Ou, Roderic Grupen, Allen Hanson, and =20 Edward Riseman Distributed Smart Cameras for Aging in Place 17:30 - 18:15 Session 5: Panel -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Fri Oct 13 07:37:45 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GYLM0-0000G3-LT; Fri, 13 Oct 2006 07:37:28 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GYLLy-0000BL-OL for mip4@ietf.org; Fri, 13 Oct 2006 07:37:26 -0400 Received: from airmail.airvananet.com ([12.6.244.34] helo=airmail.wirelessworld.airvananet.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GYLLv-0005St-EK for mip4@ietf.org; Fri, 13 Oct 2006 07:37:26 -0400 Received: from nilgiri.india.wirelessworld.airvananet.com ([192.168.51.3]) by airmail.wirelessworld.airvananet.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 13 Oct 2006 07:36:34 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 13 Oct 2006 17:06:30 +0530 Message-ID: <653F3CF58193744C9DE59C217C072B588F0A8F@nilgiri.india.wirelessworld.airvananet.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MIP & AAA Thread-Index: Acbuu9NvDdCupqHcQ+KR4KHhlABRjA== From: "Arunkumar Sivaraman" To: X-OriginalArrivalTime: 13 Oct 2006 11:36:34.0404 (UTC) FILETIME=[D60BF240:01C6EEBB] X-Spam-Score: 0.0 (/) X-Scan-Signature: 2bf730a014b318fd3efd65b39b48818c Subject: [Mip4] MIP & AAA X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2108314181==" Errors-To: mip4-bounces@ietf.org This is a multi-part message in MIME format. --===============2108314181== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6EEBB.D3CE13EE" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6EEBB.D3CE13EE Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I have a clarification for the following scenario. =20 a. FA is behind firewall/nat (ie, FA having private address). b. MN sends a MIP RRQ to the FA. FA makes a access-request and sends it to a AAA-proxy/broker.=20 =20 The doubt I have is what all parameters will the proxy/broker change before it forwards to the home AAA. Also, radius has something called proxy-state attributes but rfc 2865 doesn't explicitly mention the attributes. What are these attributes and are they standardized in nature? =20 regards, =20 Arunkumar Sivaraman, Airvana India Pvt. Ltd., Ph: +91-80-41348788. =20 "Work is something I do between weekends." =20 ------_=_NextPart_001_01C6EEBB.D3CE13EE Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I have a clarification for the following = scenario.

 

  1. FA is behind = firewall/nat (ie, FA having private address).
  2. MN sends a MIP RRQ to = the FA. FA makes a access-request and sends it to a AAA-proxy/broker. =

 

The doubt I have is what all parameters will the proxy/broker change before it forwards to the home AAA. Also, radius has something called proxy-state attributes but rfc 2865 doesn’t = explicitly mention the attributes. What are these attributes and are they = standardized in nature?

 

regards,

 

Arunkumar Sivaraman,

Airvana India Pvt. Ltd.,

Ph: +91-80-41348788.

 

"Work is something I do between = weekends."

 

------_=_NextPart_001_01C6EEBB.D3CE13EE-- --===============2108314181== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ --===============2108314181==-- From mip4-bounces@ietf.org Fri Oct 13 13:47:45 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GYR8L-0007nk-8H; Fri, 13 Oct 2006 13:47:45 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GYR8K-0007nf-OE for mip4@ietf.org; Fri, 13 Oct 2006 13:47:44 -0400 Received: from prufrock.cs.umd.edu ([128.8.128.102]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GYR8G-00056E-Aa for mip4@ietf.org; Fri, 13 Oct 2006 13:47:44 -0400 Received: (from sharno@localhost) by prufrock.cs.umd.edu (8.12.10/8.12.5) id k9DHleh9022715 for mip4@ietf.org; Fri, 13 Oct 2006 13:47:40 -0400 (EDT) Date: Fri, 13 Oct 2006 13:47:40 -0400 (EDT) From: Tamer Elsharnouby Message-Id: <200610131747.k9DHleh9022715@prufrock.cs.umd.edu> To: mip4@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 Subject: [Mip4] IEEE NetCri 2007: Call for papers X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org ** Apologies if you receive multiple copies of this call for papers ** =============================================================================== Call for Papers NetCri 07 The First International Workshop on Research Challenges in Next Generation Networks for First Responders and Critical Infrastructures http://www.cs.umd.edu/~sharno/NetCri In Conjunction with IEEE IPCCC 2007, New Orleans, Louisiana, April 11-13 =============================================================================== As advances in pervasive computing, wireless communication and sensor networks continue, more opportunities are open to first responders and critical infra- structures to benefit from these technologies. Providing first responders with the best possible technology, infrastructure and services help save the lives of the general public and the first responders as well. One of the main challenges to the operations of first responders and critical infrastructures is to deploy a communication network that is dependable, secure, and rapidly deployable. In order to operate effectively, the deployed network supports services such as location determination, audio and video communication, and in site and remote sensing. Another key feature for first responders and critical infrastructures networks is to support interactions among multiple heterogen- eous networks. This workshop provides a forum for researchers, industry, and government agencies to discuss the challenges facing the design, deployment and operation- al issues for next generation network support for first responders and critical infrastructure. The workshop will identify and define fundamental concepts and techniques, resolve conflicts between different approaches in the area, and provide a common ground for an advanced research and development agenda. Topics of interest include, but are not limited to: - Smart environments (buildings, roads, vehicles, etc.) - Fast roaming in heterogonous network environment - Localization and time synchronization - Rapidly deployable and self configuring services and networks - Security, dependability, privacy, and performance trade-offs - QoS in heterogeneous wireless networks - Sensor and actuator networks for information gathering and real-time control - Network and system support for augmented reality and visual analytics - Simulation studies of first responders and critical infrastructures’ networks - Novel and adaptive communication protocols to support first responders and critical infrastructure’ operation - Resource management and allocation - Power control management - Admission, load and flow control - Performance analysis and experimentation of heterogeneous wireless networks - Security techniques and methods for heterogeneous wireless networks - Interoperability among WLANs, Cellular, WSN and wired networks - Metrics and measurements on heterogeneous networks - Mobility models and traffic patterns in disaster areas - Cross-layer design - Testbeds Paper Submission Papers should describe original, previously unpublished work, not currently under review by another conference, workshop, or journal. Authors are invited to submit a maximum of 6 pages papers including the abstract, figures and references. Papers should include the title, author(s), authors' affiliation and an abstract. The formatting should be according to IEEE rules. Papers should be submitted in a PDF format using the EDAS submission system. Accepted papers will be accessible through the IEEE digital library and are included in the conference proceedings. Important Dates Submission deadline: November 30, 2006 Notification of acceptance: January 5, 2007 Camera ready version: January 26, 2007 Workshop Organizing Committee Program Co-Chairs Mohamed Eltoweissy, Virginia Tech, USA Moustafa Youssef, University of Maryland, USA Publicity Co-Chairs Tamer Elsharnouby, Microsoft Corporation, USA James Joshi, University of Pittsburg, USA -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Mon Oct 16 10:28:20 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZTRw-0004kr-81; Mon, 16 Oct 2006 10:28:16 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GYUne-0002dI-KS; Fri, 13 Oct 2006 17:42:38 -0400 Received: from demokritos1.cytanet.com.cy ([195.14.130.225]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GYUna-0004J1-0j; Fri, 13 Oct 2006 17:42:38 -0400 Received: from [192.168.0.101] (adsl-2-120.cytanet.com.cy [83.168.2.120]) by demokritos1.cytanet.com.cy (Postfix) with ESMTP id 6965E48017; Sat, 14 Oct 2006 00:42:09 +0300 (EEST) From: Christos Panayiotou To: Christosp@ucy.ac.cy Content-Type: text/plain Organization: University of Cyprus Date: Sat, 14 Oct 2006 00:45:57 +0300 Message-Id: <1160775957.7627.83.camel@ECELP09> Mime-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: 7bit X-Virus-Scanned: By virus scanner at Cytanet X-Spam-Score: 1.8 (+) X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d X-Mailman-Approved-At: Mon, 16 Oct 2006 10:28:13 -0400 Cc: Subject: [Mip4] WiOpt'07 Reminder for submission deadline X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Dear Colleague, Apologies for multiple copies of this call for papers. This is a reminder for the extended submission deadline for WiOpt07 which is fast approaching (October 16, 2006)! ===================================================== WiOpt07: Call for Papers 5th Intl. Symposium on Modeling and Optimization in Mobile, Ad Hoc, and Wireless Networks http://www.wiopt.org April 16-20, 2007, Limassol, Cyprus ****New Submission Deadline is October 16, 2006 **** Scope of the Symposium =================================== The design of wireless networks offers challenges not present in fixed networks: both the offered traffic and the network capacity depend on the mobility of the nodes. The designs should not only be functioning correctly, they are also expected to optimize the performance with respect to many criteria, such as energy efficiency, quality of service, and capacity utilization. This symposium intends to bring together researchers and practitioners working on optimization of wireless network design and operations. It welcomes different perspectives, including performance analysis, protocol design, wireless communication, and optimization theory. Contributions to this conference should improve the state-of-the-art in design, analysis, dimensioning and operations of wireless network by providing insights into theoretical aspects as well as providing practical methods and tools. All forms of wireless networks are of interest: from cellular wide-area and local-area networks to dense and sparse ad-hoc networks; domain specific vehicular, public-transport and personal-area networks as well as application-specific sensor networks. Topics of interest include, but are not limited to: +++++++++++++++++++++++++++++++++++++++++++++++++++ ** Modeling of mobility and its influence on systems performance ** Approaches to dynamic spectrum allocation ** Interference control for unlicensed spectral bands ** Effective techniques for simulation of large wireless networks ** Delay and disruption tolerant wireless communication ** Fundamental performance limits ** Analysis and modeling based on measurements ** Protocol design for optimal system performance ** Pricing and incentives in mobile and ad-hoc networks ** Security and co-operation models and analysis ** Optimization techniques for performance, scalability and manageability ** Energy efficiency in mobile and sensor networks ** Measures of quality with associated performance evaluation Submissions ============ Papers should be submitted as extended abstracts of up to 8 pages with single column format and one-and-a-half line spacing, and contain sufficient information to allow for a detailed review. Papers should be submitted in pdf or ps format (see the conference website www.wiopt.org for details). The final manuscript will be 10 pages in double column format. The proceedings will be published by IEEE and accepted papers will be available online via the IEEE website. Adjunct Workshops ================== Several one-day workshops will accompany the main WiOpt Symposium: *** WiNMee/WiTNeMo 2007 : International Workshop on Wireless Network Measurements *** RAWNET 2007 : Resource Allocation in Wireless Networks *** SPASWIN 2007: Spatial Stochastic Models for Wireless Networks *** CONCOM 2007 : Control over Communication Channels *** WNC3 2007 : Wireless Networks: Communication, Cooperation and Competition Important Dates =============== Submission deadline: October 16, 2006 Notification of acceptance: December 18, 2007 Camera-ready copy: January 19, 2007 Steering Committee ================== Imrich Chlamtac, CREATE-NET Italy Eitan Altman, INRIA, France Tamer Basar, UIUC,USA Jon Crowcroft, Cambridge Univ, UK Anthony Ephremides, Univ. of Maryland, USA Daniele Miorandi, CREATE-NET, Italy Organizing Committee ==================== General Chair: *Leandros Tassiullas, Univ. of Thessally, Greece Technical Program Co-Chairs *Leonidas Georgiadis, Aristotle Univ. Greece *Gunnar Karlsson, KTH, Stockholm, Sweden General Vice Chair *Andreas Pitsillides, University of Cyprus Local Arrangements Chair *Stavros Toumpis, University of Cyprus Finance Chair *Karen Decker, ICST Workshops Chair *C. D. Charalambous, University of Cyprus Publicity Chair *Christos Panayiotou, University of Cyprus Conference Coordinator *Zsuzsanna Lanyi-Kaszab, ICST Sponsorship =========== Wiopt'07 is co-sponsored by Create-net, ICST, IFIP TC6.3, IEEE Information Theory, Control and Communications Societies (approval pending) -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Mon Oct 16 10:29:05 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZTSj-0004og-Dk; Mon, 16 Oct 2006 10:29:05 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZA09-0003Kb-Ip; Sun, 15 Oct 2006 13:42:17 -0400 Received: from [2001:12f0:201:1:202:e3ff:fe0f:b8d] (helo=mailman.ufsc.br) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZA04-0007Vp-84; Sun, 15 Oct 2006 13:42:17 -0400 Received: from localhost (localhost [127.0.0.1]) by mailman.ufsc.br (Postfix) with ESMTP id EA4967DFB1; Sun, 15 Oct 2006 14:39:42 -0300 (BRT) Received: from mailman.ufsc.br ([127.0.0.1]) by localhost (mailman.ufsc.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29045-01; Sun, 15 Oct 2006 14:39:32 -0300 (BRT) Received: from mailman.ufsc.br (mailman.ufsc.br [150.162.1.5]) by mailman.ufsc.br (Postfix) with ESMTP id 102607DEFB; Sun, 15 Oct 2006 14:38:29 -0300 (BRT) X-Original-To: researchers@mailman.ufsc.br Delivered-To: researchers@mailman.ufsc.br Received: from localhost (localhost [127.0.0.1]) by mailman.ufsc.br (Postfix) with ESMTP id 2B98D7DEF4 for ; Sun, 15 Oct 2006 14:38:18 -0300 (BRT) Received: from mailman.ufsc.br ([127.0.0.1]) by localhost (mailman.ufsc.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28731-04 for ; Sun, 15 Oct 2006 14:38:14 -0300 (BRT) Received: from rot.barddal.br (44054.static.fln.virtua.com.br [200.174.44.54]) by mailman.ufsc.br (Postfix) with ESMTP id 741907DEF2 for ; Sun, 15 Oct 2006 14:38:14 -0300 (BRT) Received: from mi0f9a3e303b4e (201-41-246-176.fnsce703.dsl.brasiltelecom.net.br [201.41.246.176] (may be forged)) (authenticated bits=0) by rot.barddal.br (8.13.1/8.13.1) with ESMTP id k9FHbDDu029230; Sun, 15 Oct 2006 17:37:16 GMT Message-ID: <001901c6f080$91bbc540$4000a8c0@mi0f9a3e303b4e> From: "Profa Mirela Sechi Moretti Annoni Notare" To: Date: Sun, 15 Oct 2006 15:37:15 -0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Antivirus: avast! (VPS 0641-4, 13/10/2006), Outbound message X-Antivirus-Status: Clean X-barddal-MailScanner-Information: Please contact the ISP for more information X-barddal-MailScanner: Found to be clean X-barddal-MailScanner-From: mirela@barddal.br X-Virus-Scanned: by amavisd-new at mailman.ufsc.br X-BeenThere: researchers@mailman.ufsc.br X-Mailman-Version: 2.1.5 Precedence: list X-Virus-Scanned: by amavisd-new at mailman.ufsc.br Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.1 (/) X-Scan-Signature: 76c7db407a166e4c39f35d8215d8dd32 X-Mailman-Approved-At: Mon, 16 Oct 2006 10:29:03 -0400 Cc: Subject: [Mip4] [Researchers] I2TS2006 EXTENDED DEADLINE X-BeenThere: mip4@ietf.org List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org CALL FOR PAPERS I2TS'2006 - 5th International Information and Telecommunication Technolog= ies Symposium Cuiab=E1, Mato Grosso, Brazil, December 06-08, 2006 EXTENDED DEADLINE 22/10/2006 The International Information and Telecommunication Technologies Symposiu= m (I2TS'2006) at Cuiab=E1 city,in the paradisiac Pantanal (South Amazonia), Brazil. I2TS'2006 serves as an international forum for people from academia,indus= try and research labs, for presenting recent results in information and telecommunication technologies research and applications. I2TS'2006 includes Technical Sessions, Tool Sessions, Poster Sessions and Mini-coursers. SUBMISSION GUIDELINES Authors are encouraged to submit both theoretical and practical results o= f significance. Demonstration of new tools/applications are welcome. The papers should be submitted in electronic form (PDF only) by JEMS system (Brazilian EDAS) at https://submissoes.sbc.org.br/i2ts2006= . The length of the papers are as follows: Full papers: 8 pages (IEEE Two Column Format) Short papers: 4 pages (IEEE Two Column Format) - research in progress Posters and Tools: 2 pages (IEEE Two COlumn Format) See Instruction for Authors in the web page. The English papers will be published in hard copy and CD-ROM; the portuguese papers will be published in CD-ROM only (same ISBN). Best papers will be invited to submit extended version to IEEE-R9 LatinAmerica and RESI magazines. Relevant topics include, but are not limited to: TELECOMMUNICATION AND WIRELESS NETWORKS - Wireless Sensor Networks - Mobile Ad Hoc Networks - MANETs - Wireless Multimedia - Telecommunication Technology - Optical Networks and Switching - Wireless WANs, LANs and PANs (Personal Area Networks) - Quality of Service - Mobile wireless network Planning, Management, Control and Monitoring - Security and Privacy - Applications and Case Studies COMPUTER NETWORKS, REAL TIME AND DISTRIBUTED SYSTEMS - Real-Time and Multimedia Systems - Parallel and Distributed Systems - Distributed and Mobile Computing - Distributed Algorithms and Architectures - Distributed Operating Systems - Distributed Data Management - Computer Networks - P2P and Overlay networks - Quality of Service - Network Planning, Management, Control and Monitoring - Security and Privacy - Applications and Case Studies DISTRIBUTED SIMULATIONS, UBIQUITOUS COMPUTING AND INFORMATION TECHNOLOGY - Large Scale Distributed Interactive Simulation - Ubiquitous Computing (architectures, systems, human-computer interactio= n) - Context aware computing - Web-Based Systems (architectures, programming models, tools etc) - Semantic web and ontologies - Embedded Systems - Criminal in the Internet and Electronic Justice - Tools for Computational Forensic - Applications and Case Studies - Collaborative Virtual Environments (Synchronization, Extensibility, Persistency, Interoperability, Scalability, Adaptability, Security) TOOL SESSIONS and POSTER SESSIONS Authors are encouraged to submit papers describing tools suitable for on-line demonstration. Standard microcomputers will be available for tool sessions. The tool and poster papers will undergo a regular review process and will be published in the conference proceedings in a dedicated tool a= nd poster sessions, respectively. MINI-COURSES Proposals for half-day or full-day MiniCourses are solicited on timely topics related to the above areas. The proposal must include description and short-biographies. IMPORTANT DATES Paper/Poster/ToolMiniCourses Submission Deadline: October 22th, 2006 Authors Notification: November 18th, 2006 Camera Ready/Paper Registration: November 25th, 2006 Sponsored by: UFSC-INE - Federal University of Santa Catarina UNIVAG - Varzea Grande University BARDDAL - Barddal University CEFET-MT - Federal Technical Center IEEE-R9 - IEEE Region9 - LatinAmerica GENERAL CO-CHAIRS Azzedine Boukerche - University of Ottawa - Canada Jo=E3o Bosco Mangueira Sobral - UFSC - Brazil TECHNICAL PROGRAM COMMITTEE CO-CHAIRS Antonio Alfredo F. Loureiro - UFMG - Brazil Mirela Sechi Moretti Annoni Notare - Barddal University - Brazil PROGRAM COMMITTEE Abbas, Claudia Barenco - UnB - Brazil Aguiar, Einstein Lemos de - UFMT - Brazil Almulla, Mohammed - Kuwait University - Kuwait Araujo, Regina Borges - UFSCar - Brazil Benyoucef, Morad - University of Ottawa - Canada Breunig, Adriano - CEFET-MT - Brazil Bononi, Luciano - University of Bologna - Italy Boukerche, Azzedine - University of Ottawa - Canada Calamoneri, Tiziana - University of Rome "La Sapienza" - Italy Camargo, Jo=E3o Batista - USP - Brazil Castro, Julio Cesar Hern=E1ndez - Universidad Carlos III - Spain Correa, Ghilson Ramalho - CEFET-MT - Brazil Correa, Pedro Luiz Pizzigatti - USP - Brazil Cruz, Fernando Augusto da Silva - UFSC - Brazil Dantas, Mario Ant=F4nio Ribeiro - INE/UFSC - Brazil Gondim, Paulo Roberto de Lira - UnB - Brazil Fortes, Renata Pontin M. - ICMC/USP - Brazil Filho, Bartolomeu Uch=F4a - EEL/UFSC, Brazil Greve, Fab=EDola Gon=E7alves Pereira - UFBA - Brazil Guardia, H=E9lio Crestana - UFSCar - Brazil Ionescu, Dan - University of Ottawa - Canada Jardini, Jos=E9 Antonio - USP - Brazil Karatza, Helen - University of Thessaloniki - Greece Kurt, Akif - Istanbul University - Turkey Martinez, Jeimy Jos=E9 Cano - Uniandes - Col=F4mbia Martins, Ronan Marcelo - CEFET-MT - Brasil Mateus, Geraldo Robson - DCC/UFMG - Brazil Mello, Rodrigo Fernandes - ICMC/USP - Brazil Melo, Alba Cristina Magalh=E3es Alves - UnB Brazil Min, Geyong - University of Bradford - UK Moreira, Edson dos Santos - ICMC/USP - Brazil Narasimhan, Lakshmi - University of Newcastle - Australia Nikoleletseas, Sotiris E. - Computer Technology Institute - Greece Notare, Mirela Sechi Moretti Annoni - Barddal University - Brazil Oliveira, Ruy - CEFET-MT - Brazil Ould-Khaoua, Mohamed M. - University of Glasgow - UK Pacheco, Roberto - UFSC - Brazil Paris, Jehan-Fran=E7ois - University of Houston - USA Penna, Manoel Camillo de Oliveira Neto - PUC/PR - Brazil Pizzolato, Ednaldo Briganti - UFSCar - Brazil Puttini, Ricardo Staciarini - UnB - Brazil Riso, Bernardo Gon=E7alves - UFSC - Brazil Rocha, Carlos Aurelio Faria da - EEL/UFSC - Brazil Silva, Jorge S=E1 - DEI/UC - Portugal Sklavos, Nicolas - Technological Educational Institute of Messolonghi - Greece Sobral, Jo=E3o Bosco Mangueira - UFSC - Brazil Souza, Patr=EDcia Cristiane de - UFMT - Brazil Souza Jr., Rafael Tim=F3teo - UnB - Brazil Trevelin, Luis Carlos - USCar - Brazil Villalba, Luis Javier Garc=EDa - Universidad Complutense de Madrid - Spai= n Wangham, Michelle - Barddal - Brazil Zomaya, Albert - University of Sydney - Australia ORGANIZING COMMITTEE Lucas Guardalben - PPGCC-UFSC - Brazil Joelson de Alencar Degaspari - PPGCC-UFSC - Brazil Claudio Jos=E9 Biazus - PPGCC-UFSC - Brazil Igor Vinicius Mussoi de Lima - PPGCC-UFSC - Brazil Mario Pereira Guitte -UNIVAG - Brazil Rosana Ravache - UNIVAG - Brazil M=E1rcia Ribeiro - UNIVAG - Brazil Kenji Kido - UNIVAG - Brazil Koga, Miguel - UNEMAT - Brazil LOCAL ARRANGEMENT CHAIR Fernando Marcos Bonnemasou Moreira de Castilho - UNIVAG - Brazil PUBLICITY COMMITTEE Francisco J. A. de Aquino, EEL-UFSC - Brazil Cristiano Maciel - IC-UFF/RJ - Brazil Renato Bobsin Machado - UNIOESTE/PR - Brazil Jo=E3o Paulo Delgado Preti - CEFET/MT - Brazil Metuzalen Gon=E7alves Silva - UNEMAT - Brazil Robson Gomes de Melo - UNEMAT - Brazil ADVISORY BOARD COMMITTEE Azzedine Boukerche - University of Ottawa - Canada Antonio Alfredo F. Loureiro - UFMG - Brazil Bernardo Gon=E7alves Riso - UFSC - Brazil Manoel Camillo de Oliveira Penna Neto - PUC/PR - Brazil STEERING COMMITTEE CO-CHAIRS Azzedine Boukerche - University of Ottawa - Canada Mirela Sechi Moretti Annoni Notare - Barddal University - Brazil FURTHER INFORMATION For additional information, please send an e-mail to Prof. Mirela Secchi Annoni Moretti Notare (mirela@barddal.br) or Prof. Prof. Jo=E3o Bosco Mangueira Sobral (bosco@inf.ufsc.br) Updated conference announcement and information are accessible at the symposium home page at www.inf.ufsc.br/i2ts2006.=20 --=20 Esta mensagem foi verificada pelo sistema de antiv=EDrus e acredita-se estar livre de perigo. _______________________________________________ Researchers mailing list Researchers@mailman.ufsc.br http://mailman.ufsc.br/mailman/listinfo/researchers -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Tue Oct 17 06:09:04 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZlsQ-00029E-9M; Tue, 17 Oct 2006 06:08:50 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZlsP-000294-7r for mip4@ietf.org; Tue, 17 Oct 2006 06:08:49 -0400 Received: from av10-1-sn2.hy.skanova.net ([81.228.8.181]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZlsN-0002dO-Iv for mip4@ietf.org; Tue, 17 Oct 2006 06:08:49 -0400 Received: by av10-1-sn2.hy.skanova.net (Postfix, from userid 502) id D959737F47; Tue, 17 Oct 2006 12:08:46 +0200 (CEST) Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av10-1-sn2.hy.skanova.net (Postfix) with ESMTP id 5507037EC8; Tue, 17 Oct 2006 12:08:45 +0200 (CEST) Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com [81.232.110.214]) by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 193FC37E44; Tue, 17 Oct 2006 12:08:42 +0200 (CEST) Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.63) (envelope-from ) id 1GZlsC-00065E-K8; Tue, 17 Oct 2006 12:08:36 +0200 Message-ID: <4534ABA4.2020803@levkowetz.com> Date: Tue, 17 Oct 2006 12:08:36 +0200 From: Henrik Levkowetz User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909) MIME-Version: 1.0 To: Mobile IPv4 Mailing List X-Enigmail-Version: 0.94.0.0 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false X-Spam-Score: 0.1 (/) X-Scan-Signature: 0e9ebc0cbd700a87c0637ad0e2c91610 Cc: mip4-chairs@tools.ietf.org Subject: [Mip4] Proposed charter update for NEMOv4 work X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0726007344==" Errors-To: mip4-bounces@ietf.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============0726007344== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig256EB492CEF7BC9F54DDB903" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig256EB492CEF7BC9F54DDB903 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, We're working on a charter update for MIPv4. One of the things we'd like to add is a work item covering the NEMOv4 specification. We'd like to add the following item to the charter: 11. NEMO v4 Support The Network Mobility (nemo) working group deals with the problem of mobility of a whole network, such as might exist inside a vehicle, train, or airplane. The nemo working group has developed draft specifications for both IPv6 and IPv4 mobile networks. However, it has been recognized that the IPv4 version of the protocol can be viewed as an extension of the basic Mobile IPv4 protocol, and there is good reason to do this extension in the mip4 working group. The working group will take on the NEMO v4 internet draft and progress it along the standards track. If you have comments on this, please send them to the list. Regerds, Henrik and Pete (The resulting full charter text is here: Description of Working Group: IP mobility support for IPv4 nodes (hosts and routers) is specified in RFC3344. RFC 3344 mobility allows a node to continue using its "permanent" home address as it moves around the Internet. The Mobile IP protocols support transparency above the IP layer, including maintenance of active TCP connections and UDP port bindings.Besides the basic Mobile IPv4 (MIPv4) protocols, several other drafts deal with concerns such as optimization, security, extensions, AAA support, and deployment issues. MIPv4 is currently being deployed on a wide basis (e.g., in cdma2000 networks). The scope of the deployment is on a fairly large scale and accordingly, the MIP4 WG will focus on deployment issues and on addressing known deficiencies and shortcomings in the protocol that have come up as a result of deployment experience. Specifically, the working group will complete the work items to facilitate interactions with AAA environments, interactions with enterprise environments when MIPv4 is used therein, and updating existing protocol specifications in accordance with deployment needs and advancing those protocols that are on the standards track. Work expected to be done by the MIP4 WG as proposed by this charter is as follows: 1. MIPv4 has been a proposed standard for several years. It has been adopted by other standard development organizations and has been deployed commercially. One of the next steps for the WG is to advance the protocol to draft standard status. As part of advancing base Mobile IP specs to DS, the MIPv4 NAI RFC (2794) will be revised to reflect implementation experience 2. Work items that are pending from the previous Mobile IP WG, which will be completed by the MIP4 WG, are: - completion of the MIB for the revised base Mobile IP specification (2006bis) - regional registration draft. 3. The MIP4 WG will also complete the work on MIPv4 interactions in VPN scenarios. This work will involve identifying the requirements and a solution development for MIPv4 operation in the presence of IPsec VPNs. 4. Additionally, a proposal has been made for how MOBIKE could work together with MIPv4. This proposal does not describe any new protocol, but formulates a best current practice for deploying MOBIKE together with MIPv4. The working group will adopt and complete this document. 5. Some issues have been raised with respect to RFC3519. These will be identified and addressed as appropriate, through errata, revision of RFC 3519, and/or supplemental documents as needed. 6. It has been proposed that the FMIP protocol, which has been standardised for MIPv6 in the MIPSHOP working group, should also be published as an experimental protocol for MIPv4. A draft for this exists. The working group will take up and carry this work forward to publication 7. An extension to carry generic strings in the Registration Reply message has been proposed. The purpose is to supply supplemental human-readable information intended to the MN user. The working group will complete the specification and applicability statement of such an extension. 8. RADIUS attributes for MIP4. A set of RADIUS attributes has been proposed for MIPv4. The working group will first produce a requirements specification, describing how the work differs from the requirements in RFC 2977 and the functionality provided by RFC 4004 (the MIPv4 Diameter App). The reason why this first step is required is that RFC 3127 shows that full RFC 2977 functionality can't be provided by even a considerably extended RADIUS, so we need to match the requirements to what can be done within RADIUS. Provided the requirements work finds approval with ADs and RADEXT WG, the workgroup will complete the specification of MIPv4 RADIUS attributes, solicit feedback from the RADEXT WG, adjust, and submit this for publication. Note that the work may require extensions to the RADIUS attribute space which will be handled outside the MIP4 WG. 9. MIPv4 Extension for Configuration Options. Several drafts have proposed extensions to help improve configuration of MIPv4 clients. The latest proposal is for a general configuration option extension which could carry information such as e.g., DNS address and DHCP server address. The working group will take on and complete one proposal for a configuration option extension. 10. Dual-stack Support There have been several proposals for how to enable an IPv6 connection over a network that supports Mobile IPv4. A protocol enhancement to MIPv4 would allow for IPv6 support in a region where Mobile IPv4 has already been implemented and deployed. This would allow a dual stack mobile node to maintain IPv6 connectivity when using MIPv4. The solution would therefore be applicable only to networks that are not deploying Mobile IPv6. The working group will take on and complete one proposal for IPv6 over Mobile IPv4. This work is restricted to a small protocol extension similar to current Mobile IPv4 functionality. Support for advanced Mobile IPv6 functionality is strictly outside the scope. A problem statement covering both Mobile IPv4 and IPv6 dual-stack issues is expected to come out of MIP6 WG, and will not be developed in MIP4 WG. 11. NEMO v4 Support The Network Mobility (nemo) working group deals with the problem of mobility of a whole network, such as might exist inside a vehicle, train, or airplane. The nemo working group has developed draft specifications for both IPv6 and IPv4 mobile networks. However, it has been recognized that the IPv4 version of the protocol can be viewed as an extension of the basic Mobile IPv4 protocol, and there is good reason to do this extension in the mip4 working group. The working group will take on the NEMO v4 internet draft and progress it along the standards track. ) --------------enig256EB492CEF7BC9F54DDB903 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iD8DBQFFNKukeVhrtTJkXCMRAjgAAKDYhmduMoqmmTw/AkFCmLvWi6VJNwCgvJbP u1EYppVYno28vRPagEBM49M= =ZxSe -----END PGP SIGNATURE----- --------------enig256EB492CEF7BC9F54DDB903-- --===============0726007344== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ --===============0726007344==-- From mip4-bounces@ietf.org Tue Oct 17 14:18:46 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZtWU-0000F1-Rf; Tue, 17 Oct 2006 14:18:42 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZsyy-0008A8-Tw for mip4@ietf.org; Tue, 17 Oct 2006 13:44:04 -0400 Received: from mail119.messagelabs.com ([216.82.241.179]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GZsyv-0005g5-LK for mip4@ietf.org; Tue, 17 Oct 2006 13:44:04 -0400 X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-3.tower-119.messagelabs.com!1161107040!10281248!1 X-StarScan-Version: 5.5.10.7; banners=-,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 3228 invoked from network); 17 Oct 2006 17:44:00 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-3.tower-119.messagelabs.com with SMTP; 17 Oct 2006 17:44:00 -0000 Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id k9HHi0gW005767 for ; Tue, 17 Oct 2006 10:44:00 -0700 (MST) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id k9HHhxNM003596 for ; Tue, 17 Oct 2006 12:43:59 -0500 (CDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Tue, 17 Oct 2006 13:43:58 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-deng-mip4-generic-notification-message-02.txt Thread-Index: AcbyE9MO39zif61xTK2b0OC/8fCeJQ== From: "McCann Peter-A001034" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 X-Mailman-Approved-At: Tue, 17 Oct 2006 14:18:41 -0400 Subject: [Mip4] draft-deng-mip4-generic-notification-message-02.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org During the last working group meeting, we had a discussion on draft-deng-mip4-generic-notification-message-02.txt. There were 3 or 4 people who spoke out in favor of adding this to the charter. I'd like to poll the list on this. Who is in favor of adopting this as a working group item? Opposed? If we get consensus to add this we can do it at the same time as we do the NEMOv4 addition. -Pete -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Tue Oct 17 14:54:54 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZu5W-0004cm-Fg; Tue, 17 Oct 2006 14:54:54 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZu5U-0004cg-LB for mip4@ietf.org; Tue, 17 Oct 2006 14:54:52 -0400 Received: from web83007.mail.mud.yahoo.com ([209.191.87.13]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GZu5Q-00052Z-8G for mip4@ietf.org; Tue, 17 Oct 2006 14:54:52 -0400 Received: (qmail 15921 invoked by uid 60001); 17 Oct 2006 18:54:36 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=oe4BRhiN894tbItnr9u4HL5b5JwqbMGQrkHnE7mLwXTp9d8qF6WQBGnoDN8aNMRs65zXsaVZfArDGp1UXtrx4hc2rICXhn9OSe6DWWSVCm9zNcAGBna/njUtkO6Zi+Uuw/ZGVQ/CNhS15Bk39lu25rcI6xfGETSBgOjSIrC+MJ8= ; Message-ID: <20061017185436.15919.qmail@web83007.mail.mud.yahoo.com> Received: from [152.131.12.192] by web83007.mail.mud.yahoo.com via HTTP; Tue, 17 Oct 2006 11:54:36 PDT Date: Tue, 17 Oct 2006 11:54:36 -0700 (PDT) From: Subject: Re: [Mip4] draft-deng-mip4-generic-notification-message-02.txt To: McCann Peter-A001034 , mip4@ietf.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.2 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Cc: X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org My initial reaction is ambivalence. Signaling of this type certainly seems useful, maybe even necessary, but ultimately applications ought to be able to communicate with mobile nodes without actually being aware that they are mobile nodes. So, will the basic MIP4 protocol continue to function (perhaps suboptimally) in the absence of notification support? Certainly, notifications could be treated as unexpected UDP packets, and that's already true of existing control messages Hmm...I supposed that all translates to "support". === Gregory Woodhouse "Mathematics is the science of patterns." --Lynn Arthur Steen, 1988 ----- Original Message ---- From: McCann Peter-A001034 To: mip4@ietf.org Sent: Tuesday, October 17, 2006 10:43:58 AM Subject: [Mip4] draft-deng-mip4-generic-notification-message-02.txt During the last working group meeting, we had a discussion on draft-deng-mip4-generic-notification-message-02.txt. There were 3 or 4 people who spoke out in favor of adding this to the charter. I'd like to poll the list on this. Who is in favor of adopting this as a working group item? Opposed? If we get consensus to add this we can do it at the same time as we do the NEMOv4 addition. -Pete -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Tue Oct 17 15:00:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZuAw-0001n6-FS; Tue, 17 Oct 2006 15:00:30 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZuAv-0001n0-1v for mip4@ietf.org; Tue, 17 Oct 2006 15:00:29 -0400 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZuAr-0005lZ-Ls for mip4@ietf.org; Tue, 17 Oct 2006 15:00:29 -0400 Received: from sj-dkim-8.cisco.com ([171.68.10.93]) by sj-iport-5.cisco.com with ESMTP; 17 Oct 2006 12:00:25 -0700 Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-8.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9HJ0Oee004637; Tue, 17 Oct 2006 12:00:24 -0700 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k9HIxvOn026785; Tue, 17 Oct 2006 12:00:20 -0700 (PDT) Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 17 Oct 2006 12:00:15 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Mip4] Proposed charter update for NEMOv4 work Date: Tue, 17 Oct 2006 12:00:14 -0700 Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5202B54055@xmb-sjc-235.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Proposed charter update for NEMOv4 work Thread-Index: Acbx1J+piz7HebDHTn6fbG+NaQQYTQASRuqg From: "Kent Leung \(kleung\)" To: "Henrik Levkowetz" , "Mobile IPv4 Mailing List" X-OriginalArrivalTime: 17 Oct 2006 19:00:15.0828 (UTC) FILETIME=[7B4DE140:01C6F21E] DKIM-Signature: a=rsa-sha1; q=dns; l=1446; t=1161111624; x=1161975624; c=relaxed/relaxed; s=sjdkim8002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=kleung@cisco.com; z=From:=22Kent=20Leung=20\(kleung\)=22=20 |Subject:RE=3A=20[Mip4]=20Proposed=20charter=20update=20for=20NEMOv4=20work; X=v=3Dcisco.com=3B=20h=3D7q48mDpkZ229FpIyeeCLvEex83M=3D; b=bRH5H5UYNFxfBp0AXc3ih25EKkCZPo67AdtoL2/qsU9N3P/Vp4xyWQjod2dJBA89hJzsA2Ct OPsSJPKU1r21l9c4FdEiEGhGt+BimHuG0rop86ahBEO3Dtpn5JWeK4Xc; Authentication-Results: sj-dkim-8.cisco.com; header.From=kleung@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Cc: mip4-chairs@tools.ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi Henrik and Pete. I'm in favor to have NEMOv4 as a work item. It fits naturally in MIP4 WG since Mobile Router is a section in RFC 3344 and backwards to RFC 2002. The extensions are for supporting IPv4 networks. There's value to extend the support for Mobile Router. Kent=20 -----Original Message----- From: Henrik Levkowetz [mailto:henrik@levkowetz.com]=20 Sent: Tuesday, October 17, 2006 3:09 AM To: Mobile IPv4 Mailing List Cc: mip4-chairs@tools.ietf.org Subject: [Mip4] Proposed charter update for NEMOv4 work Hi, We're working on a charter update for MIPv4. One of the things we'd like to add is a work item covering the NEMOv4 specification. We'd like to add the following item to the charter: 11. NEMO v4 Support The Network Mobility (nemo) working group deals with the problem of mobility of a whole network, such as might exist inside a vehicle, train, or airplane. The nemo working group has developed draft specifications for both IPv6 and IPv4 mobile networks. However, it has been recognized that the IPv4 version of the protocol can be viewed as an extension of the basic Mobile IPv4 protocol, and there is good reason to do this extension in the mip4 working group. The working group will take on the NEMO v4 internet draft and progress it along the standards track. If you have comments on this, please send them to the list. Regerds, Henrik and Pete -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Tue Oct 17 15:23:47 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZuXG-0000GL-MU; Tue, 17 Oct 2006 15:23:34 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZuXF-0000F0-MK for mip4@ietf.org; Tue, 17 Oct 2006 15:23:33 -0400 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZuXC-0000eg-9f for mip4@ietf.org; Tue, 17 Oct 2006 15:23:33 -0400 Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-3.cisco.com with ESMTP; 17 Oct 2006 12:23:29 -0700 Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9HJNTho028196; Tue, 17 Oct 2006 12:23:29 -0700 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k9HJNRix011390; Tue, 17 Oct 2006 12:23:29 -0700 (PDT) Received: from xmb-sjc-224.amer.cisco.com ([128.107.191.98]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 17 Oct 2006 12:23:28 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Mip4] Proposed charter update for NEMOv4 work Date: Tue, 17 Oct 2006 12:23:27 -0700 Message-ID: <28CEA477BE98ED48AF08A0B637A74BF40273B2F7@xmb-sjc-224.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Proposed charter update for NEMOv4 work Thread-Index: Acbx1J+piz7HebDHTn6fbG+NaQQYTQASRuqgAADuIbA= From: "Gopal Dommety \(gdommety\)" To: "Kent Leung \(kleung\)" , "Henrik Levkowetz" , "Mobile IPv4 Mailing List" X-OriginalArrivalTime: 17 Oct 2006 19:23:28.0730 (UTC) FILETIME=[B989DBA0:01C6F221] DKIM-Signature: a=rsa-sha1; q=dns; l=2307; t=1161113009; x=1161977009; c=relaxed/simple; s=sjdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=gdommety@cisco.com; z=From:=22Gopal=20Dommety=20\(gdommety\)=22=20 |Subject:RE=3A=20[Mip4]=20Proposed=20charter=20update=20for=20NEMOv4=20work; X=v=3Dcisco.com=3B=20h=3DbiNgd2ddiETt4/61MZYuSXoUaOk=3D; b=lSIyYWbiQ7Z+sFlVduhJsMxGS6ez2Q2DmdcXCe2G32YkDGANkoia961xGgaT2MDTYPZBUGA1 rAicE3drRHGtmbNRdsJD0g+/Tu9XRUKRxoDVSXsMF2RGwHBJoayOiJjv; Authentication-Results: sj-dkim-1.cisco.com; header.From=gdommety@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d Cc: mip4-chairs@tools.ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hello Henrik and Pete, I am also in favour of a charter update to include NEMOv4. It fits in the MIPv4 working group and adds value to Mobile IP v4 and there is a need for interoperability. Regards, -Gopal =20 Gopal Dommety ------------------------------------------------------- Judgment hinders imagination ---------------------------------------------- -----Original Message----- From: Kent Leung (kleung)=20 Sent: Tuesday, October 17, 2006 12:00 PM To: Henrik Levkowetz; Mobile IPv4 Mailing List Cc: mip4-chairs@tools.ietf.org Subject: RE: [Mip4] Proposed charter update for NEMOv4 work Hi Henrik and Pete. I'm in favor to have NEMOv4 as a work item. It fits naturally in MIP4 WG since Mobile Router is a section in RFC 3344 and backwards to RFC 2002. The extensions are for supporting IPv4 networks. There's value to extend the support for Mobile Router. Kent=20 -----Original Message----- From: Henrik Levkowetz [mailto:henrik@levkowetz.com] Sent: Tuesday, October 17, 2006 3:09 AM To: Mobile IPv4 Mailing List Cc: mip4-chairs@tools.ietf.org Subject: [Mip4] Proposed charter update for NEMOv4 work Hi, We're working on a charter update for MIPv4. One of the things we'd like to add is a work item covering the NEMOv4 specification. We'd like to add the following item to the charter: 11. NEMO v4 Support The Network Mobility (nemo) working group deals with the problem of mobility of a whole network, such as might exist inside a vehicle, train, or airplane. The nemo working group has developed draft specifications for both IPv6 and IPv4 mobile networks. However, it has been recognized that the IPv4 version of the protocol can be viewed as an extension of the basic Mobile IPv4 protocol, and there is good reason to do this extension in the mip4 working group. The working group will take on the NEMO v4 internet draft and progress it along the standards track. If you have comments on this, please send them to the list. Regerds, Henrik and Pete -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Tue Oct 17 15:42:00 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZup6-0004eR-DJ; Tue, 17 Oct 2006 15:42:00 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZup4-0004bo-KD for mip4@ietf.org; Tue, 17 Oct 2006 15:41:58 -0400 Received: from mail128.messagelabs.com ([216.82.250.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GZup3-0002zF-9o for mip4@ietf.org; Tue, 17 Oct 2006 15:41:58 -0400 X-VirusChecked: Checked X-Env-Sender: alexandru.petrescu@motorola.com X-Msg-Ref: server-9.tower-128.messagelabs.com!1161114015!3152042!1 X-StarScan-Version: 5.5.10.7; banners=-,-,- X-Originating-IP: [129.188.136.10] Received: (qmail 30028 invoked from network); 17 Oct 2006 19:40:15 -0000 Received: from motgate6.mot.com (HELO motgate.mot.com) (129.188.136.10) by server-9.tower-128.messagelabs.com with SMTP; 17 Oct 2006 19:40:15 -0000 Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232]) by motgate.mot.com (8.12.11/Motorola) with ESMTP id k9HJi3fn007635 for ; Tue, 17 Oct 2006 12:44:04 -0700 (MST) Received: from [10.129.40.99] ([10.129.40.99]) by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id k9HJeBV9013864; Tue, 17 Oct 2006 14:40:12 -0500 (CDT) Message-ID: <4535319A.1080406@motorola.com> Date: Tue, 17 Oct 2006 21:40:10 +0200 From: Alexandru Petrescu User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: McCann Peter-A001034 Subject: Re: [Mip4] draft-deng-mip4-generic-notification-message-02.txt References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Cc: mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org McCann Peter-A001034 wrote: > During the last working group meeting, we had a discussion on > draft-deng-mip4-generic-notification-message-02.txt. There were 3 or > 4 people who spoke out in favor of adding this to the charter. > > I'd like to poll the list on this. Who is in favor of adopting this > as a working group item? Opposed? I'm in favor. The notification could be: please change the home agent run rfc4433 (MIP dynamic HA assignment) or please acquire a different home address, a different home prefix, a different moving prefix (DHCPv4 PD), etc. However, some of the examples given in the draft raise me some questions, I could comment on those when time comes. Alex -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Tue Oct 17 17:46:54 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZwlt-0003jq-Ka; Tue, 17 Oct 2006 17:46:49 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZwls-0003jg-Jb for mip4@ietf.org; Tue, 17 Oct 2006 17:46:48 -0400 Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZwlr-0007nu-6X for mip4@ietf.org; Tue, 17 Oct 2006 17:46:48 -0400 Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 17 Oct 2006 14:46:46 -0700 Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9HLkk5E000802; Tue, 17 Oct 2006 14:46:46 -0700 Received: from irp-view7.cisco.com (irp-view7.cisco.com [171.70.65.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k9HLkkW5020890; Tue, 17 Oct 2006 14:46:46 -0700 (PDT) Date: Tue, 17 Oct 2006 14:46:46 -0700 (PDT) From: Sri Gundavelli To: gregory.woodhouse@sbcglobal.net Subject: Re: [Mip4] draft-deng-mip4-generic-notification-message-02.txt In-Reply-To: <20061017185436.15919.qmail@web83007.mail.mud.yahoo.com> Message-ID: References: <20061017185436.15919.qmail@web83007.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed DKIM-Signature: a=rsa-sha1; q=dns; l=2016; t=1161121606; x=1161985606; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=sgundave@cisco.com; z=From:Sri=20Gundavelli=20 |Subject:Re=3A=20[Mip4]=20draft-deng-mip4-generic-notification-message-02.txt; X=v=3Dcisco.com=3B=20h=3D6JUbOaQIiwAXEmlQ89vRV393u3Y=3D; b=rNkHm41d7rx0Cdj+tBROIT+1Y3+yAcdwEdxcOJPmrDWknc6vVsZXku3loD8X+Yvxf+uXluaT VHzDH0FMTc2c4rJoMRgksWxS8kv8X0pVQN3ibvjJCZw0VP2NiY4S58uf; Authentication-Results: sj-dkim-3.cisco.com; header.From=sgundave@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 Cc: mip4@ietf.org, McCann Peter-A001034 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Yes. I support this as well. We have found the need for this in many scenarios. We need this simple HA to MN notification mechanism. [PS: I'm on the author list] Sri On Tue, 17 Oct 2006, gregory.woodhouse@sbcglobal.net wrote: > My initial reaction is ambivalence. Signaling of this type certainly seems useful, maybe even necessary, but ultimately applications ought to be able to communicate with mobile nodes without actually being aware that they are mobile nodes. So, will the basic MIP4 protocol continue to function (perhaps suboptimally) in the absence of notification support? Certainly, notifications could be treated as unexpected UDP packets, and that's already true of existing control messages > > Hmm...I supposed that all translates to "support". > > === > Gregory Woodhouse > > "Mathematics is the science of patterns." > --Lynn Arthur Steen, 1988 > > > ----- Original Message ---- > From: McCann Peter-A001034 > To: mip4@ietf.org > Sent: Tuesday, October 17, 2006 10:43:58 AM > Subject: [Mip4] draft-deng-mip4-generic-notification-message-02.txt > > > During the last working group meeting, we had a discussion > on draft-deng-mip4-generic-notification-message-02.txt. > There were 3 or 4 people who spoke out in favor of adding > this to the charter. > > I'd like to poll the list on this. Who is in favor of > adopting this as a working group item? Opposed? > > If we get consensus to add this we can do it at the same > time as we do the NEMOv4 addition. > > -Pete > > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www1.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www1.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Wed Oct 18 02:14:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ga4h9-0000FL-Lj; Wed, 18 Oct 2006 02:14:27 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ga4h8-0000FF-R7 for mip4@ietf.org; Wed, 18 Oct 2006 02:14:26 -0400 Received: from smtp.tele.fi ([192.89.123.25]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ga4h4-0006Ff-Fu for mip4@ietf.org; Wed, 18 Oct 2006 02:14:26 -0400 Received: from titanium.secgo.net (unknown [194.215.226.66]) by smtp.tele.fi (Postfix) with ESMTP id 8D441218D9; Wed, 18 Oct 2006 09:14:15 +0300 (EEST) Received: from [192.168.131.185] ([192.168.131.185]) by titanium.secgo.net with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Oct 2006 09:14:14 +0300 Message-ID: <4535C635.1080208@secgo.com> Date: Wed, 18 Oct 2006 09:14:13 +0300 From: Tom K Weckstrom User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Henrik Levkowetz Subject: Re: [Mip4] Proposed charter update for NEMOv4 work References: <4534ABA4.2020803@levkowetz.com> In-Reply-To: <4534ABA4.2020803@levkowetz.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 X-OriginalArrivalTime: 18 Oct 2006 06:14:15.0041 (UTC) FILETIME=[A2F41710:01C6F27C] X-Spam-Flag: NO X-Spam-Status: NO, hits=0 required=5 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Cc: mip4-chairs@tools.ietf.org, Mobile IPv4 Mailing List X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi all. +1 from me for including the below NEMOv4 goal into MIP4 charter. BR, Tom P.S. Nitpick: ", such as might" --> ", which might" Henrik Levkowetz wrote: > Hi, >=20 > We're working on a charter update for MIPv4. One of the things > we'd like to add is a work item covering the NEMOv4 specification. >=20 > We'd like to add the following item to the charter: >=20 > 11. NEMO v4 Support >=20 > The Network Mobility (nemo) working group deals with the problem > of mobility of a whole network, such as might exist inside a > vehicle, train, or airplane. The nemo working group has > developed draft specifications for both IPv6 and IPv4 mobile > networks. However, it has been recognized that the IPv4 > version of the protocol can be viewed as an extension of > the basic Mobile IPv4 protocol, and there is good reason > to do this extension in the mip4 working group. The > working group will take on the NEMO v4 internet draft and > progress it along the standards track. >=20 > If you have comments on this, please send them to the list. >=20 > Regerds, >=20 > Henrik and Pete --=20 Tom Weckstr=F6m Secgo Software Oy Lars Sonckin kaari 16, FIN-02600 Espoo Tel:+358 207 402 555 Mobile:+35840 77 230 77 Fax:+35842 77 230 77 -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Wed Oct 18 03:30:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ga5sP-0001IE-2b; Wed, 18 Oct 2006 03:30:09 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ga5sN-0001H8-7Y for mip4@ietf.org; Wed, 18 Oct 2006 03:30:07 -0400 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ga5sM-0004zd-MN for mip4@ietf.org; Wed, 18 Oct 2006 03:30:07 -0400 Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k9I7U2Bb029278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 18 Oct 2006 00:30:03 -0700 Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109]) by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k9I7Ts1g012727; Wed, 18 Oct 2006 00:30:01 -0700 (PDT) Received: from SANEXCAS02.na.qualcomm.com ([172.30.36.176]) by NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Oct 2006 00:25:55 -0700 Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Oct 2006 00:25:54 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Mip4] Proposed charter update for NEMOv4 work Date: Wed, 18 Oct 2006 00:25:51 -0700 Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A24A790@NAEX14.na.qualcomm.com> In-Reply-To: <4534ABA4.2020803@levkowetz.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Proposed charter update for NEMOv4 work Thread-Index: Acbx1KI0ufjcWmkFSG645BP7a8+FAAAsaibA From: "Tsirtsis, George" To: "Henrik Levkowetz" , "Mobile IPv4 Mailing List" X-OriginalArrivalTime: 18 Oct 2006 07:25:54.0994 (UTC) FILETIME=[A5ECD920:01C6F286] X-Spam-Score: 0.0 (/) X-Scan-Signature: 86f85b2f88b0d50615aed44a7f9e33c7 Cc: mip4-chairs@tools.ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org I support the NEMOv4 work for the same reasons Kent/Gopal and others have indicated. George > -----Original Message----- > From: Henrik Levkowetz [mailto:henrik@levkowetz.com] > Sent: Tuesday, October 17, 2006 6:09 AM > To: Mobile IPv4 Mailing List > Cc: mip4-chairs@tools.ietf.org > Subject: [Mip4] Proposed charter update for NEMOv4 work >=20 > Hi, >=20 > We're working on a charter update for MIPv4. One of the things > we'd like to add is a work item covering the NEMOv4 specification. >=20 > We'd like to add the following item to the charter: >=20 > 11. NEMO v4 Support >=20 > The Network Mobility (nemo) working group deals with the problem > of mobility of a whole network, such as might exist inside a > vehicle, train, or airplane. The nemo working group has > developed draft specifications for both IPv6 and IPv4 mobile > networks. However, it has been recognized that the IPv4 > version of the protocol can be viewed as an extension of > the basic Mobile IPv4 protocol, and there is good reason > to do this extension in the mip4 working group. The > working group will take on the NEMO v4 internet draft and > progress it along the standards track. >=20 > If you have comments on this, please send them to the list. >=20 >=20 > Regerds, >=20 > Henrik and Pete >=20 >=20 >=20 > (The resulting full charter text is here: >=20 >=20 > Description of Working Group: >=20 > IP mobility support for IPv4 nodes (hosts and routers) is specified in > RFC3344. RFC 3344 mobility allows a node to continue using its > "permanent" home address as it moves around the Internet. The Mobile > IP protocols support transparency above the IP layer, including > maintenance of active TCP connections and UDP port bindings.Besides > the basic Mobile IPv4 (MIPv4) protocols, several other drafts deal > with concerns such as optimization, security, extensions, AAA support, > and deployment issues. >=20 > MIPv4 is currently being deployed on a wide basis (e.g., in cdma2000 > networks). The scope of the deployment is on a fairly large scale and > accordingly, the MIP4 WG will focus on deployment issues and on > addressing known deficiencies and shortcomings in the protocol that > have come up as a result of deployment experience. Specifically, the > working group will complete the work items to facilitate interactions > with AAA environments, interactions with enterprise environments when > MIPv4 is used therein, and updating existing protocol specifications > in accordance with deployment needs and advancing those protocols that > are on the standards track. >=20 > Work expected to be done by the MIP4 WG as proposed by this charter is > as follows: >=20 > 1. MIPv4 has been a proposed standard for several years. It has been > adopted by other standard development organizations and has been > deployed commercially. One of the next steps for the WG is to advance > the protocol to draft standard status. As part of advancing base > Mobile IP specs to DS, the MIPv4 NAI RFC (2794) will be revised to > reflect implementation experience >=20 > 2. Work items that are pending from the previous Mobile IP WG, which > will be completed by the MIP4 WG, are: >=20 > - completion of the MIB for the revised base Mobile IP specification > (2006bis) >=20 > - regional registration draft. >=20 > 3. The MIP4 WG will also complete the work on MIPv4 interactions in > VPN scenarios. This work will involve identifying the requirements and > a solution development for MIPv4 operation in the presence of IPsec > VPNs. >=20 > 4. Additionally, a proposal has been made for how MOBIKE could work > together with MIPv4. This proposal does not describe any new protocol, > but formulates a best current practice for deploying MOBIKE together > with MIPv4. The working group will adopt and complete this document. >=20 > 5. Some issues have been raised with respect to RFC3519. These will be > identified and addressed as appropriate, through errata, revision of > RFC 3519, and/or supplemental documents as needed. >=20 > 6. It has been proposed that the FMIP protocol, which has been > standardised for MIPv6 in the MIPSHOP working group, should also be > published as an experimental protocol for MIPv4. A draft for this > exists. The working group will take up and carry this work forward to > publication >=20 > 7. An extension to carry generic strings in the Registration Reply > message has been proposed. The purpose is to supply supplemental > human-readable information intended to the MN user. The working group > will complete the specification and applicability statement of such an > extension. >=20 > 8. RADIUS attributes for MIP4. A set of RADIUS attributes has been > proposed for MIPv4. >=20 > The working group will first produce a requirements specification, > describing how the work differs from the requirements in RFC 2977 and > the functionality provided by RFC 4004 (the MIPv4 Diameter App). The > reason why this first step is required is that RFC 3127 shows that > full RFC 2977 functionality can't be provided by even a considerably > extended RADIUS, so we need to match the requirements to what can be > done within RADIUS. >=20 > Provided the requirements work finds approval with ADs and RADEXT WG, > the workgroup will complete the specification of MIPv4 RADIUS > attributes, solicit feedback from the RADEXT WG, adjust, and submit > this for publication. Note that the work may require extensions to the > RADIUS attribute space which will be handled outside the MIP4 WG. >=20 > 9. MIPv4 Extension for Configuration Options. >=20 > Several drafts have proposed extensions to help improve configuration > of MIPv4 clients. The latest proposal is for a general configuration > option extension which could carry information such as e.g., DNS > address and DHCP server address. The working group will take on and > complete one proposal for a configuration option extension. >=20 > 10. Dual-stack Support >=20 > There have been several proposals for how to enable an IPv6 connection > over a network that supports Mobile IPv4. A protocol enhancement to > MIPv4 would allow for IPv6 support in a region where Mobile IPv4 has > already been implemented and deployed. This would allow a dual stack > mobile node to maintain IPv6 connectivity when using MIPv4. The > solution would therefore be applicable only to networks that are > not deploying Mobile IPv6. >=20 > The working group will take on and complete one proposal for IPv6 over > Mobile IPv4. This work is restricted to a small protocol extension > similar to current Mobile IPv4 functionality. Support for advanced > Mobile IPv6 functionality is strictly outside the scope. >=20 > A problem statement covering both Mobile IPv4 and IPv6 dual-stack > issues is expected to come out of MIP6 WG, and will not be developed > in MIP4 WG. >=20 > 11. NEMO v4 Support >=20 > The Network Mobility (nemo) working group deals with the problem > of mobility of a whole network, such as might exist inside a > vehicle, train, or airplane. The nemo working group has > developed draft specifications for both IPv6 and IPv4 mobile > networks. However, it has been recognized that the IPv4 > version of the protocol can be viewed as an extension of > the basic Mobile IPv4 protocol, and there is good reason > to do this extension in the mip4 working group. The > working group will take on the NEMO v4 internet draft and > progress it along the standards track. >=20 > ) -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Wed Oct 18 06:52:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ga929-0001fk-F5; Wed, 18 Oct 2006 06:52:25 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ga926-0001dK-Om for mip4@ietf.org; Wed, 18 Oct 2006 06:52:22 -0400 Received: from m13-19.163.com ([220.181.13.19]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Ga924-0000Br-CT for mip4@ietf.org; Wed, 18 Oct 2006 06:52:22 -0400 Received: from 192.168.208.41(221.221.33.186) ( 192.168.208.41(221.221.33.186) [192.168.208.41(221.221.33.186)] ) by webmail-app19 (Coremail) ; Wed, 18 Oct 2006 18:52:11 +0800 (CST) MIME-Version: 1.0 Message-ID: <4536075B.0000BA.29180@bj163app19.163.com> Date: Wed, 18 Oct 2006 18:52:11 +0800 (CST) From: "liangjing" To: mip4@ietf.org Subject: Re: [Mip4] draft-deng-mip4-generic-notifi cation-message-02.txt X-Priority: 3 X-Originating-IP: [192.168.208.41(221.221.33.186)] X-Mailer: 163com X-Spam-Score: 0.5 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2133638772==" Errors-To: mip4-bounces@ietf.org --===============2133638772== Content-Type: Multipart/Alternative; boundary="Boundary-=_kBItasFnuasIobPaHcMwMNbOCOoR" --Boundary-=_kBItasFnuasIobPaHcMwMNbOCOoR Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit I am in favor of this draft. This draft has proposed the notification message in the comprehensive way. I do believe it is needed in mip4 group charter. Jing Liang --Boundary-=_kBItasFnuasIobPaHcMwMNbOCOoR Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable
I am in favor of this draft. This draft has proposed the notificatio= n message in the comprehensive way. I do believe it is needed in mip= 4 group charter.
 
Jing Liang
 
 
 
 







=0A=0A=09=C3=C0 =C5=AE =BF=D6 =B2=C0 =B0=DC =BC=D2 =D0=E3 (= =D7=E9 =CD=BC ) =0A=09
=0A=09 =B6= =C0 =BC=D2 =C5=FB =C2=B6 ! =D0=A1 =D7=CA =C5=AE =C8=CB 8 =B8=F6 =BE=F8 =B6= =A5 =D2=FE =C3=D8 =B5=C4 =C8=A4 =CA=C2 ( =D7=E9 =CD=BC )=0A=0A=0A --Boundary-=_kBItasFnuasIobPaHcMwMNbOCOoR-- --===============2133638772== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ --===============2133638772==-- From mip4-bounces@ietf.org Wed Oct 18 08:31:16 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaAZU-0006SZ-1p; Wed, 18 Oct 2006 08:30:56 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaAZS-0006ST-Ml for mip4@ietf.org; Wed, 18 Oct 2006 08:30:54 -0400 Received: from csnet1.cs.tsinghua.edu.cn ([166.111.68.226]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GaAZQ-0005cs-GL for mip4@ietf.org; Wed, 18 Oct 2006 08:30:54 -0400 Received: (qmail 13623 invoked by uid 0); 18 Oct 2006 13:02:00 -0000 Received: from th024066.ip.tsinghua.edu.cn (HELO Yong-Cui-at-Tsinghua) (yong@59.66.24.66) by csnet1.cs.tsinghua.edu.cn with SMTP; 18 Oct 2006 13:02:00 -0000 Date: Wed, 18 Oct 2006 20:30:50 +0800 From: "Yong" To: "mip4" Subject: Re: [Mip4] draft-deng-mip4-generic-notification-message-02.txt X-mailer: Foxmail 5.0 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Message-Id: A generic message which is sent directly to mobile node will be much better than multiple unique message. Therefor I support this draft. -Yong > ----- Original Message ---- > From: McCann Peter-A001034 > To: mip4@ietf.org > Sent: Tuesday, October 17, 2006 10:43:58 AM > Subject: [Mip4] draft-deng-mip4-generic-notification-message-02.txt > > > During the last working group meeting, we had a discussion on > draft-deng-mip4-generic-notification-message-02.txt. > There were 3 or 4 people who spoke out in favor of adding this to the > charter. > > I'd like to poll the list on this. Who is in favor of adopting this > as a working group item? Opposed? > > If we get consensus to add this we can do it at the same time as we do > the NEMOv4 addition. > > -Pete > -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Wed Oct 18 08:45:41 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaAnl-0000P0-9a; Wed, 18 Oct 2006 08:45:41 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaAnj-0000ND-B5 for mip4@ietf.org; Wed, 18 Oct 2006 08:45:39 -0400 Received: from [162.105.30.183] (helo=infosec.pku.edu.cn) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaAne-00082j-Hw for mip4@ietf.org; Wed, 18 Oct 2006 08:45:39 -0400 Received: from ibm-k190liobzyy (unknown [162.105.85.137]) by infosec.pku.edu.cn (Postfix) with ESMTP id A165E7ADEA; Wed, 18 Oct 2006 20:44:55 +0800 (CST) Date: Wed, 18 Oct 2006 20:44:55 +0800 From: "Cao, Zhen" To: "Yong" , "mip4" References: Subject: Re: Re: [Mip4] draft-deng-mip4-generic-notification-message-02.txt Message-ID: <200610182044547748868@infosec.pku.edu.cn> Organization: PKU X-mailer: Foxmail 6, 5, 104, 21 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Cc: X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org yes, those unique message could be multiple options of this notification message, I also support this work item. Many thanks, Zhen 2006-10-18 -----Original Message----- From: Yong caozhen@infosec.pku.edu.cn Sent: 2006-10-18 To: mip4 Subject: Re: [Mip4] draft-deng-mip4-generic-notification-message-02.txt > > >A generic message which is sent directly to mobile node will be much >better than multiple unique message. Therefor I support this draft. > >-Yong > >> ----- Original Message ---- >> From: McCann Peter-A001034 >> To: mip4@ietf.org >> Sent: Tuesday, October 17, 2006 10:43:58 AM >> Subject: [Mip4] draft-deng-mip4-generic-notification-message-02.txt >> >> >> During the last working group meeting, we had a discussion on >> draft-deng-mip4-generic-notification-message-02.txt. >> There were 3 or 4 people who spoke out in favor of adding this to the >> charter. >> >> I'd like to poll the list on this. Who is in favor of adopting this >> as a working group item? Opposed? >> >> If we get consensus to add this we can do it at the same time as we do >> the NEMOv4 addition. >> >> -Pete >> > > > > > > >-- >Mip4 mailing list: Mip4@ietf.org > Web interface: https://www1.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html >Supplemental site: http://www.mip4.org/ > -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Wed Oct 18 12:16:10 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaE5R-00033x-VT; Wed, 18 Oct 2006 12:16:09 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaE5Q-0002v9-TP for mip4@ietf.org; Wed, 18 Oct 2006 12:16:08 -0400 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaDvx-0005hL-P1 for mip4@ietf.org; Wed, 18 Oct 2006 12:06:27 -0400 Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-5.cisco.com with ESMTP; 18 Oct 2006 09:06:21 -0700 Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-4.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9IG6LHx000911; Wed, 18 Oct 2006 09:06:21 -0700 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k9IG6LW4014749; Wed, 18 Oct 2006 09:06:21 -0700 (PDT) Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Oct 2006 09:06:20 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Mip4] draft-deng-mip4-generic-notification-message-02.txt Date: Wed, 18 Oct 2006 09:06:20 -0700 Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5202B54449@xmb-sjc-235.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] draft-deng-mip4-generic-notification-message-02.txt Thread-Index: AcbyE9MO39zif61xTK2b0OC/8fCeJQAu3SNQ From: "Kent Leung \(kleung\)" To: "McCann Peter-A001034" , X-OriginalArrivalTime: 18 Oct 2006 16:06:20.0852 (UTC) FILETIME=[59FCA740:01C6F2CF] DKIM-Signature: a=rsa-sha1; q=dns; l=886; t=1161187581; x=1162051581; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=kleung@cisco.com; z=From:=22Kent=20Leung=20\(kleung\)=22=20 |Subject:RE=3A=20[Mip4]=20draft-deng-mip4-generic-notification-message-02.txt; X=v=3Dcisco.com=3B=20h=3DBdXljyQj7EPYTnczmSt+ayULgmo=3D; b=NsrFUmOYuDCe7RyXQaqnOqO2cAhPGPqswYZ70GTKrYnrPaPwCMUUJq8NNKOdW7bE7tnvyM2Z gTHdNRaREq5dldiOcSMKFw0Q5Q2G8HxJahax7o33xdmAOzetBSXzGrQ4; Authentication-Results: sj-dkim-4.cisco.com; header.From=kleung@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Cc: X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Yes, I'm in favor. Kent=20 -----Original Message----- From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com]=20 Sent: Tuesday, October 17, 2006 10:44 AM To: mip4@ietf.org Subject: [Mip4] draft-deng-mip4-generic-notification-message-02.txt During the last working group meeting, we had a discussion on draft-deng-mip4-generic-notification-message-02.txt. There were 3 or 4 people who spoke out in favor of adding this to the charter. I'd like to poll the list on this. Who is in favor of adopting this as a working group item? Opposed? If we get consensus to add this we can do it at the same time as we do the NEMOv4 addition. -Pete -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Wed Oct 18 17:35:28 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaJ44-0001KB-RX; Wed, 18 Oct 2006 17:35:04 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaJ43-0001GB-D7 for mip4@ietf.org; Wed, 18 Oct 2006 17:35:03 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaIrt-0005ym-Pk for mip4@ietf.org; Wed, 18 Oct 2006 17:22:31 -0400 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k9ILMRHw003489 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 18 Oct 2006 14:22:28 -0700 Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com [129.46.134.172]) by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k9ILMG3D023334; Wed, 18 Oct 2006 14:22:27 -0700 (PDT) Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Oct 2006 14:22:23 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Mip4] Proposed charter update for NEMOv4 work Date: Wed, 18 Oct 2006 14:22:29 -0700 Message-ID: In-Reply-To: <4534ABA4.2020803@levkowetz.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Proposed charter update for NEMOv4 work Thread-Index: Acbx1KH5k5LY8/TMRpajHnYp/AO8AgBJtnAQ From: "Narayanan, Vidya" To: "Henrik Levkowetz" , "Mobile IPv4 Mailing List" X-OriginalArrivalTime: 18 Oct 2006 21:22:23.0080 (UTC) FILETIME=[805B0680:01C6F2FB] X-Spam-Score: 0.0 (/) X-Scan-Signature: bf422c85703d3d847fb014987125ac48 Cc: mip4-chairs@tools.ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org I support this work as well.=20 Vidya=20 > -----Original Message----- > From: Henrik Levkowetz [mailto:henrik@levkowetz.com]=20 > Sent: Tuesday, October 17, 2006 3:09 AM > To: Mobile IPv4 Mailing List > Cc: mip4-chairs@tools.ietf.org > Subject: [Mip4] Proposed charter update for NEMOv4 work >=20 > Hi, >=20 > We're working on a charter update for MIPv4. One of the=20 > things we'd like to add is a work item covering the NEMOv4=20 > specification. >=20 > We'd like to add the following item to the charter: >=20 > 11. NEMO v4 Support >=20 > The Network Mobility (nemo) working group deals with the problem > of mobility of a whole network, such as might exist inside a > vehicle, train, or airplane. The nemo working group has > developed draft specifications for both IPv6 and IPv4 mobile > networks. However, it has been recognized that the IPv4 > version of the protocol can be viewed as an extension of > the basic Mobile IPv4 protocol, and there is good reason > to do this extension in the mip4 working group. The > working group will take on the NEMO v4 internet draft and > progress it along the standards track. >=20 > If you have comments on this, please send them to the list. >=20 >=20 > Regerds, >=20 > Henrik and Pete >=20 >=20 >=20 > (The resulting full charter text is here: >=20 >=20 > Description of Working Group: >=20 > IP mobility support for IPv4 nodes (hosts and routers) is=20 > specified in > RFC3344. RFC 3344 mobility allows a node to continue using its > "permanent" home address as it moves around the Internet. The Mobile > IP protocols support transparency above the IP layer, including > maintenance of active TCP connections and UDP port bindings.Besides > the basic Mobile IPv4 (MIPv4) protocols, several other drafts deal > with concerns such as optimization, security, extensions,=20 > AAA support, > and deployment issues. >=20 > MIPv4 is currently being deployed on a wide basis (e.g., in cdma2000 > networks). The scope of the deployment is on a fairly large=20 > scale and > accordingly, the MIP4 WG will focus on deployment issues and on > addressing known deficiencies and shortcomings in the protocol that > have come up as a result of deployment experience. Specifically, the > working group will complete the work items to facilitate=20 > interactions > with AAA environments, interactions with enterprise=20 > environments when > MIPv4 is used therein, and updating existing protocol specifications > in accordance with deployment needs and advancing those=20 > protocols that > are on the standards track. >=20 > Work expected to be done by the MIP4 WG as proposed by this=20 > charter is > as follows: >=20 > 1. MIPv4 has been a proposed standard for several years. It has been > adopted by other standard development organizations and has been > deployed commercially. One of the next steps for the WG is=20 > to advance > the protocol to draft standard status. As part of advancing base > Mobile IP specs to DS, the MIPv4 NAI RFC (2794) will be revised to > reflect implementation experience >=20 > 2. Work items that are pending from the previous Mobile IP WG, which > will be completed by the MIP4 WG, are: >=20 > - completion of the MIB for the revised base Mobile IP specification > (2006bis) >=20 > - regional registration draft. >=20 > 3. The MIP4 WG will also complete the work on MIPv4 interactions in > VPN scenarios. This work will involve identifying the=20 > requirements and > a solution development for MIPv4 operation in the presence of IPsec > VPNs. >=20 > 4. Additionally, a proposal has been made for how MOBIKE could work > together with MIPv4. This proposal does not describe any=20 > new protocol, > but formulates a best current practice for deploying MOBIKE together > with MIPv4. The working group will adopt and complete this document. >=20 > 5. Some issues have been raised with respect to RFC3519.=20 > These will be > identified and addressed as appropriate, through errata, revision of > RFC 3519, and/or supplemental documents as needed. >=20 > 6. It has been proposed that the FMIP protocol, which has been > standardised for MIPv6 in the MIPSHOP working group, should also be > published as an experimental protocol for MIPv4. A draft for this > exists. The working group will take up and carry this work=20 > forward to > publication >=20 > 7. An extension to carry generic strings in the Registration Reply > message has been proposed. The purpose is to supply supplemental > human-readable information intended to the MN user. The=20 > working group > will complete the specification and applicability statement=20 > of such an > extension. >=20 > 8. RADIUS attributes for MIP4. A set of RADIUS attributes has been > proposed for MIPv4. >=20 > The working group will first produce a requirements specification, > describing how the work differs from the requirements in=20 > RFC 2977 and > the functionality provided by RFC 4004 (the MIPv4 Diameter App). The > reason why this first step is required is that RFC 3127 shows that > full RFC 2977 functionality can't be provided by even a considerably > extended RADIUS, so we need to match the requirements to what can be > done within RADIUS. >=20 > Provided the requirements work finds approval with ADs and=20 > RADEXT WG, > the workgroup will complete the specification of MIPv4 RADIUS > attributes, solicit feedback from the RADEXT WG, adjust, and submit > this for publication. Note that the work may require=20 > extensions to the > RADIUS attribute space which will be handled outside the MIP4 WG. >=20 > 9. MIPv4 Extension for Configuration Options. >=20 > Several drafts have proposed extensions to help improve=20 > configuration > of MIPv4 clients. The latest proposal is for a general configuration > option extension which could carry information such as e.g., DNS > address and DHCP server address. The working group will take on and > complete one proposal for a configuration option extension. >=20 > 10. Dual-stack Support >=20 > There have been several proposals for how to enable an IPv6=20 > connection > over a network that supports Mobile IPv4. A protocol enhancement to > MIPv4 would allow for IPv6 support in a region where Mobile IPv4 has > already been implemented and deployed. This would allow a dual stack > mobile node to maintain IPv6 connectivity when using MIPv4. The > solution would therefore be applicable only to networks that are > not deploying Mobile IPv6. >=20 > The working group will take on and complete one proposal=20 > for IPv6 over > Mobile IPv4. This work is restricted to a small protocol extension > similar to current Mobile IPv4 functionality. Support for advanced > Mobile IPv6 functionality is strictly outside the scope. >=20 > A problem statement covering both Mobile IPv4 and IPv6 dual-stack > issues is expected to come out of MIP6 WG, and will not be developed > in MIP4 WG. >=20 > 11. NEMO v4 Support >=20 > The Network Mobility (nemo) working group deals with the problem > of mobility of a whole network, such as might exist inside a > vehicle, train, or airplane. The nemo working group has > developed draft specifications for both IPv6 and IPv4 mobile > networks. However, it has been recognized that the IPv4 > version of the protocol can be viewed as an extension of > the basic Mobile IPv4 protocol, and there is good reason > to do this extension in the mip4 working group. The > working group will take on the NEMO v4 internet draft and > progress it along the standards track. >=20 > ) >=20 >=20 -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Thu Oct 19 11:07:44 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaZUi-0002Fo-Bb; Thu, 19 Oct 2006 11:07:40 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaSg9-0000wL-BH for mip4@ietf.org; Thu, 19 Oct 2006 03:51:01 -0400 Received: from mail.sis.pitt.edu ([136.142.116.22]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaSf5-00062Q-A9 for mip4@ietf.org; Thu, 19 Oct 2006 03:49:56 -0400 Received: from gis39 (gis39.exp.sis.pitt.edu [136.142.118.94]) by mail.sis.pitt.edu (8.13.8/8.13.8) with ESMTP id k9J7nrW9004771 for ; Thu, 19 Oct 2006 03:49:53 -0400 (EDT) Date: Thu, 19 Oct 2006 03:49:53 -0400 (EDT) Message-ID: <27837671.1771161244195843.JavaMail.javamailuser@localhost> From: James Joshi To: mip4@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.56 on 136.142.116.22 X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca X-Mailman-Approved-At: Thu, 19 Oct 2006 11:07:39 -0400 Subject: [Mip4] CFP NetCri-07 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org [Apologies for multiple postings] The First International Workshop on Research Challenges in Next Generation Networks for First Responders and Critical Infrastructures http://www.cs.umd.edu/~sharno/NetCri07/ In conjunction with The IEEE IPCCC 2007, New Orleans, Louisiana, April 11-13 http://www.ipccc.org/ =================================================================== Program Description ------------------- As advances in pervasive computing, wireless communication and sensor networks continue, more opportunities are open to first responders and critical infrastructures to benefit from these technologies. Providing first responders with the best possible technology, infrastructure and services help save the lives of the general public and the first responders as well. One of the main challenges to the operations of first responders and critical infrastructures is to deploy a communication network that is dependable, secure, and rapidly deployable. In order to operate effectively, the deployed network supports services such as location determination, audio and video communication, and in site and remote sensing. Another key feature for first responders and critical infrastructures networks is to support interactions among multiple heterogeneous networks. This workshop provides a forum for researchers, industry, and government agencies to discuss the challenges facing the design, deployment and operational issues for next generation network support for first responders and critical infrastructure. The workshop will identify and define fundamental concepts and techniques, resolve conflicts between different approaches in the area, and provide a common ground for an advanced research and development agenda. Topics of interest include, but are not limited to: - Smart environments (buildings, roads, vehicles, etc.) - Fast roaming in heterogonous network environment - Localization and time synchronization - Rapidly deployable and self configuring services and networks - Security, dependability, privacy, and performance trade-offs - QoS in heterogeneous wireless networks - Sensor and actuator networks for information gathering and real-time control - Network and system support for augmented reality and visual analytics - Test beds - Simulation studies of first responders and critical infrastructures? networks - Novel and adaptive communication protocols to support first responders and critical infrastructure? operation - Resource management and allocation - Power control management - Admission, load and flow control - Performance analysis and experimentation of heterogeneous wireless networks - Security techniques and methods for heterogeneous wireless networks - Interoperability among WLANs, Cellular, WSN and wired networks - Measurements on heterogeneous networks - Mobility models and traffic patterns in disaster areas - Cross-layer design Workshop Co-chairs ------------------ Mohamed Eltoweissy, Virginia Tech, USA Moustafa Youssef, University of Maryland, USA -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Thu Oct 19 17:13:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GafCl-0006Hz-K8; Thu, 19 Oct 2006 17:13:31 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GafCU-0004ms-TC for mip4@ietf.org; Thu, 19 Oct 2006 17:13:14 -0400 Received: from mail125.messagelabs.com ([85.158.136.35]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GafCT-0003S2-Fd for mip4@ietf.org; Thu, 19 Oct 2006 17:13:14 -0400 X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-14.tower-125.messagelabs.com!1161292386!17818822!1 X-StarScan-Version: 5.5.10.7; banners=-,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 27926 invoked from network); 19 Oct 2006 21:13:06 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-14.tower-125.messagelabs.com with SMTP; 19 Oct 2006 21:13:06 -0000 Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id k9JLD5Fb021298 for ; Thu, 19 Oct 2006 14:13:05 -0700 (MST) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id k9JLD4c0028854 for ; Thu, 19 Oct 2006 16:13:05 -0500 (CDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Thu, 19 Oct 2006 17:13:04 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: WGLC: draft-ietf-mip4-gen-ext-00.txt Thread-Index: Acbzw12ZV2XXQ8hdREG211R3NLzWBQ== From: "McCann Peter-A001034" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa X-Mailman-Approved-At: Thu, 19 Oct 2006 17:13:31 -0400 Cc: Henrik Levkowetz Subject: [Mip4] WGLC: draft-ietf-mip4-gen-ext-00.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org This message announces a WG last call on: "MIPv4 Extension for Configuration Options Exchange" draft-ietf-mip4-gen-ext-00.txt The last call will conclude at 24:00 UTC on Friday, 3 November 2006. "MIPv4 Extension for Configuration Options Exchange" describes new Mobile IPv4 extensions for carrying configuration information, where the information is formatted according to existing DHCP configuration options. A URL for this internet draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-gen-ext-00.txt Please respond to this WG last call: * If you have no comments on the draft, and support its advancement, simply respond with a line containing something like "I support the advancement of this document to the IESG with a request for publication as proposed standard." If you have comments, please use a line similar to the one above, and supplement this with your comments. * If you *don't* support its advancement, respond with a line containing something like the following, supplemented by your comments - "I don't support the advancement of this document to the IESG with a request for publication as proposed standard, for the following reasons:" ... Pete & Henrik -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Thu Oct 19 21:45:37 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GajS5-0007rt-M3; Thu, 19 Oct 2006 21:45:37 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GajS4-0007qQ-Kx for mip4@ietf.org; Thu, 19 Oct 2006 21:45:36 -0400 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GajRx-0000CJ-Ru for mip4@ietf.org; Thu, 19 Oct 2006 21:45:36 -0400 Received: from wee.isi.edu (wee.isi.edu [128.9.168.112]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id k9K1j6D8012645 for ; Thu, 19 Oct 2006 18:45:06 -0700 (PDT) From: Wei Ye To: mip4@ietf.org Content-Type: text/plain; charset=UTF-8 Date: Thu, 19 Oct 2006 18:45:05 -0700 Message-Id: <1161308705.5170.39.camel@wee.isi.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 (2.6.3-1.fc5.5) X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: weiye@isi.edu Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by boreas.isi.edu id k9K1j6D8012645 X-Spam-Score: 0.6 (/) X-Scan-Signature: 4d9aaf4f837d0910b987cb9188300fdd Subject: [Mip4] ACM SenSys'06 call for participation X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Our apologies if you have received multiple copies. --------------- Cut off date for early registration is *October 30, 2006*: http://www.regonline.com/Checkin.asp?EventId=3D97157 Conference Hotels: Rooms at the Boulderado are still available. http://www.boulderado.com/ Rate: $129/night (Group code: ACM) Bus service will pick up at the offical SenSys hotels. --------------- ACM SenSys 2006 - Call for Participation The 4th ACM Conference on Embedded Networked Sensor Systems http://sensys.acm.org/2006/ Boulder, Colorado, USA October 31 - November 3, 2006 In the short period since its inception in Los Angeles in 2003, SenSys has risen to become the leading forum for reporting on new, exciting, and technically important research in the field of sensor networks. Please note that the cut off dates for the conference hotels and early registration are September 29 and October 30, respectively. This year we have a stellar conference for you that includes: * A keynote by David Carlson Director, International Polar Year Program Office, and formally, Director of the Atmospheric Technology Division of the US National Centre for Atmospheric Research (NCAR). * 24 technical papers * 29 Sensor network demos * 19 Posters - representing early results and work-in-progress * 2 one day workshops on emerging and important new topics in sensor networks. The workshops will be held the day prior to the main technical program + First Workshop on World-Sensor-Web: Mobile Device Centric Sensory Networks and Applications http://www.sensorplanet.org/wsw2006/ + First Workshop on Distributed Smart Cameras http://www.iti.tugraz.at/dsc06/ Registration is now open: http://www.regonline.com/Checkin.asp?EventId=3D97157 Important Dates: Cut off date for reduced hotel rates is *September 29, 2006* Cut off date for early registration is *October 30, 2006* Please book and register today to guarantee the best rates. One behalf of the whole organizing team we very much look forward to seeing you at SenSys in Boulder! Best regards, Andrew T. Campbell SenSys 2006 General Chair Thanks to our sponsors: ACM SIGCOMM, SIGMOBILE, SIGARCH, SIGOPS, SIGMETRICS, SIGBED NSF, NCAR, ISTS, Crossbow, Intel, Microsoft Research, Moteiv, Nokia Below you'll find the technical program. Please go to http://sensys.acm.org/2006/ for more information. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D **Technical Program, Demos, and Posters** =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Wednesday, November 1 08:15-08:30 Opening announcements 08:30-10:00 Keynote David Carlson Director, International Polar Year Program Office 10:00-10:30 Break 10:30-12:00 Operating Systems t-kernel: Providing Reliable OS Support to Wireless Sensor Networks Lin Gu, John A. Stankovic (University of Virginia) Run-time Dynamic Linking for Reprogramming Wireless Sensor Networks Adam Dunkels, Niclas Finne, Joakim Eriksson, Thiemo Voigt (Swedish Institute of Computer Science) Protothreads: Simplifying Event-Driven Programming of Memory- Constrained Embedded Systems Adam Dunkels, Oliver Schmidt, Thiemo Voigt (Swedish Institute of Computer Science), Muneeb Ali (TU Delft) 12:00-13:30 Lunch 13:30-14:30 Sensing Capturing High-Frequency Phenomena Using a Bandwidth-Limited Sensor Network Ben Greenstein, Christopher Mar, Alex Pesterev, Shahin Farshchi, Eddie Kohler, Jack Judy, Deborah Estrin (UCLA) Virtual High-resolution for Sensor Networks Aman Kansal, William J. Kaiser, Gregory J. Pottie, Mani B. Srivastava (UCLA) and Gaurav Sukhatme (USC) 14:30-15:00 Break 15:00 -16:30 Routing and Dissemination RBP: Robust Broadcast Propagation in Wireless Networks Fred Stann (Amgen), John Heidemann, Rajesh Shroff, Muhammad Zaki Murtaza (USC/ISI) Interest Dissemination with Directional Antenna for Wireless Sensor Networks with Mobile Sinks Yihong Wu, Xiaobo Chen, Lin Zhang, Zhisheng Niu (Tsinghua University) Lazy Cross-Link Removal for Geographic Routing Young-Jin Kim, Ramesh Govindan (USC), Brad Karp (University Colledge London), Scott Shenker (UCB) 18:30-22:30 Banquet at the Walnut Brewery Boulder's Original Brew Pub 1123 Walnut Street Thursday, November 2 09:00-10:00 Configuration StarDust: A Flexible Architecture for Passive Localization in Wireless Sensor Networks Radu Stoleru, Pascal Vicaire, Tian He, John A. Stankovic (University of Virginia) The Design and Implementation of a Self-Calibrating Distributed Acoustic Sensing Platform Lewis Girod (MIT/CSAIL), Martin Lukac, Vlad Trifa, Deborah Estrin (UCLA) 10:00-10:30 Break 10:30-11:30 In-network Processing Target Tracking with Binary Proximity Sensors: Fundamental Limits, Minimal Descriptions, and Algorithms Nisheeth Shrivastava, Raghuraman Mudumbai, Upamanyu Madhow, Subhash Suri (UCSB) Data Compression Algorithms for Energy-Constrained Devices in Delay Tolerant Networks Christopher M. Sadler, Margaret Martonosi (Princeton University) 11:30-13:00 Lunch 13:00-14:30 Radio Propagation and Transport Datalink Streaming in Wireless Sensor Networks Raghu K. Ganti, Praveen Jayachandran, Tarek F. Abdelzaher, and Haiyun Luo (UIUC) ATPC: Adaptive Transmission Power Control for Wireless Sensor Shan Lin (University of Virginia), Tian He (University of Minnesota), Jingbin Zhang, Gang Zhou, Lin Gu, John A. Stankovic (University of Virginia) Experimental Study of Concurrent Transmission in Wireless Sensor Networks Dongjin Son, Bhaskar Krishnamachari (USC), John Heidemann (USC/ISI) 14:30-15:00 Break 15:00-16:30 Storage and Abstractions Abstractions for Safe Concurrent Programming in Networked Embedded Systems William P. McCartney, Nigamanth Sridhar (Cleveland State University) Scalable Data Aggregation for Dynamic Events in Sensor Networks Kai-Wei Fan, Sha Liu, Prasun Sinha (The Ohio State University) An Energy-Optimized Object Storage System for Memory-Constrained Sensor Devices Gaurav Mathur, Peter Desnoyers, Deepak Ganesan, Prashant Shenoy (University of Massachusetts, Amherst) 16:30-20:00 Demonstration and poster session List of accepted demonstrations and posters http://sensys.acm.org/2006/demo_poster.html 20:00-21:00 TinyOS Alliance BoF Friday, November 3 08:30-10:00 Architecture CarTel: A Distributed Mobile Sensor Computing System Bret Hull, Vladimir Bychkovsky, Yang Zhang, Kevin Chen, Michel Goraczko, Allen Miu, Eugene Shih, Hari Balakrishnan, Samuel Madden (MIT/CSAIL) MELETE: Supporting Concurrent Applications in Wireless Sensor Networks Yang Yu, Loren Rittle (Motorola Labs), Jason LeBrun (UCD), Vartika Bhandari (UIUC) The Tenet Architecture for Tiered Sensor Networks Omprakash Gnawali (USC), Ben Greenstein (UCLA), Ki-Young Jang (USC), August Joki (UCLA), Jeongyeup Paek, Marcos Vieira (USC), Deborah Estrin (UCLA), Ramesh Govindan (USC), Eddie Kohler (UCLA) 10:00-10:30 Break 10:30-12:00 Media Access Control Funneling-MAC: A Localized, Sink-Oriented MAC for Boosting Fidelity in Sensor Networks Gahng-Seop Ahn (Columbia University), Emiliano Miluzzo, Andrew T. Campbell (Dartmouth College), Se Gi Hong (Columbia University), Francesca Cuomo (University of Rome "La Sapienza") X-MAC: A Short Preamble MAC Protocol for Duty-Cycled Wireless Sensor Networks Michael Buettner, Gary V. Yee, Eric Anderson, Richard Han (University of Colorado, Boulder) Ultra-Low Duty Cycle MAC with Scheduled Channel Polling Wei Ye, Fabio Silva, John Heidemann (USC/ISI) 12:00-12:15 Best Talk Award and Closing 14:30-16:30 NCAR Tour (optional) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ***************DEMOS********************* =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D SignetLab: Deployable Sensor Network Testbed and Management Tool Riccardo Crepaldi, Albert F Harris III, Alberto Scarpa, Andrea Zanella, Michele Zorzi (University of Padova) An Eventual Consistent Wireless Light Control System Jeonghoon Kang (Korea Electronics Technology Institute), Alec Woo (Arch Rock), Junejae Yoo, Myunghyun Yoon (Korea Electronics Technology Institute) Data Analysis Tools for Sensor-Based Science Stuart Ozer (Microsoft Research), Alex Szalay (Johns Hopkins University), Jim Gray (Microsoft Research), Andreas Terzis, Razvan Musaloiu-E., Katalin Szlavecz, Josh Cogan, Randal Burns (Johns Hopkins University) Data Collection in Delay Tolerant Mobile Sensor Networks using SCAR Cecilia Mascolo, Mirco Musolesi, Bence Pasztor (University College London) cCAM: Ultra Compact, High Data-Rate Wireless Sensor Node with a Miniature Camera Chulsung Park, Pai H. Chou (UCI) Using Grid Technologies to Optimise a Wireless Sensor Network for Flood Management Danny Hughes, Phil Greenwood, Geoff Coulson, Gordon Blair, Barry Porter, Paul Grace, Florian Pappenberger, Paul Smith, Keith Beven (Lancaster University) A Funneling-MAC for High Performance Data Collection in Sensor Networks Gahng-Seop Ahn (Columbia University) Emiliano Miluzzo, Andrew T. Campbell (Dartmouth College) A Storage-centric Camera Sensor Network Gaurav Mathur, Paul Chukiu, Peter Desnoyers, Deepak Ganesan, Prashant Shenoy (University of Massachusetts) Real-Time Volcanic Earthquake Localization Geoffrey Werner-Allen, Patrick Swieskowski, Matt Welsh (Harvard University) Low Power, Low Cost, Wireless Camera Sensor Nodes For Human Detection Jason Schlessman, Jaechang Shim, Ikdong Kim, Yun Cheol Baek, Wayne Wolf (Princeton University) A Unified Architecture for Flexible Radio Power Management in Wireless Sensor Networks Kevin Klues, Guoliang Xing, Chenyang Lu (Washington University) A Self-Calibrating Distributed Acoustic Sensing Platform Lewis D Girod (MIT/CSAIL), Martin Lukac (UCLA), Vladimir Trifa (EPFL), Deborah Estrin (UCLA) A Virtualizing OS Kernel for Wireless Sensor Networks Lin Gu, John A Stankovic (University of Virginia) Flexible Hardware/Software Platform for Tracking Applications Junaid Ansari, Jos=C3=83=C2=A9 S=C3=83=C2=A1nchez, Marina Petrova, Janne = Riihij=C3=83=C2=A4rvi, Ossi Raivio, Krisakorn Rerkrai, Chirstine Jardak, Frank Oldewurtel, Mathias Wellens, Lili Wu, Petri M=C3=83=C2=A4h=C3=83=C2=B6nen (RWTH Aachen Univer= sity) Simple Sensor Syndiciation Michael Colagrosso, Wade Simmons, Marianne Graham (Colorado School of Mines) Responsive and Energy-Efficient Sensor Networking for Real Time Location Tracking Henoc Agbota, Mike Hazas (Lancaster University) Demonstrating Distributed Signal Strength Location Estimation Neal Patwari (University of Utah), Alfred O. Hero (University of Michigan) Sensing and Reproducing the Shapes of 3D Objects Using Claytronics Padmanabhan Pillai, Jason Campbell (Intel Research Pittsburgh) Cascades: An Extensible Heterogeneous Sensor Networking Framework Phillip Sitbon, Nirupama Bulusu, Wu-Chi Feng (Portland State University) LiteOS - A Lightweight Operating System for C++ Software Development in Sensor Networks Qing Cao, Tarek Abdelzaher (UIUC) GRAIL: General Real-Time Adaptable Indoor Localization Yingying Chen (Rutgers University), Eiman Elnahrawy (Kordinate LLC), John-Austen Francisco, Konstantinos Kleisouris (Rutgers University), Xiaoyan Li (Lafayette College), Hongyi Xue (Rutgers University), Richard P. Martin (Rutgers University and Kordinate LLC) A Hierarchical Location Directory Service Across Sensor and IP Networks Sangeeta Bhattacharya, Chien-Liang Fok, Chenyang Lu, Gruia-Catalin Roman (Washington University) Software Radio Implementation of Short-range Wireless Standards for Sensor Networking Thomas Schmid, Tad Dreier, Mani B. Srivastava (UCLA) The CarTel Mobile Sensor Computing System Vladimir L Bychkovsky, Kevin Chen, Michel Goraczko, Hongyi Hu, Bret W Hull, Allen K Miu, Eugene I Shih, Yang Zhang (MIT) TOSDev: A Rapid Development Environment for TinyOS William P McCartney, Nigamanth Sridhar (Cleveland State University) Step-wise Context Extraction in AoK Mule System Yuichi Uehara, Masato Mori, Nayuta Ishii (Tokyo Denki University), Yoh Shiraishi (The University of Tokyo) Yoshito Tobe (Tokyo Denki University) SensorMap: A Web Site for Sensors World-Wide Suman Nath, Jie Liu, Jessica Miller, Feng Zhao (Microsoft Research), Andre Santanche (UNICAMP) Mobility Centric Campus Area Sensor Network for Locality Specific Applications Mukundan Sridharan, Anish Arora, Rajiv Ramnath, Emre Ertin (The Ohio State University) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ***************Posters******************* =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Routing and Processing Multiple Aggregate Queries in Sensor Networks Niki Trigoni, Alexandre Guitton, Antonios Skordylis (University of London) Rateless Codes for Data Dissemination in Sensor Networks Andrew Hagedorn, David Starobinski, Ari Trachtenberg (Boston University) AMSecure: Secure Link-Layer Communication in TinyOS for IEEE 802.15.4- based Wireless Sensor Networks Anthony D Wood, John A Stankovic (University of Virginia) Virtual Sensing Range Emiliano Miluzzo, Nicholas D Lane, Andrew T Campbell (Dartmouth College) uScan: A Lightweight Two-Tier Global Sensing CoverageDesign Yu Gu, Tian He (University of Minnesota) SkiScape Sensing Shane B. Eisenman (Columbia University), Andrew T. Campbell (Dartmouth College) Channel Surfing: Defending WirelessSensor Networks from Jamming and Interference Wenyuan Xu, Wade Trappe, Yanyong Zhang (Rutgers University) Energy Adaptation Techniques to Optimize Data Delivery in Store-and- Forward Sensor Networks Pei Zhang, Margaret Martonosi (Princeton Unviersity) A Distributed Reliable Data Transport Strategy for Event Based Wireless Sensor Networks Yuyan Xue, Byrav Ramamurthy, Ying Lu (University of Nebraska - Lincoln) Lowering Radio Duty Cycle Through Temperature Compensated Timing Joakim Arfvidsson, Eric Park, Philip Levis (Stanford University) Collaborative Scheduling of Event Types and Allocation of Rates for Wireless Sensor Nodes with Multiple Sensing Units Hidayet Ozgur Sanli, Hasan Cam (Arizona State University) Kaizen: Improving Sensor Network Operating Systems James Horey, Jean-Charles Tournier, Arthur B Maccabe (University of New Mexico) Achieving Realistic Sensing Area Modeling Joengmin Hwang, Tian He, Yongdae Kim (University of Minnesota) Is Data-Centric Storage and Querying Scalable? Joon Ahn, Bhaskar Krishnamachari (USC) Understanding the Causes of Packet Delivery Success and Failure in Dense Wireless Sensor Networks Kannan Srinivasan (Stanford University), Prabal Dutta, Arsalan Tavakoli (UCB), Philip Levis (Stanford University) WaveScope: A Signal-Oriented Data Stream Management System Lewis Girod, Kyle Jamieson, Yuan Mei, Ryan Newton, Stanislav Rost, Arvind Thiagarajan, Hari Balakrishnan, Samuel Madden (MIT/CSAIL) Comprehensive Monitoring of CO2 Sequestration in Subalpine Forest Ecosystems and its Relation to Global Warming Lynette L. Laffea, Russ K. Monson, Ryan Manning, Ashly Glasser, Richard Han (University of Colorado, Boulder), Steve Oncley, Jielun Sun, Sean Burns, Steve Semmer, John Militzer (NCAR) TINX A Tiny Index Design for Flash Memory on Wireless Sensor Devices Ajay Mani, Manjunath B Rajashekhar, Philip Levis (Stanford University) Wireless Sensor Networks for Structural Health Monitoring Sukun Kim, Shamim Pakzad, David Culler, James Demmel, Gregory Fenves, Steve Glaser (UCB), Martin Turon (Crossbow) -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Fri Oct 20 11:41:39 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GawV0-0001ID-Qe; Fri, 20 Oct 2006 11:41:30 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GawUz-0001I8-CC for mip4@ietf.org; Fri, 20 Oct 2006 11:41:29 -0400 Received: from [219.239.227.109] (helo=act.buaa.edu.cn) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GawUr-0004xE-Jk for mip4@ietf.org; Fri, 20 Oct 2006 11:41:29 -0400 Received: from [219.224.167.69] [219.239.227.196] by act.buaa.edu.cn with ESMTP (SMTPD32-8.02) id A80A1A900D0; Fri, 20 Oct 2006 23:15:22 +0800 Message-ID: <4538E808.90305@cse.buaa.edu.cn> Date: Fri, 20 Oct 2006 23:15:20 +0800 From: Qin Li User-Agent: Thunderbird 1.5.0.7 (X11/20060927) MIME-Version: 1.0 To: pete.mccann@motorola.com Subject: RE: [Mip4] draft-deng-mip4-generic-notification-message-02.txt X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Cc: mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Yes, I'm in favor of adopt this draft. -----Original Message----- From: pete.mccann@motorola.com Sent: Tuesday, October 17, 2006 10:44 AM To: mip4@ietf.org Subject: [Mip4] draft-deng-mip4-generic-notification-message-02.txt During the last working group meeting, we had a discussion on draft-deng-mip4-generic-notification-message-02.txt. There were 3 or 4 people who spoke out in favor of adding this to the charter. I'd like to poll the list on this. Who is in favor of adopting this as a working group item? Opposed? If we get consensus to add this we can do it at the same time as we do the NEMOv4 addition. -Pete -- Mip4 mailing list: Mip4 at ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Fri Oct 20 11:50:44 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gawdv-0000Br-Oc; Fri, 20 Oct 2006 11:50:43 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gawdv-0000Bl-0L for mip4@ietf.org; Fri, 20 Oct 2006 11:50:43 -0400 Received: from mail119.messagelabs.com ([216.82.241.179]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gawds-0006PJ-JM for mip4@ietf.org; Fri, 20 Oct 2006 11:50:42 -0400 X-VirusChecked: Checked X-Env-Sender: alexandru.petrescu@motorola.com X-Msg-Ref: server-11.tower-119.messagelabs.com!1161359436!11115131!1 X-StarScan-Version: 5.5.10.7; banners=-,-,- X-Originating-IP: [129.188.136.100] Received: (qmail 13751 invoked from network); 20 Oct 2006 15:50:36 -0000 Received: from motgate.mot.com (HELO motgate.mot.com) (129.188.136.100) by server-11.tower-119.messagelabs.com with SMTP; 20 Oct 2006 15:50:36 -0000 Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234]) by motgate.mot.com (Motorola/Motorola) with ESMTP id k9KFoZOr002793; Fri, 20 Oct 2006 08:50:35 -0700 (MST) Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117]) by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id k9KFoRgN029156; Fri, 20 Oct 2006 10:50:33 -0500 (CDT) Message-ID: <4538F042.20804@motorola.com> Date: Fri, 20 Oct 2006 17:50:26 +0200 From: Alexandru Petrescu User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Henrik Levkowetz Subject: Re: [Mip4] Proposed charter update for NEMOv4 work References: <4534ABA4.2020803@levkowetz.com> In-Reply-To: <4534ABA4.2020803@levkowetz.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f Cc: mip4-chairs@tools.ietf.org, Mobile IPv4 Mailing List X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org I too support adoption of WG items related to IPv4 network mobility. I'm co-authoring the NEMOv4 draft. I've parallely requested a short presentation slot in San Diego meeting. The draft is at ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-nemo-v4-base-01.txt It's actually a third revision, since it existed as a personal proposal in NEMO WG, prior to being a WG item there. The authorship didn't change much since first incarnation, however, the Ack section was updated to reflect several improvements on the draft. Looking forward, Alex Henrik Levkowetz wrote: > Hi, > > We're working on a charter update for MIPv4. One of the things we'd > like to add is a work item covering the NEMOv4 specification. > > We'd like to add the following item to the charter: > > 11. NEMO v4 Support > > The Network Mobility (nemo) working group deals with the problem of > mobility of a whole network, such as might exist inside a vehicle, > train, or airplane. The nemo working group has developed draft > specifications for both IPv6 and IPv4 mobile networks. However, it > has been recognized that the IPv4 version of the protocol can be > viewed as an extension of the basic Mobile IPv4 protocol, and there > is good reason to do this extension in the mip4 working group. The > working group will take on the NEMO v4 internet draft and progress it > along the standards track. > > If you have comments on this, please send them to the list. > > > Regerds, > > Henrik and Pete > > > > (The resulting full charter text is here: > > > Description of Working Group: > > IP mobility support for IPv4 nodes (hosts and routers) is specified > in RFC3344. RFC 3344 mobility allows a node to continue using its > "permanent" home address as it moves around the Internet. The Mobile > IP protocols support transparency above the IP layer, including > maintenance of active TCP connections and UDP port bindings.Besides > the basic Mobile IPv4 (MIPv4) protocols, several other drafts deal > with concerns such as optimization, security, extensions, AAA > support, and deployment issues. > > MIPv4 is currently being deployed on a wide basis (e.g., in cdma2000 > networks). The scope of the deployment is on a fairly large scale > and accordingly, the MIP4 WG will focus on deployment issues and on > addressing known deficiencies and shortcomings in the protocol that > have come up as a result of deployment experience. Specifically, the > working group will complete the work items to facilitate > interactions with AAA environments, interactions with enterprise > environments when MIPv4 is used therein, and updating existing > protocol specifications in accordance with deployment needs and > advancing those protocols that are on the standards track. > > Work expected to be done by the MIP4 WG as proposed by this charter > is as follows: > > 1. MIPv4 has been a proposed standard for several years. It has been > adopted by other standard development organizations and has been > deployed commercially. One of the next steps for the WG is to advance > the protocol to draft standard status. As part of advancing base > Mobile IP specs to DS, the MIPv4 NAI RFC (2794) will be revised to > reflect implementation experience > > 2. Work items that are pending from the previous Mobile IP WG, which > will be completed by the MIP4 WG, are: > > - completion of the MIB for the revised base Mobile IP specification > (2006bis) > > - regional registration draft. > > 3. The MIP4 WG will also complete the work on MIPv4 interactions in > VPN scenarios. This work will involve identifying the requirements > and a solution development for MIPv4 operation in the presence of > IPsec VPNs. > > 4. Additionally, a proposal has been made for how MOBIKE could work > together with MIPv4. This proposal does not describe any new > protocol, but formulates a best current practice for deploying MOBIKE > together with MIPv4. The working group will adopt and complete this > document. > > 5. Some issues have been raised with respect to RFC3519. These will > be identified and addressed as appropriate, through errata, revision > of RFC 3519, and/or supplemental documents as needed. > > 6. It has been proposed that the FMIP protocol, which has been > standardised for MIPv6 in the MIPSHOP working group, should also be > published as an experimental protocol for MIPv4. A draft for this > exists. The working group will take up and carry this work forward to > publication > > 7. An extension to carry generic strings in the Registration Reply > message has been proposed. The purpose is to supply supplemental > human-readable information intended to the MN user. The working group > will complete the specification and applicability statement of such > an extension. > > 8. RADIUS attributes for MIP4. A set of RADIUS attributes has been > proposed for MIPv4. > > The working group will first produce a requirements specification, > describing how the work differs from the requirements in RFC 2977 and > the functionality provided by RFC 4004 (the MIPv4 Diameter App). The > reason why this first step is required is that RFC 3127 shows that > full RFC 2977 functionality can't be provided by even a considerably > extended RADIUS, so we need to match the requirements to what can be > done within RADIUS. > > Provided the requirements work finds approval with ADs and RADEXT WG, > the workgroup will complete the specification of MIPv4 RADIUS > attributes, solicit feedback from the RADEXT WG, adjust, and submit > this for publication. Note that the work may require extensions to > the RADIUS attribute space which will be handled outside the MIP4 WG. > > > > 9. MIPv4 Extension for Configuration Options. > > Several drafts have proposed extensions to help improve configuration > of MIPv4 clients. The latest proposal is for a general configuration > option extension which could carry information such as e.g., DNS > address and DHCP server address. The working group will take on and > complete one proposal for a configuration option extension. > > 10. Dual-stack Support > > There have been several proposals for how to enable an IPv6 > connection over a network that supports Mobile IPv4. A protocol > enhancement to MIPv4 would allow for IPv6 support in a region where > Mobile IPv4 has already been implemented and deployed. This would > allow a dual stack mobile node to maintain IPv6 connectivity when > using MIPv4. The solution would therefore be applicable only to > networks that are not deploying Mobile IPv6. > > The working group will take on and complete one proposal for IPv6 > over Mobile IPv4. This work is restricted to a small protocol > extension similar to current Mobile IPv4 functionality. Support for > advanced Mobile IPv6 functionality is strictly outside the scope. > > A problem statement covering both Mobile IPv4 and IPv6 dual-stack > issues is expected to come out of MIP6 WG, and will not be developed > in MIP4 WG. > > 11. NEMO v4 Support > > The Network Mobility (nemo) working group deals with the problem of > mobility of a whole network, such as might exist inside a vehicle, > train, or airplane. The nemo working group has developed draft > specifications for both IPv6 and IPv4 mobile networks. However, it > has been recognized that the IPv4 version of the protocol can be > viewed as an extension of the basic Mobile IPv4 protocol, and there > is good reason to do this extension in the mip4 working group. The > working group will take on the NEMO v4 internet draft and progress it > along the standards track. > > ) > > -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Fri Oct 20 12:23:46 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gax9u-0003Zp-1f; Fri, 20 Oct 2006 12:23:46 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gax9t-0003Zk-Ez for mip4@ietf.org; Fri, 20 Oct 2006 12:23:45 -0400 Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gax9r-00043I-0w for mip4@ietf.org; Fri, 20 Oct 2006 12:23:45 -0400 Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 20 Oct 2006 18:23:43 +0200 Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by ams-dkim-2.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9KGNfeA004539; Fri, 20 Oct 2006 18:23:41 +0200 Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com [64.104.123.69]) by hkg-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k9KGNcVt005510; Sat, 21 Oct 2006 00:23:38 +0800 (CST) Received: from xmb-hkg-416.apac.cisco.com ([64.104.123.88]) by xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 21 Oct 2006 00:23:37 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Mip4] WGLC: draft-ietf-mip4-gen-ext-00.txt Date: Sat, 21 Oct 2006 00:23:36 +0800 Message-ID: <35912544FC930E49BF20EF16C3EF27650191597F@xmb-hkg-416.apac.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] WGLC: draft-ietf-mip4-gen-ext-00.txt Thread-Index: Acbzw12ZV2XXQ8hdREG211R3NLzWBQAnfKwg From: "Yoshi Tsuda \(yotsuda\)" To: "McCann Peter-A001034" , X-OriginalArrivalTime: 20 Oct 2006 16:23:37.0962 (UTC) FILETIME=[18FA94A0:01C6F464] DKIM-Signature: a=rsa-sha1; q=dns; l=2538; t=1161361422; x=1162225422; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=yotsuda@cisco.com; z=From:=22Yoshi=20Tsuda=20\(yotsuda\)=22=20 |Subject:RE=3A=20[Mip4]=20WGLC=3A=20draft-ietf-mip4-gen-ext-00.txt; X=v=3Dcisco.com=3B=20h=3DBFiQYzVdPORuH75vxmEFmDATMJc=3D; b=kPslo8Bo+T45PEJnUUuWmlIQ4cWsvEhdq1Xb6nq1Dwx0khOI4E4zE/FaKbZyocXlmmAyhH81 LUzEeuaPH93hbf7EJrGYy++oj66UOGgtrO5K/8HPwyJDe1kxR24Jp6WJ; Authentication-Results: ams-dkim-2; header.From=yotsuda@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8 Cc: yoshi@cisco.com, Henrik Levkowetz X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi MIP WG, "I support the advancement of this document to the IESG with a request for publication as proposed standard." But, I have one comment: - There might be a security issue to include some DHCP options, such as Server Identifier(code=3D54) and Client = Identifier(code=3D61). - If others know there parameters, some malicious hosts can send a DHCP Release packet to the DHCP server by using MIP tunnel, for example, I'm afraid. - Thus, I would appreciate some security considerations to prevent this kind of issue. Sorry for my late comment. Thanks. -Yoshi > -----Original Message----- > From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com]=20 > Sent: Friday, October 20, 2006 6:13 AM > To: mip4@ietf.org > Cc: Henrik Levkowetz > Subject: [Mip4] WGLC: draft-ietf-mip4-gen-ext-00.txt >=20 > This message announces a WG last call on: >=20 > "MIPv4 Extension for Configuration Options Exchange" > draft-ietf-mip4-gen-ext-00.txt >=20 > The last call will conclude at 24:00 UTC on Friday, 3 November 2006. >=20 > "MIPv4 Extension for Configuration Options Exchange"=20 > describes new Mobile IPv4 extensions for carrying=20 > configuration information, where the information is formatted=20 > according to existing DHCP configuration options. >=20 > A URL for this internet draft is: >=20 > http://www.ietf.org/internet-drafts/draft-ietf-mip4-gen-ext-00.txt >=20 >=20 > Please respond to this WG last call: >=20 >=20 > * If you have no comments on the draft, and support its advancement, > simply respond with a line containing something like >=20 >=20 > "I support the advancement of this document to the IESG with a > request for publication as proposed standard." >=20 >=20 > If you have comments, please use a line similar to the one=20 > above, and > supplement this with your comments. >=20 >=20 >=20 > * If you *don't* support its advancement, respond with a line=20 > containing > something like the following, supplemented by your comments - >=20 >=20 > "I don't support the advancement of this document to the IESG with > a request for publication as proposed standard, for the following > reasons:" > ... >=20 >=20 >=20 >=20 > Pete & Henrik >=20 > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www1.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ >=20 -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Fri Oct 20 22:49:20 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gb6v1-0004YP-Tk; Fri, 20 Oct 2006 22:49:03 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gb6v0-0004YF-SP for mip4@ietf.org; Fri, 20 Oct 2006 22:49:02 -0400 Received: from nf-out-0910.google.com ([64.233.182.191]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gb6uy-0007GD-17 for mip4@ietf.org; Fri, 20 Oct 2006 22:49:02 -0400 Received: by nf-out-0910.google.com with SMTP id n15so1719587nfc for ; Fri, 20 Oct 2006 19:48:58 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=dYZjrhWW4Bz3DqvNJxZRcOvZfpHm+qRfaTP1axsLyr4+DcYwvta9oUcEKSB2ELvF4tz4XkxT3RDMvaYIoSQGf9QQfvf7b/fwbYSdi2DfVRVu72XCCte6FtcFQ9RtQxePbZbIy34lgwkvoD8QNc/LicbdV6fNlspZHkTcl68fyIc= Received: by 10.78.97.7 with SMTP id u7mr3172224hub; Fri, 20 Oct 2006 19:48:58 -0700 (PDT) Received: by 10.78.106.16 with HTTP; Fri, 20 Oct 2006 19:48:58 -0700 (PDT) Message-ID: Date: Fri, 20 Oct 2006 22:48:58 -0400 From: "Shaili Desai" To: mip4@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Subject: [Mip4] Seamless mobilty X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hello all I am new to this group, but wanted to know if anyone is looking into issue of seamless mobility when we switch from 802.3 network to 802.11. Does that work with Mobile IPv4?? I would highly appreciate if someone can help for the same, as I am doing my research project in Seamless mobility. Thanks in advance. -- Thanx Shaili Desai Master's Candidate Telecommunications and Management University of Maryland,College Park,USA -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Sat Oct 21 16:53:01 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GbNpa-0001Wp-PX; Sat, 21 Oct 2006 16:52:34 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GbNpZ-0001Vh-3N for mip4@ietf.org; Sat, 21 Oct 2006 16:52:33 -0400 Received: from email1.etri.re.kr ([129.254.16.131] helo=email1.etri.info) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GbHAX-0000m6-Gi for mip4@ietf.org; Sat, 21 Oct 2006 09:45:49 -0400 Received: from mail pickup service by email1.etri.info with Microsoft SMTPSVC; Sat, 21 Oct 2006 22:49:30 +0900 Priority: normal X-ReadCheckName: mip4%40ietf.org Thread-Topic: [Mip4] Seamless mobilty X-ReadCheckMessageID: <2a852d58-d940-4a54-8e4a-c87394e7d569@etri.re.kr> thread-index: Acb1F7uUoRy9bPFDT9qYTCnJF3rSbg== From: =?ks_c_5601-1987?B?wfbBpMjG?= To: "Shaili Desai" , Bcc: Subject: RE: [Mip4] Seamless mobilty Date: Sat, 21 Oct 2006 22:49:30 +0900 Comment: =?ks_c_5601-1987?B?x9GxucD8wNrF673Fv6yxuL/4LCDAzLW/xeu9xSDHpcHY?= =?ks_c_5601-1987?B?v6yxuMbALCC047Tn?= Message-ID: <0fe401c6f517$bb98bd00$8310fe81@etri.info> MIME-Version: 1.0 X-Mailer: Microsoft CDO for Exchange 2000 Content-Class: urn:content-classes:message Importance: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757 X-OriginalArrivalTime: 21 Oct 2006 13:49:30.0923 (UTC) FILETIME=[BBBA27B0:01C6F517] X-Spam-Score: 4.1 (++++) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Cc: X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?ks_c_5601-1987?B?wfbBpMjG?= List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2061754889==" Errors-To: mip4-bounces@ietf.org This is a multi-part message in MIME format. --===============2061754889== Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="----=_NextPart_000_0FDF_01C6F563.2B7E1B10" Content-Class: urn:content-classes:message This is a multi-part message in MIME format. ------=_NextPart_000_0FDF_01C6F563.2B7E1B10 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 ------=_NextPart_000_0FDF_01C6F563.2B7E1B10 Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 PERJViBpZD1tc2dib2R5IHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiCxvLiy Ij4NCjxESVY+SGVsbG8sIFNoYWlsaSBEZXNhaTwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxE SVY+VGhlIElFRUUgODAyLjIxIFdHIHdoaWNoIGRlYWxzIHdpdGggdGhlIE1JSCAoTWVkaWEmbmJz cDtJbmRlcGVuZGVudCBIYW5kb3Zlcik8L0RJVj4NCjxESVY+Zml0cyB5b3VyIGludGVyZXN0Ljwv RElWPg0KPERJVj5QbGVhc2UgcmVmZXIgdGhlIHNpdGUsIDxBIGhyZWY9Imh0dHA6Ly93d3cuaWVl ZTgwMi5vcmcvMjEiPmh0dHA6Ly93d3cuaWVlZTgwMi5vcmcvMjE8L0E+PC9ESVY+DQo8RElWPiZu YnNwOzwvRElWPg0KPERJVj5SZWdhcmRzLDwvRElWPg0KPERJVj4tSnVuZ2hvb248L0RJVj4NCjxE SVY+PEJSPi0tLS0tv/i6uyC43r3DwfYtLS0tLTxCUj48Qj66uLO9ILvntvc6PC9CPiAiU2hhaWxp IERlc2FpIiAmbHQ7c2hhaWxpZW50c0BnbWFpbC5jb20mZ3Q7PEJSPjxCPrq4s70gs6/CpTo8L0I+ IDIwMDYtMTAtMjEgv8DA/CAxMTo0ODo1ODxCUj48Qj653rTCILvntvc6PC9CPiAibWlwNEBpZXRm Lm9yZyIgJmx0O21pcDRAaWV0Zi5vcmcmZ3Q7PEJSPjxCPsL8wbY6PC9CPiA8QlI+PEI+waa48To8 L0I+IFtNaXA0XSBTZWFtbGVzcyBtb2JpbHR5PEJSPjxCUj48L0RJVj4NCjxESVY+PCEtLSBDb252 ZXJ0ZWQgZnJvbSB0ZXh0L3BsYWluIGZvcm1hdCAtLT48QlI+DQo8UD48Rk9OVCBzaXplPTI+SGVs bG8gYWxsPEJSPjxCUj5JIGFtIG5ldyB0byB0aGlzIGdyb3VwLCBidXQgd2FudGVkIHRvIGtub3cg aWYgYW55b25lIGlzIGxvb2tpbmcgaW50bzxCUj5pc3N1ZSBvZiBzZWFtbGVzcyBtb2JpbGl0eSB3 aGVuIHdlIHN3aXRjaCBmcm9tIDgwMi4zIG5ldHdvcmsgdG88QlI+ODAyLjExLjxCUj48QlI+RG9l cyB0aGF0IHdvcmsgd2l0aCBNb2JpbGUgSVB2ND8/PEJSPjxCUj5JIHdvdWxkIGhpZ2hseSBhcHBy ZWNpYXRlIGlmIHNvbWVvbmUgY2FuIGhlbHAgZm9yIHRoZSBzYW1lLCBhcyBJIGFtPEJSPmRvaW5n IG15IHJlc2VhcmNoIHByb2plY3QgaW4gU2VhbWxlc3MgbW9iaWxpdHkuPEJSPjxCUj5UaGFua3Mg aW4gYWR2YW5jZS48QlI+PEJSPi0tPEJSPlRoYW54PEJSPlNoYWlsaSBEZXNhaTxCUj5NYXN0ZXIn cyBDYW5kaWRhdGU8QlI+VGVsZWNvbW11bmljYXRpb25zIGFuZCBNYW5hZ2VtZW50PEJSPlVuaXZl cnNpdHkgb2YgTWFyeWxhbmQsQ29sbGVnZSBQYXJrLFVTQTxCUj48QlI+LS08QlI+TWlwNCBtYWls aW5nIGxpc3Q6IE1pcDRAaWV0Zi5vcmc8QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IFdlYiBpbnRlcmZh Y2U6IDxBIGhyZWY9Imh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21pcDQi IHRhcmdldD1fYmxhbms+aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbWlw NDwvQT48QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IENoYXJ0ZXIgcGFnZTogPEEgaHJlZj0i aHR0cDovL3d3dy5pZXRmLm9yZy9odG1sLmNoYXJ0ZXJzL21pcDQtY2hhcnRlci5odG1sIiB0YXJn ZXQ9X2JsYW5rPmh0dHA6Ly93d3cuaWV0Zi5vcmcvaHRtbC5jaGFydGVycy9taXA0LWNoYXJ0ZXIu aHRtbDwvQT48QlI+U3VwcGxlbWVudGFsIHNpdGU6IDxBIGhyZWY9Imh0dHA6Ly93d3cubWlwNC5v cmcvIiB0YXJnZXQ9X2JsYW5rPmh0dHA6Ly93d3cubWlwNC5vcmcvPC9BPjxCUj48L0ZPTlQ+PC9Q PjwvRElWPjwvRElWPjxpbWcgc3R5bGU9ImRpc3BsYXk6bm9uZSIgd2lkdGg9MCBoZWlnaHQ9MCBz cmM9Imh0dHA6Ly91bWFpbC5ldHJpLnJlLmtyL0V4dGVybmFsX1JlYWRDaGVjay5hc3B4P2VtYWls PW1pcDRAaWV0Zi5vcmcmbmFtZT1taXA0JTQwaWV0Zi5vcmcmZnJvbWVtYWlsPWpoamVlQGV0cmku cmUua3ImbWVzc2FnZWlkPSUzQzJhODUyZDU4LWQ5NDAtNGE1NC04ZTRhLWM4NzM5NGU3ZDU2OUBl dHJpLnJlLmtyJTNFIj4= ------=_NextPart_000_0FDF_01C6F563.2B7E1B10-- --===============2061754889== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ --===============2061754889==-- From mip4-bounces@ietf.org Sun Oct 22 10:42:23 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GbeWU-0002Fe-QX; Sun, 22 Oct 2006 10:41:58 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GbeWT-0002FZ-Eb for mip4@ietf.org; Sun, 22 Oct 2006 10:41:57 -0400 Received: from mail119.messagelabs.com ([216.82.241.179]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GbeWS-0002Xa-6z for mip4@ietf.org; Sun, 22 Oct 2006 10:41:57 -0400 X-VirusChecked: Checked X-Env-Sender: alexandru.petrescu@motorola.com X-Msg-Ref: server-3.tower-119.messagelabs.com!1161528115!11006483!1 X-StarScan-Version: 5.5.10.7; banners=-,-,- X-Originating-IP: [129.188.136.10] Received: (qmail 19521 invoked from network); 22 Oct 2006 14:41:55 -0000 Received: from motgate6.mot.com (HELO motgate.mot.com) (129.188.136.10) by server-3.tower-119.messagelabs.com with SMTP; 22 Oct 2006 14:41:55 -0000 Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231]) by motgate.mot.com (8.12.11/Motorola) with ESMTP id k9MEjrNY009689; Sun, 22 Oct 2006 07:45:55 -0700 (MST) Received: from [10.129.41.27] ([10.129.41.27]) by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id k9MEfoKb021145; Sun, 22 Oct 2006 09:41:51 -0500 (CDT) Message-ID: <453B832E.5070807@motorola.com> Date: Sun, 22 Oct 2006 16:41:50 +0200 From: Alexandru Petrescu User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Shaili Desai Subject: Re: [Mip4] Seamless mobilty References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Cc: mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Shaili Desai wrote: > Hello all > > I am new to this group, but wanted to know if anyone is looking into > issue of seamless mobility when we switch from 802.3 network to > 802.11. Which issue more exactly? Two interfaces active simultaneously (such as no packet loss)? Bicasting the packets? Implementation of Fast Mobile IPv4? > Does that work with Mobile IPv4?? YEs, Mobile IPv4 implementation accomodates ok switching from one interface to another, be it Ethernet to WiFi. > I would highly appreciate if someone can help for the same, as I am > doing my research project in Seamless mobility. Yes, but what aspects of 'seamless mobility' do you look at. Any prototyping planned? Alex -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Mon Oct 23 03:06:24 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gbtt2-0001FF-Nq; Mon, 23 Oct 2006 03:06:16 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GbtsK-0008OP-6V; Mon, 23 Oct 2006 03:05:32 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GbtdK-0005wU-Vo; Mon, 23 Oct 2006 02:50:03 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id E88C826E5C; Mon, 23 Oct 2006 06:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GbtdK-0006SM-P4; Mon, 23 Oct 2006 02:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 23 Oct 2006 02:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 386e0819b1192672467565a524848168 Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-fmipv4-02.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Mobility for IPv4 Working Group of the IETF. Title : Mobile IPv4 Fast Handovers Author(s) : R. Koodli, C. Perkins Filename : draft-ietf-mip4-fmipv4-02.txt Pages : 19 Date : 2006-10-22 The Mobile IPv6 fast handover document [2] specifies a protocol to improve latency and packet loss resulting from Mobile IPv6 handover operations. This document adapts the protocol for IPv4 networks to improve performance over Mobile IPv4 operations, including processing of Agent Advertisements, new Care of Address acquisition and Registration Request and Reply. Using the concepts outlined in [2], this document also addresses movement detection, IP address configuration and location update latencies during a handover. For reducing the IP address configuration, the document currently proposes that the new CoA is always made to be the new access router's IP address. Additional mechanisms may be defined in the future versions of this document. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-fmipv4-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mip4-fmipv4-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mip4-fmipv4-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-10-22183234.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-fmipv4-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-fmipv4-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-10-22183234.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ --NextPart-- From mip4-bounces@ietf.org Mon Oct 23 09:10:34 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GbzZT-0001rd-Tu; Mon, 23 Oct 2006 09:10:27 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GbzZT-0001rY-7B for Mip4@ietf.org; Mon, 23 Oct 2006 09:10:27 -0400 Received: from [211.94.36.20] (helo=mail.chinaunicom.com.cn) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GbzZ9-0003eN-Ex for Mip4@ietf.org; Mon, 23 Oct 2006 09:10:27 -0400 thread-index: Acb2pFt7bKAfUBGNS3SM+E99xSdmLQ== Received: from arbi ([211.94.36.208]) by mail.chinaunicom.com.cn with Microsoft SMTPSVC(5.0.2195.6713); Mon, 23 Oct 2006 21:08:39 +0800 Message-ID: <007b01c6f6a4$805dfaf0$7216c00a@arbi> From: "Binfeng Yan" To: Subject: Re: [Mip4] draft-deng-mip4-generic-notification-message-02.txt Date: Mon, 23 Oct 2006 21:09:41 +0800 X-Priority: 3 X-MSMail-Priority: Normal Content-Class: urn:content-classes:message Importance: normal Priority: normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 X-RFC2646: Format=Flowed; Original X-OriginalArrivalTime: 23 Oct 2006 13:08:39.0655 (UTC) FILETIME=[5B7BD770:01C6F6A4] X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Cc: X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org This protocol has various application scenario such as in cdma packet-switched network. So I am in favor of adopting this as a working group item. -Binfeng Yan > ----- Original Message ---- > From: McCann Peter-A001034 > To: mip4@ietf.org > Sent: Tuesday, October 17, 2006 10:43:58 AM > Subject: [Mip4] draft-deng-mip4-generic-notification-message-02.txt > > > During the last working group meeting, we had a discussion on > draft-deng-mip4-generic-notification-message-02.txt. > There were 3 or 4 people who spoke out in favor of adding this to the > charter. > > I'd like to poll the list on this. Who is in favor of adopting this > as a working group item? Opposed? > > If we get consensus to add this we can do it at the same time as we do > the NEMOv4 addition. > > -Pete > > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www1.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > ±¾Óʼþ¼°Æ丽¼þº¬ÓÐÖйúÁªÍ¨µÄ±£ÃÜÐÅÏ¢£¬½öÏÞÓÚ·¢Ë͸øÉÏÃæµØÖ·ÖÐÁгöµÄ¸öÈË»òȺ ×é¡£Çë½ÓÊÕÕß×¢Òâ±£ÃÜ£¬Î´¾­·¢¼þÈËÊéÃæÐí¿É£¬²»µÃÏòÈκεÚÈý·½×éÖ¯ºÍ¸öÈË͸¶±¾ ÓʼþËùº¬ÐÅÏ¢µÄÈ«²¿»ò²¿·Ö¡£Èç¹ûÄú´íÊÕÁ˱¾Óʼþ£¬ÇëÄúÁ¢¼´Í¨Öª·¢¼þÈ˲¢É¾³ý±¾ÓÊ ¼þ£¡Ð»Ð»¡£ This e-mail and its attachments contain confidential information from China Unicom, which is intended only for the person or entity whose address is listed above. Recipients named above are obligated to maintain secrecy£¬and they are not permitted to disclose the total or partial contents of this e-mail to others besides the sender¡¯s written permission. If you receive this e-mail in error, please inform the sender immediately and delete it. Thank you. -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Wed Oct 25 14:13:42 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcnG2-00007K-28; Wed, 25 Oct 2006 14:13:42 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcnF5-00083L-0i for mip4@ietf.org; Wed, 25 Oct 2006 14:12:43 -0400 Received: from mail119.messagelabs.com ([216.82.241.179]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GcnF3-0006ZW-PJ for mip4@ietf.org; Wed, 25 Oct 2006 14:12:42 -0400 X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-14.tower-119.messagelabs.com!1161799960!12033669!1 X-StarScan-Version: 5.5.10.7; banners=-,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 5719 invoked from network); 25 Oct 2006 18:12:40 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-14.tower-119.messagelabs.com with SMTP; 25 Oct 2006 18:12:40 -0000 Received: from il06exb01.corp.mot.com (il06exr04.mot.com [129.188.137.134]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id k9PICdHv024897 for ; Wed, 25 Oct 2006 11:12:39 -0700 (MST) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by il06exb01.corp.mot.com (8.13.1/8.13.0) with ESMTP id k9PICcFi017831 for ; Wed, 25 Oct 2006 13:12:39 -0500 (CDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Wed, 25 Oct 2006 14:12:37 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Agenda for MIP4 Thread-Index: Acb4YSass0pJPt5bRFi20bRZzfpEXg== From: "McCann Peter-A001034" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 X-Mailman-Approved-At: Wed, 25 Oct 2006 14:13:40 -0400 Subject: [Mip4] Agenda for MIP4 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Below is a first draft agenda for our mip4 meeting in San Diego. Please send any additional requests for presentation slots to pete.mccann@motorola.com and henrik@levkowetz.com as soon as possible. -Pete Mobility for IPv4 WG =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D WEDNESDAY, November 8, 2006 1510-1610 Afternoon Session II Harbor Island I =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D CHAIRS: Henrik Levkowetz Pete McCann AGENDA: 1. Preliminaries 10 min Chairs - Blue sheets - Note takers - Jabber scribe - Agenda bashing 2. Document Status 15 min Chairs 3. New charter proposals 15 min, Chairs 3.1 MIPv4 based Moving Network (NEMO) support 5 min, Chairs draft-tsirtsis-nemov4-dynamic draft-tsirtsis-nemov4-fa draft-ietf-nemo-v4-base It been proposed to standardise some moving network support, and a proposed charter addition has received favourable support on the mipv4 list. 3.2. Generic notification mechanism 5 min, Chairs draft-deng-mip4-generic-notification-message-02.txt It has been proposed to also add this as a work item to the charter, and the list response has bee favourable 4. FMIPv4 updates 5 min, Rajeev Koodli draft-ietf-mip4-fmipv4 5. The MIPv4 nemo base document 5 min, Alex P. draft-ietf-nemo-v4-base This document was earlier handled by the NEMO working group. If the new charter containing work on MIPv4 moving networks, it is expected that this will be the base document taken forward by the MIP4 working group. = =3D=3D=3D=3D=3D=3D=3D=3D=3D Total time 60 min -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Wed Oct 25 14:49:00 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcnoC-0006um-DS; Wed, 25 Oct 2006 14:49:00 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcnoB-0006uh-Te for mip4@ietf.org; Wed, 25 Oct 2006 14:48:59 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcnoA-0005QZ-88 for mip4@ietf.org; Wed, 25 Oct 2006 14:48:59 -0400 Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k9PImuKT026124 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 25 Oct 2006 11:48:56 -0700 Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109]) by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k9PImrwT018157; Wed, 25 Oct 2006 11:48:55 -0700 (PDT) Received: from SANEXCAS02.na.qualcomm.com ([172.30.36.176]) by NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Oct 2006 11:48:53 -0700 Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Oct 2006 11:48:52 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Mip4] Proposed charter update for NEMOv4 work Date: Wed, 25 Oct 2006 11:48:56 -0700 Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A2AC26A@NAEX14.na.qualcomm.com> In-Reply-To: <4538F042.20804@motorola.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Proposed charter update for NEMOv4 work Thread-Index: Acb0X7hYioZjozFQRzy/wnUY01iESgEBd5iQ From: "Tsirtsis, George" To: "Alexandru Petrescu" , "Henrik Levkowetz" X-OriginalArrivalTime: 25 Oct 2006 18:48:52.0721 (UTC) FILETIME=[37720610:01C6F866] X-Spam-Score: 0.0 (/) X-Scan-Signature: a3f7094ccc62748c06b21fcf44c073ee Cc: mip4-chairs@tools.ietf.org, Mobile IPv4 Mailing List X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org I would also like to give a short presentation on the two extension drafts for NEMOv4: http://www.ietf.org/internet-drafts/draft-tsirtsis-nemov4-dynamic-00.txt http://www.ietf.org/internet-drafts/draft-tsirtsis-nemov4-fa-00.txt The idea was that these drafts would become WG drafts too. May I assume the charter change covers these? Thanks George > -----Original Message----- > From: Alexandru Petrescu [mailto:alexandru.petrescu@motorola.com] > Sent: Friday, October 20, 2006 11:50 AM > To: Henrik Levkowetz > Cc: mip4-chairs@tools.ietf.org; Mobile IPv4 Mailing List > Subject: Re: [Mip4] Proposed charter update for NEMOv4 work >=20 > I too support adoption of WG items related to IPv4 network mobility. > I'm co-authoring the NEMOv4 draft. >=20 > I've parallely requested a short presentation slot in San Diego meeting. >=20 > The draft is at > ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-nemo-v4-bas e- > 01.txt > It's actually a third revision, since it existed as a personal proposal > in NEMO WG, prior to being a WG item there. >=20 > The authorship didn't change much since first incarnation, however, the > Ack section was updated to reflect several improvements on the draft. >=20 > Looking forward, >=20 > Alex >=20 > Henrik Levkowetz wrote: > > Hi, > > > > We're working on a charter update for MIPv4. One of the things we'd > > like to add is a work item covering the NEMOv4 specification. > > > > We'd like to add the following item to the charter: > > > > 11. NEMO v4 Support > > > > The Network Mobility (nemo) working group deals with the problem of > > mobility of a whole network, such as might exist inside a vehicle, > > train, or airplane. The nemo working group has developed draft > > specifications for both IPv6 and IPv4 mobile networks. However, it > > has been recognized that the IPv4 version of the protocol can be > > viewed as an extension of the basic Mobile IPv4 protocol, and there > > is good reason to do this extension in the mip4 working group. The > > working group will take on the NEMO v4 internet draft and progress it > > along the standards track. > > > > If you have comments on this, please send them to the list. > > > > > > Regerds, > > > > Henrik and Pete > > > > > > > > (The resulting full charter text is here: > > > > > > Description of Working Group: > > > > IP mobility support for IPv4 nodes (hosts and routers) is specified > > in RFC3344. RFC 3344 mobility allows a node to continue using its > > "permanent" home address as it moves around the Internet. The Mobile > > IP protocols support transparency above the IP layer, including > > maintenance of active TCP connections and UDP port bindings.Besides > > the basic Mobile IPv4 (MIPv4) protocols, several other drafts deal > > with concerns such as optimization, security, extensions, AAA > > support, and deployment issues. > > > > MIPv4 is currently being deployed on a wide basis (e.g., in cdma2000 > > networks). The scope of the deployment is on a fairly large scale > > and accordingly, the MIP4 WG will focus on deployment issues and on > > addressing known deficiencies and shortcomings in the protocol that > > have come up as a result of deployment experience. Specifically, the > > working group will complete the work items to facilitate > > interactions with AAA environments, interactions with enterprise > > environments when MIPv4 is used therein, and updating existing > > protocol specifications in accordance with deployment needs and > > advancing those protocols that are on the standards track. > > > > Work expected to be done by the MIP4 WG as proposed by this charter > > is as follows: > > > > 1. MIPv4 has been a proposed standard for several years. It has been > > adopted by other standard development organizations and has been > > deployed commercially. One of the next steps for the WG is to advance > > the protocol to draft standard status. As part of advancing base > > Mobile IP specs to DS, the MIPv4 NAI RFC (2794) will be revised to > > reflect implementation experience > > > > 2. Work items that are pending from the previous Mobile IP WG, which > > will be completed by the MIP4 WG, are: > > > > - completion of the MIB for the revised base Mobile IP specification > > (2006bis) > > > > - regional registration draft. > > > > 3. The MIP4 WG will also complete the work on MIPv4 interactions in > > VPN scenarios. This work will involve identifying the requirements > > and a solution development for MIPv4 operation in the presence of > > IPsec VPNs. > > > > 4. Additionally, a proposal has been made for how MOBIKE could work > > together with MIPv4. This proposal does not describe any new > > protocol, but formulates a best current practice for deploying MOBIKE > > together with MIPv4. The working group will adopt and complete this > > document. > > > > 5. Some issues have been raised with respect to RFC3519. These will > > be identified and addressed as appropriate, through errata, revision > > of RFC 3519, and/or supplemental documents as needed. > > > > 6. It has been proposed that the FMIP protocol, which has been > > standardised for MIPv6 in the MIPSHOP working group, should also be > > published as an experimental protocol for MIPv4. A draft for this > > exists. The working group will take up and carry this work forward to > > publication > > > > 7. An extension to carry generic strings in the Registration Reply > > message has been proposed. The purpose is to supply supplemental > > human-readable information intended to the MN user. The working group > > will complete the specification and applicability statement of such > > an extension. > > > > 8. RADIUS attributes for MIP4. A set of RADIUS attributes has been > > proposed for MIPv4. > > > > The working group will first produce a requirements specification, > > describing how the work differs from the requirements in RFC 2977 and > > the functionality provided by RFC 4004 (the MIPv4 Diameter App). The > > reason why this first step is required is that RFC 3127 shows that > > full RFC 2977 functionality can't be provided by even a considerably > > extended RADIUS, so we need to match the requirements to what can be > > done within RADIUS. > > > > Provided the requirements work finds approval with ADs and RADEXT WG, > > the workgroup will complete the specification of MIPv4 RADIUS > > attributes, solicit feedback from the RADEXT WG, adjust, and submit > > this for publication. Note that the work may require extensions to > > the RADIUS attribute space which will be handled outside the MIP4 WG. > > > > > > > > 9. MIPv4 Extension for Configuration Options. > > > > Several drafts have proposed extensions to help improve configuration > > of MIPv4 clients. The latest proposal is for a general configuration > > option extension which could carry information such as e.g., DNS > > address and DHCP server address. The working group will take on and > > complete one proposal for a configuration option extension. > > > > 10. Dual-stack Support > > > > There have been several proposals for how to enable an IPv6 > > connection over a network that supports Mobile IPv4. A protocol > > enhancement to MIPv4 would allow for IPv6 support in a region where > > Mobile IPv4 has already been implemented and deployed. This would > > allow a dual stack mobile node to maintain IPv6 connectivity when > > using MIPv4. The solution would therefore be applicable only to > > networks that are not deploying Mobile IPv6. > > > > The working group will take on and complete one proposal for IPv6 > > over Mobile IPv4. This work is restricted to a small protocol > > extension similar to current Mobile IPv4 functionality. Support for > > advanced Mobile IPv6 functionality is strictly outside the scope. > > > > A problem statement covering both Mobile IPv4 and IPv6 dual-stack > > issues is expected to come out of MIP6 WG, and will not be developed > > in MIP4 WG. > > > > 11. NEMO v4 Support > > > > The Network Mobility (nemo) working group deals with the problem of > > mobility of a whole network, such as might exist inside a vehicle, > > train, or airplane. The nemo working group has developed draft > > specifications for both IPv6 and IPv4 mobile networks. However, it > > has been recognized that the IPv4 version of the protocol can be > > viewed as an extension of the basic Mobile IPv4 protocol, and there > > is good reason to do this extension in the mip4 working group. The > > working group will take on the NEMO v4 internet draft and progress it > > along the standards track. > > > > ) > > > > >=20 >=20 > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www1.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Wed Oct 25 17:44:23 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcqXt-0006uT-T1; Wed, 25 Oct 2006 17:44:21 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcqXs-0006uN-AS for mip4@ietf.org; Wed, 25 Oct 2006 17:44:20 -0400 Received: from av7-2-sn3.vrr.skanova.net ([81.228.9.182]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcqXq-0005Ny-TY for mip4@ietf.org; Wed, 25 Oct 2006 17:44:20 -0400 Received: by av7-2-sn3.vrr.skanova.net (Postfix, from userid 502) id 56E7C38212; Wed, 25 Oct 2006 23:44:05 +0200 (CEST) Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net [81.228.9.101]) by av7-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 45BE137E92; Wed, 25 Oct 2006 23:44:05 +0200 (CEST) Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com [81.232.110.214]) by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id B1AE637E7C; Wed, 25 Oct 2006 23:44:17 +0200 (CEST) Received: from localhost ([127.0.0.1]) by shiraz with esmtp (Exim 4.63) (envelope-from ) id 1GcqXk-0007Ao-47; Wed, 25 Oct 2006 23:44:12 +0200 Message-ID: <453FDAA9.20005@levkowetz.com> Date: Wed, 25 Oct 2006 23:44:09 +0200 From: Henrik Levkowetz User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909) MIME-Version: 1.0 To: Mobile IPv4 Mailing List X-Enigmail-Version: 0.94.0.0 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on shiraz); SAEximRunCond expanded to false X-Spam-Score: 0.1 (/) X-Scan-Signature: 386e0819b1192672467565a524848168 Cc: mip4-chairs@tools.ietf.org Subject: [Mip4] Update, agenda v.03: X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0458339574==" Errors-To: mip4-bounces@ietf.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============0458339574== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE67E974A2E17D06EA0847E6F" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE67E974A2E17D06EA0847E6F Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, Here's an updated agenda: Mobility for IPv4 WG =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D WEDNESDAY, November 8, 2006 1510-1610 Afternoon Session II Harbor Island I =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D CHAIRS: Henrik Levkowetz Pete McCann AGENDA: 1. Preliminaries 10 min, Chairs - Blue sheets - Note takers - Jabber scribe - Agenda bashing 2. Document Status 15 min, Chairs 3. New charter proposals 3.1 MIPv4 based Moving Network (NEMO) support 5 min, Chairs It been proposed to standardise some moving network support, and a proposed charter addition has received favourable support on the mipv4 list. 3.2. Generic notification mechanism 5 min, Chairs draft-deng-mip4-generic-notification-message-02.txt It has been proposed to also add this as a work item to the charter, and the list response has bee favourable 4. FMIPv4 updates 5 min, Rajeev draft-ietf-mip4-fmipv4 5. The MIPv4 nemo base document 5 min, Alex P. draft-ietf-nemo-v4-base This document was earlier handled by the NEMO working group. If the new charter containing work on MIPv4 moving networks, it is expected that this will be the base document taken forward by the MIP4 working group. 6. MIPv4 nemo extension documents 10 min, George draft-tsirtsis-nemov4-dynamic draft-tsirtsis-nemov4-fa These two documents propose extensions to MIPv4 nemo to do dynamic prefix allocatin, and add FA support. =3D=3D=3D=3D=3D=3D= =3D=3D=3D Total time 55 min --------------enigE67E974A2E17D06EA0847E6F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iD8DBQFFP9qpeVhrtTJkXCMRAqgSAJ49xoTzKqLPlW76IZeTY+7X5gstcwCgmRWf OmJXmjZb8A0XYZCHOLCJ7E8= =T7OC -----END PGP SIGNATURE----- --------------enigE67E974A2E17D06EA0847E6F-- --===============0458339574== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ --===============0458339574==-- From mip4-bounces@ietf.org Wed Oct 25 17:47:41 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcqb7-0008S2-0u; Wed, 25 Oct 2006 17:47:41 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcpEP-0006RI-FT for mip4@ietf.org; Wed, 25 Oct 2006 16:20:09 -0400 Received: from av11-1-sn2.hy.skanova.net ([81.228.8.183]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcpE6-0005vk-8k for mip4@ietf.org; Wed, 25 Oct 2006 16:20:09 -0400 Received: by av11-1-sn2.hy.skanova.net (Postfix, from userid 502) id 69C92381A1; Wed, 25 Oct 2006 22:19:49 +0200 (CEST) Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net [81.228.8.92]) by av11-1-sn2.hy.skanova.net (Postfix) with ESMTP id 58643380D3; Wed, 25 Oct 2006 22:19:49 +0200 (CEST) Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com [81.232.110.214]) by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id E415D37E61; Wed, 25 Oct 2006 22:19:48 +0200 (CEST) Received: from localhost ([127.0.0.1]) by shiraz with esmtp (Exim 4.63) (envelope-from ) id 1GcpDw-0006wY-Dv; Wed, 25 Oct 2006 22:19:40 +0200 Message-ID: <453FC6DA.10907@levkowetz.com> Date: Wed, 25 Oct 2006 22:19:38 +0200 From: Henrik Levkowetz User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909) MIME-Version: 1.0 To: "Tsirtsis, George" Subject: Re: [Mip4] Proposed charter update for NEMOv4 work References: <7EB20EA0938B4D42A2D82689365C9B7A2AC26A@NAEX14.na.qualcomm.com> In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A2AC26A@NAEX14.na.qualcomm.com> X-Enigmail-Version: 0.94.0.0 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on shiraz); SAEximRunCond expanded to false X-Spam-Score: 0.1 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Cc: mip4-chairs@tools.ietf.org, Mobile IPv4 Mailing List , Alexandru Petrescu X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0607593872==" Errors-To: mip4-bounces@ietf.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============0607593872== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigCDC11EF16295CE8B5969261B" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigCDC11EF16295CE8B5969261B Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi George, on 2006-10-25 20:48 Tsirtsis, George said the following: > I would also like to give a short presentation on the two extension > drafts for NEMOv4: > http://www.ietf.org/internet-drafts/draft-tsirtsis-nemov4-dynamic-00.tx= t > http://www.ietf.org/internet-drafts/draft-tsirtsis-nemov4-fa-00.txt >=20 > The idea was that these drafts would become WG drafts too. May I assume= > the charter change covers these? The charter change introduces NEMO/MIPv4 as a MIP4 work item, but doesn't specifically mention documents. Assuming that the charter revision is accepted, the working group will have to adopt individual draft as working group drafts. I don't expect adding an item to present these two to the agenda should be a problem. Regards, Henrik --------------enigCDC11EF16295CE8B5969261B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iD8DBQFFP8baeVhrtTJkXCMRAmhtAJwOYk0aWpdbH+mJ3XgtIOe4CYkLGQCfZ1VS AokVJ+HZiZBXFVx8/OrSgnQ= =MoNm -----END PGP SIGNATURE----- --------------enigCDC11EF16295CE8B5969261B-- --===============0607593872== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ --===============0607593872==-- From mip4-bounces@ietf.org Wed Oct 25 22:07:05 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcudu-0003br-Lj; Wed, 25 Oct 2006 22:06:50 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcudu-0003bi-5p for mip4@ietf.org; Wed, 25 Oct 2006 22:06:50 -0400 Received: from dsl092-223-006.sfo1.dsl.speakeasy.net ([66.92.223.6] helo=moe.corp.azairenet.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gcudt-0003V1-KG for mip4@ietf.org; Wed, 25 Oct 2006 22:06:50 -0400 Received: from [10.1.201.12] ([66.92.223.6]) by moe.corp.azairenet.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Oct 2006 19:06:48 -0700 Message-ID: <45401838.5070409@azairenet.com> Date: Wed, 25 Oct 2006 19:06:48 -0700 From: Vijay Devarapalli User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: mip4@ietf.org Subject: Re: [Mip4] WGLC: draft-ietf-mip4-gen-ext-00.txt References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 26 Oct 2006 02:06:48.0593 (UTC) FILETIME=[6515E810:01C6F8A3] X-Spam-Score: 0.1 (/) X-Scan-Signature: bf422c85703d3d847fb014987125ac48 Cc: McCann Peter-A001034 , Henrik Levkowetz X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org this document needs some work before it can be sent to the IESG. at a high level we need to say that this document defines a new configuration options exchange extension, but we just use the extension to carry the DHCP and BOOTP options as defined in RFC 2132. the security considerations section needs some serious consideration. :) some specific comments. > This document describes the mechanism for providing the host > configuration information during Mobile IP registration. perhaps mention here that this is primarily for home link information. for configuration information on the visited link, you are better off using DHCP on the visited link. > One or more > Configuration Options Exchange Extensions may be included in the > registration message to provide the Mobile Node the configuration > parameters needed for network service usage (e.g. DNS). what is "network service usage"? network access? > 1. Introduction > > Mobile IPv4 lacks the capability to dynamically configure the > interface parameters (e.g. home subnet mask) and network service > elements (e.g. DNS servers) on the Mobile Node. These information s/these/this > There are possible > ways to deliver foreign network's configuration information to the > Mobile Node, but there is no method for the home network (where the > Mobile Node is logically anchored) to provide these parameters. suggest re-wording to There are mechanisms such as DHCP for the mobile node to configure information from the foreign network, but not from the home network when the mobile node is not attached to the home network. > To configure the Mobile Node with the configuration parameters at the > time of MIPv4 registration an extension should be defined to carry > such information. This document defines this MIPv4 extension. suggest re-wording to This document defines a new extension that can be used to carry configuration parameters during Mobile IPv4 registration. > 2. Configuration Options Exchange Extension > > The Mobile IPv4 extension has the format shown in this section to > carry configuration information. This extension MAY be included as a > part of Mobile IP Registration Request or Registration Reply. > > 0 1 2 3 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Type | Length | Entity-Type | Sub-Type | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Config-Data > +-+-+-+-+-+-... > > > Figure 1: Configuration Options Exchange Extension > > Type > > IPV4-CONF-OPTIONS-EXT-TYPE (This extension value will be > assigned by IANA from the numbering space defined in [RFC3344] > for skippable extensions) IPV4-CONF-OPTIONS-EXT-TYPE is wierd. aren't the Mobile IPv4 extensions known by a name? see RFC 3344. instead say Type Configuration Options Exchange Extension the text in the parenthesis can be removed because it appears in the IANA Considerations section later. > This field indicates which Mobility Agent was asked or inserted > the extension in the Registration Request or Registration > Reply, respectively. suggest re-wording to This field indicates which mobility agent the request was sent to when the extension is present in a Registration Request and which mobility agent inserted the extension in a Registration Reply. or something like that... > 3. Processing of Configuration Options Exchange Extension > > The Mobile Node may request values for specific configuration > parameters from the Home Agent and/or Foreign Agent by including the > 'Parameter Request List' option in the Registration Request. The this is the first time the Parameter Request List option is being mentioned in this document. I guess we need to say that this option is defined in RFC 2132. > list of requested parameters is specified as a string of octets, > where each octet is a valid DHCP option code as defined in [RFC2132]. > If this extension is included in the Registration Request, the Home > Agent or Foreign Agent (indicated in the Entity-Type field) should > provide requested information in the Registration Reply. The > Configuration Options Exchange extension should be repeated in the > Registration Request for parameter(s) request based on the Entity- > Type. If there are no Configuration Options Exchange Extension in > the Registration Request, it's up to the Home Agent or Foreign Agent > to decide which configuration parameter to include in the > Configuration Options Exchange extension. The configuration > parameter(s) should not be overwritten by the Foreign Agent if the > Home Agent has included them in the Configuration Options Exchange > extension. The Entity-Type field is set to the Mobility Agent that > appended the extension in the Registration Reply. > > When a network entity (identified in the Entity-Type field of the > extension) network entity includes the mobile node also in this case. wonder if "network entity" is the right term. < adds a Configuration Options Exchange Extension to a > Registration Request or Registration Reply message, this extension > MUST appear prior to any authentication extensions added by that > entity. > > Example: > > Mobile Node wants to obtain the home network prefix mask and DNS > servers' IP addresses from its Home Agent during registration. The > Registration Request would contain the following values in the > Configuration Options Exchange Extension. > > 0 1 2 3 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | | =6 | =1 | =0 | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ what is "Rsv"? > | =55 | =2 | =1 | =6 | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ what is "OpCode=55"? > 4. IANA Considerations > > This draft defines new Mobile IPv4 extension of types IPV4-CONF- > OPTIONS-EXT-TYPE as defined in Section 2 of this document. suggest re-wording to This draft defines new Mobile IPv4 extension, the Configuration Options Exchange Extension as defined in Section 2. > 5. Security Considerations > > There are no additional security aspects imposed by this document in > addition to the one defined in [RFC3344]. is that true? typically information that is being exchanged here is sent one-hop from the access network to the mobile node. or at least it is contained in the access network. now we are sending this information across the Internet unencrypted. for e.g. we are sending the IP address of the DNS server to a remote mobile node without encrypting the information. so its not possible that there are no new security considerations. Vijay -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Thu Oct 26 15:48:28 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdBDI-00087Q-KX; Thu, 26 Oct 2006 15:48:28 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdB7Z-000558-FP for mip4@ietf.org; Thu, 26 Oct 2006 15:42:33 -0400 Received: from msg-mx0.usc.edu ([128.125.137.5]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdAxX-00062P-Ff for mip4@ietf.org; Thu, 26 Oct 2006 15:32:13 -0400 Received: from halcyon.usc.edu ([128.125.72.33]) by msg-mx0.usc.edu (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTP id <0J7R00FQMCXM3590@msg-mx0.usc.edu> for mip4@ietf.org; Thu, 26 Oct 2006 12:32:10 -0700 (PDT) Received: from localhost (amol@localhost) by halcyon.usc.edu (8.10.1/8.10.1/usc) with ESMTP id k9QJW9806806; Thu, 26 Oct 2006 12:32:09 -0700 (PDT) Date: Thu, 26 Oct 2006 12:32:09 -0700 (PDT) From: Amol Bakshi To: mip4@ietf.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT X-Authentication-warning: halcyon.usc.edu: amol owned process doing -bs X-Spam-Score: 0.6 (/) X-Scan-Signature: b84f8c8fba0e1389e5eb998b64078964 X-Mailman-Approved-At: Thu, 26 Oct 2006 15:48:27 -0400 Cc: amol@usc.edu Subject: [Mip4] DCOSS 2007 CFP; Submission deadline Feb 5, 2007 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org ========================================= IEEE International Conference on Distributed Computing in Sensor Systems June 18 - 20, 2007 Santa Fe, New Mexico, USA ========================================= WWW.DCOSS.ORG The 2007 International Conference on Distributed Computing in Sensor Systems (DCOSS '07) will take place in Santa Fe during June 18 - 20, 2007. The first and second DCOSS conferences, held at Marina Del Rey and San Francisco respectively, featured high quality research papers and interesting invited and contributed poster/presentation sessions. DCOSS '07 is intended to cover several aspects of distributed computing in sensor systems such as high level abstractions, computational models, systematic design methodologies, algorithms, analysis and applications. The conference will be co-located with several closely related workshops, and will provide a forum for researchers and practitioners to present their contributions related to the above high-level aspects of distributed sensor systems. In addition to contributed papers, the meeting will also include keynote addresses by leading researchers, a panel discussion, and a poster/presentation session. SPONSORED BY IEEE Computer Society Technical Committee on Parallel Processing (TCPP) IEEE Computer Society Technical Committee on Distributed Processing (TCDP) Held in co-operation with ACM SIGARCH ACM SIGBED European Association for Theoretical Computer Science (EATCS) IFIP WG 10.3 MEETING INFORMATION The advance program will be available in April 2007. Check http://www.dcoss.org/ for updated information. IMPORTANT DATES Monday February 5, 2007 Paper Submission Due Monday April 2, 2007 Notification of Acceptance/Rejection Monday April 16, 2007 Camera-Ready Paper Due ------------------------------------------------------------------------ ============================== CALL FOR PARTICIPATION ============================== CALL FOR PAPERS Distributed sensor systems have become a highly active research area due to their potential for providing diverse new capabilities. Such systems allow intelligent dense monitoring of physical environments, which makes them immensely useful for data collection and analysis. While much ongoing research has addressed networking, communication and low-level self-configuration issues in such systems, there are also significant challenges pertaining to systematic design, algorithm development and analysis, and abstract modeling in order to achieve efficient and robust realizations of large-scale distributed sensor systems. The large number of sensor devices involved, severe power, computational and memory limitations, resource heterogeneity, dense deployment and frequent failures pose novel challenges to design, algorithms, analysis and implementation. The focus of the conference is on distributed computing issues in large-scale networked sensor systems (including algorithms, applications, and systematic design techniques and tools), but networking-related contributions that support high level abstractions are also welcome. Authors are invited to submit original unpublished manuscripts that demonstrate current research on computational aspects of distributed sensor systems. Topics of interest include but are not limited to: - Computation and programming models - Energy models, minimization, awareness - Distributed algorithms for collaborative information processing - Theoretical performance analysis: complexity, correctness, scalability, fault-tolerance - Abstractions for modular design - Languages, operating systems - Task allocation, reprogramming and reconfiguration - Dynamic resource management - Scalable, heterogeneous architectures (node and system-level) - Middleware interfaces, communication and processing primitives - Design, simulation and optimization tools for deployment and operation - Design automation and application synthesis techniques - Case studies: lessons from real world deployments PAPER SUBMISSION Submitted manuscripts may not exceed 12 single-spaced pages using 12-point size font on 8.5x11 inch pages, including figures and tables. References may be included in addition to the 12 pages. Submissions will be judged on correctness, originality, technical strength, significance, quality of presentation, and interest and relevance to the conference attendees. Submitted papers may not have appeared in or be under consideration for another conference or a journal. Submission procedures will be available via Web access at http://www.dcoss.org/ All manuscripts will be reviewed. Manuscripts must be received by February 5, 2007, by 5 p.m. U.S. Pacific Coast Time. Notification of review decisions will be mailed by April 2, 2007. Camera-ready papers will be due April 16, 2007. DCOSS '07 Proceedings will be distributed at the Conference. PROGRAM CHAIR James Aspnes Yale University USA PROGRAM VICE CHAIRS Algorithms: Christian Scheideler, TU Munich, Germany Applications: Anish Arora, Ohio State Univ., USA Systems: Samuel Madden, MIT, USA POSTER/PRESENTATION SESSION The conference will include a poster session for researchers and practitioners to present novel on-going work-in-progress and to obtain feedback from conference attendees in an informal setting. Authors of accepted posters will have an opportunity to briefly present their work in this session. Select invited presentations and posters from industry and academia may also be included in this session. Submission details and deadlines will be available at the DCOSS website. POSTER CHAIR Wendi Heinzelman Univ. of Rochester USA BEST PAPER AWARDS Awards will be given for one best paper in each of the three conference technical tracks: algorithms, applications, and systems. ================================= DCOSS '07 ORGANIZATION ================================= GENERAL CO-CHAIRS Sotiris Nikoletseas University of Patras and CTI Greece Viktor K. Prasanna University of Southern California USA VICE GENERAL CHAIR Azzedine Boukerche University of Ottawa Canada PROGRAM CHAIR James Aspnes Yale University USA WORKSHOPS CHAIR Jim Reich Palo Alto Research Center USA POSTER CHAIR Wendi Heinzelman University of Rochester USA PROCEEDINGS CHAIR Yang Yu Motorola Labs USA PUBLICITY CO-CHAIRS Amol Bakshi University of Southern California USA Sanjay Jha University of New South Wales Australia Christian Schindelhauer University of Freiburg Germany FINANCE CHAIR Germaine Gusthiot University of Geneva Switzerland STEERING COMMITTEE Sajal Das, University of Texas at Arlington, USA Josep Diaz, UPC Barcelona, Spain Deborah Estrin, University of California, Los Angeles, USA Phil Gibbons, Intel Research, Pittsburgh, USA Sotiris Nikoletseas, University of Patras and CTI, Greece Christos Papadimitriou, University of California, Berkeley, USA Kris Pister, University of California, Berkeley, and Dust, Inc., USA Viktor Prasanna, University of Southern California, Los Angeles, USA Jose Rolim, University of Geneva, Switzerland (CHAIR) -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From mip4-bounces@ietf.org Thu Oct 26 17:03:24 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdCNc-0007M7-E5; Thu, 26 Oct 2006 17:03:12 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdBMu-00021x-TL; Thu, 26 Oct 2006 15:58:24 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdBEu-0007E2-Cy; Thu, 26 Oct 2006 15:50:08 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 5AA8726E53; Thu, 26 Oct 2006 19:50:08 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GdBEu-0005Kl-80; Thu, 26 Oct 2006 15:50:08 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 26 Oct 2006 15:50:08 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-reg-tunnel-04.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Mobility for IPv4 Working Group of the IETF. Title : Mobile IPv4 Regional Registration Author(s) : E. Fogelström, et al. Filename : draft-ietf-mip4-reg-tunnel-04.txt Pages : 35 Date : 2006-10-26 Using Mobile IP, a mobile node registers with its home agent each time it changes care-of address. This document describes a new kind of "regional registrations", i.e. registrations local to the visited domain. The regional registrations are performed via a new network entity called a Gateway Foreign Agent (GFA) and introduce a layer of hierarchy in the visited domain. Regional registrations reduce the number of signaling messages to the home network, and reduce the signaling delay when a mobile node moves from one foreign agent to another within the same visited domain. This document is an optional extension to the Mobile IPv4 protocol. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-reg-tunnel-04.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mip4-reg-tunnel-04.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mip4-reg-tunnel-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-10-26120907.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-reg-tunnel-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-reg-tunnel-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-10-26120907.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ --NextPart--