IETF Logo Mail Archive

[Teas] Re: [OPS-DIR]Re: Opsdir last call review of draft-ietf-teas-actn-vn-yang-26

Mahesh Jethanandani <mjethanandani@gmail.com> Sat, 08 June 2024 16:17 UTC

Return-Path: <mjethanandani@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 8F9B3C14F6A8; Sat, 8 Jun 2024 09:17:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-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 5WzK30qOythr; Sat, 8 Jun 2024 09:17:20 -0700 (PDT)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (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 0E454C14F5E8; Sat, 8 Jun 2024 09:17:20 -0700 (PDT)
Received: by mail-qk1-x72a.google.com with SMTP id af79cd13be357-7955af79812so14697685a.1; Sat, 08 Jun 2024 09:17:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717863439; x=1718468239; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=p1bp49kxp33OKNLZFxq+bpI1mJBfDAYUJwsO/pBcJ84=; b=nVNZBCyZMlTYSAXSum6d6VuP4vGaGxgibdxi7Qn6x25YgVzpQydTQJmYm2EcCYfofm hL2RakqIJ1Leb26OZvLLVS1jDO86Mr6KCutHinJHbT3Z6m5L2Zh/9ktqp9TZKXmqd74B pRQdxymdOiQrKCxTYmhSB3JjhqxaVI1k5KDRO89B+okJSAEnRzsQ23Ai92vBZWlP1XZm 4y+VeJhsEXGLm444oeKpHh045iJspbnAN9PzYZUpLcFy0FuZvSk4rIMQD/PgrbfF0J9B gcjHSUpyeyZ/cITcn4oxOUr4YvrhuvwfUjGgdmFm4LID8NfPpvQHB5CwRhP8phDBcatX sSZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717863439; x=1718468239; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=p1bp49kxp33OKNLZFxq+bpI1mJBfDAYUJwsO/pBcJ84=; b=mn647yd9hTvsIK3C1DQIOJLF4W8oPGLI5N8saSP5Pqj6No+/drGY2kqUTJ8+6pARZB u8VpRtfy618w0PYuE7N0u01mwcU7TPRMZ7tK9Lq8TXYpHA0B/fHoKIZEwWI6QTAQEaMe N13vQwzbJei1UPZ6TSnEmQ/nz0zCdNOp9X3CahW8sMVw5TRWVMmzAa8XA9g/G1nwoXra sZX1/AXB3OWd2dFXdnHzq3a9mMZbIvk4Qb0ihBuEXoDqqhLFy2mBmg9HJfU5rTw1cSKs kuecaajKeNGbtOM2+ZtDIbhFmTTUmjP5cU+1gBSLg11Qraal2thBy3Dh/MWzDL1252EF G+tA==
X-Forwarded-Encrypted: i=1; AJvYcCVfXmDfRjypQD1OZXibInDaPU1SIViBdNcDd0kjE9TQfCd1aump4NJPmxfsPJaIKk+jKKr44a/CQG/t7TB6hulhZapfkA3WbddpChw+6zO41N3vS2rgcPbCdUU1+V+KLyLiY8W5qf+I3kDyfUSEtGacvus/85w4LdfPvsVtTt9YafMsqCi6j0yvwXdqd4D5
X-Gm-Message-State: AOJu0YzmgOt4pqUwQtul05AXRoWHOTuAr02S6tOvvvW7fXBox3bnWf+F OKJT8TUmfr84nStrdF/yRwGFTbDtoATditYMXj2km8YP58ILZOcm
X-Google-Smtp-Source: AGHT+IHkBtE44aQebiFhwU2XN2E/JicNrrHMFDJBRsuX5Io7wtx5hAxaBmiMqqcEEkpzVEP8T8UjkA==
X-Received: by 2002:a05:620a:a97:b0:795:2377:a484 with SMTP id af79cd13be357-7953c63a866mr498627185a.32.1717863438715; Sat, 08 Jun 2024 09:17:18 -0700 (PDT)
Received: from smtpclient.apple (pool-72-79-60-137.nwrknj.east.verizon.net. [72.79.60.137]) by smtp.gmail.com with ESMTPSA id af79cd13be357-7954e5ab739sm114608085a.44.2024.06.08.09.17.16 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 08 Jun 2024 09:17:16 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <D2242790-3AFD-4661-9856-AF469B5FD807@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E173FC23-4716-4598-91A3-3F0135D9BD0D"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.15\))
Date: Sat, 08 Jun 2024 12:17:16 -0400
In-Reply-To: <CAB75xn6aJyxBrSbAAHk+GkvNiwLGrWGpXNhe76BU1U4p22SvwA@mail.gmail.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
References: <171757068446.34933.7846006565304880228@ietfa.amsl.com> <CAB75xn6aJyxBrSbAAHk+GkvNiwLGrWGpXNhe76BU1U4p22SvwA@mail.gmail.com>
X-Mailer: Apple Mail (2.3654.120.0.1.15)
Message-ID-Hash: 4XDCOIGAJQHPB3V5PU4YKB3NGBAB5YHQ
X-Message-ID-Hash: 4XDCOIGAJQHPB3V5PU4YKB3NGBAB5YHQ
X-MailFrom: mjethanandani@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-teas.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "Wubo (lana)" <lana.wubo@huawei.com>, ops-dir@ietf.org, draft-ietf-teas-actn-vn-yang.all@ietf.org, last-call@ietf.org, teas@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Teas] Re: [OPS-DIR]Re: Opsdir last call review of draft-ietf-teas-actn-vn-yang-26
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/ml3vG35zYRMIWl3fBoGMH0ntf8A>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Owner: <mailto:teas-owner@ietf.org>
List-Post: <mailto:teas@ietf.org>
List-Subscribe: <mailto:teas-join@ietf.org>
List-Unsubscribe: <mailto:teas-leave@ietf.org>

Hi Dhruv,

> On Jun 7, 2024, at 2:57 AM, Dhruv Dhody <dhruv.ietf@gmail.com> wrote:
> 
>  
> >From this sentence, it seems that LTP refers to the LTP in the native TE
> topology, because in YANG, PE is defined as the PE node in the native TE
> Topology. While in the YANG model and the Examples in B.1. VN JSON, it looks
> like "ltp" is the LTP within the abstract node, correct? If so, could the YANG
> path be modified to a relative path of the abstract node?
> 
> 
> Dhruv: Since the 'te-node-id' is not a key, it is not possible to change to relative path like "path "/nw:networks/nw:network/nw:node[tet:te-node-id=current()/../abstract-node]/nt:termination-point/tet:te-tp-id";"
> Instead I will update the description. 

I am not able to understand this comment. I understand that you cannot provide a path like you mention above, but at the same time, Wubo does make a good point. Which LTP is being referred to? The one in the underlying layer or in the abstract layer?


Mahesh Jethanandani
mjethanandani@gmail.com

v2.40.3 | Report a Bug | By Email | System Status