Re: [spring] General Proxy behavior in SR Service Programming

"Francois Clad (fclad)" <fclad@cisco.com> Sun, 26 July 2020 19:33 UTC

Return-Path: <fclad@cisco.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C57B3A13E8 for <spring@ietfa.amsl.com>; Sun, 26 Jul 2020 12:33:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.62
X-Spam-Level:
X-Spam-Status: No, score=-9.62 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, 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=C1gwiNUK; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Tz8MnVZ2
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 oGXo0vNR7t63 for <spring@ietfa.amsl.com>; Sun, 26 Jul 2020 12:33:21 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 812C63A13E4 for <spring@ietf.org>; Sun, 26 Jul 2020 12:33:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3392; q=dns/txt; s=iport; t=1595792001; x=1597001601; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=AiOlYFqKzPDkXunlOquGmKDkA3JTE+WByXw2Bo8QzG0=; b=C1gwiNUKt0ELI4+ikJsLH/CFhvDk+ijksgSUqnnV4UnIkN1ZJn0FdxjA h4l1A0Kl2CkjiqdmIIDzlMCMAna9zS3e6vaxJ6JUee5JC3Z6YtT/cpMkI es6HzQaKIDX5fwGkOKFGQ8Wu7qnkCvCYqXCMnRIquT3MCIV18+pEY/dQK A=;
IronPort-PHdr: =?us-ascii?q?9a23=3AzSxY8xakm1LsjH5z23RL99//LSx94ef9IxIV55?= =?us-ascii?q?w7irlHbqWk+dH4MVfC4el21QWXD4fc5vZEgu7OvrrmH2cH5MXJvHMDdclKUB?= =?us-ascii?q?kIwYUTkhc7CcGIQUv8MLbxbiM8EcgDMT0t/3yyPUVPXsqrYVrUry6w6jMWGh?= =?us-ascii?q?z7LQdvIKL+HYuBx8iy3vq5rpvUZQgAjTGhYLR0eROxqwiZtsQfjYZ4bKgrzR?= =?us-ascii?q?6cqXpTcOMQzmRtdl8=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BJAgAd2R1f/5hdJa1gHQEBAQEJARI?= =?us-ascii?q?BBQUBQIE5BQELAYFRUQdvWC8shDSDRgONMJkGgUKBEQNVCwEBAQwBARgLCgI?= =?us-ascii?q?EAQGECEQCF4ILAiQ3Bg4CAwEBCwEBBQEBAQIBBgRthVwMhXICBAEBEBERDAE?= =?us-ascii?q?BLAwPAgEIGgImAgICJQsVEAIEARIUDoMEAYJLAy4BDqENAoE5iGF2gTKDAQE?= =?us-ascii?q?BBYJKglsYgg4DBoEOKgGCbINZhjcagUE/gREnDBCBT1AuPoJcAQGBKgESASE?= =?us-ascii?q?Xgn8zgi2PToMSkiuQYwqCXo8Qil4DHoJ7jnONdpIWnxoCBAIEBQIOAQEFgWk?= =?us-ascii?q?kZ3BwFTsqAYI+UBcCDY4eDBeDToUUhUJ0NwIGAQcBAQMJfI8gAQE?=
X-IronPort-AV: E=Sophos;i="5.75,399,1589241600"; d="scan'208";a="793782730"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 26 Jul 2020 19:33:20 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by rcdn-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 06QJXK2w022507 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 26 Jul 2020 19:33:20 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sun, 26 Jul 2020 14:33:20 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sun, 26 Jul 2020 15:33:19 -0400
Received: from NAM11-DM6-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Sun, 26 Jul 2020 15:33:19 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=TbjCDIT3de9rSeF8Zhicok7I5kLA7fCt8QWG3TO42JfdJNDmdLAARArLrQArAxhRiyU2iPTljmzFQFH2eoLkhVxwaPmfFG2ELMJ15fMq8usCuoV2fK+hLbth4OMoTs9xAL1QjxjkeVJLtGkzZgf6cXT/RsE9a9c8pc3Gp2zyvLRuebIuPZg+a5y0htioVmyFtYV0To0xv5fNDkq0ipDh93wWJin3D1eTFhbvkFrgmDc3UdhDRQgijvwQTkexGZK2mHSjrpy5ZrW0JqKgJc2G7skvDlII+XoT1Pz9Wcmt2hPY0jkXkUQuLLY8Id9D9EKE38+TZ55tE3zCkqHcgvc8CA==
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=AiOlYFqKzPDkXunlOquGmKDkA3JTE+WByXw2Bo8QzG0=; b=D03ABrsBNg5Fp42DsdqZ9tDlMIBd8krl2hPDehN7NlBj/iIplHWIciD/nOBTNZVUAozCgzY5D1EFuF2/HS6demUr+iBIxxlSwSLtR6xhWiDSVBf9QE9l875ghbdxzsaiU/IF+EObcCjHMOnQ0XdR/6vBA8h1ugdHpywRbtNOjMd44PzOb96VpUn9K1CgKU+RLqPGsE9j+gGbpgUYMS3UEftKsqQLzPC4RvB8zpHcHN9GScHFwBzP2U5Elnz0uj5lJbB7cawgtB6mC/hjYSFhez9jGewChAJ8Yq6Y6YJ9QW/ib6oz0T6hMSw/2u3U8HsalfO2owSsX+QW5MAdsJjNtg==
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=AiOlYFqKzPDkXunlOquGmKDkA3JTE+WByXw2Bo8QzG0=; b=Tz8MnVZ2oYOkc5xIzFNZnhtDd1nf+qsnTr9wuF0q6whxDOvIYAhhU1sXggY3rSnYE5FWh9qhJpgdZc7LhWAOfuSwjKfm/MkNKtA+nfHG/MZdPuiGZld4AQEhnia/WvSRiwK3G86jfzFV9Za1N0GWvaBROkIHYCDUxJmnVg3l0gQ=
Received: from DM5PR11MB1979.namprd11.prod.outlook.com (2603:10b6:3:10b::19) by DM6PR11MB3050.namprd11.prod.outlook.com (2603:10b6:5:71::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3216.23; Sun, 26 Jul 2020 19:33:18 +0000
Received: from DM5PR11MB1979.namprd11.prod.outlook.com ([fe80::791d:5c52:f954:f85c]) by DM5PR11MB1979.namprd11.prod.outlook.com ([fe80::791d:5c52:f954:f85c%10]) with mapi id 15.20.3216.031; Sun, 26 Jul 2020 19:33:18 +0000
From: "Francois Clad (fclad)" <fclad@cisco.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "spring@ietf.org" <spring@ietf.org>
Thread-Topic: [spring] General Proxy behavior in SR Service Programming
Thread-Index: AQHWYrCy1ltJGnyvQUun/MsmGCL66KkaY18A
Date: Sun, 26 Jul 2020 19:33:18 +0000
Message-ID: <AD76C305-5108-4C7C-9946-D9B001E86071@cisco.com>
References: <3c542370-c7dd-9ec2-8120-186f24b993b2@joelhalpern.com>
In-Reply-To: <3c542370-c7dd-9ec2-8120-186f24b993b2@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.39.20071300
authentication-results: joelhalpern.com; dkim=none (message not signed) header.d=none;joelhalpern.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [2a01:cb10:43:4400:65d5:2221:f9c5:145a]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f44b342e-fac8-4dac-e770-08d8319abfba
x-ms-traffictypediagnostic: DM6PR11MB3050:
x-microsoft-antispam-prvs: <DM6PR11MB30507F1BC1D8B09BB0788D9DAC750@DM6PR11MB3050.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: r2aWyHLdT4UIT/GJIOxep+uVTAyVZMNoMQAzUU+QeGQCp46yDAQgnoWZukB9FMLW4YMhDUowiJOGC2AjM5TpvOHHNpyV5F+e3DhbnCsk8U4Aw4+4USb+q9U2yU3XKcTNyY7HgqgH4k+CCmd4JM8coxBLi80TKzKMXYSVH/FFuvQTqsTG6HtMBYqQ9BVGjYufgZZVnIGpKuxtY8oRXbOwQteK0H38BeOA/WtYMsVrPbbLJJtfmTXKDS46QJJ8ptlJSnanIrMIEK3K8gApVUF4zXS4VgQ/RI5sYgE6xPRpbri9be4CSTIYNp2URS3SzpfDLYGSDN4Mg5n4ll0clEFuYU509r8/EBOnyGxTQT35qymtwoj+mkZN3XEhWtFa3ZZ7+gD4nnBJ9lXRL/iQNj0U8A==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM5PR11MB1979.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(39860400002)(346002)(136003)(396003)(376002)(366004)(8676002)(66476007)(66946007)(71200400001)(2616005)(86362001)(33656002)(2906002)(110136005)(83380400001)(8936002)(5660300002)(186003)(64756008)(66556008)(66446008)(316002)(36756003)(6506007)(91956017)(6486002)(478600001)(6512007)(76116006)(966005); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: 3fpFRkS43N7gc3vAvMo5eZcVaPWKXsb02MQRlfrQemYu5V33oVCg91kkaI/NewZcRYX8rs/vUAsHRe79ASCqLIX9XV1OhR6yZB9QqX9BZPYhJKfnLs3SILnItCcL7ilaPeqeBTjBQTc+xcrwi5chR40Jca5s8r+mzDIAODDzB8XBgrndcJabxJUe6zm/Ec+jXmZBrj3kiKAI1UfWQUNXTk6ilh+7epzFBBNnJMTndLsH5IIf/FttMUE6+eyh1PE3SNX/cl+K08e/v9qmb0sKo5lBEmqi8tVCW3uzTlueEOkeNKDbz9uDwNR0LqgR9wS74PgPiJD5xJlwh+KulOErAmYDRP3Z26me6Ae5tvRYqDG0whK9lY6wi3Rm1gOWXxoXPRSDbFQpjlHvSekWA25gsoP+weskADOC0oBPu1GdLO9Nu207E8CTOykHtxR+zExkh9Ejr+lVSHFr3GzoYnjDlujFqvsk1zyyvpuzMmCMpHjUUjb2Trxhv3T49axpRVT0DnYthxXclLFqiYrB+1bFwAB76CukGTU6yPSZ0kixZdE=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <42F77E5D57ECA2429E5B961D94FFF306@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM5PR11MB1979.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f44b342e-fac8-4dac-e770-08d8319abfba
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jul 2020 19:33:18.4117 (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: gx4OZI6fLLa58/zLWXleoLC0Y0TYEbUVu4LhY9BCIbHmZNP6DROUgB3pYZGt82RQ
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB3050
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: rcdn-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/r2SLux6kvt8SEw-k1O-skC0h9rA>
Subject: Re: [spring] General Proxy behavior in SR Service Programming
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jul 2020 19:33:24 -0000

Hi Joel,

Thank you for your email.

A proxy and its associated SF can be seen from the network as a single entity: a packet enters this entity from the network, gets processed by the SF, and exits towards the network. The packet modifications that occur between the entry and exit of this entity are compliant with existing standards.

Whatever happens between the proxy and SF is internal processing and invisible to the network. However, a network operator or controller needs some information about the proxy’s internal behavior to determine an appropriate SID-list through the SF and possibly configure the proxy.

Cheers,
Francois


On 25/07/2020 20:23, "spring on behalf of Joel M. Halpern" <spring-bounces@ietf.org on behalf of jmh@joelhalpern.com> wrote:

    <chair hat off for now;  This issue may, depending upon resolution, 
    become a chair issue, in which case, I will look at it through a 
    different lens.  Heck, I may even disagree with myself.>

    Let me start by saying that I understand and support what the draft is 
    trying to do.  While I like SFC, I am under no illusions that it is or 
    should be the only answer to service chaining / service programming.

    Further, I understand what the proxies are for.  They seem necessary. 
    To deploy this stuff, we have to be able to work with older equipment. 
    Proxies seem the best way to do so.

    The document is even clear that  proxy is a new kind of thing.  Good.

    In order to do its job, and as I read this document, the SR proxies (of 
    various kinds) violate the rules for MPLS processing, SRH processing, 
    and IPv6 processing at various points.  They have to.

    It seems to me that we need to accept this requirement, and state it 
    clearly.  Most likely, this would suggest that we will want some form of 
    signoff from the MPLS and 6man working groups that these violations, for 
    these specific reasons, are acceptable to the community.  Personally, I 
    would rather have the discussion soon, rather than pretending it is a 
    non-issue and having the discussion during IETF last call.

    Maybe I am misreading, and things are less conflicted.  That would be great.

    Yours,
    Joel

    <chair hat returning to wherever it belongs.>

    _______________________________________________
    spring mailing list
    spring@ietf.org
    https://www.ietf.org/mailman/listinfo/spring