> This proposal doesn't satisfy the problem statement.
> (which nobody wrote. :)
Perhaps we could start by writing up the usage scenarios we have in mind?
I'll start:
1. I want to point a web browser at the configuration interface of the
router in my attic;
2. I want to point a web browser at the boom-box in my living room
2a. the boom-box speaks IP and is Homenet-aware;
2b. the boom-box speaks IP but is not Homenet-aware;
3. I want you to join in a game that I'm playing, so I need a memorable
public URL for the Nethack server
3a. the Nethack server is in my Homenet;
3b. the Nethack server is outside my Homenet;
4. I'm running a BitTorrent seeder, and I want the RIAA to be able to
perform a reverse mapping on my IP address so they can use a memorable
name in their correspondence.
Naming of routers and hosts is likely to use different mechanisms, which
is why I separate (1) and (2). I've never understood the purpose of
reverse mapping except for debugging, so (4) is the best I could come up
with.
-- Juliusz
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
