Return-Path: <paul.kyzivat@comcast.net>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 8A1141294F1
 for <sipcore@ietfa.amsl.com>; Thu, 22 Dec 2016 10:24:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.8
X-Spam-Level: 
X-Spam-Status: No, score=-5.8 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7,
 RP_MATCHES_RCVD=-3.1, SPF_PASS=-0.001]
 autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
 header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44])
 by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 1vi7duRW3pMI for <sipcore@ietfa.amsl.com>;
 Thu, 22 Dec 2016 10:24:17 -0800 (PST)
Received: from resqmta-po-07v.sys.comcast.net (resqmta-po-07v.sys.comcast.net
 [IPv6:2001:558:fe16:19:96:114:154:166])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 32CAA129671
 for <sipcore@ietf.org>; Thu, 22 Dec 2016 10:24:17 -0800 (PST)
Received: from resomta-po-09v.sys.comcast.net ([96.114.154.233])
 by resqmta-po-07v.sys.comcast.net with SMTP
 id K82Gc4pZA1yUhK82Kc4EhC; Thu, 22 Dec 2016 18:24:16 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net;
 s=q20161114; t=1482431056;
 bh=Amce5yAKpL70KGCqOU93V3kdCgwxxPAIhi6dYIAA5PQ=;
 h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version:
 Content-Type;
 b=Ksapcs+r9ZBkzRqpRifdSVzuRcsV0QyTRkezhBc89tv54v9eFkHbHDFPREInkGJ+G
 IUNfTFn4JheG47rs6mcvaK7vciv8/y/EBLHJfBMNWfnVemAP9J1ctTJ0CeYtbnFBsA
 ZUYf3CQwXWon6ngGpNO9aJT1Wt7W+Urv+JA5KMaN38esxom5NCH83k17xyNW9dMYm4
 lAyBZUJanwF8BEiMqH70+FUqyhDLhlxvfvOYo/IJfoCzyQy6wC/lbajvDSfidd9gjV
 yOXXoLQZISVMvfsVCaoFS0u/UxAvRvnn1Ot3fovYs6MtyFwHVm7jS4lomLEtp9ihr/
 n+6sHgK63k1zw==
Received: from [192.168.1.110] ([73.186.127.100])
 by resomta-po-09v.sys.comcast.net with SMTP
 id K82JcgsoGXhnsK82JcaXfo; Thu, 22 Dec 2016 18:24:16 +0000
To: sipcore@ietf.org
References: <87tw9xvuap.fsf@hobgoblin.ariadne.com>
From: Paul Kyzivat <paul.kyzivat@comcast.net>
Message-ID: <16e6ecb4-64cd-b814-d3c9-8c1c5e7cbe94@comcast.net>
Date: Thu, 22 Dec 2016 13:24:15 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0)
 Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <87tw9xvuap.fsf@hobgoblin.ariadne.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfBuS6Lt16Jz2CjNw88lLyLWPSqLPcu3WkkIHRni/c2ClsLxRY9bAcA2dbySw3K4zxJ5vVB8JDgmKbDhZ9stMLf5RPu2fptuvd87H9LfKK3ZnxVmTtXAn
 ciMwI9kUOzKMMgu64C/+8iOfYMlN04przmHWrEFZGfgWJSGyA1GEAimxNx/jV4PeVvK75cqbWXWisg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/gOyCTouDHf08FyWS1M_GcPrdR7s>
Subject: Re: [sipcore] Comments on draft-ietf-sipcore-status-unwanted-00
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
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: Thu, 22 Dec 2016 18:24:18 -0000

On 12/21/16 4:36 PM, Dale R. Worley wrote:

>    The service provider delivering calls to
>    the user issuing the response may, for example, add the calling party
>    to a personal blacklist specific to the called party, or may use the
>    information as input when computing the likelihood that the calling
>    party is placing unwanted calls ("crowd sourcing"), might initiate a
>    traceback request, or could report the calling number to government
>    authorities.
>
> This list has 4 items:
>
>    may, for example, add the calling party to a personal blacklist
>    specific to the called party,
>
>    or may use the information as input when computing the likelihood
>    that the calling party is placing unwanted calls ("crowd
>    sourcing"),
>
>    might initiate a traceback request,
>
>    or could report the calling number to government authorities.
>
> There is a lack of parallelism in that clauses use "may", "might", and
> "could" to indicate possbility.  There are two uses of "or".  The
> first item contains commas, but the items are not separated by
> semicolons.  Reformulating this by (1) consistently using MAY, (2)
> using one "or" before the last item, and (3) moving the "for example"
> to before the list (thus escaping the rule regarding semicolons):
>
>    The service provider delivering calls to the user issuing the
>    response, for example, MAY add the calling party to a personal
>    blacklist specific to the called party, MAY use the information as
>    input when computing the likelihood that the calling party is
>    placing unwanted calls ("crowd sourcing"), MAY initiate a traceback
>    request, or MAY report the calling number to government
>    authorities.

IIUC these actions are not mutually exclusive. So I would:

s/or MAY report/and MAY report/

	Thanks,
	Paul

