[Roll] [roll] #155: draft-ietf-roll-security-threats

[Roll] [roll] #155: draft-ietf-roll-security-threats - LLN Device Security Model

"roll issue tracker" <trac+roll@trac.tools.ietf.org> Sun, 23 February 2014 20:19 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: roll issue tracker <trac+roll@trac.tools.ietf.org>
Precedence: bulk
Auto-Submitted: auto-generated
To: draft-ietf-roll-security-threats@tools.ietf.org, mariainesrobles@gmail.com
Date: Sun, 23 Feb 2014 20:19:26 -0000
Message-ID: <067.4659dcd26e0386f2f368b2f9adf0b460@trac.tools.ietf.org>
Resent-To: angel.lozano@upf.edu, mcr+ietf@sandelman.ca, mischa.dohler@cttc.es, roger.alexander@cooperindustries.com, tzeta.tsao@cooperindustries.com, vanesa.daza@upf.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/mz9pZA8eH8kUDi-rPIa1JZVJq6Q
Cc: roll@ietf.org
Subject: [Roll] [roll] #155: draft-ietf-roll-security-threats - LLN Device Security Model
Reply-To: roll@ietf.org

#155: draft-ietf-roll-security-threats - LLN Device Security Model

 Reported by Robert Cragie - 02/17/2014

 Section 7.5.1  Mechanisms and Operations

 Figure 5: LLN Device Security Model

 <rcc>I don't really get this diagram - it isn't really telling me much. If
 anything, it is missing the  point made earlier that security required for
 the application domain determines the level of security for routing and
 the stack. Even then, there may be different levels of security required
 in the application domain which would dictate a different approach to
 security. For example, if the LLN is only ever going to be "best effort"
 then there may not be a need to provide stringent protection on the
 routing protocol, whereas the application layer may in itself require a
 high degree of privacy between peer nodes in the LLN (e.g. a shared
 mesh)</rcc>

-- 
-------------------------------------+-------------------------------------
 Reporter:                           |      Owner:  draft-ietf-roll-
  mariainesrobles@gmail.com          |  security-threats@tools.ietf.org
     Type:  defect                   |     Status:  new
 Priority:  major                    |  Milestone:
Component:  security-threats         |    Version:
 Severity:  In WG Last Call          |   Keywords:
-------------------------------------+-------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/roll/trac/ticket/155>
roll <http://tools.ietf.org/wg/roll/>

[Roll] [roll] #155: draft-ietf-roll-security-thre… roll issue tracker
Re: [Roll] [roll] #155: draft-ietf-roll-security-… roll issue tracker
Re: [Roll] [roll] #155 (security-threats): draft-… roll issue tracker