AAA%20Pending%20Issues

1
AAA Pending Issues

• This presentation will probably involve audience
  discussion, which will create action items. Use
  PowerPoint to keep track of these action items
  during your presentation
• In Slide Show, click on the right mouse button
• Select Meeting Minder
• Select the Action Items tab
• Type in action items as they come up
• Click OK to dismiss this box
• This will automatically create an Action Item
  slide at the end of your presentation with your
  points entered.

• Pat R. Calhoun
• Sun Microsystems, Inc.

2
Issues that need attention

• Result-Code AVP in proxy environments
• Accounting data format
• Accounting Polling issues
• End-to-end Security
• Transport selection
• RADIUS Migration Issues
• Data Model
• Meaning and use of M bit

3
Issues that need attention (cont)

• DIAMETER MIB
• Tight Consistency State Management
• Non-IP Filters
• IANA Considerations

4
Result-Code AVP

• The issue has to deal with the Result-Code AVP in
  a proxy environment.
• How does a NAS deal with a response that contains
  a successful Result-Code AVP from the home
  server, and a second Result-Code AVP with an
  error inserted by a proxy.
• Currently, only one such AVP can be present, so
  if two are present, which one wins? What if
  end-to-end is employed?

5
Accounting Data Format

• There has been some discussion on whether ADIF
  should be used in DIAMETER accounting.
• There are two options
• ADIF (the ADIF spec would have to be extended for
  each DIAMETER extension). It is felt that ADIF
  would increase interoperability.
• Individual AVPs (ala RADIUS). This is viewed as
  perhaps a simpler approach.

6
Accounting Polling Issues

• The issue with server initiated polling is how it
  works in a roaming scenario.
• The design team felt that polling was adequate
  for non-roaming cases, but how would a server
  treat roaming sessions differently from
  non-roaming?
• The solutions I-D recommends that polling still
  be supported, but as optional.
• Does the WG feel that polling should be supported?

7
Batched Accounting

• Batched accounting is no longer an issue, since
  it is no longer supported.

8
End-to-End Security

• End-to-End security is being covered by other
  presentations, but the following issues have been
  raised
• How is a symmetric key distributed to two
  entities across a proxy chain?
• Is this feature required? If so, could it be
  standardized at a later time in order to minimize
  the impact on other documents?

9
Transport Selection

• There is a separate presentation on this area,
  but the following issues have been raised
• Is TCP appropriate as a MAY? What are the
  interoperability implications?
• What are the proxy behavior for congestion
  control under SCTP?
• Is UDP a valid transport mapping?

10
RADIUS Migration

• The design team concluded that the text in the
  DIAMETER implementation guidelines is the correct
  approach, but a careful review of the text is
  necessary.
• A possible addition to the protocol is a new
  AVP/attribute that is included when protocol
  translation occurs. It was felt that this would
  be a very useful troubleshooting tool.

11
Data Model

• There are several presentations on the data model
  issue, but the pending issues raised are
• How could requests be distinguished from
  responses?
• What formal notation should be used in the
  DIAMETER documents? Solutions must not affect the
  on-the-wire PDU format.

12
Meaning and use of M bit

• There has been considerable discussions on
  whether the M bit should be removed.
• Specifically, the use of the M bit seems to
  have raised some objections.
• In order to move forward, its use, and how to
  deal with such errors must be well defined.

13
DIAMETER MIB

• A list of the objects that need to be managed
  needs to be identified. This work was not
  completed by the design team, who felt that the
  MIB could follow the base protocol.
• Should each extension have its own MIB, or
  should a giant MIB exist? It seems like the
  former is a better approach.
• How are sensitive objects transferred in SNMP?
  Perhaps IKE or Kerberos?

14
Tight Consistency State Management

• The Design Team was not sure that there were
  valid underlying requirements for tight
  consistency.
• This was viewed as requiring a reliable,
  scalable, distributed resource management
  protocol, that works in both roaming and
  non-roaming networks.

15
Non-IP Filters

• The solutions I-D now includes a very flexible
  filtering definition for IP, but does not attempt
  to specify the format of non-IP filters.
• Perhaps interested parties could generate an
  Internet Draft that defines such filter formats.

16
IANA Considerations

• The solutions I-D raises an interesting point
  that IANA needs to be made aware that a new
  registry needs to be created.
• Apparently, there is a delay in creating new
  registries, so the WG should get this work stated
  asap.