Re: [sipcore] I-D Action: draft-ietf-sipcore-rejected-07.txt

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 24 April 2019 04:35 UTC

To: sipcore@ietf.org
References: <155607397517.32461.8003402784805398777@ietfa.amsl.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <8cd3e094-837c-621b-9eaa-c9abc3c770a4@alum.mit.edu>
Date: Wed, 24 Apr 2019 00:35:38 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <155607397517.32461.8003402784805398777@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/93rqepvLftDDAHRUbnP7IBMP2cE>
Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-rejected-07.txt
Precedence: list

A couple of nits:

Section 1:

s/service providers may not block/service providers may not be permitted 
to block/

(Otherwise it can be read as discretionary - might not block.)

Later in the section, the following:

    An algorithm can be vulnerable to an algorithm
    subject to the base rate fallacy

is very odd. (An algorithm is vulnerable to an algorithm?)
I don't know quite what was intended. Perhaps:


    An algorithm can be vulnerable to the base rate fallacy

Section 4.1:

s/One would construct the JWS would as follows./One would construct the 
JWS as follows./

	Thanks,
	Paul

[sipcore] I-D Action: draft-ietf-sipcore-rejected… internet-drafts
Re: [sipcore] I-D Action: draft-ietf-sipcore-reje… Paul Kyzivat