[Teas] Re: [mpls] Re: Call for adoption: draft-beeram-mpls-rsvp-sr-01 (Ends 2026-11-17)

"Barth, Colby" <jonathan.barth@hpe.com> Wed, 18 November 2026 15:35 UTC

Received: from mx0b-002e3701.pphosted.com (mx0b-002e3701.pphosted.com [148.163.143.35]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id AF24946; Wed, 18 Nov 2026 15:35:22 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=hpe.com header.s=pps0720 header.b=jDKL5KH0; spf=pass (mx.ietf.org: domain of jonathan.barth@hpe.com designates 148.163.143.35 as permitted sender) smtp.mailfrom=jonathan.barth@hpe.com; dmarc=pass (policy=reject) header.from=hpe.com; arc=pass ("microsoft.com:s=arcselector10001:i=1")
Received: from pps.filterd (m0148664.ppops.net [127.0.0.1]) by mx0b-002e3701.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 6AIFQwSo243050; Wed, 18 Nov 2026 15:35:21 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hpe.com; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to; s=pps0720; bh=BacpWdUNjtSfHRXRgD3qpZs19H u8cN/Bfp09TsxBUf0=; b=jDKL5KH03v0KMO7QShJ1jW8owwAovz8jaaUkToJMiL bULlUY+4VLDDOE/JgGCSxdQLeiJg2QdXK2rfdbVp0D3N1knpugyXC3WeF0Pv9Do+ 7pEgLaAD3Tas+aJQwsYRJDw/LQCMcJ4oHFsPY5Sd1I/ZIuoZ+StskmOnbXY/sDas 9xYLhYIz3puIOgfBDOV8rKHSD990yP4K5xM+rgKQbnNi4+kY2U1LI7qxWBQtss5G BgQ9p0JNFknFTvD6Ne83uipC7V71pft1ryUJESzx0fRIiZkB2oUjWmjJl8dMXFGO 7vi3aPUjqWynDQANhHMHY9gkbo5H+VDLh3UznWxBOOAw==
Received: from p1lg14881.it.hpe.com (p1lg14881.it.hpe.com [16.230.97.202]) by mx0b-002e3701.pphosted.com (PPS) with ESMTPS id 4j1eam0gjm-1 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Wed, 18 Nov 2026 15:35:21 +0000 (GMT)
Received: from p1wg14923.americas.hpqcorp.net (unknown [10.119.18.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by p1lg14881.it.hpe.com (Postfix) with ESMTPS id 817E5802B89; Wed, 18 Nov 2026 15:35:19 +0000 (UTC)
Received: from p1wg14927.americas.hpqcorp.net (10.119.18.117) by p1wg14923.americas.hpqcorp.net (10.119.18.111) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.43; Wed, 18 Nov 2026 03:35:19 -1200
Received: from p1wg14925.americas.hpqcorp.net (10.119.18.114) by p1wg14927.americas.hpqcorp.net (10.119.18.117) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.43; Wed, 18 Nov 2026 03:34:48 -1200
Received: from p1wg14919.americas.hpqcorp.net (16.230.19.122) by p1wg14925.americas.hpqcorp.net (10.119.18.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.43 via Frontend Transport; Wed, 18 Nov 2026 03:34:48 -1200
Received: from DM5PR08CU004.outbound.protection.outlook.com (192.58.206.38) by edge.it.hpe.com (16.230.19.122) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.43; Wed, 18 Nov 2026 03:34:45 -1200
ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=AjhADoAGTuWLYJ9HNxNRQWRYXK1tXI3UZw5Df7lLCEJW2Jgiwxox03gSS5Inoo9Jo3t3HmhGShgnakyDhqtdVKiuCgszzwMz2LjyPzK7f7yL3dA76Mw2fhc1eLX4wRNqKtCqfLvxK0hSzMVFVMN6tt5W2F+hAXlD5GIi7WwluS1g52IKbOD8uJ4Iw2AFhbWgDamxErzKWzeB81zrWLN0GTvW4XCOXzh5DrCjeesHcZ0qxZ+RC4sON1zAL2reG9AK9v5WWMALEchKokkAuxok4nahCCwa0SsIjyeiJ+DtjAJUWo24Kwyd2MVmwJ2A6bHQ8XAk//8bwGq9n16/7NiQng==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=BacpWdUNjtSfHRXRgD3qpZs19Hu8cN/Bfp09TsxBUf0=; b=cx/t8CTHXht0FlNt9pYc9yRJqwnLrJQEEI/zv2xYdzs2AM301LB+6l6nIR90XiLjtHLDR3qImlH5jpTRr1zPn7cZkLmUPerjJdazJBSNyRjpPszTTs34WmhKZdFMmYrFhkPFQ8c0YY8VovjLEmlhK5ZDFEqEnxd7IO5Zwe+7x9OSy9aaKGMuBhVDK8UPDFDa44pTEgNru6j3mu73+/tn2zoSHWk66fbk8QI9MHuO15QDzezGU8hW0uPmhc8FVK8Q/jjhRJg6j/hOUVMNKaQILZitHQAzhBWM4et5ZULkDvkbzf13rIE4/rVrNR9SY/arZ/vmmhrbW8ItTDXXmbr4EA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=hpe.com; dmarc=pass action=none header.from=hpe.com; dkim=pass header.d=hpe.com; arc=none
Received: from SJ2PR84MB3370.NAMPRD84.PROD.OUTLOOK.COM (2603:10b6:a03:58d::7) by DM4PR84MB1926.NAMPRD84.PROD.OUTLOOK.COM (2603:10b6:8:4d::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.21.615.14; Wed, 18 Nov 2026 15:34:42 +0000
Received: from SJ2PR84MB3370.NAMPRD84.PROD.OUTLOOK.COM ([fe80::b074:7eab:8af5:9835]) by SJ2PR84MB3370.NAMPRD84.PROD.OUTLOOK.COM ([fe80::b074:7eab:8af5:9835%5]) with mapi id 15.21.0615.009; Wed, 18 Nov 2026 15:34:42 +0000
From: "Barth, Colby" <jonathan.barth@hpe.com>
To: Robert Raszuk <rraszuk@gmail.com>, Tarek Saad <tsaad.net@gmail.com>
Thread-Topic: [mpls] Re: Call for adoption: draft-beeram-mpls-rsvp-sr-01 (Ends 2026-11-17)
Thread-Index: AQHdd1NMkT+5rwgFSEygQ6JoAAieHLcz7MTA
Date: Wed, 18 Nov 2026 15:34:41 +0000
Message-ID: <SJ2PR84MB3370B21BB0826A9DE4C0071A927A2@SJ2PR84MB3370.NAMPRD84.PROD.OUTLOOK.COM>
References: <179358330469.1013311.4077472205935423431@dt-datatracker-7dc874ff8f-sl5zv> <LV8P220MB1914664DC588F7968E9FFF31FC7A2@LV8P220MB1914.NAMP220.PROD.OUTLOOK.COM> <CA+b+ER=_WBfNGiJFXuRKqbTF4daFFhc+xKH-7L8RTKfwMoqt4A@mail.gmail.com>
In-Reply-To: <CA+b+ER=_WBfNGiJFXuRKqbTF4daFFhc+xKH-7L8RTKfwMoqt4A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-reactions: allow
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: SJ2PR84MB3370:EE_|DM4PR84MB1926:EE_
x-ms-office365-filtering-correlation-id: ea37fa40-8a01-49a2-939b-08df45897710
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230040|23010399003|366016|1800799024|376014|4022899009|261022113327099003|261021123027099003|38070700021|261021135927099003|261022075727099003|10067099003|5023799004|56012099006|4143699003|261026135527099003|261026140227099003|261021133027099003|261022115727099003|261028144727099003|261021130227099003|261022105027099003|261026130827099003|261021121427099003|261102124527099003|261102123227099003|261026121527099003|261009223027099003|22082099003|18002099003|6133799003|13003099007|8096899003|3023799007;
x-microsoft-antispam-message-info: +X+IqsMxvPSwBeRfTofW0JxY8jpOk3naB7nVCNs8PMDU7rx+iIu+uYccZJqrwHFprv9e512L/+xe8gLtJr9CPlLgkMOKJTilGkM+yz4hX1OENXky1TkgpNCp6ksjXIYA+cAxYginS70Er8jVHD/GD7WPKBB7vw2taf/XFt7S3Cn57oQ8ZtIa0fJo2PPswIVkNzZ/dPncnTbOoX9v9SeaKftSmed4dpTwcluTp6gEsG7aXZAn0PJBO+l0JqayqY4ndUQ0/4luks3XeGH+U3Py4wBYlVKyTKeskiX2HXOxPCGJKcOz2H63v+UNxqpvy36WdAot3jZZHGhDrPst4Qarad9NA2FEgdDMp3fi24SK15HSIGFWp0hjEzStCBVFRbPuR61aheKQybun9oncYeYzIkvb5Y1XTqQW7jWLs8d8jH5/DGVWdUUMILAV1BEtg14O/S9SCk5Ju+z/YC2jS7dZGBHfb8irmEAlZnJjYb1lOwz7nsBEQxP4KirRzKVGDU+30IK8mL3qce1IejL2xXc2yYZON5+g3Yw762JXow0muLH2WA86/AqNT4wraXUViELDwI/xd2w+HI815PEm1WfRXTNol8fE0t3GXl3LRUgcuwoaMjAfeyssPBdtT+NxSZKx6ZEkPdk2Yy6fTLEEQWNXX+fs34K/FRmbO3soccx3Ns8=
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:SJ2PR84MB3370.NAMPRD84.PROD.OUTLOOK.COM;PTR:;CAT:NONE;SFS:(13230040)(23010399003)(366016)(1800799024)(376014)(4022899009)(261022113327099003)(261021123027099003)(38070700021)(261021135927099003)(261022075727099003)(10067099003)(5023799004)(56012099006)(4143699003)(261026135527099003)(261026140227099003)(261021133027099003)(261022115727099003)(261028144727099003)(261021130227099003)(261022105027099003)(261026130827099003)(261021121427099003)(261102124527099003)(261102123227099003)(261026121527099003)(261009223027099003)(22082099003)(18002099003)(6133799003)(13003099007)(8096899003)(3023799007);DIR:OUT;SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: JD8UoZA3mpzo3z6T52jzZzf1egAHh1DtnZI7wEdRSq2HPoj5wDWVRD/rxwL+LpW/uuPHclp9m+Y3bxvaU55Wg4h/8G+26OQ8O71vs6zAOF8oOnk1zzcLQfoO21aI1nzvS0H/j7V5wJLZ3IxsJWpltMyX47UMAjRBwYFf+73IBN6/cJEck8yin2odujgHIjel31RdqimHPVPWVizDJ3CQa4jVF00/TWDuXN2gJIqDp9x4Oa9tWEXLpILQ8lrBBilrz0Os6oomt1sA14HBZPbISWoz2Pttcbff7hWbOGXOFgLerzpssAPw6ecLpnXREYGozmRxuWQ8iSMSWl40Q/xtih4AxsNMXMpqfauK6rs9CmgRZXLuYust/zTrVlxefik5sgrF2EVuuNQeTNROnUN0TZYS5gzaMDUhtZNhcweaKwLaohxvWrQBkRaO63SJyQKApbrmzFWqLVb3tu8ywYq3lBLfPCip11U+E7qGsF9ysa0Blrrbr5nJJoF5JkjYbQtKgrqRHzyKV9hLajZGog/8UaUA4pdPb+Zchmrj/G8smO/V8vYG1Mdpa3UUCM8hUhTKMTh57Glnjo1v9FIxgCguijAPkTK0Nem1CviYoRURNNkWA9gFaS37gWf+ejPYpUDunYKBhx++vNl0vWHintmlJTvmPBPuEc1ieNIKBNeVbispV6PH5B8bXb/BYpDaoisxXX713F+e7zmuE1hf8jJTGu/i7Gx87CPo8mxevbAubMDSDGl1eqIvzo4z4Zrkn3hACKgoQ8/JGo4OW8ltrnFvQ0H79XXYMJMD5uFO/ihnP+KDdGm7aG2KkcwOuQJLrxlQ9X6FFVFgCtMvhwwBjgi8PSGcGNouA58e+blcILcIauYSvJKP/JKxIKu3MYnVcQAOKM4uaVhPBkTEJXCaHDnfpJNeQl9SeCTDZqZUggfixcQ6WZqArSO9J0/O7vCABF9POSXbW9xWGfSVcTqrekMunF5IOG+EJVyfq3NWENhLOejZBuxbOiQXpT8z8ScWmt54yHkIeOHlDanuZH2MjGz2qZdP8D2Kubjf+wdiJ6nRAPGBL8rYJfuVisHuF5Bd/ULX1K5pGEAd36BKxRPAdUCrSpwCoDQpxIdSrqbTyAAa2wxXoPUqQH/6veonPHFX1+3E+7ma7j4xFWCQw83GUb+kv24HHcj8WXqclYTcGHLQs5XPU1nqZpuaQQTBEqaCoZKNTl2VLGctoMh20albwp/9HeMfc/HtKQVNfyxM4yOGZ6vaJ1j9Myartfqe+QPtE927I4AvnW1yCSNJ5wQ6d7kgkt2x2FCQeyYo+ExEFsp3IN6R8Y1YrqQ6n3jBFaEqc1Nz65gT4J8svDb0ouTneJtXtTGDIOsY4GTP8OtbqlejuyZPrs18G8vBk/DvkpN8k05tNkldhWwLpwJlbGE96KFzyAUln5ZBSgTZHg7Y2HBvsNqS4izypCDvD692T1dbXNWXRxxxje0qgZ362XUSFEllXSGbii+IbLsOaadE+0FpYuj7WwHhHuj5a84Iwxh0dVR0kkARB+BEWzf7n2+2uMyZdJNM4AvZVvKbCQzEx3PLua3yhnECNiWQiNUegkArtiywIMKa5U8UiN5OxfiFeb50oQJJDMQykfQLxe+C0Mg5se9/k1kCqk/f3Awu6Lplc8muyt7sM83dPPbICyEbi20EsDUhnqtzDa775gCgP2ReKI877kMcGTZJfKsdZDAVsd46lmBsj4O7RIh5OtHN3u5KMTpHUk4AvPzGbLfKYbiko+I=
Content-Type: multipart/alternative; boundary="_000_SJ2PR84MB3370B21BB0826A9DE4C0071A927A2SJ2PR84MB3370NAMP_"
MIME-Version: 1.0
X-Exchange-RoutingPolicyChecked: e2ylp4fYgiCmxPVHLz/O3/IFNViVphClcbxYpKyULFN6RQlYeMjTnWY/WBhEg3aXlq28ScT6tUrLjZ3P3QcLP9uMJqEFqtsEU3ALxeKZ06kaNFDLSeao6jNYxLa/egy7y4CEe9MkfHJqaz26d8FUDN/IC9lGZuhZV2WbeZmINVIWBFqBUCQWHNIzLmRH/jwEBLHazrHwYrFRcNcj6Gfzvr8Z5Tq+pQgveR6Pa1riny5KjtWt9B/vco2B3YVXhnZ0HYm2Ss2EMIpB9kwJC4idTDAndIBioyN+oPaqDU7CE6wuAiWgLDeyxdiiVjoALUnFlSuJ3i9FK+x8Dn9RrjXe7w==
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: SJ2PR84MB3370.NAMPRD84.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: ea37fa40-8a01-49a2-939b-08df45897710
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Nov 2026 15:34:41.9930 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 105b2061-b669-4b31-92ac-24d304d195dc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: jNEYTRt5AEIi/Biqx+d8ivT5Rv5xll77m4KDFQBSzKjIdeKPzbmZJb84wYegPcQqGl77y/PVI+UIMphtpDbnGw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM4PR84MB1926
X-OriginatorOrg: hpe.com
X-Proofpoint-GUID: nyq5jQNuzoeCqkhhVa1LIkruvSD-T9an
X-Authority-Analysis: v=2.4 cv=L++I0OT8 c=1 sm=1 tr=0 ts=6afdc5b9 cx=c_pps a=FAnPgvRYq/vnBSvlTDCQOQ==:117 a=FAnPgvRYq/vnBSvlTDCQOQ==:17 a=z/mQ4Ysz8XfWz/Q5cLBRGdckG28=:19 a=lCpzRmAYbLLaTzLvsPZ7Mbvzbb8=:19 a=xqWC_Br6kY4A:10 a=zJRp6_cAMcgA:10 a=VkNPw1HP01LnGYTKEx00:22 a=gQcMVamqm3wCPoSYhaRC:22 a=NCWKwCw8Xy9Og0ibBRsL:22 a=pGLkceISAAAA:8 a=48vgC7mUAAAA:8 a=W2MVTk-LEqp03VJCNXoA:9 a=lqcHg5cX4UMA:10 a=QEXdDO2ut3YA:10 a=dgiMH8c_Y3aV5ORYCjQA:9 a=E3ftpQZuYwzrfmOf:21 a=_W_S_7VecoQA:10
X-Proofpoint-ORIG-GUID: nyq5jQNuzoeCqkhhVa1LIkruvSD-T9an
X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYxMTE4MDA2MSBTYWx0ZWRfX1y9CLC69ewGW RyGicXGfS5ciV9KvzEWTlcKiEL8DwSvuxU0/s2fLpEs+k1vZvtXAmdOQuAc7yqw8bQXagDNkQ5d wxBCUDNe7M5B+XmkUbym4YbMB/cdSsc4EDs2e/b+TtzQlsMf5u4GoX9snfaqPHPva9LNA6sntXW Nukeb6n10UTQBNsMupxYzQPzTRC8p1KcqrWx3VxpdXKky2iMiWvu5Hl4JFOOlaKSvSjbvpoOvTX zEXmGOxaE5E2zYjAFMBcowzio8cy78RwIjOwpxDBIpl6yirdxh3su1D5gya5cimdsL1v0zHDE+A 0nrlPXG/PRzEHzPjKQPYEMkyJZ3IB01BVpN+SS1utFvFkJjwu3Y4IuzwZW5kMcHMtL+kSzURRrq il8v1rbmknIhiKzWqAtRPRi1r5jnUj0Ql9Fpceukd8CmSLlza6jqw4MBDClHSLtsSXGQ87RS5rZ JYJVdwDvmBipVYk333A==
X-Proofpoint-Spam-Info: AW1haW4tMjYxMTE4MDA2MSBTYWx0ZWRfX8kbyKaF02ovP VJBBlPZrgApzpft3ab/KW9+m5K+KBPw5gTMFFpY4HQ3UlbPQZzKpaae4ycycybLi+qS3vI4rGb5 3LFkFjCpNkvUE5L8FgREEv7JM6RROgs=
X-HPE-SCL: -1
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1176,Hydra:6.1.138,FMLib:17.12.100.49 definitions=2026-11-18_04,2026-11-16_01,2025-10-01_01
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 lowpriorityscore=0 bulkscore=0 phishscore=0 impostorscore=0 suspectscore=0 spamscore=0 priorityscore=1501 clxscore=1015 malwarescore=0 adultscore=0 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.22.0-2611040001 definitions=main-2611180061
X-Spamd-Bar: -----------------------------
X-Original-From: "Barth, Colby" <jonathan.barth@hpe.com>
Message-ID-Hash: 3HSLVIQJAWOLYFODYAVP2JC45LXSR4WS
X-Message-ID-Hash: 3HSLVIQJAWOLYFODYAVP2JC45LXSR4WS
X-MailFrom: forwardingalgorithm@dmarc.ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-teas.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "mpls@ietf.org" <mpls@ietf.org>, "draft-beeram-mpls-rsvp-sr@ietf.org" <draft-beeram-mpls-rsvp-sr@ietf.org>, "TEAS WG (teas@ietf.org)" <teas@ietf.org>, spring <spring@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, TEAS WG Chairs <teas-chairs@ietf.org>, spring Chairs <spring-chairs@ietf.org>
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Teas] Re: [mpls] Re: Call for adoption: draft-beeram-mpls-rsvp-sr-01 (Ends 2026-11-17)
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/X_gz0W8IwnbwS6RD7sBUdox_ylQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Owner: <mailto:teas-owner@ietf.org>
List-Post: <mailto:teas@ietf.org>
List-Subscribe: <mailto:teas-join@ietf.org>
List-Unsubscribe: <mailto:teas-leave@ietf.org>

Hi Robert,

I think we need to distinguish between general network engineering challenges and issues specific to the solution proposed in this draft.

The points you raise regarding non-TE traffic, multicast replication, transient loops, and failure or congestion notification are not unique to RSVP-TE. They apply, in varying degrees, to just about any network architecture, including Segment Routing.

Some specific observations:

  *   RSVP-TE bandwidth reservations obviously do not require that 100% of network traffic be carried in TE tunnels. Coexistence questions have already been raised but importantly accounting for non-TE traffic and other consumers of network resources is a well-understood engineering consideration. It does not invalidate the benefits of distributed bandwidth management and admission control.

  *   Multicast replication, transient forwarding loops, and microloops are not RSVP-TE-specific problems. These are general networking challenges that exist regardless of the TE technology being used.

  *   RSVP-TE has well-established mechanisms for failure detection, local protection, and resource notification. In particular, RSVP-TE FRR provides local protection without waiting for end-to-end signaling. Suggesting that RSVP-TE relies on RESV_TEAR for fast failure recovery overlooks mechanisms that have been widely deployed for decades.

I take issue with the characterization of RSVP-TE as "legacy TE style networking." RSVP-TE provides capabilities that remain valuable in modern networks, particularly distributed bandwidth management, admission control, and preemption. The fact that these mechanisms have been around for some time doesn't make them obsolete.

More importantly, I don't see how these concerns relate to the proposal in this draft. The proposal is actually quite simple. It doesn't introduce a new TE architecture or change how RSVP-TE bandwidth management works. It simply allows existing RSVP-TE signaling and control-plane capabilities to be used with an SR-MPLS forwarding plane.

The relevant question for this adoption call is whether there is value in applying RSVP-TE control-plane capabilities while also using SR-MPLS forwarding. As a co-author, I obviously believe there is.

-- Colby


________________________________
From: Robert Raszuk <rraszuk@gmail.com>
Date: Wednesday, November 18, 2026 at 3:52 AM
To: Tarek Saad <tsaad.net@gmail.com>
Cc: mpls@ietf.org <mpls@ietf.org>; draft-beeram-mpls-rsvp-sr@ietf.org <draft-beeram-mpls-rsvp-sr@ietf.org>; TEAS WG (teas@ietf.org) <teas@ietf.org>; spring <spring@ietf.org>; mpls-chairs@ietf.org <mpls-chairs@ietf.org>; TEAS WG Chairs <teas-chairs@ietf.org>; spring Chairs <spring-chairs@ietf.org>
Subject: Re: [mpls] Re: Call for adoption: draft-beeram-mpls-rsvp-sr-01 (Ends 2026-11-17)

Dear Tarek,

Please kindly augment the section "Architectural Objections and Concerns Key Opponents:" with some of concerns I raised:

* Any TE BW allocation in the control plane work well when network supports 100% of TE traffic. When there is no TE traffic in the network all reservations made fall back to normal QoS - and there is not a good universal mapping between queue depths and interface bandwidth

* Any network which supports multicast or flexicast where there is in network replication does not fit the end to end TE unicast model and congestion is likely to occur. Note that traffic carried by those technologies may be more important than unicast transit traffic.

* Any loops and microloops formed in the network (even transient) may very effectively jeopardize any end to end TE efforts.

* RSVP-TE does not have any built in fast mechanisms to notify endpoints about link failures (RSVP RESV_TEAR is too slow) or congestion nor can notice any forms of brownouts.

Yes those are high level observations not introduced by draft-beeram-mpls-rsvp-sr alone, but IMO are important points to consider when making judgement about progressing with more legacy TE style of networking.

Kind regards,
Robert


On Wed, Nov 18, 2026 at 7:02 AM Tarek Saad <tsaad.net@gmail.com<mailto:tsaad.net@gmail.com>> wrote:
Thanks to everyone who participated in the adoption poll for draft-beeram-mpls-rsvp-sr. I am including a summary of the discussion and a proposal for the next steps below.

Document: draft-beeram-mpls-rsvp-sr
Engagement: High (approx. 59 messages from 23 unique participants)
WGs Involved: MPLS, SPRING, TEAS
Current Version: -02 (posted 2026-11-15)


  1.
Summary of Support from Key Proponents:
     *
Provides a practical, rational method for bandwidth reservation in SR-MPLS networks.
     *
Leverages existing, mature RSVP-TE control planes while using the SR-MPLS data plane (reusing Adj-SIDs).
     *
Provides distributed admission control without requiring a full stateful PCE for all scenarios.
  2.
Architectural Objections and Concerns Key Opponents:
     *
State Conflict: Contention that the draft introduces transit state into SR, which critics argue violates RFC 8402 and RFC 8426 (stateless transit nodes).
     *
Coexistence: Questions on how RSVP-TE signaled Adj-SIDs coexist with IGP-distributed Adj-SIDs on the same forwarding plane.
     *
Value Proposition: Concerns that retrofitting RSVP-TE is a tactical fix that may distract from long-term controller-based/PCE solutions.
  3.
Proposed Joint Interim Meeting (MPLS, SPRING, TEAS) Duration: 3 Hours Objective: Resolve foundational architectural questions before proceeding with adoption or determining WG homes.

To resolve the impasse, the MPLS chairs propose a joint interim meeting between MPLS, SPRING, and TEAS (the date and time will be announced later).

  *
Objective: Resolve foundational architectural questions before proceeding with adoption or determining WG homes.
  *
Agenda Items:
     *
Scope: What are we trying to do?
     *
Reservation Locality: Where are the reservations made (transit, ingress, or central)?
     *
Strict Hops: Does bandwidth reservation only make sense for strict hops, regardless of reservation type (central or distributed)?
     *
Signaling Support: Is there broad support for a signaling plane solution for distributed reservation?
     *
Protocol Evolution: Does it make sense to build on an existing signaling protocol (like RSVP-TE)?
     *
Unified Solution: Should there be just one solution for both MPLS-SR and SRv6?
     *   Architecture: What should the high-level solution look like?


Regards,
Tarek (MPLS WG chair)

From: Tarek Saad via Datatracker <noreply@ietf.org<mailto:noreply@ietf.org>>
Date: Sunday, November 1, 2026 at 5:35 PM
To: mpls@ietf.org<mailto:mpls@ietf.org> <mpls@ietf.org<mailto:mpls@ietf.org>>; mpls-chairs@ietf.org<mailto:mpls-chairs@ietf.org> <mpls-chairs@ietf.org<mailto:mpls-chairs@ietf.org>>; draft-beeram-mpls-rsvp-sr@ietf.org<mailto:draft-beeram-mpls-rsvp-sr@ietf.org> <draft-beeram-mpls-rsvp-sr@ietf.org<mailto:draft-beeram-mpls-rsvp-sr@ietf.org>>
Subject: Call for adoption: draft-beeram-mpls-rsvp-sr-01 (Ends 2026-11-17)

This message starts a mpls WG Call for Adoption of:
draft-beeram-mpls-rsvp-sr-01

This Working Group Call for Adoption ends on 2026-11-17

Abstract:
   RFC 8577 introduced the concept of signaling RSVP-TE tunnels on a
   shared MPLS forwarding plane using preinstalled "TE link labels".
   Those labels are functionally equivalent to Segment Routing (SR)
   Adjacency Segment Identifiers (Adj-SIDs) but are allocated and
   distributed solely via RSVP-TE signaling.

   This document extends RFC 8577 so that RSVP-TE tunnels can use
   Segment Routing over MPLS (SR-MPLS) Adj-SIDs, as specified in RFC
   8402 and RFC 8660, in place of TE link labels.  It restricts scope to
   Adj-SIDs attached to a single unidirectional adjacency and defines
   the signaling procedures and protocol extensions required to couple
   the RSVP-TE control plane with the SR-MPLS data plane.

Please reply to this message and indicate whether or not you support adoption
of this Internet-Draft by the mpls WG. Comments to explain your preference
are greatly appreciated. Please reply to all recipients of this message and
include this message in your response.

Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [2].
Appropriate IPR disclosures required for full conformance with the provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].

Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp78/__;!!NpxR!mC9SN0ss_tiv7hXAGw7R194fohBPEbeyKuN0NEa22sINUYwMXrptG2FM9p8-osqua02u7D56vTdf3Ie5$>
[2] https://datatracker.ietf.org/doc/bcp79/<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp79/__;!!NpxR!mC9SN0ss_tiv7hXAGw7R194fohBPEbeyKuN0NEa22sINUYwMXrptG2FM9p8-osqua02u7D56vX6AiIfc$>
[3] https://datatracker.ietf.org/doc/rfc6701/<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/rfc6701/__;!!NpxR!mC9SN0ss_tiv7hXAGw7R194fohBPEbeyKuN0NEa22sINUYwMXrptG2FM9p8-osqua02u7D56vXTS7R9t$>

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-beeram-mpls-rsvp-sr/<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-beeram-mpls-rsvp-sr/__;!!NpxR!mC9SN0ss_tiv7hXAGw7R194fohBPEbeyKuN0NEa22sINUYwMXrptG2FM9p8-osqua02u7D56vb7mTgr4$>

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-beeram-mpls-rsvp-sr-01<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-beeram-mpls-rsvp-sr-01__;!!NpxR!mC9SN0ss_tiv7hXAGw7R194fohBPEbeyKuN0NEa22sINUYwMXrptG2FM9p8-osqua02u7D56vTlnWSPC$>

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-beeram-mpls-rsvp-sr-01<https://urldefense.com/v3/__https://author-tools.ietf.org/iddiff?url2=draft-beeram-mpls-rsvp-sr-01__;!!NpxR!mC9SN0ss_tiv7hXAGw7R194fohBPEbeyKuN0NEa22sINUYwMXrptG2FM9p8-osqua02u7D56vXLK1TRv$>
_______________________________________________
mpls mailing list -- mpls@ietf.org<mailto:mpls@ietf.org>
To unsubscribe send an email to mpls-leave@ietf.org<mailto:mpls-leave@ietf.org>