IETF Logo Mail Archive

[scim] [Technical Errata Reported] RFC7644 (4670)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 15 April 2016 20:20 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: scim@ietfa.amsl.com
Delivered-To: scim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4332012DAB1 for <scim@ietfa.amsl.com>; Fri, 15 Apr 2016 13:20:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.918
X-Spam-Level:
X-Spam-Status: No, score=-107.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
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 GSCT4ZQEVY33 for <scim@ietfa.amsl.com>; Fri, 15 Apr 2016 13:20:46 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDFA512D9BE for <scim@ietf.org>; Fri, 15 Apr 2016 13:20:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id AC0E918000B; Fri, 15 Apr 2016 13:20:27 -0700 (PDT)
To: phil.hunt@yahoo.com, kelly.grizzle@sailpoint.com, morteza.ansari@cisco.com, erik.wahlstrom@nexusgroup.com, cmortimore@salesforce.com, ben@nostrum.com, alissa@cooperw.in, aamelnikov@fastmail.fm, moransar@cisco.com, leifj@sunet.se
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20160415202027.AC0E918000B@rfc-editor.org>
Date: Fri, 15 Apr 2016 13:20:27 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/scim/bWgaqUejvAuv9h49DaWkEw1Lksk>
X-Mailman-Approved-At: Mon, 18 Apr 2016 01:14:28 -0700
Cc: scim@ietf.org, rfc-editor@rfc-editor.org, zmeeagain@gmail.com
Subject: [scim] [Technical Errata Reported] RFC7644 (4670)
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Simple Cloud Identity Management BOF <scim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/scim>, <mailto:scim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/scim/>
List-Post: <mailto:scim@ietf.org>
List-Help: <mailto:scim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/scim>, <mailto:scim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Apr 2016 20:20:48 -0000

The following errata report has been submitted for RFC7644,
"System for Cross-domain Identity Management: Protocol".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=7644&eid=4670

--------------------------------------
Type: Technical
Reported by: Vassilis Michalitsis <zmeeagain@gmail.com>

Section: 3.4.2.2

Original Text
-------------
Filters MUST be evaluated using the following order of operations, in
   order of precedence:

   1.  Grouping operators

   2.  Logical operators - where "not" takes precedence over "and",
       which takes precedence over "or"

   3.  Attribute operators

Corrected Text
--------------
Filters MUST be evaluated using the following order of operations, in
   order of precedence:

   1.  Grouping operators

   2.  Attribute operators

   3.  Logical operators - where "not" takes precedence over "and",
       which takes precedence over "or"

Notes
-----
It seems that the precedence of logical and attribute precedence is reversed? The filter filter=title sw "M" and userType eq "Employee" is meant to be interpreted as filter=(title sw "M") and (userType eq "Employee"). 
This is also the "expected" behaviour consistent with most other languages - with the notable exception of unary "or" which in SCIM is disambiguated as it can only apply to a parenthesized filter expression.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC7644 (draft-ietf-scim-api-19)
--------------------------------------
Title               : System for Cross-domain Identity Management: Protocol
Publication Date    : September 2015
Author(s)           : P. Hunt, Ed., K. Grizzle, M. Ansari, E. Wahlstroem, C. Mortimore
Category            : PROPOSED STANDARD
Source              : System for Cross-domain Identity Management
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG

v2.23.0 | Report a Bug | By Email