Multiple ALTO Resources Query Using Multipart Message
draft-zhang-alto-multipart-05
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Authors |
|
J. Zhang
,
Y. Yang
|
|
Last updated |
|
2021-01-14
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
html
xml
pdf
htmlized (tools)
htmlized
bibtex
|
Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
ALTO WG J. Zhang
Internet-Draft Tongji University
Intended status: Standards Track Y.R. Yang
Expires: 18 July 2021 Yale University
14 January 2021
Multiple ALTO Resources Query Using Multipart Message
draft-zhang-alto-multipart-05
Abstract
Many ALTO use cases involve multiple ALTO information resources like
different network maps, cost maps and property maps to achieve their
own specific goals. To make the ALTO client query them one by one is
not only inefficient but also error-prone. The inconsistent
responses can be performed because of the unstable communication
environment, and finally conduct the unexpected traffic optimization.
Further more, some ALTO information resources may have correlation,
which means one's input parameters may depends on another one's
response. To address those issues, some advanced query schema is
required. This document proposes an ALTO extension to support the
multiple ALTO resources query in the single request using the HTTP
multipart message and the existing JSON query languages.
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 [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 https://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 18 July 2021.
Zhang & Yang Expires 18 July 2021 [Page 1]
Internet-Draft Multipart January 2021
Copyright Notice
Copyright (c) 2021 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 (https://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. Terminologies . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Resource Query Entry . . . . . . . . . . . . . . . . . . 4
2.2. Resource Response Entry . . . . . . . . . . . . . . . . . 4
2.3. Resource Response Entry Body . . . . . . . . . . . . . . 4
3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Simple Batch Query . . . . . . . . . . . . . . . . . . . 4
3.2. Properties Constrained Query . . . . . . . . . . . . . . 5
3.3. Path Vector Query . . . . . . . . . . . . . . . . . . . . 5
4. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Design Space of Multipart Resource in ALTO . . . . . . . . . 6
6. Multipart Query Resource . . . . . . . . . . . . . . . . . . 7
6.1. Media Type . . . . . . . . . . . . . . . . . . . . . . . 7
6.2. HTTP Method . . . . . . . . . . . . . . . . . . . . . . . 7
6.3. Capabilities . . . . . . . . . . . . . . . . . . . . . . 7
6.4. Accept Input Parameters . . . . . . . . . . . . . . . . . 7
6.5. Uses . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.6. Response . . . . . . . . . . . . . . . . . . . . . . . . 8
7. Protocol Errors . . . . . . . . . . . . . . . . . . . . . . . 8
7.1. Partial Error . . . . . . . . . . . . . . . . . . . . . . 9
7.2. Entire Error . . . . . . . . . . . . . . . . . . . . . . 10
8. Incremental Update Integration . . . . . . . . . . . . . . . 10
9. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 10
9.1. IRD Example . . . . . . . . . . . . . . . . . . . . . . . 10
9.2. Example 1: Simple Batch Query . . . . . . . . . . . . . . 12
9.3. Example 2: Properties Constrained Query . . . . . . . . . 14
Show full document text