Re: [v6ops] draft-taylor-v6ops-fragdrop WGLC

I think this is a useful review of the issues. I think it makes
operationally pertinant observations.

I think it stands reasonably neutrally in the 'frag or not' debate, because
both sides can inform themselves from it. I doubt its going to change many
people's minds on the fundamental question.

I think it helps inform the question(s) being asked. It made me think
harder about the potential for changes to fragments to include upper-layer
headers, and to what extent that kind of change might break things, or help
with the considerations of risk and load and capability in deployed
equipment.

I am a little worried the document makes unattributed statements about ASIC
and FPGA costs. I think they need to be fleshed out, because this kind of
unsubstantiated and unattributed comment can lead to people continuing to
assume things which applied once, to some vendors, but doesn't apply now
(consider the whole thing about secure disk wiping which was predicated on
a very specific generation of HDD hardware. Or, the "BGP is dying we need
locator+id" debate, which arguably stems from a false premise)

Having said that, if google employees say that they use systems on their
'edge' which do this, thats certainly attributed.

-G

On Mon, Aug 19, 2013 at 4:00 AM, Fred Baker <fred@cisco.com> wrote:

> This is to initiate a two week working group last call of
> http://tools.ietf.org/html/draft-taylor-v6ops-fragdrop.  Please read it
> now. If you find nits
> (spelling errors, minor suggested wording changes, etc), comment to the
> authors; if you find greater issues, such as disagreeing with a
> statement or finding additional issues that need to be addressed,
> please post your comments to the list.
>
> We are looking specifically for comments on the importance of the
> document as well as its content. If you have read the document and
> believe it to be of operational utility, that is also an important
> comment to make.
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>