| rfc8006v1.txt | rfc8006.txt | |||
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) B. Niven-Jenkins | Internet Engineering Task Force (IETF) B. Niven-Jenkins | |||
| Request for Comments: 8006 R. Murray | Request for Comments: 8006 R. Murray | |||
| Category: Standards Track Velocix (Alcatel-Lucent) | Category: Standards Track Velocix (Alcatel-Lucent) | |||
| ISSN: 2070-1721 M. Caulfield | ISSN: 2070-1721 M. Caulfield | |||
| Cisco Systems | Cisco Systems | |||
| K. Ma | K. Ma | |||
| Ericsson | Ericsson | |||
| G. Watson | ||||
| Velocix (Alcatel-Lucent) | ||||
| K. Leung | ||||
| Cisco Systems | ||||
| October 2016 | October 2016 | |||
| Content Delivery Network Interconnection (CDNI) Metadata | Content Delivery Network Interconnection (CDNI) Metadata | |||
| Abstract | Abstract | |||
| The Content Delivery Network Interconnection (CDNI) metadata | The Content Delivery Network 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 | |||
| skipping to change at page 4, line 6 | skipping to change at page 3, line 50 | |||
| 7.2. "CDNI Metadata Footprint Types" Registry . . . . . . . . 57 | 7.2. "CDNI Metadata Footprint Types" Registry . . . . . . . . 57 | |||
| 7.3. "CDNI Metadata Protocol Types" Registry . . . . . . . . . 58 | 7.3. "CDNI Metadata Protocol Types" Registry . . . . . . . . . 58 | |||
| 8. Security Considerations . . . . . . . . . . . . . . . . . . . 58 | 8. Security Considerations . . . . . . . . . . . . . . . . . . . 58 | |||
| 8.1. Authentication and Integrity . . . . . . . . . . . . . . 58 | 8.1. Authentication and Integrity . . . . . . . . . . . . . . 58 | |||
| 8.2. Confidentiality and Privacy . . . . . . . . . . . . . . . 59 | 8.2. Confidentiality and Privacy . . . . . . . . . . . . . . . 59 | |||
| 8.3. Securing the CDNI Metadata Interface . . . . . . . . . . 59 | 8.3. Securing the CDNI Metadata Interface . . . . . . . . . . 59 | |||
| 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 60 | 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 60 | |||
| 9.1. Normative References . . . . . . . . . . . . . . . . . . 60 | 9.1. Normative References . . . . . . . . . . . . . . . . . . 60 | |||
| 9.2. Informative References . . . . . . . . . . . . . . . . . 62 | 9.2. Informative References . . . . . . . . . . . . . . . . . 62 | |||
| Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 63 | Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 63 | |||
| Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 63 | ||||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 63 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 63 | |||
| 1. Introduction | 1. Introduction | |||
| Content Delivery Network Interconnection (CDNI) [RFC6707] enables a | Content Delivery Network Interconnection (CDNI) [RFC6707] enables a | |||
| downstream Content Delivery Network (dCDN) to service content | downstream Content Delivery Network (dCDN) to service content | |||
| requests on behalf of an upstream CDN (uCDN). | requests on behalf of an upstream CDN (uCDN). | |||
| The CDNI metadata interface (MI) is discussed in [RFC7336] along with | The CDNI metadata interface (MI) is discussed in [RFC7336] along with | |||
| four other interfaces that can be used to compose a CDNI solution | four other interfaces that can be used to compose a CDNI solution | |||
| skipping to change at page 63, line 16 | skipping to change at page 63, line 16 | |||
| Interconnection (CDNI) Control Interface / Triggers", | Interconnection (CDNI) Control Interface / Triggers", | |||
| RFC 8007, DOI 10.17487/RFC8007, October 2016, | RFC 8007, DOI 10.17487/RFC8007, October 2016, | |||
| <http://www.rfc-editor.org/info/rfc8007>. | <http://www.rfc-editor.org/info/rfc8007>. | |||
| Acknowledgments | Acknowledgments | |||
| The authors would like to thank David Ferguson, Francois Le Faucheur, | The authors would like to thank David Ferguson, Francois Le Faucheur, | |||
| Jan Seedorf, and Matt Miller for their valuable comments and input to | Jan Seedorf, and Matt Miller for their valuable comments and input to | |||
| this document. | this document. | |||
| Contributors | ||||
| The authors would also like to thank Grant Watson and Kent Leung for | ||||
| their contributions to this document. | ||||
| Authors' Addresses | Authors' Addresses | |||
| Ben Niven-Jenkins | Ben Niven-Jenkins | |||
| Velocix (Alcatel-Lucent) | Velocix (Alcatel-Lucent) | |||
| 3 Ely Road | 3 Ely Road | |||
| Milton, Cambridge CB24 6AA | Milton, Cambridge CB24 6AA | |||
| United Kingdom | United Kingdom | |||
| Email: ben@velocix.com | Email: ben@velocix.com | |||
| skipping to change at page 64, line 12 | skipping to change at line 2895 | |||
| Phone: +1-978-936-9307 | Phone: +1-978-936-9307 | |||
| Email: mcaulfie@cisco.com | Email: mcaulfie@cisco.com | |||
| Kevin J. Ma | Kevin J. Ma | |||
| Ericsson | Ericsson | |||
| 43 Nagog Park | 43 Nagog Park | |||
| Acton, MA 01720 | Acton, MA 01720 | |||
| United States of America | United States of America | |||
| Phone: +1 978-844-5100 | Phone: +1 978-844-5100 | |||
| Email: kevin.j.ma@ericsson.com | Email: kevin.j.ma@ericsson.com | |||
| Grant Watson | ||||
| Velocix (Alcatel-Lucent) | ||||
| 3 Ely Road | ||||
| Milton, Cambridge CB24 6AA | ||||
| United Kingdom | ||||
| Email: gwatson@velocix.com | ||||
| Kent Leung | ||||
| Cisco Systems | ||||
| 3625 Cisco Way | ||||
| San Jose, CA 95134 | ||||
| United States of America | ||||
| Email: kleung@cisco.com | ||||
| End of changes. 4 change blocks. | ||||
| 4 lines changed or deleted | 6 lines changed or added | |||
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||