RADEXT WG - PowerPoint Presentation

Slide1

RADEXT WGIETF 81

AgendaJuly 25, 20110900-1130

Please join the Jabber room:

radext@jabber.ietf.orgSlide2

Changing of the guard Outgoing co-chair Bernard A.Incoming co-chair Jouni K. Thanks for many years of RADEXT contributions Slide3

Note Well

Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: the IETF plenary session,any IETF working group, BOF or portion thereof,

the IESG or any member thereof on behalf of the IESG,

the IAB or any member thereof on behalf of the IAB,

any IETF mailing list, including the IETF list itself,

any working group or design team list, or any other list functioning under IETF auspices,

the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3978 (updated by RFC 4748) and RFC 3979(updated by RFC 4879).

Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice.

Please consult RFC 3978 (and RFC 4748) for details.

A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements.

A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.Slide4

Intellectual Property

When starting a presentation you MUST say if:There is IPR associated with your draftThe restrictions listed in section 5 of RFC 3978/4748 apply to your draftWhen asking questions or commenting on a draft:

You MUST disclose any IPR you know of relating to the technology under discussion

References

RFC 5378 and RFC 3979 (updated by RFC 4879)

“Note well” textSlide5

Agenda (1 of 2)9:00 - 09:20 AM, Preliminaries (20 minutes)Note Well, Note Takers, Jabber scribeAgenda bashDocument StatusIPv6 items (45 minutes)9:20 - 9:35 AM Radius Extensions for CGN Configurations, Dean Cheng (15 minutes)http://www.ietf.org/id/draft-cheng-behave-cgn-cfg-radius-ext-00.txt9:35 - 9:50 AM RADIUS Attributes for IPv6 Access Networks, Wojcieh Dec (15 minutes)http://tools.ietf.org/html/draft-ietf-radext-ipv6-access9:50 - 10:05 AM RADIUS accounting for traffic classes, Stefan Winter (15 min) http://tools.ietf.org/html/draft-winter-radext-fancyaccountingSlide6

Agenda (2 of 2)Enhancement items (30 minutes)10:05 AM - 10:15 AM Dynamic Peer Discovery, Stefan Winter (10 minutes)http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery10:15 - 10:25 AM RFC4282bis, Alan DeKok (10 minutes)10:25 - 10:35 AM RADIUS Protocol Extensions, Alan DeKok (10 minutes)http://tools.ietf.org/html/draft-ietf-radext-radius-extensionsSecurity items (20 minutes)10:35 - 10:45 AM RADIUS over DTLS, Alan DeKok (10 minutes)http://tools.ietf.org/html/draft-ietf-radext-dtls10:45 - 10:55 AM RADIUS over TLS, Stefan Winter (10 minutes)http://tools.ietf.org/html/draft-ietf-radext-radsecDiscussion and Wrap-up (35 minutes)10:55 – 11:15 AM Discussion (20 minutes)Email list server migration 11:15 - 11:30 AM Next Steps: WG Chairs & ADs (15 minutes) WG Goals/Milestones status Slide7

DocumentEditorStatusNext Step(s)RFC Published Nothing published since IETF80In RFC Editor QueueRADIUS over TCP(draft-ietf-radext-tcp-transport-09)A. DeKok Normative reference to RADSEC, pending its completionComplete RADSECCompleted IETF Last Call: Open Issues

Crypto agility requirements(draft-ietf-radext-crypto-agility-requirements-06)D. NelsonIETF LC completed 2011-06-14Has a DISCUSS. Has enough positions to pass once DISCUSSes are resolved. Revised ID neededCompleted WG Last Call: Open IssuesRADIUS attributes for IPv6 access (draft-ietf-radext-ipv6-access-05)W. DecVersion -05 published 2011-07-05No open issues Discuss today; Redo WGLC TLS encryption for RADIUS(draft-ietf-radext-radsec-08)S. WinterVersion -09 published 2011-07-08Discuss today; Redo WGLC RADEXT Status (1 of 2) Slide8

DocumentEditorStatusNext Step(s)In progress WG items (active)RADIUS Protocol Extensions(draft-ietf-radext-radius-extensions-01)A. DeKokVersion -01 published 2011-06-05Discuss todayRADIUS over DTLS(draft-ietf-radext-dtls-01)A. DeKokVersion -01 expired 2011-04-11Accepted as WG item at IETF78Need to restart NAI-based peer discovery(draft-ietf-radext-dynamic discovery-03)

S. WinterVersion -03 published 2011-07-11Discuss todayIn Progress WG Items (stalled)Filtering and redirection attributes(draft-ietf-radext-filter-rules-03)M. SanchezMoribund draft (expired Jan. 2008)Diameter defined superset AVPsEvaluate interest to restart post-IETF 81New tunnel types values(draft-ietf-radext-tunnel-type-00)A. TiwariMoribund draft (expired Nov. 2008)Pending PROTO writeupUnder review as WG itemsIEEE 802 attributes(draft-aboba-radext-wlan-13)B. AbobaVersion -13 published Feb. 2010DisEvaluate interest to restart post-IETF 81

RADEXT Status (2 of 2) Slide9

RADEXT Mailing ListMigrationSituationRADEXT mailing list is on legacy ops.ietf.org list serversNearly all other WGs are on www.ietf.org/mail-archive servers MotivationNo longer rely on any one individual for list supportBetter email error handling ProposalUse similar procedure used by Fred Baker and v6ops migrationTransfer all existing subscribers to new server Declare Day 1 date on which all discussion transferred to new serversLeverage same process as v6ops for archive preservation Slide10

WG Goals/MilestonesGoal/MilestoneStatusAction/UpdateDesign guidelines PRFC6158Management Authorization PRFC5607Status ServerPRFC 5997IPv6 access I-D

-05 in review Attribute Space Extension-01 in review Crypto Agility Revise ID needed New RADIUS transports TCP/TLS and UDP/DTLS-09 of TCP/TLS in review; UDP/DTLS expired IEEE 802 attributesRestart after IETF81?Slide11

Feedback?