Re: [PATCH net-next] ipv6: Implement limits on hop by hop and destination options

2017-05-12 Thread Tom Herbert
On Fri, May 12, 2017 at 8:38 AM, David Miller wrote: > From: Tom Herbert > Date: Wed, 10 May 2017 14:33:19 -0700 > >> RFC 2460 (IPv6) defines hop by hop options and destination options >> extension headers. Both of these carry a list of TLVs which is >>

Re: [PATCH net-next] ipv6: Implement limits on hop by hop and destination options

2017-05-12 Thread David Miller
From: Tom Herbert Date: Wed, 10 May 2017 14:33:19 -0700 > RFC 2460 (IPv6) defines hop by hop options and destination options > extension headers. Both of these carry a list of TLVs which is > only limited by the maximum length of the extension header (2048 > bytes). By the

[PATCH net-next] ipv6: Implement limits on hop by hop and destination options

2017-05-10 Thread Tom Herbert
RFC 2460 (IPv6) defines hop by hop options and destination options extension headers. Both of these carry a list of TLVs which is only limited by the maximum length of the extension header (2048 bytes). By the spec a host must process all the TLVs in these options, however these could be used as a