<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.sparks-sipcore-refer-clarifications" target="https://datatracker.ietf.org/doc/html/draft-sparks-sipcore-refer-clarifications-05">
   <front>
      <title>Clarifications for the use of REFER with RFC6665</title>
      <author initials="R." surname="Sparks" fullname="Robert Sparks">
         <organization>Oracle</organization>
      </author>
      <author initials="A." surname="Roach" fullname="Adam Roach">
         <organization>Mozilla</organization>
      </author>
      <date month="October" day="27" year="2014" />
      <abstract>
	 <t>   An accepted SIP REFER method creates an implicit subscription using
   the SIP-Specific Event Notification Framework.  That framework was
   revised by RFC6665.  This document highlights the implications of the
   requirement changes in RFC6665, and updates the definition of the
   REFER method, RFC3515, to clarify and disambiguate the impact of
   those changes.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-sparks-sipcore-refer-clarifications-05" />
   
</reference>
