[Pce] Proposal for signaling ECMP or UCMP paths

"Mike Koldychev (mkoldych)" <mkoldych@cisco.com> Fri, 12 July 2019 21:02 UTC

Return-Path: <mkoldych@cisco.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DA07120167 for <pce@ietfa.amsl.com>; Fri, 12 Jul 2019 14:02:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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=JRePSKpi; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=EEuDjBaS
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 0pCya6osigIg for <pce@ietfa.amsl.com>; Fri, 12 Jul 2019 14:02:22 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 066D112006B for <pce@ietf.org>; Fri, 12 Jul 2019 14:02:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=628; q=dns/txt; s=iport; t=1562965341; x=1564174941; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=ZfXZ9t6vBcFb4yvFNc/9JNKHgAnIO1W8YibzSY3YIvA=; b=JRePSKpihL2g4HCZPj/i70hGQhGg1S4bvokf2vH3rW3hoCLBuW8hBKu+ faX0zL+5pw6B3i6DfL2zJO5LuG6/tFjbgdDmeCF+C8mZcQBafapqwXy7o ktRMqmDr4vVA6YyZnuHc6QMjjYqtO0FyqpA6x8RXytSf47KSP6y5mRIqi A=;
IronPort-PHdr: 9a23:Ja1RHhMjGaDvCQsnCJYl6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEu6w/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETBoZkYMTlg0kDtSCDBj+L/nuYz0xHOxJVURu+DewNk0GUMs=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DyCgAo9Chd/5ldJa1lHQIfBQeBTwKBQlADalUgBAsoh2MDjk5MmVuBLoEkA1QJAQEBDAEBJQgCAQGEQAKCViM0CQ4BAwEBBAEBAgEFbYU8AQuFTxQoBgEBOBEBPkImAQQbGoMBgWoDHQEOoFgCgTiIYIIjgnkBAQWBMgGDWhiCEgMGgTQBi14XgUA/gRFGgh6DTQIBgWKDOoImqmYJAoIZA4ZVjU6CHBCHJI43hCKJEodGkAcCBAIEBQIOAQEFgVA4gVhwFTuCbIYyilNygSmPOwEB
X-IronPort-AV: E=Sophos;i="5.63,483,1557187200"; d="scan'208";a="593217472"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 12 Jul 2019 21:02:18 +0000
Received: from XCH-RCD-015.cisco.com (xch-rcd-015.cisco.com [173.37.102.25]) by rcdn-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x6CL2Ixf007169 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <pce@ietf.org>; Fri, 12 Jul 2019 21:02:18 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-RCD-015.cisco.com (173.37.102.25) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 12 Jul 2019 16:02:18 -0500
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 12 Jul 2019 16:02:17 -0500
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 12 Jul 2019 17:02:17 -0400
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=ZfXZ9t6vBcFb4yvFNc/9JNKHgAnIO1W8YibzSY3YIvA=; b=EEuDjBaS1SpJd6GNntTCC/YgjPA+VBCg4bAETECZz/YPip2U7oWUsgfqZFWEzAuZZ+slbpwcnkdOnToanM+ouiUDejIiqNGouWrriTQc5neraLjVW4G9a92JRGxwD536ZOp3USc+GFXPFnY9NKh9W0kqZwf9YTBXWI/Leb69iiw=
Received: from BN6PR11MB0051.namprd11.prod.outlook.com (10.161.153.153) by BN6PR11MB3972.namprd11.prod.outlook.com (10.255.130.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2052.19; Fri, 12 Jul 2019 21:02:15 +0000
Received: from BN6PR11MB0051.namprd11.prod.outlook.com ([fe80::7972:d14b:4c60:adb2]) by BN6PR11MB0051.namprd11.prod.outlook.com ([fe80::7972:d14b:4c60:adb2%3]) with mapi id 15.20.2052.022; Fri, 12 Jul 2019 21:02:15 +0000
From: "Mike Koldychev (mkoldych)" <mkoldych@cisco.com>
To: "pce@ietf.org" <pce@ietf.org>
Thread-Topic: Proposal for signaling ECMP or UCMP paths
Thread-Index: AdU49K/vyO4W8EA5RLe2JmFfCByyTQ==
Date: Fri, 12 Jul 2019 21:02:15 +0000
Message-ID: <BN6PR11MB0051E72151F46F5690CEAE9AD3F20@BN6PR11MB0051.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mkoldych@cisco.com;
x-originating-ip: [2001:420:2840:1250:f9ef:bdfe:66ff:5a09]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 5d5c0aeb-fbd4-45f8-c6a5-08d7070c3816
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600148)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:BN6PR11MB3972;
x-ms-traffictypediagnostic: BN6PR11MB3972:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <BN6PR11MB3972F7A967FE1C888A9F7A06D3F20@BN6PR11MB3972.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 00963989E5
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(39860400002)(396003)(366004)(376002)(346002)(189003)(199004)(8936002)(256004)(2351001)(81156014)(1730700003)(8676002)(102836004)(186003)(86362001)(6506007)(33656002)(7736002)(305945005)(99286004)(486006)(7696005)(74316002)(46003)(2501003)(476003)(478600001)(53936002)(9686003)(6306002)(6436002)(55016002)(5640700003)(316002)(81166006)(5660300002)(25786009)(6916009)(76116006)(66446008)(66946007)(64756008)(66556008)(66476007)(2906002)(4744005)(14454004)(52536014)(6116002)(68736007)(71200400001)(966005)(71190400001); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR11MB3972; H:BN6PR11MB0051.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: p92Gsgri40N22m2t6swQbblQFgXtRLNIbLw9hmuL3yFJG6SUFZHL3dxoTH7QbmiSyaZcJkDUqghe1DAHD54y0paWFdS9ENvJpZ0MlrninkjUKUGHqOdsMq35ZYLDmgImfOhGp166mRIMPDwffsVL7c/SkLcuuX1vQo2HWrka378vxtqJjKrLa+qIMRRIvUP+47vhR/cqHOctFYfO6bsyGRpLkwLxOGaliM1UJ+4i7p1nRS4tC/4+4KyqnqOnOqaA90e8tR28Fd+zsvJOoGxLbC2v9E9oFfYWfoHWlQxgPrGq8VFF1r7XsiWLUIoPXxoYULPWLfdgJ5I7MyA2dBx/ZZP8OezjXifvEKqjQNCMxsz1oCKDgWPjjBj9FTAGiDnsDTbu98b3cYGrTmI7ezVtSjVdT3GCNRgyiEtnnarxb9Q=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 5d5c0aeb-fbd4-45f8-c6a5-08d7070c3816
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jul 2019 21:02:15.4135 (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: mkoldych@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR11MB3972
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.25, xch-rcd-015.cisco.com
X-Outbound-Node: rcdn-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/apAMFyp6NOba9LpjmfkBsWVt0dE>
Subject: [Pce] Proposal for signaling ECMP or UCMP paths
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jul 2019 21:02:25 -0000

Hi WG,

As per SPRING WG, SR Policy may contain multiple Candidate Paths and each Candidate Path may contain multiple Segment Lists. Existing SR standards in PCEP allow only a single ERO (one Segment List) for the SR Path in a stateful PCEP message. There is a need to signal multiple Segment Lists in PCEP for this as well as other load balancing use cases. 

See the link that describes this, as well as list possible ways to achieve this. Please provide your feedback on the list or during the WG session.

https://github.com/dhruvdhody-huawei/105/blob/master/multiple_ERO_jl03a.pdf

Thanks,
Mike.