RE: stds-802-16-mobile: Re: Security Issues Discussion
There may be a reason to specify some higher layer behaviours as a
recommended practice. E.G. An SS should use EAP-TLS as the EAP method.
The reason is that if it is a recommended practice, conformance to it
can be established, for the purposes of interoperability, even though it
is not manadatory behaviour.
Informative text cannot really be conformed to.
This is not to say I think we are very far along defining what we would
be specfiying for upper layer auth.
DJ
David Johnston
Intel Corporation
Chair, IEEE 802 Handoff ECSG
Email : dj.johnston@intel.com
Tel : 503 380 5578 (Mobile)
Tel : 503 264 3855 (Office)
> -----Original Message-----
> From: Ofer Kelman [mailto:okelman@Airspan.com]
> Sent: Thursday, November 20, 2003 4:10 AM
> To: Johnston, Dj; Kiernan, Brian G.; Jeff Mandin; csyoon@etri.re.kr
> Cc: stds-802-16-mobile@ieee.org
> Subject: RE: stds-802-16-mobile: Re: Security Issues Discussion
>
>
> All,
>
> The best suggestion I read here was to add an informative
> appendix and include all this stuff in.
>
> Ofer
>
>
> -----Original Message-----
> From: Johnston, Dj [mailto:dj.johnston@intel.com]
> Sent: 20 November, 2003 12:10 AM
> To: Kiernan, Brian G.; Jeff Mandin; csyoon@etri.re.kr
> Cc: stds-802-16-mobile@ieee.org
> Subject: RE: stds-802-16-mobile: Re: Security Issues Discussion
>
>
> The way I see it, there are hooks and mechanisms that we would be wise
> to put in to enable interworking between different networks.
>
> Defining primitives for base-base communication between networks for
> instance. We would find it difficult to define the transport without
> stepping out of scope. But the primitives map directly into normative
> behaviour that determines whether interworking is possible and we MUST
> address it because no one else will do it for us.
>
> DJ
>
>
> David Johnston
> Intel Corporation
> Chair, IEEE 802 Handoff ECSG
>
> Email : dj.johnston@intel.com
> Tel : 503 380 5578 (Mobile)
> Tel : 503 264 3855 (Office)
>
> > -----Original Message-----
> > From: owner-stds-802-16-mobile@majordomo.ieee.org
> > [mailto:owner-stds-802-16-mobile@majordomo.ieee.org] On
> > Behalf Of Kiernan, Brian G.
> > Sent: Wednesday, November 19, 2003 12:56 PM
> > To: Jeff Mandin; csyoon@etri.re.kr
> > Cc: stds-802-16-mobile@ieee.org
> > Subject: RE: stds-802-16-mobile: Re: Security Issues Discussion
> >
> >
> > Sooner is better than later, so long as the answer is good.
> Regarding
> > "internetworking between different networks", I agree that is
> > beyond our
> > scope, but we should be careful not to do anything that
> will preclude
> > it.
> >
> > -----Original Message-----
> > From: Jeff Mandin [mailto:jmandin@streetwaves-networks.com]
> > Sent: Wednesday, November 19, 2003 7:48 AM
> > To: csyoon@etri.re.kr
> > Cc: stds-802-16-mobile@ieee.org
> > Subject: stds-802-16-mobile: Re: Security Issues Discussion
> >
> > Yoon hi,
> >
> > Thanks for your msg and list of ETRI contacts. I think we
> all agree
> > regarding most of your procedural
> > suggestions. Note however that "internetworking between different
> > networks" is not part of our scope
> > or mandate. Also Brian initially suggested presenting
> > initial work in
> > January, then the final contribution
> > at the next plenary - but obviously sooner is better.
> >
> > >- We will list up the other issues to discuss in this Ad
> Hoc group
> > such as coexistence of original privacy mechanisms and open privacy
> > mechanisms, security issues during handover, >and enhancement
> > of privacy
> >
> > mechanisms, etc
> >
> > Agreed.
> >
> > Regards,
> >
> > - Jeff
> >
> >
> >
>
>