IETF Logo Mail Archive

Re: [sipcore] Alissa Cooper's No Objection on draft-ietf-sipcore-sip-push-21: (with COMMENT)

Ben Campbell <ben@nostrum.com> Wed, 09 January 2019 19:41 UTC

Return-Path: <ben@nostrum.com>
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 3A853130F49; Wed, 9 Jan 2019 11:41:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.68
X-Spam-Level:
X-Spam-Status: No, score=-1.68 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
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 bwDbQDcC2Iui; Wed, 9 Jan 2019 11:41:41 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38A8612DF72; Wed, 9 Jan 2019 11:41:41 -0800 (PST)
Received: from [10.0.1.45] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x09JfYab057539 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 9 Jan 2019 13:41:35 -0600 (CST) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1547062896; bh=qCT0wM/HwSDF5elwNeZXRnWHQQ2WWXN/M9HEsFZPP3k=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=V+cdfqw+s2KWvsoj4FugN6hQEc9wskJxyuv6dsEK4RUw0FBwlOtwlZRzNKsbOqmmK QSkWX4+nqtj6dUxm1nQlbDLulT4rGNwCwWIBhV3uE7IB/PNTydVmIEJqwcuVus/iZx 5ieCFgWz9JOtJ3iUGBXsaRmg+QysNpiUdnoLHnPo=
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.45]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <465FEA4A-2FE5-41EC-B64B-9AC2FF87B575@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_130A95AB-BAD8-4158-94C0-653327F8B9D8"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Wed, 09 Jan 2019 13:41:33 -0600
In-Reply-To: <154704757670.5000.17039213405863685065.idtracker@ietfa.amsl.com>
Cc: The IESG <iesg@ietf.org>, sipcore-chairs@ietf.org, draft-ietf-sipcore-sip-push@ietf.org, sipcore@ietf.org, br@brianrosen.net
To: Alissa Cooper <alissa@cooperw.in>
References: <154704757670.5000.17039213405863685065.idtracker@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/akBKrhGhVD2ycUpD1rseD8b-Ots>
Subject: Re: [sipcore] Alissa Cooper's No Objection on draft-ietf-sipcore-sip-push-21: (with COMMENT)
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 09 Jan 2019 19:41:42 -0000


> On Jan 9, 2019, at 9:26 AM, Alissa Cooper <alissa@cooperw.in> wrote:
> 
> Alissa Cooper has entered the following ballot position for
> draft-ietf-sipcore-sip-push-21: No Objection
> 
> 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-sip-push/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Section 13: "MUST ... unless" is a construct worth avoiding.
> 
> 

Hi Alissa,

I can see why that specific "MUST... unless” may not be appropriate, given the vagueness of the condition and the way we’ve constructed “MUST support/SHOULD use” requirements for TLS in the past.

But are you suggesting that conditional MUSTs are never appropriate?  I’ve been recommended “MUST ... unless...” constructions for cases where the MUST is true except in enumerated special cases. “SHOULD” doesn’t really accomplish the same thing, since a SHOULD as defined by 2119 allows for exceptions beyond those enumerated in the spec.

Thanks!

Ben.

v2.23.0 | Report a Bug | By Email