Subject: [drinks] Diffs between draft-ietf-drinks-spp-framework-05 and 04

From: David Schwartz <[email-masked]>
Date: Sun, 18 Aug 2013 10:29:43 +0000

The diff page is online http://www.ietf.org/rfcdiff?url1=draft-ietf-drinks-spp-framework-05&url2=draft-ietf-drinks-spp-framework-04

At a high level, other than nits the major change has to do with the relationship between a PublicIdentifier and a DestinationGroup. PublicIdentifier has now been promoted to a first class object as opposed to previously being scoped within a DestinationGroup.

:D

(some specific details below)

(page numbers represent 04 document)

Page 6 - section outline cleanup
Page 11 - Figure 2 tightening up
Page 11 - Figure 2 changes - Public Identifier change to match object changes (destGrpRef --> dgName
Page 11 - corresponding text change -

(04)  "An SPPF Public Identifier is associated with a Destination Group"
(05)   "An SPPF Public Identifier may be a member of zero or more Destination Groups"
---
(04)  "…being associated with a Destination Group"
(05)  "…forcing membership in one or more Destination Groups"

Page 13 - tightened up text around egress routes
(04) "the 'svcs' element identifies the SED records associated with the SED Group"
(05) "the 'svcs' element specifies ENUM services ((e.g.,E2U+pstn:sip+sip) that are used to identify the SED records associated with the SED Group"

Spelling mistakes

Page 17 - grammer fix
Page 18 - Spelling

PublicIDType changes to reflect the change in schema regarding the DestinationGroup

Section 6.2
(04) - "The abstract XML schema type definition PubIDType is a generalization for the concrete Public Identifier schema types. PubIDType element 'dgName' represents the name of the destination group that a given Public Identifier may be a member of."
(05) - "The abstract XML schema type definition PubIdType is a generalization for the concrete Public Identifier schema types. PubIdType element 'dgName' represents the name of a destination group that a given Public Identifier may be a member of. Note that this element may be present multiple times so that a given Public Identifier may be a member of multiple destination groups"

Corresponding schema changes

Added section 7 introductory text - "In addition to the operation specific object types, all operations MAY specify the minor version of the protocol that when used in conjunction with the major version (that can be for instance specified in the protocol namespace) can serve to identify the version of the SPPF protocol that the client is using. If the minor version is not specified, the latest minor version supported by the SPPF server for the given major version will be used. Additionally, operations that may potentially modify persistent protocol objects SHOULD include a transaction ID as well."