RADEXT WG Virtual Interim

1
RADEXT WGVirtual Interim

• Agenda
• Tuesday, October 13, 2009
• 800 1000 AM PDT

Please join the Jabber room radext_at_jabber.ietf.or
g
2
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.

3
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

4
Virtual Meeting Tools

• RADIUS Issue Web page
• http//www.drizzle.com/aboba/RADEXT/
• Slides
• http//www.drizzle.com/aboba/RADEXT/oct_virtual_i
  nterim/
• Jabber room radext_at_jabber.ietf.org
• Can use this to discuss potential avenues to
  issue resolution, post URLs to mailing list
  messages, web pages, etc.

5
Virtual Meeting Tools (contd)

• Conference bridge
• Phone [phone]
• Conference ID 9182049
• Passcode not required
• Live Meeting Web conferencing (optional)
• http//ops.ietf.org/lists/radiusext/2009/msg00445.
  html
• Or just read these slides.
• Problem resolution
• If you are having issues, try calling baboba9132
  on Skype.

6
Alternate Conference Info

• DimDim Teleconference bridge and Web conferencing
  facilities are also available in event of an
  emergency.
• Phone [phone]
• Passcode 226220
• Web conference http//webmeeting.dimdim.com/porta
  l/JoinForm.action?meetingRoomNameabobaemailbern
  ard_aboba_at_hotmail.comdisplayNamebernard_abobaas
  Presenterfalse

7
RADEXT WG Virtual Interim Agenda

• 800 AM 820 AM Preliminaries
• Jabber scribe
• Agenda bash
• Document Status

8
Documents Completing IETF Last Call

• 820 AM 830 AM Design Guidelines, Alan DeKok,
  10 minutes
• http//tools.ietf.org/html/draft-ietf-radext-desig
  n

9
Documents Completing WG Last Call

• 830 AM -840 AM Status-Server, Alan DeKok
• http//tools.ietf.org/html/draft-ietf-radext-statu
  s-server
• 840 AM 850 AM RADIUS over TCP, Alan DeKok
• http//tools.ietf.org/html/draft-ietf-radext-tcp-t
  ransport

10
Under Consideration for Adoption

• 850 AM 900 AM, RADIUS over DTLS, Alan DeKok
• http//tools.ietf.org/html/draft-dekok-radext-dtls
  
• 900 AM 910 AM, RADIUS Attributes for IEEE 802
  Networks
• http//tools.ietf.org/html/draft-aboba-radext-wlan
  
• 910 AM 930 AM, IPv6 Attribute Design Issues,
  Hannes Tschofenig
• http//tools.ietf.org/html/draft-lourdelet-radext-
  ipv6-access

11
Feedback?