Re: [Apn] A new draft on APN for your review, thank you!

Linda Dunbar <linda.dunbar@futurewei.com> Wed, 20 January 2021 16:27 UTC

Return-Path: <linda.dunbar@futurewei.com>
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 6EB863A14DB; Wed, 20 Jan 2021 08:27:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 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, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 rwpDEVZWDUN4; Wed, 20 Jan 2021 08:27:22 -0800 (PST)
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (mail-eopbgr690110.outbound.protection.outlook.com [40.107.69.110]) (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 0F48F3A14D8; Wed, 20 Jan 2021 08:27:21 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DjsqEEnsjcgQLUBCowes8/xK2ok+c5c6HG6uOSGc1+ib7w/J6pzaCNcBoyiCaxIV40ssjp01TrypmF4oxG+zsbUNf7zzOXRoyBjlMw3ysvICeLbCOq3pvMHve20f83H/KZq9aJUvvvqJpKrBL+Rh2mZrBOh1dKmey9aJ+UC+hB0kUFDGkh34+crjYsfAiZQxINkVP/fjD8iZxwfKnW0jJTU6DANVoBN2kyi5lfHcNoc6jJKgJNUDysuxk6tCLgTjQPdRjJt4Em0ZSn/cEYfnj1+6UVbYsnzyaReOi7Tf3YKAh41Ze2Tn3SpxssUSKjB4mumjDiwwYl6CacfjFx6NSQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=CquDsLwY4tdkecMYO+X8JEt5mU6bPNGFroLqPXAR1eQ=; b=ZiJ/xgtKuEwCi1QvLPc4QjUx1hd3n/XV5Lc+rjTnerzQ+ew0nAvrwRBw18B5WEhwHZx9/py5CnMp6T5qRJmuvV6Nr42gn/cfxPBUbnDLk55+vSV7QVJbsZydcDXnw0jjmaOPo5TeT8weyxcCCsQQmNgbY5blsa6fCVwqOxIoh43JiS6E0p7ZDXsT0Pjr+vjV0RXcXJw6xK5pD7ftG0vjhlO4MhlfCpFMaQZJFWvJGRm0Y6RzhheMEvp30R2obMqyhWKomDagWNLUjvsEvwJJK5n7A/iyVW6GuDi4RY/aCxY03TDB5xBHk6pVnqprMDzigk5xFC5xvA6+vluOWLTnTw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=CquDsLwY4tdkecMYO+X8JEt5mU6bPNGFroLqPXAR1eQ=; b=hPIj8wlc+EKdaa/iRmAnHEq0sRoQnkoOrSRj6klirj9JmIhYWROBiHWI5hgp01/KSyjwEvU8Tr4giwjQAcDCFHdtOWNrMYvO54c7jdAI46NyeBMpS7D53H6OSK9jCEgxS5iKjdw3MSxgGP8gy59j/ziBq2DHncIUKLio1ITC8XI=
Received: from DM6PR13MB2330.namprd13.prod.outlook.com (2603:10b6:5:cc::16) by DM6PR13MB3196.namprd13.prod.outlook.com (2603:10b6:5:19f::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.7; Wed, 20 Jan 2021 16:27:19 +0000
Received: from DM6PR13MB2330.namprd13.prod.outlook.com ([fe80::c1e2:96dd:2538:b0c4]) by DM6PR13MB2330.namprd13.prod.outlook.com ([fe80::c1e2:96dd:2538:b0c4%3]) with mapi id 15.20.3763.014; Wed, 20 Jan 2021 16:27:18 +0000
From: Linda Dunbar <linda.dunbar@futurewei.com>
To: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>, "apn@ietf.org" <apn@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Thread-Topic: A new draft on APN for your review, thank you!
Thread-Index: AdbSj5OZJp0yHZz0SGiKnve9MVZvEAcTh4oQABokBCA=
Date: Wed, 20 Jan 2021 16:27:18 +0000
Message-ID: <DM6PR13MB23304D634C339923835657E285A20@DM6PR13MB2330.namprd13.prod.outlook.com>
References: <4278D47A901B3041A737953BAA078ADE197FAE1A@DGGEML532-MBX.china.huawei.com>
In-Reply-To: <4278D47A901B3041A737953BAA078ADE197FAE1A@DGGEML532-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;huawei.com; dmarc=none action=none header.from=futurewei.com;
x-originating-ip: [72.180.73.64]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 17894fb7-0162-4565-88ed-08d8bd6041b4
x-ms-traffictypediagnostic: DM6PR13MB3196:
x-microsoft-antispam-prvs: <DM6PR13MB31964CABF5CE04285C47EF8085A20@DM6PR13MB3196.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 9cdzUlGuOVFKe5cSZTEYepL60IEimHvFPQ54D+mJBmO9tgqjiWyfLduZS/tHeHsyr8a04hI2WPWQ6Z7sxRPKS/vmkqhddRNs//32YEkK+yPG+FJN+I/t/+SsuT9ocJbPBaXzT0j7gGBROzwuGfdqbfDy5wb4NENM1pSH5xxkp13ivfIa9wezjES0qKgbArfv1x2aJ5eN/19LFBc81rSnZ4UvH7f8sObBo1HAn4YQADeXKKSZvusIURcGzM97k8/HE6VgVtqBOU9vdsKU8VT3vKSs70Bfp3pvALxZs8BmkQUoVCQ9X7Z9N1Gluh0O0pGaMnF7Js9442gW9mCyTkcMR9WFPVzWlAxZX1GnDwgu4o4TvXHO1SkkMBMggMo+sY2Qy4VP4jGhBXbNWNQYI9W+SVfNbXKtkZOSs3K8aCi3oCZ49qjhcLL0Y0zdZS8XxSiYG/q268dssmoh051U1EzTDVlbbyDuL0RbLJ0dQa5V86XsWqjTigZyzp3KSelzfvSFEVVhgG0hgANppoGWr/0tmzj5aaIM6x+9dKWqYS6S5KXK2Wmdj2KhQrEnqMAlBziES+NPdE4A5DIrRbgtYdOZ3VZrzNj6po/tJf61vghUFYfNWvNt5O/whJtt5B6lT2J7nTSdWO0plBEgfpCH1xze4g==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM6PR13MB2330.namprd13.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(376002)(346002)(39840400004)(396003)(136003)(366004)(478600001)(66446008)(186003)(86362001)(4001150100001)(7696005)(316002)(110136005)(52536014)(9686003)(76116006)(83380400001)(66946007)(26005)(64756008)(2906002)(166002)(33656002)(6506007)(4743002)(53546011)(66476007)(966005)(66556008)(8936002)(71200400001)(8676002)(44832011)(5660300002)(55016002)(15398625002); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: jczKhpBArmDblrB3Mg9JlDpzsspljvhLo0Tts6suH/gRFucnN0inCA+yxGRpRmM2ibx2xzza/E//7fhfOi8uBR6hXN5X7DqPFYfnFJlzpJFVwJhjxv+Zwd9aE3WcsRJaY98BLfYa059+yPrY+nDmgTV1d6h2dN2iXOMFEQo0hJZqHvhn7uYTvyy/EvcRQL35zGopqNQZjNJXDuw+fAO8DqfqurQ6VtxcVPiTtMt+8XJkPWZcFC+M4IDJBhTAJosAOI6QCJRkuGUhuf9MXXJZbasSCgHySFgMFkoVYrl0cFxqLDbwT+ZmWKi+cqF9ppnV0+qCtd5Nzrt7ihTReQQ9WOnwmUkjdLdaNNNIy4epGeFvv5lN178X6HUeQdIn+aSMWCG3yCtjJjInj2ztMBjU/uPkZe2TaCgD3l38AqPV0Vpx/fVaQkq52huGzO0nohd0IIq50zHV6LdBmgwAkY0TkA7RdtzPrlbxgiHLYrArl29qAfsaNPsuBrujsJ1+1lg3u6SHFhwjAIZQzs4w7rCbSNve8U3shSSg22kr+aBuHIqPpWR+EeOwXv+tZfLxlXtQimucpg63JWrkxW19s3QmcJhXCj5lQ5JcoULJc7CSAseAUhTe1H3hp/2jZZusexCx90LoKHimjYx4ZVty/vrEZftXU7/RII262SzsuNksgoiQizvb0u1cyJA14TThjiNhPYNWfteLBarQR5RvnCxp2mbzz9I5t6KM7218RuvVCFNGgz+venj7ZlI3rU+V/7IIzw04gE5A5JDsNcgo+8IErmcuOs4cmmIU7iwowjmZFPybvkYsKLsAt1qvOVfd93n8wWdZ4dbChm2W04cg/eoGQeRVavicYH15DShWLRPYu7ui3zYrFkXUHIsjO90zLXtl09SvWa0JXDtvJ4azLHtwljnV3E7D5RkWxeXDQKnkMm6qQv/YbPcV0N1jako5V44FOatDYtfODseGcO8rIvc4Ymxrc4wMcC4VETFkIx71gZrsnNIEAT3h2kLegd5Q0oHX2i7cFLkEvc9aO3oY6zWvWvggC0/iM0cOKsVvRtPgyFQkLb2o2hpDTCAhDHKqi2PL
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DM6PR13MB23304D634C339923835657E285A20DM6PR13MB2330namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR13MB2330.namprd13.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 17894fb7-0162-4565-88ed-08d8bd6041b4
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Jan 2021 16:27:18.9166 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: M7yJ3mfaB1Fa1xR6fHmHpKXXosWLGpix3rQ7Gzyhi56JUxKzDAeGCJMRgEJetOHkKxbqVkhWRMyJ7eLIjKn1ZQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR13MB3196
Archived-At: <https://mailarchive.ietf.org/arch/msg/apn/xJqbbGOCifbqTx3ZS5XvhiTMtzU>
Subject: Re: [Apn] A new draft on APN for your review, thank you!
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, 20 Jan 2021 16:27:25 -0000

ShuPing,

As described in the MEF70 document,
"APPID matches could be simple protocol matches (that could be accomplished with the other Criteria such as DPORT) such as "SSH" or "SNMP" or "RTP", but they can also support deeper inspection of packets such as "SNMP GET NEXT" or "HTTP POST" or "TWAMP [15] STOP-SESSION".

How does the standard match and the custom match work in the real system?
[Linda] Standard Match can be the combination of packet's 5 tuple header. Custom match can be using the DPI to extract out the payload as matching criteria (such as HTTP Post).

What are the key elements in the system? How do they interact?
[Linda] If the packets are encrypted, which are more and more often now, a subscriber has to provide the Key to the Service Provider for decrypt the packets if the subscribe needs the service provider to perform the application based forwarding.

Please let me know if you have further questions.

Linda Dunbar
From: rtgwg <rtgwg-bounces@ietf.org> On Behalf Of Pengshuping (Peng Shuping)
Sent: Wednesday, January 20, 2021 12:18 AM
To: apn@ietf.org; rtgwg@ietf.org
Subject: RE: A new draft on APN for your review, thank you!

Dear all,

In the MEF 70 "SD-WAN Service Attribute and Services", Table 4 on Page 36 has defined the fields (from layer 2 through layer 4) which are expected to be able to match against ingress IP Packets. APPID is explicitly listed as a criterion.

"The APPID Policy Criterion provides the ability for the Service Provider to define and name both simple and complex matches. These can include standard matches available to all of the Service Provider's Subscribers from a catalog and/or custom matches developed by the Service Provider by agreement with a particular Subscriber."

https://www.mef.net/wp-content/uploads/2019/07/MEF-70.pdf<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.mef.net%2Fwp-content%2Fuploads%2F2019%2F07%2FMEF-70.pdf&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C892e480ad68740030b8208d8bd0b2e21%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637467203005954259%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=VYMC84%2BEEFnTHMK9WEt53EU7Voj%2FJPKOKgtHKJsS1sc%3D&reserved=0>

Is there anybody who knows more about the details about this criterion and its implementations of the catalog and the interactions? How does the standard match and the custom match work in the real system? What are the key elements in the system? How do they interact?

Many thanks!

Best regards,
Shuping


From: Pengshuping (Peng Shuping)
Sent: Tuesday, December 15, 2020 11:12 AM
To: apn@ietf.org<mailto:apn@ietf.org>; rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Subject: A new draft on APN for your review, thank you!


Dear all,



A new draft on APN has been posted, https://datatracker.ietf.org/doc/html/draft-peng-apn-scope-gap-analysis<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-peng-apn-scope-gap-analysis&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C892e480ad68740030b8208d8bd0b2e21%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637467203005964256%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=C%2BchzeUr4e%2BHvC1avNuFQ0N7kzY1IhzR5Vo%2BtPc26W4%3D&reserved=0>.



In this draft, we clarified the scope of the APN work in IETF, introduced an example use case and the basic solution. Moreover, we compared with the existing "similar" work/solutions and did corresponding gap analysis.



Your review and comments are very much appreciated. Thank you!



Best regards,

Shuping





A new version of I-D, draft-peng-apn-scope-gap-analysis-00.txt

has been successfully submitted by Shuping Peng and posted to the IETF repository.



Name:              draft-peng-apn-scope-gap-analysis

Revision: 00

Title:                 APN Scope and Gap Analysis

Document date:      2020-12-16

Group:              Individual Submission

Pages:              11

URL:            https://www.ietf.org/archive/id/draft-peng-apn-scope-gap-analysis-00.txt<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-peng-apn-scope-gap-analysis-00.txt&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C892e480ad68740030b8208d8bd0b2e21%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637467203005964256%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=g7Aqz9wEarRwCFgxGiMtxaA7Y0YcQkCFJ6cjItNIUXY%3D&reserved=0>

Status:         https://datatracker.ietf.org/doc/draft-peng-apn-scope-gap-analysis/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-peng-apn-scope-gap-analysis%2F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C892e480ad68740030b8208d8bd0b2e21%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637467203005974253%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=oMC2LPj%2FeBc3qAW5qMiy42PpK%2F6NisLSZIt4nybx6Nk%3D&reserved=0>

Htmlized:       https://datatracker.ietf.org/doc/html/draft-peng-apn-scope-gap-analysis<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-peng-apn-scope-gap-analysis&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C892e480ad68740030b8208d8bd0b2e21%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637467203005974253%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=n2Bh%2F7hNbJfYrgJ1x6JMro8qFukhHN4B93SCYtZm5w0%3D&reserved=0>

Htmlized:       https://tools.ietf.org/html/draft-peng-apn-scope-gap-analysis-00<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-peng-apn-scope-gap-analysis-00&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C892e480ad68740030b8208d8bd0b2e21%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637467203005984248%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=V9etnojzROD4BiNUyChWgqyI%2B3SQOiWb5iqr8CjDly0%3D&reserved=0>





Abstract:

   The APN work in IETF is focused on developing a framework and set of

   mechanisms to derive, convey and use an identifier to allow for

   implementing fine-grain user-, application-, and service-level

   requirements at the network layer.  This document describes the scope

   of the APN work and the solution gap analysis.