Re: [L3sm] Feedback and operators+implementers input for L3NM draft-aguado-opsawg-l3sm-l3nm-00

Jeff Tantsura <jefftant.ietf@gmail.com> Tue, 28 May 2019 00:23 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: l3sm@ietfa.amsl.com
Delivered-To: l3sm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98D811200E6 for <l3sm@ietfa.amsl.com>; Mon, 27 May 2019 17:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e5cZ1-aE8wO5 for <l3sm@ietfa.amsl.com>; Mon, 27 May 2019 17:23:20 -0700 (PDT)
Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (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 DA377120099 for <l3sm@ietf.org>; Mon, 27 May 2019 17:23:19 -0700 (PDT)
Received: by mail-io1-xd31.google.com with SMTP id h6so5801267ioh.3 for <l3sm@ietf.org>; Mon, 27 May 2019 17:23:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:in-reply-to:references:subject:mime-version; bh=i9EPf9BIQAZS5vVmL0hTJCIv8/XwLOlTE4iuXPFfTbA=; b=XXaJHPUfHxO8hsdQvdiJwQPdpcaIiCKwAEBKvk9dSw8nchDbxeZJRv+54eYFAjA9b0 qlgqu8Q9NFq8KmGFH9P1shH4YkxkaljPQ+poeK3iJZmWytsGrcIoUfAXlhGuTB529zU1 boYjxi020RJ3uLJij97S8xl4kdaZa3JPZhCtywbqz+EX99NddKWgJFg4FuCKD5uGi7E1 HvBqYkzVHdkJQ+kyDfS1hWJ6tSZu2SkMIQklfvZZU1w07gfQJZgV6sIXGVnxCKlMerdj 5Etj02oM2MC3vvXyDJMhiK+iTyYL5E4n6+ASjYVB6d8ENhi/lQXAP9FH7oTLBPgq98gB 8w8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version; bh=i9EPf9BIQAZS5vVmL0hTJCIv8/XwLOlTE4iuXPFfTbA=; b=b+e/g7ndd6sCmmKc4j3xKEbxRWYiQaLwP2RwhdR2dhVRDfCcPmewGoytyYrXYNGaOp tseVhZIR6w1g8/wL+T1h8GbjUmAhMpw/3513wj1wwQ0bY8VVfSU/PW3LVKEkHTunscns TyeHe3zVDaiPYzyecfx69c15mNHgU6pgqtfvXsbPZtl9hOhM9jigNxzU43RLkZUxNrSH Azk0yMAYdEzkhUPXU1aDZt9Nby/hS3WnmD5RTemjvkz9lvvBc2v125s9fnGtDP+effKO kTfix7BcH3sLDxFI50OubjRN8DxVK/mYet7jrpySd2QQAUELWBOcPFS4SahMibly+V9K VWKw==
X-Gm-Message-State: APjAAAVL+5dL4g+LK93ghN11x7iXQ+GWhCiFoji+s3dnKaQTDyrV2xgi IpM/PGtOoVmMLQvys60OcEUzoTOw
X-Google-Smtp-Source: APXvYqwlyXzvAB0ZAlwwy+fUucdl3z6b716K60fSzblbMNiwjgaUJxAHwsRrHEB8SV+nIL0CwqVBfg==
X-Received: by 2002:a6b:e702:: with SMTP id b2mr6091896ioh.175.1559002998788; Mon, 27 May 2019 17:23:18 -0700 (PDT)
Received: from [10.1.253.22] ([216.221.150.18]) by smtp.gmail.com with ESMTPSA id d22sm4116685ioc.51.2019.05.27.17.23.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 May 2019 17:23:18 -0700 (PDT)
Date: Mon, 27 May 2019 17:23:08 -0700
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: "=?utf-8?Q?l3sm=40ietf.org?=" <l3sm@ietf.org>, =?utf-8?Q?Oscar_Gonz=C3=A1lez_de_Dios?= <oscar.gonzalezdedios@telefonica.com>
Message-ID: <11c27e0e-d6ec-4f20-9ac2-668c135ae1a0@Spark>
In-Reply-To: <DB6PR0601MB261324E6D96CECF06DFAD2E5FD1D0@DB6PR0601MB2613.eurprd06.prod.outlook.com>
References: <DB6PR0601MB261324E6D96CECF06DFAD2E5FD1D0@DB6PR0601MB2613.eurprd06.prod.outlook.com>
X-Readdle-Message-ID: 11c27e0e-d6ec-4f20-9ac2-668c135ae1a0@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5cec7f74_15014acb_de9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/NY089l-7L4Rr_unH9uHVj5VSVOQ>
Subject: Re: [L3sm] Feedback and operators+implementers input for L3NM draft-aguado-opsawg-l3sm-l3nm-00
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: L3VPN Service YANG Model discussion group <l3sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3sm>, <mailto:l3sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l3sm/>
List-Post: <mailto:l3sm@ietf.org>
List-Help: <mailto:l3sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3sm>, <mailto:l3sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2019 00:23:23 -0000

Oscar,

Very much needed work, thanks for doing it! Some coordination with TEAS work would be necessary. Operational states need to be defined.
I'd also welcome architectural presentation of the draft in RTGWG.

Cheers,
Jeff
On May 27, 2019, 10:19 AM -0700, Oscar González de Dios <oscar.gonzalezdedios@telefonica.com>;, wrote:
> Dear L3SM colleagues,
>
>      I would like to ask for feedback on an operator-led initiative to build a L3VPN Network Yang model (let’s refer to it as L3NM) building on top of the work that was carried out in the L3SM working group. The first draft is available in https://tools.ietf.org/html/draft-aguado-opsawg-l3sm-l3nm-00. As the working group is now formally closed, I have also sent the email and posted the first version of the draft in the context of OPSAWG.
>
>       Please note that the yang model itself is still a work in progress, and the first intention is to show the need of having such a model and how it related to current initiatives. The starting point of the work is the L3VPN Yang model defined in RFC 8299.  More complex deployment scenarios involving the  coordination of different VPN instances and different technologies to  provide end-to-end VPN connectivity is out of scope of this document,  but is discussed in https://tools.ietf.org/html/draft-evenwu-opsawg-yang-composed-vpn-03 .
>
>     RFC 8309 splits the service models into “Customer Service Model” and “Service Delivery Model”. The L3SM Yang model, defined in RFC 8299, is valid for the customer to network operator conversation, but if operators want to use it for the conversations between the B/OSS (business and operation support systems) and the network orchestrator (or controller, depending on the terminology used) then the model has some gaps. There are two options:
>
> “Augment” approach. This is the approach shown in version 00. The model in RFC 8299 is extended via augmentation to cover the gaps. Still, some parameters defined by L3SM may not be necessary for the network version of the service model (those more related to the customer, which are mandatory for the direct customer interface).
> “Prune and extend” approach. This approach will present an easier way to ignore and prune unnecessary information defined at L3SM. At the same time, any extension can be presented as part of the main module, and not as augments of an existing model. However, many content would be similar to L3SM
>
> In the draft you can find a first set of topics covered by the model.  The scenarios covered include: the integration of ethernet and encapsulation parameters, the extension for transport resources (e.g. RTs and RDs) to be orchestrated from the management system, far-end  configuration of PEs not managed by the management system and the definition for PE identification. Note the end customer does not really care about the internal network resources, neither does care exactly which PE is used. Those decisions are taken by the operator, that then with the help of the control systems will deploy the service.
>
>     We would like to ask input from operators/service providers who might use this model and from software implementers who might code the model.
>
>     Best Regards,
>
>                 Oscar
>
>
>
> 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
> _______________________________________________
> L3sm mailing list
> L3sm@ietf.org
> https://www.ietf.org/mailman/listinfo/l3sm