Triple Play / Multiplay Computer Networks 2007 Week 8 Lecture 2 by Donald Neal

Week 8 Lecture 2 COPS RADIUS CoA Triple Play / Quad Play / Multiplay Architecture

RADIUS, Again BRAS RADIUS Authentication RADIUS Accounting Access-Request Access-Accept (Policy) Authorisation at Session Start

RADIUS, Again BRAS RADIUS Authentication RADIUS Accounting Customer Database LDAP

(Self)Provisioning with RADIUS BRAS RADIUS Authentication RADIUS Accounting Customer Database LDAP WWW/Provisioning

Common Open Policy Service PEP Policy Enforcement Point Policy Server/ Policy Decision Point Client-Open (OPN) Client-Accept(CAT) One transaction per client type Keepalive (KA) Request (REQ) Decision (DEC) Report State (RPT)

Common Open Policy Service PEP Policy Enforcement Point Policy Server/ Policy Decision Point Decision (DEC) Report State (RPT) Delete Query State (DRQ) Report State(RPT) Client-Close Per-client type. Can be sent by PDP or by PEP.

Common Open Policy Service PEP Policy Enforcement Point Policy Server/ Policy Decision Point REQ causes the PDP to establish state for that IP address, ifindex and client type That state retained until PEP says it's no longer needed, or after contact with the PEP is lost. Every REQ has a DEC, but a DEC can be sent without a REQ.

(Self)Provisioning with COPS BRA S (PEP) RADIUS Authentication RADIUS Accounting Customer Database WWW COPS PDP (and accounting?)

COPS Authentication PEP Policy Enforcement Point Policy Server/ Policy Decision Point In Theory Client-Open (OPN) Client-Type AAA Client-Accept(CAT) Client-Open (OPN) Client-Type IP Client-Accept(CAT) Client-Open (OPN) Client-Type SIP... Not standardised?

The Goblin Channel BRA S (PEP) RADIUS Authentication Customer Database WWW COPS PDP (and accounting?) VIDEO INTERNET

Triple-Play Goblin Net BNG (PEP) RADIUS Authentication Customer Database Portal COPS Brains (PDP) VIDEO INTERNET VoIP

RADIUS Change of Authorisation BNG RADIUS Server CoA-Request CoA-Response Needs VSA.

RADIUS CoA - RFC | Code | Identifier | Length | | | | Authenticator | | | | Attributes Code The Code field is one octet, and identifies the type of RADIUS packet. Packets received with an invalid Code field MUST be silently discarded. RADIUS codes (decimal) for this extension are assigned as follows: 40 - Disconnect-Request [RFC2882] 41 - Disconnect-ACK [RFC2882] 42 - Disconnect-NAK [RFC2882] 43 - CoA-Request [RFC2882] 44 - CoA-ACK [RFC2882] 45 - CoA-NAK [RFC2882]

Triple Play / Quad Play / Multiplay

Geoff Huston in February 2006 “peer-to-peer file sharing has taken over the Internet, with estimates of between 45% to 70% of total internet traffic volumes being attributable to music and video sharing. This has turned the Internet into one of the more prodigious music and video distribution systems ever conceived. This shift in user behaviour has significant implications for the entertainment industry’s chosen distribution methods, and it is likely that the industry will ultimately come to terms with peer sharing technologies such as BitTorrent. The loser in all this is likely to be real time video delivery systems, so one reasonable conclusion is that real time content delivery, or Triple Play time, is over – BitTorrent has won over the user! -

And... Vodafone Apple Microsoft BBC DRM YouTube

Further Reading Broadband Network Architectures COPS RFC2748 – The COPS (Common Open Policy Service) Protocol RFC3084 – COPS Usage for Policy Provisioning RADIUS CoA RFC Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS) BBC iPlayer Campaign Against DRM -

Reading for Next Lecture Pepelnjack & Guichard, MPLS and VPN Architectures pp. 5-30