APN Security and Privacy Considerations
draft-peng-apn-security-privacy-consideration-00

Document Type Active Internet-Draft (individual)
Authors Shuping Peng  , Zhenbin Li  , Daniel Voyer  , Cong Li  , Peng Liu  , Chang Cao 
Last updated 2020-09-29
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            S. Peng
Internet-Draft                                                     Z. Li
Intended status: Informational                       Huawei Technologies
Expires: April 4, 2021                                          D. Voyer
                                                             Bell Canada
                                                                   C. Li
                                                           China Telecom
                                                                  P. Liu
                                                            China Mobile
                                                                  C. Cao
                                                            China Unicom
                                                         October 1, 2020

                APN Security and Privacy Considerations
            draft-peng-apn-security-privacy-consideration-00

Abstract

   APN (Application-aware Networking) architecture aims to convey
   Application-aware Information including application/user/flow
   identifiers and SLA/service requirements along with the data packets
   into the network and make the network aware of applications and their
   requirements in order to provide corresponding application-aware
   network services and guarantee their SLA requirements.

   There have been challenges of the privacy and security issues that
   could potentially be introduced by conveying the application-aware
   information into the network.  This document describes the security
   and privacy considerations of APN in various possible scenarios
   wherein APN will be deployed.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

Peng, et al.              Expires April 4, 2021                 [Page 1]
Internet-Draft          APN Security and Privacy            October 2020

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 4, 2021.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminologies . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Adding Points of Application-aware Information  . . . . . . .   4
     3.1.  APN Framework . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  App-info added by the application . . . . . . . . . . . .   4
     3.3.  App-info added by the Network Edge Device . . . . . . . .   4
   4.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   5
     4.1.  Network Operator Self-Operating Application . . . . . . .   5
     4.2.  Application Providers Self-Operating Network  . . . . . .   5
     4.3.  Network Operator's Limited Controlled Domain  . . . . . .   5
     4.4.  Network Operator Controlled Edge Devices  . . . . . . . .   6
     4.5.  Encrypted App-Info carried in the data packets  . . . . .   6
     4.6.  Explicit App-Info carried in the data packets . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
     5.1.  Inter-DC Scenario . . . . . . . . . . . . . . . . . . . .   7
     5.2.  Enterprise Scenario . . . . . . . . . . . . . . . . . . .   7
     5.3.  Broadband Scenarios . . . . . . . . . . . . . . . . . . .   8
   6.  Potential Security Issues and Mitigations . . . . . . . . . .   9
     6.1.  One application within one terminal . . . . . . . . . . .   9
     6.2.  Two different applications within one terminal  . . . . .  10
Show full document text