Hi James,

> -----Original Message-----
> From: ipv6-boun...@ietf.org [mailto:ipv6-boun...@ietf.org] On Behalf Of
> james woodyatt
> Sent: Friday, June 28, 2013 1:41 PM
> To: 6man
> Subject: Re: New Version Notification for draft-bonica-6man-frag-
> deprecate-00.txt
> 
> On Jun 28, 2013, at 12:32 , Templin, Fred L <fred.l.temp...@boeing.com>
> wrote:
> > [I wrote:]
> >>
> >> I'm also excited to learn about how we're going to add PLPMTUD to
> GRE
> >> and tunnel-mode IPsec ESP so they have some hope of using path MTU
> >> larger than 1280 octets.
> >
> > https://datatracker.ietf.org/doc/draft-templin-intarea-seal/
> 
> I'm not sure I read this comment correctly.  Are you suggesting that we
> should replace tunnel-mode ESP and GRE tunnels with SEAL in order to
> get PLPMTUD to work?

No, I am saying that these and others are compatible with SEAL.
The SEAL header has a "next header" field exactly like an IPv6
extension header, and that next header could be IPsec, GRE, etc.
Used in this way, the SEAL header has the same footprint as an
IPv6 fragmentation header.

That said, SEAL could be used in place of other tunnel types like
GRE and IPv6/IPv6. How they all fit together is something we should
discuss either here or in intarea.

> Are we all *really* okay with just trashing ESP
> and GRE like that?  Maybe we should be moving to deprecate those too?

Not what I am suggesting. SEAL+GRE, SEAL+IPsec-ESP, etc. all work
just fine.

Thanks - Fred
fred.l.temp...@boeing.com
 
> --
> james woodyatt <j...@apple.com>
> core os networking
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to