[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [radext] #22: Review
#22: Review
Changes (by bernard_aboba@â):
* status: new => closed
* resolution: => fixed
Comment:
The proposed resolution is as follows:
Within Section 4.3, change the following text:
Proposals MUST NOT introduce new capabilities negotation features
into the RADIUS protocol, but rather MUST use the existing
mechanisms. Included in such negotiation techniques are "hint and
accept" and "hint and reject" mechanisms, where the NAS (RADIUS
client) provides a list of supported algorithms and the RADIUS server
selects one.
to:
Proposals MUST NOT introduce new capabilities negotiation features
into the RADIUS protocol, but rather MUST use existing mechanisms.
Negotiation techniques include "hint and accept" and "hint and
reject" mechanisms, where the RADIUS request provides a list of
supported algorithms and one is selected in the response. Since it
is necessary to integrity protect the list of algorithms, at least
one ciphersuite needs to be used to protect the request and response.
--
--------------------------------+-------------------------------------------
Reporter: jsalowey@â | Owner: bernard_aboba@â
Type: defect | Status: closed
Priority: major | Milestone: milestone1
Component: Crypto-Agility | Version: 1.0
Severity: Active WG Document | Resolution: fixed
Keywords: |
--------------------------------+-------------------------------------------
Ticket URL: <http://trac.tools.ietf.org/wg/radext/trac/ticket/22#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/>