[Last-Call] Re: Genart last call review of draft-ietf-bier-frr-06

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks Mike.  That works for me.
Yours,
Joel



Sent via the Samsung Galaxy S20 FE 5G, an AT&T 5G smartphone


-------- Original message --------
From: Michael McBride <michael.mcbride@xxxxxxxxxxxxx>
Date: 2/24/25 6:36 PM (GMT-05:00)
To: Joel Halpern <jmh@xxxxxxxxxxxxxxx>, gen-art@xxxxxxxx
Cc: bier@xxxxxxxx, draft-ietf-bier-frr.all@xxxxxxxx, last-call@xxxxxxxx
Subject: RE: Genart last call review of draft-ietf-bier-frr-06

Hi again Joel,

This is what I wound up doing (MM):

  >  Section 4 (Representations for BIER-FRR Forwarding Data) begins:
"To minimize the occurrence of redundant packets, it is essential that backup entries are prioritized for use within the single extended BIFT, as described in Section 3.2)."
    However, section 3.2 does not discuss prioritizing anything nor duplicate
    avoidance.  I presume this should reference some other section of the
    document? (Some of the relevant text is in section 4.1.)

MM: Extended BIFTs are described in several areas so I wound up just dropping the "as described in Section 3.2)."

    Section 5.3 (Example, in Protection Levels) seems to be showing various
    backup paths.  I found myself confused when the text says that the backup
    path to provide node protection for B5 (presumably, for the case where B5
    is thought to have failed) ends with -B5?

MM: To make it more clear that it's protecting B5 from a B6 node failure I changed the sentence to "Protecting BFER B5 from a BFR-NBR B6 node
   failure can only be provided through the backup path B1-B2-B3-B4-B5." This matches Figure 8.

Thanks again.
mike
-- 
last-call mailing list -- last-call@xxxxxxxx
To unsubscribe send an email to last-call-leave@xxxxxxxx

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux