Re: [Roll] [roll] #136: - draft-ietf-roll-applicability-ami - Add a section of the Security Considerations for each instance where the RPL security mechanism are not to be used

["Popa, Daniel" <[e-mail]>]

Hello all, 

Chris:

Just to clarify: The applicability statement for AMI network focuses on use of RPL (+ 6LowPAN/IPv6) over standard IEEE wireless and PLC link-layer technologies  (i.e., IEEE Std 802.15.4g/4e and IEEE Std P1901.2, respectively). Each of these standards is coming with a link-layer security specification. 

Following you recommendation: we can add a new section - "Security Considerations" - to the section where we describe the link-layer security features (i.e., to the Section 9.2.3 called "Security features provided by the MAC sub-layer"). Alternatively, we can keep the Section 9.2.3 as it is and in the content that will be provided we describe how the link-layer security features will meet the requirements of the RPL security services.  Which of these approaches will better answer your request?

Would such clarifications meet your expectations? 

Regards,
Daniel

-----Message d'origine-----
De : roll issue tracker [mailto:[e-mail]] 
Envoyé : mardi 17 décembre 2013 06:51
À : [e-mail]; [e-mail]
Cc : [e-mail]
Objet : [roll] #136: - draft-ietf-roll-applicability-ami - Add a section of the Security Considerations for each instance where the RPL security mechanism are not to be used

#136: - draft-ietf-roll-applicability-ami - Add a section of the Security Considerations for each instance where the RPL security mechanism are not to be used

 Source: http://www.ietf.org/mail-archive/web/secdir/current/msg04477.html


 From: Chris Lonvick <clonvick at cisco.com>
 Date: Fri, 13 Dec 2013 11:41:54 -0800 (PST)



 “The authors note that other security mechanisms may be used, which would  mean that the security functions of RPL would not be needed. I would  recommend that a section of the Security Considerations be added for each  instance where the RPL security mechanism are not to be used. Each of  those sections should show how the replacement mechanisms will meet the  requirements of the RPL security services that are described in 6550.”

-- 
-------------------------------------+----------------------------------
-------------------------------------+---
 Reporter:                           |      Owner:  draft-ietf-roll-
  [e-mail]          |  applicability-
     Type:  defect                   |  [e-mail]
 Priority:  major                    |     Status:  new
Component:  applicability-ami        |  Milestone:
 Severity:  Active WG Document       |    Version:
                                     |   Keywords:
-------------------------------------+----------------------------------
-------------------------------------+---

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