
From internet-drafts@ietf.org  Mon Jan 16 07:31:08 2012
Return-Path: <internet-drafts@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 F351D21F8516; Mon, 16 Jan 2012 07:31:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.445
X-Spam-Level: 
X-Spam-Status: No, score=-102.445 tagged_above=-999 required=5 tests=[AWL=-0.073, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, 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 QJMeKRz1suel; Mon, 16 Jan 2012 07:31:07 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5674321F8427; Mon, 16 Jan 2012 07:31:03 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20120116153103.11942.21957.idtracker@ietfa.amsl.com>
Date: Mon, 16 Jan 2012 07:31:03 -0800
Cc: alto@ietf.org
Subject: [alto] I-D Action: draft-ietf-alto-reqs-13.txt
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, 16 Jan 2012 15:31:08 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Application-Layer Traffic Optimizatio=
n Working Group of the IETF.

	Title           : Application-Layer Traffic Optimization (ALTO) Requiremen=
ts
	Author(s)       : Sebastian Kiesel
                          Stefano Previdi
                          Martin Stiemerling
                          Richard Woundy
                          Yang Richard Yang
	Filename        : draft-ietf-alto-reqs-13.txt
	Pages           : 22
	Date            : 2012-01-16

   Many Internet applications are used to access resources, such as
   pieces of information or server processes, which are available in
   several equivalent replicas on different hosts.  This includes, but
   is not limited to, peer-to-peer file sharing applications.  The goal
   of Application-Layer Traffic Optimization (ALTO) is to provide
   guidance to applications, which have to select one or several hosts
   from a set of candidates capable of providing a desired resource.
   This guidance shall be based on parameters that affect performance
   and efficiency of the data transmission between the hosts, e.g., the
   topological distance.  The ultimate goal is to improve performance
   (or Quality of Experience) in the application while reducing resource
   consumption in the underlying network infrastructure.

   This document enumerates requirements for specifying, assessing, or
   comparing protocols and implementations.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-alto-reqs-13.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-alto-reqs-13.txt


From sebi@gw01.ehlo.wurstkaes.de  Mon Jan 16 07:45:06 2012
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 07BAE21F8687 for <alto@ietfa.amsl.com>; Mon, 16 Jan 2012 07:45:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.022
X-Spam-Level: 
X-Spam-Status: No, score=-2.022 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, SARE_SUB_OBFU_Q1=0.227]
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 4poiofoCaGzk for <alto@ietfa.amsl.com>; Mon, 16 Jan 2012 07:45:05 -0800 (PST)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [188.246.4.151]) by ietfa.amsl.com (Postfix) with ESMTP id 16AF521F8684 for <alto@ietf.org>; Mon, 16 Jan 2012 07:45:04 -0800 (PST)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.72) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1Rmok1-0005gY-GV for alto@ietf.org; Mon, 16 Jan 2012 16:45:01 +0100
Date: Mon, 16 Jan 2012 16:45:01 +0100
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: alto@ietf.org
Message-ID: <20120116154501.GA13277@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] [internet-drafts@ietf.org: I-D Action: draft-ietf-alto-reqs-13.txt]
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, 16 Jan 2012 15:45:06 -0000

Dear ALTO WG folks,

this new version of the ALTO requirements draft addresses one concern we
heard several times during last call, which is about the two query modes
("sorting oracle" vs. "map") and how to ensure interoperability between
implementations.  We consider this a clarification which does not change
what has been WG consensus several years ago.


OLD (draft-ietf-alto-reqs-12.txt and before):
>
>  REQ.  ARv12-21: An ALTO client protocol MUST support at least one
>  query mode, either the target-aware or the target-independent query
>  mode.
>
>  REQ.  ARv12-22: An ALTO client protocol SHOULD support both the
>  target-aware and the target-independent query mode.

NEW (draft-ietf-alto-reqs-13.txt):
>
>  REQ.  ARv13-21: An ALTO client protocol specification MUST specify at
>  least one query mode, either the target-aware or the target-
>  independent query mode.
>
>  REQ.  ARv13-22: An ALTO client protocol specification SHOULD specify
>  both the target-aware and the target-independent query mode.  If an
>  ALTO client protocol specification specifies more than one query
>  mode, it MUST define at least one of these modes as REQUIRED to
>  implement by ALTO Clients and ALTO Servers.  Furthermore, it MUST
>  specify an appropriate protocol mechanism for negotiating between
>  ALTO Client and ALTO Server, which query mode to use.


Thanks,
Sebastian


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

Date: Mon, 16 Jan 2012 07:31:03 -0800
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: alto@ietf.org
Subject: [alto] I-D Action: draft-ietf-alto-reqs-13.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization Working Group of the IETF.

	Title           : Application-Layer Traffic Optimization (ALTO) Requirements
	Author(s)       : Sebastian Kiesel
                          Stefano Previdi
                          Martin Stiemerling
                          Richard Woundy
                          Yang Richard Yang
	Filename        : draft-ietf-alto-reqs-13.txt
	Pages           : 22
	Date            : 2012-01-16

   Many Internet applications are used to access resources, such as
   pieces of information or server processes, which are available in
   several equivalent replicas on different hosts.  This includes, but
   is not limited to, peer-to-peer file sharing applications.  The goal
   of Application-Layer Traffic Optimization (ALTO) is to provide
   guidance to applications, which have to select one or several hosts
   from a set of candidates capable of providing a desired resource.
   This guidance shall be based on parameters that affect performance
   and efficiency of the data transmission between the hosts, e.g., the
   topological distance.  The ultimate goal is to improve performance
   (or Quality of Experience) in the application while reducing resource
   consumption in the underlying network infrastructure.

   This document enumerates requirements for specifying, assessing, or
   comparing protocols and implementations.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-alto-reqs-13.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-alto-reqs-13.txt

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

----- End forwarded message -----

From enrico.marocco@telecomitalia.it  Mon Jan 30 07:53:38 2012
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 DC71721F8633 for <alto@ietfa.amsl.com>; Mon, 30 Jan 2012 07:53:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.311
X-Spam-Level: 
X-Spam-Status: No, score=-100.311 tagged_above=-999 required=5 tests=[AWL=0.408, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245,  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 mn1KKsGIN2qB for <alto@ietfa.amsl.com>; Mon, 30 Jan 2012 07:53:38 -0800 (PST)
Received: from GRFEDG701BA020.telecomitalia.it (grfedg701ba020.telecomitalia.it [156.54.233.200]) by ietfa.amsl.com (Postfix) with ESMTP id D619121F85F6 for <alto@ietf.org>; Mon, 30 Jan 2012 07:53:37 -0800 (PST)
Received: from GRFHUB701BA020.griffon.local (10.188.101.111) by GRFEDG701BA020.telecomitalia.it (10.188.45.100) with Microsoft SMTP Server (TLS) id 8.2.254.0; Mon, 30 Jan 2012 16:53:30 +0100
Received: from MacLab.local (163.162.180.246) by smtp.telecomitalia.it (10.188.101.114) with Microsoft SMTP Server (TLS) id 8.2.254.0; Mon, 30 Jan 2012 16:53:29 +0100
Message-ID: <4F26BD49.8000009@telecomitalia.it>
Date: Mon, 30 Jan 2012 16:54:49 +0100
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: "alto@ietf.org" <alto@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms090008040303050405060105"
Subject: [alto] ALTO extensions: new list + problem statement
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, 30 Jan 2012 15:53:39 -0000

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

Hi folks,

the new altoext@ietf.org mailing list has just been created to discuss
possible extensions to the about-to-be-finished ALTO protocol.

We have also recently submitted a draft trying to summarize the
previous discussions on the subject:
http://tools.ietf.org/html/draft-marocco-alto-next

In a nutshell: the possible extensions, primarily intended to better
address the CDN/datacenter and server-to-server use cases, mainly
concern:
  + a server-to-client notification mechanism;
  + additional types of information, such as:
    o network link load (average, over some recent timeframe);
    o server load (average, over some recent timeframe);
    o availability of resources such as memory, content, installed
      applications.

The new mailing list has been created in order to get broader feedback
and to get together people with experience in different areas. If you
have an opinion on whether and why the proposed (and possibly further)
extensions will be a good or a bad idea, you can join the discussion
at: https://www.ietf.org/mailman/listinfo/altoext

--=20
Ciao,
Enrico


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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINfjCC
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
5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIHQjCCBiqgAwIBAgIDAt9AMA0GCSqGSIb3DQEB
BQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTEwODIyMDYyNDA2
WhcNMTIwODIyMDM0MDM3WjB8MSAwHgYDVQQNExc0OTAyNDItOU1QZVJYRnFlVVU0QUMybTEo
MCYGA1UEAwwfZW5yaWNvLm1hcm9jY29AdGVsZWNvbWl0YWxpYS5pdDEuMCwGCSqGSIb3DQEJ
ARYfZW5yaWNvLm1hcm9jY29AdGVsZWNvbWl0YWxpYS5pdDCCASIwDQYJKoZIhvcNAQEBBQAD
ggEPADCCAQoCggEBALl4L3Uj7TJrMbll5JAyphws2AMR67q3D2FH0JmRqQ5r+ujqaxyeHcrx
Kclu2tz/D3SPtZAlcDOclxpEDbpxXlMpo+3DsbNweNgSF6mnyRDYU2ay3qO54ENz21GZ64bl
ZRsMI6KsGnxm7sORWLUdx229ijARs3aQD1js9bidUJsnxg26UvnwpJ8eGoFiCLzzsQXUD+OL
3TXEGrTzt+B2RDb13TIOe085T8jzBh08wNKPTDmKjxy5m35Xn8QfRy8b93d0wUs98Fst5iND
EgHEHc9CwurwLYrOd/1ZkbfAoRi7kRQ0Ih4wKkP+Lkww/0qHEIrrgW+aVmGjkQ0nidAaE+sC
AwEAAaOCA7owggO2MAkGA1UdEwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUF
BwMCBggrBgEFBQcDBDAdBgNVHQ4EFgQUYgEiK9qxBHth8ziqydxV7QYZn1QwHwYDVR0jBBgw
FoAUU3Ltkpzg2ssBXHx+ljVO8tS4UYIwKgYDVR0RBCMwIYEfZW5yaWNvLm1hcm9jY29AdGVs
ZWNvbWl0YWxpYS5pdDCCAiEGA1UdIASCAhgwggIUMIICEAYLKwYBBAGBtTcBAgIwggH/MC4G
CCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMDQGCCsGAQUF
BwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUucGRmMIH3BggrBgEF
BQcCAjCB6jAnFiBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTADAgEBGoG+VGhp
cyBjZXJ0aWZpY2F0ZSB3YXMgaXNzdWVkIGFjY29yZGluZyB0byB0aGUgQ2xhc3MgMSBWYWxp
ZGF0aW9uIHJlcXVpcmVtZW50cyBvZiB0aGUgU3RhcnRDb20gQ0EgcG9saWN5LCByZWxpYW5j
ZSBvbmx5IGZvciB0aGUgaW50ZW5kZWQgcHVycG9zZSBpbiBjb21wbGlhbmNlIG9mIHRoZSBy
ZWx5aW5nIHBhcnR5IG9ibGlnYXRpb25zLjCBnAYIKwYBBQUHAgIwgY8wJxYgU3RhcnRDb20g
Q2VydGlmaWNhdGlvbiBBdXRob3JpdHkwAwIBAhpkTGlhYmlsaXR5IGFuZCB3YXJyYW50aWVz
IGFyZSBsaW1pdGVkISBTZWUgc2VjdGlvbiAiTGVnYWwgYW5kIExpbWl0YXRpb25zIiBvZiB0
aGUgU3RhcnRDb20gQ0EgcG9saWN5LjA2BgNVHR8ELzAtMCugKaAnhiVodHRwOi8vY3JsLnN0
YXJ0c3NsLmNvbS9jcnR1MS1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzAB
hi1odHRwOi8vb2NzcC5zdGFydHNzbC5jb20vc3ViL2NsYXNzMS9jbGllbnQvY2EwQgYIKwYB
BQUHMAKGNmh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczEuY2xpZW50
LmNhLmNydDAjBgNVHRIEHDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcN
AQEFBQADggEBAF4gnxCzZVmINcZh7ZMB6G1+8/kV6pLqDxyUidalFSJ8KLwJxrxhESOb+E7d
JHxZBuJFH1NBXuVn+MI7rqa/HI7PkLJjkHhMH8ay7jhR2VVMIFYAqRn9O22oDDw2iEigYkgo
HcHP1vD5rtydbGr6mCcHOtWCk5B7FqEoMYTQRO1F6szoqORVaajVtZeSwtVAMufV20tohyUL
hpOH5lZDblsej2XueyJVqD8RYSUJp7w4eMpr5CTP9QdNBS0cca83JA070JMudV+ozG6ADIBx
mGPrWyPv7PmjBBGIXxPJJRxDsDyJBYhs+qh6fZWNl6WZkQNepkn7IAUB0+0ggds992kxggPQ
MIIDzAIBATCBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzAp
BgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0
YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMC30AwCQYF
Kw4DAhoFAKCCAhAwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTIwMTMwMTU1NDQ5WjAjBgkqhkiG9w0BCQQxFgQU6YaakzpgwiK5IF91nB4365/0IWEwXwYJ
KoZIhvcNAQkPMVIwUDALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCA
MA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGlBgkrBgEEAYI3EAQx
gZcwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQL
EyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENv
bSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDAt9AMIGnBgsqhkiG
9w0BCRACCzGBl6CBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMC30Aw
DQYJKoZIhvcNAQEBBQAEggEAII8VsxlzeLbgE0Eha30jvHywDZUbYgLkKlJHPgr+6SkGbekU
ROxWafXZ3u/CiMba/x0Uwel0KoKl2neGXI3Y/bTlDYjV8fMAfJi7u0jvVcTtS11QzFvy6eAN
ibysHPMaio2iaFNGMk4jarJzsp+1s997T3BTLM8KKYY+Z0pNum5zMhklIKevWSWaGCPdyVpC
XpefbsWwIY7YMOJazFoZHb5rnSyao0GrLU7Ieu9SPIoRtmMq5y/hO7BwkXXNX90Cfipit6GS
pc0GFGjDQ3o3wou2yG56RFtu1huhc8Pj3cVJaVZEUUUjK4EecxCeEI6qdcor2XmPIP1IPgso
fa1HPgAAAAAAAA==
--------------ms090008040303050405060105--

From ben@niven-jenkins.co.uk  Mon Jan 30 09:03:08 2012
Return-Path: <ben@niven-jenkins.co.uk>
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 D0DC521F85E5 for <alto@ietfa.amsl.com>; Mon, 30 Jan 2012 09:03:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.953
X-Spam-Level: 
X-Spam-Status: No, score=-101.953 tagged_above=-999 required=5 tests=[AWL=-0.813, BAYES_20=-0.74, J_CHICKENPOX_44=0.6, 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 16rBu1jCj1pK for <alto@ietfa.amsl.com>; Mon, 30 Jan 2012 09:03:08 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.62]) by ietfa.amsl.com (Postfix) with ESMTP id 312D421F85E4 for <alto@ietf.org>; Mon, 30 Jan 2012 09:03:08 -0800 (PST)
Received: from host1.cachelogic.com ([212.44.43.80] helo=dhcp-125-devlan.cachelogic.com) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1RrudG-0002ye-BC for alto@ietf.org; Mon, 30 Jan 2012 17:03:06 +0000
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 30 Jan 2012 17:03:05 +0000
Message-Id: <A35E0DC7-C133-480C-9967-EC62CAE9BCA0@niven-jenkins.co.uk>
To: alto@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Subject: [alto] Are ALTO costs always End to End?
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, 30 Jan 2012 17:03:08 -0000

Colleagues,

In the current specification of ALTO, are costs always End to End?

What I mean by that is when looking at ALTO cost maps is it possible to =
safely assume that of there is a cost between PIDX & PID Y and a cost =
between PIDY & PIDZ then the cost between PIDX & PIDZ can be calculated =
as cost(PIDX,PIDY)+cost(PIDY,PIDZ)? [If this assumption does hold, it is =
obviously not applicable to ordinal cost types].

I suspect the answer is no, but I wanted to check what the definitive =
answer is.


For example if a cost map contains:

   "map" : {
     "PID1": { "PID2": 1 },
     "PID2": { "PID1": 1, "PID3": 2 },
     "PID3": { "PID2": 2 }

Can one assume that the cost between PID1 & PID3 is 3 (PID1->PID2 + =
PID2->PID3)?

How about if the cost map contains:

   "map" : {
     "PID1": { "PID2": 1, "PID3": 3 },
     "PID2": { "PID1": 1, "PID3": 2 },
     "PID3": { "PID2": 2, "PID1": 3 }

Can one assume PID2 is on a path between PID1 & PID3?

Thanks
Ben


From vkg@bell-labs.com  Mon Jan 30 15:02:15 2012
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 2D53421F8473 for <alto@ietfa.amsl.com>; Mon, 30 Jan 2012 15:02:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.48
X-Spam-Level: 
X-Spam-Status: No, score=-106.48 tagged_above=-999 required=5 tests=[AWL=-0.481, BAYES_00=-2.599, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_MED=-4, 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 LjWMLtuQBuON for <alto@ietfa.amsl.com>; Mon, 30 Jan 2012 15:02:14 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 4F83D21F8444 for <alto@ietf.org>; Mon, 30 Jan 2012 15:02:14 -0800 (PST)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id q0UN28AC010412 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 30 Jan 2012 17:02:09 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q0UN27u3017602 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 30 Jan 2012 17:02:08 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q0UN27wZ008545; Mon, 30 Jan 2012 17:02:07 -0600 (CST)
Message-ID: <4F272268.4070804@bell-labs.com>
Date: Mon, 30 Jan 2012 17:06:16 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111222 Thunderbird/9.0
MIME-Version: 1.0
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
References: <A35E0DC7-C133-480C-9967-EC62CAE9BCA0@niven-jenkins.co.uk>
In-Reply-To: <A35E0DC7-C133-480C-9967-EC62CAE9BCA0@niven-jenkins.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Cc: alto <alto@ietf.org>
Subject: Re: [alto] Are ALTO costs always End to End?
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, 30 Jan 2012 23:02:15 -0000

As individual.

Ben: Please see inline.

On 01/30/2012 11:03 AM, Ben Niven-Jenkins wrote:
> Colleagues,
>
> In the current specification of ALTO, are costs always End to End?
>
> What I mean by that is when looking at ALTO cost maps is it possible
> to safely assume that of there is a cost between PIDX& PID Y and a cost
> between PIDY& PIDZ then the cost between PIDX& PIDZ can be calculated as
> cost(PIDX,PIDY)+cost(PIDY,PIDZ)? [If this assumption does hold, it is
> obviously not applicable to ordinal cost types].
>
> I suspect the answer is no, but I wanted to check what the
> definitiveanswer is.

It will be interesting to hear from the authors, but here is my
two cents.

If I take the cost map and create a graph from it, and if the graph is
connected and I simply run Dijkstra's shortest path algorithm on it,
then I suspect the answer is yes.

More below.

> For example if a cost map contains:
>
>     "map" : {
>       "PID1": { "PID2": 1 },
>       "PID2": { "PID1": 1, "PID3": 2 },
>       "PID3": { "PID2": 2 }

If one were to construct a graph from the above cost map --- omitting
edges emanating and terminating at the same vertex and assuming
bi-directional links --- one would get:

           PID-2
            /\
          1/  \2
          /    \
       PID-1  PID-3

> Can one assume that the cost between PID1& PID3 is 3 (PID1->PID2 +
> PID2->PID3)?

Clearly, PID-3 is reachable from PID-1 via PID-2 at a cost of 3.

Now, for the second example I get a graph of the form:

> How about if the cost map contains:
>
>     "map" : {
>       "PID1": { "PID2": 1, "PID3": 3 },
>       "PID2": { "PID1": 1, "PID3": 2 },
>       "PID3": { "PID2": 2, "PID1": 3 }

           PID-2
            /\
          1/  \2
          /    \
     PID-1------PID-3
             3

> Can one assume PID2 is on a path between PID1&  PID3?

PID-2 may be on a path, but it may not be the *shortest* path.
Although in the above example, it really does not matter since the cost
to reach PID-3 from PID-1 is 3 regardless of whether we go through
PID-2 or directly from PID-1 to PID-3.  Now, if the shortest path
computation algorithm was optimizing other metrics besides cost of the
edges (say, the hop count), then the best path from PID-1 to PID-3 would
be the direct path.

Thanks,

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

From ben@niven-jenkins.co.uk  Mon Jan 30 15:51:28 2012
Return-Path: <ben@niven-jenkins.co.uk>
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 2FE0211E80F4 for <alto@ietfa.amsl.com>; Mon, 30 Jan 2012 15:51:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.049
X-Spam-Level: 
X-Spam-Status: No, score=-103.049 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, J_CHICKENPOX_44=0.6, 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 Uqq2zzXvBht9 for <alto@ietfa.amsl.com>; Mon, 30 Jan 2012 15:51:27 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.62]) by ietfa.amsl.com (Postfix) with ESMTP id 6A1A511E80EA for <alto@ietf.org>; Mon, 30 Jan 2012 15:51:21 -0800 (PST)
Received: from cpc10-cmbg15-2-0-cust121.5-4.cable.virginmedia.com ([86.30.246.122] helo=[192.168.0.3]) by mail5.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1Rs10K-0002jA-62; Mon, 30 Jan 2012 23:51:20 +0000
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <4F272268.4070804@bell-labs.com>
Date: Mon, 30 Jan 2012 23:51:16 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <6A051A1C-3C3E-43C7-888C-AB1E98CB2A86@niven-jenkins.co.uk>
References: <A35E0DC7-C133-480C-9967-EC62CAE9BCA0@niven-jenkins.co.uk> <4F272268.4070804@bell-labs.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
X-Mailer: Apple Mail (2.1084)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: alto <alto@ietf.org>
Subject: Re: [alto] Are ALTO costs always End to End?
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, 30 Jan 2012 23:51:28 -0000

Vijay,

On 30 Jan 2012, at 23:06, Vijay K. Gurbani wrote:

> As individual.
>=20
> Ben: Please see inline.
>=20
> On 01/30/2012 11:03 AM, Ben Niven-Jenkins wrote:
>> Colleagues,
>>=20
>> In the current specification of ALTO, are costs always End to End?
>>=20
>> What I mean by that is when looking at ALTO cost maps is it possible
>> to safely assume that of there is a cost between PIDX& PID Y and a =
cost
>> between PIDY& PIDZ then the cost between PIDX& PIDZ can be calculated =
as
>> cost(PIDX,PIDY)+cost(PIDY,PIDZ)? [If this assumption does hold, it is
>> obviously not applicable to ordinal cost types].
>>=20
>> I suspect the answer is no, but I wanted to check what the
>> definitiveanswer is.
>=20
> It will be interesting to hear from the authors, but here is my
> two cents.
>=20
> If I take the cost map and create a graph from it, and if the graph is
> connected and I simply run Dijkstra's shortest path algorithm on it,
> then I suspect the answer is yes.

I guess my question is really whether an ALTO cost map is a graph or a =
mesh? I always assumed it was a mesh but then I got wondering...

> More below.
>=20
>> For example if a cost map contains:
>>=20
>>    "map" : {
>>      "PID1": { "PID2": 1 },
>>      "PID2": { "PID1": 1, "PID3": 2 },
>>      "PID3": { "PID2": 2 }
>=20
> If one were to construct a graph from the above cost map --- omitting
> edges emanating and terminating at the same vertex and assuming
> bi-directional links --- one would get:
>=20
>          PID-2
>           /\
>         1/  \2
>         /    \
>      PID-1  PID-3

>=20
>> Can one assume that the cost between PID1& PID3 is 3 (PID1->PID2 +
>> PID2->PID3)?
>=20
> Clearly, PID-3 is reachable from PID-1 via PID-2 at a cost of 3.

I started considering that case but then wondered how to tell the =
difference between PID3 being reachable from PID1 via PID2 and PID2, for =
example, being a dual homed host/site that isn't capable/configured of =
routing between its WAN interfaces?

This might be a case where we'd need a PID property to distinguish =
"transit" PIDs from "End Host" PIDs.

Ben


>=20
> Now, for the second example I get a graph of the form:
>=20
>> How about if the cost map contains:
>>=20
>>    "map" : {
>>      "PID1": { "PID2": 1, "PID3": 3 },
>>      "PID2": { "PID1": 1, "PID3": 2 },
>>      "PID3": { "PID2": 2, "PID1": 3 }
>=20
>          PID-2
>           /\
>         1/  \2
>         /    \
>    PID-1------PID-3
>            3
>=20
>> Can one assume PID2 is on a path between PID1&  PID3?
>=20
> PID-2 may be on a path, but it may not be the *shortest* path.
> Although in the above example, it really does not matter since the =
cost
> to reach PID-3 from PID-1 is 3 regardless of whether we go through
> PID-2 or directly from PID-1 to PID-3.  Now, if the shortest path
> computation algorithm was optimizing other metrics besides cost of the
> edges (say, the hop count), then the best path from PID-1 to PID-3 =
would
> be the direct path.
>=20
> Thanks,
>=20
> - vijay
> --=20
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
> Web:   http://ect.bell-labs.com/who/vkg/


From jmedved@cisco.com  Mon Jan 30 22:22:33 2012
Return-Path: <jmedved@cisco.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 6E93521F84C8 for <alto@ietfa.amsl.com>; Mon, 30 Jan 2012 22:22:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_MED=-4]
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 08CSmwUf2dDZ for <alto@ietfa.amsl.com>; Mon, 30 Jan 2012 22:22:31 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id B5FF221F8495 for <alto@ietf.org>; Mon, 30 Jan 2012 22:22:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmedved@cisco.com; l=4103; q=dns/txt; s=iport; t=1327990951; x=1329200551; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=s7VkiIJd9C3VAeNTvwy5C5ZETXeuEOdTkXLt7bWdzA0=; b=Dbd8L0dnihsO9gps2BXVc3ue+pgZ1VVEfr6LkNsgPK40mO3yMNQSm+h+ LQjz/egnW5q4EgE4PjU0LsN6rdjGo9LmrX3EgMgSmZRSu+6f69V7LMXb3 ZeAeqaqhNb4GR9TDrpYdyHE+4fBlvssLCo4B6NmsP7SXNts1gNKg+jBOT 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArkHAL+HJ0+rRDoH/2dsb2JhbABDgw2rVoEFgXIBAQEDAQEBAQ8BFBM0CwULCxguJzAGEyKHWgmaNwGeUosBBwICCQUMBhMBCAUDAwmDHAUYAgsCBWMVG4JaYwSIQIxehVeNHA
X-IronPort-AV: E=Sophos;i="4.71,594,1320624000"; d="scan'208";a="27909705"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 31 Jan 2012 06:22:31 +0000
Received: from [10.21.74.158] ([10.21.74.158]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q0V6MVJ9008931; Tue, 31 Jan 2012 06:22:31 GMT
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Jan Medved <jmedved@cisco.com>
In-Reply-To: <6A051A1C-3C3E-43C7-888C-AB1E98CB2A86@niven-jenkins.co.uk>
Date: Mon, 30 Jan 2012 22:22:30 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <DB00A268-EA37-411B-AFB0-AFB6776046B7@cisco.com>
References: <A35E0DC7-C133-480C-9967-EC62CAE9BCA0@niven-jenkins.co.uk> <4F272268.4070804@bell-labs.com> <6A051A1C-3C3E-43C7-888C-AB1E98CB2A86@niven-jenkins.co.uk>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
X-Mailer: Apple Mail (2.1251.1)
Cc: alto <alto@ietf.org>
Subject: Re: [alto] Are ALTO costs always End to End?
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, 31 Jan 2012 06:22:33 -0000

On Jan 30, 2012, at 3:51 PM, Ben Niven-Jenkins wrote:

> Vijay,
>=20
> On 30 Jan 2012, at 23:06, Vijay K. Gurbani wrote:
>=20
>> As individual.
>>=20
>> Ben: Please see inline.
>>=20
>> On 01/30/2012 11:03 AM, Ben Niven-Jenkins wrote:
>>> Colleagues,
>>>=20
>>> In the current specification of ALTO, are costs always End to End?
>>>=20
>>> What I mean by that is when looking at ALTO cost maps is it possible
>>> to safely assume that of there is a cost between PIDX& PID Y and a =
cost
>>> between PIDY& PIDZ then the cost between PIDX& PIDZ can be =
calculated as
>>> cost(PIDX,PIDY)+cost(PIDY,PIDZ)? [If this assumption does hold, it =
is
>>> obviously not applicable to ordinal cost types].
>>>=20
>>> I suspect the answer is no, but I wanted to check what the
>>> definitiveanswer is.
>>=20
>> It will be interesting to hear from the authors, but here is my
>> two cents.
>>=20
>> If I take the cost map and create a graph from it, and if the graph =
is
>> connected and I simply run Dijkstra's shortest path algorithm on it,
>> then I suspect the answer is yes.
>=20
> I guess my question is really whether an ALTO cost map is a graph or a =
mesh? I always assumed it was a mesh but then I got wondering...
>=20
>> More below.
>>=20
>>> For example if a cost map contains:
>>>=20
>>>   "map" : {
>>>     "PID1": { "PID2": 1 },
>>>     "PID2": { "PID1": 1, "PID3": 2 },
>>>     "PID3": { "PID2": 2 }
>>=20
>> If one were to construct a graph from the above cost map --- omitting
>> edges emanating and terminating at the same vertex and assuming
>> bi-directional links --- one would get:
>>=20
>>         PID-2
>>          /\
>>        1/  \2
>>        /    \
>>     PID-1  PID-3
>=20
>>=20
>>> Can one assume that the cost between PID1& PID3 is 3 (PID1->PID2 +
>>> PID2->PID3)?
>>=20
>> Clearly, PID-3 is reachable from PID-1 via PID-2 at a cost of 3.
>=20
> I started considering that case but then wondered how to tell the =
difference between PID3 being reachable from PID1 via PID2 and PID2, for =
example, being a dual homed host/site that isn't capable/configured of =
routing between its WAN interfaces?
>=20

It's not clear what you mean. Can you perhaps draw a diagram that would =
explain the topology you have in mind?

> This might be a case where we'd need a PID property to distinguish =
"transit" PIDs from "End Host" PIDs.
>=20

A "transit" PID does not make sense. As Vijay explained below, you can =
not infer any topology from ALTO costs. If you need topology, it's best =
to get it directly from IGP/BGP routing protocols, or to use something =
like BGP-LS which helps to avoid peering with IGP speakers.


> Ben
>=20

/Jan

>=20
>>=20
>> Now, for the second example I get a graph of the form:
>>=20
>>> How about if the cost map contains:
>>>=20
>>>   "map" : {
>>>     "PID1": { "PID2": 1, "PID3": 3 },
>>>     "PID2": { "PID1": 1, "PID3": 2 },
>>>     "PID3": { "PID2": 2, "PID1": 3 }
>>=20
>>         PID-2
>>          /\
>>        1/  \2
>>        /    \
>>   PID-1------PID-3
>>           3
>>=20
>>> Can one assume PID2 is on a path between PID1&  PID3?
>>=20
>> PID-2 may be on a path, but it may not be the *shortest* path.
>> Although in the above example, it really does not matter since the =
cost
>> to reach PID-3 from PID-1 is 3 regardless of whether we go through
>> PID-2 or directly from PID-1 to PID-3.  Now, if the shortest path
>> computation algorithm was optimizing other metrics besides cost of =
the
>> edges (say, the hop count), then the best path from PID-1 to PID-3 =
would
>> be the direct path.
>>=20
>> Thanks,
>>=20
>> - vijay
>> --=20
>> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
>> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
>> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
>> Web:   http://ect.bell-labs.com/who/vkg/
>=20
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto


From sprevidi@cisco.com  Tue Jan 31 03:14:53 2012
Return-Path: <sprevidi@cisco.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 6E6C821F864E for <alto@ietfa.amsl.com>; Tue, 31 Jan 2012 03:14:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_44=0.6, 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 YyYeBG9d98Kb for <alto@ietfa.amsl.com>; Tue, 31 Jan 2012 03:14:52 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 7726321F862B for <alto@ietf.org>; Tue, 31 Jan 2012 03:14:52 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from stew-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q0VBEoXR024641 for <alto@ietf.org>; Tue, 31 Jan 2012 12:14:50 +0100 (CET)
Received: from dhcp-10-55-90-53.cisco.com (dhcp-10-55-90-53.cisco.com [10.55.90.53]) by stew-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q0VBEmvN018618; Tue, 31 Jan 2012 12:14:49 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: stefano previdi <sprevidi@cisco.com>
In-Reply-To: <6A051A1C-3C3E-43C7-888C-AB1E98CB2A86@niven-jenkins.co.uk>
Date: Tue, 31 Jan 2012 12:14:48 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <489EF99B-832D-4B52-B8ED-5F1612F8BFE2@cisco.com>
References: <A35E0DC7-C133-480C-9967-EC62CAE9BCA0@niven-jenkins.co.uk> <4F272268.4070804@bell-labs.com> <6A051A1C-3C3E-43C7-888C-AB1E98CB2A86@niven-jenkins.co.uk>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
X-Mailer: Apple Mail (2.1251.1)
Cc: alto <alto@ietf.org>
Subject: Re: [alto] Are ALTO costs always End to End?
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, 31 Jan 2012 11:14:53 -0000

Ben, Vijay,

On Jan 31, 2012, at 12:51 AM, Ben Niven-Jenkins wrote:
> Vijay,
>=20
> On 30 Jan 2012, at 23:06, Vijay K. Gurbani wrote:
>=20
>> As individual.
>>=20
>> Ben: Please see inline.
>>=20
>> On 01/30/2012 11:03 AM, Ben Niven-Jenkins wrote:
>>> Colleagues,
>>>=20
>>> In the current specification of ALTO, are costs always End to End?
>>>=20
>>> What I mean by that is when looking at ALTO cost maps is it possible
>>> to safely assume that of there is a cost between PIDX& PID Y and a =
cost
>>> between PIDY& PIDZ then the cost between PIDX& PIDZ can be =
calculated as
>>> cost(PIDX,PIDY)+cost(PIDY,PIDZ)? [If this assumption does hold, it =
is
>>> obviously not applicable to ordinal cost types].
>>>=20
>>> I suspect the answer is no, but I wanted to check what the
>>> definitiveanswer is.
>>=20
>> It will be interesting to hear from the authors, but here is my
>> two cents.
>>=20
>> If I take the cost map and create a graph from it, and if the graph =
is
>> connected and I simply run Dijkstra's shortest path algorithm on it,
>> then I suspect the answer is yes.
>=20
> I guess my question is really whether an ALTO cost map is a graph or a =
mesh? I always assumed it was a mesh but then I got wondering...


Well, you raised a pretty valid (and tricky) point here. I don't think=20=

we ever put much attention on the topology representation an alto map=20
could/should/must have. It could be a graph, it could be an instance of=20=

a pre-calculated shortest path (i.e.: you won't see all paths but only=20=

the shortest one).

Note that the construction of the alto maps doesn't have to follow any=20=

specific rules as it is out of scope. IOW: you get what  alto server=20
decides to give you.



>> More below.
>>=20
>>> For example if a cost map contains:
>>>=20
>>>   "map" : {
>>>     "PID1": { "PID2": 1 },
>>>     "PID2": { "PID1": 1, "PID3": 2 },
>>>     "PID3": { "PID2": 2 }
>>=20
>> If one were to construct a graph from the above cost map --- omitting
>> edges emanating and terminating at the same vertex and assuming
>> bi-directional links --- one would get:
>>=20
>>         PID-2
>>          /\
>>        1/  \2
>>        /    \
>>     PID-1  PID-3
>=20
>>=20
>>> Can one assume that the cost between PID1& PID3 is 3 (PID1->PID2 +
>>> PID2->PID3)?
>>=20
>> Clearly, PID-3 is reachable from PID-1 via PID-2 at a cost of 3.


keep in mind that asymmetric routing is very common so you better=20
compute your paths according to the direction the traffic is going=20
to take.

In your example it doesn't make much different but in case you have a=20
more meshed topology, it really DOES make the difference.=20

You MUST have all mechanisms in order to match what your routers/network
will do at the end of the day (i.e.: packets are forwarded according to=20=

your ospf/isis shortest path and BGP selection, not your alto magic).


> I started considering that case but then wondered how to tell the =
difference between PID3 being reachable from PID1 via PID2 and PID2, for =
example, being a dual homed host/site that isn't capable/configured of =
routing between its WAN interfaces?

Good point.

I suppose that by default all PIDs will have similar capabilities. IOW:=20=

in the picture Vijay drawn I expect all :IDs having "routing/transit"=20
capabilities.

SPF-Dijsktra computation will give you the exact picture of your =
topology.=20
And if you apply some extensions (like reverse-spf, multi-root-spf, etc=20=

etc) you can sort out most cases.


> This might be a case where we'd need a PID property to distinguish =
"transit" PIDs from "End Host" PIDs.


sounds pretty reasonable to me.

s.

>=20
> Ben
>=20
>=20
>>=20
>> Now, for the second example I get a graph of the form:
>>=20
>>> How about if the cost map contains:
>>>=20
>>>   "map" : {
>>>     "PID1": { "PID2": 1, "PID3": 3 },
>>>     "PID2": { "PID1": 1, "PID3": 2 },
>>>     "PID3": { "PID2": 2, "PID1": 3 }
>>=20
>>         PID-2
>>          /\
>>        1/  \2
>>        /    \
>>   PID-1------PID-3
>>           3
>>=20
>>> Can one assume PID2 is on a path between PID1&  PID3?
>>=20
>> PID-2 may be on a path, but it may not be the *shortest* path.
>> Although in the above example, it really does not matter since the =
cost
>> to reach PID-3 from PID-1 is 3 regardless of whether we go through
>> PID-2 or directly from PID-1 to PID-3.  Now, if the shortest path
>> computation algorithm was optimizing other metrics besides cost of =
the
>> edges (say, the hop count), then the best path from PID-1 to PID-3 =
would
>> be the direct path.
>>=20
>> Thanks,
>>=20
>> - vijay
>> --=20
>> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
>> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
>> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
>> Web:   http://ect.bell-labs.com/who/vkg/
>=20
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>=20


From vkg@bell-labs.com  Tue Jan 31 07:04:16 2012
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 4C1C621F85DA for <alto@ietfa.amsl.com>; Tue, 31 Jan 2012 07:04:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.766
X-Spam-Level: 
X-Spam-Status: No, score=-106.766 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 VXkMuP19j96z for <alto@ietfa.amsl.com>; Tue, 31 Jan 2012 07:04:15 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 93DC721F8566 for <alto@ietf.org>; Tue, 31 Jan 2012 07:04:15 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id q0VF4D0V015187 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 31 Jan 2012 09:04:14 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q0VF4Dla031226 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 31 Jan 2012 09:04:13 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q0VF4CnK009450; Tue, 31 Jan 2012 09:04:13 -0600 (CST)
Message-ID: <4F2803E7.1090000@bell-labs.com>
Date: Tue, 31 Jan 2012 09:08:23 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111222 Thunderbird/9.0
MIME-Version: 1.0
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
References: <A35E0DC7-C133-480C-9967-EC62CAE9BCA0@niven-jenkins.co.uk> <4F272268.4070804@bell-labs.com> <6A051A1C-3C3E-43C7-888C-AB1E98CB2A86@niven-jenkins.co.uk> <489EF99B-832D-4B52-B8ED-5F1612F8BFE2@cisco.com>
In-Reply-To: <489EF99B-832D-4B52-B8ED-5F1612F8BFE2@cisco.com>
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.9
Cc: alto <alto@ietf.org>
Subject: Re: [alto] Are ALTO costs always End to End?
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, 31 Jan 2012 15:04:16 -0000

On 01/31/2012 05:14 AM, stefano previdi wrote:
ben> This might be a case where we'd need a PID property to distinguish
ben> "transit" PIDs from "End Host" PIDs.
ben>
stefano> sounds pretty reasonable to me.

Ben: I suspect that your question had a foundation of some sort
and was not simply a fishing expedition ;-)

Let me ask you this: is the PID property that you would like to put
in useful for CDN-usage in ALTO?  If so, and since others
(Stefano) appear to agree, then it is worth a larger discussion on
the need of such a property to support emerging usages of ALTO.

Thanks,

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

From sprevidi@cisco.com  Tue Jan 31 07:29:47 2012
Return-Path: <sprevidi@cisco.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 1844421F8606 for <alto@ietfa.amsl.com>; Tue, 31 Jan 2012 07:29:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, 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 j-U4UvuTlt6t for <alto@ietfa.amsl.com>; Tue, 31 Jan 2012 07:29:46 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 1391821F862A for <alto@ietf.org>; Tue, 31 Jan 2012 07:29:45 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from stew-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q0VFTicS025807 for <alto@ietf.org>; Tue, 31 Jan 2012 16:29:44 +0100 (CET)
Received: from dhcp-10-55-90-53.cisco.com (dhcp-10-55-90-53.cisco.com [10.55.90.53]) by stew-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q0VFThoQ012589; Tue, 31 Jan 2012 16:29:43 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=iso-8859-1
From: stefano previdi <sprevidi@cisco.com>
In-Reply-To: <4F2803E7.1090000@bell-labs.com>
Date: Tue, 31 Jan 2012 16:29:43 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <E37CB818-879F-4087-BBD2-C9A9A13F2846@cisco.com>
References: <A35E0DC7-C133-480C-9967-EC62CAE9BCA0@niven-jenkins.co.uk> <4F272268.4070804@bell-labs.com> <6A051A1C-3C3E-43C7-888C-AB1E98CB2A86@niven-jenkins.co.uk> <489EF99B-832D-4B52-B8ED-5F1612F8BFE2@cisco.com> <4F2803E7.1090000@bell-labs.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: alto <alto@ietf.org>
Subject: Re: [alto] Are ALTO costs always End to End?
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, 31 Jan 2012 15:29:47 -0000

On Jan 31, 2012, at 4:08 PM, Vijay K. Gurbani wrote:

> On 01/31/2012 05:14 AM, stefano previdi wrote:
> ben> This might be a case where we'd need a PID property to distinguish
> ben> "transit" PIDs from "End Host" PIDs.
> ben>
> stefano> sounds pretty reasonable to me.
> 
> Ben: I suspect that your question had a foundation of some sort
> and was not simply a fishing expedition ;-)
> 
> Let me ask you this: is the PID property that you would like to put
> in useful for CDN-usage in ALTO?


there are a variety of cases where this would be useful. When 
you distribute a link-state topology you know you're talking 
about routers and links and semantic is well-known. Same when 
you advertise BGP routes or VPNv4 routes or whatever... the 
protocol has the semantic you need to consider.

In ALTO you have the necessary bits to tell if cost is based on 
routing or air miles or others but you don't really know what a 
PID is (other than a bunch of addresses).


>  If so, and since others
> (Stefano) appear to agree, then it is worth a larger discussion on
> the need of such a property to support emerging usages of ALTO.


yes, I _tend_ to agree... until we find disagreement of course ;-)

s.


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


From vkg@bell-labs.com  Tue Jan 31 11:17:45 2012
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 0746E11E8087 for <alto@ietfa.amsl.com>; Tue, 31 Jan 2012 11:17:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.756
X-Spam-Level: 
X-Spam-Status: No, score=-106.756 tagged_above=-999 required=5 tests=[AWL=-0.157, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 asDI1EBsXbrZ for <alto@ietfa.amsl.com>; Tue, 31 Jan 2012 11:17:43 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 3C1C211E8072 for <alto@ietf.org>; Tue, 31 Jan 2012 11:17:43 -0800 (PST)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id q0VJHfFO003718 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 31 Jan 2012 13:17:41 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q0VJHfYO005989 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 31 Jan 2012 13:17:41 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q0VJHenO013096; Tue, 31 Jan 2012 13:17:40 -0600 (CST)
Message-ID: <4F283F4F.6070305@bell-labs.com>
Date: Tue, 31 Jan 2012 13:21:51 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111222 Thunderbird/9.0
MIME-Version: 1.0
To: stefano previdi <sprevidi@cisco.com>
References: <A35E0DC7-C133-480C-9967-EC62CAE9BCA0@niven-jenkins.co.uk> <4F272268.4070804@bell-labs.com> <6A051A1C-3C3E-43C7-888C-AB1E98CB2A86@niven-jenkins.co.uk> <489EF99B-832D-4B52-B8ED-5F1612F8BFE2@cisco.com> <4F2803E7.1090000@bell-labs.com> <E37CB818-879F-4087-BBD2-C9A9A13F2846@cisco.com>
In-Reply-To: <E37CB818-879F-4087-BBD2-C9A9A13F2846@cisco.com>
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.10
Cc: alto <alto@ietf.org>
Subject: Re: [alto] Are ALTO costs always End to End?
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, 31 Jan 2012 19:17:45 -0000

On 01/31/2012 09:29 AM, stefano previdi wrote:
> there are a variety of cases where this would be useful. When you
> distribute a link-state topology you know you're talking about
> routers and links and semantic is well-known. Same when you advertise
> BGP routes or VPNv4 routes or whatever... the protocol has the
> semantic you need to consider.

Stefano: True.

> In ALTO you have the necessary bits to tell if cost is based on
> routing or air miles or others but you don't really know what a PID
> is (other than a bunch of addresses).

That was a strategic design decision, as far as I can recall.
A PID abstracted a collection of some hosts, the collection
being defined by the entity populating such a collection in
a network map and cost map for the consumption of the ALTO
server.

Now, there is nothing that stops us from having a singleton
host --- a router --- be in its own PID and then show that
PID as being reachable from other PIDs.  This affects the
case that Ben may be thinking about ... Ben?

> yes, I _tend_ to agree... until we find disagreement of course ;-)

Of course.  To be sure, I am not disagreeing with you; just
trying to add to the discussion.

Ciao,

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