Re: [Teas] [E] Re: Slicing Framework Open issue #1 : Service != Realization

[Kiran M <[e-mail]>]

yes, looks good. I hope that documents that refer to this one use them 
properly.
------------------------------------------------------------------------
*From:* Jalil, Luay [mailto:luay.jalil=[e-mail]]
*Sent:* Friday, March 25, 2022, 4:48 AM
*To:* LUIS MIGUEL CONTRERAS MURILLO
*Cc:* [e-mail]
*Subject:* [Teas] [E] Re: Slicing Framework Open issue #1 : Service != 
Realization

> +1
>
> Regards,
> *Luay*
>
>
> On Fri, Mar 25, 2022 at 10:49 AM LUIS MIGUEL CONTRERAS MURILLO 
> <[e-mail]> wrote:
>
>     Hi all,
>
>     Agree, the proposed change is ok.
>
>     Best regards
>
>     Luis
>
>     -----Mensaje original-----
>     De: Teas <[e-mail]> En nombre de Joel M. Halpern
>     Enviado el: viernes, 25 de marzo de 2022 10:30
>     Para: [e-mail]
>     Asunto: Re: [Teas] Slicing Framework Open issue #1 : Service !=
>     Realization
>
>     Works for me.
>     Yours,
>     Joel
>
>     On 3/25/2022 5:17 AM, Adrian Farrel wrote:
>     > Hi,
>     >
>     > First in a series of emails to resolve the open issues mentioned
>     > during the TEAS meeting.
>     >
>     > We have, for the longest time, suffered from a blurring between the
>     > service provided to the customer, and how that service is
>     engineered in the network.
>     > This leads us to talk about VPNs in a way where sometimes a VPN is
>     > what the customer gets and sometimes it is what the operator
>     > engineers. A good example is the term "MPLS VPN" as though the
>     > customer cares whether the VPN is provided using MPLS technology.
>     >
>     > We have, to some extent, clarifies this with recent YANG "Customer
>     > Service Models" that describe the service offered to the
>     customer, but
>     > do not constrain the provider's choice of implementation
>     technology or options.
>     >
>     > As the discussion of IETF Network Slices continues, I have
>     repeatedly
>     > seen some blurring between the topics of the "IETF Network Slice
>     > Service" and the "IETF Network Slice." It seems to me that this
>     mixing
>     > of concepts will continue as future readers pick up the document.
>     >
>     > Although I have tried to use the two terms clearly and
>     distinctly, the
>     > document is missing a clear statement to disambiguate the two.
>     >
>     > Section 3 provides the definitions of the two terms at some length
>     > using subsections. The clarification would get lost if it was placed
>     > at the bottom of the section after the subsections, so I propose to
>     > include some text near the top of section as follows.
>     >
>     > OLD
>     >     IETF Network Slices are created to meet specific requirements,
>     >     typically expressed as bandwidth, latency, latency
>     variation, and
>     >     other desired or required characteristics. Creation of an IETF
>     >     Network Slice is initiated by a management system or other
>     >     application used to specify network-related conditions for
>     particular
>     >     traffic flows in response to an actual or logical IETF
>     Network Slice
>     >     service request.
>     >
>     >     Once created, these slices can be monitored, modified,
>     deleted, and
>     >     otherwise managed.
>     >
>     >     Applications and components will be able to use these IETF
>     Network
>     >     Slices to move packets between the specified end-points of the
>     >     service in accordance with specified characteristics.
>     > NEW
>     >     IETF Network Slices are created to meet specific requirements,
>     >     typically expressed as bandwidth, latency, latency
>     variation, and
>     >     other desired or required characteristics. Creation of an IETF
>     >     Network Slice is initiated by a management system or other
>     >     application used to specify network-related conditions for
>     particular
>     >     traffic flows in response to an actual or logical IETF
>     Network Slice
>     >     service request.
>     >
>     >     Once created, these slices can be monitored, modified,
>     deleted, and
>     >     otherwise managed.
>     >
>     >     Applications and components will be able to use these IETF
>     Network
>     >     Slices to move packets between the specified end-points of the
>     >     service in accordance with specified characteristics.
>     >
>     >     A clear distinction should be made between the "IETF Network
>     >     Slice service" which is the function delivered to the customer
>     >     (see Section 3.2) and which is agnostic to the technologies and
>     >     Mechanisms used by the service provider, and the "IETF Network
>     >     Slice" which is the realization of the service in the provider's
>     >     network achieved by partitioning network resources and by
>     >     applying certain tools and techniques within the network (see
>     >     Section 3.1).
>     > END
>     >
>     > Any objections?
>     >
>     > Thanks,
>     > Adrian
>     >
>     > _______________________________________________
>     > Teas mailing list
>     > [e-mail]
>     >
>     https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_teas&d=DwIGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=k0DrrBeS0St-D1jEwNQ_u1ZyHQXQly5fgCsWF0VTh7o&m=ZgpFwbYBRDMbGaCALx4Ex8KrMyZD-gVEhsHKWD9592QJ8dwgs8zvLN3YyhpE0lAq&s=PT9yEot5W1FaYvK-vS_Gc8_apuR_Azv2CkH7JBiNeUw&e=
>     <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_teas&d=DwIGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=k0DrrBeS0St-D1jEwNQ_u1ZyHQXQly5fgCsWF0VTh7o&m=ZgpFwbYBRDMbGaCALx4Ex8KrMyZD-gVEhsHKWD9592QJ8dwgs8zvLN3YyhpE0lAq&s=PT9yEot5W1FaYvK-vS_Gc8_apuR_Azv2CkH7JBiNeUw&e=>
>
>
>     _______________________________________________
>     Teas mailing list
>     [e-mail]
>     https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_teas&d=DwIGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=k0DrrBeS0St-D1jEwNQ_u1ZyHQXQly5fgCsWF0VTh7o&m=ZgpFwbYBRDMbGaCALx4Ex8KrMyZD-gVEhsHKWD9592QJ8dwgs8zvLN3YyhpE0lAq&s=PT9yEot5W1FaYvK-vS_Gc8_apuR_Azv2CkH7JBiNeUw&e=
>     <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_teas&d=DwIGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=k0DrrBeS0St-D1jEwNQ_u1ZyHQXQly5fgCsWF0VTh7o&m=ZgpFwbYBRDMbGaCALx4Ex8KrMyZD-gVEhsHKWD9592QJ8dwgs8zvLN3YyhpE0lAq&s=PT9yEot5W1FaYvK-vS_Gc8_apuR_Azv2CkH7JBiNeUw&e=>
>
>
>     ________________________________
>
>     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
>     _______________________________________________
>     Teas mailing list
>     [e-mail]
>     https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_teas&d=DwIGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=k0DrrBeS0St-D1jEwNQ_u1ZyHQXQly5fgCsWF0VTh7o&m=ZgpFwbYBRDMbGaCALx4Ex8KrMyZD-gVEhsHKWD9592QJ8dwgs8zvLN3YyhpE0lAq&s=PT9yEot5W1FaYvK-vS_Gc8_apuR_Azv2CkH7JBiNeUw&e=
>     <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_teas&d=DwIGaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=k0DrrBeS0St-D1jEwNQ_u1ZyHQXQly5fgCsWF0VTh7o&m=ZgpFwbYBRDMbGaCALx4Ex8KrMyZD-gVEhsHKWD9592QJ8dwgs8zvLN3YyhpE0lAq&s=PT9yEot5W1FaYvK-vS_Gc8_apuR_Azv2CkH7JBiNeUw&e=>
>
>
>
> _______________________________________________
> Teas mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/teas