[radext] #87: Guidance on mandatory-to-implement algorithms

["radext issue tracker" <trac+radext@zinfandel.tools.ietf.org>]

#87: Guidance on mandatory-to-implement algorithms

 Section 4.2 does not provide any guidance as to what cryptographic
 algorithms are acceptable for designation as mandatory-to-implement, nor
 does it reference any such guidance.

 My recommendation is that the following paragraph be added to Section 4.2:

 Guidance on acceptable algorithms can be found in [NIST-SP800-131A].
 It is RECOMMENDED that mandatory-to-implement cryptographic
 algorithms be chosen from among those classified as "Acceptable"
 with no known deprecation date within [NIST-SP800-131A].

-- 
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@â            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  critical                   |   Milestone:  milestone1
Component:  Crypto-Agility             |     Version:  1.0       
 Severity:  Active WG Document         |    Keywords:            
---------------------------------------+------------------------------------

Ticket URL: <https://wiki.tools.ietf.org/wg/radext/trac/ticket/87>
radext <http://tools.ietf.org/radext/>


--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>