IETF Logo Mail Archive

Re: [Sip] draft-ietf-sip-hop-limit-diagnostics-03

Cullen Jennings <fluffy@cisco.com> Mon, 26 June 2006 16:01 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FutWG-0006Gv-JR; Mon, 26 Jun 2006 12:01:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FutWE-0006Ft-OD for sip@ietf.org; Mon, 26 Jun 2006 12:00:58 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FutWD-0003jw-G5 for sip@ietf.org; Mon, 26 Jun 2006 12:00:58 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-4.cisco.com with ESMTP; 26 Jun 2006 09:00:56 -0700
X-IronPort-AV: i="4.06,176,1149490800"; d="scan'208"; a="1832685834:sNHT189428856"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id k5QG0upL008428; Mon, 26 Jun 2006 09:00:56 -0700
Received: from [192.168.1.2] (sjc-vpn6-344.cisco.com [10.21.121.88]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k5QG0tCU018528; Mon, 26 Jun 2006 09:00:55 -0700 (PDT)
In-Reply-To: <1150495197.10237.51.camel@sukothai.pingtel.com>
References: <1150495197.10237.51.camel@sukothai.pingtel.com>
Mime-Version: 1.0 (Apple Message framework v750)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <D831F539-2E71-4E3A-936C-CA379BA4236A@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-hop-limit-diagnostics-03
Date: Mon, 26 Jun 2006 09:00:50 -0700
To: Scott Lawrence <slawrence@pingtel.com>
X-Mailer: Apple Mail (2.750)
DKIM-Signature: a=rsa-sha1; q=dns; l=218; t=1151337656; x=1152201656; c=relaxed/simple; s=sjdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:Cullen=20Jennings=20<fluffy@cisco.com> |Subject:Re=3A=20[Sip]=20draft-ietf-sip-hop-limit-diagnostics-03; X=v=3Dcisco.com=3B=20h=3D0FJyW9HIjHsgYBk3YGwwY6dorOk=3D; b=oR6apiYezVVmQdLanvakncnY4eaw9Y9TKvEms+ZiH+nrah6vy38rJAHBJpBusW62mXdhMwtW vECesqeH/yqxdO/jDt5l9PyYOvW7NxvdrUEdXHvXEtL6pYg9dE19Hvek;
Authentication-Results: sj-dkim-2.cisco.com; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Cc: SIP WG List <sip@ietf.org>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.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: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

On Jun 16, 2006, at 2:59 PM, Scott Lawrence wrote:

>
> There are, I think, two issues remaining for discussion:

I disagree - I don't think the draft of the discussion has addressed  
the issue I brought up.

_______________________________________________
Sip mailing list  https://www1.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

v2.23.0 | Report a Bug | By Email