Re: [arch-d] APN (Application-aware Networking) Mailing List

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Mon, 17 August 2020 18:52 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB1A53A1055; Mon, 17 Aug 2020 11:52:37 -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 VL58exIEwYt0; Mon, 17 Aug 2020 11:52:36 -0700 (PDT)
Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) (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 D289C3A0FA9; Mon, 17 Aug 2020 11:52:33 -0700 (PDT)
Received: by mail-yb1-xb2b.google.com with SMTP id y134so9994453yby.2; Mon, 17 Aug 2020 11:52:33 -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=xZHYRn6htPC2hDmXfSirSouzOkMsZGPSRoOV8DWtao4=; b=ngcC5IAHzMPOn7HhsH7Usf3t3zF4F4eSl/zVSPJfq/scI9ozRIVvsdXPaCIrUpO+L3 ZAXQPhJxsJRkGrlCzQKW2Z3EHsRIFxF4J495HKYdJTduZAYnfIjJjxvIKXNl84CGYjya cnOqE+PBZzjY1OpF1ScOCjO1XbDNrdh72RBPYzGyIyb+O+I0txH67Ds6uSvLmA5clChV QQqKzEXoEXQtpmiJH6ABKBgkZM054+JrgYOGZucd6G0kqxn4za5DRwhKcqKEeJFBz/Qr HEfqO1CdhNawT+PYhs+JnJugzgt2+6NwKrCGyj61lNM2ZeRwSDG5xafoIK2OjyJVgdt9 9d6g==
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=xZHYRn6htPC2hDmXfSirSouzOkMsZGPSRoOV8DWtao4=; b=d/1gzwW1Zp/yNFe5EUFiECrfOPYLmjhQpYIuskjZyUJBdVH4EoBXklPKB5poryRxIq qFjl4gCDn3Co4BtlowIqB8fg7y0CuvUttZTRiQyp8xXsToLxFiVQFRayGhsNbreK3Z4y pINlC3lFaOVjfu4x/ZwY2/awvkbh6AN4Ccg/hON35tInnHP1ZUzySr1H/3FQI1j6iWck aSfJ5ENFkB958kl/Rx5XSkQzktqBHW3HC7xJk8O47rJZNZh09ys+MEDMUmBqOTc79D1t 34r8q62DsIkgKIj43UpvCjHO3uuwsB82mqVTRVlrVYS3q+upWa7wkxLW8mHtMw/yOxqG zVVg==
X-Gm-Message-State: AOAM530UJ+xf09vWF2QzLlYGPue9jkiRfutAkplfPkM/3eJRIoW5dWXN gwl6Ep+TLTJFMXEtEjE5TFR8fU8z6GRUIdkdpJQ=
X-Google-Smtp-Source: ABdhPJwndBZvRC2TytoRaUIf7KDx4LvJAYv9XxpK3/rGd3rGsDlUKeRoWts1LVUPtzEKfJNy2a8IlcN3kCPQMHZsmUU=
X-Received: by 2002:a25:40cb:: with SMTP id n194mr21940561yba.380.1597690353019; Mon, 17 Aug 2020 11:52:33 -0700 (PDT)
MIME-Version: 1.0
References: <5A5B4DE12C0DAC44AF501CD9A2B01A8D9381CC52@dggemm512-mbs.china.huawei.com> <171DEAE6-BC06-44B8-88E9-64BA20850450@strayalpha.com>
In-Reply-To: <171DEAE6-BC06-44B8-88E9-64BA20850450@strayalpha.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 17 Aug 2020 13:52:06 -0500
Message-ID: <CAKKJt-f16EsJa62Cym6XTakVBSo4OmwQWAqbxOQTOfDQTm01qQ@mail.gmail.com>
To: Lizhenbin <lizhenbin@huawei.com>
Cc: "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>, "daniel@olddog.co.uk" <daniel@olddog.co.uk>, "rtgwg@ietf.org" <rtgwg@ietf.org>, Joe Touch <touch@strayalpha.com>, panrg-chairs@irtf.org
Content-Type: multipart/alternative; boundary="000000000000f3eee905ad1745df"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/8uCkgstjoTpf5g3qgeeMc1DwWLU>
Subject: Re: [arch-d] APN (Application-aware Networking) Mailing List
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Aug 2020 18:52:41 -0000

Adding the PANRG chairs, in case I get something wrong about PANRG ...

On Fri, Aug 14, 2020 at 7:37 PM Joe Touch <touch@strayalpha.com> wrote:

> This WG appears to be revisiting the issues of the expired trigtran wg. It
> might be useful to understand why that did not succeed and whether you are
> asking the same question twice and expecting a different answer.
>

Joe. thank you for nudging me on this thread.

PANRG (https://datatracker.ietf.org/rg/panrg/about/) has a draft about the
history of Path-Aware Networking (
https://datatracker.ietf.org/doc/draft-irtf-panrg-what-not-to-do/), and why
most path-aware networking technologies haven't been deployed, although it
seems they should have been deployed (especially to the people who proposed
them).

TRIGTRAN specifically is covered in
https://tools.ietf.org/html/draft-irtf-panrg-what-not-to-do-12#section-5.5,
but TRIGTRAN was one of eight technologies considered, and we found enough
commonality to justify summarizing what we learned in 12 lessons (
https://tools.ietf.org/html/draft-irtf-panrg-what-not-to-do-12#section-2),
and then considering whether what we've learned is still relevant (
https://tools.ietf.org/html/draft-irtf-panrg-what-not-to-do-12#section-3).
Some are, some aren't.

This document doesn't have any standing in the IETF, other than providing
information, but I hope it's helpful for you (full disclosure, I'm the
editor).

Best,

Spencer


> Joe
>
> > On Aug 12, 2020, at 9:25 PM, Lizhenbin <lizhenbin@huawei.com> wrote:
> >
> > Hi Folks,
> >
> > The APN mailing list has been created. If you have interest in the work,
> please subscribe.
> >
> > List address: apn@ietf.org
> > Archive: https://mailarchive.ietf.org/arch/browse/apn
> > To subscribe: https://www.ietf.org/mailman/listinfo/apn
> >
> > Purpose:
> > This email list is the discussion list for the Application-aware
> Networking (APN). Application-aware Networking is a mechanism whereby
> traffic flows can be steered and routed within the network to ensure that
> the specific service levels needed by applications can be delivered.
> >
> > This list belongs to IETF area: RTG
> >
> >
> > Look forward to going on to have more discussion in the mailing list.
> >
> >
> >
> > Best regards,
> > Zhenbin (Robin)
> >
> >
> >
> > ________________________________________
> > 发件人: Architecture-discuss [architecture-discuss-bounces@ietf.org] 代表
> Lizhenbin [lizhenbin@huawei.com]
> > 发送时间: 2020年7月29日 0:17
> > 收件人: architecture-discuss@ietf.org; rtgwg@ietf.org
> > 抄送: daniel@olddog.co.uk
> > 主题: [arch-d] APN (Application-aware Networking) Side Meeting
> >
> > Hi All,
> > We will have the APN side meeting at 12:30 - 14:00 UTC on July 30
> (Thursday). The agenda and the WebEx information is provided in the
> following link.
> > https://github.com/APN-Community/IETF108-Side-Meeting-APN
> >
> > There has been several similar work like APN such as SPUD and PLUS.
> Recently Network Token work was also proposed. The side meeting is to try
> to clarify the scope of APN comparing with other work. The possible
> usecases are also proposed for the APN work. Another goal of the side
> meeting is to clarify the security and privacy issues which are always
> proposed against such application-ware networking work. In RTGWG session
> held yesterday, the presentation of APN work discussed the possible
> scenarios related with the security and privacy issues. The following
> slides is for your reference:
> >
> https://www.ietf.org/proceedings/108/slides/slides-108-rtgwg-8-rtgwg-apn6-01
> >
> > Since it is a complex cross-area work and there is much background
> information, wish you could join the side meeting if you have interest in
> the work and your comments and suggestions are appreciated.
> >
> >
> > Best Regards,
> > Daniel & Zhenbin (Robin)
> > _______________________________________________
> > Architecture-discuss mailing list
> > Architecture-discuss@ietf.org
> > https://www.ietf.org/mailman/listinfo/architecture-discuss
> > _______________________________________________
> > Architecture-discuss mailing list
> > Architecture-discuss@ietf.org
> > https://www.ietf.org/mailman/listinfo/architecture-discuss
>
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss
>