[Sip] Future of this mailing list

"DRAGE, Keith (Keith)" <drage@alcatel-lucent.com> Wed, 15 April 2009 13:24 UTC

Return-Path: <drage@alcatel-lucent.com>
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 66DC13A6E49 for <sip@core3.amsl.com>; Wed, 15 Apr 2009 06:24:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.063
X-Spam-Level:
X-Spam-Status: No, score=-4.063 tagged_above=-999 required=5 tests=[AWL=-1.814, BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 ObNzHFWdK2Em for <sip@core3.amsl.com>; Wed, 15 Apr 2009 06:24:15 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id 660DB3A6C1C for <sip@ietf.org>; Wed, 15 Apr 2009 06:24:15 -0700 (PDT)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail2.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n3FDPPO2011087 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <sip@ietf.org>; Wed, 15 Apr 2009 15:25:25 +0200
Received: from FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com ([135.120.45.39]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Wed, 15 Apr 2009 15:25:26 +0200
From: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
To: "sip@ietf.org" <sip@ietf.org>
Date: Wed, 15 Apr 2009 15:25:23 +0200
Thread-Topic: Future of this mailing list
Thread-Index: Acm9zaHI39/zqgJ8TyuYMcInmZfROQ==
Message-ID: <28B7C3AA2A7ABA4A841F11217ABE78D675884B51@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.80
Subject: [Sip] Future of this mailing list
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2009 13:24:16 -0000

If you are currently using this mailing list for discussion of documents other than those listed below:

-	you should consider subscribing to one, other or both of the sipcore or dispatch mailing lists.

https://www.ietf.org/mailman/listinfo/dispatch

https://www.ietf.org/mailman/listinfo/sipcore

-	you should think about starting new threads, and transferring existing threads to these mailing lists (see the charters to work out which one). Obviously as everyone needs to resubscribe, you should probably leave this a week or so until that has occurred.

My understanding of the documents that should continue to be discussed on this list (because they are all with the IESG or beyond) are:

-	draft-ietf-sip-gruu (in RFC editor's queue)
-	draft-ietf-sip-ice-option-tag (in RFC editor's queue)
-	draft-ietf-sip-sips (in RFC editor's queue)
-	draft-ietf-sip-dtls-srtp-framework (in RFC editor's queue)

-	draft-ietf-sip-outbound
-	draft-ietf-sip-certs
-	draft-ietf-sip-session-policy-framework
-	draft-ietf-sip-record-route-fix
-	draft-ietf-sip-body-handling
-	draft-ietf-sip-connect-reuse
-	draft-ietf-sip-domain-certs
-	draft-ietf-sip-eku
-	draft-ietf-sip-ua-privacy
-	draft-ietf-sip-xcapevent

-	draft-ietf-sip-location-conveyance (until potential transfer to GEOPRIV or some other handling is discussed and resolved)

I hope I have the above list correct. If you think there are errors then please inform me.

General discussion of sip issues should not occur on this list.

And finally, I suggest that crossposting to multiple lists (old or new) should be avoided.

regards

Keith