CDNI Requirements draft-lefaucheur-cdni-requirements-01 Mohamed Boucadair Christian Jacquenet
-
Upload
aubrey-hicks -
Category
Documents
-
view
214 -
download
0
description
Transcript of CDNI Requirements draft-lefaucheur-cdni-requirements-01 Mohamed Boucadair Christian Jacquenet
![Page 1: CDNI Requirements draft-lefaucheur-cdni-requirements-01 Mohamed Boucadair Christian Jacquenet](https://reader036.fdocuments.in/reader036/viewer/2022082723/5a4d1b0c7f8b9ab05998c18d/html5/thumbnails/1.jpg)
www.huawei.com
CDNI Requirementsdraft-lefaucheur-cdni-requirements-01
Mohamed Boucadair ([email protected])Christian Jacquenet ([email protected])Dean Cheng ([email protected])Yiu Lee ([email protected])
IETF77, Anaheim
Francois Le Faucheur, CiscoMahesh Viveganandhan, Cisco
Grant Watson, BTYiu Lee, Comcast
IETF 80, Prague
![Page 2: CDNI Requirements draft-lefaucheur-cdni-requirements-01 Mohamed Boucadair Christian Jacquenet](https://reader036.fdocuments.in/reader036/viewer/2022082723/5a4d1b0c7f8b9ab05998c18d/html5/thumbnails/2.jpg)
Requirements Structure Sets of Requirements
Generic Requirements Control Protocol Requirements Request Routing Protocol Requirements Metadata Distribution Protocol Requirements Logging Protocol Requirements Security Requirements
Scopes (in each set): Initial scope (within potential WG initial charter)
MUST: strong convergence that it is required “day1” SHOULD/MAY: needs further arbitration on whether it can be
supported “day1” Future scope (outside potential WG initial charter)
![Page 3: CDNI Requirements draft-lefaucheur-cdni-requirements-01 Mohamed Boucadair Christian Jacquenet](https://reader036.fdocuments.in/reader036/viewer/2022082723/5a4d1b0c7f8b9ab05998c18d/html5/thumbnails/3.jpg)
Generic Requirements R1: Leverage existing protocols. R2: No change in the user agent (the client). R3: CDNI solution must not be intrusive into CDNs:
dCDN and uCDN are not required to know each other’s cache topology, cache status,…
R4 & R5: HTTP is the first supported protocol for Delivery and Acquisition.
R8: [should] support cascaded CDNs. R9: [should] support any kind of CDNI topology (e.g. Star, Ring,
Tree etc.) R10: CDNI must prevent looping R11: CDNI must consider known issues with 3rd party references
uCDN= upstream CDNdCDN= downstream CDN
![Page 4: CDNI Requirements draft-lefaucheur-cdni-requirements-01 Mohamed Boucadair Christian Jacquenet](https://reader036.fdocuments.in/reader036/viewer/2022082723/5a4d1b0c7f8b9ab05998c18d/html5/thumbnails/4.jpg)
Control Protocol Requirements
These requirements are defined to: Enable CDNs to communicate for management/bootstrapping
prior to the actual content delivery. Enable uCDN to trigger actions in dCDN
Some highlights: R15: Content Purge request by uCDN (invalidate/delete an
object). R16: Content Purge Acknowledgment by dCDN. R17: Trigger Metadata pre-positioning from the uCDN to dCDN. R18: [should] Trigger content pre-positioning from the uCDN to
dCDN
![Page 5: CDNI Requirements draft-lefaucheur-cdni-requirements-01 Mohamed Boucadair Christian Jacquenet](https://reader036.fdocuments.in/reader036/viewer/2022082723/5a4d1b0c7f8b9ab05998c18d/html5/thumbnails/5.jpg)
Request Routing Protocol Requirements These requirements are defined to allow the uCDN
Routing-Request System (RRS) to delegate a request to the dCDN RRS.
Highlights: R27: dCDN can refuse further request delegations (“busy” tone) R28: [should] dCDN advertises capabilities (e.g. footprint,
content types), resources (e.g. streaming bandwidth) and affinities (e.g. delivery cost)
R30: [may] dCDN advertises policy/admin-info (e.g. max requests per second, max aggregate volume)
R31 & R32: efficient for small objects (aka DNS-based) and for large objects (aka HTTP-based)
R33 & R34: Support both Recursive Request Routing and Iterative Request Routing.
R37: Pass the user agent location information. R38: Pass the content metadata location information.
![Page 6: CDNI Requirements draft-lefaucheur-cdni-requirements-01 Mohamed Boucadair Christian Jacquenet](https://reader036.fdocuments.in/reader036/viewer/2022082723/5a4d1b0c7f8b9ab05998c18d/html5/thumbnails/6.jpg)
Metadata Distribution Protocol Requirements
These requirements are defined to allow the uCDN to communicate to dCDN the “distribution metadata”
Highlights: R45: uCDN provides metadata to dCDN R46: Support both pre-positioning and dynamic content
acquisition R47: Support metadata “Pull” R48: Support metadata “Push” R49 & R50: metadata must convey where/how dCDN can
acquire content R51 & R52: Support real-time Add/Modify/Delete metadata R53 & R54: Metadata data structure must support referencing a
single object or a set of objects. R58 & R59 : Support distribution control policies (geo-blocking,
time window & authorization checks (e.g. URI signing)Distribution metadata = metadata that is relevant to, and has to be processed, by CDNs (eg where to acquire content, time window)
![Page 7: CDNI Requirements draft-lefaucheur-cdni-requirements-01 Mohamed Boucadair Christian Jacquenet](https://reader036.fdocuments.in/reader036/viewer/2022082723/5a4d1b0c7f8b9ab05998c18d/html5/thumbnails/7.jpg)
Logging Protocol Requirements
In a distributed system such as CDNI, logging is used to track/recreate the chain of events (for accounting, monitoring, analytics, troubleshooting).
Highlights: R63: Reliable logging. R64: dCDN provides logging to uCDN for content delivery
performed by dCDN on behalf of uCDN R67: Support offload batch upload of log files.
![Page 8: CDNI Requirements draft-lefaucheur-cdni-requirements-01 Mohamed Boucadair Christian Jacquenet](https://reader036.fdocuments.in/reader036/viewer/2022082723/5a4d1b0c7f8b9ab05998c18d/html5/thumbnails/8.jpg)
Security Requirements
A set of requirements to secure CDNI R74: Support secure channel to exchange data over Internet. R75: Protect against DOS attack. R76: [should] non-repudiation of logs. R77: [should] Protect against spoofed log. R78: [may] Define a mechanism to delegate credentials to
downstream CDN to acquire content from the origin.
![Page 9: CDNI Requirements draft-lefaucheur-cdni-requirements-01 Mohamed Boucadair Christian Jacquenet](https://reader036.fdocuments.in/reader036/viewer/2022082723/5a4d1b0c7f8b9ab05998c18d/html5/thumbnails/9.jpg)
Questions?
![Page 10: CDNI Requirements draft-lefaucheur-cdni-requirements-01 Mohamed Boucadair Christian Jacquenet](https://reader036.fdocuments.in/reader036/viewer/2022082723/5a4d1b0c7f8b9ab05998c18d/html5/thumbnails/10.jpg)
Two New Terms Recursive CDNI Request Routing
Consult the downstream CDN to make the routing decision
Iterative CDNI Request Routing Make the routing decision without consulting downstream CDN