Reviewer: Joerg Ott Review result: Ready This document has been reviewed as part of the transport area review team's ongoing effort to review key IETF documents. These comments were written primarily for the transport area directors, but are copied to the document's authors and WG to allow them to address any issues raised and also to the IETF discussion list for information. When done at the time of IETF Last Call, the authors should consider this review as part of the last-call comments they receive. Please always CC tsv-art@xxxxxxxx if you reply to or forward this review. The document defines the transmission and reception behaviour as well as the configuration information for encapsulating DetNet MPLS packets over UDP. The draft provides an explicit applicability statement concerning carrying non-congestion controlled traffic. With the latter in mind, the document seems to be complete. (Fragmentation and reassembly seem to be already covered with MPLS-over-UDP in RFC7510 and RFC4023) One quick question to the authors: Section 5 provides the necessary information to be configured for flow mapping and makes reference to IP source and destination addresses. Is the presence of network (and port) address translation devices/functions covered elsewhere in the many specs to ensure proper transmission at a sender and proper reverse mapping at a receiver? It would be up to the control plane to determine the appropriate addresses. Does this need explicit mentioning? Best, Jörg -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
