An Extension for Application-Layer Traffic Optimization (ALTO): Entity Property Maps
draft-ietf-alto-unified-props-new-24

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, Vijay Gurbani <vijay.gurbani@gmail.com>, alto-chairs@ietf.org, alto@ietf.org, draft-ietf-alto-unified-props-new@ietf.org, martin.h.duke@gmail.com, rfc-editor@rfc-editor.org, vijay.gurbani@gmail.com
Subject: Protocol Action: 'An ALTO Extension: Entity Property Maps' to Proposed Standard (draft-ietf-alto-unified-props-new-23.txt)

The IESG has approved the following document:
- 'An ALTO Extension: Entity Property Maps'
  (draft-ietf-alto-unified-props-new-23.txt) as Proposed Standard

This document is the product of the Application-Layer Traffic Optimization
Working Group.

The IESG contact persons are Zaheduzzaman Sarker and Martin Duke.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-alto-unified-props-new/

Ballot Text

Technical Summary

   This document extends the base Application-Layer Traffic Optimization
   (ALTO) Protocol by generalizing the concept of "endpoint properties"
   to entities defined by a wide set of objects, instead of only IP
   addresses.  Further, these properties are presented as maps, similar
   to the network and cost maps in the base ALTO protocol.  The protocol
   is extended in two major directions.  First, from endpoints
   restricted to IP addresses to entities covering a wider and
   extensible set of objects; second, from properties on specific
   endpoints to entire entity property maps.  These extensions introduce
   additional features allowing entities and property values to be
   specific to a given information resource.  This is made possible by a
   generic and flexible design of entity and property types.

Working Group Summary

  The working group process has been uncontroversial.

Document Quality

  There are three known implementations. As with all ALTO documents,
  the work does not have a clear deployment roadmap.

Personnel

 The document shepherd is Vijay K. Gurbani, and the responsible area director is
Martin Duke.

RFC Editor Note