[sip-ops] Anouncing new Sip-Ops mailing list

Cullen Jennings <fluffy@cisco.com> Mon, 27 April 2009 19:12 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: sip-ops@core3.amsl.com
Delivered-To: sip-ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC6AB3A6FED; Mon, 27 Apr 2009 12:12:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.593
X-Spam-Level:
X-Spam-Status: No, score=-106.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 DVOvblVc3jvG; Mon, 27 Apr 2009 12:12:26 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 9D0C53A6AB5; Mon, 27 Apr 2009 12:12:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.40,256,1238976000"; d="scan'208";a="157040987"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-3.cisco.com with ESMTP; 27 Apr 2009 19:13:46 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n3RJDkLJ018596; Mon, 27 Apr 2009 12:13:46 -0700
Received: from [192.168.4.177] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n3RJDjis015349; Mon, 27 Apr 2009 19:13:45 GMT
Message-Id: <FEAB7736-5426-4AC2-A6BA-54D0A7A41C29@cisco.com>
From: Cullen Jennings <fluffy@cisco.com>
To: sip-ops@ietf.org, ops-area@ietf.org, rai@ietf.org, ops-dir@ietf.org, sipping <sipping@ietf.org>
Impp: xmpp:cullenfluffyjennings@jabber.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 27 Apr 2009 13:13:44 -0600
X-Mailer: Apple Mail (2.930.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=959; t=1240859626; x=1241723626; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20<fluffy@cisco.com> |Subject:=20Anouncing=20new=20Sip-Ops=20mailing=20list=20 |Sender:=20; bh=K7DuTheGRiwMCr9seyr+eB+O3RNm63clRiS/PWtDCOg=; b=UoqRUZZlBr3lpUJi34l7wn7fbSz90lCzdgOw5lSiF48YLOd9UxCLKJi4ZG IqfrVLrdbUVnnl6hzqEeWp0jYjsoKKs4j1NgrLkwOg1qGzOsQbpiy/yH3+6E VWDGR3IDptr9KzU/9DCTCA12f+BFE6CuBA1562CuM09Ls2mTD+Rk4=;
Authentication-Results: sj-dkim-1; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
Cc: Robert Sparks <rjsparks@nostrum.com>
Subject: [sip-ops] Anouncing new Sip-Ops mailing list
X-BeenThere: sip-ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Operations <sip-ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip-ops>, <mailto:sip-ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-ops>
List-Post: <mailto:sip-ops@ietf.org>
List-Help: <mailto:sip-ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-ops>, <mailto:sip-ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Apr 2009 19:12:28 -0000

We have set up a new list for discussion of SIP Operational issues.  
You can subscribe at

https://www.ietf.org/mailman/listinfo/sip-ops

The purpose of the SIP-Ops mailing list is to discuss issues and
requirements related to operating a SIP domain, which may drive the
need for IETF standardization or Best-Common-Practice documentation.
For example, issues or needs related to troubleshooting, diagnostics,
security, and administration relating to operating a SIP domain would
be candidates for this list. This is not a list to ask questions
about implementing current standards, nor about specific
product/vendor issues. Issues related to peering between domains are
more appropriate for discussion in SPEERMINT.

Thanks to Victor and Hadriel for running the list.

Cullen <RAI AD>

PS - if you reply to this email, please trim the WGs on the too line  
appropriate. We don't need threads cross posted to several mailing  
lists.