[DNSOP] Dnsdir last call review of draft-ietf-dnsop-dnssec-bootstrapping-08

Reviewer: Scott Rose Review result: Ready I believe the draft is ready, with a minor typo/nit that don't change the document: In Section 5.1 second paragraph has "Signaling Zone" while other instances are "signaling zone". Scott _

[DNSOP] Dnsdir early review of draft-ietf-dnsop-dnssec-bootstrapping-04

Reviewer: Scott Rose Review result: Ready with Issues Review of dnssec-bootstrapping The draft is likely OK to proceed as there are only a few nits that do not change the overall contents. I am confused about if it adds to methods in RFC 8078 or replaces methods in RFC 8078. 1. Abstract

[DNSOP] Dnsdir telechat review of draft-ietf-dnsop-rfc5933-bis-12

Reviewer: Scott Rose Review result: Ready with Nits This Internet-Draft assigns a code point to a cryptographic algorithm for use in DNSSEC and obsoletes a preceding algorithm. The DNS and DNSSEC protocols are not changed in any way and in that sense of review the I-D is Ready. The nits listed

Re: [DNSOP] New Version Notification for draft-kumari-ogud-dnsop-cds-00.txt

dropping it. Registrars/service providers can figure that out on their own (if they haven't already). Scott Paul ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop === Scott Rose NIST

Re: [DNSOP] identitytheft.gov DNSSEC Issue

identitytheft.gov. Looks like it’s been this way for about a week. Todd Szymanski| Data Network Administration Sprint | Service Management ATT1..c === Scott Rose NIST scott.r...@nist.gov +1 301-975-8439

Re: [DNSOP] WGLC: draft-ietf-dnsop-dnssec-dps-framework-04.txt

___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop === Scott Rose NIST sco...@nist.gov +1 301-975-8439 Google Voice: +1 571-249-3671 http://www.dnsops.gov

Re: [DNSOP] RFC4641bis Section 4.4.5 proposed new text

Antoin Verschuren wrote: Hi All, I have drafted some new proposed text for section 4.4.5 of RFC4641bis. I tried to bring some more structure to the section while maintaining most of the text from the current iteration of the document. It now clearly separates: -Definition of terms

Re: [DNSOP] dns data exchanged between host and local dns-sever

___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop -- Scott RoseComputer Scientist NIST ph: +1 301-975-8439 scott.r...@nist.gov http://www-x.antd.nist.gov/dnssec http

Re: [DNSOP] WGLC: DNSSEC Trust Anchor Configuration and Maintenance

... Also, as Paul pointed out, it looks like Paul and I are one person with a long name. :) Scott -- Scott RoseComputer Scientist NIST ph: +1 301-975-8439 scott.r...@nist.gov http://www-x.antd.nist.gov/dnssec http://www.dnsops.gov

Re: [DNSOP] Proposed changes to RFC 4641: rollovers

/dnsop === Scott Rose NIST [EMAIL PROTECTED] ph: +1 301-975-8439 http://www-x.antd.nist.gov/dnssec http://www.dnsops.gov/ === ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman

[DNSOP] question on nameserver management reqs draft

that would need to view configuration options, but would not be allowed to modify, add or delete (e.g. some security auditor). Scott === Scott Rose NIST [EMAIL PROTECTED] ph: +1 301-975-8439 http://www-x.antd.nist.gov/dnssec http://www.dnsops.gov

Re: [DNSOP] suggestion for 4641bis: key algorithm rollover section

algorithm, the integrity of the zone is never broken. ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop === Scott Rose NIST [EMAIL PROTECTED] ph: +1 301-975-8439 http://www

Re: [DNSOP] Revising RFC 4641 on DNSSEC Operational Practices

://www.ietf.org/mailman/listinfo/dnsop -- Scott RoseComputer Scientist NIST ph: +1 301-975-8439 [EMAIL PROTECTED] http://www-x.antd.nist.gov/dnssec http://www.dnsops.gov

Re: [DNSOP] I-D Action:draft-ietf-dnsop-dnssec-trust-anchor-01.txt

___ DNSOP mailing list DNSOP@ietf.org http://www.ietf.org/mailman/listinfo/dnsop -- Scott RoseComputer Scientist NIST ph: +1 301-975-8439 [EMAIL PROTECTED] http://www-x.antd.nist.gov/dnssec http://www.dnsops.gov