draft-ietf-drinks-spp-framework-03.txt   draft-ietf-drinks-spp-framework-04.txt 
DRINKS K. Cartwright DRINKS K. Cartwright
Internet-Draft V. Bhatia Internet-Draft V. Bhatia
Intended status: Standards Track TNS Intended status: Standards Track TNS
Expires: April 25, 2013 S. Ali Expires: August 29, 2013 S. Ali
NeuStar NeuStar
D. Schwartz D. Schwartz
XConnect XConnect
October 22, 2012 February 25, 2013
Session Peering Provisioning Framework (SPPF) Session Peering Provisioning Framework (SPPF)
draft-ietf-drinks-spp-framework-03 draft-ietf-drinks-spp-framework-04
Abstract Abstract
This document specifies the data model and the overall structure for This document specifies the data model and the overall structure for
a framework to provision session establishment data into Session Data a framework to provision session establishment data into Session Data
Registries and SIP Service Provider data stores. The framework is Registries and SIP Service Provider data stores. The framework is
called the Session Peering Provisioning Framework (SPPF). The called the Session Peering Provisioning Framework (SPPF). The
provisioned data is typically used by network elements for session provisioned data is typically used by network elements for session
establishment. establishment.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 25, 2013. This Internet-Draft will expire on August 29, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 17, line 49 skipping to change at page 17, line 49
The SPPF data model contains various object relationships. In some The SPPF data model contains various object relationships. In some
cases, these object relationships are established by embedding the cases, these object relationships are established by embedding the
unique identity of the related object inside the relating object. unique identity of the related object inside the relating object.
Note that an object's unique identity is required to Delete or Get Note that an object's unique identity is required to Delete or Get
the details of an object. The following sub-sections normatively the details of an object. The following sub-sections normatively
define the various object keys in SPPF and the attributes of those define the various object keys in SPPF and the attributes of those
keys . keys .
"Name" attributes that are used as components of object key types "Name" attributes that are used as components of object key types
MUST be treated case insensitive, more specifically, comparison MUST be treated case insensitive, more specifically, comparison
operations MUST use the toNFKC_Casefold() function, as specified in operations MUST use the toCasefold() function, as specified in
Section 3.13 of [reference to Unicode 6.1] Section 3.13 of [Unicode6.1].
5.2.1. Generic Object Key Type 5.2.1. Generic Object Key Type
Most objects in SPPF are uniquely identified by an object key that Most objects in SPPF are uniquely identified by an object key that
has the object's name, object's type and its Registrant's has the object's name, object's type and its Registrant's
organization ID as its attributes. The abstract type called organization ID as its attributes. The abstract type called
ObjKeyType is where this unique identity is housed. Any concrete ObjKeyType is where this unique identity is housed. Any concrete
representation of the ObjKeyType MUST contain the following: representation of the ObjKeyType MUST contain the following:
Object Name: The name of the object. Object Name: The name of the object.
skipping to change at page 64, line 5 skipping to change at page 63, line 35
[RFC6116] Bradner, S., Conroy, L., and K. Fujiwara, "The E.164 to [RFC6116] Bradner, S., Conroy, L., and K. Fujiwara, "The E.164 to
Uniform Resource Identifiers (URI) Dynamic Delegation Uniform Resource Identifiers (URI) Dynamic Delegation
Discovery System (DDDS) Application (ENUM)", RFC 6116, Discovery System (DDDS) Application (ENUM)", RFC 6116,
March 2011. March 2011.
[RFC6461] Channabasappa, S., "Data for Reachability of Inter-/ [RFC6461] Channabasappa, S., "Data for Reachability of Inter-/
Intra-NetworK SIP (DRINKS) Use Cases and Protocol Intra-NetworK SIP (DRINKS) Use Cases and Protocol
Requirements", RFC 6461, January 2012. Requirements", RFC 6461, January 2012.
[Unicode6.1]
The Unicode Consortium, "The Unicode Standard - Version
6.1", Unicode 6.1, January 2012.
Authors' Addresses Authors' Addresses
Kenneth Cartwright Kenneth Cartwright
TNS TNS
1939 Roland Clarke Place 1939 Roland Clarke Place
Reston, VA 20191 Reston, VA 20191
USA USA
Email: kcartwright@tnsi.com Email: kcartwright@tnsi.com
 End of changes. 7 change blocks. 
7 lines changed or deleted 11 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/