Skip to main content

Last Call Review of draft-ietf-dime-congestion-flow-attributes-01
review-ietf-dime-congestion-flow-attributes-01-opsdir-lc-dunbar-2015-06-08-00

Request Review of draft-ietf-dime-congestion-flow-attributes
Requested revision No specific revision (document currently at 02)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2015-06-01
Requested 2015-05-24
Authors Lyle Bertz , Serge Manning , Brent Hirschman
Draft last updated 2015-06-08
Completed reviews Genart Last Call review of -01 by Brian E. Carpenter (diff)
Genart Telechat review of -01 by Brian E. Carpenter (diff)
Secdir Last Call review of -01 by Tero Kivinen (diff)
Opsdir Last Call review of -01 by Linda Dunbar (diff)
Assignment Reviewer Linda Dunbar
State Completed
Review review-ietf-dime-congestion-flow-attributes-01-opsdir-lc-dunbar-2015-06-08
Reviewed revision 01 (document currently at 02)
Result Has Issues
Completed 2015-06-08
review-ietf-dime-congestion-flow-attributes-01-opsdir-lc-dunbar-2015-06-08-00

I have reviewed this document as part of the Operational directorate's ongoing
effort to review all IETF documents being processed by the IESG.
 These comments were written primarily for the benefit of the operational area
 directors. Document editors and WG chairs should treat these comments just
 like any other last call comments.



I have some questions for the proposed AVPs by this document.

-



The ECN is marked on packets by network nodes in the middle. Is it the Receiver
of ECN marked data packets sending the proposed AVPs to the Diameter Server?

-



If no ECN marked data packets are received, does it mean the receiver won’t
send the AVPs being proposed by the draft?

-



Diameter is the protocol for Authentication, Authorization, and Accounting.  Is
it the “originator” sending the AAA request? If yes, the “Originator” may not
 even have any ECN marked packets, how does the flow “Originator” constructed
 the proposed AVPs?



Thank you.



Linda Dunbar