[Bier] overdue text on BEIR TE

Lou Berger <lberger@labn.net> Tue, 14 April 2020 13:02 UTC

Return-Path: <lberger@labn.net>
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 12EB43A0DF8 for <bier@ietfa.amsl.com>; Tue, 14 Apr 2020 06:02:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 HCsicjdflFZY for <bier@ietfa.amsl.com>; Tue, 14 Apr 2020 06:02:31 -0700 (PDT)
Received: from gproxy4-pub.mail.unifiedlayer.com (gproxy4-pub.mail.unifiedlayer.com [69.89.23.142]) (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 4BCE03A0DF7 for <bier@ietf.org>; Tue, 14 Apr 2020 06:02:31 -0700 (PDT)
Received: from cmgw12.unifiedlayer.com (unknown [10.9.0.12]) by gproxy4.mail.unifiedlayer.com (Postfix) with ESMTP id BBA96178131 for <bier@ietf.org>; Tue, 14 Apr 2020 06:46:48 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id OKxkjhEFUN8ArOKxkjiliM; Tue, 14 Apr 2020 06:46:48 -0600
X-Authority-Reason: nr=8
X-Authority-Analysis: v=2.3 cv=PpW9kTE3 c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=xqWC_Br6kY4A:10:nop_ipv6 a=IkcTkHD0fZMA:10:nop_charset_1 a=cl8xLZFz6L8A:10:nop_rcvd_month_year a=Vy_oeq2dmq0A:10:endurance_base64_authed_username_1 a=48vgC7mUAAAA:8 a=YRQhCe0djwIYlrBpC1gA:9 a=QEXdDO2ut3YA:10:nop_charset_2 a=w1C3t2QeGrPiZgrLijVG:22 a=pHzHmUro8NiASowvMSCR:22 a=nt3jZW36AmriUCFCBwmW:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Date: Message-ID:To:Subject:From:Sender:Reply-To:Cc:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=mqzNYgRx8i99iTH7z9NOluF7D4RT/N9bvG3Tc1oVWsQ=; b=kUptwCqon7cRXZRI/JiBCnBBhc IMXuVQ1k2NhYky/V0msFfbM3GiDNt3uOf/Ctw4IEO8OeK/hMltxL/m+F+f6jrqhLN5c/smjjDT3Eu ZjVpvDUjAH75QfJVGNbK4Qczx;
Received: from [127.0.0.1] (port=54153 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <lberger@labn.net>) id 1jOKxk-004M1l-Gp for bier@ietf.org; Tue, 14 Apr 2020 06:46:48 -0600
From: Lou Berger <lberger@labn.net>
To: BIER WG <bier@ietf.org>
Message-ID: <744d9749-69c0-0280-3533-9716ea8332fb@labn.net>
Date: Tue, 14 Apr 2020 08:46:43 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 127.0.0.1
X-Source-L: Yes
X-Exim-ID: 1jOKxk-004M1l-Gp
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: ([IPv6:::1]) [127.0.0.1]:54153
X-Source-Auth: lberger@labn.net
X-Email-Count: 1
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/KIA6B8X0jLojWbClIqH8n-eoBPM>
Subject: [Bier] overdue text on BEIR TE
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: Tue, 14 Apr 2020 13:02:33 -0000

Hi,

This is a bit overdue - but I somehow imagine that many will understand 
life hasn't been happening in a normal way recently.

I suggest the text enclosed below be incorporated into the BEIR TE 
draft, perhaps at the end of section 2 or a new section 3. Please excuse 
any typos, and I'm sure it will need some tweaking to best align with 
BIER terminology.

Lou

PS I'm triple booked during today's interim, but still hope to be there.

---------------------------------------------------

2.5. Traffic Engineering Considerations

Traffic Engineering [RFC3272-Bis] provides performance optimization of 
operational IP networks while utilizing network resources economically 
and reliably.  The key elements needed to effect TE are policy, path 
steering and resource management. These elements require support at the 
control/controller level and within the forwarding plane.

Policy decisions are made within the BIER-TE control plane, i.e., within 
BIER-TE Controllers.  Controllers use policy when composing BitStrings 
(BFR flow state) and BFR BIFT state. The mapping of user/IP traffic to 
specific BitStrings/BEIR-TE flows is made based on policy. The specifics 
details of BIER-TE policies and how a controller uses such are out of 
scope of this document.

Path steering is supported  via the definition of a BitString. 
BitStrings used in BIER-TE are composed based on policy and resource 
management considerations.  When composing BIER-TE BitStrings, a 
Controller MUST take into account the resources available at each BFR 
and for each BP.  Resource availability is typically provided 
dynamically via routing protocol information, but may also be obtained 
via the BIER-TE control protocol.  The resource usage of an individual 
BP can be tracked on a Controller based on its local accounting and via 
routing or the BIER-TE control protocol. This implies that such 
information be collected by each BFR.

Resource management also has implications on the BFR forwarding plane.  
BIER-TE supporting BFRs  MAY support per BIFT entry resources and 
resource allocation. Example resources include buffers, policing and 
rate-shaping mechanisms which are typically supported via queuing.  This 
level of resource control, while optional, is important in networks that 
wish to support congestion management policies to control or regulate 
the offered traffic to deliver different levels of service and alleviate 
congestion problems, or those networks that wish to control latencies 
experienced by specific traffic flows.

[RFC3272-Bis] https://tools.ietf.org/html/draft-dt-teas-rfc3272bis