< draft-ietf-alto-path-vector-24.txt   draft-ietf-alto-path-vector-25.txt >
ALTO K. Gao ALTO K. Gao
Internet-Draft Sichuan University Internet-Draft Sichuan University
Intended status: Experimental Y. Lee Intended status: Experimental Y. Lee
Expires: 8 September 2022 Samsung Expires: 21 September 2022 Samsung
S. Randriamasy S. Randriamasy
Nokia Bell Labs Nokia Bell Labs
Y.R. Yang Y.R. Yang
Yale University Yale University
J. Zhang J. Zhang
Tongji University Tongji University
7 March 2022 20 March 2022
An ALTO Extension: Path Vector An ALTO Extension: Path Vector
draft-ietf-alto-path-vector-24 draft-ietf-alto-path-vector-25
Abstract Abstract
This document is an extension to the base Application-Layer Traffic This document is an extension to the base Application-Layer Traffic
Optimization (ALTO) protocol. It extends the ALTO Cost Map and ALTO Optimization (ALTO) protocol. It extends the ALTO Cost Map and ALTO
Property Map services so that an application can decide which Property Map services so that an application can decide which
endpoint(s) to connect based on not only numerical/ordinal cost endpoint(s) to connect based on not only numerical/ordinal cost
values but also fine-grained abstract information of the paths. This values but also fine-grained abstract information of the paths. This
is useful for applications whose performance is impacted by specified is useful for applications whose performance is impacted by specified
components of a network on the end-to-end paths, e.g., they may infer components of a network on the end-to-end paths, e.g., they may infer
skipping to change at page 2, line 4 skipping to change at page 2, line 4
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 8 September 2022. This Internet-Draft will expire on 21 September 2022.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2022 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 3, line 5 skipping to change at page 3, line 5
6.2.2. Domain-Specific Entity Identifier . . . . . . . . . . 23 6.2.2. Domain-Specific Entity Identifier . . . . . . . . . . 23
6.2.3. Hierarchy and Inheritance . . . . . . . . . . . . . . 23 6.2.3. Hierarchy and Inheritance . . . . . . . . . . . . . . 23
6.2.4. Media Type of Defining Resource . . . . . . . . . . . 23 6.2.4. Media Type of Defining Resource . . . . . . . . . . . 23
6.3. ANE Property Name . . . . . . . . . . . . . . . . . . . . 24 6.3. ANE Property Name . . . . . . . . . . . . . . . . . . . . 24
6.4. Initial ANE Property Types . . . . . . . . . . . . . . . 24 6.4. Initial ANE Property Types . . . . . . . . . . . . . . . 24
6.4.1. Maximum Reservable Bandwidth . . . . . . . . . . . . 24 6.4.1. Maximum Reservable Bandwidth . . . . . . . . . . . . 24
6.4.2. Persistent Entity ID . . . . . . . . . . . . . . . . 25 6.4.2. Persistent Entity ID . . . . . . . . . . . . . . . . 25
6.4.3. Examples . . . . . . . . . . . . . . . . . . . . . . 25 6.4.3. Examples . . . . . . . . . . . . . . . . . . . . . . 25
6.5. Path Vector Cost Type . . . . . . . . . . . . . . . . . . 26 6.5. Path Vector Cost Type . . . . . . . . . . . . . . . . . . 26
6.5.1. Cost Metric: ane-path . . . . . . . . . . . . . . . . 26 6.5.1. Cost Metric: ane-path . . . . . . . . . . . . . . . . 26
6.5.2. Cost Mode: array . . . . . . . . . . . . . . . . . . 26 6.5.2. Cost Mode: array . . . . . . . . . . . . . . . . . . 27
6.6. Part Resource ID and Part Content ID . . . . . . . . . . 27 6.6. Part Resource ID and Part Content ID . . . . . . . . . . 27
7. Specification: Service Extensions . . . . . . . . . . . . . . 27 7. Specification: Service Extensions . . . . . . . . . . . . . . 27
7.1. Notations . . . . . . . . . . . . . . . . . . . . . . . . 27 7.1. Notations . . . . . . . . . . . . . . . . . . . . . . . . 27
7.2. Multipart Filtered Cost Map for Path Vector . . . . . . . 27 7.2. Multipart Filtered Cost Map for Path Vector . . . . . . . 28
7.2.1. Media Type . . . . . . . . . . . . . . . . . . . . . 27 7.2.1. Media Type . . . . . . . . . . . . . . . . . . . . . 28
7.2.2. HTTP Method . . . . . . . . . . . . . . . . . . . . . 28 7.2.2. HTTP Method . . . . . . . . . . . . . . . . . . . . . 28
7.2.3. Accept Input Parameters . . . . . . . . . . . . . . . 28 7.2.3. Accept Input Parameters . . . . . . . . . . . . . . . 28
7.2.4. Capabilities . . . . . . . . . . . . . . . . . . . . 29 7.2.4. Capabilities . . . . . . . . . . . . . . . . . . . . 29
7.2.5. Uses . . . . . . . . . . . . . . . . . . . . . . . . 30 7.2.5. Uses . . . . . . . . . . . . . . . . . . . . . . . . 30
7.2.6. Response . . . . . . . . . . . . . . . . . . . . . . 30 7.2.6. Response . . . . . . . . . . . . . . . . . . . . . . 30
7.3. Multipart Endpoint Cost Service for Path Vector . . . . . 34 7.3. Multipart Endpoint Cost Service for Path Vector . . . . . 34
7.3.1. Media Type . . . . . . . . . . . . . . . . . . . . . 34 7.3.1. Media Type . . . . . . . . . . . . . . . . . . . . . 34
7.3.2. HTTP Method . . . . . . . . . . . . . . . . . . . . . 34 7.3.2. HTTP Method . . . . . . . . . . . . . . . . . . . . . 34
7.3.3. Accept Input Parameters . . . . . . . . . . . . . . . 34 7.3.3. Accept Input Parameters . . . . . . . . . . . . . . . 34
7.3.4. Capabilities . . . . . . . . . . . . . . . . . . . . 35 7.3.4. Capabilities . . . . . . . . . . . . . . . . . . . . 35
skipping to change at page 26, line 50 skipping to change at page 27, line 9
mode (see Section 6.5.2) MUST return as the cost value a JSON array mode (see Section 6.5.2) MUST return as the cost value a JSON array
of ANEName and the client MUST also check that each element contained of ANEName and the client MUST also check that each element contained
in the array is an ANEName (Section 6.1). Otherwise, the client MUST in the array is an ANEName (Section 6.1). Otherwise, the client MUST
discard the response and SHOULD follow the instructions in discard the response and SHOULD follow the instructions in
Section 8.3.4.3 of [RFC7285] to handle the error. Section 8.3.4.3 of [RFC7285] to handle the error.
6.5.2. Cost Mode: array 6.5.2. Cost Mode: array
The cost mode "array" indicates that every cost value in the response The cost mode "array" indicates that every cost value in the response
body of a (Filtered) Cost Map or an Endpoint Cost Service MUST be body of a (Filtered) Cost Map or an Endpoint Cost Service MUST be
interpreted as a JSON array object. This cost mode can be applied to interpreted as a JSON array object. While this cost mode can be
all cost metrics. applied to all cost metrics, additional specifications will be needed
to clarify the semantics of the array cost mode when combined with
cost metrics other than 'ane-path'.
6.6. Part Resource ID and Part Content ID 6.6. Part Resource ID and Part Content ID
A Part Resource ID is encoded as a JSON string with the same format A Part Resource ID is encoded as a JSON string with the same format
as that of the type ResourceID (Section 10.2 of [RFC7285]). as that of the type ResourceID (Section 10.2 of [RFC7285]).
Even though the client-id assigned to a Path Vector request and the Even though the client-id assigned to a Path Vector request and the
Part Resource ID MAY contain up to 64 characters by their own Part Resource ID MAY contain up to 64 characters by their own
definition, their concatenation (see Section 5.3.2) MUST also conform definition, their concatenation (see Section 5.3.2) MUST also conform
to the same length constraint. The same requirement applies to the to the same length constraint. The same requirement applies to the
 End of changes. 7 change blocks. 
9 lines changed or deleted 11 lines changed or added

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