| < draft-ietf-cdni-metadata-20.txt | draft-ietf-cdni-metadata-21.txt > | |||
|---|---|---|---|---|
| Network Working Group B. Niven-Jenkins | Network Working Group B. Niven-Jenkins | |||
| Internet-Draft R. Murray | Internet-Draft R. Murray | |||
| Intended status: Standards Track Velocix (Alcatel-Lucent) | Intended status: Standards Track Velocix (Alcatel-Lucent) | |||
| Expires: February 3, 2017 M. Caulfield | Expires: March 1, 2017 M. Caulfield | |||
| Cisco Systems | Cisco Systems | |||
| K. Ma | K. Ma | |||
| Ericsson | Ericsson | |||
| August 2, 2016 | August 28, 2016 | |||
| CDN Interconnection Metadata | CDN Interconnection Metadata | |||
| draft-ietf-cdni-metadata-20 | draft-ietf-cdni-metadata-21 | |||
| Abstract | Abstract | |||
| The Content Delivery Networks Interconnection (CDNI) metadata | The Content Delivery Networks Interconnection (CDNI) metadata | |||
| interface enables interconnected Content Delivery Networks (CDNs) to | interface enables interconnected Content Delivery Networks (CDNs) to | |||
| exchange content distribution metadata in order to enable content | exchange content distribution metadata in order to enable content | |||
| acquisition and delivery. The CDNI metadata associated with a piece | acquisition and delivery. The CDNI metadata associated with a piece | |||
| of content provides a downstream CDN with sufficient information for | of content provides a downstream CDN with sufficient information for | |||
| the downstream CDN to service content requests on behalf of an | the downstream CDN to service content requests on behalf of an | |||
| upstream CDN. This document describes both a base set of CDNI | upstream CDN. This document describes both a base set of CDNI | |||
| skipping to change at page 1, line 47 ¶ | skipping to change at page 1, line 47 ¶ | |||
| 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 February 3, 2017. | This Internet-Draft will expire on March 1, 2017. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2016 IETF Trust and the persons identified as the | Copyright (c) 2016 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 | |||
| skipping to change at page 16, line 20 ¶ | skipping to change at page 16, line 20 ¶ | |||
| match the Hostname or IP address in the host property the value | match the Hostname or IP address in the host property the value | |||
| from the content request when converted to lowercase MUST be | from the content request when converted to lowercase MUST be | |||
| identical to the value of the host property when converted to | identical to the value of the host property when converted to | |||
| lowercase. All implementations MUST support IPv4 addresses | lowercase. All implementations MUST support IPv4 addresses | |||
| encoded as specified by the 'IPv4address' rule in Section 3.2.2 | encoded as specified by the 'IPv4address' rule in Section 3.2.2 | |||
| of [RFC3986]. IPv6 addresses MUST be encoded in one of the | of [RFC3986]. IPv6 addresses MUST be encoded in one of the | |||
| IPv6 address formats specified in [RFC5952] although receivers | IPv6 address formats specified in [RFC5952] although receivers | |||
| MUST support all IPv6 address formats specified in [RFC4291]. | MUST support all IPv6 address formats specified in [RFC4291]. | |||
| Hostnames MUST conform to the Domain Name System (DNS) syntax | Hostnames MUST conform to the Domain Name System (DNS) syntax | |||
| defined in [RFC1034] and [RFC1123]. Internationalized Domain | defined in [RFC1034] and [RFC1123]. Internationalized Domain | |||
| Names (IDN) must first be transformed to the IDNA encoding as | Names (IDN) must first be transformed to the the A-label form | |||
| per [RFC5891]. | [RFC5890] as per [RFC5891]. | |||
| Type: Endpoint | Type: Endpoint | |||
| Mandatory-to-Specify: Yes. | Mandatory-to-Specify: Yes. | |||
| Property: host-metadata | Property: host-metadata | |||
| Description: CDNI metadata to apply when delivering content | Description: CDNI metadata to apply when delivering content | |||
| that matches this host. | that matches this host. | |||
| skipping to change at page 39, line 51 ¶ | skipping to change at page 39, line 51 ¶ | |||
| A Hostname (with optional port) or an IP address (with optional | A Hostname (with optional port) or an IP address (with optional | |||
| port). | port). | |||
| All implementations MUST support IPv4 addresses encoded as specified | All implementations MUST support IPv4 addresses encoded as specified | |||
| by the 'IPv4address' rule in Section 3.2.2 of [RFC3986]. IPv6 | by the 'IPv4address' rule in Section 3.2.2 of [RFC3986]. IPv6 | |||
| addresses MUST be encoded in one of the IPv6 address formats | addresses MUST be encoded in one of the IPv6 address formats | |||
| specified in [RFC5952] although receivers MUST support all IPv6 | specified in [RFC5952] although receivers MUST support all IPv6 | |||
| address formats specified in [RFC4291]. Hostnames MUST conform to | address formats specified in [RFC4291]. Hostnames MUST conform to | |||
| the Domain Name System (DNS) syntax defined in [RFC1034] and | the Domain Name System (DNS) syntax defined in [RFC1034] and | |||
| [RFC1123]. Internationalized Domain Names (IDN) must first be | [RFC1123]. Internationalized Domain Names (IDN) must first be | |||
| transformed to the IDNA encoding as per [RFC5891]. | transformed to the A-label form [RFC5890] as per [RFC5891]. | |||
| Type: String | Type: String | |||
| Example Hostname: | Example Hostname: | |||
| "metadata.ucdn.example" | "metadata.ucdn.example" | |||
| Example IPv4 address: | Example IPv4 address: | |||
| "192.0.2.1" | "192.0.2.1" | |||
| skipping to change at page 62, line 19 ¶ | skipping to change at page 62, line 19 ¶ | |||
| [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing | [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing | |||
| Architecture", RFC 4291, DOI 10.17487/RFC4291, February | Architecture", RFC 4291, DOI 10.17487/RFC4291, February | |||
| 2006, <http://www.rfc-editor.org/info/rfc4291>. | 2006, <http://www.rfc-editor.org/info/rfc4291>. | |||
| [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an | [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an | |||
| IANA Considerations Section in RFCs", BCP 26, RFC 5226, | IANA Considerations Section in RFCs", BCP 26, RFC 5226, | |||
| DOI 10.17487/RFC5226, May 2008, | DOI 10.17487/RFC5226, May 2008, | |||
| <http://www.rfc-editor.org/info/rfc5226>. | <http://www.rfc-editor.org/info/rfc5226>. | |||
| [RFC5890] Klensin, J., "Internationalized Domain Names for | ||||
| Applications (IDNA): Definitions and Document Framework", | ||||
| RFC 5890, DOI 10.17487/RFC5890, August 2010, | ||||
| <http://www.rfc-editor.org/info/rfc5890>. | ||||
| [RFC5891] Klensin, J., "Internationalized Domain Names in | [RFC5891] Klensin, J., "Internationalized Domain Names in | |||
| Applications (IDNA): Protocol", RFC 5891, | Applications (IDNA): Protocol", RFC 5891, | |||
| DOI 10.17487/RFC5891, August 2010, | DOI 10.17487/RFC5891, August 2010, | |||
| <http://www.rfc-editor.org/info/rfc5891>. | <http://www.rfc-editor.org/info/rfc5891>. | |||
| [RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6 | [RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6 | |||
| Address Text Representation", RFC 5952, | Address Text Representation", RFC 5952, | |||
| DOI 10.17487/RFC5952, August 2010, | DOI 10.17487/RFC5952, August 2010, | |||
| <http://www.rfc-editor.org/info/rfc5952>. | <http://www.rfc-editor.org/info/rfc5952>. | |||
| skipping to change at page 63, line 15 ¶ | skipping to change at page 63, line 15 ¶ | |||
| 11.2. Informative References | 11.2. Informative References | |||
| [I-D.ietf-cdni-control-triggers] | [I-D.ietf-cdni-control-triggers] | |||
| Murray, R. and B. Niven-Jenkins, "CDNI Control Interface / | Murray, R. and B. Niven-Jenkins, "CDNI Control Interface / | |||
| Triggers", draft-ietf-cdni-control-triggers-15 (work in | Triggers", draft-ietf-cdni-control-triggers-15 (work in | |||
| progress), May 2016. | progress), May 2016. | |||
| [I-D.ietf-cdni-redirection] | [I-D.ietf-cdni-redirection] | |||
| Niven-Jenkins, B. and R. Brandenburg, "Request Routing | Niven-Jenkins, B. and R. Brandenburg, "Request Routing | |||
| Redirection interface for CDN Interconnection", draft- | Redirection interface for CDN Interconnection", draft- | |||
| ietf-cdni-redirection-19 (work in progress), July 2016. | ietf-cdni-redirection-20 (work in progress), August 2016. | |||
| [I-D.ietf-cdni-uri-signing] | [I-D.ietf-cdni-uri-signing] | |||
| Leung, K., Faucheur, F., Brandenburg, R., Downey, B., and | Leung, K., Faucheur, F., Brandenburg, R., Downey, B., and | |||
| M. Fisher, "URI Signing for CDN Interconnection (CDNI)", | M. Fisher, "URI Signing for CDN Interconnection (CDNI)", | |||
| draft-ietf-cdni-uri-signing-09 (work in progress), June | draft-ietf-cdni-uri-signing-09 (work in progress), June | |||
| 2016. | 2016. | |||
| [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, | [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, | |||
| DOI 10.17487/RFC2818, May 2000, | DOI 10.17487/RFC2818, May 2000, | |||
| <http://www.rfc-editor.org/info/rfc2818>. | <http://www.rfc-editor.org/info/rfc2818>. | |||
| End of changes. 8 change blocks. | ||||
| 8 lines changed or deleted | 13 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/ | ||||