
From vkg@bell-labs.com  Mon Jun  3 10:00:17 2013
Return-Path: <vkg@bell-labs.com>
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 C2E1321F8E9A for <alto@ietfa.amsl.com>; Mon,  3 Jun 2013 10:00:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.999
X-Spam-Level: 
X-Spam-Status: No, score=-107.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1CtGY10s5Djw for <alto@ietfa.amsl.com>; Mon,  3 Jun 2013 10:00:12 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 8145021F8F38 for <alto@ietf.org>; Mon,  3 Jun 2013 10:00:12 -0700 (PDT)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r53H0ANw008394 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Mon, 3 Jun 2013 12:00:11 -0500 (CDT)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r53H0Alu008395 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Mon, 3 Jun 2013 12:00:10 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r53H0AAY001920 for <alto@ietf.org>; Mon, 3 Jun 2013 12:00:10 -0500 (CDT)
Message-ID: <51ACCC7A.3000501@bell-labs.com>
Date: Mon, 03 Jun 2013 12:03:54 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130311 Thunderbird/17.0.4
MIME-Version: 1.0
To: alto <alto@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Subject: [alto] Final date/time for ALTO virtual interim
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 03 Jun 2013 17:00:17 -0000

All: Based on the poll responses received to date, the ALTO virtual
interim will be held on:

   Wednesday, Jun 19 2013 10:00 AM US Central /
                          11:00 AM US Eastern /
                           8:00 AM US Pacific /
                           5:00 PM Paris, Rome, Frankfurt /
                           4:00 PM London
   Duration: 1 hour.

Please mark your calendars.  Additional logistical information will
follow shortly.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq

From iesg-secretary@ietf.org  Mon Jun  3 13:54:39 2013
Return-Path: <iesg-secretary@ietf.org>
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 078F911E810E; Mon,  3 Jun 2013 13:54:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.454
X-Spam-Level: 
X-Spam-Status: No, score=-102.454 tagged_above=-999 required=5 tests=[AWL=0.146, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IqMIV5j5tLVO; Mon,  3 Jun 2013 13:54:29 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E720611E80EC; Mon,  3 Jun 2013 13:48:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.50
Message-ID: <20130603204844.14443.14801.idtracker@ietfa.amsl.com>
Date: Mon, 03 Jun 2013 13:48:44 -0700
Cc: alto@ietf.org
Subject: [alto] ALTO WG Virtual Interim Meetig, June 19, 2013
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 03 Jun 2013 20:54:39 -0000

This is to announce a virtual interim meeting for the ALTO Working
Group to take place on Wednesday, June 19, 2013 from 10:00 AM - 11:00
AM US Central (Chicago) time.

The goal of the meeting is to encourage real-time participation with
the anticipation of closing any lingering issues on the ALTO protocol.

A detailed agenda and logistic information will be sent out separately
to the ALTO WG mailing list. For the moment, the WG should pay close
attention to the latest version of the ALTO protocol draft:

http://tools.ietf.org/html/draft-ietf-alto-protocol-16

Thank you.

Vijay K. Gurbani and Enrico Marocco
ALTO WG Co-chairs.

From iesg-secretary@ietf.org  Thu Jun  6 07:22:09 2013
Return-Path: <iesg-secretary@ietf.org>
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 780F621F84B4; Thu,  6 Jun 2013 07:22:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.156
X-Spam-Level: 
X-Spam-Status: No, score=-102.156 tagged_above=-999 required=5 tests=[AWL=0.444, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9fOyZ+8uNqjn; Thu,  6 Jun 2013 07:22:05 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C04921F9052; Thu,  6 Jun 2013 07:21:54 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.50
Sender: <iesg-secretary@ietf.org>
Message-ID: <20130606142147.22131.10273.idtracker@ietfa.amsl.com>
Date: Thu, 06 Jun 2013 07:21:47 -0700
Cc: alto@ietf.org
Subject: [alto] Last Call: <draft-ietf-alto-server-discovery-08.txt> (ALTO Server	Discovery) to Proposed Standard
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
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: <http://www.ietf.org/mail-archive/web/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, 06 Jun 2013 14:22:09 -0000

The IESG has received a request from the Application-Layer Traffic
Optimization WG (alto) to consider the following document:
- 'ALTO Server Discovery'
  <draft-ietf-alto-server-discovery-08.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2013-06-20. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

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.

   This document specifies a procedure for resource consumer initiated
   ALTO server discovery, which can be used if the ALTO client is
   embedded in the resource consumer.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-alto-server-discovery/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-alto-server-discovery/ballot/


The following IPR Declarations may be related to this I-D:

   http://datatracker.ietf.org/ipr/1952/




From vkg@bell-labs.com  Tue Jun 11 06:42:45 2013
Return-Path: <vkg@bell-labs.com>
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 7F59221F998D for <alto@ietfa.amsl.com>; Tue, 11 Jun 2013 06:42:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gUHmUyFcTHTa for <alto@ietfa.amsl.com>; Tue, 11 Jun 2013 06:42:41 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 0BB9021F9997 for <alto@ietf.org>; Tue, 11 Jun 2013 06:42:40 -0700 (PDT)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id r5BDgeTA028512 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Tue, 11 Jun 2013 08:42:40 -0500 (CDT)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r5BDgdvi026000 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Tue, 11 Jun 2013 08:42:39 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r5BDgdOE007432 for <alto@ietf.org>; Tue, 11 Jun 2013 08:42:39 -0500 (CDT)
Message-ID: <51B72A34.7040201@bell-labs.com>
Date: Tue, 11 Jun 2013 08:46:28 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130514 Thunderbird/17.0.6
MIME-Version: 1.0
To: alto <alto@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Subject: [alto] Virtual interim meeting coordinates and agenda
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 11 Jun 2013 13:42:46 -0000

All: As announced on the list [1], the ALTO virtual interim is
scheduled as follows:

   Wednesday, Jun 19 2013 10:00 AM US Central /
                          11:00 AM US Eastern /
                           8:00 AM US Pacific /
                           5:00 PM Paris, Rome, Frankfurt /
                           4:00 PM London
   Duration: 1 hour.

The call-in number and related logistics are below.

The agenda is to drive the protocol document to completion.  Here
are the details of the agenda:

Wed Jun 19 2013 ALTO Virtual Meeting Agenda
Chairs: Enrico Marocco and Vijay Gurbani

05m Chairs             Administrivia
45m ALTO protocol      ALTO Protocol issue discussion
     authors            Draft: http://tools.ietf.org/html/draft-
                               ietf-alto-protocol-16
10m Chairs/attendees   Wrap-up and next steps

The coordinates to join Webex are below:

Topic: ALTO
Date: Wednesday, June 19, 2013
Time: 8:00 am, Pacific Daylight Time (San Francisco, GMT-07:00)
Meeting Number: 645 607 733
Meeting Password: 1234

-------------------------------------------------------
To join the online meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to 
https://ietf.webex.com/ietf/j.php?ED=225532257&UID=1566983432&PW=NM2YyODZkY2Iy&RT=MiM0
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: 1234
4. Click "Join".

To view in other time zones or languages, please click the link:
https://ietf.webex.com/ietf/j.php?ED=225532257&UID=1566983432&PW=NM2YyODZkY2Iy&ORT=MiM0

-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
Call-in toll number (US/Canada): 1-650-479-3208

Access code:645 607 733

-------------------------------------------------------
For assistance
-------------------------------------------------------
1. Go to https://ietf.webex.com/ietf/mc
2. On the left navigation bar, click "Support".

You can contact me at:
cmorgan@amsl.com
1-510-492-4085

To add this meeting to your calendar program (for example Microsoft 
Outlook), click this link:
https://ietf.webex.com/ietf/j.php?ED=225532257&UID=1566983432&ICS=MI&LD=1&RD=2&ST=1&SHA2=AAAAAtY6iMG29ba-kj-MS-/gy45HusMvtagIo--gcStf5DL4&RT=MiM0

The playback of UCF (Universal Communications Format) rich media files 
requires appropriate players. To view this type of rich media files in 
the meeting, please check whether you have the players installed on your 
computer by going to https://ietf.webex.com/ietf/systemdiagnosis.php.

Sign up for a free trial of WebEx
http://www.webex.com/go/mcemfreetrial

http://www.webex.com

CCP:+16504793208x645607733#

IMPORTANT NOTICE: This WebEx service includes a feature that allows 
audio and any documents and other materials exchanged or viewed during 
the session to be recorded. By joining this session, you automatically 
consent to such recordings. If you do not consent to the recording, 
discuss your concerns with the meeting host prior to the start of the 
recording or do not join the session. Please note that any such 
recordings may be subject to discovery in the event of litigation.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq

From enrico.marocco@telecomitalia.it  Wed Jun 19 00:56:06 2013
Return-Path: <enrico.marocco@telecomitalia.it>
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 F293D21F9A25 for <alto@ietfa.amsl.com>; Wed, 19 Jun 2013 00:56:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.644
X-Spam-Level: 
X-Spam-Status: No, score=-101.644 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245,  RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X0foE4ddkevi for <alto@ietfa.amsl.com>; Wed, 19 Jun 2013 00:56:02 -0700 (PDT)
Received: from GRFEDG702RM001.telecomitalia.it (grfedg702rm001.telecomitalia.it [217.169.121.21]) by ietfa.amsl.com (Postfix) with ESMTP id 5435821F9104 for <alto@ietf.org>; Wed, 19 Jun 2013 00:55:49 -0700 (PDT)
Received: from grfhub703rm001.griffon.local (10.19.3.10) by GRFEDG702RM001.telecomitalia.it (10.173.88.21) with Microsoft SMTP Server (TLS) id 8.3.297.1; Wed, 19 Jun 2013 09:55:47 +0200
Received: from MacLab.local (10.229.8.22) by smtp.telecomitalia.it (10.19.9.236) with Microsoft SMTP Server (TLS) id 8.3.297.1; Wed, 19 Jun 2013 09:55:47 +0200
Message-ID: <51C16402.6050007@telecomitalia.it>
Date: Wed, 19 Jun 2013 09:55:46 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: <alto@ietf.org>
References: <51B72A34.7040201@bell-labs.com>
In-Reply-To: <51B72A34.7040201@bell-labs.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms060503070401010406040306"
X-TI-Disclaimer: Disclaimer1
Subject: Re: [alto] Virtual interim meeting coordinates and agenda
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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 Jun 2013 07:56:06 -0000

--------------ms060503070401010406040306
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,

meeting materials for today's virtual interim are available at
http://www.ietf.org/proceedings/interim/2013/06/19/alto/proceedings.html

The focus of the meeting will be on the residual issues with the
protocol specification that need to be closed before moving the document
forward. The complete list of such issues is available on the protocol
slide deck (that, although still in draft form, is already worth a read).=


Enrico

On 6/11/13 3:46 PM, Vijay K. Gurbani wrote:
> All: As announced on the list [1], the ALTO virtual interim is
> scheduled as follows:
>=20
>    Wednesday, Jun 19 2013 10:00 AM US Central /
>                           11:00 AM US Eastern /
>                            8:00 AM US Pacific /
>                            5:00 PM Paris, Rome, Frankfurt /
>                            4:00 PM London
>    Duration: 1 hour.
>=20
> The call-in number and related logistics are below.
>=20
> The agenda is to drive the protocol document to completion.  Here
> are the details of the agenda:
>=20
> Wed Jun 19 2013 ALTO Virtual Meeting Agenda
> Chairs: Enrico Marocco and Vijay Gurbani
>=20
> 05m Chairs             Administrivia
> 45m ALTO protocol      ALTO Protocol issue discussion
>      authors            Draft: http://tools.ietf.org/html/draft-
>                                ietf-alto-protocol-16
> 10m Chairs/attendees   Wrap-up and next steps
>=20
> The coordinates to join Webex are below:
>=20
> Topic: ALTO
> Date: Wednesday, June 19, 2013
> Time: 8:00 am, Pacific Daylight Time (San Francisco, GMT-07:00)
> Meeting Number: 645 607 733
> Meeting Password: 1234
>=20
> -------------------------------------------------------
> To join the online meeting (Now from mobile devices!)
> -------------------------------------------------------
> 1. Go to=20
> https://ietf.webex.com/ietf/j.php?ED=3D225532257&UID=3D1566983432&PW=3D=
NM2YyODZkY2Iy&RT=3DMiM0
> 2. If requested, enter your name and email address.
> 3. If a password is required, enter the meeting password: 1234
> 4. Click "Join".
>=20
> To view in other time zones or languages, please click the link:
> https://ietf.webex.com/ietf/j.php?ED=3D225532257&UID=3D1566983432&PW=3D=
NM2YyODZkY2Iy&ORT=3DMiM0
>=20
> -------------------------------------------------------
> To join the audio conference only
> -------------------------------------------------------
> Call-in toll number (US/Canada): 1-650-479-3208
>=20
> Access code:645 607 733
>=20
> -------------------------------------------------------
> For assistance
> -------------------------------------------------------
> 1. Go to https://ietf.webex.com/ietf/mc
> 2. On the left navigation bar, click "Support".
>=20
> You can contact me at:
> cmorgan@amsl.com
> 1-510-492-4085
>=20
> To add this meeting to your calendar program (for example Microsoft=20
> Outlook), click this link:
> https://ietf.webex.com/ietf/j.php?ED=3D225532257&UID=3D1566983432&ICS=3D=
MI&LD=3D1&RD=3D2&ST=3D1&SHA2=3DAAAAAtY6iMG29ba-kj-MS-/gy45HusMvtagIo--gcS=
tf5DL4&RT=3DMiM0
>=20
> The playback of UCF (Universal Communications Format) rich media files =

> requires appropriate players. To view this type of rich media files in =

> the meeting, please check whether you have the players installed on you=
r=20
> computer by going to https://ietf.webex.com/ietf/systemdiagnosis.php.
>=20
> Sign up for a free trial of WebEx
> http://www.webex.com/go/mcemfreetrial
>=20
> http://www.webex.com
>=20
> CCP:+16504793208x645607733#
>=20
> IMPORTANT NOTICE: This WebEx service includes a feature that allows=20
> audio and any documents and other materials exchanged or viewed during =

> the session to be recorded. By joining this session, you automatically =

> consent to such recordings. If you do not consent to the recording,=20
> discuss your concerns with the meeting host prior to the start of the=20
> recording or do not join the session. Please note that any such=20
> recordings may be subject to discovery in the event of litigation.
>=20
> Thanks,
>=20
> - vijay
>=20



--------------ms060503070401010406040306
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINdzCC
BjQwggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOr
lr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSM
zR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6
qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSD
kOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQOJebr/f/h5t95
m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqD
CH14qywGXLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy
6QMVQjbbMXltUfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPI
zKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKf
KSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HOR
z9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9
sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCie
uoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7t
w1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQ
G2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t
5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIHOzCCBiOgAwIBAgIDBKfoMA0GCSqGSIb3DQEB
BQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTIwODA3MDkxNTQz
WhcNMTMwODA4MDczMzM3WjB1MRkwFwYDVQQNExBvWkNPVnNYc09NME9mcExwMSgwJgYDVQQD
DB9lbnJpY28ubWFyb2Njb0B0ZWxlY29taXRhbGlhLml0MS4wLAYJKoZIhvcNAQkBFh9lbnJp
Y28ubWFyb2Njb0B0ZWxlY29taXRhbGlhLml0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB
CgKCAQEAshI2shfUZ7P5RVcP04fJ4OfYmK/RUyokJpuJE4KaSOLArtpNtlYo6MtXfmZzA8y/
5HChSAmPvqUwhMMYh1LurWbOdX4uKXO1gsFrPOtxTa6qin6lXaJ3bo2pKnkN9mQkjvm0E23r
rrT3MC6h6UfyFAcvs01+yq9wVuxxRdC4LZTGAbXGkE34GQAnBy9eqvJ+m351hPaaVw9u8CWN
uyv9YKLXpicS/q8j2EOpFBCkZVp0E8fViSXViGtuhfbW6R+TjTXJZN06DEqb/vpRSWkvBDf0
UqDFrgmlmSnXJ/xpaygAJcHyE5qjRXkIV7adTkg9Z/Z2lJXvtDUdHbNBiYcVOwIDAQABo4ID
ujCCA7YwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsG
AQUFBwMEMB0GA1UdDgQWBBT1YgWCbkVCN8iNgS49Fh9R2ZC8wTAfBgNVHSMEGDAWgBRTcu2S
nODaywFcfH6WNU7y1LhRgjAqBgNVHREEIzAhgR9lbnJpY28ubWFyb2Njb0B0ZWxlY29taXRh
bGlhLml0MIICIQYDVR0gBIICGDCCAhQwggIQBgsrBgEEAYG1NwECAjCCAf8wLgYIKwYBBQUH
AgEWImh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwgfcGCCsGAQUFBwICMIHq
MCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRp
ZmljYXRlIHdhcyBpc3N1ZWQgYWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24g
cmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkg
Zm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGluIGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcg
cGFydHkgb2JsaWdhdGlvbnMuMIGcBggrBgEFBQcCAjCBjzAnFiBTdGFydENvbSBDZXJ0aWZp
Y2F0aW9uIEF1dGhvcml0eTADAgECGmRMaWFiaWxpdHkgYW5kIHdhcnJhbnRpZXMgYXJlIGxp
bWl0ZWQhIFNlZSBzZWN0aW9uICJMZWdhbCBhbmQgTGltaXRhdGlvbnMiIG9mIHRoZSBTdGFy
dENvbSBDQSBwb2xpY3kuMDYGA1UdHwQvMC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wu
Y29tL2NydHUxLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6
Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MxL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2
aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMS5jbGllbnQuY2EuY3J0
MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUFAAOC
AQEAIn8FoRaqvQzo8aGNi4EbPhIMX8aPIMhX3L/N+8sMyFe3cpSyjij47DW1K330zDJnoyZs
kuI10EzfK0wwY+D2qMQPGAmPDkix5t2dYQj6DKh1yBlBwAf7c65Ty1kpgtdymSptDJKVZcK6
R2CJ91oRBCZIObcWrG/0FZIr55+InAYyLDrlk34MwBmINhBZ4oRJdrzG6OC7cK4vG1ZWrAFE
GHVwx1uG2NXRUXQTH9DGYcwwfPo4uinFCwHZAJ2Il/J0Mqui5x+N/7p+WUlGRyb67qxg7ect
f2095+YDnbqIKIz7fGzw8XTwpjYbvWZplkG93qRXr8MRD9ukgxpxpHG2dTGCA90wggPZAgEB
MIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwSn6DAJBgUrDgMCGgUA
oIICHTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzA2MTkw
NzU1NDZaMCMGCSqGSIb3DQEJBDEWBBQYtAb2ukopZ4Ek6CZScpCsAtrBBzBsBgkqhkiG9w0B
CQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcN
AwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGlBgkrBgEE
AYI3EAQxgZcwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9T
dGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDBKfoMIGn
BgsqhkiG9w0BCRACCzGBl6CBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2
BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENB
AgMEp+gwDQYJKoZIhvcNAQEBBQAEggEAOMuNlJVWcVl8I184+/dhIeOjNlFztrDoGsUVy9ga
5bK7u30uFhyncYdV0jS/qkBeo62qJRIT9WIpnWx/OXChPmBSiUt89xlpGxXz7KP/oEZVsAng
aAUDtpXKIdGLGEb1yVROS8JrHvQngQ7weS/bgHOxoQ0Cl8eMdPaf3pm7PEkqJ8IhsxU9TXa2
lsYX4BL+E8itIFiyDQJrxHbHoshCvwiXNWuu2kFxrciwpG+R9dkSSezd3YIJ6ooJqkSY9vPk
BG5whYDEhnMpiec4oTu2xWlm+IhERvCE1vCS8X3tozZlAZYNC17x4MlkcEE1PrDrCz02meBv
GLTMqHewv6NhfgAAAAAAAA==
--------------ms060503070401010406040306--

From Jan.Seedorf@neclab.eu  Wed Jun 19 05:49:51 2013
Return-Path: <Jan.Seedorf@neclab.eu>
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 6AEA321F9A36 for <alto@ietfa.amsl.com>; Wed, 19 Jun 2013 05:49:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IR-hDJ+OaHh6 for <alto@ietfa.amsl.com>; Wed, 19 Jun 2013 05:49:47 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 08D8521F938E for <alto@ietf.org>; Wed, 19 Jun 2013 05:49:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id A99D51045B8 for <alto@ietf.org>; Wed, 19 Jun 2013 14:49:25 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lQFZJx6F1FYJ for <alto@ietf.org>; Wed, 19 Jun 2013 14:49:25 +0200 (CEST)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id 871DB1045B7 for <alto@ietf.org>; Wed, 19 Jun 2013 14:49:20 +0200 (CEST)
Received: from DAPHNIS.office.hd ([169.254.2.234]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0323.003; Wed, 19 Jun 2013 14:48:57 +0200
From: Jan Seedorf <Jan.Seedorf@neclab.eu>
To: IETF ALTO <alto@ietf.org>
Thread-Topic: Protocol update -16: Security Consideration Section
Thread-Index: Ac5s6L4+OEOXcz+7QwC8jJerF+qAnA==
Date: Wed, 19 Jun 2013 12:48:56 +0000
Message-ID: <2779C9F0771F974CAD742BAE6D9904FE5555A21A@DAPHNIS.office.hd>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.5.89]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [alto] Protocol update -16: Security Consideration Section
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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 Jun 2013 12:49:51 -0000

Dear all,

I read the latest version of the draft (-16), and I think it really is in g=
ood shape (apart from the open issues we will discuss in the interim meetin=
g later today). I had a closer look at the latest security considerations s=
ection, and --- thanks to Sebastian and Hannes --- it is much better struct=
ured than before and reads quite well. Below are some minor comments, all o=
f these are small things and could probably be addressed by adding a single=
 sentence each to help make clearer to the reader what the security conside=
rations are:

-- 14.1.3. Limitations to Authenticity and Integrity
The text only talks about the URI of the IRD being compromised, which is (a=
s discussed on this list) more a problem of ALTO service discovery. But wha=
t about cases where the URI domain name is correct, but the ALTO server its=
elf has been compromised by malware? In that case, even TLS might not help.=
 Is this an obvious threat or should it be explicitly mentioned?

-- 14.3.2. Protection Strategies for Confidentiality
The previous section "risk scenarios" mentions 3 types of risks, but protec=
tion strategies are only suggested for type 1 and type 2

-- 14.4.2 Protection Strategies for Privacy
Apart from using obfuscation techniques as suggested in the text, the ALTO =
client could also consider to alternate between several ALTO server when qu=
erying for ALTO information (in cases where possible, i.e. more than one AL=
TO server has the info and these ALTO servers are not expected to collude).=
 This would not help against an intercepting third party, but it would help=
 somewhat against tracking at a single ALTO server. Additionally, the class=
ic solution of a mix-net-type solution comes to mind, where an ALTO privacy=
 service would act on behalf of many clients, hiding their identity. Should=
 we add text on these considerations (again, if obvious we should probably =
not mention it)?

-- 14.5.2 Protection Strategies for Availability
Against a DDoS attack with spoofed source IPs, a simple cookie mechanism (a=
s used in IPSec to prevent complex server computations caused by forged req=
uests) could help. Of course, this would also need to be specified in an ex=
tension document.

 	- Jan

> -----Original Message-----
> From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of Y=
.
> Richard Yang
> Sent: Wednesday, May 22, 2013 3:28 AM
> To: IETF ALTO
> Subject: [alto] Protocol update
>=20
> Hi all,
>=20
> We just posted a version to seek feedback. A diff of the changes can be
> found at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-alto-protocol-16
>=20
>=20
> Here are major changes:
>=20
> 1. Network Map Version Tags
>    Changed Sec. 6.3 to mention the consistency discussions
>=20
> 2. Mention cross Cost Map
>   Added a short section Sec. 6.4
>=20
> 3. Add a short guideline section Sec. 8.3.6 on Refresh
>=20
> 4. Changed to single media-type
>   Please see Sec. 8.5
>=20
> 5. Other changes suggested per the mailing list.
>=20
> Your feedback is greatly appreciated!
>=20
> Richard

From sebi@gw01.ehlo.wurstkaes.de  Wed Jun 19 07:13:10 2013
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 5C40221F9B8C for <alto@ietfa.amsl.com>; Wed, 19 Jun 2013 07:13:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gzG9FX51Ct36 for <alto@ietfa.amsl.com>; Wed, 19 Jun 2013 07:13:09 -0700 (PDT)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [IPv6:2a02:a00:e000:116::41]) by ietfa.amsl.com (Postfix) with ESMTP id 65E7021F9113 for <alto@ietf.org>; Wed, 19 Jun 2013 07:13:08 -0700 (PDT)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.72) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1UpJ8A-00023X-5Z; Wed, 19 Jun 2013 16:13:02 +0200
Date: Wed, 19 Jun 2013 16:13:02 +0200
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: Jan Seedorf <Jan.Seedorf@neclab.eu>
Message-ID: <20130619141302.GD3489@gw01.ehlo.wurstkaes.de>
References: <2779C9F0771F974CAD742BAE6D9904FE5555A21A@DAPHNIS.office.hd>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2779C9F0771F974CAD742BAE6D9904FE5555A21A@DAPHNIS.office.hd>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: IETF ALTO <alto@ietf.org>
Subject: Re: [alto] Protocol update -16: Security Consideration Section
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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 Jun 2013 14:13:10 -0000

Jan, all,

On Wed, Jun 19, 2013 at 12:48:56PM +0000, Jan Seedorf wrote:
> Dear all,
> 
> I read the latest version of the draft (-16), and I think it really is
> in good shape (apart from the open issues we will discuss in the
> interim meeting later today). I had a closer look at the latest
> security considerations section, and --- thanks to Sebastian and
> Hannes --- it is much better structured than before and reads quite
> well. Below are some minor comments, all of these are small things and
> could probably be addressed by adding a single sentence each to help
> make clearer to the reader what the security considerations are:
> 
> -- 14.1.3. Limitations to Authenticity and Integrity The text only
> talks about the URI of the IRD being compromised, which is (as
> discussed on this list) more a problem of ALTO service discovery. But
> what about cases where the URI domain name is correct, but the ALTO
> server itself has been compromised by malware? In that case, even TLS
> might not help. Is this an obvious threat or should it be explicitly
> mentioned?

I think we should not open that can of worms.

On an architectural level there is no problem.  If you start thinking
what could happen if entities did not behave as specified, there will be
no end of things that could happen.

After short thinking not a single (protocol specification) RFC comes to
my mind that discusses the possibility of compromized implementations.
Do you know any?

> -- 14.3.2. Protection Strategies for Confidentiality The previous
> section "risk scenarios" mentions 3 types of risks, but protection
> strategies are only suggested for type 1 and type 2

I think the first sentence of 14.3.2 should read:

old:

To address risk type (1), the Provider of an ALTO Server must ...

new

To address risk types (1) and (3), the Provider of an ALTO Server must ...


> -- 14.4.2 Protection Strategies for Privacy Apart from using
> obfuscation techniques as suggested in the text, the ALTO client could
> also consider to alternate between several ALTO server when querying
> for ALTO information (in cases where possible, i.e. more than one ALTO
> server has the info and these ALTO servers are not expected to
> collude). This would not help against an intercepting third party, but
> it would help somewhat against tracking at a single ALTO server.
> Additionally, the classic solution of a mix-net-type solution comes to
> mind, where an ALTO privacy service would act on behalf of many
> clients, hiding their identity. Should we add text on these
> considerations (again, if obvious we should probably not mention it)?

That approach is nice, but IMO it makes many assumptions. For example,
there should be many and really non-collaborating operators of ALTO
servers with identical (or equvalent) content, and the client must be
able to discover them.

Adding this as a vague idea to a standards track document is IMO not
adequate (maybe it could go to the deployment considerations document).
And for a full specification it is probably a bit late now, unless many
people say we really need this ...


> -- 14.5.2 Protection Strategies for Availability Against a DDoS attack
> with spoofed source IPs, a simple cookie mechanism (as used in IPSec
> to prevent complex server computations caused by forged requests)
> could help. Of course, this would also need to be specified in an
> extension document.

We already have an example (hashcash) for more advanced protection
schemes that are outside of the scope fo this core document. Adding
a seocnd example does not add anything.

Furthermore I believe that operators of HTTP based services nowadays
have significant experience in protecting them against DoS attacks (not
necessarily by mechanisms from a network security textbook ;-) ), so
I don't think we should go too far.


Just my $0.02

Thanks
Sebastian

From sebi@gw01.ehlo.wurstkaes.de  Wed Jun 19 14:06:14 2013
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 0FAB021F9B12 for <alto@ietfa.amsl.com>; Wed, 19 Jun 2013 14:06:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0yFl295nCoz4 for <alto@ietfa.amsl.com>; Wed, 19 Jun 2013 14:06:13 -0700 (PDT)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [IPv6:2a02:a00:e000:116::41]) by ietfa.amsl.com (Postfix) with ESMTP id B4BA821F9AD3 for <alto@ietf.org>; Wed, 19 Jun 2013 14:06:10 -0700 (PDT)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.72) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1UpPZt-0004JT-Db for alto@ietf.org; Wed, 19 Jun 2013 23:06:05 +0200
Date: Wed, 19 Jun 2013 23:06:05 +0200
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: alto@ietf.org
Message-ID: <20130619210605.GE3489@gw01.ehlo.wurstkaes.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: [alto] draft-ietf-alto-protocol-16: introduction section
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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 Jun 2013 21:06:14 -0000

Dear all,

as discussed in the virtual interim today, I think the introduction
section should give crossrefs to the problem statement and requirements
RFCs at a prominent place.  Whether to repeat the problem statement
in different words or not, is indeed a question of taste. I don't think
it is neccessary but I dpn't object against the current text.
Cross-checking against the other two RFCs I see no contradictions.

So my proposal is to add something between the section titles of 
1. and 1.1., maybe:



1.  Introduction

The protocol specified in this document provides a solution for
the issues identified in the ALTO problem statement [RFC 5693].
It meets the requirements itemized in the ALTO requirements document
[RFC 6708]. A short, non-normative overview on the problem and the
solution approach is given in the following subsections.

1.1.  Background and Problem Statement

...


------------------------------------------------------------

One more comment about section 1.2.2, which says:

    For example, a peer-to-peer overlay application can use information
    provided by an ALTO Service to avoid selecting peers connected with
    low bandwidth links. 


ALTO and link bandwidth is a mine field - not impossible at all, but
difficult, see the long discussions we had, partly summarized in sec.
8.2.3 of draft-ietf-alto-deployments-06.  Therefore I think it would
be wise to use a less controversial example here, say:


    For example, a peer-to-peer overlay application can use information
    provided by an ALTO Service to avoid selecting peers connected via
    intercontinental (i.e., high-delay) links.



Thanks
Sebastian

From yang.r.yang@gmail.com  Wed Jun 19 18:49:49 2013
Return-Path: <yang.r.yang@gmail.com>
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 8EC8421F9F82 for <alto@ietfa.amsl.com>; Wed, 19 Jun 2013 18:49:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OyzxS8imP0IM for <alto@ietfa.amsl.com>; Wed, 19 Jun 2013 18:49:49 -0700 (PDT)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 3B56721F9F95 for <alto@ietf.org>; Wed, 19 Jun 2013 18:49:48 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id um15so5611821pbc.24 for <alto@ietf.org>; Wed, 19 Jun 2013 18:49:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=abupyMGpT5E+JpCIgOn0ygGoGR4Yf20rgRH6U1ep6b0=; b=QVwwDK0RSV5z1kHYHwJ+bhlvVlEupxsKtnEFNAd5afaeEy2pSQo9WSuMNsd6Ag2mwV h5xNCzPNluFAW9MJl2NOQRuup7pso8d6Rmyf348Mvhz0xkKcVGg0I8Zh6+nlb8Eq8ShT ILvNN5wCFIv9hSKQoLoZJbF2uWRANxPvSqZFN3J56s+t12aa+dYXhMS0X/6szPmYNdyB X2x4F0TsJcnwQientciQKvB1MQiaqU1ivSi5vuhVrYdudB/Zx9I0Hx5gG0L9VFUZy3AH te1biOEQ5tC1+eviRKxa93kEy+xyoIxXOVzMxZWi67wh90c0lf4YhkOxuFJyi3Y++jve 6xew==
MIME-Version: 1.0
X-Received: by 10.68.231.37 with SMTP id td5mr5381265pbc.52.1371692987892; Wed, 19 Jun 2013 18:49:47 -0700 (PDT)
Sender: yang.r.yang@gmail.com
Received: by 10.68.43.99 with HTTP; Wed, 19 Jun 2013 18:49:47 -0700 (PDT)
In-Reply-To: <20130619210605.GE3489@gw01.ehlo.wurstkaes.de>
References: <20130619210605.GE3489@gw01.ehlo.wurstkaes.de>
Date: Wed, 19 Jun 2013 21:49:47 -0400
X-Google-Sender-Auth: I_IjV9jrPYqf2NjB6-Y1L3id9RQ
Message-ID: <CANUuoLqQq4EGYCZJ=8mDFW47tW21OBJ_-sxOQ2SgNcYtMy6z9g@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
To: Sebastian Kiesel <ietf-alto@skiesel.de>
Content-Type: multipart/alternative; boundary=047d7b33d91648cceb04df8c299c
Cc: IETF ALTO <alto@ietf.org>
Subject: Re: [alto] draft-ietf-alto-protocol-16: introduction section
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 20 Jun 2013 01:49:49 -0000

--047d7b33d91648cceb04df8c299c
Content-Type: text/plain; charset=ISO-8859-1

Hi Sebastian,

Thank you for your always excellent comments.

On Wed, Jun 19, 2013 at 5:06 PM, Sebastian Kiesel <ietf-alto@skiesel.de>wrote:

> Dear all,
>
> as discussed in the virtual interim today, I think the introduction
> section should give crossrefs to the problem statement and requirements
> RFCs at a prominent place.  Whether to repeat the problem statement
> in different words or not, is indeed a question of taste. I don't think
> it is neccessary but I dpn't object against the current text.
> Cross-checking against the other two RFCs I see no contradictions.
>
> So my proposal is to add something between the section titles of
> 1. and 1.1., maybe:
>
> 1.  Introduction
>
> The protocol specified in this document provides a solution for
> the issues identified in the ALTO problem statement [RFC 5693].
> It meets the requirements itemized in the ALTO requirements document
> [RFC 6708]. A short, non-normative overview on the problem and the
> solution approach is given in the following subsections.
>
>
OK. We will adopt it.


> 1.1.  Background and Problem Statement
>
> ...
>
> ------------------------------------------------------------
>
> One more comment about section 1.2.2, which says:
>
>     For example, a peer-to-peer overlay application can use information
>     provided by an ALTO Service to avoid selecting peers connected with
>     low bandwidth links.
>
>
> ALTO and link bandwidth is a mine field - not impossible at all, but
> difficult, see the long discussions we had, partly summarized in sec.
> 8.2.3 of draft-ietf-alto-deployments-06.  Therefore I think it would
> be wise to use a less controversial example here, say:
>
>
>     For example, a peer-to-peer overlay application can use information
>     provided by an ALTO Service to avoid selecting peers connected via
>     intercontinental (i.e., high-delay) links.
>
>
>
I like the revision. I may suggest some change to the wording, since some
two points in two continents may be closer to some two intra-continent
points:

For example, a peer-to-peer overlay application can use information
provided by an ALTO Service to avoid selecting peers connected via
high-delay links (e.g., some intercontinental links).

What do you think?

Richard


>
> Thanks
> Sebastian
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>

--047d7b33d91648cceb04df8c299c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra">Hi Sebastian,</div><div cla=
ss=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Thank you for your =
always excellent comments.<br><br><div class=3D"gmail_quote">On Wed, Jun 19=
, 2013 at 5:06 PM, Sebastian Kiesel <span dir=3D"ltr">&lt;<a href=3D"mailto=
:ietf-alto@skiesel.de" target=3D"_blank">ietf-alto@skiesel.de</a>&gt;</span=
> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">Dear all,<br>
<br>
as discussed in the virtual interim today, I think the introduction<br>
section should give crossrefs to the problem statement and requirements<br>
RFCs at a prominent place. =A0Whether to repeat the problem statement<br>
in different words or not, is indeed a question of taste. I don&#39;t think=
<br>
it is neccessary but I dpn&#39;t object against the current text.<br>
Cross-checking against the other two RFCs I see no contradictions.<br>
<br>
So my proposal is to add something between the section titles of<br>
1. and 1.1., maybe:<br><br>
1. =A0Introduction<br>
<br>
The protocol specified in this document provides a solution for<br>
the issues identified in the ALTO problem statement [RFC 5693].<br>
It meets the requirements itemized in the ALTO requirements document<br>
[RFC 6708]. A short, non-normative overview on the problem and the<br>
solution approach is given in the following subsections.<br>
<br></blockquote><div><br></div><div style>OK. We will adopt it.</div><div =
style>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex">

1.1. =A0Background and Problem Statement<br>
<br>
...<br><br>
------------------------------------------------------------<br>
<br>
One more comment about section 1.2.2, which says:<br>
<br>
=A0 =A0 For example, a peer-to-peer overlay application can use information=
<br>
=A0 =A0 provided by an ALTO Service to avoid selecting peers connected with=
<br>
=A0 =A0 low bandwidth links.<br>
<br>
<br>
ALTO and link bandwidth is a mine field - not impossible at all, but<br>
difficult, see the long discussions we had, partly summarized in sec.<br>
8.2.3 of draft-ietf-alto-deployments-06. =A0Therefore I think it would<br>
be wise to use a less controversial example here, say:<br>
<br>
<br>
=A0 =A0 For example, a peer-to-peer overlay application can use information=
<br>
=A0 =A0 provided by an ALTO Service to avoid selecting peers connected via<=
br>
=A0 =A0 intercontinental (i.e., high-delay) links.<br>
<br>
<br></blockquote><div style><br>I like the revision. I may suggest some cha=
nge to the wording, since some=A0</div><div style>two points in two contine=
nts=A0may be closer to some two intra-continent points:</div><div style><br=
>
</div><div style>For example, a peer-to-peer overlay application can use in=
formation<br>provided by an ALTO Service to avoid selecting peers connected=
 via<br>high-delay links (e.g., some intercontinental links).<br></div>
<div style><br></div><div style>What do you think?</div><div style><br></di=
v><div style>Richard</div><div style>=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-co=
lor:rgb(204,204,204);border-left-style:solid;padding-left:1ex">

<br>
Thanks<br>
Sebastian<br>
_______________________________________________<br>
alto mailing list<br>
<a href=3D"mailto:alto@ietf.org">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/alto</a><br>
</blockquote></div><br></div></div>

--047d7b33d91648cceb04df8c299c--

From sebi@gw01.ehlo.wurstkaes.de  Wed Jun 19 23:46:18 2013
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 BACC621F99A5 for <alto@ietfa.amsl.com>; Wed, 19 Jun 2013 23:46:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vV7q8Vqnyunm for <alto@ietfa.amsl.com>; Wed, 19 Jun 2013 23:46:18 -0700 (PDT)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [IPv6:2a02:a00:e000:116::41]) by ietfa.amsl.com (Postfix) with ESMTP id 2822121F8E6E for <alto@ietf.org>; Wed, 19 Jun 2013 23:46:17 -0700 (PDT)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.72) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1UpYd2-0007C1-5A; Thu, 20 Jun 2013 08:45:56 +0200
Date: Thu, 20 Jun 2013 08:45:56 +0200
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: "Y. Richard Yang" <yry@cs.yale.edu>
Message-ID: <20130620064556.GG3489@gw01.ehlo.wurstkaes.de>
References: <20130619210605.GE3489@gw01.ehlo.wurstkaes.de> <CANUuoLqQq4EGYCZJ=8mDFW47tW21OBJ_-sxOQ2SgNcYtMy6z9g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CANUuoLqQq4EGYCZJ=8mDFW47tW21OBJ_-sxOQ2SgNcYtMy6z9g@mail.gmail.com>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: IETF ALTO <alto@ietf.org>
Subject: Re: [alto] draft-ietf-alto-protocol-16: introduction section
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 20 Jun 2013 06:46:18 -0000

Hi Richard,

On Wed, Jun 19, 2013 at 09:49:47PM -0400, Y. Richard Yang wrote:
> > One more comment about section 1.2.2, which says:
> >
> >     For example, a peer-to-peer overlay application can use information
> >     provided by an ALTO Service to avoid selecting peers connected with
> >     low bandwidth links.
> >
> >
> > ALTO and link bandwidth is a mine field - not impossible at all, but
> > difficult, see the long discussions we had, partly summarized in sec.
> > 8.2.3 of draft-ietf-alto-deployments-06.  Therefore I think it would
> > be wise to use a less controversial example here, say:
> >
> >
> >     For example, a peer-to-peer overlay application can use information
> >     provided by an ALTO Service to avoid selecting peers connected via
> >     intercontinental (i.e., high-delay) links.
> >
> >
> >
> I like the revision. I may suggest some change to the wording, since some
> two points in two continents may be closer to some two intra-continent
> points:
> 
> For example, a peer-to-peer overlay application can use information
> provided by an ALTO Service to avoid selecting peers connected via
> high-delay links (e.g., some intercontinental links).
> 
> What do you think?

Even better!

Thanks
Sebastian

From richard.alimi@gmail.com  Thu Jun 20 00:45:43 2013
Return-Path: <richard.alimi@gmail.com>
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 F373621E80DE for <alto@ietfa.amsl.com>; Thu, 20 Jun 2013 00:45:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TcQD9+axJJPF for <alto@ietfa.amsl.com>; Thu, 20 Jun 2013 00:45:42 -0700 (PDT)
Received: from mail-vb0-x229.google.com (mail-vb0-x229.google.com [IPv6:2607:f8b0:400c:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 26DC421F9BAE for <alto@ietf.org>; Thu, 20 Jun 2013 00:45:42 -0700 (PDT)
Received: by mail-vb0-f41.google.com with SMTP id p13so4401933vbe.14 for <alto@ietf.org>; Thu, 20 Jun 2013 00:45:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; bh=xl8RG+p+smqSz92tAyjVvPkzb4mKNP46GRNzgQSdLxw=; b=F374qiAGTuDzPYVxuaz6L3d9Mpp1+CQZBIBvzRsYL4jhePi9cfORFGfSCWGPQ4OTc0 yixF/pc/0GEObiAZAVJIekuBCtEUMWZtcwmTjEfIAOhiFJvLP/MaRv3aJjflVdoiVERq Y02nuTsBcQFlpfp54fH3zNs495n1mjkqdKmk+C9f0o/GlTW5NTAz+HWIs8m4bchTwx3n LUSTtSDQtgoRcD+Ro+irOEHgsMgq2g0CEU80ClQTRcuRU97eW34msKsMLUlQZnyuosdt r6rLCec30bCV94vFjbsDM8tqTVY2d6SuyY+VIODQT4TchT50Fpsq4itsWlv1fEcBlusZ PsEA==
X-Received: by 10.58.97.238 with SMTP id ed14mr2388196veb.34.1371714341538; Thu, 20 Jun 2013 00:45:41 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.52.17.193 with HTTP; Thu, 20 Jun 2013 00:45:21 -0700 (PDT)
From: Richard Alimi <rich@velvetsea.net>
Date: Thu, 20 Jun 2013 00:45:21 -0700
X-Google-Sender-Auth: 8Lcq7JBmpRpchw0aH6uTCkJM-HY
Message-ID: <CA+cvDaaHTb0G3x8E3NwSC4fu1AsaW2z9xA=dWUiERM9DXG_o=A@mail.gmail.com>
To: alto@ietf.org
Content-Type: multipart/alternative; boundary=089e013a16660f9cf404df9122aa
Subject: [alto] Clarifying Cost Map Dependencies on a Network Map
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 20 Jun 2013 07:45:43 -0000

--089e013a16660f9cf404df9122aa
Content-Type: text/plain; charset=ISO-8859-1

[ We would like to hear feedback on this.  We are planning to revise and
submit a new version ASAP, so please voice opinions on this within the next
few days, by Monday, June 24th. ]

Background:

Today, the ALTO protocol as a 'version tag' to indicate which version of a
network map is used by a particular cost map.

In a particularly simple case, a single ALTO server is served by a single
hostname (or IP address, whatever), and it exposes a single network map and
one or more cost maps.  There is no ambiguity here - a client automatically
knows that any version tag refers to the single network map that is hosted
by the server.

There are two alternate scenarios where ambiguities arrive:

(Scenario 1) An IRD hosted by alto.isp1.example.com refers cost maps
provided by some third-party, say alto.third-party.example.com.  In this
scenario, do version tags exposed by
alto.third-party.example.comcorrespond to the network map provided by
alto.isp1.example.com?

(Scenario 2) A single ALTO server (single hostname) wishes to provide two
different network maps (say, different levels of aggregation) and wants to
provide cost maps for each of them.  Currently, the version tag
accompanying a cost map is not sufficient for a client to determine which
network map a particular cost map is based on.

Proposal:

To resolve these problems, we'd like to propose a simple change to the
version tag accompanying the cost map - it would now include the URI to the
network map in addition to an opaque ID.

OLD (what we have now):

{
 "meta" : {},
 "data" : {
   "cost-type" : {"cost-mode"  : "numerical",
                  "cost-metric": "routingcost"},
   "map-vtag"  : "1266506139",
   "map" : {
     "PID1": { "PID1": 1,  "PID2": 5,  "PID3": 10 },
     "PID2": { "PID1": 5,  "PID2": 1,  "PID3": 15 },
     "PID3": { "PID1": 20, "PID2": 15  }
   }
 }
}


NEW PROPOSAL:

{
 "meta" : {},
 "data" : {
   "cost-type" : {"cost-mode"  : "numerical",
                  "cost-metric": "routingcost"},
   "network-map" : {

     "uri": "http://alto.example.com/networkmap1"

     "vtag": "1266506139"

     }

   "map" : {
     "PID1": { "PID1": 1,  "PID2": 5,  "PID3": 10 },
     "PID2": { "PID1": 5,  "PID2": 1,  "PID3": 15 },
     "PID3": { "PID1": 20, "PID2": 15  }
   }
 }
}


Compared to the current approach we have in draft -16 (which is for a
version tag to be consistent within resources served by the same hostname),
this has the following advantages:
- It provides a more flexible solution to Scenario 1
- It allows us to handle Scenario 2

An possible addition to this approach would be explicitly declare the
dependency between the cost map and the network map in the IRD.

Feedback would be great.  The editors believe this would be a strong
improvement to the draft.

Thanks,
Rich

--089e013a16660f9cf404df9122aa
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>[ We would like to hear feedback on this. =A0We =
are planning to revise and submit a new version ASAP, so please voice opini=
ons on this within the next few days, by Monday, June 24th. ]</div></div><d=
iv>

<br></div><div style>Background:</div><div><br></div>Today, the ALTO protoc=
ol as a &#39;version tag&#39; to indicate which version of a network map is=
 used by a particular cost map.<div><br></div><div>In a particularly simple=
 case, a single ALTO server is served by a single hostname (or IP address, =
whatever), and it exposes a single network map and one or more cost maps. =
=A0There is no ambiguity here - a client automatically knows that any versi=
on tag refers to the single network map that is hosted by the server.</div>

<div><br></div><div>There are two alternate scenarios where ambiguities arr=
ive:</div><div style><br></div><div style>(Scenario 1) An IRD hosted by <a =
href=3D"http://alto.isp1.example.com">alto.isp1.example.com</a> refers cost=
 maps provided by some third-party, say <a href=3D"http://alto.third-party.=
example.com">alto.third-party.example.com</a>. =A0In this scenario, do vers=
ion tags exposed by <a href=3D"http://alto.third-party.example.com">alto.th=
ird-party.example.com</a> correspond to the network map provided by <a href=
=3D"http://alto.isp1.example.com">alto.isp1.example.com</a>?</div>

<div style><br></div><div style>(Scenario 2) A single ALTO server (single h=
ostname) wishes to provide two different network maps (say, different level=
s of aggregation) and wants to provide cost maps for each of them. =A0Curre=
ntly, the version tag accompanying a cost map is not sufficient for a clien=
t to determine which network map a particular cost map is based on.</div>

<div style><br></div><div style>Proposal:</div><div style><br></div><div st=
yle>To resolve these problems, we&#39;d like to propose a simple change to =
the version tag accompanying the cost map - it would now include the URI to=
 the network map in addition to an opaque ID.</div>

<div style><br></div><div style>OLD (what we have now):</div><div style><br=
></div><div style><pre class=3D"" style=3D"font-size:1em;margin-top:0px;mar=
gin-bottom:0px;color:rgb(0,0,0)">{
 &quot;meta&quot; : {},
 &quot;data&quot; : {
   &quot;cost-type&quot; : {&quot;cost-mode&quot;  : &quot;numerical&quot;,
                  &quot;cost-metric&quot;: &quot;routingcost&quot;},
   &quot;map-vtag&quot;  : &quot;1266506139&quot;,
   &quot;map&quot; : {
     &quot;PID1&quot;: { &quot;PID1&quot;: 1,  &quot;PID2&quot;: 5,  &quot;=
PID3&quot;: 10 },
     &quot;PID2&quot;: { &quot;PID1&quot;: 5,  &quot;PID2&quot;: 1,  &quot;=
PID3&quot;: 15 },
     &quot;PID3&quot;: { &quot;PID1&quot;: 20, &quot;PID2&quot;: 15  }
   }
 }
}</pre></div><div style><br></div><div style>NEW PROPOSAL:</div><div style>=
<br></div><div style><div><pre class=3D"" style=3D"font-size:1em;margin-top=
:0px;margin-bottom:0px;color:rgb(0,0,0)">{
 &quot;meta&quot; : {},
 &quot;data&quot; : {
   &quot;cost-type&quot; : {&quot;cost-mode&quot;  : &quot;numerical&quot;,
                  &quot;cost-metric&quot;: &quot;routingcost&quot;},
   &quot;network-map&quot; : {</pre><pre class=3D"" style=3D"font-size:1em;=
margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">     &quot;uri&quot;: &q=
uot;<a href=3D"http://alto.example.com/networkmap1">http://alto.example.com=
/networkmap1</a>&quot;</pre>

<pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"=
><span style=3D"font-size:11px">     &quot;vtag&quot;:</span><span style=3D=
"font-size:1em;font-family:arial"> &quot;1266506139&quot;</span></pre><pre =
class=3D"" style=3D"margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">

<span style=3D"font-size:1em;font-family:arial">     }</span></pre><pre cla=
ss=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0=
,0,0)">   &quot;map&quot; : {
     &quot;PID1&quot;: { &quot;PID1&quot;: 1,  &quot;PID2&quot;: 5,  &quot;=
PID3&quot;: 10 },
     &quot;PID2&quot;: { &quot;PID1&quot;: 5,  &quot;PID2&quot;: 1,  &quot;=
PID3&quot;: 15 },
     &quot;PID3&quot;: { &quot;PID1&quot;: 20, &quot;PID2&quot;: 15  }
   }
 }
}</pre></div><div><br></div><div style>Compared to the current approach we =
have in draft -16 (which is for a version tag to be consistent within resou=
rces served by the same hostname), this has the following advantages:<br>

- It provides a more flexible solution to Scenario 1</div><div style>- It a=
llows us to handle Scenario 2</div><div style><br></div><div style>An possi=
ble addition to this approach would be explicitly declare the dependency be=
tween the cost map and the network map in the IRD.</div>

<div style><br></div><div style>Feedback would be great. =A0The editors bel=
ieve this would be a strong improvement to the draft.</div><div style><br><=
/div><div style>Thanks,</div><div style>Rich</div></div></div>

--089e013a16660f9cf404df9122aa--

From enrico.marocco@telecomitalia.it  Thu Jun 20 03:02:50 2013
Return-Path: <enrico.marocco@telecomitalia.it>
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 28A9221F9FCB for <alto@ietfa.amsl.com>; Thu, 20 Jun 2013 03:02:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.669
X-Spam-Level: 
X-Spam-Status: No, score=-101.669 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245,  RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jdK8VwuXqaTC for <alto@ietfa.amsl.com>; Thu, 20 Jun 2013 03:02:42 -0700 (PDT)
Received: from GRFEDG701RM001.telecomitalia.it (grfedg701rm001.telecomitalia.it [217.169.121.20]) by ietfa.amsl.com (Postfix) with ESMTP id 6701E21F9EBD for <alto@ietf.org>; Thu, 20 Jun 2013 03:02:41 -0700 (PDT)
Received: from grfhub703rm001.griffon.local (10.19.3.10) by GRFEDG701RM001.telecomitalia.it (10.173.88.20) with Microsoft SMTP Server (TLS) id 8.3.297.1; Thu, 20 Jun 2013 12:02:37 +0200
Received: from MacLab.local (10.229.8.22) by smtp.telecomitalia.it (10.19.9.236) with Microsoft SMTP Server (TLS) id 8.3.297.1; Thu, 20 Jun 2013 12:02:37 +0200
Message-ID: <51C2D33C.6010500@telecomitalia.it>
Date: Thu, 20 Jun 2013 12:02:36 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "alto@ietf.org" <alto@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms080904040708080501070301"
X-TI-Disclaimer: Disclaimer1
Subject: [alto] Raw interim minutes
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 20 Jun 2013 10:02:50 -0000

--------------ms080904040708080501070301
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,

here are the raw notes taken by Micheal (very detailed, thanks again
Micheal!). Please take a look and point out any inaccuracies.

Rich has already started a separate thread to address the only remaining
open point. Please comment on that as well, so that authors can produce
a final WG version of the document soon.

Enrico

********************************

ALTO interim meeting
June 19, 2013, 17:00-18:00 CET
Notetaker: Michael Scharf


Agenda (Enrico Marocco)
------


draft-ietf-alto-protococol (Richard Alimi)
--------------------------

* Changes in -16

* Slide 4: Item 1: IRD declaration

* Slide 5: Item 2: Update frequency

Enrico: Discuss this now or at the end of the presentation?
Richard Yang: Recommend one method or leave it open?
Richard A.: Leave it on HTTP. Benefits is that we don't have to track HTT=
P.
Enrico: I tend to agree with Richard A., going with HTTP is generally
recommended.
Richard Y.: We should recommend that ALTO server should have cache
control. HTTP doesn't mandate this.
Enrico: Any objection to using HTTP?
<NONE>

* Slide 6: Item 2: Update frequency

Sebastian Kiesel: What is the meaning of the first sentence? It has no
normative language. Do we need it?
Richard A.: We can just drop the first part of the sentence.
Enrico: Any objections?
<NONE>

* Slide 7: Item 3: Equivalence of Server Data

Richard Y.: I want to back what Richard A said.
Richard A.: Redirection from custom.alto.example.com to alto.example.com
not possible.
Richard Y.: Let's go to the next slide before discussing solutions.

* Slide 8: Solution to item 3

Richard Y.: Seems to be more flexible solution.

*** NOTE: audio outage of several seconds for the note-taker ***

Richard A.: Can we simplify this to not affect the IRD? For instance,
only use the second proposal on slide 8?
Richard Y.: This would work, too.
Richard A.: What is the benefit of adding it to IRD?
Richard Y.: Metadata is only in one place.
Enrico: Does everybody understand the problem and the two solutions?
Michael: I don't understand the options. I haven't followed this issue
before, but if you want to hear opinions, I can't really comment based
on what was presented here.
Richard Y.: Idea 1 is to use the URI? Idea 2 is to encode URI in cost
map metadata.
Michael: I understand the problem, and it seems to be an important
problem, but I don't fully get the tradeoff between the solutions.
Richard A.: Explanation of slide 8 and 9
Enrico: I suggest that the authors agree on a solution and post it on
the mailing list.
Michael: Yes, the solution 2 seems OK, but some written explanation of
the rationale would help.
Richard A.: I then suggest to use the second solution without IRD entry.

* Slide 9: Proposed Tentative Timeline

Richard A.: When to schedule the WGLC?
Enrico: Best practice is not to span the IETF week. Recall that this
blocks all other drafts, including adoption of the discovery drafts,
extensions, etc.

Enrico: I suggest that the authors send a note to the list with the
(only) remaining entry.
Spencer Dawkins: I agree on your statement of avoiding a WGLC during the
IETF week.

* Security discussion

Richard Y.: Security issues. Do we want to spend some minutes on the
discussion between Jan and Sebastian?
Sebastian: I don't have much to add to what we discussed on the list. We
have given the security section a new layout and I am happy with it. Jan
found some minor issues, some bugs and some are probably beyond a
standards track document. We should probably await the SECDIR review.
Jan: I agree with Sebastian. I read it and the section is very good. I
just posted some thoughts, which are minor issues.
Sebastian: The issue is that there are three kinds of risks and only two
counter-measures.
Jan: I agree with Sebastian. The purpose of the section is to give
implementors an understanding of the security issues. But, again, the
text is actually fine.
Enrico: Thanks to Sebastian and Jan, this is very useful. The whole
document improved a lot since Orlando.

Enrico: Further comments?
Sebastian: Beginning of the document - "solution benefits" is uncommon.
Do we want to have this? This is a small question I still have in mind.
Richard Y.: You want to remove Section 1.2?
Sebastian: Maybe the whole introduction could be reworked, to shorten
it? Something like "This is the protocol that solves the problem
explained in ...". But it is just a  comment, I don't have a strong feeli=
ng.
Richard A.: I prefer documents that are somewhat self-contained.
Sebastian: I will go through the introduction and check if there are
contradictions.
Jan: I just realized that the document refers to the problem statement
RFC only in the terminology section. It should probably be mentioned in
the introduction, too.
Sebastian: Reading this document, it is not clear to me that this is the
outcome of the ALTO WG and result of a problem analysis etc.
Jan: This is somehow a matter of taste. A short re-cap may be fine. What
it definitively missing is a better reference to the problem statement
draft.
Sebastian: I back that. The problem statement and requirement documents
should be refered. I will check the text for consistency with them.
Enrico: I agree. Checking for consistency is good to do now. There is a
chance that there will be further comments on the introduction during
the publishing process. We must be prepared to react to IESG reviews on
that in any case.
Sebastian: Actually, my proposal could help here.
Enrico: It is a matter of taste, but there may be strong opinions in the
IESG.

Richard Y.: Clarification questions: Are we allowed to submit drafts on
extensions for the upcoming IETF?
Enrico: I will check with my co-chair and the ADs. My thinking is that
the milestone is completing the WGLC of the protocol document.
Richard Y.: People want to talk about ALTO extensions.
Enrico: Understood, but the document was due 2 years ago. But we see
light at the end of the tunnel.

End of meeting


--------------ms080904040708080501070301
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINdzCC
BjQwggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOr
lr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSM
zR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6
qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSD
kOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQOJebr/f/h5t95
m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqD
CH14qywGXLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy
6QMVQjbbMXltUfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPI
zKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKf
KSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HOR
z9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9
sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCie
uoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7t
w1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQ
G2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t
5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIHOzCCBiOgAwIBAgIDBKfoMA0GCSqGSIb3DQEB
BQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTIwODA3MDkxNTQz
WhcNMTMwODA4MDczMzM3WjB1MRkwFwYDVQQNExBvWkNPVnNYc09NME9mcExwMSgwJgYDVQQD
DB9lbnJpY28ubWFyb2Njb0B0ZWxlY29taXRhbGlhLml0MS4wLAYJKoZIhvcNAQkBFh9lbnJp
Y28ubWFyb2Njb0B0ZWxlY29taXRhbGlhLml0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB
CgKCAQEAshI2shfUZ7P5RVcP04fJ4OfYmK/RUyokJpuJE4KaSOLArtpNtlYo6MtXfmZzA8y/
5HChSAmPvqUwhMMYh1LurWbOdX4uKXO1gsFrPOtxTa6qin6lXaJ3bo2pKnkN9mQkjvm0E23r
rrT3MC6h6UfyFAcvs01+yq9wVuxxRdC4LZTGAbXGkE34GQAnBy9eqvJ+m351hPaaVw9u8CWN
uyv9YKLXpicS/q8j2EOpFBCkZVp0E8fViSXViGtuhfbW6R+TjTXJZN06DEqb/vpRSWkvBDf0
UqDFrgmlmSnXJ/xpaygAJcHyE5qjRXkIV7adTkg9Z/Z2lJXvtDUdHbNBiYcVOwIDAQABo4ID
ujCCA7YwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsG
AQUFBwMEMB0GA1UdDgQWBBT1YgWCbkVCN8iNgS49Fh9R2ZC8wTAfBgNVHSMEGDAWgBRTcu2S
nODaywFcfH6WNU7y1LhRgjAqBgNVHREEIzAhgR9lbnJpY28ubWFyb2Njb0B0ZWxlY29taXRh
bGlhLml0MIICIQYDVR0gBIICGDCCAhQwggIQBgsrBgEEAYG1NwECAjCCAf8wLgYIKwYBBQUH
AgEWImh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwgfcGCCsGAQUFBwICMIHq
MCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRp
ZmljYXRlIHdhcyBpc3N1ZWQgYWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24g
cmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkg
Zm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGluIGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcg
cGFydHkgb2JsaWdhdGlvbnMuMIGcBggrBgEFBQcCAjCBjzAnFiBTdGFydENvbSBDZXJ0aWZp
Y2F0aW9uIEF1dGhvcml0eTADAgECGmRMaWFiaWxpdHkgYW5kIHdhcnJhbnRpZXMgYXJlIGxp
bWl0ZWQhIFNlZSBzZWN0aW9uICJMZWdhbCBhbmQgTGltaXRhdGlvbnMiIG9mIHRoZSBTdGFy
dENvbSBDQSBwb2xpY3kuMDYGA1UdHwQvMC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wu
Y29tL2NydHUxLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6
Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MxL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2
aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMS5jbGllbnQuY2EuY3J0
MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUFAAOC
AQEAIn8FoRaqvQzo8aGNi4EbPhIMX8aPIMhX3L/N+8sMyFe3cpSyjij47DW1K330zDJnoyZs
kuI10EzfK0wwY+D2qMQPGAmPDkix5t2dYQj6DKh1yBlBwAf7c65Ty1kpgtdymSptDJKVZcK6
R2CJ91oRBCZIObcWrG/0FZIr55+InAYyLDrlk34MwBmINhBZ4oRJdrzG6OC7cK4vG1ZWrAFE
GHVwx1uG2NXRUXQTH9DGYcwwfPo4uinFCwHZAJ2Il/J0Mqui5x+N/7p+WUlGRyb67qxg7ect
f2095+YDnbqIKIz7fGzw8XTwpjYbvWZplkG93qRXr8MRD9ukgxpxpHG2dTGCA90wggPZAgEB
MIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwSn6DAJBgUrDgMCGgUA
oIICHTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzA2MjAx
MDAyMzZaMCMGCSqGSIb3DQEJBDEWBBS3FbJhAIX8c6Fz7s9tUnb9HkRszjBsBgkqhkiG9w0B
CQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcN
AwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGlBgkrBgEE
AYI3EAQxgZcwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9T
dGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDBKfoMIGn
BgsqhkiG9w0BCRACCzGBl6CBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2
BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENB
AgMEp+gwDQYJKoZIhvcNAQEBBQAEggEAiHNY46u7dSKoA2hAtQD69whKvW7CBGJutZXidRij
ow3S2ROSKaCcjbPZpM0IKfMTJhji56tPd3Js/tFl7b3LwLcCGmZngVaFPDfJKn/uCfalCo9O
6O8vWOmx98+Cpyt2OG9ETKUD2zpgnHz6y+0wrN4kA3QXV5lh75rD5RzgDCfru2WeFkmth/cw
UAvpQV9eQGta3SHRcriRbOWo0HicIOsJsh/GW57mK7pTx9uJd9uOSWXy8qDd6NiOAwE5D1wj
mYxQu1XdWWI0l5XxNnp0+wrJ7IAamce3ktxT4lSWJut3m21c0Z78UEZDbLbopAysTJKqi1gg
kg/wNFpA7PnQIAAAAAAAAA==
--------------ms080904040708080501070301--

From sabine.randriamasy@alcatel-lucent.com  Fri Jun 21 07:34:34 2013
Return-Path: <sabine.randriamasy@alcatel-lucent.com>
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 0C1CB21E811B for <alto@ietfa.amsl.com>; Fri, 21 Jun 2013 07:34:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BA5U3qosY-Mk for <alto@ietfa.amsl.com>; Fri, 21 Jun 2013 07:34:27 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id D156B11E8197 for <alto@ietf.org>; Fri, 21 Jun 2013 07:34:21 -0700 (PDT)
Received: from us70uusmtp4.zam.alcatel-lucent.com (h135-5-2-66.lucent.com [135.5.2.66]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r5LEYHKG009365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 21 Jun 2013 09:34:18 -0500 (CDT)
Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (us70uwxchhub02.zam.alcatel-lucent.com [135.5.2.49]) by us70uusmtp4.zam.alcatel-lucent.com (GMO) with ESMTP id r5LEYDna027985 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 21 Jun 2013 10:34:17 -0400
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (135.239.2.112) by US70UWXCHHUB02.zam.alcatel-lucent.com (135.5.2.49) with Microsoft SMTP Server (TLS) id 14.2.247.3; Fri, 21 Jun 2013 10:34:06 -0400
Received: from FR711WXCHMBA03.zeu.alcatel-lucent.com ([169.254.3.135]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Fri, 21 Jun 2013 16:33:54 +0200
From: "RANDRIAMASY, SABINE (SABINE)" <sabine.randriamasy@alcatel-lucent.com>
To: Richard Alimi <rich@velvetsea.net>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: [alto] Clarifying Cost Map Dependencies on a Network Map
Thread-Index: AQHObYo0BXlN9V1qwECMOBbRVGR/0plAO/uQ
Date: Fri, 21 Jun 2013 14:33:53 +0000
Message-ID: <A7A5844EB93EB94AB22C2068B10AD65A6907B6@FR711WXCHMBA03.zeu.alcatel-lucent.com>
References: <CA+cvDaaHTb0G3x8E3NwSC4fu1AsaW2z9xA=dWUiERM9DXG_o=A@mail.gmail.com>
In-Reply-To: <CA+cvDaaHTb0G3x8E3NwSC4fu1AsaW2z9xA=dWUiERM9DXG_o=A@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.41]
Content-Type: multipart/alternative; boundary="_000_A7A5844EB93EB94AB22C2068B10AD65A6907B6FR711WXCHMBA03zeu_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Subject: Re: [alto] Clarifying Cost Map Dependencies on a Network Map
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 21 Jun 2013 14:34:34 -0000

--_000_A7A5844EB93EB94AB22C2068B10AD65A6907B6FR711WXCHMBA03zeu_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Rich,

Definitely, scenario2 and 1 are convincing motivations and I support your p=
roposal. I also approve specifying the dependency in the IRD to avoid reque=
sting an irrelevant Cost Map in such scenarios.
Best regards
Sabine


De : alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] De la part de Ric=
hard Alimi
Envoy=E9 : jeudi 20 juin 2013 09:45
=C0 : alto@ietf.org
Objet : [alto] Clarifying Cost Map Dependencies on a Network Map

[ We would like to hear feedback on this.  We are planning to revise and su=
bmit a new version ASAP, so please voice opinions on this within the next f=
ew days, by Monday, June 24th. ]

Background:

Today, the ALTO protocol as a 'version tag' to indicate which version of a =
network map is used by a particular cost map.

In a particularly simple case, a single ALTO server is served by a single h=
ostname (or IP address, whatever), and it exposes a single network map and =
one or more cost maps.  There is no ambiguity here - a client automatically=
 knows that any version tag refers to the single network map that is hosted=
 by the server.

There are two alternate scenarios where ambiguities arrive:

(Scenario 1) An IRD hosted by alto.isp1.example.com<http://alto.isp1.exampl=
e.com> refers cost maps provided by some third-party, say alto.third-party.=
example.com<http://alto.third-party.example.com>.  In this scenario, do ver=
sion tags exposed by alto.third-party.example.com<http://alto.third-party.e=
xample.com> correspond to the network map provided by alto.isp1.example.com=
<http://alto.isp1.example.com>?

(Scenario 2) A single ALTO server (single hostname) wishes to provide two d=
ifferent network maps (say, different levels of aggregation) and wants to p=
rovide cost maps for each of them.  Currently, the version tag accompanying=
 a cost map is not sufficient for a client to determine which network map a=
 particular cost map is based on.

Proposal:

To resolve these problems, we'd like to propose a simple change to the vers=
ion tag accompanying the cost map - it would now include the URI to the net=
work map in addition to an opaque ID.

OLD (what we have now):


{

 "meta" : {},

 "data" : {

   "cost-type" : {"cost-mode"  : "numerical",

                  "cost-metric": "routingcost"},

   "map-vtag"  : "1266506139",

   "map" : {

     "PID1": { "PID1": 1,  "PID2": 5,  "PID3": 10 },

     "PID2": { "PID1": 5,  "PID2": 1,  "PID3": 15 },

     "PID3": { "PID1": 20, "PID2": 15  }

   }

 }

}

NEW PROPOSAL:


{

 "meta" : {},

 "data" : {

   "cost-type" : {"cost-mode"  : "numerical",

                  "cost-metric": "routingcost"},

   "network-map" : {

     "uri": "http://alto.example.com/networkmap1"

     "vtag": "1266506139"





     }

   "map" : {

     "PID1": { "PID1": 1,  "PID2": 5,  "PID3": 10 },

     "PID2": { "PID1": 5,  "PID2": 1,  "PID3": 15 },

     "PID3": { "PID1": 20, "PID2": 15  }

   }

 }

}

Compared to the current approach we have in draft -16 (which is for a versi=
on tag to be consistent within resources served by the same hostname), this=
 has the following advantages:
- It provides a more flexible solution to Scenario 1
- It allows us to handle Scenario 2

An possible addition to this approach would be explicitly declare the depen=
dency between the cost map and the network map in the IRD.

Feedback would be great.  The editors believe this would be a strong improv=
ement to the draft.

Thanks,
Rich

--_000_A7A5844EB93EB94AB22C2068B10AD65A6907B6FR711WXCHMBA03zeu_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.PrformatHTMLCar
	{mso-style-name:"Pr=E9format=E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Rich,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Definitely, scenario2 and=
 1 are convincing motivations and I support your proposal. I also approve s=
pecifying the dependency in the IRD to avoid requesting
 an irrelevant Cost Map in such scenarios. &nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Best regards<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Sabine<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><b><span lang=3D"FR" st=
yle=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quo=
t;">De&nbsp;:</span></b><span lang=3D"FR" style=3D"font-size:10.0pt;font-fa=
mily:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> alto-bounces@ietf.org [mai=
lto:alto-bounces@ietf.org]
<b>De la part de</b> Richard Alimi<br>
<b>Envoy=E9&nbsp;:</b> jeudi 20 juin 2013 09:45<br>
<b>=C0&nbsp;:</b> alto@ietf.org<br>
<b>Objet&nbsp;:</b> [alto] Clarifying Cost Map Dependencies on a Network Ma=
p<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">[ We would like to hear=
 feedback on this. &nbsp;We are planning to revise and submit a new version=
 ASAP, so please voice opinions on this within the next few days, by Monday=
, June 24th. ]<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">Background:<o:p></o:p><=
/p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">Today, the ALTO protoco=
l as a 'version tag' to indicate which version of a network map is used by =
a particular cost map.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">In a particularly simpl=
e case, a single ALTO server is served by a single hostname (or IP address,=
 whatever), and it exposes a single network map and one or more cost maps. =
&nbsp;There is no ambiguity here - a client
 automatically knows that any version tag refers to the single network map =
that is hosted by the server.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">There are two alternate=
 scenarios where ambiguities arrive:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">(Scenario 1) An IRD hos=
ted by <a href=3D"http://alto.isp1.example.com">
alto.isp1.example.com</a> refers cost maps provided by some third-party, sa=
y <a href=3D"http://alto.third-party.example.com">
alto.third-party.example.com</a>. &nbsp;In this scenario, do version tags e=
xposed by <a href=3D"http://alto.third-party.example.com">
alto.third-party.example.com</a> correspond to the network map provided by =
<a href=3D"http://alto.isp1.example.com">
alto.isp1.example.com</a>?<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">(Scenario 2) A single A=
LTO server (single hostname) wishes to provide two different network maps (=
say, different levels of aggregation) and wants to provide cost maps for ea=
ch of them. &nbsp;Currently, the version
 tag accompanying a cost map is not sufficient for a client to determine wh=
ich network map a particular cost map is based on.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">Proposal:<o:p></o:p></p=
>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">To resolve these proble=
ms, we'd like to propose a simple change to the version tag accompanying th=
e cost map - it would now include the URI to the network map in addition to=
 an opaque ID.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">OLD (what we have now):=
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
</div>
<div>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">{<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck"> &quot;meta&quot; : {},<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck"> &quot;data&quot; : {<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">&nbsp;&nbsp; &quot;cost-type&quot; : {&quot;cost-mode&quot;&nbsp; : &qu=
ot;numerical&quot;,<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;cost-metric&quot;: &quot;routingcost&=
quot;},<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">&nbsp;&nbsp; &quot;map-vtag&quot;&nbsp; : &quot;1266506139&quot;,<o:p><=
/o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">&nbsp;&nbsp; &quot;map&quot; : {<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">&nbsp;&nbsp;&nbsp;&nbsp; &quot;PID1&quot;: { &quot;PID1&quot;: 1,&nbsp;=
 &quot;PID2&quot;: 5,&nbsp; &quot;PID3&quot;: 10 },<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">&nbsp;&nbsp;&nbsp;&nbsp; &quot;PID2&quot;: { &quot;PID1&quot;: 5,&nbsp;=
 &quot;PID2&quot;: 1,&nbsp; &quot;PID3&quot;: 15 },<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">&nbsp;&nbsp;&nbsp;&nbsp; &quot;PID3&quot;: { &quot;PID1&quot;: 20, &quo=
t;PID2&quot;: 15&nbsp; }<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">&nbsp;&nbsp; }<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck"> }<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">}<o:p></o:p></span></pre>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">NEW PROPOSAL:<o:p></o:p=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
</div>
<div>
<div>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">{<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck"> &quot;meta&quot; : {},<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck"> &quot;data&quot; : {<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">&nbsp;&nbsp; &quot;cost-type&quot; : {&quot;cost-mode&quot;&nbsp; : &qu=
ot;numerical&quot;,<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;cost-metric&quot;: &quot;routingcost&=
quot;},<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">&nbsp;&nbsp; &quot;network-map&quot; : {<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">&nbsp;&nbsp;&nbsp;&nbsp; &quot;uri&quot;: &quot;<a href=3D"http://alto.=
example.com/networkmap1">http://alto.example.com/networkmap1</a>&quot;<o:p>=
</o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:8.5pt;color:blac=
k">&nbsp;&nbsp;&nbsp;&nbsp; &quot;vtag&quot;:</span><span style=3D"font-fam=
ily:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black"> &quot;1266506139=
&quot;</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"color:black"><o:p>&nbsp;</=
o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"color:black"><o:p>&nbsp;</=
o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-family:&quot;Arial&qu=
ot;,&quot;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp; }</span><s=
pan style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">&nbsp;&nbsp; &quot;map&quot; : {<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">&nbsp;&nbsp;&nbsp;&nbsp; &quot;PID1&quot;: { &quot;PID1&quot;: 1,&nbsp;=
 &quot;PID2&quot;: 5,&nbsp; &quot;PID3&quot;: 10 },<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">&nbsp;&nbsp;&nbsp;&nbsp; &quot;PID2&quot;: { &quot;PID1&quot;: 5,&nbsp;=
 &quot;PID2&quot;: 1,&nbsp; &quot;PID3&quot;: 15 },<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">&nbsp;&nbsp;&nbsp;&nbsp; &quot;PID3&quot;: { &quot;PID1&quot;: 20, &quo=
t;PID2&quot;: 15&nbsp; }<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">&nbsp;&nbsp; }<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck"> }<o:p></o:p></span></pre>
<pre style=3D"margin-left:36.0pt"><span style=3D"font-size:12.0pt;color:bla=
ck">}<o:p></o:p></span></pre>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">Compared to the current=
 approach we have in draft -16 (which is for a version tag to be consistent=
 within resources served by the same hostname), this has the following adva=
ntages:<br>
- It provides a more flexible solution to Scenario 1<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">- It allows us to handl=
e Scenario 2<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">An possible addition to=
 this approach would be explicitly declare the dependency between the cost =
map and the network map in the IRD.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">Feedback would be great=
. &nbsp;The editors believe this would be a strong improvement to the draft=
.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">Thanks,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">Rich<o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_A7A5844EB93EB94AB22C2068B10AD65A6907B6FR711WXCHMBA03zeu_--

From sabine.randriamasy@alcatel-lucent.com  Mon Jun 24 10:02:52 2013
Return-Path: <sabine.randriamasy@alcatel-lucent.com>
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 E14C711E8161 for <alto@ietfa.amsl.com>; Mon, 24 Jun 2013 10:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PKUEQqSQqlzl for <alto@ietfa.amsl.com>; Mon, 24 Jun 2013 10:02:46 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id D561511E816B for <alto@ietf.org>; Mon, 24 Jun 2013 10:02:45 -0700 (PDT)
Received: from us70tusmtp1.zam.alcatel-lucent.com (h135-5-2-63.lucent.com [135.5.2.63]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id r5OH2amL007291 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Mon, 24 Jun 2013 12:02:37 -0500 (CDT)
Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (us70uwxchhub02.zam.alcatel-lucent.com [135.5.2.49]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id r5OH2aWl031755 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <alto@ietf.org>; Mon, 24 Jun 2013 13:02:36 -0400
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (135.239.2.112) by US70UWXCHHUB02.zam.alcatel-lucent.com (135.5.2.49) with Microsoft SMTP Server (TLS) id 14.2.247.3; Mon, 24 Jun 2013 13:02:36 -0400
Received: from FR711WXCHMBA01.zeu.alcatel-lucent.com ([169.254.1.6]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Mon, 24 Jun 2013 19:02:32 +0200
From: "RANDRIAMASY, SABINE (SABINE)" <sabine.randriamasy@alcatel-lucent.com>
To: "alto@ietf.org" <alto@ietf.org>
Thread-Topic: draft-ietf-alto-protocol-16 - minor comments
Thread-Index: Ac5w/J0HqmODOryMRwyyiUyu9W72tA==
Date: Mon, 24 Jun 2013 17:02:31 +0000
Message-ID: <A7A5844EB93EB94AB22C2068B10AD65A699E17@FR711WXCHMBA01.zeu.alcatel-lucent.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.38]
Content-Type: multipart/mixed; boundary="_004_A7A5844EB93EB94AB22C2068B10AD65A699E17FR711WXCHMBA01zeu_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Subject: [alto] draft-ietf-alto-protocol-16 - minor comments
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 24 Jun 2013 17:02:53 -0000

--_004_A7A5844EB93EB94AB22C2068B10AD65A699E17FR711WXCHMBA01zeu_
Content-Type: multipart/alternative;
	boundary="_000_A7A5844EB93EB94AB22C2068B10AD65A699E17FR711WXCHMBA01zeu_"

--_000_A7A5844EB93EB94AB22C2068B10AD65A699E17FR711WXCHMBA01zeu_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear all,

While going through the latest update, I have listed some minor comments an=
d typos and  suggest some re-phrasings below, in particular in paragraphs o=
n new features such as the new cost type and the in/re-direction to other I=
RDs. I also attached a text file with the comments.
Hoping it helps.
Sabine


---------------------------------------
COMMENTS ON draft-ietf-alto-protocol-16
---------------------------------------


- everything in ++ indicates ADDED text, including white space
- everything in -- indicated REMOVED text


[Page 27] =A78.5.3 Example
The example IRD exposes a capability called "cost-type-name" that is not in=
troduced before and it would help to add some sentences to better distingui=
sh the roles of "cost-type-name" and "cost-type". Especially as the combina=
tion of cost metric and cost mode into cost type is new to people who alrea=
dy coded an ALTO Client. Besides, the field "cost-type" of the meta member =
defines the cost type names but also specifies their members. So I propose =
to add some text after the example IRD and before sentence "Specifically, t=
he "meta" member of the example IRD defines....", that would look like:

"When an ALTO Client wants to fetch the Cost Types supported at the uris li=
sted in the ALTO Server, it should look after string "cost-type-names". The=
 values of "cost-type-names" indicate Cost Types whose Cost Metric and Cost=
 Mode are specified in the field "cost-type" of member "meta" of the IRD. S=
pecifically etc. ...".


[Page 28] =A7 8.5.4 Delegation and Multiple Choices
Redirection to another IRD is another new feature so like in the previous s=
ection, I suggest to add text on the media-type. A proposal for the first p=
aragraph:

"... In the example above, the -- +fourth uri/entry+ provides additional Ne=
twork and Cost Maps via a separate subdomain, "custom.alto.example.com". +T=
his re/indirection is indicated by the media-type "application/alto-directo=
ry+json"+. In particular etc. ...".



[Page 30] =A7 8.5.5.1 ALTO Client
text says: "In general, it is preferred for ALTO Clients to use GET request=
s where appropriate, since it is more likely for responses to be cachable."

As the ECS seems as attractive as the Cost Map Service in many use cases, I=
'd prefer to mention preferences for both CostMap and ECS with a text like:

"An ALTO Client may prefer to use GET requests for cacheable information. I=
t may on the other hand prefer POST requests for example to get ALTO costs =
or properties on a restricted set of PIDs or Endpoints or to update cached =
information previously acquired via GET requests."



[Page 37] =A7 9.6. Cost Type
text says: "The combinaton of CostType and a CostMode defines a CostType"
Given the latest specs in =A76.1 and the IRD examples, the sentence should =
be "The combinaton of +a+ Cost++Type and a Cost++Mode defines a Cost++Type"

The object CostType specified in this section contains a field called "Cost=
Model" where I believe the "l" should be removed to give "CostMode-l-".



[Page 38] =A7 10 Protocol Specification: Service Information Resources
A "d" should be added in sentence, to have: "This section documents.... def=
ine+d+ ... document".



[Page 40] Section 10.1.1.6 Example
In paragraph after the example, in following part of 2nd sentence: "such as=
 transforming the Network Map into a IP trie": should it be "tree"?





--_000_A7A5844EB93EB94AB22C2068B10AD65A699E17FR711WXCHMBA01zeu_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"FR">Dear all,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FR"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">While going through the latest update, I have listed=
 some minor comments and typos and &nbsp;suggest some re-phrasings below, i=
n particular in paragraphs on new features such as the new cost type and th=
e in/re-direction to other IRDs. I also
 attached a text file with the comments. <o:p></o:p></p>
<p class=3D"MsoNormal">Hoping it helps. <o:p></o:p></p>
<p class=3D"MsoNormal">Sabine<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">---------------------------------------<o:p></o:p></=
p>
<p class=3D"MsoNormal">COMMENTS ON draft-ietf-alto-protocol-16<o:p></o:p></=
p>
<p class=3D"MsoNormal">---------------------------------------<o:p></o:p></=
p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">- everything in &#43;&#43; indicates ADDED text, inc=
luding white space<o:p></o:p></p>
<p class=3D"MsoNormal">- everything in -- indicated REMOVED text<o:p></o:p>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">[Page 27] =A78.5.3 Example<o:p></o:p></p>
<p class=3D"MsoNormal">The example IRD exposes a capability called &quot;co=
st-type-name&quot; that is not introduced before and it would help to add s=
ome sentences to better distinguish the roles of &quot;cost-type-name&quot;=
 and &quot;cost-type&quot;. Especially as the combination of cost
 metric and cost mode into cost type is new to people who already coded an =
ALTO Client. Besides, the field &quot;cost-type&quot; of the meta member de=
fines the cost type names but also specifies their members. So I propose to=
 add some text after the example IRD and before
 sentence &quot;Specifically, the &quot;meta&quot; member of the example IR=
D defines....&quot;, that would look like:
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;When an ALTO Client wants to fetch the Cost Ty=
pes supported at the uris listed in the ALTO Server, it should look after s=
tring &quot;cost-type-names&quot;. The values of &quot;cost-type-names&quot=
; indicate Cost Types whose Cost Metric and Cost Mode are specified
 in the field &quot;cost-type&quot; of member &quot;meta&quot; of the IRD. =
Specifically etc. ...&quot;. <o:p>
</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">[Page 28] =A7 8.5.4 Delegation and Multiple Choices<=
o:p></o:p></p>
<p class=3D"MsoNormal">Redirection to another IRD is another new feature so=
 like in the previous section, I suggest to add text on the media-type. A p=
roposal for the first paragraph:
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;... In the example above, the -- &#43;fourth u=
ri/entry&#43; provides additional Network and Cost Maps via a separate subd=
omain, &quot;custom.alto.example.com&quot;. &#43;This re/indirection is ind=
icated by the media-type &quot;application/alto-directory&#43;json&quot;&#4=
3;.
 In particular etc. ...&quot;. <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">[Page 30] =A7 8.5.5.1 ALTO Client<o:p></o:p></p>
<p class=3D"MsoNormal">text says: &quot;In general, it is preferred for ALT=
O Clients to use GET requests where appropriate, since it is more likely fo=
r responses to be cachable.&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">As the ECS seems as attractive as the Cost Map Servi=
ce in many use cases, I'd prefer to mention preferences for both CostMap an=
d ECS with a text like:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;An ALTO Client may prefer to use GET requests =
for cacheable information. It may on the other hand prefer POST requests fo=
r example to get ALTO costs or properties on a restricted set of PIDs or En=
dpoints or to update cached information
 previously acquired via GET requests.&quot; <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">[Page 37] =A7 9.6. Cost Type <o:p></o:p></p>
<p class=3D"MsoNormal">text says: &quot;The combinaton of CostType and a Co=
stMode defines a CostType&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">Given the latest specs in =A76.1 and the IRD example=
s, the sentence should be &quot;The combinaton of &#43;a&#43; Cost&#43;&#43=
;Type and a Cost&#43;&#43;Mode defines a Cost&#43;&#43;Type&quot;<o:p></o:p=
></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The object CostType specified in this section contai=
ns a field called &quot;CostModel&quot; where I believe the &quot;l&quot; s=
hould be removed to give &quot;CostMode-l-&quot;.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">[Page 38] =A7 10 Protocol Specification: Service Inf=
ormation Resources<o:p></o:p></p>
<p class=3D"MsoNormal">A &quot;d&quot; should be added in sentence, to have=
: &quot;This section documents.... define&#43;d&#43; ... document&quot;.&nb=
sp;
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">[Page 40] Section 10.1.1.6 Example<o:p></o:p></p>
<p class=3D"MsoNormal">In paragraph after the example, in following part of=
 2nd sentence: &quot;such as transforming the Network Map into a IP trie&qu=
ot;: should it be &quot;tree&quot;?
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_A7A5844EB93EB94AB22C2068B10AD65A699E17FR711WXCHMBA01zeu_--

--_004_A7A5844EB93EB94AB22C2068B10AD65A699E17FR711WXCHMBA01zeu_
Content-Type: text/plain; name="alto_protocol-16_comments_sr.txt"
Content-Description: alto_protocol-16_comments_sr.txt
Content-Disposition: attachment;
	filename="alto_protocol-16_comments_sr.txt"; size=3078;
	creation-date="Fri, 21 Jun 2013 13:53:02 GMT";
	modification-date="Mon, 24 Jun 2013 17:00:25 GMT"
Content-Transfer-Encoding: base64

DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCkNPTU1FTlRTIE9OIGRy
YWZ0LWlldGYtYWx0by1wcm90b2NvbC0xNg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tDQoNCg0KLSBldmVyeXRoaW5nIGluICsrIGluZGljYXRlcyBBRERFRCB0ZXh0LCBp
bmNsdWRpbmcgd2hpdGUgc3BhY2UNCi0gZXZlcnl0aGluZyBpbiAtLSBpbmRpY2F0ZWQgUkVNT1ZF
RCB0ZXh0DQoNCg0KW1BhZ2UgMjddIKc4LjUuMyBFeGFtcGxlDQpUaGUgZXhhbXBsZSBJUkQgZXhw
b3NlcyBhIGNhcGFiaWxpdHkgY2FsbGVkICJjb3N0LXR5cGUtbmFtZSIgdGhhdCBpcyBub3QgaW50
cm9kdWNlZCBiZWZvcmUgYW5kIGl0IHdvdWxkIGhlbHAgdG8gYWRkIHNvbWUgc2VudGVuY2VzIHRv
IGJldHRlciBkaXN0aW5ndWlzaCB0aGUgcm9sZXMgb2YgImNvc3QtdHlwZS1uYW1lIiBhbmQgImNv
c3QtdHlwZSIuIEVzcGVjaWFsbHkgYXMgdGhlIGNvbWJpbmF0aW9uIG9mIGNvc3QgbWV0cmljIGFu
ZCBjb3N0IG1vZGUgaW50byBjb3N0IHR5cGUgaXMgbmV3IHRvIHBlb3BsZSB3aG8gYWxyZWFkeSBj
b2RlZCBhbiBBTFRPIENsaWVudC4gQmVzaWRlcywgdGhlIGZpZWxkICJjb3N0LXR5cGUiIG9mIHRo
ZSBtZXRhIG1lbWJlciBkZWZpbmVzIHRoZSBjb3N0IHR5cGUgbmFtZXMgYnV0IGFsc28gc3BlY2lm
aWVzIHRoZWlyIG1lbWJlcnMuIFNvIEkgcHJvcG9zZSB0byBhZGQgc29tZSB0ZXh0IGFmdGVyIHRo
ZSBleGFtcGxlIElSRCBhbmQgYmVmb3JlIHNlbnRlbmNlICJTcGVjaWZpY2FsbHksIHRoZSAibWV0
YSIgbWVtYmVyIG9mIHRoZSBleGFtcGxlIElSRCBkZWZpbmVzLi4uLiIsIHRoYXQgd291bGQgbG9v
ayBsaWtlOiANCg0KIldoZW4gYW4gQUxUTyBDbGllbnQgd2FudHMgdG8gZmV0Y2ggdGhlIENvc3Qg
VHlwZXMgc3VwcG9ydGVkIGF0IHRoZSB1cmlzIGxpc3RlZCBpbiB0aGUgQUxUTyBTZXJ2ZXIsIGl0
IHNob3VsZCBsb29rIGFmdGVyIHN0cmluZyAiY29zdC10eXBlLW5hbWVzIi4gVGhlIHZhbHVlcyBv
ZiAiY29zdC10eXBlLW5hbWVzIiBpbmRpY2F0ZSBDb3N0IFR5cGVzIHdob3NlIENvc3QgTWV0cmlj
IGFuZCBDb3N0IE1vZGUgYXJlIHNwZWNpZmllZCBpbiB0aGUgZmllbGQgImNvc3QtdHlwZSIgb2Yg
bWVtYmVyICJtZXRhIiBvZiB0aGUgSVJELiBTcGVjaWZpY2FsbHkgZXRjLiAuLi4iLiANCg0KIA0K
DQpbUGFnZSAyOF0gpyA4LjUuNCBEZWxlZ2F0aW9uIGFuZCBNdWx0aXBsZSBDaG9pY2VzDQpSZWRp
cmVjdGlvbiB0byBhbm90aGVyIElSRCBpcyBhbm90aGVyIG5ldyBmZWF0dXJlIHNvIGxpa2UgaW4g
dGhlIHByZXZpb3VzIHNlY3Rpb24sIEkgc3VnZ2VzdCB0byBhZGQgdGV4dCBvbiB0aGUgbWVkaWEt
dHlwZS4gQSBwcm9wb3NhbCBmb3IgdGhlIGZpcnN0IHBhcmFncmFwaDogDQoNCiIuLi4gSW4gdGhl
IGV4YW1wbGUgYWJvdmUsIHRoZSAtLSArZm91cnRoIHVyaS9lbnRyeSsgcHJvdmlkZXMgYWRkaXRp
b25hbCBOZXR3b3JrIGFuZCBDb3N0IE1hcHMgdmlhIGEgc2VwYXJhdGUgc3ViZG9tYWluLCAiY3Vz
dG9tLmFsdG8uZXhhbXBsZS5jb20iLiArVGhpcyByZS9pbmRpcmVjdGlvbiBpcyBpbmRpY2F0ZWQg
YnkgdGhlIG1lZGlhLXR5cGUgImFwcGxpY2F0aW9uL2FsdG8tZGlyZWN0b3J5K2pzb24iKy4gSW4g
cGFydGljdWxhciBldGMuIC4uLiIuIA0KDQoNCg0KW1BhZ2UgMzBdIKcgOC41LjUuMSBBTFRPIENs
aWVudA0KdGV4dCBzYXlzOiAiSW4gZ2VuZXJhbCwgaXQgaXMgcHJlZmVycmVkIGZvciBBTFRPIENs
aWVudHMgdG8gdXNlIEdFVCByZXF1ZXN0cyB3aGVyZSBhcHByb3ByaWF0ZSwgc2luY2UgaXQgaXMg
bW9yZSBsaWtlbHkgZm9yIHJlc3BvbnNlcyB0byBiZSBjYWNoYWJsZS4iDQoNCkFzIHRoZSBFQ1Mg
c2VlbXMgYXMgYXR0cmFjdGl2ZSBhcyB0aGUgQ29zdCBNYXAgU2VydmljZSBpbiBtYW55IHVzZSBj
YXNlcywgSSdkIHByZWZlciB0byBtZW50aW9uIHByZWZlcmVuY2VzIGZvciBib3RoIENvc3RNYXAg
YW5kIEVDUyB3aXRoIGEgdGV4dCBsaWtlOg0KDQoiQW4gQUxUTyBDbGllbnQgbWF5IHByZWZlciB0
byB1c2UgR0VUIHJlcXVlc3RzIGZvciBjYWNoZWFibGUgaW5mb3JtYXRpb24uIEl0IG1heSBvbiB0
aGUgb3RoZXIgaGFuZCBwcmVmZXIgUE9TVCByZXF1ZXN0cyBmb3IgZXhhbXBsZSB0byBnZXQgQUxU
TyBjb3N0cyBvciBwcm9wZXJ0aWVzIG9uIGEgcmVzdHJpY3RlZCBzZXQgb2YgUElEcyBvciBFbmRw
b2ludHMgb3IgdG8gdXBkYXRlIGNhY2hlZCBpbmZvcm1hdGlvbiBwcmV2aW91c2x5IGFjcXVpcmVk
IHZpYSBHRVQgcmVxdWVzdHMuIiANCg0KDQoNCltQYWdlIDM3XSCnIDkuNi4gQ29zdCBUeXBlIA0K
dGV4dCBzYXlzOiAiVGhlIGNvbWJpbmF0b24gb2YgQ29zdFR5cGUgYW5kIGEgQ29zdE1vZGUgZGVm
aW5lcyBhIENvc3RUeXBlIg0KR2l2ZW4gdGhlIGxhdGVzdCBzcGVjcyBpbiCnNi4xIGFuZCB0aGUg
SVJEIGV4YW1wbGVzLCB0aGUgc2VudGVuY2Ugc2hvdWxkIGJlICJUaGUgY29tYmluYXRvbiBvZiAr
YSsgQ29zdCsrVHlwZSBhbmQgYSBDb3N0KytNb2RlIGRlZmluZXMgYSBDb3N0KytUeXBlIg0KDQpU
aGUgb2JqZWN0IENvc3RUeXBlIHNwZWNpZmllZCBpbiB0aGlzIHNlY3Rpb24gY29udGFpbnMgYSBm
aWVsZCBjYWxsZWQgIkNvc3RNb2RlbCIgd2hlcmUgSSBiZWxpZXZlIHRoZSAibCIgc2hvdWxkIGJl
IHJlbW92ZWQgdG8gZ2l2ZSAiQ29zdE1vZGUtbC0iLiANCg0KDQoNCltQYWdlIDM4XSCnIDEwIFBy
b3RvY29sIFNwZWNpZmljYXRpb246IFNlcnZpY2UgSW5mb3JtYXRpb24gUmVzb3VyY2VzDQpBICJk
IiBzaG91bGQgYmUgYWRkZWQgaW4gc2VudGVuY2UsIHRvIGhhdmU6ICJUaGlzIHNlY3Rpb24gZG9j
dW1lbnRzLi4uLiBkZWZpbmUrZCsgLi4uIGRvY3VtZW50Ii4gIA0KDQoNCg0KW1BhZ2UgNDBdIFNl
Y3Rpb24gMTAuMS4xLjYgRXhhbXBsZQ0KSW4gcGFyYWdyYXBoIGFmdGVyIHRoZSBleGFtcGxlLCBp
biBmb2xsb3dpbmcgcGFydCBvZiAybmQgc2VudGVuY2U6ICJzdWNoIGFzIHRyYW5zZm9ybWluZyB0
aGUgTmV0d29yayBNYXAgaW50byBhIElQIHRyaWUiOiBzaG91bGQgaXQgYmUgInRyZWUiPyANCg0K

--_004_A7A5844EB93EB94AB22C2068B10AD65A699E17FR711WXCHMBA01zeu_--

From sabine.randriamasy@alcatel-lucent.com  Mon Jun 24 10:16:40 2013
Return-Path: <sabine.randriamasy@alcatel-lucent.com>
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 88CFC21E813C for <alto@ietfa.amsl.com>; Mon, 24 Jun 2013 10:16:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KmxZbKNF18Oc for <alto@ietfa.amsl.com>; Mon, 24 Jun 2013 10:16:33 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id A7AE221E8138 for <alto@ietf.org>; Mon, 24 Jun 2013 10:16:33 -0700 (PDT)
Received: from us70uusmtp4.zam.alcatel-lucent.com (h135-5-2-66.lucent.com [135.5.2.66]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r5OHGVBP025267 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Mon, 24 Jun 2013 12:16:32 -0500 (CDT)
Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (us70uwxchhub02.zam.alcatel-lucent.com [135.5.2.49]) by us70uusmtp4.zam.alcatel-lucent.com (GMO) with ESMTP id r5OHGVoj001121 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <alto@ietf.org>; Mon, 24 Jun 2013 13:16:31 -0400
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) by US70UWXCHHUB02.zam.alcatel-lucent.com (135.5.2.49) with Microsoft SMTP Server (TLS) id 14.2.247.3; Mon, 24 Jun 2013 13:16:31 -0400
Received: from FR711WXCHMBA01.zeu.alcatel-lucent.com ([169.254.1.6]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Mon, 24 Jun 2013 19:16:28 +0200
From: "RANDRIAMASY, SABINE (SABINE)" <sabine.randriamasy@alcatel-lucent.com>
To: "RANDRIAMASY, SABINE (SABINE)" <sabine.randriamasy@alcatel-lucent.com>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: draft-ietf-alto-protocol-16 - minor comments 
Thread-Index: AQHOcP6PUcLqPpstlUOjM9Lin6tMmQ==
Date: Mon, 24 Jun 2013 17:16:27 +0000
Message-ID: <A7A5844EB93EB94AB22C2068B10AD65A699E39@FR711WXCHMBA01.zeu.alcatel-lucent.com>
References: <A7A5844EB93EB94AB22C2068B10AD65A699E17@FR711WXCHMBA01.zeu.alcatel-lucent.com>
In-Reply-To: <A7A5844EB93EB94AB22C2068B10AD65A699E17@FR711WXCHMBA01.zeu.alcatel-lucent.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.38]
Content-Type: multipart/alternative; boundary="_000_A7A5844EB93EB94AB22C2068B10AD65A699E39FR711WXCHMBA01zeu_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Subject: Re: [alto] draft-ietf-alto-protocol-16 - minor comments
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 24 Jun 2013 17:16:40 -0000

--_000_A7A5844EB93EB94AB22C2068B10AD65A699E39FR711WXCHMBA01zeu_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Sorry, In my comment on [Page 37] =A7 9.6. Cost Type, I made the same typo =
I wanted to point out and forgot to indicate that "Cost Type" should be rep=
laced  by "Cost Metric" and "combinaton" by "combinat+i+on", so the sentenc=
e in =A7 9.6 should be:
be "The combinat+i+on of +a+ Cost+++Metric+ and a Cost++Mode defines a Cost=
++Type"

Sabine


De : alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] De la part de RAN=
DRIAMASY, SABINE (SABINE)
Envoy=E9 : lundi 24 juin 2013 19:03
=C0 : alto@ietf.org
Objet : [alto] draft-ietf-alto-protocol-16 - minor comments

Dear all,

While going through the latest update, I have listed some minor comments an=
d typos and  suggest some re-phrasings below, in particular in paragraphs o=
n new features such as the new cost type and the in/re-direction to other I=
RDs. I also attached a text file with the comments.
Hoping it helps.
Sabine


---------------------------------------
COMMENTS ON draft-ietf-alto-protocol-16
---------------------------------------


- everything in ++ indicates ADDED text, including white space
- everything in -- indicated REMOVED text


[Page 27] =A78.5.3 Example
The example IRD exposes a capability called "cost-type-name" that is not in=
troduced before and it would help to add some sentences to better distingui=
sh the roles of "cost-type-name" and "cost-type". Especially as the combina=
tion of cost metric and cost mode into cost type is new to people who alrea=
dy coded an ALTO Client. Besides, the field "cost-type" of the meta member =
defines the cost type names but also specifies their members. So I propose =
to add some text after the example IRD and before sentence "Specifically, t=
he "meta" member of the example IRD defines....", that would look like:

"When an ALTO Client wants to fetch the Cost Types supported at the uris li=
sted in the ALTO Server, it should look after string "cost-type-names". The=
 values of "cost-type-names" indicate Cost Types whose Cost Metric and Cost=
 Mode are specified in the field "cost-type" of member "meta" of the IRD. S=
pecifically etc. ...".


[Page 28] =A7 8.5.4 Delegation and Multiple Choices
Redirection to another IRD is another new feature so like in the previous s=
ection, I suggest to add text on the media-type. A proposal for the first p=
aragraph:

"... In the example above, the -- +fourth uri/entry+ provides additional Ne=
twork and Cost Maps via a separate subdomain, "custom.alto.example.com". +T=
his re/indirection is indicated by the media-type "application/alto-directo=
ry+json"+. In particular etc. ...".



[Page 30] =A7 8.5.5.1 ALTO Client
text says: "In general, it is preferred for ALTO Clients to use GET request=
s where appropriate, since it is more likely for responses to be cachable."

As the ECS seems as attractive as the Cost Map Service in many use cases, I=
'd prefer to mention preferences for both CostMap and ECS with a text like:

"An ALTO Client may prefer to use GET requests for cacheable information. I=
t may on the other hand prefer POST requests for example to get ALTO costs =
or properties on a restricted set of PIDs or Endpoints or to update cached =
information previously acquired via GET requests."



[Page 37] =A7 9.6. Cost Type
text says: "The combinaton of CostType and a CostMode defines a CostType"
Given the latest specs in =A76.1 and the IRD examples, the sentence should =
be "The combinaton of +a+ Cost++Type and a Cost++Mode defines a Cost++Type"

The object CostType specified in this section contains a field called "Cost=
Model" where I believe the "l" should be removed to give "CostMode-l-".



[Page 38] =A7 10 Protocol Specification: Service Information Resources
A "d" should be added in sentence, to have: "This section documents.... def=
ine+d+ ... document".



[Page 40] Section 10.1.1.6 Example
In paragraph after the example, in following part of 2nd sentence: "such as=
 transforming the Network Map into a IP trie": should it be "tree"?





--_000_A7A5844EB93EB94AB22C2068B10AD65A699E39FR711WXCHMBA01zeu_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">Sorry, In my comment on=
 [Page 37] =A7 9.6. Cost Type, I made the same typo I wanted to point out a=
nd forgot to indicate that &#8220;Cost Type&#8221; should be replaced &nbsp=
;by &#8220;Cost Metric&#8221; and &#8220;combinaton&#8221; by &#8220;combin=
at&#43;i&#43;on&#8221;,
 so the sentence in =A7 9.6 should be:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">be &quot;The combinat&#=
43;i&#43;on of &#43;a&#43; Cost&#43;&#43;&#43;Metric&#43; and a Cost&#43;&#=
43;Mode defines a Cost&#43;&#43;Type&quot;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">Sabine<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><b><span lang=3D"FR" st=
yle=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quo=
t;">De&nbsp;:</span></b><span lang=3D"FR" style=3D"font-size:10.0pt;font-fa=
mily:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> alto-bounces@ietf.org [mai=
lto:alto-bounces@ietf.org]
<b>De la part de</b> RANDRIAMASY, SABINE (SABINE)<br>
<b>Envoy=E9&nbsp;:</b> lundi 24 juin 2013 19:03<br>
<b>=C0&nbsp;:</b> alto@ietf.org<br>
<b>Objet&nbsp;:</b> [alto] draft-ietf-alto-protocol-16 - minor comments<o:p=
></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"FR">Dear =
all,</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><span lang=3D"FR">&nbsp=
;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">While going through the=
 latest update, I have listed some minor comments and typos and &nbsp;sugge=
st some re-phrasings below, in particular in paragraphs on new features suc=
h as the new cost type and the in/re-direction
 to other IRDs. I also attached a text file with the comments. <o:p></o:p><=
/p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">Hoping it helps. <o:p><=
/o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">Sabine<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">-----------------------=
----------------<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">COMMENTS ON draft-ietf-=
alto-protocol-16<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">-----------------------=
----------------<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">- everything in &#43;&#=
43; indicates ADDED text, including white space<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">- everything in -- indi=
cated REMOVED text<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">[Page 27] =A78.5.3 Exam=
ple<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">The example IRD exposes=
 a capability called &quot;cost-type-name&quot; that is not introduced befo=
re and it would help to add some sentences to better distinguish the roles =
of &quot;cost-type-name&quot; and &quot;cost-type&quot;. Especially
 as the combination of cost metric and cost mode into cost type is new to p=
eople who already coded an ALTO Client. Besides, the field &quot;cost-type&=
quot; of the meta member defines the cost type names but also specifies the=
ir members. So I propose to add some text
 after the example IRD and before sentence &quot;Specifically, the &quot;me=
ta&quot; member of the example IRD defines....&quot;, that would look like:
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&quot;When an ALTO Clie=
nt wants to fetch the Cost Types supported at the uris listed in the ALTO S=
erver, it should look after string &quot;cost-type-names&quot;. The values =
of &quot;cost-type-names&quot; indicate Cost Types whose Cost
 Metric and Cost Mode are specified in the field &quot;cost-type&quot; of m=
ember &quot;meta&quot; of the IRD. Specifically etc. ...&quot;.
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">[Page 28] =A7 8.5.4 Del=
egation and Multiple Choices<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">Redirection to another =
IRD is another new feature so like in the previous section, I suggest to ad=
d text on the media-type. A proposal for the first paragraph:
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&quot;... In the exampl=
e above, the -- &#43;fourth uri/entry&#43; provides additional Network and =
Cost Maps via a separate subdomain, &quot;custom.alto.example.com&quot;. &#=
43;This re/indirection is indicated by the media-type &quot;application/alt=
o-directory&#43;json&quot;&#43;.
 In particular etc. ...&quot;. <o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">[Page 30] =A7 8.5.5.1 A=
LTO Client<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">text says: &quot;In gen=
eral, it is preferred for ALTO Clients to use GET requests where appropriat=
e, since it is more likely for responses to be cachable.&quot;<o:p></o:p></=
p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">As the ECS seems as att=
ractive as the Cost Map Service in many use cases, I'd prefer to mention pr=
eferences for both CostMap and ECS with a text like:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&quot;An ALTO Client ma=
y prefer to use GET requests for cacheable information. It may on the other=
 hand prefer POST requests for example to get ALTO costs or properties on a=
 restricted set of PIDs or Endpoints or to
 update cached information previously acquired via GET requests.&quot; <o:p=
></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">[Page 37] =A7 9.6. Cost=
 Type <o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">text says: &quot;The co=
mbinaton of CostType and a CostMode defines a CostType&quot;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">Given the latest specs =
in =A76.1 and the IRD examples, the sentence should be &quot;The combinaton=
 of &#43;a&#43; Cost&#43;&#43;Type and a Cost&#43;&#43;Mode defines a Cost&=
#43;&#43;Type&quot;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">The object CostType spe=
cified in this section contains a field called &quot;CostModel&quot; where =
I believe the &quot;l&quot; should be removed to give &quot;CostMode-l-&quo=
t;.
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">[Page 38] =A7 10 Protoc=
ol Specification: Service Information Resources<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">A &quot;d&quot; should =
be added in sentence, to have: &quot;This section documents.... define&#43;=
d&#43; ... document&quot;.&nbsp;
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">[Page 40] Section 10.1.=
1.6 Example<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">In paragraph after the =
example, in following part of 2nd sentence: &quot;such as transforming the =
Network Map into a IP trie&quot;: should it be &quot;tree&quot;?
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:36.0pt">&nbsp;<o:p></o:p></p>
</div>
</body>
</html>

--_000_A7A5844EB93EB94AB22C2068B10AD65A699E39FR711WXCHMBA01zeu_--

From michael.scharf@alcatel-lucent.com  Mon Jun 24 12:19:51 2013
Return-Path: <michael.scharf@alcatel-lucent.com>
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 1FC3E11E817C for <alto@ietfa.amsl.com>; Mon, 24 Jun 2013 12:19:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tgwbe-syGT9S for <alto@ietfa.amsl.com>; Mon, 24 Jun 2013 12:19:44 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 216B221E80EF for <alto@ietf.org>; Mon, 24 Jun 2013 12:19:43 -0700 (PDT)
Received: from us70tusmtp2.zam.alcatel-lucent.com (h135-5-2-64.lucent.com [135.5.2.64]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id r5OJJgKr024260 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 24 Jun 2013 14:19:42 -0500 (CDT)
Received: from US70UWXCHHUB01.zam.alcatel-lucent.com (us70uwxchhub01.zam.alcatel-lucent.com [135.5.2.48]) by us70tusmtp2.zam.alcatel-lucent.com (GMO) with ESMTP id r5OJJdZP019369 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 24 Jun 2013 15:19:41 -0400
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) by US70UWXCHHUB01.zam.alcatel-lucent.com (135.5.2.48) with Microsoft SMTP Server (TLS) id 14.2.247.3; Mon, 24 Jun 2013 15:19:39 -0400
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.60]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Mon, 24 Jun 2013 21:19:36 +0200
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: Richard Alimi <rich@velvetsea.net>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: [alto] Clarifying Cost Map Dependencies on a Network Map
Thread-Index: AQHObYo095s5ObXcEEK23h+TvXwMW5lFNqTA
Date: Mon, 24 Jun 2013 19:19:35 +0000
Message-ID: <655C07320163294895BBADA28372AF5D05119A@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <CA+cvDaaHTb0G3x8E3NwSC4fu1AsaW2z9xA=dWUiERM9DXG_o=A@mail.gmail.com>
In-Reply-To: <CA+cvDaaHTb0G3x8E3NwSC4fu1AsaW2z9xA=dWUiERM9DXG_o=A@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Subject: Re: [alto] Clarifying Cost Map Dependencies on a Network Map
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 24 Jun 2013 19:19:51 -0000

I agree that in particular scenario 2 is relevant and should be addressed.=
=20

Like Sabine, I wonder how a client would actually deal with two different n=
etwork maps if we don't provide any hint in the IRD (probably IRD entries c=
an be entirely optional if there is only one network map). Should the clien=
t query all candidate cost maps in that case?

For what it is worth, at first sight, an alternative to the proposed "refer=
s-to" solution on slide 8 of the interim meeting slide deck would be an ext=
ended IRD entry for each network map:

       {
         "uri" : "http://alto.example.com/networkmap1",
         "media-type" : "application/alto-networkmap+json",
         "used-by": {
           "http://alto.example.com/costmap/num/routingcost_lowres"
         }
       },
       {
         "uri" : "http://alto.example.com/networkmap2",
         "media-type" : "application/alto-networkmap+json",
         "used-by": {
           "http://alto.example.com/costmap/num/routingcost_highres"
         }
       },

One motivation for that syntax would be to better explain the differences b=
etween the several network maps. I don't have any strong preference, though=
.

Another potential solution would be to define network map capabilities (suc=
h as "resolution" for scenario 2). Has this been discussed already? That ap=
proach alone might not solve scenario 1.


Finally, after having re-read some parts of -16, I wonder if some sections =
implicitly assume that there is only a single network map (notable exceptio=
n: Section 6.3). For instance:

"10.1.1. Network Map

   The Network Map Information Resource lists for each PID, the network
   locations (endpoints) within the PID.  It MUST be provided by an ALTO
   Server."

"It" is a little bit unclear to me. More explicit would be something like "=
An ALTO server MUST provide at least one network map."

Best regards

Michael



> -----Original Message-----
> From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On=20
> Behalf Of Richard Alimi
> Sent: Thursday, June 20, 2013 9:45 AM
> To: alto@ietf.org
> Subject: [alto] Clarifying Cost Map Dependencies on a Network Map
>=20
> [ We would like to hear feedback on this.  We are planning to=20
> revise and submit a new version ASAP, so please voice=20
> opinions on this within the next few days, by Monday, June 24th. ]
>=20
> Background:
>=20
> Today, the ALTO protocol as a 'version tag' to indicate which=20
> version of a network map is used by a particular cost map.
>=20
> In a particularly simple case, a single ALTO server is served=20
> by a single hostname (or IP address, whatever), and it=20
> exposes a single network map and one or more cost maps. =20
> There is no ambiguity here - a client automatically knows=20
> that any version tag refers to the single network map that is=20
> hosted by the server.
>=20
> There are two alternate scenarios where ambiguities arrive:
>=20
> (Scenario 1) An IRD hosted by alto.isp1.example.com refers=20
> cost maps provided by some third-party, say=20
> alto.third-party.example.com.  In this scenario, do version=20
> tags exposed by alto.third-party.example.com correspond to=20
> the network map provided by alto.isp1.example.com?
>=20
> (Scenario 2) A single ALTO server (single hostname) wishes to=20
> provide two different network maps (say, different levels of=20
> aggregation) and wants to provide cost maps for each of them.=20
>  Currently, the version tag accompanying a cost map is not=20
> sufficient for a client to determine which network map a=20
> particular cost map is based on.
>=20
> Proposal:
>=20
> To resolve these problems, we'd like to propose a simple=20
> change to the version tag accompanying the cost map - it=20
> would now include the URI to the network map in addition to=20
> an opaque ID.
>=20
> OLD (what we have now):
>=20
> {
>  "meta" : {},
>  "data" : {
>    "cost-type" : {"cost-mode"  : "numerical",
>                   "cost-metric": "routingcost"},
>    "map-vtag"  : "1266506139",
>    "map" : {
>      "PID1": { "PID1": 1,  "PID2": 5,  "PID3": 10 },
>      "PID2": { "PID1": 5,  "PID2": 1,  "PID3": 15 },
>      "PID3": { "PID1": 20, "PID2": 15  }
>    }
>  }
> }
>=20
> NEW PROPOSAL:
>=20
> {
>  "meta" : {},
>  "data" : {
>    "cost-type" : {"cost-mode"  : "numerical",
>                   "cost-metric": "routingcost"},
>    "network-map" : {
>      "uri": "http://alto.example.com/networkmap1"
>      "vtag": "1266506139"
>=20
>=20
>      }
>    "map" : {
>      "PID1": { "PID1": 1,  "PID2": 5,  "PID3": 10 },
>      "PID2": { "PID1": 5,  "PID2": 1,  "PID3": 15 },
>      "PID3": { "PID1": 20, "PID2": 15  }
>    }
>  }
> }
>=20
> Compared to the current approach we have in draft -16 (which=20
> is for a version tag to be consistent within resources served=20
> by the same hostname), this has the following advantages:
> - It provides a more flexible solution to Scenario 1
> - It allows us to handle Scenario 2
>=20
> An possible addition to this approach would be explicitly=20
> declare the dependency between the cost map and the network=20
> map in the IRD.
>=20
> Feedback would be great.  The editors believe this would be a=20
> strong improvement to the draft.
>=20
> Thanks,
> Rich
> =

From yang.r.yang@gmail.com  Sun Jun 30 21:17:06 2013
Return-Path: <yang.r.yang@gmail.com>
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 BC6C521F9EDC for <alto@ietfa.amsl.com>; Sun, 30 Jun 2013 21:17:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6vTEyO1+iRTm for <alto@ietfa.amsl.com>; Sun, 30 Jun 2013 21:17:05 -0700 (PDT)
Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 7E16121F9ED3 for <alto@ietf.org>; Sun, 30 Jun 2013 21:17:05 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id r10so2275377pdi.13 for <alto@ietf.org>; Sun, 30 Jun 2013 21:17:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Z1dc/HDICoC7bYFDd37TbI3NMSpS5OYeN8Tfoy2gkXM=; b=WJO8FbdGjhhQm+pELs1TnbuQSqUJDwjVxBDnW2ofQSXIRJbiWYMrT9tLsSQ198e8tI zPAjg4BpwfGNJjb9ryMXm+jLBHz8w55hmIpI1mp7WL7MWVAaCNtHwaqjo0w4V/887nFP XjtaY+YMgfepaOVKfADDbTFAlPcOQtHJL9ceq2LuD0j0ykAJo+wcLSoEEyWLM7XOfQG1 6OJXLms2cziccLuAeumDU6VxNXUlHakOIhBCzqMoVyCdQeNopglgNE+29hQeR+yQyPpo BdtdZlfTYcrgNt0jMoxYcNFTOpCVh5qfLlANSiHZhmELl3BFclR90U7qnwTz/C+wA88F g0qQ==
MIME-Version: 1.0
X-Received: by 10.68.115.131 with SMTP id jo3mr22122431pbb.133.1372652223210;  Sun, 30 Jun 2013 21:17:03 -0700 (PDT)
Sender: yang.r.yang@gmail.com
Received: by 10.68.43.99 with HTTP; Sun, 30 Jun 2013 21:17:02 -0700 (PDT)
In-Reply-To: <A7A5844EB93EB94AB22C2068B10AD65A699E17@FR711WXCHMBA01.zeu.alcatel-lucent.com>
References: <A7A5844EB93EB94AB22C2068B10AD65A699E17@FR711WXCHMBA01.zeu.alcatel-lucent.com>
Date: Mon, 1 Jul 2013 00:17:02 -0400
X-Google-Sender-Auth: hYnHaiVlG_w2YtwRF2AYvUN9Ll0
Message-ID: <CANUuoLpw57Xx=m_ykGEdRpFnb+RQ-9jn1UHwt=G=PG7W_pBaTw@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
To: "RANDRIAMASY, SABINE (SABINE)" <sabine.randriamasy@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=047d7b111c992a290804e06b8053
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] draft-ietf-alto-protocol-16 - minor comments
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 01 Jul 2013 04:17:06 -0000

--047d7b111c992a290804e06b8053
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Sabine,

Thanks a lot for the excellent comments! Please see below.


On Mon, Jun 24, 2013 at 1:02 PM, RANDRIAMASY, SABINE (SABINE) <
sabine.randriamasy@alcatel-lucent.com> wrote:

>  Dear all,****
>
> ** **
>
> While going through the latest update, I have listed some minor comments
> and typos and  suggest some re-phrasings below, in particular in paragrap=
hs
> on new features such as the new cost type and the in/re-direction to othe=
r
> IRDs. I also attached a text file with the comments. ****
>
> Hoping it helps. ****
>
> Sabine****
>
> ** **
>
> ** **
>
> ---------------------------------------****
>
> COMMENTS ON draft-ietf-alto-protocol-16****
>
> ---------------------------------------****
>
> ** **
>
> ** **
>
> - everything in ++ indicates ADDED text, including white space****
>
> - everything in -- indicated REMOVED text****
>
> ** **
>
> ** **
>
> [Page 27] =A78.5.3 Example****
>
> The example IRD exposes a capability called "cost-type-name" that is not
> introduced before and it would help to add some sentences to better
> distinguish the roles of "cost-type-name" and "cost-type". Especially as
> the combination of cost metric and cost mode into cost type is new to
> people who already coded an ALTO Client. Besides, the field "cost-type" o=
f
> the meta member defines the cost type names but also specifies their
> members. So I propose to add some text after the example IRD and before
> sentence "Specifically, the "meta" member of the example IRD defines...."=
,
> that would look like: ****
>
> ** **
>
> "When an ALTO Client wants to fetch the Cost Types supported at the uris
> listed in the ALTO Server, it should look after string "cost-type-names".
> The values of "cost-type-names" indicate Cost Types whose Cost Metric and
> Cost Mode are specified in the field "cost-type" of member "meta" of the
> IRD. Specifically etc. ...". ** **
>
> ** **** **
>
Good comment. Here is the new text based on your suggestion:

      Specifically, the "meta" member of the example IRD defines a
      field named "cost-types", which defines the names of cost
      types. For example, "num-routing" in the example is the name
      that refers to a Cost Type with Cost Mode being "numerical" and
      Cost Metric being "routingcost".  The value of "cost-types" is
      of type IRDMetaCostTypes defined below; see  Section 9.6 for the
definition of CostType.

      The names defined in "cost-types" can be used in the
      "resources" entries. For example, the second entry of
      "resources" defines a Cost Map.  The "cost-type-names" of its
      "capabilities" specifies that this resource supports a Cost Type
      named as "num-routing". The ALTO Client looks up the name
      "num-routing" in "cost-types" of the IRD to obtain the Cost Type
      named as "num-routing". The last entry of "resources" uses all
      four names defined in "cost-types".


> [Page 28] =A7 8.5.4 Delegation and Multiple Choices****
>
> Redirection to another IRD is another new feature so like in the previous
> section, I suggest to add text on the media-type. A proposal for the firs=
t
> paragraph:
>
> "... In the example above, the -- +fourth uri/entry+ provides additional
> Network and Cost Maps via a separate subdomain, "custom.alto.example.com"=
.
> +This re/indirection is indicated by the media-type
> "application/alto-directory+json"+. In particular etc. ... ".
>

Good suggestion. Here is the new text based on your suggestion:

     Consider the preceding example.  The fourth entry of
      "resources" provides additional Network and Cost Maps via a
      separate subdomain: "custom.alto.example.com". This delegation
      is indicated by the media-type
      "application/alto-directory+json". The ALTO Client can discover
      the maps available at "custom.alto.example.com" by successfully
      performing a request to
      "http://custom.alto.example.com/maps":

> **
>
> ** **
>
> ** **
>
> ** **
>
> [Page 30] =A7 8.5.5.1 ALTO Client****
>
> text says: "In general, it is preferred for ALTO Clients to use GET
> requests where appropriate, since it is more likely for responses to be
> cachable."****
>
> ** **
>
> As the ECS seems as attractive as the Cost Map Service in many use cases,
> I'd prefer to mention preferences for both CostMap and ECS with a text li=
ke:
> ****
>
> ** **
>
> "An ALTO Client may prefer to use GET requests for cacheable information.
> It may on the other hand prefer POST requests for example to get ALTO cos=
ts
> or properties on a restricted set of PIDs or Endpoints or to update cache=
d
> information previously acquired via GET requests." ****
>
> **
>
Here is the revised text to add the POST part f your suggestion:

       In general, it is preferred for ALTO Clients to use GET
        requests where appropriate, since it is more likely for
        responses to be cachable. However, an ALTO Client may need to
        use POST, for example, to get ALTO costs or properties that
        are for a restricted set of PIDs or Endpoints, or to update
        cached information previously acquired via GET requests."

> **
>
> ** **
>
> [Page 37] =A7 9.6. Cost Type ****
>
> text says: "The combinaton of CostType and a CostMode defines a CostType"=
*
> ***
>
> Given the latest specs in =A76.1 and the IRD examples, the sentence shoul=
d
> be "The combinaton of +a+ Cost++Type and a Cost++Mode defines a Cost++Typ=
e"
> ****
>
> ** **
>
> The object CostType specified in this section contains a field called
> "CostModel" where I believe the "l" should be removed to give
> "CostMode-l-". ****
>
> **
>
Fixed both:
       The combination of a CostMetric and a CostMode defines a
      CostType:
object {
  CostMetric cost-metric;
  CostMode   cost-mode;
  [JSONString description;]
} CostType;


> **
>
> ** **
>
> ** **
>
> [Page 38] =A7 10 Protocol Specification: Service Information Resources***=
*
>
> A "d" should be added in sentence, to have: "This section documents....
> define+d+ ... document".  ****
>
> ** **
>
> **
>
Good catch. Fixed.


>  **
>
> ** **
>
> [Page 40] Section 10.1.1.6 Example****
>
> In paragraph after the example, in following part of 2nd sentence: "such
> as transforming the Network Map into a IP trie": should it be "tree"? ***=
*
>
> **
>
I see the ambiguity. Here is a new text:

 If lookup efficiency at runtime is crucial, then the returned
         Cost Map and Network Map can be transformed into data
         structures offering more efficient lookup. For example, one
         may store the Cost Map as a matrix, and the Network Map as a
         trie-based data structure, which may allow efficient
         longest-prefix matching of IP addresses.

Please let us know if they address your comments.

Thanks again.

Richard

> **
>
> ** **
>
> ** **
>
> ** **
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
>

--047d7b111c992a290804e06b8053
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Sabine,<div><br></div><div style>Thanks a lot for the e=
xcellent comments! Please see below.</div><div class=3D"gmail_extra"><br><b=
r><div class=3D"gmail_quote">On Mon, Jun 24, 2013 at 1:02 PM, RANDRIAMASY, =
SABINE (SABINE) <span dir=3D"ltr">&lt;<a href=3D"mailto:sabine.randriamasy@=
alcatel-lucent.com" target=3D"_blank">sabine.randriamasy@alcatel-lucent.com=
</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D""><span lang=3D"FR">Dear all,<u></u><u></u></span></p>
<p class=3D""><span lang=3D"FR"><u></u>=A0<u></u></span></p>
<p class=3D"">While going through the latest update, I have listed some min=
or comments and typos and =A0suggest some re-phrasings below, in particular=
 in paragraphs on new features such as the new cost type and the in/re-dire=
ction to other IRDs. I also
 attached a text file with the comments. <u></u><u></u></p>
<p class=3D"">Hoping it helps. <u></u><u></u></p>
<p class=3D"">Sabine<u></u><u></u></p>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D"">---------------------------------------<u></u><u></u></p>
<p class=3D"">COMMENTS ON draft-ietf-alto-protocol-16<u></u><u></u></p>
<p class=3D"">---------------------------------------<u></u><u></u></p>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D"">- everything in ++ indicates ADDED text, including white spac=
e<u></u><u></u></p>
<p class=3D"">- everything in -- indicated REMOVED text<u></u><u></u></p>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D"">[Page 27] =A78.5.3 Example<u></u><u></u></p>
<p class=3D"">The example IRD exposes a capability called &quot;cost-type-n=
ame&quot; that is not introduced before and it would help to add some sente=
nces to better distinguish the roles of &quot;cost-type-name&quot; and &quo=
t;cost-type&quot;. Especially as the combination of cost
 metric and cost mode into cost type is new to people who already coded an =
ALTO Client. Besides, the field &quot;cost-type&quot; of the meta member de=
fines the cost type names but also specifies their members. So I propose to=
 add some text after the example IRD and before
 sentence &quot;Specifically, the &quot;meta&quot; member of the example IR=
D defines....&quot;, that would look like:
<u></u><u></u></p>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D"">&quot;When an ALTO Client wants to fetch the Cost Types suppo=
rted at the uris listed in the ALTO Server, it should look after string &qu=
ot;cost-type-names&quot;. The values of &quot;cost-type-names&quot; indicat=
e Cost Types whose Cost Metric and Cost Mode are specified
 in the field &quot;cost-type&quot; of member &quot;meta&quot; of the IRD. =
Specifically etc. ...&quot;. <u></u>
<u></u></p>
<p class=3D""><u></u>=A0<u></u><u></u>=A0<u></u></p></div></div></blockquot=
e><div style>Good comment. Here is the new text based on your suggestion:</=
div><div style><br></div><div style><div>=A0 =A0 =A0 Specifically, the &quo=
t;meta&quot; member of the example IRD defines a</div>
<div>=A0 =A0 =A0 field named &quot;cost-types&quot;, which defines the name=
s of cost</div><div>=A0 =A0 =A0 types. For example, &quot;num-routing&quot;=
 in the example is the name</div><div>=A0 =A0 =A0 that refers to a Cost Typ=
e with Cost Mode being &quot;numerical&quot; and</div>
<div>=A0 =A0 =A0 Cost Metric being &quot;routingcost&quot;. =A0The value of=
 &quot;cost-types&quot; is</div><div>=A0 =A0 =A0 of type IRDMetaCostTypes d=
efined below; see =A0Section 9.6 for the definition of CostType.</div><div>=
<br></div><div>
=A0 =A0 =A0 The names defined in &quot;cost-types&quot; can be used in the<=
/div><div>=A0 =A0 =A0 &quot;resources&quot; entries. For example, the secon=
d entry of</div><div>=A0 =A0 =A0 &quot;resources&quot; defines a Cost Map. =
=A0The &quot;cost-type-names&quot; of its</div>
<div>=A0 =A0 =A0 &quot;capabilities&quot; specifies that this resource supp=
orts a Cost Type</div><div>=A0 =A0 =A0 named as &quot;num-routing&quot;. Th=
e ALTO Client looks up the name</div><div>=A0 =A0 =A0 &quot;num-routing&quo=
t; in &quot;cost-types&quot; of the IRD to obtain the Cost Type</div>
<div>=A0 =A0 =A0 named as &quot;num-routing&quot;. The last entry of &quot;=
resources&quot; uses all</div><div>=A0 =A0 =A0 four names defined in &quot;=
cost-types&quot;.</div></div><div style>=A0</div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left=
-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div>
<p class=3D"">[Page 28] =A7 8.5.4 Delegation and Multiple Choices<u></u><u>=
</u></p>
<p class=3D"">Redirection to another IRD is another new feature so like in =
the previous section, I suggest to add text on the media-type. A proposal f=
or the first paragraph:</p>
<p class=3D"">&quot;... In the example above, the -- +fourth uri/entry+ pro=
vides additional Network and Cost Maps via a separate subdomain, &quot;<a h=
ref=3D"http://custom.alto.example.com" target=3D"_blank">custom.alto.exampl=
e.com</a>&quot;. +This re/indirection is indicated by the media-type &quot;=
application/alto-directory+json&quot;+.
 In particular etc. ... &quot;.</p></div></div></blockquote><div><br></div>=
<div style>Good suggestion. Here is the new text based on your suggestion:<=
/div><div style>=A0</div><div style><div>=A0 =A0 =A0Consider the preceding =
example. =A0The fourth entry of</div>
<div>=A0 =A0 =A0 &quot;resources&quot; provides additional Network and Cost=
 Maps via a</div><div>=A0 =A0 =A0 separate subdomain: &quot;<a href=3D"http=
://custom.alto.example.com">custom.alto.example.com</a>&quot;. This delegat=
ion</div><div>
=A0 =A0 =A0 is indicated by the media-type</div><div>=A0 =A0 =A0 &quot;appl=
ication/alto-directory+json&quot;. The ALTO Client can discover</div><div>=
=A0 =A0 =A0 the maps available at &quot;<a href=3D"http://custom.alto.examp=
le.com">custom.alto.example.com</a>&quot; by successfully</div>
<div>=A0 =A0 =A0 performing a request to</div><div>=A0 =A0 =A0 &quot;<a hre=
f=3D"http://custom.alto.example.com/maps">http://custom.alto.example.com/ma=
ps</a>&quot;:</div></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);=
border-left-style:solid;padding-left:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D""><u></=
u></p>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D"">[Page 30] =A7 8.5.5.1 ALTO Client<u></u><u></u></p>
<p class=3D"">text says: &quot;In general, it is preferred for ALTO Clients=
 to use GET requests where appropriate, since it is more likely for respons=
es to be cachable.&quot;<u></u><u></u></p>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D"">As the ECS seems as attractive as the Cost Map Service in man=
y use cases, I&#39;d prefer to mention preferences for both CostMap and ECS=
 with a text like:<u></u><u></u></p>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D"">&quot;An ALTO Client may prefer to use GET requests for cache=
able information. It may on the other hand prefer POST requests for example=
 to get ALTO costs or properties on a restricted set of PIDs or Endpoints o=
r to update cached information
 previously acquired via GET requests.&quot; <u></u><u></u></p>
<p class=3D""><u></u>=A0</p></div></div></blockquote><div style>Here is the=
 revised text to add the POST part f your suggestion:</div><div style><br><=
div>=A0 =A0 =A0 =A0In general, it is preferred for ALTO Clients to use GET<=
/div><div>
=A0 =A0 =A0 =A0 requests where appropriate, since it is more likely for</di=
v><div>=A0 =A0 =A0 =A0 responses to be cachable. However, an ALTO Client ma=
y need to</div><div>=A0 =A0 =A0 =A0 use POST, for example, to get ALTO cost=
s or properties that</div>
<div>=A0 =A0 =A0 =A0 are for a restricted set of PIDs or Endpoints, or to u=
pdate</div><div>=A0 =A0 =A0 =A0 cached information previously acquired via =
GET requests.&quot;=A0</div></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><p class=3D""><u></u></p=
>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D"">[Page 37] =A7 9.6. Cost Type <u></u><u></u></p>
<p class=3D"">text says: &quot;The combinaton of CostType and a CostMode de=
fines a CostType&quot;<u></u><u></u></p>
<p class=3D"">Given the latest specs in =A76.1 and the IRD examples, the se=
ntence should be &quot;The combinaton of +a+ Cost++Type and a Cost++Mode de=
fines a Cost++Type&quot;<u></u><u></u></p>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D"">The object CostType specified in this section contains a fiel=
d called &quot;CostModel&quot; where I believe the &quot;l&quot; should be =
removed to give &quot;CostMode-l-&quot;.
<u></u><u></u></p>
<p class=3D""><u></u>=A0</p></div></blockquote><div style>Fixed both:</div>=
<div style>=A0 =A0 =A0 =A0The combination of a CostMetric and a CostMode de=
fines a</div><div>=A0 =A0 =A0 CostType:</div><div>object {</div><div>=A0 Co=
stMetric cost-metric;</div>
<div>=A0 CostMode =A0 cost-mode;</div><div>=A0 [JSONString description;]</d=
iv><div>} CostType;</div><div>=A0=A0</div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:=
rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D""><u></=
u></p>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D"">[Page 38] =A7 10 Protocol Specification: Service Information =
Resources<u></u><u></u></p>
<p class=3D"">A &quot;d&quot; should be added in sentence, to have: &quot;T=
his section documents.... define+d+ ... document&quot;.=A0
<u></u><u></u></p>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D""><u></u></p></div></div></blockquote><div style>Good catch. Fi=
xed.</div><div style>=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,=
204);border-left-style:solid;padding-left:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D"">=A0<u=
></u></p>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D"">[Page 40] Section 10.1.1.6 Example<u></u><u></u></p>
<p class=3D"">In paragraph after the example, in following part of 2nd sent=
ence: &quot;such as transforming the Network Map into a IP trie&quot;: shou=
ld it be &quot;tree&quot;?
<u></u><u></u></p>
<p class=3D""><u></u>=A0</p></div></div></blockquote><div style>I see the a=
mbiguity. Here is a new text:</div><div style><br></div><div style><div>=A0=
If lookup efficiency at runtime is crucial, then the returned</div><div>=A0=
 =A0 =A0 =A0 =A0Cost Map and Network Map can be transformed into data</div>
<div>=A0 =A0 =A0 =A0 =A0structures offering more efficient lookup. For exam=
ple, one</div><div>=A0 =A0 =A0 =A0 =A0may store the Cost Map as a matrix, a=
nd the Network Map as a</div><div>=A0 =A0 =A0 =A0 =A0trie-based data struct=
ure, which may allow efficient</div>
<div>=A0 =A0 =A0 =A0 =A0longest-prefix matching of IP addresses.</div><div>=
<br></div><div style>Please let us know if they address your comments.</div=
><div style><br></div><div style>Thanks again.</div><div style><br></div><d=
iv style>
Richard</div></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border=
-left-style:solid;padding-left:1ex"><div lang=3D"EN-US" link=3D"blue" vlink=
=3D"purple">
<div><p class=3D""><u></u></p>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D""><u></u>=A0<u></u></p>
</div>
</div>

<br>_______________________________________________<br>
alto mailing list<br>
<a href=3D"mailto:alto@ietf.org">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/alto</a><br>
<br></blockquote></div><br></div></div>

--047d7b111c992a290804e06b8053--

From richard.alimi@gmail.com  Sun Jun 30 23:44:10 2013
Return-Path: <richard.alimi@gmail.com>
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 9299021F9F2F for <alto@ietfa.amsl.com>; Sun, 30 Jun 2013 23:44:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IQov9ch1tbKd for <alto@ietfa.amsl.com>; Sun, 30 Jun 2013 23:44:09 -0700 (PDT)
Received: from mail-vc0-x22b.google.com (mail-vc0-x22b.google.com [IPv6:2607:f8b0:400c:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id B8BC721F9F2B for <alto@ietf.org>; Sun, 30 Jun 2013 23:44:08 -0700 (PDT)
Received: by mail-vc0-f171.google.com with SMTP id gd11so1737777vcb.30 for <alto@ietf.org>; Sun, 30 Jun 2013 23:44:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=IHKaBSIT7gYijrP9yytUJzcg8oqiw6M/dNb1e75jWjE=; b=I91QVF4OsOBamrp6nwGO2rhhzQ/Uy53Ml0NT9VexBvIz5ckXhcZsfhpqNsiIQqiOHP f2Qkkrov/SDb9zTOpYrcuFXR62E/EIKYsuc+heHmmdYqQbXB6NVRysjqIkyl9rtzV2PJ yCJlRCJXQMaZCdremf39q+7nkEKzci42VoBf+dqcGY+K82gxJtJJ/fStIolTcJc7g6v7 84t9hNmbR9H6CJDDg6YLkq3sZnh2PBlOY0ghqbSqbVT6ZWVWT+irOJgriAh5mWegpQKd mECFgd/nItrnzngmVnx0VLJ5TCrdUXkM6rCySlAFXFgm8dSXKuwhL/RPNny9MLNGOKKF gK/w==
X-Received: by 10.58.29.228 with SMTP id n4mr9244593veh.50.1372661042576; Sun, 30 Jun 2013 23:44:02 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.52.17.193 with HTTP; Sun, 30 Jun 2013 23:43:42 -0700 (PDT)
In-Reply-To: <655C07320163294895BBADA28372AF5D05119A@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <CA+cvDaaHTb0G3x8E3NwSC4fu1AsaW2z9xA=dWUiERM9DXG_o=A@mail.gmail.com> <655C07320163294895BBADA28372AF5D05119A@FR712WXCHMBA15.zeu.alcatel-lucent.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Sun, 30 Jun 2013 23:43:42 -0700
X-Google-Sender-Auth: hEORRXHf_KZhKgqKr-hGaCQtnDo
Message-ID: <CA+cvDaawQ6MazSw5gNYCuCcxbBWVdV+JA_nGGxPcpt2G7B787w@mail.gmail.com>
To: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=047d7b6d8dacd7055404e06d8dcc
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Clarifying Cost Map Dependencies on a Network Map
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 01 Jul 2013 06:44:10 -0000

--047d7b6d8dacd7055404e06d8dcc
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Jun 24, 2013 at 12:19 PM, Scharf, Michael (Michael) <
michael.scharf@alcatel-lucent.com> wrote:

> I agree that in particular scenario 2 is relevant and should be addressed.
>
> Like Sabine, I wonder how a client would actually deal with two different
> network maps if we don't provide any hint in the IRD (probably IRD entries
> can be entirely optional if there is only one network map). Should the
> client query all candidate cost maps in that case?
>

One possibility would be to first grab for the desired cost map, and then
retrieve the network map it depends on.  There is a potential loss in
efficiency since the client could fetch the network map and cost map in
parallel.

This seems to point in favor of listing the dependency explicitly in the
IRD, and I'm okay with that.  IIRC, Richard Yang was in favor of this as
well.

All that said, I was sitting down to write the text, and it turns out to be
a bit tricky.  In particular, when one specifies the URI for the network
map in the "refers-to" attribute, which URI is it?  Is it the exact same
URI present in the Network Map's entry in the IRD, or is it some canonical
(absolute) URI for that Network Map resource?  If the former, then those
URIs may be relative and this doesn't handle Scenario 1 very well.  If the
latter, then the ALTO Server generating the IRD has to know the series of
redirects that the client may experience (since the client may get relative
URIs for each Information Resource, and Section 5 of RFC3986 indicates that
the result of the relative -> absolute conversion may be dependent on
redirects that were followed).  These solutions get to be kind of ugly.

Two ideas come to mind for what we can do:
(1) Give each Information Resource a UUID, and refer to the dependencies by
UUID instead of a URI.
(2) Consider the addition of metadata to the IRD to declare dependencies to
be an extension (but we must still change Version Tags to declare the URI
for the Network Map in the base protocol).

I do think this is a nice-to-have optimization, but I don't think its
strictly necessary to satisfy this use case.  I could be persuaded either
way.

[ The change to the Version Tags ends up being straightforward, since the
server specifies all of them explicitly and can enforce that a single
Network Map URI be returned; there is no ambiguity introduced by relative
URIs in that case. ]


> For what it is worth, at first sight, an alternative to the proposed
> "refers-to" solution on slide 8 of the interim meeting slide deck would be
> an extended IRD entry for each network map:
>
>        {
>          "uri" : "http://alto.example.com/networkmap1",
>          "media-type" : "application/alto-networkmap+json",
>          "used-by": {
>            "http://alto.example.com/costmap/num/routingcost_lowres"
>          }
>        },
>        {
>          "uri" : "http://alto.example.com/networkmap2",
>          "media-type" : "application/alto-networkmap+json",
>          "used-by": {
>            "http://alto.example.com/costmap/num/routingcost_highres"
>          }
>        },
>
> One motivation for that syntax would be to better explain the differences
> between the several network maps. I don't have any strong preference,
> though.
>
>
Interesting idea.  I'm trying to think about what would be more natural
from an implementation standpoint.  If I were writing a client, I think I
would primarily be interested in the cost map, and then I would need to
figure out which Network Map is required to interpret that Cost Map.  From
that standpoint, it seems like listing the dependency along with the Cost
Map seems more natural.  I have a slight preference for the "refers-to"
approach but beyond what I just mentioned I don't have any strong technical
reasons.


> Another potential solution would be to define network map capabilities
> (such as "resolution" for scenario 2). Has this been discussed already?
> That approach alone might not solve scenario 1.
>
>
I don't think the notion of network map capabilities has been discussed
yet, but given that we need to finish up the protocol ASAP, perhaps that
could be an extension?


>
> Finally, after having re-read some parts of -16, I wonder if some sections
> implicitly assume that there is only a single network map (notable
> exception: Section 6.3). For instance:
>
> "10.1.1. Network Map
>
>    The Network Map Information Resource lists for each PID, the network
>    locations (endpoints) within the PID.  It MUST be provided by an ALTO
>    Server."
>
> "It" is a little bit unclear to me. More explicit would be something like
> "An ALTO server MUST provide at least one network map."
>

Yes - agreed. We'll adjust the text here.  Thanks for pointing this out.

Thanks!
Rich


>
> Best regards
>
> Michael
>
>
>
> > -----Original Message-----
> > From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On
> > Behalf Of Richard Alimi
> > Sent: Thursday, June 20, 2013 9:45 AM
> > To: alto@ietf.org
> > Subject: [alto] Clarifying Cost Map Dependencies on a Network Map
> >
> > [ We would like to hear feedback on this.  We are planning to
> > revise and submit a new version ASAP, so please voice
> > opinions on this within the next few days, by Monday, June 24th. ]
> >
> > Background:
> >
> > Today, the ALTO protocol as a 'version tag' to indicate which
> > version of a network map is used by a particular cost map.
> >
> > In a particularly simple case, a single ALTO server is served
> > by a single hostname (or IP address, whatever), and it
> > exposes a single network map and one or more cost maps.
> > There is no ambiguity here - a client automatically knows
> > that any version tag refers to the single network map that is
> > hosted by the server.
> >
> > There are two alternate scenarios where ambiguities arrive:
> >
> > (Scenario 1) An IRD hosted by alto.isp1.example.com refers
> > cost maps provided by some third-party, say
> > alto.third-party.example.com.  In this scenario, do version
> > tags exposed by alto.third-party.example.com correspond to
> > the network map provided by alto.isp1.example.com?
> >
> > (Scenario 2) A single ALTO server (single hostname) wishes to
> > provide two different network maps (say, different levels of
> > aggregation) and wants to provide cost maps for each of them.
> >  Currently, the version tag accompanying a cost map is not
> > sufficient for a client to determine which network map a
> > particular cost map is based on.
> >
> > Proposal:
> >
> > To resolve these problems, we'd like to propose a simple
> > change to the version tag accompanying the cost map - it
> > would now include the URI to the network map in addition to
> > an opaque ID.
> >
> > OLD (what we have now):
> >
> > {
> >  "meta" : {},
> >  "data" : {
> >    "cost-type" : {"cost-mode"  : "numerical",
> >                   "cost-metric": "routingcost"},
> >    "map-vtag"  : "1266506139",
> >    "map" : {
> >      "PID1": { "PID1": 1,  "PID2": 5,  "PID3": 10 },
> >      "PID2": { "PID1": 5,  "PID2": 1,  "PID3": 15 },
> >      "PID3": { "PID1": 20, "PID2": 15  }
> >    }
> >  }
> > }
> >
> > NEW PROPOSAL:
> >
> > {
> >  "meta" : {},
> >  "data" : {
> >    "cost-type" : {"cost-mode"  : "numerical",
> >                   "cost-metric": "routingcost"},
> >    "network-map" : {
> >      "uri": "http://alto.example.com/networkmap1"
> >      "vtag": "1266506139"
> >
> >
> >      }
> >    "map" : {
> >      "PID1": { "PID1": 1,  "PID2": 5,  "PID3": 10 },
> >      "PID2": { "PID1": 5,  "PID2": 1,  "PID3": 15 },
> >      "PID3": { "PID1": 20, "PID2": 15  }
> >    }
> >  }
> > }
> >
> > Compared to the current approach we have in draft -16 (which
> > is for a version tag to be consistent within resources served
> > by the same hostname), this has the following advantages:
> > - It provides a more flexible solution to Scenario 1
> > - It allows us to handle Scenario 2
> >
> > An possible addition to this approach would be explicitly
> > declare the dependency between the cost map and the network
> > map in the IRD.
> >
> > Feedback would be great.  The editors believe this would be a
> > strong improvement to the draft.
> >
> > Thanks,
> > Rich
> >
>

--047d7b6d8dacd7055404e06d8dcc
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
On Mon, Jun 24, 2013 at 12:19 PM, Scharf, Michael (Michael) <span dir=3D"lt=
r">&lt;<a href=3D"mailto:michael.scharf@alcatel-lucent.com" target=3D"_blan=
k">michael.scharf@alcatel-lucent.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">I agree that in particular scenario 2 is relevant and shou=
ld be addressed.<br>


<br>
Like Sabine, I wonder how a client would actually deal with two different n=
etwork maps if we don&#39;t provide any hint in the IRD (probably IRD entri=
es can be entirely optional if there is only one network map). Should the c=
lient query all candidate cost maps in that case?<br>

</blockquote><div><br></div><div style=3D"font-family:arial,sans-serif;font=
-size:13px">One possibility would be to first grab for the desired cost map=
, and then retrieve the network map it depends on. =A0There is a potential =
loss in efficiency since the client could fetch the network map and cost ma=
p in parallel.</div>

<div style=3D"font-family:arial,sans-serif;font-size:13px"><br></div><div><=
span style=3D"font-family:arial,sans-serif;font-size:13px">This seems to po=
int in favor of listing the dependency explicitly in the IRD, and I&#39;m o=
kay with that. =A0IIRC, Richard Yang was in favor of this as well.</span></=
div>

<div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br></span=
></div><div><span style=3D"font-family:arial,sans-serif;font-size:13px">All=
 that said, I was sitting down to write the text, and it turns out to be a =
bit tricky. =A0In particular, when one specifies the URI for the network ma=
p in the &quot;refers-to&quot; attribute, which URI is it? =A0Is it the exa=
ct same URI present in the Network Map&#39;s entry in the IRD, or is it som=
e canonical (absolute) URI for that Network Map resource? =A0If the former,=
 then those URIs may be relative and this doesn&#39;t handle Scenario 1 ver=
y well. =A0If the latter, then the ALTO Server generating the IRD has to kn=
ow the series of redirects that the client may experience (since the client=
 may get relative URIs for each Information Resource, and Section 5 of RFC3=
986 indicates that the result of the relative -&gt; absolute conversion may=
 be dependent on redirects that were followed). =A0These solutions get to b=
e kind of ugly.</span></div>

<div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br></span=
></div><div><span style=3D"font-family:arial,sans-serif;font-size:13px">Two=
 ideas come to mind for what we can do:</span></div><div><span style=3D"fon=
t-family:arial,sans-serif;font-size:13px">(1) Give each Information Resourc=
e a UUID, and refer to the dependencies by UUID instead of a URI.</span></d=
iv>

<div><span style=3D"font-family:arial,sans-serif;font-size:13px">(2) Consid=
er the addition of metadata to the IRD to declare dependencies to be an ext=
ension (but we must still change Version Tags to declare the URI for the Ne=
twork Map in the base protocol).</span></div>

<div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br></span=
></div><div><span style=3D"font-family:arial,sans-serif;font-size:13px">I d=
o think this is a nice-to-have optimization, but I don&#39;t think its stri=
ctly necessary to satisfy this use case. =A0I could be persuaded either way=
.</span></div>

<div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br></span=
></div><div><font face=3D"arial, sans-serif">[ The change to the Version Ta=
gs ends up being straightforward, since the server specifies all of them ex=
plicitly and can enforce that a single Network Map URI be returned; there i=
s no ambiguity introduced by relative URIs in that case. ]</font></div>

<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex"><br>
For what it is worth, at first sight, an alternative to the proposed &quot;=
refers-to&quot; solution on slide 8 of the interim meeting slide deck would=
 be an extended IRD entry for each network map:<br>
<br>
=A0 =A0 =A0 =A0{<br>
=A0 =A0 =A0 =A0 =A0&quot;uri&quot; : &quot;<a href=3D"http://alto.example.c=
om/networkmap1" target=3D"_blank">http://alto.example.com/networkmap1</a>&q=
uot;,<br>
=A0 =A0 =A0 =A0 =A0&quot;media-type&quot; : &quot;application/alto-networkm=
ap+json&quot;,<br>
=A0 =A0 =A0 =A0 =A0&quot;used-by&quot;: {<br>
=A0 =A0 =A0 =A0 =A0 =A0&quot;<a href=3D"http://alto.example.com/costmap/num=
/routingcost_lowres" target=3D"_blank">http://alto.example.com/costmap/num/=
routingcost_lowres</a>&quot;<br>
=A0 =A0 =A0 =A0 =A0}<br>
=A0 =A0 =A0 =A0},<br>
=A0 =A0 =A0 =A0{<br>
=A0 =A0 =A0 =A0 =A0&quot;uri&quot; : &quot;<a href=3D"http://alto.example.c=
om/networkmap2" target=3D"_blank">http://alto.example.com/networkmap2</a>&q=
uot;,<br>
=A0 =A0 =A0 =A0 =A0&quot;media-type&quot; : &quot;application/alto-networkm=
ap+json&quot;,<br>
=A0 =A0 =A0 =A0 =A0&quot;used-by&quot;: {<br>
=A0 =A0 =A0 =A0 =A0 =A0&quot;<a href=3D"http://alto.example.com/costmap/num=
/routingcost_highres" target=3D"_blank">http://alto.example.com/costmap/num=
/routingcost_highres</a>&quot;<br>
=A0 =A0 =A0 =A0 =A0}<br>
=A0 =A0 =A0 =A0},<br>
<br>
One motivation for that syntax would be to better explain the differences b=
etween the several network maps. I don&#39;t have any strong preference, th=
ough.<br>
<br></blockquote><div><br></div><div><span style=3D"font-family:arial,sans-=
serif;font-size:13px">Interesting idea. =A0I&#39;m trying to think about wh=
at would be more natural from an implementation standpoint. =A0If I were wr=
iting a client, I think I would primarily be interested in the cost map, an=
d then I would need to figure out which Network Map is required to interpre=
t that Cost Map. =A0From that standpoint, it seems like listing the depende=
ncy along with the Cost Map seems more natural. =A0I have a slight preferen=
ce for the &quot;refers-to&quot; approach but beyond what I just mentioned =
I don&#39;t have any strong technical reasons.</span><br>

</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);borde=
r-left-style:solid;padding-left:1ex">
Another potential solution would be to define network map capabilities (suc=
h as &quot;resolution&quot; for scenario 2). Has this been discussed alread=
y? That approach alone might not solve scenario 1.<br>
<br></blockquote><div>=A0</div><div><span style=3D"font-family:arial,sans-s=
erif;font-size:13px">I don&#39;t think the notion of network map capabiliti=
es has been discussed yet, but given that we need to finish up the protocol=
 ASAP, perhaps that could be an extension?</span></div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex">
<br>
Finally, after having re-read some parts of -16, I wonder if some sections =
implicitly assume that there is only a single network map (notable exceptio=
n: Section 6.3). For instance:<br>
<br>
&quot;10.1.1. Network Map<br>
<br>
=A0 =A0The Network Map Information Resource lists for each PID, the network=
<br>
=A0 =A0locations (endpoints) within the PID. =A0It MUST be provided by an A=
LTO<br>
=A0 =A0Server.&quot;<br>
<br>
&quot;It&quot; is a little bit unclear to me. More explicit would be someth=
ing like &quot;An ALTO server MUST provide at least one network map.&quot;<=
br></blockquote><div><br></div><div><span style=3D"font-family:arial,sans-s=
erif;font-size:13px">Yes - agreed. We&#39;ll adjust the text here. =A0Thank=
s for pointing this out.</span><br>

</div><div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br>=
</span></div><div><span style=3D"font-family:arial,sans-serif;font-size:13p=
x">Thanks!</span></div><div><span style=3D"font-family:arial,sans-serif;fon=
t-size:13px">Rich</span></div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex">
<br>
Best regards<br>
<span class=3D""><font color=3D"#888888"><br>
Michael<br>
</font></span><div class=3D""><div class=3D"h5"><br>
<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:alto-bounces@ietf.org">alto-bounces@ietf.org</=
a> [mailto:<a href=3D"mailto:alto-bounces@ietf.org">alto-bounces@ietf.org</=
a>] On<br>
&gt; Behalf Of Richard Alimi<br>
&gt; Sent: Thursday, June 20, 2013 9:45 AM<br>
&gt; To: <a href=3D"mailto:alto@ietf.org">alto@ietf.org</a><br>
&gt; Subject: [alto] Clarifying Cost Map Dependencies on a Network Map<br>
&gt;<br>
&gt; [ We would like to hear feedback on this. =A0We are planning to<br>
&gt; revise and submit a new version ASAP, so please voice<br>
&gt; opinions on this within the next few days, by Monday, June 24th. ]<br>
&gt;<br>
&gt; Background:<br>
&gt;<br>
&gt; Today, the ALTO protocol as a &#39;version tag&#39; to indicate which<=
br>
&gt; version of a network map is used by a particular cost map.<br>
&gt;<br>
&gt; In a particularly simple case, a single ALTO server is served<br>
&gt; by a single hostname (or IP address, whatever), and it<br>
&gt; exposes a single network map and one or more cost maps.<br>
&gt; There is no ambiguity here - a client automatically knows<br>
&gt; that any version tag refers to the single network map that is<br>
&gt; hosted by the server.<br>
&gt;<br>
&gt; There are two alternate scenarios where ambiguities arrive:<br>
&gt;<br>
&gt; (Scenario 1) An IRD hosted by <a href=3D"http://alto.isp1.example.com"=
 target=3D"_blank">alto.isp1.example.com</a> refers<br>
&gt; cost maps provided by some third-party, say<br>
&gt; <a href=3D"http://alto.third-party.example.com" target=3D"_blank">alto=
.third-party.example.com</a>. =A0In this scenario, do version<br>
&gt; tags exposed by <a href=3D"http://alto.third-party.example.com" target=
=3D"_blank">alto.third-party.example.com</a> correspond to<br>
&gt; the network map provided by <a href=3D"http://alto.isp1.example.com" t=
arget=3D"_blank">alto.isp1.example.com</a>?<br>
&gt;<br>
&gt; (Scenario 2) A single ALTO server (single hostname) wishes to<br>
&gt; provide two different network maps (say, different levels of<br>
&gt; aggregation) and wants to provide cost maps for each of them.<br>
&gt; =A0Currently, the version tag accompanying a cost map is not<br>
&gt; sufficient for a client to determine which network map a<br>
&gt; particular cost map is based on.<br>
&gt;<br>
&gt; Proposal:<br>
&gt;<br>
&gt; To resolve these problems, we&#39;d like to propose a simple<br>
&gt; change to the version tag accompanying the cost map - it<br>
&gt; would now include the URI to the network map in addition to<br>
&gt; an opaque ID.<br>
&gt;<br>
&gt; OLD (what we have now):<br>
&gt;<br>
&gt; {<br>
&gt; =A0&quot;meta&quot; : {},<br>
&gt; =A0&quot;data&quot; : {<br>
&gt; =A0 =A0&quot;cost-type&quot; : {&quot;cost-mode&quot; =A0: &quot;numer=
ical&quot;,<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 &quot;cost-metric&quot;: &quot;rou=
tingcost&quot;},<br>
&gt; =A0 =A0&quot;map-vtag&quot; =A0: &quot;1266506139&quot;,<br>
&gt; =A0 =A0&quot;map&quot; : {<br>
&gt; =A0 =A0 =A0&quot;PID1&quot;: { &quot;PID1&quot;: 1, =A0&quot;PID2&quot=
;: 5, =A0&quot;PID3&quot;: 10 },<br>
&gt; =A0 =A0 =A0&quot;PID2&quot;: { &quot;PID1&quot;: 5, =A0&quot;PID2&quot=
;: 1, =A0&quot;PID3&quot;: 15 },<br>
&gt; =A0 =A0 =A0&quot;PID3&quot;: { &quot;PID1&quot;: 20, &quot;PID2&quot;:=
 15 =A0}<br>
&gt; =A0 =A0}<br>
&gt; =A0}<br>
&gt; }<br>
&gt;<br>
&gt; NEW PROPOSAL:<br>
&gt;<br>
&gt; {<br>
&gt; =A0&quot;meta&quot; : {},<br>
&gt; =A0&quot;data&quot; : {<br>
&gt; =A0 =A0&quot;cost-type&quot; : {&quot;cost-mode&quot; =A0: &quot;numer=
ical&quot;,<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 &quot;cost-metric&quot;: &quot;rou=
tingcost&quot;},<br>
&gt; =A0 =A0&quot;network-map&quot; : {<br>
&gt; =A0 =A0 =A0&quot;uri&quot;: &quot;<a href=3D"http://alto.example.com/n=
etworkmap1" target=3D"_blank">http://alto.example.com/networkmap1</a>&quot;=
<br>
&gt; =A0 =A0 =A0&quot;vtag&quot;: &quot;1266506139&quot;<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0}<br>
&gt; =A0 =A0&quot;map&quot; : {<br>
&gt; =A0 =A0 =A0&quot;PID1&quot;: { &quot;PID1&quot;: 1, =A0&quot;PID2&quot=
;: 5, =A0&quot;PID3&quot;: 10 },<br>
&gt; =A0 =A0 =A0&quot;PID2&quot;: { &quot;PID1&quot;: 5, =A0&quot;PID2&quot=
;: 1, =A0&quot;PID3&quot;: 15 },<br>
&gt; =A0 =A0 =A0&quot;PID3&quot;: { &quot;PID1&quot;: 20, &quot;PID2&quot;:=
 15 =A0}<br>
&gt; =A0 =A0}<br>
&gt; =A0}<br>
&gt; }<br>
&gt;<br>
&gt; Compared to the current approach we have in draft -16 (which<br>
&gt; is for a version tag to be consistent within resources served<br>
&gt; by the same hostname), this has the following advantages:<br>
&gt; - It provides a more flexible solution to Scenario 1<br>
&gt; - It allows us to handle Scenario 2<br>
&gt;<br>
&gt; An possible addition to this approach would be explicitly<br>
&gt; declare the dependency between the cost map and the network<br>
&gt; map in the IRD.<br>
&gt;<br>
&gt; Feedback would be great. =A0The editors believe this would be a<br>
&gt; strong improvement to the draft.<br>
&gt;<br>
&gt; Thanks,<br>
&gt; Rich<br>
&gt; </div></div></blockquote></div><br></div></div>

--047d7b6d8dacd7055404e06d8dcc--
