Re: [DMM] 6.6. T.M.GTP4.D description (Re: I-D Action: draft-ietf-dmm-srv6-mobile-uplane-05.txt

[Kentaro Ebisawa]

> Actually no, because it is assumed that the prefix of B’ could be a SID
for End.GTP4.E instantiated in SRGW. But you’re correct the B’ doesn’t need
to be filled with arg.mob.session.

So the assumption here is that both T.M.GTP4.D and End.M.GTP4.E are
instantiated on the same SRGW.
If that's what you intend,  considering B' doesn't need arg.mob.session, it
might be more natural to say like below, since the source IPv6 of the
packet translated by T.M.GTP4.D corresponds to S' mentioned in 6.5.
End.M.GTP4.E.
(And since GTP-U is uni-directional, T.M.GTP4.D and End.M.GTP4.E might not
be instantiated on the same SRGW. e.g. for scaling purpose)

If End.M.GTP4.E is also instantiated on the SR gateway, the Source UPF
Prefix of B' SHOULD be SRGW-IPv6-LOC-FUNC of End.M.GTP4.E SID
instantiated on the SR gateway.


Just my two cents.
-- 
Kentaro Ebisawa 


On Mon, Jul 8, 2019 at 11:50 PM Satoru Matsushima <
satoru.matsush...@gmail.com> wrote:

> Thanks Kentaro for you prompt review prior to my announce. :-)
>
> Thank you for updating the draft. Nice to see T.M.Tmap was renamed to
> T.M.GTP4.D corresponding to End.M.GTP4.E. :)
>
>
> It helps to improve consistency of the draft, thanks.
>
> Some feedback about the updated description.
>
> > 6.6. T.M.GTP4.D
> > ...
> > The prefix of B’ SHOULD be an End.M.GTP4.E SID with its format
> > instantiated at an SR gateway with the IPv4 SA of the receiving
> > packet.
>
> "The B’" is IPv6 SA so I think this should correspond to S' in
> End.M.GTP4.E rather than to SID.
>
>
> Actually no, because it is assumed that the prefix of B’ could be a SID
> for End.GTP4.E instantiated in SRGW. But you’re correct the B’ doesn’t need
> to be filled with arg.mob.session.
>
> Cheers,
> --satoru
>
> So it might be more clear to depict the packet format (diagram) again and
> mention B' has the following format with the IPv4 SA of the receiving
> packet.
>
> 0 127
> +--++--+
> | Source UPF Prefix|IPv4 SA | any bit pattern(ignored) |
> +--++--+
>128-a-b a b
>
> --
> Kentaro Ebisawa 
>
> -- Original Message --
> From: internet-dra...@ietf.org
> To: i-d-annou...@ietf.org
> Cc: dmm@ietf.org
> Sent: 2019/07/08 21:16:07
> Subject: [DMM] I-D Action: draft-ietf-dmm-srv6-mobile-uplane-05.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Distributed Mobility Management WG of the
> IETF.
>
>Title   : Segment Routing IPv6 for Mobile User Plane
>Authors : Satoru Matsushima
>  Clarence Filsfils
>  Miya Kohno
>  Pablo Camarillo
>  Daniel Voyer
>  Charles E. Perkins
> Filename: draft-ietf-dmm-srv6-mobile-uplane-05.txt
> Pages   : 28
> Date: 2019-07-08
>
> Abstract:
>   This document shows the applicability of SRv6 (Segment Routing IPv6)
>   to the user-plane of mobile networks.  The network programming nature
>   of SRv6 accomplish mobile user-plane functions in a simple manner.
>   The statelessness of SRv6 and its ability to control both service
>   layer path and underlying transport can be beneficial to the mobile
>   user-plane, providing flexibility, end-to-end network slicing and SLA
>   control for various applications.  This document describes the SRv6
>   mobile user plane behavior and defines the SID functions for that.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dmm-srv6-mobile-uplane/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-dmm-srv6-mobile-uplane-05
> https://datatracker.ietf.org/doc/html/draft-ietf-dmm-srv6-mobile-uplane-05
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dmm-srv6-mobile-uplane-05
>
>
> 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/
>
> ___
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm
>
> ___
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm
>
>
___
dmm mailing list
dmm@ietf.org
https://www.ietf.org/mailman/listinfo/dmm

Re: [DMM] 6.6. T.M.GTP4.D description (Re: I-D Action: draft-ietf-dmm-srv6-mobile-uplane-05.txt

[Satoru Matsushima]

Thanks Kentaro for you prompt review prior to my announce. :-)

> Thank you for updating the draft. Nice to see T.M.Tmap was renamed to 
> T.M.GTP4.D corresponding to End.M.GTP4.E. :)

It helps to improve consistency of the draft, thanks.

> Some feedback about the updated description.
> 
> > 6.6. T.M.GTP4.D
> > ...
> > The prefix of B’ SHOULD be an End.M.GTP4.E SID with its format
> > instantiated at an SR gateway with the IPv4 SA of the receiving
> > packet.
> 
> "The B’" is IPv6 SA so I think this should correspond to S' in End..M.GTP4.E 
> rather than to SID.

Actually no, because it is assumed that the prefix of B’ could be a SID for 
End.GTP4.E instantiated in SRGW. But you’re correct the B’ doesn’t need to be 
filled with arg.mob.session.

Cheers,
--satoru

> So it might be more clear to depict the packet format (diagram) again and 
> mention B' has the following format with the IPv4 SA of the receiving packet.
> 
> 0 127
> +--++--+
> | Source UPF Prefix|IPv4 SA | any bit pattern(ignored) |
> +--++--+
>128-a-b a b
> 
> -- 
> Kentaro Ebisawa 
> 
> -- Original Message --
> From: internet-dra...@ietf.org
> To: i-d-annou...@ietf.org
> Cc: dmm@ietf.org
> Sent: 2019/07/08 21:16:07
> Subject: [DMM] I-D Action: draft-ietf-dmm-srv6-mobile-uplane-05.txt
> 
>>  
>> A New Internet-Draft is available from the on-line Internet-Drafts 
>> directories.
>> This draft is a work item of the Distributed Mobility Management WG of the 
>> IETF.
>>  
>>Title   : Segment Routing IPv6 for Mobile User Plane
>>Authors : Satoru Matsushima
>>  Clarence Filsfils
>>  Miya Kohno
>>  Pablo Camarillo
>>  Daniel Voyer
>>  Charles E. Perkins
>> Filename: draft-ietf-dmm-srv6-mobile-uplane-05.txt
>> Pages   : 28
>> Date: 2019-07-08
>>  
>> Abstract:
>>   This document shows the applicability of SRv6 (Segment Routing IPv6)
>>   to the user-plane of mobile networks.  The network programming nature
>>   of SRv6 accomplish mobile user-plane functions in a simple manner.
>>   The statelessness of SRv6 and its ability to control both service
>>   layer path and underlying transport can be beneficial to the mobile
>>   user-plane, providing flexibility, end-to-end network slicing and SLA
>>   control for various applications.  This document describes the SRv6
>>   mobile user plane behavior and defines the SID functions for that.
>>  
>>  
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-dmm-srv6-mobile-uplane/
>>  
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-dmm-srv6-mobile-uplane-05
>> https://datatracker.ietf.org/doc/html/draft-ietf-dmm-srv6-mobile-uplane-05
>>  
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-dmm-srv6-mobile-uplane-05
>>  
>>  
>> 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/
>>  
>> ___
>> dmm mailing list
>> dmm@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmm
> ___
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm
___
dmm mailing list
dmm@ietf.org
https://www.ietf.org/mailman/listinfo/dmm

Re: [DMM] IETF105 - Call for agenda items

[Sri Gundavelli (sgundave)]

Gentle reminder. Please send your requests by 11th of July.


Sri


On 6/30/19, 10:02 AM, "dmm on behalf of Sri Gundavelli (sgundave)"
 wrote:

>Folks:
>
>We are planning to have a f2f DMM WG meeting at IETF-105. It is currently
>scheduled for Wednesday, 24 July 2019, Morning Session I 1000-1200.
>If you have any topics to present, please send your request to the chairs
>(as a response to this email) with the following information.
>
>
>>>Topic Name:
>>>Presenter Name:
>>>Time:
>>>Draft Reference (if any):
>
>
>- Dapeng & Sri
>>
>>
>>
>
>___
>dmm mailing list
>dmm@ietf.org
>https://www.ietf.org/mailman/listinfo/dmm

___
dmm mailing list
dmm@ietf.org
https://www.ietf.org/mailman/listinfo/dmm

[DMM] 6.6. T.M.GTP4.D description (Re: I-D Action: draft-ietf-dmm-srv6-mobile-uplane-05.txt

[Kentaro Ebisawa]

Hi,

Thank you for updating the draft. Nice to see T.M.Tmap was renamed to 
T.M.GTP4.D corresponding to End.M.GTP4.E. :)


Some feedback about the updated description.

> 6.6. T.M.GTP4.D
> ...
> The prefix of B’ SHOULD be an End.M.GTP4.E SID with its format
> instantiated at an SR gateway with the IPv4 SA of the receiving
> packet.

"The B’" is IPv6 SA so I think this should correspond to S' in 
End.M.GTP4.E rather than to SID.
So it might be more clear to depict the packet format (diagram) again 
and mention B' has the following format with the IPv4 SA of the 
receiving packet.


0 127
+--++--+
| Source UPF Prefix|IPv4 SA | any bit pattern(ignored) |
+--++--+
   128-a-b a b

--
Kentaro Ebisawa 

-- Original Message --
From: internet-dra...@ietf.org
To: i-d-annou...@ietf.org
Cc: dmm@ietf.org
Sent: 2019/07/08 21:16:07
Subject: [DMM] I-D Action: draft-ietf-dmm-srv6-mobile-uplane-05.txt



A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Distributed Mobility Management WG of 
the IETF.


   Title   : Segment Routing IPv6 for Mobile User Plane
   Authors : Satoru Matsushima
 Clarence Filsfils
 Miya Kohno
 Pablo Camarillo
 Daniel Voyer
 Charles E. Perkins
Filename: draft-ietf-dmm-srv6-mobile-uplane-05.txt
Pages   : 28
Date: 2019-07-08

Abstract:
  This document shows the applicability of SRv6 (Segment Routing IPv6)
  to the user-plane of mobile networks.  The network programming nature
  of SRv6 accomplish mobile user-plane functions in a simple manner.
  The statelessness of SRv6 and its ability to control both service
  layer path and underlying transport can be beneficial to the mobile
  user-plane, providing flexibility, end-to-end network slicing and SLA
  control for various applications.  This document describes the SRv6
  mobile user plane behavior and defines the SID functions for that.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmm-srv6-mobile-uplane/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-dmm-srv6-mobile-uplane-05
https://datatracker.ietf.org/doc/html/draft-ietf-dmm-srv6-mobile-uplane-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dmm-srv6-mobile-uplane-05


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/

___
dmm mailing list
dmm@ietf.org
https://www.ietf.org/mailman/listinfo/dmm___
dmm mailing list
dmm@ietf.org
https://www.ietf.org/mailman/listinfo/dmm

[DMM] I-D Action: draft-ietf-dmm-5g-uplane-analysis-02.txt

[internet-drafts]

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Distributed Mobility Management WG of the IETF.

Title   : User Plane Protocol and Architectural Analysis on 
3GPP 5G System
Authors : Shunsuke Homma
  Takuya Miyasaka
  Satoru Matsushima
  Daniel Voyer
Filename: draft-ietf-dmm-5g-uplane-analysis-02.txt
Pages   : 39
Date: 2019-07-08

Abstract:
   This document analyzes the mobile user plane protocol and the
   architecture specified in 3GPP 5G documents.  The analysis work is to
   clarify those specifications, extract protocol and architectural
   requirements and derive evaluation aspects for user plane protocols
   on IETF side.  This work is corresponding to the User Plane Protocol
   Study work on 3GPP side.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmm-5g-uplane-analysis/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-dmm-5g-uplane-analysis-02
https://datatracker.ietf.org/doc/html/draft-ietf-dmm-5g-uplane-analysis-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dmm-5g-uplane-analysis-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/

___
dmm mailing list
dmm@ietf.org
https://www.ietf.org/mailman/listinfo/dmm

[DMM] I-D Action: draft-ietf-dmm-srv6-mobile-uplane-05.txt

[internet-drafts]

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Distributed Mobility Management WG of the IETF.

Title   : Segment Routing IPv6 for Mobile User Plane
Authors : Satoru Matsushima
  Clarence Filsfils
  Miya Kohno
  Pablo Camarillo
  Daniel Voyer
  Charles E. Perkins
Filename: draft-ietf-dmm-srv6-mobile-uplane-05.txt
Pages   : 28
Date: 2019-07-08

Abstract:
   This document shows the applicability of SRv6 (Segment Routing IPv6)
   to the user-plane of mobile networks.  The network programming nature
   of SRv6 accomplish mobile user-plane functions in a simple manner.
   The statelessness of SRv6 and its ability to control both service
   layer path and underlying transport can be beneficial to the mobile
   user-plane, providing flexibility, end-to-end network slicing and SLA
   control for various applications.  This document describes the SRv6
   mobile user plane behavior and defines the SID functions for that.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmm-srv6-mobile-uplane/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-dmm-srv6-mobile-uplane-05
https://datatracker.ietf.org/doc/html/draft-ietf-dmm-srv6-mobile-uplane-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dmm-srv6-mobile-uplane-05


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/

___
dmm mailing list
dmm@ietf.org
https://www.ietf.org/mailman/listinfo/dmm

Re: [DMM] New Version Notification for draft-rokui-5g-transport-slice-00.txt

[Rokui, Reza (Nokia - CA/Ottawa)]

Sure Takuya I will add them to the new version of the draft.

Cheers,
Reza

From: Takuya Miyasaka 
Date: Sunday, July 7, 2019 at 9:07 PM
To: Reza Rokui , "netsli...@ietf.org" 
, "rt...@ietf.org" , "ops...@ietf.org" 
, "t...@ietf.org" , "dmm@ietf.org" 

Subject: Re: [DMM] New Version Notification for 
draft-rokui-5g-transport-slice-00.txt


Hi Reza,

Thanks for your response and please see my comments below with [Taku].

Thanks,
Takuya
On 2019/07/04 23:51, Rokui, Reza (Nokia - CA/Ottawa) wrote:
Hi Takuya,
Very good question. The response is inline.

Reza


From: Takuya Miyasaka 

Date: Wednesday, July 3, 2019 at 7:54 AM
To: Reza Rokui , 
"netsli...@ietf.org" 
, 
"rt...@ietf.org" 
, 
"ops...@ietf.org" 
, 
"t...@ietf.org" , 
"dmm@ietf.org" 
Subject: Re: [DMM] New Version Notification for 
draft-rokui-5g-transport-slice-00.txt


Hi Reza,

Thanks for sharing this draft. I'm curious about how to bind/associate 
3GPP(RAN/Core) slice instance and Transport slice instance and section 5.2 of 
this draft describes as follows:

  o In order to have the connectivity between RAN1 and UPF1, the RAN
 and Core slices should be associated to Transport slice. This is
 also a by-product of the Transport slice connectivity interface
 when all allocated resources for access points (such as allocated
 VLAN IDs, IP addresses etc) are conveyed to RAN and Core Slices.
 This will be done by cordiantion between transport slice
 controller and E2E network slice controller.

As for this sentences, could you confirm if following procedures will be 
conducted between controllers in order to associate independent slice instances 
or not?
 - E2E Network Slice Controller sends a request on transport slice creation to 
Transport Controller (interface 10 of Fig.2)
 - Transport Controller creates transport slice instance and sends access point 
information(e.g. VLAN ID) to E2E Network Slice Controller
 - E2E Network Slice Controller sends a request on access point 
creation/modification to RAN/Core Controller
 - RAN/Core Controller create/modify access point on gNB/UPF respectively, 
which means gNB/UPF starts to attach adequate access point information(e.g. 
VLAN ID) on their user plane packet

[Reza] The above procedure is correct but this is one way to implement the 
binding (aka association) between RAN-Transport slices and Core-Transport 
slices.

[Taku] OK. If such kinds of procedures are taken at Core/RAN Controller, it 
might be better to describe such procedures in Section3.
  We also have to check if these access point information can be 
conveyed at the 3GPP defined interface between E2E Controller and Core/RAN 
Controller.

There are other ways to implement the binding. For example, the transport slice 
controller can populate the following two tables dynamically during the 
transport slice creation, modification or deletion and expose access to this 
table using open APIs. Then, the RAN/Core network functions or RAN/Core slice 
controllers can access these APIs to program the VLAN/IP/Labels.

  *   RAN-Transport mapping table: Which maps the RAN VLAN/IP address/MPLS 
Labels etc to network slice
  *   Core-Transport mapping table: Which maps the Core VLAN/IP address/MPLS 
Labels etc to network slice

[Taku] That sounds good.

  *



Thanks,
Takuya Miyasaka
KDDI Research
On 2019/07/02 23:06, Rokui, Reza (Nokia - CA/Ottawa) wrote:
Hi all,

This is to inform you that the following new draft has been submitted to ietf.
The goal of this draft is to demonstrate the role of ietf for 5g network 
slicing in area of transport slices.

Your review and feedback would be greatly appreciated.

Thanks,



Reza Rokui







On 2019-07-02, 9:30 AM, 
"internet-dra...@ietf.org" 
 wrote:





A new version of I-D, draft-rokui-5g-transport-slice-00.txt

has been successfully submitted by Reza Rokui and posted to the

IETF repository.



Name:   draft-rokui-5g-transport-slice

Revision: 00

Title:  5G Transport Slice Connectivity Interface

Document date:  2019-07-02

Group:  Individual Submission

Pages:  28
URL:
https://www.ietf.org/internet-drafts/draft-rokui-5g-transport-slice-00.txt
Status: 
https://datatracker.ietf.org/doc/draft-rokui-5g-transport-slice/
Htmlized:   
https://tools.ietf.org/html/draft-rokui-5g-transport-slice-00
Htmlized:   
https://datatracker.ietf.org/doc/html/draft-rokui-5g-transport-slice





Abstract:

   The 5G Network slicing is an approach to provide separate independent

   E2E logi