ieee 802 plenary, singapore, march, 2011 1 bq-nfinn-axbq-editing-0311-v01.pdf p802.1axbq editing...

6
IEEE 802 plenary, Singapore, March, 2011 1 bq-nfinn-Axbq-editing-0311-v01.pdf P802.1AXbq editing plan Rev. 1 Norman Finn [email protected]

Upload: lillian-cullen

Post on 27-Mar-2015

214 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: IEEE 802 plenary, Singapore, March, 2011 1 bq-nfinn-Axbq-editing-0311-v01.pdf P802.1AXbq editing plan Rev. 1 Norman Finn nfinn@cisco.com

IEEE 802 plenary, Singapore, March, 2011 1bq-nfinn-Axbq-editing-0311-v01.pdf

P802.1AXbq editing plan

Rev. 1

Norman [email protected]

Page 2: IEEE 802 plenary, Singapore, March, 2011 1 bq-nfinn-Axbq-editing-0311-v01.pdf P802.1AXbq editing plan Rev. 1 Norman Finn nfinn@cisco.com

2IEEE 802 plenary, Singapore, March, 2011bq-nfinn-Axbq-editing-0311-v01.pdf

Some decisions made

PAR and Five Criteria are set (modulo a new Internet draft).

We will use Stephen Haddock’s baggy pants model.

DRNI connects only two networks.

We have a large set of desired characteristics, among which are:

•Fast convergence after a failure.

•Capability for bi-directional symmetry of link usage.

•Capability for frame distribution by service.

• Insulation of each connected network from fault events in the other network.

•No restrictions on the operations of the connected networks.

Page 3: IEEE 802 plenary, Singapore, March, 2011 1 bq-nfinn-Axbq-editing-0311-v01.pdf P802.1AXbq editing plan Rev. 1 Norman Finn nfinn@cisco.com

3IEEE 802 plenary, Singapore, March, 2011bq-nfinn-Axbq-editing-0311-v01.pdf

Some decisions to make

Do we signal individual services’ states/needs between Portals, or depend on pre-configured service sets?

•Pro individual: Closer to current practice, easier to describe, easier to create configuration.

•Con individual: Requires increase in LACP PDU size, and even then one can run out of space if too many services present.

What information must be passed among the nodes in the Interconnect?

•This depends on whether we want to achieve total insulation of the two networks from each other.

• It depends on whether we want to achieve good load distribution in the face of networks changing service to Portal node assignments.

Page 4: IEEE 802 plenary, Singapore, March, 2011 1 bq-nfinn-Axbq-editing-0311-v01.pdf P802.1AXbq editing plan Rev. 1 Norman Finn nfinn@cisco.com

4IEEE 802 plenary, Singapore, March, 2011bq-nfinn-Axbq-editing-0311-v01.pdf

Current 802.1AX document

1. Overview

2. Normative references

3. Definitions

4. Acronyms and abbreviations

5. Link Aggregation

6. Management

A (informative) Collection and Distribution functions

B (informative) LACP standby link selection and dynamic Key management

C (normative) SNMP MIB definitions for Link Aggregation

(All sections except Annex C and perhaps Annex B need some changes)

Page 5: IEEE 802 plenary, Singapore, March, 2011 1 bq-nfinn-Axbq-editing-0311-v01.pdf P802.1AXbq editing plan Rev. 1 Norman Finn nfinn@cisco.com

5IEEE 802 plenary, Singapore, March, 2011bq-nfinn-Axbq-editing-0311-v01.pdf

In a nutshell:

1. Overview

2. Normative references

3. Definitions

4. Acronyms and abbreviations

5. Link Aggregation• 5.7 PICS

6. Management

A (inform) Collection and Distribution functions

B (inform) LACP standby link selection and dynamic Key management

C (norm) SNMP MIB definitions for Link Aggregation

1. Overview 2. Normative references 3. Definitions 4. Acronyms and abbreviations 5. Link Aggregation 6. Distributed Resilient Network

Interconnect 7. Management 8. PICS A (inform) Collection and

Distribution functions B (inform) LACP standby link

selection and dynamic Key management

C (norm) SNMP MIB definitions for LinkAgg and DRNI

BEFORE AFTER

Page 6: IEEE 802 plenary, Singapore, March, 2011 1 bq-nfinn-Axbq-editing-0311-v01.pdf P802.1AXbq editing plan Rev. 1 Norman Finn nfinn@cisco.com

6IEEE 802 plenary, Singapore, March, 2011bq-nfinn-Axbq-editing-0311-v01.pdf

Expanding clauses 5 and 6

5. Link Aggregation

5.1 Overview

5.2 Link Aggregation operation

5.3 Link Aggregation Control

5.4 Link Aggregation Control Protocol (LACP)

5.5 Marker Protocol

5.6 Configuration capabilities and restrictions

5.7 Protocol implementation conformance statement (PICS) proforma

Distributed Resilient Network Interconnect

6.1 Overview

6.2 DRNI operation

6.3 DRNI Control

6.4 LACP-DRNI

6.6 Configuration capabilities and restrictions

6.7 Requirements for networks connected via DRNI.

Clause 5 AFTER Clause 6 AFTER