From nobody Tue Apr 4 08:01:58 2017 Return-Path: X-Original-To: netslices@ietfa.amsl.com Delivered-To: netslices@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A31F41296E5 for ; Tue, 4 Apr 2017 08:01:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.7 X-Spam-Level: X-Spam-Status: No, score=-3.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NFMGB7kZ_SH9 for ; Tue, 4 Apr 2017 08:01:52 -0700 (PDT) Received: from xenon23.um.es (xenon23.um.es [155.54.212.163]) by ietfa.amsl.com (Postfix) with ESMTP id ACA6D1296DF for ; Tue, 4 Apr 2017 08:01:51 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by xenon23.um.es (Postfix) with ESMTP id 8061135CE for ; Tue, 4 Apr 2017 17:01:49 +0200 (CEST) X-Virus-Scanned: by antispam in UMU at xenon23.um.es Received: from xenon23.um.es ([127.0.0.1]) by localhost (xenon23.um.es [127.0.0.1]) (amavisd-new, port 10024) with LMTP id uhxiaqs6w6Uv for ; Tue, 4 Apr 2017 17:01:49 +0200 (CEST) Received: from mail-qk0-f177.google.com (mail-qk0-f177.google.com [209.85.220.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: fabrizio.ippoliti@um.es) by xenon23.um.es (Postfix) with ESMTPSA id 2ECBC70CA for ; Tue, 4 Apr 2017 17:01:48 +0200 (CEST) Received: by mail-qk0-f177.google.com with SMTP id g195so71805608qke.2 for ; Tue, 04 Apr 2017 08:01:48 -0700 (PDT) X-Gm-Message-State: AFeK/H1yylXfOU8vqhosSWVneO0lWLosq1Wo0jIzKQDKl/uD7CAVl5F6R1+KIsfNcRgFIZhSrACnL/yQ+oGQdQ== X-Received: by 10.55.165.2 with SMTP id o2mr3457875qke.101.1491318107416; Tue, 04 Apr 2017 08:01:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.142.69 with HTTP; Tue, 4 Apr 2017 08:01:27 -0700 (PDT) In-Reply-To: <6E81EE37-7EA6-4B92-95DE-76DC94E81D02@sit.fraunhofer.de> References: <2304F3B5-DAD9-4B9A-BC24-11BDA3D30A0B@huawei.com> <6E81EE37-7EA6-4B92-95DE-76DC94E81D02@sit.fraunhofer.de> From: Fabrizio Ippoliti Date: Tue, 4 Apr 2017 17:01:27 +0200 X-Gmail-Original-Message-ID: Message-ID: To: Henk Birkholz Cc: netslices@ietf.org Content-Type: multipart/alternative; boundary=94eb2c05fde80a39b7054c588ea2 Archived-At: Subject: Re: [Netslices] Slides for side meeting X-BeenThere: netslices@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "This list is intended for discussion and review of network slicing at IETF." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Apr 2017 15:01:56 -0000 --94eb2c05fde80a39b7054c588ea2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello everyone, Like Henk, I would like to know if any audio - at least - recording would be released. Thanks, Best regards 2017-03-28 1:38 GMT+02:00 Henk Birkholz : > Hello, > > will there be audio & video recording available afterwards? > > Viele Gr=C3=BC=C3=9Fe, > > Henk > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > _______________________________________________ > Netslices mailing list > Netslices@ietf.org > https://www.ietf.org/mailman/listinfo/netslices > > --94eb2c05fde80a39b7054c588ea2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello everyone,

Like Henk, I would like= to know if any audio - at least - recording would be released.
<= br>
Thanks,
Best regards=C2=A0

2017-03-28 1:38 GMT+02:00 Henk= Birkholz <henk.birkholz@sit.fraunhofer.de>:
Hello,

will there be audio & video recording available afterwards?

Viele Gr=C3=BC=C3=9Fe,

Henk
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.=
_______________________________________________
Netslices mailing list
Netslices@ietf.org
https://www.ietf.org/mailman/listinfo/netslices<= /a>


--94eb2c05fde80a39b7054c588ea2-- From nobody Wed Apr 5 04:59:51 2017 Return-Path: X-Original-To: netslices@ietfa.amsl.com Delivered-To: netslices@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 809931200F1 for ; Wed, 5 Apr 2017 04:59:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.221 X-Spam-Level: X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BOZLwGwOcyUH for ; Wed, 5 Apr 2017 04:59:45 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAA9E126C83 for ; Wed, 5 Apr 2017 04:59:41 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DEE29279; Wed, 05 Apr 2017 11:59:39 +0000 (GMT) Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 5 Apr 2017 12:59:38 +0100 Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.223]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0235.001; Wed, 5 Apr 2017 19:59:22 +0800 From: "Dongjie (Jimmy)" To: "netslices@ietf.org" CC: "stewart.bryant" , "Kiran.Makhijani" , Alex Galis Thread-Topic: IETF98 netslices side meeting minutes and audio record Thread-Index: AdKuA9+AKJ/LGip/RpiqJAXCx9JOjQ== Date: Wed, 5 Apr 2017 11:59:21 +0000 Message-ID: <76CD132C3ADEF848BD84D028D243C92793623E89@NKGEML515-MBS.china.huawei.com> Accept-Language: en-US, zh-CN Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.130.151.75] Content-Type: multipart/alternative; boundary="_000_76CD132C3ADEF848BD84D028D243C92793623E89NKGEML515MBSchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090205.58E4DC2C.000B, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.5.223, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 7f9e5c0c9498cd66c34007b30c0b8fe6 Archived-At: Subject: [Netslices] IETF98 netslices side meeting minutes and audio record X-BeenThere: netslices@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "This list is intended for discussion and review of network slicing at IETF." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Apr 2017 11:59:49 -0000 --_000_76CD132C3ADEF848BD84D028D243C92793623E89NKGEML515MBSchi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear all, Here are the merged minutes of the network slicing side meeting in IETF98. = Please let us know if you have any comments or corrections. The audio record of the side meeting is at: https://ietf.webex.com/ietf/ldr= .php?RCID=3Dbcd84b0593be0f1c7afda8385c105704. Unfortunately the quality is = not good. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Network Slicing Side Meeting in IETF98 2017.3.27 18:15-21:15, Vevey 1/2, Chicago Chairs: Stewart Bryant (Huawei), Alex Galis (UCL) Alex briefly introduces the purpose of the side meeting. 1. Introduction and problem statement , Alex Netslicing is not new, now move fast with 5G. Key characteristics of network slicing Network slicing work items at IETF Q&A: None 2. 3GPP 5G network slicing use cases, Xavier Introduce the architecture of NS in 3GPP Core network slicing RAN slicing: early study indicates mainly by preconfigured Q&A: Omar: In 3GPP, how many slices can be provided on the RAN side? Speaker: Don't know Q: Does RAN selects core network slices? Speaker: No. RAN selects the functions of the core, CCNF chooses the core s= lice. Q: Does CCNF provide mobility management function? A: Yes. John Strassner: Is there a model driven approach to orchestration? Data com= es from different parts of the networks. From management or orchestration p= oint of view, have you done modeling of the functions, for interoperability= ? 3GPP-IETF liaison person: Be aware that deadline of Phase 1 of 5G in 3GPP i= s June 2018. The results from IETF should go hand in hand with 3GPP. Q: the title is use case, but content is more of architecture, would need = more use cases to discuss. A: there is another use case draft to be presented. Hannu: From the presentation, what points are you pointing out for IETF to = consider? Speaker: No answer for this yet. 3.Network Slicing use cases, Kiran eMBB: large bandwidth, VR/AR ask for low latency uRLLC: latency mMTC: other type use case: ask for contribution of use case Q&A: George: from 5G deployment point of view, it is also important to have vert= ical industry involved. 4. ICN use-case, Ravi Q&A: Q: Is this pure ICN or over IP? A: This is over IP. Q: Is SFC used in this slicing use case? A: Not really. User asks for content from some cache. But SFC may not be in= volved. 5. Network Slicing Architecture, Liang Geng Introduces reference architecture and key components of network slicing Q&A Q: what is the formal definition of network slice? A: combined resources of connectivity, network functions, computing, storag= e and some exposed provisioning. Another definition: Logical segment of net= works. Q: slice can be small, medium and large. The current definition is too wide= . Can we narrow down a little bit? A: Welcome input to the definition Igor: can we define net slice as distributed data centers? A: Need to include DCI. Sue: For dynamic control and management, the recent work on revised datasto= re etc. in netmod/netconf may be relevant, also the topology and rib models= in i2rs and teas, suggest to consider align with these works in next step. 6. Network slicing, technique viewpoints and functional roles, Pedro Requirements: flexibility, plasticity, composability Q&A: none 7. How to slice network, a slicing for IETF, Hannu Q&A Q: NFV works on slicing but haven't seen how that works. How IETF interacts= with NFV? Do not reinvent what NFV does. Q: How does dynamic slicing work? A: It is orchestration work Jie: What does multi-cites mean? Is low latency slice just one of the use c= ases? A: Multi-site means topology not only p2p, but with customized connectivity= . Yes low latency is just one case of transport slice, can be slices with o= ther requirement. Q: there is a work being done on multi-domain orchestration and slicing (5G= EX). 8. Autonomous Transport network, Qiang Li Q&A Igor: identify one of the gap: the function to discover, negotiate and abst= ract the view of the topology, there is related work in teas wg (ACTN). 9. ACTN and slicing, Gert What is network slicing, and what is not? Quote definition of network slicing in NFV 5G white paper What slices are not: probably a broadcast mechanism Q&A: none 10. FPSM in dmm, Satoru Enable separation of data and control plane functions of mobile network Coordination between transport and mobile functions/services to form networ= k slice Q&A: none Open discussion: 1. Any of the topics relevant to IETF? A half in the room agree 2. Who is willing to work on document? Or who is willing to help to sc= ope the work in IETF? 3. Should we build the charter for BoF at next IETF? Dave Allan: Charter is good. Need to identify what is the scope, what is no= t in the scope of IETF. Young: TEAS and ACTN is making progress on network slicing (and telemetry),= need to identify gaps Geroge: A charter is needed, and write down what is out of scope, and prior= itize the work which is needed by other organizations. David Sinicrope: gap analysis should not only for IETF, but also understand= what other people are doing with gap analysis, avoid overlapping with othe= rs, may liaison with ITU-T SG13. Stewart: Finding critical technical points within scope of IETF is importan= t George: IETF needs to provide input to 3GPP ??: The use cases can apply to non-5G and 5G, the scope of our work may not= be limited by 3GPP 5G. 5G and non-5G, which use-cases are included in the scope? 5G - high capacity access network but it takes network and cloud. Peter Smith: Even without 5G, we still need an end-to-end network slicing m= echanism. Kiran: Need to identify what should to be standardized in IETF, the charter= . ??: Suggest to make the scope small so can match the pace of 5G requirement= on slicing. Gert: Not sure we share a common view of network slice, would be good to cl= arify this. Dave Allan: Not sure IETF needs a unique definition of network slice. Sugge= st to use industry definition so that IETF can help the industry and find t= he unique value. Gert: Maybe find another term for network slice in IETF. --_000_76CD132C3ADEF848BD84D028D243C92793623E89NKGEML515MBSchi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear all,

 

Here are the merged minutes of = the network slicing side meeting in IETF98. Please let us know if you have = any comments or corrections.

 

The audio record of the side me= eting is at: https://ie= tf.webex.com/ietf/ldr.php?RCID=3Dbcd84b0593be0f1c7afda8385c105704. Unfo= rtunately the quality is not good.

 

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D

Network Slicing Side Meeting in= IETF98

2017.3.27  18:15-21:15, Ve= vey 1/2, Chicago

 

Chairs: Stewart Bryant (Huawei)= , Alex Galis (UCL)

 

Alex briefly introduces the pur= pose of the side meeting.

 

1.     = ; Introduction and problem statement ,  Alex

Netslicing is not new, now move= fast with 5G.

Key characteristics of network = slicing

Network slicing work items at I= ETF

Q&A: None=

 

 

2.     = ; 3GPP 5G network slicing use cases,  Xavier

Introduce the architecture of N= S in 3GPP

Core network slicing=

RAN slicing: early study indica= tes mainly by preconfigured

Q&A:

Omar: In 3GPP, how many slices = can be provided on the RAN side?

Speaker: Don’t know<= /o:p>

Q: Does RAN selects core networ= k slices?

Speaker: No. RAN selects the fu= nctions of the core, CCNF chooses the core slice.

Q: Does CCNF provide mobility m= anagement function?

A: Yes.

John Strassner: Is there a mode= l driven approach to orchestration? Data comes from different parts of the = networks. From management or orchestration point of view, have you done mod= eling of the functions, for interoperability?

3GPP-IETF liaison person: Be aw= are that deadline of Phase 1 of 5G in 3GPP is June 2018. The results from I= ETF should go hand in hand with 3GPP.

Q:  the title is use case,= but content is more of architecture, would need more use cases to discuss.=

A: there is another use case dr= aft to be presented.

Hannu: From the presentation, w= hat points are you pointing out for IETF to consider?

Speaker: No answer for this yet= .

 

 

3.Network Slicing use cases,&nb= sp;  Kiran

eMBB: large bandwidth, VR/AR as= k for low latency

uRLLC: latency

mMTC:

other type use case:

ask for contribution of use cas= e

Q&A:

George: from 5G deployment poin= t of view, it is also important to have vertical industry involved.

 

 

4. ICN use-case,  Ravi

Q&A:

Q: Is this pure ICN or over IP?=

A: This is over IP.<= /span>

Q: Is SFC used in this slicing = use case?

A: Not really. User asks for co= ntent from some cache. But SFC may not be involved.

 

 

5. Network Slicing Architecture= ,  Liang Geng

Introduces reference architectu= re and key components of network slicing

Q&A

Q: what is the formal definitio= n of network slice?

A: combined resources of connec= tivity, network functions, computing, storage and some exposed provisioning= . Another definition: Logical segment of networks.

Q: slice can be small, medium a= nd large. The current definition is too wide. Can we narrow down a little b= it?

A: Welcome input to the definit= ion

Igor: can we define net slice a= s distributed data centers?

A: Need to include DCI.

Sue: For dynamic control and ma= nagement, the recent work on revised datastore etc. in netmod/netconf may b= e relevant, also the topology and rib models in i2rs and teas, suggest to c= onsider align with these works in next step.

 

 

6. Network slicing, technique v= iewpoints and functional roles,  Pedro

    Requirements= : flexibility, plasticity, composability

Q&A: none=

 

 

7. How to slice network, a slic= ing for IETF,  Hannu

Q&A

Q: NFV works on slicing but hav= en’t seen how that works. How IETF interacts with NFV? Do not reinven= t what NFV does.

Q: How does dynamic slicing wor= k?

A: It is orchestration work

Jie: What does multi-cites mean= ? Is low latency slice just one of the use cases?

A: Multi-site means topology no= t only p2p, but with customized connectivity. Yes low latency is just one c= ase of transport slice, can be slices with other requirement.

Q: there is a work being done o= n multi-domain orchestration and slicing (5GEX).

 

 

8. Autonomous Transport network= ,  Qiang Li

Q&A

Igor: identify one of the gap: = the function to discover, negotiate and abstract the view of the topology, = there is related work in teas wg (ACTN).

 

 

9. ACTN and slicing,  Gert=

What is network slicing, and wh= at is not?

Quote definition of network sli= cing in NFV 5G white paper

What slices are not: probably a= broadcast mechanism

Q&A: none=

 

 

10. FPSM in dmm,  Satoru

Enable separation of data and c= ontrol plane functions of mobile network

Coordination between transport = and mobile functions/services to form network slice

Q&A: none=

 

 

Open discussion:

1.     = ; Any of the topics relevant to IETF?  A half in the room agree

2.     = ; Who is willing to work on document? Or who is willing to help to scope th= e work in IETF?

3.     = ; Should we build the charter for BoF at next IETF?

 

Dave Allan: Charter is good. Ne= ed to identify what is the scope, what is not in the scope of IETF.

 

Young: TEAS and ACTN is making = progress on network slicing (and telemetry), need to identify gaps

 

Geroge: A charter is needed, an= d write down what is out of scope, and prioritize the work which is needed = by other organizations.

 

David Sinicrope: gap analysis s= hould not only for IETF, but also understand what other people are doing wi= th gap analysis, avoid overlapping with others, may liaison with ITU-T SG13= .

 

Stewart: Finding critical techn= ical points within scope of IETF is important

 

George: IETF needs to provide i= nput to 3GPP

 

??: The use cases can apply to = non-5G and 5G, the scope of our work may not be limited by 3GPP 5G.

 

5G and non-5G, which use-cases = are included in the scope?

 

5G – high capacity access= network but it takes network and cloud.

 

Peter Smith: Even without 5G, w= e still need an end-to-end network slicing mechanism.

 

Kiran: Need to identify what sh= ould to be standardized in IETF, the charter.

 

??: Suggest to make the scope s= mall so can match the pace of 5G requirement on slicing.<= /p>

 

Gert: Not sure we share a commo= n view of network slice, would be good to clarify this.

 

Dave Allan: Not sure IETF needs= a unique definition of network slice. Suggest to use industry definition s= o that IETF can help the industry and find the unique value.  

 

Gert: Maybe find another term f= or network slice in IETF.

--_000_76CD132C3ADEF848BD84D028D243C92793623E89NKGEML515MBSchi_--