From mailman-bounces@core3.amsl.com  Fri Feb  1 05:34:50 2008
Return-Path: <mailman-bounces@core3.amsl.com>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CBFB328CF5C
	for <ietfarch-mip4-archive@core3.amsl.com>; Fri,  1 Feb 2008 05:34:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level: 
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[AWL=0.010,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4X6KI+Cyfn68 for <ietfarch-mip4-archive@core3.amsl.com>;
	Fri,  1 Feb 2008 05:34:17 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6D45428D3F0
	for <mip4-archive@optimus.ietf.org>; Fri,  1 Feb 2008 05:08:37 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: mip4-archive@optimus.ietf.org
X-No-Archive: yes
Message-ID: <mailman.12138.1201870985.31726.mailman@core3.amsl.com>
Date: Fri, 01 Feb 2008 05:03:05 -0800
Precedence: bulk
X-BeenThere: mailman@core3.amsl.com
X-Mailman-Version: 2.1.9
List-Id: <mailman.core3.amsl.com>
X-List-Administrivia: yes
Sender: mailman-bounces@core3.amsl.com
Errors-To: mailman-bounces@core3.amsl.com

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

http://www.ietf.org/mailman/options/mip4/mip4-archive%40optimus.ietf.org
From mailman-bounces@core3.amsl.com  Fri Feb  1 05:35:27 2008
Return-Path: <mailman-bounces@core3.amsl.com>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 005BF294A9F
	for <ietfarch-mip4-archive@core3.amsl.com>; Fri,  1 Feb 2008 05:34:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level: 
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[AWL=0.010,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tWmFHdp3V4T8 for <ietfarch-mip4-archive@core3.amsl.com>;
	Fri,  1 Feb 2008 05:34:33 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B9BC22958DA
	for <mip4-archive@optimus.ietf.org>; Fri,  1 Feb 2008 05:08:50 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: mip4-archive@optimus.ietf.org
X-No-Archive: yes
Message-ID: <mailman.12138.1201870986.31733.mailman@core3.amsl.com>
Date: Fri, 01 Feb 2008 05:03:06 -0800
Precedence: bulk
X-BeenThere: mailman@core3.amsl.com
X-Mailman-Version: 2.1.9
List-Id: <mailman.core3.amsl.com>
X-List-Administrivia: yes
Sender: mailman-bounces@core3.amsl.com
Errors-To: mailman-bounces@core3.amsl.com

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

http://www.ietf.org/mailman/options/mip4/mip4-archive%40optimus.ietf.org
From mip4-bounces@ietf.org  Fri Feb  1 10:37:10 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EFE6C28C4D4;
	Fri,  1 Feb 2008 10:37:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.041
X-Spam-Level: 
X-Spam-Status: No, score=-2.041 tagged_above=-999 required=5 tests=[AWL=0.558,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bUe0mJGAwKXQ; Fri,  1 Feb 2008 10:37:10 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4CD9228C46B;
	Fri,  1 Feb 2008 10:37:07 -0800 (PST)
X-Original-To: mip4@ietf.org
Delivered-To: mip4@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 6E0A73A683D; Fri,  1 Feb 2008 10:36:56 -0800 (PST)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080201183656.6E0A73A683D@core3.amsl.com>
Date: Fri,  1 Feb 2008 10:36:56 -0800 (PST)
Cc: mip4@ietf.org
Subject: [Mip4] I-D
	Action:draft-ietf-mip4-generic-notification-message-03.txt
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobility for IPv4 Working Group of the IETF.


	Title           : Generic Notification Message for Mobile IPv4
	Author(s)       : H. Deng, et al.
	Filename        : draft-ietf-mip4-generic-notification-message-03.txt
	Pages           : 25
	Date            : 2008-02-01

This document specifies protocol enhancements that allow Mobile IPv4
entities to send and receive explicit notification messages using a
new Mobile IPv4 message type designed for this purpose.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip4-generic-notification-message-03.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-mip4-generic-notification-message-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mip4-generic-notification-message-03.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2008-02-01082258.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip4-generic-notification-message-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mip4-generic-notification-message-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-02-01082258.I-D\@ietf.org>


--OtherAccess--

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

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

--NextPart--



From mip4-bounces@ietf.org  Sat Feb  2 05:29:36 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 98CFD28C6FB;
	Sat,  2 Feb 2008 05:29:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.571
X-Spam-Level: **
X-Spam-Status: No, score=2.571 tagged_above=-999 required=5 tests=[AWL=-0.463,
	BAYES_40=-0.185, HTML_MESSAGE=1, TVD_SPACE_RATIO=2.219]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qp8iaXBmdXtc; Sat,  2 Feb 2008 05:29:35 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 88A6528C6D5;
	Sat,  2 Feb 2008 05:29:35 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C8D7028C6C8
	for <mip4@core3.amsl.com>; Sat,  2 Feb 2008 05:29:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0RkVAfUtsRiA for <mip4@core3.amsl.com>;
	Sat,  2 Feb 2008 05:29:33 -0800 (PST)
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168])
	by core3.amsl.com (Postfix) with ESMTP id 61E7728C6E7
	for <mip4@ietf.org>; Sat,  2 Feb 2008 05:29:04 -0800 (PST)
Received: by ug-out-1314.google.com with SMTP id u2so2368001uge.46
	for <mip4@ietf.org>; Sat, 02 Feb 2008 05:30:40 -0800 (PST)
Received: by 10.67.196.2 with SMTP id y2mr6736721ugp.60.1201959040415;
	Sat, 02 Feb 2008 05:30:40 -0800 (PST)
Received: by 10.67.101.20 with HTTP; Sat, 2 Feb 2008 05:30:40 -0800 (PST)
Message-ID: <6c4d82cc0802020530s391cbc00xec3c7b75d70d4b06@mail.gmail.com>
Date: Sat, 2 Feb 2008 21:30:40 +0800
From: "te te" <testcfp@gmail.com>
To: mip4@ietf.org
MIME-Version: 1.0
Subject: [Mip4] hello!
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0991279236=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

--===============0991279236==
Content-Type: multipart/alternative; 
	boundary="----=_Part_28501_10829938.1201959040410"

------=_Part_28501_10829938.1201959040410
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

hello~!everybody!

------=_Part_28501_10829938.1201959040410
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

hello~!everybody!<br>

------=_Part_28501_10829938.1201959040410--

--===============0991279236==
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: http://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0991279236==--


From mip4-bounces@ietf.org  Tue Feb  5 13:53:46 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6411F3A9C5E;
	Tue,  5 Feb 2008 13:53:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.001
X-Spam-Level: **
X-Spam-Status: No, score=2.001 tagged_above=-999 required=5 tests=[AWL=0.666,
	BAYES_50=0.001, HTML_MESSAGE=1, IP_NOT_FRIENDLY=0.334]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MKSntlPT4IhV; Tue,  5 Feb 2008 13:53:46 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B85273A728C;
	Tue,  5 Feb 2008 13:42:41 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A07E3A6B79
	for <mip4@core3.amsl.com>; Tue,  5 Feb 2008 13:42:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4WhXTXGlW1Qb for <mip4@core3.amsl.com>;
	Tue,  5 Feb 2008 13:42:38 -0800 (PST)
Received: from n21b.bullet.mail.sp1.yahoo.com (n21b.bullet.mail.sp1.yahoo.com
	[69.147.65.253]) by core3.amsl.com (Postfix) with SMTP id 57C1B3A6EEA
	for <mip4@ietf.org>; Tue,  5 Feb 2008 13:24:34 -0800 (PST)
Received: from [216.252.122.216] by n21.bullet.sp1.yahoo.com with NNFMP;
	05 Feb 2008 20:20:21 -0000
Received: from [69.147.65.165] by t1.bullet.sp1.yahoo.com with NNFMP;
	05 Feb 2008 20:20:21 -0000
Received: from [127.0.0.1] by omp500.mail.sp1.yahoo.com with NNFMP;
	05 Feb 2008 20:20:21 -0000
X-Yahoo-Newman-Property: ymail-5
X-Yahoo-Newman-Id: 320225.88514.bm@omp500.mail.sp1.yahoo.com
Received: (qmail 68097 invoked by uid 60001); 5 Feb 2008 20:20:20 -0000
X-YMail-OSG: 8dzD3wkVM1nYuhMx55DP0I9Hah3.pupAN3TUt6w2
Received: from [168.223.21.216] by web45902.mail.sp1.yahoo.com via HTTP;
	Tue, 05 Feb 2008 12:20:20 PST
Date: Tue, 5 Feb 2008 12:20:20 -0800 (PST)
From: John Edward <jeedward@yahoo.com>
To: mip4@ietf.org
MIME-Version: 1.0
Message-ID: <672722.66551.qm@web45902.mail.sp1.yahoo.com>
Subject: [Mip4] Draft paper submission deadline is extended: HPCNCS-08
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0187245654=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

--===============0187245654==
Content-Type: multipart/alternative; boundary="0-225165930-1202242820=:66551"
Content-Transfer-Encoding: 8bit

--0-225165930-1202242820=:66551
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit


Dear Colleagues and Friends

 

Kindly share the announcement below with those who may be interested: thank you in advance.  

 

Sincerely

John Edward
   
  HPCNCS-08 Draft paper submission deadline is extended.
   
  The 2008 International Conference on High Performance Computing, Networking and Communication Systems (HPCNCS-08) (website: www.PromoteResearch.org ) will be held during July 7-10 2008 in Orlando, FL, USA. We invite draft paper submissions and the deadline is extended until February 19 2008 due to several requests from the authors.
   
  The conference will be held at the same time and place where several major events (please see below) are taking place. The website contains more details.
   
  Sincerely
  John Edward
   
  ·        International Conference on Artificial Intelligence and Pattern Recognition (AIPR-08) 
  ·        International Conference on Automation, Robotics and Control Systems (ARCS-08)
  ·        International Conference on Bioinformatics, Computational Biology, Genomics and Chemoinformatics (BCBGC-08)
  ·        International Conference on Enterprise Information Systems and Web Technologies (EISWT-08)
  ·        International Conference on High Performance Computing, Networking and Communication Systems (HPCNCS-08)
  ·        International Conference on Software Engineering Theory and Practice (SETP-08)  
  ·        International Conference on Theoretical and Mathematical Foundations of Computer Science (TMFCS-08)
   
   

       
---------------------------------
Looking for last minute shopping deals?  Find them fast with Yahoo! Search.
--0-225165930-1202242820=:66551
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<PRE><A name=OLE_LINK4></A><A name=OLE_LINK3><SPAN style="mso-bookmark: OLE_LINK4"><TT><SPAN style="COLOR: black; FONT-FAMILY: 'Times New Roman'; mso-ansi-font-size: 12.0pt; mso-bidi-font-size: 12.0pt"><FONT size=3>Dear Colleagues and Friends<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p></FONT></SPAN></TT></SPAN></A></PRE><PRE><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><TT><SPAN style="COLOR: black; FONT-FAMILY: 'Times New Roman'; mso-ansi-font-size: 12.0pt; mso-bidi-font-size: 12.0pt"><o:p><FONT size=3>&nbsp;</FONT></o:p></SPAN></TT></SPAN></SPAN></PRE><PRE><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><TT><SPAN style="COLOR: black; FONT-FAMILY: 'Times New Roman'; mso-ansi-font-size: 12.0pt; mso-bidi-font-size: 12.0pt"><FONT size=3>Kindly share the announcement below with those who may be interested: thank you in advance.<SPAN style="mso-spacerun: yes">&nbsp;
 </SPAN><o:p></o:p></FONT></SPAN></TT></SPAN></SPAN></PRE><PRE><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><TT><SPAN style="COLOR: black; FONT-FAMILY: 'Times New Roman'; mso-ansi-font-size: 12.0pt; mso-bidi-font-size: 12.0pt"><o:p><FONT size=3>&nbsp;</FONT></o:p></SPAN></TT></SPAN></SPAN></PRE><PRE><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><TT><SPAN style="COLOR: black; FONT-FAMILY: 'Times New Roman'; mso-ansi-font-size: 12.0pt; mso-bidi-font-size: 12.0pt"><FONT size=3>Sincerely<o:p></o:p></FONT></SPAN></TT></SPAN></SPAN></PRE><PRE><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><TT><SPAN style="COLOR: black; FONT-FAMILY: 'Times New Roman'; mso-ansi-font-size: 12.0pt; mso-bidi-font-size: 12.0pt"><FONT size=3>John Edward<o:p></o:p></FONT></SPAN></TT></SPAN></SPAN></PRE>  <div class=MsoNormal style="MARGIN: 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark:
 OLE_LINK4"><o:p><FONT face="Times New Roman" size=3>&nbsp;</FONT></o:p></SPAN></SPAN></div>  <div class=MsoNormal style="MARGIN: 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><FONT face="Times New Roman" size=3>HPCNCS-08 Draft paper submission deadline is extended.</FONT></SPAN></SPAN></div>  <div class=MsoNormal style="MARGIN: 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><o:p><FONT face="Times New Roman" size=3>&nbsp;</FONT></o:p></SPAN></SPAN></div>  <div class=MsoNormal style="MARGIN: 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><FONT face="Times New Roman" size=3>The 2008 International Conference on High Performance Computing, Networking and Communication Systems (HPCNCS-08) (website: </FONT></SPAN></SPAN><A href="http://www.promoteresearch.org/"><FONT face="Times New Roman"><FONT size=3><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark:
 OLE_LINK4">www.PromoteResearch.org</SPAN></SPAN><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"></SPAN></SPAN></FONT></FONT></A><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><FONT face="Times New Roman" size=3> ) will be held during July 7-10 2008 in <?xml:namespace prefix = st1 ns = "urn:schemas-microsoft-com:office:smarttags" /><st1:place w:st="on"><st1:City w:st="on">Orlando</st1:City>, <st1:State w:st="on">FL</st1:State>, <st1:country-region w:st="on">USA</st1:country-region></st1:place>. We invite draft paper submissions and the deadline is extended until February 19 2008 due to several requests from the authors.</FONT></SPAN></SPAN></div>  <div class=MsoNormal style="MARGIN: 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><o:p><FONT face="Times New Roman" size=3>&nbsp;</FONT></o:p></SPAN></SPAN></div>  <div class=MsoNormal style="MARGIN: 0pt"><SPAN style="mso-bookmark:
 OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><FONT face="Times New Roman" size=3>The conference will be held at the same time and place where several major events (please see below) are taking place. The website contains more details.</FONT></SPAN></SPAN></div>  <div class=MsoNormal style="MARGIN: 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><o:p><FONT face="Times New Roman" size=3>&nbsp;</FONT></o:p></SPAN></SPAN></div>  <div class=MsoNormal style="MARGIN: 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><FONT face="Times New Roman" size=3>Sincerely</FONT></SPAN></SPAN></div>  <div class=MsoNormal style="MARGIN: 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><FONT face="Times New Roman" size=3>John Edward</FONT></SPAN></SPAN></div><SPAN style="mso-bookmark: OLE_LINK4"></SPAN><SPAN style="mso-bookmark: OLE_LINK3"></SPAN>  <div class=MsoNormal style="MARGIN:
 0pt"><o:p><FONT face="Times New Roman" size=3>&nbsp;</FONT></o:p></div>  <div style="MARGIN-LEFT: 31.5pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1"><SPAN style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style="mso-list: Ignore"><FONT size=3>·</FONT><SPAN style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPAN><FONT face="Times New Roman" size=3>International Conference on Artificial Intelligence and Pattern Recognition (AIPR-08) </FONT></div>  <div style="MARGIN-LEFT: 31.5pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1"><SPAN style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style="mso-list: Ignore"><FONT size=3>·</FONT><SPAN style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPAN><FONT face="Times New Roman" size=3>International Conference on Automation, Robotics and Control Systems
 (ARCS-08)</FONT></div>  <div style="MARGIN-LEFT: 31.5pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1"><SPAN style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style="mso-list: Ignore"><FONT size=3>·</FONT><SPAN style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPAN><FONT face="Times New Roman" size=3>International Conference on Bioinformatics, Computational Biology, Genomics and Chemoinformatics (BCBGC-08)</FONT></div>  <div style="MARGIN-LEFT: 31.5pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1"><SPAN style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style="mso-list: Ignore"><FONT size=3>·</FONT><SPAN style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPAN><FONT face="Times New Roman" size=3>International Conference on <st1:City w:st="on"><st1:place
 w:st="on">Enterprise</st1:place></st1:City> Information Systems and Web Technologies (EISWT-08)</FONT></div>  <div style="MARGIN-LEFT: 31.5pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1"><SPAN style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style="mso-list: Ignore"><FONT size=3>·</FONT><SPAN style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPAN><FONT face="Times New Roman" size=3>International Conference on High Performance Computing, Networking and Communication Systems (HPCNCS-08)</FONT></div>  <div style="MARGIN-LEFT: 31.5pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1"><SPAN style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style="mso-list: Ignore"><FONT size=3>·</FONT><SPAN style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPAN><FONT face="Times New Roman"><FONT size=3><SPAN
 style="COLOR: black">International Conference on Software Engineering Theory and Practice (SETP-08) </SPAN><SPAN style="mso-spacerun: yes">&nbsp;</SPAN></FONT></FONT></div>  <div style="MARGIN-LEFT: 31.5pt; TEXT-INDENT: -18pt; mso-list: l0 level1 lfo1"><SPAN style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style="mso-list: Ignore"><FONT size=3>·</FONT><SPAN style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPAN><FONT face="Times New Roman" size=3>International Conference on Theoretical and Mathematical Foundations of Computer Science (TMFCS-08)</FONT></div>  <div class=MsoNormal style="MARGIN: 0pt"><o:p><FONT face="Times New Roman" size=3>&nbsp;</FONT></o:p></div>  <div class=MsoNormal style="MARGIN: 0pt"><o:p><FONT face="Times New Roman" size=3>&nbsp;</FONT></o:p></div><p>&#32;
      <hr size=1>Looking for last minute shopping deals? <a href="http://us.rd.yahoo.com/evt=51734/*http://tools.search.yahoo.com/newsearch/category.php?category=shopping"> 
Find them fast with Yahoo! Search.</a>
--0-225165930-1202242820=:66551--


--===============0187245654==
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: http://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0187245654==--



From mip4-bounces@ietf.org  Wed Feb  6 05:52:33 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8AD783A6DC2;
	Wed,  6 Feb 2008 05:52:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.505
X-Spam-Level: 
X-Spam-Status: No, score=-2.505 tagged_above=-999 required=5 tests=[AWL=0.745,
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RyMXjU7f0E7J; Wed,  6 Feb 2008 05:52:32 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CAFE23A6CB0;
	Wed,  6 Feb 2008 05:52:32 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5BFAA3A6CE0
	for <mip4@core3.amsl.com>; Wed,  6 Feb 2008 05:52:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id y-3kAAR4dl3G for <mip4@core3.amsl.com>;
	Wed,  6 Feb 2008 05:52:31 -0800 (PST)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 89CF03A69EC
	for <mip4@ietf.org>; Wed,  6 Feb 2008 05:52:31 -0800 (PST)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	5A2B22155D; Wed,  6 Feb 2008 14:54:02 +0100 (CET)
X-AuditID: c1b4fb3e-abdeabb0000007e1-2a-47a9bbfae152
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	462FE21529; Wed,  6 Feb 2008 14:54:02 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 6 Feb 2008 14:54:01 +0100
Received: from [147.214.22.209] ([147.214.22.209]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 6 Feb 2008 14:54:01 +0100
Message-ID: <47A9BBF9.5000201@ericsson.com>
Date: Wed, 06 Feb 2008 14:54:01 +0100
From: Henrik Levkowetz <henrik.levkowetz@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: MIP4 Mailing list <mip4@ietf.org>
X-Enigmail-Version: 0.95.6
X-OriginalArrivalTime: 06 Feb 2008 13:54:01.0536 (UTC)
	FILETIME=[BA6A2C00:01C868C7]
X-Brightmail-Tracker: AAAAAA==
Subject: [Mip4] Shepherd writeup for draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi,


I'm currently doing the document shepherd writeup for this draft.

My impression is that all issues raised during the WG last call
has been addressed in -05; if this is not the case, please speak
up now.


Best,

	Henrik
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb  6 06:15:03 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 96D8D3A6E36;
	Wed,  6 Feb 2008 06:15:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id L1fm3o72SODd; Wed,  6 Feb 2008 06:15:02 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7FA8D3A6E2A;
	Wed,  6 Feb 2008 06:15:02 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9953C3A6E2A
	for <mip4@core3.amsl.com>; Wed,  6 Feb 2008 06:15:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UHvZlCCka8Gm for <mip4@core3.amsl.com>;
	Wed,  6 Feb 2008 06:15:00 -0800 (PST)
Received: from mail153.messagelabs.com (mail153.messagelabs.com
	[216.82.253.51]) by core3.amsl.com (Postfix) with SMTP id B76AC3A6E08
	for <mip4@ietf.org>; Wed,  6 Feb 2008 06:15:00 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-2.tower-153.messagelabs.com!1202307391!10025063!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [144.189.100.102]
Received: (qmail 31083 invoked from network); 6 Feb 2008 14:16:31 -0000
Received: from motgate4.mot.com (HELO motgate4.mot.com) (144.189.100.102)
	by server-2.tower-153.messagelabs.com with SMTP;
	6 Feb 2008 14:16:31 -0000
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate4.mot.com (8.12.11/Motorola) with ESMTP id m16EGVR4018735;
	Wed, 6 Feb 2008 07:16:31 -0700 (MST)
Received: from az10vts04.mot.com (az10vts04.mot.com [10.64.251.245])
	by az33exr03.mot.com (8.13.1/Vontu) with SMTP id m16EGUkV007953;
	Wed, 6 Feb 2008 08:16:30 -0600 (CST)
Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id m16EGRar007874;
	Wed, 6 Feb 2008 08:16:28 -0600 (CST)
Message-ID: <47A9C136.9020905@gmail.com>
Date: Wed, 06 Feb 2008 15:16:22 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Henrik Levkowetz <henrik.levkowetz@ericsson.com>
References: <47A9BBF9.5000201@ericsson.com>
In-Reply-To: <47A9BBF9.5000201@ericsson.com>
X-Antivirus: avast! (VPS 080205-0, 05/02/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
Cc: MIP4 Mailing list <mip4@ietf.org>
Subject: Re: [Mip4] Shepherd writeup for draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Henrik Levkowetz wrote:
> Hi,
> 
> 
> I'm currently doing the document shepherd writeup for this draft.
> 
> My impression is that all issues raised during the WG last call has 
> been addressed in -05; if this is not the case, please speak up now.

Well, since you ask - I do support this draft.

There's however a security nit that I've tried to discuss several times
in both DSMIPv4 and DSMIPv6 contexts, if I remember correctly.  Those
two protocols don't seem to use a Prefix Table at HA but do use NEMO
extensions (prefixes in reg/bu messages).  This may have some security
issues: how is HA sure that the IPv6 prefix it received in a RegReq is
allowed for this Mobile Router?  An attacker MR could put the prefix of
a legitimate MR in there and obtain its traffic.

But frankly speaking I don't remember the conclusions of our prior
discussions on this topic.  If that was agreed at that time then I don't
oppose.  If we need to discuss it further we can start with the
following textual nit:

draft-ietf-mip4-dsmipv4-05.txt:
> 5.  Security Considerations
> 
> This specification operates in the security constraints and 
> requirements of [RFC3344].  It extends the operations defined in 
> [RFC3344] for IPv4 home addresses to cover home IPv6 addresses 
> prefixes [...]

Addresses _and_ prefixes?  Addressed prefixes?  Or?

Alex


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb  6 07:45:51 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 557483A6F6E;
	Wed,  6 Feb 2008 07:45:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gpOL-4U4fnMp; Wed,  6 Feb 2008 07:45:47 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6B4DF3A6E59;
	Wed,  6 Feb 2008 07:45:47 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 021213A6E59
	for <mip4@core3.amsl.com>; Wed,  6 Feb 2008 07:45:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9TpXBdSQkjdy for <mip4@core3.amsl.com>;
	Wed,  6 Feb 2008 07:45:46 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id F03D33A6C06
	for <mip4@ietf.org>; Wed,  6 Feb 2008 07:45:45 -0800 (PST)
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 06 Feb 2008 07:47:18 -0800
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m16FlIQI014798; 
	Wed, 6 Feb 2008 07:47:18 -0800
Received: from irp-view13.cisco.com (irp-view13.cisco.com [171.70.120.60])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id m16FlHHk001269;
	Wed, 6 Feb 2008 15:47:17 GMT
Date: Wed, 6 Feb 2008 07:47:17 -0800 (PST)
From: Sri Gundavelli <sgundave@cisco.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
In-Reply-To: <47A9C136.9020905@gmail.com>
Message-ID: <Pine.GSO.4.63.0802060743170.27313@irp-view13.cisco.com>
References: <47A9BBF9.5000201@ericsson.com> <47A9C136.9020905@gmail.com>
MIME-Version: 1.0
Authentication-Results: sj-dkim-1; header.From=sgundave@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: Henrik Levkowetz <henrik.levkowetz@ericsson.com>,
	MIP4 Mailing list <mip4@ietf.org>
Subject: Re: [Mip4] Shepherd writeup for draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org



On Wed, 6 Feb 2008, Alexandru Petrescu wrote:

> Henrik Levkowetz wrote:
>> Hi,
>>
>>
>> I'm currently doing the document shepherd writeup for this draft.
>>
>> My impression is that all issues raised during the WG last call has
>> been addressed in -05; if this is not the case, please speak up now.
>
> Well, since you ask - I do support this draft.
>
> There's however a security nit that I've tried to discuss several times
> in both DSMIPv4 and DSMIPv6 contexts, if I remember correctly.  Those
> two protocols don't seem to use a Prefix Table at HA but do use NEMO
> extensions (prefixes in reg/bu messages).  This may have some security
> issues: how is HA sure that the IPv6 prefix it received in a RegReq is
> allowed for this Mobile Router?  An attacker MR could put the prefix of
> a legitimate MR in there and obtain its traffic.
>


I agree, prefix authorization is required. The draft needs to state
that a given prefix that a mobile is claiming is indeed authorized
to be assigned for that mobile (if the draft is not saying that
currently). Probably few lines stating the same should be sufficient ?


Sri



> But frankly speaking I don't remember the conclusions of our prior
> discussions on this topic.  If that was agreed at that time then I don't
> oppose.  If we need to discuss it further we can start with the
> following textual nit:
>
> draft-ietf-mip4-dsmipv4-05.txt:
>> 5.  Security Considerations
>>
>> This specification operates in the security constraints and
>> requirements of [RFC3344].  It extends the operations defined in
>> [RFC3344] for IPv4 home addresses to cover home IPv6 addresses
>> prefixes [...]
>
> Addresses _and_ prefixes?  Addressed prefixes?  Or?
>
> Alex
>
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
> -- 
> Mip4 mailing list: Mip4@ietf.org
>    Web interface: http://www.ietf.org/mailman/listinfo/mip4
>     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
>
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb  6 08:47:06 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 637283A6F57;
	Wed,  6 Feb 2008 08:47:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.149,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id oZes6NT5+IUM; Wed,  6 Feb 2008 08:47:05 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5AC723A6F59;
	Wed,  6 Feb 2008 08:47:05 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AE6C43A6F0B
	for <mip4@core3.amsl.com>; Wed,  6 Feb 2008 08:47:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id po+ePPeaCtiw for <mip4@core3.amsl.com>;
	Wed,  6 Feb 2008 08:47:03 -0800 (PST)
Received: from merlot.tools.ietf.org (unknown
	[IPv6:2001:698:9:31:214:22ff:fe21:bb])
	by core3.amsl.com (Postfix) with ESMTP id 394513A6DE6
	for <mip4@ietf.org>; Wed,  6 Feb 2008 08:47:03 -0800 (PST)
Received: from localhost ([127.0.0.1]:57616 helo=chardonnay.local)
	by merlot.tools.ietf.org with esmtp (Exim 4.68)
	(envelope-from <henrik@levkowetz.com>)
	id 1JMnRn-0007nB-1Y; Wed, 06 Feb 2008 17:48:31 +0100
Message-ID: <47A9E4DE.4050308@levkowetz.com>
Date: Wed, 06 Feb 2008 17:48:30 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: Sri Gundavelli <sgundave@cisco.com>
References: <47A9BBF9.5000201@ericsson.com> <47A9C136.9020905@gmail.com>
	<Pine.GSO.4.63.0802060743170.27313@irp-view13.cisco.com>
In-Reply-To: <Pine.GSO.4.63.0802060743170.27313@irp-view13.cisco.com>
X-Enigmail-Version: 0.95.6
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: sgundave@cisco.com, alexandru.petrescu@gmail.com,
	henrik.levkowetz@ericsson.com, mip4@ietf.org,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on merlot.tools.ietf.org);
	SAEximRunCond expanded to false
Cc: Alexandru Petrescu <alexandru.petrescu@gmail.com>,
	MIP4 Mailing list <mip4@ietf.org>,
	Henrik Levkowetz <henrik.levkowetz@ericsson.com>
Subject: Re: [Mip4] Shepherd writeup for draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0170982661=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

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

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

Hi,

On 2008-02-06 16:47 Sri Gundavelli said the following:
>=20
> On Wed, 6 Feb 2008, Alexandru Petrescu wrote:
>=20
>> Henrik Levkowetz wrote:
>>> Hi,
>>>
>>>
>>> I'm currently doing the document shepherd writeup for this draft.
>>>
>>> My impression is that all issues raised during the WG last call has
>>> been addressed in -05; if this is not the case, please speak up now.
>> Well, since you ask - I do support this draft.
>>
>> There's however a security nit that I've tried to discuss several time=
s
>> in both DSMIPv4 and DSMIPv6 contexts, if I remember correctly.  Those
>> two protocols don't seem to use a Prefix Table at HA but do use NEMO
>> extensions (prefixes in reg/bu messages).  This may have some security=

>> issues: how is HA sure that the IPv6 prefix it received in a RegReq is=

>> allowed for this Mobile Router?  An attacker MR could put the prefix o=
f
>> a legitimate MR in there and obtain its traffic.
>>
>=20
>=20
> I agree, prefix authorization is required. The draft needs to state
> that a given prefix that a mobile is claiming is indeed authorized
> to be assigned for that mobile (if the draft is not saying that
> currently). Probably few lines stating the same should be sufficient ?

Mph.  The draft extends 3344, it does not extend the MIPv4 network mobili=
ty
extensions.

I think it would be more appropriate to leave MR operation with DSMIP
for discussion in the network mobility drafts, and express operation with=

and restrictions on MN-owned prefixes only here.

But what does the authors say?


	Henrik


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

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

iD8DBQFHqeTeeVhrtTJkXCMRAmDiAKCoBj6unCDpJ7nX0XwZUiYJFpICSQCgzIJq
esTebdrZKeI70LvvcUxaBtY=
=UpTP
-----END PGP SIGNATURE-----

--------------enig0EE8C018E7B766148F434EEC--

--===============0170982661==
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: http://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0170982661==--


From mip4-bounces@ietf.org  Wed Feb  6 08:55:42 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3FEFE3A6928;
	Wed,  6 Feb 2008 08:55:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lN6NyZxW8l1O; Wed,  6 Feb 2008 08:55:41 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 524433A6F9B;
	Wed,  6 Feb 2008 08:55:41 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 050433A6FE2
	for <mip4@core3.amsl.com>; Wed,  6 Feb 2008 08:55:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gNpwLI6HlIdq for <mip4@core3.amsl.com>;
	Wed,  6 Feb 2008 08:55:39 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id 384B53A6F9B
	for <mip4@ietf.org>; Wed,  6 Feb 2008 08:55:39 -0800 (PST)
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-2.cisco.com with ESMTP; 06 Feb 2008 08:57:11 -0800
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m16GvA1C016600; 
	Wed, 6 Feb 2008 08:57:10 -0800
Received: from irp-view13.cisco.com (irp-view13.cisco.com [171.70.120.60])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m16Gv9fa027109;
	Wed, 6 Feb 2008 16:57:09 GMT
Date: Wed, 6 Feb 2008 08:57:09 -0800 (PST)
From: Sri Gundavelli <sgundave@cisco.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
In-Reply-To: <47A9E4DE.4050308@levkowetz.com>
Message-ID: <Pine.GSO.4.63.0802060854280.27313@irp-view13.cisco.com>
References: <47A9BBF9.5000201@ericsson.com> <47A9C136.9020905@gmail.com>
	<Pine.GSO.4.63.0802060743170.27313@irp-view13.cisco.com>
	<47A9E4DE.4050308@levkowetz.com>
MIME-Version: 1.0
Authentication-Results: sj-dkim-2; header.From=sgundave@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: Alexandru Petrescu <alexandru.petrescu@gmail.com>,
	MIP4 Mailing list <mip4@ietf.org>,
	Henrik Levkowetz <henrik.levkowetz@ericsson.com>
Subject: Re: [Mip4] Shepherd writeup for draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi Henrik,



On Wed, 6 Feb 2008, Henrik Levkowetz wrote:

> Mph.  The draft extends 3344, it does not extend the MIPv4 network mobility
> extensions.
>
> I think it would be more appropriate to leave MR operation with DSMIP
> for discussion in the network mobility drafts, and express operation with
> and restrictions on MN-owned prefixes only here.

But, the draft is allowing prefix allocations and that is beyond 3344.
So, there needs to be some guidance on how HA should behave when
there is a RRQ containing a prefix that belongs to some other MN.
I think a simple statement on prefix authorization should be sufficient.
Not sure, if Alex has some other approach in mind.

Sri




>
> But what does the authors say?
>
>
> 	Henrik
>
>
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb  6 09:02:33 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A071E3A6FDD;
	Wed,  6 Feb 2008 09:02:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bPQpGI72Kwy6; Wed,  6 Feb 2008 09:02:28 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3496F3A6F01;
	Wed,  6 Feb 2008 09:02:28 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6ABA53A6D60
	for <mip4@core3.amsl.com>; Wed,  6 Feb 2008 09:02:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8JznpmHX9JeN for <mip4@core3.amsl.com>;
	Wed,  6 Feb 2008 09:02:25 -0800 (PST)
Received: from mail153.messagelabs.com (mail153.messagelabs.com
	[216.82.253.51]) by core3.amsl.com (Postfix) with SMTP id 85EB43A6FF6
	for <mip4@ietf.org>; Wed,  6 Feb 2008 09:02:25 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-3.tower-153.messagelabs.com!1202317435!9971073!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [144.189.100.103]
Received: (qmail 22042 invoked from network); 6 Feb 2008 17:03:56 -0000
Received: from motgate3.mot.com (HELO motgate3.mot.com) (144.189.100.103)
	by server-3.tower-153.messagelabs.com with SMTP;
	6 Feb 2008 17:03:56 -0000
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate3.mot.com (8.12.11/Motorola) with ESMTP id m16H3pVd029276;
	Wed, 6 Feb 2008 10:03:55 -0700 (MST)
Received: from az10vts01 (az10vts01.mot.com [10.64.251.242])
	by az33exr04.mot.com (8.13.1/Vontu) with SMTP id m16H3oBQ017379;
	Wed, 6 Feb 2008 11:03:50 -0600 (CST)
Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id m16H3lOb017283;
	Wed, 6 Feb 2008 11:03:48 -0600 (CST)
Message-ID: <47A9E86D.7040206@gmail.com>
Date: Wed, 06 Feb 2008 18:03:41 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Sri Gundavelli <sgundave@cisco.com>
References: <47A9BBF9.5000201@ericsson.com> <47A9C136.9020905@gmail.com>
	<Pine.GSO.4.63.0802060743170.27313@irp-view13.cisco.com>
	<47A9E4DE.4050308@levkowetz.com>
	<Pine.GSO.4.63.0802060854280.27313@irp-view13.cisco.com>
In-Reply-To: <Pine.GSO.4.63.0802060854280.27313@irp-view13.cisco.com>
X-Antivirus: avast! (VPS 080205-0, 05/02/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
Cc: Henrik Levkowetz <henrik.levkowetz@ericsson.com>,
	MIP4 Mailing list <mip4@ietf.org>, Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: [Mip4] Shepherd writeup for draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Sri Gundavelli wrote:
> Hi Henrik,
> 
> 
> 
> On Wed, 6 Feb 2008, Henrik Levkowetz wrote:
> 
>> Mph.  The draft extends 3344, it does not extend the MIPv4 network 
>> mobility extensions.
>> 
>> I think it would be more appropriate to leave MR operation with 
>> DSMIP for discussion in the network mobility drafts, and express 
>> operation with and restrictions on MN-owned prefixes only here.
> 
> But, the draft is allowing prefix allocations and that is beyond 
> 3344.

In addition to prefix allocation it clearly states that "The [DSMIPv4]
solution supports the registration of IPv6 home address(es) and/or
prefix(s) in addition to regular IPv4 home address registration."

> So, there needs to be some guidance on how HA should behave when 
> there is a RRQ containing a prefix that belongs to some other MN. I 
> think a simple statement on prefix authorization should be 
> sufficient. Not sure, if Alex has some other approach in mind.

I agree, one could write a statement like "HA should make sure it
authorizes the prefix, with a method outside the scope of this document"
or it could define a Prefix Table holding pairs of prefix-homeaddress
and describe how HA checks the prefix received in the regreq.

But I'm not sure what authors think about this aspect.

Alex


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb  6 09:10:53 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 255EB3A7083;
	Wed,  6 Feb 2008 09:10:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id b4DVsW-IwmkG; Wed,  6 Feb 2008 09:10:52 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3948C3A7068;
	Wed,  6 Feb 2008 09:10:52 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9CD313A7068
	for <mip4@core3.amsl.com>; Wed,  6 Feb 2008 09:10:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zNV5o-M5Sqj5 for <mip4@core3.amsl.com>;
	Wed,  6 Feb 2008 09:10:50 -0800 (PST)
Received: from mail153.messagelabs.com (mail153.messagelabs.com
	[216.82.253.51]) by core3.amsl.com (Postfix) with SMTP id 653773A6F01
	for <mip4@ietf.org>; Wed,  6 Feb 2008 09:10:50 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-12.tower-153.messagelabs.com!1202317941!7032500!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 18769 invoked from network); 6 Feb 2008 17:12:21 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-12.tower-153.messagelabs.com with SMTP;
	6 Feb 2008 17:12:21 -0000
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id m16HCLtR000662;
	Wed, 6 Feb 2008 10:12:21 -0700 (MST)
Received: from il06vts01.mot.com (il06vts01.mot.com [129.188.137.141])
	by il06exr04.mot.com (8.13.1/Vontu) with SMTP id m16HCKTO017827;
	Wed, 6 Feb 2008 11:12:20 -0600 (CST)
Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id m16HCI56017760;
	Wed, 6 Feb 2008 11:12:19 -0600 (CST)
Message-ID: <47A9EA6D.8010202@gmail.com>
Date: Wed, 06 Feb 2008 18:12:13 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Sri Gundavelli <sgundave@cisco.com>
References: <47A9BBF9.5000201@ericsson.com>
	<47A9C136.9020905@gmail.com>	<Pine.GSO.4.63.0802060743170.27313@irp-view13.cisco.com>	<47A9E4DE.4050308@levkowetz.com>	<Pine.GSO.4.63.0802060854280.27313@irp-view13.cisco.com>
	<47A9E86D.7040206@gmail.com>
In-Reply-To: <47A9E86D.7040206@gmail.com>
X-Antivirus: avast! (VPS 080205-0, 05/02/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
Cc: Henrik Levkowetz <henrik.levkowetz@ericsson.com>,
	MIP4 Mailing list <mip4@ietf.org>, Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: [Mip4] Shepherd writeup for draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Alexandru Petrescu wrote:
> Sri Gundavelli wrote:
>> Hi Henrik,
>>
>>
>>
>> On Wed, 6 Feb 2008, Henrik Levkowetz wrote:
>>
>>> Mph.  The draft extends 3344, it does not extend the MIPv4 network 
>>> mobility extensions.
>>>
>>> I think it would be more appropriate to leave MR operation with 
>>> DSMIP for discussion in the network mobility drafts, and express 
>>> operation with and restrictions on MN-owned prefixes only here.
>> But, the draft is allowing prefix allocations and that is beyond 
>> 3344.
> 
> In addition to prefix allocation it clearly states that "The [DSMIPv4]
> solution supports the registration of IPv6 home address(es) and/or
> prefix(s) in addition to regular IPv4 home address registration."
> 
>> So, there needs to be some guidance on how HA should behave when 
>> there is a RRQ containing a prefix that belongs to some other MN. I 
>> think a simple statement on prefix authorization should be 
>> sufficient. Not sure, if Alex has some other approach in mind.
> 
> I agree, one could write a statement like "HA should make sure it
> authorizes the prefix, with a method outside the scope of this document"
> or it could define a Prefix Table holding pairs of prefix-homeaddress
> and describe how HA checks the prefix received in the regreq.

Or one could eliminate all use of IPv6 prefixes from DSMIPv4 RegReq and 
refer to NEMOv6 encapsulated in IPv4 instead.  Just another alternative.

Alex

> 
> But I'm not sure what authors think about this aspect.
> 
> Alex
> 
> 
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email 
> ______________________________________________________________________


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb  6 18:02:37 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E82FA3A7070;
	Wed,  6 Feb 2008 18:02:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.113
X-Spam-Level: 
X-Spam-Status: No, score=-1.113 tagged_above=-999 required=5 tests=[AWL=1.486,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0wYJZ7JxXzea; Wed,  6 Feb 2008 18:02:37 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 11A003A70B9;
	Wed,  6 Feb 2008 18:02:37 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CB3FA3A711B
	for <mip4@core3.amsl.com>; Wed,  6 Feb 2008 18:02:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Ax3Y+fcm4rDd for <mip4@core3.amsl.com>;
	Wed,  6 Feb 2008 18:02:36 -0800 (PST)
Received: from omta01sl.mx.bigpond.com (omta01sl.mx.bigpond.com
	[144.140.92.153])
	by core3.amsl.com (Postfix) with ESMTP id CDF313A7070
	for <mip4@ietf.org>; Wed,  6 Feb 2008 18:02:34 -0800 (PST)
Received: from oaamta08sl.mx.bigpond.com ([124.190.105.201])
	by omta01sl.mx.bigpond.com with ESMTP id
	<20080207020404.QECG6603.omta01sl.mx.bigpond.com@oaamta08sl.mx.bigpond.com>
	for <mip4@ietf.org>; Thu, 7 Feb 2008 02:04:04 +0000
Received: from PC20005 ([124.190.105.201]) by oaamta08sl.mx.bigpond.com
	with ESMTP
	id <20080207020403.HVIL19800.oaamta08sl.mx.bigpond.com@PC20005>;
	Thu, 7 Feb 2008 02:04:03 +0000
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: "'Henrik Levkowetz'" <henrik@levkowetz.com>,
	"'Sri Gundavelli'" <sgundave@cisco.com>
Date: Thu, 7 Feb 2008 13:03:38 +1000
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAZgswlBrljUKcZNe3mbTCm8KAAAAQAAAAsVee1FW010S7uKd3DI+VhQEAAAAA@elevatemobile.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: Acho4CtkXtTAfTx6SLOYTxY2bjfpGgAVWIaA
In-Reply-To: <47A9E4DE.4050308@levkowetz.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID
	str=0001.0A010207.47AA6713.0069,ss=1,fgs=0
Cc: 'Alexandru Petrescu' <alexandru.petrescu@gmail.com>,
	'MIP4 Mailing list' <mip4@ietf.org>,
	'Henrik Levkowetz' <henrik.levkowetz@ericsson.com>
Subject: Re: [Mip4] Shepherd writeup for draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi Henrik,

 > > I agree, prefix authorization is required. The draft needs to state
 > > that a given prefix that a mobile is claiming is indeed authorized
 > > to be assigned for that mobile (if the draft is not saying that
 > > currently). Probably few lines stating the same should be 
 > sufficient ?
 > 
 > Mph.  The draft extends 3344, it does not extend the MIPv4 
 > network mobility
 > extensions.
 > 
 > I think it would be more appropriate to leave MR operation with DSMIP
 > for discussion in the network mobility drafts, and express 
 > operation with
 > and restrictions on MN-owned prefixes only here.
 > 
 > But what does the authors say?

=> I think the issue being raised is not a security issue. It's an
implementation guidline for ensuring prefix authorisation. The prefix table
is just a conceptual data structure used by nemo. So, simply stating that
the HA should delegate prefixes to authorise MRs is sufficient, it's an
editorial issue whether we have to state that the HA should use a conceptual
data structure called the prefix table or not. 

Hesham

 > 
 > 
 > 	Henrik
 > 
 > 


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb  7 00:48:47 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 91F043A7549;
	Thu,  7 Feb 2008 00:48:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.472
X-Spam-Level: 
X-Spam-Status: No, score=-2.472 tagged_above=-999 required=5 tests=[AWL=0.127,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id z-bpU5PLXxpY; Thu,  7 Feb 2008 00:48:46 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5A4D33A75FA;
	Thu,  7 Feb 2008 00:48:45 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 544F63A75E8
	for <mip4@core3.amsl.com>; Thu,  7 Feb 2008 00:48:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ADISMbb3D51L for <mip4@core3.amsl.com>;
	Thu,  7 Feb 2008 00:48:41 -0800 (PST)
Received: from merlot.tools.ietf.org (unknown
	[IPv6:2001:698:9:31:214:22ff:fe21:bb])
	by core3.amsl.com (Postfix) with ESMTP id AB99C3A7635
	for <mip4@ietf.org>; Thu,  7 Feb 2008 00:47:37 -0800 (PST)
Received: from localhost ([127.0.0.1]:37598 helo=chardonnay.local)
	by merlot.tools.ietf.org with esmtp (Exim 4.68)
	(envelope-from <henrik@levkowetz.com>)
	id 1JN2RG-0002lT-KM; Thu, 07 Feb 2008 09:48:58 +0100
Message-ID: <47AAC5F9.20702@levkowetz.com>
Date: Thu, 07 Feb 2008 09:48:57 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: Hesham Soliman <Hesham@elevatemobile.com>
References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAZgswlBrljUKcZNe3mbTCm8KAAAAQAAAAsVee1FW010S7uKd3DI+VhQEAAAAA@elevatemobile.com>
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAZgswlBrljUKcZNe3mbTCm8KAAAAQAAAAsVee1FW010S7uKd3DI+VhQEAAAAA@elevatemobile.com>
X-Enigmail-Version: 0.95.6
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: Hesham@elevatemobile.com, sgundave@cisco.com,
	alexandru.petrescu@gmail.com, mip4@ietf.org,
	henrik.levkowetz@ericsson.com, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on merlot.tools.ietf.org);
	SAEximRunCond expanded to false
Cc: 'Alexandru Petrescu' <alexandru.petrescu@gmail.com>,
	'MIP4 Mailing list' <mip4@ietf.org>,
	'Henrik Levkowetz' <henrik.levkowetz@ericsson.com>,
	'Sri Gundavelli' <sgundave@cisco.com>
Subject: Re: [Mip4] Shepherd writeup for draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2146085956=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

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

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

Hi Hesham,

On 2008-02-07 04:03 Hesham Soliman said the following:
> Hi Henrik,
>=20
>>> I agree, prefix authorization is required. The draft needs to state
>>> that a given prefix that a mobile is claiming is indeed authorized
>>> to be assigned for that mobile (if the draft is not saying that
>>> currently). Probably few lines stating the same should be=20
>> sufficient ?
>>
>> Mph.  The draft extends 3344, it does not extend the MIPv4=20
>> network mobility
>> extensions.
>>
>> I think it would be more appropriate to leave MR operation with DSMIP
>> for discussion in the network mobility drafts, and express=20
>> operation with
>> and restrictions on MN-owned prefixes only here.
>>
>> But what does the authors say?
>=20
> I think the issue being raised is not a security issue. It's an
> implementation guidline for ensuring prefix authorisation. The prefix t=
able
> is just a conceptual data structure used by nemo.

Agreed.  We shouldn't make the language in this draft dependent on that
particular way of expressing things, but should make clear what we requir=
e
of the HA.

> So, simply stating that
> the HA should delegate prefixes to authorise MRs is sufficient, it's an=

> editorial issue whether we have to state that the HA should use a conce=
ptual
> data structure called the prefix table or not.=20

Right. Could you propose some text?


	Henrik




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

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

iD8DBQFHqsX5eVhrtTJkXCMRAqV6AKCpJlh8lxdG9vZfjfSLHpvdliSuGwCfcuwE
7nPQlKCYaSPwfUUinIcjUJg=
=98yw
-----END PGP SIGNATURE-----

--------------enig40302B1DA32F566D37E7813C--

--===============2146085956==
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: http://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============2146085956==--


From mip4-bounces@ietf.org  Thu Feb  7 00:52:34 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E922D3A75F5;
	Thu,  7 Feb 2008 00:52:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.67
X-Spam-Level: 
X-Spam-Status: No, score=-1.67 tagged_above=-999 required=5 tests=[AWL=0.929,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OINfNRvuYJOf; Thu,  7 Feb 2008 00:52:34 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A76373A75F4;
	Thu,  7 Feb 2008 00:52:33 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4FF393A75AB
	for <mip4@core3.amsl.com>; Thu,  7 Feb 2008 00:52:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4F+3Fkt3SJ1J for <mip4@core3.amsl.com>;
	Thu,  7 Feb 2008 00:52:30 -0800 (PST)
Received: from omta04sl.mx.bigpond.com (omta04sl.mx.bigpond.com
	[144.140.93.156])
	by core3.amsl.com (Postfix) with ESMTP id AE9723A7598
	for <mip4@ietf.org>; Thu,  7 Feb 2008 00:51:34 -0800 (PST)
Received: from oaamta02sl.mx.bigpond.com ([124.190.105.201])
	by omta04sl.mx.bigpond.com with ESMTP id
	<20080207085304.QCPN7960.omta04sl.mx.bigpond.com@oaamta02sl.mx.bigpond.com>
	for <mip4@ietf.org>; Thu, 7 Feb 2008 08:53:04 +0000
Received: from PC20005 ([124.190.105.201]) by oaamta02sl.mx.bigpond.com
	with ESMTP
	id <20080207085303.MZNE8361.oaamta02sl.mx.bigpond.com@PC20005>;
	Thu, 7 Feb 2008 08:53:03 +0000
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: "'Henrik Levkowetz'" <henrik@levkowetz.com>
Date: Thu, 7 Feb 2008 19:52:34 +1000
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAZgswlBrljUKcZNe3mbTCm8KAAAAQAAAAO4BR705sv0aoGrCw36YpnAEAAAAA@elevatemobile.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AchpZkvWqrLVMGC/Rtqpn2STwI7e3AACMqWw
In-Reply-To: <47AAC5F9.20702@levkowetz.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID
	str=0001.0A010209.47AAC6EF.00AE,ss=1,fgs=0
Cc: 'Alexandru Petrescu' <alexandru.petrescu@gmail.com>,
	'MIP4 Mailing list' <mip4@ietf.org>,
	'Henrik Levkowetz' <henrik.levkowetz@ericsson.com>,
	'Sri Gundavelli' <sgundave@cisco.com>
Subject: Re: [Mip4] Shepherd writeup for draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org


 > > I think the issue being raised is not a security issue. It's an
 > > implementation guidline for ensuring prefix authorisation. 
 > The prefix table
 > > is just a conceptual data structure used by nemo.
 > 
 > Agreed.  We shouldn't make the language in this draft 
 > dependent on that
 > particular way of expressing things, but should make clear 
 > what we require
 > of the HA.
 > 
 > > So, simply stating that
 > > the HA should delegate prefixes to authorise MRs is 
 > sufficient, it's an
 > > editorial issue whether we have to state that the HA 
 > should use a conceptual
 > > data structure called the prefix table or not. 
 > 
 > Right. Could you propose some text?

=> I walked into this one :) sure, I'll send some text.

Hesham

 > 
 > 
 > 	Henrik
 > 
 > 
 > 
 > 


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb  7 01:39:47 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D6E4A3A765B;
	Thu,  7 Feb 2008 01:39:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id q87vBPrFKsNH; Thu,  7 Feb 2008 01:39:47 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0E6C13A75EC;
	Thu,  7 Feb 2008 01:39:47 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 99D553A75EC
	for <mip4@core3.amsl.com>; Thu,  7 Feb 2008 01:39:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id I6D++Hh8pKya for <mip4@core3.amsl.com>;
	Thu,  7 Feb 2008 01:39:45 -0800 (PST)
Received: from hs-out-2122.google.com (hs-out-0708.google.com [64.233.178.244])
	by core3.amsl.com (Postfix) with ESMTP id 7F2CC3A7524
	for <mip4@ietf.org>; Thu,  7 Feb 2008 01:39:45 -0800 (PST)
Received: by hs-out-2122.google.com with SMTP id 54so2678234hsz.5
	for <mip4@ietf.org>; Thu, 07 Feb 2008 01:41:15 -0800 (PST)
Received: by 10.142.105.14 with SMTP id d14mr5960396wfc.67.1202377274537;
	Thu, 07 Feb 2008 01:41:14 -0800 (PST)
Received: by 10.142.11.11 with HTTP; Thu, 7 Feb 2008 01:41:14 -0800 (PST)
Message-ID: <d3886a520802070141y5db7d563r8cbed09df126b825@mail.gmail.com>
Date: Thu, 7 Feb 2008 09:41:14 +0000
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Hesham Soliman" <Hesham@elevatemobile.com>
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAZgswlBrljUKcZNe3mbTCm8KAAAAQAAAAO4BR705sv0aoGrCw36YpnAEAAAAA@elevatemobile.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <47AAC5F9.20702@levkowetz.com>
	<!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAZgswlBrljUKcZNe3mbTCm8KAAAAQAAAAO4BR705sv0aoGrCw36YpnAEAAAAA@elevatemobile.com>
Cc: Henrik Levkowetz <henrik.levkowetz@ericsson.com>,
	Alexandru Petrescu <alexandru.petrescu@gmail.com>,
	MIP4 Mailing list <mip4@ietf.org>, Henrik Levkowetz <henrik@levkowetz.com>,
	Sri Gundavelli <sgundave@cisco.com>
Subject: Re: [Mip4] Shepherd writeup for draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi all,

With respect to how "authorized" prefixes are allocated, I am a bit
reluctant to be too prescribing in the specification. The spec
indicates that the MN MAY request an address/prefix and the HA MAY
provide an address/prefix. Do we really need to say much about how the
HA makes the decision? At most we could add something like this:

"How a home agent decides to provide, or accept, an IPv6 home address
or prefix to a given mobile node, is out of scope of this
specification. Local configuration or external authorization via
RADIUS/DIAMETER or other mechanisms may be used to make such
determination."

How is that?

George



On Feb 7, 2008 9:52 AM, Hesham Soliman <Hesham@elevatemobile.com> wrote:
>
>  > > I think the issue being raised is not a security issue. It's an
>  > > implementation guidline for ensuring prefix authorisation.
>  > The prefix table
>  > > is just a conceptual data structure used by nemo.
>  >
>  > Agreed.  We shouldn't make the language in this draft
>  > dependent on that
>  > particular way of expressing things, but should make clear
>  > what we require
>  > of the HA.
>  >
>  > > So, simply stating that
>  > > the HA should delegate prefixes to authorise MRs is
>  > sufficient, it's an
>  > > editorial issue whether we have to state that the HA
>  > should use a conceptual
>  > > data structure called the prefix table or not.
>  >
>  > Right. Could you propose some text?
>
> => I walked into this one :) sure, I'll send some text.
>
>
> Hesham
>
>  >
>  >
>  >      Henrik
>  >
>  >
>  >
>  >
>
>
> --
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: http://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
>
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb  7 02:24:09 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9F1A43A7717;
	Thu,  7 Feb 2008 02:24:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.538
X-Spam-Level: 
X-Spam-Status: No, score=-2.538 tagged_above=-999 required=5 tests=[AWL=0.061,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id DX6i66ACvupl; Thu,  7 Feb 2008 02:24:08 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 015C43A7727;
	Thu,  7 Feb 2008 02:24:01 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AB2313A76F0
	for <mip4@core3.amsl.com>; Thu,  7 Feb 2008 02:23:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id g91zXF0cW-z8 for <mip4@core3.amsl.com>;
	Thu,  7 Feb 2008 02:23:55 -0800 (PST)
Received: from merlot.tools.ietf.org (unknown
	[IPv6:2001:698:9:31:214:22ff:fe21:bb])
	by core3.amsl.com (Postfix) with ESMTP id 84CE93A76FE
	for <mip4@ietf.org>; Thu,  7 Feb 2008 02:22:03 -0800 (PST)
Received: from localhost ([127.0.0.1]:56451 helo=chardonnay.local)
	by merlot.tools.ietf.org with esmtp (Exim 4.68)
	(envelope-from <henrik@levkowetz.com>)
	id 1JN3ui-0005MR-SF; Thu, 07 Feb 2008 11:23:28 +0100
Message-ID: <47AADC20.8030602@levkowetz.com>
Date: Thu, 07 Feb 2008 11:23:28 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: George Tsirtsis <tsirtsis@googlemail.com>
References: <47AAC5F9.20702@levkowetz.com>	
	<!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAZgswlBrljUKcZNe3mbTCm8KAAAAQAAAAO4BR705sv0aoGrCw36YpnAEAAAAA@elevatemobile.com>
	<d3886a520802070141y5db7d563r8cbed09df126b825@mail.gmail.com>
In-Reply-To: <d3886a520802070141y5db7d563r8cbed09df126b825@mail.gmail.com>
X-Enigmail-Version: 0.95.6
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: tsirtsis@googlemail.com, Hesham@elevatemobile.com,
	alexandru.petrescu@gmail.com, mip4@ietf.org,
	henrik.levkowetz@ericsson.com, sgundave@cisco.com,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on merlot.tools.ietf.org);
	SAEximRunCond expanded to false
Cc: Sri Gundavelli <sgundave@cisco.com>,
	Alexandru Petrescu <alexandru.petrescu@gmail.com>,
	MIP4 Mailing list <mip4@ietf.org>,
	Henrik Levkowetz <henrik.levkowetz@ericsson.com>,
	Hesham Soliman <Hesham@elevatemobile.com>
Subject: Re: [Mip4] Shepherd writeup for draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0976187714=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

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

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

Hi George,

On 2008-02-07 10:41 George Tsirtsis said the following:
> Hi all,
>=20
> With respect to how "authorized" prefixes are allocated, I am a bit
> reluctant to be too prescribing in the specification. The spec
> indicates that the MN MAY request an address/prefix and the HA MAY
> provide an address/prefix. Do we really need to say much about how the
> HA makes the decision? At most we could add something like this:
>=20
> "How a home agent decides to provide, or accept, an IPv6 home address
> or prefix to a given mobile node, is out of scope of this
> specification. Local configuration or external authorization via
> RADIUS/DIAMETER or other mechanisms may be used to make such
> determination."
>=20
> How is that?

Works for me. =20

Editorially, I think I'd prefer s/prefix to a given/prefix for a given/.


	Henrik




> George
>=20
>=20
>=20
> On Feb 7, 2008 9:52 AM, Hesham Soliman <Hesham@elevatemobile.com> wrote=
:
>>  > > I think the issue being raised is not a security issue. It's an
>>  > > implementation guidline for ensuring prefix authorisation.
>>  > The prefix table
>>  > > is just a conceptual data structure used by nemo.
>>  >
>>  > Agreed.  We shouldn't make the language in this draft
>>  > dependent on that
>>  > particular way of expressing things, but should make clear
>>  > what we require
>>  > of the HA.
>>  >
>>  > > So, simply stating that
>>  > > the HA should delegate prefixes to authorise MRs is
>>  > sufficient, it's an
>>  > > editorial issue whether we have to state that the HA
>>  > should use a conceptual
>>  > > data structure called the prefix table or not.
>>  >
>>  > Right. Could you propose some text?
>>
>> =3D> I walked into this one :) sure, I'll send some text.
>>
>>
>> Hesham
>>
>>  >
>>  >
>>  >      Henrik
>>  >
>>  >
>>  >
>>  >
>>
>>
>> --
>> Mip4 mailing list: Mip4@ietf.org
>>     Web interface: http://www.ietf.org/mailman/listinfo/mip4
>>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html=

>> Supplemental site: http://www.mip4.org/
>>
>=20


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

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

iD8DBQFHqtwgeVhrtTJkXCMRAjR9AJ49+3D2fkA48uY4FFvGupUfq+YtSgCcCvtt
i1fDx//SS65NHdKuRR373Eg=
=pndZ
-----END PGP SIGNATURE-----

--------------enig7A5345CF797FFFFAD211DB0C--

--===============0976187714==
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: http://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0976187714==--


From mip4-bounces@ietf.org  Thu Feb  7 02:31:42 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 29D5E3A766F;
	Thu,  7 Feb 2008 02:31:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.004
X-Spam-Level: 
X-Spam-Status: No, score=-2.004 tagged_above=-999 required=5 tests=[AWL=0.595,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OWYUQMPVe6tK; Thu,  7 Feb 2008 02:31:41 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 263023A76B9;
	Thu,  7 Feb 2008 02:31:39 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 051E53A7578
	for <mip4@core3.amsl.com>; Thu,  7 Feb 2008 02:31:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KCeHG06v8eYT for <mip4@core3.amsl.com>;
	Thu,  7 Feb 2008 02:31:37 -0800 (PST)
Received: from omta05sl.mx.bigpond.com (omta05sl.mx.bigpond.com
	[144.140.93.195])
	by core3.amsl.com (Postfix) with ESMTP id AD3F33A7692
	for <mip4@ietf.org>; Thu,  7 Feb 2008 02:31:26 -0800 (PST)
Received: from oaamta05sl.mx.bigpond.com ([124.190.105.201])
	by omta05sl.mx.bigpond.com with ESMTP id
	<20080207103255.UDYX26389.omta05sl.mx.bigpond.com@oaamta05sl.mx.bigpond.com>
	for <mip4@ietf.org>; Thu, 7 Feb 2008 10:32:55 +0000
Received: from PC20005 ([124.190.105.201]) by oaamta05sl.mx.bigpond.com
	with ESMTP
	id <20080207103254.PLVL23867.oaamta05sl.mx.bigpond.com@PC20005>;
	Thu, 7 Feb 2008 10:32:54 +0000
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: "'George Tsirtsis'" <tsirtsis@googlemail.com>
Date: Thu, 7 Feb 2008 21:32:30 +1000
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAZgswlBrljUKcZNe3mbTCm8KAAAAQAAAA8THlAkjllE6+NarXyu933wEAAAAA@elevatemobile.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AchpbZanPT9+h+dnTISxUp7+Z97k1QAD4QPg
In-Reply-To: <d3886a520802070141y5db7d563r8cbed09df126b825@mail.gmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID
	str=0001.0A010205.47AADE56.006F,ss=1,fgs=0
Cc: 'Henrik Levkowetz' <henrik.levkowetz@ericsson.com>,
	'Alexandru Petrescu' <alexandru.petrescu@gmail.com>,
	'MIP4 Mailing list' <mip4@ietf.org>,
	'Henrik Levkowetz' <henrik@levkowetz.com>,
	'Sri Gundavelli' <sgundave@cisco.com>
Subject: Re: [Mip4] Shepherd writeup for draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Works for me too.

Hesham 

 > -----Original Message-----
 > From: George Tsirtsis [mailto:tsirtsis@googlemail.com] 
 > Sent: Thursday, February 07, 2008 7:41 PM
 > To: Hesham Soliman
 > Cc: Henrik Levkowetz; Alexandru Petrescu; MIP4 Mailing list; 
 > Henrik Levkowetz; Sri Gundavelli
 > Subject: Re: [Mip4] Shepherd writeup for draft-ietf-mip4-dsmipv4
 > 
 > Hi all,
 > 
 > With respect to how "authorized" prefixes are allocated, I am a bit
 > reluctant to be too prescribing in the specification. The spec
 > indicates that the MN MAY request an address/prefix and the HA MAY
 > provide an address/prefix. Do we really need to say much 
 > about how the
 > HA makes the decision? At most we could add something like this:
 > 
 > "How a home agent decides to provide, or accept, an IPv6 home address
 > or prefix to a given mobile node, is out of scope of this
 > specification. Local configuration or external authorization via
 > RADIUS/DIAMETER or other mechanisms may be used to make such
 > determination."
 > 
 > How is that?
 > 
 > George
 > 
 > 
 > 
 > On Feb 7, 2008 9:52 AM, Hesham Soliman 
 > <Hesham@elevatemobile.com> wrote:
 > >
 > >  > > I think the issue being raised is not a security 
 > issue. It's an
 > >  > > implementation guidline for ensuring prefix authorisation.
 > >  > The prefix table
 > >  > > is just a conceptual data structure used by nemo.
 > >  >
 > >  > Agreed.  We shouldn't make the language in this draft
 > >  > dependent on that
 > >  > particular way of expressing things, but should make clear
 > >  > what we require
 > >  > of the HA.
 > >  >
 > >  > > So, simply stating that
 > >  > > the HA should delegate prefixes to authorise MRs is
 > >  > sufficient, it's an
 > >  > > editorial issue whether we have to state that the HA
 > >  > should use a conceptual
 > >  > > data structure called the prefix table or not.
 > >  >
 > >  > Right. Could you propose some text?
 > >
 > > => I walked into this one :) sure, I'll send some text.
 > >
 > >
 > > Hesham
 > >
 > >  >
 > >  >
 > >  >      Henrik
 > >  >
 > >  >
 > >  >
 > >  >
 > >
 > >
 > > --
 > > Mip4 mailing list: Mip4@ietf.org
 > >     Web interface: http://www.ietf.org/mailman/listinfo/mip4
 > >      Charter page: 
 > http://www.ietf.org/html.charters/mip4-charter.html
 > > Supplemental site: http://www.mip4.org/
 > >
 > 


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb  7 03:20:23 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 663A43A76E9;
	Thu,  7 Feb 2008 03:20:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KYZ2Mng7u2C6; Thu,  7 Feb 2008 03:20:22 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7820B3A771C;
	Thu,  7 Feb 2008 03:20:22 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 05B463A770F
	for <mip4@core3.amsl.com>; Thu,  7 Feb 2008 03:20:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SyzXerH28pde for <mip4@core3.amsl.com>;
	Thu,  7 Feb 2008 03:20:20 -0800 (PST)
Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.235])
	by core3.amsl.com (Postfix) with ESMTP id C5B133A765E
	for <mip4@ietf.org>; Thu,  7 Feb 2008 03:20:19 -0800 (PST)
Received: by wx-out-0506.google.com with SMTP id s8so3252889wxc.31
	for <mip4@ietf.org>; Thu, 07 Feb 2008 03:21:50 -0800 (PST)
Received: by 10.142.163.14 with SMTP id l14mr6033612wfe.73.1202383309307;
	Thu, 07 Feb 2008 03:21:49 -0800 (PST)
Received: by 10.142.11.11 with HTTP; Thu, 7 Feb 2008 03:21:48 -0800 (PST)
Message-ID: <d3886a520802070321p4c56a58fo29e19b32c4042033@mail.gmail.com>
Date: Thu, 7 Feb 2008 11:21:49 +0000
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Henrik Levkowetz" <henrik@levkowetz.com>
In-Reply-To: <47AADC20.8030602@levkowetz.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <47AAC5F9.20702@levkowetz.com>
	<!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAZgswlBrljUKcZNe3mbTCm8KAAAAQAAAAO4BR705sv0aoGrCw36YpnAEAAAAA@elevatemobile.com>
	<d3886a520802070141y5db7d563r8cbed09df126b825@mail.gmail.com>
	<47AADC20.8030602@levkowetz.com>
Cc: Sri Gundavelli <sgundave@cisco.com>,
	Alexandru Petrescu <alexandru.petrescu@gmail.com>,
	MIP4 Mailing list <mip4@ietf.org>,
	Henrik Levkowetz <henrik.levkowetz@ericsson.com>,
	Hesham Soliman <Hesham@elevatemobile.com>
Subject: Re: [Mip4] Shepherd writeup for draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Henrik,

Could you clarify the editorial change you are suggesting....I am not
sure I understand what you are saying.

Aslo, do you want me to produce a new version now or shall I handle
this together with any AD comments?

George

On Feb 7, 2008 10:23 AM, Henrik Levkowetz <henrik@levkowetz.com> wrote:
> Hi George,
>
> On 2008-02-07 10:41 George Tsirtsis said the following:
> > Hi all,
> >
> > With respect to how "authorized" prefixes are allocated, I am a bit
> > reluctant to be too prescribing in the specification. The spec
> > indicates that the MN MAY request an address/prefix and the HA MAY
> > provide an address/prefix. Do we really need to say much about how the
> > HA makes the decision? At most we could add something like this:
> >
> > "How a home agent decides to provide, or accept, an IPv6 home address
> > or prefix to a given mobile node, is out of scope of this
> > specification. Local configuration or external authorization via
> > RADIUS/DIAMETER or other mechanisms may be used to make such
> > determination."
> >
> > How is that?
>
> Works for me.
>
> Editorially, I think I'd prefer s/prefix to a given/prefix for a given/.
>
>
>         Henrik
>
>
>
>
>
> > George
> >
> >
> >
> > On Feb 7, 2008 9:52 AM, Hesham Soliman <Hesham@elevatemobile.com> wrote:
> >>  > > I think the issue being raised is not a security issue. It's an
> >>  > > implementation guidline for ensuring prefix authorisation.
> >>  > The prefix table
> >>  > > is just a conceptual data structure used by nemo.
> >>  >
> >>  > Agreed.  We shouldn't make the language in this draft
> >>  > dependent on that
> >>  > particular way of expressing things, but should make clear
> >>  > what we require
> >>  > of the HA.
> >>  >
> >>  > > So, simply stating that
> >>  > > the HA should delegate prefixes to authorise MRs is
> >>  > sufficient, it's an
> >>  > > editorial issue whether we have to state that the HA
> >>  > should use a conceptual
> >>  > > data structure called the prefix table or not.
> >>  >
> >>  > Right. Could you propose some text?
> >>
> >> => I walked into this one :) sure, I'll send some text.
> >>
> >>
> >> Hesham
> >>
> >>  >
> >>  >
> >>  >      Henrik
> >>  >
> >>  >
> >>  >
> >>  >
> >>
> >>
> >> --
> >> Mip4 mailing list: Mip4@ietf.org
> >>     Web interface: http://www.ietf.org/mailman/listinfo/mip4
> >>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> >> Supplemental site: http://www.mip4.org/
> >>
> >
>
>
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb  7 03:26:58 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8C6293A77FF;
	Thu,  7 Feb 2008 03:26:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level: 
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UgQoJRfAajLa; Thu,  7 Feb 2008 03:26:57 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 92B073A75C0;
	Thu,  7 Feb 2008 03:26:57 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 538C63A765E
	for <mip4@core3.amsl.com>; Thu,  7 Feb 2008 03:26:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id O+q0sAUlNXyJ for <mip4@core3.amsl.com>;
	Thu,  7 Feb 2008 03:26:55 -0800 (PST)
Received: from merlot.tools.ietf.org (unknown
	[IPv6:2001:698:9:31:214:22ff:fe21:bb])
	by core3.amsl.com (Postfix) with ESMTP id DE5543A770F
	for <mip4@ietf.org>; Thu,  7 Feb 2008 03:26:05 -0800 (PST)
Received: from localhost ([127.0.0.1]:57935 helo=chardonnay.local)
	by merlot.tools.ietf.org with esmtp (Exim 4.68)
	(envelope-from <henrik@levkowetz.com>)
	id 1JN4uh-0001Ay-80; Thu, 07 Feb 2008 12:27:31 +0100
Message-ID: <47AAEB20.40200@levkowetz.com>
Date: Thu, 07 Feb 2008 12:27:28 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: George Tsirtsis <tsirtsis@googlemail.com>
References: <47AAC5F9.20702@levkowetz.com>	<!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAZgswlBrljUKcZNe3mbTCm8KAAAAQAAAAO4BR705sv0aoGrCw36YpnAEAAAAA@elevatemobile.com>	<d3886a520802070141y5db7d563r8cbed09df126b825@mail.gmail.com>	<47AADC20.8030602@levkowetz.com>
	<d3886a520802070321p4c56a58fo29e19b32c4042033@mail.gmail.com>
In-Reply-To: <d3886a520802070321p4c56a58fo29e19b32c4042033@mail.gmail.com>
X-Enigmail-Version: 0.95.6
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: tsirtsis@googlemail.com, sgundave@cisco.com,
	alexandru.petrescu@gmail.com, mip4@ietf.org,
	henrik.levkowetz@ericsson.com, Hesham@elevatemobile.com,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on merlot.tools.ietf.org);
	SAEximRunCond expanded to false
Cc: Hesham Soliman <Hesham@elevatemobile.com>,
	Alexandru Petrescu <alexandru.petrescu@gmail.com>,
	MIP4 Mailing list <mip4@ietf.org>,
	Henrik Levkowetz <henrik.levkowetz@ericsson.com>,
	Sri Gundavelli <sgundave@cisco.com>
Subject: Re: [Mip4] Shepherd writeup for draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0444316365=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

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

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

Hi George,

On 2008-02-07 12:21 George Tsirtsis said the following:
> Henrik,
>=20
> Could you clarify the editorial change you are suggesting....I am not
> sure I understand what you are saying.

I'd prefer:

"How a home agent decides to provide, or accept, an IPv6 home address
or prefix for a given mobile node, is out of scope of this
specification. Local configuration or external authorization via
RADIUS/DIAMETER or other mechanisms may be used to make such
determination."

> Aslo, do you want me to produce a new version now or shall I handle
> this together with any AD comments?

Let's hold off a little bit, to see if anything else comes up.  I also
have to complete my shepherd's read-through of the document as it is
now (a requirement for the writeup); there could be minor change
suggestions from that.


	Henrik

> George
>=20
> On Feb 7, 2008 10:23 AM, Henrik Levkowetz <henrik@levkowetz.com> wrote:=

>> Hi George,
>>
>> On 2008-02-07 10:41 George Tsirtsis said the following:
>>> Hi all,
>>>
>>> With respect to how "authorized" prefixes are allocated, I am a bit
>>> reluctant to be too prescribing in the specification. The spec
>>> indicates that the MN MAY request an address/prefix and the HA MAY
>>> provide an address/prefix. Do we really need to say much about how th=
e
>>> HA makes the decision? At most we could add something like this:
>>>
>>> "How a home agent decides to provide, or accept, an IPv6 home address=

>>> or prefix to a given mobile node, is out of scope of this
>>> specification. Local configuration or external authorization via
>>> RADIUS/DIAMETER or other mechanisms may be used to make such
>>> determination."
>>>
>>> How is that?
>> Works for me.
>>
>> Editorially, I think I'd prefer s/prefix to a given/prefix for a given=
/.
>>
>>
>>         Henrik
>>
>>
>>
>>
>>
>>> George
>>>
>>>
>>>
>>> On Feb 7, 2008 9:52 AM, Hesham Soliman <Hesham@elevatemobile.com> wro=
te:
>>>>  > > I think the issue being raised is not a security issue. It's an=

>>>>  > > implementation guidline for ensuring prefix authorisation.
>>>>  > The prefix table
>>>>  > > is just a conceptual data structure used by nemo.
>>>>  >
>>>>  > Agreed.  We shouldn't make the language in this draft
>>>>  > dependent on that
>>>>  > particular way of expressing things, but should make clear
>>>>  > what we require
>>>>  > of the HA.
>>>>  >
>>>>  > > So, simply stating that
>>>>  > > the HA should delegate prefixes to authorise MRs is
>>>>  > sufficient, it's an
>>>>  > > editorial issue whether we have to state that the HA
>>>>  > should use a conceptual
>>>>  > > data structure called the prefix table or not.
>>>>  >
>>>>  > Right. Could you propose some text?
>>>>
>>>> =3D> I walked into this one :) sure, I'll send some text.
>>>>
>>>>
>>>> Hesham
>>>>
>>>>  >
>>>>  >
>>>>  >      Henrik
>>>>  >
>>>>  >
>>>>  >
>>>>  >
>>>>
>>>>
>>>> --
>>>> Mip4 mailing list: Mip4@ietf.org
>>>>     Web interface: http://www.ietf.org/mailman/listinfo/mip4
>>>>      Charter page: http://www.ietf.org/html.charters/mip4-charter.ht=
ml
>>>> Supplemental site: http://www.mip4.org/
>>>>
>>


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

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

iD8DBQFHqusheVhrtTJkXCMRAhfNAKCYDOluxiUj2xLMkZuizQMTh8dYmACg8tle
ZqfLZwm04sa9mphVwT3VafM=
=APCo
-----END PGP SIGNATURE-----

--------------enig8F67818E867EC04A02E260CB--

--===============0444316365==
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: http://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0444316365==--


From mip4-bounces@ietf.org  Thu Feb  7 03:37:01 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2D2733A777E;
	Thu,  7 Feb 2008 03:37:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QHNf1iXCCwZK; Thu,  7 Feb 2008 03:37:01 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C2FFF3A75C0;
	Thu,  7 Feb 2008 03:36:57 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 836A53A77C0
	for <mip4@core3.amsl.com>; Thu,  7 Feb 2008 03:36:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SXn6IaxCjMHw for <mip4@core3.amsl.com>;
	Thu,  7 Feb 2008 03:36:56 -0800 (PST)
Received: from hs-out-2122.google.com (hs-out-0708.google.com [64.233.178.243])
	by core3.amsl.com (Postfix) with ESMTP id 2EC353A689A
	for <mip4@ietf.org>; Thu,  7 Feb 2008 03:35:54 -0800 (PST)
Received: by hs-out-2122.google.com with SMTP id 54so2707558hsz.5
	for <mip4@ietf.org>; Thu, 07 Feb 2008 03:37:24 -0800 (PST)
Received: by 10.143.16.9 with SMTP id t9mr6042811wfi.164.1202384243514;
	Thu, 07 Feb 2008 03:37:23 -0800 (PST)
Received: by 10.142.11.11 with HTTP; Thu, 7 Feb 2008 03:37:23 -0800 (PST)
Message-ID: <d3886a520802070337r4bb3f010v4c7b65803794f3d6@mail.gmail.com>
Date: Thu, 7 Feb 2008 11:37:23 +0000
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Henrik Levkowetz" <henrik@levkowetz.com>
In-Reply-To: <47AAEB20.40200@levkowetz.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <47AAC5F9.20702@levkowetz.com>
	<!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAZgswlBrljUKcZNe3mbTCm8KAAAAQAAAAO4BR705sv0aoGrCw36YpnAEAAAAA@elevatemobile.com>
	<d3886a520802070141y5db7d563r8cbed09df126b825@mail.gmail.com>
	<47AADC20.8030602@levkowetz.com>
	<d3886a520802070321p4c56a58fo29e19b32c4042033@mail.gmail.com>
	<47AAEB20.40200@levkowetz.com>
Cc: Hesham Soliman <Hesham@elevatemobile.com>,
	Alexandru Petrescu <alexandru.petrescu@gmail.com>,
	MIP4 Mailing list <mip4@ietf.org>,
	Henrik Levkowetz <henrik.levkowetz@ericsson.com>,
	Sri Gundavelli <sgundave@cisco.com>
Subject: Re: [Mip4] Shepherd writeup for draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

ok, thanks.
George

On Feb 7, 2008 11:27 AM, Henrik Levkowetz <henrik@levkowetz.com> wrote:
> Hi George,
>
> On 2008-02-07 12:21 George Tsirtsis said the following:
> > Henrik,
> >
> > Could you clarify the editorial change you are suggesting....I am not
> > sure I understand what you are saying.
>
> I'd prefer:
>
> "How a home agent decides to provide, or accept, an IPv6 home address
> or prefix for a given mobile node, is out of scope of this
> specification. Local configuration or external authorization via
> RADIUS/DIAMETER or other mechanisms may be used to make such
> determination."
>
> > Aslo, do you want me to produce a new version now or shall I handle
> > this together with any AD comments?
>
> Let's hold off a little bit, to see if anything else comes up.  I also
> have to complete my shepherd's read-through of the document as it is
> now (a requirement for the writeup); there could be minor change
> suggestions from that.
>
>
>
>         Henrik
>
> > George
> >
> > On Feb 7, 2008 10:23 AM, Henrik Levkowetz <henrik@levkowetz.com> wrote:
> >> Hi George,
> >>
> >> On 2008-02-07 10:41 George Tsirtsis said the following:
> >>> Hi all,
> >>>
> >>> With respect to how "authorized" prefixes are allocated, I am a bit
> >>> reluctant to be too prescribing in the specification. The spec
> >>> indicates that the MN MAY request an address/prefix and the HA MAY
> >>> provide an address/prefix. Do we really need to say much about how the
> >>> HA makes the decision? At most we could add something like this:
> >>>
> >>> "How a home agent decides to provide, or accept, an IPv6 home address
> >>> or prefix to a given mobile node, is out of scope of this
> >>> specification. Local configuration or external authorization via
> >>> RADIUS/DIAMETER or other mechanisms may be used to make such
> >>> determination."
> >>>
> >>> How is that?
> >> Works for me.
> >>
> >> Editorially, I think I'd prefer s/prefix to a given/prefix for a given/.
> >>
> >>
> >>         Henrik
> >>
> >>
> >>
> >>
> >>
> >>> George
> >>>
> >>>
> >>>
> >>> On Feb 7, 2008 9:52 AM, Hesham Soliman <Hesham@elevatemobile.com> wrote:
> >>>>  > > I think the issue being raised is not a security issue. It's an
> >>>>  > > implementation guidline for ensuring prefix authorisation.
> >>>>  > The prefix table
> >>>>  > > is just a conceptual data structure used by nemo.
> >>>>  >
> >>>>  > Agreed.  We shouldn't make the language in this draft
> >>>>  > dependent on that
> >>>>  > particular way of expressing things, but should make clear
> >>>>  > what we require
> >>>>  > of the HA.
> >>>>  >
> >>>>  > > So, simply stating that
> >>>>  > > the HA should delegate prefixes to authorise MRs is
> >>>>  > sufficient, it's an
> >>>>  > > editorial issue whether we have to state that the HA
> >>>>  > should use a conceptual
> >>>>  > > data structure called the prefix table or not.
> >>>>  >
> >>>>  > Right. Could you propose some text?
> >>>>
> >>>> => I walked into this one :) sure, I'll send some text.
> >>>>
> >>>>
> >>>> Hesham
> >>>>
> >>>>  >
> >>>>  >
> >>>>  >      Henrik
> >>>>  >
> >>>>  >
> >>>>  >
> >>>>  >
> >>>>
> >>>>
> >>>> --
> >>>> Mip4 mailing list: Mip4@ietf.org
> >>>>     Web interface: http://www.ietf.org/mailman/listinfo/mip4
> >>>>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> >>>> Supplemental site: http://www.mip4.org/
> >>>>
> >>
>
>
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb  7 05:55:44 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 511D63A7938;
	Thu,  7 Feb 2008 05:55:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uReWo0UAX+D6; Thu,  7 Feb 2008 05:55:44 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C16633A79B2;
	Thu,  7 Feb 2008 05:54:59 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4F0AA3A79A9
	for <mip4@core3.amsl.com>; Thu,  7 Feb 2008 05:54:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1w0CexIce249 for <mip4@core3.amsl.com>;
	Thu,  7 Feb 2008 05:54:56 -0800 (PST)
Received: from mail119.messagelabs.com (mail119.messagelabs.com
	[216.82.241.179])
	by core3.amsl.com (Postfix) with SMTP id 48C703A7946
	for <mip4@ietf.org>; Thu,  7 Feb 2008 05:54:07 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-3.tower-119.messagelabs.com!1202392536!48042571!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [144.189.100.102]
Received: (qmail 14565 invoked from network); 7 Feb 2008 13:55:37 -0000
Received: from motgate4.mot.com (HELO motgate4.mot.com) (144.189.100.102)
	by server-3.tower-119.messagelabs.com with SMTP;
	7 Feb 2008 13:55:37 -0000
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate4.mot.com (8.12.11/Motorola) with ESMTP id m17DtZZ1011235;
	Thu, 7 Feb 2008 06:55:35 -0700 (MST)
Received: from az10vts03 (az10vts03.mot.com [10.64.251.244])
	by az33exr02.mot.com (8.13.1/Vontu) with SMTP id m17DtXLx004383;
	Thu, 7 Feb 2008 07:55:34 -0600 (CST)
Received: from [127.0.0.1] (ZFR01-2117.ea.mot.com [10.161.197.9])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id m17DtUJL004331;
	Thu, 7 Feb 2008 07:55:30 -0600 (CST)
Message-ID: <47AB0DD1.9020201@gmail.com>
Date: Thu, 07 Feb 2008 14:55:29 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: George Tsirtsis <tsirtsis@googlemail.com>
References: <47AAC5F9.20702@levkowetz.com>	
	<!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAZgswlBrljUKcZNe3mbTCm8KAAAAQAAAAO4BR705sv0aoGrCw36YpnAEAAAAA@elevatemobile.com>
	<d3886a520802070141y5db7d563r8cbed09df126b825@mail.gmail.com>
In-Reply-To: <d3886a520802070141y5db7d563r8cbed09df126b825@mail.gmail.com>
X-Antivirus: avast! (VPS 080206-0, 06/02/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
Cc: Henrik Levkowetz <henrik.levkowetz@ericsson.com>,
	Hesham Soliman <Hesham@elevatemobile.com>,
	Alexandru Petrescu <alexandru.petrescu@gmail.com>,
	Sri Gundavelli <sgundave@cisco.com>, MIP4 Mailing list <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: [Mip4] Shepherd writeup for draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

George Tsirtsis wrote:
> Hi all,
> 
> With respect to how "authorized" prefixes are allocated, I am a bit 
> reluctant to be too prescribing in the specification. The spec 
> indicates that the MN MAY request an address/prefix and the HA MAY 
> provide an address/prefix. Do we really need to say much about how 
> the HA makes the decision? At most we could add something like this:
> 
> "How a home agent decides to provide, or accept, an IPv6 home address
>  or prefix to a given mobile node, is out of scope of this 
> specification.

One should at least say that the HA MUST decide/accept on that prefix,
and that this draft does not offer a means to do so.  If the draft
doesn't say HA MUST decide then this is a security issue.

Alex


> Local configuration or external authorization via RADIUS/DIAMETER or 
> other mechanisms may be used to make such determination."
> 
> How is that?
> 
> George
> 
> 
> 
> On Feb 7, 2008 9:52 AM, Hesham Soliman <Hesham@elevatemobile.com> 
> wrote:
>>>> I think the issue being raised is not a security issue. It's an
>>>>  implementation guidline for ensuring prefix authorisation.
>>> The prefix table
>>>> is just a conceptual data structure used by nemo.
>>> 
>>> Agreed.  We shouldn't make the language in this draft dependent 
>>> on that particular way of expressing things, but should make 
>>> clear what we require of the HA.
>>> 
>>>> So, simply stating that the HA should delegate prefixes to 
>>>> authorise MRs is
>>> sufficient, it's an
>>>> editorial issue whether we have to state that the HA
>>> should use a conceptual
>>>> data structure called the prefix table or not.
>>> 
>>> Right. Could you propose some text?
>> 
>> => I walked into this one :) sure, I'll send some text.
>> 
>> 
>> Hesham
>> 
>>> 
>>> 
>>> Henrik
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> -- Mip4 mailing list: Mip4@ietf.org Web interface: 
>> http://www.ietf.org/mailman/listinfo/mip4 Charter page: 
>> http://www.ietf.org/html.charters/mip4-charter.html Supplemental 
>> site: http://www.mip4.org/
>> 
> 


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb 11 07:55:08 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4A7613A6C59;
	Mon, 11 Feb 2008 07:55:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.292
X-Spam-Level: 
X-Spam-Status: No, score=-1.292 tagged_above=-999 required=5
	tests=[AWL=-0.855, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id EJOXHyDG7AMp; Mon, 11 Feb 2008 07:55:06 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 33F233A6C0D;
	Mon, 11 Feb 2008 07:55:06 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7C0183A6BDD
	for <mip4@core3.amsl.com>; Mon, 11 Feb 2008 07:55:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UPdnsAAeUGvx for <mip4@core3.amsl.com>;
	Mon, 11 Feb 2008 07:55:00 -0800 (PST)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id EA1C63A6C0D
	for <mip4@ietf.org>; Mon, 11 Feb 2008 07:54:59 -0800 (PST)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	3FDB621304; Mon, 11 Feb 2008 16:56:24 +0100 (CET)
X-AuditID: c1b4fb3e-addeebb0000007e1-ff-47b07028acd8
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	22E4E2124A; Mon, 11 Feb 2008 16:56:24 +0100 (CET)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 11 Feb 2008 16:56:23 +0100
Received: from [147.214.22.209] ([147.214.22.209]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 11 Feb 2008 16:56:23 +0100
Message-ID: <47B07027.6010502@ericsson.com>
Date: Mon, 11 Feb 2008 16:56:23 +0100
From: Henrik Levkowetz <henrik.levkowetz@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: George Tsirtsis <tsirtsis@qualcomm.com>, 
	Hesham Soliman <Hesham@elevatemobile.com>,
	Vincent Park <vpark@qualcomm.com>
X-Enigmail-Version: 0.95.6
X-OriginalArrivalTime: 11 Feb 2008 15:56:23.0730 (UTC)
	FILETIME=[A6C4D120:01C86CC6]
X-Brightmail-Tracker: AAAAAA==
Cc: mip4-chairs@tools.ietf.org, MIP4 Mailing list <mip4@ietf.org>
Subject: [Mip4] Shepherd read-through of draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi,

I've done the required shepherd's read through of this document, and
found only one thing which would cause comments in the shepherd
writeup, which is is a missing specification of the return code numbering
space in the IANA Considerations section.

There are a bunch of editorial comments and possible language
clarifications, though; since it seems we're doing one more rev based
on the recent comments on the list, the authors might want to fold in
these in the new rev, too?


Regards,

	Henrik

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


Section 2., paragraph 2:

>    Extensions defined in this document allow a node that has IPv4 and
>    IPv6 addresses [RFC2460] to maintain communications with any of its
>    addresses while moving in IPv4 or dual stack networks.

  s/with any/through any/


Section 2., paragraph 3:

>    Essentially, this specification separates the Mobile IPv4 signaling
>    from the IP version of the traffic it tunnels.  Mobile IPv4 with the
>    present extensions remains a signaling protocol that runs over IPv4,
>    and yet can set-up any combination of IPv4 and/or IPv6 over IPv4
>    tunnels.

  maybe instead just say "and yet can set up both IPv4 and IPv6
  tunnels over IPv4." ?


Section 2.3., paragraph 2:

>    In the implicit mode, the mobile node does not include a IPv6 Prefix
>    Extensions in the Registration Request.  The home agent can use any
>    mechanism (not defined in this document) to determine the IPv6
>    Prefix(es) owned by the mobile node and to set up forwarding for
>    these prefixes.  In this mode of operation all traffic to and from
>    the IPv6 prefixes MUST be encapsulated over the IPv4 tunnel between
>    the mobile node's IPv4 home address and the IPv4 address of the home
>    agent, and as such it is transparent to any foreign agent in the
>    path.  This IPv4 tunnel is established by mechanisms that are out of
>    the scope of this document on both the mobile node and home agent
>    when operating in the implicit mode.

  s/not include a IPv6 Prefix/not include any IPv6 Prefix/


Section 3.1., paragraph 1:

>    A new skippable extension to the Mobile IPv4 header in accordance to
>    the short extension format of [RFC3344] is defined here.

  s/Mobile IPv4 header/Mobile IPv4 registration request message/


Section 3.1., paragraph 6:

>       DSMIPv4 Extensions (skippable type range to be assigned by IANA)

  s/DSMIPv4 Extensions/TBD (DSMIPv4 Extension)
  s/type range/type/


Section 3.2., paragraph 1:

>    A new skippable extension to the Mobile IPv4 header in accordance to
>    the short extension format of [RFC3344] is defined here.

  s/Mobile IPv4 header/Mobile IPv4 registration reply message/


Section 3.2., paragraph 6:

>       DSMIPv4 Extensions (skippable type range to be assigned by IANA)

  s/DSMIPv4 Extensions/TBD (DSMIPv4 Extension)
  s/type range/type/


Section 3.3., paragraph 1:

>    A new skippable extension to the Mobile IPv4 header in accordance to
>    the short extension format of [RFC3344] is defined here.

  s/Mobile IPv4 header/Mobile IPv4 registration request message/


Section 0, paragraph 2:

>    Type
>       DSMIPv4 Extensions (skippable type range to be assigned by IANA)

  s/DSMIPv4 Extensions/TBD (DSMIPv4 Extension)
  s/type range/type/


Section 4.2., paragraph 2:

>    If an IPv6 code extension is included in a registration reply then,
>    the extension indicates the success or failure of the IPv6 prefix
>    registration.  The IPv6 code extension does not affect in any way the
>    code value in the registration reply header but it is superseded by
>    it.  In other words if the code field in the registration reply
>    header is set to a reject code, then all IPv6 prefix extensions are
>    also rejected.  If the code field in the registration reply header,
>    however, is set to an accept code, then an IPv6 code extension with a
>    code field set to a reject code, only rejects the binding for the
>    specific IPv6 prefix indicated in the same extension.

  s/reply then,/reply, then/
  s/set to a reject code, only/set to a reject code only/


Section 4.2., paragraph 3:

>    Note that a rejecting IPv6 code extension has the same effect with
>    not including such extension at all in the sense that in both cases
>    the mobile node and foreign agent must act as if the corresponding
>    IPv6 prefix extension included in the registration request was
>    rejected.  Of course, the inclusion of the IPv6 code extension allows
>    the home agent to indicate why a given IPv6 prefix extension was
>    rejected.  Consequently, home agent implementations of this
>    specification SHOULD include IPv6 code extensions in registration
>    reply messages, in response to registration request messages included
>    IPv6 prefix extensions.

  s/same effect with/same effect as/
  s/including such extension/including such an extension/


  It seems to me that with this you've covered the case of no IPv6 code
  extensions at all in the reply, and (although not clearly expressed)
  the case where the HA responds with an IPv6 code extension for each
  IPv6 prefix extension.  But what about a reply which only contains
  IPv6 code extensions for some of the prefix extensions, but not all?
  Is this permitted?  How should it be handled?


Section 4.3., paragraph 2:

>    For each IPv6 prefix extension included in a valid registration
>    request, a home agent that supports this specification SHOULD include
>    a corresponding IPv6 code extension in the registration reply
>    message.  For each accepted IPv6 prefix the home agent MUST decide
>    the tunneling mode it is going to use and set the Code field of the
>    IPv6 code extension to the appropriate value.  The IPv6 prefix field
>    of each of the IPv6 code extensions included in the registration
>    reply MUST match the IPv6 prefix field of an IPv6 prefix extensions
>    included in the corresponding registration request message.

  And presumably, there must not be conflicting IPv6 code extensions,
  i.e., 2 code extensions matching the same prefix extension?
  Maybe clarify this?


Section 4.3., paragraph 3:

>    If the IPv6 home address included in a IPv6 prefix extension is not
>    an on-link IPv6 address with respect to the home agent's current
>    Prefix List or a prefix it is configured to serve, the home agent
>    MUST reject the IPv6 prefix extension and SHOULD return an IPv6 code
>    extension with rejection code "registration rejected, not home
>    subnet" in the registration reply to the mobile node.

  s/ a IPv6/ an IPv6/


Section 4.3., paragraph 4:

>    When the IPv6 prefix extension contains a /128 IPv6 address and
>    unless this home agent already has a binding for the given IPv6
>    address indicated, the home agent MUST perform Duplicate Address
>    Detection [RFC4862] on the mobile node's home IPv6 link before
>    returning a registration reply.  This ensures that no other node on
>    the home link is using the IPv6 home address.  Duplicate address
>    detection is not required when the IPv6 prefix extension contains a
>    prefix.  If this Duplicate Address Detection fails for the given IPv6
>    home address or an associated link local address, then the home agent
>    MUST reject the IPv6 prefix extensions and SHOULD return a
>    registration reply to the mobile node, in which the code field of a
>    corresponding IPv6 code extension is set to "registration rejected,
>    Duplicate Address Detection failed".

  s/reject the IPv6 prefix extensions/reject the IPv6 prefix extension/
  s/the code field of a corresponding/the code field of the corresponding/


  The two paragraphs above covers the two cases of prefixes outside
  the HA's prefix list, and DAD checked 128's, but not possible
  over- lap between prefix ranges of different mobile nodes within
  the HA's prefix list.  Shouldn't this also be covered explicitly?
  (It is implicit in the next section, but never said explicitly...)

Section 4.3., paragraph 5:

>    When the home agent sends a successful registration reply to the
>    mobile node, with the Code field of a corresponding IPv6 code
>    extension set to one of the "registration accepted" values, the home
>    agent assures the mobile node that its IPv6 address(es) will be kept
>    unique by the home agent for as long as the lifetime is granted for
>    the binding.  It also indicates the tunneling mode used i.e.,
>    tunneling to home address or care-of address, based on the value of
>    the code field used in the IPv6 code extension.


Section 4.3.1., paragraph 2:

>    The dual stack home agent MUST act as defined in MIPv6 [RFC3775],
>    Section 10.4.1. in order to intercept IPv6 packets for the mobile
>    nodes it serves.

  Maybe s/The dual stack home agent/In this respect, the dual stack
  home agent/


Section 4.3.2., paragraph 1:

>    A dual stack home agent that supports the IPv6 extensions defined in
>    this specification, MUST keep track of the following IPv6 related
>    state for the mobile nodes it supports, in addition to what state is
>    defined in [RFC3344].

  s/in addition to what state is/in addition to the state which is/


Section 4.3.2., paragraph 6:

>    When IPv6 traffic is encapsulated over the tunnel between the HA and
>    the mobile node's care-off address, the tunneling mechanism used
>    should be the same with the mechanism negotiated by the Mobile IP
>    header as defined in MIPv4 [RFC3344].  In that case, when IPinIP
>    encapsulation is negotiated, IPv6 is tunneled over IPv4 according
>    to[RFC4213].  GRE and Minimal Encapsulation techniques also allow
>    tunneling of IPv6 packets by setting the Protocol Type [RFC2784] and
>    Protocol [RFC2004] fields to appropriate payload type defined for
>    IPv6 by IANA.  When, however, IPv6 traffic is encapsulated over the
>    tunnel between the HA and the mobile node's home address, IPv6 is
>    always tunneled over IPv4 according to [RFC4213], no matter what
>    tunneling mechanism is negotiated in MIPv4 signaling.

  s/should be the same with/should be the same as/


Section 4.3.2., paragraph 7:

>    A home agent that supports this specification MUST be able to defend
>    IPv4 and IPv6 packets destined to registered mobile nodes according
>    to mechanisms described in MIPv4 [RFC3344] and MIPv6 [RFC3775]
>    specifications.

  I find this a weird formulation. You defend an address, but forward
  (or drop) packets, no?  Did you mean defend the addresses here? or
  forward packets?


Section 4.3.2., paragraph 9:

>    1) Registration request is received with one or more IPv6 prefix
>    extensions.  An IPv6 tunneling mode extension is not included.

  s/ 1) Registration request/ 1) A registration request/


Section 4.3.2., paragraph 10:

>       All IPv6 packets destined to the registered IPv6 prefix(es) MUST
>       be tunneled by the home agent to the registered IPv4 home address
>       of the mobile.  The home agent first encapsulates the IPv6 packet
>       addressed to the mobile node's IPv4 home address, and then tunnels
>       this encapsulated packet to the foreign agent.  This extra level
>       of encapsulation is required so that IPv6 routing remains
>       transparent to a foreign agent that does not support IPv6.  When
>       received by the foreign agent, the unicast encapsulated packet is
>       detunneled and delivered to the mobile node in the same way as any
>       other packet.  The mobile node must decapsulate the received IPv4
>       packet it receives in order to recover the original IPv6 packet.
>       Additionally, the home agent MUST be prepared to accept reverse
>       tunneled packets from the IPv4 home address of the mobile
>       encapsulating IPv6 packets sent by that mobile.

  s/first encapsulates the IPv6 packet addressed to/
   /first encapsulates the IPv6 packet, addressing it to/
  s/the received IPv4 packet it receives/the received IPv4 packet/

  Maybe make the last sentence a separate paragraph.


Section 4.3.2., paragraph 11:

>    2) Registration request is received with one or more IPv6 prefix
>    extensions.  An IPv6 tunneling mode extension is included.

  s/ 2) Registration request/ 2) A registration request/


Section 4.3.2., paragraph 14:

>    The home agent SHOULD check that all IPv6 packets received from the
>    mobile node over a tunnel from the home address or the care-of
>    address, include a source address that falls under the registered
>    IPv6 prefix(es) for that mobile node.  If the source address of a
>    tunneled packet is not the registered IPv4 care-of address or the
>    registered IPv4 home addresses, the packet SHOULD be dropped.  If the
>    source address of the encapsulated packet does not match any of the
>    registered home addresses and/or prefixes the packet SHOULD be
>    dropped.

  The text on the IPv4 address check could need some clarification --
  is 'a tunnelled packet' 1) the inner packet or 2) the inner packet
  plus encapsulation?  Normally the first, but it seems you here use
  it as if it means the second...


Section 4.3.2., paragraph 15:

>    Interception and tunneling IPv6 multicast addressed packets on the
>    home network are only done if the home agent supports multicast group
>    membership control messages from the mobile node as described in the
>    next section.  Multicast IPv6 packets addressed to a multicast
>    address with link-local scope [RFC4291], to which the mobile node is
>    subscribed, MUST NOT be tunneled to the mobile node.  These packets
>    SHOULD be silently discarded (after delivering to other local
>    multicast recipients).  Multicast packets addressed to a multicast
>    address with a scope larger than link-local, but smaller than global
>    (e.g., site- local and organization-local [RFC4291], to which the
>    mobile node is subscribed, SHOULD NOT be tunneled to the mobile node.
>    Multicast packets addressed with a global scope, to which the mobile
>    node has successfully subscribed, MUST be tunneled to the mobile
>    node.

  s/home network are only done/home network is only done/


Section 4.4., paragraph 1:

>    A dual stack foreign agent that supports the IPv6 extensions defined
>    in this specification MUST keep track of the following IPv6 related
>    state for the mobile IP clients it supports in addition to what state
>    is defined in [RFC3344].

  s/in addition to what state is/in addition to the state which is/


Section 4.5., paragraph 14:

>    The mobile node SHOULD include exactly one IPv6 tunneling mode
>    extension if it uses the co-located care-of address model and it
>    wants to request that IPv6 packets are tunneled to its co-located
>    care-of address.  If the mobile node uses the co-located care-of
>    address model but it does not include the IPv6 tunneling mode
>    extension the home agent will tunnel IPv6 traffic to the mobile
>    node's home address.  The mobile node MUST NOT include an IPv6
>    tunneling mode extension if it uses the care-of address mode of
>    operation.  Note that if the mobile includes an IPv6 tunneling mode
>    extension in this case, IPv6 packets could be tunneled to the FA by
>    the HA.  The FA is then likely to drop them since it may not have
>    appropriate state to process them.

  Maybe clarify by s/if it uses the care-of address mode/
  	/if it uses the foreign-agent care-of address mode/


Section 4.6.1., paragraph 3:

>    A mobile node MAY include one or more IPv6 prefix extensions with the
>    IPv6 Prefix field set to ::interface_identifier, where
>    interface_identifier is the unique layer 2 address of the client.
>    The interface_identifier MUST be less than or equal to 64 bits in
>    length.  In this case the prefix length field SHOULD be set to 128.

  Why isn't this specified as MUST?  I don't see any benefit of
  specifying it as a SHOULD, only possible confusion...


Section 4.8., paragraph 1:

>    If the care-of address is a private address then Mobile IP NAT
>    Traversal as [RFC3519] MAY be used in combination with the extensions
>    described in this specification.  In that case, to transport IPv6
>    packets, the next header field of the Mobile Tunnel Data message
>    header [RFC3519] MUST be set to the value for IPv6."

  s/IPv6."/IPv6./



Section 6:

  In addition to the IANA actions already described, I believe there is
  an additional new number space for the return codes of the DSMIPv4
  code extension, which need to be established by IANA and have the
  codes defined in this spedification registered.


Section 6., paragraph 1:

>    This specification requires the allocation of a new number for
>    DSMIPv4 extensions, from the space of numbers for skippable mobility
>    extensions (i.e., 128-255) defined for Mobile IPv4 [RFC3344] at
>    http://www.iana.org/assignments/mobileip-numbers.

  s/new number/new type number/


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb 11 07:58:49 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC46A3A6C77;
	Mon, 11 Feb 2008 07:58:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.668
X-Spam-Level: 
X-Spam-Status: No, score=-0.668 tagged_above=-999 required=5
	tests=[AWL=-0.853, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	FM_FORGED_GMAIL=0.622, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QXx61H0PNd6T; Mon, 11 Feb 2008 07:58:43 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5E49C3A6C4C;
	Mon, 11 Feb 2008 07:58:43 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E775E3A6C41
	for <mip4@core3.amsl.com>; Mon, 11 Feb 2008 07:58:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id K0IGXsoXfaPW for <mip4@core3.amsl.com>;
	Mon, 11 Feb 2008 07:58:40 -0800 (PST)
Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.186])
	by core3.amsl.com (Postfix) with ESMTP id 67B2C3A6C4C
	for <mip4@ietf.org>; Mon, 11 Feb 2008 07:58:39 -0800 (PST)
Received: by rn-out-0910.google.com with SMTP id a46so1825322rne.10
	for <mip4@ietf.org>; Mon, 11 Feb 2008 08:00:04 -0800 (PST)
Received: by 10.143.162.8 with SMTP id p8mr124280wfo.49.1202745603565;
	Mon, 11 Feb 2008 08:00:03 -0800 (PST)
Received: by 10.142.11.11 with HTTP; Mon, 11 Feb 2008 08:00:03 -0800 (PST)
Message-ID: <d3886a520802110800j2ffd1d5fs1feb5f5d492de2fc@mail.gmail.com>
Date: Mon, 11 Feb 2008 16:00:03 +0000
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Henrik Levkowetz" <henrik.levkowetz@ericsson.com>
In-Reply-To: <47B07027.6010502@ericsson.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <47B07027.6010502@ericsson.com>
Cc: Vincent Park <vpark@qualcomm.com>, mip4-chairs@tools.ietf.org,
	George Tsirtsis <tsirtsis@qualcomm.com>, MIP4 Mailing list <mip4@ietf.org>,
	Hesham Soliman <Hesham@elevatemobile.com>
Subject: Re: [Mip4] Shepherd read-through of draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi Henrik,

Thanks for the review. I will fold your edits in and publish a new version asap.

Thanks
George

On Feb 11, 2008 3:56 PM, Henrik Levkowetz <henrik.levkowetz@ericsson.com> wrote:
> Hi,
>
> I've done the required shepherd's read through of this document, and
> found only one thing which would cause comments in the shepherd
> writeup, which is is a missing specification of the return code numbering
> space in the IANA Considerations section.
>
> There are a bunch of editorial comments and possible language
> clarifications, though; since it seems we're doing one more rev based
> on the recent comments on the list, the authors might want to fold in
> these in the new rev, too?
>
>
> Regards,
>
>         Henrik
>
> ------------------------------------------------------------------------
>
>
> Section 2., paragraph 2:
>
> >    Extensions defined in this document allow a node that has IPv4 and
> >    IPv6 addresses [RFC2460] to maintain communications with any of its
> >    addresses while moving in IPv4 or dual stack networks.
>
>   s/with any/through any/
>
>
> Section 2., paragraph 3:
>
> >    Essentially, this specification separates the Mobile IPv4 signaling
> >    from the IP version of the traffic it tunnels.  Mobile IPv4 with the
> >    present extensions remains a signaling protocol that runs over IPv4,
> >    and yet can set-up any combination of IPv4 and/or IPv6 over IPv4
> >    tunnels.
>
>   maybe instead just say "and yet can set up both IPv4 and IPv6
>   tunnels over IPv4." ?
>
>
> Section 2.3., paragraph 2:
>
> >    In the implicit mode, the mobile node does not include a IPv6 Prefix
> >    Extensions in the Registration Request.  The home agent can use any
> >    mechanism (not defined in this document) to determine the IPv6
> >    Prefix(es) owned by the mobile node and to set up forwarding for
> >    these prefixes.  In this mode of operation all traffic to and from
> >    the IPv6 prefixes MUST be encapsulated over the IPv4 tunnel between
> >    the mobile node's IPv4 home address and the IPv4 address of the home
> >    agent, and as such it is transparent to any foreign agent in the
> >    path.  This IPv4 tunnel is established by mechanisms that are out of
> >    the scope of this document on both the mobile node and home agent
> >    when operating in the implicit mode.
>
>   s/not include a IPv6 Prefix/not include any IPv6 Prefix/
>
>
> Section 3.1., paragraph 1:
>
> >    A new skippable extension to the Mobile IPv4 header in accordance to
> >    the short extension format of [RFC3344] is defined here.
>
>   s/Mobile IPv4 header/Mobile IPv4 registration request message/
>
>
> Section 3.1., paragraph 6:
>
> >       DSMIPv4 Extensions (skippable type range to be assigned by IANA)
>
>   s/DSMIPv4 Extensions/TBD (DSMIPv4 Extension)
>   s/type range/type/
>
>
> Section 3.2., paragraph 1:
>
> >    A new skippable extension to the Mobile IPv4 header in accordance to
> >    the short extension format of [RFC3344] is defined here.
>
>   s/Mobile IPv4 header/Mobile IPv4 registration reply message/
>
>
> Section 3.2., paragraph 6:
>
> >       DSMIPv4 Extensions (skippable type range to be assigned by IANA)
>
>   s/DSMIPv4 Extensions/TBD (DSMIPv4 Extension)
>   s/type range/type/
>
>
> Section 3.3., paragraph 1:
>
> >    A new skippable extension to the Mobile IPv4 header in accordance to
> >    the short extension format of [RFC3344] is defined here.
>
>   s/Mobile IPv4 header/Mobile IPv4 registration request message/
>
>
> Section 0, paragraph 2:
>
> >    Type
> >       DSMIPv4 Extensions (skippable type range to be assigned by IANA)
>
>   s/DSMIPv4 Extensions/TBD (DSMIPv4 Extension)
>   s/type range/type/
>
>
> Section 4.2., paragraph 2:
>
> >    If an IPv6 code extension is included in a registration reply then,
> >    the extension indicates the success or failure of the IPv6 prefix
> >    registration.  The IPv6 code extension does not affect in any way the
> >    code value in the registration reply header but it is superseded by
> >    it.  In other words if the code field in the registration reply
> >    header is set to a reject code, then all IPv6 prefix extensions are
> >    also rejected.  If the code field in the registration reply header,
> >    however, is set to an accept code, then an IPv6 code extension with a
> >    code field set to a reject code, only rejects the binding for the
> >    specific IPv6 prefix indicated in the same extension.
>
>   s/reply then,/reply, then/
>   s/set to a reject code, only/set to a reject code only/
>
>
> Section 4.2., paragraph 3:
>
> >    Note that a rejecting IPv6 code extension has the same effect with
> >    not including such extension at all in the sense that in both cases
> >    the mobile node and foreign agent must act as if the corresponding
> >    IPv6 prefix extension included in the registration request was
> >    rejected.  Of course, the inclusion of the IPv6 code extension allows
> >    the home agent to indicate why a given IPv6 prefix extension was
> >    rejected.  Consequently, home agent implementations of this
> >    specification SHOULD include IPv6 code extensions in registration
> >    reply messages, in response to registration request messages included
> >    IPv6 prefix extensions.
>
>   s/same effect with/same effect as/
>   s/including such extension/including such an extension/
>
>
>   It seems to me that with this you've covered the case of no IPv6 code
>   extensions at all in the reply, and (although not clearly expressed)
>   the case where the HA responds with an IPv6 code extension for each
>   IPv6 prefix extension.  But what about a reply which only contains
>   IPv6 code extensions for some of the prefix extensions, but not all?
>   Is this permitted?  How should it be handled?
>
>
> Section 4.3., paragraph 2:
>
> >    For each IPv6 prefix extension included in a valid registration
> >    request, a home agent that supports this specification SHOULD include
> >    a corresponding IPv6 code extension in the registration reply
> >    message.  For each accepted IPv6 prefix the home agent MUST decide
> >    the tunneling mode it is going to use and set the Code field of the
> >    IPv6 code extension to the appropriate value.  The IPv6 prefix field
> >    of each of the IPv6 code extensions included in the registration
> >    reply MUST match the IPv6 prefix field of an IPv6 prefix extensions
> >    included in the corresponding registration request message.
>
>   And presumably, there must not be conflicting IPv6 code extensions,
>   i.e., 2 code extensions matching the same prefix extension?
>   Maybe clarify this?
>
>
> Section 4.3., paragraph 3:
>
> >    If the IPv6 home address included in a IPv6 prefix extension is not
> >    an on-link IPv6 address with respect to the home agent's current
> >    Prefix List or a prefix it is configured to serve, the home agent
> >    MUST reject the IPv6 prefix extension and SHOULD return an IPv6 code
> >    extension with rejection code "registration rejected, not home
> >    subnet" in the registration reply to the mobile node.
>
>   s/ a IPv6/ an IPv6/
>
>
> Section 4.3., paragraph 4:
>
> >    When the IPv6 prefix extension contains a /128 IPv6 address and
> >    unless this home agent already has a binding for the given IPv6
> >    address indicated, the home agent MUST perform Duplicate Address
> >    Detection [RFC4862] on the mobile node's home IPv6 link before
> >    returning a registration reply.  This ensures that no other node on
> >    the home link is using the IPv6 home address.  Duplicate address
> >    detection is not required when the IPv6 prefix extension contains a
> >    prefix.  If this Duplicate Address Detection fails for the given IPv6
> >    home address or an associated link local address, then the home agent
> >    MUST reject the IPv6 prefix extensions and SHOULD return a
> >    registration reply to the mobile node, in which the code field of a
> >    corresponding IPv6 code extension is set to "registration rejected,
> >    Duplicate Address Detection failed".
>
>   s/reject the IPv6 prefix extensions/reject the IPv6 prefix extension/
>   s/the code field of a corresponding/the code field of the corresponding/
>
>
>   The two paragraphs above covers the two cases of prefixes outside
>   the HA's prefix list, and DAD checked 128's, but not possible
>   over- lap between prefix ranges of different mobile nodes within
>   the HA's prefix list.  Shouldn't this also be covered explicitly?
>   (It is implicit in the next section, but never said explicitly...)
>
> Section 4.3., paragraph 5:
>
> >    When the home agent sends a successful registration reply to the
> >    mobile node, with the Code field of a corresponding IPv6 code
> >    extension set to one of the "registration accepted" values, the home
> >    agent assures the mobile node that its IPv6 address(es) will be kept
> >    unique by the home agent for as long as the lifetime is granted for
> >    the binding.  It also indicates the tunneling mode used i.e.,
> >    tunneling to home address or care-of address, based on the value of
> >    the code field used in the IPv6 code extension.
>
>
> Section 4.3.1., paragraph 2:
>
> >    The dual stack home agent MUST act as defined in MIPv6 [RFC3775],
> >    Section 10.4.1. in order to intercept IPv6 packets for the mobile
> >    nodes it serves.
>
>   Maybe s/The dual stack home agent/In this respect, the dual stack
>   home agent/
>
>
> Section 4.3.2., paragraph 1:
>
> >    A dual stack home agent that supports the IPv6 extensions defined in
> >    this specification, MUST keep track of the following IPv6 related
> >    state for the mobile nodes it supports, in addition to what state is
> >    defined in [RFC3344].
>
>   s/in addition to what state is/in addition to the state which is/
>
>
> Section 4.3.2., paragraph 6:
>
> >    When IPv6 traffic is encapsulated over the tunnel between the HA and
> >    the mobile node's care-off address, the tunneling mechanism used
> >    should be the same with the mechanism negotiated by the Mobile IP
> >    header as defined in MIPv4 [RFC3344].  In that case, when IPinIP
> >    encapsulation is negotiated, IPv6 is tunneled over IPv4 according
> >    to[RFC4213].  GRE and Minimal Encapsulation techniques also allow
> >    tunneling of IPv6 packets by setting the Protocol Type [RFC2784] and
> >    Protocol [RFC2004] fields to appropriate payload type defined for
> >    IPv6 by IANA.  When, however, IPv6 traffic is encapsulated over the
> >    tunnel between the HA and the mobile node's home address, IPv6 is
> >    always tunneled over IPv4 according to [RFC4213], no matter what
> >    tunneling mechanism is negotiated in MIPv4 signaling.
>
>   s/should be the same with/should be the same as/
>
>
> Section 4.3.2., paragraph 7:
>
> >    A home agent that supports this specification MUST be able to defend
> >    IPv4 and IPv6 packets destined to registered mobile nodes according
> >    to mechanisms described in MIPv4 [RFC3344] and MIPv6 [RFC3775]
> >    specifications.
>
>   I find this a weird formulation. You defend an address, but forward
>   (or drop) packets, no?  Did you mean defend the addresses here? or
>   forward packets?
>
>
> Section 4.3.2., paragraph 9:
>
> >    1) Registration request is received with one or more IPv6 prefix
> >    extensions.  An IPv6 tunneling mode extension is not included.
>
>   s/ 1) Registration request/ 1) A registration request/
>
>
> Section 4.3.2., paragraph 10:
>
> >       All IPv6 packets destined to the registered IPv6 prefix(es) MUST
> >       be tunneled by the home agent to the registered IPv4 home address
> >       of the mobile.  The home agent first encapsulates the IPv6 packet
> >       addressed to the mobile node's IPv4 home address, and then tunnels
> >       this encapsulated packet to the foreign agent.  This extra level
> >       of encapsulation is required so that IPv6 routing remains
> >       transparent to a foreign agent that does not support IPv6.  When
> >       received by the foreign agent, the unicast encapsulated packet is
> >       detunneled and delivered to the mobile node in the same way as any
> >       other packet.  The mobile node must decapsulate the received IPv4
> >       packet it receives in order to recover the original IPv6 packet.
> >       Additionally, the home agent MUST be prepared to accept reverse
> >       tunneled packets from the IPv4 home address of the mobile
> >       encapsulating IPv6 packets sent by that mobile.
>
>   s/first encapsulates the IPv6 packet addressed to/
>    /first encapsulates the IPv6 packet, addressing it to/
>   s/the received IPv4 packet it receives/the received IPv4 packet/
>
>   Maybe make the last sentence a separate paragraph.
>
>
> Section 4.3.2., paragraph 11:
>
> >    2) Registration request is received with one or more IPv6 prefix
> >    extensions.  An IPv6 tunneling mode extension is included.
>
>   s/ 2) Registration request/ 2) A registration request/
>
>
> Section 4.3.2., paragraph 14:
>
> >    The home agent SHOULD check that all IPv6 packets received from the
> >    mobile node over a tunnel from the home address or the care-of
> >    address, include a source address that falls under the registered
> >    IPv6 prefix(es) for that mobile node.  If the source address of a
> >    tunneled packet is not the registered IPv4 care-of address or the
> >    registered IPv4 home addresses, the packet SHOULD be dropped.  If the
> >    source address of the encapsulated packet does not match any of the
> >    registered home addresses and/or prefixes the packet SHOULD be
> >    dropped.
>
>   The text on the IPv4 address check could need some clarification --
>   is 'a tunnelled packet' 1) the inner packet or 2) the inner packet
>   plus encapsulation?  Normally the first, but it seems you here use
>   it as if it means the second...
>
>
> Section 4.3.2., paragraph 15:
>
> >    Interception and tunneling IPv6 multicast addressed packets on the
> >    home network are only done if the home agent supports multicast group
> >    membership control messages from the mobile node as described in the
> >    next section.  Multicast IPv6 packets addressed to a multicast
> >    address with link-local scope [RFC4291], to which the mobile node is
> >    subscribed, MUST NOT be tunneled to the mobile node.  These packets
> >    SHOULD be silently discarded (after delivering to other local
> >    multicast recipients).  Multicast packets addressed to a multicast
> >    address with a scope larger than link-local, but smaller than global
> >    (e.g., site- local and organization-local [RFC4291], to which the
> >    mobile node is subscribed, SHOULD NOT be tunneled to the mobile node.
> >    Multicast packets addressed with a global scope, to which the mobile
> >    node has successfully subscribed, MUST be tunneled to the mobile
> >    node.
>
>   s/home network are only done/home network is only done/
>
>
> Section 4.4., paragraph 1:
>
> >    A dual stack foreign agent that supports the IPv6 extensions defined
> >    in this specification MUST keep track of the following IPv6 related
> >    state for the mobile IP clients it supports in addition to what state
> >    is defined in [RFC3344].
>
>   s/in addition to what state is/in addition to the state which is/
>
>
> Section 4.5., paragraph 14:
>
> >    The mobile node SHOULD include exactly one IPv6 tunneling mode
> >    extension if it uses the co-located care-of address model and it
> >    wants to request that IPv6 packets are tunneled to its co-located
> >    care-of address.  If the mobile node uses the co-located care-of
> >    address model but it does not include the IPv6 tunneling mode
> >    extension the home agent will tunnel IPv6 traffic to the mobile
> >    node's home address.  The mobile node MUST NOT include an IPv6
> >    tunneling mode extension if it uses the care-of address mode of
> >    operation.  Note that if the mobile includes an IPv6 tunneling mode
> >    extension in this case, IPv6 packets could be tunneled to the FA by
> >    the HA.  The FA is then likely to drop them since it may not have
> >    appropriate state to process them.
>
>   Maybe clarify by s/if it uses the care-of address mode/
>         /if it uses the foreign-agent care-of address mode/
>
>
> Section 4.6.1., paragraph 3:
>
> >    A mobile node MAY include one or more IPv6 prefix extensions with the
> >    IPv6 Prefix field set to ::interface_identifier, where
> >    interface_identifier is the unique layer 2 address of the client.
> >    The interface_identifier MUST be less than or equal to 64 bits in
> >    length.  In this case the prefix length field SHOULD be set to 128.
>
>   Why isn't this specified as MUST?  I don't see any benefit of
>   specifying it as a SHOULD, only possible confusion...
>
>
> Section 4.8., paragraph 1:
>
> >    If the care-of address is a private address then Mobile IP NAT
> >    Traversal as [RFC3519] MAY be used in combination with the extensions
> >    described in this specification.  In that case, to transport IPv6
> >    packets, the next header field of the Mobile Tunnel Data message
> >    header [RFC3519] MUST be set to the value for IPv6."
>
>   s/IPv6."/IPv6./
>
>
>
> Section 6:
>
>   In addition to the IANA actions already described, I believe there is
>   an additional new number space for the return codes of the DSMIPv4
>   code extension, which need to be established by IANA and have the
>   codes defined in this spedification registered.
>
>
> Section 6., paragraph 1:
>
> >    This specification requires the allocation of a new number for
> >    DSMIPv4 extensions, from the space of numbers for skippable mobility
> >    extensions (i.e., 128-255) defined for Mobile IPv4 [RFC3344] at
> >    http://www.iana.org/assignments/mobileip-numbers.
>
>   s/new number/new type number/
>
>
> --
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: http://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
>
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb 11 20:41:35 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 93F0028CBD9;
	Mon, 11 Feb 2008 20:41:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.1
X-Spam-Level: **
X-Spam-Status: No, score=2.1 tagged_above=-999 required=5 tests=[AWL=0.653,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=1, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LtM-9fsPhOXk; Mon, 11 Feb 2008 20:41:34 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9CB6728CBD3;
	Mon, 11 Feb 2008 20:41:34 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 104B928CBD2
	for <mip4@core3.amsl.com>; Mon, 11 Feb 2008 20:41:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5BLYU623cSPw for <mip4@core3.amsl.com>;
	Mon, 11 Feb 2008 20:41:32 -0800 (PST)
Received: from n8b.bullet.ukl.yahoo.com (n8b.bullet.ukl.yahoo.com
	[217.146.182.218])
	by core3.amsl.com (Postfix) with SMTP id A760828CBD0
	for <mip4@ietf.org>; Mon, 11 Feb 2008 20:41:31 -0800 (PST)
Received: from [217.12.4.215] by n8.bullet.ukl.yahoo.com with NNFMP;
	12 Feb 2008 04:42:55 -0000
Received: from [216.252.122.217] by t2.bullet.ukl.yahoo.com with NNFMP;
	12 Feb 2008 04:42:55 -0000
Received: from [69.147.84.100] by t2.bullet.sp1.yahoo.com with NNFMP;
	12 Feb 2008 04:42:55 -0000
Received: from [127.0.0.1] by omp201.mail.sp1.yahoo.com with NNFMP;
	12 Feb 2008 04:42:55 -0000
X-Yahoo-Newman-Property: ymail-5
X-Yahoo-Newman-Id: 38584.66773.bm@omp201.mail.sp1.yahoo.com
Received: (qmail 1283 invoked by uid 60001); 12 Feb 2008 03:16:31 -0000
X-YMail-OSG: JcqGKsoVM1mrCljYwFlcHjfln95nhlOAKcXqUv4F
Received: from [71.49.102.78] by web45902.mail.sp1.yahoo.com via HTTP;
	Mon, 11 Feb 2008 19:16:31 PST
Date: Mon, 11 Feb 2008 19:16:31 -0800 (PST)
From: John Edward <jeedward@yahoo.com>
To: mip4@ietf.org
MIME-Version: 1.0
Message-ID: <500427.99743.qm@web45902.mail.sp1.yahoo.com>
Subject: [Mip4] HPCNCS-08 Draft paper submission is deadline is just few
	days from now
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0824429432=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

--===============0824429432==
Content-Type: multipart/alternative; boundary="0-1122498797-1202786191=:99743"
Content-Transfer-Encoding: 8bit

--0-1122498797-1202786191=:99743
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit



Dear Colleagues and Friends

 

Kindly share the announcement below with those who may be interested: thank you in advance.  

 

Sincerely

John Edward
 
HPCNCS-08 Draft paper submission deadline is just few days from now
 
The 2008 International Conference on High Performance Computing, Networking and Communication Systems (HPCNCS-08) (website: www.PromoteResearch.org ) will be held during July 7-10 2008 in Orlando, FL, USA. We invite draft paper submissions and the deadline is extended until February 19 2008 due to several requests from the authors.
 
The conference will be held at the same time and place where several major events (please see below) are taking place. The website contains more details.
 
Sincerely
John Edward
 
·         International Conference on Artificial Intelligence and Pattern Recognition (AIPR-08) 
·         International Conference on Automation, Robotics and Control Systems (ARCS-08)
·         International Conference on Bioinformatics, Computational Biology, Genomics and Chemoinformatics (BCBGC-08)
·         International Conference on Enterprise Information Systems and Web Technologies (EISWT-08)
·         International Conference on High Performance Computing, Networking and Communication Systems (HPCNCS-08)
·         International Conference on Software Engineering Theory and Practice (SETP-08)  
·         International Conference on Theoretical and Mathematical Foundations of Computer Science (TMFCS-08)


       
---------------------------------
Never miss a thing.   Make Yahoo your homepage.
--0-1122498797-1202786191=:99743
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<PRE><A name=OLE_LINK4></A><PRE><A name=OLE_LINK4></A><A name=OLE_LINK3><SPAN style="mso-bookmark: OLE_LINK4"><TT><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Times New Roman','serif'">Dear Colleagues and Friends<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p></SPAN></TT></SPAN></A></PRE><PRE><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><TT><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Times New Roman','serif'"><o:p>&nbsp;</o:p></SPAN></TT></SPAN></SPAN></PRE><PRE><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><TT><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Times New Roman','serif'">Kindly share the announcement below with those who may be interested: thank you in advance.<SPAN style="mso-spacerun: yes">&nbsp; </SPAN><o:p></o:p></SPAN></TT></SPAN></SPAN></PRE><PRE><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark:
 OLE_LINK4"><TT><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Times New Roman','serif'"><o:p>&nbsp;</o:p></SPAN></TT></SPAN></SPAN></PRE><PRE><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><TT><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Times New Roman','serif'">Sincerely<o:p></o:p></SPAN></TT></SPAN></SPAN></PRE><PRE><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><TT><SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Times New Roman','serif'">John Edward<o:p></o:p></SPAN></TT></SPAN></SPAN></PRE><div class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><o:p><FONT face="Times New Roman" size=3>&nbsp;</FONT></o:p></SPAN></SPAN></div><div class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><FONT face="Times New Roman" size=3>HPCNCS-08 Draft paper
 submission deadline is just few days from now</FONT></SPAN></SPAN></div><div class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><o:p><FONT face="Times New Roman" size=3>&nbsp;</FONT></o:p></SPAN></SPAN></div><div class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><FONT face="Times New Roman" size=3>The 2008 International Conference on High Performance Computing, Networking and Communication Systems (HPCNCS-08) (website: </FONT></SPAN></SPAN><A href="http://www.promoteresearch.org/"><FONT size=3><FONT face="Times New Roman"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4">www.PromoteResearch.org</SPAN></SPAN><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"></SPAN></SPAN></FONT></FONT></A><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><FONT face="Times New
 Roman" size=3> ) will be held during July 7-10 2008 in Orlando, FL, USA. We invite draft paper submissions and the deadline is extended until February 19 2008 due to several requests from the authors.</FONT></SPAN></SPAN></div><div class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><o:p><FONT face="Times New Roman" size=3>&nbsp;</FONT></o:p></SPAN></SPAN></div><div class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><FONT face="Times New Roman" size=3>The conference will be held at the same time and place where several major events (please see below) are taking place. The website contains more details.</FONT></SPAN></SPAN></div><div class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><o:p><FONT face="Times New Roman" size=3>&nbsp;</FONT></o:p></SPAN></SPAN></div><div
 class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><FONT face="Times New Roman" size=3>Sincerely</FONT></SPAN></SPAN></div><div class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><FONT face="Times New Roman" size=3>John Edward</FONT></SPAN></SPAN></div><SPAN style="mso-bookmark: OLE_LINK4"></SPAN><SPAN style="mso-bookmark: OLE_LINK3"></SPAN><div class=MsoNormal style="MARGIN: 0in 0in 0pt"><o:p><FONT face="Times New Roman" size=3>&nbsp;</FONT></o:p></div><div style="MARGIN-LEFT: 31.5pt; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1"><SPAN style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style="mso-list: Ignore"><FONT size=3>·</FONT><SPAN style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPAN><FONT face="Times New Roman" size=3>International
 Conference on Artificial Intelligence and Pattern Recognition (AIPR-08) </FONT></div><div style="MARGIN-LEFT: 31.5pt; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1"><SPAN style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style="mso-list: Ignore"><FONT size=3>·</FONT><SPAN style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPAN><FONT face="Times New Roman" size=3>International Conference on Automation, Robotics and Control Systems (ARCS-08)</FONT></div><div style="MARGIN-LEFT: 31.5pt; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1"><SPAN style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style="mso-list: Ignore"><FONT size=3>·</FONT><SPAN style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPAN><FONT face="Times New Roman" size=3>International Conference on Bioinformatics,
 Computational Biology, Genomics and Chemoinformatics (BCBGC-08)</FONT></div><div style="MARGIN-LEFT: 31.5pt; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1"><SPAN style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style="mso-list: Ignore"><FONT size=3>·</FONT><SPAN style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPAN><FONT face="Times New Roman" size=3>International Conference on Enterprise Information Systems and Web Technologies (EISWT-08)</FONT></div><div style="MARGIN-LEFT: 31.5pt; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1"><SPAN style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style="mso-list: Ignore"><FONT size=3>·</FONT><SPAN style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPAN><FONT face="Times New Roman" size=3>International Conference on High Performance
 Computing, Networking and Communication Systems (HPCNCS-08)</FONT></div><div style="MARGIN-LEFT: 31.5pt; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1"><SPAN style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style="mso-list: Ignore"><FONT size=3>·</FONT><SPAN style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPAN><FONT size=3><FONT face="Times New Roman"><SPAN style="COLOR: black">International Conference on Software Engineering Theory and Practice (SETP-08) </SPAN><SPAN style="mso-spacerun: yes">&nbsp;</SPAN></FONT></FONT></div><div style="MARGIN-LEFT: 31.5pt; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo1"><SPAN style="FONT-FAMILY: Symbol; mso-fareast-font-family: Symbol; mso-bidi-font-family: Symbol"><SPAN style="mso-list: Ignore"><FONT size=3>·</FONT><SPAN style="FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></SPAN></SPAN><FONT
 face="Times New Roman" size=3>International Conference on Theoretical and Mathematical Foundations of Computer Science (TMFCS-08)</FONT></div></PRE><p>&#32;



      <hr size=1>Never miss a thing.  <a href="http://us.rd.yahoo.com/evt=51438/*http://www.yahoo.com/r/hs"> Make Yahoo your homepage.</a>


--0-1122498797-1202786191=:99743--


--===============0824429432==
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: http://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0824429432==--



From mip4-bounces@ietf.org  Tue Feb 12 04:20:57 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F23D33A6E01;
	Tue, 12 Feb 2008 04:20:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.668
X-Spam-Level: 
X-Spam-Status: No, score=-0.668 tagged_above=-999 required=5
	tests=[AWL=-0.853, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	FM_FORGED_GMAIL=0.622, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id u9cCj6DmdKbD; Tue, 12 Feb 2008 04:20:55 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B314C3A6A7C;
	Tue, 12 Feb 2008 04:20:55 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EF1EE28C0F6
	for <mip4@core3.amsl.com>; Tue, 12 Feb 2008 04:20:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dXgctKBPA3yM for <mip4@core3.amsl.com>;
	Tue, 12 Feb 2008 04:20:53 -0800 (PST)
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174])
	by core3.amsl.com (Postfix) with ESMTP id 6027F3A68A2
	for <mip4@ietf.org>; Tue, 12 Feb 2008 04:20:52 -0800 (PST)
Received: by ug-out-1314.google.com with SMTP id u2so1269456uge.46
	for <mip4@ietf.org>; Tue, 12 Feb 2008 04:22:16 -0800 (PST)
Received: by 10.142.52.9 with SMTP id z9mr931210wfz.134.1202818934864;
	Tue, 12 Feb 2008 04:22:14 -0800 (PST)
Received: by 10.142.11.11 with HTTP; Tue, 12 Feb 2008 04:22:14 -0800 (PST)
Message-ID: <d3886a520802120422w1e97e076r7893aa039b7de395@mail.gmail.com>
Date: Tue, 12 Feb 2008 12:22:14 +0000
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Henrik Levkowetz" <henrik.levkowetz@ericsson.com>
In-Reply-To: <47B07027.6010502@ericsson.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <47B07027.6010502@ericsson.com>
Cc: Vincent Park <vpark@qualcomm.com>, mip4-chairs@tools.ietf.org,
	George Tsirtsis <tsirtsis@qualcomm.com>, MIP4 Mailing list <mip4@ietf.org>,
	Hesham Soliman <Hesham@elevatemobile.com>
Subject: Re: [Mip4] Shepherd read-through of draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi Henrik,

I have reviewed your comments and suggested changes and have accepted
I think all of them. Below I removed all the corrections accepted
outright and just provide responses and alternative text where more
significant text changes have been made. If you could have a quick
look before I publish the new version it would be good.

Thanks again for the review.
George

On Feb 11, 2008 3:56 PM, Henrik Levkowetz <henrik.levkowetz@ericsson.com> wrote:
> Hi,
>
> I've done the required shepherd's read through of this document, and
> found only one thing which would cause comments in the shepherd
> writeup, which is is a missing specification of the return code numbering
> space in the IANA Considerations section.
>
> There are a bunch of editorial comments and possible language
> clarifications, though; since it seems we're doing one more rev based
> on the recent comments on the list, the authors might want to fold in
> these in the new rev, too?
>
>
> Regards,
>
>         Henrik
>
> ------------------------------------------------------------------------
...
>
>   It seems to me that with this you've covered the case of no IPv6 code
>   extensions at all in the reply, and (although not clearly expressed)
>   the case where the HA responds with an IPv6 code extension for each
>   IPv6 prefix extension.  But what about a reply which only contains
>   IPv6 code extensions for some of the prefix extensions, but not all?
>   Is this permitted?  How should it be handled?
>

GT> Good point. I rephrased the last paragraph to say this:
                  " Consequently, home agent implementations of this
                    specification SHOULD include, in the registration reply
                    messages, an IPv6 code extension for each IPv6 prefix
                    extension included in the corresponding registration request
                    message"

>
> Section 4.3., paragraph 2:
>
> >    For each IPv6 prefix extension included in a valid registration
> >    request, a home agent that supports this specification SHOULD include
> >    a corresponding IPv6 code extension in the registration reply
> >    message.  For each accepted IPv6 prefix the home agent MUST decide
> >    the tunneling mode it is going to use and set the Code field of the
> >    IPv6 code extension to the appropriate value.  The IPv6 prefix field
> >    of each of the IPv6 code extensions included in the registration
> >    reply MUST match the IPv6 prefix field of an IPv6 prefix extensions
> >    included in the corresponding registration request message.
>
>   And presumably, there must not be conflicting IPv6 code extensions,
>   i.e., 2 code extensions matching the same prefix extension?
>   Maybe clarify this?
>

GT> Yes, clarified
>
>   The two paragraphs above covers the two cases of prefixes outside
>   the HA's prefix list, and DAD checked 128's, but not possible
>   over- lap between prefix ranges of different mobile nodes within
>   the HA's prefix list.  Shouldn't this also be covered explicitly?
>   (It is implicit in the next section, but never said explicitly...)
>

GT> What about this new wording at the end of the section: "Note that
for IPv6 prefixes (rather than addresses), the home
                    agent does not have to perform Duplicate Address Detection
                    but it MUST check that allocated prefixes are not
                    overlapping so that all addresses under each allocated
                    prefix are allocated only to a single mobile node at any one
                    time"


>
> Section 4.3.2., paragraph 7:
>
> >    A home agent that supports this specification MUST be able to defend
> >    IPv4 and IPv6 packets destined to registered mobile nodes according
> >    to mechanisms described in MIPv4 [RFC3344] and MIPv6 [RFC3775]
> >    specifications.
>
>   I find this a weird formulation. You defend an address, but forward
>   (or drop) packets, no?  Did you mean defend the addresses here? or
>   forward packets?
>

GT> Yes, good catch, rephrased to:
"A home agent that supports this specification MUST be
                        able to defend IPv4 and IPv6 addresses
                        registered by mobile nodes according to mechanisms
                        described in..."

>
> Section 4.3.2., paragraph 14:
>
> >    The home agent SHOULD check that all IPv6 packets received from the
> >    mobile node over a tunnel from the home address or the care-of
> >    address, include a source address that falls under the registered
> >    IPv6 prefix(es) for that mobile node.  If the source address of a
> >    tunneled packet is not the registered IPv4 care-of address or the
> >    registered IPv4 home addresses, the packet SHOULD be dropped.  If the
> >    source address of the encapsulated packet does not match any of the
> >    registered home addresses and/or prefixes the packet SHOULD be
> >    dropped.
>
>   The text on the IPv4 address check could need some clarification --
>   is 'a tunnelled packet' 1) the inner packet or 2) the inner packet
>   plus encapsulation?  Normally the first, but it seems you here use
>   it as if it means the second...
>

GT> Yes, the text is not clear enough. How is this?:
"The home agent SHOULD check that all inner IPv6 packets
                        received from the mobile node over a tunnel with outer
                        source address the home address or the care-of address,
                        include a source address that falls under the registered
                        IPv6 prefix(es) for that mobile node. If the source
                        address of the outer header of a tunneled packet is not
                        the registered IPv4 care-of address or the registered
                        IPv4 home addresses, the packet SHOULD be dropped. If
                        the source address of the inner header of an
                        tunneled packet does not match any of the registered
                        home addresses and/or prefixes the packet SHOULD be
                        dropped."

>
> Section 4.6.1., paragraph 3:
>
> >    A mobile node MAY include one or more IPv6 prefix extensions with the
> >    IPv6 Prefix field set to ::interface_identifier, where
> >    interface_identifier is the unique layer 2 address of the client.
> >    The interface_identifier MUST be less than or equal to 64 bits in
> >    length.  In this case the prefix length field SHOULD be set to 128.
>
>   Why isn't this specified as MUST?  I don't see any benefit of
>   specifying it as a SHOULD, only possible confusion...
>

GT> Yes, true, corrected.
..
>
>
> Section 6:
>
>   In addition to the IANA actions already described, I believe there is
>   an additional new number space for the return codes of the DSMIPv4
>   code extension, which need to be established by IANA and have the
>   codes defined in this spedification registered.
>
>
GT> Yes, good. I added the following as a paragraph before the last one.:
"Finally, this specification creates a new space for the Code
                field of the IPv6 code extension. Values 0, 1, 8, 9, 10, 11 are
                defined in this specification. Values 0-7 are reserved for
                accept codes and the rest of the values are reserved for reject
                values."
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb 12 04:37:42 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F2AC228C1BC;
	Tue, 12 Feb 2008 04:37:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.601
X-Spam-Level: 
X-Spam-Status: No, score=-0.601 tagged_above=-999 required=5
	tests=[AWL=-0.786, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	FM_FORGED_GMAIL=0.622, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3DiinadmTJbK; Tue, 12 Feb 2008 04:37:40 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A2503A6E4E;
	Tue, 12 Feb 2008 04:37:40 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8097C3A6E47
	for <mip4@core3.amsl.com>; Tue, 12 Feb 2008 04:37:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RS9lXCqUjJA4 for <mip4@core3.amsl.com>;
	Tue, 12 Feb 2008 04:37:35 -0800 (PST)
Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.230])
	by core3.amsl.com (Postfix) with ESMTP id E318F3A6D8A
	for <mip4@ietf.org>; Tue, 12 Feb 2008 04:37:34 -0800 (PST)
Received: by wr-out-0506.google.com with SMTP id 50so5759220wri.25
	for <mip4@ietf.org>; Tue, 12 Feb 2008 04:38:58 -0800 (PST)
Received: by 10.142.231.7 with SMTP id d7mr928258wfh.194.1202819937891;
	Tue, 12 Feb 2008 04:38:57 -0800 (PST)
Received: by 10.142.11.11 with HTTP; Tue, 12 Feb 2008 04:38:57 -0800 (PST)
Message-ID: <d3886a520802120438q3ed0de6fje8db2b4f626a7a7@mail.gmail.com>
Date: Tue, 12 Feb 2008 12:38:57 +0000
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Henrik Levkowetz" <henrik.levkowetz@ericsson.com>
In-Reply-To: <d3886a520802120422w1e97e076r7893aa039b7de395@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <47B07027.6010502@ericsson.com>
	<d3886a520802120422w1e97e076r7893aa039b7de395@mail.gmail.com>
Cc: Vincent Park <vpark@qualcomm.com>, mip4-chairs@tools.ietf.org,
	George Tsirtsis <tsirtsis@qualcomm.com>, MIP4 Mailing list <mip4@ietf.org>,
	Hesham Soliman <Hesham@elevatemobile.com>
Subject: Re: [Mip4] Shepherd read-through of draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Henrik et.al.,

One more thing. I have been thinking about the references list which
is rather long. I just introduced an informative references section
which I did not have before and I need some advice on what to move
there. What is the convention here? I would think that DSMIPOv4 really
only depends on MIPv4, MIPv6 and NEMO. Everything else could be
informative reference....but is this right? Any rule of thumb I can
follow?

Thanks
George

On Feb 12, 2008 12:22 PM, George Tsirtsis <tsirtsis@googlemail.com> wrote:
> Hi Henrik,
>
> I have reviewed your comments and suggested changes and have accepted
> I think all of them. Below I removed all the corrections accepted
> outright and just provide responses and alternative text where more
> significant text changes have been made. If you could have a quick
> look before I publish the new version it would be good.
>
> Thanks again for the review.
> George
>
> On Feb 11, 2008 3:56 PM, Henrik Levkowetz <henrik.levkowetz@ericsson.com> wrote:
> > Hi,
> >
> > I've done the required shepherd's read through of this document, and
> > found only one thing which would cause comments in the shepherd
> > writeup, which is is a missing specification of the return code numbering
> > space in the IANA Considerations section.
> >
> > There are a bunch of editorial comments and possible language
> > clarifications, though; since it seems we're doing one more rev based
> > on the recent comments on the list, the authors might want to fold in
> > these in the new rev, too?
> >
> >
> > Regards,
> >
> >         Henrik
> >
> > ------------------------------------------------------------------------
> ...
> >
> >   It seems to me that with this you've covered the case of no IPv6 code
> >   extensions at all in the reply, and (although not clearly expressed)
> >   the case where the HA responds with an IPv6 code extension for each
> >   IPv6 prefix extension.  But what about a reply which only contains
> >   IPv6 code extensions for some of the prefix extensions, but not all?
> >   Is this permitted?  How should it be handled?
> >
>
> GT> Good point. I rephrased the last paragraph to say this:
>                   " Consequently, home agent implementations of this
>                     specification SHOULD include, in the registration reply
>                     messages, an IPv6 code extension for each IPv6 prefix
>                     extension included in the corresponding registration request
>                     message"
>
> >
> > Section 4.3., paragraph 2:
> >
> > >    For each IPv6 prefix extension included in a valid registration
> > >    request, a home agent that supports this specification SHOULD include
> > >    a corresponding IPv6 code extension in the registration reply
> > >    message.  For each accepted IPv6 prefix the home agent MUST decide
> > >    the tunneling mode it is going to use and set the Code field of the
> > >    IPv6 code extension to the appropriate value.  The IPv6 prefix field
> > >    of each of the IPv6 code extensions included in the registration
> > >    reply MUST match the IPv6 prefix field of an IPv6 prefix extensions
> > >    included in the corresponding registration request message.
> >
> >   And presumably, there must not be conflicting IPv6 code extensions,
> >   i.e., 2 code extensions matching the same prefix extension?
> >   Maybe clarify this?
> >
>
> GT> Yes, clarified
> >
> >   The two paragraphs above covers the two cases of prefixes outside
> >   the HA's prefix list, and DAD checked 128's, but not possible
> >   over- lap between prefix ranges of different mobile nodes within
> >   the HA's prefix list.  Shouldn't this also be covered explicitly?
> >   (It is implicit in the next section, but never said explicitly...)
> >
>
> GT> What about this new wording at the end of the section: "Note that
> for IPv6 prefixes (rather than addresses), the home
>                     agent does not have to perform Duplicate Address Detection
>                     but it MUST check that allocated prefixes are not
>                     overlapping so that all addresses under each allocated
>                     prefix are allocated only to a single mobile node at any one
>                     time"
>
>
> >
> > Section 4.3.2., paragraph 7:
> >
> > >    A home agent that supports this specification MUST be able to defend
> > >    IPv4 and IPv6 packets destined to registered mobile nodes according
> > >    to mechanisms described in MIPv4 [RFC3344] and MIPv6 [RFC3775]
> > >    specifications.
> >
> >   I find this a weird formulation. You defend an address, but forward
> >   (or drop) packets, no?  Did you mean defend the addresses here? or
> >   forward packets?
> >
>
> GT> Yes, good catch, rephrased to:
> "A home agent that supports this specification MUST be
>                         able to defend IPv4 and IPv6 addresses
>                         registered by mobile nodes according to mechanisms
>                         described in..."
>
> >
> > Section 4.3.2., paragraph 14:
> >
> > >    The home agent SHOULD check that all IPv6 packets received from the
> > >    mobile node over a tunnel from the home address or the care-of
> > >    address, include a source address that falls under the registered
> > >    IPv6 prefix(es) for that mobile node.  If the source address of a
> > >    tunneled packet is not the registered IPv4 care-of address or the
> > >    registered IPv4 home addresses, the packet SHOULD be dropped.  If the
> > >    source address of the encapsulated packet does not match any of the
> > >    registered home addresses and/or prefixes the packet SHOULD be
> > >    dropped.
> >
> >   The text on the IPv4 address check could need some clarification --
> >   is 'a tunnelled packet' 1) the inner packet or 2) the inner packet
> >   plus encapsulation?  Normally the first, but it seems you here use
> >   it as if it means the second...
> >
>
> GT> Yes, the text is not clear enough. How is this?:
> "The home agent SHOULD check that all inner IPv6 packets
>                         received from the mobile node over a tunnel with outer
>                         source address the home address or the care-of address,
>                         include a source address that falls under the registered
>                         IPv6 prefix(es) for that mobile node. If the source
>                         address of the outer header of a tunneled packet is not
>                         the registered IPv4 care-of address or the registered
>                         IPv4 home addresses, the packet SHOULD be dropped. If
>                         the source address of the inner header of an
>                         tunneled packet does not match any of the registered
>                         home addresses and/or prefixes the packet SHOULD be
>                         dropped."
>
> >
> > Section 4.6.1., paragraph 3:
> >
> > >    A mobile node MAY include one or more IPv6 prefix extensions with the
> > >    IPv6 Prefix field set to ::interface_identifier, where
> > >    interface_identifier is the unique layer 2 address of the client.
> > >    The interface_identifier MUST be less than or equal to 64 bits in
> > >    length.  In this case the prefix length field SHOULD be set to 128.
> >
> >   Why isn't this specified as MUST?  I don't see any benefit of
> >   specifying it as a SHOULD, only possible confusion...
> >
>
> GT> Yes, true, corrected.
> ..
> >
> >
> > Section 6:
> >
> >   In addition to the IANA actions already described, I believe there is
> >   an additional new number space for the return codes of the DSMIPv4
> >   code extension, which need to be established by IANA and have the
> >   codes defined in this spedification registered.
> >
> >
> GT> Yes, good. I added the following as a paragraph before the last one.:
> "Finally, this specification creates a new space for the Code
>                 field of the IPv6 code extension. Values 0, 1, 8, 9, 10, 11 are
>                 defined in this specification. Values 0-7 are reserved for
>                 accept codes and the rest of the values are reserved for reject
>                 values."
>
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb 12 07:30:08 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E168D28CC69;
	Tue, 12 Feb 2008 07:30:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id orj4MGuin03G; Tue, 12 Feb 2008 07:30:03 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3B42328C2E6;
	Tue, 12 Feb 2008 07:30:03 -0800 (PST)
X-Original-To: mip4@ietf.org
Delivered-To: mip4@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id DBBC628C2DC; Tue, 12 Feb 2008 07:30:01 -0800 (PST)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080212153001.DBBC628C2DC@core3.amsl.com>
Date: Tue, 12 Feb 2008 07:30:01 -0800 (PST)
Cc: mip4@ietf.org
Subject: [Mip4] I-D
	Action:draft-ietf-mip4-generic-notification-message-03.txt
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobility for IPv4 Working Group of the IETF.


	Title           : Generic Notification Message for Mobile IPv4
	Author(s)       : H. Deng, et al.
	Filename        : draft-ietf-mip4-generic-notification-message-03.txt
	Pages           : 25
	Date            : 2008-02-12

This document specifies protocol enhancements that allow Mobile IPv4
entities to send and receive explicit notification messages using a
new Mobile IPv4 message type designed for this purpose.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip4-generic-notification-message-03.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-mip4-generic-notification-message-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mip4-generic-notification-message-03.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2008-02-12072004.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip4-generic-notification-message-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mip4-generic-notification-message-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-02-12072004.I-D\@ietf.org>


--OtherAccess--

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

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

--NextPart--


From mip4-bounces@ietf.org  Tue Feb 12 13:16:52 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6417628C5F7;
	Tue, 12 Feb 2008 13:16:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.346
X-Spam-Level: 
X-Spam-Status: No, score=-1.346 tagged_above=-999 required=5
	tests=[AWL=-0.909, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JLqNWAUfKCjs; Tue, 12 Feb 2008 13:16:51 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2A54D28C4E9;
	Tue, 12 Feb 2008 13:16:51 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6A38428C39B
	for <mip4@core3.amsl.com>; Tue, 12 Feb 2008 13:16:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UeJPnvccAYHB for <mip4@core3.amsl.com>;
	Tue, 12 Feb 2008 13:16:49 -0800 (PST)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [194.146.105.14])
	by core3.amsl.com (Postfix) with ESMTP id CB19B28C5A6
	for <mip4@ietf.org>; Tue, 12 Feb 2008 13:16:48 -0800 (PST)
Received: from localhost ([127.0.0.1]:40874 helo=chardonnay.local)
	by merlot.tools.ietf.org with esmtp (Exim 4.69)
	(envelope-from <henrik@levkowetz.com>)
	id 1JP2Vr-0005oO-4B; Tue, 12 Feb 2008 22:17:59 +0100
Message-ID: <47B20CF9.601@levkowetz.com>
Date: Tue, 12 Feb 2008 22:17:45 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: George Tsirtsis <tsirtsis@googlemail.com>
References: <47B07027.6010502@ericsson.com>	<d3886a520802120422w1e97e076r7893aa039b7de395@mail.gmail.com>
	<d3886a520802120438q3ed0de6fje8db2b4f626a7a7@mail.gmail.com>
In-Reply-To: <d3886a520802120438q3ed0de6fje8db2b4f626a7a7@mail.gmail.com>
X-Enigmail-Version: 0.95.6
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: tsirtsis@googlemail.com, vpark@qualcomm.com,
	mip4-chairs@tools.ietf.org, tsirtsis@qualcomm.com, mip4@ietf.org,
	Hesham@elevatemobile.com, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on merlot.tools.ietf.org);
	SAEximRunCond expanded to false
Cc: Vincent Park <vpark@qualcomm.com>, mip4-chairs@tools.ietf.org,
	George Tsirtsis <tsirtsis@qualcomm.com>, MIP4 Mailing list <mip4@ietf.org>,
	Hesham Soliman <Hesham@elevatemobile.com>
Subject: Re: [Mip4] Shepherd read-through of draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1870529108=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

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

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

Hi George,

On 2008-02-12 13:38 George Tsirtsis said the following:
> Henrik et.al.,
>=20
> One more thing. I have been thinking about the references list which
> is rather long. I just introduced an informative references section
> which I did not have before and I need some advice on what to move
> there. What is the convention here? I would think that DSMIPOv4 really
> only depends on MIPv4, MIPv6 and NEMO. Everything else could be
> informative reference....but is this right? Any rule of thumb I can
> follow?

Sounds good to me.  The rule of thumb is that if somebody needs to read
a document in order to implement the current spec., then that document
is normative.  Otherwise, informative.

Regards,

	Henrik


> Thanks
> George
>=20
> On Feb 12, 2008 12:22 PM, George Tsirtsis <tsirtsis@googlemail.com> wro=
te:
>> Hi Henrik,
>>
>> I have reviewed your comments and suggested changes and have accepted
>> I think all of them. Below I removed all the corrections accepted
>> outright and just provide responses and alternative text where more
>> significant text changes have been made. If you could have a quick
>> look before I publish the new version it would be good.
>>
>> Thanks again for the review.
>> George
>>
>> On Feb 11, 2008 3:56 PM, Henrik Levkowetz <henrik.levkowetz@ericsson.c=
om> wrote:
>>> Hi,
>>>
>>> I've done the required shepherd's read through of this document, and
>>> found only one thing which would cause comments in the shepherd
>>> writeup, which is is a missing specification of the return code numbe=
ring
>>> space in the IANA Considerations section.
>>>
>>> There are a bunch of editorial comments and possible language
>>> clarifications, though; since it seems we're doing one more rev based=

>>> on the recent comments on the list, the authors might want to fold in=

>>> these in the new rev, too?
>>>
>>>
>>> Regards,
>>>
>>>         Henrik
>>>
>>> ---------------------------------------------------------------------=
---
>> ...
>>>   It seems to me that with this you've covered the case of no IPv6 co=
de
>>>   extensions at all in the reply, and (although not clearly expressed=
)
>>>   the case where the HA responds with an IPv6 code extension for each=

>>>   IPv6 prefix extension.  But what about a reply which only contains
>>>   IPv6 code extensions for some of the prefix extensions, but not all=
?
>>>   Is this permitted?  How should it be handled?
>>>
>> GT> Good point. I rephrased the last paragraph to say this:
>>                   " Consequently, home agent implementations of this
>>                     specification SHOULD include, in the registration =
reply
>>                     messages, an IPv6 code extension for each IPv6 pre=
fix
>>                     extension included in the corresponding registrati=
on request
>>                     message"
>>
>>> Section 4.3., paragraph 2:
>>>
>>>>    For each IPv6 prefix extension included in a valid registration
>>>>    request, a home agent that supports this specification SHOULD inc=
lude
>>>>    a corresponding IPv6 code extension in the registration reply
>>>>    message.  For each accepted IPv6 prefix the home agent MUST decid=
e
>>>>    the tunneling mode it is going to use and set the Code field of t=
he
>>>>    IPv6 code extension to the appropriate value.  The IPv6 prefix fi=
eld
>>>>    of each of the IPv6 code extensions included in the registration
>>>>    reply MUST match the IPv6 prefix field of an IPv6 prefix extensio=
ns
>>>>    included in the corresponding registration request message.
>>>   And presumably, there must not be conflicting IPv6 code extensions,=

>>>   i.e., 2 code extensions matching the same prefix extension?
>>>   Maybe clarify this?
>>>
>> GT> Yes, clarified
>>>   The two paragraphs above covers the two cases of prefixes outside
>>>   the HA's prefix list, and DAD checked 128's, but not possible
>>>   over- lap between prefix ranges of different mobile nodes within
>>>   the HA's prefix list.  Shouldn't this also be covered explicitly?
>>>   (It is implicit in the next section, but never said explicitly...)
>>>
>> GT> What about this new wording at the end of the section: "Note that
>> for IPv6 prefixes (rather than addresses), the home
>>                     agent does not have to perform Duplicate Address D=
etection
>>                     but it MUST check that allocated prefixes are not
>>                     overlapping so that all addresses under each alloc=
ated
>>                     prefix are allocated only to a single mobile node =
at any one
>>                     time"
>>
>>
>>> Section 4.3.2., paragraph 7:
>>>
>>>>    A home agent that supports this specification MUST be able to def=
end
>>>>    IPv4 and IPv6 packets destined to registered mobile nodes accordi=
ng
>>>>    to mechanisms described in MIPv4 [RFC3344] and MIPv6 [RFC3775]
>>>>    specifications.
>>>   I find this a weird formulation. You defend an address, but forward=

>>>   (or drop) packets, no?  Did you mean defend the addresses here? or
>>>   forward packets?
>>>
>> GT> Yes, good catch, rephrased to:
>> "A home agent that supports this specification MUST be
>>                         able to defend IPv4 and IPv6 addresses
>>                         registered by mobile nodes according to mechan=
isms
>>                         described in..."
>>
>>> Section 4.3.2., paragraph 14:
>>>
>>>>    The home agent SHOULD check that all IPv6 packets received from t=
he
>>>>    mobile node over a tunnel from the home address or the care-of
>>>>    address, include a source address that falls under the registered=

>>>>    IPv6 prefix(es) for that mobile node.  If the source address of a=

>>>>    tunneled packet is not the registered IPv4 care-of address or the=

>>>>    registered IPv4 home addresses, the packet SHOULD be dropped.  If=
 the
>>>>    source address of the encapsulated packet does not match any of t=
he
>>>>    registered home addresses and/or prefixes the packet SHOULD be
>>>>    dropped.
>>>   The text on the IPv4 address check could need some clarification --=

>>>   is 'a tunnelled packet' 1) the inner packet or 2) the inner packet
>>>   plus encapsulation?  Normally the first, but it seems you here use
>>>   it as if it means the second...
>>>
>> GT> Yes, the text is not clear enough. How is this?:
>> "The home agent SHOULD check that all inner IPv6 packets
>>                         received from the mobile node over a tunnel wi=
th outer
>>                         source address the home address or the care-of=
 address,
>>                         include a source address that falls under the =
registered
>>                         IPv6 prefix(es) for that mobile node. If the s=
ource
>>                         address of the outer header of a tunneled pack=
et is not
>>                         the registered IPv4 care-of address or the reg=
istered
>>                         IPv4 home addresses, the packet SHOULD be drop=
ped. If
>>                         the source address of the inner header of an
>>                         tunneled packet does not match any of the regi=
stered
>>                         home addresses and/or prefixes the packet SHOU=
LD be
>>                         dropped."
>>
>>> Section 4.6.1., paragraph 3:
>>>
>>>>    A mobile node MAY include one or more IPv6 prefix extensions with=
 the
>>>>    IPv6 Prefix field set to ::interface_identifier, where
>>>>    interface_identifier is the unique layer 2 address of the client.=

>>>>    The interface_identifier MUST be less than or equal to 64 bits in=

>>>>    length.  In this case the prefix length field SHOULD be set to 12=
8.
>>>   Why isn't this specified as MUST?  I don't see any benefit of
>>>   specifying it as a SHOULD, only possible confusion...
>>>
>> GT> Yes, true, corrected.
>> ..
>>>
>>> Section 6:
>>>
>>>   In addition to the IANA actions already described, I believe there =
is
>>>   an additional new number space for the return codes of the DSMIPv4
>>>   code extension, which need to be established by IANA and have the
>>>   codes defined in this spedification registered.
>>>
>>>
>> GT> Yes, good. I added the following as a paragraph before the last on=
e.:
>> "Finally, this specification creates a new space for the Code
>>                 field of the IPv6 code extension. Values 0, 1, 8, 9, 1=
0, 11 are
>>                 defined in this specification. Values 0-7 are reserved=
 for
>>                 accept codes and the rest of the values are reserved f=
or reject
>>                 values."
>>


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

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

iD8DBQFHsg0GeVhrtTJkXCMRAtm9AJ0dp85idVmqtD2cVhP7ksVORkDNtACgkMZH
ITyQGNPl2S2ECxx4JpkdoMs=
=fHW9
-----END PGP SIGNATURE-----

--------------enigB4C989B1507DE71F6C726708--

--===============1870529108==
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: http://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1870529108==--


From mip4-bounces@ietf.org  Tue Feb 12 13:32:20 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 05A8728C499;
	Tue, 12 Feb 2008 13:32:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.267
X-Spam-Level: 
X-Spam-Status: No, score=-1.267 tagged_above=-999 required=5
	tests=[AWL=-0.830, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id syZWcWvaCSpk; Tue, 12 Feb 2008 13:32:18 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9466F3A6E82;
	Tue, 12 Feb 2008 13:32:18 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3413028C216
	for <mip4@core3.amsl.com>; Tue, 12 Feb 2008 13:32:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uVWdOWPL0DRQ for <mip4@core3.amsl.com>;
	Tue, 12 Feb 2008 13:32:16 -0800 (PST)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [194.146.105.14])
	by core3.amsl.com (Postfix) with ESMTP id A90DB3A6BD9
	for <mip4@ietf.org>; Tue, 12 Feb 2008 13:32:15 -0800 (PST)
Received: from localhost ([127.0.0.1]:43471 helo=chardonnay.local)
	by merlot.tools.ietf.org with esmtp (Exim 4.69)
	(envelope-from <henrik@levkowetz.com>)
	id 1JP2kn-0006oO-Qa; Tue, 12 Feb 2008 22:33:25 +0100
Message-ID: <47B210A5.1010902@levkowetz.com>
Date: Tue, 12 Feb 2008 22:33:25 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: George Tsirtsis <tsirtsis@googlemail.com>
References: <47B07027.6010502@ericsson.com>
	<d3886a520802120422w1e97e076r7893aa039b7de395@mail.gmail.com>
In-Reply-To: <d3886a520802120422w1e97e076r7893aa039b7de395@mail.gmail.com>
X-Enigmail-Version: 0.95.6
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: tsirtsis@googlemail.com, henrik.levkowetz@ericsson.com,
	vpark@qualcomm.com, mip4-chairs@tools.ietf.org,
	tsirtsis@qualcomm.com, mip4@ietf.org, Hesham@elevatemobile.com,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on merlot.tools.ietf.org);
	SAEximRunCond expanded to false
Cc: Henrik Levkowetz <henrik.levkowetz@ericsson.com>,
	Hesham Soliman <Hesham@elevatemobile.com>, mip4-chairs@tools.ietf.org,
	George Tsirtsis <tsirtsis@qualcomm.com>, MIP4 Mailing list <mip4@ietf.org>,
	Vincent Park <vpark@qualcomm.com>
Subject: Re: [Mip4] Shepherd read-through of draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1902397500=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

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

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

Hi George,

On 2008-02-12 13:22 George Tsirtsis said the following:
> Hi Henrik,
>=20
> I have reviewed your comments and suggested changes and have accepted
> I think all of them. Below I removed all the corrections accepted
> outright and just provide responses and alternative text where more
> significant text changes have been made. If you could have a quick
> look before I publish the new version it would be good.
>=20
> Thanks again for the review.
> George
>=20
> On Feb 11, 2008 3:56 PM, Henrik Levkowetz <henrik.levkowetz@ericsson.co=
m> wrote:
>> Hi,
>>
>> I've done the required shepherd's read through of this document, and
>> found only one thing which would cause comments in the shepherd
>> writeup, which is is a missing specification of the return code number=
ing
>> space in the IANA Considerations section.
>>
>> There are a bunch of editorial comments and possible language
>> clarifications, though; since it seems we're doing one more rev based
>> on the recent comments on the list, the authors might want to fold in
>> these in the new rev, too?
>>
>>
>> Regards,
>>
>>         Henrik
>>
>> ----------------------------------------------------------------------=
--
> ...
>>   It seems to me that with this you've covered the case of no IPv6 cod=
e
>>   extensions at all in the reply, and (although not clearly expressed)=

>>   the case where the HA responds with an IPv6 code extension for each
>>   IPv6 prefix extension.  But what about a reply which only contains
>>   IPv6 code extensions for some of the prefix extensions, but not all?=

>>   Is this permitted?  How should it be handled?
>>
>=20
> GT> Good point. I rephrased the last paragraph to say this:
>                   " Consequently, home agent implementations of this
>                     specification SHOULD include, in the registration r=
eply
>                     messages, an IPv6 code extension for each IPv6 pref=
ix
>                     extension included in the corresponding registratio=
n request
>                     message"

Umm. Yes. But there's no indication of what happens if the HA doesn't
comply, which is what I really was wondering about.  You actually describ=
e
that in detail later, but you might point forward to the right section he=
re
by saying something like "A detailed description of how the mobile node
handles different IPv6 code extension code values and absent IPv6 code
extensions is given in Section ...."

Hmm.  That makes me realize something which bothered me a bit earlier --
the extension name 'IPv6 code extension' is a bit - umm, imprecise.  Have=

you considered any other names?  IPv6 prefix reply extension?  It's late
in the game, so I wouldn't insist on any change here, but I realized that=

I'd reacted to this a bit during the previous read-through when I saw the=

sentence I proposed above...

>> Section 4.3., paragraph 2:
>>
>>>    For each IPv6 prefix extension included in a valid registration
>>>    request, a home agent that supports this specification SHOULD incl=
ude
>>>    a corresponding IPv6 code extension in the registration reply
>>>    message.  For each accepted IPv6 prefix the home agent MUST decide=

>>>    the tunneling mode it is going to use and set the Code field of th=
e
>>>    IPv6 code extension to the appropriate value.  The IPv6 prefix fie=
ld
>>>    of each of the IPv6 code extensions included in the registration
>>>    reply MUST match the IPv6 prefix field of an IPv6 prefix extension=
s
>>>    included in the corresponding registration request message.
>>   And presumably, there must not be conflicting IPv6 code extensions,
>>   i.e., 2 code extensions matching the same prefix extension?
>>   Maybe clarify this?
>>
>=20
> GT> Yes, clarified

Thanks.

>>   The two paragraphs above covers the two cases of prefixes outside
>>   the HA's prefix list, and DAD checked 128's, but not possible
>>   over- lap between prefix ranges of different mobile nodes within
>>   the HA's prefix list.  Shouldn't this also be covered explicitly?
>>   (It is implicit in the next section, but never said explicitly...)
>>
>=20
> GT> What about this new wording at the end of the section: "Note that
> for IPv6 prefixes (rather than addresses), the home
>                     agent does not have to perform Duplicate Address De=
tection
>                     but it MUST check that allocated prefixes are not
>                     overlapping so that all addresses under each alloca=
ted
>                     prefix are allocated only to a single mobile node a=
t any one
>                     time"

Splendid.

>> Section 4.3.2., paragraph 7:
>>
>>>    A home agent that supports this specification MUST be able to defe=
nd
>>>    IPv4 and IPv6 packets destined to registered mobile nodes accordin=
g
>>>    to mechanisms described in MIPv4 [RFC3344] and MIPv6 [RFC3775]
>>>    specifications.
>>   I find this a weird formulation. You defend an address, but forward
>>   (or drop) packets, no?  Did you mean defend the addresses here? or
>>   forward packets?
>>
>=20
> GT> Yes, good catch, rephrased to:
> "A home agent that supports this specification MUST be
>                         able to defend IPv4 and IPv6 addresses
>                         registered by mobile nodes according to mechani=
sms
>                         described in..."

Excellent.

>> Section 4.3.2., paragraph 14:
>>
>>>    The home agent SHOULD check that all IPv6 packets received from th=
e
>>>    mobile node over a tunnel from the home address or the care-of
>>>    address, include a source address that falls under the registered
>>>    IPv6 prefix(es) for that mobile node.  If the source address of a
>>>    tunneled packet is not the registered IPv4 care-of address or the
>>>    registered IPv4 home addresses, the packet SHOULD be dropped.  If =
the
>>>    source address of the encapsulated packet does not match any of th=
e
>>>    registered home addresses and/or prefixes the packet SHOULD be
>>>    dropped.
>>   The text on the IPv4 address check could need some clarification --
>>   is 'a tunnelled packet' 1) the inner packet or 2) the inner packet
>>   plus encapsulation?  Normally the first, but it seems you here use
>>   it as if it means the second...
>>
>=20
> GT> Yes, the text is not clear enough. How is this?:
> "The home agent SHOULD check that all inner IPv6 packets
>                         received from the mobile node over a tunnel wit=
h outer
>                         source address the home address or the care-of =
address,
>                         include a source address that falls under the r=
egistered
>                         IPv6 prefix(es) for that mobile node. If the so=
urce
>                         address of the outer header of a tunneled packe=
t is not
>                         the registered IPv4 care-of address or the regi=
stered
>                         IPv4 home addresses, the packet SHOULD be dropp=
ed. If
>                         the source address of the inner header of an
>                         tunneled packet does not match any of the regis=
tered
>                         home addresses and/or prefixes the packet SHOUL=
D be
>                         dropped."

Good.

>> Section 4.6.1., paragraph 3:
>>
>>>    A mobile node MAY include one or more IPv6 prefix extensions with =
the
>>>    IPv6 Prefix field set to ::interface_identifier, where
>>>    interface_identifier is the unique layer 2 address of the client.
>>>    The interface_identifier MUST be less than or equal to 64 bits in
>>>    length.  In this case the prefix length field SHOULD be set to 128=
=2E
>>   Why isn't this specified as MUST?  I don't see any benefit of
>>   specifying it as a SHOULD, only possible confusion...
>>
>=20
> GT> Yes, true, corrected.

Good.

> ..
>>
>> Section 6:
>>
>>   In addition to the IANA actions already described, I believe there i=
s
>>   an additional new number space for the return codes of the DSMIPv4
>>   code extension, which need to be established by IANA and have the
>>   codes defined in this spedification registered.
>>
>>
> GT> Yes, good. I added the following as a paragraph before the last one=
=2E:
> "Finally, this specification creates a new space for the Code
>                 field of the IPv6 code extension. Values 0, 1, 8, 9, 10=
, 11 are
>                 defined in this specification. Values 0-7 are reserved =
for
>                 accept codes and the rest of the values are reserved fo=
r reject
>                 values."

Ah.  Good.


	Henrik


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

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

iD8DBQFHshCleVhrtTJkXCMRAjnDAJ4jo4bh3Yont8PUCgBRMKWGLVYyaACgwvjm
WTJIjGKcKJa2M7KsMMj1jIg=
=iTre
-----END PGP SIGNATURE-----

--------------enigE5AAD5C7DF25518FD673E2F2--

--===============1902397500==
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: http://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1902397500==--


From mip4-bounces@ietf.org  Tue Feb 12 19:00:05 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AC2DC28C6C5;
	Tue, 12 Feb 2008 19:00:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id b1WOq3caCYz5; Tue, 12 Feb 2008 19:00:04 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D921228C699;
	Tue, 12 Feb 2008 19:00:03 -0800 (PST)
X-Original-To: mip4@ietf.org
Delivered-To: mip4@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 2520D3A68A5; Tue, 12 Feb 2008 19:00:00 -0800 (PST)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080213030001.2520D3A68A5@core3.amsl.com>
Date: Tue, 12 Feb 2008 19:00:01 -0800 (PST)
Cc: mip4@ietf.org
Subject: [Mip4] I-D
	Action:draft-ietf-mip4-generic-notification-message-04.txt
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobility for IPv4 Working Group of the IETF.


	Title           : Generic Notification Message for Mobile IPv4
	Author(s)       : H. Deng, et al.
	Filename        : draft-ietf-mip4-generic-notification-message-04.txt
	Pages           : 25
	Date            : 2008-02-12

This document specifies protocol enhancements that allow Mobile IPv4
entities to send and receive explicit notification messages using a
new Mobile IPv4 message type designed for this purpose.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip4-generic-notification-message-04.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-mip4-generic-notification-message-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mip4-generic-notification-message-04.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2008-02-12184714.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip4-generic-notification-message-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mip4-generic-notification-message-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-02-12184714.I-D\@ietf.org>


--OtherAccess--

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

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

--NextPart--


From mip4-bounces@ietf.org  Wed Feb 13 05:17:17 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4600C28C7AE;
	Wed, 13 Feb 2008 05:17:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.405
X-Spam-Level: 
X-Spam-Status: No, score=-0.405 tagged_above=-999 required=5
	tests=[AWL=-0.590, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	FM_FORGED_GMAIL=0.622, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CpL13FcxckSq; Wed, 13 Feb 2008 05:17:16 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 09AB928C7D0;
	Wed, 13 Feb 2008 05:17:16 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B876828C7B9
	for <mip4@core3.amsl.com>; Wed, 13 Feb 2008 05:17:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RA068SVRMYy4 for <mip4@core3.amsl.com>;
	Wed, 13 Feb 2008 05:17:13 -0800 (PST)
Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.184])
	by core3.amsl.com (Postfix) with ESMTP id CF7CD28C7AE
	for <mip4@ietf.org>; Wed, 13 Feb 2008 05:17:12 -0800 (PST)
Received: by rn-out-0910.google.com with SMTP id a46so19336rne.10
	for <mip4@ietf.org>; Wed, 13 Feb 2008 05:18:35 -0800 (PST)
Received: by 10.142.251.9 with SMTP id y9mr2092841wfh.43.1202908714707;
	Wed, 13 Feb 2008 05:18:34 -0800 (PST)
Received: by 10.142.11.11 with HTTP; Wed, 13 Feb 2008 05:18:34 -0800 (PST)
Message-ID: <d3886a520802130518k7a77de75lb65dcdea70f9286b@mail.gmail.com>
Date: Wed, 13 Feb 2008 13:18:34 +0000
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Henrik Levkowetz" <henrik@levkowetz.com>
In-Reply-To: <47B210A5.1010902@levkowetz.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <47B07027.6010502@ericsson.com>
	<d3886a520802120422w1e97e076r7893aa039b7de395@mail.gmail.com>
	<47B210A5.1010902@levkowetz.com>
Cc: Henrik Levkowetz <henrik.levkowetz@ericsson.com>,
	Hesham Soliman <Hesham@elevatemobile.com>, mip4-chairs@tools.ietf.org,
	George Tsirtsis <tsirtsis@qualcomm.com>, MIP4 Mailing list <mip4@ietf.org>,
	Vincent Park <vpark@qualcomm.com>
Subject: Re: [Mip4] Shepherd read-through of draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi Henrik,

I pointed to the right section as you suggested and I changed the
terminology. Now the extensions are:
"IPv6 Prefix Request" and "IPv6 Prefix Reply". I think this makes a
lot of sense and I do not mind it is late in the game.

I am going to publish the draft now and any further nits we can deal
with in the AD review.

Thanks again for your help.

George

On Feb 12, 2008 9:33 PM, Henrik Levkowetz <henrik@levkowetz.com> wrote:
> Hi George,
>
> On 2008-02-12 13:22 George Tsirtsis said the following:
>
> > Hi Henrik,
> >
> > I have reviewed your comments and suggested changes and have accepted
> > I think all of them. Below I removed all the corrections accepted
> > outright and just provide responses and alternative text where more
> > significant text changes have been made. If you could have a quick
> > look before I publish the new version it would be good.
> >
> > Thanks again for the review.
> > George
> >
> > On Feb 11, 2008 3:56 PM, Henrik Levkowetz <henrik.levkowetz@ericsson.com> wrote:
> >> Hi,
> >>
> >> I've done the required shepherd's read through of this document, and
> >> found only one thing which would cause comments in the shepherd
> >> writeup, which is is a missing specification of the return code numbering
> >> space in the IANA Considerations section.
> >>
> >> There are a bunch of editorial comments and possible language
> >> clarifications, though; since it seems we're doing one more rev based
> >> on the recent comments on the list, the authors might want to fold in
> >> these in the new rev, too?
> >>
> >>
> >> Regards,
> >>
> >>         Henrik
> >>
> >> ------------------------------------------------------------------------
> > ...
> >>   It seems to me that with this you've covered the case of no IPv6 code
> >>   extensions at all in the reply, and (although not clearly expressed)
> >>   the case where the HA responds with an IPv6 code extension for each
> >>   IPv6 prefix extension.  But what about a reply which only contains
> >>   IPv6 code extensions for some of the prefix extensions, but not all?
> >>   Is this permitted?  How should it be handled?
> >>
> >
> > GT> Good point. I rephrased the last paragraph to say this:
> >                   " Consequently, home agent implementations of this
> >                     specification SHOULD include, in the registration reply
> >                     messages, an IPv6 code extension for each IPv6 prefix
> >                     extension included in the corresponding registration request
> >                     message"
>
> Umm. Yes. But there's no indication of what happens if the HA doesn't
> comply, which is what I really was wondering about.  You actually describe
> that in detail later, but you might point forward to the right section here
> by saying something like "A detailed description of how the mobile node
> handles different IPv6 code extension code values and absent IPv6 code
> extensions is given in Section ...."
>
> Hmm.  That makes me realize something which bothered me a bit earlier --
> the extension name 'IPv6 code extension' is a bit - umm, imprecise.  Have
> you considered any other names?  IPv6 prefix reply extension?  It's late
> in the game, so I wouldn't insist on any change here, but I realized that
> I'd reacted to this a bit during the previous read-through when I saw the
> sentence I proposed above...
>
> >> Section 4.3., paragraph 2:
> >>
> >>>    For each IPv6 prefix extension included in a valid registration
> >>>    request, a home agent that supports this specification SHOULD include
> >>>    a corresponding IPv6 code extension in the registration reply
> >>>    message.  For each accepted IPv6 prefix the home agent MUST decide
> >>>    the tunneling mode it is going to use and set the Code field of the
> >>>    IPv6 code extension to the appropriate value.  The IPv6 prefix field
> >>>    of each of the IPv6 code extensions included in the registration
> >>>    reply MUST match the IPv6 prefix field of an IPv6 prefix extensions
> >>>    included in the corresponding registration request message.
> >>   And presumably, there must not be conflicting IPv6 code extensions,
> >>   i.e., 2 code extensions matching the same prefix extension?
> >>   Maybe clarify this?
> >>
> >
> > GT> Yes, clarified
>
> Thanks.
>
> >>   The two paragraphs above covers the two cases of prefixes outside
> >>   the HA's prefix list, and DAD checked 128's, but not possible
> >>   over- lap between prefix ranges of different mobile nodes within
> >>   the HA's prefix list.  Shouldn't this also be covered explicitly?
> >>   (It is implicit in the next section, but never said explicitly...)
> >>
> >
> > GT> What about this new wording at the end of the section: "Note that
> > for IPv6 prefixes (rather than addresses), the home
> >                     agent does not have to perform Duplicate Address Detection
> >                     but it MUST check that allocated prefixes are not
> >                     overlapping so that all addresses under each allocated
> >                     prefix are allocated only to a single mobile node at any one
> >                     time"
>
> Splendid.
>
> >> Section 4.3.2., paragraph 7:
> >>
> >>>    A home agent that supports this specification MUST be able to defend
> >>>    IPv4 and IPv6 packets destined to registered mobile nodes according
> >>>    to mechanisms described in MIPv4 [RFC3344] and MIPv6 [RFC3775]
> >>>    specifications.
> >>   I find this a weird formulation. You defend an address, but forward
> >>   (or drop) packets, no?  Did you mean defend the addresses here? or
> >>   forward packets?
> >>
> >
> > GT> Yes, good catch, rephrased to:
> > "A home agent that supports this specification MUST be
> >                         able to defend IPv4 and IPv6 addresses
> >                         registered by mobile nodes according to mechanisms
> >                         described in..."
>
> Excellent.
>
>
> >> Section 4.3.2., paragraph 14:
> >>
> >>>    The home agent SHOULD check that all IPv6 packets received from the
> >>>    mobile node over a tunnel from the home address or the care-of
> >>>    address, include a source address that falls under the registered
> >>>    IPv6 prefix(es) for that mobile node.  If the source address of a
> >>>    tunneled packet is not the registered IPv4 care-of address or the
> >>>    registered IPv4 home addresses, the packet SHOULD be dropped.  If the
> >>>    source address of the encapsulated packet does not match any of the
> >>>    registered home addresses and/or prefixes the packet SHOULD be
> >>>    dropped.
> >>   The text on the IPv4 address check could need some clarification --
> >>   is 'a tunnelled packet' 1) the inner packet or 2) the inner packet
> >>   plus encapsulation?  Normally the first, but it seems you here use
> >>   it as if it means the second...
> >>
> >
> > GT> Yes, the text is not clear enough. How is this?:
> > "The home agent SHOULD check that all inner IPv6 packets
> >                         received from the mobile node over a tunnel with outer
> >                         source address the home address or the care-of address,
> >                         include a source address that falls under the registered
> >                         IPv6 prefix(es) for that mobile node. If the source
> >                         address of the outer header of a tunneled packet is not
> >                         the registered IPv4 care-of address or the registered
> >                         IPv4 home addresses, the packet SHOULD be dropped. If
> >                         the source address of the inner header of an
> >                         tunneled packet does not match any of the registered
> >                         home addresses and/or prefixes the packet SHOULD be
> >                         dropped."
>
> Good.
>
> >> Section 4.6.1., paragraph 3:
> >>
> >>>    A mobile node MAY include one or more IPv6 prefix extensions with the
> >>>    IPv6 Prefix field set to ::interface_identifier, where
> >>>    interface_identifier is the unique layer 2 address of the client.
> >>>    The interface_identifier MUST be less than or equal to 64 bits in
> >>>    length.  In this case the prefix length field SHOULD be set to 128.
> >>   Why isn't this specified as MUST?  I don't see any benefit of
> >>   specifying it as a SHOULD, only possible confusion...
> >>
> >
> > GT> Yes, true, corrected.
>
> Good.
>
> > ..
> >>
> >> Section 6:
> >>
> >>   In addition to the IANA actions already described, I believe there is
> >>   an additional new number space for the return codes of the DSMIPv4
> >>   code extension, which need to be established by IANA and have the
> >>   codes defined in this spedification registered.
> >>
> >>
> > GT> Yes, good. I added the following as a paragraph before the last one.:
> > "Finally, this specification creates a new space for the Code
> >                 field of the IPv6 code extension. Values 0, 1, 8, 9, 10, 11 are
> >                 defined in this specification. Values 0-7 are reserved for
> >                 accept codes and the rest of the values are reserved for reject
> >                 values."
>
> Ah.  Good.
>
>
>         Henrik
>
>
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb 13 05:30:06 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2E1D528C84C;
	Wed, 13 Feb 2008 05:30:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vDIAhbebybji; Wed, 13 Feb 2008 05:30:05 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 77D0928C7EC;
	Wed, 13 Feb 2008 05:30:04 -0800 (PST)
X-Original-To: mip4@ietf.org
Delivered-To: mip4@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 85F703A6F62; Wed, 13 Feb 2008 05:30:01 -0800 (PST)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080213133001.85F703A6F62@core3.amsl.com>
Date: Wed, 13 Feb 2008 05:30:01 -0800 (PST)
Cc: mip4@ietf.org
Subject: [Mip4] I-D Action:draft-ietf-mip4-dsmipv4-06.txt
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobility for IPv4 Working Group of the IETF.


	Title           : Dual Stack Mobile IPv4
	Author(s)       : G. Tsirtsis, et al.
	Filename        : draft-ietf-mip4-dsmipv4-06.txt
	Pages           : 27
	Date            : 2008-02-13

This specification provides IPv6 extensions to the Mobile IPv4
protocol.  The extensions allow a dual stack node to use IPv4 and
IPv6 home addresses as well as to move between IPv4 and dual stack
network infrastructures.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip4-dsmipv4-06.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-mip4-dsmipv4-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mip4-dsmipv4-06.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2008-02-13052707.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip4-dsmipv4-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mip4-dsmipv4-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-02-13052707.I-D\@ietf.org>


--OtherAccess--

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

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

--NextPart--


From mip4-bounces@ietf.org  Wed Feb 13 06:28:45 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC93428C7A7;
	Wed, 13 Feb 2008 06:28:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5
	tests=[AWL=-1.540, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kcfoIvDqsz8L; Wed, 13 Feb 2008 06:28:44 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BAA7C3A6CC1;
	Wed, 13 Feb 2008 06:28:44 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C4C1E3A6CC1
	for <mip4@core3.amsl.com>; Wed, 13 Feb 2008 06:28:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id eWWgLYaeqg5T for <mip4@core3.amsl.com>;
	Wed, 13 Feb 2008 06:28:42 -0800 (PST)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [194.146.105.14])
	by core3.amsl.com (Postfix) with ESMTP id C2BBE3A6C96
	for <mip4@ietf.org>; Wed, 13 Feb 2008 06:28:42 -0800 (PST)
Received: from wdhcp-158-110.verkstad.net ([192.36.158.110]:54339)
	by merlot.tools.ietf.org with esmtpsa (TLS-1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.69) (envelope-from <henrik@levkowetz.com>)
	id 1JPIcW-0003io-M2; Wed, 13 Feb 2008 15:29:57 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
To: George Tsirtsis <tsirtsis@googlemail.com>
In-Reply-To: <d3886a520802130518k7a77de75lb65dcdea70f9286b@mail.gmail.com>
X-Mailer: iPhone Mail (1C28)
References: <47B07027.6010502@ericsson.com>
	<d3886a520802120422w1e97e076r7893aa039b7de395@mail.gmail.com>
	<47B210A5.1010902@levkowetz.com>
	<d3886a520802130518k7a77de75lb65dcdea70f9286b@mail.gmail.com>
Message-Id: <866891F7-DDCF-4A46-A9DD-8BFA3F15F5A4@levkowetz.com>
Mime-Version: 1.0 (iPhone Mail 1C28)
Date: Wed, 13 Feb 2008 15:26:30 +0100
X-SA-Exim-Connect-IP: 192.36.158.110
X-SA-Exim-Rcpt-To: tsirtsis@googlemail.com, henrik.levkowetz@ericsson.com,
	vpark@qualcomm.com, mip4-chairs@tools.ietf.org,
	tsirtsis@qualcomm.com, mip4@ietf.org, Hesham@elevatemobile.com,
	henrik@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Tue, 21 Aug 2007 23:39:36 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: Henrik Levkowetz <henrik.levkowetz@ericsson.com>,
	Hesham Soliman <Hesham@elevatemobile.com>,
	"mip4-chairs@tools.ietf.org" <mip4-chairs@tools.ietf.org>,
	George Tsirtsis <tsirtsis@qualcomm.com>, MIP4 Mailing list <mip4@ietf.org>,
	Vincent Park <vpark@qualcomm.com>
Subject: Re: [Mip4] Shepherd read-through of draft-ietf-mip4-dsmipv4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi George,

On Feb 13, 2008, at 2:18 PM, "George Tsirtsis"  
<tsirtsis@googlemail.com> wrote:

> Hi Henrik,
>
> I pointed to the right section as you suggested and I changed the
> terminology. Now the extensions are:
> "IPv6 Prefix Request" and "IPv6 Prefix Reply". I think this makes a
> lot of sense and I do not mind it is late in the game.
>
> I am going to publish the draft now and any further nits we can deal
> with in the AD review.

Great. I'll complete and submit the shepherd's writeup and publication  
request.

Regards,

     Henrik


> Thanks again for your help.
>
> George
>
> On Feb 12, 2008 9:33 PM, Henrik Levkowetz <henrik@levkowetz.com>  
> wrote:
>> Hi George,
>>
>> On 2008-02-12 13:22 George Tsirtsis said the following:
>>
>>> Hi Henrik,
>>>
>>> I have reviewed your comments and suggested changes and have  
>>> accepted
>>> I think all of them. Below I removed all the corrections accepted
>>> outright and just provide responses and alternative text where more
>>> significant text changes have been made. If you could have a quick
>>> look before I publish the new version it would be good.
>>>
>>> Thanks again for the review.
>>> George
>>>
>>> On Feb 11, 2008 3:56 PM, Henrik Levkowetz <henrik.levkowetz@ericsson.com 
>>> > wrote:
>>>> Hi,
>>>>
>>>> I've done the required shepherd's read through of this document,  
>>>> and
>>>> found only one thing which would cause comments in the shepherd
>>>> writeup, which is is a missing specification of the return code  
>>>> numbering
>>>> space in the IANA Considerations section.
>>>>
>>>> There are a bunch of editorial comments and possible language
>>>> clarifications, though; since it seems we're doing one more rev  
>>>> based
...
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb 13 08:09:45 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BEE9228C87F;
	Wed, 13 Feb 2008 08:09:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.972
X-Spam-Level: 
X-Spam-Status: No, score=-0.972 tagged_above=-999 required=5
	tests=[AWL=-0.535, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1mD4LqZXGcaS; Wed, 13 Feb 2008 08:09:44 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5CA7C3A6FA2;
	Wed, 13 Feb 2008 08:09:41 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 67A7B3A6F9B;
	Wed, 13 Feb 2008 08:09:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XejVPP2G8jHr; Wed, 13 Feb 2008 08:09:38 -0800 (PST)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 4EF7428C8AD;
	Wed, 13 Feb 2008 08:09:14 -0800 (PST)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	23715214FE; Wed, 13 Feb 2008 17:10:36 +0100 (CET)
X-AuditID: c1b4fb3e-a91fcbb000000b15-81-47b3167bee96
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	E9C4B2120F; Wed, 13 Feb 2008 17:10:35 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Feb 2008 17:10:35 +0100
Received: from [147.214.22.209] ([147.214.22.209]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Feb 2008 17:10:35 +0100
Message-ID: <47B3167B.7020706@ericsson.com>
Date: Wed, 13 Feb 2008 17:10:35 +0100
From: Henrik Levkowetz <henrik.levkowetz@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: IESG Secretary <iesg-secretary@ietf.org>
X-Enigmail-Version: 0.95.6
X-OriginalArrivalTime: 13 Feb 2008 16:10:35.0410 (UTC)
	FILETIME=[F73C5F20:01C86E5A]
X-Brightmail-Tracker: AAAAAA==
Cc: mip4-chairs@tools.ietf.org, int-ads@tools.ietf.org,
	MIP4 Mailing list <mip4@ietf.org>
Subject: [Mip4] Publication Request: draft-ietf-mip4-dsmipv4-06.txt
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi,

This is a request to the IESG to consider draft-ietf-mip4-dsmipv4-06.txt
for publication as an RFC.

I enclose the Document Shepherd Questionnaire, below.

Regards,

	Henrik

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


   (1.a)  Who is the Document Shepherd for this document?  Has the
          Document Shepherd personally reviewed this version of the
          document and, in particular, does he or she believe this
          version is ready for forwarding to the IESG for publication?

	* Henrik Levkowetz, MIP4 co-chair
	* Reviewed, yes
	* Ready, yes.
	  RFC-editor: please change "IPv6 packetm" to "IPv6 packet,"
	  in para. 10 of Section 4.3.2.

   (1.b)  Has the document had adequate review both from key WG members
          and from key non-WG members?  Does the Document Shepherd have
          any concerns about the depth or breadth of the reviews that
          have been performed?

	* Yes
	* No

   (1.c)  Does the Document Shepherd have concerns that the document
          needs more review from a particular or broader perspective,
          e.g., security, operational complexity, someone familiar with
          AAA, internationalization or XML?

	* No

   (1.d)  Does the Document Shepherd have any specific concerns or
          issues with this document that the Responsible Area Director
          and/or the IESG should be aware of?  For example, perhaps he
          or she is uncomfortable with certain parts of the document, or
          has concerns whether there really is a need for it.  In any
          event, if the WG has discussed those issues and has indicated
          that it still wishes to advance the document, detail those
          concerns here.  Has an IPR disclosure related to this document
          been filed?  If so, please include a reference to the
          disclosure and summarize the WG discussion and conclusion on
          this issue.

	* No concerns
	* No IPR disclosures

   (1.e)  How solid is the WG consensus behind this document?  Does it
          represent the strong concurrence of a few individuals, with
          others being silent, or does the WG as a whole understand and
          agree with it?

	* The WG last call was generally positive, but raised some
	  issues.  These have all been handled in version -06.

   (1.f)  Has anyone threatened an appeal or otherwise indicated extreme
          discontent?  If so, please summarise the areas of conflict in
          separate email messages to the Responsible Area Director.  (It
          should be in a separate email because this questionnaire is
          entered into the ID Tracker.)

	* No threat of appeal or other discontent.

   (1.g)  Has the Document Shepherd personally verified that the
          document satisfies all ID nits?  (See
          http://www.ietf.org/ID-Checklist.html and
          http://tools.ietf.org/tools/idnits/).  Boilerplate checks are
          not enough; this check needs to be thorough.  Has the document
          met all formal review criteria it needs to, such as the MIB
          Doctor, media type and URI type reviews?

	* Idnits check passed, plus manual verification as needed, including:
		- Network byte order
		- IANA considerations
		- Author Address
		- Meaningful Abstract
		- Meaningful Security Considerations
		- Not outdateable text
		- Protocol behaviour characteristics

   (1.h)  Has the document split its references into normative and
          informative?  Are there normative references to documents that
          are not ready for advancement or are otherwise in an unclear
          state?  If such normative references exist, what is the
          strategy for their completion?  Are there normative references
          that are downward references, as described in [RFC3967]?  If
          so, list these downward references to support the Area
          Director in the Last Call procedure for them [RFC3967].

	* Reference split OK (this is covered by 1.g)
	* No references to documents not ready for advancements
	* No downward refs

   (1.i)  Has the Document Shepherd verified that the document IANA
          consideration section exists and is consistent with the body
          of the document?  If the document specifies protocol
          extensions, are reservations requested in appropriate IANA
          registries?  Are the IANA registries clearly identified?  If
          the document creates a new registry, does it define the
          proposed initial contents of the registry and an allocation
          procedure for future registrations?  Does it suggest a
          reasonable name for the new registry?  See [RFC2434].  If the
          document describes an Expert Review process has Shepherd
          conferred with the Responsible Area Director so that the IESG
          can appoint the needed Expert during the IESG Evaluation?

	* IANA considerations verified (this is covered by 1.g)
	* All other items of 1.i verified

   (1.j)  Has the Document Shepherd verified that sections of the
          document that are written in a formal language, such as XML
          code, BNF rules, MIB definitions, etc., validate correctly in
          an automated checker?

	* Not applicable

   (1.k)  The IESG approval announcement includes a Document
          Announcement Write-Up.  Please provide such a Document
          Announcement Write-Up?  Recent examples can be found in the
          "Action" announcements for approved documents.  The approval
          announcement contains the following sections:

          Technical Summary

	*   "This specification provides extensions to the Mobile IPv4
	    protocol, which allow a dual stack node to use both IPv4 and
	    IPv6 home addresses, while moving between IPv4 and dual stack
	    network attachment points."

          Working Group Summary
             Was there anything in WG process that is worth noting?  For
             example, was there controversy about particular points or
             were there decisions where the consensus was particularly
             rough?

	* Nothing to note.

          Document Quality
             Are there existing implementations of the protocol?  Have a
             significant number of vendors indicated their plan to
             implement the specification?  Are there any reviewers that
             merit special mention as having done a thorough review,
             e.g., one that resulted in important changes or a
             conclusion that the document had no substantive issues?  If
             there was a MIB Doctor, Media Type or other expert review,
             what was its course (briefly)?  In the case of a Media Type
             review, on what date was the request posted?

	* The protocol has been implemented by Flarion, and an internal
	  implementation has also been made at IPunplugged.  The shepherd
	  does not have further knowledge of implementation plans (although
	  he'd guess that Cisco has already implemented this, and if not,
	  will shortly do so).
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb 15 06:00:06 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0788428D1BB;
	Fri, 15 Feb 2008 06:00:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Ap3qtI3p6irW; Fri, 15 Feb 2008 06:00:03 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 30E303A6ACA;
	Fri, 15 Feb 2008 06:00:03 -0800 (PST)
X-Original-To: mip4@ietf.org
Delivered-To: mip4@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 1CD7D3A695E; Fri, 15 Feb 2008 06:00:01 -0800 (PST)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080215140002.1CD7D3A695E@core3.amsl.com>
Date: Fri, 15 Feb 2008 06:00:02 -0800 (PST)
Cc: mip4@ietf.org
Subject: [Mip4] I-D Action:draft-ietf-mip4-nemov4-fa-02.txt
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobility for IPv4 Working Group of the IETF.


	Title           : FA extensions to NEMOv4 Base
	Author(s)       : G. Tsirtsis, et al.
	Filename        : draft-ietf-mip4-nemov4-fa-02.txt
	Pages           : 15
	Date            : 2008-02-15

The base NEMOv4 specification defines extensions to Mobile IPv4 for
mobile networks.  NEMOv4 extensions are defined for use only by the
mobile node and the home agent.  This specification introduces
extensions for NEMO support on the foreign agent.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemov4-fa-02.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-mip4-nemov4-fa-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mip4-nemov4-fa-02.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2008-02-15055803.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip4-nemov4-fa-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mip4-nemov4-fa-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-02-15055803.I-D\@ietf.org>


--OtherAccess--

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

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

--NextPart--


From mip4-bounces@ietf.org  Fri Feb 15 06:04:48 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B99A028D1AD;
	Fri, 15 Feb 2008 06:04:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.039
X-Spam-Level: *
X-Spam-Status: No, score=1.039 tagged_above=-999 required=5 tests=[AWL=0.854,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sYQUNHnM6QC9; Fri, 15 Feb 2008 06:04:48 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F0D5A3A6A47;
	Fri, 15 Feb 2008 06:04:47 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A9D193A68AE
	for <mip4@core3.amsl.com>; Fri, 15 Feb 2008 06:04:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Xj6D-ZMgVySq for <mip4@core3.amsl.com>;
	Fri, 15 Feb 2008 06:04:45 -0800 (PST)
Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.180])
	by core3.amsl.com (Postfix) with ESMTP id 9CD2D3A6ACA
	for <mip4@ietf.org>; Fri, 15 Feb 2008 06:04:00 -0800 (PST)
Received: by el-out-1112.google.com with SMTP id j27so812761elf.25
	for <mip4@ietf.org>; Fri, 15 Feb 2008 06:05:20 -0800 (PST)
Received: by 10.143.40.18 with SMTP id s18mr2268418wfj.168.1203084320185;
	Fri, 15 Feb 2008 06:05:20 -0800 (PST)
Received: by 10.142.177.9 with HTTP; Fri, 15 Feb 2008 06:05:20 -0800 (PST)
Message-ID: <d3886a520802150605kdeb7e16j13c4463500f5210b@mail.gmail.com>
Date: Fri, 15 Feb 2008 14:05:20 +0000
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "MIP4 Mailing list" <mip4@ietf.org>
MIME-Version: 1.0
Content-Disposition: inline
Subject: [Mip4] draft-ietf-mip4-nemov4-fa-02
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi all,

I just published v02 of the nemov4 FA support draft to add a proper
IANA section, fix nits, and make some other minor corrections.
When nemov4-base gets published we will be able to use the correct
Type number assigned by IANA for the extension defined in this draft
and then I think we will be good to go.

If you have any other comments please let me know.

George
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb 17 23:40:23 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CCFE528C1BA;
	Sun, 17 Feb 2008 23:40:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level: 
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5
	tests=[AWL=-1.961, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id NuSjHL8H4zhe; Sun, 17 Feb 2008 23:40:22 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 96E5E3A6C97;
	Sun, 17 Feb 2008 23:40:22 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 71C083A6C97
	for <mip4@core3.amsl.com>; Sun, 17 Feb 2008 23:40:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id oDhye8qsioNE for <mip4@core3.amsl.com>;
	Sun, 17 Feb 2008 23:40:20 -0800 (PST)
Received: from mail119.messagelabs.com (mail119.messagelabs.com
	[216.82.241.179])
	by core3.amsl.com (Postfix) with SMTP id 556B93A6C8F
	for <mip4@ietf.org>; Sun, 17 Feb 2008 23:40:20 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-7.tower-119.messagelabs.com!1203320417!36357679!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 2765 invoked from network); 18 Feb 2008 07:40:17 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-7.tower-119.messagelabs.com with SMTP;
	18 Feb 2008 07:40:17 -0000
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id m1I7eHje020122
	for <mip4@ietf.org>; Mon, 18 Feb 2008 00:40:17 -0700 (MST)
Received: from il06vts03.mot.com (il06vts03.mot.com [129.188.137.143])
	by il06exr03.mot.com (8.13.1/Vontu) with SMTP id m1I7eH53026511
	for <mip4@ietf.org>; Mon, 18 Feb 2008 01:40:17 -0600 (CST)
Received: from [127.0.0.1] ([10.129.40.110])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id m1I7eFal026496
	for <mip4@ietf.org>; Mon, 18 Feb 2008 01:40:16 -0600 (CST)
Message-ID: <47B9365F.8040006@gmail.com>
Date: Mon, 18 Feb 2008 08:40:15 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Mobile IPv4 Mailing List <mip4@ietf.org>
Content-Type: multipart/mixed; boundary="------------050909080609090207000705"
X-Antivirus: avast! (VPS 080217-0, 17/02/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
Subject: [Mip4] [Fwd: New Version Notification for
	draft-ietf-mip4-nemo-v4-base-09]
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.
--------------050909080609090207000705
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Dear MIP4 WG,

Following IANA and IESG review I submitted a new version of this draft. 
  The main modifications are corrections on Code behaviour, a new 
extended Introduction section and a enhanced encoding of the Prefix 
fields (now it includes a non-contiguous netmask as well) and mentioning 
of manageability of Mobile Routers.

The included Change Log is:
>   From draft-ietf-mip4-nemo-v4-base-08.txt to
>    draft-ietf-mip4-nemo-v4-base-09.txt, following IANA and IESG
>    comments:
> 
>    o  Introduced an Optional Netmask field in both registrations and
>       replies.  This is used when address/prefixlength is not a
>       sufficient expression of network mask, for example when the subnet
>       mask needs to be expressed as a non-contiguous set of 1bits (e.g.
>       255.255.0.255).  Also described the reasoning of this in a section
>       of its own.
> 
>    o  Extended the Introduction section with two subsections: example of
>       mobile network and overall protocol operation.  Illustrated two
>       figures.
> 
>    o  Added Local Fixed Node term definition and some citations to
>       reference rfc4885 "Network Mobility Support Terminology".
> 
>    o  Clarified text about the Code field.  There are two Code fields:
>       one in Registration Reply header (the Code proper) and one in the
>       Mobile Network Extension header.  Also clarified conditions of
>       proper Code being 0 successful and and relationships of proper
>       Code 0 to Code in the Mobile Network Extension.
> 
>    o  Added a sub-section 'Mobile Router Management' about the initial
>       configuration, ongoing supervision and management indicators of a
>       Mobile Router and Home Agent.
> 
>    o  Substituted 'MOBNET_UNAUTHORIZED' for 'MOBNET_UNAUTHORIZED_MR'.
> 
>    o  Substituted 'IANA to assign rules' for 'IANA to modify rules'.
> 
>    o  Stressed that "applications that do not support MTU discovery are
>       adversely affected by the additional header encapsulations,
>       because the usable MTU is reduced with each level of nesting."
> 
>    o  Removed citations and reference to rfc3344bis
>       (draft-ietf-mip4-rfc3344bis-05).
> 
>    o  Removed citations and reference to rfc2434bis
>       (draft-narten-iana-considerations-rfc2434bis-08).
> 
>    o  Extended the Acknowledgements section.


Alex


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________
--------------050909080609090207000705
Content-Type: message/rfc822;
 name="New Version Notification for draft-ietf-mip4-nemo-v4-base-09.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename*0="New Version Notification for draft-ietf-mip4-nemo-v4-base-09";
 filename*1=".eml"

Received: from zuk35exm63.ds.mot.com ([10.178.4.20]) by zuk35exm62.ds.mot.com with Microsoft SMTPSVC(6.0.3790.2709);
	 Mon, 18 Feb 2008 07:33:29 +0000
Received: from il06exr04.mot.com ([129.188.137.134]) by zuk35exm63.ds.mot.com with Microsoft SMTPSVC(6.0.3790.2709);
	 Mon, 18 Feb 2008 07:33:28 +0000
Received: from motgate7.mot.com (motgate7.mot.com [129.188.136.7])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id m1I7XRca005805
	for <alexandru.petrescu@motorola.com>; Mon, 18 Feb 2008 01:33:27 -0600 (CST)
Received: from mail128.messagelabs.com (mail128.messagelabs.com [216.82.250.131])
	by motgate7.mot.com (8.12.11/Motorola) with SMTP id m1I7XQQg023481
	for <alexandru.petrescu@motorola.com>; Mon, 18 Feb 2008 00:33:27 -0700 (MST)
X-VirusChecked: Checked
X-Env-Sender: wwwrun@core3.amsl.com
X-Msg-Ref: server-7.tower-128.messagelabs.com!1203320005!2468383!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [64.170.98.32]
X-SpamReason: No, hits=0.0 required=7.0 tests=
Received: (qmail 2171 invoked from network); 18 Feb 2008 07:33:25 -0000
Received: from mail.ietf.org (HELO mail.ietf.org) (64.170.98.32)
  by server-7.tower-128.messagelabs.com with SMTP; 18 Feb 2008 07:33:25 -0000
Received: by core3.amsl.com (Postfix, from userid 30)
	id EC1123A6B23; Sun, 17 Feb 2008 23:33:26 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: "Alexandru Petrescu"<alexandru.petrescu@motorola.com>
Cc: <kleung@cisco.com>, <gdommety@cisco.com>, <vidyan@qualcomm.com>
From: IETF I-D Submission Tool<idsubmission@ietf.org>
Subject: New Version Notification for draft-ietf-mip4-nemo-v4-base-09 
Message-Id: <20080218073326.EC1123A6B23@core3.amsl.com>
Date: Sun, 17 Feb 2008 23:33:26 -0800 (PST)
Return-Path: wwwrun@core3.amsl.com
X-OriginalArrivalTime: 18 Feb 2008 07:33:28.0955 (UTC) FILETIME=[8E17CCB0:01C87200]
X-Antivirus: avast! (VPS 080217-0, 17/02/2008), Inbound message
X-Antivirus-Status: Clean


A new version of I-D, draft-ietf-mip4-nemo-v4-base-09.txt has been successfuly submitted by Alexandru Petrescu and posted to the IETF repository.

Filename:	 draft-ietf-mip4-nemo-v4-base
Revision:	 09
Title:		 Network Mobility (NEMO) Extensions for Mobile IPv4
Creation_date:	 2008-02-17
WG ID:		 mip4
Number_of_pages: 32

Abstract:
This document describes a protocol for supporting Mobile Networks
between a Mobile Router and a Home Agent by extending the Mobile IPv4
protocol.  A Mobile Router is responsible for the mobility of one or
more network segments or subnets moving together.  The Mobile Router
hides its mobility from the nodes on the mobile network.  The nodes
on the Mobile Network may be fixed in relationship to the Mobile
Router and may not have any mobility function.

Extensions to Mobile IPv4 are introduced to support Mobile Networks.
                                                                                  


The IETF Secretariat.



--------------050909080609090207000705
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: http://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--------------050909080609090207000705--


From mip4-bounces@ietf.org  Sun Feb 17 23:45:10 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A608328C214;
	Sun, 17 Feb 2008 23:45:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vr+GKob8DkUu; Sun, 17 Feb 2008 23:45:06 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3B08B28C246;
	Sun, 17 Feb 2008 23:45:06 -0800 (PST)
X-Original-To: mip4@ietf.org
Delivered-To: mip4@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 5DAE23A6C97; Sun, 17 Feb 2008 23:45:01 -0800 (PST)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080218074501.5DAE23A6C97@core3.amsl.com>
Date: Sun, 17 Feb 2008 23:45:01 -0800 (PST)
Cc: mip4@ietf.org
Subject: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-09.txt
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobility for IPv4 Working Group of the IETF.


	Title           : Network Mobility (NEMO) Extensions for Mobile IPv4
	Author(s)       : K. Leung, et al.
	Filename        : draft-ietf-mip4-nemo-v4-base-09.txt
	Pages           : 32
	Date            : 2008-02-17

This document describes a protocol for supporting Mobile Networks
between a Mobile Router and a Home Agent by extending the Mobile IPv4
protocol.  A Mobile Router is responsible for the mobility of one or
more network segments or subnets moving together.  The Mobile Router
hides its mobility from the nodes on the mobile network.  The nodes
on the Mobile Network may be fixed in relationship to the Mobile
Router and may not have any mobility function.

Extensions to Mobile IPv4 are introduced to support Mobile Networks.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-09.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-mip4-nemo-v4-base-09.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-09.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2008-02-17233326.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-09.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mip4-nemo-v4-base-09.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-02-17233326.I-D\@ietf.org>


--OtherAccess--

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

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

--NextPart--


From mip4-bounces@ietf.org  Mon Feb 18 03:15:08 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9543428C366;
	Mon, 18 Feb 2008 03:15:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.594
X-Spam-Level: 
X-Spam-Status: No, score=-2.594 tagged_above=-999 required=5 tests=[AWL=0.005,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dAN7IjJs7uHe; Mon, 18 Feb 2008 03:15:07 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5279228C358;
	Mon, 18 Feb 2008 03:15:03 -0800 (PST)
X-Original-To: mip4@ietf.org
Delivered-To: mip4@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 527E128C326; Mon, 18 Feb 2008 03:15:00 -0800 (PST)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080218111501.527E128C326@core3.amsl.com>
Date: Mon, 18 Feb 2008 03:15:01 -0800 (PST)
Cc: mip4@ietf.org
Subject: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-10.txt
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobility for IPv4 Working Group of the IETF.


	Title           : Network Mobility (NEMO) Extensions for Mobile IPv4
	Author(s)       : K. Leung, et al.
	Filename        : draft-ietf-mip4-nemo-v4-base-10.txt
	Pages           : 32
	Date            : 2008-02-18

This document describes a protocol for supporting Mobile Networks
between a Mobile Router and a Home Agent by extending the Mobile IPv4
protocol.  A Mobile Router is responsible for the mobility of one or
more network segments or subnets moving together.  The Mobile Router
hides its mobility from the nodes on the mobile network.  The nodes
on the Mobile Network may be fixed in relationship to the Mobile
Router and may not have any mobility function.

Extensions to Mobile IPv4 are introduced to support Mobile Networks.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-10.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-mip4-nemo-v4-base-10.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-10.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2008-02-18030630.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-10.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mip4-nemo-v4-base-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-02-18030630.I-D\@ietf.org>


--OtherAccess--

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

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

--NextPart--


From mip4-bounces@ietf.org  Fri Feb 22 08:55:37 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 26B1028C389;
	Fri, 22 Feb 2008 08:55:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.664
X-Spam-Level: 
X-Spam-Status: No, score=-0.664 tagged_above=-999 required=5
	tests=[AWL=-0.527, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, MIME_8BIT_HEADER=0.3, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Y8ABefRflXT3; Fri, 22 Feb 2008 08:55:36 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3D4D728C372;
	Fri, 22 Feb 2008 08:55:36 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9376828C377
	for <mip4@core3.amsl.com>; Fri, 22 Feb 2008 08:55:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id m9tA3FSb-fsw for <mip4@core3.amsl.com>;
	Fri, 22 Feb 2008 08:55:33 -0800 (PST)
Received: from smtp.inet.fi (smtp.inet.fi [192.89.123.192])
	by core3.amsl.com (Postfix) with ESMTP id BF20828C339
	for <mip4@ietf.org>; Fri, 22 Feb 2008 08:55:33 -0800 (PST)
Received: from lohi.mit.sonera.com (lohi.mit.sonera.com [192.194.74.130])
	by smtp.inet.fi (Postfix) with ESMTP id 24AA16E32
	for <mip4@ietf.org>; Fri, 22 Feb 2008 18:55:28 +0200 (EET)
Received: from lohi.mit.sonera.com (localhost [127.0.0.1])
	by lohi.mit.sonera.com (Postfix) with ESMTP id E12A28DE4B
	for <mip4@ietf.org>; Fri, 22 Feb 2008 18:45:53 +0200 (EET)
Received: from suutari.mit.sonera.com (suutari.mit.sonera.com [194.142.21.7])
	by lohi.mit.sonera.com (Postfix) with ESMTP id CB51A8DE4A
	for <mip4@ietf.org>; Fri, 22 Feb 2008 18:45:53 +0200 (EET)
Received: from suutari.mit.sonera.com (suutari.mit.sonera.com [194.142.21.7])
	by suutari.mit.sonera.com (Postfix) with ESMTP id DC212C2EA0
	for <mip4@ietf.org>; Fri, 22 Feb 2008 18:55:21 +0200 (EET)
Date: Fri, 22 Feb 2008 18:55:21 +0200 (EET)
From: =?ISO-8859-1?Q?Antti_M=E4kel=E4?= <antti.makela@teliasonera.com>
X-X-Sender: makelan2@suutari.mit.sonera.com
To: mip4@ietf.org
Message-ID: <Pine.LNX.4.63.0802221853210.9651@suutari.mit.sonera.com>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED;
	BOUNDARY="-1899886827-1671812328-1203699321=:9651"
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: [Mip4] New version of Haaro
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---1899886827-1671812328-1203699321=:9651
Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8BIT


Just uploaded new version of the route rptimization draft I presented in 
Vancouver.

Biggest changes

  - Adding signaling diagrams
  - Addressing scalability concerns with a compression scheme
  - Addressing (somewhat) concerns on RR, making it optional

http://www.ietf.org/internet-drafts/draft-makela-mip4-nemo-haaro-01.txt

-- 
- Antti Mäkelä | Senior Network Architect | +358 2040 21613 -
- Integrated Enterprise Services / TeliaSonera Corporation -
---1899886827-1671812328-1203699321=:9651
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: http://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

---1899886827-1671812328-1203699321=:9651--


From mip4-bounces@ietf.org  Mon Feb 25 15:09:12 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F08A428C95A;
	Mon, 25 Feb 2008 15:09:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Q06KzRkW-uxw; Mon, 25 Feb 2008 15:09:11 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B521028D0EA;
	Mon, 25 Feb 2008 14:03:22 -0800 (PST)
X-Original-To: mip4@ietf.org
Delivered-To: mip4@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30)
	id DA5BE28D08F; Mon, 25 Feb 2008 14:03:20 -0800 (PST)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20080225220320.DA5BE28D08F@core3.amsl.com>
Date: Mon, 25 Feb 2008 14:03:20 -0800 (PST)
Cc: mip4 chair <mip4-chairs@tools.ietf.org>,
	Internet Architecture Board <iab@iab.org>,
	mip4 mailing list <mip4@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Mip4] Protocol Action: 'Secure Connectivity and Mobility using
 Mobile IPv4 and MOBIKE' to BCP
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

The IESG has approved the following document:

- 'Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE '
   <draft-ietf-mip4-mobike-connectivity-03.txt> as a BCP

This document is the product of the Mobility for IPv4 Working Group. 

The IESG contact persons are Jari Arkko and Mark Townsley.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip4-mobike-connectivity-03.txt

Technical Summary
 
  This document describes the interaction of Mobile IPv4 and MOBIKE.
  The focus is on providing access to an enterprise or operator private
  network where the mobile node can connect either directly on trusted
  links or through a VPN gateway from the untrusted Internet. The
  document outlines various scenarios for the different arrangements of
  VPN and Mobile IP tunnels, and recommends procedures for execution
  upon detection of mobility events.

Working Group Summary

  This document is a product of the Mobile IPv4 working group. It
  has gone through 2 working group last calls and is mature and
  ready for publication.

Document Quality

  The specification has been reviewed by a number of
  WG participants.

Personnel

  Document shepherd: Pete McCann
  Responsible AD: Jari Arkko

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: http://www.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 Feb 29 21:00:57 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: ietfarch-mip4-archive@core3.amsl.com
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 340C73A68D7;
	Fri, 29 Feb 2008 21:00:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.867
X-Spam-Level: 
X-Spam-Status: No, score=-1.867 tagged_above=-999 required=5
	tests=[AWL=-2.430, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3dWFqZJezjsh; Fri, 29 Feb 2008 21:00:53 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 425133A6A73;
	Fri, 29 Feb 2008 21:00:53 -0800 (PST)
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3ABF23A6949
	for <mip4@core3.amsl.com>; Fri, 29 Feb 2008 21:00:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id G6HnXZYChJ7r for <mip4@core3.amsl.com>;
	Fri, 29 Feb 2008 21:00:51 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id 5D9CE3A6DDE
	for <mip4@ietf.org>; Fri, 29 Feb 2008 21:00:51 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.25,430,1199692800"; d="scan'208,217";a="15471741"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-5.cisco.com with ESMTP; 29 Feb 2008 21:00:43 -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 m2150hev025680
	for <mip4@ietf.org>; Fri, 29 Feb 2008 21:00:43 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m2150hCQ025917
	for <mip4@ietf.org>; Sat, 1 Mar 2008 05:00:43 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Feb 2008 21:00:43 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 29 Feb 2008 21:00:41 -0800
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5205910642@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: new PMIPv4 draft
Thread-Index: Ach7WTMR/S6ehC8dQrmi7EAcS+obxg==
From: "Kent Leung (kleung)" <kleung@cisco.com>
To: <mip4@ietf.org>
X-OriginalArrivalTime: 01 Mar 2008 05:00:43.0456 (UTC)
	FILETIME=[33FCA400:01C87B59]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1331; t=1204347643;
	x=1205211643; 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:=20new=20PMIPv4=20draft |Sender:=20;
	bh=wF1jmrl30+ydpxloB6E9WV8L5tKocxg+3Pxud8GlysE=;
	b=gVA4WjTonSYbBFaABxiic+9Gkxcc5ISZQ79L63BysrCcjzTzoQpYGEDxIw
	MsqFw7oMx69mReK++Axa8x3eYX7hu3RHbEF4tpu5rrTryKFLgr5z8V+9hXcX
	0j9ZN8dads;
Authentication-Results: sj-dkim-3; header.From=kleung@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Subject: [Mip4] new PMIPv4 draft
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www.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://www.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1067832691=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1067832691==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C87B59.33D8BFCA"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C87B59.33D8BFCA
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

For those who are following the Proxy Mobile IPv4 draft, the latest
version has been published.
=20
http://tools.ietf.org/wg/mip4/draft-leung-mip4-proxy-mode-07.txt
=20
Kent

------_=_NextPart_001_01C87B59.33D8BFCA
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.3243" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D265215804-01032008>For =
those who are=20
following the Proxy Mobile IPv4 draft, the latest version has been=20
published.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><A=20
href=3D"http://tools.ietf.org/wg/mip4/draft-leung-mip4-proxy-mode-07.txt"=
>http://tools.ietf.org/wg/mip4/draft-leung-mip4-proxy-mode-07.txt</A></FO=
NT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D265215804-01032008><FONT face=3DArial=20
size=3D2>Kent</FONT></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C87B59.33D8BFCA--

--===============1067832691==
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://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1067832691==--


