-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Joe,
I have reviewed the document, and I support it. section 1. s/complimentary/complementary/ section 4.3. Unbound's implementation currently only accepts trust anchors after the validFrom has passed and not during add-hold-down-time before. I think it is harmless to accept not-yet-valid keys some time in advance, so I think the text is fine, but I am unsure if I should adjust my implementation. Best regards, Wouter On 31/10/15 23:18, Suzanne Woolf wrote: > Joe, > > Thanks for the update. > > Those of you who supported publication— I assume Joe will be > reminding you to review :-) > > > best, Suzanne > >> On Oct 31, 2015, at 4:50 PM, Joe Abley <jab...@hopcount.ca> >> wrote: >> >> Hi, >> >> Just a clarification to the wg, since I think my earlier note on >> this was buried in some long thread -- the authors of >> draft-jabley-dnssec-trust-anchor have taken it to the ISE and it >> has been accepted as a draft on the independent stream. >> >> The next step in the process is for some people to review it. >> Please feel free to do that and send your opinions to >> rfc-...@rfc-editor.org, ideally cc'ing the authors (directly or >> via this list) so that we know what is happening. >> >> If there are changes proposed as part of the review we will >> follow up with edits and submit them, per the usual process. >> >> Thanks all, >> >> >> Joe >> >> _______________________________________________ DNSOP mailing >> list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop > > _______________________________________________ DNSOP mailing list > DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWOJroAAoJEJ9vHC1+BF+NVO0P/2CdXDFq+R5mkYutQ7teJJrS tASghCtEySAjFk6CL8v3g3gX2Uio8Q+m48KetLUha9GbmrSFoQg3bHeFrREzJrtN SDMVfayI8mmkO//uTeY7kJ5ivgt+vVpbLi154ZxD3Qj1Xtnaykbc2cNYleu3mqWP Zz0aCPZTYfIkzOI3ywa6euGT20pJYERfuB6x7/pp5LPQJTVRgQ/ZmoninTknRbAF XmOSOsSAVCsr2c3iV6WpkMpA0EkoBwbvsqpfElKq2DtAtnfcY9Wow7xXa+t7UIar 4jjw0R1aCqBVi7dyAGgcqhszy4s0qIhOwUePbS3BUN6IJVJ4ZNluRis6Mm9IzDVn WR0l7x/8KZPLD9loDoHxrlqCeWkZG1YikRjP8WKLnAnwuMt2Mewdyk/PBNnkfiSp M4Txk4IeLUQoNIPSsLsxUNU54UcOHQYDC7C4oL0C2rtE9+pxotFafbBQyrV+7dtd hQBvgLWuturK8c6XcD1x2APV0WtOyvg06bI3X8uMqiY9Xo9z3id13+5INSbIdUHf xOMI7lcO81GvpSLMsO+MqlhDQMg4DabwhLc2fTSFEbiPNEFJYVlZuKWi2/bR61rr Xz41AcAtLyvdXnKCs5M/o9DmyRywA606/XamqbqrAZTQxIdyQzH5SviFJ24MZmW1 GO8L8IyU8czDVnztIXUg =ab3f -----END PGP SIGNATURE----- _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
