[bess] RFC 8502 on L2L3 VPN Multicast MIB

rfc-editor@rfc-editor.org Sat, 22 December 2018 01:16 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53A41130F40; Fri, 21 Dec 2018 17:16:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 sZZcCoUPgoy9; Fri, 21 Dec 2018 17:16:39 -0800 (PST)
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 49482130EC9; Fri, 21 Dec 2018 17:16:39 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id DD3C6B81A87; Fri, 21 Dec 2018 17:16:37 -0800 (PST)
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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, bess@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20181222011637.DD3C6B81A87@rfc-editor.org>
Date: Fri, 21 Dec 2018 17:16:37 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/s1MenP1QVYnOzvBrHH360wKQ3XM>
Subject: [bess] =?utf-8?q?RFC_8502_on_L2L3_VPN_Multicast_MIB?=
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Dec 2018 01:16:42 -0000

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

        
        RFC 8502

        Title:      L2L3 VPN Multicast MIB 
        Author:     Z. Zhang,
                    H. Tsunoda
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2018
        Mailbox:    zzhang@juniper.net, 
                    tsuno@m.ieice.org
        Pages:      20
        Characters: 40349
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bess-l2l3-vpn-mcast-mib-16.txt

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

        DOI:        10.17487/RFC8502

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes two MIB modules that will be used by
other MIB modules for monitoring and/or configuring Layer 2 and Layer
3 Virtual Private Networks that support multicast.

This document is a product of the BGP Enabled Services 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