From jeedward@yahoo.com Sat May 2 09:28:46 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 38B5D3A692F for ; Sat, 2 May 2009 09:28:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.633 X-Spam-Level: X-Spam-Status: No, score=-0.633 tagged_above=-999 required=5 tests=[AWL=-1.290, BAYES_20=-0.74, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EOSFdcu2JbDi for ; Sat, 2 May 2009 09:28:45 -0700 (PDT) Received: from n67.bullet.mail.sp1.yahoo.com (n67.bullet.mail.sp1.yahoo.com [98.136.44.47]) by core3.amsl.com (Postfix) with SMTP id 3B87828C0DC for ; Sat, 2 May 2009 09:28:45 -0700 (PDT) Received: from [216.252.122.216] by n67.bullet.mail.sp1.yahoo.com with NNFMP; 02 May 2009 16:30:09 -0000 Received: from [69.147.65.168] by t1.bullet.sp1.yahoo.com with NNFMP; 02 May 2009 16:30:09 -0000 Received: from [127.0.0.1] by omp503.mail.sp1.yahoo.com with NNFMP; 02 May 2009 16:30:09 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 646988.12639.bm@omp503.mail.sp1.yahoo.com Received: (qmail 23199 invoked by uid 60001); 2 May 2009 16:30:08 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1241281808; bh=BuzvDkzlPg0joXRYfl1LIMfeF/AhywlZC1Sioo3o74g=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=zvZLesTHM2v8d4AmJyHZumGWr+dHZXP820nfPv0cjmf5wz21rjBAOBB0kfyfqwt8uHgO84puz9LvoFb7d4/+sKOt6WmdOKE6AKKwElivfBR7mJ5JnLqnlwCw4vZj6Yrs/kYgS/CHPsJVqwWpOw64BLbLLL3JGc+DRpmfxeZH8JU= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=lPuyQy54Fb4zMbW7QwMXBngQ3W1vdq7ozGleVZAvCJroGcyX1VeggPzLGthcEhLR4yc6Hfeh24T88tWpdtA9W24kzTC22OjKgmqXSqynPUxXKxtVrnrMDRhEWnatNVyiT9aJLufv4WNiFbTkHc82Bc8WJ5UvjZgQZRDWzA4ciuU=; Message-ID: <422410.10960.qm@web45912.mail.sp1.yahoo.com> X-YMail-OSG: pZEBf04VM1lhjxfigwb0QeP_qMEFUyUAll3Rzh1p7kqNLZmpGW4m8jHR8uz5h3t2b8wJxxNcyKkRrORmEiJd0lA3ViGk1WJ8Q8CmRDGcxbiKW3Ny0RoNZp2pQHe23zKXRjy75mR1UqPG7P2VFsjjxd4Y58DLyI0DJRjaa6Gx6.3.fCuSh5pFubq9c.VRadH12OfJTCrfxwsYy4MSckw25P4HrqDUPHn_AedehuyacIFLs3F154Ns2fLyrmg8kWST69Unkct2fmbwx1imCkqAsP0n6L1x3Jmks9RZHf3_tdUTws0YShDRnkzXYbJ3eADJWA-- Received: from [67.233.191.18] by web45912.mail.sp1.yahoo.com via HTTP; Sat, 02 May 2009 09:30:08 PDT X-Mailer: YahooMailClassic/5.2.20 YahooMailWebService/0.7.289.1 Date: Sat, 2 May 2009 09:30:08 -0700 (PDT) From: John Edward To: jeedward@yahoo.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1995875282-1241281808=:10960" X-Mailman-Approved-At: Mon, 04 May 2009 14:41:26 -0700 Subject: [Mip4] Extended draft paper submission: HPCNCS-09 call for papers X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 May 2009 16:28:46 -0000 --0-1995875282-1241281808=:10960 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Extended draft paper submission: HPCNCS-09 call for papers =A0 This Extended Call for Papers for the 2009 International Conference on High= Performance Computing, Networking and Communication Systems (HPCNCS-09) (w= ebsite: http://www.PromoteResearch.org ) is for those who didn't get a chan= ce to submit the papers for the earlier call for papers. The papers receive= d and accepted in response to this extended call for papers will be include= d in the final version of the respective conference proceedings. These proc= eedings will be either ready by the time of the conference (i.e., they will= be available during the conference) or soon after the conference (before t= he end of August 2009), based how fast the proceedings can be prepared.=20 Note: If you have already submitted a paper (whether accepted or rejected o= r currently under review) for MULTICONF-09, please DO NOT submit that paper= again to this extended call for papers.=20 IMPORTANT DATES:=20 Draft paper submission date: May 11, 2009=20 Acceptance/rejection decision: May 21, 2009 Camera ready paper and copyright and pre-registration due: May 28, 2009 Conference dates: July 13-16, 2009 =A0 =A0 HPCNCS-09 will be held during July 13-16 2009 in Orlando, FL, USA. We invit= e draft paper submissions. The conference will take place at the same time = and venue where several other international conferences are taking place. T= he other conferences include: =B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Artificial Intellig= ence and Pattern Recognition (AIPR-09)=20 =B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Automation, Robotic= s and Control Systems (ARCS-09) =B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Bioinformatics, Com= putational Biology, Genomics and Chemoinformatics (BCBGC-09)=20 =B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Enterprise Informat= ion Systems and Web Technologies (EISWT-09) =B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Information Securit= y and Privacy (ISP-09) =B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Recent Advances in = Information Technology and Applications (RAITA-09) =B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Software Engineerin= g Theory and Practice (SETP-09)=20 =B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Theory and Applicat= ions of Computational Science (TACS-09) =B7=A0=A0=A0=A0=A0=A0=A0=A0 International Conference on Theoretical and Mat= hematical Foundations of Computer Science (TMFCS-09) =A0 The website http://www.PromoteResearch.org contains more details. =A0 Sincerely John Edward Publicity committee =A0 =A0 =A0=0A=0A=0A --0-1995875282-1241281808=:10960 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable

Extended draft paper submission: HPCNC= S-09 call for papers

 

This Extended Call for Papers for the 2009 International Conference on High Performance Computing, Networking an= d Communication Systems (HPCNCS-09) (website: <= /SPAN>http://www.PromoteResearch.org= ) is for those who didn't get a chance to sub= mit the papers for the earlier call for papers. The papers received and acc= epted in response to this extended call for papers will be included in the final version of the resp= ective conference proceedings. These proceedings will be either ready by th= e time of the conference (i.e., they will be available during the conferenc= e) or soon after the conference (before the end of August 2009), based how = fast the proceedings can be prepared.

Note: If you have already submitted = a paper (whether accepted or rejected or currently under review) for MULTIC= ONF-09, please DO NOT submit that paper again to this extended call for pap= ers.


IMPORTANT DATES:

Draft paper submission date: May 11, 2009
Acceptance/re= jection decision: May 21, 2009
Camera ready paper and copyright and pre-= registration due: May 28, 2009
Conference dates: July 13-16, 2009=

 

 

HPCNCS-09 will be held during = July 13-16 2009 in Orlando, FL, USA. We invite draft paper submissions. The= conference will take place at the same time and venue where several other = international conferences are taking place. The other conferences include:<= SPAN style=3D"COLOR: black"><= /DIV>

=B7         <= /FONT>

=B7         International Conference on Automation, Robotics and Control Systems (ARC= S-09)

=B7         International Conference on Bioinformatics, Computational Biology, Genomi= cs and Chemoinformatics (BCBGC-09) <= /SPAN>

=B7         International Conference on Enterprise Information Systems and Web Techno= logies (EISWT-09)

=B7         International Conference on Information Security and Privacy (ISP-09)

=B7         International Conference on Recent Advances in Information Technology and= Applications (RAITA-09)

=B7         International Conference on Software Engineering Theory and Practice (SET= P-09)

=B7         International Conference on Theory and Applications of Computational Scie= nce (TACS-09)

=B7          

The website h= ttp://www.PromoteResearch.org contains more details.

 

Sincerely

John Edward

Publicity committee

 

 

 


=0A=0A= =0A=0A --0-1995875282-1241281808=:10960-- From pete.mccann@motorola.com Tue May 5 08:46:46 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E4433A6CE9 for ; Tue, 5 May 2009 08:46:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WpOxAukJ2Bs8 for ; Tue, 5 May 2009 08:46:45 -0700 (PDT) Received: from mail128.messagelabs.com (mail128.messagelabs.com [216.82.250.131]) by core3.amsl.com (Postfix) with ESMTP id 6BF6A3A70F1 for ; Tue, 5 May 2009 08:46:42 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-14.tower-128.messagelabs.com!1241538483!24005100!1 X-StarScan-Version: 6.0.0; banners=-,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 7639 invoked from network); 5 May 2009 15:48:04 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-14.tower-128.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 May 2009 15:48:04 -0000 Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133]) by motgate8.mot.com (8.14.3/8.14.3) with ESMTP id n45Fm3R1008613 for ; Tue, 5 May 2009 08:48:03 -0700 (MST) Received: from il06vts01.mot.com (il06vts01.mot.com [129.188.137.141]) by il06exr03.mot.com (8.13.1/Vontu) with SMTP id n45Fm3D0024438 for ; Tue, 5 May 2009 10:48:03 -0500 (CDT) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id n45Fm2hP024432 for ; Tue, 5 May 2009 10:48:03 -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, 5 May 2009 11:47:37 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Recharter: Multiple Tunnel Support Thread-Index: AcnNmNDbMcuRI+dXQmaJ8g/mqcFpSg== From: "McCann Peter-A001034" To: X-CFilter-Loop: Reflected Cc: Henrik Levkowetz Subject: [Mip4] Recharter: Multiple Tunnel Support X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 15:46:46 -0000 Hi, all, During our meeting at IETF74, we discussed whether to take on the multiple tunnel support and flow movement, as described in these two drafts: draft-gundavelli-mip4-multiple-tunnel-support-00.txt draft-tsirtsis-mip4-flowmove-01.txt The sense of the room seemed to be that we should combine these two drafts and take the result on as a new work item. This message is a request to confirm/reject this approach. Please respond to this e-mail with an indication of whether you agree or disagree, and state your reasons why. -Pete =20 From pete.mccann@motorola.com Tue May 5 08:46:46 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE9093A6CE9 for ; Tue, 5 May 2009 08:46:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sFd9kjYBbmgT for ; Tue, 5 May 2009 08:46:46 -0700 (PDT) Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by core3.amsl.com (Postfix) with ESMTP id E22CF3A7144 for ; Tue, 5 May 2009 08:46:42 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-8.tower-119.messagelabs.com!1241538484!34220072!1 X-StarScan-Version: 6.0.0; banners=-,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 19591 invoked from network); 5 May 2009 15:48:04 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-8.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 May 2009 15:48:04 -0000 Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133]) by motgate8.mot.com (8.14.3/8.14.3) with ESMTP id n45Fm4ZF008620 for ; Tue, 5 May 2009 08:48:04 -0700 (MST) Received: from il06vts03.mot.com (il06vts03.mot.com [129.188.137.143]) by il06exr03.mot.com (8.13.1/Vontu) with SMTP id n45Fm3rX024456 for ; Tue, 5 May 2009 10:48:03 -0500 (CDT) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id n45Fm2hR024432 for ; Tue, 5 May 2009 10:48:03 -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, 5 May 2009 11:47:52 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Recharter: BTN Fast Handoff Thread-Index: AcnNmNmbsIgk59D8Sqiufm9p2jANMA== From: "McCann Peter-A001034" To: X-CFilter-Loop: Reflected Cc: Henrik Levkowetz Subject: [Mip4] Recharter: BTN Fast Handoff X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 15:46:47 -0000 Hi, all, During our meeting at IETF74, we discussed whether to take on the Better Than Nothing fast handoff work, as described in=20 this draft: draft-doswald-robert-mip4-btn-fmipv4-00.txt The sense of the room seemed to be that there was not enough interest to take this on as a new work item. This message is a request to confirm/reject this approach. Please respond to this e-mail with an indication of whether you agree or disagree, and state your reasons why. -Pete =20 From pete.mccann@motorola.com Tue May 5 08:47:12 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B82B28C244 for ; Tue, 5 May 2009 08:47:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.475 X-Spam-Level: X-Spam-Status: No, score=-6.475 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MPFgGcr5AFkt for ; Tue, 5 May 2009 08:47:11 -0700 (PDT) Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by core3.amsl.com (Postfix) with ESMTP id BE6AC3A6D9F for ; Tue, 5 May 2009 08:47:08 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-7.tower-119.messagelabs.com!1241538514!29803164!1 X-StarScan-Version: 6.0.0; banners=-,-,- X-Originating-IP: [136.182.1.12] Received: (qmail 18406 invoked from network); 5 May 2009 15:48:34 -0000 Received: from motgate2.mot.com (HELO motgate2.mot.com) (136.182.1.12) by server-7.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 May 2009 15:48:34 -0000 Received: from il27exr03.cig.mot.com (il27exr03.mot.com [10.17.196.72]) by motgate2.mot.com (8.14.3/8.14.3) with ESMTP id n45FmYd2000460 for ; Tue, 5 May 2009 08:48:34 -0700 (MST) Received: from il27vts03 (il27vts03.cig.mot.com [10.17.196.87]) by il27exr03.cig.mot.com (8.13.1/Vontu) with SMTP id n45FmXQp025146 for ; Tue, 5 May 2009 10:48:33 -0500 (CDT) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by il27exr03.cig.mot.com (8.13.1/8.13.0) with ESMTP id n45FmWho025098 for ; Tue, 5 May 2009 10:48:32 -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, 5 May 2009 11:48:06 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Recharter: Home Agent Assisted Route Optimization Thread-Index: AcnNmOHjAFND+9NZRRGgm1Etff6wEA== From: "McCann Peter-A001034" To: X-CFilter-Loop: Reflected Cc: Henrik Levkowetz Subject: [Mip4] Recharter: Home Agent Assisted Route Optimization X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 15:47:12 -0000 Hi, all, During our meeting at IETF74, we discussed whether to take on Home Agent Assisted Route Optimization, as described in this draft: draft-makela-mip4-nemo-haaro-03.txt The sense of the room was that we needed more discussion to understand the scope and applicability of this draft. Please, if you support this work item, respond to this message with a summary of why you think it is important for the mip4 working group to take it on at this time. -Pete From pete.mccann@motorola.com Tue May 5 08:47:12 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 46A8A3A6D9F for ; Tue, 5 May 2009 08:47:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.489 X-Spam-Level: X-Spam-Status: No, score=-6.489 tagged_above=-999 required=5 tests=[AWL=0.111, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id apJZ8fSYB6EU for ; Tue, 5 May 2009 08:47:11 -0700 (PDT) Received: from mail128.messagelabs.com (mail128.messagelabs.com [216.82.250.131]) by core3.amsl.com (Postfix) with ESMTP id DD33128C241 for ; Tue, 5 May 2009 08:47:09 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-8.tower-128.messagelabs.com!1241538515!7576090!1 X-StarScan-Version: 6.0.0; banners=-,-,- X-Originating-IP: [136.182.1.14] Received: (qmail 4348 invoked from network); 5 May 2009 15:48:36 -0000 Received: from motgate4.mot.com (HELO motgate4.mot.com) (136.182.1.14) by server-8.tower-128.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 May 2009 15:48:36 -0000 Received: from il27exr03.cig.mot.com (il27exr03.mot.com [10.17.196.72]) by motgate4.mot.com (8.14.3/8.14.3) with ESMTP id n45FmZsl002093 for ; Tue, 5 May 2009 08:48:35 -0700 (MST) Received: from az10vts04.mot.com (il27vts04.cig.mot.com [10.17.196.88]) by il27exr03.cig.mot.com (8.13.1/Vontu) with SMTP id n45FmYDB025182 for ; Tue, 5 May 2009 10:48:34 -0500 (CDT) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by il27exr03.cig.mot.com (8.13.1/8.13.0) with ESMTP id n45FmWhq025098 for ; Tue, 5 May 2009 10:48:33 -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, 5 May 2009 11:48:19 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Recharter: Bulk Revocation Thread-Index: AcnNmOnHv6dNwALmRwuY3jTR52LuuA== From: "McCann Peter-A001034" To: X-CFilter-Loop: Reflected Cc: Henrik Levkowetz Subject: [Mip4] Recharter: Bulk Revocation X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 15:47:12 -0000 Hi, all, During our meeting at IETF74, we discussed whether to take on the Bulk Revocation work, as described in this draft: draft-acee-mip4-bulk-revocation-01.txt There was some support for this work during the meeting, but the sense of the room seemed to be that we need to have more discusion of the need for this before taking it on as a work item. Please, if you support this work item, respond to this message with a summary of why you think it is important for the mip4 working group to take it on at this time. -Pete From pete.mccann@motorola.com Tue May 5 08:47:46 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A41DB3A6CE7 for ; Tue, 5 May 2009 08:47:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.5 X-Spam-Level: X-Spam-Status: No, score=-6.5 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2H2QzEGbSlID for ; Tue, 5 May 2009 08:47:46 -0700 (PDT) Received: from mail153.messagelabs.com (mail153.messagelabs.com [216.82.253.51]) by core3.amsl.com (Postfix) with ESMTP id 1BE8D3A6B2F for ; Tue, 5 May 2009 08:47:42 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-8.tower-153.messagelabs.com!1241538542!13404244!1 X-StarScan-Version: 6.0.0; banners=-,-,- X-Originating-IP: [136.182.1.15] Received: (qmail 6660 invoked from network); 5 May 2009 15:49:03 -0000 Received: from motgate5.mot.com (HELO motgate5.mot.com) (136.182.1.15) by server-8.tower-153.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 May 2009 15:49:03 -0000 Received: from il27exr03.cig.mot.com (il27exr03.mot.com [10.17.196.72]) by motgate5.mot.com (8.14.3/8.14.3) with ESMTP id n45Fn2df009946 for ; Tue, 5 May 2009 08:49:02 -0700 (MST) Received: from il27vts03 (il27vts03.cig.mot.com [10.17.196.87]) by il27exr03.cig.mot.com (8.13.1/Vontu) with SMTP id n45Fn1OK025712 for ; Tue, 5 May 2009 10:49:01 -0500 (CDT) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by il27exr03.cig.mot.com (8.13.1/8.13.0) with ESMTP id n45Fn1be025696 for ; Tue, 5 May 2009 10:49:01 -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, 5 May 2009 11:48:38 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Recharter: GRE Key Extension Thread-Index: AcnNmPTE2kgpVqDgSiqJIzRK5XZG1A== From: "McCann Peter-A001034" To: X-CFilter-Loop: Reflected Cc: Henrik Levkowetz Subject: [Mip4] Recharter: GRE Key Extension X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 15:47:46 -0000 Hi, all, During our meeting at IETF74, we discussed whether to take on a draft describing how to negotiate GRE Keys for when GRE tunneling is used with Mobile IPv4, as described in this draft: draft-yegani-gre-key-extension-03.txt The sense of the room was that we should adopt this draft as a new work item. This message is a request to confirm/reject this approach. Please respond to this e-mail with an indication of whether you agree or disagree, and state your reasons why. -Pete From pete.mccann@motorola.com Tue May 5 08:48:39 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1DA0328C27B for ; Tue, 5 May 2009 08:48:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.509 X-Spam-Level: X-Spam-Status: No, score=-6.509 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yMB0LWtjaDEm for ; Tue, 5 May 2009 08:48:38 -0700 (PDT) Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by core3.amsl.com (Postfix) with ESMTP id DBFE928C16E for ; Tue, 5 May 2009 08:48:29 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-15.tower-119.messagelabs.com!1241538595!26369875!1 X-StarScan-Version: 6.0.0; banners=-,-,- X-Originating-IP: [136.182.1.15] Received: (qmail 1660 invoked from network); 5 May 2009 15:49:55 -0000 Received: from motgate5.mot.com (HELO motgate5.mot.com) (136.182.1.15) by server-15.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 May 2009 15:49:55 -0000 Received: from il27exr04.cig.mot.com ([10.17.196.73]) by motgate5.mot.com (8.14.3/8.14.3) with ESMTP id n45Fnt0g010104 for ; Tue, 5 May 2009 08:49:55 -0700 (MST) Received: from az10vts04.mot.com (il27vts04.cig.mot.com [10.17.196.88]) by il27exr04.cig.mot.com (8.13.1/Vontu) with SMTP id n45FntMl027035 for ; Tue, 5 May 2009 10:49:55 -0500 (CDT) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by il27exr04.cig.mot.com (8.13.1/8.13.0) with ESMTP id n45Fnss2027030 for ; Tue, 5 May 2009 10:49:54 -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, 5 May 2009 11:49:18 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Recharter: Host Configuration Thread-Index: AcnNmQynkZb31cBSTDSBN90Fs1Ht5g== From: "McCann Peter-A001034" To: X-CFilter-Loop: Reflected Cc: Henrik Levkowetz Subject: [Mip4] Recharter: Host Configuration X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 15:48:39 -0000 Hi, all, During our meeting at IETF74, we discussed the way forward for host configuration with Mobile IPv4. On the table are the following drafts: draft-ietf-mip4-gen-ext-04.txt draft-deng-mip4-host-configuration-00.txt draft-chakrabarti-mip4-mcbc-03.txt There was an involved discussion during the meeting on what to do. The point was raised that some SDOs are already extending mip4 with VSEs to do host configuration, and that some support is needed for non-DHCP clients. Issues with the handling of the broadcast DHCPDISCOVER on the home link were also raised, and some people thought that the current specifications would require the home agent to relay every DHCPDISCOVER to every connected mobile node. This clearly would be unacceptable. However, we don't want to go creating too many mechanisms for host configuration that would require maintenance of mip4 every time we add a new configuration option. One proposal put forth by George at the meeting was to do one extension to mip4 to carry a unicast address of a DHCP server, and then run DHCPINFORM directly between the mobile host and=20 that server using unicast messages. Is this the most viable way forward? Please respond to this note with a message saying whether you agree/disagree with this approach, and state your reasons why. Note that there was also support for the multicast-broadcast enhancement draft independent of DHCP. I will create a separate thread to discuss whether to take on that work in our rechartering effort. -Pete From pete.mccann@motorola.com Tue May 5 08:48:39 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 992B828C16E for ; Tue, 5 May 2009 08:48:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.516 X-Spam-Level: X-Spam-Status: No, score=-6.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LgvkpaaDiQO5 for ; Tue, 5 May 2009 08:48:38 -0700 (PDT) Received: from mail128.messagelabs.com (mail128.messagelabs.com [216.82.250.131]) by core3.amsl.com (Postfix) with ESMTP id 54F7928C281 for ; Tue, 5 May 2009 08:48:30 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-2.tower-128.messagelabs.com!1241538595!10237820!1 X-StarScan-Version: 6.0.0; banners=-,-,- X-Originating-IP: [136.182.1.14] Received: (qmail 14785 invoked from network); 5 May 2009 15:49:56 -0000 Received: from motgate4.mot.com (HELO motgate4.mot.com) (136.182.1.14) by server-2.tower-128.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 May 2009 15:49:56 -0000 Received: from il27exr04.cig.mot.com (il27exr04.mot.com [10.17.196.73]) by motgate4.mot.com (8.14.3/8.14.3) with ESMTP id n45Fntfj002342 for ; Tue, 5 May 2009 08:49:55 -0700 (MST) Received: from il27vts01 (il27vts01.cig.mot.com [10.17.196.85]) by il27exr04.cig.mot.com (8.13.1/Vontu) with SMTP id n45FntDB027046 for ; Tue, 5 May 2009 10:49:55 -0500 (CDT) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by il27exr04.cig.mot.com (8.13.1/8.13.0) with ESMTP id n45Fnss4027030 for ; Tue, 5 May 2009 10:49:55 -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, 5 May 2009 11:49:27 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Recharter: Ethernet Service Support Thread-Index: AcnNmRH7OKJDFCkjRGil4lbiFFG7wQ== From: "McCann Peter-A001034" To: X-CFilter-Loop: Reflected Cc: Henrik Levkowetz Subject: [Mip4] Recharter: Ethernet Service Support X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 15:48:39 -0000 Hi, all, During our meeting at IETF74, we discussed whether to take on a draft describing support for Ethernet service to a mobile node, as described in this draft: draft-wu-mip4-ether-00.txt The sense of the room seemed to be that we NOT take on this=20 as a work item at this time. This message is a request to confirm/reject this approach. Please respond to this e-mail with an indication of whether you agree or disagree, and state your reasons why. -Pete From pete.mccann@motorola.com Tue May 5 08:52:18 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 29A0428C255 for ; Tue, 5 May 2009 08:52:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OXa-h+QI6xsW for ; Tue, 5 May 2009 08:52:17 -0700 (PDT) Received: from mail55.messagelabs.com (mail55.messagelabs.com [216.82.241.163]) by core3.amsl.com (Postfix) with ESMTP id 7E9883A6D74 for ; Tue, 5 May 2009 08:51:51 -0700 (PDT) X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-13.tower-55.messagelabs.com!1241538665!96936448!1 X-StarScan-Version: 6.0.0; banners=-,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 11180 invoked from network); 5 May 2009 15:53:16 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-13.tower-55.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 May 2009 15:53:16 -0000 Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133]) by motgate8.mot.com (8.14.3/8.14.3) with ESMTP id n45FoJmC009604 for ; Tue, 5 May 2009 08:50:19 -0700 (MST) Received: from il06vts04.mot.com (il06vts04.mot.com [129.188.137.144]) by il06exr03.mot.com (8.13.1/Vontu) with SMTP id n45FoIHV027413 for ; Tue, 5 May 2009 10:50:18 -0500 (CDT) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id n45FoIhD027406 for ; Tue, 5 May 2009 10:50:18 -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, 5 May 2009 11:49:34 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Recharter: Multicast/Broadcast Support Thread-Index: AcnNmRZQWmemLFzQT8qZhgmQF4gHow== From: "McCann Peter-A001034" To: X-CFilter-Loop: Reflected Cc: Henrik Levkowetz Subject: [Mip4] Recharter: Multicast/Broadcast Support X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 15:52:18 -0000 Hi, all, This is a call for consensus to see whether we want to adopt the IPv4 Mobility Extension for Multicast and Broadcast Packets, as described in the following draft: draft-chakrabarti-mip4-mcbc-03.txt Please respond with a message stating whether you support or oppose this action, and your reasons why. -Pete From denghui02@gmail.com Tue May 5 09:22:22 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A973F3A6899 for ; Tue, 5 May 2009 09:22:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F5dJtPjLmLCu for ; Tue, 5 May 2009 09:22:21 -0700 (PDT) Received: from gv-out-0910.google.com (gv-out-0910.google.com [216.239.58.191]) by core3.amsl.com (Postfix) with ESMTP id 22C2F3A6A0D for ; Tue, 5 May 2009 09:22:20 -0700 (PDT) Received: by gv-out-0910.google.com with SMTP id l14so213702gvf.15 for ; Tue, 05 May 2009 09:23:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=R0PVR57kX6zUWyPpSFtCGHVzDcCFyr/BNkxNBhXPLWg=; b=LKEPXgHsqvLsWOSMIi6VOyKNLoIy8oUEqeMjqX3hhdHk+3E4WWd84/VwsVuu2GgfhN U3/8FYNCdwNWvAnC/WOpE1BpDpQ1wvtW5FJEz2EJxI3/1xlrkn0YrD4v9IAH8nS2Gjr4 Lv+0+QepD5027E47bgJ9qthWnZo+f9cCMMQ8k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=mO2TpYFD3yIUVrfBNM14c1RyvbQq/XvI1lpy17S8v97HhyEDO2LdEVq1pB+qkyq0bN THAt5x9ORLWmzQllJSySKmlg/4j/4VqLfZMqCcTz0zIvXqxloSPlZfOCH7P/lMAcB9yV 7PLuZyo21gJzv+T8wErKJZ2BVezKxerHNZLhY= MIME-Version: 1.0 Received: by 10.142.58.20 with SMTP id g20mr94325wfa.20.1241540624581; Tue, 05 May 2009 09:23:44 -0700 (PDT) In-Reply-To: References: Date: Wed, 6 May 2009 00:23:44 +0800 Message-ID: <1d38a3350905050923s49121a73s888ce3ae954a41fc@mail.gmail.com> From: Hui Deng To: McCann Peter-A001034 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: mip4@ietf.org, Henrik Levkowetz Subject: Re: [Mip4] Recharter: Multicast/Broadcast Support X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 16:22:22 -0000 Hello, all I support this work, but just want to point out there are another related draft avilable before at http://tools.ietf.org/html/draft-deng-multimob-mip4-00 Thanks -Hui 2009/5/5 McCann Peter-A001034 : > Hi, all, > > This is a call for consensus to see whether we want to adopt > the IPv4 Mobility Extension for Multicast and Broadcast Packets, > as described in the following draft: > > draft-chakrabarti-mip4-mcbc-03.txt > > Please respond with a message stating whether you support or oppose > this action, and your reasons why. > > -Pete > -- > Mip4 mailing list: Mip4@ietf.org > =A0 =A0Web interface: https://www.ietf.org/mailman/listinfo/mip4 > =A0 =A0 Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > From denghui02@gmail.com Tue May 5 09:24:09 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 433213A6899 for ; Tue, 5 May 2009 09:24:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d3MwR9ijd3ws for ; Tue, 5 May 2009 09:24:08 -0700 (PDT) Received: from gv-out-0910.google.com (gv-out-0910.google.com [216.239.58.190]) by core3.amsl.com (Postfix) with ESMTP id 441E83A6915 for ; Tue, 5 May 2009 09:24:08 -0700 (PDT) Received: by gv-out-0910.google.com with SMTP id l14so214228gvf.15 for ; Tue, 05 May 2009 09:25:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Dpg8a5wEWFPlg2AbVVemavyUzLxSZIrkHUuKINf6wIU=; b=QbPokcBJ8YxjrIjYMcm+NiIWB6RPzuqTPEFztFGzwXFcreGXhPY+OKWf+h1w8ALSsa tdpktE8/S5P9ZGDkJZGdHo+sHbS23LxINTQ9UujW0c2Keu/R13Gpqr0ARe9LubEuxWHX elp/2SF7+lfHC8icY/eVK4d224WEGYkGfycu4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=OvJSeW9DN0fi84aSvSeUy+iiUl9GZZIaAeog2x7XMGtw24j1lPdNGtLMs8CuHXdRrk 02VQHG/UFBknNMQn4kS8am6v25cLw2AtV8sALrAxnNNf37vgU1+Gd+MQ+n+gCZQBGfQb aW8/3kvv3q3IEXg7Xqse5iSe7cWkLa3asAbZo= MIME-Version: 1.0 Received: by 10.142.192.1 with SMTP id p1mr97384wff.17.1241540733427; Tue, 05 May 2009 09:25:33 -0700 (PDT) In-Reply-To: References: Date: Wed, 6 May 2009 00:25:33 +0800 Message-ID: <1d38a3350905050925g537b45f9w29f35d0f5ef53224@mail.gmail.com> From: Hui Deng To: McCann Peter-A001034 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: mip4@ietf.org, Henrik Levkowetz Subject: Re: [Mip4] Recharter: GRE Key Extension X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 16:24:09 -0000 Hi, all I support this work, since it is what mip4 is lacking at the moment. -Hui 2009/5/5 McCann Peter-A001034 : > Hi, all, > > During our meeting at IETF74, we discussed whether to take on > a draft describing how to negotiate GRE Keys for when GRE tunneling > is used with Mobile IPv4, as described in this draft: > > draft-yegani-gre-key-extension-03.txt > > The sense of the room was that we should adopt this draft as > a new work item. > > This message is a request to confirm/reject this approach. =A0Please > respond to this e-mail with an indication of whether you agree > or disagree, and state your reasons why. > > -Pete > -- > Mip4 mailing list: Mip4@ietf.org > =A0 =A0Web interface: https://www.ietf.org/mailman/listinfo/mip4 > =A0 =A0 Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > From denghui02@gmail.com Tue May 5 09:26:53 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CD74A3A6BDA for ; Tue, 5 May 2009 09:26:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.235 X-Spam-Level: X-Spam-Status: No, score=-2.235 tagged_above=-999 required=5 tests=[AWL=0.364, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mPrfsUrDXEpy for ; Tue, 5 May 2009 09:26:47 -0700 (PDT) Received: from mail-bw0-f174.google.com (mail-bw0-f174.google.com [209.85.218.174]) by core3.amsl.com (Postfix) with ESMTP id 5528E28C13B for ; Tue, 5 May 2009 09:26:37 -0700 (PDT) Received: by bwz22 with SMTP id 22so1414454bwz.37 for ; Tue, 05 May 2009 09:28:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=dbLkoTfyGTjdYUCZc+dKpbZjQ7iljFeG2Nu1lq4FcsA=; b=we4oy8x010gBQgOBLu9ls/Vno+RJxM425sGcXHkCyCrG6LplR4ohd8USLR4sI0K0Pc YzYu3Vj7wjlzUKaQu4cqDEYrqmPYjmhLAFYRR/qtILaUxe+vB6b8pdeB38BRKgRrMWwU qZ2dsZx/cyLkrutpxiwlHAwOiHYb7cvxXR+P4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=rB5bpPOkjx0YJJyBKo277A8HQO/k8bihZcYMazCMsYQuzF685R2yOv8bTttw6hKoL+ FDo92XJIy1YyG24PiRuZJ7F2Fs/GxQXLl+siB1QZpTjNnM/aQZl70zx5vKuZ2QXq41e0 Jo3GIL53Q9tzCYFkgweo2XMoo+cTgmeBNuNyE= MIME-Version: 1.0 Received: by 10.142.58.5 with SMTP id g5mr80653wfa.170.1241540880422; Tue, 05 May 2009 09:28:00 -0700 (PDT) In-Reply-To: References: Date: Wed, 6 May 2009 00:28:00 +0800 Message-ID: <1d38a3350905050928y4f4a4cb0ue670266e27168174@mail.gmail.com> From: Hui Deng To: McCann Peter-A001034 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: mip4@ietf.org, Henrik Levkowetz Subject: Re: [Mip4] Recharter: Multiple Tunnel Support X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 16:26:53 -0000 Hi, all I support this work since there are enough interest to work on it. -Hui 2009/5/5 McCann Peter-A001034 : > Hi, all, > > During our meeting at IETF74, we discussed whether to take on > the multiple tunnel support and flow movement, as described in > these two drafts: > > draft-gundavelli-mip4-multiple-tunnel-support-00.txt > draft-tsirtsis-mip4-flowmove-01.txt > > The sense of the room seemed to be that we should combine these > two drafts and take the result on as a new work item. > > This message is a request to confirm/reject this approach. =A0Please > respond to this e-mail with an indication of whether you agree > or disagree, and state your reasons why. > > -Pete > > -- > Mip4 mailing list: Mip4@ietf.org > =A0 =A0Web interface: https://www.ietf.org/mailman/listinfo/mip4 > =A0 =A0 Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > From AMUHANNA@nortel.com Tue May 5 09:33:38 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5751A28C232 for ; Tue, 5 May 2009 09:33:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.581 X-Spam-Level: X-Spam-Status: No, score=-6.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id knaeFDlaiz8r for ; Tue, 5 May 2009 09:33:37 -0700 (PDT) Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 8744128C244 for ; Tue, 5 May 2009 09:31:02 -0700 (PDT) Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n45GWNm24674; Tue, 5 May 2009 16:32:23 GMT 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, 5 May 2009 11:31:41 -0500 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Recharter: GRE Key Extension Thread-Index: AcnNmPTE2kgpVqDgSiqJIzRK5XZG1AABVQgg References: From: "Ahmad Muhanna" To: "McCann Peter-A001034" , Cc: Henrik Levkowetz Subject: Re: [Mip4] Recharter: GRE Key Extension X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 May 2009 16:33:38 -0000 Hello Pete, GRE as a tunneling mechanism is supported by Mobile IPv4 specification. Adding a dynamic mechanism for exchanging the GRE keys using the MIP4 signaling is very useful and allows the identification of different flows based on the GRE key. Therefore, I support this to be adopted as a work item. Regards, Ahmad =20 > -----Original Message----- > From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On=20 > Behalf Of McCann Peter-A001034 > Sent: Tuesday, May 05, 2009 10:49 AM > To: mip4@ietf.org > Cc: Henrik Levkowetz > Subject: [Mip4] Recharter: GRE Key Extension >=20 > Hi, all, >=20 > During our meeting at IETF74, we discussed whether to take on=20 > a draft describing how to negotiate GRE Keys for when GRE=20 > tunneling is used with Mobile IPv4, as described in this draft: >=20 > draft-yegani-gre-key-extension-03.txt >=20 > The sense of the room was that we should adopt this draft as=20 > a new work item. >=20 > This message is a request to confirm/reject this approach. =20 > Please respond to this e-mail with an indication of whether=20 > you agree or disagree, and state your reasons why. >=20 > -Pete > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ >=20 From w52006@huawei.com Tue May 5 17:31:50 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C237F3A6C91 for ; Tue, 5 May 2009 17:31:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.499 X-Spam-Level: X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id boXx3o2R5Gom for ; Tue, 5 May 2009 17:31:50 -0700 (PDT) Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id C72413A6831 for ; Tue, 5 May 2009 17:31:49 -0700 (PDT) Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJ700L6O5J6RQ@szxga03-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 08:33:06 +0800 (CST) Received: from huawei.com ([172.24.1.24]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJ7005185J67F@szxga03-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 08:33:06 +0800 (CST) Received: from w52006a ([10.164.12.21]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KJ7007VY5J5RH@szxml04-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 08:33:06 +0800 (CST) Date: Wed, 06 May 2009 08:33:05 +0800 From: Yungui Wang In-reply-to: <1d38a3350905050928y4f4a4cb0ue670266e27168174@mail.gmail.com> To: 'Hui Deng' , 'McCann Peter-A001034' Message-id: <005f01c9cde2$39163730$150ca40a@china.huawei.com> Organization: huawei MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable Thread-index: AcnNno4jMP1Wy9g8T2Gz+uYPzlj4MAAQ0FGA Cc: mip4@ietf.org, 'Henrik Levkowetz' Subject: Re: [Mip4] Recharter: Multiple Tunnel Support X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: w52006@huawei.com List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 00:31:50 -0000 Support too. =20 I have one question: does it cover HMIP domain (rfc4857) yet? B.R. Yungui =20 > -----Original Message----- > From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On=20 > Behalf Of Hui Deng > Sent: Wednesday, May 06, 2009 12:28 AM > To: McCann Peter-A001034 > Cc: mip4@ietf.org; Henrik Levkowetz > Subject: Re: [Mip4] Recharter: Multiple Tunnel Support >=20 > Hi, all >=20 > I support this work since there are enough interest to work on it. >=20 > -Hui >=20 > 2009/5/5 McCann Peter-A001034 : > > Hi, all, > > > > During our meeting at IETF74, we discussed whether to take on > > the multiple tunnel support and flow movement, as described in > > these two drafts: > > > > draft-gundavelli-mip4-multiple-tunnel-support-00.txt > > draft-tsirtsis-mip4-flowmove-01.txt > > > > The sense of the room seemed to be that we should combine these > > two drafts and take the result on as a new work item. > > > > This message is a request to confirm/reject this approach. =A0Please > > respond to this e-mail with an indication of whether you agree > > or disagree, and state your reasons why. > > > > -Pete > > > > -- > > Mip4 mailing list: Mip4@ietf.org > > =A0 =A0Web interface: https://www.ietf.org/mailman/listinfo/mip4 > > =A0 =A0 Charter page:=20 > http://www.ietf.org/html.charters/mip4-charter.html > > Supplemental site: http://www.mip4.org/ > > > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ >=20 From w52006@huawei.com Tue May 5 18:15:29 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 976273A709D for ; Tue, 5 May 2009 18:15:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.551 X-Spam-Level: X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[AWL=1.048, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iU29xCMlitGx for ; Tue, 5 May 2009 18:15:28 -0700 (PDT) Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 343B73A704B for ; Tue, 5 May 2009 18:15:28 -0700 (PDT) Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJ700KWQ7K27M@szxga02-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 09:16:50 +0800 (CST) Received: from huawei.com ([172.24.1.33]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJ700GG77K2JC@szxga02-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 09:16:50 +0800 (CST) Received: from w52006a ([10.164.12.21]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KJ700KHZ7K1GR@szxml06-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 09:16:50 +0800 (CST) Date: Wed, 06 May 2009 09:16:49 +0800 From: Yungui Wang In-reply-to: To: 'McCann Peter-A001034' , mip4@ietf.org Message-id: <006001c9cde8$55387580$150ca40a@china.huawei.com> Organization: huawei MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-index: AcnNmRH7OKJDFCkjRGil4lbiFFG7wQATe96A Cc: 'Henrik Levkowetz' Subject: Re: [Mip4] Recharter: Ethernet Service Support X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: w52006@huawei.com List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 01:15:29 -0000 Hello I support this work. The emulated Ethernet over fixed IP infrastructure had be widely deployed as rfc4448 and rfc4719, etc. In fixed and mobile convergence network, it is possible that mobile network infrastructure could also offer the emulated Ethernet service. For example, Ethernet service traversing WiMAX network is described in 01029_r001_NWG_ETH_Srvs_R1-5_Stage2_ Amendment_Rel_1[1].5_v1.0.2_V&V INTERIM Draft.doc from http://members.wimaxforum.org/apps/org/workgroup/nwg/ documents.php. B.R. /Yungui > -----Original Message----- > From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On > Behalf Of McCann Peter-A001034 > Sent: Tuesday, May 05, 2009 11:49 PM > To: mip4@ietf.org > Cc: Henrik Levkowetz > Subject: [Mip4] Recharter: Ethernet Service Support > > Hi, all, > > During our meeting at IETF74, we discussed whether to take on > a draft describing support for Ethernet service to a mobile node, > as described in this draft: > > draft-wu-mip4-ether-00.txt > > The sense of the room seemed to be that we NOT take on this > as a work item at this time. > > This message is a request to confirm/reject this approach. Please > respond to this e-mail with an indication of whether you agree > or disagree, and state your reasons why. > > -Pete > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > From Mohana.Jeyatharan@sg.panasonic.com Tue May 5 18:28:41 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A5863A6997 for ; Tue, 5 May 2009 18:28:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.281 X-Spam-Level: X-Spam-Status: No, score=0.281 tagged_above=-999 required=5 tests=[AWL=0.371, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ujTih5UZhx6R for ; Tue, 5 May 2009 18:28:40 -0700 (PDT) Received: from smtp.mei.co.jp (smtp.mei.co.jp [133.183.100.20]) by core3.amsl.com (Postfix) with ESMTP id 735353A6A8E for ; Tue, 5 May 2009 18:28:40 -0700 (PDT) Received: from mail-gw.jp.panasonic.com ([157.8.1.145]) by smtp.mei.co.jp (8.12.11.20060614/3.7W/kc-maile11) with ESMTP id n461U2fJ002093; Wed, 6 May 2009 10:30:02 +0900 (JST) Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlb3) with ESMTP id n461U2s18948; Wed, 6 May 2009 10:30:02 +0900 (JST) Received: from pslexc01.psl.local (localhost [127.0.0.1]) by mail.jp.panasonic.com (8.11.6p2/3.7W/kc-maili04) with ESMTP id n461U1w18439; Wed, 6 May 2009 10:30:01 +0900 (JST) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 6 May 2009 09:31:41 +0800 Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.5.7235.2 Message-ID: <5F09D220B62F79418461A978CA0921BD0350518A@pslexc01.psl.local> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Recharter: Multiple Tunnel Support thread-index: AcnNmNDbMcuRI+dXQmaJ8g/mqcFpSgAUXflA From: "Mohana Jeyatharan" To: "McCann Peter-A001034" , Cc: Henrik Levkowetz Subject: Re: [Mip4] Recharter: Multiple Tunnel Support X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 01:28:41 -0000 Hi all, I support this work since there is enough interest and also it is very useful. BR, Mohana > -----Original Message----- > From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of > McCann Peter-A001034 > Sent: Tuesday, May 05, 2009 11:48 PM > To: mip4@ietf.org > Cc: Henrik Levkowetz > Subject: [Mip4] Recharter: Multiple Tunnel Support >=20 > Hi, all, >=20 > During our meeting at IETF74, we discussed whether to take on > the multiple tunnel support and flow movement, as described in > these two drafts: >=20 > draft-gundavelli-mip4-multiple-tunnel-support-00.txt > draft-tsirtsis-mip4-flowmove-01.txt >=20 > The sense of the room seemed to be that we should combine these > two drafts and take the result on as a new work item. >=20 > This message is a request to confirm/reject this approach. Please > respond to this e-mail with an indication of whether you agree > or disagree, and state your reasons why. >=20 > -Pete >=20 > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ From prvs=370501d4c=rahman@redback.com Tue May 5 20:26:41 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC1663A68BC for ; Tue, 5 May 2009 20:26:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aJ+u4NljpU8s for ; Tue, 5 May 2009 20:26:41 -0700 (PDT) Received: from mgate.redback.com (mgate.redback.com [155.53.3.41]) by core3.amsl.com (Postfix) with ESMTP id 71E4D28C29D for ; Tue, 5 May 2009 20:26:25 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.40,301,1239001200"; d="scan'208";a="1463249" Received: from prattle.redback.com ([155.53.12.9]) by mgate.redback.com with ESMTP; 05 May 2009 20:27:52 -0700 Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id AC5ED539E4E; Tue, 5 May 2009 20:27:52 -0700 (PDT) Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05955-01; Tue, 5 May 2009 20:27:52 -0700 (PDT) Received: from rbsjx.ad.redback.com (rbsjxh1.redback.com [155.53.14.105]) by prattle.redback.com (Postfix) with ESMTP id 99AD7539E4D; Tue, 5 May 2009 20:27:52 -0700 (PDT) Received: from RBSJX.ad.redback.com ([155.53.14.103]) by rbsjxh1.ad.redback.com ([155.53.14.105]) with mapi; Tue, 5 May 2009 20:27:52 -0700 From: Shahriar Rahman To: McCann Peter-A001034 , "mip4@ietf.org" Date: Tue, 5 May 2009 20:26:06 -0700 Thread-Topic: Recharter: GRE Key Extension Thread-Index: AcnNmPTE2kgpVqDgSiqJIzRK5XZG1AAYWEPQ Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Henrik Levkowetz Subject: Re: [Mip4] Recharter: GRE Key Extension X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 03:28:40 -0000 Hi, I support work on this topic as it's a currently gap in MIP4. Thanks. Shah -----Original Message----- From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of McC= ann Peter-A001034 Sent: Tuesday, May 05, 2009 8:49 AM To: mip4@ietf.org Cc: Henrik Levkowetz Subject: [Mip4] Recharter: GRE Key Extension Hi, all, During our meeting at IETF74, we discussed whether to take on a draft describing how to negotiate GRE Keys for when GRE tunneling is used with Mobile IPv4, as described in this draft: draft-yegani-gre-key-extension-03.txt The sense of the room was that we should adopt this draft as a new work item. This message is a request to confirm/reject this approach. Please respond to this e-mail with an indication of whether you agree or disagree, and state your reasons why. -Pete -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From prvs=370501d4c=rahman@redback.com Tue May 5 20:26:40 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C44EB3A6DF4 for ; Tue, 5 May 2009 20:26:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5l-oASx7EciQ for ; Tue, 5 May 2009 20:26:39 -0700 (PDT) Received: from mgate.redback.com (mgate.redback.com [155.53.3.41]) by core3.amsl.com (Postfix) with ESMTP id BEE7528C258 for ; Tue, 5 May 2009 20:25:53 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.40,301,1239001200"; d="scan'208";a="1463238" Received: from prattle.redback.com ([155.53.12.9]) by mgate.redback.com with ESMTP; 05 May 2009 20:27:20 -0700 Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id E36912E16E3; Tue, 5 May 2009 20:27:20 -0700 (PDT) Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05761-09; Tue, 5 May 2009 20:27:20 -0700 (PDT) Received: from rbsjx.ad.redback.com (rbsjxh2.redback.com [155.53.14.106]) by prattle.redback.com (Postfix) with ESMTP id 988FB2E16E2; Tue, 5 May 2009 20:27:20 -0700 (PDT) Received: from RBSJX.ad.redback.com ([155.53.14.103]) by rbsjxh2.ad.redback.com ([155.53.14.106]) with mapi; Tue, 5 May 2009 20:27:20 -0700 From: Shahriar Rahman To: McCann Peter-A001034 , "mip4@ietf.org" Date: Tue, 5 May 2009 20:25:33 -0700 Thread-Topic: Recharter: Multiple Tunnel Support Thread-Index: AcnNmNDbMcuRI+dXQmaJ8g/mqcFpSgAYXR4Q Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Henrik Levkowetz Subject: Re: [Mip4] Recharter: Multiple Tunnel Support X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 03:28:44 -0000 Hi, I support work on this topic. Thanks. Shah -----Original Message----- From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of McC= ann Peter-A001034 Sent: Tuesday, May 05, 2009 8:48 AM To: mip4@ietf.org Cc: Henrik Levkowetz Subject: [Mip4] Recharter: Multiple Tunnel Support Hi, all, During our meeting at IETF74, we discussed whether to take on the multiple tunnel support and flow movement, as described in these two drafts: draft-gundavelli-mip4-multiple-tunnel-support-00.txt draft-tsirtsis-mip4-flowmove-01.txt The sense of the room seemed to be that we should combine these two drafts and take the result on as a new work item. This message is a request to confirm/reject this approach. Please respond to this e-mail with an indication of whether you agree or disagree, and state your reasons why. -Pete =20 -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From prvs=370501d4c=rahman@redback.com Tue May 5 20:27:50 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 323323A6880 for ; Tue, 5 May 2009 20:27:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U10hU9KOI5XL for ; Tue, 5 May 2009 20:27:49 -0700 (PDT) Received: from mgate.redback.com (mgate.redback.com [155.53.3.41]) by core3.amsl.com (Postfix) with ESMTP id 79C7D3A6837 for ; Tue, 5 May 2009 20:27:49 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.40,301,1239001200"; d="scan'208";a="1463262" Received: from prattle.redback.com ([155.53.12.9]) by mgate.redback.com with ESMTP; 05 May 2009 20:29:16 -0700 Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id AAA4A70C38A; Tue, 5 May 2009 20:29:16 -0700 (PDT) Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05955-05; Tue, 5 May 2009 20:29:16 -0700 (PDT) Received: from rbsjx.ad.redback.com (rbsjxh1.redback.com [155.53.14.105]) by prattle.redback.com (Postfix) with ESMTP id 9989570C38D; Tue, 5 May 2009 20:29:16 -0700 (PDT) Received: from RBSJX.ad.redback.com ([155.53.14.103]) by rbsjxh1.ad.redback.com ([155.53.14.105]) with mapi; Tue, 5 May 2009 20:29:16 -0700 From: Shahriar Rahman To: McCann Peter-A001034 , "mip4@ietf.org" Date: Tue, 5 May 2009 20:27:30 -0700 Thread-Topic: Recharter: Ethernet Service Support Thread-Index: AcnNmRH7OKJDFCkjRGil4lbiFFG7wQAYWtKA Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Henrik Levkowetz Subject: Re: [Mip4] Recharter: Ethernet Service Support X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 03:28:49 -0000 Hi, I support work on this topic and could be interested to assist in the works= . Thanks. Shah -----Original Message----- From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of McC= ann Peter-A001034 Sent: Tuesday, May 05, 2009 8:49 AM To: mip4@ietf.org Cc: Henrik Levkowetz Subject: [Mip4] Recharter: Ethernet Service Support Hi, all, During our meeting at IETF74, we discussed whether to take on a draft describing support for Ethernet service to a mobile node, as described in this draft: draft-wu-mip4-ether-00.txt The sense of the room seemed to be that we NOT take on this=20 as a work item at this time. This message is a request to confirm/reject this approach. Please respond to this e-mail with an indication of whether you agree or disagree, and state your reasons why. -Pete -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From sunseawq@huawei.com Tue May 5 23:09:18 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 038173A6A48 for ; Tue, 5 May 2009 23:09:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.471 X-Spam-Level: X-Spam-Status: No, score=-0.471 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ailwvrW+lHqY for ; Tue, 5 May 2009 23:09:10 -0700 (PDT) Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 156843A6824 for ; Tue, 5 May 2009 23:09:10 -0700 (PDT) Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJ7009D0L5EL8@szxga03-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 14:10:26 +0800 (CST) Received: from huawei.com ([172.24.1.24]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJ700CVQL5EF3@szxga03-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 14:10:26 +0800 (CST) Received: from w53375 ([10.164.12.38]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KJ7006PGL5DOW@szxml04-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 14:10:26 +0800 (CST) Date: Wed, 06 May 2009 14:10:25 +0800 From: Qin Wu To: Shahriar Rahman , McCann Peter-A001034 , mip4@ietf.org Message-id: <02c601c9ce11$58c82f50$260ca40a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Outlook Express 6.00.2900.3138 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: Cc: Henrik Levkowetz Subject: Re: [Mip4] Recharter: Ethernet Service Support X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 06:09:18 -0000 Thanks Shah, I am glad you join this work. As we discussed in the IETF74 meeting, I will consider to incorporate VSE mechanism as another candidate mechanism to transport ethernet service across MIP to what we already have in the draft. And your further comments and suggestion are welcome in the maillist. Regards! -Qin ----- Original Message ----- From: "Shahriar Rahman" To: "McCann Peter-A001034" ; Cc: "Henrik Levkowetz" Sent: Wednesday, May 06, 2009 11:27 AM Subject: Re: [Mip4] Recharter: Ethernet Service Support > Hi, > I support work on this topic and could be interested to assist in the works. > > Thanks. > Shah > > -----Original Message----- > From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of McCann Peter-A001034 > Sent: Tuesday, May 05, 2009 8:49 AM > To: mip4@ietf.org > Cc: Henrik Levkowetz > Subject: [Mip4] Recharter: Ethernet Service Support > > Hi, all, > > During our meeting at IETF74, we discussed whether to take on > a draft describing support for Ethernet service to a mobile node, > as described in this draft: > > draft-wu-mip4-ether-00.txt > > The sense of the room seemed to be that we NOT take on this > as a work item at this time. > > This message is a request to confirm/reject this approach. Please > respond to this e-mail with an indication of whether you agree > or disagree, and state your reasons why. > > -Pete > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www.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://www.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > From denghui02@gmail.com Tue May 5 23:16:45 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5BBA63A6B0F for ; Tue, 5 May 2009 23:16:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.24 X-Spam-Level: X-Spam-Status: No, score=-2.24 tagged_above=-999 required=5 tests=[AWL=0.359, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LWWEcg03hTWm for ; Tue, 5 May 2009 23:16:37 -0700 (PDT) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.169]) by core3.amsl.com (Postfix) with ESMTP id D53803A6B70 for ; Tue, 5 May 2009 23:15:52 -0700 (PDT) Received: by wf-out-1314.google.com with SMTP id 29so4377692wff.31 for ; Tue, 05 May 2009 23:17:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=VTWS4bkb8IOLVEKzJcaaV1vYJ57Jv/77sg5YVW3QzOg=; b=EGop3XsLgTtm/zMDpg7Tm4BobS9dnznZtuBIfdW7gcP9/OyR6zE0Kg/jYs4RQZO9FE Eg0Sl8j2O/uaincQmeJiTLs5xheXwxPs3gmcfF2EQOkSM5TfXoUlIZwbZWg4DpN4S+zy 2MZ35kUd9zeusvXVQUKHdhrdeU7en1LVv1CAk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=WY2FBfVeVvMQu2X8QTVwSRDLeJ17Eh4rSfy0JCtZiZx/Z8Ih9VigReSzN/dCEswNNt Y/VKtk+mI1NzsuEN4tzOaTYNoo6PhXMcRC/Z8gk7uCGbm/lyWkXYqw6sn4OTWrXosTrA 1UzvktP5vPfEs1kLyD28wNEsowhOjB1anGAi4= MIME-Version: 1.0 Received: by 10.142.207.8 with SMTP id e8mr350819wfg.278.1241590638415; Tue, 05 May 2009 23:17:18 -0700 (PDT) In-Reply-To: References: Date: Wed, 6 May 2009 14:17:18 +0800 Message-ID: <1d38a3350905052317xb5b764rc5e61c2835f48d49@mail.gmail.com> From: Hui Deng To: McCann Peter-A001034 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: mip4@ietf.org, Henrik Levkowetz Subject: Re: [Mip4] Recharter: Ethernet Service Support X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 06:16:45 -0000 Hello, all It seems major concerns have been considered by the updated version. so I support this work as well -Hui 2009/5/5 McCann Peter-A001034 : > Hi, all, > > During our meeting at IETF74, we discussed whether to take on > a draft describing support for Ethernet service to a mobile node, > as described in this draft: > > draft-wu-mip4-ether-00.txt > > The sense of the room seemed to be that we NOT take on this > as a work item at this time. > > This message is a request to confirm/reject this approach. =A0Please > respond to this e-mail with an indication of whether you agree > or disagree, and state your reasons why. > > -Pete > -- > Mip4 mailing list: Mip4@ietf.org > =A0 =A0Web interface: https://www.ietf.org/mailman/listinfo/mip4 > =A0 =A0 Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > From sunseawq@huawei.com Tue May 5 23:16:51 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E0BAF3A6D7E for ; Tue, 5 May 2009 23:16:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.471 X-Spam-Level: X-Spam-Status: No, score=-0.471 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NkNfsscuQx5B for ; Tue, 5 May 2009 23:16:44 -0700 (PDT) Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 2D0C53A6D19 for ; Tue, 5 May 2009 23:16:33 -0700 (PDT) Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJ700AOSLHP94@szxga01-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 14:17:49 +0800 (CST) Received: from huawei.com ([172.24.1.33]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJ7002XZLHPL3@szxga01-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 14:17:49 +0800 (CST) Received: from w53375 ([10.164.12.38]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KJ7005FLLHO4I@szxml06-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 14:17:49 +0800 (CST) Date: Wed, 06 May 2009 14:17:48 +0800 From: Qin Wu To: McCann Peter-A001034 , mip4@ietf.org Message-id: <02f701c9ce12$610d6210$260ca40a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Outlook Express 6.00.2900.3138 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: Cc: Henrik Levkowetz Subject: Re: [Mip4] Recharter: GRE Key Extension X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 06:16:52 -0000 I support this work, since GRE mechanism has already been pushed forward in the netlmm WG, mip4 WG needs the similar synchroneous work. ----- Original Message ----- From: "McCann Peter-A001034" To: Cc: "Henrik Levkowetz" Sent: Tuesday, May 05, 2009 11:48 PM Subject: [Mip4] Recharter: GRE Key Extension > Hi, all, > > During our meeting at IETF74, we discussed whether to take on > a draft describing how to negotiate GRE Keys for when GRE tunneling > is used with Mobile IPv4, as described in this draft: > > draft-yegani-gre-key-extension-03.txt > > The sense of the room was that we should adopt this draft as > a new work item. > > This message is a request to confirm/reject this approach. Please > respond to this e-mail with an indication of whether you agree > or disagree, and state your reasons why. > > -Pete > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > From sunseawq@huawei.com Tue May 5 23:33:55 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 92C4228C247 for ; Tue, 5 May 2009 23:33:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.472 X-Spam-Level: X-Spam-Status: No, score=-0.472 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ejHpeaJCwhSZ for ; Tue, 5 May 2009 23:33:46 -0700 (PDT) Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id C84B528C27B for ; Tue, 5 May 2009 23:32:24 -0700 (PDT) Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJ700AVBM8494@szxga01-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 14:33:41 +0800 (CST) Received: from huawei.com ([172.24.1.24]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJ7002B7M84L3@szxga01-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 14:33:40 +0800 (CST) Received: from w53375 ([10.164.12.38]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KJ7006CWM82OW@szxml04-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 14:33:39 +0800 (CST) Date: Wed, 06 May 2009 14:33:38 +0800 From: Qin Wu To: McCann Peter-A001034 , mip4@ietf.org Message-id: <036301c9ce14$972657b0$260ca40a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Outlook Express 6.00.2900.3138 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: Cc: Henrik Levkowetz Subject: Re: [Mip4] Recharter: Ethernet Service Support X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 06:33:55 -0000 Hi, Folks: We just submitted the updated Internet draft: http://www.ietf.org/internet-drafts/draft-wu-mip4-ether-01.txt Your Comments and suggestions are welcome. Regards! -Qin ----- Original Message ----- From: "McCann Peter-A001034" To: Cc: "Henrik Levkowetz" Sent: Tuesday, May 05, 2009 11:49 PM Subject: [Mip4] Recharter: Ethernet Service Support > Hi, all, > > During our meeting at IETF74, we discussed whether to take on > a draft describing support for Ethernet service to a mobile node, > as described in this draft: > > draft-wu-mip4-ether-00.txt > > The sense of the room seemed to be that we NOT take on this > as a work item at this time. > > This message is a request to confirm/reject this approach. Please > respond to this e-mail with an indication of whether you agree > or disagree, and state your reasons why. > > -Pete > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > From sunseawq@huawei.com Tue May 5 23:49:36 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1EEC13A6A3F for ; Tue, 5 May 2009 23:49:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.472 X-Spam-Level: X-Spam-Status: No, score=-0.472 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0BiQiD6I5qyF for ; Tue, 5 May 2009 23:49:29 -0700 (PDT) Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id D90D63A6D55 for ; Tue, 5 May 2009 23:48:46 -0700 (PDT) Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJ700HOHMVQAU@szxga04-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 14:47:50 +0800 (CST) Received: from huawei.com ([172.24.1.33]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJ700281MVQYM@szxga04-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 14:47:50 +0800 (CST) Received: from w53375 ([10.164.12.38]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KJ7005OSMVP4I@szxml06-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 14:47:50 +0800 (CST) Date: Wed, 06 May 2009 14:47:49 +0800 From: Qin Wu To: McCann Peter-A001034 , mip4@ietf.org Message-id: <03ed01c9ce16$925e3660$260ca40a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Outlook Express 6.00.2900.3138 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: Cc: Henrik Levkowetz Subject: Re: [Mip4] Recharter: Multiple Tunnel Support X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 06:49:36 -0000 Since this work does cover multi-homing issues in the mip4 scenario, I would like to support this work. -Qin ----- Original Message ----- From: "McCann Peter-A001034" To: Cc: "Henrik Levkowetz" Sent: Tuesday, May 05, 2009 11:47 PM Subject: [Mip4] Recharter: Multiple Tunnel Support > Hi, all, > > During our meeting at IETF74, we discussed whether to take on > the multiple tunnel support and flow movement, as described in > these two drafts: > > draft-gundavelli-mip4-multiple-tunnel-support-00.txt > draft-tsirtsis-mip4-flowmove-01.txt > > The sense of the room seemed to be that we should combine these > two drafts and take the result on as a new work item. > > This message is a request to confirm/reject this approach. Please > respond to this e-mail with an indication of whether you agree > or disagree, and state your reasons why. > > -Pete > > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > From sgundave@cisco.com Wed May 6 15:15:10 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A233D3A6949 for ; Wed, 6 May 2009 15:15:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.14 X-Spam-Level: X-Spam-Status: No, score=-6.14 tagged_above=-999 required=5 tests=[AWL=-0.141, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NOIk5nem75m6 for ; Wed, 6 May 2009 15:15:09 -0700 (PDT) Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id ADDA63A6ABF for ; Wed, 6 May 2009 15:15:09 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.40,305,1238976000"; d="scan'208";a="299764221" Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 06 May 2009 22:16:37 +0000 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/8.12.11) with ESMTP id n46MGbZl029663; Wed, 6 May 2009 15:16:37 -0700 Received: from irp-view13.cisco.com (irp-view13.cisco.com [171.70.120.60]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n46MGbUO023906; Wed, 6 May 2009 22:16:37 GMT Date: Wed, 6 May 2009 15:16:37 -0700 (PDT) From: Sri Gundavelli To: McCann Peter-A001034 In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1088; t=1241648197; x=1242512197; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=sgundave@cisco.com; z=From:=20Sri=20Gundavelli=20 |Subject:=20Re=3A=20[Mip4]=20Recharter=3A=20Home=20Agent=20 Assisted=20Route=20Optimization |Sender:=20; bh=iqz3jEl88xaF5jB9toFsWh2tb1nKBeyjEivX8ROpW9s=; b=lx59+B+HwzsiIQmIbFTQiWAkJqGDoM4srW1wY7Iv+u9aiAJY7OzYttJYW8 IRwWU8RfWqyaUhnxb0vXruNSg5kriHs+O6BMHKkfoH/77gh0IFPNY3u30Fph Kt07K5SuUf; Authentication-Results: sj-dkim-4; header.From=sgundave@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); Cc: mip4@ietf.org, Henrik Levkowetz Subject: Re: [Mip4] Recharter: Home Agent Assisted Route Optimization X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 22:15:10 -0000 Some v.good work went into this draft, lot of details. I will post my comments later. If the WG is interested in this topic (market for this is the question), this is probably a base. Also, keeping this in experimental track makes lot of sense. I'd support this in experimental track. Sri On Tue, 5 May 2009, McCann Peter-A001034 wrote: > Hi, all, > > During our meeting at IETF74, we discussed whether to take on > Home Agent Assisted Route Optimization, as described in this > draft: > > draft-makela-mip4-nemo-haaro-03.txt > > The sense of the room was that we needed more discussion to > understand the scope and applicability of this draft. > > Please, if you support this work item, respond to this message > with a summary of why you think it is important for the mip4 > working group to take it on at this time. > > -Pete > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > From sgundave@cisco.com Wed May 6 15:16:24 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D651C3A68DC for ; Wed, 6 May 2009 15:16:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.438 X-Spam-Level: X-Spam-Status: No, score=-6.438 tagged_above=-999 required=5 tests=[AWL=0.161, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id re2-f34qVkoh for ; Wed, 6 May 2009 15:16:24 -0700 (PDT) Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 847103A6A94 for ; Wed, 6 May 2009 15:15:50 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.40,305,1238976000"; d="scan'208";a="181926622" Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-1.cisco.com with ESMTP; 06 May 2009 22:17:18 +0000 Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n46MHIUN030556; Wed, 6 May 2009 15:17:18 -0700 Received: from irp-view13.cisco.com (irp-view13.cisco.com [171.70.120.60]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n46MHISH018687; Wed, 6 May 2009 22:17:18 GMT Date: Wed, 6 May 2009 15:17:17 -0700 (PDT) From: Sri Gundavelli To: McCann Peter-A001034 In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=891; t=1241648238; x=1242512238; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=sgundave@cisco.com; z=From:=20Sri=20Gundavelli=20 |Subject:=20Re=3A=20[Mip4]=20Recharter=3A=20GRE=20Key=20Ext ension |Sender:=20; bh=/ErufBoCGIAze3oIeDtHJJeYmFz9nE1LRx6XCSul/4c=; b=dio++QCJKkwoDuVCXP+pYXrHm9IpG8THuRW1B7MjmjaHF6dGJRkEx80tdb L/aDu/gCmV7HNA+7FjbgTgAfy+n98JjeNasWCyX5/cUWFibsCxSwDvPGQ32b wDdA2W80o/; Authentication-Results: sj-dkim-4; header.From=sgundave@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); Cc: mip4@ietf.org, Henrik Levkowetz Subject: Re: [Mip4] Recharter: GRE Key Extension X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 22:16:24 -0000 I support this draft. Its there for 3 or 4 years, hope it can move faster. On Tue, 5 May 2009, McCann Peter-A001034 wrote: > Hi, all, > > During our meeting at IETF74, we discussed whether to take on > a draft describing how to negotiate GRE Keys for when GRE tunneling > is used with Mobile IPv4, as described in this draft: > > draft-yegani-gre-key-extension-03.txt > > The sense of the room was that we should adopt this draft as > a new work item. > > This message is a request to confirm/reject this approach. Please > respond to this e-mail with an indication of whether you agree > or disagree, and state your reasons why. > > -Pete > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > From sgundave@cisco.com Wed May 6 15:23:41 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6CC3F3A6A05 for ; Wed, 6 May 2009 15:23:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.44 X-Spam-Level: X-Spam-Status: No, score=-6.44 tagged_above=-999 required=5 tests=[AWL=0.159, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DR1yMjPQ8XWn for ; Wed, 6 May 2009 15:23:40 -0700 (PDT) Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 827703A67D4 for ; Wed, 6 May 2009 15:23:40 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.40,305,1238976000"; d="scan'208";a="299769382" Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 06 May 2009 22:25:08 +0000 Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n46MP80r011316; Wed, 6 May 2009 15:25:08 -0700 Received: from irp-view13.cisco.com (irp-view13.cisco.com [171.70.120.60]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n46MP8v0025028; Wed, 6 May 2009 22:25:08 GMT Date: Wed, 6 May 2009 15:25:07 -0700 (PDT) From: Sri Gundavelli To: McCann Peter-A001034 In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=665; t=1241648708; x=1242512708; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=sgundave@cisco.com; z=From:=20Sri=20Gundavelli=20 |Subject:=20Re=3A=20[Mip4]=20Recharter=3A=20Multicast/Broad cast=20Support |Sender:=20; bh=UlVQ9fVPVpgxFFnGCkVwfhwEyxCDjzIOUiQRqMsSBbw=; b=pFZAdj9/wUHmTnDpO5byaAEHHiKv/K+QwdBYFx4iKP3UAuq0HscovSvRRR 82eifYJO0xchWWvz5YKazhjAYrOmevVUHH7uIfLTtgRHQt/tYgljSYjH4Thf gvj9L0qavXNKKkxtSNITjqR2IXf7bamwvIlsxmA6QGRigf1wgpVZY=; Authentication-Results: sj-dkim-1; header.From=sgundave@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); Cc: mip4@ietf.org, Henrik Levkowetz Subject: Re: [Mip4] Recharter: Multicast/Broadcast Support X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 22:23:41 -0000 I support this optimization work. On Tue, 5 May 2009, McCann Peter-A001034 wrote: > Hi, all, > > This is a call for consensus to see whether we want to adopt > the IPv4 Mobility Extension for Multicast and Broadcast Packets, > as described in the following draft: > > draft-chakrabarti-mip4-mcbc-03.txt > > Please respond with a message stating whether you support or oppose > this action, and your reasons why. > > -Pete > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > From kleung@cisco.com Thu May 7 08:50:35 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B095A3A6CD2 for ; Thu, 7 May 2009 08:50:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.598 X-Spam-Level: X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ood8sKiwGSoj for ; Thu, 7 May 2009 08:50:34 -0700 (PDT) Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 1641128C16D for ; Thu, 7 May 2009 08:49:52 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.40,311,1238976000"; d="scan'208";a="300273108" Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 07 May 2009 15:51:11 +0000 Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n47FpBvo015248; Thu, 7 May 2009 08:51:11 -0700 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n47FpBZf008239; Thu, 7 May 2009 15:51:11 GMT 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); Thu, 7 May 2009 08:51:10 -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 Date: Thu, 7 May 2009 08:51:10 -0700 Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5208B6AB52@xmb-sjc-235.amer.cisco.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Recharter: Multiple Tunnel Support Thread-Index: AcnNmNDbMcuRI+dXQmaJ8g/mqcFpSgBknv9A References: From: "Kent Leung (kleung)" To: "McCann Peter-A001034" , X-OriginalArrivalTime: 07 May 2009 15:51:10.0987 (UTC) FILETIME=[A4A945B0:01C9CF2B] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1130; t=1241711471; x=1242575471; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=kleung@cisco.com; z=From:=20=22Kent=20Leung=20(kleung)=22=20 |Subject:=20RE=3A=20[Mip4]=20Recharter=3A=20Multiple=20Tunn el=20Support |Sender:=20; bh=EnicDLjSBgzZcG2WIRmGntECAofIKpLTQ4b7TywjfwA=; b=G32YjHOrAT9ccWiHa9ZfvJ5E+HfGxvpRUuRO/2S9as5h6cDkf0WbcXhVy+ x5suyZW5LnwIpPj9axRaSHbrsi+R/LBMAzvP03M0/payZCRyxlbPzOo90Y+W RbpHGcxsMI; Authentication-Results: sj-dkim-3; header.From=kleung@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); Cc: Henrik Levkowetz Subject: Re: [Mip4] Recharter: Multiple Tunnel Support X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2009 15:50:35 -0000 I support this work item because multiple tunnel support is a real-world use case. Kent=20 -----Original Message----- From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of McCann Peter-A001034 Sent: Tuesday, May 05, 2009 8:48 AM To: mip4@ietf.org Cc: Henrik Levkowetz Subject: [Mip4] Recharter: Multiple Tunnel Support Hi, all, During our meeting at IETF74, we discussed whether to take on the multiple tunnel support and flow movement, as described in these two drafts: draft-gundavelli-mip4-multiple-tunnel-support-00.txt draft-tsirtsis-mip4-flowmove-01.txt The sense of the room seemed to be that we should combine these two drafts and take the result on as a new work item. This message is a request to confirm/reject this approach. Please respond to this e-mail with an indication of whether you agree or disagree, and state your reasons why. -Pete =20 -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From kleung@cisco.com Thu May 7 08:52:46 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 439483A6F4E for ; Thu, 7 May 2009 08:52:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q4B4FDnx2JrS for ; Thu, 7 May 2009 08:52:43 -0700 (PDT) Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 3817C3A722F for ; Thu, 7 May 2009 08:50:53 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.40,311,1238976000"; d="scan'208";a="159807210" Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-3.cisco.com with ESMTP; 07 May 2009 15:52:11 +0000 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/8.12.11) with ESMTP id n47FqBBi030356; Thu, 7 May 2009 08:52:11 -0700 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n47FqBGg024800; Thu, 7 May 2009 15:52:11 GMT 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); Thu, 7 May 2009 08:52:11 -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 Date: Thu, 7 May 2009 08:52:11 -0700 Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5208B6AB5A@xmb-sjc-235.amer.cisco.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Recharter: GRE Key Extension Thread-Index: AcnNmPTE2kgpVqDgSiqJIzRK5XZG1ABkroRA References: From: "Kent Leung (kleung)" To: "McCann Peter-A001034" , X-OriginalArrivalTime: 07 May 2009 15:52:11.0348 (UTC) FILETIME=[C8A3A140:01C9CF2B] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1052; t=1241711531; x=1242575531; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=kleung@cisco.com; z=From:=20=22Kent=20Leung=20(kleung)=22=20 |Subject:=20RE=3A=20[Mip4]=20Recharter=3A=20GRE=20Key=20Ext ension |Sender:=20; bh=gqyR0nI4zgCd3rc9wRJCBMrLF+on6blmmb7yEr42pBo=; b=QMT1BrpEpGLmIUMpBHEqpSDl9b9LY9M5Ho+NFtvoO3UBBzz2cZxhPsIIul 4ZU5OtUTVHWBT0i6GPC510T4PtPINTJzM8wWiEZ7eiymwYZ7EkQvT5bTRwN9 Kc6e2clqxO; Authentication-Results: sj-dkim-4; header.From=kleung@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); Cc: Henrik Levkowetz Subject: Re: [Mip4] Recharter: GRE Key Extension X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2009 15:52:46 -0000 I support this work item because it is used/required by other SDOs.=20 Kent -----Original Message----- From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of McCann Peter-A001034 Sent: Tuesday, May 05, 2009 8:49 AM To: mip4@ietf.org Cc: Henrik Levkowetz Subject: [Mip4] Recharter: GRE Key Extension Hi, all, During our meeting at IETF74, we discussed whether to take on a draft describing how to negotiate GRE Keys for when GRE tunneling is used with Mobile IPv4, as described in this draft: draft-yegani-gre-key-extension-03.txt The sense of the room was that we should adopt this draft as a new work item. This message is a request to confirm/reject this approach. Please respond to this e-mail with an indication of whether you agree or disagree, and state your reasons why. -Pete -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From kleung@cisco.com Thu May 7 09:02:38 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 935CD28C2E0 for ; Thu, 7 May 2009 09:02:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4GymDZaE2siE for ; Thu, 7 May 2009 09:02:37 -0700 (PDT) Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id EA88D28C2ED for ; Thu, 7 May 2009 09:02:22 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.40,311,1238976000"; d="scan'208";a="182308279" Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-1.cisco.com with ESMTP; 07 May 2009 16:03:51 +0000 Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n47G3m3i025016; Thu, 7 May 2009 09:03:48 -0700 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n47G3mMY023442; Thu, 7 May 2009 16:03:48 GMT Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 7 May 2009 09:03:48 -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 Date: Thu, 7 May 2009 09:03:46 -0700 Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5208B6AB72@xmb-sjc-235.amer.cisco.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Recharter: Host Configuration Thread-Index: AcnNmQynkZb31cBSTDSBN90Fs1Ht5gBk0LCA References: From: "Kent Leung (kleung)" To: "McCann Peter-A001034" , X-OriginalArrivalTime: 07 May 2009 16:03:48.0005 (UTC) FILETIME=[67E10D50:01C9CF2D] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2125; t=1241712231; x=1242576231; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=kleung@cisco.com; z=From:=20=22Kent=20Leung=20(kleung)=22=20 |Subject:=20RE=3A=20[Mip4]=20Recharter=3A=20Host=20Configur ation |Sender:=20; bh=9HY3PKUFGTYnuEKWRyySB/EmmdigvJjC72n7JAhJJIk=; b=sWgWuFCqSPhKbZgH+xJJN8/3dZ6TxKha0OJ40hWMrQN0eFy7P2psVJ50VO jyX+iHizWIJ3PZ94qJVVBRPnIh+FeDqUqW9rk8EQ/GcgS0Kcx0wHtxFc6vBv 236HnFVbaM; Authentication-Results: sj-dkim-2; header.From=kleung@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); Cc: Henrik Levkowetz Subject: Re: [Mip4] Recharter: Host Configuration X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2009 16:02:38 -0000 I support a work item for host configuration. George's proposal should be studied further. Kent=20 -----Original Message----- From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of McCann Peter-A001034 Sent: Tuesday, May 05, 2009 8:49 AM To: mip4@ietf.org Cc: Henrik Levkowetz Subject: [Mip4] Recharter: Host Configuration Hi, all, During our meeting at IETF74, we discussed the way forward for host configuration with Mobile IPv4. On the table are the following drafts: draft-ietf-mip4-gen-ext-04.txt draft-deng-mip4-host-configuration-00.txt draft-chakrabarti-mip4-mcbc-03.txt There was an involved discussion during the meeting on what to do. The point was raised that some SDOs are already extending mip4 with VSEs to do host configuration, and that some support is needed for non-DHCP clients. Issues with the handling of the broadcast DHCPDISCOVER on the home link were also raised, and some people thought that the current specifications would require the home agent to relay every DHCPDISCOVER to every connected mobile node. This clearly would be unacceptable. However, we don't want to go creating too many mechanisms for host configuration that would require maintenance of mip4 every time we add a new configuration option. One proposal put forth by George at the meeting was to do one extension to mip4 to carry a unicast address of a DHCP server, and then run DHCPINFORM directly between the mobile host and that server using unicast messages. Is this the most viable way forward? Please respond to this note with a message saying whether you agree/disagree with this approach, and state your reasons why. Note that there was also support for the multicast-broadcast enhancement draft independent of DHCP. I will create a separate thread to discuss whether to take on that work in our rechartering effort. -Pete -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ From sunseawq@huawei.com Mon May 11 18:17:34 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 399F63A6807 for ; Mon, 11 May 2009 18:17:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.473 X-Spam-Level: X-Spam-Status: No, score=-0.473 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0dDCEVneGsEA for ; Mon, 11 May 2009 18:17:33 -0700 (PDT) Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 80ED73A69D3 for ; Mon, 11 May 2009 18:17:00 -0700 (PDT) Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJI002JVBMKPE@szxga03-in.huawei.com> for mip4@ietf.org; Tue, 12 May 2009 09:18:21 +0800 (CST) Received: from huawei.com ([172.24.1.33]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJI001XKBMKT0@szxga03-in.huawei.com> for mip4@ietf.org; Tue, 12 May 2009 09:18:20 +0800 (CST) Received: from w53375 ([10.164.12.38]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KJI00LLGBMJU1@szxml06-in.huawei.com> for mip4@ietf.org; Tue, 12 May 2009 09:18:20 +0800 (CST) Date: Tue, 12 May 2009 09:18:18 +0800 From: Qin Wu To: mip4@ietf.org Message-id: <004701c9d29f$88afdeb0$260ca40a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Outlook Express 6.00.2900.3138 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <20090512010128.F0EF03A6A49@core3.amsl.com> Cc: shah.rahman@ericsson.com Subject: Re: [Mip4] New Version Notification for draft-wu-mip4-ether-02 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 May 2009 01:17:34 -0000 Hi, Folks: Just for your information, We have just posted the second version of the Internet Draft on ethernet service transport over MIP as Shah's comments. http://www.ietf.org/internet-drafts/draft-wu-mip4-ether-02.txt Thank for Shah's valuable input. Also for anybody who is interested in this topic, your comments and suggestions are welcome! Regards! -Qin ----- Original Message ----- From: "IETF I-D Submission Tool" To: Cc: ; ; Sent: Tuesday, May 12, 2009 9:01 AM Subject: New Version Notification for draft-wu-mip4-ether-02 > > A new version of I-D, draft-wu-mip4-ether-02.txt has been successfuly submitted by Wenson Wu and posted to the IETF repository. > > Filename: draft-wu-mip4-ether > Revision: 02 > Title: MIP Extension for Ethernet Service transport Support > Creation_date: 2009-05-12 > WG ID: Independent Submission > Number_of_pages: 12 > > Abstract: > The IP Mobility Protocol [RFC3344] enables a mobile node maintain IP > connectivity when it changes its location. However, it is not enough > to enable the node to maintain L2 connectivity between mobile node > and Ethernet service provider in order to support Ethernet service > transport. This document describes "Ethernet Service Transport" > mobility option for mobile IPv4 that is intended to assist home agent > tunnel Ethernet packets from the home link to the FA on the foreign > link during the datagram delivery process. > > > > The IETF Secretariat. > > > From plattner@tik.ee.ethz.ch Fri May 15 06:07:32 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6368E3A6BD7 for ; Fri, 15 May 2009 06:07:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qfgYlGjVpzzo for ; Fri, 15 May 2009 06:07:32 -0700 (PDT) Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by core3.amsl.com (Postfix) with ESMTP id 25FA83A6B44 for ; Fri, 15 May 2009 06:07:31 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 641D7D93D4 for ; Fri, 15 May 2009 15:09:04 +0200 (MEST) X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 0FEQ7-EJIqTK for ; Fri, 15 May 2009 15:09:04 +0200 (MEST) Received: from tik44x.ee.ethz.ch (tik44x.ee.ethz.ch [129.132.67.137]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 35B6BD93CF for ; Fri, 15 May 2009 15:09:04 +0200 (MEST) Received: by tik44x.ee.ethz.ch (Postfix, from userid 9250) id 2529A1386E93; Fri, 15 May 2009 15:09:04 +0200 (CEST) To: mip4@ietf.org Message-Id: <20090515130904.2529A1386E93@tik44x.ee.ethz.ch> Date: Fri, 15 May 2009 15:09:04 +0200 (CEST) From: plattner@tik.ee.ethz.ch (Bernhard Plattner) X-Mailman-Approved-At: Fri, 15 May 2009 08:12:07 -0700 Subject: [Mip4] Call for Papers - 4th International Workshop on Self-Organizing Systems (IWSOS 2009) X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 May 2009 13:18:18 -0000 CALL FOR PAPERS IWSOS 2009 - 4th International Workshop on Self-Organizing Systems December 9-11, 2009, ETH Zurich, Zurich, Switzerland http://iwsos2009.ethz.ch Workshop Scope IWSOS 2009 is the fourth workshop in a series of annual workshops dedicated to self-organization in networks and networked systems. The necessity for and expected benefit of self-organization is caused by the growing scale, complexity, and heterogeneity of future networked systems, like the future Internet. Future networks will form complex networks integrating wired and wireless infrastructures with mobile ad-hoc, and sensor networks that could be spontaneously deployed in hostile environments, have a dynamic population and a potentially short life time. In spite of this, there will be stringent user requirements, such as high availability and real-time guarantees. Although self-organization is desirable for these kinds of networks, it is not yet clear to what extent self-organization can be exploited. Research into networked systems started a few years ago to systematically investigate self-organization and has lead to a multitude of open research issues. The applicability of well-known self-organizing techniques to specific networks and networked systems is being investigated, as well as adaptations and novel approaches inspired by cooperation in nature and evolutionary dynamics, sociology, and game theory. Additionally, models originating from areas like control theory and complex systems research, are being applied to networked systems to analyze their controllability and behavior. Aspects of engineering self-organizing networked systems are studied that draw on approaches like programmable networks, and tools and frameworks for deploying, testing, and monitoring self-organizing networks. The role of self-organization in the future Internet and the impact on its architecture is an important topic, as well as the application of self-organization in future intelligent tra nsportation systems and vehicular ad-hoc networks. Building on the success of its predecessors, this workshop aims at bringing together leading international researchers to create a visionary forum for discussing the future of self-organization in networked systems. Topics include, but are not limited to the following. Key Topics * Self-organization and self-management * Self-configuration and self-optimization * Self-protection, -diagnosis, and -healing * Self-organizing Networks and networked systems * Autonomic networking principles and practice * Control theory based models and approaches to self-organization * Group-forming networks and techniques * Programmable and cognitive networks as a basis for self-organization * Visualization of network state * Inspiring models of self-organization in nature and society (e.g., bio-inspired or based on game theory) * Self-organization for Quality of Service * Resilience, robustness and fault tolerance for networked systems * Security in self-organizing networked systems * Self-organization in peer-to-peer, sensor and ad-hoc networks * Self-organization for ubiquitous computing * Self-organization in heterogeneous network convergence * Evolutionary principles of the (future, emerging) Internet * Self-configuring place-and-play mobile networks * Self-organizing vehicular ad-hoc networks * Methods for configuration and management of large, complex networks * Applications, e.g. the self-organizing home network * Risks of self-organization * The human in the loop of self-organizing networks Paper Submission IWSOS invites submission of manuscripts as full or short papers that present original research results, and that have not been previously published or are currently under review by another conference or journal. Any previous or simultaneous publication of related material should be explicitly noted in the submission. All papers must be submitted in PDF format. Submissions will be peer reviewed by at least three members of the international TPC and judged on originality, significance, interest, clarity, relevance, and correctness. Full Papers Submissions should be full-length papers up to 12 pages using the LNCS style, including all figures and references, and must include an abstract of 100-150 words. Short Papers Submissions should be position papers, challenging papers, and papers presenting first or late results up to 6 pages length (LNCS style, including all figures and references), and must include an abstract of 100-150 words. Accepted Papers The proceedings will be published by Springer-Verlag in their Lecture Notes in Computer Science (LNCS) series. At least one of the authors of each accepted paper must attend IWSOS 2009 to present the paper. Posters and Demonstrations To complement the main technical programme of IWSOS 2009, we are soliciting extended abstracts (up to two pages, LNCS style) that describe posters and demonstrations that will be presented at an informal session during the workshop. This session should provide a platform to present and discuss work-in-progress and demonstrations. The abstracts will be collected and made available at the event. Important Dates Full Paper submission deadline: July 10, 2009 Notification of acceptance: September 12, 2009 Short Paper submission deadline: August 14, 2009 Notification of acceptance: September 12, 2009 Poster submission deadline: October 16, 2009 Notification of acceptance: October 30, 2009 Camera-ready papers due: September 30, 2009 Early registration ends: October 6, 2009 (except for poster authors) From sunseawq@huawei.com Mon May 18 19:09:15 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AE7D13A708E for ; Mon, 18 May 2009 19:09:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.231 X-Spam-Level: X-Spam-Status: No, score=0.231 tagged_above=-999 required=5 tests=[AWL=-0.763, BAYES_05=-1.11, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GOjzfJE9VZ8v for ; Mon, 18 May 2009 19:09:14 -0700 (PDT) Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 9A94C28C1C3 for ; Mon, 18 May 2009 19:09:14 -0700 (PDT) Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJV00623CPR7I@szxga01-in.huawei.com> for mip4@ietf.org; Tue, 19 May 2009 10:10:40 +0800 (CST) Received: from huawei.com ([172.24.1.24]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJV00GOPCPRUQ@szxga01-in.huawei.com> for mip4@ietf.org; Tue, 19 May 2009 10:10:39 +0800 (CST) Received: from w53375 ([10.164.12.38]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KJV005DSCPOQ7@szxml04-in.huawei.com> for mip4@ietf.org; Tue, 19 May 2009 10:10:39 +0800 (CST) Date: Tue, 19 May 2009 10:10:35 +0800 From: Qin Wu To: Christian Makaya , mip4@ietf.org Message-id: <033901c9d826$ff374960$260ca40a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Outlook Express 6.00.2900.3138 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <005f01c9cde7$000cfb40$260ca40a@china.huawei.com> <4A11862A.6090106@research.telcordia.com> Cc: Shahriar Rahman , 'Hui Deng' Subject: Re: [Mip4] Fw: Recharter: Ethernet Service Support X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2009 02:09:15 -0000 Hi, Christian: Thank for your feedback. Just let you know, we have already updated the version 2. As regarding your comments, please see my reply below. > Below, you'll find some comments based on my review of your I-D > draft-wu-mip4-ether-01.txt: > > Introduction: > > Remove the r: "The capability .......service providers to _provide_ IP > services ..." [Qin]: Right, there appears to be a typo here, thanks you for pointing out this. > Third bullet: ISP-head _and_ to enable > > Last paragraph: "... home address assignment _policies_ and tunnel ... > can be operated _in_ parallel to ..." [Qin]: Right, good catch. > Terminology: > > GRE Extension: check: _to differentiate between *difference* Ethernet_ > ... Not clear what you mean. [Qin]: I actually said GRE extension can be used to differentiate between different Ethernet service based on GRE keys. Here is a nits, thank you for pointing out this. > Section 3.3 > > VLAN tags process in _both direction_ towards ... [Qin]: It is okay with me, I can change bidirection into both direction. > Section 4.2 > " ... the communication between the MN and the home agent needs to be > modified to support Ethernet frame network..." This statement maybe > difficult in order to sell your proposal. [Qin] You are right. We could add some text to say: " In order to support Ethernet service delivery in mobile IPv4 scenario, the communication between the MN and the home agent needs to be modified to setup binding between MN's MAC address and FA CoA. " What do you think of it? > I do not understand what do you mean by: "host behind the MN" is it a > router/IP node? MN is one of the end-point of communication path. Which > node/host is behind MN? [Qin]: What I mean here is in multi-host support scenario(please see the section 3.4 of this draft), there are multiple mobile devices connected to the bridge behind Mobile Router. The mobile router contains a bridge forwarding to the mobile devices behind the MR. The traffic sent from the mobile device should be forwarded by the Mobile Router to the Ethernet sevice provider. In this scenario, the MN is the mobile router and not a end point of communication path. The mobile device behind the mobile router is the real end point of communication path. > Section 6.2 > _to differentiate between *difference* Ethernet_ services or flows... > Not clear what you mean. [Qin]: It is a typo, the difference should be changed into different, thank you for correcting me. > Last sentence: "... Wu Expires ....", formatting issue, need to check. > > Section 7.2 > > Home Agent Operatio_*n > *_Best regards, > Christian_* > *_ From kaishos@gmail.com Tue May 19 06:14:56 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 376543A6E5E; Tue, 19 May 2009 06:14:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.109 X-Spam-Level: X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VmSlxjX3MCWp; Tue, 19 May 2009 06:14:55 -0700 (PDT) Received: from mail-fx0-f158.google.com (mail-fx0-f158.google.com [209.85.220.158]) by core3.amsl.com (Postfix) with ESMTP id D40E03A6B3D; Tue, 19 May 2009 06:14:54 -0700 (PDT) Received: by fxm2 with SMTP id 2so3863559fxm.37 for ; Tue, 19 May 2009 06:16:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=P3oBl+3mt2ANVqYARvd3uU2+9arX6sM9ISNsYWsQt3U=; b=F04NerNSjps7n89Dq9gLAEnWVXLw7ZP2uiJltRYkUfs/js+ARcSrZVOUXOXWZ5kfGj AFggb48JesnIzcBB1pDK6MNTfST14DbzaIe8Ws1gshJwqnnct65ywyDoHfFsJ5WZ+S6L hzC5tLyQtUB9skydHmfDjIKgikG7z4dRnjBes= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=lWE8zwI7aIQEZm+iePAyfvyhNO27kJ/OhNRxcwi8OwdhBBH+IJ9+4zZYQlXuVHwqSm 5xlVqg3+ax+xLhJNwLLezq/ZTYbAqvVad8ESy5nHTsNSWCVuH7K4ExCQE2XctOZR44r9 IsS1L3s9WtJ2Pg/AYSiF1TGIdaHj/HSz3J5I0= MIME-Version: 1.0 Received: by 10.204.70.135 with SMTP id d7mr47940bkj.87.1242738988721; Tue, 19 May 2009 06:16:28 -0700 (PDT) Date: Tue, 19 May 2009 15:16:28 +0200 Message-ID: <5819563d0905190616m34ba5111hd435408c3c1f3efb@mail.gmail.com> From: KKloe Kaishoto To: mip4@ietf.org, mip6@ietf.org Content-Type: multipart/alternative; boundary=001636c5a9e8f8a841046a43b7cb X-Mailman-Approved-At: Tue, 19 May 2009 07:30:15 -0700 Subject: [Mip4] Initial handshake X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2009 13:17:07 -0000 --001636c5a9e8f8a841046a43b7cb Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hallo, my name is Pablo and I am wondering how a mobile establishes a connection to a correspondent node, I am guessing it uses the ordinary TCP/IP three way handshake but I am wondering if there is somewhere more specified how the packages are composed if they are anything special with them when using Mobile IPv4 or Mobile IPv6? --001636c5a9e8f8a841046a43b7cb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hallo, my name is Pablo and I am wondering how a mobile establishes a conne= ction to a correspondent node, I am guessing it uses the ordinary TCP/IP th= ree way handshake but I am wondering if there is somewhere more specified h= ow the packages are composed if they are anything special with them when us= ing Mobile IPv4 or Mobile IPv6?
--001636c5a9e8f8a841046a43b7cb-- From charles.perkins@earthlink.net Tue May 19 09:21:19 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 00C6A28C0FB; Tue, 19 May 2009 09:21:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.392 X-Spam-Level: X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[AWL=1.207, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FIDhQSL1M7bs; Tue, 19 May 2009 09:21:17 -0700 (PDT) Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by core3.amsl.com (Postfix) with ESMTP id 60EF33A6A93; Tue, 19 May 2009 09:20:43 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=HE/k0N91TKilEuPsMvkq6mWCCuNan972Ea4evhlmIN08PqO095rNbu6ZkW+GG8Zh; h=Received:Message-ID:Date:From:Organization:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [38.96.10.141] (helo=[192.168.1.100]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1M6S55-0000yR-Kx; Tue, 19 May 2009 12:22:19 -0400 Message-ID: <4A12DCBA.3010305@earthlink.net> Date: Tue, 19 May 2009 09:22:18 -0700 From: "Charles E. Perkins" Organization: Wichorus Inc. User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: KKloe Kaishoto References: <5819563d0905190616m34ba5111hd435408c3c1f3efb@mail.gmail.com> In-Reply-To: <5819563d0905190616m34ba5111hd435408c3c1f3efb@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956abb457f1b4332f52f11a20e13c92aeb5f46c40a6a2bb307b350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 38.96.10.141 Cc: mip6@ietf.org, mip4@ietf.org Subject: Re: [Mip4] Initial handshake X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2009 16:21:19 -0000 Hello Pablo, Mobile IPv* is specifically constructed so that TCP (or any other transport protocol that would normally be carried by IP) will work without any knowledge of Mobile IP. So UDP, SCTP, ICMP, all should just work. Regards, Charlie P. KKloe Kaishoto wrote: > Hallo, my name is Pablo and I am wondering how a mobile establishes a > connection to a correspondent node, I am guessing it uses the ordinary > TCP/IP three way handshake but I am wondering if there is somewhere > more specified how the packages are composed if they are anything > special with them when using Mobile IPv4 or Mobile IPv6? > ------------------------------------------------------------------------ > > -- > Mip4 mailing list: Mip4@ietf.org > Web interface: https://www.ietf.org/mailman/listinfo/mip4 > Charter page: http://www.ietf.org/html.charters/mip4-charter.html > Supplemental site: http://www.mip4.org/ > From jules@dcs.gla.ac.uk Wed May 20 09:10:33 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA52F3A6B62; Wed, 20 May 2009 09:10:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.998 X-Spam-Level: X-Spam-Status: No, score=-3.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5cnqkfsRS3KI; Wed, 20 May 2009 09:10:25 -0700 (PDT) Received: from mr1.dcs.gla.ac.uk (mr1.dcs.gla.ac.uk [130.209.249.184]) by core3.amsl.com (Postfix) with ESMTP id 59B233A6A74; Wed, 20 May 2009 09:10:24 -0700 (PDT) Received: from vpn3.dcs.gla.ac.uk ([130.209.254.3]:53564) by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42) id 1M6oNn-0002Fc-Ex; Wed, 20 May 2009 17:11:08 +0100 Message-Id: From: Julie Maitland To: Julie Maitland Content-Type: multipart/alternative; boundary=Apple-Mail-18-388174720 Mime-Version: 1.0 (Apple Message framework v930.3) Date: Wed, 20 May 2009 17:11:03 +0100 X-Mailer: Apple Mail (2.930.3) X-Mailman-Approved-At: Fri, 22 May 2009 07:46:37 -0700 Subject: [Mip4] CfP: 4th International Conference on Pervasive Computing Technologies for Healthcare 2010 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 May 2009 16:17:03 -0000 --Apple-Mail-18-388174720 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Apologies if you receive multiple copies of this call due to cross posting. Please feel free to distribute to others who might be interested. **** Call for Papers **** 4th International Conference on Pervasive Computing Technologies for Healthcare 2010 http://www.pervasivehealth.org March 22nd-25th 2010, Munich, Germany Pervasive healthcare is an emerging research discipline, focusing on the development and application of pervasive and ubiquitous computing technology for healthcare and wellness. Pervasive healthcare seeks to respond to a variety of pressures on healthcare systems, including the increased incidence of life-style related and chronic diseases, emerging consumerism in healthcare, need for empowering patients and relatives for self-care and management of their health, and need to provide seamless access for health care services, independent of time and place. Pervasive healthcare may be defined from two perspectives. First, it is the development and application of pervasive computing (or ubiquitous computing, ambient intelligence) technologies for healthcare, health and wellness management. Second, it seeks to make healthcare available to anyone, anytime, and anywhere by removing locational, time and other restraints while increasing both the coverage and quality of healthcare. The Pervasive Healthcare conference aims to gather together technology experts, practitioners, industry and national authorities contributing towards the development and application of human-centered pervasive and ubiquitous computing technology for healthcare and wellness. *** CONTRIBUTIONS *** We seek novel, innovative, and exciting work in areas including but not limited to: Technology * Design and evaluation of patient and ambient-related sensors * Wearable and implantable sensor integration * Energy management and harvesting * Sensor networks for pervasive healthcare * Data fusion in pervasive healthcare environments * Physiological models for interpreting medical sensor data * Decision support algorithms for sensor data analysis * Human to machine interfaces User Needs * Usability and acceptability issues * Social implications * Coverage and delivery of pervasive healthcare services * Cognitive deficits (mild cognitive impairment, dementia,...) * Physical deficits (mobility,...) * Vegetative deficits (incontinence, adipositas, cardiovascular diseases,...) * Telemedicine Applications * Clinical applications, validation and evaluation studies * Pervasive healthcare applications for citizen for chronic disease management & health risk management * Health promotion, and disease prevention * Wearable, ambient and home based health and wellness measurement and monitoring technologies * Continuous vs event-driven monitoring of patients in diverse environments * Health interfaces, information visualisation and feedback * Health-related ICT for Development * Assistive Devices for temporal and spatial orientation * Activity recognition and fall detection * Entertainment, educational and motivational aids Management of Pervasive Healthcare * Business cases and cost issues * Electronic citizen-managed health records * Security and privacy in pervasive healthcare * Training of healthcare professional for pervasive healthcare * Legal and regulatory issues in pervasive healthcare * Insurance payments and cost aspects * Standards and interoperability in pervasive healthcare * Using mobile devices for healthcare information storage, update, and transmission *** TYPE OF SUBMISSIONS *** Pervasive Health will accept submissions in the following categories: 1 Full papers (up to 8 pages submissions) - Full papers are submissions describing results and original research work not submitted or published elsewhere in one of the four main categories listed below. Full papers should properly place the work within the field, cite related work, and clearly indicate the innovative aspects of the work and its contribution to the field. 2 Posters (up to 4 pages submissions) - Authors are invited to submit work in progress whose preliminary results are already interesting to Pervasive Health audience. The poster track will give Pervasive Health attendees a way to learn about ongoing research initiatives and will provide presenters with an excellent opportunity to receive invaluable direct feedback from experts. 3 Demos and Videos (2 pages submissions) - For the first time, Pervasive Health Conference proposes a demos and videos track that will showcase the latest developments and prototypes related to the topics of interest of the conference. The expected submissions should describe the demo from both, the technical side and its contribution to healthcare aspects 4 Workshop Proposals A separate Call for Workshops will be issued in due course. Please check conference website (http://www.pervasivehealth.org). All accepted submissions will be published in IEEE Xplore Digital Library. *** IMPORTANT DATES **** All Papers Categories Submissions: December 4, 2009 Notification of Acceptance: February 8, 2010 Camera-ready Manuscripts due: February 26, 2010 Conference Dates: March 22-25, 2010 *** WORKSHOPS *** Please visit the Workshops pages for detailed submission requirements and procedures. *** SUBMISSION INSTRUCTIONS *** Please visit the Submission page for detailed submission requirements and procedures. http://www.pervasivehealth.org/submission.shtml *** PUBLICATION *** Please visit the Publications page for more information. http://www.pervasivehealth.org/publication.shtml __________________________ Julie Maitland Social/Ubiquitous/Mobile Group Department of Computer Science University of Glasgow phone: +44 141 330 2333 web: http://www.dcs.gla.ac.uk/~jules 'Dream as if you'll live forever, live as if you'll die today' - James Dean --Apple-Mail-18-388174720 Content-Type: multipart/mixed; boundary=Apple-Mail-19-388174723 --Apple-Mail-19-388174723 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable
Apologies if you receive = multiple copies of this call due to cross posting.
Please feel = free to distribute to others who might be = interested. 

**** Call for Papers = ****

4th International Conference on Pervasive = Computing Technologies for Healthcare = 2010


March 22nd-25th 2010, Munich, = Germany


Pervasive healthcare is = an emerging research discipline, focusing on the development and = application of pervasive and ubiquitous computing technology for = healthcare and wellness. Pervasive healthcare seeks to respond to a = variety of pressures on healthcare systems, including the increased = incidence of life-style related and chronic diseases, emerging = consumerism in healthcare, need for empowering patients and relatives = for self-care and management of their health, and need to provide = seamless access for health care services, independent of time and = place. 

Pervasive healthcare may be = defined from two perspectives. First, it is the development and = application of pervasive computing (or ubiquitous computing, ambient = intelligence) technologies for healthcare, health and wellness = management. Second, it seeks to make healthcare available to anyone, = anytime, and anywhere by removing locational, time and other restraints = while increasing both the coverage and quality of = healthcare. 

The Pervasive Healthcare = conference aims to gather together technology experts, practitioners, = industry and national authorities contributing towards the development = and application of human-centered pervasive and ubiquitous computing = technology for healthcare and = wellness.


= *** CONTRIBUTIONS ***

We seek novel, = innovative, and exciting work in areas including but not limited = to:

Technology
* Design and = evaluation of patient and ambient-related sensors
* Wearable = and implantable sensor integration 
* Energy management = and harvesting 
* Sensor networks for pervasive = healthcare
* Data fusion in pervasive healthcare = environments
* Physiological models for interpreting medical = sensor data
* Decision support algorithms for sensor data = analysis 
* Human to machine = interfaces

User Needs
* Usability and = acceptability issues
* Social implications
* = Coverage and delivery of pervasive healthcare services
* = Cognitive deficits (mild cognitive impairment, = dementia,...) 
* Physical deficits = (mobility,...) 
* Vegetative deficits (incontinence, = adipositas, cardiovascular diseases,...) 
* = Telemedicine

Applications
* Clinical = applications, validation and evaluation studies
* Pervasive = healthcare applications for citizen for chronic disease management & = health risk management
* Health promotion, and disease = prevention
* Wearable, ambient and home based health and = wellness measurement and monitoring technologies
* Continuous = vs event-driven monitoring of patients in diverse = environments
* Health interfaces, information visualisation = and feedback 
* Health-related ICT for = Development
* Assistive Devices for temporal and spatial = orientation
* Activity recognition and fall = detection
* Entertainment, educational and motivational = aids

Management of Pervasive = Healthcare
* Business cases and cost issues
* = Electronic citizen-managed health records
* Security and = privacy in pervasive healthcare
* Training of healthcare = professional for pervasive healthcare
* Legal and regulatory = issues in pervasive healthcare
* Insurance payments and cost = aspects
* Standards and interoperability in pervasive = healthcare
* Using mobile devices for healthcare information = storage, update, and = transmission


= *** TYPE OF SUBMISSIONS ***

Pervasive = Health will accept submissions in the following = categories: 

1 Full papers (up to 8 pages = submissions) - Full papers are submissions describing results and = original research work not submitted or published elsewhere in one of = the four main categories listed below. Full papers should properly place = the work within the field, cite related work, and clearly indicate the = innovative aspects of the work and its contribution to the = field. 

2 Posters (up to 4 pages = submissions) - Authors are invited to submit work in progress whose = preliminary results are already interesting to Pervasive Health = audience. The poster track will give Pervasive Health attendees a way to = learn about ongoing research initiatives and will provide presenters = with an excellent opportunity to receive invaluable direct feedback from = experts. 

3 Demos and Videos (2 pages = submissions) - For the first time, Pervasive Health Conference proposes = a demos and videos track that will showcase the latest developments and = prototypes related to the topics of interest of the conference. The = expected submissions should describe the demo from both, the technical = side and its contribution to healthcare = aspects

4 Workshop Proposals
A = separate Call for Workshops will be issued in due course. Please check = conference website (http://www.pervasivehealth.org= ).



All accepted = submissions will be published in IEEE Xplore Digital = Library.


*** IMPORTANT DATES = ****
All Papers Categories Submissions: December = 4, 2009
Notification of Acceptance: = February 8, 2010
Camera-ready Manuscripts due: = February 26, 2010
Conference Dates: = March 22-25, 2010 
*** WORKSHOPS = ***
Please visit the Workshops pages for detailed submission = requirements and procedures.

*** SUBMISSION = INSTRUCTIONS ***
Please visit the Submission page for detailed = submission requirements and procedures.

*** = PUBLICATION ***
Please visit the Publications page for more = information.

= --Apple-Mail-19-388174723 Content-Disposition: attachment; filename=cfp2010.txt Content-Type: text/plain; x-unix-mode=0644; name="cfp2010.txt" Content-Transfer-Encoding: 7bit **** Call for Papers **** 4th International Conference on Pervasive Computing Technologies for Healthcare 2010 http://www.pervasivehealth.org March 22nd-25th 2010, Munich, Germany Pervasive healthcare is an emerging research discipline, focusing on the development and application of pervasive and ubiquitous computing technology for healthcare and wellness. Pervasive healthcare seeks to respond to a variety of pressures on healthcare systems, including the increased incidence of life-style related and chronic diseases, emerging consumerism in healthcare, need for empowering patients and relatives for self-care and management of their health, and need to provide seamless access for health care services, independent of time and place. Pervasive healthcare may be defined from two perspectives. First, it is the development and application of pervasive computing (or ubiquitous computing, ambient intelligence) technologies for healthcare, health and wellness management. Second, it seeks to make healthcare available to anyone, anytime, and anywhere by removing locational, time and other restraints while increasing both the coverage and quality of healthcare. The Pervasive Healthcare conference aims to gather together technology experts, practitioners, industry and national authorities contributing towards the development and application of human-centered pervasive and ubiquitous computing technology for healthcare and wellness. *** CONTRIBUTIONS *** We seek novel, innovative, and exciting work in areas including but not limited to: Technology * Design and evaluation of patient and ambient-related sensors * Wearable and implantable sensor integration * Energy management and harvesting * Sensor networks for pervasive healthcare * Data fusion in pervasive healthcare environments * Physiological models for interpreting medical sensor data * Decision support algorithms for sensor data analysis * Human to machine interfaces User Needs * Usability and acceptability issues * Social implications * Coverage and delivery of pervasive healthcare services * Cognitive deficits (mild cognitive impairment, dementia,...) * Physical deficits (mobility,...) * Vegetative deficits (incontinence, adipositas, cardiovascular diseases,...) * Telemedicine Applications * Clinical applications, validation and evaluation studies * Pervasive healthcare applications for citizen for chronic disease management & health risk management * Health promotion, and disease prevention * Wearable, ambient and home based health and wellness measurement and monitoring technologies * Continuous vs event-driven monitoring of patients in diverse environments * Health interfaces, information visualisation and feedback * Health-related ICT for Development * Assistive Devices for temporal and spatial orientation * Activity recognition and fall detection * Entertainment, educational and motivational aids Management of Pervasive Healthcare * Business cases and cost issues * Electronic citizen-managed health records * Security and privacy in pervasive healthcare * Training of healthcare professional for pervasive healthcare * Legal and regulatory issues in pervasive healthcare * Insurance payments and cost aspects * Standards and interoperability in pervasive healthcare * Using mobile devices for healthcare information storage, update, and transmission *** TYPE OF SUBMISSIONS *** Pervasive Health will accept submissions in the following categories: 1 Full papers (up to 8 pages submissions) - Full papers are submissions describing results and original research work not submitted or published elsewhere in one of the four main categories listed below. Full papers should properly place the work within the field, cite related work, and clearly indicate the innovative aspects of the work and its contribution to the field. 2 Posters (up to 4 pages submissions) - Authors are invited to submit work in progress whose preliminary results are already interesting to Pervasive Health audience. The poster track will give Pervasive Health attendees a way to learn about ongoing research initiatives and will provide presenters with an excellent opportunity to receive invaluable direct feedback from experts. 3 Demos and Videos (2 pages submissions) - For the first time, Pervasive Health Conference proposes a demos and videos track that will showcase the latest developments and prototypes related to the topics of interest of the conference. The expected submissions should describe the demo from both, the technical side and its contribution to healthcare aspects 4 Workshop Proposals A separate Call for Workshops will be issued in due course. Please check conference website (http://www.pervasivehealth.org). All accepted submissions will be published in IEEE Xplore Digital Library. *** IMPORTANT DATES **** All Papers Categories Submissions: December 4, 2009 Notification of Acceptance: February 8, 2010 Camera-ready Manuscripts due: February 26, 2010 Conference Dates: March 22-25, 2010 *** WORKSHOPS *** Please visit the Workshops pages for detailed submission requirements and procedures. *** SUBMISSION INSTRUCTIONS *** Please visit the Submission page for detailed submission requirements and procedures. http://www.pervasivehealth.org/submission.shtml *** PUBLICATION *** Please visit the Publications page for more information. http://www.pervasivehealth.org/publication.shtml --Apple-Mail-19-388174723 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable
__________________________

Julie = Maitland
Social/Ubiquitous/Mobile Group
Department = of Computer Science
University of = Glasgow

phone: +44 141 330 2333






= --Apple-Mail-19-388174723-- --Apple-Mail-18-388174720-- From kaishos@gmail.com Mon May 25 01:36:17 2009 Return-Path: X-Original-To: mip4@core3.amsl.com Delivered-To: mip4@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 18CAB3A68B5 for ; Mon, 25 May 2009 01:36:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.027 X-Spam-Level: X-Spam-Status: No, score=-1.027 tagged_above=-999 required=5 tests=[AWL=-0.843, BAYES_40=-0.185, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hZgr2aT-QibL for ; Mon, 25 May 2009 01:36:16 -0700 (PDT) Received: from mail-fx0-f168.google.com (mail-fx0-f168.google.com [209.85.220.168]) by core3.amsl.com (Postfix) with ESMTP id DB5E43A6D30 for ; Mon, 25 May 2009 01:35:58 -0700 (PDT) Received: by fxm12 with SMTP id 12so1162403fxm.37 for ; Mon, 25 May 2009 01:37:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=rlLw9SsA3+mJo9zs0kFBVqtC7egXEOClThaWSV4NV4o=; b=DVUNmzwBj8M+eG6eT0GEPQM3eUsLt4V+U4FetzaU21UsPa0pbCl5ZXe/uprJHAC/Td O11PrGhWKp8tgd2QcGqIpJS4gmx27QqvuSLaRHTErS9pTRQBBhLHrxIV/YUGO/J0XOuY mbI/trn7QdjBAp1ib1OY0P0o0/WvEyOHyY+m4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=UuScs1KDMnAZqb1A2u4xj6NB9v81H0UUGSaLwfwu8Nir/lWSb8RiHKWxOiBJaV7Mu9 9Cg/YrW2lFgmU7WRURC5fe9fxwLnGIWwIXr7zDo++9dWS55/wOz4GMkRPtB8PMpm+gxW ReROQsFxR0aEVuhGRLqiAGDDXNF8uqDd7j0zg= MIME-Version: 1.0 Received: by 10.204.101.71 with SMTP id b7mr6722540bko.156.1243240656996; Mon, 25 May 2009 01:37:36 -0700 (PDT) Date: Mon, 25 May 2009 10:37:36 +0200 Message-ID: <5819563d0905250137n70a64ce8i6dd9fc595c8fa0ac@mail.gmail.com> From: KKloe Kaishoto To: mip4@ietf.org Content-Type: multipart/alternative; boundary=0016e6de04e1bb0950046ab88556 X-Mailman-Approved-At: Tue, 26 May 2009 13:31:55 -0700 Subject: [Mip4] Current Implementation in companies X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 May 2009 08:36:17 -0000 --0016e6de04e1bb0950046ab88556 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hallo again, I was wondering if you know any company that have implemented this in their product and is in use in the private or public domain for mobile applications? --0016e6de04e1bb0950046ab88556 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hallo again, I was wondering if you know any company that have implemented this in their product and is in use in the private or public domain for mobile applications?
--0016e6de04e1bb0950046ab88556--