Re: [Mip6] WG LC: I-D draft-ietf-mip6-bootstrap-ps-01.txt (Problem Statement for bootstrapping Mobile IPv6 )

"Junghoon Jee" <jhjee@etri.re.kr> Wed, 16 February 2005 09:56 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19494 for <mip6-web-archive@ietf.org>; Wed, 16 Feb 2005 04:56:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1MGc-0006l4-Gt for mip6-web-archive@ietf.org; Wed, 16 Feb 2005 05:18:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1Lp6-0004PX-DI; Wed, 16 Feb 2005 04:50:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1LjO-0002w8-1N for mip6@megatron.ietf.org; Wed, 16 Feb 2005 04:44:26 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18503 for <mip6@ietf.org>; Wed, 16 Feb 2005 04:44:23 -0500 (EST)
Received: from email1.etri.re.kr ([129.254.16.131] helo=email1.etri.info) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1M4b-0006Tc-NL for mip6@ietf.org; Wed, 16 Feb 2005 05:06:22 -0500
Received: from FlyToWorld ([129.254.112.107]) by email1.etri.info with Microsoft SMTPSVC(6.0.3790.211); Wed, 16 Feb 2005 18:44:40 +0900
Message-ID: <008401c5140c$0e1f9100$6b70fe81@FlyToWorld>
From: Junghoon Jee <jhjee@etri.re.kr>
To: mip6@ietf.org, Gopal Dommety <gdommety@cisco.com>
References: <4.3.2.7.2.20050215120213.026355d0@mira-sjc5-d.cisco.com>
Subject: Re: [Mip6] WG LC: I-D draft-ietf-mip6-bootstrap-ps-01.txt (Problem Statement for bootstrapping Mobile IPv6 )
Date: Wed, 16 Feb 2005 18:44:05 +0900
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-OriginalArrivalTime: 16 Feb 2005 09:44:40.0909 (UTC) FILETIME=[22FCE7D0:01C5140C]
X-Spam-Score: 2.2 (++)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0611280225=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 2.2 (++)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc

Hello, Gopal

I would like to re-comment about this WG I-D.
I think this I-D needs to be refined to clearly state about 
the relationship between the network access service and mobility service,
& local home agent assignment issue.
I raised 3 questions related with this as follows.

Q1. Should the network access service be always performed when a MN bootstraps ? 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Section 6.  Network Access and Mobility services
[Page 14]
Only having Mobile IPv6 service is not possible, since the Mobile IPv6 protocol requires
ability to send and receive IPv6 packets.  
=> It seems that network access service should be always performed.

Section 7.1  Mobility Service Subscription Scenario
=> There is no words about network access service.

Q2. Does we have to consider the case of  infrastructure-less scenario when we develop a bootstrapping solution or not ?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Section 7.4 Infrastructure-less scenario
[Page 17]
This specific scenario is not supported in this document.  The reason
for this is described in Section 9.
Section 9. Security Considerations
Thus, the case of infrastructure-less network where there is absolutely 
no pre-mediated trust is kept outside of scope of this document.
=> It seems that we don't need to consider the infrastructure-less scenario 
     when we create a bootstrapping solution.

Q3. Does a bootstrapping solution should support local home agent assignment or not ?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Section 5.1.2  Dynamic Home Agent Assignment
[Page 10]
Local home agents
      The mobile node's home ASP may want to allow a local roaming
      partner ASP to assign a local home agent for the mobile node.
      This is useful both from the point of view of communications
      efficiency, and has also been mentioned as one approach to support
      location privacy.
=> What is the exact meaning of the 'useful' and 'also been mentioned' ?
     Is the local home agent function optional[MAY] ?

draft-le-aaa-mipv6-requirements-03.txt
Section 5.5.  Home agent allocation
   Such functionality SHOULD also be considered when designing the AAA
   support for MIPv6 solution.
=> It seems that we SHOULD support the local HA assignment function.
I already know that draft-ietf-mip6-bootstrap-ps is not a I-D that describe the requirement &
draft-le-aaa-mipv6-requirements was expired. 
But i think that we have to decide about this because many different approaches can be come out depending on our decision.

--Junghoon

----- Original Message ----- 
From: "Gopal Dommety" <gdommety@cisco.com>
To: <mip6@ietf.org>
Sent: Wednesday, February 16, 2005 5:11 AM
Subject: [Mip6] WG LC: I-D draft-ietf-mip6-bootstrap-ps-01.txt (Problem Statement for bootstrapping Mobile IPv6 )


> 
> Hello All,
> 
> 
> This is a Working Group Last Call for the following I-D:
> draft-ietf-mip6-bootstrap-ps-01.txt
> Title:
> Problem Statement for bootstrapping Mobile IPv6
> 
> Please note that the status intended for this I-D is Proposed Standard.
> 
> Please review and post your comments by March 3rd, 2005.
> 
> -Chairs,
> 
> URL-ID is:
> http://www.ietf.org/internet-drafts/draft-ietf-mip6-bootstrap-ps-01.txt
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6