Re: [alto] the discovery problem

Haibin Song <melodysong@huawei.com> Mon, 26 July 2010 11:57 UTC

Return-Path: <melodysong@huawei.com>
X-Original-To: alto@core3.amsl.com
Delivered-To: alto@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 038343A6A09 for <alto@core3.amsl.com>; Mon, 26 Jul 2010 04:57:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.194
X-Spam-Level: *
X-Spam-Status: No, score=1.194 tagged_above=-999 required=5 tests=[AWL=-0.620, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, SARE_LWSHORTT=1.24]
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 TjZMRKtI2OVn for <alto@core3.amsl.com>; Mon, 26 Jul 2010 04:57:53 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 015D03A680A for <alto@ietf.org>; Mon, 26 Jul 2010 04:57:53 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L65005T6YKREA@szxga03-in.huawei.com> for alto@ietf.org; Mon, 26 Jul 2010 19:58:03 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L6500FNJYKOV1@szxga03-in.huawei.com> for alto@ietf.org; Mon, 26 Jul 2010 19:58:03 +0800 (CST)
Received: from jys0449573 (dhcp-72e6.meeting.ietf.org [130.129.114.230]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L6500CVUYKLXY@szxml02-in.huawei.com>; Mon, 26 Jul 2010 19:58:03 +0800 (CST)
Date: Mon, 26 Jul 2010 13:57:49 +0800
From: Haibin Song <melodysong@huawei.com>
In-reply-to: <8B0A9FCBB9832F43971E38010638454F03EB773643@SISPE7MB1.commscope.com>
To: "'Thomson, Martin'" <Martin.Thomson@andrew.com>, alto@ietf.org
Message-id: <007801cb2c87$7e869f30$7b93dd90$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset="us-ascii"
Content-language: zh-cn
Content-transfer-encoding: 7bit
Thread-index: AcssuNRnYDgi75aXQ068cI+XAdrgAgAMdOUQ
References: <8B0A9FCBB9832F43971E38010638454F03EB773643@SISPE7MB1.commscope.com>
Subject: Re: [alto] the discovery problem
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2010 11:57:54 -0000

I totally agree. Please see section 5.1 in draft-song-alto-server-discovery
for the DNS discovery method for ALTO. And check section 5.1.2.1 for reusing
the DHCP option for domain name. And check section 5.1.2.3 for the
limitations of the reverse DNS lookup.

BR,
Haibin



Martin Thomson wrote:

>draft-ietf-geopriv-lis-discovery probably provides most of what you will
need for your application.  You could possibly even use the DHCP option
defined there.

>The security problems arising from the delegation scenario is described
briefly in draft-barnes-hard-problem.  You might have fewer problems with
this with ALTO.

draft-thomson-geopriv-res-gw-discovery includes the more controversial
portion - the use of the reverse tree.  We did originally follow the PTR,
but that had even more problems.  For instance, two IPs in different
networks - and different servers - can refer to the same domain.

Feedback on the draft that uses the reverse tree has been nothing less than
harsh.  It would take me more time than I have right now to go through all
the issues.  I'm happy to expand on this in person.

I would strongly recommend that you look at draft-ietf-geopriv-lis-discovery
as defining the scope of what is achievable in the short term ...and what
you should look at addressing now.

>--Martin
_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto