Multiple Upstream Interface Support for IGMP/MLD Proxy
draft-asaeda-pim-multiif-igmpmldproxy-00
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2015-03-23
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
PIM Working Group H. Asaeda
Internet-Draft K. Matsuzono
Expires: September 24, 2015 NICT
March 23, 2015
Multiple Upstream Interface Support for IGMP/MLD Proxy
draft-asaeda-pim-multiif-igmpmldproxy-00
Abstract
This document describes the way of supporting multiple upstream
interfaces for an IGMP/MLD proxy device. The proposed extension
enables an IGMP/MLD proxy device to receive multicast sessions/
channels through the different upstream interfaces. The upstream
interface is selected based on the pre-configured supported address
prefixes and interface priority value. A mechanism for upstream
interface takeover that switches from an inactive upstream interface
to an active upstream interface is also described.
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 http://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 September 24, 2015.
Copyright Notice
Copyright (c) 2015 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
(http://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
to this document. Code Components extracted from this document must
Asaeda & Matsuzono Expires September 24, 2015 [Page 1]
Internet-Draft Multiple Upstream for IGMP/MLD Proxy March 2015
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 . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Upstream Selection Mechanism . . . . . . . . . . . . . . . . 5
3.1. Channel-Based Upstream Selection . . . . . . . . . . . . 5
3.2. Subscriber-Based Upstream Selection . . . . . . . . . . . 5
4. Upstream Interface Takeover . . . . . . . . . . . . . . . . . 5
5. Candidate Upstream Interface Configuration . . . . . . . . . 6
5.1. Subscriber Address Prefix and Supported Address Prefix . 7
5.2. Interface Priority . . . . . . . . . . . . . . . . . . . 8
5.3. Active Interval . . . . . . . . . . . . . . . . . . . . . 8
5.4. Default Upstream Interface . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.1. Normative References . . . . . . . . . . . . . . . . . . 10
8.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
The Internet Group Management Protocol (IGMP) [2][4] for IPv4 and the
Multicast Listener Discovery Protocol (MLD) [3][4] for IPv6 are the
standard protocols for hosts to initiate joining or leaving of
multicast sessions. A proxy device performing IGMP/MLD-based
forwarding (as known as IGMP/MLD proxy) [5] maintains multicast
membership information by IGMP/MLD protocols on the downstream
interfaces and sends IGMP/MLD membership report messages via the
upstream interface to the upstream multicast routers when the
membership information changes (e.g., by receiving solicited/
unsolicited report messages). The proxy device forwards appropriate
multicast packets received on its upstream interface to each
downstream interface based on the downstream interface's
subscriptions.
According to the specification of [5], an IGMP/MLD proxy has *a
single* upstream interface and one or more downstream interfaces.
The multicast forwarding tree must be manually configured by
designating upstream and downstream interfaces on an IGMP/MLD proxy
device, and the root of the tree is expected to be connected to a
wider multicast infrastructure. An IGMP/MLD proxy device hence
Show full document text