IETF Logo Mail Archive

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

"Henry Sinnreich" <henry@pulver.com> Fri, 21 October 2005 19:30 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ET2al-0000Hn-9o; Fri, 21 Oct 2005 15:30:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ET2ah-0000Eh-OS for sipping@megatron.ietf.org; Fri, 21 Oct 2005 15:30:11 -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 PAA28317 for <sipping@ietf.org>; Fri, 21 Oct 2005 15:30:00 -0400 (EDT)
Message-Id: <200510211930.PAA28317@ietf.org>
Received: from mail.pulver.com ([192.246.69.184]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ET2mt-0003TU-1x for sipping@ietf.org; Fri, 21 Oct 2005 15:42:48 -0400
Received: (qmail 15022 invoked by uid 510); 21 Oct 2005 15:44:05 -0400
Received: from henry@pulver.com by mail.pulver.com by uid 508 with qmail-scanner-1.22-st-qms (clamdscan: 0.72. spamassassin: 2.63. Clear:RC:1(24.1.136.53):. Processed in 0.893574 secs); 21 Oct 2005 19:44:05 -0000
X-Antivirus-MYDOMAIN-Mail-From: henry@pulver.com via mail.pulver.com
X-Antivirus-MYDOMAIN: 1.22-st-qms (Clear:RC:1(24.1.136.53):. Processed in 0.893574 secs Process 15017)
Received: from c-24-1-136-53.hsd1.tx.comcast.net (HELO 1AB764895C324D3) (henry@pulver.com@24.1.136.53) by 192.246.69.184 with SMTP; Fri, 21 Oct 2005 19:44:04 +0000
From: Henry Sinnreich <henry@pulver.com>
To: 'Dan Wing' <dwing@cisco.com>, henry@sinnreich.net, 'Arjun Roychowdhury' <arjunrc@gmail.com>
Subject: RE: [Sipping] draft-camarillo-sipping-sbc-funcs-02.txt
Date: Fri, 21 Oct 2005 14:29:59 -0500
Organization: pulver.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <200510211847.j9LIlnJh020176@sj-core-2.cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcXV8C6QbMUqojAPTHqGxQoRonqDOgAVkWzgAApZf3AAATVCEA==
X-Antivirus-MYDOMAIN-Message-ID: <112992384483515017@mail.pulver.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Cc: 'sipping' <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: henry@pulver.com
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

> SBCs are a Best Current Practice?

Sorry, I meant the content: "SIP-Unfriendly Functions" for a BCP.

Thanks, Henry


-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On Behalf
Of Dan Wing
Sent: Friday, October 21, 2005 1:48 PM
To: henry@sinnreich.net; 'Arjun Roychowdhury'
Cc: 'sipping'
Subject: RE: [Sipping] draft-camarillo-sipping-sbc-funcs-02.txt

> 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?

-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

v2.23.0 | Report a Bug | By Email