draft-ietf-cdni-control-triggers-10.txt | draft-ietf-cdni-control-triggers-11.txt | |||
---|---|---|---|---|
Network Working Group R. Murray | Network Working Group R. Murray | |||
Internet-Draft B. Niven-Jenkins | Internet-Draft B. Niven-Jenkins | |||
Intended status: Standards Track Velocix (Alcatel-Lucent) | Intended status: Standards Track Velocix (Alcatel-Lucent) | |||
Expires: June 8, 2016 December 6, 2015 | Expires: June 9, 2016 December 7, 2015 | |||
CDNI Control Interface / Triggers | CDNI Control Interface / Triggers | |||
draft-ietf-cdni-control-triggers-10 | draft-ietf-cdni-control-triggers-11 | |||
Abstract | Abstract | |||
This document describes the part of the CDN Interconnection Control | This document describes the part of the CDN Interconnection Control | |||
Interface that allows a CDN to trigger activity in an interconnected | Interface that allows a CDN to trigger activity in an interconnected | |||
CDN that is configured to deliver content on its behalf. The | CDN that is configured to deliver content on its behalf. The | |||
upstream CDN can use this mechanism to request that the downstream | upstream CDN can use this mechanism to request that the downstream | |||
CDN pre-positions metadata or content, or that it invalidates or | CDN pre-positions metadata or content, or that it invalidates or | |||
purges metadata or content. The upstream CDN can monitor the status | purges metadata or content. The upstream CDN can monitor the status | |||
of activity that it has triggered in the downstream CDN. | of activity that it has triggered in the downstream CDN. | |||
skipping to change at page 1, line 42 | skipping to change at page 1, line 42 | |||
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 June 8, 2016. | This Internet-Draft will expire on June 9, 2016. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2015 IETF Trust and the persons identified as the | Copyright (c) 2015 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 39, line 34 | skipping to change at page 39, line 34 | |||
The authors thank Kevin Ma for his input, and Carsten Bormann for his | The authors thank Kevin Ma for his input, and Carsten Bormann for his | |||
review and formalization of the JSON data. | review and formalization of the JSON data. | |||
10. References | 10. References | |||
10.1. Normative References | 10.1. Normative References | |||
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
Requirement Levels", BCP 14, RFC 2119, March 1997. | Requirement Levels", BCP 14, RFC 2119, March 1997. | |||
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000. | ||||
[RFC6707] Niven-Jenkins, B., Le Faucheur, F., and N. Bitar, "Content | ||||
Distribution Network Interconnection (CDNI) Problem | ||||
Statement", RFC 6707, September 2012. | ||||
[RFC7159] Bray, T., "The JavaScript Object Notation (JSON) Data | [RFC7159] Bray, T., "The JavaScript Object Notation (JSON) Data | |||
Interchange Format", RFC 7159, March 2014. | Interchange Format", RFC 7159, March 2014. | |||
[RFC7230] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol | [RFC7230] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol | |||
(HTTP/1.1): Message Syntax and Routing", RFC 7230, June | (HTTP/1.1): Message Syntax and Routing", RFC 7230, June | |||
2014. | 2014. | |||
[RFC7231] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol | [RFC7231] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol | |||
(HTTP/1.1): Semantics and Content", RFC 7231, June 2014. | (HTTP/1.1): Semantics and Content", RFC 7231, June 2014. | |||
skipping to change at page 40, line 27 | skipping to change at page 40, line 32 | |||
[I-D.ietf-cdni-metadata] | [I-D.ietf-cdni-metadata] | |||
Niven-Jenkins, B., Murray, R., Caulfield, M., and K. Ma, | Niven-Jenkins, B., Murray, R., Caulfield, M., and K. Ma, | |||
"CDN Interconnection Metadata", draft-ietf-cdni- | "CDN Interconnection Metadata", draft-ietf-cdni- | |||
metadata-12 (work in progress), October 2015. | metadata-12 (work in progress), October 2015. | |||
[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-13 (work in progress), October 2015. | ietf-cdni-redirection-13 (work in progress), October 2015. | |||
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000. | ||||
[RFC6707] Niven-Jenkins, B., Le Faucheur, F., and N. Bitar, "Content | ||||
Distribution Network Interconnection (CDNI) Problem | ||||
Statement", RFC 6707, September 2012. | ||||
[RFC7336] Peterson, L., Davie, B., and R. van Brandenburg, | [RFC7336] Peterson, L., Davie, B., and R. van Brandenburg, | |||
"Framework for Content Distribution Network | "Framework for Content Distribution Network | |||
Interconnection (CDNI)", RFC 7336, August 2014. | Interconnection (CDNI)", RFC 7336, August 2014. | |||
[RFC7337] Leung, K. and Y. Lee, "Content Distribution Network | [RFC7337] Leung, K. and Y. Lee, "Content Distribution Network | |||
Interconnection (CDNI) Requirements", RFC 7337, August | Interconnection (CDNI) Requirements", RFC 7337, August | |||
2014. | 2014. | |||
Appendix A. Formalization of the JSON Data | Appendix A. Formalization of the JSON Data | |||
End of changes. 5 change blocks. | ||||
9 lines changed or deleted | 9 lines changed or added | |||
This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |