Hi Wes, Thanks for the feedback. I have entered the issues in the tracker [1] and will start processing them. [1] https://github.com/ietf-wg-avtcore/draft-ietf-avtcore-rtp-j2k-scl/issues Best, -- Pierre On Fri, May 16, 2025 at 3:22 PM Wes Hardaker via Datatracker <noreply@xxxxxxxx> wrote: > > Document: draft-ietf-avtcore-rtp-j2k-scl > Title: RTP Payload Format for sub-codestream latency JPEG 2000 streaming > Reviewer: Wes Hardaker > Review result: Has Nits > > I have reviewed this document as part of the security directorate's ongoing > effort to review all IETF documents being processed by the IESG. These comments > were written primarily for the benefit of the security area directors. Document > editors and WG chairs should treat these comments just like any other last call > comments. > > The summary of the review is: ready with a few minor comments/nits > > Version reviewed: -05 > > Overall: the document is extremely well written with less typos than I've > generally seen in most documents (especially my own). Well done! > > Comments: > > - I'm less familiar with the anima work, but generally there are a lot of > acronyms that don't get an early spell-out-expansion (eg: PLM, PLT, ORDH, ORDB, > POS, PID, SOC, EOC, etc). But maybe this is normal for anima documents? > > - The biggest of the security related things I've wondered is what happens if > things like MUSTs are not followed. For example, if the timestamp frames do > not advance at required regular intervals, what does the client get and can > that be used to mess with their results in some way? What happens if the ESEQ > * 65536 + sequence number wraps around an int32 or int64? > > - What happens to a client if the jpeg2000-scl type is sent with parameters of > width=HUGE, height=HUGE? Is 2^32 bits really needed? What happens if a client > ties to pre-allocate memory based on receiving this sizing requirements? > > - the smallest of nits ever I think: in appendix A, the table order is NAME > SAMP COMPS ... but the description order is NAME COMPS SAMP ... > > > -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
