In your previous mail you wrote:
So I guess we should treat this issue in a related API discussion.
I'd like to propose the following approach:
- the scoping architecture draft only defines the numerical zone IDs
and their aliases for readability (like "site1")
- the scoping architecture draft does NOT define the zone "names", but
mentions that implementation can use intuitive names in the textual
representation, and that interface names can be used as
interface/link/subnet zone IDs by default.
- write a separate informational document, which talks about the API
of the scoping issues, including possible representation of names,
and mapping of numerical identifiers and names.
=> what we need is a more general (than "site1") notion of names
and the way to translate names to zone IDs and the reverse.
The actual syntax and semantics of names are not very important if
some simple rules (no % in names for instance) are given.
Regards
[EMAIL PROTECTED]
PS: I am waiting for a concrete proposal (i.e. a draft)
PPS: don't forget to update RFC 2732
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
