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

daniel@olddog.co.uk Tue, 18 August 2020 09:09 UTC

Return-Path: <dk@danielking.net>
X-Original-To: apn@ietfa.amsl.com
Delivered-To: apn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E4363A0807 for <apn@ietfa.amsl.com>; Tue, 18 Aug 2020 02:09:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=danielking-net.20150623.gappssmtp.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 Q67iwCBn8VSN for <apn@ietfa.amsl.com>; Tue, 18 Aug 2020 02:09:27 -0700 (PDT)
Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (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 2AD4D3A0802 for <apn@ietf.org>; Tue, 18 Aug 2020 02:09:26 -0700 (PDT)
Received: by mail-wm1-x32e.google.com with SMTP id g8so15565681wmk.3 for <apn@ietf.org>; Tue, 18 Aug 2020 02:09:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=danielking-net.20150623.gappssmtp.com; s=20150623; h=sender:from:to:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=5vrjmTbzWN5d5WbWOWszGbhE+dNFIeeVkCv/1NnTscs=; b=F6d5/8cRqVXlXtUCtRdU/p1FAE5tAWfN0yIzPfu0B7yNI+/5DubOW/0U3uslyDPqsu rAoEYUIB/F670Wt/r1rbbjZfLZorGD9vYM9/SGF6RMmZS5GGgZpnyIdcX05O8y5yftgu PeQkc+Dr7/HM5TuvZaG0uxp6ZYVYpymzvNXPCryw10pr2jp7x2uF79G3iYJSBJbI0gtK 27Ex8OsL4v55Eyb0XpRP4Yuu3t79HfnAo5RUC7tuX/TTJ8yOPIYAWpgBXoql/oJFPseT F6WX0t+0Qi+PZaGL3fOIHWSL6SBtOI74QHtxxj6vzQKFPf2zR4eVi3hBe8GMieyrHtfV tpLQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:references:in-reply-to:subject :date:message-id:mime-version:thread-index:content-language; bh=5vrjmTbzWN5d5WbWOWszGbhE+dNFIeeVkCv/1NnTscs=; b=LBwAmxapcR7iTT5+0t9BR+r8ZFkDrgwlHlQJJN2vs5x7R4AZzxuW7k8jffzMCbJFjx ovCoJLkkBmwhP3LwUe66MxwPEi1KI30N/pi3XriJsE0qmR51Gqo/J0N85nuk/NF21uCS wGlLm9dnyz2qD7jUOJvWVbCDAP8lKDShfHPNzpgYcI5nMI3pLaBUCwzn5MEEvOCvP1HM NclpvQHKBkI+XvfRh+xEZCZ+p1stgwZzzAww8lm0azxLpjwuJrG//uTVy/55ntWyKmV9 H1yyjuZ0MXONTkO1lcjIb5YPmLfR+ZNTojdsGfYvKuZdpEtLe0o1V9y0MKrJiMixwWFd qsRA==
X-Gm-Message-State: AOAM53368eAkKQkqQc9sW6mLFAYgx6ttfPTUu4J13Y3fbfvispLeTCnZ IRd1fsnrkQEdbrrjug6OhuHYLjWcXHbk7byZ
X-Google-Smtp-Source: ABdhPJyfgcEJ4jzETSaz378mzimBzfqSDei9Rrrj6fYYEbq+CBKjCaoETwUv1nAWvx2BhmwrYi9ngg==
X-Received: by 2002:a1c:448a:: with SMTP id r132mr18042816wma.158.1597741761427; Tue, 18 Aug 2020 02:09:21 -0700 (PDT)
Received: from CIPHER ([2a00:23c7:100:ca00:cc35:1314:ee50:63b3]) by smtp.gmail.com with ESMTPSA id b7sm30823227wrs.67.2020.08.18.02.09.20 for <apn@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Aug 2020 02:09:20 -0700 (PDT)
Sender: Daniel King <dk@danielking.net>
X-Google-Original-Sender: <dk@danielking.net>
From: <daniel@olddog.co.uk>
To: <apn@ietf.org>
References: <5A5B4DE12C0DAC44AF501CD9A2B01A8D9381CC52@dggemm512-mbs.china.huawei.com> <171DEAE6-BC06-44B8-88E9-64BA20850450@strayalpha.com> <CAKKJt-f16EsJa62Cym6XTakVBSo4OmwQWAqbxOQTOfDQTm01qQ@mail.gmail.com>
In-Reply-To: <CAKKJt-f16EsJa62Cym6XTakVBSo4OmwQWAqbxOQTOfDQTm01qQ@mail.gmail.com>
Date: Tue, 18 Aug 2020 10:09:17 +0100
Message-ID: <008701d6753f$410da110$c328e330$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0088_01D67547.A2D4A120"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHWcpxSZIXZn4Fr1kqEHxPhhvLq4ak8qcgAgADvaWA=
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/apn/s_Bjpz4vWuiEIRa8B2szf98e3OE>
Subject: [Apn] FW: [External] Re: [arch-d] APN (Application-aware Networking) Mailing List
X-BeenThere: apn@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Application-aware Networking <apn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apn>, <mailto:apn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/apn/>
List-Post: <mailto:apn@ietf.org>
List-Help: <mailto:apn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apn>, <mailto:apn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Aug 2020 09:09:31 -0000

 

From: Architecture-discuss <architecture-discuss-bounces@ietf.org> On Behalf Of Spencer Dawkins at IETF
Sent: 17 August 2020 19:52
To: Lizhenbin <lizhenbin@huawei.com>
Cc: panrg-chairs@irtf.org; rtgwg@ietf.org; architecture-discuss@ietf.org; daniel@olddog.co.uk
Subject: [External] Re: [arch-d] APN (Application-aware Networking) Mailing List

 

This email originated outside the University. Check before clicking links or attachments.

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 <mailto: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/ <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Frg%2Fpanrg%2Fabout%2F&data=02%7C01%7Cd.king%40lancaster.ac.uk%7Cf3df80414d9e4329a2ff08d842dec957%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C1%7C637332871918266347&sdata=Tg9VKUA2LkLSNrWkEhYKSmK4LENqhUAmA1xbAP%2BnTfY%3D&reserved=0> ) has a draft about the history of Path-Aware Networking (https://datatracker.ietf.org/doc/draft-irtf-panrg-what-not-to-do/ <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 <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-irtf-panrg-what-not-to-do-12%23section-5.5&data=02%7C01%7Cd.king%40lancaster.ac.uk%7Cf3df80414d9e4329a2ff08d842dec957%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C1%7C637332871918276293&sdata=ILlxhGKKPRf%2Fb1jU9Gi4v9IvVPUN8yBKY0N6L4vBt5s%3D&reserved=0> , 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 <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-irtf-panrg-what-not-to-do-12%23section-2&data=02%7C01%7Cd.king%40lancaster.ac.uk%7Cf3df80414d9e4329a2ff08d842dec957%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C1%7C637332871918276293&sdata=rrgMWiFCTSMd%2Fs30xtQ2%2BhKdMac4avJyaehlYiU27yo%3D&reserved=0> ), 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 <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-irtf-panrg-what-not-to-do-12%23section-3&data=02%7C01%7Cd.king%40lancaster.ac.uk%7Cf3df80414d9e4329a2ff08d842dec957%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C1%7C637332871918286260&sdata=LnZuyulU7uqLEtIypz6hpl3iW%2FkFGyJXAx261f5mVYI%3D&reserved=0> ). 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 <mailto: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 <mailto:apn@ietf.org> 
> Archive: https://mailarchive.ietf.org/arch/browse/apn <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fbrowse%2Fapn&data=02%7C01%7Cd.king%40lancaster.ac.uk%7Cf3df80414d9e4329a2ff08d842dec957%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C1%7C637332871918286260&sdata=%2F1ao5J2uRqGeBbEzIZ9%2BjBG0OCSynGnROUDhjEgBcsw%3D&reserved=0> 
> To subscribe: https://www.ietf.org/mailman/listinfo/apn <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fapn&data=02%7C01%7Cd.king%40lancaster.ac.uk%7Cf3df80414d9e4329a2ff08d842dec957%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C1%7C637332871918286260&sdata=NO6q1VztegN7jvxh36PjA45zfkv4r6xk2%2B6PTIissAU%3D&reserved=0> 
> 
> 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 <mailto:architecture-discuss-bounces@ietf.org> ] 代表 Lizhenbin [lizhenbin@huawei.com <mailto:lizhenbin@huawei.com> ]
> 发送时间: 2020年7月29日 0:17
> 收件人: architecture-discuss@ietf.org <mailto:architecture-discuss@ietf.org> ; rtgwg@ietf.org <mailto:rtgwg@ietf.org> 
> 抄送: daniel@olddog.co.uk <mailto: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 <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAPN-Community%2FIETF108-Side-Meeting-APN&data=02%7C01%7Cd.king%40lancaster.ac.uk%7Cf3df80414d9e4329a2ff08d842dec957%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C1%7C637332871918296209&sdata=q0qRltwYw%2BPQkbSnTNyjHqfuKCb30mB%2BiV35oDOl0jI%3D&reserved=0> 
> 
> 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 <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fproceedings%2F108%2Fslides%2Fslides-108-rtgwg-8-rtgwg-apn6-01&data=02%7C01%7Cd.king%40lancaster.ac.uk%7Cf3df80414d9e4329a2ff08d842dec957%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C1%7C637332871918296209&sdata=OJh2urJmlvVjUFzga8%2FE7KlltKBgDY6rL83Yc7uz7k8%3D&reserved=0> 
> 
> 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 <mailto:Architecture-discuss@ietf.org> 
> https://www.ietf.org/mailman/listinfo/architecture-discuss <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Farchitecture-discuss&data=02%7C01%7Cd.king%40lancaster.ac.uk%7Cf3df80414d9e4329a2ff08d842dec957%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C1%7C637332871918306166&sdata=Vb%2FUuRJPJcpK3syIwVcYV221%2BTs9TPSOcspp8LmKT8w%3D&reserved=0> 
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org <mailto:Architecture-discuss@ietf.org> 
> https://www.ietf.org/mailman/listinfo/architecture-discuss <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Farchitecture-discuss&data=02%7C01%7Cd.king%40lancaster.ac.uk%7Cf3df80414d9e4329a2ff08d842dec957%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C1%7C637332871918306166&sdata=Vb%2FUuRJPJcpK3syIwVcYV221%2BTs9TPSOcspp8LmKT8w%3D&reserved=0> 

_______________________________________________
Architecture-discuss mailing list
Architecture-discuss@ietf.org <mailto:Architecture-discuss@ietf.org> 
https://www.ietf.org/mailman/listinfo/architecture-discuss <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Farchitecture-discuss&data=02%7C01%7Cd.king%40lancaster.ac.uk%7Cf3df80414d9e4329a2ff08d842dec957%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C1%7C637332871918306166&sdata=Vb%2FUuRJPJcpK3syIwVcYV221%2BTs9TPSOcspp8LmKT8w%3D&reserved=0>