[Apn] New to Application-aware Networking Discussions?

daniel@olddog.co.uk Wed, 12 August 2020 19:57 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 64A2E3A0863 for <apn@ietfa.amsl.com>; Wed, 12 Aug 2020 12:57:42 -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 aWpxwhGkEhuk for <apn@ietfa.amsl.com>; Wed, 12 Aug 2020 12:57:40 -0700 (PDT)
Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (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 EBE733A0593 for <apn@ietf.org>; Wed, 12 Aug 2020 12:57:36 -0700 (PDT)
Received: by mail-wr1-x42d.google.com with SMTP id c15so3144731wrs.11 for <apn@ietf.org>; Wed, 12 Aug 2020 12:57:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=danielking-net.20150623.gappssmtp.com; s=20150623; h=sender:from:to:cc:subject:date:message-id:mime-version:thread-index :content-language; bh=+ruGGmzWz5T8FFeQaXuOxmwvuW3QYxeKDRGsPqXy2FQ=; b=qqMQucUXNuqWCBEgUpmNMAM5Sfp495JdPSMG/A2t6bdooHyiKYjQ0PllIA7khyfqNj X25TpcZZpyuSljKh9m4onPt+xZA4kMf8VI0udq8ueZqalZOsMEOuoyvSL18tA/8hW2Ww hwGLP/b7wYxQLpq+oHtkUqQ/h3NnBNVnj4Pav+DX9wdLbqaXgc0rvhogFU81LtLRvfXF 5IdtQmyH6B6n+r135w3Ra4lMsMy3HFC2BaDMd4PEhMnwGxbI8X164JCorTQAOAIXyu5e A/9S7V+Q7n0axMAKZrLxqHH3HEw7KY4dHCPZZ9R7pxxHnDge6k3UlrHgfdzXyHD3eplv FEKA==
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:cc:subject:date:message-id :mime-version:thread-index:content-language; bh=+ruGGmzWz5T8FFeQaXuOxmwvuW3QYxeKDRGsPqXy2FQ=; b=sr1HkSkLmWZtD1z1DC1mjFniWbgz+LQ5xYal9VZwHlg0WJ80NHe630j1C5GtiE6tvl i1n7+VlNBpGVCbU9wuUUMyM+8k6FrPj0ncreEEnciwHrXrcyFVf3kbYxV7zdspwobGBw Xb1grnh6e8pX+tN4XfcZfbyF7mPh+FC8Hvj15nzzDN+drtWajAm82TYgQpqtpmHmGepw ZzUNJ7i1lW+RD1sBAt7lm3auKG1Jm5EQQvAVfNIjy0Orrnt56z5qEfx6rNHHdKeldnB4 RLRuZJD/SRubhVOC+pCJon1dNabxp2f2w9ImsO13j+1DX6R6hwfyL2KvLE3W+1nvONhr Ueuw==
X-Gm-Message-State: AOAM532qZ/AL6qcpVYthwB8FEUH7umxtljY2pGb4rc3m2/6/9r0TjKYF ohDeGT6C8V3gZHCcruOPT02uaq9gY6hScwuu
X-Google-Smtp-Source: ABdhPJxFsNHJbHmfWWAsB8N2Dg1dJT1U2eJPBahhmsb4kNQIZH7gRod74A/hL9sDvSTZ6nNRi6ykMw==
X-Received: by 2002:adf:ec08:: with SMTP id x8mr664866wrn.235.1597262254529; Wed, 12 Aug 2020 12:57:34 -0700 (PDT)
Received: from CIPHER ([2a00:23c7:100:ca00:a57a:654f:ba4b:9a37]) by smtp.gmail.com with ESMTPSA id j2sm6381012wrp.46.2020.08.12.12.57.33 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Aug 2020 12:57:33 -0700 (PDT)
Sender: Daniel King <dk@danielking.net>
X-Google-Original-Sender: <dk@danielking.net>
From: <daniel@olddog.co.uk>
To: <apn@ietf.org>
Cc: "'Lizhenbin'" <lizhenbin@huawei.com>
Date: Wed, 12 Aug 2020 20:57:32 +0100
Message-ID: <001101d670e2$d15b9c10$7412d430$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0012_01D670EB.3320A050"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdZw4pJOAkm69d4kRpyOqKAI/PPCUQ==
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/apn/c1HbUImV5zfsUUwwqQPhZLjIi0k>
Subject: [Apn] New to Application-aware Networking Discussions?
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: Wed, 12 Aug 2020 19:57:42 -0000

Greetings!

 

In case you're new to the discussions, here is a summary of
Application-aware Networking (APN). 

 

What is APN? 

 

o 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 work is distinct from
tokens, where traffic flows are guided or classified onto tunnels or paths.

 

Have APN discussions already taken place?

 

o Yes, the most recent discussion occurred during IETF 108 as a side-meeting
(30th July 2020). The agenda and minutes are posted
(https://etherpad.wikimedia.org/p/v108-apn-side-meeting). The focus of the
session was to review the prior discussion (SPUD & PLUS) on the problem
space and ask operators to outline the use case and problem scope. 

 

o We have discussed potential solutions to the use cases and requirements
principal operators presented during the IETF 108 side-meeting.

 

Are there any APN or related I-Ds that I can read? (Yes)

 

o Problem Statement & Use cases:

- https://tools.ietf.org/html/draft-li-apn-problem-statement-usecases-00

- https://tools.ietf.org/html/draft-liu-apn-edge-usecase-00

- https://tools.ietf.org/html/draft-zhang-apn-acceleration-usecase-00

o Framework

- https://tools.ietf.org/html/draft-li-apn-framework-00

o Requirements on Application-awareness in Networks

- https://tools.ietf.org/html/draft-yiakoumis-network-tokens-01

- https://tools.ietf.org/html/draft-herbert-fast-04

- https://tools.ietf.org/html/draft-li-6man-app-aware-ipv6-network-00

 

Why did we create an APN  discussion list?

 

o There has been a lot of initial APN interest between early collaborators.
We need to continue the discussion and see if this work is relevant to the
IETF community, and if there is a willingness to develop solutions to the
use cases and requirements that the operators have identified. 

 

Kind Regards,

Dan and Robin