[Bier] Plans for draft-ietf-bier-ipv6-requirements

Adrian Farrel <adrian@olddog.co.uk> Sat, 01 May 2021 10:42 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D65B3A1386; Sat, 1 May 2021 03:42:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.782
X-Spam-Level:
X-Spam-Status: No, score=0.782 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAY_BE_FORGED=2.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=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 yhhnIkLgFGLB; Sat, 1 May 2021 03:42:31 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 726CB3A1382; Sat, 1 May 2021 03:42:27 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta6.iomartmail.com (8.14.4/8.14.4) with ESMTP id 141AgKgV011923; Sat, 1 May 2021 11:42:20 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 7B07C2203A; Sat, 1 May 2021 11:42:20 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs3.iomartmail.com (Postfix) with ESMTPS id 6602922032; Sat, 1 May 2021 11:42:20 +0100 (BST)
Received: from LAPTOPK7AS653V (74.197.bbplus.pte-ag1.dyn.plus.net [81.174.197.74] (may be forged)) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id 141AgJEE003461 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 1 May 2021 11:42:19 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'BIER WG'" <bier@ietf.org>
Cc: <draft-ietf-bier-ipv6-requirements@ietf.org>
Date: Sat, 1 May 2021 11:42:19 +0100
Organization: Old Dog Consulting
Message-ID: <01e801d73e76$a9f46c30$fddd4490$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: Adc+dCgezVRXt1a0SPiAUsVrQizUDw==
Content-Language: en-gb
X-Originating-IP: 81.174.197.74
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-26124.006
X-TM-AS-Result: No--4.495-10.0-31-10
X-imss-scan-details: No--4.495-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-26124.006
X-TMASE-Result: 10--4.494500-10.000000
X-TMASE-MatchedRID: UjGGZgD0m5UOwAmmWH5kBGxZ52CskxD+4Z1E3dd9R5lSCC/XvBtGypHc Remxdl5jT3xbA8Cn+evO39xuTH+S8oAAbHuIyuvnN8QmGQ8nUhovsOOmgOo1mSaTNbgbq25FQnU C1jfTwgt9bir0JAlV/yivjKXQTfpLsUfeSO4/2THVr2dC6ax+agKflB9+9kWViR84olPm6b20y3 Da3B9hq+LzNWBegCW2XC3N7C7YzrfQqQhSw0x2VGrz/G/ZSbVq+gtHj7OwNO0kshYUTZcZE797a 3xBG7FRraavcXfmWnxEziEKI+pDv2/3Vic9mx3g6Hq9RCTLxvsstHmcXeW1eBVSGW4LjW40FYnP SoXfG8ckhYHVA/r8kw==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/EUuqh0Bmy48nVPYLjNMHNZ5nkdc>
Subject: [Bier] Plans for draft-ietf-bier-ipv6-requirements
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 May 2021 10:42:34 -0000

Hi,

I notice that draft-ietf-bier-ipv6-requirements has expired.

There was lots of discussion about the draft in November and December last
year, but nothing seems to have happened since.

Is it our plan to use the draft as a repository for the results of
discussions, or is there an intention to pursue publication as an RFC.

In either case, it would be good to see an update that captures the
discussions from the end of last year.

Thanks,
Adrian