Re: [5gangip] New Version Notification for draft-xyzy-atick-gaps-00.txt

[Dino Farinacci <[e-mail]>]

On Jun 7, 2018, at 2:12 PM, FIGURELLE, TERRY F <[e-mail]> wrote:
> 
> The MTU mismatch?

Yes, thanks for the explaination. But what are the other two issues: “between vendors” and “between address families”.

Dino

> 
> We already have vendors working on auto-MTU adjust and working on device requirements so whenever it gets an updated MTU in PCO the device will honor it. We were told that this is something 3GPP would not be interested in since it is a temp deployment challenge not a long term challenge. Plus we require MRU>MTU so most elements can get a larger packet then they can send. We can set MTU per APN so the 5G APN is set to use full 1500 byte "Internet" MTU.
> 
> Thus you can have a network where legacy APN's stull do their thing then decide when/where to use larger MTU. IMS looks ripe for a larger than 1500 byte MTU. Those SIP messages can be huge. But we need to validate all the vendors can support this and work the details to get there.
> 
> Now if you can get the entire Internet to support more that 1500 byte MTU, you are better than me.
> 
> We worked a lot on MTU discovery but even for IPv6 this just doesn't pan out. I wish it did but realities sometimes suck and its taking way too long to get to all IPv6 ☹
> 
> Now if you meant something else please rephrase it concisely.
> 
>> -----Original Message-----
>> From: Dino Farinacci <[e-mail]>
>> Sent: Thursday, June 07, 2018 1:34 PM
>> To: FIGURELLE, TERRY F <[e-mail]>
>> Cc: Tom Herbert <[e-mail]>; Luigi Iannone <[e-mail]>;
>> 5GANGIP <[e-mail]>
>> Subject: Re: [5gangip] New Version Notification for draft-xyzy-atick-gaps-
>> 00.txt
>> 
>>> Apparently X2 handoffs not only can’t go between vendor and IP address
>> families they can’t go between MTU sizes. So we need to do all the tracking
>> areas in a market to avoid S1 handovers.
>> 
>> Do you think this is a problem worth solving?
>> 
>> Dino