Re: [Teas] WG Last Call: draft-ietf-teas-actn-vn-yang-19

Dhruv Dhody <dhruv.ietf@gmail.com> Tue, 24 October 2023 04:31 UTC

Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4756CC151533; Mon, 23 Oct 2023 21:31:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 DeNF5LJI6MOR; Mon, 23 Oct 2023 21:31:46 -0700 (PDT)
Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (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 52725C151536; Mon, 23 Oct 2023 21:31:46 -0700 (PDT)
Received: by mail-vs1-xe29.google.com with SMTP id ada2fe7eead31-457cb2fe3abso1700139137.3; Mon, 23 Oct 2023 21:31:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698121905; x=1698726705; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=c6+NR0dvMTdrGYquqpBcaNN5kuXR7NHH4NmjtUnPFnU=; b=ZpuhzV0ckAu5bHU/3FhOjhbuMtXQMP+ZqC3iOfszNGzog4Y8l2xg3+5Ju8EXA6+Brg nNXSzT1kkUsJ57oS9u7S/gyLFZ4n/R6h1drrwm9Fl47suxXrZXfgtVcNWqcuuALEDu7V mysUeLLYuIGaSLX/OOPlNh3I3U5opHq+6Gn2ebP3tmFC3xuqgJ8yH7ellC3lvPPViFVy IXZMsxfOuMRE9mhXXU5gfuB/2jESmXSeqzCjzn760PJVOjxocjvpCDocHypgc9m9akLh n5q3o0vfMRNArq0lCnV4II0V7KDEY2T1pSrGQOKh9YGy34ozBBTsBCar1wztFNM44Q1R TDqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698121905; x=1698726705; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=c6+NR0dvMTdrGYquqpBcaNN5kuXR7NHH4NmjtUnPFnU=; b=c9ifRCxa9kF9/t+I0yZ9QTP0lCa6WoVMGPs8GmfdBMH2oZhPKdStUzVzl71UEOXMBL XlgsjV1osIt2M9gaTcW2ow9v+rgeJZ0BV5HrP6N+cKJP9PDQkXzMB61ZuFiOTDf8leTh mHGmXjEDWikojagS6f+ZcAEaQWyZX+pgzEqC8z7mt3aJxmS7BSmlia2sWObjeQtY2Dqu 5JH1n585MS0GvMvJgPfqZPVSSZpGBlXpkhhRh3ws9u30k3YCQ5d7eGdYipeOXSlYQ66U JlWwjjypxrZjG5rOtlFqb+yMYtrPKwQqw87klGauyCJvkx6oLfz/j2yyZxlZRPdNnljO ZdYw==
X-Gm-Message-State: AOJu0YxdPSCaiKFSRJNIAPxZ1ucyity01JiMcWOQgZLwkbYXkvmb8BSr i3npV+WtCXPN2t1xcp7YA3Xq1nqwRhVDW/cFs5M=
X-Google-Smtp-Source: AGHT+IEn/yhm7q7hTXSc28/ukI3L+BTJBBxfR8UvobGMHBwq6zKsxXnX9h5DSGXwKQ2Dmqgox26CM8O7Sl9Gc9WdG5s=
X-Received: by 2002:a05:6102:204e:b0:457:d3ef:cbe5 with SMTP id q14-20020a056102204e00b00457d3efcbe5mr10399441vsr.20.1698121904725; Mon, 23 Oct 2023 21:31:44 -0700 (PDT)
MIME-Version: 1.0
References: <f8a1c7632aca4c09808782639632664c@huawei.com> <CAB75xn4XcMn0u-fKb49V67uV8GJCUOX6dGwgq517LO-Sc9xKkw@mail.gmail.com> <afce4aa0bd644e72ac86b26dc2636653@huawei.com> <CAB75xn7CrR3Yoir_nQ4KZN7PR4ogZmjuHXgrmWdR4tt-7E=i2A@mail.gmail.com> <a497cd2c9a2245579ab8e5eaa5a939a1@huawei.com>
In-Reply-To: <a497cd2c9a2245579ab8e5eaa5a939a1@huawei.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Tue, 24 Oct 2023 09:31:07 +0500
Message-ID: <CAB75xn7znYptcP=f6ZQ9S8YQ3pRqY_WevChwzvednOjtRat_zw@mail.gmail.com>
To: "Wubo (lana)" <lana.wubo@huawei.com>
Cc: Vishnu Pavan Beeram <vishnupavan@gmail.com>, TEAS WG <teas@ietf.org>, TEAS WG Chairs <teas-chairs@ietf.org>, Qin Wu <bill.wu@huawei.com>
Content-Type: multipart/alternative; boundary="000000000000eaa61906086ed088"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/nmwU6uStJFWpA5n3ft4ivLXZry0>
Subject: Re: [Teas] WG Last Call: draft-ietf-teas-actn-vn-yang-19
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Oct 2023 04:31:50 -0000

Hi Bo,

On Tue, Oct 24, 2023 at 8:53 AM Wubo (lana) <lana.wubo@huawei.com> wrote:

> Hi Dhruv,
>
>
>
> Thanks for the reply.
>
> For type 1 and type 2, all components, including VNs, VNAPs, and
> VN-members, are mapped to relevant nodes in the TE topology. So I think
> “vn-type” is useful for the CNC to determine the operations of TYPE1 and
> TYPE2. Otherwise, the TE topology always needs to be queried before the
> operations. And per the definition of VN, the VN type seems a key attribute
> of the VN.
>
>
>

The elements in this model - VN, VNAPs, VN-members remain the same for both
type 1 and type 2 i.e. you will not find any difference in how they are
set. Checkout VN1 and VN2 in JSON in Section 7.1. The difference is
primarily in the referred TE topology model. Look for underlay in the
abstract2 network and compare it with abstract1. Since this is coming from
CNC itself there is no need for any query.

Hope this clarifies...

Thanks!
Dhruv



> Thanks,
>
> Bo
>
>
>
> *From:* Dhruv Dhody <dhruv.ietf@gmail.com>
> *Sent:* Tuesday, October 24, 2023 11:27 AM
> *To:* Wubo (lana) <lana.wubo@huawei.com>
> *Cc:* Vishnu Pavan Beeram <vishnupavan@gmail.com>; TEAS WG <teas@ietf.org>;
> TEAS WG Chairs <teas-chairs@ietf.org>; Qin Wu <bill.wu@huawei.com>
> *Subject:* Re: [Teas] WG Last Call: draft-ietf-teas-actn-vn-yang-19
>
>
>
> Hi Bo,
>
>
>
>
>
>
>
> On Tue, Oct 24, 2023 at 8:18 AM Wubo (lana) <lana.wubo@huawei.com> wrote:
>
> Hi Dhruv,
>
>
>
> Thanks for addressing my comments.
>
> I have one more question: Is there an explicit way to know the setting of
> VN type1 and VN type2? For example, “vn-type”? Or do these two types not
> need to be distinguished and can be switched in the realization?
>
>
>
>
>
> Good question! As one of our aims was to keep this model generic (at the
> same time fully applicable to ACTN), we decided to not include an explicit
> VN-type and let that be implicit based on the TE topology details set by
> the CNC. If the CNC provides an underlay path in TE-topology's connectivity
> matrix, it is Type 2, otherwise it is type 1.
>
>
>
> Thanks!
>
> Dhruv
>
>
>
> Thanks,
>
> Bo
>
>
>
> *From:* Dhruv Dhody <dhruv.ietf@gmail.com>
> *Sent:* Monday, October 23, 2023 1:42 PM
> *To:* Wubo (lana) <lana.wubo@huawei.com>
> *Cc:* Vishnu Pavan Beeram <vishnupavan@gmail.com>; TEAS WG <teas@ietf.org>;
> TEAS WG Chairs <teas-chairs@ietf.org>; Qin Wu <bill.wu@huawei.com>
> *Subject:* Re: [Teas] WG Last Call: draft-ietf-teas-actn-vn-yang-19
>
>
>
> Hi Bo,
>
>
>
> Thanks for your review...
>
>
>
> On Thu, Oct 19, 2023 at 9:58 AM Wubo (lana) <lana.wubo=
> 40huawei.com@dmarc.ietf.org> wrote:
>
> Hi all,
>
>
>
> Sorry for the late reply. I support WGLC. I have reviewed the document and
> have a few minor editorial comments:
>
> 1. Figure 2 and 3: The basic components of the VN are AP/VNAP and
> vn-member. If the mapping between L1-L8 and AP/VNAP can be showed in Figure
> 2 and Figure 3, it is more clear to me to understand the relationship of VN
> and abstract node (AN).
>
>
>
> Dhruv: Since these examples are focusing on single VN, I don't think there
> would be any added advantage.
>
>
>
>
>
> 2. YANG model: It is recommended that the “abstract-node“ under ”vn-ap”
> to add some description on what scenarios is needed, which seems redundant
> with ‘ltp’.
>
>
>
> Dhruv: A reference to the abstract topology makes the correlation easier
> and it is not mandatory.
>
>
>
>
>
> 3. JSON Example: The text description of VN3 (Type 1) does not correspond
> to the JSON example. It seems to me:
>
> OLD:
>
> VN Member: 104 (L1 to L4)/107 (L1 to L7) {multi-dest}
>
> VN Member: 204 (L2 to L4)/304 (L3 to L4) {multi-src}
>
> NEW:
>
> VN Member: 103 (L1 to L3)/107 (L1 to L7) {multi-dest}
>
> VN Member: 108 (L1 to L8)/308 (L3 to L8) {multi-src}
>
>
>
>
>
> Dhruv: I updated the text and JSON as well to reflect the example
> correctly. Thanks for spotting this!
>
>
>
> Regards,
>
> Dhruv
>
>
>
>
>
> Thanks,
>
> Bo
>
>
>
> *发件人:* Teas <teas-bounces@ietf.org> *代表 *Vishnu Pavan Beeram
> *发送时间:* 2023年9月12日 20:19
> *收件人:* TEAS WG <teas@ietf.org>
> *抄送:* TEAS WG Chairs <teas-chairs@ietf.org>
> *主题:* [Teas] WG Last Call: draft-ietf-teas-actn-vn-yang-19
>
>
>
> All,
>
> This starts a two-week working group last call on
>
> https://datatracker.ietf.org/doc/draft-ietf-teas-actn-vn-yang/
>
>
>
> The working group last call ends on September 26th, 2023.
>
> Please send your comments to the working group mailing list.
>
> Positive comments, e.g., "I've reviewed this document
> and believe it is ready for publication", are welcome!
> This is useful and important, even from authors.
>
> Note: IPR has been disclosed on this document
>
>
> Thank you,
> Pavan, Lou and Oscar
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>
>