1 / 5

Prefix Assignment and distribution of other configuration infromation

Prefix Assignment and distribution of other configuration infromation. Ole Trøan @ Homenet IETF82. Problem:. How to assign stable prefixes to links in an arbitrary topology home network? How to distribute other configuration information (DNS servers etc )?

gyda
Download Presentation

Prefix Assignment and distribution of other configuration infromation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Prefix Assignment and distribution of other configuration infromation Ole Trøan@Homenet IETF82

  2. Problem: • How to assign stable prefixes to links in an arbitrary topology home network? • How to distribute other configuration information (DNS servers etc)? • Given multiple sources of information

  3. Possible Solutions (interim): • Layer 2/RFC6204 topology – null solution • Multilink subnet routing • Hosts routes combined with ND flooding (draft-ietf-ipv6-multilink-subnets-00) • Hierarchical DHCP Prefix DelegationRFC3633 + draft-chakrabarti-homenet-prefix-alloc-00 • Flat DHCP Prefix Delegation RFC3633 + draft-baker-homenet-prefix-assignment-00 • Zeroconf OSPF draft-arkko-homenet-prefix-assignment-01 • NAT (IPv6 NAT or NPT66) • Others

  4. Consider: Flooding vs Request/Reply • Request/Reply may require a God server • Make handling multiple sources of information difficult • Request/Reply requires some way of discovery of the “server”. • Flooding is distributed state. All routers in the network has the same view of the network. Assuming link-state routing here. • Requires “collision detection” • Both assumes fate sharing that the node injecting site-prefix or being the server are co-located with the border router

More Related