Re: [Int-area] Comment on draft-ietf-intarea-frag-fragile-02

2019-02-12 Thread Erik Kline
> Most network providers abide by the policy that you describe. If all of their > interior links support an MTU of N, their access links support an MTU of N > minus M, where M is the highest possible encapsulation overhead. Ah, well, if they already do this then perhaps there doesn't need to be

Re: [Int-area] Comment on draft-ietf-intarea-frag-fragile-02

2019-02-12 Thread Ron Bonica
Hi Eric, Most network providers abide by the policy that you describe. If all of their interior links support an MTU of N, their access links support an MTU of N minus M, where M is the highest possible encapsulation overhead. This guarantees that MTU issues never occur on interior links.

Re: [Int-area] Comment on draft-ietf-intarea-frag-fragile-02

2019-02-12 Thread Tom Herbert
On Tue, Feb 12, 2019 at 10:26 AM Erik Kline wrote: > > I think in that case it's just ensuring the MTU given to the customer > via their access link can be carried through their network without, or > which a minimum of, fragmentation. > > I finally found some text to which I was referred, in 3GPP

Re: [Int-area] Comment on draft-ietf-intarea-frag-fragile-02

2019-02-12 Thread Erik Kline
I think in that case it's just ensuring the MTU given to the customer via their access link can be carried through their network without, or which a minimum of, fragmentation. I finally found some text to which I was referred, in 3GPP TS 29.060 (GTP) v15.2.0 section 13.2: All backbone links

[Int-area] I-D Action: draft-ietf-intarea-frag-fragile-09.txt

2019-02-12 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Internet Area Working Group WG of the IETF. Title : IP Fragmentation Considered Fragile Authors : Ron Bonica Fred Baker