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

Joe Touch <touch@strayalpha.com> Sat, 15 August 2020 00:37 UTC

Return-Path: <touch@strayalpha.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 961943A0B2F; Fri, 14 Aug 2020 17:37:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.319
X-Spam-Level:
X-Spam-Status: No, score=-1.319 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, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 2t5tN1TJcRN0; Fri, 14 Aug 2020 17:37:28 -0700 (PDT)
Received: from server217-4.web-hosting.com (server217-4.web-hosting.com [198.54.116.98]) (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 20E6C3A14DF; Fri, 14 Aug 2020 17:37:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Transfer-Encoding:Content-Type:Sender: Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender :Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=Fx/TU+ZuvEtlxt/3IUNV08Sqs+1rkMkbT4jpWIiDrOY=; b=rv6SbC92mptndsbz/AQIAB4Wm3 4xYJFH2bXzZnc8LvclQvkV9NBrF3lh+xoVUIc8zayz2wjlTS2MhghlskC9PtYqjFptN7YH6DL8XfO Fivs/kYHjjTkQ96CIEQmNpSEqPHoM8p++PnhvIwE7R+EDIn8QoE3p/JqaSpkMh+Pfu8ZS+JT2G6zs zS2HtXOyBn9gkOjKJm1PptPYT6OMqvxpz3qywQc/oKhEmqNruYNvxqA3SLQnKdx14IB4Ukpk/DZ/s b/hjLgIh7EL7acizgDflUNbWU9CX7IcgMSb7Isj9gBer2W2wVOrJD0NAZEQ71yd1UZkEER5JBCZO8 xUtAVLyQ==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:49182 helo=[192.168.1.5]) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <touch@strayalpha.com>) id 1k6kCG-002tyR-3i; Fri, 14 Aug 2020 20:37:24 -0400
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <5A5B4DE12C0DAC44AF501CD9A2B01A8D9381CC52@dggemm512-mbs.china.huawei.com>
Date: Fri, 14 Aug 2020 17:37:19 -0700
Cc: "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>, "daniel@olddog.co.uk" <daniel@olddog.co.uk>
Message-Id: <171DEAE6-BC06-44B8-88E9-64BA20850450@strayalpha.com>
References: <5A5B4DE12C0DAC44AF501CD9A2B01A8D9381CC52@dggemm512-mbs.china.huawei.com>
To: Lizhenbin <lizhenbin@huawei.com>
X-Mailer: iPhone Mail (17G80)
X-OutGoing-Spam-Status: No, score=-0.2
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/37QqXtXsRYec5MzRuGbq0PRngcI>
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: Sat, 15 Aug 2020 00:37:30 -0000

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

> 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