Re: [Teas] Moving forward with draft-ietf-teas-ietf-network-slices

Hi Adrian,

Thanks for your hard work for the slice architecture.

I have a little comments,  as we know, there are slice scenarios that have nothing to do with VPN, for example, multiple slices in backbone can be used for connections between metros. So it is strange to put a usecase (VPN+) of slice be as a scheme for slice architecture, as section 6.3 described.

Regards,

PSF

原始邮件

发件人：AdrianFarrel
收件人：teas@ietf.org;
日 期 ：2021年05月04日 17:11
主 题 ：[Teas] Moving forward with draft-ietf-teas-ietf-network-slices

Several important points:

1. This is work in progress and you are all allowed to comment on any of the
text. Changes made here are based on text floated on the list and comments
received, but this is NOT confirmed consensus and is still open for
modification.

2. You can see the changes this time around at
https://www.ietf.org/rfcdiff?url1=draft-ietf-teas-ietf-network-slices-01&url
2=draft-ietf-teas-ietf-network-slices-02&difftype=--hwdiff
   a. Eric has retired, but is still following the work
   b. No longer need the Editor's Note in Section 1
   c. "Consumer" vs "customer". I have made this consistent (we only need to
use one
        term). I selected "Customer" because that seemed best, but I know
some people
        prefer "consumer". Please discuss if you are not happy.
   d. Changes for Isolation text and introduction of "SLE" for
"unquantifiable objectives" 
        as proposed on the list, with edits for the comments received
   e. Changes for realisation of network slices as proposed on list, with
edits for the
       comments received.
   f. Various small editorials
   g. Fix ordering of end-matter sections
   h. Remove "Unused Material" Appendix (as it was unused :-)

3. Next work topics (in no particular order)
   a. Definition of a Network Slice Service (based on a discussion started
on the list by John Drake)
   b. Definition of End Points (ditto)
   c. Resolve "duplication" between Figure 1 and Figure 3 as well as
surrounding text
   d. Propose a functional architecture for realising network slices

4. I think that at least 3d will need a meeting. If 3a or 3b gets a
significant level of
    discussion on the list then it should also have a meeting. I will try to
give a week's
    notice for any meeting and pick a time that works for California and
Beijing. But,
    please note that you don't have to come to a meeting to have an opinion
- that is
    what the mailing list is for.

Best,
Adrian

-----Original Message-----
From: Teas <teas-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
Sent: 04 May 2021 09:56
To: i-d-announce@ietf.org
Cc: teas@ietf.org
Subject: [Teas] I-D Action: draft-ietf-teas-ietf-network-slices-02.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-02.txt
    Pages           : 32
    Date            : 2021-05-04

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-02
https://datatracker.ietf.org/doc/html/draft-ietf-teas-ietf-network-slices-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-ietf-network-slices-02

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/

_______________________________________________
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