%% You should probably cite draft-shi-alto-yang-model-03 instead of this revision.
@techreport{shi-alto-yang-model-00,
	number =	{draft-shi-alto-yang-model-00},
	type =		{Internet-Draft},
	institution =	{Internet Engineering Task Force},
	publisher =	{Internet Engineering Task Force},
	note =		{Work in Progress},
	url =		{https://datatracker.ietf.org/doc/html/draft-shi-alto-yang-model-00},
        author =	{Xiao Shi and Y. Richard Yang and Michael Scharf},
	title =		{{A YANG Data Model for Base ALTO Data and Services}},
	pagetotal =	66,
	year =		,
	month =		,
	day =		,
	abstract =	{The Application-Layer Traffic Optimization (ALTO) protocol {[}RFC7285{]} defines a set of network information services, including the network- map service, the cost-map service, the filtered map services, the endpoint property service, and the endpoint cost service. A meta service, called the information resource directory (IRD) service, allows an ALTO server to provide ALTO clients with meta information (e.g., the access URI) about each resource and service it provides. {[}RFC7285{]} uses a RESTful design and encodes client request parameters and server responses using JSON. One may consider that most of these services are based on data maintained at an ALTO server. Hence, in this document, we explore how one may use the data modeling language YANG {[}RFC6020{]} to specify the services defined in {[}RFC7285{]}. We first define two YANG models for RPC specification and data instance description of of ALTO services. We then discuss the "standard operations" defined in NETCONF/RESTCONF to evaluate potential integration.},
}