Re: [Sipping] draft-camarillo-sipping-sbc-funcs-02.txt

David R Oran <oran@cisco.com> Sat, 22 October 2005 15:41 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ETLUe-0000p7-8O; Sat, 22 Oct 2005 11:41:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ETLUb-0000mW-Ge for sipping@megatron.ietf.org; Sat, 22 Oct 2005 11:41:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16960 for <sipping@ietf.org>; Sat, 22 Oct 2005 11:40:57 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETLgx-0003Hq-Rg for sipping@ietf.org; Sat, 22 Oct 2005 11:53:57 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-2.cisco.com with ESMTP; 22 Oct 2005 08:40:59 -0700
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j9MFeuub006577; Sat, 22 Oct 2005 08:40:56 -0700 (PDT)
Received: from [10.32.245.153] (stealth-10-32-245-153.cisco.com [10.32.245.153]) by imail.cisco.com (8.12.11/8.12.10) with SMTP id j9MFp9mX013301; Sat, 22 Oct 2005 08:51:09 -0700
In-Reply-To: <200510211847.j9LIlnJh020176@sj-core-2.cisco.com>
References: <200510211847.j9LIlnJh020176@sj-core-2.cisco.com>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <474EE209-8565-4F08-ABDE-2C26110B7775@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [Sipping] draft-camarillo-sipping-sbc-funcs-02.txt
Date: Sat, 22 Oct 2005 11:40:53 -0400
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.734)
DKIM-Signature: a=rsa-sha1; q=dns; l=502; t=1129996270; x=1130428470; c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding; d=cisco.com; i=oran@cisco.com; z=Subject:Re=3A=20[Sipping]=20draft-camarillo-sipping-sbc-funcs-02.txt| From:David=20R=20Oran=20<oran@cisco.com>| Date:Sat,=2022=20Oct=202005=2011=3A40=3A53=20-0400| Content-Type:text/plain=3B=20charset=3DUS-ASCII=3B=20format=3Dflowed| Content-Transfer-Encoding:7bit; b=movBZIDtDqi78LIDiwOZ7cprWkgYLngTizmCS1A7LuOY2Q9wF0Wy7vaVFwI3DX7q//ybk/u3 ckHFPAO6g77Vhp1oAn0xHGZaXU57yiTSpOcMq9eSHI80slmnmjpTnavO7s2pUg1jU+1JvSoHBvH iLuxVPsOvl6T7YOq7kt0G8vc=
Authentication-Results: imail.cisco.com; header.From=oran@cisco.com; dkim=pass ( message from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: 'sipping' <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

On Oct 21, 2005, at 2:47 PM, Dan Wing wrote:

>> This is a document that should be quickly advanced on the BCP
>> track, since the topic is of high interest in the industry.
>>
>
> SBCs are a Best Current Practice?
>
How about just overloading the acronym to be "Breaks Current Practice".

> -d
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP