Dear ALTO WG members, This is a short summary of updates in *alto-cdni-request-routing-alto-03*.
*Major updates:* 1. Add a new section, "*section 7 Protocol Errors"*. 2. In *section 3.6*, shorten the original encoding with *BaseAdvertisementObject* defined in Section 5.1 of RFC 8008. 3. In *section 3.6*, remove the description of optimization to keep the document clean, but keep a note about the optimization of BaseAdvertisement objects. * Note: Further optimization of BaseAdvertisement objects to* * effectively provide the advertisement of capabilities with footprint* * restrictions is certainly possible, however, it is not necessary for* * the basic interconnection of CDNs. The note here is for* * completeness, however, the specifics of such mechanisms are outside* * the scope of this document.* *Minor updates:* 1. Change media type of CDNI FCI Map to *"application/alto+cdnifcimap+json"* .. 2. Change the response name of CDNI FCI Map to *"cdni-fci-map"* so it is consist with "network-map", "cost-map", "endpoint-cost-map". 3. Fix some typos. Any comments or feedback are highly appreciated! Bests, Shawn Lin On Mon, Jun 18, 2018 at 12:56 PM <[email protected]> wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Application-Layer Traffic Optimization WG > of the IETF. > > Title : Content Delivery Network Interconnection (CDNI) > Request Routing: CDNI Footprint and Capabilities Advertisement using ALTO > Authors : Jan Seedorf > Y.R. Yang > Kevin J. Ma > Jon Peterson > X.S. Lin > Filename : draft-ietf-alto-cdni-request-routing-alto-03.txt > Pages : 34 > Date : 2018-06-17 > > Abstract: > The Content Delivery Networks Interconnection (CDNI) WG is defining a > set of protocols to inter-connect CDNs, to achieve multiple goals > such as extending the reach of a given CDN to areas that are not > covered by that particular CDN. One component that is needed to > achieve the goal of CDNI is the CDNI Request Routing Footprint & > Capabilities Advertisement interface (FCI) [RFC7336]. [RFC8008] has > defined precisely the semantics of FCI and provided guidelines on the > FCI protocol, but the exact protocol is explicitly outside the scope > of that document. In this document, we define an FCI protocol using > the Application-Layer Traffic Optimization (ALTO) protocol. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-alto-cdni-request-routing-alto/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-alto-cdni-request-routing-alto-03 > > https://datatracker.ietf.org/doc/html/draft-ietf-alto-cdni-request-routing-alto-03 > > A diff from the previous version is available at: > > https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cdni-request-routing-alto-03 > > > Please note that it may take a couple of minutes from the time of > submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > alto mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/alto >
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
