Re: [Lsr] New Version Notificationfordraft-cheng-ospf-adjacency-suppress-00.txt
Yingzhen Qu <yingzhen.ietf@gmail.com> Mon, 13 March 2023 20:16 UTC
Return-Path: <yingzhen.ietf@gmail.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15ABEC157902 for <lsr@ietfa.amsl.com>; Mon, 13 Mar 2023 13:16:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.853
X-Spam-Level:
X-Spam-Status: No, score=-0.853 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, NUMERIC_HTTP_ADDR=1.242, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 ohmAl0WYUJ61 for <lsr@ietfa.amsl.com>; Mon, 13 Mar 2023 13:16:36 -0700 (PDT)
Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) (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 13534C14CE4A for <lsr@ietf.org>; Mon, 13 Mar 2023 13:16:36 -0700 (PDT)
Received: by mail-vs1-xe35.google.com with SMTP id v27so12121088vsa.7 for <lsr@ietf.org>; Mon, 13 Mar 2023 13:16:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678738595; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=PnV1fIAIfkV+w+jSQ58gd56pXjefqnsEo2811t6dxj4=; b=Bp+vs00+RT4KarXwKJPSYobUL6uXnkJOj6ItwPOZHAIantcwvNJLz4lilL2kigFFfr u/to/to4V/RfQeUmXaFVuhxBCaimjGvfSnNz2nw4m+VT0Y5iIgHuQlhKpSkhJrCfYfYf 8BCfCVnCACk227Fa/0xmRqJDQ8/VDKmBP4iZj4sEzOP3JffhipDps8w71pmoY6VJO5Ir m+hnqulIaBsG2PB8NmHgYbC2FmYCVVdukUMvSw8Iio5Aby9nfMrfxk2zBMSneNWNBH7l MJQde27Nq7UEvs3DK8emQR8b8pm6y9NfLj1ndM8O+QYrpo+Zq9w+AH4QM7+Hpmwx/0EU 2brQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678738595; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=PnV1fIAIfkV+w+jSQ58gd56pXjefqnsEo2811t6dxj4=; b=GgH4YC0+wIti5WDSMiEN4CpKwRjRC0En/HnEHIPK2hRFqUdCQO6bu5T/QQdmoo+UVX HV5lTaWmBCzuUIzN6z2Tg+OBXy0mLAD74bCm/dxQGF0H8G2Bnon6hGp0v6Ay8Fc05pev utgIFkhEutMqgDgnsCW3VoI0ILXPUbTLJiSunvM32vJcCK13mlvJVSqmkVGYLjkbHSJP TXNRTfo7oy1+RyD1hvVrOO9QIC22fTbOWM2zdFuIhV+iIA+3rZOXHWDbBdHhcO4BNXFc 9f3bVfuzMK6/0fFcjty3dRfNaFeA0KSe2idR4uyyAiWekpVNvvoi55ziVuF59tB/u/7C PRkw==
X-Gm-Message-State: AO0yUKUgHJMWxEoDel15qwNJXBzucosNGqUp1/MaHp3zABIVeRWupDA2 /w3mx99YpDo8LpKEnOQSUHINz32EWkUDFvcIRQ==
X-Google-Smtp-Source: AK7set+9UF7ZOk3uMn0vnDbtjzK03/dzC8Tywt5zd3qlNYTWLoGZEyakDHZIRVEp/YaQ8TFvihXZOpEZJRv/d7WozHo=
X-Received: by 2002:a67:ea49:0:b0:411:a740:c3ea with SMTP id r9-20020a67ea49000000b00411a740c3eamr23673026vso.0.1678738594932; Mon, 13 Mar 2023 13:16:34 -0700 (PDT)
MIME-Version: 1.0
References: <2b066406f183b42-0004a.Richmail.00008050997247534461@chinamobile.com> <EE024B84-A922-45A0-9B52-01281728AF26@gmail.com> <7FFD5712-3D9F-432B-AD61-F3E85FC12460@gmail.com>
In-Reply-To: <7FFD5712-3D9F-432B-AD61-F3E85FC12460@gmail.com>
From: Yingzhen Qu <yingzhen.ietf@gmail.com>
Date: Mon, 13 Mar 2023 13:16:23 -0700
Message-ID: <CABY-gOPoE9-W_keHaRidHJjZE5+RMhKSozFrjWgW+3NB+XH1fQ@mail.gmail.com>
To: Acee Lindem <acee.ietf@gmail.com>
Cc: "Mengxiao.Chen" <chen.mengxiao@h3c.com>, Les Ginsberg <ginsberg@cisco.com>, lsr <lsr@ietf.org>, Weiqiang Cheng <chengweiqiang@chinamobile.com>, linchangwang <linchangwang.04414@h3c.com>
Content-Type: multipart/alternative; boundary="0000000000009f2cee05f6cdc946"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/D7HIU8ZghyB3Edj5rr2a6Tz2McM>
Subject: Re: [Lsr] New Version Notificationfordraft-cheng-ospf-adjacency-suppress-00.txt
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Mar 2023 20:16:40 -0000
Noted. will add it to the agenda. Thanks, Yingzhen On Mon, Mar 13, 2023 at 1:06 PM Acee Lindem <acee.ietf@gmail.com> wrote: > Hi Yinzhen, > > I would like 5 minutes to present an alternative solution. The > presentation should immediately follow this presentation as the > hypothetical problem will have already have been presented. > > There isn’t a draft yet as I’m not sure this problem really needs to be > solved. > > Thanks, > Acee > > > On Mar 7, 2023, at 1:34 PM, Acee Lindem <acee.ietf@gmail.com> wrote: > > > > Hi Liyan, > > > > This is very unlikely to happen as flooding between the routers > commences as soon as they reach Exchange state. I’m wondering if you’ve > actually seen this situation or it is hypothetical. > > > > In any case, I have a better solution which wouldn’t add the delay for > the next hello packet without the SA flag to be received before advertising > the link. I’m busy with some other things right now and want to think about > it more. > > > > For now, we will add your presentation to the list for IETF 116. > > > > Thanks, > > Acee > > > > > > > >> On Mar 7, 2023, at 3:54 AM, Liyan Gong <gongliyan@chinamobile.com> > wrote: > >> > >> > >> Hi Les and Acee, > >> > >> Let me explain it further through the following diagram. > >> > >> 1) The neighbor relationship between Router A and Router B is stable. > The route 10.1.1.1/32 is reachable. > >> 2)Router A unplanned restarts and the loopback address has been > deleted.The process of the neighbor establish is as follows. > >> 3)The temporary blackhole occurs during the time range stated in the > right brace. > >> > >> There are two key points: > >> 1)Neighbor router reached the full state earlier. > >> 2)Neighbor router received the reoriginated lsas late. > >> > >> So,this purpose of the draft is to delay the point 1). > >> > >> Hope this helps,thank you. > >> > >> <1.png> > >> <image.png> > >> Best Regards, > >> Liyan > >> > >> > >> ----邮件原文---- > >> 发件人:"Mengxiao.Chen" <chen.mengxiao@h3c.com> > >> 收件人:"Les Ginsberg (ginsberg)" <ginsberg=40cisco.com@dmarc.ietf.org>,AceeLindem > <acee.ietf@gmail.com>,Liyan Gong <gongliyan@chinamobile.com> > >> 抄 送: lsr <lsr@ietf.org>,Weiqiang Cheng <chengweiqiang@chinamobile.com>,linchangwang > <linchangwang.04414@h3c.com> > >> 发送时间:2023-03-07 15:19:59 > >> 主题:Re: [Lsr] New Version Notification > fordraft-cheng-ospf-adjacency-suppress-00.txt > >> > >> Hi Les, > >> > >> Thank you for your comments. > >> OSPF does include the LSDB sync requirement. But OSPF state machine > does not guarantee the two routers attain FULL state at the same time. > >> > >> R1(restart)------R2------R3 > >> > >> R1 LSDB: R1's new router-LSA, seq 80000001 > >> R2 LSDB: R1's old router-LSA, seq 80000500 > >> > >> When R1 restarts from an unplanned outage, R1 will reinitialize its LSA > sequence number. But R2 has the previous copies of R1's LSA, which has > larger sequence number. > >> R2 thinks its local LSAs are "newer". So, R2 will attain FULL state, > without requesting R1 to update. > >> This may cause temporary blackholes to occur until R1 regenerates and > floods its own LSAs with higher sequence numbers. > >> > >> Thanks, > >> Mengxiao > >> > >> -----Original Message----- > >> From: Lsr <lsr-bounces@ietf.org> On Behalf Of Les Ginsberg (ginsberg) > >> Sent: Tuesday, March 7, 2023 1:29 AM > >> To: Acee Lindem <acee.ietf@gmail.com>; Liyan Gong < > gongliyan@chinamobile.com> > >> Cc: lsr <lsr@ietf.org> > >> Subject: Re: [Lsr] New Version Notification for > draft-cheng-ospf-adjacency-suppress-00.txt > >> > >> +1 to what Acee has said. > >> > >> As historical context, the SA bit was defined in IS-IS precisely > because IS-IS adjacency state machine does NOT include LSPDB sync as a > requirement before the adjacency is usable (unlike OSPF). > >> OSPF does not need SA bit. > >> > >> Les > >> > >>> -----Original Message----- > >>> From: Lsr <lsr-bounces@ietf.org> On Behalf Of Acee Lindem > >>> Sent: Monday, March 6, 2023 8:01 AM > >>> To: Liyan Gong <gongliyan@chinamobile.com> > >>> Cc: lsr <lsr@ietf.org> > >>> Subject: Re: [Lsr] New Version Notification for > draft-cheng-ospf-adjacency- > >>> suppress-00.txt > >>> > >>> Hi Liyan, > >>> > >>> I should replied to this Email rather than your request for an IETF > 116 slot. > >>> Please reply to this one. > >>> > >>> I’m sorry but I don’t get this draft from a quick read. An OSPF router > would > >>> not advertise an adjacency until the router is in FULL state. An OSPF > router > >>> will not attain FULL state until database synchronization is complete. > >>> The following statement from you use case is incorrect: > >>> > >>> So, without requesting the starting router to update its LSAs, the > >>> neighbors of the starting router may transition to "Full" state and > >>> route the traffic through the starting router. > >>> > >>> Why do you think you need this extension? > >>> > >>> > >>> Thanks, > >>> Acee > >>> > >>> > >>>> On Mar 6, 2023, at 9:10 AM, Liyan Gong <gongliyan@chinamobile.com> > >>> wrote: > >>>> > >>>> Dear All, > >>>> We have posted a new draft > https://datatracker.ietf.org/doc/draft-cheng- > >>> ospf-adjacency-suppress/. > >>>> This draft describes the extension of OSPF LLS to signal adjacency > >>> suppression which is functionally similar to the SA bit of Restart TLV > in IS-IS. > >>>> The purpose is to avoid the temporary blackhole when a router restarts > >>> from unplanned outages. > >>>> We are looing forward to your comments.Thanks a lot. > >>>> > >>>> Best Regards, > >>>> Liyan > >>>> > >>>> ----邮件原文---- > >>>> 发件人:internet-drafts <internet-drafts@ietf.org> > >>>> 收件人:Changwang Lin <linchangwang.04414@h3c.com>,Liyan Gong > >>> <gongliyan@chinamobile.com>,Mengxiao Chen > >>> <chen.mengxiao@h3c.com>,Weiqiang Cheng > >>> <chengweiqiang@chinamobile.com> > >>>> 抄 送: (无) > >>>> 发送时间:2023-03-06 17:43:39 > >>>> 主题:New Version Notification for draft-cheng-ospf-adjacency-suppress- > >>> 00.txt > >>>> > >>>> > >>>> A new version of I-D, draft-cheng-ospf-adjacency-suppress-00.txt > >>>> has been successfully submitted by Mengxiao Chen and posted to the > >>>> IETF repository. > >>>> > >>>> Name: draft-cheng-ospf-adjacency-suppress > >>>> Revision: 00 > >>>> Title: OSPF Adjacency Suppression > >>>> Document date: 2023-03-06 > >>>> Group: Individual Submission > >>>> Pages: 8 > >>>> URL: > https://www.ietf.org/archive/id/draft-cheng-ospf-adjacency- > >>> suppress-00.txt > >>>> Status: > https://datatracker.ietf.org/doc/draft-cheng-ospf-adjacency- > >>> suppress/ > >>>> Htmlized: > https://datatracker.ietf.org/doc/html/draft-cheng-ospf- > >>> adjacency-suppress > >>>> > >>>> > >>>> Abstract: > >>>> This document describes a mechanism for a router to signal its > >>>> neighbors to suppress advertising the adjacency to it until link- > >>>> state database synchronization is complete. This minimizes transient > >>>> routing disruption when a router restarts from unplanned outages. > >>>> > >>>> > >>>> > >>>> > >>>> The IETF Secretariat > >>>> > >>>> > >>>> > >>>> Subject:New Version Notification for draft-cheng-ospf-adjacency- > >>> suppress-00.txt > >>>> > >>>> > >>>> A new version of I-D, draft-cheng-ospf-adjacency-suppress-00.txt > >>>> has been successfully submitted by Mengxiao Chen and posted to the > >>>> IETF repository. > >>>> > >>>> Name: draft-cheng-ospf-adjacency-suppress > >>>> Revision: 00 > >>>> Title: OSPF Adjacency Suppression > >>>> Document date: 2023-03-06 > >>>> Group: Individual Submission > >>>> Pages: 8 > >>>> URL: > https://www.ietf.org/archive/id/draft-cheng-ospf-adjacency- > >>> suppress-00.txt > >>>> Status: > https://datatracker.ietf.org/doc/draft-cheng-ospf-adjacency- > >>> suppress/ > >>>> Htmlized: > https://datatracker.ietf.org/doc/html/draft-cheng-ospf- > >>> adjacency-suppress > >>>> > >>>> > >>>> Abstract: > >>>> This document describes a mechanism for a router to signal its > >>>> neighbors to suppress advertising the adjacency to it until link- > >>>> state database synchronization is complete. This minimizes transient > >>>> routing disruption when a router restarts from unplanned outages. > >>>> > >>>> > >>>> > >>>> > >>>> The IETF Secretariat > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> Lsr mailing list > >>>> Lsr@ietf.org > >>>> https://www.ietf.org/mailman/listinfo/lsr > >>> > >>> _______________________________________________ > >>> Lsr mailing list > >>> Lsr@ietf.org > >>> https://www.ietf.org/mailman/listinfo/lsr > >> _______________________________________________ > >> Lsr mailing list > >> Lsr@ietf.org > >> https://www.ietf.org/mailman/listinfo/lsr > >> > ------------------------------------------------------------------------------------------------------------------------------------- > >> 本邮件及其附件含有新华三集团的保密信息,仅限于发送给上面地址中列出 > >> 的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、 > >> 或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本 > >> 邮件! > >> This e-mail and its attachments contain confidential information from > New H3C, which is > >> intended only for the person or entity whose address is listed above. > Any use of the > >> information contained herein in any way (including, but not limited to, > total or partial > >> disclosure, reproduction, or dissemination) by persons other than the > intended > >> recipient(s) is prohibited. If you receive this e-mail in error, please > notify the sender > >> by phone or email immediately and delete it! > >> _______________________________________________ > >> Lsr mailing list > >> Lsr@ietf.org > >> https://www.ietf.org/mailman/listinfo/lsr > >> > >> Subject:Re: [Lsr] New Version Notification > fordraft-cheng-ospf-adjacency-suppress-00.txt > >> > >> Hi Les, > >> > >> Thank you for your comments. > >> OSPF does include the LSDB sync requirement. But OSPF state machine > does not guarantee the two routers attain FULL state at the same time. > >> > >> R1(restart)------R2------R3 > >> > >> R1 LSDB: R1's new router-LSA, seq 80000001 > >> R2 LSDB: R1's old router-LSA, seq 80000500 > >> > >> When R1 restarts from an unplanned outage, R1 will reinitialize its LSA > sequence number. But R2 has the previous copies of R1's LSA, which has > larger sequence number. > >> R2 thinks its local LSAs are "newer". So, R2 will attain FULL state, > without requesting R1 to update. > >> This may cause temporary blackholes to occur until R1 regenerates and > floods its own LSAs with higher sequence numbers. > >> > >> Thanks, > >> Mengxiao > >> > >> -----Original Message----- > >> From: Lsr <lsr-bounces@ietf.org> On Behalf Of Les Ginsberg (ginsberg) > >> Sent: Tuesday, March 7, 2023 1:29 AM > >> To: Acee Lindem <acee.ietf@gmail.com>; Liyan Gong < > gongliyan@chinamobile.com> > >> Cc: lsr <lsr@ietf.org> > >> Subject: Re: [Lsr] New Version Notification for > draft-cheng-ospf-adjacency-suppress-00.txt > >> > >> +1 to what Acee has said. > >> > >> As historical context, the SA bit was defined in IS-IS precisely > because IS-IS adjacency state machine does NOT include LSPDB sync as a > requirement before the adjacency is usable (unlike OSPF). > >> OSPF does not need SA bit. > >> > >> Les > >> > >>> -----Original Message----- > >>> From: Lsr <lsr-bounces@ietf.org> On Behalf Of Acee Lindem > >>> Sent: Monday, March 6, 2023 8:01 AM > >>> To: Liyan Gong <gongliyan@chinamobile.com> > >>> Cc: lsr <lsr@ietf.org> > >>> Subject: Re: [Lsr] New Version Notification for > draft-cheng-ospf-adjacency- > >>> suppress-00.txt > >>> > >>> Hi Liyan, > >>> > >>> I should replied to this Email rather than your request for an IETF > 116 slot. > >>> Please reply to this one. > >>> > >>> I’m sorry but I don’t get this draft from a quick read. An OSPF router > would > >>> not advertise an adjacency until the router is in FULL state. An OSPF > router > >>> will not attain FULL state until database synchronization is complete. > >>> The following statement from you use case is incorrect: > >>> > >>> So, without requesting the starting router to update its LSAs, the > >>> neighbors of the starting router may transition to "Full" state and > >>> route the traffic through the starting router. > >>> > >>> Why do you think you need this extension? > >>> > >>> > >>> Thanks, > >>> Acee > >>> > >>> > >>>> On Mar 6, 2023, at 9:10 AM, Liyan Gong <gongliyan@chinamobile.com> > >>> wrote: > >>>> > >>>> Dear All, > >>>> We have posted a new draft > https://datatracker.ietf.org/doc/draft-cheng- > >>> ospf-adjacency-suppress/. > >>>> This draft describes the extension of OSPF LLS to signal adjacency > >>> suppression which is functionally similar to the SA bit of Restart TLV > in IS-IS. > >>>> The purpose is to avoid the temporary blackhole when a router restarts > >>> from unplanned outages. > >>>> We are looing forward to your comments.Thanks a lot. > >>>> > >>>> Best Regards, > >>>> Liyan > >>>> > >>>> ----邮件原文---- > >>>> 发件人:internet-drafts <internet-drafts@ietf.org> > >>>> 收件人:Changwang Lin <linchangwang.04414@h3c.com>,Liyan Gong > >>> <gongliyan@chinamobile.com>,Mengxiao Chen > >>> <chen.mengxiao@h3c.com>,Weiqiang Cheng > >>> <chengweiqiang@chinamobile.com> > >>>> 抄 送: (无) > >>>> 发送时间:2023-03-06 17:43:39 > >>>> 主题:New Version Notification for draft-cheng-ospf-adjacency-suppress- > >>> 00.txt > >>>> > >>>> > >>>> A new version of I-D, draft-cheng-ospf-adjacency-suppress-00.txt > >>>> has been successfully submitted by Mengxiao Chen and posted to the > >>>> IETF repository. > >>>> > >>>> Name: draft-cheng-ospf-adjacency-suppress > >>>> Revision: 00 > >>>> Title: OSPF Adjacency Suppression > >>>> Document date: 2023-03-06 > >>>> Group: Individual Submission > >>>> Pages: 8 > >>>> URL: > https://www.ietf.org/archive/id/draft-cheng-ospf-adjacency- > >>> suppress-00.txt > >>>> Status: > https://datatracker.ietf.org/doc/draft-cheng-ospf-adjacency- > >>> suppress/ > >>>> Htmlized: > https://datatracker.ietf.org/doc/html/draft-cheng-ospf- > >>> adjacency-suppress > >>>> > >>>> > >>>> Abstract: > >>>> This document describes a mechanism for a router to signal its > >>>> neighbors to suppress advertising the adjacency to it until link- > >>>> state database synchronization is complete. This minimizes transient > >>>> routing disruption when a router restarts from unplanned outages. > >>>> > >>>> > >>>> > >>>> > >>>> The IETF Secretariat > >>>> > >>>> > >>>> > >>>> Subject:New Version Notification for draft-cheng-ospf-adjacency- > >>> suppress-00.txt > >>>> > >>>> > >>>> A new version of I-D, draft-cheng-ospf-adjacency-suppress-00.txt > >>>> has been successfully submitted by Mengxiao Chen and posted to the > >>>> IETF repository. > >>>> > >>>> Name: draft-cheng-ospf-adjacency-suppress > >>>> Revision: 00 > >>>> Title: OSPF Adjacency Suppression > >>>> Document date: 2023-03-06 > >>>> Group: Individual Submission > >>>> Pages: 8 > >>>> URL: > https://www.ietf.org/archive/id/draft-cheng-ospf-adjacency- > >>> suppress-00.txt > >>>> Status: > https://datatracker.ietf.org/doc/draft-cheng-ospf-adjacency- > >>> suppress/ > >>>> Htmlized: > https://datatracker.ietf.org/doc/html/draft-cheng-ospf- > >>> adjacency-suppress > >>>> > >>>> > >>>> Abstract: > >>>> This document describes a mechanism for a router to signal its > >>>> neighbors to suppress advertising the adjacency to it until link- > >>>> state database synchronization is complete. This minimizes transient > >>>> routing disruption when a router restarts from unplanned outages. > >>>> > >>>> > >>>> > >>>> > >>>> The IETF Secretariat > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> Lsr mailing list > >>>> Lsr@ietf.org > >>>> https://www.ietf.org/mailman/listinfo/lsr > >>> > >>> _______________________________________________ > >>> Lsr mailing list > >>> Lsr@ietf.org > >>> https://www.ietf.org/mailman/listinfo/lsr > >> _______________________________________________ > >> Lsr mailing list > >> Lsr@ietf.org > >> https://www.ietf.org/mailman/listinfo/lsr > >> > ------------------------------------------------------------------------------------------------------------------------------------- > >> 本邮件及其附件含有新华三集团的保密信息,仅限于发送给上面地址中列出 > >> 的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、 > >> 或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本 > >> 邮件! > >> This e-mail and its attachments contain confidential information from > New H3C, which is > >> intended only for the person or entity whose address is listed above. > Any use of the > >> information contained herein in any way (including, but not limited to, > total or partial > >> disclosure, reproduction, or dissemination) by persons other than the > intended > >> recipient(s) is prohibited. If you receive this e-mail in error, please > notify the sender > >> by phone or email immediately and delete it! > >> _______________________________________________ > >> Lsr mailing list > >> Lsr@ietf.org > >> https://www.ietf.org/mailman/listinfo/lsr > >> > > > >
- Re: [Lsr] New Version Notificationfordraft-cheng-… Liyan Gong
- Re: [Lsr] New Version Notificationfordraft-cheng-… Acee Lindem
- Re: [Lsr] New Version Notificationfordraft-cheng-… Acee Lindem
- Re: [Lsr] New Version Notificationfordraft-cheng-… Yingzhen Qu