draft ietf radext filter rules 00 txt draft ietf radext redirection 00 txt
Download
Skip this Video
Download Presentation
draft-ietf-radext-filter-rules-00-txt draft-ietf-radext-redirection-00-txt

Loading in 2 Seconds...

play fullscreen
1 / 6

draft-ietf-radext-filter-rules-00-txt draft-ietf-radext-redirection-00-txt - PowerPoint PPT Presentation


  • 262 Views
  • Uploaded on

draft-ietf-radext-filter-rules-00-txt draft-ietf-radext-redirection-00-txt IETF 65 – Dallas,TX Bernard Aboba Farid Adrangi Paul Congdon Avi Lior Mauricio Sanchez The Split draft-ietf-radext-ieee802-01 split into three documents draft-ietf-radext-vlan-00 : Bernard Aboba lead editor

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'draft-ietf-radext-filter-rules-00-txt draft-ietf-radext-redirection-00-txt' - ostinmannual


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
draft ietf radext filter rules 00 txt draft ietf radext redirection 00 txt

draft-ietf-radext-filter-rules-00-txtdraft-ietf-radext-redirection-00-txt

IETF 65 – Dallas,TX

Bernard Aboba

Farid Adrangi

Paul Congdon

Avi Lior

Mauricio Sanchez

the split
The Split
  • draft-ietf-radext-ieee802-01 split into three documents
    • draft-ietf-radext-vlan-00 : Bernard Aboba lead editor
    • draft-ietf-radext-filter-rules-00 : Mauricio Sanchez lead editor
    • draft-ietf-radext-redirection-00 : editor TBA
  • Why?
    • Contentious filtering attributes impeded progress of entire document
  • Split allows staging of attribute delivery
    • draft-ietf-radext-vlan-00 completed WGLC last week
    • draft-ietf-radext-fiter-00 no later than Oct. 2006
    • draft-ietf-radext-redirection no later than Dec. 2006
attribute summary
Attribute Summary

draft-ietf-radext-ieee802-00/01

VLAN attributes

Egress-VLAN-ID

Ingress-Filters

VLAN-Name

Quality of Service Attributes

User-Priority-Table

QoS-Filter-Rule

Filter Attributes

NAS-Filter-Rule

Acct-NAS-Filter-Rule

EAP Accounting

Acct-EAP-Auth-Method

draft-ietf-radext-vlan-00

VLAN attributes

Egress-VLAN-ID

Ingress-Filters

VLAN-Name

Quality of Service Attributes

User-Priority-Table

draft-ietf-radext-filter-rules-00

Filter Attributes

NAS-Traffic-Rule

Acct-NAS-Traffic-Rule

draft-ietf-radext-redirection-00

TBD

Likely just guidelines for NAS-Traffic-Rule

filter draft issues and work items
“filter” draft issues and work items
  • Renamed NAS-Filter-Rule attribute to NAS-Traffic-Rule to avoid immediate confusion with Diameter’s version
  • Closure of number of issues
    • I102 : NAS/QOS-Filter-Rule
    • I109 : HTTP NAS-Filter-Rule assumes port 80
    • I110 : Compliance and Coherence
    • I112 : NAS-Filter-Rule
    • I116 : Technical Comments
    • I129 : Editorial NITS
  • Pending (Filter-01)
    • I167 : Compatibility with RFC2866 and RFC3576
    • I168 : Editorial Comments
filter draft open issues
“filter” draft open issues
  • I111 – Accounting (Greg W.)
    • Proposal to remove suspect wording sent to email list
  • I114 – NAS-Filter-Rule Accounting (Bernard A.)
    • Use case sent to email list
    • Discussed at IETF64
  • I115 – NITs (Dave N.)
    • Mostly closed; There is dependency on I114 for one
  • I130 – Diameter Interoperability (Bernard A.)
  • I164 – Review (Jari A.)
    • Misc. NITS; mostly closed except for Diameter issue (as I130)
  • I169 – Handling unparseable rules (Greg W.)
  • I170 – Precedence and Order for NAS-Filter-Rule (Greg W.)
i130 diameter compatibility
I130 – Diameter Compatibility
  • At IETF 64 tenuous consensus was to:

a. Not split-up attribute into multiple attribute

b. Use existing practices to allow Diameter to inherit RADIUS NAS-Filter-Rule attribute

c. Rename attribute to avoid confusion

  • Consensus fell apart on point B
    • “Diameter community should get their say on rule syntax”
    • “We shouldn’t have two related yet non-compatible attributes”
  • New proposal: Radius/Diameter Lockstep
    • DIME WG exposed to current rule syntax and given opportunity to speak up; No one thus far
    • RADEXT WG completes attribute with DIME WG formal blessing of syntax
    • DIME WG updates Diameter with *same* syntax from RADIUS
ad