From mip4-bounces@ietf.org  Fri Apr  4 10:17:05 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EFFF628C40B;
	Fri,  4 Apr 2008 10:17:05 -0700 (PDT)
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 5CAB93A6A7C
	for <mip4@core3.amsl.com>; Fri,  4 Apr 2008 10:17:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Zvcq0wOZ8-hm for <mip4@core3.amsl.com>;
	Fri,  4 Apr 2008 10:16:59 -0700 (PDT)
Received: from mail153.messagelabs.com (mail153.messagelabs.com
	[216.82.253.51]) by core3.amsl.com (Postfix) with SMTP id C11E328C507
	for <mip4@ietf.org>; Fri,  4 Apr 2008 10:16:31 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: pete.mccann@motorola.com
X-Msg-Ref: server-2.tower-153.messagelabs.com!1207329392!8493948!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 31934 invoked from network); 4 Apr 2008 17:16:32 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-2.tower-153.messagelabs.com with SMTP;
	4 Apr 2008 17:16:32 -0000
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id m34HGWs7024619
	for <mip4@ietf.org>; Fri, 4 Apr 2008 10:16:32 -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 m34HGWdx017125
	for <mip4@ietf.org>; Fri, 4 Apr 2008 12:16:32 -0500 (CDT)
Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id m34HGVqb017115
	for <mip4@ietf.org>; Fri, 4 Apr 2008 12:16:31 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 4 Apr 2008 13:16:30 -0400
Message-ID: <BE4B07D4197BF34EB3B753DD34EBCD130272ABAE@de01exm67.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WGLC: draft-ietf-mip4-generic-notification-message-04.txt
thread-index: AciWd5/DNuCke2dhQBqVWbOvHrpBxQ==
From: "McCann Peter-A001034" <pete.mccann@motorola.com>
To: <mip4@ietf.org>
X-CFilter-Loop: Reflected
Cc: henrik@levkowetz.com
Subject: [Mip4] WGLC: 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: <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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

This message announces a 2-week working group last call on:

"Generic Notification Message for Mobile IPv4"          
draft-ietf-mip4-generic-notification-message-04.txt

The last call will end at 24:00 UTC on Friday, April 18 2008.

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


Please respond to this working group last call:

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

    "I support the advancement of this document to the IESG with a
     request for publication as a Proposed Standard RFC."

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


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

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

Please direct all replies to the Mobile IPv4 mailing list,
mip4@ietf.org.


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


From mip4-bounces@ietf.org  Fri Apr  4 10:32:27 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 146DE3A6D39;
	Fri,  4 Apr 2008 10:32:27 -0700 (PDT)
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 8EF663A67D7
	for <mip4@core3.amsl.com>; Fri,  4 Apr 2008 10:32:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Hhv3PGr+NtUg for <mip4@core3.amsl.com>;
	Fri,  4 Apr 2008 10:32:24 -0700 (PDT)
Received: from mail128.messagelabs.com (mail128.messagelabs.com
	[216.82.250.131])
	by core3.amsl.com (Postfix) with SMTP id 0D14228C4E2
	for <mip4@ietf.org>; Fri,  4 Apr 2008 10:31:39 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: pete.mccann@motorola.com
X-Msg-Ref: server-4.tower-128.messagelabs.com!1207330305!23077883!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.189.100.103]
Received: (qmail 16475 invoked from network); 4 Apr 2008 17:31:45 -0000
Received: from motgate3.mot.com (HELO motgate3.mot.com) (144.189.100.103)
	by server-4.tower-128.messagelabs.com with SMTP;
	4 Apr 2008 17:31:45 -0000
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate3.mot.com (8.12.11/Motorola) with ESMTP id m34HVior026960
	for <mip4@ietf.org>; Fri, 4 Apr 2008 10:31:45 -0700 (MST)
Received: from az10vts03 (az10vts03.mot.com [10.64.251.244])
	by az33exr04.mot.com (8.13.1/Vontu) with SMTP id m34HViJS025204
	for <mip4@ietf.org>; Fri, 4 Apr 2008 12:31:44 -0500 (CDT)
Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id m34HVgkX025195
	for <mip4@ietf.org>; Fri, 4 Apr 2008 12:31:43 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 4 Apr 2008 13:31:41 -0400
Message-ID: <BE4B07D4197BF34EB3B753DD34EBCD130272ABC0@de01exm67.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-mccann-mip4-mbb-00.txt
thread-index: AciWeb7Xj1Zc8hGYTzukWio37cmMpQ==
From: "McCann Peter-A001034" <pete.mccann@motorola.com>
To: <mip4@ietf.org>
X-CFilter-Loop: Reflected
Subject: [Mip4] draft-mccann-mip4-mbb-00.txt
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

<<Chair hat off>>

I've just uploaded a short draft that contains some suggestions
on HA implementation details to assist in make-before-break 
handoffs.  I hope people can read and comment:

   A make-before-break handoff is one where resources on a target system
   are allocated prior to releasing the resources on a source system.
   Make-before-break can be an effective means to provide a more
   seamless handoff with fewer dropped packets.  The existing Mobile
   IPv4 specification supports simultaneous bindings, which can
   facilitate a make-before-break handoff.  However, the binding state
   at the home agent is only one example of a resource that can be
   allocated; others include the link connection to the Foreign Agent
   (or access router) and the provision of security associations between
   the mobile node and the mobility agents.  It may be desirable to set
   up these resources on the target system without necessarily creating
   a binding entry on the Home Agent.  This document provides some
   additional conventions on the use of simultaneous bindings in a make-
   before-break handoff that can be used to optimize the allocation of
   resources in these scenarios.

These suggestions might be appropriate for inclusion in rfc3344bis,
if there is still time to make them, or it could be published as a 
separate document.

Please, let me know what you think!

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


From mip4-bounces@ietf.org  Fri Apr  4 12:02:38 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9DD903A6FA8;
	Fri,  4 Apr 2008 12:02:38 -0700 (PDT)
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 17D673A6F9C
	for <mip4@core3.amsl.com>; Fri,  4 Apr 2008 12:02:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level: 
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5
	tests=[AWL=-0.295, BAYES_00=-2.599, MISSING_HEADERS=1.292]
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 PqLEIWqlI1J6 for <mip4@core3.amsl.com>;
	Fri,  4 Apr 2008 12:02:34 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by core3.amsl.com (Postfix) with ESMTP id AD86228C6C1
	for <mip4@ietf.org>; Fri,  4 Apr 2008 12:01:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP id 618BE1D33AF
	for <mip4@ietf.org>; Fri,  4 Apr 2008 12:01:53 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1])
	by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 11303-05 for <mip4@ietf.org>; Fri,  4 Apr 2008 12:01:53 -0700 (PDT)
Received: from [jR???n?IPv6???1] (login004.redback.com [155.53.12.57])
	by prattle.redback.com (Postfix) with ESMTP id DC46D1D33AE
	for <mip4@ietf.org>; Fri,  4 Apr 2008 12:01:52 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v753)
In-Reply-To: <15ABAEBC-3ADC-40C1-B044-E02A79D474A6@redback.com>
References: <15ABAEBC-3ADC-40C1-B044-E02A79D474A6@redback.com>
Message-Id: <E45A1B6B-D754-48FA-AECC-BE35F6C4CE9D@redback.com>
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
From: Acee Lindem <acee@redback.com>
Date: Fri, 4 Apr 2008 15:01:52 -0400
X-Mailer: Apple Mail (2.753)
X-Virus-Scanned: by amavisd-new at redback.com
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 - foreign
	agent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Any opinions?
Thanks,
Acee
On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:

> With respect to our MIP4 HA implementation, we've had several  
> discussions as to whether a registration reply should be generated  
> when the registration request fails FA-HA authentication. The  
> existence of the 132 reply code would imply that one should always  
> respond. However, this is contrary to way authentication works in  
> most protocols (at least routing protocols) and would seem to leave  
> the HA more susceptible to DoS attacks. I checked the RFC 3344 BIS  
> draft and there has been no change in this area.
> Thanks,
> Acee

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


From mip4-bounces@ietf.org  Fri Apr  4 19:08:07 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EB8873A68B3;
	Fri,  4 Apr 2008 19:08:07 -0700 (PDT)
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 D6A783A68D3
	for <mip4@core3.amsl.com>; Fri,  4 Apr 2008 19:08:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sfwg77g7rYBm for <mip4@core3.amsl.com>;
	Fri,  4 Apr 2008 19:08:05 -0700 (PDT)
Received: from ind-iport-1.cisco.com (ind-iport-1.cisco.com [64.104.129.195])
	by core3.amsl.com (Postfix) with ESMTP id D62113A68AA
	for <mip4@ietf.org>; Fri,  4 Apr 2008 19:08:04 -0700 (PDT)
Received: from hkg-dkim-1.cisco.com ([10.75.231.161])
	by ind-iport-1.cisco.com with ESMTP; 05 Apr 2008 07:38:08 +0530
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94])
	by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m35287in008381; 
	Sat, 5 Apr 2008 10:08:07 +0800
Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com
	[64.104.123.69])
	by hkg-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m35287Rn023054;
	Sat, 5 Apr 2008 02:08:07 GMT
Received: from xmb-hkg-416.apac.cisco.com ([64.104.123.88]) by
	xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 5 Apr 2008 10:08:05 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 5 Apr 2008 10:05:46 +0800
Message-ID: <35912544FC930E49BF20EF16C3EF2765035A930F@xmb-hkg-416.apac.cisco.com>
In-Reply-To: <E45A1B6B-D754-48FA-AECC-BE35F6C4CE9D@redback.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
	foreignagent failed authentication
Thread-Index: AciWh4UtagEYO0eESJufqeCrpih3YAAN1CIw
References: <15ABAEBC-3ADC-40C1-B044-E02A79D474A6@redback.com>
	<E45A1B6B-D754-48FA-AECC-BE35F6C4CE9D@redback.com>
From: "Yoshi Tsuda (yotsuda)" <yotsuda@cisco.com>
To: "Acee Lindem" <acee@redback.com>
X-OriginalArrivalTime: 05 Apr 2008 02:08:05.0198 (UTC)
	FILETIME=[E27126E0:01C896C1]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1662; t=1207361287;
	x=1208225287; c=relaxed/simple; s=hkgdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=yotsuda@cisco.com;
	z=From:=20=22Yoshi=20Tsuda=20(yotsuda)=22=20<yotsuda@cisco.c
	om> |Subject:=20RE=3A=20[Mip4]=20RFC=203344=20-=20Home=20Agent=
	20Registration=20Code=20132=20-=20foreignagent=20failed=20au
	thentication |Sender:=20;
	bh=xtzhm1PnGytCz+Ba37oOctz1+7OiaA9e4iP5oevHVHM=;
	b=aB2Ji3228cpsciIe0H7LQwoXhNPpcBp4q9ZGN/v6r+PPPu9Uo1fuZoN3Mb
	VSXKwHcvg6rMuC7g4E6MJcxGAUAHPJFXlK8Yxkm+LJgM71zzc4KQBUfcRDWP
	Xjfj9a8Qxt3z0QQLUZ8f8YsGjBdbsXb8EuOLG2tbQ5WB1XL99c/uw=;
Authentication-Results: hkg-dkim-1; header.From=yotsuda@cisco.com; dkim=pass (
	sig from cisco.com/hkgdkim1002 verified; ); 
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
	foreignagent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi Acee,

 The 3.8.2.1 section of rfc3344 doesn't mandate for an HA to reply
 an RRP to an MN with 132, but it just says an HA "should" send
 an RRP to an MN with 132.
 Thus, you have the option not to send an RRP to an MN based on
 your policy against DoS attacks.  You know, an rfc doesn't define
 a specific policy, but mechanism.  So, I believe, the original rfc
 works fine.

Cheers.
-Yoshi

> -----Original Message-----
> From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On 
> Behalf Of Acee Lindem
> Sent: Friday, April 04, 2008 12:02 PM
> Cc: Mobile IPv4 Mailing List
> Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 
> 132 - foreignagent failed authentication
> 
> Any opinions?
> Thanks,
> Acee
> On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:
> 
> > With respect to our MIP4 HA implementation, we've had several 
> > discussions as to whether a registration reply should be generated 
> > when the registration request fails FA-HA authentication. The 
> > existence of the 132 reply code would imply that one should always 
> > respond. However, this is contrary to way authentication 
> works in most 
> > protocols (at least routing protocols) and would seem to 
> leave the HA 
> > more susceptible to DoS attacks. I checked the RFC 3344 BIS 
> draft and 
> > there has been no change in this area.
> > Thanks,
> > Acee
> 
> --
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
> 
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Sat Apr  5 12:48:35 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E94ED3A6B51;
	Sat,  5 Apr 2008 12:48:35 -0700 (PDT)
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 9F12E3A6B51
	for <mip4@core3.amsl.com>; Sat,  5 Apr 2008 12:48:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[AWL=0.350, 
	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 Twvg0+Mg6TiJ for <mip4@core3.amsl.com>;
	Sat,  5 Apr 2008 12:48:34 -0700 (PDT)
Received: from merlot.tools.ietf.org (unknown
	[IPv6:2a01:3f0:0:31:214:22ff:fe21:bb])
	by core3.amsl.com (Postfix) with ESMTP id BE3623A681A
	for <mip4@ietf.org>; Sat,  5 Apr 2008 12:48:33 -0700 (PDT)
Received: from localhost ([127.0.0.1]:58291 helo=chardonnay.local)
	by merlot.tools.ietf.org with esmtp (Exim 4.69)
	(envelope-from <henrik@levkowetz.com>)
	id 1JiENT-00025V-Vo; Sat, 05 Apr 2008 21:48:40 +0200
Message-ID: <47F7D785.60003@levkowetz.com>
Date: Sat, 05 Apr 2008 21:48:21 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: Acee Lindem <acee@redback.com>
References: <15ABAEBC-3ADC-40C1-B044-E02A79D474A6@redback.com>
	<E45A1B6B-D754-48FA-AECC-BE35F6C4CE9D@redback.com>
In-Reply-To: <E45A1B6B-D754-48FA-AECC-BE35F6C4CE9D@redback.com>
X-Enigmail-Version: 0.95.6
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: acee@redback.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: Mobile IPv4 Mailing List <mip4@ietf.org>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 - foreign
 agent failed authentication
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="===============0126664359=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

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

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

Hi Acee,

Your post sums it up pretty much, but let me add this:  In some
situations and deployments, mainly when you're setting up a new
deployment environment, you actually want to generate the replies
for debugging and informative purposes, while mostly you want to
turn them off to avoid DoS attacks.  At least one HA implementation
I know has the behaviour configurable, for that reason.  And as
the RFC 3344 and 3344bis text seems to match this usage reasonably
well, I don't think we want to change it?


	Henrik

On 2008-04-04 21:01 Acee Lindem said the following:
> Any opinions?
> Thanks,
> Acee
> On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:
>=20
>> With respect to our MIP4 HA implementation, we've had several =20
>> discussions as to whether a registration reply should be generated =20
>> when the registration request fails FA-HA authentication. The =20
>> existence of the 132 reply code would imply that one should always =20
>> respond. However, this is contrary to way authentication works in =20
>> most protocols (at least routing protocols) and would seem to leave =20
>> the HA more susceptible to DoS attacks. I checked the RFC 3344 BIS =20
>> draft and there has been no change in this area.
>> Thanks,
>> Acee
>=20


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

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

iD8DBQFH99eXeVhrtTJkXCMRAs2FAJwNqrjiK7wrbL5EaV4im9rLcKtSCQCfSnta
XavP+5Oyh+1MUdYBVtIEWeM=
=+hFq
-----END PGP SIGNATURE-----

--------------enig282554A863454223EECA9FCF--

--===============0126664359==
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/

--===============0126664359==--


From mip4-bounces@ietf.org  Mon Apr  7 02:41:48 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3EFB33A6C3E;
	Mon,  7 Apr 2008 02:41:48 -0700 (PDT)
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 A7ECA3A6C3E
	for <mip4@core3.amsl.com>; Mon,  7 Apr 2008 02:41:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.102
X-Spam-Level: 
X-Spam-Status: No, score=-1.102 tagged_above=-999 required=5 tests=[AWL=0.875, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 rkAJF83QHkxq for <mip4@core3.amsl.com>;
	Mon,  7 Apr 2008 02:41:46 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175])
	by core3.amsl.com (Postfix) with ESMTP id 094B73A6939
	for <mip4@ietf.org>; Mon,  7 Apr 2008 02:41:45 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 25so1363404wfa.31
	for <mip4@ietf.org>; Mon, 07 Apr 2008 02:41:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=dq+zNZoYosVmmSLKzcbvx1SgGkDcaPDg4ms0mxt/7q4=;
	b=B5fRVrrQ8mTta8AzzOdOZF0ewFenXneDE8x1x/XG3Ny1DqE0sfJeq56k+NOMegDm+r+l6PycP1W+oO75hPZlvrddStctunEjLfz08EhgboDX8R/jG1LadcHWDER8lLp+hdOqUOaYyRk2WUJVxLixaGDqseyePLDbo7SWcBHWKu4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=F+qixGZNpGHq1YhAiK27GpsjIfIZ7vBMaOElbU3UVxF74U3nTtCTmap2Ztm/0j1mfvqUIfr0YJfcQpHJ75//mA0gjuKfLfXMmzcl9NqjjMEwPVFA+LTdAOrduilIEmayfL0IVir7Zd85s7fWmI68r1j9uN0aLhfaK7wP4vGXMo4=
Received: by 10.143.162.8 with SMTP id p8mr2315988wfo.63.1207561318689;
	Mon, 07 Apr 2008 02:41:58 -0700 (PDT)
Received: by 10.142.224.10 with HTTP; Mon, 7 Apr 2008 02:41:58 -0700 (PDT)
Message-ID: <d3886a520804070241k3a1f53f0ye00327adb22351b4@mail.gmail.com>
Date: Mon, 7 Apr 2008 10:41:58 +0100
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Henrik Levkowetz" <henrik@levkowetz.com>
In-Reply-To: <47F7D785.60003@levkowetz.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <15ABAEBC-3ADC-40C1-B044-E02A79D474A6@redback.com>
	<E45A1B6B-D754-48FA-AECC-BE35F6C4CE9D@redback.com>
	<47F7D785.60003@levkowetz.com>
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>, Acee Lindem <acee@redback.com>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 - foreign
	agent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi all,

 I have the following comments you may want to consider:

1) The SHOULD language is very strong. SHOULD in an RFC means that the
IETF thinks that the procedure should be followed by all
implementations unless the implementor has a very good reason not to
do so. In other words, and in this case, the RFC says that the IETF
thinks HAs should send these 131(MN auth failed)/132(FA auth failed)
codes, although not sending them does not break interoperability.

The recent discussion indicates that we are not so sure that this is
the correct course of "default" action. On the contrary one should
think carefuly if there is a potential DoS attack in a given
implementation/deployment and then decide whether such messages should
be sent. If that is what we think then the correct language in that
"the HA SHOULD NOT send RREP messages" in this case.

2) If MN-HA auth fails notify the FA! What I think would make most
sense is something like the following::

-  if MN-FA auth fails:
 "the HA MUST discard the message and SHOULD NOT send any response."

- If the MN-FA auth fails, however:
 "the HA MUST discard the message and MAY send a response (with code
131) to the FA if one exists, otherwise the HA SHOULD NOT send any
response"

I think sending a message to the FA when the MN-HA auth fails makes
sense don't you?

Again I am not sure if RFC3344bis can acommodate such change, since
this would require FAs to understand code 131, which may not do
currently. Still I do not think this would really break any
implementation, Most likely an FA would just log the error, not
knowing what to do next beyond understanding this as a rejection.

Thoughts?
George


2008/4/5 Henrik Levkowetz <henrik@levkowetz.com>:
> Hi Acee,
>
>  Your post sums it up pretty much, but let me add this:  In some
>  situations and deployments, mainly when you're setting up a new
>  deployment environment, you actually want to generate the replies
>  for debugging and informative purposes, while mostly you want to
>  turn them off to avoid DoS attacks.  At least one HA implementation
>  I know has the behaviour configurable, for that reason.  And as
>  the RFC 3344 and 3344bis text seems to match this usage reasonably
>  well, I don't think we want to change it?
>
>
>         Henrik
>
>  On 2008-04-04 21:01 Acee Lindem said the following:
>
>
>
> > Any opinions?
> > Thanks,
> > Acee
> > On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:
> >
> >
> > > With respect to our MIP4 HA implementation, we've had several
> discussions as to whether a registration reply should be generated  when the
> registration request fails FA-HA authentication. The  existence of the 132
> reply code would imply that one should always  respond. However, this is
> contrary to way authentication works in  most protocols (at least routing
> protocols) and would seem to leave  the HA more susceptible to DoS attacks.
> I checked the RFC 3344 BIS  draft and there has been no change in this area.
> > > Thanks,
> > > Acee
> > >
> >
> >
>
>
> --
>  Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>  Supplemental site: http://www.mip4.org/
>
>
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Mon Apr  7 08:48:49 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5D40F28C35B;
	Mon,  7 Apr 2008 08:48:49 -0700 (PDT)
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 3B80F28C39B
	for <mip4@core3.amsl.com>; Mon,  7 Apr 2008 08:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.625
X-Spam-Level: 
X-Spam-Status: No, score=-0.625 tagged_above=-999 required=5 tests=[AWL=1.352, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 wfnr3IbDRXAk for <mip4@core3.amsl.com>;
	Mon,  7 Apr 2008 08:48:46 -0700 (PDT)
Received: from gv-out-0910.google.com (gv-out-0910.google.com [216.239.58.186])
	by core3.amsl.com (Postfix) with ESMTP id 1FC4B3A67D4
	for <mip4@ietf.org>; Mon,  7 Apr 2008 08:48:42 -0700 (PDT)
Received: by gv-out-0910.google.com with SMTP id i36so216119gve.15
	for <mip4@ietf.org>; Mon, 07 Apr 2008 08:48:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=TZwFNKUM7fc8QIIoH95JL6WiOuOedlrTUFoLy6uCQ8k=;
	b=I3yhQdXiaNkcTMYRnQxWEJNCGgvptwIRLJoc1/VDMWSLMONWl8STUJOjGDrFD8kUNyzGUWJG2aXhCYzHBctziKNM+prsXHa4EdXtgjlFU8IgHle72c4TP3dosu0pM9WRr4rTrbbUXoNg0xQ8yrVclu18yT+qS3pYv2risbmm2RE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=Xmukhim8icuCq/rPVoOcawnNzfgNWOo1g0Vg55RjVJNV6mj5B2zSWmd8TrFP8Mol1moo3dqhjYKVquy1VD+ImbmHFNDSz+T4WwkYo1/ctUG+dX/nxM2J0qpz+A6nxBu9Ef5ZBig6Ba7N4IMwkjjTm3QhcPcMM1FdCzThbHk6+4U=
Received: by 10.142.48.14 with SMTP id v14mr2606398wfv.14.1207583334384;
	Mon, 07 Apr 2008 08:48:54 -0700 (PDT)
Received: by 10.142.224.10 with HTTP; Mon, 7 Apr 2008 08:48:54 -0700 (PDT)
Message-ID: <d3886a520804070848w380815b1i77901820bc7e4425@mail.gmail.com>
Date: Mon, 7 Apr 2008 16:48:54 +0100
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Henrik Levkowetz" <henrik@levkowetz.com>
In-Reply-To: <d3886a520804070241k3a1f53f0ye00327adb22351b4@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <15ABAEBC-3ADC-40C1-B044-E02A79D474A6@redback.com>
	<E45A1B6B-D754-48FA-AECC-BE35F6C4CE9D@redback.com>
	<47F7D785.60003@levkowetz.com>
	<d3886a520804070241k3a1f53f0ye00327adb22351b4@mail.gmail.com>
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>, Acee Lindem <acee@redback.com>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 - foreign
	agent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

See a correction below (Thanks to Ahmad for spotting the mistake)

On Mon, Apr 7, 2008 at 10:41 AM, George Tsirtsis
<tsirtsis@googlemail.com> wrote:
> Hi all,
>
>   I have the following comments you may want to consider:
>
>  1) The SHOULD language is very strong. SHOULD in an RFC means that the
>  IETF thinks that the procedure should be followed by all
>  implementations unless the implementor has a very good reason not to
>  do so. In other words, and in this case, the RFC says that the IETF
>  thinks HAs should send these 131(MN auth failed)/132(FA auth failed)
>  codes, although not sending them does not break interoperability.
>
>  The recent discussion indicates that we are not so sure that this is
>  the correct course of "default" action. On the contrary one should
>  think carefuly if there is a potential DoS attack in a given
>  implementation/deployment and then decide whether such messages should
>  be sent. If that is what we think then the correct language in that
>  "the HA SHOULD NOT send RREP messages" in this case.
>
>  2) If MN-HA auth fails notify the FA! What I think would make most
>  sense is something like the following::
>
>  -  if MN-FA auth fails:

GT> This should have been:
 - If the FA-HA auth fails, however

>   "the HA MUST discard the message and SHOULD NOT send any response."
>

>  - If the MN-FA auth fails, however:

GT> This should have been:
 - If the MN-HA auth fails, however:

>   "the HA MUST discard the message and MAY send a response (with code
>  131) to the FA if one exists, otherwise the HA SHOULD NOT send any
>  response"
>
>  I think sending a message to the FA when the MN-HA auth fails makes
>  sense don't you?
>
>  Again I am not sure if RFC3344bis can acommodate such change, since
>  this would require FAs to understand code 131, which may not do
>  currently. Still I do not think this would really break any
>  implementation, Most likely an FA would just log the error, not
>  knowing what to do next beyond understanding this as a rejection.
>
>  Thoughts?
>  George
>
>
>  2008/4/5 Henrik Levkowetz <henrik@levkowetz.com>:
>
>
> > Hi Acee,
>  >
>  >  Your post sums it up pretty much, but let me add this:  In some
>  >  situations and deployments, mainly when you're setting up a new
>  >  deployment environment, you actually want to generate the replies
>  >  for debugging and informative purposes, while mostly you want to
>  >  turn them off to avoid DoS attacks.  At least one HA implementation
>  >  I know has the behaviour configurable, for that reason.  And as
>  >  the RFC 3344 and 3344bis text seems to match this usage reasonably
>  >  well, I don't think we want to change it?
>  >
>  >
>  >         Henrik
>  >
>  >  On 2008-04-04 21:01 Acee Lindem said the following:
>  >
>  >
>  >
>  > > Any opinions?
>  > > Thanks,
>  > > Acee
>  > > On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:
>  > >
>  > >
>  > > > With respect to our MIP4 HA implementation, we've had several
>  > discussions as to whether a registration reply should be generated  when the
>  > registration request fails FA-HA authentication. The  existence of the 132
>  > reply code would imply that one should always  respond. However, this is
>  > contrary to way authentication works in  most protocols (at least routing
>  > protocols) and would seem to leave  the HA more susceptible to DoS attacks.
>  > I checked the RFC 3344 BIS  draft and there has been no change in this area.
>  > > > Thanks,
>  > > > Acee
>  > > >
>  > >
>  > >
>  >
>  >
>  > --
>
>
> >  Mip4 mailing list: Mip4@ietf.org
>  >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>  >      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>  >  Supplemental site: http://www.mip4.org/
>  >
>  >
>
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Mon Apr  7 09:36:23 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D5FE63A6E94;
	Mon,  7 Apr 2008 09:36:23 -0700 (PDT)
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 7E7BB3A6CD4
	for <mip4@core3.amsl.com>; Mon,  7 Apr 2008 09:36:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 7CQRsbMdrIZb for <mip4@core3.amsl.com>;
	Mon,  7 Apr 2008 09:36:22 -0700 (PDT)
Received: from zcars04f.nortel.com (zcars04f.nortel.com [47.129.242.57])
	by core3.amsl.com (Postfix) with ESMTP id 02FDE3A6963
	for <mip4@ietf.org>; Mon,  7 Apr 2008 09:36:21 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m37GaKI04179; Mon, 7 Apr 2008 16:36:21 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 7 Apr 2008 11:36:02 -0500
Message-ID: <C5A96676FCD00745B64AE42D5FCC9B6E178C5965@zrc2hxm0.corp.nortel.com>
In-Reply-To: <d3886a520804070848w380815b1i77901820bc7e4425@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] RFC 3344 - Home Agent Registration Code 132 - foreign
	agent failed authentication
Thread-Index: AciYx2D7M+Fo7kH2ReGecNYZh40w5wABFOlw
References: <15ABAEBC-3ADC-40C1-B044-E02A79D474A6@redback.com>
	<E45A1B6B-D754-48FA-AECC-BE35F6C4CE9D@redback.com>
	<47F7D785.60003@levkowetz.com>
	<d3886a520804070241k3a1f53f0ye00327adb22351b4@mail.gmail.com>
	<d3886a520804070848w380815b1i77901820bc7e4425@mail.gmail.com>
From: "Ahmad Muhanna" <amuhanna@nortel.com>
To: "George Tsirtsis" <tsirtsis@googlemail.com>,
	"Henrik Levkowetz" <henrik@levkowetz.com>
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>, Acee Lindem <acee@redback.com>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 - foreign
	agent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

George, let me understand what you are trying to say:

1. If FA-HA authentication fails, then HA MUST discard the message and
HA SHOULD not send any response. This is irrelevant to what happens with
MN-HA AE, because if FA-HA fails there is no point to validate MN-HA AE.

2. If MN-HA AE fails, then?

2.1. Does this mean that FA-HA AE was present and was successfully
processed? If yes, it makes a lot of sense to send a RRP to the MN with
code 131.

2.2. Id FA-HA AE is not there, then probably it is less stronger for the
HA to send RRP with an error code 131. However, sending RRP with error
code in normal case is very useful. I agree that MN and HA should be in
sync but there is a possibility for errors and there is nothing wrong to
inform the MN whenever safe and necessary.

However, in general, I support leaving RFC3344 wording as is. Why?

I agree with George on the definition of SHOULD. BUT what more of a
reason than a DoS attack for the HA not to send a RRQ with error code
131 or any other code. I would rather leave it to implementation rather
than go through every single scenario and document it here. Back to the
same discussion, let us leave some room for those architect to do some
work and identify how their HA will address DoS attack. There are many
ways to do it and at the same time continue to satisfy the SHOULD as per
RFC3344.

My 2 cents.


Regards,
Ahmad
 

> -----Original Message-----
> From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On 
> Behalf Of George Tsirtsis
> Sent: Monday, April 07, 2008 10:49 AM
> To: Henrik Levkowetz
> Cc: Mobile IPv4 Mailing List; Acee Lindem
> Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 
> 132 - foreign agent failed authentication
> 
> See a correction below (Thanks to Ahmad for spotting the mistake)
> 
> On Mon, Apr 7, 2008 at 10:41 AM, George Tsirtsis 
> <tsirtsis@googlemail.com> wrote:
> > Hi all,
> >
> >   I have the following comments you may want to consider:
> >
> >  1) The SHOULD language is very strong. SHOULD in an RFC means that 
> > the  IETF thinks that the procedure should be followed by all  
> > implementations unless the implementor has a very good 
> reason not to  
> > do so. In other words, and in this case, the RFC says that 
> the IETF  
> > thinks HAs should send these 131(MN auth failed)/132(FA 
> auth failed)  
> > codes, although not sending them does not break interoperability.
> >
> >  The recent discussion indicates that we are not so sure 
> that this is  
> > the correct course of "default" action. On the contrary one should  
> > think carefuly if there is a potential DoS attack in a given  
> > implementation/deployment and then decide whether such 
> messages should  
> > be sent. If that is what we think then the correct language 
> in that  
> > "the HA SHOULD NOT send RREP messages" in this case.
> >
> >  2) If MN-HA auth fails notify the FA! What I think would 
> make most  
> > sense is something like the following::
> >
> >  -  if MN-FA auth fails:
> 
> GT> This should have been:
>  - If the FA-HA auth fails, however
> 
> >   "the HA MUST discard the message and SHOULD NOT send any 
> response."
> >
> 
> >  - If the MN-FA auth fails, however:
> 
> GT> This should have been:
>  - If the MN-HA auth fails, however:
> 
> >   "the HA MUST discard the message and MAY send a response 
> (with code
> >  131) to the FA if one exists, otherwise the HA SHOULD NOT 
> send any  
> > response"
> >
> >  I think sending a message to the FA when the MN-HA auth 
> fails makes  
> > sense don't you?
> >
> >  Again I am not sure if RFC3344bis can acommodate such 
> change, since  
> > this would require FAs to understand code 131, which may not do  
> > currently. Still I do not think this would really break any  
> > implementation, Most likely an FA would just log the error, not  
> > knowing what to do next beyond understanding this as a rejection.
> >
> >  Thoughts?
> >  George
> >
> >
> >  2008/4/5 Henrik Levkowetz <henrik@levkowetz.com>:
> >
> >
> > > Hi Acee,
> >  >
> >  >  Your post sums it up pretty much, but let me add this:  
> In some  >  
> > situations and deployments, mainly when you're setting up a new  >  
> > deployment environment, you actually want to generate the 
> replies  >  
> > for debugging and informative purposes, while mostly you 
> want to  >  
> > turn them off to avoid DoS attacks.  At least one HA 
> implementation  >  
> > I know has the behaviour configurable, for that reason.  And as  >  
> > the RFC 3344 and 3344bis text seems to match this usage 
> reasonably  >  
> > well, I don't think we want to change it?
> >  >
> >  >
> >  >         Henrik
> >  >
> >  >  On 2008-04-04 21:01 Acee Lindem said the following:
> >  >
> >  >
> >  >
> >  > > Any opinions?
> >  > > Thanks,
> >  > > Acee
> >  > > On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:
> >  > >
> >  > >
> >  > > > With respect to our MIP4 HA implementation, we've 
> had several  
> > > discussions as to whether a registration reply should be 
> generated  
> > when the  > registration request fails FA-HA authentication. The  
> > existence of the 132  > reply code would imply that one 
> should always  
> > respond. However, this is  > contrary to way authentication 
> works in  
> > most protocols (at least routing  > protocols) and would 
> seem to leave  the HA more susceptible to DoS attacks.
> >  > I checked the RFC 3344 BIS  draft and there has been no 
> change in this area.
> >  > > > Thanks,
> >  > > > Acee
> >  > > >
> >  > >
> >  > >
> >  >
> >  >
> >  > --
> >
> >
> > >  Mip4 mailing list: Mip4@ietf.org
> >  >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
> >  >      Charter page: 
> http://www.ietf.org/html.charters/mip4-charter.html
> >  >  Supplemental site: http://www.mip4.org/  >  >
> >
> -- 
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
> 
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Mon Apr  7 09:48:25 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 79E2D3A6C5A;
	Mon,  7 Apr 2008 09:48:25 -0700 (PDT)
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 7DDD228C1D6
	for <mip4@core3.amsl.com>; Mon,  7 Apr 2008 09:48:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.269
X-Spam-Level: 
X-Spam-Status: No, score=-1.269 tagged_above=-999 required=5 tests=[AWL=0.708, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 9GB2K-FsgwMq for <mip4@core3.amsl.com>;
	Mon,  7 Apr 2008 09:48:23 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.171])
	by core3.amsl.com (Postfix) with ESMTP id DAA773A6C5A
	for <mip4@ietf.org>; Mon,  7 Apr 2008 09:48:22 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 25so1549119wfa.31
	for <mip4@ietf.org>; Mon, 07 Apr 2008 09:48:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=UJFmgcclFQ6zPgXE8Qjc76BHsnVKoo16kWjdU8Ewaz4=;
	b=H3YfBSpZMw4WgWUFIwo6RJAiFWwZiA8rMTCxpJq7NHGE2nVv38PFVECSXSzzlCMU3RKY01373QUL75lkaGs/8JAkJyWfYe5SThDdGq9RQrPJhjOpOjxehZqRgzc7kxarHKGgBn9xv4CVtAcydUA7DqtvKWXr8MGC/vI5K0MTZCw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=pxfR5mKCFPfLC3g+m7C0uWJz4e6un7bfl0tJXyFQpCoWbRp5mxxy/62PxdPQCJl+nUcO39nrQqtcNoRLam2ahox+uWb7p/YwxpAi3ya/WwnNi5TzFWSCvB+I9FK2hC9H6u0ih5z0jRsfRzsrHzcRoz9obgUu7x5HWJOh6lajsVY=
Received: by 10.142.141.21 with SMTP id o21mr2589775wfd.199.1207586914234;
	Mon, 07 Apr 2008 09:48:34 -0700 (PDT)
Received: by 10.142.224.10 with HTTP; Mon, 7 Apr 2008 09:48:34 -0700 (PDT)
Message-ID: <d3886a520804070948u6c8cd4e1gdceab669742c9ac2@mail.gmail.com>
Date: Mon, 7 Apr 2008 17:48:34 +0100
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Ahmad Muhanna" <amuhanna@nortel.com>
In-Reply-To: <C5A96676FCD00745B64AE42D5FCC9B6E178C5965@zrc2hxm0.corp.nortel.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <15ABAEBC-3ADC-40C1-B044-E02A79D474A6@redback.com>
	<E45A1B6B-D754-48FA-AECC-BE35F6C4CE9D@redback.com>
	<47F7D785.60003@levkowetz.com>
	<d3886a520804070241k3a1f53f0ye00327adb22351b4@mail.gmail.com>
	<d3886a520804070848w380815b1i77901820bc7e4425@mail.gmail.com>
	<C5A96676FCD00745B64AE42D5FCC9B6E178C5965@zrc2hxm0.corp.nortel.com>
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>, Acee Lindem <acee@redback.com>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 - foreign
	agent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

On Mon, Apr 7, 2008 at 5:36 PM, Ahmad Muhanna <amuhanna@nortel.com> wrote:
> George, let me understand what you are trying to say:
>
>  1. If FA-HA authentication fails, then HA MUST discard the message and
>  HA SHOULD not send any response. This is irrelevant to what happens with
>  MN-HA AE, because if FA-HA fails there is no point to validate MN-HA AE.
>

GT> Yes

>  2. If MN-HA AE fails, then?
>
>  2.1. Does this mean that FA-HA AE was present and was successfully
>  processed? If yes, it makes a lot of sense to send a RRP to the MN with
>  code 131.
>

GT> Not exactly. What I am saying is that in this case the HA should
notify the FA (not the MN!). Remember the MN may be an attacker in
which case the FA needs to be notified of that possibility.

>  2.2. Id FA-HA AE is not there, then probably it is less stronger for the
>  HA to send RRP with an error code 131.

GT> I still think that if it is known that an FA exists (whether FA-HA
AE is used or not) it is useful to notify the FA (again not the MN).

> However, sending RRP with error
>  code in normal case is very useful. I agree that MN and HA should be in
>  sync but there is a possibility for errors and there is nothing wrong to
>  inform the MN whenever safe and necessary.
>

GT> Of course sending RRP with error codes e.g., if the timestamp is
wrong or some other reason is very important....here we are just
talking about the special case of authentication failures.

>  However, in general, I support leaving RFC3344 wording as is. Why?
>
>  I agree with George on the definition of SHOULD. BUT what more of a
>  reason than a DoS attack for the HA not to send a RRQ with error code
>  131 or any other code. I would rather leave it to implementation rather
>  than go through every single scenario and document it here. Back to the
>  same discussion, let us leave some room for those architect to do some
>  work and identify how their HA will address DoS attack. There are many
>  ways to do it and at the same time continue to satisfy the SHOULD as per
>  RFC3344.
>

GT> I think if people are not comfortable with describing in
RFC3344bis the behavior I argue for above, at least the SHOULD, should
be changed to MAY or even SHOULD NOT, depending how strong a message
we want to give. Note that non of these changes breaks existing
implementations. To break existing implementation we would have to
change this to MUST NOT.

Tegards
George
>
>
>  > -----Original Message-----
>  > From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On
>  > Behalf Of George Tsirtsis
>
> > Sent: Monday, April 07, 2008 10:49 AM
>  > To: Henrik Levkowetz
>  > Cc: Mobile IPv4 Mailing List; Acee Lindem
>  > Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code
>  > 132 - foreign agent failed authentication
>  >
>
>
> > See a correction below (Thanks to Ahmad for spotting the mistake)
>  >
>  > On Mon, Apr 7, 2008 at 10:41 AM, George Tsirtsis
>  > <tsirtsis@googlemail.com> wrote:
>  > > Hi all,
>  > >
>  > >   I have the following comments you may want to consider:
>  > >
>  > >  1) The SHOULD language is very strong. SHOULD in an RFC means that
>  > > the  IETF thinks that the procedure should be followed by all
>  > > implementations unless the implementor has a very good
>  > reason not to
>  > > do so. In other words, and in this case, the RFC says that
>  > the IETF
>  > > thinks HAs should send these 131(MN auth failed)/132(FA
>  > auth failed)
>  > > codes, although not sending them does not break interoperability.
>  > >
>  > >  The recent discussion indicates that we are not so sure
>  > that this is
>  > > the correct course of "default" action. On the contrary one should
>  > > think carefuly if there is a potential DoS attack in a given
>  > > implementation/deployment and then decide whether such
>  > messages should
>  > > be sent. If that is what we think then the correct language
>  > in that
>  > > "the HA SHOULD NOT send RREP messages" in this case.
>  > >
>  > >  2) If MN-HA auth fails notify the FA! What I think would
>  > make most
>  > > sense is something like the following::
>  > >
>  > >  -  if MN-FA auth fails:
>  >
>  > GT> This should have been:
>  >  - If the FA-HA auth fails, however
>  >
>  > >   "the HA MUST discard the message and SHOULD NOT send any
>  > response."
>  > >
>  >
>  > >  - If the MN-FA auth fails, however:
>  >
>  > GT> This should have been:
>  >  - If the MN-HA auth fails, however:
>  >
>  > >   "the HA MUST discard the message and MAY send a response
>  > (with code
>  > >  131) to the FA if one exists, otherwise the HA SHOULD NOT
>  > send any
>  > > response"
>  > >
>  > >  I think sending a message to the FA when the MN-HA auth
>  > fails makes
>  > > sense don't you?
>  > >
>  > >  Again I am not sure if RFC3344bis can acommodate such
>  > change, since
>  > > this would require FAs to understand code 131, which may not do
>  > > currently. Still I do not think this would really break any
>  > > implementation, Most likely an FA would just log the error, not
>  > > knowing what to do next beyond understanding this as a rejection.
>  > >
>  > >  Thoughts?
>  > >  George
>  > >
>  > >
>  > >  2008/4/5 Henrik Levkowetz <henrik@levkowetz.com>:
>  > >
>  > >
>  > > > Hi Acee,
>  > >  >
>  > >  >  Your post sums it up pretty much, but let me add this:
>  > In some  >
>  > > situations and deployments, mainly when you're setting up a new  >
>  > > deployment environment, you actually want to generate the
>  > replies  >
>  > > for debugging and informative purposes, while mostly you
>  > want to  >
>  > > turn them off to avoid DoS attacks.  At least one HA
>  > implementation  >
>  > > I know has the behaviour configurable, for that reason.  And as  >
>  > > the RFC 3344 and 3344bis text seems to match this usage
>  > reasonably  >
>  > > well, I don't think we want to change it?
>  > >  >
>  > >  >
>  > >  >         Henrik
>  > >  >
>  > >  >  On 2008-04-04 21:01 Acee Lindem said the following:
>  > >  >
>  > >  >
>  > >  >
>  > >  > > Any opinions?
>  > >  > > Thanks,
>  > >  > > Acee
>  > >  > > On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:
>  > >  > >
>  > >  > >
>  > >  > > > With respect to our MIP4 HA implementation, we've
>  > had several
>  > > > discussions as to whether a registration reply should be
>  > generated
>  > > when the  > registration request fails FA-HA authentication. The
>  > > existence of the 132  > reply code would imply that one
>  > should always
>  > > respond. However, this is  > contrary to way authentication
>  > works in
>  > > most protocols (at least routing  > protocols) and would
>  > seem to leave  the HA more susceptible to DoS attacks.
>  > >  > I checked the RFC 3344 BIS  draft and there has been no
>  > change in this area.
>  > >  > > > Thanks,
>  > >  > > > Acee
>  > >  > > >
>  > >  > >
>  > >  > >
>  > >  >
>  > >  >
>  > >  > --
>  > >
>  > >
>  > > >  Mip4 mailing list: Mip4@ietf.org
>  > >  >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>  > >  >      Charter page:
>  > http://www.ietf.org/html.charters/mip4-charter.html
>  > >  >  Supplemental site: http://www.mip4.org/  >  >
>  > >
>  > --
>
>
> > Mip4 mailing list: Mip4@ietf.org
>  >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>  >      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>  > Supplemental site: http://www.mip4.org/
>  >
>
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Mon Apr  7 11:06:21 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BDD043A6BC3;
	Mon,  7 Apr 2008 11:06:21 -0700 (PDT)
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 88AA43A6BC3
	for <mip4@core3.amsl.com>; Mon,  7 Apr 2008 11:06:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.946
X-Spam-Level: 
X-Spam-Status: No, score=-1.946 tagged_above=-999 required=5 tests=[AWL=0.653, 
	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 Kmy0AM9uD2mZ for <mip4@core3.amsl.com>;
	Mon,  7 Apr 2008 11:06:15 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by core3.amsl.com (Postfix) with ESMTP id 45F403A6A90
	for <mip4@ietf.org>; Mon,  7 Apr 2008 11:06:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP id 550AF8C20F2;
	Mon,  7 Apr 2008 11:06:29 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1])
	by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 22795-04; Mon,  7 Apr 2008 11:06:29 -0700 (PDT)
Received: from [?*???n?IPv6???1] (login004.redback.com [155.53.12.57])
	by prattle.redback.com (Postfix) with ESMTP id 522BE8C20EF;
	Mon,  7 Apr 2008 11:06:28 -0700 (PDT)
In-Reply-To: <d3886a520804070948u6c8cd4e1gdceab669742c9ac2@mail.gmail.com>
References: <15ABAEBC-3ADC-40C1-B044-E02A79D474A6@redback.com>
	<E45A1B6B-D754-48FA-AECC-BE35F6C4CE9D@redback.com>
	<47F7D785.60003@levkowetz.com>
	<d3886a520804070241k3a1f53f0ye00327adb22351b4@mail.gmail.com>
	<d3886a520804070848w380815b1i77901820bc7e4425@mail.gmail.com>
	<C5A96676FCD00745B64AE42D5FCC9B6E178C5965@zrc2hxm0.corp.nortel.com>
	<d3886a520804070948u6c8cd4e1gdceab669742c9ac2@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <1A15BB56-11A4-448A-ACBF-A63BDF43AF6B@redback.com>
From: Acee Lindem <acee@redback.com>
Date: Mon, 7 Apr 2008 14:06:27 -0400
To: George Tsirtsis <tsirtsis@googlemail.com>
X-Mailer: Apple Mail (2.753)
X-Virus-Scanned: by amavisd-new at redback.com
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>,
	Ahmad Muhanna <amuhanna@nortel.com>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 - foreign
	agent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

I'd support this change in RFC 3344.
Thanks,
Acee

On Apr 7, 2008, at 12:48 PM, George Tsirtsis wrote:

> On Mon, Apr 7, 2008 at 5:36 PM, Ahmad Muhanna <amuhanna@nortel.com>  
> wrote:
>> George, let me understand what you are trying to say:
>>
>>  1. If FA-HA authentication fails, then HA MUST discard the  
>> message and
>>  HA SHOULD not send any response. This is irrelevant to what  
>> happens with
>>  MN-HA AE, because if FA-HA fails there is no point to validate MN- 
>> HA AE.
>>
>
> GT> Yes
>
>>  2. If MN-HA AE fails, then?
>>
>>  2.1. Does this mean that FA-HA AE was present and was successfully
>>  processed? If yes, it makes a lot of sense to send a RRP to the  
>> MN with
>>  code 131.
>>
>
> GT> Not exactly. What I am saying is that in this case the HA should
> notify the FA (not the MN!). Remember the MN may be an attacker in
> which case the FA needs to be notified of that possibility.
>
>>  2.2. Id FA-HA AE is not there, then probably it is less stronger  
>> for the
>>  HA to send RRP with an error code 131.
>
> GT> I still think that if it is known that an FA exists (whether FA-HA
> AE is used or not) it is useful to notify the FA (again not the MN).
>
>> However, sending RRP with error
>>  code in normal case is very useful. I agree that MN and HA should  
>> be in
>>  sync but there is a possibility for errors and there is nothing  
>> wrong to
>>  inform the MN whenever safe and necessary.
>>
>
> GT> Of course sending RRP with error codes e.g., if the timestamp is
> wrong or some other reason is very important....here we are just
> talking about the special case of authentication failures.
>
>>  However, in general, I support leaving RFC3344 wording as is. Why?
>>
>>  I agree with George on the definition of SHOULD. BUT what more of a
>>  reason than a DoS attack for the HA not to send a RRQ with error  
>> code
>>  131 or any other code. I would rather leave it to implementation  
>> rather
>>  than go through every single scenario and document it here. Back  
>> to the
>>  same discussion, let us leave some room for those architect to do  
>> some
>>  work and identify how their HA will address DoS attack. There are  
>> many
>>  ways to do it and at the same time continue to satisfy the SHOULD  
>> as per
>>  RFC3344.
>>
>
> GT> I think if people are not comfortable with describing in
> RFC3344bis the behavior I argue for above, at least the SHOULD, should
> be changed to MAY or even SHOULD NOT, depending how strong a message
> we want to give. Note that non of these changes breaks existing
> implementations. To break existing implementation we would have to
> change this to MUST NOT.
>
> Tegards
> George
>>
>>
>>> -----Original Message-----
>>> From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On
>>> Behalf Of George Tsirtsis
>>
>>> Sent: Monday, April 07, 2008 10:49 AM
>>> To: Henrik Levkowetz
>>> Cc: Mobile IPv4 Mailing List; Acee Lindem
>>> Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code
>>> 132 - foreign agent failed authentication
>>>
>>
>>
>>> See a correction below (Thanks to Ahmad for spotting the mistake)
>>>
>>> On Mon, Apr 7, 2008 at 10:41 AM, George Tsirtsis
>>> <tsirtsis@googlemail.com> wrote:
>>>> Hi all,
>>>>
>>>>   I have the following comments you may want to consider:
>>>>
>>>>  1) The SHOULD language is very strong. SHOULD in an RFC means that
>>>> the  IETF thinks that the procedure should be followed by all
>>>> implementations unless the implementor has a very good
>>> reason not to
>>>> do so. In other words, and in this case, the RFC says that
>>> the IETF
>>>> thinks HAs should send these 131(MN auth failed)/132(FA
>>> auth failed)
>>>> codes, although not sending them does not break interoperability.
>>>>
>>>>  The recent discussion indicates that we are not so sure
>>> that this is
>>>> the correct course of "default" action. On the contrary one should
>>>> think carefuly if there is a potential DoS attack in a given
>>>> implementation/deployment and then decide whether such
>>> messages should
>>>> be sent. If that is what we think then the correct language
>>> in that
>>>> "the HA SHOULD NOT send RREP messages" in this case.
>>>>
>>>>  2) If MN-HA auth fails notify the FA! What I think would
>>> make most
>>>> sense is something like the following::
>>>>
>>>>  -  if MN-FA auth fails:
>>>
>>> GT> This should have been:
>>>  - If the FA-HA auth fails, however
>>>
>>>>   "the HA MUST discard the message and SHOULD NOT send any
>>> response."
>>>>
>>>
>>>>  - If the MN-FA auth fails, however:
>>>
>>> GT> This should have been:
>>>  - If the MN-HA auth fails, however:
>>>
>>>>   "the HA MUST discard the message and MAY send a response
>>> (with code
>>>>  131) to the FA if one exists, otherwise the HA SHOULD NOT
>>> send any
>>>> response"
>>>>
>>>>  I think sending a message to the FA when the MN-HA auth
>>> fails makes
>>>> sense don't you?
>>>>
>>>>  Again I am not sure if RFC3344bis can acommodate such
>>> change, since
>>>> this would require FAs to understand code 131, which may not do
>>>> currently. Still I do not think this would really break any
>>>> implementation, Most likely an FA would just log the error, not
>>>> knowing what to do next beyond understanding this as a rejection.
>>>>
>>>>  Thoughts?
>>>>  George
>>>>
>>>>
>>>>  2008/4/5 Henrik Levkowetz <henrik@levkowetz.com>:
>>>>
>>>>
>>>>> Hi Acee,
>>>>>
>>>>>  Your post sums it up pretty much, but let me add this:
>>> In some  >
>>>> situations and deployments, mainly when you're setting up a new  >
>>>> deployment environment, you actually want to generate the
>>> replies  >
>>>> for debugging and informative purposes, while mostly you
>>> want to  >
>>>> turn them off to avoid DoS attacks.  At least one HA
>>> implementation  >
>>>> I know has the behaviour configurable, for that reason.  And as  >
>>>> the RFC 3344 and 3344bis text seems to match this usage
>>> reasonably  >
>>>> well, I don't think we want to change it?
>>>>>
>>>>>
>>>>>         Henrik
>>>>>
>>>>>  On 2008-04-04 21:01 Acee Lindem said the following:
>>>>>
>>>>>
>>>>>
>>>>>> Any opinions?
>>>>>> Thanks,
>>>>>> Acee
>>>>>> On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:
>>>>>>
>>>>>>
>>>>>>> With respect to our MIP4 HA implementation, we've
>>> had several
>>>>> discussions as to whether a registration reply should be
>>> generated
>>>> when the  > registration request fails FA-HA authentication. The
>>>> existence of the 132  > reply code would imply that one
>>> should always
>>>> respond. However, this is  > contrary to way authentication
>>> works in
>>>> most protocols (at least routing  > protocols) and would
>>> seem to leave  the HA more susceptible to DoS attacks.
>>>>> I checked the RFC 3344 BIS  draft and there has been no
>>> change in this area.
>>>>>>> Thanks,
>>>>>>> Acee
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>
>>>>
>>>>>  Mip4 mailing list: Mip4@ietf.org
>>>>>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>>>>>      Charter page:
>>> http://www.ietf.org/html.charters/mip4-charter.html
>>>>>  Supplemental site: http://www.mip4.org/  >  >
>>>>
>>> --
>>
>>
>>> Mip4 mailing list: Mip4@ietf.org
>>>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>>>      Charter page: http://www.ietf.org/html.charters/mip4- 
>>> charter.html
>>> Supplemental site: http://www.mip4.org/
>>>
>>

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


From mip4-bounces@ietf.org  Mon Apr  7 11:10:53 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AC67A28C1B0;
	Mon,  7 Apr 2008 11:10:53 -0700 (PDT)
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 8867328C0FE
	for <mip4@core3.amsl.com>; Mon,  7 Apr 2008 11:10:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.854
X-Spam-Level: 
X-Spam-Status: No, score=-5.854 tagged_above=-999 required=5 tests=[AWL=0.745, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jhUHjL+z87rV for <mip4@core3.amsl.com>;
	Mon,  7 Apr 2008 11:10:47 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id 0F31928C1B0
	for <mip4@ietf.org>; Mon,  7 Apr 2008 11:10:29 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.25,618,1199692800"; d="scan'208";a="20291046"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-5.cisco.com with ESMTP; 07 Apr 2008 11:10:43 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m37IAhKX011299; 
	Mon, 7 Apr 2008 11:10:43 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m37IAgsg013845;
	Mon, 7 Apr 2008 18:10:42 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); 
	Mon, 7 Apr 2008 11:10:42 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 7 Apr 2008 11:10:41 -0700
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5205D1726E@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <E45A1B6B-D754-48FA-AECC-BE35F6C4CE9D@redback.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
	foreignagent failed authentication
Thread-Index: AciWh4Z57h2Bo9yzTSagx61HnkddUgCT9jdQ
From: "Kent Leung (kleung)" <kleung@cisco.com>
To: "Acee Lindem" <acee@redback.com>
X-OriginalArrivalTime: 07 Apr 2008 18:10:42.0764 (UTC)
	FILETIME=[B175D0C0:01C898DA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1763; t=1207591843;
	x=1208455843; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kleung@cisco.com;
	z=From:=20=22Kent=20Leung=20(kleung)=22=20<kleung@cisco.com>
	|Subject:=20RE=3A=20[Mip4]=20RFC=203344=20-=20Home=20Agent=
	20Registration=20Code=20132=20-=20foreignagent=20failed=20au
	thentication |Sender:=20;
	bh=FcMHpiGv+T7EVaVcK5F7yFQFgQhUYUT6ct8Uuuz3OuE=;
	b=GnRftltJIpAkB4MV8kAhfFTnEM/1FtRT4F3w/6RSeaiIkMJbjDSEP6O2dw
	inwzQweLFQE53npynMfuvt6w5AxSsTiTKK+v3w/3wn5hlM76f9hJx0RunuFa
	eBg5qqaJ06;
Authentication-Results: sj-dkim-2; header.From=kleung@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
	foreignagent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Isn't there a significantly higher chance of DoS attacks from MNs (i.e.
invalid MN-HA Auth Ext) than from FAs (i.e. invalid FA-HA Auth Ext)?
When FA-HA authentication fails, it's usually due to misconfiguration.
Of course, a rogue MN can append FA-HA Auth Ext in the request.  

I've always preferred not to send reply when authentication failed by
only logging the event.  But then always runs into cases when the reply
was required.  So I think it's up to implementation to decide the
sending of the RRP or not when authentication fails.  Not sure if
changing the RFC is necessary.

Kent

-----Original Message-----
From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of
Acee Lindem
Sent: Friday, April 04, 2008 12:02 PM
Cc: Mobile IPv4 Mailing List
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
foreignagent failed authentication

Any opinions?
Thanks,
Acee
On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:

> With respect to our MIP4 HA implementation, we've had several 
> discussions as to whether a registration reply should be generated 
> when the registration request fails FA-HA authentication. The 
> existence of the 132 reply code would imply that one should always 
> respond. However, this is contrary to way authentication works in most

> protocols (at least routing protocols) and would seem to leave the HA 
> more susceptible to DoS attacks. I checked the RFC 3344 BIS draft and 
> there has been no change in this area.
> Thanks,
> Acee

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


From mip4-bounces@ietf.org  Mon Apr  7 11:19:00 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EEE953A6E9B;
	Mon,  7 Apr 2008 11:18:59 -0700 (PDT)
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 94FC528C1B1
	for <mip4@core3.amsl.com>; Mon,  7 Apr 2008 11:18:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.226
X-Spam-Level: 
X-Spam-Status: No, score=-6.226 tagged_above=-999 required=5 tests=[AWL=0.373, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3IeSVAi2mQ-Y for <mip4@core3.amsl.com>;
	Mon,  7 Apr 2008 11:18:57 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86])
	by core3.amsl.com (Postfix) with ESMTP id 15FF23A6DB6
	for <mip4@ietf.org>; Mon,  7 Apr 2008 11:18:57 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.25,618,1199692800"; d="scan'208";a="10412997"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-4.cisco.com with ESMTP; 07 Apr 2008 11:18:35 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m37IIakf027176; 
	Mon, 7 Apr 2008 11:18:36 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m37IIaEW023294;
	Mon, 7 Apr 2008 18:18:36 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); 
	Mon, 7 Apr 2008 11:18:36 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 7 Apr 2008 11:18:34 -0700
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5205D17280@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <d3886a520804070241k3a1f53f0ye00327adb22351b4@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
	foreignagent failed authentication
Thread-Index: AciYk6PMe+ea2k74SRWj8jPUMwW8KQAR1UXQ
From: "Kent Leung (kleung)" <kleung@cisco.com>
To: "George Tsirtsis" <tsirtsis@googlemail.com>,
	"Henrik Levkowetz" <henrik@levkowetz.com>
X-OriginalArrivalTime: 07 Apr 2008 18:18:36.0037 (UTC)
	FILETIME=[CB8D8B50:01C898DB]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4370; t=1207592316;
	x=1208456316; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kleung@cisco.com;
	z=From:=20=22Kent=20Leung=20(kleung)=22=20<kleung@cisco.com>
	|Subject:=20RE=3A=20[Mip4]=20RFC=203344=20-=20Home=20Agent=
	20Registration=20Code=20132=20-=20foreignagent=20failed=20au
	thentication |Sender:=20;
	bh=3s+B897pgHlZE0Il9hER3MAlPkIWmn5DLa35inqzLzA=;
	b=VdZuFoz4vzHWTfyriX0dAYw8DkynEJsOzAtonf5T+DIpghe1p5HdnDUvW0
	QYoaDEbjF1H/rjRVW6T1f78OExSvvoVB/p9Bi+hFCpUXVCkEoVPGaSPSpFEq
	9q1tVeVonj;
Authentication-Results: sj-dkim-3; header.From=kleung@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>, Acee Lindem <acee@redback.com>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
	foreignagent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi George.  I'm not clear by "sending a message to the FA when MN-HA
auth fails"?  Is this the RRP with error code 131?  If so, does the FA
forward the RRP to the MN?

Or the intention is to only notify the FA and not the MN to avoid DoS
attack?  

What happens if the MN is appending the FA-HA auth ext?

Today, FA already receive error code 131 when MN-HA auth failed if the
HA is sending the RRP.  I'm not sure what's new here.  
  
Kent 

-----Original Message-----
From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of
George Tsirtsis
Sent: Monday, April 07, 2008 2:42 AM
To: Henrik Levkowetz
Cc: Mobile IPv4 Mailing List; Acee Lindem
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
foreignagent failed authentication

Hi all,

 I have the following comments you may want to consider:

1) The SHOULD language is very strong. SHOULD in an RFC means that the
IETF thinks that the procedure should be followed by all implementations
unless the implementor has a very good reason not to do so. In other
words, and in this case, the RFC says that the IETF thinks HAs should
send these 131(MN auth failed)/132(FA auth failed) codes, although not
sending them does not break interoperability.

The recent discussion indicates that we are not so sure that this is the
correct course of "default" action. On the contrary one should think
carefuly if there is a potential DoS attack in a given
implementation/deployment and then decide whether such messages should
be sent. If that is what we think then the correct language in that "the
HA SHOULD NOT send RREP messages" in this case.

2) If MN-HA auth fails notify the FA! What I think would make most sense
is something like the following::

-  if MN-FA auth fails:
 "the HA MUST discard the message and SHOULD NOT send any response."

- If the MN-FA auth fails, however:
 "the HA MUST discard the message and MAY send a response (with code
131) to the FA if one exists, otherwise the HA SHOULD NOT send any
response"

I think sending a message to the FA when the MN-HA auth fails makes
sense don't you?

Again I am not sure if RFC3344bis can acommodate such change, since this
would require FAs to understand code 131, which may not do currently.
Still I do not think this would really break any implementation, Most
likely an FA would just log the error, not knowing what to do next
beyond understanding this as a rejection.

Thoughts?
George


2008/4/5 Henrik Levkowetz <henrik@levkowetz.com>:
> Hi Acee,
>
>  Your post sums it up pretty much, but let me add this:  In some  
> situations and deployments, mainly when you're setting up a new  
> deployment environment, you actually want to generate the replies  for

> debugging and informative purposes, while mostly you want to  turn 
> them off to avoid DoS attacks.  At least one HA implementation  I know

> has the behaviour configurable, for that reason.  And as  the RFC 3344

> and 3344bis text seems to match this usage reasonably  well, I don't 
> think we want to change it?
>
>
>         Henrik
>
>  On 2008-04-04 21:01 Acee Lindem said the following:
>
>
>
> > Any opinions?
> > Thanks,
> > Acee
> > On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:
> >
> >
> > > With respect to our MIP4 HA implementation, we've had several
> discussions as to whether a registration reply should be generated  
> when the registration request fails FA-HA authentication. The  
> existence of the 132 reply code would imply that one should always  
> respond. However, this is contrary to way authentication works in  
> most protocols (at least routing
> protocols) and would seem to leave  the HA more susceptible to DoS
attacks.
> I checked the RFC 3344 BIS  draft and there has been no change in this
area.
> > > Thanks,
> > > Acee
> > >
> >
> >
>
>
> --
>  Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>  Supplemental site: http://www.mip4.org/
>
>
--
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Mon Apr  7 12:10:42 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DFC163A6809;
	Mon,  7 Apr 2008 12:10:42 -0700 (PDT)
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 B62A628C2C9
	for <mip4@core3.amsl.com>; Mon,  7 Apr 2008 12:10:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Qv847PdbMkTZ for <mip4@core3.amsl.com>;
	Mon,  7 Apr 2008 12:10:29 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56])
	by core3.amsl.com (Postfix) with ESMTP id 7451E28C3AA
	for <mip4@ietf.org>; Mon,  7 Apr 2008 12:10:24 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m37JAMR03181; Mon, 7 Apr 2008 19:10:22 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 7 Apr 2008 14:10:16 -0500
Message-ID: <C5A96676FCD00745B64AE42D5FCC9B6E178C5ED0@zrc2hxm0.corp.nortel.com>
In-Reply-To: <d3886a520804070948u6c8cd4e1gdceab669742c9ac2@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] RFC 3344 - Home Agent Registration Code 132 - foreign
	agent failed authentication
Thread-Index: AciYzz45qX8DrJ1FSSmTmE5HNUdGgQAE5Rlg
References: <15ABAEBC-3ADC-40C1-B044-E02A79D474A6@redback.com>
	<E45A1B6B-D754-48FA-AECC-BE35F6C4CE9D@redback.com>
	<47F7D785.60003@levkowetz.com>
	<d3886a520804070241k3a1f53f0ye00327adb22351b4@mail.gmail.com>
	<d3886a520804070848w380815b1i77901820bc7e4425@mail.gmail.com>
	<C5A96676FCD00745B64AE42D5FCC9B6E178C5965@zrc2hxm0.corp.nortel.com>
	<d3886a520804070948u6c8cd4e1gdceab669742c9ac2@mail.gmail.com>
From: "Ahmad Muhanna" <amuhanna@nortel.com>
To: "George Tsirtsis" <tsirtsis@googlemail.com>
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>, Acee Lindem <acee@redback.com>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 - foreign
	agent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

George,

Is there a mechanism in RFC3344 or anywwhere else that the HA can send a
RRP that only destined to the FA?
I am not aware of that functionality, could you please explain.

Thanks.

Regards,
Ahmad
 

> -----Original Message-----
> From: George Tsirtsis [mailto:tsirtsis@googlemail.com] 
> Sent: Monday, April 07, 2008 11:49 AM
> To: Muhanna, Ahmad (RICH1:2H10)
> Cc: Henrik Levkowetz; Mobile IPv4 Mailing List; Acee Lindem
> Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 
> 132 - foreign agent failed authentication
> 
> On Mon, Apr 7, 2008 at 5:36 PM, Ahmad Muhanna 
> <amuhanna@nortel.com> wrote:
> > George, let me understand what you are trying to say:
> >
> >  1. If FA-HA authentication fails, then HA MUST discard the message 
> > and  HA SHOULD not send any response. This is irrelevant to what 
> > happens with  MN-HA AE, because if FA-HA fails there is no 
> point to validate MN-HA AE.
> >
> 
> GT> Yes
> 
> >  2. If MN-HA AE fails, then?
> >
> >  2.1. Does this mean that FA-HA AE was present and was 
> successfully  
> > processed? If yes, it makes a lot of sense to send a RRP to the MN 
> > with  code 131.
> >
> 
> GT> Not exactly. What I am saying is that in this case the HA should
> notify the FA (not the MN!). Remember the MN may be an 
> attacker in which case the FA needs to be notified of that 
> possibility.
> 
> >  2.2. Id FA-HA AE is not there, then probably it is less 
> stronger for 
> > the  HA to send RRP with an error code 131.
> 
> GT> I still think that if it is known that an FA exists (whether FA-HA
> AE is used or not) it is useful to notify the FA (again not the MN).
> 
> > However, sending RRP with error
> >  code in normal case is very useful. I agree that MN and HA 
> should be 
> > in  sync but there is a possibility for errors and there is nothing 
> > wrong to  inform the MN whenever safe and necessary.
> >
> 
> GT> Of course sending RRP with error codes e.g., if the timestamp is
> wrong or some other reason is very important....here we are 
> just talking about the special case of authentication failures.
> 
> >  However, in general, I support leaving RFC3344 wording as is. Why?
> >
> >  I agree with George on the definition of SHOULD. BUT what 
> more of a  
> > reason than a DoS attack for the HA not to send a RRQ with 
> error code
> >  131 or any other code. I would rather leave it to implementation 
> > rather  than go through every single scenario and document it here. 
> > Back to the  same discussion, let us leave some room for those 
> > architect to do some  work and identify how their HA will 
> address DoS 
> > attack. There are many  ways to do it and at the same time 
> continue to 
> > satisfy the SHOULD as per  RFC3344.
> >
> 
> GT> I think if people are not comfortable with describing in
> RFC3344bis the behavior I argue for above, at least the 
> SHOULD, should be changed to MAY or even SHOULD NOT, 
> depending how strong a message we want to give. Note that non 
> of these changes breaks existing implementations. To break 
> existing implementation we would have to change this to MUST NOT.
> 
> Tegards
> George
> >
> >
> >  > -----Original Message-----
> >  > From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On  > 
> > Behalf Of George Tsirtsis
> >
> > > Sent: Monday, April 07, 2008 10:49 AM
> >  > To: Henrik Levkowetz
> >  > Cc: Mobile IPv4 Mailing List; Acee Lindem  > Subject: Re: [Mip4] 
> > RFC 3344 - Home Agent Registration Code  > 132 - foreign 
> agent failed 
> > authentication  >
> >
> >
> > > See a correction below (Thanks to Ahmad for spotting the mistake)
> >  >
> >  > On Mon, Apr 7, 2008 at 10:41 AM, George Tsirtsis  > 
> > <tsirtsis@googlemail.com> wrote:
> >  > > Hi all,
> >  > >
> >  > >   I have the following comments you may want to consider:
> >  > >
> >  > >  1) The SHOULD language is very strong. SHOULD in an RFC means 
> > that  > > the  IETF thinks that the procedure should be followed by 
> > all  > > implementations unless the implementor has a very good  > 
> > reason not to  > > do so. In other words, and in this case, the RFC 
> > says that  > the IETF  > > thinks HAs should send these 131(MN auth 
> > failed)/132(FA  > auth failed)  > > codes, although not 
> sending them 
> > does not break interoperability.
> >  > >
> >  > >  The recent discussion indicates that we are not so 
> sure  > that 
> > this is  > > the correct course of "default" action. On the 
> contrary 
> > one should  > > think carefuly if there is a potential DoS 
> attack in a 
> > given  > > implementation/deployment and then decide 
> whether such  > 
> > messages should  > > be sent. If that is what we think then the 
> > correct language  > in that  > > "the HA SHOULD NOT send RREP 
> > messages" in this case.
> >  > >
> >  > >  2) If MN-HA auth fails notify the FA! What I think 
> would  > make 
> > most  > > sense is something like the following::
> >  > >
> >  > >  -  if MN-FA auth fails:
> >  >
> >  > GT> This should have been:
> >  >  - If the FA-HA auth fails, however  >
> >  > >   "the HA MUST discard the message and SHOULD NOT send any
> >  > response."
> >  > >
> >  >
> >  > >  - If the MN-FA auth fails, however:
> >  >
> >  > GT> This should have been:
> >  >  - If the MN-HA auth fails, however:
> >  >
> >  > >   "the HA MUST discard the message and MAY send a response
> >  > (with code
> >  > >  131) to the FA if one exists, otherwise the HA SHOULD NOT  > 
> > send any  > > response"
> >  > >
> >  > >  I think sending a message to the FA when the MN-HA 
> auth  > fails 
> > makes  > > sense don't you?
> >  > >
> >  > >  Again I am not sure if RFC3344bis can acommodate such 
>  > change, 
> > since  > > this would require FAs to understand code 131, which may 
> > not do  > > currently. Still I do not think this would really break 
> > any  > > implementation, Most likely an FA would just log 
> the error, 
> > not  > > knowing what to do next beyond understanding this as a 
> > rejection.
> >  > >
> >  > >  Thoughts?
> >  > >  George
> >  > >
> >  > >
> >  > >  2008/4/5 Henrik Levkowetz <henrik@levkowetz.com>:
> >  > >
> >  > >
> >  > > > Hi Acee,
> >  > >  >
> >  > >  >  Your post sums it up pretty much, but let me add this:
> >  > In some  >
> >  > > situations and deployments, mainly when you're setting 
> up a new  
> > >  > > deployment environment, you actually want to generate the  > 
> > replies  >  > > for debugging and informative purposes, 
> while mostly 
> > you  > want to  >  > > turn them off to avoid DoS attacks.  
> At least 
> > one HA  > implementation  >  > > I know has the behaviour 
> > configurable, for that reason.  And as  >  > > the RFC 3344 and 
> > 3344bis text seems to match this usage  > reasonably  >  > 
> > well, I 
> > don't think we want to change it?
> >  > >  >
> >  > >  >
> >  > >  >         Henrik
> >  > >  >
> >  > >  >  On 2008-04-04 21:01 Acee Lindem said the following:
> >  > >  >
> >  > >  >
> >  > >  >
> >  > >  > > Any opinions?
> >  > >  > > Thanks,
> >  > >  > > Acee
> >  > >  > > On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:
> >  > >  > >
> >  > >  > >
> >  > >  > > > With respect to our MIP4 HA implementation, 
> we've  > had 
> > several  > > > discussions as to whether a registration 
> reply should 
> > be  > generated  > > when the  > registration request fails FA-HA 
> > authentication. The  > > existence of the 132  > reply code would 
> > imply that one  > should always  > > respond. However, this is  > 
> > contrary to way authentication  > works in  > > most protocols (at 
> > least routing  > protocols) and would  > seem to leave  the HA more 
> > susceptible to DoS attacks.
> >  > >  > I checked the RFC 3344 BIS  draft and there has been no  > 
> > change in this area.
> >  > >  > > > Thanks,
> >  > >  > > > Acee
> >  > >  > > >
> >  > >  > >
> >  > >  > >
> >  > >  >
> >  > >  >
> >  > >  > --
> >  > >
> >  > >
> >  > > >  Mip4 mailing list: Mip4@ietf.org
> >  > >  >     Web interface: 
> https://www.ietf.org/mailman/listinfo/mip4
> >  > >  >      Charter page:
> >  > http://www.ietf.org/html.charters/mip4-charter.html
> >  > >  >  Supplemental site: http://www.mip4.org/  >  >  > >  > --
> >
> >
> > > Mip4 mailing list: Mip4@ietf.org
> >  >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
> >  >      Charter page: 
> http://www.ietf.org/html.charters/mip4-charter.html
> >  > Supplemental site: http://www.mip4.org/  >
> >
> 
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Mon Apr  7 18:27:06 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9B54E3A6C42;
	Mon,  7 Apr 2008 18:27:06 -0700 (PDT)
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 9C89B28C16B
	for <mip4@core3.amsl.com>; Mon,  7 Apr 2008 18:27:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.023
X-Spam-Level: 
X-Spam-Status: No, score=-2.023 tagged_above=-999 required=5 tests=[AWL=0.576, 
	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 hhjqwMDqMwwn for <mip4@core3.amsl.com>;
	Mon,  7 Apr 2008 18:27:04 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by core3.amsl.com (Postfix) with ESMTP id 9BA4E3A6BF3
	for <mip4@ietf.org>; Mon,  7 Apr 2008 18:27:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP id 7B0B7CF42F7;
	Mon,  7 Apr 2008 18:27:19 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1])
	by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 09597-08; Mon,  7 Apr 2008 18:27:19 -0700 (PDT)
Received: from [*????n?IPv6???1] (login005.redback.com [155.53.12.64])
	by prattle.redback.com (Postfix) with ESMTP id 0C555CF42F6;
	Mon,  7 Apr 2008 18:27:18 -0700 (PDT)
In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC5205D1726E@xmb-sjc-235.amer.cisco.com>
References: <2979E38DD6FC6544B789C8DAD7BAFC5205D1726E@xmb-sjc-235.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <610F564D-AB4E-43B0-81C1-9E8974B35A5B@redback.com>
From: Acee Lindem <acee@redback.com>
Date: Mon, 7 Apr 2008 21:27:18 -0400
To: Kent Leung (kleung) <kleung@cisco.com>
X-Mailer: Apple Mail (2.753)
X-Virus-Scanned: by amavisd-new at redback.com
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
	foreignagent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org


On Apr 7, 2008, at 2:10 PM, Kent Leung (kleung) wrote:

> Isn't there a significantly higher chance of DoS attacks from MNs  
> (i.e.
> invalid MN-HA Auth Ext) than from FAs (i.e. invalid FA-HA Auth Ext)?

Yes. This seems like a more likely attack.

> When FA-HA authentication fails, it's usually due to misconfiguration.
> Of course, a rogue MN can append FA-HA Auth Ext in the request.
>
> I've always preferred not to send reply when authentication failed by
> only logging the event.  But then always runs into cases when the  
> reply
> was required.  So I think it's up to implementation to decide the
> sending of the RRP or not when authentication fails.  Not sure if
> changing the RFC is necessary.

Would you be opposed to changing the "SHOULD" to a "MAY" as proposed  
by George?

Thanks,
Acee


>
> Kent
>
> -----Original Message-----
> From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On  
> Behalf Of
> Acee Lindem
> Sent: Friday, April 04, 2008 12:02 PM
> Cc: Mobile IPv4 Mailing List
> Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
> foreignagent failed authentication
>
> Any opinions?
> Thanks,
> Acee
> On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:
>
>> With respect to our MIP4 HA implementation, we've had several
>> discussions as to whether a registration reply should be generated
>> when the registration request fails FA-HA authentication. The
>> existence of the 132 reply code would imply that one should always
>> respond. However, this is contrary to way authentication works in  
>> most
>
>> protocols (at least routing protocols) and would seem to leave the HA
>> more susceptible to DoS attacks. I checked the RFC 3344 BIS draft and
>> there has been no change in this area.
>> Thanks,
>> Acee
>
> --
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
> -- 
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/

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


From mip4-bounces@ietf.org  Mon Apr  7 22:33:05 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 902E23A6C8E;
	Mon,  7 Apr 2008 22:33:05 -0700 (PDT)
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 B344F28C293
	for <mip4@core3.amsl.com>; Mon,  7 Apr 2008 22:33:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.151
X-Spam-Level: 
X-Spam-Status: No, score=-0.151 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765,
	HOST_EQ_STATICB=1.372, HOST_MISMATCH_COM=0.311]
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 t1-hq8aEJMV6 for <mip4@core3.amsl.com>;
	Mon,  7 Apr 2008 22:33:02 -0700 (PDT)
Received: from hitachihk8.hitachi.cn (static-ip-174-194-65-202.rev.dyxnet.com
	[202.65.194.174])
	by core3.amsl.com (Postfix) with ESMTP id D7FF53A6C32
	for <mip4@ietf.org>; Mon,  7 Apr 2008 22:33:00 -0700 (PDT)
Received: (qmail 15226 invoked from network); 8 Apr 2008 05:33:13 -0000
X-NetworkBox-HamSign: 0101;OUT;hitachihk8;935231692238af1d2b7543ba73ed24b9;
Received: from unknown (HELO hitachihk7.hitachi.cn) (170.95.94.4)
	by 170.95.94.11 with SMTP; 8 Apr 2008 05:33:12 -0000
Received: (qmail 15560 invoked from network); 8 Apr 2008 05:33:11 -0000
X-NetworkBox-HamSign: 0101;OUT;hitachihk7;5caa839eceb6018f269355f7a24cac39;
Received: from hchidc401.hitachi-china.com (170.95.94.69)
	by 172.16.10.10 with SMTP; 8 Apr 2008 05:33:11 -0000
Received: from hchibjrdpyang ([10.96.2.35]) by hchidc401.hitachi-china.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 8 Apr 2008 13:33:10 +0800
From: "Peng Yang" <pyang@hitachi.cn>
To: "'McCann Peter-A001034'" <pete.mccann@motorola.com>,
	<mip4@ietf.org>
Date: Tue, 8 Apr 2008 13:33:12 +0800
Message-ID: <008b01c8993a$09823420$2302600a@hitachichina.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD130272ABAE@de01exm67.ds.mot.com>
Importance: Normal
X-OriginalArrivalTime: 08 Apr 2008 05:33:10.0442 (UTC)
	FILETIME=[082DA0A0:01C8993A]
X-Scanned-By-hitachihk7: Virus scan performed by network-box
X-Scanned-By-hitachihk7: Scanner file id is hitachihk7-1207632791.153-15555-000
X-Scanned-By-hitachihk7: No known viruses found in message (received+scanned
	in 0.01/0.27 secs)
X-Scanned-By-hitachihk7: Spam-Check-Result: No,
	hits=0 required=7 tests= autolearn=no version=2.0
X-Scanned-By-hitachihk8: Virus scan performed by network-box
X-Scanned-By-hitachihk8: Scanner file id is hitachihk8-1207632793.297-15197-000
X-Scanned-By-hitachihk8: No known viruses found in message (received+scanned
	in 0.04/0.09 secs)
X-Scanned-By-hitachihk8: Spam-Check-Result: No,
	hits=0 required=7 tests= autolearn=no version=2.0
X-Scanned-By-hitachihk8: Whitelisted with valid signature (outbound via
	Network Box hitachihk7)
Cc: henrik@levkowetz.com
Subject: Re: [Mip4] WGLC: 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: <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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi, Folks in MIP4:

I am in favor of this solution. It provides rich flexibility, while some
information should be shared among MIPv4 nodes (MN/FA/HA) explicitly.
And, with the built-in replay protection and generic security schemes in
RFC3344, we DO NOT need to worry about security risks to support this
new protocol. 

All in all, I support this solution to go though IESG for request of
publication as standard RFC. 

BRG
P.Y

> >-----Original Message-----
> >From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf
Of
> >McCann Peter-A001034
> >Sent: Saturday, April 05, 2008 1:17 AM
> >To: mip4@ietf.org
> >Cc: henrik@levkowetz.com
> >Subject: [Mip4] WGLC:
draft-ietf-mip4-generic-notification-message-04.txt
> >
> >This message announces a 2-week working group last call on:
> >
> >"Generic Notification Message for Mobile IPv4"
> >draft-ietf-mip4-generic-notification-message-04.txt
> >
> >The last call will end at 24:00 UTC on Friday, April 18 2008.
> >
> >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-notificatio
n
> >-message-04.txt
> >
> >
> >Please respond to this working group last call:
> >
> >* If you have no comments on the draft, and support its advancement,
> >  simply respond with a line containing something like
> >
> >    "I support the advancement of this document to the IESG with a
> >     request for publication as a Proposed Standard RFC."
> >
> >   If you have comments, please use a line similar to the one above,
> >   and supplement this with your comments.
> >
> >
> >* If you *don't* support its advancement, respond with a line
> >  containing something like the following, supplemented by your
> >  comments -
> >
> >    "I don't support the advancement of this document to the IESG
with
> >     a request for publication as a Proposed Standard RFC, for the
> >     following reasons:"
> >    ...
> >
> >Please direct all replies to the Mobile IPv4 mailing list,
> >mip4@ietf.org.
> >
> >
> >-Pete
> >--
> >Mip4 mailing list: Mip4@ietf.org
> >    Web interface: https://www.ietf.org/mailman/listinfo/mip4
> >     Charter page:
http://www.ietf.org/html.charters/mip4-charter.html
> >Supplemental site: http://www.mip4.org/

Disclaimer:
The contents of this e-mail, and its attachments, if any, are confidential and may be protected
by law against any unauthorized use.  If you have received this e-mail by mistake or have
reason to believe that you are not the intended recipient, please notify the sender by reply
e-mail as soon as possible and delete it from your computer system immediately thereafter.
If you are not the intended recipient, you must not copy this e-mail or attachment or disclose
the contents to any other person.  While we have made every effort to keep our network virus free,
we take no responsibility for any computer virus which might be transferred by way of this e-mail.
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Tue Apr  8 01:54:40 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 484F628C1B8;
	Tue,  8 Apr 2008 01:54:40 -0700 (PDT)
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 7DBB23A6E83
	for <mip4@core3.amsl.com>; Tue,  8 Apr 2008 01:54:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level: 
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[AWL=0.676, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 whVSVtxGSgYS for <mip4@core3.amsl.com>;
	Tue,  8 Apr 2008 01:54:38 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175])
	by core3.amsl.com (Postfix) with ESMTP id AA9ED28C1B8
	for <mip4@ietf.org>; Tue,  8 Apr 2008 01:54:37 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 25so1924254wfa.31
	for <mip4@ietf.org>; Tue, 08 Apr 2008 01:54:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=+X1cFy+PCKAl6GJmsKtiEaTueSJ3SNTVCErlX/Kdurk=;
	b=q7fgRfRZ57efYtIKHOUruRrMZfxhfxbkUOdSW+wlnDboYEAv/An1ZSWxApY5m1XhHqYaXM4f2taB0jPcz/J4DbLMrpieWUoTzzxibLwfkfLIQC227bqLZV4vEeXDYGEEiSP96oNjNXr6FLlo0FP2Ey5y9KSV8dKwBFT6nmeL1Ec=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=VrMbpClwqjUksymvxhkIp+Y+3+FM8/seqlnWk6meYMWs1KKDErBbiUstkeSdH6VznTENENgEuV0009bHhYxXnwC3b45/i+sw21GeMtc6PzTUs2FIsOXcj2gvE75DMnVmSjtvQllCClEx/8caUq44pFg4/KHPxqQVA0OaaS5IbIw=
Received: by 10.143.11.15 with SMTP id o15mr1614013wfi.310.1207644893007;
	Tue, 08 Apr 2008 01:54:53 -0700 (PDT)
Received: by 10.142.224.10 with HTTP; Tue, 8 Apr 2008 01:54:52 -0700 (PDT)
Message-ID: <d3886a520804080154y34eaa083rb02d6f826d19db04@mail.gmail.com>
Date: Tue, 8 Apr 2008 09:54:52 +0100
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Kent Leung (kleung)" <kleung@cisco.com>
In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC5205D17280@xmb-sjc-235.amer.cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <d3886a520804070241k3a1f53f0ye00327adb22351b4@mail.gmail.com>
	<2979E38DD6FC6544B789C8DAD7BAFC5205D17280@xmb-sjc-235.amer.cisco.com>
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>, Acee Lindem <acee@redback.com>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
	foreignagent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi Kent et.al.,

What I am saying is two things:

1) in general sending a reply when authentication fails is bad
practice and should not be recommended by IETF RFCs. So the "SHOULD"
language is too strong. IMO it should either become SHOULD NOT, or at
MAY with a warning of the possible attack.

2) In the special case where,
    a) the HA knows for a fact that a valid FA exists (i.e., an FA-HA
AE checks out), and
    b) if the MN-HA AE fails,
it makes sense for the HA to notify the FA of that fact (presumably
using 131 code). In that case I think the RFC should say that the FA
again SHOULD NOT forward the response to the MN, or at worse MAY
forward it with a warning of the possible attack.

I think both of the above are correct but I will understand if people
do not want to both with (2), in which case we can just do (1).

I hope the above is clear but see some more below...

On Mon, Apr 7, 2008 at 7:18 PM, Kent Leung (kleung) <kleung@cisco.com> wrote:
> Hi George.  I'm not clear by "sending a message to the FA when MN-HA
>  auth fails"?  Is this the RRP with error code 131?  If so, does the FA
>  forward the RRP to the MN?
>

GT> No I think the FA should not forward it as I say in (1) above.

>  Or the intention is to only notify the FA and not the MN to avoid DoS
>  attack?
>

GT> Yes, exactly. The problem is of course that existing FA
implementations maybe forwarding this message by default but I think
that is fine.

>  What happens if the MN is appending the FA-HA auth ext?
>

GT> Then the FA-HA AE will fail and will not meet the special case
condition (2a) above so no response should be sent by the HA.

>  Today, FA already receive error code 131 when MN-HA auth failed if the
>  HA is sending the RRP.  I'm not sure what's new here.
>

GT> Maybe now it is clearer?

>
>  Kent
>
>  -----Original Message-----
>  From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of
>
> George Tsirtsis
>  Sent: Monday, April 07, 2008 2:42 AM
>  To: Henrik Levkowetz
>
> Cc: Mobile IPv4 Mailing List; Acee Lindem
>  Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
>  foreignagent failed authentication
>
>
>
> Hi all,
>
>   I have the following comments you may want to consider:
>
>  1) The SHOULD language is very strong. SHOULD in an RFC means that the
>  IETF thinks that the procedure should be followed by all implementations
>  unless the implementor has a very good reason not to do so. In other
>  words, and in this case, the RFC says that the IETF thinks HAs should
>  send these 131(MN auth failed)/132(FA auth failed) codes, although not
>  sending them does not break interoperability.
>
>  The recent discussion indicates that we are not so sure that this is the
>  correct course of "default" action. On the contrary one should think
>  carefuly if there is a potential DoS attack in a given
>  implementation/deployment and then decide whether such messages should
>  be sent. If that is what we think then the correct language in that "the
>  HA SHOULD NOT send RREP messages" in this case.
>
>  2) If MN-HA auth fails notify the FA! What I think would make most sense
>  is something like the following::
>
>  -  if MN-FA auth fails:
>   "the HA MUST discard the message and SHOULD NOT send any response."
>
>  - If the MN-FA auth fails, however:
>   "the HA MUST discard the message and MAY send a response (with code
>  131) to the FA if one exists, otherwise the HA SHOULD NOT send any
>  response"
>
>  I think sending a message to the FA when the MN-HA auth fails makes
>  sense don't you?
>
>  Again I am not sure if RFC3344bis can acommodate such change, since this
>  would require FAs to understand code 131, which may not do currently.
>  Still I do not think this would really break any implementation, Most
>  likely an FA would just log the error, not knowing what to do next
>  beyond understanding this as a rejection.
>
>  Thoughts?
>  George
>
>
>  2008/4/5 Henrik Levkowetz <henrik@levkowetz.com>:
>  > Hi Acee,
>  >
>  >  Your post sums it up pretty much, but let me add this:  In some
>  > situations and deployments, mainly when you're setting up a new
>  > deployment environment, you actually want to generate the replies  for
>
>  > debugging and informative purposes, while mostly you want to  turn
>  > them off to avoid DoS attacks.  At least one HA implementation  I know
>
>  > has the behaviour configurable, for that reason.  And as  the RFC 3344
>
>  > and 3344bis text seems to match this usage reasonably  well, I don't
>  > think we want to change it?
>  >
>  >
>  >         Henrik
>  >
>  >  On 2008-04-04 21:01 Acee Lindem said the following:
>  >
>  >
>  >
>  > > Any opinions?
>  > > Thanks,
>  > > Acee
>  > > On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:
>  > >
>  > >
>  > > > With respect to our MIP4 HA implementation, we've had several
>  > discussions as to whether a registration reply should be generated
>  > when the registration request fails FA-HA authentication. The
>  > existence of the 132 reply code would imply that one should always
>  > respond. However, this is contrary to way authentication works in
>  > most protocols (at least routing
>  > protocols) and would seem to leave  the HA more susceptible to DoS
>  attacks.
>  > I checked the RFC 3344 BIS  draft and there has been no change in this
>  area.
>  > > > Thanks,
>  > > > Acee
>  > > >
>  > >
>  > >
>  >
>  >
>  > --
>  >  Mip4 mailing list: Mip4@ietf.org
>  >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>  >      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>  >  Supplemental site: http://www.mip4.org/
>  >
>  >
>  --
>  Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>  Supplemental site: http://www.mip4.org/
>
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Tue Apr  8 07:17:10 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1BF653A6ADB;
	Tue,  8 Apr 2008 07:17:10 -0700 (PDT)
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 C9B503A6A31
	for <mip4@core3.amsl.com>; Tue,  8 Apr 2008 07:17:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FDayfKjpMxYq for <mip4@core3.amsl.com>;
	Tue,  8 Apr 2008 07:17:04 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56])
	by core3.amsl.com (Postfix) with ESMTP id E0A973A6E20
	for <mip4@ietf.org>; Tue,  8 Apr 2008 07:17:03 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m38EHDP29389; Tue, 8 Apr 2008 14:17:13 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 8 Apr 2008 09:17:09 -0500
Message-ID: <C5A96676FCD00745B64AE42D5FCC9B6E17910016@zrc2hxm0.corp.nortel.com>
In-Reply-To: <d3886a520804080154y34eaa083rb02d6f826d19db04@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
	foreignagent failed authentication
Thread-Index: AciZVjxPaXvw1McnTDKFWQy4YSYfYwAKCmKQ
References: <d3886a520804070241k3a1f53f0ye00327adb22351b4@mail.gmail.com>
	<2979E38DD6FC6544B789C8DAD7BAFC5205D17280@xmb-sjc-235.amer.cisco.com>
	<d3886a520804080154y34eaa083rb02d6f826d19db04@mail.gmail.com>
From: "Ahmad Muhanna" <amuhanna@nortel.com>
To: "George Tsirtsis" <tsirtsis@googlemail.com>,
	"Kent Leung (kleung)" <kleung@cisco.com>
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>, Acee Lindem <acee@redback.com>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
	foreignagent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

George,

I am not sure where you are coming from on this issue! The best advice
is to "stop digging :)"

But let me say the following without addressing too many of the little
details of your attempt to change the whole Mobile IPv4 architecture to
address, IMO, a non-issue. Not only MIPv4 architecture you are trying to
change but you are proposing a new security architecture:)

RFC3344 implementations has been working for years and it works just
fine. We need to stop customizing the standard to fit certain scenario
here and there. Actually in order to be exact, certain views of handling
certain scenarios. MIP4 (RFC3344) assumes that the FA is a passive node
and all what it does (in this regard) it relays RRQ to the respected HA
or the RRP to the MN. How the FA would know then when to relay the RRP
and when NOT even those with code 131? What you are trying to articulate
is against RFC3344 architecture. May be you would like to have a new
draft out there for a new FA NOT only that but a new security
architecture. That is absolutely fine, then people will have a real
choice between what in RFC3344 and your proposal.

Please see one more comment inline.

Cheers!

Best Regards,
Ahmad
 

> -----Original Message-----
> From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On 
> Behalf Of George Tsirtsis
> Sent: Tuesday, April 08, 2008 3:55 AM
> To: Kent Leung (kleung)
> Cc: Mobile IPv4 Mailing List; Henrik Levkowetz; Acee Lindem
> Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 
> 132 - foreignagent failed authentication
> 
> Hi Kent et.al.,
> 
> What I am saying is two things:
> 
> 1) in general sending a reply when authentication fails is 
> bad practice and should not be recommended by IETF RFCs. So 
> the "SHOULD"
> language is too strong. IMO it should either become SHOULD 
> NOT, or at MAY with a warning of the possible attack.
> 
> 2) In the special case where,
>     a) the HA knows for a fact that a valid FA exists (i.e., 
> an FA-HA AE checks out), and
>     b) if the MN-HA AE fails,
> it makes sense for the HA to notify the FA of that fact 
> (presumably using 131 code). In that case I think the RFC 
> should say that the FA again SHOULD NOT forward the response 
> to the MN, or at worse MAY forward it with a warning of the 
> possible attack.

[Ahmad]
This is a very interesting security proposal!

RFC3344 made it optional to the MN and the FA to have a security
association MN-FA AE in order to secure the signaling link between the
MN and the FA (I believe for valid reasons). Later on, IETF introduced
MN-AAA AE as part of RFC3012 (RFC4721) to help resolving the same issue.
NOW: You are proposing a new mechanism where the FA relies on the MN-HA
AE to secure its link with the MN and identify bad rouge mobile node.
Wow!

As I said above, a new draft for this proposal will save a lot of people
a lot of time while at the same time keep RFC3344 SANE.

Best Regards,
Ahmad

> 
> I think both of the above are correct but I will understand 
> if people do not want to both with (2), in which case we can 
> just do (1).
> 
> I hope the above is clear but see some more below...
> 
> On Mon, Apr 7, 2008 at 7:18 PM, Kent Leung (kleung) 
> <kleung@cisco.com> wrote:
> > Hi George.  I'm not clear by "sending a message to the FA 
> when MN-HA  
> > auth fails"?  Is this the RRP with error code 131?  If so, 
> does the FA  
> > forward the RRP to the MN?
> >
> 
> GT> No I think the FA should not forward it as I say in (1) above.
> 
> >  Or the intention is to only notify the FA and not the MN 
> to avoid DoS  
> > attack?
> >
> 
> GT> Yes, exactly. The problem is of course that existing FA
> implementations maybe forwarding this message by default but 
> I think that is fine.
> 
> >  What happens if the MN is appending the FA-HA auth ext?
> >
> 
> GT> Then the FA-HA AE will fail and will not meet the special case
> condition (2a) above so no response should be sent by the HA.
> 
> >  Today, FA already receive error code 131 when MN-HA auth failed if 
> > the  HA is sending the RRP.  I'm not sure what's new here.
> >
> 
> GT> Maybe now it is clearer?
> 
> >
> >  Kent
> >
> >  -----Original Message-----
> >  From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] 
> On Behalf 
> > Of
> >
> > George Tsirtsis
> >  Sent: Monday, April 07, 2008 2:42 AM
> >  To: Henrik Levkowetz
> >
> > Cc: Mobile IPv4 Mailing List; Acee Lindem
> >  Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 -  
> > foreignagent failed authentication
> >
> >
> >
> > Hi all,
> >
> >   I have the following comments you may want to consider:
> >
> >  1) The SHOULD language is very strong. SHOULD in an RFC means that 
> > the  IETF thinks that the procedure should be followed by all 
> > implementations  unless the implementor has a very good 
> reason not to 
> > do so. In other  words, and in this case, the RFC says that 
> the IETF 
> > thinks HAs should  send these 131(MN auth failed)/132(FA 
> auth failed) 
> > codes, although not  sending them does not break interoperability.
> >
> >  The recent discussion indicates that we are not so sure 
> that this is 
> > the  correct course of "default" action. On the contrary one should 
> > think  carefuly if there is a potential DoS attack in a given  
> > implementation/deployment and then decide whether such 
> messages should  
> > be sent. If that is what we think then the correct language in that 
> > "the  HA SHOULD NOT send RREP messages" in this case.
> >
> >  2) If MN-HA auth fails notify the FA! What I think would make most 
> > sense  is something like the following::
> >
> >  -  if MN-FA auth fails:
> >   "the HA MUST discard the message and SHOULD NOT send any 
> response."
> >
> >  - If the MN-FA auth fails, however:
> >   "the HA MUST discard the message and MAY send a response 
> (with code
> >  131) to the FA if one exists, otherwise the HA SHOULD NOT 
> send any  
> > response"
> >
> >  I think sending a message to the FA when the MN-HA auth 
> fails makes  
> > sense don't you?
> >
> >  Again I am not sure if RFC3344bis can acommodate such 
> change, since 
> > this  would require FAs to understand code 131, which may 
> not do currently.
> >  Still I do not think this would really break any 
> implementation, Most  
> > likely an FA would just log the error, not knowing what to do next  
> > beyond understanding this as a rejection.
> >
> >  Thoughts?
> >  George
> >
> >
> >  2008/4/5 Henrik Levkowetz <henrik@levkowetz.com>:
> >  > Hi Acee,
> >  >
> >  >  Your post sums it up pretty much, but let me add this:  
> In some  > 
> > situations and deployments, mainly when you're setting up a new  > 
> > deployment environment, you actually want to generate the 
> replies  for
> >
> >  > debugging and informative purposes, while mostly you 
> want to  turn  
> > > them off to avoid DoS attacks.  At least one HA implementation  I 
> > know
> >
> >  > has the behaviour configurable, for that reason.  And as 
>  the RFC 
> > 3344
> >
> >  > and 3344bis text seems to match this usage reasonably  well, I 
> > don't  > think we want to change it?
> >  >
> >  >
> >  >         Henrik
> >  >
> >  >  On 2008-04-04 21:01 Acee Lindem said the following:
> >  >
> >  >
> >  >
> >  > > Any opinions?
> >  > > Thanks,
> >  > > Acee
> >  > > On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:
> >  > >
> >  > >
> >  > > > With respect to our MIP4 HA implementation, we've 
> had several  
> > > discussions as to whether a registration reply should be 
> generated  
> > > when the registration request fails FA-HA authentication. The  > 
> > existence of the 132 reply code would imply that one should 
> always  > 
> > respond. However, this is contrary to way authentication 
> works in  > 
> > most protocols (at least routing  > protocols) and would 
> seem to leave  
> > the HA more susceptible to DoS  attacks.
> >  > I checked the RFC 3344 BIS  draft and there has been no 
> change in 
> > this  area.
> >  > > > Thanks,
> >  > > > Acee
> >  > > >
> >  > >
> >  > >
> >  >
> >  >
> >  > --
> >  >  Mip4 mailing list: Mip4@ietf.org
> >  >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
> >  >      Charter page: 
> http://www.ietf.org/html.charters/mip4-charter.html
> >  >  Supplemental site: http://www.mip4.org/  >  >
> >  --
> >  Mip4 mailing list: Mip4@ietf.org
> >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
> >      Charter page: 
> http://www.ietf.org/html.charters/mip4-charter.html
> >  Supplemental site: http://www.mip4.org/
> >
> --
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
> 
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Tue Apr  8 07:43:21 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 43C6628C378;
	Tue,  8 Apr 2008 07:43:21 -0700 (PDT)
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 D153028C37E
	for <mip4@core3.amsl.com>; Tue,  8 Apr 2008 07:43:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.331
X-Spam-Level: 
X-Spam-Status: No, score=-1.331 tagged_above=-999 required=5 tests=[AWL=0.646, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 Z6wk8IEk8+1c for <mip4@core3.amsl.com>;
	Tue,  8 Apr 2008 07:43:18 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.171])
	by core3.amsl.com (Postfix) with ESMTP id 5B36728C33A
	for <mip4@ietf.org>; Tue,  8 Apr 2008 07:43:14 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 25so2060052wfa.31
	for <mip4@ietf.org>; Tue, 08 Apr 2008 07:43:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=fUE2yu9vuu7yDYr7KOXIyw0lavkB9a0RpzupB76zBbQ=;
	b=JQztt/RzJ9KYXfSnOY9JSKezGplLn8EZHeDxPlWhxdPLDQwMnWQGsaD2aT0sfjj5gmmUu3f7S9ohDkVOPGtvrGiYYUWTbEW5ssGBMcoN1jwsI6WQutUAI0L4T7BGrv2PxQtWTH6EtdMU21CNZwzzwLmNSnWXXx9jnBJJ5YDeuPM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=xBGo44dpvNrk6ASJB0dMlPOrKchH6pkR3CXa2F+RZpkk45xkG5+aNKrV35V6h1cecl/YaP8Y/uwpF3CwN10lIIRN1vK60l+LcamOUmGJuErVldesUD6bVQK+0Ke0DsBP9V31SaRJgEnnCEbKWZKrprr00/RUq4tfxsdkCNHgj/s=
Received: by 10.142.229.4 with SMTP id b4mr3130574wfh.158.1207665810166;
	Tue, 08 Apr 2008 07:43:30 -0700 (PDT)
Received: by 10.142.224.10 with HTTP; Tue, 8 Apr 2008 07:43:30 -0700 (PDT)
Message-ID: <d3886a520804080743s141ddafdo5e67c12d63856bfc@mail.gmail.com>
Date: Tue, 8 Apr 2008 15:43:30 +0100
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Ahmad Muhanna" <amuhanna@nortel.com>
In-Reply-To: <C5A96676FCD00745B64AE42D5FCC9B6E17910016@zrc2hxm0.corp.nortel.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <d3886a520804070241k3a1f53f0ye00327adb22351b4@mail.gmail.com>
	<2979E38DD6FC6544B789C8DAD7BAFC5205D17280@xmb-sjc-235.amer.cisco.com>
	<d3886a520804080154y34eaa083rb02d6f826d19db04@mail.gmail.com>
	<C5A96676FCD00745B64AE42D5FCC9B6E17910016@zrc2hxm0.corp.nortel.com>
Cc: "Kent Leung \(kleung\)" <kleung@cisco.com>,
	Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>, Acee Lindem <acee@redback.com>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
	foreignagent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Ahmad,

You could just say that you prefer not to change the RFC, instead of
all this nonsense about me proposing a different security
architecture.

As I said, I can understand if people do not want to bother with (2),
but at least (1) seems to be reasonable.

George

On Tue, Apr 8, 2008 at 3:17 PM, Ahmad Muhanna <amuhanna@nortel.com> wrote:
> George,
>
>  I am not sure where you are coming from on this issue! The best advice
>  is to "stop digging :)"
>
>  But let me say the following without addressing too many of the little
>  details of your attempt to change the whole Mobile IPv4 architecture to
>  address, IMO, a non-issue. Not only MIPv4 architecture you are trying to
>  change but you are proposing a new security architecture:)
>
>  RFC3344 implementations has been working for years and it works just
>  fine. We need to stop customizing the standard to fit certain scenario
>  here and there. Actually in order to be exact, certain views of handling
>  certain scenarios. MIP4 (RFC3344) assumes that the FA is a passive node
>  and all what it does (in this regard) it relays RRQ to the respected HA
>  or the RRP to the MN. How the FA would know then when to relay the RRP
>  and when NOT even those with code 131? What you are trying to articulate
>  is against RFC3344 architecture. May be you would like to have a new
>  draft out there for a new FA NOT only that but a new security
>  architecture. That is absolutely fine, then people will have a real
>  choice between what in RFC3344 and your proposal.
>
>  Please see one more comment inline.
>
>  Cheers!
>
>  Best Regards,
>  Ahmad
>
>
>
>  > -----Original Message-----
>  > From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On
>  > Behalf Of George Tsirtsis
>
> > Sent: Tuesday, April 08, 2008 3:55 AM
>  > To: Kent Leung (kleung)
>  > Cc: Mobile IPv4 Mailing List; Henrik Levkowetz; Acee Lindem
>  > Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code
>  > 132 - foreignagent failed authentication
>  >
>
> > Hi Kent et.al.,
>  >
>  > What I am saying is two things:
>  >
>  > 1) in general sending a reply when authentication fails is
>  > bad practice and should not be recommended by IETF RFCs. So
>  > the "SHOULD"
>  > language is too strong. IMO it should either become SHOULD
>  > NOT, or at MAY with a warning of the possible attack.
>  >
>  > 2) In the special case where,
>  >     a) the HA knows for a fact that a valid FA exists (i.e.,
>  > an FA-HA AE checks out), and
>  >     b) if the MN-HA AE fails,
>  > it makes sense for the HA to notify the FA of that fact
>  > (presumably using 131 code). In that case I think the RFC
>  > should say that the FA again SHOULD NOT forward the response
>  > to the MN, or at worse MAY forward it with a warning of the
>  > possible attack.
>
>  [Ahmad]
>  This is a very interesting security proposal!
>
>  RFC3344 made it optional to the MN and the FA to have a security
>  association MN-FA AE in order to secure the signaling link between the
>  MN and the FA (I believe for valid reasons). Later on, IETF introduced
>  MN-AAA AE as part of RFC3012 (RFC4721) to help resolving the same issue.
>  NOW: You are proposing a new mechanism where the FA relies on the MN-HA
>  AE to secure its link with the MN and identify bad rouge mobile node.
>  Wow!
>
>  As I said above, a new draft for this proposal will save a lot of people
>  a lot of time while at the same time keep RFC3344 SANE.
>
>  Best Regards,
>  Ahmad
>
>
>
>  >
>  > I think both of the above are correct but I will understand
>  > if people do not want to both with (2), in which case we can
>  > just do (1).
>  >
>  > I hope the above is clear but see some more below...
>  >
>  > On Mon, Apr 7, 2008 at 7:18 PM, Kent Leung (kleung)
>  > <kleung@cisco.com> wrote:
>  > > Hi George.  I'm not clear by "sending a message to the FA
>  > when MN-HA
>  > > auth fails"?  Is this the RRP with error code 131?  If so,
>  > does the FA
>  > > forward the RRP to the MN?
>  > >
>  >
>  > GT> No I think the FA should not forward it as I say in (1) above.
>  >
>  > >  Or the intention is to only notify the FA and not the MN
>  > to avoid DoS
>  > > attack?
>  > >
>  >
>  > GT> Yes, exactly. The problem is of course that existing FA
>  > implementations maybe forwarding this message by default but
>  > I think that is fine.
>  >
>  > >  What happens if the MN is appending the FA-HA auth ext?
>  > >
>  >
>  > GT> Then the FA-HA AE will fail and will not meet the special case
>  > condition (2a) above so no response should be sent by the HA.
>  >
>  > >  Today, FA already receive error code 131 when MN-HA auth failed if
>  > > the  HA is sending the RRP.  I'm not sure what's new here.
>  > >
>  >
>  > GT> Maybe now it is clearer?
>  >
>  > >
>  > >  Kent
>  > >
>  > >  -----Original Message-----
>  > >  From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org]
>  > On Behalf
>  > > Of
>  > >
>  > > George Tsirtsis
>  > >  Sent: Monday, April 07, 2008 2:42 AM
>  > >  To: Henrik Levkowetz
>  > >
>  > > Cc: Mobile IPv4 Mailing List; Acee Lindem
>  > >  Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
>  > > foreignagent failed authentication
>  > >
>  > >
>  > >
>  > > Hi all,
>  > >
>  > >   I have the following comments you may want to consider:
>  > >
>  > >  1) The SHOULD language is very strong. SHOULD in an RFC means that
>  > > the  IETF thinks that the procedure should be followed by all
>  > > implementations  unless the implementor has a very good
>  > reason not to
>  > > do so. In other  words, and in this case, the RFC says that
>  > the IETF
>  > > thinks HAs should  send these 131(MN auth failed)/132(FA
>  > auth failed)
>  > > codes, although not  sending them does not break interoperability.
>  > >
>  > >  The recent discussion indicates that we are not so sure
>  > that this is
>  > > the  correct course of "default" action. On the contrary one should
>  > > think  carefuly if there is a potential DoS attack in a given
>  > > implementation/deployment and then decide whether such
>  > messages should
>  > > be sent. If that is what we think then the correct language in that
>  > > "the  HA SHOULD NOT send RREP messages" in this case.
>  > >
>  > >  2) If MN-HA auth fails notify the FA! What I think would make most
>  > > sense  is something like the following::
>  > >
>  > >  -  if MN-FA auth fails:
>  > >   "the HA MUST discard the message and SHOULD NOT send any
>  > response."
>  > >
>  > >  - If the MN-FA auth fails, however:
>  > >   "the HA MUST discard the message and MAY send a response
>  > (with code
>  > >  131) to the FA if one exists, otherwise the HA SHOULD NOT
>  > send any
>  > > response"
>  > >
>  > >  I think sending a message to the FA when the MN-HA auth
>  > fails makes
>  > > sense don't you?
>  > >
>  > >  Again I am not sure if RFC3344bis can acommodate such
>  > change, since
>  > > this  would require FAs to understand code 131, which may
>  > not do currently.
>  > >  Still I do not think this would really break any
>  > implementation, Most
>  > > likely an FA would just log the error, not knowing what to do next
>  > > beyond understanding this as a rejection.
>  > >
>  > >  Thoughts?
>  > >  George
>  > >
>  > >
>  > >  2008/4/5 Henrik Levkowetz <henrik@levkowetz.com>:
>  > >  > Hi Acee,
>  > >  >
>  > >  >  Your post sums it up pretty much, but let me add this:
>  > In some  >
>  > > situations and deployments, mainly when you're setting up a new  >
>  > > deployment environment, you actually want to generate the
>  > replies  for
>  > >
>  > >  > debugging and informative purposes, while mostly you
>  > want to  turn
>  > > > them off to avoid DoS attacks.  At least one HA implementation  I
>  > > know
>  > >
>  > >  > has the behaviour configurable, for that reason.  And as
>  >  the RFC
>  > > 3344
>  > >
>  > >  > and 3344bis text seems to match this usage reasonably  well, I
>  > > don't  > think we want to change it?
>  > >  >
>  > >  >
>  > >  >         Henrik
>  > >  >
>  > >  >  On 2008-04-04 21:01 Acee Lindem said the following:
>  > >  >
>  > >  >
>  > >  >
>  > >  > > Any opinions?
>  > >  > > Thanks,
>  > >  > > Acee
>  > >  > > On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:
>  > >  > >
>  > >  > >
>  > >  > > > With respect to our MIP4 HA implementation, we've
>  > had several
>  > > > discussions as to whether a registration reply should be
>  > generated
>  > > > when the registration request fails FA-HA authentication. The  >
>  > > existence of the 132 reply code would imply that one should
>  > always  >
>  > > respond. However, this is contrary to way authentication
>  > works in  >
>  > > most protocols (at least routing  > protocols) and would
>  > seem to leave
>  > > the HA more susceptible to DoS  attacks.
>  > >  > I checked the RFC 3344 BIS  draft and there has been no
>  > change in
>  > > this  area.
>  > >  > > > Thanks,
>  > >  > > > Acee
>  > >  > > >
>  > >  > >
>  > >  > >
>  > >  >
>  > >  >
>  > >  > --
>  > >  >  Mip4 mailing list: Mip4@ietf.org
>  > >  >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>  > >  >      Charter page:
>  > http://www.ietf.org/html.charters/mip4-charter.html
>  > >  >  Supplemental site: http://www.mip4.org/  >  >
>  > >  --
>  > >  Mip4 mailing list: Mip4@ietf.org
>  > >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>  > >      Charter page:
>  > http://www.ietf.org/html.charters/mip4-charter.html
>  > >  Supplemental site: http://www.mip4.org/
>  > >
>  > --
>  > Mip4 mailing list: Mip4@ietf.org
>  >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>  >      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>  > Supplemental site: http://www.mip4.org/
>  >
>  --
>  Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>  Supplemental site: http://www.mip4.org/
>
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Tue Apr  8 08:52:57 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 587FD3A6AFB;
	Tue,  8 Apr 2008 08:52:57 -0700 (PDT)
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 6A59D3A685B
	for <mip4@core3.amsl.com>; Tue,  8 Apr 2008 08:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.334
X-Spam-Level: 
X-Spam-Status: No, score=-2.334 tagged_above=-999 required=5 tests=[AWL=0.265, 
	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 bQWxAQdqjbWQ for <mip4@core3.amsl.com>;
	Tue,  8 Apr 2008 08:52:53 -0700 (PDT)
Received: from merlot.tools.ietf.org (unknown
	[IPv6:2a01:3f0:0:31:214:22ff:fe21:bb])
	by core3.amsl.com (Postfix) with ESMTP id AF0783A6A31
	for <mip4@ietf.org>; Tue,  8 Apr 2008 08:52:53 -0700 (PDT)
Received: from localhost ([127.0.0.1]:46875 helo=chardonnay.local)
	by merlot.tools.ietf.org with esmtp (Exim 4.69)
	(envelope-from <henrik@levkowetz.com>)
	id 1JjG89-0001Dt-Me; Tue, 08 Apr 2008 17:53:05 +0200
Message-ID: <47FB94D7.8030908@levkowetz.com>
Date: Tue, 08 Apr 2008 17:52:55 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: George Tsirtsis <tsirtsis@googlemail.com>
References: <d3886a520804070241k3a1f53f0ye00327adb22351b4@mail.gmail.com>	<2979E38DD6FC6544B789C8DAD7BAFC5205D17280@xmb-sjc-235.amer.cisco.com>
	<d3886a520804080154y34eaa083rb02d6f826d19db04@mail.gmail.com>
In-Reply-To: <d3886a520804080154y34eaa083rb02d6f826d19db04@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, kleung@cisco.com, mip4@ietf.org,
	acee@redback.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: "Kent Leung \(kleung\)" <kleung@cisco.com>,
	Mobile IPv4 Mailing List <mip4@ietf.org>, Acee Lindem <acee@redback.com>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132
 -	foreignagent failed authentication
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="===============0384340819=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

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

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

Hi,

<hat type=3D"regular-bozo">

On 2008-04-08 10:54 George Tsirtsis said the following:
> Hi Kent et.al.,
>=20
> What I am saying is two things:
>=20
> 1) in general sending a reply when authentication fails is bad
> practice and should not be recommended by IETF RFCs. So the "SHOULD"
> language is too strong. IMO it should either become SHOULD NOT, or at
> MAY with a warning of the possible attack.

I'm in favour of changing the wording to "MAY".

>=20
> 2) In the special case where,
>     a) the HA knows for a fact that a valid FA exists (i.e., an FA-HA
> AE checks out), and
>     b) if the MN-HA AE fails,
> it makes sense for the HA to notify the FA of that fact (presumably
> using 131 code). In that case I think the RFC should say that the FA
> again SHOULD NOT forward the response to the MN, or at worse MAY
> forward it with a warning of the possible attack.

I'm not decided on this.  Personally, I'd like to see proposed text to
decide either way.


Regards,

	Henrik


</hat>


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

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

iD8DBQFH+5TheVhrtTJkXCMRApwyAJoDKmK+7LPv+ojCHYe8ShQYZJPyvACffQfw
79g6so1OzpuMQlbliX53uPo=
=v2wI
-----END PGP SIGNATURE-----

--------------enigFEA45E63F225DBC2EE61C54B--

--===============0384340819==
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/

--===============0384340819==--


From mip4-bounces@ietf.org  Tue Apr  8 08:57:55 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 39F5E3A6DB2;
	Tue,  8 Apr 2008 08:57:55 -0700 (PDT)
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 40C103A6DCD
	for <mip4@core3.amsl.com>; Tue,  8 Apr 2008 08:57:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[AWL=0.250, 
	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 5iln0dhrfB4h for <mip4@core3.amsl.com>;
	Tue,  8 Apr 2008 08:57:46 -0700 (PDT)
Received: from merlot.tools.ietf.org (unknown
	[IPv6:2a01:3f0:0:31:214:22ff:fe21:bb])
	by core3.amsl.com (Postfix) with ESMTP id 8BACE28C2F5
	for <mip4@ietf.org>; Tue,  8 Apr 2008 08:57:45 -0700 (PDT)
Received: from localhost ([127.0.0.1]:48421 helo=chardonnay.local)
	by merlot.tools.ietf.org with esmtp (Exim 4.69)
	(envelope-from <henrik@levkowetz.com>)
	id 1JjGCt-0001qW-MP; Tue, 08 Apr 2008 17:58:00 +0200
Message-ID: <47FB9607.9050509@levkowetz.com>
Date: Tue, 08 Apr 2008 17:57:59 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: Mobile IPv4 Mailing List <mip4@ietf.org>
References: <d3886a520804070241k3a1f53f0ye00327adb22351b4@mail.gmail.com>	<2979E38DD6FC6544B789C8DAD7BAFC5205D17280@xmb-sjc-235.amer.cisco.com>	<d3886a520804080154y34eaa083rb02d6f826d19db04@mail.gmail.com>	<C5A96676FCD00745B64AE42D5FCC9B6E17910016@zrc2hxm0.corp.nortel.com>
	<d3886a520804080743s141ddafdo5e67c12d63856bfc@mail.gmail.com>
In-Reply-To: <d3886a520804080743s141ddafdo5e67c12d63856bfc@mail.gmail.com>
X-Enigmail-Version: 0.95.6
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: 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
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132
 -	foreignagent failed authentication
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="===============0491660545=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

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

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

Hi,

In order to follow my own advise and efforts to get issue trackers more
used in the IETF, I've added this issue to the MIP4 issue tracker:
  http://tools.ietf.org/wg/mip4/trac/ticket/6

The open issues status for documents with issue tracker entries (for
working groups that have issue trackers on tools.ietf.org) are now visibl=
e
on the WG status page:
  http://tools.ietf.org/wg/mip4


Regards,

	Henrik


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

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

iD8DBQFH+5YHeVhrtTJkXCMRAoS8AJ9R0MFkmgxYaR2MltuadMXno1uDEQCgqB6J
gIuu/A/I6lFw1fhVGQws7DE=
=jkOd
-----END PGP SIGNATURE-----

--------------enigC42B27FFEDFA2CB41B038F9C--

--===============0491660545==
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/

--===============0491660545==--


From mip4-bounces@ietf.org  Tue Apr  8 09:18:36 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 13D4828C356;
	Tue,  8 Apr 2008 09:18:36 -0700 (PDT)
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 13AD93A69C6
	for <mip4@core3.amsl.com>; Tue,  8 Apr 2008 09:18:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.351
X-Spam-Level: 
X-Spam-Status: No, score=-6.351 tagged_above=-999 required=5 tests=[AWL=0.248, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AiqWnBR4CP1s for <mip4@core3.amsl.com>;
	Tue,  8 Apr 2008 09:18:31 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id 934603A6BB8
	for <mip4@ietf.org>; Tue,  8 Apr 2008 09:18:31 -0700 (PDT)
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-2.cisco.com with ESMTP; 08 Apr 2008 09:18:47 -0700
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 m38GIlSR010341; 
	Tue, 8 Apr 2008 09:18:47 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m38GIl68012553;
	Tue, 8 Apr 2008 16:18:47 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 8 Apr 2008 09:18:47 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 8 Apr 2008 09:18:44 -0700
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5205D176BD@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <610F564D-AB4E-43B0-81C1-9E8974B35A5B@redback.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] RFC 3344 - Home Agent Registration Code 132 -foreignagent
	failed authentication
Thread-Index: AciZF7G5EgEivW6oSJOtEsc/NAl+wAAeeUYw
From: "Kent Leung (kleung)" <kleung@cisco.com>
To: "Acee Lindem" <acee@redback.com>
X-OriginalArrivalTime: 08 Apr 2008 16:18:47.0733 (UTC)
	FILETIME=[39672650:01C89994]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3635; t=1207671527;
	x=1208535527; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kleung@cisco.com;
	z=From:=20=22Kent=20Leung=20(kleung)=22=20<kleung@cisco.com>
	|Subject:=20RE=3A=20[Mip4]=20RFC=203344=20-=20Home=20Agent=
	20Registration=20Code=20132=20-foreignagent=20failed=20authe
	ntication |Sender:=20;
	bh=cG4uu2VjEkdTNm6UXkagcpmTb70bwhxL0zx+zKxcevI=;
	b=BJGMIHKK4aNgTb86Pe9SOtzQNlPkJBMYfBwCrKaILkdSySB2EQ8AqfXT33
	0UNr8muQcfPfGZlbclPu1e5xlA/tu9OgrDYfPx7UaOTYSPSaa9Aok5eI2+s5
	Rh9fuabnzC;
Authentication-Results: sj-dkim-3; header.From=kleung@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132
	-foreignagent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

I have slight adversion to the language change.  Not because I disagree
with George's reasoning.  But on the fact that deployments and
implementations already have default behavior based on existing RFC.  So
not clear what is accomplished from the practical perspective.  Whatever
the default behavior is in the implementation, there will need to be a
knob for the alternative behavior.  So in essence, both needs to be
supported. The language change would only stir up unnecessary bickering
among vendors on whose default behavior is more right.

BTW, experience has shown that sending reply with error code 132 has
been advantageous.  The FA-HA authentication failure discovered
misconfiguration.  Have not seen any cases of DoS attack from FAs.  So I
prefer to leave the SHOULD as is.

Kent 

-----Original Message-----
From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of
Acee Lindem
Sent: Monday, April 07, 2008 6:27 PM
To: Kent Leung (kleung)
Cc: Mobile IPv4 Mailing List
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132
-foreignagent failed authentication


On Apr 7, 2008, at 2:10 PM, Kent Leung (kleung) wrote:

> Isn't there a significantly higher chance of DoS attacks from MNs 
> (i.e.
> invalid MN-HA Auth Ext) than from FAs (i.e. invalid FA-HA Auth Ext)?

Yes. This seems like a more likely attack.

> When FA-HA authentication fails, it's usually due to misconfiguration.
> Of course, a rogue MN can append FA-HA Auth Ext in the request.
>
> I've always preferred not to send reply when authentication failed by 
> only logging the event.  But then always runs into cases when the 
> reply was required.  So I think it's up to implementation to decide 
> the sending of the RRP or not when authentication fails.  Not sure if 
> changing the RFC is necessary.

Would you be opposed to changing the "SHOULD" to a "MAY" as proposed by
George?

Thanks,
Acee


>
> Kent
>
> -----Original Message-----
> From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf 
> Of Acee Lindem
> Sent: Friday, April 04, 2008 12:02 PM
> Cc: Mobile IPv4 Mailing List
> Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 - 
> foreignagent failed authentication
>
> Any opinions?
> Thanks,
> Acee
> On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:
>
>> With respect to our MIP4 HA implementation, we've had several 
>> discussions as to whether a registration reply should be generated 
>> when the registration request fails FA-HA authentication. The 
>> existence of the 132 reply code would imply that one should always 
>> respond. However, this is contrary to way authentication works in 
>> most
>
>> protocols (at least routing protocols) and would seem to leave the HA

>> more susceptible to DoS attacks. I checked the RFC 3344 BIS draft and

>> there has been no change in this area.
>> Thanks,
>> Acee
>
> --
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
> --
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/

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


From mip4-bounces@ietf.org  Tue Apr  8 09:28:35 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7404828C1D3;
	Tue,  8 Apr 2008 09:28:35 -0700 (PDT)
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 D2FBF3A6C5D
	for <mip4@core3.amsl.com>; Tue,  8 Apr 2008 09:28:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.413
X-Spam-Level: 
X-Spam-Status: No, score=-6.413 tagged_above=-999 required=5 tests=[AWL=0.186, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0NWVFYuaJVOH for <mip4@core3.amsl.com>;
	Tue,  8 Apr 2008 09:28:33 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 3DC153A6C40
	for <mip4@ietf.org>; Tue,  8 Apr 2008 09:28:33 -0700 (PDT)
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 08 Apr 2008 09:28:49 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m38GSncX001562; 
	Tue, 8 Apr 2008 09:28:49 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m38GSn8E016452;
	Tue, 8 Apr 2008 16:28:49 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); 
	Tue, 8 Apr 2008 09:28:49 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 8 Apr 2008 09:28:47 -0700
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5205D176CD@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <d3886a520804080154y34eaa083rb02d6f826d19db04@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
	foreignagent failed authentication
Thread-Index: AciZVjpMFduww4mETg+OWvcIvI/0LAAPiXTg
From: "Kent Leung (kleung)" <kleung@cisco.com>
To: "George Tsirtsis" <tsirtsis@googlemail.com>
X-OriginalArrivalTime: 08 Apr 2008 16:28:49.0351 (UTC)
	FILETIME=[9FFEC570:01C89995]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7420; t=1207672129;
	x=1208536129; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kleung@cisco.com;
	z=From:=20=22Kent=20Leung=20(kleung)=22=20<kleung@cisco.com>
	|Subject:=20RE=3A=20[Mip4]=20RFC=203344=20-=20Home=20Agent=
	20Registration=20Code=20132=20-=20foreignagent=20failed=20au
	thentication |Sender:=20;
	bh=LztSBazzxSbwapwZ2mEG2iX/wetmM/olBDhCpkd1bhA=;
	b=Eek9nJlVVc514wY4VgiBNtGwSYn/HDqSSUdx0V8V5zw+y4rovRct2qT+ZD
	Hu49H5N0xdQ+mo8eweuXhEivKel0jO0YOX6fXyFO/n8E+Olw8KehFVoysx1e
	CtiDTy+6Oh;
Authentication-Results: sj-dkim-2; header.From=kleung@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>, Acee Lindem <acee@redback.com>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
	foreignagent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

For #2, how does FA objectively decide if it should forward the reply to
the MN or not?  MN would like to know if its request was received or not
by the HA.  If a misconfigured-SA MN doesn't hear reply, it will send
more registration which would look more like a DoS attack.  But if it
received an error code that it failed authentication, then it could stop
and indicate to the user to call support or something.  

It seems to me that the issue you are trying to address could be an
alternative signaling from the HA to the FA when HA detects a DoS attack
(i.e. some registration/sec threshold from particular user reached).
Then the FA is explicitly made aware and can do something about it such
as shut down the L2 link.

I think embedding this DoS attack support in the normal registration
signaling may not be the ideal approach.  Not sure if my idea is any
better.  But I think 4433bis need not change to deal with the scenario.

Kent

-----Original Message-----
From: George Tsirtsis [mailto:tsirtsis@googlemail.com] 
Sent: Tuesday, April 08, 2008 1:55 AM
To: Kent Leung (kleung)
Cc: Henrik Levkowetz; Mobile IPv4 Mailing List; Acee Lindem
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
foreignagent failed authentication

Hi Kent et.al.,

What I am saying is two things:

1) in general sending a reply when authentication fails is bad practice
and should not be recommended by IETF RFCs. So the "SHOULD"
language is too strong. IMO it should either become SHOULD NOT, or at
MAY with a warning of the possible attack.

2) In the special case where,
    a) the HA knows for a fact that a valid FA exists (i.e., an FA-HA AE
checks out), and
    b) if the MN-HA AE fails,
it makes sense for the HA to notify the FA of that fact (presumably
using 131 code). In that case I think the RFC should say that the FA
again SHOULD NOT forward the response to the MN, or at worse MAY forward
it with a warning of the possible attack.

I think both of the above are correct but I will understand if people do
not want to both with (2), in which case we can just do (1).

I hope the above is clear but see some more below...

On Mon, Apr 7, 2008 at 7:18 PM, Kent Leung (kleung) <kleung@cisco.com>
wrote:
> Hi George.  I'm not clear by "sending a message to the FA when MN-HA  
> auth fails"?  Is this the RRP with error code 131?  If so, does the FA

> forward the RRP to the MN?
>

GT> No I think the FA should not forward it as I say in (1) above.

>  Or the intention is to only notify the FA and not the MN to avoid DoS

> attack?
>

GT> Yes, exactly. The problem is of course that existing FA
implementations maybe forwarding this message by default but I think
that is fine.

>  What happens if the MN is appending the FA-HA auth ext?
>

GT> Then the FA-HA AE will fail and will not meet the special case
condition (2a) above so no response should be sent by the HA.

>  Today, FA already receive error code 131 when MN-HA auth failed if 
> the  HA is sending the RRP.  I'm not sure what's new here.
>

GT> Maybe now it is clearer?

>
>  Kent
>
>  -----Original Message-----
>  From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf 
> Of
>
> George Tsirtsis
>  Sent: Monday, April 07, 2008 2:42 AM
>  To: Henrik Levkowetz
>
> Cc: Mobile IPv4 Mailing List; Acee Lindem
>  Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 -  
> foreignagent failed authentication
>
>
>
> Hi all,
>
>   I have the following comments you may want to consider:
>
>  1) The SHOULD language is very strong. SHOULD in an RFC means that 
> the  IETF thinks that the procedure should be followed by all 
> implementations  unless the implementor has a very good reason not to 
> do so. In other  words, and in this case, the RFC says that the IETF 
> thinks HAs should  send these 131(MN auth failed)/132(FA auth failed) 
> codes, although not  sending them does not break interoperability.
>
>  The recent discussion indicates that we are not so sure that this is 
> the  correct course of "default" action. On the contrary one should 
> think  carefuly if there is a potential DoS attack in a given  
> implementation/deployment and then decide whether such messages should

> be sent. If that is what we think then the correct language in that 
> "the  HA SHOULD NOT send RREP messages" in this case.
>
>  2) If MN-HA auth fails notify the FA! What I think would make most 
> sense  is something like the following::
>
>  -  if MN-FA auth fails:
>   "the HA MUST discard the message and SHOULD NOT send any response."
>
>  - If the MN-FA auth fails, however:
>   "the HA MUST discard the message and MAY send a response (with code
>  131) to the FA if one exists, otherwise the HA SHOULD NOT send any  
> response"
>
>  I think sending a message to the FA when the MN-HA auth fails makes  
> sense don't you?
>
>  Again I am not sure if RFC3344bis can acommodate such change, since 
> this  would require FAs to understand code 131, which may not do
currently.
>  Still I do not think this would really break any implementation, Most

> likely an FA would just log the error, not knowing what to do next  
> beyond understanding this as a rejection.
>
>  Thoughts?
>  George
>
>
>  2008/4/5 Henrik Levkowetz <henrik@levkowetz.com>:
>  > Hi Acee,
>  >
>  >  Your post sums it up pretty much, but let me add this:  In some  >

> situations and deployments, mainly when you're setting up a new  > 
> deployment environment, you actually want to generate the replies  for
>
>  > debugging and informative purposes, while mostly you want to  turn

> > them off to avoid DoS attacks.  At least one HA implementation  I 
> know
>
>  > has the behaviour configurable, for that reason.  And as  the RFC 
> 3344
>
>  > and 3344bis text seems to match this usage reasonably  well, I 
> don't  > think we want to change it?
>  >
>  >
>  >         Henrik
>  >
>  >  On 2008-04-04 21:01 Acee Lindem said the following:
>  >
>  >
>  >
>  > > Any opinions?
>  > > Thanks,
>  > > Acee
>  > > On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:
>  > >
>  > >
>  > > > With respect to our MIP4 HA implementation, we've had several  
> > discussions as to whether a registration reply should be generated  
> > when the registration request fails FA-HA authentication. The  > 
> existence of the 132 reply code would imply that one should always  > 
> respond. However, this is contrary to way authentication works in  > 
> most protocols (at least routing  > protocols) and would seem to leave

> the HA more susceptible to DoS  attacks.
>  > I checked the RFC 3344 BIS  draft and there has been no change in 
> this  area.
>  > > > Thanks,
>  > > > Acee
>  > > >
>  > >
>  > >
>  >
>  >
>  > --
>  >  Mip4 mailing list: Mip4@ietf.org
>  >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>  >      Charter page:
http://www.ietf.org/html.charters/mip4-charter.html
>  >  Supplemental site: http://www.mip4.org/  >  >
>  --
>  Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>  Supplemental site: http://www.mip4.org/
>
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Tue Apr  8 11:57:42 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 595E628C3F8;
	Tue,  8 Apr 2008 11:57:42 -0700 (PDT)
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 C32BB28C3EE
	for <mip4@core3.amsl.com>; Tue,  8 Apr 2008 11:57:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.45
X-Spam-Level: 
X-Spam-Status: No, score=-6.45 tagged_above=-999 required=5 tests=[AWL=0.149, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KS3lypZnH7Wx for <mip4@core3.amsl.com>;
	Tue,  8 Apr 2008 11:57:40 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id 4961D28C3EB
	for <mip4@ietf.org>; Tue,  8 Apr 2008 11:57:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.25,625,1199692800"; d="scan'208";a="20536071"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-5.cisco.com with ESMTP; 08 Apr 2008 11:57:56 -0700
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 m38IvuR7020748; 
	Tue, 8 Apr 2008 11:57:56 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m38IvuxW017030;
	Tue, 8 Apr 2008 18:57:56 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 8 Apr 2008 11:57:56 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 8 Apr 2008 11:57:55 -0700
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5205D177E9@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD130272ABC0@de01exm67.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] draft-mccann-mip4-mbb-00.txt
Thread-Index: AciWeb7Xj1Zc8hGYTzukWio37cmMpQDJ8wlg
From: "Kent Leung (kleung)" <kleung@cisco.com>
To: "McCann Peter-A001034" <pete.mccann@motorola.com>, <mip4@ietf.org>
X-OriginalArrivalTime: 08 Apr 2008 18:57:56.0722 (UTC)
	FILETIME=[750B3D20:01C899AA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2797; t=1207681076;
	x=1208545076; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kleung@cisco.com;
	z=From:=20=22Kent=20Leung=20(kleung)=22=20<kleung@cisco.com>
	|Subject:=20RE=3A=20[Mip4]=20draft-mccann-mip4-mbb-00.txt
	|Sender:=20; bh=uQ1GL7iUHkrKkKqSg2QS10mPWmqTRcAkI3ax6gfO8DE=;
	b=PLxAhgLjbQjB4/7h+JPA2IOLM3N9I4BuqWYcsJzzpRHuAhrTcXe7eXl41Y
	K4hWYO5EYjWj9gvKobYTmSeqMZTUK1Lr9/VoIAZ8eOAwwtKxbxii4fc2H/yE
	3mQKHzpGLR;
Authentication-Results: sj-dkim-3; header.From=kleung@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Subject: Re: [Mip4] draft-mccann-mip4-mbb-00.txt
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi Pete.  The draft seems to only point out that the security
association can be fetched during the pre-registration exchange using
RFC 3957.  But this RFC is not in use, AFAIK.  It's not clear to me if
that the draft clearly identify other benefits besides the early SA
establishment.  In the PMIP case, it's unlikely that the PMIP client/PMA
would have the MN-AAA key which is needed to derive the other keys in
RFC 3957.

The use of the 'S' bit (and zero lifetime and new CoA) for this purpose
seems kludgy in the protocol.  It may be better to have explicit
Pre-registration Extension to indicate that the message is intended to
perform operations on the entities before actual handoff signaled by
registration request/reply exchange.

So maybe the draft has some promise.  But it would be much better if the
applicability is better articulated.  I'm willing to help out if that is
desired.

Kent 

-----Original Message-----
From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of
McCann Peter-A001034
Sent: Friday, April 04, 2008 10:32 AM
To: mip4@ietf.org
Subject: [Mip4] draft-mccann-mip4-mbb-00.txt

<<Chair hat off>>

I've just uploaded a short draft that contains some suggestions on HA
implementation details to assist in make-before-break handoffs.  I hope
people can read and comment:

   A make-before-break handoff is one where resources on a target system
   are allocated prior to releasing the resources on a source system.
   Make-before-break can be an effective means to provide a more
   seamless handoff with fewer dropped packets.  The existing Mobile
   IPv4 specification supports simultaneous bindings, which can
   facilitate a make-before-break handoff.  However, the binding state
   at the home agent is only one example of a resource that can be
   allocated; others include the link connection to the Foreign Agent
   (or access router) and the provision of security associations between
   the mobile node and the mobility agents.  It may be desirable to set
   up these resources on the target system without necessarily creating
   a binding entry on the Home Agent.  This document provides some
   additional conventions on the use of simultaneous bindings in a make-
   before-break handoff that can be used to optimize the allocation of
   resources in these scenarios.

These suggestions might be appropriate for inclusion in rfc3344bis, if
there is still time to make them, or it could be published as a separate
document.

Please, let me know what you think!

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


From mip4-bounces@ietf.org  Wed Apr  9 05:49:09 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A47E928C471;
	Wed,  9 Apr 2008 05:49:09 -0700 (PDT)
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 B421C28C472
	for <mip4@core3.amsl.com>; Wed,  9 Apr 2008 05:49:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.925
X-Spam-Level: 
X-Spam-Status: No, score=-0.925 tagged_above=-999 required=5 tests=[AWL=1.052, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 bHGWLY87Bar3 for <mip4@core3.amsl.com>;
	Wed,  9 Apr 2008 05:49:04 -0700 (PDT)
Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.191])
	by core3.amsl.com (Postfix) with ESMTP id 2FFAD28C47B
	for <mip4@ietf.org>; Wed,  9 Apr 2008 05:49:02 -0700 (PDT)
Received: by rn-out-0910.google.com with SMTP id a46so2789627rne.9
	for <mip4@ietf.org>; Wed, 09 Apr 2008 05:49:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=USGOXQmJQWesm4slaXOR/EqGKppfWsskN90oH7ByJ8Q=;
	b=avNqfYjqY9tNxEv4KrN5excVq6hzR3uGlXBbg6gMwuafEPnRFreJd8CoDcV/YbYR1g4RUoFrlSscMU1Dq+FDL37bqwbGofJi3nIdUCCQ2ux/W6jdCJlvH7YFap6w3828mxoRPrggL0xwC4K+uU/v51Vbu3c1E5sn5m68cyYQKfo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=cFEyE94ydNSHAwbxMyhIlqQtW/s6Kr186fd7O4RBAZMO5Wu9f9aiPHkMlzTUext55ixI5a/bVOgegcatbMycRHBHwQJ2rvwyTg0XKVl605ZA0syE7W1vmt0SPysuV/a/RaGvr7MhDyD4SXgG5lELTcNohE7xQHj/m2gBh4628TM=
Received: by 10.142.191.2 with SMTP id o2mr24291wff.101.1207745360148;
	Wed, 09 Apr 2008 05:49:20 -0700 (PDT)
Received: by 10.142.224.10 with HTTP; Wed, 9 Apr 2008 05:49:20 -0700 (PDT)
Message-ID: <d3886a520804090549n76a55f82ud640c6d14f722ac7@mail.gmail.com>
Date: Wed, 9 Apr 2008 13:49:20 +0100
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Kent Leung (kleung)" <kleung@cisco.com>
In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC5205D176BD@xmb-sjc-235.amer.cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <610F564D-AB4E-43B0-81C1-9E8974B35A5B@redback.com>
	<2979E38DD6FC6544B789C8DAD7BAFC5205D176BD@xmb-sjc-235.amer.cisco.com>
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>, Acee Lindem <acee@redback.com>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132
	-foreignagent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

OK, so from the various comments I get that my proposal (2) maybe
pushing things too far so I am not going to insist.

Kent, could you clarify why you do not want to soften the SHOULD
language, to at least a MAY + a warning?
It seems to me that such a change is not going to break any existing
implementations; instead it will allow any new implementations to make
more informed decision on this. Note that both SHOULD and MAY are
compatible with implementations that either send or don't send the
131/132 codes. Only if we change this to MUST/MUST NOT we would break
something, so this is only a matter of emphasis and recommendation.

Regards
George

On Tue, Apr 8, 2008 at 5:18 PM, Kent Leung (kleung) <kleung@cisco.com> wrote:
> I have slight adversion to the language change.  Not because I disagree
>  with George's reasoning.  But on the fact that deployments and
>  implementations already have default behavior based on existing RFC.  So
>  not clear what is accomplished from the practical perspective.  Whatever
>  the default behavior is in the implementation, there will need to be a
>  knob for the alternative behavior.  So in essence, both needs to be
>  supported. The language change would only stir up unnecessary bickering
>  among vendors on whose default behavior is more right.
>
>  BTW, experience has shown that sending reply with error code 132 has
>  been advantageous.  The FA-HA authentication failure discovered
>  misconfiguration.  Have not seen any cases of DoS attack from FAs.  So I
>  prefer to leave the SHOULD as is.
>
>
>  Kent
>
>  -----Original Message-----
>  From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of
>  Acee Lindem
>
>
> Sent: Monday, April 07, 2008 6:27 PM
>  To: Kent Leung (kleung)
>  Cc: Mobile IPv4 Mailing List
>  Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132
>  -foreignagent failed authentication
>
>
>  On Apr 7, 2008, at 2:10 PM, Kent Leung (kleung) wrote:
>
>  > Isn't there a significantly higher chance of DoS attacks from MNs
>  > (i.e.
>  > invalid MN-HA Auth Ext) than from FAs (i.e. invalid FA-HA Auth Ext)?
>
>  Yes. This seems like a more likely attack.
>
>  > When FA-HA authentication fails, it's usually due to misconfiguration.
>  > Of course, a rogue MN can append FA-HA Auth Ext in the request.
>  >
>  > I've always preferred not to send reply when authentication failed by
>  > only logging the event.  But then always runs into cases when the
>  > reply was required.  So I think it's up to implementation to decide
>  > the sending of the RRP or not when authentication fails.  Not sure if
>  > changing the RFC is necessary.
>
>  Would you be opposed to changing the "SHOULD" to a "MAY" as proposed by
>  George?
>
>  Thanks,
>  Acee
>
>
>  >
>  > Kent
>  >
>  > -----Original Message-----
>  > From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf
>  > Of Acee Lindem
>  > Sent: Friday, April 04, 2008 12:02 PM
>  > Cc: Mobile IPv4 Mailing List
>  > Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 -
>  > foreignagent failed authentication
>  >
>  > Any opinions?
>  > Thanks,
>  > Acee
>  > On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:
>  >
>  >> With respect to our MIP4 HA implementation, we've had several
>  >> discussions as to whether a registration reply should be generated
>  >> when the registration request fails FA-HA authentication. The
>  >> existence of the 132 reply code would imply that one should always
>  >> respond. However, this is contrary to way authentication works in
>  >> most
>  >
>  >> protocols (at least routing protocols) and would seem to leave the HA
>
>  >> more susceptible to DoS attacks. I checked the RFC 3344 BIS draft and
>
>  >> there has been no change in this area.
>  >> Thanks,
>  >> Acee
>  >
>  > --
>  > Mip4 mailing list: Mip4@ietf.org
>  >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>  >      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>  > Supplemental site: http://www.mip4.org/
>  > --
>  > Mip4 mailing list: Mip4@ietf.org
>  >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>  >      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>  > Supplemental site: http://www.mip4.org/
>
>  --
>  Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>  Supplemental site: http://www.mip4.org/
>  --
>
>
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>  Supplemental site: http://www.mip4.org/
>
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Wed Apr  9 07:52:36 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8DF863A6C64;
	Wed,  9 Apr 2008 07:52:36 -0700 (PDT)
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 BD6973A6AA0
	for <mip4@core3.amsl.com>; Wed,  9 Apr 2008 07:52:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.833
X-Spam-Level: 
X-Spam-Status: No, score=-1.833 tagged_above=-999 required=5 tests=[AWL=0.431, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334]
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 D6O2jYQgMsFP for <mip4@core3.amsl.com>;
	Wed,  9 Apr 2008 07:52:31 -0700 (PDT)
Received: from web84314.mail.re1.yahoo.com (web84314.mail.re1.yahoo.com
	[69.147.74.193]) by core3.amsl.com (Postfix) with SMTP id 191F33A6D7A
	for <mip4@ietf.org>; Wed,  9 Apr 2008 07:52:30 -0700 (PDT)
Received: (qmail 53728 invoked by uid 60001); 9 Apr 2008 14:52:48 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID;
	b=bktxrZmKzT3931hlxxZkkooFRVyRjekVtiHXZ4OxNmKSr5mmia8NSJJFCdmY9G9hVWQFlJ1zOSSi44mF9iT8ux2AeLzWVaCaq+bPdV/sjORBhXz2UjvGio/EnTRoji9DA0kanGnRkdeFG1U9hfb5KuWd+PUav4G1z+Yl6MC8Lzk=;
X-YMail-OSG: wmU4E04VM1miTzCOduCgAoiuZWgQXAXdp36gdiiz3xQkklc2z3UMwrddf5tPondS1qOE6MxgTh3SgSWHmnoHrFU6aZOAYWrT0yNcNW2ieJ92lBJO8L0-
Received: from [206.16.17.212] by web84314.mail.re1.yahoo.com via HTTP;
	Wed, 09 Apr 2008 07:52:47 PDT
X-Mailer: YahooMailRC/902.40 YahooMailWebService/0.7.162
Date: Wed, 9 Apr 2008 07:52:47 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: McCann Peter-A001034 <pete.mccann@motorola.com>
MIME-Version: 1.0
Message-ID: <125622.53463.qm@web84314.mail.re1.yahoo.com>
Cc: mip4@ietf.org
Subject: [Mip4] WGLC: draft-ietf-mip4-generic-notification-message-04.txt
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
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="===============0565860815=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

--===============0565860815==
Content-Type: multipart/alternative; boundary="0-2052008368-1207752767=:53463"

--0-2052008368-1207752767=:53463
Content-Type: text/plain; charset=us-ascii

I support the advancement of this document to the IESG with a
     request for publication as a Proposed Standard RFC.


Regards,

Behcet
----- Original Message ----
From: McCann Peter-A001034 <pete.mccann@motorola.com>
To: mip4@ietf.org
Cc: henrik@levkowetz.com
Sent: Friday, April 4, 2008 12:16:30 PM
Subject: [Mip4] WGLC: draft-ietf-mip4-generic-notification-message-04.txt

This message announces a 2-week working group last call on:

"Generic Notification Message for Mobile IPv4"          
draft-ietf-mip4-generic-notification-message-04.txt

The last call will end at 24:00 UTC on Friday, April 18 2008.

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


Please respond to this working group last call:

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

    "I support the advancement of this document to the IESG with a
     request for publication as a Proposed Standard RFC."

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


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

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

Please direct all replies to the Mobile IPv4 mailing list,
mip4@ietf.org.


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




--0-2052008368-1207752767=:53463
Content-Type: text/html; charset=us-ascii

<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:14pt"><div style="font-family: times new roman,new york,times,serif; font-size: 14pt;">I 
support 
the 
advancement 
of 
this 
document 
to 
the 
IESG 
with 
a<br>&nbsp; 
&nbsp; 
 
request 
for 
publication 
as 
a 
Proposed 
Standard 
RFC.<br><br><br>Regards,<br><br>Behcet<br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: McCann Peter-A001034 &lt;pete.mccann@motorola.com&gt;<br>To: mip4@ietf.org<br>Cc: henrik@levkowetz.com<br>Sent: Friday, April 4, 2008 12:16:30 PM<br>Subject: [Mip4] WGLC: draft-ietf-mip4-generic-notification-message-04.txt<br><br>
This 
message 
announces 
a 
2-week 
working 
group 
last 
call 
on:<br><br>"Generic 
Notification 
Message 
for 
Mobile 
IPv4"&nbsp; 
&nbsp; 
&nbsp; 
&nbsp; 
&nbsp; <br>draft-ietf-mip4-generic-notification-message-04.txt<br><br>The 
last 
call 
will 
end 
at 
24:00 
UTC 
on 
Friday, 
April 
18 
2008.<br><br>This 
document 
specifies 
protocol 
enhancements 
that 
allow 
Mobile 
IPv4<br>entities 
to 
send 
and 
receive 
explicit 
notification 
messages 
using 
a<br>new 
Mobile 
IPv4 
message 
type 
designed 
for 
this 
purpose.<br><br>A 
URL 
for 
this 
Internet-Draft 
is:<br><a href="http://www.ietf.org/internet-drafts/draft-ietf-mip4-generic-notification" target="_blank">http://www.ietf.org/internet-drafts/draft-ietf-mip4-generic-notification</a><br>-message-04.txt<br><br><br>Please 
respond 
to 
this 
working 
group 
last 
call:<br><br>* 
If 
you 
have 
no 
comments 
on 
the 
draft, 
and 
support 
its 
advancement,<br>&nbsp; 
simply 
respond 
with 
a 
line 
containing 
something 
like<br><br>&nbsp; 
&nbsp; 
"I 
support 
the 
advancement 
of 
this 
document 
to 
the 
IESG 
with 
a<br>&nbsp; 
&nbsp; 
 
request 
for 
publication 
as 
a 
Proposed 
Standard 
RFC."<br><br>&nbsp; 
 
If 
you 
have 
comments, 
please 
use 
a 
line 
similar 
to 
the 
one 
above,<br>&nbsp; 
 
and 
supplement 
this 
with 
your 
comments.<br><br><br>* 
If 
you 
*don't* 
support 
its 
advancement, 
respond 
with 
a 
line<br>&nbsp; 
containing 
something 
like 
the 
following, 
supplemented 
by 
your<br>&nbsp; 
comments 
-<br><br>&nbsp; 
&nbsp; 
"I 
don't 
support 
the 
advancement 
of 
this 
document 
to 
the 
IESG 
with<br>&nbsp; 
&nbsp; 
 
a 
request 
for 
publication 
as 
a 
Proposed 
Standard 
RFC, 
for 
the<br>&nbsp; 
&nbsp; 
 
following 
reasons:"<br>&nbsp; 
&nbsp; 
...<br><br>Please 
direct 
all 
replies 
to 
the 
Mobile 
IPv4 
mailing 
list,<br><a ymailto="mailto:mip4@ietf.org" href="mailto:mip4@ietf.org">mip4@ietf.org</a>.<br><br><br>-Pete<br>-- <br>Mip4 
mailing 
list: 
<a ymailto="mailto:Mip4@ietf.org" href="mailto:Mip4@ietf.org">Mip4@ietf.org</a><br>&nbsp; 
&nbsp; 
Web 
interface: 
<a href="https://www.ietf.org/mailman/listinfo/mip4" target="_blank">https://www.ietf.org/mailman/listinfo/mip4</a><br>&nbsp; 
&nbsp; 
 
Charter 
page: 
<a href="http://www.ietf.org/html.charters/mip4-charter.html" target="_blank">http://www.ietf.org/html.charters/mip4-charter.html</a><br>Supplemental 
site: 
<a href="http://www.mip4.org/" target="_blank">http://www.mip4.org/</a><br></div><br></div></div></body></html>
--0-2052008368-1207752767=:53463--

--===============0565860815==
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/

--===============0565860815==--


From mip4-bounces@ietf.org  Wed Apr  9 08:02:17 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B7C4028C14E;
	Wed,  9 Apr 2008 08:02:17 -0700 (PDT)
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 E370A28C0E7
	for <mip4@core3.amsl.com>; Wed,  9 Apr 2008 08:02:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 65l1E6a6XEL9 for <mip4@core3.amsl.com>;
	Wed,  9 Apr 2008 08:02:15 -0700 (PDT)
Received: from zrtps0kn.nortel.com (zrtps0kn.nortel.com [47.140.192.55])
	by core3.amsl.com (Postfix) with ESMTP id 121BC3A68FE
	for <mip4@ietf.org>; Wed,  9 Apr 2008 08:02:14 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m39F26b12781; Wed, 9 Apr 2008 15:02:06 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 9 Apr 2008 10:02:05 -0500
Message-ID: <C5A96676FCD00745B64AE42D5FCC9B6E179628BA@zrc2hxm0.corp.nortel.com>
In-Reply-To: <d3886a520804090549n76a55f82ud640c6d14f722ac7@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] RFC 3344 - Home Agent Registration Code 132 -foreignagent
	failed authentication
Thread-Index: AciaQCqWkpjIrzORTy6c2KvI21GBKAABvifg
References: <610F564D-AB4E-43B0-81C1-9E8974B35A5B@redback.com>
	<2979E38DD6FC6544B789C8DAD7BAFC5205D176BD@xmb-sjc-235.amer.cisco.com>
	<d3886a520804090549n76a55f82ud640c6d14f722ac7@mail.gmail.com>
From: "Ahmad Muhanna" <amuhanna@nortel.com>
To: "George Tsirtsis" <tsirtsis@googlemail.com>,
	"Kent Leung (kleung)" <kleung@cisco.com>
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>, Acee Lindem <acee@redback.com>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132
	-foreignagent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi George,
Please allow me to jump in and comment on this.

Regards,
Ahmad 

> 
> Kent, could you clarify why you do not want to soften the 
> SHOULD language, to at least a MAY + a warning?
> It seems to me that such a change is not going to break any 
> existing implementations; 
> instead it will allow any new 
> implementations to make more informed decision on this. 

[Ahmad]
Could you please explain how the change from "SHOULD" to "MAY" will make
the new implementation to make a "more informed" decision?

> Note 
> that both SHOULD and MAY are compatible with implementations 
> that either send or don't send the
> 131/132 codes. 

[Ahmad]
Okay. You seem to say that there are already existing implementation
that send 131/132 and there are some that do not. Ok. then what is the
problem?

Are we trying to find a way out for those existing implementations which
decided NOT to send these error codes probably because they believe that
they are trying to avoid replying to "what is called DoS attack"?

My apologies for referring to it as "What is called DoS attack" because
until now, I do not understand the characteristics of such DoS attack?
If we understand it, then we probably will be able to make a more
informed decision.

> Only if we change this to MUST/MUST NOT we 
> would break something, so this is only a matter of emphasis 
> and recommendation.
> 
> Regards
> George
> 
> On Tue, Apr 8, 2008 at 5:18 PM, Kent Leung (kleung) 
> <kleung@cisco.com> wrote:
> > I have slight adversion to the language change.  Not because I 
> > disagree  with George's reasoning.  But on the fact that 
> deployments 
> > and  implementations already have default behavior based on 
> existing 
> > RFC.  So  not clear what is accomplished from the practical 
> > perspective.  Whatever  the default behavior is in the 
> implementation, 
> > there will need to be a  knob for the alternative behavior.  So in 
> > essence, both needs to be  supported. The language change 
> would only 
> > stir up unnecessary bickering  among vendors on whose 
> default behavior is more right.
> >
> >  BTW, experience has shown that sending reply with error 
> code 132 has  
> > been advantageous.  The FA-HA authentication failure discovered  
> > misconfiguration.  Have not seen any cases of DoS attack 
> from FAs.  So 
> > I  prefer to leave the SHOULD as is.
> >
> >
> >  Kent
> >
> >  -----Original Message-----
> >  From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] 
> On Behalf 
> > Of  Acee Lindem
> >
> >
> > Sent: Monday, April 07, 2008 6:27 PM
> >  To: Kent Leung (kleung)
> >  Cc: Mobile IPv4 Mailing List
> >  Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132  
> > -foreignagent failed authentication
> >
> >
> >  On Apr 7, 2008, at 2:10 PM, Kent Leung (kleung) wrote:
> >
> >  > Isn't there a significantly higher chance of DoS attacks 
> from MNs  
> > > (i.e.
> >  > invalid MN-HA Auth Ext) than from FAs (i.e. invalid 
> FA-HA Auth Ext)?
> >
> >  Yes. This seems like a more likely attack.
> >
> >  > When FA-HA authentication fails, it's usually due to 
> misconfiguration.
> >  > Of course, a rogue MN can append FA-HA Auth Ext in the request.
> >  >
> >  > I've always preferred not to send reply when 
> authentication failed 
> > by  > only logging the event.  But then always runs into cases when 
> > the  > reply was required.  So I think it's up to implementation to 
> > decide  > the sending of the RRP or not when authentication fails.  
> > Not sure if  > changing the RFC is necessary.
> >
> >  Would you be opposed to changing the "SHOULD" to a "MAY" 
> as proposed 
> > by  George?
> >
> >  Thanks,
> >  Acee
> >
> >
> >  >
> >  > Kent
> >  >
> >  > -----Original Message-----
> >  > From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On 
> > Behalf  > Of Acee Lindem  > Sent: Friday, April 04, 2008 
> 12:02 PM  > 
> > Cc: Mobile IPv4 Mailing List  > Subject: Re: [Mip4] RFC 3344 - Home 
> > Agent Registration Code 132 -  > foreignagent failed 
> authentication  >  
> > > Any opinions?
> >  > Thanks,
> >  > Acee
> >  > On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:
> >  >
> >  >> With respect to our MIP4 HA implementation, we've had 
> several  >> 
> > discussions as to whether a registration reply should be 
> generated  >> 
> > when the registration request fails FA-HA authentication. The  >> 
> > existence of the 132 reply code would imply that one should 
> always  >> 
> > respond. However, this is contrary to way authentication 
> works in  >> 
> > most  >  >> protocols (at least routing protocols) and 
> would seem to 
> > leave the HA
> >
> >  >> more susceptible to DoS attacks. I checked the RFC 3344 
> BIS draft 
> > and
> >
> >  >> there has been no change in this area.
> >  >> Thanks,
> >  >> Acee
> >  >
> >  > --
> >  > Mip4 mailing list: Mip4@ietf.org
> >  >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
> >  >      Charter page: 
> http://www.ietf.org/html.charters/mip4-charter.html
> >  > Supplemental site: http://www.mip4.org/  > --  > Mip4 
> mailing list: 
> > Mip4@ietf.org
> >  >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
> >  >      Charter page: 
> http://www.ietf.org/html.charters/mip4-charter.html
> >  > Supplemental site: http://www.mip4.org/
> >
> >  --
> >  Mip4 mailing list: Mip4@ietf.org
> >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
> >      Charter page: 
> http://www.ietf.org/html.charters/mip4-charter.html
> >  Supplemental site: http://www.mip4.org/
> >  --
> >
> >
> > Mip4 mailing list: Mip4@ietf.org
> >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
> >      Charter page: 
> http://www.ietf.org/html.charters/mip4-charter.html
> >  Supplemental site: http://www.mip4.org/
> >
> --
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
> 
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Wed Apr  9 08:06:36 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 03E1D3A68FE;
	Wed,  9 Apr 2008 08:06:36 -0700 (PDT)
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 785833A6C07
	for <mip4@core3.amsl.com>; Wed,  9 Apr 2008 08:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6-rCalNH9gEx for <mip4@core3.amsl.com>;
	Wed,  9 Apr 2008 08:06:27 -0700 (PDT)
Received: from mail153.messagelabs.com (mail153.messagelabs.com
	[216.82.253.51]) by core3.amsl.com (Postfix) with SMTP id B59BD3A6A17
	for <mip4@ietf.org>; Wed,  9 Apr 2008 08:06:27 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: pete.mccann@motorola.com
X-Msg-Ref: server-15.tower-153.messagelabs.com!1207753605!6065610!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 2648 invoked from network); 9 Apr 2008 15:06:45 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-15.tower-153.messagelabs.com with SMTP;
	9 Apr 2008 15:06:45 -0000
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id m39F6jGo007948
	for <mip4@ietf.org>; Wed, 9 Apr 2008 08:06:45 -0700 (MST)
Received: from il06vts04.mot.com (il06vts04.mot.com [129.188.137.144])
	by il06exr01.mot.com (8.13.5/Vontu) with SMTP id m39F6iwL012644
	for <mip4@ietf.org>; Wed, 9 Apr 2008 10:06:44 -0500 (CDT)
Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18])
	by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id m39F6h2h012632
	for <mip4@ietf.org>; Wed, 9 Apr 2008 10:06:43 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 9 Apr 2008 11:06:42 -0400
Message-ID: <BE4B07D4197BF34EB3B753DD34EBCD130276B6E5@de01exm67.ds.mot.com>
In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC5205D177E9@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] draft-mccann-mip4-mbb-00.txt
thread-index: AciWeb7Xj1Zc8hGYTzukWio37cmMpQDJ8wlgACw1C0A=
References: <BE4B07D4197BF34EB3B753DD34EBCD130272ABC0@de01exm67.ds.mot.com>
	<2979E38DD6FC6544B789C8DAD7BAFC5205D177E9@xmb-sjc-235.amer.cisco.com>
From: "McCann Peter-A001034" <pete.mccann@motorola.com>
To: "Kent Leung (kleung)" <kleung@cisco.com>, <mip4@ietf.org>
X-CFilter-Loop: Reflected
Subject: Re: [Mip4] draft-mccann-mip4-mbb-00.txt
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi, Kent,

Thanks for reading the document.  See below...

Kent Leung (kleung) wrote:
> Hi Pete.  The draft seems to only point out that the security
> association can be fetched during the pre-registration exchange using
> RFC 3957.  But this RFC is not in use, AFAIK.  It's not clear to me
> if that the draft clearly identify other benefits besides the early
> SA establishment.  In the PMIP case, it's unlikely that the PMIP
> client/PMA would have the MN-AAA key which is needed to derive the
> other keys in RFC 3957.      

We originally started the draft to solve a problem when handing off
from PMIPv4 to CMIPv4; the idea is to complete authentication on
the CMIPv4 side without actually setting up the tunnel for the bearer
traffic, but to do that at a later time.  There are deployments 
that use MN-AAA, and personally, I think these deployments should
also be using RFC 3957 because it solves the problem of distributing
complete security associations, whereas other solutions just distribute
keys.  In any case, it doesn't really matter whether or not the
deployment uses 3957 as long as it has authentication (MN-AAA and
FA Challenge/Response) which most CMIP deployments do.

> The use of the 'S' bit (and zero lifetime and new CoA) for this
> purpose seems kludgy in the protocol.  It may be better to have
> explicit Pre-registration Extension to indicate that the message is
> intended to perform operations on the entities before actual handoff
> signaled by registration request/reply exchange.    

We decided to use the 'S' bit because it seems logical that the
node is trying to create another registration without tearing down
the old one, albeit one which doesn't tunnel traffic hence the zero
lifetime.  However, I'm open to other ways of solving the problem 
and perhaps a new extension would work; however, we really wanted to
introduce just the minimum amount of new specification and the current
approach could even be considered an implementation option in an
existing
HA.

> So maybe the draft has some promise.  But it would be much better if
> the applicability is better articulated.  I'm willing to help out if
> that is desired.  

Thanks for that - maybe this note can clear up some of the intentions
of the draft.

-Pete

> Kent
> 
> -----Original Message-----
> From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf
> Of McCann Peter-A001034 
> Sent: Friday, April 04, 2008 10:32 AM
> To: mip4@ietf.org
> Subject: [Mip4] draft-mccann-mip4-mbb-00.txt
> 
> <<Chair hat off>>
> 
> I've just uploaded a short draft that contains some suggestions on HA
> implementation details to assist in make-before-break handoffs.  I
> hope people can read and comment:  
> 
>    A make-before-break handoff is one where resources on a target
>    system are allocated prior to releasing the resources on a source
>    system. Make-before-break can be an effective means to provide a
>    more seamless handoff with fewer dropped packets.  The existing
>    Mobile IPv4 specification supports simultaneous bindings, which can
>    facilitate a make-before-break handoff.  However, the binding state
>    at the home agent is only one example of a resource that can be
>    allocated; others include the link connection to the Foreign Agent
>    (or access router) and the provision of security associations
>    between the mobile node and the mobility agents.  It may be
>    desirable to set up these resources on the target system without
>    necessarily creating a binding entry on the Home Agent.  This
>    document provides some additional conventions on the use of
>    simultaneous bindings in a make- before-break handoff that can be
>    used to optimize the allocation of resources in these scenarios.
> 
> These suggestions might be appropriate for inclusion in rfc3344bis,
> if there is still time to make them, or it could be published as a
> separate document.  
> 
> Please, let me know what you think!
> 
> -Pete

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


From mip4-bounces@ietf.org  Thu Apr 10 01:12:59 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3517F3A6F1E;
	Thu, 10 Apr 2008 01:12:59 -0700 (PDT)
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 406773A6F12
	for <mip4@core3.amsl.com>; Thu, 10 Apr 2008 01:12:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SqAPi45EYlWq for <mip4@core3.amsl.com>;
	Thu, 10 Apr 2008 01:12:57 -0700 (PDT)
Received: from mail2.heig-vd.ch (mail2.heig-vd.ch [193.134.216.149])
	by core3.amsl.com (Postfix) with ESMTP id 3ACBD3A6F0E
	for <mip4@ietf.org>; Thu, 10 Apr 2008 01:12:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by mail2.heig-vd.ch (8.13.7/8.13.1/MailGateway 2.01) with ESMTP id
	m3A8DDMX001473 for <mip4@ietf.org>; Thu, 10 Apr 2008 10:13:13 +0200
X-Virus-Scanned: amavisd-new from YCOM SA at heig-vd.ch
Received: from mail2.heig-vd.ch ([127.0.0.1])
	by localhost (mail2.heig-vd.ch [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id NHjgEmqZyvhe for <mip4@ietf.org>;
	Thu, 10 Apr 2008 10:13:13 +0200 (CEST)
Received: from eint13.einet.ad.eivd.ch ([10.192.41.30])
	by mail2.heig-vd.ch (8.13.7/8.13.7/MailGateway 2.01) with ESMTP id
	m3A8DBZr001471 for <mip4@ietf.org>; Thu, 10 Apr 2008 10:13:12 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 10 Apr 2008 10:13:09 +0200
Message-ID: <B6147297D2C35643B07A241261CA1E30145981@eint13.einet.ad.eivd.ch>
In-Reply-To: <mailman.13074.1207753594.4932.mip4@ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] draft-doswald-robert-mip4-btn-fmipv4-00.txt
Thread-Index: AciaU2E/kX2eOSpDQEWFnxnh0DvOQAAimsgg
References: <mailman.13074.1207753594.4932.mip4@ietf.org>
From: "DOSWALD Alistair" <Alistair.Doswald@heig-vd.ch>
To: <mip4@ietf.org>
Subject: [Mip4]  draft-doswald-robert-mip4-btn-fmipv4-00.txt
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hello,

I've recently uploaded a relatively short draft concerning fast
handovers for Mobile IPv4. Its title is "Better Than Nothing Mobile IPv4
Fast Handovers" (draft-doswald-robert-mip4-btn-fmipv4-00.txt, url:
http://www.tools.ietf.org/html/draft-doswald-robert-mip4-btn-fmipv4-00).
Here's the abstract: 

Proposed fast handover solutions for Mobile IPv4 depend on the
presence of Foreign Agents (FA) in the networks between which the
Mobile Node (MN) moves to ensure their operation.  However, in many
situations the MN moves into networks without FAs.  This document
proposes a solution that includes fast handover mechanisms involving
a direct connection to the Home Agent (HA).  This solution is not a
full fledged fast handover proposal, but rather a complement to RFC
4881: Low-Latency Handovers in Mobile IPv4, and RFC 4988: Mobile IPv4
Fast Handover.

The idea is basically to have faster handovers when moving between
networks that don't have an FA, or when only one of the networks has an
FA. If you have time to read it, I'd appreciate comments, suggestions
and criticisms.

Sincerely,

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


From mip4-bounces@ietf.org  Thu Apr 10 15:32:07 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D644B28C50A;
	Thu, 10 Apr 2008 15:32:07 -0700 (PDT)
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 7A7ED28C50D
	for <mip4@core3.amsl.com>; Thu, 10 Apr 2008 15:32:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.475
X-Spam-Level: 
X-Spam-Status: No, score=-6.475 tagged_above=-999 required=5 tests=[AWL=0.124, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id HTqbWesRUub3 for <mip4@core3.amsl.com>;
	Thu, 10 Apr 2008 15:32:05 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 3DF2328C503
	for <mip4@ietf.org>; Thu, 10 Apr 2008 15:32:05 -0700 (PDT)
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-1.cisco.com with ESMTP; 10 Apr 2008 15:32:27 -0700
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 m3AMWRVQ002924; 
	Thu, 10 Apr 2008 15:32:27 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m3AMWRxq023182;
	Thu, 10 Apr 2008 22:32:27 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 10 Apr 2008 15:32:26 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 10 Apr 2008 15:32:24 -0700
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5205D87904@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <d3886a520804090549n76a55f82ud640c6d14f722ac7@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] RFC 3344 - Home Agent Registration Code 132 -foreignagent
	failed authentication
Thread-Index: AciaQCF5Ffw0qdvsTwOZc/7OYs545wBGegUw
From: "Kent Leung (kleung)" <kleung@cisco.com>
To: "George Tsirtsis" <tsirtsis@googlemail.com>
X-OriginalArrivalTime: 10 Apr 2008 22:32:26.0994 (UTC)
	FILETIME=[C1266520:01C89B5A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5549; t=1207866747;
	x=1208730747; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kleung@cisco.com;
	z=From:=20=22Kent=20Leung=20(kleung)=22=20<kleung@cisco.com>
	|Subject:=20RE=3A=20[Mip4]=20RFC=203344=20-=20Home=20Agent=
	20Registration=20Code=20132=20-foreignagent=20failed=20authe
	ntication |Sender:=20;
	bh=I/uc20S3CwXwqjj6HYwS4N5W76Mlvwjz/gsFXHCndzs=;
	b=caVopIkjvN/Jq8JfAGsoEbDrT6gPf7n5S6jgWtL7ZsYU/Yb3OB/n++H91z
	8HbO3wWl5lne0aiyEDgXnn4GdHR1RJoqg3wjqKxURSdZacx8dVcScaW71Tn/
	o0ayoofxIr;
Authentication-Results: sj-dkim-3; header.From=kleung@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>, Acee Lindem <acee@redback.com>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132
	-foreignagent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi George.  I mentioned the reasons in my previous email: default
implementation adhering to RFC language in deployment for years and
experience has shown usefulness of reply and lack of FA DoS attacks.
Keeping the language the same does not break anything or prevent
implementations from supporting both cases. :)

Kent

-----Original Message-----
From: George Tsirtsis [mailto:tsirtsis@googlemail.com] 
Sent: Wednesday, April 09, 2008 5:49 AM
To: Kent Leung (kleung)
Cc: Acee Lindem; Mobile IPv4 Mailing List
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132
-foreignagent failed authentication

OK, so from the various comments I get that my proposal (2) maybe
pushing things too far so I am not going to insist.

Kent, could you clarify why you do not want to soften the SHOULD
language, to at least a MAY + a warning?
It seems to me that such a change is not going to break any existing
implementations; instead it will allow any new implementations to make
more informed decision on this. Note that both SHOULD and MAY are
compatible with implementations that either send or don't send the
131/132 codes. Only if we change this to MUST/MUST NOT we would break
something, so this is only a matter of emphasis and recommendation.

Regards
George

On Tue, Apr 8, 2008 at 5:18 PM, Kent Leung (kleung) <kleung@cisco.com>
wrote:
> I have slight adversion to the language change.  Not because I 
> disagree  with George's reasoning.  But on the fact that deployments 
> and  implementations already have default behavior based on existing 
> RFC.  So  not clear what is accomplished from the practical 
> perspective.  Whatever  the default behavior is in the implementation,

> there will need to be a  knob for the alternative behavior.  So in 
> essence, both needs to be  supported. The language change would only 
> stir up unnecessary bickering  among vendors on whose default behavior
is more right.
>
>  BTW, experience has shown that sending reply with error code 132 has

> been advantageous.  The FA-HA authentication failure discovered  
> misconfiguration.  Have not seen any cases of DoS attack from FAs.  So

> I  prefer to leave the SHOULD as is.
>
>
>  Kent
>
>  -----Original Message-----
>  From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf 
> Of  Acee Lindem
>
>
> Sent: Monday, April 07, 2008 6:27 PM
>  To: Kent Leung (kleung)
>  Cc: Mobile IPv4 Mailing List
>  Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132  
> -foreignagent failed authentication
>
>
>  On Apr 7, 2008, at 2:10 PM, Kent Leung (kleung) wrote:
>
>  > Isn't there a significantly higher chance of DoS attacks from MNs  
> > (i.e.
>  > invalid MN-HA Auth Ext) than from FAs (i.e. invalid FA-HA Auth
Ext)?
>
>  Yes. This seems like a more likely attack.
>
>  > When FA-HA authentication fails, it's usually due to
misconfiguration.
>  > Of course, a rogue MN can append FA-HA Auth Ext in the request.
>  >
>  > I've always preferred not to send reply when authentication failed 
> by  > only logging the event.  But then always runs into cases when 
> the  > reply was required.  So I think it's up to implementation to 
> decide  > the sending of the RRP or not when authentication fails.  
> Not sure if  > changing the RFC is necessary.
>
>  Would you be opposed to changing the "SHOULD" to a "MAY" as proposed 
> by  George?
>
>  Thanks,
>  Acee
>
>
>  >
>  > Kent
>  >
>  > -----Original Message-----
>  > From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On 
> Behalf  > Of Acee Lindem  > Sent: Friday, April 04, 2008 12:02 PM  > 
> Cc: Mobile IPv4 Mailing List  > Subject: Re: [Mip4] RFC 3344 - Home 
> Agent Registration Code 132 -  > foreignagent failed authentication  >

> > Any opinions?
>  > Thanks,
>  > Acee
>  > On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:
>  >
>  >> With respect to our MIP4 HA implementation, we've had several  >> 
> discussions as to whether a registration reply should be generated  >>

> when the registration request fails FA-HA authentication. The  >> 
> existence of the 132 reply code would imply that one should always  >>

> respond. However, this is contrary to way authentication works in  >> 
> most  >  >> protocols (at least routing protocols) and would seem to 
> leave the HA
>
>  >> more susceptible to DoS attacks. I checked the RFC 3344 BIS draft 
> and
>
>  >> there has been no change in this area.
>  >> Thanks,
>  >> Acee
>  >
>  > --
>  > Mip4 mailing list: Mip4@ietf.org
>  >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>  >      Charter page:
http://www.ietf.org/html.charters/mip4-charter.html
>  > Supplemental site: http://www.mip4.org/  > --  > Mip4 mailing list:

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


From mip4-bounces@ietf.org  Thu Apr 10 15:40:28 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 17D3E3A69B3;
	Thu, 10 Apr 2008 15:40:28 -0700 (PDT)
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 2D2FE3A684F
	for <mip4@core3.amsl.com>; Thu, 10 Apr 2008 15:40:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.493
X-Spam-Level: 
X-Spam-Status: No, score=-6.493 tagged_above=-999 required=5 tests=[AWL=0.106, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9qUvvYMcYJ1K for <mip4@core3.amsl.com>;
	Thu, 10 Apr 2008 15:40:26 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id 1355D3A699C
	for <mip4@ietf.org>; Thu, 10 Apr 2008 15:40:22 -0700 (PDT)
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-2.cisco.com with ESMTP; 10 Apr 2008 15:40:44 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m3AMehbO010880; 
	Thu, 10 Apr 2008 15:40:43 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m3AMehJM028130;
	Thu, 10 Apr 2008 22:40:44 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 10 Apr 2008 15:40:43 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 10 Apr 2008 15:40:40 -0700
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5205D87911@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD130276B6E5@de01exm67.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] draft-mccann-mip4-mbb-00.txt
Thread-Index: AciWeb7Xj1Zc8hGYTzukWio37cmMpQDJ8wlgACw1C0AAQhufkA==
From: "Kent Leung (kleung)" <kleung@cisco.com>
To: "McCann Peter-A001034" <pete.mccann@motorola.com>, <mip4@ietf.org>
X-OriginalArrivalTime: 10 Apr 2008 22:40:43.0725 (UTC)
	FILETIME=[E93987D0:01C89B5B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4756; t=1207867244;
	x=1208731244; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kleung@cisco.com;
	z=From:=20=22Kent=20Leung=20(kleung)=22=20<kleung@cisco.com>
	|Subject:=20RE=3A=20[Mip4]=20draft-mccann-mip4-mbb-00.txt
	|Sender:=20; bh=fjsqvjYG5wuQG/4soi+aUfUfnzsqNniM1hAqoEZZ+LY=;
	b=JQo00LlN0mtIjkMtMUwvz+E/fdrPDQWb0PJxx7RszwZNbcj7hVztPYgKiR
	axIs/NgpuUt8pTXZzEFv/JUfUF+MxvsR5dUFBzY1vIQ2vvmAMrnYa4qJFqqW
	3WKVclnxbdPt8C+TPLse9ZaTH76PMTqGgC9tGl4ONPdKfddhxj5bY=;
Authentication-Results: sj-dkim-1; header.From=kleung@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Subject: Re: [Mip4] draft-mccann-mip4-mbb-00.txt
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

 
Comments below.

-----Original Message-----
From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com] 
Sent: Wednesday, April 09, 2008 8:07 AM
To: Kent Leung (kleung); mip4@ietf.org
Subject: RE: [Mip4] draft-mccann-mip4-mbb-00.txt

Hi, Kent,

Thanks for reading the document.  See below...

Kent Leung (kleung) wrote:
> Hi Pete.  The draft seems to only point out that the security 
> association can be fetched during the pre-registration exchange using 
> RFC 3957.  But this RFC is not in use, AFAIK.  It's not clear to me if

> that the draft clearly identify other benefits besides the early SA 
> establishment.  In the PMIP case, it's unlikely that the PMIP 
> client/PMA would have the MN-AAA key which is needed to derive the
> other keys in RFC 3957.      

We originally started the draft to solve a problem when handing off from
PMIPv4 to CMIPv4; the idea is to complete authentication on the CMIPv4
side without actually setting up the tunnel for the bearer traffic, but
to do that at a later time.  There are deployments that use MN-AAA, and
personally, I think these deployments should also be using RFC 3957
because it solves the problem of distributing complete security
associations, whereas other solutions just distribute keys.  In any
case, it doesn't really matter whether or not the deployment uses 3957
as long as it has authentication (MN-AAA and FA Challenge/Response)
which most CMIP deployments do.

KL> So the context is handover from PMIPv4 to CMIPv4.  CMIPv4 to PMIPv4
is not covered?  

If RFC 3957 is not used, then what method will set up the security
associations?  I'm not sure how the MN-AAA and FA challenge/response can
be avoided when switching over to CMIPv4, assuming no SA fetched ahead
of time?


> The use of the 'S' bit (and zero lifetime and new CoA) for this 
> purpose seems kludgy in the protocol.  It may be better to have 
> explicit Pre-registration Extension to indicate that the message is 
> intended to perform operations on the entities before actual handoff
> signaled by registration request/reply exchange.    

We decided to use the 'S' bit because it seems logical that the node is
trying to create another registration without tearing down the old one,
albeit one which doesn't tunnel traffic hence the zero lifetime.
However, I'm open to other ways of solving the problem and perhaps a new
extension would work; however, we really wanted to introduce just the
minimum amount of new specification and the current approach could even
be considered an implementation option in an existing HA.

KL> Either way, it's a change to existing HA implementation. :)

Kent

> So maybe the draft has some promise.  But it would be much better if 
> the applicability is better articulated.  I'm willing to help out if 
> that is desired.

Thanks for that - maybe this note can clear up some of the intentions of
the draft.

-Pete

> Kent
> 
> -----Original Message-----
> From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf 
> Of McCann Peter-A001034
> Sent: Friday, April 04, 2008 10:32 AM
> To: mip4@ietf.org
> Subject: [Mip4] draft-mccann-mip4-mbb-00.txt
> 
> <<Chair hat off>>
> 
> I've just uploaded a short draft that contains some suggestions on HA 
> implementation details to assist in make-before-break handoffs.  I 
> hope people can read and comment:
> 
>    A make-before-break handoff is one where resources on a target
>    system are allocated prior to releasing the resources on a source
>    system. Make-before-break can be an effective means to provide a
>    more seamless handoff with fewer dropped packets.  The existing
>    Mobile IPv4 specification supports simultaneous bindings, which can
>    facilitate a make-before-break handoff.  However, the binding state
>    at the home agent is only one example of a resource that can be
>    allocated; others include the link connection to the Foreign Agent
>    (or access router) and the provision of security associations
>    between the mobile node and the mobility agents.  It may be
>    desirable to set up these resources on the target system without
>    necessarily creating a binding entry on the Home Agent.  This
>    document provides some additional conventions on the use of
>    simultaneous bindings in a make- before-break handoff that can be
>    used to optimize the allocation of resources in these scenarios.
> 
> These suggestions might be appropriate for inclusion in rfc3344bis, if

> there is still time to make them, or it could be published as a 
> separate document.
> 
> Please, let me know what you think!
> 
> -Pete

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


From mip4-bounces@ietf.org  Fri Apr 11 02:16:53 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D6C143A6A4F;
	Fri, 11 Apr 2008 02:16:53 -0700 (PDT)
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 309623A68AD
	for <mip4@core3.amsl.com>; Fri, 11 Apr 2008 02:16:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.357
X-Spam-Level: 
X-Spam-Status: No, score=-1.357 tagged_above=-999 required=5 tests=[AWL=0.620, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 DrEhQ2CfhXkY for <mip4@core3.amsl.com>;
	Fri, 11 Apr 2008 02:16:51 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.173])
	by core3.amsl.com (Postfix) with ESMTP id EAC073A67FA
	for <mip4@ietf.org>; Fri, 11 Apr 2008 02:16:50 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 25so416877wfa.31
	for <mip4@ietf.org>; Fri, 11 Apr 2008 02:17:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=+u7oWXzxYTMfYz1GkGIPSt+MqkNp7WQQsy0UNHy8wTQ=;
	b=HxKdYNoYNrHE4ZAPHD819vmT2qmC9Hn8yv+S8EPWZeeR7a08qTA01NgKRJB3vseV4mi7CQabXFvfwoBwu7AFsHinfkGw9YCtKWIDnEIPImBYoH+D7fmcOFw+6s+osfKi7P5TelUSF1N9+VCSUCC9ABw82gU0/jCiJm5bbipHG0Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=NQdM4d6ueby2AYZXjeCwrAI1UhIhwau4XKGgDqJVsZuhfWNqn3HkK3xvTBg3hdTzSNIJDHUw4a2pXo5/Rl39ftN56n6jqbYEB5CZLsxfZSIDBOT/5SCBwi0MwIylEDaXP3sGBYpZOtBrsycd4rSVxSPPNASBlvqs+36hKu11TR4=
Received: by 10.142.87.7 with SMTP id k7mr769994wfb.167.1207905433893;
	Fri, 11 Apr 2008 02:17:13 -0700 (PDT)
Received: by 10.142.224.10 with HTTP; Fri, 11 Apr 2008 02:17:13 -0700 (PDT)
Message-ID: <d3886a520804110217r73464f25p864f4f300b424059@mail.gmail.com>
Date: Fri, 11 Apr 2008 10:17:13 +0100
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Kent Leung (kleung)" <kleung@cisco.com>
In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC5205D87904@xmb-sjc-235.amer.cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <d3886a520804090549n76a55f82ud640c6d14f722ac7@mail.gmail.com>
	<2979E38DD6FC6544B789C8DAD7BAFC5205D87904@xmb-sjc-235.amer.cisco.com>
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>, Acee Lindem <acee@redback.com>
Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132
	-foreignagent failed authentication
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

OK Kent, I understand your position.
Regards
George

On Thu, Apr 10, 2008 at 11:32 PM, Kent Leung (kleung) <kleung@cisco.com> wrote:
> Hi George.  I mentioned the reasons in my previous email: default
>  implementation adhering to RFC language in deployment for years and
>  experience has shown usefulness of reply and lack of FA DoS attacks.
>  Keeping the language the same does not break anything or prevent
>  implementations from supporting both cases. :)
>
>
>  Kent
>
>  -----Original Message-----
>  From: George Tsirtsis [mailto:tsirtsis@googlemail.com]
>
> Sent: Wednesday, April 09, 2008 5:49 AM
>  To: Kent Leung (kleung)
>
>
> Cc: Acee Lindem; Mobile IPv4 Mailing List
>  Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132
>  -foreignagent failed authentication
>
>  OK, so from the various comments I get that my proposal (2) maybe
>  pushing things too far so I am not going to insist.
>
>  Kent, could you clarify why you do not want to soften the SHOULD
>  language, to at least a MAY + a warning?
>  It seems to me that such a change is not going to break any existing
>  implementations; instead it will allow any new implementations to make
>  more informed decision on this. Note that both SHOULD and MAY are
>  compatible with implementations that either send or don't send the
>  131/132 codes. Only if we change this to MUST/MUST NOT we would break
>  something, so this is only a matter of emphasis and recommendation.
>
>  Regards
>  George
>
>  On Tue, Apr 8, 2008 at 5:18 PM, Kent Leung (kleung) <kleung@cisco.com>
>  wrote:
>  > I have slight adversion to the language change.  Not because I
>  > disagree  with George's reasoning.  But on the fact that deployments
>  > and  implementations already have default behavior based on existing
>  > RFC.  So  not clear what is accomplished from the practical
>  > perspective.  Whatever  the default behavior is in the implementation,
>
>  > there will need to be a  knob for the alternative behavior.  So in
>  > essence, both needs to be  supported. The language change would only
>  > stir up unnecessary bickering  among vendors on whose default behavior
>  is more right.
>  >
>  >  BTW, experience has shown that sending reply with error code 132 has
>
>  > been advantageous.  The FA-HA authentication failure discovered
>  > misconfiguration.  Have not seen any cases of DoS attack from FAs.  So
>
>  > I  prefer to leave the SHOULD as is.
>  >
>  >
>  >  Kent
>  >
>  >  -----Original Message-----
>  >  From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf
>  > Of  Acee Lindem
>  >
>  >
>  > Sent: Monday, April 07, 2008 6:27 PM
>  >  To: Kent Leung (kleung)
>  >  Cc: Mobile IPv4 Mailing List
>  >  Subject: Re: [Mip4] RFC 3344 - Home Agent Registration Code 132
>  > -foreignagent failed authentication
>  >
>  >
>  >  On Apr 7, 2008, at 2:10 PM, Kent Leung (kleung) wrote:
>  >
>  >  > Isn't there a significantly higher chance of DoS attacks from MNs
>  > > (i.e.
>  >  > invalid MN-HA Auth Ext) than from FAs (i.e. invalid FA-HA Auth
>  Ext)?
>  >
>  >  Yes. This seems like a more likely attack.
>  >
>  >  > When FA-HA authentication fails, it's usually due to
>  misconfiguration.
>  >  > Of course, a rogue MN can append FA-HA Auth Ext in the request.
>  >  >
>  >  > I've always preferred not to send reply when authentication failed
>  > by  > only logging the event.  But then always runs into cases when
>  > the  > reply was required.  So I think it's up to implementation to
>  > decide  > the sending of the RRP or not when authentication fails.
>  > Not sure if  > changing the RFC is necessary.
>  >
>  >  Would you be opposed to changing the "SHOULD" to a "MAY" as proposed
>  > by  George?
>  >
>  >  Thanks,
>  >  Acee
>  >
>  >
>  >  >
>  >  > Kent
>  >  >
>  >  > -----Original Message-----
>  >  > From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On
>  > Behalf  > Of Acee Lindem  > Sent: Friday, April 04, 2008 12:02 PM  >
>  > Cc: Mobile IPv4 Mailing List  > Subject: Re: [Mip4] RFC 3344 - Home
>  > Agent Registration Code 132 -  > foreignagent failed authentication  >
>
>  > > Any opinions?
>  >  > Thanks,
>  >  > Acee
>  >  > On Mar 21, 2008, at 10:49 AM, Acee Lindem wrote:
>  >  >
>  >  >> With respect to our MIP4 HA implementation, we've had several  >>
>  > discussions as to whether a registration reply should be generated  >>
>
>  > when the registration request fails FA-HA authentication. The  >>
>  > existence of the 132 reply code would imply that one should always  >>
>
>  > respond. However, this is contrary to way authentication works in  >>
>  > most  >  >> protocols (at least routing protocols) and would seem to
>  > leave the HA
>  >
>  >  >> more susceptible to DoS attacks. I checked the RFC 3344 BIS draft
>  > and
>  >
>  >  >> there has been no change in this area.
>  >  >> Thanks,
>  >  >> Acee
>  >  >
>  >  > --
>  >  > Mip4 mailing list: Mip4@ietf.org
>  >  >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>  >  >      Charter page:
>  http://www.ietf.org/html.charters/mip4-charter.html
>  >  > Supplemental site: http://www.mip4.org/  > --  > Mip4 mailing list:
>
>  > Mip4@ietf.org
>  >  >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>  >  >      Charter page:
>  http://www.ietf.org/html.charters/mip4-charter.html
>  >  > Supplemental site: http://www.mip4.org/
>  >
>  >  --
>  >  Mip4 mailing list: Mip4@ietf.org
>  >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>  >      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>  >  Supplemental site: http://www.mip4.org/
>  >  --
>  >
>  >
>  > Mip4 mailing list: Mip4@ietf.org
>  >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>  >      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>  >  Supplemental site: http://www.mip4.org/
>  >
>
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Fri Apr 11 08:06:15 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B71FF3A6F21;
	Fri, 11 Apr 2008 08:06:14 -0700 (PDT)
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 040C83A6EAB
	for <mip4@core3.amsl.com>; Fri, 11 Apr 2008 08:06:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gIzmFDaaYRmf for <mip4@core3.amsl.com>;
	Fri, 11 Apr 2008 08:06:00 -0700 (PDT)
Received: from mail119.messagelabs.com (mail119.messagelabs.com
	[216.82.241.179])
	by core3.amsl.com (Postfix) with SMTP id 76D4D3A6E8F
	for <mip4@ietf.org>; Fri, 11 Apr 2008 08:05:34 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: pete.mccann@motorola.com
X-Msg-Ref: server-3.tower-119.messagelabs.com!1207926357!29148361!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 1027 invoked from network); 11 Apr 2008 15:05:57 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-3.tower-119.messagelabs.com with SMTP;
	11 Apr 2008 15:05:57 -0000
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id m3BF5uYS006489
	for <mip4@ietf.org>; Fri, 11 Apr 2008 08:05:56 -0700 (MST)
Received: from il06vts01.mot.com (il06vts01.mot.com [129.188.137.141])
	by il06exr02.mot.com (8.13.1/Vontu) with SMTP id m3BF5u34026190
	for <mip4@ietf.org>; Fri, 11 Apr 2008 10:05:56 -0500 (CDT)
Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id m3BF5tj6026169
	for <mip4@ietf.org>; Fri, 11 Apr 2008 10:05:55 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 11 Apr 2008 11:05:53 -0400
Message-ID: <BE4B07D4197BF34EB3B753DD34EBCD130279DC7D@de01exm67.ds.mot.com>
In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC5205D87911@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] draft-mccann-mip4-mbb-00.txt
thread-index: AciWeb7Xj1Zc8hGYTzukWio37cmMpQDJ8wlgACw1C0AAQhufkAAiCUEg
References: <BE4B07D4197BF34EB3B753DD34EBCD130276B6E5@de01exm67.ds.mot.com>
	<2979E38DD6FC6544B789C8DAD7BAFC5205D87911@xmb-sjc-235.amer.cisco.com>
From: "McCann Peter-A001034" <pete.mccann@motorola.com>
To: "Kent Leung (kleung)" <kleung@cisco.com>, <mip4@ietf.org>
X-CFilter-Loop: Reflected
Subject: Re: [Mip4] draft-mccann-mip4-mbb-00.txt
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi, Kent,

Kent Leung (kleung) wrote:
> Comments below.
> 
> -----Original Message-----
> From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com]
> Sent: Wednesday, April 09, 2008 8:07 AM
> To: Kent Leung (kleung); mip4@ietf.org
> Subject: RE: [Mip4] draft-mccann-mip4-mbb-00.txt
> 
> Hi, Kent,
> 
> Thanks for reading the document.  See below...
> 
> Kent Leung (kleung) wrote:
>> Hi Pete.  The draft seems to only point out that the security
>> association can be fetched during the pre-registration exchange using
>> RFC 3957.  But this RFC is not in use, AFAIK.  It's not clear to me
>> if 
> 
>> that the draft clearly identify other benefits besides the early SA
>> establishment.  In the PMIP case, it's unlikely that the PMIP
>> client/PMA would have the MN-AAA key which is needed to derive the
>> other keys in RFC 3957.
> 
> We originally started the draft to solve a problem when handing off
> from 
> PMIPv4 to CMIPv4; the idea is to complete authentication on the
> CMIPv4 side without actually setting up the tunnel for the bearer
> traffic, but to do that at a later time.  There are deployments that
> use MN-AAA, and personally, I think these deployments should also be
> using RFC 3957 because it solves the problem of distributing complete
> security associations, whereas other solutions just distribute keys. 
> In any case, it doesn't really matter whether or not the deployment
> uses 3957 as long as it has authentication (MN-AAA and FA
> Challenge/Response) which most CMIP deployments do.        
> 
>> So the context is handover from PMIPv4 to CMIPv4.  CMIPv4 to PMIPv4
>> is not covered? 

I would imagine that a PMIP network already has security associations
in place to protect the proxy registrations.

> If RFC 3957 is not used, then what method will set up the security
> associations?  I'm not sure how the MN-AAA and FA challenge/response
> can be avoided when switching over to CMIPv4, assuming no SA fetched
> ahead of time?   

No, they wouldn't be avoided; in fact the draft anticipates their use.
If 3957 isn't being used, the HA can do whatever it needs to set up
the security association such as fetching it from AAA or whatever.
 
>> The use of the 'S' bit (and zero lifetime and new CoA) for this
>> purpose seems kludgy in the protocol.  It may be better to have
>> explicit Pre-registration Extension to indicate that the message is
>> intended to perform operations on the entities before actual handoff
>> signaled by registration request/reply exchange.
> 
> We decided to use the 'S' bit because it seems logical that the node
> is trying to create another registration without tearing down the old
> one, albeit one which doesn't tunnel traffic hence the zero lifetime.
> However, I'm open to other ways of solving the problem and perhaps a
> new extension would work; however, we really wanted to introduce just
> the minimum amount of new specification and the current approach
> could even be considered an implementation option in an existing HA. 
> 
>> Either way, it's a change to existing HA implementation. :)

True, but no new PDUs need to be decoded.

-Pete

> Kent
> 
>> So maybe the draft has some promise.  But it would be much better if
>> the applicability is better articulated.  I'm willing to help out if
>> that is desired.
> 
> Thanks for that - maybe this note can clear up some of the intentions
> of the draft. 
> 
> -Pete
> 
>> Kent
>> 
>> -----Original Message-----
>> From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf
>> Of McCann Peter-A001034 Sent: Friday, April 04, 2008 10:32 AM
>> To: mip4@ietf.org
>> Subject: [Mip4] draft-mccann-mip4-mbb-00.txt
>> 
>> <<Chair hat off>>
>> 
>> I've just uploaded a short draft that contains some suggestions on HA
>> implementation details to assist in make-before-break handoffs.  I
>> hope people can read and comment:
>> 
>>    A make-before-break handoff is one where resources on a target
>>    system are allocated prior to releasing the resources on a source
>>    system. Make-before-break can be an effective means to provide a
>>    more seamless handoff with fewer dropped packets.  The existing
>>    Mobile IPv4 specification supports simultaneous bindings, which
>>    can facilitate a make-before-break handoff.  However, the binding
>>    state at the home agent is only one example of a resource that
>>    can be allocated; others include the link connection to the
>>    Foreign Agent (or access router) and the provision of security
>>    associations between the mobile node and the mobility agents.  It
>>    may be desirable to set up these resources on the target system
>>    without necessarily creating a binding entry on the Home Agent. 
>>    This document provides some additional conventions on the use of
>>    simultaneous bindings in a make- before-break handoff that can be
>>    used to optimize the allocation of resources in these scenarios.
>> 
>> These suggestions might be appropriate for inclusion in rfc3344bis,
>> if 
> 
>> there is still time to make them, or it could be published as a
>> separate document. 
>> 
>> Please, let me know what you think!
>> 
>> -Pete

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


From mip4-bounces@ietf.org  Fri Apr 11 17:27:04 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8E0433A6AAA;
	Fri, 11 Apr 2008 17:27:04 -0700 (PDT)
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 2F21D3A67DF
	for <mip4@core3.amsl.com>; Fri, 11 Apr 2008 17:27:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.108
X-Spam-Level: 
X-Spam-Status: No, score=0.108 tagged_above=-999 required=5 tests=[AWL=0.086, 
	BAYES_00=-2.599, HOST_EQ_STATIC=1.172, MSGID_MULTIPLE_AT=1.449]
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 gVDfqJYVC5yM for <mip4@core3.amsl.com>;
	Fri, 11 Apr 2008 17:27:02 -0700 (PDT)
Received: from mail.zteusa.com (28.2a.0540.static.theplanet.com [64.5.42.40])
	by core3.amsl.com (Postfix) with ESMTP id 545E73A6A4C
	for <mip4@ietf.org>; Fri, 11 Apr 2008 17:27:02 -0700 (PDT)
Received: from ywu (69-229-94-147.ded.pacbell.net [69.229.94.147])
	by mail.zteusa.com (8.13.4/8.13.4/SuSE Linux 0.7) with ESMTP id
	m3C0Rn0W013077
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Fri, 11 Apr 2008 19:27:50 -0500
From: "Yingzhe Wu" <yingzhe.wu@zteusa.com>
To: "'McCann Peter-A001034'" <pete.mccann@motorola.com>, <mip4@ietf.org>
References: <BE4B07D4197BF34EB3B753DD34EBCD130272ABAE@de01exm67.ds.mot.com>
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD130272ABAE@de01exm67.ds.mot.com>
Date: Fri, 11 Apr 2008 17:27:36 -0700
Message-ID: <004c01c89c34$029cc4c0$07d64e40$@wu@zteusa.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AciWd5/DNuCke2dhQBqVWbOvHrpBxQFurWxQ
Content-Language: en-us
Cc: henrik@levkowetz.com
Subject: Re: [Mip4] WGLC: 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: <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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

I support the advancement of this document to the IESG with a request for
publication as a Proposed Standard RFC.

A minor comment: In Figure 3, change the box AAA/HA to AAA, better match the
description above. The case for HA notification to FA already in section 3.3
below.

Thanks,
Yingzhe

-----Original Message-----
From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of
McCann Peter-A001034
Sent: Friday, April 04, 2008 10:17 AM
To: mip4@ietf.org
Cc: henrik@levkowetz.com
Subject: [Mip4] WGLC: draft-ietf-mip4-generic-notification-message-04.txt

This message announces a 2-week working group last call on:

"Generic Notification Message for Mobile IPv4"          
draft-ietf-mip4-generic-notification-message-04.txt

The last call will end at 24:00 UTC on Friday, April 18 2008.

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


Please respond to this working group last call:

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

    "I support the advancement of this document to the IESG with a
     request for publication as a Proposed Standard RFC."

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


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

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

Please direct all replies to the Mobile IPv4 mailing list,
mip4@ietf.org.


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

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


From mip4-bounces@ietf.org  Sun Apr 13 23:27:31 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C47223A6C5F;
	Sun, 13 Apr 2008 23:27:31 -0700 (PDT)
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 A90943A69C3
	for <mip4@core3.amsl.com>; Sun, 13 Apr 2008 23:27:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.506
X-Spam-Level: 
X-Spam-Status: No, score=-6.506 tagged_above=-999 required=5 tests=[AWL=0.093, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id J1KXnRZC5-2H for <mip4@core3.amsl.com>;
	Sun, 13 Apr 2008 23:27:28 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id D9A163A6A3C
	for <mip4@ietf.org>; Sun, 13 Apr 2008 23:27:28 -0700 (PDT)
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-2.cisco.com with ESMTP; 13 Apr 2008 23:27:59 -0700
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 m3E6RxgY024927; 
	Sun, 13 Apr 2008 23:27:59 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m3E6RwTe007863;
	Mon, 14 Apr 2008 06:27:58 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 13 Apr 2008 23:27:58 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 13 Apr 2008 23:27:55 -0700
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5205E109A5@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD130279DC7D@de01exm67.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] draft-mccann-mip4-mbb-00.txt
Thread-Index: AciWeb7Xj1Zc8hGYTzukWio37cmMpQDJ8wlgACw1C0AAQhufkAAiCUEgAITkPeA=
From: "Kent Leung (kleung)" <kleung@cisco.com>
To: "McCann Peter-A001034" <pete.mccann@motorola.com>, <mip4@ietf.org>
X-OriginalArrivalTime: 14 Apr 2008 06:27:58.0687 (UTC)
	FILETIME=[AE9A7EF0:01C89DF8]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2064; t=1208154479;
	x=1209018479; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kleung@cisco.com;
	z=From:=20=22Kent=20Leung=20(kleung)=22=20<kleung@cisco.com>
	|Subject:=20RE=3A=20[Mip4]=20draft-mccann-mip4-mbb-00.txt
	|Sender:=20; bh=cUULqAacy80vto+IZDtIdMef7f1js6xPpUo/Vs0qyiU=;
	b=PbmSFTWFqZsgJvp+om//fzybvNrGuy5wrNjTuLTgSrBGl/0xNoBlEak0NR
	j0OFk4meMHXHB9qjRyNbhjiH7MoNV21XU4Yynjf4g+SfRTdTyw24foT5FXiN
	osqZt8PDh+;
Authentication-Results: sj-dkim-2; header.From=kleung@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Subject: Re: [Mip4] draft-mccann-mip4-mbb-00.txt
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

 

> If RFC 3957 is not used, then what method will set up the security 
> associations?  I'm not sure how the MN-AAA and FA challenge/response 
> can be avoided when switching over to CMIPv4, assuming no SA fetched
> ahead of time?   

No, they wouldn't be avoided; in fact the draft anticipates their use.
If 3957 isn't being used, the HA can do whatever it needs to set up the
security association such as fetching it from AAA or whatever.
 
KL> OK.  That is reasonable.  The preregistation message can fetch
subscriber attributes from AAA server in advance.


>> The use of the 'S' bit (and zero lifetime and new CoA) for this 
>> purpose seems kludgy in the protocol.  It may be better to have 
>> explicit Pre-registration Extension to indicate that the message is 
>> intended to perform operations on the entities before actual handoff 
>> signaled by registration request/reply exchange.
> 
> We decided to use the 'S' bit because it seems logical that the node 
> is trying to create another registration without tearing down the old 
> one, albeit one which doesn't tunnel traffic hence the zero lifetime.
> However, I'm open to other ways of solving the problem and perhaps a 
> new extension would work; however, we really wanted to introduce just 
> the minimum amount of new specification and the current approach could

> even be considered an implementation option in an existing HA.
> 
>> Either way, it's a change to existing HA implementation. :)

True, but no new PDUs need to be decoded.

KL> My initial reaction to re-using/overloading the S-bit (which was
defined for simultaneous bindings) was that it was confusing to be using
for a different function, namely pre-registration operation.  Now, your
explanation helps with why that approach was selected.  Though I'm not
sure if I would quite agree with that because both the message initiator
and the HA have to have the new logic for dealing with the new
signaling, regardless if it's a bit or extension. 

Kent

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


From mip4-bounces@ietf.org  Mon Apr 14 06:04:38 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 23D123A6B50;
	Mon, 14 Apr 2008 06:04:38 -0700 (PDT)
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 71E843A6CC8
	for <mip4@core3.amsl.com>; Mon, 14 Apr 2008 06:04:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.486
X-Spam-Level: 
X-Spam-Status: No, score=-6.486 tagged_above=-999 required=5 tests=[AWL=0.113, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tBaa1XgN84A8 for <mip4@core3.amsl.com>;
	Mon, 14 Apr 2008 06:04:31 -0700 (PDT)
Received: from zcars04f.nortel.com (zcars04f.nortel.com [47.129.242.57])
	by core3.amsl.com (Postfix) with ESMTP id 21BFA3A6A4C
	for <mip4@ietf.org>; Mon, 14 Apr 2008 06:04:31 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m3ED4o617123; Mon, 14 Apr 2008 13:04:51 GMT
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 14 Apr 2008 08:04:37 -0500
Message-ID: <C5A96676FCD00745B64AE42D5FCC9B6E17AF4A60@zrc2hxm0.corp.nortel.com>
In-reply-to: <2979E38DD6FC6544B789C8DAD7BAFC5205E109A5@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] draft-mccann-mip4-mbb-00.txt
Thread-index: AciWeb7Xj1Zc8hGYTzukWio37cmMpQDJ8wlgACw1C0AAQhufkAAiCUEgAITkPeAADjNIcA==
References: <BE4B07D4197BF34EB3B753DD34EBCD130279DC7D@de01exm67.ds.mot.com>
	<2979E38DD6FC6544B789C8DAD7BAFC5205E109A5@xmb-sjc-235.amer.cisco.com>
From: "Ahmad Muhanna" <amuhanna@nortel.com>
To: "Kent Leung (kleung)" <kleung@cisco.com>,
	"McCann Peter-A001034" <pete.mccann@motorola.com>, <mip4@ietf.org>
Subject: Re: [Mip4] draft-mccann-mip4-mbb-00.txt
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

 
> 
> >> The use of the 'S' bit (and zero lifetime and new CoA) for this 
> >> purpose seems kludgy in the protocol.  It may be better to have 
> >> explicit Pre-registration Extension to indicate that the 
> message is 
> >> intended to perform operations on the entities before 
> actual handoff 
> >> signaled by registration request/reply exchange.
> > 
> > We decided to use the 'S' bit because it seems logical that 
> the node 
> > is trying to create another registration without tearing 
> down the old 
> > one, albeit one which doesn't tunnel traffic hence the zero 
> lifetime.
> > However, I'm open to other ways of solving the problem and 
> perhaps a 
> > new extension would work; however, we really wanted to 
> introduce just 
> > the minimum amount of new specification and the current 
> approach could
> 
> > even be considered an implementation option in an existing HA.
> > 
> >> Either way, it's a change to existing HA implementation. :)
> 
> True, but no new PDUs need to be decoded.
> 
> KL> My initial reaction to re-using/overloading the S-bit (which was
> defined for simultaneous bindings) was that it was confusing 
> to be using for a different function, namely pre-registration 
> operation.  Now, your explanation helps with why that 
> approach was selected.  Though I'm not sure if I would quite 
> agree with that because both the message initiator and the HA 
> have to have the new logic for dealing with the new 
> signaling, regardless if it's a bit or extension.

[Ahmad]
I tend to agree. 
I actually communicated my views earlier to Pete offline and mentioned
that since the proposal include changes at the MN and the HA anyway,
then why not we do a clean solution for this pr-registration by using a
new extension rather than over load the status bit logic.

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


From mip4-bounces@ietf.org  Mon Apr 14 06:09:53 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ED48F3A6E6C;
	Mon, 14 Apr 2008 06:09:53 -0700 (PDT)
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 7CB4A3A6B50
	for <mip4@core3.amsl.com>; Mon, 14 Apr 2008 06:09:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Zi2sBZiyD9hY for <mip4@core3.amsl.com>;
	Mon, 14 Apr 2008 06:09:49 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56])
	by core3.amsl.com (Postfix) with ESMTP id 53E6B3A67CE
	for <mip4@ietf.org>; Mon, 14 Apr 2008 06:09:49 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m3ED9jW18984; Mon, 14 Apr 2008 13:09:45 GMT
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 14 Apr 2008 08:09:29 -0500
Message-ID: <C5A96676FCD00745B64AE42D5FCC9B6E17AF4A76@zrc2hxm0.corp.nortel.com>
In-reply-to: <C5A96676FCD00745B64AE42D5FCC9B6E17AF4A60@zrc2hxm0.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] draft-mccann-mip4-mbb-00.txt
Thread-index: AciWeb7Xj1Zc8hGYTzukWio37cmMpQDJ8wlgACw1C0AAQhufkAAiCUEgAITkPeAADjNIcAAAU1EQ
References: <BE4B07D4197BF34EB3B753DD34EBCD130279DC7D@de01exm67.ds.mot.com>
	<2979E38DD6FC6544B789C8DAD7BAFC5205E109A5@xmb-sjc-235.amer.cisco.com>
	<C5A96676FCD00745B64AE42D5FCC9B6E17AF4A60@zrc2hxm0.corp.nortel.com>
From: "Ahmad Muhanna" <amuhanna@nortel.com>
To: "Ahmad Muhanna" <amuhanna@nortel.com>,
	"Kent Leung (kleung)" <kleung@cisco.com>,
	"McCann Peter-A001034" <pete.mccann@motorola.com>, <mip4@ietf.org>
Subject: Re: [Mip4] draft-mccann-mip4-mbb-00.txt
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org


> > 
> > KL> My initial reaction to re-using/overloading the S-bit (which was
> > defined for simultaneous bindings) was that it was confusing to be 
> > using for a different function, namely pre-registration operation.  
> > Now, your explanation helps with why that approach was selected.  
> > Though I'm not sure if I would quite agree with that 
> because both the 
> > message initiator and the HA have to have the new logic for dealing 
> > with the new signaling, regardless if it's a bit or extension.
> 
> [Ahmad]
> I tend to agree. 
> I actually communicated my views earlier to Pete offline and 
> mentioned that since the proposal include changes at the MN 
> and the HA anyway, then why not we do a clean solution for 
> this pr-registration by using a new extension rather than 
> over load the status bit logic.

[Ahmad]
Hmmm.. meant to say the Simultaneous binding bit:-)
> 
> > 
> > Kent
> > 
> > --
> > Mip4 mailing list: Mip4@ietf.org
> >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
> >      Charter page: 
> http://www.ietf.org/html.charters/mip4-charter.html
> > Supplemental site: http://www.mip4.org/
> > 
> --
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
> 
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Mon Apr 14 07:49:29 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 863C83A68D9;
	Mon, 14 Apr 2008 07:49:29 -0700 (PDT)
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 1481F3A68D9
	for <mip4@core3.amsl.com>; Mon, 14 Apr 2008 07:49:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Cl9MB+XmJLtH for <mip4@core3.amsl.com>;
	Mon, 14 Apr 2008 07:49:28 -0700 (PDT)
Received: from mail153.messagelabs.com (mail153.messagelabs.com
	[216.82.253.51]) by core3.amsl.com (Postfix) with SMTP id 498623A67D0
	for <mip4@ietf.org>; Mon, 14 Apr 2008 07:49:28 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: pete.mccann@motorola.com
X-Msg-Ref: server-2.tower-153.messagelabs.com!1208184598!9322136!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 8853 invoked from network); 14 Apr 2008 14:49:58 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-2.tower-153.messagelabs.com with SMTP;
	14 Apr 2008 14:49:58 -0000
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id m3EEnvNd006424
	for <mip4@ietf.org>; Mon, 14 Apr 2008 07:49:57 -0700 (MST)
Received: from il06vts02.mot.com (il06vts02.mot.com [129.188.137.142])
	by il06exr02.mot.com (8.13.1/Vontu) with SMTP id m3EEnvW3028438
	for <mip4@ietf.org>; Mon, 14 Apr 2008 09:49:57 -0500 (CDT)
Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id m3EEnuvx028430
	for <mip4@ietf.org>; Mon, 14 Apr 2008 09:49:56 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 14 Apr 2008 10:49:55 -0400
Message-ID: <BE4B07D4197BF34EB3B753DD34EBCD130279E163@de01exm67.ds.mot.com>
In-Reply-To: <C5A96676FCD00745B64AE42D5FCC9B6E17AF4A76@zrc2hxm0.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] draft-mccann-mip4-mbb-00.txt
thread-index: AciWeb7Xj1Zc8hGYTzukWio37cmMpQDJ8wlgACw1C0AAQhufkAAiCUEgAITkPeAADjNIcAAAU1EQAAN/wXA=
References: <BE4B07D4197BF34EB3B753DD34EBCD130279DC7D@de01exm67.ds.mot.com>
	<2979E38DD6FC6544B789C8DAD7BAFC5205E109A5@xmb-sjc-235.amer.cisco.com>
	<C5A96676FCD00745B64AE42D5FCC9B6E17AF4A60@zrc2hxm0.corp.nortel.com>
	<C5A96676FCD00745B64AE42D5FCC9B6E17AF4A76@zrc2hxm0.corp.nortel.com>
From: "McCann Peter-A001034" <pete.mccann@motorola.com>
To: "Ahmad Muhanna" <amuhanna@nortel.com>,
	"Kent Leung (kleung)" <kleung@cisco.com>, <mip4@ietf.org>
X-CFilter-Loop: Reflected
Subject: Re: [Mip4] draft-mccann-mip4-mbb-00.txt
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi, Ahmad, Kent,

In principle I am open to solving the problem in a different
way if we can.  Let's work offline and try to come back with
a draft that we are all happy with.  I think we at least have
a common agreement on the problem to be solved.

Thanks,

-Pete


Ahmad Muhanna wrote:
>>>KL> My initial reaction to re-using/overloading the S-bit (which was
>>> defined for simultaneous bindings) was that it was confusing to be
>>> using for a different function, namely pre-registration operation.
>>> Now, your explanation helps with why that approach was selected.
>>> Though I'm not sure if I would quite agree with that because both
>>> the message initiator and the HA have to have the new logic for
>>> dealing with the new signaling, regardless if it's a bit or
>>> extension. 
>> 
>> [Ahmad]
>> I tend to agree.
>> I actually communicated my views earlier to Pete offline and
>> mentioned that since the proposal include changes at the MN and the
>> HA anyway, then why not we do a clean solution for this
>> pr-registration by using a new extension rather than over load the
>> status bit logic. 
> 
> [Ahmad]
> Hmmm.. meant to say the Simultaneous binding bit:-)
>> 
>>> 
>>> Kent
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Mon Apr 14 13:01:03 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 87BA23A6EE4;
	Mon, 14 Apr 2008 13:01:03 -0700 (PDT)
X-Original-To: mip4@ietf.org
Delivered-To: mip4@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30)
	id 4CA063A67E2; Mon, 14 Apr 2008 13:01:01 -0700 (PDT)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20080414200102.4CA063A67E2@core3.amsl.com>
Date: Mon, 14 Apr 2008 13:01:02 -0700 (PDT)
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: 'Mobile IPv4 Traversal Across IPsec-based
 VPN Gateways' to Proposed Standard
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>
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:

- 'Mobile IPv4 Traversal Across IPsec-based VPN Gateways '
   <draft-ietf-mip4-vpn-problem-solution-05.txt> as a Proposed Standard

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-vpn-problem-solution-05.txt

Technical Summary
 
  This document outlines a solution for the Mobile IPv4 and IPsec
  coexistence problem for enterprise users.  The solution consists of
  an applicability statement for using Mobile IPv4 and IPsec for
  session mobility in corporate remote access scenarios, and a required
  mechanism for detecting the trusted internal network securely. The
  solution requires only changes to the mobile node; changes to Mobile
  IPv4 or IPsec protocols, the VPN gateway, or the home agent are not
  required.
 
Working Group Summary
 
  This is a product of the MIP4 WG, and has the backing of the
  WG. It has emerged from the work done by the VPN traversal
  design team.

Protocol Quality
 
  This specification has been reviewed by Henrik Levkowetz, Vijay
  Deverapalli, Jari Arkko, and members of the MIP4 WG.

Note to RFC Editor
 
  In Section 5.2, change:

  OLD:
   The overhead consists of the following:
  NEW:
   The maximum overhead of 97 octets in the 'cvc' access mode
   consists of the following: 

  Also, please change s/abovementioned/above mentioned and
  s/untypical/atypical throughout the document.

  Add to the end of the IANA Considerations section:

    Allocation of new Sub-Type values can be made via
    Expert Review and Specification Required [I-D.narten-iana-
    considerations-rfc2434bis].

  And add draft-narten as a new normative reference.

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


From mip4-bounces@ietf.org  Mon Apr 14 19:13:58 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5AB5F28C230;
	Mon, 14 Apr 2008 19:13:58 -0700 (PDT)
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 4F7083A6A81
	for <mip4@core3.amsl.com>; Mon, 14 Apr 2008 19:13:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.189
X-Spam-Level: 
X-Spam-Status: No, score=-0.189 tagged_above=-999 required=5 tests=[AWL=2.410, 
	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 qGNRT1k09Yc5 for <mip4@core3.amsl.com>;
	Mon, 14 Apr 2008 19:13:55 -0700 (PDT)
Received: from ict.ac.cn (webmail.ict.ac.cn [159.226.39.7])
	by core3.amsl.com (Postfix) with ESMTP id 173103A6C9F
	for <mip4@ietf.org>; Mon, 14 Apr 2008 19:13:49 -0700 (PDT)
Received: (qmail 14709 invoked by uid 507); 15 Apr 2008 10:27:28 +0800
Received: from localhost (HELO webmail.ict.ac.cn) (zhouanfu@127.0.0.1)
	by ict.ac.cn with SMTP; 15 Apr 2008 10:27:28 +0800
Received: from 10.21.5.187 (SquirrelMail authenticated user zhouanfu)
	by webmail.ict.ac.cn with HTTP; Tue, 15 Apr 2008 10:27:28 +0800 (CST)
Message-ID: <1651.10.21.5.187.1208226448.squirrel@webmail.ict.ac.cn>
In-Reply-To: <mailman.7.1208199602.13604.mip4@ietf.org>
References: <mailman.7.1208199602.13604.mip4@ietf.org>
Date: Tue, 15 Apr 2008 10:27:28 +0800 (CST)
From: zhouanfu@ict.ac.cn
To: mip4@ietf.org
User-Agent: SquirrelMail/1.4.6
MIME-Version: 1.0
X-Priority: 3 (Normal)
Importance: Normal
Subject: Re: [Mip4] WGLC: 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: <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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

I support the advancement of this document to the IESG with a request for
publication as a Proposed Standard RFC.

During our research on MIP4, We find it is necessary to allow Mobile IPv4
entities to send and receive explicit notification messages using a
new Mobile IPv4 message type.




> Send Mip4 mailing list submissions to
> 	mip4@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://www.ietf.org/mailman/listinfo/mip4
> or, via email, send a message with subject or body 'help' to
> 	mip4-request@ietf.org
>
> You can reach the person managing the list at
> 	mip4-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Mip4 digest..."
>
>
> Today's Topics:
>
>    1. Re: draft-mccann-mip4-mbb-00.txt (Kent Leung (kleung))
>    2. Re: draft-mccann-mip4-mbb-00.txt (Ahmad Muhanna)
>    3. Re: draft-mccann-mip4-mbb-00.txt (Ahmad Muhanna)
>    4. Re: draft-mccann-mip4-mbb-00.txt (McCann Peter-A001034)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 13 Apr 2008 23:27:55 -0700
> From: "Kent Leung (kleung)" <kleung@cisco.com>
> Subject: Re: [Mip4] draft-mccann-mip4-mbb-00.txt
> To: "McCann Peter-A001034" <pete.mccann@motorola.com>, <mip4@ietf.org>
> Message-ID:
> 	<2979E38DD6FC6544B789C8DAD7BAFC5205E109A5@xmb-sjc-235.amer.cisco.com>
> Content-Type: text/plain;	charset="us-ascii"
>
>
>
>> If RFC 3957 is not used, then what method will set up the security
>> associations?  I'm not sure how the MN-AAA and FA challenge/response
>> can be avoided when switching over to CMIPv4, assuming no SA fetched
>> ahead of time?
>
> No, they wouldn't be avoided; in fact the draft anticipates their use.
> If 3957 isn't being used, the HA can do whatever it needs to set up the
> security association such as fetching it from AAA or whatever.
>
> KL> OK.  That is reasonable.  The preregistation message can fetch
> subscriber attributes from AAA server in advance.
>
>
>>> The use of the 'S' bit (and zero lifetime and new CoA) for this
>>> purpose seems kludgy in the protocol.  It may be better to have
>>> explicit Pre-registration Extension to indicate that the message is
>>> intended to perform operations on the entities before actual handoff
>>> signaled by registration request/reply exchange.
>>
>> We decided to use the 'S' bit because it seems logical that the node
>> is trying to create another registration without tearing down the old
>> one, albeit one which doesn't tunnel traffic hence the zero lifetime.
>> However, I'm open to other ways of solving the problem and perhaps a
>> new extension would work; however, we really wanted to introduce just
>> the minimum amount of new specification and the current approach could
>
>> even be considered an implementation option in an existing HA.
>>
>>> Either way, it's a change to existing HA implementation. :)
>
> True, but no new PDUs need to be decoded.
>
> KL> My initial reaction to re-using/overloading the S-bit (which was
> defined for simultaneous bindings) was that it was confusing to be using
> for a different function, namely pre-registration operation.  Now, your
> explanation helps with why that approach was selected.  Though I'm not
> sure if I would quite agree with that because both the message initiator
> and the HA have to have the new logic for dealing with the new
> signaling, regardless if it's a bit or extension.
>
> Kent
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 14 Apr 2008 08:04:37 -0500
> From: "Ahmad Muhanna" <amuhanna@nortel.com>
> Subject: Re: [Mip4] draft-mccann-mip4-mbb-00.txt
> To: "Kent Leung (kleung)" <kleung@cisco.com>,	"McCann Peter-A001034"
> 	<pete.mccann@motorola.com>, <mip4@ietf.org>
> Message-ID:
> 	<C5A96676FCD00745B64AE42D5FCC9B6E17AF4A60@zrc2hxm0.corp.nortel.com>
> Content-Type: text/plain;	charset="US-ASCII"
>
>
>>
>> >> The use of the 'S' bit (and zero lifetime and new CoA) for this
>> >> purpose seems kludgy in the protocol.  It may be better to have
>> >> explicit Pre-registration Extension to indicate that the
>> message is
>> >> intended to perform operations on the entities before
>> actual handoff
>> >> signaled by registration request/reply exchange.
>> >
>> > We decided to use the 'S' bit because it seems logical that
>> the node
>> > is trying to create another registration without tearing
>> down the old
>> > one, albeit one which doesn't tunnel traffic hence the zero
>> lifetime.
>> > However, I'm open to other ways of solving the problem and
>> perhaps a
>> > new extension would work; however, we really wanted to
>> introduce just
>> > the minimum amount of new specification and the current
>> approach could
>>
>> > even be considered an implementation option in an existing HA.
>> >
>> >> Either way, it's a change to existing HA implementation. :)
>>
>> True, but no new PDUs need to be decoded.
>>
>> KL> My initial reaction to re-using/overloading the S-bit (which was
>> defined for simultaneous bindings) was that it was confusing
>> to be using for a different function, namely pre-registration
>> operation.  Now, your explanation helps with why that
>> approach was selected.  Though I'm not sure if I would quite
>> agree with that because both the message initiator and the HA
>> have to have the new logic for dealing with the new
>> signaling, regardless if it's a bit or extension.
>
> [Ahmad]
> I tend to agree.
> I actually communicated my views earlier to Pete offline and mentioned
> that since the proposal include changes at the MN and the HA anyway,
> then why not we do a clean solution for this pr-registration by using a
> new extension rather than over load the status bit logic.
>
>>
>> Kent
>>
>> --
>> 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/
>>
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 14 Apr 2008 08:09:29 -0500
> From: "Ahmad Muhanna" <amuhanna@nortel.com>
> Subject: Re: [Mip4] draft-mccann-mip4-mbb-00.txt
> To: "Ahmad Muhanna" <amuhanna@nortel.com>,	"Kent Leung (kleung)"
> 	<kleung@cisco.com>,	"McCann Peter-A001034" <pete.mccann@motorola.com>,
> 	<mip4@ietf.org>
> Message-ID:
> 	<C5A96676FCD00745B64AE42D5FCC9B6E17AF4A76@zrc2hxm0.corp.nortel.com>
> Content-Type: text/plain;	charset="US-ASCII"
>
>
>> >
>> > KL> My initial reaction to re-using/overloading the S-bit (which was
>> > defined for simultaneous bindings) was that it was confusing to be
>> > using for a different function, namely pre-registration operation.
>> > Now, your explanation helps with why that approach was selected.
>> > Though I'm not sure if I would quite agree with that
>> because both the
>> > message initiator and the HA have to have the new logic for dealing
>> > with the new signaling, regardless if it's a bit or extension.
>>
>> [Ahmad]
>> I tend to agree.
>> I actually communicated my views earlier to Pete offline and
>> mentioned that since the proposal include changes at the MN
>> and the HA anyway, then why not we do a clean solution for
>> this pr-registration by using a new extension rather than
>> over load the status bit logic.
>
> [Ahmad]
> Hmmm.. meant to say the Simultaneous binding bit:-)
>>
>> >
>> > Kent
>> >
>> > --
>> > Mip4 mailing list: Mip4@ietf.org
>> >     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>> >      Charter page:
>> http://www.ietf.org/html.charters/mip4-charter.html
>> > Supplemental site: http://www.mip4.org/
>> >
>> --
>> Mip4 mailing list: Mip4@ietf.org
>>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>> Supplemental site: http://www.mip4.org/
>>
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 14 Apr 2008 10:49:55 -0400
> From: "McCann Peter-A001034" <pete.mccann@motorola.com>
> Subject: Re: [Mip4] draft-mccann-mip4-mbb-00.txt
> To: "Ahmad Muhanna" <amuhanna@nortel.com>,	"Kent Leung (kleung)"
> 	<kleung@cisco.com>, <mip4@ietf.org>
> Message-ID:
> 	<BE4B07D4197BF34EB3B753DD34EBCD130279E163@de01exm67.ds.mot.com>
> Content-Type: text/plain;	charset="us-ascii"
>
> Hi, Ahmad, Kent,
>
> In principle I am open to solving the problem in a different
> way if we can.  Let's work offline and try to come back with
> a draft that we are all happy with.  I think we at least have
> a common agreement on the problem to be solved.
>
> Thanks,
>
> -Pete
>
>
> Ahmad Muhanna wrote:
>>>>KL> My initial reaction to re-using/overloading the S-bit (which was
>>>> defined for simultaneous bindings) was that it was confusing to be
>>>> using for a different function, namely pre-registration operation.
>>>> Now, your explanation helps with why that approach was selected.
>>>> Though I'm not sure if I would quite agree with that because both
>>>> the message initiator and the HA have to have the new logic for
>>>> dealing with the new signaling, regardless if it's a bit or
>>>> extension.
>>>
>>> [Ahmad]
>>> I tend to agree.
>>> I actually communicated my views earlier to Pete offline and
>>> mentioned that since the proposal include changes at the MN and the
>>> HA anyway, then why not we do a clean solution for this
>>> pr-registration by using a new extension rather than over load the
>>> status bit logic.
>>
>> [Ahmad]
>> Hmmm.. meant to say the Simultaneous binding bit:-)
>>>
>>>>
>>>> Kent
>
>
> ------------------------------
>
> --
> 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/
>
>
> End of Mip4 Digest, Vol 47, Issue 13
> ************************************
>
>


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


From mip4-bounces@ietf.org  Thu Apr 17 14:58:07 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 590A83A6D6C;
	Thu, 17 Apr 2008 14:58:07 -0700 (PDT)
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 672FA3A68C4
	for <mip4@core3.amsl.com>; Fri, 11 Apr 2008 19:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.948
X-Spam-Level: 
X-Spam-Status: No, score=-3.948 tagged_above=-999 required=5 tests=[AWL=0.650, 
	BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id HH1esBHxoI2u for <mip4@core3.amsl.com>;
	Fri, 11 Apr 2008 19:57:08 -0700 (PDT)
Received: from caip.rutgers.edu (caip.rutgers.edu [128.6.236.16])
	by core3.amsl.com (Postfix) with ESMTP id 41DBF3A6862
	for <mip4@ietf.org>; Fri, 11 Apr 2008 19:57:08 -0700 (PDT)
Received: from LENOVO5C399A8F (pool-71-187-228-135.nwrknj.fios.verizon.net
	[71.187.228.135]) (authenticated bits=0)
	by caip.rutgers.edu (8.13.8/8.13.8) with ESMTP id m3C2vSIn024743
	for <mip4@ietf.org>; Fri, 11 Apr 2008 22:57:28 -0400
From: "Dario Pompili" <pompili@caip.rutgers.edu>
To: <mip4@ietf.org>
Date: Fri, 11 Apr 2008 22:57:33 -0400
Message-ID: <00ab01c89c48$f4cd9030$0201a8c0@LENOVO5C399A8F>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
thread-index: AcicSAXJBwK6oUl8Tye/yfVkD0obXwAAB8+wAAAxXlA=
X-Scanned-By: MIMEDefang 2.62 on 128.6.236.16
X-Mailman-Approved-At: Thu, 17 Apr 2008 14:58:06 -0700
Subject: [Mip4] CFP: The Third ACM International Workshop on UnderWater
	Networks (WUWNet 2008)
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="===============1138828241=="
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1138828241==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00AC_01C89C27.6DBBF030"

This is a multi-part message in MIME format.

------=_NextPart_000_00AC_01C89C27.6DBBF030
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

> -----------------------------------------------------
>       The Third ACM International Workshop on
>          UnderWater Networks (WUWNet 2008)
>           http://wuwnet08.engr.uconn.edu/
> 
>         In conjunction with ACM MobiCom 2008
>                  September 15, 2008
>            San Francisco, California, USA
> 
>        Sponsored by ACM SIGMOBILE and IEEE OES
> -----------------------------------------------------
> 
> 
> Overview & Scope   
> ****************
> 
> Water covers 71% of the earth's surface with oceans, rivers 
> and lakes. Water systems are of vital importance to climate 
> regulation, agriculture, nutrient production, oil retrieval 
> and transportation, etc., yet they represent one of the least 
> explored frontiers. As such, there is significant interest 
> in real-time, in-situ monitoring of aquatic environments for 
> scientific, environmental, commercial, safety and military 
> applications.
> 
> Underwater networking has attracted strong attention in the 
> recent a few years. Although there is a long history of 
> underwater acoustic communication, many new applications 
> requires networking of multiple nodes, either static or mobile, 
> and potentially over multiple hops. The physical challenges of 
> acoustic channel and the complexity of diverse aquatic environments 
> require us to completely re-think network design for underwater 
> environments. Some major challenges at the physical layer and 
> higher layers include the severely limited range-dependent 
> bandwidth and attenuation, extensive time-varying multi-path 
> propagation, the low speed of sound in water that is 5 orders 
> of magnitude less than that of radio waves in air. In addition, 
> underwater nodes are neither inexpensive nor easy to deploy. 
> These distinct features yield grand challenges to every layer 
> of the protocol suite in underwater networks.
> 
> The goal of the workshop is to bring together researchers and 
> practitioners in areas relevant to underwater networks. Thus, 
> all layers of the protocol stack, from the physical layer to 
> application, will be represented. Its objective is to serve 
> as a forum for presenting state of the art research, exchanging 
> ideas and experiences, and facilitating interaction and collaboration.
> The workshop will span one day, including presentations of 
> technical papers, keynote speeches, and a poster/demo session. 
> Submissions for technical papers should describe original research, 
> not published or currently under review for other workshops, 
> conferences, or journals.  
>  
> Topics include, but are not limited to:
> 
> - Network architecture design 
> - Efficient acoustic communications
> - Cooperative underwater communications
> - Medium access control
> - Routing and forwarding
> - Reliable data transfer
> - Security and robustness
> - In-network data storage
> - Resource management (energy, bandwidth) 
> - Localization and time synchronization
> - Data fusion, dissemination, tracking
> - Network modeling and simulations
> - Network planning and deployment
> - New applications utilizing underwater networks
> - Testbed and systems: real-world experience
> 
> 
> Submission Guidelines
> *********************
> 
> The workshop accepts both regular full papers and short papers. 
> Short papers present new ideas or new visions that may influence 
> the direction of future research, yet they may be less mature 
> than full papers. While an exhaustive evaluation of the proposed 
> ideas is not necessary, insight and in-depth understanding of 
> the issues is expected. Short papers will be reviewed the same 
> way as full papers by the technical program committee and will 
> be published in the workshop proceedings.
> 
> All paper submissions will be handled electronically. Authors 
> should prepare a PDF or PostScript version of their papers. 
> The page limit for full papers is 8 pages, and that for short 
> papers is 4 pages. Both types of papers should be submitted 
> using the same submission procedure. However, the title of 
> short papers must start with the word "Short Papers:", i.e., 
> "Short Papers: Rest of the Title." All papers should use font 
> size that is not smaller than 10 points, and must fit properly 
> on US letter-sized paper (8.5x11 inches) with 1-inch margins. 
> Detailed instructions on the paper submission procedure and 
> format will be available on the workshop web pages.
> 
> Submitted papers will be judged based on their quality and 
> novelty through a rigorous peer-reviewing process. All accepted 
> papers will appear in the workshop proceedings. Some papers that 
> cannot be included in the main workshop program may be accepted 
> as extended abstracts. If the authors agree, these papers will 
> be included in the proceedings as 2-page extended abstracts and 
> will be presented at the workshop in a poster session. The call 
> for posters and demos will be announced separately.
> 
> 
> Important dates (Tentative)
> ***************************
> 
> Submission deadline: May 9, 2008
> Acceptance notification: June 19, 2008 
> Camera-ready version due: July 7, 2008
> Workshop date: September 15, 2008
> 
> 
> Workshop Organizing Committee
> *****************************
> 
> General Chair: 
> 
> Milica Stojanovic (MIT/WHOI)
> 
> Technical Program Co-Chairs:
> 
> Phil Schniter (The Ohio State University) 
> Wei Ye (University of Southern California)
> 
> WUWNet Steering Committee: 
> 
> Ian F. Akyildiz (Georgia Institute of Technology)
> Jun-Hong Cui (University of Connecticut, Chair) 
> David Hung-Chang Du (University of Minnesota)
> Kevin Fall (Intel Research, Berkeley)
> Robert H. Headrick (Office of Naval Research)
> John Heidemann (University of Southern California)
> Urbashi Mitra (University of Southern California)
> Milica Stojanovic (MIT/WHOI)
> 
> Posters/Demos and Awards Chair:
> 
> Shengli Zhou (University of Connecticut)
> 
> Finance Chair:
>  
> Payman Arabshahi (University of Washington)
> 
> Publicity/Publications Chair:
> 
> Dario Pompili (Rutgers, The State University of New Jersey)
> 
> Local Arrangements and Registration Co-Chairs:
> 
> Quiliang Liang (University of Texas at Arlington)
> Shu Xiao (Cisco, Inc.) 
> 
> 
> Technical Program Committee (incomplete)
> ****************************************
> 
> Payman Arabshahi (University of Washington)
> Mandar Chitre (National University of Singapore)
> Jun-Hong Cui (University of Connecticut)
> Tolga Duman (Arizona State University)
> Kevin Fall (Intel Research, Berkeley)
> Lee Freitag (Woods Hole Oceanographic Institution)
> Joao Pedro Gomes (Universidade Tecnica de Lisboa)
> John Heidemann (University of Southern California)
> Dan Kilfoyle (Science Applications International Corporation)
> Scott Midkiff (Virginia Tech/NSF)
> Urbashi Mitra (University of Southern California)
> Mehul Motani (National University of Singapore)
> Dario Pompili (Rutgers, The State University of New Jersey)
> Robert Qiu (Tennessee Technological University)
> Volkan Rodoplu (University of California, Santa Barbara)
> Daniel Rouseff (Applied Physics Lab, University of Washington)
> Daniela Rus (Massachusetts Institute of Technology)
> Curt Schurgers (University of California, San Diego)
> Geoffrey Xie (Naval Postgraduate School)
> Michele Zorzi (University of Padova, Italy)
> 
> 
> 
> ------------------------------------------------------------------
> Dario Pompili, Ph.D.
> Assistant Professor
> Department of Electrical & Computer Engineering
> CoRE Building - Room 615
> Rutgers, The State University of New Jersey
> 96 Frelinghuysen Road, Piscataway, NJ 08854
> Phone: (732) 445-6400 ext. 202
> Fax: (732) 445-0593
> Email1: pompili@ece.rutgers.edu
> Email2: pompili@caip.rutgers.edu
> WWW: http://www.ece.rutgers.edu/~pompili
> ------------------------------------------------------------------- 
> 

------=_NextPart_000_00AC_01C89C27.6DBBF030
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7036.0">
<TITLE>CFP: The Third ACM International Workshop on UnderWater Networks =
(WUWNet 2008)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 =
FACE=3D"Arial">-----------------------------------------------------</FON=
T>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The =
Third ACM International Workshop on</FONT>

<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
UnderWater Networks (WUWNet 2008)</FONT>

<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</FONT><A HREF=3D"http://wuwnet08.engr.uconn.edu/"><U><FONT =
COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://wuwnet08.engr.uconn.edu/</FONT></U></A>
</P>

<P><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In conjunction =
with ACM MobiCom 2008</FONT>

<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; September 15, 2008</FONT>

<BR><FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; San Francisco, California, USA</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Sponsored by ACM SIGMOBILE and IEEE OES</FONT>

<BR><FONT SIZE=3D2 =
FACE=3D"Arial">-----------------------------------------------------</FON=
T>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Overview &amp; Scope&nbsp;&nbsp; =
</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">****************</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Water covers 71% of the earth's surface =
with oceans, rivers </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">and lakes. Water systems are of vital =
importance to climate </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">regulation, agriculture, nutrient =
production, oil retrieval </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">and transportation, etc., yet they =
represent one of the least </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">explored frontiers. As such, there is =
significant interest </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">in real-time, in-situ monitoring of =
aquatic environments for </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">scientific, environmental, commercial, =
safety and military </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">applications.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Underwater networking has attracted =
strong attention in the </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">recent a few years. Although there is =
a long history of </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">underwater acoustic communication, =
many new applications </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">requires networking of multiple nodes, =
either static or mobile, </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">and potentially over multiple hops. =
The physical challenges of </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">acoustic channel and the complexity of =
diverse aquatic environments </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">require us to completely re-think =
network design for underwater </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">environments. Some major challenges at =
the physical layer and </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">higher layers include the severely =
limited range-dependent </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">bandwidth and attenuation, extensive =
time-varying multi-path </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">propagation, the low speed of sound in =
water that is 5 orders </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">of magnitude less than that of radio =
waves in air. In addition, </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">underwater nodes are neither =
inexpensive nor easy to deploy. </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">These distinct features yield grand =
challenges to every layer </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">of the protocol suite in underwater =
networks.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The goal of the workshop is to bring =
together researchers and </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">practitioners in areas relevant to =
underwater networks. Thus, </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">all layers of the protocol stack, from =
the physical layer to </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">application, will be represented. Its =
objective is to serve </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">as a forum for presenting state of the =
art research, exchanging </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">ideas and experiences, and =
facilitating interaction and collaboration.</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">The workshop will span one day, =
including presentations of </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">technical papers, keynote speeches, =
and a poster/demo session. </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Submissions for technical papers =
should describe original research, </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">not published or currently under =
review for other workshops, </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">conferences, or journals.&nbsp; =
</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Topics include, but are not limited =
to:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">- Network architecture design </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">- Efficient acoustic =
communications</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">- Cooperative underwater =
communications</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">- Medium access control</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">- Routing and forwarding</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">- Reliable data transfer</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">- Security and robustness</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">- In-network data storage</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">- Resource management (energy, =
bandwidth) </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">- Localization and time =
synchronization</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">- Data fusion, dissemination, =
tracking</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">- Network modeling and =
simulations</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">- Network planning and =
deployment</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">- New applications utilizing =
underwater networks</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">- Testbed and systems: real-world =
experience</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Submission Guidelines</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">*********************</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The workshop accepts both regular full =
papers and short papers. </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Short papers present new ideas or new =
visions that may influence </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">the direction of future research, yet =
they may be less mature </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">than full papers. While an exhaustive =
evaluation of the proposed </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">ideas is not necessary, insight and =
in-depth understanding of </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">the issues is expected. Short papers =
will be reviewed the same </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">way as full papers by the technical =
program committee and will </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">be published in the workshop =
proceedings.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">All paper submissions will be handled =
electronically. Authors </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">should prepare a PDF or PostScript =
version of their papers. </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">The page limit for full papers is 8 =
pages, and that for short </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">papers is 4 pages. Both types of =
papers should be submitted </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">using the same submission procedure. =
However, the title of </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">short papers must start with the word =
&quot;Short Papers:&quot;, i.e., </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&quot;Short Papers: Rest of the =
Title.&quot; All papers should use font </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">size that is not smaller than 10 =
points, and must fit properly </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">on US letter-sized paper (8.5x11 =
inches) with 1-inch margins. </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Detailed instructions on the paper =
submission procedure and </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">format will be available on the =
workshop web pages.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Submitted papers will be judged based =
on their quality and </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">novelty through a rigorous =
peer-reviewing process. All accepted </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">papers will appear in the workshop =
proceedings. Some papers that </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">cannot be included in the main =
workshop program may be accepted </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">as extended abstracts. If the authors =
agree, these papers will </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">be included in the proceedings as =
2-page extended abstracts and </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">will be presented at the workshop in a =
poster session. The call </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">for posters and demos will be =
announced separately.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Important dates (Tentative)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">***************************</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Submission deadline: May 9, 2008</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Acceptance notification: June 19, 2008 =
</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Camera-ready version due: July 7, =
2008</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Workshop date: September 15, =
2008</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Workshop Organizing Committee</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">*****************************</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">General Chair: </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Milica Stojanovic (MIT/WHOI)</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Technical Program Co-Chairs:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Phil Schniter (The Ohio State =
University) </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Wei Ye (University of Southern =
California)</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">WUWNet Steering Committee: </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Ian F. Akyildiz (Georgia Institute of =
Technology)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Jun-Hong Cui (University of =
Connecticut, Chair) </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">David Hung-Chang Du (University of =
Minnesota)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Kevin Fall (Intel Research, =
Berkeley)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Robert H. Headrick (Office of Naval =
Research)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">John Heidemann (University of Southern =
California)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Urbashi Mitra (University of Southern =
California)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Milica Stojanovic (MIT/WHOI)</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Posters/Demos and Awards Chair:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Shengli Zhou (University of =
Connecticut)</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Finance Chair:</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Payman Arabshahi (University of =
Washington)</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Publicity/Publications Chair:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Dario Pompili (Rutgers, The State =
University of New Jersey)</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Local Arrangements and Registration =
Co-Chairs:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Quiliang Liang (University of Texas at =
Arlington)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Shu Xiao (Cisco, Inc.) </FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Technical Program Committee =
(incomplete)</FONT>

<BR><FONT SIZE=3D2 =
FACE=3D"Arial">****************************************</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Payman Arabshahi (University of =
Washington)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Mandar Chitre (National University of =
Singapore)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Jun-Hong Cui (University of =
Connecticut)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Tolga Duman (Arizona State =
University)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Kevin Fall (Intel Research, =
Berkeley)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Lee Freitag (Woods Hole Oceanographic =
Institution)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Joao Pedro Gomes (Universidade Tecnica =
de Lisboa)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">John Heidemann (University of Southern =
California)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Dan Kilfoyle (Science Applications =
International Corporation)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Scott Midkiff (Virginia =
Tech/NSF)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Urbashi Mitra (University of Southern =
California)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Mehul Motani (National University of =
Singapore)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Dario Pompili (Rutgers, The State =
University of New Jersey)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Robert Qiu (Tennessee Technological =
University)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Volkan Rodoplu (University of =
California, Santa Barbara)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Daniel Rouseff (Applied Physics Lab, =
University of Washington)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Daniela Rus (Massachusetts Institute =
of Technology)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Curt Schurgers (University of =
California, San Diego)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Geoffrey Xie (Naval Postgraduate =
School)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Michele Zorzi (University of Padova, =
Italy)</FONT>
</P>
<BR>
<BR>

<P><SPAN LANG=3D"it"><FONT =
FACE=3D"Arial">----------------------------------------------------------=
--------</FONT></SPAN>

<BR><SPAN LANG=3D"it"><FONT FACE=3D"Arial">Dario Pompili, =
Ph.D.</FONT></SPAN>

<BR><SPAN LANG=3D"it"><FONT FACE=3D"Arial">Assistant =
Professor</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT FACE=3D"Arial">Department of Electrical =
&amp; Computer Engineering</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT FACE=3D"Arial">CoRE Building - Room =
615</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT FACE=3D"Arial">Rutgers, The State =
University of New Jersey</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT FACE=3D"Arial">96 Frelinghuysen Road, =
Piscataway, NJ 08854</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT FACE=3D"Arial">Phone: (732) 445-6400 ext. =
202</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT FACE=3D"Arial">Fax: (732) =
445-0593</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT FACE=3D"Arial">Email1: =
pompili@ece.rutgers.edu</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT FACE=3D"Arial">Email2: =
pompili@caip.rutgers.edu</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT FACE=3D"Arial">WWW: </FONT></SPAN><A =
HREF=3D"http://www.ece.rutgers.edu/~pompili"><SPAN =
LANG=3D"en-us"><U><FONT COLOR=3D"#0000FF" =
FACE=3D"Arial">http://www.ece.rutgers.edu/~pompili</FONT></U></SPAN></A><=
SPAN LANG=3D"en-us"></SPAN>

<BR><SPAN LANG=3D"it"><FONT =
FACE=3D"Arial">----------------------------------------------------------=
---------</FONT></SPAN><SPAN LANG=3D"en-us"><FONT =
FACE=3D"Arial">=A0</FONT></SPAN><SPAN LANG=3D"it"></SPAN>
</P>

</BODY>
</HTML>
------=_NextPart_000_00AC_01C89C27.6DBBF030--


--===============1138828241==
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/

--===============1138828241==--



From mip4-bounces@ietf.org  Mon Apr 21 01:48:06 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4F47C3A6D98;
	Mon, 21 Apr 2008 01:48:06 -0700 (PDT)
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 829743A6F15
	for <mip4@core3.amsl.com>; Mon, 21 Apr 2008 01:48:05 -0700 (PDT)
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 mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SlXkCmF0eLIR for <mip4@core3.amsl.com>;
	Mon, 21 Apr 2008 01:48:04 -0700 (PDT)
Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.229])
	by core3.amsl.com (Postfix) with ESMTP id 4602D3A6CE7
	for <mip4@ietf.org>; Mon, 21 Apr 2008 01:48:04 -0700 (PDT)
Received: by wr-out-0506.google.com with SMTP id 50so677603wra.13
	for <mip4@ietf.org>; Mon, 21 Apr 2008 01:48:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=kFsXbbpyPN49T8lD6Gr4PmxJrmmewFxoJVT+gXi8VfU=;
	b=pO5OixRm/6a5QFXFzYB7lW0Vd+9WOA4sgVmCrhtBU4thqDlX+n5cHznEcjwfml3AfkhFUycnIgX33OCx1tOLBhNTvZbGW8afcCNZhqZVzHqoFtmfASBm+MvvasgS+EPql9UIrwzj1GaYsw8gBJr7sXYIWvFcq+yUXY8alS/zBV8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=ZR2COfSQk3B7uGU8QIJ+Qyd/8WpclSbw2BLiuXFq1sfEcPWSNdiV38yBTHF2y/AMa7bUkQaPxjZ11JwrXaVGSUJN+HCGdzhy88eqeVdTRBUMZVEi5jagxfDD+Vu/6Wcu9O2xu04UMAyjyOVHT3C+QoeL3ZgjaC5nZvZaP1dIiLE=
Received: by 10.142.144.16 with SMTP id r16mr1608013wfd.97.1208767689198;
	Mon, 21 Apr 2008 01:48:09 -0700 (PDT)
Received: by 10.142.177.9 with HTTP; Mon, 21 Apr 2008 01:48:09 -0700 (PDT)
Message-ID: <d3886a520804210148n51918d3bgc786f069c7e15395@mail.gmail.com>
Date: Mon, 21 Apr 2008 09:48:09 +0100
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "McCann Peter-A001034" <pete.mccann@motorola.com>
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD130272ABAE@de01exm67.ds.mot.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <AciWd5/DNuCke2dhQBqVWbOvHrpBxQ==>
	<BE4B07D4197BF34EB3B753DD34EBCD130272ABAE@de01exm67.ds.mot.com>
Cc: mip4@ietf.org, henrik@levkowetz.com
Subject: Re: [Mip4] WGLC: 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: <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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Just over the two weeks WGLC notice but for what is worth:

   "I support the advancement of this document to the IESG with a
    request for publication as a Proposed Standard RFC."

Regards
George

On Fri, Apr 4, 2008 at 6:16 PM, McCann Peter-A001034
<pete.mccann@motorola.com> wrote:
> This message announces a 2-week working group last call on:
>
>  "Generic Notification Message for Mobile IPv4"
>  draft-ietf-mip4-generic-notification-message-04.txt
>
>  The last call will end at 24:00 UTC on Friday, April 18 2008.
>
>  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
>
>
>  Please respond to this working group last call:
>
>  * If you have no comments on the draft, and support its advancement,
>   simply respond with a line containing something like
>
>     "I support the advancement of this document to the IESG with a
>      request for publication as a Proposed Standard RFC."
>
>    If you have comments, please use a line similar to the one above,
>    and supplement this with your comments.
>
>
>  * If you *don't* support its advancement, respond with a line
>   containing something like the following, supplemented by your
>   comments -
>
>     "I don't support the advancement of this document to the IESG with
>      a request for publication as a Proposed Standard RFC, for the
>      following reasons:"
>     ...
>
>  Please direct all replies to the Mobile IPv4 mailing list,
>  mip4@ietf.org.
>
>
>  -Pete
>  --
>  Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>  Supplemental site: http://www.mip4.org/
>
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Wed Apr 23 16:47:21 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7141228C311;
	Wed, 23 Apr 2008 16:47:21 -0700 (PDT)
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 4A48C3A6C9F;
	Wed, 23 Apr 2008 16:47:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.269
X-Spam-Level: 
X-Spam-Status: No, score=-17.269 tagged_above=-999 required=5
	tests=[AWL=-0.270, BAYES_00=-2.599, J_CHICKENPOX_93=0.6,
	USER_IN_DEF_WHITELIST=-15]
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 GMeWl361+g1A; Wed, 23 Apr 2008 16:47:15 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207])
	by core3.amsl.com (Postfix) with ESMTP id 806BC3A6D00;
	Wed, 23 Apr 2008 16:47:15 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70)
	id 5C847125D14; Wed, 23 Apr 2008 16:47:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20080423234721.5C847125D14@bosco.isi.edu>
Date: Wed, 23 Apr 2008 16:47:21 -0700 (PDT)
Cc: mip4@ietf.org, rfc-editor@rfc-editor.org
Subject: [Mip4] RFC 5177 on Network Mobility (NEMO) Extensions for Mobile
	IPv4
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>
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


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5177

        Title:      Network Mobility (NEMO) Extensions for 
                    Mobile IPv4 
        Author:     K. Leung, G. Dommety,
                    V. Narayanan, A. Petrescu
        Status:     Standards Track
        Date:       April 2008
        Mailbox:    kleung@cisco.com, 
                    gdommety@cisco.com, 
                    vidyan@qualcomm.com,
                    alexandru.petrescu@motorola.com
        Pages:      26
        Characters: 56094
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mip4-nemo-v4-base-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5177.txt

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.
[STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


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


From mip4-bounces@ietf.org  Thu Apr 24 02:52:47 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 02AA83A692A;
	Thu, 24 Apr 2008 02:52:47 -0700 (PDT)
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 8AA853A67A3
	for <mip4@core3.amsl.com>; Thu, 24 Apr 2008 02:52:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level: 
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5
	tests=[AWL=-0.225, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622,
	J_CHICKENPOX_93=0.6]
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 ATaGFp4re7wP for <mip4@core3.amsl.com>;
	Thu, 24 Apr 2008 02:52:44 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.169])
	by core3.amsl.com (Postfix) with ESMTP id 7E89B3A693D
	for <mip4@ietf.org>; Thu, 24 Apr 2008 02:52:44 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 25so2466032wfa.31
	for <mip4@ietf.org>; Thu, 24 Apr 2008 02:52:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=Ugs6OjYxF4GAUV8EC+0QHGomCkCKXUO5jq5saIBbNLg=;
	b=IyAAFb7ZH3CtYnwyEp8KP9ADLpEYpXSFcV+bntW9F3Qe4MnP30pNDcl+sheZGOkingmBduIjaldSgSKJlBvba+YReWifkIWe5X+DhsBtfmJwOGyXhI2+SoLKNCDEAnhmH2sNzh9Rsqpy67otMVFYXGetO1cgoNmojLNMCYoCKrg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=RlQgKu4WF6N/AY5k6d+zs+Y3Jl3/B66CyA9v6qjt3H9mwEYDOgcp/D0H6Nvhnqkun+GngO4Egz1diCrplf50m67lp4lo7VROFnRg/3/uE17q6bl2Mz4WGgIB/lqQJVVQZGEpeHMnLZOzUD/CsgjZrSb8HwLBJyRcJXimelsRODY=
Received: by 10.142.106.18 with SMTP id e18mr169289wfc.33.1209030769941;
	Thu, 24 Apr 2008 02:52:49 -0700 (PDT)
Received: by 10.142.177.9 with HTTP; Thu, 24 Apr 2008 02:52:49 -0700 (PDT)
Message-ID: <d3886a520804240252k69507066gb0c652704829bcaf@mail.gmail.com>
Date: Thu, 24 Apr 2008 10:52:49 +0100
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: mip4@ietf.org
In-Reply-To: <20080423234721.5C847125D14@bosco.isi.edu>
MIME-Version: 1.0
Content-Disposition: inline
References: <20080423234721.5C847125D14@bosco.isi.edu>
Subject: Re: [Mip4] RFC 5177 on Network Mobility (NEMO) Extensions for
	Mobile IPv4
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi all,

Now that NEMOv4-base is outof the way, how about starting the process
for http://tools.ietf.org/html/draft-ietf-mip4-nemov4-fa-02 ?


Regards
George

On Thu, Apr 24, 2008 at 12:47 AM,  <rfc-editor@rfc-editor.org> wrote:
>
>  A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 5177
>
>         Title:      Network Mobility (NEMO) Extensions for
>                     Mobile IPv4
>         Author:     K. Leung, G. Dommety,
>                     V. Narayanan, A. Petrescu
>         Status:     Standards Track
>         Date:       April 2008
>         Mailbox:    kleung@cisco.com,
>                     gdommety@cisco.com,
>                     vidyan@qualcomm.com,
>                     alexandru.petrescu@motorola.com
>         Pages:      26
>         Characters: 56094
>         Updates/Obsoletes/SeeAlso:   None
>
>         I-D Tag:    draft-ietf-mip4-nemo-v4-base-11.txt
>
>         URL:        http://www.rfc-editor.org/rfc/rfc5177.txt
>
>  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.
>  [STANDARDS TRACK]
>
>  This document is a product of the Mobility for IPv4 Working Group of the IETF.
>
>  This is now a Proposed Standard Protocol.
>
>  STANDARDS TRACK: This document specifies an Internet standards track
>  protocol for the Internet community,and requests discussion and suggestions
>  for improvements.  Please refer to the current edition of the Internet
>  Official Protocol Standards (STD 1) for the standardization state and
>  status of this protocol.  Distribution of this memo is unlimited.
>
>  This announcement is sent to the IETF list and the RFC-DIST list.
>  Requests to be added to or deleted from the IETF distribution list
>  should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
>  added to or deleted from the RFC-DIST distribution list should
>  be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>
>  Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>  an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
>
>  help: ways_to_get_rfcs. For example:
>
>         To: rfc-info@RFC-EDITOR.ORG
>         Subject: getting rfcs
>
>         help: ways_to_get_rfcs
>
>  Requests for special distribution should be addressed to either the
>  author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
>  specifically noted otherwise on the RFC itself, all RFCs are for
>  unlimited distribution.
>
>  Submissions for Requests for Comments should be sent to
>  RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
>  Authors, for further information.
>
>
>  The RFC Editor Team
>  USC/Information Sciences Institute
>
>  ...
>
>
>  _______________________________________________
>  IETF-Announce mailing list
>  IETF-Announce@ietf.org
>  https://www.ietf.org/mailman/listinfo/ietf-announce
>
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Thu Apr 24 03:04:27 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CFE0D3A68B8;
	Thu, 24 Apr 2008 03:04:27 -0700 (PDT)
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 34FD83A67A3
	for <mip4@core3.amsl.com>; Thu, 24 Apr 2008 03:04:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5
	tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_93=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YN7xI4-rlZt9 for <mip4@core3.amsl.com>;
	Thu, 24 Apr 2008 03:04:25 -0700 (PDT)
Received: from mail128.messagelabs.com (mail128.messagelabs.com
	[216.82.250.131])
	by core3.amsl.com (Postfix) with SMTP id E6FB43A68B8
	for <mip4@ietf.org>; Thu, 24 Apr 2008 03:04:24 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-12.tower-128.messagelabs.com!1209031469!17591643!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [144.189.100.103]
Received: (qmail 20452 invoked from network); 24 Apr 2008 10:04:29 -0000
Received: from motgate3.mot.com (HELO motgate3.mot.com) (144.189.100.103)
	by server-12.tower-128.messagelabs.com with SMTP;
	24 Apr 2008 10:04:29 -0000
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate3.mot.com (8.12.11/Motorola) with ESMTP id m3OA4Tnf025977;
	Thu, 24 Apr 2008 03:04:29 -0700 (MST)
Received: from az10vts01 (az10vts01.mot.com [10.64.251.242])
	by az33exr01.mot.com (8.13.1/Vontu) with SMTP id m3OA4Sxe012298;
	Thu, 24 Apr 2008 05:04:28 -0500 (CDT)
Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id m3OA4QJB012163;
	Thu, 24 Apr 2008 05:04:26 -0500 (CDT)
Message-ID: <48105B1F.3030102@gmail.com>
Date: Thu, 24 Apr 2008 12:04:15 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: George Tsirtsis <tsirtsis@googlemail.com>
References: <20080423234721.5C847125D14@bosco.isi.edu>
	<d3886a520804240252k69507066gb0c652704829bcaf@mail.gmail.com>
In-Reply-To: <d3886a520804240252k69507066gb0c652704829bcaf@mail.gmail.com>
X-Antivirus: avast! (VPS 080423-1, 23/04/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
Cc: mip4@ietf.org
Subject: Re: [Mip4] RFC 5177 on Network Mobility (NEMO) Extensions
 for	Mobile IPv4
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: 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,
> 
> Now that NEMOv4-base is outof the way, how about starting the process
> for http://tools.ietf.org/html/draft-ietf-mip4-nemov4-fa-02 ?

Not sure whether you request procedural advancement or technical discussion.

Technically, I think there's need of some more syncing on FA-NEMO docs, 
eg citing numbers already allocated, ordering between different mobile 
network extensions, and maybe other things.  The Sec section could say 
how new risks are introduced by th etunnelling extension and how 
protection is offered.  3.1 background could picture a figure or two of 
tunnels.  Just some thoughts...

Alex

> 
> 
> Regards
> George
> 
> On Thu, Apr 24, 2008 at 12:47 AM,  <rfc-editor@rfc-editor.org> wrote:
>>  A new Request for Comments is now available in online RFC libraries.
>>
>>
>>         RFC 5177
>>
>>         Title:      Network Mobility (NEMO) Extensions for
>>                     Mobile IPv4
>>         Author:     K. Leung, G. Dommety,
>>                     V. Narayanan, A. Petrescu
>>         Status:     Standards Track
>>         Date:       April 2008
>>         Mailbox:    kleung@cisco.com,
>>                     gdommety@cisco.com,
>>                     vidyan@qualcomm.com,
>>                     alexandru.petrescu@motorola.com
>>         Pages:      26
>>         Characters: 56094
>>         Updates/Obsoletes/SeeAlso:   None
>>
>>         I-D Tag:    draft-ietf-mip4-nemo-v4-base-11.txt
>>
>>         URL:        http://www.rfc-editor.org/rfc/rfc5177.txt
>>
>>  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.
>>  [STANDARDS TRACK]
>>
>>  This document is a product of the Mobility for IPv4 Working Group of the IETF.
>>
>>  This is now a Proposed Standard Protocol.
>>
>>  STANDARDS TRACK: This document specifies an Internet standards track
>>  protocol for the Internet community,and requests discussion and suggestions
>>  for improvements.  Please refer to the current edition of the Internet
>>  Official Protocol Standards (STD 1) for the standardization state and
>>  status of this protocol.  Distribution of this memo is unlimited.
>>
>>  This announcement is sent to the IETF list and the RFC-DIST list.
>>  Requests to be added to or deleted from the IETF distribution list
>>  should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
>>  added to or deleted from the RFC-DIST distribution list should
>>  be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>>
>>  Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>>  an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
>>
>>  help: ways_to_get_rfcs. For example:
>>
>>         To: rfc-info@RFC-EDITOR.ORG
>>         Subject: getting rfcs
>>
>>         help: ways_to_get_rfcs
>>
>>  Requests for special distribution should be addressed to either the
>>  author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
>>  specifically noted otherwise on the RFC itself, all RFCs are for
>>  unlimited distribution.
>>
>>  Submissions for Requests for Comments should be sent to
>>  RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
>>  Authors, for further information.
>>
>>
>>  The RFC Editor Team
>>  USC/Information Sciences Institute
>>
>>  ...
>>
>>
>>  _______________________________________________
>>  IETF-Announce mailing list
>>  IETF-Announce@ietf.org
>>  https://www.ietf.org/mailman/listinfo/ietf-announce
>>


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


From mip4-bounces@ietf.org  Thu Apr 24 03:09:51 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C3F913A68D3;
	Thu, 24 Apr 2008 03:09:51 -0700 (PDT)
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 5BAA13A67E1
	for <mip4@core3.amsl.com>; Thu, 24 Apr 2008 03:09:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.527
X-Spam-Level: 
X-Spam-Status: No, score=-1.527 tagged_above=-999 required=5
	tests=[AWL=-0.150, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622,
	J_CHICKENPOX_93=0.6]
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 twGvHuv5Rhmy for <mip4@core3.amsl.com>;
	Thu, 24 Apr 2008 03:09:49 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.173])
	by core3.amsl.com (Postfix) with ESMTP id 463443A69D2
	for <mip4@ietf.org>; Thu, 24 Apr 2008 03:09:49 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 25so2472157wfa.31
	for <mip4@ietf.org>; Thu, 24 Apr 2008 03:09:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=+SuExlvgQ6zdO1aO/MBAcoiBrjXguZTry0kDb0wWSCo=;
	b=HTTlNSPrih7S92Z0c1aOwvbbDWcLKjHrhO0uIhkeoTDxwhiYBGhP6q9E0Vlk0HQ7639kmBCh5UUGmrlrcoz38h266FyA0awIFTBiYS/6zncXZqg/+DEDERKiK9PZtLXFpG+q6bjtUf5Prv1IU7MDGpbm12EetAZ/3FH9vDZsvKw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=XHEQ4xbMXjPcC4H93JfcIV/WsgtW4rjNb4Jk0f8b/qSjyO31N6hNTEz892oY7RyhjXvC1i+jFPBAXNh5fHkYXhIVcu2lXk++49jIcmiR5zQwf/Pg0Y1gKIo4HU5fH1ZWVvIUVl/ZFoCOe6RHxOy5SnMGJflpZRuyzLxEooq35G4=
Received: by 10.142.141.21 with SMTP id o21mr494408wfd.56.1209031794682;
	Thu, 24 Apr 2008 03:09:54 -0700 (PDT)
Received: by 10.142.177.9 with HTTP; Thu, 24 Apr 2008 03:09:54 -0700 (PDT)
Message-ID: <d3886a520804240309p1379b3adv35a2f109f5132afb@mail.gmail.com>
Date: Thu, 24 Apr 2008 11:09:54 +0100
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Alexandru Petrescu" <alexandru.petrescu@gmail.com>
In-Reply-To: <48105B1F.3030102@gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <20080423234721.5C847125D14@bosco.isi.edu>
	<d3886a520804240252k69507066gb0c652704829bcaf@mail.gmail.com>
	<48105B1F.3030102@gmail.com>
Cc: mip4@ietf.org
Subject: Re: [Mip4] RFC 5177 on Network Mobility (NEMO) Extensions for
	Mobile IPv4
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi Alex,

Any feedback is good.

- we should indeed sync up the docs a bit more now that one is stable.
I will do that.
- what new threats do you see with the new tunneling extension?
- not sure I see a reason to do more figures, but if you or someone
puts together some relevant figures I would be ok with including them
in the draft.

Thanks
George

On Thu, Apr 24, 2008 at 11:04 AM, Alexandru Petrescu
<alexandru.petrescu@gmail.com> wrote:
> George Tsirtsis wrote:
>
> > Hi all,
> >
> > Now that NEMOv4-base is outof the way, how about starting the process
> > for http://tools.ietf.org/html/draft-ietf-mip4-nemov4-fa-02 ?
> >
>
>  Not sure whether you request procedural advancement or technical
> discussion.
>
>  Technically, I think there's need of some more syncing on FA-NEMO docs, eg
> citing numbers already allocated, ordering between different mobile network
> extensions, and maybe other things.  The Sec section could say how new risks
> are introduced by th etunnelling extension and how protection is offered.
> 3.1 background could picture a figure or two of tunnels.  Just some
> thoughts...
>
>  Alex
>
>
>
>
> >
> >
> > Regards
> > George
> >
> > On Thu, Apr 24, 2008 at 12:47 AM,  <rfc-editor@rfc-editor.org> wrote:
> >
> > >  A new Request for Comments is now available in online RFC libraries.
> > >
> > >
> > >        RFC 5177
> > >
> > >        Title:      Network Mobility (NEMO) Extensions for
> > >                    Mobile IPv4
> > >        Author:     K. Leung, G. Dommety,
> > >                    V. Narayanan, A. Petrescu
> > >        Status:     Standards Track
> > >        Date:       April 2008
> > >        Mailbox:    kleung@cisco.com,
> > >                    gdommety@cisco.com,
> > >                    vidyan@qualcomm.com,
> > >                    alexandru.petrescu@motorola.com
> > >        Pages:      26
> > >        Characters: 56094
> > >        Updates/Obsoletes/SeeAlso:   None
> > >
> > >        I-D Tag:    draft-ietf-mip4-nemo-v4-base-11.txt
> > >
> > >        URL:        http://www.rfc-editor.org/rfc/rfc5177.txt
> > >
> > >  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.
> > >  [STANDARDS TRACK]
> > >
> > >  This document is a product of the Mobility for IPv4 Working Group of
> the IETF.
> > >
> > >  This is now a Proposed Standard Protocol.
> > >
> > >  STANDARDS TRACK: This document specifies an Internet standards track
> > >  protocol for the Internet community,and requests discussion and
> suggestions
> > >  for improvements.  Please refer to the current edition of the Internet
> > >  Official Protocol Standards (STD 1) for the standardization state and
> > >  status of this protocol.  Distribution of this memo is unlimited.
> > >
> > >  This announcement is sent to the IETF list and the RFC-DIST list.
> > >  Requests to be added to or deleted from the IETF distribution list
> > >  should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
> > >  added to or deleted from the RFC-DIST distribution list should
> > >  be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
> > >
> > >  Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
> > >  an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
> > >
> > >  help: ways_to_get_rfcs. For example:
> > >
> > >        To: rfc-info@RFC-EDITOR.ORG
> > >        Subject: getting rfcs
> > >
> > >        help: ways_to_get_rfcs
> > >
> > >  Requests for special distribution should be addressed to either the
> > >  author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.
> Unless
> > >  specifically noted otherwise on the RFC itself, all RFCs are for
> > >  unlimited distribution.
> > >
> > >  Submissions for Requests for Comments should be sent to
> > >  RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to
> RFC
> > >  Authors, for further information.
> > >
> > >
> > >  The RFC Editor Team
> > >  USC/Information Sciences Institute
> > >
> > >  ...
> > >
> > >
> > >  _______________________________________________
> > >  IETF-Announce mailing list
> > >  IETF-Announce@ietf.org
> > >  https://www.ietf.org/mailman/listinfo/ietf-announce
> > >
> > >
> >
>
>
>  ______________________________________________________________________
>  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: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Thu Apr 24 03:27:10 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0CB513A6995;
	Thu, 24 Apr 2008 03:27:10 -0700 (PDT)
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 BE4EE3A6A36
	for <mip4@core3.amsl.com>; Thu, 24 Apr 2008 03:27:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.653
X-Spam-Level: 
X-Spam-Status: No, score=-5.653 tagged_above=-999 required=5
	tests=[AWL=-0.946, BAYES_00=-2.599, J_CHICKENPOX_93=0.6,
	MISSING_HEADERS=1.292, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id h0OBPWon2FuJ for <mip4@core3.amsl.com>;
	Thu, 24 Apr 2008 03:27:06 -0700 (PDT)
Received: from mail119.messagelabs.com (mail119.messagelabs.com
	[216.82.241.179])
	by core3.amsl.com (Postfix) with SMTP id 35A233A6A08
	for <mip4@ietf.org>; Thu, 24 Apr 2008 03:27:06 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-2.tower-119.messagelabs.com!1209032830!21537151!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 18791 invoked from network); 24 Apr 2008 10:27:10 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-2.tower-119.messagelabs.com with SMTP;
	24 Apr 2008 10:27:10 -0000
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id m3OARALI028622
	for <mip4@ietf.org>; Thu, 24 Apr 2008 03:27:10 -0700 (MST)
Received: from il06vts02.mot.com (il06vts02.mot.com [129.188.137.142])
	by il06exr03.mot.com (8.13.1/Vontu) with SMTP id m3OARAot025085
	for <mip4@ietf.org>; Thu, 24 Apr 2008 05:27:10 -0500 (CDT)
Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id m3OAR87M025072
	for <mip4@ietf.org>; Thu, 24 Apr 2008 05:27:09 -0500 (CDT)
Message-ID: <4810607C.6020302@gmail.com>
Date: Thu, 24 Apr 2008 12:27:08 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
CC: mip4@ietf.org
References: <20080423234721.5C847125D14@bosco.isi.edu>	
	<d3886a520804240252k69507066gb0c652704829bcaf@mail.gmail.com>	
	<48105B1F.3030102@gmail.com>
	<d3886a520804240309p1379b3adv35a2f109f5132afb@mail.gmail.com>
In-Reply-To: <d3886a520804240309p1379b3adv35a2f109f5132afb@mail.gmail.com>
X-Antivirus: avast! (VPS 080423-1, 23/04/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
Subject: Re: [Mip4] RFC 5177 on Network Mobility (NEMO) Extensions for
 Mobile IPv4
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

George Tsirtsis wrote:
> Hi Alex,
> 
> Any feedback is good.
> 
> - we should indeed sync up the docs a bit more now that one is
> stable. I will do that. - what new threats do you see with the new
> tunneling extension?

For example what happens if FA requests with the tunneling extension but
the MR prefers it not.

You don't see any threat with the tunneling extension?  MR-FA-HA is a
three-party communication and very much prone to risks.

> - not sure I see a reason to do more figures, but if you or someone 
> puts together some relevant figures I would be ok with including them
>  in the draft.

Thinking about this.  I think the doc has no other figure.  Section 3.1
is way too short and compressed.  When reading, I need to mentally 
picture those tunnels to understand it.  If I had figures in 3.1 my 
reading would be eased.  Maybe I'll provide some figures later.

Alex

> 
> Thanks George
> 
> On Thu, Apr 24, 2008 at 11:04 AM, Alexandru Petrescu 
> <alexandru.petrescu@gmail.com> wrote:
>> George Tsirtsis wrote:
>> 
>>> Hi all,
>>> 
>>> Now that NEMOv4-base is outof the way, how about starting the
>>> process for
>>> http://tools.ietf.org/html/draft-ietf-mip4-nemov4-fa-02 ?
>>> 
>> Not sure whether you request procedural advancement or technical 
>> discussion.
>> 
>> Technically, I think there's need of some more syncing on FA-NEMO
docs, eg
>> citing numbers already allocated, ordering between different mobile
>> 
network
>> extensions, and maybe other things.  The Sec section could say how
new risks
>> are introduced by th etunnelling extension and how protection is
>> offered. 3.1 background could picture a figure or two of tunnels.
>> Just some thoughts...
>> 
>> Alex
>> 
>> 
>> 
>> 
>>> 
>>> Regards George
>>> 
>>> On Thu, Apr 24, 2008 at 12:47 AM,  <rfc-editor@rfc-editor.org>
>>> wrote:
>>> 
>>>> A new Request for Comments is now available in online RFC
>>>> libraries.
>>>> 
>>>> 
>>>> RFC 5177
>>>> 
>>>> Title:      Network Mobility (NEMO) Extensions for Mobile IPv4 
>>>> Author:     K. Leung, G. Dommety, V. Narayanan, A. Petrescu 
>>>> Status:     Standards Track Date:       April 2008 Mailbox:
>>>> kleung@cisco.com, gdommety@cisco.com, vidyan@qualcomm.com, 
>>>> alexandru.petrescu@motorola.com Pages:      26 Characters:
>>>> 56094 Updates/Obsoletes/SeeAlso:   None
>>>> 
>>>> I-D Tag:    draft-ietf-mip4-nemo-v4-base-11.txt
>>>> 
>>>> URL:        http://www.rfc-editor.org/rfc/rfc5177.txt
>>>> 
>>>> 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. [STANDARDS TRACK]
>>>> 
>>>> This document is a product of the Mobility for IPv4 Working
>>>> Group of
>> the IETF.
>>>> This is now a Proposed Standard Protocol.
>>>> 
>>>> STANDARDS TRACK: This document specifies an Internet standards
>>>> track protocol for the Internet community,and requests
>>>> discussion and
>> suggestions
>>>> for improvements.  Please refer to the current edition of the
>>>> Internet Official Protocol Standards (STD 1) for the
>>>> standardization state and status of this protocol.
>>>> Distribution of this memo is unlimited.
>>>> 
>>>> This announcement is sent to the IETF list and the RFC-DIST
>>>> list. Requests to be added to or deleted from the IETF
>>>> distribution list should be sent to IETF-REQUEST@IETF.ORG.
>>>> Requests to be added to or deleted from the RFC-DIST
>>>> distribution list should be sent to
>>>> RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>>>> 
>>>> Details on obtaining RFCs via FTP or EMAIL may be obtained by
>>>> sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the
>>>> message body
>>>> 
>>>> help: ways_to_get_rfcs. For example:
>>>> 
>>>> To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs
>>>> 
>>>> help: ways_to_get_rfcs
>>>> 
>>>> Requests for special distribution should be addressed to either
>>>> the author of the RFC in question, or to
>>>> RFC-Manager@RFC-EDITOR.ORG.
>> Unless
>>>> specifically noted otherwise on the RFC itself, all RFCs are
>>>> for unlimited distribution.
>>>> 
>>>> Submissions for Requests for Comments should be sent to 
>>>> RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223,
>>>> Instructions to
>> RFC
>>>> Authors, for further information.
>>>> 
>>>> 
>>>> The RFC Editor Team USC/Information Sciences Institute
>>>> 
>>>> ...
>>>> 
>>>> 
>>>> _______________________________________________ IETF-Announce
>>>> mailing list IETF-Announce@ietf.org 
>>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>>> 
>>>> 
>> 
>> ______________________________________________________________________
>>  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: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Thu Apr 24 03:31:44 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EABEC3A6A36;
	Thu, 24 Apr 2008 03:31:44 -0700 (PDT)
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 BE8203A6AE9
	for <mip4@core3.amsl.com>; Thu, 24 Apr 2008 03:31:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.49
X-Spam-Level: 
X-Spam-Status: No, score=-1.49 tagged_above=-999 required=5 tests=[AWL=-0.113, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_93=0.6]
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 py2+ld58Wxlv for <mip4@core3.amsl.com>;
	Thu, 24 Apr 2008 03:31:42 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.171])
	by core3.amsl.com (Postfix) with ESMTP id A62DD3A699B
	for <mip4@ietf.org>; Thu, 24 Apr 2008 03:31:42 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 25so2479137wfa.31
	for <mip4@ietf.org>; Thu, 24 Apr 2008 03:31:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=rrp4NG1pTQuU+SUWKp8YPFnOwZW1kyH2GeaN3TL29SQ=;
	b=TlSWHNhYyI1gVI9AImdp3pzTObdXF/T2HjDQX1Z2lQPZcJa0ja8kiJUrNW6M/tclri8/8DZiC/rvGbmFQGgIOJMINz4GTBl2BVb3FhniAWc/nbv0kgT8bgRD9bbxLf6wmQKAsLBNqzQG4docViNofYoHcCS5nD6LDOJthLgi+PY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=wHIVqVPmIwHOuD5vai03OSNCfJ0kJTeqUUOxA6T80JJxbH+ccWcAk7cANIx0HZ/yT1VEMy7dyZmGktrgxLjHY2Q8WXdZeKX4DXtlM6glxV4YcrEWLk9ywBLVsg0fQCeQwVFb5BxTOv9SGXeBWfRN7Tfn2pGXOA7B+kVvD8LmZig=
Received: by 10.142.163.14 with SMTP id l14mr417535wfe.230.1209033107967;
	Thu, 24 Apr 2008 03:31:47 -0700 (PDT)
Received: by 10.142.177.9 with HTTP; Thu, 24 Apr 2008 03:31:47 -0700 (PDT)
Message-ID: <d3886a520804240331s77412af0p3b1b5f831274fe4f@mail.gmail.com>
Date: Thu, 24 Apr 2008 11:31:47 +0100
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
In-Reply-To: <48105FFF.7020904@motorola.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <20080423234721.5C847125D14@bosco.isi.edu>
	<d3886a520804240252k69507066gb0c652704829bcaf@mail.gmail.com>
	<48105B1F.3030102@gmail.com>
	<d3886a520804240309p1379b3adv35a2f109f5132afb@mail.gmail.com>
	<48105FFF.7020904@motorola.com>
Cc: Alexandru Petrescu <alexandru.petrescu@gmail.com>, mip4@ietf.org
Subject: Re: [Mip4] RFC 5177 on Network Mobility (NEMO) Extensions for
	Mobile IPv4
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

On Thu, Apr 24, 2008 at 11:25 AM, Alexandru Petrescu
<alexandru.petrescu@motorola.com> wrote:
> George Tsirtsis wrote:
>
> > Hi Alex,
> >
> > Any feedback is good.
> >
> > - we should indeed sync up the docs a bit more now that one is stable.
> > I will do that.
> > - what new threats do you see with the new tunneling extension?
> >
>
>  For example what happens if FA requests with the tunneling extension but
> the MR prefers it not.
>
>  You don't see any threat with the tunneling extension?  MR-FA-HA is a
> three-party communication and very much prone to risks.
>
>
GT> What I do not see is any threats different from what regular
MIPv4-FA mode offers. Section 5.4 indicates that if the MN uses
colocated mode, then the FA (even if it sets the R flag in the FAA)
must not include a tunneling extension. If the MN uses the FA mode,
however, it is of course up to the FA to decide to terminate handle
IPv6 packets or not. I do not see a problem with that,


>
> > - not sure I see a reason to do more figures, but if you or someone
> > puts together some relevant figures I would be ok with including them
> > in the draft.
> >
>
>  Thinking about this.  I think the doc has no other figure.  Section 3.1 is
> way too short and compressed.  I need to mentally picture those tunnels to
> understand it.  If I had figures in 3.1 my reading would be eased.  Maybe
> I'll provide some figures later.
>

GT> That would be good. Thanks.


>  Alex
>
>
>
>
> >
> > Thanks
> > George
> >
> > On Thu, Apr 24, 2008 at 11:04 AM, Alexandru Petrescu
> > <alexandru.petrescu@gmail.com> wrote:
> >
> > > George Tsirtsis wrote:
> > >
> > >
> > > > Hi all,
> > > >
> > > > Now that NEMOv4-base is outof the way, how about starting the process
> > > > for http://tools.ietf.org/html/draft-ietf-mip4-nemov4-fa-02 ?
> > > >
> > > >
> > >  Not sure whether you request procedural advancement or technical
> > > discussion.
> > >
> > >  Technically, I think there's need of some more syncing on FA-NEMO docs,
> eg
> > > citing numbers already allocated, ordering between different mobile
> network
> > > extensions, and maybe other things.  The Sec section could say how new
> risks
> > > are introduced by th etunnelling extension and how protection is
> offered.
> > > 3.1 background could picture a figure or two of tunnels.  Just some
> > > thoughts...
> > >
> > >  Alex
> > >
> > >
> > >
> > >
> > >
> > > >
> > > > Regards
> > > > George
> > > >
> > > > On Thu, Apr 24, 2008 at 12:47 AM,  <rfc-editor@rfc-editor.org> wrote:
> > > >
> > > >
> > > > >  A new Request for Comments is now available in online RFC
> libraries.
> > > > >
> > > > >
> > > > >       RFC 5177
> > > > >
> > > > >       Title:      Network Mobility (NEMO) Extensions for
> > > > >                   Mobile IPv4
> > > > >       Author:     K. Leung, G. Dommety,
> > > > >                   V. Narayanan, A. Petrescu
> > > > >       Status:     Standards Track
> > > > >       Date:       April 2008
> > > > >       Mailbox:    kleung@cisco.com,
> > > > >                   gdommety@cisco.com,
> > > > >                   vidyan@qualcomm.com,
> > > > >                   alexandru.petrescu@motorola.com
> > > > >       Pages:      26
> > > > >       Characters: 56094
> > > > >       Updates/Obsoletes/SeeAlso:   None
> > > > >
> > > > >       I-D Tag:    draft-ietf-mip4-nemo-v4-base-11.txt
> > > > >
> > > > >       URL:        http://www.rfc-editor.org/rfc/rfc5177.txt
> > > > >
> > > > >  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.
> > > > >  [STANDARDS TRACK]
> > > > >
> > > > >  This document is a product of the Mobility for IPv4 Working Group
> of
> > > > >
> > > >
> > > the IETF.
> > >
> > > >
> > > > >  This is now a Proposed Standard Protocol.
> > > > >
> > > > >  STANDARDS TRACK: This document specifies an Internet standards
> track
> > > > >  protocol for the Internet community,and requests discussion and
> > > > >
> > > >
> > > suggestions
> > >
> > > >
> > > > >  for improvements.  Please refer to the current edition of the
> Internet
> > > > >  Official Protocol Standards (STD 1) for the standardization state
> and
> > > > >  status of this protocol.  Distribution of this memo is unlimited.
> > > > >
> > > > >  This announcement is sent to the IETF list and the RFC-DIST list.
> > > > >  Requests to be added to or deleted from the IETF distribution list
> > > > >  should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
> > > > >  added to or deleted from the RFC-DIST distribution list should
> > > > >  be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
> > > > >
> > > > >  Details on obtaining RFCs via FTP or EMAIL may be obtained by
> sending
> > > > >  an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
> > > > >
> > > > >  help: ways_to_get_rfcs. For example:
> > > > >
> > > > >       To: rfc-info@RFC-EDITOR.ORG
> > > > >       Subject: getting rfcs
> > > > >
> > > > >       help: ways_to_get_rfcs
> > > > >
> > > > >  Requests for special distribution should be addressed to either the
> > > > >  author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.
> > > > >
> > > >
> > > Unless
> > >
> > > >
> > > > >  specifically noted otherwise on the RFC itself, all RFCs are for
> > > > >  unlimited distribution.
> > > > >
> > > > >  Submissions for Requests for Comments should be sent to
> > > > >  RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions
> to
> > > > >
> > > >
> > > RFC
> > >
> > > >
> > > > >  Authors, for further information.
> > > > >
> > > > >
> > > > >  The RFC Editor Team
> > > > >  USC/Information Sciences Institute
> > > > >
> > > > >  ...
> > > > >
> > > > >
> > > > >  _______________________________________________
> > > > >  IETF-Announce mailing list
> > > > >  IETF-Announce@ietf.org
> > > > >  https://www.ietf.org/mailman/listinfo/ietf-announce
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >  ______________________________________________________________________
> > >  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: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Fri Apr 25 06:00:04 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5AFD728C326;
	Fri, 25 Apr 2008 06:00:04 -0700 (PDT)
X-Original-To: mip4@ietf.org
Delivered-To: mip4@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 5617D28C30C; Fri, 25 Apr 2008 06:00:01 -0700 (PDT)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080425130002.5617D28C30C@core3.amsl.com>
Date: Fri, 25 Apr 2008 06:00:01 -0700 (PDT)
Cc: mip4@ietf.org
Subject: [Mip4] I-D Action:draft-ietf-mip4-nemov4-fa-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: <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>
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-03.txt
	Pages           : 10
	Date            : 2008-04-25

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-03.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-mip4-nemov4-fa-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://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 Apr 25 06:27:31 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0D8CB3A6B52;
	Fri, 25 Apr 2008 06:27:31 -0700 (PDT)
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 4065B3A6939
	for <mip4@core3.amsl.com>; Fri, 25 Apr 2008 06:27:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.767
X-Spam-Level: 
X-Spam-Status: No, score=-1.767 tagged_above=-999 required=5 tests=[AWL=0.210, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 pnbBeIgcxtmX for <mip4@core3.amsl.com>;
	Fri, 25 Apr 2008 06:27:29 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.172])
	by core3.amsl.com (Postfix) with ESMTP id 0BBB83A694D
	for <mip4@ietf.org>; Fri, 25 Apr 2008 06:27:29 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 25so2994479wfa.31
	for <mip4@ietf.org>; Fri, 25 Apr 2008 06:27:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=YoE9psuR1KCN7b6ViNoNftmhdM7gJxFU8WPkpFHZSQ4=;
	b=QMqIUVrSuv7LIq/dbQJq5wcJFO8ZKI+Zv/cqz2/D3e/bV/dbqWQbZHYD7bJCPFRTSQtFiDZIWIy+S06w/P4grCKsPYiRYNQpfzysVPBT0RlcdSqzedAHv9iIoERiK4zYDIeitDSz0Pi8OhEdxejbimytgkLJB6g7S24zDAkR2Vw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=EsNpErxCY/MWI8I+SlOjIMbtL9dDow4DX+wxRI910r943Vqz/dCYU8D1PB6IOJ4gGMKCUtZsWOkk/J+r56JdwHLQbI/9V+nalNAiqMvdsABNfPwXDpMRoOv0h+kscLt8IfwVeUKKlWSx4wz/7meP4fhlS5xz1wnhiCJ/aqVCpYY=
Received: by 10.142.58.12 with SMTP id g12mr1021982wfa.269.1209130053784;
	Fri, 25 Apr 2008 06:27:33 -0700 (PDT)
Received: by 10.142.177.9 with HTTP; Fri, 25 Apr 2008 06:27:33 -0700 (PDT)
Message-ID: <d3886a520804250627ndd3005ev5e997cfb69118472@mail.gmail.com>
Date: Fri, 25 Apr 2008 14:27:33 +0100
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: mip4@ietf.org
In-Reply-To: <20080425130002.5617D28C30C@core3.amsl.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <20080425130002.5617D28C30C@core3.amsl.com>
Subject: Re: [Mip4] I-D Action:draft-ietf-mip4-nemov4-fa-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: <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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi all,

This version is now aligned with RFC5177. As far as I am concerned
this is ready for WGLC.

Alex if you still intent to provide figures we can wait for that, but
if you change your mind please let us know so we can push on.

Regards
George




2008/4/25  <Internet-Drafts@ietf.org>:
> 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-03.txt
>         Pages           : 10
>         Date            : 2008-04-25
>
>  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-03.txt
>
>  Internet-Drafts are also available by anonymous FTP at:
>  ftp://ftp.ietf.org/internet-drafts/
>
>  Below is the data which will enable a MIME compliant mail reader
>  implementation to automatically retrieve the ASCII version of the
>  Internet-Draft.
>
>
> --
>  Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>  Supplemental site: http://www.mip4.org/
>
>
-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Fri Apr 25 07:46:46 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8AF6A28C325;
	Fri, 25 Apr 2008 07:46:46 -0700 (PDT)
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 871BB3A6E0D
	for <mip4@core3.amsl.com>; Fri, 25 Apr 2008 07:46:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nrxZyzzti7Vg for <mip4@core3.amsl.com>;
	Fri, 25 Apr 2008 07:46:44 -0700 (PDT)
Received: from mail128.messagelabs.com (mail128.messagelabs.com
	[216.82.250.131])
	by core3.amsl.com (Postfix) with SMTP id 4B3173A6920
	for <mip4@ietf.org>; Fri, 25 Apr 2008 07:46:44 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-5.tower-128.messagelabs.com!1209134808!1477753!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [144.189.100.102]
Received: (qmail 15125 invoked from network); 25 Apr 2008 14:46:48 -0000
Received: from motgate4.mot.com (HELO motgate4.mot.com) (144.189.100.102)
	by server-5.tower-128.messagelabs.com with SMTP;
	25 Apr 2008 14:46:48 -0000
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate4.mot.com (8.12.11/Motorola) with ESMTP id m3PEkmGf003218;
	Fri, 25 Apr 2008 07:46:48 -0700 (MST)
Received: from az10vts01 (az10vts01.mot.com [10.64.251.242])
	by az33exr03.mot.com (8.13.1/Vontu) with SMTP id m3PEklHT020851;
	Fri, 25 Apr 2008 09:46:47 -0500 (CDT)
Received: from [127.0.0.1] ([10.129.41.23])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id m3PEki7U020817;
	Fri, 25 Apr 2008 09:46:45 -0500 (CDT)
Message-ID: <4811EED3.5080600@gmail.com>
Date: Fri, 25 Apr 2008 16:46:43 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: George Tsirtsis <tsirtsis@googlemail.com>
References: <20080425130002.5617D28C30C@core3.amsl.com>
	<d3886a520804250627ndd3005ev5e997cfb69118472@mail.gmail.com>
In-Reply-To: <d3886a520804250627ndd3005ev5e997cfb69118472@mail.gmail.com>
X-Antivirus: avast! (VPS 080425-0, 25/04/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
Cc: mip4@ietf.org
Subject: Re: [Mip4] I-D Action:draft-ietf-mip4-nemov4-fa-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: <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: 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,
> 
> This version is now aligned with RFC5177. As far as I am concerned
> this is ready for WGLC.
> 
> Alex if you still intent to provide figures we can wait for that, but
> if you change your mind please let us know so we can push on.

George I will not work under pressure.  Please go ahead without my 
contribution.

Alex

> 
> Regards
> George
> 
> 
> 
> 
> 2008/4/25  <Internet-Drafts@ietf.org>:
>> 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-03.txt
>>         Pages           : 10
>>         Date            : 2008-04-25
>>
>>  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-03.txt
>>
>>  Internet-Drafts are also available by anonymous FTP at:
>>  ftp://ftp.ietf.org/internet-drafts/
>>
>>  Below is the data which will enable a MIME compliant mail reader
>>  implementation to automatically retrieve the ASCII version of the
>>  Internet-Draft.
>>
>>
>> --
>>  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/
>>
>>


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


From mip4-bounces@ietf.org  Fri Apr 25 08:08:17 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 637DE3A6A8F;
	Fri, 25 Apr 2008 08:08:17 -0700 (PDT)
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 89A2F3A693C
	for <mip4@core3.amsl.com>; Fri, 25 Apr 2008 08:08:16 -0700 (PDT)
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 mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zMgW2uqArdfJ for <mip4@core3.amsl.com>;
	Fri, 25 Apr 2008 08:08:15 -0700 (PDT)
Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.226])
	by core3.amsl.com (Postfix) with ESMTP id 247DC3A6A8F
	for <mip4@ietf.org>; Fri, 25 Apr 2008 08:08:15 -0700 (PDT)
Received: by wx-out-0506.google.com with SMTP id i26so3128316wxd.31
	for <mip4@ietf.org>; Fri, 25 Apr 2008 08:08:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=uvCWp6jx8fHpdomL6E4o/rr6KmIkaK/Nq8HFoLwoJOw=;
	b=Ls4hzK0UmQwme+NoDmdF1mXvKSkl+l4uCCDVCX7EZ8skDomJglZpwp2SAy64rMTeQLx1qgeoGYSxIuWx0ME793q9njdv90CiG7OUu0vBiv4qcGgv8uBhtmGcNrWbUvTxh3skUNaMj36z2xwUIIckBpNv+0oRHtzTaaPHFs4iPgU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=lcgy/DOQ+ynGSDZCuK8NHbzeAts18akE16GPaZMtiNPhDcpPT9260aZX1ZOeToCpaOwSZHfqS3f+IeQ8opMbuoGhJCbLoNTAWWXjZ31TQkmQt07t/IWMtwNKlgfY9Qg5Fwb7n2zZ/3p16BHYWGgsBatOaFQWFqCvCmRyRLl7a0I=
Received: by 10.100.93.19 with SMTP id q19mr7715489anb.143.1209136099708;
	Fri, 25 Apr 2008 08:08:19 -0700 (PDT)
Received: by 10.100.197.12 with HTTP; Fri, 25 Apr 2008 08:08:19 -0700 (PDT)
Message-ID: <d3886a520804250808m28de9f72tb110f3129d4e80ba@mail.gmail.com>
Date: Fri, 25 Apr 2008 16:08:19 +0100
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Alexandru Petrescu" <alexandru.petrescu@gmail.com>
In-Reply-To: <4811EED3.5080600@gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <20080425130002.5617D28C30C@core3.amsl.com>
	<d3886a520804250627ndd3005ev5e997cfb69118472@mail.gmail.com>
	<4811EED3.5080600@gmail.com>
Cc: mip4@ietf.org
Subject: Re: [Mip4] I-D Action:draft-ietf-mip4-nemov4-fa-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: <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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hey, I did not mean to pressure anyone...this is a volunteer organization.

Personally I do not think it is important, but I am not in a hurry
either. So, if you think this is important then I am OK with waiting.

In general, however, I like things to have a visible end when
possible. So when you offer to do something I like to hear something
like "I can do it in a week, ....in the next month, ....before Dublin"

Thanks
George

On Fri, Apr 25, 2008 at 3:46 PM, Alexandru Petrescu
<alexandru.petrescu@gmail.com> wrote:
> George Tsirtsis wrote:
>
> > Hi all,
> >
> > This version is now aligned with RFC5177. As far as I am concerned
> > this is ready for WGLC.
> >
> > Alex if you still intent to provide figures we can wait for that, but
> > if you change your mind please let us know so we can push on.
> >
>
>  George I will not work under pressure.  Please go ahead without my
> contribution.
>
>  Alex
>
>
>
>
> >
> > Regards
> > George
> >
> >
> >
> >
> > 2008/4/25  <Internet-Drafts@ietf.org>:
> >
> > > 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-03.txt
> > >        Pages           : 10
> > >        Date            : 2008-04-25
> > >
> > >  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-03.txt
> > >
> > >  Internet-Drafts are also available by anonymous FTP at:
> > >  ftp://ftp.ietf.org/internet-drafts/
> > >
> > >  Below is the data which will enable a MIME compliant mail reader
> > >  implementation to automatically retrieve the ASCII version of the
> > >  Internet-Draft.
> > >
> > >
> > > --
> > >  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/
> > >
> > >
> > >
> >
>
>
>  ______________________________________________________________________
>  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: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Fri Apr 25 09:01:55 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8865528C353;
	Fri, 25 Apr 2008 09:01:55 -0700 (PDT)
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 8934A28C33D
	for <mip4@core3.amsl.com>; Fri, 25 Apr 2008 09:01:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qG9EdEG8sOSG for <mip4@core3.amsl.com>;
	Fri, 25 Apr 2008 09:01:46 -0700 (PDT)
Received: from mail153.messagelabs.com (mail153.messagelabs.com
	[216.82.253.51]) by core3.amsl.com (Postfix) with SMTP id ABA8F28C36B
	for <mip4@ietf.org>; Fri, 25 Apr 2008 09:01:16 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-14.tower-153.messagelabs.com!1209139280!11230829!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [144.189.100.102]
Received: (qmail 28030 invoked from network); 25 Apr 2008 16:01:20 -0000
Received: from motgate4.mot.com (HELO motgate4.mot.com) (144.189.100.102)
	by server-14.tower-153.messagelabs.com with SMTP;
	25 Apr 2008 16:01:20 -0000
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate4.mot.com (8.12.11/Motorola) with ESMTP id m3PG1K1A016838;
	Fri, 25 Apr 2008 09:01:20 -0700 (MST)
Received: from az10vts01 (az10vts01.mot.com [10.64.251.242])
	by az33exr04.mot.com (8.13.1/Vontu) with SMTP id m3PG1JmS023765;
	Fri, 25 Apr 2008 11:01:19 -0500 (CDT)
Received: from [127.0.0.1] ([10.129.40.71])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id m3PG1EgB023659;
	Fri, 25 Apr 2008 11:01:17 -0500 (CDT)
Message-ID: <48120049.2060404@gmail.com>
Date: Fri, 25 Apr 2008 18:01:13 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: George Tsirtsis <tsirtsis@googlemail.com>
References: <20080425130002.5617D28C30C@core3.amsl.com>	
	<d3886a520804250627ndd3005ev5e997cfb69118472@mail.gmail.com>	
	<4811EED3.5080600@gmail.com>
	<d3886a520804250808m28de9f72tb110f3129d4e80ba@mail.gmail.com>
In-Reply-To: <d3886a520804250808m28de9f72tb110f3129d4e80ba@mail.gmail.com>
X-Antivirus: avast! (VPS 080425-0, 25/04/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
Cc: Alexandru Petrescu <alexandru.petrescu@gmail.com>, mip4@ietf.org
Subject: Re: [Mip4] I-D Action:draft-ietf-mip4-nemov4-fa-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: <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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

GEorge, sorry, I over-reacted.  I'm busy starring at satellites over 
Earth right now so I think I can draw pictures before Dublin, and even 
discuss more ordering and security aspects.

Alex

George Tsirtsis wrote:
> Hey, I did not mean to pressure anyone...this is a volunteer organization.
> 
> Personally I do not think it is important, but I am not in a hurry
> either. So, if you think this is important then I am OK with waiting.
> 
> In general, however, I like things to have a visible end when
> possible. So when you offer to do something I like to hear something
> like "I can do it in a week, ....in the next month, ....before Dublin"
> 
> Thanks
> George
> 
> On Fri, Apr 25, 2008 at 3:46 PM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
>> George Tsirtsis wrote:
>>
>>> Hi all,
>>>
>>> This version is now aligned with RFC5177. As far as I am concerned
>>> this is ready for WGLC.
>>>
>>> Alex if you still intent to provide figures we can wait for that, but
>>> if you change your mind please let us know so we can push on.
>>>
>>  George I will not work under pressure.  Please go ahead without my
>> contribution.
>>
>>  Alex
>>
>>
>>
>>
>>> Regards
>>> George
>>>
>>>
>>>
>>>
>>> 2008/4/25  <Internet-Drafts@ietf.org>:
>>>
>>>> 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-03.txt
>>>>        Pages           : 10
>>>>        Date            : 2008-04-25
>>>>
>>>>  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-03.txt
>>>>
>>>>  Internet-Drafts are also available by anonymous FTP at:
>>>>  ftp://ftp.ietf.org/internet-drafts/
>>>>
>>>>  Below is the data which will enable a MIME compliant mail reader
>>>>  implementation to automatically retrieve the ASCII version of the
>>>>  Internet-Draft.
>>>>
>>>>
>>>> --
>>>>  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/
>>>>
>>>>
>>>>
>>
>>  ______________________________________________________________________
>>  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: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Fri Apr 25 14:32:20 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E797528C1B1;
	Fri, 25 Apr 2008 14:32:20 -0700 (PDT)
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 3B64E3A6DC5
	for <mip4@core3.amsl.com>; Fri, 25 Apr 2008 14:32:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level: 
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_93=0.6]
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 KSYjG5Fh62hg for <mip4@core3.amsl.com>;
	Fri, 25 Apr 2008 14:32:18 -0700 (PDT)
Received: from smtp7-g19.free.fr (smtp7-g19.free.fr [212.27.42.64])
	by core3.amsl.com (Postfix) with ESMTP id BD9F93A6DF6
	for <mip4@ietf.org>; Fri, 25 Apr 2008 14:31:43 -0700 (PDT)
Received: from smtp7-g19.free.fr (localhost [127.0.0.1])
	by smtp7-g19.free.fr (Postfix) with ESMTP id A68D032280F;
	Fri, 25 Apr 2008 23:31:47 +0200 (CEST)
Received: from [127.0.0.1] (bur91-3-82-239-213-32.fbx.proxad.net
	[82.239.213.32])
	by smtp7-g19.free.fr (Postfix) with ESMTP id 4E26F322821;
	Fri, 25 Apr 2008 23:31:22 +0200 (CEST)
Message-ID: <48124DA9.2090703@gmail.com>
Date: Fri, 25 Apr 2008 23:31:21 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: George Tsirtsis <tsirtsis@googlemail.com>
References: <20080423234721.5C847125D14@bosco.isi.edu>	
	<d3886a520804240252k69507066gb0c652704829bcaf@mail.gmail.com>	
	<48105B1F.3030102@gmail.com>
	<d3886a520804240309p1379b3adv35a2f109f5132afb@mail.gmail.com>
In-Reply-To: <d3886a520804240309p1379b3adv35a2f109f5132afb@mail.gmail.com>
X-Antivirus: avast! (VPS 080425-1, 25/04/2008), Outbound message
X-Antivirus-Status: Clean
Cc: Alexandru Petrescu <alexandru.petrescu@gmail.com>, mip4@ietf.org
Subject: Re: [Mip4] RFC 5177 on Network Mobility (NEMO) Extensions for
 Mobile IPv4
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

George Tsirtsis wrote:
[...]
> - not sure I see a reason to do more figures, but if you or someone 
> puts together some relevant figures I would be ok with including them
>  in the draft.

George, some figures are ready, but please clarify me some things first.

When the FA CoA model is used, and no nemov4-fa optimizations, and MR
attached to FA, does a packet's header captured on the link from HA to
FA, packet originally sent from CN to LFN, look like this?

                             src= HA@
                             dst= FA@________________(1)
                             src= HA@
                             dst= MR's HoA___________(2)
                             src= CN@
                             dst= LFN@

Do we call this model a "Foreign Agent Care-of Address" model instead of
a "Care-of Address" model? (section 3.1 ambiguously says "When the
co-located care-of address model is used [vs] When the care-of address
model is used")?

Do we expect a Modified IP Header and a Minimal Forwarding Header (RFC
2004 "Minimal Encapsulation withn IP"), or a GRE Header (RFC 2784
"Generic Routing Encapsulation"), anywhere at points (1) or (2) above?
Or do we assume always IP-in-IP encapsulation (RFC 2003 "IP
Encapsulation within IP").

Alex

> 
> Thanks George
> 
> On Thu, Apr 24, 2008 at 11:04 AM, Alexandru Petrescu 
> <alexandru.petrescu@gmail.com> wrote:
>> George Tsirtsis wrote:
>> 
>>> Hi all,
>>> 
>>> Now that NEMOv4-base is outof the way, how about starting the 
>>> process for 
>>> http://tools.ietf.org/html/draft-ietf-mip4-nemov4-fa-02 ?
>>> 
>> Not sure whether you request procedural advancement or technical 
>> discussion.
>> 
>> Technically, I think there's need of some more syncing on FA-NEMO 
>> docs, eg citing numbers already allocated, ordering between 
>> different mobile network extensions, and maybe other things.  The 
>> Sec section could say how new risks are introduced by th 
>> etunnelling extension and how protection is offered. 3.1 background
>>  could picture a figure or two of tunnels.  Just some thoughts...
>> 
>> Alex
>> 
>> 
>> 
>> 
>>> 
>>> Regards George
>>> 
>>> On Thu, Apr 24, 2008 at 12:47 AM,  <rfc-editor@rfc-editor.org> 
>>> wrote:
>>> 
>>>> A new Request for Comments is now available in online RFC 
>>>> libraries.
>>>> 
>>>> 
>>>> RFC 5177
>>>> 
>>>> Title:      Network Mobility (NEMO) Extensions for Mobile IPv4 
>>>> Author:     K. Leung, G. Dommety, V. Narayanan, A. Petrescu 
>>>> Status:     Standards Track Date:       April 2008 Mailbox: 
>>>> kleung@cisco.com, gdommety@cisco.com, vidyan@qualcomm.com, 
>>>> alexandru.petrescu@motorola.com Pages:      26 Characters: 
>>>> 56094 Updates/Obsoletes/SeeAlso:   None
>>>> 
>>>> I-D Tag:    draft-ietf-mip4-nemo-v4-base-11.txt
>>>> 
>>>> URL:        http://www.rfc-editor.org/rfc/rfc5177.txt
>>>> 
>>>> 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. [STANDARDS TRACK]
>>>> 
>>>> This document is a product of the Mobility for IPv4 Working 
>>>> Group of
>> the IETF.
>>>> This is now a Proposed Standard Protocol.
>>>> 
>>>> STANDARDS TRACK: This document specifies an Internet standards
>>>>  track protocol for the Internet community,and requests 
>>>> discussion and
>> suggestions
>>>> for improvements.  Please refer to the current edition of the 
>>>> Internet Official Protocol Standards (STD 1) for the 
>>>> standardization state and status of this protocol. Distribution
>>>>  of this memo is unlimited.
>>>> 
>>>> This announcement is sent to the IETF list and the RFC-DIST 
>>>> list. Requests to be added to or deleted from the IETF 
>>>> distribution list should be sent to IETF-REQUEST@IETF.ORG. 
>>>> Requests to be added to or deleted from the RFC-DIST 
>>>> distribution list should be sent to 
>>>> RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>>>> 
>>>> Details on obtaining RFCs via FTP or EMAIL may be obtained by 
>>>> sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the 
>>>> message body
>>>> 
>>>> help: ways_to_get_rfcs. For example:
>>>> 
>>>> To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs
>>>> 
>>>> help: ways_to_get_rfcs
>>>> 
>>>> Requests for special distribution should be addressed to either
>>>>  the author of the RFC in question, or to 
>>>> RFC-Manager@RFC-EDITOR.ORG.
>> Unless
>>>> specifically noted otherwise on the RFC itself, all RFCs are 
>>>> for unlimited distribution.
>>>> 
>>>> Submissions for Requests for Comments should be sent to 
>>>> RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, 
>>>> Instructions to
>> RFC
>>>> Authors, for further information.
>>>> 
>>>> 
>>>> The RFC Editor Team USC/Information Sciences Institute
>>>> 
>>>> ...
>>>> 
>>>> 
>>>> _______________________________________________ IETF-Announce 
>>>> mailing list IETF-Announce@ietf.org 
>>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>>> 
>>>> 
>> 
>> ______________________________________________________________________
>>  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: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Mon Apr 28 01:20:25 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1C32C3A6E46;
	Mon, 28 Apr 2008 01:20:25 -0700 (PDT)
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 DB26A3A6E2F
	for <mip4@core3.amsl.com>; Mon, 28 Apr 2008 01:20:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level: 
X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5
	tests=[AWL=-0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622,
	J_CHICKENPOX_93=0.6]
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 KE-fGJ9lXN4y for <mip4@core3.amsl.com>;
	Mon, 28 Apr 2008 01:20:22 -0700 (PDT)
Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179])
	by core3.amsl.com (Postfix) with ESMTP id 9702B3A6B56
	for <mip4@ietf.org>; Mon, 28 Apr 2008 01:20:18 -0700 (PDT)
Received: by py-out-1112.google.com with SMTP id x19so5926261pyg.24
	for <mip4@ietf.org>; Mon, 28 Apr 2008 01:20:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=YOpa9sCnaq72s8RrGhJwRTkHrw5IY5YdhVeOaDBIcHk=;
	b=gML0vkyLQiZV49ZfLKRVzOhupe6hSGQIjX5R1sFZzK47BzIW+QP++nbJ8V70YJQQrlUiHd/6AIPm1mj3GVLc4fYwL4KtIHyOy3ILgrTDdEPRBE/0fprcJ+r4OGwFLA+ksQmoNxR4mLB/qE976TAsfgRcU2E9+MXKfoOqRT912D8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=xlR/rMcF12A/4N6Af64caM+j09J/Rcb4Re7eRRZLyQNWfnF5H/+Xs3BmH6yWg+fMldgGYxr+6S13WBG3hdsguFIyBk2gkNfmcqH+TrFIUCYNWsmqh0/PW79L+T7sCRE8X2RLCcxHQyFk1YcJdhbiq25xkHtxbcaAA0dZGO96Gw8=
Received: by 10.142.221.19 with SMTP id t19mr2248441wfg.100.1209370821777;
	Mon, 28 Apr 2008 01:20:21 -0700 (PDT)
Received: by 10.142.177.9 with HTTP; Mon, 28 Apr 2008 01:20:21 -0700 (PDT)
Message-ID: <d3886a520804280120l2d30ae74gd90457a0b6e15500@mail.gmail.com>
Date: Mon, 28 Apr 2008 09:20:21 +0100
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Alexandru Petrescu" <alexandru.petrescu@gmail.com>
In-Reply-To: <48124DA9.2090703@gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <20080423234721.5C847125D14@bosco.isi.edu>
	<d3886a520804240252k69507066gb0c652704829bcaf@mail.gmail.com>
	<48105B1F.3030102@gmail.com>
	<d3886a520804240309p1379b3adv35a2f109f5132afb@mail.gmail.com>
	<48124DA9.2090703@gmail.com>
Cc: mip4@ietf.org
Subject: Re: [Mip4] RFC 5177 on Network Mobility (NEMO) Extensions for
	Mobile IPv4
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

Hi Alex,

inline...

On Fri, Apr 25, 2008 at 10:31 PM, Alexandru Petrescu
<alexandru.petrescu@gmail.com> wrote:
> George Tsirtsis wrote:
>  [...]
>
>
> > - not sure I see a reason to do more figures, but if you or someone puts
> together some relevant figures I would be ok with including them
> >  in the draft.
> >
>
>  George, some figures are ready, but please clarify me some things first.
>
>  When the FA CoA model is used, and no nemov4-fa optimizations, and MR
>  attached to FA, does a packet's header captured on the link from HA to
>  FA, packet originally sent from CN to LFN, look like this?
>
>                             src= HA@
>                             dst= FA@________________(1)
>                             src= HA@
>                             dst= MR's HoA___________(2)
>                             src= CN@
>                             dst= LFN@
>
>  Do we call this model a "Foreign Agent Care-of Address" model instead of
>  a "Care-of Address" model? (section 3.1 ambiguously says "When the
>  co-located care-of address model is used [vs] When the care-of address
>  model is used")?
>

GT> The above shows a "care-of address" model (aka "FA" model).
colocated care-of address model is the one where the MN has a unique
care-of addresses, as opposed to a shared on, and I think this is
standard MIPv4 terminology.


>  Do we expect a Modified IP Header and a Minimal Forwarding Header (RFC
>  2004 "Minimal Encapsulation withn IP"), or a GRE Header (RFC 2784
>  "Generic Routing Encapsulation"), anywhere at points (1) or (2) above?
>  Or do we assume always IP-in-IP encapsulation (RFC 2003 "IP
>  Encapsulation within IP").
>

GT> All the encapsulations are negotiated as part of RFC3344, which
should fully apply in this case for point (1). (2) is just IP in IP as
per NEMO.

>  Alex
>
>
>
>
> >
> > Thanks George
> >
> > On Thu, Apr 24, 2008 at 11:04 AM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
> >
> > > George Tsirtsis wrote:
> > >
> > >
> > > > Hi all,
> > > >
> > > > Now that NEMOv4-base is outof the way, how about starting the process
> for http://tools.ietf.org/html/draft-ietf-mip4-nemov4-fa-02 ?
> > > >
> > > >
> > > Not sure whether you request procedural advancement or technical
> discussion.
> > >
> > > Technically, I think there's need of some more syncing on FA-NEMO docs,
> eg citing numbers already allocated, ordering between different mobile
> network extensions, and maybe other things.  The Sec section could say how
> new risks are introduced by th etunnelling extension and how protection is
> offered. 3.1 background
> > >  could picture a figure or two of tunnels.  Just some thoughts...
> > >
> > > Alex
> > >
> > >
> > >
> > >
> > >
> > > >
> > > > Regards George
> > > >
> > > > On Thu, Apr 24, 2008 at 12:47 AM,  <rfc-editor@rfc-editor.org> wrote:
> > > >
> > > >
> > > > > A new Request for Comments is now available in online RFC libraries.
> > > > >
> > > > >
> > > > > RFC 5177
> > > > >
> > > > > Title:      Network Mobility (NEMO) Extensions for Mobile IPv4
> Author:     K. Leung, G. Dommety, V. Narayanan, A. Petrescu Status:
> Standards Track Date:       April 2008 Mailbox: kleung@cisco.com,
> gdommety@cisco.com, vidyan@qualcomm.com, alexandru.petrescu@motorola.com
> Pages:      26 Characters: 56094 Updates/Obsoletes/SeeAlso:   None
> > > > >
> > > > > I-D Tag:    draft-ietf-mip4-nemo-v4-base-11.txt
> > > > >
> > > > > URL:        http://www.rfc-editor.org/rfc/rfc5177.txt
> > > > >
> > > > > 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.
> [STANDARDS TRACK]
> > > > >
> > > > > This document is a product of the Mobility for IPv4 Working Group of
> > > > >
> > > >
> > > the IETF.
> > >
> > > >
> > > > > This is now a Proposed Standard Protocol.
> > > > >
> > > > > STANDARDS TRACK: This document specifies an Internet standards
> > > > >  track protocol for the Internet community,and requests discussion
> and
> > > > >
> > > >
> > > suggestions
> > >
> > > >
> > > > > for improvements.  Please refer to the current edition of the
> Internet Official Protocol Standards (STD 1) for the standardization state
> and status of this protocol. Distribution
> > > > >  of this memo is unlimited.
> > > > >
> > > > > This announcement is sent to the IETF list and the RFC-DIST list.
> Requests to be added to or deleted from the IETF distribution list should be
> sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the
> RFC-DIST distribution list should be sent to
> RFC-DIST-REQUEST@RFC-EDITOR.ORG.
> > > > >
> > > > > Details on obtaining RFCs via FTP or EMAIL may be obtained by
> sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
> > > > >
> > > > > help: ways_to_get_rfcs. For example:
> > > > >
> > > > > To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs
> > > > >
> > > > > help: ways_to_get_rfcs
> > > > >
> > > > > Requests for special distribution should be addressed to either
> > > > >  the author of the RFC in question, or to
> RFC-Manager@RFC-EDITOR.ORG.
> > > > >
> > > >
> > > Unless
> > >
> > > >
> > > > > specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> > > > >
> > > > > Submissions for Requests for Comments should be sent to
> RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to
> > > > >
> > > >
> > > RFC
> > >
> > > >
> > > > > Authors, for further information.
> > > > >
> > > > >
> > > > > The RFC Editor Team USC/Information Sciences Institute
> > > > >
> > > > > ...
> > > > >
> > > > >
> > > > > _______________________________________________ IETF-Announce
> mailing list IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > > ______________________________________________________________________
> > >  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: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Mon Apr 28 01:37:21 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9C0383A6A29;
	Mon, 28 Apr 2008 01:37:21 -0700 (PDT)
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 526283A6A29
	for <mip4@core3.amsl.com>; Mon, 28 Apr 2008 01:37:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level: 
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KHjBf1bK1Uxi for <mip4@core3.amsl.com>;
	Mon, 28 Apr 2008 01:37:20 -0700 (PDT)
Received: from mail153.messagelabs.com (mail153.messagelabs.com
	[216.82.253.51]) by core3.amsl.com (Postfix) with SMTP id 7227C3A68B9
	for <mip4@ietf.org>; Mon, 28 Apr 2008 01:37:20 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-3.tower-153.messagelabs.com!1209371843!8509155!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [144.189.100.105]
Received: (qmail 14314 invoked from network); 28 Apr 2008 08:37:23 -0000
Received: from motgate5.mot.com (HELO motgate5.mot.com) (144.189.100.105)
	by server-3.tower-153.messagelabs.com with SMTP;
	28 Apr 2008 08:37:23 -0000
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate5.mot.com (8.12.11/Motorola) with ESMTP id m3S8bMV1029083;
	Mon, 28 Apr 2008 01:37:23 -0700 (MST)
Received: from az10vts03 (az10vts03.mot.com [10.64.251.244])
	by az33exr03.mot.com (8.13.1/Vontu) with SMTP id m3S8bLAB002610;
	Mon, 28 Apr 2008 03:37:22 -0500 (CDT)
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 m3S8bJrO002467;
	Mon, 28 Apr 2008 03:37:20 -0500 (CDT)
Message-ID: <48158CB4.1070502@gmail.com>
Date: Mon, 28 Apr 2008 10:37:08 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: George Tsirtsis <tsirtsis@googlemail.com>
References: <20080423234721.5C847125D14@bosco.isi.edu>	
	<d3886a520804240252k69507066gb0c652704829bcaf@mail.gmail.com>	
	<48105B1F.3030102@gmail.com>	
	<d3886a520804240309p1379b3adv35a2f109f5132afb@mail.gmail.com>	
	<48124DA9.2090703@gmail.com>
	<d3886a520804280120l2d30ae74gd90457a0b6e15500@mail.gmail.com>
In-Reply-To: <d3886a520804280120l2d30ae74gd90457a0b6e15500@mail.gmail.com>
X-Antivirus: avast! (VPS 080427-0, 27/04/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
Cc: Alexandru Petrescu <alexandru.petrescu@gmail.com>, mip4@ietf.org
Subject: Re: [Mip4] RFC 5177 on Network Mobility (NEMO) Extensions for
 Mobile IPv4
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

George Tsirtsis wrote:
> Hi Alex,
> 
> inline...
> 
> On Fri, Apr 25, 2008 at 10:31 PM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
>> George Tsirtsis wrote:
>>  [...]
>>
>>
>>> - not sure I see a reason to do more figures, but if you or someone puts
>> together some relevant figures I would be ok with including them
>>>  in the draft.
>>>
>>  George, some figures are ready, but please clarify me some things first.
>>
>>  When the FA CoA model is used, and no nemov4-fa optimizations, and MR
>>  attached to FA, does a packet's header captured on the link from HA to
>>  FA, packet originally sent from CN to LFN, look like this?
>>
>>                             src= HA@
>>                             dst= FA@________________(1)
>>                             src= HA@
>>                             dst= MR's HoA___________(2)
>>                             src= CN@
>>                             dst= LFN@
>>
>>  Do we call this model a "Foreign Agent Care-of Address" model instead of
>>  a "Care-of Address" model? (section 3.1 ambiguously says "When the
>>  co-located care-of address model is used [vs] When the care-of address
>>  model is used")?
>>
> 
> GT> The above shows a "care-of address" model (aka "FA" model).
> colocated care-of address model is the one where the MN has a unique
> care-of addresses, as opposed to a shared on, and I think this is
> standard MIPv4 terminology.

Not sure which RFC one is thinking about when invoking "care-of address 
model" but RFC3344 seems to mention "Foreign Agent Care-of Address mode" 
vs "Co-located Care-of Address mode", page 11.

RFC3344 doesn't seem to mention shared address, nor models.

What am I missing?

>>  Do we expect a Modified IP Header and a Minimal Forwarding Header (RFC
>>  2004 "Minimal Encapsulation withn IP"), or a GRE Header (RFC 2784
>>  "Generic Routing Encapsulation"), anywhere at points (1) or (2) above?
>>  Or do we assume always IP-in-IP encapsulation (RFC 2003 "IP
>>  Encapsulation within IP").
>>
> 
> GT> All the encapsulations are negotiated as part of RFC3344, which
> should fully apply in this case for point (1). (2) is just IP in IP as
> per NEMO.

Ok.

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


From mip4-bounces@ietf.org  Mon Apr 28 02:02:38 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7B65428C182;
	Mon, 28 Apr 2008 02:02:38 -0700 (PDT)
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 CA7BC28C14D
	for <mip4@core3.amsl.com>; Mon, 28 Apr 2008 02:02:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.827
X-Spam-Level: 
X-Spam-Status: No, score=-1.827 tagged_above=-999 required=5 tests=[AWL=0.150, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 CsBLwskBy1J9 for <mip4@core3.amsl.com>;
	Mon, 28 Apr 2008 02:02:36 -0700 (PDT)
Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181])
	by core3.amsl.com (Postfix) with ESMTP id C9D703A6BE8
	for <mip4@ietf.org>; Mon, 28 Apr 2008 02:02:35 -0700 (PDT)
Received: by py-out-1112.google.com with SMTP id x19so5939631pyg.24
	for <mip4@ietf.org>; Mon, 28 Apr 2008 02:02:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=TZ+RKaa1r9/hh0c0G/s3iiaKmh84LPthullh52LV2EU=;
	b=IGKB8JWDnROOUWJhLHSGorzLvhlfuFKMdEsE5UK8HIyrmDj1DKp717xZuGQaKP7hc634lxmJ1vNLoz3wv6YrEfuw5BTUJ1tVZA1vIexeC5TLtAfM9RqXxyFGHcBNWM/KJJvWrgYH/D/dFtPqckEzI05v+wjM83ja45EqsP53fEU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=xpoPXX2owa15+x+i2UNFQMe84xsKY+76SM7tHXQDAB+Bh9d5+niSmyHMQVCEW4FBAGipa6Ws75HpiwZa25g1sKdQ869z6+Oscskfwerh/Wc8D1JlauPknxBYhQisgMBq21aXVWBWccQ1hKAjxHb80KYTbc/UicM50/PW6SQclS8=
Received: by 10.142.57.12 with SMTP id f12mr1906304wfa.277.1209373358921;
	Mon, 28 Apr 2008 02:02:38 -0700 (PDT)
Received: by 10.142.177.9 with HTTP; Mon, 28 Apr 2008 02:02:38 -0700 (PDT)
Message-ID: <d3886a520804280202s5bca249by73b636a53ccd8f5e@mail.gmail.com>
Date: Mon, 28 Apr 2008 10:02:38 +0100
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Alexandru Petrescu" <alexandru.petrescu@gmail.com>
In-Reply-To: <48158CB4.1070502@gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <20080423234721.5C847125D14@bosco.isi.edu>
	<d3886a520804240252k69507066gb0c652704829bcaf@mail.gmail.com>
	<48105B1F.3030102@gmail.com>
	<d3886a520804240309p1379b3adv35a2f109f5132afb@mail.gmail.com>
	<48124DA9.2090703@gmail.com>
	<d3886a520804280120l2d30ae74gd90457a0b6e15500@mail.gmail.com>
	<48158CB4.1070502@gmail.com>
Cc: mip4@ietf.org
Subject: Re: [Mip4] RFC 5177 on Network Mobility (NEMO) Extensions for
	Mobile IPv4
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

You are missing nothing :-)
 I will align the terminology better when I incorporate your figures
in the draft.

Thanks
George

On Mon, Apr 28, 2008 at 9:37 AM, Alexandru Petrescu
<alexandru.petrescu@gmail.com> wrote:
>
> George Tsirtsis wrote:
>
> > Hi Alex,
> >
> > inline...
> >
> > On Fri, Apr 25, 2008 at 10:31 PM, Alexandru Petrescu
> > <alexandru.petrescu@gmail.com> wrote:
> >
> > > George Tsirtsis wrote:
> > >  [...]
> > >
> > >
> > >
> > > > - not sure I see a reason to do more figures, but if you or someone
> puts
> > > >
> > > together some relevant figures I would be ok with including them
> > >
> > > >  in the draft.
> > > >
> > > >
> > >  George, some figures are ready, but please clarify me some things
> first.
> > >
> > >  When the FA CoA model is used, and no nemov4-fa optimizations, and MR
> > >  attached to FA, does a packet's header captured on the link from HA to
> > >  FA, packet originally sent from CN to LFN, look like this?
> > >
> > >                            src= HA@
> > >                            dst= FA@________________(1)
> > >                            src= HA@
> > >                            dst= MR's HoA___________(2)
> > >                            src= CN@
> > >                            dst= LFN@
> > >
> > >  Do we call this model a "Foreign Agent Care-of Address" model instead
> of
> > >  a "Care-of Address" model? (section 3.1 ambiguously says "When the
> > >  co-located care-of address model is used [vs] When the care-of address
> > >  model is used")?
> > >
> > >
> >
> > GT> The above shows a "care-of address" model (aka "FA" model).
> > colocated care-of address model is the one where the MN has a unique
> > care-of addresses, as opposed to a shared on, and I think this is
> > standard MIPv4 terminology.
> >
>
>  Not sure which RFC one is thinking about when invoking "care-of address
> model" but RFC3344 seems to mention "Foreign Agent Care-of Address mode" vs
> "Co-located Care-of Address mode", page 11.
>
>  RFC3344 doesn't seem to mention shared address, nor models.
>
>  What am I missing?
>
>
>
> >
> > >  Do we expect a Modified IP Header and a Minimal Forwarding Header (RFC
> > >  2004 "Minimal Encapsulation withn IP"), or a GRE Header (RFC 2784
> > >  "Generic Routing Encapsulation"), anywhere at points (1) or (2) above?
> > >  Or do we assume always IP-in-IP encapsulation (RFC 2003 "IP
> > >  Encapsulation within IP").
> > >
> > >
> >
> > GT> All the encapsulations are negotiated as part of RFC3344, which
> > should fully apply in this case for point (1). (2) is just IP in IP as
> > per NEMO.
> >
>
>  Ok.
>
>  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: https://www.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/


From mip4-bounces@ietf.org  Mon Apr 28 06:34:20 2008
Return-Path: <mip4-bounces@ietf.org>
X-Original-To: mip4-archive@optimus.ietf.org
Delivered-To: ietfarch-mip4-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D62223A6E20;
	Mon, 28 Apr 2008 06:34:20 -0700 (PDT)
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 BED0B3A6E0A
	for <mip4@core3.amsl.com>; Mon, 28 Apr 2008 06:34:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.284
X-Spam-Level: 
X-Spam-Status: No, score=-6.284 tagged_above=-999 required=5 tests=[AWL=0.315, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id eum6u1LMkPRF for <mip4@core3.amsl.com>;
	Mon, 28 Apr 2008 06:34:14 -0700 (PDT)
Received: from mail128.messagelabs.com (mail128.messagelabs.com
	[216.82.250.131])
	by core3.amsl.com (Postfix) with SMTP id 3D6543A6D5D
	for <mip4@ietf.org>; Mon, 28 Apr 2008 06:34:14 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-12.tower-128.messagelabs.com!1209389656!17927747!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 31857 invoked from network); 28 Apr 2008 13:34:16 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-12.tower-128.messagelabs.com with SMTP;
	28 Apr 2008 13:34:16 -0000
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id m3SDYGvd010538;
	Mon, 28 Apr 2008 06:34:16 -0700 (MST)
Received: from il06vts04.mot.com (il06vts04.mot.com [129.188.137.144])
	by il06exr04.mot.com (8.13.1/Vontu) with SMTP id m3SDYF06000627;
	Mon, 28 Apr 2008 08:34:15 -0500 (CDT)
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 m3SDYEvo000599;
	Mon, 28 Apr 2008 08:34:14 -0500 (CDT)
Message-ID: <4815D255.2010602@gmail.com>
Date: Mon, 28 Apr 2008 15:34:13 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: George Tsirtsis <tsirtsis@googlemail.com>
References: <20080423234721.5C847125D14@bosco.isi.edu>	
	<d3886a520804240252k69507066gb0c652704829bcaf@mail.gmail.com>	
	<48105B1F.3030102@gmail.com>	
	<d3886a520804240309p1379b3adv35a2f109f5132afb@mail.gmail.com>	
	<48124DA9.2090703@gmail.com>	
	<d3886a520804280120l2d30ae74gd90457a0b6e15500@mail.gmail.com>	
	<48158CB4.1070502@gmail.com>
	<d3886a520804280202s5bca249by73b636a53ccd8f5e@mail.gmail.com>
In-Reply-To: <d3886a520804280202s5bca249by73b636a53ccd8f5e@mail.gmail.com>
X-Antivirus: avast! (VPS 080427-0, 27/04/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
Cc: mip4@ietf.org
Subject: Re: [Mip4] RFC 5177 on Network Mobility (NEMO) Extensions for
 Mobile IPv4
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org

>> Do we expect a Modified IP Header and a Minimal Forwarding Header
>> (RFC
>>> 2004 "Minimal Encapsulation withn IP"), or a GRE Header (RFC 2784
>>>  "Generic Routing Encapsulation"), anywhere at points (1) or (2)
>>> above? Or do we assume always IP-in-IP encapsulation (RFC 2003
>>> "IP Encapsulation within IP").
>>> 
> 
> GT> All the encapsulations are negotiated as part of RFC3344, which 
> should fully apply in this case for point (1). (2) is just IP in IP
> as per NEMO.

In the figures below I assumed only IP-in-IP encapsulation (bits M and G 
are zero).  But if G is 1 - will NTE remove GRE header?

George Tsirtsis wrote:
> You are missing nothing :-) I will align the terminology better when
> I incorporate your figures in the draft.

LEt's talk the figures below.

Is this draft _only_ for FA CoA mode?  I'd suppose yes, but it says
"Extensions defined in this document allow the mobile node and/or a
foreign agent to indicate to the home agent".

Can the MR send a RegReq with a NEMOv4 Tunneling Extension when it
attaches to a FA?  To whom does it send it?

Could NEMOv4-enabled FA send a Registration Reply containing a NEMOv4
Tunnelling Extension?  To whom does it send it?

Sorry, these may be basic 3344 things that I'm not clear.  The figures 
below are only approximative and need to be more precise.  Shall I 
remove the exchange where FA originates RegRep?

Alex

   RFC3344/RFC5177 doing FA-CoA mode       This draft doing FA-CoA mode
                                       (NTE: NEMOv4 Tunnelling Extension)

     LFN MR  FA             HA  CN        LFN MR  FA             HA  CN
      |  |   |    RegReq    |   |          |  |   | RegReq NTE    |   |
      |  |   |------------->|   |          |  |   |------------->|   |
      |  |   |              |   |          |  |   |              |   |
      |  |   |    RegRep    |   |          |  |   | RegRep NTE   |   |
      |  |   |<-------------|   |          |  |   |<-------------|   |
      |  |   |              |   |          |  |   |              |   |

            OR                                        OR

      |  |   |              |   |          |  |   |              |   |
      |  | RegReq           |   |          |  | RegReq  NTE      |   |
      |  |-->|------------->|   |          |  |-->|------------->|   |
      |  |   |              |   |          |  |   |              |   |
      |  | RegRep           |   |          |  | RegRep  NTE      |   |
      |  |<--|<-------------|   |          |  |<--|<-------------|   |
      |  |   |              |   |          |  |   |              |   |
      |  |   |              |   |          |  |   |              |   |

              --------------
          ---/             /-\                    ----------------
       __/_ ( _ _ _ _ _ _ (_/_)__           _____/ _ _ _ _ _ _  _/_\__
         \  (             ( \ )                  \               \ /
          ---\             \-/                    ----------------
              --------------

     Application packet  RegReq           Application packet  RegReq
     header from CN to   captured         header from CN to   captured
     LFN, captured on    on HA-FA         LFN, captured on    on HA-FA
     HA-FA link          link             HA-FA link          link
     ------------------  ---------        ------------------  ---------
     src= HA@            src= FA@         src= HA@            src= FA@
     dst= FA@            dst= HA@         dst= FA@            dst= HA@
     src= HA@            UDP header       src= CN@            UDP header
     dst= MR's HoA                        dst= LFN@
     src= CN@                             Payload
     dst= LFN@
     Payload

[tunnel graphs Thubert-inspired]


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


