I realised while reading this draft that I just don't understand its operating model. It refers to the "requesting" router supplying Prefix Collection and Prefix Information to the delegating router:
> When requesting prefixes a requesting router MUST add for each > requested prefix a Prefix Information in the Prefix Delegation option > of the RS message. However, by definition the requesting router doesn't know what prefix(es) it will be given. So surely all it can ask for is N unspecified prefixes of given lengths? It also says: > PC_ID: An unique identifier of the Prefix Collection. The > PC_ID MUST be unique among all PC_ID known by the > requesting router. How can the requesting router provide this in its REQ message? By guessing? > 11. Security Considerations > > TBD OK, but since a vehicular network is open to any one of millions of unmanaged devices, this will need to be *very* convincing, especially in preventing DOS. Regards Brian Carpenter -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
