Here are my last call comments on draft-ietf-homenet-prefix-assignment: "implementing reliable broadcast" seems like an imprecise specification of "Flooding Mechanism". Exactly what characteristics are desired for the Flooding Mechanism: reliable delivery of the state of "published Assigned Prefixes" within some time limit?
Might seem like a nit ... but what is a "node"? Always a router? Can it be a host? Is it some abstract function that can appear in either a host or a router? Editorial: in the definition of Private Link, "requesting router" would be a better term than "client" (see RFC 3633). Are Shared Links identified in some way in the mechanism? If so, how? I see the phrase "there never is more than one Assigned Prefix per Delegated Prefix and Link pair", but I don't see how a Link is identified. Similarly, "The Assigned Prefix is advertised through the Flooding Mechanism as assigned to its associated Link" Or maybe I'm missing something and the identification isn't necessary? - Ralph _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
