Re: (sipp) Loopback & SST
William Allen Simpson <bill.simpson@um.cc.umich.edu> Thu, 21 July 1994 04:13 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa22241; 21 Jul 94 0:13 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa22237; 21 Jul 94 0:13 EDT
Received: from Sun.COM by CNRI.Reston.VA.US id aa20476; 21 Jul 94 0:13 EDT
Received: from Eng.Sun.COM (zigzag.Eng.Sun.COM) by Sun.COM (sun-barr.Sun.COM) id AA04390; Wed, 20 Jul 94 10:06:57 PDT
Received: from sunroof2.Eng.Sun.COM by Eng.Sun.COM (4.1/SMI-4.1) id AA21925; Wed, 20 Jul 94 10:07:09 PDT
Received: by sunroof2.Eng.Sun.COM (4.1/SMI-4.1) id AA01149; Wed, 20 Jul 94 10:07:57 PDT
Received: from Eng.Sun.COM (engnews1) by sunroof2.Eng.Sun.COM (4.1/SMI-4.1) id AA01138; Wed, 20 Jul 94 10:07:46 PDT
Received: from Sun.COM (sun-barr) by Eng.Sun.COM (4.1/SMI-4.1) id AA03778; Wed, 20 Jul 94 10:05:29 PDT
Received: from merit.edu by Sun.COM (sun-barr.Sun.COM) id AA03980; Wed, 20 Jul 94 10:05:02 PDT
Received: from pm002-19.dialip.mich.net (pm002-19.dialip.mich.net [35.1.48.100]) by merit.edu (8.6.8.1/merit-1.0) with SMTP id NAA22439 for <sipp@sunroof.eng.sun.com>; Wed, 20 Jul 1994 13:04:59 -0400
Date: Wed, 20 Jul 1994 15:09:25 +0000
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: William Allen Simpson <bill.simpson@um.cc.umich.edu>
Message-Id: <2888.bill.simpson@um.cc.umich.edu>
To: sipp@sunroof.eng.sun.com
Subject: Re: (sipp) Loopback & SST
X-Orig-Sender: owner-sipp@sunroof.eng.sun.com
Precedence: bulk
Reply-To: sipp@sunroof.eng.sun.com
> From: Steve Deering <deering@parc.xerox.com> > > One solution might be to move the SIPP loopback address somewhere else in > > the address space. For example, an all-nodes multicast with intra-node > > scope sounds awfully like a loopback to me, but I'm not multicast expert. > > The loopback address may be used a source address, whereas a multicast > adress may not. > I suggested the same thing. I'm not sure this is a good argument against it. When is the loopback ever used as a source address? Another reasonable reply was from Bob that FE prefix is technically a local-use address which can be filtered out for misbehaving hosts. The same thing has to be done for intra-node scope multicast destinations anyway. And we might as well filter all multicast sources, too. So, we accomplish the same thing more efficiently by using an intra-node scope as loopback. I still think that loopback should be FF01::1. Actually, that reminds me of my old wish that intra-node would be scope 0 rather than 1. Then, loopback would be FF::1, the logical successor to 127..1. But, this is minor. (What's less than intra-node? Intra-process? Why are we reserving it? If so, maybe we should move it up to make room for intra-cpu for multi-cpu platforms. ;-) Bill.Simpson@um.cc.umich.edu ------------------------------------------------------------------------------ IETF SIPP Working Group - Archives: parcftp.xerox.com:/pub/sipp Unsubscribe: unsubscribe sipp (as message body, not subject) Direct all administrative requests to majordomo@sunroof.eng.sun.com
- (sipp) Loopback & SST owner-sipp
- Re: (sipp) Loopback & SST Steve Deering
- Re: (sipp) Loopback & SST William Allen Simpson
- Re: (sipp) Loopback & SST Steve Deering
- Re: (sipp) Loopback & SST Matt Crawford