From nobody Sun Nov 8 18:20:11 2020 Return-Path: X-Original-To: dnsop@ietfa.amsl.com Delivered-To: dnsop@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 452323A10BD; Sun, 8 Nov 2020 18:20:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.087 X-Spam-Level: X-Spam-Status: No, score=-2.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IQhWvrUNTsMw; Sun, 8 Nov 2020 18:20:09 -0800 (PST) Received: from mail-oi1-x233.google.com (mail-oi1-x233.google.com [IPv6:2607:f8b0:4864:20::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD79E3A10B9; Sun, 8 Nov 2020 18:20:08 -0800 (PST) Received: by mail-oi1-x233.google.com with SMTP id u127so8723405oib.6; Sun, 08 Nov 2020 18:20:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=HGkzconKJqjyfU6WHkOUNKc1UptvvPjURyI/tHn7MC8=; b=TmpEP102CZSF3N7lnOVXkArudvRhLE3+WOQyI8pSTPqKEzJuFnZlRqPim45DIY4nmD PbljvrSm6HoYxpcQEYcdJnjtfNSfqWlkbrndtoSPij+skI77Z00qju3q+HSdjOf7+qgS q47MAWYLK1czELxYdOgjQdnbPX5lKbBoI0/hDfZMftxLsC6YIkvQA4JPlqOO14RpbMIG 7KWkj8OCBeLfjE0Ylh9yZEjR4G7K1y/gqBRmwFsZp6ucSkIv9YESdAAt2L+DRZRCW4O/ e+d6dQD9HW97P0pm1XVS2BOtSWnrHCs9iW1muBhOS9wK4XP1LRntVUHZSsEK8KE/ZChj 8pnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=HGkzconKJqjyfU6WHkOUNKc1UptvvPjURyI/tHn7MC8=; b=JhB3KVASYxTXwAjUXMdh7zqlIuhY9MQMfKO07E6zWKQkWTDyrlhNgfmnmTHDAKM+ne uZG5OWRsVpH3jxitVCWWiVe0j3UkJHYTFyfBj3IxPqVJMLNB34LgTDfH+gKGJlqG10jG fzxhZHlvUtuyJOhDTIJC+EdqhOK1QFcZNzO9tNbFEVh/g1pUuSQKu4oo+3u4LbRQypxp bqpOe2hiCTXX2ggy/iXRWiiLd7P1Ei0JgIAyanI5avZy3/I0ZvgCLMDlHm5UdlKWtF9P csQSkerFPpm2fznIZ33ODrhPDJPn/m1VmmBE/n8K+rwgZUHaZML9gqSnnmLQU8HUg8wG 93jg== X-Gm-Message-State: AOAM530CMAONVzJG42emkZGTRS7KqfVrBGqKhdRLT0ZI6RjcIEjdR68Q TyL7OEr4pf+CgWe/HrHvcEI5KMK7OLfCe/Wpi4oA0b8O2y0XaQ== X-Google-Smtp-Source: ABdhPJxQKGnhCTxoHEK/4o34qAQdLa7ThfH0EwSEA8ChKU7Fh909+ZAVJuee0cXnc//IXL01Rinz0S6ap5jFbWM/hfo= X-Received: by 2002:aca:3605:: with SMTP id d5mr8015710oia.45.1604888407815; Sun, 08 Nov 2020 18:20:07 -0800 (PST) MIME-Version: 1.0 From: Tim Wicinski Date: Sun, 8 Nov 2020 21:19:57 -0500 Message-ID: To: dnsop Cc: dnsop-chairs Content-Type: multipart/alternative; boundary="00000000000073b93605b3a333be" Archived-At: Subject: [DNSOP] Call for Adoption: RFC8499-bis X-BeenThere: dnsop@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF DNSOP WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Nov 2020 02:20:10 -0000 --00000000000073b93605b3a333be Content-Type: text/plain; charset="UTF-8" All When the chairs discussed sending out the call for adoption, we originally planned to request for people to speak up if they had objections. However, this part was dropped when I sent the email out. The chairs would like to do a ONE week second call for adoption on RFC8499-bis. The Current text is https://tools.ietf.org/html/rfc8499 and the current terminology additions are https://tools.ietf.org/html/draft-ietf-dnsop-terminology-ter-02. There will be other small updates to RFC 8499, focused on fixing errors in the current text. Please review this draft, and we are looking for *objections to adoption*, and send comments to the list stating your objections. This call will end November 14, 2020. Thanks, tim wicinski DNSOP co-chair --00000000000073b93605b3a333be Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

A= ll


When the chairs discussed sending out the call for adoption, we or= iginally planned to request for people to speak up if they had objections.= =C2=A0 However, this part was dropped when I sent the email out.=C2=A0


RFC8499-bi= s.=C2=A0


The Current tex= t is https://tools.ietf.org/html/rfc8= 499 and the current termin= ology additions are https://tools.ietf.org/html/draft-ietf-dnsop-terminology-ter-02= . There will be other small updates to RFC 8499, focused on fixing error= s in the current text.


Please review this draft, and we are looking f= or *objections to adoption*, and send comments to the list stating your obj= ections.


This call will end November 14, 2020.=C2=A0


Thanks,

= tim wicinski

DNSOP co-chair



--00000000000073b93605b3a333be--