On Fri, Jun 14, 2013 at 2:19 PM, Tony Hain <[email protected]> wrote:
> Focus on the real operational requirement (firewall functionality), then > make sure that the constraint automatically tracks evolution in firewall > functionality. Getting there leads to L4 in the first fragment, and > anything > else leads to artificial constraints that will need to be redone, if that > is > even possible. > The problem with that approach is that for a very substantial fraction of Internet backbones, the real operational requirement is substantially *less* capable than what is written in RFC 2460 and than what you propose here.
-------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
