Security SG Dallas meeting agenda Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Security SG Dallas meeting agenda To : stds-802-21@LISTSERV.IEEE.ORG Subject : Security SG Dallas meeting agenda From : Yoshihiro Ohba < yohba@tari.toshiba.com > Date : Mon, 3 Nov 2008 17:19:57 -0500 Delivered-to : mhonarc@GROUPER.IEEE.ORG List-help : < http://listserv.ieee.org/cgi-bin/wa?

Security SG: Revised issue list Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Security SG: Revised issue list To : stds-802-21@LISTSERV.IEEE.ORG Subject : Security SG: Revised issue list From : Yoshihiro Ohba < yohba@tari.toshiba.com > Date : Wed, 16 Jul 2008 17:15:48 -0400 Delivered-to : mhonarc@GROUPER.IEEE.ORG List-help : < http://listserv.ieee.org/cgi-bin/wa?

Security SG: teleconference April 2 Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Security SG: teleconference April 2 To : stds-802-21@LISTSERV.IEEE.ORG Subject : Security SG: teleconference April 2 From : Yoshihiro Ohba < yohba@tari.toshiba.com > Date : Thu, 27 Mar 2008 21:30:02 -0400 List-Help : < http://listserv.ieee.org/cgi-bin/wa?

The security suite independent security requirements specify security requirements that support the security architecture and apply to all security suites.

The security suite independent security requirements specify security requirements that support the security architecture and apply to all security suites.

The security-related PIB attributes are required to manage security.

The security-related PIB attributes are required to manage security.

The security-related PIB attributes are required to manage security.

The security-related PIB attributes are required to manage security.

The security-related PIB attributes are required to manage security across all layers.

The security-related PIB attributes are required to manage security across all layers.

Security SG meeting report is available Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Security SG meeting report is available To : stds-802-21@LISTSERV.IEEE.ORG Subject : Security SG meeting report is available From : Yoshihiro Ohba < yohba@tari.toshiba.com > Date : Fri, 28 Sep 2007 11:30:03 -0400 List-Help : < http://listserv.ieee.org/cgi-bin/wa?

2005-07-18 Page 1 Secure Device Identity TutorialBorza/Viega Secure Device Identity Tutorial Mike Borza John Viega with Charles Qi Karen Zelenko 2005-07-18 Page 2 Secure Device Identity TutorialBorza/Viega Agenda ● Secure Device Identity – 100,000 foot view ● The 5 criteria ● The 10,000 foot view ● Related technologies ● Related presentations – Charles Qi, Broadcom Broadsafe HSM – Karen Zelenko – Phoenix Technologies security modules 2005-07-18 Page 3 Secure Device Identity TutorialBorza/Viega The 100,000 Foot View 2005-07-18 Page 4 Secure Device Identity TutorialBorza/Viega What is it?

Re: [STDS-802-16] Fw: [STDS-802-16] [Security] Cleaning up 802.16e secur Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Re: [STDS-802-16] Fw: [STDS-802-16] [Security] Cleaning up 802.16e security To : STDS-802-16@LISTSERV.IEEE.ORG Subject : Re: [STDS-802-16] Fw: [STDS-802-16] [Security] Cleaning up 802.16e security From : Yigal < yigall@runcom.co.il > Date : Thu, 22 Jul 2004 10:35:32 +0200 Importance : Normal In-Reply-To : < 003301c46fa9$d4e28e30$6400a8c0@pbarberdesktop > Reply-To : yigall@runcom.co.il Sender : owner-stds-802-16@LISTSERV.IEEE.ORG Title: [Àüüȸ½Å] [STDS-802-16] Cleaning up 802.16e security Hi Philip, Chulsik,   I fully support Chulsik.

[802.3_1TPCE] ***Google Secure Shared Document*** Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index [802.3_1TPCE] ***Google Secure Shared Document*** To : STDS-802-3-1TPCE@xxxxxxxxxxxxxxxxx Subject : [802.3_1TPCE] ***Google Secure Shared Document*** From : Colt Correa < ccorrea@xxxxxxxxxxxxxx > Date : Sat, 22 Apr 2017 17:37:02 -0700 Delivered-to : mhonarc@xxxxxxxxxxxxxxxx List-help : < https://listserv.ieee.org/cgi-bin/wa?

[bp] Make a secure income with Google Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index [bp] Make a secure income with Google To : stds-802-3-blade@xxxxxxxx Subject : [bp] Make a secure income with Google From : "Casey Overton" < XKKRI@xxxxxxxxxxxxx > Date : Thu, 26 Feb 2004 23:13:13 -0200 baltimore-injudicious : fay aylesbury acanthus Cc : stds-802-3-efm-copper@xxxxxxxx , stds-802-3-efm-oam@xxxxxxxx , stds-802-3-efm-p2mp@xxxxxxxx , stds-802-3-efm@xxxxxxxx , stds-802-3-hssg@xxxxxxxx , stds-802-3-pwrviamdi@xxxxxxxx Sender : owner-stds-802-3-blade@xxxxxxxxxxxxxxxxxx Title: 128.30.226.69 m In my 54 Page comprehensive guide I'll show you how to use Affiliate Programs together with Google AdWords to make a good living.  

MIH Security Use Case Discussion Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index MIH Security Use Case Discussion To : STDS-802-21@LISTSERV.IEEE.ORG Subject : MIH Security Use Case Discussion From : Lily Chen < llchen@nist.gov > Date : Mon, 12 May 2008 09:54:19 -0400 List-Help : < http://listserv.ieee.org/cgi-bin/wa?

RE: [EFM] OAM security and authentication Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index RE: [EFM] OAM security and authentication To : < mattsquire@xxxxxxx >, "Harry Hvostov" < HHvostov@xxxxxxxxxxxx > Subject : RE: [EFM] OAM security and authentication From : "Bob Barrett" < bob.barrett@xxxxxxxxxxxxxxx > Date : Tue, 18 Sep 2001 11:25:50 +0100 Cc : < malcolm.herring@btinternet.com >, < stds-802-3-efm@ieee.org > Importance : Normal In-Reply-To : < 3BA6C50F.62D9893B@xxxxxxx > Reply-To : < bob.barrett@xxxxxxxxxxxxxxx > Sender : owner-stds-802-3-efm@majordomo.ieee.org I agree, security and authentication come under Geoff's wider definition of Ethernet Subscriber Access (ESA) rather than EFM as defined by 802.3, and therefore are not really part of the layer 1 / layer 2 standards effort.

Re: [STDS-802-16] Fw: [STDS-802-16] [Security] Cleaning up 802.16e secur Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Re: [STDS-802-16] Fw: [STDS-802-16] [Security] Cleaning up 802.16e security To : STDS-802-16@listserv.ieee.org Subject : Re: [STDS-802-16] Fw: [STDS-802-16] [Security] Cleaning up 802.16e security From : "Iyer, Prakash" < prakash.iyer@INTEL.COM > Date : Thu, 22 Jul 2004 07:42:55 -0700 Reply-To : "Iyer, Prakash" < prakash.iyer@INTEL.COM > Sender : owner-stds-802-16@listserv.ieee.org Thread-Index : AcRvwbw6rXBq5N1gQKqxTUi3OLC4/AAMsAuAAAEQrXA= Thread-Topic : [STDS-802-16] Fw: [STDS-802-16] [Security] Cleaning up 802.16e security Title: [Àüüȸ½Å] [STDS-802-16] Cleaning up 802.16e security I second DJ's views on this.

["Security Suite Compromise" in response to the NO voters.

Re: [STDS-802-16] Fw: [STDS-802-16] [Security] Cleaning up 802.16e secur Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Re: [STDS-802-16] Fw: [STDS-802-16] [Security] Cleaning up 802.16e security To : STDS-802-16@listserv.ieee.org Subject : Re: [STDS-802-16] Fw: [STDS-802-16] [Security] Cleaning up 802.16e security From : "Johnston, Dj" < dj.johnston@INTEL.COM > Date : Thu, 22 Jul 2004 07:09:33 -0700 Reply-To : "Johnston, Dj" < dj.johnston@INTEL.COM > Sender : owner-stds-802-16@listserv.ieee.org Thread-Index : AcRvwbw6rXBq5N1gQKqxTUi3OLC4/AAMsAuA Thread-Topic : [STDS-802-16] Fw: [STDS-802-16] [Security] Cleaning up 802.16e security Title: [Àüüȸ½Å] [STDS-802-16] Cleaning up 802.16e security Yigal, I think (and hope) that you misunderstand the current discussion.  

= Prev by thread: Re: [STDS-802-16] Fw: [STDS-802-16] [Security] Cleaning up 802.16 e security Next by thread: Re: [STDS-802-16] Fw: [STDS-802-16] [Security] Cleaning up 802.16e security Index(es): Date Threa

Re: [STDS-802-16] Fw: [STDS-802-16] [Security] Cleaning up 802.16e secur Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Re: [STDS-802-16] Fw: [STDS-802-16] [Security] Cleaning up 802.16e security To : STDS-802-16@LISTSERV.IEEE.ORG Subject : Re: [STDS-802-16] Fw: [STDS-802-16] [Security] Cleaning up 802.16e security From : "Kiernan, Brian G." < Brian.Kiernan@INTERDIGITAL.COM > Date : Thu, 22 Jul 2004 11:12:24 -0400 Reply-To : "Kiernan, Brian G." < Brian.Kiernan@INTERDIGITAL.COM > Sender : owner-stds-802-16@LISTSERV.IEEE.ORG Thread-Index : AcRvwdl+GdpSHSWYS2yVcgIQ/wUL3AAO779g Thread-Topic : [STDS-802-16] Fw: [STDS-802-16] [Security] Cleaning up 802.16e security Title: [Àüüȸ½Å] [STDS-802-16] Cleaning up 802.16e security Yigal,   I think you made one small, but very important, error in your statement.

>I agree with people who believe that security requires >security experts.

The security considerations provide security analysis and rationale for the security architecture and algorithm suite.