Re: [mpls] [Technical Errata Reported] RFC4090 (4203)
Yakov Rekhter <yakov@juniper.net> Thu, 18 December 2014 02:12 UTC
Return-Path: <yakov@juniper.net>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD98B1A0021 for <mpls@ietfa.amsl.com>; Wed, 17 Dec 2014 18:12:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.302
X-Spam-Level:
X-Spam-Status: No, score=-1.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_25=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
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 QMvaXwmpDpVM for <mpls@ietfa.amsl.com>; Wed, 17 Dec 2014 18:12:04 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0779.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::779]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30EA01A007C for <mpls@ietf.org>; Wed, 17 Dec 2014 18:12:04 -0800 (PST)
Received: from BY2PR05CA040.namprd05.prod.outlook.com (10.141.250.30) by DM2PR05MB445.namprd05.prod.outlook.com (10.141.104.154) with Microsoft SMTP Server (TLS) id 15.1.31.17; Thu, 18 Dec 2014 02:11:40 +0000
Received: from BN1BFFO11FD024.protection.gbl (2a01:111:f400:7c10::1:173) by BY2PR05CA040.outlook.office365.com (2a01:111:e400:2c5f::30) with Microsoft SMTP Server (TLS) id 15.1.36.23 via Frontend Transport; Thu, 18 Dec 2014 02:11:40 +0000
Received: from P-EMF02-SAC.jnpr.net (66.129.239.16) by BN1BFFO11FD024.mail.protection.outlook.com (10.58.144.87) with Microsoft SMTP Server (TLS) id 15.1.26.17 via Frontend Transport; Thu, 18 Dec 2014 02:11:39 +0000
Received: from magenta.juniper.net (172.17.27.123) by P-EMF02-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Wed, 17 Dec 2014 18:11:38 -0800
Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id sBI2BBW53068; Wed, 17 Dec 2014 18:11:11 -0800 (PST) (envelope-from yakov@juniper.net)
Message-ID: <201412180211.sBI2BBW53068@magenta.juniper.net>
To: Alia Atlas <akatlas@gmail.com>
In-Reply-To: <CAG4d1rciohjaMVmqkER=BL7EsXwMu5B4jQtTdRH=PS1NeK7VVA@mail.gmail.com>
References: <20141217200749.EAB02181CD8@rfc-editor.org> <CAG4d1rcHf7bv7tWYpj9uvtPJ8tPu-JzbXpQ2A8TAA7prQzcNMA@mail.gmail.com> <201412172105.sBHL52u19645@magenta.juniper.net> <CAG4d1reBGUoaihvOKsfz7XHzYymoB6AUXkUL=avfiwk4j5aszA@mail.gmail.com> <201412172141.sBHLfqu40272@magenta.juniper.net> <CAG4d1rciohjaMVmqkER=BL7EsXwMu5B4jQtTdRH=PS1NeK7VVA@mail.gmail.com>
X-MH-In-Reply-To: Alia Atlas <akatlas@gmail.com> message dated "Wed, 17 Dec 2014 16:46:25 -0500."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <64323.1418868671.1@juniper.net>
Date: Wed, 17 Dec 2014 18:11:11 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-EOPAttributedMessage: 0
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.16 as permitted sender)
Authentication-Results: spf=softfail (sender IP is 66.129.239.16) smtp.mailfrom=yakov@juniper.net;
X-Forefront-Antispam-Report: CIP:66.129.239.16; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(377454003)(164054003)(199003)(37854004)(24454002)(51704005)(189002)(106466001)(23726002)(50466002)(19580405001)(120916001)(107046002)(19580395003)(21056001)(105596002)(76176999)(2950100001)(575784001)(92566001)(6806004)(86362001)(512874002)(62966003)(97736003)(77156002)(15974865002)(15188155005)(110136001)(19617315012)(46102003)(87936001)(47776003)(16799955002)(1411001)(97756001)(4396001)(16796002)(93886004)(16601075003)(99396003)(84676001)(81156004)(15975445007)(77096005)(54356999)(69596002)(64706001)(15395725005)(50986999)(31966008)(20776003)(46406003)(68736005)(579004)(559001)(299355004); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR05MB445; H:P-EMF02-SAC.jnpr.net; FPR:; SPF:SoftFail; MLV:sfv; PTR:InfoDomainNonexistent; A:1; MX:1; LANG:en;
X-Microsoft-Antispam: UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR05MB445;
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004); SRVR:DM2PR05MB445;
X-Forefront-PRVS: 042957ACD7
X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:DM2PR05MB445;
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/mpls/g-zjgQI7JleCCxErl_GnXADyoTM
Cc: "mpls@ietf.org" <mpls@ietf.org>, Ross Callon <rcallon@juniper.net>
Subject: Re: [mpls] [Technical Errata Reported] RFC4090 (4203)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 18 Dec 2014 02:12:14 -0000
Alia, > > Alia, > > > > > Yakov, > > > > > > On Wed, Dec 17, 2014 at 4:05 PM, Yakov Rekhter <yakov@juniper.net> > > wrote: > > > > > > > Alia, > > > > > > > > > Hi Yakov, > > > > > > > > > > Could you clarify your point for this errata? In RFC 4090, in the > > > > > terminology it says: > > > > > "Backup Path: The LSP that is responsible for backing up one > > > > > protected LSP. A backup path refers to > > > > > either a detour LSP or a backup tunnel. > > > > > > > > > > Backup Tunnel: The LSP that is used to backup up one of the many > > > > > LSPs in many-to-one backup." > > > > > > > > In the terminology it also says: > > > > > > > > "Bypass Tunnel: An LSP that is used to protect a set of LSPs > > > > passing over a common facility." > > > > > > > > My point is that (unless the term "bypass tunnel" means the same > > > > as "backup path" or "backup tunnel") in many-to-one backup > > > > the "local protection available" flag for a given protected LSP > > > > MUST be set when the PLR has a *bypass* tunnel for that LSP. > > > > > > > > > > Ah - ok. A backup path that uses a bypass tunnel is not just the bypass > > > tunnel itself. > > > > Correct. > > > > > There's the state associated for the protected LSP that > > > also needs to be created and installed. In more concrete terms, this > > > is installing an out-segment with the appropriate label for the protected > > > LSP to be understood by the merge point as > > > well as an outer label for the bypass LSP. > > > > > > So, the text refers to a backup path instead of a bypass tunnel because > > > having the bypass tunnel isn't quite sufficient. > > > Does that make sense to you? > > > > The current text is incorrect. This is because a PLR may signal a > > backup path at the time of failure. Yet, one should not wait for > > the failure to set the "local protection available" flag. The PLR > > should set this flag as soon as it has a *bypass* tunnel. > > The backup path is created by the PLR before the failure and thus, before > the associated signaling. Once the PLR has done the work to create > a backup path using an existing bypass tunnel - which is internal > work - then the PLR should set the "local protection available" flag. Perhaps we should step back and ask whether the quote from section 6: Whenever the PLR has a backup path available, the PLR MUST set the "local protection available" flag. talks about forwarding state or control plane state. Is there any text in rfc4090 that answers this question ? Yakov. > > Alia > > > > > Yakov. > > > > > > > > Regards, > > > Alia > > > > > > > > > > Yakov. > > > > > > > > > Thanks, > > > > > Alia > > > > > > > > > > On Wed, Dec 17, 2014 at 3:07 PM, RFC Errata System < > > > > > rfc-editor@rfc-editor.org> wrote: > > > > > > > > > > > The following errata report has been submitted for RFC4090, > > > > > > "Fast Reroute Extensions to RSVP-TE for LSP Tunnels". > > > > > > > > > > > > -------------------------------------- > > > > > > You may review the report below and at: > > > > > > http://www.rfc-editor.org/errata_search.php?rfc=4090&eid=4203 > > > > > > > > > > > > -------------------------------------- > > > > > > Type: Technical > > > > > > Reported by: Yakov Rekhter <yakov@juniper.net> > > > > > > > > > > > > Section: 6 > > > > > > > > > > > > Original Text > > > > > > ------------- > > > > > > Whenever the PLR has a backup path available, the PLR MUST set > > > > > > the "local protection available" flag. > > > > > > > > > > > > > > > > > > Corrected Text > > > > > > -------------- > > > > > > Whenever the PLR has a one-to-one backup LSP or bypass tunnel > > > > > > available, the PLR MUST set the "local protection available" flag. > > > > > > > > > > > > > > > > > > Notes > > > > > > ----- > > > > > > In the case of facility-based FRR the PLR must set the "local > > > > protection > > > > > > available" flag if it has the bypass tunnel available. > > > > > > > > > > > > Instructions: > > > > > > ------------- > > > > > > This erratum is currently posted as "Reported". If necessary, > > please > > > > > > use "Reply All" to discuss whether it should be verified or > > > > > > rejected. When a decision is reached, the verifying party (IESG) > > > > > > can log in to change the status and edit the report, if necessary. > > > > > > > > > > > > -------------------------------------- > > > > > > RFC4090 (draft-ietf-mpls-rsvp-lsp-fastreroute-07) > > > > > > -------------------------------------- > > > > > > Title : Fast Reroute Extensions to RSVP-TE for LSP > > > > Tunnels > > > > > > Publication Date : May 2005 > > > > > > Author(s) : P. Pan, Ed., G. Swallow, Ed., A. Atlas, Ed. > > > > > > Category : PROPOSED STANDARD > > > > > > Source : Multiprotocol Label Switching > > > > > > Area : Routing > > > > > > Stream : IETF > > > > > > Verifying Party : IESG > > > > > > > > > > > > > > > > > > > > > > --001a11397a2c9bda6e050a6f31ae > > > > > Content-Type: text/html; charset="UTF-8" > > > > > Content-Transfer-Encoding: quoted-printable > > > > > > > > > > <div dir=3D"ltr">Hi Yakov,<br><br>Could you clarify your point for > > this > > > > err= > > > > > ata?=C2=A0 In RFC 4090, in the terminology it says:<br>" Backup > > > > Path: = > > > > > The LSP that is responsible for backing up one<br>=C2=A0 =C2=A0 > > =C2=A0 > > > > =C2= > > > > > =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0protected > > > > LSP.= > > > > > =C2=A0 A backup path refers to either a detour LSP<br>=C2=A0 =C2=A0 > > > > =C2=A0 = > > > > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0or a > > > > backup t= > > > > > unnel.<br><br>=C2=A0 Backup Tunnel: The LSP that is used to backup up > > > > one o= > > > > > f the many<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 > > > > =C2= > > > > > =A0LSPs in many-to-one > > > > backup."<div><br></div><div>Thanks,</div><div>A= > > > > > lia</div></div><div class=3D"gmail_extra"><br><div > > > > class=3D"gmail_quote">On= > > > > > Wed, Dec 17, 2014 at 3:07 PM, RFC Errata System <span > > > > dir=3D"ltr"><<a h= > > > > > ref=3D"mailto:rfc-editor@rfc-editor.org" > > > > target=3D"_blank">rfc-editor@rfc-e= > > > > > ditor.org</a>></span> wrote:<br><blockquote class=3D"gmail_quote" > > > > style= > > > > > =3D"margin:0 0 0 .8ex;border-left:1px #ccc > > solid;padding-left:1ex">The > > > > foll= > > > > owing errata report has been submitted for RFC4090,<br> > > > > > "Fast Reroute Extensions to RSVP-TE for LSP Tunnels".<br> > > > > > <br> > > > > > --------------------------------------<br> > > > > > You may review the report below and at:<br> > > > > > <a href=3D" > > > > http://www.rfc-editor.org/errata_search.php?rfc=3D4090&eid= > > > > > =3D4203" target=3D"_blank"> > > > > http://www.rfc-editor.org/errata_search.php?rfc= > > > > > =3D4090&eid=3D4203</a><br> > > > > > <br> > > > > > --------------------------------------<br> > > > > > Type: Technical<br> > > > > > Reported by: Yakov Rekhter <<a href=3D"mailto:yakov@juniper.net > > > > ">yakov@j= > > > > > uniper.net</a>><br> > > > > > <br> > > > > > Section: 6<br> > > > > > <br> > > > > > Original Text<br> > > > > > -------------<br> > > > > > Whenever the PLR has a backup path available, the PLR MUST set<br> > > > > > the "local protection available" flag.<br> > > > > > <br> > > > > > <br> > > > > > Corrected Text<br> > > > > > --------------<br> > > > > > Whenever the PLR has a one-to-one backup LSP or bypass tunnel<br> > > > > > available, the PLR MUST set the "local protection > > available" > > > > flag= > > > > > .<br> > > > > > <br> > > > > > <br> > > > > > Notes<br> > > > > > -----<br> > > > > > In the case of facility-based FRR the PLR must set the "local > > > > protecti= > > > > > on available" flag if it has the bypass tunnel available.<br> > > > > > <br> > > > > > Instructions:<br> > > > > > -------------<br> > > > > > This erratum is currently posted as "Reported". If > > necessary, > > > > ple= > > > > > ase<br> > > > > > use "Reply All" to discuss whether it should be verified > > or<br> > > > > > rejected. When a decision is reached, the verifying party (IESG)<br> > > > > > can log in to change the status and edit the report, if > > necessary.<br> > > > > > <br> > > > > > --------------------------------------<br> > > > > > RFC4090 (draft-ietf-mpls-rsvp-lsp-fastreroute-07)<br> > > > > > --------------------------------------<br> > > > > > Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Fast > > > > Reroute = > > > > > Extensions to RSVP-TE for LSP Tunnels<br> > > > > > Publication Date=C2=A0 =C2=A0 : May 2005<br> > > > > > Author(s)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: P. Pan, Ed., G. > > > > Swallow= > > > > > , Ed., A. Atlas, Ed.<br> > > > > > Category=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : PROPOSED > STANDARD<br> > > > > > Source=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : > > Multiprotocol > > > > Labe= > > > > > l Switching<br> > > > > > Area=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : > > Routing<br> > > > > > Stream=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : IETF<br> > > > > > Verifying Party=C2=A0 =C2=A0 =C2=A0: IESG<br> > > > > > <br> > > > > > </blockquote></div><br></div> > > > > > > > > > > --001a11397a2c9bda6e050a6f31ae-- > > > > > > > > > > --047d7b5d99a33a914b050a70164e > > > Content-Type: text/html; charset="UTF-8" > > > Content-Transfer-Encoding: quoted-printable > > > > > > <div dir=3D"ltr">Yakov,<div class=3D"gmail_extra"><br><div > > class=3D"gmail_q= > > > uote">On Wed, Dec 17, 2014 at 4:05 PM, Yakov Rekhter <span > > dir=3D"ltr"><= > > > <a href=3D"mailto:yakov@juniper.net" target=3D"_blank">yakov@juniper.net > > </a= > > > >></span> wrote:<br><blockquote class=3D"gmail_quote" > > style=3D"margin:0 = > > > 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Alia,<br> > > > <span class=3D""><br> > > > > Hi Yakov,<br> > > > ><br> > > > > Could you clarify your point for this errata?=C2=A0 In RFC 4090, in > > th= > > > e<br> > > > > terminology it says:<br> > > > >=C2=A0 "Backup Path: The LSP that is responsible for backing up > > on= > > > e<br> > > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 > > =C2=A0 = > > > =C2=A0 =C2=A0 protected LSP.=C2=A0 A backup path refers to either a<br> > > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 > > =C2=A0 = > > > =C2=A0 =C2=A0 detour LSP or a backup tunnel.<br> > > > ><br> > > > >=C2=A0 =C2=A0Backup Tunnel: The LSP that is used to backup up one of > > th= > > > e many<br> > > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 LSPs > > in = > > > many-to-one backup."<br> > > > <br> > > > </span>In the terminology it also says:<br> > > > <br> > > > =C2=A0 =C2=A0"Bypass Tunnel: An LSP that is used to protect a set > > of L= > > > SPs<br> > > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 passing over a common > > facility.&q= > > > uot;<br> > > > <br> > > > My point is that (unless the term "bypass tunnel" means the > > same<= > > > br> > > > as "backup path" or "backup tunnel") in many-to-one > > bac= > > > kup<br> > > > the "local protection available" flag for a given protected > > LSP<b= > > > r> > > > MUST be set when the PLR has a *bypass* tunnel for that > > LSP.<br></blockquot= > > > e><div><br></div><div>Ah - ok.=C2=A0 A backup path that uses a bypass > > tunne= > > > l is not just the bypass tunnel</div><div>itself.=C2=A0 There's the > > sta= > > > te associated for the protected LSP that also needs to > > be</div><div>created= > > > and installed.=C2=A0 In more concrete terms, this is installing an > > out-seg= > > > ment with=C2=A0</div><div>the appropriate label for the protected LSP to > > be= > > > understood by the merge point as</div><div>well as an outer label for > > the = > > > bypass LSP.</div><div><br></div><div>So, the text refers to a backup > > path i= > > > nstead of a bypass tunnel because having the</div><div>bypass tunnel > > isn= > > > 9;t quite sufficient.=C2=A0 Does that make sense to > > you?</div><div><br></di= > > > v><div>Regards,</div><div>Alia</div><div>=C2=A0</div><blockquote > > class=3D"g= > > > mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc > > solid;padding-l= > > > eft:1ex"> > > > Yakov.<br> > > > <div><div class=3D"h5"><br> > > > > Thanks,<br> > > > > Alia<br> > > > ><br> > > > > On Wed, Dec 17, 2014 at 3:07 PM, RFC Errata System <<br> > > > > <a href=3D"mailto:rfc-editor@rfc-editor.org"> > > rfc-editor@rfc-editor.org= > > > </a>> wrote:<br> > > > ><br> > > > > > The following errata report has been submitted for RFC4090,<br> > > > > > "Fast Reroute Extensions to RSVP-TE for LSP > > Tunnels".<b= > > > r> > > > > ><br> > > > > > --------------------------------------<br> > > > > > You may review the report below and at:<br> > > > > > <a href=3D" > > http://www.rfc-editor.org/errata_search.php?rfc=3D4090= > > > &eid=3D4203" target=3D"_blank"> > > http://www.rfc-editor.org/errata_search.= > > > php?rfc=3D4090&eid=3D4203</a><br> > > > > ><br> > > > > > --------------------------------------<br> > > > > > Type: Technical<br> > > > > > Reported by: Yakov Rekhter <<a href=3D"mailto: > > yakov@juniper.ne= > > > t">yakov@juniper.net</a>><br> > > > > ><br> > > > > > Section: 6<br> > > > > ><br> > > > > > Original Text<br> > > > > > -------------<br> > > > > > Whenever the PLR has a backup path available, the PLR MUST > > set<br= > > > > > > > > > the "local protection available" flag.<br> > > > > ><br> > > > > ><br> > > > > > Corrected Text<br> > > > > > --------------<br> > > > > > Whenever the PLR has a one-to-one backup LSP or bypass > > tunnel<br> > > > > > available, the PLR MUST set the "local protection > > available&= > > > quot; flag.<br> > > > > ><br> > > > > ><br> > > > > > Notes<br> > > > > > -----<br> > > > > > In the case of facility-based FRR the PLR must set the > > "loca= > > > l protection<br> > > > > > available" flag if it has the bypass tunnel available.<br> > > > > ><br> > > > > > Instructions:<br> > > > > > -------------<br> > > > > > This erratum is currently posted as "Reported". If > > nece= > > > ssary, please<br> > > > > > use "Reply All" to discuss whether it should be > > verifie= > > > d or<br> > > > > > rejected. When a decision is reached, the verifying party > > (IESG)<= > > > br> > > > > > can log in to change the status and edit the report, if > > necessary= > > > .<br> > > > > ><br> > > > > > --------------------------------------<br> > > > > > RFC4090 (draft-ietf-mpls-rsvp-lsp-fastreroute-07)<br> > > > > > --------------------------------------<br> > > > > > Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: > > Fas= > > > t Reroute Extensions to RSVP-TE for LSP Tunnels<br> > > > > > Publication Date=C2=A0 =C2=A0 : May 2005<br> > > > > > Author(s)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: P. Pan, > > Ed., = > > > G. Swallow, Ed., A. Atlas, Ed.<br> > > > > > Category=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : PROPOSED > > STAN= > > > DARD<br> > > > > > Source=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : > > Multipro= > > > tocol Label Switching<br> > > > > > Area=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : > > Rou= > > > ting<br> > > > > > Stream=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : > > IETF<br> > > > > > Verifying Party=C2=A0 =C2=A0 =C2=A0: IESG<br> > > > > ><br> > > > > ><br> > > > ><br> > > > </div></div>> --001a11397a2c9bda6e050a6f31ae<br> > > > > Content-Type: text/html; charset=3D"UTF-8"<br> > > > > Content-Transfer-Encoding: quoted-printable<br> > > > ><br> > > > > <div dir=3D3D"ltr">Hi > > Yakov,<br><br>Could = > > > you clarify your point for this err=3D<br> > > > > ata?=3DC2=3DA0 In RFC 4090, in the terminology it > > says:<br>&= > > > quot; Backup Path: =3D<br> > > > > The LSP that is responsible for backing up one<br>=3DC2=3DA0 > > =3D= > > > C2=3DA0 =3DC2=3DA0 =3DC2=3D<br> > > > > =3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 > > =3DC2=3DA= > > > 0 =3DC2=3DA0 =3DC2=3DA0protected LSP.=3D<br> > > > > =3DC2=3DA0 A backup path refers to either a detour > > LSP<br>=3DC2= > > > =3DA0 =3DC2=3DA0 =3DC2=3DA0 =3D<br> > > > > =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 > > =3DC= > > > 2=3DA0 =3DC2=3DA0 =3DC2=3DA0or a backup t=3D<br> > > > > unnel.<br><br>=3DC2=3DA0 Backup Tunnel: The LSP that is > > us= > > > ed to backup up one o=3D<br> > > > > f the many<br>=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 > > =3DC2= > > > =3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3D<br> > > > > =3DA0LSPs in many-to-one > > backup.&quot;<div><br></di= > > > v><div>Thanks,</div><div>A=3D<br> > > > > lia</div></div><div > > class=3D3D"gmail_extra"&g= > > > t;<br><div class=3D3D"gmail_quote">On=3D<br> > > > >=C2=A0 Wed, Dec 17, 2014 at 3:07 PM, RFC Errata System <span > > dir=3D3= > > > D"ltr">&lt;<a h=3D<br> > > > > ref=3D3D"mailto:<a href=3D"mailto:rfc-editor@rfc-editor.org > > ">rfc-= > > > editor@rfc-editor.org</a>" > > target=3D3D"_blank">rfc-editor= > > > @rfc-e=3D<br> > > > > <a href=3D"http://ditor.org" target=3D"_blank">ditor.org > > </a></a>= > > > &gt;</span> wrote:<br><blockquote > > class=3D3D"gmail_= > > > quote" style=3D<br> > > > > =3D3D"margin:0 0 0 .8ex;border-left:1px #ccc > > solid;padding-left:1= > > > ex">The foll=3D<br> > > > owing errata report has been submitted for RFC4090,<br><br> > > > > &quot;Fast Reroute Extensions to RSVP-TE for LSP > > Tunnels&quot;= > > > .<br><br> > > > > <br><br> > > > > --------------------------------------<br><br> > > > > You may review the report below and at:<br><br> > > > > <a href=3D3D"<a href=3D" > > http://www.rfc-editor.org/errata_searc= > > > h.php?rfc=3D3D4090&amp;eid=3D" target=3D"_blank"> > > http://www.rfc-editor.= > > > org/errata_search.php?rfc=3D3D4090&amp;eid=3D</a><br> > > > > =3D3D4203" target=3D3D"_blank"><a href=3D" > > http://www= > > > .rfc-editor.org/errata_search.php?rfc=3D" target=3D"_blank"> > > http://www.rfc-= > > > editor.org/errata_search.php?rfc=3D</a><br> > > > > =3D3D4090&amp;eid=3D3D4203</a><br><br> > > > > <br><br> > > > > --------------------------------------<br><br> > > > > Type: Technical<br><br> > > > > Reported by: Yakov Rekhter &lt;<a href=3D3D"mailto:<a > > href= > > > =3D"mailto:yakov@juniper.net">yakov@juniper.net</a>">yakov@j > > =3D<br> > > > > <a href=3D"http://uniper.net" target=3D"_blank">uniper.net > > </a></a&g= > > > t;&gt;<br><br> > > > > <br><br> > > > > Section: 6<br><br> > > > > <br><br> > > > > Original Text<br><br> > > > > -------------<br><br> > > > > Whenever the PLR has a backup path available, the PLR MUST > > set<br&g= > > > t;<br> > > > > the &quot;local protection available&quot; > > flag.<br><br> > > > > <br><br> > > > > <br><br> > > > > Corrected Text<br><br> > > > > --------------<br><br> > > > > Whenever the PLR has a one-to-one backup LSP or bypass > > tunnel<br>= > > > ;<br> > > > > available, the PLR MUST set the &quot;local protection > > available&a= > > > mp;quot; flag=3D<br> > > > > .<br><br> > > > > <br><br> > > > > <br><br> > > > > Notes<br><br> > > > > -----<br><br> > > > > In the case of facility-based FRR the PLR must set the > > &quot;local= > > > protecti=3D<br> > > > > on available&quot; flag if it has the bypass tunnel > > available.<= > > > br><br> > > > > <br><br> > > > > Instructions:<br><br> > > > > -------------<br><br> > > > > This erratum is currently posted as &quot;Reported&quot;. > > If n= > > > ecessary, ple=3D<br> > > > > ase<br><br> > > > > use &quot;Reply All&quot; to discuss whether it should be > > veri= > > > fied or<br><br> > > > > rejected. When a decision is reached, the verifying party > > (IESG)<br= > > > ><br> > > > > can log in to change the status and edit the report, if > > necessary.<= > > > br><br> > > > > <br><br> > > > > --------------------------------------<br><br> > > > > RFC4090 (draft-ietf-mpls-rsvp-lsp-fastreroute-07)<br><br> > > > > --------------------------------------<br><br> > > > > Title=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 > > =3DC2=3DA0= > > > =3DC2=3DA0 =3DC2=3DA0: Fast Reroute =3D<br> > > > > Extensions to RSVP-TE for LSP Tunnels<br><br> > > > > Publication Date=3DC2=3DA0 =3DC2=3DA0 : May 2005<br><br> > > > > Author(s)=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 > > =3DC2= > > > =3DA0: P. Pan, Ed., G. Swallow=3D<br> > > > > , Ed., A. Atlas, Ed.<br><br> > > > > Category=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 > > =3DC2= > > > =3DA0 : PROPOSED STANDARD<br><br> > > > > Source=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 > > =3DC2=3DA= > > > 0 =3DC2=3DA0 : Multiprotocol Labe=3D<br> > > > > l Switching<br><br> > > > > Area=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 > > =3DC2=3DA0 = > > > =3DC2=3DA0 =3DC2=3DA0 : Routing<br><br> > > > > Stream=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 > > =3DC2=3DA= > > > 0 =3DC2=3DA0 : IETF<br><br> > > > > Verifying Party=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0: IESG<br><br> > > > > <br><br> > > > > </blockquote></div><br></div><br> > > > ><br> > > > > --001a11397a2c9bda6e050a6f31ae--<br> > > > </blockquote></div><br></div></div> > > > > > > --047d7b5d99a33a914b050a70164e-- > > > > --001a11c1e9ee40fd19050a7068c9 > Content-Type: text/html; charset="UTF-8" > Content-Transfer-Encoding: quoted-printable > > <div dir=3D"ltr">Yakov,<div class=3D"gmail_extra"><br><div class=3D"gmail_q= > uote">On Wed, Dec 17, 2014 at 4:41 PM, Yakov Rekhter <span dir=3D"ltr"><= > <a href=3D"mailto:yakov@juniper.net" target=3D"_blank">yakov@juniper.net</a= > >></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 = > 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Alia,<br> > <span class=3D""><br> > > Yakov,<br> > ><br> > > On Wed, Dec 17, 2014 at 4:05 PM, Yakov Rekhter <<a href=3D"mailto:y= > akov@juniper.net">yakov@juniper.net</a>> wrote:<br> > ><br> > > > Alia,<br> > > ><br> > > > > Hi Yakov,<br> > > > ><br> > > > > Could you clarify your point for this errata?=C2=A0 In RFC 4= > 090, in the<br> > > > > terminology it says:<br> > > > >=C2=A0 "Backup Path: The LSP that is responsible for bac= > king up one<br> > > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= > =A0 =C2=A0 =C2=A0 =C2=A0 protected LSP.=C2=A0 A backup path refers to eithe= > r a<br> > > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= > =A0 =C2=A0 =C2=A0 =C2=A0 detour LSP or a backup tunnel.<br> > > > ><br> > > > >=C2=A0 =C2=A0Backup Tunnel: The LSP that is used to backup up= > one of the many<br> > > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= > =A0 LSPs in many-to-one backup."<br> > > ><br> > > > In the terminology it also says:<br> > > ><br> > > >=C2=A0 =C2=A0 "Bypass Tunnel: An LSP that is used to protect = > a set of LSPs<br> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0passing over a com= > mon facility."<br> > > ><br> > > > My point is that (unless the term "bypass tunnel" means= > the same<br> > > > as "backup path" or "backup tunnel") in many-= > to-one backup<br> > > > the "local protection available" flag for a given prote= > cted LSP<br> > > > MUST be set when the PLR has a *bypass* tunnel for that LSP.<br> > > ><br> > ><br> > > Ah - ok.=C2=A0 A backup path that uses a bypass tunnel is not just the= > bypass<br> > > tunnel itself.<br> > <br> > </span>Correct.<br> > <span class=3D""><br> > > There's the state associated for the protected LSP that<br> > > also needs to be created and installed.=C2=A0 In more concrete terms, = > this<br> > > is installing an out-segment with the appropriate label for the protec= > ted<br> > > LSP to be understood by the merge point as<br> > > well as an outer label for the bypass LSP.<br> > ><br> > > So, the text refers to a backup path instead of a bypass tunnel becaus= > e<br> > > having the bypass tunnel isn't quite sufficient.<br> > > Does that make sense to you?<br> > <br> > </span>The current text is incorrect. This is because a PLR may signal a<br= > > > backup path at the time of failure. Yet, one should not wait for<br> > the failure to set the "local protection available" flag. The PLR= > <br> > should set this flag as soon as it has a *bypass* tunnel.<br></blockquote><= > div><br></div><div>The backup path is created by the PLR before the failure= > and thus, before the</div><div>associated signaling.=C2=A0 Once the PLR ha= > s done the work to create a backup path using</div><div>an existing bypass = > tunnel - which is internal work - then the PLR should set</div><div>the &qu= > ot;local protection available" flag. =C2=A0</div><div><br></div><div>A= > lia=C2=A0<br></div><div><br></div><div>=C2=A0</div><blockquote class=3D"gma= > il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef= > t:1ex"> > Yakov.<br> > <div><div class=3D"h5"><br> > ><br> > > Regards,<br> > > Alia<br> > ><br> > ><br> > > > Yakov.<br> > > ><br> > > > > Thanks,<br> > > > > Alia<br> > > > ><br> > > > > On Wed, Dec 17, 2014 at 3:07 PM, RFC Errata System <<br> > > > > <a href=3D"mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-= > editor.org</a>> wrote:<br> > > > ><br> > > > > > The following errata report has been submitted for RFC4= > 090,<br> > > > > > "Fast Reroute Extensions to RSVP-TE for LSP Tunnel= > s".<br> > > > > ><br> > > > > > --------------------------------------<br> > > > > > You may review the report below and at:<br> > > > > > <a href=3D"http://www.rfc-editor.org/errata_search.php?= > rfc=3D4090&eid=3D4203" target=3D"_blank">http://www.rfc-editor.org/erra= > ta_search.php?rfc=3D4090&eid=3D4203</a><br> > > > > ><br> > > > > > --------------------------------------<br> > > > > > Type: Technical<br> > > > > > Reported by: Yakov Rekhter <<a href=3D"mailto:yakov@= > juniper.net">yakov@juniper.net</a>><br> > > > > ><br> > > > > > Section: 6<br> > > > > ><br> > > > > > Original Text<br> > > > > > -------------<br> > > > > > Whenever the PLR has a backup path available, the PLR M= > UST set<br> > > > > > the "local protection available" flag.<br> > > > > ><br> > > > > ><br> > > > > > Corrected Text<br> > > > > > --------------<br> > > > > > Whenever the PLR has a one-to-one backup LSP or bypass = > tunnel<br> > > > > > available, the PLR MUST set the "local protection = > available" flag.<br> > > > > ><br> > > > > ><br> > > > > > Notes<br> > > > > > -----<br> > > > > > In the case of facility-based FRR the PLR must set the = > "local<br> > > > protection<br> > > > > > available" flag if it has the bypass tunnel availa= > ble.<br> > > > > ><br> > > > > > Instructions:<br> > > > > > -------------<br> > > > > > This erratum is currently posted as "Reported"= > ;. If necessary, please<br> > > > > > use "Reply All" to discuss whether it should = > be verified or<br> > > > > > rejected. When a decision is reached, the verifying par= > ty (IESG)<br> > > > > > can log in to change the status and edit the report, if= > necessary.<br> > > > > ><br> > > > > > --------------------------------------<br> > > > > > RFC4090 (draft-ietf-mpls-rsvp-lsp-fastreroute-07)<br> > > > > > --------------------------------------<br> > > > > > Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = > =C2=A0: Fast Reroute Extensions to RSVP-TE for LSP<br> > > > Tunnels<br> > > > > > Publication Date=C2=A0 =C2=A0 : May 2005<br> > > > > > Author(s)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: P. = > Pan, Ed., G. Swallow, Ed., A. Atlas, Ed.<br> > > > > > Category=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : PRO= > POSED STANDARD<br> > > > > > Source=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = > : Multiprotocol Label Switching<br> > > > > > Area=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = > =C2=A0 : Routing<br> > > > > > Stream=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = > : IETF<br> > > > > > Verifying Party=C2=A0 =C2=A0 =C2=A0: IESG<br> > > > > ><br> > > > > ><br> > > > ><br> > > > > --001a11397a2c9bda6e050a6f31ae<br> > > > > Content-Type: text/html; charset=3D"UTF-8"<br> > > > > Content-Transfer-Encoding: quoted-printable<br> > > > ><br> > > > > <div dir=3D3D"ltr">Hi Yakov,<br><br= > >Could you clarify your point for this<br> > > > err=3D<br> > > > > ata?=3DC2=3DA0 In RFC 4090, in the terminology it says:<b= > r>&quot; Backup<br> > > > Path: =3D<br> > > > The LSP that is responsible for backing up one<br>=3DC= > 2=3DA0 =3DC2=3DA0 =3DC2=3DA0<br> > > > =3DC2=3D<br> > > > > =3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0= > =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0protected<br> > > > LSP.=3D<br> > > > > =3DC2=3DA0 A backup path refers to either a detour LSP<br= > >=3DC2=3DA0 =3DC2=3DA0<br> > > > =3DC2=3DA0 =3D<br> > > > > =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2= > =3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0or a<br> > > > backup t=3D<br> > > > > unnel.<br><br>=3DC2=3DA0 Backup Tunnel: The LSP = > that is used to backup up<br> > > > one o=3D<br> > > > > f the many<br>=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2= > =3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0<br> > > > =3DC2=3D<br> > > > > =3DA0LSPs in many-to-one<br> > > > backup.&quot;<div><br></div><div>Than= > ks,</div><div>A=3D<br> > > > > lia</div></div><div class=3D3D"gmail_ext= > ra"><br><div<br> > > > class=3D3D"gmail_quote">On=3D<br> > > > >=C2=A0 Wed, Dec 17, 2014 at 3:07 PM, RFC Errata System <sp= > an<br> > > > dir=3D3D"ltr">&lt;<a h=3D<br> > > > > ref=3D3D"mailto:<a href=3D"mailto:rfc-editor@rfc-editor= > .org">rfc-editor@rfc-editor.org</a>"<br> > > > target=3D3D"_blank">rfc-editor@rfc-e=3D<br> > > > > <a href=3D"http://ditor.org" target=3D"_blank">ditor.org</a>= > </a>&gt;</span> wrote:<br><blockquote class=3D3D&q= > uot;gmail_quote"<br> > > > style=3D<br> > > > > =3D3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd= > ing-left:1ex">The<br> > > > foll=3D<br> > > > owing errata report has been submitted for RFC4090,<br><br> > > > > &quot;Fast Reroute Extensions to RSVP-TE for LSP Tunnels= > &quot;.<br><br> > > > > <br><br> > > > > --------------------------------------<br><br> > > > > You may review the report below and at:<br><br> > > > > <a href=3D3D"<br> > > > <a href=3D"http://www.rfc-editor.org/errata_search.php?rfc=3D3D40= > 90&amp;eid=3D" target=3D"_blank">http://www.rfc-editor.org/errata_searc= > h.php?rfc=3D3D4090&amp;eid=3D</a><br> > > > > =3D3D4203" target=3D3D"_blank"><br> > > > <a href=3D"http://www.rfc-editor.org/errata_search.php?rfc=3D" ta= > rget=3D"_blank">http://www.rfc-editor.org/errata_search.php?rfc=3D</a><br> > > > > =3D3D4090&amp;eid=3D3D4203</a><br><br> > > > > <br><br> > > > > --------------------------------------<br><br> > > > > Type: Technical<br><br> > > > > Reported by: Yakov Rekhter &lt;<a href=3D3D"mail= > to:<a href=3D"mailto:yakov@juniper.net">yakov@juniper.net</a><br> > > > ">yakov@j=3D<br> > > > > <a href=3D"http://uniper.net" target=3D"_blank">uniper.net</= > a></a>&gt;<br><br> > > > > <br><br> > > > > Section: 6<br><br> > > > > <br><br> > > > > Original Text<br><br> > > > > -------------<br><br> > > > > Whenever the PLR has a backup path available, the PLR MUST s= > et<br><br> > > > > the &quot;local protection available&quot; flag.<= > br><br> > > > > <br><br> > > > > <br><br> > > > > Corrected Text<br><br> > > > > --------------<br><br> > > > > Whenever the PLR has a one-to-one backup LSP or bypass tunne= > l<br><br> > > > > available, the PLR MUST set the &quot;local protection a= > vailable&quot;<br> > > > flag=3D<br> > > > > .<br><br> > > > > <br><br> > > > > <br><br> > > > > Notes<br><br> > > > > -----<br><br> > > > > In the case of facility-based FRR the PLR must set the &= > quot;local<br> > > > protecti=3D<br> > > > > on available&quot; flag if it has the bypass tunnel avai= > lable.<br><br> > > > > <br><br> > > > > Instructions:<br><br> > > > > -------------<br><br> > > > > This erratum is currently posted as &quot;Reported&q= > uot;. If necessary,<br> > > > ple=3D<br> > > > > ase<br><br> > > > > use &quot;Reply All&quot; to discuss whether it shou= > ld be verified or<br><br> > > > > rejected. When a decision is reached, the verifying party (I= > ESG)<br><br> > > > > can log in to change the status and edit the report, if nece= > ssary.<br><br> > > > > <br><br> > > > > --------------------------------------<br><br> > > > > RFC4090 (draft-ietf-mpls-rsvp-lsp-fastreroute-07)<br><= > br> > > > > --------------------------------------<br><br> > > > > Title=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 = > =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0: Fast<br> > > > Reroute =3D<br> > > > > Extensions to RSVP-TE for LSP Tunnels<br><br> > > > > Publication Date=3DC2=3DA0 =3DC2=3DA0 : May 2005<br><b= > r> > > > > Author(s)=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2= > =3DA0 =3DC2=3DA0: P. Pan, Ed., G.<br> > > > Swallow=3D<br> > > > > , Ed., A. Atlas, Ed.<br><br> > > > > Category=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3D= > A0 =3DC2=3DA0 : PROPOSED STANDARD<br><br> > > > > Source=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0= > =3DC2=3DA0 =3DC2=3DA0 : Multiprotocol<br> > > > Labe=3D<br> > > > > l Switching<br><br> > > > > Area=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 = > =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 : Routing<br><br> > > > > Stream=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0= > =3DC2=3DA0 =3DC2=3DA0 : IETF<br><br> > > > > Verifying Party=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0: IESG<br&= > gt;<br> > > > > <br><br> > > > > </blockquote></div><br></div><br> > > > ><br> > > > > --001a11397a2c9bda6e050a6f31ae--<br> > > ><br> > ><br> > </div></div>> --047d7b5d99a33a914b050a70164e<br> > <span class=3D"">> Content-Type: text/html; charset=3D"UTF-8"<= > br> > > Content-Transfer-Encoding: quoted-printable<br> > ><br> > </span>> <div dir=3D3D"ltr">Yakov,<div class=3D3D&quo= > t;gmail_extra"><br><div class=3D3D"gmail_q=3D<br> > > uote">On Wed, Dec 17, 2014 at 4:05 PM, Yakov Rekhter <span = > dir=3D3D"ltr">&lt;=3D<br> > > <a href=3D3D"mailto:<a href=3D"mailto:yakov@juniper.net">yakov= > @juniper.net</a>" target=3D3D"_blank"><a href=3D"mailto:y= > akov@juniper.net">yakov@juniper.net</a></a=3D<br> > > >&gt;</span> wrote:<br><blockquote class=3D3D&qu= > ot;gmail_quote" style=3D3D"margin:0 =3D<br> > > 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Alia,<= > ;br><br> > > <span class=3D3D""><br><br> > > &gt; Hi Yakov,<br><br> > > &gt;<br><br> > > &gt; Could you clarify your point for this errata?=3DC2=3DA0 In RF= > C 4090, in th=3D<br> > > e<br><br> > > &gt; terminology it says:<br><br> > > &gt;=3DC2=3DA0 &quot;Backup Path: The LSP that is responsible = > for backing up on=3D<br> > e<br><br> > > &gt;=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2= > =3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3D<br> > > =3DC2=3DA0 =3DC2=3DA0 protected LSP.=3DC2=3DA0 A backup path refers to= > either a<br><br> > > &gt;=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2= > =3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3D<br> > > =3DC2=3DA0 =3DC2=3DA0 detour LSP or a backup tunnel.<br><br> > > &gt;<br><br> > > &gt;=3DC2=3DA0 =3DC2=3DA0Backup Tunnel: The LSP that is used to ba= > ckup up one of th=3D<br> > > e many<br><br> > > &gt;=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2= > =3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 LSPs in =3D<br> > > many-to-one backup.&quot;<br><br> > > <br><br> > > </span>In the terminology it also says:<br><br> > > <br><br> > > =3DC2=3DA0 =3DC2=3DA0&quot;Bypass Tunnel: An LSP that is used to p= > rotect a set of L=3D<br> > > SPs<br><br> > > =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 pass= > ing over a common facility.&q=3D<br> > > uot;<br><br> > > <br><br> > > My point is that (unless the term &quot;bypass tunnel&quot; me= > ans the same<=3D<br> > > br><br> > > as &quot;backup path&quot; or &quot;backup tunnel&quot= > ;) in many-to-one bac=3D<br> > > kup<br><br> > > the &quot;local protection available&quot; flag for a given pr= > otected LSP<b=3D<br> > > r><br> > > MUST be set when the PLR has a *bypass* tunnel for that LSP.<br>= > </blockquot=3D<br> > > e><div><br></div><div>Ah - ok.=3DC2=3DA0 A = > backup path that uses a bypass tunne=3D<br> > > l is not just the bypass tunnel</div><div>itself.=3DC2=3DA= > 0 There&#39;s the sta=3D<br> > > te associated for the protected LSP that also needs to be</div>&= > lt;div>created=3D<br> > >=C2=A0 and installed.=3DC2=3DA0 In more concrete terms, this is install= > ing an out-seg=3D<br> > > ment with=3DC2=3DA0</div><div>the appropriate label for th= > e protected LSP to be=3D<br> > >=C2=A0 understood by the merge point as</div><div>well as a= > n outer label for the =3D<br> > > bypass LSP.</div><div><br></div><div>So,= > the text refers to a backup path i=3D<br> > > nstead of a bypass tunnel because having the</div><div>byp= > ass tunnel isn&#3=3D<br> > > 9;t quite sufficient.=3DC2=3DA0 Does that make sense to you?</div&g= > t;<div><br></di=3D<br> > > v><div>Regards,</div><div>Alia</div><div= > >=3DC2=3DA0</div><blockquote class=3D3D"g=3D<br> > > mail_quote" style=3D3D"margin:0 0 0 .8ex;border-left:1px #cc= > c solid;padding-l=3D<br> > > eft:1ex"><br> > > Yakov.<br><br> > > <div><div class=3D3D"h5"><br><br> > > &gt; Thanks,<br><br> > > &gt; Alia<br><br> > > &gt;<br><br> > > &gt; On Wed, Dec 17, 2014 at 3:07 PM, RFC Errata System &lt;&l= > t;br><br> > > &gt; <a href=3D3D"mailto:<a href=3D"mailto:rfc-editor@rfc-= > editor.org">rfc-editor@rfc-editor.org</a>"><a href=3D"mailto:rfc-ed= > itor@rfc-editor.org">rfc-editor@rfc-editor.org</a>=3D<br> > > </a>&gt; wrote:<br><br> > > &gt;<br><br> > > &gt; &gt; The following errata report has been submitted for R= > FC4090,<br><br> > > &gt; &gt; &quot;Fast Reroute Extensions to RSVP-TE for LSP= > Tunnels&quot;.<b=3D<br> > > r><br> > > &gt; &gt;<br><br> > > &gt; &gt; --------------------------------------<br><br> > > &gt; &gt; You may review the report below and at:<br><br= > > > > &gt; &gt; <a href=3D3D"<a href=3D"http://www.rfc-edito= > r.org/errata_search.php?rfc=3D3D4090=3D" target=3D"_blank">http://www.rfc-e= > ditor.org/errata_search.php?rfc=3D3D4090=3D</a><br> > > &amp;eid=3D3D4203" target=3D3D"_blank"><a href= > =3D"http://www.rfc-editor.org/errata_search.=3D" target=3D"_blank">http://w= > ww.rfc-editor.org/errata_search.=3D</a><br> > > php?rfc=3D3D4090&amp;eid=3D3D4203</a><br><br> > > &gt; &gt;<br><br> > > &gt; &gt; --------------------------------------<br><br> > > &gt; &gt; Type: Technical<br><br> > > &gt; &gt; Reported by: Yakov Rekhter &lt;<a href=3D3D&q= > uot;mailto:<a href=3D"mailto:yakov@juniper.ne">yakov@juniper.ne</a>=3D<br> > > t"><a href=3D"mailto:yakov@juniper.net">yakov@juniper.net</a>&= > lt;/a>&gt;<br><br> > > &gt; &gt;<br><br> > > &gt; &gt; Section: 6<br><br> > > &gt; &gt;<br><br> > > &gt; &gt; Original Text<br><br> > > &gt; &gt; -------------<br><br> > > &gt; &gt; Whenever the PLR has a backup path available, the PL= > R MUST set<br=3D<br> > > ><br> > > &gt; &gt; the &quot;local protection available&quot; f= > lag.<br><br> > > &gt; &gt;<br><br> > > &gt; &gt;<br><br> > > &gt; &gt; Corrected Text<br><br> > > &gt; &gt; --------------<br><br> > > &gt; &gt; Whenever the PLR has a one-to-one backup LSP or bypa= > ss tunnel<br><br> > > &gt; &gt; available, the PLR MUST set the &quot;local prot= > ection available&=3D<br> > > quot; flag.<br><br> > > &gt; &gt;<br><br> > > &gt; &gt;<br><br> > > &gt; &gt; Notes<br><br> > > &gt; &gt; -----<br><br> > > &gt; &gt; In the case of facility-based FRR the PLR must set t= > he &quot;loca=3D<br> > > l protection<br><br> > > &gt; &gt; available&quot; flag if it has the bypass tunnel= > available.<br><br> > > &gt; &gt;<br><br> > > &gt; &gt; Instructions:<br><br> > > &gt; &gt; -------------<br><br> > > &gt; &gt; This erratum is currently posted as &quot;Report= > ed&quot;. If nece=3D<br> > > ssary, please<br><br> > > &gt; &gt; use &quot;Reply All&quot; to discuss whether= > it should be verifie=3D<br> > > d or<br><br> > > &gt; &gt; rejected. When a decision is reached, the verifying = > party (IESG)<=3D<br> > > br><br> > > &gt; &gt; can log in to change the status and edit the report,= > if necessary=3D<br> > > .<br><br> > > &gt; &gt;<br><br> > > &gt; &gt; --------------------------------------<br><br> > > &gt; &gt; RFC4090 (draft-ietf-mpls-rsvp-lsp-fastreroute-07)<= > ;br><br> > > &gt; &gt; --------------------------------------<br><br> > > &gt; &gt; Title=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3D= > C2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0: Fas=3D<br> > > t Reroute Extensions to RSVP-TE for LSP Tunnels<br><br> > > &gt; &gt; Publication Date=3DC2=3DA0 =3DC2=3DA0 : May 2005<= > br><br> > > &gt; &gt; Author(s)=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0= > =3DC2=3DA0 =3DC2=3DA0: P. Pan, Ed., =3D<br> > > G. Swallow, Ed., A. Atlas, Ed.<br><br> > > &gt; &gt; Category=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 = > =3DC2=3DA0 =3DC2=3DA0 : PROPOSED STAN=3D<br> > > DARD<br><br> > > &gt; &gt; Source=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 = > =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 : Multipro=3D<br> > > tocol Label Switching<br><br> > > &gt; &gt; Area=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC= > 2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 : Rou=3D<br> > > ting<br><br> > > &gt; &gt; Stream=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 = > =3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0 : IETF<br><br> > > &gt; &gt; Verifying Party=3DC2=3DA0 =3DC2=3DA0 =3DC2=3DA0: IES= > G<br><br> > > &gt; &gt;<br><br> > > &gt; &gt;<br><br> > > &gt;<br><br> > > </div></div>&gt; --001a11397a2c9bda6e050a6f31ae<br&= > gt;<br> > > &gt; Content-Type: text/html; charset=3D3D&quot;UTF-8&quot= > ;<br><br> > > &gt; Content-Transfer-Encoding: quoted-printable<br><br> > > &gt;<br><br> > > &gt; &lt;div dir=3D3D3D&quot;ltr&quot;&gt;Hi Yakov= > ,&lt;br&gt;&lt;br&gt;Could =3D<br> > > you clarify your point for this err=3D3D<br><br> > > &gt; ata?=3D3DC2=3D3DA0 In RFC 4090, in the terminology it says:&a= > mp;lt;br&gt;&amp;=3D<br> > > quot; Backup Path: =3D3D<br><br> > > &gt; The LSP that is responsible for backing up one&lt;br&= > gt;=3D3DC2=3D3DA0 =3D3D=3D<br> > > C2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3D<br><br> > > &gt; =3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2= > =3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA=3D<br> > > 0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA0protected LSP.=3D3D<br><br> > > &gt; =3D3DC2=3D3DA0 A backup path refers to either a detour LSP&am= > p;lt;br&gt;=3D3DC2=3D<br> > > =3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3D<br><br> > > &gt; =3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA0 = > =3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC=3D<br> > > 2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA0or a backup t=3D3D<br><br> > > &gt; unnel.&lt;br&gt;&lt;br&gt;=3D3DC2=3D3DA0 Back= > up Tunnel: The LSP that is us=3D<br> > > ed to backup up one o=3D3D<br><br> > > &gt; f the many&lt;br&gt;=3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D= > 3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D<br> > > =3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3D<b= > r><br> > > &gt; =3D3DA0LSPs in many-to-one backup.&amp;quot;&lt;div&a= > mp;gt;&lt;br&gt;&lt;/di=3D<br> > > v&gt;&lt;div&gt;Thanks,&lt;/div&gt;&lt;div&= > ;gt;A=3D3D<br><br> > > &gt; lia&lt;/div&gt;&lt;/div&gt;&lt;div class= > =3D3D3D&quot;gmail_extra&quot;&g=3D<br> > > t;&lt;br&gt;&lt;div class=3D3D3D&quot;gmail_quote&= > quot;&gt;On=3D3D<br><br> > > &gt;=3DC2=3DA0 Wed, Dec 17, 2014 at 3:07 PM, RFC Errata System &am= > p;lt;span dir=3D3D3=3D<br> > > D&quot;ltr&quot;&gt;&amp;lt;&lt;a h=3D3D<br>= > <br> > > &gt; ref=3D3D3D&quot;mailto:<a href=3D3D"mailto:<a hre= > f=3D"mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>"&= > gt;rfc-=3D<br> > > <a href=3D"mailto:editor@rfc-editor.org">editor@rfc-editor.org</a><= > /a>&quot; target=3D3D3D&quot;_blank&quot;&gt;rfc-editor= > =3D<br> > > @rfc-e=3D3D<br><br> > > &gt; <a href=3D3D"<a href=3D"http://ditor.org" target=3D"_= > blank">http://ditor.org</a>" target=3D3D"_blank"><a href= > =3D"http://ditor.org" target=3D"_blank">ditor.org</a></a>&lt;/a&a= > mp;gt;=3D<br> > > &amp;gt;&lt;/span&gt; wrote:&lt;br&gt;&lt;bloc= > kquote class=3D3D3D&quot;gmail_=3D<br> > > quote&quot; style=3D3D<br><br> > > &gt; =3D3D3D&quot;margin:0 0 0 .8ex;border-left:1px #ccc solid= > ;padding-left:1=3D<br> > > ex&quot;&gt;The foll=3D3D<br><br> > > owing errata report has been submitted for RFC4090,&lt;br&gt;&= > lt;br><br> > > &gt; &amp;quot;Fast Reroute Extensions to RSVP-TE for LSP Tunn= > els&amp;quot;=3D<br> > > .&lt;br&gt;<br><br> > > &gt; &lt;br&gt;<br><br> > > &gt; --------------------------------------&lt;br&gt;<b= > r><br> > > &gt; You may review the report below and at:&lt;br&gt;<= > br><br> > > &gt; &lt;a href=3D3D3D&quot;<a href=3D3D"<a href= > =3D"http://www.rfc-editor.org/errata_searc=3D" target=3D"_blank">http://www= > .rfc-editor.org/errata_searc=3D</a><br> > > h.php?rfc=3D3D3D4090&amp;amp;eid=3D3D" target=3D3D"_blan= > k"><a href=3D"http://www.rfc-editor." target=3D"_blank">http://www.= > rfc-editor.</a>=3D<br> > > org/errata_search.php?rfc=3D3D3D4090&amp;amp;eid=3D3D</a><= > ;br><br> > > &gt; =3D3D3D4203&quot; target=3D3D3D&quot;_blank&quot;= > &gt;<a href=3D3D"<a href=3D"http://www" target=3D"_blank">http:= > //www</a>=3D<br> > > .<a href=3D"http://rfc-editor.org/errata_search.php?rfc=3D3D" target= > =3D"_blank">rfc-editor.org/errata_search.php?rfc=3D3D</a>" target=3D3D= > "_blank"><a href=3D"http://www.rfc-" target=3D"_blank">http://= > www.rfc-</a>=3D<br> > > <a href=3D"http://editor.org/errata_search.php?rfc=3D3D" target=3D"_bl= > ank">editor.org/errata_search.php?rfc=3D3D</a></a><br><br> > > &gt; =3D3D3D4090&amp;amp;eid=3D3D3D4203&lt;/a&gt;&= > lt;br&gt;<br><br> > > &gt; &lt;br&gt;<br><br> > > &gt; --------------------------------------&lt;br&gt;<b= > r><br> > > &gt; Type: Technical&lt;br&gt;<br><br> > > &gt; Reported by: Yakov Rekhter &amp;lt;&lt;a href=3D3D3D&= > amp;quot;mailto:<a href=3D<br> > > =3D3D"mailto:<a href=3D"mailto:yakov@juniper.net">yakov@juniper.n= > et</a>"><a href=3D"mailto:yakov@juniper.net">yakov@juniper.net</a>&= > lt;/a>&quot;&gt;yakov@j=3D3D<br><br> > > &gt; <a href=3D3D"<a href=3D"http://uniper.net" target=3D"= > _blank">http://uniper.net</a>" target=3D3D"_blank"><a hre= > f=3D"http://uniper.net" target=3D"_blank">uniper.net</a></a>&lt;/= > a&g=3D<br> > > t;&amp;gt;&lt;br&gt;<br><br> > > &gt; &lt;br&gt;<br><br> > > &gt; Section: 6&lt;br&gt;<br><br> > > &gt; &lt;br&gt;<br><br> > > &gt; Original Text&lt;br&gt;<br><br> > > &gt; -------------&lt;br&gt;<br><br> > > &gt; Whenever the PLR has a backup path available, the PLR MUST se= > t&lt;br&g=3D<br> > > t;<br><br> > > &gt; the &amp;quot;local protection available&amp;quot; fl= > ag.&lt;br&gt;<br><br> > > &gt; &lt;br&gt;<br><br> > > &gt; &lt;br&gt;<br><br> > > &gt; Corrected Text&lt;br&gt;<br><br> > > &gt; --------------&lt;br&gt;<br><br> > > &gt; Whenever the PLR has a one-to-one backup LSP or bypass tunnel= > &lt;br&gt=3D<br> > > ;<br><br> > > &gt; available, the PLR MUST set the &amp;quot;local protectio= > n available&a=3D<br> > > mp;quot; flag=3D3D<br><br> > > &gt; .&lt;br&gt;<br><br> > > &gt; &lt;br&gt;<br><br> > > &gt; &lt;br&gt;<br><br> > > &gt; Notes&lt;br&gt;<br><br> > > &gt; -----&lt;br&gt;<br><br> > > &gt; In the case of facility-based FRR the PLR must set the &a= > mp;quot;local=3D<br> > >=C2=A0 protecti=3D3D<br><br> > > &gt; on available&amp;quot; flag if it has the bypass tunnel a= > vailable.&lt;=3D<br> > > br&gt;<br><br> > > &gt; &lt;br&gt;<br><br> > > &gt; Instructions:&lt;br&gt;<br><br> > > &gt; -------------&lt;br&gt;<br><br> > > &gt; This erratum is currently posted as &amp;quot;Reported&am= > p;amp;quot;. If n=3D<br> > > ecessary, ple=3D3D<br><br> > > &gt; ase&lt;br&gt;<br><br> > > &gt; use &amp;quot;Reply All&amp;quot; to discuss whether = > it should be veri=3D<br> > > fied or&lt;br&gt;<br><br> > > &gt; rejected. When a decision is reached, the verifying party (IE= > SG)&lt;br=3D<br> > > &gt;<br><br> > > &gt; can log in to change the status and edit the report, if neces= > sary.&lt;=3D<br> > > br&gt;<br><br> > > &gt; &lt;br&gt;<br><br> > > &gt; --------------------------------------&lt;br&gt;<b= > r><br> > > &gt; RFC4090 (draft-ietf-mpls-rsvp-lsp-fastreroute-07)&lt;br&a= > mp;gt;<br><br> > > &gt; --------------------------------------&lt;br&gt;<b= > r><br> > > &gt; Title=3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3= > DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA0=3D<br> > >=C2=A0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA0: Fast Reroute =3D3D<br><br> > > &gt; Extensions to RSVP-TE for LSP Tunnels&lt;br&gt;<br= > ><br> > > &gt; Publication Date=3D3DC2=3D3DA0 =3D3DC2=3D3DA0 : May 2005&= > lt;br&gt;<br><br> > > &gt; Author(s)=3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2= > =3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D<br> > > =3D3DA0: P. Pan, Ed., G. Swallow=3D3D<br><br> > > &gt; , Ed., A. Atlas, Ed.&lt;br&gt;<br><br> > > &gt; Category=3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2= > =3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D<br> > > =3D3DA0 : PROPOSED STANDARD&lt;br&gt;<br><br> > > &gt; Source=3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D= > 3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA=3D<br> > > 0 =3D3DC2=3D3DA0 : Multiprotocol Labe=3D3D<br><br> > > &gt; l Switching&lt;br&gt;<br><br> > > &gt; Area=3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3D= > A0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D<br> > > =3D3DC2=3D3DA0 =3D3DC2=3D3DA0 : Routing&lt;br&gt;<br><br= > > > > &gt; Stream=3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D= > 3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA=3D<br> > > 0 =3D3DC2=3D3DA0 : IETF&lt;br&gt;<br><br> > > &gt; Verifying Party=3D3DC2=3D3DA0 =3D3DC2=3D3DA0 =3D3DC2=3D3DA0: = > IESG&lt;br&gt;<br><br> > > &gt; &lt;br&gt;<br><br> > > &gt; &lt;/blockquote&gt;&lt;/div&gt;&lt;br&= > ;gt;&lt;/div&gt;<br><br> > > &gt;<br><br> > > &gt; --001a11397a2c9bda6e050a6f31ae--<br><br> > > </blockquote></div><br></div></div><br> > ><br> > > --047d7b5d99a33a914b050a70164e--<br> > </blockquote></div><br></div></div> > > --001a11c1e9ee40fd19050a7068c9--
- Re: [mpls] [Technical Errata Reported] RFC4090 (4… Alia Atlas
- [mpls] [Technical Errata Reported] RFC4090 (4203) RFC Errata System
- Re: [mpls] [Technical Errata Reported] RFC4090 (4… Yakov Rekhter
- Re: [mpls] [Technical Errata Reported] RFC4090 (4… Alia Atlas
- Re: [mpls] [Technical Errata Reported] RFC4090 (4… Yakov Rekhter
- Re: [mpls] [Technical Errata Reported] RFC4090 (4… Alia Atlas
- Re: [mpls] [Technical Errata Reported] RFC4090 (4… Yakov Rekhter
- Re: [mpls] [Technical Errata Reported] RFC4090 (4… Alia Atlas
- Re: [mpls] [Technical Errata Reported] RFC4090 (4… Yakov Rekhter
- [mpls] [Errata Verified] RFC4090 (4203) RFC Errata System