| Internet-Draft | Saas Path Metric | October 2023 |
| Sheng, et al. | Expires 25 April 2024 | [Page] |
This document extends BGP to advertise the SaaS path performance metrics from the gateway sites to branch sites. The user can access SaaS applications through the DIA (Direct Internet Access) link at the branch site or through the DIA link at the gateway site, or use the DIA link of a gateway site for redundancy. This approach will improve the SaaS access experience for end-users.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 25 April 2024.¶
Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
With the continuous cloudification of enterprise IT architectures and widespread use of public clouds, more and more enterprises are turning their infrastructures (such as enterprise data centers) to cloudification, abandoning traditional closed IT architectures and using open network architectures. To further achieve this goal, enterprises' mission-critical applications, such as office, production ERP systems, and sales systems, are migrated to the cloud. In this case, enterprises increasingly rely on software as a service (SaaS) provided by application service providers and prefer to access mission-critical applications from the cloud over the Internet.¶
Accessing SaaS applications like SalesForce, SharePoint, Dropbox and Office 365 over congested public networks can be unreliable and slow, due to heavy traffic, packet loss, and fluctuating latencies. Application slowness results in poor end-user experience.¶
This document provides a way to improve the SaaS access experience. As shown in the Figure 1, user can access SaaS applications through the DIA (Direct Internet Access) link at the branch site or through the DIA link at the gateway site. The GWs at the gateway site normally have stronger capabilities and will provide SaaS access services for branch sites. The CPE at the branch site need to choose the best path for each SaaS application. The performance of the path between gateway and SaaS application needs to be advertised to CPE. This document extends BGP to advertise the SaaS path performance metrics.¶
(^^^^^^^^^^^^^^^^^^^^^^^)
( SaaS Apps )
( +----+ +----+ +----+ )
( |App1| |App2| |App3| )
( +----+ +----+ +----+ )
(^^^^^^^^^^^^^^^^^^^^^^^)
| | |
| | |
| .|----|
| ( | |)
.-|( | | )--.
+-----(--+Internet/MPLS )
/ '--( | | )--'
/ ( | \)
/ '|----'\
+ | +----|-----------+
DIA | Link \ | +--|--+ |
| +-------------\--| GW2 | |
| / SD-WAN Tunnel \ +-----+ |
| / |\ Hub Site|
+----+ +-|/-+ SD-WAN Tunnel | \-----+ |
|User|--|CPE1|-----------------| GW1 | |
+----+ +----+ | +-----+ |
Branch Site +----------------+
In addition to terms defined in [I-D.ietf-idr-sdwan-edge-discovery], this document uses following terms:¶
DIA: Direct Internet Access¶
FQDN: Fully Qualified Domain Name¶
QoS: Quality of Service¶
SaaS: Software-as-a-Service¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
This section uses the scenario shown in Figure 1 as an example to describe how to implement the SaaS Path Optimization solution.¶
Both the Branch and GW routers initiate periodic probes to target SaaS applications. The GW routers advertise the probe result to the Branch routers. The following figure shows the SaaS Path Performance Metrics table on the CPE1. Note that in this example, CPE1, GW1, and GW2 have multiple paths for accessing App1, 2 paths are listed for each device. The access to App2 and App3 is similar, only one entry is listed for the purpose of simplifying the description.¶
+----+--+-----+---------------+-----+------+---+---+---+---+-----+ |Name|ID|Path |Path Out Intf |O_QoS|Status| L | D | J | B |F_QoS| | | |Index|(# Remote) | | | | | | | | +----+--+-----+---------------+-----+------+---+---+---+---+-----+ |App1|10| I11 | GE 0/0/1.1 | 75 | Good | 1|150| 40|B01| 75 | +----+--+-----+---------------+-----+------+---+---+---+---+-----+ |App1|10| I12 | GE 0/0/1.1 | 80 | Good | 1|160| 40|B01| 80 | +----+--+-----+---------------+-----+------+---+---+---+---+-----+ |App1|10| I13 |# GW1-System IP| 85 | Good | 0|100| 40|B11| 83 | +----+--+-----+---------------+-----+------+---+---+---+---+-----+ |App1|10| I14 |# GW1-System IP| 85 | Good | 0|100| 40|B12| 81 | +----+--+-----+---------------+-----+------+---+---+---+---+-----+ |App1|10| I15 |# GW2-System IP| 90 | Best | 0| 80| 20|B13| 82 | +----+--+-----+---------------+-----+------+---+---+---+---+-----+ |App1|10| I16 |# GW2-System IP| 90 | Best | 0| 80| 20|B14| 88 | +----+--+-----+---------------+-----+------+---+---+---+---+-----+ |App2|20| I02 | GE 0/0/1.1 | 40 |Issue | 5|180|101|B02| 40 | +----+--+-----+---------------+-----+------+---+---+---+---+-----+ |App2|20| I21 |# GW1-System IP| 80 | Good | 1|100| 70|B21| 75 | +----+--+-----+---------------+-----+------+---+---+---+---+-----+ |App2|20| I22 |# GW2-System IP| 60 | Acct | 3|160| 80|B22| 55 | +----+--+-----+---------------+-----+------+---+---+---+---+-----+ |App3|30| I03 | GE 0/0/1.1 | 90 | Best | 0| 58| 20|B03| 90 | +----+--+-----+---------------+-----+------+---+---+---+---+-----+ |App3|30| I31 |# GW1-System IP| 80 | Good | 0| 65| 30|B31| 78 | +----+--+-----+---------------+-----+------+---+---+---+---+-----+ |App3|30| I32 |# GW2-System IP| 75 | Acct | 2|130| 90|B32| 72 | +----+--+-----+---------------+-----+------+---+---+---+---+-----+ L: Loss D: Delay J: Jitter B: Bandwidth Acct: Acceptable O_QoS: Original QoS F_QoS: Final QoS
Upon receiving the QoS score from the GW router, CPE1 will calculates the Final QoS score based on the SD-WAN tunnel status and and the received QoS score. When a user of CPE1 accesses a SaaS applications, CPE1 determines the best performing path toward the SaaS application based on the Final QoS score (F_QoS).¶
For example If App1 is the target SaaS Application, select the SaaS path that passes through GW2 with the Path Index I16 because it has the highest score: 88. If App2 is the target SaaS Application, select the SaaS path that passes through GW1 with the Path Index I21 because it has the highest score: 75. If App3 is the target SaaS application, select the local SaaS path with the Path Index I03 because it has the highest score: 90.¶
The BGP SD-WAN NLRI as defined in [I-D.ietf-idr-sdwan-edge-discovery] is shown below:¶
+-----------------------------------+ | Route Type (2 octets) | +-----------------------------------+ | Length (2 octets) | +-----------------------------------+ ~ ~ | Type Specific Value (variable) | ~ ~ +-----------------------------------+
Where:¶
Route (NLRI) Type: 2 octet value to define the encoding of the rest of the SD-WAN NLRI.¶
Length: 2 octets of length expressed in bits as defined in [RFC4760].¶
This document defines an additional route type to be used for the advertisement of the SaaS Path Performance Metrics between different enterprise sites:¶
+--------------------+ | Route Type = 2 | 2 octets +--------------------+ | Length | 2 octets +--------------------+ | Site ID | 4 octets +--------------------+ | APP ID | 4 octets +--------------------+ | APP Req | 1 octet +--------------------+ | Path Index Type | 1 octet +--------------------+ | Path Index Value | 3 or 4 or 16 octets +--------------------+ | SD-WAN-Node-ID | 4 or 16 octets +--------------------+
Where:¶
Route Type: 2, SaaS Path Performance Route¶
Length: 2 octets of length expressed in bits as defined in [RFC4760].¶
Site ID: 4 octets, A site ID is a unique identifier of an enterprise site in the SD-WAN network.¶
APP ID: 4 octets, SaaS Application ID, a unique Application ID to identify different applications. Application may be deployed using different IP address in different area. Thus an ID is needed to identify the application.¶
APP Req: 1 octet, Application requirement to indicate the application requirement of the path quality. For example, an real time video conferencing application requires higher quality than a background file backup application. The value includes:¶
Path Index Type: Indicates the type of the path index.¶
Path Index Value: a Path Index Type specific Value:¶
Type 1, the Path Index Value is a 4-byte local index value, which is used to identify an outbound interface for accessing SaaS applications.¶
Type 2, the Path Index Value is a 3-byte MPLS label, which is used to identify an outbound interface for accessing the SaaS application.¶
Type 3, The Path Index Value is a 16-byte SRv6 SID, which is used to identify an outbound interface for accessing a SaaS application, and its Endpoint Behavior is End.DT2SaaSPath: Decapsulate SRv6 packet, then send the packet to the target SaaS application from the outbound interface indicated by the SRv6 SID.¶
SD-WAN Node ID: The node's IPv4 or IPv6 address.¶
The Metadata Path Attribute has been as defined in [I-D.ietf-idr-5g-edge-service-metadata]. This document introduces some additional Sub-TLVs to encode the SaaS Path Performance Metrics and SaaS Application Information.¶
Another option is to use the above Sub-TLVs in the Tunnel Encapsulation Attribute [RFC9012]. In this option, the tunnel type "SaaS Application Path Performance" is added.¶
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delay Sub-Type = TBD1 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delay |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where:¶
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Loss Sub-Type = TBD2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Loss |
+-+-+-+-+-+-+-+-+
Where:¶
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Jitter Sub-Type = TBD3 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Jitter |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where:¶
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bandwidth Sub-Type = TBD4 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bandwidth |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where:¶
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status Sub-Type = TBD5 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status |
+-+-+-+-+-+-+-+-+
Where:¶
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS Sub-Type = TBD6 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| QoS |
+-+-+-+-+-+-+-+-+
Where:¶
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SaaS AppName Sub-Type = TBD7 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ ~
| Application Name (1-n Octets) |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where:¶
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AppDomainName Sub-Type = TBD8 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ ~
| Application Domain Name (Variable) |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where:¶
TBD.¶
Shunwan Zhuang Huawei Email: zhuangshunwan@huawei.com¶
Penghe Tang Huawei Technologies Email: tangpenghe@huawei.com@huawei.com¶