Re: [OPSAWG] Call for adoption, draft-krishnan-opsawg-large-flow-load-balancing/

Below are comments from Pete (as an individual) and responses below.

Agreed Pete - will do.

Thanks,
Ramki

-----Original Message-----
From: Pete Moyer 
Sent: Thursday, April 11, 2013 7:08 PM
To: ramki Krishnan
Subject: RE: [OPSAWG] Call for adoption, draft-krishnan-opsawg-large-flow-load-balancing/

Cool. One last comment -

>>Did you mean "....is required to allow the import of large flow information from the router."?
No, in this case, the large flow recognition (detection) is handled in a external management station. The detected large flows need to be imported to the router for re-balancing purposes.

OK, I missed that but now I read it correctly. Perhaps you might say "export" (aka: push) to the router rather than "import" (aka: pull) to the router. That will also avoid confusion I think.

Thanks.

-----Original Message-----
From: ramki Krishnan 
Sent: Thursday, April 11, 2013 12:12 PM
To: Pete Moyer; Sanjay Khanna; Gary Seebaum; Norival Figueira
Subject: RE: [OPSAWG] Call for adoption, draft-krishnan-opsawg-large-flow-load-balancing/

Hi Pete,

Thanks a lot. For some of the questions, I will cc the opsawg mailing list. The chairs love to see activity in the mailing list.

>>Section 3, Step 2) The egress component links are periodically scanned for link
   utilization. If the egress component link utilization exceeds a pre-
   programmed threshold, an operator alert is generated. The large flows
   mapped to the congested egress component link are exported to a
   central management entity.

>>Did you mean "Information about the large flows mapped to the congested egress component link are exported to a central management entity."
Yes, thanks for catching this.

>>Section 4.2) In cases where large flow recognition is handled by an external
   management station (see Section 3.1.3), an information model for
   flows is required to allow the import of large flow information to
   the router.

>>Did you mean "....is required to allow the import of large flow information from the router."?
No, in this case, the large flow recognition (detection) is handled in a external management station. The detected large flows need to be imported to the router for re-balancing purposes.

>> Also, have you considered any OpenFlow/SDN use case for re-balancing the flows?
Certainly. I have not explicitly mentioned OpenFlow since it is not advocated by IETF.

Regarding SDN, it is covered in section 4.2 " In cases where large flow recognition is handled by an external  management station (see Section 3.1.3), an information model for flows is required to allow the import of large flow information to  the router....". The SDN application would be an sFlow collector performing the large flow recognition.

Thanks,
Ramki

-----Original Message-----
From: Pete Moyer 
Sent: Thursday, April 11, 2013 11:45 AM
To: ramki Krishnan; Sanjay Khanna; Gary Seebaum; Norival Figueira
Subject: RE: [OPSAWG] Call for adoption, draft-krishnan-opsawg-large-flow-load-balancing/

I will do that. I do have a few comments:

Section 3, Step 2) The egress component links are periodically scanned for link
   utilization. If the egress component link utilization exceeds a pre-
   programmed threshold, an operator alert is generated. The large flows
   mapped to the congested egress component link are exported to a
   central management entity.

Did you mean "Information about the large flows mapped to the congested egress component link are exported to a central management entity."

Section 4.2) In cases where large flow recognition is handled by an external
   management station (see Section 3.1.3), an information model for
   flows is required to allow the import of large flow information to
   the router.

Did you mean "....is required to allow the import of large flow information from the router."?

Also, have you considered any OpenFlow/SDN use case for re-balancing the flows? 

Thanks.

-----Original Message-----
From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf Of Melinda Shore
Sent: Wednesday, April 10, 2013 6:16 AM
To: opsawg@ietf.org
Subject: [OPSAWG] Call for adoption, draft-krishnan-opsawg-large-flow-load-balancing/

This is a call for working group adoption of http://datatracker.ietf.org/doc/draft-krishnan-opsawg-large-flow-load-balancing/.

The authors report that they've incorporated feedback given at the IETF 86 meeting, in particular
  . information model for flow rebalancing
  . operational considerations

We'll be assessing consensus on 24 April 2013.

Thanks,

Melinda
_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg