Re: [dhcwg] Call for Adoption: draft-yeh-dhc-dhcpv6-prefix-pool-opt-08

[<[e-mail]>]

Dear Chairs, all,

I support the adoption of this draft as it allows to:

* Avoid misbehaving routers which inject a large number of individual prefixes instead of aggregating them. The behaviour of the edge router supporting this mechanism is deterministic and it does not depend on a specific implementation. Network operators may decide to inject an aggregate even if all individual prefixes are not assigned to connected nodes. 

* Control the prefixes to be injected in routing without requiring a dedicated configuration interface no a new DHCP message. 

* Retrieve the set of routes injected by the router embedding the relay agent.

Cheers,
Med

PS: I'm also co-author of the draft.
 

>-----Message d'origine-----
>De : [e-mail] [mailto:[e-mail]] De 
>la part de Ted Lemon
>Envoyé : vendredi 24 août 2012 17:32
>À : [e-mail] WG
>Objet : [dhcwg] Call for Adoption: 
>draft-yeh-dhc-dhcpv6-prefix-pool-opt-08
>
>The authors have proposed that the working group adopt the 
>prefix pool option draft as a working group item.   We have 
>engaged in some correspondence with participants in the 
>Routing Area, and while some helpful advice was given, no 
>objections were raised to going forward with the work, and 
>it's a DHCP protocol extension, so it makes sense for it to 
>happen in the DHC working group.
>
>The document proposes an extension to the DHCP protocol that 
>allows the DHCP server to communicate prefixes to the provider 
>edge router when doing prefix delegation, such that this 
>router can advertise a route to an aggregate prefix, rather 
>than to many individual prefixes, and so that this router does 
>not have to perform ad-hoc prefix aggregation, which may 
>produce less optimal results.
>
>If you think this work should be adopted by the working group, 
>please reply to this message saying so.   If you think this 
>work should not be adopted by the working group, please reply 
>to this message saying so.   We will evaluate consensus on September 7.
>
>_______________________________________________
>dhcwg mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/dhcwg
>