[Last-Call] Opsdir last call review of draft-ietf-cellar-ffv1-17

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Reviewer: Qin Wu
Review result: Ready

I have reviewed this document on behalf of the Operations and Management
Directorate. Four questions  need to be clarified: 1. why document v0,v1,v3 in
draft-ietf-cellar-ffv1 as informational and document v4 in
draft-ietf-cellar-ffv1-v4-14 as standard track? Not clear the key difference
between v04 and all other previous versions? 2. Why not specify transport, is
container sto which the ffv1 is mapped equivalent to transport? without
transport, how to provide confidentiality, integrity, and source authenticity?
3. how error_status and crc parity are used? e.g., using crc parity detect
error? can error be repaired? how? 4. Is bitstream parameters such as version,
micor-version,num_h_slices,num_v_slices sensitity information that can
disclosed? any security risk?


-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux