Return-Path: <noreply@ietf.org>
X-Original-To: int-area@ietf.org
Delivered-To: int-area@mail2.ietf.org
Received: from [10.244.6.108] (unknown [4.156.85.76])
	by mail2.ietf.org (Postfix) with ESMTP id 783F9EAC8A9E;
	Thu,  7 May 2026 12:17:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1778181479; bh=3RreLaG8jOrWUOLABWCJ1pTlLdLiYg/no6mMSHfmUCw=;
	h=From:To:Cc:Subject:Reply-To:Date;
	b=Q/IfOO2/1Qi9cBKeFDCs0SyiAsJQmFAaMcKQSXXqjbO7H8Fvo/geXjIrHobDLdGmn
	 RcPli/+4crAhzR1MwAgwUUXD9YMmKQfkBx372uZF2GNbkSsEEC8rfkL1lSqk1hbRJv
	 jzeCk9my1OfZk1sYEN1JWbvkkT8xGjsBdqVMY7Xk=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mohamed Boucadair via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.63.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: 
 <177818147932.1370621.9414802574519265766@dt-datatracker-787b78d5f6-p2rl2>
Date: Thu, 07 May 2026 12:17:59 -0700
Message-ID-Hash: 4M6PCSBZHFLQNL7EYPLTBR6X2MDSWC4G
X-Message-ID-Hash: 4M6PCSBZHFLQNL7EYPLTBR6X2MDSWC4G
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency;
 loop; banned-address; member-moderation; header-match-int-area.ietf.org-0;
 nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size;
 news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-intarea-proxy-config@ietf.org, int-area@ietf.org,
 intarea-chairs@ietf.org, meral.shirazipour@ericsson.com
X-Mailman-Version: 3.3.9rc6
Reply-To: Mohamed Boucadair <mohamed.boucadair@orange.com>
Subject: =?utf-8?q?=5BInt-area=5D_Mohamed_Boucadair=27s_Abstain_on_draft-ietf-intarea?=
	=?utf-8?q?-proxy-config-13=3A_=28with_COMMENT=29?=
List-Id: IETF Internet Area WG Mailing List <int-area.ietf.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/int-area/mdRh9usic-ib4lfIY2R2qUbRNZM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Owner: <mailto:int-area-owner@ietf.org>
List-Post: <mailto:int-area@ietf.org>
List-Subscribe: <mailto:int-area-join@ietf.org>
List-Unsubscribe: <mailto:int-area-leave@ietf.org>

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/



