RFC 9062 on Framework and Requirements for Ethernet VPN (EVPN) Operations, Administration, and Maintenance (OAM)
rfc-editor@rfc-editor.org Thu, 01 July 2021 01:31 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 AEA6C3A0ADE; Wed, 30 Jun 2021 18:31:47 -0700 (PDT)
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 wXYg97b16EGr; Wed, 30 Jun 2021 18:31:42 -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 CA2B63A0AEE; Wed, 30 Jun 2021 18:31:42 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A3C8AF40768; Wed, 30 Jun 2021 18:31:23 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9062 on Framework and Requirements for Ethernet VPN (EVPN) Operations, Administration, and Maintenance (OAM)
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: <20210701013123.A3C8AF40768@rfc-editor.org>
Date: Wed, 30 Jun 2021 18:31:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/-CqYUPSQxe_txo5maJ0ooc3vtJo>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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, 01 Jul 2021 01:31:48 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9062
Title: Framework and Requirements for Ethernet VPN (EVPN)
Operations, Administration, and Maintenance (OAM)
Author: S. Salam,
A. Sajassi,
S. Aldrin,
J. Drake,
D. Eastlake 3rd
Status: Informational
Stream: IETF
Date: June 2021
Mailbox: ssalam@cisco.com,
sajassi@cisco.com,
aldrin.ietf@gmail.com,
jdrake@juniper.net,
d3e3e3@gmail.com
Pages: 16
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-bess-evpn-oam-req-frmwk-10.txt
URL: https://www.rfc-editor.org/info/rfc9062
DOI: 10.17487/RFC9062
This document specifies the requirements and reference framework for
Ethernet VPN (EVPN) Operations, Administration, and Maintenance
(OAM). The requirements cover the OAM aspects of EVPN and Provider
Backbone Bridge EVPN (PBB-EVPN). The framework defines the layered
OAM model encompassing the EVPN service layer, network layer,
underlying Packet Switched Network (PSN) transport layer, and link
layer but focuses on the service and network layers.
This document is a product of the BGP Enabled Services Working Group of the IETF.
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