NAI-based Dynamic Peer Discovery for RADIUS over TLS and DTLS

DNS definitions of RadSec servers can be either NAPTR records or SRV records. When both are defined, the resolution algorithm prefers NAPTR results (see section below). The NAPTR service field used is "AAA+RADSECT". The SRV prefix used is "_radsec._tcp". It is expected that in most cases, the label used for the records is the DNS representation (punycode) of the literal realm name for which the server is the AAA server. However, arbitrary other labels may be used if, for example, a roaming consortium uses realm names which are not associated to DNS names or special-purpose consortia where a globally valid discovery is not a use case. Such other labels require a consortium-wide agreement about the transformation from realm name to lookup label. Examples: A general-purpose AAA server for realm example.com might have DNS entries as follows: example.com. IN NAPTR 50 50 "s" "AAAS+RADSECT" "" _radsec._tcp.foobar.example.com. _radsec._tcp.example.com. IN SRV 0 10 2083 radsec.example.com. Consortium "foo" provides roaming services for banks. The realms used are of the form enterprise-name.foobankroam. The consortium operates a special purpose DNS server for the (private) TLD "foobankroam" which all AAA servers use to resolve realm names. "Rupt, Inc." is part of the consortium. On the consortium's DNS server, realm bank-rupt.foobankroam might have the following DNS entries: bank-rupt.foobankroam IN NAPTR 50 50 "a" "AAAS+RADSECT" "" "triple-a.bank-rupt.com" _radsec._tcp.bank-rupt.foobankroam IN SRV 0 10 2083 triple-a-backup.bank-rupt.com" the eduroam consortium uses realms based on DNS, but provides its services to a closed community only. However, a AAA domain participating in eduroam may also want to expose AAA services to other, general-purpose, applications (on the same or other AAA servers). Due to that, the eduroam consortium uses labels prefixed with "eduroam." and eduroam AAA servers use these labels to look up servers. An eduroam participant which also provides general-purpose AAA on a different server might have the following DNS entries: eduroam.restena.lu. IN NAPTR 50 50 "a" "AAAS+RADSECT" "" aaa-eduroam.restena.lu restena.lu. IN NAPTR 50 50 "a" "AAAS+RADSECT" "" aaa-default.restena.lu _radsec._tcp.eduroam.restena.lu. IN SRV 0 10 2083 aaa-eduroam.restena.lu. _radsec._tcp.restena.lu. IN SRV 0 10 2083 aaa-default.restena.lu.

For a given NAI-based input realm, the following algorithm is used to determine the AAA server to contact: Transform input realm into punycode. Optional: modify result from previous step according to agreed consortium procedures Perform NAPTR query for service "AAAS+RADSECT" with result of step 1 (or 2) as label If no result, continue at step 7. Evaluate NAPTR result, perform subsequent lookup steps until lookup yields one or more hostnames. Memorize Order/Preference fields for all hostnames. Continue at step 9. Prefix result of step 1 (or 2) with "_radsec._tcp." Perform SRV lookup with result of step 7 as label. This yields one or more hostname. Memorize Order/Preference fields for all hostnames. Order hostnames according to the Order/Preference fields. Perform A/AAAA RR lookup for all hosts in descending order of preference until one of the RRs results in a successful connection. For example, if the User-Name realm was 'example.com', and DNS contained the following records, the following subsequent lookups would be performed: example.com. IN NAPTR 50 50 "s" "AAAS+RADSECT" "" _radsec._tcp.example.com. _radsec._tcp.example.com. IN SRV 0 10 2083 radsec.example.com. radsec.example.com. IN AAAA 2001:0DB8::202:44ff:fe0a:f704 Then the target selected would be a RadSec server on port 2083 at IPv6 address 2001:0DB8::202:44ff:fe0a:f704. If no connection to this IPv6 address can be established, the algorithm continues to query a A record.

When using DNS without security, the replies to NAPTR, SRV and A/AAAA requests as described in section can not be trusted. RADIUS transports have an out-of-DNS-band means to verify that the discovery attempt led to the intended target (TLD/DTLS: ceritifcate verification or TLS shared secret ciphers; UDP/TCP: the RADIUS shared secret) and are safe from DNS-based redirection attacks. [Note: assuming here that a hypothetical RADIUS/UDP SRV discovery will NOT deliver the shared secret in the DNS response!] The discovery process is always susceptible to bidding down attacks if a realm has SRV records for RADIUS/UDP and/or RADIUS/TCP as well as for RADIUS/TLS and/or RADIUS/DTLS. While the SRV query will expose both transports, an attacker in the routing path might suppress the subsequent A/AAAA results for the TLS or DTLS peer and trick the inititating peer into using the weakly protected UDP or TCP transports. The use of DNSSEC can not fully mitigate this attack, since it does not provide a means to detect packet suppression. The only way to disable such bidding down attacks is by intiating connections only to the peer(s) which match or exceed a configured minimum security level. An implementation SHOULD provide a means to configure the administratively desired minimum security level.