Re: Host Addressing Conventions [addr-conv 2.8]

Paul Francis--formerly Tsuchiya <francis@thumper.bellcore.com> Tue, 15 June 1993 16:15 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10456; 15 Jun 93 12:15 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa10452; 15 Jun 93 12:15 EDT
Received: from thumper.bellcore.com by CNRI.Reston.VA.US id aa12183; 15 Jun 93 12:15 EDT
Received: by thumper.bellcore.com (4.1/4.7) id <AA14992> for P.County@latrobe.edu.au; Tue, 15 Jun 93 11:14:57 EDT
Received: from tsuchiya.bellcore.com by thumper.bellcore.com (4.1/4.7) id <AA14988> for /usr/lib/sendmail -oi -fowner-pip X-pip; Tue, 15 Jun 93 11:14:55 EDT
Received: by tsuchiya.bellcore.com (4.1/4.7) id <AA14313> for pip@thumper.bellcore.com; Tue, 15 Jun 93 11:14:54 EDT
Date: Tue, 15 Jun 1993 11:14:54 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Paul Francis--formerly Tsuchiya <francis@thumper.bellcore.com>
Message-Id: <9306151514.AA14313@tsuchiya.bellcore.com>
To: Garrett.Wollman@uvm.edu, francis@thumper.bellcore.com
Subject: Re: Host Addressing Conventions [addr-conv 2.8]
Cc: pip@thumper.bellcore.com

>  
>  I would much rather have the router make this decision, based on---for
>  example---network utilization.  I think I sent an example of this
>  about two months ago, but I forget where.  The host really doesn't
>  have the proper information to make this choice.  As I noted in my
>  earlier message, I think that simple textual substitution of ``area''
>  for ``LAN'' will allow this to work, when combined with either some
>  form of Proxy ARP (ugh!) or an address-resolution mechanism that
>  looks like ESIS.
>  

Well, your argument is certainly valid.  In spite of all appearances
to the contrary (ie, the Pip header.....), I'm trying to keep Pip
as simple as possible.....

None-the-less, very little has to be changed to make this work,
mainly ES-IS.  Another advantage of doing this is the mobility
bit.  Even with LAN-based addressing, if a host is mobile but its
movements are constrained to an "Area", then it is nice to just
advertise it in routing locally and not give it new addresses.....

We are already implementing router discovery.  Maybe we should take
a look at it to see what needs to be done to make it full ESIS.....

Any comment from other people pro or con?

PX