Re: [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solution-02.txt
<Gabor.Bajko@nokia.com> Mon, 14 April 2008 18:44 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 295D228C2E9; Mon, 14 Apr 2008 11:44:17 -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 B3CB83A69B8 for <mipshop-mih-dt@core3.amsl.com>; Mon, 14 Apr 2008 11:44:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.001, 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 aKX17zJwYZpT for <mipshop-mih-dt@core3.amsl.com>; Mon, 14 Apr 2008 11:44:14 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id 5101A3A6CCC for <mipshop-mih-dt@ietf.org>; Mon, 14 Apr 2008 11:44:14 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id m3EIfqf0005842 for <mipshop-mih-dt@ietf.org>; Mon, 14 Apr 2008 13:46:57 -0500
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 14 Apr 2008 21:44:07 +0300
Received: from daebe103.NOE.Nokia.com ([10.241.35.24]) by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 14 Apr 2008 13:44:05 -0500
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 14 Apr 2008 13:44:05 -0500
Message-ID: <E5E76343C87BB34ABC6C3FDF3B31272702399E26@daebe103.NOE.Nokia.com>
In-Reply-To: <48037655.3030308@nist.gov>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-topic: [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solution-02.txt
Thread-index: AcieQzYSndYqequLRC66Rl1JWEjFGAAHDZGg
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> <48037655.3030308@nist.gov>
From: Gabor.Bajko@nokia.com
To: mipshop-mih-dt@ietf.org
X-OriginalArrivalTime: 14 Apr 2008 18:44:05.0985 (UTC) FILETIME=[845D5510:01C89E5F]
X-Nokia-AV: Clean
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>
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
Tele, This looks good to me too. Let's submit. - gabor >-----Original Message----- >From: ext Nada Golmie [mailto:nada.golmie@nist.gov] >Sent: Monday, April 14, 2008 8:21 AM >To: Telemaco Melia (tmelia) >Cc: Subir Das; Bajko Gabor (Nokia-OCTO/MtView); >mipshop-mih-dt@ietf.org >Subject: Re: [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solution-02.txt > >Hi Tele, > >I am OK with the document and in favor of submitting for >final approval. >-Nada > > >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 >> > > >-- >Nada Golmie, Ph.D. >Manager, High Speed Network Technologies Group National >Institute of Standards and Technology 100 Bureau Dr. Stop >8920 Gaithersburg, MD 20899 >Email: nada@nist.gov >Phone: (301) 975-4190 >Fax: (301) 590-0932 >Web: http://w3.antd.nist.gov > > > > _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www.ietf.org/mailman/listinfo/mipshop-mih-dt
- [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solution… Telemaco Melia (tmelia)
- Re: [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solu… Telemaco Melia (tmelia)
- Re: [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solu… Gabor.Bajko
- Re: [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solu… Vijay Devarapalli
- Re: [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solu… Telemaco Melia (tmelia)
- Re: [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solu… Vijay Devarapalli
- Re: [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solu… Telemaco Melia (tmelia)
- Re: [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solu… Telemaco Melia (tmelia)
- Re: [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solu… Nada Golmie
- Re: [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solu… Gabor.Bajko
- Re: [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solu… Subir Das