This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

[ipv6-wg] [v6ops] Extension Headers / Impact on Security Devices

Previous message (by thread): [ipv6-wg] [v6ops] Extension Headers / Impact on Security Devices
Next message (by thread): [ipv6-wg] [v6ops] Extension Headers / Impact on Security Devices

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Ole Troan otroan at employees.org
Fri Jun 19 09:10:55 CEST 2015

>> Tell me this. Would you be happier if the fragmentation rule said that the first fragment had to contain the entire IPv6 header, plus the transport layer header (for ACL support)? I think Fernando would support such a statement (I think I have "heard" him make such a statement).
> 
> It would certainly make *me* happier…

done.
RFC7112.

cheers,
Ole
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: </ripe/mail/archives/ipv6-wg/attachments/20150619/23f44d8d/attachment.sig>

Previous message (by thread): [ipv6-wg] [v6ops] Extension Headers / Impact on Security Devices
Next message (by thread): [ipv6-wg] [v6ops] Extension Headers / Impact on Security Devices

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ipv6-wg Archives ]