Re: [mpls] RtgDir Review: draft-ietf-mpls-ri-rsvp-frr-05

Chandrasekar Ramachandran <csekar@juniper.net> Fri, 21 June 2019 09:14 UTC

Return-Path: <csekar@juniper.net>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC26A120098; Fri, 21 Jun 2019 02:14:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.709
X-Spam-Level:
X-Spam-Status: No, score=-2.709 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_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 nBCAB6MlejC4; Fri, 21 Jun 2019 02:14:28 -0700 (PDT)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DF6412006F; Fri, 21 Jun 2019 02:14:28 -0700 (PDT)
Received: from pps.filterd (m0108156.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x5L95FQF032546; Fri, 21 Jun 2019 02:14:25 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=PPS1017; bh=XIPcRH3Qht3tUuf/qKXY4IEBvFvmJJOWuxCoMCpAB+Q=; b=T11bEeMXzR5eJokDNSHKlWexATJGhB0U5mqFwE5Kmh63XAvG1wDxU4ktKEgGsB4w8+25 5m4V0XaArpE5w+/GZUKsi8DEeiWfvxbJMyB5asNtXOFKJIVe/lZbK1LUNfAfrfh0aBLV p3kb8V8u3y8iK5Ch2xK57rBtutz/BjnIc2IL/lXYnGlzQTCDo1GhQNq4xx2gPyGO9WMo 2rFAP3AWh34mwEeLn3k3X/oZEEWAZ+ONfVtvULeGxTY8AjN/o8DCSO76M4muK5NyQnNZ uFxf3Lwr/eZzwKSHCr6s0y52EODEUVj6FwvjIZLeld9BkoR/WhS/FhbRQA0TE+CiKAR7 mw==
Received: from nam02-bl2-obe.outbound.protection.outlook.com (mail-bl2nam02lp2057.outbound.protection.outlook.com [104.47.38.57]) by mx0a-00273201.pphosted.com with ESMTP id 2t8tvr84s8-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 21 Jun 2019 02:14:25 -0700
Received: from BYAPR05MB5477.namprd05.prod.outlook.com (20.177.185.202) by BYAPR05MB6662.namprd05.prod.outlook.com (20.178.235.92) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2008.13; Fri, 21 Jun 2019 09:14:21 +0000
Received: from BYAPR05MB5477.namprd05.prod.outlook.com ([fe80::d4fa:13a5:a614:a868]) by BYAPR05MB5477.namprd05.prod.outlook.com ([fe80::d4fa:13a5:a614:a868%4]) with mapi id 15.20.2008.007; Fri, 21 Jun 2019 09:14:21 +0000
From: Chandrasekar Ramachandran <csekar@juniper.net>
To: "julien.meuric@orange.com" <julien.meuric@orange.com>
CC: "rtg-ads@ietf.org" <rtg-ads@ietf.org>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "draft-ietf-mpls-ri-rsvp-frr.all@ietf.org" <draft-ietf-mpls-ri-rsvp-frr.all@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: RtgDir Review: draft-ietf-mpls-ri-rsvp-frr-05
Thread-Index: AQHVKA8RSFgR78pb30yoMR7ykQS37Kalztjg
Content-Class:
Date: Fri, 21 Jun 2019 09:14:21 +0000
Message-ID: <BYAPR05MB5477CD42582D01E9D0C314CCD9E70@BYAPR05MB5477.namprd05.prod.outlook.com>
References: <25527_1555000351_5CAF6C1F_25527_187_1_c344649c-bea5-5d0e-3b76-2bd28be6d226@orange.com> <BYAPR05MB547700FDE3B96DEF070438E6D9E40@BYAPR05MB5477.namprd05.prod.outlook.com> <2098_1561039664_5D0B9330_2098_160_1_84b25e23-a628-854e-fb5d-f9ffdcdb170e@orange.com> <BYAPR05MB54778F145B53DCC233032F48D9E40@BYAPR05MB5477.namprd05.prod.outlook.com> <30928_1561107317_5D0C9B75_30928_253_5_092a01d2-2c01-1f57-7b13-47a85b103048@orange.com>
In-Reply-To: <30928_1561107317_5D0C9B75_30928_253_5_092a01d2-2c01-1f57-7b13-47a85b103048@orange.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.2.0.14
dlp-reaction: no-action
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=True; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Owner=csekar@juniper.net; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2019-06-21T09:14:15.3067202Z; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Name=Juniper Business Use Only; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Application=Microsoft Azure Information Protection; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ActionId=b0cfe2c3-0ade-4a17-a451-76837378dab2; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Extended_MSFT_Method=Automatic
x-originating-ip: [116.197.184.12]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 62b1b16e-8bd7-466d-f51a-08d6f628d8d1
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:BYAPR05MB6662;
x-ms-traffictypediagnostic: BYAPR05MB6662:
x-microsoft-antispam-prvs: <BYAPR05MB6662DA27D2F595D26F4865C5D9E70@BYAPR05MB6662.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0075CB064E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(376002)(346002)(136003)(39860400002)(366004)(13464003)(37854004)(189003)(199004)(51914003)(53936002)(99286004)(6436002)(5024004)(256004)(7736002)(305945005)(3846002)(14444005)(6116002)(5640700003)(66066001)(9686003)(25786009)(4326008)(74316002)(2906002)(14454004)(478600001)(55016002)(8936002)(6916009)(33656002)(8676002)(229853002)(6246003)(81166006)(81156014)(316002)(52536014)(486006)(26005)(7696005)(2501003)(86362001)(446003)(11346002)(76176011)(5660300002)(102836004)(476003)(68736007)(53546011)(76116006)(54906003)(6506007)(73956011)(186003)(66946007)(66476007)(71200400001)(66556008)(64756008)(71190400001)(66446008)(2351001); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB6662; H:BYAPR05MB5477.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: Eb8bV+xHKDRy6zkiXykTpW7HxuhwFiCjj/JWURxyB1cdT9Deb0RFclRLRFc13s6z3NsZ7kU3lzJeQv/pGaf0O7x7FCRxOVzf+tx8PigQ8w//YWiBFYdD9JYkcO2tajTIaFXgUzFFVMEXOVBYiEn9e/kkBnz12+iwcokpxEMf3ALljD3essy1TQzpPUuxCM577HD5G0/kZd9Af5e3LzFQ28y6PAQmKYFuUVAam7Ce+xe9Vz5Wjamb4yrgJ8hRNJgDnZxUBY5chePxYwDHugOU7fzM1DJO+6X7YZJHVjLjflVEBnYZYbaHbzZjUiJ/xSWCtLC/ak2rI3W5PK0drR0j5tYp2dAquhFajMYEt/Kwu26jQ1/AEFJxxQ5OjRaXuenEAbFO6+EW1dr2dSNJ9Q2qgYpWvRixOtSgY/uZTYPTLO0=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 62b1b16e-8bd7-466d-f51a-08d6f628d8d1
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jun 2019 09:14:21.4568 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: csekar@juniper.net
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB6662
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-06-21_07:, , 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=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1906210077
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/EJLC206GVxOxtT9edpmIvAD6SuI>
Subject: Re: [mpls] RtgDir Review: draft-ietf-mpls-ri-rsvp-frr-05
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jun 2019 09:14:31 -0000

Hi Julien,


Juniper Business Use Only

> -----Original Message-----
> From: julien.meuric@orange.com <julien.meuric@orange.com>;
> Sent: Friday, June 21, 2019 2:25 PM
> To: Chandrasekar Ramachandran <csekar@juniper.net>;
> Cc: rtg-ads@ietf.org; rtg-dir@ietf.org; draft-ietf-mpls-ri-rsvp-frr.all@ietf.org;
> mpls@ietf.org
> Subject: Re: RtgDir Review: draft-ietf-mpls-ri-rsvp-frr-05
> 
> Hi Chandra,
> 
> Your response seems to summarize section 4.6.2.1. about the "downstream
> direction", which is fine. My comment below is about section 4.6.2.2.
> which describes the "upstream direction": how could an RSVP-TE message
> sent to a Phop be a Path instead of a Resv? Am I missing something?

[Chandra] Let me illustrate with an example LSP as shown below.

    A  -> B -> C -> D

If ingress A does not support the extensions defined in the draft and requests node protection for the LSP, then long refresh will not be enforced on the LSP segment A -> B -> C. In other words, Path messages from A to B, Path messages from B to C, Resv messages from B to A, and Resv messages from C to B, will not use long refresh interval. This behavior ensures that neither primary Path from B to C nor backup LSP Path from A to C during local repair would use long refresh. Hence, node C may opt to time out LSP state normally in case of B-C link failure without requiring any explicit state cleanup messages from node A or node B.

In general, if there is a non-compliant node along the path of an LSP and if the ingress node has requested node protection, then backward compatibility procedures will come into force on two hops upstream & two hops downstream of that non-compliant node.

Thanks,
Chandra.

> Cheers,
> 
> Julien
> 
> 
> On 20/06/2019 17:08, Chandrasekar Ramachandran wrote:
> > Hi Julien,
> > Please refer inline.
> >
> >
> > Juniper Internal
> >
> >> -----Original Message-----
> >> From: julien.meuric@orange.com <julien.meuric@orange.com>;
> >> Sent: Thursday, June 20, 2019 7:38 PM
> >>
> >> Hi Chandra,
> >>
> >> Thanks for the update. I've just taken a look at the diff: it looks
> >> fine, with an improved MUST/SHOULD ratio. I haven't checked all nits,
> >> but it seems you missed a key one in section 4.6.2.2., leaving a Path
> >> message when talking about upstream (see below).
> > [Chandra] The text "carried in the Path to" is intended because the
> expected outcome is not to apply long refresh in the two hop
> neighborhood. That is, if the Phop node (say node X) does not support the
> extensions, then two nodes downstream of node X must use backward
> compatible refresh interval. This will enable the NP-MP of node X to time
> out the path state normally when the refresh timeout expires.
> >
> > Thanks,
> > Chandra.
> >
> >> Cheers,
> >>
> >> Julien
> >>
> >>
> >> On 20/06/2019 15:42, Chandrasekar Ramachandran wrote:
> >>> [...]
> >>>
> >>>> -----Original Message-----
> >>>> From: julien.meuric@orange.com <julien.meuric@orange.com>;
> >>>> Sent: Thursday, April 11, 2019 10:03 PM
> >>>>
> >>>> - s/in TIME_VALUES object carried in PATH to default value/in the
> >>>> TIME_VALUES object carried in the *Resv* message to a default
> >>>> value/
> >>
> >>
> ______________________________________________________________
> >> ___________________________________________________________
> >>
> >> Ce message et ses pieces jointes peuvent contenir des informations
> >> confidentielles ou privilegiees et ne doivent donc pas etre diffuses,
> >> exploites ou copies sans autorisation. Si vous avez recu ce message
> >> par erreur, veuillez le signaler a l'expediteur et le detruire ainsi
> >> que les pieces jointes. Les messages electroniques etant susceptibles
> >> d'alteration, Orange decline toute responsabilite si ce message a ete
> altere, deforme ou falsifie. Merci.
> >>
> >> This message and its attachments may contain confidential or
> >> privileged information that may be protected by law; they should not
> >> be distributed, used or copied without authorisation.
> >> If you have received this email in error, please notify the sender
> >> and delete this message and its attachments.
> >> As emails may be altered, Orange is not liable for messages that have
> >> been modified, changed or falsified.
> >> Thank you.
> 
> 
> ______________________________________________________________
> ___________________________________________________________
> 
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites
> ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez
> le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les
> messages electroniques etant susceptibles d'alteration, Orange decline
> toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged
> information that may be protected by law; they should not be distributed,
> used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.