After the Homenet meeting in Paris I realized that the group needs
good principles for its name-space work. The principles in -arch-02 are
a good start but IMHO not sufficient.
It makes not sense to be proposing/evaluating solutions when there
are no agreed upon principles/requirements.
The chairs have been bugging me to follow up with a contribution.
Below is my attempt at defining as compactly/broadly as
possible design principles for Name services:
a) Homenet name-service MUST NOT interfere with Internet name-service
b) Homenet name-service MUST NOT be in Internet name space.
e) Homenet name-service MUST function throughout the whole "site"
c) Homenet name-service SHOULD support both lookups and discovery
d) Homenet name-service SHOULD be considerate of bandwidth usage
e) Homenet name-service MUST allow segmentation of "name space" for
different classes/groups/cliques of applications/devices
g) Homenet name-service SHOULD allow both broadcast service as well as
more traditional lookup service.
I'm expecting a lively discussion on this topic :-)
Olafur
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
