Re: [Lsr] Working Group Last Call on "Advertising L2 Bundle Member Link Attributes in OSPF" - draft-ietf-lsr-ospf-l2bundles-03

Anoop Ghanwani <anoop@alumni.duke.edu> Fri, 06 May 2022 18:05 UTC

Return-Path: <ghanwani@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 EC11EC157B5E; Fri, 6 May 2022 11:05:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level:
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 TiBum-vNaZAW; Fri, 6 May 2022 11:05:29 -0700 (PDT)
Received: from mail-qk1-f175.google.com (mail-qk1-f175.google.com [209.85.222.175]) (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 853C5C157B37; Fri, 6 May 2022 11:05:29 -0700 (PDT)
Received: by mail-qk1-f175.google.com with SMTP id s4so6476331qkh.0; Fri, 06 May 2022 11:05:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=r4EIgjsR4PQbKSuxbfEljhrqCOQ8v0CtNLdD1Nyy6OM=; b=eam+/Y46VYsN+S8kpxYDOWuheybN6NiAq3lD9QuZgx/nn9sW047JOmakTuwGIQ7nDj onpo9c5Q+pvrhjCEKaRo6TeBUTkQPy0Scfmu+FXwBNdb9GlfnPEiRdnxzJ8+JCm+PaZv M1LOLv27W5hYJETmTlHy74GVcSQ/3fmO5elZtpHFbv9tLBgOCSLumZWEJdA4iRu3gNPY QvGVdwF1mCVHfNrPKwOPwHVxGfkuihfbOwnOhYB5/W5eaX9IaR6PAla7SOAVPCcw+iFT crJkRa5hntc29iQbDsBLtHw3pwUDG0ZgB/dsv2sZmrUIReWYxjrYqUq8V4AxG/GR2cSn 8hRA==
X-Gm-Message-State: AOAM5333iLkUfdvHZfvoDnHSkOH9/TIN04M33B205AG7lB3nIA802whf mS4N9+xcsazYT6NKDTyIFxMF7jzGOtofXRdtTzmh9zaA
X-Google-Smtp-Source: ABdhPJwlxOhgsSfeWjzZXYxErcUBiESigXXc6hMjzLuPUYCk2yIJImvq+S74/GbpsG78pztkx+uAtgkNZl+fqJSJASQ=
X-Received: by 2002:a37:4d4:0:b0:69f:cc67:6f89 with SMTP id 203-20020a3704d4000000b0069fcc676f89mr3239777qke.61.1651860328575; Fri, 06 May 2022 11:05:28 -0700 (PDT)
MIME-Version: 1.0
References: <552AD876-AF65-48B5-B7DC-C85266BDD4E5@cisco.com>
In-Reply-To: <552AD876-AF65-48B5-B7DC-C85266BDD4E5@cisco.com>
From: Anoop Ghanwani <anoop@alumni.duke.edu>
Date: Fri, 06 May 2022 11:05:17 -0700
Message-ID: <CA+-tSzyYY+f31rKfq=PQB5QwFpYbFUJFxgTCh6K63hg3FeXGRg@mail.gmail.com>
To: "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>
Cc: "lsr@ietf.org" <lsr@ietf.org>, "draft-ietf-lsr-ospf-l2bundles@ietf.org" <draft-ietf-lsr-ospf-l2bundles@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001a76dd05de5bb43d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/lSNcIwMkdbsbzjv7gOdjvbFjbS0>
Subject: Re: [Lsr] Working Group Last Call on "Advertising L2 Bundle Member Link Attributes in OSPF" - draft-ietf-lsr-ospf-l2bundles-03
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.34
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: Fri, 06 May 2022 18:05:32 -0000

If I have router R1 connected to an L2 switch by an L2 bundle, and router
R2 connected to that L2 switch by a single link, is it still OK to
configure R1 to send L2 Bundle Member Link Attributes?  I think it would be
helpful to include that clarification in the draft.

On Thu, May 5, 2022 at 10:51 AM Acee Lindem (acee) <acee=
40cisco.com@dmarc.ietf.org> wrote:

> This begins a Working Group Last Call for draft-ietf-lsr-ospf-l2bundles.
> While there hasn’t been as much discussion as I would like on the draft,
>  it is filling a gap in OSPF corresponding to IS-IS Link Bundles (RFC
> 8668).  Please review and send your comments, support, or objection to this
> list before 12 AM UTC on May 20th, 2022.
>
>
>
> Thanks,
>
> Acee
>
>
>
>
>
>
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>