Hi, On 08 Nov 2013, at 12:52, Greg White <[email protected]> wrote: > 1) Yes, CableLabs has settled on a formal specification. It can be found > in Annex M of > http://www.cablelabs.com/specifications/CM-SP-MULPIv3.1-I01-131029.pdf > > 2) see above.
great, thanks Greg! > 3) Probably not directly. We have requested that Cisco update the PIE I-D > to include the updates to the core PIE algorithm made as part of the > CableLabs evaluation. CableLabs will draft an I-D to cover the remaining > gaps between that and what can be found in 1. I think this achieves what > you are after. Let me know if not. That sounds like pretty good plan. One remaining question is what will happen if the AQM WG - after adopting the PIE contribution - makes modifications. Is CableLabs prepared to update their specs based on whet we'll do, referring to an eventual IETF RFC rather than maintaining a separate spec? Or will CableLabs also continue work on the spec and we may end up with eventual divergence? (Or will the CableLabs spec of PIE remain frozen at its current version?) Having asked that, I want to make clear that the working relationship with CableLabs has been good, and it's not that I'm expecting problems here. It's after all - at least at the moment - the same people working on PIE here and there. It's just that I've been involved in cases in the IETF before where things fell through the cracks when two SDOs simultaneously worked on something, and it's messy to create alignment after that has happened. So an explicit agreement about how this will go forward would be good to have. Thanks, Lars
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ aqm mailing list [email protected] https://www.ietf.org/mailman/listinfo/aqm
