[sipcore] Magnus Westerlund's Discuss on draft-ietf-sipcore-callinfo-spam-04: (with DISCUSS and COMMENT)

Magnus Westerlund via Datatracker <noreply@ietf.org> Tue, 01 October 2019 15:23 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 3EB2F12089D; Tue, 1 Oct 2019 08:23:14 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Magnus Westerlund 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.103.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <156994339417.23785.17592549456460131068.idtracker@ietfa.amsl.com>
Date: Tue, 01 Oct 2019 08:23:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/9knSnyu9UppKGgD79QorK2YcfRY>
Subject: [sipcore] Magnus Westerlund's Discuss on draft-ietf-sipcore-callinfo-spam-04: (with DISCUSS and COMMENT)
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: Tue, 01 Oct 2019 15:23:15 -0000

Magnus Westerlund 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:
----------------------------------------------------------------------

Section 7:

Which ABNF is used here, please provide a reference. I also very much would
appreciate that the normative reference for "iana-token" was provided in this
section rather than 8.3.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Section 8.3:

So I am slightly worried that there are no recommendations on the criteria the
expert should have for accepting or rejecting an registration request. Well
there is always the possibility for appealing a registration request if it gets
rejected. Considering that these labels are very much social constructs they
will be culture dependent and what may be acceptable in one culture may not be
in another. I would expect that being very liberal is the only way forward
here. At the same time allowing many overlapping labels could enable attacks on
the system.  Was these aspects discussed in the WG?