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

2018-03-13 Thread Tom Herbert
On Mon, Mar 12, 2018 at 10:57 PM, Satoru Matsushima wrote: > Dear Sridhar, > > It’s nice to see you in DMM list as well. :-) > >> [...snip...] > > >> 1. Section 5.2.2 of the draft says, >> >> UPF2_in : (Z,A) -> UPF2 maps the flow w/ >>

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

2018-03-13 Thread John Kaippallimalil
Satoru, Thanks for the responses. In the Enhanced mode - section 5.2, it is still not clear (if or) how multiple UPFs on path would be programmed. 23.501, 5.6.4 discusses about a single PDU session with multiple PDU Session anchors. What would the SR path look like: gNB --> UPF1 --> UPF2 (2 s

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

2018-03-13 Thread Satoru Matsushima
Hello Tom, Thank you for your feedback. > ...snip... > - Pick a handful of representative formats, maybe something like five, > and do an an equivalent comparison. For instance, it should be easy to > deduce the equivalent packet formats for traditional mode in SR that > are needed for GTP and I

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

2018-03-13 Thread Dino Farinacci
> 2. For traditional mode (basic mode), could you please elaborate on the MTU > overhead being less than GTPU? GTPU encap MTU overhead = 20 octets outer IPv4 > header + 8 octets UDP header + 12 octets GTPU header + Extension header for > QFI. SRv6 encap MTU overhead = 40 octets IPv6 header + EH