| < draft-so-network-aware-application-problem-01.txt | draft-so-network-aware-application-problem-02.txt > | |||
|---|---|---|---|---|
| Network Working Group Ning So (UTD) | Network Working Group Ning So (UTD) | |||
| Internet Draft Young Lee (Huawei) | Internet Draft Young Lee (Huawei) | |||
| Intended status: Informational Dave McDysan (Verizon) | Intended status: Informational Dave McDysan (Verizon) | |||
| Greg Bernstein (Grotto) | Greg Bernstein (Grotto) | |||
| Tae Yeon Kim (ETRI) | Tae Yeon Kim (ETRI) | |||
| Kohei Shiomoto (NTT) | Kohei Shiomoto (NTT) | |||
| Oscar Gonzalez de Dios (Telefonica) | Oscar Gonzalez de Dios (Telefonica) | |||
| October 21, 2010 | April 20, 2011 | |||
| Problem Statement for Network Aware Application Resource Assignment | Problem Statement for Network Aware Application Resource Assignment | |||
| and Mobility (NA-ARAM) in Data Center Environments | and Mobility (NA-ARAM) in Data Center Environments | |||
| draft-so-network-aware-application-problem-01.txt | draft-so-network-aware-application-problem-02.txt | |||
| Status of this Memo | Status of this Memo | |||
| This Internet-Draft is submitted to IETF in full conformance with the | This Internet-Draft is submitted to IETF in full conformance with the | |||
| provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF), its areas, and its working groups. Note that | Task Force (IETF), its areas, and its working groups. Note that | |||
| other groups may also distribute working documents as Internet- | other groups may also distribute working documents as Internet- | |||
| Drafts. | Drafts. | |||
| skipping to change at page 1, line 38 ¶ | skipping to change at page 1, line 38 ¶ | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
| http://www.ietf.org/ietf/1id-abstracts.txt | http://www.ietf.org/ietf/1id-abstracts.txt | |||
| The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
| http://www.ietf.org/shadow.html. | http://www.ietf.org/shadow.html. | |||
| This Internet-Draft will expire on April 21, 2011. | This Internet-Draft will expire on October 20, 2011. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2010 IETF Trust and the persons identified as the | Copyright (c) 2011 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| Internet-Draft Network Aware Application Resource Assignment & Mobility | Internet-Draft Network Aware Application Resource Assignment & Mobility | |||
| October 2010 | ||||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
| to this document. | to this document. | |||
| Abstract | Abstract | |||
| Data Centers offer various application services to end-users such as | Data Centers offer various application services to end-users such as | |||
| skipping to change at page 2, line 34 ¶ | skipping to change at page 2, line 32 ¶ | |||
| and the application resources conditions. | and the application resources conditions. | |||
| Currently such decisions are made with very little or no information | Currently such decisions are made with very little or no information | |||
| concerning the underlying network used to deliver those services. | concerning the underlying network used to deliver those services. | |||
| Hence such decisions are inherently sub-optimal. In addition the lack | Hence such decisions are inherently sub-optimal. In addition the lack | |||
| of network awareness may result in not meeting the end-user | of network awareness may result in not meeting the end-user | |||
| application service objectives. | application service objectives. | |||
| Table of Contents | Table of Contents | |||
| 1. Introduction..................................................3 | 1. Introduction........................................ 3 | |||
| 1.1. Terminology...............................................3 | 1.1. Terminology..................................... 3 | |||
| 2. Network and Application Contexts...............................4 | 2. Network and Application Contexts........................ 4 | |||
| 2.1. Server level load condition...............................6 | 2.1. Server level load condition........................ 6 | |||
| 2.2. Intra-DC network condition................................6 | 2.2. Intra-DC network condition......................... 6 | |||
| 2.3. Carrier MAN/WAN network condition (the networks that connect | 2.3. Carrier MAN/WAN network condition (the networks that connect | |||
| the data centers and connect end users to the data centers)....6 | the data centers and connect end users to the data centers).. 6 | |||
| 2.4. User condition............................................7 | 2.4. User condition................................... 7 | |||
| 3. Problem Statement..............................................7 | 3. Problem Statement .................................... 7 | |||
| 4. High-level requirements........................................8 | 4. High-level requirements................................ 8 | |||
| 4.1. End-User to Application/DC Provider Communication.........9 | 4.1. End-User to Application/DC Provider Communication...... 9 | |||
| 4.2. Inter DC communication....................................9 | 4.2. Inter DC communication............................ 9 | |||
| 4.3. Data Center-Network Stratum Communication (NS Query)......9 | 4.3. Data Center-Network Stratum Communication (NS Query).... 9 | |||
| 4.3.1. Application Profile.................................10 | 4.3.1. Application Profile.......................... 10 | |||
| 4.3.2. Network Load Data to be queried.....................10 | 4.3.2. Network Load Data to be queried................ 10 | |||
| 4.3.3. Responses to NS Query from network to application...11 | 4.3.3. Responses to NS Query from network to application. 11 | |||
| 5. Security Considerations.......................................11 | 5. Security Considerations............................... 11 | |||
| 6. IANA Considerations...........................................11 | 6. IANA Considerations.................................. 11 | |||
| 7. References....................................................11 | 7. References......................................... 11 | |||
| 7.1. Informative References...................................11 | 7.1. Informative References........................... 11 | |||
| Author's Addresses...............................................13 | Author's Addresses..................................... 13 | |||
| Internet-Draft Network Aware Application Resource Assignment & Mobility | Internet-Draft Network Aware Application Resource Assignment & Mobility | |||
| October 2010 | Intellectual Property Statement .......................... 13 | |||
| Disclaimer of Validity.................................. 14 | ||||
| Intellectual Property Statement..................................13 | ||||
| Disclaimer of Validity...........................................14 | ||||
| 1. Introduction | 1. Introduction | |||
| Data Centers offer application services to end-users such as video | Data Centers offer application services to end-users such as video | |||
| gaming [WoWAct], [WoWHrs], [GameServ] and [GroupGame], cloud | gaming [WoWAct], [WoWHrs], [GameServ] and [GroupGame], cloud | |||
| computing [CostCloud], grid application [GFD-122] and others. Many | computing [CostCloud], grid application [GFD-122] and others. Many | |||
| application services offered by Data Center to end-users make | application services offered by Data Center to end-users make | |||
| significant use of the underlying networks resources in the form of | significant use of the underlying networks resources in the form of | |||
| bandwidth consumption used to carry the actual traffic between a data | bandwidth consumption used to carry the actual traffic between a data | |||
| center and the end-users. | center and the end-users. | |||
| skipping to change at page 4, line 6 ¶ | skipping to change at page 4, line 6 ¶ | |||
| 1.1. Terminology | 1.1. Terminology | |||
| This section describes key terminology used in this document. | This section describes key terminology used in this document. | |||
| Application Stratum -- The functional block which manages and | Application Stratum -- The functional block which manages and | |||
| controls application resources and provides application resources to | controls application resources and provides application resources to | |||
| a variety of clients/end-users. | a variety of clients/end-users. | |||
| Internet-Draft Network Aware Application Resource Assignment & Mobility | Internet-Draft Network Aware Application Resource Assignment & Mobility | |||
| October 2010 | ||||
| Application Profile -- The characteristics of the application from a | Application Profile -- The characteristics of the application from a | |||
| network traffic perspective and the QoS requirements that the | network traffic perspective and the QoS requirements that the | |||
| application service will require from the network. | application service will require from the network. | |||
| Application Resources -- Non-network resources critical to achieving | Application Resources -- Non-network resources critical to achieving | |||
| the application service functionality. Examples include: caches, | the application service functionality. Examples include: caches, | |||
| mirrors, application specific servers, content, large data sets, and | mirrors, application specific servers, content, large data sets, and | |||
| computing power. | computing power. | |||
| Application Service -- A networked application offered to a variety | Application Service -- A networked application offered to a variety | |||
| skipping to change at page 5, line 6 ¶ | skipping to change at page 5, line 6 ¶ | |||
| 2. Network and Application Contexts | 2. Network and Application Contexts | |||
| This section discusses the network and application contexts and the | This section discusses the network and application contexts and the | |||
| key components that will help understand problems that will be | key components that will help understand problems that will be | |||
| discussed in the subsequent section. Figure 1 below depicts | discussed in the subsequent section. Figure 1 below depicts | |||
| overarching network and application architecture in which to show the | overarching network and application architecture in which to show the | |||
| key components. | key components. | |||
| Internet-Draft Network Aware Application Resource Assignment & Mobility | Internet-Draft Network Aware Application Resource Assignment & Mobility | |||
| October 2010 | ||||
| ,-----. --------------- | ,-----. --------------- | |||
| ---------- / App \ | DC 1 | | ---------- / App \ | DC 1 | | |||
| | End-user |. . .>( Control ) | o o o | | | End-user |. . .>( Control ) | o o o | | |||
| | | \ / | \|/ | | | | \ / | \|/ | | |||
| ---------- `-----' | O | | ---------- `-----' | O | | |||
| | ----- --|------ | | ----- --|------ | |||
| | | | | | | |||
| | | | | | | |||
| | --------------------------|-- | | --------------------------|-- | |||
| | / PE1 | \ | | / PE1 | \ | |||
| skipping to change at page 6, line 6 ¶ | skipping to change at page 6, line 6 ¶ | |||
| . Carrier Network (access network is not shown for brevity's sake) | . Carrier Network (access network is not shown for brevity's sake) | |||
| There are a number of factors that need be considered in choosing the | There are a number of factors that need be considered in choosing the | |||
| right server in the right data center for an application request or | right server in the right data center for an application request or | |||
| in instantiating new VMs/applications or migrating existing | in instantiating new VMs/applications or migrating existing | |||
| VMs/applications: | VMs/applications: | |||
| . Server level load condition in a data center | . Server level load condition in a data center | |||
| Internet-Draft Network Aware Application Resource Assignment & Mobility | Internet-Draft Network Aware Application Resource Assignment & Mobility | |||
| October 2010 | ||||
| . Intra data center network condition | . Intra data center network condition | |||
| . Carrier MAN/WAN network condition | . Carrier MAN/WAN network condition | |||
| . User Condition | . User Condition | |||
| Details of potential constraining factors for each of the list above | Details of potential constraining factors for each of the list above | |||
| are as follows: | are as follows: | |||
| 2.1. Server level load condition | 2.1. Server level load condition | |||
| skipping to change at page 7, line 6 ¶ | skipping to change at page 7, line 6 ¶ | |||
| data centers and connect end users to the data centers) | data centers and connect end users to the data centers) | |||
| o Type of networks and the technical capabilities of the | o Type of networks and the technical capabilities of the | |||
| networks; | networks; | |||
| o Bandwidth capabilities and availability; | o Bandwidth capabilities and availability; | |||
| o latency; | o latency; | |||
| o jitter; | o jitter; | |||
| o packet loss; | o packet loss; | |||
| Internet-Draft Network Aware Application Resource Assignment & Mobility | Internet-Draft Network Aware Application Resource Assignment & Mobility | |||
| October 2010 | ||||
| o And other Network Performance Objective (NPO) as defined in | o And other Network Performance Objective (NPO) as defined in | |||
| section 5 of [ITU-T Y.1541]. | section 5 of [ITU-T Y.1541]. | |||
| 2.4. User condition | 2.4. User condition | |||
| o User access capabilities and limitations (e.g., user | o User access capabilities and limitations (e.g., user | |||
| terminal information such as codec for video application); | terminal information such as codec for video application); | |||
| o User location; | o User location; | |||
| o Optional user preferences (for some application, user may | o Optional user preferences (for some application, user may | |||
| be able to specify its preferences. For example, the | be able to specify its preferences. For example, the | |||
| skipping to change at page 8, line 6 ¶ | skipping to change at page 8, line 6 ¶ | |||
| providing an optimal decision across multiple VLANs and multiple Data | providing an optimal decision across multiple VLANs and multiple Data | |||
| Centers. This capability is often referred to as global load | Centers. This capability is often referred to as global load | |||
| balancing. | balancing. | |||
| First of all, there is no standard solution for the communication | First of all, there is no standard solution for the communication | |||
| exchange among load balancers located in different Data Centers. This | exchange among load balancers located in different Data Centers. This | |||
| implies that load balancers from different vendors cannot communicate | implies that load balancers from different vendors cannot communicate | |||
| to each other. | to each other. | |||
| Internet-Draft Network Aware Application Resource Assignment & Mobility | Internet-Draft Network Aware Application Resource Assignment & Mobility | |||
| October 2010 | ||||
| Secondly, load balancers know little about the underlying network | Secondly, load balancers know little about the underlying network | |||
| conditions listed in the previous section. Nor is it user condition | conditions listed in the previous section. Nor is it user condition | |||
| aware. | aware. | |||
| In some cases, application controllers can estimate network load | In some cases, application controllers can estimate network load | |||
| based on ping latency, and network topology based on trace routes in | based on ping latency, and network topology based on trace routes in | |||
| the Internet, based on the assumption that the underlying transport | the Internet, based on the assumption that the underlying transport | |||
| network is an IP network, and the routing is based on simple IP | network is an IP network, and the routing is based on simple IP | |||
| forwarding. | forwarding. | |||
| skipping to change at page 9, line 6 ¶ | skipping to change at page 9, line 6 ¶ | |||
| This capability is referred to as Network Stratum Query (NS Query) in | This capability is referred to as Network Stratum Query (NS Query) in | |||
| this document. | this document. | |||
| 4. High-level requirements | 4. High-level requirements | |||
| This section discusses high-level requirements to support network- | This section discusses high-level requirements to support network- | |||
| aware application resource assignment and mobility in the data center | aware application resource assignment and mobility in the data center | |||
| environments. | environments. | |||
| Internet-Draft Network Aware Application Resource Assignment & Mobility | Internet-Draft Network Aware Application Resource Assignment & Mobility | |||
| October 2010 | ||||
| 4.1. End-User to Application/DC Provider Communication | 4.1. End-User to Application/DC Provider Communication | |||
| End-users are the entities that make requests to the Application | End-users are the entities that make requests to the Application | |||
| Controller (aka, global load balancer, or front-end server). As | Controller (aka, global load balancer, or front-end server). As | |||
| Figure 1 shows, the Application Controller interfaces users and makes | Figure 1 shows, the Application Controller interfaces users and makes | |||
| server assignment decision for the user application. Once resources | server assignment decision for the user application. Once resources | |||
| are allocated or made available, they consume application resources | are allocated or made available, they consume application resources | |||
| offered by application/Data Center provider. | offered by application/Data Center provider. | |||
| End-users may communicate several things to the Application | End-users may communicate several things to the Application | |||
| skipping to change at page 10, line 6 ¶ | skipping to change at page 10, line 6 ¶ | |||
| . Intra-DC network conditions defined in Section 2.2 need to be | . Intra-DC network conditions defined in Section 2.2 need to be | |||
| made available to the Application Controller (Global Load | made available to the Application Controller (Global Load | |||
| Balancer) from each of the Data Centers where the application | Balancer) from each of the Data Centers where the application | |||
| servers are located. | servers are located. | |||
| 4.3. Data Center-Network Stratum Communication (NS Query) | 4.3. Data Center-Network Stratum Communication (NS Query) | |||
| The Application Controller plays the key role in choosing the optimal | The Application Controller plays the key role in choosing the optimal | |||
| server for an application request. The Application Controller can | server for an application request. The Application Controller can | |||
| Internet-Draft Network Aware Application Resource Assignment & Mobility | Internet-Draft Network Aware Application Resource Assignment & Mobility | |||
| October 2010 | ||||
| interface with an application gateway that interfaces with network | interface with an application gateway that interfaces with network | |||
| and runs NS Query. The details of NS Query are addressed in a | and runs NS Query. The details of NS Query are addressed in a | |||
| separate draft [NS Query]. | separate draft [NS Query]. | |||
| 4.3.1. Application Profile | 4.3.1. Application Profile | |||
| The application Stratum needs to provide the application profile to | The application Stratum needs to provide the application profile to | |||
| network. | network. | |||
| Example service profile information that can be useful to network to | Example service profile information that can be useful to network to | |||
| understand is as follows: | understand is as follows: | |||
| skipping to change at page 11, line 6 ¶ | skipping to change at page 11, line 6 ¶ | |||
| Note that this can be asked in a different way. For example, the | Note that this can be asked in a different way. For example, the | |||
| query can simply ask: | query can simply ask: | |||
| . Can you route x amount of b/w (in a particular point in network) | . Can you route x amount of b/w (in a particular point in network) | |||
| within y ms of latency? | within y ms of latency? | |||
| . Can you route x amount of b/w (in a particular point in network) | . Can you route x amount of b/w (in a particular point in network) | |||
| with no packet loss? | with no packet loss? | |||
| Internet-Draft Network Aware Application Resource Assignment & Mobility | Internet-Draft Network Aware Application Resource Assignment & Mobility | |||
| October 2010 | ||||
| 4.3.3. Responses to NS Query from network to application | 4.3.3. Responses to NS Query from network to application | |||
| Upon receiving the network query from application, the network should | Upon receiving the network query from application, the network should | |||
| be able to perform the following functions: | be able to perform the following functions: | |||
| . Using the given location mapping information (e.g., the server | . Using the given location mapping information (e.g., the server | |||
| location and the end-user location or a set of server locations | location and the end-user location or a set of server locations | |||
| in different data centers), the network should be able to derive | in different data centers), the network should be able to derive | |||
| its network condition data. | its network condition data. | |||
| skipping to change at page 12, line 6 ¶ | skipping to change at page 12, line 6 ¶ | |||
| for the Simple Network Management Protocol (SNMP)," | for the Simple Network Management Protocol (SNMP)," | |||
| January, 1998. | January, 1998. | |||
| [Y.2011] General principles and general reference model for Next | [Y.2011] General principles and general reference model for Next | |||
| Generation Networks, October, 2004. | Generation Networks, October, 2004. | |||
| [Y.2012] Functional Requirements and architecture of the NGN, April, | [Y.2012] Functional Requirements and architecture of the NGN, April, | |||
| 2010. | 2010. | |||
| Internet-Draft Network Aware Application Resource Assignment & Mobility | Internet-Draft Network Aware Application Resource Assignment & Mobility | |||
| October 2010 | ||||
| [GameServ]P. Quax, J. Dierckx, B. Cornelissen, G. Vansichem, and W. | [GameServ]P. Quax, J. Dierckx, B. Cornelissen, G. Vansichem, and W. | |||
| Lamotte, "Dynamic server allocation in a real-life | Lamotte, "Dynamic server allocation in a real-life | |||
| deployable communications architecture for networked | deployable communications architecture for networked | |||
| games," Proceedings of the 7th ACM SIGCOMM Workshop on | games," Proceedings of the 7th ACM SIGCOMM Workshop on | |||
| Network and System Support for Games, Worcester, | Network and System Support for Games, Worcester, | |||
| Massachusetts: ACM, 2008, pp. 66-71. | Massachusetts: ACM, 2008, pp. 66-71. | |||
| [GroupGame] K. Vik, C. Griwodz, and P. Halvorsen, "Applicability of | [GroupGame] K. Vik, C. Griwodz, and P. Halvorsen, "Applicability of | |||
| group communication for increased scalability in MMOGs," | group communication for increased scalability in MMOGs," | |||
| skipping to change at page 13, line 6 ¶ | skipping to change at page 13, line 6 ¶ | |||
| networks," ACM SIGCOMM, Vol. 39, Number1, January 2009. | networks," ACM SIGCOMM, Vol. 39, Number1, January 2009. | |||
| [NS Query] Y. Lee, et. al., "Problem Statement for Network Stratum | [NS Query] Y. Lee, et. al., "Problem Statement for Network Stratum | |||
| Query," draft-lee-network-stratum-query-problem, work in | Query," draft-lee-network-stratum-query-problem, work in | |||
| progress. | progress. | |||
| [Y.1541] Network performance objectives for IP-based services, | [Y.1541] Network performance objectives for IP-based services, | |||
| February, 2002. | February, 2002. | |||
| Internet-Draft Network Aware Application Resource Assignment & Mobility | Internet-Draft Network Aware Application Resource Assignment & Mobility | |||
| October 2010 | ||||
| Author's Addresses | Author's Addresses | |||
| Ning So (Editor) | Ning So (Editor) | |||
| Univerity of Texas at Dallas | Univerity of Texas at Dallas | |||
| Email: ningso@yahoo.com | Email: ningso@yahoo.com | |||
| Young Lee (Editor) | Young Lee (Editor) | |||
| Huawei Technologies | Huawei Technologies | |||
| 1700 Alma Drive, Suite 500 | 1700 Alma Drive, Suite 500 | |||
| skipping to change at page 14, line 6 ¶ | skipping to change at page 14, line 6 ¶ | |||
| Intellectual Property Statement | Intellectual Property Statement | |||
| The IETF Trust takes no position regarding the validity or scope of | The IETF Trust takes no position regarding the validity or scope of | |||
| any Intellectual Property Rights or other rights that might be | any Intellectual Property Rights or other rights that might be | |||
| claimed to pertain to the implementation or use of the technology | claimed to pertain to the implementation or use of the technology | |||
| described in any IETF Document or the extent to which any license | described in any IETF Document or the extent to which any license | |||
| under such rights might or might not be available; nor does it | under such rights might or might not be available; nor does it | |||
| Internet-Draft Network Aware Application Resource Assignment & Mobility | Internet-Draft Network Aware Application Resource Assignment & Mobility | |||
| October 2010 | ||||
| represent that it has made any independent effort to identify any | represent that it has made any independent effort to identify any | |||
| such rights. | such rights. | |||
| Copies of Intellectual Property disclosures made to the IETF | Copies of Intellectual Property disclosures made to the IETF | |||
| Secretariat and any assurances of licenses to be made available, or | Secretariat and any assurances of licenses to be made available, or | |||
| the result of an attempt made to obtain a general license or | the result of an attempt made to obtain a general license or | |||
| permission for the use of such proprietary rights by implementers or | permission for the use of such proprietary rights by implementers or | |||
| users of this specification can be obtained from the IETF on-line IPR | users of this specification can be obtained from the IETF on-line IPR | |||
| repository at http://www.ietf.org/ipr | repository at http://www.ietf.org/ipr | |||
| End of changes. 19 change blocks. | ||||
| 48 lines changed or deleted | 26 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||