My ID on addressing
Garrett.Wollman@uvm.edu Sun, 10 January 1993 23:02 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08314;
10 Jan 93 18:02 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa08310;
10 Jan 93 18:01 EST
Received: from thumper.bellcore.com by CNRI.Reston.VA.US id aa09895;
10 Jan 93 18:02 EST
Received: from sadye.emba.uvm.edu by thumper.bellcore.com (4.1/4.7)
id <AA02998> for ietf-archive@nri.reston.va.us; Sun, 10 Jan 93 18:00:50 EST
Received: by sadye.emba.uvm.edu id AA00208
(5.65/6.02); Sat, 9 Jan 93 17:51:58 -0500
Date: Sat, 9 Jan 93 17:51:58 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Garrett.Wollman@uvm.edu
Message-Id: <9301092251.AA00208@sadye.emba.uvm.edu>
To: pip@thumper.bellcore.com
Subject: My ID on addressing
PIP folks:
Before my holiday vacation, I put out an ID on what I have called
"NAP-based addressing." Unfortunately, I was not explicit enough in
my request message, so it got filed under the DNS WG (I had expected
it to be draft-wollman-...). Oh, dear, another mailing-list I have to
join and see what they're saying about me.
In any event, I'd like to encourage everybody to take a look at
draft-ietf-dns-nap-00.{txt,ps}, and let me know what you think. The
ideas set out there are basically my idea of how to solve the
Addressing Problem and the Mobile Host Problem (which I guess we could
call "ROAD-complete", by analogy with "AI-complete") in the context of
PIP, in a way which doesn't completely break the architecture of the
existing DNS.
-GAWollman
--
Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ...
wollman@emba.uvm.edu | Shashish is the bonding of hearts in spite of distance.
uvm-gen!wollman | It is a bond more powerful than absence. We like people
UVM disagrees. | who like Shashish. - Claude McKenzie + Florent Vollant
- My ID on addressing Garrett.Wollman
- Re: My ID on addressing Paul Tsuchiya
- Re: My ID on addressing Garrett.Wollman