From nemo-bounces@ietf.org Wed Jun 01 07:02:22 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DdQzO-0002DY-Qr; Wed, 01 Jun 2005 07:02:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DdQzN-0002DL-20 for nemo@megatron.ietf.org; Wed, 01 Jun 2005 07:02:21 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03711 for ; Wed, 1 Jun 2005 07:02:18 -0400 (EDT) Received: from lisbon.ucdavis.edu ([169.237.104.166]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DdRJA-00043G-1r for nemo@ietf.org; Wed, 01 Jun 2005 07:22:49 -0400 Received: from lymeon.ucdavis.edu (lymeon.ucdavis.edu [169.237.104.171]) by lisbon.ucdavis.edu (8.13.3/8.13.1/it-defang-5.3.0) with ESMTP id j51B2Gvn029493 for ; Wed, 1 Jun 2005 04:02:17 -0700 (PDT) Received: from lymeon.ucdavis.edu (localhost [127.0.0.1]) by lymeon.ucdavis.edu (8.12.10/8.12.9/UCD5.2.0) with ESMTP id j51B2Gb4029503 for ; Wed, 1 Jun 2005 04:02:16 -0700 (PDT) Received: (from www@localhost) by lymeon.ucdavis.edu (8.12.10/8.12.9/Submit) id j51B2Gdm029502; Wed, 1 Jun 2005 04:02:16 -0700 (PDT) Date: Wed, 1 Jun 2005 04:02:16 -0700 (PDT) Message-Id: <200506011102.j51B2Gdm029502@lymeon.ucdavis.edu> To: nemo@ietf.org From: "Fan Zhao" X-Errors-To: fanzhao@blue.ucdavis.edu X-Mailer: Geckomail-b16 X-Originating-IP: [128.120.178.196] X-User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) X-Scanned-By: MIMEDefang 2.49 on 169.237.104.195 X-Spam-Score: 0.0 (/) X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027 Subject: [nemo] Deadline extended: JSAC-MRNM X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-bounces@ietf.org PLEASE ACCEPT OUR APOLOGIES IF YOU RECEIVE MULTIPLE COPIES CALL FOR PAPERS IEEE Journal on Selected Areas in Communications MOBILE ROUTERS AND NETWORK MOBILITY The deadline is extened until June 5th. http://www.argreenhouse.com/society/J-SAC/Calls/mobile_routers.html Network mobility support is concerned with managing the mobility of an entire network that is changing its point of attachment to the Internet and thus its reachability in the Internet topology. If network mobility is not explicitly supported by some mechanisms, existing sessions break and connectivity to the global Internet is lost. A mobile network is composed of Mobile Router(s) (MR) and Mobile Network Nodes (MNN) that can be fixed or mobile. There has been rapid development in network mobility support, i.e., providing Internet connectivity to the networks that move using mobile routers since the inception of Mobile IPv4 in 1996. Seamless Internet access in public transportation such as in trains and busses can be possible if mobile routers are used. Cars with low-power sensors seamlessly connected to the Internet constitute yet another example of networks which move. To date, some airline companies announced Internet connectivity support during commercial flights and this trend is expected to accelerate and cover most if not all flights. This issue is focused on modeling, analysis, and simulation of network mobility support protocols. We solicit papers presenting original and unpublished work including, but not limited to the following topics: * Modeling and Analysis of Network Mobility o Modeling, analysis and simulation of mobile router o Protocols for route optimization o Mobility issues inside a mobile network o Mobile IPv6 extensions for route optimization o Nested mobile networks o Multihomed mobile networks o Operational issues to deploy mobile networks o Auto-configuration for mobile networks o Mobile router support on cellular phone platforms * Services in the Networks that Move o Service advertisement and discovery protocols in networks that move o Specifications nad models of services for network mobility o Encryption and authentication in service access for network mobility * Security Issues in Network Mobility o Security analysis of present network mobility support protocols o Applications of AAA and EAP to network mobility o Interaction with security-enhanced modules in other layers (vertically) or other middle boxes (horizontally) Prospective authors should follow the IEEE J-SAC manuscript format described in the Information for Authors. Authors MUST submit their draft manuscripts through the EDAS peer review website, together with a short abstract (approximately 150 words) in the EDAS website form. Please note potential authors should create their own accounts through the EDAS peer review website before submitting manuscript(s). EDAS will accept manuscripts in PDF format only. There will be one round of reviewers and acceptance will be limited to those papers requiring only moderate revisions. The following timetable applies: Manuscript Submission: JUNE 5, 2005 Acceptance Notification: December 1, 2005 Final Manuscript Due: March 1, 2006 Publication: 3rd Quarter 2006 Guest Editorial Board: Behcet Sarikaya Computer Science Dept Univ of Northern British Columbia Prince George, BC Canada V2N 4Z9 sarikaya@unbc.ca S. Felix Wu Dept of Computer Science Univ of California at Davis Davis, CA 95616 USA wu@cs.ucdavis.edu Gopal Dommety Cisco Systems, Inc 170 West Tasman Dr San Jose, CA 95134-1706 USA gdommety@cisco.com Claude Castelluccia INRIA Rhône-Alpes ZIRST 655 Ave de l'Europe Montbonnot 38334 Saint Ismier cedex France claude.castelluccia@inria.fr Thierry Ernst Jun Murai Lab Keio Univ K-square Town Campus 1488-8 Ogura, Saiwai-ku, Kawasaki, Kanagawa 212-0054 Japan ernst@sfc.wide.ad.jp Charles E. Perkins Communication Systems Lab Nokia Research Center 313 Fairchild Dr Mountain View, CA 94943 USA charliep@iprg.nokia.com From nemo-bounces@ietf.org Fri Jun 03 12:19:08 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DeEt2-0000QV-1j; Fri, 03 Jun 2005 12:19:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DeEt0-0000Os-1t; Fri, 03 Jun 2005 12:19:06 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11847; Fri, 3 Jun 2005 12:19:03 -0400 (EDT) From: Basavaraj.Patil@nokia.com Received: from mgw-ext01.nokia.com ([131.228.20.93]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DeFDF-00081q-AF; Fri, 03 Jun 2005 12:40:02 -0400 Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id j53GIwma016001; Fri, 3 Jun 2005 19:19:02 +0300 Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 3 Jun 2005 19:18:43 +0300 Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 3 Jun 2005 11:18:40 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 3 Jun 2005 11:18:39 -0500 Message-ID: <456943D540CFC14A8D7138E64843F85301042164@daebe101.NOE.Nokia.com> Thread-Topic: Design team formed for addressing v4 traversal Thread-Index: AcVoV+cHzxslcntLTH+GlD2uf4edtg== To: , X-OriginalArrivalTime: 03 Jun 2005 16:18:40.0472 (UTC) FILETIME=[E7773580:01C56857] X-Spam-Score: 0.3 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Content-Transfer-Encoding: quoted-printable Cc: Subject: [nemo] Design team formed for addressing v4 traversal X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-bounces@ietf.org Hello, The MIP6 and NEMO WGs have formed a design team to work on developing a comprehensive solution for dealing with the problem of MIP6 MNs/Routers that roam into and attach to a v4 only access network.=20 The design team consists of : James Kempf, Ryuji Wakikawa, Pascal Thubert, Hesham Soliman and, Vijay Devarapalli =20 The MIP6/NEMO chairs will advise the design team as needed. The charter of the design team is to: 1. Write up the problem statement, scenarios to be addressed and requirements=20 2. Develop a protocol solution to address the scenarios The design team will present at least the scenarios and problem statement being worked on at the next IETF meeting (IETF63). A mailing list for the DT discussions has been setup (thanks to Ryuji). The archives will be made available to the MIP6/NEMO WGs when the design team has concluded.=20 If you have any questions about this work, please contact the chairs. -MIP6/NEMO chairs From nemo-bounces@ietf.org Tue Jun 07 03:49:37 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DfYq9-0005uR-9y; Tue, 07 Jun 2005 03:49:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DfYZ1-0003N6-Rq; Tue, 07 Jun 2005 03:31:55 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23815; Tue, 7 Jun 2005 03:31:53 -0400 (EDT) Received: from szxga02-in.huawei.com ([61.144.161.54] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DfYtz-0003T2-Pd; Tue, 07 Jun 2005 03:53:38 -0400 Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IHP00CQNEGUQG@szxga02-in.huawei.com>; Tue, 07 Jun 2005 15:36:31 +0800 (CST) Received: from szxml02-in ([172.24.1.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IHP00DMKEGUTB@szxga02-in.huawei.com>; Tue, 07 Jun 2005 15:36:30 +0800 (CST) Received: from c03731 ([10.110.90.91]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IHP008WKEGNHG@szxml02-in.huawei.com>; Tue, 07 Jun 2005 15:36:24 +0800 (CST) Date: Tue, 07 Jun 2005 15:31:41 +0800 From: chenhongfei In-reply-to: <42A4D42F.4050708@iprg.nokia.com> To: "'Vijay Devarapalli'" Message-id: <000001c56b32$f3767250$5b5a6e0a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Mailer: Microsoft Outlook, Build 10.0.2627 Content-type: multipart/related; boundary="Boundary_(ID_R0/5BqIVchcsgNI5gXyMyg)" Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Spam-Score: 0.3 (/) X-Scan-Signature: b148ead9c6581b10314b24a9438d3a5f X-Mailman-Approved-At: Tue, 07 Jun 2005 03:49:35 -0400 Cc: nemo@ietf.org, mip6@ietf.org, Basavaraj.Patil@nokia.com Subject: [nemo] RE: RE: [Mip6] Design team formed for addressing v4 traversal X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-bounces@ietf.org This is a multi-part message in MIME format. --Boundary_(ID_R0/5BqIVchcsgNI5gXyMyg) Content-type: multipart/alternative; boundary="Boundary_(ID_r59r0AblhMIBmKPlqDqhkA)" --Boundary_(ID_r59r0AblhMIBmKPlqDqhkA) Content-type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7BIT Hi It's difficult to describe my question clearly by word. look the figure please. Router A is the gateway of the Enterprise network. Router B is a router location in the v6 internet. HOST-A and HOST-B are v4/v6 pc. Enterprise network and the v6 internet and the Metro network are operated by different department. Router A should access the v6 internet without changed the Metro network. After I read the charter of the design team. I think that result of the design team is a good solution. Router B is HA and HOST-A is MN. Is that right? -----Original Message----- From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com] Sent: Tuesday, June 07, 2005 6:55 AM To: chenhongfei Cc: Basavaraj.Patil@nokia.com; nemo@ietf.org; mip6@ietf.org Subject: Re: Re: [Mip6] Design team formed for addressing v4 traversal I am not sure I understood your questions completely, but I will try to answer some of the questions. chenhongfei wrote: > Hello, > > CNGI(China Next Generation Internet) which is ipv4/ipv6 network has been > builded last year. But the network of the collage is IPv4 only now. and > the gateway router of the collage isn't connect CNGI directly. It > connect CNGI across the metro network which is ipv4 only. So the ISATAP > isn't a good solution. I read about the charter of design term. Could > this protocol solve this issue? yes. the college network and the metro network will both be treated as pure IPv4 routable Internet and the MN would be able to reach the IPv6 Home Agent. > Could HA assign a fixed IPv6 address for > MN? yes. the MN can have a fixed IPv6 HoA. Vijay > > Hongfei Chen > > -----SJ<~T-<~----- > 7"<~HK: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] 4z1m > Basavaraj.Patil@nokia.com > 7"KMJ1 JU<~HK: mip6@ietf.org; nemo@ietf.org > VwLb: [Mip6] Design team formed for addressing v4 traversal > > > Hello, > > The MIP6 and NEMO WGs have formed a design team to work on developing > a comprehensive solution for dealing with the problem of MIP6 > MNs/Routers that roam into and attach to a v4 only access network. > > The design team consists of : > James Kempf, Ryuji Wakikawa, Pascal Thubert, Hesham Soliman and, > Vijay Devarapalli > > The MIP6/NEMO chairs will advise the design team as needed. > > The charter of the design team is to: > > 1. Write up the problem statement, scenarios to be addressed and > requirements > 2. Develop a protocol solution to address the scenarios > > The design team will present at least the scenarios and problem > statement being worked on at the next IETF meeting (IETF63). > A mailing list for the DT discussions has been setup (thanks to > Ryuji). The archives will be made available to the MIP6/NEMO WGs when > the design team has concluded. > > If you have any questions about this work, please contact the chairs. > > -MIP6/NEMO chairs > > > > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www1.ietf.org/mailman/listinfo/mip6 > > > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www1.ietf.org/mailman/listinfo/mip6 --Boundary_(ID_r59r0AblhMIBmKPlqDqhkA) Content-type: text/html; charset=us-ascii Content-Transfer-Encoding: 7BIT

Hi

It’s difficult to describe my question clearly by word. look the figure please.

Router A is the gateway of the Enterprise network. Router B is a router location in the v6 internet. HOST-A and HOST-B are v4/v6 pc. Enterprise network and the v6 internet and the Metro network are operated  by different department. Router A should access the v6 internet without changed the Metro network. After I read the charter of the design team. I think that result of the design team is a good solution. Router B is HA and HOST-A is MN. Is that right?

 

 

-----Original Message-----
From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com]
Sent: Tuesday, June 07, 2005 6:55 AM
To: chenhongfei
Cc: Basavaraj.Patil@nokia.com; nemo@ietf.org; mip6@ietf.org
Subject: Re: Re: [Mip6] Design team formed for addressing v4 traversal

 

I am not sure I understood your questions completely, but I will

try to answer some of the questions.

 

chenhongfei wrote:

> Hello,

>

> CNGI(China Next Generation Internet) which is ipv4/ipv6 network has been

> builded last year. But the network of the collage is IPv4 only now. and

> the gateway router of the collage isn't connect CNGI directly. It

> connect CNGI across the metro network which is ipv4 only. So the ISATAP

> isn't a good solution. I read about the charter of design term. Could

> this protocol solve this issue?

 

yes. the college network and the metro network will both be treated

as pure IPv4 routable Internet and the MN would be able to reach

the IPv6 Home Agent.

 

> Could HA assign a fixed IPv6 address for

> MN?

 

yes. the MN can have a fixed IPv6 HoA.

 

Vijay

 

>

> Hongfei Chen

>

> -----SJ<~T-<~-----

> 7"<~HK: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] 4z1m

> Basavaraj.Patil@nokia.com

> 7"KMJ1<d: 2005Dj6TB4HU 0:19

> JU<~HK: mip6@ietf.org; nemo@ietf.org

> VwLb: [Mip6] Design team formed for addressing v4 traversal

>

>

> Hello,

>

> The MIP6 and NEMO WGs have formed a design team to work on developing

> a comprehensive solution for dealing with the problem of MIP6

> MNs/Routers that roam into and attach to a v4 only access network.

>

> The design team consists of :

> James Kempf, Ryuji Wakikawa, Pascal Thubert, Hesham Soliman and,

> Vijay Devarapalli 

>

> The MIP6/NEMO chairs will advise the design team as needed.

>

> The charter of the design team is to:

>

> 1. Write up the problem statement, scenarios to be addressed and

>    requirements

> 2. Develop a protocol solution to address the scenarios

>

> The design team will present at least the scenarios and problem

> statement being worked on at the next IETF meeting (IETF63).

> A mailing list for the DT discussions has been setup (thanks to

> Ryuji). The archives will be made available to the MIP6/NEMO WGs when

> the design team has concluded.

>

> If you have any questions about this work, please contact the chairs.

>

> -MIP6/NEMO chairs

>

>

>

> _______________________________________________

> Mip6 mailing list

> Mip6@ietf.org

> https://www1.ietf.org/mailman/listinfo/mip6

>

>

> _______________________________________________

> Mip6 mailing list

> Mip6@ietf.org

> https://www1.ietf.org/mailman/listinfo/mip6

--Boundary_(ID_r59r0AblhMIBmKPlqDqhkA)-- --Boundary_(ID_R0/5BqIVchcsgNI5gXyMyg) Content-id: Content-type: image/gif; name=image001.gif Content-transfer-encoding: base64 Content-disposition: attachment; filename=image001.gif Content-Transfer-Encoding: base64 R0lGODlhxwEMAXcAMSH+GlNvZnR3YXJlOiBNaWNyb3NvZnQgT2ZmaWNlACH5BAEAAAAALAAAAADG AQwBhQAAAAAAAAwMDAcHBxUVFRAQEBMTExgYGA8PDxQUFBcXFw4ODg0NDQkJCREREQoKChISEhkZ GQQEBCMjIysrKzw8PDMzMzs7OyoqKiAgIFxcXFhYWEVFRVZWVl9fX2JiYn9/f3t7e3Z2dmxsbHp6 emtra5OTk4ODg4eHh5eXl52dnZWVlbe3t6+vr6enp9vb29fX19/f38/Pz8fHx+/v7+fn5/f39/// /wECAwECAwECAwECAwECAwECAwECAwECAwb/QEBASBwai8ijMslcOpvQpzRKnVqr2Ku2ORR2A98w wDsGl8XktFmNXrvb8LOcPX/X43Tydp/t8/9+WWtjhIWGh4iJiouMjY6PkJGSk5SVlpeYmZqbnJ2e kV2foqOkpaanqKmqq6yag62wsbKztLW2t6ahuLu8vb6/wMGPr8LFxsfIycrDy83Oz9DRrcTS1dbX 2Nm62dzd3t+91ODj5OXmm9vn6uvs7YTi7vHy89Hp9Pf4+cDw+v3+/6nsARxIsGAmfgYTKlxoSCDD h7TASJxoZglEVggvaiQFyApFixsrOQxJEl1GdERKSjqpsiUjkKtGuiwkc6bNMl5qBtSpkuXN/41G KvqSmPInz58Lgx69RdToUqT6lAqFBpPkU6j0mo7TCvQqVndepXF9GParOp/fxiZEa3ZdWW9qB75t 2y0uPrtR59KtdkSh3q1757G9+xdu4cDJ8Dr6yG+Q4mJ9+x1GfKzwl3eHqAkMOxmUv8GUnx2+jLMh os0iZXUWG7rcZNI5YxMLqqcibaK2z6yGBDrt7ta4Oodxo7t06al9adc+buu3MufAm3uCjTOyLtKX JxYdTly6YOjRZwk3jnk7TeZIyqecHVxw+LrTKZou/k5+7o+ytadpDj5Y7/f7IIabWwBi0x9ASpnz X4HhAJjggdMwyJeEmEEYk4UUfoLhRRue0v9hhp18yNCC4YgIIiYmjkhieycukyJZL7oSY4sr0Xja iuLZmJiOicxICY48ouIjh0DGFCRkRypS5E5J/jJkSU++1KSTUyqJzJJVopTlaZVtyaKXmRmDJZg/ ksklkmaqlmaYwoy5JjNvnudfnBjRKec+UR6Zp1EB2imkn/MNtSePg/LZIKClFGooL24iqp6j5H0J 6XST3hmcoidiilSUmoLY6U2cfiqhqDM9ZmSlnJDqFH+optrqjS+q6uCrVoona3i3QmVirtHxuumH jQLqq67B1krrJcNipV8uyQbWrFlVhXgsitNaYuokxdr5bGjjVSvmsiiC29Zr29K1YSg61YT/roCu elvmqUUtou6j5prk7rs7OabdG01NlVO5Ox50748WWlefcd29si63BwE87qmwdfcvdea1NpfD9QaE nhoHW1oxw8hi/LCHdvRrMm76XqsrtXruIrKeL0+oBX7RujIwsixnqLKUu8U8skg+XxmbhmMG/VVZ Rvs3IMmW3ZyatUnXooS/Ru7co9NP46usfC4vGPWi2H4dYadW0xsiY8ZOLC5NYnuntU3ZcjSYcxHf eF7dDbUtKSh6Mzvszr/hfXd5gpu9F9Klxh1hjtvZ5i929T3Yt9RAQxmvNrxpqBt2eHN3nMTOejW5 va6lS+nlU/e7cXUfO1s5UAQ28lqkqCNM/3vhrmMbkt7p4oifx5yLi67ichGs0eRHRYa1x3BymGjK UivPMykvVG/99djTKProOD/fcaBZZz607J5cb8L56Kev/vU6v50Uyd8zX+P8kUu5SfUmBHCD+vzn /5EJ1WMQZ7hnrVwwgQ0oU5hyHHeb4SyHPdKj3STwZ4IbWNCCAehf+vR3wf0B8AUFEt3xPASF9dAn XkLJjgnrlsKXbGMuL+BfBy14Pv2hj4M0rKAHP4ir15GFhE5QXXpQWJ0B3cZ2aFiM4SARQw3qsIPn m6ETAdirAjrPgCucj8EIR0QTIpF1i1nYBKc4wx3qcIroAyFwBgiR/hjRcZtLUP3giBy2Sf9FOUos SxPRyMcpqhFk7ltLG//zgT1qEIceLKMT/wjIsLXxeF4p5AY3CMUoKlKDjKQM4h7pvKt8oJB7LKMZ ZXjBDKbxBR+oog/fN8KnfPKT+CujKcnYweq9UpWBLAgBrXg5Rrzylebr4ylt+UtcOpKVsJNgIn7J TFBi75nXa+Yt18hLv1hliYiQpja3yc1PKqlsI4JaOFVxR7zwRBzgEWMjusnOdtrxd2CjnyDJyUUJ ogU1HLEUYySigXb6U5t/3OfWVkkQDF3HdqZJXtpO9yiBovKfEAXmO/cVT89Yk571zA/V8qOH2lCM oQiD50Mj6s9Mqg2eLWHjPDVGOCGCbl3/LfRiL0FaBJQCYKQk5WYA87bPpfUkl5+pU0ZZxzXzqHCI M2VoT9NBzJw2c6c94pdNR2g8g5xLTul44Z2S0zj5EW2pirCeU2FpUrvdjXgKAqpkhKo28KGOjkLE ZqrQtp9FRLOd7GuYS7ZnVVgUzKtns89GGwFNaF5ol82zaKbgJ9fAdixZU11rVQsaT3U2o6cICl/x zLW252A2KgT9B2LlWSOfumhiklVrPkbLGyAV9bJoFVpog+qXyAItghNixyZ1WdvXztVhnYVLyJiC hViwFlbBdRXA0CYT3KKpmn41Yk2XCk64+TafyxXoIQQwgAlsAAQcIEABnhOusSU1c9VN/6xoYwtG bdiUAB2gwQxhQAEDyBa6fsvnKI7rVo3FrKgGYIEoLRiCA4hJr6J4kJAGm7MQntdAhDDACQZ8wQpg 6i+zuy45k0tat+TJud6YAIUvWAMEtElGDauZcZGqWuGm13vqQMGIK3xigUFNVFazrWYFpeGIRI0A Ap7xDURQKMtw5rIsNtZJzokn+/DYHAOQr5Bb0CebHbMeSpyDvPJYIh0zhb2yKAAMhHyDFIz3UKST HYOdoRiKCrY49xkcozjMqPF5wwVkTiWatSQvMGPEIVvkGBjx2F6XnbaxVBkBmScwlPhsOa1nwgNM TYtaywFWGgSowYxZQIA6a26h5LAH5P8WWCHgITrBy+3vNSowYhoooGv7Za1WTDY0/TAQei8mmJ8T xSZvxFeU9PV0gh+tW/UqrceiUTU2FNCCGFxQBidIgLBRfTV5mO7YXk72pauRAAY0wAIBcIB9Dc3r M31HzXuiK3y2bSZ47FLFpz7srtka75WVu9d5ieCHz5HVHsJY2Xd56+Lcg+9GDtvclGW3cuc9bQf/ u95ZAThK1A0WhBv801YBcYq1a+1qiwaOJzyZrelsZbkVvCCFNeyNs30Wi7NZPTBFj+CgEzdRGySY fczrShhe45MfWqZa7q9laUptidMDfzZEI2N4aHT+LhGytk6oy0nePSwq3B0UnOEsDyn/RR4im7cu /znFPtpvZZZ3wVdvhyEtWcmk56+SOfzg1zcb9oABvXXreVx8/pr2daxdfZfsOiapLlpQkxeh6dFq oMj1576f4+/pu6Qlc35Nj8NWjrWejQJz7XMSQjyBJ8y8b/MEeWEKs6w/rHupjPtR8m0Mcl5U/C4k OUVEsv2Ci7S0WTelpqBnmcXOtXmUaF9DSuL+9sfvH+pTr/rdxar1LqR064XPC7KiT5S0xGD6bJlS K2kcmYwTYaHxPtPvt+KXsdQ6H2fY1J+iu/LRe7CSa0cvOc79T0N4qvVMf767TnN3O+d0rucd4idT sGc2Q7dg+KFTKQdN26R7HSYXPJcZ/70BeuMzFlxhgQooUGP1TxC4c33VIBCSbhwHAB3oTx94Zfnm JHHzAAtwASBgAQ2wAHUCaAx2gniVZCtVdQE3J85BABegaR0EAxjgN4SXCDiFg9KkRtQVU1kxGoQB GcWiAhRGApRCXZeQhEooUVzSEa4hfzsWOwf2Gx4wYxewdzSTCVqohFCVZteAefvVDpz3Z7sRATYw YzUgbcxgg5SmCU2Fgzs1h/VDFbKBUfwGWwlWAmTGAc2lYwciVmPVhoNYcp7FcEkzgTcmCngmZCiA XCU4C/7XTTpneGHog27jYsm2GgzgbELGaRT4ibjQgKP4ewh2bHv2hlC3Gg4gA2RGZf+vqIOhplxV RiXWYH4HBoaSUAApQGZERncodovEYiDGKAkfQGYVAHbtsjdzwmaYeDqrAQGsSGEzMG7OaBLPpyq3 IjKg4woWMGI2kAEhiGoHkjra9i0vMzyeoAC/VkY1cI07KI9XSFGs0SZBs46bIAAK4AJjZkEysAIE IICdpzlYKAVuhow/J4JfCHGRkAAFIAHg5gB6eFHtcylfozCe0iKxYpGYYyMQSVys1zfsQSEtyR8F 042MY3SaFCTXUk5NKIh8UXYC1CQKdgVbdlz4FJTL84SWFz1HOIBMkpRX9E0uWX5+pTtWCZXxsGQq GYeAVpUR6JRYWWzGRocH82a35lH/+6FAy/EvD1QyhAaWYXkWTJYj1/EENcUcdjBUuZFFB5R3wLiU cdly4rNiWjRdW2QwUoVVUXdEC5NEgxmYcvmYAzdqXcSXsRdpineAlCmZkAlpY5kvoLcvXBOaGYhr I2eAUvWWxNaZ/LYUueIrMzktrsmNvBKbx8IWtolxrOmZn6ksu+lhipU7v5mRnPkzw7kVs5mTxxmM wXk4yxlqOHZSXRlGzWeIzylcVwkvuON7q+l4cXidhlGK3/l6YaJQgDlw4LmS4qmbEcNAb9VAdxlX vZee7sWD95Z3CUMdk5Z4iEeY9Kme+HVwq5MEyxJz/HlQtvKf9Rku05idZAc+Bmod/wg6nwpajIFV NJGDgW5FmuuYkhWKixK5JHxndtb5oVhmhBfDWCTKUib6k/6VhkRJILl5mxhJceDgky16KYlhkwvX oDl6X4dXD035oy7ymh/no0T6clSBYzyapGh3ogEyo6z5LIoipbvZpPZJbk4qlsX4JFi6pRfCDSlp pcepjrEFh2Calf/Vl7oTREiapjcqlz0JVm8Kp60ZVHVqpx2npxX6pXyaJWT6pwgSqIKaWoV6nX56 qC2jqIhKqIwacY+6nIkaqdpDqWXqqJYqh5n6m5O6qTLpqVOKqaDKm6OKlZ1aqu8hqqiKnKtqqq1q qqr6qmIqq0l5qrTKLrfqNLaaqzAZw6v3squ+ejTB+quxOqz1aKw06oXK2pdi1Kww96yI56zRCq0f I63VSq3WmoDGGgQAOw== --Boundary_(ID_R0/5BqIVchcsgNI5gXyMyg)-- From nemo-bounces@ietf.org Thu Jun 09 07:42:43 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DgLQp-0004qK-0j; Thu, 09 Jun 2005 07:42:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DgLQn-0004q8-36 for nemo@megatron.ietf.org; Thu, 09 Jun 2005 07:42:41 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16407 for ; Thu, 9 Jun 2005 07:42:40 -0400 (EDT) Received: from mail.sfc.wide.ad.jp ([203.178.142.146]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DgLmE-0005cH-KP for nemo@ietf.org; Thu, 09 Jun 2005 08:04:51 -0400 Received: from iseran.local (jules.nautilus6.org [203.178.138.2]) by mail.sfc.wide.ad.jp (Postfix) with ESMTP id D473F4CC95 for ; Thu, 9 Jun 2005 20:41:46 +0900 (JST) Date: Thu, 9 Jun 2005 20:42:21 +0900 From: Thierry Ernst To: ml-nemo Message-Id: <20050609204221.2f04d59c.ernst@sfc.wide.ad.jp> Organization: Keio University X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; powerpc-apple-darwin7.8.0) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Multipart=_Thu__9_Jun_2005_20_42_21_+0900_1s5sfS3G_Q9vQyJq" X-Spam-Score: 0.0 (/) X-Scan-Signature: 2bf730a014b318fd3efd65b39b48818c Subject: [nemo] Fw: I-D ACTION:draft-montavont-mobileip-multihoming-pb-statement-04.txt X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-bounces@ietf.org This is a multi-part message in MIME format. --Multipart=_Thu__9_Jun_2005_20_42_21_+0900_1s5sfS3G_Q9vQyJq Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Dear all, We have submitted an improved version of our Problem Statement draft for multihomed mobile nodes operating MIP6. This problem statement could apply to the case of Mobile Router operating NEMO Basic Support (issues discussed in that draft are a subset of draft-ietf-nemo-multihoming-issues. We would appreciate to get comments specific to the case of MNs operating Mobile IPv6 on the monami6 ML recently created to discuss the set up of a Monami6 BOF at the forthcoming IETF meeting in Paris. The BOF is about multihomed mobile nodes operating either Mobile IPv6 or NEMO Basic Support. Please visit http://www.nautilus6.org/ietf/index.html for joining the discussion and to read more about the Monami6 objectives. Thierry --Multipart=_Thu__9_Jun_2005_20_42_21_+0900_1s5sfS3G_Q9vQyJq Content-Type: message/rfc822 Content-Disposition: inline Return-Path: X-Original-To: ernst@sfc.wide.ad.jp Received: from ironport1.sfc.wide.ad.jp (ironport1.sfc.wide.ad.jp [203.178.142.150]) by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 093F04C0E5; Thu, 9 Jun 2005 05:15:29 +0900 (JST) Received: from megatron.ietf.org (132.151.6.71) by ironport1.sfc.wide.ad.jp with ESMTP; 09 Jun 2005 05:15:48 +0900 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAQAAA+k= X-IronPort-AV: i="3.93,184,1114959600"; d="txt'208?scan'208,208"; a="1935063:sNHT94478468" Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dg6wD-0006C8-GN; Wed, 08 Jun 2005 16:14:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dg6ah-0005Km-Rv for i-d-announce@megatron.ietf.org; Wed, 08 Jun 2005 15:51:55 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00830 for ; Wed, 8 Jun 2005 15:51:53 -0400 (EDT) Message-Id: <200506081951.PAA00830@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Wed, 08 Jun 2005 15:51:53 -0400 Subject: I-D ACTION:draft-montavont-mobileip-multihoming-pb-statement-04.txt X-BeenThere: i-d-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: internet-drafts@ietf.org List-Id: i-d-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: i-d-announce-bounces@ietf.org Errors-To: i-d-announce-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Analysis of Multihoming in Mobile IPv6 Author(s) : N. Montavont, et al. Filename : draft-montavont-mobileip-multihoming-pb-statement-04.txt Pages : 33 Date : 2005-6-8 The use of multiple interfaces is foreseen to provide ubiquitous, permanent and fault-tolerant access to the Internet, particularly on mobile nodes which are more prone to failure or sudden lack of connectivity. However, Mobile IPv6 currently lacks support for such multihomed nodes. Individual solutions have been proposed to extend Mobile IPv6 but all issues have not been addressed in a single document. The purpose of the present document is thus to fill up this gap and to raise the discussion in order to make sure that forthcoming solutions will address all the issues. In this document, we propose a taxonomy to classify the situations where a mobile node could be multihomed. This taxonomy is then used to highlight the issues preventing mobile nodes operating Mobile IPv6 to be multihomed. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-montavont-mobileip-multihoming-pb-statement-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-montavont-mobileip-multihoming-pb-statement-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-montavont-mobileip-multihoming-pb-statement-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: <2005-6-8162236.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-montavont-mobileip-multihoming-pb-statement-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-montavont-mobileip-multihoming-pb-statement-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-6-8162236.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --NextPart-- --Multipart=_Thu__9_Jun_2005_20_42_21_+0900_1s5sfS3G_Q9vQyJq-- From nemo-bounces@ietf.org Thu Jun 09 14:53:39 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DgS9r-0003dz-4x; Thu, 09 Jun 2005 14:53:39 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DgS9p-0003dS-L1; Thu, 09 Jun 2005 14:53:38 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03675; Thu, 9 Jun 2005 14:53:36 -0400 (EDT) Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DgSVK-0002rK-H1; Thu, 09 Jun 2005 15:15:52 -0400 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j59IL1k11805; Thu, 9 Jun 2005 11:21:01 -0700 X-mProtect: <200506091821> Nokia Silicon Valley Messaging Protection Received: from mvdhcp141133.americas.nokia.com (172.18.141.133, claiming to be "[127.0.0.1]") by darkstar.iprg.nokia.com smtpd8NMjaV; Thu, 09 Jun 2005 11:20:59 PDT Message-ID: <42A89003.4000300@iprg.nokia.com> Date: Thu, 09 Jun 2005 11:52:51 -0700 From: Vijay Devarapalli User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: chenhongfei References: <000001c56b32$f3767250$5b5a6e0a@china.huawei.com> In-Reply-To: <000001c56b32$f3767250$5b5a6e0a@china.huawei.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 4b7d60495f1a7f2e853e8cbae7e6dbfc Content-Transfer-Encoding: 8bit Cc: nemo@ietf.org, mip6@ietf.org, Basavaraj.Patil@nokia.com Subject: [nemo] Re: [Mip6] Design team formed for addressing v4 traversal X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-bounces@ietf.org chenhongfei wrote: > Hi > > Its difficult to describe my question clearly by word. look the figure > please. > > Router A is the gateway of the Enterprise network. Router B is a router > location in the v6 internet. HOST-A and HOST-B are v4/v6 pc. Enterprise > network and the v6 internet and the Metro network are operated by > different department. Router A should access the v6 internet without > changed the Metro network. After I read the charter of the design team. > I think that result of the design team is a good solution. Router B is > HA and HOST-A is MN. Is that right? yes. this scenario will be addressed. regards Vijay > > > > > > -----Original Message----- > From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com] > Sent: Tuesday, June 07, 2005 6:55 AM > To: chenhongfei > Cc: Basavaraj.Patil@nokia.com; nemo@ietf.org; mip6@ietf.org > Subject: Re: Re: [Mip6] Design team formed for addressing v4 traversal > > > > I am not sure I understood your questions completely, but I will > > try to answer some of the questions. > > > > chenhongfei wrote: > >> Hello, > >> > >> CNGI(China Next Generation Internet) which is ipv4/ipv6 network has been > >> builded last year. But the network of the collage is IPv4 only now. and > >> the gateway router of the collage isn't connect CNGI directly. It > >> connect CNGI across the metro network which is ipv4 only. So the ISATAP > >> isn't a good solution. I read about the charter of design term. Could > >> this protocol solve this issue? > > > > yes. the college network and the metro network will both be treated > > as pure IPv4 routable Internet and the MN would be able to reach > > the IPv6 Home Agent. > > > >> Could HA assign a fixed IPv6 address for > >> MN? > > > > yes. the MN can have a fixed IPv6 HoA. > > > > Vijay > > > >> > >> Hongfei Chen > >> > >> -----SJ<~T-<~----- > >> 7"<~HK: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] 4z1m > >> Basavaraj.Patil@nokia.com > >> 7"KMJ1 >> JU<~HK: mip6@ietf.org; nemo@ietf.org > >> VwLb: [Mip6] Design team formed for addressing v4 traversal > >> > >> > >> Hello, > >> > >> The MIP6 and NEMO WGs have formed a design team to work on developing > >> a comprehensive solution for dealing with the problem of MIP6 > >> MNs/Routers that roam into and attach to a v4 only access network. > >> > >> The design team consists of : > >> James Kempf, Ryuji Wakikawa, Pascal Thubert, Hesham Soliman and, > >> Vijay Devarapalli > >> > >> The MIP6/NEMO chairs will advise the design team as needed. > >> > >> The charter of the design team is to: > >> > >> 1. Write up the problem statement, scenarios to be addressed and > >> requirements > >> 2. Develop a protocol solution to address the scenarios > >> > >> The design team will present at least the scenarios and problem > >> statement being worked on at the next IETF meeting (IETF63). > >> A mailing list for the DT discussions has been setup (thanks to > >> Ryuji). The archives will be made available to the MIP6/NEMO WGs when > >> the design team has concluded. > >> > >> If you have any questions about this work, please contact the chairs. > >> > >> -MIP6/NEMO chairs > >> > >> > >> > >> _______________________________________________ > >> Mip6 mailing list > >> Mip6@ietf.org > >> https://www1.ietf.org/mailman/listinfo/mip6 > >> > >> > >> _______________________________________________ > >> Mip6 mailing list > >> Mip6@ietf.org > >> https://www1.ietf.org/mailman/listinfo/mip6 > From nemo-bounces@ietf.org Fri Jun 17 04:26:30 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DjCBK-0002RM-FQ; Fri, 17 Jun 2005 04:26:30 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DjCBJ-0002RH-9E for nemo@megatron.ietf.org; Fri, 17 Jun 2005 04:26:29 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24268 for ; Fri, 17 Jun 2005 04:26:27 -0400 (EDT) Received: from mail.sfc.wide.ad.jp ([203.178.142.146]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DjCYM-000833-Ci for nemo@ietf.org; Fri, 17 Jun 2005 04:50:19 -0400 Received: from [10.0.2.194] (jules.nautilus6.org [203.178.138.2]) by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 7B8E64D88B for ; Fri, 17 Jun 2005 17:25:10 +0900 (JST) Message-ID: <42B28951.7050905@sfc.wide.ad.jp> Date: Fri, 17 Jun 2005 17:26:57 +0900 From: Romain KUNTZ Organization: Keio University User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: nemo Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Content-Transfer-Encoding: 7bit Subject: [nemo] Same MNP registered for several HoA X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-bounces@ietf.org Dear all, I am currently performing some multihoming tests with NEMO Basic Support. The topology I am currently testing is (2,1,1): two MRs registered to the same HA, registering the same prefix. I would like to know if there was already a consensus about the fact that a HA can or cannot allow to bind the same MNP to 2 different HoA (this is typically what happens in the scenario I mentioned). AFAIK RFC3963 does not suggest anything about that, nor the drafts about prefix delegation for NEMO BS. Regards, -- Romain KUNTZ kuntz@sfc.wide.ad.jp From nemo-bounces@ietf.org Fri Jun 17 08:28:50 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DjFxq-0000uo-Eb; Fri, 17 Jun 2005 08:28:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DjFxo-0000uj-Pn for nemo@megatron.ietf.org; Fri, 17 Jun 2005 08:28:48 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10820 for ; Fri, 17 Jun 2005 08:28:47 -0400 (EDT) Received: from motgate8.mot.com ([129.188.136.8]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DjGKu-0008Hy-5K for nemo@ietf.org; Fri, 17 Jun 2005 08:52:41 -0400 Received: from az33exr04.mot.com ([10.64.251.234]) by motgate8.mot.com (Motorola/Motgate7) with ESMTP id j5HCatW9015971; Fri, 17 Jun 2005 05:36:55 -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 j5HCVbH2020636; Fri, 17 Jun 2005 07:31:38 -0500 (CDT) Message-ID: <42B2C1E6.6020306@motorola.com> Date: Fri, 17 Jun 2005 14:28:22 +0200 From: Alexandru Petrescu User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63 MIME-Version: 1.0 To: Romain KUNTZ Subject: Re: [nemo] Same MNP registered for several HoA References: <42B28951.7050905@sfc.wide.ad.jp> In-Reply-To: <42B28951.7050905@sfc.wide.ad.jp> X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Content-Transfer-Encoding: 7bit Cc: nemo X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-bounces@ietf.org Romain KUNTZ wrote: > Dear all, > > I am currently performing some multihoming tests with NEMO Basic > Support. The topology I am currently testing is (2,1,1): two MRs > registered to the same HA, registering the same prefix. > > I would like to know if there was already a consensus about the fact > that a HA can or cannot allow to bind the same MNP to 2 different HoA > (this is typically what happens in the scenario I mentioned). Romain, I can not remember about that consensus, sorry, but I have some remarks. I am not sure one could require HA to allow or not allow multiple bindings for same MNP towards different HoAs. But what one could do is to require the routing mechanism to *work* according to some new functionality. In my understanding, for a certain prefix a router should have a unique route towards a certain IP address. If there are two such routes, and without any other differentiator, only one of those routes will be taken into account for forwarding. In practice either the last route or the first route in the table will actually be used, depending on implementation. Bindings are like routes. If one needs multiple bindings (same MNP different target HoA) then one needs a differentiator for selecting among those routes when forwarding packets. For routes, this has been done with traffic engineering I believe. OSPF TE, and MPLS come to mind, but I'm not expert. In these cases the same-prefix routes are distinguished by bandwidth and other "forced" constraints (overcoming the simple longest-prefix-matches). So one may think about OSPF-TE over tunnels, for NEMO, or similar. Just some remarks... Alex From nemo-bounces@ietf.org Fri Jun 17 15:03:30 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DjM7m-0007Zp-A4; Fri, 17 Jun 2005 15:03:30 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DjM7k-0007ZR-VW for nemo@megatron.ietf.org; Fri, 17 Jun 2005 15:03:29 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13628 for ; Fri, 17 Jun 2005 15:03:27 -0400 (EDT) Received: from node-402449f2.sfo.onnet.us.uu.net ([64.36.73.242] helo=deimos.multihop.net) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DjMUp-0003D6-Gc for nemo@ietf.org; Fri, 17 Jun 2005 15:27:25 -0400 Received: from localhost (unknown [127.0.0.1]) by deimos.multihop.net (Postfix) with ESMTP id D12AC6211 for ; Fri, 17 Jun 2005 12:02:33 -0700 (PDT) Received: from deimos.multihop.net ([127.0.0.1]) by localhost (deimos.multihop.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02536-08 for ; Fri, 17 Jun 2005 12:02:33 -0700 (PDT) Received: by deimos.multihop.net (Postfix, from userid 1013) id 958A3620B; Fri, 17 Jun 2005 12:02:33 -0700 (PDT) Received: from [192.103.16.119] (unknown [192.103.16.119]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by deimos.multihop.net (Postfix) with ESMTP id E34AC60E1 for ; Fri, 17 Jun 2005 12:02:30 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v622) Content-Transfer-Encoding: 7bit Message-Id: <284041bdbfe8c15303bbdf3b1771ce77@kniveton.com> Content-Type: text/plain; charset=US-ASCII; format=flowed To: nemo WG From: "T.J.Kniveton" Date: Fri, 17 Jun 2005 12:03:06 -0700 X-Mailer: Apple Mail (2.622) X-Virus-Scanned: by amavisd-new at deimos.multihop.net X-Spam-Score: 0.0 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 Content-Transfer-Encoding: 7bit Subject: [nemo] Fwd: Internet-Drafts Submission Cutoff Dates for the 63rd IETF Meeting in Paris, France X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-bounces@ietf.org Please remember the cutoff dates for drafts- Begin forwarded message: >> From: ietf-secretariat@ietf.org >> Date: Fri, 17 Jun 2005 00:00:02 -0400 >> >> >> There are two (2) Internet-Draft cutoff dates for the 63rd >> IETF Meeting in Paris, France: >> >> July 11th: Cutoff Date for Initial (i.e., version -00) >> Internet-Draft Submissions >> >> All initial Internet-Drafts (version -00) must be submitted by Monday, >> July 11th at 9:00 AM ET. As always, all initial submissions with a >> filename beginning with "draft-ietf" must be approved by the >> appropriate WG Chair before they can be processed or announced. The >> Secretariat would appreciate receiving WG Chair approval by Tuesday, >> July 5th at 9:00 AM ET. >> >> July 18th: Cutoff Date for Revised (i.e., version -01 and higher) >> Internet-Draft Submissions >> >> All revised Internet-Drafts (version -01 and higher) must be submitted >> by Monday, July 18th at 9:00 AM ET. >> >> Initial and revised Internet-Drafts received after their respective >> cutoff dates will not be made available in the Internet-Drafts >> directory or announced until on or after Monday, August 1st at 9:00 >> AM ET, when Internet-Draft posting resumes. Please do not wait until >> the last minute to submit. >> >> PLEASE NOTE THE CHANGE OF PROCEDURE: If you submit an initial or >> revised Internet-Draft after their respective cutoff deadlines, then >> your document will be retained and posted when Internet-Draft >> processing resumes. You will no longer be required to resubmit the >> document. >> >> Thank you for your understanding and cooperation. If you have any >> questions or concerns, then please send a message to >> internet-drafts@ietf.org. >> >> The IETF Secretariat >> >> FYI: The Internet-Draft cutoff dates as well as other significant >> dates >> for the 63rd IETF Meeting can be found at >> http://www.ietf.org/meetings/cutoff_dates_63.html. >> >> _______________________________________________ >> IETF-Announce mailing list >> IETF-Announce@ietf.org >> https://www1.ietf.org/mailman/listinfo/ietf-announce >> > From nemo-bounces@ietf.org Fri Jun 17 15:51:15 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DjMrz-0006fp-H6; Fri, 17 Jun 2005 15:51:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DjMry-0006fk-CS for nemo@megatron.ietf.org; Fri, 17 Jun 2005 15:51:14 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17507 for ; Fri, 17 Jun 2005 15:51:12 -0400 (EDT) Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DjNF7-0006TA-5y for nemo@ietf.org; Fri, 17 Jun 2005 16:15:10 -0400 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j5HJKPv25277; Fri, 17 Jun 2005 12:20:25 -0700 X-mProtect: <200506171920> Nokia Silicon Valley Messaging Protection Received: from mvdhcp141139.americas.nokia.com (172.18.141.139, claiming to be "[172.18.141.139]") by darkstar.iprg.nokia.com smtpdRyLVVr; Fri, 17 Jun 2005 12:20:18 PDT Message-ID: <42B3298F.3060606@iprg.nokia.com> Date: Fri, 17 Jun 2005 12:50:39 -0700 From: Vijay Devarapalli User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Romain KUNTZ Subject: Re: [nemo] Same MNP registered for several HoA References: <42B28951.7050905@sfc.wide.ad.jp> In-Reply-To: <42B28951.7050905@sfc.wide.ad.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Content-Transfer-Encoding: 7bit Cc: nemo X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-bounces@ietf.org Romain KUNTZ wrote: > Dear all, > > I am currently performing some multihoming tests with NEMO Basic Support. > The topology I am currently testing is (2,1,1): two MRs registered to the > same HA, registering the same prefix. > > I would like to know if there was already a consensus about the fact > that a HA can or cannot allow to bind the same MNP to 2 different HoA > (this is typically what happens in the scenario I mentioned). AFAIK > RFC3963 does not suggest anything about that, nor the drafts about > prefix delegation for NEMO BS. the design goal when working on RFC 3963 was that we should not prevent any mutli-homing scenario. thats why it is kind of silent on this. it should be okay to have the same prefix in two different binding cache entries. the only check that is performed is whether a particular MR is authorized for a particular prefix. if both MRs are allowed to use the particular MNP, then binding updates from both MRs will succeed. as Alex pointed out, you have to be careful when you create routes for the MNP. you have to pick one MR (or have both routes and let your forwarding code figure out which route to use). I agree this should be considered in prefix delegation. I am hoping this will be clarified when we do the multi-homing solution for NEMO. Vijay From nemo-bounces@ietf.org Wed Jun 22 14:02:48 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl9Ym-0005ZM-Dt; Wed, 22 Jun 2005 14:02:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl9Yk-0005Xm-34 for nemo@megatron.ietf.org; Wed, 22 Jun 2005 14:02:46 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07299 for ; Wed, 22 Jun 2005 14:02:43 -0400 (EDT) Received: from mail.sfc.wide.ad.jp ([203.178.142.146]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dl9gb-0000W4-SJ for nemo@ietf.org; Wed, 22 Jun 2005 14:10:55 -0400 Received: from [192.108.119.182] (dhcp2.ipv6.rennes.enst-bretagne.fr [192.108.119.182]) by mail.sfc.wide.ad.jp (Postfix) with ESMTP id D0A604C9FC for ; Thu, 23 Jun 2005 02:44:36 +0900 (JST) Message-ID: <42B9A3F8.90407@sfc.wide.ad.jp> Date: Wed, 22 Jun 2005 19:46:32 +0200 From: Romain KUNTZ Organization: Keio University User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: nemo Subject: Re: [nemo] Same MNP registered for several HoA References: <42B28951.7050905@sfc.wide.ad.jp> <42B3298F.3060606@iprg.nokia.com> In-Reply-To: <42B3298F.3060606@iprg.nokia.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Content-Transfer-Encoding: 7bit X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-bounces@ietf.org Hi Vijay and Alexandru, Thanks for your answers, Vijay Devarapalli wrote: > the design goal when working on RFC 3963 was that we should not > prevent any mutli-homing scenario. thats why it is kind of silent > on this. > > it should be okay to have the same prefix in two different binding > cache entries. the only check that is performed is whether a > particular MR is authorized for a particular prefix. if both MRs > are allowed to use the particular MNP, then binding updates from > both MRs will succeed. Ok that was my understanding. I think this behaviour is useful for fault recovery when you have a Mobile Network with 2 MR, each MR advertising and registering the same prefix. If one of the MR fails, then the HA will be able to choose the other MR once the entry in the BC for the first one is deleted and the tunnel endpoint updated. Regards, -- Romain KUNTZ kuntz@sfc.wide.ad.jp From nemo-bounces@ietf.org Mon Jun 27 09:34:49 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DmtlB-0003j4-6T; Mon, 27 Jun 2005 09:34:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DizLA-0000e2-SQ for nemo@megatron.ietf.org; Thu, 16 Jun 2005 14:43:48 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24041 for ; Thu, 16 Jun 2005 14:43:44 -0400 (EDT) Received: from hkueee2.eee.hku.hk ([147.8.180.60]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dizi7-0004BU-9T for nemo@ietf.org; Thu, 16 Jun 2005 15:07:32 -0400 Received: from se6000 (se6000.eee.hku.hk [147.8.180.36]) by hkueee2.eee.hku.hk (8.13.4/8.13.4) with ESMTP id j5GIh0V8026816; Fri, 17 Jun 2005 02:43:00 +0800 (HKT) Date: Fri, 17 Jun 2005 02:43:00 +0800 (HKT) From: Ka-Cheong Leung X-X-Sender: kcleung@se6000 To: nemo@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-HKUEEE-MailScanner-Information: www.eee.hku.hk/intranet/computer/faq/mailscanner.htm X-HKUEEE-MailScanner: Found to be clean X-HKUEEE-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.657, required 5, AWL 0.28, BAYES_00 -2.60, SUBJ_ALL_CAPS 0.67) Subject: [NEMO] [CFP] NASM 2005 X-Spam-Score: 0.6 (/) X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3 X-Mailman-Approved-At: Mon, 27 Jun 2005 09:34:47 -0400 X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kcleung@ieee.org List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-bounces@ietf.org (We apologize if you receive multiple copies of this CFP.) CALL FOR PAPERS The First International Workshop on Network Architecture and Service Models NASM 2005 November 21-23, 2005 Fudan University, Shanghai, China http://www.elec.qmul.ac.uk/wharf/NASM-2005.htm Technically Co-Sponsored by: British Computer Society (BCS) Institution of Electrical Engineers (IEE) Queen Mary / Fudan Joint Laboratory in Mobile Networks and Ubiquitous Computing SCOPE Network architecture and service model are two key topics of network research and applications. With the rapid development of optical and wireless communications, chips and software, network architectures are changing and new service models are needed. Many research and technical challenges are being addressed by researchers from both industries and academia. It is viewed that through international collaboration among several experts in different parts of the globe, greater research excellence and achievements can be made. OBJECTIVE The objective of this workshop is to discuss new approaches and technologies in the field of next generation networks (NGN), ad hoc mobile networks, wireless sensor networks, and P2P networks. TOPICS OF INTERESTS The main topics of interests include, but not limited to: * Network architectures and services * Optical and wireless networks * Routing and scheduling * Application model and QoS * Mobile network architecture * MAC and QoS MAC in MANET * Mobile addressing * Mobile routing * Mobile applications PAPER SUBMISSIONS - Format: Submissions should include an abstract of 100 words, 5-7 keywords, the e-mail address of the corresponding author, and must not exceed 8 pages (in 2-column format), including tables and figures, with PDF, Postscript, or MS Word format. - Submission: Please submit your paper directly to the workshop chair or co-chair. E-mail: xinw@fudan.edu.cn - Review: Contributions will be reviewed by at least three reviewers from both program committee and external reviewers for relevance and technical contents on basis of papers. - Publication: Selected accepted papers will be published as special issues of International Journal of Ad Hoc and Ubiquitous Computing (IJHAUC). IMPORTANT DATES Paper Submission Due: August 31, 2005 Acceptance Notification: October 15, 2005 Final Camera-Ready Paper: October 22, 2005 Author Registration: October 22, 2005 Workshop Date: November 22, 2005 ORGANIZERS AND COMMITTEE Honorary Chair Prof. Jiangxing Wu, NDSC, China General Chair Prof. CK Toh, Queen Mary University of London, UK Technical Program Chair Prof. Xiangyang Xue, Fudan University, China TPC Members Prof. Victor Li, University of Hong Kong, China Prof. Laurie Cuthbert, University of London, UK Prof. Hong Shen, Japan Advanced Institute of Science and Technology, Japan Prof. Yoshiaki Kakuda, Hiroshima University, Japan Prof. Tadanori Mizuno, Shizuoka University, Japan Prof. Shuigeng Zhou, Fudan University, China Prof. Ke Xu, Tsinghua University, China Prof. Hai Jin, Wuhan University, China Prof. Jiandong Li, Xidian University, China Prof. Zhengbin Li, Peking University, China Prof. Y.-H. Choi, Seoul National University, Korea Prof. H.-K. Kahng, Korea University, Korea Prof. D.-K. Kim, Kyungpook National University, Korea Dr. Jiang Du, Queensland University, Australia Prof. Lai Xu, Vrije University, Netherlands Prof. Jun Zhang, National Chiao Tung University, China Prof. Qing'an Zeng, Southeast University, China Prof. H-C. Chao, National Dong Hwa University, Taiwan, China Prof. J.-C. Chen, National Hsing Hwa University, Taiwan, China Prof. Y. S. Chen, National Chung Cheng University, Taiwan, China Dr. Russell Hsing, Telcordia Technologies Inc., USA Prof. Wei K. Tsai, University of California Irvine, USA Prof. Joe Hui, Arizona State University, USA Local Arrangements Chair Prof. Wang Xin, Fudan University, China Publicity Chair Dr. K.-C. Leung, University of Hong Kong, China From nemo-bounces@ietf.org Mon Jun 27 09:34:49 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DmtlB-0003jT-MX; Mon, 27 Jun 2005 09:34:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DkUqv-0000r8-Vz; Mon, 20 Jun 2005 18:34:50 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17506; Mon, 20 Jun 2005 18:34:47 -0400 (EDT) Received: from thing1.cs.uvic.ca ([142.104.100.110]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DkVEj-0007tR-H6; Mon, 20 Jun 2005 18:59:25 -0400 Received: from yang (yang [142.104.100.105]) by thing1.cs.UVic.CA (8.12.10/8.12.8) with ESMTP id j5KMXhcD005053; Mon, 20 Jun 2005 15:33:44 -0700 Date: Mon, 20 Jun 2005 15:33:43 -0700 (PDT) From: Kui Wu X-X-Sender: wkui@yang To: tccc@cs.columbia.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-CS-Spam-Score: 0.072 () BAYES_20,CS_SALES_14,CS_VGA_10 X-CS-Spam-Status: No X-Scanned-By: MIMEDefang 2.41 X-Spam-Score: 0.0 (/) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a X-Mailman-Approved-At: Mon, 27 Jun 2005 09:34:47 -0400 Cc: Subject: [nemo] The deadline for paper submission to WoNS 2005 is extended to June 30 X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-bounces@ietf.org Due to several requests, the deadline for the First IEEE LCN Workshop on Network Security (WoNS 2005) has been extended to June 30, 2005. Apologies if you receive multiple copies of this Call for Papers ============================ The First IEEE LCN Workshop on Network Security (WoNS 2005) Sydney, Australia, November 15-17, 2005. The First International Workshop on Network Security (WoNS), will be a one-day workshop, held in conjunction with the IEEE Conference on Local Computer Networks (LCN). The workshop will bring together networking researchers, engineers, and practitioners with participants from industry, academia, and government. The workshop will be a full-day event on Tuesday November 15th. (Please also visit http://www.ieeelcn.org) Topics of Interest: The proliferation of commercial activities over different networked systems has brought security concerns on an unprecedented scale. From traditional Internet-based applications to newly emerging ubiquitous services over 3G, Wireless LAN, and mobile ad hoc networks, there is an increasing demand of measures to guarantee the confidentiality, integrity, and availability of system services. The main purpose of this workshop is to promote further research interests and activities on network security. It is also aimed at increasing the synergy between academic and industrial researchers working in this area. We are interested in experimental, systems-related, and work-in-progress papers in all aspects of network security. The topics of interest include (but are not limited to): * Novel and emerging secure architecture * Study of attack strategies, attack modeling * Key management * Intrusion detection techniques * Intrusion response, alarm management, and correlation analysis * Study of tradeoffs between security and system performance * Intrusion tolerance systems * Secure protocols * Security for emerging network technologies (e.g., ad hoc networks, sensor networks, WiMAX, WPAN, etc.) Papers should describe original, previously unpublished work, not currently under review by another conference, workshop, or journal. Paper length should not exceed 20 pages. Papers should be submitted electronically in PDF format via EDAS. Accepted papers will appear in the IEEE LCN conference proceedings. Important dates Paper submission deadline: June 30, 2005 (5pm EST) Notification of acceptance: July 28, 2005 Camera-ready paper due: August 25, 2005 Author registration deadline: August 19, 2005 Workshop: November 15, 2005 From nemo-bounces@ietf.org Mon Jun 27 18:25:23 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dn22d-00060u-Fo; Mon, 27 Jun 2005 18:25:23 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dn22c-0005zJ-IY for nemo@megatron.ietf.org; Mon, 27 Jun 2005 18:25:22 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03665 for ; Mon, 27 Jun 2005 18:25:19 -0400 (EDT) Received: from node-402449f2.sfo.onnet.us.uu.net ([64.36.73.242] helo=deimos.multihop.net) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dn2Rk-0002TO-NW for nemo@ietf.org; Mon, 27 Jun 2005 18:51:27 -0400 Received: from localhost (unknown [127.0.0.1]) by deimos.multihop.net (Postfix) with ESMTP id 423F963F9 for ; Mon, 27 Jun 2005 15:24:47 -0700 (PDT) Received: from deimos.multihop.net ([127.0.0.1]) by localhost (deimos.multihop.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 43400-09 for ; Mon, 27 Jun 2005 15:24:46 -0700 (PDT) Received: by deimos.multihop.net (Postfix, from userid 1013) id E972E63F7; Mon, 27 Jun 2005 15:24:46 -0700 (PDT) Received: from [192.103.16.119] (unknown [192.103.16.119]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by deimos.multihop.net (Postfix) with ESMTP id 2E80463F2 for ; Mon, 27 Jun 2005 15:24:45 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v622) In-Reply-To: <42B9A3F8.90407@sfc.wide.ad.jp> References: <42B28951.7050905@sfc.wide.ad.jp> <42B3298F.3060606@iprg.nokia.com> <42B9A3F8.90407@sfc.wide.ad.jp> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <9582a13be650f6f4301d201e58e3289e@kniveton.com> Content-Transfer-Encoding: 7bit From: "T.J.Kniveton" Subject: Re: [nemo] Same MNP registered for several HoA Date: Mon, 27 Jun 2005 15:24:57 -0700 To: nemo WG X-Mailer: Apple Mail (2.622) X-Virus-Scanned: by amavisd-new at deimos.multihop.net X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Content-Transfer-Encoding: 7bit X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-bounces@ietf.org As you guys noted, the draft is pretty silent on the question of using the same MNP for more than one MR. It's possible to implement things that way, but you'd better "know what you're doing" if you want to try it, since it could cause lots of problems. Until now, it's not a question that came up very often, though we did consider it also for prefix delegation. TJ From nemo-bounces@ietf.org Tue Jun 28 03:39:47 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DnAh9-0007d4-0K; Tue, 28 Jun 2005 03:39:47 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DnAh6-0007cz-SA for nemo@megatron.ietf.org; Tue, 28 Jun 2005 03:39:45 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09935 for ; Tue, 28 Jun 2005 03:39:43 -0400 (EDT) Received: from web33515.mail.mud.yahoo.com ([68.142.206.164]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DnB6Q-0006pQ-6i for nemo@ietf.org; Tue, 28 Jun 2005 04:05:54 -0400 Received: (qmail 15062 invoked by uid 60001); 28 Jun 2005 07:39:35 -0000 Message-ID: <20050628073935.15060.qmail@web33515.mail.mud.yahoo.com> Received: from [68.18.206.88] by web33515.mail.mud.yahoo.com via HTTP; Tue, 28 Jun 2005 00:39:35 PDT X-RocketYMMF: yangxiao_acm Date: Tue, 28 Jun 2005 00:39:35 -0700 (PDT) From: Yang Xiao To: nemo@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.1 (/) X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d Content-Transfer-Encoding: 8bit Subject: [nemo] Journal Special Issue: Wireless Network Security X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yangxiao@ieee.org List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-bounces@ietf.org (Our apologies if you receive multiple copies) EURASIP Journal on Wireless Communications and Networking, special issue on Wireless Network Security http://www.hindawi.com/journals/wcn/si/wns.html Guest Editors: Yang Xiao, Computer Science Department, The University of Memphis, Memphis, TN 38152, USA Yi-Bing Lin, Department of Computer Science and Information Engineering, National Chiao Tung University, Taiwan Ding-Zhu Du, Department of Computer Science & Engineering, University of Minnesota, Minneapolis, MN 55455, USA Recent advances in wireless network technologies have rapidly developed in recent years, as evidenced by wireless location area networks (WLANs), wireless personal area networks (WPANs), wireless metropolitan area networks (WMANs), and wireless wide area networks (WWANs), that is, cellular networks. A major impediment to their deployment, however, is wireless network security. For example, the lack of data confidentiality in wired equivalent privacy (WEP) protocol has been proven, and newly adopted standards such as IEEE 802.11i robust secruity network (RSN) and IEEE 802.15.3a ultra-wideband (UWB) are not fully tested and, as such, may expose unforeseen security vulnerabilities. The effort to improve wireless network security is linked with many technical challenges including compatibility with legacy wireless networks, complexity in implementation, and cost/performance trade-offs. The need to address wireless network security and to provide timely, solid technical contributions establishes the motivation behind this special issue. This special issue will focus on novel and functional ways to improve wireless network security. Papers that do not focus on wireless network security will not be reviewed. Specific areas of interest in WLANs, WPANs, WMANs, and WWANs include, but are not limited to: Attacks, security mechanisms, and security services Authentication Access control Data confidentiality Data integrity Nonrepudiation Encryption and decryption Key management Fraudulent usage Wireless network security performance evaluation Wireless link layer security Tradeoff analysis between performance and security Authentication and authorization for mobile service network Wireless security standards (IEEE 802.11, IEEE 802.15, IEEE 802.16, 3GPP, and 3GPP2) Authors should follow the EURASIP JWCN manuscript format described at the journal site http://wcn.hindawi.com/. Prospective authors should submit an electronic copy of their complete manuscript through the EURASIP JWCN's manuscript tracking system at http://www.mstracking.com/wcn/, according to the following timetable. Manuscript Due October 1, 2005 Acceptance Notification February 1, 2006 Final Manuscript Due May 1, 2006 Publication Date 3rd Quarter, 2006 Refereeing: If you are willing to referee paper(s) for this special issue, please visit the following URL:http://www.mstracking.com/wcn/si/si.php?si=WNS. All referees shall receive a complimentary copy of the special issue upon publication. From nemo-bounces@ietf.org Tue Jun 28 15:57:15 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DnMCp-0002Zw-BA; Tue, 28 Jun 2005 15:57:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DnMCU-0002P3-NK; Tue, 28 Jun 2005 15:56:54 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13362; Tue, 28 Jun 2005 15:56:50 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DnMVL-0004J6-Ah; Tue, 28 Jun 2005 16:16:23 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1DnM5q-00088K-OD; Tue, 28 Jun 2005 15: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: Tue, 28 Jun 2005 15:50:02 -0400 X-Spam-Score: 0.4 (/) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Cc: nemo@ietf.org Subject: [nemo] I-D ACTION:draft-ietf-nemo-home-network-models-04.txt X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-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 Network Mobility Working Group of the IETF. Title : NEMO Home Network models Author(s) : P. Thubert, et al. Filename : draft-ietf-nemo-home-network-models-04.txt Pages : 24 Date : 2005-6-28 This paper documents some usage patterns and the associated issues when deploying a Home Network for NEMO-enabled Mobile Routers, conforming the NEMO Basic Support draft [8]. The aim here is specifically to provide some examples of organization of the Home Network, as they were discussed in NEMO related mailing lists. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-nemo-home-network-models-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-nemo-home-network-models-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-nemo-home-network-models-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: <2005-6-28150842.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-nemo-home-network-models-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-nemo-home-network-models-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-6-28150842.I-D@ietf.org> --OtherAccess-- --NextPart-- From nemo-bounces@ietf.org Tue Jun 28 18:35:59 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DnOgR-0007Md-No; Tue, 28 Jun 2005 18:35:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DnOgQ-0007MU-C5 for nemo@megatron.ietf.org; Tue, 28 Jun 2005 18:35:58 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05436 for ; Tue, 28 Jun 2005 18:35:55 -0400 (EDT) Received: from mail.sfc.wide.ad.jp ([203.178.142.146]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DnP5q-0005XA-9N for nemo@ietf.org; Tue, 28 Jun 2005 19:02:15 -0400 Received: from iseran.local (ARennes-351-1-61-201.w82-126.abo.wanadoo.fr [82.126.97.201]) by mail.sfc.wide.ad.jp (Postfix) with ESMTP id EC3864C9AF; Wed, 29 Jun 2005 07:34:24 +0900 (JST) Date: Tue, 28 Jun 2005 21:54:27 +0900 From: Thierry Ernst To: ml-nemo Message-Id: <20050628215427.5f01f626.ernst@sfc.wide.ad.jp> Organization: Keio University X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; powerpc-apple-darwin7.8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: 0.7 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Content-Transfer-Encoding: 7bit Cc: tj Subject: [nemo] NEMO WG 63rd Agenda X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-bounces@ietf.org Dear all, We have requested a 2h slot for NEMO WG at Paris meeting. The most important topics to be discussed are the following WG items: - WG status and milestones - draft-ietf-nemo-multihoming-issue update and next steps - Prefix Delegation (draft-kniveton and draft-droms to be issued as draft-ietf-...-00) - NEMO routing optimization problem statement and analysis (2 draft-ietf-..-00 to be issued) - regarding IPv4 Traversal, I don't know if the output of the design team will be discussed in the NEMO or the MIP6 WG. If there are other topics that you want to discussed (e.g. MIB), please send a request to TJ and myself indicating: - title - name of speaker - associated draft if any - purpose of the discussion - length of slot Slots will be allocated based on availabilities and priority will be given to important WG items. As usual, we expect that topics discussed at the meeting are discussed on the ML beforehand. Thierry. From nemo-bounces@ietf.org Wed Jun 29 07:39:42 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dnaus-0006Gi-L2; Wed, 29 Jun 2005 07:39:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dnaur-0006Fj-UF for nemo@megatron.ietf.org; Wed, 29 Jun 2005 07:39:41 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08046 for ; Wed, 29 Jun 2005 07:39:41 -0400 (EDT) Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DnbKO-0000R1-UL for nemo@ietf.org; Wed, 29 Jun 2005 08:06:06 -0400 Received: from ams-core-1.cisco.com (144.254.224.150) by ams-iport-1.cisco.com with ESMTP; 29 Jun 2005 13:39:29 +0200 Received: from xbh-ams-331.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j5TBdQDg004045 for ; Wed, 29 Jun 2005 13:39:27 +0200 (MEST) Received: from xmb-ams-337.cisco.com ([144.254.231.82]) by xbh-ams-331.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 29 Jun 2005 13:39:25 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 29 Jun 2005 13:39:22 +0200 Message-ID: <7892795E1A87F04CADFCCF41FADD00FC010B1821@xmb-ams-337.emea.cisco.com> Thread-Topic: Status of draft-ietf-nemo-home-network-models Thread-Index: AcV5CKajOH2ThfPlTNuSttmvahVsXwDlkOWQ From: "Pascal Thubert \(pthubert\)" To: X-OriginalArrivalTime: 29 Jun 2005 11:39:26.0182 (UTC) FILETIME=[33DEF060:01C57C9F] X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Content-Transfer-Encoding: quoted-printable Subject: [nemo] RE: Status of draft-ietf-nemo-home-network-models X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-bounces@ietf.org http://www.ietf.org/internet-drafts/draft-ietf-nemo-home-network-models- 04.txt=20 FYI: I submitted an update of the home models to pass the new id-nits: http://www.ietf.org/internet-drafts/draft-ietf-nemo-home-network-models- 04.txt=20 There is no change in the core text. Pascal From nemo-bounces@ietf.org Thu Jun 30 16:59:25 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Do684-0005iq-Uc; Thu, 30 Jun 2005 16:59:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Do67y-0005il-I3 for nemo@megatron.ietf.org; Thu, 30 Jun 2005 16:59:18 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23170 for ; Thu, 30 Jun 2005 16:59:16 -0400 (EDT) Received: from web33509.mail.mud.yahoo.com ([68.142.206.158]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Do6Xn-0003jy-2V for nemo@ietf.org; Thu, 30 Jun 2005 17:26:00 -0400 Received: (qmail 76032 invoked by uid 60001); 30 Jun 2005 20:59:07 -0000 Message-ID: <20050630205907.76030.qmail@web33509.mail.mud.yahoo.com> Received: from [141.225.9.145] by web33509.mail.mud.yahoo.com via HTTP; Thu, 30 Jun 2005 13:59:07 PDT X-RocketYMMF: yangxiao_acm Date: Thu, 30 Jun 2005 13:59:07 -0700 (PDT) From: Yang Xiao To: nemo@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Content-Transfer-Encoding: 8bit Cc: yangxiao@ieee.org Subject: [nemo] Journal Special issue on Security Issues in Sensor Networks X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yangxiao@ieee.org List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-bounces@ietf.org (Our apologies if you receive multiple copies) International Journal of Security and Networks (IJSN), Special Issue on Security Issues in Sensor Networks http://www.cs.memphis.edu/~yxiao/IJSN_Snesor_Security.html -----------------------------------------------------------------------Guest Editors Yang Xiao, The University of Memphis, USA E-mail: yangxiao@ieee.org Xiaohua Jia, City University of Hong Kong, Hong Kong E-mail: csjia@cityu.edu.hk Bo Sun, Lamar University, USA E-mail: bsun@cs.lamar.edu Xiaojiang Du, North Dakota State University, USA E-mail: bsun@cs.lamar.edu -----------------------------------------------------------------------Security in Sensor networks differ from those in other traditional networks with many aspects such as limited memory space, limited computation capability, etc. Therefore, sensor network security has some unique features which do not exist in other networks. The need to address security issues, and provide timely, solid technical contributions of security solutions in sensor networks establishes the motivation behind this special issue. This special issue is dedicated to sensor network security. A paper should have security in sensor networks as the focus. Specific areas of interest include, but not limit to: . Key Managements in sensor networks . Secure Routing in secure networks . Light weight Encryption and authentication in Sensor networks . Attacks and solutions in Sensor networks . Other areas which are related to both security and sensor networks. The manuscripts should be submitted as an e-mail attachment in PDF format to Prof. Bo Sun at bsun@cs.lamar.edu. If the file is larger than 1MB, the authors are encouraged to use WINZIP. Furthermore, each author is required to help the review process of the special issue. ----------------------------------------------------------------------- Schedule: Submission deadline: Oct. 15, 2005 Notification: Jan. 15, 2006 Final Paper Submission: Feb. 1, 2005 Publication of special issue: Middle 2006 ----------------------------------------------------------------------- From nemo-bounces@ietf.org Thu Jun 30 17:01:01 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Do69d-0005vU-1t; Thu, 30 Jun 2005 17:01:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Do69a-0005uU-60 for nemo@megatron.ietf.org; Thu, 30 Jun 2005 17:00:58 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23293 for ; Thu, 30 Jun 2005 17:00:55 -0400 (EDT) Received: from web33509.mail.mud.yahoo.com ([68.142.206.158]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Do6ZP-0003lx-OS for nemo@ietf.org; Thu, 30 Jun 2005 17:27:40 -0400 Received: (qmail 76587 invoked by uid 60001); 30 Jun 2005 21:00:49 -0000 Message-ID: <20050630210049.76585.qmail@web33509.mail.mud.yahoo.com> Received: from [141.225.9.145] by web33509.mail.mud.yahoo.com via HTTP; Thu, 30 Jun 2005 14:00:48 PDT X-RocketYMMF: yangxiao_acm Date: Thu, 30 Jun 2005 14:00:48 -0700 (PDT) From: Yang Xiao To: nemo@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Content-Transfer-Encoding: 8bit Cc: yangxiao@ieee.org Subject: [nemo] Journal Special issue on Security Issues in Sensor Networks X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yangxiao@ieee.org List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-bounces@ietf.org (Our apologies if you receive multiple copies) International Journal of Security and Networks (IJSN), Special Issue on Security Issues in Sensor Networks http://www.cs.memphis.edu/~yxiao/IJSN_Snesor_Security.html -----------------------------------------------------------------------Guest Editors Yang Xiao, The University of Memphis, USA E-mail: yangxiao@ieee.org Xiaohua Jia, City University of Hong Kong, Hong Kong E-mail: csjia@cityu.edu.hk Bo Sun, Lamar University, USA E-mail: bsun@cs.lamar.edu Xiaojiang Du, North Dakota State University, USA E-mail: bsun@cs.lamar.edu -----------------------------------------------------------------------Security in Sensor networks differ from those in other traditional networks with many aspects such as limited memory space, limited computation capability, etc. Therefore, sensor network security has some unique features which do not exist in other networks. The need to address security issues, and provide timely, solid technical contributions of security solutions in sensor networks establishes the motivation behind this special issue. This special issue is dedicated to sensor network security. A paper should have security in sensor networks as the focus. Specific areas of interest include, but not limit to: . Key Managements in sensor networks . Secure Routing in secure networks . Light weight Encryption and authentication in Sensor networks . Attacks and solutions in Sensor networks . Other areas which are related to both security and sensor networks. The manuscripts should be submitted as an e-mail attachment in PDF format to Prof. Bo Sun at bsun@cs.lamar.edu. If the file is larger than 1MB, the authors are encouraged to use WINZIP. Furthermore, each author is required to help the review process of the special issue. ----------------------------------------------------------------------- Schedule: Submission deadline: Oct. 15, 2005 Notification: Jan. 15, 2006 Final Paper Submission: Feb. 1, 2005 Publication of special issue: Middle 2006 ----------------------------------------------------------------------- From nemo-bounces@ietf.org Thu Jun 30 17:07:58 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Do6GM-0007gO-53; Thu, 30 Jun 2005 17:07:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Do6GL-0007g4-Es for nemo@megatron.ietf.org; Thu, 30 Jun 2005 17:07:57 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23990 for ; Thu, 30 Jun 2005 17:07:55 -0400 (EDT) Received: from web33515.mail.mud.yahoo.com ([68.142.206.164]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Do6g8-0003zr-5q for nemo@ietf.org; Thu, 30 Jun 2005 17:34:39 -0400 Received: (qmail 62681 invoked by uid 60001); 30 Jun 2005 21:07:45 -0000 Message-ID: <20050630210745.62679.qmail@web33515.mail.mud.yahoo.com> Received: from [141.225.9.145] by web33515.mail.mud.yahoo.com via HTTP; Thu, 30 Jun 2005 14:07:45 PDT X-RocketYMMF: yangxiao_acm Date: Thu, 30 Jun 2005 14:07:45 -0700 (PDT) From: Yang Xiao To: nemo@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Content-Transfer-Encoding: 8bit Cc: yangxiao@ieee.org Subject: [nemo] Journal Special issue on Security Issues in Sensor Networks X-BeenThere: nemo@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yangxiao@ieee.org List-Id: NEMO Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: nemo-bounces@ietf.org Errors-To: nemo-bounces@ietf.org (Our apologies if you receive multiple copies) International Journal of Security and Networks (IJSN), Special Issue on Security Issues in Sensor Networks http://www.cs.memphis.edu/~yxiao/IJSN_Snesor_Security.html -----------------------------------------------------------------------Guest Editors Yang Xiao, The University of Memphis, USA E-mail: yangxiao@ieee.org Xiaohua Jia, City University of Hong Kong, Hong Kong E-mail: csjia@cityu.edu.hk Bo Sun, Lamar University, USA E-mail: bsun@cs.lamar.edu Xiaojiang Du, North Dakota State University, USA E-mail: bsun@cs.lamar.edu -----------------------------------------------------------------------Security in Sensor networks differ from those in other traditional networks with many aspects such as limited memory space, limited computation capability, etc. Therefore, sensor network security has some unique features which do not exist in other networks. The need to address security issues, and provide timely, solid technical contributions of security solutions in sensor networks establishes the motivation behind this special issue. This special issue is dedicated to sensor network security. A paper should have security in sensor networks as the focus. Specific areas of interest include, but not limit to: . Key Managements in sensor networks . Secure Routing in secure networks . Light weight Encryption and authentication in Sensor networks . Attacks and solutions in Sensor networks . Other areas which are related to both security and sensor networks. The manuscripts should be submitted as an e-mail attachment in PDF format to Prof. Bo Sun at bsun@cs.lamar.edu. If the file is larger than 1MB, the authors are encouraged to use WINZIP. Furthermore, each author is required to help the review process of the special issue. ----------------------------------------------------------------------- Schedule: Submission deadline: Oct. 15, 2005 Notification: Jan. 15, 2006 Final Paper Submission: Feb. 1, 2005 Publication of special issue: Middle 2006 -----------------------------------------------------------------------