Tech-invite3GPPspaceIETFspace
959493929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 7878

Session Peering Provisioning (SPP) Protocol over SOAP

Pages: 83
Proposed Standard
Part 4 of 4 – Pages 62 to 83
First   Prev   None

Top   ToC   RFC7878 - Page 62   prevText

10.13. Get Destination Group

SSP2 uses the spppGetRequest operation to tally the last provisioned record for Destination Group DEST_GRP_SSP2_1. <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Header/> <soapenv:Body> <urn:spppGetRequest> <!--1 or more repetitions:--> <objKey xsi:type="urn:ObjKeyType"> <rant>iana-en:222</rant> <name>DEST_GRP_SSP2_1</name> <type>DestGrp</type> </objKey> </urn:spppGetRequest> </soapenv:Body> </soapenv:Envelope>
Top   ToC   RFC7878 - Page 63
   The Registry completes the request successfully and returns a
   favorable response.

   <?xml version="1.0" encoding="UTF-8"?>
   <S:Envelope
    xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <S:Body>
     <ns3:spppGetResponse
      xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
      xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
      <overallResult>
       <code>1000</code>
       <msg>success</msg>
      </overallResult>
      <resultObj xsi:type="ns2:DestGrpType">
       <ns2:rant>iana-en:222</ns2:rant>
       <ns2:rar>iana-en:223</ns2:rar>
       <ns2:cDate>2012-10-22T09:30:10Z</ns2:cDate>
       <ns2:dgName>DEST_GRP_SSP2_1</ns2:dgName>
      </resultObj>
     </ns3:spppGetResponse>
    </S:Body>
   </S:Envelope>
Top   ToC   RFC7878 - Page 64

10.14. Get Public Identifier

SSP2 obtains the last provisioned record associated with a given TN. <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Header/> <soapenv:Body> <urn:spppGetRequest> <!--1 or more repetitions:--> <objKey xsi:type="urn:PubIdKeyType"> <rant>iana-en:222</rant> <number> <urn1:value>+12025556666</urn1:value> <urn1:type>TN</urn1:type> </number> </objKey> </urn:spppGetRequest> </soapenv:Body> </soapenv:Envelope>
Top   ToC   RFC7878 - Page 65
   The Registry completes the request successfully and returns a
   favorable response.

   <S:Envelope
    xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <S:Body>
     <ns3:spppGetResponse
      xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
      xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
      <overallResult>
       <code>1000</code>
       <msg>success</msg>
      </overallResult>
      <resultObj xsi:type="ns2:TNType">
       <ns2:rant>iana-en:222</ns2:rant>
       <ns2:rar>iana-en:223</ns2:rar>
       <ns2:cDate>2012-10-22T09:30:10Z</ns2:cDate>
       <ns2:dgName>DEST_GRP_SSP2_1</ns2:dgName>
       <ns2:tn>+12025556666</ns2:tn>
       <ns2:corInfo>
        <ns2:corClaim>true</ns2:corClaim>
        <ns2:cor>true</ns2:cor>
        <ns2:corDate>2010-05-30T09:30:10Z</ns2:corDate>
       </ns2:corInfo>
      </resultObj>
     </ns3:spppGetResponse>
    </S:Body>
   </S:Envelope>
Top   ToC   RFC7878 - Page 66

10.15. Get SED Group Request

SSP2 obtains the last provisioned record for the SED Group SED_GRP_SSP2_1. <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Header/> <soapenv:Body> <urn:spppGetRequest> <!--1 or more repetitions:--> <objKey xsi:type="urn:ObjKeyType"> <rant>iana-en:222</rant> <name>SED_GRP_SSP2_1</name> <type>SedGrp</type> </objKey> </urn:spppGetRequest> </soapenv:Body> </soapenv:Envelope>
Top   ToC   RFC7878 - Page 67
   The Registry completes the request successfully and returns a
   favorable response.

   <?xml version="1.0" encoding="UTF-8"?>
   <S:Envelope
    xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <S:Body>
     <ns3:spppGetResponse
      xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
      xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
      <overallResult>
       <code>1000</code>
       <msg>success</msg>
      </overallResult>
      <resultObj xsi:type="ns2:SedGrpType">
       <ns2:rant>iana-en:222</ns2:rant>
       <ns2:rar>iana-en:223</ns2:rar>
       <ns2:cDate>2012-10-22T09:30:10Z</ns2:cDate>
       <ns2:sedGrpName>SED_GRP_SSP2_1</ns2:sedGrpName>
       <ns2:sedRecRef>
        <ns2:sedKey xsi:type="ns3:ObjKeyType">
         <rant>iana-en:222</rant>
         <name>SED_SSP2_SBE2</name>
         <type>SedRec</type>
        </ns2:sedKey>
        <ns2:priority>100</ns2:priority>
       </ns2:sedRecRef>
       <ns2:sedRecRef>
        <ns2:sedKey xsi:type="ns3:ObjKeyType">
         <rant>iana-en:222</rant>
         <name>SED_SSP2_SBE4</name>
         <type>SedRec</type>
        </ns2:sedKey>
        <ns2:priority>101</ns2:priority>
       </ns2:sedRecRef>
       <ns2:dgName>DEST_GRP_SSP2_1</ns2:dgName>
       <ns2:isInSvc>true</ns2:isInSvc>
       <ns2:priority>10</ns2:priority>
      </resultObj>
     </ns3:spppGetResponse>
    </S:Body>
   </S:Envelope>
Top   ToC   RFC7878 - Page 68

10.16. Get SED Group Offers Request

SSP2 fetches the last provisioned SED Group Offer to the <peeringOrg> SSP1. <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1"> <soapenv:Header/> <soapenv:Body> <urn:getSedGrpOffersRequest> <offeredTo>iana-en:111</offeredTo> </urn:getSedGrpOffersRequest> </soapenv:Body> </soapenv:Envelope>
Top   ToC   RFC7878 - Page 69
   The Registry processes the request successfully and returns a
   favorable response.

   <?xml version="1.0" encoding="UTF-8"?>
   <S:Envelope
    xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <S:Body>
     <ns3:spppGetResponse
      xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
      xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
      <overallResult>
       <code>1000</code>
       <msg>success</msg>
      </overallResult>
      <resultObj xsi:type="ns2:SedGrpOfferType">
       <ns2:rant>iana-en:222</ns2:rant>
       <ns2:rar>iana-en:223</ns2:rar>
       <ns2:cDate>2012-10-22T09:30:10Z</ns2:cDate>
       <ns2:sedGrpOfferKey
        xsi:type="ns3:SedGrpOfferKeyType">
        <sedGrpKey>
         <rant>iana-en:222</rant>
         <name>SED_GRP_SSP2_1</name>
         <type>SedGrp</type>
        </sedGrpKey>
        <offeredTo>iana-en:111</offeredTo>
       </ns2:sedGrpOfferKey>
       <ns2:status>offered</ns2:status>
       <ns2:offerDateTime>
        2006-05-04T18:13:51.0Z
       </ns2:offerDateTime>
      </resultObj>
     </ns3:spppGetResponse>
    </S:Body>
   </S:Envelope>
Top   ToC   RFC7878 - Page 70

10.17. Get Egress Route

SSP1 wants to verify the last provisioned record for the Egress Route called EGR_RTE_01. <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Header/> <soapenv:Body> <urn:spppGetRequest> <!--1 or more repetitions:--> <objKey xsi:type="urn:ObjKeyType"> <rant>iana-en:111</rant> <name>EGR_RTE_01</name> <type>EgrRte</type> </objKey> </urn:spppGetRequest> </soapenv:Body> </soapenv:Envelope>
Top   ToC   RFC7878 - Page 71
   The Registry completes the request successfully and returns a
   favorable response.

   <?xml version="1.0" encoding="UTF-8"?>
   <S:Envelope
    xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <S:Body>
     <ns3:spppGetResponse
      xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
      xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
      <overallResult>
       <code>1000</code>
       <msg>success</msg>
      </overallResult>
      <resultObj xsi:type="ns2:EgrRteType">
       <ns2:rant>iana-en:222</ns2:rant>
       <ns2:rar>iana-en:223</ns2:rar>
       <ns2:cDate>2012-10-22T09:30:10Z</ns2:cDate>
       <ns2:egrRteName>EGR_RTE_01</ns2:egrRteName>
       <ns2:pref>50</ns2:pref>
       <ns2:regxRewriteRule>
        <ns2:ere>^(.*)$</ns2:ere>
        <ns2:repl>sip:\1@sbe1.ssp1.example.com</ns2:repl>
       </ns2:regxRewriteRule>
       <ns2:ingrSedGrp xsi:type="ns3:ObjKeyType">
        <rant>iana-en:222</rant>
        <name>SED_GRP_SSP2_1</name>
        <type>SedRec</type>
       </ns2:ingrSedGrp>
      </resultObj>
     </ns3:spppGetResponse>
    </S:Body>
   </S:Envelope>
Top   ToC   RFC7878 - Page 72

10.18. Delete Destination Group

SSP2 initiates a request to delete the Destination Group DEST_GRP_SSP2_1. <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Header/> <soapenv:Body> <urn:spppDelRequest> <!--1 or more repetitions:--> <objKey xsi:type="urn:ObjKeyType"> <rant>iana-en:222</rant> <name>DEST_GRP_SSP2_1</name> <type>DestGrp</type> </objKey> </urn:spppDelRequest> </soapenv:Body> </soapenv:Envelope> The Registry completes the request successfully and returns a favorable response. <?xml version="1.0" encoding="UTF-8"?> <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> <S:Body> <ns3:spppDelResponse xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> <serverTransId>tx_12354</serverTransId> <overallResult> <code>1000</code> <msg>Request Succeeded.</msg> </overallResult> </ns3:spppDelResponse> </S:Body> </S:Envelope>
Top   ToC   RFC7878 - Page 73

10.19. Delete Public Identifier

SSP2 chooses to deactivate the TN and remove it from the Registry. <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Header/> <soapenv:Body> <urn:spppDelRequest> <!--1 or more repetitions:--> <objKey xsi:type="urn:PubIdKeyType"> <rant>iana-en:222</rant> <number> <urn1:value>+12025556666</urn1:value> <urn1:type>TN</urn1:type> </number> </objKey> </urn:spppDelRequest> </soapenv:Body> </soapenv:Envelope> The Registry completes the request successfully and returns a favorable response. <?xml version="1.0" encoding="UTF-8"?> <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> <S:Body> <ns3:spppDelResponse xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> <serverTransId>tx_12354</serverTransId> <overallResult> <code>1000</code> <msg>Request Succeeded.</msg> </overallResult> </ns3:spppDelResponse> </S:Body> </S:Envelope>
Top   ToC   RFC7878 - Page 74

10.20. Delete SED Group Request

SSP2 removes the SED Group called SED_GRP_SSP2_1. <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Header/> <soapenv:Body> <urn:spppDelRequest> <!--1 or more repetitions:--> <objKey xsi:type="urn:ObjKeyType"> <rant>iana-en:222</rant> <name>SED_GRP_SSP2_1</name> <type>SedGrp</type> </objKey> </urn:spppDelRequest> </soapenv:Body> </soapenv:Envelope> The Registry completes the request successfully and returns a favorable response. <?xml version="1.0" encoding="UTF-8"?> <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> <S:Body> <ns3:spppDelResponse xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> <serverTransId>tx_12354</serverTransId> <overallResult> <code>1000</code> <msg>Request Succeeded.</msg> </overallResult> </ns3:spppDelResponse> </S:Body> </S:Envelope>
Top   ToC   RFC7878 - Page 75

10.21. Delete SED Group Offers Request

SSP2 no longer wants to share SED Group SED_GRP_SSP2_1 with SSP1. <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Header/> <soapenv:Body> <urn:spppDelRequest> <!--1 or more repetitions:--> <objKey xsi:type="urn:SedGrpOfferKeyType"> <sedGrpKey> <rant>iana-en:222</rant> <name>SED_GRP_SSP2_1</name> <type>SedGrp</type> </sedGrpKey> <offeredTo>iana-en:111</offeredTo> </objKey> </urn:spppDelRequest> </soapenv:Body> </soapenv:Envelope> The Registry completes the request successfully and returns a favorable response. Restoring this resource sharing will require a new SED Group Offer from SSP2 to SSP1 followed by a successful SED Group Accept request from SSP1. <?xml version="1.0" encoding="UTF-8"?> <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> <S:Body> <ns3:spppDelResponse xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> <serverTransId>tx_12354</serverTransId> <overallResult> <code>1000</code> <msg>Request Succeeded.</msg> </overallResult> </ns3:spppDelResponse> </S:Body> </S:Envelope>
Top   ToC   RFC7878 - Page 76

10.22. Delete Egress Route

SSP1 decides to remove the Egress Route with the label EGR_RTE_01. <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Header/> <soapenv:Body> <urn:spppDelRequest> <!--1 or more repetitions:--> <objKey xsi:type="urn:ObjKeyType"> <rant>iana-en:111</rant> <name>EGR_RTE_01</name> <type>EgrRte</type> </objKey> </urn:spppDelRequest> </soapenv:Body> </soapenv:Envelope> The Registry completes the request successfully and returns a favorable response. <?xml version="1.0" encoding="UTF-8"?> <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> <S:Body> <ns3:spppDelResponse xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1" xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1"> <serverTransId>tx_12354</serverTransId> <overallResult> <code>1000</code> <msg>Request Succeeded.</msg> </overallResult> </ns3:spppDelResponse> </S:Body> </S:Envelope>
Top   ToC   RFC7878 - Page 77

10.23. Batch Request

Following is an example of how some of the operations mentioned in previous sections MAY be performed by an SPPF client as a batch in one single SPPP over SOAP request. In the sample request below, SSP1 wants to accept a SED Group Offer from SSP3, add a Destination Group, add a Naming Authority Pointer (NAPTR) SED Record, add a SED Group, add a SED Group Offer, delete a previously provisioned TN type Public Identifier, delete a previously provisioned SED Group, and reject a SED Group Offer from SSP4. <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:ietf:params:xml:ns:sppf:soap:1" xmlns:urn1="urn:ietf:params:xml:ns:sppf:base:1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Header/> <soapenv:Body> <urn:spppBatchRequest> <clientTransId>txn_1467</clientTransId> <minorVer>1</minorVer> <acceptSedGrpOffer> <sedGrpKey> <rant>iana-en:225</rant> <name>SED_SSP3_SBE1_Offered</name> <type>SedGrp</type> </sedGrpKey> <offeredTo>iana-en:222</offeredTo> </acceptSedGrpOffer> <addObj xsi:type="urn1:DestGrpType"> <urn1:rant>iana-en:222</urn1:rant> <urn1:rar>iana-en:223</urn1:rar> <urn1:dgName>DEST_GRP_SSP2_1</urn1:dgName> </addObj> <addObj xsi:type="urn1:NAPTRType"> <urn1:rant>iana-en:222</urn1:rant> <urn1:rar>iana-en:223</urn1:rar> <urn1:sedName>SED_SSP2_SBE2</urn1:sedName> <urn1:order>10</urn1:order> <urn1:flags>u</urn1:flags> <urn1:svcs>E2U+sip</urn1:svcs>
Top   ToC   RFC7878 - Page 78
       <urn1:regx>
        <urn1:ere>^(.*)$</urn1:ere>
        <urn1:repl>sip:\1@sbe2.ssp2.example.com</urn1:repl>
       </urn1:regx>
      </addObj>

      <addObj xsi:type="urn1:SedGrpType">
       <urn1:rant>iana-en:222</urn1:rant>
       <urn1:rar>iana-en:223</urn1:rar>
       <urn1:sedGrpName>SED_GRP_SSP2_1</urn1:sedGrpName>
       <urn1:sedRecRef>
        <urn1:sedKey xsi:type="urn:ObjKeyType">
         <rant>iana-en:222</rant>
         <name>SED_SSP2_SBE2</name>
         <type>SedRec</type>
        </urn1:sedKey>
       <urn1:priority>100</urn1:priority>
       </urn1:sedRecRef>
        <urn1:dgName>DEST_GRP_SSP2_1</urn1:dgName>
        <urn1:isInSvc>true</urn1:isInSvc>
        <urn1:priority>10</urn1:priority>
      </addObj>

      <addObj xsi:type="urn1:SedGrpOfferType">
       <urn1:rant>iana-en:222</urn1:rant>
       <urn1:rar>iana-en:223</urn1:rar>
       <urn1:sedGrpOfferKey xsi:type="urn:SedGrpOfferKeyType">
        <sedGrpKey xsi:type="urn:ObjKeyType">
         <rant>iana-en:222</rant>
         <name>SED_GRP_SSP2_1</name>
         <type>SedGrp</type>
        </sedGrpKey>
        <offeredTo>iana-en:111</offeredTo>
       </urn1:sedGrpOfferKey>
       <urn1:status>offered</urn1:status>
       <urn1:offerDateTime>
        2006-05-04T18:13:51.0Z
       </urn1:offerDateTime>
      </addObj>

      <delObj xsi:type="urn:PubIdKeyType">
       <rant>iana-en:222</rant>
       <number>
        <urn1:value>+12025556666</urn1:value>
        <urn1:type>TN</urn1:type>
       </number>
      </delObj>
Top   ToC   RFC7878 - Page 79
      <delObj xsi:type="urn:ObjKeyType">
       <rant>iana-en:222</rant>
       <name>SED_GRP_SSP2_Previous</name>
       <type>SedGrp</type>
      </delObj>

      <rejectSedGrpOffer>
       <sedGrpKey>
        <rant>iana-en:226</rant>
        <name>SED_SSP4_SBE1_Offered</name>
        <type>SedGrp</type>
       </sedGrpKey>
       <offeredTo>iana-en:222</offeredTo>
      </rejectSedGrpOffer>

     </urn:spppBatchRequest>
    </soapenv:Body>
   </soapenv:Envelope>

   The Registry completes the request successfully and returns a
   favorable response.

   <?xml version="1.0" encoding="UTF-8"?>
   <S:Envelope
    xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
    <S:Body>
     <ns3:spppBatchResponse
      xmlns:ns2="urn:ietf:params:xml:ns:sppf:base:1"
      xmlns:ns3="urn:ietf:params:xml:ns:sppf:soap:1">
      <serverTransId>tx_12354</serverTransId>
      <overallResult>
       <code>1000</code>
       <msg>Request Succeeded.</msg>
      </overallResult>
     </ns3:spppBatchResponse>
    </S:Body>
   </S:Envelope>
Top   ToC   RFC7878 - Page 80

11. Security Considerations

The base security considerations of SPPP outlined in Section 9 of [RFC7877] also apply to SPPP over SOAP implementations. Additionally, the following must be considered: SPPP over SOAP is used to query and update session peering data and addresses, so the ability to access this protocol should be limited to users and systems that are authorized to query and update this data. Because this data is sent in both directions, it may not be sufficient for just the client or user to be authenticated with the server. The identity of the server should also be authenticated by the client, which is often accomplished using the TLS certificate exchange and validation described in [RFC2818].

11.1. Vulnerabilities

Section 5 describes the use of HTTP and TLS as the underlying substrate protocols for SPPP over SOAP. These underlying protocols may have various vulnerabilities, and these may be inherited by SPPP over SOAP. SPPP over SOAP itself may have vulnerabilities because an authorization model is not explicitly specified in this document. During a TLS handshake, TLS servers can optionally request a certificate from a TLS client; that option is not a requirement for this protocol. This presents a denial-of-service risk in which unauthenticated clients can consume server CPU resources by creating TLS sessions. The risk is increased if the server supports client- initiated renegotiation. This risk can be mitigated by disabling client-initiated renegotiation on the server and by ensuring that other means (such as firewall access control lists) are used to restrict unauthenticated client access to servers. In conjunction with the above, it is important that SPPP over SOAP implementations implement an authorization model that considers the source of each query or update request and determines whether it is reasonable to authorize that source to perform that specific query or update.
Top   ToC   RFC7878 - Page 81

12. IANA Considerations

This document uses URNs to describe XML Namespaces and XML Schemas. According to [RFC3688], IANA has performed the following URN assignment: URN: urn:ietf:params:xml:ns:sppf:soap:1 Registrant Contact: IESG XML: See Section 9 of [RFC7878]

13. References

13.1. Normative References

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, <http://www.rfc-editor.org/info/rfc3688>. [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS) Protocol Version 1.2", RFC 5246, DOI 10.17487/RFC5246, August 2008, <http://www.rfc-editor.org/info/rfc5246>. [RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing", RFC 7230, DOI 10.17487/RFC7230, June 2014, <http://www.rfc-editor.org/info/rfc7230>. [RFC7231] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content", RFC 7231, DOI 10.17487/RFC7231, June 2014, <http://www.rfc-editor.org/info/rfc7231>. [RFC7235] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer Protocol (HTTP/1.1): Authentication", RFC 7235, DOI 10.17487/RFC7235, June 2014, <http://www.rfc-editor.org/info/rfc7235>.
Top   ToC   RFC7878 - Page 82
   [RFC7525]  Sheffer, Y., Holz, R., and P. Saint-Andre,
              "Recommendations for Secure Use of Transport Layer
              Security (TLS) and Datagram Transport Layer Security
              (DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May
              2015, <http://www.rfc-editor.org/info/rfc7525>.

   [RFC7877]  Cartwright, K., Bhatia, V., Ali, S., and D. Schwartz,
              "Session Peering Provisioning Framework (SPPF)", RFC 7877,
              DOI 10.17487/RFC7877, August 2016,
              <http://www.rfc-editor.org/info/rfc7877>.

   [SOAPREF]  Gudgin, M., Hadley, M., Moreau, J., and H. Nielsen, "SOAP
              Version 1.2 Part 1: Messaging Framework (Second Edition)",
              W3C Recommendation REC-SOAP12-part1-20070427, April 2007,
              <http://www.w3.org/TR/soap12-part1/>.

13.2. Informative References

[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, DOI 10.17487/RFC2818, May 2000, <http://www.rfc-editor.org/info/rfc2818>. [RFC5321] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321, DOI 10.17487/RFC5321, October 2008, <http://www.rfc-editor.org/info/rfc5321>. [W3C.REC-xml-20081126] Sperberg-McQueen, C., Yergeau, F., Bray, T., Maler, E., and J. Paoli, "Extensible Markup Language (XML) 1.0 (Fifth Edition)", W3C Recommendation REC-xml-20081126, November 2008, <http://www.w3.org/TR/2008/REC-xml-20081126>. [WSDLREF] Christensen, E., Curbera, F., Meredith, G., and S. Weerawarana, "Web Services Description Language (WSDL) 1.1", W3C Note NOTE-wsdl-20010315, March 2001, <http://www.w3.org/TR/2001/NOTE-wsdl-20010315>.

Acknowledgements

This document is a result of various discussions held with the IETF DRINKS working group, specifically the protocol design team, with contributions from the following individuals, in alphabetical order: Syed Ali, Vikas Bhatia, Kenneth Cartwright, Sumanth Channabasappa, Lisa Dusseault, Deborah A. Guyton, Scott Hollenbeck, Otmar Lendl, Manjul Maharishi, Mickael Marrache, Alexander Mayrhofer, Samuel Melloul, Jean-Francois Mule, Peter Saint-Andre, David Schwartz, and Richard Shockey.
Top   ToC   RFC7878 - Page 83

Authors' Addresses

Kenneth Cartwright TNS 10740 Parkridge Boulevard Reston, VA 20191 United States Email: kcartwright@tnsi.com Vikas Bhatia TNS 10740 Parkridge Boulevard Reston, VA 20191 United States Email: vbhatia@tnsi.com Jean-Francois Mule Apple Inc. 1 Infinite Loop Cupertino, CA 95014 United States Email: jfmule@apple.com Alexander Mayrhofer nic.at GmbH Karlsplatz 1/2/9 Wien A-1010 Austria Email: alexander.mayrhofer@nic.at