RE: [802.21] IS Higher Layer Transport Requirements conf call on December 8
Yoshi,
I think the conclusion of the discussion in Vancouver was that since
802.21 does not have enough expertise to work on security (and that
include threat analysis), we will leave the security work to MIPSHOP.
Stefano
>-----Original Message-----
>From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
>Sent: Wednesday, December 07, 2005 5:40 PM
>To: Faccin Stefano (Nokia-NRC/Dallas)
>Cc: STDS-802-21@listserv.ieee.org
>Subject: Re: [802.21] IS Higher Layer Transport Requirements
>conf call on December 8
>
>Hi,
>
>I have the following discussion item for the IS requirements.
>
>There are basic security requirements in 21-05-0441-00-0000-IS_Ad Hoct:
>
>"
>The IS protocol requires that security shall be provided at
>least at the transport layer
>
> Individual security mechanisms and requirements at the
>transport layer are left to the underlying protocol
>
> Changes to the header fields, IEs and structure messages
>should not affect the security mechanisms defined for
>underlying transmission "
>
>Are they sufficient for IETF requirements? If not, we need to
>do threat analysis for IS to identify detailed security requirements.
>
>Best regards,
>Yoshihiro Ohba
>
>
>On Fri, Dec 02, 2005 at 12:59:38PM -0600, Stefano M. Faccin wrote:
>> Hi, Subir asked me to facilitate this meeting while he's on vacation.
>> Please find enclosed the conference call information.
>> Stefano
>>
>> Agenda:
>> - discussion of IS requirements wrt IETF work (continuation from the
>> Vancouver meeting): 30-60 minutes
>> - IEs and their representation (Vivek): 30 minutes
>>
>> Conference details:
>> US dial-in: +1 972 894 6500
>>
>> Conference ID: 57113
>>
>> PIN: 53187
>