1 / 9

draft-ietf-radext-filter-rules-01-txt “NAS-Traffic-Rule Attribute”

draft-ietf-radext-filter-rules-01-txt “NAS-Traffic-Rule Attribute”. Bernard Aboba Farid Adrangi Paul Congdon Avi Lior Mauricio Sanchez. draft-ietf-radext-filter-05-txt “NAS-Filter-Rule Attribute”. Bernard Aboba Paul Congdon Mauricio Sanchez IETF 67 – San Diego, CA. Agenda.

zachery-houston
Download Presentation

draft-ietf-radext-filter-rules-01-txt “NAS-Traffic-Rule Attribute”

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. draft-ietf-radext-filter-rules-01-txt “NAS-Traffic-Rule Attribute” Bernard Aboba Farid Adrangi Paul Congdon Avi Lior Mauricio Sanchez draft-ietf-radext-filter-05-txt“NAS-Filter-Rule Attribute” Bernard Aboba Paul Congdon Mauricio Sanchez IETF 67 – San Diego, CA

  2. Agenda • Draft Comparison • draft-ietf-radext-filter-05-txt • Status • Next steps • draft-ietf-radext-filter-rules-01-txt • Status • Next steps

  3. Draft Comparison draft-ietf-radext-filter-rules-01 • Two Attributes • NAS-Traffic-Rule • Acct-NAS-Traffic-Rule • Based on Diameter’s IPFilterRule format • Provides more functionality than IPFilterRule • More rule types • More actions draft-ietf-radext-filter-05 • One Attribute • NAS-Filter-Rule • Uses Diameter’s IPFilterRule format verbatim • Provides the same functionality as IPFilterRule and NAS-Filter-Rule AVP

  4. “NAS-Filter-Rule” status • Five new draft versions since IETF66 • Resolved issues • I199: Attribute Length • I202: Diameter-RADIUS GW Behavior not Specified • Open issues, quickly reaching closure • I198: Attribute Concatenation/splitting

  5. I198: Attribute Concatenation/Splitting • Base questions • How to split a long rule across multiple rules? • Allow multiple rules within one attribute? • Proposals • Over half dozen since IETF 65 • Usage of ‘tag’ field was favorite out of IETF 66 • Current: No ‘tag’ field; use only NULL between rules; Flexible rules on how rules can be placed into attributes

  6. “NAS-Filter-Rule” Next Steps • Reach consensus of changes due to I198 in draft -05 • Take -05 to WG last call

  7. “NAS-Traffic-Rule” Status • No new drafts since IETF 65… • Still waiting on comment response from issue submitters • Will follow up individually…again

  8. draft-ietf-radext-filter-rules-01-txt Open Issues • I111 – Accounting (Greg W.) • Mostly closed; Awaiting for insight from 3GPP reps • I114 – NAS-Filter-Rule Accounting (Bernard A.) • Awaiting Bernard’s response to proposal from Jan/10/06 • Diameter Compatibility • I130 – Diameter Interoperability (Bernard A.) • I164 – Review (Jari A.) • Presented proposal at IETF 65; Consensus reached • I169 – Handling unparseable rules (Greg W.) • Awaiting Greg’s response to proposal from June/22/06 • I170 – Precedence and Order for NAS-Filter-Rule (Greg W.) • Discussion ongoing; Discussed proposal at IETF 65; Need group consensus of propsal • I192 – Comments (Jouni K.) • Editorial changes made in -01 draft; Awaiting Jouni’s response to proposal from June/24/06

  9. “NAS-Traffic-Rule” Next Steps • Solution consensus of open issues over next couple of weeks • New version (-02) within month • Kickstart draft-ietf-radext-redirection-00 draft

More Related