Re: [CCAMP] Question on draft-zheng-ccamp-yang-otn-slicing-03

Aihua Guo <aihuaguo.ietf@gmail.com> Mon, 24 January 2022 17:01 UTC

Return-Path: <aihuaguo.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 7DE9E3A0A30 for <ccamp@ietfa.amsl.com>; Mon, 24 Jan 2022 09:01:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.477
X-Spam-Level:
X-Spam-Status: No, score=-0.477 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_IMAGE_ONLY_24=1.618, HTML_IMAGE_RATIO_04=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jIRDuFGtoxdo for <ccamp@ietfa.amsl.com>; Mon, 24 Jan 2022 09:01:50 -0800 (PST)
Received: from mail-oi1-x234.google.com (mail-oi1-x234.google.com [IPv6:2607:f8b0:4864:20::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 771AC3A0A24 for <ccamp@ietf.org>; Mon, 24 Jan 2022 09:01:49 -0800 (PST)
Received: by mail-oi1-x234.google.com with SMTP id y23so8137407oia.13 for <ccamp@ietf.org>; Mon, 24 Jan 2022 09:01:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rzdR1y0W5ZdYGsCzjGTqHFWo6hwIuBunYFhf2QvgqUw=; b=nJBoq3lflcAVJZhe3jF0yRLFYZiL2Pv0pPa5OS6cqTfuIcklDFrUgcviRIZMj96yZB tazCRqR2MevZbCTB9/cIkC5Hl9wN+H8mjsxDyM9PJs8EnTbxvHze25n3HAsvy/B6Q5fR AYSgccZaKLRuLBZTJpuwJoFnHKGe6buG4IiyXo8RJvnUdNhrmYw3h67mUvuXZX/dTNzK GZY05CV+/c91K1o28nMLdUw3y1+nvlT85y22di0sgZpyqH/QJyZPGWkbiTtbDfsqfFso vz81TcAXMuy5Ytq3RNMekqXMk9dZ9FFuaFHNEkbcyflwDs+AIbo67SrHwOJ59EATyeVs G9sw==
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=rzdR1y0W5ZdYGsCzjGTqHFWo6hwIuBunYFhf2QvgqUw=; b=C4xaRi+MMIXXTP6fVCuo1N9SVqvKdTMmjUZ6H0chWTEpluJAHiUs171uCqXrTmNWu7 xlcB6vdiUzENH8gnG7kSkOs41h/b+wcs8iQzvIBR+gEElobUTGn71KfixQkKCrFVP/0Q jX1y0FIFTU1ii2VzE1NFopFudxtphcHHuuMqaDpejnpMvCC4axSh8/9XUSuiQxqpSSe3 AoOp4aAbbPT2Trplv79sxuhk2C1eiaWL0wagee/VfYQvRUZi0VFvqr6n1gvAjpmiO0Im EtwuCwuraayR8w2OAr1IU+xH+fNThFDzjafSJMw4GiwK3CaIb7OyT70Z1oLGwRyKhAtP 1H7Q==
X-Gm-Message-State: AOAM532+nuTbqIpiTxMbTzyP/LTtSAzwzFLMqgZWFQUb2wb75moZ+iKG odS2NopweHOLk95+5MoPau/kmVdkxdxEu2U2ZXIi18C6
X-Google-Smtp-Source: ABdhPJysKmZ09EksAImskC8zMTbHZRYNdbl+mElT10iZLjMkDMIbYrJyQEG0gDKIgbr+QjGvjdSycW4LzvfuOGrkDD4=
X-Received: by 2002:a54:4809:: with SMTP id j9mr2219106oij.136.1643043707354; Mon, 24 Jan 2022 09:01:47 -0800 (PST)
MIME-Version: 1.0
References: <C15968C8-A7D0-4E53-B833-592E505D4553@ciena.com>
In-Reply-To: <C15968C8-A7D0-4E53-B833-592E505D4553@ciena.com>
From: Aihua Guo <aihuaguo.ietf@gmail.com>
Date: Mon, 24 Jan 2022 12:01:36 -0500
Message-ID: <CAFS+G6TDmTbY+pVstJ+ongoxcAm4etD2VdudFXNKMReRUi7Rkg@mail.gmail.com>
To: "Rokui, Reza" <rrokui@ciena.com>
Cc: CCAMP <ccamp@ietf.org>, Fatai Zhang <zhangfatai=40huawei.com@dmarc.ietf.org>
Content-Type: multipart/related; boundary="00000000000087526f05d656ec6f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccamp/Jy3RNb0LX01JiiLnFvCU-buI0iE>
Subject: Re: [CCAMP] Question on draft-zheng-ccamp-yang-otn-slicing-03
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 24 Jan 2022 17:01:55 -0000

Hi Reza,

Thank you for the comments. I agree with you that from the IETF NSC
perspective, OTN-SC can be seen as just an NS realizer for underlying OTN
technology. Additionally, OTN-SC could use the same interface to support
technology-specific slicing for OTN-aware customers. These points can be
captured in the next revision of the draft.

Thanks,
Aihua

On Mon, Jan 24, 2022 at 9:00 AM Rokui, Reza <rrokui@ciena.com> wrote:

> Hi AIhua,
>
>
>
> I would like to bring another item for discussion which is relationship
> between OTN-SC and following draft:
>
>    - draft-contreras-teas-slice-controller-models-01
>
>
>
> In this draft, the internal logic of an IETF Network Slice Controller has
> been discussed which shown in picture on left. There is one
> technology-specific functional block called “NS Realizer”.
>
> If you compare this with picture on right, it seems reasonable to assume
> OTN-SC is simply the NS Realizer for OTN technology.
>
>
>
> IMO, it would be helpful if this concept is captured in your draft to
> reflect this fact that OTN-SC is just a “NS Realizer” for OTN network.
>
>
>
> Cheers,
>
> Reza
>
>
>
>
>
> [image: Diagram Description automatically generated]
>