Re: [Idr] Existing solutions in enforcing Flow based forwarding can be used by draft-dunbar-idr-5g-edge-compute-app-meta-data
"Acee Lindem (acee)" <acee@cisco.com> Wed, 02 December 2020 21:37 UTC
Return-Path: <acee@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1443B3A1600 for <idr@ietfa.amsl.com>; Wed, 2 Dec 2020 13:37:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.619
X-Spam-Level:
X-Spam-Status: No, score=-9.619 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=WxDH4xGZ; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Dw5Jd+4d
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 LSakDm6RiYgd for <idr@ietfa.amsl.com>; Wed, 2 Dec 2020 13:37:47 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C61443A156E for <idr@ietf.org>; Wed, 2 Dec 2020 13:36:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=25223; q=dns/txt; s=iport; t=1606944987; x=1608154587; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=cbTYg43/hfQsWvEQTzO8bf5aZuA4QsR8gKgvaMj2Yko=; b=WxDH4xGZvfoQib019701dpwK3ZHnjMiiyFvF1oqQTtQr2452N0TJIaB6 OqH7t9g+cmnMvEMdg2/bKmytZomqbZP2VrG5PRxEOl8/Z9fh3uGFQAcVp 6eadKeh0skNGFcAl8mx+oyRtpyYI0SZQDJWgJaS+kGlJCwD+LnFnV9WpM 8=;
X-IPAS-Result: A0D/BwDyB8hffY0NJK1igliBIy9RfA5NLy4KhDKDSAONXJkIglMDVAsBAQENAQEnBgIEAQGBNAGCUUQCF4F9AiU3Bg4CAwEBAQMCAwEBAQEFAQEBAgEGBBQBAYY8DIVyAQEBAQMSER0BATgPAgEIEQMBAiQHAgICMB0IAQEEARIbB4MEAYF+VwMuAQ6iXAKBPIhpdoEygwQBAQWBMhU/AoMeGIIQAwaBOIJzg3aGVxuCAIE4HIInLj6CXQEBAYFGOA2CajOCLJBYEIMahyadVAqCcpszAx+iJB2TVaEVAgQCBAUCDgEBBYFsIoFBEQdwFTsqAYI+UBcCDY5YgzqEWYV/dAI1AgYBCQEBAwl8jmcBgRABAQ
IronPort-PHdr: 9a23:v76OBhc8tOmCl/0K8fTzK+vslGMj4e+mNxMJ6pchl7NFe7ii+JKnJkHE+PFxlwaTB9fV9u5ZkefJvqGmUmsFst6Ns3EHJZpLURJNycAbhBcpD8PND0rnZOXrYCo3EIUnNhdl8ni3PFITFJP4YFvf8XOv8SMIFwryNEx+IeGmUoLXht68gua1/ZCbag5UhT27NLV1Khj+rQjYusQMx4V4LaNkwRrSqXwOcONTlm4=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.78,387,1599523200"; d="scan'208,217";a="622337143"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 02 Dec 2020 21:36:26 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by alln-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id 0B2LaQbk029179 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 2 Dec 2020 21:36:26 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 2 Dec 2020 15:36:26 -0600
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 2 Dec 2020 16:36:25 -0500
Received: from NAM10-MW2-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 2 Dec 2020 15:36:24 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=TinUhza6j9s0NBKRJZGRi6kLY+zqo504vmJESgpTX0LFCEt/GAkW56mPTcc+cPnfnosSrGS4r9EArxSWMD/K0iOT5Ow6y83zeMbiUKdWKJ8xDwYwP0OjchjJt/nGV86wweUHr3qP0lCx3RafqPLuAm9Abr5QHrxov34rEmZTi49l9YtmkIjXd/4jHO1fCZJPGmlVBNwpJTMlOHbs136LCbKrHR3leO7dIQ1ZvkhEbnLNUfV78lSl51Mq9kFKKfPKTPA9lhD5rahtRbGqHltTbfkLXA0FQCIQfYznaPPGSbfa5pkkHG5Qggn0prA0ufbqKb8PCH8uhep5M3/PYmWkbw==
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=cbTYg43/hfQsWvEQTzO8bf5aZuA4QsR8gKgvaMj2Yko=; b=lMOIh7qNtBmSuDTA5xeW9GexFlaSjgx52i63FbBPp9MQyMDuG8M1FvYnSbK3J8pgti5HcMN8CwC2xnu45LuNZT37EVkrqxxN8FJdoXHV+sRIRBr0lNpOochRLG+1utmvearfSSPX3hvApoIsEhiZGudNlFfcCqDQ8pnOp9mLKmhhNLUtaCPR+lx8HX1/Eme199ZGkDlekP3v2/IbQEuOKgnmwqGJdR195w5rtaQFaHnb14paCFSyYQFTfvvSn9unMct+1HMYXLLllkHFL6wvbW4XV/OY9KBaphVUaMSL5irfi6lvW+mUGQv7/d4Rsir+FgonzVHRfYO4B8N8YqzsMg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=cbTYg43/hfQsWvEQTzO8bf5aZuA4QsR8gKgvaMj2Yko=; b=Dw5Jd+4d/XwDyrlmgl6HRiBBC/pizS+bumc1THjmrV/2YTePN0KEr1dRQHPdljJVqt9jOuuV90NxfSy4xpoh9Ts6p5rpc2sMpR7vqz0fWHpfZuHAzFW2XLBguXF/FE5zQ9JdfUd1W+8AFPiRDiTW8JDiODYu8fnfW2GD7eSunq0=
Received: from BYAPR11MB2887.namprd11.prod.outlook.com (2603:10b6:a03:89::27) by SJ0PR11MB4909.namprd11.prod.outlook.com (2603:10b6:a03:2af::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3611.20; Wed, 2 Dec 2020 21:35:09 +0000
Received: from BYAPR11MB2887.namprd11.prod.outlook.com ([fe80::65a7:2fad:a960:2557]) by BYAPR11MB2887.namprd11.prod.outlook.com ([fe80::65a7:2fad:a960:2557%3]) with mapi id 15.20.3611.031; Wed, 2 Dec 2020 21:35:09 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Linda Dunbar <linda.dunbar@futurewei.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: Existing solutions in enforcing Flow based forwarding can be used by draft-dunbar-idr-5g-edge-compute-app-meta-data
Thread-Index: AdbIDqowHb3+VOrRTI6SVuOpy6sGLQAum5cA
Date: Wed, 02 Dec 2020 21:35:09 +0000
Message-ID: <3C8F724B-DBE1-4C70-A055-9CFB822D69A9@cisco.com>
References: <SN6PR13MB233415994F565A8F8B12682985F40@SN6PR13MB2334.namprd13.prod.outlook.com>
In-Reply-To: <SN6PR13MB233415994F565A8F8B12682985F40@SN6PR13MB2334.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.43.20110804
authentication-results: futurewei.com; dkim=none (message not signed) header.d=none;futurewei.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [136.56.133.70]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: cee8898c-42ab-42a1-2fc1-08d8970a24ea
x-ms-traffictypediagnostic: SJ0PR11MB4909:
x-microsoft-antispam-prvs: <SJ0PR11MB49097BE7798EF0FBE1528487C2F30@SJ0PR11MB4909.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: gh3Icbt9zu+w/y0rUPoUVPju6Vc3He4MGxpStmQHFY5g3pF9C+mzDgS0vyjtos4XeCgT45+6Mr0zGhh5ZuOvE4STbOhL0MLbRqXnwISnit8vpKM5BN3FxsuoEaCCi6i5pRpPI1g/Pew//vLTeukk2qRCgl6L78pt/jEyE0X1ag/dcR2enG4gAMh+5p/nt27R1W4ZGTdH3XI06Csl0jynrTXrDcv0Vqpun9xe8AfseSwWXukYyTQwZtqKGHrDQzD/F8l92Mg4Sat/fPRyx0r3hr2uKJ3j377WueHC5NFMxvLM8DK0VqbYmbJzwuNE2WzimF6d5a/MFKPTQRZAOe/Upa8Cp5xajt1QHatDIFTF5+PAxTjUzJq+0V6aLSpbMxyST+EIYVcGbxSiK6hMwWk/ncM/sEsHvGvKF1qei7bjjx9FiHGTaXAerjY2ggFsxCv/LLRkZoC2BtP0H/EiwGzSLg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BYAPR11MB2887.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(376002)(366004)(396003)(346002)(39860400002)(136003)(5660300002)(316002)(66446008)(64756008)(66476007)(186003)(66556008)(6486002)(66946007)(8676002)(166002)(76116006)(86362001)(26005)(53546011)(9326002)(2906002)(33656002)(2616005)(66574015)(8936002)(6506007)(478600001)(21615005)(966005)(71200400001)(6512007)(83380400001)(110136005)(36756003)(45980500001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: qUERLXZPLtsTVtF4NlNSUlfz/3szMLBkSCKEquYKXhUc2qqnNAE+MIzGMsiQM8pPASVV8+S4zL7ke3yziaCZG91uZoB7SvRtm3gcDZeer0V4YgFYsQVNVozieDLb2FUl/EUonVQj7aRYMvmQ9ZK6rObd+b1B2RKa5ulmoqp0KT6mYycCR0t22tMzm8No3GMsQ5ijKh4jrQvYyRgXqi+2SmWHDe1PvtCw6xjFaLxbdiJx8QNStDvBTTcSQuNiU22rt2C8PCrfBWybGdxIutG0ZCmSSESbs/eO04++wuD3oJfTXJ2kaMoV1ofmXB8hHoGbzMMUYxXL0DSt3bJxB2Onk2dqopLTUmNCaCoZdZndlvBpguK2vc0oNzOtyPvy//lLrH7UEFxUE8F1sIxNhjF5Iy0jTo7Lg+Ohiw46BlZin8AQlQ6AhwkXd2Mw6U0bmUSJM4BmTz8hyHi0BJ3Woy0lQ88moiyE9r2zTmRJr2pCh+1OddV7ueRkVtbcRjwZkW/j1iy0Qik6llAcgPE3SagDpDo6Cqeqecv6C4oWZcwaONIZkBMtjRTET3prXCwxebDdmY0AcYLfwW5w6jQWISdatpEAI/f4+9EA+IEwykxBIZJEUY/2oY3xNE7o7+cqwBwJp0LAaQDasULPZZtSiUMnVuighqx7BRrzTWTL9jgaWHyKEB3bnqK3wU8YNfHPazugPIhXdegakopvDQpPczW2p8g4O+Rfow4a4bOx/+YlgyE673JLaYAM02LoWipw2NV6UnQsnP4tXqrICwNlG0ct4wRVEDAfvAbNsm9VdNDj1lfYB4O/RcyzCWtYduOwTgGEnTC6Fe/gNeQ+asmdRpnB/QDSg3qlFd42LX1PKLrJQ4wH9eRV5iU4F0ox2rrrsXdSiOY5ClaeCqFM5osVhEEVxIkfNqMrRnS3ffX76GXJazheCkqnUUIf0H7uDaQZYvcIcJBJVKgrAZ+oOja5sEjgy3uDe5665IAm2jT0FvpHgzxyaa+txVJBmZyY8C44H+YK
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_3C8F724BDBE14C70A0559CFB822D69A9ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BYAPR11MB2887.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: cee8898c-42ab-42a1-2fc1-08d8970a24ea
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Dec 2020 21:35:09.6270 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: MGtm1I/DQNUaVknXCqHjpYd782/p/6BghCluyKnb8d95jlHh/0bc8pg5jF57dCWw
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SJ0PR11MB4909
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.12, xch-rcd-002.cisco.com
X-Outbound-Node: alln-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/J2IWucTHvHO8UInnexzTiBBBQiA>
Subject: Re: [Idr] Existing solutions in enforcing Flow based forwarding can be used by draft-dunbar-idr-5g-edge-compute-app-meta-data
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Dec 2020 21:37:57 -0000
Hi Linda, There are a couple limitations here that need to be covered in the draft. The first is that you are assuming the anycast servers are all attached to a router one hop away (or at least on a path where the first hop will always on the shortest path to the same instance of an anycast server). Otherwise, your assumption of the routing decision being made solely in the 5G site router doesn’t hold. Second, when there is a handover from the Site A router to the Site B router, how does the Site B router know which instance of the anycast server the UE was bound to on the Site A router? I guess it doesn’t without some design. Thanks, Acee From: Linda Dunbar <linda.dunbar@futurewei.com> Date: Tuesday, December 1, 2020 at 1:21 PM To: Acee Lindem <acee@cisco.com>, IDR List <idr@ietf.org> Subject: Existing solutions in enforcing Flow based forwarding can be used by draft-dunbar-idr-5g-edge-compute-app-meta-data Acee, You asked a question on how to enforce one flow to be nailed towards the same location for an ANYCAST address during the IETF 109 IDR Friday session. Here are some links showing that the commercial routers already support the feature, a.k.a. Flow Affinity, or Flow-based load balancing. https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/lanswitch/configuration/xe-3s/lanswitch-xe-3s-book/lnsw-flow-portchannel-load.html https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/data-flow-affinity-edit-chassis.html draft-dunbar-idr-5g-edge-compute-app-meta-data states that the ingress node, i.e. the router Ra/Rb which are adjacent to 5G UPF (or Packet Session anchor point-PSA), can use Flow ID (in IPv6 header) or UDP/TCP port number combined with Source Address in IPv4 to enforce packets in one flow being placed in one tunnel to one Egress router, such as R1, R2, or R3 in the figure below. All other nodes in the network don’t need to take any extra action. Does it address your concern? +--+ |UE|---\+---------+ +------------------+ +--+ | 5G | +---------+ | S1: aa08::4450 | +--+ | Site +--++---+ +----+ | |UE|----| A |PSA| Ra| | R1 | S2: aa08::4460 | +--+ | +---+---+ +----+ | +---+ | | | | | S3: aa08::4470 | |UE1|---/+---------+ | | +------------------+ +---+ |IP Network | L-DN1 |(3GPP N6) | | | | +------------------+ | UE1 | | | S1: aa08::4450 | | moves to | +----+ | | Site B | | R3 | S2: aa08::4460 | v | +----+ | | | | S3: aa08::4470 | | | +------------------+ | | L-DN3 +--+ | | |UE|---\+---------+ | | +------------------+ +--+ | 5G | | | | S1: aa08::4450 | +--+ | Site +--++-+--+ +----+ | |UE|----| B |PSA| Rb | | R2 | S2: aa08::4460 | +--+ | +--++----+ +----+ | +--+ | | +-----------+ | S3: aa08::4470 | |UE|---/+---------+ +------------------+ +--+ L-DN2 Figure 1: App Servers in different edge DCs Thank you very much Linda Dunbar
- [Idr] Existing solutions in enforcing Flow based … Linda Dunbar
- Re: [Idr] Existing solutions in enforcing Flow ba… Acee Lindem (acee)
- Re: [Idr] Existing solutions in enforcing Flow ba… Linda Dunbar
- Re: [Idr] Existing solutions in enforcing Flow ba… Aijun Wang
- Re: [Idr] Existing solutions in enforcing Flow ba… Linda Dunbar
- Re: [Idr] Existing solutions in enforcing Flow ba… Linda Dunbar