draft-ietf-drinks-spp-framework-07.txt   draft-ietf-drinks-spp-framework-08.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: October 24, 2014 S. Ali Expires: April 25, 2015 S. Ali
NeuStar NeuStar
D. Schwartz D. Schwartz
XConnect XConnect
April 22, 2014 October 22, 2014
Session Peering Provisioning Framework (SPPF) Session Peering Provisioning Framework (SPPF)
draft-ietf-drinks-spp-framework-07 draft-ietf-drinks-spp-framework-08
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 October 24, 2014. This Internet-Draft will expire on April 25, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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
skipping to change at page 41, line 18 skipping to change at page 41, line 18
issues inherent to the specific lower-level mechanism used for any issues inherent to the specific lower-level mechanism used for any
implementation of SPPF. SPPF also has its own set of higher-level implementation of SPPF. SPPF also has its own set of higher-level
exposures that are likely to be independent of lower-layer mechanism exposures that are likely to be independent of lower-layer mechanism
choices. choices.
9.3.1. DoS Issues Inherited from Transport Mechanism 9.3.1. DoS Issues Inherited from Transport Mechanism
SPPF implementation is in general dependent on the selection and SPPF implementation is in general dependent on the selection and
implementation of a lower-level transport protocol and a binding implementation of a lower-level transport protocol and a binding
between that protocol and SPPF. The archetypal SPPF implementation between that protocol and SPPF. The archetypal SPPF implementation
uses XML (http://www.w3.org/TR/xml/) representation in a SOAP (http:/ uses XML (http://www.w3.org/TR/xml/) representation in a SOAP
/www.w3.org/TR/soap/) request/response framework over HTTP (http://www.w3.org/TR/soap/) request/response framework over HTTP
([RFC2616]), and probably also uses TLS ([RFC5246]) for on-the wire ([RFC2616]), and probably also uses TLS ([RFC5246]) for on-the wire
data integrity and participant authentication, and might use HTTP data integrity and participant authentication, and might use HTTP
Digest authentication ([RFC2609]). Digest authentication ([RFC2609]).
The typical deployment scenario for SPPF is to have servers in a The typical deployment scenario for SPPF is to have servers in a
managed facility, and therefore techniques such as Network Ingress managed facility, and therefore techniques such as Network Ingress
Filtering ([RFC2609]) are generally applicable. In short, any DoS Filtering ([RFC2609]) are generally applicable. In short, any DoS
mechanism affecting a typical HTTP implementation would affect such mechanism affecting a typical HTTP implementation would affect such
an SPPF implementation, and the mitigation tools for HTTP in general an SPPF implementation, and the mitigation tools for HTTP in general
also therefore apply to SPPF. also therefore apply to SPPF.
 End of changes. 5 change blocks. 
6 lines changed or deleted 6 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/