Requested revision
| Standard: | IEEE 802.1Q &/or IEEE 802.1AX | Clause: | Appropriate clauses for LinkLAG MIB and TLV |
| Clause title: | Appropriate clauses for LinkLAG MIB and TLV | ||
Rationale for revision
The current IEEE 802.1 standards are silent on how LLDP is to operate over
an aggregated
link. This could lead to incompatible implementations in the marketplace.
- Is there one LLDP session per physical link or one for the
aggregated link? Or are there both?
- Background
- new-pelissier-laglldp-0110.pdf "Notes from LLDP over LAG
concall"
- new-congdon-linkag-LLDP-0110.pdf "Disambiguating LLDP
agents over a Link Aggregation"
- new-lynch-LLDP-over-LAG-0911.pdf "Eliminating the
ambiguity of running LLDP over LAGs"Proposed text
1) Document in IEEE 802.1Q or IEEE 802.1AX the requirements and
operational behavior
for LLDP in the present of Link Aggregation
- Either redefine the use of some of the reserve bits or add new
fields to the
existing LAG TLV (to disambiguate the source & target of LLDP
frames)
2) Identify which TLVs should be sent on each individual link or on the
aggregate
3) Resolve the architectural addressing issues introduced by running LLDP
over a LAG.Impact on existing networks
None known at this time.
See background presentations (above) for potential backwards
compatibility implications.
Originator
| Name: | Jeffrey Lynch | Email: | jjlynch@us.ibm.com |
| Affiliation: | IBM | ||
| Submitted: | 2011-09-08 | ||