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

Michael Welzl <michawe@ifi.uio.no> Wed, 20 November 2019 09:59 UTC

Return-Path: <michawe@ifi.uio.no>
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 24E74120890 for <panrg@ietfa.amsl.com>; Wed, 20 Nov 2019 01:59:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Q4imSoKVtT7Y for <panrg@ietfa.amsl.com>; Wed, 20 Nov 2019 01:59:26 -0800 (PST)
Received: from mail-out01.uio.no (mail-out01.uio.no [IPv6:2001:700:100:10::50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B31B612081F for <panrg@irtf.org>; Wed, 20 Nov 2019 01:59:25 -0800 (PST)
Received: from mail-mx12.uio.no ([129.240.10.84]) by mail-out01.uio.no with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.3) (envelope-from <michawe@ifi.uio.no>) id 1iXMle-0002ll-QG; Wed, 20 Nov 2019 10:59:22 +0100
Received: from dhcp-96d5.meeting.ietf.org ([31.133.150.213]) by mail-mx12.uio.no with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) user michawe (Exim 4.92.3) (envelope-from <michawe@ifi.uio.no>) id 1iXMlc-0005Hv-Is; Wed, 20 Nov 2019 10:59:22 +0100
From: Michael Welzl <michawe@ifi.uio.no>
Message-Id: <48D5BAA2-82CD-450D-86F1-158C9B2D1BED@ifi.uio.no>
Content-Type: multipart/alternative; boundary="Apple-Mail=_245D3CEF-82DA-46CB-B015-73584FE19C72"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 20 Nov 2019 17:59:16 +0800
In-Reply-To: <CAKKJt-dLzVuyLYrBeEveaXtpciYTGWvytZwCKJ8OoqGtvpKYEw@mail.gmail.com>
Cc: panrg@irtf.org
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
References: <157283651841.13257.12041055131542329112@ietfa.amsl.com> <CAKKJt-f+sKd2GRYNn7C9DMtNVox1LJsg-HSBVLDedU7j_1S3qA@mail.gmail.com> <CAKKJt-dLzVuyLYrBeEveaXtpciYTGWvytZwCKJ8OoqGtvpKYEw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-UiO-SPF-Received: Received-SPF: neutral (mail-mx12.uio.no: 31.133.150.213 is neither permitted nor denied by domain of ifi.uio.no) client-ip=31.133.150.213; envelope-from=michawe@ifi.uio.no; helo=dhcp-96d5.meeting.ietf.org;
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, HTML_MESSAGE=0.001, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 4DFBCA25208EE988674F3762D8F10EA2D71D0AC9
Archived-At: <https://mailarchive.ietf.org/arch/msg/panrg/RiWwdtI0p--i0aSFxYLbug0iflY>
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: Wed, 20 Nov 2019 09:59:29 -0000

Hi,

I recently read this, for the first time after a long break (I think my last time was -00), and I must say that I love this document.
So useful, and so well written!  Congratulations!

Cheers,
Michael


> On Nov 20, 2019, at 5:37 PM, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:
> 
> Dear PANRG,
> 
> I realized three things as I worked on slides for IETF 106.
> I am planning to ask for a Last Call within the research group in the near future, and 
> There is significant new text in -04 describing the IETF 105 discussion that I haven't heard comments on, from the research group, and
> Our session is in the last slot of Friday, and I have 15 minutes, and I would LOVE it if we don't spend precious face to face time wordsmithing new text that Spencer has written. 
> If you have an opportunity to take a look at https://tools.ietf.org/rfcdiff?url2=draft-irtf-panrg-what-not-to-do-04.txt <https://tools.ietf.org/rfcdiff?url2=draft-irtf-panrg-what-not-to-do-04.txt> before Friday, focusing on Section 3, that would be great, and if you have an opportunity to send email or pull requests about anything that seems strange or insane, that would be REALLY great.
> 
> Thanks,
> 
> Spencer, as editor
> 
> 
> On Mon, Nov 4, 2019 at 11:08 AM Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com <mailto:spencerdawkins.ietf@gmail.com>> wrote:
> Dear PANRG, 
> 
> On Sun, Nov 3, 2019 at 9:02 PM <internet-drafts@ietf.org <mailto: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/ <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://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 <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 <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 <http://tools.ietf.org/>.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/ <ftp://ftp.ietf.org/internet-drafts/>
> 
> _______________________________________________
> Panrg mailing list
> Panrg@irtf.org <mailto:Panrg@irtf.org>
> https://www.irtf.org/mailman/listinfo/panrg <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
> _______________________________________________
> Panrg mailing list
> Panrg@irtf.org
> https://www.irtf.org/mailman/listinfo/panrg