
|
Issue 35: What is the expected representation and/or encoding of FQDN as used in Diameter identities Details: Does the FQDN have a syntatic meaning or semantic., i.e. Is it suppose to just look like an ASCII version of an FQDN or does it actually have to be DNS resolvable ? Status: No activity Notes: The encoding and semantic meaning has relevance in the following: Dynamic peer connection during redirect indication Host comparison as used in Election, Origin-Host verification etc.; Dependent on encoding (DNS encoding, Internationalization support etc). Current thinking seems to indicate that the we should revert to an ASCII form of representation as a default |