MEF9 UNI接口以太网服务抽象测试套件：E-Line/E-LAN功能详解

需积分: 9 153 浏览量更新于2024-07-17 收藏 456KB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

MEF9是 Metro Ethernet Forum (MEF) 发布的一项重要规范，专注于在统一网络接口（UNI）上对以太网服务进行测试。该规范建立在MEF6的基础之上，后者定义了与以太网业务相关的术语和标准。MEF9测试套件的主要目标是确保设备和服务提供商能够在UNI端点提供高质量、一致的E-Line（点到点连接）和E-LAN（多点到多点连接）业务。在MEF9中，测试覆盖的关键方面包括但不限于以下几个部分： 1. 服务功能验证：这套测试旨在验证设备是否能正确实现MEF6定义的以太网业务模型，如带宽保障、服务质量(QoS)控制、链路保护和恢复等。这确保了服务的稳定性和可靠性。 2. 协议一致性：测试涵盖了不同厂商设备间的协议一致性，保证了不同供应商的产品在UNI接口上的互操作性。 3. 性能指标：测试涉及吞吐量、延迟、丢包率等关键性能参数，以衡量设备在高负载下的性能表现。 4. 管理框架支持：MEF9还关注了对于ASON (ASON 控制平面) 和OAM (Operation, Administration, and Maintenance) 的支持，这些都是现代以太网服务管理的重要组成部分。 5. 可扩展性和灵活性：测试涵盖新特性如SDN (Software-Defined Networking) 和NFV (Network Function Virtualization) 的兼容性，以适应不断演进的网络技术环境。 6. 文档和报告合规性：用户被授权修改文档中的信息，但必须包含MEF的版权声明，并且复制时需注明许可。 MEF9 Abstract Test Suite 的发布日期是2004年10月，这意味着它反映了当时的业界最佳实践和标准。然而，由于技术的快速发展，这些测试可能会定期更新，以适应新的技术趋势和标准变迁。因此，使用MEF9时，需要确保遵循最新的测试指南和更新，以保持网络服务的高效和合规。同时，MEF本身并不承担更新或纠正文档内容的责任，用户应自行检查最新的技术发展和安全威胁。

资源详情

资源推荐

Abstract Test Suite For Ethernet Services at the UNI

MEF 9

the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this

document is authorized to modify any of the information contained herein.

Page 3

3. Scope

This document defines the requirements and corresponding test procedures to qualify the ability of a

Metro Ethernet Network to deliver Ethernet services, such as E-Line and E-LAN services as defined

by the Metro Ethernet Forum. The tests are defined from the point of view of the Subscriber’s

equipment that is used to access the services. The goals of the test definitions are three-fold. The first

goal is to provide test procedures to Subscribers to help them ensure the successful integration of

Ethernet Services into their overall networking infrastructures. The second goal is to provide test

definitions to host, switch, and router vendors allowing them to ensure that their products can be used

in the MEN to allow Subscribers to successfully access Ethernet Services. The third is to provide

Service Providers with a suite of tests that allow them to determine the ability of the MEN to offer

Ethernet Services conformant to Metro Ethernet Forum specifications. The requirements defined in

this document are based on Sections 6 and 7 of the Metro Ethernet Forum Technical Committee

Ethernet Services Model document [Ethernet Services Model]. Requirements and test procedures to

qualify the readiness of a MEN to support further services, attributes and parameters will be defined in

subsequent revisions.

This document does not define methods for the measurement or monitoring of Service Level

Specifications (SLSs) but it does define test procedures which determine the readiness of a MEN to

deliver various SLSs defined in [Traffic and Performance Parameters for Ethernet Service Level

Specifications]. This document does not re-define metrics or testing methods described in any of the

standards documents already defined by such groups as the Benchmarking Methodology Working

Group (BMWG) of the Internet Engineering Task Force (IETF), however metrics used in this

document conform to BMWG definitions.

Implementation specifications are outside the scope of this document. This document may be updated

in the future to reflect new work in the MEF Technical Committee.

4. Compliance Levels

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”,

“SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be

interpreted as described in RFC 2119. All key words MUST be use upper case, bold text.

5. Introduction

This document describes the requirements and corresponding test procedures to be used when testing

the ability of a MEN to deliver Ethernet Services, such as the E-Line and E-LAN services defined in

[Ethernet Services Definitions]. Vendors can refer to such requirements and test procedures in the

development and commercial cycles of their products, carriers can use them to ensure that the devices

or systems they select to deploy in the MEN will result in the successful delivery of Ethernet Services

and subscribers can attach to the MEN knowing that the Ethernet services they access satisfy criteria

based on accepted requirements and test procedures.

Abstract Test Suite For Ethernet Services at the UNI

MEF 9

the following statement: "Reproduced with permission of the Metro Ethernet Forum." No user of this

document is authorized to modify any of the information contained herein.

Page 4

The definition of the requirements a MEN must satisfy to deliver Metro Ethernet services is tightly

based on the MEF 1 [Ethernet Services Model], [Ethernet Services Definitions] and [Traffic and

Performance Definitions] documents of the Technical Committee of the Metro Ethernet Forum. The

Ethernet Service Definition Framework was created by the Metro Ethernet Forum (MEF) to provide

the service attributes and parameters to create an Ethernet service. The relationship between this

document and the three MEF services documents is illustrated in Figure 1.

Figure 1: Relationship between different MEF Services Group documents and the Ethernet

Services Test Definition document

Various types of criteria can be used to establish the requirements a MEN must satisfy to deliver

Ethernet services. This document refers to four such criteria: functional, conformance, interoperability

and performance.

Functional criteria: A MEN will have to satisfy certain well-defined functional criteria some of which

can be safely taken for granted and others which it will be useful to test. An example of the latter

would be that a MEN correctly filters BPDUs (Bridge Protocol Data Units) when configured to do so.

Conformance criteria: A MEN must also satisfy certain well-defined conformance criteria. An example

of this is that a MEN MUST NOT deliver frames to the UNI on which they originated

Interoperability criteria: A further criteria is interoperability. An example of this would be the ability of

a device to participate in the same arbitrary MEN as the device of another vendor or, more generally,

of other vendors.

Performance criteria

Functional, conformance and interoperability test results are typically reported as ‘pass’ or ‘fail’,

whereas performance test results are generally reported in terms of frame counts, such as numbers of

lost frames; times, such as mean time to recover in milliseconds; and rates, such as frames per second

forwarding rates.

: A MEN must also meet certain performance criteria. An example of this would

be the ability to successfully forward a certain percentile of frames without loss.

剩余39页未读，继续阅读

book66

粉丝: 0
资源: 3

MEF9 UNI接口以太网服务抽象测试套件：E-Line/E-LAN功能详解

MEF18 Abstract Test Suite for Circuit Emulation Services

MEF14 Abstract Test Suite for Traffic Management Phase 1

mef 带参数构造函数

作者介绍了相关背景,及spd-mef算法的优势,首先,spd-mef生成的加权图没有噪声。因

winform mef加载其它项目界面 demo

MEF的prism框架模块化开发

.net core MEF

eCPRI中MEF指的是什么

MEF如何实现插件式管理，相应的例子讲解下

c# caliburn.micro mef 插件

.net core 热更新

visual studio扩展

生成对抗网络加注意力机制

我想找图像融合的banchmark

PartCreationPolicy特性

C#WPF MVVM进销存

WPF中Caliburn.Micro框架

densefuse复现

写一篇有关lncRNA调控猪骨骼肌生长的综述

Awesome_mixins-0.4-py2-none-any.whl.zip

最新资源