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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 15 July 2020 15:33 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 84CDC3A0039 for <panrg@ietfa.amsl.com>; Wed, 15 Jul 2020 08:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 1TxIQm4ygXCm for <panrg@ietfa.amsl.com>; Wed, 15 Jul 2020 08:33:48 -0700 (PDT)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (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 C8CAF3A0035 for <panrg@irtf.org>; Wed, 15 Jul 2020 08:33:45 -0700 (PDT)
Received: by mail-lj1-x22f.google.com with SMTP id b25so3074956ljp.6 for <panrg@irtf.org>; Wed, 15 Jul 2020 08:33:45 -0700 (PDT)
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 :cc; bh=KkoBfj1C/Z2x8gWmJTa53wbxbw1Rr7uO6pjrmqpzBG4=; b=rURjD/fH6RTJhIdgUaTGplKirOqG5uJDwc6TGTJYh2bzjEpLh2Y+m8Kv7zA7O2GLgf Ed+nZcRjMahcQiS1Q6NsidgM1WS0ynw8zcGNO+eqopvtV+Wu56dl3cFa2kAbbPonDwDU SqB+nbRw1P1ZCnaXdawnmHOEf5x2I5g96+Vo4CrAOrFZ2ivcskZ7ko7lkRNI021KvgvE BjkqHiK5OHyaAE/pPGHcrKj1aBdrVnJ6K2mSe8uG2A6oH06Z/08Edb+2YZJ8Dsfzqjzj yOtsBBQh1zBKvVTL9hn1MdsTQuLIyZNyDk+XTIYU7Fd0vNGWrnB05D0VfhuZVphnK86s 83Dw==
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:cc; bh=KkoBfj1C/Z2x8gWmJTa53wbxbw1Rr7uO6pjrmqpzBG4=; b=P0gj3HQYm6TSEX9noWOlfKkQoWLwpARe0zEO0d8xpOwrioONBFLSClopbT+amQmPhP I84N3mXDSsj3Y7cYTMDUuugHqF9FHLZFfWjun8ZoEPmTpsqLSoHFs49/rzy7DN7iwLPV thwWxxiGW9FX09d1LHCuDEKwsLLJAWuNEEIqt2GpCaRg9zbTgxmJ06Nd3pEMleNbkroR wqAIreGb2u7CaKEhOjiSNgh04yeACcSs7jadZw+CbRsHUheILXbW+3Y8FemNtwLSm6jk n/W0+EizQR+sN41298wz6R+7jvfIWoJKSOQuFo+dQRCa6XO9euMg9qD9QsjAkt82Eg/b GqFg==
X-Gm-Message-State: AOAM530gqV+HJqKLC/uF+0luyoPVgpnaSgnbiIYsNEuNKOSvs5LFnvZY UlLBDafG658eGFq83XJN38A1qsiMWQqizltYrSM=
X-Google-Smtp-Source: ABdhPJwgGEeed4xIvKuJOSYqxO/Leqlw9WIhiTPN/Co7SiKAbVbwVPVcM1IXoq2aOf9Nb+jsxvYlih0BnPGRDuXqFgI=
X-Received: by 2002:a2e:8043:: with SMTP id p3mr5377430ljg.469.1594827223599; Wed, 15 Jul 2020 08:33:43 -0700 (PDT)
MIME-Version: 1.0
References: <159417679704.25830.1254352128780008991@ietfa.amsl.com> <CAKKJt-e7k+x0rqYg_y8Nv4ht0Sh0qDvt65mAqeoncCT+WGwnUQ@mail.gmail.com> <24122_1594823879_5F0F14C7_24122_77_8_787AE7BB302AE849A7480A190F8B9330314F99C0@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <24122_1594823879_5F0F14C7_24122_77_8_787AE7BB302AE849A7480A190F8B9330314F99C0@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 15 Jul 2020 10:33:16 -0500
Message-ID: <CAKKJt-fPOWCBWDoZtYLiaeR3ArrR+-pJe_Sad-m4ECWPADbjzA@mail.gmail.com>
To: Mohamed Boucadair <mohamed.boucadair@orange.com>
Cc: panrg@irtf.org
Content-Type: multipart/alternative; boundary="000000000000240e4e05aa7ca644"
Archived-At: <https://mailarchive.ietf.org/arch/msg/panrg/GYTbAZKbG32vus-vCb3hEiwJCbQ>
Subject: Re: [PANRG] I-D Action: draft-irtf-panrg-what-not-to-do-10.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, 15 Jul 2020 15:33:49 -0000

I got this comment in private e-mail, but I'm responding on-list, because
the comment affects at least two working group drafts. My apologies to Med
for that.

Hi Med,

On Wed, Jul 15, 2020 at 9:37 AM <mohamed.boucadair@orange.com> wrote:

> Hi Spencer,
>
>
>
> Other than the version change, I don’t see any “text” change in -10.
>

I managed to trip over a bug in the datatracker/tools pages submitting -09
(Robert and Henrik are still nudging everything back into place), so -10
was just a resubmit with the version number bumped. Doing
https://www.ietf.org/rfcdiff?url2=draft-irtf-panrg-what-not-to-do-09.txt
shows the actual diff I was submitting.

If you have to make a change, I would rather include the definition rather
> than adding a pointer to the questions I-D. I don’t think it is a good idea
> to have I-D.irtf-panrg-questions as normative.
>

I may have misunderstood the details about what we talked about at the
PANRG interim meeting. Let me ask the research group, so I'm only
submitting one update, if that's needed.

What I'm pretty sure we agreed, was to have the draft authors go off in a
corner and come up with a working definition that would go in -questions,
rather than have four definitions (one in the charter and three in our
research group drafts).

So far, so good ...

It seemed right to me that I would point to the definition in -
I-D.irtf-panrg-questions in what-not-to-do, rather than repeat the working
definition in what-not-to-do.

It seemed right to me that the reference to  I-D.irtf-panrg-questions would
be normative, so that's what I did.

ANOTHER way of doing this, is repeating the definition from
I-D.irtf-panrg-questions in what-not-to-do, with an informative reference
to  I-D.irtf-panrg-questions.

Does anyone object to me copying the definition over?

Best,

Spencer


>
>
>
> Cheers,
>
> Med
>
>
>
> *De :* Panrg [mailto:panrg-bounces@irtf.org] *De la part de* Spencer
> Dawkins at IETF
> *Envoyé :* mercredi 8 juillet 2020 05:02
> *À :* panrg-chairs@irtf.org
> *Cc :* panrg@irtf.org
> *Objet :* Re: [PANRG] I-D Action: draft-irtf-panrg-what-not-to-do-10.txt
>
>
>
> Dear Brian and Jen,
>
>
>
> This version now points to the working definition of "path awareness" in
> panrg-questions. From my perspective, it's ready to go forward for
> publication.
>
>
>
> Make good choices, of course.
>
>
>
> Best,
>
>
>
> Spencer
>
>
>
> On Tue, Jul 7, 2020 at 9:53 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-10.txt
>         Pages           : 36
>         Date            : 2020-07-07
>
> 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.
>
>
> 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-10
> https://datatracker.ietf.org/doc/html/draft-irtf-panrg-what-not-to-do-10
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-irtf-panrg-what-not-to-do-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/
>
>
> _______________________________________________
> Panrg mailing list
> Panrg@irtf.org
> https://www.irtf.org/mailman/listinfo/panrg
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>
>