IETF Logo Mail Archive

Re: [MEXT] New Version Notification for draft-perkins-mext-hatunaddr-01.txt

Romain KUNTZ <rkuntz@us.toyota-itc.com> Thu, 04 August 2011 18:38 UTC

Return-Path: <rkuntz@us.toyota-itc.com>
X-Original-To: mext@ietfa.amsl.com
Delivered-To: mext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1518A11E80A6 for <mext@ietfa.amsl.com>; Thu, 4 Aug 2011 11:38:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.52
X-Spam-Level:
X-Spam-Status: No, score=-6.52 tagged_above=-999 required=5 tests=[AWL=0.079, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hpMVMlh7D9wE for <mext@ietfa.amsl.com>; Thu, 4 Aug 2011 11:38:52 -0700 (PDT)
Received: from na3sys009aog104.obsmtp.com (na3sys009aog104.obsmtp.com [74.125.149.73]) by ietfa.amsl.com (Postfix) with SMTP id 5CAE311E808C for <mext@ietf.org>; Thu, 4 Aug 2011 11:38:51 -0700 (PDT)
Received: from mail-pz0-f49.google.com ([209.85.210.49]) (using TLSv1) by na3sys009aob104.postini.com ([74.125.148.12]) with SMTP ID DSNKTjrnSctdZymoEAxsSGp7Qm465kLnvhk5@postini.com; Thu, 04 Aug 2011 11:39:08 PDT
Received: by mail-pz0-f49.google.com with SMTP id 6so1241703pzk.22 for <mext@ietf.org>; Thu, 04 Aug 2011 11:39:05 -0700 (PDT)
Received: by 10.143.20.28 with SMTP id x28mr1100677wfi.349.1312483145337; Thu, 04 Aug 2011 11:39:05 -0700 (PDT)
Received: from hong-lt.paloalto.toyota-itc.com ([206.132.173.18]) by mx.google.com with ESMTPS id m7sm2488983pbk.54.2011.08.04.11.39.04 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 04 Aug 2011 11:39:04 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset="us-ascii"
From: Romain KUNTZ <rkuntz@us.toyota-itc.com>
In-Reply-To: <4E399F6E.8090508@computer.org>
Date: Thu, 04 Aug 2011 11:39:02 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <75B8624B-6C94-4B7F-9487-DCF0E06B5256@us.toyota-itc.com>
References: <20110803185832.21283.61262.idtracker@ietfa.amsl.com> <4E399F6E.8090508@computer.org>
To: charliep@computer.org
X-Mailer: Apple Mail (2.1244.3)
Cc: mext <mext@ietf.org>
Subject: Re: [MEXT] New Version Notification for draft-perkins-mext-hatunaddr-01.txt
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2011 18:38:53 -0000

Hello Charlie,

If the MN has to tunnel data to a different HA than the one to which it sends the BU, then it also needs an IPsec SA with that HA. How would the MN create such SA as it does not know in advance what HA it may use for tunneling? My guess is that the MN is supposed to trust the address received in the option and create the SA upon reception of the option. Similarly, all of the HA tunneling box would also need to  be configured with the corresponding SA. Some considerations about that may be needed in the draft.

Regards,
romain
 

On Aug 3, 2011, at 12:20, Charles E. Perkins wrote:

> 
> Hello folks,
> 
> My draft has now made it through the submission process.
> Please excuse the repeat notification...
> 
> Comments will be appreciated.
> 
> Regards,
> Charlie P.
> 
> 
> -------- Original Message --------
> Subject: New Version Notification for draft-perkins-mext-hatunaddr-01.txt
> Date: Wed, 03 Aug 2011 11:58:32 -0700
> From: <internet-drafts@ietf.org>
> To: <charliep@computer.org>
> CC: <charliep@computer.org>
> 
> A new version of I-D, draft-perkins-mext-hatunaddr-01.txt has been successfully submitted by Charles Perkins and posted to the IETF repository.
> 
> Filename:	 draft-perkins-mext-hatunaddr
> Revision:	 01
> Title:		 Alternate Tunnel Source Address for Home Agent
> Creation date:	 2011-08-03
> WG ID:		 Individual Submission
> Number of pages: 10
> 
> Abstract:
>   Widely deployed mobility management systems for wireless
>   communications have isolated the path for forwarding data from the
>   control plane signaling for mobility management.  To realize this
>   requirement with Mobile IP requires that the control functions of the
>   home agent be addressable at a different IP address than the source
>   IP address of the tunnel between the home agent and mobile node.
>   Similar considerations hold for mobility anchors implementing
>   Hierarchical Mobile IP or PMIP.
> 
> 
> 
> 
> The IETF Secretariat
> 
> _______________________________________________
> MEXT mailing list
> MEXT@ietf.org
> https://www.ietf.org/mailman/listinfo/mext

v2.23.0 | Report a Bug | By Email