Subject: Re: [Teas] Disposition of draft-ietf-teas-ietf-network-slice-definition-00

From: <[email-masked]>
Date: Fri, 2 Apr 2021 13:01:45 +0000

Hi John, all, 

Thank you for initiating this.

I do see a value in merging the definition draft into the framework. This will at least avoid some inconsistencies I raised in the past between the two.

I know that the authors of the definition I-D kindly organized off-list discussions to explore many aspects of the definition I-D. It would be fair to let them share/inject the conclusions of these discussions into the merged document. Thanks.   

Cheers,
Med

> -----Message d'origine-----
> De : Teas [mailto:[email-masked]] De la part de John E Drake
> Envoyé : mercredi 31 mars 2021 17:44
> À : [email-masked]
> Objet : [Teas] Disposition of draft-ietf-teas-ietf-network-slice-
> definition-00
> 
> Hi,
> 
> Eric and I have been asked by the teas working group chairs to merge
> the subject draft into the framework
> draft: https://datatracker.ietf.org/doc/html/draft-ietf-teas-ietf-
> network-slice-framework-00.  Our proposal is detailed below.
> 
> 
> Definition of IETF Network Slices
>             draft-ietf-teas-ietf-network-slice-definition-01
> 
> Table of Contents
> 
>    1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .
> 2
> 
> *****JD  The content of the two introductions will be merged
> 
>    2.  Terms and Abbreviations . . . . . . . . . . . . . . . . . . .
> 3
> 
> *****JD  This will be a new section 2 in the Framework draft.    The
> current
> section 2 of the Framework draft will be split between the new
> section 2 and possibly sections 3 and 4.
> 
>    3.  Definition and Scope of IETF Network Slice  . . . . . . . . .
> 4
> 
> *****JD  This section will be moved to the new section 2.
> 
>    4.  IETF Network Slice System Characteristics . . . . . . . . . .
> 4
> 
> *****JD  This section will be moved to the new section 2
> 
>      4.1.  Objectives for IETF Network Slices  . . . . . . . . . . .
> 5
> 
> *****JD  This section will be split  between the new section 2 and
> possibly sections 3 and 4.
> 
>        4.1.1.  Service Level Objectives  . . . . . . . . . . . . . .
> 5
>        4.1.2.  Minimal Set of SLOs . . . . . . . . . . . . . . . . .
> 5
>        4.1.3.  Other Objectives  . . . . . . . . . . . . . . . . . .
> 7
> 
> *****JD  These sections will be moved to the new section 2.
> 
>      4.2.  IETF Network Slice Endpoints  . . . . . . . . . . . . . .
> 7
> 
> *****JD  This section will be moved to the new section 2 and will be
> updated to use the terminology agreed upon on the mailing list.  A
> reference to RFC 4364's section 9 "Carriers' Carriers"
> (https://datatracker.ietf.org/doc/html/rfc4364#section-9)
> will be added.  We will also note that the 'CE', 'attachment
> circuit', and 'PE' can all be virtualized.
> 
>        4.2.1.  IETF Network Slice Connectivity Types . . . . . . . .
> 9
> 
> *****JD  This section will be moved to the new section 2.
> 
>      4.3.  IETF Network Slice Composition  . . . . . . . . . . . . .
> 9
> 
> *****JD  This section will be moved to the new section 2.  Note that
> the non-definitional material in *all* of the preceding sections will
> be split between sections 3 and 4.  Section
> 4 will become a generalized 'Applicability' section .
> 
>    5.  IETF Network Slice Structure  . . . . . . . . . . . . . . . .
> 10
> 
> *****JD  This section will be split  between the new section 2 and
> possibly sections 3 and 4.
> 
>    6.  IETF Network Slice Stakeholders . . . . . . . . . . . . . . .
> 11
> 
> *****JD  This section will be moved to section 4.
> 
>    7.  IETF Network Slice Controller Interfaces  . . . . . . . . . .
> 12
> 
> *****JD  This is covered in section 3.3.
> 
>    8.  Realizing IETF Network Slice  . . . . . . . . . . . . . . . .
> 12
> 
> *****JD  This is covered in section 3.5.
> 
>    9.  Isolation in IETF Network Slices  . . . . . . . . . . . . . .
> 13
>      9.1.  Isolation as a Service Requirement  . . . . . . . . . . .
> 13
>      9.2.  Isolation in IETF Network Slice Realization . . . . . . .
> 13
> 
> *****JD  These sections will be moved to the new section 2.  They
> assume a definition of the term 'isolation' which has never been
> explicitly rendered, so we will propose a definition to the mailing
> list.
> 
>    10. Security Considerations . . . . . . . . . . . . . . . . . . .
> 14
> 
> *****JD  Relevant material will be moved to section 5.2.  We will
> propose what we consider to be relevant and irrelevant material to
> the mailing list.
> 
>    11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .
> 14
> 
> *****JD  The Framework draft already has this section.
> 
>    12. Acknowledgment  . . . . . . . . . . . . . . . . . . . . . . .
> 15
> 
> *****JD  This section will be moved to section 6.
> 
>    13. Informative References  . . . . . . . . . . . . . . . . . . .
> 15
> 
> *****JD  This section will be moved to section 7.
> 
>    Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .
> 17
> 
> *****JD  This will need to be sorted out with the authors and
> contributors to the Framework draft.
> 
> 
> 
> *****JD  For reference, below is the current table of contents for
> the Framework draft:
> 
> Framework for IETF Network Slices
>             draft-ietf-teas-ietf-network-slice-framework-00
> 
> Table of Contents
> 
>    1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .
> 2
>    2.  IETF Network Slice Objectives . . . . . . . . . . . . . . . .
> 4
>    3.  Framework . . . . . . . . . . . . . . . . . . . . . . . . . .
> 5
>      3.1.  Management systems or other applications  . . . . . . . .
> 6
>      3.2.  Expressing connectivity intents . . . . . . . . . . . . .
> 6
>      3.3.  IETF Network Slice Controller (NSC) . . . . . . . . . . .
> 8
>        3.3.1.  Northbound Interface (NBI)  . . . . . . . . . . . . .
> 9
>      3.4.  Mapping . . . . . . . . . . . . . . . . . . . . . . . . .
> 9
>      3.5.  Underlying technology . . . . . . . . . . . . . . . . . .
> 9
>    4.  Applicability of ACTN to IETF Network Slices  . . . . . . . .
> 10
>    5.  Considerations  . . . . . . . . . . . . . . . . . . . . . . .
> 12
>      5.1.  Monitoring  . . . . . . . . . . . . . . . . . . . . . . .
> 12
>      5.2.  Security Considerations . . . . . . . . . . . . . . . . .
> 13
>      5.3.  Privacy Considerations  . . . . . . . . . . . . . . . . .
> 13
>      5.4.  IANA Considerations . . . . . . . . . . . . . . . . . . .
> 13
>    6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .
> 13
>    7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .
> 14
>      7.1.  Normative References  . . . . . . . . . . . . . . . . . .
> 14
>      7.2.  Informative References  . . . . . . . . . . . . . . . . .
> 14
>    Contributors  . . . . . . . . . . . . . . . . . . . . . . . . . .
> 17
>    Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .
> 18
> 
> Yours Irrespectively,
> 
> John
> 
> 
> Juniper Business Use Only
> 
> _______________________________________________
> Teas mailing list
> [email-masked]
> 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.