Re: Host Addressing Conventions [addr-conv 2.8]
Paul Francis--formerly Tsuchiya <francis@thumper.bellcore.com> Mon, 14 June 1993 21:25 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11327; 14 Jun 93 17:25 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa11323; 14 Jun 93 17:25 EDT
Received: from thumper.bellcore.com by CNRI.Reston.VA.US id aa21350; 14 Jun 93 17:25 EDT
Received: by thumper.bellcore.com (4.1/4.7) id <AA07115> for ietf-archive@nri.reston.va.us; Mon, 14 Jun 93 17:25:00 EDT
Received: from tsuchiya.bellcore.com by thumper.bellcore.com (4.1/4.7) id <AA07110> for /usr/lib/sendmail -oi -fowner-pip X-pip; Mon, 14 Jun 93 17:24:59 EDT
Received: by tsuchiya.bellcore.com (4.1/4.7) id <AA13220> for pip@thumper.bellcore.com; Mon, 14 Jun 93 17:24:58 EDT
Date: Mon, 14 Jun 1993 17:24:58 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Paul Francis--formerly Tsuchiya <francis@thumper.bellcore.com>
Message-Id: <9306142124.AA13220@tsuchiya.bellcore.com>
To: Garrett.Wollman@uvm.edu, pip@thumper.bellcore.com
Subject: Re: Host Addressing Conventions [addr-conv 2.8]
> > I'm a bit concerned about the idea of ``LAN-based'' addresses. I > thought one of the problems we were trying to solve was the > ``multi-homed host problem''. But unless I misunderstand something > here, it looks like it should be possible to replace all occurrences > of ``LAN'' with ``Area'' and have things still work. (The > substitution of ``ESIS'' for ``ARP'' is left as an exercise for the > reader.) Or perhaps when Paul wrote ``LAN'' he meant something akin > to what I mean by an ``Area''. > No, I mean LAN. I really like LAN based addressing. It seems to me a very natural place to put an address boundary-- address follows topology..... As for multi-homing, it is solved in another way....the host gets multiple addresses, a Pip host picks one, and switches to the other if it gets a PCMP Packet Not Delivered indicating that one LAN can't be reached. (Anyway, even with areas, you haven't completely solved the multi-homing problem. A host might be multi-homed to multiple areas). PX
- Host Addressing Conventions [addr-conv 2.8] Garrett.Wollman
- Re: Host Addressing Conventions [addr-conv 2.8] Paul Francis--formerly Tsuchiya
- Re: Host Addressing Conventions [addr-conv 2.8] Garrett.Wollman
- Re: Host Addressing Conventions [addr-conv 2.8] braja
- Re: Host Addressing Conventions [addr-conv 2.8] Paul Francis--formerly Tsuchiya
- Re: Host Addressing Conventions [addr-conv 2.8] Garrett.Wollman
- Re: Host Addressing Conventions [addr-conv 2.8] Paul Francis--formerly Tsuchiya
- Re: Host Addressing Conventions [addr-conv 2.8] Garrett.Wollman
- Re: Host Addressing Conventions [addr-conv 2.8] Paul Francis--formerly Tsuchiya
- Re: Host Addressing Conventions [addr-conv 2.8] Garrett.Wollman
- Re: Host Addressing Conventions [addr-conv 2.8] Paul Francis--formerly Tsuchiya