Re: [Teas-ns-dt] Comments to the ACTN reference in the framework document during today's call

LUIS MIGUEL CONTRERAS MURILLO <luismiguel.contrerasmurillo@telefonica.com> Fri, 06 March 2020 15:20 UTC

Return-Path: <luismiguel.contrerasmurillo@telefonica.com>
X-Original-To: teas-ns-dt@ietfa.amsl.com
Delivered-To: teas-ns-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96C473A0908 for <teas-ns-dt@ietfa.amsl.com>; Fri, 6 Mar 2020 07:20:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=telefonica.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 gpp15qi_ooTf for <teas-ns-dt@ietfa.amsl.com>; Fri, 6 Mar 2020 07:20:06 -0800 (PST)
Received: from EUR05-VI1-obe.outbound.protection.outlook.com (mail-vi1eur05on2096.outbound.protection.outlook.com [40.107.21.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EE053A0909 for <teas-ns-dt@ietf.org>; Fri, 6 Mar 2020 07:20:05 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=e51NhZeDIxE5/lJoD5AJo3oJ8FI6KXIwC5idn5qBmURQNub5mM3DV/b+ZywK95Rc1gcFs0MVFgohx8poZE8hSk3ULdEffZiLCKybDclasia02+OumkhKMGnzzMolVBYHd1Z39KknO4fic/N/F7s7/vIsqMV8gCqRMcAe1mEdCigDzuBe/6juNdzOSBFoX0T1Dyy22AgF9HQ3bxL23szRQzgEFVOm5HxCp12rHCa5Zqw29eSjHOfnNzP/Kb8fCtJtxFPo7DX6QCK8WSuPxw4KfGsJXn1D5XhfnAFVa6gkAzvzorzEAwNCQw5eUdUupQeNxrkZ4taipg6aeSD2vp9YbA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=9QxI8XYjTnybWDuXVx9QkRAYx3Q0aXANiBkM1eXP3JQ=; b=lq1aEfEhnPkjQTSpiD1NUHtUmSb8ngiuVerU9NYlAnIibYyPNwMhaYrv5j2Yo4cAnUlOMVbyazzHglKUbGoYsOM4BeTWunl4Fzy33KN8sWlqi8W1vhsit/hoiXr2IGgyivoMLy7jT7zp1RoRI3y3MTU1FipL8mckbzU/HcYKfG2KGIojjFywtWW1UMP1DY0wuVbLUkkjzB9SVXGhgAUanM9zSFHXgSoyKBpfmesYEGLdvGdBX/jCdH8qGzhwn9+ZDFsZnwnRd4gLReiIxjzHIoCFkZ+J+aQnjxeHpzU4o5+iw2VWu/Xl1awoBeF2jHmeO2YmfMqWdCPvQkgnUNBztA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=telefonica.com; dmarc=pass action=none header.from=telefonica.com; dkim=pass header.d=telefonica.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telefonica.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=9QxI8XYjTnybWDuXVx9QkRAYx3Q0aXANiBkM1eXP3JQ=; b=I7ZePKTVaW+dO1gMt6YCkgDlOI6nxSvnNJu8QCQdSiJ/IDy6MBk2rENR3UGmRCWB1q9xwr8j3BAiHld7QMftckzqi7TdibxMtSII5O+KDvleR0Gh9raN7y4fwSQijXuWe5T2mi7+i4+dKRaN304lK2WkogAdery/enalaZ9GHhM=
Received: from VI1PR0601MB2157.eurprd06.prod.outlook.com (10.169.136.147) by VI1PR0601MB2398.eurprd06.prod.outlook.com (10.173.82.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2772.18; Fri, 6 Mar 2020 15:20:03 +0000
Received: from VI1PR0601MB2157.eurprd06.prod.outlook.com ([fe80::e4c7:fe9d:bad6:7d71]) by VI1PR0601MB2157.eurprd06.prod.outlook.com ([fe80::e4c7:fe9d:bad6:7d71%11]) with mapi id 15.20.2793.013; Fri, 6 Mar 2020 15:20:03 +0000
From: LUIS MIGUEL CONTRERAS MURILLO <luismiguel.contrerasmurillo@telefonica.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
CC: "teas-ns-dt@ietf.org" <teas-ns-dt@ietf.org>
Thread-Topic: [Teas-ns-dt] Comments to the ACTN reference in the framework document during today's call
Thread-Index: AdXzESm3i0X8aQ/aTdeCuoInpBr9yQAc4ksAABEkvQA=
Date: Fri, 6 Mar 2020 15:20:03 +0000
Message-ID: <VI1PR0601MB21571701C34F6A17347A8BFA9EE30@VI1PR0601MB2157.eurprd06.prod.outlook.com>
References: <VI1PR0601MB2157F00BBFBF1C96E3CF05299EE20@VI1PR0601MB2157.eurprd06.prod.outlook.com> <CAB75xn4t4YVzHcFz8EK-UVpKLmkVxVUfpprLOjOO456h-cJdwA@mail.gmail.com>
In-Reply-To: <CAB75xn4t4YVzHcFz8EK-UVpKLmkVxVUfpprLOjOO456h-cJdwA@mail.gmail.com>
Accept-Language: es-ES, en-US
Content-Language: es-ES
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=luismiguel.contrerasmurillo@telefonica.com;
x-originating-ip: [195.235.92.33]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 0cd45a23-1fc1-4899-ef3f-08d7c1e1d821
x-ms-traffictypediagnostic: VI1PR0601MB2398:
x-microsoft-antispam-prvs: <VI1PR0601MB2398FCC2EB387B3A7182C6C59EE30@VI1PR0601MB2398.eurprd06.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0334223192
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(346002)(39860400002)(376002)(396003)(136003)(366004)(199004)(189003)(4326008)(2906002)(8936002)(478600001)(9686003)(81156014)(81166006)(8676002)(966005)(52536014)(71200400001)(55016002)(5660300002)(33656002)(6506007)(53546011)(66574012)(6916009)(7696005)(316002)(86362001)(66476007)(66556008)(76116006)(186003)(66446008)(64756008)(66946007)(26005)(786003)(9010500006); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR0601MB2398; H:VI1PR0601MB2157.eurprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: telefonica.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: aDIKBrFk+6hhN8KkgF2Ktt4sDNUl78zvsKQYLQcnzMh/iJbodAI6sgDisVppS0CvzdJgyRuyHNyd8GyFg9gTqd6AmIzlFuWTx+zbbNxsp7CKTjNMbIHbk2YRVuM7LWGlbhZpPnAvHNrRuyCWsbu+w06efiYg/jYkUtMqqkpRQCY61r0pRzFCeCAfSL0eGe/z6DDcofXrnPwmmEB1PXGQ9HTRSeOaiFpr88n2+kkAoD/ws3yDSzKUUNxLTkrcmUISkGSZokh9b8+kf3oOnbCMAS/3o6qB4KnCEuaAAIT7aeiqD4zJ+M/pg4FPrKZ7lsQD8htZ2nlt9d4GUSpcodO246L+j/N1EntfeNc+xbbxw0sB+fBVNNEuGFEQ6YalfSd6yDTL5YRIYYK6L5+gkfDDOSlXggwQLFWqBQZc9p+9NRAj13NXBHo54TdWKkpYRFk/9BfJDysI9k5eOeD0cFCminbVQ7LGow51Mk+ftdfK2gvhW8UPccUBmCaZVbOUzfrygqe6jZT/qJJM4hn2nlmxZJT1XBZvyvWbjgiXsF0gL8X+atnmxlbs/hxW+MQeYOD8wFEsJJXZaejSTV+GdtDCNQ==
x-ms-exchange-antispam-messagedata: MrM0qUBrp+M/ji4fS6+C8msX8POaszCOLjRd7yAcGz2LGisDeSd6LQyKe2DFrEVQSQ7POkzP2i+dKwmgnjwx6JrZeAkg4/kRsRO89GV6v0Yu9IZZHGALuhZrTG9bjWa+P90RMauQ5QQn38CjHSqp0w==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: telefonica.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0cd45a23-1fc1-4899-ef3f-08d7c1e1d821
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Mar 2020 15:20:03.2280 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9744600e-3e04-492e-baa1-25ec245c6f10
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Lu33HQNUDT0w/ubyEivSoK8AYeyFSji7ozYa9zaNFdzs5ogXbTBZMz+MLc555MZZ+mbAVn67v/BLQzIbRT8/6oZS8W9BomqZ6EE1obud8e67NCc/lcWcwPb2RRNHABfxisiZRKn21AP84bwoPj1Hog==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0601MB2398
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas-ns-dt/KHQ7iNEIrFz547Roi_iwUdKCP_8>
Subject: Re: [Teas-ns-dt] Comments to the ACTN reference in the framework document during today's call
X-BeenThere: teas-ns-dt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TEAS Network Slicing Design Team <teas-ns-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas-ns-dt>, <mailto:teas-ns-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas-ns-dt/>
List-Post: <mailto:teas-ns-dt@ietf.org>
List-Help: <mailto:teas-ns-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas-ns-dt>, <mailto:teas-ns-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2020 15:20:09 -0000

Hi Dhruv,

I see your point. I don't have any problem showing relationship with existing work (that's fine), but maybe it could be convenient to refer to it as "exemplary" or "potential" or whatever other way of indicating that it is only a possible case. Maybe moving it to an annex can have the same effect.

Regarding the different angles to look at the mapping, I understand your approach. The only risk here is to derive from it that the TSC has the same functionality of the CNC, which could not be the case.

In summary, I'm not against your rationale, I would like simply to keep the things general to leave room for analyzing further how they could actually fit to existing outcomes from TEAS and/or other WGs. Maybe we are anticipating something that could not be fully correct afterwards.

Best regards

Luis


-----Mensaje original-----
De: Dhruv Dhody <dhruv.ietf@gmail.com>
Enviado el: viernes, 6 de marzo de 2020 7:59
Para: LUIS MIGUEL CONTRERAS MURILLO <luismiguel.contrerasmurillo@telefonica.com>
CC: teas-ns-dt@ietf.org
Asunto: Re: [Teas-ns-dt] Comments to the ACTN reference in the framework document during today's call

Hi Luis,

On Thu, Mar 5, 2020 at 10:54 PM LUIS MIGUEL CONTRERAS MURILLO <luismiguel.contrerasmurillo@telefonica.com> wrote:
>
> Because of the same reason as before, I couldn’t verbally comment on this, so in case you didn’t echoed my comment I share by mail.
>
>
>
> My question here is: should not the mapping to ACTN be considered as a potential solution and in consequence go to a solutions draft? I think framework document should be rather generic, and the explicit mapping to ACTN (at least, as it is now) can create confusion.
>

I think it is critical that some context setting is required with existing published work in TEAS WG. This is different from the "mapping and realization" piece of the transport network slicing (which could be out of scope as you have indicated).

Not including this section, creates its own confusion with the very first questions being - how does this work with existing TEAS standards.

>
>
> I mention this because another possible view of looking to that could be to consider CNC as the higher level system, not necessarily at the same level as the TSC, sicne TSC and Network controller could be the same piece, thus mapping to the MDSC.  So, in my view, such mapping is not straightforward.
>

Another way to look at it is in terms of interfaces. TSC speaks TSC SBI in southbound; CNC speaks CMI in its southbound. So the current mapping fits nicely! And that is why TSC NBI is needed (which did not exist in ACTN).

To me a higher-level-system (beyond transport networks) acting as CNC is a case of a collapsed controllers, which is quite usual as these functions can be combined and split as per RFC 8453.

Thanks!
Dhruv

>
>
> Best regards
>
>
>
> Luis
>
>
>
> __________________________________
>
> Luis M. Contreras
>
>
>
> Technology and Planning
>
> Transport, IP and Interconnection Networks
>
> Telefónica I+D / Global CTIO unit / Telefónica
>
>
>
> Distrito Telefónica, Edificio Sur 3, Planta 3
>
> 28050 Madrid
>
> España / Spain
>
>
>
> Skype (Lync): +34 91 312 9084
>
> Mobile: +34 680 947 650
>
> luismiguel.contrerasmurillo@telefonica.com
>
>
>
>
>
>
> ________________________________
>
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.
>
> The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.
>
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu
> destinatário, pode conter informação privilegiada ou confidencial e é
> para uso exclusivo da pessoa ou entidade de destino. Se não é vossa
> senhoria o destinatário indicado, fica notificado de que a leitura,
> utilização, divulgação e/ou cópia sem autorização pode estar proibida
> em virtude da legislação vigente. Se recebeu esta mensagem por erro,
> rogamos-lhe que nos o comunique imediatamente por esta mesma via e
> proceda a sua destruição
> --
> Teas-ns-dt mailing list
> Teas-ns-dt@ietf.org
> https://www.ietf.org/mailman/listinfo/teas-ns-dt

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição