Last Call Review of draft-ietf-pals-ple-08
review-ietf-pals-ple-08-genart-lc-halpern-2024-10-11-00

Request Review of draft-ietf-pals-ple
Requested revision No specific revision (document currently at 13)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2024-10-23
Requested 2024-10-09
Authors Steven Gringeri , Jeremy Whittaker , Nicolai Leymann , Christian Schmutzer , Chris Brown
I-D last updated 2024-10-11
Completed reviews Rtgdir Last Call review of -06 by Tal Mizrahi (diff)
Genart Last Call review of -08 by Joel M. Halpern (diff)
Secdir Last Call review of -08 by Christian Huitema (diff)
Opsdir Last Call review of -10 by Tony Li (diff)
Tsvart Last Call review of -09 by Tommy Pauly (diff)
Secdir Last Call review of -09 by Christian Huitema (diff)
Secdir Telechat review of -12 by Christian Huitema (diff)
Assignment Reviewer Joel M. Halpern
State Completed
Request Last Call review on draft-ietf-pals-ple by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/c8N-P86mokalN32VRKkrczbf5VY
Reviewed revision 08 (document currently at 13)
Result Ready w/nits
Completed 2024-10-11
review-ietf-pals-ple-08-genart-lc-halpern-2024-10-11-00
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-pals-ple-08
Reviewer: Joel Halpern
Review Date: 2024-10-11
IETF LC End Date: 2024-10-23
IESG Telechat date: Not scheduled for a telechat

Summary: This draft is ready for publication as a Proposed Standard

Major issues: N/A

Minor issues: N/A

Nits/editorial comments:
    Section 5.2.1 defining the PLEA Control Word describes two pairs of bits,
    one pair called RSSV and described in the usual way for describing reserved
    bits.  A second pair is called FRG and is described more teresely but
    appears to be simply more reserved bits.   It is unclear why these two
    fields are separated, and why the wording is slightly different between
    them.

    Section 6 desccribes the basic payload and the byte aligned payload.  The
    description makes it look like there are two different forms.  Thinking
    about it, the payload is always in bytes, so the sender will fill bits from
    the source until it has filled the fixed number of bytes.  SO what is the
    difference between 6.1 and 6.2?