From tlr+bounce@w3.org Mon Jun  2 09:27:54 2008
Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU
	[18.7.7.76])
	by pch.mit.edu (8.13.6/8.12.8) with ESMTP id m52DRshp021347
	for <saag@PCH.mit.edu>; Mon, 2 Jun 2008 09:27:54 -0400
Received: from mit.edu (W92-130-BARRACUDA-1.MIT.EDU [18.7.21.220])
	by fort-point-station.mit.edu (8.13.6/8.9.2) with ESMTP id
	m52DRiju003453
	for <saag@mit.edu>; Mon, 2 Jun 2008 09:27:44 -0400 (EDT)
Received: from homer.w3.org (ssh.w3.org [128.30.52.60])
	by mit.edu (Spam Firewall) with ESMTP id 9BCFE92E56F
	for <saag@mit.edu>; Mon,  2 Jun 2008 09:27:17 -0400 (EDT)
Received: from iCoaster.does-not-exist.org (homer.w3.org [128.30.52.30])
	by homer.w3.org (Postfix) with ESMTP id 243AF4F4CF;
	Mon,  2 Jun 2008 09:27:17 -0400 (EDT)
Received: from tlr by iCoaster.does-not-exist.org with local (Exim 4.66)
	(envelope-from <tlr+bounce@w3.org>)
	id K1U81G-001LGQ-HM; Mon, 02 Jun 2008 15:27:16 +0200
Date: Mon, 2 Jun 2008 15:27:16 +0200
From: Thomas Roessler <tlr@w3.org>
To: saag@mit.edu
Message-ID: <20080602132716.GF553@iCoaster.does-not-exist.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.17 (2007-11-01)
X-Spam-Score: 0.12
X-Spam-Flag: NO
X-Scanned-By: MIMEDefang 2.42
Cc: frederick.hirsch@nokia.com
Subject: [saag] W3C charters XML Security Working Group
X-BeenThere: saag@mit.edu
X-Mailman-Version: 2.1.6
Precedence: list
List-Id: IETF Security Area Advisory Group <saag.mit.edu>
List-Unsubscribe: <http://mailman.mit.edu/mailman/listinfo/saag>,
	<mailto:saag-request@mit.edu?subject=unsubscribe>
List-Archive: <http://mailman.mit.edu/pipermail/saag>
List-Post: <mailto:saag@mit.edu>
List-Help: <mailto:saag-request@mit.edu?subject=help>
List-Subscribe: <http://mailman.mit.edu/mailman/listinfo/saag>,
	<mailto:saag-request@mit.edu?subject=subscribe>
X-List-Received-Date: Mon, 02 Jun 2008 13:27:54 -0000

Hello,

the W3C has chartered a new XML Security Working Group:

  http://www.w3.org/2008/xmlsec
  http://www.w3.org/2008/02/xmlsec-charter

The Group is tasked to take next steps with the XML Signature and
XML Encryption family of specifications, as discussed at the
workshop last September:

  http://www.w3.org/2007/xmlsec/ws/

If you're interested in this work and work for a W3C member
organization, please contact your Advisory Committee Representative.
If you don't know who that is, I'll be happy to make introductions.

If you're interested, but don't work for a W3C member organization,
please contact Frederick Hirsch (chair) and myself.

Thanks,
-- 
Thomas Roessler, W3C  <tlr@w3.org>  +33-4-89063488

From Craemer@isoc.org Mon Jun  2 14:33:30 2008
Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU
	[18.7.21.83])
	by pch.mit.edu (8.13.6/8.12.8) with ESMTP id m52IXUlQ016804
	for <saag@PCH.mit.edu>; Mon, 2 Jun 2008 14:33:30 -0400
Received: from mit.edu (M24-004-BARRACUDA-3.MIT.EDU [18.7.7.114])
	by pacific-carrier-annex.mit.edu (8.13.6/8.9.2) with ESMTP id
	m52IXFBK001074
	for <saag@mit.edu>; Mon, 2 Jun 2008 14:33:17 -0400 (EDT)
Received: from smtp140.iad.emailsrvr.com (smtp140.iad.emailsrvr.com
	[207.97.245.140])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mit.edu (Spam Firewall) with ESMTP id 6057DF687C5
	for <saag@mit.edu>; Mon,  2 Jun 2008 14:32:51 -0400 (EDT)
Received: from relay4.r5.iad.mlsrvr.com (localhost [127.0.0.1])
	by relay4.r5.iad.mlsrvr.com (SMTP Server) with ESMTP id E7C1DDF14
	for <saag@mit.edu>; Mon,  2 Jun 2008 14:32:50 -0400 (EDT)
Received: by relay4.r5.iad.mlsrvr.com (Authenticated sender:
	craemer-AT-isoc.org) with ESMTP id D41F3DF04
	for <saag@mit.edu>; Mon,  2 Jun 2008 14:32:50 -0400 (EDT)
From: "Kevin Craemer" <Craemer@isoc.org>
To: <saag@mit.edu>
Date: Mon, 2 Jun 2008 14:32:50 -0400
Message-ID: <000b01c8c4df$0ff896c0$e501a8c0@ISOC.local>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcjE3w9WBebyC+wFRv+5IUpLiXq0uQ==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Spam-Score: 0.14
X-Spam-Flag: NO
X-Scanned-By: MIMEDefang 2.42
X-Mailman-Approved-At: Mon, 02 Jun 2008 14:50:54 -0400
Subject: [saag] Network & Distributed System Security Symposium - Call for
	Papers
X-BeenThere: saag@mit.edu
X-Mailman-Version: 2.1.6
Precedence: list
List-Id: IETF Security Area Advisory Group <saag.mit.edu>
List-Unsubscribe: <http://mailman.mit.edu/mailman/listinfo/saag>,
	<mailto:saag-request@mit.edu?subject=unsubscribe>
List-Archive: <http://mailman.mit.edu/pipermail/saag>
List-Post: <mailto:saag@mit.edu>
List-Help: <mailto:saag-request@mit.edu?subject=help>
List-Subscribe: <http://mailman.mit.edu/mailman/listinfo/saag>,
	<mailto:saag-request@mit.edu?subject=subscribe>
X-List-Received-Date: Mon, 02 Jun 2008 18:33:30 -0000


Please consider responding to this Call for Papers.

Kevin Craemer
Internet Society

= = = = = = = = =

CALL FOR PAPERS

Network and Distributed System Security Symposium (NDSS '09)
The Catamaran Resort Hotel and Spa
San Diego, California
February 8-11, 2009

Submissions due: September 12, 2008

NDSS fosters information exchange among research scientists and
practitioners of network and distributed system security services. The
target audience includes those interested in practical aspects of network
and distributed system security, with a focus on actual system design and
implementation (rather than theory). A major goal is to encourage and enable
the Internet community to apply, deploy, and advance the state of available
security technology. The proceedings are published by the Internet Society.
Submissions are solicited in, but not limited to, the following areas:

- Security of Web-based applications and services.
- Anti-malware techniques: detection, analysis, prevention.
- Intrusion prevention, detection, and response.
- Security for electronic voting.
- Combating cyber-crime: anti-phishing, anti-spam, anti-fraud techniques.
- Privacy and anonymity technologies.  
- Network perimeter controls: firewalls, packet filters, application
gateways.  
- Security for emerging technologies: sensor networks, wireless/mobile (and
ad hoc) networks, personal communication systems. 
- Security for peer-to-peer and overlay network systems.  
- Security for electronic commerce: e.g., payment, barter, EDI,
notarization, timestamping, endorsement, and licensing.  
- Implementation, deployment and management of network security policies.  
- Intellectual property protection: protocols, implementations, metering,
watermarking, digital rights management.  
- Integrating security services with system and application security
facilities and protocols.
- Public key infrastructures, key management, certification, and revocation.

- Special problems and case studies: e.g., tradeoffs between security and
efficiency, usability, reliability and cost.  
- Security for collaborative applications: teleconferencing and
video-conferencing.
- Software hardening: e.g., detecting and defending against software bugs
(overflows, etc.)  
- Security for large-scale systems and critical infrastructures. 
- Integrating security in Internet protocols: routing, naming, network
management.  

For more information, please see
http://www.isoc.org/isoc/conferences/ndss/09/


From Pasi.Eronen@nokia.com Wed Jun 18 06:09:57 2008
Received: from pacific-carrier-annex.mit.edu (PACIFIC-CARRIER-ANNEX.MIT.EDU
	[18.7.21.83])
	by pch.mit.edu (8.13.6/8.12.8) with ESMTP id m5IA9ugd005368
	for <saag@PCH.mit.edu>; Wed, 18 Jun 2008 06:09:56 -0400
Received: from mit.edu (M24-004-BARRACUDA-3.MIT.EDU [18.7.7.114])
	by pacific-carrier-annex.mit.edu (8.13.6/8.9.2) with ESMTP id
	m5IA9jaU020536
	for <saag@mit.edu>; Wed, 18 Jun 2008 06:09:45 -0400 (EDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mit.edu (Spam Firewall) with ESMTP id 7ABF3F9CC08
	for <saag@mit.edu>; Wed, 18 Jun 2008 06:09:24 -0400 (EDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m5IA98Y6006533 for <saag@mit.edu>; Wed, 18 Jun 2008 13:09:22 +0300
Received: from vaebh103.NOE.Nokia.com ([10.160.244.24]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 18 Jun 2008 13:09:13 +0300
Received: from vaebe104.NOE.Nokia.com ([10.160.244.59]) by
	vaebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 18 Jun 2008 13:09:07 +0300
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Wed, 18 Jun 2008 13:09:06 +0300
Message-ID: <1696498986EFEC4D9153717DA325CB72F38710@vaebe104.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Mailing list move
Thread-Index: AcjRK1e1VYBvV6bRR2GRw/p70bpR/A==
From: <Pasi.Eronen@nokia.com>
To: <saag@mit.edu>
X-OriginalArrivalTime: 18 Jun 2008 10:09:07.0307 (UTC)
	FILETIME=[582AFBB0:01C8D12B]
X-Nokia-AV: Clean
X-Spam-Score: 2.469
X-Spam-Level: ** (2.469)
X-Spam-Flag: NO
X-Scanned-By: MIMEDefang 2.42
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by pch.mit.edu id
	m5IA9ugd005368
Subject: [saag] Mailing list move
X-BeenThere: saag@mit.edu
X-Mailman-Version: 2.1.6
Precedence: list
List-Id: IETF Security Area Advisory Group <saag.mit.edu>
List-Unsubscribe: <http://mailman.mit.edu/mailman/listinfo/saag>,
	<mailto:saag-request@mit.edu?subject=unsubscribe>
List-Archive: <http://mailman.mit.edu/pipermail/saag>
List-Post: <mailto:saag@mit.edu>
List-Help: <mailto:saag-request@mit.edu?subject=help>
List-Subscribe: <http://mailman.mit.edu/mailman/listinfo/saag>,
	<mailto:saag-request@mit.edu?subject=subscribe>
X-List-Received-Date: Wed, 18 Jun 2008 10:09:57 -0000

Hi all,

The SAAG mailing list will be moved from mit.edu to ietf.org in 
the near future.

Current subscribers will be automatically subscribed to the new list
(and you'll get a message from Mailman when this has happened).
Depending on how you've configured your mail filters/procmail
rules, you may have to update them.

We'll provide more information when we know the exact cutoff date,
new archive location, etc.

Best regards,
Pasi (& Tim)


