Skip to main content

Early Review of draft-ietf-teas-5g-ns-ip-mpls-02
review-ietf-teas-5g-ns-ip-mpls-02-tsvart-early-nishida-2024-01-07-00

Request Review of draft-ietf-teas-5g-ns-ip-mpls
Requested revision No specific revision (document currently at 04)
Type Early Review
Team Transport Area Review Team (tsvart)
Deadline 2024-01-08
Requested 2023-12-11
Requested by Oscar Gonzalez de Dios
Authors Krzysztof Grzegorz Szarkowicz , Richard Roberts , Julian Lucek , Mohamed Boucadair , Luis M. Contreras
I-D last updated 2024-01-07
Completed reviews Rtgdir Early review of -02 by Alvaro Retana (diff)
Tsvart Early review of -02 by Yoshifumi Nishida (diff)
Intdir Early review of -02 by Timothy Winters (diff)
Comments
We are interested in identifying any area-specific issues.
Assignment Reviewer Yoshifumi Nishida
State Completed
Request Early review on draft-ietf-teas-5g-ns-ip-mpls by Transport Area Review Team Assigned
Posted at https://mailarchive.ietf.org/arch/msg/tsv-art/NMRlf8El_VnKy2ZDvm9MMbQLwec
Reviewed revision 02 (document currently at 04)
Result Almost ready
Completed 2024-01-07
review-ietf-teas-5g-ns-ip-mpls-02-tsvart-early-nishida-2024-01-07-00
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@ietf.org if you reply to or forward this review.

Summary: I don't think there is any transport protocol related issues in
this document. I think this document is almost ready for publication as an
informational RFC, but it might be good to consider the following points.

This is a fairly long document that contains various information. I think
it would be good if it describes which people should read it as well as
how to utilize the information in the doc in the introduction. Also, it
seems that some information described in the doc is not strongly related
to others. Do we expect that the readers of the doc should read entire
document or only part of it based on their interests? In the latter case,
I think it would be good to describe who should read which sections.

Nits:
  Section 7.1
     what is transport controller? I think the term and its role should be
     explained more clearly.

--
Yoshi