Re: [mpls] WGLC for draft-ietf-mpls-ri-rsvp-frr-02

Chandrasekar Ramachandran <> Mon, 29 January 2018 13:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6F0CF12EB84; Mon, 29 Jan 2018 05:44:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.71
X-Spam-Status: No, score=-0.71 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, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id zd0M1HJIwwqg; Mon, 29 Jan 2018 05:44:18 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3169012EBD3; Mon, 29 Jan 2018 05:40:23 -0800 (PST)
Received: from pps.filterd ( []) by ( with SMTP id w0TDdaSo015142; Mon, 29 Jan 2018 05:40:20 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=0PxRKH/1p+yqU89E8M0UdpkDs7lcvm+Ix1bqRADTmhI=; b=OCCORKG+6t5LwQTMov+DpoXjuEUZjrMX63uBhb465GCD0rHTF2hrzo0dpi6wSgAFHhor Tublgtpr8MwjLg+lZKF7xLwYESeaQzKc0Wy0MHBG3vh+JQZSDEaxy4costXagbkkHeu+ a17W92mz0xgOfmSfVzZDf3p0wltHWaPMY1cpqpKqwvFI+NNb96OluLr6ktku1JaiB0v7 ulZdT1ZI7e0En5rVMljsHeXTVTmWof3oS3KBwt2+TgiGU3GRJxqsEyp2XDlQGjz8z/1c J3XmFZdd2FP0Swly5aUrj0iu8EmOHZyK9PzyF9Hk/atHKBuZLBgK+6iOgTE9dPKsN9NS sg==
Received: from ( []) by with ESMTP id 2ft4mk804c-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 29 Jan 2018 05:40:19 -0800
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.464.6; Mon, 29 Jan 2018 13:40:15 +0000
Received: from ([]) by ([]) with mapi id 15.20.0464.008; Mon, 29 Jan 2018 13:40:15 +0000
From: Chandrasekar Ramachandran <>
To: Alexander Okonnikov <>, "Mike Taillon (mtaillon)" <>
CC: "" <>, "" <>
Thread-Topic: [mpls] WGLC for draft-ietf-mpls-ri-rsvp-frr-02
Thread-Index: AQHTlvBhHQVZ0k7cwEyJa+O5xdC0sKOK2rBQ
Date: Mon, 29 Jan 2018 13:40:15 +0000
Message-ID: <>
References: <FRXPR01MB040778B3FB1875A5130DF6B298110@FRXPR01MB0407.DEUPRD01.PROD.OUTLOOK.DE> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN3PR0501MB1331; 7:9xKpdL5I5/3X4McDa7Bob6seHvy7b3kumhoshe2WSrrK2OqzfqyZ7n/K2p7CWO0N3M5A19LPFbXoip36ck8VlPmAXPiKYO1/md7eiZusmfReXJ1zmhW/ZrRq548PGDCstRcsl+5Np3Id+4GpTMNDjWN5LRO51/eDhPt4n4DqeP8DdkV7Ltdlh3mZUKqZ3sPfFoFuXzbP2Pnrb+lHP7BpzDkYSZWJqvCao78pXO1WgEMBkUbVC314oMZ88V0DvmId
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 6cba0b35-7c9c-4b0b-7e76-08d5671dd479
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(48565401081)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:BN3PR0501MB1331;
x-ms-traffictypediagnostic: BN3PR0501MB1331:
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:(28532068793085)(10436049006162)(120809045254105)(260130700054247)(95692535739014)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(8121501046)(5005006)(93006095)(93001095)(3231101)(944501161)(3002001)(10201501046)(6055026)(6041288)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123558120)(20161123562045)(6072148)(201708071742011); SRVR:BN3PR0501MB1331; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0501MB1331;
x-forefront-prvs: 0567A15835
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(39380400002)(39860400002)(396003)(346002)(366004)(37854004)(189003)(199004)(77096007)(102836004)(39060400002)(966005)(2906002)(8676002)(8936002)(81156014)(81166006)(478600001)(316002)(4326008)(2950100002)(6246003)(14454004)(97736004)(6116002)(99286004)(54906003)(110136005)(3846002)(19609705001)(790700001)(5660300001)(66066001)(186003)(26005)(9686003)(6306002)(59450400001)(54896002)(55016002)(2900100001)(106356001)(53546011)(68736007)(7696005)(25786009)(6506007)(53936002)(236005)(86362001)(33656002)(7736002)(229853002)(606006)(3280700002)(3660700001)(76176011)(74316002)(6436002)(9326002)(105586002)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0501MB1331;; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None ( does not designate permitted sender hosts)
x-microsoft-antispam-message-info: Q6AuVsBtXaUeVRor+g9TOpon68dg/6veHX7kV+KD6Ot0o33hk27s1ffP7lv2jQMNvUT8oSvHPUJH/Whhu4RW7Q==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BN3PR0501MB137715A1FE30162695F8C5ACD9E50BN3PR0501MB1377_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 6cba0b35-7c9c-4b0b-7e76-08d5671dd479
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jan 2018 13:40:15.8768 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0501MB1331
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-29_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801290182
Archived-At: <>
Subject: Re: [mpls] WGLC for draft-ietf-mpls-ri-rsvp-frr-02
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 29 Jan 2018 13:44:21 -0000

Hi Alexander,
RI-RSVP-FRR specification does not remove the backup LSP signaling but only uses B-SFRR association to enable the PLR to signal availability of local protection to the corresponding Merge Point (MP). The MP does not carry B-SFRR association back to the PLR for the actual FRR summarization. RI-RSVP-FRR aims to remove the dependencies that facility FRR has on a short refresh interval. So, with these extensions the LSP states on the Merge Point can remain long enough to ensure that PLR is not time constrained to schedule backup LSP signaling immediately.

Your comment/question though is relevant to the actual FRR summarization (i.e. summary-frr draft) where the PLR does not have to send the entire backup LSP Path message to the MP after the failure.


From: mpls [] On Behalf Of Alexander Okonnikov
Sent: Saturday, January 27, 2018 3:25 AM
To: Mike Taillon (mtaillon) <>
Subject: Re: [mpls] WGLC for draft-ietf-mpls-ri-rsvp-frr-02


What about signaling of MTU, which in regular facility FRR is conveyed in ADSPEC within Path of backup LSP. Per my understanding with proposed solution this information is being lost. Maybe it could be done by signaling MTU in SUMMARY_FRR_BYPASS object and specifying procedure for MP regarding modifying ADSPEC objects of the protected LSPs.

Thank you.

26 янв. 2018 г., в 20:04, Mike Taillon (mtaillon) <<>> написал(а):

I have reviewed the latest version of this document and believe this is ready to progress to the next stage.
-Mike (as a contributor)

On Jan 10, 2018, at 9:56 AM,<> wrote:

Working Group,

This is to initiate a two week MPLS working group last call in on

Please send your comments to the mpls wg mailing list (<>).

Please note that there is already one IPR disclosed for the individual

All the authors and contributors have stated on the working group
mailing list that they are not aware of any other IPRs that relates to
this document.

As with any WGLC, working group participants are requested to read
the document and comment. If you feel that the document is ready
for publication, it is appropriate to respond to the WGLC with a short
and simple email indicating support.

This working group last call ends January 24th, 2018.



mpls mailing list<><>

mpls mailing list<>