[sipcore] Alissa Cooper's Discuss on draft-ietf-sipcore-callinfo-spam-04: (with DISCUSS)
Alissa Cooper via Datatracker <noreply@ietf.org> Wed, 02 October 2019 20:53 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: sipcore@ietf.org
Delivered-To: sipcore@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D8D11120018; Wed, 2 Oct 2019 13:53:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-sipcore-callinfo-spam@ietf.org, Brian Rosen <br@brianrosen.net>, sipcore-chairs@ietf.org, br@brianrosen.net, sipcore@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.104.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alissa Cooper <alissa@cooperw.in>
Message-ID: <157004961078.8961.7729070037801244717.idtracker@ietfa.amsl.com>
Date: Wed, 02 Oct 2019 13:53:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/mQn_R9VYqbKzkYAvCntvNvAvH7k>
Subject: [sipcore] Alissa Cooper's Discuss on draft-ietf-sipcore-callinfo-spam-04: (with DISCUSS)
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Oct 2019 20:53:31 -0000
Alissa Cooper has entered the following ballot position for draft-ietf-sipcore-callinfo-spam-04: Discuss 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/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-sipcore-callinfo-spam/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- (1) It seems to me that there is a privacy consideration that is not discussed in this document, namely the unwanted exposure of the call types to third parties. If I'm receiving a lot of calls from the debt collection agency and my UA displays that information in my call log for anyone who might have access to my phone, or an eavesdropper can glean that information from intercepting my SIP signaling, as a user I probably want to be able to tell my SIP provider to disable this. Perhaps this capability to request that certain Call-Info headers not be sent is captured generically in RFC 3261 (I don't remember), in which case pointing that out here would be good. Or if not, I think something needs to be said about the ability for callees to turn off the transmission of these type labels. (2) I'm a little uncomfortable with this document being the definitive source for call types for all phone systems everywhere, since presumably these types have other uses in telephony beyond the use envisioned by this spec. Is there another document that could be cited as the definitive source for these types?
- [sipcore] Alissa Cooper's Discuss on draft-ietf-s… Alissa Cooper via Datatracker