[Bier] charter and document statuses

Alia Atlas <akatlas@gmail.com> Mon, 11 April 2016 19:08 UTC

Return-Path: <akatlas@gmail.com>
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 759EE12F34B for <bier@ietfa.amsl.com>; Mon, 11 Apr 2016 12:08:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.699
X-Spam-Level:
X-Spam-Status: No, score=-102.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 F6MqmZVKiJIu for <bier@ietfa.amsl.com>; Mon, 11 Apr 2016 12:08:09 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (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 E865112F350 for <bier@ietf.org>; Mon, 11 Apr 2016 12:08:08 -0700 (PDT)
Received: by mail-ob0-x232.google.com with SMTP id k9so21145214obk.2 for <bier@ietf.org>; Mon, 11 Apr 2016 12:08:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=SPGfZQ6mjxBb6bWR5jsdQ3pZRqBV9wKIzT83o1kTf8o=; b=nZ0cibcFsVGHxySPdWSeDJcmSvxagv7dTrSd40cfA+n+omJRpa7m+lVKuAFbJLw8ih S9BkSkFoPk+1AsQUNBljj213NeL6r/mPIIqSdfHaexwUsMIJLE9Zh7IsUs/mGeNZfnXR tPmJ7W14CDanMJ4EoocERlaSZvpHyA49vh5/o8eC0ZcDKupkoCSnevbvl5oibPUGy+wM 5wvySnxiomyeXp3811eNdiGNWlqKPlOsE3D3qbclp0YtTcEH76PVhEHBdMc4f+V420SU zGAApC9glnLARyQT39Cc0gr/xJ3aCDNmMeVsK3wH1NAcmuWssepiqwcWKEsDrpNvTtsr 9EOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=SPGfZQ6mjxBb6bWR5jsdQ3pZRqBV9wKIzT83o1kTf8o=; b=igfr0ypy7DhUCitLhvqWcXO7C8muC7IhZuxQoq5fDIby1BjmAd7DH04ZG5w/NiHW/f 5e2lGoUaB9wCPIZ5CLZnDKJfgTVgkj/B+cuq4XRjL6r3HPmc0k+BCROTTngW3ozPRnCh yq4qcKZAzOZIy2F7SjBBTDcgIFE8zBt9Dkr4tQgDEzOna29XJBwPtQga+IkEiMNylFOL QBqTCXokMI9gjZfDfnysjhSpFpwxqzU2qEJsNo9MfYB23x+4jgMJTSM/8MjXPA7+DYbb obsZavH49nCGctjfPGX+hP3xoK5HgmiIxNN9ieMaWvSPBpCmUB9dUOnWxoEapSO9O4O2 RGAQ==
X-Gm-Message-State: AD7BkJKyOhTl/41Gd9VsuA1EHXjrjAMunXtCvKBvH2s1MzDO8dqbIHbUR6/4O3xQxQ7IQ6dt3Ag5gdKRjsyhrw==
MIME-Version: 1.0
X-Received: by 10.182.38.233 with SMTP id j9mr10603425obk.57.1460401688290; Mon, 11 Apr 2016 12:08:08 -0700 (PDT)
Received: by 10.60.115.168 with HTTP; Mon, 11 Apr 2016 12:08:08 -0700 (PDT)
Date: Mon, 11 Apr 2016 15:08:08 -0400
Message-ID: <CAG4d1rd-Aad3kUYG4NL7mqx95s1+b3Vo7dYsmyDQMiEJUBb9Vg@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
To: "bier@ietf.org" <bier@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c33936dc349f05303a43bc"
Archived-At: <http://mailarchive.ietf.org/arch/msg/bier/eyPNbgs1QQ7_mNK5m_YnjlQu4kE>
Subject: [Bier] charter and document statuses
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 11 Apr 2016 19:08:10 -0000

I went back and reviewed the current BIER charter and expected work items.

The work item we had agreed upon is:


9) Deployment Evaluation: Once there is deployment experience, the
WG will produce an Informational RFC describing the benefits,
problems, and trade-offs for using BIER instead of traditional
multicast forwarding mechanisms. Ideally, this should also contain
an analysis of the impact and benefit of the new BIER data-plane to
the overall Internet architecture. This document is intended to be
used to evaluate whether to recharter BIER to produce Standards
Track RFCs.


If there is interest in changing from Experimental status, I will need to
see such a draft to support a recharter.

Thanks,
Alia