RADIUSDiameter Gateway RADIA Application draftzorndimeradiagate00 txt Glen Zorn

RADIUS-Diameter Gateway (RADIA) Application draft-zorn-dime-radia-gate-00. txt Glen Zorn Lionel Morand

Problem Statement • Basic guidelines for RADIUS/Diameter translation given in RFC 4005 (NASREQ) • Some limitations in the mapping process: – e. g. a single Diameter AVP can be longer than an entire RADIUS message! – Unsatisfactory workaround • e. g. REJECT Diameter message with AVP longer than 253 bytes • Proposal: • Remove any NASREQ-based translation limitation by… • … encapsulating RADIUS message in a single AVP

RADIUS-Diameter Gateway Application (RADIA) • A simple application: – One new command pair: • RADIA-Request/Answer (RDR) – One new mandatory Diameter AVP: • Radius- Message AVP • RADIUS messages are entirely encapsulated in the Radius- Message AVP and sent between Diameter end-points using RDR/RDA.

Message format RADIA-Request <RDR> : : = < Diameter Header: CC 1, REQ, PXY > RADIA-Answer <RDA> : : = < Diameter Header: CC 2, REQ, PXY > { Origin-Host } { Origin-Realm } { Destination-Realm } { Auth-Application-Id } { Radius-Message} [ User-Name ] [ Destination-Host ] * [ Proxy-Info ] * [ Route-Record ] * [ AVP ]

Next Step • Comment/question? • Support for this work? • WG document?