<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.polk-sipping-e2e-sec-assurance" target="https://datatracker.ietf.org/doc/html/draft-polk-sipping-e2e-sec-assurance-00">
   <front>
      <title>Requirements for Assured End-to-End Signaling Security within the Session Initiation Protocol</title>
      <author initials="J." surname="Polk" fullname="James Polk">
         <organization>Cisco Systems</organization>
      </author>
      <date month="July" day="13" year="2005" />
      <abstract>
	 <t>   The Session Initiation Protocol (SIP) has existing mechanisms for 
   securing its signaling messages.  SIP has several transport 
   layers it works across: TCP, UDP, SCTP, and TLS over TCP.  There 
   currently is no mechanism to ensure that if TLS over TCP is chosen 
   by the originating UAC, the messaging will remain encrypted on a 
   hop-by-hop basis to the destination UAS.  This document discusses 
   this scenario, providing the requirements for such to exist, and 
   offering pieces of a possible solution for this set of requirements.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-polk-sipping-e2e-sec-assurance-00" />
   
</reference>
