Update on Requirements for Multicast AAA coordinated between Content Providers and Network Service P

1
Update on Requirements for Multicast AAA
coordinated between Content Provider(s) and
Network Service Provider(s) draft-ietf-mboned-m
accnt-req-08

• Tsunemasa Hayashi, NTT
• Haixiang He, Nortel
• Hiroaki Satou, NTT
• Hiroshi Ohta, NTT
• Susheela Vaidya, Cisco Systems

2
Outline (1) Status

• mboned-maccnt-req-04 submitted February 2006 and
  proceeded through WGLC after IETF 65 Dallas
• mboned-maccnt-req-05 submitted September 2007 to
  address IESG DISCUSS comments (06, 07 were just
  version number updates to keep alive)
• The latest version (mboned-maccnt-req-08) was a
  reorganization of the requirements at the advice
  of ADs and others
• Introduction and explanation/logic of need for
  draft redone
• no requirements added
• requirements reorganized

3
Outline (2)

• 1. Introduction- rewritten
• 3. Current Business Models
• 3.1. Single entity model where CP and NSP are the
  same entity
• Rewritten, simplified
• Removed reference to Information Server
• 3.2. Multiple entity model without direct
  content-based billing (e.g. advertising model)
• new section
• 4. Proposed Model Multity-entity CDS with direct
  billing of the end user
• Slightly rewritten to fit draft reorganization
• Removed reference to Information Server

4
Outline (3) Requirements

• Requirements reordered/ regrouped
• 4.1. Information Required by Entities to Support
  the Proposed Business Model
• User identification and Authentication
• authorization for content consumption eligibility
• user tracking for billing based on actual content
  consumption and network resource usage
• User Authorization
• prevent content access by ineligible users
• NSP needs a mechanism to receive channel
  programming data from CP
• Content usage information by user
• Required to precisely log information such as
  who (host/user) is accessing what content at what
  time (join action) until what time (leave
  action).
• Nice result of the access-control decision
• Notification to Users of the Result of the Join
  Request

5
Outline (4) Requirements

• Requirements reordered/ regrouped
• 5. Admission Control for Multicasting
• NSP should be able to apply appropriate access
  controlling actions based on user eligibility
  status
• Access control for eligible users
• Ability to reject action requested by ineligible
  users
• Controlling bandwidth for each users, and overall
  bandwidth. (2 requirements companied into 1 more
  general requirement)

6
Outline (5) Requirements

• Requirements reordered/ regrouped
• 6. Performance requirements
• 7. Concomitant requirements
• Scalability
• Service and Terminal Portability
• Deployable as Alternative to Unicast
• Support of ASM and SSM
• Small Impact on the Existing Product
• Multicast Replication

7
Outline (6)

• 8. Constituent Logical Functional Components (New
  section, copied/adapted from draft-ietf-mboned-mul
  tiaaa-framework-08.txt)
• 9. Acknowledgements
• 10. IANA Considerations
• 11. Security Considerations
• 12. Privacy considerations

No changes
8
Going Forward

• - draft was reorganized, but no requirements were
  added. does it need to go undergo WGLC again?