Re: [Dime] Limited flexibility with NAPTR queries
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Dime] Limited flexibility with NAPTR queries
Hi Tolga,
Something, which is bothering me recently is the limited flexibility when using NAPTR service fields to locate Diameter servers. The current values placed in the registry allow to find *a* Diameter server in a given domain. It doesn't help much if one is looking for a server for a specific application in a given domain. This could work in environments where each domain (or better said each domain which envisions use of DNS to locate its servers) has a relay/redirect as the main contact point.
My initial thoughts are:
a) We can have registry entries for each Diameter application (could be hard to manage ?)
b) We can explain in the bis document that NAPTR query should resolve to a relay/redirect for the domain, if the domain supports more than one Diameter application.
I would prefer option (b) for simplicity though I'm concerned about
explain deployment considerations such as these in the base spec. It may
open up the door for adding many more possible deployment scenarios
within the base spec. It maybe possible to add this in the guidelines
doc but I'm sure.
regards,
victor
regards,
victor
Or am I missing something?
Thanks,
Tolga
_______________________________________________
DiME mailing list
DiME at ietf.org
https://www1.ietf.org/mailman/listinfo/dime
_______________________________________________
DiME mailing list
DiME at ietf.org
https://www1.ietf.org/mailman/listinfo/dime
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.