Presentation is loading. Please wait.

Presentation is loading. Please wait.

Antonio de la Oliva (UC3M)

Similar presentations


Presentation on theme: "Antonio de la Oliva (UC3M)"— Presentation transcript:

1 Antonio de la Oliva (UC3M)
IEEE 802.1CQ ToC Antonio de la Oliva (UC3M)

2 Current state 1. Overview 1.1 Scope 2. Normative references
3. Definitions, acronyms and abbreviations 3.1  Definitions 3.2  Acronyms and abbreviations 4. Basics of multicast and local address assignment 5. Theory of operation 6. Address space 6.1  Null address 6.2  Default blocks 6.3  Well-known multicast addresses 7. Message formats 7.1 Address client behavior 7.2 Address server behavior 7.3 Bridge behavior 8. Interaction with 802.1X, 802.1AE, etc.

3 Proposed ToC 1. Overview Interaction with DHCP
1.1 Scope Normative references Definitions, acronyms and abbreviations 3.1  Definitions 3.2  Acronyms and abbreviations Basics of multicast and local address assignment Architecture Proxy DHCP Identifiers Theory of operation Address space 6.1  Null address 6.2  Default blocks: Blocks reserved for randomnization 6.3  Well-known multicast addresses Protocol definitions Unicast self-assignment Multicast self-assignment Local Address Assignment Protocol (LAAP) Interaction with DHCP Discovery of MAC Address Local Policies WLAN WIRED Interaction with 802.1X, 802.1AE, etc. (this must include deviceID) Appendix IEEE PAD Deployment scenarios

4 Open topics Identifiers DHCP interaction
We must have identifiers to enable the mapping of STAs to known MAC address Requirement from WBA? Identifier does not need to be unique for the STA, it can have multiple Ids and use them as required. Potentially one per point of attachment Do we need to specify some bunding between the ID and the address? Cryptographic relation 64 bits? Randomnly choosen? DHCP interaction Shall we asume Proxies are able to get pull of addresses out of DHCP? Of any quadrant?

5 Open Points Shall we use MAAP for multicast addresses?
Do we need a new redefinition of it for multicast? Probably we have a problem with the multicast pull, specified in 1722 Blocks of addresses and allocation of addresses What can we safely used as source address in self-assignment? EUI-48? Do we want to define a default block of addresses for randomisation? We have something working to discover the MAC Address Policy in IEEE What do we do for wired? LDP?


Download ppt "Antonio de la Oliva (UC3M)"

Similar presentations


Ads by Google