Re: PROs/CONs of SIP/PIP/TUBA
Steve Deering <deering@parc.xerox.com> Mon, 17 May 1993 16:54 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00991;
17 May 93 12:54 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa00987;
17 May 93 12:54 EDT
Received: from p.lanl.gov by CNRI.Reston.VA.US id aa08597; 17 May 93 12:54 EDT
Received: from noc-gw.lanl.gov by p.lanl.gov (5.65/1.14)
id AA24217; Mon, 17 May 93 10:51:37 -0600
Received: by noc-gw.lanl.gov (4.1/SMI-4.1)
id AA12641; Mon, 17 May 93 10:51:11 MDT
Return-Path: <deering@parc.xerox.com>
Received: from p.lanl.gov by noc-gw.lanl.gov (4.1/SMI-4.1)
id AA12637; Mon, 17 May 93 10:51:10 MDT
Received: from alpha.Xerox.COM by p.lanl.gov (5.65/1.14)
id AA24185; Mon, 17 May 93 10:51:10 -0600
Received: from skylark.parc.xerox.com ([13.2.116.7]) by alpha.xerox.com with
SMTP id <11651>; Mon, 17 May 1993 09:50:30 PDT
Received: from localhost by skylark.parc.xerox.com with SMTP id <12171>;
Mon, 17 May 1993 09:50:20 -0700
To: John Day <Day@bbn.com>
Cc: pip@thumper.bellcore.com, sip@caldera.usc.edu, tuba@lanl.gov
Subject: Re: PROs/CONs of SIP/PIP/TUBA
In-Reply-To: Your message of "Mon, 17 May 93 10:10:03 PDT."
<9305171608.AA21198@thumper.bellcore.com>
Date: Mon, 17 May 1993 09:50:06 PDT
X-Orig-Sender: Steve Deering <deering@parc.xerox.com>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Steve Deering <deering@parc.xerox.com>
Message-Id: <93May17.095020pdt.12171@skylark.parc.xerox.com>
> While I could be wrong from my last reading of IPAE, if I move my end > system from one place to another all of the addresses I used to connect > to will have changed. That's incorrect. Maybe you are confusing IPAE with NAT? > Why else are they exploring these methods to download addresses? What "downloading" are you referring to? > Sorry Steve, but connection-oriented or not, pdus with different > priorities are simply different flows. Yes, I understand that model. What I was talking about is how those flows should be identified, by address+priority or by address alone. > I realize that this is a shift in frame of reference in how we normally > think about things and that such shifts are hard to think about. One of the goals of the SIP design is to avoid unnecessary shifts of frames of reference, so that SIP isn't hard to think about. > Doing the routing does not require doing a directory lookup for each > packet's destination address (or only if you look at the problem wrong). > The router merely has to know how it treats which flows which are > identified by their addresses. Are you proposing that the priority be indicated by well-known values in a well-known subfield of the addresses, or does the mapping of address to priority require external information, such as a directory entry or information distributed in a routing protocol? If the latter, it will be significantly and unnecessarily more expensive to support. > You are making this problem too difficult. Maybe you are making its solution too expensive? Steve
- PROs/CONs of SIP/PIP/TUBA Eric Fleischman
- Re: PROs/CONs of SIP/PIP/TUBA John Day
- Re: PROs/CONs of SIP/PIP/TUBA Steve Deering
- Re: PROs/CONs of SIP/PIP/TUBA John Day
- Re: PROs/CONs of SIP/PIP/TUBA John Day
- Re: PROs/CONs of SIP/PIP/TUBA John Day
- Re: PROs/CONs of SIP/PIP/TUBA Steve Deering
- Re: PROs/CONs of SIP/PIP/TUBA Ross Callon
- Re: PROs/CONs of SIP/PIP/TUBA Tony Whyman
- Re: PROs/CONs of SIP/PIP/TUBA Tony Whyman
- Re: PROs/CONs of SIP/PIP/TUBA William Allen Simpson