[alto] Fwd: I-D Action: draft-ietf-alto-xdom-disc-02.txt

2018-03-05 Thread Sebastian Kiesel 
Dear ALTO WG folks,

this new version of the Cross-Domain Server Discovery draft gives
a better specification of the discovery procedure (Ch. 2), without 
changing it.  We hope that it addresses all comments from the reviews
of last summer. Thanks again to all reviewers, and as allways: further
comments are most welcome!

cheers,
Sebastian

- Forwarded message from internet-dra...@ietf.org -

Date: Mon, 05 Mar 2018 11:56:18 -0800
From: internet-dra...@ietf.org
To: i-d-annou...@ietf.org
Cc: alto@ietf.org
Subject: [alto] I-D Action: draft-ietf-alto-xdom-disc-02.txt


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   : Application Layer Traffic Optimization (ALTO) 
Cross-Domain Server Discovery
Authors : Sebastian Kiesel
  Martin Stiemerling
Filename: draft-ietf-alto-xdom-disc-02.txt
Pages   : 31
Date: 2018-03-05

Abstract:
   The goal of Application-Layer Traffic Optimization (ALTO) is to
   provide guidance to applications that have to select one or several
   hosts from a set of candidates capable of providing a desired
   resource.  ALTO is realized by a client-server protocol.  Before an
   ALTO client can ask for guidance it needs to discover one or more
   ALTO servers that can provide suitable guidance.

   In some deployment scenarios, in particular if the information about
   the network topology is partitioned and distributed over several ALTO
   servers, it may be needed to discover an ALTO server outside of the
   own network domain, in order to get appropriate guidance.  This
   document details applicable scenarios, itemizes requirements, and
   specifies a procedure for ALTO cross-domain server discovery.

   Technically, the procedure specified in this document takes one
   IP address or prefix and a U-NAPTR Service Parameter (i.e., "ALTO:
   http" or "ALTO:https") as parameters.  It performs DNS lookups (for
   NAPTR resource records in the in-addr.arpa. or ip6.arpa. tree) and
   returns one or more URI(s) of information resources related to that
   IP address or prefix.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-alto-xdom-disc/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-alto-xdom-disc-02
https://datatracker.ietf.org/doc/html/draft-ietf-alto-xdom-disc-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-xdom-disc-02


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

- End forwarded message -

___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

[alto] I-D Action: draft-ietf-alto-xdom-disc-02.txt

2018-03-05 Thread internet-drafts 

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   : Application Layer Traffic Optimization (ALTO) 
Cross-Domain Server Discovery
Authors : Sebastian Kiesel
  Martin Stiemerling
Filename: draft-ietf-alto-xdom-disc-02.txt
Pages   : 31
Date: 2018-03-05

Abstract:
   The goal of Application-Layer Traffic Optimization (ALTO) is to
   provide guidance to applications that have to select one or several
   hosts from a set of candidates capable of providing a desired
   resource.  ALTO is realized by a client-server protocol.  Before an
   ALTO client can ask for guidance it needs to discover one or more
   ALTO servers that can provide suitable guidance.

   In some deployment scenarios, in particular if the information about
   the network topology is partitioned and distributed over several ALTO
   servers, it may be needed to discover an ALTO server outside of the
   own network domain, in order to get appropriate guidance.  This
   document details applicable scenarios, itemizes requirements, and
   specifies a procedure for ALTO cross-domain server discovery.

   Technically, the procedure specified in this document takes one
   IP address or prefix and a U-NAPTR Service Parameter (i.e., "ALTO:
   http" or "ALTO:https") as parameters.  It performs DNS lookups (for
   NAPTR resource records in the in-addr.arpa. or ip6.arpa. tree) and
   returns one or more URI(s) of information resources related to that
   IP address or prefix.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-alto-xdom-disc/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-alto-xdom-disc-02
https://datatracker.ietf.org/doc/html/draft-ietf-alto-xdom-disc-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-xdom-disc-02


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] The new version of "Unicorn: Resource Orchestration for Multi-Domain, Geo-Distributed Data Analytics" has been uploaded for review.

2018-03-05 Thread Qiao Xiang 
Dear WG members,

I just uploaded a new version of the draft “Unicorn: Resource Orchestration
for Multi-Domain, Geo-Distributed Data Analytics” under the I-D
draft-xiang-alto-multidomain-analytics-01.txt. Compared with the 00
version, some major updates are mode. The following is the excerpt:

1. Add an overview of the characteristics of multi-domain, geo-distributed
data analytics.
2. Based on the above characteristics, add the design requirements of the
resource orchestration for multi-domain, geo-distributed data analytics.
3. Add a review of existing resource orchestration system designs for data
analytics systems.
4. Update the architecture of the Unicorn system.
5. Update the motivation of using ALTO as the key information model in
Unicorn.
6. Give the design details of the three-phase resource discovery in Unicorn.
7. Design an ALTO extension for privacy-preserving interdomain resource
information aggregation.

Any comments and feedback would be of great help to improve the design and
the draft and much appreciated it. Thank you very much. :-)


Best
Qiao Xiang
-- 
Qiao Xiang
Postdoctoral Fellow,
Department of Computer Science,
Yale University
___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

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

2018-03-05 Thread internet-drafts 

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-new-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] I-D Action: draft-ietf-alto-path-vector-03.txt

2018-03-05 Thread internet-drafts 

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   : ALTO Extension: Path Vector Cost Type
Authors : Greg Bernstein
  Shiwei Dawn Chen
  Kai Gao
  Young Lee
  Wendy Roome
  Michael Scharf
  Y. Richard Yang
  Jingxuan Jensen Zhang
Filename: draft-ietf-alto-path-vector-03.txt
Pages   : 25
Date: 2018-03-05

Abstract:
   The Application-Layer Traffic Optimization (ALTO) protocol [RFC7285]
   has defined several resources and services to provide clients with
   basic network information.  However, the base ALTO protocol and
   latest extensions only provide end-to-end metrics, which are
   insufficient to satisfy the demands of solving more complex network
   optimization problems.  This document introduces an extension to the
   base ALTO protocol, namely the path-vector extension, which allows
   ALTO clients to query information such as capacity regions for a
   given set of flows.  A non-normative example called multi-flow
   scheduling is presented to illustrate the limitations of existing
   ALTO (endpoint) cost maps.  After that, details of the extension are
   defined.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-alto-path-vector/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-alto-path-vector-03
https://datatracker.ietf.org/doc/html/draft-ietf-alto-path-vector-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-path-vector-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] Agenda requests for London IETF

2018-03-05 Thread Vijay K. Gurbani 
Folks: Pursuant to the call for agenda requests on Feb-17 [1], we have
only received a couple of agenda requests.

If you have sent them out, please make sure that you Cc both Jan and me,
and please make sure you get an acknowledgement.

If you have not sent them out, you should do so today as draft agendas
are due on Wednesday (tomorrow).

[1] https://www.ietf.org/mail-archive/web/alto/current/msg03606.html

Cheers,

- vijay
--
Vijay K. Gurbani / vijay.gurb...@nokia.com
Network Data Science, Nokia Networks
Calendar: http://goo.gl/x3Ogq

___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

Re: [alto] Agenda requests for IETF 101 in London

2018-03-05 Thread Danny Alex Lachos Perez 
Dear ALTO WG chairs.

I would like to request a slot to present the draft of “ALTO-based
Broker-assisted Multi-domain Orchestration”:

Time needed: 10-15 minutes
Name of presenter: Danny Alex Lachos Perez
I-D: https://datatracker.ietf.org/doc/draft-lachosrothenberg-alto-brokermdo/

Thanks in advance for the consideration.

Cheers,

Danny Lachos

On Sat, Feb 17, 2018 at 7:55 PM, Jan Seedorf  wrote:

> Dear all,
>
> please let us (the chairs) know if you want to present during the ALTO
> session at IETF-101 in London.
>
> We really want to make progress with the milestones, so clear preference
> in the agenda will be given to documents that address the milestones.
>
> We hope to see many of you in London,
>
> Vijay & Jan
>
> ___
> 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

Re: [alto] unified-props, cellular addresses and path-vector - registry

2018-03-05 Thread Randriamasy, Sabine (Nokia - FR/Paris-Saclay) 
Hi,

Definitely there is a need to expose the motivation to cell addresses 
registered in the ALTO address type registry and the ALTO domain registry.  For 
the moment, I will add the related text to the 
[draft-randriamasy-alto-cellular-adresses] draft.
Thanks,
Sabine


From: yang.r.y...@gmail.com [mailto:yang.r.y...@gmail.com] On Behalf Of Y. 
Richard Yang
Sent: Saturday, March 03, 2018 12:44 AM
To: Jensen Zhang 
Cc: Randriamasy, Sabine (Nokia - FR/Paris-Saclay) 
; alto@ietf.org
Subject: Re: [alto] unified-props, cellular addresses and path-vector - registry

Hi Jensen,

Thanks for the comments. Please see below.

On Thu, Mar 1, 2018 at 3:12 AM, Jensen Zhang 
> wrote:
Hi Sabine, all

Let me post some considerations on this topic. Please see my comments inline.
On Wed, Feb 28, 2018 at 6:17 AM Randriamasy, Sabine (Nokia - FR/Paris-Saclay) 
>
 wrote:
Hi Jensen, Kai, Vijay, all

Thanks all for this discussion on registries, which needs a separate thread so 
I added “registry” to the initial thread.
The ALTO Entity Domain Registry of the Unified Properties (UP) draft is to be 
seen as an extension of the ALTO Address Type Registry specified in RFC 7285. 
Indeed ipv4 and ipv6 map to both ALTO Address Type and ALTO Domain Type where 
the latter set covers the first one.

Yes. I think the goal of the ALTO Entity Domain Registry is to be an extension 
of the ALTO Address Type Registry. But the relationship between these two 
registries need to be clarified in the documents.

This is a good discussion. I can see two views regarding the extension word:
1. ALTO Entity Domain Registry is a superset of ALTO Address Type Registry;
2. ALTO Entity Domain Registry and ALTO Address Type Registry are two distinct 
sets, and we only want the intersection to be specified consistently.

My understanding/view is one, and we should make it clear.


Definitely, Jensen’s explanations (items 1) and 2) ) in his e-mail of Feb 27, 
2018 at 3:10 PM should be used in sections 2.7 or 9.2 of the UP draft to 
clarify the relation between both.

Yes, agree. I will edit it.

OK. Let's edit it.


For section 9.2  of the UP draft, I agree with Jensen’s views and understand 
Kai’s concerns. We may consider adding a sentence generalized from Sections 
3.1.1.2 and 3.1.2.2 to have something like :
"When a new address type is registered in the ALTO Address Type Registry of 
[RFC7285], the same identifier MUST be also registered in the ALTO Entity 
Domain Registry. And the Entity Address Encoding for this entity domain 
identifier MUST cover both Address Encoding and Prefix Encoding of the same 
identifier registered in the ALTO Address Type Registry [RFC7285]."
“For the purpose of defining properties, an individual Entity address and the 
corresponding full-length prefix are considered aliases for the same entity.”

Yes, such a sentence is helpful.

Would this help addressing the issue?

Yes, enforce address type registered as entity domain can help to guarantee 
consistency. But I think it is not enough.

Considering a prior document registers a new entity domain called 'AAA' first, 
the 'AAA' can be a valid entity domain but not a valid address type at this 
moment. Then, another later document registers a new address type also called 
'AAA'. If the encoding of the address type 'AAA' is not consistent with the 
encoding of the entity domain 'AAA', there will be some issue.

So I propose we add a new column in the ALTO Entity Domain Registry table, 
maybe called 'Valid for ALTO Addresses', to indicate which entity domain can 
also be used as an address type and which cannot. Those entity domains marked 
as 'Valid for ALTO Addresses' don't have to be registered in ALTO Address Type 
Registry again. In this way, we can make 'ALTO Entity Domain Registry' a 
superset of 'ALTO Address Type Registry'. But of course, other columns of the 
ALTO Entity Domain Registry should be adjusted to distinguish individual 
address encoding from the prefix/block address encoding.

Any thougthts?


This seems to be a good idea---I always like syntax enforced consistency.

Thanks!
Richard


Thanks,
Jensen


Thanks,
Sabine



From: alto [mailto:alto-boun...@ietf.org] On 
Behalf Of Jensen Zhang
Sent: Tuesday, February 27, 2018 10:11 AM
To: Kai Gao >
Cc: alto@ietf.org
Subject: Re: [alto] unified-props, cellular addresses and path-vector

Hi Kai,

Thanks for your comment. See inline.
On Tue, Feb 27, 2018 at 4:38 PM Kai Gao 
> wrote:
Hi Jensen,

Please see inline.

On 02/27/2018 03:44 PM, Jensen Zhang wrote:
Hi all,

Continue the discussion above. I suggest modifying the first