📡
Blockcast Network - Light Paper (It's a WIP)
  • Welcome to Blockcast Network
  • Intro
    • The Internet Capacity Crunch
  • Overview
    • What is Blockcast?
    • Mission And Values
    • How Blockcast Works
    • Ecosystem Roles
  • Building Blocks
    • Control Plane
      • dCDN Controller
      • CDN Interconnect
      • Challenge Coordination
      • Service Contracts
    • Data Plane
      • Multicast HTTP Adaption
      • Multicast Backbone
      • Traffic Router
    • Consensus Layer
  • Getting Started
    • How Do I Participate in The Network
      • BEACON
        • Start Running your BEACON Today
        • BEACON Common Questions
      • RELAY
      • CAST
Powered by GitBook
On this page
  1. Building Blocks
  2. Data Plane

Traffic Router

PreviousMulticast BackboneNextConsensus Layer

Last updated 6 months ago

Blockcast CDNs use a traffic router that respond to DNS or HTTP based user requests using the client IP either resolve or redirect traffic to the best edge server to deliver the response. Request delegations can also be sent via the CDN interconnection request routing interface and include the content provider signature as per RFC9246 or RFC9421, so the downstream CDN can verify and bill requests.

\

HTTP based request routing is easier to implement on home caches because it can use unpriviledged ports (>1024) that can work on restrictive OS like Android or ChromeOS. However, it does not work on ISP networks that give subscribers the same public IP address. In this case, ISPs can configure Blockcast’s traffic router to be an authoritative DNS server, receiver nodes can get secure Relay hardware that can run DNS in your home, or you can send client authenticated DNS requests that can be proxied on an a separate device.

\

Another important function of Blockcast’s traffic router is to enable MAHP gateways in Receiver or Relays to resolve the address of the multicast source, or fallback AMT server that will proxy services using proven coverage information and the user’s address.

\