Re: [Teas] New Slicing revision: I-D Action: draft-ietf-teas-ietf-network-slices-01.txt

[Daniele Ceccarelli <[e-mail]>]

Hi Adrian,

Completely agree. 
Please see in line for some more comments.

BR
Daniele  

> -----Original Message-----
> From: Adrian Farrel <[e-mail]>
> Sent: den 16 april 2021 21:06
> To: Daniele Ceccarelli <[e-mail]>; [e-mail]
> Subject: RE: [Teas] New Slicing revision: I-D Action: draft-ietf-teas-ietf-network-
> slices-01.txt
> 
> Hi Daniele,
> 
> > Regarding the discussion on realization.
> >
> > Maybe we could have section 6 split into an analysis of existing
> > tools,
> something like:
> >
> > 6.  Applicability of existing IETF tools to IETF Network Slices
> > 6.1 ACTN
> > 6.2 Enhanced VPN
> > 6.3 draft-bestbar
> 
> Yes, that's the split I am seeing (although may need a better name for 6.3).

[DC] yes definitely. Maybe something like: "Network slicing and slice aggregates in IP/MPLS networks"

> 
> However, I don't envision much text in each section. IMHO, this document is not
> the place to expound in detail on the realisation possibilities. Once we have
> established the key architectural points in this document, people can write other
> documents (applicability statements) to explain how their favourite approach
> can be applied to satisfy the architecture.

[DC] Makes sense. It's not the scope of the framework to define solutions. An hook to existing work is more than enough. Maybe solution drafts might go into a more detailed analysis of how each solution can meet the requirements.

> 
> > (I still believe the VTN can be a particular type of VN...but this is
> another story)
> 
> That is a discussion that is really worth continuing, but I think it is outside the
> scope of this document.
> 
> > Willing to be more creative we could split them into data plane, and
> control/management
> > plane?
> 
> I wonder whether this should find its way into...
>      5.5.  Realizing IETF Network Slice  . . . . . . . . . . . . . .  20
>        5.5.1.  Underlying Technology . . . . . . . . . . . . . . . .  20
> 
[DC]  yes, that's a valuable option. Even if as you said above it would be just an reference.

> Cheers,
> Adrian
> 
> -----Original Message-----
> From: Teas <[e-mail]> On Behalf Of Adrian Farrel
> Sent: den 16 april 2021 12:39
> To: [e-mail]
> Cc: [e-mail]
> Subject: [Teas] New Slicing revision: I-D Action:
> draft-ietf-teas-ietf-network-slices-01.txt
> 
> Hi,
> 
> In this revision, I have tidied the text. That involved:
> - Fixing inconsistent editorial standards between the source documents
> - Some more minor editorials
> - Moving a couple of sections around
> - Collapsing a little duplication arising from pulling text from two places
> - Removing cross-references between the source documents
> - Removing the tagging of the source material
> 
> In doing so, there were two small paragraphs that didn't seem to belong.
> These can be seen in the Appendix.
> 
> ACTION: All: Please shout if you believe this text should not be deleted.
> 
> While this document is now in a condition that can be reviewed and commented
> on, I propose to make some suggestions to reduce and consolidate the text. I
> will bring these to the list as separate threads (some have already been seen on
> the list, but we should make the proposed changes clear). They will
> cover:
> 
> - Discussion of realisation.
>   This should be a discussion of architectural realisation, not of underlying
> technologies.
>   Currently we have:
>    - a large section on ACTN
>    - a couple of references to VPN+
>    - no mention of the architecture underlying draft-bestbar-teas-yang-slice-
> policy
>   I already suggested (on list) a way to reduce the ACTN text, but it has since
> been
>   proposed to me that all discussion of realisation of the architecture can be best
>   achieved with brief paragraphs and references. I will propose text.
> 
> - Isolation and "unmeasurable SLOs"
>   This has long been a contentious topic. I think we had reached a bit of a
> compromise
>   in the definitions draft, but doing the merge has caused me to re-read it and I
> am
>   uneasy. I will be making a text suggestion to clarify the purpose and meaning of
> the
>   section on isolation, and that will depend on us also clarifying the description
> of
>   "directly measurable SLOs" and "indirectly measurable SLOs.
> 
> - Revisiting the definition of a network slice
>   This is obviously pretty core to our work! John Drake previously sent a
> suggestion to
>   the list (2021-04-03). This caused a bit of discussion and raises a number of
> points.
>   I plan to try to tease out the various points to see whether we can agree them
>   Separately and then come up with new definitions text. This may be a good
> topic
>   For our first telechat on the document.
> 
> ACTION: Chairs: Decide what the rules are for having telechat meetings for this
> document.
> 
> Thanks,
> Adrian
> 
> -----Original Message-----
> From: I-D-Announce <[e-mail]> On Behalf Of internet-
> [e-mail]
> Sent: 16 April 2021 11:19
> To: [e-mail]
> Cc: [e-mail]
> Subject: I-D Action: draft-ietf-teas-ietf-network-slices-01.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Traffic Engineering Architecture and Signaling
> WG of the IETF.
> 
>         Title           : Framework for IETF Network Slices
>         Authors         : Adrian Farrel
>                           Eric Gray
>                           John Drake
>                           Reza Rokui
>                           Shunsuke Homma
>                           Kiran Makhijani
>                           Luis M. Contreras
>                           Jeff Tantsura
> 	Filename        : draft-ietf-teas-ietf-network-slices-01.txt
> 	Pages           : 33
> 	Date            : 2021-04-16
> 
> Abstract:
>    This document describes network slicing in the context of networks
>    built from IETF technologies.  It defines the term "IETF Network
>    Slice" and establishes the general principles of network slicing in
>    the IETF context.
> 
>    The document discusses the general framework for requesting and
>    operating IETF Network Slices, the characteristics of an IETF Network
>    Slice, the necessary system components and interfaces, and how
>    abstract requests can be mapped to more specific technologies.  The
>    document also discusses related considerations with monitoring and
>    security.
> 
>    This document also provides definitions of related terms to enable
>    consistent usage in other IETF documents that describe or use aspects
>    of IETF Network Slices.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-teas-ietf-network-slices/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-teas-ietf-network-slices-01
> https://datatracker.ietf.org/doc/html/draft-ietf-teas-ietf-network-slices-01
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-ietf-network-slices-01
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> 
> _______________________________________________
> I-D-Announce mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html or
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> _______________________________________________
> Teas mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/teas