On Fri, Apr 29, 2022 at 06:57:26AM -0700, The IESG wrote: > > The IESG has received a request from the Application-Layer Traffic > Optimization WG (alto) to consider the following document: - 'A Cost Mode > Registry for the Application-Layer Traffic Optimization > (ALTO) Protocol' > <draft-ietf-alto-cost-mode-02.txt> as Proposed Standard > > 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 2022-05-13. Exceptionally, comments may > be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning > of the Subject line to allow automated sorting. This document is meeting a real need by fleshing out an extension point for ALTO that was previously over-constrained and not actually usable for extensions. The security considerations section currently just defers to the core ALTO procotol spec, RFC 7285. This seems appropriate, as this document is just opening up the extension point, but we might also consider providing specific encouragement for authors of new cost modes to document considerations unique to that cost mode. Hopefully such documents would already provide comprehensive security considerations, though, so it does not seem strictly needed for us to say anything here. -Ben -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
