API Catalog

Service Specification schema of L1 Subscriber Virtual Connection A subscriber L1VC represents the logical attachment of a Subscriber L1VC to two SubscriberL1VCEndPoint. Reference MEF 63 Section 8.2.

SdWanUni is a resource that represents the boundary between the responsibility of the Subscriber and the responsibility of the Service Provider. Reference MEF 70.2, Section 7.4 SD-WAN UNI.

An association of SD-WAN Virtual Connection End Points in an SD-WAN Service that provides the logical construct of a L3 Virtual Private Routed Network for a Subscriber. SwVc is a resource that represents a SD-WAN Virtual Connection. Reference MEF 70.2 Section 9 SD-WAN Virtual Connection (SWVC) Service Attribute.

The SwVcEndPoint is the construct that represents the attachment of an SWVC to a UNI. The SwVcEndPoint provides a container for attributes of the SWVC that can differ at each UNI. Reference MEF 70.2 Section 10 SD-WAN Virtual Connection (SWVC) End Point. Service Attributes.

Underlay Connectivity Services are network services independent of the SD-WAN Service and can have a large number of "characteristics" or "attributes" that define their configuration and behavior. Reference MEF 70.2, Section 12.1 UCS Service Attributes

A UCS is connected to a UCS UNI by a UCS End Point. Some service architectures support multiple UCSs at the same UCS UNI. The UCS End Point captures Service Attributes at the UCS UNI whose value can differ between UCSs. Reference MEF 70.1 Section 14 UCS End Point Service Attributes.

Access to an Underlay Connectivity Service is provided at the SD-WAN Edge via the UCS UNI. Reference MEF W70.2 Section 12.2 SD-WAN UCS UNI Service Attributes.

Product Specification schema of Cross Connection Type-0

• A Type-0 Cross-Connection MUST transport the signal received at the ingress External Interface transparently (i.e., bit identical) to the egress External Interface.
• For a Type-0 Cross-Connection the values of the CableType parameters of the Cross-Connection External Interface Type Service Attribute MUST be the same at each Cross [...]

Product Specification schema of Cross Connection Type-1 A Type-1 Cross-Connection MUST terminate the incoming signal (received from the ingress External Interface) below the PCS layer, pass the PCS codewords transparently (i.e., bit identical), and source another PHY below the PCS layer to the egress External Interface.

This file forms part of MEF W116 LSO Cantata and LSO Sonata Product Inventory API

This specification represents MEF work in progress and is subject to change.

This API implements Business Requirements that are defined in MEF Standard: MEF 81

It allows the Buyer to retrieve the information about existing Product instances from Seller's Product Inventory.

Supported use cases:

• [...]

Product Specification schema of Layer 2 Cross-Connection A Type-2 Cross-Connection MUST terminate the Ethernet PHY and perform MAC Bridging (i.e., support a MAC Relay Entity) as defined in IEEE 802.1Q

Google Layer 2 Partner Interconnect. This Product is used to model information needed by Service Provider to establish a Layer 2 Partner Interconntect.