IETF Logo Mail Archive

Re: [alto] the discovery problem

"Roni Even" <ron.even.tlv@gmail.com> Sat, 07 August 2010 07:00 UTC

Return-Path: <ron.even.tlv@gmail.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 4F6E23A6765 for <alto@core3.amsl.com>; Sat, 7 Aug 2010 00:00:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001, 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 shrJD7T1qPEo for <alto@core3.amsl.com>; Sat, 7 Aug 2010 00:00:14 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 246C83A6358 for <alto@ietf.org>; Sat, 7 Aug 2010 00:00:13 -0700 (PDT)
Received: by fxm16 with SMTP id 16so3928868fxm.31 for <alto@ietf.org>; Sat, 07 Aug 2010 00:00:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=vTwFll3fJ0uZtgiVQbx3Afi+UYgv0m5xyajutJJ7qh8=; b=NuCiFUQjx5kudiF0wlpjbH6zhyP8A1DQwiVm5CYBZ7fydrHXLpUznK/ZECXyZk3woI MctjSH7ufVaL1v40I5y3E1JMrDHQiQGoObCrZ4u3/OW4E2nVoPixWpJqg0vOMrwYkYaX EXFPazxrvIwCmF82Nq81yxv59VS7aFxW0oDUw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; b=wOwEOM6Z4bBBOEpepF/0wzdCdRi8RsJ3IjyOlBjtBY8ImCr4OaGBNMdDLUfWjo/EAl 6MLfCZ9WTBtMarIwdbsBoTEBbXQSJhTaArN/1H4ux34qwWQ8665bW0jKvjgaeMz7RRYt X+GcAPwys0jC++KzxxMOcOFl/5M8ORR+S8O+Q=
Received: by 10.223.121.193 with SMTP id i1mr13834141far.77.1281164445316; Sat, 07 Aug 2010 00:00:45 -0700 (PDT)
Received: from windows8d787f9 ([109.65.11.133]) by mx.google.com with ESMTPS id w11sm929858fao.37.2010.08.07.00.00.42 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 07 Aug 2010 00:00:43 -0700 (PDT)
From: Roni Even <ron.even.tlv@gmail.com>
To: 'Sebastian Kiesel' <ietf-alto@skiesel.de>, "'Thomson, Martin'" <Martin.Thomson@andrew.com>
References: <8B0A9FCBB9832F43971E38010638454F03EB773643@SISPE7MB1.commscope.com> <20100726210234.GC5290@nat01e.ehlo.wurstkaes.de>
In-Reply-To: <20100726210234.GC5290@nat01e.ehlo.wurstkaes.de>
Date: Sat, 07 Aug 2010 09:59:17 +0300
Message-ID: <4c5d049b.4b6adf0a.039b.38eb@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcstBeiPdUtOailJS62aXIshn9I5AwI96z4w
Content-Language: en-us
Cc: alto@ietf.org
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: Sat, 07 Aug 2010 07:00:15 -0000

Sebastian,
The current version tries also to address what you call "normal" ALTO server
discovery and the authors said that a name change will follow.
There is also draft-song-alto-server-discovery-03 that tried to address the
points made in previous meeting and I thought that the direction was to
merge both drafts and have just one.

Roni Even

> -----Original Message-----
> From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of
> Sebastian Kiesel
> Sent: Tuesday, July 27, 2010 12:03 AM
> To: Thomson, Martin
> Cc: alto@ietf.org
> Subject: Re: [alto] the discovery problem
> 
> Martin,
> 
> On Mon, Jul 26, 2010 at 07:51:06PM +0800, Thomson, Martin 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.
> 
> This might be true for the "normal" ALTO server discovery, when the
> ALTO client is located in the resource consumer (e.g., peer of a p2p
> app), which will eventually access the desired resource.
> 
> The 3pdisc use case is different:
> 
> Host "B" (e.g., a tracker) connected to an arbitrary network receives
> an
> inbound TCP/UDP flow from another host "A" (e.g., peer) in another
> arbitrary access network.  We do not want to make any assumptions on
> the
> L7 protocol, so all "B" knows is the source IP in the packets that
> belongs to "A" (or to the outermost NAT box in front of "A", which
> should be enough for our purposes, carrier-grade NAT might need
> additional discussion).  Knowing only this IP address, host "B" then
> needs to discover an ALTO server that can give guidance for optimizing
> host A's peer selection.
> 
> This seems to be basically the same scenario as described in sec. 3.2
> of
> http://tools.ietf.org/id/draft-thomson-geopriv-res-gw-lis-discovery-
> 03.txt
> What happened to that draft?
> 
> 
> Thanks,
> Sebastian
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto

v2.23.0 | Report a Bug | By Email