<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.holmberg-sipcore-auth-id" target="https://datatracker.ietf.org/doc/html/draft-holmberg-sipcore-auth-id-00">
   <front>
      <title>Authorization server identity</title>
      <author initials="C." surname="Holmberg" fullname="Christer Holmberg">
         </author>
      <date month="October" day="27" year="2014" />
      <abstract>
	 <t>   The 3rd-Generation Partnership Project (3GPP) has defined how the
   WebRTC framework can be used to provide access to IMS services.
   Users can use &quot;web credentials&quot; (e.g. a username and password) to
   retrieve an authorization token (e.g. an OAuth 2.0 access token),
   which is included in the user registration request sent towards the
   IMS network.

   3GPP has specified a requirement, that the eP-CSCF shall be able to
   include a string value, representing the identity of the WAF, in the
   REGISTER request forwarded towards the S-CSCF.  The S-CSCF can use
   the identity for e.g. policy and routing decisions.

   This document defines a new Authorization header field parameter,
   &#x27;authorization-entity&#x27;, which the eP-CSCF can include in a REGISTER
   request in order to convey the identity of the WAF towards the
   S-CSCF.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-holmberg-sipcore-auth-id-00" />
   
</reference>
