draft-ietf-drinks-spprov-08.txt   draft-ietf-drinks-spprov-09.txt 
skipping to change at page 1, line 14 skipping to change at page 1, line 14
Internet-Draft CableLabs Internet-Draft CableLabs
Intended status: Standards Track K. Cartwright Intended status: Standards Track K. Cartwright
Expires: January 13, 2012 TNS Expires: January 13, 2012 TNS
S. Ali S. Ali
NeuStar NeuStar
A. Mayrhofer A. Mayrhofer
enum.at GmbH enum.at GmbH
July 12, 2011 July 12, 2011
Session Peering Provisioning Protocol Session Peering Provisioning Protocol
draft-ietf-drinks-spprov-08 draft-ietf-drinks-spprov-09
Abstract Abstract
This document defines a protocol for provisioning session This document defines a protocol for provisioning session
establishment data into Session Data Registries and SIP Service establishment data into Session Data Registries and SIP Service
Provider data stores. The provisioned data is typically used by Provider data stores. The provisioned data is typically used by
various network elements for session peering. various network elements for session peering.
This document describes the Session Peering Provisioning Protocol This document describes the Session Peering Provisioning Protocol
used by clients to provision registries. The document provides a set used by clients to provision registries. The document provides a set
skipping to change at page 10, line 38 skipping to change at page 10, line 38
5. The data object layer defines the base set of SPPP data objects 5. The data object layer defines the base set of SPPP data objects
that can be included in update operations or returned in that can be included in update operations or returned in
operation responses. operation responses.
3.2. Protocol Data Model 3.2. Protocol Data Model
The data model illustrated and described in Figure 3 defines the The data model illustrated and described in Figure 3 defines the
logical objects and the relationships between these objects that the logical objects and the relationships between these objects that the
SPPP protocol supports. SPPP defines the protocol operations through SPPP protocol supports. SPPP defines the protocol operations through
which an SPPP client populates a egistry with these logical objects. which an SPPP client populates a registry with these logical objects.
Various clients belonging to different egistrars may use the protocol Various clients belonging to different registrars may use the
for populating the registry's data. protocol for populating the registry's data.
The logical structure presented below is consistent with the The logical structure presented below is consistent with the
terminology and requirements defined in terminology and requirements defined in
[I-D.ietf-drinks-usecases-requirements]. [I-D.ietf-drinks-usecases-requirements].
+-------------+ +------------------+ +-------------+ +------------------+
| all object | |Organization: | | all object | |Organization: |
| types |----->|orgId | | types |----->|orgId |
+------+------+ | | +------+------+ | |
All objects are +------------------+ All objects are +------------------+
skipping to change at page 13, line 14 skipping to change at page 13, line 14
[I-D.ietf-drinks-usecases-requirements], SPPP defines three type [I-D.ietf-drinks-usecases-requirements], SPPP defines three type
of Route Records: URIType, NAPTRType, and NSType. These Route of Route Records: URIType, NAPTRType, and NSType. These Route
Records extend the abstract type RteRecType and inherit the common Records extend the abstract type RteRecType and inherit the common
attribute 'priority' that is meant for setting precedence across attribute 'priority' that is meant for setting precedence across
the route records defined within a Route Group in a protocol the route records defined within a Route Group in a protocol
agnostic fashion. agnostic fashion.
o Organization: o Organization:
An Organization is an entity that may fulfill the role of a An Organization is an entity that may fulfill the role of a
Registrant or of the peering organization. All SPPP objects are registrant or a peering organization. All SPPP objects are
associated with an organization identifier to identify each associated with an organization identifier to identify each
object's registrant, while tracking the identity of the registrar object's registrant, while tracking the identity of the registrar
that provisioned each SPPP object is left as a matter of policy that provisioned each SPPP object is left as a matter of policy
for an SPPP implementation. A Route Group object is also for an SPPP implementation. A Route Group object is also
associated with a set of zero or more organization identifiers associated with a set of zero or more organization identifiers
that identify the peering organization(s) whose resolution query that identify the peering organization(s) whose resolution query
responses may include the routing information (SED) defined in the responses may include the routing information (SED) defined in the
Route Records within that Route Group. A peering organization is Route Records within that Route Group. A peering organization is
an entity that the registrant intends to share the SED data with. an entity that the registrant intends to share the SED data with.
A route group SPPP object is associated with a set of zero or more A route group SPPP object is associated with a set of zero or more
skipping to change at page 28, line 29 skipping to change at page 28, line 29
Refer to that section of the document for a detailed description of Refer to that section of the document for a detailed description of
the spppQueryResponse element. the spppQueryResponse element.
6.3. Add Public Identifier Operation 6.3. Add Public Identifier Operation
A Public Identifier is the search key used for locating the session A Public Identifier is the search key used for locating the session
establishment data (SED). In many cases, a Public Identifier is establishment data (SED). In many cases, a Public Identifier is
attributed to the end user who has a retail relationship with the attributed to the end user who has a retail relationship with the
service provider or registrant organization. SPPP supports the service provider or registrant organization. SPPP supports the
notion of the carrier-of-record as defined in RFC 5067. Therefore, notion of the carrier-of-record as defined in RFC 5067. Therefore,
the registrant under which the Public Identity is being created can the registrant under whom the Public Identity is being created can
optionally claim to be a carrier-of-record. optionally claim to be a carrier-of-record.
SPPP identifies two types of Public Identifiers: telephone numbers SPPP identifies two types of Public Identifiers: telephone numbers
(TN), and the routing numbers (RN). SPPP provides structures to (TN), and the routing numbers (RN). SPPP provides structures to
manage a single TN, a contiguous range of TNs, and a TN prefix. manage a single TN, a contiguous range of TNs, and a TN prefix.
The abstract XML schema type definition PubIDType is a generalization The abstract XML schema type definition PubIDType is a generalization
for the concrete the Public Identifier schema types. PubIDType for the concrete the Public Identifier schema types. PubIDType
element 'dgName' represents the name of the destination group that a element 'dgName' represents the name of the destination group that a
given Public Identifier is a member of. Because a Destination Group given Public Identifier is a member of. Because a Destination Group
skipping to change at page 38, line 20 skipping to change at page 38, line 20
this document. this document.
As with the responses to all update operations, the result of the As with the responses to all update operations, the result of the
AddRteGrpRqstType operation is contained in the generic AddRteGrpRqstType operation is contained in the generic
spppUpdateResponse data structure described in an earlier sections of spppUpdateResponse data structure described in an earlier sections of
this document. For a detailed description of the spppUpdateResponse this document. For a detailed description of the spppUpdateResponse
data structure refer to that section of the document. data structure refer to that section of the document.
6.6. Get Route Groups Operation 6.6. Get Route Groups Operation
The getRteGrpsRqst operation allows a SPPP client to get the The getRteGrpsRqst operation allows an SPPP client to get the
properties of Route Group objects that the registrar is authorized to properties of Route Group objects that the registrar is authorized to
view on behalf of the registrant. The server will attempt to find a view on behalf of the registrant. The server will attempt to find a
Route Group object that has the registrant ID and route group name Route Group object that has the registrant ID and route group name
pair contained in each ObjKeyType object instance. If no ObjKeyType pair contained in each ObjKeyType object instance. If no ObjKeyType
objects are found in the request then the server will return the list objects are found in the request then the server will return the list
of all Route Group objects that belongs to the registrant. If there of all Route Group objects that belongs to the registrant. If there
are no matching Route Groups found then an empty result set will be are no matching Route Groups found then an empty result set will be
returned. returned.
The element passed into the spppQueryRequest element for this The element passed into the spppQueryRequest element for this
skipping to change at page 43, line 33 skipping to change at page 43, line 33
resolution server to arrive at the final usable URI. resolution server to arrive at the final usable URI.
As with the responses to all update operations, the result of the As with the responses to all update operations, the result of the
AddRteRecRqstType operation is contained in the generic AddRteRecRqstType operation is contained in the generic
spppUpdateResponse data structure described in an earlier sections of spppUpdateResponse data structure described in an earlier sections of
this document. For a detailed description of the spppUpdateResponse this document. For a detailed description of the spppUpdateResponse
data structure refer to that section of the document. data structure refer to that section of the document.
6.8. Get Route Records Operation 6.8. Get Route Records Operation
The getRteRecsRqst operation allows a SPPP client to get the The getRteRecsRqst operation allows an SPPP client to get the
properties of Route Record objects that a registrar is authorized to properties of Route Record objects that a registrar is authorized to
view on behalf of the registrant. The server will attempt to find a view on behalf of the registrant. The server will attempt to find a
Route Record object that has the registrant ID and route record name Route Record object that has the registrant ID and route record name
pair contained in each ObjKeyType object instance. If no ObjKeyType pair contained in each ObjKeyType object instance. If no ObjKeyType
objects are found in the request then the server will return the list objects are found in the request then the server will return the list
of all Route Record that belongs to the registrant. If there are no of all Route Record that belongs to the registrant. If there are no
matching Route Record found then an empty result set will be matching Route Record found then an empty result set will be
returned. returned.
The element passed into the spppQueryRequest element for this The element passed into the spppQueryRequest element for this
skipping to change at page 48, line 27 skipping to change at page 48, line 27
BasicUpdateRqstType and contains a RteGrpOfferKeyType object. BasicUpdateRqstType and contains a RteGrpOfferKeyType object.
As with the responses to all update operations, the result of the As with the responses to all update operations, the result of the
RejectRteGrpOfferRqstType operation is contained in the generic RejectRteGrpOfferRqstType operation is contained in the generic
spppUpdateResponse data structure described in an earlier sections of spppUpdateResponse data structure described in an earlier sections of
this document. For a detailed description of the spppUpdateResponse this document. For a detailed description of the spppUpdateResponse
data structure refer to that section of the document. data structure refer to that section of the document.
6.12. Get Route Group Offers Operation 6.12. Get Route Group Offers Operation
The getRteGrpOffersRqst operation allows a SPPP client to get the The getRteGrpOffersRqst operation allows an SPPP client to get the
properties of zero or more Route Group Offer objects that registrar properties of zero or more Route Group Offer objects that registrar
is authorized to view on behalf of the registrant. The server will is authorized to view on behalf of the registrant. The server will
attempt to find Route Group Offer objects that have all the attempt to find Route Group Offer objects that have all the
properties specified in the criteria passed into the operation. If properties specified in the criteria passed into the operation. If
no criteria is passed in then the server will return the list of no criteria is passed in then the server will return the list of
Route Group Offer objects that belongs to the registrant. If there Route Group Offer objects that belongs to the registrant. If there
are no matching Route Group Offers found then an empty result set are no matching Route Group Offers found then an empty result set
will be returned. will be returned.
The element passed into the spppQueryRequest element for this The element passed into the spppQueryRequest element for this
 End of changes. 7 change blocks. 
9 lines changed or deleted 9 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/