Hello all, We wanted to make you aware of a document we submitted a while back --unfortunately *someone*[0] forgot to put -6man- somewhere in the title.
This document explains issues that *operators* have with "long header chains" and devices that need to see the L4 information. We understand that this is likely to be a controversial document, and will spark lively discussion[1]. W [0]: Ok, it was me… [1]: AKA Nomex underwear time. Begin forwarded message: > From: [email protected] > Subject: New Version Notification for draft-wkumari-long-headers-00.txt > Date: February 4, 2013 10:07:59 AM EST > To: [email protected] > Cc: [email protected], [email protected] > > > A new version of I-D, draft-wkumari-long-headers-00.txt > has been successfully submitted by Warren Kumari and posted to the > IETF repository. > > Filename: draft-wkumari-long-headers > Revision: 00 > Title: Operational Issues Associated With Long IPv6 Extension > Header Chains > Creation date: 2013-02-04 > WG ID: Individual Submission > Number of pages: 9 > URL: > http://www.ietf.org/internet-drafts/draft-wkumari-long-headers-00.txt > Status: http://datatracker.ietf.org/doc/draft-wkumari-long-headers > Htmlized: http://tools.ietf.org/html/draft-wkumari-long-headers-00 > > > Abstract: > This document outlines a set of issues with the use of long IPv6 > extension header chains. It considers their use in the context of > today's IPv6 Internet and potential interaction with forwarding > devices that require upper-layer headers. > > > > > The IETF Secretariat > -- Do not meddle in the affairs of dragons, for you are crunchy and taste good with ketchup. -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
