[Bier] BIER rechartering happening
Alia Atlas <akatlas@gmail.com> Thu, 08 February 2018 19:41 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 170361272E1 for <bier@ietfa.amsl.com>; Thu, 8 Feb 2018 11:41:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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, 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 mgjAqVcMJOPV for <bier@ietfa.amsl.com>; Thu, 8 Feb 2018 11:41:20 -0800 (PST)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (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 76FC0126CF6 for <bier@ietf.org>; Thu, 8 Feb 2018 11:41:20 -0800 (PST)
Received: by mail-oi0-x22a.google.com with SMTP id j188so4350007oib.6 for <bier@ietf.org>; Thu, 08 Feb 2018 11:41:20 -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; bh=MKKfwjdwRLJ2CwR6yCPFFDAZ1C2r8sia90FFb55Kedg=; b=NtOlcq10sm7nZODjGvUBU3opONhZ1tNPdFWEq2sEFbScZEHArYP6Mwi9+kswiAZWcp Dg7LAhg0b3HPaoMTZkV8+Mf5P6/1Fo/FEbCmIe7E1wkDadXP3L14Tw6Lm6p/pyaEXzUg SC5XC+Q9zOE4PtemwnrvsijkzSDYJothlJekE9U9crZp/qX10GuwlnsnEZqFPhWZLo/1 19qCtbBzrS6wSNSAPGqXn44h03hrKXyvHmgrgHW1WKDR5jwe7X8fYuk/1WsQ7ClUNDwJ QSxkrpdddEeUQ7Cgpu0o11vRbr+BoFJixMX1IDFgRrNbCmJA0lxhA8ukGJIr+UgVlLyw ubJQ==
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; bh=MKKfwjdwRLJ2CwR6yCPFFDAZ1C2r8sia90FFb55Kedg=; b=js7ISRq+qStHBOHtyx1tpumhLgJ7UfAVws/DXnfOSi7eSi4QpKCe8HWuuFo27yHa95 dntmPrXefPtnZl6xL/RXFqXg5fBub2MqACh+kiHYAvoW2V1L6T3G/vebwN2dD2HmZT65 RlCu3F7bWrNXkNDnqHqKfXhV96C2xptJkeBcFBUrmwK4HdrxrkChTElEEx6WhfgsiaO2 YjarmTuBsMtr1TFfrM6R8bnhRVJPZzmACmx0f+L/xLbFFu4GN6Ru5POU0libxF4LXUvC oAXTZ0S6HE4TCCv31MDzj6hMiriRmLzKutNnWkdu4vpRbJM9sDl16Np7VGVq3/hMj4U0 cD8g==
X-Gm-Message-State: APf1xPCvx/YAqRyinFLBNQioatcDgB08OaS19hJVqhmJPUkcczumeOJC YWefkGzCKEbv2NPKsvOH6dGkmvMm6kkiuCmsXjkyZMlw
X-Google-Smtp-Source: AH8x227iZ5OolSWIuxmLP0X/Ot5lvr1aV3acTffJJeyBlPtPudPHQR8eklzmfUdzRMDwE3+EFUHAOWJqPX4MVyYzNhM=
X-Received: by 10.202.243.84 with SMTP id r81mr119729oih.5.1518118879109; Thu, 08 Feb 2018 11:41:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.40.246 with HTTP; Thu, 8 Feb 2018 11:41:18 -0800 (PST)
From: Alia Atlas <akatlas@gmail.com>
Date: Thu, 08 Feb 2018 14:41:18 -0500
Message-ID: <CAG4d1rdvqGqXmDW-ry_FYpEOj4zmV89RvzqJkfMMd9k+JhzoQg@mail.gmail.com>
To: bier@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c0955d0842a9c0564b898d5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/J1CUMtbpjogUWTX6d90PORBZV_U>
Subject: [Bier] BIER rechartering happening
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 08 Feb 2018 19:41:27 -0000
Hi, The BIER rechartering is happening and scheduled for internal review in 2 weeks. Based on the discussion, I've updated a few points. The current charter text is below. You can also find it (and do diffs) at: https://datatracker.ietf.org/doc/charter-ietf-bier/ It is version charter-ietf-bier-01-01. ============== The BIER (Bit Index Explicit Replication) Working Group has defined an architecture [RFC 8279] for multicast forwarding that uses an encapsulation [RFC 8296] that can be used on MPLS or Ethernet transport. The BIER-WG is now chartered to produce Standards Track RFCs and to update or do a Status Change for those RFCs previously published as Experimental (RFC 8279, RFC 8296, etc.). First and primarily, the BIER-WG will complete its work on: 1) Transition Mechanisms: The WG will describe how BIER can be introduced in existing multicast networks to shift multicast delivery either end-to-end or in part of a network from mechanisms such as PIM, ng-MVPN, etc. A minimum of the necessary mechanisms to support incremental deployment and/or managing different BIER mask-length compatibility may be defined. Operation of BIER in non-congruent topologies, i.e. topologies where not all routers are BIER capable can also be addressed. In addition to tunneling solutions, other approaches to make BIER deployable in such environments can be worked on. Each such mechanism must include an applicability statement to differentiate its necessity from other proposed mechanisms. 2) Applicability Statements: The WG will describe how BIER can be applied to multicast L3VPN and to EVPN. This draft will describe what mechanism is used to communicate the group membership between the ingress router and the egress routers, what scalability considerations may arise, and any deployment considerations. The WG will work on additional applicability statements, as needed, describing how BIER can be applied. 3) Use Case: The WG may produce one use-case document that clearly articulates the potential benefits of BIER for different use-cases. 4) Manageability and OAM: The WG will describe how OAM will work in a BIER domain and what simplifications BIER offers for managing the multicast traffic. A strong preference will be given to extensions to existing protocols. 5) Management models: The WG may work on YANG models and, as needed, management APIs to support common manageability. 6) IGP extensions. When a BIER domain falls within a "link state IGP" network, the information needed to set up the BIER forwarding tables (e.g., the mapping between a given bit position and a given egress router) may be carried in the link state advertisements of the IGP. The link state advertisements may also carry other information related to forwarding (e.g., the IGP may support multiple topologies, in which case it may be necessary to advertise which topologies are to be used for BIER forwarding). Any necessary extensions to the IGP will be specified by the WG as Standards Track, in cooperation with the LSR WG. The BIER-WG is additionally chartered to start Standards Track work on: 7) BIER in IPv6 : A mechanism to use BIER natively in IPv6 may be standardized if coordinated with the 6MAN WG and with understood applicability. 8) BIER Traffic Engineering: An architecture for BIER-TE is defined in draft-ietf-bier-te-arch; associated fundamental technology is included. 9) Extensions to support BIER in multi-area IGP Deployments The BIER-WG is chartered to investigate the following topics. The adoption of any Standards Track drafts will require a milestone approved by the responsible Area Director. 10) Novel uses of the BIER bitmap: There are a variety of proposals for additional algorithms and other uses of the BIER bitmap and encapsulation beyond BIER and BIER-TE. 11) BIER between Autonomous Domains: With understood applicability, these scenarios may be investigated. 12) Use of BIER in Controller-based Architectures: How might controllers be used to provide calculated BIRTs and/or BIFTs tables to BFRs? 13) Applicability of BIER to Applications: The WG may advise on the applicability of BIER to various applications. The BIER-WG will coordinate with several different working groups and must include the relevant other working groups during working group last call on the relevant drafts. BIER-WG will coordinate with MPLS-WG on the associated MPLS-based OAM mechanisms. BIER-WG will coordinate with LSR-WG on extensions to flood BIER-related information. BIER-WG will advise BABEL-WG on Babel extensions to support BIER. BIER-WG will coordinate with BESS-WG and IDR-WG on the applicability of existing BGP-based mechanisms for providing multicast group membership information. BIER-WG will coordinate with PIM-WG on the applicability of and extensions to PIM, IGMP, and MLD to support BIER operations and transition; BIER-WG will work directly on the applicability statements, as needed. Regards, Alia
- [Bier] BIER rechartering happening Alia Atlas