Requirements for the extension of the IGMP/MLD proxy functionality to support multiple upstream interfaces
draft-ietf-pim-multiple-upstreams-reqs-07

The information below is for an old version of the document
Document Type Active Internet-Draft (pim WG)
Last updated 2018-11-06 (latest revision 2018-10-22)
Replaces draft-contreras-pim-multiple-upstreams-reqs
Stream IETF
Intended RFC status Informational
Formats pdf htmlized bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Stig Venaas
Shepherd write-up Show (last changed 2017-11-20)
IESG IESG state AD is watching
Consensus Boilerplate Unknown
Telechat date
Responsible AD Alvaro Retana
Send notices to Stig Venaas <stig@venaas.com>, aretana.ietf@gmail.com
PIM Working Group                                          LM. Contreras
Internet-Draft                                                Telefonica
Intended status: Informational                             CJ. Bernardos
Expires: April 25, 2019                 Universidad Carlos III de Madrid
                                                               H. Asaeda
                                                                    NICT
                                                              N. Leymann
                                                        Deutsche Telekom
                                                        October 22, 2018

 Requirements for the extension of the IGMP/MLD proxy functionality to
                  support multiple upstream interfaces
               draft-ietf-pim-multiple-upstreams-reqs-07

Abstract

   The purpose of this document is to define the requirements for a MLD
   (for IPv6) or IGMP (for IPv4) proxy with multiple interfaces covering
   a variety of applicability scenarios.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 25, 2019.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Contreras, et al.        Expires April 25, 2019                 [Page 1]
Internet-Draft  Reqs for MLD proxy with multiple upstream   October 2018

   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Problem statement . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Scenarios of applicability  . . . . . . . . . . . . . . . . .   5
     4.1.  Fixed network scenarios . . . . . . . . . . . . . . . . .   6
       4.1.1.  Multicast wholesale offer for residential services  .   6
         4.1.1.1.  Requirements  . . . . . . . . . . . . . . . . . .   6
       4.1.2.  Multicast resiliency  . . . . . . . . . . . . . . . .   6
         4.1.2.1.  Requirements  . . . . . . . . . . . . . . . . . .   7
       4.1.3.  Load balancing for multicast traffic in the metro
               segment . . . . . . . . . . . . . . . . . . . . . . .   7
         4.1.3.1.  Requirements  . . . . . . . . . . . . . . . . . .   7
       4.1.4.  Network merging with different multicast services . .   8
         4.1.4.1.  Requirements  . . . . . . . . . . . . . . . . . .   8
       4.1.5.  Multicast service migration . . . . . . . . . . . . .   9
         4.1.5.1.  Requirements  . . . . . . . . . . . . . . . . . .   9
     4.2.  Mobile network scenarios  . . . . . . . . . . . . . . . .   9
   5.  Summary of requirements . . . . . . . . . . . . . . . . . . .  10
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   The aim of this document is to define the functionality that an IGMP/
   MLD proxy with multiple upstream interfaces should have in order to
   support different scenarios of applicability in both fixed and mobile
   networks.  This functionality is needed in order to simplify node
   functionality and to ensure an easier deployment of multicast
   capabilities in all the use cases described in this document.

   For doing that, a number of scenarios are described, representing
   current deployments and needs from operator's networks.  From that
Show full document text