Re: [alto] Progress on CDNI FCI Draft

Jan Seedorf <ietf@j-f-s.de> Thu, 04 July 2019 10:24 UTC

Return-Path: <ietf@j-f-s.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 42130120025; Thu, 4 Jul 2019 03:24:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 Z1VUkN9dAiEi; Thu, 4 Jul 2019 03:24:34 -0700 (PDT)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EFD412001B; Thu, 4 Jul 2019 03:24:33 -0700 (PDT)
Received: from Jans-MacBook-Air.local ([89.246.121.159]) by mrelayeu.kundenserver.de (mreue010 [212.227.15.167]) with ESMTPSA (Nemesis) id 1N8XkP-1idiCk0sGv-014XYM; Thu, 04 Jul 2019 12:24:31 +0200
To: Jensen Zhang <jingxuan.n.zhang@gmail.com>, draft-ietf-alto-cdni-request-routing-alto@ietf.org, IETF ALTO <alto@ietf.org>
References: <CAAbpuyq8QRYYvn_rO37V_vqkB-zwCZpyP3XL56OZwGgzRukmZA@mail.gmail.com>
From: Jan Seedorf <ietf@j-f-s.de>
Message-ID: <1656ec7c-71ee-6e27-53da-6323f362df19@j-f-s.de>
Date: Thu, 04 Jul 2019 12:24:25 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <CAAbpuyq8QRYYvn_rO37V_vqkB-zwCZpyP3XL56OZwGgzRukmZA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------9FC102158FF9EA90F9761D8B"
Content-Language: en-US
X-Provags-ID: V03:K1:mOv9Vz2w0KRlFObVEzK0qmA8zlncMNHgSZpoGelyEBzfkR+awUf UxivakVOanHPmvVZ6tUwaAzUMU2+4UEcVqJMoArERKimasbcQqQ5LJEtRKROvEumPDIrq43 XVVFol6B3qtwTGbzp+B4O6TLpm2TSQoYGA8DeD2EKatcdUWJ29/01/ar+Z2oz2KtncBHX6Z RvHwYGxJZ6ZIDWo73klQQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:EHjv08JZQ2o=:sBQec8jcJq6p2ddSKGI+zI /LSgVmbPY+VH6b2BgQKZNtMcx3Tct+bTuO0RP8EYYGCZw61EtlVyICIoyjpBkLxGanl82vcO+ ou1ZO3gPCe630ZEEDvNqlIuvA73ou3NMov+XZkPgG1dx8PBxEKGMswRPFh+cpJrKBz0nxkfLI ooHC3SdJ0Sqyr7iwgJaUPP019NOSVA5PRDy9f+9woGFq0unTpVhF82Sn2IKp0I2DSo8RU08dw OcmpDl5EJY9eoQCr5vBvVp89JLDcCrWNcEcsbU47lYdFZ4h+P6FBOnhcraSN/pkKzBbTPlhw0 pcZkY4BBi2QtEj/A4EpctAfH3WeclUqm2OenhhOLYxHUk9c/3gXF37OmxekX9a8KZ4Fw4SN+c JVzKLfCX7MiQcPnpQ+NP+gorJdJrdGgtrfbILTob00BVGtmUryZDq8l/bFMwUJOtdFbOuqaHw 7qy7y/NyEqTAil7y848aeAK6lQVK/f5Enh/7N8jasVJ6+N9w1iwwi+0nP5waFdwLx/TqiIUXM DU8s8sGVhbO0lYhzCP+XGj2VlPaIc7soHZrF7gXmsfoeaAbvdyWmU2wWSHS8N7gDHbUeXzQi9 tLyXzMlsDyUn5CsD/BMaAg6CQWJm0jABg+ivmHfH1L2FJDQ9FUkhcLbsPVN2AZKvA9WFYrWEy 7K2D6MOrBJUGB+lEZNpMqJI+TIB6Yh55j3vvlKWwi5aIL7QhzfZeXcXX76eWqF26CrSGEbPlW ALbB7unREDUWJFddzjvhCfZUaH+zzmNGFAzl12lEQ3e9Dv5Ks0kBq0Fd82I=
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/Ym01oSt0Uij33SlqxtWUkHRoNFQ>
Subject: Re: [alto] Progress on CDNI FCI Draft
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: Thu, 04 Jul 2019 10:24:36 -0000

Dear Jensen,

it is too late for such drastic design changes. What has long been 
agreed in the CDNI WG is that RFC8006/8008 define the JSON format for 
CDNI which suit the CDNI requirements. These had been discussed in CDNI 
for many years at many meetings. So that is fixed. What we need to do in 
ALTO is design an ALTO-based transport for these JSON objects, i.e. 
fefining a new ALTO service for the JSON objects specified in RFC8006/8008.

  - Jan

On 03.07.19 15:30, Jensen Zhang wrote:
> Hi authors of draft-ietf-cdni-request-routing-alto,
>
> Do we have any updates on the CDNI FCI document since IETF 104? 
> Considering the CDNI FCI is an important use case of ALTO and a 
> potential use case of the unified properties, I would like to resume 
> the discussion and make this work move forward.
>
> I have the following questions to the current CDNI FCI document:
>
> 1. According to the discussion we did in IETF 104, the design of the 
> original CDNI FCI encoding in RFC8006/8008 is not an object-map. So it 
> does not match the Map service design in the ALTO framework. Do we 
> still want to reuse the encoding, or design new encodings to match the 
> ALTO Map service framework?
> 2. Do we strongly require a more general query service for CDNI FCI? 
> And what kind of queries are really required? Could we have some use 
> cases to motivate the requirements?
>
> I would like to engage in the discussion and the document revision 
> if possible. I am looking forward to receiving the feedback from 
> coauthors and other WG members.
>
> Thanks,
> Jensen