Re: [Teas] DC topo model

Adrian Farrel <adrian@olddog.co.uk> Sun, 06 August 2023 13:24 UTC

Return-Path: <adrian@olddog.co.uk>
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 9FA96C14CF1B for <teas@ietfa.amsl.com>; Sun, 6 Aug 2023 06:24:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=olddog.co.uk
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 2oU7lw1PYDy1 for <teas@ietfa.amsl.com>; Sun, 6 Aug 2023 06:24:25 -0700 (PDT)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (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 C1345C14CF0C for <teas@ietf.org>; Sun, 6 Aug 2023 06:24:22 -0700 (PDT)
Received: from vs4.iomartmail.com (vs4.iomartmail.com [10.12.10.122]) by mta7.iomartmail.com (8.14.7/8.14.7) with ESMTP id 376DOKP5013778; Sun, 6 Aug 2023 14:24:20 +0100
Received: from vs4.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id D2D584604A; Sun, 6 Aug 2023 14:24:19 +0100 (BST)
Received: from vs4.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id C6CCD46043; Sun, 6 Aug 2023 14:24:19 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs4.iomartmail.com (Postfix) with ESMTPS; Sun, 6 Aug 2023 14:24:19 +0100 (BST)
Received: from LAPTOPK7AS653V (82-69-109-75.dsl.in-addr.zen.co.uk [82.69.109.75]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.7/8.14.7) with ESMTP id 376DOJXE014869 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 6 Aug 2023 14:24:19 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'LUIS MIGUEL CONTRERAS MURILLO' <luismiguel.contrerasmurillo@telefonica.com>, 'TEAS WG' <teas@ietf.org>
References: <1378735280.756348.1690568741136@www.getmymail.co.uk> <DB9PR06MB7915686409FD9F30974419AA9E09A@DB9PR06MB7915.eurprd06.prod.outlook.com>
In-Reply-To: <DB9PR06MB7915686409FD9F30974419AA9E09A@DB9PR06MB7915.eurprd06.prod.outlook.com>
Date: Sun, 06 Aug 2023 14:24:18 +0100
Organization: Old Dog Consulting
Message-ID: <091b01d9c869$4e1c2950$ea547bf0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_091C_01D9C871.AFE154A0"
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQHfgCMw720pWEbeS5WlQQiiVXF1AgE/tgjAr8fUPXA=
X-Originating-IP: 82.69.109.75
X-Thinkmail-Auth: adrian@olddog.co.uk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=olddog.co.uk; h=reply-to :from:to:references:in-reply-to:subject:date:message-id :mime-version:content-type; s=20221128; bh=0rUqLaRElANQEdSW/j4Iv OmMlK6DiUcEgHo2O6e2Ohk=; b=UyoPtC523xdUjzD5Oher0iFfngEglRFwGt+2i YHIEe7Q/b+zT5HmeW+atHYJCe2NIpON9eYttoBLlReGHqzA8+NMu8HSe7O7rXp4z SVlQOny0HlclQIAr4U6KJZ7lQYgvjK5kYnTWvaZehM70DIE/BhUZnGreEAftYAik E9Ftu+UZxI5w3bGBbiutBvnFrtyhghY7tm00ijBe+QfL2H9x+h2l4U2E7kPN0665 4mA+FaDdN6GAuIK72RzA6UiLdBNN8KXKi04NN6IxqQaOyKsoVShI3dmHF0X6eatz 78DiHOBXJl3D/G3CD4QFUaMKcyQxiAwo6TnL0qT8BtVePclhg==
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-27796.007
X-TM-AS-Result: No--34.424-10.0-31-10
X-imss-scan-details: No--34.424-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-27796.007
X-TMASE-Result: 10--34.424300-10.000000
X-TMASE-MatchedRID: OoEa6u7Uk5/uYusHgJkgymjJpufOqOIAz/yBGeBkff8DYMKGFRHEiV6/ 9ZADn0zMhaG5EyTT/hm+FFt5FsnUj567BAwwL5I6lDt5PQMgj02IP8tyWMRkee/m0bmpDCNAh7w 8b9AwvtVFS1R7f3eKlIfgClIaA5yIfOaYwP8dcX6LeKSmObt0Kc9MhHp9AQ+0ECbXQv7eAnYJ3M vryyFEr5M1rHyS5oCXdvvbftTsJScB6/aPodnUlust+6egjyLAHW7srwepo1w9npQCD4p3Zo9uY IJLkmvLVGfQASkmiVBYY5K8AD7C0ZyZM46Vt55C18e/rEAghxpzqHzf9/158Zu2O77r/OM3max+ pHXx7HMBNYzLsJUSdd2HR6CmYvEmmncTQEc+X8HzdfBwMSp49FdlFb7gPMhTFFD0T7Xiy74cTSi 7vdg5r70Q7s7KCbDzz9kBTQLL02UQQz+TtuPws0kXItYda75bu++bOb/neSIdxMntO89tJfrysH qvQhIuV6E0elrnpAalkZbr4D1y6MUumVz0RfCZ+sHeZZKWcvrJp6eXziyuSW4ScRih29fPxBhtE ym4Qe1v/H55jRNHuTBI7p5NTen7uBor/YI192X42bLFnve692WJ7VoWHTPsJiJpfssK6r7aTGrL P3nCulgFfpaHUMwu2FMcgddyBa/wlvzzUUaf2ToSfZud5+GgKUyR2mjZLjrCiZMR9A73Q8I8YW4 vKFnf1GS9Dk8MpfcKpnsevCOcArk1u2T7z9gaiJAbVZuRcFvEAvvAznb2XoLb3bpB3AxedaQJ9G mEmupZZWe18OKYSNvgnnTI8F5AYsfP2TTq8cZTGvUnJAUHmpsoi2XrUn/JlR1cT9YafQVWhNrmU WSdQcePjXoH9NMLKzfM9B6IRt7+efAnnZBiL6nKAIYoU8L4F5iXm5LZACA=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/QnymOcghj1gYA8BYA0ZC9Au2Z4I>
Subject: Re: [Teas] DC topo model
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: Sun, 06 Aug 2023 13:24:29 -0000

Thanks, that’s helpful.

Adrian

 

From: LUIS MIGUEL CONTRERAS MURILLO <luismiguel.contrerasmurillo@telefonica.com> 
Sent: 04 August 2023 07:50
To: Adrian Farrel <adrian@olddog.co.uk>; TEAS WG <teas@ietf.org>
Subject: RE: [Teas] DC topo model

 

Hi Adrian,

 

Regarding the possible overlap with CATS, I think it is draft-ietf-teas-sf-aware-topo-model the closest draft to CATS aspects. This is because draft-ietf-teas-sf-aware-topo-model is related to Service Functions already in place, so subject to result end-points of a potential traffic steering decision.

 

The case of draft-llc-teas-dc-aware-topo-model is more related to the availability of resources in computing facilities (i.e., centralized cloud, edge environments, etc) where no Service Functions have been yet deployed. In fact, the usage of this model could be precisely to provide TE network topology up to those facilities with the aim of instantiating Service Functions there. So, one step before in the overall service lifecycle.

 

Regarding who might consume the model, linking as well with the question from Daniele at the mic, certainly we lack of details now in the draft. This is taken as a ToDo for next version. As quick answer, as said before, the idea is to facilitate informed decisions at the time of deploying service instances so that the compute part plus the TE part can be taken into consideration.

 

Thanks for the question,

 

Best regards

 

Luis  

 

De: Teas <teas-bounces@ietf.org <mailto:teas-bounces@ietf.org> > En nombre de Adrian Farrel
Enviado el: viernes, 28 de julio de 2023 20:26
Para: TEAS WG <teas@ietf.org <mailto:teas@ietf.org> >
Asunto: [Teas] DC topo model

 

I was happily dozing at the back of the meeting when the AD woke me up to ask about the overlap between draft-llc-teas-dc-aware-topo-model and CATS 

  

My initial reaction was that it may be closer to IVY, but on re-reading I see that it does use the word "compute" 

  

I think a lot of the question comes to who might consume this model. Is it intended to provide a picture of the DC for the DC's operator, for other control processes within the DC, or for consumers outside the DC? 

  

I think the draft should answer that question to give scope to how the model will be used and what it should contain 

  

Cheers, 

Adrian 

 

  _____  


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 confidential and privileged 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

  _____  


Le informamos de que el responsable del tratamiento de sus datos es la entidad del Grupo Telefónica vinculada al remitente, con la finalidad de mantener el contacto profesional y gestionar la relación establecida con el destinatario o con la entidad a la que está vinculado. Puede contactar con el responsable del tratamiento y ejercitar sus derechos escribiendo a privacidad.web@telefonica.com <mailto:privacidad.web@telefonica.com> . Puede consultar información adicional sobre el tratamiento de sus datos en nuestra Política de Privacidad <https://www.telefonica.com/es/telefonica-politica-de-privacidad-de-terceros/> .

We inform you that the data controller is the Telefónica Group entity linked to the sender, for the purpose of maintaining professional contact and managing the relationship established with the recipient or with the entity to which it is linked. You may contact the data controller and exercise your rights by writing to privacidad.web@telefonica.com <mailto:privacidad.web@telefonica.com> . You may consult additional information on the processing of your data in our Privacy Policy <https://www.telefonica.com/en/wp-content/uploads/sites/5/2022/12/Telefonica-Third-data-subjects-Privacy-Policy.pdf> .

Informamos que o responsável pelo tratamento dos seus dados é a entidade do Grupo Telefónica vinculada ao remetente, a fim de manter o contato professional e administrar a relação estabelecida com o destinatário ou com a entidade à qual esteja vinculado. Você pode entrar em contato com o responsável do tratamento de dados e exercer os seus direitos escrevendo a privacidad.web@telefonica.com <mailto:privacidad.web@telefonica.com> . Você pode consultar informação adicional sobre o tratamento do seus dados na nossa Política de Privacidade <https://www.telefonica.com/es/politica-de-privacidade-de-terceiros/> .