[jdev] Off-topic: DANE applicability in JP (Re: Securing XMPP)

[Peter Saint-Andre]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 8/29/13 1:47 AM, Yusuke DOI wrote:
> (Warning: off-topic)

Not off-topic at all!

> Dear Peter,
> 
> (2013-08-29 10:27), Peter Saint-Andre wrote:
>> And our friends in .jp don't even have DNS SRV support yet!
> 
> I asked a question on current situation of .jp to some of my DNS 
> friends. They told me the issue is resolved. Also, they're aware of
> the issue that a major DNS hosting service does not accept SRV and
> some other useful RRTYPEs. But even in jp domain one can use one's
> own DNS server to enable SRV-based discovery as usual :-) (ah, and
> SRV is an essential part of EXI alternative transport)
> 
>> Hi,
>> 
>> .jp TLD also supports DNSSEC validation since January 2011. So,
>> DNSSEC/DANE can be used technically under .jp TLD, like .se.
>> 
>> But perhaps you know, you need to choose "DNSSEC-ready"
>> registrar. I believe it is the same situation like .se, and
>> other DNSSEC-supported TLDs.
> 
> Best Regards,

Thanks for the report. That is good news!

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSKgXwAAoJEOoGpJErxa2p250QAJGy2cpTg9S8ag8Z3UD6/0vb
CgUYBp3dzPnzFSOCY9vX3FM6SRjlaagRxHhqQy7TWdMXWL5gEutwIu5Zdfmnv6f5
0osOETLZnyB/ctsoTunIrMo1gzCT3ADl08+ybdnXmdH4MRnfa25JKYvQ4UVD2Kvn
QlCg7wZfcsBqcsAHvlrVdG/u2sQkrGGwE6Lw1kRquHckoJmLwyvcVDS9k0TJhLHW
N9DJiGMplsurNQHT+Uuniow/kIYhavh5mhetN5b9PMQciLALVq2Mhl6oAA15jPWq
1iZJc9RLjCxx5UTbVjb09hkfZb9XP8neY8yRocxXN1Tm0ZBEANhp3k6Robftngka
ymKkH+kuXJkhDskrK342LKUPnE7N9PdPaesePnzU/3Dvm1CtEI5p0ztL5zWDUQfF
1j5xBe/3NDHzeot0taha4dNwVvAEr6VEL57fU6Le02KbnSjgNsWg5ecsfpAwkrPE
LZJcQcWuQSSXceSeVgBX7BebZPj+O8hfOM+dB+84KxVMyXvCqQqjVqnaukJvj71J
Wnr+OzmX4p3dlk0o++g0iB/RI+w+wiAYgMOYxjbchshBy/eTe4Y8tUchKEvO2vTe
YKHTuquDuZ8cEgxr/80a/UCLq3oWMJkR9SzwV/mIgb95CYsw16HkbyVtElI0hIpZ
s2Dvv43SNqyTzcugfjWk
=ace3
-----END PGP SIGNATURE-----