BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] DNSSEC
- Subject: [Discuss] DNSSEC
- From: warlord at MIT.EDU (Derek Atkins)
- Date: Sun, 07 Dec 2014 15:01:42 -0500
- In-reply-to: <54848271.4000601@gmail.com> (Richard Pieri's message of "Sun, 07 Dec 2014 11:38:09 -0500")
- References: <BN3PR0401MB1204647CA6E7523747D3077FDC670@BN3PR0401MB1204.namprd04.prod.outlook.com> <54848271.4000601@gmail.com>
Richard Pieri <richard.pieri at gmail.com> writes: > According to me, the answer to your followup question is this: given a > resolver that pre-dates RFC 3597 or does not implement RFC 3597 for > some technical reason (Internet of Things constraints perhaps?), you > cannot rely on it to pass DNSSEC RRs. Considering RFC 3597 was published in *2003* I would expect everything today to support it. -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH warlord at MIT.EDU PGP key available
- Follow-Ups:
- [Discuss] DNSSEC
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] DNSSEC
- References:
- [Discuss] DNSSEC
- From: blu at nedharvey.com (Edward Ned Harvey (blu))
- [Discuss] DNSSEC
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] DNSSEC
- Prev by Date: [Discuss] DNSSEC
- Next by Date: [Discuss] free SSL certs from the EFF
- Previous by thread: [Discuss] DNSSEC
- Next by thread: [Discuss] DNSSEC
- Index(es):