Fred,
Quite to the contrary, I have spent a good deal of time reviewing the SEAL
draft. (Although I am now one version behind. The document is now in version
61.)
SEAL attempts to solve many problems. These include:
- source address authentication
- detection of packet duplication and reordering
- fragmentation at a layer above IP
- MTU discovery
In order to solve all of these problems, SEAL invents good bit of protocol
machinery. Much of this machinery a) already exists at another layer and b) is
not required to solve the problem at hand. This makes SEAL a much more
heavyweight than the simple point solution that we seek.
Ron
>
> SEAL solves the problem too. Transport-mode SEAL took me 15 minutes to
> write, and is really just a couple of paragraphs. In addition to
> providing a universal sublayer that can handle any transport protocol
> 'X', SEAL also provides an RFC4821 path MTU probing facility. And, if
> ingress filtering is thought to be a problem, it also provides a data
> origin authentication facility.
>
> It seems Ron that you are trying to avoid a closer examination of SEAL.
>
>
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
