From pramod.s.pawar@bt.com Fri Jul 22 07:27:02 2011 Return-Path: X-Original-To: smime@ietfa.amsl.com Delivered-To: smime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 763F821F8AAC; Fri, 22 Jul 2011 07:27:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.555 X-Spam-Level: X-Spam-Status: No, score=-1.555 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HELO_MISMATCH_COM=0.553, HTML_FONT_SIZE_LARGE=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hSL5CiFtaHHb; Fri, 22 Jul 2011 07:27:02 -0700 (PDT) Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id C8B0D21F86A1; Fri, 22 Jul 2011 07:27:01 -0700 (PDT) Received: from smtpe1.intersmtp.com (smtp64.intersmtp.COM [62.239.224.237]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p6MEQjW9001945 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL); Fri, 22 Jul 2011 07:26:46 -0700 (MST) (envelope-from pramod.s.pawar@bt.com) Received: from EVHUB70-UKRD.domain1.systemhost.net (10.36.3.153) by RDW083A008ED64.smtp-e4.hygiene.service (10.187.98.13) with Microsoft SMTP Server (TLS) id 8.3.159.2; Fri, 22 Jul 2011 15:26:57 +0100 Received: from EVMHT03-UKBR.domain1.systemhost.net (193.113.108.56) by EVHUB70-UKRD.domain1.systemhost.net (10.36.3.153) with Microsoft SMTP Server (TLS) id 14.1.323.0; Fri, 22 Jul 2011 15:26:57 +0100 Received: from EMV01-UKBR.domain1.systemhost.net ([169.254.1.8]) by EVMHT03-UKBR.domain1.systemhost.net ([193.113.108.56]) with mapi; Fri, 22 Jul 2011 15:26:57 +0100 From: To: Date: Fri, 22 Jul 2011 15:22:18 +0100 Thread-Topic: SecureComm2011 - Call for Posters Thread-Index: AQHMSHtoSbchWvVRbkqRKXkAgK15NA== Message-ID: <3C541DF34C043743A7BE9C16B7D2F72901FA7B0A21@EMV01-UKBR.domain1.systemhost.net> Accept-Language: en-US, en-GB Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB Content-Type: multipart/alternative; boundary="_000_3C541DF34C043743A7BE9C16B7D2F72901FA7B0A21EMV01UKBRdoma_" MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 22 Jul 2011 08:08:03 -0700 Subject: [smime] SecureComm2011 - Call for Posters X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jul 2011 14:27:02 -0000 --_000_3C541DF34C043743A7BE9C16B7D2F72901FA7B0A21EMV01UKBRdoma_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable SECURECOMM 2011 CALL FOR POSTERS Seventh International Conference on Network Security & Privacy (SecureComm = 2011) London, United Kingdom Sept 7-9, 2011 WWW: http://www.securecomm.org Deadline for submissions: 3rd August 2011 Notification of Acceptance: 10th August 2011 ________________________________ The poster session will provide a forum for researchers to show their work = and obtain constructive feedback on ongoing research from knowledgeable con= ference attendees. Areas of technical interest are the same as those listed= in the technical call for papers. While the poster need not describe compl= eted work, it should report on research for which at least preliminary resu= lts are available. At least one of the authors of the poster must register for the conference = for the poster to be included as part of the poster session. SUBMISSION INSTRUCTIONS ________________________________ Each submission should also include an abstract of up to 250 words summariz= ing the research work and 2 A4 pages detailing the scientific merit of the = research work. Both the abstract and the poster must have the title, authors, institutiona= l affiliations and contact information. Please submit your poster to the Conference General Chair Dr Muttukrishnan = Rajarajan Email: r.muttukrishnan@city.ac.uk , in PDF format. PRESENTATION OF POSTERS ________________________________ Authors of accepted poster proposals will have a chance to present the post= er to interested attendees during a special poster session at the conferenc= e. Well-crafted posters will tell the story well by themselves, but author= s of posters are expected to be available to describe and discuss the work = in the poster during the session. ________________________________ --_000_3C541DF34C043743A7BE9C16B7D2F72901FA7B0A21EMV01UKBRdoma_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

= &n= bsp;

= SECURECOMM 2011

= CALL FOR POSTERS

= Seventh International Conference on Network Security & Privacy (SecureComm 201= 1)
London, United Kingdom
Sept 7-9, 2011

WWW: http://www.securecomm.org

Deadline for submissions: 3rd August 2011

Notification of Acceptance: 10th August 2011

The poster sessio= n will provide a forum for researchers to show their work and obtain constr= uctive feedback on ongoing research from knowledgeable conference attendees. Areas of technical interest are the same as those li= sted in the technical call for papers. While the poster need not describe c= ompleted work, it should report on research for which at least preliminary = results are available.

<= font color=3D"#000000">At l= east one of the authors of the poster must register for the conference for = the poster to be included as part of the poster session.

 <= /font>

SUBMISSION INSTRUCTIONS

Each submission should a= lso include an abstract of up to 250 words summarizing the research work an= d 2 A4 pages detailing the scientific merit of the research work.

Both the abstract and th= e poster must have the title, authors, institutional affiliations and conta= ct information.

Please submit your poste= r to the Conference General Chair Dr Muttukrishnan Rajarajan Email: r.muttukrishnan@city.ac.uk<= /u> , in PDF format.

 

PRESENTATION OF POSTERS

Authors of accepted post= er proposals will have a chance to present the poster to interested attende= es during a special poster session at the conference.  Well-crafted po= sters will tell the story well by themselves, but authors of posters are ex= pected to be available to describe and discuss the work in the poster durin= g the session.

 
<= /div>
--_000_3C541DF34C043743A7BE9C16B7D2F72901FA7B0A21EMV01UKBRdoma_-- From stephen.farrell@cs.tcd.ie Sun Jul 24 08:24:07 2011 Return-Path: X-Original-To: smime@ietfa.amsl.com Delivered-To: smime@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73DF121F85F7; Sun, 24 Jul 2011 08:24:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.599 X-Spam-Level: X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9TlOWk-FTdUN; Sun, 24 Jul 2011 08:24:06 -0700 (PDT) Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by ietfa.amsl.com (Postfix) with ESMTP id 93A5721F89BE; Sun, 24 Jul 2011 08:24:06 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id F1C51171C73; Sun, 24 Jul 2011 16:23:58 +0100 (IST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1311521036; bh=AWw0B9KhlJqbbS 4GKM5UtHo3hB9+W+F/AL7FGEmC4hA=; b=v2yUsJyqjVT4J8gNH5RuVx6ntuFD2y LAQt+M4kcubRwgk4afW0eLhghzW3inlGexn3XL5ml2pd3Eocrs8zzwVwCUYwf3mt 2yjBrQRB8UBTYh5w1hs7blx4AIxI/i3iiQZZlceqBEaWlPsapiC3UKyyYpjSBUnc /plLxaPdKZ9EtHDVI0d4CfaZNfRTkoyQGtNUGEFopL2ARVAY00NhE9NrhiPXxwd0 64QdooKHKFoEcibMKbBG1Yb66+YDn0twFJ+M26syqOtIe6IU7XIGeTHHkWV4Mx/N uc1GOGqXaUn0n1WlA2vuoV0yI0rGK0/YHFMZjDLuKGII5Zn0vXHqK3uA== X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id XRws5YROZAuN; Sun, 24 Jul 2011 16:23:56 +0100 (IST) Received: from [130.129.39.94] (unknown [130.129.39.94]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 991C1171BFE; Sun, 24 Jul 2011 16:23:56 +0100 (IST) Message-ID: <4E2C38F5.4090004@cs.tcd.ie> Date: Sun, 24 Jul 2011 16:23:33 +0100 From: Stephen Farrell User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.18) Gecko/20110617 Lightning/1.0b2 Thunderbird/3.1.11 MIME-Version: 1.0 To: "saag@ietf.org" , smime@ietf.org References: <20101201161335.3154FE070E@rfc-editor.org> In-Reply-To: <20101201161335.3154FE070E@rfc-editor.org> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 24 Jul 2011 11:26:00 -0700 Subject: [smime] Fwd: [Technical Errata Reported] RFC5958 (2653) X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2011 15:24:07 -0000 Just in case anyone cares I plan to mark this verified tomorrow unless I hear something to the contrary. The only reason to send it around is that Sean submitted it, I'll be verifying it and there's no current WG to shout stop, so this is really just a transparency thing. If you read the erratum, I think it'll be crystal clear that verify is the right thing. S. -------- Original Message -------- Subject: [Technical Errata Reported] RFC5958 (2653) Date: Wed, 1 Dec 2010 08:13:35 -0800 (PST) From: RFC Errata System To: turners@ieca.com, iesg@iesg.org CC: turners@ieca.com, rfc-editor@rfc-editor.org The following errata report has been submitted for RFC5958, "Asymmetric Key Packages". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5958&eid=2653 -------------------------------------- Type: Technical Reported by: Sean Turner Section: 2 and App A Original Text ------------- ct-asymmetric-key-package CONTENT-TYPE ::= { AsymmetricKeyPackage IDENTIFIED BY id-ct-KP-aKeyPackage } Corrected Text -------------- ct-asymmetric-key-package CONTENT-TYPE ::= { TYPE AsymmetricKeyPackage IDENTIFIED BY id-ct-KP-aKeyPackage } Notes ----- With the approval of errata 2612 (http://www.rfc-editor.org/errata_search.php?eid=2612), the asymmetric key package content type definition also needs to be updated to add "TYPE" to the CONTENT-TYPE definition. Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5958 (draft-turner-asymmetrickeyformat-05) -------------------------------------- Title : Asymmetric Key Packages Publication Date : August 2010 Author(s) : S. Turner Category : PROPOSED STANDARD Source : IETF - NON WORKING GROUP Area : N/A Stream : IETF Verifying Party : IESG