Re: [radext] #85: Confidentiality Requirements

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

#85: Confidentiality Requirements

Changes (by bernard_aboba@â):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Proposal is to change the existing text to the following:

 Proposals MUST support the negotiation of cryptographic algorithms
 for per-packet integrity/authentication protection.
 It is RECOMMENDED that solutions provide support for confidentiality,
 either by supporting encryption of entire RADIUS packets or
 by encrypting individual RADIUS attributes.
 This includes providing support for improving the confidentiality of
 existing encrypted (sometimes referred to as "hidden")
 attributes as well as encrypting attributes (such as location attributes)
 that are currently transmitted in cleartext.
 Proposals supporting confidentiality MUST support the negotiation
 of cryptographic algorithms for encryption.

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

Ticket URL: <https://wiki.tools.ietf.org/wg/radext/trac/ticket/85#comment:1>
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/>