[straw] RFC 7403 on A Media-Based Traceroute Function for the Session Initiation Protocol (SIP)
rfc-editor@rfc-editor.org Fri, 07 November 2014 01:32 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: straw@ietfa.amsl.com
Delivered-To: straw@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BBB81ACE4D; Thu, 6 Nov 2014 17:32:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.496
X-Spam-Level:
X-Spam-Status: No, score=-107.496 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gRMLf6yULp88; Thu, 6 Nov 2014 17:32:44 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 026011ACE55; Thu, 6 Nov 2014 17:32:36 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id C48A0181C99; Thu, 6 Nov 2014 17:32:21 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20141107013221.C48A0181C99@rfc-editor.org>
Date: Thu, 06 Nov 2014 17:32:21 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/straw/VhnBwvuUhxvqzDG2JHwF52t-j0s
Cc: straw@ietf.org, rfc-editor@rfc-editor.org
Subject: [straw] RFC 7403 on A Media-Based Traceroute Function for the Session Initiation Protocol (SIP)
X-BeenThere: straw@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Sip Traversal Required for Applications to Work \(STRAW\) working group discussion list" <straw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/straw>, <mailto:straw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/straw/>
List-Post: <mailto:straw@ietf.org>
List-Help: <mailto:straw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/straw>, <mailto:straw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Nov 2014 01:32:45 -0000
A new Request for Comments is now available in online RFC libraries. RFC 7403 Title: A Media-Based Traceroute Function for the Session Initiation Protocol (SIP) Author: H. Kaplan Status: Standards Track Stream: IETF Date: November 2014 Mailbox: hadrielk@yahoo.com Pages: 7 Characters: 15108 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-straw-sip-traceroute-03.txt URL: https://www.rfc-editor.org/rfc/rfc7403.txt SIP already provides the ability to perform hop-by-hop traceroute for SIP messages using the Max-Forwards header field 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 that 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 to test the media path when SIP sessions go through media-relaying back-to-back user agents (B2BUAs). This document is a product of the Sip Traversal Required for Applications to Work Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/rfc.html Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC