Yes, that’s all there is.
Scott From: Barry Leiba <barryle...@computer.org> Sent: Thursday, January 28, 2021 8:34 AM To: Hollenbeck, Scott <shollenb...@verisign.com> Cc: draft-ietf-regext-dnrd-objects-mapping....@ietf.org; gustavo.loz...@icann.org; regext@ietf.org Subject: [EXTERNAL] Re: [Ext] FInal check on draft-ietf-regext-dnrd-objects-mapping-11 Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. The stuff called out by idnits will be handled by the RFC Editor, including tying up the ref to 8909 (and 6234 is already in the downref registry, so that’s been fine from last call). If that’s all there is, then we’re ready to go. Barry On Thu, Jan 28, 2021 at 8:22 AM Hollenbeck, Scott <shollenb...@verisign.com<mailto:shollenb...@verisign.com>> wrote: Belay what I just said about idnits – I got it working: Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (Dec 16, 2020) is 43 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: draft-ietf-regext-data-escrow has been published as RFC 8909 -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-3166-1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-E164' ** Downref: Normative reference to an Informational RFC: RFC 6234 -- Possible downref: Non-RFC (?) normative reference: ref. 'V42' Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 4 comments (--). We should update the reference to draft-ietf-regext-data-escrow. Scott From: Barry Leiba <barryle...@computer.org<mailto:barryle...@computer.org>> Sent: Wednesday, January 27, 2021 3:56 PM To: Gustavo Lozano <gustavo.loz...@icann.org<mailto:gustavo.loz...@icann.org>>; Hollenbeck, Scott <shollenb...@verisign.com<mailto:shollenb...@verisign.com>> Cc: draft-ietf-regext-dnrd-objects-mapping....@ietf.org<mailto:draft-ietf-regext-dnrd-objects-mapping....@ietf.org>; regext <regext@ietf.org<mailto:regext@ietf.org>> Subject: [EXTERNAL] Re: [Ext] FInal check on draft-ietf-regext-dnrd-objects-mapping-11 Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Thanks, Gustavo. Scott, will you check, as document shepherd, and then I’ll be all set. Barry On Wed, Jan 27, 2021 at 3:49 PM Gustavo Lozano <gustavo.loz...@icann.org<mailto:gustavo.loz...@icann.org>> wrote: Hello Barry, To the best of my knowledge this draft is ready for your approval. Regards, Gustavo On 1/25/21, 13:37, "Barry Leiba" <barryle...@computer.org<mailto:barryle...@computer.org>> wrote: Authors and document shepherd: I'm just doing a final check whether draft-ietf-regext-dnrd-objects-mapping-11 is ready for approval. Is there anything else you want to look over and/or tweak before I approve it? Barry
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
