Mohamed Boucadair has entered the following ballot position for draft-ietf-intarea-proxy-config-13: Abstain
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-intarea-proxy-config/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Hi all, The discussion revealed that the intended applicability scope is even more than I got when first reviewing the document. This claims to cover discovery of any proxy (including proxies that are widely deployed out there such SIP proxies and for which there are alrady plenty discovery mechanisms). I’m concerned as this is adding duplicated functionality, not backed by real operational problems/needs. I’m more concerned that we are adding a duplicated mechanism for the discovery of these mechanisms using a tool that is not deployed today (PvD). Cheers, Med (*) My previous ballot: https://mailarchive.ietf.org/arch/msg/int-area/hwQi9ThqisyEAANJJHx6ywCGSUw/ _______________________________________________ Int-area mailing list -- [email protected] To unsubscribe send an email to [email protected]
