[Bier] BIER rechartering
Alia Atlas <akatlas@gmail.com> Tue, 23 January 2018 23:12 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 AC24A12D88C for <bier@ietfa.amsl.com>; Tue, 23 Jan 2018 15:12:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_NONE=-0.0001, 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 Z6nzb5ltfacW for <bier@ietfa.amsl.com>; Tue, 23 Jan 2018 15:12:13 -0800 (PST)
Received: from mail-ot0-x22d.google.com (mail-ot0-x22d.google.com [IPv6:2607:f8b0:4003:c0f::22d]) (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 EB7FD124205 for <bier@ietf.org>; Tue, 23 Jan 2018 15:12:12 -0800 (PST)
Received: by mail-ot0-x22d.google.com with SMTP id 44so1981201otk.8 for <bier@ietf.org>; Tue, 23 Jan 2018 15:12:12 -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=Jw+nlRALACg5iR7D2tZgyv6MOjRHLlsNxYEx7gDLk6U=; b=TTLn3MBDsmku2aqlB8fsGqAOrX2sXycN+3Yv74zotuwUDTPpGq8XhDlyypPhgQ/Pv4 NpkfBsMiKJ4sCyIufswdAoy6z7VZmQQ3uz4WPNkVZ9EZLiYCy1PDhsR6YbAcwnx0pI96 Vu3k6IMrqmT59xSv8EbgOB0XM3r8CpoXKbghj4HqUF7VZ4E2+2/UYH+MZ5t/4JXMnKxJ usnYLFZGrMENe4g3DH1MInruDOtyPrwC4+aDlTothXqEgBeFrl2ivJ494ZC0n34BVXvI QvVCqFpiEqDLofpEQHVrXDnMLRdSAWc6iywGJGZ1OKGwydpMuRfX+QfgfhbwPLfqjStW JyjQ==
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=Jw+nlRALACg5iR7D2tZgyv6MOjRHLlsNxYEx7gDLk6U=; b=dtq1Neqg/AQ8NhSufVamQM+1I5heBuyH1IDzTlLu05xb7EWAqTcomn7PbC9SaXPTyA EoTo4cmSZs41l1SSy6ZHfkJRwcUAJ44eF30rQdylhpSB6wz1i/vxAmKSQ4UvK9hfCZL5 Em64o4qUwm+C9SOA0O/yIMWeTN3H7aarNWTq61AGc4V//NWhYjXAWZ9s9OYM9uCISyFu L6aK9+8AOlgH5fxatyHuidQiJQis/24fXjftHuP5onDXztOIp12lJdV/w1WWIIx1u8t2 JWf1s/9yr4AJQuZbVwgEtLEFFBD/f/sYA/8UTnB8nHk9DwzYWE6ma6RaZV9J+cAaVpB/ yUjQ==
X-Gm-Message-State: AKwxytdEcXGed/+EJbRZzdGlD7iJDizs7vrBP+YyfiltYSHfufJ36nH4 6bi+BkFVIubAYIu2YzgDfGRK1/HhsVvp0HJJCoXQrgv2
X-Google-Smtp-Source: AH8x225gBoM8YV0IN1xy0rVwExX+jt3j0CGnTpZk/nneQSOTOV2dnWx3AoRxQIBsRCjtM5oWT61wEwblyiEvAk7QrBk=
X-Received: by 10.157.17.98 with SMTP id p31mr1216579otp.362.1516749131945; Tue, 23 Jan 2018 15:12:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.21.103 with HTTP; Tue, 23 Jan 2018 15:12:11 -0800 (PST)
From: Alia Atlas <akatlas@gmail.com>
Date: Tue, 23 Jan 2018 18:12:11 -0500
Message-ID: <CAG4d1rdCysU+qnb=9U9iaZ+UefudWYDmz=mNPSfhDPuWNQQHVw@mail.gmail.com>
To: bier@ietf.org
Content-Type: multipart/alternative; boundary="001a113e15d6391a44056379adbb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/tucoF8RgzE2B6p_A8SKJmJ2PxAE>
Subject: [Bier] BIER rechartering
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: Tue, 23 Jan 2018 23:12:15 -0000
As discussed, I have been working with Tony and Greg on the planned rechartering for the BIER WG. You can find this version at: https://datatracker.ietf.org/doc/charter-ietf-bier/. Please send comments. I want this to make the February 8 IESG telechat. ================================ 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 partially deployed and still provide useful functionality. 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, if needed, MIB modules 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. Such functionality may focus on assuming software or slow-path support first. 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. ================================= Thanks, Alia
- [Bier] BIER rechartering Alia Atlas
- Re: [Bier] BIER rechartering Dolganow, Andrew (Nokia - SG/Singapore)
- Re: [Bier] BIER rechartering Tony Przygienda
- [Bier] 回复: BIER rechartering 徐小虎(义先)
- Re: [Bier] 回复: BIER rechartering Tony Przygienda
- [Bier] 回复: 回复: BIER rechartering 徐小虎(义先)
- Re: [Bier] 回复: BIER rechartering Tony Przygienda
- Re: [Bier] 回复: BIER rechartering Tony Przygienda
- Re: [Bier] BIER rechartering Dolganow, Andrew (Nokia - SG/Singapore)
- Re: [Bier] BIER rechartering Jeff Tantsura
- Re: [Bier] BIER rechartering Tony Przygienda
- Re: [Bier] BIER rechartering Dolganow, Andrew (Nokia - SG/Singapore)
- Re: [Bier] BIER rechartering Xiejingrong
- Re: [Bier] BIER rechartering Xiejingrong
- Re: [Bier] BIER rechartering Xiejingrong
- Re: [Bier] BIER rechartering Dolganow, Andrew (Nokia - SG/Singapore)
- Re: [Bier] BIER rechartering Xiejingrong
- Re: [Bier] BIER rechartering Alia Atlas
- Re: [Bier] BIER rechartering Dolganow, Andrew (Nokia - SG/Singapore)
- Re: [Bier] BIER rechartering Tony Przygienda
- Re: [Bier] BIER rechartering Xiejingrong
- Re: [Bier] BIER rechartering Xiejingrong
- Re: [Bier] BIER rechartering Purkayastha, Debashish
- Re: [Bier] BIER rechartering Alia Atlas