Dear all, This draft purports to end an "endless cycle": I quote "Break the endless cycle that resulted in HBH being a DOS vector." RFC 9098 explained why potential DOS vectors exist. To me, this draft draft-ietf-v6ops-hbh doesn't resolve the issues mentioned in RFC 9098. Section 4 "Modern Router Architecture" seems too simplistic. I suspect many router implementers wouldn't recognize their own work in this phrasing. Section 9 is under-specified to the point I considered it problematic. Kind regards, Job On Mon, Aug 19, 2024 at 02:47:53PM -0700, The IESG wrote: > > The IESG has received a request from the IPv6 Operations WG (v6ops) to > consider the following document: - 'Operational Issues with Processing of the > Hop-by-Hop Options Header' > <draft-ietf-v6ops-hbh-10.txt> as Informational RFC > > The IESG plans to make a decision in the next few weeks, and solicits final > comments on this action. Please send substantive comments to the > last-call@xxxxxxxx mailing lists by 2024-09-02. Exceptionally, comments may > be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning > of the Subject line to allow automated sorting. > > Abstract > > > This document describes the processing of the Hop-by-Hop Options > Header (HBH) in current routers in the aspects of standards > specification, common implementations, and default operations. This > document outlines reasons why the Hop-by-Hop Options Header is rarely > utilized in current networks. In addition, this document describes > how HBH Options Header could be used as a powerful mechanism allowing > deployment and operations of new services requiring a more optimized > way to leverage network resources of an infrastructure. The purpose > of this draft is to document reasons why HBH Options Header is rarely > used within networks. It motivates the benefits and requirements > needed to enable wider use of HBH Options. > > > > > > The file can be obtained via > https://datatracker.ietf.org/doc/draft-ietf-v6ops-hbh/ > > > > No IPR declarations have been submitted directly on this I-D. > > > > > > _______________________________________________ > IETF-Announce mailing list -- ietf-announce@xxxxxxxx > To unsubscribe send an email to ietf-announce-leave@xxxxxxxx -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
