rfc8896v4.txt		rfc8896.txt
	skipping to change at line 1192 ¶		skipping to change at line 1192 ¶
	For cost type "num-routingcost", the solicited ALTO Server has		For cost type "num-routingcost", the solicited ALTO Server has
	defined 3 different daily patterns, each represented by a Calendar to		defined 3 different daily patterns, each represented by a Calendar to
	cover the week of Monday, June 30th at 00:00 to Sunday, July 6th		cover the week of Monday, June 30th at 00:00 to Sunday, July 6th
	23:59:		23:59:
	* C1 for Monday, Tuesday, Wednesday, and Thursday (weekdays)		* C1 for Monday, Tuesday, Wednesday, and Thursday (weekdays)
	* C2 for Saturday and Sunday (weekends)		* C2 for Saturday and Sunday (weekends)
	* C3 for Friday (maintenance outage on July 4, 2019 from 02:00:00		* C3 for Friday (maintenance outage on July 4, 2019 from 02:00:00
	GMT to 04:00:00 GMT or a big holiday such as New Year evening).		GMT to 04:00:00 GMT or a big holiday that is widely celebrated and
			generates massive connections).
	In the following example, the ALTO Client sends its request on		In the following example, the ALTO Client sends its request on
	Tuesday, July 1st 2019 at 13:15.		Tuesday, July 1st 2019 at 13:15.
	The "routingcost" values are assumed to be encoded in 3 digits.		The "routingcost" values are assumed to be encoded in 3 digits.
	POST /calendar/endpointcost/lookup HTTP/1.1		POST /calendar/endpointcost/lookup HTTP/1.1
	Host: custom.alto.example.com		Host: custom.alto.example.com
	Content-Length: 304		Content-Length: 304
	Content-Type: application/alto-endpointcostparams+json		Content-Type: application/alto-endpointcostparams+json
End of changes. 1 change blocks.
	1 lines changed or deleted		2 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/