idnits 2.17.1 draft-ietf-alto-cost-calendar-01.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 document seems to lack a Security Considerations section. ** There are 10 instances of too long lines in the document, the longest one being 10 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 97 has weird spacing: '...nt cost map...' == Line 354 has weird spacing: '...NString cost...' == Line 355 has weird spacing: '...NString tim...' == Line 356 has weird spacing: '...NNumber num...' == Line 580 has weird spacing: '...Boolean cal...' == (5 more instances...) -- The document date (February 13, 2017) is 2629 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: 'TODO' is mentioned on line 933, but not defined == Missing Reference: 'OPTIONAL' is mentioned on line 643, but not defined == Unused Reference: 'ID-alto-protocol' is defined on line 1227, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 5693 -- Duplicate reference: RFC7285, mentioned in 'RFC7285', was also mentioned in 'ID-alto-protocol'. Summary: 3 errors (**), 0 flaws (~~), 10 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group S. Randriamasy 3 Internet-Draft Nokia Bell Labs 4 Intended status: Standards Track R. Yang 5 Expires: August 17, 2017 Yale University 6 Q. Wu 7 Huawei 8 L. Deng 9 China Mobile 10 N. Schwan 11 Thales Deutschland 12 February 13, 2017 14 ALTO Cost Calendar 15 draft-ietf-alto-cost-calendar-01 17 Abstract 19 The goal of Application-Layer Traffic Optimization (ALTO) is to 20 bridge the gap between network and applications by provisioning 21 network related information in order to allow applications to make 22 network informed decisions. The present draft extends the ALTO cost 23 information so as to broaden the decision possibilities of 24 applications to not only decide 'where' to connect to, but also 25 'when'. This is useful to applications that need to schedule their 26 data transfers and connections and have a degree of freedom to do so. 27 ALTO guidance to schedule application traffic can also efficiently 28 help for load balancing and resources efficiency. Besides, the ALTO 29 Cost Calendar allows to schedule the ALTO requests themselves and 30 thus to save a number of ALTO transactions. 32 This draft proposes new capabilities and attributes on filtered cost 33 maps and endpoint costs enabling an ALTO Server to provide "Cost 34 Calendars". These capabilities are applicable to time-sensitive ALTO 35 metrics. With ALTO Cost Calendars, an ALTO Server exposes ALTO Cost 36 Values in JSON arrays where each value corresponds to a given time 37 interval. The time intervals as well as other Calendar attributes 38 are specified in the IRD and ALTO Server responses. 40 Requirements Language 42 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 43 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 44 document are to be interpreted as described in RFC 2119 [RFC2119]. 46 Status of This Memo 48 This Internet-Draft is submitted in full conformance with the 49 provisions of BCP 78 and BCP 79. 51 Internet-Drafts are working documents of the Internet Engineering 52 Task Force (IETF). Note that other groups may also distribute 53 working documents as Internet-Drafts. The list of current Internet- 54 Drafts is at http://datatracker.ietf.org/drafts/current/. 56 Internet-Drafts are draft documents valid for a maximum of six months 57 and may be updated, replaced, or obsoleted by other documents at any 58 time. It is inappropriate to use Internet-Drafts as reference 59 material or to cite them other than as "work in progress." 61 This Internet-Draft will expire on August 17, 2017. 63 Copyright Notice 65 Copyright (c) 2017 IETF Trust and the persons identified as the 66 document authors. All rights reserved. 68 This document is subject to BCP 78 and the IETF Trust's Legal 69 Provisions Relating to IETF Documents 70 (http://trustee.ietf.org/license-info) in effect on the date of 71 publication of this document. Please review these documents 72 carefully, as they describe your rights and restrictions with respect 73 to this document. Code Components extracted from this document must 74 include Simplified BSD License text as described in Section 4.e of 75 the Trust Legal Provisions and are provided without warranty as 76 described in the Simplified BSD License. 78 Table of Contents 80 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 81 2. Overview of ALTO Cost Calendars . . . . . . . . . . . . . . . 5 82 2.1. ALTO Cost Calendar information features . . . . . . . . . 5 83 2.2. ALTO Calendar design characteristics . . . . . . . . . . 6 84 2.2.1. ALTO Cost Calendar for all cost modes . . . . . . . . 7 85 2.2.2. Compatibility with legacy ALTO Clients . . . . . . . 7 86 3. ALTO Calendar specification: IRD extensions . . . . . . . . . 7 87 3.1. Calendar attributes in the IRD resources capabilities . . 7 88 3.2. Calendars in a delegate IRD . . . . . . . . . . . . . . . 9 89 3.3. Example IRD with ALTO Cost Calendars . . . . . . . . . . 9 90 4. ALTO Calendar specification: Service Information Resources . 12 91 4.1. Calendar extensions for Filtered Cost Maps . . . . . . . 12 92 4.1.1. Calendar extensions in Filtered cost map requests . . 13 93 4.1.2. Calendar extensions in Filtered Cost map responses . 13 94 4.1.3. Use case and example for a FCM with a bandwidth 95 Calendar . . . . . . . . . . . . . . . . . . . . . . 15 96 4.2. Calendar extensions in the Endpoint Cost Map Service . . 17 97 4.2.1. Calendar specific input in Endpoint cost map 98 requests . . . . . . . . . . . . . . . . . . . . . . 17 99 4.2.2. Calendar attributes in the Endpoint Cost Map response 17 100 4.2.3. Use case and example for the ECS with a routingcost 101 Calendar . . . . . . . . . . . . . . . . . . . . . . 18 102 4.2.4. use case and example for the ECS with a multi-cost 103 calendar for routingcost and latency . . . . . . . . 21 104 4.3. Recap of rules related to ALTO Cost Calendars . . . . . . 23 105 5. Use cases for ALTO Cost Schedule . . . . . . . . . . . . . . 23 106 5.1. Bulk Data Transfer scheduling upon bandwidth calendars . 23 107 5.1.1. Applicable example transaction . . . . . . . . . . . 24 108 5.2. Applications with limited connectivity or access to 109 datacenters . . . . . . . . . . . . . . . . . . . . . . . 24 110 5.2.1. Applicable example transaction . . . . . . . . . . . 26 111 5.3. SDN Controller guided traffic scheduling with Calendars . 26 112 5.3.1. Applicable example transaction . . . . . . . . . . . 27 113 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 114 6.1. Information for IANA on proposed Cost Types . . . . . . . 27 115 6.2. Information for IANA on proposed Endpoint Propeeries . . 27 116 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 27 117 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 27 118 8.1. Normative References . . . . . . . . . . . . . . . . . . 27 119 8.2. Informative References . . . . . . . . . . . . . . . . . 28 120 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28 122 1. Introduction 124 IETF is currently standardizing the ALTO protocol which aims at 125 providing guidance to overlay applications needing to select one or 126 several hosts from a set of candidates able to provide a desired 127 resource. This guidance is based on parameters that affect 128 performance and efficiency of the data transmission between the hosts 129 such as the topological distance. The goal of ALTO is to improve the 130 Quality of Experience (QoE) in the application while optimizing 131 resource usage in the underlying network infrastructure. 133 The ALTO protocol in [RFC7285] specifies a Network Map which defines 134 groupings of endpoints in provider-defined network regions (called 135 PIDs). The Cost Map Service, Endpoint Cost Service (ECS) and 136 Endpoint Ranking Service then provide ISP-defined costs and rankings 137 for connections among the specified endpoints and PIDs and thus 138 incentives for application clients to connect to ISP preferred 139 locations, e.g. to reduce their costs. ALTO intentionally avoids 140 provisioning realtime information as explained in the ALTO Problem 141 Statement [RFC5693] and ALTO Requirements [RFC5693].Thus the current 142 Cost Map and Endpoint Cost Service are providing, for a given Cost 143 Type, exactly one path cost value. Applications have to query one of 144 these two services to retrieve the currently valid cost values. They 145 therefore need to plan their ALTO information requests according to 146 their own estimation of the frequency of cost value change. 148 With [RFC7285], an ALTO client should interpret the returned costs as 149 those at the query moment. However, Network costs can fluctuate, 150 e.g. due to diurnal patterns of traffic demand or planned events such 151 as network maintenance, holidays or highly publicized events. 152 Providing network costs for only the current time thus may not be 153 sufficient, in particular for applications that can schedule their 154 traffic in a span of time, for example by deferring backup to night 155 during traffic trough. 157 In case the ALTO Cost value changes are predicable over a certain 158 period of time and the application does not require immediate data 159 transfer, it can save time to get the whole set of cost values over 160 this period in one ALTO response. Using them to schedule data 161 transfers allows optimising the network resources usage and QoE. 162 ALTO Clients and Servers can also minimize their workload by 163 accordingly scheduling their data exchanges. 165 This document extends RFC7285 to allow an ALTO server to provide 166 network costs for a given duration of time. A sequence of network 167 costs across a time span for a given pair of network locations is 168 named an "ALTO Cost Calendar". The Filtered Cost Map Service and 169 Endpoint Cost Service are extended to provide Cost Calendars. In 170 addition to this functional ALTO enhancement, we expect to further 171 gain on storage and on the wire data exchange by gathering multiple 172 Cost Values for one Cost Type into one single ALTO Server response. 174 In this draft an "ALTO Cost Calendar" is specified by information 175 resources capabilities that are applicable to time-sensitive ALTO 176 metrics. An ALTO Cost Calendar exposes ALTO Cost Values in JSON 177 arrays where each value corresponds to a given time interval. The 178 time intervals as well as other Calendar attributes are specified in 179 the IRD and in the Server response to allow the ALTO Client to 180 interpret the received ALTO values. Last, the proposed extensions 181 for ALTO Calendars are applicable to any Cost Mode and they ensure 182 backwards compatibility with legacy ALTO clients. 184 In the rest of this document, Section 2 provides the design 185 characteristics. Sections 3 and 4 define the formal specifications 186 for the IRD and the information resources. Section 5 provides non- 187 normative use cases to illustrate the usage of cost calendars. IANA 188 considerations and security considerations will be completed in 189 further versions. 191 2. Overview of ALTO Cost Calendars 193 An ALTO Cost calendar provided by the ALTO Server provides 2 194 information items: 196 o an array of values for a given metric, where each value 197 corresponds to a time interval, where the value array can 198 sometimes be a cyclic pattern that repeats a certain number of 199 times. 201 o attributes describing the time scope of the calendar such as the 202 size and number of the intervals and the date of the starting 203 point of the calendar, allowing an ALTO Client to properly 204 interpret the values. 206 An ALTO Cost Calendar can be used like a "time table" to figure out 207 the best time to schedule data transfers and also to proactively 208 manage application traffic given predictable events such as flash 209 crowds, traffic intensive holidays and network maintenance. It may 210 be viewed as a synthetic abstraction of real measurements that can be 211 historic or be a prediction for upcoming time periods. 213 Most likely, the ALTO Cost Calendar would be used for the Endpoint 214 Cost Service, assuming that a limited set of feasible Endpoints for a 215 non-real time application is already identified, that they do not 216 need to be accessed immediately and that their access can be 217 scheduled within a given time period. The Filtered Cost Map service 218 is also applicable as long as the size of the Map allows it. 220 2.1. ALTO Cost Calendar information features 222 The Calendar attributes are provided in the IRD and in ALTO Server 223 responses. The IRD announces attributes with dateless values in its 224 information resources capabilities, where as attributes with time 225 dependent values are provided in the "meta" of Server responses. The 226 ALTO Cost Calendar attributes provide the following information: 228 o attributes to interpret the time scope of the Calendar value 229 array: 231 * generic time zone, 233 * applicable time interval for each calendar value: combining 234 numbers and time units to reflect for example: 1 hour, 2 235 minutes, 10 seconds, 1 week, 1 month, 237 * duration of the Calendar: e.g. the number of intervals provided 238 in the calendar. 240 o "calendar-start-date": specifying when the calendar starts, that 241 is to which date the first value of the cost calendar is 242 applicable. 244 o "repeated": an optional attribute indicating for how many 245 iterations the provided calendar will have the same values. The 246 server may use it to allow the client to schedule its next request 247 and thus save its own workload by avoiding to process useless 248 requests. 250 2.2. ALTO Calendar design characteristics 252 The protocol extension placeholders for an ALTO Calendar are: the 253 IRD, the ALTO requests and responses for Cost calendars. 255 Extensions are designed to be light and ensure backwards 256 compatibility with base protocol ALTO Clients and with other 257 extensions. It uses section 8.3.7 "Parsing of Unknown Fields" of 258 RFC7285 that writes: "Extensions may include additional fields within 259 JSON objects defined in this document. ALTO implementations MUST 260 ignore unknown fields when processing ALTO messages." 262 The calendar-specific capabilities are integrated in the information 263 resources of the IRD and in the "meta" member of ALTO responses to 264 Cost Calendars requests. A calendar and its capabilities are 265 associated to a given information resource and within this 266 information resource to a given cost type. This design has several 267 advantages: 269 o it does not introduce a new mode, 271 o it does not introduce new media types, 273 o it allows an ALTO Server to offer calendar capabilities on a cost 274 type, with attributes values adapted to each information resource. 276 The Applicable Calendared information resources are: 278 o the Filtered Cost Map, 280 o the Endpoint Cost Map. 282 The ALTO Server can choose in which frequency it provides cost 283 Calendars to ALTO Clients. It may either provide calendar updates 284 starting at the request date, or carefully schedule its updates so as 285 to take profit from a potential repetition/periodicity of calendar 286 values. 288 2.2.1. ALTO Cost Calendar for all cost modes 290 Calendars are well-suited for values encoded in the 'numerical' mode. 291 However, Calendars can also represent any metric considered as time- 292 sensitive by an ALTO Server. For example, types of Cost values such 293 as JSONBool can also be expressed as calendars, as states may be 294 "true" or "false" depending on given time periods or likewise, values 295 represented by strings, such as "medium", "high", "low", "blue", 296 "open" . 298 Note also that a Calendar is applicable as well to time-sensitive 299 metrics provided in the 'ordinal' mode, if these values are time- 300 sentitive and their update is carefully managed by the ALTO Server. 302 2.2.2. Compatibility with legacy ALTO Clients 304 The ALTO protocol extensions for Cost Calendars have been defined so 305 as to ensure that Calendar capable ALTO Servers can provide legacy 306 ALTO Clients with legacy information resources as well. That is a 307 legacy ALTO Client can request resources and receive responses as 308 specified in RFC7285. 310 For compatibility with legacy ALTO Clients specified in RFC7285, 311 calendared information resources are not applicable for full Cost 312 Maps for the following reason: a legacy ALTO client would receive a 313 Calendared Cost Map via an HTTP 'GET' command. As specified in 314 section 8.3.7 of RFC7285, it will ignore the Calendar Attributes 315 indicated in the "meta" of the responses. Therefore, lacking 316 information on calendar attributes, it will not be able to correctly 317 interpret and process the values of the received array of calendar 318 cost values. 320 3. ALTO Calendar specification: IRD extensions 322 The Calendar attributes in the IRD information resources capabilities 323 carry constant dateless values. A calendar is associated to an 324 information resource rather than a cost type. For example, a Server 325 can provide a "routingcost" calendar for the Filtered Cost Map 326 Service at a granularity of one day and a "routingcost" calendar for 327 the Endpoint Cost service at a finer granularity but for a limited 328 number of endpoints. 330 3.1. Calendar attributes in the IRD resources capabilities 332 When for an applicable resource , an ALTO Server provides a Cost 333 Calendar for a given Cost Type, it MUST indicate this in the IRD 334 capabilities of this resource, by an object of type 335 'CalendarAttributes', associated to this Cost Type and specified 336 below. 338 The capabilities of a Calendar aware information resource entry have 339 a member named "calendar-attributes" which is an array of objects of 340 type CalendarAttributes. It is necessary to use an array because of 341 resources such as Filtered Cost Map and Endpoint Cost Map, for which 342 the member "cost-type-names" is an array of 1 or more values. 344 RULE: a member "calendar-attributes" MUST appear only once for each 345 applicable cost type name of a resource entry. If "calendar- 346 attributes" are specified several times for a same "cost-type-name" 347 in the capabilities of a resource entry, the ALTO client SHOULD 348 ignore any calendar capabilities on this "cost-type-name" for this 349 ressource entry. 351 CalendarAttributes calendar-attributes <1..*>; 353 object{ 354 [JSONString cost-type-name;] 355 JSONString time-interval-size; 356 JSONNumber number-of-intervals; 357 } CalendarAttributes; 359 o "cost-type-name": 361 * an optional member indicating the cost-type-name in the IRD 362 entry to which the capabilities apply. If this not present, it 363 MUST be assumed to correspond to its index in the "cost-type- 364 names" list of the IRD resource entry. 366 o "time-interval-size": 368 * is the duration of an ALTO calendar time interval, expressed as 369 a time unit appended to the number of these units. The time 370 unit, ranges from "second" to "year". The number is encoded 371 with an integer. Example values are: "5 minute" , "2 hour", 372 meaning that each calendar value applies on a time interval 373 that lasts respectively 5 minutes and 2 hours. 375 o "number-of-intervals": 377 * the integer number of values of the cost calendar array, at 378 least equal to 1. 380 - Attribute "cost-type-name" , if used, provides a better readability 381 to the calendar attributes specified in the IRD and avoids confusion 382 with calendar attributes of other cost-types. 384 - Multiplying Attributes 'time-interval-size' and 'number-of- 385 intervals' provides the duration of the provided calendar. For 386 example an ALTO Server may provide a calendar for ALTO values 387 changing every 'time-interval-size' equal to 5 minutes. If 'number- 388 of-intervals' has the value 12, then the duration of the provided 389 calendar is "1 hour". 391 3.2. Calendars in a delegate IRD 393 One option to clarify IRD resources is that a "root" ALTO Server 394 implementing base protocol resources delegates "specialized" 395 information resources such as the ones providing Cost Calendars to 396 another ALTO Server running in a subdomain specified with its URI in 397 the "root" ALTO Server. This option is described in Section 9.2.4 398 "Delegation using IRDs" of RFC7285. 400 This document provides an example, where a "root" ALTO Server runs in 401 a domain called "alto.example.com". It delegates the announcement of 402 Calendars capabilities to an ALTO Server running in a subdomain 403 called "custom.alto.example.com". The location of the "delegate 404 Calendar IRD" is assumed to be indicated in the "root" IRD by the 405 resource entry: "custom-calendared-resources". 407 Another advantage is that some Cost Types for some resources may be 408 more advantageous as Cost Calendars and it makes few sense to get 409 them as a single value. For example, Cost Types with predictable and 410 frequently changing values, calendared in short time intervals such 411 as a minute. 413 3.3. Example IRD with ALTO Cost Calendars 415 The cost types in this example are either specified in the base ALTO 416 protocol or may be proposed in other drafts see 417 [draft-ietf-alto-performance-metrics]. In this example, the 418 available cost metrics are indicated in the "meta" field by cost type 419 names "num-routingcost", "num-latency", "num-pathbandwidth" and 420 "string-quality-status". Metrics "routingcost" , 'latency' and 421 'Availbandwidth' are available in the "numerical" Cost Mode. Metric 422 "quality-status" is available in the "string" Cost Mode. 424 The example IRD includes 2 particular URIs providing calendars: 426 o "http://custom.alto.example.com/calendar/costmap/filtered": a 427 filtered cost map in which calendar capabilities are indicated for 428 cost type names: "num-routingcost", "num-pathbandwidth" and 429 "string-service-status", 431 o "http://custom.alto.example.com/calendar/endpointcost/lookup": an 432 endpoint cost map in which in which calendar capabilities are 433 indicated for cost type names: "num-routingcost", "num-latency", 434 "num-pathbandwidth", "string-service-status". 436 The design of the Calendar capabilities allows that some calendars on 437 a cost type name are available in several information resources with 438 different Calendar Attributes. This is the case for calendars on 439 "num-routingcost", "num-pathbandwidth" and "string-service-status" , 440 available in both the Filtered Cost map and Endpoint Cost map 441 service, but with different time interval sizes for "num- 442 pathbandwidth" and "string-service-status". 444 GET /calendars-directory HTTP/1.1 445 Host: custom.alto.example.com 446 Accept: application/alto-directory+json,application/alto-error+json 447 --------------- 449 HTTP/1.1 200 OK 450 Content-Length: [TODO] 451 Content-Type: application/alto-directory+json 453 { 454 "meta" : { 455 "cost-types": { 456 "num-routingcost": { 457 "cost-mode" : "numerical", 458 "cost-metric" : "routingcost" 459 }, 460 "num-latency": { 461 "cost-mode" : "numerical", 462 "cost-metric": "latency" 463 }, 464 "num-pathbandwidth": { 465 "cost-mode" : "numerical", 466 "cost-metric": "Availbandwidth", 467 }, 468 "string-qual-status": { 469 "cost-mode" : "string", 470 "cost-metric": "quality-status", 471 } 472 ... other meta ... 473 }, 475 "resources" : { 476 "filtered-cost-map-calendar" : { 477 "uri" : "http://custom.alto.example.com/calendar/costmap/filtered", 478 "media-type" : "application/alto-costmap+json", 479 "accepts" : "application/alto-costmapfilter+json", 480 "capabilities" : { 481 "cost-constraints" : true, 482 "cost-type-names" : [ "num-routingcost", "num-pathbandwidth", 483 "string-service-status" ], 484 "calendar-attributes" : [ 485 {"cost-type-names" : [ "num-routingcost", "num-pathbandwidth" ], 486 "time-interval-size" : "1 hour", 487 "number-of-intervals" : 24 488 }, 489 {"cost-type-names" : "string-service-status", 490 "time-interval-size" : "30 minute", 491 "number-of-intervals" : 48 492 } 493 ] // end calendar-attributes 494 "uses": [ "my-default-network-map" ] 495 } 496 }, 498 "endpoint-cost-calendar-map" : { 499 "uri" : "http://custom.alto.example.com/calendar/endpointcost/lookup", 500 "media-types" : [ "application/alto-endpointcost+json" ], 501 "accepts" : [ "application/alto-endpointcostparams+json" ], 502 "capabilities" : { 503 "cost-constraints" : true, 504 "cost-type-names" : [ "num-routingcost", "num-latency", 505 "num-pathbandwidth", "string-service-status" ], 506 "calendar-attributes" : [ 507 {"cost-type-names" : "num-routingcost", 508 "time-interval-size" : "1 hour", 509 "number-of-intervals" : 24 510 }, 511 {"cost-type-names" : "latency", 512 "time-interval-size" : "5 minute", 513 "number-of-intervals" : 12 514 }, 515 {"cost-type-names" : "num-pathbandwidth", 516 "time-interval-size" : "1 minute", 517 "number-of-intervals" : 60 518 }, 519 {"cost-type-names" : "string-service-status", 520 "time-interval-size" : "2 minute", 521 "number-of-intervals" : 30 522 } 523 ] 524 "uses": [ "my-default-network-map" ] 525 } // ECM capab 526 } //info resource N 528 } // ressources 530 In this example IRD, for the filtered cost map service: 532 o the Calendar for 'num-routingcost' and 'num-pathbandwidth' is an 533 array of 24 values each provided on a time interval lasting 1 534 hour. 536 o the Calendar for "string-service-status": "is an array of 48 537 values each provided on a time interval lasting 30 minutes. 539 For the endpoint cost map service: 541 o the Calendar for 'num-routingcost': is an array of 24 values each 542 provided on a time interval lasting 1 hour. 544 o the Calendar for 'latency': is an array of 12 values each provided 545 on a time interval lasting 5 minutes. 547 o the Calendar for 'num-pathbandwidth': is an array of 60 values 548 each provided on a time interval lasting 1 minute. 550 o the Calendar for "string-service-status": "is an array of 30 551 values each provided on a time interval lasting 2 minutes. 553 4. ALTO Calendar specification: Service Information Resources 555 This section documents the individual information resources defined 556 to provide the Calendared information services defined in this 557 document. 559 The reference time zone for the provided time values is GMT because 560 the option chosen to express the time format is the HTTP header 561 fields format: 563 Date: Tue, 15 Nov 2014 08:12:31 GMT 565 4.1. Calendar extensions for Filtered Cost Maps 567 A legacy ALTO client requests and gets filtered cost map responses as 568 specified in RFC7285. 570 4.1.1. Calendar extensions in Filtered cost map requests 572 The input parameters of a "legacy" request for a filtered cost map, 573 defined by object ReqFilteredCostMap in section 11.3.2 of RFC7285, 574 are augmented with one additional member. 576 A Calendar-aware ALTO client requesting a Calendar on a given Cost 577 Type for a Filtered Cost Map resource having Calendar capabilities 578 MUST add the following field to its input parameters: 580 JSONBoolean calendared<1..*>; 582 This field is an array of 1 to N boolean values, where N is the 583 number of requested metrics. Each boolean value indicates whether or 584 not the ALTO Server should provide the values for this Cost Type as a 585 calendar. 587 This field MUST NOT be specified if member "calendar-attributes" is 588 not present for this information resource. 590 A Calendar-aware ALTO client supporting single cost type values, as 591 specified in RFC7285, MUST provide an array of 1 element: 593 "calendared" : [true]; 595 A Calendar-aware ALTO client that is also Multi-Cost aware MUST 596 provide an array of N values set to "true" or "false", depending 597 whether it wants the applicable Cost Type values as a single or 598 calendared value. 600 If this field is not present, it MUST be assumed to have only values 601 equal to "false". 603 4.1.2. Calendar extensions in Filtered Cost map responses 605 The calendared costs are JSONArrays instead of JSONNumbers for the 606 legacy ALTO implementation. All arrays have a number of values equal 607 to 'number-of-intervals'. 609 The "meta" field of a Calendared Filtered Cost map response MUST 610 include at least: 612 o if the ALTO Client supports cost values for one Cost Type at a 613 time only: the "meta" fields specified in RFC 7285 for these 614 information service responses: 616 * "dependent-vtags ", 617 * "cost-type" field. 619 o if the ALTO Client supports cost values for several Cost Types at 620 a time, as specified in [draft-ietf-alto-multi-cost] : the "meta" 621 fields specified in [draft-ietf-alto-multi-cost] for these 622 information service responses: 624 * "dependent-vtags ", 626 * "cost-type" field with value set to '{}', for backwards 627 compatibility with RFC7285. 629 * "multi-cost-types" field. 631 In addition, the "meta" field of a Calendared Filtered Cost map 632 response MUST include the member "calendar-response-attributes" for 633 the requested information resource, together with the values provided 634 by the ALTO Server for these attributes. This member is an array of 635 objects of type "CalendarResponseAttributes", defined as follows: 637 CalendarResponseAttributes calendar-response-attributes <1..*>; 639 object{ 640 JSONString calendar-start-time; 641 JSONString time-interval-size; 642 JSONNumber number-of-intervals; 643 [JSONNumber repeated;] [OPTIONAL] 644 } CalendarResponseAttributes; 646 o "calendar-start-time": indicates the date at which the first value 647 of the calendar applies. By default, the value provided for the 648 "calendar-start-time" attribute SHOULD be no later than the 649 request date. 651 o "time-interval-size": as specified in section "Calendar attributes 652 in the IRD resources capabilities", 654 o "number-of-intervals": as specified in section "Calendar 655 attributes in the IRD resources capabilities", 657 o "repeated": is an optional field provided for Calendars. It is an 658 integer N greater or equal to '1' that indicates how many 659 iterations of the calendar value array starting at the date 660 indicated by "calendar-start-time" have the same values. The 661 number N includes the provided iteration. 663 Using the member "repeated" helps minimizing on the wire data 664 exchange: by providing it, an ALTO Server will avoid unecessary 665 processing of requests for Calendars with unchanged values while it 666 allows ALTO Clients to save their resources as well. 668 For example: if the "calendar-start-time" member has value "Mon, 30 669 Jun 2014 at 00:00:00 GMT" and if the value of member "repeated" is 670 equal to 4, it means that the calendar values are the same values on 671 Monday, Tuesday, Wednesday and Thursday. The ALTO Client thus may 672 use the same calendar for the next 4 duration periods following 673 "calendar-start-time". 675 4.1.3. Use case and example for a FCM with a bandwidth Calendar 677 An example of non-real time information that can be provisioned in a 678 'calendar' is the expected path bandwidth. While the transmission 679 rate can be measured in real time by end systems, the operator of a 680 data center is in the position of formulating preferences for given 681 paths, at given time periods for example to avoid traffic peaks due 682 to diurnal usage patterns. In this example, we assume that an ALTO 683 Client requests a bandwidth calendar as specified in the IRD to 684 shedule its bulk data transfers as described in the use cases. 686 In the example IRD, calendars for cost type name "num-pathbandwidth" 687 are available for the information resources: "filtered-cost-calendar- 688 map" and "endpoint-cost-calendar-map". The ALTO Client requests a 689 calendar for "num-pathbandwidth" via a POST request for a filtered 690 cost map. 692 We suppose in this example that the ALTO Client sends its request on 693 Tuesday July 1st 2014 at 13:15 695 POST /calendar/costmap/filtered HTTP/1.1 696 Host: alto.example.com 697 Content-Length: [TODO] 698 Content-Type: application/alto-costmapfilter+json 699 Accept: application/alto-costmap+json,application/alto-error+json 701 { 702 "cost-type" : {"cost-mode" : "numerical", "cost-metric" : "Availbandwidth"}, 703 "calendared" : [true], 705 "pids" : { 706 "srcs" : [ "PID1", "PID2" ], 707 "dsts" : [ "PID1", "PID2", "PID3" ] 708 } 709 } 711 HTTP/1.1 200 OK 712 Content-Length: [TODO] 713 Content-Type: application/alto-costmap+json 715 { 716 "meta" : { 717 "dependent-vtags" : [...], 718 "cost-type" : {"cost-mode" : "numerical", "cost-metric" : "Availbandwidth"}, 719 "calendar-response-attributes" : [ 720 "calendar-start-time" : Tue, 1 Jul 2014 13:00:00 GMT, 721 "time-interval-size" : "2 hour", 722 "numb-intervals" : 12 723 ] 724 }, 726 "cost-map" : { 727 "PID1": { "PID1": [v1,v2, ... v12], 728 "PID2": [v1,v2, ... v12], 729 "PID3": [v1,v2, ... v12] }, 730 "PID2": { "PID1": [v1,v2, ... v12], 731 "PID2": [v1,v2, ... v12], 732 "PID3": [v1,v2, ... v12] } 733 } 734 } 736 4.2. Calendar extensions in the Endpoint Cost Map Service 738 This document extends the Endpoint Cost Service, as defined in 739 {11.5.1} of [RFC7285], by adding new input parameters and 740 capabilities, and by returning JSONArrays instead of JSONNumbers as 741 the cost values. The media type {11.5.1.1} and HTTP method 742 {11.5.1.2} are unchanged. 744 4.2.1. Calendar specific input in Endpoint cost map requests 746 The extensions to the requests for calendared Endpoint Cost Maps are 747 the same as for the Filtered Cost Map Service, specified in section 748 XXXX of this draft. 750 The ReqEndpointCostMap object for a Calendared ECM request will have 751 the following format: 753 object { 754 CostType cost-type; 755 [JSONBoolean calendared<1..*>;] 756 EndpointFilter endpoints; 757 } ReqEndpointCostMap; 759 object { 760 [TypedEndpointAddr srcs<0..*>;] 761 [TypedEndpointAddr dsts<0..*>;] 762 } EndpointFilter; 764 4.2.2. Calendar attributes in the Endpoint Cost Map response 766 The "meta" field of a Calendared Endpoint Cost map response MUST 767 include at least: 769 o if the ALTO Client supports cost values for one Cost Type at a 770 time only: the "meta" fields specified in {11.5.1.6} of RFC 7285 771 for the Endpoint Cost response: 773 * "cost-type" field. 775 o if the ALTO Client supports cost values for several Cost Types at 776 a time, as specified in [draft-ietf-alto-multi-cost] : the "meta" 777 fields specified in [draft-ietf-alto-multi-cost] for the the 778 Endpoint Cost response: 780 * "cost-type" field with value set to '{}', for backwards 781 compatibility with RFC7285. 783 * "multi-cost-types" field. 785 If the client request does not provide member "calendared" or if it 786 provides it with a value equal to 'false', then the ALTO Server 787 response is exactly as specified in the above cited references. 789 If the ALTO client provides member "calendared" with a value equal to 790 'true' in the input parameters, the "meta" member of a Calendared 791 Endpoint Cost Map response MUST include the same addifional member 792 "calendar-response-attributes" as specified for the Filtered Cost Map 793 Service. The Server response is thus changed as follows: 795 o the "meta" member has one additional field 796 "CalendarResponseAttributes", as specified for the Filtered Cost 797 Map Service, 799 o the calendared costs are JSONArrays instead of JSONNumbers for the 800 legacy ALTO implementation. All arrays have a number of values 801 equal to 'number-of-intervals'. 803 4.2.3. Use case and example for the ECS with a routingcost Calendar 805 Let us assume an Application Client is located in an end sytem with 806 limited resources and having an access to the network that is either 807 intermittent or provides an acceptable quality in limited but 808 predictable time periods. Therefore, it needs to both schedule its 809 resources greedy networking activities and its ALTO transactions. 811 The Application Client has the choice to trade content or resources 812 with a set of Endpoints and needs to decide with which one it will 813 connect and at what time. For instance, the Endpoints are spread in 814 different time-zones, or have intermittent access. In this example, 815 the 'routingcost' is assumed to be time sentitive with values 816 provided as ALTO Calendars. 818 The ALTO Client associated to the Application Client queries an ALTO 819 Calendar on 'routingcost' and will get the Calendar covering the 24 820 hours time period "containing" the date and time of the ALTO client 821 request. 823 For Cost Type 'num-routingcost', the sollicited ALTO Server has 824 defined 3 different daily patterns each represented by a Calendar, to 825 cover the week of Monday June 30th at 00:00 to Sunday July 6th 23:59: 827 - C1 for Monday, Tuesday, Wednesday, Thursday, (week days) 829 - C2 for Saturday, Sunday, (week end) 830 - C3 for Friday (maintenance outage on July 4, 2014 from 02:00:00 GMT 831 to 04:00:00 GMT, or big holiday such as New Year evening). 833 In the following example, the ALTO Client sends its request on 834 Tuesday July 1st 2014 at 13:15. 836 POST /calendar/endpointcost/lookup HTTP/1.1 837 Host: alto.example.com 838 Content-Length: [TODO] 839 Content-Type: application/alto-endpointcostparams+json 840 Accept: application/alto-endpointcost+json,application/alto-error+json 842 { 843 "cost-type" : {"cost-mode" : "numerical", "cost-metric" : "routingcost"}, 844 "calendared" : [true], 845 "endpoints" : { 846 "srcs": [ "ipv4:192.0.2.2" ], 847 "dsts": [ 848 "ipv4:192.0.2.89", 849 "ipv4:198.51.100.34", 850 "ipv4:203.0.113.45", 851 "ipv6:2000::1:2345:6789:abcd" 852 ] 853 } 854 } 856 HTTP/1.1 200 OK 857 Content-Length: [TODO] 858 Content-Type: application/alto-endpointcost+json 860 { 861 "meta" : { 862 "cost-type" : {"cost-mode" : "numerical", "cost-metric" : "routingcost"}, 863 "calendar-response-attributes" : [ 864 { "calendar-start-time" : Mon, 30 Jun 2014 00:00:00 GMT, 865 "time-interval-size" : "1 hour", 866 "numb-intervals" : 24, 867 "repeated": 4 } 868 ], 869 } // end meta 871 "endpoint-cost-map" : { 872 "ipv4:192.0.2.2": { 873 "ipv4:192.0.2.89" : [v1, v2, ... v24], 874 "ipv4:198.51.100.34" : [v1, v2, ... v24], 875 "ipv4:203.0.113.45" : [v1, v2, ... v24], 876 "ipv6:2000::1:2345:6789:abcd" : [v1, v2, ... v24] 877 } 878 } 879 } 880 When the Client gets the Calendar for "routingcost", it sees that the 881 "calendar-start-time" is Monday at 00h00 GMT and member "repeated" is 882 equal to '4'. It understands that the provided values are valid 883 until Thursday included and will only need to get a Calendar update 884 on Friday. 886 4.2.4. use case and example for the ECS with a multi-cost calendar for 887 routingcost and latency 889 In this example, it is assumed that the ALTO Server implements multi- 890 cost capabilities, as specified in [draft-ietf-alto-multi-cost] . 891 That is, an ALTO client can request and receive values for several 892 cost types in one single transaction. An illustrating use case is a 893 path selection done on the basis of 2 metrics: routing cost and 894 latency. 896 As in the previous example, the IRD indicates that the ALTO Server 897 provides "routingcost" Calendars in terms of 24 time intervals of 1 898 hour each. 900 For metric "latency", the IRD indicates that the ALTO Server provides 901 Calendars in terms of 12 time intervals values lasting each 5 902 minutes. 904 In the following example transaction, the ALTO Client sends its 905 request on Tuesday July 1st 2014 at 13:15. 907 POST calendar/endpointcost/lookup HTTP/1.1 908 Host: alto.example.com 909 Content-Length: [TODO] 910 Content-Type: application/alto-endpointcostparams+json 911 Accept: application/alto-endpointcost+json,application/alto-error+json 913 { 914 "cost-type" : {}, 915 "multi-cost-types" : [ 916 {"cost-mode" : "numerical", "cost-metric" : "routingcost"}, 917 {"cost-mode" : "numerical", "cost-metric" : "latency"} 918 ], 919 "calendared" : [true, true], 920 "endpoints" : { 921 "srcs": [ "ipv4:192.0.2.2" ], 922 "dsts": [ 923 "ipv4:192.0.2.89", 924 "ipv4:198.51.100.34", 925 "ipv4:203.0.113.45", 926 "ipv6:2000::1:2345:6789:abcd" 927 ] 929 } 930 } 932 HTTP/1.1 200 OK 933 Content-Length: [TODO] 934 Content-Type: application/alto-endpointcost+json 936 { 937 "meta" : { 938 "multi-cost-types" : [ 939 {"cost-mode" : "numerical", "cost-metric" : "routingcost"}, 940 {"cost-mode" : "numerical", "cost-metric" : "latency"} 941 ], 942 "calendar-response-attributes" : [ 943 { "cost-type-name : num-routingcost" 944 "calendar-start-time" : Mon, 30 Jun 2014 00:00:00 GMT, 945 "time-interval-size" : "1 hour", 946 "numb-intervals" : 24, 947 "repeated": 4 }, 948 { "cost-type-name : num-latency" 949 "calendar-start-time" : Tue, 1 Jul 2014 13:00:00 GMT, 950 "time-interval-size" : "5 minute", 951 "numb-intervals" : 12} 952 ], 953 } // end meta 955 "endpoint-cost-map" : { 956 "ipv4:192.0.2.2": { 957 "ipv4:192.0.2.89" : [[r1, r2, ... r24], [l1, l2, ... l12]], 958 "ipv4:198.51.100.34" : [[r1, r2, ... r24], [l1, l2, ... l12]], 959 "ipv4:203.0.113.45" : [[r1, r2, ... r24], [l1, l2, ... l12]], 960 "ipv6:2000::1:2345:6789:abcd" : [[r1, r2, ... r24], [l1, l2, ... l12]] 961 } 962 } 963 } 965 When receiving the response, the client sees that the calendar values 966 for 'routing cost' are repeated for 4 iterations. Therefore, in its 967 next requests until the routing cost calendar is expected to change, 968 the client will only need to request a calendar for "latency". 970 Without the ALTO Calendar extensions, the ALTO client would have no 971 clue on the dynamicity of the metric value change and would spend 972 needless time requesting values at an inappropriate pace. In 973 addition, without the Multi-Cost ALTO capabilities, the ALTO client 974 would duplicate this waste of time as it would need to send one 975 request per cost metric. 977 4.3. Recap of rules related to ALTO Cost Calendars 979 XXXXX TO BE COMPLETED + MOVED AT THE END OF THE SPECS 981 A Calendar-aware ALTO Server MUST implement the base protocol 982 specified in RFC7285. 984 When a metric is available as a calendar, it MUST be available as a 985 single value as well. An ALTO Server aquiring cost values in limited 986 time intervals only can construct a single value from the value 987 array. 989 Calendared information resources MUST be requested via a POST method. 991 5. Use cases for ALTO Cost Schedule 993 [THIS SECTION NEEDS TO BE SHORTENED ] 995 This section presents use cases showing the benefits of ALTO Cost 996 calendars for applications needing to decide both "where" to connect 997 and "when". 999 5.1. Bulk Data Transfer scheduling upon bandwidth calendars 1001 Large Internet Content Providers (ICPs) like Facebook or YouTube, as 1002 well as CDNs rely on data replication across multiple sites and time 1003 zones to offload the core site and increase user experience through 1004 shorter latency from a local site. Typically the usage pattern of 1005 these data centers or caches follows a location dependent diurnal 1006 demand pattern. In these examples, data replication across the 1007 various locations of an ICP, leads to bulk data transfers between 1008 datacenters on a diurnal pattern. 1010 In the meantime, there is a degree of freedom on when the content is 1011 transmitted from the origin server to the caching node, or from the 1012 core site to a local site. However, scheduling these data transfers 1013 is a non-trivial task as they should not infer with the user peak 1014 demand to avoid degradation of user experience and to decrease 1015 billing costs for the datacenter operator by leveraging off-peak 1016 hours for the transfer. 1018 As a result, these ICPs need to have a good knowledge on the link 1019 utilization patterns between the different datacenters before making 1020 an efficient scheduling decision. While usage data today is already 1021 gathered and used to schedule data transfers, provisioning these data 1022 gets increasingly complex with the number of CDN nodes and datacenter 1023 operators that are involved. In particular, privacy concerns prevent 1024 that this kind of data is shared across administrative domains. The 1025 ALTO Cost Calendar avoids these problems by presenting an abstracted 1026 view of time sensitive utilization maps through a dedicated ALTO 1027 service to allow ICPs a coherent scheduling of data transfers across 1028 administrative domains and time zones. 1030 Likewise, bandwidth Calendaring allows network operators to reserve 1031 resources in advance according to agreements with their customers, 1032 enabling them to transmit data with specified starting time and 1033 duration, for example, for a scheduled bulk data replication between 1034 data centers. Traditionally, this can be supported by a Network 1035 Management System operation such as path pre-establishment and 1036 activation on the agreed starting time. However, this does not 1037 provide efficient network usage since the established paths exclude 1038 the possibility of being used by other services even when they are 1039 not used for undertaking any service. 1041 An ALTO Cost calendar for TE metrics on transfer paths can support 1042 the scheduled bulk data replication with better efficiency since it 1043 can alleviate the processing burden on network elements. 1045 Cost calendars for these time-sensitive ALTO TE metrics need to 1046 consider the network topology and the dynamicity of the traffic. For 1047 example, a small topology with low density and low capacity that 1048 carries inpredictable, heavy and bursty traffic has few chances to 1049 exhibit stationary TE metric value patterns over large periods and 1050 would benefit to use the ALTO Calendar over smaller time slots. Some 1051 ALTO TE metric values, even aggregated over time may need to be 1052 updated at a frequency that would require doing ALTO requests at a 1053 pace that would be overload both the ALTO Client and the Server. 1054 Large high capacity topologies would benefit from Cost Calendars with 1055 a coarse time granularity for the filtered cost map service where as 1056 Calendars of finer time granularity for the Endpoint Cost Service 1057 would be better suited for small low density and capacity topologies. 1059 5.1.1. Applicable example transaction 1061 Assuming a Large high capacity topology, an applicable example 1062 transaction for this us case is provided by section 4.1.3. "Example 1063 transaction for a FCM with a "request-date" bandwidth Calendar". 1065 5.2. Applications with limited connectivity or access to datacenters 1067 Some applications are limited in their connectivity either in time or 1068 resources or both. For example applications running on devices in 1069 remote locations or in developing countries that need to synchronize 1070 their state with a data center periodically, in particular if 1071 sometimes there is no connection at all. Example applications are 1072 enterprise database update, remote learning, remote computation 1073 distributed on several data center endpoints. 1075 Wireless connections have a variable quality and may even be 1076 intermittent. On the other hand, the wireless network conditions 1077 have a rapid impact on applications while they can sometimes be 1078 predicted over a span of time. Non real time applications and time- 1079 insensitive data transfers such as client patching, archive syncing, 1080 etc. can benefit from careful scheduling. It is thus desirable to 1081 provide ALTO clients with routing costs to connection nodes (i.e. 1082 Application Endpoints) over different time periods. This would allow 1083 end systems using ALTO aware application clients to schedule their 1084 connections to application endpoints. 1086 Another challenge arises with applications using data and physical 1087 resources scattered around the world. For non-real time 1088 applications, the interaction with Endpoints can be orchestratrated 1089 and scheduled at the time slots corresponding to the best possible 1090 network conditions. For instance, resource Ra downloaded from 1091 Endpoint EPa at time t1, Resource Rb uploaded to EPb at time t2, some 1092 batch computation involving Ra and Rb done on EPc at time t3 and 1093 results R(A,B) downloaded to EPd and EPe at time t4. 1095 +-----+ +-----+ 1096 | EPa | | EPb | <----- Rb 1097 +-----+ +-----+ (t2=50) 1098 | +-------+ | 1099 Ra --------------> | EPc | | 1100 (time t1=10) | | | 1101 |t3=100 | <----------------- Rb 1102 +-------+ 1103 | \ 1104 | \ 1105 R(Ra,Rb) 1106 (t4=200) 1107 | \ 1108 | -------------------. 1109 V V 1110 +-----+ +-----+ 1111 | EPd | | EPe | 1112 +-----+ +-----+ 1114 5.2.1. Applicable example transaction 1116 An applicable example transaction for this use case is provided by 1117 section 4.2.3. "Example transaction for the ECS with a "periodic" 1118 routingcost Calendar". 1120 5.3. SDN Controller guided traffic scheduling with Calendars 1122 An ALTO Server can assist an SDN Controller by hosting abstracted 1123 network information that can be provided to SDN aware applications 1124 via an ALTO Client. 1126 Via the Northbound interface (NBI), applications may get QoE 1127 impacting information such as network provider preferences w.r.t. 1128 delay and bandwidth on the network paths. Such information may be 1129 provided via the ALTO Service. 1131 One key objective of an SDN controller is the ability to balance the 1132 application traffic whenever possible. Resources availability may 1133 often be predicted and strong incentives for applications to time 1134 shift their traffic may be given by network operators appropriately 1135 setting routing cost values at different time values, according to 1136 their policy on network utilization over time. 1138 To achieve this objective, the SDN controller can: 1140 1. get the network state information from its controlled network 1141 elements through its southbound API and derive an estimation of 1142 these values over given time frames 1144 2. abstract the network topology and end to end path costs and store 1145 them in an ALTO Server as Network Maps and Cost Calendars 1147 3. deliver these values to ALTO Clients linked to SDN applications, 1148 through the NBI. 1150 This way: 1152 o On one hand, the applications get the best possible QoE, as they 1153 can pick the best time for them to access one or more Endpoints or 1154 PIDs, 1156 o One the other hand, the SDN controller achieves load balancing and 1157 optimizes application traffic as it may guide the application 1158 traffic so as to better distribute the traffic over time. 1160 5.3.1. Applicable example transaction 1162 An applicable example transaction for this use case is provided by 1163 section 4.2.4. "Example transaction for the ECS with a calendar on 1164 both routingcost and latency". 1166 6. IANA Considerations 1168 Information for the ALTO Endpoint property registry maintained by the 1169 IANA and related to the new Endpoints supported by the acting ALTO 1170 server. These definitions will be formulated according to the syntax 1171 defined in Section on "ALTO Endpoint Property Registry" of [RFC7285] 1172 , 1174 Information for the ALTO Cost Type Registry maintained by the IANA 1175 and related to the new Cost Types supported by the acting ALTO 1176 server. These definitions will be formulated according to the syntax 1177 defined in Section on "ALTO Cost Type Registry" of [RFC7285], 1179 6.1. Information for IANA on proposed Cost Types 1181 When a new ALTO Cost Type is defined, accepted by the ALTO working 1182 group and requests for IANA registration MUST include the following 1183 information, detailed in Section 11.2: Identifier, Intended 1184 Semantics, Security Considerations. 1186 6.2. Information for IANA on proposed Endpoint Propeeries 1188 Likewise, an ALTO Endpoint Property Registry could serve the same 1189 purposes as the ALTO Cost Type registry. Application to IANA 1190 registration for Endpoint Properties would follow a similar process. 1192 7. Acknowledgements 1194 Thank you to Diego Lopez, He Peng and Haibin Song and the ALTO WG for 1195 fruitful discussions. 1197 8. References 1199 8.1. Normative References 1201 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1202 Requirement Levels", BCP 14, RFC 2119, 1203 DOI 10.17487/RFC2119, March 1997, 1204 . 1206 [RFC5693] Seedorf, J. and E. Burger, "Application-Layer Traffic 1207 Optimization (ALTO) Problem Statement", RFC 5693, 1208 DOI 10.17487/RFC5693, October 2009, 1209 . 1211 8.2. Informative References 1213 [draft-ietf-alto-multi-cost] 1214 S. Randriamasy, W. Roome, N. Schwan, , "Multi-Cost ALTO 1215 (work in progress), draft-ietf-alto-multi-cost", September 1216 2016. 1218 [draft-ietf-alto-performance-metrics] 1219 Q. Wu, Y. Yang, Y. Lee, D. Dhody, S. Randriamasy, , "ALTO 1220 Performance Cost Metrics (work in progress)", September 1221 2016. 1223 [draft-yang-alto-topology] 1224 Y. Yang, , "ALTO Topology Considerations (work in 1225 progress)", July 2013. 1227 [ID-alto-protocol] 1228 R.Alimi, R. Penno, Y. Yang, Eds., "ALTO Protocol, RFC 1229 7285", September 2014. 1231 [RFC7285] R. Alimi, R. Yang, R. Penno, Eds., "ALTO Protocol", 1232 September 2014. 1234 [sdnrg] "Software Defined Network Research Group, 1235 http://trac.tools.ietf.org/group/irtf/trac/wiki/sdnrg". 1237 [slides-88-alto-5-topology] 1238 G. Bernstein, Y. Lee, Y. Yang, , , "ALTO Topology Service: 1239 Use Cases, Requirements and Framework (presentation slides 1240 IETF88 ALTO WG session), 1241 http://tools.ietf.org/agenda/88/slides/ 1242 slides-88-alto-5.pdf", November 2013. 1244 Authors' Addresses 1246 Sabine Randriamasy 1247 Nokia Bell Labs 1248 Route de Villejust 1249 NOZAY 91460 1250 FRANCE 1252 Email: Sabine.Randriamasy@nokia-bell-labs.com 1253 Richard Yang 1254 Yale University 1255 51 Prospect st 1256 New Haven, CT 06520 1257 USA 1259 Email: yry@cs.yale.edu 1261 Qin Wu 1262 Huawei 1263 101 Software Avenue, Yuhua District 1264 Nanjing, Jiangsu 210012 1265 China 1267 Email: sunseawq@huawei.com 1269 Lingli Deng 1270 China Mobile 1271 China 1273 Email: denglingli@chinamobile.com 1275 Nico Schwan 1276 Thales Deutschland 1278 Email: nico.schwan@thalesgroup.com