draft-ietf-opsawg-large-flow-load-balancing-08.txt   draft-ietf-opsawg-large-flow-load-balancing-09.txt 
skipping to change at page 1, line 17 skipping to change at page 1, line 17
Dell Dell
Ning So Ning So
Tata Communications Tata Communications
B. Khasnabish B. Khasnabish
ZTE Corporation ZTE Corporation
April 6, 2014 April 6, 2014
Mechanisms for Optimizing LAG/ECMP Component Link Utilization in Mechanisms for Optimizing LAG/ECMP Component Link Utilization in
Networks Networks
draft-ietf-opsawg-large-flow-load-balancing-08.txt draft-ietf-opsawg-large-flow-load-balancing-09.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. This document may not be modified, provisions of BCP 78 and BCP 79. This document may not be modified,
and derivative works of it may not be created, except to publish it and derivative works of it may not be created, except to publish it
as an RFC and to translate it into languages other than English. as an RFC and to translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 19, line 40 skipping to change at page 19, line 40
. For ECMP: The ECMP group and the ECMP Nexthop along with the . For ECMP: The ECMP group and the ECMP Nexthop along with the
relative weight of traffic to be assigned to each ECMP Nexthop relative weight of traffic to be assigned to each ECMP Nexthop
are required. are required.
It is possible to have an ECMP nexthop that itself comprises a LAG. It is possible to have an ECMP nexthop that itself comprises a LAG.
In that case, we would have to specify the new weights for both the In that case, we would have to specify the new weights for both the
ECMP nexthops within the ECMP group as well as the component links ECMP nexthops within the ECMP group as well as the component links
within the LAG. within the LAG.
In the case where an ECMP component link itself comprises a LAG, we
would have to specify new weights for both the component links within
the ECMP group as well as the component links within the LAG.
5.5. Export of Flow Information 5.5. Export of Flow Information
Exporting large flow information is required when large flow Exporting large flow information is required when large flow
recognition is being done on a router, but the decision to rebalance recognition is being done on a router, but the decision to rebalance
is being made in an external management station. Large flow is being made in an external management station. Large flow
information includes flow identification and the component link ID information includes flow identification and the component link ID
that the flow currently is assigned to. Other information such as that the flow currently is assigned to. Other information such as
flow QoS and bandwidth may be exported too. flow QoS and bandwidth may be exported too.
The IPFIX information model [RFC 7012] can be leveraged for large The IPFIX information model [RFC 7012] can be leveraged for large
 End of changes. 2 change blocks. 
1 lines changed or deleted 5 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/