Re: [Lsr] Robert Wilton's No Objection on draft-ietf-lsr-ospf-l2bundles-06: (with COMMENT)
Ketan Talaulikar <ketant.ietf@gmail.com> Wed, 05 October 2022 05:19 UTC
Return-Path: <ketant.ietf@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 D7C2DC1524C9; Tue, 4 Oct 2022 22:19:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id beCI7V8Aq51M; Tue, 4 Oct 2022 22:18:58 -0700 (PDT)
Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (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 54EA8C14CE36; Tue, 4 Oct 2022 22:18:47 -0700 (PDT)
Received: by mail-vs1-xe2c.google.com with SMTP id a129so16786859vsc.0; Tue, 04 Oct 2022 22:18:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=VFs7j47y0mmdjZE6EnnwOclMnqkQlTz0KqKfD3+mE+k=; b=Kgo6zpyUeyU42JWZRKsyJZKRuZSWhb3A/Mc9xfkOYCwih7xtz3s3C4iasB1AFxaHgA fB7cLZaN9wytQO0YdHzfl0wBrwpd7V1e7bzWJLHl+aVYV4seMUEXOs6hl3hHjO3PEquA NOZCgU4CVXssUSBXcUZu0vxdP8gkIkf3QF3Z5/pMcRkqk7iKrGCjBFVdIPifWuqInrcF IJjJB5To+qCpNzofzCJcaPBwdHepqyNDG6F3xfjHbJT/dIwNbqbJsgwNB07+PuOtkdvZ ZypQhsnR+xg5LbQVteXRyHZoMcIKRzuYS5w5x9Z5FqWPLVw2Qhp1X/v68PonCXghzKnT L9kQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=VFs7j47y0mmdjZE6EnnwOclMnqkQlTz0KqKfD3+mE+k=; b=qs3+UfZz9fhu7oO+KvrJ5rY8Bqv31fvV7ukoLbJUwkTg3Qvhx5loZEjXE2lOn8qRYt 45CElIYpAQwxCe6TVy6AMryKRfDpwqJyU6FwW2FrGSEbGKtO7gqj+MbOtRflCbn1G1+H OiO9WxCudTcN6u+YZ2QT+co4fPsEnVZ1jAtvW+7yohKtMmeR0om91JFlmfhUrgNgiMCT EB2Z9N/pjMZAOuFv7zDbG8xUXiAvxdkk0ottvgzN0dg3Mj50/37+0Oey/ZgyNW+FpV6l o0ZiDboE9kf6PICCkW3Z8TIEFoB3cuTnw37O4g9ILuSG8ZkqhdtcpC9VMTNoUuhYPb/t 0oiw==
X-Gm-Message-State: ACrzQf0KihWx6jOZvxyX2A2tnqrGN66s+Osa3oDEhi1nrTzH7WP9cOVs 8VcZYJLQWDjnMS1Se7J84tdkt7G4IXK7UikFFUd683nN/8c=
X-Google-Smtp-Source: AMsMyM7k+PT3bWhESIH/HwSiRKgyLQ34343UHvWXkid/EkYfWbEEIcQ37vRqKFfafDUAkeAqhgbqY7D+Hndxhggiqhg=
X-Received: by 2002:a67:c104:0:b0:3a6:c886:5aac with SMTP id d4-20020a67c104000000b003a6c8865aacmr2483633vsj.64.1664947126140; Tue, 04 Oct 2022 22:18:46 -0700 (PDT)
MIME-Version: 1.0
References: <166487665151.52178.16157705231314687692@ietfa.amsl.com> <CAH6gdPzJjEGcfADt7tP=rRzogQWagboCki2KVJAQJTfJDyzdRg@mail.gmail.com> <B6218AAC-7E54-48AA-B5CB-39E6A9FBF80B@cisco.com> <CAH6gdPxWCxQx8JDsjw1TdfTmU1-zGZKovpvAgH=5VTo2kcQzYw@mail.gmail.com> <7B58A161-BE20-477D-AA93-62AB6A557EA7@cisco.com> <BY5PR11MB41961392F6184EB379B31257B55A9@BY5PR11MB4196.namprd11.prod.outlook.com> <A057E559-3297-4DF9-B366-8B10D61CACE5@cisco.com>
In-Reply-To: <A057E559-3297-4DF9-B366-8B10D61CACE5@cisco.com>
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Date: Wed, 05 Oct 2022 10:48:34 +0530
Message-ID: <CAH6gdPz68czkaYfG1gKVm=6-MffO=shZVJM3iQf2a35cey7Q9g@mail.gmail.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
Cc: "Rob Wilton (rwilton)" <rwilton@cisco.com>, The IESG <iesg@ietf.org>, "draft-ietf-lsr-ospf-l2bundles@ietf.org" <draft-ietf-lsr-ospf-l2bundles@ietf.org>, "lsr-chairs@ietf.org" <lsr-chairs@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>, "chopps@chopps.org" <chopps@chopps.org>
Content-Type: multipart/alternative; boundary="00000000000006027b05ea42b67a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/E0YL8vQq4BTrF2R7wXX9AvNYJi8>
Subject: Re: [Lsr] Robert Wilton's No Objection on draft-ietf-lsr-ospf-l2bundles-06: (with COMMENT)
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 05 Oct 2022 05:19:01 -0000
Hi Rob/Acee, Thanks for your suggestions. We've just posted an update with the changes as discussed: https://datatracker.ietf.org/doc/html/draft-ietf-lsr-ospf-l2bundles-07 Thanks, Ketan On Tue, Oct 4, 2022 at 10:27 PM Acee Lindem (acee) <acee@cisco.com> wrote: > Hi Rob, > > > > *From: *"Rob Wilton (rwilton)" <rwilton@cisco.com> > *Date: *Tuesday, October 4, 2022 at 11:51 AM > *To: *Acee Lindem <acee@cisco.com>, Ketan Talaulikar < > ketant.ietf@gmail.com> > *Cc: *The IESG <iesg@ietf.org>, "draft-ietf-lsr-ospf-l2bundles@ietf.org" < > draft-ietf-lsr-ospf-l2bundles@ietf.org>, "lsr-chairs@ietf.org" < > lsr-chairs@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>, Christian Hopps < > chopps@chopps.org> > *Subject: *RE: Robert Wilton's No Objection on > draft-ietf-lsr-ospf-l2bundles-06: (with COMMENT) > > > > Hi Acee, Ketan, > > > > One other alternative could be to add an Informative reference to the base > OSPF YANG module (that is about to be an RFC), and indicate that the > configuration is expected to be an update or augmentation to that base OSPF > YANG module? > > > > That would be better. > > > > Is there somewhere for these new config knobs are being tracked - so that > they don’t get forgotten? > > > > We have the Datatracker for that… > > > > Thanks, > > Acee > > > > Thanks, > > Rob > > > > > > > > *From:* Acee Lindem (acee) <acee@cisco.com> > *Sent:* 04 October 2022 16:13 > *To:* Ketan Talaulikar <ketant.ietf@gmail.com> > *Cc:* Rob Wilton (rwilton) <rwilton@cisco.com>; The IESG <iesg@ietf.org>; > draft-ietf-lsr-ospf-l2bundles@ietf.org; lsr-chairs@ietf.org; lsr@ietf.org; > chopps@chopps.org > *Subject:* Re: Robert Wilton's No Objection on > draft-ietf-lsr-ospf-l2bundles-06: (with COMMENT) > > > > Hi Ketan, > > > > *From: *Ketan Talaulikar <ketant.ietf@gmail.com> > *Date: *Tuesday, October 4, 2022 at 10:44 AM > *To: *Acee Lindem <acee@cisco.com> > *Cc: *"Rob Wilton (rwilton)" <rwilton@cisco.com>, The IESG <iesg@ietf.org>, > "draft-ietf-lsr-ospf-l2bundles@ietf.org" < > draft-ietf-lsr-ospf-l2bundles@ietf.org>, "lsr-chairs@ietf.org" < > lsr-chairs@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>, Christian Hopps < > chopps@chopps.org> > *Subject: *Re: Robert Wilton's No Objection on > draft-ietf-lsr-ospf-l2bundles-06: (with COMMENT) > *Resent-From: *<alias-bounces@ietf.org> > *Resent-To: *Yingzhen Qu <yingzhen.ietf@gmail.com>, Christian Hopps < > chopps@chopps.org>, Acee Lindem <acee@cisco.com> > *Resent-Date: *Tuesday, October 4, 2022 at 10:44 AM > > > > Hi Acee, > > > > Thanks for your quick response. > > > > My question was : Can we put an informative reference to > https://datatracker.ietf.org/doc/draft-ietf-lsr-ospf-yang-augmentation-v1/ > (of which you are co-author) in the OSPF L2 Bundles draft? > > > > This assumes that an upcoming version of this augmentation-v1 draft will > cover the configuration/enablement of this feature. > > > > We also would need to update the Link State Database for the advertisement > of the individual links. I think you can just say a future YANG draft as > the reference Is not mandatory. > > > > Thanks, > > Acee > > > > > > > > Thanks. > > Ketan > > > > > > On Tue, Oct 4, 2022 at 8:07 PM Acee Lindem (acee) <acee@cisco.com> wrote: > > Hi Ketan, > > > > See inlie. > > > > *From: *Ketan Talaulikar <ketant.ietf@gmail.com> > *Date: *Tuesday, October 4, 2022 at 10:23 AM > *To: *"Rob Wilton (rwilton)" <rwilton@cisco.com> > *Cc: *The IESG <iesg@ietf.org>, "draft-ietf-lsr-ospf-l2bundles@ietf.org" < > draft-ietf-lsr-ospf-l2bundles@ietf.org>, "lsr-chairs@ietf.org" < > lsr-chairs@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>, Christian Hopps < > chopps@chopps.org>, Acee Lindem <acee@cisco.com> > *Subject: *Re: Robert Wilton's No Objection on > draft-ietf-lsr-ospf-l2bundles-06: (with COMMENT) > > > > Hi Rob, > > > > Thanks for your review and please check inline below for responses. > > > > The updates as discussed below will be included in the next update. > > > > > > On Tue, Oct 4, 2022 at 3:14 PM Robert Wilton via Datatracker < > noreply@ietf.org> wrote: > > Robert Wilton has entered the following ballot position for > draft-ietf-lsr-ospf-l2bundles-06: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to > https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ > for more information about how to handle DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-lsr-ospf-l2bundles/ > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Hi, > > I support Lars's discuss. > > I don't really object to publishing this document, although I don't really > like > the fact that the LAG member information that is being propagated isn't of > any > relevance to OSPF routing itself, and OSPF is being used only as a generic > information propagation mechanism. However, I acknowledge that horse has > probably bolted long ago. > > > > KT> What we are doing here is adding more information for use in the TE-DB > that is related to OSPF adjacencies. Originally, Opaque LSAs were > introduced in OSPF for carrying additional info for TE-DB - even though > that info was not really consumed by OSPF protocol. I can understand that > "the line" may be blurred in this respect. > > > > > One point that is not clear to me, is the configuration/management of this > feature: Is the expectation that OSPF implementations that support this > RFC > would automatically propagate bundle member information? Or would this be > disabled by default and need to be enabled through configuration? > > > > KT> There should not be automatic enablement. It needs to be enabled via > configuration. We will add an Operational Considerations section to clarify > this with the following text added: > > > > <NEW> > > Implementations MUST NOT enable the advertisement of Layer 2 bundle member > links and their attributes in OSPF LSAs by default and MUST provide a > configuration option to enable their advertisement on specific links. > > </NEW> > > > > If there is > configuration associated with this feature then would it be part of a > updated > version of the standard OSPF YANG model, or is it via YANG module > augmentation > to the base OSPF YANG module? > > > > KT> I would expect the enablement to be an augmentation to the base OSPF > YANG model. > > > > If this is configurable then having an > informational reference to how/where this OSPF feature can be configured > would > likely be helpful. > > > > KT> We do not currently have this covered. I believe this can be added in > https://datatracker.ietf.org/doc/draft-ietf-lsr-ospf-yang-augmentation-v1/ > - however, this is not something that has been discussed in the WG or with > the authors of this document. > > > > Acee/Yingzhen, if you agree that the OSPF YANG augmentation draft can > cover this, then we can add a reference in this document. > > > > The OSPF YANG model (as has been the case with all the protocol YANG > models) has been a moving target for years in terms of features, YANG > types, and YANG conventions. At this point, it will soon be published as > RFC 9129. New features will be included in follow-on drafts including > https://datatracker.ietf.org/doc/draft-ietf-lsr-ospf-yang-augmentation-v1/ > which would be a better reference. > > > > Thanks, > Acee > > > > > > Thanks, > > Ketan > > > > > Regards, > Rob > >
- [Lsr] Robert Wilton's No Objection on draft-ietf-… Robert Wilton via Datatracker
- Re: [Lsr] Robert Wilton's No Objection on draft-i… Ketan Talaulikar
- Re: [Lsr] Robert Wilton's No Objection on draft-i… Acee Lindem (acee)
- Re: [Lsr] Robert Wilton's No Objection on draft-i… Ketan Talaulikar
- Re: [Lsr] Robert Wilton's No Objection on draft-i… Acee Lindem (acee)
- Re: [Lsr] Robert Wilton's No Objection on draft-i… Rob Wilton (rwilton)
- Re: [Lsr] Robert Wilton's No Objection on draft-i… Acee Lindem (acee)
- Re: [Lsr] Robert Wilton's No Objection on draft-i… Ketan Talaulikar
- Re: [Lsr] Robert Wilton's No Objection on draft-i… John Scudder
- Re: [Lsr] Robert Wilton's No Objection on draft-i… Acee Lindem (acee)