Re: [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solution-02.txt
"Telemaco Melia (tmelia)" <tmelia@cisco.com> Mon, 14 April 2008 11:55 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 F3DA828C2CD; Mon, 14 Apr 2008 04:55:44 -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 0583F28C2E0 for <mipshop-mih-dt@core3.amsl.com>; Mon, 14 Apr 2008 04:55:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.41
X-Spam-Level:
X-Spam-Status: No, score=-6.41 tagged_above=-999 required=5 tests=[AWL=0.188, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 ptrEoVCYxQMZ for <mipshop-mih-dt@core3.amsl.com>; Mon, 14 Apr 2008 04:55:41 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 73CC628C2D1 for <mipshop-mih-dt@ietf.org>; Mon, 14 Apr 2008 04:55:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.25,655,1199660400"; d="scan'208,217";a="6201329"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 14 Apr 2008 13:56:04 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m3EBu4s3030270; Mon, 14 Apr 2008 13:56:04 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m3EBu4Ag014665; Mon, 14 Apr 2008 11:56:04 GMT
Received: from xmb-ams-335.cisco.com ([144.254.231.80]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 14 Apr 2008 13:56:04 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 14 Apr 2008 13:56:53 +0200
Message-ID: <DD0238A0AAE9B74A8F70A91BDF497C2F038583F4@xmb-ams-335.emea.cisco.com>
In-Reply-To: <DD0238A0AAE9B74A8F70A91BDF497C2F03857F5C@xmb-ams-335.emea.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MIPSHOP-MIH-DT] draft-ietf-mipshop-mstp-solution-02.txt
Thread-Index: AciYzxGREQhChYyTQXiWcXNZoqr8AABuY1KQAFV81HAAkf0T0A==
References: <DD0238A0AAE9B74A8F70A91BDF497C2F0380108B@xmb-ams-335.emea.cisco.com><E5E76343C87BB34ABC6C3FDF3B31272702336AC5@daebe103.NOE.Nokia.com> <DD0238A0AAE9B74A8F70A91BDF497C2F03857F5C@xmb-ams-335.emea.cisco.com>
From: "Telemaco Melia (tmelia)" <tmelia@cisco.com>
To: Subir Das <subir@research.telcordia.com>, Gabor.Bajko@nokia.com, mipshop-mih-dt@ietf.org
X-OriginalArrivalTime: 14 Apr 2008 11:56:04.0769 (UTC) FILETIME=[846C3910:01C89E26]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=14598; t=1208174164; x=1209038164; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=tmelia@cisco.com; z=From:=20=22Telemaco=20Melia=20(tmelia)=22=20<tmelia@cisco. com> |Subject:=20RE=3A=20[MIPSHOP-MIH-DT]=20draft-ietf-mipshop-m stp-solution-02.txt |Sender:=20; bh=R/RLHRIco1ULfMyIDqULZoy85eTAxLnmiNEptZGHIAI=; b=QVtsOn30KJ0NCTUWgdSh3/h9VWiOIB3k4HHiT5NLYowGeW5E/3PFDePz/F ECpFby103L885H/6kpvc1EBcg0lZdxL8M4aqvQTr8k8C9nE3qBoqntEUsW2o b1AoS+ov2v;
Authentication-Results: ams-dkim-2; header.From=tmelia@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; );
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: multipart/mixed; boundary="===============0461921896=="
Sender: mipshop-mih-dt-bounces@ietf.org
Errors-To: mipshop-mih-dt-bounces@ietf.org
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
- [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