[Teas] Representing explicit route objects and recorded route objects for fast-reroute protected and backup LSPs
Aidan Copeland <aidan.copeland@metaswitch.com> Thu, 29 June 2017 08:41 UTC
Return-Path: <aidan.copeland@metaswitch.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2115612EC05; Thu, 29 Jun 2017 01:41:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level:
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=metaswitch.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 dUXHDEuNmBhv; Thu, 29 Jun 2017 01:41:15 -0700 (PDT)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0125.outbound.protection.outlook.com [104.47.41.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0918127180; Thu, 29 Jun 2017 01:41:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metaswitch.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=eSEfi1B0JtRZS4c9xSr7H6PI8q/xJGf8kmq1a+6gBsc=; b=qrvfN8nOY0Rt/f+scHRAUjeoahcSnAOjeYDl1oJg1k7FSblrz4/peaUBocCOmb6s/ZQOrvC9HBJcM+zp0XydxQL2m/0TVQ8jFXzRzM7tDCtr9yzU+jB8SzDmxXTaOU0hDFeQDDPbcPmQTYIwqUEWZpxJUSFbRlyZuNVGvnxRrQo=
Received: from BL2PR02MB2066.namprd02.prod.outlook.com (10.167.96.150) by BL2PR02MB2065.namprd02.prod.outlook.com (10.167.96.149) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1199.15; Thu, 29 Jun 2017 08:41:10 +0000
Received: from BL2PR02MB2066.namprd02.prod.outlook.com ([fe80::44f4:72b2:a266:a7ee]) by BL2PR02MB2066.namprd02.prod.outlook.com ([fe80::44f4:72b2:a266:a7ee%13]) with mapi id 15.01.1199.019; Thu, 29 Jun 2017 08:41:10 +0000
From: Aidan Copeland <aidan.copeland@metaswitch.com>
To: "draft-ietf-teas-yang-rsvp-te@ietf.org" <draft-ietf-teas-yang-rsvp-te@ietf.org>
CC: "teas@ietf.org" <teas@ietf.org>
Thread-Topic: Representing explicit route objects and recorded route objects for fast-reroute protected and backup LSPs
Thread-Index: AdLwsxZZ5hwI/B/+RL+KKiQtdRPGGw==
Date: Thu, 29 Jun 2017 08:41:10 +0000
Message-ID: <BL2PR02MB206678F66CBF3B29EB1C5FBDE9D20@BL2PR02MB2066.namprd02.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=metaswitch.com;
x-originating-ip: [2620:104:4000:7064:d185:505f:add1:e39]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BL2PR02MB2065; 7:G0QBo06WRI/PmFI8T0GNAL6JHv5F62K2xYoFL2l5AmBpwrDk5EVxuXG9xkj0LLrzJFKOLpayC3u8HF7fkpj9e6SV8/Z+C6bSobpQrHe0XnqE8T+5CnKgWwRPMbkisnY4xTg0kGeynQQ0vTYHvjDHFRBWzDm7JAATgbKoA/GhCc4MUxeHCFuFGHzGkoD73KvHsyu7sxlnezZvJNAA3sV2/U7KTSoVtaE/JDztzldr1v5RKdJ5uo2seRdSXZE5/QHNyY6Kewkxa48uUIASMhOkJX/XlneIMrwnuiqzWbu01u/7j11C4r9Kl7VX1DrX7XJYK52TET37yGUhXj5p6NZHKWEwkRnR/Mg0gNp4CdUDrZJZC0Nj4vhRFVhPCfifkFZa6hgO0ogeGe48ctf4gcx3dMQmfKtNrVfdh0aYVu058DMNW+mYQpHy+tZIqfvIsc7pTBHlyGxG+vg33PsbcRjxLrlcVS5t1unAr7mWzeNfMYRGclrN8jS1zOaYU71gACqCQ1A7RlH23+QOQFAV3VA6Tm3En+TUKM7UPk6EVhx4Z068j9eZ+0XUUB1nqhqts2kWXBsueSIXUS/R1cNl5XRkFD/FPr9YwpA5rWnyv0DNhpEv2SgR5ofuIv5uDbCjFA/v45IxqhnYEbr/qtbjMHWDHJ8A72oWYUBkzPRhMZMQ4JjM0wCngy1apIGGJeSkAVcoyjqm9HHVv8boOG+LliKWNoZmCOjpQxxSE3/HeL/X+cA9X8rVgvCitTSj0XjCf6ykTJm2dt0qJu0/l0fG4XrM33KzfG/R74yLERlI9plmsb8=
x-ms-office365-filtering-correlation-id: f1c69ccb-49ab-48cf-9d00-08d4beca97da
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(201703131423075)(201703031133081)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:BL2PR02MB2065;
x-ms-traffictypediagnostic: BL2PR02MB2065:
x-microsoft-antispam-prvs: <BL2PR02MB2065717B082CCB89DB9A3E47E9D20@BL2PR02MB2065.namprd02.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(151999592597050)(133145235818549)(26388249023172)(236129657087228)(148574349560750)(21748063052155)(209349559609743);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(3002001)(93006095)(93001095)(10201501046)(100000703101)(100105400095)(6041248)(20161123560025)(20161123564025)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(20161123562025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BL2PR02MB2065; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BL2PR02MB2065;
x-forefront-prvs: 0353563E2B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39840400002)(39450400003)(39410400002)(39400400002)(39850400002)(33656002)(6506006)(450100002)(74316002)(9686003)(5250100002)(38730400002)(14454004)(2351001)(790700001)(8676002)(6116002)(8936002)(2900100001)(102836003)(6306002)(81166006)(5640700003)(3280700002)(55016002)(54896002)(478600001)(54356999)(99286003)(6916009)(4326008)(3660700001)(25786009)(50986999)(189998001)(110136004)(7736002)(2906002)(86362001)(53936002)(5630700001)(7696004)(5660300001)(6436002)(2501003); DIR:OUT; SFP:1102; SCL:1; SRVR:BL2PR02MB2065; H:BL2PR02MB2066.namprd02.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BL2PR02MB206678F66CBF3B29EB1C5FBDE9D20BL2PR02MB2066namp_"
MIME-Version: 1.0
X-OriginatorOrg: metaswitch.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jun 2017 08:41:10.4565 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9d9e56eb-f613-4ddb-b27b-bfcdf14b2cdb
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL2PR02MB2065
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/uzh3iSiCTtn8gKqkpnHSIFPPOSc>
Subject: [Teas] Representing explicit route objects and recorded route objects for fast-reroute protected and backup LSPs
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jun 2017 08:41:18 -0000
Authors, Draft draft-ietf-teas-yang-rsvp-te defines state lists within the scope of the LSP to report * the set of incoming explicit route hops * the set of outgoing explicit route hops * the set of incoming record route subobjects * the set of outgoing record route subobjects. I am interested in how the YANG might be used to report this information for an LSP using the one-to-one-backup method of providing Fast Reroute protection. When using this method, any LSP might be expected to have N downstream paths and M upstream paths, each with a different set of incoming/outgoing ER hops/RR subobjects. Is this something that the current version of the YANG is intended to support; or is it likely to support it in a future version? Do you consider that it would be suitable to introduce lists of upstream and downstream paths, each of which would report the ERO and RRO information, as well as potentially the bandwidth information, corresponding to that path? Thank you Aidan Copeland
- [Teas] Representing explicit route objects and re… Aidan Copeland