{"id":2005,"date":"2020-01-15T07:49:41","date_gmt":"2020-01-15T04:49:41","guid":{"rendered":"https:\/\/telcocloudbridge.com\/?p=2005"},"modified":"2026-09-21T18:58:55","modified_gmt":"2026-09-21T18:58:55","slug":"mef-70-for-sd-wan-a-cheat-sheet","status":"publish","type":"post","link":"https:\/\/telecomlighthouse.com\/?p=2005","title":{"rendered":"MEF-70 for SD-WAN- A cheat sheet!"},"content":{"rendered":"\n

This guest blog on MEF-70 is written by Anuradha Udunuwara – My friend and a Subject Matter Expert for Carrier Ethernet, SDN, NFV, and SD-WAN.<\/p>\n\n\n\n

……………………………………………………..<\/p>\n\n\n\n

You have probably heard a lot about Software-Defined WAN or SD-WAN.<\/p>\n\n\n\n

So, you may know that It falls within the larger scope of SDx and Software-Defined anything ( if you are new, you can check this video<\/a> to learn more about SDx and SDN) <\/p>\n\n\n\n

Depending on the context, SD-WAN<\/a> could mean a service, technology or an architecture (Just recall \u201cEthernet\u201d \u2013 service (Carrier Ethernet), protocol (Data Link layer), interface etc.). <\/p>\n\n\n\n\n\n\n\n

What is MEF-70 and why so much buzz around it?<\/h3>\n\n\n\n

With MEF 70, MEF is doing the same thing for SD-WAN ( that it did for Carrier Ethernet); taking SD-WAN as a service and define the required attributes supporting the easy adoption, interoperability or as MEF says, define the \u201ccommon language for SD-WAN services<\/a>\u201d. The below from MEF, clearly explains that;<\/p>\n\n\n\n

\u201cMEF\u2019s SD-WAN service definition\nstandard describes requirements<\/strong> for\nan application-aware, over-the-top WAN connectivity service that uses policies\nto determine how application flows are directed over multiple underlay networks\nirrespective of the underlay technologies\nor service providers who deliver them<\/strong>.\u201d<\/em><\/p>\n\n\n\n

MEF-70 is a great milestone by MEF and a big step towards standardizing how a user can get a standard SD-WAN service from a managed SD-WAN service provider. It enables the deployment of SD-WAN with standard service attributes. More importantly, the buyer and seller of service can refer to the same terms, which will lead to service transparency for both service providers and its customers.<\/p>\n\n\n\n

MEF-70 at a high level includes the following two things:<\/p>\n\n\n\n

\"\"
Fig. 01 \u2013 Main contents of the MEF 70 Technical Standard <\/figcaption><\/figure><\/div>\n\n\n\n

What is Service Attribute?<\/h3>\n\n\n\n

MEF Services, such as SD-WAN, are specified using Service Attributes<\/strong>. A Service Attribute captures specific information that is agreed on between the Service Provider<\/strong> (an organization that provides services to Subscribers) and the Subscriber (end-user of service) of a MEF Service, and it describes some aspect of the service behavior. SD-WAN Service Attributes<\/strong> includes the enumeration and description of the information that is agreed between the SD-WAN Subscriber and the SD-WAN Service Provider, <\/em>while SD-WAN Service Framework<\/strong> defines the instances of an SD-WAN Service based on the definitions, service elements, and Service Attributes<\/em><\/p>\n\n\n\n

For easy understanding, the content of MEF 70 can further be divided into two major areas.<\/p>\n\n\n\n

\"what
Fig. 02 \u2013 Main areas covered in MEF 70 Technical Standard <\/figcaption><\/figure><\/div>\n\n\n\n

As you can see, Service Attributes <\/em>is further divided into 3 main areas (small circles);<\/p>\n\n\n\n

  1. SWVC\n(S<\/strong>D-W<\/strong>AN V<\/strong>irtual C<\/strong>onnection) Service Attributes<\/li>
  2.  SWVC EP (SWVC E<\/strong>nd P<\/strong>oint Service\nAttributes<\/li>
  3. SD-WAN\nUNI (SD-WAN U<\/strong>ser N<\/strong>etwork I<\/strong>nterface) Service Attributes<\/li><\/ol>\n\n\n\n

    So Service Attribute is an important part of MEF-70<\/p>\n\n\n\n

    However, before discussing SD-WAN service attributes, it is worthwhile to discuss the basic components of SD-WAN architecture and basic terms like UCS, TVC, application flows and policies ( also described in MEF-70). After discussing these terms, we will return again to service attributes.<\/p>\n\n\n\n

    SD-WAN Service Components Architecture<\/h3>\n\n\n\n

    The following diagram shows the association of the components of an SD-WAN service which are also described below and described in MEF-70. SD-WAN Edge is the customer premises equipment also called SD-WAN CPE.<\/p>\n\n\n\n

    \"SD-WAN
    Fig. 03 \u2013 SD-WAN service components <\/figcaption><\/figure><\/div>\n\n\n\n

    Component 1: SD-WAN Virtual Connection <\/h3>\n\n\n\n

    SWVC or SD-WAN Virtual Connection is an association of SD-WAN Virtual Connection End Points in an SD-WAN Service that provides the logical construct of an L3 Virtual Private Routed Network for a Subscriber. <\/p>\n\n\n\n

    Component 2: SWVC Endpoint<\/h3>\n\n\n\n

    SWVC End Point or SWVC EP is a logical\nconstruct at an SD-WAN UNI that partitions Ingress IP Packets into Application\nFlows, applies a Policy to each IP Packet based on the associated Application\nFlow, and selects an appropriate path to transport the IP Packet over the SWVC.\n<\/p>\n\n\n\n

    Component 3: UNI<\/h3>\n\n\n\n

    SD-WAN UNI or (User Network Interface)\nis the demarcation point between the responsibility of the SD-WAN Service\nProvider and the SD-WAN Subscriber. <\/p>\n\n\n\n

    UCS and TVC-Two important things on which SD-WAN service is constructed<\/h3>\n\n\n\n

    SD-WAN Services operate over Underlay Connectivity Services (UCS). UCSs are network service offerings that provide connectivity between the Subscriber sites. UCSs can include a variety of services including, but not limited to, Ethernet Services (as defined in MEF 6.2), IP Services (as defined in MEF 61.1), L1 Connectivity Services (as defined in MEF 63), and public Internet Services. Access to these UCSs can be via a variety of networking technologies, such as DSL, HFC, LTE, fiber, Wi-Fi, Ethernet, and the transport can be based on Ethernet switching, IP Routing, MPLS, or other technologies. <\/p>\n\n\n\n

    In the Fig. 03 above, if traffic is flowing from Site A to Site B, the Site A SD-WAN UNI<\/em> will become an Ingress SD-WAN UNI and the Site B SD-WAN UNI<\/em> will become an Egress SD-WAN UNI. <\/p>\n\n\n\n

    An SD-WAN Service Provider typically builds point-to-point paths called Tunnel Virtual Connections (TVCs) across UCSs that compose an SD-WAN Service. TVCs define the logical forwarding topology of the SD-WAN Service. Each TVC is built over a single UCS with a well-defined set of characteristics, many of which are inherited from the UCS. To forward each ingress IP packet, SD-WAN Edge has to select a TVC.  By building point-to-point TVCs, a Service Provider creates a virtual topology that can be different from the physical topology of the UCS. For example, if one of the UCS is an EP-LAN service connecting all of the SD-WAN Edges, but the Service Provider only builds TVCs from the Headquarters site to each remote site (and not between the remote sites) then the SD-WAN Service is, effectively, a hub and spoke even though the UCS provides a full mesh.<\/p>\n\n\n\n

    As TVCs are internal to the Service implementation, they do not have Service Attributes. <\/p>\n\n\n\n

    We now move to internet breakout, which is also an important concept and part of MEF-70<\/p>\n\n\n\n

    Internet Breakout<\/h3>\n\n\n\n

    When one or more of the UCSc in the SD-WAN Service is an Internet Service (assume UCS2 above), some Application Flows can be forwarded directly to the Internet without being sent over a TVC delivering to another SD-WAN UNI. This capability is called Internet Breakout<\/strong>.<\/p>\n\n\n\n

    Application Flows and Policies<\/strong> <\/h3>\n\n\n\n

    One of the major characteristics of an SD-WAN service<\/a> is the forwarding of IP Packets across different UCSs with different attributes based on Policies<\/strong> applied to Application Flows<\/strong>. <\/p>\n\n\n\n

    Let\u2019s take an example to understand the Application Flows, Flow Groups, and Policies. Assume there are three Application Flows; strawberry, raspberry and blackberry in the Application Flow Group berries. A Policy can be assigned to the group berries, which becomes the Policy for the three Application Flows. Each Application Flow in the group can nonetheless have an explicit Policy assignment that supersedes the group Policy.<\/p>\n\n\n\n

    Suppose a Policy smoothie is assigned to the berries Application Flow Group at an SWVC EP, then the three listed flows will be forwarded over the SD-WAN using Policy smoothie. However, if at the SWVC EP the Policy pie is assigned to Application Flow strawberry, then raspberry and blackberry will be forwarded using Policy smoothie, and strawberry will be forwarded using Policy pie.<\/p>\n\n\n\n

    After describing the important terms, lets come back to describe the service attributes.<\/p>\n\n\n\n

    SWVC Service Attributes<\/strong> <\/h3>\n\n\n\n

    As identified, this has 3 sections. Let\u2019s look at them one by one.<\/p>\n\n\n\n

    Service Attribute 1: SWVC (S<\/strong>D-W<\/strong>AN V<\/strong>irtual C<\/strong>onnection) Service Attributes <\/h3>\n\n\n\n

    Service Attribute 1: SWVC (S<\/strong>D-W<\/strong>AN V<\/strong>irtual C<\/strong>onnection) Service Attributes<\/p>\n\n\n\n

    As shown in the below diagram, the SWVC Service attribute has further seven sub-attributes. There is one instance of these attributes for each SWVC.<\/p>\n\n\n\n

    \"SWVC
    Fig. 04 \u2013 SWVC Service Attributes <\/figcaption><\/figure>\n\n\n\n

    SWVC List of Policies Service Attribute<\/strong> includes 6 Policy Criterion as described in the below table taken from MEF-70.<\/p>\n\n\n\n

    Table 01 \u2013 Policy Criteria<\/p>\n\n\n\n

    Policy Criteria Name <\/strong><\/td> What does it indicate? <\/strong><\/td><\/tr>
    \n ENCRYPTION\n <\/td>\n Whether or not the Application Flow requires encryption\n <\/td><\/tr>
    \n PUBLIC-PRIVATE\n <\/td>\n Whether the Application Flow can traverse Public or Private UCS (or\n both)\n <\/td><\/tr>
    \n INTERNETBREAKOUT\n <\/td>\n Whether the Application Flow should be forwarded to an Internet\n destination\n <\/td><\/tr>
    \n BILLING-METHOD\n <\/td>\n Whether the Application Flow can be sent over an UCS that has usage-based\n or flat-rate billing\n <\/td><\/tr>
    \n BACKUP\n <\/td>\n Whether this Application Flow can use a TVC designated as\n \u201cbackup\u201d\n <\/td><\/tr>
    \n BANDWIDTH\n <\/td>\n Specifies a rate limit on the Application Flow\n <\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Even though\nMEF 70 defines the above Policy Criteria, the Service Provider, if required can\nhave its own additional criterion defined by them.<\/p>\n\n\n\n

    Application Flows that can be recognized by the SD-WAN service and information about how to identify IP Packets in each Application Flowis specified by the SWVC List of Application Flows Service Attribute. MEF 70 defines 15 Application Flow Criteria that can be used to describe Application Flows.<\/p>\n\n\n\n

    Service Attribute 2: SWVC EP Service Attributes <\/h3>\n\n\n\n

    As described in Fig. 03, SWVC EP is the\nconstruct that represents the attachment of an SWVC to a UNI. The SWVC EP\nprovides a container for attributes of the SWVC that can differ at each UNI.\nThere are 3 attributes defined by MEF 70 as below.<\/p>\n\n\n\n

    \"SWVC
    Fig. 05 – SWVC End Point Service Attributes <\/figcaption><\/figure><\/div>\n\n\n\n

    Fig. 05 – SWVC End Point Service Attributes<\/p>\n\n\n\n

    Service Attribute 3: UNI (U<\/strong>ser N<\/strong>etwork I<\/strong>nterface) Service Attributes <\/h3>\n\n\n\n

    At any given UNI there is only a single Subscriber and a single Service Provider.  MEF 70 defines 5 SD-WAN UNI Service Attributes (shown in the below diagram). SD-WAN Service delivers IP packets between multiple Subscriber Network locations. Therefore, if you carefully see, you can identify that most of the attributes are adapted from the UNI Services Attributes and UNI Access Link Service Attributes section of the MEF Service Attributes for Subscriber IP Services Technical Specification (MEF 61.1). This has been done to achieve the commonality between MEF IP Services and MEF SD-WAN Services. <\/p>\n\n\n\n

    \"SD-WAN
    Fig. 06 – SD-WAN UNI Service Attributes <\/figcaption><\/figure><\/div>\n\n\n\n

    <\/p>\n\n\n\n

    That\u2019s my answer to the question What is MEF 70<\/em> and a brief cheat sheet. If you have any questions or comments, I\u2019m happy to answer them. <\/p>\n\n\n\n

    If\nyou are interested about updating your knowledge in general and on digital,\ndigital technologies, digital disruptions and digital marketing in particular,\nyou can check ARC Tube \u2013 The Knowledge Spark<\/a> .<\/p>\n\n\n\n

    Anuradha Udunuwara, ARC Tube<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

    This guest blog on MEF-70 is written by Anuradha Udunuwara – My friend and a Subject Matter Expert for Carrier Ethernet, SDN, NFV, and SD-WAN. …………………………………………………….. You have probably heard a lot about Software-Defined WAN or SD-WAN. So, you may know that It falls within the larger scope of SDx and Software-Defined anything ( if […]<\/p>\n","protected":false},"author":2,"featured_media":2018,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[],"class_list":["post-2005","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sd-wan"],"_links":{"self":[{"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/posts\/2005","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2005"}],"version-history":[{"count":1,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/posts\/2005\/revisions"}],"predecessor-version":[{"id":3645,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/posts\/2005\/revisions\/3645"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/media\/2018"}],"wp:attachment":[{"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2005"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2005"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2005"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}