Re: [spring] Managing "global" SIDs

Jeff Tantsura <jefftant.ietf@gmail.com> Wed, 24 July 2019 18:02 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 205A112028E for <spring@ietfa.amsl.com>; Wed, 24 Jul 2019 11:02:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 jEltJHlpcZyx for <spring@ietfa.amsl.com>; Wed, 24 Jul 2019 11:02:13 -0700 (PDT)
Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (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 F055812015B for <spring@ietf.org>; Wed, 24 Jul 2019 11:02:12 -0700 (PDT)
Received: by mail-qt1-x82f.google.com with SMTP id w17so2064752qto.10 for <spring@ietf.org>; Wed, 24 Jul 2019 11:02:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version; bh=O75V/mqVdvwqo21WfKDer3ZATUpKrkiXssANZ1Rp/gU=; b=JMymrgvhHWlhHYESrxkmVqCx2lboLCHGm/EOXVc9FNntd8MVVe4jjjrmFnxQ6MdZI1 UIlI07SNZvyF7PIJa4FwBkNuPQFtppZzIcSRsHdcypzzgW4Xyvift+jZya4OV24eI0e6 FkE/1IMWgEZPBMDrVYd5bgaaf1cR1aoy6zoPOG6di8TeqZaWvG49KjUG047bkVA/HS4t DFp1LONicHPHWza1IiKl5mrv43/9yAZ78N2Kk4OxFw6eJgCTLdbRBaXK7wmA2ZfH8tmX ArZ8Rj2SVTZUoGeCkK9c+bJQlbTyfMG5oH8dxYFTbFS/JxN5nHewl2W7YfBml2Vkxp5R hcjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version; bh=O75V/mqVdvwqo21WfKDer3ZATUpKrkiXssANZ1Rp/gU=; b=W1NyrhWdj6ZDEWnpUW+/jnjvD8BwDxlchyGRPskSzCpa4T4190LorsvoqEUZStsxi/ NpvbkpULQ/RyUHLK+yWyUnxc81egEqLMleSKH7AviWt8Z2NqN8tHr+YROBdBYDh5wdC+ RwWBgBZjvnvtH2ixNHfChfbUbl4nYHlcsZ1XGItesRjGPJFJCaKSn0ifvf5sOXA2811l Jjbo/vjUQKrhzeX8Tt3cSs9ot7V6MixJdvBN+Oz5xnirLlc1BEgQ3/GnFuXeC7ziGJvO hlNnJmYZ2E+2cwAvJtN60m7Jw8Qtif0CvyCFmU0i30kyXssMjRByQ+jMISpr6+GSl3QC C3wQ==
X-Gm-Message-State: APjAAAWgXSQCMne2sgB/RwlL8Xz/UW1VhJInIRClTXJggyq0jA9uuMsZ HAexIUvaEyt+HOlaYB4A+NQ=
X-Google-Smtp-Source: APXvYqzfJPPgrXb8XtGWHtARFk0w4mSetG0iQJGr1JoXO8dOxy/DBFvnE4PRNn7kp2wv6SntJazMnA==
X-Received: by 2002:a0c:e703:: with SMTP id d3mr57649533qvn.194.1563991332070; Wed, 24 Jul 2019 11:02:12 -0700 (PDT)
Received: from [2001:67c:1232:144:2083:8e8c:ff7f::] ([2001:67c:1232:144:d98:cf9c:3dd2:aa26]) by smtp.gmail.com with ESMTPSA id y2sm21159489qkj.8.2019.07.24.11.02.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 Jul 2019 11:02:11 -0700 (PDT)
Date: Wed, 24 Jul 2019 14:02:02 -0400
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, "Andrew G. Malis" <agmalis@gmail.com>
Cc: SPRING WG List <spring@ietf.org>, Kireeti Kompella <kireeti.kompella@gmail.com>, Robert Raszuk <rraszuk@gmail.com>
Message-ID: <d44f23a9-4a6c-49fa-be2d-58ecad58d8e6@Spark>
In-Reply-To: <CAA=duU1YJDPFKtpXF+i3_YsqoOaN_n-P5dvVkTn3OY6nJ1=P2w@mail.gmail.com>
References: <CABRz93VUjBJhCB8aq7goV6_ws=0jJb5UeOPSeapP4c3+WUbH8w@mail.gmail.com> <CA+b+ER=pKm=KrQP3BO+=Vz6ByLzvZvmeTFeqJr9ntiUg_L5UBA@mail.gmail.com> <CABRz93W=S2P9AoMmwhUxMtjXvE6K6q1TB3ax5kMwBO=qhptcQw@mail.gmail.com> <AM0PR03MB382888B3783231FA5A629D2C9DC60@AM0PR03MB3828.eurprd03.prod.outlook.com> <CAA=duU1YJDPFKtpXF+i3_YsqoOaN_n-P5dvVkTn3OY6nJ1=P2w@mail.gmail.com>
X-Readdle-Message-ID: d44f23a9-4a6c-49fa-be2d-58ecad58d8e6@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5d389d1f_1a27709e_12dc6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/aOrZiVo4ZvTj0rRKt03XABxKDXc>
Subject: Re: [spring] Managing "global" SIDs
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jul 2019 18:02:16 -0000

All of the tasks described belong in management plane, while I’m not particularly fond of using DHCP, having single source of truth for configurational state is better than configuring box by box (and excel to manage it :))
Most SP’s (and as Stephane alluded) already have a centralized management entity that takes care of configuration management and soft resource (such as IP’s, SID’s, RT/RDs, etc allocation.

Cheers,
Jeff
On Jul 24, 2019, 12:38 PM -0400, Andrew G. Malis <agmalis@gmail.com>, wrote:
> Sasha,
>
> Most "normal" DHCP servers require manual configuration of some sort if you want to guarantee persistence of the assigned IP address (i.e. "static" DHCP). So we're back to "manual" management, even if the results of the manual management are conveyed by a dynamic protocol.
>
> Cheers,
> Andy
>
>
> > On Wed, Jul 24, 2019 at 11:53 AM Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> wrote:
> > > Robert, Kireeti and all,
> > > I think that both loopbacks and their association with SIDs should be kept persistent.
> > >
> > > Whether such persistency is provided by the means of static configuration, or by the means that are external to some dynamic protocol is a different question.
> > > E.g., a “normal” DHCP client (like my office computer) may think that it obtains a dynamic IP address in the company network from the DHCP server every time I turn it on, but the DHCP server actually takes care to assign to it the same IP address every time.
> > >
> > > Does this help in any way?
> > >
> > > Regards,
> > > Sasha
> > >
> > > Office: +972-39266302
> > > Cell:      +972-549266302
> > > Email:   Alexander.Vainshtein@ecitele.com
> > >
> > > From: spring <spring-bounces@ietf.org> On Behalf Of Kireeti Kompella
> > > Sent: Wednesday, July 24, 2019 6:36 PM
> > > To: Robert Raszuk <rraszuk@gmail.com>
> > > Cc: SPRING WG List <spring@ietf.org>
> > > Subject: Re: [spring] Managing "global" SIDs
> > >
> > > Hi Robert,
> > >
> > > On Wed, Jul 24, 2019 at 11:09 AM Robert Raszuk <rraszuk@gmail.com> wrote:
> > > > Hi Kireeti,
> > > >
> > > > I would like to challenge a bit your fundamental assumption which is to state that while loopbacks are very important and locally significant and warrant manual/nms provisioning SIDs are not.
> > >
> > > Actually, what I said at the mike is that I believe that both loopbacks and global SIDs should be managed by DHCP.  But that's a distraction; the point at hand is whether global SIDs should be managed "manually" (or by NMS or equivalent) (i.e., static), or by a protocol (say DHCP) (i.e., dynamic).  You say the former ... thanks for the feedback.
> > >
> > >  --
> > > Kireeti
> > >
> > > ___________________________________________________________________________
> > >
> > > This e-mail message is intended for the recipient only and contains information which is
> > > CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this
> > > transmission in error, please inform us by e-mail, phone or fax, and then delete the original
> > > and all copies thereof.
> > > ___________________________________________________________________________
> > > _______________________________________________
> > > spring mailing list
> > > spring@ietf.org
> > > https://www.ietf.org/mailman/listinfo/spring
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring