IETF Logo Mail Archive

Re: [CCAMP] Do we need a definition for the term "T-NBI"..?

Daniele Ceccarelli <daniele.ietf@gmail.com> Wed, 27 March 2024 08:30 UTC

Return-Path: <daniele.ietf@gmail.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E21ABC14F749; Wed, 27 Mar 2024 01:30:57 -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=unavailable 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 PRtTVqi4T1Rt; Wed, 27 Mar 2024 01:30:57 -0700 (PDT)
Received: from mail-ua1-x933.google.com (mail-ua1-x933.google.com [IPv6:2607:f8b0:4864:20::933]) (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 30BF8C14EB17; Wed, 27 Mar 2024 01:30:52 -0700 (PDT)
Received: by mail-ua1-x933.google.com with SMTP id a1e0cc1a2514c-7dec16fc4b2so1542356241.3; Wed, 27 Mar 2024 01:30:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711528251; x=1712133051; 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=NImXGdUSINRO36ra2SNL+W2UPmbiCSBMsoH96LGAI7U=; b=KeIopS+uEs4/fpxPJDGzDQAjU3tZvjshjyYrDngnhCmCe5Q+a9cGtSH/LQ0vR8uPs3 vmweJoHfuM/Fy8K4j04GWucQ4l+Fc97SdYpgx+DwO4OOUp3lshGcne13xDxLvhlwd9Qr /zgc+n6M57M28H+Ng0ltAQ7+GeWr9dWno7znNzDU/i9D09tRZ2hwlgn7oujP6xgpP8Hx 1q0rV5Fy62HqOHR0ISnC8mVpVbF48olA02pdDxmZeo1xaeks0PPKwElkk3hJMG2BpSJn 2DrqkFdLpDbxeSXyDAJNQ2KtPhXa7VEz7JnQ68pVrgpjJCPdhGobhi1pbX0JzF8tVs59 kBqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711528251; x=1712133051; 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=NImXGdUSINRO36ra2SNL+W2UPmbiCSBMsoH96LGAI7U=; b=U7a91PD8xGCQSzpou55Z5AsXxitTsucOBWcGRGxVtftiRWzHMb3d99e0rNZkdmWwvQ iWOqZRif32KfxhyTxKkek377+ew/mp5ZrbVq5FFJqg9UmrMePsqToVJMmCArsKFDSoym yIsAO6uQOmZ6EOjWRrX+MfUhLvlYrhVDTis7kQYyZGZjVqdwUuLyrZxe/2II3vqGuB54 cPG/ZlDi8jZhSclnEV4i3haF3Zxg5BSOpLoS0LW1/mCftIrBLJag3pIMQtL769EtqiUp v2Uadglci53FiRlXblBWIUOyer8ibKiFCrdTIz1kd3Sz5wf8eQ7L/TI0jFuRQ8BTfR3R lsxw==
X-Forwarded-Encrypted: i=1; AJvYcCWnGx9U0AKw2C15hxnWA89rJXmY1uI1qessycsAL1XVXz66XPson8lMx8JUsNz+NqCOHNjd4rqh85L0cLh08pOT2nm68BOWZSYu
X-Gm-Message-State: AOJu0YwaaJbhGgaucnNlw3D+pIlm4GSQWP8cDU7Gqe53PvFXzgS7edeV EWC7cbsxZ8t9DLTzbLMWAK2Ix6/i7meq0UbhocAkX0vG7VoJkrtIWYKkW2AN6tFwZn2HtdtVQPU VsA8apAcEgoOlvNHi8LXPpTUKbSk5vgfEAJB/1u83
X-Google-Smtp-Source: AGHT+IE79Me0rA4RS50OJhrYa3iiYs0Ho7yEYI7coHa6DAenMx7eWb7z1yMBVdE3ZUqUKOB3CrbUE/I2c5G9nFmhMqM=
X-Received: by 2002:a05:6122:459b:b0:4d4:1b6a:7924 with SMTP id de27-20020a056122459b00b004d41b6a7924mr2206570vkb.8.1711528250783; Wed, 27 Mar 2024 01:30:50 -0700 (PDT)
MIME-Version: 1.0
References: <180bce4510e1440384c96acdf5d6c958@huawei.com>
In-Reply-To: <180bce4510e1440384c96acdf5d6c958@huawei.com>
From: Daniele Ceccarelli <daniele.ietf@gmail.com>
Date: Wed, 27 Mar 2024 09:30:39 +0100
Message-ID: <CAB01kMgNrG-x+Nu087xan74y67idC5KU5uQz4XzFLvMpUKdPfg@mail.gmail.com>
To: Italo Busi <Italo.Busi=40huawei.com@dmarc.ietf.org>
Cc: "ccamp@ietf.org" <ccamp@ietf.org>, "transport-nbi-dt@ietf.org" <transport-nbi-dt@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006940070614a039ba"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/zhiCifjLNx5OfkBGQz1O4MZv17Q>
Subject: Re: [CCAMP] Do we need a definition for the term "T-NBI"..?
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Mar 2024 08:30:58 -0000

Hi Italo,

this looks really good to me. Please find below the text with some minor
edits.
Thanks
Daniele
The optical transport domain is designed to support various connectivity
services, such as Wavelenght Division Multiplexing (WDM) and the Optical
Transport Network (OTN). A primary objective for network operators is to
automate the establishment of these services in single-layer as well as complex
hierarchical, multi-domain transport networks. Exposing capability and
infrastructure assets is crucial to providing access to network resources
and offering advanced control and manageability features. Optical transport
Application Programming Interfaces (APIs) becomes essential to achieve this.
The "Transport Northbound Interface" (T-NBI) refers to those APIs.  are
well-defined, open interfaces vital for network operators. They provide the
capability to view  manage optical transport resources and effectively
operate multi-vendor and multi-domain networks. Furthermore, the T-NBI API
is instrumental in facilitating the coordination and automation of service
provisioning, thereby enhancing efficiency and operational flexibility when
managing optical network resources.

On Fri, Mar 22, 2024 at 2:01 AM Italo Busi <Italo.Busi=
40huawei.com@dmarc.ietf.org> wrote:

> As discussed during the CCAMP WG session today, we are looking for some
> feedbacks from the WG about this open issue we are discussing in the
> context of the TNBI DT:
>
> *https://github.com/ietf-ccamp-wg/transport-nbi/issues/115*
> <https://github.com/ietf-ccamp-wg/transport-nbi/issues/115>
>
> The initial definition (to be improved) we are considering is the
> following:
>
> The optical transport domain is designed to support various connectivity
> services, such as Wave Division Multiplexing (WDM) and the Optical
> Transport Network (OTN). A primary objective for network operators is to
> automate the establishment of these services in single-layer and complex
> hierarchical, multi-domain optical transport networks. Exposing capability
> and infrastructure assets are crucial to providing access to network
> resources and offering advanced control and manageability features. Optical
> transport Application Programming Interface (API) becomes essential to
> achieve this.
> The "Transport Northbound Interface" (T-NBI) API are well-defined, open
> interfaces vital for network operators. They provide the capability to view
> optical transport resources and effectively operate multi-vendor and
> multi-domain networks. Furthermore, the T-NBI API is instrumental in
> facilitating the coordination and automation of service provisioning,
> thereby enhancing efficiency and operational flexibility when managing
> optical network resources.
> Do you have any comments or suggestions on how to improve this definition?
>
> Thanks, Italo
>
>
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>

v2.23.0 | Report a Bug | By Email