draft-ietf-alto-multi-cost-09.txt   draft-ietf-alto-multi-cost-10.txt 
Network Working Group S. Randriamasy Network Working Group S. Randriamasy
Internet-Draft W. Roome Internet-Draft W. Roome
Intended status: Standards Track Nokia Bell Labs Intended status: Standards Track Nokia Bell Labs
Expires: October 27, 2017 N. Schwan Expires: October 29, 2017 N. Schwan
Thales Deutschland Thales Deutschland
April 25, 2017 April 27, 2017
Multi-Cost ALTO Multi-Cost ALTO
draft-ietf-alto-multi-cost-09 draft-ietf-alto-multi-cost-10
Abstract Abstract
The ALTO (Application Layer-Traffic Optimization) Protocol The ALTO (Application Layer-Traffic Optimization) Protocol
([RFC7285]) defines several services that return various metrics ([RFC7285]) defines several services that return various metrics
describing the costs between network endpoints. describing the costs between network endpoints.
This document defines a new service that allows an ALTO Client to This document defines a new service that allows an ALTO Client to
retrieve several cost metrics in a single request for an ALTO retrieve several cost metrics in a single request for an ALTO
Filtered Cost Map and Endpoint Cost Map. In addition, it extends the Filtered Cost Map and Endpoint Cost Map. In addition, it extends the
constraints to further filter those maps by allowing a client to constraints to further filter those maps by allowing a client to
specify a logical combination of tests on several cost metrics. specify a logical combination of tests on several cost metrics.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 27, 2017. This Internet-Draft will expire on October 29, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Overview Of Approach . . . . . . . . . . . . . . . . . . . . 5 3. Overview Of Approach . . . . . . . . . . . . . . . . . . . . 5
3.1. Multi-Cost Data Format . . . . . . . . . . . . . . . . . 5 3.1. Multi-Cost Data Format . . . . . . . . . . . . . . . . . 5
3.2. Compatibility With Legacy ALTO Clients . . . . . . . . . 5 3.2. Compatibility With Legacy ALTO Clients . . . . . . . . . 5
3.3. Filtered Multi Cost Map Resources . . . . . . . . . . . . 6 3.3. Filtered Multi Cost Map Resources . . . . . . . . . . . . 6
3.4. Endpoint Cost Service Resources . . . . . . . . . . . . . 6 3.4. Endpoint Cost Service Resources . . . . . . . . . . . . . 6
3.5. Full Cost Map Resources . . . . . . . . . . . . . . . . . 7 3.5. Full Cost Map Resources . . . . . . . . . . . . . . . . . 7
3.6. Extended Constraint Tests . . . . . . . . . . . . . . . . 7 3.6. Extended Constraint Tests . . . . . . . . . . . . . . . . 7
3.6.1. Extended constraint predicates . . . . . . . . . . . 7 3.6.1. Extended constraint predicates . . . . . . . . . . . 7
3.6.2. Extended logical combination of predicates . . . . . 7 3.6.2. Extended logical combination of predicates . . . . . 7
skipping to change at page 4, line 29 skipping to change at page 4, line 22
requests such as: "select solutions with either (moderate "hopcount" requests such as: "select solutions with either (moderate "hopcount"
AND high "routingcost") OR (higher "hopcount" AND moderate AND high "routingcost") OR (higher "hopcount" AND moderate
"routingcost")". "routingcost")".
This document is organized as follows: Section 2 defines terminology This document is organized as follows: Section 2 defines terminology
used in this document. Section 3 gives a non-normative overview of used in this document. Section 3 gives a non-normative overview of
the multi-cost extensions, and Section 4 gives their formal the multi-cost extensions, and Section 4 gives their formal
definitions. Section 5 gives several complete examples. The definitions. Section 5 gives several complete examples. The
remaining sections describe the IANA and privacy considerations. remaining sections describe the IANA and privacy considerations.
1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
When the words appear in lower case, their natural language meaning
is used.
2. Terminology 2. Terminology
o ALTO transaction: A request/response exchange between an ALTO o ALTO transaction: A request/response exchange between an ALTO
Client and an ALTO Server. Client and an ALTO Server.
o Client: This term refers to an ALTO client, when used with a o Client: This term refers to an ALTO client, when used with a
capital "C". capital "C".
o Endpoint (EP): An endpoint is defined as in {2.1} of [RFC7285]. o Endpoint (EP): An endpoint is defined as in {2.1} of [RFC7285].
It can be for example a peer, a CDN storage location, a physical It can be for example a peer, a CDN storage location, a physical
 End of changes. 7 change blocks. 
10 lines changed or deleted 14 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/