idnits 2.17.1 draft-wu-alto-endpoint-pid-properties-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([I-D.ietf-alto-protocol]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (January 27, 2014) is 3735 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'I-D.ietf-alto-protocol' is mentioned on line 101, but not defined == Outdated reference: A later version (-27) exists of draft-ietf-alto-protocol-16 Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ALTO working group Q. Wu 3 Internet-Draft Huawei 4 Intended status: Standards Track Z. Cao 5 Expires: July 31, 2014 China Mobile 6 January 27, 2014 8 Endpoint and PID Property Extension for virtualized endpoint and 9 infrastructure 10 draft-wu-alto-endpoint-pid-properties-00 12 Abstract 14 This document extends the Application-Layer Traffic Optimization 15 (ALTO) protocol [I-D.ietf-alto-protocol] and Proposes additional new 16 Endpoint properties and PID properties for virtualized endpoint and 17 infrastructure. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on July 31, 2014. 36 Copyright Notice 38 Copyright (c) 2014 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. Conventions used in this document . . . . . . . . . . . . . . 4 55 3. PID properties . . . . . . . . . . . . . . . . . . . . . . . . 5 56 3.1. PID Property Type: resourcetype . . . . . . . . . . . . . 5 57 3.2. PID Property Type: servingload . . . . . . . . . . . . . . 5 58 3.3. PID Property Type: supportedcapacity . . . . . . . . . . . 5 59 3.4. PID Property Type: availcapacity . . . . . . . . . . . . . 5 60 4. Endpoint Properties Extension . . . . . . . . . . . . . . . . 6 61 4.1. Endpoint Property Type: nodetype . . . . . . . . . . . . . 6 62 4.2. Endpoint Property Type: servicetype . . . . . . . . . . . 6 63 4.3. Endpoint Property Type: forwarding class . . . . . . . . . 6 64 4.4. Endpoint Property Type: Packetrateutilization . . . . . . 6 65 4.5. Endpoint Property Type: bandwidthutilization . . . . . . . 6 66 4.6. Endpoint Property Type: memoryutilization . . . . . . . . 7 67 4.7. Endpoint Property Type: availablememory . . . . . . . . . 7 68 4.8. Endpoint Property Type: ributilization . . . . . . . . . . 7 69 4.9. Endpoint Property Type: fibutilization . . . . . . . . . . 7 70 4.10. Endpoint Property Type: cpuutilization . . . . . . . . . . 7 71 4.11. Endpoint Property Type: availablestorage . . . . . . . . . 7 72 4.12. Endpoint Property Type: supportedaclnum . . . . . . . . . 7 73 4.13. Endpoint Property Type: virtualcontextnum . . . . . . . . 8 74 4.14. Endpoint Property Type: supportedpacketrate . . . . . . . 8 75 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 76 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 77 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 78 7.1. Normative References . . . . . . . . . . . . . . . . . . . 11 79 7.2. Informative References . . . . . . . . . . . . . . . . . . 11 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 82 1. Introduction 84 As stated in [I-D.ietf-alto-protocol], an Endpoint is an application 85 or host that is capable of communicating (sending and/or receiving 86 messages) on a network. An Endpoint is typically either a Resource 87 Provider or Resource Consumer. 89 With the growth of network virtualization technology, steering 90 traffic through specific services nodes at different layers or 91 bypassing them completely becomes important. A service node may be 92 running in its own virtualized system space or physically separated 93 across hosting systems. The information provided about these service 94 nodes includes service network location (for topology creation), 95 service type (e.g. firewall, load balancer, etc.) and, optionally, 96 administrative information about the service functions such as load, 97 capacity and operating status. To facilitate alto service discovery 98 for these service node information, the endpoint properties and cost 99 needs to be extended. 101 As stated in [I-D.ietf-alto-protocol], Provider-defined Identifiers 102 (PIDs) is introduced to provide an indirect and network-agnostic way 103 to specify an aggregation of network endpoints that may be treated 104 similarly, based on network topology, type, or other properties. 105 When network endpoints are aggregated at Data Center level, the 106 information provided by a data center include administrative 107 information such as load, capacity, operating status. 109 This document proposes extending the property concept by allowing 110 PIDs to have properties. 112 2. Conventions used in this document 114 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 115 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 116 document are to be interpreted as described in RFC2119 [RFC2119]. 118 3. PID properties 120 The ALTO base protocol defines endpoint property in the form of 121 (name, value) pair associated with the selected endpoint address, 122 e.g., pid. But it doesn't define any property for PID. However it 123 can be useful to report an data center's load, capacity, operating 124 status when network endpoints are aggregated at Data Center level. 125 This document define x new PID properties for virtualized 126 infrastructure to support service topologies creation and service 127 node discovery. 129 3.1. PID Property Type: resourcetype 131 An ALTO Server MAY define the 'resourcetype' Endpoint Property Type 132 for each Network Map that it provides. 134 3.2. PID Property Type: servingload 136 An ALTO Server MAY define the 'servingload' Endpoint Property Type 137 for each Network Map that it provides. 139 3.3. PID Property Type: supportedcapacity 141 An ALTO Server MAY define the 'supportedcapacity' Endpoint Property 142 Type for each Network Map that it provides. 144 3.4. PID Property Type: availcapacity 146 An ALTO Server MAY define the 'supportedcapacity' Endpoint Property 147 Type for each Network Map that it provides. 149 4. Endpoint Properties Extension 151 An endpoint may have various different properties. The example 152 property of an Endpoint is network location such as pid or its 153 connectivity type such as ADSL (Asymmetric Digital Subscriber Line), 154 Cable, or FTTH (Fiber To The Home). The endpoint property can be 155 used in both Map service or endpoint property service. The base ALTO 156 protocol [ALTO] has defined three endpoint properties, i.e., 157 pid,priv:,exp: (Section 7.1.1 of ALTO base specification [ALTO]). 158 This document define 14 new endpoint properties for virtualized 159 endpoint to support service topologies creation and service chaining. 161 4.1. Endpoint Property Type: nodetype 163 An ALTO Server MAY define the 'nodetype' Endpoint Property Type for 164 each Network Map that it provides. The 'nodetype' Endpoint Property 165 is used to indicate the endpoint type. The endpoint types may 166 include service function enabled node, service function chain ingress 167 node, service function chain egress node. 169 4.2. Endpoint Property Type: servicetype 171 An ALTO Server MAY define the 'servicetype' Endpoint Property Type 172 for each Network Map that it provides. The 'servicetype' Endpoint 173 Property reflect service type the endpoint supports. The service 174 types may include firewall type, DPI type, NAT44 type, Load balancer 175 type. 177 4.3. Endpoint Property Type: forwarding class 179 An ALTO Server MAY define the 'forwardingclass' Endpoint Property 180 Type for each Network Map that it provides. The 'forwardingclass' 181 Endpoint Property reflects forwarding class the endpoint supports. 182 The supported forwarding classes include expedited forwarding, 183 assured forwarding,network control, best effort. 185 4.4. Endpoint Property Type: Packetrateutilization 187 An ALTO Server MAY define the 'packetrateutilization' Endpoint 188 Property Type for each Network Map that it provides. The 189 'packetrateutilization' Endpoint Property is used to indicate packet 190 rate utilization. 192 4.5. Endpoint Property Type: bandwidthutilization 194 An ALTO Server MAY define the 'bandwidthutilization' Endpoint 195 Property Type for each Network Map that it provides. The ' 196 bandwidthutilization ' Endpoint Property is used to indicate packet 197 rate utilization. 199 4.6. Endpoint Property Type: memoryutilization 201 An ALTO Server MAY define the 'availablememory' Endpoint Property 202 Type for each Network Map that it provides. The ' availablememory' 203 Endpoint Property is used to indicate packet rate utilization. 205 4.7. Endpoint Property Type: availablememory 207 An ALTO Server MAY define the 'availablememory' Endpoint Property 208 Type for each Network Map that it provides. The ' availablememory' 209 Endpoint Property is used to indicate packet rate utilization. 211 4.8. Endpoint Property Type: ributilization 213 An ALTO Server MAY define the 'ributilization' Endpoint Property Type 214 for each Network Map that it provides. The ' ributilization ' 215 Endpoint Property is used to indicate packet rate utilization. 217 4.9. Endpoint Property Type: fibutilization 219 An ALTO Server MAY define the 'fibutilization' Endpoint Property Type 220 for each Network Map that it provides. The ' fibutilization ' 221 Endpoint Property is used to indicate packet rate utilization. 223 4.10. Endpoint Property Type: cpuutilization 225 An ALTO Server MAY define the 'cpuutilization' Endpoint Property Type 226 for each Network Map that it provides. The ' cpuutilization ' 227 Endpoint Property is used to indicate packet rate utilization. 229 4.11. Endpoint Property Type: availablestorage 231 An ALTO Server MAY define the 'ributilization' Endpoint Property Type 232 for each Network Map that it provides. The ' availablestorage ' 233 Endpoint Property is used to indicate packet rate utilization. 235 4.12. Endpoint Property Type: supportedaclnum 237 An ALTO Server MAY define the 'supportedaclnum' Endpoint Property 238 Type for each Network Map that it provides. 'supportedaclnum' 239 Endpoint Property reflects endpoint capability from supported ACL 240 number perspective. 242 4.13. Endpoint Property Type: virtualcontextnum 244 An ALTO Server MAY define the 'virtualcontextnum' Endpoint Property 245 Type for each Network Map that it provides. 'virtualcontextnum' 246 Endpoint Property reflects endpoint capability from supported ACL 247 number perspective. 249 4.14. Endpoint Property Type: supportedpacketrate 251 An ALTO Server MAY define the 'supportedpacketrate' Endpoint Property 252 Type for each Network Map that it provides. 'virtualcontextnum' 253 Endpoint Property reflects endpoint capability from supported ACL 254 number perspective. 256 5. Security Considerations 258 The properties defined in this document present no security 259 considerations beyond those in Section 14 of the base ALTO 260 specification [ALTO]. 262 6. IANA Considerations 264 TBC. 266 7. References 268 7.1. Normative References 270 [ALTO] Alimi, R., "ALTO Protocol", 271 ID draft-ietf-alto-protocol-16, May 2013. 273 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 274 Requirement Levels", March 1997. 276 7.2. Informative References 278 [I.D-bitar-i2rs-service-chaining] 279 Bitar, N., Heron, G., and L. Fang, "Interface to the 280 Routing System (I2RS) for Service Chaining: Use Cases and 281 Requirements", ID draft-bitar-i2rs-service-chaining-00, 282 July 2013. 284 Authors' Addresses 286 Qin Wu 287 Huawei 288 101 Software Avenue, Yuhua District 289 Nanjing, Jiangsu 210012 290 China 292 Email: bill.wu@huawei.com 294 Zhen Cao 295 China Mobile 296 53A Xibianmennei Ave., Xuanwu District 297 Beijing, Beijing 100053 298 P.R. China 300 Email: zehn.cao@gmail.com