Re: [alto] I-D Action: draft-ietf-alto-unified-props-new-03.txt

Jan Seedorf <ietf@j-f-s.de> Fri, 16 March 2018 19:09 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 062BD129515 for <alto@ietfa.amsl.com>; Fri, 16 Mar 2018 12:09:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 LH7vjkvv4O3G for <alto@ietfa.amsl.com>; Fri, 16 Mar 2018 12:08:58 -0700 (PDT)
Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.75]) (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 157A4120727 for <alto@ietf.org>; Fri, 16 Mar 2018 12:08:57 -0700 (PDT)
Received: from Jans-MacBook-Air.local ([93.221.204.51]) by mrelayeu.kundenserver.de (mreue103 [212.227.15.183]) with ESMTPSA (Nemesis) id 0Ld3z6-1eF5aq19Mm-00iAjX for <alto@ietf.org>; Fri, 16 Mar 2018 20:08:56 +0100
To: alto@ietf.org
References: <152027137044.14531.5682402665531273162@ietfa.amsl.com> <031cfc63-716f-6215-d16b-e97f477d85a5@j-f-s.de> <HE1PR0702MB3738BF945BA8A635D6F1E97E95D70@HE1PR0702MB3738.eurprd07.prod.outlook.com>
From: Jan Seedorf <ietf@j-f-s.de>
Message-ID: <7ef85ec9-8de6-d706-44c7-88457b769fb0@j-f-s.de>
Date: Fri, 16 Mar 2018 20:08:55 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <HE1PR0702MB3738BF945BA8A635D6F1E97E95D70@HE1PR0702MB3738.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Provags-ID: V03:K0:U/iE0dia+5Qm4Bhb4J5ulp4HLZU3SRz+vLk+9O9p0B+ai3LgO1S 05Kej6CnaVmWlYqiTbd1+JRlQUKNxrIqTFBR0JDWZKdz6rxNeQ3JWiHejmw2qH6NdOvaeNU Z1bQwvOgTLNTrCRYi44L56hAA10LYlKWg6/Ugn2lOle6RtI38M/Eur1fFiqS55UbqZF8D+P HlrKLzopmth+DkWyn40mA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:10yJUiJBIuc=:ZJFdh4ktIRR2pUaPL0uiJt wKnqJEeuhJVrbxt1UTBNLbRFxnQFRs9JDjeDWwBCYovR9mEWCa4lyuxJ9X8S6NYnzgHki9JQY OjkdKuemaQSM6qtjvCuff4Z0dtObQpLLFoocBUiYTrUFjPRQ3weIzlS8ui+aoeMHs6tMDPJB1 zQ9adH2yxE6XQwnwLMjgRd1IlCu0B0Q8u1kFuKb33if4zsPwGha7E97OSKpWzeNxgbV3qjqDp uu95nnGYWEgpfUsjPX4G8MqrxuXLYA1raYw6xTKTNfkh1bk+XkvIa7ppPNl4suhFAiQtUnSLA xB94XyfSTEw0u8hHKHtMvqDjoU+plb3Uxemb6Klqoykfq8NaFT3YzRcg2bPbtFrN0uc5tBzhh HkPR3Jssh2oaEVv+3EYvT056HCBUrCWy91febd4WQzhFTyxA7lP6T145yP9wPtbtBNWEEmvKR cKR272FdvJb0YzrCm4V5DrB3Xa2SYyGc1gY51B4KYNu+iHPO2Zp276qrn0m98rSwCDsqsqNCi Fe1Ifek81btpm6pOoiOkLTa/YFWI2OA1lB7YkLuSG3D1oiwItB3iKlb+7t09Z+mZKmrx4IogH 5WKLm4one41yKyJexDtyp4AUnO8tbpFbNO3Nu6rUlyxXq9MT4K01VJH9oDZDe9MPUtKoOwas6 pl4wGRw5Yhuic8WfhczjNrwslikYSAkSQ7X7yaWaV87FxcjpEWQc/kCyTOlJy9xlbTQ6Dh9x0 YdDhXyK74BstRMPS8VbLq286X6heWi0Wu2ouqj3XYWDK2b0Lsojhu4CfvWA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/oyaY8X-BLmwzZGgDxfJ2QZHXkpI>
Subject: Re: [alto] I-D Action: draft-ietf-alto-unified-props-new-03.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 16 Mar 2018 19:09:01 -0000

Hi Sabine,

thanks for your answer; yes, that answers my question. That means that 
we can move UP ahead and your cellular address draft may add such 
endpoints at a later point in time.

  - Jan


On 16.03.18 15:12, Randriamasy, Sabine (Nokia - FR/Paris-Saclay) wrote:
> Hi Jan,
>
> The current option is to keep the cellular addresses in a separate draft. Upon discussion among its authors, the UP draft focuses on the introduction of a new service information resource which is the (Filtered) Property Map service, applied to "entities" that extend from Endpoints to PIDs, ANEs, Cells and other potential entities. So the UP draft would provide the framework to convey Property Maps and introduce new Entities.
>   
> The definition of specific entities such as cells and ANEs are respectively located in the "ALTO Cellular Addresses" and "Path Vector" drafts.
> The impact of cellular addresses and the UP draft is that cells are both entities and endpoints, and this has raised the need to further harmonize the usage of ALTO Address Type and ALTO Domain Type registries. Specifications in this direction have been added in section if the UP draft section on IANA considerations.
>
> Hope this answers your question,
> Sabine
>   
>
> -----Original Message-----
> From: alto [mailto:alto-bounces@ietf.org] On Behalf Of Jan Seedorf
> Sent: Thursday, March 15, 2018 11:28 PM
> To: alto@ietf.org
> Subject: Re: [alto] I-D Action: draft-ietf-alto-unified-props-new-03.txt
>
> Authors,
>
> can you please update the WG regarding the following:
>
>> I am taking a look again at the possibility of integrating cellular
>> into UP quickly. An alternative is that we get it done shortly, in the
>> next couple days.
>>
>> If this is the approach, Sabine is a great person to work together.
>> Make sense, Sabine?
> So, has this been done for UP-03, or are we moving UP and path vector ahead and will add cellular addresses later on?
>
>    - Jan
>
>
> On 05.03.18 18:36, internet-drafts@ietf.org wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF.
>>
>>           Title           : Unified Properties for the ALTO Protocol
>>           Authors         : Wendy Roome
>>                             Shiwei Dawn Chen
>>                             Sabine Randriamasy
>>                             Y. Richard Yang
>>                             Jingxuan Jensen Zhang
>> 	Filename        : draft-ietf-alto-unified-props-new-03.txt
>> 	Pages           : 27
>> 	Date            : 2018-03-05
>>
>> Abstract:
>>      This document extends the Application-Layer Traffic Optimization
>>      (ALTO) Protocol [RFC7285] by generalizing the concept of "endpoint
>>      properties" to other entity domains, and by presenting those
>>      properties as maps, similar to the network and cost maps in ALTO.
>>
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-alto-unified-props-new/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-alto-unified-props-new-03
>> https://datatracker.ietf.org/doc/html/draft-ietf-alto-unified-props-ne
>> w-03
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-unified-props-new-03
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto