Skip to main content

Early Review of draft-ietf-bess-evpn-irb-extended-mobility-10

Request Review of draft-ietf-bess-evpn-irb-extended-mobility-10
Requested revision 10 (document currently at 17)
Type Early Review
Team Routing Area Directorate (rtgdir)
Deadline 2023-07-14
Requested 2023-06-30
Requested by Stephane Litkowski
Authors Neeraj Malhotra , Ali Sajassi , Aparna Pattekar , Jorge Rabadan , Avinash Reddy Lingala , John Drake
I-D last updated 2023-07-17
Completed reviews Rtgdir Early review of -10 by Donald E. Eastlake 3rd (diff)
Assignment Reviewer Donald E. Eastlake 3rd
State Completed
Request Early review on draft-ietf-bess-evpn-irb-extended-mobility by Routing Area Directorate Assigned
Posted at
Reviewed revision 10 (document currently at 17)
Result Has issues
Completed 2023-07-17
I have been selected to do a routing directorate “early” review of this

This is an early general readiness review of this draft.

For more information about the Routing Directorate, please see

Document: draft-ietf-bess-evpn-irb-extended-mobility-10.txt
Reviewer: Donald Eastlake
Review Date: 2023 July 17
Intended Status: Standards Track


I have some minor concerns about this document that I think should be
resolved before it is submitted to the IESG.


I would rate the readability of the draft as moderate. Hopefully some of my
suggestions below will help.

I believe the technical quality is high and the document takes a reasonable
approach to maintaining appropriate handling of sequence numbers when there
is a mobility event that changes the pairing between MAC and IP addresses
under various circumstances; however, I do have a few questions below.

This document repeatedly says that it may be considered a clarification of
RFC 7432. I believe it is true that the behavior specified in this document
is permitted by RFC 7432 but other behaviors are permitted and perhaps
common. In order to handle the mobility cases covered in this document the
behaviors in the document would have to be implemented or some other
solution adopted. Thus I think the title page header should show this
document as updating RFC 7432 and this should be mentioned in the Abstract
and Introduction.

It seems to me that the last paragraph of Section 7.2 ignores the case
where Mx-IPx with sequence number N movez to Mz-IPx where child IP-MACs
under Mz were currently being advertised with sequence number M where M >
N. The paragraph says the new Mz sequence number must be incremented to N+1
but if M>N I think it must be incremented to M+1. I have suggested changes
to the last two paragraphs of Section 7.2 in the attached.

Drafts should generally be worded so the text will be correct in the final
RFC. So both occurrences of "proposed" in this draft should be replaced by
"specified" or "defined" and occurrences of "draft" in the body text should
be replaced with "document".

Section 2.1 lists subsequent sections as Informative or Normative but omits
Sections 3 and 7. I think Section 3 is Informative. The right category for
Section 7 is a bit unclear but I'm inclined towards normative.

Section 10.2 refers to section 6.1 but there isn't any section 6.1. The
bullet point in Section 10.2 seems essentially incomplete: What "MUST be
higher than the "Mz" sequence number"?

In the last sentence of Section 4.3.1, it is not completely clear what "It"
refers to. Assuming it is the interpretation in the previous sentence, I
suggest "It could be interpreted as" -> "This interpretation could be

"GW devices" occurs only once in this document in Section 2 and GW is never
expanded. I suggest, assuming this is correct, that the phrase be replaced
with "PE devices".

In section 9, since it is not expanded and not listed in the glossary, I
think "EXT-COMM" -> "Extended Community".

Based on the usual order of RFC Sections and the RFC Editor's recommended
table of contents, I think Sections 1 and 2 should be swapped.

The requirements language boilerplate at the beginning of Section 1 needs
to be updated to the latest version also normatively referencing RFC 8174.

The document references RFC 7432 but I think it should reference the
rfc7432bis draft instead.

I am doubtful that there are truly no new security considerations. At a
minimum, I would think the Security Consideration section (section 11)
should refer readers to the Security Considerations sections of [EVPN-IRB]
and rfc7432bis and should state that the methods specified in this document
will increase the consumption of sequence numbers.

RFCs are generally limited to a maximum of five authors. This document
lists six but does say why it needs to list that many. This could be in a
first page note to be deleted before publication.


Abstract: "Procedure to handle host mobility" -> "The procedure to handle
host mobility"

Section 2, first sentence: "EVPN-IRB enables capability ..." -> "EVPN-IRB
enables the capability ...

Section 2: "Purpose of this draft is to define additional ..." => "This
document defines additional ... "

Section 4.3.1: "Complication with this ..." -> "The complication with this

Section 8.8: "This sections is to be treated as optional ..." -> "This
section is optional ..."

Although the above stuck out a bit more to me, there are many other nits
including some spelling typos and a duplicated word, so I went through
marking what I consider to be fixes and these are shown in the attached.

I hope this review is helpful.
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA