Re: RTGWG feedback on APN next steps

Donald Eastlake <d3e3e3@gmail.com> Wed, 06 April 2022 22:41 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CD633A0EEB; Wed, 6 Apr 2022 15:41:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.857
X-Spam-Level:
X-Spam-Status: No, score=-6.857 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 0f2tK5HTbdR5; Wed, 6 Apr 2022 15:41:24 -0700 (PDT)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (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 279913A0EE9; Wed, 6 Apr 2022 15:41:24 -0700 (PDT)
Received: by mail-lf1-x12a.google.com with SMTP id bu29so6687496lfb.0; Wed, 06 Apr 2022 15:41:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Pc/k0QkUaNQt2r25sQkDVJ4k6QxSr/2ber6z8WxUc6c=; b=dZF3HUFh35GJjFdOtEeWXAJElPQTdijGfQ4iiJ97WBstO2fTnNgsemJNKpyyAf9BMl rCCAJ8J+nrQ/O2Ae67ZvrEAyf2HA8C6KLPPZh+LlvuQZ8lkOjs5OTR6rjXMlroGSYKnL 6hEFz7kjWQIBn+NC6/XRvfRyimcw4XVmVzsJVMqM/Ggvx5X9vMa3HO0R+OnfbbY7n4UG DmaGDwSAxTQUwFHEplaIoPlJg/huwVuHb5Pwjy3JLK92f/Sr670tDjESD5QpfT7mU7ZV kv6XIdY0LaU9rxzPMwlbIZJimfXtQn7jaEwwiUCvmqEdRkd35ivDgbvb7KUEuQKqEtoF +6HA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Pc/k0QkUaNQt2r25sQkDVJ4k6QxSr/2ber6z8WxUc6c=; b=erzjth/JP7fcR25dHC6tmOy75JWYAPSNeATkYZsFxSouV24hF26tTsZnJhvSFjt1g7 XP+b64mAXg1V+uCFZip2vhXlVQeCPecTi0MfWG8c+PuQXRMLcw1Lf8aplF55TgBcF3c6 s1vgjfBXyWuhebW/sCXLW3Pwgtmluvx4zTah4dX7i+BsUWBIweQLSpo7cfs/fvwVnbfC E5JOmlow5yvN04ZbHek37h6ZjqNLSvVVxLAGh+E20klodBtNpDA4UbDAws/XG6NjXZ6W gHIgFG4x7t2Ia65KdNfbUPeyrj2NfCZeH4Z2rpOQGURyKdAKeTiOEYl5REXh2kwY5oiW AcKA==
X-Gm-Message-State: AOAM53112X1XHF1JbYzPhjwlk9c6gkeBLFMxyVEYFn39QSJTouQpLxL+ zi87So0iUOvPGTRMrgMUMtXB3euRjxheILGazLq7vc5E
X-Google-Smtp-Source: ABdhPJwqkgQK+hyvnZ9lTV5/hztSUulDkFkVAEo095GTw7o3iSxHY4MzQ6H3uxYA9lnNcmgOJ2YAY6nCM6nh4aKwLI4=
X-Received: by 2002:a05:6512:e9a:b0:44a:3491:863a with SMTP id bi26-20020a0565120e9a00b0044a3491863amr7737463lfb.133.1649284882160; Wed, 06 Apr 2022 15:41:22 -0700 (PDT)
MIME-Version: 1.0
References: <204D8DE6-F51C-4551-B1D7-1D69DBCA3626@hxcore.ol>
In-Reply-To: <204D8DE6-F51C-4551-B1D7-1D69DBCA3626@hxcore.ol>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 6 Apr 2022 18:41:10 -0400
Message-ID: <CAF4+nEEpg54fCA=17rt1A95-=PUzBvbb_CtWjEh5voYDYdQMRw@mail.gmail.com>
Subject: Re: RTGWG feedback on APN next steps
To: Jeff Tantsura <jefftant.ietf@gmail.com>
Cc: RTGWG <rtgwg@ietf.org>, rtgwg-chairs <rtgwg-chairs@ietf.org>, "rtg-ads@ietf.org" <rtg-ads@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000088dec705dc040f0e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/n7HkiokBQ03coTTprf1WuC7_z6A>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2022 22:41:27 -0000

Hi,

I think that the APN scope has been sufficiently clarified and bounded and
that there are enough people interested and willing to work on it that the
formation of a WG is justified.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com


On Tue, Apr 5, 2022 at 1:15 PM Jeff Tantsura <jefftant.ietf@gmail.com>
wrote:

> Dear RTGWG,
>
>
>
>
>
> APN has been presented at RTGWG multiple times, and we see the evolution
> of the
>
> documents, including the scope of the problem and framework.  This topic
> needs
>
> collaboration across WGs; we can foresee that not all issues to be
> addressed are
>
> within the charter of RTGWG and would span beyond the Routing area.
>
>
>
> RTGWG is chartered to provide a venue for new work, there are a couple of
> different options and one option for handling
>
> such new work would be to recommend the development of a new WG.
>
> The Chairs would then want to recommend that the ADs consider forming a
> focus WG, with a set of well defined deliverables and milestones (after
> delivery the group would be shut down) to work on a framework for APN.
>
>
>
> We would like to solicit the WG for opinions.  Please note that comments
> about
>
> existing APN documents should be sent to apn@ietf.org.  This thread
> focuses on
>
> support or objection to recommending that the ADs consider the formation
> of a
>
> new WG.
>
>
>
> Please send your comments, support, or objectiond.
>
> Thanks!
>
>
>
>
>
> Cheers,
>
> Yingzhen  Jeff
>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>