[Idr] Status and IPR messages
Susan Hares <shares@ndzh.com> Fri, 04 March 2022 01:39 UTC
Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EFCD3A09E3 for <idr@ietfa.amsl.com>; Thu, 3 Mar 2022 17:39:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.698
X-Spam-Level: *
X-Spam-Status: No, score=1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.186, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URG_BIZ=0.573, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 NBi_OM2dG3Mg for <idr@ietfa.amsl.com>; Thu, 3 Mar 2022 17:39:55 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 4EE2F3A0879 for <idr@ietf.org>; Thu, 3 Mar 2022 17:39:55 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.107.120.176;
From: Susan Hares <shares@ndzh.com>
To: idr@ietf.org
Date: Thu, 03 Mar 2022 20:39:49 -0500
Message-ID: <04cf01d82f68$bd7ade40$38709ac0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_04D0_01D82F3E.D4AA7B90"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AdgvYKEWx0HvQzK2SOyinp6pXMTvaA==
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ZoXkjWa5tjcfqKfGcbaYoTJGRAM>
Subject: [Idr] Status and IPR messages
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2022 01:39:58 -0000
I hope you survived the fast number of IPR calls today. Some might have called today's mail - IPR Spam. Below is the status, or you can just read: https://trac.ietf.org/trac/idr/wiki/idr-draft-status For those looking for your draft to enter Adoption process, you may be interested in The IDR adoption process. (https://trac.ietf.org/trac/idr/wiki/IDR%20adoption%20process) The rest of the email is a full status update in preparation for IETF 113. We'll send a delta just before IETF 113. Let me know if I missed your WG adoption request or WG LC request. Cheers, Sue IDR Adoption Process. ============== One note on our adoption process, IDR adopts two types of drafts. Type 1) drafts for approved work projects (Flow Specification, BGP auto-configuration, CAR/CT BGP-LS, and SR) or urgent requests from other WGs. Type 2) Proposed drafts - great new ideas or revisions to drafts The drafts for WG projects are subjects of interims, Discussions on IDR mail list, and coaching by IDR chairs. These drafts get WG adoption calls ASAP. The proposed drafts get added in order of request. IDR chairs have raised the question of putting draft-sas-idr-maxprefix-inbound to the head of the type 2 queue. Status (from adoption queue to RFCs) =============== Type 1: Adoptions Upcoming adoptions for BGP projects (March and early April) Flow Specification: 1 draft (3/4 to 3/18) draft-hares-flow-specification-05.txt BGP Auto-configuration: 4-5 drafts (Jeff Haas) Interim: Sept 27, 2021, Oct 18, 2021, Jan 24, 2022 Email discussion (2/28 - 3/18) Adoption call (TBD - probably before IETF 113) Note: ADs and IDR chairs will call consensus CAR/CT Drafts: draft-kaliraj-idr-bgp-clasful-transport-planes draft-dskc-bess-bgp-car Interim: Jan 24, 2022 Email discussion (2/18-3/25) Adoption call: (TBD - after IETF 113) Note: IDR/BESS will coordinate Type 2 drafts: (in order of request) 1) draft-wang-idr-bgp-ifit-capabilities 2) draft-hb-sr-p2mp-policy 3) draft-dunbar-idr-5g-edge-compute-app-meta-data 4) draft-zhou-idr-bgp-srmpls-elp 5) draft-head-idr-bgp-ls-isis-fr 6) draft-sas-idr-maxprefix-inbound Type 2 with Revision pending 1) draft-wang-idr-vpn-pref-orf-02 - 2) draft-zzhang-idr-rt-derived-community 3) draft-zzhang-idr-tunnel-encapsulation-label-stack On hold (need to chat with authors) 1) draft-chen-bgp-redist - 2) draft-wu-idr-bgp-segment-allocation-08.txt - need author response ===== Adopted/New drafts draft-ief-idr-bgpls-sr-vtn-mt-00.txt draft-ietf-idr-bfd-subcode-00.txt 2 drafts preparing to go to WG LC draft-ietf-idr-bgp-model draft-ietf-idr-sr-policy-fit 1 draft in WG LC draft-ietf-idr-wide-bgp-communities 1 draft past WG LC: draft-ietf-id-segment-routing-te-policy John Scudder noted a problem so authors Need a revision. Watch for WG LC on revisions. 6 drafts in Alvaros queue RFC7752bis + 4 bgp-ls drafts + draft-ietf-idr-rpd. RFC Since January, 2022 1 RFC (RFC9184) - draft-ietf-idr-bgp-ext-com-registry 1 approved RFC - draft-ietf-bgp-open-policy-23. 2 drafts preparing to go to WG LC draft-ietf-idr-bgp-model draft-ietf-idr-sr-policy-fit Adopted/New drafts draft-ief-idr-bgpls-sr-vtn-mt-00.txt draft-ietf-idr-bfd-subcode-00.txt
- [Idr] Status and IPR messages Susan Hares
- Re: [Idr] Status and IPR messages Susan Hares