Re: [babel] proposed info model change

David Schinazi <dschinazi.ietf@gmail.com> Fri, 12 February 2021 03:09 UTC

Return-Path: <dschinazi.ietf@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 067753A1114 for <babel@ietfa.amsl.com>; Thu, 11 Feb 2021 19:09:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, 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 JNdMMlroGcw5 for <babel@ietfa.amsl.com>; Thu, 11 Feb 2021 19:09:48 -0800 (PST)
Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (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 78E333A1111 for <babel@ietf.org>; Thu, 11 Feb 2021 19:09:48 -0800 (PST)
Received: by mail-pg1-x529.google.com with SMTP id b21so5344149pgk.7 for <babel@ietf.org>; Thu, 11 Feb 2021 19:09:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=iTq6161eiOPDvfl5FMCZMbcyQThv3tOSXQv9K6PDXMI=; b=tB6w3f3r+FUnLgD8pA4qu9h/b5ODcrvO7It3mREnsma8sxILLF/iyK80qeBS7nbhSi HBoSG3uXbTgosTPQuIuTSrLI6kDAuA7oba3kxsYqxg7lCMWAgaMtJKYv1gRzR9vrKUyj BdrVeVM8Gx5QjQWC7LfLYLbhbUuLriyV1VHz01aUtxDng+zk3mEihSkW5BT1ZejX372e qrPGeRjISbYR11CiD0RoXJ45/wlOaBM+0OGhYv8fiGNrCMZKuOeIo4be9nbAXfZvAsXu NG/4kP7WAwfYo2BSi8E/ZlJli/WWjHiKi7O2ikARJovLUgTthy6k6WiPuyhr7xk5Z/C5 SfLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=iTq6161eiOPDvfl5FMCZMbcyQThv3tOSXQv9K6PDXMI=; b=SmfXtpXwlrQ8WzfIdmWnO7ggG9Pvq2ZBkzx1gW79qUFFZAgjX04CSgqgvrkOFtM4yg O+tiXteVKPozfcFZnG/V54TdYVTr+VHAyB2ENQUzwAAYW/hhgrf31nxKVi89nceszA/V H3Rvo7dH338Cy/3A+DrhysKkbQ8quv2JrMGf+bXb6T4kQPJdeGCamzxtBwNRzi8lTJPV KMAbVivXOQv1ITDuCEZedI3kwlnzQERH16/U0aa+C+jxRtAQhXBF8zJbUstkEwPbEiZR yRtL38GOmO9etiPeplL1nsZqVUFthS1m58pMbyHolrcR8X8XQYwTNNFFocIgcOUuOCRc 4Alw==
X-Gm-Message-State: AOAM530h2gJLWyxNRbSJuKI5KuC3J5f5yTafvzjtucOdll1StT2hIvGO J0loC0F9l2wnNbS45uwQaE6Sq45tz8GNlRTUx/A=
X-Google-Smtp-Source: ABdhPJzthDHdtgQqchBKy5euhhPnc9t7U+xwv/qZ5FQNQyeTh3XSmXmGkU/fQUvG+h9vUrZPXIgJD2MxPynrj1gBYgk=
X-Received: by 2002:a62:384c:0:b029:1e3:8bca:5701 with SMTP id f73-20020a62384c0000b02901e38bca5701mr1140232pfa.7.1613099387833; Thu, 11 Feb 2021 19:09:47 -0800 (PST)
MIME-Version: 1.0
References: <DM6PR02MB6924E3E2DD5568E247859E18C38C9@DM6PR02MB6924.namprd02.prod.outlook.com> <87blcqpau7.fsf@toke.dk> <E5F69D0C-7130-42D3-9080-C2EE5786D917@gmail.com> <878s7up8n0.fsf@toke.dk>
In-Reply-To: <878s7up8n0.fsf@toke.dk>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Thu, 11 Feb 2021 19:09:36 -0800
Message-ID: <CAPDSy+6YWPr81uKHrWYoY=TZ0A18A_Ui3=CyLP=1K-ezwmgF-g@mail.gmail.com>
To: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= <toke=40toke.dk@dmarc.ietf.org>
Cc: Mahesh Jethanandani <mjethanandani@gmail.com>, "STARK, BARBARA H" <bs7652@att.com>, "babel@ietf.org" <babel@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ffcfca05bb1af777"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/LtBpKLux05YiX5FvmZyBjUzokjk>
Subject: Re: [babel] proposed info model change
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2021 03:09:50 -0000

We banned all-zeroes and all-ones between draft-ietf-babel-rfc6126bis-00
and draft-ietf-babel-rfc6126bis-01. If memory serves, the idea was to
reserve them for future extensibility. Also, banning all-zeroes allows
using that as a sentinel value in software.

Adding the uniqueness requirement sounds good to me, but removing the ban
on all-zeroes/all-ones could lead to problems. If the core protocol doesn't
allow it, why should the informational model allow it?

David

On Thu, Feb 11, 2021 at 2:00 PM Toke Høiland-Jørgensen <toke=
40toke.dk@dmarc.ietf.org> wrote:

> Mahesh Jethanandani <mjethanandani@gmail.com> writes:
>
> > Hi Toke,
> >
> > The rational has to do with what a data model like YANG does with
> > router-id. To it the router-id is a key, in the form of a string. That
> > string has to be unique. YANG does not prevent it being a string of
> > zeros or ones, provided that string is unique. Thus the dropping of
> > the "MUST NOT” and the addition of “MUST”.
>
> Right. I seem to recall there being some other reason why it shouldn't
> be 0, but can't find the discussion now, and looking at the code that
> doesn't seem to care. So no objection from me I guess :)
>
> -Toke
>
> _______________________________________________
> babel mailing list
> babel@ietf.org
> https://www.ietf.org/mailman/listinfo/babel
>