Re: [MIPSHOP-MIH-DT] [Mipshop] WG last call on MIHsolution document(draft-ietf-mipshop-mstp-solution-01.txt)

<Gabor.Bajko@nokia.com> Fri, 29 February 2008 23:31 UTC

Return-Path: <mipshop-mih-dt-bounces@ietf.org>
X-Original-To: ietfarch-mipshop-mih-dt-archive@core3.amsl.com
Delivered-To: ietfarch-mipshop-mih-dt-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D6BF328C6AF; Fri, 29 Feb 2008 15:31:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.383
X-Spam-Level:
X-Spam-Status: No, score=-1.383 tagged_above=-999 required=5 tests=[AWL=-0.946, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jr1EfcSYmCvG; Fri, 29 Feb 2008 15:31:50 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5F0D33A6D8E; Fri, 29 Feb 2008 15:31:50 -0800 (PST)
X-Original-To: mipshop-mih-dt@core3.amsl.com
Delivered-To: mipshop-mih-dt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 976243A6DEF for <mipshop-mih-dt@core3.amsl.com>; Fri, 29 Feb 2008 15:31:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n5CvBFmR6lD8 for <mipshop-mih-dt@core3.amsl.com>; Fri, 29 Feb 2008 15:31:48 -0800 (PST)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id DC9FE3A6D8E for <mipshop-mih-dt@ietf.org>; Fri, 29 Feb 2008 15:31:47 -0800 (PST)
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id m1TNWRje001813; Fri, 29 Feb 2008 17:33:14 -0600
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 1 Mar 2008 01:30:56 +0200
Received: from daebe103.NOE.Nokia.com ([10.241.35.24]) by daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 29 Feb 2008 17:30:33 -0600
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 29 Feb 2008 17:30:33 -0600
Message-ID: <E5E76343C87BB34ABC6C3FDF3B312727020CF4C4@daebe103.NOE.Nokia.com>
In-Reply-To: <2817AF6876483A489EB08E0D28D232550D0E2384@PRVPVSMAIL07.corp.twcable.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MIPSHOP-MIH-DT] [Mipshop] WG last call on MIHsolution document(draft-ietf-mipshop-mstp-solution-01.txt)
Thread-Index: AchwGx+VSypE/6ppQdOkmgv5WWPI6QC8/gXgAf8tGdA=
References: <47B37F17.5000902@azairenet.com> <2817AF6876483A489EB08E0D28D232550CE46662@PRVPVSMAIL07.corp.twcable.com> <DD0238A0AAE9B74A8F70A91BDF497C2F0342D2AD@xmb-ams-335.emea.cisco.com><47B5E005.5040709@azairenet.com> <47B604D6.5060405@gmail.com> <2817AF6876483A489EB08E0D28D232550D0E2384@PRVPVSMAIL07.corp.twcable.com>
From: <Gabor.Bajko@nokia.com>
To: <kevin.noll@twcable.com>, <telemaco.melia@googlemail.com>, <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 29 Feb 2008 23:30:33.0776 (UTC) FILETIME=[147F5B00:01C87B2B]
X-Nokia-AV: Clean
Cc: mipshop-mih-dt@ietf.org
Subject: Re: [MIPSHOP-MIH-DT] [Mipshop] WG last call on MIHsolution document(draft-ietf-mipshop-mstp-solution-01.txt)
X-BeenThere: mipshop-mih-dt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIPSHOP Media Independent Handover Design Team List <mipshop-mih-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mipshop-mih-dt>, <mailto:mipshop-mih-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/mipshop-mih-dt>
List-Post: <mailto:mipshop-mih-dt@ietf.org>
List-Help: <mailto:mipshop-mih-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mipshop-mih-dt>, <mailto:mipshop-mih-dt-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mipshop-mih-dt-bounces@ietf.org
Errors-To: mipshop-mih-dt-bounces@ietf.org

Hello Kevin,

Thanks for your comments. Since I wrote most of section 5, I try to
address your comments to that section: 

-- snip --

I also skip the editorial comments, I will correct the text as you
suggested.

>> 7. Sect. 5 para. 4 - clarify
>> "In case MoS is provided in a remote network other than visited or 
>> home network (scenario S4)" might be better stated as "In the case 
>> that MoS is provided by a third-party network (scenario S4)"

Ok, I'll change the sentence to "In case MoS is provided by a
third-party network, which is different from the current visited
network, ..."

>> 9. Sect. 5.1 para. 1 - technical
>> I'm not sure I agree with the statement that "Home domains are 
>> usually pre-configured in the MN". On what basis is this assumption 
>> made? Even if it is a correct assumption, shouldn't there be a 
>> provision for the scenario where the MN does *NOT* have the home
domain pre-configured?

If the home domain is not preconfigured, how would the MN find it out?
The subscription is tight to a network, which is the home. If there is
no home network, there is no subscription.

>> 13. Sect. 5.2 para. 3 and 4 - technical Perhaps the authors can 
>> clarify what the expected result of the reverse DNS query should be.
>> It seems to me that it would not be uncommon for the reverse query 
>> (if it doesn't fail altogether) to return a domain name that is not 
>> the same as the desired MoS realm name. For example, what if the 
>> reverse query returns something like 
>> node1234.dulles.va.myprovider.net, but the MoS realm should be 
>> myprovider.net? Should the MN attempt to contact the MoS based on the
>> returned domain name and remove portions of the domain name 
>> iteratively until it successfully finds an MoS?

I don't know the answer to this question. I need to investigate how
other specs handle this or implementations deal with it. 

>> 16. Sect 5.3 para 4 - technical
>> What is the document references by "[REF TO NEW DOC]"?

It is a new I.D, which was submitted last week. We need to put the name
of that I.D there (draft-stupar-mos-diameter-options).

>> 18. Sect 5.3 - technical
>> This discovery method seems to assume the use of IPv6 and DHCPv6, but
>> does not state that assumption anywhere that I can find. Even if this
>> is the correct assumption, what happens if only IPv4 and DHCPv4 are 
>> available to the MN?

I-D.bajko-mos-dhcp-options defines extensions to discover MoS only in
visited network for the dhcpv4 case. If the MN is using MIPv4, then the
bootstrapping can happen using AAA. If the MN is only using dhcpv4, then
according to the current status of the work, it can only discover an MoS
in the visited network. To support MoS discovery in the home network
while roaming, using dhcpv4, we would need additional work (define a few
additional dhcpv4 extensions). The question is, do we have or foresee a
deployment scenario which would require this? 

>> 19. Sect. 5.4 - technical
>> Why can the MoS domain name not be pre-configured?

It can, but all 3rd party domain names cannot be preconfigured, it is
not feasible. I will clarify the text.


>> 21. Sect. 5.4 - technical
>> Would an alternative method of discovering the third party MoS be 
>> similar to that described in sect. 5.3 where the AAAh and/or AAAv are
>> able to return the third party MoS information?

Well, what the MN discovers using the procedures in section 5.3 is an
MoS address provided to the MN by the home network. That MoS may
virtually be anywhere (in visited, in home, in a preconfigured 3rd
party), but it is provided to the MN as per the policy in the
subscription. In section 5.4 we define a scenario when the MN does want
an MoS address from a specific 3rd party (maybe in addition of the home
MoS).

Thanks for the good catches.
- gabor
_______________________________________________
MIPSHOP-MIH-DT mailing list
MIPSHOP-MIH-DT@ietf.org
https://www.ietf.org/mailman/listinfo/mipshop-mih-dt