1 / 7

Autonomic IPv6 Edge Prefix Management in Large-scale Networks ANIMA WG IETF 95, April 2015

Autonomic IPv6 Edge Prefix Management in Large-scale Networks ANIMA WG IETF 95, April 2015. draft-ietf-anima-prefix-management-00 Sheng Jiang Brian Carpenter Qiong Sun Zongpeng Du. Reminder – Motivation. To validate the application and reusability of Anima components.

jshreffler
Download Presentation

Autonomic IPv6 Edge Prefix Management in Large-scale Networks ANIMA WG IETF 95, April 2015

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. Autonomic IPv6 Edge Prefix Management in Large-scale Networks ANIMA WGIETF 95, April 2015 draft-ietf-anima-prefix-management-00 Sheng JiangBrian CarpenterQiong SunZongpeng Du

  2. Reminder – Motivation • To validate the application and reusability of Anima components. • In large networks, prefix management still depends on human planning. Management of IPv6 prefixes is rigid and static after initial planning. • The autonomic networking mechanism is to dynamically and autonomically manage IPv6 address space in large-scale networks. • Ideally, administrators just configure a single IPv6 prefix for the whole network and the initial prefix length for each device role. Page 2

  3. Reminder – Overview • A prefix requesting device needs more address space. • Discovers peer devices that may be able to provide extra address space by GRASP Discovery message for the PrefixManager objective. • Then negotiates with a discovered peer for the needed address space using GRASP messages. • In a single administrative domain, the network operator manages all PrefixManager devices with the same Intent rules, flooded using GRASP. • Discovery, negotiation & flooding messages go through the secure Autonomic Control Plane (ACP). Page 3

  4. Main Changes in WG –00 draft Focus is on prefix management at the network edge (i.e. assume that core is already numbered). But the solution is not restrictive. The description is now much more specific about the usage of GRASP. The mechanism is now intended to be “PD friendly”. If nodes support DHCPv6 Prefix Delegation, it will be used. If not, the GRASP negotiation itself will delegate a prefix. Page 4

  5. GRASP objectives (1)in CDDL notation objective = ["PrefixManager", objective-flags, loop-count, PD-support, length, ?prefix] loop-count = 0..255 ; see GRASP spec objective-flags /= ; see GRASP spec PD-support = true / false ; indicates if sender supports PD length = 0..128 ; requested/offered prefix length prefix = bytes .size 16 ; offered prefix in binary Page 5

  6. GRASP objectives (2)in CDDL notation objective = ["Intent.PrefixManager",objective-flags, loop-count, text] loop-count = 0..255 ; see GRASP spec objective-flags /= ; see GRASP spec ; The text object would be the relevant intentstatements (format TBD) transmitted as asingle string. Alternatively, we would use the proposed CBOR encoding for yang. Page 6

  7. Next Steps Reviews and comments wanted, of course. We also want a volunteer to try writing a prototype PrefixManager ASA. Easiest would be to write in Python 3 since there is a prototype GRASP implementation and API. Page 7

More Related