Multi-Cost ALTO
draft-ietf-alto-multi-cost-09
The information below is for an old version of the document | |||
---|---|---|---|
Document | Type | Active Internet-Draft (alto WG) | |
Last updated | 2017-04-25 | ||
Replaces | draft-randriamasy-alto-multi-cost | ||
Stream | IETF | ||
Intended RFC status | Proposed Standard | ||
Formats | pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Jan Seedorf | ||
Shepherd write-up | Show (last changed 2017-02-23) | ||
IESG | IESG state | IESG Evaluation::AD Followup | |
Consensus Boilerplate | Yes | ||
Telechat date |
Needs 3 more YES or NO OBJECTION positions to pass. |
||
Responsible AD | Mirja Kühlewind | ||
Send notices to | "Jan Seedorf" <ietf@j-f-s.de> | ||
IANA | IANA review state | Version Changed - Review Needed |
Network Working Group S. Randriamasy Internet-Draft W. Roome Intended status: Standards Track Nokia Bell Labs Expires: October 27, 2017 N. Schwan Thales Deutschland April 25, 2017 Multi-Cost ALTO draft-ietf-alto-multi-cost-09 Abstract The ALTO (Application Layer-Traffic Optimization) Protocol ([RFC7285]) defines several services that return various metrics describing the costs between network endpoints. This document defines a new service that allows an ALTO Client to retrieve several cost metrics in a single request for an ALTO Filtered Cost Map and Endpoint Cost Map. In addition, it extends the constraints to further filter those maps by allowing a client to 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 This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on October 27, 2017. Randriamasy, et al. Expires October 27, 2017 [Page 1] Internet-Draft Multi-Cost ALTO April 2017 Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Overview Of Approach . . . . . . . . . . . . . . . . . . . . 5 3.1. Multi-Cost Data Format . . . . . . . . . . . . . . . . . 5 3.2. Compatibility With Legacy ALTO Clients . . . . . . . . . 5 3.3. Filtered Multi Cost Map Resources . . . . . . . . . . . . 6 3.4. Endpoint Cost Service Resources . . . . . . . . . . . . . 6 3.5. Full Cost Map Resources . . . . . . . . . . . . . . . . . 7 3.6. Extended Constraint Tests . . . . . . . . . . . . . . . . 7 3.6.1. Extended constraint predicates . . . . . . . . . . . 7 3.6.2. Extended logical combination of predicates . . . . . 7 3.6.3. Testable Cost Types in constraints . . . . . . . . . 8 3.6.4. Testable Cost Type Names in IRD capabilities . . . . 9 3.6.5. Legacy ALTO Client issues . . . . . . . . . . . . . . 9 4. Protocol Extensions for Multi-Cost ALTO Transactions . . . . 11 4.1. Filtered Cost Map Extensions . . . . . . . . . . . . . . 11 4.1.1. Capabilities . . . . . . . . . . . . . . . . . . . . 11 4.1.2. Accept Input Parameters . . . . . . . . . . . . . . . 12 4.1.3. Response . . . . . . . . . . . . . . . . . . . . . . 15 4.2. Endpoint Cost Service Extensions . . . . . . . . . . . . 15 4.2.1. Capabilities . . . . . . . . . . . . . . . . . . . . 16 4.2.2. Accept Input Parameters . . . . . . . . . . . . . . . 16 4.2.3. Response . . . . . . . . . . . . . . . . . . . . . . 17 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.1. Information Resource Directory . . . . . . . . . . . . . 17 5.2. Multi-Cost Filtered Cost Map: Example #1 . . . . . . . . 19 5.3. Multi-Cost Filtered Cost Map: Example #2 . . . . . . . . 20 5.4. Multi-Cost Filtered Cost Map: Example #3 . . . . . . . . 22 5.5. Multi-Cost Filtered Cost Map: Example #4 . . . . . . . . 23Show full document text