From mip4-bounces@ietf.org Sun Nov 05 22:22:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ggv49-0001SJ-GJ; Sun, 05 Nov 2006 22:22:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ggo0b-0003PN-31; Sun, 05 Nov 2006 14:50:21 -0500
Received: from listserv.acm.org ([63.118.7.46] helo=ozzie.acm.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Ggo0T-0007ql-He; Sun, 05 Nov 2006 14:50:21 -0500
Received: from ozzie (listserv.acm.org) by ozzie.acm.org (LSMTP for Windows NT
	v1.1b) with SMTP id <5.0023AC73@ozzie.acm.org>;
	5 Nov 2006 14:52:37 -0500
Received: by LISTSERV.ACM.ORG (LISTSERV-TCP/IP release 14.3) with spool id
	17605673 for SENSORNET@LISTSERV.ACM.ORG; Sun, 5 Nov 2006 14:52:24
	-0500
Received: from psmtp.com (exprod7mx70.postini.com) by ozzie.acm.org (LSMTP for
	Windows NT v1.1b) with SMTP id <5.0023AC71@ozzie.acm.org>; 5 Nov 2006
	14:52:24 -0500
Received: from source ([131.107.115.212]) (using TLSv1) by
	exprod7mx70.postini.com ([64.18.6.14]) with SMTP; Sun, 05 Nov 2006
	13:49:58 CST
Received: from mailout6.microsoft.com (157.54.69.150) by
	TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with
	Microsoft SMTP Server id 8.0.685.10; Sun, 5 Nov 2006 11:49:57 -0800
Received: from IGT-HUB-02.redmond.corp.microsoft.com ([157.54.69.153]) by
	mailout6.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830);  Sun, 5
	Nov 2006 11:49:57 -0800
Received: from TK5-EXHUB-C102.redmond.corp.microsoft.com ([157.54.70.72]) by
	IGT-HUB-02.redmond.corp.microsoft.com over TLS secured channel with
	Microsoft SMTPSVC(6.0.3790.1830);  Sun, 5 Nov 2006 11:49:57 -0800
Received: from NA-EXMSG-C105.redmond.corp.microsoft.com ([157.54.52.48]) by
	TK5-EXHUB-C102.redmond.corp.microsoft.com ([157.54.70.72]) with mapi;
	Sun, 5 Nov 2006 11:49:56 -0800
Thread-Topic: FW: IPSN'07 Last CFP (abstract due Monday, Nov. 6)
Thread-Index: AccBE5FPGcXpCF58TZiecgUzbzaY3w==
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 05 Nov 2006 19:49:57.0451 (UTC)
	FILETIME=[9256B1B0:01C70113]
Message-ID: <55E173F65C36D94DBCC89D904E3CB21D232A426621@NA-EXMSG-C105.redmond.corp.microsoft.com>
Date: Sun, 5 Nov 2006 11:49:55 -0800
From: Feng Zhao <zhao@MICROSOFT.COM>
To: SENSORNET@LISTSERV.ACM.ORG
Precedence: list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
X-Mailman-Approved-At: Sun, 05 Nov 2006 22:22:28 -0500
Cc: 
Subject: [Mip4] FW: IPSN'07 Last CFP (abstract due Monday, Nov. 6)
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Reply-To: Feng Zhao <zhao@MICROSOFT.COM>
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

The annual IPSN/SPOTS submission deadline is upon us again. I'd like to enc=
ourage you to wrap up some of your nice work on sensornet in the past year =
into a paper, and consider submitting it to either the IPSN or the SPOTS tr=
ack: http://www.cse.wustl.edu/ipsn07.html .

Hope to see many of you in Cambridge, Mass.


Feng

---------
Feng Zhao, Microsoft Research, One Microsoft Way, Redmond, WA 98052, tel. 4=
25-706-8777, fax 425-936-7329, zhao@microsoft.com, http://research.microsof=
t.com/~zhao


-----Original Message-----
From: ACM SIGBED SensorNet List [mailto:SENSORNET@LISTSERV.ACM.ORG] On Beha=
lf Of Ying Zhang
Sent: Friday, November 03, 2006 4:40 PM
To: SENSORNET@LISTSERV.ACM.ORG
Subject: IPSN'07 Last CFP (abstract due Monday, Nov. 6)

*Please note that the submission format for the full paper is:* *ACM SIG (t=
wo column, 9pt)*
*URL: http://www.acm.org/sigs/pubs/proceed/template.html*
Details of the submission are available at IPSN07 Website:
http://www.cse.wustl.edu/ipsn07.html

-Ying


-----------------------------------------------------------------------

CALL FOR PAPERS
The Sixth International Conference on
Information Processing in Sensor Networks (IPSN'07)

April 25 - 27, 2007 - Cambridge, Massachusetts, USA

The sixth International Conference on Information Processing in Sensor Netw=
orks (IPSN 2007) will continue the success of previous five symposia to bri=
ng together researchers from academia, industry, and government to present =
and discuss recent work in sensor network research and applications. IPSN d=
raws upon many disciplines including signal and image processing, informati=
on and coding theory, networking and protocols, distributed algorithms, wir=
eless communications, machine learning, embedded systems design, and databa=
ses and information management.

To further foster the collaboration between theory and practice, this confe=
rence will feature two interleaving tracks: IPSN, focusing more on informat=
ion processing algorithms,and SPOTS, focusing on platform tools and design =
methods for network embedded sensors.
In addition, IPSN'07 will feature a competition; details for rules and part=
icipation will be announced in the IPSN'07 competition website http://www.c=
s.virginia.edu/~whitehouse/ipsn07competition/.

Topics covered in IPSN sessions include, but are not limited to, the follow=
ing:

- Distributed & collaborative signal processing
- Network protocols for sensor networks
- Coding, compression & information theory
- Distributed query processing
- Detection, classification, estimation, tracking
- Sensor tasking and control
- Networked sensing and control
- In-network processing and aggregation
- Distributed control & actuation
- Distributed inference & fusion
- Fault tolerance
- Network coverage, connectivity & longevity
- Data storage in sensor networks
- Location and time services
- Energy and resource management
- Programming models and languages
- Real-time scheduling
- Security
- Application & demonstration of sensor networks

Topics covered in SPOTS sessions include, but are not limited to, the follo=
wing:

- Embedded networked sensor system platforms, platform modeling and analysi=
s tools
- Architectural design, modeling and optimization tools for sensor nodes an=
d networks
- Sensor node components and interfaces, middleware and system services
- Applications of embedded networked sensing with actual field deployments =
that highlight new themes in the design and operation of these complete sys=
tems.

Organization Committee

General Chair: Tarek Abdelzaher (University of Illinois at Urbana-Champaign=
), IPSN co-Chairs: Leo Guibas (Stanford University) and Matt Welsh (Harvard=
 University), SPOTS co-Chairs: Bill Kaiser (University of California at Los=
 Angles) and Ralph Kling (Crossbow), Competition Chair: Kamin Whitehouse (U=
niversity of Virginia), Demos Chair: Phil Levis (Stanford University), Fina=
nce Chair: John Heidemann (University of Southern California), Industry Spo=
nsorship Chair: Joe Hellerstein (University of California at Berkeley), Loc=
al Arrangements: Seth Teller (Massachusetts Institute of Technology), Poste=
r Chair: Haiyun Luo (University of Illinois at Urbana-Champaign), Publicati=
ons Chair: Bhaskar Krishnamachari (University of Southern California), Publ=
icity Chair: Ying Zhang (Palo Alto Research Center), Registration Chair: Ji=
e Liu (Microsoft Research), Web Chair: Chenyang Lu (Washington University i=
n St. Louis)


Location: Cambridge, MA (MIT Campus)

Important Dates:

Abstracts Due: Mon, Nov 6th, 2006
Papers Due: Mon, Nov 13th, 2006
Acceptance Decision: Mon, Jan 29th, 2007 Camera Ready: Fri, Feb 23rd, 2007
Conference: Wed-Fri, Apr. 25-27th, 2007

Website:

http://www.cse.wustl.edu/ipsn07.html

Submission Guidelines:

All papers will be submitted electronically, in Portable Document Format (P=
DF). Instructions for submission will be available at
IPSN'07 website: http://www.cse.wustl.edu/ipsn07.html.

Submission must meet the following criteria:
- A paper must be original material that has not been previously published =
nor is currently under review by another conference or journal.
- Submitted papers should be no longer than 10 pages in ACM two- column for=
mat for conferences.

Each paper will be reviewed by the Technical Programming Committee.
Accepted papers will appear in the conference proceedings. Following the IP=
SN tradition, an accepted paper will be presented either in the single-trac=
k session, or in the poster session, depending on its content not its quali=
ty.

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Mon Nov 06 11:35:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gh7Qy-0007Eb-EB; Mon, 06 Nov 2006 11:34:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GgyWV-0002VM-4W; Mon, 06 Nov 2006 02:03:59 -0500
Received: from birke.aot.cs.tu-berlin.de ([130.149.154.85]
	helo=mail.dai-labor.de) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GgyWP-0008Mb-JX; Mon, 06 Nov 2006 02:03:59 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 6 Nov 2006 08:03:52 +0100
Message-ID: <400C86AD756C4549ABB66856F1E7E68D010D0783@birke3.dai-lab.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CFP Tridentcom 2007 -  NEW CONFERENCE DATE: MAY 21-23
Thread-Index: AccBcbcGCqRQtPNtQ/SWACbFh9S9IQ==
From: "Frank Steuer" <frank.steuer@dai-labor.de>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f
X-Mailman-Approved-At: Mon, 06 Nov 2006 11:34:51 -0500
Cc: Nirmala Shenoy <ns@nssa.rit.edu>, Frank Steuer <frank.steuer@dai-labor.de>
Subject: [Mip4] CFP Tridentcom 2007 -  NEW CONFERENCE DATE: MAY 21-23
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

          [Our apologies if receive multiple copies.]



            The conference date had to be changed!
         =20
            *** NEW CONFERENCE DATE: MAY 21-23 ***



                       CALL FOR PAPERS


*************** T R I D E N T C O M  2 0 0 7 ****************

     Third International IEEE/Create-Net Conference on    =20
      Test beds and Research Infrastructures for the=20
          Development of Networks and Communities=20

   May 21-23, 2007, Grosvenor Resort, Orlando, Florida USA

                 http://www.tridentcom.org              =20

-------------------------------------------------------------


******************* IMPORTANT DEADLINES *********************
-------------------------------------------------------------

Full papers due (to be received by):        December 31, 2006

Demo proposals due:                         December 31, 2006

Notification of acceptance:                 February 28, 2007

Submission of camera-ready papers:             March 31, 2007

-------------------------------------------------------------


SCOPE
-------------------------------------------------------------
Telecommunication infrastructures play a vital role in modern
society. Advances in the range of network service offerings,
performance, quality of service, security, and ubiquity=20
continue to flourish, despite global economy fluctuations.
Access to experimental infrastructures for real-life=20
applications by specific user communities benefits all of the
stakeholders involved: the end users, because of the=20
first-hand evaluation of the provided services, the=20
researchers and infrastructure experimenters, because of the
knowledge gained from hands-on study and analysis, and the=20
service providers, because of the business exploitation of=20
the network.=20

The goal of TridentCom is to create a forum where=20
telecommunication networks researchers, vendors, providers=20
and users can exchange ideas on past experience,=20
requirements, needs, and visions for future establishment of=20
such infrastructures. It showcases experimental activities,=20
such as testing, verification, integration, measurement, and=20
deployment, which are pivotal to achieving next generation=20
communications.=20


PAPER SUBMISSION
-------------------------------------------------------------
Prospective authors are invited to submit high quality papers=20
as well as demonstration proposals reporting on all aspects=20
of testbed and research infrastructure operation and=20
management, including, but not limited to:

* Next Generation Internet Testbeds
* Next Generation Wireless Network Testbeds
* Next Generation Optical Network Testbeds=20
* Ubiquitous Network Testbeds
* Wireless Sensor Testbeds
* Testbed Operation & Management for User Communities
* Testbed Operation & Management for Research Communities
* Testbed Cooperation & Integration
* Innovative Measurements Methodologies & Tools
* Traffic Measurements Testbeds
* Software Tools to Support Distributed Testbeds /
  Virtual Laboratories
* Management of Massive Databases of Experimental Data
* Knowledge & Technology Transfer Procedures
* Security (AAA) Testing on Open Testbeds
* Social Impacts of Infrastructures
* Infrastructures for Real-Life Applications
* Business Models for Infrastructure Budgeting & Planning
* Infrastructure Renting & Pricing Policies
* Vendors & Providers Partnerships

Authors are invited to submit full papers of up to 10 pages,
including references, figures and tables, formatted according
to the IEEE 8.5" x 11" proceedings format.
Submission instructions are available on the website:=20
www.tridentcom.org.


Special Session
-------------------------------------------------------------
Testbed and trials for Governmental, Military and other=20
Special Purpose networks


DEMOS
------------------------------------------------------------
Demo proposals should consist of the following:

* title and description of the demo,
* picture of demo setup and/or screenshots of demo GUIs
* infrastructure requirements, and
* biographical sketch of the presenter(s).


ORGANIZING COMMITTEE
------------------------------------------------------------
General Chair
  Csaba A. Szabo, BUTE, Hungary

Vice General Chair
  Janise McNair, University of Florida, USA

Technical Program Co-Chairs
  Thomas Woo, Bell-Labs, USA
  Tereza Carvalho, Univ. Sao Paulo, Brazil
  Miguel =C1ngel  Lagunas, CTTC - UPC, Spain

Local  Arrangements Chair
  Damla Turgut, Univ. Central Florida, USA

Demo Co-Chairs
  Miguel Ponce de Leon, Waterford Inst.
    Technology, Ireland
  Raheem Beyah, Georgia State University

Panel Co-Chairs
  Diego Bartolome, CTTC, Spain
  Wenye Wang, North Carolina State University

Publicity Co-Chairs
  Frank Steuer, TU Berlin, Germany
  Nirmala Shenoy, Rochester Institute of Technology, USA

Web Chair:
  Sungrae Cho, Georgia Southern University


STEERING COMMITTEE
--------------------------------------------------------
Imrich Chlamtac (Chair), Create-Net, Univ. Trento, Italy
Albert Sitja, CTTC, Spain
Brian Bigalke, IEEE COMSOC
Csaba A. Szabo, BUTE, Hungary

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Mon Nov 06 11:35:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gh7Rd-0007UH-Ts; Mon, 06 Nov 2006 11:35:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gh7Ms-0005bz-TJ
	for mip4@ietf.org; Mon, 06 Nov 2006 11:30:38 -0500
Received: from nucleon.liquidweb.com ([64.91.224.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gh7Mo-0008PF-J8
	for mip4@ietf.org; Mon, 06 Nov 2006 11:30:38 -0500
Received: from c-69-181-8-85.hsd1.ca.comcast.net ([69.181.8.85]:4309
	helo=Oana2) by nucleon.liquidweb.com with esmtpa (Exim 4.52)
	id 1Gh7Md-0005to-F2
	for mip4@ietf.org; Mon, 06 Nov 2006 11:30:23 -0500
Message-ID: <27602064.1162830752060.JavaMail.Onitza@Oana2>
Date: Mon, 6 Nov 2006 08:32:32 -0800 (PST)
From: invitation@iaria.org
To: mip4@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ClamAntiVirus-Scanner: This mail is clean
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - nucleon.liquidweb.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - iaria.org
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 9af087f15dbdd4c64ae6bbcdbc5b1d44
X-Mailman-Approved-At: Mon, 06 Nov 2006 11:35:32 -0500
Subject: [Mip4] Call for Papers || ICONS 2006 || ICN 2007 || Martinique,
 April 22-28, 2007
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org


Papers published by the IEEE Computer Society Press

Papers published in the IEEE Xplore Digital Library

Papers indexed with SCI 

Best Paper Awards

All papers are peer-reviewed

 
CALL FOR PAPERS
 
The Second International Conference on Systems 

ICONS 2007
 
April 22-28, 2007 - Martinique

Site: http://www.iaria.org/conferences2007/CfPICONS07.html  

 
Featuring the workshops: 

- MCL 2007: The Second International Workshop on Mobile Communications and Learning 

- ADSYS 2007: The First International Workshop on Advanced Systems 

- APSYS 2007: The First International Workshop on Application-oriented Systems 

- SAFESYS 2007: The First International Workshop on Safety in Industrial Systems 


Important deadlines:

Full paper submission, November 20, 2006

Author notification, December 20, 2006

Registration and Camera ready, January 15, 2007
 

Tracks:

Track 1: Systems? theory and practice

Track 2: System engineering

Track 3: Systems? instrumentation

Track 4: Embedded systems and systems-on-the-chip

Track 5: Target-oriented systems 

Track 6: Specialized systems 

Track 7: Validation systems

Track 8: Security and protection systems

 
 
====================================
====================================
 
Papers published by the IEEE Computer Society Press

Papers published in the IEEE Xplore Digital Library

Papers indexed with SCI 

Best Paper Awards

All papers are peer-reviewed

 
CALL FOR PAPERS
 
The Sixth International Conference on Networking 

ICN 2007
 
April 22-28, 2007 - Martinique

Site:  http://www.iaria.org/conferences2007/ICN07.html

 
Important deadlines:

Full paper submission, November 20, 2006

Author notification, December 20, 2006

Registration and Camera ready, January 15, 2007


Topics of interest include, but are not limited to the following: 

1. Communication theory

2. Communications switching and routing

3. Communications modeling

4. Communications security

5. Computer communications

6. Distributed communications

7. Signal processing in communications

8. Multimedia and multicast communications

9. Wireless communications (satellite, WLL, 4G, Ad Hoc, sensor networks)

10. Next generation networks [NGN] principles

11. Storage area networks [SAN]

12. Access and home networks

13. High-speed networks

14. Optical networks

15. Peer-to-peer and overlay networking

16. Mobile networking and systems

17. MPLS-VPN, IPSec-VPN networks

18. GRID networks

19. Broadband networks

20. Quality of service, service level agreement [QoS/SLA]

21. Reliability, availability, serviceability [RAS]

22. Traffic engineering, metering, monitoring

23. Voice over IP services

24. Performance evaluation, tools, simulation

25. Network, control and service architectures

26. Network signaling, pricing and billing

27. Network middleware

28. Telecommunication networks architectures

29. On-demand networks, utility computing architectures

30. Applications and case studies

31. NGN protocol design and evaluation

32. NGN Standard Activities [ITU, TMF, 3GPP, IETF, etc.]

33. NGN Device Instrumentation

34. Network Management, scheduling and policy

35. NGN policy-based control

36. Networks policy-based management

37. Management of autonomic networks and systems

================================================

To be removed from this announcement list, please reply to this email with UNSUBSCRIBE in the subject field. 




-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Mon Nov 06 16:33:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GhC6O-000147-Mq; Mon, 06 Nov 2006 16:33:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gh9MH-00062v-Hn
	for mip4@ietf.org; Mon, 06 Nov 2006 13:38:09 -0500
Received: from mail.sis.pitt.edu ([136.142.116.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gh9MF-0007jY-7E
	for mip4@ietf.org; Mon, 06 Nov 2006 13:38:09 -0500
Received: from gis39 (gis39.exp.sis.pitt.edu [136.142.118.94])
	by mail.sis.pitt.edu (8.13.8/8.13.8) with ESMTP id kA6Ic61q017499
	for <mip4@ietf.org>; Mon, 6 Nov 2006 13:38:06 -0500 (EST)
Date: Mon, 6 Nov 2006 13:38:06 -0500 (EST)
Message-ID: <3874052.1771162838292421.JavaMail.javamailuser@localhost>
From: James Joshi <jjoshi@mail.sis.pitt.edu>
To: mip4@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.56 on 136.142.116.22
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
X-Mailman-Approved-At: Mon, 06 Nov 2006 16:33:55 -0500
Subject: [Mip4] CFP NetCri-07
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

[Apologies for multiple postings]

The First International Workshop on Research Challenges in Next Generation Networks for First Responders and Critical Infrastructures
http://www.cs.umd.edu/~sharno/NetCri07/

In conjunction with
The IEEE IPCCC 2007, New Orleans, Louisiana, April 11-13
http://www.ipccc.org/

===================================================================


Program Description
-------------------

As advances in pervasive computing, wireless communication and sensor networks continue, more opportunities are open to first responders and critical infrastructures to benefit from these technologies. Providing first responders with the best possible technology, infrastructure and services help save the lives of the general public and the first responders as well. One of the main challenges to the operations of first responders and critical infrastructures is to deploy a communication network that is dependable, secure, and rapidly deployable. In order to operate effectively, the deployed network supports services such as location determination, audio and video communication, and in site and remote sensing. Another key feature for first responders and critical infrastructures networks is to support interactions among multiple heterogeneous networks.

This workshop provides a forum for researchers, industry, and government agencies to discuss the challenges facing the design, deployment and operational issues for next generation network support for first responders and critical infrastructure. The workshop will identify and define fundamental concepts and techniques, resolve conflicts between different approaches in the area, and provide a common ground for an advanced research and development agenda. Topics of interest include, but are not limited to:

- Smart environments (buildings, roads, vehicles, etc.)
- Fast roaming in heterogonous network environment
- Localization and time synchronization 
- Rapidly deployable and self configuring services and networks
- Security, dependability, privacy, and performance trade-offs
- QoS in heterogeneous wireless networks
- Sensor and actuator networks for information gathering and real-time control
- Network and system support for augmented reality and visual analytics
- Test beds
- Simulation studies of first responders and critical infrastructures? networks
- Novel and adaptive communication protocols to support first responders and critical infrastructure? operation
- Resource management and allocation
- Power control management
- Admission, load and flow control
- Performance analysis and experimentation of heterogeneous wireless networks
- Security techniques and methods for heterogeneous wireless networks
- Interoperability among WLANs, Cellular, WSN and wired networks
- Measurements on heterogeneous networks
- Mobility models and traffic patterns in disaster areas
- Cross-layer design


Workshop Co-chairs
------------------

Mohamed Eltoweissy, Virginia Tech, USA
Moustafa Youssef, University of Maryland, USA


Publicity Chair
------------------

Tamer Elsharnouby, Microsoft Corporation, USA
James Joshi, University of Pittsburgh, USA


Technical Program Committee
------------------

Arup Acharya, IBM TJ Watson Research Center, USA
Ashok Agrawala, University of Maryland, USA
Mustaque Ahamad, Georgia Tech, USA
Jonathan Agre, Fujitsu Lab, USA
Nils Aschenbruck, University of Bonn, Germany
Farag Azzedine, King Fahd University, Saudi Arabia
Doreen Cheng, Samsung Research, USA
Nagwa Elmakky, Alexandria University, Egypt
Mohamed Gouda, University of Texas, USA
Elena Guara, Coventry University, UK
Wendi Heinzelman, University of Rochester, USA
James Joshi, University of Pittsburgh, USA
P. Krishnan, Avaya Labs, USA
Scott Midkiff, Virginia Tech, USA
Tamer Nadeem,  Siemens Research, USA
Dragos Niculescu, NEC Labs, USA
Stephan Olariu, Old Dominion University, USA
Stephen D. Wolthusen,  University of London, USA
Mohamed Younis,  University of Maryland at Baltimore County, USA
Adel Youssef, Google, USA




-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Nov 07 02:00:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GhKwl-0007n6-7H; Tue, 07 Nov 2006 02:00:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GhKwj-0007mC-VH
	for mip4@ietf.org; Tue, 07 Nov 2006 02:00:33 -0500
Received: from airmail.airvananet.com ([12.6.244.34]
	helo=airmail.wirelessworld.airvananet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GhKwf-0005G4-Gx
	for mip4@ietf.org; Tue, 07 Nov 2006 02:00:33 -0500
Received: from nilgiri.india.wirelessworld.airvananet.com ([192.168.51.3]) by
	airmail.wirelessworld.airvananet.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 7 Nov 2006 01:59:15 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.
Date: Tue, 7 Nov 2006 12:28:58 +0530
Message-ID: <653F3CF58193744C9DE59C217C072B5896D658@nilgiri.india.wirelessworld.airvananet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Query regarding MN-AAA authenticator calculation.
Thread-Index: AccB66vzD1uvoeyxTEe6mCzho4JntQASU/1A
From: "Arun SG" <arunsg@airvana.com>
To: <mip4@ietf.org>
X-OriginalArrivalTime: 07 Nov 2006 06:59:15.0466 (UTC)
	FILETIME=[3CCB3EA0:01C7023A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f884eb1d4ec5a230688d7edc526ea665
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

=20
Hello,=20
Please refer to the old thread pasted below. Can someone please provide
a few followup clarifications ?

1. What is the current status of 3012bis?=20
2. This para in 3012 and 3012bis states:=20

If the MN-AAA Authentication extension (see Section 6) is present in the
message, or if an NAI extension is included indicating that the mobile
node belongs to a different administrative domain, the foreign agent may
take actions outside the scope of this protocol specification to carry
out the authentication of the mobile node.

Does this then mean that this specification is restricted to the case
when the MN, FA and AAA all belong to the same administrative domain?=20

3. While CHAP_SPI declares that MD5 is to be used, I could not find a
description of how the "key" that is to be used in MD5 is obtained. Is
there an implicitly understanding that this is preshared, or perhaps
obtained through some other key exchange mechanims ?=20


MD5      (High-order byte from Challenge || Key || <<<<------is this
thru' IKE or some other means?
        MD5(Preceding Mobile IP data ||
        Type, Subtype (if present), Length, SPI) ||
        Least-order 237 bytes from Challenge))

Thanks in advance,=20
Arun



RE: [Mip4] Query regarding MN-AAA authenticator calculation.

------------------------------------------------------------------------
--------

To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri at motorola.com>=20
Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.=20
From: Kent Leung <kleung at cisco.com>=20
Date: Fri, 04 Mar 2005 17:21:21 -0800=20
Cc: "'Pete McCann'" <mccap at lucent.com>, Archana <archana_p at
huawei.com>, mip4 at ietf.org=20
In-reply-to: <EBF631554F9CD7118D0B00065BF34DCB18379493@il27exm03.cig.mot
.com>=20
List-help: <mailto:mip4-request@ietf.org?subject=3Dhelp>=20
List-id: Mobility for IPv4 <mip4.ietf.org>=20
List-post: <mailto:mip4@ietf.org>=20
List-subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
<mailto:mip4-request@ietf.org?subject=3Dsubscribe>=20
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
<mailto:mip4-request@ietf.org?subject=3Dunsubscribe>=20
Sender: mip4-bounces at ietf.org=20

------------------------------------------------------------------------
--------

Hi Madjid.  The rfc3012bis draft covers the CCoA mode.


Based on local policy, a Mobile Node with co-located care-of-address
   MAY include the Mobile-AAA Authentication extension in Registration
   Request.  In this case, if the Mobile Node uses SPI value of CHAP_SPI
   or HMAC_CHAP_SPI (section 8) in the MN-AAA Authentication extension,
   Mobile Node MUST include the Mobile-Foreign Challenge extension prior
   to the Mobile-AAA Authentication extension.  The mechanism used by
   the Mobile Node to obtain the Challenge value is outside the scope of
   this document.

Kent


At 03:52 PM 3/4/2005 -0600, Nakhjiri Madjid-MNAKHJI1 wrote:=20
Hi,

I have been meaning to respond to this as well. I agree there is no
RADIUS MD5. However, there is a problem with sending all the following


Preceding Mobile IP data ||
        Type, Subtype (if present), Length, SPI) ||
       Least-order 237 bytes from Challenge

Over RADIUS messages, since RADIUS packets can be at most 4K long and
attributes at most 253 bytes (if I understood this correctly), which
means you do have to calculate a hash of the data above before packing
it over RADIUS messaging, if you want the AAA server to do the same
calculations. If anybody has a number on the number of bytes the data
above takes, I would appreciate it??
We tried to explain this in our draft on RADIUS support for MIP-AAA
signaling.


http://www.ietf.org/internet-drafts/draft-nakhjiri-radius-mip4-00.txt

We ran into another problem with this and that was: the challenge is
used only in conjunctions with FAs and when the MN uses a CcoA and
registers through HA directly, there won't be any challenge to calculate


MD5      (High-order byte from Challenge || Key ||
        MD5(Preceding Mobile IP data ||
        Type, Subtype (if present), Length, SPI) ||
        Least-order 237 bytes from Challenge))

Our proposal based on Charlie's suggestion (no mean to push the blame,
Charlie :) ) was to include zero octets whenever challenge data was
needed in that case.


Any thoughts?

Madjid
-----Original Message-----
From: mip4-bounces at ietf.org [mailto:mip4-bounces at ietf.org] On
Behalf Of Pete McCann
Sent: Friday, February 25, 2005 9:48 AM
To: Archana
Cc: mip4 at ietf.org
Subject: [Mip4] Query regarding MN-AAA authenticator calculation.


Hi, Archana,

Archana writes:
> Hi
> According to RFC 3012, the MN-AAA authenticator is computed by
applying MD5
> on the following data
>
> High-order byte from Challenge || Key ||
> MD5(Preceding Mobile IP data ||
> Type, Subtype (if present), Length, SPI) ||
> Least-order 237 bytes from Challenge
>
> I have the following queries regarding the above computation. Any help
in
> the clarifying them will be highly appreciated.
>
> 1. What is meant by High-order and Least order ?


"High-order" means "most significant".  You can also interpret it as
"leftmost" when looking at the encoding of the Challenge in a Mobile
IP Extension.

> 2. How does the Radius MD5 algorithm differ in calculating the
Authenticator
> from a MD5 algorithm


There is no special "Radius MD5" as far as I know.


MD5 is specified in RFC3121.  It is a well-known hash function that
processes the input and produces a 16 octet hash.


The calculation shown above is compatible with existing RADIUS servers
that are used for authenticating PPP/CHAP, i.e., the code used for
PPP/CHAP can be re-used to compute the above authenticator, assuming
that the FA can precompute the inner MD5 and send it in an
Access-Request.


-Pete


 > Thanks in advance
 > Archana


--
Mip4 mailing list: Mip4 at ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


--
Mip4 mailing list: Mip4 at ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--
     |           |                   Kent Leung
    :|:         :|:                  IP Mobility Development
   :|||:       :|||:                 Internet Technologies Division
  :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
 c i s c o S y s t e m s             Email: kleung at cisco.com


--
Mip4 mailing list: Mip4 at ietf.org
   Web interface: https://www1.ietf.org/mailman/listinfo/mip4
    Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/





------------------------------------------------------------------------
--------

Prev by Date: RE: [Mip4] Query regarding MN-AAA authenticator
calculation.=20
Next by Date: [Mip4] [Deadline Approaching] Final CFP: IEEE WirelessCom
Symposium on Mobile Computing, 2005=20
Previous by thread: RE: [Mip4] Query regarding MN-AAA authenticator
calculation.=20
Next by thread: RE: [Mip4] Query regarding MN-AAA authenticator
calculation.=20
Index(es):=20
Date=20
Thread=20
Note: Messages sent to this list are the opinions of the senders and do
not imply endorsement by the IETF.=20

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Nov 07 12:44:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GhUzc-000556-Sb; Tue, 07 Nov 2006 12:44:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GhUxt-0004TI-K7
	for mip4@ietf.org; Tue, 07 Nov 2006 12:42:25 -0500
Received: from mail119.messagelabs.com ([216.82.241.179])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GhUxq-0002iX-5w
	for mip4@ietf.org; Tue, 07 Nov 2006 12:42:25 -0500
X-VirusChecked: Checked
X-Env-Sender: pete.mccann@motorola.com
X-Msg-Ref: server-4.tower-119.messagelabs.com!1162921341!9494845!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 16394 invoked from network); 7 Nov 2006 17:42:21 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-4.tower-119.messagelabs.com with SMTP;
	7 Nov 2006 17:42:21 -0000
Received: from il06exb01.corp.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id kA7HgLmX021715
	for <mip4@ietf.org>; Tue, 7 Nov 2006 10:42:21 -0700 (MST)
Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18])
	by il06exb01.corp.mot.com (8.13.1/8.13.0) with ESMTP id kA7HgKAo001868
	for <mip4@ietf.org>; Tue, 7 Nov 2006 11:42:20 -0600 (CST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.
Date: Tue, 7 Nov 2006 12:42:20 -0500
Message-ID: <BE4B07D4197BF34EB3B753DD34EBCD13011B06C0@de01exm67.ds.mot.com>
In-Reply-To: <653F3CF58193744C9DE59C217C072B5896D658@nilgiri.india.wirelessworld.airvananet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Query regarding MN-AAA authenticator calculation.
Thread-Index: AccB66vzD1uvoeyxTEe6mCzho4JntQASU/1AABeY49A=
From: "McCann Peter-A001034" <pete.mccann@motorola.com>
To: "Arun SG" <arunsg@airvana.com>, <mip4@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f0b5a4216bfa030ed8a6f68d1833f8ae
X-Mailman-Approved-At: Tue, 07 Nov 2006 12:44:11 -0500
Cc: 
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi, Arun,

Arun SG wrote:
> Hello,
> Please refer to the old thread pasted below. Can someone please
> provide a few followup clarifications ?=20
>=20
> 1. What is the current status of 3012bis?

3012bis is currently in AUTH48, one of the very last stages before
publication.  I think we are still waiting on responses from a couple
of the authors.

> 2. This para in 3012 and 3012bis states:
>=20
> If the MN-AAA Authentication extension (see Section 6) is present in
> the message, or if an NAI extension is included indicating that the
> mobile node belongs to a different administrative domain, the foreign
> agent may take actions outside the scope of this protocol
> specification to carry out the authentication of the mobile node.   =20
>=20
> Does this then mean that this specification is restricted to the case
> when the MN, FA and AAA all belong to the same administrative domain?=20

Certainly not.  It just says that the action taken by the FA to
validate the MN-AAA extension is outside the scope of this document.

> 3. While CHAP_SPI declares that MD5 is to be used, I could not find a
> description of how the "key" that is to be used in MD5 is obtained.
> Is there an implicitly understanding that this is preshared, or
> perhaps obtained through some other key exchange mechanims ?  =20

The "key" is a long-term secret shared between the MN and the
home AAA server.  It is configured using out-of-band mechanisms that
are outside the scope of 3012.
>=20
> MD5      (High-order byte from Challenge || Key || <<<<------is this
> thru' IKE or some other means?
>         MD5(Preceding Mobile IP data ||
>         Type, Subtype (if present), Length, SPI) ||
>         Least-order 237 bytes from Challenge))
>=20
> Thanks in advance,
> Arun

Hope this helps.

-Pete

>=20
>=20
> RE: [Mip4] Query regarding MN-AAA authenticator calculation.
>=20
>
------------------------------------------------------------------------
> --------
>=20
> To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri at motorola.com>
> Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.
> From: Kent Leung <kleung at cisco.com>
> Date: Fri, 04 Mar 2005 17:21:21 -0800
> Cc: "'Pete McCann'" <mccap at lucent.com>, Archana <archana_p at
> huawei.com>, mip4 at ietf.org
> In-reply-to:
> <EBF631554F9CD7118D0B00065BF34DCB18379493@il27exm03.cig.mot .com>
> List-help: <mailto:mip4-request@ietf.org?subject=3Dhelp>
> List-id: Mobility for IPv4 <mip4.ietf.org>
> List-post: <mailto:mip4@ietf.org>
> List-subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
> <mailto:mip4-request@ietf.org?subject=3Dsubscribe>
> List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
> <mailto:mip4-request@ietf.org?subject=3Dunsubscribe>
> Sender: mip4-bounces at ietf.org
>=20
>
------------------------------------------------------------------------
> --------
>=20
> Hi Madjid.  The rfc3012bis draft covers the CCoA mode.
>=20
>=20
> Based on local policy, a Mobile Node with co-located care-of-address
>    MAY include the Mobile-AAA Authentication extension in Registration
>    Request.  In this case, if the Mobile Node uses SPI value of
>    CHAP_SPI or HMAC_CHAP_SPI (section 8) in the MN-AAA Authentication
>    extension, Mobile Node MUST include the Mobile-Foreign Challenge
>    extension prior to the Mobile-AAA Authentication extension.  The
>    mechanism used by the Mobile Node to obtain the Challenge value is
>    outside the scope of this document.
>=20
> Kent
>=20
>=20
> At 03:52 PM 3/4/2005 -0600, Nakhjiri Madjid-MNAKHJI1 wrote:
> Hi,
>=20
> I have been meaning to respond to this as well. I agree there is no
> RADIUS MD5. However, there is a problem with sending all the following
>=20
>=20
> Preceding Mobile IP data ||
>         Type, Subtype (if present), Length, SPI) ||
>        Least-order 237 bytes from Challenge
>=20
> Over RADIUS messages, since RADIUS packets can be at most 4K long and
> attributes at most 253 bytes (if I understood this correctly), which
> means you do have to calculate a hash of the data above before packing
> it over RADIUS messaging, if you want the AAA server to do the same
> calculations. If anybody has a number on the number of bytes the data
> above takes, I would appreciate it??
> We tried to explain this in our draft on RADIUS support for MIP-AAA
> signaling.
>=20
>=20
> http://www.ietf.org/internet-drafts/draft-nakhjiri-radius-mip4-00.txt
>=20
> We ran into another problem with this and that was: the challenge is
> used only in conjunctions with FAs and when the MN uses a CcoA and
> registers through HA directly, there won't be any challenge to
> calculate=20
>=20
>=20
> MD5      (High-order byte from Challenge || Key ||
>         MD5(Preceding Mobile IP data ||
>         Type, Subtype (if present), Length, SPI) ||
>         Least-order 237 bytes from Challenge))
>=20
> Our proposal based on Charlie's suggestion (no mean to push the blame,
> Charlie :) ) was to include zero octets whenever challenge data was
> needed in that case.
>=20
>=20
> Any thoughts?
>=20
> Madjid
> -----Original Message-----
> From: mip4-bounces at ietf.org [mailto:mip4-bounces at ietf.org] On
> Behalf Of Pete McCann
> Sent: Friday, February 25, 2005 9:48 AM
> To: Archana
> Cc: mip4 at ietf.org
> Subject: [Mip4] Query regarding MN-AAA authenticator calculation.
>=20
>=20
> Hi, Archana,
>=20
> Archana writes:
>> Hi
>> According to RFC 3012, the MN-AAA authenticator is computed by
>> applying MD5 on the following data=20
>>=20
>> High-order byte from Challenge || Key ||
>> MD5(Preceding Mobile IP data ||
>> Type, Subtype (if present), Length, SPI) ||
>> Least-order 237 bytes from Challenge
>>=20
>> I have the following queries regarding the above computation. Any
>> help in the clarifying them will be highly appreciated.
>>=20
>> 1. What is meant by High-order and Least order ?
>=20
>=20
> "High-order" means "most significant".  You can also interpret it as
> "leftmost" when looking at the encoding of the Challenge in a Mobile
> IP Extension.
>=20
>> 2. How does the Radius MD5 algorithm differ in calculating the
>> Authenticator from a MD5 algorithm
>=20
>=20
> There is no special "Radius MD5" as far as I know.
>=20
>=20
> MD5 is specified in RFC3121.  It is a well-known hash function that
> processes the input and produces a 16 octet hash.
>=20
>=20
> The calculation shown above is compatible with existing RADIUS servers
> that are used for authenticating PPP/CHAP, i.e., the code used for
> PPP/CHAP can be re-used to compute the above authenticator, assuming
> that the FA can precompute the inner MD5 and send it in an
> Access-Request.
>=20
>=20
> -Pete
>=20
>=20
>  > Thanks in advance
>  > Archana
>=20
>=20
> --
> Mip4 mailing list: Mip4 at ietf.org
>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
>=20
>=20
> --
> Mip4 mailing list: Mip4 at ietf.org
>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
>=20
> --
>      |           |                   Kent Leung
>     :|:         :|:                  IP Mobility Development
>    :|||:       :|||:                 Internet Technologies Division
>   :|||||||:   :|||||||:              Voice: 408.526.5030
> .:|||||||||:.:|||||||||:.             Fax:   408.525.1653
>  c i s c o S y s t e m s             Email: kleung at cisco.com
>=20
>=20
> --
> Mip4 mailing list: Mip4 at ietf.org
>    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
>=20
>=20
>=20
>=20
>=20
>
------------------------------------------------------------------------
> --------
>=20
> Prev by Date: RE: [Mip4] Query regarding MN-AAA authenticator
> calculation.
> Next by Date: [Mip4] [Deadline Approaching] Final CFP: IEEE
> WirelessCom=20
> Symposium on Mobile Computing, 2005
> Previous by thread: RE: [Mip4] Query regarding MN-AAA authenticator
> calculation.
> Next by thread: RE: [Mip4] Query regarding MN-AAA authenticator
> calculation.
> Index(es):
> Date
> Thread
> Note: Messages sent to this list are the opinions of the senders and
> do=20
> not imply endorsement by the IETF.


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Nov 07 18:28:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GhaMp-0006rF-94; Tue, 07 Nov 2006 18:28:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gha4H-0002Xp-AU
	for mip4@ietf.org; Tue, 07 Nov 2006 18:09:21 -0500
Received: from mail119.messagelabs.com ([216.82.241.179])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gha4G-0004xd-33
	for mip4@ietf.org; Tue, 07 Nov 2006 18:09:21 -0500
X-VirusChecked: Checked
X-Env-Sender: pete.mccann@motorola.com
X-Msg-Ref: server-14.tower-119.messagelabs.com!1162940956!13915239!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 9437 invoked from network); 7 Nov 2006 23:09:16 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-14.tower-119.messagelabs.com with SMTP;
	7 Nov 2006 23:09:16 -0000
Received: from az33exr02.mot.com ([10.64.251.232])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id kA7N9FMI000179
	for <mip4@ietf.org>; Tue, 7 Nov 2006 16:09:15 -0700 (MST)
Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id kA7N9Esf008840
	for <mip4@ietf.org>; Tue, 7 Nov 2006 17:09:15 -0600 (CST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] WGLC: draft-ietf-mip4-gen-ext-00.txt
Date: Tue, 7 Nov 2006 18:09:15 -0500
Message-ID: <BE4B07D4197BF34EB3B753DD34EBCD13011B08D1@de01exm67.ds.mot.com>
In-Reply-To: <45401838.5070409@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] WGLC: draft-ietf-mip4-gen-ext-00.txt
Thread-Index: Acb4o4zenLPGLKvYSp+cqDu9Cg6GFgKHd1ug
From: "McCann Peter-A001034" <pete.mccann@motorola.com>
To: <mip4@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
X-Mailman-Approved-At: Tue, 07 Nov 2006 18:28:30 -0500
Cc: Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

The working group last call on draft-ietf-mip4-gen-ext-00.txt has
concluded.  It looks like we got one set of very constructive comments
(thanks Vijay).  A revised I-D is needed to address the comments.

-Pete



-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Nov 07 23:53:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GhfQo-0004iG-7Z; Tue, 07 Nov 2006 23:52:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GhfQn-0004dC-0j
	for mip4@ietf.org; Tue, 07 Nov 2006 23:52:57 -0500
Received: from airmail.airvananet.com ([12.6.244.34]
	helo=airmail.wirelessworld.airvananet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GhfQj-0007GT-Fx
	for mip4@ietf.org; Tue, 07 Nov 2006 23:52:56 -0500
Received: from nilgiri.india.wirelessworld.airvananet.com ([192.168.51.3]) by
	airmail.wirelessworld.airvananet.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 7 Nov 2006 23:51:52 -0500
Content-class: urn:content-classes:message
Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.
Date: Wed, 8 Nov 2006 10:21:48 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <653F3CF58193744C9DE59C217C072B5896D86E@nilgiri.india.wirelessworld.airvananet.com>
X-MS-Has-Attach: 
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Query regarding MN-AAA authenticator calculation.
Thread-Index: AccB66vzD1uvoeyxTEe6mCzho4JntQASU/1AABeY49AAF3ZnEA==
From: "Arun SG" <arunsg@airvana.com>
To: "McCann Peter-A001034" <pete.mccann@motorola.com>,
	<mip4@ietf.org>
X-OriginalArrivalTime: 08 Nov 2006 04:51:52.0919 (UTC)
	FILETIME=[9BE4DE70:01C702F1]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2a9ffb6f997442a3b543bcdaf483b990
Cc: 
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Thanks, Peter.
This is certainly helpful. Is there work underway that would cover the
FA action in case of MN-AAA authentication ?
Arun=20

-----Original Message-----
From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com]=20
Sent: Tuesday, November 07, 2006 11:12 PM
To: Arun SG; mip4@ietf.org
Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.

Hi, Arun,

Arun SG wrote:
> Hello,
> Please refer to the old thread pasted below. Can someone please=20
> provide a few followup clarifications ?
>=20
> 1. What is the current status of 3012bis?

3012bis is currently in AUTH48, one of the very last stages before
publication.  I think we are still waiting on responses from a couple of
the authors.

> 2. This para in 3012 and 3012bis states:
>=20
> If the MN-AAA Authentication extension (see Section 6) is present in=20
> the message, or if an NAI extension is included indicating that the=20
> mobile node belongs to a different administrative domain, the foreign=20
> agent may take actions outside the scope of this protocol
> specification to carry out the authentication of the mobile node.   =20
>=20
> Does this then mean that this specification is restricted to the case=20
> when the MN, FA and AAA all belong to the same administrative domain?

Certainly not.  It just says that the action taken by the FA to validate
the MN-AAA extension is outside the scope of this document.

> 3. While CHAP_SPI declares that MD5 is to be used, I could not find a=20
> description of how the "key" that is to be used in MD5 is obtained.
> Is there an implicitly understanding that this is preshared, or
> perhaps obtained through some other key exchange mechanims ?  =20

The "key" is a long-term secret shared between the MN and the home AAA
server.  It is configured using out-of-band mechanisms that are outside
the scope of 3012.
>=20
> MD5      (High-order byte from Challenge || Key || <<<<------is this
> thru' IKE or some other means?
>         MD5(Preceding Mobile IP data ||
>         Type, Subtype (if present), Length, SPI) ||
>         Least-order 237 bytes from Challenge))
>=20
> Thanks in advance,
> Arun

Hope this helps.

-Pete

>=20
>=20
> RE: [Mip4] Query regarding MN-AAA authenticator calculation.
>=20
>
------------------------------------------------------------------------
> --------
>=20
> To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri at motorola.com>
> Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.
> From: Kent Leung <kleung at cisco.com>
> Date: Fri, 04 Mar 2005 17:21:21 -0800
> Cc: "'Pete McCann'" <mccap at lucent.com>, Archana <archana_p at=20
> huawei.com>, mip4 at ietf.org
> In-reply-to:
> <EBF631554F9CD7118D0B00065BF34DCB18379493@il27exm03.cig.mot .com>
> List-help: <mailto:mip4-request@ietf.org?subject=3Dhelp>
> List-id: Mobility for IPv4 <mip4.ietf.org>
> List-post: <mailto:mip4@ietf.org>
> List-subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
> <mailto:mip4-request@ietf.org?subject=3Dsubscribe>
> List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
> <mailto:mip4-request@ietf.org?subject=3Dunsubscribe>
> Sender: mip4-bounces at ietf.org
>=20
>
------------------------------------------------------------------------
> --------
>=20
> Hi Madjid.  The rfc3012bis draft covers the CCoA mode.
>=20
>=20
> Based on local policy, a Mobile Node with co-located care-of-address
>    MAY include the Mobile-AAA Authentication extension in Registration
>    Request.  In this case, if the Mobile Node uses SPI value of
>    CHAP_SPI or HMAC_CHAP_SPI (section 8) in the MN-AAA Authentication
>    extension, Mobile Node MUST include the Mobile-Foreign Challenge
>    extension prior to the Mobile-AAA Authentication extension.  The
>    mechanism used by the Mobile Node to obtain the Challenge value is
>    outside the scope of this document.
>=20
> Kent
>=20
>=20
> At 03:52 PM 3/4/2005 -0600, Nakhjiri Madjid-MNAKHJI1 wrote:
> Hi,
>=20
> I have been meaning to respond to this as well. I agree there is no=20
> RADIUS MD5. However, there is a problem with sending all the following
>=20
>=20
> Preceding Mobile IP data ||
>         Type, Subtype (if present), Length, SPI) ||
>        Least-order 237 bytes from Challenge
>=20
> Over RADIUS messages, since RADIUS packets can be at most 4K long and=20
> attributes at most 253 bytes (if I understood this correctly), which=20
> means you do have to calculate a hash of the data above before packing

> it over RADIUS messaging, if you want the AAA server to do the same=20
> calculations. If anybody has a number on the number of bytes the data=20
> above takes, I would appreciate it??
> We tried to explain this in our draft on RADIUS support for MIP-AAA=20
> signaling.
>=20
>=20
> http://www.ietf.org/internet-drafts/draft-nakhjiri-radius-mip4-00.txt
>=20
> We ran into another problem with this and that was: the challenge is=20
> used only in conjunctions with FAs and when the MN uses a CcoA and=20
> registers through HA directly, there won't be any challenge to=20
> calculate
>=20
>=20
> MD5      (High-order byte from Challenge || Key ||
>         MD5(Preceding Mobile IP data ||
>         Type, Subtype (if present), Length, SPI) ||
>         Least-order 237 bytes from Challenge))
>=20
> Our proposal based on Charlie's suggestion (no mean to push the blame,

> Charlie :) ) was to include zero octets whenever challenge data was=20
> needed in that case.
>=20
>=20
> Any thoughts?
>=20
> Madjid
> -----Original Message-----
> From: mip4-bounces at ietf.org [mailto:mip4-bounces at ietf.org] On=20
> Behalf Of Pete McCann
> Sent: Friday, February 25, 2005 9:48 AM
> To: Archana
> Cc: mip4 at ietf.org
> Subject: [Mip4] Query regarding MN-AAA authenticator calculation.
>=20
>=20
> Hi, Archana,
>=20
> Archana writes:
>> Hi
>> According to RFC 3012, the MN-AAA authenticator is computed by=20
>> applying MD5 on the following data
>>=20
>> High-order byte from Challenge || Key || MD5(Preceding Mobile IP data

>> || Type, Subtype (if present), Length, SPI) || Least-order 237 bytes=20
>> from Challenge
>>=20
>> I have the following queries regarding the above computation. Any=20
>> help in the clarifying them will be highly appreciated.
>>=20
>> 1. What is meant by High-order and Least order ?
>=20
>=20
> "High-order" means "most significant".  You can also interpret it as=20
> "leftmost" when looking at the encoding of the Challenge in a Mobile=20
> IP Extension.
>=20
>> 2. How does the Radius MD5 algorithm differ in calculating the=20
>> Authenticator from a MD5 algorithm
>=20
>=20
> There is no special "Radius MD5" as far as I know.
>=20
>=20
> MD5 is specified in RFC3121.  It is a well-known hash function that=20
> processes the input and produces a 16 octet hash.
>=20
>=20
> The calculation shown above is compatible with existing RADIUS servers

> that are used for authenticating PPP/CHAP, i.e., the code used for=20
> PPP/CHAP can be re-used to compute the above authenticator, assuming=20
> that the FA can precompute the inner MD5 and send it in an=20
> Access-Request.
>=20
>=20
> -Pete
>=20
>=20
>  > Thanks in advance
>  > Archana
>=20
>=20
> --
> Mip4 mailing list: Mip4 at ietf.org
>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
>=20
>=20
> --
> Mip4 mailing list: Mip4 at ietf.org
>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
>=20
> --
>      |           |                   Kent Leung
>     :|:         :|:                  IP Mobility Development
>    :|||:       :|||:                 Internet Technologies Division
>   :|||||||:   :|||||||:              Voice: 408.526.5030
> .:|||||||||:.:|||||||||:.             Fax:   408.525.1653
>  c i s c o S y s t e m s             Email: kleung at cisco.com
>=20
>=20
> --
> Mip4 mailing list: Mip4 at ietf.org
>    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
>=20
>=20
>=20
>=20
>=20
>
------------------------------------------------------------------------
> --------
>=20
> Prev by Date: RE: [Mip4] Query regarding MN-AAA authenticator=20
> calculation.
> Next by Date: [Mip4] [Deadline Approaching] Final CFP: IEEE=20
> WirelessCom Symposium on Mobile Computing, 2005 Previous by thread:=20
> RE: [Mip4] Query regarding MN-AAA authenticator calculation.
> Next by thread: RE: [Mip4] Query regarding MN-AAA authenticator=20
> calculation.
> Index(es):
> Date
> Thread
> Note: Messages sent to this list are the opinions of the senders and=20
> do not imply endorsement by the IETF.


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Nov 08 12:14:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ghr0q-0002Fq-Fj; Wed, 08 Nov 2006 12:14:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ghr0p-0002Fl-2h
	for mip4@ietf.org; Wed, 08 Nov 2006 12:14:55 -0500
Received: from mail119.messagelabs.com ([216.82.241.179])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Ghr0h-0002hi-HD
	for mip4@ietf.org; Wed, 08 Nov 2006 12:14:54 -0500
X-VirusChecked: Checked
X-Env-Sender: pete.mccann@motorola.com
X-Msg-Ref: server-3.tower-119.messagelabs.com!1163005076!13545216!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [144.189.100.103]
Received: (qmail 15752 invoked from network); 8 Nov 2006 16:57:56 -0000
Received: from motgate3.mot.com (HELO motgate3.mot.com) (144.189.100.103)
	by server-3.tower-119.messagelabs.com with SMTP;
	8 Nov 2006 16:57:56 -0000
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate3.mot.com (8.12.11/Motorola) with ESMTP id kA8GvtSQ020439
	for <mip4@ietf.org>; Wed, 8 Nov 2006 09:57:55 -0700 (MST)
Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id kA8GvsNP028177
	for <mip4@ietf.org>; Wed, 8 Nov 2006 10:57:55 -0600 (CST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.
Date: Wed, 8 Nov 2006 11:57:47 -0500
Message-ID: <BE4B07D4197BF34EB3B753DD34EBCD13011B0AB4@de01exm67.ds.mot.com>
In-Reply-To: <653F3CF58193744C9DE59C217C072B5896D86E@nilgiri.india.wirelessworld.airvananet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Query regarding MN-AAA authenticator calculation.
Thread-Index: AccB66vzD1uvoeyxTEe6mCzho4JntQASU/1AABeY49AAF3ZnEAAZXchA
From: "McCann Peter-A001034" <pete.mccann@motorola.com>
To: "Arun SG" <arunsg@airvana.com>, <mip4@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 155726d2f5fe5eb5c40a9f079fd9e841
Cc: 
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

RFC 4004 describes a Diameter application that can be used
by the FA to verify the challenge-response and propagate
the Registration Request to a home agent in another domain.

There is not currently an IETF specification for what happens
in RADIUS but we may be taking up that work in future.

-Pete

Arun SG wrote:
> Thanks, Peter.
> This is certainly helpful. Is there work underway that would cover
> the FA action in case of MN-AAA authentication ?=20
> Arun
>=20
> -----Original Message-----
> From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com]
> Sent: Tuesday, November 07, 2006 11:12 PM
> To: Arun SG; mip4@ietf.org
> Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.
>=20
> Hi, Arun,
>=20
> Arun SG wrote:
>> Hello,
>> Please refer to the old thread pasted below. Can someone please
>> provide a few followup clarifications ?
>>=20
>> 1. What is the current status of 3012bis?
>=20
> 3012bis is currently in AUTH48, one of the very last stages before
> publication.  I think we are still waiting on responses from a couple
> of the authors. =20
>=20
>> 2. This para in 3012 and 3012bis states:
>>=20
>> If the MN-AAA Authentication extension (see Section 6) is present in
>> the message, or if an NAI extension is included indicating that the
>> mobile node belongs to a different administrative domain, the foreign
>> agent may take actions outside the scope of this protocol
>> specification to carry out the authentication of the mobile node.
>>=20
>> Does this then mean that this specification is restricted to the case
>> when the MN, FA and AAA all belong to the same administrative domain?
>=20
> Certainly not.  It just says that the action taken by the FA to
> validate the MN-AAA extension is outside the scope of this document.=20
>=20
>> 3. While CHAP_SPI declares that MD5 is to be used, I could not find a
>> description of how the "key" that is to be used in MD5 is obtained.
>> Is there an implicitly understanding that this is preshared, or
>> perhaps obtained through some other key exchange mechanims ?
>=20
> The "key" is a long-term secret shared between the MN and the home
> AAA server.  It is configured using out-of-band mechanisms that are
> outside the scope of 3012. =20
>>=20
>> MD5      (High-order byte from Challenge || Key || <<<<------is this
>> thru' IKE or some other means?
>>         MD5(Preceding Mobile IP data ||
>>         Type, Subtype (if present), Length, SPI) ||
>>         Least-order 237 bytes from Challenge))
>>=20
>> Thanks in advance,
>> Arun
>=20
> Hope this helps.
>=20
> -Pete
>=20
>>=20
>>=20
>> RE: [Mip4] Query regarding MN-AAA authenticator calculation.
>>=20
>>=20
>
------------------------------------------------------------------------
>> --------
>>=20
>> To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri at motorola.com>
>> Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.
>> From: Kent Leung <kleung at cisco.com>
>> Date: Fri, 04 Mar 2005 17:21:21 -0800
>> Cc: "'Pete McCann'" <mccap at lucent.com>, Archana <archana_p at
>> huawei.com>, mip4 at ietf.org In-reply-to:
>> <EBF631554F9CD7118D0B00065BF34DCB18379493@il27exm03.cig.mot .com>
>> List-help: <mailto:mip4-request@ietf.org?subject=3Dhelp>
>> List-id: Mobility for IPv4 <mip4.ietf.org>
>> List-post: <mailto:mip4@ietf.org>
>> List-subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
>> <mailto:mip4-request@ietf.org?subject=3Dsubscribe>
>> List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
>> <mailto:mip4-request@ietf.org?subject=3Dunsubscribe>
>> Sender: mip4-bounces at ietf.org
>>=20
>>=20
>
------------------------------------------------------------------------
>> --------
>>=20
>> Hi Madjid.  The rfc3012bis draft covers the CCoA mode.
>>=20
>>=20
>> Based on local policy, a Mobile Node with co-located care-of-address
>>    MAY include the Mobile-AAA Authentication extension in
>>    Registration Request.  In this case, if the Mobile Node uses SPI
>>    value of CHAP_SPI or HMAC_CHAP_SPI (section 8) in the MN-AAA
>>    Authentication extension, Mobile Node MUST include the
>>    Mobile-Foreign Challenge extension prior to the Mobile-AAA
>>    Authentication extension.  The mechanism used by the Mobile Node
>>    to obtain the Challenge value is outside the scope of this
>> document.=20
>>=20
>> Kent
>>=20
>>=20
>> At 03:52 PM 3/4/2005 -0600, Nakhjiri Madjid-MNAKHJI1 wrote:
>> Hi,
>>=20
>> I have been meaning to respond to this as well. I agree there is no
>> RADIUS MD5. However, there is a problem with sending all the
>> following=20
>>=20
>>=20
>> Preceding Mobile IP data ||
>>         Type, Subtype (if present), Length, SPI) ||
>>        Least-order 237 bytes from Challenge
>>=20
>> Over RADIUS messages, since RADIUS packets can be at most 4K long and
>> attributes at most 253 bytes (if I understood this correctly), which
>> means you do have to calculate a hash of the data above before
>> packing=20
>=20
>> it over RADIUS messaging, if you want the AAA server to do the same
>> calculations. If anybody has a number on the number of bytes the data
>> above takes, I would appreciate it??
>> We tried to explain this in our draft on RADIUS support for MIP-AAA
>> signaling.=20
>>=20
>>=20
>> http://www.ietf.org/internet-drafts/draft-nakhjiri-radius-mip4-00.txt
>>=20
>> We ran into another problem with this and that was: the challenge is
>> used only in conjunctions with FAs and when the MN uses a CcoA and
>> registers through HA directly, there won't be any challenge to
>> calculate=20
>>=20
>>=20
>> MD5      (High-order byte from Challenge || Key ||
>>         MD5(Preceding Mobile IP data ||
>>         Type, Subtype (if present), Length, SPI) ||
>>         Least-order 237 bytes from Challenge))
>>=20
>> Our proposal based on Charlie's suggestion (no mean to push the
>> blame,=20
>=20
>> Charlie :) ) was to include zero octets whenever challenge data was
>> needed in that case.=20
>>=20
>>=20
>> Any thoughts?
>>=20
>> Madjid
>> -----Original Message-----
>> From: mip4-bounces at ietf.org [mailto:mip4-bounces at ietf.org] On
>> Behalf Of Pete McCann Sent: Friday, February 25, 2005 9:48 AM
>> To: Archana
>> Cc: mip4 at ietf.org
>> Subject: [Mip4] Query regarding MN-AAA authenticator calculation.
>>=20
>>=20
>> Hi, Archana,
>>=20
>> Archana writes:
>>> Hi
>>> According to RFC 3012, the MN-AAA authenticator is computed by
>>> applying MD5 on the following data
>>>=20
>>> High-order byte from Challenge || Key || MD5(Preceding Mobile IP
>>> data=20
>=20
>>>>> Type, Subtype (if present), Length, SPI) || Least-order 237 bytes
>>>>> from Challenge=20
>>>=20
>>> I have the following queries regarding the above computation. Any
>>> help in the clarifying them will be highly appreciated.
>>>=20
>>> 1. What is meant by High-order and Least order ?
>>=20
>>=20
>> "High-order" means "most significant".  You can also interpret it as
>> "leftmost" when looking at the encoding of the Challenge in a Mobile
>> IP Extension.=20
>>=20
>>> 2. How does the Radius MD5 algorithm differ in calculating the
>>> Authenticator from a MD5 algorithm
>>=20
>>=20
>> There is no special "Radius MD5" as far as I know.
>>=20
>>=20
>> MD5 is specified in RFC3121.  It is a well-known hash function that
>> processes the input and produces a 16 octet hash.
>>=20
>>=20
>> The calculation shown above is compatible with existing RADIUS
>> servers=20
>=20
>> that are used for authenticating PPP/CHAP, i.e., the code used for
>> PPP/CHAP can be re-used to compute the above authenticator, assuming
>> that the FA can precompute the inner MD5 and send it in an
>> Access-Request.=20
>>=20
>>=20
>> -Pete
>>=20
>>=20
>>  > Thanks in advance
>>  > Archana
>>=20
>>=20
>> --
>> Mip4 mailing list: Mip4 at ietf.org
>>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>>      Charter page:
>> http://www.ietf.org/html.charters/mip4-charter.html Supplemental
>> site: http://www.mip4.org/=20
>>=20
>>=20
>> --
>> Mip4 mailing list: Mip4 at ietf.org
>>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>>      Charter page:
>> http://www.ietf.org/html.charters/mip4-charter.html Supplemental
>> site: http://www.mip4.org/=20
>>=20
>> --
>>      |           |                   Kent Leung
>>     :|:         :|:                  IP Mobility Development
>>    :|||:       :|||:                 Internet Technologies Division
>>   :|||||||:   :|||||||:              Voice: 408.526.5030
>> .:|||||||||:.:|||||||||:.             Fax:   408.525.1653
>>  c i s c o S y s t e m s             Email: kleung at cisco.com
>>=20
>>=20
>> --
>> Mip4 mailing list: Mip4 at ietf.org
>>    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>>     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>> Supplemental site: http://www.mip4.org/
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>
------------------------------------------------------------------------
>> --------
>>=20
>> Prev by Date: RE: [Mip4] Query regarding MN-AAA authenticator
>> calculation. Next by Date: [Mip4] [Deadline Approaching] Final CFP:
>> IEEE WirelessCom Symposium on Mobile Computing, 2005 Previous by
>> thread: RE: [Mip4] Query regarding MN-AAA authenticator calculation.
>> Next by thread: RE: [Mip4] Query regarding MN-AAA authenticator
>> calculation. Index(es):
>> Date
>> Thread
>> Note: Messages sent to this list are the opinions of the senders and
>> do not imply endorsement by the IETF.


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Nov 15 14:09:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GkQ8g-0002zv-WA; Wed, 15 Nov 2006 14:09:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GkQ8e-0002zj-SV
	for mip4@ietf.org; Wed, 15 Nov 2006 14:09:36 -0500
Received: from mail119.messagelabs.com ([216.82.241.179])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GkQ8e-0007aY-D8
	for mip4@ietf.org; Wed, 15 Nov 2006 14:09:36 -0500
X-VirusChecked: Checked
X-Env-Sender: pete.mccann@motorola.com
X-Msg-Ref: server-8.tower-119.messagelabs.com!1163617774!10421732!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 19627 invoked from network); 15 Nov 2006 19:09:34 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-8.tower-119.messagelabs.com with SMTP;
	15 Nov 2006 19:09:34 -0000
Received: from il06exb01.corp.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id kAFJ9XoU004935
	for <mip4@ietf.org>; Wed, 15 Nov 2006 12:09:33 -0700 (MST)
Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18])
	by il06exb01.corp.mot.com (8.13.1/8.13.0) with ESMTP id kAFJ9XgH021418
	for <mip4@ietf.org>; Wed, 15 Nov 2006 13:09:33 -0600 (CST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C708E9.95670D1D"
Date: Wed, 15 Nov 2006 14:09:32 -0500
Message-ID: <BE4B07D4197BF34EB3B753DD34EBCD1301223BFF@de01exm67.ds.mot.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: IETF 67 Meeting Minutes
Thread-Index: AccI6ZUDMKXr4tmtQqeJ8X1y6yGoAA==
From: "McCann Peter-A001034" <pete.mccann@motorola.com>
To: <mip4@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a492040269d440726bfd84680622cee7
Subject: [Mip4] IETF 67 Meeting Minutes
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C708E9.95670D1D
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Please find the draft meeting minutes attached.  Please send any
corrections
to the mip4 list ASAP.

-Pete

------_=_NextPart_001_01C708E9.95670D1D
Content-Type: text/plain;
	name="mip4minutes.txt"
Content-Transfer-Encoding: base64
Content-Description: mip4minutes.txt
Content-Disposition: attachment;
	filename="mip4minutes.txt"

TWVldGluZyBub3RlcyBmb3IgTUlQNCBXRzoNCg0KU3RhcnQgdGltZSAzOjE0cG0NCg0KQWdlbmRh
IHByZXNlbnRlZDoNCg0KTW9iaWxpdHkgZm9yIElQdjQgV0cNCj09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQoNCldF
RE5FU0RBWSwgTm92ZW1iZXIgOCwgMjAwNg0KMTUxMC0xNjEwIEFmdGVybm9vbiBTZXNzaW9uIElJ
DQpIYXJib3IgSXNsYW5kIEkNCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQoNCkNIQUlSUzogSGVucmlrIExldmtv
d2V0eiA8aGVucmlrQGxldmtvd2V0ei5jb20+DQogICAgICAgIFBldGUgTWNDYW5uIDxtY2NhcEBw
ZXRvbmkub3JnPg0KDQpBR0VOREE6DQoNCjEuIFByZWxpbWluYXJpZXMgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIDEwIG1pbiwgQ2hhaXJzDQogICAtIEJsdWUgc2hlZXRz
DQogICAtIE5vdGUgdGFrZXJzDQogICAtIEphYmJlciBzY3JpYmUNCiAgIC0gQWdlbmRhIGJhc2hp
bmcNCg0KMi4gRG9jdW1lbnQgU3RhdHVzICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgMTUgbWluLCBDaGFpcnMNCg0KICAgIEFjdGl2ZToNCiAgICAgIGRyYWZ0LWlldGYtbWlw
NC1kc21pcHY0CQkJCUFjdGl2ZSAJSGVucmlrDQogICAgICAtIENvbW1lbnRzIHJlcXVlc3RlZA0K
DQogICAgICBkcmFmdC1pZXRmLW1pcDQtZm1pcHY0CQkJICAJQWN0aXZlIAlQZXRlICANCiAgICAg
IC0gTGFzdCBDYWxsOiAyMDA2LTA5LTA1DQogICAgICAtIFJldmlzZWQgZHJhZnQgc3VibWl0dGVk
IDIwMDYtMTAtMjINCg0KICAgICAgZHJhZnQtaWV0Zi1taXA0LWdlbi1leHQJCQkgCUFjdGl2ZQlQ
ZXRlICANCiAgICAgIC0gTGFzdCBDYWxsOiAyMDA2LTEwLTE5DQogICAgICAtIEdvb2QgY29tbWVu
dHMsIHJldmlzZWQgZHJhZnQgbmVlZGVkLg0KDQogICAgICBkcmFmdC1pZXRmLW1pcDQtbWVzc2Fn
ZS1zdHJpbmctZXh0CSAgCUFjdGl2ZSAJSGVucmlrIA0KICAgICAgLSBMYXN0IENhbGw6IDIwMDYt
MDYtMTMNCiAgICAgIC0gTmVlZHMgU2hlcGhlcmQgV3JpdGV1cA0KDQogICAgICBkcmFmdC1pZXRm
LW1pcDQtbW9iaWtlLWNvbm5lY3Rpdml0eSAJICAJQWN0aXZlIAlQZXRlICANCiAgICAgIC0gTGFz
dCBDYWxsOiAyMDA2LTA0LTE0DQogICAgICAtIE5lZWRzIDJuZCBMYXN0IENhbGwsIG5leHQgd2Vl
aw0KDQogICAgICBkcmFmdC1pZXRmLW1pcDQtcmZjMjAwNmJpcyAJCSAgCUFjdGl2ZSAJSGVucmlr
DQogICAgICAtIFJldmlzZWQgZHJhZnQgbmVlZGVkLiBOdWRnZSBuZWVkZWQNCg0KQWN0aW9uIGl0
ZW06IEtlbnQgdG8gcmV2aXNlIGRyYWZ0LCB3YXNuJ3QgY2xlYXIgaGFkIHJlc3BvbnNpYmlsaXR5
LiAgDQpIZW5yaWsgbWVudGlvbmVkIHRoYXQgSGFzc2Ugd2FzIHRoZSByZXZpZXdlci4NCg0KDQog
ICAgUmVjZW50bHkgRXhwaXJlZDoNCiAgICAgIGRyYWZ0LWlldGYtbWlwNC1yYWRpdXMtcmVxdWly
ZW1lbnRzCSAgCUV4cC4gCVBldGUNCiAgICAgIC0gTmVlZHMgcmV2aWV3IQ0KDQpWaWpheSAuLi4g
d2h5IGFyZSB0aGUgcmVxdWlyZW1lbnRzIG5lZWRlZD8NCkhlbnJpayBleHBsYWluIHRoYXQgcmVx
dWlyZW1lbnRzIGRyYWZ0IHdhcyBhc2tlZCB0byBiZSBkb25lLg0KSGVucmlrOiBUaGVyZSB3ZXJl
IHN0cm9uZyBvYmplY3Rpb25zLiBEdXJpbmcgdGhlIGRpc2N1c3Npb24gd2Ugd2VyZSBhcmUgYXNr
ZWQgdG8gZG8gZmlyc3QgdGhlIHJlcXVpcmVtZW50cyBkb2N1bWVudCBhbmQgdGhlbiBmb2xsb3cg
dXAuIEl0IGlzIG5vdCBzb21ldGhpbmcgd2UgdGhvdWdodCB3ZSBuZWVkLCBidXQgd2Ugd2VyZSBh
c2tlZCBmb3IgaXQuDQpNYWRqaWQ6IFdoeSBkbyB3ZSBuZWVkIHRvIGdvIGJhY2sgYW5kIHJlc3Vi
bWl0IGl0LiBUaGUgSUVTRyB3YXMgc3VwcG9zZWQgdG8gcmV2aWV3Lg0KSGVucmlrOiBkbyB5b3Ug
ZXhwZWN0IHRoZSBJRVNHIHRvIGxvb2sgYXQgaXQgaWYgdGhlIFdHIGhhc24ndCBsb29rZWQgYXQg
aXQuIElmIGl0IG5vYm9keSByZWFkIGl0IGl0J3MgYW4gaW5kaXZpZHVhbCBkcmFmdC4NCkphcmk6
IExldCdzIGRvIHRoZSByZXZpZXcgYW5kIG1vdmUgaXQgb24uDQpNYWRqaWQ6IGlzIGl0IHBvc3Np
YmxlIHRvIGRvIHRoZSByZXZpZXcgYW5kIHJlc3VibWl0IGFmdGVyPw0KSGVucmlrOiBZZXMuDQoN
Cg0KICAgICAgZHJhZnQtaWV0Zi1taXA0LXJmYzMzNDRiaXMgCQkgIAlFeHAuIAlIZW5yaWsNCiAg
ICAgIC0gTmV3IHJldmlzaW9uIGFsbW9zdCBzdWJtaXR0ZWQNCg0KUGVya2luczogSW5jb25zaXN0
ZW5jeSBpc3N1ZSB3aXRoIGNvcHlpbmcgVURQIHBvcnQgbnVtYmVyDQpIZW5yaWs6IFB1dCB0aGUg
aXNzdWUgb24gdGhlIE1MDQpQZXRlOiBOZWVkIHRvIHJlc3VibWl0IC0gdGhlIGRyYWZ0IHdhcyBy
ZWplY3RlZCBmcm9tIGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZw0KDQogICAgICBkcmFmdC1pZXRm
LW1pcDQtdnBuLXByb2JsZW0tc29sdXRpb24JICAJRXhwLiAJSGVucmlrIA0KICAgICAgLSBMYXN0
IENhbGw6IDIwMDYtMDQtMjQNCiAgICAgIC0gTmVlZHMgU2hlcGhlcmQgd3JpdGV1cC4NCg0KICAg
IElFU0cgUHJvY2Vzc2luZzoNCiAgICAgIGRyYWZ0LWlldGYtbWlwNC1yZWctdHVubmVsCQkgIAlJ
RVNHICAJUGV0ZSAgDQogICAgICAtIExhc3QgQ2FsbDogU2V2ZXJhbCB0aW1lcywgbGFzdCB0aW1l
IDIwMDQoPykNCiAgICAgIC0gTmV3IHJldmlzaW9uIHN1Ym1pdHRlZCwgbmVlZHMgdmVyaWZpY2F0
aW9uIG9mIGlzc3VlcyBzZXR0bGVkLg0KDQpKYXJpOiBJIGxvb2tlZCBhdCB0aGUgc3BlYywgYW5k
IHRoZSBtYWpvciBjb21tZW50IGZyb20gVmlkeWEgaGFzIGJlZW4NCiAgYWRkcmVzc2VkLCBidXQg
SSBicm91Z2h0IHRoYXQgdXAgdG8gVmlkeWEgYW5kIHNoZSBkaWRuJ3QgYWdyZWUuIElmIHdlDQog
IGNhbid0IGNvbWUgdG8gY29uY2x1c2lvbiwgSSdkIGxpa2UgdG8gc2F5IHRoaXMgdGFyZ2V0cyBl
eHBlcmltZW50YWwgc28NCiAgdGhlIGJhciBpcyBsb3dlci4NCg0KQUNUSU9OIElURU0gb24gY2hh
aXJzOiBnZXQgVmlkeWEsIGF1dGhvcnMgYW5kIGNoYWlycyB0b2dldGhlci4NCg0KICAgIFJGQy1F
ZGl0b3IncyBRdWV1ZToNCiAgICAgIGRyYWZ0LWlldGYtbWlwNC1yZmMzMDEyYmlzCQkgIAlSRkMg
RWQgUXVldWUJDQogICAgICBkcmFmdC1pZXRmLW1vYmlsZWlwLWxvd2xhdGVuY3ktaGFuZG9mZnMt
djQgIAlSRkMgRWQgUXVldWUJDQoNCjMuIE5ldyBjaGFydGVyIHByb3Bvc2FscyAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIA0KDQozLjEgTUlQdjQgYmFzZWQgTW92aW5nIE5ldHdvcmsg
KE5FTU8pIHN1cHBvcnQJCSAgNSBtaW4sIENoYWlycw0KDQogICAgSXQgYmVlbiBwcm9wb3NlZCB0
byBzdGFuZGFyZGlzZSBzb21lIG1vdmluZyBuZXR3b3JrDQogICAgc3VwcG9ydCwgYW5kIGEgcHJv
cG9zZWQgY2hhcnRlciBhZGRpdGlvbiBoYXMgcmVjZWl2ZWQNCiAgICBmYXZvdXJhYmxlIHN1cHBv
cnQgb24gdGhlIG1pcHY0IGxpc3QuDQoNCkhlbnJpazogSSdkIGxpa2UgdG8gYXNrIHBlb3BsZSBo
ZXJlIHJlZ2FyZGluZyB0aGUgYmFzZSBtb3ZpbmcgbmV0d29yaw0KICBzdXBwb3J0LiBEbyBwZW9w
bGUgaGF2ZSBjb21tZW50cz8NClNyaTogd2hhdCBoYXBwZW5lZCB0byAzNTE5YmlzIGRyYWZ0Pw0K
SGVucmlrOiBuZWVkIHRvIG1ha2Ugc3VyZSBpdCdzIG9uIHRoZSBjaGFydGVyDQpTcmk6IGFsbW9z
dCBkb25lIHdpdGggY2hhbmdlcw0KDQpWb3RlIGZvciB3b3JrIGl0ZW06DQoNCnllczogMTANCm5v
OiAwDQoNCmNoYXJsZXMgUGVya2luczogUkZDIDIwMDIgaGFzIHRleHQgYWJvdXQgTW9iaWxlIFJv
dXRlciAtIG5vDQogIG9wcG9zaXRpb24sIEkganVzdCBub3RlZCB0aGF0IGl0J3MgYSBnb29kIGlk
ZWEgdG8gYmUgbW9yZSBzcGVjaWZpYw0KICBhYm91dCB3aGF0IGlzIHRoZSBzcGVjaWZpYyBjaGFu
Z2UgaW4gY2hhcnRlcg0KDQpIZW5yaWs6IFRoZSBjaGFydGVyIHRleHQgd2FzIHBvc3RlZCB0byB0
aGUgbGlzdCwgcGxzIGNvbW1lbnQuDQpIZW5yaWs6IFRoZSByb29tIGlzIGluIGFncmVlbWVudCB3
aXRoIHRoZSBsaXN0IHNvIHdlJ2xsIHRha2UgdGhpcyBvbi4NCg0KDQozLjIuIEdlbmVyaWMgbm90
aWZpY2F0aW9uIG1lY2hhbmlzbSAgICAgICAgICAgICAgICAgICAgICAgNSBtaW4sIENoYWlycw0K
DQogICAgZHJhZnQtZGVuZy1taXA0LWdlbmVyaWMtbm90aWZpY2F0aW9uLW1lc3NhZ2UtMDIudHh0
DQoNCiAgICBJdCBoYXMgYmVlbiBwcm9wb3NlZCB0byBhbHNvIGFkZCB0aGlzIGFzIGEgd29yayBp
dGVtDQogICAgdG8gdGhlIGNoYXJ0ZXIsIGFuZCB0aGUgbGlzdCByZXNwb25zZSBoYXMgYmVlIGZh
dm91cmFibGUNCg0KVm90ZSBmb3Igd29yayBpdGVtOg0KeWVzOiA3DQpubzogMA0KDQoNCjQuIEZN
SVB2NCB1cGRhdGVzICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICA1IG1p
biwgUmFqZWV2DQoNCiAgIGRyYWZ0LWlldGYtbWlwNC1mbWlwdjQNCg0KVmlqYXkgcHJlc2VudGVk
IFdHTEMgcmV2aXNpb25zLiAgTW9zdCB3ZXJlIGNsYXJpZmljYXRpb25zIGluIHRoZSBkZXNjcmlw
dGlvbi4NCg0KUHJvdG9jb2wgZm9yIHY2IHdhcyBzaW1wbGVyIGJlY2F1c2Ugd2UgZGlkbid0IGhh
dmUgdG8gZGVhbCB3aXRoDQpmb3JlaWduIGFnZW50IGFuZCBjb2xsb2NhdGVkIGNhcmUtb2YgYWRk
cmVzcyBtb2RlLiBXZSBjbGFyaWZpZWQgdGhlDQp0ZXh0IHRvIGV4cGxhaW4gYmV0dGVyIHRoZSBG
QSBjYXJlLW9mIG1vZGUvY29sbG9jYXRlZCBjYXJlLW9mIG1vZGVzLg0KDQpyZXZlcnNlIHR1bm5l
bGluZyBmcm9tIE1OIHRvIEhBDQoNCk5ldyBzZWN0aW9uIGFkZGVkICJGYWN0b3JzIEFmZmVjdGlu
ZyBIYW5kb3ZlciIuICBOZWVkIHJldmlldy4NCkJldHRlciBleHBsYW5hdGlvbiBvZiB3aGF0IHdl
J3JlIHRyeWluZyB0byBvcHRpbWl6ZSwgZGVsYXlzIGZhY3Rvcg0KY29udHJpYnV0aW5nIHRvIG92
ZXJhbGwgcGljdHVyZS4NCg0KUGV0ZTogYW55IGNvbW1lbnQ/IE5vIGNvbW1lbnQuDQoNCg0KNS4g
VGhlIE1JUHY0IG5lbW8gYmFzZSBkb2N1bWVudAkJCQkgIDUgbWluLCBBbGV4IFAuDQoNCiAgIGRy
YWZ0LWlldGYtbmVtby12NC1iYXNlDQoNCiAgIFRoaXMgZG9jdW1lbnQgd2FzIGVhcmxpZXIgaGFu
ZGxlZCBieSB0aGUgTkVNTyB3b3JraW5nDQogICBncm91cC4gIElmIHRoZSBuZXcgY2hhcnRlciBj
b250YWluaW5nIHdvcmsgb24gTUlQdjQNCiAgIG1vdmluZyBuZXR3b3JrcywgaXQgaXMgZXhwZWN0
ZWQgdGhhdCB0aGlzIHdpbGwgYmUgdGhlDQogICBiYXNlIGRvY3VtZW50IHRha2VuIGZvcndhcmQg
YnkgdGhlIE1JUDQgd29ya2luZyBncm91cC4NCg0KQWxleCBwcmVzZW50ZWQgbmVtbyBiYXNpYyBz
dXBwb3J0LiAgVGhpcyBkb2N1bWVudCB3YXMgcHJlc2VudGVkIHRvIE5FTU8gV0cuDQpGaXJzdCBw
cmVzZW50YXRpb24gb2YgdGhpcyB0b3BpYyBpbiB0aGlzIFdHLiBSRkMzMzQ0IGFscmVhZHkgaGFz
DQpsYW5ndWFnZSBhYm91dCBpdC4gVGhlIHByb3RvY29sIGlzIGFuIGV4dGVuc2lvbiB0byBtaXA0
IHdoaWNoIGFsbG93cw0KZm9yIG1vdmVtZW50IG9mIGhvc3QgYmVoaW5kIGEgbW9iaWxlIHJvdXRl
ci4NCg0KVGhlIHByb3RvY29sIHdhcyBmaXJzdCBwcmVzZW50ZWQgdG8gTkVNTyBXRyB3aGljaCBo
YXMgYWxyZWFkeSBkZXNpZ25lZA0KMzk2MyBmb3IgdjYgbW92aW5nIG5ldHdvcmtzLiBXZSBsYXN0
IGNhbGxlZCB0aGF0IGRvY3VtZW50IGluIE5FTU8uDQoNClRoZSBwcm90b2NvbCBpcyB2ZXJ5IHNp
bXBsZTogaXQgZXh0ZW5kcyByZWdpc3RyYXRpb24gcmVxdWVzdCBhbmQNCnJlcGx5LiBUaGUgRm9y
ZWlnbiBhZ2VudCBpc24ndCBpbnZvbHZlZCBpbiB0aGlzIHByb3RvY29sLg0KDQpUaGUgTU4gZG9u
J3QgbmVlZCB0byBoYXZlIG1vYmlsaXR5IHN1cHBvcnQuDQoNCkl0IHVzZXMgYSBwcmVmaXggdGFi
bGUgdG8gZG8gc2VjdXJpdHkgY2hlY2tzIHdoZXJlIGEgcm9ndWUgTVIgcHJldGVuZA0KdG8gb3du
IGEgcHJlZml4IG93biBieSBhbm90aGVyIGxlZ2l0aW1hdGUgTVIuDQogICAgICAgICAgICAgICAg
IA0KVGhlc2UgYXJlIHRoZSBleHRlbnNpb25zIHBhcmFtZXRlcnMuIFlvdSBjYW4gaGF2ZSBzZXZl
cmFsIHByZWZpeGVzIGluDQp0aGlzIHBhcmFtZXRlcnMgYm90aCBpbiByZXF1ZXN0IGFuZCByZXBs
eS4NCg0KVGhlcmUgYXJlIHR3byBtb2RlIG9mIG9wZXJhdGlvbjogZXhwbGljaXQgYW5kIGltcGxp
Y2l0LiANCkltcGxpY2l0IGlzIGxpa2UgaW4gMzM0NC4gRXhwbGljaXQgZXhwb3NlcyB0aGUgcHJl
Zml4ZXMgaW4gdGhlc2UNCm1lc3NhZ2VzIGFuZCBzaG91bGQgaGVscCBkZWJ1Z2dpbmcuDQoNCldl
IHdlbnQgdGhyb3VnaCBzZXZlcmFsIFdHIG1lZXRpbmcsIHdlIHdlbnQgdG8gTEMgaW4gTkVNTy4g
Tm90IG1hbnkgY29tbWVudHMuIA0KDQpXZSBoYXZlIGFuIGV0aGVyZWFsIGltcGxlbWVudGF0aW9u
IGRlY29kaW5nIHBhY2tldHMuIFdlIGRvbid0IGhhdmUgeWV0DQpJQU5BIG51bWJlcnMsIGl0IHdv
dWxkIGJlIGdyZWF0IGlmIHdlIGNvdWxkIG9idGFpbiB0aGVtIGluc3RlYWQgb2YNClRCQS4NCg0K
VGhlIGRyYWZ0IG9yaWdpbmFsbHkgaGFkIHZlcnkgbXVjaCB0ZXh0IHRyeWluZyB0byBkZWFsIHdp
dGggbWFueQ0KYXNwZWN0cy4gQGUgcmVhbGl6ZWQgdGhhdCBpdCdzIHZlcnkgY29tcGxleCBhbmQg
Y29tcGxpY2F0ZWQgdG8gbWFrZQ0KZXZlcnlib2R5IGhhcHB5IC0tIE1SLCBIQSwgRkEuDQpXZSB0
cmllZCB0byBzZXBhcmF0ZSBleHRlbnNpb25zIGJldHdlZW4gdGhvc2UuDQoNClZpamF5IHNhaWQg
Y3VycmVudCBIQSBzZXRzIHVwIGEgdHVubmVsIHRvIENvQSBhbmQgYW5vdGhlciB0dW5uZWwgdG8N
Ck1SJ3MgSG9tZSBBZGRyZXNzLg0KDQpSZW1vdmUgb3B0aW1pemF0aW9uIG1ldGhvZC4NCg0KVmlq
YXk6IHRoZSBJQU5BIG51bWJlcnMsIEkgZG9uJ3QgdGhpbmsgeW91IGdldCBudW1iZXJzIGJlZm9y
ZSB5b3UgZ2V0DQppbnRvIHRoZSBxdWV1ZS4NCg0KQWxleDogWWVzIHRoYXQncyB0cnVlLCBidXQg
d2Ugd291bGQgbGlrZSB0byBoYXZlIGZvciBpbnRlcm9wZXJhYmlsaXR5Lg0KDQpWaWpheTogU29t
ZXRoaW5nIHdlJ3ZlIGRvbmUgaW4gdGhlIHNwZWMgaXMgdG8gcmVjb21tZW5kIHZhbHVlcyBpbiB0
aGUNCnNwZWMsIGFuZCBhc2tpbmcgdGhleSB3ZXJlIHJlbW92ZWQgd2hlbiBpbiB0aGUgUkZDIGVk
aXRvci4gQnV0IGlzIGhhcw0KcHJvYmxlbS4NCg0KSGVucmlrOiBZZXMgcGxlYXNlIGRvbid0IGRv
IHRoYXQsIGJ1dCByYXRoZXIgdXNlIGV4cGVyaW1lbnRhbCB2YWx1ZXMNCmFzIHBlciB0aGUgZ3Vp
ZGVsaW5lcyB3ZSBoYXZlIGVzdGFibGlzaGVkLg0KDQpBbGV4OiBPayB3ZSdsbCB1c2UgZXhwZXJp
bWVudGFsIHZhbHVlcy4gT0sgdGhhdCB3YXMgbGFzdCBpc3N1ZS4NCg0KR2VvcmdlczogWW91J3Jl
IGdvaW5nIHRvIHJlbW92ZSBvbGQgdGV4dCBhYm91dCBmb3JlaWduIGFnZW50PyBUaGUgc3BlYw0K
d2lsbCBkZXNjcmliZSBwcm90b2NvbCBiZXR3ZW4gTVIgYW5kIEhBIGFuZCB3aWxsIGhhdmUgbm90
aGluZyB0byBkbw0Kd2l0aCBGQT8NCg0KQWxleDogVGhhdCdzIHRoZSBpbnRlbnQsIGJ1dCB3ZSBt
aWdodCB3YW50IHRoYXQgdG8gd29yayB3aXRoDQp1bm1vZGlmaWVkIDMzNDQgRkENCg0KSGVucmlr
OiBTb21ldGhpbmcgbW9yZSBhYm91dCBleHBlcmltZW50YWwgdmFsdWVzLiBJbiBjYXNlIGV2ZXJ5
Ym9keSBkb2Vzbid0IGtub3cgdGhpcywgNDA0NiBkZXNjcmliZXMgZ3VpZGVsaW5lcyBvbiBob3cg
dG8gdXNlIHZhbHVlcyBmb3IgZXhwZXJpbWVudGluZy4NCg0KQWxleDogQnV0IGl0IHN0aWxsIG5l
ZWQgdG8gYmUgYWdyZWVkIGFib3V0IHZhbHVlcy4uLi4NCg0KLi4uDQoNCktlbnQ6IENvbW1lbnQg
ZnJvbSBWaWpheSwganVzdCB3YW50IHRvIG1ha2Ugc3VyZS4gDQpDb21tZW50IG9uIHJlbW92aW5n
IHNvbWUgb3B0aW1pemF0aW9uLiBGb3Igb3B0aW1pemluZyAuLi4gaW4gQ0NvQSBtb2RlLi4uLg0K
DQpBbGV4OiAuLiBpdCdzIG5vdCBlbm91Z2ggZm9yIGltcGxlbWVudGVycy4gUGVyaGFwcyBoYXZl
IG1vcmUgY29tcGxldGUNCmRlc2NyaXB0aW9ucyBidXQgb3V0c2lkZSBvZiB0aGUgYmFzZS4NCg0K
S2VudDogVGhlIHVub3B0aW1pemVkIHdvdWxkIGJlIGluIHRoZSBkcmFmdC4uLg0KDQpBbGV4OiBX
ZSBzaG91bGQgZGlzY3VzcyB0aGF0IGxhdGVyLg0KDQpLZW50OiBXaGF0IHdlJ3JlIHRyeWluZyB0
byBhY2NvbXBsaXNoIGlzIHN1cHBvcnQgb2YgbGVnYWN5IEZBLiBJIGRvbid0DQp0aGluayB0aGF0
IHdlIGNhbiAuLi4uDQoNCkdlb3JnZXM6IFRoZSBvcHRpbWl6YXRpb24gdGhhdCB5b3UncmUgdGFs
a2luZyBhYm91dCBpcyAuLi4NCg0KQWxleDogLi4uDQoNCkdlb3JnZXM6IFRoZXJlJ3Mgbm8gRkEg
aW4gdGhpcyBjYXNlLiBXZSBjYW4gYWRkIHRoaXMgdG8gdGhlIEZBDQpleHRlbnNpb24uIEl0IGlz
IG5vdCBjbGVhciBpZiB0aGF0IGNvb3JkaW5hdGlvbiBpcyBuZWVkZWQuDQoNCkFsZXg6IEl0IG1p
Z2h0IGJlIHRoYXQgaW4gcHJhY3RpY2UgdGhpcyBvcHRpbWl6YXRpb24gZG9lc24ndCByZXF1aXJl
DQpvcHRpbWl6YXRpb24gYXQgdGhlIEZBLg0KDQpIZW5yaWs6IHdoYXQgd2lsIGhhcHBlbiBiZWZv
cmUgd2UgZGVjaWRlIGlzIGEgbmV3IGNoYXJ0ZXIsIHRoZW4gd2UgY2FuDQpkZWNpZGUuIEkgZG9u
J3QgZXhwZWN0IGFueSBwcm9ibGVtIHdpdGggaXQsIGJ1dCB0aGF0J3MgdGhlIGZvcm1hbCB3YXkN
Cm9mIGRvaW5nIGl0Lg0KDQpBbGV4OiBPayB0aGFua3MuDQoNCg0KDQo2LiBNSVB2NCBuZW1vIGV4
dGVuc2lvbiBkb2N1bWVudHMJCQkgMTAgbWluLCBHZW9yZ2UNCg0KICAgZHJhZnQtdHNpcnRzaXMt
bmVtb3Y0LWR5bmFtaWMNCiAgIGRyYWZ0LXRzaXJ0c2lzLW5lbW92NC1mYQ0KDQoNCkdlb3JnZSBw
cmVzZW50ZWQgRFNNSVB2NCB1cGRhdGUNCg0KV0cgZHJhZnQgcHVibGlzaGVkIGluIEp1bHksIHNp
bmNlIHRoZW4gaW50ZWdyYXRlZCBjb21tZW50cyBhbmQNCmNvcnJlY3Rpb25zIHBsdXMgY2xhcmlm
aWNhdGlvbnMsIHNvb24gdjAxLg0KDQpUaGlzIHByZWZpeCBkZWxlZ2F0aW9uIHRleHQuIHRoZSBz
cGVjIGFsbG93cyBmb3IgdHdvIHdheXMgLi4uDQoNCi4uLiBJIGhhdmUgdG8gcmV2aWV3IHRoZSBw
cmVmaXggZGVsZWdhdGlvbnMNCg0KU3JpOiBzbyB5b3UgdHJ5IHRvIC4uLg0KDQpHZW9yZ2VzOiBJ
J20ganVzdCB0cnlpbmcgdG8gdXNlIGFzIGlzLCBzbyB0aGF0IEkgZG9uJ3QgaGF2ZSB0byBjaGFu
Z2UgaXQuDQoNCk5vdyBkaXNjdXNzaW5nIE5FTU92NCBleHRlbnNpb25zDQoNCnlvdSBoYXZlIGlt
cGxpY2l0IG9yIGV4cGxpY2l0IG1vZGUuIER5bmFtaWMgbW9kZSBhbGxvdyBwcmVmaXggdG8gYmUN
CnNlbnQgZnJvbSBNTiB0byBIQSBzZXQgdG8gemVybyBzbyB0aGF0IGFnZW50IGNhbiBmaWxsIGlu
Lg0KDQpTcmk6IERIQ1AgUEQgZHJhZnQgYnkgUGFzY2FsLCBpcyB0aGlzIHVzZWQgaW4gdGhpcyBk
cmFmdD8NCkdlb3JnZTogTm90IGNsZWFyIGlmIGFueXRoaW5nIG5lZWRzIHRvIGJlIGNoYW5nZWQN
Cg0KTmV4dCBzdGVwOiBhY2NlcHQgYXMgV0cgaXRlbXM/IEl0J3MgbGlua2VkIHRvIHRoZSBiYXNl
IHN1cHBvcnQuDQoNCkFsZXg6IFRoZSBESENQIGR5bmFtaWMgYWxsb2NhdGlvbiwgaWYgd2UgaGF2
ZSBhIGNsZWFyIGlkZWEgYWJvdXQgSEENCmJlaW5nIGEgc2VydmVyIGFuZCB0aGUgTVIgYSByZWxh
eSBhbmQgdGhlIGZvcmVpZ24gYWdlbnQgYSBzdWItc3VicmVsYXkNCkkgdGhpbmsgLi4uLiBZb3Ug
c2FpZCB0aGF0IEhBIGFsbG9jYXRlcyBIb21lIG5ldHdvcmsgcHJlZml4IHRvIE1SLiBJDQp0aGlu
ayBpdCdzIG5vdCBhbHdheXMgdGhlIGNhc2UuDQoNCkdlb3JnZXMgOiBpdCBpcyBhIHJlbGF5DQoN
CkFsZXg6IHNvIGlmIGl0IGlzIHJlbGF5IGl0IGRvZXNuJ3QgYWxsb2NhdGUgYW55dGhpbmcgSSdk
IGxpa2UgdG8gc2F5DQp0aGF0IEZBIGNhbiBhbHNvIGRvIGl0Lg0KDQpBbGV4OiBUaGUgRkEgYW5k
IEhBIGNvdWxkIGJlIGxpbmtlZC4gQXJlIHlvdSBvcGVuIHRvIG1vZGlmeSB0aGUgZGVzY3JpcHRp
b24/DQoNCkhlbnJpazogb24gYSBoaWdoIGxldmVsIEkgd2FudCB0byBzYXkgdGhhdCBwcm92aWRl
ZCB0aGF0IHdlIHRha2Ugb24NCnRoaXMgd29yayAoaSB0aGluayB3ZSBzaG91bGQpIHRoZXNlIGFy
ZSBuYXR1cmFsIHdheXMgb2YgZG9pbmcgdGhpbmdzLA0KaW4gZ2VuZXJhbCBpdCBtYWtlcyBzZW5z
ZS4NCg0KUGV0ZTogc2hvdyBoYW5kcy4uIGhvdyBtYW55IHBlb3BsZSB0aGluayB3ZSBzaG91bGQg
aGF2ZSB0aGF0IGluIHRoZQ0KY2hhcnRlcjogMTUuIE9wcG9zZWQ6IG5vbmUuDQoNCg0KDQpHZW9y
Z2U6IEFzayBXRyB0byByZXZpZXcgdGhlIEZsb3cgSUQgRXh0IGRyYWZ0LCBub3QgcmVxdWVzdGlu
ZyBhcyBXRyBpdGVtDQoNCkphcmk6IEkgdGhpbmsgdGhlcmUncyBlbm91Z2ggb24gdGhlIGNoYXJ0
ZXIsIHNvIGxldCdzIG5vdCBnbyB0aGVyZS4NCg0KS2VudDogbWFrZSBzdXJlIHRoYXQgMjc5NGJp
cyBkaWRuJ3QgZmFsbCBvZmYgdGhlIFdHIGNoYXJ0ZXINCg0KUGV0ZTogZXhwZWN0IGEgbmV3IHZl
cnNpb24gdG8gYmUgcHVibGlzaGVkIGFuZCByZXZpZXdlZCBieSBXRw0KDQoNCkVuZCBtZWV0aW5n
OiA0OjAzcG0NCg0KDQoNCg0K

------_=_NextPart_001_01C708E9.95670D1D
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

------_=_NextPart_001_01C708E9.95670D1D--




From mip4-bounces@ietf.org Wed Nov 15 14:15:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GkQDt-0005SX-KF; Wed, 15 Nov 2006 14:15:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GkQDt-0005SI-1o
	for mip4@ietf.org; Wed, 15 Nov 2006 14:15:01 -0500
Received: from mail119.messagelabs.com ([216.82.241.179])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GkQDq-0000hZ-QN
	for mip4@ietf.org; Wed, 15 Nov 2006 14:15:01 -0500
X-VirusChecked: Checked
X-Env-Sender: pete.mccann@motorola.com
X-Msg-Ref: server-6.tower-119.messagelabs.com!1163618096!10754841!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [144.189.100.105]
Received: (qmail 24261 invoked from network); 15 Nov 2006 19:14:56 -0000
Received: from motgate5.mot.com (HELO motgate5.mot.com) (144.189.100.105)
	by server-6.tower-119.messagelabs.com with SMTP;
	15 Nov 2006 19:14:56 -0000
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate5.mot.com (8.12.11/Motorola) with ESMTP id kAFJEuER019424
	for <mip4@ietf.org>; Wed, 15 Nov 2006 12:14:56 -0700 (MST)
Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id kAFJEtNY023400
	for <mip4@ietf.org>; Wed, 15 Nov 2006 13:14:55 -0600 (CST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] IETF 67 Meeting Minutes
Date: Wed, 15 Nov 2006 14:14:54 -0500
Message-ID: <BE4B07D4197BF34EB3B753DD34EBCD1301223C04@de01exm67.ds.mot.com>
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD1301223BFF@de01exm67.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] IETF 67 Meeting Minutes
Thread-Index: AccI6ZUDMKXr4tmtQqeJ8X1y6yGoAAAAJjQw
From: "McCann Peter-A001034" <pete.mccann@motorola.com>
To: <mip4@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Forgot to mention: many thanks to Kent Leung and Julien Laganier for
taking the notes
during the meeting.

-Pete

McCann Peter-A001034 wrote:
> Please find the draft meeting minutes attached.  Please send any
> corrections to the mip4 list ASAP.=20
>=20
> -Pete


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Nov 16 18:31:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gkqhr-0007oW-Bj; Thu, 16 Nov 2006 18:31:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gkqhp-0007oP-Se
	for mip4@ietf.org; Thu, 16 Nov 2006 18:31:41 -0500
Received: from usaga01-in.huawei.com ([12.129.211.51])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gkqhm-0005rr-5z
	for mip4@ietf.org; Thu, 16 Nov 2006 18:31:41 -0500
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J8U00I81K0L5K@usaga01-in.huawei.com> for
	mip4@ietf.org; Thu, 16 Nov 2006 15:31:34 -0800 (PST)
Received: from N737011
	(pool-71-112-12-134.sttlwa.dsl-w.verizon.net [71.112.12.134])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with ESMTPA id <0J8U001AXK0DZW@usaga01-in.huawei.com> for mip4@ietf.org;
	Thu, 16 Nov 2006 15:31:33 -0800 (PST)
Date: Thu, 16 Nov 2006 15:31:26 -0800
From: Madjid Nakhjiri <mnakhjiri@huawei.com>
Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.
In-reply-to: <BE4B07D4197BF34EB3B753DD34EBCD13011B0AB4@de01exm67.ds.mot.com>
To: 'McCann Peter-A001034' <pete.mccann@motorola.com>,
	'Arun SG' <arunsg@airvana.com>, mip4@ietf.org
Message-id: <004401c709d7$570a2610$2f01a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AccB66vzD1uvoeyxTEe6mCzho4JntQASU/1AABeY49AAF3ZnEAAZXchAAZ/vHIA=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7118f330e2af0a096ba071c5e99ca10e
Cc: 'Madjid Nakhjiri' <mnakhjiri@huawei.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Actually there is the draft-nakhjiri-radius-mip4-02.txt that was submitted
to mip4 WG for specifying how this can be supported through RADIUS. That
draft is now expired. We have not submitted a new version, since the IESG
asked us to submit a requirement document first stating that we will not try
to improve RADIUS functionality for support of MIP4. The work is pending
working group review of the requirement work
draft-ietf-mip4-radius-requirements-00.txt by the wG and later IESG. The
requirement doc has also expired, and we need to resubmit it, with a new
date basically:) If you are interested and cannot find these drafts over the
web, let me and know and I send it to you.
My plan is to submit the requirement-01 as soon as I get to it. But that
should not stop people from reviewing it, all that is going to change is the
doc date.

Thanks and Regards,

Madjid

-----Original Message-----
From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com] 
Sent: Wednesday, November 08, 2006 8:58 AM
To: Arun SG; mip4@ietf.org
Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.

RFC 4004 describes a Diameter application that can be used
by the FA to verify the challenge-response and propagate
the Registration Request to a home agent in another domain.

There is not currently an IETF specification for what happens
in RADIUS but we may be taking up that work in future.

-Pete

Arun SG wrote:
> Thanks, Peter.
> This is certainly helpful. Is there work underway that would cover
> the FA action in case of MN-AAA authentication ? 
> Arun
> 
> -----Original Message-----
> From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com]
> Sent: Tuesday, November 07, 2006 11:12 PM
> To: Arun SG; mip4@ietf.org
> Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.
> 
> Hi, Arun,
> 
> Arun SG wrote:
>> Hello,
>> Please refer to the old thread pasted below. Can someone please
>> provide a few followup clarifications ?
>> 
>> 1. What is the current status of 3012bis?
> 
> 3012bis is currently in AUTH48, one of the very last stages before
> publication.  I think we are still waiting on responses from a couple
> of the authors.  
> 
>> 2. This para in 3012 and 3012bis states:
>> 
>> If the MN-AAA Authentication extension (see Section 6) is present in
>> the message, or if an NAI extension is included indicating that the
>> mobile node belongs to a different administrative domain, the foreign
>> agent may take actions outside the scope of this protocol
>> specification to carry out the authentication of the mobile node.
>> 
>> Does this then mean that this specification is restricted to the case
>> when the MN, FA and AAA all belong to the same administrative domain?
> 
> Certainly not.  It just says that the action taken by the FA to
> validate the MN-AAA extension is outside the scope of this document. 
> 
>> 3. While CHAP_SPI declares that MD5 is to be used, I could not find a
>> description of how the "key" that is to be used in MD5 is obtained.
>> Is there an implicitly understanding that this is preshared, or
>> perhaps obtained through some other key exchange mechanims ?
> 
> The "key" is a long-term secret shared between the MN and the home
> AAA server.  It is configured using out-of-band mechanisms that are
> outside the scope of 3012.  
>> 
>> MD5      (High-order byte from Challenge || Key || <<<<------is this
>> thru' IKE or some other means?
>>         MD5(Preceding Mobile IP data ||
>>         Type, Subtype (if present), Length, SPI) ||
>>         Least-order 237 bytes from Challenge))
>> 
>> Thanks in advance,
>> Arun
> 
> Hope this helps.
> 
> -Pete
> 
>> 
>> 
>> RE: [Mip4] Query regarding MN-AAA authenticator calculation.
>> 
>> 
>
------------------------------------------------------------------------
>> --------
>> 
>> To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri at motorola.com>
>> Subject: RE: [Mip4] Query regarding MN-AAA authenticator calculation.
>> From: Kent Leung <kleung at cisco.com>
>> Date: Fri, 04 Mar 2005 17:21:21 -0800
>> Cc: "'Pete McCann'" <mccap at lucent.com>, Archana <archana_p at
>> huawei.com>, mip4 at ietf.org In-reply-to:
>> <EBF631554F9CD7118D0B00065BF34DCB18379493@il27exm03.cig.mot .com>
>> List-help: <mailto:mip4-request@ietf.org?subject=help>
>> List-id: Mobility for IPv4 <mip4.ietf.org>
>> List-post: <mailto:mip4@ietf.org>
>> List-subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
>> <mailto:mip4-request@ietf.org?subject=subscribe>
>> List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
>> <mailto:mip4-request@ietf.org?subject=unsubscribe>
>> Sender: mip4-bounces at ietf.org
>> 
>> 
>
------------------------------------------------------------------------
>> --------
>> 
>> Hi Madjid.  The rfc3012bis draft covers the CCoA mode.
>> 
>> 
>> Based on local policy, a Mobile Node with co-located care-of-address
>>    MAY include the Mobile-AAA Authentication extension in
>>    Registration Request.  In this case, if the Mobile Node uses SPI
>>    value of CHAP_SPI or HMAC_CHAP_SPI (section 8) in the MN-AAA
>>    Authentication extension, Mobile Node MUST include the
>>    Mobile-Foreign Challenge extension prior to the Mobile-AAA
>>    Authentication extension.  The mechanism used by the Mobile Node
>>    to obtain the Challenge value is outside the scope of this
>> document. 
>> 
>> Kent
>> 
>> 
>> At 03:52 PM 3/4/2005 -0600, Nakhjiri Madjid-MNAKHJI1 wrote:
>> Hi,
>> 
>> I have been meaning to respond to this as well. I agree there is no
>> RADIUS MD5. However, there is a problem with sending all the
>> following 
>> 
>> 
>> Preceding Mobile IP data ||
>>         Type, Subtype (if present), Length, SPI) ||
>>        Least-order 237 bytes from Challenge
>> 
>> Over RADIUS messages, since RADIUS packets can be at most 4K long and
>> attributes at most 253 bytes (if I understood this correctly), which
>> means you do have to calculate a hash of the data above before
>> packing 
> 
>> it over RADIUS messaging, if you want the AAA server to do the same
>> calculations. If anybody has a number on the number of bytes the data
>> above takes, I would appreciate it??
>> We tried to explain this in our draft on RADIUS support for MIP-AAA
>> signaling. 
>> 
>> 
>> http://www.ietf.org/internet-drafts/draft-nakhjiri-radius-mip4-00.txt
>> 
>> We ran into another problem with this and that was: the challenge is
>> used only in conjunctions with FAs and when the MN uses a CcoA and
>> registers through HA directly, there won't be any challenge to
>> calculate 
>> 
>> 
>> MD5      (High-order byte from Challenge || Key ||
>>         MD5(Preceding Mobile IP data ||
>>         Type, Subtype (if present), Length, SPI) ||
>>         Least-order 237 bytes from Challenge))
>> 
>> Our proposal based on Charlie's suggestion (no mean to push the
>> blame, 
> 
>> Charlie :) ) was to include zero octets whenever challenge data was
>> needed in that case. 
>> 
>> 
>> Any thoughts?
>> 
>> Madjid
>> -----Original Message-----
>> From: mip4-bounces at ietf.org [mailto:mip4-bounces at ietf.org] On
>> Behalf Of Pete McCann Sent: Friday, February 25, 2005 9:48 AM
>> To: Archana
>> Cc: mip4 at ietf.org
>> Subject: [Mip4] Query regarding MN-AAA authenticator calculation.
>> 
>> 
>> Hi, Archana,
>> 
>> Archana writes:
>>> Hi
>>> According to RFC 3012, the MN-AAA authenticator is computed by
>>> applying MD5 on the following data
>>> 
>>> High-order byte from Challenge || Key || MD5(Preceding Mobile IP
>>> data 
> 
>>>>> Type, Subtype (if present), Length, SPI) || Least-order 237 bytes
>>>>> from Challenge 
>>> 
>>> I have the following queries regarding the above computation. Any
>>> help in the clarifying them will be highly appreciated.
>>> 
>>> 1. What is meant by High-order and Least order ?
>> 
>> 
>> "High-order" means "most significant".  You can also interpret it as
>> "leftmost" when looking at the encoding of the Challenge in a Mobile
>> IP Extension. 
>> 
>>> 2. How does the Radius MD5 algorithm differ in calculating the
>>> Authenticator from a MD5 algorithm
>> 
>> 
>> There is no special "Radius MD5" as far as I know.
>> 
>> 
>> MD5 is specified in RFC3121.  It is a well-known hash function that
>> processes the input and produces a 16 octet hash.
>> 
>> 
>> The calculation shown above is compatible with existing RADIUS
>> servers 
> 
>> that are used for authenticating PPP/CHAP, i.e., the code used for
>> PPP/CHAP can be re-used to compute the above authenticator, assuming
>> that the FA can precompute the inner MD5 and send it in an
>> Access-Request. 
>> 
>> 
>> -Pete
>> 
>> 
>>  > Thanks in advance
>>  > Archana
>> 
>> 
>> --
>> Mip4 mailing list: Mip4 at ietf.org
>>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>>      Charter page:
>> http://www.ietf.org/html.charters/mip4-charter.html Supplemental
>> site: http://www.mip4.org/ 
>> 
>> 
>> --
>> Mip4 mailing list: Mip4 at ietf.org
>>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>>      Charter page:
>> http://www.ietf.org/html.charters/mip4-charter.html Supplemental
>> site: http://www.mip4.org/ 
>> 
>> --
>>      |           |                   Kent Leung
>>     :|:         :|:                  IP Mobility Development
>>    :|||:       :|||:                 Internet Technologies Division
>>   :|||||||:   :|||||||:              Voice: 408.526.5030
>> .:|||||||||:.:|||||||||:.             Fax:   408.525.1653
>>  c i s c o S y s t e m s             Email: kleung at cisco.com
>> 
>> 
>> --
>> Mip4 mailing list: Mip4 at ietf.org
>>    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>>     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>> Supplemental site: http://www.mip4.org/
>> 
>> 
>> 
>> 
>> 
>> 
>
------------------------------------------------------------------------
>> --------
>> 
>> Prev by Date: RE: [Mip4] Query regarding MN-AAA authenticator
>> calculation. Next by Date: [Mip4] [Deadline Approaching] Final CFP:
>> IEEE WirelessCom Symposium on Mobile Computing, 2005 Previous by
>> thread: RE: [Mip4] Query regarding MN-AAA authenticator calculation.
>> Next by thread: RE: [Mip4] Query regarding MN-AAA authenticator
>> calculation. Index(es):
>> Date
>> Thread
>> Note: Messages sent to this list are the opinions of the senders and
>> do not imply endorsement by the IETF.


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Fri Nov 17 12:52:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gl7sd-00015N-Nw; Fri, 17 Nov 2006 12:51:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gl7sc-00012e-Bj
	for mip4@ietf.org; Fri, 17 Nov 2006 12:51:58 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gl7sX-0002Ms-Cs
	for mip4@ietf.org; Fri, 17 Nov 2006 12:51:58 -0500
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-4.cisco.com with ESMTP; 17 Nov 2006 09:51:53 -0800
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id kAHHpqgu025676
	for <mip4@ietf.org>; Fri, 17 Nov 2006 09:51:52 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id kAHHpqdI017548
	for <mip4@ietf.org>; Fri, 17 Nov 2006 09:51:52 -0800 (PST)
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); 
	Fri, 17 Nov 2006 09:51:52 -0800
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 17 Nov 2006 09:51:52 -0800
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5202DFC6A7@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Proxy Mobile IPv4 in the WG charter
Thread-Index: AccKcRALK3JjuYGhShOIr9RtW9WMJA==
From: "Kent Leung \(kleung\)" <kleung@cisco.com>
To: <mip4@ietf.org>
X-OriginalArrivalTime: 17 Nov 2006 17:51:52.0517 (UTC)
	FILETIME=[10588F50:01C70A71]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2014; t=1163785912;
	x=1164649912; c=relaxed/simple; s=sjdkim7002;
	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<kleung@cisco.com>
	|Subject:=20Proxy=20Mobile=20IPv4=20in=20the=20WG=20charter
	|Sender:=20; bh=Zap5WDsrBQQZQWgz/uPxNituSuFUGKzlIjXPa3Hbmek=;
	b=HIXpaY3m+hoC1meZVPZtJSNHvuTdcHUvz6M93o9XHRbE4Inc1cKnQP6Ri3hKRSu4FnhJGBLT
	hv2Nvgo5+ago+BuvdW89lOVS0NXyPT3/I5QokrJuMM9QLAl+5E9t1Fui;
Authentication-Results: sj-dkim-7; header.From=kleung@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim7002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Subject: [Mip4] Proxy Mobile IPv4 in the WG charter
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1255672779=="
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1255672779==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C70A71.105820AD"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C70A71.105820AD
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi.  The draft-leung-mip4-proxy-mode-01.txt draft describes using Mobile
IPv4 in proxy mode to provide network-based mobility management.  There
will need to be some more work on the draft.  But wanted to get some
sense of support for Proxy Mobile IPv4 in this WG.  Certainly there are
a few SDOs which have either adopted or interested in such mechanism.
=20
Do folks want to take this on as a WG item eventually?
=20
Kent

------_=_NextPart_001_01C70A71.105820AD
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2976" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D187494217-17112006><FONT face=3DArial =
size=3D2>Hi.&nbsp; The <FONT=20
face=3D"Times New Roman">draft-leung-mip4-proxy-mode-01.txt draft =
describes using=20
Mobile IPv4 in proxy mode to provide network-based mobility =
management.&nbsp;=20
There will need to be some more work on the draft.&nbsp; But wanted to =
get some=20
sense of support for Proxy Mobile IPv4 in this WG.&nbsp; Certainly there =
are a=20
few SDOs which have either adopted or interested in such=20
mechanism.</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D187494217-17112006><FONT face=3DArial size=3D2><FONT=20
face=3D"Times New Roman"></FONT></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D187494217-17112006><FONT face=3DArial size=3D2><FONT=20
face=3D"Times New Roman">Do folks want to take this on as a WG item=20
eventually?</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D187494217-17112006><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D187494217-17112006><FONT=20
size=3D2>Kent</FONT></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C70A71.105820AD--


--===============1255672779==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1255672779==--




From mip4-bounces@ietf.org Fri Nov 17 13:27:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gl8Qo-0002XL-En; Fri, 17 Nov 2006 13:27:18 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gl8Qn-0002Wl-N5
	for mip4@ietf.org; Fri, 17 Nov 2006 13:27:17 -0500
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Gl8Qj-0003ZN-5o
	for mip4@ietf.org; Fri, 17 Nov 2006 13:27:17 -0500
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Nov 2006 19:27:03 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter
Date: Fri, 17 Nov 2006 19:26:53 +0100
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB026040F2047@FTRDMEL2.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Proxy Mobile IPv4 in the WG charter
Thread-Index: AccKcRALK3JjuYGhShOIr9RtW9WMJAABJbVg
From: "MORAND Lionel RD-CORE-ISS" <lionel.morand@orange-ftgroup.com>
To: "Kent Leung \(kleung\)" <kleung@cisco.com>,
	<mip4@ietf.org>
X-OriginalArrivalTime: 17 Nov 2006 18:27:03.0867 (UTC)
	FILETIME=[FACF00B0:01C70A75]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: 
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0855218802=="
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0855218802==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C70A75.FA2231EE"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C70A75.FA2231EE
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi, Kent
=20
Could it possible to know which SDOs have adopted or are interested in =
such a solution?
=20
BR,
=20
Lionel


________________________________

	De : Kent Leung (kleung) [mailto:kleung@cisco.com]=20
	Envoy=E9 : vendredi 17 novembre 2006 18:52
	=C0 : mip4@ietf.org
	Objet : [Mip4] Proxy Mobile IPv4 in the WG charter
=09
=09
	Hi.  The draft-leung-mip4-proxy-mode-01.txt draft describes using =
Mobile IPv4 in proxy mode to provide network-based mobility management.  =
There will need to be some more work on the draft.  But wanted to get =
some sense of support for Proxy Mobile IPv4 in this WG.  Certainly there =
are a few SDOs which have either adopted or interested in such =
mechanism.
	=20
	Do folks want to take this on as a WG item eventually?
	=20
	Kent


------_=_NextPart_001_01C70A75.FA2231EE
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2963" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D074432418-17112006><FONT =
face=3DArial=20
color=3D#008000 size=3D2>Hi, Kent</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D074432418-17112006><FONT =
face=3DArial=20
color=3D#008000 size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D074432418-17112006><FONT =
face=3DArial=20
color=3D#008000 size=3D2>Could it possible to know which SDOs have =
adopted or are=20
interested in such a solution?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D074432418-17112006><FONT =
face=3DArial=20
color=3D#008000 size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D074432418-17112006><FONT =
face=3DArial=20
color=3D#008000 size=3D2>BR,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D074432418-17112006><FONT =
face=3DArial=20
color=3D#008000 size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D074432418-17112006><FONT =
face=3DArial=20
color=3D#008000 size=3D2>Lionel</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #008000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Dfr dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>De&nbsp;:</B> Kent Leung (kleung)=20
  [mailto:kleung@cisco.com] <BR><B>Envoy=E9&nbsp;:</B> vendredi 17 =
novembre 2006=20
  18:52<BR><B>=C0&nbsp;:</B> mip4@ietf.org<BR><B>Objet&nbsp;:</B> [Mip4] =
Proxy=20
  Mobile IPv4 in the WG charter<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT face=3DArial =
size=3D2>Hi.&nbsp; The=20
  <FONT face=3D"Times New Roman">draft-leung-mip4-proxy-mode-01.txt =
draft=20
  describes using Mobile IPv4 in proxy mode to provide network-based =
mobility=20
  management.&nbsp; There will need to be some more work on the =
draft.&nbsp; But=20
  wanted to get some sense of support for Proxy Mobile IPv4 in this =
WG.&nbsp;=20
  Certainly there are a few SDOs which have either adopted or interested =
in such=20
  mechanism.</FONT></FONT></SPAN></DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT face=3DArial =
size=3D2><FONT=20
  face=3D"Times New Roman"></FONT></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT face=3DArial =
size=3D2><FONT=20
  face=3D"Times New Roman">Do folks want to take this on as a WG item=20
  eventually?</FONT></FONT></SPAN></DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT=20
size=3D2>Kent</FONT></SPAN></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C70A75.FA2231EE--


--===============0855218802==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0855218802==--




From mip4-bounces@ietf.org Fri Nov 17 15:45:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GlAaF-0005FH-Rn; Fri, 17 Nov 2006 15:45:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gl8Id-0006RW-LM
	for mip4@ietf.org; Fri, 17 Nov 2006 13:18:51 -0500
Received: from dynamo.ecn.purdue.edu ([128.46.200.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gl8I9-0005w9-El
	for mip4@ietf.org; Fri, 17 Nov 2006 13:18:51 -0500
Received: from dynamo.ecn.purdue.edu (localhost [127.0.0.1])
	by dynamo.ecn.purdue.edu (8.13.6/8.13.6) with ESMTP id kAHIICpP006343
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <mip4@ietf.org>; Fri, 17 Nov 2006 13:18:12 -0500 (EST)
Received: (from vr@localhost)
	by dynamo.ecn.purdue.edu (8.13.6/8.13.6) id kAHIIB6S006325
	for mip4@ietf.org; Fri, 17 Nov 2006 13:18:12 -0500 (EST)
Date: Fri, 17 Nov 2006 13:18:12 -0500 (EST)
From: Vijay Raghunathan <vr@ecn.purdue.edu>
Message-Id: <200611171818.kAHIIB6S006325@dynamo.ecn.purdue.edu>
To: mip4@ietf.org
X-Virus-Scanned-ECN: by amavisd-new
X-ECN-Spam-Status: No
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48
X-Mailman-Approved-At: Fri, 17 Nov 2006 15:45:08 -0500
Subject: [Mip4] CFP: SECON 2007 (2 weeks to deadline!)
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org


*************** 2 WEEKS REMAINING TO CONFERENCE DEADLINE! **************

========================================================================
                           CALL FOR PAPERS

                           IEEE SECON 2007

          The Fourth IEEE Communications Society Conference on
          Sensor, Mesh and Ad Hoc Communications and Networks                 
                   http://www.ieee-secon.org/2007/

                             Merged with
IEEE International Workshop on Wireless Ad-hoc & Sensor Networks (IWWAN)

                      San Diego, California, USA
                           June 18-21, 2007
========================================================================

The fourth annual IEEE SECON conference will provide a unique forum to
exchange ideas, techniques, and applications, discuss best practices,
raise awareness, and share experiences among researchers, practitioners,
standard developers and policy makers in the field of sensor, ad-hoc, 
and mesh networks and systems. IEEE SECON grew out of IEEE INFOCOM in 
2004, in order to create an event that focused on the important and 
exciting topics of sensor, mesh and ad-hoc communications and networks.
This year, SECON has been merged with the IEEE International Workshop
on Wireless Ad-hoc and Sensor Networks (IWWAN).

Original technical papers that address the communications, networking,
applications, systems and algorithmic aspects of mesh and sensor
networks, as well as those that describe practical deployment and
implementation experiences are solicited for presentation at the
conference and publication in the conference proceedings. Papers
presenting novel contributions in such disciplines as communications,
networking protocols and architectures, algorithms, embedded systems,
middleware and information management, and novel applications are
solicited.

PAPERS:

Full papers describing original, previously unpublished research
work, experimental efforts, practical experiences, and industrial and
commercial developments in sensor, ad-hoc, and mesh communications and
networks are solicited. Authors are particularly encouraged to submit
papers that have a deep focus on a specific discipline, are stimulated
by the synergistic interaction of diverse disciplines, or describe
practical application of technology to real-world problems. Submitted
papers should not be concurrently under review at any another workshop,
symposium, conference, or journal.

Specific topics of interest include, but are not limited to:

* Architectures and protocols to support wireless communication, 
localization, time synchronization, routing, data dissemination, and 
other distributed services in heterogeneous, large-scale, distributed 
mesh and sensor networks.

* Algorithms and theories for management, supervisory control, and
monitoring of distributed ad-hoc networks, and techniques for the 
interpretation and use of sensor data in decision-making processes.

* Theories and models on fundamental information and communication
aspects of wireless mesh and sensor networks.

* Mechanisms for authenticated, secure communication and data 
dissemination in sensor and mesh networks.

* Algorithms and protocols to support quality of service in mesh and
sensor networks, including admission control, resource allocation and 
fairness, and capacity planning.

* Performance measurement and modeling techniques for large-scale
distributed ad-hoc and sensor networks and their evaluation.

* Integration of sensors into engineered systems, including techniques 
for exploiting on-sensor renewable power sources, mechanisms for online 
self-calibration and self-testing, and schemes to maximize accuracy and 
minimize false alarms.

* Hardware platforms and testbeds incorporating multiple sensors,
embedded processors, actuators, and wireless interfaces.

* Software architectures, middleware, and tools for mesh and sensor
network applications development, deployment, and management.

* Practical implementations, case-studies, and real-world experiences 
in designing and deploying large scale ad-hoc, mesh, and sensor network
applications.

POSTERS, DEMOS, AND EXHIBITS: 

SECON will also include poster/demo sessions that provide an interactive
forum to present work in progress, showcase real system implementations,
highlight industrial/commercial developments, and discuss key research 
challenges in the fields of sensor, mesh, and ad-hoc networks. Details
about the poster and demo submission procedure will soon be available
on the conference web site.

PAPER SUBMISSION INSTRUCTIONS:

Paper submissions will be handled electronically through the EDAS web 
based system. Details about the submission process including formatting
instructions and templates are available at the conference website
located at http://www.ieee-secon.org/2007/.

Accepted papers will be published in the conference proceedings and will
be archived on IEEE Xplore. IEEE Communications Society policy mandates
that all accepted SECON 2007 papers must have at least one associated 
registration at the regular rate. For authors co-authoring  multiple 
papers, one regular registration is valid for up to three papers.

IMPORTANT DATES:

Paper registration: November 30, 2006 (by 11:59pm PST)
Full paper submission: December 7, 2006 (by 11:59pm PST)
Decision notification: February 26, 2007
Camera ready paper due: March 22, 2007

CONFERENCE ORGANIZING COMMITEE:

GENERAL CHAIR:
Rene Cruz, UC San Diego (cruz@ece.ucsd.edu)

VICE-CHAIR:
Wendi Heinzelman, University of Rochester (wheinzel@ece.rochester.edu)

TECHNICAL PROGRAM CO-CHAIRS:
Kevin Almeroth, UC Santa Barbara (almeroth@cs.ucsb.edu)
Robin Kravets, UIUC (rhk@cs.uiuc.edu)

PANELS CO-CHAIRS:
Wenye Wang, NC State University
Al Harris, University of Padova

POSTERS/DEMOs CO-CHAIRS:
Mingyan Liu, University of Michigan
Jie Liu, Microsoft Research

WORKSHOP CHAIR:
Rajeev Shorey, GM Research

PUBLICITY CHAIR:
Vijay Raghunathan, Purdue University

LOCAL ARRANGEMENTS CHAIR:
Curt Schurgers, UC San Diego

EXHIBITS CHAIR:
Cedric Westphal, Nokia

TRAVEL AWARDS CHAIR:
Srinivasan Ramasubramanian, University of Arizona

WEB CHAIR:
Navid Ehsan, UC San Diego

STANDING COMMITTEE: 
Fred Bauer, PacketHop (fred@fredbauer.com) - Chair
Hamid Aghvami, King's College London
Mischa Dohler, France Telecom
Harvey Freeman, Booz Allen Hamilton
Sung-Ju Lee, HP Labs
Prasant Mohapatra, University of California, Davis
Krishna Sivalingam, University of Maryland, Baltimore County

TECHNICAL PROGRAM COMMITTEE:
Available on the conference webpage

========================================================================


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Sun Nov 19 01:27:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Glg8T-0001wd-JI; Sun, 19 Nov 2006 01:26:37 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Glg8S-0001wU-E1
	for mip4@ietf.org; Sun, 19 Nov 2006 01:26:36 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Glg8P-00035z-QX
	for mip4@ietf.org; Sun, 19 Nov 2006 01:26:36 -0500
Received: from sj-dkim-6.cisco.com ([171.68.10.81])
	by sj-iport-4.cisco.com with ESMTP; 18 Nov 2006 22:26:33 -0800
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-6.cisco.com (8.12.11/8.12.11) with ESMTP id kAJ6QXvA010269; 
	Sat, 18 Nov 2006 22:26:33 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id kAJ6QWdE022810;
	Sat, 18 Nov 2006 22:26:33 -0800 (PST)
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); 
	Sat, 18 Nov 2006 22:26:32 -0800
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter
Date: Sat, 18 Nov 2006 22:26:31 -0800
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5202E5B7B8@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Proxy Mobile IPv4 in the WG charter
Thread-Index: AccKcRALK3JjuYGhShOIr9RtW9WMJAABJbVgAEsFYgA=
From: "Kent Leung \(kleung\)" <kleung@cisco.com>
To: "MORAND Lionel RD-CORE-ISS" <lionel.morand@orange-ftgroup.com>,
	<mip4@ietf.org>
X-OriginalArrivalTime: 19 Nov 2006 06:26:32.0952 (UTC)
	FILETIME=[A8005F80:01C70BA3]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5522; t=1163917593;
	x=1164781593; c=relaxed/simple; s=sjdkim6002;
	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<kleung@cisco.com>
	|Subject:=20RE=3A=20[Mip4]=20Proxy=20Mobile=20IPv4=20in=20the=20WG=20char
	ter |Sender:=20;
	bh=DtWPQMnlDLUMbj/PYW4YB+FhmOubEdSVmswAGLAxTWI=;
	b=W8fEQW01UUJdOJI7Wtbtu0zF9qL/0O5/0xs78V8fMz3y7rK0us+h8c93PnthWOLeHSDpslqk
	MSX7igZU51Tsnnja/tlWmjzOB2FVrdqk0LQFQ6e4DUVKymxABPF7fYBo;
Authentication-Results: sj-dkim-6; header.From=kleung@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim6002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac
Cc: 
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0777494428=="
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0777494428==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C70BA3.A7C1244D"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C70BA3.A7C1244D
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Lionel.  WiMAX has adopted PMIPv4 and 3GPP2 is interested.  In =
addition, PMIPv4 is used in some environments where the hosts don't have =
MIPv4 client software.
=20
Kent

________________________________

From: MORAND Lionel RD-CORE-ISS =
[mailto:lionel.morand@orange-ftgroup.com]=20
Sent: Friday, November 17, 2006 10:27 AM
To: Kent Leung (kleung); mip4@ietf.org
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter


Hi, Kent
=20
Could it possible to know which SDOs have adopted or are interested in =
such a solution?
=20
BR,
=20
Lionel


________________________________

	De : Kent Leung (kleung) [mailto:kleung@cisco.com]=20
	Envoy=E9 : vendredi 17 novembre 2006 18:52
	=C0 : mip4@ietf.org
	Objet : [Mip4] Proxy Mobile IPv4 in the WG charter
=09
=09
	Hi.  The draft-leung-mip4-proxy-mode-01.txt draft describes using =
Mobile IPv4 in proxy mode to provide network-based mobility management.  =
There will need to be some more work on the draft.  But wanted to get =
some sense of support for Proxy Mobile IPv4 in this WG.  Certainly there =
are a few SDOs which have either adopted or interested in such =
mechanism.
	=20
	Do folks want to take this on as a WG item eventually?
	=20
	Kent


------_=_NextPart_001_01C70BA3.A7C1244D
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2976" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D218481206-19112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Lionel.&nbsp; WiMAX has adopted PMIPv4 and =
3GPP2 is=20
interested.&nbsp; In addition, PMIPv4 is used in&nbsp;some environments =
where=20
the hosts don't have MIPv4 client software.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D218481206-19112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D218481206-19112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Kent</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> MORAND Lionel RD-CORE-ISS=20
[mailto:lionel.morand@orange-ftgroup.com] <BR><B>Sent:</B> Friday, =
November 17,=20
2006 10:27 AM<BR><B>To:</B> Kent Leung (kleung);=20
mip4@ietf.org<BR><B>Subject:</B> RE: [Mip4] Proxy Mobile IPv4 in the WG=20
charter<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D074432418-17112006><FONT =
face=3DArial=20
color=3D#008000 size=3D2>Hi, Kent</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D074432418-17112006><FONT =
face=3DArial=20
color=3D#008000 size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D074432418-17112006><FONT =
face=3DArial=20
color=3D#008000 size=3D2>Could it possible to know which SDOs have =
adopted or are=20
interested in such a solution?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D074432418-17112006><FONT =
face=3DArial=20
color=3D#008000 size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D074432418-17112006><FONT =
face=3DArial=20
color=3D#008000 size=3D2>BR,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D074432418-17112006><FONT =
face=3DArial=20
color=3D#008000 size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D074432418-17112006><FONT =
face=3DArial=20
color=3D#008000 size=3D2>Lionel</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #008000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Dfr dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>De&nbsp;:</B> Kent Leung (kleung)=20
  [mailto:kleung@cisco.com] <BR><B>Envoy=E9&nbsp;:</B> vendredi 17 =
novembre 2006=20
  18:52<BR><B>=C0&nbsp;:</B> mip4@ietf.org<BR><B>Objet&nbsp;:</B> [Mip4] =
Proxy=20
  Mobile IPv4 in the WG charter<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT face=3DArial =
size=3D2>Hi.&nbsp; The=20
  <FONT face=3D"Times New Roman">draft-leung-mip4-proxy-mode-01.txt =
draft=20
  describes using Mobile IPv4 in proxy mode to provide network-based =
mobility=20
  management.&nbsp; There will need to be some more work on the =
draft.&nbsp; But=20
  wanted to get some sense of support for Proxy Mobile IPv4 in this =
WG.&nbsp;=20
  Certainly there are a few SDOs which have either adopted or interested =
in such=20
  mechanism.</FONT></FONT></SPAN></DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT face=3DArial =
size=3D2><FONT=20
  face=3D"Times New Roman"></FONT></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT face=3DArial =
size=3D2><FONT=20
  face=3D"Times New Roman">Do folks want to take this on as a WG item=20
  eventually?</FONT></FONT></SPAN></DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT=20
size=3D2>Kent</FONT></SPAN></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C70BA3.A7C1244D--


--===============0777494428==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0777494428==--




From mip4-bounces@ietf.org Sun Nov 19 05:19:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gljlm-0000jd-3f; Sun, 19 Nov 2006 05:19:26 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gljll-0000jY-DH
	for mip4@ietf.org; Sun, 19 Nov 2006 05:19:25 -0500
Received: from mail128.messagelabs.com ([216.82.250.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gljlk-0008Q8-3p
	for mip4@ietf.org; Sun, 19 Nov 2006 05:19:25 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-13.tower-128.messagelabs.com!1163931563!8333618!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [144.189.100.103]
Received: (qmail 7021 invoked from network); 19 Nov 2006 10:19:23 -0000
Received: from motgate3.mot.com (HELO motgate3.mot.com) (144.189.100.103)
	by server-13.tower-128.messagelabs.com with SMTP;
	19 Nov 2006 10:19:23 -0000
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate3.mot.com (8.12.11/Motorola) with ESMTP id kAJAJMZq024083;
	Sun, 19 Nov 2006 03:19:22 -0700 (MST)
Received: from [10.169.4.115] (mvp-10-169-4-115.corp.mot.com [10.169.4.115])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id kAJAJJEh025087;
	Sun, 19 Nov 2006 04:19:21 -0600 (CST)
Message-ID: <45602F9C.7050304@motorola.com>
Date: Sun, 19 Nov 2006 11:19:08 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: "Kent Leung (kleung)" <kleung@cisco.com>
Subject: Re: [Mip4] Proxy Mobile IPv4 in the WG charter
References: <2979E38DD6FC6544B789C8DAD7BAFC5202E5B7B8@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC5202E5B7B8@xmb-sjc-235.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: MORAND Lionel RD-CORE-ISS <lionel.morand@orange-ftgroup.com>, mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Kent Leung (kleung) wrote:
> Hi Lionel.  WiMAX has adopted PMIPv4 and 3GPP2 is interested.

In general, I don't think that adoption of a particular protocol by a
particular SDO makes it enough of a case for adopting it at IETF too.
  If one SDO already adopted a protocol then it's supposedly known how
it works, how it's deployed, what are its needs.

On another hand, I think it can benefit the SDO to have feedback from
this working group about this particular protocol, driven by a
consensus procedure.

Some aspects may be unclear when taking on a particular protocol at
IETF after being developped at SDO.  For example, if consensusing
PMIPv4 here finds out that PMIPv4 needs some enhancements (for
example: co-locate the AAA server with the HA) - will that particular
SDO accept this new IETF version of the PMIPv4 protocol.

> In addition, PMIPv4 is used in some environments where the hosts 
> don't have MIPv4 client software.

That is more plausible.  Can we picture an idea what do those
environments (non-WiMax, non-3Gx) look like.

Alex

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Sun Nov 19 18:51:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GlwR6-0001QH-Pw; Sun, 19 Nov 2006 18:50:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GlMxM-0001Ei-20
	for mip4@ietf.org; Sat, 18 Nov 2006 04:57:52 -0500
Received: from ns1.siteground5.com ([67.15.157.13] helo=serv01.siteground5.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GlMxG-0000X6-3x
	for mip4@ietf.org; Sat, 18 Nov 2006 04:57:52 -0500
Received: from boostwor by serv01.siteground5.com with local (Exim 4.52)
	id 1GlMxF-0006aZ-24
	for mip4@ietf.org; Sat, 18 Nov 2006 03:57:45 -0600
To: mip4@ietf.org
Date: Sat, 18 Nov 2006 03:57:45 -0600
From: contact@ntms2007.org
Message-ID: <a2e2ce56c49f9c011435f4f250577677@www.boostwork.com>
X-Priority: 3
X-Mailer: PHPMailer [version 1.73]
X-Mailer: PHPlist v2.10.2
X-MessageID: 37
X-ListMember: mip4@ietf.org
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="iso-8859-1"
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - serv01.siteground5.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [32094 501] / [47 12]
X-AntiAbuse: Sender Address Domain - serv01.siteground5.com
X-Source: /usr/bin/php
X-Source-Args: /usr/bin/php index.php 
X-Source-Dir: boostwork.com:/public_html/phpemaillist/admin
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
X-Mailman-Approved-At: Sun, 19 Nov 2006 18:50:55 -0500
Subject: [Mip4] [NTMS 2007] DEADLINE DECEMBER 20, 2006
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

We apologize for multiple receipts.

--------------------- CALL FOR PAPERS - NTMS 2007
1th International Conference on New Technologies, Mobility and
Security (NTMS 2007)
 Technically co-sponsored by IFIP and IEEE France Computer Section
 April 30 to May 3, 2007 - Beirut, Lebanon
 http://www.ntms2007.org

IMPORTANT DATES
------------------------------
Draft papers should be submitted by December 20, 2006 
Authors will receive the acceptance notification by February 20, 2007

Final papers for presentation should be sent before March 15, 2007 

ABOUT NTMS'2007
------------------------------
NTMS'2007 aims at fostering advances in the areas of New
Technologies, Wireless Networks, Mobile Computing, Ad hoc and Ambient
Networks, QoS, Network Security and E-commerce, to mention a few, and
provides a dynamic forum for researchers, students and professionals
to present their state-of-the-art research and development in these
interesting areas. 
The event will be combined with tutorial sessions and workshops.
Tutorials will precede the main program, aiming at the dissemination
of mature knowledge and technology advances in the field. Two or more
Workshops will immediately follow the main conference, offering the
opportunity for a more focused exchange of ideas and presentation of
on-going research relevant to selected topics. During NTMS'2007, demo
areas will also be available to R&D labs and consortia to demonstrate
their prototype implementations, or other prominent results.

TOPICS OF INTEREST
-------------------------------
The organising and technical committees of the conference are seeking
original contributions in the areas of, but not limited to:

 Analysis and design of network architectures and algorithms 
Network management and traffic engineering 
Network, transport, and application-layer protocols 
Resource management, quality of service, signalling & scheduling 
Routing, switching, and addressing 
Network fault-tolerance & reliability, debugging & troubleshooting 
Network security, vulnerability, authentication and access control 
Intrusion Detection, Prediction, and Countermeasures 
Smart Device, Identity, Privacy and Trust 
Privacy, contract agreements, and payment systems 
Public key infrastructure implementation 
Mobile code security & Security management 
E-business and E-commerce security 
Peer-to-peer, overlay, and content distribution networks 
Optical networks and switching 
Wireless Mesh Networks & Metropolitan Area Networks (WiMAX, 802.16e) 
3G & Wireless Personal Area Networks (Wimedia, UWB, Bluetooth, ...) 
Wireless Local Area Networks (Wi-Fi, ...) & Wireless Local Loop 
Ad hoc, Sensor Networks and Embedded Systems, Ambient Networks 
Mobility management and Handover 
Medium Access Control & Scheduling Techniques for Wireless Systems 
Cross-layer network design and optimization 
Pervasive, Ubiquitous and Mobile Computing 
Agents and Middleware, Agent Computing and Agent Applications 
Grid and cluster computing & Context aware computing 
Adaptation software development 
Next generation systems & Service-oriented techniques 
Component based software engineering &Software verification &
analysis 
Web Commerce & Services, Data models, Web searching & querying 
XML, Query Processing & Optimization, Storage Structures & Indexing 
Web Mining & Web Semantic 

SUBMISSION GUIDELINES
--------------------------------------
Authors are invited to submit complete and original papers. All
submitted papers will be refereed for quality, correctness,
originality and relevance. Authors of accepted papers will be
required to produce final
versions of their papers in IEEE camera ready format (double column)
according to IEEE Computer Society Press style guidelines Preferred
maximum paper length is 5 printed pages (10-point font) including
figures, graphics and tables. However, papers for review of up to 8
pages in length will also be accepted, although accepted papers
exceeding 5 pages will be charged an overlength fee of $100 for the
6th page.
NTMS'2007 is using the EDAS Conference Management System
(http://edas.info) to manage paper submissions process. 

The proposal for tutorial should include the title and clear
explanation of the content of the proposed tutorial. Please include
in the proposal (1) Organizer Name, (2) Name of proposed instructor,
(3) Title of tutorial and detailed outline, (4) Qualifications of
proposed instructor, (5) Full contact information: mailing address,
telephone & fax number, and email address.

FOR MORE INFORMATION PLEASE VISIT THE NTMS'2007 WEB SITE:
http://www.ntms2007.org






--
Powered by PHPlist, www.phplist.com --



-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Mon Nov 20 10:13:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GmApe-0003S3-ON; Mon, 20 Nov 2006 10:13:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GmApd-0003Rq-5W
	for mip4@ietf.org; Mon, 20 Nov 2006 10:13:13 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GmApb-0006PS-KV
	for mip4@ietf.org; Mon, 20 Nov 2006 10:13:13 -0500
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kAKFD9VN020507
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 20 Nov 2006 07:13:10 -0800
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	kAKFD6Rx023281; Mon, 20 Nov 2006 07:13:08 -0800 (PST)
Received: from sanexcas01.na.qualcomm.com ([172.30.36.175]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Nov 2006 07:13:05 -0800
Received: from NAEX16.na.qualcomm.com ([10.47.6.158]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Nov 2006 07:13:05 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter
Date: Mon, 20 Nov 2006 07:13:03 -0800
Message-ID: <2309978910A6A6478C2C7585692B0AF40A5825@NAEX16.na.qualcomm.com>
In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC5202DFC6A7@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Proxy Mobile IPv4 in the WG charter
Thread-Index: AccKcRALK3JjuYGhShOIr9RtW9WMJACQ5Elw
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: "Kent Leung \(kleung\)" <kleung@cisco.com>, <mip4@ietf.org>
X-OriginalArrivalTime: 20 Nov 2006 15:13:05.0948 (UTC)
	FILETIME=[614EBDC0:01C70CB6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bfe538a859d88717fa3c8a6377d62f90
Cc: 
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1602421131=="
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1602421131==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C70CB6.60FCD265"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C70CB6.60FCD265
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Kent,

=20

I think it makes sense for the PMIPv4 protocol to be standardized by
this group. I also think we should separate the way the protocol is used
in the field from what the generic protocol is that might be applicable
in various different systems. I think your draft is mixing the two
issues together.=20

=20

IMO we should have a very simple and hopefully sort specification
defining the changes (if any) to MIPv4 required so that the protocol can
run in proxy mode. In addition, if it is deemed necessary/useful, we can
have informational document(s) showing how PMIPv4 is used in various
systems.=20

=20

I have some specific comments on the protocol itself but we can talk
about that if/when this becomes a WG document.

=20

Thanks

George=20

=20

________________________________

From: Kent Leung (kleung) [mailto:kleung@cisco.com]=20
Sent: Friday, November 17, 2006 12:52 PM
To: mip4@ietf.org
Subject: [Mip4] Proxy Mobile IPv4 in the WG charter

=20

Hi.  The draft-leung-mip4-proxy-mode-01.txt draft describes using Mobile
IPv4 in proxy mode to provide network-based mobility management.  There
will need to be some more work on the draft.  But wanted to get some
sense of support for Proxy Mobile IPv4 in this WG.  Certainly there are
a few SDOs which have either adopted or interested in such mechanism.

=20

Do folks want to take this on as a WG item eventually?

=20

Kent


------_=_NextPart_001_01C70CB6.60FCD265
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Hi Kent,</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I think it makes sense for the =
PMIPv4
protocol to be standardized by this group. I also think we should =
separate the
way the protocol is used in the field from what the generic protocol is =
that
might be applicable in various different systems. I think your draft is =
mixing
the two issues together. </span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>IMO we should have a very simple =
and hopefully
sort specification defining the changes (if any) to MIPv4 required so =
that the
protocol can run in proxy mode. In addition, if it is deemed =
necessary/useful, we
can have informational document(s) showing how PMIPv4 is used in various
systems. </span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I have some specific comments on =
the
protocol itself but we can talk about that if/when this becomes a WG =
document.</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>George </span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Kent =
Leung
(kleung) [mailto:kleung@cisco.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, November =
17, 2006
12:52 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> mip4@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [Mip4] Proxy =
Mobile IPv4
in the WG charter</span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi.&nbsp; The </span></font><font size=3D2><span
style=3D'font-size:10.0pt'>draft-leung-mip4-proxy-mode-01.txt draft =
describes
using Mobile IPv4 in proxy mode to provide network-based mobility
management.&nbsp; There will need to be some more work on the =
draft.&nbsp; But
wanted to get some sense of support for Proxy Mobile IPv4 in this =
WG.&nbsp;
Certainly there are a few SDOs which have either adopted or interested =
in such
mechanism.</span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'>Do folks want to take this on as a WG item =
eventually?</span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'>Kent</span></font></p>

</div>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C70CB6.60FCD265--


--===============1602421131==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1602421131==--




From mip4-bounces@ietf.org Mon Nov 20 10:31:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GmB7C-0005It-Ht; Mon, 20 Nov 2006 10:31:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GmB7B-0005Ih-O2
	for mip4@ietf.org; Mon, 20 Nov 2006 10:31:21 -0500
Received: from web60320.mail.yahoo.com ([209.73.178.128])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GmB79-00080s-9C
	for mip4@ietf.org; Mon, 20 Nov 2006 10:31:21 -0500
Received: (qmail 34095 invoked by uid 60001); 20 Nov 2006 15:31:19 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type;
	b=WzAWnx7lLTMJwTPExDH1n3zBwGcxx66lb7U/bYRKViyvKB2OC0TYwcaW/oj1gwNArLmvk9XA8fYQg8rTUq6Yt7MbQNyLjh52shKmZ4n9OeXw50VuOw7T9rzuCIbcR1oBasiO6utQel4rAXQuFL9xChVkrjtNmGJrfmsQr6B2d3g=
	; 
Message-ID: <20061120153119.34093.qmail@web60320.mail.yahoo.com>
Received: from [12.129.211.52] by web60320.mail.yahoo.com via HTTP;
	Mon, 20 Nov 2006 07:31:19 PST
Date: Mon, 20 Nov 2006 07:31:18 -0800 (PST)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: [Mip4] Proxy Mobile IPv4 in the WG charter
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0929206276=="
Errors-To: mip4-bounces@ietf.org

--===============0929206276==
Content-Type: multipart/alternative; boundary="0-1229320193-1164036678=:34076"

--0-1229320193-1164036678=:34076
Content-Type: text/plain; charset=ascii
Content-Transfer-Encoding: quoted-printable

Is there a netlmm4 WG? IMHO pmip4 could be standardized there if any? WGs c=
an shut down if no new work left, and that is usually good practice, there =
is nothing wrong in doing such a thing.=0A  No offense to any one.=0A=0AReg=
ards,=0A=0A--behcet=0A=0A=0A=0A----- Original Message ----=0AFrom: "Tsirtsi=
s, George" <tsirtsis@qualcomm.com>=0ATo: Kent Leung (kleung) <kleung@cisco.=
com>; mip4@ietf.org=0ASent: Monday, November 20, 2006 9:13:03 AM=0ASubject:=
 RE: [Mip4] Proxy Mobile IPv4 in the WG charter=0A=0A=0AHi Kent,=0A =0AI th=
ink it makes sense for the PMIPv4 protocol to be standardized by this group=
. I also think we should separate the way the protocol is used in the field=
 from what the generic protocol is that might be applicable in various diff=
erent systems. I think your draft is mixing the two issues together. =0A =
=0AIMO we should have a very simple and hopefully sort specification defini=
ng the changes (if any) to MIPv4 required so that the protocol can run in p=
roxy mode. In addition, if it is deemed necessary/useful, we can have infor=
mational document(s) showing how PMIPv4 is used in various systems. =0A =0A=
I have some specific comments on the protocol itself but we can talk about =
that if/when this becomes a WG document.=0A =0AThanks=0AGeorge =0A =0A=0A=
=0A=0AFrom: Kent Leung (kleung) [mailto:kleung@cisco.com] =0ASent: Friday, =
November 17, 2006 12:52 PM=0ATo: mip4@ietf.org=0ASubject: [Mip4] Proxy Mobi=
le IPv4 in the WG charter=0A =0AHi.  The draft-leung-mip4-proxy-mode-01.txt=
 draft describes using Mobile IPv4 in proxy mode to provide network-based m=
obility management.  There will need to be some more work on the draft.  Bu=
t wanted to get some sense of support for Proxy Mobile IPv4 in this WG.  Ce=
rtainly there are a few SDOs which have either adopted or interested in suc=
h mechanism.=0A =0ADo folks want to take this on as a WG item eventually?=
=0A =0AKent=0A-- =0AMip4 mailing list: Mip4@ietf.org=0A    Web interface: h=
ttps://www1.ietf.org/mailman/listinfo/mip4=0A     Charter page: http://www.=
ietf.org/html.charters/mip4-charter.html=0ASupplemental site: http://www.mi=
p4.org/
--0-1229320193-1164036678=:34076
Content-Type: text/html; charset=ascii
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:times new roman, new york, times, serif;=
font-size:12pt"><DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman=
, new york, times, serif"><FONT color=3D#0060bf>Is there a netlmm4 WG? IMHO=
 pmip4 could be standardized there if any? WGs can shut down if no new work=
 left, and that is usually good practice, there is nothing wrong in doing s=
uch a thing.</FONT></DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: tim=
es new roman, new york, times, serif"><FONT color=3D#0060bf>&nbsp; No offen=
se to any one.</FONT></DIV>=0A<P><FONT color=3D#0060bf></FONT>&nbsp;</P>=0A=
<P><FONT color=3D#0060bf>Regards,</FONT></P>=0A<P><FONT color=3D#0060bf></F=
ONT>&nbsp;</P>=0A<P><FONT color=3D#0060bf>--behcet</P>=0A<DIV style=3D"FONT=
-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif"><BR></FO=
NT><BR></DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman=
, new york, times, serif">----- Original Message ----<BR>From: "Tsirtsis, G=
eorge" &lt;tsirtsis@qualcomm.com&gt;<BR>To: Kent Leung (kleung) &lt;kleung@=
cisco.com&gt;; mip4@ietf.org<BR>Sent: Monday, November 20, 2006 9:13:03 AM<=
BR>Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter<BR><BR>=0A<STYLE=
>=0A<!--=0A _filtered {font-family:SimSun;=0Apanose-1:2 1 6 0 3 1 1 1 1 1;}=
=0A _filtered {font-family:Tahoma;=0Apanose-1:2 11 6 4 3 5 4 4 2 4;}=0A _fi=
ltered {=0Apanose-1:0 0 0 0 0 0 0 0 0 0;}=0A/* Style Definitions */=0A p.Ms=
oNormal, li.MsoNormal, div.MsoNormal=0A=09{margin:0in;=0Amargin-bottom:.000=
1pt;=0Afont-size:12.0pt;=0Afont-family:"Times New Roman";}=0Aa:link, span.M=
soHyperlink=0A=09{color:blue;=0Atext-decoration:underline;}=0Aa:visited, sp=
an.MsoHyperlinkFollowed=0A=09{color:purple;=0Atext-decoration:underline;}=
=0Aspan.EmailStyle17=0A=09{font-family:Arial;=0Acolor:navy;}=0A _filtered {=
=0Amargin:1.0in 1.25in 1.0in 1.25in;}=0Adiv.Section1=0A=09{}=0A-->=0A</STYL=
E>=0A=0A<DIV class=3DSection1>=0A<P class=3DMsoNormal><FONT face=3DArial co=
lor=3Dnavy size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMIL=
Y: Arial">Hi Kent,</SPAN></FONT></P>=0A<P class=3DMsoNormal><FONT face=3DAr=
ial color=3Dnavy size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT=
-FAMILY: Arial">&nbsp;</SPAN></FONT></P>=0A<P class=3DMsoNormal><FONT face=
=3DArial color=3Dnavy size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: navy;=
 FONT-FAMILY: Arial">I think it makes sense for the PMIPv4 protocol to be s=
tandardized by this group. I also think we should separate the way the prot=
ocol is used in the field from what the generic protocol is that might be a=
pplicable in various different systems. I think your draft is mixing the tw=
o issues together. </SPAN></FONT></P>=0A<P class=3DMsoNormal><FONT face=3DA=
rial color=3Dnavy size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: navy; FON=
T-FAMILY: Arial">&nbsp;</SPAN></FONT></P>=0A<P class=3DMsoNormal><FONT face=
=3DArial color=3Dnavy size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: navy;=
 FONT-FAMILY: Arial">IMO we should have a very simple and hopefully sort sp=
ecification defining the changes (if any) to MIPv4 required so that the pro=
tocol can run in proxy mode. In addition, if it is deemed necessary/useful,=
 we can have informational document(s) showing how PMIPv4 is used in variou=
s systems. </SPAN></FONT></P>=0A<P class=3DMsoNormal><FONT face=3DArial col=
or=3Dnavy size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY=
: Arial">&nbsp;</SPAN></FONT></P>=0A<P class=3DMsoNormal><FONT face=3DArial=
 color=3Dnavy size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FA=
MILY: Arial">I have some specific comments on the protocol itself but we ca=
n talk about that if/when this becomes a WG document.</SPAN></FONT></P>=0A<=
P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN style=3D=
"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">&nbsp;</SPAN></FONT></P>=
=0A<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN styl=
e=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Thanks</SPAN></FONT>=
</P>=0A<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN =
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">George </SPAN></=
FONT></P>=0A<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><=
SPAN style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">&nbsp;</SPA=
N></FONT></P>=0A<DIV style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in=
; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-L=
EFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">=0A<DI=
V>=0A<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FO=
NT face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">=0A<HR=
 tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>=0A</SPAN></FONT></DI=
V>=0A<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN style=3D"FO=
NT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT><=
/B><FONT face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY=
: Tahoma"> Kent Leung (kleung) [mailto:kleung@cisco.com] <BR><B><SPAN style=
=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Friday, November 17, 2006 12:52 PM<=
BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> mip4@ietf.org<BR><B>=
<SPAN style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> [Mip4] Proxy Mobile I=
Pv4 in the WG charter</SPAN></FONT></P></DIV>=0A<P class=3DMsoNormal><FONT =
face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">&nbsp;</S=
PAN></FONT></P>=0A<DIV>=0A<P class=3DMsoNormal><FONT face=3DArial size=3D2>=
<SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi.&nbsp; The </SPAN></=
FONT><FONT size=3D2><SPAN style=3D"FONT-SIZE: 10pt">draft-leung-mip4-proxy-=
mode-01.txt draft describes using Mobile IPv4 in proxy mode to provide netw=
ork-based mobility management.&nbsp; There will need to be some more work o=
n the draft.&nbsp; But wanted to get some sense of support for Proxy Mobile=
 IPv4 in this WG.&nbsp; Certainly there are a few SDOs which have either ad=
opted or interested in such mechanism.</SPAN></FONT></P></DIV>=0A<DIV>=0A<P=
 class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN style=3D"F=
ONT-SIZE: 12pt">&nbsp;</SPAN></FONT></P></DIV>=0A<DIV>=0A<P class=3DMsoNorm=
al><FONT face=3D"Times New Roman" size=3D2><SPAN style=3D"FONT-SIZE: 10pt">=
Do folks want to take this on as a WG item eventually?</SPAN></FONT></P></D=
IV>=0A<DIV>=0A<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3>=
<SPAN style=3D"FONT-SIZE: 12pt">&nbsp;</SPAN></FONT></P></DIV>=0A<DIV>=0A<P=
 class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D2><SPAN style=3D"F=
ONT-SIZE: 10pt">Kent</SPAN></FONT></P></DIV></DIV></DIV>=0A<DIV>-- <BR>Mip4=
 mailing list: Mip4@ietf.org<BR>&nbsp;&nbsp;&nbsp;&nbsp;Web interface: <A h=
ref=3D"https://www1.ietf.org/mailman/listinfo/mip4" target=3D_blank>https:/=
/www1.ietf.org/mailman/listinfo/mip4</A><BR>&nbsp;&nbsp;&nbsp;&nbsp; Charte=
r page: <A href=3D"http://www.ietf.org/html.charters/mip4-charter.html" tar=
get=3D_blank>http://www.ietf.org/html.charters/mip4-charter.html</A><BR>Sup=
plemental site: <A href=3D"http://www.mip4.org/" target=3D_blank>http://www=
.mip4.org/</A></DIV></DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: ti=
mes new roman, new york, times, serif"><BR></DIV></div></body></html>
--0-1229320193-1164036678=:34076--


--===============0929206276==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0929206276==--




From mip4-bounces@ietf.org Mon Nov 20 10:48:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GmBNZ-0003wS-1r; Mon, 20 Nov 2006 10:48:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GmBNX-0003uf-GF
	for mip4@ietf.org; Mon, 20 Nov 2006 10:48:15 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GmBNU-0001cj-Np
	for mip4@ietf.org; Mon, 20 Nov 2006 10:48:15 -0500
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kAKFmA2J023001
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 20 Nov 2006 07:48:10 -0800
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	kAKFm9t5008517; Mon, 20 Nov 2006 07:48:09 -0800
Received: from SANEXCAS02.na.qualcomm.com ([172.30.36.176]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Nov 2006 07:48:08 -0800
Received: from NAEX16.na.qualcomm.com ([10.47.6.158]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Nov 2006 07:48:08 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter
Date: Mon, 20 Nov 2006 07:48:07 -0800
Message-ID: <2309978910A6A6478C2C7585692B0AF40A5830@NAEX16.na.qualcomm.com>
In-Reply-To: <20061120153119.34093.qmail@web60320.mail.yahoo.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Proxy Mobile IPv4 in the WG charter
Thread-Index: AccMueLDDqeqUqvfQLqul7tm2ICEpAAAQ07Q
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: "Behcet Sarikaya" <sarikaya@ieee.org>
X-OriginalArrivalTime: 20 Nov 2006 15:48:08.0542 (UTC)
	FILETIME=[468D1FE0:01C70CBB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 089da5e32269fece1072c9ff54523f20
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0567865544=="
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0567865544==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C70CBB.465AD29D"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C70CBB.465AD29D
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

In the last IETF meeting there was agreement (to be confirmed on the
list) for a number of new items to be added to the MIP4 charter and a
few more things were left out because the WG has too many things to do.
I do not think MIP4 is going anywhere for a while longer....=20

=20

________________________________

From: Behcet Sarikaya [mailto:behcetsarikaya@yahoo.com]=20
Sent: Monday, November 20, 2006 10:31 AM
To: Tsirtsis, George
Cc: mip4@ietf.org
Subject: Re: [Mip4] Proxy Mobile IPv4 in the WG charter

=20

Is there a netlmm4 WG? IMHO pmip4 could be standardized there if any?
WGs can shut down if no new work left, and that is usually good
practice, there is nothing wrong in doing such a thing.

  No offense to any one.

=20

Regards,

=20

--behcet

=20

----- Original Message ----
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: Kent Leung (kleung) <kleung@cisco.com>; mip4@ietf.org
Sent: Monday, November 20, 2006 9:13:03 AM
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter

Hi Kent,

=20

I think it makes sense for the PMIPv4 protocol to be standardized by
this group. I also think we should separate the way the protocol is used
in the field from what the generic protocol is that might be applicable
in various different systems. I think your draft is mixing the two
issues together.=20

=20

IMO we should have a very simple and hopefully sort specification
defining the changes (if any) to MIPv4 required so that the protocol can
run in proxy mode. In addition, if it is deemed necessary/useful, we can
have informational document(s) showing how PMIPv4 is used in various
systems.=20

=20

I have some specific comments on the protocol itself but we can talk
about that if/when this becomes a WG document.

=20

Thanks

George=20

=20

________________________________

From: Kent Leung (kleung) [mailto:kleung@cisco.com]=20
Sent: Friday, November 17, 2006 12:52 PM
To: mip4@ietf.org
Subject: [Mip4] Proxy Mobile IPv4 in the WG charter

=20

Hi.  The draft-leung-mip4-proxy-mode-01.txt draft describes using Mobile
IPv4 in proxy mode to provide network-based mobility management.  There
will need to be some more work on the draft.  But wanted to get some
sense of support for Proxy Mobile IPv4 in this WG.  Certainly there are
a few SDOs which have either adopted or interested in such mechanism.

=20

Do folks want to take this on as a WG item eventually?

=20

Kent

--=20
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

=20


------_=_NextPart_001_01C70CBB.465AD29D
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered)">
<style>
<!--
_filtered {font-family:SimSun;=0A=
panose-1:2 1 6 0 3 1 1 1 1 1;}
_filtered {font-family:Tahoma;=0A=
panose-1:2 11 6 4 3 5 4 4 2 4;}
_filtered {=0A=
panose-1:0 0 0 0 0 0 0 0 0 0;}
_filtered {=0A=
margin:1.0in 1.25in 1.0in 1.25in;}

 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{margin-right:0in;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.emailstyle17
	{font-family:Arial;
	color:navy;}
span.EmailStyle19
	{font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>In the last IETF meeting there was
agreement (to be confirmed on the list) for a number of new items to be =
added
to the MIP4 charter and a few more things were left out because the WG =
has too
many things to do. I do not think MIP4 is going anywhere for a while =
longer&#8230;.
</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Behcet Sarikaya
[mailto:behcetsarikaya@yahoo.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, November =
20, 2006
10:31 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Tsirtsis, George<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> mip4@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [Mip4] Proxy =
Mobile
IPv4 in the WG charter</span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

<div>

<div>

<p class=3DMsoNormal><font size=3D3 color=3D"#0060bf" face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:#0060BF'>Is there a netlmm4 WG? IMHO =
pmip4 could
be standardized there if any? WGs can shut down if no new work left, and =
that
is usually good practice, there is nothing wrong in doing such a =
thing.</span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 color=3D"#0060bf" face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:#0060BF'>&nbsp; No offense to any =
one.</span></font></p>

</div>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p><font size=3D3 color=3D"#0060bf" face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt;color:#0060BF'>Regards,</span></font></p>

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

<p><font size=3D3 color=3D"#0060bf" face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt;color:#0060BF'>--behcet</span></font></p>

<div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>----- Original =
Message
----<br>
From: &quot;Tsirtsis, George&quot; &lt;tsirtsis@qualcomm.com&gt;<br>
To: Kent Leung (kleung) &lt;kleung@cisco.com&gt;; mip4@ietf.org<br>
Sent: Monday, November 20, 2006 9:13:03 AM<br>
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG =
charter</span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Hi Kent,</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I think it makes sense for the =
PMIPv4
protocol to be standardized by this group. I also think we should =
separate the
way the protocol is used in the field from what the generic protocol is =
that
might be applicable in various different systems. I think your draft is =
mixing
the two issues together. </span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>IMO we should have a very simple =
and
hopefully sort specification defining the changes (if any) to MIPv4 =
required so
that the protocol can run in proxy mode. In addition, if it is deemed
necessary/useful, we can have informational document(s) showing how =
PMIPv4 is
used in various systems. </span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I have some specific comments on =
the
protocol itself but we can talk about that if/when this becomes a WG =
document.</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>George </span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Kent =
Leung
(kleung) [mailto:kleung@cisco.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, November =
17, 2006
12:52 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> mip4@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [Mip4] Proxy =
Mobile IPv4
in the WG charter</span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi.&nbsp; The </span></font><font size=3D2><span
style=3D'font-size:10.0pt'>draft-leung-mip4-proxy-mode-01.txt draft =
describes
using Mobile IPv4 in proxy mode to provide network-based mobility
management.&nbsp; There will need to be some more work on the =
draft.&nbsp; But
wanted to get some sense of support for Proxy Mobile IPv4 in this =
WG.&nbsp;
Certainly there are a few SDOs which have either adopted or interested =
in such
mechanism.</span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'>Do folks want to take this on as a WG item =
eventually?</span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'>Kent</span></font></p>

</div>

</div>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>-- <br>
Mip4 mailing list: Mip4@ietf.org<br>
&nbsp;&nbsp;&nbsp;&nbsp;Web interface: <a
href=3D"https://www1.ietf.org/mailman/listinfo/mip4" =
target=3D"_blank">https://www1.ietf.org/mailman/listinfo/mip4</a><br>
&nbsp;&nbsp;&nbsp;&nbsp; Charter page: <a
href=3D"http://www.ietf.org/html.charters/mip4-charter.html" =
target=3D"_blank">http://www.ietf.org/html.charters/mip4-charter.html</a>=
<br>
Supplemental site: <a href=3D"http://www.mip4.org/" =
target=3D"_blank">http://www.mip4.org/</a></span></font></p>

</div>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

</div>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C70CBB.465AD29D--


--===============0567865544==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0567865544==--




From mip4-bounces@ietf.org Mon Nov 20 16:45:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GmGws-0002Va-KM; Mon, 20 Nov 2006 16:45:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GmGwr-0002VJ-Pm
	for mip4@ietf.org; Mon, 20 Nov 2006 16:45:05 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GmGwp-0007pu-9b
	for mip4@ietf.org; Mon, 20 Nov 2006 16:45:05 -0500
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kAKLj09k031014
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 20 Nov 2006 13:45:01 -0800
Received: from NAEXBR03.na.qualcomm.com (naexbr03.na.qualcomm.com
	[129.46.134.172])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id kAKLd8bc022702; 
	Mon, 20 Nov 2006 13:44:59 -0800 (PST)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Nov 2006 13:43:57 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter
Date: Mon, 20 Nov 2006 13:43:52 -0800
Message-ID: <C24CB51D5AA800449982D9BCB90325132D4EC1@NAEX13.na.qualcomm.com>
In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC5202DFC6A7@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Proxy Mobile IPv4 in the WG charter
Thread-Index: AccKcRALK3JjuYGhShOIr9RtW9WMJACeekRg
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Kent Leung \(kleung\)" <kleung@cisco.com>, <mip4@ietf.org>
X-OriginalArrivalTime: 20 Nov 2006 21:43:57.0503 (UTC)
	FILETIME=[FB860CF0:01C70CEC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Cc: 
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1747271133=="
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1747271133==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C70CEC.FB5BFD30"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C70CEC.FB5BFD30
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Kent,
If NETLMM supported IPv4 endpoints, do we still need a standardized
PMIPv4 solution? Or, is this an effort to document what has been already
deployed?=20
=20
Regards,
Vidya


________________________________

	From: Kent Leung (kleung) [mailto:kleung@cisco.com]=20
	Sent: Friday, November 17, 2006 9:52 AM
	To: mip4@ietf.org
	Subject: [Mip4] Proxy Mobile IPv4 in the WG charter
=09
=09
	Hi.  The draft-leung-mip4-proxy-mode-01.txt draft describes
using Mobile IPv4 in proxy mode to provide network-based mobility
management.  There will need to be some more work on the draft.  But
wanted to get some sense of support for Proxy Mobile IPv4 in this WG.
Certainly there are a few SDOs which have either adopted or interested
in such mechanism.
	=20
	Do folks want to take this on as a WG item eventually?
	=20
	Kent


------_=_NextPart_001_01C70CEC.FB5BFD30
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2963" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D498342921-20112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Kent,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D498342921-20112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>If NETLMM supported IPv4 endpoints, do we still =
need a=20
standardized PMIPv4 solution? Or, is this an effort to document what has =
been=20
already deployed? </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D498342921-20112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D498342921-20112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D498342921-20112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Vidya</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Kent Leung (kleung)=20
  [mailto:kleung@cisco.com] <BR><B>Sent:</B> Friday, November 17, 2006 =
9:52=20
  AM<BR><B>To:</B> mip4@ietf.org<BR><B>Subject:</B> [Mip4] Proxy Mobile =
IPv4 in=20
  the WG charter<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT face=3DArial =
size=3D2>Hi.&nbsp; The=20
  <FONT face=3D"Times New Roman">draft-leung-mip4-proxy-mode-01.txt =
draft=20
  describes using Mobile IPv4 in proxy mode to provide network-based =
mobility=20
  management.&nbsp; There will need to be some more work on the =
draft.&nbsp; But=20
  wanted to get some sense of support for Proxy Mobile IPv4 in this =
WG.&nbsp;=20
  Certainly there are a few SDOs which have either adopted or interested =
in such=20
  mechanism.</FONT></FONT></SPAN></DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT face=3DArial =
size=3D2><FONT=20
  face=3D"Times New Roman"></FONT></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT face=3DArial =
size=3D2><FONT=20
  face=3D"Times New Roman">Do folks want to take this on as a WG item=20
  eventually?</FONT></FONT></SPAN></DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT=20
size=3D2>Kent</FONT></SPAN></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C70CEC.FB5BFD30--


--===============1747271133==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1747271133==--




From mip4-bounces@ietf.org Tue Nov 21 04:47:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GmSDg-0007Nl-S8; Tue, 21 Nov 2006 04:47:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GmSDg-0007Ng-IJ
	for mip4@ietf.org; Tue, 21 Nov 2006 04:47:12 -0500
Received: from mxs1.siemens.at ([194.138.12.131] helo=atvies1zqx.siemens.at)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GmSDU-0001um-NG
	for mip4@ietf.org; Tue, 21 Nov 2006 04:47:12 -0500
Received: from vies1kbx.sie.siemens.at ([158.226.129.82])
	by atvies1zqx.siemens.at  with ESMTP id kAL9jY3u011935;
	Tue, 21 Nov 2006 10:45:34 +0100
Received: from nets138a.ww300.siemens.net ([158.226.129.98])
	by vies1kbx.sie.siemens.at (8.12.11.20060308/8.12.1) with ESMTP id
	kAL9komH006498; Tue, 21 Nov 2006 10:46:55 +0100
Received: from zagh223a.ww300.siemens.net ([141.29.124.9]) by
	nets138a.ww300.siemens.net with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Nov 2006 10:46:55 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter
Date: Tue, 21 Nov 2006 10:46:09 +0100
Message-ID: <3C31CDD06342EA4A8137716247B1CD680139C926@zagh223a.ww300.siemens.net>
In-Reply-To: <E1GlAaG-0005GP-PQ@megatron.ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Proxy Mobile IPv4 in the WG charter
Thread-Index: AccKiW1V7v6MeeR3R7GU/Xy6VjpA7gCvKn7A
From: "Damic, Damjan" <damjan.damic@siemens.com>
To: <kleung@cisco.com>, <mip4@ietf.org>
X-OriginalArrivalTime: 21 Nov 2006 09:46:55.0123 (UTC)
	FILETIME=[FA999630:01C70D51]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: 
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hello,

I believe the Proxy MIP4 is worth the effort, and that MIP4 WG is the
appropriate place to address it.
Even though the idea originated by a different SDO, people (including
myself) believe having something standardized through IETF gives the
matter additional meaning and credibility.
A group work in IETF on such an item could therefore serve to provide a
critical feedback to the existing proposal, and possibly to align the
specification in the way the WG perceives it should be (as already
pointed by Alex and George).

Kind regards,
Damjan

=20
>Date: Fri, 17 Nov 2006 09:51:52 -0800
>From: "Kent Leung \(kleung\)" <kleung@cisco.com>
>Subject: [Mip4] Proxy Mobile IPv4 in the WG charter
>To: <mip4@ietf.org>
>=09
>
>Hi.  The draft-leung-mip4-proxy-mode-01.txt draft describes=20
>using Mobile
>IPv4 in proxy mode to provide network-based mobility management.  There
>will need to be some more work on the draft.  But wanted to get some
>sense of support for Proxy Mobile IPv4 in this WG.  Certainly there are
>a few SDOs which have either adopted or interested in such mechanism.
>=20
>Do folks want to take this on as a WG item eventually?
>=20
>Kent

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Nov 21 12:52:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GmZn9-0002Mq-Ux; Tue, 21 Nov 2006 12:52:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GmZn8-0002Mf-L7
	for mip4@ietf.org; Tue, 21 Nov 2006 12:52:18 -0500
Received: from mail128.messagelabs.com ([216.82.250.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GmZn6-0004BZ-Nm
	for mip4@ietf.org; Tue, 21 Nov 2006 12:52:18 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-5.tower-128.messagelabs.com!1164131480!8570422!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [144.189.100.101]
Received: (qmail 8950 invoked from network); 21 Nov 2006 17:51:20 -0000
Received: from motgate2.mot.com (HELO motgate2.mot.com) (144.189.100.101)
	by server-5.tower-128.messagelabs.com with SMTP;
	21 Nov 2006 17:51:20 -0000
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate2.mot.com (8.12.11/Motorola) with ESMTP id kALHpJ8W018975;
	Tue, 21 Nov 2006 10:51:19 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id kALHpHbp008597;
	Tue, 21 Nov 2006 11:51:18 -0600 (CST)
Message-ID: <45633C94.1030703@motorola.com>
Date: Tue, 21 Nov 2006 18:51:16 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: Re: [Mip4] Proxy Mobile IPv4 in the WG charter
References: <C24CB51D5AA800449982D9BCB90325132D4EC1@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB90325132D4EC1@NAEX13.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: "Kent Leung \(kleung\)" <kleung@cisco.com>, mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Narayanan, Vidya wrote:
> Hi Kent, If NETLMM supported IPv4 endpoints, do we still need a 
> standardized PMIPv4 solution?

Not sure what NETLMM is, or whether it supported IPv4 endpoints.

The other question is whether the known FA mode of MIP4 can figure as
a candidate for what WiMax nominates as Proxy MIP, and the CCoA mode
as what WiMax nominates Client MIP.

Alex

> Or, is this an effort to document what has been already deployed?
> 
> Regards, Vidya
> 
> ------------------------------------------------------------------------
>  *From:* Kent Leung (kleung) [mailto:kleung@cisco.com] *Sent:* 
> Friday, November 17, 2006 9:52 AM *To:* mip4@ietf.org *Subject:* 
> [Mip4] Proxy Mobile IPv4 in the WG charter
> 
> Hi.  The draft-leung-mip4-proxy-mode-01.txt draft describes using 
> Mobile IPv4 in proxy mode to provide network-based mobility 
> management.  There will need to be some more work on the draft. But
> wanted to get some sense of support for Proxy Mobile IPv4 in this
> WG.  Certainly there are a few SDOs which have either adopted or
> interested in such mechanism.
> 
> Do folks want to take this on as a WG item eventually?
> 
> Kent
> 


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Nov 21 14:33:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GmbNM-0003qs-0g; Tue, 21 Nov 2006 14:33:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GmZeY-0005el-Tz
	for mip4@ietf.org; Tue, 21 Nov 2006 12:43:26 -0500
Received: from mail.sis.pitt.edu ([136.142.116.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GmZeX-0002hj-Jt
	for mip4@ietf.org; Tue, 21 Nov 2006 12:43:26 -0500
Received: from gis39 (gis39.exp.sis.pitt.edu [136.142.118.94])
	by mail.sis.pitt.edu (8.13.8/8.13.8) with ESMTP id kALHhDk4023788
	for <mip4@ietf.org>; Tue, 21 Nov 2006 12:43:13 -0500 (EST)
Date: Tue, 21 Nov 2006 12:43:13 -0500 (EST)
Message-ID: <3874052.1771164131003015.JavaMail.javamailuser@localhost>
From: James Joshi <jjoshi@mail.sis.pitt.edu>
To: mip4@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.58 on 136.142.116.22
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
X-Mailman-Approved-At: Tue, 21 Nov 2006 14:33:47 -0500
Subject: [Mip4] CFP NetCri-07
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

[Apologies for multiple postings]

The First International Workshop on Research Challenges in Next Generation Networks for First Responders and Critical Infrastructures
http://www.cs.umd.edu/~sharno/NetCri07/

In conjunction with
The IEEE IPCCC 2007, New Orleans, Louisiana, April 11-13
http://www.ipccc.org/

===================================================================


Program Description
-------------------

As advances in pervasive computing, wireless communication and sensor networks continue, more opportunities are open to first responders and critical infrastructures to benefit from these technologies. Providing first responders with the best possible technology, infrastructure and services help save the lives of the general public and the first responders as well. One of the main challenges to the operations of first responders and critical infrastructures is to deploy a communication network that is dependable, secure, and rapidly deployable. In order to operate effectively, the deployed network supports services such as location determination, audio and video communication, and in site and remote sensing. Another key feature for first responders and critical infrastructures networks is to support interactions among multiple heterogeneous networks.

This workshop provides a forum for researchers, industry, and government agencies to discuss the challenges facing the design, deployment and operational issues for next generation network support for first responders and critical infrastructure. The workshop will identify and define fundamental concepts and techniques, resolve conflicts between different approaches in the area, and provide a common ground for an advanced research and development agenda. Topics of interest include, but are not limited to:

- Smart environments (buildings, roads, vehicles, etc.)
- Fast roaming in heterogonous network environment
- Localization and time synchronization 
- Rapidly deployable and self configuring services and networks
- Security, dependability, privacy, and performance trade-offs
- QoS in heterogeneous wireless networks
- Sensor and actuator networks for information gathering and real-time control
- Network and system support for augmented reality and visual analytics
- Test beds
- Simulation studies of first responders and critical infrastructures? networks
- Novel and adaptive communication protocols to support first responders and critical infrastructure? operation
- Resource management and allocation
- Power control management
- Admission, load and flow control
- Performance analysis and experimentation of heterogeneous wireless networks
- Security techniques and methods for heterogeneous wireless networks
- Interoperability among WLANs, Cellular, WSN and wired networks
- Measurements on heterogeneous networks
- Mobility models and traffic patterns in disaster areas
- Cross-layer design


Workshop Co-chairs
------------------

Mohamed Eltoweissy, Virginia Tech, USA
Moustafa Youssef, University of Maryland, USA


Publicity Chair
------------------

Tamer Elsharnouby, Microsoft Corporation, USA
James Joshi, University of Pittsburgh, USA


Technical Program Committee
------------------

Arup Acharya, IBM TJ Watson Research Center, USA
Ashok Agrawala, University of Maryland, USA
Mustaque Ahamad, Georgia Tech, USA
Jonathan Agre, Fujitsu Lab, USA
Nils Aschenbruck, University of Bonn, Germany
Farag Azzedine, King Fahd University, Saudi Arabia
Doreen Cheng, Samsung Research, USA
Nagwa Elmakky, Alexandria University, Egypt
Mohamed Gouda, University of Texas, USA
Elena Guara, Coventry University, UK
Wendi Heinzelman, University of Rochester, USA
James Joshi, University of Pittsburgh, USA
P. Krishnan, Avaya Labs, USA
Scott Midkiff, Virginia Tech, USA
Tamer Nadeem,  Siemens Research, USA
Dragos Niculescu, NEC Labs, USA
Stephan Olariu, Old Dominion University, USA
Stephen D. Wolthusen,  University of London, USA
Mohamed Younis,  University of Maryland at Baltimore County, USA
Adel Youssef, Google, USA




-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Nov 21 19:46:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GmgFL-0005QU-Ka; Tue, 21 Nov 2006 19:45:51 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GmgFK-0005QN-KD
	for mip4@ietf.org; Tue, 21 Nov 2006 19:45:51 -0500
Received: from mgw-ext11.nokia.com ([131.228.20.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GmgFI-00066L-Ub
	for mip4@ietf.org; Tue, 21 Nov 2006 19:45:50 -0500
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext11.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id
	kAM0LkfQ018415 for <mip4@ietf.org>; Wed, 22 Nov 2006 02:23:25 +0200
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Nov 2006 02:22:18 +0200
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Nov 2006 18:22:15 -0600
Received: from [10.241.174.73] ([10.241.174.73]) by daebe101.NOE.Nokia.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Nov 2006 18:22:16 -0600
Message-ID: <45639838.5090507@nokia.com>
Date: Tue, 21 Nov 2006 16:22:16 -0800
From: "Charles E. Perkins" <charles.perkins@nokia.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Mobile IPv4 Mailing List <mip4@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Nov 2006 00:22:16.0125 (UTC)
	FILETIME=[438E7ED0:01C70DCC]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Subject: [Mip4] New revision for rfc3344bis;
	UDP inconsistency and candidate solution
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hello folks,

I have a revision of rfc3344bis all ready to go.  I am
thinking about making one further small modification,
according to the following discussion.

Some time ago, I received an e-mail about some
inconsistency in the language used by rfc3344bis
when describing the handling of the Source Port field
of Registration Reply messages by the home agent.

The confusion arises because of the following conflicting
elements of the specification:
- The UDP destination port of the Registration Request
   is set to 434
- The home agent is mandated to copy the value of the
   destination port of the Registration Request message
   into the UDP source port field of the Registration Reply
- That source port field is described as "variable".

As pointed out, copying the value of the destination
port into the source port should be identically the same
as setting the source port value to 434.  So, the value
of the field cannot be described as "variable" as things
now stand.

It could well be that there are implementations of
foreign agents and mobile nodes that check to make
sure that the value is correct according to the above
specified procedure, so I am reluctant to change the
actual behavior of the home agent.

I propose the following text changes:

(A) In section "3.4. Registration Reply", change

 >    UDP fields:
 >
 >        Source Port           <variable>

to be:

    UDP fields:

        Source Port           434

This conforms also with language used in
section 3.7.2.3.


(B). In section "3.8.3.1. IP/UDP Fields", change:

 >       UDP Source Port
 >                Copied from the UDP Destination Port of the Registration
 >                Request.

to be:

          UDP Source Port
                 Set to the value 434

=============================================

I expect to send out the new revision of rfc3344bis with
these changes in the next day or two.  This revision is
otherwise the same as should have already have been
posted to the Internet Draft before the recent IETF
meeting.

Regards,
Charlie P.

PS. Thanks to Hrishikesh Kulkarni for pointing out the
        discrepancy on this matter.

-- 
Please address return e-mail to charles.perkins@nokia.com


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Nov 22 03:26:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GmnQj-0006lp-La; Wed, 22 Nov 2006 03:26:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GmnQi-0006lh-NY
	for mip4@ietf.org; Wed, 22 Nov 2006 03:26:04 -0500
Received: from firewall.codebay.fi ([212.68.7.211])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GmnQh-0002fG-EN
	for mip4@ietf.org; Wed, 22 Nov 2006 03:26:04 -0500
Received: from [172.20.100.221] by firewall.codebay.fi with esmtp (Exim 4.63)
	(envelope-from <sami.vaarala@iki.fi>)
	id 1GmnQO-0006rL-WD; Wed, 22 Nov 2006 10:25:45 +0200
Message-ID: <456409F8.7070302@iki.fi>
Date: Wed, 22 Nov 2006 10:27:36 +0200
From: Sami Vaarala <sami.vaarala@iki.fi>
User-Agent: Mail/News 1.5 (X11/20060228)
MIME-Version: 1.0
To: "Charles E. Perkins" <charles.perkins@nokia.com>
Subject: Re: [Mip4] New revision for rfc3344bis;
	UDP inconsistency and candidate solution
References: <45639838.5090507@nokia.com>
In-Reply-To: <45639838.5090507@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Charles E. Perkins wrote:
> Hello folks,
 > [...]
> 
> As pointed out, copying the value of the destination
> port into the source port should be identically the same
> as setting the source port value to 434.  So, the value
> of the field cannot be described as "variable" as things
> now stand.

Hi,

I haven't been following this discussion closely, but there
may be cases with NATs and port forwarding where this assumption
is incorrect.  For instance, if the HA is behind a port forwarding
device, the MN may be sending to port 434 but HA receiving at some
other port.

This is, of course, not necessarily something that has to be dealt
with in 3344bis, but a NAT/PF supporting implementation will have
to deal with.

BR,

-Sami

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Nov 22 04:08:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gmo6B-0006iV-37; Wed, 22 Nov 2006 04:08:55 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gmo69-0006i9-Ee
	for mip4@ietf.org; Wed, 22 Nov 2006 04:08:53 -0500
Received: from av6-2-sn3.vrr.skanova.net ([81.228.9.180])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Gmo66-0007fz-U8
	for mip4@ietf.org; Wed, 22 Nov 2006 04:08:53 -0500
Received: by av6-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id CFB4238311; Wed, 22 Nov 2006 10:08:49 +0100 (CET)
Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net
	[81.228.9.102]) by av6-2-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 60A5A388CC; Wed, 22 Nov 2006 10:08:49 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 2A97937E4A;
	Wed, 22 Nov 2006 10:08:47 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1Gmo62-0002Oz-U8; Wed, 22 Nov 2006 10:08:47 +0100
Message-ID: <4564139D.4090704@levkowetz.com>
Date: Wed, 22 Nov 2006 10:08:45 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: Sami Vaarala <sami.vaarala@iki.fi>
Subject: Re: [Mip4] New revision for rfc3344bis;
	UDP inconsistency and candidate solution
References: <45639838.5090507@nokia.com> <456409F8.7070302@iki.fi>
In-Reply-To: <456409F8.7070302@iki.fi>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: "Charles E. Perkins" <charles.perkins@nokia.com>,
	Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0693751525=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0693751525==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig0764D5886B3B3095C2F20770"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig0764D5886B3B3095C2F20770
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

on 2006-11-22 09:27 Sami Vaarala said the following:
> Charles E. Perkins wrote:
>> Hello folks,
>  > [...]
>>=20
>> As pointed out, copying the value of the destination
>> port into the source port should be identically the same
>> as setting the source port value to 434.  So, the value
>> of the field cannot be described as "variable" as things
>> now stand.
>=20
> Hi,
>=20
> I haven't been following this discussion closely, but there
> may be cases with NATs and port forwarding where this assumption
> is incorrect.  For instance, if the HA is behind a port forwarding
> device, the MN may be sending to port 434 but HA receiving at some
> other port.

I agree with Sami.  Removing the 'variable' characterisation is fine,
but I'd still prefer to retain the current language which specifies
copying the incoming destination port value into the outgoing source
port value.


	Henrik


--------------enig0764D5886B3B3095C2F20770
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFZBOeeVhrtTJkXCMRAnchAJ0XhqCV34ukqWWCsQ8pmn87W2skUgCfXYd0
nhAN7W+9YU/+sct5fPSmpHw=
=jpC7
-----END PGP SIGNATURE-----

--------------enig0764D5886B3B3095C2F20770--


--===============0693751525==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0693751525==--




From mip4-bounces@ietf.org Wed Nov 22 08:23:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gms43-0008Nv-6l; Wed, 22 Nov 2006 08:22:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gms42-0008N9-Dy
	for mip4@ietf.org; Wed, 22 Nov 2006 08:22:58 -0500
Received: from mail119.messagelabs.com ([216.82.241.179])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gms41-00088h-7L
	for mip4@ietf.org; Wed, 22 Nov 2006 08:22:58 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-7.tower-119.messagelabs.com!1164201776!6242046!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.100]
Received: (qmail 12297 invoked from network); 22 Nov 2006 13:22:56 -0000
Received: from motgate.mot.com (HELO motgate.mot.com) (129.188.136.100)
	by server-7.tower-119.messagelabs.com with SMTP;
	22 Nov 2006 13:22:56 -0000
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate.mot.com (Motorola/Motorola) with ESMTP id kAMDMtps025875;
	Wed, 22 Nov 2006 06:22:56 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id kAMDMrOf005302;
	Wed, 22 Nov 2006 07:22:54 -0600 (CST)
Message-ID: <45644F2D.2070805@motorola.com>
Date: Wed, 22 Nov 2006 14:22:53 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Sami Vaarala <sami.vaarala@iki.fi>
Subject: Re: [Mip4] New revision for rfc3344bis;
	UDP inconsistency and candidate solution
References: <45639838.5090507@nokia.com> <456409F8.7070302@iki.fi>
In-Reply-To: <456409F8.7070302@iki.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: "Charles E. Perkins" <charles.perkins@nokia.com>,
	Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Sami Vaarala wrote:
> Charles E. Perkins wrote:
>> Hello folks, [...]
>> 
>> As pointed out, copying the value of the destination port into
>> the source port should be identically the same as setting the
>> source port value to 434.  So, the value of the field cannot be
>> described as "variable" as things now stand.
> 
> Hi,
> 
> I haven't been following this discussion closely, but there may be
> cases with NATs and port forwarding where this assumption is
> incorrect.  For instance, if the HA is behind a port forwarding 
> device, the MN may be sending to port 434 but HA receiving at some 
> other port.
> 
> This is, of course, not necessarily something that has to be dealt 
> with in 3344bis, but a NAT/PF supporting implementation will have 
> to deal with.

Intermediary NAT/FWDs (between MN and HA) can indeed change port
numbers, but it would make little sense to change the dst port number
of a packet from MN and HA; probably they better change the src port
number of that packet.  It may happen they do though.

Alex



-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Nov 22 08:26:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gms7G-0003gH-7t; Wed, 22 Nov 2006 08:26:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gms7E-0003fY-Np
	for mip4@ietf.org; Wed, 22 Nov 2006 08:26:16 -0500
Received: from mail128.messagelabs.com ([216.82.250.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gms7C-0008Mz-DB
	for mip4@ietf.org; Wed, 22 Nov 2006 08:26:16 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-12.tower-128.messagelabs.com!1164201769!473194!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [144.189.100.103]
Received: (qmail 20842 invoked from network); 22 Nov 2006 13:22:50 -0000
Received: from motgate3.mot.com (HELO motgate3.mot.com) (144.189.100.103)
	by server-12.tower-128.messagelabs.com with SMTP;
	22 Nov 2006 13:22:50 -0000
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate3.mot.com (8.12.11/Motorola) with ESMTP id kAMDMjS1011224;
	Wed, 22 Nov 2006 06:22:45 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id kAMDMguq005132;
	Wed, 22 Nov 2006 07:22:43 -0600 (CST)
Message-ID: <45644F21.1000902@motorola.com>
Date: Wed, 22 Nov 2006 14:22:41 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: [Mip4] New revision for rfc3344bis;
	UDP inconsistency and candidate solution
References: <45639838.5090507@nokia.com> <456409F8.7070302@iki.fi>
	<4564139D.4090704@levkowetz.com>
In-Reply-To: <4564139D.4090704@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: "Charles E. Perkins" <charles.perkins@nokia.com>,
	Sami Vaarala <sami.vaarala@iki.fi>,
	Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Henrik Levkowetz wrote:
> Hi,
> 
> on 2006-11-22 09:27 Sami Vaarala said the following:
>> Charles E. Perkins wrote:
>>> Hello folks, [...] As pointed out, copying the value of the 
>>> destination port into the source port should be identically the
>>>  same as setting the source port value to 434.  So, the value
>>> of the field cannot be described as "variable" as things now 
>>> stand.
>> Hi,
>> 
>> I haven't been following this discussion closely, but there may 
>> be cases with NATs and port forwarding where this assumption is 
>> incorrect.  For instance, if the HA is behind a port forwarding 
>> device, the MN may be sending to port 434 but HA receiving at 
>> some other port.
> 
> I agree with Sami.  Removing the 'variable' characterisation is 
> fine, but I'd still prefer to retain the current language which 
> specifies copying the incoming destination port value into the 
> outgoing source port value.

Somehow yes.

Isn't it that the 'variable' word is there to mention that the src
port number of RegRep can be anything (not necessarily 434)?  Tcp
server implementations often run that way: listen on a well-known port
number for establishing connections but use the next available (above
10000) port number for src of packet sent by server.

I don't have strong feelings about that, and implementations with
fixed 434 port number on both ways can work ok too.

Alex


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Nov 22 09:43:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GmtJm-0003yr-62; Wed, 22 Nov 2006 09:43:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GmtJk-0003wK-Og
	for mip4@ietf.org; Wed, 22 Nov 2006 09:43:16 -0500
Received: from zcars04f.nortel.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GmtJi-0001Pc-8p
	for mip4@ietf.org; Wed, 22 Nov 2006 09:43:16 -0500
Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com
	[47.103.123.73])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	kAMEgwo15450; Wed, 22 Nov 2006 09:42:58 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] New revision for rfc3344bis;
	UDP inconsistency and candidate solution
Date: Wed, 22 Nov 2006 08:42:57 -0600
Message-ID: <6FC4416DDE56C44DA0AEE67BC7CA43711191A5CD@zrc2hxm2.corp.nortel.com>
In-Reply-To: <4564139D.4090704@levkowetz.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] New revision for rfc3344bis;
	UDP inconsistency and candidate solution
Thread-Index: AccOFhTriJ/f6NXwRx+OrICIBTi8hAALcKOQ
From: "Ahmad Muhanna" <amuhanna@nortel.com>
To: "Henrik Levkowetz" <henrik@levkowetz.com>,
	"Sami Vaarala" <sami.vaarala@iki.fi>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: "Charles E. Perkins" <charles.perkins@nokia.com>,
	Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org


Since this has been out there with no reported issues and problems for a
long time, I believe if we need to make any changes, we need to allow
the current wording for backward compatibility.

Regards,
Ahmad
=20

> -----Original Message-----
> From: Henrik Levkowetz [mailto:henrik@levkowetz.com]=20
> Sent: Wednesday, November 22, 2006 3:09 AM
> To: Sami Vaarala
> Cc: Charles E. Perkins; Mobile IPv4 Mailing List
> Subject: Re: [Mip4] New revision for rfc3344bis; UDP=20
> inconsistency and candidate solution
>=20
> Hi,
>=20
> on 2006-11-22 09:27 Sami Vaarala said the following:
> > Charles E. Perkins wrote:
> >> Hello folks,
> >  > [...]
> >>=20
> >> As pointed out, copying the value of the destination port into the=20
> >> source port should be identically the same as setting the=20
> source port=20
> >> value to 434.  So, the value of the field cannot be described as=20
> >> "variable" as things now stand.
> >=20
> > Hi,
> >=20
> > I haven't been following this discussion closely, but there may be=20
> > cases with NATs and port forwarding where this assumption is=20
> > incorrect.  For instance, if the HA is behind a port forwarding=20
> > device, the MN may be sending to port 434 but HA receiving at some=20
> > other port.
>=20
> I agree with Sami.  Removing the 'variable' characterisation=20
> is fine, but I'd still prefer to retain the current language=20
> which specifies copying the incoming destination port value=20
> into the outgoing source port value.
>=20
>=20
> 	Henrik
>=20
>=20

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Nov 22 10:35:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gmu83-0006Kr-6p; Wed, 22 Nov 2006 10:35:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gmu2k-0001qk-HO; Wed, 22 Nov 2006 10:29:46 -0500
Received: from reserv5.univ-lille1.fr ([193.49.225.19])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gmu2f-0006Ny-Fh; Wed, 22 Nov 2006 10:29:46 -0500
Received: from malonne.lifl.fr (malonne.lifl.fr [134.206.10.29])
	by reserv5.univ-lille1.fr (8.13.7/jtpda-5.3.1) with ESMTP id
	kAMFRlGY028704 ; Wed, 22 Nov 2006 16:27:47 +0100
Received: from ROMY (romy.lifl.fr [134.206.11.216])
	by malonne.lifl.fr  with ESMTP id kAMFRaq02734
	; Wed, 22 Nov 2006 16:27:37 +0100 (MET)
From: "Nathalie Mitton" <nathalie.mitton@inria.fr>
To: "Nathalie Mitton" <nathalie.mitton@inria.fr>
Date: Wed, 22 Nov 2006 16:27:51 +0100
Organization: LIFL
Message-ID: <003001c70e4a$cdb18340$d80bce86@ROMY>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Thread-Index: AccOR1mGwiOkvBT/Qoygmr1ifrv/zQAAPbzA
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2
	(reserv5.univ-lille1.fr [193.49.225.19]);
	Wed, 22 Nov 2006 16:27:55 +0100 (CET)
X-USTL-MailScanner-Information: Please contact the ISP for more information
X-USTL-MailScanner: Found to be clean
X-USTL-MailScanner-From: nathalie.mitton@inria.fr
X-Spam-Status: No
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 69fdda0fad34612ba96c69ba1eef6423
X-Mailman-Approved-At: Wed, 22 Nov 2006 10:35:14 -0500
Cc: 
Subject: [Mip4] TR: CFP - MASS 2007 - Pisa, Italy - October 2007
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0526225726=="
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0526225726==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0031_01C70E53.2F75EB40"

This is a multi-part message in MIME format.

------=_NextPart_000_0031_01C70E53.2F75EB40
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

This message is cross-posted to several lists. Apologies for any duplicate
postings.

 

IEEE MASS 2007 (http://www.ieee-mass.org <http://www.ieee-mass.org/> )

 

The Fourth IEEE International Conference on Mobile Ad-hoc and Sensor Systems

 

Call For Papers

 

Wireless multi-hop communication is envisioned in multiple scenarios where
network nodes communicate via other network nodes: conferences, hospitals,
battlefields, rescue operations, environment control, cars-to-cars, and
monitoring scenarios. Wireless mesh networks have been applied as
alternatives for providing Internet access in remote business and
residential areas. Wireless sensor networks are being deployed for several
industrial control processes and for monitoring environment. This conference
aims to address multi-hop ad-hoc and sensor networks systems, covering
topics ranging from technology issues up to the applications aspects.
Original manuscripts that focus on the analytical modeling,
protocol/algorithm design, and/or experimental studies of the following
topics of interest are sought:

*        physical layer impact on higher level protocols

*        MAC protocols for ad-hoc and sensor networks (802.11, 802.15.4,
UWB) Provisioning of wireless QoS in terms of bandwidth and delay assurance

*        Routing protocols (unicast, multicast, broadcast, geocast) and
routing metrics

*        Data transport in wireless ad hoc and sensor networks

*        Power-aware and energy-efficient design

*        Topology construction and coverage maintenance

*        Cross layer design and optimization

*        Incentives and game theoretic approaches in wireless ad-hoc
networks

*        Localization and synchronization in wireless sensor networks

*        Data gathering, fusion, and dissemination in wireless sensor

*        Reliability, security, and trustworthiness issues in ad hoc and
sensor networks

*        Operating system and middleware support

*        Measurements and practical experience from experimental systems and
test-beds

*        Modeling, analysis and performance evaluation

*        Mesh networking

*        Delay tolerant networks and opportunistic networking

*        Handoff and mobility management and seamless internetworking

*        Peer-to-peer, overlay, and content distribution wireless ad hoc
networks

*        Reliability, security, and trustworthiness issues in ad hoc and
sensor networks

 

Paper submission
All submissions must be full papers in .pdf or .ps (PostScript) format.
Papers must be uploaded to EDAS by March 31, 2007, and must not exceed 10
single-spaced, two-column pages using at least 11 point size fonts on 8.5 x
11 inch pages. Detailed submission instructions will be published in due
time on the conference website  <http://www.cse.fau.edu/mass2006/>
http://www.ieee-mass.org together with format files.

 

Workshops
Proposals for full day workshops are solicited. Selections will be made
considering the expertise and experience of the workshop organizers and the
relevance of the topic to the central theme of the conference. Proposals of
at most 4 pages, including a 1-page biographical sketch, should be submitted
to the Workshops Chair by March 31, 2007

 

Demos
Technical demonstration of experimental ad hoc networking and computing
systems are solicited. To Instructions for submitting a demo proposal will
be published in due time on the conference website.

 

Important dates
Manuscript Submission Due: March 31, 2007
Acceptance Notification: June 30, 2007
Final Manuscript Due: August 10, 2007

 


------=_NextPart_000_0031_01C70E53.2F75EB40
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"metricconverter"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Georgia;
	panose-1:2 4 5 2 5 4 5 2 3 3;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1029724326;
	mso-list-type:hybrid;
	mso-list-template-ids:683329664 67895297 67895299 67895301 67895297 =
67895299 67895301 67895297 67895299 67895301;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1
	{mso-list-id:1068918932;
	mso-list-template-ids:2008030408;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style>

</head>

<body lang=3DFR link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<div style=3D'border:none;border-bottom:solid windowtext =
1.0pt;padding:0cm 0cm 1.0pt 0cm'>

<p class=3DMsoNormal><b><font size=3D2 color=3D"#660000" =
face=3DGeorgia><span
lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Georgia;color:#660000;
font-weight:bold'>This message is cross-posted to several lists. =
Apologies for
any duplicate postings.<o:p></o:p></span></font></b></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-bottom:solid windowtext =
1.0pt;padding:0cm 0cm 1.0pt 0cm'>

<p class=3DMsoNormal><b><font size=3D5 color=3D"#660000" =
face=3DGeorgia><span
lang=3DEN-GB =
style=3D'font-size:19.0pt;font-family:Georgia;color:#660000;
font-weight:bold'>IEEE MASS 2007 </span></font></b><b><font color=3Dblue
face=3DGeorgia><span lang=3DEN-GB =
style=3D'font-family:Georgia;color:blue;font-weight:
bold'>(<a =
href=3D"http://www.ieee-mass.org/">http://www.ieee-mass.org</a>)<o:p></o:=
p></span></font></b></p>

<p class=3DMsoNormal><b><font size=3D5 color=3D"#660000" =
face=3DGeorgia><span
lang=3DEN-GB =
style=3D'font-size:19.0pt;font-family:Georgia;color:#660000;
font-weight:bold'><o:p>&nbsp;</o:p></span></font></b></p>

<p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><b><font =
size=3D5
color=3D"#660000" face=3DGeorgia><span lang=3DEN-GB =
style=3D'font-size:19.0pt;
font-family:Georgia;color:#660000;font-weight:bold'>The Fourth IEEE
International Conference on <st1:place w:st=3D"on">Mobile</st1:place> =
Ad-hoc and
Sensor Systems<o:p></o:p></span></font></b></p>

<p class=3DMsoNormal><b><font size=3D5 color=3D"#660000" =
face=3DGeorgia><span
lang=3DEN-GB =
style=3D'font-size:19.0pt;font-family:Georgia;color:#660000;
font-weight:bold'><o:p>&nbsp;</o:p></span></font></b></p>

<p class=3DMsoNormal><b><font size=3D5 color=3D"#660000" =
face=3DGeorgia><span
lang=3DEN-GB =
style=3D'font-size:19.0pt;font-family:Georgia;color:#660000;
font-weight:bold'>Call For Papers<o:p></o:p></span></font></b></p>

<p class=3DMsoNormal><b><font size=3D5 color=3D"#660000" =
face=3DGeorgia><span
lang=3DEN-GB =
style=3D'font-size:19.0pt;font-family:Georgia;color:#660000;
font-weight:bold'><o:p>&nbsp;</o:p></span></font></b></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#660000" =
face=3DVerdana><span lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Verdana;color:#660000'>Wireless =
multi-hop
communication is envisioned in multiple scenarios where network nodes
communicate via other network nodes: conferences, hospitals, =
battlefields,
rescue operations, environment control, cars-to-cars, and monitoring =
scenarios.
Wireless mesh networks have been applied as alternatives for providing =
Internet
access in remote business and residential areas. Wireless sensor =
networks are
being deployed for several industrial control processes and for =
monitoring
environment. This conference aims to address multi-hop ad-hoc and sensor
networks systems, covering topics ranging from technology issues up to =
the
applications aspects. Original manuscripts that focus on the analytical
modeling, protocol/algorithm design, and/or experimental studies of the
following topics of interest are sought:<o:p></o:p></span></font></p>

</div>

<div style=3D'border:none;border-bottom:solid windowtext =
1.0pt;padding:0cm 0cm 1.0pt 0cm'>

<p class=3DMsoNormal =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo3'><![if !supportLists]><font
size=3D2 color=3D"#660000" face=3DSymbol><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Symbol;color:#660000'><span =
style=3D'mso-list:Ignore'>&middot;<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana;
color:#660000'>physical layer impact on higher level =
protocols<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo3'><![if !supportLists]><font
size=3D2 color=3D"#660000" face=3DSymbol><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Symbol;color:#660000'><span =
style=3D'mso-list:Ignore'>&middot;<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana;
color:#660000'>MAC protocols for ad-hoc and sensor networks (802.11, =
802.15.4,
UWB) Provisioning of wireless QoS in terms of bandwidth and delay =
assurance<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo3'><![if !supportLists]><font
size=3D2 color=3D"#660000" face=3DSymbol><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Symbol;color:#660000'><span =
style=3D'mso-list:Ignore'>&middot;<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana;
color:#660000'>Routing protocols (unicast, multicast, broadcast, =
geocast) and
routing metrics<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo3'><![if !supportLists]><font
size=3D2 color=3D"#660000" face=3DSymbol><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Symbol;color:#660000'><span =
style=3D'mso-list:Ignore'>&middot;<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana;
color:#660000'>Data transport in wireless ad hoc and sensor =
networks<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo3'><![if !supportLists]><font
size=3D2 color=3D"#660000" face=3DSymbol><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Symbol;color:#660000'><span =
style=3D'mso-list:Ignore'>&middot;<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana;
color:#660000'>Power-aware and energy-efficient =
design<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo3'><![if !supportLists]><font
size=3D2 color=3D"#660000" face=3DSymbol><span =
style=3D'font-size:10.0pt;font-family:
Symbol;color:#660000'><span style=3D'mso-list:Ignore'>&middot;<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span =
style=3D'font-size:10.0pt;font-family:Verdana;color:#660000'>Topology
construction and coverage maintenance<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo3'><![if !supportLists]><font
size=3D2 color=3D"#660000" face=3DSymbol><span =
style=3D'font-size:10.0pt;font-family:
Symbol;color:#660000'><span style=3D'mso-list:Ignore'>&middot;<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span =
style=3D'font-size:10.0pt;font-family:Verdana;color:#660000'>Cross
layer design and optimization<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo3'><![if !supportLists]><font
size=3D2 color=3D"#660000" face=3DSymbol><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Symbol;color:#660000'><span =
style=3D'mso-list:Ignore'>&middot;<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana;
color:#660000'>Incentives and game theoretic approaches in wireless =
ad-hoc
networks<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo3'><![if !supportLists]><font
size=3D2 color=3D"#660000" face=3DSymbol><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Symbol;color:#660000'><span =
style=3D'mso-list:Ignore'>&middot;<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana;
color:#660000'>Localization and synchronization in wireless sensor =
networks<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo3'><![if !supportLists]><font
size=3D2 color=3D"#660000" face=3DSymbol><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Symbol;color:#660000'><span =
style=3D'mso-list:Ignore'>&middot;<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana;
color:#660000'>Data gathering, fusion, and dissemination in wireless =
sensor<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo3'><![if !supportLists]><font
size=3D2 color=3D"#660000" face=3DSymbol><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Symbol;color:#660000'><span =
style=3D'mso-list:Ignore'>&middot;<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana;
color:#660000'>Reliability, security, and trustworthiness issues in ad =
hoc and
sensor networks<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo3'><![if !supportLists]><font
size=3D2 color=3D"#660000" face=3DSymbol><span =
style=3D'font-size:10.0pt;font-family:
Symbol;color:#660000'><span style=3D'mso-list:Ignore'>&middot;<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span =
style=3D'font-size:10.0pt;font-family:Verdana;color:#660000'>Operating
system and middleware support<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo3'><![if !supportLists]><font
size=3D2 color=3D"#660000" face=3DSymbol><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Symbol;color:#660000'><span =
style=3D'mso-list:Ignore'>&middot;<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana;
color:#660000'>Measurements and practical experience from experimental =
systems
and test-beds<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo3'><![if !supportLists]><font
size=3D2 color=3D"#660000" face=3DSymbol><span =
style=3D'font-size:10.0pt;font-family:
Symbol;color:#660000'><span style=3D'mso-list:Ignore'>&middot;<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span =
style=3D'font-size:10.0pt;font-family:Verdana;color:#660000'>Modeling,
analysis and performance evaluation<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo3'><![if !supportLists]><font
size=3D2 color=3D"#660000" face=3DSymbol><span =
style=3D'font-size:10.0pt;font-family:
Symbol;color:#660000'><span style=3D'mso-list:Ignore'>&middot;<font =
size=3D1
face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span =
style=3D'font-size:10.0pt;font-family:Verdana;color:#660000'>Mesh
networking<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo3'><![if !supportLists]><font
size=3D2 color=3D"#660000" face=3DSymbol><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Symbol;color:#660000'><span =
style=3D'mso-list:Ignore'>&middot;<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana;
color:#660000'>Delay tolerant networks and opportunistic =
networking<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo3'><![if !supportLists]><font
size=3D2 color=3D"#660000" face=3DSymbol><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Symbol;color:#660000'><span =
style=3D'mso-list:Ignore'>&middot;<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana;
color:#660000'>Handoff and mobility management and seamless =
internetworking<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo3'><![if !supportLists]><font
size=3D2 color=3D"#660000" face=3DSymbol><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Symbol;color:#660000'><span =
style=3D'mso-list:Ignore'>&middot;<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana;
color:#660000'>Peer-to-peer, overlay, and content distribution wireless =
ad hoc
networks<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo3'><![if !supportLists]><font
size=3D2 color=3D"#660000" face=3DSymbol><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
font-family:Symbol;color:#660000'><span =
style=3D'mso-list:Ignore'>&middot;<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana;
color:#660000'>Reliability, security, and trustworthiness issues in ad =
hoc and
sensor networks<o:p></o:p></span></font></p>

</div>

<div style=3D'border:none;border-bottom:solid windowtext =
1.0pt;padding:0cm 0cm 1.0pt 0cm'>

<p class=3DMsoNormal><font size=3D2 color=3D"#660000" =
face=3DVerdana><span lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Verdana;color:#660000'><o:p>&nbsp;<=
/o:p></span></font></p>

<p class=3DMsoNormal><b><font size=3D3 color=3D"#660000" =
face=3DVerdana><span
lang=3DEN-GB =
style=3D'font-size:12.0pt;font-family:Verdana;color:#660000;
font-weight:bold'>Paper submission</span></font></b><font =
color=3D"#660000"
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-family:Verdana;color:#660000'><br>
</span></font><font size=3D2 color=3D"#660000" face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Verdana;color:#660000'>All =
submissions must
be full papers in .pdf or .ps (PostScript) format. Papers must be =
uploaded to
EDAS by March 31, 2007, and must not exceed 10 single-spaced, two-column =
pages
using at least 11 point size fonts on 8.5 x <st1:metricconverter
ProductID=3D"11 inch" w:st=3D"on">11 inch</st1:metricconverter> pages. =
Detailed
submission instructions will be published in due time on the conference =
website
</span></font><font size=3D2 color=3D"#660000" face=3DVerdana><span =
style=3D'font-size:
10.0pt;font-family:Verdana;color:#660000'><a
href=3D"http://www.cse.fau.edu/mass2006/"><b><font size=3D1><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-weight:bold;text-decoration:none'>http://ww=
w.ieee-mass.org
together with</span></font></b><b><font size=3D1 color=3D"#990000"><span
lang=3DEN-GB =
style=3D'font-size:9.0pt;color:#990000;font-weight:bold;text-decoration:
none'> </span></font></b></a></span></font><font size=3D2 =
color=3D"#660000"
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Verdana;
color:#660000'>format files.</span></font><b><font size=3D5 =
color=3D"#660000"
face=3DGeorgia><span lang=3DEN-GB =
style=3D'font-size:19.0pt;font-family:Georgia;
color:#660000;font-weight:bold'><o:p></o:p></span></font></b></p>

<p class=3DMsoNormal><b><font size=3D5 color=3D"#660000" =
face=3DGeorgia><span
lang=3DEN-GB =
style=3D'font-size:19.0pt;font-family:Georgia;color:#660000;
font-weight:bold'><o:p>&nbsp;</o:p></span></font></b></p>

<p class=3DMsoNormal><b><font size=3D3 color=3D"#660000" =
face=3DVerdana><span
lang=3DEN-GB =
style=3D'font-size:12.0pt;font-family:Verdana;color:#660000;
font-weight:bold'>Workshops</span></font></b><font color=3D"#660000"
face=3DVerdana><span lang=3DEN-GB =
style=3D'font-family:Verdana;color:#660000'><br>
</span></font><font size=3D2 color=3D"#660000" face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Verdana;color:#660000'>Proposals =
for full
day workshops are solicited. Selections will be made considering the =
expertise and
experience of the workshop organizers and the relevance of the topic to =
the
central theme of the conference. Proposals of at most 4 pages, including =
a
1-page biographical sketch, should be submitted to the Workshops Chair =
by March
31, 2007<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#660000" =
face=3DVerdana><span lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Verdana;color:#660000'><o:p>&nbsp;<=
/o:p></span></font></p>

<p class=3DMsoNormal><b><font size=3D3 color=3D"#660000" =
face=3DVerdana><span
lang=3DEN-GB =
style=3D'font-size:12.0pt;font-family:Verdana;color:#660000;
font-weight:bold'>Demos</span></font></b><font color=3D"#660000" =
face=3DVerdana><span
lang=3DEN-GB style=3D'font-family:Verdana;color:#660000'><br>
</span></font><font size=3D2 color=3D"#660000" face=3DVerdana><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Verdana;color:#660000'>Technical
demonstration of experimental ad hoc networking and computing systems =
are
solicited. To Instructions for submitting a demo proposal will be =
published in
due time on the conference website.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#660000" =
face=3DVerdana><span lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:Verdana;color:#660000'><o:p>&nbsp;<=
/o:p></span></font></p>

<p class=3DMsoNormal><b><font size=3D3 color=3D"#660000" =
face=3DVerdana><span
style=3D'font-size:12.0pt;font-family:Verdana;color:#660000;font-weight:b=
old'>Important
dates</span></font></b><font color=3D"#660000" face=3DVerdana><span
style=3D'font-family:Verdana;color:#660000'><br>
</span></font><font size=3D2 color=3D"#660000" face=3DVerdana><span =
style=3D'font-size:
10.0pt;font-family:Verdana;color:#660000'>Manuscript Submission Due: =
March 31,
2007<br>
Acceptance Notification: June 30, 2007<br>
Final Manuscript Due: August 10, 2007<o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0031_01C70E53.2F75EB40--



--===============0526225726==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0526225726==--





From mip4-bounces@ietf.org Wed Nov 22 11:35:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gmv47-0005PC-Ci; Wed, 22 Nov 2006 11:35:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gmv46-0005OL-6K
	for mip4@ietf.org; Wed, 22 Nov 2006 11:35:14 -0500
Received: from av9-1-sn3.vrr.skanova.net ([81.228.9.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gmv3t-0008CB-6z
	for mip4@ietf.org; Wed, 22 Nov 2006 11:35:14 -0500
Received: by av9-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 64F6A37FED; Wed, 22 Nov 2006 17:35:00 +0100 (CET)
Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net
	[81.228.9.102]) by av9-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 43B4B37EA8; Wed, 22 Nov 2006 17:35:00 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 55F1537E93;
	Wed, 22 Nov 2006 17:34:57 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1Gmv3h-0002hT-U9; Wed, 22 Nov 2006 17:34:50 +0100
Message-ID: <45647C27.4040208@levkowetz.com>
Date: Wed, 22 Nov 2006 17:34:47 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: mip4-ads@tools.ietf.org, Mobile IPv4 Mailing List <mip4@ietf.org>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c0aa019322dfce838bd8604f5a841b57
Cc: mip4-chairs@tools.ietf.org
Subject: [Mip4] Charter Update Proposal
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0697477140=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0697477140==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig6289D48CB10A78F48AA9092B"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig6289D48CB10A78F48AA9092B
Content-Type: multipart/mixed; boundary="------------060807040904090709040201"

This is a multi-part message in MIME format.
--------------060807040904090709040201
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,


Both the list and the WG meeting during IETF-67 indicated support for
adding moving network support and a notification mechanism to the
charter, so below is a proposal for a charter update.  (The resulting
charter, if the updates are accepted, are provided as an attachment.)

We propose to add the following two items to the list of work to
be done:

  11. MIPv4 Moving Network Support

  The Network Mobility (nemo) working group deals with the problem of
  mobility of a whole network, such as might exist inside a vehicle,
  train, or airplane.  The nemo working group has developed draft
  specifications for both IPv6 and IPv4 mobile networks.  However, it has=

  been recognized that the IPv4 version of the protocol can be viewed as
  an extension of the basic Mobile IPv4 protocol, and there is good reaso=
n
  to do this extension in the mip4 working group.  The working group will=

  take on the MIPv4 network mobility internet draft and progress it along=

  the standards track.  In addition, the working group will take up
  extensions to the basic MIPv4 moving network support in the areas of
  dynamic prefix assignment and foreign agent support.


  12. Asynchronous Notification Mechanism

  In some situations, there is a need for Mobile IPv4 entities, such as
  the home agent, foreign agent and mobile node to send and receive
  asynchronous notification events during a mobility session.  The base
  Mobile IP Specification [RFC3344] does not have a provision for this. A=

  new MIPv4 message pair which would support asynchronous notifications,
  and a notification model describing how to use these messages has been
  proposed.  The working group will take on the existing MIPv4
  notification message draft as a starting point, review and update it as=

  needed, and progress it as a standards track document.  In addition, th=
e
  working group will also consider defining specific usages of the
  notification message based on the examples in the current document.=20

We also propose to add the following milestones:

   Sep 2007	Base MIPv4 Mobile Network Support (Draft Std.) to IESG
   Nov 2007	MIPv4 Mobile Network Support for FAs (Draft Std.) to IESG
   Nov 2007	MIPv4 Mobile Network Support Dynamic Address Assignment (Draf=
t Std.) to IESG


If you have comments or suggestions relating to the suggested update, ple=
ase
send them to the list.


Best Regards,

	Henrik and Pete



--------------060807040904090709040201
Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0";
	name="mip4-charter-2006-11-22.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="mip4-charter-2006-11-22.txt"

Mobility for IPv4 (mip4)
------------------------

 Charter
 Last Modified: 2006-07-25

 Current Status: Active Working Group

 Chair(s):
     Henrik Levkowetz  <henrik@levkowetz.com>
     Pete McCann  <mccap@petoni.org>

 Internet Area Director(s):
     Jari Arkko  <jari.arkko@piuha.net>
     Mark Townsley  <townsley@cisco.com>

 Internet Area Advisor:
     Jari Arkko  <jari.arkko@piuha.net>

 Mailing Lists:=20
     General Discussion:mip4@ietf.org
     To Subscribe:      mip4-request@ietf.org
         In Body:       subscribe
     Archive:           http://www.ietf.org/mail-archive/web/mip4/index.h=
tml

Description of Working Group:

IP mobility support for IPv4 nodes (hosts and routers) is specified in
RFC3344. RFC 3344 mobility allows a node to continue using its
"permanent" home address as it moves around the Internet. The Mobile
IP protocols support transparency above the IP layer, including
maintenance of active TCP connections and UDP port bindings.  Besides
the basic Mobile IPv4 (MIPv4) protocols, several other drafts deal
with concerns such as optimization, security, extensions, AAA support,
and deployment issues.

MIPv4 is currently being deployed on a wide basis (e.g., in cdma2000
networks). The scope of the deployment is on a fairly large scale and
accordingly, the MIP4 WG will focus on deployment issues and on
addressing known deficiencies and shortcomings in the protocol that
have come up as a result of deployment experience. Specifically, the
working group will complete the work items to facilitate interactions
with AAA environments, interactions with enterprise environments when
MIPv4 is used therein, and updating existing protocol specifications
in accordance with deployment needs and advancing those protocols that
are on the standards track.

Work expected to be done by the MIP4 WG as proposed by this charter is
as follows:

1. MIPv4 has been a proposed standard for several years. It has been
adopted by other standard development organizations and has been
deployed commercially. One of the next steps for the WG is to advance
the protocol to draft standard status. As part of advancing base
Mobile IP specs to DS, the MIPv4 NAI RFC (2794) will be revised to
reflect implementation experience.

2. Work items that are pending from the previous Mobile IP WG, which
will be completed by the MIP4 WG, are:

- completion of the MIB for the revised base Mobile IP specification
(2006bis)

- regional registration draft.

3. The MIP4 WG will also complete the work on MIPv4 interactions in
VPN scenarios. This work will involve identifying the requirements and
a solution development for MIPv4 operation in the presence of IPsec
VPNs.

4. Additionally, a proposal has been made for how MOBIKE could work
together with MIPv4. This proposal does not describe any new protocol,
but formulates a best current practice for deploying MOBIKE together
with MIPv4. The working group will adopt and complete this document.

5. Some issues have been raised with respect to RFC3519. These will be
identified and addressed as appropriate, through errata, revision of
RFC 3519, and/or supplemental documents as needed.

6. It has been proposed that the FMIP protocol, which has been
standardised for MIPv6 in the MIPSHOP working group, should also be
published as an experimental protocol for MIPv4. A draft for this
exists. The working group will take up and carry this work forward to
publication

7. An extension to carry generic strings in the Registration Reply
message has been proposed. The purpose is to supply supplemental
human-readable information intended to the MN user. The working group
will complete the specification and applicability statement of such an
extension.

8. RADIUS attributes for MIP4. A set of RADIUS attributes has been
proposed for MIPv4.

The working group will first produce a requirements specification,
describing how the work differs from the requirements in RFC 2977 and
the functionality provided by RFC 4004 (the MIPv4 Diameter App). The
reason why this first step is required is that RFC 3127 shows that
full RFC 2977 functionality can't be provided by even a considerably
extended RADIUS, so we need to match the requirements to what can be
done within RADIUS.

Provided the requirements work finds approval with ADs and RADEXT WG,
the workgroup will complete the specification of MIPv4 RADIUS
attributes, solicit feedback from the RADEXT WG, adjust, and submit
this for publication. Note that the work may require extensions to the
RADIUS attribute space which will be handled outside the MIP4 WG.

9. MIPv4 Extension for Configuration Options.

Several drafts have proposed extensions to help improve configuration
of MIPv4 clients. The latest proposal is for a general configuration
option extension which could carry information such as e.g., DNS
address and DHCP server address. The working group will take on and
complete one proposal for a configuration option extension.

10. Dual-stack Support

There have been several proposals for how to enable an IPv6 connection
over a network that supports Mobile IPv4. A protocol enhancement to
MIPv4 would allow for IPv6 support in a region where Mobile IPv4 has
already been implemented and deployed. This would allow a dual stack
mobile node to maintain IPv6 connectivity when using MIPv4. The
solution would therefore be applicable only to networks that are
not deploying Mobile IPv6.

The working group will take on and complete one proposal for IPv6 over
Mobile IPv4. This work is restricted to a small protocol extension
similar to current Mobile IPv4 functionality. Support for advanced
Mobile IPv6 functionality is strictly outside the scope.

A problem statement covering both Mobile IPv4 and IPv6 dual-stack
issues is expected to come out of MIP6 WG, and will not be developed
in MIP4 WG.


11. MIPv4 Moving Network Support
=20
The Network Mobility (nemo) working group deals with the problem of
mobility of a whole network, such as might exist inside a vehicle,
train, or airplane.  The nemo working group has developed draft
specifications for both IPv6 and IPv4 mobile networks.  However, it has
been recognized that the IPv4 version of the protocol can be viewed as
an extension of the basic Mobile IPv4 protocol, and there is good reason
to do this extension in the mip4 working group.  The working group will
take on the MIPv4 network mobility internet draft and progress it along
the standards track.  In addition, the working group will take up
extensions to the basic MIPv4 moving network support in the areas of
dynamic prefix assignment and foreign agent support.


12. Asynchronous Notification Mechanism

In some situations, there is a need for Mobile IPv4 entities, such as
the home agent, foreign agent and mobile node to send and receive
asynchronous notification events during a mobility session.  The base
Mobile IP Specification [RFC3344] does not have a provision for this. A
new MIPv4 message pair which would support asynchronous notifications,
and a notification model describing how to use these messages has been
proposed.  The working group will take on the existing MIPv4
notification message draft as a starting point, review and update it as
needed, and progress it as a standards track document.  In addition, the
working group will also consider defining specific usages of the
notification message based on the examples in the current document.=20


Goals and Milestones:

   Done         AAA Keys for MIPv4 to IESG=20
   Done         MIPv4 VPN interaction problem statement to IESG=20
   Done         Low latency handover to experimental=20
   Done         Experimental MIPv4 message and extensions draft to IESG=20
   Done         Dynamic Home Agent assignment protocol solution to IESG=20
   Done         Revised MIPv4 Challenge/Response (3012bis) to IESG=20
   Done         Regional registration document to IESG=20
   Jan 2007     MIPv4 Mobike interaction (BCP) to the IESG=20
   Feb 2007     MIPv4 Extension for Config. Options (Proposed Std.) to th=
e IESG=20
   Dec 2006     MIPv4 VPN interaction (BCP) to the IESG=20
   May 2007     RADIUS Extensions for MIPv4 to the RADEXT WG for comment =

   Jan 2007     Revised MIPv4 specification to IESG for Draft Std.=20
   Dec 2006     Generic Strings for MIPv4 (Proposed Std.) to the IESG=20
   Mar 2007     MIPv4 RADIUS Extensions Requirements to the IESG=20
   Dec 2006     FMIPv4 (Experimental) to the IESG=20
   Sep 2007     RADIUS Extensions for MIPv4 (Proposed Std.) to the IESG=20
   Nov 2007     Revised rfc2794bis (NAI extension) (Draft Std.) to the IE=
SG=20
   Aug 2007     Revised MIB for MIPv4 (Proposed Std.) to IESG=20
   Apr 2007     Dual-stack MIPv4 (Draft Std.) to IESG=20
   Jul 2007	Notification Mechanism (Draft Std.) to IESG
   Sep 2007	Base MIPv4 Mobile Network Support (Draft Std.) to IESG
   Nov 2007	MIPv4 Mobile Network Support for FAs (Draft Std.) to IESG
   Nov 2007	MIPv4 Mobile Network Support Dynamic Address Assignment (Draf=
t Std.) to IESG


--------------060807040904090709040201--

--------------enig6289D48CB10A78F48AA9092B
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFZHwneVhrtTJkXCMRAuH0AKCtsHc824hZb5GD/oNuZgXLfX/ILQCfU9ah
8LWTgD8wg/FNp0B/++aa9C0=
=I3Ww
-----END PGP SIGNATURE-----

--------------enig6289D48CB10A78F48AA9092B--


--===============0697477140==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0697477140==--




From mip4-bounces@ietf.org Thu Nov 23 00:31:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gn7Am-0006b5-OB; Thu, 23 Nov 2006 00:30:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gn7Al-0006az-FJ
	for mip4@ietf.org; Thu, 23 Nov 2006 00:30:55 -0500
Received: from mgw-ext14.nokia.com ([131.228.20.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gn7Aj-0006lX-Qa
	for mip4@ietf.org; Thu, 23 Nov 2006 00:30:55 -0500
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext14.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id
	kAN5TawT019545 for <mip4@ietf.org>; Thu, 23 Nov 2006 07:30:49 +0200
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Nov 2006 07:29:56 +0200
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Nov 2006 23:29:50 -0600
Received: from [10.243.5.68] ([10.243.5.68]) by daebe101.NOE.Nokia.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 22 Nov 2006 23:28:32 -0600
Message-ID: <4565317D.7010506@nokia.com>
Date: Wed, 22 Nov 2006 21:28:29 -0800
From: "Charles E. Perkins" <charles.perkins@nokia.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: ext Ahmad Muhanna <amuhanna@nortel.com>, sami.vaarala@iki.fi
Subject: Re: [Mip4] New revision for rfc3344bis;
	UDP inconsistency and candidate solution
References: <6FC4416DDE56C44DA0AEE67BC7CA43711191A5CD@zrc2hxm2.corp.nortel.com>
In-Reply-To: <6FC4416DDE56C44DA0AEE67BC7CA43711191A5CD@zrc2hxm2.corp.nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Nov 2006 05:28:32.0476 (UTC)
	FILETIME=[3720E1C0:01C70EC0]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org


Hello Ahmad and Sami,

As far as I know, the proposed wording change is
backward compatible.

Regarding port forwarding NATs, I hope there are none
that change the destination port!  The home agent can't
be listening to all the possible destination ports and
treating all incoming messages to all ports as Mobile IP
messages.

I can see that a NAT box might change the source port
number, and the wording changes I proposed would not
affect that.

Isn't this right?

Regards,
Charlie P.


ext Ahmad Muhanna wrote:
> Since this has been out there with no reported issues and problems for a
> long time, I believe if we need to make any changes, we need to allow
> the current wording for backward compatibility.
>
> Regards,
> Ahmad
>  
>
>   
>> -----Original Message-----
>> From: Henrik Levkowetz [mailto:henrik@levkowetz.com] 
>> Sent: Wednesday, November 22, 2006 3:09 AM
>> To: Sami Vaarala
>> Cc: Charles E. Perkins; Mobile IPv4 Mailing List
>> Subject: Re: [Mip4] New revision for rfc3344bis; UDP 
>> inconsistency and candidate solution
>>
>> Hi,
>>
>> on 2006-11-22 09:27 Sami Vaarala said the following:
>>     
>>> Charles E. Perkins wrote:
>>>       
>>>> Hello folks,
>>>>         
>>>  > [...]
>>>       
>>>> As pointed out, copying the value of the destination port into the 
>>>> source port should be identically the same as setting the 
>>>>         
>> source port 
>>     
>>>> value to 434.  So, the value of the field cannot be described as 
>>>> "variable" as things now stand.
>>>>         
>>> Hi,
>>>
>>> I haven't been following this discussion closely, but there may be 
>>> cases with NATs and port forwarding where this assumption is 
>>> incorrect.  For instance, if the HA is behind a port forwarding 
>>> device, the MN may be sending to port 434 but HA receiving at some 
>>> other port.
>>>       
>> I agree with Sami.  Removing the 'variable' characterisation 
>> is fine, but I'd still prefer to retain the current language 
>> which specifies copying the incoming destination port value 
>> into the outgoing source port value.
>>
>>
>> 	Henrik
>>
>>
>>     


-- 
Please address return e-mail to charles.perkins@nokia.com


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Nov 23 04:43:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GnB7I-0008Nt-M6; Thu, 23 Nov 2006 04:43:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GnB7I-0008Nn-BI
	for mip4@ietf.org; Thu, 23 Nov 2006 04:43:36 -0500
Received: from ns.academica.fi ([82.133.251.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GnB7E-000636-Sz
	for mip4@ietf.org; Thu, 23 Nov 2006 04:43:36 -0500
Received: from [82.133.140.68] (ip82-133-140-68.customer.academica.fi
	[82.133.140.68])
	by ns.academica.fi (Postfix) with ESMTP id E54D9199326;
	Thu, 23 Nov 2006 10:41:08 +0200 (EET)
Message-ID: <45656CD6.6050800@iki.fi>
Date: Thu, 23 Nov 2006 11:41:42 +0200
From: Sami Vaarala <sami.vaarala@iki.fi>
User-Agent: Icedove 1.5.0.7 (X11/20061013)
MIME-Version: 1.0
To: "Charles E. Perkins" <charles.perkins@nokia.com>
Subject: Re: [Mip4] New revision for rfc3344bis;
	UDP inconsistency and candidate solution
References: <6FC4416DDE56C44DA0AEE67BC7CA43711191A5CD@zrc2hxm2.corp.nortel.com>
	<4565317D.7010506@nokia.com>
In-Reply-To: <4565317D.7010506@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
	ext Ahmad Muhanna <amuhanna@nortel.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Charles E. Perkins wrote:
> 
> Hello Ahmad and Sami,
> 
> As far as I know, the proposed wording change is
> backward compatible.
> 
> Regarding port forwarding NATs, I hope there are none
> that change the destination port!  The home agent can't
> be listening to all the possible destination ports and
> treating all incoming messages to all ports as Mobile IP
> messages.
> 
> I can see that a NAT box might change the source port
> number, and the wording changes I proposed would not
> affect that.

There are HAs that can listen on other port(s) beside 434.
Operation on these other ports is not directly covered by
the specification as such, but it would be preferable that
the wording "just work" in that case, too.

In particular, it would be bad if an implementor decided
to support running a HA on a non-standard port, receiving
requests on some port X, but still sending responses using
port 443 as source port.  Even though that might work in
some cases, it would likely fail with NAT devices and other
stateful routers; thus it is important for the HA to copy
ports exactly from the RRQ (just swapping them).

That being said, if we want to *preclude* using other ports
in the base specification, then this change is a no-op.

Best,

-Sami

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Nov 23 05:02:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GnBPf-0000nv-RI; Thu, 23 Nov 2006 05:02:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GnBPe-0000nq-QJ
	for mip4@ietf.org; Thu, 23 Nov 2006 05:02:34 -0500
Received: from av10-2-sn2.hy.skanova.net ([81.228.8.182])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GnBPd-0000gy-B7
	for mip4@ietf.org; Thu, 23 Nov 2006 05:02:34 -0500
Received: by av10-2-sn2.hy.skanova.net (Postfix, from userid 502)
	id B253137FEC; Thu, 23 Nov 2006 11:02:32 +0100 (CET)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net
	[81.228.8.92]) by av10-2-sn2.hy.skanova.net (Postfix) with ESMTP
	id 7E5D937F12; Thu, 23 Nov 2006 11:02:32 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id 310EA37E5B;
	Thu, 23 Nov 2006 11:02:32 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1GnBPb-0002VG-KM; Thu, 23 Nov 2006 11:02:31 +0100
Message-ID: <456571AD.8090301@levkowetz.com>
Date: Thu, 23 Nov 2006 11:02:21 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: "Charles E. Perkins" <charles.perkins@nokia.com>
Subject: Re: [Mip4] New revision for rfc3344bis;
	UDP inconsistency and candidate solution
References: <6FC4416DDE56C44DA0AEE67BC7CA43711191A5CD@zrc2hxm2.corp.nortel.com>
	<4565317D.7010506@nokia.com>
In-Reply-To: <4565317D.7010506@nokia.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Cc: sami.vaarala@iki.fi, Mobile IPv4 Mailing List <mip4@ietf.org>,
	ext Ahmad Muhanna <amuhanna@nortel.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0940915626=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0940915626==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig04C204A289025957284E33A6"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig04C204A289025957284E33A6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Charlie

on 2006-11-23 06:28 Charles E. Perkins said the following:
> Hello Ahmad and Sami,
>=20
> As far as I know, the proposed wording change is
> backward compatible.
>=20
> Regarding port forwarding NATs, I hope there are none
> that change the destination port!  The home agent can't
> be listening to all the possible destination ports and
> treating all incoming messages to all ports as Mobile IP
> messages.
>=20
> I can see that a NAT box might change the source port
> number, and the wording changes I proposed would not
> affect that.
>=20
> Isn't this right?

As far as I'm concerned, this is actually immaterial.  There may
or may not be port forwarding NAT cases where the destination
port is changed.  If there are, it has to be set up so on purpose,
however; it won't happen randomly.

What I can see matters is for instance that I have come across cases
where people have for complex reasons wanted to deploy some HAs
listening to other ports than 434.  Changing the specification now to
read 'send on 434' instead of 'copy from destination port' would break
that.

Removing the statement that the port is 'variable' is, I believe,
a good thing.  It removes a blemish.

Changing from 'copy from destination port' to 434 is gratuitous
breakage; it doesn't help consistency, but it does have the potential
for harm.


	Henrik


> Regards,
> Charlie P.
>=20
>=20
> ext Ahmad Muhanna wrote:
>> Since this has been out there with no reported issues and problems for=
 a
>> long time, I believe if we need to make any changes, we need to allow
>> the current wording for backward compatibility.
>>
>> Regards,
>> Ahmad
>> =20
>>
>>  =20
>>> -----Original Message-----
>>> From: Henrik Levkowetz [mailto:henrik@levkowetz.com]=20
>>> Sent: Wednesday, November 22, 2006 3:09 AM
>>> To: Sami Vaarala
>>> Cc: Charles E. Perkins; Mobile IPv4 Mailing List
>>> Subject: Re: [Mip4] New revision for rfc3344bis; UDP=20
>>> inconsistency and candidate solution
>>>
>>> Hi,
>>>
>>> on 2006-11-22 09:27 Sami Vaarala said the following:
>>>    =20
>>>> Charles E. Perkins wrote:
>>>>      =20
>>>>> Hello folks,
>>>>>        =20
>>>>  > [...]
>>>>      =20
>>>>> As pointed out, copying the value of the destination port into the =

>>>>> source port should be identically the same as setting the=20
>>>>>        =20
>>> source port=20
>>>    =20
>>>>> value to 434.  So, the value of the field cannot be described as=20
>>>>> "variable" as things now stand.
>>>>>        =20
>>>> Hi,
>>>>
>>>> I haven't been following this discussion closely, but there may be=20
>>>> cases with NATs and port forwarding where this assumption is=20
>>>> incorrect.  For instance, if the HA is behind a port forwarding=20
>>>> device, the MN may be sending to port 434 but HA receiving at some=20
>>>> other port.
>>>>      =20
>>> I agree with Sami.  Removing the 'variable' characterisation=20
>>> is fine, but I'd still prefer to retain the current language=20
>>> which specifies copying the incoming destination port value=20
>>> into the outgoing source port value.
>>>
>>>
>>> 	Henrik
>>>
>>>
>>>    =20
>=20
>=20


--------------enig04C204A289025957284E33A6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFZXG2eVhrtTJkXCMRAsWrAKCSqYLlojOy5qPa1LRmdHsK+5F/mgCgv7B8
dGyaHgTF2JNQ8fm4AgFxVkk=
=k9iN
-----END PGP SIGNATURE-----

--------------enig04C204A289025957284E33A6--


--===============0940915626==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0940915626==--




From mip4-bounces@ietf.org Thu Nov 23 15:20:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GnL3F-0005Lu-LJ; Thu, 23 Nov 2006 15:20:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GnL3D-0005Lo-JC
	for mip4@ietf.org; Thu, 23 Nov 2006 15:20:03 -0500
Received: from zcars04f.nortel.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GnL3C-0004mk-9C
	for mip4@ietf.org; Thu, 23 Nov 2006 15:20:03 -0500
Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com
	[47.103.123.73])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	kANKJx118287; Thu, 23 Nov 2006 15:19:59 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] New revision for rfc3344bis;
	UDP inconsistency and candidate solution
Date: Thu, 23 Nov 2006 14:19:57 -0600
Message-ID: <6FC4416DDE56C44DA0AEE67BC7CA437111994ADC@zrc2hxm2.corp.nortel.com>
In-Reply-To: <4565317D.7010506@nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] New revision for rfc3344bis;
	UDP inconsistency and candidate solution
Thread-Index: AccOwMSAMOwz/ldASJi6fgMLs+57nwAezMSQ
From: "Ahmad Muhanna" <amuhanna@nortel.com>
To: "Charles E. Perkins" <charles.perkins@nokia.com>, <sami.vaarala@iki.fi>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi Charlie,

Never mind, after reading this one more time, I do not see any problem
with the proposed changes.  I actually was thinking of the source UDP
port of the RRQ as sent by the FA.=20

Regards,
Ahmad
=20

> -----Original Message-----
> From: Charles E. Perkins [mailto:charles.perkins@nokia.com]=20
> Sent: Wednesday, November 22, 2006 11:28 PM
> To: Muhanna, Ahmad (RICH1:2H10); sami.vaarala@iki.fi
> Cc: Mobile IPv4 Mailing List
> Subject: Re: [Mip4] New revision for rfc3344bis; UDP=20
> inconsistency and candidate solution
>=20
>=20
> Hello Ahmad and Sami,
>=20
> As far as I know, the proposed wording change is backward compatible.
>=20
> Regarding port forwarding NATs, I hope there are none that=20
> change the destination port!  The home agent can't be=20
> listening to all the possible destination ports and treating=20
> all incoming messages to all ports as Mobile IP messages.
>=20
> I can see that a NAT box might change the source port number,=20
> and the wording changes I proposed would not affect that.
>=20
> Isn't this right?
>=20
> Regards,
> Charlie P.
>=20
>=20
> ext Ahmad Muhanna wrote:
> > Since this has been out there with no reported issues and=20
> problems for=20
> > a long time, I believe if we need to make any changes, we need to=20
> > allow the current wording for backward compatibility.
> >
> > Regards,
> > Ahmad
> > =20
> >
> >  =20
> >> -----Original Message-----
> >> From: Henrik Levkowetz [mailto:henrik@levkowetz.com]
> >> Sent: Wednesday, November 22, 2006 3:09 AM
> >> To: Sami Vaarala
> >> Cc: Charles E. Perkins; Mobile IPv4 Mailing List
> >> Subject: Re: [Mip4] New revision for rfc3344bis; UDP inconsistency=20
> >> and candidate solution
> >>
> >> Hi,
> >>
> >> on 2006-11-22 09:27 Sami Vaarala said the following:
> >>    =20
> >>> Charles E. Perkins wrote:
> >>>      =20
> >>>> Hello folks,
> >>>>        =20
> >>>  > [...]
> >>>      =20
> >>>> As pointed out, copying the value of the destination=20
> port into the=20
> >>>> source port should be identically the same as setting the
> >>>>        =20
> >> source port
> >>    =20
> >>>> value to 434.  So, the value of the field cannot be described as=20
> >>>> "variable" as things now stand.
> >>>>        =20
> >>> Hi,
> >>>
> >>> I haven't been following this discussion closely, but=20
> there may be=20
> >>> cases with NATs and port forwarding where this assumption is=20
> >>> incorrect.  For instance, if the HA is behind a port forwarding=20
> >>> device, the MN may be sending to port 434 but HA=20
> receiving at some=20
> >>> other port.
> >>>      =20
> >> I agree with Sami.  Removing the 'variable'=20
> characterisation is fine,=20
> >> but I'd still prefer to retain the current language which=20
> specifies=20
> >> copying the incoming destination port value into the=20
> outgoing source=20
> >> port value.
> >>
> >>
> >> 	Henrik
> >>
> >>
> >>    =20
>=20
>=20
> --
> Please address return e-mail to charles.perkins@nokia.com
>=20
>=20

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Sun Nov 26 15:06:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GoQGg-0000i1-Nc; Sun, 26 Nov 2006 15:06:26 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GoQGf-0000ct-87
	for mip4@ietf.org; Sun, 26 Nov 2006 15:06:25 -0500
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GoQGd-0003cE-Nr
	for mip4@ietf.org; Sun, 26 Nov 2006 15:06:25 -0500
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id CB46989880;
	Sun, 26 Nov 2006 22:06:11 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 6E05589879;
	Sun, 26 Nov 2006 22:06:11 +0200 (EET)
Message-ID: <4569F3B3.5020905@piuha.net>
Date: Sun, 26 Nov 2006 22:06:11 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.8 (X11/20061117)
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
References: <45647C27.4040208@levkowetz.com>
In-Reply-To: <45647C27.4040208@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: mip4-chairs@tools.ietf.org, mip4-ads@tools.ietf.org,
	Mobile IPv4 Mailing List <mip4@ietf.org>
Subject: [Mip4] Re: Charter Update Proposal
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

This looks reasonable. I'm taking this for processing.

--Jari

Henrik Levkowetz kirjoitti:
> Hi,
>
>
> Both the list and the WG meeting during IETF-67 indicated support for
> adding moving network support and a notification mechanism to the
> charter, so below is a proposal for a charter update.  (The resulting
> charter, if the updates are accepted, are provided as an attachment.)
>
> We propose to add the following two items to the list of work to
> be done:
>
>   11. MIPv4 Moving Network Support
>
>   The Network Mobility (nemo) working group deals with the problem of
>   mobility of a whole network, such as might exist inside a vehicle,
>   train, or airplane.  The nemo working group has developed draft
>   specifications for both IPv6 and IPv4 mobile networks.  However, it has
>   been recognized that the IPv4 version of the protocol can be viewed as
>   an extension of the basic Mobile IPv4 protocol, and there is good reason
>   to do this extension in the mip4 working group.  The working group will
>   take on the MIPv4 network mobility internet draft and progress it along
>   the standards track.  In addition, the working group will take up
>   extensions to the basic MIPv4 moving network support in the areas of
>   dynamic prefix assignment and foreign agent support.
>
>
>   12. Asynchronous Notification Mechanism
>
>   In some situations, there is a need for Mobile IPv4 entities, such as
>   the home agent, foreign agent and mobile node to send and receive
>   asynchronous notification events during a mobility session.  The base
>   Mobile IP Specification [RFC3344] does not have a provision for this. A
>   new MIPv4 message pair which would support asynchronous notifications,
>   and a notification model describing how to use these messages has been
>   proposed.  The working group will take on the existing MIPv4
>   notification message draft as a starting point, review and update it as
>   needed, and progress it as a standards track document.  In addition, the
>   working group will also consider defining specific usages of the
>   notification message based on the examples in the current document. 
>
> We also propose to add the following milestones:
>
>    Sep 2007	Base MIPv4 Mobile Network Support (Draft Std.) to IESG
>    Nov 2007	MIPv4 Mobile Network Support for FAs (Draft Std.) to IESG
>    Nov 2007	MIPv4 Mobile Network Support Dynamic Address Assignment (Draft Std.) to IESG
>
>
> If you have comments or suggestions relating to the suggested update, please
> send them to the list.
>
>
> Best Regards,
>
> 	Henrik and Pete
>
>
>   


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Sun Nov 26 20:41:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GoVUg-0006rQ-IX; Sun, 26 Nov 2006 20:41:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GoVUg-0006r4-1A
	for mip4@ietf.org; Sun, 26 Nov 2006 20:41:14 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GoVUd-000408-Nw
	for mip4@ietf.org; Sun, 26 Nov 2006 20:41:14 -0500
Received: from [10.1.210.5] ([66.92.223.6]) by mail2.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Sun, 26 Nov 2006 17:41:10 -0800
Message-ID: <456A4232.3040308@azairenet.com>
Date: Sun, 26 Nov 2006 17:41:06 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: "Charles E. Perkins" <charles.perkins@nokia.com>
Subject: Re: [Mip4] New revision for rfc3344bis;
	UDP inconsistency and candidate solution
References: <45639838.5090507@nokia.com>
In-Reply-To: <45639838.5090507@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Nov 2006 01:41:10.0317 (UTC)
	FILETIME=[1D6B9DD0:01C711C5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Charles E. Perkins wrote:

> As pointed out, copying the value of the destination
> port into the source port should be identically the same
> as setting the source port value to 434.  So, the value
> of the field cannot be described as "variable" as things
> now stand.

I agree with Sami and Henrik. just copy the
destination port on the registration request
instead of saying port 434 explicitly.

> I propose the following text changes:
> 
> (A) In section "3.4. Registration Reply", change
> 
>  >    UDP fields:
>  >
>  >        Source Port           <variable>
> 
> to be:
> 
>    UDP fields:
> 
>        Source Port           434

    UDP fields:

        Source Port           Copied from the UDP destination port
                              of the corresponding Registration
                              Request.

> (B). In section "3.8.3.1. IP/UDP Fields", change:
> 
>  >       UDP Source Port
>  >                Copied from the UDP Destination Port of the Registration
>  >                Request.

and leave this as is.

Vijay

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Mon Nov 27 03:18:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GobhC-000104-Bn; Mon, 27 Nov 2006 03:18:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GobhB-0000zw-KB
	for mip4@ietf.org; Mon, 27 Nov 2006 03:18:33 -0500
Received: from av9-1-sn3.vrr.skanova.net ([81.228.9.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GobhA-000444-0g
	for mip4@ietf.org; Mon, 27 Nov 2006 03:18:33 -0500
Received: by av9-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 496433829F; Mon, 27 Nov 2006 09:18:31 +0100 (CET)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101]) by av9-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 2A53238294; Mon, 27 Nov 2006 09:18:31 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 0FBA537E48;
	Mon, 27 Nov 2006 09:18:30 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1Gobh8-0004Qn-Kc; Mon, 27 Nov 2006 09:18:30 +0100
Message-ID: <456A9F54.8020704@levkowetz.com>
Date: Mon, 27 Nov 2006 09:18:28 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: "Charles E.Perkins" <charliep@iprg.nokia.com>
Subject: Re: [Mip4] rfc3344bis.txt
References: <40F30D4B.766B64EA@iprg.nokia.com>
In-Reply-To: <40F30D4B.766B64EA@iprg.nokia.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1041891061=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1041891061==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigC20006A0C201D40ABB8B1E6F"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigC20006A0C201D40ABB8B1E6F
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Charlie,

on 2004-07-13 00:14 Charles E.Perkins said the following:
> Hello folks,
>=20
> I have submitted an Internet Draft containing a revised
> version of RFC 3344 to the Internet Drafts control subsystem.
> Whether it will succeed, still remains to be seen.  There
> are new requirements placed on Internet Drafts, and I didn't
> have a perfect template from which to steal text.

Many recent drafts are just fine.  Here's one example:

http://tools.ietf.org/html/draft-ietf-mip4-mobike-connectivity-01

The appropriate boilerplate was published in RFC 3978, in March 2005;
it's hardly new any more: http://tools.ietf.org/html/rfc3978

There will however be a small adjustment needed soon, based on
RFC 4748, http://tools.ietf.org/html/rfc4748, which changes the
copyright notices to specify the IETF Trust.  You may want to make
that change at once.

Finally, there's a tool ('idnits') which you can use to get feedback
on things that might need fixing up before submitting a draft for
publication (and we're getting close to that now, I think ;) :

http://tools.ietf.org/tools/idnits/

Looking at the output from idnits, there seems to be some stuff that
could need fixing.  The short form output is given below; if you
run the tool with the verbose option, you'll get the exact
boilerplate needed as part of the output, ready for cut and paste:

----------------------------------------------------------------------

idnits 1.118=20

tmp/rfc3344bis.txt:


  Checking nits according to http://www.ietf.org/ID-Checklist.html:
  * The document seems to lack an Authors' Addresses Section.
  * The document seems to lack separate sections for Informative/Normativ=
e
    References.
   =20
    Checking conformance with RFC 3978/3979 boilerplate...

  * Found RFC 3979 Section 5 paragraph 1 boilerplate (on line 4581), whic=
h is
    fine, but *also* found RFC 2026 Section 10.4A boilerplate on line 382=
2. It
    should be removed.
  * Found RFC 3979 Section 5 paragraph 3 boilerplate (on line 4594), whic=
h is
    fine, but *also* found RFC 2026 Section 10.4B boilerplate on line 382=
8. It
    should be removed.

  Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt:=

  - Mismatching filename: the document gives the document name as
    'draft-ietf-mip4-rfc3344bis-03', but the file name used is 'rfc3344bi=
s'

  Miscellaneous warnings:
  - * In addition to RFC 3979 Section 5 paragraph 1 boilerplate, a sectio=
n
    with a similar start was also found:

    "The IETF takes no position regarding the validity or scope of any
    intellectual property or other rights that might be claimed to
    pertain to the implementation or use of the technology described in
    this document or the extent to which any license under such rights
    might or might not be available; neither does it represent that it
    has made any effort to identify any such rights.  Information on the
    IETF's procedures with respect to rights in standards-track and
    standards-related documentation can be found in BCP-11.  Copies of
    claims of rights made available for publication and any assurances of=

    licenses to be made available, or the result of an attempt made to
    obtain a general license or permission for the use of such
    proprietary rights by implementors or users of this specification can=

    be obtained from the IETF Secretariat.")

  - * In addition to RFC 3979 Section 5 paragraph 3 boilerplate, a sectio=
n
    with a similar start was also found:

    "The IETF invites any interested party to bring to its attention any
    copyrights, patents or patent applications, or other proprietary
    rights which may cover technology that may be required to practice
    this standard.  Please address the information to the IETF Executive
    Director.")

  - The copyright year in the RFC 3978 Section 5.4 Copyright Line does no=
t
    match the current year
  - Line 743 has weird spacing: '... Length   indi...'
  - Line 4372 has weird spacing: '...ensions  used ...'

  Experimental warnings:
  - Looks like a reference, but probably isn't: 'M' on line 3676 (?)
  - Unused Reference: '4' is defined on line 4390, but not referenced
  - Unused Reference: '7' is defined on line 4403, but not referenced
  - Unused Reference: '23' is defined on line 4468, but not referenced
  - Unused Reference: '25' is defined on line 4476, but not referenced
  - Unused Reference: '26' is defined on line 4480, but not referenced
  - Unused Reference: '29' is defined on line 4492, but not referenced
  - Unused Reference: '31' is defined on line 4502, but not referenced
  - Unused Reference: '35' is defined on line 4520, but not referenced
  - Unused Reference: '36' is defined on line 4525, but not referenced
  - Unused Reference: '37' is defined on line 4530, but not referenced
  - Unused Reference: '41' is defined on line 4546, but not referenced
  - Unused Reference: '42' is defined on line 4550, but not referenced

    Run idnits with the --verbose option for more detailed information.

----------------------------------------------------------------------


	Henrik


--------------enigC20006A0C201D40ABB8B1E6F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFap9UeVhrtTJkXCMRAvqeAJ0dMz4G9bF+xgEdIgivSv5wN+NHFgCeIjjF
Oe5vb4ZVYiQQZN62IXwFAuY=
=SUKe
-----END PGP SIGNATURE-----

--------------enigC20006A0C201D40ABB8B1E6F--


--===============1041891061==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1041891061==--




From mip4-bounces@ietf.org Mon Nov 27 19:28:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Goqq7-0002vU-Mx; Mon, 27 Nov 2006 19:28:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Goqq7-0002vP-3x
	for mip4@ietf.org; Mon, 27 Nov 2006 19:28:47 -0500
Received: from av9-1-sn3.vrr.skanova.net ([81.228.9.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Goqq5-0000A4-Gh
	for mip4@ietf.org; Mon, 27 Nov 2006 19:28:47 -0500
Received: by av9-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id E56CD38050; Tue, 28 Nov 2006 01:28:44 +0100 (CET)
Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net
	[81.228.9.102]) by av9-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id C777537E52; Tue, 28 Nov 2006 01:28:44 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 9025037E4D;
	Tue, 28 Nov 2006 01:28:44 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1Goqpx-00005v-Fv; Tue, 28 Nov 2006 01:28:37 +0100
Message-ID: <456B82B2.6040902@levkowetz.com>
Date: Tue, 28 Nov 2006 01:28:34 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: [Mip4] rfc3344bis.txt
References: <40F30D4B.766B64EA@iprg.nokia.com> <456A9F54.8020704@levkowetz.com>
In-Reply-To: <456A9F54.8020704@levkowetz.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 995b2e24d23b953c94bac5288c432399
Cc: "Charles E. Perkins" <charles.perkins@nokia.com>,
	Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0775126592=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0775126592==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigDA0716DF82341AE5C1DD1157"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigDA0716DF82341AE5C1DD1157
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


Oh, dear, oh, dear.

My email client or server is playing tricks on me -- the mail that
I responded to (below) popped up, fresh, unread and unanswered
yesterday, and I didn't notice that it was severely outdated!!

I don't know how this has happened, but it occurs to me that it
has happened to me certainly once, and maybe twice before over the
last 2 years -- and maybe ??  even once with this precise same
message from Charlie ???

Anyway, my excuses for burdening you with outdated traffic!


Regards,

	Henrik




on 2006-11-27 09:18 Henrik Levkowetz said the following:
> Hi Charlie,
>=20
> on 2004-07-13 00:14 Charles E.Perkins said the following:
>> Hello folks,
>>=20
>> I have submitted an Internet Draft containing a revised
>> version of RFC 3344 to the Internet Drafts control subsystem.
>> Whether it will succeed, still remains to be seen.  There
>> are new requirements placed on Internet Drafts, and I didn't
>> have a perfect template from which to steal text.
>=20
> Many recent drafts are just fine.  Here's one example:
>=20
> http://tools.ietf.org/html/draft-ietf-mip4-mobike-connectivity-01
>=20
> The appropriate boilerplate was published in RFC 3978, in March 2005;
> it's hardly new any more: http://tools.ietf.org/html/rfc3978
>=20
> There will however be a small adjustment needed soon, based on
> RFC 4748, http://tools.ietf.org/html/rfc4748, which changes the
> copyright notices to specify the IETF Trust.  You may want to make
> that change at once.
>=20
> Finally, there's a tool ('idnits') which you can use to get feedback
> on things that might need fixing up before submitting a draft for
> publication (and we're getting close to that now, I think ;) :
>=20
> http://tools.ietf.org/tools/idnits/
>=20
> Looking at the output from idnits, there seems to be some stuff that
> could need fixing.  The short form output is given below; if you
> run the tool with the verbose option, you'll get the exact
> boilerplate needed as part of the output, ready for cut and paste:
>=20
> ----------------------------------------------------------------------
>=20
> idnits 1.118=20
>=20
> tmp/rfc3344bis.txt:
>=20
>=20
>   Checking nits according to http://www.ietf.org/ID-Checklist.html:
>   * The document seems to lack an Authors' Addresses Section.
>   * The document seems to lack separate sections for Informative/Normat=
ive
>     References.
>    =20
>     Checking conformance with RFC 3978/3979 boilerplate...
>=20
>   * Found RFC 3979 Section 5 paragraph 1 boilerplate (on line 4581), wh=
ich is
>     fine, but *also* found RFC 2026 Section 10.4A boilerplate on line 3=
822. It
>     should be removed.
>   * Found RFC 3979 Section 5 paragraph 3 boilerplate (on line 4594), wh=
ich is
>     fine, but *also* found RFC 2026 Section 10.4B boilerplate on line 3=
828. It
>     should be removed.
>=20
>   Checking nits according to http://www.ietf.org/ietf/1id-guidelines.tx=
t:
>   - Mismatching filename: the document gives the document name as
>     'draft-ietf-mip4-rfc3344bis-03', but the file name used is 'rfc3344=
bis'
>=20
>   Miscellaneous warnings:
>   - * In addition to RFC 3979 Section 5 paragraph 1 boilerplate, a sect=
ion
>     with a similar start was also found:
>=20
>     "The IETF takes no position regarding the validity or scope of any
>     intellectual property or other rights that might be claimed to
>     pertain to the implementation or use of the technology described in=

>     this document or the extent to which any license under such rights
>     might or might not be available; neither does it represent that it
>     has made any effort to identify any such rights.  Information on th=
e
>     IETF's procedures with respect to rights in standards-track and
>     standards-related documentation can be found in BCP-11.  Copies of
>     claims of rights made available for publication and any assurances =
of
>     licenses to be made available, or the result of an attempt made to
>     obtain a general license or permission for the use of such
>     proprietary rights by implementors or users of this specification c=
an
>     be obtained from the IETF Secretariat.")
>=20
>   - * In addition to RFC 3979 Section 5 paragraph 3 boilerplate, a sect=
ion
>     with a similar start was also found:
>=20
>     "The IETF invites any interested party to bring to its attention an=
y
>     copyrights, patents or patent applications, or other proprietary
>     rights which may cover technology that may be required to practice
>     this standard.  Please address the information to the IETF Executiv=
e
>     Director.")
>=20
>   - The copyright year in the RFC 3978 Section 5.4 Copyright Line does =
not
>     match the current year
>   - Line 743 has weird spacing: '... Length   indi...'
>   - Line 4372 has weird spacing: '...ensions  used ...'
>=20
>   Experimental warnings:
>   - Looks like a reference, but probably isn't: 'M' on line 3676 (?)
>   - Unused Reference: '4' is defined on line 4390, but not referenced
>   - Unused Reference: '7' is defined on line 4403, but not referenced
>   - Unused Reference: '23' is defined on line 4468, but not referenced
>   - Unused Reference: '25' is defined on line 4476, but not referenced
>   - Unused Reference: '26' is defined on line 4480, but not referenced
>   - Unused Reference: '29' is defined on line 4492, but not referenced
>   - Unused Reference: '31' is defined on line 4502, but not referenced
>   - Unused Reference: '35' is defined on line 4520, but not referenced
>   - Unused Reference: '36' is defined on line 4525, but not referenced
>   - Unused Reference: '37' is defined on line 4530, but not referenced
>   - Unused Reference: '41' is defined on line 4546, but not referenced
>   - Unused Reference: '42' is defined on line 4550, but not referenced
>=20
>     Run idnits with the --verbose option for more detailed information.=

>=20
> ----------------------------------------------------------------------
>=20
>=20
> 	Henrik
>=20
>=20


--------------enigDA0716DF82341AE5C1DD1157
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFa4KyeVhrtTJkXCMRAjvgAKD8yugE2Gdk4v7jkJ099svUj1KieQCgy3Eh
R/i9wl2V1CwqiPmOeqJjnkQ=
=axhr
-----END PGP SIGNATURE-----

--------------enigDA0716DF82341AE5C1DD1157--


--===============0775126592==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0775126592==--




From mip4-bounces@ietf.org Tue Nov 28 11:37:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gp5x8-0004Ys-Hl; Tue, 28 Nov 2006 11:37:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gp5x7-0004YV-Ca
	for mip4@ietf.org; Tue, 28 Nov 2006 11:37:01 -0500
Received: from mail128.messagelabs.com ([216.82.250.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gp5x4-0007JO-1r
	for mip4@ietf.org; Tue, 28 Nov 2006 11:37:01 -0500
X-VirusChecked: Checked
X-Env-Sender: pete.mccann@motorola.com
X-Msg-Ref: server-9.tower-128.messagelabs.com!1164731388!3172129!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 4254 invoked from network); 28 Nov 2006 16:29:48 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-9.tower-128.messagelabs.com with SMTP;
	28 Nov 2006 16:29:48 -0000
Received: from il06exb01.corp.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id kASGTmRJ022538
	for <mip4@ietf.org>; Tue, 28 Nov 2006 09:29:48 -0700 (MST)
Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18])
	by il06exb01.corp.mot.com (8.13.1/8.13.0) with ESMTP id kASGTmVw000068
	for <mip4@ietf.org>; Tue, 28 Nov 2006 10:29:48 -0600 (CST)
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, 28 Nov 2006 11:29:47 -0500
Message-ID: <BE4B07D4197BF34EB3B753DD34EBCD130125E6C2@de01exm67.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WGLC: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: AccTCmsX+3AuBSnxSX+BjwQKcbmG8Q==
From: "McCann Peter-A001034" <pete.mccann@motorola.com>
To: <mip4@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: [Mip4] WGLC: draft-ietf-mip4-mobike-connectivity-01.txt
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

This message announces a (second) WG last call on:

   "Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
   draft-ietf-mip4-mobike-connectivity-01.txt

The last call will conclude at 24:00 UTC on Tuesday, 12 December 2006.

"Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
describes=20
a solution using Mobile IPv4 and mobility extensions to IKEv2 (MOBIKE)
to=20
provide secure connectivity and mobility.

A URL for this internet draft is:

http://www.ietf.org/internet-drafts/draft-ietf-mip4-mobike-connectivity-
01.txt


Please respond to this WG last call:


* If you have no comments on the draft, and support its advancement,
  simply respond with a line containing something like


   "I support the advancement of this document to the IESG with a
    request for publication as proposed standard."


  If you have comments, please use a line similar to the one above, and
  supplement this with your comments.



* If you *don't* support its advancement, respond with a line containing
  something like the following, supplemented by your comments -


   "I don't support the advancement of this document to the IESG with
    a request for publication as proposed standard, for the following
    reasons:"
   ...




    Pete & Henrik

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Nov 28 15:15:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gp9MO-0002Xy-Cd; Tue, 28 Nov 2006 15:15:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gp9MM-0002Xp-IL
	for mip4@ietf.org; Tue, 28 Nov 2006 15:15:18 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gp9MJ-0007Ie-U5
	for mip4@ietf.org; Tue, 28 Nov 2006 15:15:18 -0500
Received: from sj-dkim-8.cisco.com ([171.68.10.93])
	by sj-iport-3.cisco.com with ESMTP; 28 Nov 2006 12:15:15 -0800
X-IronPort-AV: i="4.09,471,1157353200"; 
	d="scan'208,217"; a="449905129:sNHT107760014"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-8.cisco.com (8.12.11/8.12.11) with ESMTP id kASKFFEQ020649; 
	Tue, 28 Nov 2006 12:15:15 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id kASKEMP9013793;
	Tue, 28 Nov 2006 12:15:15 -0800 (PST)
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Nov 2006 12:15:07 -0800
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter
Date: Tue, 28 Nov 2006 12:15:06 -0800
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5202EDC26D@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Proxy Mobile IPv4 in the WG charter
Thread-Index: AccKcRALK3JjuYGhShOIr9RtW9WMJACQ5ElwAZ0yUbA=
From: "Kent Leung \(kleung\)" <kleung@cisco.com>
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>, <mip4@ietf.org>
X-OriginalArrivalTime: 28 Nov 2006 20:15:07.0878 (UTC)
	FILETIME=[E61FD060:01C71329]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=9936; t=1164744915;
	x=1165608915; c=relaxed/relaxed; s=sjdkim8002;
	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<kleung@cisco.com>
	|Subject:=20RE=3A=20[Mip4]=20Proxy=20Mobile=20IPv4=20in=20the=20WG=20char
	ter |Sender:=20;
	bh=wrVHmNotsPFtyQYNbzAle4roO2rZkzF8gDTgEVQ7wxw=;
	b=E5dMbw8/nxRQeS4d43n9CZK34SYc1fnCZ/rDTNjXKkpXbiFPfFQsDfcg9SWqpDgBmBlJlzm/
	32fUhT3D0VRkeNWKx+F70j1PqFU81+PQIxyNDGFBBs0XDEmyyNRNpYOL;
Authentication-Results: sj-dkim-8; header.From=kleung@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim8002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bfe538a859d88717fa3c8a6377d62f90
Cc: 
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0114157934=="
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0114157934==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C71329.E5FFE65D"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C71329.E5FFE65D
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi George.  Sorry for the delay.
=20
Good point about differentiating between standardizing a proxy MIPv4
protocol vs. existing proxy MIPv4 use case.  My proposal is to come up
with the former, defining simple and short spec on Proxy Mobile IPv4.
=20
Thanks for the clarification.
=20
Kent

________________________________

From: Tsirtsis, George [mailto:tsirtsis@qualcomm.com]=20
Sent: Monday, November 20, 2006 7:13 AM
To: Kent Leung (kleung); mip4@ietf.org
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter



Hi Kent,

=20

I think it makes sense for the PMIPv4 protocol to be standardized by
this group. I also think we should separate the way the protocol is used
in the field from what the generic protocol is that might be applicable
in various different systems. I think your draft is mixing the two
issues together.=20

=20

IMO we should have a very simple and hopefully sort specification
defining the changes (if any) to MIPv4 required so that the protocol can
run in proxy mode. In addition, if it is deemed necessary/useful, we can
have informational document(s) showing how PMIPv4 is used in various
systems.=20

=20

I have some specific comments on the protocol itself but we can talk
about that if/when this becomes a WG document.

=20

Thanks

George=20

=20

________________________________

From: Kent Leung (kleung) [mailto:kleung@cisco.com]=20
Sent: Friday, November 17, 2006 12:52 PM
To: mip4@ietf.org
Subject: [Mip4] Proxy Mobile IPv4 in the WG charter

=20

Hi.  The draft-leung-mip4-proxy-mode-01.txt draft describes using Mobile
IPv4 in proxy mode to provide network-based mobility management.  There
will need to be some more work on the draft.  But wanted to get some
sense of support for Proxy Mobile IPv4 in this WG.  Certainly there are
a few SDOs which have either adopted or interested in such mechanism.

=20

Do folks want to take this on as a WG item eventually?

=20

Kent


------_=_NextPart_001_01C71329.E5FFE65D
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2995" name=3DGENERATOR>
<STYLE>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D409401120-28112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi George.&nbsp; Sorry for the =
delay.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D409401120-28112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D409401120-28112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Good point about differentiating between =
standardizing a=20
proxy MIPv4 protocol vs. existing proxy MIPv4 use case.&nbsp; My =
proposal is to=20
come up with the former, defining simple and short spec on Proxy Mobile=20
IPv4.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D409401120-28112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D409401120-28112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Thanks for the =
clarification.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D409401120-28112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D409401120-28112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Kent</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Tsirtsis, George=20
[mailto:tsirtsis@qualcomm.com] <BR><B>Sent:</B> Monday, November 20, =
2006 7:13=20
AM<BR><B>To:</B> Kent Leung (kleung); mip4@ietf.org<BR><B>Subject:</B> =
RE:=20
[Mip4] Proxy Mobile IPv4 in the WG charter<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Hi=20
Kent,</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I think it =
makes sense=20
for the PMIPv4 protocol to be standardized by this group. I also think =
we should=20
separate the way the protocol is used in the field from what the generic =

protocol is that might be applicable in various different systems. I =
think your=20
draft is mixing the two issues together. </SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">IMO we should =
have a=20
very simple and hopefully sort specification defining the changes (if =
any) to=20
MIPv4 required so that the protocol can run in proxy mode. In addition, =
if it is=20
deemed necessary/useful, we can have informational document(s) showing =
how=20
PMIPv4 is used in various systems. </SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I have some =
specific=20
comments on the protocol itself but we can talk about that if/when this =
becomes=20
a WG document.</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Thanks</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">George=20
</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
<DIV=20
style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =

face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"> Kent=20
Leung (kleung) [mailto:kleung@cisco.com] <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Friday, November 17, 2006 =
12:52=20
PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
mip4@ietf.org<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B> [Mip4]=20
Proxy Mobile IPv4 in the WG charter</SPAN></FONT></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi.&nbsp; The =
</SPAN></FONT><FONT=20
size=3D2><SPAN style=3D"FONT-SIZE: =
10pt">draft-leung-mip4-proxy-mode-01.txt draft=20
describes using Mobile IPv4 in proxy mode to provide network-based =
mobility=20
management.&nbsp; There will need to be some more work on the =
draft.&nbsp; But=20
wanted to get some sense of support for Proxy Mobile IPv4 in this =
WG.&nbsp;=20
Certainly there are a few SDOs which have either adopted or interested =
in such=20
mechanism.</SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt">Do folks want to take this on as a WG item=20
eventually?</SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D2><SPAN=20
style=3D"FONT-SIZE: =
10pt">Kent</SPAN></FONT></P></DIV></DIV></DIV></BODY></HTML>

------_=_NextPart_001_01C71329.E5FFE65D--


--===============0114157934==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0114157934==--




From mip4-bounces@ietf.org Tue Nov 28 15:17:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gp9Oq-0006E7-Ci; Tue, 28 Nov 2006 15:17:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gp9Op-0006BU-2c
	for mip4@ietf.org; Tue, 28 Nov 2006 15:17:51 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gp9On-0007fA-97
	for mip4@ietf.org; Tue, 28 Nov 2006 15:17:51 -0500
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-5.cisco.com with ESMTP; 28 Nov 2006 12:17:48 -0800
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id kASKHm8j019541; 
	Tue, 28 Nov 2006 12:17:48 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id kASKHmW4018690;
	Tue, 28 Nov 2006 12:17:48 -0800 (PST)
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Nov 2006 12:17:48 -0800
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter
Date: Tue, 28 Nov 2006 12:17:47 -0800
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5202EDC271@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Proxy Mobile IPv4 in the WG charter
Thread-Index: AccMueLDDqeqUqvfQLqul7tm2ICEpAAAQ07QAZvCx8A=
From: "Kent Leung \(kleung\)" <kleung@cisco.com>
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Behcet Sarikaya" <sarikaya@ieee.org>
X-OriginalArrivalTime: 28 Nov 2006 20:17:48.0218 (UTC)
	FILETIME=[45B1C1A0:01C7132A]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=15127; t=1164745068;
	x=1165609068; c=relaxed/simple; s=sjdkim1002;
	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<kleung@cisco.com>
	|Subject:=20RE=3A=20[Mip4]=20Proxy=20Mobile=20IPv4=20in=20the=20WG=20char
	ter |Sender:=20;
	bh=JlDNpFQPNNn4Laria6xyzNMjrTKjB/ftnrTMNxdjGD0=;
	b=ohgIIbHaZ21lTk23Pn2w0S8Ft7fWDjsOUu74q9l4cgHOyroeSMODgZxAbS/NympUwAjVHTGF
	nQriQEsB+CGZXkaeRmZkSuUBW9UT6Jlrat6JFRv4vJz6KyrCOQ8uxYIj;
Authentication-Results: sj-dkim-1; header.From=kleung@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd3d702b63698072ba67a75ce9e0fc9e
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1790746522=="
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1790746522==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7132A.45926A19"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7132A.45926A19
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

There is no NETLMM4 WG.  Mobile IPv4 is becoming more prevalent.  I
expect more work items being fed back from real world deployments.
=20
Kent

________________________________

From: Tsirtsis, George [mailto:tsirtsis@qualcomm.com]=20
Sent: Monday, November 20, 2006 7:48 AM
To: Behcet Sarikaya
Cc: mip4@ietf.org
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter



In the last IETF meeting there was agreement (to be confirmed on the
list) for a number of new items to be added to the MIP4 charter and a
few more things were left out because the WG has too many things to do.
I do not think MIP4 is going anywhere for a while longer....=20

=20

________________________________

From: Behcet Sarikaya [mailto:behcetsarikaya@yahoo.com]=20
Sent: Monday, November 20, 2006 10:31 AM
To: Tsirtsis, George
Cc: mip4@ietf.org
Subject: Re: [Mip4] Proxy Mobile IPv4 in the WG charter

=20

Is there a netlmm4 WG? IMHO pmip4 could be standardized there if any?
WGs can shut down if no new work left, and that is usually good
practice, there is nothing wrong in doing such a thing.

  No offense to any one.

=20

Regards,

=20

--behcet

=20

----- Original Message ----
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: Kent Leung (kleung) <kleung@cisco.com>; mip4@ietf.org
Sent: Monday, November 20, 2006 9:13:03 AM
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter

Hi Kent,

=20

I think it makes sense for the PMIPv4 protocol to be standardized by
this group. I also think we should separate the way the protocol is used
in the field from what the generic protocol is that might be applicable
in various different systems. I think your draft is mixing the two
issues together.=20

=20

IMO we should have a very simple and hopefully sort specification
defining the changes (if any) to MIPv4 required so that the protocol can
run in proxy mode. In addition, if it is deemed necessary/useful, we can
have informational document(s) showing how PMIPv4 is used in various
systems.=20

=20

I have some specific comments on the protocol itself but we can talk
about that if/when this becomes a WG document.

=20

Thanks

George=20

=20

________________________________

From: Kent Leung (kleung) [mailto:kleung@cisco.com]=20
Sent: Friday, November 17, 2006 12:52 PM
To: mip4@ietf.org
Subject: [Mip4] Proxy Mobile IPv4 in the WG charter

=20

Hi.  The draft-leung-mip4-proxy-mode-01.txt draft describes using Mobile
IPv4 in proxy mode to provide network-based mobility management.  There
will need to be some more work on the draft.  But wanted to get some
sense of support for Proxy Mobile IPv4 in this WG.  Certainly there are
a few SDOs which have either adopted or interested in such mechanism.

=20

Do folks want to take this on as a WG item eventually?

=20

Kent

--=20
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

=20


------_=_NextPart_001_01C7132A.45926A19
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2995" name=3DGENERATOR>
<STYLE>
<!--
_filtered {font-family:SimSun;=0A=
panose-1:2 1 6 0 3 1 1 1 1 1;}
_filtered {font-family:Tahoma;=0A=
panose-1:2 11 6 4 3 5 4 4 2 4;}
_filtered {=0A=
panose-1:0 0 0 0 0 0 0 0 0 0;}
_filtered {=0A=
margin:1.0in 1.25in 1.0in 1.25in;}

 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{margin-right:0in;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.emailstyle17
	{font-family:Arial;
	color:navy;}
span.EmailStyle19
	{font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D070431520-28112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>There is no NETLMM4 WG.&nbsp; Mobile IPv4 is =
becoming more=20
prevalent.&nbsp; I expect more work items being fed back from real world =

deployments.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D070431520-28112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D070431520-28112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Kent</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Tsirtsis, George=20
[mailto:tsirtsis@qualcomm.com] <BR><B>Sent:</B> Monday, November 20, =
2006 7:48=20
AM<BR><B>To:</B> Behcet Sarikaya<BR><B>Cc:</B> =
mip4@ietf.org<BR><B>Subject:</B>=20
RE: [Mip4] Proxy Mobile IPv4 in the WG charter<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">In the last =
IETF=20
meeting there was agreement (to be confirmed on the list) for a number =
of new=20
items to be added to the MIP4 charter and a few more things were left =
out=20
because the WG has too many things to do. I do not think MIP4 is going =
anywhere=20
for a while longer&#8230;. </SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
<DIV=20
style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =

face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"> Behcet=20
Sarikaya [mailto:behcetsarikaya@yahoo.com] <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, November 20, 2006 =
10:31=20
AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Tsirtsis,=20
George<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B>=20
mip4@ietf.org<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B> Re:=20
[Mip4] Proxy Mobile IPv4 in the WG charter</SPAN></FONT></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
<DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3D#0060bf =
size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; COLOR: #0060bf">Is there a netlmm4 WG? IMHO =
pmip4 could=20
be standardized there if any? WGs can shut down if no new work left, and =
that is=20
usually good practice, there is nothing wrong in doing such a=20
thing.</SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3D#0060bf =
size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; COLOR: #0060bf">&nbsp; No offense to any=20
one.</SPAN></FONT></P></DIV>
<P><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
<P><FONT face=3D"Times New Roman" color=3D#0060bf size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; COLOR: #0060bf">Regards,</SPAN></FONT></P>
<P><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
<P><FONT face=3D"Times New Roman" color=3D#0060bf size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; COLOR: #0060bf">--behcet</SPAN></FONT></P>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT face=3D"Times =
New Roman"=20
size=3D3><SPAN style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV>
<DIV>
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT face=3D"Times =
New Roman"=20
size=3D3><SPAN style=3D"FONT-SIZE: 12pt">----- Original Message =
----<BR>From:=20
"Tsirtsis, George" &lt;tsirtsis@qualcomm.com&gt;<BR>To: Kent Leung =
(kleung)=20
&lt;kleung@cisco.com&gt;; mip4@ietf.org<BR>Sent: Monday, November 20, =
2006=20
9:13:03 AM<BR>Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG=20
charter</SPAN></FONT></P>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Hi=20
Kent,</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I think it =
makes sense=20
for the PMIPv4 protocol to be standardized by this group. I also think =
we should=20
separate the way the protocol is used in the field from what the generic =

protocol is that might be applicable in various different systems. I =
think your=20
draft is mixing the two issues together. </SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">IMO we should =
have a=20
very simple and hopefully sort specification defining the changes (if =
any) to=20
MIPv4 required so that the protocol can run in proxy mode. In addition, =
if it is=20
deemed necessary/useful, we can have informational document(s) showing =
how=20
PMIPv4 is used in various systems. </SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I have some =
specific=20
comments on the protocol itself but we can talk about that if/when this =
becomes=20
a WG document.</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Thanks</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">George=20
</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"></SPAN></FONT>&nbsp;</P>
<DIV=20
style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =

face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"> Kent=20
Leung (kleung) [mailto:kleung@cisco.com] <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Friday, November 17, 2006 =
12:52=20
PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
mip4@ietf.org<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B> [Mip4]=20
Proxy Mobile IPv4 in the WG charter</SPAN></FONT></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi.&nbsp; The =
</SPAN></FONT><FONT=20
size=3D2><SPAN style=3D"FONT-SIZE: =
10pt">draft-leung-mip4-proxy-mode-01.txt draft=20
describes using Mobile IPv4 in proxy mode to provide network-based =
mobility=20
management.&nbsp; There will need to be some more work on the =
draft.&nbsp; But=20
wanted to get some sense of support for Proxy Mobile IPv4 in this =
WG.&nbsp;=20
Certainly there are a few SDOs which have either adopted or interested =
in such=20
mechanism.</SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt">Do folks want to take this on as a WG item=20
eventually?</SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt">Kent</SPAN></FONT></P></DIV></DIV></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">-- <BR>Mip4 mailing list:=20
Mip4@ietf.org<BR>&nbsp;&nbsp;&nbsp;&nbsp;Web interface: <A=20
href=3D"https://www1.ietf.org/mailman/listinfo/mip4"=20
target=3D_blank>https://www1.ietf.org/mailman/listinfo/mip4</A><BR>&nbsp;=
&nbsp;&nbsp;&nbsp;=20
Charter page: <A =
href=3D"http://www.ietf.org/html.charters/mip4-charter.html"=20
target=3D_blank>http://www.ietf.org/html.charters/mip4-charter.html</A><B=
R>Supplemental=20
site: <A href=3D"http://www.mip4.org/"=20
target=3D_blank>http://www.mip4.org/</A></SPAN></FONT></P></DIV></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt"></SPAN></FONT>&nbsp;</P></DIV></DIV></DIV></DIV></BODY></HTML>

------_=_NextPart_001_01C7132A.45926A19--


--===============1790746522==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1790746522==--




From mip4-bounces@ietf.org Tue Nov 28 15:20:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gp9Rf-0001QK-V4; Tue, 28 Nov 2006 15:20:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gp9Re-0001PB-1U
	for mip4@ietf.org; Tue, 28 Nov 2006 15:20:46 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gp9Rc-00080t-FY
	for mip4@ietf.org; Tue, 28 Nov 2006 15:20:46 -0500
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-4.cisco.com with ESMTP; 28 Nov 2006 12:20:44 -0800
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 kASKKh37009990; 
	Tue, 28 Nov 2006 12:20:43 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id kASKKhip012057;
	Tue, 28 Nov 2006 12:20:43 -0800 (PST)
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); 
	Tue, 28 Nov 2006 12:20:43 -0800
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter
Date: Tue, 28 Nov 2006 12:20:42 -0800
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5202EDC276@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Proxy Mobile IPv4 in the WG charter
Thread-Index: AccKcRALK3JjuYGhShOIr9RtW9WMJACeekRgAY/W5aA=
From: "Kent Leung \(kleung\)" <kleung@cisco.com>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>, <mip4@ietf.org>
X-OriginalArrivalTime: 28 Nov 2006 20:20:43.0051 (UTC)
	FILETIME=[ADE727B0:01C7132A]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5301; t=1164745243;
	x=1165609243; 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<kleung@cisco.com>
	|Subject:=20RE=3A=20[Mip4]=20Proxy=20Mobile=20IPv4=20in=20the=20WG=20char
	ter |Sender:=20;
	bh=x+dPGe7clSsR1OtlDJuz74P9v6hQydI4QEfe8znWn1I=;
	b=vbnLiye8uJQg5ccep70Sh7St9ov4Q3qG8tQLh0jATLd6CPZ8fJzjvYjaE86SLr40B8uhq7Pm
	WgRiJYRX5jfy/LVpnVQjdMItfeH7HX27tRsM1x4wGcd7dbiBOXKfBuxk;
Authentication-Results: sj-dkim-3; header.From=kleung@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Cc: 
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1978208302=="
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1978208302==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7132A.ADC4AF61"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7132A.ADC4AF61
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Vidya.  We need a IPv4 signaling solution as well.  IPv4 is not going
away.  Mobile IPv4 use is growing.  We should have a good standard for
MIPv4 in proxy mode.
=20
Kent

________________________________

From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]=20
Sent: Monday, November 20, 2006 1:44 PM
To: Kent Leung (kleung); mip4@ietf.org
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter


Hi Kent,
If NETLMM supported IPv4 endpoints, do we still need a standardized
PMIPv4 solution? Or, is this an effort to document what has been already
deployed?=20
=20
Regards,
Vidya


________________________________

	From: Kent Leung (kleung) [mailto:kleung@cisco.com]=20
	Sent: Friday, November 17, 2006 9:52 AM
	To: mip4@ietf.org
	Subject: [Mip4] Proxy Mobile IPv4 in the WG charter
=09
=09
	Hi.  The draft-leung-mip4-proxy-mode-01.txt draft describes
using Mobile IPv4 in proxy mode to provide network-based mobility
management.  There will need to be some more work on the draft.  But
wanted to get some sense of support for Proxy Mobile IPv4 in this WG.
Certainly there are a few SDOs which have either adopted or interested
in such mechanism.
	=20
	Do folks want to take this on as a WG item eventually?
	=20
	Kent


------_=_NextPart_001_01C7132A.ADC4AF61
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2995" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D406131820-28112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Vidya.&nbsp; We need a IPv4 signaling =
solution as=20
well.&nbsp; IPv4 is not going away.&nbsp; Mobile IPv4 use is =
growing.&nbsp; We=20
should have a good standard for&nbsp;MIPv4 in proxy =
mode.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D406131820-28112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D406131820-28112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Kent</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Narayanan, Vidya=20
[mailto:vidyan@qualcomm.com] <BR><B>Sent:</B> Monday, November 20, 2006 =
1:44=20
PM<BR><B>To:</B> Kent Leung (kleung); mip4@ietf.org<BR><B>Subject:</B> =
RE:=20
[Mip4] Proxy Mobile IPv4 in the WG charter<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D498342921-20112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Kent,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D498342921-20112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>If NETLMM supported IPv4 endpoints, do we still =
need a=20
standardized PMIPv4 solution? Or, is this an effort to document what has =
been=20
already deployed? </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D498342921-20112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D498342921-20112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D498342921-20112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Vidya</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Kent Leung (kleung)=20
  [mailto:kleung@cisco.com] <BR><B>Sent:</B> Friday, November 17, 2006 =
9:52=20
  AM<BR><B>To:</B> mip4@ietf.org<BR><B>Subject:</B> [Mip4] Proxy Mobile =
IPv4 in=20
  the WG charter<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT face=3DArial =
size=3D2>Hi.&nbsp; The=20
  <FONT face=3D"Times New Roman">draft-leung-mip4-proxy-mode-01.txt =
draft=20
  describes using Mobile IPv4 in proxy mode to provide network-based =
mobility=20
  management.&nbsp; There will need to be some more work on the =
draft.&nbsp; But=20
  wanted to get some sense of support for Proxy Mobile IPv4 in this =
WG.&nbsp;=20
  Certainly there are a few SDOs which have either adopted or interested =
in such=20
  mechanism.</FONT></FONT></SPAN></DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT face=3DArial =
size=3D2><FONT=20
  face=3D"Times New Roman"></FONT></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT face=3DArial =
size=3D2><FONT=20
  face=3D"Times New Roman">Do folks want to take this on as a WG item=20
  eventually?</FONT></FONT></SPAN></DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D187494217-17112006><FONT=20
size=3D2>Kent</FONT></SPAN></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C7132A.ADC4AF61--


--===============1978208302==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1978208302==--




From mip4-bounces@ietf.org Tue Nov 28 15:25:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gp9WL-0005fy-Ga; Tue, 28 Nov 2006 15:25:37 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gp9WK-0005bt-7q
	for mip4@ietf.org; Tue, 28 Nov 2006 15:25:36 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gp9WH-0008WA-Tx
	for mip4@ietf.org; Tue, 28 Nov 2006 15:25:36 -0500
Received: from sj-dkim-5.cisco.com ([171.68.10.79])
	by sj-iport-3.cisco.com with ESMTP; 28 Nov 2006 12:25:33 -0800
X-IronPort-AV: i="4.09,471,1157353200"; 
	d="scan'208"; a="449906800:sNHT56047752"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id kASKPXiw009009; 
	Tue, 28 Nov 2006 12:25:33 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id kASKPROh019660;
	Tue, 28 Nov 2006 12:25:33 -0800 (PST)
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); 
	Tue, 28 Nov 2006 12:25:23 -0800
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter
Date: Tue, 28 Nov 2006 12:25:22 -0800
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5202EDC27C@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Proxy Mobile IPv4 in the WG charter
Thread-Index: AccNlcmwPtkYQawpQ8Ca8NXFWHhZPgFlRN0g
From: "Kent Leung \(kleung\)" <kleung@cisco.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>,
	"Narayanan, Vidya" <vidyan@qualcomm.com>
X-OriginalArrivalTime: 28 Nov 2006 20:25:23.0153 (UTC)
	FILETIME=[54DB5410:01C7132B]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1753; t=1164745533;
	x=1165609533; c=relaxed/simple; s=sjdkim5002;
	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<kleung@cisco.com>
	|Subject:=20RE=3A=20[Mip4]=20Proxy=20Mobile=20IPv4=20in=20the=20WG=20char
	ter |Sender:=20;
	bh=BQHIRq+XbyeNosbfv8GRto7c+WGa9lDnnXdYcJkl1+s=;
	b=lPwy+tSgxJIdNJa/1fhwRhT6/ZbdWTxhgjUdSd31y8xBYgtKx5YHALfmAttql4cp5lvYthOO
	s6EwLLzLfxV/RKMjVAABFKVNX18dF+66aIWV4oRoWTwt3tD8ryuV+uZe;
Authentication-Results: sj-dkim-5; header.From=kleung@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim5002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi Alex.  WiMAX supports both client MIPv4 and proxy MIPv4 modes.  I
prefer to keep the discussion focused on the need to standardize MIPv4
in proxy mode in IETF.  I believe it would be highly valuable
specification and has potential widespread use.

Kent=20

-----Original Message-----
From: Alexandru Petrescu [mailto:alexandru.petrescu@motorola.com]=20
Sent: Tuesday, November 21, 2006 9:51 AM
To: Narayanan, Vidya
Cc: Kent Leung (kleung); mip4@ietf.org
Subject: Re: [Mip4] Proxy Mobile IPv4 in the WG charter

Narayanan, Vidya wrote:
> Hi Kent, If NETLMM supported IPv4 endpoints, do we still need a=20
> standardized PMIPv4 solution?

Not sure what NETLMM is, or whether it supported IPv4 endpoints.

The other question is whether the known FA mode of MIP4 can figure as a
candidate for what WiMax nominates as Proxy MIP, and the CCoA mode as
what WiMax nominates Client MIP.

Alex

> Or, is this an effort to document what has been already deployed?
>=20
> Regards, Vidya
>=20
> ----------------------------------------------------------------------
> --
>  *From:* Kent Leung (kleung) [mailto:kleung@cisco.com] *Sent:* Friday,

> November 17, 2006 9:52 AM *To:* mip4@ietf.org *Subject:* [Mip4] Proxy=20
> Mobile IPv4 in the WG charter
>=20
> Hi.  The draft-leung-mip4-proxy-mode-01.txt draft describes using=20
> Mobile IPv4 in proxy mode to provide network-based mobility=20
> management.  There will need to be some more work on the draft. But=20
> wanted to get some sense of support for Proxy Mobile IPv4 in this WG.

> Certainly there are a few SDOs which have either adopted or interested

> in such mechanism.
>=20
> Do folks want to take this on as a WG item eventually?
>=20
> Kent
>=20

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Nov 28 15:57:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GpA19-0001xp-Sn; Tue, 28 Nov 2006 15:57:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GpA18-0001xg-A3
	for mip4@ietf.org; Tue, 28 Nov 2006 15:57:26 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GpA16-0006Eh-VG
	for mip4@ietf.org; Tue, 28 Nov 2006 15:57:26 -0500
Received: from [10.1.210.7] ([66.92.223.6]) by mail2.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 28 Nov 2006 12:57:23 -0800
Message-ID: <456CA2B2.9010708@azairenet.com>
Date: Tue, 28 Nov 2006 12:57:22 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: mip4@ietf.org
Subject: Re: [Mip4] WGLC: draft-ietf-mip4-mobike-connectivity-01.txt
References: <BE4B07D4197BF34EB3B753DD34EBCD130125E6C2@de01exm67.ds.mot.com>
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD130125E6C2@de01exm67.ds.mot.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Nov 2006 20:57:24.0048 (UTC)
	FILETIME=[CDCCA500:01C7132F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: McCann Peter-A001034 <pete.mccann@motorola.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

just wanted to point out that the only major change
since the last WG last call was to add a new section
in the Appendix to show how the solution can be
applied to a mobile operator network.

Vijay

McCann Peter-A001034 wrote:
> This message announces a (second) WG last call on:
> 
>    "Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
>    draft-ietf-mip4-mobike-connectivity-01.txt
> 
> The last call will conclude at 24:00 UTC on Tuesday, 12 December 2006.
> 
> "Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
> describes 
> a solution using Mobile IPv4 and mobility extensions to IKEv2 (MOBIKE)
> to 
> provide secure connectivity and mobility.
> 
> A URL for this internet draft is:
> 
> http://www.ietf.org/internet-drafts/draft-ietf-mip4-mobike-connectivity-
> 01.txt
> 
> 
> Please respond to this WG last call:
> 
> 
> * If you have no comments on the draft, and support its advancement,
>   simply respond with a line containing something like
> 
> 
>    "I support the advancement of this document to the IESG with a
>     request for publication as proposed standard."
> 
> 
>   If you have comments, please use a line similar to the one above, and
>   supplement this with your comments.
> 
> 
> 
> * If you *don't* support its advancement, respond with a line containing
>   something like the following, supplemented by your comments -
> 
> 
>    "I don't support the advancement of this document to the IESG with
>     a request for publication as proposed standard, for the following
>     reasons:"
>    ...
> 
> 
> 
> 
>     Pete & Henrik
> 


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Nov 28 16:13:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GpAGi-0000v2-7N; Tue, 28 Nov 2006 16:13:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GpAGg-0000um-CH
	for mip4@ietf.org; Tue, 28 Nov 2006 16:13:30 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GpAGe-0001jT-0y
	for mip4@ietf.org; Tue, 28 Nov 2006 16:13:30 -0500
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-4.cisco.com with ESMTP; 28 Nov 2006 13:13:27 -0800
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 kASLDR3W031563; 
	Tue, 28 Nov 2006 13:13:27 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id kASLDQiq007035;
	Tue, 28 Nov 2006 13:13:27 -0800 (PST)
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); 
	Tue, 28 Nov 2006 13:13:27 -0800
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] New revision for rfc3344bis;
	UDP inconsistency and candidate solution
Date: Tue, 28 Nov 2006 13:13:26 -0800
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5202EDC2CE@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] New revision for rfc3344bis;
	UDP inconsistency and candidate solution
Thread-Index: AccRxWrX+tvBw5p+QxiQ1FPWjiiUhwBbI8bA
From: "Kent Leung \(kleung\)" <kleung@cisco.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	"Charles E. Perkins" <charles.perkins@nokia.com>
X-OriginalArrivalTime: 28 Nov 2006 21:13:27.0053 (UTC)
	FILETIME=[0BCB8BD0:01C71332]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1642; t=1164748407;
	x=1165612407; c=relaxed/simple; s=sjdkim1002;
	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<kleung@cisco.com>
	|Subject:=20RE=3A=20[Mip4]=20New=20revision=20for=20rfc3344bis=3BUDP=20in
	consistency=20and=20candidate=20solution |Sender:=20;
	bh=LIlkIAGg87xt4jQWMuP5G5FP4iRN/PRLluyMV5YphX8=;
	b=AWzct7DPlqX9U0g0FebAyHtr5FdFqC6djNbygADVTjspAHx23iXjCBx/VQzQ4rW79wlPYuQ9
	2ct+hmHuEJLm93Pc0+280MuhYJAQF6jcbaYMPcY86h8NfFkXWBMp2yFD;
Authentication-Results: sj-dkim-1; header.From=kleung@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Yes, I agree as well.

Kent=20

-----Original Message-----
From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]=20
Sent: Sunday, November 26, 2006 5:41 PM
To: Charles E. Perkins
Cc: Mobile IPv4 Mailing List
Subject: Re: [Mip4] New revision for rfc3344bis;UDP inconsistency and
candidate solution

Charles E. Perkins wrote:

> As pointed out, copying the value of the destination port into the=20
> source port should be identically the same as setting the source port=20
> value to 434.  So, the value of the field cannot be described as=20
> "variable" as things now stand.

I agree with Sami and Henrik. just copy the destination port on the
registration request instead of saying port 434 explicitly.

> I propose the following text changes:
>=20
> (A) In section "3.4. Registration Reply", change
>=20
>  >    UDP fields:
>  >
>  >        Source Port           <variable>
>=20
> to be:
>=20
>    UDP fields:
>=20
>        Source Port           434

    UDP fields:

        Source Port           Copied from the UDP destination port
                              of the corresponding Registration
                              Request.

> (B). In section "3.8.3.1. IP/UDP Fields", change:
>=20
>  >       UDP Source Port
>  >                Copied from the UDP Destination Port of the
Registration
>  >                Request.

and leave this as is.

Vijay

--
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Nov 28 17:09:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GpB9B-0007Tu-N9; Tue, 28 Nov 2006 17:09:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GpB9A-0007Tg-8n
	for mip4@ietf.org; Tue, 28 Nov 2006 17:09:48 -0500
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GpB98-00025C-P4
	for mip4@ietf.org; Tue, 28 Nov 2006 17:09:48 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id DB46D1E0262
	for <mip4@ietf.org>; Tue, 28 Nov 2006 17:09:42 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 30371-02 for <mip4@ietf.org>;
	Tue, 28 Nov 2006 17:09:38 -0500 (EST)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP
	for <mip4@ietf.org>; Tue, 28 Nov 2006 17:09:38 -0500 (EST)
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 28 Nov 2006 17:09:37 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter
Date: Tue, 28 Nov 2006 17:09:37 -0500
Message-ID: <7CCD07160348804497EF29E9EA5560D7FBD585@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Proxy Mobile IPv4 in the WG charter
Thread-Index: AccNlcmwPtkYQawpQ8Ca8NXFWHhZPgFlRN0gAAOdamA=
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Kent Leung (kleung)" <kleung@cisco.com>,
	"Alexandru Petrescu" <alexandru.petrescu@motorola.com>,
	"Narayanan, Vidya" <vidyan@qualcomm.com>
X-OriginalArrivalTime: 28 Nov 2006 22:09:37.0261 (UTC)
	FILETIME=[E49879D0:01C71339]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi Kent,

Thanks for bringing this up. I support standardization of PMIP4 in IETF.
This is the only way we can make sure that a single PMIP4 protocol is
used across all SDOs. There is sufficient industry traction on PMIP4,
therefore it should be included in the MIP4 WG charter.

-Kuntal


> -----Original Message-----
> From: Kent Leung (kleung) [mailto:kleung@cisco.com]=20
> Sent: Tuesday, November 28, 2006 2:25 PM
> To: Alexandru Petrescu; Narayanan, Vidya
> Cc: mip4@ietf.org
> Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter
>=20
> Hi Alex.  WiMAX supports both client MIPv4 and proxy MIPv4=20
> modes.  I prefer to keep the discussion focused on the need=20
> to standardize MIPv4 in proxy mode in IETF.  I believe it=20
> would be highly valuable specification and has potential=20
> widespread use.
>=20
> Kent=20
>=20
> -----Original Message-----
> From: Alexandru Petrescu [mailto:alexandru.petrescu@motorola.com]
> Sent: Tuesday, November 21, 2006 9:51 AM
> To: Narayanan, Vidya
> Cc: Kent Leung (kleung); mip4@ietf.org
> Subject: Re: [Mip4] Proxy Mobile IPv4 in the WG charter
>=20
> Narayanan, Vidya wrote:
> > Hi Kent, If NETLMM supported IPv4 endpoints, do we still need a=20
> > standardized PMIPv4 solution?
>=20
> Not sure what NETLMM is, or whether it supported IPv4 endpoints.
>=20
> The other question is whether the known FA mode of MIP4 can=20
> figure as a candidate for what WiMax nominates as Proxy MIP,=20
> and the CCoA mode as what WiMax nominates Client MIP.
>=20
> Alex
>=20
> > Or, is this an effort to document what has been already deployed?
> >=20
> > Regards, Vidya
> >=20
> >=20
> ----------------------------------------------------------------------
> > --
> >  *From:* Kent Leung (kleung) [mailto:kleung@cisco.com]=20
> *Sent:* Friday,
>=20
> > November 17, 2006 9:52 AM *To:* mip4@ietf.org *Subject:*=20
> [Mip4] Proxy=20
> > Mobile IPv4 in the WG charter
> >=20
> > Hi.  The draft-leung-mip4-proxy-mode-01.txt draft describes using=20
> > Mobile IPv4 in proxy mode to provide network-based mobility=20
> > management.  There will need to be some more work on the draft. But=20
> > wanted to get some sense of support for Proxy Mobile IPv4=20
> in this WG.
>=20
> > Certainly there are a few SDOs which have either adopted or=20
> interested
>=20
> > in such mechanism.
> >=20
> > Do folks want to take this on as a WG item eventually?
> >=20
> > Kent
> >=20
>=20
> --
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
>=20

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Nov 28 18:45:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GpCdx-0008F6-Nx; Tue, 28 Nov 2006 18:45:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GpCdw-0008F0-Ns
	for mip4@ietf.org; Tue, 28 Nov 2006 18:45:40 -0500
Received: from web60318.mail.yahoo.com ([209.73.178.126])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GpCdu-00076A-7f
	for mip4@ietf.org; Tue, 28 Nov 2006 18:45:40 -0500
Received: (qmail 64251 invoked by uid 60001); 28 Nov 2006 23:45:23 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type;
	b=YHr+50UM44p1RNZ+k4lHG/huS02lz6nQhLypBkbI1XJtqt3ZWSxCv5K1EEGQpkUIlr917OokrTPLruWuy8i3ZTXsmazHwPjSPMWR8MFg3p8RFXHXO8H2lIVfh0kh4lpwZjp5KWw1Ru3TH0BRMcwccfa67/uPbK9YJiKbcZG/9ss=
	; 
Message-ID: <20061128234523.64249.qmail@web60318.mail.yahoo.com>
Received: from [12.129.211.52] by web60318.mail.yahoo.com via HTTP;
	Tue, 28 Nov 2006 15:45:23 PST
Date: Tue, 28 Nov 2006 15:45:22 -0800 (PST)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: [Mip4] Proxy Mobile IPv4 in the WG charter
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
MIME-Version: 1.0
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1259896401=="
Errors-To: mip4-bounces@ietf.org

--===============1259896401==
Content-Type: multipart/alternative; boundary="0-171152848-1164757522=:15698"

--0-171152848-1164757522=:15698
Content-Type: text/plain; charset=ascii
Content-Transfer-Encoding: quoted-printable

I am neutral on PMIPv4 standardization, in fact may be we should not.=0ASin=
ce netlmm WG from the beginning has not ruled out a v4 solution and since n=
etlmm WG decided to do PMIPv6, it seems logical that netlmm does PMIPv4 as =
well. Is there a problem with that?=0A=0A--behcet=0A=0A=0A=0A----- Original=
 Message ----=0AFrom: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>=
=0ATo: Kent Leung (kleung) <kleung@cisco.com>; Alexandru Petrescu <alexandr=
u.petrescu@motorola.com>; "Narayanan, Vidya" <vidyan@qualcomm.com>=0ACc: mi=
p4@ietf.org=0ASent: Tuesday, November 28, 2006 4:09:37 PM=0ASubject: RE: [M=
ip4] Proxy Mobile IPv4 in the WG charter=0A=0A=0AHi Kent,=0A=0AThanks for b=
ringing this up. I support standardization of PMIP4 in IETF.=0AThis is the =
only way we can make sure that a single PMIP4 protocol is=0Aused across all=
 SDOs. There is sufficient industry traction on PMIP4,=0Atherefore it shoul=
d be included in the MIP4 WG charter.=0A=0A-Kuntal=0A=0A=0A> -----Original =
Message-----=0A> From: Kent Leung (kleung) [mailto:kleung@cisco.com] =0A> S=
ent: Tuesday, November 28, 2006 2:25 PM=0A> To: Alexandru Petrescu; Narayan=
an, Vidya=0A> Cc: mip4@ietf.org=0A> Subject: RE: [Mip4] Proxy Mobile IPv4 i=
n the WG charter=0A> =0A> Hi Alex.  WiMAX supports both client MIPv4 and pr=
oxy MIPv4 =0A> modes.  I prefer to keep the discussion focused on the need =
=0A> to standardize MIPv4 in proxy mode in IETF.  I believe it =0A> would b=
e highly valuable specification and has potential =0A> widespread use.=0A> =
=0A> Kent =0A> =0A> -----Original Message-----=0A> From: Alexandru Petrescu=
 [mailto:alexandru.petrescu@motorola.com]=0A> Sent: Tuesday, November 21, 2=
006 9:51 AM=0A> To: Narayanan, Vidya=0A> Cc: Kent Leung (kleung); mip4@ietf=
.org=0A> Subject: Re: [Mip4] Proxy Mobile IPv4 in the WG charter=0A> =0A> N=
arayanan, Vidya wrote:=0A> > Hi Kent, If NETLMM supported IPv4 endpoints, d=
o we still need a =0A> > standardized PMIPv4 solution?=0A> =0A> Not sure wh=
at NETLMM is, or whether it supported IPv4 endpoints.=0A> =0A> The other qu=
estion is whether the known FA mode of MIP4 can =0A> figure as a candidate =
for what WiMax nominates as Proxy MIP, =0A> and the CCoA mode as what WiMax=
 nominates Client MIP.=0A> =0A> Alex=0A> =0A> > Or, is this an effort to do=
cument what has been already deployed?=0A> > =0A> > Regards, Vidya=0A> > =
=0A> > =0A> ---------------------------------------------------------------=
-------=0A> > --=0A> >  *From:* Kent Leung (kleung) [mailto:kleung@cisco.co=
m] =0A> *Sent:* Friday,=0A> =0A> > November 17, 2006 9:52 AM *To:* mip4@iet=
f.org *Subject:* =0A> [Mip4] Proxy =0A> > Mobile IPv4 in the WG charter=0A>=
 > =0A> > Hi.  The draft-leung-mip4-proxy-mode-01.txt draft describes using=
 =0A> > Mobile IPv4 in proxy mode to provide network-based mobility =0A> > =
management.  There will need to be some more work on the draft. But =0A> > =
wanted to get some sense of support for Proxy Mobile IPv4 =0A> in this WG.=
=0A> =0A> > Certainly there are a few SDOs which have either adopted or =0A=
> interested=0A> =0A> > in such mechanism.=0A> > =0A> > Do folks want to ta=
ke this on as a WG item eventually?=0A> > =0A> > Kent=0A> > =0A> =0A> --=0A=
> Mip4 mailing list: Mip4@ietf.org=0A>     Web interface: https://www1.ietf=
.org/mailman/listinfo/mip4=0A>      Charter page: http://www.ietf.org/html.=
charters/mip4-charter.html=0A> Supplemental site: http://www.mip4.org/=0A> =
=0A=0A--=0AMip4 mailing list: Mip4@ietf.org=0A    Web interface: https://ww=
w1.ietf.org/mailman/listinfo/mip4=0A     Charter page: http://www.ietf.org/=
html.charters/mip4-charter.html=0ASupplemental site: http://www.mip4.org/
--0-171152848-1164757522=:15698
Content-Type: text/html; charset=ascii
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:times new roman, new york, times, serif;=
font-size:12pt"><DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman=
, new york, times, serif"><FONT color=3D#6000bf>I am neutral on PMIPv4 stan=
dardization, in fact may be we should not.</FONT></DIV>=0A<DIV style=3D"FON=
T-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif"><FONT c=
olor=3D#6000bf>Since netlmm WG from the beginning has <STRONG>not </STRONG>=
ruled out a v4 solution and since netlmm WG decided to do PMIPv6, it seems =
logical that netlmm does PMIPv4 as well. Is there a problem with that?</FON=
T></DIV>=0A<P><FONT color=3D#6000bf></FONT>&nbsp;</P>=0A<P><FONT color=3D#6=
000bf>--behcet</P>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new =
roman, new york, times, serif"><BR></FONT><BR></DIV>=0A<DIV style=3D"FONT-S=
IZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">----- Orig=
inal Message ----<BR>From: "Chowdhury, Kuntal" &lt;kchowdhury@starentnetwor=
ks.com&gt;<BR>To: Kent Leung (kleung) &lt;kleung@cisco.com&gt;; Alexandru P=
etrescu &lt;alexandru.petrescu@motorola.com&gt;; "Narayanan, Vidya" &lt;vid=
yan@qualcomm.com&gt;<BR>Cc: mip4@ietf.org<BR>Sent: Tuesday, November 28, 20=
06 4:09:37 PM<BR>Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter<BR=
><BR>=0A<DIV>Hi Kent,<BR><BR>Thanks for bringing this up. I support standar=
dization of PMIP4 in IETF.<BR>This is the only way we can make sure that a =
single PMIP4 protocol is<BR>used across all SDOs. There is sufficient indus=
try traction on PMIP4,<BR>therefore it should be included in the MIP4 WG ch=
arter.<BR><BR>-Kuntal<BR><BR><BR>&gt; -----Original Message-----<BR>&gt; Fr=
om: Kent Leung (kleung) [mailto:kleung@cisco.com] <BR>&gt; Sent: Tuesday, N=
ovember 28, 2006 2:25 PM<BR>&gt; To: Alexandru Petrescu; Narayanan, Vidya<B=
R>&gt; Cc: mip4@ietf.org<BR>&gt; Subject: RE: [Mip4] Proxy Mobile IPv4 in t=
he WG charter<BR>&gt; <BR>&gt; Hi Alex.&nbsp;&nbsp;WiMAX supports both clie=
nt MIPv4 and proxy MIPv4 <BR>&gt; modes.&nbsp;&nbsp;I prefer to keep the di=
scussion focused on the need <BR>&gt; to standardize MIPv4 in proxy mode in=
 IETF.&nbsp;&nbsp;I believe it <BR>&gt; would be highly valuable specificat=
ion and has potential <BR>&gt; widespread use.<BR>&gt; <BR>&gt; Kent <BR>&g=
t; <BR>&gt;
 -----Original Message-----<BR>&gt; From: Alexandru Petrescu [mailto:alexan=
dru.petrescu@motorola.com]<BR>&gt; Sent: Tuesday, November 21, 2006 9:51 AM=
<BR>&gt; To: Narayanan, Vidya<BR>&gt; Cc: Kent Leung (kleung); mip4@ietf.or=
g<BR>&gt; Subject: Re: [Mip4] Proxy Mobile IPv4 in the WG charter<BR>&gt; <=
BR>&gt; Narayanan, Vidya wrote:<BR>&gt; &gt; Hi Kent, If NETLMM supported I=
Pv4 endpoints, do we still need a <BR>&gt; &gt; standardized PMIPv4 solutio=
n?<BR>&gt; <BR>&gt; Not sure what NETLMM is, or whether it supported IPv4 e=
ndpoints.<BR>&gt; <BR>&gt; The other question is whether the known FA mode =
of MIP4 can <BR>&gt; figure as a candidate for what WiMax nominates as Prox=
y MIP, <BR>&gt; and the CCoA mode as what WiMax nominates Client MIP.<BR>&g=
t; <BR>&gt; Alex<BR>&gt; <BR>&gt; &gt; Or, is this an effort to document wh=
at has been already deployed?<BR>&gt; &gt; <BR>&gt; &gt; Regards, Vidya<BR>=
&gt; &gt; <BR>&gt; &gt; <BR>&gt;
 ----------------------------------------------------------------------<BR>=
&gt; &gt; --<BR>&gt; &gt;&nbsp;&nbsp;*From:* Kent Leung (kleung) [mailto:kl=
eung@cisco.com] <BR>&gt; *Sent:* Friday,<BR>&gt; <BR>&gt; &gt; November 17,=
 2006 9:52 AM *To:* mip4@ietf.org *Subject:* <BR>&gt; [Mip4] Proxy <BR>&gt;=
 &gt; Mobile IPv4 in the WG charter<BR>&gt; &gt; <BR>&gt; &gt; Hi.&nbsp;&nb=
sp;The draft-leung-mip4-proxy-mode-01.txt draft describes using <BR>&gt; &g=
t; Mobile IPv4 in proxy mode to provide network-based mobility <BR>&gt; &gt=
; management.&nbsp;&nbsp;There will need to be some more work on the draft.=
 But <BR>&gt; &gt; wanted to get some sense of support for Proxy Mobile IPv=
4 <BR>&gt; in this WG.<BR>&gt; <BR>&gt; &gt; Certainly there are a few SDOs=
 which have either adopted or <BR>&gt; interested<BR>&gt; <BR>&gt; &gt; in =
such mechanism.<BR>&gt; &gt; <BR>&gt; &gt; Do folks want to take this on as=
 a WG item eventually?<BR>&gt; &gt; <BR>&gt; &gt; Kent<BR>&gt; &gt; <BR>&gt=
; <BR>&gt;
 --<BR>&gt; Mip4 mailing list: Mip4@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp=
; Web interface: <A href=3D"https://www1.ietf.org/mailman/listinfo/mip4" ta=
rget=3D_blank>https://www1.ietf.org/mailman/listinfo/mip4</A><BR>&gt;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Charter page: <A href=3D"http://www.ietf.org/=
html.charters/mip4-charter.html" target=3D_blank>http://www.ietf.org/html.c=
harters/mip4-charter.html</A><BR>&gt; Supplemental site: <A href=3D"http://=
www.mip4.org/" target=3D_blank>http://www.mip4.org/</A><BR>&gt; <BR><BR>--<=
BR>Mip4 mailing list: Mip4@ietf.org<BR>&nbsp;&nbsp;&nbsp;&nbsp;Web interfac=
e: <A href=3D"https://www1.ietf.org/mailman/listinfo/mip4" target=3D_blank>=
https://www1.ietf.org/mailman/listinfo/mip4</A><BR>&nbsp;&nbsp;&nbsp;&nbsp;=
 Charter page: <A href=3D"http://www.ietf.org/html.charters/mip4-charter.ht=
ml" target=3D_blank>http://www.ietf.org/html.charters/mip4-charter.html</A>=
<BR>Supplemental site: <A href=3D"http://www.mip4.org/" target=3D_blank>htt=
p://www.mip4.org/</A></DIV></DIV>=0A<DIV style=3D"FONT-SIZE: 12pt; FONT-FAM=
ILY: times new roman, new york, times, serif"><BR></DIV></div></body></html=
>
--0-171152848-1164757522=:15698--


--===============1259896401==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1259896401==--




From mip4-bounces@ietf.org Wed Nov 29 01:56:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GpJMQ-0007CI-5b; Wed, 29 Nov 2006 01:56:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GpJMP-0007CA-26
	for mip4@ietf.org; Wed, 29 Nov 2006 01:56:01 -0500
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GpJML-0000EK-CK
	for mip4@ietf.org; Wed, 29 Nov 2006 01:56:01 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 056061E0289
	for <mip4@ietf.org>; Wed, 29 Nov 2006 01:55:52 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 05747-12 for <mip4@ietf.org>;
	Wed, 29 Nov 2006 01:55:47 -0500 (EST)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP
	for <mip4@ietf.org>; Wed, 29 Nov 2006 01:55:47 -0500 (EST)
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 29 Nov 2006 01:55:47 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter
Date: Wed, 29 Nov 2006 01:55:46 -0500
Message-ID: <7CCD07160348804497EF29E9EA5560D7FBD58E@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Proxy Mobile IPv4 in the WG charter
Thread-Index: AccTR0jZbZa1V4bFSl2INJi1gITZ7wAOzCUg
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Behcet Sarikaya" <sarikaya@ieee.org>
X-OriginalArrivalTime: 29 Nov 2006 06:55:47.0152 (UTC)
	FILETIME=[65B78D00:01C71383]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8eeb555810cda1f2c5989480370dc4ca
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0656109281=="
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0656109281==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C71383.657185A7"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C71383.657185A7
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Behcet,
=20
I am not clear on what you meant by "in fact may be we should not". We
should not what? Please clarify.
=20
MIP4 and NETLMM both are IETF WGs. The goal is to define PMIP4 protocol
in IETF...so, as long as there is enough interest and support to get the
job done, the place should not matter very much.
=20
-Kuntal
=20



________________________________

	From: Behcet Sarikaya [mailto:behcetsarikaya@yahoo.com]=20
	Sent: Tuesday, November 28, 2006 5:45 PM
	To: Chowdhury, Kuntal
	Cc: mip4@ietf.org
	Subject: Re: [Mip4] Proxy Mobile IPv4 in the WG charter
=09
=09
	I am neutral on PMIPv4 standardization, in fact may be we should
not.
	Since netlmm WG from the beginning has not ruled out a v4
solution and since netlmm WG decided to do PMIPv6, it seems logical that
netlmm does PMIPv4 as well. Is there a problem with that?

	=20

	--behcet



	----- Original Message ----
	From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
	To: Kent Leung (kleung) <kleung@cisco.com>; Alexandru Petrescu
<alexandru.petrescu@motorola.com>; "Narayanan, Vidya"
<vidyan@qualcomm.com>
	Cc: mip4@ietf.org
	Sent: Tuesday, November 28, 2006 4:09:37 PM
	Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter
=09
=09
	Hi Kent,
=09
	Thanks for bringing this up. I support standardization of PMIP4
in IETF.
	This is the only way we can make sure that a single PMIP4
protocol is
	used across all SDOs. There is sufficient industry traction on
PMIP4,
	therefore it should be included in the MIP4 WG charter.
=09
	-Kuntal
=09
=09
	> -----Original Message-----
	> From: Kent Leung (kleung) [mailto:kleung@cisco.com]=20
	> Sent: Tuesday, November 28, 2006 2:25 PM
	> To: Alexandru Petrescu; Narayanan, Vidya
	> Cc: mip4@ietf.org
	> Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter
	>=20
	> Hi Alex.  WiMAX supports both client MIPv4 and proxy MIPv4=20
	> modes.  I prefer to keep the discussion focused on the need=20
	> to standardize MIPv4 in proxy mode in IETF.  I believe it=20
	> would be highly valuable specification and has potential=20
	> widespread use.
	>=20
	> Kent=20
	>=20
	> -----Original Message-----
	> From: Alexandru Petrescu
[mailto:alexandru.petrescu@motorola.com]
	> Sent: Tuesday, November 21, 2006 9:51 AM
	> To: Narayanan, Vidya
	> Cc: Kent Leung (kleung); mip4@ietf.org
	> Subject: Re: [Mip4] Proxy Mobile IPv4 in the WG charter
	>=20
	> Narayanan, Vidya wrote:
	> > Hi Kent, If NETLMM supported IPv4 endpoints, do we still
need a=20
	> > standardized PMIPv4 solution?
	>=20
	> Not sure what NETLMM is, or whether it supported IPv4
endpoints.
	>=20
	> The other question is whether the known FA mode of MIP4 can=20
	> figure as a candidate for what WiMax nominates as Proxy MIP,=20
	> and the CCoA mode as what WiMax nominates Client MIP.
	>=20
	> Alex
	>=20
	> > Or, is this an effort to document what has been already
deployed?
	> >=20
	> > Regards, Vidya
	> >=20
	> >=20
	>
----------------------------------------------------------------------
	> > --
	> >  *From:* Kent Leung (kleung) [mailto:kleung@cisco.com]=20
	> *Sent:* Friday,
	>=20
	> > November 17, 2006 9:52 AM *To:* mip4@ietf.org *Subject:*=20
	> [Mip4] Proxy=20
	> > Mobile IPv4 in the WG charter
	> >=20
	> > Hi.  The draft-leung-mip4-proxy-mode-01.txt draft describes
using=20
	> > Mobile IPv4 in proxy mode to provide network-based mobility=20
	> > management.  There will need to be some more work on the
draft. But=20
	> > wanted to get some sense of support for Proxy Mobile IPv4=20
	> in this WG.
	>=20
	> > Certainly there are a few SDOs which have either adopted or=20
	> interested
	>=20
	> > in such mechanism.
	> >=20
	> > Do folks want to take this on as a WG item eventually?
	> >=20
	> > Kent
	> >=20
	>=20
	> --
	> Mip4 mailing list: Mip4@ietf.org
	>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
	>      Charter page:
http://www.ietf.org/html.charters/mip4-charter.html
	> Supplemental site: http://www.mip4.org/
	>=20
=09
	--
	Mip4 mailing list: Mip4@ietf.org
	    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
	     Charter page:
http://www.ietf.org/html.charters/mip4-charter.html
	Supplemental site: http://www.mip4.org/



------_=_NextPart_001_01C71383.657185A7
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<STYLE type=3Dtext/css>DIV {
	MARGIN: 0px
}
</STYLE>

<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D775104906-29112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Behcet,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D775104906-29112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D775104906-29112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I am not clear on what you meant by "in fact =
may be we=20
should not". We should not what? Please clarify.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D775104906-29112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D775104906-29112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>MIP4 and NETLMM both are IETF WGs. The goal is =
to define=20
PMIP4 protocol in IETF...so, as long as there is enough interest and =
support to=20
get the job done, the place should not matter very =
much.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D775104906-29112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D775104906-29112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>-Kuntal</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D775104906-29112006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Behcet Sarikaya=20
  [mailto:behcetsarikaya@yahoo.com] <BR><B>Sent:</B> Tuesday, November =
28, 2006=20
  5:45 PM<BR><B>To:</B> Chowdhury, Kuntal<BR><B>Cc:</B>=20
  mip4@ietf.org<BR><B>Subject:</B> Re: [Mip4] Proxy Mobile IPv4 in the =
WG=20
  charter<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, =
times, serif">
  <DIV=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, =
times, serif"><FONT=20
  color=3D#6000bf>I am neutral on PMIPv4 standardization, in fact may be =
we should=20
  not.</FONT></DIV>
  <DIV=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, =
times, serif"><FONT=20
  color=3D#6000bf>Since netlmm WG from the beginning has <STRONG>not=20
  </STRONG>ruled out a v4 solution and since netlmm WG decided to do =
PMIPv6, it=20
  seems logical that netlmm does PMIPv4 as well. Is there a problem with =

  that?</FONT></DIV>
  <P><FONT color=3D#6000bf></FONT>&nbsp;</P>
  <P><FONT color=3D#6000bf>--behcet</P>
  <DIV=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, =
times, serif"><BR></FONT><BR></DIV>
  <DIV=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, =
times, serif">-----=20
  Original Message ----<BR>From: "Chowdhury, Kuntal"=20
  &lt;kchowdhury@starentnetworks.com&gt;<BR>To: Kent Leung (kleung)=20
  &lt;kleung@cisco.com&gt;; Alexandru Petrescu=20
  &lt;alexandru.petrescu@motorola.com&gt;; "Narayanan, Vidya"=20
  &lt;vidyan@qualcomm.com&gt;<BR>Cc: mip4@ietf.org<BR>Sent: Tuesday, =
November=20
  28, 2006 4:09:37 PM<BR>Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG =

  charter<BR><BR>
  <DIV>Hi Kent,<BR><BR>Thanks for bringing this up. I support =
standardization of=20
  PMIP4 in IETF.<BR>This is the only way we can make sure that a single =
PMIP4=20
  protocol is<BR>used across all SDOs. There is sufficient industry =
traction on=20
  PMIP4,<BR>therefore it should be included in the MIP4 WG=20
  charter.<BR><BR>-Kuntal<BR><BR><BR>&gt; -----Original =
Message-----<BR>&gt;=20
  From: Kent Leung (kleung) [mailto:kleung@cisco.com] <BR>&gt; Sent: =
Tuesday,=20
  November 28, 2006 2:25 PM<BR>&gt; To: Alexandru Petrescu; Narayanan,=20
  Vidya<BR>&gt; Cc: mip4@ietf.org<BR>&gt; Subject: RE: [Mip4] Proxy =
Mobile IPv4=20
  in the WG charter<BR>&gt; <BR>&gt; Hi Alex.&nbsp;&nbsp;WiMAX supports =
both=20
  client MIPv4 and proxy MIPv4 <BR>&gt; modes.&nbsp;&nbsp;I prefer to =
keep the=20
  discussion focused on the need <BR>&gt; to standardize MIPv4 in proxy =
mode in=20
  IETF.&nbsp;&nbsp;I believe it <BR>&gt; would be highly valuable =
specification=20
  and has potential <BR>&gt; widespread use.<BR>&gt; <BR>&gt; Kent =
<BR>&gt;=20
  <BR>&gt; -----Original Message-----<BR>&gt; From: Alexandru Petrescu=20
  [mailto:alexandru.petrescu@motorola.com]<BR>&gt; Sent: Tuesday, =
November 21,=20
  2006 9:51 AM<BR>&gt; To: Narayanan, Vidya<BR>&gt; Cc: Kent Leung =
(kleung);=20
  mip4@ietf.org<BR>&gt; Subject: Re: [Mip4] Proxy Mobile IPv4 in the WG=20
  charter<BR>&gt; <BR>&gt; Narayanan, Vidya wrote:<BR>&gt; &gt; Hi Kent, =
If=20
  NETLMM supported IPv4 endpoints, do we still need a <BR>&gt; &gt; =
standardized=20
  PMIPv4 solution?<BR>&gt; <BR>&gt; Not sure what NETLMM is, or whether =
it=20
  supported IPv4 endpoints.<BR>&gt; <BR>&gt; The other question is =
whether the=20
  known FA mode of MIP4 can <BR>&gt; figure as a candidate for what =
WiMax=20
  nominates as Proxy MIP, <BR>&gt; and the CCoA mode as what WiMax =
nominates=20
  Client MIP.<BR>&gt; <BR>&gt; Alex<BR>&gt; <BR>&gt; &gt; Or, is this an =
effort=20
  to document what has been already deployed?<BR>&gt; &gt; <BR>&gt; &gt; =

  Regards, Vidya<BR>&gt; &gt; <BR>&gt; &gt; <BR>&gt;=20
  =
----------------------------------------------------------------------<BR=
>&gt;=20
  &gt; --<BR>&gt; &gt;&nbsp;&nbsp;*From:* Kent Leung (kleung)=20
  [mailto:kleung@cisco.com] <BR>&gt; *Sent:* Friday,<BR>&gt; <BR>&gt; =
&gt;=20
  November 17, 2006 9:52 AM *To:* mip4@ietf.org *Subject:* <BR>&gt; =
[Mip4] Proxy=20
  <BR>&gt; &gt; Mobile IPv4 in the WG charter<BR>&gt; &gt; <BR>&gt; &gt; =

  Hi.&nbsp;&nbsp;The draft-leung-mip4-proxy-mode-01.txt draft describes =
using=20
  <BR>&gt; &gt; Mobile IPv4 in proxy mode to provide network-based =
mobility=20
  <BR>&gt; &gt; management.&nbsp;&nbsp;There will need to be some more =
work on=20
  the draft. But <BR>&gt; &gt; wanted to get some sense of support for =
Proxy=20
  Mobile IPv4 <BR>&gt; in this WG.<BR>&gt; <BR>&gt; &gt; Certainly there =
are a=20
  few SDOs which have either adopted or <BR>&gt; interested<BR>&gt; =
<BR>&gt;=20
  &gt; in such mechanism.<BR>&gt; &gt; <BR>&gt; &gt; Do folks want to =
take this=20
  on as a WG item eventually?<BR>&gt; &gt; <BR>&gt; &gt; Kent<BR>&gt; =
&gt;=20
  <BR>&gt; <BR>&gt; --<BR>&gt; Mip4 mailing list:=20
  Mip4@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Web interface: <A=20
  href=3D"https://www1.ietf.org/mailman/listinfo/mip4"=20
  =
target=3D_blank>https://www1.ietf.org/mailman/listinfo/mip4</A><BR>&gt;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Charter=20
  page: <A href=3D"http://www.ietf.org/html.charters/mip4-charter.html"=20
  =
target=3D_blank>http://www.ietf.org/html.charters/mip4-charter.html</A><B=
R>&gt;=20
  Supplemental site: <A href=3D"http://www.mip4.org/"=20
  target=3D_blank>http://www.mip4.org/</A><BR>&gt; <BR><BR>--<BR>Mip4 =
mailing=20
  list: Mip4@ietf.org<BR>&nbsp;&nbsp;&nbsp;&nbsp;Web interface: <A=20
  href=3D"https://www1.ietf.org/mailman/listinfo/mip4"=20
  =
target=3D_blank>https://www1.ietf.org/mailman/listinfo/mip4</A><BR>&nbsp;=
&nbsp;&nbsp;&nbsp;=20
  Charter page: <A =
href=3D"http://www.ietf.org/html.charters/mip4-charter.html"=20
  =
target=3D_blank>http://www.ietf.org/html.charters/mip4-charter.html</A><B=
R>Supplemental=20
  site: <A href=3D"http://www.mip4.org/"=20
  target=3D_blank>http://www.mip4.org/</A></DIV></DIV>
  <DIV=20
  style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, =
times, serif"><BR></DIV></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C71383.657185A7--


--===============0656109281==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0656109281==--




From mip4-bounces@ietf.org Wed Nov 29 05:33:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GpMkN-0001Vz-FI; Wed, 29 Nov 2006 05:32:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GpMkM-0001VS-Br
	for mip4@ietf.org; Wed, 29 Nov 2006 05:32:58 -0500
Received: from mail128.messagelabs.com ([216.82.250.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GpMkK-0006M8-EN
	for mip4@ietf.org; Wed, 29 Nov 2006 05:32:58 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-2.tower-128.messagelabs.com!1164796375!9222254!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 27668 invoked from network); 29 Nov 2006 10:32:55 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-2.tower-128.messagelabs.com with SMTP;
	29 Nov 2006 10:32:55 -0000
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id kATAWoVd006513;
	Wed, 29 Nov 2006 03:32:54 -0700 (MST)
Received: from [10.161.194.48] (ZFR01-2999.ea.mot.com [10.161.194.48])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id kATAWnEN025060;
	Wed, 29 Nov 2006 04:32:50 -0600 (CST)
Message-ID: <456D61D1.9020307@motorola.com>
Date: Wed, 29 Nov 2006 11:32:49 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: "Kent Leung (kleung)" <kleung@cisco.com>
Subject: Re: PMIPv4 vs FA MIP4 (was: [Mip4] Proxy Mobile IPv4 in the WG
	charter)
References: <2979E38DD6FC6544B789C8DAD7BAFC5202EDC27C@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC5202EDC27C@xmb-sjc-235.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: "Narayanan, Vidya" <vidyan@qualcomm.com>, mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Kent Leung (kleung) wrote:
> Hi Alex.  WiMAX supports both client MIPv4 and proxy MIPv4 modes.  I
> prefer to keep the discussion focused on the need to standardize MIPv4
> in proxy mode in IETF.  I believe it would be highly valuable
> specification and has potential widespread use.

Hi Kent, thanks for the reply.

My question was what is the fundamental difference between WiMax PMIPv4 
and IETF FA-mode MIPv4?

They may be worth investigating.

Alex

> 
> Kent 
> 
> -----Original Message-----
> From: Alexandru Petrescu [mailto:alexandru.petrescu@motorola.com] 
> Sent: Tuesday, November 21, 2006 9:51 AM
> To: Narayanan, Vidya
> Cc: Kent Leung (kleung); mip4@ietf.org
> Subject: Re: [Mip4] Proxy Mobile IPv4 in the WG charter
> 
> Narayanan, Vidya wrote:
>> Hi Kent, If NETLMM supported IPv4 endpoints, do we still need a 
>> standardized PMIPv4 solution?
> 
> Not sure what NETLMM is, or whether it supported IPv4 endpoints.
> 
> The other question is whether the known FA mode of MIP4 can figure as a
> candidate for what WiMax nominates as Proxy MIP, and the CCoA mode as
> what WiMax nominates Client MIP.
> 
> Alex
> 
>> Or, is this an effort to document what has been already deployed?
>>
>> Regards, Vidya
>>
>> ----------------------------------------------------------------------
>> --
>>  *From:* Kent Leung (kleung) [mailto:kleung@cisco.com] *Sent:* Friday,
> 
>> November 17, 2006 9:52 AM *To:* mip4@ietf.org *Subject:* [Mip4] Proxy 
>> Mobile IPv4 in the WG charter
>>
>> Hi.  The draft-leung-mip4-proxy-mode-01.txt draft describes using 
>> Mobile IPv4 in proxy mode to provide network-based mobility 
>> management.  There will need to be some more work on the draft. But 
>> wanted to get some sense of support for Proxy Mobile IPv4 in this WG.
> 
>> Certainly there are a few SDOs which have either adopted or interested
> 
>> in such mechanism.
>>
>> Do folks want to take this on as a WG item eventually?
>>
>> Kent
>>
> 


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Nov 29 05:57:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GpN7k-0007O4-G4; Wed, 29 Nov 2006 05:57:08 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GpN7j-0007Nz-7k
	for mip4@ietf.org; Wed, 29 Nov 2006 05:57:07 -0500
Received: from ceiling.dave.sonera.fi ([131.177.130.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GpN7h-00034t-Oi
	for mip4@ietf.org; Wed, 29 Nov 2006 05:57:07 -0500
Received: from ceiling.dave.sonera.fi (localhost [127.0.0.1]) by
	ceiling.dave.sonera.fi (Sendmail) with ESMTP id kATAutCx020363
	for <mip4@ietf.org>; Wed, 29 Nov 2006 12:56:56 +0200 (EET)
Received: from [131.177.37.116] (l50029133.pool.sonera.fi [131.177.37.116]) by
	ceiling.dave.sonera.fi (Sendmail) with ESMTP id kATAusYk020347;
	Wed, 29 Nov 2006 12:56:54 +0200 (EET)
Message-ID: <456D6775.4050905@teliasonera.com>
Date: Wed, 29 Nov 2006 12:56:53 +0200
From: Jouni Korhonen <jouni.korhonen@teliasonera.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip4] WGLC: draft-ietf-mip4-mobike-connectivity-01.txt
References: <BE4B07D4197BF34EB3B753DD34EBCD130125E6C2@de01exm67.ds.mot.com>
	<456CA2B2.9010708@azairenet.com>
In-Reply-To: <456CA2B2.9010708@azairenet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: mip4@ietf.org, McCann Peter-A001034 <pete.mccann@motorola.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi Vijay,

I think it was me who asked for this appendix. I'm happy to have it 
there now. I'm not sure whether it makes any additional value to mention 
in appendix A that the operator trusted network could also be 
implemented as the home link from MNs. For certain wireless technologies 
this would give a nice optimization.

Apart from the above "I support the advancement of this document to the 
IESG with a request for publication as proposed standard."

Cheers,
	Jouni

Vijay Devarapalli kirjoitti:
> just wanted to point out that the only major change
> since the last WG last call was to add a new section
> in the Appendix to show how the solution can be
> applied to a mobile operator network.
> 
> Vijay
> 
> McCann Peter-A001034 wrote:
>> This message announces a (second) WG last call on:
>>
>>    "Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
>>    draft-ietf-mip4-mobike-connectivity-01.txt
>>
>> The last call will conclude at 24:00 UTC on Tuesday, 12 December 2006.
>>
>> "Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
>> describes a solution using Mobile IPv4 and mobility extensions to 
>> IKEv2 (MOBIKE)
>> to provide secure connectivity and mobility.
>>
>> A URL for this internet draft is:
>>
>> http://www.ietf.org/internet-drafts/draft-ietf-mip4-mobike-connectivity-
>> 01.txt
>>
>>
>> Please respond to this WG last call:
>>
>>
>> * If you have no comments on the draft, and support its advancement,
>>   simply respond with a line containing something like
>>
>>
>>    "I support the advancement of this document to the IESG with a
>>     request for publication as proposed standard."
>>
>>
>>   If you have comments, please use a line similar to the one above, and
>>   supplement this with your comments.
>>
>>
>>
>> * If you *don't* support its advancement, respond with a line containing
>>   something like the following, supplemented by your comments -
>>
>>
>>    "I don't support the advancement of this document to the IESG with
>>     a request for publication as proposed standard, for the following
>>     reasons:"
>>    ...
>>
>>
>>
>>
>>     Pete & Henrik
>>
> 
> 

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Nov 29 11:23:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GpSDM-0001uB-Nf; Wed, 29 Nov 2006 11:23:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GpSDL-0001ti-Hv
	for mip4@ietf.org; Wed, 29 Nov 2006 11:23:15 -0500
Received: from mail128.messagelabs.com ([216.82.250.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GpSDB-0002f7-PR
	for mip4@ietf.org; Wed, 29 Nov 2006 11:23:15 -0500
X-VirusChecked: Checked
X-Env-Sender: sbrao@motorola.com
X-Msg-Ref: server-4.tower-128.messagelabs.com!1164817028!9214999!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.10]
Received: (qmail 5997 invoked from network); 29 Nov 2006 16:17:08 -0000
Received: from motgate6.mot.com (HELO motgate.mot.com) (129.188.136.10)
	by server-4.tower-128.messagelabs.com with SMTP;
	29 Nov 2006 16:17:08 -0000
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate.mot.com (8.12.11/Motorola) with ESMTP id kATGMXWx013576
	for <mip4@ietf.org>; Wed, 29 Nov 2006 09:22:35 -0700 (MST)
Received: from ct11exm63.ds.mot.com (ct11exm63.am.mot.com [10.177.8.47])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id kATGH5bR022645
	for <mip4@ietf.org>; Wed, 29 Nov 2006 10:17:06 -0600 (CST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter
Date: Wed, 29 Nov 2006 11:17:01 -0500
Message-ID: <92D17ACC46FB33448977916D9EC398F001289C52@ct11exm63.ds.mot.com>
In-Reply-To: <7CCD07160348804497EF29E9EA5560D7FBD58E@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Proxy Mobile IPv4 in the WG charter
Thread-Index: AccTR0jZbZa1V4bFSl2INJi1gITZ7wAOzCUgABN09tA=
From: "Rao Satyanarayana-W60007" <sbrao@motorola.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>,
	"Behcet Sarikaya" <sarikaya@ieee.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8df1ceff7d5e1ba4a25ab9834397277b
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0346285065=="
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0346285065==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C713D1.CE4CD631"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C713D1.CE4CD631
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I think it makes sense to develop a specification for the operation of
PMIPv4. It would help interoperability.
If  I am a service provider I would like my network to work with both
CMIPv4 hosts as well as hosts without CMIPv4. If a proxy is involved to
provide such a transparency then it helps to understand the operations
of such a proxy agent and its location and its interaction if any with
the host for which it is acting as a proxy and its interaction with
other elements of the MIPv4 infrastructure and its configuration and
management aspects.=20
=20
I am neutral to whether the work should be done in MIPv4 WG or netLMM
WG.
=20
- Satya Rao
Mobile Devices Technology Office
Motorola
Tel: 512-427-7335
Email: sbrao@motorola.com <mailto:sbrao@motorola.com>=20
=20


________________________________

	From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]=20
	Sent: Wednesday, November 29, 2006 12:56 AM
	To: Behcet Sarikaya
	Cc: mip4@ietf.org
	Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter
=09
=09
	Behcet,
	=20
	I am not clear on what you meant by "in fact may be we should
not". We should not what? Please clarify.
	=20
	MIP4 and NETLMM both are IETF WGs. The goal is to define PMIP4
protocol in IETF...so, as long as there is enough interest and support
to get the job done, the place should not matter very much.
	=20
	-Kuntal
	=20
=09
=09

________________________________

		From: Behcet Sarikaya [mailto:behcetsarikaya@yahoo.com]=20
		Sent: Tuesday, November 28, 2006 5:45 PM
		To: Chowdhury, Kuntal
		Cc: mip4@ietf.org
		Subject: Re: [Mip4] Proxy Mobile IPv4 in the WG charter
	=09
	=09
		I am neutral on PMIPv4 standardization, in fact may be
we should not.
		Since netlmm WG from the beginning has not ruled out a
v4 solution and since netlmm WG decided to do PMIPv6, it seems logical
that netlmm does PMIPv4 as well. Is there a problem with that?

		=20

		--behcet



		----- Original Message ----
		From: "Chowdhury, Kuntal"
<kchowdhury@starentnetworks.com>
		To: Kent Leung (kleung) <kleung@cisco.com>; Alexandru
Petrescu <alexandru.petrescu@motorola.com>; "Narayanan, Vidya"
<vidyan@qualcomm.com>
		Cc: mip4@ietf.org
		Sent: Tuesday, November 28, 2006 4:09:37 PM
		Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG charter
	=09
	=09
		Hi Kent,
	=09
		Thanks for bringing this up. I support standardization
of PMIP4 in IETF.
		This is the only way we can make sure that a single
PMIP4 protocol is
		used across all SDOs. There is sufficient industry
traction on PMIP4,
		therefore it should be included in the MIP4 WG charter.
	=09
		-Kuntal
	=09
	=09
		> -----Original Message-----
		> From: Kent Leung (kleung) [mailto:kleung@cisco.com]=20
		> Sent: Tuesday, November 28, 2006 2:25 PM
		> To: Alexandru Petrescu; Narayanan, Vidya
		> Cc: mip4@ietf.org
		> Subject: RE: [Mip4] Proxy Mobile IPv4 in the WG
charter
		>=20
		> Hi Alex.  WiMAX supports both client MIPv4 and proxy
MIPv4=20
		> modes.  I prefer to keep the discussion focused on the
need=20
		> to standardize MIPv4 in proxy mode in IETF.  I believe
it=20
		> would be highly valuable specification and has
potential=20
		> widespread use.
		>=20
		> Kent=20
		>=20
		> -----Original Message-----
		> From: Alexandru Petrescu
[mailto:alexandru.petrescu@motorola.com]
		> Sent: Tuesday, November 21, 2006 9:51 AM
		> To: Narayanan, Vidya
		> Cc: Kent Leung (kleung); mip4@ietf.org
		> Subject: Re: [Mip4] Proxy Mobile IPv4 in the WG
charter
		>=20
		> Narayanan, Vidya wrote:
		> > Hi Kent, If NETLMM supported IPv4 endpoints, do we
still need a=20
		> > standardized PMIPv4 solution?
		>=20
		> Not sure what NETLMM is, or whether it supported IPv4
endpoints.
		>=20
		> The other question is whether the known FA mode of
MIP4 can=20
		> figure as a candidate for what WiMax nominates as
Proxy MIP,=20
		> and the CCoA mode as what WiMax nominates Client MIP.
		>=20
		> Alex
		>=20
		> > Or, is this an effort to document what has been
already deployed?
		> >=20
		> > Regards, Vidya
		> >=20
		> >=20
		>
----------------------------------------------------------------------
		> > --
		> >  *From:* Kent Leung (kleung)
[mailto:kleung@cisco.com]=20
		> *Sent:* Friday,
		>=20
		> > November 17, 2006 9:52 AM *To:* mip4@ietf.org
*Subject:*=20
		> [Mip4] Proxy=20
		> > Mobile IPv4 in the WG charter
		> >=20
		> > Hi.  The draft-leung-mip4-proxy-mode-01.txt draft
describes using=20
		> > Mobile IPv4 in proxy mode to provide network-based
mobility=20
		> > management.  There will need to be some more work on
the draft. But=20
		> > wanted to get some sense of support for Proxy Mobile
IPv4=20
		> in this WG.
		>=20
		> > Certainly there are a few SDOs which have either
adopted or=20
		> interested
		>=20
		> > in such mechanism.
		> >=20
		> > Do folks want to take this on as a WG item
eventually?
		> >=20
		> > Kent
		> >=20
		>=20
		> --
		> Mip4 mailing list: Mip4@ietf.org
		>     Web interface:
https://www1.ietf.org/mailman/listinfo/mip4
		>      Charter page:
http://www.ietf.org/html.charters/mip4-charter.html
		> Supplemental site: http://www.mip4.org/
		>=20
	=09
		--
		Mip4 mailing list: Mip4@ietf.org
		    Web interface:
https://www1.ietf.org/mailman/listinfo/mip4
		     Charter page:
http://www.ietf.org/html.charters/mip4-charter.html
		Supplemental site: http://www.mip4.org/



------_=_NextPart_001_01C713D1.CE4CD631
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<STYLE type=3Dtext/css>DIV {
	MARGIN: 0px
}
</STYLE>

<META content=3D"MSHTML 6.00.2900.2995" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D409170616-29112006><FONT =
color=3D#0000ff=20
size=3D2>I think it makes sense to develop a specification for the =
operation of=20
PMIPv4. It would help interoperability.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D409170616-29112006><FONT =
color=3D#0000ff=20
size=3D2>If&nbsp; I am a service provider I would like my network to =
work with=20
both CMIPv4 hosts as well as hosts without CMIPv4. If a proxy is =
involved to=20
provide such a transparency then it helps to understand the operations =
of such a=20
proxy agent and its location and its interaction if any with the host =
for which=20
it is acting as a proxy and its interaction with other elements of the =
MIPv4=20
infrastructure and&nbsp;its configuration and management aspects.=20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D409170616-29112006><FONT =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D409170616-29112006><FONT =
color=3D#0000ff=20
size=3D2>I am neutral to whether the work should be&nbsp;done in MIPv4 =
WG or=20
netLMM&nbsp; WG.</FONT></SPAN></DIV>
<DIV><FONT color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3D"Curlz MT" size=3D2><EM>- Satya =
Rao</EM></FONT></DIV>
<DIV align=3Dleft><FONT size=3D2>Mobile Devices Technology =
Office</FONT></DIV>
<DIV align=3Dleft><FONT size=3D2>Motorola</FONT></DIV>
<DIV align=3Dleft><FONT size=3D2>Tel: 512-427-7335</FONT></DIV>
<DIV align=3Dleft><FONT size=3D2>Email: </FONT><A=20
href=3D"mailto:sbrao@motorola.com"><FONT=20
size=3D2>sbrao@motorola.com</FONT></A></DIV>
<DIV>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Chowdhury, Kuntal=20
  [mailto:kchowdhury@starentnetworks.com] <BR><B>Sent:</B> Wednesday, =
November=20
  29, 2006 12:56 AM<BR><B>To:</B> Behcet Sarikaya<BR><B>Cc:</B>=20
  mip4@ietf.org<BR><B>Subject:</B> RE: [Mip4] Proxy Mobile IPv4 in the =
WG=20
  charter<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D775104906-29112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Behcet,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D775104906-29112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D775104906-29112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>I am not clear on what you meant by "in fact =
may be we=20
  should not". We should not what? Please clarify.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D775104906-29112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D775104906-29112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>MIP4 and NETLMM both are IETF WGs. The goal =
is to define=20
  PMIP4 protocol in IETF...so, as long as there is enough interest and =
support=20
  to get the job done, the place should not matter very=20
much.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D775104906-29112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D775104906-29112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>-Kuntal</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D775104906-29112006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> Behcet Sarikaya=20
    [mailto:behcetsarikaya@yahoo.com] <BR><B>Sent:</B> Tuesday, November =
28,=20
    2006 5:45 PM<BR><B>To:</B> Chowdhury, Kuntal<BR><B>Cc:</B>=20
    mip4@ietf.org<BR><B>Subject:</B> Re: [Mip4] Proxy Mobile IPv4 in the =
WG=20
    charter<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, =
times, serif">
    <DIV=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, =
times, serif"><FONT=20
    color=3D#6000bf>I am neutral on PMIPv4 standardization, in fact may =
be we=20
    should not.</FONT></DIV>
    <DIV=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, =
times, serif"><FONT=20
    color=3D#6000bf>Since netlmm WG from the beginning has <STRONG>not=20
    </STRONG>ruled out a v4 solution and since netlmm WG decided to do =
PMIPv6,=20
    it seems logical that netlmm does PMIPv4 as well. Is there a problem =
with=20
    that?</FONT></DIV>
    <P><FONT color=3D#6000bf></FONT>&nbsp;</P>
    <P><FONT color=3D#6000bf>--behcet</P>
    <DIV=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, =
times, serif"><BR></FONT><BR></DIV>
    <DIV=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, =
times, serif">-----=20
    Original Message ----<BR>From: "Chowdhury, Kuntal"=20
    &lt;kchowdhury@starentnetworks.com&gt;<BR>To: Kent Leung (kleung)=20
    &lt;kleung@cisco.com&gt;; Alexandru Petrescu=20
    &lt;alexandru.petrescu@motorola.com&gt;; "Narayanan, Vidya"=20
    &lt;vidyan@qualcomm.com&gt;<BR>Cc: mip4@ietf.org<BR>Sent: Tuesday, =
November=20
    28, 2006 4:09:37 PM<BR>Subject: RE: [Mip4] Proxy Mobile IPv4 in the =
WG=20
    charter<BR><BR>
    <DIV>Hi Kent,<BR><BR>Thanks for bringing this up. I support =
standardization=20
    of PMIP4 in IETF.<BR>This is the only way we can make sure that a =
single=20
    PMIP4 protocol is<BR>used across all SDOs. There is sufficient =
industry=20
    traction on PMIP4,<BR>therefore it should be included in the MIP4 WG =

    charter.<BR><BR>-Kuntal<BR><BR><BR>&gt; -----Original =
Message-----<BR>&gt;=20
    From: Kent Leung (kleung) [mailto:kleung@cisco.com] <BR>&gt; Sent: =
Tuesday,=20
    November 28, 2006 2:25 PM<BR>&gt; To: Alexandru Petrescu; Narayanan, =

    Vidya<BR>&gt; Cc: mip4@ietf.org<BR>&gt; Subject: RE: [Mip4] Proxy =
Mobile=20
    IPv4 in the WG charter<BR>&gt; <BR>&gt; Hi Alex.&nbsp;&nbsp;WiMAX =
supports=20
    both client MIPv4 and proxy MIPv4 <BR>&gt; modes.&nbsp;&nbsp;I =
prefer to=20
    keep the discussion focused on the need <BR>&gt; to standardize =
MIPv4 in=20
    proxy mode in IETF.&nbsp;&nbsp;I believe it <BR>&gt; would be highly =

    valuable specification and has potential <BR>&gt; widespread =
use.<BR>&gt;=20
    <BR>&gt; Kent <BR>&gt; <BR>&gt; -----Original Message-----<BR>&gt; =
From:=20
    Alexandru Petrescu [mailto:alexandru.petrescu@motorola.com]<BR>&gt; =
Sent:=20
    Tuesday, November 21, 2006 9:51 AM<BR>&gt; To: Narayanan, =
Vidya<BR>&gt; Cc:=20
    Kent Leung (kleung); mip4@ietf.org<BR>&gt; Subject: Re: [Mip4] Proxy =
Mobile=20
    IPv4 in the WG charter<BR>&gt; <BR>&gt; Narayanan, Vidya =
wrote:<BR>&gt; &gt;=20
    Hi Kent, If NETLMM supported IPv4 endpoints, do we still need a =
<BR>&gt;=20
    &gt; standardized PMIPv4 solution?<BR>&gt; <BR>&gt; Not sure what =
NETLMM is,=20
    or whether it supported IPv4 endpoints.<BR>&gt; <BR>&gt; The other =
question=20
    is whether the known FA mode of MIP4 can <BR>&gt; figure as a =
candidate for=20
    what WiMax nominates as Proxy MIP, <BR>&gt; and the CCoA mode as =
what WiMax=20
    nominates Client MIP.<BR>&gt; <BR>&gt; Alex<BR>&gt; <BR>&gt; &gt; =
Or, is=20
    this an effort to document what has been already deployed?<BR>&gt; =
&gt;=20
    <BR>&gt; &gt; Regards, Vidya<BR>&gt; &gt; <BR>&gt; &gt; <BR>&gt;=20
    =
----------------------------------------------------------------------<BR=
>&gt;=20
    &gt; --<BR>&gt; &gt;&nbsp;&nbsp;*From:* Kent Leung (kleung)=20
    [mailto:kleung@cisco.com] <BR>&gt; *Sent:* Friday,<BR>&gt; <BR>&gt; =
&gt;=20
    November 17, 2006 9:52 AM *To:* mip4@ietf.org *Subject:* <BR>&gt; =
[Mip4]=20
    Proxy <BR>&gt; &gt; Mobile IPv4 in the WG charter<BR>&gt; &gt; =
<BR>&gt; &gt;=20
    Hi.&nbsp;&nbsp;The draft-leung-mip4-proxy-mode-01.txt draft =
describes using=20
    <BR>&gt; &gt; Mobile IPv4 in proxy mode to provide network-based =
mobility=20
    <BR>&gt; &gt; management.&nbsp;&nbsp;There will need to be some more =
work on=20
    the draft. But <BR>&gt; &gt; wanted to get some sense of support for =
Proxy=20
    Mobile IPv4 <BR>&gt; in this WG.<BR>&gt; <BR>&gt; &gt; Certainly =
there are a=20
    few SDOs which have either adopted or <BR>&gt; interested<BR>&gt; =
<BR>&gt;=20
    &gt; in such mechanism.<BR>&gt; &gt; <BR>&gt; &gt; Do folks want to =
take=20
    this on as a WG item eventually?<BR>&gt; &gt; <BR>&gt; &gt; =
Kent<BR>&gt;=20
    &gt; <BR>&gt; <BR>&gt; --<BR>&gt; Mip4 mailing list:=20
    Mip4@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Web interface: <A=20
    href=3D"https://www1.ietf.org/mailman/listinfo/mip4"=20
    =
target=3D_blank>https://www1.ietf.org/mailman/listinfo/mip4</A><BR>&gt;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Charter=20
    page: <A =
href=3D"http://www.ietf.org/html.charters/mip4-charter.html"=20
    =
target=3D_blank>http://www.ietf.org/html.charters/mip4-charter.html</A><B=
R>&gt;=20
    Supplemental site: <A href=3D"http://www.mip4.org/"=20
    target=3D_blank>http://www.mip4.org/</A><BR>&gt; <BR><BR>--<BR>Mip4 =
mailing=20
    list: Mip4@ietf.org<BR>&nbsp;&nbsp;&nbsp;&nbsp;Web interface: <A=20
    href=3D"https://www1.ietf.org/mailman/listinfo/mip4"=20
    =
target=3D_blank>https://www1.ietf.org/mailman/listinfo/mip4</A><BR>&nbsp;=
&nbsp;&nbsp;&nbsp;=20
    Charter page: <A =
href=3D"http://www.ietf.org/html.charters/mip4-charter.html"=20
    =
target=3D_blank>http://www.ietf.org/html.charters/mip4-charter.html</A><B=
R>Supplemental=20
    site: <A href=3D"http://www.mip4.org/"=20
    target=3D_blank>http://www.mip4.org/</A></DIV></DIV>
    <DIV=20
    style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, =
times, serif"><BR></DIV></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C713D1.CE4CD631--


--===============0346285065==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0346285065==--




From mip4-bounces@ietf.org Thu Nov 30 14:50:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GprvK-0006e7-OM; Thu, 30 Nov 2006 14:50:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GomS0-0000HU-5C
	for mip4@ietf.org; Mon, 27 Nov 2006 14:47:36 -0500
Received: from pcvs68.informatik.uni-stuttgart.de ([129.69.210.138])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GomRx-0001T9-N5
	for mip4@ietf.org; Mon, 27 Nov 2006 14:47:36 -0500
Received: from pcvs68.informatik.uni-stuttgart.de (localhost [127.0.0.1])
	by pcvs68.informatik.uni-stuttgart.de (8.13.6/8.13.6) with ESMTP id
	kARK5ecw016908 for <mip4@ietf.org>; Mon, 27 Nov 2006 21:05:40 +0100
Received: (from pjmarron@localhost)
	by pcvs68.informatik.uni-stuttgart.de (8.13.7/8.13.7/Submit) id
	kARK5eaG016904 for mip4@ietf.org; Mon, 27 Nov 2006 21:05:40 +0100
Date: Mon, 27 Nov 2006 21:05:40 +0100
Message-Id: <200611272005.kARK5eaG016904@pcvs68.informatik.uni-stuttgart.de>
To: mip4@ietf.org
From: marronpo@informatik.uni-stuttgart.de
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
X-Mailman-Approved-At: Thu, 30 Nov 2006 14:50:21 -0500
Subject: [Mip4] CFP: 4th European conference on Wireless Sensor Networks
	(EWSN 2007)
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

[Apologies if you receive multiple copies of this call]

========================================================================

Due to several requests the POSTER SUBMISSION DEADLINE is *EXTENDED* to 

     DECEMBER 11, 2006 (23:59 Delft local time; 17:59 EST)

========================================================================

CALL FOR POSTERS AND DEMONSTRATIONS

4th European conference on Wireless Sensor Networks (EWSN 2007)
Delft University of Technology, The Netherlands
January 29-31, 2007

http://www.ewsn.org

========================================================================

POSTERS and DEMONSTRATIONS

The poster session will provide a forum for researchers to showcase
their work and obtain feedback on ongoing research from knowledgeable
conference attendees. A poster presentation can also be accompanied by
a demonstration to illustrate an application, technology, or platform.

========================================================================

Poster and demo proposals must be submitted as a PDF file with no more
than 2 pages containing an abstract describing the research content
presented in the poster or demonstration, along with title, authors,
institutional affiliations, and contact information. The title of
poster proposals should be prefixed by "Poster Abstract:", while the
title of demonstration proposals should be prefixed by "Demo Abstract:".

Submissions must conform to the IEEE Transactions style with a 10pt
font formatted for A4 paper (use the a4paper option) and without page
numbers.  Please submit your poster proposal as a PDF E-mail
attachment to

posters@ewsn.ewi.tudelft.nl

with the subject line reading "EWSN Poster Submission" before the
deadline (Dec 11, 2006).

We will adopt a simplified review process for poster and demo
proposals. The abstracts of accepted proposals will be published in
the EWSN 2007 adjunct proceedings.


IMPORTANT DATES

Posters/Demonstrations:
Submission deadline:		Dec  11, 2006 (23:59 Delft local time; 17:59 EST)
Notification of acceptance: 	Dec 15, 2006
Camera-ready version:		Jan  8, 2007

Conference dates:		Jan 29-31, 2007


PROGRAM COMMITTEE

Koen Langendoen, Delft Univ. of Technology	(CO-CHAIR)
Thiemo Voigt, SICS				(CO-CHAIR)

Tarek Abdelzaher, Univ. of Illinois at Urbana Champaign
Michael Beigl, TU Braunschweig
Jan Beutel, ETH Zurich
Athanassios Boulis, National ICT Australia (NICTA)
Torsten Braun, Univ. of Bern
Rebecca Braynard, Duke Univ.
Nirupama Bulusu, Portland State Univ.
Srdjan Capkun, ETH Zurich
Mun Choon Chan, National Univ. of Singapore
Maarten Ditzel, TNO
Jean-Pierre Ebert, IHP microelectronics
Carlo Fischione, KTH Stockholm
Vipin Gopal, United Technologies Research Center
Takahiro Hara, Osaka Univ.
Paul Havinga, Univ. of Twente
Mike Hazas, Lancaster Univ.
Wendi Heinzelman, Univ. of Rochester
Holger Karl, Univ. of Paderborn
Bhaskar Krishnamachari, Univ. of Southern California
Chenyang Lu, Washington Univ. in St. Louis
Pedro J. Marron, Univ. of Stuttgart
Amy L. Murphy, Univ. of Lugano
Chiara Petrioli, Univ. La Sapienza Rome
Marcelo Pias, Univ. of Cambridge
Hartmut Ritter, FU Berlin
Utz Roedig, Univ. College Cork
Christian Rohner, Uppsala Univ.
Kay Roemer, ETH Zurich
Andreas Savvides, Yale
Klaus Wehrle, RWTH Aachen
Dirk Westhoff, NEC
Andreas Willig, TU Berlin
Adam Wolisz, TU Berlin
Wei Ye, USC/ISI

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



