Re: [Teas] The definition of a Network Slice in draft-nsdt-teas-ietf-network-slice-definition

I tend to agree with Daniele. We should focus on connectivity slice in IETF
at least for now. Then other types of slices that are being defined and
modeled by other SDOs (such as RAN slice and Core Network slice) should be
first evaluated to see if there would be any lack. Only then we would know
if and what IETF can fill the gap.

Perhaps this is another way of saying what Adrian initially stated.

Best regards,
Young

2020년 11월 16일 (월) 오후 9:37, Daniele Ceccarelli <daniele.ceccarelli=
40ericsson.com@dmarc.ietf.org>님이 작성:

> Hi Med,
>
> This seems to be re-opening Pandora's box.
> My understanding was that the IETF network slice was the connectivity
> component of an E2E slice.
> If we're now thinking of the connectivity part of the IETF network slice
> it means we're "elevating" the IETF network slice to compete with other
> definitions of E2E network slices.
>
> I would agree with Jari on the fact that it would be more efficient to
> focus on what we're good at and focus our effort and energy to get an
> achievement there instead of trying to cover too many different things.
>
> BR
> Daniele
>
> -----Original Message-----
> From: Teas <teas-bounces@ietf.org> On Behalf Of
> mohamed.boucadair@orange.com
> Sent: den 16 november 2020 09:08
> To: adrian@olddog.co.uk; 'Jari Arkko' <jari.arkko@piuha.net>
> Cc: teas@ietf.org; draft-nsdt-teas-ietf-network-slice-definition@ietf.org
> Subject: Re: [Teas] The definition of a Network Slice in
> draft-nsdt-teas-ietf-network-slice-definition
>
> Hi Adrian, Jari, all,
>
> I agree with the observations made by Adrian and Jari's comment.
>
> It would be helpful to have a name to refer to the connectivity component
> of an IETF network slice. Also, if there are concrete examples of
> non-connectivity IETF components that can be cited in the draft, this would
> be even great.
>
> Cheers,
> Med
>
> > -----Message d'origine-----
> > De : Teas [mailto:teas-bounces@ietf.org] De la part de Adrian Farrel
> > Envoyé : dimanche 15 novembre 2020 23:01 À : 'Jari Arkko'
> > <jari.arkko@piuha.net> Cc :
> > draft-nsdt-teas-ietf-network-slice-definition@ietf.org;
> > teas@ietf.org
> > Objet : Re: [Teas] The definition of a Network Slice in draft-nsdt-
> > teas-ietf-network-slice-definition
> >
> > Hmm.
> > Maybe a way through this would be to acknowledge slicing of all types
> > of network as possible, and then say that this document is focusing on
> > slicing of connectivity resources.
> >
> > Adrian
> >
> > -----Original Message-----
> > From: Jari Arkko <jari.arkko@piuha.net>
> > Sent: 15 November 2020 21:54
> > To: adrian@olddog.co.uk
> > Cc: teas@ietf.org; draft-nsdt-teas-ietf-network-slice-
> > definition@ietf.org
> > Subject: Re: [Teas] The definition of a Network Slice in draft-nsdt-
> > teas-ietf-network-slice-definition
> >
> > Adrian:
> >
> > Thanks for this as well. Again, I largely agree with what you suggest.
> >
> > (The one exception may be that I do believe firmly that we should be
> > careful to keep the scope of our concept close to what we are experts
> > in, i.e., communication. It also reduces the risk potential confusion
> > and overlap with others who work in the broader area.)
> >
> > Jari
> >
> > _______________________________________________
> > Teas mailing list
> > Teas@ietf.org
> > https://www.ietf.org/mailman/listinfo/teas
>
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc pas etre diffuses,
> exploites ou copies sans autorisation. Si vous avez recu ce message par
> erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les
> pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged
> information that may be protected by law; they should not be distributed,
> used or copied without authorisation.
> If you have received this email in error, please notify the sender and
> delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>