Re: [Bier] [IANA #1359191] expert review for draft-ietf-bier-tether
Christian Hopps <chopps@chopps.org> Wed, 06 March 2024 15:12 UTC
Return-Path: <chopps@chopps.org>
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 E6AA5C14F614 for <bier@ietfa.amsl.com>; Wed, 6 Mar 2024 07:12:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.894
X-Spam-Level:
X-Spam-Status: No, score=-6.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4OYbxAuRFJ_G for <bier@ietfa.amsl.com>; Wed, 6 Mar 2024 07:12:25 -0800 (PST)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 31EF5C14F60A for <bier@ietf.org>; Wed, 6 Mar 2024 07:12:25 -0800 (PST)
Received: from smtpclient.apple (172-222-091-149.res.spectrum.com [172.222.91.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 598B97D0FC; Wed, 6 Mar 2024 15:12:24 +0000 (UTC)
From: Christian Hopps <chopps@chopps.org>
Message-Id: <75DA7BF9-90F8-4196-B50A-3343CD935873@chopps.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3D3DA558-7198-4F64-9D3C-41AA3FBC66F9"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
Date: Wed, 06 Mar 2024 10:12:13 -0500
In-Reply-To: <IA1PR05MB95503DE504EB4472741FB0A6D4212@IA1PR05MB9550.namprd05.prod.outlook.com>
Cc: Christian Hopps <chopps@chopps.org>, "hannes@rtbrick.com" <hannes@rtbrick.com>, "hannes@gredler.at" <hannes@gredler.at>, "ginsberg@cisco.com" <ginsberg@cisco.com>, "bier@ietf.org" <bier@ietf.org>
To: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
References: <RT-Ticket-1359191@icann.org> <rt-5.0.3-1720372-1708044294-560.1359191-9-0@icann.org> <rt-5.0.3-106716-1708118812-495.1359191-9-0@icann.org> <CAFVe_epHGT4DdJXW5h019Z2a+Pp-MGJDuntniKK9fpHUUoMJmg@mail.gmail.com> <rt-5.0.3-286074-1708254634-1843.1359191-9-0@icann.org> <rt-5.0.3-1273884-1708972994-366.1359191-9-0@icann.org> <rt-5.0.3-585803-1709664380-1531.1359191-9-0@icann.org> <m2il1zzlt3.fsf@ja.int.chopps.org> <IA1PR05MB95503DE504EB4472741FB0A6D4212@IA1PR05MB9550.namprd05.prod.outlook.com>
X-Mailer: Apple Mail (2.3774.400.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/m1O6CxuwSJkO8X-49EqJyuWnyDk>
Subject: Re: [Bier] [IANA #1359191] expert review for draft-ietf-bier-tether
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 06 Mar 2024 15:12:29 -0000
I wasn't talking about BFR1. BFRx is a router, it's forwarding traffic to BFR[2-N] (over tunnel interfaces but the routing protocol doesn't care about this) why do you need anything more than that? I see no need for this extra technology. You simply make BFRx and it's tunnels part of the normal routing domain and let traffic flow from BFR1->X->BFRx->BFR[2-n] as you are trying to achieve, but without any new tech, just routing protocols and metrics. Thanks, Chris. > On Mar 6, 2024, at 08:37, Jeffrey (Zhaohui) Zhang <zzhang@juniper.net> wrote: > > [- IANA] > > Hi Chris, > > The benefit of tethering is explained in Section 1. Specifically, in Figure 2: > > ------ BFR2 ------- BFER2 > / > BFER1 --- BFR1 ---- X ------- BFR3 ------- BFER3 > / \ ......... > / \ > BFRx ------ BFRn ------- BFERn > > W/o using tethering, BFR1 needs to tunnel multiple copies to BFR2/3/…/n individually, which may not be desired if the BFR1—X link is bandwidth-limited. > W/ BFRx being a helper tethered to X, BFR1 only tunnels one copy to BFRx. The link between BFRx and X could be a fat local pipe and it’s much better for BFRx to tunnel individual copies to BFR2/3/…/n. > > BFRx is a normal router but it may not be in the normal path from BFR1 and BFR2/3/…/n so the tethering procedure is needed. > You can also view it as a form of TI-LFA: BFR1 tunnels packets to BFRx (as if X went down) that is not in the normal path who will then send to the final destinations. > > Thanks. > Jeffrey > > -----Original Message----- > From: BIER <bier-bounces@ietf.org <mailto:bier-bounces@ietf.org>> On Behalf Of Christian Hopps > Sent: Wednesday, March 6, 2024 5:33 AM > To: drafts-expert-review-comment@iana.org <mailto:drafts-expert-review-comment@iana.org> > Cc: chopps@chopps.org <mailto:chopps@chopps.org>; hannes@rtbrick.com <mailto:hannes@rtbrick.com>; hannes@gredler.at <mailto:hannes@gredler.at>; ginsberg@cisco.com <mailto:ginsberg@cisco.com>; bier@ietf.org <mailto:bier@ietf.org> > Subject: Re: [Bier] [IANA #1359191] expert review for draft-ietf-bier-tether > > [External Email. Be cautious of content] > > > Allocating the code-point should not destabilize IS-IS itself so it's OK as far as that goes. > > As an aside though, given a light read-through the draft's technology seems pretty questionable to me. A lot of complexity has been built here to place a router outside of the normal routing process and I don't understand why. This "helper" *router* could just be a normal BIER router in the domain and none of any of this would seem to be needed then. > > Thanks, > Chris. > > > > "David Dong via RT" <drafts-expert-review-comment@iana.org <mailto:drafts-expert-review-comment@iana.org>> writes: > > > Dear Chris Hopps and Les Ginsberg (cc: bier WG), > > > > As the designated experts for the Sub-sub-TLVs for BIER Info Sub-TLV > > registry, can you review the proposed registration in draft-ietf-bier-tether-05 for us? > > Hannes has already approved this registration. Please see: > > > > https://datatracker.ietf.org/doc/draft-ietf-bier-tether/ > > > > The due date assigned was March 1st. > > > > If this is OK, when the IESG approves the document for publication, we'll make the registration at: > > > > https://www.iana.org/assignments/isis-tlv-codepoints/ > > > > We will act after all the experts have approved this registration, unless you tell us otherwise. > > > > With thanks, > > > > David Dong > > IANA Services Sr. Specialist > > > > On Mon Feb 26 18:43:14 2024, david.dong wrote: > >> Dear Chris Hopps and Les Ginsberg (cc: bier WG), > >> > >> As the designated experts for the Sub-sub-TLVs for BIER Info Sub-TLV > >> registry, can you review the proposed registration in > >> draft-ietf-bier- > >> tether-05 for us? Hannes has already approved this registration. > >> Please see: > >> > >> https://datatracker.ietf.org/doc/draft-ietf-bier-tether/ > >> > >> The due date is March 1st. > >> > >> If this is OK, when the IESG approves the document for publication, > >> we'll make the registration at: > >> > >> https://www.iana.org/assignments/isis-tlv-codepoints/ > >> > >> We will act after all the experts have approved this registration, > >> unless you tell us otherwise. > >> > >> With thanks, > >> > >> David Dong > >> IANA Services Sr. Specialist > >> > >> On Sun Feb 18 11:10:34 2024, hannes@rtbrick.com <mailto:hannes@rtbrick.com> wrote: > >> > Hi David, > >> > > >> > No concerns from my side to make the allocation. > >> > > >> > thanks, > >> > > >> > /hannes > >> > > >> > On Fri, Feb 16, 2024 at 10:26 PM David Dong via RT < > >> > drafts-expert-review-comment@iana.org <mailto:drafts-expert-review-comment@iana.org>> wrote: > >> > > >> > > Dear Chris Hopps, Hannes Gredler, Les Ginsberg (cc: bier WG), > >> > > > >> > > As the designated experts for the Sub-sub-TLVs for BIER Info Sub- > >> > > TLV registry, can you review the proposed registration in > >> > > draft-ietf-bier-tether-05 for us? Please see > >> > > > >> > > https://datatracker.ietf.org/doc/draft-ietf-bier-tether/ > >> > > > >> > > The due date is March 1st. > >> > > > >> > > If this is OK, when the IESG approves the document for > >> > > publication, we'll make the registration at: > >> > > > >> > > https://www.iana.org/assignments/isis-tlv-codepoints/ > >> > > > >> > > We will act after all the experts have approved this > >> > > registration, unless you tell us otherwise. > >> > > > >> > > With thanks, > >> > > > >> > > David Dong > >> > > IANA Services Sr. Specialist > >> > > > >> > > > > Juniper Business Use Only
- [Bier] [IANA #1359191] expert review for draft-ie… David Dong via RT
- Re: [Bier] [IANA #1359191] expert review for draf… Hannes Gredler
- [Bier] [IANA #1359191] expert review for draft-ie… David Dong via RT
- [Bier] [IANA #1359191] expert review for draft-ie… David Dong via RT
- Re: [Bier] [IANA #1359191] expert review for draf… Christian Hopps
- Re: [Bier] [IANA #1359191] expert review for draf… Jeffrey (Zhaohui) Zhang
- Re: [Bier] [IANA #1359191] expert review for draf… Christian Hopps
- Re: [Bier] [IANA #1359191] expert review for draf… Jeffrey (Zhaohui) Zhang
- [Bier] [IANA #1359191] expert review for draft-ie… David Dong via RT
- [Bier] [IANA #1359191] expert review for draft-ie… David Dong via RT
- [Bier] [IANA #1359191] expert review for draft-ie… David Dong via RT
- [Bier] [IANA #1359191] expert review for draft-ie… David Dong via RT
- Re: [Bier] [IANA #1359191] expert review for draf… Les Ginsberg (ginsberg)
- Re: [Bier] [IANA #1359191] expert review for draf… Les Ginsberg (ginsberg)
- Re: [Bier] [IANA #1359191] expert review for draf… Jeffrey (Zhaohui) Zhang