A Media-based Traceroute Function for the Session Initiation Protocol (SIP)
draft-ietf-straw-sip-traceroute-01

The information below is for an old version of the document
Document Type Active Internet-Draft (straw WG)
Last updated 2013-10-21
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
STRAW Working Group                                           H. Kaplan 
Internet Draft                                                   Oracle 
Intended status: Standards Track                       October 21, 2013 
Expires: April 30, 2013                                                 
                                                                        
                                                                        
                                                                        
    
    
                   A Media-based Traceroute Function for  
                   the Session Initiation Protocol (SIP) 
                    draft-ietf-straw-sip-traceroute-01 
    
    
Abstract
    
   SIP already provides the ability to perform hop-by-hop traceroute 
   for SIP messages using the Max-Forwards header field, in order to 
   determine the reachability path of requests to a target.  A 
   mechanism for media-loopback calls has also been defined separately, 
   which enables test calls to be generated which result in media being 
   looped back to the originator.  This document describes a means of 
   performing hop-by-hop traceroute-style test calls using the media-
   loopback mechanism, in order to test the media path when SIP 
   sessions go through media-relaying B2BUAs. 
    
Status of this Memo 
    
   This Internet-Draft is submitted to IETF in full conformance with 
   the provisions of BCP 78 and BCP 79. 
    
   Internet-Drafts are working documents of the Internet Engineering 
   Task Force (IETF), its areas, and its working groups.  Note that 
   other groups may also distribute working documents as Internet-
   Drafts. 
    
   Internet-Drafts are draft documents valid for a maximum of six 
   months and may be updated, replaced, or obsoleted by other documents 
   at any time.  It is inappropriate to use Internet-Drafts as 
   reference material or to cite them other than as "work in progress." 
    
   The list of current Internet-Drafts can be accessed at 
   http://www.ietf.org/ietf/1id-abstracts.txt. 
    
   The list of Internet-Draft Shadow Directories can be accessed at 
   http://www.ietf.org/shadow.html. 
 
   This Internet-Draft will expire on April 21, 2014.  
    

 
 
Kaplan                    Expires April 2014                  [Page 1] 

Internet-Draft         Media-Traceroute for SIP           October 2013 
 
 
Copyright Notice 
    
   Copyright (c) 2013 IETF Trust and the persons identified as the 
   document authors.  All rights reserved.  
        
   This document is subject to BCP 78 and the IETF Trust's Legal 
   Provisions Relating to IETF Documents 
   (http://trustee.ietf.org/license-info) in effect on the date of 
   publication of this document.  Please review these documents 
   carefully, as they describe your rights and restrictions with 
   respect to this document.  Code Components extracted from this 
   document must include Simplified BSD License text as described in 
   Section 4.e of the Trust Legal Provisions and are provided without 
   warranty as described in the Simplified BSD License. 
    
Table of Contents
    
   1. Terminology...................................................2 
   2. Introduction..................................................3 
   3. The SIP Traceroute Mechanism..................................4 
      3.1. Processing a Received Max-Forwards Header Field..........4 
      3.2. Answering the INVITE.....................................5 
   4. Security Considerations.......................................5 
   5. IANA Considerations...........................................5 
   6. Acknowledgments...............................................5 
   7. References....................................................6 
      7.1. Normative References.....................................6 
   Author's Address..................................................6 
    
    
1. Terminology
    
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 
   document are to be interpreted as described in RFC 2119.  The 
   terminology in this document conforms to RFC 2828, "Internet 
   Security Glossary". 
    
   B2BUA: a SIP Back-to-Back User Agent, which is the logical 
   combination of a User Agent Server (UAS) and User Agent Client 
   (UAC). 
    
   UAS: a SIP User Agent Server. 
    
   UAC: a SIP User Agent Client. 
    
   Traceroute: a mechanism to trace a path of hops from an originator 
   to a destination.  For IP, this is typically done using the TTL 
   field of the IP header, starting at the value 1 and incrementing by 
 
 
Kaplan                   Expires - April 2014                 [Page 2] 

Internet-Draft         Media-Traceroute for SIP           October 2013 
 
 
   1 as each IP hop responds with an ICMP error.  For SIP this can be 
Show full document text