IETF Logo Mail Archive

Re: [alto] Discussion II: Unifying cost-mode and cost-type to a single type

"Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com> Sat, 23 February 2013 20:43 UTC

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 047A521F8E69 for <alto@ietfa.amsl.com>; Sat, 23 Feb 2013 12:43:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.467
X-Spam-Level:
X-Spam-Status: No, score=-9.467 tagged_above=-999 required=5 tests=[AWL=0.782, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yew-e+g3xyWq for <alto@ietfa.amsl.com>; Sat, 23 Feb 2013 12:43:29 -0800 (PST)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id 3C26321F8E2C for <alto@ietf.org>; Sat, 23 Feb 2013 12:43:28 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r1NKhQOL026671 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sat, 23 Feb 2013 21:43:26 +0100
Received: from FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com ([135.120.45.56]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Sat, 23 Feb 2013 21:43:26 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: Sebastian Kiesel <ietf-alto@skiesel.de>, "Roome, W D" <w.roome@alcatel-lucent.com>
Date: Sat, 23 Feb 2013 21:43:23 +0100
Thread-Topic: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
Thread-Index: Ac4R4kDTVDRLGqG/TmeqZAwW3AnqZQAIeWXQ
Message-ID: <2A886F9088894347A3BE0CC5B7A85F3E9AA10D624B@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
References: <45A697A8FFD7CF48BCF2BE7E106F06040901008C@xmb-rcd-x04.cisco.com> <CD4D112F.36160%w.roome@alcatel-lucent.com> <20130223162358.GH9265@gw01.ehlo.wurstkaes.de>
In-Reply-To: <20130223162358.GH9265@gw01.ehlo.wurstkaes.de>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
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: Sat, 23 Feb 2013 20:43:30 -0000

> On the other hand, there are many other cost types (or 
> "rating criteria", as the ALTO requirements document RFC 6708 
> calls them), where an exact specification how to compute and 
> how to encode them makes sense, e.g.:
> 
> - draft-scharf-alto-vpn-service-00  talks about publishing the
>   geographical location of a data center using ALTO. How excatly
>   do we encode longitude/latitude?   This might fit into two lines
>   of text directly in the IANA registry.

For what it is worth (slightly off-topic in this thread): Approximate geographic location is already explicitly mentioned in the ALTO charter ("Initially the WG will consider: IP ranges to prefer and to avoid, ranked lists of the peers requested by the client, information about topological proximity and approximate geographic locations.").

IMHO, regarding geographical locations, draft-scharf-alto-vpn-service-00 just suggests something that the charter already mentions.

Michael

v2.23.0 | Report a Bug | By Email