Skip to main content

Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks
draft-ietf-nvo3-rfc7348bis-12

Note: This ballot was opened for revision 04 and is now closed.

Gunter Van de Velde
Yes
Christopher Inacio
No Objection
Comment (2026-09-03 for -05) Sent
thanks to Charlie K. for the SECDIR review.

I'm also confused as to why this is informational and not Proposed Standard - is this documenting a standard from another entity / what's already in wide spread use?
Deb Cooley
No Objection
Comment (2026-09-01 for -05) Not sent
Thanks to Charlie Kaufman for their secdir review.
Éric Vyncke
(was Discuss) No Objection
Comment (2026-10-09 for -11) Sent
Thanks for the important work in this document, I simply hope that this widely deployed technology will eventually be a Proposed Standard.

Thanks also for the lengthy discussion to resolve my previous DISCUSS ballot: https://mailarchive.ietf.org/arch/msg/bmwg/KYW_XRJnQawRxK63XOEYgRVWKmU/
Gorry Fairhurst
No Objection
Comment (2026-09-03 for -05) Sent
Thanks for providing this document. I do not see any transport-protocol related concerns and assume that rate/congestion  control and integrity checks are performed as normal for the encapsulated traffic, if that is so, I have no objection to publication of this specification.
Jim Guichard
No Objection
Ketan Talaulikar
(was Discuss) No Objection
Comment (2026-09-16 for -10) Sent
Thanks to the authors and the WG for their work on this document.

Bringing VXLAN base specification on the IETF stream is a step that I 
support wholeheartedly.

Also thanks to Ali for the document updates and responses to address
my concerns and comments from my initial ballot.
Mike Bishop
No Objection
Comment (2026-08-31 for -05) Sent
# IESG review of draft-ietf-nvo3-rfc7348bis-05

CC @MikeBishop

## Comments

### Section 8.1, paragraph 2

Shouldn't this document request IANA to update the Reference, Assignee,
and Contact fields for that registration? For IETF documents, that would
normally point to the RFC and the IETF/IESG.

### Section 8.2, paragraph 5

I agree with Ketan, these seem more like Unassigned than Reserved.

## Nits

All comments below are about very minor potential issues that you may choose to
address in some way - or ignore - as you see fit. Some were flagged by
automated tools (via https://github.com/larseggert/ietf-reviewtool), so there
will likely be some false positives. There is no need to let me know what you
did with these suggestions.

### Grammar/style

#### Section 3.1, paragraph 1
```
mpatible with a Layer 2 model for inter- VM communication. A key characteris
                                  ^^^^^^^^^
```
This word seems to be formatted incorrectly. Consider fixing the spacing or
removing the hyphen completely.

## Notes

This review is in the ["IETF Comments" Markdown format][ICMF]. You can use the
[`ietf-comments` tool][ICT] to automatically convert this review into
individual GitHub issues. Review generated by the [`ietf-reviewtool`][IRT].

[ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md
[ICT]: https://github.com/mnot/ietf-comments
[IRT]: https://github.com/larseggert/ietf-reviewtool
Mohamed Boucadair
(was Discuss) No Objection
Comment (2026-09-17 for -10) Sent
Hi Mallik, Dinesh, Larry, Sridhar, and Ali, 

The changes [1] and clarifications adequately address all points raised in my initial ballot [2]. Thank you for taking care of the review. 

Cheers,
Med

[1] https://author-tools.ietf.org/iddiff?url1=draft-ietf-nvo3-rfc7348bis-05&url2=draft-ietf-nvo3-rfc7348bis-10&difftype=--html

[2] https://mailarchive.ietf.org/arch/msg/nvo3/4f6FVy2I3JhL31n8R-q7rc9elp4/
Roman Danyliw
No Objection
Comment (2026-08-31 for -05) Not sent
Thank you to Peter Yee for the GENART review.

I support the DISCUSS positions of Ketan Talaulikar and Med Boucadair
Tommy Jensen Former IESG member
No Objection
No Objection (2026-09-02 for -05) Not sent
I strongly support Éric's thorough DISCUSS ballot. Additionally, as a minor phrasing point, I wish that PMTUD wasn't used as an alternative to supporting sufficiently high MTU values along the path (this should really be a "do both" situation in my opinion for defense in depth).