Security SG aganda for Jacksonville meeting Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Security SG aganda for Jacksonville meeting To : stds-802-21@LISTSERV.IEEE.ORG Subject : Security SG aganda for Jacksonville meeting From : Yoshihiro Ohba < yohba@tari.toshiba.com > Date : Tue, 6 May 2008 11:32:30 -0400 List-Help : < http://listserv.ieee.org/cgi-bin/wa?

Permitting SET operations in a non-secure environment can have a negative effect on network operations.

The specific portion of the PNC responsible for controlling all security functions is the security manager (SM).

The specific portion of the PNC responsible for controlling all security functions is the security manager (SM).

SUBED1=STDS-802-SEC&A=1 Follow-Ups : Re: [802SEC] Mentor security certificate expired From: "Benjamin A.

security hole in 802.3hssg web site Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index security hole in 802.3hssg web site To : stds-802-3-hssg-owner@majordomo.ieee.org Subject : security hole in 802.3hssg web site From : "Roger B.

[802SEC] FW: Security Standards Opportunity Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index [802SEC] FW: Security Standards Opportunity To : "IEEE802" < stds-802-sec@ieee.org > Subject : [802SEC] FW: Security Standards Opportunity From : "Jim Carlo" < jcarlo@ti.com > Date : Tue, 14 Aug 2001 16:14:27 -0500 Importance : Normal Reply-To : < jcarlo@ti.com > Sender : owner-stds-802-sec@majordomo.ieee.org fyi and comments (I will collect), if any.

[802SEC] Link Security summary and direction Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index [802SEC] Link Security summary and direction To : < stds-802-sec@ieee.org > Subject : [802SEC] Link Security summary and direction From : "Dolors Sala" < dolors@ieee.org > Date : Wed, 12 Mar 2003 20:05:05 -0500 Sender : owner-stds-802-sec@majordomo.ieee.org Dear SEC members,   Attached is the summary of the Link Security SG meeting, including the initial set of scenarios, objectives and business level requirements for the unified security architecture.  

Security SG: teleconference April 16 Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Security SG: teleconference April 16 To : stds-802-21@LISTSERV.IEEE.ORG Subject : Security SG: teleconference April 16 From : Yoshihiro Ohba < yohba@tari.toshiba.com > Date : Tue, 15 Apr 2008 15:18:14 -0400 List-Help : < http://listserv.ieee.org/cgi-bin/wa?

Call for contributions on Security SG TR Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Call for contributions on Security SG TR To : stds-802-21@LISTSERV.IEEE.ORG Subject : Call for contributions on Security SG TR From : Yoshihiro Ohba < yohba@tari.toshiba.com > Date : Tue, 2 Oct 2007 12:56:01 -0400 List-Help : < http://listserv.ieee.org/cgi-bin/wa?

Security SG: Definition of Administrative Domain Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Security SG: Definition of Administrative Domain To : stds-802-21@LISTSERV.IEEE.ORG Subject : Security SG: Definition of Administrative Domain From : Yoshihiro Ohba < yohba@tari.toshiba.com > Date : Wed, 5 Dec 2007 21:16:11 -0500 List-Help : < http://listserv.ieee.org/cgi-bin/wa?

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: 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?

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 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?

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.

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.

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

[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: [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.

Best Regards, Yoshihiro Ohba On Fri, Jan 04, 2008 at 09:45:42AM -0500, Yoshihiro Ohba wrote: > Submission Deadline is January 7, 2008, AOE (Anywhere on Earth). > > After the deadline, I'll submit agenda for Security SG meeting in Taipei. > > Yoshihiro Ohba > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > > Follow-Ups : RE: [802.21] Security SG: Reminder for TR contribution From: Ron Pon References : Security SG: Reminder for TR contribution From: Yoshihiro Ohba Re: [802.21] Security SG: Reminder for TR contribution From: Yoshihiro Ohba Prev by Date: RE: [802.21] 802.21 Security PAR: Initial write-up Next by Date: MRPM PAR & 5C Previous by thread: Re: [802.21] Security SG: Reminder for TR contribution Next by thread: RE: [802.21] Security SG: Reminder for TR contribution Index(es): Date Thread

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.