Subject: [alto] FW: New Version Notification for draft-deng-alto-p2p-ext-06.txt

From: Lingli Deng <[email-masked]>
Date: Thu, 11 Jun 2015 02:19:23 +0000

Date: Thu, 11 Jun 2015 09:19:47 +0800
From: [email-masked]
To: [email-masked]; [email-masked]
Subject: Fw:New Version Notification for draft-deng-alto-p2p-ext-06.txt

Hi all,
We posted a new revision for extended endpoint properties, which is updated according to suggestions and comments gathered in Dallas.  Please refer to the following remarks to the discussion minutes for further clarifications.Your review and comments would be more than welcome.
Regards,Lingli
**from alto@ietf92 minutes**draft-deng-alto-p2p-ext-05JS: should we hold information that changes frequently (like 2G/3G/4G)?[dll]: 06 version updated and use "cellular" for "2G/3G/4G" instead of "2G", "3G" and "4G", which can be subject to frequent changes.VG (Vijay Gurbani): How to prevent revealing private information?[dll]: There is a dedicated section describing the privacy protection mechanism that might be used by ALTO for endpoint property.In a word, the privacy protection requirement is considered to be an application-specific, property-specific and operator-specific,which can be addressed by introduction of privacy protection mapping in property definition and policy configuration.Where the general mechanism for privacy protectionJS: Max bandwidth / best technology for a given endpoint may be more stable.[dll] Bandwidth related information has been defined as one of the subscription related property "provisioned_bandwidth" in Section 4.4.2.JS: Who has read a document? 2 hands raised.RY: Document touches dynamics and privacy.JS: This topic is returning. According to IESG, ALTO is not for TE and avoiding congestions, information changing within seconds are out of scope. Daily - in scope.[dll] In the text, it is clearly stated that dynamic congestion related information is out of scope for endpoint properties. However, there is no clear boundary between which is in scope and which is not.RY: What is too dynamic, what is not?JS (as indiv.): 3G/4G is too dynamic.[dll] Changed into cellular in the latest version.JS: Rich Woundy was always concerned about disclosing business information.RY: Privacy is a serious issue.[dll] Privacy is an honoured requirement. General considerations and guidelines are stated in Section 3.3.And for each property specified afterwards, property-specific privacy considerations are stated respectively.Take network_access for instance: There is concern about undesirable privacy leakage via network_access properties to distrusted ALTO clients. In such cases, according to the definitions above, either the endpoint itself or the ISP who is running the ALTO server can either specify an access control policy to prevent undesirable exposure to specific ALTO clients or use a privacy preserving mapping from the raw description of access technologies to a number of abstract relative ranking information instead. Moreover, the endpoint or the ISP might choose to use another subscription related property "provisioned_bandwidth" (defined later in Section 4.4.2) instead of "network_access".SS (Sergey Slovetskiy): What defines what is in scope / out of scope?JS: ALTO Prolem StatementSS: Fast-changing properties may be important for CDNs.[dll]: Would be happy to hear more about this consideration, and let the WG decide if they are suitable to be defined as endpoint properties.

---------
邓灵莉

中国移动通信研究院

[email-masked]
----邮件原文----
发件人：internet-drafts <[email-masked]>
收件人：Haibin Song <[email-masked]>,Qin Wu <[email-masked]>,Wenson Wu <[email-masked]>,Richard Yang <[email-masked]>,Haibin Song <[email-masked]>,Deng Lingli <[email-masked]>,Sebastian Kiesel <[email-masked]>,Yang Yang <[email-masked]>,Lingli Deng <[email-masked]>,Sebastian Kiesel <[email-masked]>
抄　送: (无)
发送时间：2015-06-11 09:09:45
主题：New Version Notification for draft-deng-alto-p2p-ext-06.txt

A new version of I-D, draft-deng-alto-p2p-ext-06.txt

has been successfully submitted by Lingli Deng and posted to the

IETF repository.

Name:		draft-deng-alto-p2p-ext

Revision:	06

Title:		Extended End Point Properties for Application-Layer Traffic Optimization

Document date:	2015-06-10

Group:		Individual Submission

Pages:		18

URL: https://www.ietf.org/internet-drafts/draft-deng-alto-p2p-ext-06.txt

Status: https://datatracker.ietf.org/doc/draft-deng-alto-p2p-ext/

Htmlized: https://tools.ietf.org/html/draft-deng-alto-p2p-ext-06

Diff: https://www.ietf.org/rfcdiff?url2=draft-deng-alto-p2p-ext-06

Abstract:

 The purpose of the Application-Layer Traffic Optimization (ALTO)

 protocol is to provide better-than-random peer selection for P2P

 networks. The base ALTO protocol focuses, only on providing network

 topological location information (i.e., network maps and cost maps).

 However, the peer selection method of an endpoint may also use other

 properties, such as geographic location. This document defines a

 framework and an extended set of End Point properties (EP properties)

 to extend the base ALTO protocol.

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.

The IETF Secretariat

Subject：New Version Notification for draft-deng-alto-p2p-ext-06.txt

A new version of I-D, draft-deng-alto-p2p-ext-06.txt

has been successfully submitted by Lingli Deng and posted to the

IETF repository.

Name:		draft-deng-alto-p2p-ext

Revision:	06

Title:		Extended End Point Properties for Application-Layer Traffic Optimization

Document date:	2015-06-10

Group:		Individual Submission

Pages:		18

URL: https://www.ietf.org/internet-drafts/draft-deng-alto-p2p-ext-06.txt

Status: https://datatracker.ietf.org/doc/draft-deng-alto-p2p-ext/

Htmlized: https://tools.ietf.org/html/draft-deng-alto-p2p-ext-06

Diff: https://www.ietf.org/rfcdiff?url2=draft-deng-alto-p2p-ext-06

Abstract:

 The purpose of the Application-Layer Traffic Optimization (ALTO)

 protocol is to provide better-than-random peer selection for P2P

 networks. The base ALTO protocol focuses, only on providing network

 topological location information (i.e., network maps and cost maps).

 However, the peer selection method of an endpoint may also use other

 properties, such as geographic location. This document defines a

 framework and an extended set of End Point properties (EP properties)

 to extend the base ALTO protocol.

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.

The IETF Secretariat