IETF Logo Mail Archive

Omnibus reply - EIDs

yakov@watson.ibm.com Sun, 10 July 1994 18:50 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa02709; 10 Jul 94 14:50 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa02705; 10 Jul 94 14:50 EDT
Received: from murtoa.cs.mu.OZ.AU by CNRI.Reston.VA.US id aa08841; 10 Jul 94 14:50 EDT
Received: from mailing-list by murtoa.cs.mu.OZ.AU (8.6.9/1.0) id EAA12444; Mon, 11 Jul 1994 04:46:35 +1000
Received: from munnari.oz.au by murtoa.cs.mu.OZ.AU (8.6.9/1.0) with SMTP id EAA12413; Mon, 11 Jul 1994 04:33:25 +1000
Precedence: list
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: yakov@watson.ibm.com
Received: from watson.ibm.com by munnari.oz.au with SMTP (5.83--+1.3.1+0.50) id AA20474; Mon, 11 Jul 1994 04:33:22 +1000 (from yakov@watson.ibm.com)
Message-Id: <9407101833.20474@munnari.oz.au>
Received: from YKTVMV by watson.ibm.com (IBM VM SMTP V2R3) with BSMTP id 9599; Sun, 10 Jul 94 14:33:18 EDT
Date: Sun, 10 Jul 1994 14:28:01 -0400
To: kre@munnari.oz.au
Cc: big-internet@munnari.oz.au
Subject: Omnibus reply - EIDs

Ref:  Your note of Sat, 09 Jul 1994 08:31:28 +1000

Robert,
>Incidentally, this kind of example also shows the need for strict
>source route. What's wrong with them is that they currently require
>too much knowledge, strict routes usually need to apply just one
>or two hops, not the whole path.

The functionality you asking for is quite similar to the IPng
requirements from the Unified Architecture point of view
(see Internet Draft draft-estrin-ipng-unified-routing-00.txt).
The source route encoding in the BigTen packet format is designed
to address this functional requirement.

Yakov.

v2.23.0 | Report a Bug | By Email