Path Aware Networking: Obstacles to Deployment (A Bestiary of Roads Not Taken)
draft-irtf-panrg-what-not-to-do-13
PANRG S. Dawkins, Ed.
Internet-Draft Tencent America
Intended status: Informational 1 September 2020
Expires: 5 March 2021
Path Aware Networking: Obstacles to Deployment (A Bestiary of Roads Not
Taken)
draft-irtf-panrg-what-not-to-do-13
Abstract
At the first meeting of the Path Aware Networking Research Group, the
research group agreed to catalog and analyze past efforts to develop
and deploy Path Aware techniques, most of which were unsuccessful or
at most partially successful, in order to extract insights and
lessons for path-aware networking researchers.
This document contains that catalog and analysis.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 5 March 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Dawkins Expires 5 March 2021 [Page 1]
Internet-Draft What Not To Do September 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Purpose of This Document . . . . . . . . . . . . . . . . 4
1.2. What Does "Path Awareness" Mean in this Document? . . . . 4
1.3. Note to RFC Editor . . . . . . . . . . . . . . . . . . . 4
1.4. A Note About Path-Aware Techniques Included In This
Document . . . . . . . . . . . . . . . . . . . . . . . . 5
1.5. Venue for Discussion of this Document . . . . . . . . . . 5
1.6. Architectural Guidance . . . . . . . . . . . . . . . . . 5
1.7. Terminology Used in this Document . . . . . . . . . . . . 6
2. Summary of Lessons Learned . . . . . . . . . . . . . . . . . 6
2.1. Justifying Deployment . . . . . . . . . . . . . . . . . . 6
2.2. Providing Benefits for Early Adopters . . . . . . . . . . 6
2.3. Providing Benefits During Partial Deployment . . . . . . 7
2.4. Outperforming End-to-end Protocol Mechanisms . . . . . . 7
2.5. Paying for Path Aware Techniques . . . . . . . . . . . . 7
2.6. Impact on Operational Practices . . . . . . . . . . . . . 7
2.7. Per-connection State . . . . . . . . . . . . . . . . . . 7
2.8. Keeping Traffic on Fast-paths . . . . . . . . . . . . . . 8
2.9. Endpoints Trusting Intermediate Nodes . . . . . . . . . . 8
2.10. Intermediate Nodes Trusting Endpoints . . . . . . . . . . 8
2.11. Reacting to Distant Signals . . . . . . . . . . . . . . . 8
2.12. Support in Endpoint Protocol Stacks . . . . . . . . . . . 9
3. Do We Understand the Lessons We've Learned? . . . . . . . . . 9
4. Template for Contributions . . . . . . . . . . . . . . . . . 12
5. Contributions . . . . . . . . . . . . . . . . . . . . . . . . 12
5.1. Stream Transport (ST, ST2, ST2+) . . . . . . . . . . . . 12
5.1.1. Reasons for Non-deployment . . . . . . . . . . . . . 13
5.1.2. Lessons Learned. . . . . . . . . . . . . . . . . . . 13
5.2. Integrated Services (IntServ) . . . . . . . . . . . . . . 13
5.2.1. Reasons for Non-deployment . . . . . . . . . . . . . 14
5.2.2. Lessons Learned. . . . . . . . . . . . . . . . . . . 15
5.3. Quick-Start TCP . . . . . . . . . . . . . . . . . . . . . 15
5.3.1. Reasons for Non-deployment . . . . . . . . . . . . . 16
5.3.2. Lessons Learned . . . . . . . . . . . . . . . . . . . 17
5.4. ICMP Source Quench . . . . . . . . . . . . . . . . . . . 18
5.4.1. Reasons for Non-deployment . . . . . . . . . . . . . 18
5.4.2. Lessons Learned . . . . . . . . . . . . . . . . . . . 18
5.5. Triggers for Transport (TRIGTRAN) . . . . . . . . . . . . 19
5.5.1. Reasons for Non-deployment . . . . . . . . . . . . . 20
5.5.2. Lessons Learned. . . . . . . . . . . . . . . . . . . 21
Show full document text