Hi, I don't normally toot about my own RFCs but I think this one needs a little publicity. It's operationally important (IMHO) that people start asking their firewall vendors to get the handling of extension headers right. It won't happen overnight of course.
Key sentence: If a forwarding node discards a packet containing a standard IPv6 extension header, it MUST be the result of a configurable policy and not just the result of a failure to recognise such a header. If you prefer html-ized format: http://tools.ietf.org/html/rfc7045 Brian -------- Original Message -------- Subject: RFC 7045 on Transmission and Processing of IPv6 Extension Headers Date: Fri, 6 Dec 2013 10:54:05 -0800 (PST) From: rfc-edi...@rfc-editor.org To: ietf-annou...@ietf.org, rfc-d...@rfc-editor.org CC: drafts-update-...@iana.org, i...@ietf.org, rfc-edi...@rfc-editor.org A new Request for Comments is now available in online RFC libraries. RFC 7045 Title: Transmission and Processing of IPv6 Extension Headers Author: B. Carpenter, S. Jiang Status: Standards Track Stream: IETF Date: December 2013 Mailbox: brian.e.carpen...@gmail.com, jiangsh...@huawei.com Pages: 10 Characters: 21852 Updates: RFC 2460, RFC 2780 I-D Tag: draft-ietf-6man-ext-transmit-05.txt URL: http://www.rfc-editor.org/rfc/rfc7045.txt Various IPv6 extension headers have been standardised since the IPv6 standard was first published. This document updates RFC 2460 to clarify how intermediate nodes should deal with such extension headers and with any that are defined in the future. It also specifies how extension headers should be registered by IANA, with a corresponding minor update to RFC 2780. This document is a product of the IPv6 Maintenance Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php For downloading RFCs, see http://www.rfc-editor.org/rfc.html Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC -------------------------------------------------------------------- IETF IPv6 working group mailing list i...@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------