RADEXT%20Issues%20and%20Fixes - PowerPoint PPT Presentation

About This Presentation
Title:

RADEXT%20Issues%20and%20Fixes

Description:

Issue 242 (EAP) Errata in RFC 3579. Clarify use of State attribute to support EAP. Issue 55 Errata in RFC 3576. Allow Message ... Issue 60 Errata in RFC 2869. ... – PowerPoint PPT presentation

Number of Views:30
Avg rating:3.0/5.0
Slides: 8
Provided by: dne47
Learn more at: https://www.ietf.org
Category:

less

Transcript and Presenter's Notes

Title: RADEXT%20Issues%20and%20Fixes


1
RADEXT Issues and Fixes
  • David B. Nelson
  • RADEXT WG
  • IETF 62
  • Minneapolis, MN

2
The Issues and Fixes Draft
  • In the WG charter as a work item
  • Intended to be an Informational RFC
  • Covers problems, issues and points of confusion
    in existing RADIUS RFCs
  • Protocol issues or documentation issues
  • Not to be used to introduce new features,
    functionality or usages

3
Repository of Issues
  • The current issues list is maintained at
    http//www.drizzle.com/aboba/RADEXT/
  • Add new issues using the issue template (at the
    sane location) and e-mail to the WG mailing list

4
Summary of Issues
  • Issue 242 (EAP) Errata in RFC 3579. Clarify use
    of State attribute to support EAP.
  • Issue 55 Errata in RFC 3576. Allow
    Message-Authenticator in CoA messages.
  • Issue 60 Errata in RFC 2869. Updates RFC 2866
    with respect to Interim-Update value of
    Acct-Status-Type.
  • Issue 61 Clarification of RFC 2865. Describe
    what to do with multiple instances of the
    Filter-ID attribute.

5
Summary of Issues
  • Issue 62 Clarification of RFC 2865. The
    Service-Type attribute has implicit Mandatory
    status.
  • Issue 63 Clarification to RFC 3579. Practices
    for extending the Request-ID beyond 8 octets.
  • Issue 67 Clarification to RFC 2865 and RFC 3580.
    What types of traffic count toward maintaining
    the sessions Idle-Timeout value?

6
Summary of Issues
  • Issue 68 Clarification to RFC 2865 (and others).
    How is RADIUS used to authorize provisioning of
    services beyond layer 2 or layer 3 network
    access?
  • Issue 69 Clarification of RFC 3576. Use of the
    Authorize-Only Service-Type within CoA messages.
  • Issue (tba) Clarification of RFC 2869.
    Appropriate use of the Access-Reject message, as
    opposed to the Access-Challenge message.

7
Next Steps
  • Stimulate a fuller discussion of these issues on
    the WG mailing list
  • One e-mail thread per issue
  • Start the RADEXT Issues and Fixes I-D
  • Dave Nelson volunteers to act as document Editor
  • Need Authors, Contributors and Reviewers to step
    forward
Write a Comment
User Comments (0)
About PowerShow.com