Re: [Sip] I-D on ICE diagnostic error code
"Christer Holmberg" <christer.holmberg@ericsson.com> Mon, 25 February 2008 07:43 UTC
Return-Path: <sip-bounces@ietf.org>
X-Original-To: ietfarch-sip-archive@core3.amsl.com
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C9B3528C12D; Sun, 24 Feb 2008 23:43:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.323
X-Spam-Level:
X-Spam-Status: No, score=-0.323 tagged_above=-999 required=5 tests=[AWL=-0.886, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QZXxM9TjkL00; Sun, 24 Feb 2008 23:43:45 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7C1473A6B58; Sun, 24 Feb 2008 23:43:45 -0800 (PST)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 70FA73A68F9 for <sip@core3.amsl.com>; Sun, 24 Feb 2008 23:43:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XPhUveiHrxTL for <sip@core3.amsl.com>; Sun, 24 Feb 2008 23:43:41 -0800 (PST)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 7EED93A67F4 for <sip@ietf.org>; Sun, 24 Feb 2008 23:43:41 -0800 (PST)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 1E9512147A; Mon, 25 Feb 2008 08:43:35 +0100 (CET)
X-AuditID: c1b4fb3e-aa1febb000000b15-29-47c271a7157f
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 013BB21339; Mon, 25 Feb 2008 08:43:35 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 25 Feb 2008 08:43:34 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 25 Feb 2008 08:43:33 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF04BFB2CC@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] I-D on ICE diagnostic error code
thread-index: Ach2Uz/5UIFbNdyvRJe6IROahBGsPAA3+W52
References: <47C07458.7080503@cisco.com>
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Jonathan Rosenberg <jdrosen@cisco.com>, IETF SIP List <sip@ietf.org>
X-OriginalArrivalTime: 25 Feb 2008 07:43:34.0569 (UTC) FILETIME=[1FF56990:01C87782]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] I-D on ICE diagnostic error code
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1098415592=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
Hi Jonathan, The response code is ICE specific. But, couldn't it be useful at least also for RFC4145, if one fails to establish a TCP connection? So, instead of "Connectivity Checks Failed" the text would be more generic and say "Connectivity Failure", or something like that... Regards, Christer ________________________________ From: sip-bounces@ietf.org on behalf of Jonathan Rosenberg Sent: Sat 23/02/2008 20:30 To: IETF SIP List Subject: [Sip] I-D on ICE diagnostic error code I just submitted: http://www.ietf.org/internet-drafts/draft-rosenberg-sip-ice-error-code-0 1.txt This is nearly identical to a draft I submitted before Vancouver, but we never discussed. The basic idea here is to define a new SIP response code for the case when all ICE connectivity checks fail. THe main benefit is that proxies can log this and collect statistics on successful and failed ICE cases from the SIP messaging. Comments welcome. -Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 499 Thornall St. Cisco Fellow Edison, NJ 08837 Cisco, Voice Technology Group jdrosen@cisco.com http://www.jdrosen.net <http://www.jdrosen.net/> PHONE: (408) 902-3084 http://www.cisco.com <http://www.cisco.com/> _______________________________________________ Sip mailing list http://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
_______________________________________________ Sip mailing list http://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- [Sip] I-D on ICE diagnostic error code Jonathan Rosenberg
- Re: [Sip] I-D on ICE diagnostic error code Christer Holmberg