Re: [PANRG] I-D Action: draft-irtf-panrg-what-not-to-do-04.txt

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Mon, 04 November 2019 03:09 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: panrg@ietfa.amsl.com
Delivered-To: panrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 630AC120871 for <panrg@ietfa.amsl.com>; Sun, 3 Nov 2019 19:09:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id avtm3ERzVJXq for <panrg@ietfa.amsl.com>; Sun, 3 Nov 2019 19:09:09 -0800 (PST)
Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE1B9120959 for <panrg@irtf.org>; Sun, 3 Nov 2019 19:09:08 -0800 (PST)
Received: by mail-lj1-x232.google.com with SMTP id 139so15934384ljf.1 for <panrg@irtf.org>; Sun, 03 Nov 2019 19:09:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=dYxFNt43CADoPHj3Gfgu2kykHVKAoNmTTlM/mqbDJig=; b=uIhwW+lCoSfvhnrKPXzKfuvqu4toGqR/AQvGGfExS2oW8TX/J/dGllP2zR08Uyt83F PFB1IJ0ntVF77KcYhvwzBm1aqvtqzgZBroXkN2uFUCXeF1ndgkzqFaIwSGktdeCdYfG8 ITk5Q7DihqnKNTV21w5JN/NIvxeDBzXfQ8bDdSnytIMejBudD9f0COZ/7yLldxSZcGC5 FWHOouGrtVQbXh8M/AgynREk4byraSGb97SICy95s31mUnb5RlaxJls+XToArgylWSUI HYIYgjFgQt2jg8iKOOBb3lP4gUWxXw+RaARI4+DIdI1INJgM28jg7NHEX7raMb8ZtTB8 Swvw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=dYxFNt43CADoPHj3Gfgu2kykHVKAoNmTTlM/mqbDJig=; b=NY3Tjn6bSWMyUXytNXEe0VyDeoP78lcG2pTwVYr5x+NMA2xS8QnPsL+d8KuisATPm0 wZRjy6ZxewfgF2oiR1BDY/zxBpT+WHeOw1KS2x0ZygQTq5JpWDzGD9bQ9EM2fQIFD72I wbvnzhCkFuNA9oaMRZ77pcID0ACqQ9o9xYEslQdKe+yaz8/jWhzkhQynQJWEP6ZqZ8W4 v/9PdRI/cqRbgYWruxPwYwLAtddiS7M/rD9R2hUxQ1TPkMHd25PBgg8kCHtNip4HIOZT COr0w3cfPPZK8LZH7XWzYGFGcA9qh/17zgdMCrZ4zt7stRGtJe7wXb580I55MXyiGyTy 1cjA==
X-Gm-Message-State: APjAAAX2Z8GB+3lJOuMQGrmXCl8PNO5zGsC6n7VqlF4JVLWdHWwXs/W7 tuF00DVr3D0PiOVJWILttN5lbGVzew8mm87+Fimtkg==
X-Google-Smtp-Source: APXvYqyPdK9TLztMgbOs2ryOB3luQGlAB0BQ4N5wK8erPhs/F+OC+MeZJe3k6VNobzUQO4Yw4M611XsfITlNutS2obk=
X-Received: by 2002:a2e:858f:: with SMTP id b15mr16893120lji.68.1572836946501; Sun, 03 Nov 2019 19:09:06 -0800 (PST)
MIME-Version: 1.0
References: <157283651841.13257.12041055131542329112@ietfa.amsl.com>
In-Reply-To: <157283651841.13257.12041055131542329112@ietfa.amsl.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sun, 03 Nov 2019 21:08:37 -0600
Message-ID: <CAKKJt-f+sKd2GRYNn7C9DMtNVox1LJsg-HSBVLDedU7j_1S3qA@mail.gmail.com>
To: panrg@irtf.org
Content-Type: multipart/alternative; boundary="0000000000007c646305967ca381"
Archived-At: <https://mailarchive.ietf.org/arch/msg/panrg/OPtoGY21CRFrHm81nI8p4OLIkbo>
Subject: Re: [PANRG] I-D Action: draft-irtf-panrg-what-not-to-do-04.txt
X-BeenThere: panrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Path Aware Networking \(Proposed\) Research Group discussion list" <panrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/panrg>, <mailto:panrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/panrg/>
List-Post: <mailto:panrg@irtf.org>
List-Help: <mailto:panrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/panrg>, <mailto:panrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Nov 2019 03:09:16 -0000

Dear PANRG,

On Sun, Nov 3, 2019 at 9:02 PM <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Path Aware Networking RG RG of the IRTF.
>
>         Title           : Path Aware Networking: Obstacles to Deployment
> (A Bestiary of Roads Not Taken)
>         Author          : Spencer Dawkins
>         Filename        : draft-irtf-panrg-what-not-to-do-04.txt
>         Pages           : 34
>         Date            : 2019-11-03
>
> 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.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-irtf-panrg-what-not-to-do/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-irtf-panrg-what-not-to-do-04
> https://datatracker.ietf.org/doc/html/draft-irtf-panrg-what-not-to-do-04
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-irtf-panrg-what-not-to-do-04
>
>
> 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/
>
> _______________________________________________
> Panrg mailing list
> Panrg@irtf.org
> https://www.irtf.org/mailman/listinfo/panrg


I've included a description of our discussion at IETF 105 on whether the
Lessons we've Learned are design invariants, or whether Path Aware
Networking technology designers need to look at their proposals and
consider those lessons.

I've also added a correction from David Black (thanks, David!).

My apologies for not pushing harder on this draft since IETF 105, but I've
now secured ongoing IETF sponsorship, so please expect more of me in the
future.

Please feel free to send comments or corrections via e-mail or Github pull
requests, as described in the draft.

I look forward to continued discussion in Singapore, whether you're there
in person or on Meetecho.

Travel safely.

Spencer