Re: [Isis-wg] [Bier] BAR field length in draft-ietf-bier-isis-extensions and draft-ietf-bier-ospf-extensions

Alia Atlas <akatlas@gmail.com> Tue, 20 February 2018 01:58 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20B62126BF3; Mon, 19 Feb 2018 17:58:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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_LOW=-0.7, 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 Vb7dqfdwEqPT; Mon, 19 Feb 2018 17:58:12 -0800 (PST)
Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::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 9E5B912008A; Mon, 19 Feb 2018 17:58:12 -0800 (PST)
Received: by mail-oi0-x22c.google.com with SMTP id f186so1460770oig.4; Mon, 19 Feb 2018 17:58:12 -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=1f77cLthezGFmZf+veYIcQ0wjC4j8XqCpPaGWfhmyGE=; b=dZbgpg96G9akTWCT7tmXqKExvqdW6G6LBdHcFO8Wlis8DWba5mfmOTIsR47KZIbYUt 8r1YBKg73nMBjmePeXdJC0mJWQmrwaKolr1NeVhLr80aeFAttU9oRJ3evNtPUr3/ljin P70jug82O1I5TbgRjt9vIIQMveVae5fIzEekiLloImpVHf8ABNpm2kYqitQjSu5S8Cmi aK89K2XyAPFbhV8J5EDERIr2X/y5/QmC9FDGLxQ2XIF/Z8Pwc1LRuzCiLnIL3p9YvhuG BH3aPYwFt7LwaSpE+PXG9p1rcqYU0pOSujkDIwtI1p3aJSlVIthg1FMJ/GP2OzBuZjF3 Vd5A==
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=1f77cLthezGFmZf+veYIcQ0wjC4j8XqCpPaGWfhmyGE=; b=eAJk0tVrmkREoNuC8Zhy73HNw/CAf1Nz2egOvzDM1BY8GT9Jsj6QXMmXXcEqC0BPjW 9wucrW0xFFowHnPekCg8kaZqsDs7Lt/ycgFdGbkFiSAiZczChqjdMhP3SB4h+JdOUwA3 8h86M5HyJ0bHCO+Y2/csQHcmh2YmPB3jILg1KIfellvlvMoOqUg4UGuBIkxeHRg4rHuL kjQv86IjiT7wzcTGBJDzrPl/x18VzFN+ijuP3AiRKNmmJXOAe9NBk3LfE7tfhlGad+cQ onsVo0/zSLTgm2EnCDIxbNDdNhMfBFrGzm61NEp5MHuarA1St2AuxTtrHHJ3EW/DzbM4 19UA==
X-Gm-Message-State: APf1xPCb0728l7/YL3niiAqoGhp66/VwfzK3aohEGfv5eSEA+i/nWywj yk5x2jreGWpKdZ5quuAuTs8U3TKkwOfrtTPdeG8=
X-Google-Smtp-Source: AH8x2251QhTsOjyWVHFz4pKu3mOIDjP/Csu+qPCeBZsYi6fAnXT/JJvxhHvioVBquJkciSLS8TqLKZkjoz1FrPyDJec=
X-Received: by 10.202.193.68 with SMTP id r65mr10779256oif.132.1519091891647; Mon, 19 Feb 2018 17:58:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.68.57 with HTTP; Mon, 19 Feb 2018 17:58:11 -0800 (PST)
In-Reply-To: <A13891D4-2F05-4956-9A77-9F98F0EFDCAE@cisco.com>
References: <CAG4d1remdUKutEdc2DU6Gaan3z63CAZVo1D-L0GXg_=eHJxffw@mail.gmail.com> <21151215-CF4E-42BD-8042-BAFDF75F54FB@cisco.com> <CAG4d1rf+ZKG=gpJPfBZx0O1Y4GP+GztL-p9yPhR9jn7uu370hA@mail.gmail.com> <03AF1119-86B0-4FB7-8D65-B378DB10CF48@cisco.com> <CAG4d1rftg0_VVhFPGB3jRfQhUVXj0druXzt4HkgcMNnqjgHpJQ@mail.gmail.com> <A13891D4-2F05-4956-9A77-9F98F0EFDCAE@cisco.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Mon, 19 Feb 2018 20:58:11 -0500
Message-ID: <CAG4d1rf6-FS=jZB5VD5SMQd7BMdOYY8Erh-xnseKkSGzEwQa5w@mail.gmail.com>
To: IJsbrand Wijnands <ice@cisco.com>
Cc: BIER WG <bier@ietf.org>, "isis-wg@ietf.org list" <isis-wg@ietf.org>
Content-Type: multipart/alternative; boundary="001a113cd1f89539cd05659b24c1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/isis-wg/K9_fD5WrvLsKubqa7rQp-o_3b2w>
Subject: Re: [Isis-wg] [Bier] BAR field length in draft-ietf-bier-isis-extensions and draft-ietf-bier-ospf-extensions
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Feb 2018 01:58:14 -0000

Ice,

At this point in the process, it would be necessary to make an overwhelming
technical argument - that would sway almost the whole
WG to your perspective.

I see you saying that you have a personal preference for having the IGP
Algorithm registry also be used for the BAR registry.   While
I do, of course, respect where you have technical expertise, my response -
particularly from a process perspective - is "that's nice".

Regards,
Alia

On Mon, Feb 19, 2018 at 8:15 PM, IJsbrand Wijnands <ice@cisco.com>; wrote:

> Alia,
>
> > An architectural argument can't also limit itself to the drafts in the
> title.
> >
> > If it sounded like the IANA registry was suggested as separate for BIER
> OSPF  and BIER ISIS, then your attempt to reframe the conversation might be
> reasonable.  Let me clarify - I see no current reason for an OSPF BAR
> registry and an ISIS BAR registry; it would just be a BAR registry.  Perhaps
> > that clarification is a good reason to get the IANA registry included in
> the next update?
>
> There is no reason for an individual BIER OSPF and BIER ISIS registry. The
> point is to align with what ever ISIS and OSPF are using to identify the
> algorithm.
>
> > The routing layer is separate from the BIER layer.  The BAR is for the
> BIER layer.
>
> The underlay is separate from the BIER layer, and each underlay can carry
> BIER specific information that is needed for for BIER to make the selection.
>
> Thx,
>
> Ice.
>
>