RFC 7910 on Interoperability between the Virtual Router Redundancy Protocol and PIM

rfc-editor@rfc-editor.org Thu, 16 June 2016 23:11 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3568512DD90 for <ietf-announce@ietfa.amsl.com>; Thu, 16 Jun 2016 16:11:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.028
X-Spam-Level:
X-Spam-Status: No, score=-104.028 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham 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 IRgLTzOdUZ2y for <ietf-announce@ietfa.amsl.com>; Thu, 16 Jun 2016 16:11: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 9C23812DD80 for <ietf-announce@ietf.org>; Thu, 16 Jun 2016 16:11:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 92934B80C46; Thu, 16 Jun 2016 16:11:46 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7910 on Interoperability between the Virtual Router Redundancy Protocol and PIM
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160616231146.92934B80C46@rfc-editor.org>
Date: Thu, 16 Jun 2016 16:11:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/2uaudJXAvXO-tLURm_5fK8fCvWc>
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2016 23:11:59 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7910

        Title:      Interoperability between the Virtual Router 
                    Redundancy Protocol and PIM 
        Author:     W. Zhou
        Status:     Informational
        Stream:     Independent
        Date:       June 2016
        Mailbox:    zhouweiisu@gmail.com
        Pages:      6
        Characters: 14255
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-zhou-pim-vrrp-06.txt

        URL:        https://www.rfc-editor.org/info/rfc7910

        DOI:        http://dx.doi.org/10.17487/RFC7910

This document introduces VRRP-aware PIM, a redundancy mechanism for
the Protocol Independent Multicast (PIM) to interoperate with the
Virtual Router Redundancy Protocol (VRRP).  It allows PIM to track
VRRP state and to preserve multicast traffic upon failover in a
redundant network with virtual routing groups enabled.  The mechanism
described in this document is based on Cisco IOS software
implementation.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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