Re: [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solution-02.txt

Subir Das <subir@research.telcordia.com> Wed, 16 April 2008 02:56 UTC

Return-Path: <mipshop-mih-dt-bounces@ietf.org>
X-Original-To: mipshop-mih-dt-archive@optimus.ietf.org
Delivered-To: ietfarch-mipshop-mih-dt-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4FB9A3A6865; Tue, 15 Apr 2008 19:56:00 -0700 (PDT)
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 688243A6865 for <mipshop-mih-dt@core3.amsl.com>; Tue, 15 Apr 2008 19:55:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.043
X-Spam-Level:
X-Spam-Status: No, score=-2.043 tagged_above=-999 required=5 tests=[AWL=0.556, 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 AK40oUp1nPJZ for <mipshop-mih-dt@core3.amsl.com>; Tue, 15 Apr 2008 19:55:53 -0700 (PDT)
Received: from flower.research.telcordia.com (flower.research.telcordia.com [128.96.41.5]) by core3.amsl.com (Postfix) with ESMTP id 90A1F3A67AF for <mipshop-mih-dt@ietf.org>; Tue, 15 Apr 2008 19:55:52 -0700 (PDT)
Received: from mailee.research.telcordia.com (mailee.research.telcordia.com [192.4.16.29]) by flower.research.telcordia.com (8.14.2/8.14.2) with ESMTP id m3G2tIXp026017; Tue, 15 Apr 2008 22:55:18 -0400 (EDT)
Received: from [127.0.0.1] (vpntnlB142 [128.96.59.142]) by mailee.research.telcordia.com (8.9.3/8.9.3) with ESMTP id WAA16728; Tue, 15 Apr 2008 22:55:11 -0400 (EDT)
Message-ID: <48056A96.90407@research.telcordia.com>
Date: Tue, 15 Apr 2008 22:55:18 -0400
From: Subir Das <subir@research.telcordia.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: "Telemaco Melia (tmelia)" <tmelia@cisco.com>
References: <DD0238A0AAE9B74A8F70A91BDF497C2F0380108B@xmb-ams-335.emea.cisco.com><E5E76343C87BB34ABC6C3FDF3B31272702336AC5@daebe103.NOE.Nokia.com> <DD0238A0AAE9B74A8F70A91BDF497C2F03857F5C@xmb-ams-335.emea.cisco.com> <DD0238A0AAE9B74A8F70A91BDF497C2F038583F4@xmb-ams-335.emea.cisco.com>
In-Reply-To: <DD0238A0AAE9B74A8F70A91BDF497C2F038583F4@xmb-ams-335.emea.cisco.com>
Content-Type: multipart/mixed; boundary="------------010600040306080109040508"
Cc: mipshop-mih-dt@ietf.org
Subject: Re: [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solution-02.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>
Sender: mipshop-mih-dt-bounces@ietf.org
Errors-To: mipshop-mih-dt-bounces@ietf.org

Tele,
Sorry for the delay. Few minor nits. Ready to go..

_Subir

Telemaco Melia (tmelia) wrote:
> Ehmmm....guys?
> Your silence scares me...are you fine with the doc?
>  
> tele
>  
>
> ------------------------------------------------------------------------
> *From:* mipshop-mih-dt-bounces@ietf.org 
> [mailto:mipshop-mih-dt-bounces@ietf.org] *On Behalf Of *Telemaco Melia 
> (tmelia)
> *Sent:* Friday, April 11, 2008 4:30 PM
> *To:* Gabor.Bajko@nokia.com; mipshop-mih-dt@ietf.org
> *Subject:* Re: [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solution-02.txt
>
> Gabor, all,
>  
> I updated the text according to your suggestions (slightly modified 
> though). Doc is attached.
>  
> I have been spending some time checking what would be the required 
> changes to delete the remark added at the end of section 5.3.
> I would like to know what Vijay and Stefano think about the issue. Do 
> you see use cases requiring an update to the specs?
> If yes, please let us know as soon as possible so we can update all 
> the docs.
> If not then we can post version -02 and boost the discussion around 
> the adoption of new documents. 
>  
> thanks
> tele
>  
> ------------------------------------------------------------------------
> *From:* Gabor.Bajko@nokia.com [mailto:Gabor.Bajko@nokia.com]
> *Sent:* Thursday, April 10, 2008 12:15 AM
> *To:* Telemaco Melia (tmelia); mipshop-mih-dt@ietf.org
> *Subject:* RE: [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solution-02.txt
>
> Hi Tele,
>  
> to the comment in 5.2 lets add this note (after the previous 
> paragraph, ending ' ... DNS query')
>  
>
> When the discovery of an MoS at the visited network, using the FQDN 
> returned in the reverse DNS query, is not successful, the MN MAY 
> attempt to remove portions from the left side of the FQDN and attempt 
> discovery again. The process MAY be repeated iteratively until a 
> successful discovery.
>
> section 5.4:
>
> modify this sentence: "If the  MN does not yet know the domain name of 
> the network, learning it may
>    require more than one operation, as pre-configuration and DHCP
>    methods can not be used."
>
> to: "If the  MN does not yet know the domain name of the network, 
> learning it may
>    require more than one operation, as  DHCP based discovery can not 
> be used and pre-configuration is not a feasible solution in case of an 
> arbitrary remote network."
>
> regarding the comment in 5.3: rfc4004 does not specify how the 
> discovery of an MoS could be done, it doesn't have a general purpose 
> container. One would need to define an extension to 4004 to be able to 
> fetch eg a preconfigured MoS address from the AAA (it could even be 
> part of draft-stupar-mos-diameter-options). I would reformulate it to 
> this:
>
> This section assumes the use of IPv6 or MIPv6 and DHCPv6 based
>    mechanisms to discover MoS services in home while the MN is in
>    visited network. If similar functionalities are desired for IPv4 or 
> MIPv4 and DHCPv4, additional AAA and DHCPv4 extensions would be 
> required. Since use cases requiring these extensions were not 
> identified at  the time of writing this document, they were excluded 
> from the scope of the document.
>
> Vijay has left azairnet and his email address doesn't work any longer. 
> An implicit question is if he will continue with his mipshop chair 
> tasks or not. It may have an impact on these documents.
>
> - Gabor
>
>
>     ------------------------------------------------------------------------
>     *From:* mipshop-mih-dt-bounces@ietf.org
>     [mailto:mipshop-mih-dt-bounces@ietf.org] *On Behalf Of *ext
>     Telemaco Melia (tmelia)
>     *Sent:* Monday, April 07, 2008 9:48 AM
>     *To:* mipshop-mih-dt@ietf.org
>     *Subject:* [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solution-02.txt
>
>     Hi guys,
>      
>     Here is the revised version. All editorial comments have been
>     hopefully digested.
>     There are only a couple of open points, you can track them looking
>     for [COMMENT].
>     One is for Gabor, the second one is about the use of DHCPv4 to
>     discover MoS in visited networks only. Your opinion is welcome.
>      
>     Please go through the document and let me know anything else missing.
>      
>     Thanks
>     Tele
>
_______________________________________________
MIPSHOP-MIH-DT mailing list
MIPSHOP-MIH-DT@ietf.org
https://www.ietf.org/mailman/listinfo/mipshop-mih-dt