Re: [alto] Warren Kumari's Discuss on draft-ietf-alto-xdom-disc-04: (with DISCUSS)

Sebastian Kiesel <ietf-alto@skiesel.de> Wed, 19 December 2018 15:41 UTC

Return-Path: <sebi@gw01.ehlo.wurstkaes.de>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A239C126CC7; Wed, 19 Dec 2018 07:41:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9aReoumKxkHg; Wed, 19 Dec 2018 07:41:47 -0800 (PST)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [IPv6:2a02:a00:e000:116::41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D80B41286D9; Wed, 19 Dec 2018 07:41:44 -0800 (PST)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.89) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1gZdyd-0004oM-4m; Wed, 19 Dec 2018 16:41:39 +0100
Date: Wed, 19 Dec 2018 16:41:39 +0100
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Cc: Warren Kumari <warren@kumari.net>, alto@ietf.org, alto-chairs@ietf.org, draft-ietf-alto-xdom-disc@ietf.org, The IESG <iesg@ietf.org>, Jan Seedorf <jan.seedorf@hft-stuttgart.de>
Message-ID: <20181219154139.bv3tfxnu7c3qd44p@gw01.ehlo.wurstkaes.de>
References: <154516546501.5516.6260976046434363502.idtracker@ietfa.amsl.com> <20181218232300.634bfvvny6jh3r3f@gw01.ehlo.wurstkaes.de> <CAHw9_iL+n0d0CejmD==ciROOTpUkjjLPSdZuYjbVxAgim5dojw@mail.gmail.com> <92EDF993-76B5-45EF-BB30-FAE6A603ECA7@kuehlewind.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <92EDF993-76B5-45EF-BB30-FAE6A603ECA7@kuehlewind.net>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/DTvyWvSQSaBOH2WfPkU_fNm10Lo>
Subject: Re: [alto] Warren Kumari's Discuss on draft-ietf-alto-xdom-disc-04: (with DISCUSS)
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Wed, 19 Dec 2018 15:41:50 -0000

Hi Mirja,

The "don't do this on your laptop" is already in section 5.1.1:

[...] Therefore, using the procedures specified
in this document for resource consumer based ALTO server discovery is
generally NOT RECOMMENDED. 

Sebastian

On Wed, Dec 19, 2018 at 04:14:45PM +0100, Mirja Kuehlewind (IETF) wrote:
> Hi Warren, hi all,
> 
> > Am 19.12.2018 um 01:48 schrieb Warren Kumari <warren@kumari.net>;:
> > 
> > On Tue, Dec 18, 2018 at 6:23 PM Sebastian Kiesel <ietf-alto@skiesel.de>; wrote:
> > Warren,
> > 
> > apologies if I restate something obvious, but the key issue for this
> > discussion is probably that the XDOM procedure is NOT supposed to be run
> > on your laptop, but instead on a centralized server such as a Content
> > Delivery Networks's (CDN) HTTP redirect server, a P2P tracker, etc.,
> > i.e., a "resource directory" in the terminology defined in RFC 5693.
> > 
> > 
> > Ah, you might be restating something obvious, but I'd certainly missed the above bit / had gotten that part backwards... 
> 
> 
> Is there anything that could/should be done to further clarify/make it more obvious in the draft? Like „Warning, don’t do this on your laptop“ ;-) … or more like some operational considerations?
> 
> Mirja
> 
>