Re: [OSPF] Genart last call review of draft-ietf-ospf-link-overload-11
Pushpasis Sarkar <pushpasis.ietf@gmail.com> Thu, 11 January 2018 09:25 UTC
Return-Path: <pushpasis.ietf@gmail.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20B7B12EAC1; Thu, 11 Jan 2018 01:25:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.699
X-Spam-Level:
X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=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=gmail.com
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 NxW73wURF7xT; Thu, 11 Jan 2018 01:25:48 -0800 (PST)
Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E379B124D6C; Thu, 11 Jan 2018 01:25:47 -0800 (PST)
Received: by mail-it0-x22c.google.com with SMTP id x42so2777539ita.4; Thu, 11 Jan 2018 01:25:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=iJsIB1LO40s19Vnd0s6cxyXIVCWBLn0umeipyR7sQ9o=; b=tIYHwHjVO4ns+zEOiMJ1GiB/ofyGsOpsN7A7CU8PpAYR0X5bEMySX/UakcsevOUj7q uqOIa7yhtFzUpbhnIq05x7Q/GD9wiv75Rj29C154mtzdTb1g5rJrOQ8jgg1SEYGwYrDU 0Zihb2JkzJuOVaNS+wYw0ymfDtplfzeb/4OIMxOe4kPXsTkleIl5sCrrc+PKeEynNiS2 15bZx2NSDsKJlIA9gWtEGdY1dNrWx+og6qVHoD8tBNnX0eoJKirYrIRp50X3PHgpqFLq 6OcCGcPz6FC3c5tRjiQIuu1ugS+WHv+3pq19SSY+L4QE/0v0YM3wWcsQRjgr14AF2gNe KH9w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=iJsIB1LO40s19Vnd0s6cxyXIVCWBLn0umeipyR7sQ9o=; b=ujOnzBZ2D7vT6vA9sJVQy9Bz7huiNs7cxMQ3dauxgu9kP8vBHN1HnOIc7SmDZVu0mZ 8zKY/5XpGe9tTOivNF+GLIMSw/fhgIDhMb9pzsxZOeEu0TnuhTE0Kpb4OhWCc37Sjvby J6lVh42ONfAmObWcRFu75UVqWWCZZsne6DAyr806xz1OrZLpNzgHKsfDKoYg4A5Hq1vW Gwu2T2XlDljwhM9iF2Lw/U7e36VK+HMxuyO1W/1syxRwBcQ4SL3q7gfAYfuUuOJMSnpb fGs6VKWUjtcZ4PCk8ESAUehl+rnRkkq/SRsxSdlupgNKlHSl0f9UvZqUr514Nrg0lUod sNjg==
X-Gm-Message-State: AKwxytcx0sTlGQLPsSNe8R/AG2NYiqkiPEtpGt49lfofJCTOzaaGjX8B wcAllG12qhjYGcoaEMDVOUjFwXKL2+vjguH0t/0=
X-Google-Smtp-Source: ACJfBou4sFxrKzdiVit9OvhB3tcHnNyB84z2cu6EB1Iqy1b16EJ4cAO6YpqmhZGM/FacDxDDVTMwF+buvr+6Q1WwL0w=
X-Received: by 10.36.181.4 with SMTP id v4mr602437ite.42.1515662747065; Thu, 11 Jan 2018 01:25:47 -0800 (PST)
MIME-Version: 1.0
Received: by 10.2.159.153 with HTTP; Thu, 11 Jan 2018 01:25:46 -0800 (PST)
In-Reply-To: <D67A4FA7.E8FF1%acee@cisco.com>
References: <151510872060.14779.1209340587073567227@ietfa.amsl.com> <D6742D72.E86AC%acee@cisco.com> <bc44e16c2bf94d34a92d10c3f64ae07e@XCH-ALN-001.cisco.com> <D6745005.E86F2%acee@cisco.com> <07098d41e11849d9a320061bb68aec0f@XCH-ALN-008.cisco.com> <cbdc429805b64c87a4f66cb3da1a49d2@XCH-ALN-001.cisco.com> <D674E4F9.E87E8%acee@cisco.com> <BN3PR05MB27061E9F6515017EF94E10DCD51C0@BN3PR05MB2706.namprd05.prod.outlook.com> <26758_1515418771_5A537493_26758_190_1_53C29892C857584299CBF5D05346208A4793F82A@OPEXCLILM21.corporate.adroot.infra.ftgroup> <CAEFuwkiy1Rdnba3jyEcYq_43Xyutm9S4mQHpuGe2UnHE11Twbw@mail.gmail.com> <D67A4FA7.E8FF1%acee@cisco.com>
From: Pushpasis Sarkar <pushpasis.ietf@gmail.com>
Date: Thu, 11 Jan 2018 14:55:46 +0530
Message-ID: <CAEFuwkhCPYUrqceKgEv0OkXOKYHkn_v+GEEkoAA+Ho7FA536nw@mail.gmail.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
Cc: Bruno Decraene <bruno.decraene@orange.com>, Shraddha Hegde <shraddha@juniper.net>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "Ketan Talaulikar (ketant)" <ketant@cisco.com>, Joel Halpern <jmh@joelhalpern.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-ospf-link-overload.all@ietf.org" <draft-ietf-ospf-link-overload.all@ietf.org>
Content-Type: multipart/alternative; boundary="f403045d996ea3619405627cbb82"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/FSZIvmR_d9xzz5LZRGTLg9SLcJI>
Subject: Re: [OSPF] Genart last call review of draft-ietf-ospf-link-overload-11
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jan 2018 09:25:52 -0000
Hi Acee, LOL.. Might as well be 'link-on-break'.. :) Anyways graceful-link-shutdown seems to be the most agreed upon. Thanks and regards, -Pushpasis On Tue, Jan 9, 2018 at 9:29 PM, Acee Lindem (acee) <acee@cisco.com> wrote: > Hi Pushpasis, Shraddha, et al, > > From: Pushpasis Sarkar <pushpasis.ietf@gmail.com> > Date: Monday, January 8, 2018 at 12:22 PM > To: Bruno Decraene <bruno.decraene@orange.com> > Cc: Shraddha Hegde <shraddha@juniper.net>, Acee Lindem <acee@cisco.com>, > "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "Ketan Talaulikar > (ketant)" <ketant@cisco.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, " > gen-art@ietf.org" <gen-art@ietf.org>, OSPF WG List <ospf@ietf.org>, " > ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-ospf-link- > overload.all@ietf.org" <draft-ietf-ospf-link-overload.all@ietf.org> > Subject: Re: Genart last call review of draft-ietf-ospf-link-overload-11 > Resent-From: <alias-bounces@ietf.org> > Resent-To: Shraddha Hegde <shraddha@juniper.net>, Pushpasis Sarkar < > pushpasis.ietf@gmail.com>, Hannes Gredler <hannes@gredler.at>, < > mnanduri@ebay.com>, Luay Jalil <luay.jalil@verizon.com>, Acee Lindem < > acee@cisco.com>, <akr@cisco.com>, Alvaro Retana <aretana.ietf@gmail.com>, > Deborah Brungard <db3546@att.com>, Alia Atlas <akatlas@gmail.com>, Acee > Lindem <acee@cisco.com> > Resent-Date: Monday, January 8, 2018 at 12:22 PM > > Hi Joel et al, > > +1 for 'graceful-link-shutdown'. > > > I think we are converging on this. I must admit that it is much better > than “link-overload”. Although Les raises a good point that this behavior > could be used for other use cases, subsequent discussions have indicated > that these could be handled differently. > > > Another possibility may be 'link-decommission'.. > > > This implies too much permanence. If you decommission something, you are > more or less retiring It which is not this use case. This is more of giving > the link a rest. Maybe we could use the there term “Link on Leave” or LOL > state ;^). > > Thanks, > Acee > > > Thanks and regards > -Pushpasis > > On Mon, Jan 8, 2018 at 7:09 PM, <bruno.decraene@orange.com> wrote: > >> >> >> >> >> *From:* Shraddha Hegde >> >> How about “graceful-link-shutdown” ? >> >> >> >> Looks good to me. >> >> Also, FYI, for BGP sessions, in the GROW WG we used the term “Graceful BGP session shutdown” and named the BGP community “GRACEFUL_SHUTDOWN” so this would align on the terminology. >> >> https://tools.ietf.org/html/draft-ietf-grow-bgp-gshut-13 >> >> >> >> Best regards, >> >> --Bruno >> >> >> >> >> >> Rgds >> >> Shraddha >> >> >> >> >> >> >> >> *From:* Acee Lindem (acee) [mailto:acee@cisco.com <acee@cisco.com>] >> *Sent:* Friday, January 5, 2018 6:50 PM >> *To:* Les Ginsberg (ginsberg) <ginsberg@cisco.com>; Ketan Talaulikar >> (ketant) <ketant@cisco.com>; Joel Halpern <jmh@joelhalpern.com>; >> gen-art@ietf.org >> *Cc:* ospf@ietf.org; ietf@ietf.org; draft-ietf-ospf-link-overload. >> all@ietf.org >> *Subject:* Re: Genart last call review of draft-ietf-ospf-link-overload- >> 11 >> >> >> >> It is not in “maintenance" mode yet as it is still being used. However, >> it is better than “overload”. “pending-maintenance” is a bit long which is >> why I suggested “pending-shutdown” since “shutdown” is term that vendors >> have used for eons to described an interface that is not in service. >> >> Thanks, >> >> Acee >> >> >> >> *From: *"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> >> *Date: *Thursday, January 4, 2018 at 11:56 PM >> *To: *"Ketan Talaulikar (ketant)" <ketant@cisco.com>, Acee Lindem < >> acee@cisco.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, " >> gen-art@ietf.org" <gen-art@ietf.org> >> *Cc: *OSPF WG List <ospf@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, " >> draft-ietf-ospf-link-overload.all@ietf.org" < >> draft-ietf-ospf-link-overload.all@ietf.org> >> *Subject: *RE: Genart last call review of draft-ietf-ospf-link-overload- >> 11 >> >> >> >> Ketan – >> >> >> >> “maintenance” I could live with. >> >> >> >> “GIR” seems to not be generic enough. >> >> >> >> Les >> >> >> >> >> >> *From:* Ketan Talaulikar (ketant) >> *Sent:* Thursday, January 04, 2018 8:09 PM >> *To:* Acee Lindem (acee) <acee@cisco.com>; Les Ginsberg (ginsberg) < >> ginsberg@cisco.com>; Joel Halpern <jmh@joelhalpern.com>; gen-art@ietf.org >> *Cc:* ospf@ietf.org; ietf@ietf.org; draft-ietf-ospf-link-overload. >> all@ietf.org >> *Subject:* RE: Genart last call review of draft-ietf-ospf-link-overload- >> 11 >> >> >> >> Hello, >> >> >> >> May I suggest something more generic like “Maintenance Mode” or “Graceful >> Insertion/Removal (GIR) Mode” which could be defined so as to cover the >> multiple scenarios in question (e.g. pending shutdown, down for repairs, >> last resort due to poor link quality, etc.). >> >> >> >> Thanks, >> >> Ketan >> >> >> >> *From:* OSPF [mailto:ospf-bounces@ietf.org <ospf-bounces@ietf.org>] *On >> Behalf Of *Acee Lindem (acee) >> *Sent:* 05 January 2018 08:14 >> *To:* Les Ginsberg (ginsberg) <ginsberg@cisco.com>; Joel Halpern < >> jmh@joelhalpern.com>; gen-art@ietf.org >> *Cc:* ospf@ietf.org; ietf@ietf.org; draft-ietf-ospf-link-overload. >> all@ietf.org >> *Subject:* Re: [OSPF] Genart last call review of >> draft-ietf-ospf-link-overload-11 >> >> >> >> Hi Les, >> >> >> >> *From: *"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> >> *Date: *Thursday, January 4, 2018 at 9:26 PM >> *To: *Acee Lindem <acee@cisco.com>, "Joel M. Halpern" < >> jmh@joelhalpern.com>, "gen-art@ietf.org" <gen-art@ietf.org> >> *Cc: *OSPF WG List <ospf@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, " >> draft-ietf-ospf-link-overload.all@ietf.org" < >> draft-ietf-ospf-link-overload.all@ietf.org> >> *Subject: *RE: Genart last call review of draft-ietf-ospf-link-overload- >> 11 >> >> >> >> > >Minor issues: >> >> > > I understand the WG likes using the term "overload" for a link >> >> > >being taken >> >> > > out of service. I think people will learn what we mean. I do wish >> >> > >we had >> >> > > not chosen to misuse the words in this fashion. This is much more >> a >> >> > > graceful-link-close indication (or clsoe-pending indication) than >> >> > >it is an >> >> > > overload indication. >> >> > >> >> > I agree with this comment but I wasn’t sure we’d reach consensus on a >> >> > better alternative. However, after some though and consideration of >> current >> >> > OSPF router terminology, I’d propose we use the term “Pending-Shutdown”. >> >> > Does anyone not agree that this is a more appropriate moniker for the >> TLV >> >> > and state? >> >> > >> >> [Les:] I agree with Joel's comment. The use of the term "overload" is >> unfortunate. >> >> But "pending-shutdown" isn’t appealing to me because - at least in most >> use cases - you aren't actually going to shutdown the link. What you are >> going to do is make a link the "link of last resort". >> >> This seems a better choice. >> >> >> >> That is not the use case - you are going to take the link down. It is not >> going to be the "link of last resort”, it is the currently the “link of >> last resort” and will imminently be taken down. >> >> >> >> >> >> The suggestion from Shraddha that this term was borrowed from IS-IS isn't >> accurate. "overload" in IS-IS has a very different meaning - it indicates a >> node either has an incomplete LSDB or (a la RFC 3277 >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_rfc3277_&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=NyjLsr7JA7mvpCJa0YmPdVKcmMXJ31bpbBaNqzCNrng&m=7GM8zN1-Ff2au_agmHAkiNYK2R5Aji-EjpyT8gmgRYU&s=769ndBiWrwubwBNccNtOnDuHr1yMD-W10WuEarCDNgI&e=> >> )an incomplete forwarding plane. >> >> >> >> The only use of "link overload" in IS-IS occurs in >> https://tools.ietf.org/html/draft-ietf-isis-reverse-metric-07#section-3.6 >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dietf-2Disis-2Dreverse-2Dmetric-2D07-23section-2D3.6&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=NyjLsr7JA7mvpCJa0YmPdVKcmMXJ31bpbBaNqzCNrng&m=7GM8zN1-Ff2au_agmHAkiNYK2R5Aji-EjpyT8gmgRYU&s=r_8muG61-ePlkCbqf7qIcHUPHGtjWf_JOH1UXH7lp8U&e=> >> and this was added recently to support the (very useful) TE use case which >> was defined in https://tools.ietf.org/html/dr >> aft-ietf-ospf-link-overload-11 >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dietf-2Dospf-2Dlink-2Doverload-2D11&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=NyjLsr7JA7mvpCJa0YmPdVKcmMXJ31bpbBaNqzCNrng&m=7GM8zN1-Ff2au_agmHAkiNYK2R5Aji-EjpyT8gmgRYU&s=umZHmgXp6i4i0PAyZbsDS0iorBurDZsFIyvaVVXEHb0&e=> >> . When this was done the term "link-overload" was cut and pasted from the >> OSPF draft. I think this should also be changed in the IS-IS draft. >> >> >> >> Agreed. >> >> >> >> Thanks, >> >> Acee >> >> >> >> Les >> >> >> >> > Thanks, >> >> > Acee >> >> > > >> >> > > >> >> > > >> >> > >> >> > _______________________________________________ >> >> > OSPF mailing list >> >> > OSPF@ietf.org >> >> > https://www.ietf.org/mailman/listinfo/ospf >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_ospf&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=NyjLsr7JA7mvpCJa0YmPdVKcmMXJ31bpbBaNqzCNrng&m=7GM8zN1-Ff2au_agmHAkiNYK2R5Aji-EjpyT8gmgRYU&s=N51dsQzqzgGoBY61VJtqkgGHlrNjgZT_-9g8G_pcOyE&e=> >> >> _________________________________________________________________________________________________________________________ >> >> 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. >> >> >
- [OSPF] Genart last call review of draft-ietf-ospf… Joel Halpern
- Re: [OSPF] Genart last call review of draft-ietf-… Acee Lindem (acee)
- Re: [OSPF] Genart last call review of draft-ietf-… Les Ginsberg (ginsberg)
- Re: [OSPF] Genart last call review of draft-ietf-… Acee Lindem (acee)
- Re: [OSPF] Genart last call review of draft-ietf-… Ketan Talaulikar (ketant)
- Re: [OSPF] Genart last call review of draft-ietf-… Les Ginsberg (ginsberg)
- Re: [OSPF] Genart last call review of draft-ietf-… Les Ginsberg (ginsberg)
- Re: [OSPF] Genart last call review of draft-ietf-… Acee Lindem (acee)
- Re: [OSPF] Genart last call review of draft-ietf-… Shraddha Hegde
- Re: [OSPF] Genart last call review of draft-ietf-… Acee Lindem (acee)
- Re: [OSPF] Genart last call review of draft-ietf-… Les Ginsberg (ginsberg)
- Re: [OSPF] Genart last call review of draft-ietf-… bruno.decraene
- Re: [OSPF] Genart last call review of draft-ietf-… Pushpasis Sarkar
- Re: [OSPF] Genart last call review of draft-ietf-… Les Ginsberg (ginsberg)
- Re: [OSPF] Genart last call review of draft-ietf-… Acee Lindem (acee)
- Re: [OSPF] Genart last call review of draft-ietf-… Pushpasis Sarkar
- Re: [OSPF] Genart last call review of draft-ietf-… Jeff Tantsura
- Re: [OSPF] Genart last call review of draft-ietf-… Shraddha Hegde