Application-Layer Traffic Optimization (ALTO) Protocol
- Created
- 2014-03-18
- Last Updated
- 2014-09-08
- Available Formats
-
XML
HTML
Plain text
Registries included below
ALTO Cost Metric Registry
- Registration Procedure(s)
-
IETF Review
- Reference
- [RFC7285]
- Available Formats
-
CSV
| Identifier |
Intended Semantics |
Reference |
| routingcost |
See Section 6.1.1.1 of [RFC7285] |
[RFC7285] |
| priv: |
Private use |
[RFC7285] |
ALTO Endpoint Property Type Registry
- Registration Procedure(s)
-
IETF Review
- Reference
- [RFC7285]
- Available Formats
-
CSV
| Identifier |
Intended Semantics |
Reference |
| pid |
See Section 7.1.1 of [RFC7285] |
[RFC7285] |
| priv: |
Private use |
[RFC7285] |
ALTO Address Type Registry
- Registration Procedure(s)
-
IETF Review
- Reference
- [RFC7285]
- Available Formats
-
CSV
| Identifier |
Address Encoding |
Prefix Encoding |
Mapping to/from IPv4/v6 |
Reference |
| ipv4 |
See Section 10.4.3 of [RFC7285] |
See Section 10.4.3 of [RFC7285] |
Direct mapping to IPv4 |
[RFC7285] |
| ipv6 |
See Section 10.4.3 of [RFC7285] |
See Section 10.4.3 of [RFC7285] |
Direct mapping to IPv6 |
[RFC7285] |
ALTO Error Code Registry
- Registration Procedure(s)
-
IETF Review
- Reference
- [RFC7285]
- Available Formats
-
CSV
| Error Code |
Intended Usage |
Reference |
| E_SYNTAX |
Parsing error in request (including identifiers). See
Section 8.5.2 of [RFC7285] |
[RFC7285] |
| E_MISSING_FIELD |
A required JSON field is missing. See
Section 8.5.2 of [RFC7285] |
[RFC7285] |
| E_INVALID_FIELD_TYPE |
The type of the value of a JSON field is invalid. See
Section 8.5.2 of [RFC7285] |
[RFC7285] |
| E_INVALID_FIELD_VALUE |
The value of a JSON field is invalid. See
Section 8.5.2 of [RFC7285] |
[RFC7285] |
