Docstoc

Issues in Well Managed IP Multicasting Services _draft-hayashi

Document Sample
Issues in Well Managed IP Multicasting Services _draft-hayashi Powered By Docstoc
					    Issues in Well Managed IP Multicasting
                   Services
        <draft-hayashi-maccnt-01.txt>

                 November 8, 2004
Tsunemasa Hayashi (hayashi.tsunemasa@lab.ntt.co.jp)
    Haixiang He (haixiang@nortelnetworks.com)
     Hiroaki Satou (satou.hiroaki@lab.ntt.co.jp)
      Hiroshi Ohta(ohta.hiroshi@lab.ntt.co.jp)

                                                      1
Outline


   • Introduce “well managed IP
     multicasting”
   • Describe operator’s requirements for
     “well managed IP multicasting”
   • Solicit active participation for the work
     on “well managed IP multicasting”




                                                 2
IP multicasting – network operator’s expectation


   • Network operators want
       – to build efficient networks for information
         distributions services (e.g., CDN,
         video/audio streaming)
       – to create value added services for which
         they can charge
       – to build a manageable network on which
         they can grasp what is happening




                                                       3
IP multicasting – current problems

   • No accounting capabilities are provided by
     the current standard (based on IGMP/MLD)
       – Network cannot identify receivers
       – Network cannot grasp user activities (when they
         joined and left)
       – Network cannot authenticate/authorize users
          • Any user can join without any eligibility check
   • Not sufficient for carrier-class services (high-
     quality, premium/fee-based)




                                                              4
 Well managed IP multicasting

                                                     5. Content key should be delivered
1. Accurate tracking (accounting)   Content server
                                                     to cover each user receiving period.
of Join/Leave by user, by group                      Charging should be based on user           6. Shorten the
                                                     reception, not on key holding period       time from order to
                                                                                                service provision.
                                          Advanced multicast CDN                                Service provision
3. Support preview to
                                                                                                on-demand is one
each group (Content)                                           router                           of the goals of
                                                                                                service providers.


                                                                               Edge node

                                    e          e                               e           2. Protect content from
               Shared Media                                     e
                                                                                           illicit access

                                                      Move
                                                       With
                                                                                             Illegal user
                                                      device
 Content key

                                                                    User may move and change devices.
                                4. End user should be able
                                to access CDN from anywhere

                                                                                                               5
Architecture example

• Network operator and content providers cooperate to provide a service.
• They need to share the content revenue
                                        There can be more than one content provider
                 Content Provider
               Content Provider          Share for the network provider (usage base)
              Content Provider
                         or
                       or
                     or ISP
    Content           ISP
                    ISP                   Share for the content provider (usage base)

     border router
     (provider edge)


                                           Network Provider

                          edge router




     End User          End User




                                                                                        6
General requirements for well managed multicasting

   •   User identification
   •   Access control
   •   Appropriate admission control for join action
   •   Accounting and billing
   •   Accumulating logs
   •   Service and terminal portability
   •   Support of ASM and SSM
   •   Quick reaction
   •   Scalability


                                                       7
Proposal


   • Clarify the possible network
     architectures and service scenarios.
   • Clarify the requirements for well
     managed IP multicasting
   • Find solutions which meet the
     requirements.




                                            8
Next Steps

   • Continue the work on “well managed
     multicasting”
   • We are working on the draft and set up
     a dedicated mailing list for this issue.
      – Mailing list:
        <mac-external@lyris.nortelnetworks.com>
      – Archive:
        http//standards.nortelnetworks.com/archive
        s/mac-external.html
   • We solicit feedback and welcome active
     participation.

                                                     9

				
DOCUMENT INFO
Shared By:
Stats:
views:4
posted:8/1/2011
language:English
pages:9
Description: IP multicasting is the multicast hardware abstraction, is a standard IP network layer protocol extensions. It does this by using a specific IP multicast address, delivered in accordance with the principle of maximum, the IP datagram transmission to a multicast group hosts a collection. Its basic approach is: When an individual to a group of people to send data, it does not have data to send data to everyone, simply send data to a specific address group booking, all add to the group's per capita You can receive the data. So the sender, the data can be sent only once to send to all recipients, greatly reducing the network load and the burden of the sender.