--- 1/draft-ietf-scim-api-12.txt 2014-11-17 17:14:47.740498477 -0800 +++ 2/draft-ietf-scim-api-13.txt 2014-11-17 17:14:47.876501802 -0800 @@ -1,25 +1,25 @@ Network Working Group P. Hunt, Ed. Internet-Draft Oracle Intended status: Standards Track K. Grizzle -Expires: April 23, 2015 SailPoint +Expires: May 21, 2015 SailPoint M. Ansari Cisco E. Wahlstroem Nexus Technology C. Mortimore Salesforce - October 20, 2014 + November 17, 2014 System for Cross-Domain Identity Management: Protocol - draft-ietf-scim-api-12 + draft-ietf-scim-api-13 Abstract The System for Cross-Domain Identity Management (SCIM) specification is an HTTP based protocol that makes managing identities in multi- domain scenarios easier to support through a standardized services. Examples include but are not limited to enterprise to cloud service providers, and inter-cloud based scenarios. The specification suite seeks to build upon experience with existing schemas and deployments, placing specific emphasis on simplicity of development and @@ -37,21 +37,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on April 23, 2015. + This Internet-Draft will expire on May 21, 2015. Copyright Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -2609,22 +2609,23 @@ | | be operated on. This occurs | | | | when the specified "path" | | | | value contains a filter that | | | | yields no match. | | | invalidValue | A required value was | GET (Section | | | missing, or the value | 3.2.2), POST | | | specified was not compatible | (Create - Section | | | with the operation or | 3.1, Query - | | | attribute type (see Section | Section 3.2.2), PUT | | | 2.1 [I-D.ietf-scim-core-sche | (Section 3.3.1), | - | | ma]). | PATCH (Section | - | | | 3.3.2) | + | | ma]), or schema (see Section | PATCH (Section | + | | 4 [I-D.ietf-scim-core-schema | 3.3.2) | + | | ]). | | | invalidVers | The specified SCIM protocol | GET (Section | | | version is not supported | 3.2.2), POST (ALL), | | | (see Section 3.11). | PUT (Section | | | | 3.3.1), PATCH | | | | (Section 3.3.2), | | | | DELETE (Section | | | | 3.4) | +--------------+------------------------------+---------------------+ Table 8: Table of SCIM Detail Error Keyword Values @@ -3061,30 +3062,30 @@ | messages:2.0:Error | | 3.10 | +---------------------------------+-----------------+---------------+ Table 9: SCIM Schema URIs for Data Resources 8. References 8.1. Normative References [I-D.ietf-precis-saslprepbis] - Saint-Andre, P. and A. Melnikov, "Preparation and - Comparison of Internationalized Strings Representing - Usernames and Passwords", draft-ietf-precis-saslprepbis-08 - (work in progress), October 2014. + Saint-Andre, P. and A. Melnikov, "Preparation, + Enforcement, and Comparison of Internationalized Strings + Representing Usernames and Passwords", draft-ietf-precis- + saslprepbis-09 (work in progress), October 2014. [I-D.ietf-scim-core-schema] Hunt, P., Grizzle, K., Wahlstroem, E., and C. Mortimore, "System for Cross-Domain Identity Management: Core - Schema", draft-ietf-scim-core-schema-12 (work in - progress), October 2014. + Schema", draft-ietf-scim-core-schema-13 (work in + progress), November 2014. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003. [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005. @@ -3112,23 +3113,24 @@ Transfer Protocol (HTTP/1.1): Range Requests", RFC 7233, June 2014. [RFC7235] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol (HTTP/1.1): Authentication", RFC 7235, June 2014. 8.2. Informative References [I-D.ietf-precis-framework] Saint-Andre, P. and M. Blanchet, "PRECIS Framework: - Preparation and Comparison of Internationalized Strings in - Application Protocols", draft-ietf-precis-framework-18 - (work in progress), September 2014. + Preparation, Enforcement, and Comparison of + Internationalized Strings in Application Protocols", + draft-ietf-precis-framework-19 (work in progress), October + 2014. [OpenSearch] Clinton, D., "OpenSearch Protocol 1.1, Draft 5", . [Order-Operations] Wikipedia, "Order of Operations: Programming Languages", . [RFC6749] Hardt, D., "The OAuth 2.0 Authorization Framework", RFC 6749, October 2012. @@ -3311,20 +3313,23 @@ Draft 12 - PH - Editorial NITs Fix line lengths in artwork to be 72 chars or less Remove unused references Fix normative terms per RFC2119 Updated reference to draft-reschke-http-status-308 to RFC7238 + Draft 13 - PH - Added clarification to error response for improperly + formated email/phonenumbers + Authors' Addresses Phil Hunt (editor) Oracle Corporation Email: phil.hunt@yahoo.com Kelly Grizzle SailPoint