Skip to main content

Telechat Review of draft-ietf-bier-te-arch-10
review-ietf-bier-te-arch-10-rtgdir-telechat-robles-2021-08-24-00

Request Review of draft-ietf-bier-te-arch
Requested revision No specific revision (document currently at 13)
Type Telechat Review
Team Routing Area Directorate (rtgdir)
Deadline 2021-08-24
Requested 2021-08-11
Requested by Alvaro Retana
Authors Toerless Eckert , Michael Menth , Gregory Cauchie
I-D last updated 2021-08-24
Completed reviews Rtgdir Last Call review of -10 by Yingzhen Qu (diff)
Tsvart Last Call review of -10 by Tommy Pauly (diff)
Genart Last Call review of -10 by Robert Sparks (diff)
Rtgdir Telechat review of -10 by Ines Robles (diff)
Assignment Reviewer Ines Robles
State Completed
Review review-ietf-bier-te-arch-10-rtgdir-telechat-robles-2021-08-24
Posted at https://mailarchive.ietf.org/arch/msg/rtg-dir/F4okb4_epSqiOQz-bYbwi6JnKw0
Reviewed revision 10 (document currently at 13)
Result Has Nits
Completed 2021-08-24
review-ietf-bier-te-arch-10-rtgdir-telechat-robles-2021-08-24-00
Hello,

I have been selected as the Routing reviewer for this draft. The Routing
Directorate seeks to review all routing or routing-related drafts as they pass
through IETF last call and IESG review, and sometimes on special request. The
purpose of the review is to provide assistance to the Routing ADs. For more
information about the Routing Directorate, please see
‚Äčhttp://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

It would be helpful if you could consider them along with any other IETF Last
Call comments that you receive, and strive to resolve them through discussion
or by updating the draft.

Document: draft-ietf-bier-te-arch-10
Reviewer: Maria Ines Robles
Review Date: 2021-08-24
IETF LC End Date: 2021-08-24
Intended Status: Standards Track

Summary:

This document describes per-packet stateless strict and loose path steered
replication and forwarding for Bit Index Explicit Replication packets
(RFC8279), BIER Tree Engineering (BIER-TE), intended to be used as the path
steering mechanism for Traffic Engineering with BIER. BIER-TE introduces a new
semantic for bit positions (BP) that indicate adjacencies.

This document is basically ready for publication. I have some minor
questions/comments.

Major Issues: No major issues found.

Minor Issues: No minor issues found.

Nits/Comments/Questions:

- Expand SI at first use --> Set Identifier (SI)?
- Expand SD at first use --> Sub Domain (SD)?

Page 7: Question, in the sentence: "...to send in addition to BFR6 via BFR4
also a copy to BFR3, the BitString needs to be (p2,p5,p8,p10,p12,p13)..." --> 
should it be added p15 as well, (p2,p5,p8,p10,p12,p13,P15) ?

Page 7: " many of which are based on assumptions..." --> it would be nice if
you could state examples of the assumptions, which assumptions?

Page 8: "BFR4 and from BFR4 to BFR uses (p1,p2,p3,p4,p6).  -->  BFR4 and from
BFR4 to BFR6 uses (p1,p2,p3,p4,p6).

Page 8: Question, in Figure 2,  You have p6 as forward_routed() to BFR6, and as
local_decap. Is this correct? Is this reuse of bit positions case?


Page 9: "...undesired duplicates or loops as explained further down in the
text."  --> (nice to reference the section where it is explained, Section 5.2)

Page 10: "See for example See Section 5.1.3...." --> delete the second See

Question: Is there specific security considerations when having overlay BIER-TE
topology?

Thank you for this document,

Ines.