On 2011-12-19 11:49, Ted Lemon wrote: > On Dec 18, 2011, at 5:17 PM, Brian E Carpenter wrote: > According to [RFC4007], a scope zone is identified by a Zone Identifier. > In practice, a scope zone often corresponds to a single interface, so > interfaces are also identified by Zone Identifiers. For consistency, > provisioning domains too are identified by Zone Identifiers. In the > simplest case, a single Zone Identifier will name an interface, a scope > zone, and a provisioning domian. In more complex cases, an interface, > the scope zone it reaches, and the corresponding provisioning domain > will have different Zone Identifiers. > > So you're proposing to identify three different things with the same kind of > identifier?
Yes. RFC4007 and current practice already mean that interfaces and scopes use the same namespace, and this would be a seamless extension. Note that it's a completely unstructured namespace that's local to the host. It maps straight into draft-carpenter-6man-uri-zoneid in a very natural way, too. (We are still far from having a proper handle on naming and addressing scopes; but that is a very different question that I've been poking at uselessly for a while: http://tools.ietf.org/html/draft-carpenter-referral-ps ) Brian _______________________________________________ mif mailing list [email protected] https://www.ietf.org/mailman/listinfo/mif
