[alto] I-D Action: draft-ietf-alto-oam-yang-17.txt
Internet-Draft draft-ietf-alto-oam-yang-17.txt is now available. It is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title: YANG Data Models for the Application-Layer Traffic Optimization (ALTO) Protocol Authors: Jingxuan Jensen Zhang Dhruv Dhody Kai Gao Roland Schott Qiufang Ma Name:draft-ietf-alto-oam-yang-17.txt Pages: 86 Dates: 2024-01-19 Abstract: This document defines a YANG data model for Operations, Administration, and Maintenance (OAM) & Management of the Application-Layer Traffic Optimization (ALTO) Protocol. The operator of an ALTO server can use this data model to (1) set up the ALTO server, (2) configure server discovery, (3) create, update and remove ALTO information resources, (4) manage the access control of each ALTO information resource, and (5) collect statistical data from the ALTO server. The application provider can also use this data model to configure ALTO clients to communicate with known ALTO servers. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-17.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-oam-yang-17 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-oam-yang-16.txt
Internet-Draft draft-ietf-alto-oam-yang-16.txt is now available. It is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title: YANG Data Models for the Application-Layer Traffic Optimization (ALTO) Protocol Authors: Jingxuan Jensen Zhang Dhruv Dhody Kai Gao Roland Schott Qiufang Ma Name:draft-ietf-alto-oam-yang-16.txt Pages: 85 Dates: 2024-01-10 Abstract: This document defines a YANG data model for Operations, Administration, and Maintenance (OAM) & Management of the Application-Layer Traffic Optimization (ALTO) Protocol. The operator of an ALTO server can use this data model to (1) set up the ALTO server, (2) configure server discovery, (3) create, update and remove ALTO information resources, (4) manage the access control of each ALTO information resource, and (5) collect statistical data from the ALTO server. The application provider can also use this data model to configure ALTO clients to communicate with known ALTO servers. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-16.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-oam-yang-16 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-22.txt
Internet-Draft draft-ietf-alto-new-transport-22.txt is now available. It is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title: The ALTO Transport Information Publication Service Authors: Kai Gao Roland Schott Yang Richard Yang Lauren Delwiche Lachlan Keller Name:draft-ietf-alto-new-transport-22.txt Pages: 42 Dates: 2024-01-03 Abstract: The ALTO Protocol (RFC 7285) leverages HTTP/1.1 and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources and the server responds with the complete content of each resource one at a time. ALTO incremental updates using Server-Sent Events (SSE) (RFC 8895) defines a multiplexing protocol on top of HTTP/1.x, so that an ALTO server can incrementally push resource updates to clients whenever monitored network information resources change, allowing the clients to monitor multiple resources at the same time. However, HTTP/2 and later versions already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. To take advantage of newer HTTP features, this document introduces the ALTO Transport Information Publication Service (TIPS). TIPS uses an incremental RESTful design to give an ALTO client the new capability to explicitly, concurrently (non-blocking) request (pull) specific incremental updates using native HTTP/2 or HTTP/3, while still functioning for HTTP/1.1. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-22.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-22 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-21.txt
Internet-Draft draft-ietf-alto-new-transport-21.txt is now available. It is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title: The ALTO Transport Information Publication Service Authors: Kai Gao Roland Schott Yang Richard Yang Lauren Delwiche Lachlan Keller Name:draft-ietf-alto-new-transport-21.txt Pages: 42 Dates: 2023-12-06 Abstract: The ALTO Protocol (RFC 7285) leverages HTTP/1.1 and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources and the server responds with the complete content of each resource one at a time. ALTO incremental updates using Server-Sent Events (SSE) (RFC 8895) defines a multiplexing protocol on top of HTTP/1.x, so that an ALTO server can incrementally push resource updates to clients whenever monitored network information resources change, allowing the clients to monitor multiple resources at the same time. However, HTTP/2 and later versions already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. To take advantage of newer HTTP features, this document introduces the ALTO Transport Information Publication Service (TIPS). TIPS uses an incremental RESTful design to give an ALTO client the new capability to explicitly, concurrently (non-blocking) request (pull) specific incremental updates using native HTTP/2 or HTTP/3, while still functioning for HTTP/1.1. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-21.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-21 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-20.txt
Internet-Draft draft-ietf-alto-new-transport-20.txt is now available. It is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title: The ALTO Transport Information Publication Service Authors: Kai Gao Roland Schott Yang Richard Yang Lauren Delwiche Lachlan Keller Name:draft-ietf-alto-new-transport-20.txt Pages: 42 Dates: 2023-11-30 Abstract: The ALTO Protocol (RFC 7285) leverages HTTP/1.1 and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources and the server responds with the complete content of each resource one at a time. ALTO incremental updates using Server-Sent Events (SSE) (RFC 8895) defines a multiplexing protocol on top of HTTP/1.x, so that an ALTO server can incrementally push resource updates to clients whenever monitored network information resources change, allowing the clients to monitor multiple resources at the same time. However, HTTP/2 and later versions already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. To take advantage of newer HTTP features, this document introduces the ALTO Transport Information Publication Service (TIPS). TIPS uses an incremental RESTful design to give an ALTO client the new capability to explicitly, concurrently (non-blocking) request (pull) specific incremental updates using native HTTP/2 or HTTP/3, while still functioning for HTTP/1.1. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-20.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-20 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-19.txt
Internet-Draft draft-ietf-alto-new-transport-19.txt is now available. It is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title: The ALTO Transport Information Publication Service Authors: Kai Gao Roland Schott Yang Richard Yang Lauren Delwiche Lachlan Keller Name:draft-ietf-alto-new-transport-19.txt Pages: 42 Dates: 2023-11-27 Abstract: The ALTO Protocol (RFC 7285) leverages HTTP/1.1 and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources and the server responds with the complete content of each resource one at a time. ALTO incremental updates using Server-Sent Events (SSE) (RFC 8895) defines a multiplexing protocol on top of HTTP/1.x, so that an ALTO server can incrementally push resource updates to clients whenever monitored network information resources change, allowing the clients to monitor multiple resources at the same time. However, HTTP/2 and later versions already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. To take advantage of newer HTTP features, this document introduces the ALTO Transport Information Publication Service (TIPS). TIPS uses an incremental RESTful design to give an ALTO client the new capability to explicitly, concurrently (non-blocking) request (pull) specific incremental updates using native HTTP/2 or HTTP/3, while still functioning for HTTP/1.1. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-19.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-19 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-18.txt
Internet-Draft draft-ietf-alto-new-transport-18.txt is now available. It is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title: The ALTO Transport Information Publication Service Authors: Kai Gao Roland Schott Yang Richard Yang Lauren Delwiche Lachlan Keller Name:draft-ietf-alto-new-transport-18.txt Pages: 42 Dates: 2023-11-08 Abstract: The ALTO Protocol (RFC 7285) leverages HTTP/1.1 and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources and the server responds with the complete content of each resource one at a time. ALTO incremental updates using Server-Sent Events (SSE) (RFC 8895) defines a multiplexing protocol on top of HTTP/1.x, so that an ALTO server can incrementally push resource updates to clients whenever monitored network information resources change, allowing the clients to monitor multiple resources at the same time. However, HTTP/2 and later versions already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. To take advantage of newer HTTP features, this document introduces the ALTO Transport Information Publication Service (TIPS). TIPS uses an incremental RESTful design to give an ALTO client the new capability to explicitly, concurrently (non-blocking) request (pull) specific incremental updates using native HTTP/2 or HTTP/3, while still functioning for HTTP/1.1. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-18.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-18 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-17.txt
Internet-Draft draft-ietf-alto-new-transport-17.txt is now available. It is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title: The ALTO Transport Information Publication Service Authors: Kai Gao Roland Schott Yang Richard Yang Lauren Delwiche Lachlan Keller Name:draft-ietf-alto-new-transport-17.txt Pages: 39 Dates: 2023-10-21 Abstract: The ALTO Protocol (RFC 7285) leverages HTTP/1.1 and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources and the server responds with the complete content of each resource one at a time. ALTO incremental updates using Server-Sent Events (SSE) (RFC 8895) defines a multiplexing protocol on top of HTTP/1.x, so that an ALTO server can incrementally push resource updates to clients whenever monitored network information resources change, allowing the clients to monitor multiple resources at the same time. However, HTTP/2 and later versions already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. To take advantage of newer HTTP features, this document introduces the ALTO Transport Information Publication Service (TIPS). TIPS uses an incremental RESTful design to give an ALTO client the new capability to explicitly, concurrently (non-blocking) request (pull) specific incremental updates using native HTTP/2 or HTTP/3, while still functioning for HTTP/1.1. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-17.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-17 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-oam-yang-15.txt
Internet-Draft draft-ietf-alto-oam-yang-15.txt is now available. It is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title: YANG Data Models for the Application-Layer Traffic Optimization (ALTO) Protocol Authors: Jingxuan Jensen Zhang Dhruv Dhody Kai Gao Roland Schott Qiufang Ma Name:draft-ietf-alto-oam-yang-15.txt Pages: 79 Dates: 2023-10-19 Abstract: This document defines a YANG data model for Operations, Administration, and Maintenance (OAM) & Management of the Application-Layer Traffic Optimization (ALTO) Protocol. The operator of an ALTO server can use this data model to (1) set up the ALTO server, (2) configure server discovery, (3) create, update and remove ALTO information resources, (4) manage the access control of each ALTO information resource, and (5) collect statistical data from the ALTO server. The application provider can also use this data model to configure ALTO clients to communicate with known ALTO servers. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-15.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-oam-yang-15 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-oam-yang-14.txt
Internet-Draft draft-ietf-alto-oam-yang-14.txt is now available. It is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title: YANG Data Models for the Application-Layer Traffic Optimization (ALTO) Protocol Authors: Jingxuan Jensen Zhang Dhruv Dhody Kai Gao Roland Schott Qiufang Ma Name:draft-ietf-alto-oam-yang-14.txt Pages: 79 Dates: 2023-10-18 Abstract: This document defines a YANG data model for Operations, Administration, and Maintenance (OAM) & Management of the Application-Layer Traffic Optimization (ALTO) Protocol. The operator of an ALTO server can use this data model to (1) set up the ALTO server, (2) configure server discovery, (3) create, update and remove ALTO information resources, (4) manage the access control of each ALTO information resource, and (5) collect statistical data from the ALTO server. The application provider can also use this data model to configure ALTO clients to communicate with known ALTO servers. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-14.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-oam-yang-14 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-oam-yang-13.txt
Internet-Draft draft-ietf-alto-oam-yang-13.txt is now available. It is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title: YANG Data Models for the Application-Layer Traffic Optimization (ALTO) Protocol Authors: Jingxuan Jensen Zhang Dhruv Dhody Kai Gao Roland Schott Qiufang Ma Name:draft-ietf-alto-oam-yang-13.txt Pages: 79 Dates: 2023-10-18 Abstract: This document defines a YANG data model for Operations, Administration, and Maintenance (OAM) & Management of the Application-Layer Traffic Optimization (ALTO) Protocol. The operator of an ALTO server can use this data model to (1) set up the ALTO server, (2) configure server discovery, (3) create, update and remove ALTO information resources, (4) manage the access control of each ALTO information resource, and (5) collect statistical data from the ALTO server. The application provider can also use this data model to configure ALTO clients to communicate with known ALTO servers. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-13.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-oam-yang-13 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-16.txt
Internet-Draft draft-ietf-alto-new-transport-16.txt is now available. It is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title: The ALTO Transport Information Publication Service Authors: Kai Gao Roland Schott Yang Richard Yang Lauren Delwiche Lachlan Keller Name:draft-ietf-alto-new-transport-16.txt Pages: 39 Dates: 2023-10-18 Abstract: The ALTO Protocol (RFC 7285) leverages HTTP/1.1 and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources and the server responds with the complete content of each resource one at a time. ALTO incremental updates using Server-Sent Events (SSE) (RFC 8895) defines a multiplexing protocol on top of HTTP/1.x, so that an ALTO server can incrementally push resource updates to clients whenever monitored network information resources change, allowing the clients to monitor multiple resources at the same time. However, HTTP/2 and later versions already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. To take advantage of newer HTTP features, this document introduces the ALTO Transport Information Publication Service (TIPS). TIPS uses an incremental RESTful design to give an ALTO client the new capability to explicitly, concurrently (non-blocking) request (pull) specific incremental updates using native HTTP/2 or HTTP/3, while still functioning for HTTP/1.1. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-16.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-16 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-15.txt
Internet-Draft draft-ietf-alto-new-transport-15.txt is now available. It is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title: The ALTO Transport Information Publication Service Authors: Kai Gao Roland Schott Yang Richard Yang Lauren Delwiche Lachlan Keller Name:draft-ietf-alto-new-transport-15.txt Pages: 42 Dates: 2023-10-10 Abstract: The ALTO Protocol (RFC 7285) leverages HTTP/1.1 and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources and the server responds with the complete content of each resource one at a time. ALTO incremental updates using Server-Sent Events (SSE) (RFC 8895) defines a multiplexing protocol on top of HTTP/1.x, so that an ALTO server can incrementally push resource updates to clients whenever monitored network information resources change, allowing the clients to monitor multiple resources at the same time. However, HTTP/2 and later versions already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. To take advantage of newer HTTP features, this document introduces the ALTO Transport Information Publication Service (TIPS). TIPS uses an incremental RESTful design to give an ALTO client the new capability to explicitly, concurrently (non-blocking) request (pull) specific incremental updates using native HTTP/2 or HTTP/3, while still functioning for HTTP/1.1. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-15.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-15 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-14.txt
Internet-Draft draft-ietf-alto-new-transport-14.txt is now available. It is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title: The ALTO Transport Information Publication Service Authors: Kai Gao Roland Schott Yang Richard Yang Lauren Delwiche Lachlan Keller Name:draft-ietf-alto-new-transport-14.txt Pages: 54 Dates: 2023-09-22 Abstract: The ALTO Protocol (RFC 7285) leverages HTTP/1.1 and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources, and the server responds with the complete content of each resource one at a time. ALTO incremental updates using Server-Sent Events (SSE) (RFC 8895) defines a multiplexing protocol on top of HTTP/1.x, so that an ALTO server can incrementally push resource updates to clients whenever monitored network information resources change, allowing the clients to monitor multiple resources at the same time. However, HTTP/2 and later versions already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. To take advantage of newer HTTP features, this document introduces the ALTO Transport Information Publication Service (TIPS). TIPS uses an incremental RESTful design to give an ALTO client the new capability to explicitly, concurrently (non-blocking) request (pull) specific incremental updates using native HTTP/2 or HTTP/3, while still functioning for HTTP/1.1. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-14.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-14 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-oam-yang-12.txt
Internet-Draft draft-ietf-alto-oam-yang-12.txt is now available. It is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title: YANG Data Models for the Application-Layer Traffic Optimization (ALTO) Protocol Authors: Jingxuan Jensen Zhang Dhruv Dhody Kai Gao Roland Schott Qiufang Ma Name:draft-ietf-alto-oam-yang-12.txt Pages: 79 Dates: 2023-09-22 Abstract: This document defines a YANG data model for Operations, Administration, and Maintenance (OAM) & Management of the Application-Layer Traffic Optimization (ALTO) Protocol. The operator of an ALTO server can use this data model to (1) set up the ALTO server, (2) configure server discovery, (3) create, update and remove ALTO information resources, (4) manage the access control of each ALTO information resource, and (5) collect statistical data from the ALTO server. The application provider can also use this data model to configure ALTO clients to communicate with known ALTO servers. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-12.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-oam-yang-12 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-13.txt
Internet-Draft draft-ietf-alto-new-transport-13.txt is now available. It is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title: The ALTO Transport Information Publication Service Authors: Kai Gao Roland Schott Yang Richard Yang Lauren Delwiche Lachlan Keller Name:draft-ietf-alto-new-transport-13.txt Pages: 54 Dates: 2023-09-19 Abstract: The ALTO Protocol (RFC 7285) leverages HTTP/1.1 and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources, and the server responds with the complete content of each resource one at a time. ALTO incremental updates using Server-Sent Events (SSE) (RFC 8895) defines a multiplexing protocol on top of HTTP/1.x, so that an ALTO server can incrementally push resource updates to clients whenever monitored network information resources change, allowing the clients to monitor multiple resources at the same time. However, HTTP/2 and later versions already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. To take advantage of newer HTTP features, this document introduces the ALTO Transport Information Publication Service (TIPS). TIPS uses an incremental RESTful design to give an ALTO client the new capability to explicitly, concurrently (non-blocking) request (pull) specific incremental updates using native HTTP/2 or HTTP/3, while still functioning for HTTP/1.1. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-13.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-13 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-oam-yang-11.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title : YANG Data Models for the Application-Layer Traffic Optimization (ALTO) Protocol Authors : Jingxuan Jensen Zhang Dhruv Dhody Kai Gao Roland Schott Qiufang Ma Filename: draft-ietf-alto-oam-yang-11.txt Pages : 81 Date: 2023-07-24 Abstract: This document defines a YANG data model for Operations, Administration, and Maintenance (OAM) & Management of the Application-Layer Traffic Optimization (ALTO) Protocol. The operator of an ALTO server can use this data model to (1) set up the ALTO server, (2) configure server discovery, (3) create, update and remove ALTO information resources, (4) manage the access control of each ALTO information resource, and (5) collect statistical data from the ALTO server. The application provider can also use this data model to configure ALTO clients to communicate with known ALTO servers. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-11.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-oam-yang-11 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-12.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title : The ALTO Transport Information Publication Service Authors : Roland Schott Yang Richard Yang Kai Gao Lauren Delwiche Lachlan Keller Filename: draft-ietf-alto-new-transport-12.txt Pages : 54 Date: 2023-07-24 Abstract: The ALTO Protocol (RFC 7285) leverages HTTP/1.1 and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources, and the server responds with the complete content of each resource one at a time. ALTO incremental updates using Server-Sent Events (SSE) (RFC 8895) defines a multiplexing protocol on top of HTTP/1.x, so that an ALTO server can incrementally push resource updates to clients whenever monitored network information resources change, allowing the clients to monitor multiple resources at the same time. However, HTTP/2 and later versions already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. To take advantage of newer HTTP features, this document introduces the ALTO Transport Information Publication Service (TIPS). TIPS uses an incremental RESTful design to give an ALTO client the new capability to explicitly, concurrently (non-blocking) request (pull) specific incremental updates using native HTTP/2 or HTTP/3, while still functioning for HTTP/1.1. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-12.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-12 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-11.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title : The ALTO Transport Information Publication Service Authors : Roland Schott Yang Richard Yang Kai Gao Lauren Delwiche Lachlan Keller Filename: draft-ietf-alto-new-transport-11.txt Pages : 49 Date: 2023-06-16 Abstract: The ALTO Protocol (RFC 7285) leverages HTTP/1.x and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources, and the server responds with the complete content of each resource one at a time. ALTO incremental updates using Server-Sent Events (SSE) (RFC 8895) defines a multiplexing protocol on top of HTTP/1.x, so that an ALTO server can incrementally push resource updates to clients whenever monitored network information resources change, allowing the clients to monitor multiple resources at the same time. However, HTTP/2 and later versions already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. To take advantage of newer HTTP features, this document introduces the ALTO Transport Information Publication Service (TIPS). TIPS uses an incremental RESTful design to give an ALTO client the new capability to explicitly, concurrently (non-blocking) request (pull) specific incremental updates using native HTTP/2 or HTTP/3, while still functioning for HTTP/1.x. TIPS also provides for an ALTO server to concurrently push specific incremental updates using native HTTP/2 or HTTP/3 server push. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-11.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-11 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-oam-yang-10.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title : YANG Data Models for the Application-Layer Traffic Optimization (ALTO) Protocol Authors : Jingxuan Jensen Zhang Dhruv Dhody Kai Gao Roland Schott Qiufang Ma Filename: draft-ietf-alto-oam-yang-10.txt Pages : 81 Date: 2023-06-15 Abstract: This document defines a YANG data model for Operations, Administration, and Maintenance (OAM) & Management of Application- Layer Traffic Optimization (ALTO) Protocol. The operator of an ALTO server can use this data model to (1) set up the ALTO server, (2) configure server discovery, (3) create, update and remove ALTO information resources, (4) manage the access control of each ALTO information resource, and (5) collect statistical data of the ALTO server. The application provider can also use this data model to configure ALTO clients to communicate with known ALTO servers. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-10.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-oam-yang-10 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-oam-yang-09.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title : YANG Data Models for the Application-Layer Traffic Optimization (ALTO) Protocol Authors : Jingxuan Jensen Zhang Dhruv Dhody Kai Gao Roland Schott Qiufang Ma Filename: draft-ietf-alto-oam-yang-09.txt Pages : 81 Date: 2023-06-13 Abstract: This document defines a YANG data model for Operations, Administration, and Maintenance (OAM) & Management of Application- Layer Traffic Optimization (ALTO) Protocol. The operator of an ALTO server can use this data model to (1) set up the ALTO server, (2) configure server discovery, (3) create, update and remove ALTO information resources, (4) manage the access control of each ALTO information resource, and (5) collect statistical data of the ALTO server. The application provider can also use this data model to configure ALTO clients to communicate with known ALTO servers. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-09.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-oam-yang-09 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-10.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title : The ALTO Transport Information Publication Service Authors : Roland Schott Yang Richard Yang Kai Gao Lauren Delwiche Lachlan Keller Filename: draft-ietf-alto-new-transport-10.txt Pages : 49 Date: 2023-06-12 Abstract: The ALTO Protocol (RFC 7285) leverages HTTP/1.x and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources, and the server responds with the complete content of each resource one at a time. ALTO incremental updates using Server-Sent Events (SSE) (RFC 8895) defines a multiplexing protocol on top of HTTP/1.x, so that an ALTO server can incrementally push resource updates to clients whenever monitored network information resources change, allowing the clients to monitor multiple resources at the same time. However, HTTP/2 and later versions already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. To take advantage of newer HTTP features, this document introduces the ALTO Transport Information Publication Service (TIPS). TIPS uses an incremental RESTful design to give an ALTO client the new capability to explicitly, concurrently (non-blocking) request (pull) specific incremental updates using native HTTP/2 or HTTP/3, while still functioning for HTTP/1.x. TIPS also provides for an ALTO server to concurrently push specific incremental updates using native HTTP/2 or HTTP/3 server push. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-10.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-10 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-oam-yang-08.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title : YANG Data Models for the Application-Layer Traffic Optimization (ALTO) Protocol Authors : Jingxuan Jensen Zhang Dhruv Dhody Kai Gao Roland Schott Qiufang Ma Filename: draft-ietf-alto-oam-yang-08.txt Pages : 81 Date: 2023-05-30 Abstract: This document defines a YANG data model for Operations, Administration, and Maintenance (OAM) & Management of Application- Layer Traffic Optimization (ALTO) Protocol. The operator of an ALTO server can use this data model to (1) set up the ALTO server, (2) configure server discovery, (3) create, update and remove ALTO information resources, (4) manage the access control of each ALTO information resource, and (5) collect statistical data of the ALTO server. The application provider can also use this data model to configure ALTO clients to communicate with known ALTO servers. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-08.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-oam-yang-08 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-09.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title : The ALTO Transport Information Publication Service Authors : Roland Schott Yang Richard Yang Kai Gao Lauren Delwiche Lachlan Keller Filename: draft-ietf-alto-new-transport-09.txt Pages : 47 Date: 2023-05-24 Abstract: The ALTO Protocol (RFC 7285) leverages HTTP/1.x and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources, and the server responds with the complete content of each resource one at a time. ALTO incremental updates using Server-Sent Events (SSE) (RFC 8895) defines a multiplexing protocol on top of HTTP/1.x, so that an ALTO server can incrementally push resource updates to clients whenever monitored network information resources change, allowing the clients to monitor multiple resources at the same time. However, HTTP/2 and later versions already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. To take advantage of newer HTTP features, this document introduces the ALTO Transport Information Publication Service (TIPS). TIPS uses an incremental RESTful design to give an ALTO client the new capability to explicitly, concurrently (non-blocking) request (pull) specific incremental updates using native HTTP/2 or HTTP/3, while still functioning for HTTP/1.x. TIPS also provides for an ALTO server to concurrently push specific incremental updates using native HTTP/2 or HTTP/3 server push. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-09.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-09 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-oam-yang-07.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title : YANG Data Models for the Application-Layer Traffic Optimization (ALTO) Protocol Authors : Jingxuan Jensen Zhang Dhruv Dhody Kai Gao Roland Schott Qiufang Ma Filename: draft-ietf-alto-oam-yang-07.txt Pages : 78 Date: 2023-05-15 Abstract: This document defines YANG data models for Operations, Administration, and Maintenance (OAM) & Management of Application- Layer Traffic Optimization (ALTO) Protocol. The operator can use these data models to set up an ALTO server, create, update and remove ALTO information resources, manage the access control, configure server discovery, and collect statistical data. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-07.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-oam-yang-07 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-08.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title : The ALTO Transport Information Publication Service Authors : Roland Schott Y. Richard Yang Kai Gao Lauren Delwiche Lachlan Keller Filename: draft-ietf-alto-new-transport-08.txt Pages : 48 Date: 2023-05-15 Abstract: The ALTO Protocol (RFC 7285) leverages HTTP/1.x and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources, and the server responds with the complete content of each resource one at a time. ALTO incremental updates using Server-Sent Events (SSE) (RFC 8895) defines a multiplexing protocol on top of HTTP/1.x, so that an ALTO server can incrementally push resource updates to clients whenever monitored network information resources change, allowing the clients to monitor multiple resources at the same time. However, HTTP/2 and later versions already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. To take advantage of newer HTTP features, this document introduces the ALTO Transport Information Publication Service (TIPS). TIPS uses an incremental RESTful design to give an ALTO client the new capability to explicitly, concurrently (non-blocking) request (pull) specific incremental updates using native HTTP/2 or HTTP/3, while still functioning for HTTP/1.x. TIPS also provides for an ALTO server to concurrently push specific incremental updates using native HTTP/2 or HTTP/3 server push. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-08.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-08 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-07.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title : The ALTO Transport Information Publication Service Authors : Roland Schott Y. Richard Yang Kai Gao Lauren Delwiche Lachlan Keller Filename: draft-ietf-alto-new-transport-07.txt Pages : 48 Date: 2023-03-13 Abstract: The ALTO Protocol (RFC 7285) leverages HTTP/1.x and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources, and the server responds with the complete content of each resource one at a time. ALTO incremental updates using Server-Sent Events (SSE) (RFC 8895) defines a multiplexing protocol on top of HTTP/1.x, so that an ALTO server can incrementally push resource updates to clients whenever monitored network information resources change, allowing the clients to monitor multiple resources at the same time. However, HTTP/2 and later versions already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. To take advantage of newer HTTP features, this document introduces the ALTO Transport Information Publication Service (TIPS). TIPS uses an incremental RESTful design to give an ALTO client the new capability to explicitly, concurrently (non-blocking) request (pull) specific incremental updates using native HTTP/2 or HTTP/3, while still functioning for HTTP/1.x. TIPS also provides an ALTO server to concurrently push specific incremental updates using native HTTP/2 or HTTP/3 server push. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-07.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-07 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-oam-yang-06.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the Application-Layer Traffic Optimization (ALTO) WG of the IETF. Title : YANG Data Models for the Application-Layer Traffic Optimization (ALTO) Protocol Authors : Jingxuan Jensen Zhang Dhruv Dhody Kai Gao Roland Schott Qiufang Ma Filename: draft-ietf-alto-oam-yang-06.txt Pages : 67 Date: 2023-03-12 Abstract: This document defines YANG data models for Operations, Administration, and Maintenance (OAM) & Management of Application- Layer Traffic Optimization (ALTO) Protocol. The operator can use these data models to set up an ALTO server, create, update and remove ALTO information resources, manage the access control, configure server discovery, and collect statistical data. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-06.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-oam-yang-06 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-oam-yang-05.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : A Yang Data Model for OAM and Management of ALTO Protocol Authors : Jingxuan Jensen Zhang Dhruv Dhody Kai Gao Roland Schott Qiufang Ma Filename: draft-ietf-alto-oam-yang-05.txt Pages : 67 Date: 2023-02-23 Abstract: This document defines a YANG data model for Operations, Administration, and Maintenance (OAM) & Management of Application- Layer Traffic Optimization (ALTO) Protocol. The operator can use the data model to set up the ALTO server, create, update and remove ALTO information resources, manage the access control, configure server discovery, and collect statistical data. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-05.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-oam-yang-05 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-oam-yang-04.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : A Yang Data Model for OAM and Management of ALTO Protocol Authors : Jingxuan Jensen Zhang Dhruv Dhody Kai Gao Roland Schott Qiufang Ma Filename: draft-ietf-alto-oam-yang-04.txt Pages : 67 Date: 2023-02-23 Abstract: This document defines a YANG data model for Operations, Administration, and Maintenance (OAM) & Management of Application- Layer Traffic Optimization (ALTO) Protocol. The operator can use the data model to set up the ALTO server, create, update and remove ALTO information resources, manage the access control, configure server discovery, and collect statistical data. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-04.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-oam-yang-04 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-06.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Transport Information Publication Service Authors : Roland Schott Y. Richard Yang Kai Gao Lauren Delwiche Lachlan Keller Filename: draft-ietf-alto-new-transport-06.txt Pages : 38 Date: 2023-02-21 Abstract: The ALTO protocol (RFC 7285) leverages HTTP/1.x and is designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources, and the server responds with the complete content of each resource one at a time. ALTO/SSE (RFC 8895) defines a multiplexing protocol on top of HTTP/1.x, so that the server can incrementally push resource updates to the client whenever monitored network information resources change, allowing the client to monitor multiple resources at the same time. However, HTTP/2 and later versions already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. To take advantage of newer HTTP features, this document introduces the ALTO Transport Information Publication Service (TIPS). TIPS allows the naming of (i.e., assigning resource identifiers to) individual incremental updates to multiple ALTO information resources, and the distribution of those names. It gives an ALTO client the capability to explicitly request (pull) a specific incremental update. It also provides an ALTO server the capability to push a specific incremental update. This document defines TIPS as a service, with client pull and server push. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-06.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-06 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-oam-yang-03.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : A Yang Data Model for OAM and Management of ALTO Protocol Authors : Jingxuan Jensen Zhang Dhruv Dhody Kai Gao Roland Schott Filename: draft-ietf-alto-oam-yang-03.txt Pages : 65 Date: 2023-02-10 Abstract: This document defines a YANG data model for Operations, Administration, and Maintenance (OAM) & Management of Application- Layer Traffic Optimization (ALTO) Protocol. The operator can use the data model to create and update ALTO information resources, manage the access control, configure server-to-server communication and server discovery, and collect statistical data. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-03.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-oam-yang-03 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-05.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Transport Information Publication Service Authors : Roland Schott Y. Richard Yang Kai Gao Lachlan Keller Filename: draft-ietf-alto-new-transport-05.txt Pages : 32 Date: 2023-02-06 Abstract: The ALTO base protocol [RFC7285] is based on HTTP/1.x, designed for the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources, and the server sends the complete content of each information resource to the client one by one. To support the use case that an ALTO client can monitor multiple resources at the same time and the ALTO server sends only their updates, the ALTO Working Group introduced ALTO/SSE [RFC8895], which defines a new, SSE-based multiplexing protocol on top of HTTP/1.x, to allow the server to concurrently, and incrementally push updates to the client whenever monitored network information resources change. However, newer versions of HTTP (e.g., HTTP/2 [RFC7540]) already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. This document introduces the ALTO transport information publication service (TIPS), which allows the naming of (i.e., assigning resource identifiers to) individual incremental updates to multiple ALTO information resources and the distribution of the naming, enabling ALTO to take advantage of newer HTTP versions. In particular, it gives an ALTO client the new capability to explicitly request (pull) a specific incremental update. It also provides an ALTO server the new capability to push a specific incremental update using native HTTP/2 or HTTP/3 server push. This document defines TIPS as a service, independent of client pull or server push. A companion document [draft-schott-alto-new-transport-push] defines the complete server- push ALTO transport based on ALTO TIPS. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-05.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-05 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-04.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Transport Information Publication Service Authors : Roland Schott Y. Richard Yang Kai Gao Jingxuan Jensen Zhang Filename: draft-ietf-alto-new-transport-04.txt Pages : 32 Date: 2022-12-31 Abstract: The ALTO base protocol [RFC7285] is based on HTTP/1.x, focusing on the simple, sequential request-reply use case, in which an ALTO client requests a sequence of information resources, and the server sends the complete content of each information resource to the client one by one. ALTO/SSE [RFC8895] defines a new transport design to allow an ALTO client to request the monitoring of multiple resources, and the server can then continuously, concurrently, and incrementally push updates whenever monitored network information resources change. But ALTO/SSE assumes an HTTP/1.x setting, and essentially designs a new concurrent transport protocol on top of a sequential HTTP/1.x connection, but newer versions of HTTP (e.g., HTTP/2 [RFC7540]) already support concurrent, non-blocking transport of multiple streams in the same HTTP connection. This document introduces the ALTO transport information publication service (TIPS), which allows the naming of individual incremental updates to multiple ALTO information resources and the distribution of the naming, enabling ALTO to take advantage of newer HTTP versions. In particular, it gives an ALTO client the new capability to explicitly request (pull) a specific incremental update. It also provides an ALTO server the new capability to push a specific incremental update using native HTTP/2 or HTTP/3 server push. This document defines TIPS as a service, independent of client pull or server push. A companion document [draft-schott-alto-new-transport-push] defines server-push ALTO transport based on ALTO TIPS. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-04.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-04 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-oam-yang-02.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : A Yang Data Model for OAM and Management of ALTO Protocol Authors : Jingxuan Jensen Zhang Dhruv Dhody Kai Gao Roland Schott Filename: draft-ietf-alto-oam-yang-02.txt Pages : 49 Date: 2022-10-24 Abstract: This document defines a YANG data model for Operations, Administration, and Maintenance (OAM) & Management of Application- Layer Traffic Optimization (ALTO) Protocol. The operator can use the data model to create and update ALTO information resources, manage the access control, configure server-to-server communication and server discovery, and collect statistical data. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-02.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-oam-yang-02 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-03.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO New Transport: ALTO Transport Information Structures Authors : Roland Schott Y. Richard Yang Kai Gao Jingxuan Jensen Zhang Filename: draft-ietf-alto-new-transport-03.txt Pages : 23 Date: 2022-10-21 Abstract: The ALTO base protocol [RFC7285] defines both the ALTO information resources and their transport from the server to the client. Using HTTP/1.x as the transport protocol, the ALTO transport in the base protocol includes the limitations of HTTP/1.x. ALTO/SSE [RFC8895] defines a new transport design addressing some of the limitations, but is still based on HTTP/1.x. This document introduces ALTO new transport, which introduces ALTO transport information structures (TIS) at an ALTO server. The introduction of ALTO TIS allows at least two types of efficient transport using HTTP: (1) HTTP/2/3 independent client (long) pull allowed by non-blocking, newer HTTP, and (2) HTTP/2 specific server push. This document defines ALTO TIS and the first design. A companion document [draft-schott-alto-new-transport-push] defines server-push ALTO transport based on ALTO TIS. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-03.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-new-transport-03 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-02.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO New Transport: ALTO Transport Information Structures Authors : Roland Schott Y. Richard Yang Kai Gao Jingxuan Jensen Zhang Filename: draft-ietf-alto-new-transport-02.txt Pages : 22 Date: 2022-10-20 Abstract: The ALTO base protocol [RFC7285] defines both the ALTO information resources and their transport from the server to the client. Using HTTP/1.x as the transport protocol, the ALTO transport in the base protocol includes the limitations of HTTP/1.x. ALTO/SSE [RFC8895] defines a new transport design addressing some of the limitations, but is still based on HTTP/1.x. This document introduces ALTO new transport, which introduces ALTO transport information structures (TIS) at an ALTO server. The introduction of ALTO TIS allows at least two types of efficient transport using HTTP: (1) HTTP/2/3 independent client (long) poll allowed by non-blocking, newer HTTP, and (2) HTTP/2 specific server push. This document defines ALTO TIS and the first design. A companion document defines server-push ALTO transport based on ALTO TIS. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-02.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-new-transport-02 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-oam-yang-01.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : A Yang Data Model for OAM and Management of ALTO Protocol Authors : Jingxuan Jensen Zhang Dhruv Dhody Kai Gao Roland Schott Filename: draft-ietf-alto-oam-yang-01.txt Pages : 44 Date: 2022-07-11 Abstract: This document defines a YANG data model for Operations, Administration, and Maintenance (OAM) & Management of Application- Layer Traffic Optimization (ALTO) Protocol. The operator can use the data model to create and update ALTO information resources, manage the access control, configure server-to-server communication and server discovery, and collect statistical data. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-01.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-oam-yang-01 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-01.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO/H2: The ALTO Protocol using HTTP/2 Authors : Roland Schott Y. Richard Yang Kai Gao Jingxuan Jensen Zhang Filename: draft-ietf-alto-new-transport-01.txt Pages : 24 Date: 2022-07-11 Abstract: The ALTO base protocol [RFC7285] uses HTTP/1.x as the transport protocol and hence ALTO transport includes the limitations of HTTP/1.x. ALTO/SSE [RFC8895] addresses some of the limitations, but is still based on HTTP/1.x. This document introduces ALTO new transport, which provides the transport functions of ALTO/SSE on top of HTTP/2, for more efficient ALTO transport. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-01.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-new-transport-01 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-new-transport-00.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO/H2: The ALTO Protocol using HTTP/2 Authors : Roland Schott Y. Richard Yang Kai Gao Jingxuan Jensen Zhang Filename: draft-ietf-alto-new-transport-00.txt Pages : 24 Date: 2022-06-22 Abstract: The ALTO base protocol [RFC7285] uses HTTP/1.x as the transport protocol and hence ALTO transport includes the limitations of HTTP/1.x. ALTO/SSE [RFC8895] addresses some of the limitations, but is still based on HTTP/1.x. This document introduces ALTO new transport, which provides the transport functions of ALTO/SSE on top of HTTP/2, for more efficient ALTO transport. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-00.html Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-cost-mode-05.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : A Cost Mode Registry for the Application-Layer Traffic Optimization (ALTO) Protocol Authors : Mohamed Boucadair Qin Wu Filename: draft-ietf-alto-cost-mode-05.txt Pages : 8 Date: 2022-06-02 Abstract: This document creates a new IANA registry for tracking cost modes supported by the Application-Layer Traffic Optimization (ALTO) Protocol. Also, this document relaxes a constraint that was imposed by the ALTO specification on allowed cost mode values. This document updates RFC 7285. Editorial Note (To be removed by RFC Editor) Please update RFC statements within the document with the RFC number to be assigned to this document. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-cost-mode/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-cost-mode-05 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cost-mode-05 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-cost-mode-04.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : A Cost Mode Registry for the Application-Layer Traffic Optimization (ALTO) Protocol Authors : Mohamed Boucadair Qin Wu Filename: draft-ietf-alto-cost-mode-04.txt Pages : 7 Date: 2022-06-01 Abstract: This document creates a new IANA registry for tracking cost modes supported by the Application-Layer Traffic Optimization (ALTO) Protocol. Also, this document relaxes a constraint that was imposed by the ALTO specification on allowed cost mode values. This document updates RFC 7285. Editorial Note (To be removed by RFC Editor) Please update RFC statements within the document with the RFC number to be assigned to this document. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-cost-mode/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-cost-mode-04 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cost-mode-04 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-cost-mode-03.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : A Cost Mode Registry for the Application-Layer Traffic Optimization (ALTO) Protocol Authors : Mohamed Boucadair Qin Wu Filename: draft-ietf-alto-cost-mode-03.txt Pages : 6 Date: 2022-05-16 Abstract: This document creates a new IANA registry for tracking cost modes supported by the Application-Layer Traffic Optimization (ALTO) Protocol. Also, this document relaxes a constraint that was imposed by the ALTO specification on allowed cost mode values. This document updates RFC 7285. Editorial Note (To be removed by RFC Editor) Please update RFC statements within the document with the RFC number to be assigned to this document. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-cost-mode/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-cost-mode-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cost-mode-03 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-cost-mode-02.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : A Cost Mode Registry for the Application-Layer Traffic Optimization (ALTO) Protocol Authors : Mohamed Boucadair Qin Wu Filename: draft-ietf-alto-cost-mode-02.txt Pages : 6 Date: 2022-04-16 Abstract: This document creates a new IANA registry for tracking cost modes supported by the Application-Layer Traffic Optimization (ALTO) protocol. Also, this document relaxes a constraint that was imposed by the ALTO specification on allowed cost mode values. This document updates RFC 7285. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-cost-mode/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-cost-mode-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cost-mode-02 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-oam-yang-00.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : A Yang Data Model for OAM and Management of ALTO Protocol Authors : Jingxuan Jensen Zhang Dhruv Dhody Kai Gao Roland Schott Filename: draft-ietf-alto-oam-yang-00.txt Pages : 36 Date: 2022-04-12 Abstract: This document defines a YANG data model for Operations, Administration, and Maintenance (OAM) & Management of Application- Layer Traffic Optimization (ALTO) Protocol. The operator can use the data model to create and update ALTO information resources, manage the access control, configure server-to-server communication and server discovery, and collect statistical data. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-oam-yang/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-oam-yang-00.html Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-cost-mode-01.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : A Cost Mode Registry for the Application-Layer Traffic Optimization (ALTO) Protocol Authors : Mohamed Boucadair Qin Wu Filename: draft-ietf-alto-cost-mode-01.txt Pages : 6 Date: 2022-04-11 Abstract: This document creates a new IANA registry for tracking cost modes supported by the Application-Layer Traffic Optimization (ALTO) protocol. Also, this document relaxes a constraint that was imposed by the ALTO specification on allowed cost mode values. This document updates RFC 7285. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-cost-mode/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-cost-mode-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cost-mode-01 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-cost-mode-00.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : A Cost Mode Registry for the Application-Layer Traffic Optimization (ALTO) Protocol Authors : Mohamed Boucadair Qin Wu Filename: draft-ietf-alto-cost-mode-00.txt Pages : 6 Date: 2022-03-21 Abstract: This document creates a new IANA registry for tracking cost modes supported by the Application-Layer Traffic Optimization (ALTO) protocol. Also, this document relaxes a constraint that was imposed by the ALTO specification on allowed cost mode values. This document updates RFC 7285. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-cost-mode/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-cost-mode-00 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-performance-metrics-28.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Performance Cost Metrics Authors : Qin Wu Y. Richard Yang Young Lee Dhruv Dhody Sabine Randriamasy Luis Miguel Contreras Murillo Filename: draft-ietf-alto-performance-metrics-28.txt Pages : 39 Date: 2022-03-21 Abstract: The cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and different applications may use different types of cost metrics. Since the ALTO base protocol (RFC 7285) defines only a single cost metric (namely, the generic "routingcost" metric), if an application wants to issue a cost map or an endpoint cost request in order to identify a resource provider that offers better performance metrics (e.g., lower delay or loss rate), the base protocol does not define the cost metric to be used. This document addresses this issue by extending the specification to provide a variety of network performance metrics, including network delay, delay variation (a.k.a, jitter), packet loss rate, hop count, and bandwidth. There are multiple sources (e.g., estimation based on measurements or service-level agreement) to derive a performance metric. This document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey the source of a performance metric. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-28 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-28 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-performance-metrics-27.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Performance Cost Metrics Authors : Qin Wu Y. Richard Yang Young Lee Dhruv Dhody Sabine Randriamasy Luis Miguel Contreras Murillo Filename: draft-ietf-alto-performance-metrics-27.txt Pages : 39 Date: 2022-03-20 Abstract: The cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and different applications may use different types of cost metrics. Since the ALTO base protocol (RFC 7285) defines only a single cost metric (namely, the generic "routingcost" metric), if an application wants to issue a cost map or an endpoint cost request in order to identify a resource provider that offers better performance metrics (e.g., lower delay or loss rate), the base protocol does not define the cost metric to be used. This document addresses this issue by extending the specification to provide a variety of network performance metrics, including network delay, delay variation (a.k.a, jitter), packet loss rate, hop count, and bandwidth. There are multiple sources (e.g., estimation based on measurements or service-level agreement) to derive a performance metric. This document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey the source of a performance metric. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-27 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-27 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-path-vector-25.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : An ALTO Extension: Path Vector Authors : Kai Gao Young Lee Sabine Randriamasy Yang Richard Yang Jingxuan Jensen Zhang Filename: draft-ietf-alto-path-vector-25.txt Pages : 69 Date: 2022-03-20 Abstract: This document is an extension to the base Application-Layer Traffic Optimization (ALTO) protocol. It extends the ALTO Cost Map and ALTO Property Map services so that an application can decide which endpoint(s) to connect based on not only numerical/ordinal cost values but also fine-grained abstract information of the paths. This is useful for applications whose performance is impacted by specified components of a network on the end-to-end paths, e.g., they may infer that several paths share common links and prevent traffic bottlenecks by avoiding such paths. This extension introduces a new abstraction called Abstract Network Element (ANE) to represent these components and encodes a network path as a vector of ANEs. Thus, it provides a more complete but still abstract graph representation of the underlying network(s) for informed traffic optimization among endpoints. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-path-vector/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-path-vector-25.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-path-vector-25 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-path-vector-24.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : An ALTO Extension: Path Vector Authors : Kai Gao Young Lee Sabine Randriamasy Yang Richard Yang Jingxuan Jensen Zhang Filename: draft-ietf-alto-path-vector-24.txt Pages : 69 Date: 2022-03-07 Abstract: This document is an extension to the base Application-Layer Traffic Optimization (ALTO) protocol. It extends the ALTO Cost Map and ALTO Property Map services so that an application can decide which endpoint(s) to connect based on not only numerical/ordinal cost values but also fine-grained abstract information of the paths. This is useful for applications whose performance is impacted by specified components of a network on the end-to-end paths, e.g., they may infer that several paths share common links and prevent traffic bottlenecks by avoiding such paths. This extension introduces a new abstraction called Abstract Network Element (ANE) to represent these components and encodes a network path as a vector of ANEs. Thus, it provides a more complete but still abstract graph representation of the underlying network(s) for informed traffic optimization among endpoints. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-path-vector/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-path-vector-24.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-path-vector-24 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-path-vector-23.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : An ALTO Extension: Path Vector Authors : Kai Gao Young Lee Sabine Randriamasy Yang Richard Yang Jingxuan Jensen Zhang Filename: draft-ietf-alto-path-vector-23.txt Pages : 69 Date: 2022-03-05 Abstract: This document is an extension to the base Application-Layer Traffic Optimization (ALTO) protocol. It extends the ALTO Cost Map and ALTO Property Map services so that an application can decide which endpoint(s) to connect based on not only numerical/ordinal cost values but also fine-grained abstract information of the paths. This is useful for applications whose performance is impacted by specified components of a network on the end-to-end paths, e.g., they may infer that several paths share common links and prevent traffic bottlenecks by avoiding such paths. This extension introduces a new abstraction called Abstract Network Element (ANE) to represent these components and encodes a network path as a vector of ANEs. Thus, it provides a more complete but still abstract graph representation of the underlying network(s) for informed traffic optimization among endpoints. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-path-vector/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-path-vector-23.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-path-vector-23 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-performance-metrics-26.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Performance Cost Metrics Authors : Qin Wu Y. Richard Yang Young Lee Dhruv Dhody Sabine Randriamasy Luis Miguel Contreras Murillo Filename: draft-ietf-alto-performance-metrics-26.txt Pages : 38 Date: 2022-03-02 Abstract: The cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and different applications may use different types of cost metrics. Since the ALTO base protocol (RFC 7285) defines only a single cost metric (namely, the generic "routingcost" metric), if an application wants to issue a cost map or an endpoint cost request in order to identify a resource provider that offers better performance metrics (e.g., lower delay or loss rate), the base protocol does not define the cost metric to be used. This document addresses this issue by extending the specification to provide a variety of network performance metrics, including network delay, delay variation (a.k.a, jitter), packet loss rate, hop count, and bandwidth. There are multiple sources (e.g., estimation based on measurements or service-level agreement) to derive a performance metric. This document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey the source of a performance metric. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-26 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-26 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-performance-metrics-25.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Performance Cost Metrics Authors : Qin Wu Y. Richard Yang Young Lee Dhruv Dhody Sabine Randriamasy Luis Miguel Contreras Murillo Filename: draft-ietf-alto-performance-metrics-25.txt Pages : 38 Date: 2022-02-28 Abstract: The cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and different applications may use different types of cost metrics. Since the ALTO base protocol (RFC 7285) defines only a single cost metric (namely, the generic "routingcost" metric), if an application wants to issue a cost map or an endpoint cost request in order to identify a resource provider that offers better performance metrics (e.g., lower delay or loss rate), the base protocol does not define the cost metric to be used. This document addresses this issue by extending the specification to provide a variety of network performance metrics, including network delay, delay variation (a.k.a, jitter), packet loss rate, hop count, and bandwidth. There are multiple sources (e.g., estimation based on measurements or service-level agreement) to derive a performance metric. This document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey the source of a performance metric. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-25 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-25 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-performance-metrics-24.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Performance Cost Metrics Authors : Qin Wu Y. Richard Yang Young Lee Dhruv Dhody Sabine Randriamasy Luis Miguel Contreras Murillo Filename: draft-ietf-alto-performance-metrics-24.txt Pages : 38 Date: 2022-02-28 Abstract: The cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and different applications may use different types of cost metrics. Since the ALTO base protocol (RFC 7285) defines only a single cost metric (namely, the generic "routingcost" metric), if an application wants to issue a cost map or an endpoint cost request in order to identify a resource provider that offers better performance metrics (e.g., lower delay or loss rate), the base protocol does not define the cost metric to be used. This document addresses this issue by extending the specification to provide a variety of network performance metrics, including network delay, delay variation (a.k.a, jitter), packet loss rate, hop count, and bandwidth. There are multiple sources (e.g., estimation based on measurements or service-level agreement) to derive a performance metric. This document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey the source of a performance metric. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-24 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-24 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-performance-metrics-23.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Performance Cost Metrics Authors : Qin Wu Y. Richard Yang Young Lee Dhruv Dhody Sabine Randriamasy Luis Miguel Contreras Murillo Filename: draft-ietf-alto-performance-metrics-23.txt Pages : 38 Date: 2022-02-28 Abstract: The cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and different applications may use different types of cost metrics. Since the ALTO base protocol (RFC 7285) defines only a single cost metric (namely, the generic "routingcost" metric), if an application wants to issue a cost map or an endpoint cost request in order to identify a resource provider that offers a better delay performance, the base protocol does not define the cost metric to be used. This document addresses this issue by extending the specification to provide a variety of network performance metrics, including network delay, delay variation (a.k.a, jitter), packet loss rate, hop count, and bandwidth. There are multiple sources (e.g., estimation based on measurements or service-level agreement) to derive a performance metric. This document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey the source of a performance metric. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-23 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-23 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-unified-props-new-24.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : An ALTO Extension: Entity Property Maps Authors : Wendy Roome Sabine Randriamasy Y. Richard Yang Jingxuan Jensen Zhang Kai Gao Filename: draft-ietf-alto-unified-props-new-24.txt Pages : 63 Date: 2022-02-28 Abstract: This document specifies an extension to the base Application-Layer Traffic Optimization (ALTO) protocol that generalizes the concept of "endpoint properties", which were so far tied to IP addresses, to entities defined by a wide set of objects. Further, these properties are presented as maps, similar to the network and cost maps in the base ALTO protocol. While supporting the endpoints and related endpoint property service defined in RFC7285, the ALTO 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. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-unified-props-new/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-unified-props-new-24 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-unified-props-new-24 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-performance-metrics-22.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Performance Cost Metrics Authors : Qin Wu Y. Richard Yang Young Lee Dhruv Dhody Sabine Randriamasy Luis Miguel Contreras Murillo Filename: draft-ietf-alto-performance-metrics-22.txt Pages : 41 Date: 2022-02-27 Abstract: The cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and different applications may use different types of cost metrics. Since the ALTO base protocol (RFC 7285) defines only a single cost metric (namely, the generic "routingcost" metric), if an application wants to issue a cost map or an endpoint cost request in order to identify a resource provider that offers a better delay performance, the base protocol does not define the cost metric to be used. This document addresses this issue by extending the specification to provide a variety of network performance metrics, including network delay, delay variation (a.k.a, jitter), packet loss rate, hop count, and bandwidth. There are multiple sources (e.g., estimation based on measurements or service-level agreement) to derive a performance metric. This document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey the source of a performance metric. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-22 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-22 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-unified-props-new-23.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : An ALTO Extension: Entity Property Maps Authors : Wendy Roome Sabine Randriamasy Y. Richard Yang Jingxuan Jensen Zhang Kai Gao Filename: draft-ietf-alto-unified-props-new-23.txt Pages : 63 Date: 2022-02-25 Abstract: This document specifies an extension to the base Application-Layer Traffic Optimization (ALTO) protocol that generalizes the concept of "endpoint properties", which were so far tied to IP addresses, to entities defined by a wide set of objects. Further, these properties are presented as maps, similar to the network and cost maps in the base ALTO protocol. While supporting the endpoints and related endpoint property service defined in RFC7285, the ALTO 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. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-unified-props-new/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-unified-props-new-23 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-unified-props-new-23 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-path-vector-22.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : An ALTO Extension: Path Vector Authors : Kai Gao Young Lee Sabine Randriamasy Yang Richard Yang Jingxuan Jensen Zhang Filename: draft-ietf-alto-path-vector-22.txt Pages : 65 Date: 2022-02-25 Abstract: This document is an extension to the base Application-Layer Traffic Optimization (ALTO) protocol. It extends the ALTO Cost Map and ALTO Property Map services so that an application can decide which endpoint(s) to connect based on not only numerical/ordinal cost values but also fine-grained abstract information of the paths. This is useful for applications whose performance is impacted by specified components of a network on the end-to-end paths, e.g., they may infer that several paths share common links and prevent traffic bottlenecks by avoiding such paths. This extension introduces a new abstraction called Abstract Network Element (ANE) to represent these components and encodes a network path as a vector of ANEs. Thus, it provides a more complete but still abstract graph representation of the underlying network(s) for informed traffic optimization among endpoints. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-path-vector/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-path-vector-22.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-path-vector-22 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-cdni-request-routing-alto-22.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : Content Delivery Network Interconnection (CDNI) Request Routing: CDNI Footprint and Capabilities Advertisement using ALTO Authors : Jan Seedorf Y. Richard Yang Kevin J. Ma Jon Peterson Jingxuan Jensen Zhang Filename: draft-ietf-alto-cdni-request-routing-alto-22.txt Pages : 44 Date: 2022-02-16 Abstract: The Content Delivery Networks Interconnection (CDNI) framework in RFC 6707 defines a set of protocols to interconnect CDNs to achieve multiple goals, including extending the reach of a given CDN. A CDNI Request Routing Footprint & Capabilities Advertisement interface (FCI) is needed to achieve the goals of a CDNI. RFC 8008 defines the FCI semantics and provides guidelines on the FCI protocol, but the exact protocol is not specified. This document defines a new Application-Layer Traffic Optimization (ALTO) service, called "CDNI Advertisement Service", that provides an implementation of the FCI, following the guidelines defined in RFC 8008. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-cdni-request-routing-alto/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-cdni-request-routing-alto-22.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cdni-request-routing-alto-22 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-cdni-request-routing-alto-21.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : Content Delivery Network Interconnection (CDNI) Request Routing: CDNI Footprint and Capabilities Advertisement using ALTO Authors : Jan Seedorf Y. Richard Yang Kevin J. Ma Jon Peterson Jingxuan Jensen Zhang Filename: draft-ietf-alto-cdni-request-routing-alto-21.txt Pages : 44 Date: 2022-02-16 Abstract: The Content Delivery Networks Interconnection (CDNI) framework in RFC 6707 defines a set of protocols to interconnect CDNs to achieve multiple goals, including extending the reach of a given CDN. A CDNI Request Routing Footprint & Capabilities Advertisement interface (FCI) is needed to achieve the goals of a CDNI. RFC 8008 defines the FCI semantics and provides guidelines on the FCI protocol, but the exact protocol is not specified. This document defines a new Application-Layer Traffic Optimization (ALTO) service, called "CDNI Advertisement Service", that provides an implementation of the FCI, following the guidelines defined in RFC 8008. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-cdni-request-routing-alto/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-cdni-request-routing-alto-21.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cdni-request-routing-alto-21 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-path-vector-21.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : An ALTO Extension: Path Vector Authors : Kai Gao Young Lee Sabine Randriamasy Yang Richard Yang Jingxuan Jensen Zhang Filename: draft-ietf-alto-path-vector-21.txt Pages : 65 Date: 2022-02-02 Abstract: This document is an extension to the base Application-Layer Traffic Optimization (ALTO) protocol. It extends the ALTO Cost Map and ALTO Property Map services so that an application can decide which endpoint(s) to connect based on not only numerical/ordinal cost values but also details of the paths. This is useful for applications whose performance is impacted by specified components of a network on the end-to-end paths, e.g., they may infer that several paths share common links and prevent traffic bottlenecks by avoiding such paths. This extension introduces a new abstraction called Abstract Network Element (ANE) to represent these components and encodes a network path as a vector of ANEs. Thus, it provides a more complete but still abstract graph representation of the underlying network(s) for informed traffic optimization among endpoints. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-path-vector/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-path-vector-21.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-path-vector-21 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-unified-props-new-22.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : An ALTO Extension: Entity Property Maps Authors : Wendy Roome Sabine Randriamasy Y. Richard Yang Jingxuan Jensen Zhang Kai Gao Filename: draft-ietf-alto-unified-props-new-22.txt Pages : 62 Date: 2022-01-25 Abstract: This document specifies an extension to the base Application-Layer Traffic Optimization (ALTO) protocol that generalizes the concept of "endpoint properties", which were so far tied to IP addresses, to entities defined by a wide set of objects. Further, these properties are presented as maps, similar to the network and cost maps in the base ALTO protocol. While supporting the endpoints and related endpoint property service defined in RFC7285, the ALTO 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. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-unified-props-new/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-unified-props-new-22 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-unified-props-new-22 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-cdni-request-routing-alto-20.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : Content Delivery Network Interconnection (CDNI) Request Routing: CDNI Footprint and Capabilities Advertisement using ALTO Authors : Jan Seedorf Y. Richard Yang Kevin J. Ma Jon Peterson Jingxuan Jensen Zhang Filename: draft-ietf-alto-cdni-request-routing-alto-20.txt Pages : 44 Date: 2022-01-25 Abstract: The Content Delivery Networks Interconnection (CDNI) framework in RFC 6707 defines a set of protocols to interconnect CDNs to achieve multiple goals, including extending the reach of a given CDN. A CDNI Request Routing Footprint & Capabilities Advertisement interface (FCI) is needed to achieve the goals of a CDNI. RFC 8008 defines the FCI semantics and provides guidelines on the FCI protocol, but the exact protocol is not specified. This document defines a new Application-Layer Traffic Optimization (ALTO) service, called "CDNI Advertisement Service", that provides an implementation of the FCI, following the guidelines defined in RFC 8008. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-cdni-request-routing-alto/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-cdni-request-routing-alto-20.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cdni-request-routing-alto-20 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-cdni-request-routing-alto-19.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : Content Delivery Network Interconnection (CDNI) Request Routing: CDNI Footprint and Capabilities Advertisement using ALTO Authors : Jan Seedorf Y. Richard Yang Kevin J. Ma Jon Peterson Jingxuan Jensen Zhang Filename: draft-ietf-alto-cdni-request-routing-alto-19.txt Pages : 44 Date: 2022-01-08 Abstract: The Content Delivery Networks Interconnection (CDNI) framework in RFC 6707 defines a set of protocols to interconnect CDNs to achieve multiple goals, including extending the reach of a given CDN. A CDNI Request Routing Footprint & Capabilities Advertisement interface (FCI) is needed to achieve the goals of a CDNI. RFC 8008 defines the FCI semantics and provides guidelines on the FCI protocol, but the exact protocol is not specified. This document defines a new Application-Layer Traffic Optimization (ALTO) service, called "CDNI Advertisement Service", that provides an implementation of the FCI, following the guidelines defined in RFC 8008. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-cdni-request-routing-alto/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-cdni-request-routing-alto-19.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cdni-request-routing-alto-19 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-path-vector-20.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : An ALTO Extension: Path Vector Authors : Kai Gao Young Lee Sabine Randriamasy Yang Richard Yang Jingxuan Jensen Zhang Filename: draft-ietf-alto-path-vector-20.txt Pages : 65 Date: 2021-12-20 Abstract: This document is an extension to the base Application-Layer Traffic Optimization (ALTO) protocol. It extends the ALTO Cost Map and ALTO Property Map services so that an application can decide which endpoint(s) to connect based on not only numerical/ordinal cost values but also details of the paths. This is useful for applications whose performance is impacted by specified components of a network on the end-to-end paths, e.g., they may infer that several paths share common links and prevent traffic bottlenecks by avoiding such paths. This extension introduces a new abstraction called Abstract Network Element (ANE) to represent these components and encodes a network path as a vector of ANEs. Thus, it provides a more complete but still abstract graph representation of the underlying network(s) for informed traffic optimization among endpoints. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-path-vector/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-path-vector-20.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-path-vector-20 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-performance-metrics-21.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Performance Cost Metrics Authors : Qin Wu Y. Richard Yang Young Lee Dhruv Dhody Sabine Randriamasy Luis Miguel Contreras Murillo Filename: draft-ietf-alto-performance-metrics-21.txt Pages : 39 Date: 2021-12-19 Abstract: The cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and different applications may use different types of cost metrics. Since the ALTO base protocol (RFC 7285) defines only a single cost metric (namely, the generic "routingcost" metric), if an application wants to issue a cost map or an endpoint cost request in order to identify a resource provider that offers a better delay performance, the base protocol does not define the cost metric to be used. This document addresses this issue by extending the specification to provide a variety of network performance metrics, including network delay, delay variation (a.k.a, jitter), packet loss rate, hop count, and bandwidth. There are multiple sources (e.g., estimation based on measurements or service-level agreement) to derive a performance metric. This document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey the source of a performance metric. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-21 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-21 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-cdni-request-routing-alto-18.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : Content Delivery Network Interconnection (CDNI) Request Routing: CDNI Footprint and Capabilities Advertisement using ALTO Authors : Jan Seedorf Y. Richard Yang Kevin J. Ma Jon Peterson Jingxuan Jensen Zhang Filename: draft-ietf-alto-cdni-request-routing-alto-18.txt Pages : 43 Date: 2021-12-13 Abstract: The Content Delivery Networks Interconnection (CDNI) framework in RFC 6707 defines a set of protocols to interconnect CDNs to achieve multiple goals, including extending the reach of a given CDN. A CDNI Request Routing Footprint & Capabilities Advertisement interface (FCI) is needed to achieve the goals of a CDNI. RFC 8008 defines precisely the semantics of FCI and provides guidelines on the FCI protocol, but the exact protocol is not specified. This document defines a new Application-Layer Traffic Optimization (ALTO) service called "CDNI Advertisement Service" that provides an implementation of the FCI, following the guidelines defined in RFC 8008. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-cdni-request-routing-alto/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-cdni-request-routing-alto-18.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cdni-request-routing-alto-18 Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-performance-metrics-20.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Performance Cost Metrics Authors : Qin Wu Y. Richard Yang Young Lee Dhruv Dhody Sabine Randriamasy Luis Miguel Contreras Murillo Filename: draft-ietf-alto-performance-metrics-20.txt Pages : 35 Date: 2021-11-30 Abstract: The cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and different applications may use different types of cost metrics. Since the ALTO base protocol (RFC 7285) defines only a single cost metric (namely, the generic "routingcost" metric), if an application wants to issue a cost map or an endpoint cost request in order to identify a resource provider that offers a better delay performance, the base protocol does not define the cost metric to be used. This document addresses this issue by extending the specification to provide a variety of network performance metrics, including network delay, delay variation (jitter), packet loss rate, hop count, and bandwidth. There are multiple sources (e.g., estimation based on measurements or service-level agreement) to derive a performance metric. This document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey the source of a performance metric. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-20 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-20 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-unified-props-new-21.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Extension: Entity Property Maps Authors : Wendy Roome Sabine Randriamasy Y. Richard Yang Jingxuan Jensen Zhang Kai Gao Filename: draft-ietf-alto-unified-props-new-21.txt Pages : 61 Date: 2021-11-26 Abstract: This document specifies an extension to the base Application-Layer Traffic Optimization (ALTO) Protocol that generalizes the concept of "endpoint properties", which were so far tied to IP addresses, to entities defined by a wide set of objects. Further, these properties are presented as maps, similar to the network and cost maps in the base ALTO protocol. While supporting the endpoints and related endpoint property service defined in RFC7285, 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. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-unified-props-new/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-unified-props-new-21 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-unified-props-new-21 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-unified-props-new-20.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Extension: Entity Property Maps Authors : Wendy Roome Sabine Randriamasy Y. Richard Yang Jingxuan Jensen Zhang Kai Gao Filename: draft-ietf-alto-unified-props-new-20.txt Pages : 61 Date: 2021-10-25 Abstract: This document specifies an extension to the base Application-Layer Traffic Optimization (ALTO) Protocol that generalizes the concept of "endpoint properties", which were so far tied to IP addresses, to entities defined by a wide set of objects. Further, these properties are presented as maps, similar to the network and cost maps in the base ALTO protocol. While supporting the endpoints and related endpoint property service defined in RFC7285, 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. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-unified-props-new/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-unified-props-new-20 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-unified-props-new-20 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-path-vector-19.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Extension: Path Vector Authors : Kai Gao Young Lee Sabine Randriamasy Yang Richard Yang Jingxuan Jensen Zhang Filename: draft-ietf-alto-path-vector-19.txt Pages : 63 Date: 2021-10-25 Abstract: This document is an extension to the base Application-Layer Traffic Optimization (ALTO) protocol. It extends the ALTO Cost Map service and ALTO Property Map service so that the application can decide which endpoint(s) to connect based on not only numerical/ordinal cost values but also details of the paths. This is useful for applications whose performance is impacted by specified components of a network on the end-to-end paths, e.g., they may infer that several paths share common links and prevent traffic bottlenecks by avoiding such paths. This extension introduces a new abstraction called Abstract Network Element (ANE) to represent these components and encodes a network path as a vector of ANEs. Thus, it provides a more complete but still abstract graph representation of the underlying network(s) for informed traffic optimization among endpoints. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-path-vector/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-path-vector-19.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-path-vector-19 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-cdni-request-routing-alto-17.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : Content Delivery Network Interconnection (CDNI) Request Routing: CDNI Footprint and Capabilities Advertisement using ALTO Authors : Jan Seedorf Y. Richard Yang Kevin J. Ma Jon Peterson Jingxuan Jensen Zhang Filename: draft-ietf-alto-cdni-request-routing-alto-17.txt Pages : 41 Date: 2021-10-25 Abstract: The Content Delivery Networks Interconnection (CDNI) framework in RFC 6707 defines a set of protocols to interconnect CDNs to achieve multiple goals, including extending the reach of a given CDN. A CDNI Request Routing Footprint & Capabilities Advertisement interface (FCI) is needed to achieve the goals of a CDNI. RFC 8008 defines precisely the semantics of FCI and provides guidelines on the FCI protocol, but the exact protocol is specified. This document defines a new Application-Layer Traffic Optimization (ALTO) service called "CDNI Advertisement Service" that provides an implementation of the FCI, following the guidelines defined in RFC 8008. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-cdni-request-routing-alto/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-cdni-request-routing-alto-17.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cdni-request-routing-alto-17 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-unified-props-new-19.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Extension: Entity Property Maps Authors : Wendy Roome Sabine Randriamasy Y. Richard Yang Jingxuan Jensen Zhang Kai Gao Filename: draft-ietf-alto-unified-props-new-19.txt Pages : 61 Date: 2021-10-25 Abstract: This document specifies an extension to the base Application-Layer Traffic Optimization (ALTO) Protocol that generalizes the concept of "endpoint properties", which were so far tied to IP addresses, to entities defined by a wide set of objects. Further, these properties are presented as maps, similar to the network and cost maps in the base ALTO protocol. While supporting the endpoints and related endpoint property service defined in RFC7285, 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. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-unified-props-new/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-unified-props-new-19 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-unified-props-new-19 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-performance-metrics-19.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Performance Cost Metrics Authors : Qin Wu Y. Richard Yang Young Lee Dhruv Dhody Sabine Randriamasy Luis Miguel Contreras Murillo Filename: draft-ietf-alto-performance-metrics-19.txt Pages : 34 Date: 2021-10-23 Abstract: The cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and different applications may use different types of cost metric. Since the ALTO base protocol (RFC 7285) defines only a single cost metric (namely, the generic "routingcost" metric), if an application wants to issue a cost map or an endpoint cost request in order to identify a resource provider that offers a better delay performance, the base protocol does not define the cost metric to be used. This document addresses this issue by extending the specification to provide a variety of network performance metrics, including network delay, delay variation (jitter), packet loss rate, hop count, and bandwidth. There are multiple sources (e.g., estimation based on measurements or service-level agreement) to derive a performance metric. This document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey the source of a performance metric. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-19 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-19 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-performance-metrics-18.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Performance Cost Metrics Authors : Qin Wu Y. Richard Yang Young Lee Dhruv Dhody Sabine Randriamasy Luis Miguel Contreras Filename: draft-ietf-alto-performance-metrics-18.txt Pages : 34 Date: 2021-10-18 Abstract: Cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and different applications may use different cost metrics. Since the ALTO base protocol (RFC 7285) defines only a single cost metric (i.e., the generic "routingcost" metric), if an application wants to issue a cost map or an endpoint cost request to determine the resource provider that offers better delay performance, the base protocol does not define the cost metric to be used. This document addresses the issue by introducing network performance metrics, including network delay, jitter, packet loss rate, hop count, and bandwidth. There are multiple sources (e.g., estimation based on measurements or service-level agreement) to derive a performance metric. This document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey the source of a performance metric. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-18 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-18 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-path-vector-18.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Extension: Path Vector Authors : Kai Gao Young Lee Sabine Randriamasy Yang Richard Yang Jingxuan Jensen Zhang Filename: draft-ietf-alto-path-vector-18.txt Pages : 63 Date: 2021-10-18 Abstract: This document is an extension to the base Application-Layer Traffic Optimization (ALTO) protocol. It extends the ALTO Cost Map service and ALTO Property Map service so that the application can decide which endpoint(s) to connect based on not only numerical/ordinal cost values but also details of the paths. This is useful for applications whose performance is impacted by specified components of a network on the end-to-end paths, e.g., they may infer that several paths share common links and prevent traffic bottlenecks by avoiding such paths. This extension introduces a new abstraction called Abstract Network Element (ANE) to represent these components and encodes a network path as a vector of ANEs. Thus, it provides a more complete but still abstract graph representation of the underlying network(s) for informed traffic optimization among endpoints. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-path-vector/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-path-vector-18.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-path-vector-18 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-path-vector-15.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Extension: Path Vector Authors : Kai Gao Young Lee Sabine Randriamasy Yang Richard Yang Jingxuan Jensen Zhang Filename: draft-ietf-alto-path-vector-15.txt Pages : 52 Date: 2021-08-09 Abstract: This document is an extension to the base Application-Layer Traffic Optimization (ALTO) protocol. It extends the ALTO Cost Map service and ALTO Property Map service so that the application can decide which endpoint(s) to connect based on not only numerical/ordinal cost values but also details of the paths. This is useful for applications whose performance is impacted by specified components of a network on the end-to-end paths, e.g., they may infer that several paths share common links and prevent traffic bottlenecks by avoiding such paths. This extension introduces a new abstraction called Abstract Network Element (ANE) to represent these components and encodes a network path as a vector of ANEs. Thus, it provides a more complete but still abstract graph representation of the underlying network(s) for informed traffic optimization among endpoints. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-path-vector/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-path-vector-15.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-path-vector-15 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-performance-metrics-17.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Performance Cost Metrics Authors : Qin Wu Y. Richard Yang Young Lee Dhruv Dhody Sabine Randriamasy Luis Miguel Contreras Murillo Filename: draft-ietf-alto-performance-metrics-17.txt Pages : 33 Date: 2021-07-27 Abstract: Cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and different applications may use different cost metrics. Since the ALTO base protocol (RFC 7285) defines only a single cost metric (i.e., the generic "routingcost" metric), if an application wants to issue a cost map or an endpoint cost request to determine the resource provider that offers better delay performance, the base protocol does not define the cost metric to be used. This document addresses the issue by introducing network performance metrics, including network delay, jitter, packet loss rate, hop count, and bandwidth. There are multiple sources (e.g., estimation based on measurements or service-level agreement) to derive a performance metric. This document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey the source of a performance metric. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-17 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-17 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-performance-metrics-16.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Performance Cost Metrics Authors : Qin Wu Y. Richard Yang Young Lee Dhruv Dhody Sabine Randriamasy Luis Miguel Contreras Filename: draft-ietf-alto-performance-metrics-16.txt Pages : 33 Date: 2021-07-11 Abstract: Cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and different applications may use different cost metrics. Since the ALTO base protocol (RFC 7285) defines only a single cost metric (i.e., the generic "routingcost" metric), if an application wants to issue a cost map or an endpoint cost request to determine the resource provider that offers better delay performance, the base protocol does not define the cost metric to be used. This document addresses the issue by introducing network performance metrics, including network delay, jitter, packet loss rate, hop count, and bandwidth. There are multiple sources (e.g., estimation based on measurements or service-level agreement) to derive a performance metric. This document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey the source of a performance metric. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-16 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-16 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-unified-props-new-17.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Extension: Entity Property Maps Authors : Wendy Roome Sabine Randriamasy Y. Richard Yang Jingxuan Jensen Zhang Kai Gao Filename: draft-ietf-alto-unified-props-new-17.txt Pages : 59 Date: 2021-04-16 Abstract: This document extends the base Application-Layer Traffic Optimization (ALTO) Protocol by generalizing the concept of "endpoint properties" as applied to endpoints as defined by IP addresses to endpoints defined by a wider set of objects. 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. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-unified-props-new/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-alto-unified-props-new-17 https://datatracker.ietf.org/doc/html/draft-ietf-alto-unified-props-new-17 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-unified-props-new-17 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-unified-props-new-16.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO extension: Entity Property Maps Authors : Wendy Roome Sabine Randriamasy Y. Richard Yang Jingxuan Jensen Zhang Kai Gao Filename: draft-ietf-alto-unified-props-new-16.txt Pages : 57 Date: 2021-02-22 Abstract: This document extends the base Application-Layer Traffic Optimization (ALTO) Protocol by generalizing the concept of "endpoint properties" as applied to endpoints as defined by IP addresses to endpoints defined by a wider set of objects. 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. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-unified-props-new/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-alto-unified-props-new-16 https://datatracker.ietf.org/doc/html/draft-ietf-alto-unified-props-new-16 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-unified-props-new-16 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-path-vector-14.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Extension: Path Vector Authors : Kai Gao Young Lee Sabine Randriamasy Yang Richard Yang Jingxuan Jensen Zhang Filename: draft-ietf-alto-path-vector-14.txt Pages : 51 Date: 2021-02-22 Abstract: This document is an extension to the base Application-Layer Traffic Optimization (ALTO) protocol. It extends the ALTO Cost Map service and ALTO Property Map service so that the application can decide which endpoint(s) to connect based on not only numerical/ordinal cost values but also details of the paths. This is useful for applications whose performance is impacted by specified components of a network on the end-to-end paths, e.g., they may infer that several paths share common links and prevent traffic bottlenecks by avoiding such paths. This extension introduces a new abstraction called Abstract Network Element (ANE) to represent these components and encodes a network path as a vector of ANEs. Thus, it provides a more complete but still abstract graph representation of the underlying network(s) for informed traffic optimization among endpoints. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-path-vector/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-path-vector-14.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-path-vector-14 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-performance-metrics-15.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Performance Cost Metrics Authors : Qin Wu Y. Richard Yang Young Lee Dhruv Dhody Sabine Randriamasy Luis Miguel Contreras Filename: draft-ietf-alto-performance-metrics-15.txt Pages : 33 Date: 2021-02-04 Abstract: Cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and different applications may use different cost metrics. Since the ALTO base protocol (RFC 7285) defines only a single cost metric (i.e., the generic "routingcost" metric), if an application wants to issue a cost map or an endpoint cost request to determine the resource provider that offers better delay performance, the base protocol does not define the cost metric to be used. This document addresses the issue by introducing network performance metrics, including network delay, jitter, packet loss rate, hop count, and bandwidth. There are multiple sources (e.g., estimation based on measurements or service-level agreement) to derive a performance metric. This document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey the source of a performance metric. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-alto-performance-metrics-15 https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-15 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-15 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-performance-metrics-14.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Performance Cost Metrics Authors : Qin Wu Y. Richard Yang Young Lee Dhruv Dhody Sabine Randriamasy Luis Miguel Contreras Filename: draft-ietf-alto-performance-metrics-14.txt Pages : 33 Date: 2021-01-13 Abstract: Cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and different applications may use different cost metrics. Since the ALTO base protocol (RFC 7285) defines only a single cost metric (i.e., the generic "routingcost" metric), if an application wants to issue a cost map or an endpoint cost request to determine the resource provider that offers better delay performance, the base protocol does not define the cost metric to be used. This document addresses the issue by introducing network performance metrics, including network delay, jitter, packet loss rate, hop count, and bandwidth. There are multiple sources (e.g., estimation based on measurements or service-level agreement) to derive a performance metric. This document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey the source of a performance metric. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-alto-performance-metrics-14 https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-14 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-14 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-cdni-request-routing-alto-16.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : Content Delivery Network Interconnection (CDNI) Request Routing: CDNI Footprint and Capabilities Advertisement using ALTO Authors : Jan Seedorf Y.R. Yang Kevin J. Ma Jon Peterson Jingxuan Jensen Zhang Filename: draft-ietf-alto-cdni-request-routing-alto-16.txt Pages : 41 Date: 2021-01-12 Abstract: The Content Delivery Networks Interconnection (CDNI) framework defines a set of protocols to interconnect CDNs, to achieve multiple goals such as extending the reach of a given CDN to areas that are not covered by that particular CDN. One component that is needed to achieve the goal of CDNI described in CDNI framework is the CDNI Request Routing Footprint & Capabilities Advertisement interface (FCI). RFC 8008 defines precisely the semantics of FCI and provides guidelines on the FCI protocol, but the exact protocol is explicitly outside the scope of that document. This document defines an FCI protocol using the Application-Layer Traffic Optimization (ALTO) protocol, following the guidelines defined in RFC 8008. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-cdni-request-routing-alto/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-alto-cdni-request-routing-alto-16 https://datatracker.ietf.org/doc/html/draft-ietf-alto-cdni-request-routing-alto-16 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cdni-request-routing-alto-16 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-cdni-request-routing-alto-15.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : Content Delivery Network Interconnection (CDNI) Request Routing: CDNI Footprint and Capabilities Advertisement using ALTO Authors : Jan Seedorf Y.R. Yang Kevin J. Ma Jon Peterson Jingxuan Jensen Zhang Filename: draft-ietf-alto-cdni-request-routing-alto-15.txt Pages : 41 Date: 2021-01-11 Abstract: The Content Delivery Networks Interconnection (CDNI) framework [RFC6707] defines a set of protocols to interconnect CDNs, to achieve multiple goals such as extending the reach of a given CDN to areas that are not covered by that particular CDN. One component that is needed to achieve the goal of CDNI described in [RFC7336] is the CDNI Request Routing Footprint & Capabilities Advertisement interface (FCI). [RFC8008] defines precisely the semantics of FCI and provides guidelines on the FCI protocol, but the exact protocol is explicitly outside the scope of that document. This document defines an FCI protocol using the Application-Layer Traffic Optimization (ALTO) protocol, following the guidelines defined in [RFC8008]. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-cdni-request-routing-alto/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-alto-cdni-request-routing-alto-15 https://datatracker.ietf.org/doc/html/draft-ietf-alto-cdni-request-routing-alto-15 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cdni-request-routing-alto-15 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-performance-metrics-13.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Performance Cost Metrics Authors : Qin Wu Y. Richard Yang Young Lee Dhruv Dhody Sabine Randriamasy Luis Miguel Contreras Filename: draft-ietf-alto-performance-metrics-13.txt Pages : 32 Date: 2021-01-11 Abstract: Cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and different applications may use different cost metrics. Since the ALTO base protocol [RFC7285] defines only a single cost metric (i.e., the generic "routingcost" metric), if an application wants to issue a cost map or an endpoint cost request to determine the resource provider that offers better delay performance, the base protocol does not define the cost metric to be used. This document addresses the issue by introducing network performance metrics, including network delay, jitter, packet loss rate, hop count, and bandwidth. There are multiple sources (e.g., estimation based on measurements or service-level agreement) to derive a performance metric. This document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey the source of a performance metric. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-alto-performance-metrics-13 https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-13 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-13 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-unified-props-new-15.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO extension: Entity Property Maps Authors : Wendy Roome Sabine Randriamasy Y. Richard Yang Jingxuan Jensen Zhang Kai Gao Filename: draft-ietf-alto-unified-props-new-15.txt Pages : 57 Date: 2020-11-26 Abstract: This document extends the base Application-Layer Traffic Optimization (ALTO) Protocol by generalizing the concept of "endpoint properties" to generic types of entities, and by presenting those properties 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. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-unified-props-new/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-alto-unified-props-new-15 https://datatracker.ietf.org/doc/html/draft-ietf-alto-unified-props-new-15 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-unified-props-new-15 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-path-vector-13.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Extension: Path Vector Authors : Kai Gao Young Lee Sabine Randriamasy Yang Richard Yang Jingxuan Jensen Zhang Filename: draft-ietf-alto-path-vector-13.txt Pages : 47 Date: 2020-11-20 Abstract: This document is an extension to the base Application-Layer Traffic Optimization (ALTO) protocol. It extends the ALTO Cost Map service and ALTO Property Map service so that the application can decide which endpoint(s) to connect based on not only numerical/ordinal cost values but also details of the paths. This is useful for applications whose performance is impacted by specified components of a network on the end-to-end paths, e.g., they may infer that several paths share common links and prevent traffic bottlenecks by avoiding such paths. This extension introduces a new abstraction called Abstract Network Element (ANE) to represent these components and encodes a network path as a vector of ANEs. Thus, it provides a more complete but still abstract graph representation of the underlying network(s) for informed traffic optimization among endpoints. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-path-vector/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-path-vector-13.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-path-vector-13 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-cdni-request-routing-alto-14.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : Content Delivery Network Interconnection (CDNI) Request Routing: CDNI Footprint and Capabilities Advertisement using ALTO Authors : Jan Seedorf Y.R. Yang Kevin J. Ma Jon Peterson Jingxuan Jensen Zhang Filename: draft-ietf-alto-cdni-request-routing-alto-14.txt Pages : 42 Date: 2020-11-17 Abstract: The Content Delivery Networks Interconnection (CDNI) framework [RFC6707] defines a set of protocols to interconnect CDNs, to achieve multiple goals such as extending the reach of a given CDN to areas that are not covered by that particular CDN. One component that is needed to achieve the goal of CDNI described in [RFC7336] is the CDNI Request Routing Footprint & Capabilities Advertisement interface (FCI). [RFC8008] defines precisely the semantics of FCI and provides guidelines on the FCI protocol, but the exact protocol is explicitly outside the scope of that document. This document defines an FCI protocol using the Application-Layer Traffic Optimization (ALTO) protocol, following the guidelines defined in [RFC8008]. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-cdni-request-routing-alto/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-alto-cdni-request-routing-alto-14 https://datatracker.ietf.org/doc/html/draft-ietf-alto-cdni-request-routing-alto-14 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cdni-request-routing-alto-14 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-cdni-request-routing-alto-13.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : Content Delivery Network Interconnection (CDNI) Request Routing: CDNI Footprint and Capabilities Advertisement using ALTO Authors : Jan Seedorf Y.R. Yang Kevin J. Ma Jon Peterson Jingxuan Jensen Zhang Filename: draft-ietf-alto-cdni-request-routing-alto-13.txt Pages : 41 Date: 2020-11-02 Abstract: The Content Delivery Networks Interconnection (CDNI) framework [RFC6707] defines a set of protocols to interconnect CDNs, to achieve multiple goals such as extending the reach of a given CDN to areas that are not covered by that particular CDN. One component that is needed to achieve the goal of CDNI described in [RFC7336] is the CDNI Request Routing Footprint & Capabilities Advertisement interface (FCI). [RFC8008] defines precisely the semantics of FCI and provides guidelines on the FCI protocol, but the exact protocol is explicitly outside the scope of that document. This document defines an FCI protocol using the Application-Layer Traffic Optimization (ALTO) protocol, following the guidelines defined in [RFC8008]. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-cdni-request-routing-alto/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-alto-cdni-request-routing-alto-13 https://datatracker.ietf.org/doc/html/draft-ietf-alto-cdni-request-routing-alto-13 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cdni-request-routing-alto-13 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-path-vector-12.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Extension: Path Vector Authors : Kai Gao Young Lee Sabine Randriamasy Yang Richard Yang Jingxuan Jensen Zhang Filename: draft-ietf-alto-path-vector-12.txt Pages : 46 Date: 2020-11-02 Abstract: This document is an extension to the base Application-Layer Traffic Optimization protocol [RFC7285]. While the current ALTO Cost Services only allow applications to obtain numerical/ordinal cost values on an end-to-end path defined by its source and destination, the present extension enables the provision of abstracted information on particular Abstract Network Elements on the path. These Abstract Network Elements, or simply Elements, are components of the network which handle data packets, and their properties may have an impact on the end-to-end performance of the applications' traffic. Examples of such Elements include physical devices such as routers, cables and interfaces, and aggregations of devices such as subnetworks and data centers. Such information is useful for applications whose performance is impacted by particular Abstract Network Elements they traverse or by their properties. Applications having the choice among several connection paths may use this information to select paths accordingly and improve their performance. In particular, they may infer that several paths share common links and prevent traffic bottlenecks by avoiding such paths. This document introduces a new cost type called Path Vector. A Path Vector is an array of entities that each identifies an Abstract Network Element (ANE). Each ANE is associated with a set of properties. ANE properties are conveyed by an ALTO information resource called "Property Map", that can be packed together with the Path Vectors in a multipart response. They can also be obtained via a separate ALTO request to a Property Map. An ALTO Property Map is an extension to the ALTO protocol, that is specified in another document entitled "Unified Properties for the ALTO Protocol" [I-D.ietf-alto-unified-props-new]. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-path-vector/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-alto-path-vector-12.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-path-vector-12 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-path-vector-11.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Extension: Path Vector Authors : Kai Gao Young Lee Nokia Bell Labs Yang Richard Yang Jingxuan Jensen Zhang Filename: draft-ietf-alto-path-vector-11.txt Pages : 44 Date: 2020-07-13 Abstract: This document is an extension to the base Application-Layer Traffic Optimization protocol [RFC7285]. The current ALTO Cost Services only allow applications to obtain cost values on an end-to-end path defined by its source and destination. The present extension provides abstracted information on particular network components or elements traversed by a path between its source and destination. Examples of such abstracted components are networks, data centers or links. This is useful for applications whose performance is impacted by particular network components they traverse or by their properties. Applications having the choice among several connection paths may use this information to select paths accordingly and improve their performance. In particular, they may infer that several paths share common links and prevent traffic bottlenecks by avoiding such paths. This document introduces a new cost type called Path Vector. A Path Vector is an array of entities that each identifies an abstracted representation of a network part and that are called Abstract Network Element (ANE). Each ANE is defined by a set of properties. ANE properties are conveyed by an ALTO information resource called "Property Map", that can be packed together with the Path Vectors in a multipart response. They can also be obtained via a separate ALTO request to a Property Map. An ALTO Property Map is an extension to the ALTO protocol, that is specified in another document entitled "Unified Properties for the ALTO Protocol" [I-D.ietf-alto-unified-props-new]. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-path-vector/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-alto-path-vector-11 https://datatracker.ietf.org/doc/html/draft-ietf-alto-path-vector-11 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-path-vector-11 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-cdni-request-routing-alto-12.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : Content Delivery Network Interconnection (CDNI) Request Routing: CDNI Footprint and Capabilities Advertisement using ALTO Authors : Jan Seedorf Y.R. Yang Kevin J. Ma Jon Peterson Jingxuan Jensen Zhang Filename: draft-ietf-alto-cdni-request-routing-alto-12.txt Pages : 41 Date: 2020-07-13 Abstract: The Content Delivery Networks Interconnection (CDNI) framework [RFC6707] defines a set of protocols to interconnect CDNs, to achieve multiple goals such as extending the reach of a given CDN to areas that are not covered by that particular CDN. One component that is needed to achieve the goal of CDNI described in [RFC7336] is the CDNI Request Routing Footprint & Capabilities Advertisement interface (FCI). [RFC8008] defines precisely the semantics of FCI and provides guidelines on the FCI protocol, but the exact protocol is explicitly outside the scope of that document. This document defines an FCI protocol using the Application-Layer Traffic Optimization (ALTO) protocol, following the guidelines defined in [RFC8008]. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-cdni-request-routing-alto/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-alto-cdni-request-routing-alto-12 https://datatracker.ietf.org/doc/html/draft-ietf-alto-cdni-request-routing-alto-12 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-cdni-request-routing-alto-12 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-unified-props-new-12.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : Unified properties for the ALTO protocol Authors : Wendy Roome Sabine Randriamasy Y. Richard Yang Jingxuan Jensen Zhang Kai Gao Filename: draft-ietf-alto-unified-props-new-12.txt Pages : 55 Date: 2020-07-13 Abstract: This document extends the Application-Layer Traffic Optimization (ALTO) Protocol [RFC7285] by generalizing the concept of "endpoint properties" to generic types of entities, and by presenting those properties as maps, similar to the network and cost maps in [RFC7285]. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-unified-props-new/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-alto-unified-props-new-12 https://datatracker.ietf.org/doc/html/draft-ietf-alto-unified-props-new-12 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-unified-props-new-12 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-performance-metrics-12.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Performance Cost Metrics Authors : Qin Wu Y. Richard Yang Young Lee Dhruv Dhody Sabine Randriamasy Luis Miguel Contreras Filename: draft-ietf-alto-performance-metrics-12.txt Pages : 32 Date: 2020-07-13 Abstract: Cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and is used in basic ALTO services including both the cost map service and the endpoint cost service. Different applications may use different cost metrics, but the ALTO base protocol [RFC7285] defines only a single cost metric, i.e., the generic "routingcost" metric; see Sec. 14.2 of [RFC7285]. Hence, if the ALTO client of an application wants to issue a cost map or an endpoint cost request to determine the resource provider that offers better delay performance (i.e., low-delay) to a resource consumer, the base protocol does not define the cost metric to be used. This document addresses the issue by introducing network performance metrics, including network delay, jitter, packet loss rate, hop count, and bandwidth. The ALTO server may derive and aggregate such performance metrics from routing protocols such as BGP-LS, OSPF-TE and ISIS-TE, or from end-to-end traffic management tools, and then expose the information to allow applications to determine "where" to connect based on network performance criteria. There are multiple sources to derive the performance metrics. For example, whether the metric reported is an estimation based on measurements or it is a service-level agreement (SLA) can define the meaning of the performance metric. Hence, an application may need additional contextual information beyond the metric value. This document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey such information. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-alto-performance-metrics-12 https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-12 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-12 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-performance-metrics-11.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Performance Cost Metrics Authors : Qin Wu Y. Richard Yang Young Lee Dhruv Dhody Sabine Randriamasy Luis Miguel Contreras Filename: draft-ietf-alto-performance-metrics-11.txt Pages : 31 Date: 2020-06-12 Abstract: Cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and is used in basic ALTO services including both the cost map service and the endpoint cost service. Different applications may use different cost metrics, but the ALTO base protocol [RFC7285] defines only a single cost metric, i.e., the generic "routingcost" metric; see Sec. 14.2 of [RFC7285]. Hence, if the ALTO client of an application wants to issue a cost map or an endpoint cost request to determine the resource provider that offers better delay performance (i.e., low-delay) to a resource consumer, the base protocol does not define the cost metric to be used. This document addresses the issue by introducing network performance metrics, including network delay, jitter, packet loss rate, hop count, and bandwidth. The ALTO server may derive and aggregate such performance metrics from routing protocols such as BGP-LS, OSPF-TE and ISIS-TE, or from end-to-end traffic management tools, and then expose the information to allow applications to determine "where" to connect based on network performance criteria. There are multiple sources to derive the performance metrics. For example, whether the metric reported is an estimation based on measurements or it is a service-level agreement (SLA) can define the meaning of the performance metric. Hence, an application may need additional contextual information beyond the metric value. This document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey such information. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-alto-performance-metrics-11 https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-11 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-11 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
[alto] I-D Action: draft-ietf-alto-performance-metrics-10.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF. Title : ALTO Performance Cost Metrics Authors : Qin Wu Y. Richard Yang Dhruv Dhody Sabine Randriamasy Luis Miguel Contreras Filename: draft-ietf-alto-performance-metrics-10.txt Pages : 30 Date: 2020-05-16 Abstract: Cost metric is a basic concept in Application-Layer Traffic Optimization (ALTO), and is used in basic ALTO services including both the cost map service and the endpoint cost service. Different applications may use different cost metrics, but the ALTO base protocol [RFC7285] documents only one single cost metric, i.e., the generic "routingcost" metric; see Sec. 14.2 of [RFC7285]. Hence, if the ALTO client of an application wants to issue a cost map or an endpoint cost request to determine the resource provider offering better delay performance (i.e., low-delay) to the resource consumer, the base protocol does not define the cost metric to be used. ALTO cost metrics can be generic metrics and this document focuses on network performance metrics, including network delay, jitter, packet loss rate, hop count, and bandwidth. When using an ALTO performance metric, an application may need additional contextual information beyond the metric value. For example, whether the metric is an estimation based on measurements or a service-level agreement (SLA) can define the meaning of the performance metric. Hence, this document introduces an additional "cost-context" field to the ALTO "cost-type" field to convey such information. To report an estimated value of a performance metric, the ALTO server may derive and aggregate from routing protocols with different granularity and scope, such as BGP-LS, OSPF-TE and ISIS-TE, or from end-to-end traffic management tools. These metrics may then be exposed by an ALTO server to allow applications to determine "where" to connect based on network performance criteria. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-alto-performance-metrics-10 https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-10 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-10 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
