Presentation on theme: "RADEXT WG IETF 79 Agenda Friday November 12, 2010 9:00-11:30 CST Please join the Jabber room:"— Presentation transcript:
RADEXT WG IETF 79 Agenda Friday November 12, 2010 9:00-11:30 CST Please join the Jabber room: firstname.lastname@example.org
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.
Intellectual Property When starting a presentation you MUST say if: There is IPR associated with your draft The restrictions listed in section 5 of RFC 3978/4748 apply to your draft When 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” text
Agenda (1 of 2) 0900-0920 Preliminaries (20 minutes) Blue sheets, Note takers, Jabber scribe Agenda Bash Document status 0920-0930 Hot Errata (10 minutes) Documents completing last IETF Call (20 minutes) 0930-0940: RADIUS over TCP, Alan DeKok (10 minutes) http://tools.ietf.org/html/draft-ietf-radext-tcp 0940-0950: Design Guidelines, Alan DeKok (10 minutes) http://tools.ietf.org/html/draft-ietf-radext-design/ WG Work Items (50 minutes) 0950-1010: RADIUS over TLS, Stefan Winter (20 minutes) http://tools.ietf.org/html/draft-ietf-radext-radsec 1010-1030: Dynamic Peer Discovery, Stefan Winter (20 minutes) http://tools.ietf.org/html/draft-ietf-radext-dynamic-discovery 1030-1040: RADIUS over DTLS, Alan DeKok or Stefan W. (10 min) http://tools.ietf.org/html/draft-ietf-radext-dtls
Agenda (2 of 2) Individual Submissions (30 minutes) 1040-1110: Extended Attributes, Alan DeKok (30 minutes) http://tools.ietf.org/html/draft-ietf-radext-extended-attributes Discussion and Wrap-up (20 minutes) 1110-1120: Discussion (10 minutes) 1120-1130: Next Steps: WG Chairs & AD (10 minutes)
DocumentEditorStatusNext Step(s) RFC Published Status-server (draft-ietf-radext-status-server-09) A. DeKokRFC 5997 published in AugustNone! In RFC Editor Queue None Completed IETF Last Call Design guidelines (draft-ietf-radext-design-19) A. DeKokVersion -19 published this weekDiscuss today IETF WGLC RADIUS over TCP (draft-ietf-radext-tcp-transport-09) A. DeKokVersion -09 published in October Presumably addresses all open issues Discuss today IETF WGLC Completed WG Last Call RADIUS attributes for IPv6 access (draft-ietf-radext-ipv6-access-02) W. DecWGLC completed in August; No commentsSecond WGLC TLS encryption for RADIUS (draft-ietf-radext-radsec-07) S. WinterVersion -07 published in July 3 open issues Discuss today Extended attributes I-D (draft-ietf-radext-extended-attributes-09) A. LiorVersion -09 published in May No comments received Discuss today RADEXT Status (1 of 2)
DocumentEditorStatusNext Step(s) In progress WG items (active) NAI-based peer discovery (draft-ietf-radext-dynamic discovery-02) S. WinterVersion -02 expired 2 open issues Discuss today RADIUS over DTLS (draft-ietf-radext-dtls-01) A. DeKokAccepted as WG item since IETF78 Version -01 published in Oct. Discuss today In Progress WG Items (stalled) Crypto agility requirements (draft-ietf-radext-crypto-agility-requirements-01) D. NelsonMoribund draft (expired May 2009) Still makes sense to complete Postpone until higher priority WG items are complete. Filtering and redirection attributes (draft-ietf-radext-filter-rules-03) M. SanchezMoribund draft (expired Jan. 2008) Diameter defined superset AVPs Postpone future discussion until higher priority WG items complete New tunnel types values (draft-ietf-radext-tunnel-type-00) A. TiwariMoribund draft (expired Nov. 2008)Pending PROTO writeup Under review as WG items IEEE 802 attributes (draft-aboba-radext-wlan-13) B. AbobaVersion -13 published Feb. 2010Postpone future discussion until higher priority WG items complete RADEXT Status (2 of 2)
Hot Errata Errata #DescriptionProposed next steps RFC 2865 (RADIUS) 1469 (Verified)Mismatch between attribute values and hex dump in section 7.3 Change errata to “Held for document update” status RFC2865 has 1 other errata logged RFC 4282 (Network Access Identifier) 753 (Verified)BNF in section 2.6 allows realm names to start with digit, which is not allowed by RFC1035 Change errata to “Held for document update” status since RFC 1123 does allow realms to start with digit RFC4282 has 6 other errata logged RFC 5997 (Status Server) 2507 (Reported)NIT: Bare “Access-Accept” potentially misleading in Section 3 (page 9) Change errata to “Held for document update” 2508 (Reported)NIT: Mention of “server” in section dealing only with clients in Section 4.6.2 (page 17); Due to copying text from server section Change errata to “Held for document update”
Your consent to our cookies if you continue to use this website.