Re: Fwd: [OPS-DIR] Opsdir early review of draft-ietf-rtgwg-segment-routing-ti-lfa-12
Ahmed Bashandy <abashandy.ietf@gmail.com> Tue, 16 January 2024 06:47 UTC
Return-Path: <abashandy.ietf@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FBB6C14F5EC; Mon, 15 Jan 2024 22:47:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j-mNXgNC7rQo; Mon, 15 Jan 2024 22:47:16 -0800 (PST)
Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com [IPv6:2607:f8b0:4864:20::32c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6B43C14EB17; Mon, 15 Jan 2024 22:47:10 -0800 (PST)
Received: by mail-ot1-x32c.google.com with SMTP id 46e09a7af769-6dec4b7b680so3110645a34.3; Mon, 15 Jan 2024 22:47:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705387630; x=1705992430; darn=ietf.org; h=in-reply-to:from:references:cc:to:content-language:subject :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=ZaeKUV5JEhKvAMRpQcGn/nhGqTc2YBfSVVoeXBRMEGg=; b=VxMCNRnwCx3jBLllNWjKd/bh/qvTPnwNBAELwsLDLQQJj+rAe3wK4sJRv358dRMeZ+ MP1roIkY68Eg3M3kKfZ/8vqegaxsbNQTHgyb4kiNLLgxZA0tqquwjh8dW1qbHDaZqdJo TWXdE2qwxxOAZO+Cr3nQIWTRJZthS9i0TpOzDeNIxIPVe8PsxThW6RlJztAPMBrBAsgc UBTOHRljukC3WgNJFLk94fbgVOyNsIN4Q+bOBqa3wkxK0AYMxqGlK+WroRC3h3Tl7htb PpIHZL0b4nmMo0iBJIBDx4rBaqJ2pNwPHZSW6SzhX/ueTqe4tNN0+wIdTa97j0tzWr7g t0mA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705387630; x=1705992430; h=in-reply-to:from:references:cc:to:content-language:subject :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=ZaeKUV5JEhKvAMRpQcGn/nhGqTc2YBfSVVoeXBRMEGg=; b=gCQYtwqVwDUPkPwbhYs8Ct7hLnF1OnUiaTb9ruAX61HsQURvKtC01jjBSOp0bIy8bG F6FC9hkNTSQuVycfjFC1gPqANIaRaRZxQ/sRrP9sL7Bzggz5BOa3TZ2EAa6INEMh1Z+c EvmaFvHERvOWnj77XzeDSpzvXPZOOV3aAwri/kZj7tbnCDUn5PIDGj7uTafiAS0sLWeo PqHdIvzUBuuMFrmO7WAnWjYwS7Lw5Z6YT6Ty1DkuVV5FGI4Ncdb6H52yL9+kCOMh+3PS DKoeujUXNJeIPNcAAjyF72slgqhdMJ1ximh7OQ2NXce+579mTHFP2ynGvA9cS+2tJDqa qGrQ==
X-Gm-Message-State: AOJu0YxVBh/Piq5Ex/gj3I4dtBwbCEHo9MOcvUpc2WqzBOccuA7FN4Fk 2hyk6zVRTrmlyfL1zvCd178=
X-Google-Smtp-Source: AGHT+IE6bfWEPmjJ5KjtR3dQovmlKINhO5UT3bTSgNFE2LKvg5rUYsLoB5nZgTlAT7bpd4COCHXm7w==
X-Received: by 2002:a05:6359:5e99:b0:172:cf9c:882a with SMTP id px25-20020a0563595e9900b00172cf9c882amr4045940rwb.32.1705387629534; Mon, 15 Jan 2024 22:47:09 -0800 (PST)
Received: from [192.168.50.246] (c-73-189-164-225.hsd1.ca.comcast.net. [73.189.164.225]) by smtp.gmail.com with ESMTPSA id c23-20020aa78817000000b006d095553f2asm8623434pfo.81.2024.01.15.22.47.06 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 15 Jan 2024 22:47:08 -0800 (PST)
Content-Type: multipart/alternative; boundary="------------QzdFkZp5oDWkHmOxyJ57eUSx"
Message-ID: <623a6d26-3c10-4252-ae09-17a9502aadef@gmail.com>
Date: Mon, 15 Jan 2024 22:47:05 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Fwd: [OPS-DIR] Opsdir early review of draft-ietf-rtgwg-segment-routing-ti-lfa-12
Content-Language: en-US
To: Gyan Mishra <hayabusagsm@gmail.com>
Cc: Alexander Vainshtein <Alexander.Vainshtein@rbbn.com>, Bruno Decraene <bruno.decraene@orange.com>, Jeff Tantsura <jefftant.ietf@gmail.com>, RTGWG <rtgwg@ietf.org>, Routing WG <rtgwg-chairs@ietf.org>, Stewart Bryant <stewart.bryant@gmail.com>, "Voyer, Daniel" <daniel.voyer@bell.ca>, Yingzhen Qu <yingzhen.ietf@gmail.com>, draft-ietf-rtgwg-segment-routing-ti-lfa@ietf.org
References: <170288281224.32101.11529769397624376875@ietfa.amsl.com> <CABNhwV0G3NfiqOSiRzk-AP53cVSWQOLka5bC7KGmvaNBq9M1Xw@mail.gmail.com> <725f0155-40ca-4935-b173-01626e75b728@gmail.com> <CABNhwV1aAD0xjytncUwmijbNWXvJ7jaFp1HuHnhDmrNNUCRjqw@mail.gmail.com>
From: Ahmed Bashandy <abashandy.ietf@gmail.com>
In-Reply-To: <CABNhwV1aAD0xjytncUwmijbNWXvJ7jaFp1HuHnhDmrNNUCRjqw@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/_VpGMrBLAZUr7Mq7V8zUtzgKmxU>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jan 2024 06:47:20 -0000
OK I'll make the change in the next few days and reply to this email with version 13 Ahmed On 1/15/24 8:12 PM, Gyan Mishra wrote: > > Yes that is correct. > > Thank you > > <http://www.verizon.com/> > > *Gyan Mishra* > > /Network Solutions A//rchitect / > > /Email gyan.s.mishra@verizon.com// > / > > /M 301 502-1347 > > / > > > > > On Mon, Jan 15, 2024 at 10:33 PM Ahmed Bashandy > <abashandy.ietf@gmail.com> wrote: > > Question regarding removal of references to > draft-bashandy-rtgwg-segment-routing-uloop. > > My understanding is that you are suggesting I remove the following > bullet from Section 2 > > * - Segment Routing may be used for prevention of such micro-loops > as described in [I-D.bashandy-rtgwg-segment-routing-uloop].* > > Is my understanding correct? > > Ahmed > > On 12/17/23 11:05 PM, Gyan Mishra wrote: >> Hi Yingzhen & Jeff >> >> I completed the updated OPSDIR Review of TO-LFA draft and changed >> status from “serious issues” to “Ready”. >> >> Thank you >> >> <http://www.verizon.com/> >> >> *Gyan Mishra* >> >> /Network Solutions A//rchitect / >> >> /Email gyan.s.mishra@verizon.com// >> / >> >> /M 301 502-1347 >> >> / >> >> >> >> >> ---------- Forwarded message --------- >> From: *Gyan Mishra via Datatracker* <noreply@ietf.org> >> Date: Mon, Dec 18, 2023 at 2:00 AM >> Subject: [OPS-DIR] Opsdir early review of >> draft-ietf-rtgwg-segment-routing-ti-lfa-12 >> To: <ops-dir@ietf.org> >> CC: <draft-ietf-rtgwg-segment-routing-ti-lfa.all@ietf.org>, >> <rtgwg@ietf.org> >> >> >> Reviewer: Gyan Mishra >> Review result: Ready >> >> I have reviewed version 12 and am updating my initial review of >> TI-LFA in >> August which this review. >> >> Summary: >> Based on revision 12 review, the draft is ready for publication. >> >> Review details: >> >> IETF 118 side meeting discussion summary: >> >> We had a very productive discussion during the side meeting, and >> the review >> comments and open issues have been addressed. >> >> Outcome of the discussion: >> It’s important for the draft to clarify that with ti-lfa, when >> IGP starts to >> reconverge, there is still a possibility for micro-loops. So >> customers should >> be advised to deploy some micro-loop protection mechanisms to >> prevent traffic >> loss. >> >> Action items for authors of the ti-lfa draft: >> • To include text from RFC7490 second paragraph of section 10 - done >> • To include the text summary in the email thread - done >> • Change the text in section 6.1 from node to link - done >> >> Next steps: >> After the draft is updated to address the open issues which was >> completed with >> version 12, Gyan Mishra will update the OPS Directorate review, >> and the RTGWG >> WG Chairs will start the WGLC of this draft. >> >> Draft updates from v11 to v12 below: >> >> When the network reconverges, micro-loops [RFC5715] can form due to >> transient inconsistencies in the forwarding tables of different >> routers. If it is determined that micro-loops are a significant >> issue in the deployment, then a suitable loop-free convergence >> method, such as one of those described in [RFC5715], [RFC6976], >> [RFC8333], or [I-D.bashandy-rtgwg-segment-routing-uloop] should be >> implemented. >> >> TI-LFA is a local operation applied by the PLR when it detects >> failure of one of its local links. As such, it does not affect: >> >> * Micro-loops that appear - or do not appear – as part of the >> distributed IGP convergence [RFC5715] on the paths to the >> destination that do not pass thru TI-LFA paths: >> >> - As explained in [RFC5714], such micro-loops may result >> in the >> traffic not reaching the PLR and therefore not following >> TI-LFA >> paths. >> >> - Segment Routing may be used for prevention of such >> micro-loops >> as described in [I-D.bashandy-rtgwg-segment-routing-uloop]. >> >> * Micro-loops that appear – or do not appear - when the >> failed link >> is repaired. >> >> TI-LFA paths are loop-free. What’s more, they follow the post- >> convergence paths, and, therefore, not subject to micro-loops >> due to >> difference in the IGP convergence times of the nodes thru >> which they >> pass. >> >> TI-LFA paths are applied from the moment the PLR detects >> failure of a >> local link and until IGP convergence at the PLR is completed. >> Therefore, early (relative to the other nodes) IGP convergence >> at the >> PLR and the consecutive ”early” release of TI-LFA paths may cause >> micro-loops, especially if these paths have been computed >> using the >> methods described in Section Section 6.2, Section 6.3, or >> Section 6.4 >> of the draft. One of the possible ways to prevent such >> micro-loops >> is local convergence delay ([RFC8333]). >> >> TI-LFA procedures are complementary to application of any >> micro-loop >> avoidance procedures in the case of link or node failure: >> >> * Link or node failure requires some urgent action to restore the >> traffic that passed thru the failed resource. TI-LFA paths are >> pre-computed and pre-installed and therefore suitable for >> urgent >> recovery >> >> * The paths used in the micro-loop avoidance procedures typically >> cannot be pre-computed. >> >> 6.1. FRR path using a direct neighbor >> >> When a direct neighbor is in P(S,X) and Q(D,x) and the link to >> that >> direct neighbor is on the post-convergence path, the outgoing >> interface is set to that neighbor and the repair segment list >> SHOULD >> be empty. >> >> This is comparable to a post-convergence LFA FRR repair. >> >> Major issues: >> None >> >> Minor issues: >> >> Stewart Bryant pick up something that was agreed but was not >> included in this >> summary: we agreed to remove the reference to draft-bashandy in >> order to make >> the discussion on uloop prevention technology neutral. >> >> So the TI-LFA draft even though it has loop preventing >> mechanisms that can >> possibly work independently of a separate uLoop avoidance >> mechanism, that there >> are cases as we both pointed out that uLoops can form, in those >> cases for >> further convergence time optimization a separate uLoop prevention >> mechanism >> maybe necessary. >> >> So in that case the current reference to the uLoop avoidance >> draft could apply. >> >> However, I do think the uLoop draft needs a lot of work >> particularly section 3 >> and is an I-D. >> >> So I agree we need to remove any references to the uLoop draft >> and stating that >> a separate from TI-LFAs uLoop prevention technology is >> necessary. The uLoop >> draft as it exists would be the appropriate draft to be >> referenced but >> unfortunately it’s not ready so I don’t think we should reference it. >> >> Nits: >> None >> >> >> _______________________________________________ >> OPS-DIR mailing list >> OPS-DIR@ietf.org >> https://www.ietf.org/mailman/listinfo/ops-dir >
- Opsdir early review of draft-ietf-rtgwg-segment-r… Gyan Mishra via Datatracker
- Fwd: [OPS-DIR] Opsdir early review of draft-ietf-… Gyan Mishra
- Re: [OPS-DIR] Opsdir early review of draft-ietf-r… Yingzhen Qu
- Re: [OPS-DIR] Opsdir early review of draft-ietf-r… Gyan Mishra
- Re: Fwd: [OPS-DIR] Opsdir early review of draft-i… Ahmed Bashandy
- Re: Fwd: [OPS-DIR] Opsdir early review of draft-i… Gyan Mishra
- Re: Fwd: [OPS-DIR] Opsdir early review of draft-i… Ahmed Bashandy
- Re: Fwd: [OPS-DIR] Opsdir early review of draft-i… Gyan Mishra
- Re: Fwd: [OPS-DIR] Opsdir early review of draft-i… Ahmed Bashandy