Path Aware Networking: Obstacles to Deployment (A Bestiary of Roads Not Taken)
draft-irtf-panrg-what-not-to-do-02

Document Type Active Internet-Draft (panrg RG)
Last updated 2019-03-31
Replaces draft-dawkins-panrg-what-not-to-do
Stream IRTF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream IRTF state (None)
Consensus Boilerplate Unknown
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
PANRG                                                    S. Dawkins, Ed.
Internet-Draft                            Wonder Hamster Internetworking
Intended status: Informational                            March 31, 2019
Expires: October 2, 2019

Path Aware Networking: Obstacles to Deployment (A Bestiary of Roads Not
                                 Taken)
                   draft-irtf-panrg-what-not-to-do-02

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 technologies, most of which were unsuccessful,
   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 October 2, 2019.

Copyright Notice

   Copyright (c) 2019 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 October 2, 2019                [Page 1]
Internet-Draft               What Not To Do                   March 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  A Note About Path-Aware Technologies Included In This
           Document  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Venue for Discussion of this Document . . . . . . . . . .   4
     1.3.  A Note for the Research Group . . . . . . . . . . . . . .   4
     1.4.  A Note for the Editor . . . . . . . . . . . . . . . . . .   4
     1.5.  Architectural Guidance  . . . . . . . . . . . . . . . . .   4
   2.  Summary of Lessons Learned  . . . . . . . . . . . . . . . . .   5
   3.  Template for Contributions  . . . . . . . . . . . . . . . . .   6
   4.  Contributions . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Stream Transport (ST, ST2, ST2+)  . . . . . . . . . . . .   7
       4.1.1.  Reasons for Non-deployment  . . . . . . . . . . . . .   8
       4.1.2.  Lessons Learned.  . . . . . . . . . . . . . . . . . .   8
     4.2.  Integrated Services (IntServ) . . . . . . . . . . . . . .   8
       4.2.1.  Reasons for Non-deployment  . . . . . . . . . . . . .   9
       4.2.2.  Lessons Learned.  . . . . . . . . . . . . . . . . . .   9
     4.3.  Quick-Start TCP . . . . . . . . . . . . . . . . . . . . .  10
       4.3.1.  Reasons for Non-deployment  . . . . . . . . . . . . .  11
       4.3.2.  Lessons Learned . . . . . . . . . . . . . . . . . . .  12
     4.4.  ICMP Source Quench  . . . . . . . . . . . . . . . . . . .  12
       4.4.1.  Reasons for Non-deployment  . . . . . . . . . . . . .  13
       4.4.2.  Lessons Learned . . . . . . . . . . . . . . . . . . .  13
     4.5.  Triggers for Transport (TRIGTRAN) . . . . . . . . . . . .  14
       4.5.1.  Reasons for Non-deployment  . . . . . . . . . . . . .  14
       4.5.2.  Lessons Learned.  . . . . . . . . . . . . . . . . . .  15
     4.6.  Shim6 . . . . . . . . . . . . . . . . . . . . . . . . . .  16
       4.6.1.  Reasons for Non-deployment  . . . . . . . . . . . . .  17
       4.6.2.  Lessons Learned . . . . . . . . . . . . . . . . . . .  18
       4.6.3.  Addendum on MultiPath TCP . . . . . . . . . . . . . .  18
     4.7.  Next Steps in Signaling (NSIS)  . . . . . . . . . . . . .  18
       4.7.1.  Reasons for Non-deployment  . . . . . . . . . . . . .  19
       4.7.2.  Lessons Learned . . . . . . . . . . . . . . . . . . .  20
     4.8.  IPv6 Flow Label . . . . . . . . . . . . . . . . . . . . .  21
       4.8.1.  Reasons for Non-deployment  . . . . . . . . . . . . .  21
       4.8.2.  Lessons Learned . . . . . . . . . . . . . . . . . . .  22
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  23
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  24
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  24
   8.  Informative References  . . . . . . . . . . . . . . . . . . .  24
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  30
Show full document text