Subject: [Int-area] suggest you add Provider managed Content into your consideration (was RE: Per-Application Networking Considerations

From: Linda Dunbar <[email-masked]>
Date: Fri, 20 Nov 2020 03:04:14 +0000

Tommy,

Thank you for writing this memo. Too bad that you didn’t get around to discuss this topic at the Interarea WG session yesterday.

Section 1 of your draft states:
if an application is to receive different treatment, the host or the application itself should be involved in requesting specific network treatment. This document explores the implications.¶<https://www.ietf.org/archive/id/draft-per-app-networking-considerations-00.html#section-1-3>

In 3GPP 5G edge computing project, there is a AF function that control the information exchange with 5G System to enhance the Edge Computing Service performance, as shown below.

It would be worthwhile to add those scenarios to your considerations. We have a presentation slot at the Friday  6MAN WG session (first on the Friday Agenda)
https://datatracker.ietf.org/doc/draft-dunbar-6man-5g-edge-compute-sticky-service/

Hope you can attend the discussion to provide your comments.

Thank you
Linda Dunbar

From: Int-area <[email-masked]> On Behalf Of Tommy Pauly
Sent: Monday, November 16, 2020 10:22 PM
To: [email-masked]
Subject: [Int-area] Per-Application Networking Considerations

Hello INTAREA,

We published a draft this week that we’d like to briefly introduce for discussion within the intarea WG, draft-per-app-networking-considerations. This is an informational document that discusses the implications of a trend we’ve noticed towards putting more application identifiers or per-application logic in the network layers. Many different proposals touch on the idea of differentiating traffic based on application, but we believe it would be useful to have a general statement about the privacy trade-offs and design considerations in this space. Moreover, we think that a broad technical group like intarea may be the right place to discuss and review this work.

https://www.ietf.org/archive/id/draft-per-app-networking-considerations-00.html<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-per-app-networking-considerations-00.html&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C1b51598c3fac4dd7027508d88ab06b61%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637411837605924809%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=LbYX5vi%2FT%2BTqPHoa%2Bu88Rqig9gbKHvkJM9APhjBf%2BRc%3D&reserved=0>

Your reviews and thoughts are appreciated!

Best,
Tommy & Lorenzo

Begin forwarded message:

From: [email-masked]<mailto:[email-masked]>
Subject: New Version Notification for draft-per-app-networking-considerations-00.txt
Date: November 15, 2020 at 8:02:12 PM PST
To: Lorenzo Colitti <[email-masked]<mailto:[email-masked]>>, Tommy Pauly <[email-masked]<mailto:[email-masked]>>

A new version of I-D, draft-per-app-networking-considerations-00.txt
has been successfully submitted by Tommy Pauly and posted to the
IETF repository.

Name:                  draft-per-app-networking-considerations
Revision:              00
Title:                      Per-Application Networking Considerations
Document date:               2020-11-15
Group:                  Individual Submission
Pages:                   7
URL:            https://www.ietf.org/archive/id/draft-per-app-networking-considerations-00.txt<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-per-app-networking-considerations-00.txt&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C1b51598c3fac4dd7027508d88ab06b61%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637411837605934803%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=NhsdU60UYUClzFvIFCDLYp0ov1Vg%2BfQ89rdsKhe1apU%3D&reserved=0>
Status:         https://datatracker.ietf.org/doc/draft-per-app-networking-considerations/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-per-app-networking-considerations%2F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C1b51598c3fac4dd7027508d88ab06b61%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637411837605934803%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=Hbj5KFCy0leo80EWcEASkqo1MkZbYlzp0R1YREglfUU%3D&reserved=0>
Html:           https://www.ietf.org/archive/id/draft-per-app-networking-considerations-00.html<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-per-app-networking-considerations-00.html&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C1b51598c3fac4dd7027508d88ab06b61%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637411837605944791%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=li9s0dthmLKh5urNXKBbWSW4xZeNvIQOBZVqNem0sV0%3D&reserved=0>
Htmlized:       https://tools.ietf.org/html/draft-per-app-networking-considerations-00<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-per-app-networking-considerations-00&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C1b51598c3fac4dd7027508d88ab06b61%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637411837605944791%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=o9pZguU1HIe7JIJQmpdU9xblQsRyPiuytvgyxDUdPbM%3D&reserved=0>

Abstract:
  This document describes considerations for and implications of using
  application identifiers as a method of differentiating traffic on
  networks.  Specifically, it discusses privacy considerations,
  possible mitigations, and considerations for user experience and API
  design.

Discussion Venues

  This note is to be removed before publishing as an RFC.

  Source for this draft and an issue tracker can be found at
  https://github.com/tfpauly/per-app-networking-considerations<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftfpauly%2Fper-app-networking-considerations&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C1b51598c3fac4dd7027508d88ab06b61%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637411837605954796%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=ETCr85belinto10ENo5kJgl2w1sM0bw4A5hbkVFVh7U%3D&reserved=0>.

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftools.ietf.org%2F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C1b51598c3fac4dd7027508d88ab06b61%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637411837605964780%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=XehxFKeoX5Ua6nNDRmZXYEMwTNXrHhptnTPhwKAKMRs%3D&reserved=0>.

The IETF Secretariat