RADIUS Attribute Extension Discussion

1
RADIUS Attribute Extension Discussion

• Monday July 10, 2006
• Bernard Aboba
• IETF 66, Montreal, Canada

2
Outline

• RADIUS Attribute Space A Status Report
• Question for the WG What do we do?
• Proposed Solutions

3
RADIUS Attribute Space (RFC 3575)

• RADIUS attributes types 1-255
• Attributes 1-191 may be allocated by IETF
  Consensus.
• Attributes 192-223 are reserved for experimental
  use
• Attributes 224-240 are for implementation-specific
  use
• Attributes 241-255 are reserved and should not be
  used.
• Current status 77 attributes available for
  allocation
• Attributes 17, 21, 54, 56-59, 89 and 123-191
  currently available for allocation
• Attributes 17 21 allocated only after others
  have been exhausted.

4
Likely Allocation Requests

• Completed IETF LC
• VLAN/Priority 4
• Delegated Prefix 1
• IETF WG work items
• Filter documents 3
• RADIUS GEOPRIV 8
• RADIUS MIPv4 31 attributes
• Individual submissions
• WLAN 7
• Prepaid 5 (with sub-attributes), 20 (w/o
  sub-attributes)
• Miscellaneous 5
• Total 64 79

5
Summary

• RADIUS attribute space exhaustion is possible.
• At best, we will have 13 attributes available for
  allocation after currently chartered items are
  completed.
• At worst, no attributes will be available.
• We are running out of time.
• Existing work items targeting completion in
  12-18 months.

6
A Question

• What Do We Do About It?
• Potential outcomes
• WG comes to consensus on a solution
• WG agrees that the problem is worth solving.
• WG standardizes extended RADIUS attribute space.
• Continued IANA allocation of RADIUS attributes
  enabled.
• Continued IETF work on RADIUS enabled.
• WG comes to consensus that a solution is not
  desirable
• WG agrees that the problem is not worth solving.
• No work needed on extended RADIUS attribute
  space.
• When RADIUS attribute space is exhausted,
  requests for IANA allocation will be refused.
• WG does not come to consensus on a solution
• Same effect as above.

7
If A Solution is Desirable

• Is the issue only RADIUS attribute extension?
• Or is it necessary to solve other problems at the
  same time?
• If multiple issues need to be addressed, how do
  we coordinate the response?
• Hollywood Analogy Do we embark on a series of
  adhoc cosmetic surgeries, hoping that the nips
  tucks will fit together?

8
Sense of the Room

• Is RADIUS attribute space exhaustion a problem
  worth solving?
• If so, is the RADEXT WG the right place to solve
  the problem?
• If so, is attribute exhaustion the only problem
  that should be solved?

9
Proposals Discussed in RADEXT

• Active Drafts
• Extended RADIUS Attributes, Barney Wolff Greg
  Weber
• http//www.ietf.org/internet-drafts/draft-wolff-ra
  dext-ext-attribute-00.txt
• RADIUS/Diameter AVP Translation, David Mitton
• http//www.ietf.org/internet-drafts/draft-mitton-d
  iameter-radius-vsas-01.txt
• Expired Drafts
• RADIUS Attribute Type Extension, Avi Lior Y.
  Li
• http//www.watersprings.org/pub/id/draft-lior-radi
  us-attribute-type-extension-00.txt

10
Extended RADIUS Attributes (Wolff Weber)

• Diameter AVP format within RADIUS

0 1 2
3 0 1 2 3 4 5 6 7 8 9 0 1 2 3
4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
-------------------------
------- Type TBA Length
AVP Code ----------
----------------------
AVP Code V M P r r r r r
AVP Length ------------
--------------------
AVP Length Vendor-ID (opt)
-------------------
-------------
Vendor-ID (opt) Data...
------------------------
11
RADIUS/Diameter AVP Translation (Mitton)

• Diameter AVP format within RADIUS

0 1 2
3 0 1 2 3 4 5 6 7 8 9 0 1
2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
-------------------------
------- Type TBA Length
V M P r r r r r Segment
-------------------------
------- Vendor-Id
(first segment only)
-------------------------
------- Vendor
Type (first segment only)
-------------------------
------- Data...
------------------
12
RADIUS Attribute Type Extension (Lior Li)

• RADIUS Extended Attribute Space only

0 1 2
3 0 1 2 3 4 5 6 7 8 9 0 1 2 3
4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
-------------------------
------- Type 26 Length
Vendor-Id (0)
-------------------------
------- Vendor-Id (0)
Extended Type
-------------------------
------- Extended Type
Length Data...
-------------------------
-------
13
Feedback?