This document discusses forming a community-based caching hosting model with smaller ISPs collectively meeting criteria to host CDN caching nodes. Key points include: - Small ISPs could qualify to host CDN caching nodes by forming a community and pooling their bandwidth and resources. - Costs like maintenance, operation and infrastructure could be reduced by sharing expenses based on bandwidth consumption across the community. - The author operates a community hosting CDN caching nodes since 2017 with six ISPs, currently hosting Facebook content and looking to partner with other CDN providers. - The community leases a data center rack and shares administrative duties, with expenses allocated using a ratio based on each member's bandwidth usage.

1. COMMUNITY BASED CDN NODE & CACHING HOSTING
Krishna Pd. Pokhrel
pokhrel.Krishna@gmail.com

2. ■ Facebook, YouTube or other CDN providers draw Most of the internet traffic
nowadays.
■ CDN providers are providing Cache Node to ISP for better performance
■ CDN providers are interested to provide cache node to big ISPs as they have large
bandwidth demand.
■ CDN providers have set criteria to provide CDN node but all ISPs may not meet those
criteria.
■ From the customer perspective, they expect same experience regardless of ISP size
and location.
■ Transparent Caching could not be a solution as most of the content are encrypted .

3. Hosting CDNs Cache Node,
forming a community Might
be a Solution…
■ Small ISPs Can collectively qualify to meet CDN provider’s criteria.
■ Less internet feed can serve high cached content.
■ User can get better experience then individual node.
■ Minimizes cost

4. Hosting CDNs Cache Node,
forming a community….
■ Maintenance and operation cost can be reduced through community serving
arrangements.
■ Expenses can be calculated according to consumption base (i.e. 95 percentile)
■ A formula can be applied to make “higher consumption lower rate and vice versa”.
■ A pooling fund can be created for expansions and contingencies.
■ Internet and other auxiliary service provider for CDN should be selected through
community-based competitive bidding process.
■ Same company will be liable for billing and other administrative works related thereof.
■ IP can be leased from community or member can contribute voluntarily for free of cost.

5. Hosting Caching, forming
a community….
■ we can implement centralize cache to save internet bandwidth and better user
experience
■ Need to impalement Policy based routing
■ Internet can be feed “use your own” so that other QoS maintained.
■ SLA won’t be affected, we can use ip-sla for reachability and availability check
■ One time setup could be complex
■ we can buy good caching software/hardware in shared investment.

6. Hosting Caching, forming a
community….
Note: still discussing with vendors for the possible challenges to implement this topology

7. Experience and
observations….
■ We are operating community to host CDN Cache Node since 2017 with participation of six ISPs.
■ The community is currently hosting Facebook FNA and approaching with other CDN providers.
■ We are leasing a rack from third-party data center.
■ One of the member is providing IP for free of cost so far.
■ One member from the community has been handling billing and other administrative work after
winning a competitive bid.
■ 1/1.2 exponential ratio is implemented to share expenses based on bandwidth consumption.
■ So far the community is working seamlessly. Other ISPs are also interested to foray in our mission.
■ Hosting transparent caching is in discussion. Some technical concerns are there which we are
having discussion with vendors.

8. Thank You