[rfc-dist] RFC 8775 on PIM Designated Router Load Balancing
rfc-editor@rfc-editor.org Thu, 23 April 2020 01:54 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14E503A109A for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 22 Apr 2020 18:54:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0R2nHWiXvQW8 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 22 Apr 2020 18:54:50 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E195D3A109C for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 22 Apr 2020 18:54:50 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 17C0FF40713; Wed, 22 Apr 2020 18:54:44 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 13C32F4070F; Wed, 22 Apr 2020 18:54:43 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200423015443.13C32F4070F@rfc-editor.org>
Date: Wed, 22 Apr 2020 18:54:43 -0700
Subject: [rfc-dist] RFC 8775 on PIM Designated Router Load Balancing
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, pim@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
RFC 8775
Title: PIM Designated Router Load Balancing
Author: Y. Cai, H. Ou,
S. Vallepalli,
M. Mishra,
S. Venaas,
A. Green
Status: Standards Track
Stream: IETF
Date: April 2020
Mailbox: yiqun.cai@alibaba-inc.com,
heidi.ou@alibaba-inc.com,
vallepal@yahoo.com,
mankamis@cisco.com,
stig@cisco.com,
andy.da.green@bt.com
Pages: 18
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pim-drlb-15.txt
URL: https://www.rfc-editor.org/info/rfc8775
DOI: 10.17487/RFC8775
On a multi-access network, one of the PIM-SM (PIM Sparse Mode)
routers is elected as a Designated Router. One of the
responsibilities of the Designated Router is to track local multicast
listeners and forward data to these listeners if the group is
operating in PIM-SM. This document specifies a modification to the
PIM-SM protocol that allows more than one of the PIM-SM routers to
take on this responsibility so that the forwarding load can be
distributed among multiple routers.
This document is a product of the Protocols for IP Multicast Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org