From routing-discussion-admin@ietf.org  Fri Aug  2 07:59:55 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15466
	for <routing-discussion-archive@odin.ietf.org>; Fri, 2 Aug 2002 07:59:55 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA09209;
	Fri, 2 Aug 2002 07:53:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA09178
	for <routing-discussion@ns.ietf.org>; Fri, 2 Aug 2002 07:53:14 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15178
	for <routing-discussion@ietf.org>; Fri, 2 Aug 2002 07:52:02 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id NAA05256;
	Fri, 2 Aug 2002 13:53:00 +0200 (MET DST)
Received: from mchh273e.demchh201e.icn.siemens.de ([139.21.200.83])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id NAA08406;
	Fri, 2 Aug 2002 13:53:01 +0200 (MET DST)
Received: by MCHH273E with Internet Mail Service (5.5.2656.59)
	id <P71Q92S5>; Fri, 2 Aug 2002 13:52:48 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B96D@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'jshen@cad.zju.edu.cn'" <jshen@cad.zju.edu.cn>
Cc: Venkata.Naidu@Marconi.com, jnc@ginger.lcs.mit.edu, fred@cisco.com,
        saq66@umkc.edu, irtf-rr@puck.nether.net, routing-discussion@ietf.org
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Fri, 2 Aug 2002 13:52:48 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="gb2312"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Hi Jing,
Find my comments inserted.
Regards
Heinrich 

1) if we want to route with DSCP it should be desired that  logical views of network based on each possible
DSCP is computed ?
HH=>
Yes, this is feasable. IMO, the alternative, that each link advertises all the DSCPs i.e. all the road systems  
it wants to be a part of, is not good eenough for two reasons:
            1) Only by computation we can make sure that each road system is "routable", i.e. enables road system
               internal transport between a particular set of edge routers.
            2) Some road systems are just the overflow-/2nd-best-route, 3rd-best-route road systems w.r.t. another
               road system. This cannot be assured without computation.     


2.)  Each router builds up a seperate routing table for each possible DSCP , and there exist a default routing table
       for packets whose DSCP are not set  ?
HH=>
     Differentiated road systems only make sense, when each of them uses only a part of the network links. A smallest
     size tree between a confined set of edge routers would yield such a "slim" road system. 
     If all your nodes are leaf nodes, then there is no difference between a shortest path tree and a smallest size tree.
     But on the other side, it still must be possible to send a packet from any edge or core router to any edge or core 
     router. I.e. we still need the exisiting best-effort road system. As long as you have only one road system you
     won't have to mark it. But as soon as there is a second one, you have to mark not only the second one 
     but also the first one. Will say you need one DSCP for traffic which shall be forwarded according to the current
     routing tables.

3.)   When a new packet arrives, the dispatching logic may look like :

      Procedure  DSCP_BASED_DISPATCH ( incoming_packet )
            if   DSCP   then
                 if  (  DSCP-related-table-exist )
                     running-table =  DSCP-related-table;

           if  running-table==NULL
                  running-table = default-table;

           out_port= find_routing_item( incoming_packet);
           enqueue(out_port, incoming_packet);

        END PROCEDURE
HH=>
Yes. I see, you already addresses the case where a packet is forwarded NOT as it should, i.e. not within the respective
road system. Of course, this needs to be covered, too. And yes, as you describe, by using the default (best effort) road system.

But, How could the logical view be computed?  DSCP is just for queueing mechanism, should that be included in LSA?

HH=> Life would be easier, if we had more available bits (we still have 2 CU currently unused Bits). But we don't have
64 Service Level Agreements either. It should be possible to satisfy DiffServ as well as DiffRout :-)

And, I think there may other problem as extensiblility and stability.
HH=> Sure. But compare it with DiffServ. DiffServ wasn't done either by one single draft and by one single IETF meeting session.

And,the last , I'm not so clear about the method computing shortest size tree, and I'm very interested in your work of
minimal partial mesh between n sites of a VPN. Would you please give a little more word or some reference sites ?

HH=>   

The idea was to interconnect n sites (PEs or CEs) by a minimal partial mesh of tunnels.It could only be a tree of
n-1 tunnels. And well, a tree of those "shortest" tunnels, which nevertheless interconnect all n sites. In principle,
it is a selection process as to sort out n-1 tunnels from n(n-1)/2 candidate tunnels.Thereafter, add those n-1 
tunnels which are inverse to the selected n-1  tunnels.

Preparation: Compute n Dijkstra-trees whereby each time another site-node becomes the root.As a result you have the best route from any node to any node (edge node as well as core node). You may sort all of these n(n-1) routes according to their
weight sums in ascending order.And you may associate a REGARD/DISREGARD-Bit to each of these routes (for speeding up the algorithm). Initially set all these Bits to REGARD=1.

Iteration:
As I told already, start out with n (separated) partitions, whereby initially each partition 
just contains  one site-node (no links yet). Also the initial set of tunnels, which finally shall become the
VPN PARTIAL MESH,is empty.
Make n-1 iteration steps.

At each iteration step, determine those two partitions, which can be combined by the shortest route(=tunnel)
among all those routes which are marked REGARD.
 
Combine the two partitions (logically), but in reality do this:
Add this determined shortest route/tunnel to VPN PARTIAL MESH. Set the REGARD/DISREGARD-Bit to DISREGARD=0 for all
those routes, which are "internal" to this combined partition. Note: this includes this shortest route/tunnel.
Precisely set the bit to DISREGARD for all those routes, wherebe the route started at a node from the one partition
and ended at a node from the other partition.

Do this n-1 times.

So far this was all about forming a "minimal size tunnel tree".


Only slightly different would be the algorithm for building what  I used to call a "minimal size multicast tree",
which extends between the sender node and the receiver nodes.

Preparation: 
Compute Dijkstra-trees as many as you have nodes in your network (edge as well as core nodes).
(So you also know the shortest route between any two core nodes as well).Hereby, each time another
node is the root node.

Like above, sort all these routes according to the ascending order of their weight sums, assign a REGARD/DISREGARD-Bit
to each of them, and initialize all these bits to REGARD=1.  

Iteration:
Start with an empty set of routes, called MULTICAST TREE, and with N partitions whereby each partition would only contain one
sender resp. receiver node initially (  for building a road system it would be any edge router 
with attached LAN, Host, ext.interface).

At each iteration step, determine those two partitions, which can be combined by the shortest route between any
node in one partition and any node in another partition. Hereby consider only those routes which are still marked REGARD.
 
Combine the two partitions (logically), but in reality do this:
Add this determined shortest route to MULTICAST TREE. Set the REGARD/DISREGARD-Bit to DISREGARD=0 for all
those routes, which are "internal" to this combined partition. Note: this includes the determined shortest route.
Precisely, set the bit to DISREGARD for all those routes, wherebe the route started at a node from the one partition
and ended at a node from the other partition.

Do this n-1 times.

As a result MULTICAST TREE will contain a list of routes (which are lists of links/nodes).
Or you may look at it in this way: MULTICAST TREE contains a list of links/nodes (which, by chance form a tree graph with
no special (root) node at all).

Take this list of links/nodes as your "basis network topology". And which ever node is part of it may run the most primitive
Dijkstra, i.e. whereby each link-weight is equal to 1, as to compute a tree which spans this tree-topology :-).
By doing so, that node will find out the right adjacent next-hop link with respect to each 
LAN/Host/ext.interface reachability prefix, i.e. can build a respective routing table.

Let's rename MULTICAST TREE to ROAD SYSTEM-for-DSCP "xyz".

It is very important that each node which is part of ROAD SYSTEM-for-DSCP "xyz", has computed the identical set of
links. This means, when, during the iteration, a particular shortest route between some separate partitions is computed,
it must be done in an unambiguous way -  yes, even if there were several equally shortest routes.Tie breaker rules
will be needed.

 


> Let's be concentrated again. And let me get to the heart of the matter.
>
> Obviously I am not the only one who thought about using the DSCP also for doing Differentiated Routing.
> Will say: not the only one who thought about indexing different Routing Tables by different DSCPs.
>
> IMO, these routing tables should represent different and very distinct and differentiated road systems.
> This is only possible, if they are genuine partial structures of the total network. In addition to them we still need
> that "default"-road system which is identical to the entire network (e.g. in order to ping any node), i.e. today's routing tables.
>

[snip]

--
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@ns.ietf.org  Fri Aug  2 07:59:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15475
	for <routing-discussion-archive@odin.ietf.org>; Fri, 2 Aug 2002 07:59:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA09960
	for routing-discussion-archive@odin.ietf.org; Fri, 2 Aug 2002 08:01:06 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA09209;
	Fri, 2 Aug 2002 07:53:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA09178
	for <routing-discussion@ns.ietf.org>; Fri, 2 Aug 2002 07:53:14 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15178
	for <routing-discussion@ietf.org>; Fri, 2 Aug 2002 07:52:02 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id NAA05256;
	Fri, 2 Aug 2002 13:53:00 +0200 (MET DST)
Received: from mchh273e.demchh201e.icn.siemens.de ([139.21.200.83])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id NAA08406;
	Fri, 2 Aug 2002 13:53:01 +0200 (MET DST)
Received: by MCHH273E with Internet Mail Service (5.5.2656.59)
	id <P71Q92S5>; Fri, 2 Aug 2002 13:52:48 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B96D@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'jshen@cad.zju.edu.cn'" <jshen@cad.zju.edu.cn>
Cc: Venkata.Naidu@Marconi.com, jnc@ginger.lcs.mit.edu, fred@cisco.com,
        saq66@umkc.edu, irtf-rr@puck.nether.net, routing-discussion@ietf.org
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Fri, 2 Aug 2002 13:52:48 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="gb2312"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Hi Jing,
Find my comments inserted.
Regards
Heinrich 

1) if we want to route with DSCP it should be desired that  logical views of network based on each possible
DSCP is computed ?
HH=>
Yes, this is feasable. IMO, the alternative, that each link advertises all the DSCPs i.e. all the road systems  
it wants to be a part of, is not good eenough for two reasons:
            1) Only by computation we can make sure that each road system is "routable", i.e. enables road system
               internal transport between a particular set of edge routers.
            2) Some road systems are just the overflow-/2nd-best-route, 3rd-best-route road systems w.r.t. another
               road system. This cannot be assured without computation.     


2.)  Each router builds up a seperate routing table for each possible DSCP , and there exist a default routing table
       for packets whose DSCP are not set  ?
HH=>
     Differentiated road systems only make sense, when each of them uses only a part of the network links. A smallest
     size tree between a confined set of edge routers would yield such a "slim" road system. 
     If all your nodes are leaf nodes, then there is no difference between a shortest path tree and a smallest size tree.
     But on the other side, it still must be possible to send a packet from any edge or core router to any edge or core 
     router. I.e. we still need the exisiting best-effort road system. As long as you have only one road system you
     won't have to mark it. But as soon as there is a second one, you have to mark not only the second one 
     but also the first one. Will say you need one DSCP for traffic which shall be forwarded according to the current
     routing tables.

3.)   When a new packet arrives, the dispatching logic may look like :

      Procedure  DSCP_BASED_DISPATCH ( incoming_packet )
            if   DSCP   then
                 if  (  DSCP-related-table-exist )
                     running-table =  DSCP-related-table;

           if  running-table==NULL
                  running-table = default-table;

           out_port= find_routing_item( incoming_packet);
           enqueue(out_port, incoming_packet);

        END PROCEDURE
HH=>
Yes. I see, you already addresses the case where a packet is forwarded NOT as it should, i.e. not within the respective
road system. Of course, this needs to be covered, too. And yes, as you describe, by using the default (best effort) road system.

But, How could the logical view be computed?  DSCP is just for queueing mechanism, should that be included in LSA?

HH=> Life would be easier, if we had more available bits (we still have 2 CU currently unused Bits). But we don't have
64 Service Level Agreements either. It should be possible to satisfy DiffServ as well as DiffRout :-)

And, I think there may other problem as extensiblility and stability.
HH=> Sure. But compare it with DiffServ. DiffServ wasn't done either by one single draft and by one single IETF meeting session.

And,the last , I'm not so clear about the method computing shortest size tree, and I'm very interested in your work of
minimal partial mesh between n sites of a VPN. Would you please give a little more word or some reference sites ?

HH=>   

The idea was to interconnect n sites (PEs or CEs) by a minimal partial mesh of tunnels.It could only be a tree of
n-1 tunnels. And well, a tree of those "shortest" tunnels, which nevertheless interconnect all n sites. In principle,
it is a selection process as to sort out n-1 tunnels from n(n-1)/2 candidate tunnels.Thereafter, add those n-1 
tunnels which are inverse to the selected n-1  tunnels.

Preparation: Compute n Dijkstra-trees whereby each time another site-node becomes the root.As a result you have the best route from any node to any node (edge node as well as core node). You may sort all of these n(n-1) routes according to their
weight sums in ascending order.And you may associate a REGARD/DISREGARD-Bit to each of these routes (for speeding up the algorithm). Initially set all these Bits to REGARD=1.

Iteration:
As I told already, start out with n (separated) partitions, whereby initially each partition 
just contains  one site-node (no links yet). Also the initial set of tunnels, which finally shall become the
VPN PARTIAL MESH,is empty.
Make n-1 iteration steps.

At each iteration step, determine those two partitions, which can be combined by the shortest route(=tunnel)
among all those routes which are marked REGARD.
 
Combine the two partitions (logically), but in reality do this:
Add this determined shortest route/tunnel to VPN PARTIAL MESH. Set the REGARD/DISREGARD-Bit to DISREGARD=0 for all
those routes, which are "internal" to this combined partition. Note: this includes this shortest route/tunnel.
Precisely set the bit to DISREGARD for all those routes, wherebe the route started at a node from the one partition
and ended at a node from the other partition.

Do this n-1 times.

So far this was all about forming a "minimal size tunnel tree".


Only slightly different would be the algorithm for building what  I used to call a "minimal size multicast tree",
which extends between the sender node and the receiver nodes.

Preparation: 
Compute Dijkstra-trees as many as you have nodes in your network (edge as well as core nodes).
(So you also know the shortest route between any two core nodes as well).Hereby, each time another
node is the root node.

Like above, sort all these routes according to the ascending order of their weight sums, assign a REGARD/DISREGARD-Bit
to each of them, and initialize all these bits to REGARD=1.  

Iteration:
Start with an empty set of routes, called MULTICAST TREE, and with N partitions whereby each partition would only contain one
sender resp. receiver node initially (  for building a road system it would be any edge router 
with attached LAN, Host, ext.interface).

At each iteration step, determine those two partitions, which can be combined by the shortest route between any
node in one partition and any node in another partition. Hereby consider only those routes which are still marked REGARD.
 
Combine the two partitions (logically), but in reality do this:
Add this determined shortest route to MULTICAST TREE. Set the REGARD/DISREGARD-Bit to DISREGARD=0 for all
those routes, which are "internal" to this combined partition. Note: this includes the determined shortest route.
Precisely, set the bit to DISREGARD for all those routes, wherebe the route started at a node from the one partition
and ended at a node from the other partition.

Do this n-1 times.

As a result MULTICAST TREE will contain a list of routes (which are lists of links/nodes).
Or you may look at it in this way: MULTICAST TREE contains a list of links/nodes (which, by chance form a tree graph with
no special (root) node at all).

Take this list of links/nodes as your "basis network topology". And which ever node is part of it may run the most primitive
Dijkstra, i.e. whereby each link-weight is equal to 1, as to compute a tree which spans this tree-topology :-).
By doing so, that node will find out the right adjacent next-hop link with respect to each 
LAN/Host/ext.interface reachability prefix, i.e. can build a respective routing table.

Let's rename MULTICAST TREE to ROAD SYSTEM-for-DSCP "xyz".

It is very important that each node which is part of ROAD SYSTEM-for-DSCP "xyz", has computed the identical set of
links. This means, when, during the iteration, a particular shortest route between some separate partitions is computed,
it must be done in an unambiguous way -  yes, even if there were several equally shortest routes.Tie breaker rules
will be needed.

 


> Let's be concentrated again. And let me get to the heart of the matter.
>
> Obviously I am not the only one who thought about using the DSCP also for doing Differentiated Routing.
> Will say: not the only one who thought about indexing different Routing Tables by different DSCPs.
>
> IMO, these routing tables should represent different and very distinct and differentiated road systems.
> This is only possible, if they are genuine partial structures of the total network. In addition to them we still need
> that "default"-road system which is identical to the entire network (e.g. in order to ping any node), i.e. today's routing tables.
>

[snip]

--
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Fri Aug  2 08:39:34 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16862
	for <routing-discussion-archive@odin.ietf.org>; Fri, 2 Aug 2002 08:39:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA11515;
	Fri, 2 Aug 2002 08:37:50 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA11486
	for <routing-discussion@optimus.ietf.org>; Fri, 2 Aug 2002 08:37:48 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16741
	for <routing-discussion@ietf.org>; Fri, 2 Aug 2002 08:36:36 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id OAA08744;
	Fri, 2 Aug 2002 14:37:42 +0200 (MET DST)
Received: from mchh274e.demchh201e.icn.siemens.de ([139.21.200.84])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id OAA12851;
	Fri, 2 Aug 2002 14:37:43 +0200 (MET DST)
Received: by MCHH274E with Internet Mail Service (5.5.2656.59)
	id <P83C1Y4Q>; Fri, 2 Aug 2002 14:37:07 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B96E@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'jshen@cad.zju.edu.cn'" <jshen@cad.zju.edu.cn>
Cc: Venkata.Naidu@Marconi.com, jnc@ginger.lcs.mit.edu, fred@cisco.com,
        saq66@umkc.edu, irtf-rr@puck.nether.net, routing-discussion@ietf.org
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Fri, 2 Aug 2002 14:37:08 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id IAA11487
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Let me resend this email and correct a stupid tiny error w.r.t. the "smallest size tunnel tree" algorithm.
However, the error highlights an important aspect: For building this tunnel tree, you have to combine two partitions
by means of an entire tunnel between some two VPN-sites which are tunnel endpoints.
No split in the middle of a tunnel will occur.
Where as:
For building a "smallest size tree" - road system
you have to combine two partitions by means of ANY route between these partitions. 
Eventually, one or two completely new branch nodes may be generated at this, at that, or at both partitions.

I will mark the change with  CHANGE***CHANGE and END OF CHANGE*** END OF CHANGE in the text.

Heinrich

-----Ursprščngliche Nachricht-----
Von: Hummel Heinrich [mailto:Heinrich.Hummel@icn.siemens.de]
Gesendet: Freitag, 2. August 2002 13:53
An: 'jshen@cad.zju.edu.cn'
Cc: Venkata.Naidu@Marconi.com; jnc@ginger.lcs.mit.edu; fred@cisco.com; saq66@umkc.edu; irtf-rr@puck.nether.net; routing-discussion@ietf.org
Betreff: AW: Differentiated Routing, not only plain rambo-SPF


Hi Jing,
Find my comments inserted.
Regards
Heinrich 

1) if we want to route with DSCP it should be desired that  logical views of network based on each possible
DSCP is computed ?
HH=>
Yes, this is feasable. IMO, the alternative, that each link advertises all the DSCPs i.e. all the road systems  
it wants to be a part of, is not good eenough for two reasons:
            1) Only by computation we can make sure that each road system is "routable", i.e. enables road system
               internal transport between a particular set of edge routers.
            2) Some road systems are just the overflow-/2nd-best-route, 3rd-best-route road systems w.r.t. another
               road system. This cannot be assured without computation.     


2.)  Each router builds up a seperate routing table for each possible DSCP , and there exist a default routing table
       for packets whose DSCP are not set  ?
HH=>
     Differentiated road systems only make sense, when each of them uses only a part of the network links. A smallest
     size tree between a confined set of edge routers would yield such a "slim" road system. 
     If all your nodes are leaf nodes, then there is no difference between a shortest path tree and a smallest size tree.
     But on the other side, it still must be possible to send a packet from any edge or core router to any edge or core 
     router. I.e. we still need the exisiting best-effort road system. As long as you have only one road system you
     won't have to mark it. But as soon as there is a second one, you have to mark not only the second one 
     but also the first one. Will say you need one DSCP for traffic which shall be forwarded according to the current
     routing tables.

3.)   When a new packet arrives, the dispatching logic may look like :

      Procedure  DSCP_BASED_DISPATCH ( incoming_packet )
            if   DSCP   then
                 if  (  DSCP-related-table-exist )
                     running-table =  DSCP-related-table;

           if  running-table==NULL
                  running-table = default-table;

           out_port= find_routing_item( incoming_packet);
           enqueue(out_port, incoming_packet);

        END PROCEDURE
HH=>
Yes. I see, you already addresses the case where a packet is forwarded NOT as it should, i.e. not within the respective
road system. Of course, this needs to be covered, too. And yes, as you describe, by using the default (best effort) road system.

But, How could the logical view be computed?  DSCP is just for queueing mechanism, should that be included in LSA?

HH=> Life would be easier, if we had more available bits (we still have 2 CU currently unused Bits). But we don't have
64 Service Level Agreements either. It should be possible to satisfy DiffServ as well as DiffRout :-)

And, I think there may other problem as extensiblility and stability.
HH=> Sure. But compare it with DiffServ. DiffServ wasn't done either by one single draft and by one single IETF meeting session.

And,the last , I'm not so clear about the method computing shortest size tree, and I'm very interested in your work of
minimal partial mesh between n sites of a VPN. Would you please give a little more word or some reference sites ?

HH=>   

The idea was to interconnect n sites (PEs or CEs) by a minimal partial mesh of tunnels.It could only be a tree of
n-1 tunnels. And well, a tree of those "shortest" tunnels, which nevertheless interconnect all n sites. In principle,
it is a selection process as to sort out n-1 tunnels from n(n-1)/2 candidate tunnels.Thereafter, add those n-1 
tunnels which are inverse to the selected n-1  tunnels.

Preparation: Compute n Dijkstra-trees whereby each time another site-node becomes the root.As a result you have the best route from any
 
CHANGE***CHANGE

site node to any site node. Here we can ignore those routes which do not start or end at a site node.

END OF CHANGE *** END OF CHANGE

You may sort all of these n(n-1) routes according to their
weight sums in ascending order.And you may associate a REGARD/DISREGARD-Bit to each of these routes (for speeding up the algorithm). Initially set all these Bits to REGARD=1.

Iteration:
As I told already, start out with n (separated) partitions, whereby initially each partition 
just contains  one site-node (no links yet). Also the initial set of tunnels, which finally shall become the
VPN PARTIAL MESH,is empty.
Make n-1 iteration steps.

At each iteration step, determine those two partitions, which can be combined by the shortest route(=tunnel)
among all those routes which are marked REGARD.
 
Combine the two partitions (logically), but in reality do this:
Add this determined shortest route/tunnel to VPN PARTIAL MESH. Set the REGARD/DISREGARD-Bit to DISREGARD=0 for all
those routes, which are "internal" to this combined partition. Note: this includes this shortest route/tunnel.
Precisely set the bit to DISREGARD for all those routes, wherebe the route started at a node from the one partition
and ended at a node from the other partition.

Do this n-1 times.

So far this was all about forming a "minimal size tunnel tree".


Only slightly different would be the algorithm for building what  I used to call a "minimal size multicast tree",
which extends between the sender node and the receiver nodes.

Preparation: 
Compute Dijkstra-trees as many as you have nodes in your network (edge as well as core nodes).
(So you also know the shortest route between any two core nodes as well).Hereby, each time another
node is the root node.

Like above, sort all these routes according to the ascending order of their weight sums, assign a REGARD/DISREGARD-Bit
to each of them, and initialize all these bits to REGARD=1.  

Iteration:
Start with an empty set of routes, called MULTICAST TREE, and with N partitions whereby each partition would only contain one
sender resp. receiver node initially (  for building a road system it would be any edge router 
with attached LAN, Host, ext.interface).

At each iteration step, determine those two partitions, which can be combined by the shortest route between any
node in one partition and any node in another partition. Hereby consider only those routes which are still marked REGARD.
 
Combine the two partitions (logically), but in reality do this:
Add this determined shortest route to MULTICAST TREE. Set the REGARD/DISREGARD-Bit to DISREGARD=0 for all
those routes, which are "internal" to this combined partition. Note: this includes the determined shortest route.
Precisely, set the bit to DISREGARD for all those routes, wherebe the route started at a node from the one partition
and ended at a node from the other partition.

Do this n-1 times.

As a result MULTICAST TREE will contain a list of routes (which are lists of links/nodes).
Or you may look at it in this way: MULTICAST TREE contains a list of links/nodes (which, by chance form a tree graph with
no special (root) node at all).

Take this list of links/nodes as your "basis network topology". And which ever node is part of it may run the most primitive
Dijkstra, i.e. whereby each link-weight is equal to 1, as to compute a tree which spans this tree-topology :-).
By doing so, that node will find out the right adjacent next-hop link with respect to each 
LAN/Host/ext.interface reachability prefix, i.e. can build a respective routing table.

Let's rename MULTICAST TREE to ROAD SYSTEM-for-DSCP "xyz".

It is very important that each node which is part of ROAD SYSTEM-for-DSCP "xyz", has computed the identical set of
links. This means, when, during the iteration, a particular shortest route between some separate partitions is computed,
it must be done in an unambiguous way -  yes, even if there were several equally shortest routes.Tie breaker rules
will be needed.

 


> Let's be concentrated again. And let me get to the heart of the matter.
>
> Obviously I am not the only one who thought about using the DSCP also for doing Differentiated Routing.
> Will say: not the only one who thought about indexing different Routing Tables by different DSCPs.
>
> IMO, these routing tables should represent different and very distinct and differentiated road systems.
> This is only possible, if they are genuine partial structures of the total network. In addition to them we still need
> that "default"-road system which is identical to the entire network (e.g. in order to ping any node), i.e. today's routing tables.
>

[snip]

--
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Fri Aug  2 08:39:35 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16871
	for <routing-discussion-archive@odin.ietf.org>; Fri, 2 Aug 2002 08:39:35 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA11679
	for routing-discussion-archive@odin.ietf.org; Fri, 2 Aug 2002 08:40:46 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA11515;
	Fri, 2 Aug 2002 08:37:50 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA11486
	for <routing-discussion@optimus.ietf.org>; Fri, 2 Aug 2002 08:37:48 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16741
	for <routing-discussion@ietf.org>; Fri, 2 Aug 2002 08:36:36 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id OAA08744;
	Fri, 2 Aug 2002 14:37:42 +0200 (MET DST)
Received: from mchh274e.demchh201e.icn.siemens.de ([139.21.200.84])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id OAA12851;
	Fri, 2 Aug 2002 14:37:43 +0200 (MET DST)
Received: by MCHH274E with Internet Mail Service (5.5.2656.59)
	id <P83C1Y4Q>; Fri, 2 Aug 2002 14:37:07 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B96E@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'jshen@cad.zju.edu.cn'" <jshen@cad.zju.edu.cn>
Cc: Venkata.Naidu@Marconi.com, jnc@ginger.lcs.mit.edu, fred@cisco.com,
        saq66@umkc.edu, irtf-rr@puck.nether.net, routing-discussion@ietf.org
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Fri, 2 Aug 2002 14:37:08 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id IAA11487
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Let me resend this email and correct a stupid tiny error w.r.t. the "smallest size tunnel tree" algorithm.
However, the error highlights an important aspect: For building this tunnel tree, you have to combine two partitions
by means of an entire tunnel between some two VPN-sites which are tunnel endpoints.
No split in the middle of a tunnel will occur.
Where as:
For building a "smallest size tree" - road system
you have to combine two partitions by means of ANY route between these partitions. 
Eventually, one or two completely new branch nodes may be generated at this, at that, or at both partitions.

I will mark the change with  CHANGE***CHANGE and END OF CHANGE*** END OF CHANGE in the text.

Heinrich

-----Ursprščngliche Nachricht-----
Von: Hummel Heinrich [mailto:Heinrich.Hummel@icn.siemens.de]
Gesendet: Freitag, 2. August 2002 13:53
An: 'jshen@cad.zju.edu.cn'
Cc: Venkata.Naidu@Marconi.com; jnc@ginger.lcs.mit.edu; fred@cisco.com; saq66@umkc.edu; irtf-rr@puck.nether.net; routing-discussion@ietf.org
Betreff: AW: Differentiated Routing, not only plain rambo-SPF


Hi Jing,
Find my comments inserted.
Regards
Heinrich 

1) if we want to route with DSCP it should be desired that  logical views of network based on each possible
DSCP is computed ?
HH=>
Yes, this is feasable. IMO, the alternative, that each link advertises all the DSCPs i.e. all the road systems  
it wants to be a part of, is not good eenough for two reasons:
            1) Only by computation we can make sure that each road system is "routable", i.e. enables road system
               internal transport between a particular set of edge routers.
            2) Some road systems are just the overflow-/2nd-best-route, 3rd-best-route road systems w.r.t. another
               road system. This cannot be assured without computation.     


2.)  Each router builds up a seperate routing table for each possible DSCP , and there exist a default routing table
       for packets whose DSCP are not set  ?
HH=>
     Differentiated road systems only make sense, when each of them uses only a part of the network links. A smallest
     size tree between a confined set of edge routers would yield such a "slim" road system. 
     If all your nodes are leaf nodes, then there is no difference between a shortest path tree and a smallest size tree.
     But on the other side, it still must be possible to send a packet from any edge or core router to any edge or core 
     router. I.e. we still need the exisiting best-effort road system. As long as you have only one road system you
     won't have to mark it. But as soon as there is a second one, you have to mark not only the second one 
     but also the first one. Will say you need one DSCP for traffic which shall be forwarded according to the current
     routing tables.

3.)   When a new packet arrives, the dispatching logic may look like :

      Procedure  DSCP_BASED_DISPATCH ( incoming_packet )
            if   DSCP   then
                 if  (  DSCP-related-table-exist )
                     running-table =  DSCP-related-table;

           if  running-table==NULL
                  running-table = default-table;

           out_port= find_routing_item( incoming_packet);
           enqueue(out_port, incoming_packet);

        END PROCEDURE
HH=>
Yes. I see, you already addresses the case where a packet is forwarded NOT as it should, i.e. not within the respective
road system. Of course, this needs to be covered, too. And yes, as you describe, by using the default (best effort) road system.

But, How could the logical view be computed?  DSCP is just for queueing mechanism, should that be included in LSA?

HH=> Life would be easier, if we had more available bits (we still have 2 CU currently unused Bits). But we don't have
64 Service Level Agreements either. It should be possible to satisfy DiffServ as well as DiffRout :-)

And, I think there may other problem as extensiblility and stability.
HH=> Sure. But compare it with DiffServ. DiffServ wasn't done either by one single draft and by one single IETF meeting session.

And,the last , I'm not so clear about the method computing shortest size tree, and I'm very interested in your work of
minimal partial mesh between n sites of a VPN. Would you please give a little more word or some reference sites ?

HH=>   

The idea was to interconnect n sites (PEs or CEs) by a minimal partial mesh of tunnels.It could only be a tree of
n-1 tunnels. And well, a tree of those "shortest" tunnels, which nevertheless interconnect all n sites. In principle,
it is a selection process as to sort out n-1 tunnels from n(n-1)/2 candidate tunnels.Thereafter, add those n-1 
tunnels which are inverse to the selected n-1  tunnels.

Preparation: Compute n Dijkstra-trees whereby each time another site-node becomes the root.As a result you have the best route from any
 
CHANGE***CHANGE

site node to any site node. Here we can ignore those routes which do not start or end at a site node.

END OF CHANGE *** END OF CHANGE

You may sort all of these n(n-1) routes according to their
weight sums in ascending order.And you may associate a REGARD/DISREGARD-Bit to each of these routes (for speeding up the algorithm). Initially set all these Bits to REGARD=1.

Iteration:
As I told already, start out with n (separated) partitions, whereby initially each partition 
just contains  one site-node (no links yet). Also the initial set of tunnels, which finally shall become the
VPN PARTIAL MESH,is empty.
Make n-1 iteration steps.

At each iteration step, determine those two partitions, which can be combined by the shortest route(=tunnel)
among all those routes which are marked REGARD.
 
Combine the two partitions (logically), but in reality do this:
Add this determined shortest route/tunnel to VPN PARTIAL MESH. Set the REGARD/DISREGARD-Bit to DISREGARD=0 for all
those routes, which are "internal" to this combined partition. Note: this includes this shortest route/tunnel.
Precisely set the bit to DISREGARD for all those routes, wherebe the route started at a node from the one partition
and ended at a node from the other partition.

Do this n-1 times.

So far this was all about forming a "minimal size tunnel tree".


Only slightly different would be the algorithm for building what  I used to call a "minimal size multicast tree",
which extends between the sender node and the receiver nodes.

Preparation: 
Compute Dijkstra-trees as many as you have nodes in your network (edge as well as core nodes).
(So you also know the shortest route between any two core nodes as well).Hereby, each time another
node is the root node.

Like above, sort all these routes according to the ascending order of their weight sums, assign a REGARD/DISREGARD-Bit
to each of them, and initialize all these bits to REGARD=1.  

Iteration:
Start with an empty set of routes, called MULTICAST TREE, and with N partitions whereby each partition would only contain one
sender resp. receiver node initially (  for building a road system it would be any edge router 
with attached LAN, Host, ext.interface).

At each iteration step, determine those two partitions, which can be combined by the shortest route between any
node in one partition and any node in another partition. Hereby consider only those routes which are still marked REGARD.
 
Combine the two partitions (logically), but in reality do this:
Add this determined shortest route to MULTICAST TREE. Set the REGARD/DISREGARD-Bit to DISREGARD=0 for all
those routes, which are "internal" to this combined partition. Note: this includes the determined shortest route.
Precisely, set the bit to DISREGARD for all those routes, wherebe the route started at a node from the one partition
and ended at a node from the other partition.

Do this n-1 times.

As a result MULTICAST TREE will contain a list of routes (which are lists of links/nodes).
Or you may look at it in this way: MULTICAST TREE contains a list of links/nodes (which, by chance form a tree graph with
no special (root) node at all).

Take this list of links/nodes as your "basis network topology". And which ever node is part of it may run the most primitive
Dijkstra, i.e. whereby each link-weight is equal to 1, as to compute a tree which spans this tree-topology :-).
By doing so, that node will find out the right adjacent next-hop link with respect to each 
LAN/Host/ext.interface reachability prefix, i.e. can build a respective routing table.

Let's rename MULTICAST TREE to ROAD SYSTEM-for-DSCP "xyz".

It is very important that each node which is part of ROAD SYSTEM-for-DSCP "xyz", has computed the identical set of
links. This means, when, during the iteration, a particular shortest route between some separate partitions is computed,
it must be done in an unambiguous way -  yes, even if there were several equally shortest routes.Tie breaker rules
will be needed.

 


> Let's be concentrated again. And let me get to the heart of the matter.
>
> Obviously I am not the only one who thought about using the DSCP also for doing Differentiated Routing.
> Will say: not the only one who thought about indexing different Routing Tables by different DSCPs.
>
> IMO, these routing tables should represent different and very distinct and differentiated road systems.
> This is only possible, if they are genuine partial structures of the total network. In addition to them we still need
> that "default"-road system which is identical to the entire network (e.g. in order to ping any node), i.e. today's routing tables.
>

[snip]

--
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Fri Aug  2 18:11:32 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09100
	for <routing-discussion-archive@odin.ietf.org>; Fri, 2 Aug 2002 18:11:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA11351;
	Fri, 2 Aug 2002 18:04:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA11323
	for <routing-discussion@optimus.ietf.org>; Fri, 2 Aug 2002 18:04:23 -0400 (EDT)
Received: from psg.com (smmsp@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08789
	for <routing-discussion@ietf.org>; Fri, 2 Aug 2002 18:03:10 -0400 (EDT)
Received: from psg.com ([147.28.0.62] helo=127.0.0.1)
	by psg.com with esmtp (Exim 3.36 #1)
	id 17akWv-000G0b-00
	for routing-discussion@ietf.org; Fri, 02 Aug 2002 15:04:18 -0700
Date: Fri, 2 Aug 2002 15:02:44 -0700
From: Alex Zinin <zinin@psg.com>
X-Mailer: The Bat! (v1.51) Personal
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <623325672.20020802150244@psg.com>
To: routing-discussion@ietf.org
Subject: IETF54: RTG Area minutes for review
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 7bit

Folks:

 Thanks to Eric Gray for taking notes at the meeting.
 Please review the minutes below before I submit them
 to the secretariat.

 Those who showed slides at the meeting, PLEASE submit
 them to minutes@ietf.org as soon as possible. When
 submitted, they can be found at
 http://www.ietf.org/proceedings/02jul/index.html

 Thank you

Alex

-------------------------------------------------------------
Alex (see slides for details):
 - announced creation of RPSEC WG, contributions welcome.
 - announced security advisors: Radia Perlman and Marcus
   Leech. Ran Atkinson is the de facto one as usual.
 - coordination with Sub-IP
 - info on getting drafts to IESG and tips

Provided working group summaries - see slides (except 
for VRRP where no slides were presented):

 BGMP - last meeting in March the WG decided to update
 the specification to mention unicast.  The specification
 was updated in June and there will be a WG last call for
 experimental status.

 IDMR - IGMPv3 specification is in the RFC Editor's queue,
 multicast router discovery needs IPv6 related updates,
 DVMRPv3 needs security work and DVMRPv3 MIB is pending
 completion of DVMRPv3.  The WG will shutdown after the
 specifications are published.

 ISIS - last meeting @ IETF 51, E-Mail migrated from Juniper
 to ietf.org, ~3 years behind original chartered schedule,
 working with IETF WGs (CCAMP, MPLS and TE-WG) and ITU-T.
 Since last meeting, there were 9 draft updates, 3 new 
 drafts and no progressions to RFC.  The WG currently has
 13 drafts and has published 4 (out of 5) IS-IS related
 RFCs since inception.  Current work items include:
 
  o       extending protocol beyond 256 LSP fragments
  o       add administrative tags for MPLS L3 VPNs
  o       extensions for multiple topological scope
  o       graceful restart extensions
  o       interoperability BCP
  o       MIB
  o       discuss relationship with ITU-T SG-15
  o       discuss adding sequence numbers to hellos
  o       discuss extensions for PCS discovery
  o       discuss proprietary TLV code points


 IDR - Sue gave very detailed status information on all IDR
 drafts in progress, including draft names, who has the token,
 status, chartered objective and when they should be complete.  
 See IDR presentation slides for details.  The drafts were 
 grouped as follows:

  o       Base drafts
  o       Oscillation drafts 
  o       Capabilities and MP drafts
  o       AS, ORF and Graceful Restart drafts
  o       Security drafts

 MSDP - discussed the status of work (see slides for details)
 and said that this would be the last meeting for the WG.
 The spec will be published as experimental.

  Q    : Why experimental and not Info?
  Alex : Since we still want people to experiment with it,
         experimental is the right status
 
 OSPF - Alex gave status of 7 drafts (see slide for details).
 
 PIM - status on 3 active drafts (see slides).
 
 SSM - WG status: 2 work items, very quiet members only mail
 list all new SSM work is being done in other WGs.  Draft 
 status: ssm-overview is waiting update after AD review, 
 ssm-arch one minor IPv6 update and then to WG last call.

 UDLR - RFC 3077 published in march, WG re-chartered in June
 to develop case studies. See slides for details of current 
 case study.

 VRRP - No progress, no slides, looking for a new WG chair.

Geoff Huston talked about BGP status in the Internet.  Growth
in route table size seems to be tailing off - more because of
better network designs and lessons learned than because of a
diminishing growth in actual network size.  More information 
is available at http://bgp.potaroo.net

Avri Doria gave a presentation on recent 'Midnight Sun' meeting
that took place in Lulea, Sweden.  See her slides for details.
Papers and workshop reports will be available at:

        http://www.cdt.luth.se/babylon/msrw

Margarett Wassermann showed slides on the IPv6 scoped addressing
support in routing. Margarett is soliciting comments from the
routing community on this issue. 

  Sue Hares thought there were drafts addressing this in BGP
  and that ISIS did not seem to have this problem

  Alex aksed to send the names of the draft to the RTG area
  list and pointed out that the isis-ipv6 draft does not consider
  implications of site-local support.

-------------------------------------------------------------



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Fri Aug  2 18:11:33 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09109
	for <routing-discussion-archive@odin.ietf.org>; Fri, 2 Aug 2002 18:11:33 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA11682
	for routing-discussion-archive@odin.ietf.org; Fri, 2 Aug 2002 18:12:41 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA11351;
	Fri, 2 Aug 2002 18:04:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA11323
	for <routing-discussion@optimus.ietf.org>; Fri, 2 Aug 2002 18:04:23 -0400 (EDT)
Received: from psg.com (smmsp@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08789
	for <routing-discussion@ietf.org>; Fri, 2 Aug 2002 18:03:10 -0400 (EDT)
Received: from psg.com ([147.28.0.62] helo=127.0.0.1)
	by psg.com with esmtp (Exim 3.36 #1)
	id 17akWv-000G0b-00
	for routing-discussion@ietf.org; Fri, 02 Aug 2002 15:04:18 -0700
Date: Fri, 2 Aug 2002 15:02:44 -0700
From: Alex Zinin <zinin@psg.com>
X-Mailer: The Bat! (v1.51) Personal
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <623325672.20020802150244@psg.com>
To: routing-discussion@ietf.org
Subject: IETF54: RTG Area minutes for review
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 7bit

Folks:

 Thanks to Eric Gray for taking notes at the meeting.
 Please review the minutes below before I submit them
 to the secretariat.

 Those who showed slides at the meeting, PLEASE submit
 them to minutes@ietf.org as soon as possible. When
 submitted, they can be found at
 http://www.ietf.org/proceedings/02jul/index.html

 Thank you

Alex

-------------------------------------------------------------
Alex (see slides for details):
 - announced creation of RPSEC WG, contributions welcome.
 - announced security advisors: Radia Perlman and Marcus
   Leech. Ran Atkinson is the de facto one as usual.
 - coordination with Sub-IP
 - info on getting drafts to IESG and tips

Provided working group summaries - see slides (except 
for VRRP where no slides were presented):

 BGMP - last meeting in March the WG decided to update
 the specification to mention unicast.  The specification
 was updated in June and there will be a WG last call for
 experimental status.

 IDMR - IGMPv3 specification is in the RFC Editor's queue,
 multicast router discovery needs IPv6 related updates,
 DVMRPv3 needs security work and DVMRPv3 MIB is pending
 completion of DVMRPv3.  The WG will shutdown after the
 specifications are published.

 ISIS - last meeting @ IETF 51, E-Mail migrated from Juniper
 to ietf.org, ~3 years behind original chartered schedule,
 working with IETF WGs (CCAMP, MPLS and TE-WG) and ITU-T.
 Since last meeting, there were 9 draft updates, 3 new 
 drafts and no progressions to RFC.  The WG currently has
 13 drafts and has published 4 (out of 5) IS-IS related
 RFCs since inception.  Current work items include:
 
  o       extending protocol beyond 256 LSP fragments
  o       add administrative tags for MPLS L3 VPNs
  o       extensions for multiple topological scope
  o       graceful restart extensions
  o       interoperability BCP
  o       MIB
  o       discuss relationship with ITU-T SG-15
  o       discuss adding sequence numbers to hellos
  o       discuss extensions for PCS discovery
  o       discuss proprietary TLV code points


 IDR - Sue gave very detailed status information on all IDR
 drafts in progress, including draft names, who has the token,
 status, chartered objective and when they should be complete.  
 See IDR presentation slides for details.  The drafts were 
 grouped as follows:

  o       Base drafts
  o       Oscillation drafts 
  o       Capabilities and MP drafts
  o       AS, ORF and Graceful Restart drafts
  o       Security drafts

 MSDP - discussed the status of work (see slides for details)
 and said that this would be the last meeting for the WG.
 The spec will be published as experimental.

  Q    : Why experimental and not Info?
  Alex : Since we still want people to experiment with it,
         experimental is the right status
 
 OSPF - Alex gave status of 7 drafts (see slide for details).
 
 PIM - status on 3 active drafts (see slides).
 
 SSM - WG status: 2 work items, very quiet members only mail
 list all new SSM work is being done in other WGs.  Draft 
 status: ssm-overview is waiting update after AD review, 
 ssm-arch one minor IPv6 update and then to WG last call.

 UDLR - RFC 3077 published in march, WG re-chartered in June
 to develop case studies. See slides for details of current 
 case study.

 VRRP - No progress, no slides, looking for a new WG chair.

Geoff Huston talked about BGP status in the Internet.  Growth
in route table size seems to be tailing off - more because of
better network designs and lessons learned than because of a
diminishing growth in actual network size.  More information 
is available at http://bgp.potaroo.net

Avri Doria gave a presentation on recent 'Midnight Sun' meeting
that took place in Lulea, Sweden.  See her slides for details.
Papers and workshop reports will be available at:

        http://www.cdt.luth.se/babylon/msrw

Margarett Wassermann showed slides on the IPv6 scoped addressing
support in routing. Margarett is soliciting comments from the
routing community on this issue. 

  Sue Hares thought there were drafts addressing this in BGP
  and that ISIS did not seem to have this problem

  Alex aksed to send the names of the draft to the RTG area
  list and pointed out that the isis-ipv6 draft does not consider
  implications of site-local support.

-------------------------------------------------------------



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Fri Aug  2 18:38:21 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09949
	for <routing-discussion-archive@odin.ietf.org>; Fri, 2 Aug 2002 18:38:20 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA12714;
	Fri, 2 Aug 2002 18:33:08 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA12685
	for <routing-discussion@optimus.ietf.org>; Fri, 2 Aug 2002 18:33:05 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09750
	for <routing-discussion@ietf.org>; Fri, 2 Aug 2002 18:31:55 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id SAA16977;
	Fri, 2 Aug 2002 18:32:33 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id SAA16310;
	Fri, 2 Aug 2002 18:32:35 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99LR9K>; Fri, 2 Aug 2002 18:32:34 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632A8@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
To: "'Alex Zinin'" <zinin@psg.com>, routing-discussion@ietf.org
Subject: RE: IETF54: RTG Area minutes for review
Date: Fri, 2 Aug 2002 18:32:25 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Alex,

  There is no mention about MANET routing protcols & 
  WG status. Looks like there are enough protocols
  in that area to discuss (other than same good old
  unicast/multicast routing protocols) ;^)

http://www1.ietf.org/mail-archive/working-groups/manet/current/msg00705.html

  Was there any discussion about which of these protocols
  are going to be standardized etc etc ?

--
Venkata.

-> -----Original Message-----
-> From: Alex Zinin [mailto:zinin@psg.com]
-> Sent: Friday, August 02, 2002 6:03 PM
-> To: routing-discussion@ietf.org
-> Subject: IETF54: RTG Area minutes for review
-> 
-> 
-> Folks:
-> 
->  Thanks to Eric Gray for taking notes at the meeting.
->  Please review the minutes below before I submit them
->  to the secretariat.
-> 
->  Those who showed slides at the meeting, PLEASE submit
->  them to minutes@ietf.org as soon as possible. When
->  submitted, they can be found at
->  http://www.ietf.org/proceedings/02jul/index.html
-> 
->  Thank you
-> 
-> Alex
-> 
-> -------------------------------------------------------------
-> Alex (see slides for details):
->  - announced creation of RPSEC WG, contributions welcome.
->  - announced security advisors: Radia Perlman and Marcus
->    Leech. Ran Atkinson is the de facto one as usual.
->  - coordination with Sub-IP
->  - info on getting drafts to IESG and tips
-> 
-> Provided working group summaries - see slides (except 
-> for VRRP where no slides were presented):
-> 
->  BGMP - last meeting in March the WG decided to update
->  the specification to mention unicast.  The specification
->  was updated in June and there will be a WG last call for
->  experimental status.
-> 
->  IDMR - IGMPv3 specification is in the RFC Editor's queue,
->  multicast router discovery needs IPv6 related updates,
->  DVMRPv3 needs security work and DVMRPv3 MIB is pending
->  completion of DVMRPv3.  The WG will shutdown after the
->  specifications are published.
-> 
->  ISIS - last meeting @ IETF 51, E-Mail migrated from Juniper
->  to ietf.org, ~3 years behind original chartered schedule,
->  working with IETF WGs (CCAMP, MPLS and TE-WG) and ITU-T.
->  Since last meeting, there were 9 draft updates, 3 new 
->  drafts and no progressions to RFC.  The WG currently has
->  13 drafts and has published 4 (out of 5) IS-IS related
->  RFCs since inception.  Current work items include:
->  
->   o       extending protocol beyond 256 LSP fragments
->   o       add administrative tags for MPLS L3 VPNs
->   o       extensions for multiple topological scope
->   o       graceful restart extensions
->   o       interoperability BCP
->   o       MIB
->   o       discuss relationship with ITU-T SG-15
->   o       discuss adding sequence numbers to hellos
->   o       discuss extensions for PCS discovery
->   o       discuss proprietary TLV code points
-> 
-> 
->  IDR - Sue gave very detailed status information on all IDR
->  drafts in progress, including draft names, who has the token,
->  status, chartered objective and when they should be complete.  
->  See IDR presentation slides for details.  The drafts were 
->  grouped as follows:
-> 
->   o       Base drafts
->   o       Oscillation drafts 
->   o       Capabilities and MP drafts
->   o       AS, ORF and Graceful Restart drafts
->   o       Security drafts
-> 
->  MSDP - discussed the status of work (see slides for details)
->  and said that this would be the last meeting for the WG.
->  The spec will be published as experimental.
-> 
->   Q    : Why experimental and not Info?
->   Alex : Since we still want people to experiment with it,
->          experimental is the right status
->  
->  OSPF - Alex gave status of 7 drafts (see slide for details).
->  
->  PIM - status on 3 active drafts (see slides).
->  
->  SSM - WG status: 2 work items, very quiet members only mail
->  list all new SSM work is being done in other WGs.  Draft 
->  status: ssm-overview is waiting update after AD review, 
->  ssm-arch one minor IPv6 update and then to WG last call.
-> 
->  UDLR - RFC 3077 published in march, WG re-chartered in June
->  to develop case studies. See slides for details of current 
->  case study.
-> 
->  VRRP - No progress, no slides, looking for a new WG chair.
-> 
-> Geoff Huston talked about BGP status in the Internet.  Growth
-> in route table size seems to be tailing off - more because of
-> better network designs and lessons learned than because of a
-> diminishing growth in actual network size.  More information 
-> is available at http://bgp.potaroo.net
-> 
-> Avri Doria gave a presentation on recent 'Midnight Sun' meeting
-> that took place in Lulea, Sweden.  See her slides for details.
-> Papers and workshop reports will be available at:
-> 
->         http://www.cdt.luth.se/babylon/msrw
-> 
-> Margarett Wassermann showed slides on the IPv6 scoped addressing
-> support in routing. Margarett is soliciting comments from the
-> routing community on this issue. 
-> 
->   Sue Hares thought there were drafts addressing this in BGP
->   and that ISIS did not seem to have this problem
-> 
->   Alex aksed to send the names of the draft to the RTG area
->   list and pointed out that the isis-ipv6 draft does not consider
->   implications of site-local support.
-> 
-> -------------------------------------------------------------
-> 
-> 
-> 
-> _______________________________________________
-> routing-discussion mailing list
-> routing-discussion@ietf.org
-> https://www1.ietf.org/mailman/listinfo/routing-discussion
-> 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Fri Aug  2 18:38:21 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09955
	for <routing-discussion-archive@odin.ietf.org>; Fri, 2 Aug 2002 18:38:21 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA12947
	for routing-discussion-archive@odin.ietf.org; Fri, 2 Aug 2002 18:39:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA12714;
	Fri, 2 Aug 2002 18:33:08 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA12685
	for <routing-discussion@optimus.ietf.org>; Fri, 2 Aug 2002 18:33:05 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09750
	for <routing-discussion@ietf.org>; Fri, 2 Aug 2002 18:31:55 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id SAA16977;
	Fri, 2 Aug 2002 18:32:33 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id SAA16310;
	Fri, 2 Aug 2002 18:32:35 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99LR9K>; Fri, 2 Aug 2002 18:32:34 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632A8@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
To: "'Alex Zinin'" <zinin@psg.com>, routing-discussion@ietf.org
Subject: RE: IETF54: RTG Area minutes for review
Date: Fri, 2 Aug 2002 18:32:25 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Alex,

  There is no mention about MANET routing protcols & 
  WG status. Looks like there are enough protocols
  in that area to discuss (other than same good old
  unicast/multicast routing protocols) ;^)

http://www1.ietf.org/mail-archive/working-groups/manet/current/msg00705.html

  Was there any discussion about which of these protocols
  are going to be standardized etc etc ?

--
Venkata.

-> -----Original Message-----
-> From: Alex Zinin [mailto:zinin@psg.com]
-> Sent: Friday, August 02, 2002 6:03 PM
-> To: routing-discussion@ietf.org
-> Subject: IETF54: RTG Area minutes for review
-> 
-> 
-> Folks:
-> 
->  Thanks to Eric Gray for taking notes at the meeting.
->  Please review the minutes below before I submit them
->  to the secretariat.
-> 
->  Those who showed slides at the meeting, PLEASE submit
->  them to minutes@ietf.org as soon as possible. When
->  submitted, they can be found at
->  http://www.ietf.org/proceedings/02jul/index.html
-> 
->  Thank you
-> 
-> Alex
-> 
-> -------------------------------------------------------------
-> Alex (see slides for details):
->  - announced creation of RPSEC WG, contributions welcome.
->  - announced security advisors: Radia Perlman and Marcus
->    Leech. Ran Atkinson is the de facto one as usual.
->  - coordination with Sub-IP
->  - info on getting drafts to IESG and tips
-> 
-> Provided working group summaries - see slides (except 
-> for VRRP where no slides were presented):
-> 
->  BGMP - last meeting in March the WG decided to update
->  the specification to mention unicast.  The specification
->  was updated in June and there will be a WG last call for
->  experimental status.
-> 
->  IDMR - IGMPv3 specification is in the RFC Editor's queue,
->  multicast router discovery needs IPv6 related updates,
->  DVMRPv3 needs security work and DVMRPv3 MIB is pending
->  completion of DVMRPv3.  The WG will shutdown after the
->  specifications are published.
-> 
->  ISIS - last meeting @ IETF 51, E-Mail migrated from Juniper
->  to ietf.org, ~3 years behind original chartered schedule,
->  working with IETF WGs (CCAMP, MPLS and TE-WG) and ITU-T.
->  Since last meeting, there were 9 draft updates, 3 new 
->  drafts and no progressions to RFC.  The WG currently has
->  13 drafts and has published 4 (out of 5) IS-IS related
->  RFCs since inception.  Current work items include:
->  
->   o       extending protocol beyond 256 LSP fragments
->   o       add administrative tags for MPLS L3 VPNs
->   o       extensions for multiple topological scope
->   o       graceful restart extensions
->   o       interoperability BCP
->   o       MIB
->   o       discuss relationship with ITU-T SG-15
->   o       discuss adding sequence numbers to hellos
->   o       discuss extensions for PCS discovery
->   o       discuss proprietary TLV code points
-> 
-> 
->  IDR - Sue gave very detailed status information on all IDR
->  drafts in progress, including draft names, who has the token,
->  status, chartered objective and when they should be complete.  
->  See IDR presentation slides for details.  The drafts were 
->  grouped as follows:
-> 
->   o       Base drafts
->   o       Oscillation drafts 
->   o       Capabilities and MP drafts
->   o       AS, ORF and Graceful Restart drafts
->   o       Security drafts
-> 
->  MSDP - discussed the status of work (see slides for details)
->  and said that this would be the last meeting for the WG.
->  The spec will be published as experimental.
-> 
->   Q    : Why experimental and not Info?
->   Alex : Since we still want people to experiment with it,
->          experimental is the right status
->  
->  OSPF - Alex gave status of 7 drafts (see slide for details).
->  
->  PIM - status on 3 active drafts (see slides).
->  
->  SSM - WG status: 2 work items, very quiet members only mail
->  list all new SSM work is being done in other WGs.  Draft 
->  status: ssm-overview is waiting update after AD review, 
->  ssm-arch one minor IPv6 update and then to WG last call.
-> 
->  UDLR - RFC 3077 published in march, WG re-chartered in June
->  to develop case studies. See slides for details of current 
->  case study.
-> 
->  VRRP - No progress, no slides, looking for a new WG chair.
-> 
-> Geoff Huston talked about BGP status in the Internet.  Growth
-> in route table size seems to be tailing off - more because of
-> better network designs and lessons learned than because of a
-> diminishing growth in actual network size.  More information 
-> is available at http://bgp.potaroo.net
-> 
-> Avri Doria gave a presentation on recent 'Midnight Sun' meeting
-> that took place in Lulea, Sweden.  See her slides for details.
-> Papers and workshop reports will be available at:
-> 
->         http://www.cdt.luth.se/babylon/msrw
-> 
-> Margarett Wassermann showed slides on the IPv6 scoped addressing
-> support in routing. Margarett is soliciting comments from the
-> routing community on this issue. 
-> 
->   Sue Hares thought there were drafts addressing this in BGP
->   and that ISIS did not seem to have this problem
-> 
->   Alex aksed to send the names of the draft to the RTG area
->   list and pointed out that the isis-ipv6 draft does not consider
->   implications of site-local support.
-> 
-> -------------------------------------------------------------
-> 
-> 
-> 
-> _______________________________________________
-> routing-discussion mailing list
-> routing-discussion@ietf.org
-> https://www1.ietf.org/mailman/listinfo/routing-discussion
-> 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Sat Aug  3 01:39:18 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18653
	for <routing-discussion-archive@odin.ietf.org>; Sat, 3 Aug 2002 01:39:18 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA05693;
	Sat, 3 Aug 2002 01:22:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA29142
	for <routing-discussion@ns.ietf.org>; Fri, 2 Aug 2002 03:49:01 -0400 (EDT)
Received: from mail.cad.zju.edu.cn (cad.zju.edu.cn [210.32.131.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA10692
	for <routing-discussion@ietf.org>; Fri, 2 Aug 2002 03:47:40 -0400 (EDT)
Received: (qmail 12597 invoked from network); 2 Aug 2002 07:53:34 -0000
Received: from unknown (HELO cad.zju.edu.cn) (210.32.131.97)
  by 210.32.131.2 with SMTP; 2 Aug 2002 07:53:34 -0000
Message-ID: <3D4A393F.AFB28274@cad.zju.edu.cn>
Date: Fri, 02 Aug 2002 15:48:15 +0800
From: shen jing <jshen@cad.zju.edu.cn>
Reply-To: jshen@cad.zju.edu.cn
Organization: State Key Lab of CAD&CG
X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
CC: jshen@cad.zju.edu.cn, Venkata.Naidu@Marconi.com, jnc@ginger.lcs.mit.edu,
        fred@cisco.com, saq66@umkc.edu, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: Re: Differentiated Routing, not only plain rambo-SPF
References: <EF8E39AA846CD411BB9C00508B951F510514B95B@MCHH267E>
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 7bit

Hi Hummel,

Do you means,

1) if we want to route with DSCP it should be desired that  logical views of network based on each possible
DSCP is computed ?


2.)  Each router builds up a seperate routing table for each possible DSCP , and there exist a default routing table
       for packets whose DSCP are not set  ?

3.)   When a new packet arrives, the dispatching logic may look like :

      Procedure  DSCP_BASED_DISPATCH ( incoming_packet )
            if   DSCP   then
                 if  (  DSCP-related-table-exist )
                     running-table =  DSCP-related-table;

           if  running-table==NULL
                  running-table = default-table;

           out_port= find_routing_item( incoming_packet);
           enqueue(out_port, incoming_packet);

        END PROCEDURE

But, How could the logical view be computed?  DSCP is just for queueing mechanism, should that be included in LSA?

And, I think there may other problem as extensiblility and stability.

And,the last , I'm not so clear about the method computing shortest size tree, and I'm very interested in your work of
minimal partial mesh between n sites of a VPN. Would you please give a little more word or some reference sites ?

Thank  you .

Regards




> Let's be concentrated again. And let me get to the heart of the matter.
>
> Obviously I am not the only one who thought about using the DSCP also for doing Differentiated Routing.
> Will say: not the only one who thought about indexing different Routing Tables by different DSCPs.
>
> IMO, these routing tables should represent different and very distinct and differentiated road systems.
> This is only possible, if they are genuine partial structures of the total network. In addition to them we still need
> that "default"-road system which is identical to the entire network (e.g. in order to ping any node), i.e. today's routing tables.
>

[snip]

--
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************





_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Sat Aug  3 01:39:19 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18666
	for <routing-discussion-archive@odin.ietf.org>; Sat, 3 Aug 2002 01:39:19 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA06616
	for routing-discussion-archive@odin.ietf.org; Sat, 3 Aug 2002 01:40:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA05693;
	Sat, 3 Aug 2002 01:22:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA29142
	for <routing-discussion@ns.ietf.org>; Fri, 2 Aug 2002 03:49:01 -0400 (EDT)
Received: from mail.cad.zju.edu.cn (cad.zju.edu.cn [210.32.131.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA10692
	for <routing-discussion@ietf.org>; Fri, 2 Aug 2002 03:47:40 -0400 (EDT)
Received: (qmail 12597 invoked from network); 2 Aug 2002 07:53:34 -0000
Received: from unknown (HELO cad.zju.edu.cn) (210.32.131.97)
  by 210.32.131.2 with SMTP; 2 Aug 2002 07:53:34 -0000
Message-ID: <3D4A393F.AFB28274@cad.zju.edu.cn>
Date: Fri, 02 Aug 2002 15:48:15 +0800
From: shen jing <jshen@cad.zju.edu.cn>
Reply-To: jshen@cad.zju.edu.cn
Organization: State Key Lab of CAD&CG
X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
CC: jshen@cad.zju.edu.cn, Venkata.Naidu@Marconi.com, jnc@ginger.lcs.mit.edu,
        fred@cisco.com, saq66@umkc.edu, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: Re: Differentiated Routing, not only plain rambo-SPF
References: <EF8E39AA846CD411BB9C00508B951F510514B95B@MCHH267E>
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 7bit

Hi Hummel,

Do you means,

1) if we want to route with DSCP it should be desired that  logical views of network based on each possible
DSCP is computed ?


2.)  Each router builds up a seperate routing table for each possible DSCP , and there exist a default routing table
       for packets whose DSCP are not set  ?

3.)   When a new packet arrives, the dispatching logic may look like :

      Procedure  DSCP_BASED_DISPATCH ( incoming_packet )
            if   DSCP   then
                 if  (  DSCP-related-table-exist )
                     running-table =  DSCP-related-table;

           if  running-table==NULL
                  running-table = default-table;

           out_port= find_routing_item( incoming_packet);
           enqueue(out_port, incoming_packet);

        END PROCEDURE

But, How could the logical view be computed?  DSCP is just for queueing mechanism, should that be included in LSA?

And, I think there may other problem as extensiblility and stability.

And,the last , I'm not so clear about the method computing shortest size tree, and I'm very interested in your work of
minimal partial mesh between n sites of a VPN. Would you please give a little more word or some reference sites ?

Thank  you .

Regards




> Let's be concentrated again. And let me get to the heart of the matter.
>
> Obviously I am not the only one who thought about using the DSCP also for doing Differentiated Routing.
> Will say: not the only one who thought about indexing different Routing Tables by different DSCPs.
>
> IMO, these routing tables should represent different and very distinct and differentiated road systems.
> This is only possible, if they are genuine partial structures of the total network. In addition to them we still need
> that "default"-road system which is identical to the entire network (e.g. in order to ping any node), i.e. today's routing tables.
>

[snip]

--
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************





_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Sat Aug  3 01:56:49 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18932
	for <routing-discussion-archive@odin.ietf.org>; Sat, 3 Aug 2002 01:56:48 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA06762;
	Sat, 3 Aug 2002 01:43:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA06732
	for <routing-discussion@optimus.ietf.org>; Sat, 3 Aug 2002 01:43:23 -0400 (EDT)
Received: from psg.com (smmsp@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18748
	for <routing-discussion@ietf.org>; Sat, 3 Aug 2002 01:42:11 -0400 (EDT)
Received: from psg.com ([147.28.0.62] helo=127.0.0.1)
	by psg.com with esmtp (Exim 3.36 #1)
	id 17arh9-000Php-00; Fri, 02 Aug 2002 22:43:19 -0700
Date: Fri, 2 Aug 2002 22:41:54 -0700
From: Alex Zinin <zinin@psg.com>
X-Mailer: The Bat! (v1.51) Personal
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <2930876508.20020802224154@psg.com>
To: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
CC: routing-discussion@ietf.org
Subject: Re: IETF54: RTG Area minutes for review
In-Reply-To: <39469E08BD83D411A3D900204840EC557632A8@vie-msgusr-01.dc.fore.com>
References: <39469E08BD83D411A3D900204840EC557632A8@vie-msgusr-01.dc.fore.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 7bit

Venkata,

> Alex,

>   There is no mention about MANET routing protcols & 
>   WG status.

Good catch. Charlie actually provided an update.
I'll put this in the notes and we should expect
Charlie to submit his slides.


> Looks like there are enough protocols
>   in that area to discuss (other than same good old
>   unicast/multicast routing protocols) ;^)

> http://www1.ietf.org/mail-archive/working-groups/manet/current/msg00705.html

Hopefully we do not have so many candidates :)

>   Was there any discussion about which of these protocols
>   are going to be standardized etc etc ?

No, there was no discussion on this. We are working
on this question, and should have a more concrete
plan by the next meeting.

Thanks.
Alex



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Sat Aug  3 01:56:49 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18940
	for <routing-discussion-archive@odin.ietf.org>; Sat, 3 Aug 2002 01:56:49 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA07175
	for routing-discussion-archive@odin.ietf.org; Sat, 3 Aug 2002 01:58:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA06762;
	Sat, 3 Aug 2002 01:43:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA06732
	for <routing-discussion@optimus.ietf.org>; Sat, 3 Aug 2002 01:43:23 -0400 (EDT)
Received: from psg.com (smmsp@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18748
	for <routing-discussion@ietf.org>; Sat, 3 Aug 2002 01:42:11 -0400 (EDT)
Received: from psg.com ([147.28.0.62] helo=127.0.0.1)
	by psg.com with esmtp (Exim 3.36 #1)
	id 17arh9-000Php-00; Fri, 02 Aug 2002 22:43:19 -0700
Date: Fri, 2 Aug 2002 22:41:54 -0700
From: Alex Zinin <zinin@psg.com>
X-Mailer: The Bat! (v1.51) Personal
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <2930876508.20020802224154@psg.com>
To: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
CC: routing-discussion@ietf.org
Subject: Re: IETF54: RTG Area minutes for review
In-Reply-To: <39469E08BD83D411A3D900204840EC557632A8@vie-msgusr-01.dc.fore.com>
References: <39469E08BD83D411A3D900204840EC557632A8@vie-msgusr-01.dc.fore.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 7bit

Venkata,

> Alex,

>   There is no mention about MANET routing protcols & 
>   WG status.

Good catch. Charlie actually provided an update.
I'll put this in the notes and we should expect
Charlie to submit his slides.


> Looks like there are enough protocols
>   in that area to discuss (other than same good old
>   unicast/multicast routing protocols) ;^)

> http://www1.ietf.org/mail-archive/working-groups/manet/current/msg00705.html

Hopefully we do not have so many candidates :)

>   Was there any discussion about which of these protocols
>   are going to be standardized etc etc ?

No, there was no discussion on this. We are working
on this question, and should have a more concrete
plan by the next meeting.

Thanks.
Alex



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 05:19:40 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05672
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 05:19:40 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA19600;
	Mon, 5 Aug 2002 05:06:32 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA19569
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 05:06:26 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05464
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 05:05:12 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id LAA05700;
	Mon, 5 Aug 2002 11:06:09 +0200 (MET DST)
Received: from mchh273e.demchh201e.icn.siemens.de ([139.21.200.83])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id LAA22325;
	Mon, 5 Aug 2002 11:06:10 +0200 (MET DST)
Received: by MCHH273E with Internet Mail Service (5.5.2656.59)
	id <P71Q02GM>; Mon, 5 Aug 2002 11:05:55 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B977@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'senthil ayyasamy'" <mplsgeek@yahoo.com>,
        "'venumadhav josyula'"
	 <venu_m_j@yahoo.com>,
        "'sven.van_den_bosch@alcatel.be'"
	 <sven.van_den_bosch@alcatel.be>
Cc: "'Andrew Walding'" <andy@cellstream.com>,
        "'kbenjamin@zvolve.com'"
	 <kbenjamin@zvolve.com>,
        "'routing-discussion@ietf.org'"
	 <routing-discussion@ietf.org>
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 11:05:51 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id FAA19570
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

From  [MPLS-OPS]: MPLS Debacle back to [routing-discussion]:Differentiated Routing, not only plain rambo-SPF
 

Senthil,
This email of yours as well as your previous one only confirms my statement, that
the entire Internet community  (or at least you and some others) is the prisoner of this rambo-SPF routing algorithm.
All the protocols you have enlisted (...,BW inversion SP,...PNNI,..) and let me also add
the reverse SPF in some multicast models, share this egocentric  SPF view.

I am    N O T     talking just another brand of rambo-SPF.

Also, it wouldn't be helpful to follow your advice (come up with requirements, application statements,...)
because if I did you would read all of it with your SPF-centric view in mind. You even do so now, after
I have explained how each router may aquire the identical view of some road system.

Another analogy: 
When you fly to some meeting place, you may get a flyer-map at the hotel concierge. The flyer-maps may be the same
no matter at which hotel you stay. But, eventually, they have a different "You are Here" markation depending on
the specific hotel. I am looking at the propagated road systems by a commonly shared view first, then I respect the
different "you are here" markation. Rambo-SPF however means:"I am here.I see the world only from my point of view."
Taking into consideration any kind of constraints and whichever weights doesn't change anything of this egocentric
view + behavior with all its disadvantages.


Heinrich

-----Ursprüngliche Nachricht-----
Von: senthil ayyasamy [mailto:mplsgeek@yahoo.com]
Gesendet: Samstag, 3. August 2002 09:40
An: venumadhav josyula; Hummel Heinrich;
'sven.van_den_bosch@alcatel.be'; mpls-ops-request@mplsrc.com
Cc: Andrew Walding; kbenjamin@zvolve.com; mpls-ops@mplsrc.com
Betreff: Re: AW: [MPLS-OPS]: MPLS Debacle



> See how many
> QoS
> > routing schemes were proposed, researched and not
> > deployed. See what is the problem with those
> routing
> > Variants and then suggest differential routing
> > Scheme.
> >
> Ok tell me why would not such a scheme work?
Where I mentioned  *differential routing* wont
work. Proposing new ideas are always easy. Let me 
illustrate with an example.

SPF+ variants of SP algo (widest SP, shortest widest
bandwidth path, bw inversion SP, ...)+ optimal
multipath+source routing+ loose source routing+
explicit paths (MPLS)+ k-shortest path and its
variants+QoS routing( load sensitive,delay sensitive,
single metric based,multi-metric based) +OSPF
extensions+ all dynamic routing schemes as mentioned 
in Ash book+PNNI + all frame relay and other type of
routing+ MPLS based (constrianed or whatever)+ overlay
based routing+ onion routing+hot potato+ cold potato
routing+...

I have listed a *few* unicast routing schemes. I can
list more routing Schemes taking multicast, any cast
into picture... leave alone ad-hoc, host mobility,
network mobility, topology independent ...so on..

Most of the above routing schemes are subsets of some
of the listed schemes. So suggesting a new routing
scheme is not a big work. Using a simple combination
and taking  some new technologies into picture, one
can come up with a new routing scheme. But frankly
that's not a correct approach for any protocol
developed in IETF.

You should exactly come up with:
- Requirements
- Applicability statement
- What problems the current schemes did not solve
which lead you to suggest the present routing scheme.
- What is the over-head when compared to the other
existing technologies??? Usegood simulation to prove
them.
- A theoretical model to prove its use by means of
routing problem formulations
- Some case studies.
- Study their properties (scalability, flexibility and
extendibility.)
- What all places it is most useful or waste
(inter-domain or intra-domain)
- Does it conform with the architectural principle
(this is important: e.g.. Scalability alone is not the
reason for intserv non-usage. It did not work within
boundaries (AS.) alone.It can transcend an autonomous
system boundary and so policy cannot be maintained.
Hence, it did not support the business models well.) 

Now come to IETF. Give an engineering perspective to
your routing scheme. Convince vendors to implement
your routing scheme.

It is sometimes unfortunate that people just come up
with some X routing scheme and try to convince
engineering folks. Some of the IETF works was just
proposals and hence did not succeed or gave problems
at the later stage. So do all the above work for your
new scheme and then everyone will accept your
proposal.

Read the below book on how well the author approach
such new schemes. 
 *G. R. Ash. Dynamic Routing in Telecommunications
Networks. McGraw Hill, New York, 1998*
This is the book, which introduced dynamic routing
schemes. It is not just bunch of ideas but has a
in-depth analysis of requirements and theory.


> CSPF (Constraint based shortest path) which is a
> kind
> of differential routing. I have some discussion in
> this thread itself on that respect. 
> Constraint based routing is modification of shortest
> path alo to account for contraints such as (BW ,
> QOS,
> policy). 

I accept this scheme. There are simulation and
mathematical work to see its behavior. But what it
lacks is *deployment* which we cannot help.
There might be lot of operational and business policy
factors associated.

> CSPF solution is quite popular many are implementing
> it , but I am not sure deployment and
> interoperatablity concerns......... CSPF answers QOS
> routing concerns (correct if i am wrong). It is not
> the all of the mechanims proposed are failure.......

Note: I could not resist and hence replied. But if
your care to respond to this mail, reply to general
routing discussion than MPLS list.

__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-admin@ietf.org  Mon Aug  5 06:07:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06556
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 06:07:53 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA22343;
	Mon, 5 Aug 2002 06:02:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA22315
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 06:02:39 -0400 (EDT)
Received: from kc-msxproto2.kc.umkc.edu (kc-msxproto2.kc.umkc.edu [134.193.143.159])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06411
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 06:01:27 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 5 Aug 2002 05:02:38 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 05:02:37 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C2521@KC-MAIL2.kc.umkc.edu>
Thread-Topic: RE: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcI8ZzoFBPJ8W16ZTKmmtn1KY9eESA==
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>
Cc: <Venkata.Naidu@marconi.com>, <jnc@ginger.lcs.mit.edu>, <fred@cisco.com>,
        <irtf-rr@puck.nether.net>, <routing-discussion@ietf.org>
X-OriginalArrivalTime: 05 Aug 2002 10:02:38.0791 (UTC) FILETIME=[3AF02570:01C23C67]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id GAA22316
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

-- Hummel Heinrich <Heinrich.Hummel@icn.siemens.de> 
wrote: > From  [MPLS-OPS]: MPLS Debacle back to
> [routing-discussion]:Differentiated Routing, not
> only plain rambo-SPF
>  
> 
> Senthil,
> This email of yours as well as your previous one
> only confirms my statement, that
> the entire Internet community  (or at least you and
> some others) is the prisoner of this rambo-SPF
> routing algorithm.
> All the protocols you have enlisted (...,BW
> inversion SP,...PNNI,..) and let me also add
> the reverse SPF in some multicast models, share this
> egocentric  SPF view.

> I am    N O T     talking just another brand of
> rambo-SPF.

My .02$:

1. The diffserv architecture, as of now, defines only 
the data plane work.  control plane activities( routing,
signaling etc)  are still open questions. 
 My argument is contradictory to what you suggest:
An effective load balancing in diffserv can be done 
by taking SPF algo into consideration. The NP-hardness 
in the existing *routing problem* formulations can be 
be approximated to polynomial time effectively by taking
both diffserv and SPF into consideration(as paths are 
predictable in a diffserv domain. )
 Most of the current routing problems formulations 
are solved by means of heuristic methods. But one can 
approximate to polynomial time by taking both SPF and 
diffserv into consideration.

Note: I am just tossing an idea. I will update you 
all once i get some good results.

2.[ some diffrout def from the discussion]

*Certainly, the basic idea of DiffRout is to use 
the DSCP-Bits, or even all 8 TOS-bits, for addressing 
different Routing Tables for looking up the next hop 
link (you can as well have one common Routing Table 
but search for the right entry while using destination 
address AND DSCP as search keys - this is up to the 
programmer).*

*In normal, state-less IP routing we cannot do 
QoS-Routing, nor sneak-around the congestion-area 
routing, nor traffic balanced routing. Instead, all 
of this is left to MPLS, where multiple states and 
multiple LSPs and multiple signalling is required.
With other words:I try to enable QoS-Routing, 
"sneak-around the congestion-area" -Routing, 
traffic balanced -Routing.*

*the intersection of all the subsets (ie., 
(QoS using MPLS-(DiffServ-Aware-TE) will make 
a *real-good* impact on end-to-end performance 
in the global Internet*   

Do me a favor. Replace the term  *DSCP* with 
*CoS* and *Diffserv* with *MPLS * in the above 
definition, you can call your new routing
scheme as *multi-protocol routing*. 
( humorous aside: Tips from a networking insider 
http://www.cs.ucsd.edu/~savage/papers/OO01.pdf :-) )

Thus said, coming with a new scheme is not a big task,
problem space and applicability statement is very 
important.

Read *An Overview of the New Routing Algorithm for 
the ARPANET, J. M. McQuillan, I. Richter, E. C. Rosen 
(Proc. Sixth Data Comm.Symposium, November 1979)*
http://www.acm.org/sigcomm/ccr/archive/1995/jan95/ccr-9501-mcquilln.pdf 

The above work marked the begining of transition from 
the old ARPANET distributed routing algorithms to 
SPF. The authors start with the *problems with the 
original algorithm*, then *need for SPF* and convinces 
the network floks that *SPF is just an increment to 
the original algorithm*. 

I am not asking you to formulate diffrout as an increment 
to SPF but just enlighten us *problem* and *need* of 
diffrout.

- Senthil.


> 
> Also, it wouldn't be helpful to follow your advice
> (come up with requirements, application
> statements,...)
> because if I did you would read all of it with your
> SPF-centric view in mind. You even do so now, after
> I have explained how each router may aquire the
> identical view of some road system.
> 
> Another analogy: 
> When you fly to some meeting place, you may get a
> flyer-map at the hotel concierge. The flyer-maps may
> be the same
> no matter at which hotel you stay. But, eventually,
> they have a different "You are Here" markation
> depending on
> the specific hotel. I am looking at the propagated
> road systems by a commonly shared view first, then I
> respect the
> different "you are here" markation. Rambo-SPF
> however means:"I am here.I see the world only from
> my point of view."
> Taking into consideration any kind of constraints
> and whichever weights doesn't change anything of
> this egocentric
> view + behavior with all its disadvantages.
> 
> 
> Heinrich
> 
> -----Ursprüngliche Nachricht-----
> Von: senthil ayyasamy [mailto:mplsgeek@yahoo.com]
> Gesendet: Samstag, 3. August 2002 09:40
> An: venumadhav josyula; Hummel Heinrich;
> 'sven.van_den_bosch@alcatel.be';
> mpls-ops-request@mplsrc.com
> Cc: Andrew Walding; kbenjamin@zvolve.com;
> mpls-ops@mplsrc.com
> Betreff: Re: AW: [MPLS-OPS]: MPLS Debacle
> 
> 
> 
> > See how many
> > QoS
> > > routing schemes were proposed, researched and
> not
> > > deployed. See what is the problem with those
> > routing
> > > Variants and then suggest differential routing
> > > Scheme.
> > >
> > Ok tell me why would not such a scheme work?
> Where I mentioned  *differential routing* wont
> work. Proposing new ideas are always easy. Let me 
> illustrate with an example.
> 
> SPF+ variants of SP algo (widest SP, shortest widest
> bandwidth path, bw inversion SP, ...)+ optimal
> multipath+source routing+ loose source routing+
> explicit paths (MPLS)+ k-shortest path and its
> variants+QoS routing( load sensitive,delay
> sensitive,
> single metric based,multi-metric based) +OSPF
> extensions+ all dynamic routing schemes as mentioned
> 
> in Ash book+PNNI + all frame relay and other type of
> routing+ MPLS based (constrianed or whatever)+
> overlay
> based routing+ onion routing+hot potato+ cold potato
> routing+...
> 
> I have listed a *few* unicast routing schemes. I can
> list more routing Schemes taking multicast, any cast
> into picture... leave alone ad-hoc, host mobility,
> network mobility, topology independent ...so on..
> 
> Most of the above routing schemes are subsets of
> some
> of the listed schemes. So suggesting a new routing
> scheme is not a big work. Using a simple combination
> and taking  some new technologies into picture, one
> can come up with a new routing scheme. But frankly
> that's not a correct approach for any protocol
> developed in IETF.
> 
> You should exactly come up with:
> - Requirements
> - Applicability statement
> - What problems the current schemes did not solve
> which lead you to suggest the present routing
> scheme.
> - What is the over-head when compared to the other
> existing technologies??? Usegood simulation to prove
> them.
> - A theoretical model to prove its use by means of
> routing problem formulations
> - Some case studies.
> - Study their properties (scalability, flexibility
> and
> extendibility.)
> - What all places it is most useful or waste
> (inter-domain or intra-domain)
> - Does it conform with the architectural principle
> (this is important: e.g.. Scalability alone is not
> the
> reason for intserv non-usage. It did not work within
> boundaries (AS.) alone.It can transcend an
> autonomous
> system boundary and so policy cannot be maintained.
> Hence, it did not support the business models well.)
> 
> 
> Now come to IETF. Give an engineering perspective to
> your routing scheme. Convince vendors to implement
> your routing scheme.
> 
> It is sometimes unfortunate that people just come up
> with some X routing scheme and try to convince
> engineering folks. Some of the IETF works was just
> proposals and hence did not succeed or gave problems
> at the later stage. So do all the above work for
> your
> new scheme and then everyone will accept your
> proposal.
> 
> Read the below book on how well the author approach
> such new schemes. 
>  *G. R. Ash. Dynamic Routing in Telecommunications
> Networks. McGraw Hill, New York, 1998*
> This is the book, which introduced dynamic routing
> schemes. It is not just bunch of ideas but has a
> in-depth analysis of requirements and theory.
> 
> 
> > CSPF (Constraint based shortest path) which is a
> > kind
> > of differential routing. I have some discussion in
> > this thread itself on that respect. 
> > Constraint based routing is modification of
> shortest
> > path alo to account for contraints such as (BW ,
> > QOS,
> > policy). 
> 
> I accept this scheme. There are simulation and
> mathematical work to see its behavior. But what it
> lacks is *deployment* which we cannot help.
> There might be lot of operational and business
> policy
> factors associated.
> 
> > CSPF solution is quite popular many are
> implementing
> > it , but I am not sure deployment and
> > interoperatablity concerns......... CSPF answers
> QOS
> > routing concerns (correct if i am wrong). It is
> not
> > the all of the mechanims proposed are
> failure.......
> 
> Note: I could not resist and hence replied. But if
> your care to respond to this mail, reply to general
> routing discussion than MPLS list.
> 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 06:07:54 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06565
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 06:07:53 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA22985
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 06:09:05 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA22343;
	Mon, 5 Aug 2002 06:02:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA22315
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 06:02:39 -0400 (EDT)
Received: from kc-msxproto2.kc.umkc.edu (kc-msxproto2.kc.umkc.edu [134.193.143.159])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06411
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 06:01:27 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 5 Aug 2002 05:02:38 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 05:02:37 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C2521@KC-MAIL2.kc.umkc.edu>
Thread-Topic: RE: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcI8ZzoFBPJ8W16ZTKmmtn1KY9eESA==
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>
Cc: <Venkata.Naidu@marconi.com>, <jnc@ginger.lcs.mit.edu>, <fred@cisco.com>,
        <irtf-rr@puck.nether.net>, <routing-discussion@ietf.org>
X-OriginalArrivalTime: 05 Aug 2002 10:02:38.0791 (UTC) FILETIME=[3AF02570:01C23C67]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id GAA22316
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

-- Hummel Heinrich <Heinrich.Hummel@icn.siemens.de> 
wrote: > From  [MPLS-OPS]: MPLS Debacle back to
> [routing-discussion]:Differentiated Routing, not
> only plain rambo-SPF
>  
> 
> Senthil,
> This email of yours as well as your previous one
> only confirms my statement, that
> the entire Internet community  (or at least you and
> some others) is the prisoner of this rambo-SPF
> routing algorithm.
> All the protocols you have enlisted (...,BW
> inversion SP,...PNNI,..) and let me also add
> the reverse SPF in some multicast models, share this
> egocentric  SPF view.

> I am    N O T     talking just another brand of
> rambo-SPF.

My .02$:

1. The diffserv architecture, as of now, defines only 
the data plane work.  control plane activities( routing,
signaling etc)  are still open questions. 
 My argument is contradictory to what you suggest:
An effective load balancing in diffserv can be done 
by taking SPF algo into consideration. The NP-hardness 
in the existing *routing problem* formulations can be 
be approximated to polynomial time effectively by taking
both diffserv and SPF into consideration(as paths are 
predictable in a diffserv domain. )
 Most of the current routing problems formulations 
are solved by means of heuristic methods. But one can 
approximate to polynomial time by taking both SPF and 
diffserv into consideration.

Note: I am just tossing an idea. I will update you 
all once i get some good results.

2.[ some diffrout def from the discussion]

*Certainly, the basic idea of DiffRout is to use 
the DSCP-Bits, or even all 8 TOS-bits, for addressing 
different Routing Tables for looking up the next hop 
link (you can as well have one common Routing Table 
but search for the right entry while using destination 
address AND DSCP as search keys - this is up to the 
programmer).*

*In normal, state-less IP routing we cannot do 
QoS-Routing, nor sneak-around the congestion-area 
routing, nor traffic balanced routing. Instead, all 
of this is left to MPLS, where multiple states and 
multiple LSPs and multiple signalling is required.
With other words:I try to enable QoS-Routing, 
"sneak-around the congestion-area" -Routing, 
traffic balanced -Routing.*

*the intersection of all the subsets (ie., 
(QoS using MPLS-(DiffServ-Aware-TE) will make 
a *real-good* impact on end-to-end performance 
in the global Internet*   

Do me a favor. Replace the term  *DSCP* with 
*CoS* and *Diffserv* with *MPLS * in the above 
definition, you can call your new routing
scheme as *multi-protocol routing*. 
( humorous aside: Tips from a networking insider 
http://www.cs.ucsd.edu/~savage/papers/OO01.pdf :-) )

Thus said, coming with a new scheme is not a big task,
problem space and applicability statement is very 
important.

Read *An Overview of the New Routing Algorithm for 
the ARPANET, J. M. McQuillan, I. Richter, E. C. Rosen 
(Proc. Sixth Data Comm.Symposium, November 1979)*
http://www.acm.org/sigcomm/ccr/archive/1995/jan95/ccr-9501-mcquilln.pdf 

The above work marked the begining of transition from 
the old ARPANET distributed routing algorithms to 
SPF. The authors start with the *problems with the 
original algorithm*, then *need for SPF* and convinces 
the network floks that *SPF is just an increment to 
the original algorithm*. 

I am not asking you to formulate diffrout as an increment 
to SPF but just enlighten us *problem* and *need* of 
diffrout.

- Senthil.


> 
> Also, it wouldn't be helpful to follow your advice
> (come up with requirements, application
> statements,...)
> because if I did you would read all of it with your
> SPF-centric view in mind. You even do so now, after
> I have explained how each router may aquire the
> identical view of some road system.
> 
> Another analogy: 
> When you fly to some meeting place, you may get a
> flyer-map at the hotel concierge. The flyer-maps may
> be the same
> no matter at which hotel you stay. But, eventually,
> they have a different "You are Here" markation
> depending on
> the specific hotel. I am looking at the propagated
> road systems by a commonly shared view first, then I
> respect the
> different "you are here" markation. Rambo-SPF
> however means:"I am here.I see the world only from
> my point of view."
> Taking into consideration any kind of constraints
> and whichever weights doesn't change anything of
> this egocentric
> view + behavior with all its disadvantages.
> 
> 
> Heinrich
> 
> -----Ursprüngliche Nachricht-----
> Von: senthil ayyasamy [mailto:mplsgeek@yahoo.com]
> Gesendet: Samstag, 3. August 2002 09:40
> An: venumadhav josyula; Hummel Heinrich;
> 'sven.van_den_bosch@alcatel.be';
> mpls-ops-request@mplsrc.com
> Cc: Andrew Walding; kbenjamin@zvolve.com;
> mpls-ops@mplsrc.com
> Betreff: Re: AW: [MPLS-OPS]: MPLS Debacle
> 
> 
> 
> > See how many
> > QoS
> > > routing schemes were proposed, researched and
> not
> > > deployed. See what is the problem with those
> > routing
> > > Variants and then suggest differential routing
> > > Scheme.
> > >
> > Ok tell me why would not such a scheme work?
> Where I mentioned  *differential routing* wont
> work. Proposing new ideas are always easy. Let me 
> illustrate with an example.
> 
> SPF+ variants of SP algo (widest SP, shortest widest
> bandwidth path, bw inversion SP, ...)+ optimal
> multipath+source routing+ loose source routing+
> explicit paths (MPLS)+ k-shortest path and its
> variants+QoS routing( load sensitive,delay
> sensitive,
> single metric based,multi-metric based) +OSPF
> extensions+ all dynamic routing schemes as mentioned
> 
> in Ash book+PNNI + all frame relay and other type of
> routing+ MPLS based (constrianed or whatever)+
> overlay
> based routing+ onion routing+hot potato+ cold potato
> routing+...
> 
> I have listed a *few* unicast routing schemes. I can
> list more routing Schemes taking multicast, any cast
> into picture... leave alone ad-hoc, host mobility,
> network mobility, topology independent ...so on..
> 
> Most of the above routing schemes are subsets of
> some
> of the listed schemes. So suggesting a new routing
> scheme is not a big work. Using a simple combination
> and taking  some new technologies into picture, one
> can come up with a new routing scheme. But frankly
> that's not a correct approach for any protocol
> developed in IETF.
> 
> You should exactly come up with:
> - Requirements
> - Applicability statement
> - What problems the current schemes did not solve
> which lead you to suggest the present routing
> scheme.
> - What is the over-head when compared to the other
> existing technologies??? Usegood simulation to prove
> them.
> - A theoretical model to prove its use by means of
> routing problem formulations
> - Some case studies.
> - Study their properties (scalability, flexibility
> and
> extendibility.)
> - What all places it is most useful or waste
> (inter-domain or intra-domain)
> - Does it conform with the architectural principle
> (this is important: e.g.. Scalability alone is not
> the
> reason for intserv non-usage. It did not work within
> boundaries (AS.) alone.It can transcend an
> autonomous
> system boundary and so policy cannot be maintained.
> Hence, it did not support the business models well.)
> 
> 
> Now come to IETF. Give an engineering perspective to
> your routing scheme. Convince vendors to implement
> your routing scheme.
> 
> It is sometimes unfortunate that people just come up
> with some X routing scheme and try to convince
> engineering folks. Some of the IETF works was just
> proposals and hence did not succeed or gave problems
> at the later stage. So do all the above work for
> your
> new scheme and then everyone will accept your
> proposal.
> 
> Read the below book on how well the author approach
> such new schemes. 
>  *G. R. Ash. Dynamic Routing in Telecommunications
> Networks. McGraw Hill, New York, 1998*
> This is the book, which introduced dynamic routing
> schemes. It is not just bunch of ideas but has a
> in-depth analysis of requirements and theory.
> 
> 
> > CSPF (Constraint based shortest path) which is a
> > kind
> > of differential routing. I have some discussion in
> > this thread itself on that respect. 
> > Constraint based routing is modification of
> shortest
> > path alo to account for contraints such as (BW ,
> > QOS,
> > policy). 
> 
> I accept this scheme. There are simulation and
> mathematical work to see its behavior. But what it
> lacks is *deployment* which we cannot help.
> There might be lot of operational and business
> policy
> factors associated.
> 
> > CSPF solution is quite popular many are
> implementing
> > it , but I am not sure deployment and
> > interoperatablity concerns......... CSPF answers
> QOS
> > routing concerns (correct if i am wrong). It is
> not
> > the all of the mechanims proposed are
> failure.......
> 
> Note: I could not resist and hence replied. But if
> your care to respond to this mail, reply to general
> routing discussion than MPLS list.
> 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From daemon@optimus.ietf.org  Mon Aug  5 06:09:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05677
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 05:19:41 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA20075
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 05:20:53 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA19600;
	Mon, 5 Aug 2002 05:06:32 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA19569
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 05:06:26 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05464
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 05:05:12 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id LAA05700;
	Mon, 5 Aug 2002 11:06:09 +0200 (MET DST)
Received: from mchh273e.demchh201e.icn.siemens.de ([139.21.200.83])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id LAA22325;
	Mon, 5 Aug 2002 11:06:10 +0200 (MET DST)
Received: by MCHH273E with Internet Mail Service (5.5.2656.59)
	id <P71Q02GM>; Mon, 5 Aug 2002 11:05:55 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B977@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'senthil ayyasamy'" <mplsgeek@yahoo.com>,
        "'venumadhav josyula'"
	 <venu_m_j@yahoo.com>,
        "'sven.van_den_bosch@alcatel.be'"
	 <sven.van_den_bosch@alcatel.be>
Cc: "'Andrew Walding'" <andy@cellstream.com>,
        "'kbenjamin@zvolve.com'"
	 <kbenjamin@zvolve.com>,
        "'routing-discussion@ietf.org'"
	 <routing-discussion@ietf.org>
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 11:05:51 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id FAA19570
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

From  [MPLS-OPS]: MPLS Debacle back to [routing-discussion]:Differentiated Routing, not only plain rambo-SPF
 

Senthil,
This email of yours as well as your previous one only confirms my statement, that
the entire Internet community  (or at least you and some others) is the prisoner of this rambo-SPF routing algorithm.
All the protocols you have enlisted (...,BW inversion SP,...PNNI,..) and let me also add
the reverse SPF in some multicast models, share this egocentric  SPF view.

I am    N O T     talking just another brand of rambo-SPF.

Also, it wouldn't be helpful to follow your advice (come up with requirements, application statements,...)
because if I did you would read all of it with your SPF-centric view in mind. You even do so now, after
I have explained how each router may aquire the identical view of some road system.

Another analogy: 
When you fly to some meeting place, you may get a flyer-map at the hotel concierge. The flyer-maps may be the same
no matter at which hotel you stay. But, eventually, they have a different "You are Here" markation depending on
the specific hotel. I am looking at the propagated road systems by a commonly shared view first, then I respect the
different "you are here" markation. Rambo-SPF however means:"I am here.I see the world only from my point of view."
Taking into consideration any kind of constraints and whichever weights doesn't change anything of this egocentric
view + behavior with all its disadvantages.


Heinrich

-----Ursprüngliche Nachricht-----
Von: senthil ayyasamy [mailto:mplsgeek@yahoo.com]
Gesendet: Samstag, 3. August 2002 09:40
An: venumadhav josyula; Hummel Heinrich;
'sven.van_den_bosch@alcatel.be'; mpls-ops-request@mplsrc.com
Cc: Andrew Walding; kbenjamin@zvolve.com; mpls-ops@mplsrc.com
Betreff: Re: AW: [MPLS-OPS]: MPLS Debacle



> See how many
> QoS
> > routing schemes were proposed, researched and not
> > deployed. See what is the problem with those
> routing
> > Variants and then suggest differential routing
> > Scheme.
> >
> Ok tell me why would not such a scheme work?
Where I mentioned  *differential routing* wont
work. Proposing new ideas are always easy. Let me 
illustrate with an example.

SPF+ variants of SP algo (widest SP, shortest widest
bandwidth path, bw inversion SP, ...)+ optimal
multipath+source routing+ loose source routing+
explicit paths (MPLS)+ k-shortest path and its
variants+QoS routing( load sensitive,delay sensitive,
single metric based,multi-metric based) +OSPF
extensions+ all dynamic routing schemes as mentioned 
in Ash book+PNNI + all frame relay and other type of
routing+ MPLS based (constrianed or whatever)+ overlay
based routing+ onion routing+hot potato+ cold potato
routing+...

I have listed a *few* unicast routing schemes. I can
list more routing Schemes taking multicast, any cast
into picture... leave alone ad-hoc, host mobility,
network mobility, topology independent ...so on..

Most of the above routing schemes are subsets of some
of the listed schemes. So suggesting a new routing
scheme is not a big work. Using a simple combination
and taking  some new technologies into picture, one
can come up with a new routing scheme. But frankly
that's not a correct approach for any protocol
developed in IETF.

You should exactly come up with:
- Requirements
- Applicability statement
- What problems the current schemes did not solve
which lead you to suggest the present routing scheme.
- What is the over-head when compared to the other
existing technologies??? Usegood simulation to prove
them.
- A theoretical model to prove its use by means of
routing problem formulations
- Some case studies.
- Study their properties (scalability, flexibility and
extendibility.)
- What all places it is most useful or waste
(inter-domain or intra-domain)
- Does it conform with the architectural principle
(this is important: e.g.. Scalability alone is not the
reason for intserv non-usage. It did not work within
boundaries (AS.) alone.It can transcend an autonomous
system boundary and so policy cannot be maintained.
Hence, it did not support the business models well.) 

Now come to IETF. Give an engineering perspective to
your routing scheme. Convince vendors to implement
your routing scheme.

It is sometimes unfortunate that people just come up
with some X routing scheme and try to convince
engineering folks. Some of the IETF works was just
proposals and hence did not succeed or gave problems
at the later stage. So do all the above work for your
new scheme and then everyone will accept your
proposal.

Read the below book on how well the author approach
such new schemes. 
 *G. R. Ash. Dynamic Routing in Telecommunications
Networks. McGraw Hill, New York, 1998*
This is the book, which introduced dynamic routing
schemes. It is not just bunch of ideas but has a
in-depth analysis of requirements and theory.


> CSPF (Constraint based shortest path) which is a
> kind
> of differential routing. I have some discussion in
> this thread itself on that respect. 
> Constraint based routing is modification of shortest
> path alo to account for contraints such as (BW ,
> QOS,
> policy). 

I accept this scheme. There are simulation and
mathematical work to see its behavior. But what it
lacks is *deployment* which we cannot help.
There might be lot of operational and business policy
factors associated.

> CSPF solution is quite popular many are implementing
> it , but I am not sure deployment and
> interoperatablity concerns......... CSPF answers QOS
> routing concerns (correct if i am wrong). It is not
> the all of the mechanims proposed are failure.......

Note: I could not resist and hence replied. But if
your care to respond to this mail, reply to general
routing discussion than MPLS list.

__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 06:55:48 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07479
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 06:55:47 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA24678;
	Mon, 5 Aug 2002 06:49:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA24650
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 06:49:50 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07310
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 06:48:37 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id MAA13882;
	Mon, 5 Aug 2002 12:49:45 +0200 (MET DST)
Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id MAA09912;
	Mon, 5 Aug 2002 12:49:46 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2656.59)
	id <PTSZC62N>; Mon, 5 Aug 2002 12:49:31 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B978@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>
Cc: Venkata.Naidu@marconi.com, jnc@ginger.lcs.mit.edu, fred@cisco.com,
        irtf-rr@puck.nether.net, routing-discussion@ietf.org
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 12:49:31 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id GAA24651
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Let me repeat:
With SPF each node computes its individual tree towards all the other nodes. The sum of all these (n) trees
will most likely cover the entire network. Some may see this advantageous (traffic is distributed all over the network).
However by "DiffRout" as I like to advocat some traffic can be locked into ONE particular slim tree of links (e.g. the smallest size tree), and having several such slim trees (= road systems), which are constructed in awareness of
each other, and which may even have assigned bandwidth, much better control of the traffic/network can be executed.

Because you mention NP-hardness:
The algorithm I showed last week is very fast and doesn't constitute any performance problem.
BTW: I can likewise provide an (yes, heuristic) algorithm (no, four of them)as to build a list of links which form a ring 
(instead of the smallest size tree) and would interconnect n edge nodes by n links. 
Even for n= 200 (as I did for draft-hummel-n-square-investigations-00.txt) it only takes one or two seconds 
computation time.
Note, it is this notorious traveling salesman problem.To find the absolute best link sequence of the ring
it would take 10**80 years computation time, given that one particular link arrangement can be 
checked within 1 micro-second. 

Heinrich

-----Ursprüngliche Nachricht-----
Von: Ayyasamy, Senthilkumar (UMKC-Student) [mailto:saq66@umkc.edu]
Gesendet: Montag, 5. August 2002 12:03
An: Hummel Heinrich
Cc: Venkata.Naidu@Marconi.com; jnc@ginger.lcs.mit.edu; fred@cisco.com;
irtf-rr@puck.nether.net; routing-discussion@ietf.org
Betreff: RE: Differentiated Routing, not only plain rambo-SPF


-- Hummel Heinrich <Heinrich.Hummel@icn.siemens.de> 
wrote: > From  [MPLS-OPS]: MPLS Debacle back to
> [routing-discussion]:Differentiated Routing, not
> only plain rambo-SPF
>  
> 
> Senthil,
> This email of yours as well as your previous one
> only confirms my statement, that
> the entire Internet community  (or at least you and
> some others) is the prisoner of this rambo-SPF
> routing algorithm.
> All the protocols you have enlisted (...,BW
> inversion SP,...PNNI,..) and let me also add
> the reverse SPF in some multicast models, share this
> egocentric  SPF view.

> I am    N O T     talking just another brand of
> rambo-SPF.

My .02$:

1. The diffserv architecture, as of now, defines only 
the data plane work.  control plane activities( routing,
signaling etc)  are still open questions. 
 My argument is contradictory to what you suggest:
An effective load balancing in diffserv can be done 
by taking SPF algo into consideration. The NP-hardness 
in the existing *routing problem* formulations can be 
be approximated to polynomial time effectively by taking
both diffserv and SPF into consideration(as paths are 
predictable in a diffserv domain. )
 Most of the current routing problems formulations 
are solved by means of heuristic methods. But one can 
approximate to polynomial time by taking both SPF and 
diffserv into consideration.

Note: I am just tossing an idea. I will update you 
all once i get some good results.

2.[ some diffrout def from the discussion]

*Certainly, the basic idea of DiffRout is to use 
the DSCP-Bits, or even all 8 TOS-bits, for addressing 
different Routing Tables for looking up the next hop 
link (you can as well have one common Routing Table 
but search for the right entry while using destination 
address AND DSCP as search keys - this is up to the 
programmer).*

*In normal, state-less IP routing we cannot do 
QoS-Routing, nor sneak-around the congestion-area 
routing, nor traffic balanced routing. Instead, all 
of this is left to MPLS, where multiple states and 
multiple LSPs and multiple signalling is required.
With other words:I try to enable QoS-Routing, 
"sneak-around the congestion-area" -Routing, 
traffic balanced -Routing.*

*the intersection of all the subsets (ie., 
(QoS using MPLS-(DiffServ-Aware-TE) will make 
a *real-good* impact on end-to-end performance 
in the global Internet*   

Do me a favor. Replace the term  *DSCP* with 
*CoS* and *Diffserv* with *MPLS * in the above 
definition, you can call your new routing
scheme as *multi-protocol routing*. 
( humorous aside: Tips from a networking insider 
http://www.cs.ucsd.edu/~savage/papers/OO01.pdf :-) )

Thus said, coming with a new scheme is not a big task,
problem space and applicability statement is very 
important.

Read *An Overview of the New Routing Algorithm for 
the ARPANET, J. M. McQuillan, I. Richter, E. C. Rosen 
(Proc. Sixth Data Comm.Symposium, November 1979)*
http://www.acm.org/sigcomm/ccr/archive/1995/jan95/ccr-9501-mcquilln.pdf 

The above work marked the begining of transition from 
the old ARPANET distributed routing algorithms to 
SPF. The authors start with the *problems with the 
original algorithm*, then *need for SPF* and convinces 
the network floks that *SPF is just an increment to 
the original algorithm*. 

I am not asking you to formulate diffrout as an increment 
to SPF but just enlighten us *problem* and *need* of 
diffrout.

- Senthil.


> 
> Also, it wouldn't be helpful to follow your advice
> (come up with requirements, application
> statements,...)
> because if I did you would read all of it with your
> SPF-centric view in mind. You even do so now, after
> I have explained how each router may aquire the
> identical view of some road system.
> 
> Another analogy: 
> When you fly to some meeting place, you may get a
> flyer-map at the hotel concierge. The flyer-maps may
> be the same
> no matter at which hotel you stay. But, eventually,
> they have a different "You are Here" markation
> depending on
> the specific hotel. I am looking at the propagated
> road systems by a commonly shared view first, then I
> respect the
> different "you are here" markation. Rambo-SPF
> however means:"I am here.I see the world only from
> my point of view."
> Taking into consideration any kind of constraints
> and whichever weights doesn't change anything of
> this egocentric
> view + behavior with all its disadvantages.
> 
> 
> Heinrich
> 
> -----Ursprüngliche Nachricht-----
> Von: senthil ayyasamy [mailto:mplsgeek@yahoo.com]
> Gesendet: Samstag, 3. August 2002 09:40
> An: venumadhav josyula; Hummel Heinrich;
> 'sven.van_den_bosch@alcatel.be';
> mpls-ops-request@mplsrc.com
> Cc: Andrew Walding; kbenjamin@zvolve.com;
> mpls-ops@mplsrc.com
> Betreff: Re: AW: [MPLS-OPS]: MPLS Debacle
> 
> 
> 
> > See how many
> > QoS
> > > routing schemes were proposed, researched and
> not
> > > deployed. See what is the problem with those
> > routing
> > > Variants and then suggest differential routing
> > > Scheme.
> > >
> > Ok tell me why would not such a scheme work?
> Where I mentioned  *differential routing* wont
> work. Proposing new ideas are always easy. Let me 
> illustrate with an example.
> 
> SPF+ variants of SP algo (widest SP, shortest widest
> bandwidth path, bw inversion SP, ...)+ optimal
> multipath+source routing+ loose source routing+
> explicit paths (MPLS)+ k-shortest path and its
> variants+QoS routing( load sensitive,delay
> sensitive,
> single metric based,multi-metric based) +OSPF
> extensions+ all dynamic routing schemes as mentioned
> 
> in Ash book+PNNI + all frame relay and other type of
> routing+ MPLS based (constrianed or whatever)+
> overlay
> based routing+ onion routing+hot potato+ cold potato
> routing+...
> 
> I have listed a *few* unicast routing schemes. I can
> list more routing Schemes taking multicast, any cast
> into picture... leave alone ad-hoc, host mobility,
> network mobility, topology independent ...so on..
> 
> Most of the above routing schemes are subsets of
> some
> of the listed schemes. So suggesting a new routing
> scheme is not a big work. Using a simple combination
> and taking  some new technologies into picture, one
> can come up with a new routing scheme. But frankly
> that's not a correct approach for any protocol
> developed in IETF.
> 
> You should exactly come up with:
> - Requirements
> - Applicability statement
> - What problems the current schemes did not solve
> which lead you to suggest the present routing
> scheme.
> - What is the over-head when compared to the other
> existing technologies??? Usegood simulation to prove
> them.
> - A theoretical model to prove its use by means of
> routing problem formulations
> - Some case studies.
> - Study their properties (scalability, flexibility
> and
> extendibility.)
> - What all places it is most useful or waste
> (inter-domain or intra-domain)
> - Does it conform with the architectural principle
> (this is important: e.g.. Scalability alone is not
> the
> reason for intserv non-usage. It did not work within
> boundaries (AS.) alone.It can transcend an
> autonomous
> system boundary and so policy cannot be maintained.
> Hence, it did not support the business models well.)
> 
> 
> Now come to IETF. Give an engineering perspective to
> your routing scheme. Convince vendors to implement
> your routing scheme.
> 
> It is sometimes unfortunate that people just come up
> with some X routing scheme and try to convince
> engineering folks. Some of the IETF works was just
> proposals and hence did not succeed or gave problems
> at the later stage. So do all the above work for
> your
> new scheme and then everyone will accept your
> proposal.
> 
> Read the below book on how well the author approach
> such new schemes. 
>  *G. R. Ash. Dynamic Routing in Telecommunications
> Networks. McGraw Hill, New York, 1998*
> This is the book, which introduced dynamic routing
> schemes. It is not just bunch of ideas but has a
> in-depth analysis of requirements and theory.
> 
> 
> > CSPF (Constraint based shortest path) which is a
> > kind
> > of differential routing. I have some discussion in
> > this thread itself on that respect. 
> > Constraint based routing is modification of
> shortest
> > path alo to account for contraints such as (BW ,
> > QOS,
> > policy). 
> 
> I accept this scheme. There are simulation and
> mathematical work to see its behavior. But what it
> lacks is *deployment* which we cannot help.
> There might be lot of operational and business
> policy
> factors associated.
> 
> > CSPF solution is quite popular many are
> implementing
> > it , but I am not sure deployment and
> > interoperatablity concerns......... CSPF answers
> QOS
> > routing concerns (correct if i am wrong). It is
> not
> > the all of the mechanims proposed are
> failure.......
> 
> Note: I could not resist and hence replied. But if
> your care to respond to this mail, reply to general
> routing discussion than MPLS list.
> 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 06:55:48 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07484
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 06:55:48 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA24957
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 06:57:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA24678;
	Mon, 5 Aug 2002 06:49:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA24650
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 06:49:50 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07310
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 06:48:37 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id MAA13882;
	Mon, 5 Aug 2002 12:49:45 +0200 (MET DST)
Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id MAA09912;
	Mon, 5 Aug 2002 12:49:46 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2656.59)
	id <PTSZC62N>; Mon, 5 Aug 2002 12:49:31 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B978@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>
Cc: Venkata.Naidu@marconi.com, jnc@ginger.lcs.mit.edu, fred@cisco.com,
        irtf-rr@puck.nether.net, routing-discussion@ietf.org
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 12:49:31 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id GAA24651
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Let me repeat:
With SPF each node computes its individual tree towards all the other nodes. The sum of all these (n) trees
will most likely cover the entire network. Some may see this advantageous (traffic is distributed all over the network).
However by "DiffRout" as I like to advocat some traffic can be locked into ONE particular slim tree of links (e.g. the smallest size tree), and having several such slim trees (= road systems), which are constructed in awareness of
each other, and which may even have assigned bandwidth, much better control of the traffic/network can be executed.

Because you mention NP-hardness:
The algorithm I showed last week is very fast and doesn't constitute any performance problem.
BTW: I can likewise provide an (yes, heuristic) algorithm (no, four of them)as to build a list of links which form a ring 
(instead of the smallest size tree) and would interconnect n edge nodes by n links. 
Even for n= 200 (as I did for draft-hummel-n-square-investigations-00.txt) it only takes one or two seconds 
computation time.
Note, it is this notorious traveling salesman problem.To find the absolute best link sequence of the ring
it would take 10**80 years computation time, given that one particular link arrangement can be 
checked within 1 micro-second. 

Heinrich

-----Ursprüngliche Nachricht-----
Von: Ayyasamy, Senthilkumar (UMKC-Student) [mailto:saq66@umkc.edu]
Gesendet: Montag, 5. August 2002 12:03
An: Hummel Heinrich
Cc: Venkata.Naidu@Marconi.com; jnc@ginger.lcs.mit.edu; fred@cisco.com;
irtf-rr@puck.nether.net; routing-discussion@ietf.org
Betreff: RE: Differentiated Routing, not only plain rambo-SPF


-- Hummel Heinrich <Heinrich.Hummel@icn.siemens.de> 
wrote: > From  [MPLS-OPS]: MPLS Debacle back to
> [routing-discussion]:Differentiated Routing, not
> only plain rambo-SPF
>  
> 
> Senthil,
> This email of yours as well as your previous one
> only confirms my statement, that
> the entire Internet community  (or at least you and
> some others) is the prisoner of this rambo-SPF
> routing algorithm.
> All the protocols you have enlisted (...,BW
> inversion SP,...PNNI,..) and let me also add
> the reverse SPF in some multicast models, share this
> egocentric  SPF view.

> I am    N O T     talking just another brand of
> rambo-SPF.

My .02$:

1. The diffserv architecture, as of now, defines only 
the data plane work.  control plane activities( routing,
signaling etc)  are still open questions. 
 My argument is contradictory to what you suggest:
An effective load balancing in diffserv can be done 
by taking SPF algo into consideration. The NP-hardness 
in the existing *routing problem* formulations can be 
be approximated to polynomial time effectively by taking
both diffserv and SPF into consideration(as paths are 
predictable in a diffserv domain. )
 Most of the current routing problems formulations 
are solved by means of heuristic methods. But one can 
approximate to polynomial time by taking both SPF and 
diffserv into consideration.

Note: I am just tossing an idea. I will update you 
all once i get some good results.

2.[ some diffrout def from the discussion]

*Certainly, the basic idea of DiffRout is to use 
the DSCP-Bits, or even all 8 TOS-bits, for addressing 
different Routing Tables for looking up the next hop 
link (you can as well have one common Routing Table 
but search for the right entry while using destination 
address AND DSCP as search keys - this is up to the 
programmer).*

*In normal, state-less IP routing we cannot do 
QoS-Routing, nor sneak-around the congestion-area 
routing, nor traffic balanced routing. Instead, all 
of this is left to MPLS, where multiple states and 
multiple LSPs and multiple signalling is required.
With other words:I try to enable QoS-Routing, 
"sneak-around the congestion-area" -Routing, 
traffic balanced -Routing.*

*the intersection of all the subsets (ie., 
(QoS using MPLS-(DiffServ-Aware-TE) will make 
a *real-good* impact on end-to-end performance 
in the global Internet*   

Do me a favor. Replace the term  *DSCP* with 
*CoS* and *Diffserv* with *MPLS * in the above 
definition, you can call your new routing
scheme as *multi-protocol routing*. 
( humorous aside: Tips from a networking insider 
http://www.cs.ucsd.edu/~savage/papers/OO01.pdf :-) )

Thus said, coming with a new scheme is not a big task,
problem space and applicability statement is very 
important.

Read *An Overview of the New Routing Algorithm for 
the ARPANET, J. M. McQuillan, I. Richter, E. C. Rosen 
(Proc. Sixth Data Comm.Symposium, November 1979)*
http://www.acm.org/sigcomm/ccr/archive/1995/jan95/ccr-9501-mcquilln.pdf 

The above work marked the begining of transition from 
the old ARPANET distributed routing algorithms to 
SPF. The authors start with the *problems with the 
original algorithm*, then *need for SPF* and convinces 
the network floks that *SPF is just an increment to 
the original algorithm*. 

I am not asking you to formulate diffrout as an increment 
to SPF but just enlighten us *problem* and *need* of 
diffrout.

- Senthil.


> 
> Also, it wouldn't be helpful to follow your advice
> (come up with requirements, application
> statements,...)
> because if I did you would read all of it with your
> SPF-centric view in mind. You even do so now, after
> I have explained how each router may aquire the
> identical view of some road system.
> 
> Another analogy: 
> When you fly to some meeting place, you may get a
> flyer-map at the hotel concierge. The flyer-maps may
> be the same
> no matter at which hotel you stay. But, eventually,
> they have a different "You are Here" markation
> depending on
> the specific hotel. I am looking at the propagated
> road systems by a commonly shared view first, then I
> respect the
> different "you are here" markation. Rambo-SPF
> however means:"I am here.I see the world only from
> my point of view."
> Taking into consideration any kind of constraints
> and whichever weights doesn't change anything of
> this egocentric
> view + behavior with all its disadvantages.
> 
> 
> Heinrich
> 
> -----Ursprüngliche Nachricht-----
> Von: senthil ayyasamy [mailto:mplsgeek@yahoo.com]
> Gesendet: Samstag, 3. August 2002 09:40
> An: venumadhav josyula; Hummel Heinrich;
> 'sven.van_den_bosch@alcatel.be';
> mpls-ops-request@mplsrc.com
> Cc: Andrew Walding; kbenjamin@zvolve.com;
> mpls-ops@mplsrc.com
> Betreff: Re: AW: [MPLS-OPS]: MPLS Debacle
> 
> 
> 
> > See how many
> > QoS
> > > routing schemes were proposed, researched and
> not
> > > deployed. See what is the problem with those
> > routing
> > > Variants and then suggest differential routing
> > > Scheme.
> > >
> > Ok tell me why would not such a scheme work?
> Where I mentioned  *differential routing* wont
> work. Proposing new ideas are always easy. Let me 
> illustrate with an example.
> 
> SPF+ variants of SP algo (widest SP, shortest widest
> bandwidth path, bw inversion SP, ...)+ optimal
> multipath+source routing+ loose source routing+
> explicit paths (MPLS)+ k-shortest path and its
> variants+QoS routing( load sensitive,delay
> sensitive,
> single metric based,multi-metric based) +OSPF
> extensions+ all dynamic routing schemes as mentioned
> 
> in Ash book+PNNI + all frame relay and other type of
> routing+ MPLS based (constrianed or whatever)+
> overlay
> based routing+ onion routing+hot potato+ cold potato
> routing+...
> 
> I have listed a *few* unicast routing schemes. I can
> list more routing Schemes taking multicast, any cast
> into picture... leave alone ad-hoc, host mobility,
> network mobility, topology independent ...so on..
> 
> Most of the above routing schemes are subsets of
> some
> of the listed schemes. So suggesting a new routing
> scheme is not a big work. Using a simple combination
> and taking  some new technologies into picture, one
> can come up with a new routing scheme. But frankly
> that's not a correct approach for any protocol
> developed in IETF.
> 
> You should exactly come up with:
> - Requirements
> - Applicability statement
> - What problems the current schemes did not solve
> which lead you to suggest the present routing
> scheme.
> - What is the over-head when compared to the other
> existing technologies??? Usegood simulation to prove
> them.
> - A theoretical model to prove its use by means of
> routing problem formulations
> - Some case studies.
> - Study their properties (scalability, flexibility
> and
> extendibility.)
> - What all places it is most useful or waste
> (inter-domain or intra-domain)
> - Does it conform with the architectural principle
> (this is important: e.g.. Scalability alone is not
> the
> reason for intserv non-usage. It did not work within
> boundaries (AS.) alone.It can transcend an
> autonomous
> system boundary and so policy cannot be maintained.
> Hence, it did not support the business models well.)
> 
> 
> Now come to IETF. Give an engineering perspective to
> your routing scheme. Convince vendors to implement
> your routing scheme.
> 
> It is sometimes unfortunate that people just come up
> with some X routing scheme and try to convince
> engineering folks. Some of the IETF works was just
> proposals and hence did not succeed or gave problems
> at the later stage. So do all the above work for
> your
> new scheme and then everyone will accept your
> proposal.
> 
> Read the below book on how well the author approach
> such new schemes. 
>  *G. R. Ash. Dynamic Routing in Telecommunications
> Networks. McGraw Hill, New York, 1998*
> This is the book, which introduced dynamic routing
> schemes. It is not just bunch of ideas but has a
> in-depth analysis of requirements and theory.
> 
> 
> > CSPF (Constraint based shortest path) which is a
> > kind
> > of differential routing. I have some discussion in
> > this thread itself on that respect. 
> > Constraint based routing is modification of
> shortest
> > path alo to account for contraints such as (BW ,
> > QOS,
> > policy). 
> 
> I accept this scheme. There are simulation and
> mathematical work to see its behavior. But what it
> lacks is *deployment* which we cannot help.
> There might be lot of operational and business
> policy
> factors associated.
> 
> > CSPF solution is quite popular many are
> implementing
> > it , but I am not sure deployment and
> > interoperatablity concerns......... CSPF answers
> QOS
> > routing concerns (correct if i am wrong). It is
> not
> > the all of the mechanims proposed are
> failure.......
> 
> Note: I could not resist and hence replied. But if
> your care to respond to this mail, reply to general
> routing discussion than MPLS list.
> 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 08:18:41 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09532
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 08:18:41 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA28479;
	Mon, 5 Aug 2002 08:13:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA28416
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 08:13:07 -0400 (EDT)
Received: from kc-msxproto4.kc.umkc.edu (kc-msxproto4.kc.umkc.edu [134.193.143.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09339
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 08:11:54 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 5 Aug 2002 07:13:04 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 07:13:04 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C2522@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcI8beJbdUnzo1mkQtOCURMJdvl8DQAAjHEA
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>
Cc: <Venkata.Naidu@marconi.com>, <jnc@ginger.lcs.mit.edu>, <fred@cisco.com>,
        <irtf-rr@puck.nether.net>, <routing-discussion@ietf.org>
X-OriginalArrivalTime: 05 Aug 2002 12:13:04.0956 (UTC) FILETIME=[73B227C0:01C23C79]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id IAA28418
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

> With SPF each node computes its individual tree towards all 
> the other nodes. The sum of all these (n) trees
> will most likely cover the entire network. Some may see this 
> advantageous (traffic is distributed all over the network).
> However by "DiffRout" as I like to advocat some traffic can 
> be locked into ONE particular slim tree of links (e.g. the 
> smallest size tree), and having several such slim trees (= 
> road systems), which are constructed in awareness of
> each other, and which may even have assigned bandwidth, much 
> better control of the traffic/network can be executed.

Ok. Understood. Let us discuss without taking problem space 
and applicability statement factors ( as you dont have one.)

1. The diffserv architecture does not assume anything about
routing stability. I am not sure, but the original designers
should have assumed that *routing system should be stable for 
a predictable functioning of diffserv components*. So, in a 
*EXTREMELY* congested network, all queuing and scheduling 
mechanisms may show some anomalous behaviour ( I am not sure 
again.)

How will diffrout help in such a situation. I dont think
you can do some sort of routing based on DSCP at that point.

2. DSCP is actually for classification (queueing mechanism.)
Can you just explain the gap between *DSCP as used for 
classification* and *DSCP as used for routing*? Remember, 
you are using DSCP both for data plane and control plane 
work here.

I am also sceptical of the following issues:

- scalability: Since you are maintaining multiple Routing
tables, doing at line rate is pretty difficult and hence
doesnt scale well.

- complexity: This work increases the complexity at per 
router level. Some people complain of increase in complexity 
for just adding three more lines in the original forwaring algo
(to include RED features.) I dont know  how much complex
the router becomes because of diffrout.

- end to end: Diffserv is defined only for edge to edge. How will 
diffrout behave when considering end to end is still open.


> The algorithm I showed last week is very fast and doesn't 
> constitute any performance problem.

How are you justifying that it doesn't consitute any performance
problems. Do you have any mathematically tractable model or 
simulation work?

Let me suggest you a method for going about your analysis:

1. Formulate  diffrout as a *diffserv routing problem* with 
all possible constraints. prove them to be NP-hard and if possible
find some heuristic results ( genetic algo based or local search
one). 
Refer *http://www.research.att.com/~jrex/papers/ieeecomm02.long.pdf*
 
2. Define QoS compuatation algebra for your work.
Refer *http://citeseer.nj.nec.com/sobrinho01algebra.html*

3. If heuritic method is not feasible, go for some approximation
methods and prove using some theoretical results. Then support your 
performance claims with some simulation results.

If you do all this, I will accept that your algorithm doesn't 
consititute any performance problem.







_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 08:18:42 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09542
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 08:18:42 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA28743
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 08:19:54 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA28479;
	Mon, 5 Aug 2002 08:13:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA28416
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 08:13:07 -0400 (EDT)
Received: from kc-msxproto4.kc.umkc.edu (kc-msxproto4.kc.umkc.edu [134.193.143.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09339
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 08:11:54 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 5 Aug 2002 07:13:04 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 07:13:04 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C2522@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcI8beJbdUnzo1mkQtOCURMJdvl8DQAAjHEA
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>
Cc: <Venkata.Naidu@marconi.com>, <jnc@ginger.lcs.mit.edu>, <fred@cisco.com>,
        <irtf-rr@puck.nether.net>, <routing-discussion@ietf.org>
X-OriginalArrivalTime: 05 Aug 2002 12:13:04.0956 (UTC) FILETIME=[73B227C0:01C23C79]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id IAA28418
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

> With SPF each node computes its individual tree towards all 
> the other nodes. The sum of all these (n) trees
> will most likely cover the entire network. Some may see this 
> advantageous (traffic is distributed all over the network).
> However by "DiffRout" as I like to advocat some traffic can 
> be locked into ONE particular slim tree of links (e.g. the 
> smallest size tree), and having several such slim trees (= 
> road systems), which are constructed in awareness of
> each other, and which may even have assigned bandwidth, much 
> better control of the traffic/network can be executed.

Ok. Understood. Let us discuss without taking problem space 
and applicability statement factors ( as you dont have one.)

1. The diffserv architecture does not assume anything about
routing stability. I am not sure, but the original designers
should have assumed that *routing system should be stable for 
a predictable functioning of diffserv components*. So, in a 
*EXTREMELY* congested network, all queuing and scheduling 
mechanisms may show some anomalous behaviour ( I am not sure 
again.)

How will diffrout help in such a situation. I dont think
you can do some sort of routing based on DSCP at that point.

2. DSCP is actually for classification (queueing mechanism.)
Can you just explain the gap between *DSCP as used for 
classification* and *DSCP as used for routing*? Remember, 
you are using DSCP both for data plane and control plane 
work here.

I am also sceptical of the following issues:

- scalability: Since you are maintaining multiple Routing
tables, doing at line rate is pretty difficult and hence
doesnt scale well.

- complexity: This work increases the complexity at per 
router level. Some people complain of increase in complexity 
for just adding three more lines in the original forwaring algo
(to include RED features.) I dont know  how much complex
the router becomes because of diffrout.

- end to end: Diffserv is defined only for edge to edge. How will 
diffrout behave when considering end to end is still open.


> The algorithm I showed last week is very fast and doesn't 
> constitute any performance problem.

How are you justifying that it doesn't consitute any performance
problems. Do you have any mathematically tractable model or 
simulation work?

Let me suggest you a method for going about your analysis:

1. Formulate  diffrout as a *diffserv routing problem* with 
all possible constraints. prove them to be NP-hard and if possible
find some heuristic results ( genetic algo based or local search
one). 
Refer *http://www.research.att.com/~jrex/papers/ieeecomm02.long.pdf*
 
2. Define QoS compuatation algebra for your work.
Refer *http://citeseer.nj.nec.com/sobrinho01algebra.html*

3. If heuritic method is not feasible, go for some approximation
methods and prove using some theoretical results. Then support your 
performance claims with some simulation results.

If you do all this, I will accept that your algorithm doesn't 
consititute any performance problem.







_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 09:20:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11835
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 09:20:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00940;
	Mon, 5 Aug 2002 09:04:11 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00914
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 09:04:10 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11157
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 09:02:56 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id PAA26069;
	Mon, 5 Aug 2002 15:04:05 +0200 (MET DST)
Received: from mchh273e.demchh201e.icn.siemens.de ([139.21.200.83])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id PAA17025;
	Mon, 5 Aug 2002 15:04:06 +0200 (MET DST)
Received: by MCHH273E with Internet Mail Service (5.5.2656.59)
	id <P71Q0SM7>; Mon, 5 Aug 2002 15:03:50 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B97B@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>
Cc: Venkata.Naidu@marconi.com, jnc@ginger.lcs.mit.edu, fred@cisco.com,
        irtf-rr@puck.nether.net, routing-discussion@ietf.org
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 15:03:43 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id JAA00915
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Find my lines inserted
Heinrich

-----Ursprüngliche Nachricht-----
Von: Ayyasamy, Senthilkumar (UMKC-Student) [mailto:saq66@umkc.edu]
Gesendet: Montag, 5. August 2002 14:13
An: Hummel Heinrich
Cc: Venkata.Naidu@Marconi.com; jnc@ginger.lcs.mit.edu; fred@cisco.com;
irtf-rr@puck.nether.net; routing-discussion@ietf.org
Betreff: RE: Differentiated Routing, not only plain rambo-SPF


> With SPF each node computes its individual tree towards all 
> the other nodes. The sum of all these (n) trees
> will most likely cover the entire network. Some may see this 
> advantageous (traffic is distributed all over the network).
> However by "DiffRout" as I like to advocat some traffic can 
> be locked into ONE particular slim tree of links (e.g. the 
> smallest size tree), and having several such slim trees (= 
> road systems), which are constructed in awareness of
> each other, and which may even have assigned bandwidth, much 
> better control of the traffic/network can be executed.

Ok. Understood. Let us discuss without taking problem space 
and applicability statement factors ( as you dont have one.)

1. The diffserv architecture does not assume anything about
routing stability. I am not sure, but the original designers
should have assumed that *routing system should be stable for 
a predictable functioning of diffserv components*. So, in a 
*EXTREMELY* congested network, all queuing and scheduling 
mechanisms may show some anomalous behaviour ( I am not sure 
again.)

How will diffrout help in such a situation. I dont think
you can do some sort of routing based on DSCP at that point.

HH=> a) With respect to a particular road system X , you may determine a respective overflow road system X-overflow.
        E.g. you may determine by computation the cernel of a smallest size tree being that set of links
        which are used by at least y  s/d-traffic combinations, whereby n < y < n*(n-1); y be a fixed assigned number.
        You may recompute the smallest size tree, but before, you want to mark all the cernel links to DISREGARD.
        Traffic which is about to enter the cernel of X, may be forwarded via X-overflow while changing the
        receive DSCP-x to DSCP-x-overflow. The decission to do so may be based on a currently available traffic load/
        traffic metering information.

      b) Or you generate road systems X0, X1, X2, X3 such that the links of Xi, avoid overlaps with links of Xj, j<i.
         One micro flow uses DSCP x0, the next one DSCP x1,... as to balance the traffic and as to avoid congestion
         in the first place.    
 


2. DSCP is actually for classification (queueing mechanism.)
Can you just explain the gap between *DSCP as used for 
classification* and *DSCP as used for routing*? Remember, 
you are using DSCP both for data plane and control plane 
work here.

HH=> I am sure that DSCP codepoints can be selected such that the DiffServ and DiffRout aspects can be supported.
     After all, DiffRout will help DiffServ to avoid anomalous behaviour in the first place. 


I am also sceptical of the following issues:

- scalability: Since you are maintaining multiple Routing
tables, doing at line rate is pretty difficult and hence
doesnt scale well.

- complexity: This work increases the complexity at per 
router level. Some people complain of increase in complexity 
for just adding three more lines in the original forwaring algo
(to include RED features.) I dont know  how much complex
the router becomes because of diffrout.

HH:> There is never a free lunch. But what are a view routing tables compared to the probably much bigger number
of p2p LSPs?

- end to end: Diffserv is defined only for edge to edge. How will 
diffrout behave when considering end to end is still open.

HH=> Help me. I am open:-)


> The algorithm I showed last week is very fast and doesn't 
> constitute any performance problem.

How are you justifying that it doesn't consitute any performance
problems. Do you have any mathematically tractable model or 
simulation work?

HH=> All I have is this C++-program, written by some students, which I have used already several times
     as to show once this aspect, once that aspect, especially w.r.t. tunneling.

Let me suggest you a method for going about your analysis:

1. Formulate  diffrout as a *diffserv routing problem* with 
all possible constraints. prove them to be NP-hard and if possible
find some heuristic results ( genetic algo based or local search
one). 
Refer *http://www.research.att.com/~jrex/papers/ieeecomm02.long.pdf*

I did explain how to determine that set of links, which forms a tree between some edge nodes.
I mentioned that you have to run Dijkstra n times as to make some preparation. If you hereby apply all
the constraints as well as the specific weights you like to be considered, then the resulting
smallest size tree will suffice them, too.
 
2. Define QoS compuatation algebra for your work. 
Refer *http://citeseer.nj.nec.com/sobrinho01algebra.html*

HH=> Do I have to ? Remember, it is August and time to go on vacation :-)

3. If heuritic method is not feasible, go for some approximation
methods and prove using some theoretical results. Then support your 
performance claims with some simulation results.

HH=> If there is enough interest, I would be happy to show this C++-program on work. 
     As I said, it is not yet enhanced with tie breaker rules. But that would be very important as to
     determine the same identical smallest size tree determined b whichever node. If this failed we would
     have to continue with rambo-SPF:-)

If you do all this, I will accept that your algorithm doesn't 
consititute any performance problem.

HH=> No problem. Be sure, it doesn't run 10**80 years :-)








_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 09:20:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11844
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 09:20:27 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA01563
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 09:21:40 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00940;
	Mon, 5 Aug 2002 09:04:11 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00914
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 09:04:10 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11157
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 09:02:56 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id PAA26069;
	Mon, 5 Aug 2002 15:04:05 +0200 (MET DST)
Received: from mchh273e.demchh201e.icn.siemens.de ([139.21.200.83])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id PAA17025;
	Mon, 5 Aug 2002 15:04:06 +0200 (MET DST)
Received: by MCHH273E with Internet Mail Service (5.5.2656.59)
	id <P71Q0SM7>; Mon, 5 Aug 2002 15:03:50 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B97B@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>
Cc: Venkata.Naidu@marconi.com, jnc@ginger.lcs.mit.edu, fred@cisco.com,
        irtf-rr@puck.nether.net, routing-discussion@ietf.org
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 15:03:43 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id JAA00915
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Find my lines inserted
Heinrich

-----Ursprüngliche Nachricht-----
Von: Ayyasamy, Senthilkumar (UMKC-Student) [mailto:saq66@umkc.edu]
Gesendet: Montag, 5. August 2002 14:13
An: Hummel Heinrich
Cc: Venkata.Naidu@Marconi.com; jnc@ginger.lcs.mit.edu; fred@cisco.com;
irtf-rr@puck.nether.net; routing-discussion@ietf.org
Betreff: RE: Differentiated Routing, not only plain rambo-SPF


> With SPF each node computes its individual tree towards all 
> the other nodes. The sum of all these (n) trees
> will most likely cover the entire network. Some may see this 
> advantageous (traffic is distributed all over the network).
> However by "DiffRout" as I like to advocat some traffic can 
> be locked into ONE particular slim tree of links (e.g. the 
> smallest size tree), and having several such slim trees (= 
> road systems), which are constructed in awareness of
> each other, and which may even have assigned bandwidth, much 
> better control of the traffic/network can be executed.

Ok. Understood. Let us discuss without taking problem space 
and applicability statement factors ( as you dont have one.)

1. The diffserv architecture does not assume anything about
routing stability. I am not sure, but the original designers
should have assumed that *routing system should be stable for 
a predictable functioning of diffserv components*. So, in a 
*EXTREMELY* congested network, all queuing and scheduling 
mechanisms may show some anomalous behaviour ( I am not sure 
again.)

How will diffrout help in such a situation. I dont think
you can do some sort of routing based on DSCP at that point.

HH=> a) With respect to a particular road system X , you may determine a respective overflow road system X-overflow.
        E.g. you may determine by computation the cernel of a smallest size tree being that set of links
        which are used by at least y  s/d-traffic combinations, whereby n < y < n*(n-1); y be a fixed assigned number.
        You may recompute the smallest size tree, but before, you want to mark all the cernel links to DISREGARD.
        Traffic which is about to enter the cernel of X, may be forwarded via X-overflow while changing the
        receive DSCP-x to DSCP-x-overflow. The decission to do so may be based on a currently available traffic load/
        traffic metering information.

      b) Or you generate road systems X0, X1, X2, X3 such that the links of Xi, avoid overlaps with links of Xj, j<i.
         One micro flow uses DSCP x0, the next one DSCP x1,... as to balance the traffic and as to avoid congestion
         in the first place.    
 


2. DSCP is actually for classification (queueing mechanism.)
Can you just explain the gap between *DSCP as used for 
classification* and *DSCP as used for routing*? Remember, 
you are using DSCP both for data plane and control plane 
work here.

HH=> I am sure that DSCP codepoints can be selected such that the DiffServ and DiffRout aspects can be supported.
     After all, DiffRout will help DiffServ to avoid anomalous behaviour in the first place. 


I am also sceptical of the following issues:

- scalability: Since you are maintaining multiple Routing
tables, doing at line rate is pretty difficult and hence
doesnt scale well.

- complexity: This work increases the complexity at per 
router level. Some people complain of increase in complexity 
for just adding three more lines in the original forwaring algo
(to include RED features.) I dont know  how much complex
the router becomes because of diffrout.

HH:> There is never a free lunch. But what are a view routing tables compared to the probably much bigger number
of p2p LSPs?

- end to end: Diffserv is defined only for edge to edge. How will 
diffrout behave when considering end to end is still open.

HH=> Help me. I am open:-)


> The algorithm I showed last week is very fast and doesn't 
> constitute any performance problem.

How are you justifying that it doesn't consitute any performance
problems. Do you have any mathematically tractable model or 
simulation work?

HH=> All I have is this C++-program, written by some students, which I have used already several times
     as to show once this aspect, once that aspect, especially w.r.t. tunneling.

Let me suggest you a method for going about your analysis:

1. Formulate  diffrout as a *diffserv routing problem* with 
all possible constraints. prove them to be NP-hard and if possible
find some heuristic results ( genetic algo based or local search
one). 
Refer *http://www.research.att.com/~jrex/papers/ieeecomm02.long.pdf*

I did explain how to determine that set of links, which forms a tree between some edge nodes.
I mentioned that you have to run Dijkstra n times as to make some preparation. If you hereby apply all
the constraints as well as the specific weights you like to be considered, then the resulting
smallest size tree will suffice them, too.
 
2. Define QoS compuatation algebra for your work. 
Refer *http://citeseer.nj.nec.com/sobrinho01algebra.html*

HH=> Do I have to ? Remember, it is August and time to go on vacation :-)

3. If heuritic method is not feasible, go for some approximation
methods and prove using some theoretical results. Then support your 
performance claims with some simulation results.

HH=> If there is enough interest, I would be happy to show this C++-program on work. 
     As I said, it is not yet enhanced with tie breaker rules. But that would be very important as to
     determine the same identical smallest size tree determined b whichever node. If this failed we would
     have to continue with rambo-SPF:-)

If you do all this, I will accept that your algorithm doesn't 
consititute any performance problem.

HH=> No problem. Be sure, it doesn't run 10**80 years :-)








_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 10:27:35 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15101
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 10:27:35 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04757;
	Mon, 5 Aug 2002 10:14:54 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04725
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 10:14:52 -0400 (EDT)
Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14583
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 10:13:37 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id QAA00901;
	Mon, 5 Aug 2002 16:14:21 +0200 (MET DST)
Received: from mchh273e.demchh201e.icn.siemens.de ([139.21.200.83])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id QAA25359;
	Mon, 5 Aug 2002 16:14:40 +0200 (MET DST)
Received: by MCHH273E with Internet Mail Service (5.5.2656.59)
	id <P71Q0VWW>; Mon, 5 Aug 2002 16:14:24 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B97E@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'jshen@cad.zju.edu.cn'" <jshen@cad.zju.edu.cn>, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 16:14:21 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="gb2312"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Jing, 
find my lines inserted
Heinrich

Hummel ,


> HH=> a) With respect to a particular road system X , you may determine a respective overflow road system X-overflow.
>         E.g. you may determine by computation the cernel of a smallest size tree being that set of links
>         which are used by at least y  s/d-traffic combinations, whereby n < y < n*(n-1); y be a fixed assigned number.
>         You may recompute the smallest size tree, but before, you want to mark all the cernel links to DISREGARD.
>         Traffic which is about to enter the cernel of X, may be forwarded via X-overflow while changing the
>         receive DSCP-x to DSCP-x-overflow. The decission to do so may be based on a currently available traffic load/
>         traffic metering information.
>

what's the meaning of "cernel"? I can't find it in dictionary.  But, if you means overflow those congested traffic to
another path, I think it will do harm to promising of SLA signed. Perhaps what we need is to reroute some part of
traffic to another path with no/less congestion

HH=> Sorry for my bad English: I mean kernel (not cernel).
   But why would it do harm to promising of SLA ? This overflow route may provide the same QoS/SLA !


>
>       b) Or you generate road systems X0, X1, X2, X3 such that the links of Xi, avoid overlaps with links of Xj, j<i.
>          One micro flow uses DSCP x0, the next one DSCP x1,... as to balance the traffic and as to avoid congestion
>          in the first place.
>

I don't think load balancing could be achieved by this way, as self-similar and asymetric distribution in internet
traffic
HH=> By utilizing an extra information (i.e. different DSCPs)we are much better of than ECMP, where source/dest. is hashed
     in a poorly way. You really get for free the routing of all packets of a particular microflow along the same route !

>

>
>
> HH:> There is never a free lunch. But what are a view routing tables compared to the probably much bigger number
> of p2p LSPs?
>

But the problem is routers have to maintein all information about DSCP they support and propagate them.
HH=> this shouldn't be a big lunch packet, right ?

>
>
> 3. If heuritic method is not feasible, go for some approximation
> methods and prove using some theoretical results. Then support your
> performance claims with some simulation results.
>
> HH=> If there is enough interest, I would be happy to show this C++-program on work.
>      As I said, it is not yet enhanced with tie breaker rules. But that would be very important as to
>      determine the same identical smallest size tree determined b whichever node. If this failed we would
>      have to continue with rambo-SPF:-)
>
> If you do all this, I will accept that your algorithm doesn't
> consititute any performance problem.
>
> HH=> No problem. Be sure, it doesn't run 10**80 years :-)

--
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 10:27:35 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15110
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 10:27:35 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA05456
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 10:28:49 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04757;
	Mon, 5 Aug 2002 10:14:54 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04725
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 10:14:52 -0400 (EDT)
Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14583
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 10:13:37 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id QAA00901;
	Mon, 5 Aug 2002 16:14:21 +0200 (MET DST)
Received: from mchh273e.demchh201e.icn.siemens.de ([139.21.200.83])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id QAA25359;
	Mon, 5 Aug 2002 16:14:40 +0200 (MET DST)
Received: by MCHH273E with Internet Mail Service (5.5.2656.59)
	id <P71Q0VWW>; Mon, 5 Aug 2002 16:14:24 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B97E@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'jshen@cad.zju.edu.cn'" <jshen@cad.zju.edu.cn>, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 16:14:21 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="gb2312"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Jing, 
find my lines inserted
Heinrich

Hummel ,


> HH=> a) With respect to a particular road system X , you may determine a respective overflow road system X-overflow.
>         E.g. you may determine by computation the cernel of a smallest size tree being that set of links
>         which are used by at least y  s/d-traffic combinations, whereby n < y < n*(n-1); y be a fixed assigned number.
>         You may recompute the smallest size tree, but before, you want to mark all the cernel links to DISREGARD.
>         Traffic which is about to enter the cernel of X, may be forwarded via X-overflow while changing the
>         receive DSCP-x to DSCP-x-overflow. The decission to do so may be based on a currently available traffic load/
>         traffic metering information.
>

what's the meaning of "cernel"? I can't find it in dictionary.  But, if you means overflow those congested traffic to
another path, I think it will do harm to promising of SLA signed. Perhaps what we need is to reroute some part of
traffic to another path with no/less congestion

HH=> Sorry for my bad English: I mean kernel (not cernel).
   But why would it do harm to promising of SLA ? This overflow route may provide the same QoS/SLA !


>
>       b) Or you generate road systems X0, X1, X2, X3 such that the links of Xi, avoid overlaps with links of Xj, j<i.
>          One micro flow uses DSCP x0, the next one DSCP x1,... as to balance the traffic and as to avoid congestion
>          in the first place.
>

I don't think load balancing could be achieved by this way, as self-similar and asymetric distribution in internet
traffic
HH=> By utilizing an extra information (i.e. different DSCPs)we are much better of than ECMP, where source/dest. is hashed
     in a poorly way. You really get for free the routing of all packets of a particular microflow along the same route !

>

>
>
> HH:> There is never a free lunch. But what are a view routing tables compared to the probably much bigger number
> of p2p LSPs?
>

But the problem is routers have to maintein all information about DSCP they support and propagate them.
HH=> this shouldn't be a big lunch packet, right ?

>
>
> 3. If heuritic method is not feasible, go for some approximation
> methods and prove using some theoretical results. Then support your
> performance claims with some simulation results.
>
> HH=> If there is enough interest, I would be happy to show this C++-program on work.
>      As I said, it is not yet enhanced with tie breaker rules. But that would be very important as to
>      determine the same identical smallest size tree determined b whichever node. If this failed we would
>      have to continue with rambo-SPF:-)
>
> If you do all this, I will accept that your algorithm doesn't
> consititute any performance problem.
>
> HH=> No problem. Be sure, it doesn't run 10**80 years :-)

--
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 12:54:45 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21989
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 12:54:44 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA14787;
	Mon, 5 Aug 2002 12:48:50 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA14758
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 12:48:48 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21780
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 12:47:36 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id MAA05039;
	Mon, 5 Aug 2002 12:48:16 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id MAA14833;
	Mon, 5 Aug 2002 12:48:17 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99MXFL>; Mon, 5 Aug 2002 12:48:16 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632AF@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@marconi.com>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
Cc: jnc@ginger.lcs.mit.edu, fred@cisco.com, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 12:48:15 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Senthil &  Shen,

-> HH:> There is never a free lunch. But what are a view routing 
->      tables compared to the probably much bigger number
->      of p2p LSPs?

  You told/questioned about theoretical correctness of 
  DiffRouting approach. Let me tell you in what direction 
  we are moving (practically).

  If you put together everything what is happening in
  IETF WGs you will see that "indirectly" we are doing
  DiffRouting. Believe me...read on...

  Read this simple draft [in IESG last call]
  http://www.ietf.org/internet-drafts/draft-ietf-tewg-te-metric-igp-00.txt

  This draft suggest to use 2 IGP metrics (right now 
  1 in IGP Hop-by-Hop topology info and another in
  IGP-TE info) efficiently to do QoS routing.
  1 metric for Data and another metric for voice.

  What is this finally boil down to - If I provide
  this feature to SPs, think, how are they going to
  use this in DiffServ domain?
  
  Simply, SPs can map 2 different services [example,
  2 different CoS-types] to these different metrics.
  Effectively we *are* doing DiffRouting...previously
  there is no name for it...(and we are getting panicked
  that we are facing a new/unresovable/performace 
  implicated problem here). 

  To extend the idea more (from 2 metrics to n metrics)
  please read draft-fedyk-isis-ospf-te-metrics-01.txt.
  I discussed this with Francois, he said, the above
  draft also is going to get into DiffServ-aware-TE problem
  space.

  Look at this way, DiffServ-Aware-TE is more than
  DiffRouting. DiffRouting is just a subset of what we
  are solving right now.

-> But the problem is routers have to maintain all information 
-> about DSCP they support and propagate them.

  Shen, yes we are flooding all the information about DSCP
  *indirectly*.

-> 1. The diffserv architecture, as of now, defines only 
-> the data plane work.  control plane activities( routing,
-> signaling etc)  are still open questions. 

  With recent changes in TE-WG and MPLS, control plane
  is now aware of DiffServ-Aware-TE. Read...
http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-proto-01.txt


-> Thus said, coming with a new scheme is not a big task,
-> problem space and applicability statement is very 
-> important.

  I agree.

-> I am not asking you to formulate diffrout as an increment 
-> to SPF but just enlighten us *problem* and *need* of 
-> diffrout.

  As a layman (problem statement & need):
  "I (end-user) will be very happy if my voice call over IP
   performs atleast as good as over POTS (proportional to
   what I pay as monthly charges)"
 
  As a technical person (problem statement):
  - Quality of Service to End User
  - End-to-end performance
  - Efficient use of Resources
  - Congestion Avoidance & Control
    ...

  How are you going to solve above problems with out using
  DiffServ-Aware-TE (aka DiffRouting)? I am very glad
  to know your *solution*:
  -  with out letting control plane know
  -  with out propagation DSCP info (directly/indirectly)
  -  with just using SPF (with out CSPF)
  -  with out using MPLS
  . . .

  Thank you.

--
Venkata.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 12:54:45 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21996
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 12:54:45 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA15135
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 12:55:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA14787;
	Mon, 5 Aug 2002 12:48:50 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA14758
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 12:48:48 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21780
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 12:47:36 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id MAA05039;
	Mon, 5 Aug 2002 12:48:16 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id MAA14833;
	Mon, 5 Aug 2002 12:48:17 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99MXFL>; Mon, 5 Aug 2002 12:48:16 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632AF@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@marconi.com>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
Cc: jnc@ginger.lcs.mit.edu, fred@cisco.com, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 12:48:15 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Senthil &  Shen,

-> HH:> There is never a free lunch. But what are a view routing 
->      tables compared to the probably much bigger number
->      of p2p LSPs?

  You told/questioned about theoretical correctness of 
  DiffRouting approach. Let me tell you in what direction 
  we are moving (practically).

  If you put together everything what is happening in
  IETF WGs you will see that "indirectly" we are doing
  DiffRouting. Believe me...read on...

  Read this simple draft [in IESG last call]
  http://www.ietf.org/internet-drafts/draft-ietf-tewg-te-metric-igp-00.txt

  This draft suggest to use 2 IGP metrics (right now 
  1 in IGP Hop-by-Hop topology info and another in
  IGP-TE info) efficiently to do QoS routing.
  1 metric for Data and another metric for voice.

  What is this finally boil down to - If I provide
  this feature to SPs, think, how are they going to
  use this in DiffServ domain?
  
  Simply, SPs can map 2 different services [example,
  2 different CoS-types] to these different metrics.
  Effectively we *are* doing DiffRouting...previously
  there is no name for it...(and we are getting panicked
  that we are facing a new/unresovable/performace 
  implicated problem here). 

  To extend the idea more (from 2 metrics to n metrics)
  please read draft-fedyk-isis-ospf-te-metrics-01.txt.
  I discussed this with Francois, he said, the above
  draft also is going to get into DiffServ-aware-TE problem
  space.

  Look at this way, DiffServ-Aware-TE is more than
  DiffRouting. DiffRouting is just a subset of what we
  are solving right now.

-> But the problem is routers have to maintain all information 
-> about DSCP they support and propagate them.

  Shen, yes we are flooding all the information about DSCP
  *indirectly*.

-> 1. The diffserv architecture, as of now, defines only 
-> the data plane work.  control plane activities( routing,
-> signaling etc)  are still open questions. 

  With recent changes in TE-WG and MPLS, control plane
  is now aware of DiffServ-Aware-TE. Read...
http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-proto-01.txt


-> Thus said, coming with a new scheme is not a big task,
-> problem space and applicability statement is very 
-> important.

  I agree.

-> I am not asking you to formulate diffrout as an increment 
-> to SPF but just enlighten us *problem* and *need* of 
-> diffrout.

  As a layman (problem statement & need):
  "I (end-user) will be very happy if my voice call over IP
   performs atleast as good as over POTS (proportional to
   what I pay as monthly charges)"
 
  As a technical person (problem statement):
  - Quality of Service to End User
  - End-to-end performance
  - Efficient use of Resources
  - Congestion Avoidance & Control
    ...

  How are you going to solve above problems with out using
  DiffServ-Aware-TE (aka DiffRouting)? I am very glad
  to know your *solution*:
  -  with out letting control plane know
  -  with out propagation DSCP info (directly/indirectly)
  -  with just using SPF (with out CSPF)
  -  with out using MPLS
  . . .

  Thank you.

--
Venkata.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 14:08:51 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25239
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 14:08:51 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA19297;
	Mon, 5 Aug 2002 14:04:27 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA19264
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 14:04:25 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25047
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 14:03:12 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA09644;
	Mon, 5 Aug 2002 14:03:52 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA24136;
	Mon, 5 Aug 2002 14:03:53 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99M5ZL>; Mon, 5 Aug 2002 14:03:52 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632B0@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@marconi.com>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
Cc: "Naidu, Venkata" <Venkata.Naidu@marconi.com>, jnc@ginger.lcs.mit.edu,
        fred@cisco.com, irtf-rr@puck.nether.net, routing-discussion@ietf.org
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 14:03:50 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Senthil,

-> I am also sceptical of the following issues:
-> 
-> - scalability: Since you are maintaining multiple Routing
-> tables, doing at line rate is pretty difficult and hence
-> doesnt scale well.

  I agree with you here. Yes! there are performance and
  scalability problems if we go for DiffRouting in a 
  hop-by-hop fashion. Then you have to maintain
  different route tables, line rate forwarding issues etc etc.

  That is why we went for source routing (using MPLS-TE).
  That effectively solved the problem of maintaining 
  multiple routing tables. Connection-less to connection-oriented
  move (with small fixed length label lookup) solved the 
  problem of line rate forwarding (directly or indirectly).
  
  Now we are moving towards MPLS-TE with DiffServ.

  Source routing also has scalability issues. This is yet to
  be solved!

-> - complexity: This work increases the complexity at per 
-> router level. Some people complain of increase in complexity 
-> for just adding three more lines in the original forwaring algo
-> (to include RED features.) I dont know  how much complex
-> the router becomes because of diffrout.

  Weight complexity with performance.
 
-> - end to end: Diffserv is defined only for edge to edge. How will 
-> diffrout behave when considering end to end is still open.

  Yes! This is what I am concerned about.

--
Venkata.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 14:08:51 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25247
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 14:08:51 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA19787
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 14:10:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA19297;
	Mon, 5 Aug 2002 14:04:27 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA19264
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 14:04:25 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25047
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 14:03:12 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA09644;
	Mon, 5 Aug 2002 14:03:52 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA24136;
	Mon, 5 Aug 2002 14:03:53 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99M5ZL>; Mon, 5 Aug 2002 14:03:52 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632B0@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@marconi.com>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
Cc: "Naidu, Venkata" <Venkata.Naidu@marconi.com>, jnc@ginger.lcs.mit.edu,
        fred@cisco.com, irtf-rr@puck.nether.net, routing-discussion@ietf.org
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 14:03:50 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Senthil,

-> I am also sceptical of the following issues:
-> 
-> - scalability: Since you are maintaining multiple Routing
-> tables, doing at line rate is pretty difficult and hence
-> doesnt scale well.

  I agree with you here. Yes! there are performance and
  scalability problems if we go for DiffRouting in a 
  hop-by-hop fashion. Then you have to maintain
  different route tables, line rate forwarding issues etc etc.

  That is why we went for source routing (using MPLS-TE).
  That effectively solved the problem of maintaining 
  multiple routing tables. Connection-less to connection-oriented
  move (with small fixed length label lookup) solved the 
  problem of line rate forwarding (directly or indirectly).
  
  Now we are moving towards MPLS-TE with DiffServ.

  Source routing also has scalability issues. This is yet to
  be solved!

-> - complexity: This work increases the complexity at per 
-> router level. Some people complain of increase in complexity 
-> for just adding three more lines in the original forwaring algo
-> (to include RED features.) I dont know  how much complex
-> the router becomes because of diffrout.

  Weight complexity with performance.
 
-> - end to end: Diffserv is defined only for edge to edge. How will 
-> diffrout behave when considering end to end is still open.

  Yes! This is what I am concerned about.

--
Venkata.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 14:12:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25354
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 14:12:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA19496;
	Mon, 5 Aug 2002 14:07:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA19469
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 14:07:12 -0400 (EDT)
Received: from kc-msxproto2.kc.umkc.edu (kc-msxproto2.kc.umkc.edu [134.193.143.159])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25143
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 14:05:59 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 5 Aug 2002 13:07:11 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 13:07:10 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C2523@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcI8oAJQz1GKp0GMTsaMjC9TZt1HLQABLuSc
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Naidu, Venkata" <Venkata.Naidu@marconi.com>,
        "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>
Cc: <jnc@ginger.lcs.mit.edu>, <fred@cisco.com>, <irtf-rr@puck.nether.net>,
        <routing-discussion@ietf.org>
X-OriginalArrivalTime: 05 Aug 2002 18:07:11.0426 (UTC) FILETIME=[EB943220:01C23CAA]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id OAA19470
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

There are certain truths to the statements you are making, 
but the conclusions you arrive at from those threads of 
fact are incorrect/flawed. I am still doubtful about its
theoretical correctness leave alone its 
* complexity
* lack of requirements
* duplicating existing functionalities(e.g.ToS routing.)
Just go through *http://www.cs.bu.edu/fac/matta/Papers/jsac95.ps*.
They do for two TOS classes: delay and throughput in a non-FCFS
scheduling environment. you are suggesting for n- classes. 
The paper concludes based on simulations and analytical results
using liapunov functions that there is some reduction in end-to-end 
delay.
So for just coming to one conclusion, the authors have done lot 
of simulation and analytical work. But it is unfortunate that you
are making sweeping conclusions without a valid proof.
 
I will reply detaily later today.But before that clarify 
these points,
- you all accept that diffrout is not going
to solve any problem.
>-> Thus said, coming with a new scheme is not a big task,
>-> problem space and applicability statement is very
>-> important.
>  I agree.
 
- It is complex.
>HH:> There is never a free lunch. But what are a view routing 
>tables compared to the probably much bigger number
>of p2p LSPs?


 
 
 
 
 

	
	


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 14:12:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25361
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 14:12:27 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA19941
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 14:13:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA19496;
	Mon, 5 Aug 2002 14:07:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA19469
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 14:07:12 -0400 (EDT)
Received: from kc-msxproto2.kc.umkc.edu (kc-msxproto2.kc.umkc.edu [134.193.143.159])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25143
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 14:05:59 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 5 Aug 2002 13:07:11 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 13:07:10 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C2523@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcI8oAJQz1GKp0GMTsaMjC9TZt1HLQABLuSc
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Naidu, Venkata" <Venkata.Naidu@marconi.com>,
        "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>
Cc: <jnc@ginger.lcs.mit.edu>, <fred@cisco.com>, <irtf-rr@puck.nether.net>,
        <routing-discussion@ietf.org>
X-OriginalArrivalTime: 05 Aug 2002 18:07:11.0426 (UTC) FILETIME=[EB943220:01C23CAA]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id OAA19470
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

There are certain truths to the statements you are making, 
but the conclusions you arrive at from those threads of 
fact are incorrect/flawed. I am still doubtful about its
theoretical correctness leave alone its 
* complexity
* lack of requirements
* duplicating existing functionalities(e.g.ToS routing.)
Just go through *http://www.cs.bu.edu/fac/matta/Papers/jsac95.ps*.
They do for two TOS classes: delay and throughput in a non-FCFS
scheduling environment. you are suggesting for n- classes. 
The paper concludes based on simulations and analytical results
using liapunov functions that there is some reduction in end-to-end 
delay.
So for just coming to one conclusion, the authors have done lot 
of simulation and analytical work. But it is unfortunate that you
are making sweeping conclusions without a valid proof.
 
I will reply detaily later today.But before that clarify 
these points,
- you all accept that diffrout is not going
to solve any problem.
>-> Thus said, coming with a new scheme is not a big task,
>-> problem space and applicability statement is very
>-> important.
>  I agree.
 
- It is complex.
>HH:> There is never a free lunch. But what are a view routing 
>tables compared to the probably much bigger number
>of p2p LSPs?


 
 
 
 
 

	
	


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 14:27:52 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25793
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 14:27:52 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA20326;
	Mon, 5 Aug 2002 14:23:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA20302
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 14:23:04 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25592
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 14:21:51 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA10707;
	Mon, 5 Aug 2002 14:22:31 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA01500;
	Mon, 5 Aug 2002 14:22:33 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99M67Z>; Mon, 5 Aug 2002 14:22:32 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632B2@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@marconi.com>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
Cc: jnc@ginger.lcs.mit.edu, fred@cisco.com, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 14:22:31 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Senthil,

-> Just go through *http://www.cs.bu.edu/fac/matta/Papers/jsac95.ps*.
-> They do for two TOS classes: delay and throughput in a non-FCFS
-> scheduling environment. you are suggesting for n- classes. 
-> The paper concludes based on simulations and analytical results
-> using liapunov functions that there is some reduction in end-to-end 
                                          ^^^^

-> delay.
-> So for just coming to one conclusion, the authors have done lot 
-> of simulation and analytical work. But it is unfortunate that you
-> are making sweeping conclusions without a valid proof.
  
  You misunderstood me. I am not concluding anything. 
  I am giving my own view in a different perspective and 
  letting you know how we can co-relate recent events.

  Let me go through the above paper - I will get back to you.

-> I will reply detaily later today.But before that clarify 
-> these points,
-> - you all accept that diffrout is not going to solve any problem.
                                                        ^^^
  
  Let us see :) You are contradicting your-self. Just in the above
  para you said "SOME reduction in end-to-end performance" and
  again said "diffrout is not going to solve ANY problem".

  If that SOME reduction is tolerable then, I think, we solved
  SOME problem. Thus I can prove that that statement 
  "diffrout is not going to solve ANY problem" is incorrect.

--
Venkata

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 14:27:52 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25802
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 14:27:52 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA20784
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 14:29:04 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA20326;
	Mon, 5 Aug 2002 14:23:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA20302
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 14:23:04 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25592
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 14:21:51 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA10707;
	Mon, 5 Aug 2002 14:22:31 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA01500;
	Mon, 5 Aug 2002 14:22:33 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99M67Z>; Mon, 5 Aug 2002 14:22:32 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632B2@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@marconi.com>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
Cc: jnc@ginger.lcs.mit.edu, fred@cisco.com, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 14:22:31 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Senthil,

-> Just go through *http://www.cs.bu.edu/fac/matta/Papers/jsac95.ps*.
-> They do for two TOS classes: delay and throughput in a non-FCFS
-> scheduling environment. you are suggesting for n- classes. 
-> The paper concludes based on simulations and analytical results
-> using liapunov functions that there is some reduction in end-to-end 
                                          ^^^^

-> delay.
-> So for just coming to one conclusion, the authors have done lot 
-> of simulation and analytical work. But it is unfortunate that you
-> are making sweeping conclusions without a valid proof.
  
  You misunderstood me. I am not concluding anything. 
  I am giving my own view in a different perspective and 
  letting you know how we can co-relate recent events.

  Let me go through the above paper - I will get back to you.

-> I will reply detaily later today.But before that clarify 
-> these points,
-> - you all accept that diffrout is not going to solve any problem.
                                                        ^^^
  
  Let us see :) You are contradicting your-self. Just in the above
  para you said "SOME reduction in end-to-end performance" and
  again said "diffrout is not going to solve ANY problem".

  If that SOME reduction is tolerable then, I think, we solved
  SOME problem. Thus I can prove that that statement 
  "diffrout is not going to solve ANY problem" is incorrect.

--
Venkata

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 14:28:47 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25877
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 14:28:47 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA20232;
	Mon, 5 Aug 2002 14:21:04 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA20203
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 14:21:02 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25544
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 14:19:49 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA10536;
	Mon, 5 Aug 2002 14:20:29 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA00911;
	Mon, 5 Aug 2002 14:20:26 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99M65C>; Mon, 5 Aug 2002 14:20:25 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632B1@vie-msgusr-01.dc.fore.com>
From: =?utf-8?B?TmFpZHUsIFZlbmthdGE=?= <Venkata.Naidu@marconi.com>
To: =?utf-8?B?J0F5eWFzYW15LCBTZW50aGlsa3VtYXIgIChVTUtDLVN0dWRlbnQpJw==?=
	 <saq66@umkc.edu>,
        =?utf-8?B?TmFpZHUsIFZlbmthdGE=?=
	 <Venkata.Naidu@marconi.com>,
        =?utf-8?B?SHVtbWVsIEhlaW5yaWNo?=
	 <Heinrich.Hummel@icn.siemens.de>
Cc: jnc@ginger.lcs.mit.edu, fred@cisco.com, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: =?utf-8?B?UkU6IERpZmZlcmVudGlhdGVkIFJvdXRpbmcsIG5vdCBvbmx5IHBs?=
	=?utf-8?B?YWluIHJhbWJvLVNQRg==?=
Date: Mon, 5 Aug 2002 14:20:25 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="utf-8"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Senthil,

-> Just go through *http://www.cs.bu.edu/fac/matta/Papers/jsac95.ps*.
-> They do for two TOS classes: delay and throughput in a non-FCFS
-> scheduling environment. you are suggesting for n- classes. 
-> The paper concludes based on simulations and analytical results
-> using liapunov functions that there is some reduction in end-to-end 
                                          ^^^^

-> delay.
-> So for just coming to one conclusion, the authors have done lot 
-> of simulation and analytical work. But it is unfortunate that you
-> are making sweeping conclusions without a valid proof.
  
  You misunderstood me. I am not concluding anything. 
  I am giving my own view in a different perspective and 
  letting you know how we can co-relate recent events.

  Let me go through the above paper - I will get back to you.

-> I will reply detaily later today.But before that clarify 
-> these points,
-> - you all accept that diffrout is not going to solve any problem.
                                                        ^^^
  
  Let us see :) You are contradicting your-self. Just in the above
  para you said "SOME reduction in end-to-end performance" and
  again said "diffrout is not going to solve ANY problem".

  If that SOME reduction is tolerable then, I think, we solved
  SOME problem. Thus I can prove that that statement 
  "diffrout is not going to solve ANY problem" is incorrect.

--
Venkata
 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 14:28:48 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25887
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 14:28:47 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA20915
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 14:29:59 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA20232;
	Mon, 5 Aug 2002 14:21:04 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA20203
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 14:21:02 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25544
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 14:19:49 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA10536;
	Mon, 5 Aug 2002 14:20:29 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA00911;
	Mon, 5 Aug 2002 14:20:26 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99M65C>; Mon, 5 Aug 2002 14:20:25 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632B1@vie-msgusr-01.dc.fore.com>
From: =?utf-8?B?TmFpZHUsIFZlbmthdGE=?= <Venkata.Naidu@marconi.com>
To: =?utf-8?B?J0F5eWFzYW15LCBTZW50aGlsa3VtYXIgIChVTUtDLVN0dWRlbnQpJw==?=
	 <saq66@umkc.edu>,
        =?utf-8?B?TmFpZHUsIFZlbmthdGE=?=
	 <Venkata.Naidu@marconi.com>,
        =?utf-8?B?SHVtbWVsIEhlaW5yaWNo?=
	 <Heinrich.Hummel@icn.siemens.de>
Cc: jnc@ginger.lcs.mit.edu, fred@cisco.com, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: =?utf-8?B?UkU6IERpZmZlcmVudGlhdGVkIFJvdXRpbmcsIG5vdCBvbmx5IHBs?=
	=?utf-8?B?YWluIHJhbWJvLVNQRg==?=
Date: Mon, 5 Aug 2002 14:20:25 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="utf-8"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Senthil,

-> Just go through *http://www.cs.bu.edu/fac/matta/Papers/jsac95.ps*.
-> They do for two TOS classes: delay and throughput in a non-FCFS
-> scheduling environment. you are suggesting for n- classes. 
-> The paper concludes based on simulations and analytical results
-> using liapunov functions that there is some reduction in end-to-end 
                                          ^^^^

-> delay.
-> So for just coming to one conclusion, the authors have done lot 
-> of simulation and analytical work. But it is unfortunate that you
-> are making sweeping conclusions without a valid proof.
  
  You misunderstood me. I am not concluding anything. 
  I am giving my own view in a different perspective and 
  letting you know how we can co-relate recent events.

  Let me go through the above paper - I will get back to you.

-> I will reply detaily later today.But before that clarify 
-> these points,
-> - you all accept that diffrout is not going to solve any problem.
                                                        ^^^
  
  Let us see :) You are contradicting your-self. Just in the above
  para you said "SOME reduction in end-to-end performance" and
  again said "diffrout is not going to solve ANY problem".

  If that SOME reduction is tolerable then, I think, we solved
  SOME problem. Thus I can prove that that statement 
  "diffrout is not going to solve ANY problem" is incorrect.

--
Venkata
 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 14:32:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26145
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 14:32:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA20605;
	Mon, 5 Aug 2002 14:26:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA20579
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 14:26:49 -0400 (EDT)
Received: from kc-msxproto4.kc.umkc.edu (kc-msxproto4.kc.umkc.edu [134.193.143.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25720
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 14:25:36 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 5 Aug 2002 13:26:47 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 13:26:46 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C2526@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcI8qrS9RFP22RL5QkCgVgbVRxxWIQAAkdNY
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Naidu, Venkata" <Venkata.Naidu@marconi.com>,
        "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>
Cc: "Naidu, Venkata" <Venkata.Naidu@marconi.com>, <jnc@ginger.lcs.mit.edu>,
        <fred@cisco.com>, <irtf-rr@puck.nether.net>,
        <routing-discussion@ietf.org>
X-OriginalArrivalTime: 05 Aug 2002 18:26:47.0222 (UTC) FILETIME=[A8686D60:01C23CAD]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id OAA20580
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

>  -> - scalability: Since you are maintaining multiple Routing
> -> tables, doing at line rate is pretty difficult and hence
> -> doesnt scale well.
> I agree with you here. Yes! there are performance and
> scalability problems if we go for DiffRouting in a
> hop-by-hop fashion. Then you have to maintain
> different route tables, line rate forwarding issues etc etc.
>
> That is why we went for source routing (using MPLS-TE).
> That effectively solved the problem of maintaining
> multiple routing tables. Connection-less to connection-oriented
> move (with small fixed length label lookup) solved the
> problem of line rate forwarding (directly or indirectly).
> 
>  Now we are moving towards MPLS-TE with DiffServ.
who told you diffserv-aware MPLS -TE scalable? 
Section 4.4 and 3.1 of http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-reqts-05.txt clearly points out the scalability problems.
  

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 14:32:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26153
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 14:32:27 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA21713
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 14:33:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA20605;
	Mon, 5 Aug 2002 14:26:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA20579
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 14:26:49 -0400 (EDT)
Received: from kc-msxproto4.kc.umkc.edu (kc-msxproto4.kc.umkc.edu [134.193.143.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25720
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 14:25:36 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 5 Aug 2002 13:26:47 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 13:26:46 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C2526@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcI8qrS9RFP22RL5QkCgVgbVRxxWIQAAkdNY
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Naidu, Venkata" <Venkata.Naidu@marconi.com>,
        "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>
Cc: "Naidu, Venkata" <Venkata.Naidu@marconi.com>, <jnc@ginger.lcs.mit.edu>,
        <fred@cisco.com>, <irtf-rr@puck.nether.net>,
        <routing-discussion@ietf.org>
X-OriginalArrivalTime: 05 Aug 2002 18:26:47.0222 (UTC) FILETIME=[A8686D60:01C23CAD]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id OAA20580
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

>  -> - scalability: Since you are maintaining multiple Routing
> -> tables, doing at line rate is pretty difficult and hence
> -> doesnt scale well.
> I agree with you here. Yes! there are performance and
> scalability problems if we go for DiffRouting in a
> hop-by-hop fashion. Then you have to maintain
> different route tables, line rate forwarding issues etc etc.
>
> That is why we went for source routing (using MPLS-TE).
> That effectively solved the problem of maintaining
> multiple routing tables. Connection-less to connection-oriented
> move (with small fixed length label lookup) solved the
> problem of line rate forwarding (directly or indirectly).
> 
>  Now we are moving towards MPLS-TE with DiffServ.
who told you diffserv-aware MPLS -TE scalable? 
Section 4.4 and 3.1 of http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-reqts-05.txt clearly points out the scalability problems.
  

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 14:41:59 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26762
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 14:41:58 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21919;
	Mon, 5 Aug 2002 14:36:23 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21893
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 14:36:21 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26368
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 14:35:08 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA11645;
	Mon, 5 Aug 2002 14:35:39 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA07502;
	Mon, 5 Aug 2002 14:35:40 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99M7Z7>; Mon, 5 Aug 2002 14:35:40 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632B3@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@marconi.com>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
Cc: jnc@ginger.lcs.mit.edu, fred@cisco.com, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 14:35:38 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Senthil,
 
-> >  Now we are moving towards MPLS-TE with DiffServ.
-> who told you diffserv-aware MPLS -TE scalable? 
-> Section 4.4 and 3.1 of 
-> http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-r
-> eqts-05.txt clearly points out the scalability problems.

  You clipped out my next line. I didn't say that DiffServ-Aware-
  MPLS-TE is scalable. I also said the same thing:
     
  " Source routing also has scalability issues. This is yet to
  be solved! "

  So, are you saying that:
  There is no difference between MPLS-TE and DiffServ-aware-MPLS-TE?
  In other words, are you saying that Differv-aware-MPLS-TE is not
  going solve ANY problem that MPLS-TE alone couldn't solve ?

--
Venkata

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 14:41:59 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26771
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 14:41:59 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA22314
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 14:43:11 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21919;
	Mon, 5 Aug 2002 14:36:23 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21893
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 14:36:21 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26368
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 14:35:08 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA11645;
	Mon, 5 Aug 2002 14:35:39 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA07502;
	Mon, 5 Aug 2002 14:35:40 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99M7Z7>; Mon, 5 Aug 2002 14:35:40 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632B3@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@marconi.com>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
Cc: jnc@ginger.lcs.mit.edu, fred@cisco.com, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 14:35:38 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Senthil,
 
-> >  Now we are moving towards MPLS-TE with DiffServ.
-> who told you diffserv-aware MPLS -TE scalable? 
-> Section 4.4 and 3.1 of 
-> http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-r
-> eqts-05.txt clearly points out the scalability problems.

  You clipped out my next line. I didn't say that DiffServ-Aware-
  MPLS-TE is scalable. I also said the same thing:
     
  " Source routing also has scalability issues. This is yet to
  be solved! "

  So, are you saying that:
  There is no difference between MPLS-TE and DiffServ-aware-MPLS-TE?
  In other words, are you saying that Differv-aware-MPLS-TE is not
  going solve ANY problem that MPLS-TE alone couldn't solve ?

--
Venkata

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 14:53:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27169
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 14:53:52 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA22507;
	Mon, 5 Aug 2002 14:49:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA22480
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 14:49:08 -0400 (EDT)
Received: from kc-msxproto4.kc.umkc.edu (kc-msxproto4.kc.umkc.edu [134.193.143.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26997
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 14:47:55 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 5 Aug 2002 13:49:07 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 13:49:07 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C2527@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcI8rSypIdCUfeI9RGC/lA8WVIZE/gAAJ/9p
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Naidu, Venkata" <Venkata.Naidu@marconi.com>,
        "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>
Cc: <jnc@ginger.lcs.mit.edu>, <fred@cisco.com>, <irtf-rr@puck.nether.net>,
        <routing-discussion@ietf.org>
X-OriginalArrivalTime: 05 Aug 2002 18:49:07.0689 (UTC) FILETIME=[C7637590:01C23CB0]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id OAA22482
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

>Let us see :) You are contradicting your-self. Just in the above
>para you said "SOME reduction in end-to-end performance" and
>again said "diffrout is not going to solve ANY problem".
end to end performance reduction is authors view. My comments were
more particular towards *diffrout* than *ToS routing*. diffrout
is suggesting n-class whereas ToS routing just two classes. you are 
mixing author's ToS scheme with your suggestions. diffrout is not
scalable when compared to ToS routing. So talk about your proposal
(diffrout) than ToS routing.

>If that SOME reduction is tolerable then, I think, we solved
>SOME problem. Thus I can prove that that statement
>"diffrout is not going to solve ANY problem" is incorrect.
which problem you have solved here? If you consider end to end 
delay as major problem that diffrout is going to solve, first let
us work with NSIS group to define the signaling mechanism and define
some per-domain behaviour, develop some inter-domain business models 
and then we will solve the problem of e2e delay across a diffserv 
network.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 14:53:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27174
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 14:53:53 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA22784
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 14:55:05 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA22507;
	Mon, 5 Aug 2002 14:49:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA22480
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 14:49:08 -0400 (EDT)
Received: from kc-msxproto4.kc.umkc.edu (kc-msxproto4.kc.umkc.edu [134.193.143.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26997
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 14:47:55 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 5 Aug 2002 13:49:07 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 13:49:07 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C2527@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcI8rSypIdCUfeI9RGC/lA8WVIZE/gAAJ/9p
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Naidu, Venkata" <Venkata.Naidu@marconi.com>,
        "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>
Cc: <jnc@ginger.lcs.mit.edu>, <fred@cisco.com>, <irtf-rr@puck.nether.net>,
        <routing-discussion@ietf.org>
X-OriginalArrivalTime: 05 Aug 2002 18:49:07.0689 (UTC) FILETIME=[C7637590:01C23CB0]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id OAA22482
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

>Let us see :) You are contradicting your-self. Just in the above
>para you said "SOME reduction in end-to-end performance" and
>again said "diffrout is not going to solve ANY problem".
end to end performance reduction is authors view. My comments were
more particular towards *diffrout* than *ToS routing*. diffrout
is suggesting n-class whereas ToS routing just two classes. you are 
mixing author's ToS scheme with your suggestions. diffrout is not
scalable when compared to ToS routing. So talk about your proposal
(diffrout) than ToS routing.

>If that SOME reduction is tolerable then, I think, we solved
>SOME problem. Thus I can prove that that statement
>"diffrout is not going to solve ANY problem" is incorrect.
which problem you have solved here? If you consider end to end 
delay as major problem that diffrout is going to solve, first let
us work with NSIS group to define the signaling mechanism and define
some per-domain behaviour, develop some inter-domain business models 
and then we will solve the problem of e2e delay across a diffserv 
network.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 15:02:15 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27647
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 15:02:15 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA22883;
	Mon, 5 Aug 2002 14:57:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA22853
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 14:57:03 -0400 (EDT)
Received: from kc-msxproto2.kc.umkc.edu (kc-msxproto2.kc.umkc.edu [134.193.143.159])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27294
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 14:55:50 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 5 Aug 2002 13:57:01 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 13:57:01 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C2528@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcI8rwht6ksrHpBIQbuUTbewf4dHSQAAfsGQ
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Naidu, Venkata" <Venkata.Naidu@marconi.com>,
        "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>
Cc: <jnc@ginger.lcs.mit.edu>, <fred@cisco.com>, <irtf-rr@puck.nether.net>,
        <routing-discussion@ietf.org>
X-OriginalArrivalTime: 05 Aug 2002 18:57:02.0143 (UTC) FILETIME=[E22F64F0:01C23CB1]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id OAA22854
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

> There is no difference between MPLS-TE and DiffServ-aware-MPLS-> TE? In other 
> words, are you saying that Differv-aware-MPLS-TE 
> is notgoing solve ANY problem that MPLS-TE alone couldn't 
> solve ?
I was just talking about diffserv aware MPLS TE which is more related to 
the context of discussion. The authors of diffserv MPLS TE draft discusses 
scalability problems.



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 15:02:15 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27656
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 15:02:15 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA23664
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 15:03:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA22883;
	Mon, 5 Aug 2002 14:57:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA22853
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 14:57:03 -0400 (EDT)
Received: from kc-msxproto2.kc.umkc.edu (kc-msxproto2.kc.umkc.edu [134.193.143.159])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27294
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 14:55:50 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 5 Aug 2002 13:57:01 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 13:57:01 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C2528@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcI8rwht6ksrHpBIQbuUTbewf4dHSQAAfsGQ
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Naidu, Venkata" <Venkata.Naidu@marconi.com>,
        "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>
Cc: <jnc@ginger.lcs.mit.edu>, <fred@cisco.com>, <irtf-rr@puck.nether.net>,
        <routing-discussion@ietf.org>
X-OriginalArrivalTime: 05 Aug 2002 18:57:02.0143 (UTC) FILETIME=[E22F64F0:01C23CB1]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id OAA22854
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

> There is no difference between MPLS-TE and DiffServ-aware-MPLS-> TE? In other 
> words, are you saying that Differv-aware-MPLS-TE 
> is notgoing solve ANY problem that MPLS-TE alone couldn't 
> solve ?
I was just talking about diffserv aware MPLS TE which is more related to 
the context of discussion. The authors of diffserv MPLS TE draft discusses 
scalability problems.



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 15:44:23 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29090
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 15:44:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA25125;
	Mon, 5 Aug 2002 15:33:53 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA25095
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 15:33:50 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28745
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 15:32:36 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id PAA15672;
	Mon, 5 Aug 2002 15:33:16 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id PAA00081;
	Mon, 5 Aug 2002 15:33:17 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99NATJ>; Mon, 5 Aug 2002 15:33:16 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632B5@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@marconi.com>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
Cc: jnc@ginger.lcs.mit.edu, fred@cisco.com, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 15:33:15 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Senthil,

-> > There is no difference between MPLS-TE and 
-> DiffServ-aware-MPLS-> TE? In other 
-> > words, are you saying that Differv-aware-MPLS-TE 
-> > is notgoing solve ANY problem that MPLS-TE alone couldn't 
-> > solve ?
-> I was just talking about diffserv aware MPLS TE which is 
-> more related to 
-> the context of discussion. The authors of diffserv MPLS TE 
-> draft discusses scalability problems.

  Yes! I am also talking about DiffServ-aware-MPLS-TE.
  In the draft-ietf-tewg-diff-te-reqts-05.txt authors
  clearly mentioned about problem statement and how we
  can benefit from DiffServ-aware-MPLS-TE (even if there
  are some scalability issues). Effectively, authors
  are trying to solve SOME problem - then how can 
  you can say that DiffServ-aware-MPLS-TE (aka DiffRouting)
  is not going to solve ANY problem.

  Scalability issues in TOS Routing are different
  from scalability issues in DiffRouting (if you consider
  TOS routing is applicable in traditional hop-by-hop
  routing case and DiffRouting is applicable in todays
  source routing cases).

  Finally, let me conclude what I agree and disagree
  with you.

  What I agree:
  - None of these approaches [traditional TOS-Routing or
    DiffRouting (DiffServ-aware-MPLS-TE)] really solve
    end-to-end QoS/Performance. I already expressed this
    concern to Fred Baker (which he concluded that as
    an open ended question) - which is fine!
http://www1.ietf.org/mail-archive/working-groups/routing-discussion/current/
msg00060.html

  - None of the above approaches are complete. They have
    some common and some different issues - for example
    scalability etc etc

  What I don't agree (my view):
  - Just because a solution has scalability issues doesn't
    mean that that solution is not going to solve ANY 
    problem.

  - Diffserv-aware-MPLS-TE is trying to solve different problems
    which we couldn't solve with traditional routing approaches
    *easily* in the past.

  - We are trying to solve (we will solve) those scalability
    issues in source routing (using hierarchical TE etc etc)
    in future.

  Do you agree? If not let me know - let us discuss :)

  If you still feel that DiffRouting is not going to solve 
  ANY problem then I will ask authors of 
  draft-ietf-tewg-diff-te-reqts-05.txt (for clarification).
  
  Finally, you didn't tell me in what other approaches
  we can solve the same issues that the DiffServ-TE is
  trying to solve (with out letting control plane know,
  with out CSPF, with out connection-oriented MPLS etc etc).
  
--
Venkata

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 15:44:23 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29097
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 15:44:23 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA25537
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 15:45:36 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA25125;
	Mon, 5 Aug 2002 15:33:53 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA25095
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 15:33:50 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28745
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 15:32:36 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id PAA15672;
	Mon, 5 Aug 2002 15:33:16 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id PAA00081;
	Mon, 5 Aug 2002 15:33:17 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99NATJ>; Mon, 5 Aug 2002 15:33:16 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632B5@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@marconi.com>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
Cc: jnc@ginger.lcs.mit.edu, fred@cisco.com, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 15:33:15 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Senthil,

-> > There is no difference between MPLS-TE and 
-> DiffServ-aware-MPLS-> TE? In other 
-> > words, are you saying that Differv-aware-MPLS-TE 
-> > is notgoing solve ANY problem that MPLS-TE alone couldn't 
-> > solve ?
-> I was just talking about diffserv aware MPLS TE which is 
-> more related to 
-> the context of discussion. The authors of diffserv MPLS TE 
-> draft discusses scalability problems.

  Yes! I am also talking about DiffServ-aware-MPLS-TE.
  In the draft-ietf-tewg-diff-te-reqts-05.txt authors
  clearly mentioned about problem statement and how we
  can benefit from DiffServ-aware-MPLS-TE (even if there
  are some scalability issues). Effectively, authors
  are trying to solve SOME problem - then how can 
  you can say that DiffServ-aware-MPLS-TE (aka DiffRouting)
  is not going to solve ANY problem.

  Scalability issues in TOS Routing are different
  from scalability issues in DiffRouting (if you consider
  TOS routing is applicable in traditional hop-by-hop
  routing case and DiffRouting is applicable in todays
  source routing cases).

  Finally, let me conclude what I agree and disagree
  with you.

  What I agree:
  - None of these approaches [traditional TOS-Routing or
    DiffRouting (DiffServ-aware-MPLS-TE)] really solve
    end-to-end QoS/Performance. I already expressed this
    concern to Fred Baker (which he concluded that as
    an open ended question) - which is fine!
http://www1.ietf.org/mail-archive/working-groups/routing-discussion/current/
msg00060.html

  - None of the above approaches are complete. They have
    some common and some different issues - for example
    scalability etc etc

  What I don't agree (my view):
  - Just because a solution has scalability issues doesn't
    mean that that solution is not going to solve ANY 
    problem.

  - Diffserv-aware-MPLS-TE is trying to solve different problems
    which we couldn't solve with traditional routing approaches
    *easily* in the past.

  - We are trying to solve (we will solve) those scalability
    issues in source routing (using hierarchical TE etc etc)
    in future.

  Do you agree? If not let me know - let us discuss :)

  If you still feel that DiffRouting is not going to solve 
  ANY problem then I will ask authors of 
  draft-ietf-tewg-diff-te-reqts-05.txt (for clarification).
  
  Finally, you didn't tell me in what other approaches
  we can solve the same issues that the DiffServ-TE is
  trying to solve (with out letting control plane know,
  with out CSPF, with out connection-oriented MPLS etc etc).
  
--
Venkata

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 20:41:52 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09297
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 20:41:52 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA09667;
	Mon, 5 Aug 2002 20:36:18 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA09637
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 20:36:16 -0400 (EDT)
Received: from kc-msxproto4.kc.umkc.edu (kc-msxproto4.kc.umkc.edu [134.193.143.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09125
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 20:35:04 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 5 Aug 2002 19:36:16 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 19:36:15 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C252A@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcI8tw/6mhAKwU3bQ0C8tvoQga4Q+wAI3MbQ
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Naidu, Venkata" <Venkata.Naidu@marconi.com>,
        "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>
Cc: <jnc@ginger.lcs.mit.edu>, <fred@cisco.com>, <irtf-rr@puck.nether.net>,
        <routing-discussion@ietf.org>
X-OriginalArrivalTime: 06 Aug 2002 00:36:16.0169 (UTC) FILETIME=[46214990:01C23CE1]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id UAA09638
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit


>   I am also talking about DiffServ-aware-MPLS-TE.
>   In the draft-ietf-tewg-diff-te-reqts-05.txt authors
>   clearly mentioned about problem statement and how we
>   can benefit from DiffServ-aware-MPLS-TE (even if there
>   are some scalability issues). Effectively, authors
>   are trying to solve SOME problem - then how can 
>   you can say that DiffServ-aware-MPLS-TE (aka DiffRouting)
>   is not going to solve ANY problem.
Diffserv aware MPLS TE draft doesn't call for bar on SPF. But
you people are keeping that as a subject and discussing.

Some of the definitions and road examples of diffrout doesn't fit 
the bill of diffserv aware MPLS TE. 

As of now, whatever techniques standardized by TE-WG, is applicable
only for intra-domain (including diffserv-aware TE.) But read some 
of your mails, you talk about end to end issues.

Do you get your problem now? If you are not clear with your problem
statement, you will tent to make deviating observations.

If Diffserv-aware-MPLS-TE = diffrout, I am in full agreement with some 
of your views. But remember again, you made some comments about end to end 
delay issues which even Faucheur et all won't accept. 

Hummel, was your original proposal same like Diffserv-aware-TE. I thought
it was different.


> 
>   Scalability issues in TOS Routing are different
>   from scalability issues in DiffRouting (if you consider
>   TOS routing is applicable in traditional hop-by-hop
>   routing case and DiffRouting is applicable in todays
>   source routing cases).

Yup ..its different. you have used some of the ToS routing 
conclusions for claiming diffrout scheme and hence, i made that
comment regarding scalability. 


>  What I don't agree (my view):
>  - Just because a solution has scalability issues doesn't
>    mean that that solution is not going to solve ANY 
>    problem.

Sorry for making such a statement. But you should also agree 
that, you did not still clearly state *why we need diffrout?*

>  Finally, you didn't tell me in what other approaches
>  we can solve the same issues that the DiffServ-TE is
>  trying to solve (with out letting control plane know,
>  with out CSPF, with out connection-oriented MPLS etc etc).
First of all control plane work in Diffserv is incomplete. 
what you want to do with *diffrout*-QoS-Routing, sneak-around 
the congestion-area routing, and traffic balanced routing.

Let me suggest you a simple technique: Use *explicit routing* of
MPLS which is the simplese one for doing sneaking around work.

Doing dynamic QoS routing is very difficult and operators 
generally dont prefer. But this is surely not a good argument :-).
i will support diffrout if you just explain me *why we need 
diffrout*. I am reading all the 14 mails regarding diffrout but 
still couldn't get a correct problem statement.

In the corner, I am too advocating a new idea which is  contradictory
to diffrout. By taking SPF into account, an effective load balancing 
can be done in diffserv architecture. I will get back to you once i get 
done with an analytical model.


  

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 20:41:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09306
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 20:41:53 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA09881
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 20:43:04 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA09667;
	Mon, 5 Aug 2002 20:36:18 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA09637
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 20:36:16 -0400 (EDT)
Received: from kc-msxproto4.kc.umkc.edu (kc-msxproto4.kc.umkc.edu [134.193.143.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09125
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 20:35:04 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 5 Aug 2002 19:36:16 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 5 Aug 2002 19:36:15 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C252A@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcI8tw/6mhAKwU3bQ0C8tvoQga4Q+wAI3MbQ
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Naidu, Venkata" <Venkata.Naidu@marconi.com>,
        "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>
Cc: <jnc@ginger.lcs.mit.edu>, <fred@cisco.com>, <irtf-rr@puck.nether.net>,
        <routing-discussion@ietf.org>
X-OriginalArrivalTime: 06 Aug 2002 00:36:16.0169 (UTC) FILETIME=[46214990:01C23CE1]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id UAA09638
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit


>   I am also talking about DiffServ-aware-MPLS-TE.
>   In the draft-ietf-tewg-diff-te-reqts-05.txt authors
>   clearly mentioned about problem statement and how we
>   can benefit from DiffServ-aware-MPLS-TE (even if there
>   are some scalability issues). Effectively, authors
>   are trying to solve SOME problem - then how can 
>   you can say that DiffServ-aware-MPLS-TE (aka DiffRouting)
>   is not going to solve ANY problem.
Diffserv aware MPLS TE draft doesn't call for bar on SPF. But
you people are keeping that as a subject and discussing.

Some of the definitions and road examples of diffrout doesn't fit 
the bill of diffserv aware MPLS TE. 

As of now, whatever techniques standardized by TE-WG, is applicable
only for intra-domain (including diffserv-aware TE.) But read some 
of your mails, you talk about end to end issues.

Do you get your problem now? If you are not clear with your problem
statement, you will tent to make deviating observations.

If Diffserv-aware-MPLS-TE = diffrout, I am in full agreement with some 
of your views. But remember again, you made some comments about end to end 
delay issues which even Faucheur et all won't accept. 

Hummel, was your original proposal same like Diffserv-aware-TE. I thought
it was different.


> 
>   Scalability issues in TOS Routing are different
>   from scalability issues in DiffRouting (if you consider
>   TOS routing is applicable in traditional hop-by-hop
>   routing case and DiffRouting is applicable in todays
>   source routing cases).

Yup ..its different. you have used some of the ToS routing 
conclusions for claiming diffrout scheme and hence, i made that
comment regarding scalability. 


>  What I don't agree (my view):
>  - Just because a solution has scalability issues doesn't
>    mean that that solution is not going to solve ANY 
>    problem.

Sorry for making such a statement. But you should also agree 
that, you did not still clearly state *why we need diffrout?*

>  Finally, you didn't tell me in what other approaches
>  we can solve the same issues that the DiffServ-TE is
>  trying to solve (with out letting control plane know,
>  with out CSPF, with out connection-oriented MPLS etc etc).
First of all control plane work in Diffserv is incomplete. 
what you want to do with *diffrout*-QoS-Routing, sneak-around 
the congestion-area routing, and traffic balanced routing.

Let me suggest you a simple technique: Use *explicit routing* of
MPLS which is the simplese one for doing sneaking around work.

Doing dynamic QoS routing is very difficult and operators 
generally dont prefer. But this is surely not a good argument :-).
i will support diffrout if you just explain me *why we need 
diffrout*. I am reading all the 14 mails regarding diffrout but 
still couldn't get a correct problem statement.

In the corner, I am too advocating a new idea which is  contradictory
to diffrout. By taking SPF into account, an effective load balancing 
can be done in diffserv architecture. I will get back to you once i get 
done with an analytical model.


  

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 22:09:29 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11597
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 22:09:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA14760;
	Mon, 5 Aug 2002 22:04:55 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04273
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 10:02:17 -0400 (EDT)
Received: from mail.cad.zju.edu.cn (cad.zju.edu.cn [210.32.131.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA13874
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 10:01:01 -0400 (EDT)
Received: (qmail 10418 invoked from network); 5 Aug 2002 14:07:09 -0000
Received: from unknown (HELO cad.zju.edu.cn) (210.32.131.97)
  by 210.32.131.2 with SMTP; 5 Aug 2002 14:07:09 -0000
Message-ID: <3D4E854E.A96D0FC2@cad.zju.edu.cn>
Date: Mon, 05 Aug 2002 22:01:50 +0800
From: shen jing <jshen@cad.zju.edu.cn>
Reply-To: jshen@cad.zju.edu.cn
Organization: State Key Lab of CAD&CG
X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: Re:  Differentiated Routing, not only plain rambo-SPF
References: <EF8E39AA846CD411BB9C00508B951F510514B97B@MCHH267E>
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 7bit

Hummel ,


> HH=> a) With respect to a particular road system X , you may determine a respective overflow road system X-overflow.
>         E.g. you may determine by computation the cernel of a smallest size tree being that set of links
>         which are used by at least y  s/d-traffic combinations, whereby n < y < n*(n-1); y be a fixed assigned number.
>         You may recompute the smallest size tree, but before, you want to mark all the cernel links to DISREGARD.
>         Traffic which is about to enter the cernel of X, may be forwarded via X-overflow while changing the
>         receive DSCP-x to DSCP-x-overflow. The decission to do so may be based on a currently available traffic load/
>         traffic metering information.
>

what's the meaning of "cernel"? I can't find it in dictionary.  But, if you means overflow those congested traffic to
another path, I think it will do harm to promising of SLA signed. Perhaps what we need is to reroute some part of
traffic to another path with no/less congestion



>
>       b) Or you generate road systems X0, X1, X2, X3 such that the links of Xi, avoid overlaps with links of Xj, j<i.
>          One micro flow uses DSCP x0, the next one DSCP x1,... as to balance the traffic and as to avoid congestion
>          in the first place.
>

I don't think load balancing could be achieved by this way, as self-similar and asymetric distribution in internet
traffic

>

>
>
> HH:> There is never a free lunch. But what are a view routing tables compared to the probably much bigger number
> of p2p LSPs?
>

But the problem is routers have to maintein all information about DSCP they support and propagate them.

>
>
> 3. If heuritic method is not feasible, go for some approximation
> methods and prove using some theoretical results. Then support your
> performance claims with some simulation results.
>
> HH=> If there is enough interest, I would be happy to show this C++-program on work.
>      As I said, it is not yet enhanced with tie breaker rules. But that would be very important as to
>      determine the same identical smallest size tree determined b whichever node. If this failed we would
>      have to continue with rambo-SPF:-)
>
> If you do all this, I will accept that your algorithm doesn't
> consititute any performance problem.
>
> HH=> No problem. Be sure, it doesn't run 10**80 years :-)

--
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************





_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 22:09:29 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11607
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 22:09:29 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA15142
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 22:10:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA14760;
	Mon, 5 Aug 2002 22:04:55 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04273
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 10:02:17 -0400 (EDT)
Received: from mail.cad.zju.edu.cn (cad.zju.edu.cn [210.32.131.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA13874
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 10:01:01 -0400 (EDT)
Received: (qmail 10418 invoked from network); 5 Aug 2002 14:07:09 -0000
Received: from unknown (HELO cad.zju.edu.cn) (210.32.131.97)
  by 210.32.131.2 with SMTP; 5 Aug 2002 14:07:09 -0000
Message-ID: <3D4E854E.A96D0FC2@cad.zju.edu.cn>
Date: Mon, 05 Aug 2002 22:01:50 +0800
From: shen jing <jshen@cad.zju.edu.cn>
Reply-To: jshen@cad.zju.edu.cn
Organization: State Key Lab of CAD&CG
X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: Re:  Differentiated Routing, not only plain rambo-SPF
References: <EF8E39AA846CD411BB9C00508B951F510514B97B@MCHH267E>
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 7bit

Hummel ,


> HH=> a) With respect to a particular road system X , you may determine a respective overflow road system X-overflow.
>         E.g. you may determine by computation the cernel of a smallest size tree being that set of links
>         which are used by at least y  s/d-traffic combinations, whereby n < y < n*(n-1); y be a fixed assigned number.
>         You may recompute the smallest size tree, but before, you want to mark all the cernel links to DISREGARD.
>         Traffic which is about to enter the cernel of X, may be forwarded via X-overflow while changing the
>         receive DSCP-x to DSCP-x-overflow. The decission to do so may be based on a currently available traffic load/
>         traffic metering information.
>

what's the meaning of "cernel"? I can't find it in dictionary.  But, if you means overflow those congested traffic to
another path, I think it will do harm to promising of SLA signed. Perhaps what we need is to reroute some part of
traffic to another path with no/less congestion



>
>       b) Or you generate road systems X0, X1, X2, X3 such that the links of Xi, avoid overlaps with links of Xj, j<i.
>          One micro flow uses DSCP x0, the next one DSCP x1,... as to balance the traffic and as to avoid congestion
>          in the first place.
>

I don't think load balancing could be achieved by this way, as self-similar and asymetric distribution in internet
traffic

>

>
>
> HH:> There is never a free lunch. But what are a view routing tables compared to the probably much bigger number
> of p2p LSPs?
>

But the problem is routers have to maintein all information about DSCP they support and propagate them.

>
>
> 3. If heuritic method is not feasible, go for some approximation
> methods and prove using some theoretical results. Then support your
> performance claims with some simulation results.
>
> HH=> If there is enough interest, I would be happy to show this C++-program on work.
>      As I said, it is not yet enhanced with tie breaker rules. But that would be very important as to
>      determine the same identical smallest size tree determined b whichever node. If this failed we would
>      have to continue with rambo-SPF:-)
>
> If you do all this, I will accept that your algorithm doesn't
> consititute any performance problem.
>
> HH=> No problem. Be sure, it doesn't run 10**80 years :-)

--
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************





_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 22:09:31 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11625
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 22:09:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA14716;
	Mon, 5 Aug 2002 22:04:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA15872
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 13:03:08 -0400 (EDT)
Received: from cs.bu.edu (root@cs.bu.edu [128.197.12.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22270
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 13:01:56 -0400 (EDT)
Received: from cs.bu.edu (matta@memphis [128.197.10.43])
	(authenticated bits=0)
	by cs.bu.edu (8.12.2/8.12.2) with ESMTP id g75H2tPq026705;
	Mon, 5 Aug 2002 13:02:55 -0400 (EDT)
Message-ID: <3D4EAFBE.3834FFC9@cs.bu.edu>
Date: Mon, 05 Aug 2002 13:02:54 -0400
From: Ibrahim Matta <matta@cs.bu.edu>
Organization: Boston University, Computer Science Department
X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: "Naidu, Venkata" <Venkata.Naidu@marconi.com>
CC: "'Ayyasamy, Senthilkumar (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>,
        jnc@ginger.lcs.mit.edu, fred@cisco.com, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: Re: Differentiated Routing, not only plain rambo-SPF
References: <39469E08BD83D411A3D900204840EC557632AF@vie-msgusr-01.dc.fore.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 7bit

"Naidu, Venkata" wrote:
>   Simply, SPs can map 2 different services [example,
>   2 different CoS-types] to these different metrics.
>   Effectively we *are* doing DiffRouting...previously
>   there is no name for it...(and we are getting panicked
>   that we are facing a new/unresovable/performace
>   implicated problem here).
> 

How is "DiffRouting" different from
old Type-of-Service (ToS) routing?

http://www.faqs.org/rfcs/rfc1349.html
http://www.cs.bu.edu/fac/matta/Papers/jsac95.ps

ibrahim


--
Ibrahim Matta       Dept of Comp Sci, 111 Cummington St, MCS-271
matta@cs.bu.edu     Assistant Prof, Boston Univ., Boston, MA 02215
Tel: (617)358-1062, Fax: (617)353-6457, URL: www.cs.bu.edu/fac/matta/


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 22:09:31 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11634
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 22:09:31 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA15153
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 22:10:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA14716;
	Mon, 5 Aug 2002 22:04:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA15872
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 13:03:08 -0400 (EDT)
Received: from cs.bu.edu (root@cs.bu.edu [128.197.12.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22270
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 13:01:56 -0400 (EDT)
Received: from cs.bu.edu (matta@memphis [128.197.10.43])
	(authenticated bits=0)
	by cs.bu.edu (8.12.2/8.12.2) with ESMTP id g75H2tPq026705;
	Mon, 5 Aug 2002 13:02:55 -0400 (EDT)
Message-ID: <3D4EAFBE.3834FFC9@cs.bu.edu>
Date: Mon, 05 Aug 2002 13:02:54 -0400
From: Ibrahim Matta <matta@cs.bu.edu>
Organization: Boston University, Computer Science Department
X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: "Naidu, Venkata" <Venkata.Naidu@marconi.com>
CC: "'Ayyasamy, Senthilkumar (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>,
        jnc@ginger.lcs.mit.edu, fred@cisco.com, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: Re: Differentiated Routing, not only plain rambo-SPF
References: <39469E08BD83D411A3D900204840EC557632AF@vie-msgusr-01.dc.fore.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 7bit

"Naidu, Venkata" wrote:
>   Simply, SPs can map 2 different services [example,
>   2 different CoS-types] to these different metrics.
>   Effectively we *are* doing DiffRouting...previously
>   there is no name for it...(and we are getting panicked
>   that we are facing a new/unresovable/performace
>   implicated problem here).
> 

How is "DiffRouting" different from
old Type-of-Service (ToS) routing?

http://www.faqs.org/rfcs/rfc1349.html
http://www.cs.bu.edu/fac/matta/Papers/jsac95.ps

ibrahim


--
Ibrahim Matta       Dept of Comp Sci, 111 Cummington St, MCS-271
matta@cs.bu.edu     Assistant Prof, Boston Univ., Boston, MA 02215
Tel: (617)358-1062, Fax: (617)353-6457, URL: www.cs.bu.edu/fac/matta/


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 22:09:44 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11658
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 22:09:44 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA14729;
	Mon, 5 Aug 2002 22:04:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA21323
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 05:42:06 -0400 (EDT)
Received: from wisbech.cl.cam.ac.uk (IDENT:41OBPYRTQJzpPhI4Yy4y8+KtpO0nH60J@mta1.cl.cam.ac.uk [128.232.0.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06097
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 05:40:54 -0400 (EDT)
Received: from shep.cl.cam.ac.uk
	([128.232.8.11] helo=cl.cam.ac.uk ident=jac22)
	by wisbech.cl.cam.ac.uk with esmtp (Exim 3.092 #1)
	id 17beNH-0000qf-00; Mon, 05 Aug 2002 10:42:03 +0100
To: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
cc: "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>,
        Jon.Crowcroft@cl.cam.ac.uk
Subject: Re: AW: Differentiated Routing, not only plain rambo-SPF 
In-Reply-To: Message from Hummel Heinrich <Heinrich.Hummel@icn.siemens.de> 
   of "Mon, 05 Aug 2002 11:05:51 +0200." <EF8E39AA846CD411BB9C00508B951F510514B977@MCHH267E> 
Date: Mon, 05 Aug 2002 10:42:03 +0100
From: Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>
Message-Id: <E17beNH-0000qf-00@wisbech.cl.cam.ac.uk>
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org


In message <EF8E39AA846CD411BB9C00508B951F510514B977@MCHH267E>, Hum
mel Heinrich typed:

 >>the entire Internet community  (or at least you and some others) 
 >>is the prisoner of this rambo-SPF routing algorithm.

there is no Internet community except in the perception of
individuals, which is quite amusing, as the "egocentric"
model of SPF you (nicely) outline is the chief
characteristic of the viewpoint that perceives the existence
of the mythical Internet community....

in the meantime, i happen to agree - i think that some form
of cooperative path computation strategy 
( e.g.  diffusive computational nash game, or
epidemic/gossip tabu search, or whathave you) might yield
more novel solutions than incremental techniques rooted in
the 35 year old stuff we've (oops, s/we/me) tended to get
stuck on....

one thing we need to do is think global - looking at
mean to peak traffic measurements now widely available, 
it behoves us to consider flipping traffic either way around 
the planet based on diurnal variations in load...as well
as looking at the tier 1 and tier 2 queueing delays, it
looks like we could consider starting to approximate a
large part of pathset computation using
geographic based schemes to seperate out capacity and
propagation-contribs to latency, from availability and load

s/d-ijk-stra/d-xyz-stra/

cheers
jon


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 22:09:45 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11667
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 22:09:45 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA15187
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 22:10:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA14729;
	Mon, 5 Aug 2002 22:04:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA21323
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 05:42:06 -0400 (EDT)
Received: from wisbech.cl.cam.ac.uk (IDENT:41OBPYRTQJzpPhI4Yy4y8+KtpO0nH60J@mta1.cl.cam.ac.uk [128.232.0.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06097
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 05:40:54 -0400 (EDT)
Received: from shep.cl.cam.ac.uk
	([128.232.8.11] helo=cl.cam.ac.uk ident=jac22)
	by wisbech.cl.cam.ac.uk with esmtp (Exim 3.092 #1)
	id 17beNH-0000qf-00; Mon, 05 Aug 2002 10:42:03 +0100
To: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
cc: "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>,
        Jon.Crowcroft@cl.cam.ac.uk
Subject: Re: AW: Differentiated Routing, not only plain rambo-SPF 
In-Reply-To: Message from Hummel Heinrich <Heinrich.Hummel@icn.siemens.de> 
   of "Mon, 05 Aug 2002 11:05:51 +0200." <EF8E39AA846CD411BB9C00508B951F510514B977@MCHH267E> 
Date: Mon, 05 Aug 2002 10:42:03 +0100
From: Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>
Message-Id: <E17beNH-0000qf-00@wisbech.cl.cam.ac.uk>
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org


In message <EF8E39AA846CD411BB9C00508B951F510514B977@MCHH267E>, Hum
mel Heinrich typed:

 >>the entire Internet community  (or at least you and some others) 
 >>is the prisoner of this rambo-SPF routing algorithm.

there is no Internet community except in the perception of
individuals, which is quite amusing, as the "egocentric"
model of SPF you (nicely) outline is the chief
characteristic of the viewpoint that perceives the existence
of the mythical Internet community....

in the meantime, i happen to agree - i think that some form
of cooperative path computation strategy 
( e.g.  diffusive computational nash game, or
epidemic/gossip tabu search, or whathave you) might yield
more novel solutions than incremental techniques rooted in
the 35 year old stuff we've (oops, s/we/me) tended to get
stuck on....

one thing we need to do is think global - looking at
mean to peak traffic measurements now widely available, 
it behoves us to consider flipping traffic either way around 
the planet based on diurnal variations in load...as well
as looking at the tier 1 and tier 2 queueing delays, it
looks like we could consider starting to approximate a
large part of pathset computation using
geographic based schemes to seperate out capacity and
propagation-contribs to latency, from availability and load

s/d-ijk-stra/d-xyz-stra/

cheers
jon


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug  5 23:03:02 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13143
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 23:03:02 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA17506;
	Mon, 5 Aug 2002 23:00:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA17467
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 23:00:18 -0400 (EDT)
Received: from kc-msxproto4.kc.umkc.edu (kc-msxproto4.kc.umkc.edu [134.193.143.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13062
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 22:59:04 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 5 Aug 2002 22:00:17 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF 
Date: Mon, 5 Aug 2002 22:00:16 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C252B@KC-MAIL2.kc.umkc.edu>
Thread-Topic: AW: Differentiated Routing, not only plain rambo-SPF 
Thread-Index: AcI87sjTRLBouwlUSh+j1K4i+yVJLQAA93YA
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Jon Crowcroft" <Jon.Crowcroft@cl.cam.ac.uk>,
        "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>
Cc: <routing-discussion@ietf.org>, <irtf-rr@puck.nether.net>
X-OriginalArrivalTime: 06 Aug 2002 03:00:17.0301 (UTC) FILETIME=[64A56450:01C23CF5]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id XAA17469
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit


> i think that some form
> of cooperative path computation strategy 
> ( e.g.  diffusive computational nash game, or
> epidemic/gossip tabu search, or whathave you) 
Cooperative path computation are highly theoretical at
the present stage. I think there might be many
assumptions and approximations to prove such strategies.

take one simple example: Throup et all describe 
methods for optimizing OSPF weights by using heuristic methods
..esp local search hueristics (tabu...) But in reality, people
generally use standard heuristics (like Weight inversely propotional
to capacity.) So i think as a least option we may choose some standard 
heuristic assumptions for solving such co-operative path computations.
So using tabu search methods are sometimes not practical.

>might yield
> more novel solutions than incremental techniques rooted in
> the 35 year old stuff we've (oops, s/we/me) tended to get
> stuck on....

Solutions might be novel. We introduced IPv6 long before but still
we could not transfer to new structure all together. we go for 
increment methods like CIDR, NAT, double stack, and ALG than transition
to a new addressing structure. So, it is always advisable to do some
incremental techniques than novel solutions. But, if you are proposing 
new structure, first we should address flag day  problem will 
trasitioning. i dont think any new systems does this work.
 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug  5 23:03:03 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13153
	for <routing-discussion-archive@odin.ietf.org>; Mon, 5 Aug 2002 23:03:03 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA18069
	for routing-discussion-archive@odin.ietf.org; Mon, 5 Aug 2002 23:04:16 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA17506;
	Mon, 5 Aug 2002 23:00:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA17467
	for <routing-discussion@optimus.ietf.org>; Mon, 5 Aug 2002 23:00:18 -0400 (EDT)
Received: from kc-msxproto4.kc.umkc.edu (kc-msxproto4.kc.umkc.edu [134.193.143.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13062
	for <routing-discussion@ietf.org>; Mon, 5 Aug 2002 22:59:04 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Mon, 5 Aug 2002 22:00:17 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF 
Date: Mon, 5 Aug 2002 22:00:16 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C252B@KC-MAIL2.kc.umkc.edu>
Thread-Topic: AW: Differentiated Routing, not only plain rambo-SPF 
Thread-Index: AcI87sjTRLBouwlUSh+j1K4i+yVJLQAA93YA
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Jon Crowcroft" <Jon.Crowcroft@cl.cam.ac.uk>,
        "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>
Cc: <routing-discussion@ietf.org>, <irtf-rr@puck.nether.net>
X-OriginalArrivalTime: 06 Aug 2002 03:00:17.0301 (UTC) FILETIME=[64A56450:01C23CF5]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id XAA17469
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit


> i think that some form
> of cooperative path computation strategy 
> ( e.g.  diffusive computational nash game, or
> epidemic/gossip tabu search, or whathave you) 
Cooperative path computation are highly theoretical at
the present stage. I think there might be many
assumptions and approximations to prove such strategies.

take one simple example: Throup et all describe 
methods for optimizing OSPF weights by using heuristic methods
..esp local search hueristics (tabu...) But in reality, people
generally use standard heuristics (like Weight inversely propotional
to capacity.) So i think as a least option we may choose some standard 
heuristic assumptions for solving such co-operative path computations.
So using tabu search methods are sometimes not practical.

>might yield
> more novel solutions than incremental techniques rooted in
> the 35 year old stuff we've (oops, s/we/me) tended to get
> stuck on....

Solutions might be novel. We introduced IPv6 long before but still
we could not transfer to new structure all together. we go for 
increment methods like CIDR, NAT, double stack, and ALG than transition
to a new addressing structure. So, it is always advisable to do some
incremental techniques than novel solutions. But, if you are proposing 
new structure, first we should address flag day  problem will 
trasitioning. i dont think any new systems does this work.
 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug  6 02:42:58 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26920
	for <routing-discussion-archive@odin.ietf.org>; Tue, 6 Aug 2002 02:42:58 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA06523;
	Tue, 6 Aug 2002 02:39:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA06495
	for <routing-discussion@optimus.ietf.org>; Tue, 6 Aug 2002 02:39:32 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26774
	for <routing-discussion@ietf.org>; Tue, 6 Aug 2002 02:38:18 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id IAA25457;
	Tue, 6 Aug 2002 08:39:27 +0200 (MET DST)
Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id IAA29038;
	Tue, 6 Aug 2002 08:39:28 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2656.59)
	id <PTSZDQ5N>; Tue, 6 Aug 2002 08:39:12 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B983@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Ibrahim Matta'" <matta@cs.bu.edu>,
        "Naidu, Venkata"
	 <Venkata.Naidu@marconi.com>
Cc: "'Ayyasamy, Senthilkumar (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>,
        jnc@ginger.lcs.mit.edu, fred@cisco.com, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 6 Aug 2002 08:39:10 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org


 

"Naidu, Venkata" wrote:
>   Simply, SPs can map 2 different services [example,
>   2 different CoS-types] to these different metrics.
>   Effectively we *are* doing DiffRouting...previously
>   there is no name for it...(and we are getting panicked
>   that we are facing a new/unresovable/performace
>   implicated problem here).
> 
Ibrahim wrote:

How is "DiffRouting" different from
old Type-of-Service (ToS) routing?

My answer:
By constructing multiple road systems, which  eventually are even constructed in awareness of
road systems constructed before (e.g. overflow road system X-overflow w.r.t. road system X)
and to lock traffic into some road system so that it is kept out of the way from other traffic. It may mean not to
take the shortest path for the individual micro flow.

Heinrich



http://www.faqs.org/rfcs/rfc1349.html
http://www.cs.bu.edu/fac/matta/Papers/jsac95.ps

ibrahim


--
Ibrahim Matta       Dept of Comp Sci, 111 Cummington St, MCS-271
matta@cs.bu.edu     Assistant Prof, Boston Univ., Boston, MA 02215
Tel: (617)358-1062, Fax: (617)353-6457, URL: www.cs.bu.edu/fac/matta/

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug  6 02:42:58 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26927
	for <routing-discussion-archive@odin.ietf.org>; Tue, 6 Aug 2002 02:42:58 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA06695
	for routing-discussion-archive@odin.ietf.org; Tue, 6 Aug 2002 02:44:11 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA06523;
	Tue, 6 Aug 2002 02:39:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA06495
	for <routing-discussion@optimus.ietf.org>; Tue, 6 Aug 2002 02:39:32 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26774
	for <routing-discussion@ietf.org>; Tue, 6 Aug 2002 02:38:18 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id IAA25457;
	Tue, 6 Aug 2002 08:39:27 +0200 (MET DST)
Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id IAA29038;
	Tue, 6 Aug 2002 08:39:28 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2656.59)
	id <PTSZDQ5N>; Tue, 6 Aug 2002 08:39:12 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B983@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Ibrahim Matta'" <matta@cs.bu.edu>,
        "Naidu, Venkata"
	 <Venkata.Naidu@marconi.com>
Cc: "'Ayyasamy, Senthilkumar (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>,
        jnc@ginger.lcs.mit.edu, fred@cisco.com, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 6 Aug 2002 08:39:10 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org


 

"Naidu, Venkata" wrote:
>   Simply, SPs can map 2 different services [example,
>   2 different CoS-types] to these different metrics.
>   Effectively we *are* doing DiffRouting...previously
>   there is no name for it...(and we are getting panicked
>   that we are facing a new/unresovable/performace
>   implicated problem here).
> 
Ibrahim wrote:

How is "DiffRouting" different from
old Type-of-Service (ToS) routing?

My answer:
By constructing multiple road systems, which  eventually are even constructed in awareness of
road systems constructed before (e.g. overflow road system X-overflow w.r.t. road system X)
and to lock traffic into some road system so that it is kept out of the way from other traffic. It may mean not to
take the shortest path for the individual micro flow.

Heinrich



http://www.faqs.org/rfcs/rfc1349.html
http://www.cs.bu.edu/fac/matta/Papers/jsac95.ps

ibrahim


--
Ibrahim Matta       Dept of Comp Sci, 111 Cummington St, MCS-271
matta@cs.bu.edu     Assistant Prof, Boston Univ., Boston, MA 02215
Tel: (617)358-1062, Fax: (617)353-6457, URL: www.cs.bu.edu/fac/matta/

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug  6 03:40:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28436
	for <routing-discussion-archive@odin.ietf.org>; Tue, 6 Aug 2002 03:40:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA09637;
	Tue, 6 Aug 2002 03:31:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA09598
	for <routing-discussion@optimus.ietf.org>; Tue, 6 Aug 2002 03:31:34 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28159
	for <routing-discussion@ietf.org>; Tue, 6 Aug 2002 03:30:19 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id JAA29369;
	Tue, 6 Aug 2002 09:31:28 +0200 (MET DST)
Received: from mchh274e.demchh201e.icn.siemens.de ([139.21.200.84])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id JAA21703;
	Tue, 6 Aug 2002 09:31:30 +0200 (MET DST)
Received: by MCHH274E with Internet Mail Service (5.5.2656.59)
	id <P83CGKP6>; Tue, 6 Aug 2002 09:31:14 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B984@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Naidu, Venkata'" <Venkata.Naidu@marconi.com>,
        "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
Cc: jnc@ginger.lcs.mit.edu, fred@cisco.com, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 6 Aug 2002 09:31:11 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id DAA09599
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

I am really surprised that the need for having several routing table is a big (scalability) issue:
(BTW:Logically it takes separate routing tables, one per DSCP. But you may as well maintain one routing table
 and search the next hop entry also based on the DSCP)

IMO stateless DiffRout-Forwarding is more scalable than MPLS or RSVP.

However,if the size of the routing table is an issue, then why wasn't it an issue so far:
Each ingress node needs to know the egress node before setting up the respective next hop entry in the routing table.
So why doesn't the IP header contain a field for the destination router address. It would allow to keep the routing tables
small: one single next hop entry w.r.t. each destination router would be sufficient.
Of course, it would be rediculous to expect any change in IPv4. But why wasn't this an issue for IPv6 ?
When IPv6 was born, I guess there have already been routing tables of respectful size.
Can anyone tell me?

Heinrich


-----Ursprüngliche Nachricht-----
Von: Naidu, Venkata [mailto:Venkata.Naidu@Marconi.com]
Gesendet: Montag, 5. August 2002 21:33
An: 'Ayyasamy, Senthilkumar (UMKC-Student)'; Hummel Heinrich
Cc: jnc@ginger.lcs.mit.edu; fred@cisco.com; irtf-rr@puck.nether.net;
routing-discussion@ietf.org
Betreff: RE: Differentiated Routing, not only plain rambo-SPF


Senthil,

-> > There is no difference between MPLS-TE and 
-> DiffServ-aware-MPLS-> TE? In other 
-> > words, are you saying that Differv-aware-MPLS-TE 
-> > is notgoing solve ANY problem that MPLS-TE alone couldn't 
-> > solve ?
-> I was just talking about diffserv aware MPLS TE which is 
-> more related to 
-> the context of discussion. The authors of diffserv MPLS TE 
-> draft discusses scalability problems.

  Yes! I am also talking about DiffServ-aware-MPLS-TE.
  In the draft-ietf-tewg-diff-te-reqts-05.txt authors
  clearly mentioned about problem statement and how we
  can benefit from DiffServ-aware-MPLS-TE (even if there
  are some scalability issues). Effectively, authors
  are trying to solve SOME problem - then how can 
  you can say that DiffServ-aware-MPLS-TE (aka DiffRouting)
  is not going to solve ANY problem.

  Scalability issues in TOS Routing are different
  from scalability issues in DiffRouting (if you consider
  TOS routing is applicable in traditional hop-by-hop
  routing case and DiffRouting is applicable in todays
  source routing cases).

  Finally, let me conclude what I agree and disagree
  with you.

  What I agree:
  - None of these approaches [traditional TOS-Routing or
    DiffRouting (DiffServ-aware-MPLS-TE)] really solve
    end-to-end QoS/Performance. I already expressed this
    concern to Fred Baker (which he concluded that as
    an open ended question) - which is fine!
http://www1.ietf.org/mail-archive/working-groups/routing-discussion/current/
msg00060.html

  - None of the above approaches are complete. They have
    some common and some different issues - for example
    scalability etc etc

  What I don't agree (my view):
  - Just because a solution has scalability issues doesn't
    mean that that solution is not going to solve ANY 
    problem.

  - Diffserv-aware-MPLS-TE is trying to solve different problems
    which we couldn't solve with traditional routing approaches
    *easily* in the past.

  - We are trying to solve (we will solve) those scalability
    issues in source routing (using hierarchical TE etc etc)
    in future.

  Do you agree? If not let me know - let us discuss :)

  If you still feel that DiffRouting is not going to solve 
  ANY problem then I will ask authors of 
  draft-ietf-tewg-diff-te-reqts-05.txt (for clarification).
  
  Finally, you didn't tell me in what other approaches
  we can solve the same issues that the DiffServ-TE is
  trying to solve (with out letting control plane know,
  with out CSPF, with out connection-oriented MPLS etc etc).
  
--
Venkata

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug  6 03:40:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28444
	for <routing-discussion-archive@odin.ietf.org>; Tue, 6 Aug 2002 03:40:57 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA10248
	for routing-discussion-archive@odin.ietf.org; Tue, 6 Aug 2002 03:42:11 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA09637;
	Tue, 6 Aug 2002 03:31:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA09598
	for <routing-discussion@optimus.ietf.org>; Tue, 6 Aug 2002 03:31:34 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28159
	for <routing-discussion@ietf.org>; Tue, 6 Aug 2002 03:30:19 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id JAA29369;
	Tue, 6 Aug 2002 09:31:28 +0200 (MET DST)
Received: from mchh274e.demchh201e.icn.siemens.de ([139.21.200.84])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id JAA21703;
	Tue, 6 Aug 2002 09:31:30 +0200 (MET DST)
Received: by MCHH274E with Internet Mail Service (5.5.2656.59)
	id <P83CGKP6>; Tue, 6 Aug 2002 09:31:14 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B984@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Naidu, Venkata'" <Venkata.Naidu@marconi.com>,
        "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
Cc: jnc@ginger.lcs.mit.edu, fred@cisco.com, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 6 Aug 2002 09:31:11 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id DAA09599
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

I am really surprised that the need for having several routing table is a big (scalability) issue:
(BTW:Logically it takes separate routing tables, one per DSCP. But you may as well maintain one routing table
 and search the next hop entry also based on the DSCP)

IMO stateless DiffRout-Forwarding is more scalable than MPLS or RSVP.

However,if the size of the routing table is an issue, then why wasn't it an issue so far:
Each ingress node needs to know the egress node before setting up the respective next hop entry in the routing table.
So why doesn't the IP header contain a field for the destination router address. It would allow to keep the routing tables
small: one single next hop entry w.r.t. each destination router would be sufficient.
Of course, it would be rediculous to expect any change in IPv4. But why wasn't this an issue for IPv6 ?
When IPv6 was born, I guess there have already been routing tables of respectful size.
Can anyone tell me?

Heinrich


-----Ursprüngliche Nachricht-----
Von: Naidu, Venkata [mailto:Venkata.Naidu@Marconi.com]
Gesendet: Montag, 5. August 2002 21:33
An: 'Ayyasamy, Senthilkumar (UMKC-Student)'; Hummel Heinrich
Cc: jnc@ginger.lcs.mit.edu; fred@cisco.com; irtf-rr@puck.nether.net;
routing-discussion@ietf.org
Betreff: RE: Differentiated Routing, not only plain rambo-SPF


Senthil,

-> > There is no difference between MPLS-TE and 
-> DiffServ-aware-MPLS-> TE? In other 
-> > words, are you saying that Differv-aware-MPLS-TE 
-> > is notgoing solve ANY problem that MPLS-TE alone couldn't 
-> > solve ?
-> I was just talking about diffserv aware MPLS TE which is 
-> more related to 
-> the context of discussion. The authors of diffserv MPLS TE 
-> draft discusses scalability problems.

  Yes! I am also talking about DiffServ-aware-MPLS-TE.
  In the draft-ietf-tewg-diff-te-reqts-05.txt authors
  clearly mentioned about problem statement and how we
  can benefit from DiffServ-aware-MPLS-TE (even if there
  are some scalability issues). Effectively, authors
  are trying to solve SOME problem - then how can 
  you can say that DiffServ-aware-MPLS-TE (aka DiffRouting)
  is not going to solve ANY problem.

  Scalability issues in TOS Routing are different
  from scalability issues in DiffRouting (if you consider
  TOS routing is applicable in traditional hop-by-hop
  routing case and DiffRouting is applicable in todays
  source routing cases).

  Finally, let me conclude what I agree and disagree
  with you.

  What I agree:
  - None of these approaches [traditional TOS-Routing or
    DiffRouting (DiffServ-aware-MPLS-TE)] really solve
    end-to-end QoS/Performance. I already expressed this
    concern to Fred Baker (which he concluded that as
    an open ended question) - which is fine!
http://www1.ietf.org/mail-archive/working-groups/routing-discussion/current/
msg00060.html

  - None of the above approaches are complete. They have
    some common and some different issues - for example
    scalability etc etc

  What I don't agree (my view):
  - Just because a solution has scalability issues doesn't
    mean that that solution is not going to solve ANY 
    problem.

  - Diffserv-aware-MPLS-TE is trying to solve different problems
    which we couldn't solve with traditional routing approaches
    *easily* in the past.

  - We are trying to solve (we will solve) those scalability
    issues in source routing (using hierarchical TE etc etc)
    in future.

  Do you agree? If not let me know - let us discuss :)

  If you still feel that DiffRouting is not going to solve 
  ANY problem then I will ask authors of 
  draft-ietf-tewg-diff-te-reqts-05.txt (for clarification).
  
  Finally, you didn't tell me in what other approaches
  we can solve the same issues that the DiffServ-TE is
  trying to solve (with out letting control plane know,
  with out CSPF, with out connection-oriented MPLS etc etc).
  
--
Venkata

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug  6 04:28:44 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29222
	for <routing-discussion-archive@odin.ietf.org>; Tue, 6 Aug 2002 04:28:44 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA12043;
	Tue, 6 Aug 2002 04:12:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA12014
	for <routing-discussion@optimus.ietf.org>; Tue, 6 Aug 2002 04:12:39 -0400 (EDT)
Received: from kc-msxproto2.kc.umkc.edu (kc-msxproto2.kc.umkc.edu [134.193.143.159])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28965
	for <routing-discussion@ietf.org>; Tue, 6 Aug 2002 04:11:25 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 6 Aug 2002 03:12:38 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 6 Aug 2002 03:12:37 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C252C@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcI9G085wsGx+1RERr2x31U9RMfHBgAAiCMA
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>,
        "Naidu, Venkata" <Venkata.Naidu@marconi.com>
Cc: <jnc@ginger.lcs.mit.edu>, <fred@cisco.com>, <irtf-rr@puck.nether.net>,
        <routing-discussion@ietf.org>
X-OriginalArrivalTime: 06 Aug 2002 08:12:38.0303 (UTC) FILETIME=[07275AF0:01C23D21]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id EAA12015
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit


> I am really surprised that the need for having several 
> routing table is a big (scalability) issue:
> (BTW:Logically it takes separate routing tables, one per 
> DSCP. But you may as well maintain one routing table
>  and search the next hop entry also based on the DSCP)
> IMO stateless DiffRout-Forwarding is more scalable than MPLS or RSVP.
  Yes diffserv forwarding is less stateful when compared to MPLS 
or RSVP. But that has nothing to do with scalability problems in maintaining 
multiple routing tables. 
There are scalability issues wrt single routing table itself. People are still 
working on scalable solutions for mimizing the overhead, wrt adding mechanisms 
like accounting and other valued added measurement functions, which requires 
processing of pkts at line rate. So i am guessing, scalablity associated with 
multiple routing tables, will be a long shot.

See again you have started with diffrout, then it was changed to diffser-aware-TE 
and now mechanisms for basic diffserv arch. 

> However,if the size of the routing table is an issue, then 
> why wasn't it an issue so far:
> Each ingress node needs to know the egress node before 
> setting up the respective next hop entry in the routing table.
> So why doesn't the IP header contain a field for the 
> destination router address. It would allow to keep the routing tables
> small: one single next hop entry w.r.t. each destination 
> router would be sufficient.
> Of course, it would be rediculous to expect any change in 
> IPv4. But why wasn't this an issue for IPv6 ?
> When IPv6 was born, I guess there have already been routing 
> tables of respectful size.
> Can anyone tell me?

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug  6 04:28:44 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29230
	for <routing-discussion-archive@odin.ietf.org>; Tue, 6 Aug 2002 04:28:44 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA12362
	for routing-discussion-archive@odin.ietf.org; Tue, 6 Aug 2002 04:29:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA12043;
	Tue, 6 Aug 2002 04:12:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA12014
	for <routing-discussion@optimus.ietf.org>; Tue, 6 Aug 2002 04:12:39 -0400 (EDT)
Received: from kc-msxproto2.kc.umkc.edu (kc-msxproto2.kc.umkc.edu [134.193.143.159])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28965
	for <routing-discussion@ietf.org>; Tue, 6 Aug 2002 04:11:25 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 6 Aug 2002 03:12:38 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 6 Aug 2002 03:12:37 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C252C@KC-MAIL2.kc.umkc.edu>
Thread-Topic: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcI9G085wsGx+1RERr2x31U9RMfHBgAAiCMA
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>,
        "Naidu, Venkata" <Venkata.Naidu@marconi.com>
Cc: <jnc@ginger.lcs.mit.edu>, <fred@cisco.com>, <irtf-rr@puck.nether.net>,
        <routing-discussion@ietf.org>
X-OriginalArrivalTime: 06 Aug 2002 08:12:38.0303 (UTC) FILETIME=[07275AF0:01C23D21]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id EAA12015
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit


> I am really surprised that the need for having several 
> routing table is a big (scalability) issue:
> (BTW:Logically it takes separate routing tables, one per 
> DSCP. But you may as well maintain one routing table
>  and search the next hop entry also based on the DSCP)
> IMO stateless DiffRout-Forwarding is more scalable than MPLS or RSVP.
  Yes diffserv forwarding is less stateful when compared to MPLS 
or RSVP. But that has nothing to do with scalability problems in maintaining 
multiple routing tables. 
There are scalability issues wrt single routing table itself. People are still 
working on scalable solutions for mimizing the overhead, wrt adding mechanisms 
like accounting and other valued added measurement functions, which requires 
processing of pkts at line rate. So i am guessing, scalablity associated with 
multiple routing tables, will be a long shot.

See again you have started with diffrout, then it was changed to diffser-aware-TE 
and now mechanisms for basic diffserv arch. 

> However,if the size of the routing table is an issue, then 
> why wasn't it an issue so far:
> Each ingress node needs to know the egress node before 
> setting up the respective next hop entry in the routing table.
> So why doesn't the IP header contain a field for the 
> destination router address. It would allow to keep the routing tables
> small: one single next hop entry w.r.t. each destination 
> router would be sufficient.
> Of course, it would be rediculous to expect any change in 
> IPv4. But why wasn't this an issue for IPv6 ?
> When IPv6 was born, I guess there have already been routing 
> tables of respectful size.
> Can anyone tell me?

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug  6 06:12:55 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01776
	for <routing-discussion-archive@odin.ietf.org>; Tue, 6 Aug 2002 06:12:55 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA16577;
	Tue, 6 Aug 2002 06:03:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA16547
	for <routing-discussion@optimus.ietf.org>; Tue, 6 Aug 2002 06:03:30 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01259
	for <routing-discussion@ietf.org>; Tue, 6 Aug 2002 06:02:16 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id MAA17417;
	Tue, 6 Aug 2002 12:03:18 +0200 (MET DST)
Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id MAA13479;
	Tue, 6 Aug 2002 12:03:19 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2656.59)
	id <PTSZDZJT>; Tue, 6 Aug 2002 12:03:03 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B985@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        "Naidu, Venkata" <Venkata.Naidu@marconi.com>,
        Hummel Heinrich
	 <Heinrich.Hummel@icn.siemens.de>
Cc: jnc@ginger.lcs.mit.edu, fred@cisco.com, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 6 Aug 2002 12:03:02 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

 

Hummel, was your original proposal same like Diffserv-aware-TE. I thought
it was different.

My answer:
DiffRout is definitively different.

My motivation and my key thoughts to open this discussions have been:
- combine the best of Intserv/MPLS and Diffserv and as a result do stateless IP forwarding but get
     what  Intserv/MPLS are providing: Qos/BW/Policy/Traffic balancing/rerouting.

- therefore construct road systems and do IP forwarding/routing also based on DSCP.

- the road systems may have assigned bandwidth. This is reasonable/feasable because some traffic can really
  be locked into some slim road system (smallest size tree, smallest ring) just like MPLS traffic can be locked into
  some LSP. Whereas with rambo-SPF bandwidth assignment makes no sense as the sum of all
  shortest path trees computed by all the nodes would span the entire network, i.e. spread traffic all over it.
  The price for staying within some road system should be acceptable: Eventually, make a few hops more.
  Based on my computations, the smallest size tree may be smaller than the avarage shortest path tree by 15-20 %. 
  So I think the detour for the packets will not be very big either.   

- be guided by what you can observe on daily road traffic: Especially in the U.S. there are so many ramp-based
  road junctions, which are more impressive than any traffic light controlled junction, so that motor-cyclists may
  jump the queue of waiting cars (=DiffServ) if the traffic light is red. 
  There are so many observations that can be made watching how the traffic is managed for cars, 
  trains, airplanes, pedestrians, etc. We all are used to it and don't discern extra smartness in it. However there is.
      
- and I realized what is the big obstacle: Yes it is this rambo-SPF routing paradigma. It does not represent the  
  surveillant view, only the egomanic view, combined with the hope that in total you get best results because 
  "the streets are emptiest when each car takes the shortest route":-). 



Heinrich
   
    




 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug  6 06:12:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01788
	for <routing-discussion-archive@odin.ietf.org>; Tue, 6 Aug 2002 06:12:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA17458
	for routing-discussion-archive@odin.ietf.org; Tue, 6 Aug 2002 06:14:08 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA16577;
	Tue, 6 Aug 2002 06:03:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA16547
	for <routing-discussion@optimus.ietf.org>; Tue, 6 Aug 2002 06:03:30 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01259
	for <routing-discussion@ietf.org>; Tue, 6 Aug 2002 06:02:16 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id MAA17417;
	Tue, 6 Aug 2002 12:03:18 +0200 (MET DST)
Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id MAA13479;
	Tue, 6 Aug 2002 12:03:19 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2656.59)
	id <PTSZDZJT>; Tue, 6 Aug 2002 12:03:03 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B985@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        "Naidu, Venkata" <Venkata.Naidu@marconi.com>,
        Hummel Heinrich
	 <Heinrich.Hummel@icn.siemens.de>
Cc: jnc@ginger.lcs.mit.edu, fred@cisco.com, irtf-rr@puck.nether.net,
        routing-discussion@ietf.org
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 6 Aug 2002 12:03:02 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

 

Hummel, was your original proposal same like Diffserv-aware-TE. I thought
it was different.

My answer:
DiffRout is definitively different.

My motivation and my key thoughts to open this discussions have been:
- combine the best of Intserv/MPLS and Diffserv and as a result do stateless IP forwarding but get
     what  Intserv/MPLS are providing: Qos/BW/Policy/Traffic balancing/rerouting.

- therefore construct road systems and do IP forwarding/routing also based on DSCP.

- the road systems may have assigned bandwidth. This is reasonable/feasable because some traffic can really
  be locked into some slim road system (smallest size tree, smallest ring) just like MPLS traffic can be locked into
  some LSP. Whereas with rambo-SPF bandwidth assignment makes no sense as the sum of all
  shortest path trees computed by all the nodes would span the entire network, i.e. spread traffic all over it.
  The price for staying within some road system should be acceptable: Eventually, make a few hops more.
  Based on my computations, the smallest size tree may be smaller than the avarage shortest path tree by 15-20 %. 
  So I think the detour for the packets will not be very big either.   

- be guided by what you can observe on daily road traffic: Especially in the U.S. there are so many ramp-based
  road junctions, which are more impressive than any traffic light controlled junction, so that motor-cyclists may
  jump the queue of waiting cars (=DiffServ) if the traffic light is red. 
  There are so many observations that can be made watching how the traffic is managed for cars, 
  trains, airplanes, pedestrians, etc. We all are used to it and don't discern extra smartness in it. However there is.
      
- and I realized what is the big obstacle: Yes it is this rambo-SPF routing paradigma. It does not represent the  
  surveillant view, only the egomanic view, combined with the hope that in total you get best results because 
  "the streets are emptiest when each car takes the shortest route":-). 



Heinrich
   
    




 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Wed Aug  7 12:22:18 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26548
	for <routing-discussion-archive@odin.ietf.org>; Wed, 7 Aug 2002 12:22:18 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA21254;
	Wed, 7 Aug 2002 12:14:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA04098
	for <routing-discussion@optimus.ietf.org>; Tue, 6 Aug 2002 09:03:53 -0400 (EDT)
Received: from mail.cad.zju.edu.cn (cad.zju.edu.cn [210.32.131.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA09670
	for <routing-discussion@ietf.org>; Tue, 6 Aug 2002 09:02:37 -0400 (EDT)
Received: (qmail 22737 invoked from network); 6 Aug 2002 13:08:54 -0000
Received: from unknown (HELO cad.zju.edu.cn) (210.32.131.97)
  by 210.32.131.2 with SMTP; 6 Aug 2002 13:08:54 -0000
Message-ID: <3D4FC927.2CF8E99E@cad.zju.edu.cn>
Date: Tue, 06 Aug 2002 21:03:36 +0800
From: shen jing <jshen@cad.zju.edu.cn>
Reply-To: jshen@cad.zju.edu.cn
Organization: State Key Lab of CAD&CG
X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
CC: irtf-rr@puck.nether.net, routing-discussion@ietf.org
Subject: Re: Differentiated Routing, not only plain rambo-SPF
References: <EF8E39AA846CD411BB9C00508B951F510514B985@MCHH267E>
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 7bit

Hi Hummel,

As DSCP is used for packet queueing in routers,  there may be many types of  queueing mechanism for scheduling of
different classes.

As mentioned in previous message that when overflow/congestion happens along some path, the flow of the same  DSCP
could be overflowed onto other path (?) or it could be dispersed onto multiple paths computed.
This means, if we want to adapt to time-varying network status  LSA must be triggered by overflow of any queue on its
outgoing interface. Because internet traffic's self-similarity characteristics and "heavy-tailed" flow sized distribution,
  we
could not expect the network status maintains a stable status. That is,  routing behavior have to be adjusted frequently.
Right ?  CBQ or the like may adjust the resource allocated dynamically according to load on routers, how could that be
reflected ?   I think, all these factors will do harm to routing stability and extensibility, esp. when we consider
inter-AS routing.

Well, I think some time to read those paper suggested.


>
>
> Hummel, was your original proposal same like Diffserv-aware-TE. I thought
> it was different.
>
> My answer:
> DiffRout is definitively different.
>
> My motivation and my key thoughts to open this discussions have been:
> - combine the best of Intserv/MPLS and Diffserv and as a result do stateless IP forwarding but get
>      what  Intserv/MPLS are providing: Qos/BW/Policy/Traffic balancing/rerouting.
>
> - therefore construct road systems and do IP forwarding/routing also based on DSCP.
>
> - the road systems may have assigned bandwidth. This is reasonable/feasable because some traffic can really
>   be locked into some slim road system (smallest size tree, smallest ring) just like MPLS traffic can be locked into
>   some LSP. Whereas with rambo-SPF bandwidth assignment makes no sense as the sum of all
>   shortest path trees computed by all the nodes would span the entire network, i.e. spread traffic all over it.
>   The price for staying within some road system should be acceptable: Eventually, make a few hops more.
>   Based on my computations, the smallest size tree may be smaller than the avarage shortest path tree by 15-20 %.
>   So I think the detour for the packets will not be very big either.
>
> - be guided by what you can observe on daily road traffic: Especially in the U.S. there are so many ramp-based
>   road junctions, which are more impressive than any traffic light controlled junction, so that motor-cyclists may
>   jump the queue of waiting cars (=DiffServ) if the traffic light is red.
>   There are so many observations that can be made watching how the traffic is managed for cars,
>   trains, airplanes, pedestrians, etc. We all are used to it and don't discern extra smartness in it. However there is.
>
> - and I realized what is the big obstacle: Yes it is this rambo-SPF routing paradigma. It does not represent the
>   surveillant view, only the egomanic view, combined with the hope that in total you get best results because
>   "the streets are emptiest when each car takes the shortest route":-).
>
> Heinrich
>
>
>
>
>
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion

--
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************





_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Wed Aug  7 12:22:19 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26559
	for <routing-discussion-archive@odin.ietf.org>; Wed, 7 Aug 2002 12:22:19 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA21579
	for routing-discussion-archive@odin.ietf.org; Wed, 7 Aug 2002 12:23:33 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA21254;
	Wed, 7 Aug 2002 12:14:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA04098
	for <routing-discussion@optimus.ietf.org>; Tue, 6 Aug 2002 09:03:53 -0400 (EDT)
Received: from mail.cad.zju.edu.cn (cad.zju.edu.cn [210.32.131.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA09670
	for <routing-discussion@ietf.org>; Tue, 6 Aug 2002 09:02:37 -0400 (EDT)
Received: (qmail 22737 invoked from network); 6 Aug 2002 13:08:54 -0000
Received: from unknown (HELO cad.zju.edu.cn) (210.32.131.97)
  by 210.32.131.2 with SMTP; 6 Aug 2002 13:08:54 -0000
Message-ID: <3D4FC927.2CF8E99E@cad.zju.edu.cn>
Date: Tue, 06 Aug 2002 21:03:36 +0800
From: shen jing <jshen@cad.zju.edu.cn>
Reply-To: jshen@cad.zju.edu.cn
Organization: State Key Lab of CAD&CG
X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
CC: irtf-rr@puck.nether.net, routing-discussion@ietf.org
Subject: Re: Differentiated Routing, not only plain rambo-SPF
References: <EF8E39AA846CD411BB9C00508B951F510514B985@MCHH267E>
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 7bit

Hi Hummel,

As DSCP is used for packet queueing in routers,  there may be many types of  queueing mechanism for scheduling of
different classes.

As mentioned in previous message that when overflow/congestion happens along some path, the flow of the same  DSCP
could be overflowed onto other path (?) or it could be dispersed onto multiple paths computed.
This means, if we want to adapt to time-varying network status  LSA must be triggered by overflow of any queue on its
outgoing interface. Because internet traffic's self-similarity characteristics and "heavy-tailed" flow sized distribution,
  we
could not expect the network status maintains a stable status. That is,  routing behavior have to be adjusted frequently.
Right ?  CBQ or the like may adjust the resource allocated dynamically according to load on routers, how could that be
reflected ?   I think, all these factors will do harm to routing stability and extensibility, esp. when we consider
inter-AS routing.

Well, I think some time to read those paper suggested.


>
>
> Hummel, was your original proposal same like Diffserv-aware-TE. I thought
> it was different.
>
> My answer:
> DiffRout is definitively different.
>
> My motivation and my key thoughts to open this discussions have been:
> - combine the best of Intserv/MPLS and Diffserv and as a result do stateless IP forwarding but get
>      what  Intserv/MPLS are providing: Qos/BW/Policy/Traffic balancing/rerouting.
>
> - therefore construct road systems and do IP forwarding/routing also based on DSCP.
>
> - the road systems may have assigned bandwidth. This is reasonable/feasable because some traffic can really
>   be locked into some slim road system (smallest size tree, smallest ring) just like MPLS traffic can be locked into
>   some LSP. Whereas with rambo-SPF bandwidth assignment makes no sense as the sum of all
>   shortest path trees computed by all the nodes would span the entire network, i.e. spread traffic all over it.
>   The price for staying within some road system should be acceptable: Eventually, make a few hops more.
>   Based on my computations, the smallest size tree may be smaller than the avarage shortest path tree by 15-20 %.
>   So I think the detour for the packets will not be very big either.
>
> - be guided by what you can observe on daily road traffic: Especially in the U.S. there are so many ramp-based
>   road junctions, which are more impressive than any traffic light controlled junction, so that motor-cyclists may
>   jump the queue of waiting cars (=DiffServ) if the traffic light is red.
>   There are so many observations that can be made watching how the traffic is managed for cars,
>   trains, airplanes, pedestrians, etc. We all are used to it and don't discern extra smartness in it. However there is.
>
> - and I realized what is the big obstacle: Yes it is this rambo-SPF routing paradigma. It does not represent the
>   surveillant view, only the egomanic view, combined with the hope that in total you get best results because
>   "the streets are emptiest when each car takes the shortest route":-).
>
> Heinrich
>
>
>
>
>
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion

--
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************





_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Wed Aug  7 14:14:23 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02268
	for <routing-discussion-archive@odin.ietf.org>; Wed, 7 Aug 2002 14:14:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28035;
	Wed, 7 Aug 2002 14:07:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28005
	for <routing-discussion@optimus.ietf.org>; Wed, 7 Aug 2002 14:07:18 -0400 (EDT)
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01792
	for <routing-discussion@ietf.org>; Wed, 7 Aug 2002 14:06:05 -0400 (EDT)
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3])
	by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id OAA28566
	for <routing-discussion@ietf.org>; Wed, 7 Aug 2002 14:06:35 -0400 (EDT)
Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22])
 by smtp.itd.nrl.navy.mil (NAVGW 2.5.2.12) with SMTP id M2002080714063511371
 ; Wed, 07 Aug 2002 14:06:35 -0400
Message-Id: <5.0.1.4.2.20020807140459.0342cf18@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Wed, 07 Aug 2002 14:06:52 -0400
To: Alex Zinin <zinin@psg.com>, "Naidu, Venkata" <Venkata.Naidu@marconi.com>
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: Re: IETF54: RTG Area minutes for review
Cc: routing-discussion@ietf.org
In-Reply-To: <2930876508.20020802224154@psg.com>
References: <39469E08BD83D411A3D900204840EC557632A8@vie-msgusr-01.dc.fore.com>
 <39469E08BD83D411A3D900204840EC557632A8@vie-msgusr-01.dc.fore.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

I put up a webpage for Charlie's slides a few weeks back.
You can find them here...
http://tonnant.itd.nrl.navy.mil/manet/yokohama/

-Joe

At 10:41 PM 8/2/2002 -0700, Alex Zinin wrote:
>Venkata,
>
>> Alex,
>
>>   There is no mention about MANET routing protcols & 
>>   WG status.
>
>Good catch. Charlie actually provided an update.
>I'll put this in the notes and we should expect
>Charlie to submit his slides.
>
>
>> Looks like there are enough protocols
>>   in that area to discuss (other than same good old
>>   unicast/multicast routing protocols) ;^)
>
>> http://www1.ietf.org/mail-archive/working-groups/manet/current/msg00705.html
>
>Hopefully we do not have so many candidates :)
>
>>   Was there any discussion about which of these protocols
>>   are going to be standardized etc etc ?
>
>No, there was no discussion on this. We are working
>on this question, and should have a more concrete
>plan by the next meeting.
>
>Thanks.
>Alex
>
>
>
>_______________________________________________
>routing-discussion mailing list
>routing-discussion@ietf.org
>https://www1.ietf.org/mailman/listinfo/routing-discussion



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Wed Aug  7 14:14:24 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02274
	for <routing-discussion-archive@odin.ietf.org>; Wed, 7 Aug 2002 14:14:24 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA28690
	for routing-discussion-archive@odin.ietf.org; Wed, 7 Aug 2002 14:15:37 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28035;
	Wed, 7 Aug 2002 14:07:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28005
	for <routing-discussion@optimus.ietf.org>; Wed, 7 Aug 2002 14:07:18 -0400 (EDT)
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01792
	for <routing-discussion@ietf.org>; Wed, 7 Aug 2002 14:06:05 -0400 (EDT)
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3])
	by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id OAA28566
	for <routing-discussion@ietf.org>; Wed, 7 Aug 2002 14:06:35 -0400 (EDT)
Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22])
 by smtp.itd.nrl.navy.mil (NAVGW 2.5.2.12) with SMTP id M2002080714063511371
 ; Wed, 07 Aug 2002 14:06:35 -0400
Message-Id: <5.0.1.4.2.20020807140459.0342cf18@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Wed, 07 Aug 2002 14:06:52 -0400
To: Alex Zinin <zinin@psg.com>, "Naidu, Venkata" <Venkata.Naidu@marconi.com>
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: Re: IETF54: RTG Area minutes for review
Cc: routing-discussion@ietf.org
In-Reply-To: <2930876508.20020802224154@psg.com>
References: <39469E08BD83D411A3D900204840EC557632A8@vie-msgusr-01.dc.fore.com>
 <39469E08BD83D411A3D900204840EC557632A8@vie-msgusr-01.dc.fore.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

I put up a webpage for Charlie's slides a few weeks back.
You can find them here...
http://tonnant.itd.nrl.navy.mil/manet/yokohama/

-Joe

At 10:41 PM 8/2/2002 -0700, Alex Zinin wrote:
>Venkata,
>
>> Alex,
>
>>   There is no mention about MANET routing protcols & 
>>   WG status.
>
>Good catch. Charlie actually provided an update.
>I'll put this in the notes and we should expect
>Charlie to submit his slides.
>
>
>> Looks like there are enough protocols
>>   in that area to discuss (other than same good old
>>   unicast/multicast routing protocols) ;^)
>
>> http://www1.ietf.org/mail-archive/working-groups/manet/current/msg00705.html
>
>Hopefully we do not have so many candidates :)
>
>>   Was there any discussion about which of these protocols
>>   are going to be standardized etc etc ?
>
>No, there was no discussion on this. We are working
>on this question, and should have a more concrete
>plan by the next meeting.
>
>Thanks.
>Alex
>
>
>
>_______________________________________________
>routing-discussion mailing list
>routing-discussion@ietf.org
>https://www1.ietf.org/mailman/listinfo/routing-discussion



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Thu Aug  8 12:26:50 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18333
	for <routing-discussion-archive@odin.ietf.org>; Thu, 8 Aug 2002 12:26:50 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA13139;
	Thu, 8 Aug 2002 12:12:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA13110
	for <routing-discussion@optimus.ietf.org>; Thu, 8 Aug 2002 12:12:30 -0400 (EDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17904
	for <routing-discussion@ietf.org>; Thu, 8 Aug 2002 12:11:15 -0400 (EDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id JAA24808
	for <routing-discussion@ietf.org>; Thu, 8 Aug 2002 09:11:59 -0700 (PDT)
X-Delivered-For: <routing-discussion@ietf.org>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id g78GBwd26614;
	Thu, 8 Aug 2002 09:11:58 -0700
X-mProtect: <200208081611> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (4.22.78.78, claiming to be "spruce.iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpd3VcCan; Thu, 08 Aug 2002 09:11:55 PDT
Message-Id: <4.3.2.7.2.20020808090349.02f43e10@mailhost.iprg.nokia.com>
X-Sender: hinden@mailhost.iprg.nokia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 08 Aug 2002 09:10:51 -0700
To: routing-discussion@ietf.org
From: Bob Hinden <hinden@iprg.nokia.com>
Subject: Obituary for Edsger Wybe Dijkstra: 1930-2002
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

From:

   http://www.cs.utexas.edu/users/UTCS/notices/dijkstra/ewdobit.html

"Professor Edsger Wybe Dijkstra, a noted pioneer of the science and 
industry of computing, died after a long struggle with cancer on 6 August 
2002 at his home in Nuenen, the Netherlands."

--------------------------------------------------------------------------

Edsger Wybe Dijkstra: 1930-2002


Professor Edsger Wybe Dijkstra, a noted pioneer of the science and industry
of computing, died after a long struggle with cancer on 6 August 2002 at his
home in Nuenen, the Netherlands.

Dijkstra was born in 1930 in Rotterdam, The Netherlands, the son of a
chemist father and a mathematician mother. He graduated from the Gymnasium
Erasmianum in Rotterdam and obtained degrees in mathematics and theoretical
physics from the University of Leyden and a Ph.D. in computing science from
the University of Amsterdam. He worked as a programmer at the Mathematisch
Centrum, Amsterdam, 1952-62; was professor of mathematics, Eindhoven
University of Technology, 1962-1984; and was a Burroughs Corporation
research fellow, 1973-1984. He held the Schlumberger Centennial Chair in
Computing Sciences at the University of Texas at Austin, 1984-1999, and
retired as Professor Emeritus in 1999.

Dijkstra is survived by his wife of over forty years, Maria (Ria) C.
Dijkstra Debets, by three children, Marcus J., Femke E., and computer
scientist Rutger M. Dijkstra, and by two grandchildren.

Dijkstra was the 1972 recipient of the ACM Turing Award, often viewed as the
Nobel Prize for computing. He was a member of the Netherlands Royal Academy
of Arts and Sciences, a member of the American Academy of Arts and Sciences,
and a Distinguished Fellow of the British Computer Society. He received the
1974 AFIPS Harry Goode Award, the 1982 IEEE Computer Pioneer Award, and the
1989 ACM SIGCSE Award for Outstanding Contributions to Computer Science
Education. Athens University of Economics awarded him an honorary doctorate
in 2001. In 2002, the C&C Foundation of Japan recognized Dijkstra "for his
pioneering contributions to the establishment of the scientific basis for
computer software through creative research in basic software theory,
algorithm theory, structured programming, and semaphores".

Dijkstra is renowned for the insight that mathematical logic is and must be
the basis for sensible computer program construction and for his
contributions to mathematical methodology. He is responsible for the idea of
building operating systems as explicitly synchronized sequential processes,
for the formal development of computer programs, and for the intellectual
foundations for the disciplined control of nondeterminacy. He is well known
for his amazingly efficient shortest path algorithm and for having designed
and coded the first Algol 60 compiler. He was famously the leader in the
abolition of the GOTO statement from programming.

Dijkstra was a prodigious writer. His entire collection of over thirteen
hundred written works was digitally scanned and is accessible at
http://www.cs.utexas.edu/users/EWD. He also corresponded regularly with
hundreds of friends and colleagues over the years --not by email but by
conventional post. He strenuously preferred the fountain pen to the computer
in producing his scholarly output and letters.

Dijkstra was notorious for his wit, eloquence, and way with words, such as
in his remark "The question of whether computers can think is like the
question of whether submarines can swim"; his advice to a promising
researcher, who asked how to select a topic for research: "Do only what only
you can do"; and his remark in his Turing Award lecture "In their capacity
as a tool, computers will be but a ripple on the surface of our culture. In
their capacity as intellectual challenge, they are without precedent in the
cultural history of mankind."

Dijkstra enriched the language of computing with many concepts and phrases,
such as structured programming, separation of concerns, synchronization,
deadly embrace, dining philosophers, weakest precondition, guarded command,
the excluded miracle, and the famous "semaphores" for controlling computer
processes. The Oxford English Dictionary cites his use of the words "vector"
and "stack" in a computing context.

Dijkstra enjoyed playing Mozart for his friends on his Boesendorfer piano.
He and his wife had a fondness for exploring state and national parks in
their Volkswagen bus, dubbed the Touring Machine, in which he wrote many
technical papers.

Throughout his scientific career, Dijkstra formulated and pursued the
highest academic ideals of scientific rigour untainted by commercial,
managerial, or political considerations. Simplicity, beauty, and eloquence
were his hallmarks, and his uncompromising insistence on elegance in
programming and mathematics was an inspiration to thousands. He judged his
own work by the highest standards and set a continuing challenge to his many
friends to do the same. For the rest, he willingly undertook the role of
Socrates, that of a gadfly to society, repeatedly goading his native and his
adoptive country by remarking on the mistakes inherent in fashionable ideas
and the dangers of time-serving compromises. Like Socrates, his most
significant legacy is to those who engaged with him in small group
discussions or scientific correspondence about half-formulated ideas and
emerging discoveries. Particularly privileged are those who attended his
reading groups in Eindhoven and Austin, known as the "Tuesday Afternoon
Clubs".

At Dijkstra's passage, let us recall Phaedo's parting remark about Socrates:
"we may truly say that of all the men of his time whom we have known, he was
the wisest and justest and best."

----------------------------------------------------------------------------


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Thu Aug  8 12:26:51 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18338
	for <routing-discussion-archive@odin.ietf.org>; Thu, 8 Aug 2002 12:26:51 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA13838
	for routing-discussion-archive@odin.ietf.org; Thu, 8 Aug 2002 12:28:05 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA13139;
	Thu, 8 Aug 2002 12:12:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA13110
	for <routing-discussion@optimus.ietf.org>; Thu, 8 Aug 2002 12:12:30 -0400 (EDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17904
	for <routing-discussion@ietf.org>; Thu, 8 Aug 2002 12:11:15 -0400 (EDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id JAA24808
	for <routing-discussion@ietf.org>; Thu, 8 Aug 2002 09:11:59 -0700 (PDT)
X-Delivered-For: <routing-discussion@ietf.org>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id g78GBwd26614;
	Thu, 8 Aug 2002 09:11:58 -0700
X-mProtect: <200208081611> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (4.22.78.78, claiming to be "spruce.iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpd3VcCan; Thu, 08 Aug 2002 09:11:55 PDT
Message-Id: <4.3.2.7.2.20020808090349.02f43e10@mailhost.iprg.nokia.com>
X-Sender: hinden@mailhost.iprg.nokia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 08 Aug 2002 09:10:51 -0700
To: routing-discussion@ietf.org
From: Bob Hinden <hinden@iprg.nokia.com>
Subject: Obituary for Edsger Wybe Dijkstra: 1930-2002
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

From:

   http://www.cs.utexas.edu/users/UTCS/notices/dijkstra/ewdobit.html

"Professor Edsger Wybe Dijkstra, a noted pioneer of the science and 
industry of computing, died after a long struggle with cancer on 6 August 
2002 at his home in Nuenen, the Netherlands."

--------------------------------------------------------------------------

Edsger Wybe Dijkstra: 1930-2002


Professor Edsger Wybe Dijkstra, a noted pioneer of the science and industry
of computing, died after a long struggle with cancer on 6 August 2002 at his
home in Nuenen, the Netherlands.

Dijkstra was born in 1930 in Rotterdam, The Netherlands, the son of a
chemist father and a mathematician mother. He graduated from the Gymnasium
Erasmianum in Rotterdam and obtained degrees in mathematics and theoretical
physics from the University of Leyden and a Ph.D. in computing science from
the University of Amsterdam. He worked as a programmer at the Mathematisch
Centrum, Amsterdam, 1952-62; was professor of mathematics, Eindhoven
University of Technology, 1962-1984; and was a Burroughs Corporation
research fellow, 1973-1984. He held the Schlumberger Centennial Chair in
Computing Sciences at the University of Texas at Austin, 1984-1999, and
retired as Professor Emeritus in 1999.

Dijkstra is survived by his wife of over forty years, Maria (Ria) C.
Dijkstra Debets, by three children, Marcus J., Femke E., and computer
scientist Rutger M. Dijkstra, and by two grandchildren.

Dijkstra was the 1972 recipient of the ACM Turing Award, often viewed as the
Nobel Prize for computing. He was a member of the Netherlands Royal Academy
of Arts and Sciences, a member of the American Academy of Arts and Sciences,
and a Distinguished Fellow of the British Computer Society. He received the
1974 AFIPS Harry Goode Award, the 1982 IEEE Computer Pioneer Award, and the
1989 ACM SIGCSE Award for Outstanding Contributions to Computer Science
Education. Athens University of Economics awarded him an honorary doctorate
in 2001. In 2002, the C&C Foundation of Japan recognized Dijkstra "for his
pioneering contributions to the establishment of the scientific basis for
computer software through creative research in basic software theory,
algorithm theory, structured programming, and semaphores".

Dijkstra is renowned for the insight that mathematical logic is and must be
the basis for sensible computer program construction and for his
contributions to mathematical methodology. He is responsible for the idea of
building operating systems as explicitly synchronized sequential processes,
for the formal development of computer programs, and for the intellectual
foundations for the disciplined control of nondeterminacy. He is well known
for his amazingly efficient shortest path algorithm and for having designed
and coded the first Algol 60 compiler. He was famously the leader in the
abolition of the GOTO statement from programming.

Dijkstra was a prodigious writer. His entire collection of over thirteen
hundred written works was digitally scanned and is accessible at
http://www.cs.utexas.edu/users/EWD. He also corresponded regularly with
hundreds of friends and colleagues over the years --not by email but by
conventional post. He strenuously preferred the fountain pen to the computer
in producing his scholarly output and letters.

Dijkstra was notorious for his wit, eloquence, and way with words, such as
in his remark "The question of whether computers can think is like the
question of whether submarines can swim"; his advice to a promising
researcher, who asked how to select a topic for research: "Do only what only
you can do"; and his remark in his Turing Award lecture "In their capacity
as a tool, computers will be but a ripple on the surface of our culture. In
their capacity as intellectual challenge, they are without precedent in the
cultural history of mankind."

Dijkstra enriched the language of computing with many concepts and phrases,
such as structured programming, separation of concerns, synchronization,
deadly embrace, dining philosophers, weakest precondition, guarded command,
the excluded miracle, and the famous "semaphores" for controlling computer
processes. The Oxford English Dictionary cites his use of the words "vector"
and "stack" in a computing context.

Dijkstra enjoyed playing Mozart for his friends on his Boesendorfer piano.
He and his wife had a fondness for exploring state and national parks in
their Volkswagen bus, dubbed the Touring Machine, in which he wrote many
technical papers.

Throughout his scientific career, Dijkstra formulated and pursued the
highest academic ideals of scientific rigour untainted by commercial,
managerial, or political considerations. Simplicity, beauty, and eloquence
were his hallmarks, and his uncompromising insistence on elegance in
programming and mathematics was an inspiration to thousands. He judged his
own work by the highest standards and set a continuing challenge to his many
friends to do the same. For the rest, he willingly undertook the role of
Socrates, that of a gadfly to society, repeatedly goading his native and his
adoptive country by remarking on the mistakes inherent in fashionable ideas
and the dangers of time-serving compromises. Like Socrates, his most
significant legacy is to those who engaged with him in small group
discussions or scientific correspondence about half-formulated ideas and
emerging discoveries. Particularly privileged are those who attended his
reading groups in Eindhoven and Austin, known as the "Tuesday Afternoon
Clubs".

At Dijkstra's passage, let us recall Phaedo's parting remark about Socrates:
"we may truly say that of all the men of his time whom we have known, he was
the wisest and justest and best."

----------------------------------------------------------------------------


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug 12 06:36:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15199
	for <routing-discussion-archive@odin.ietf.org>; Mon, 12 Aug 2002 06:36:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA00706;
	Mon, 12 Aug 2002 06:27:11 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA00676
	for <routing-discussion@optimus.ietf.org>; Mon, 12 Aug 2002 06:27:08 -0400 (EDT)
Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14019
	for <routing-discussion@ietf.org>; Mon, 12 Aug 2002 05:30:07 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id LAA27131;
	Mon, 12 Aug 2002 11:30:55 +0200 (MET DST)
Received: from mchh273e.demchh201e.icn.siemens.de ([139.21.200.83])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id LAA20967;
	Mon, 12 Aug 2002 11:31:14 +0200 (MET DST)
Received: by MCHH273E with Internet Mail Service (5.5.2656.59)
	id <P71R1ZGR>; Mon, 12 Aug 2002 11:30:51 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B98F@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Michael Menth'" <menth@informatik.uni-wuerzburg.de>,
        "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>,
        irtf-rr@puck.nether.net
Subject: AW: Dijkstra died.
Date: Mon, 12 Aug 2002 11:30:36 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id GAA00677
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Michael,
I am sure you agree to spread this news
via the routing discussion and IRTF routing research mailing lists.
Heinrich

-----Ursprüngliche Nachricht-----
Von: Michael Menth [mailto:menth@informatik.uni-wuerzburg.de]
Gesendet: Donnerstag, 8. August 2002 12:41
An: undisclosed-recipients
Betreff: Dijkstra died.



Dear friends,

Professor Edsger Wybe Dijkstra (shortest path, semaphores, etc.) has 
passed away. A moment of silence for the great man.

Kind regards, Michael

http://www.cs.utexas.edu/users/UTCS/notices/dijkstra/ewdobit.html
http://lwn.net/Articles/6993/
http://www.lwn.net/Articles/6954/

-- 
Dipl.-Inform. Michael Menth
University of Wuerzburg, Institute of Computer Science
Am Hubland, D-97074 Wuerzburg, Germany, room A212
phone: (+49)-931/888-6644, fax: (+49)-931/888-6632
mailto:menth@informatik.uni-wuerzburg.de
http://www-info3.informatik.uni-wuerzburg.de/~menth

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug 12 06:36:58 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15207
	for <routing-discussion-archive@odin.ietf.org>; Mon, 12 Aug 2002 06:36:57 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA01576
	for routing-discussion-archive@odin.ietf.org; Mon, 12 Aug 2002 06:38:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA00706;
	Mon, 12 Aug 2002 06:27:11 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA00676
	for <routing-discussion@optimus.ietf.org>; Mon, 12 Aug 2002 06:27:08 -0400 (EDT)
Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14019
	for <routing-discussion@ietf.org>; Mon, 12 Aug 2002 05:30:07 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id LAA27131;
	Mon, 12 Aug 2002 11:30:55 +0200 (MET DST)
Received: from mchh273e.demchh201e.icn.siemens.de ([139.21.200.83])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id LAA20967;
	Mon, 12 Aug 2002 11:31:14 +0200 (MET DST)
Received: by MCHH273E with Internet Mail Service (5.5.2656.59)
	id <P71R1ZGR>; Mon, 12 Aug 2002 11:30:51 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B98F@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Michael Menth'" <menth@informatik.uni-wuerzburg.de>,
        "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>,
        irtf-rr@puck.nether.net
Subject: AW: Dijkstra died.
Date: Mon, 12 Aug 2002 11:30:36 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id GAA00677
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Michael,
I am sure you agree to spread this news
via the routing discussion and IRTF routing research mailing lists.
Heinrich

-----Ursprüngliche Nachricht-----
Von: Michael Menth [mailto:menth@informatik.uni-wuerzburg.de]
Gesendet: Donnerstag, 8. August 2002 12:41
An: undisclosed-recipients
Betreff: Dijkstra died.



Dear friends,

Professor Edsger Wybe Dijkstra (shortest path, semaphores, etc.) has 
passed away. A moment of silence for the great man.

Kind regards, Michael

http://www.cs.utexas.edu/users/UTCS/notices/dijkstra/ewdobit.html
http://lwn.net/Articles/6993/
http://www.lwn.net/Articles/6954/

-- 
Dipl.-Inform. Michael Menth
University of Wuerzburg, Institute of Computer Science
Am Hubland, D-97074 Wuerzburg, Germany, room A212
phone: (+49)-931/888-6644, fax: (+49)-931/888-6632
mailto:menth@informatik.uni-wuerzburg.de
http://www-info3.informatik.uni-wuerzburg.de/~menth

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Mon Aug 12 11:22:42 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25846
	for <routing-discussion-archive@odin.ietf.org>; Mon, 12 Aug 2002 11:22:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17054;
	Mon, 12 Aug 2002 11:03:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17025
	for <routing-discussion@optimus.ietf.org>; Mon, 12 Aug 2002 11:03:31 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25243
	for <routing-discussion@ietf.org>; Mon, 12 Aug 2002 11:02:15 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id RAA10822;
	Mon, 12 Aug 2002 17:03:24 +0200 (MET DST)
Received: from mchh247e.demchh201e.icn.siemens.de ([139.21.200.57])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id RAA22672;
	Mon, 12 Aug 2002 17:03:23 +0200 (MET DST)
Received: by MCHH247E with Internet Mail Service (5.5.2656.59)
	id <P71TXVBD>; Mon, 12 Aug 2002 17:02:59 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B992@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'jshen@cad.zju.edu.cn'" <jshen@cad.zju.edu.cn>,
        Hummel Heinrich
	 <Heinrich.Hummel@icn.siemens.de>
Cc: irtf-rr@puck.nether.net, routing-discussion@ietf.org
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 12 Aug 2002 17:02:57 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA17026
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Jing,
Let me recapture and use the following DSCPs: 
DSCP-Gold-1st, DSCP-Gold-2nd, DSCP-Silver-1st,DSCP-Silver-2nd,DSCP-Bronze-1st,DSCP-Bronze-2nd. 

DSCP-Gold-1st and DSCP-Gold-2nd shall trigger DiffServ Gold-SLA handling.
DSCP-Silver-1st and DSCP-Silver-2nd shall trigger DiffServ Silver-SLA handling.
DSCP-Bronze-1st and DSCP-Bronze-2nd shall trigger DiffServ Bronze-SLA handling. 

They shall as well identify road systems: 
DSCP-Gold-1st, DSCP-Gold-2nd, DSCP-Silver-1st,DSCP-Silver-2nd,DSCP-Bronze-1st,DSCP-Bronze-2nd - built in this
sequence. Hereby each road system is based on what has been left over by the previously built road systems (in terms of
bandwidth).

Gold:  A smallest size tree of toll roads, highways, state roads, country roads.
Silver:A smallest size tree of highways, state roads, country roads.
Bronze:A smallest size tree of state roads, country roads, and highways only if no path otherwise.
 
QoS parameters (speed, packet loss rate, MTU size,..) may define the type of road.

1st and 2nd road system may be different at least  w.r.t. their kernel parts. (The kernel part be that 
center of the smallest size tree, which is used by at least m ingress/egress combinations).
Either traffic starts out with a) proper DSCP-Y-1st, resp. DSCP-Y-2nd, or b) is  changed from DSCP-Y-1st to
DSCP-Y-2nd at the rim of the kernel if some current traffic load information advises so. I prefer a) and if possible such
that any microflow will entirely take one single route.

Jing, you are mentioning two aspects, namely stability and extensibility.
Stability: 
We may toss a dice at the ingress,i.e. determine a random number Y between 0.0 and 1.0. If  
0.0<= Y < a, then we use DSCP-Y-1st, if a<= Y < 1, then we use DSCP-Y-2nd. The real number a should be such
that we avoid/dissolve some congestion and do not relocate it. At low-traffic times a is equal 1. But for the busy hour
determining value a  will be a very interesting topic. 
If any  University folks were interested in doing simulations as to determine value a for all ingress/egress combinations
and for all three SLAs, I would be happy to exchange more thoughts and details on it (so far I have always deferred it).
Especially, it would be interesting to get comparable results between what I called "Orchestrally Conducted Traffic" and
OMP.
However we would be leaving  the DiffRout-track of thoughts. Therefore we should say: this is out of scope of this thread. 
It may only be addressed by some other thread.

Extensibility:
So far I have no solution, on how to determine a smallest size tree made out of OSPF-links and EBGP/IBGP-hops.
BTW:
It seems to be appropriate to focus on  smallest size tree road systems, at least for some time, although ring and
somehow meshy road systems might also be considered. 

Can anybody contribute some  solution ? I think, it must be an identical tree of BGP-hops. Only all edge routers of the
same OSPF network must aquire the completely identical tree. Somehow:-)


Heinrich 

-----Ursprščngliche Nachricht-----
Von: shen jing [mailto:jshen@cad.zju.edu.cn]
Gesendet: Dienstag, 6. August 2002 15:04
An: Hummel Heinrich
Cc: irtf-rr@puck.nether.net; routing-discussion@ietf.org
Betreff: Re: Differentiated Routing, not only plain rambo-SPF


Hi Hummel,

As DSCP is used for packet queueing in routers,  there may be many types of  queueing mechanism for scheduling of
different classes.

As mentioned in previous message that when overflow/congestion happens along some path, the flow of the same  DSCP
could be overflowed onto other path (?) or it could be dispersed onto multiple paths computed.
This means, if we want to adapt to time-varying network status  LSA must be triggered by overflow of any queue on its
outgoing interface. Because internet traffic's self-similarity characteristics and "heavy-tailed" flow sized distribution,
  we
could not expect the network status maintains a stable status. That is,  routing behavior have to be adjusted frequently.
Right ?  CBQ or the like may adjust the resource allocated dynamically according to load on routers, how could that be
reflected ?   I think, all these factors will do harm to routing stability and extensibility, esp. when we consider
inter-AS routing.

Well, I think some time to read those paper suggested.


>
>
> Hummel, was your original proposal same like Diffserv-aware-TE. I thought
> it was different.
>
> My answer:
> DiffRout is definitively different.
>
> My motivation and my key thoughts to open this discussions have been:
> - combine the best of Intserv/MPLS and Diffserv and as a result do stateless IP forwarding but get
>      what  Intserv/MPLS are providing: Qos/BW/Policy/Traffic balancing/rerouting.
>
> - therefore construct road systems and do IP forwarding/routing also based on DSCP.
>
> - the road systems may have assigned bandwidth. This is reasonable/feasable because some traffic can really
>   be locked into some slim road system (smallest size tree, smallest ring) just like MPLS traffic can be locked into
>   some LSP. Whereas with rambo-SPF bandwidth assignment makes no sense as the sum of all
>   shortest path trees computed by all the nodes would span the entire network, i.e. spread traffic all over it.
>   The price for staying within some road system should be acceptable: Eventually, make a few hops more.
>   Based on my computations, the smallest size tree may be smaller than the avarage shortest path tree by 15-20 %.
>   So I think the detour for the packets will not be very big either.
>
> - be guided by what you can observe on daily road traffic: Especially in the U.S. there are so many ramp-based
>   road junctions, which are more impressive than any traffic light controlled junction, so that motor-cyclists may
>   jump the queue of waiting cars (=DiffServ) if the traffic light is red.
>   There are so many observations that can be made watching how the traffic is managed for cars,
>   trains, airplanes, pedestrians, etc. We all are used to it and don't discern extra smartness in it. However there is.
>
> - and I realized what is the big obstacle: Yes it is this rambo-SPF routing paradigma. It does not represent the
>   surveillant view, only the egomanic view, combined with the hope that in total you get best results because
>   "the streets are emptiest when each car takes the shortest route":-).
>
> Heinrich
>
>
>
>
>
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion

--
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************





_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Mon Aug 12 12:10:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25852
	for <routing-discussion-archive@odin.ietf.org>; Mon, 12 Aug 2002 11:22:43 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA17595
	for routing-discussion-archive@odin.ietf.org; Mon, 12 Aug 2002 11:23:58 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17054;
	Mon, 12 Aug 2002 11:03:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17025
	for <routing-discussion@optimus.ietf.org>; Mon, 12 Aug 2002 11:03:31 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25243
	for <routing-discussion@ietf.org>; Mon, 12 Aug 2002 11:02:15 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id RAA10822;
	Mon, 12 Aug 2002 17:03:24 +0200 (MET DST)
Received: from mchh247e.demchh201e.icn.siemens.de ([139.21.200.57])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id RAA22672;
	Mon, 12 Aug 2002 17:03:23 +0200 (MET DST)
Received: by MCHH247E with Internet Mail Service (5.5.2656.59)
	id <P71TXVBD>; Mon, 12 Aug 2002 17:02:59 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B992@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'jshen@cad.zju.edu.cn'" <jshen@cad.zju.edu.cn>,
        Hummel Heinrich
	 <Heinrich.Hummel@icn.siemens.de>
Cc: irtf-rr@puck.nether.net, routing-discussion@ietf.org
Subject: AW: Differentiated Routing, not only plain rambo-SPF
Date: Mon, 12 Aug 2002 17:02:57 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA17026
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Jing,
Let me recapture and use the following DSCPs: 
DSCP-Gold-1st, DSCP-Gold-2nd, DSCP-Silver-1st,DSCP-Silver-2nd,DSCP-Bronze-1st,DSCP-Bronze-2nd. 

DSCP-Gold-1st and DSCP-Gold-2nd shall trigger DiffServ Gold-SLA handling.
DSCP-Silver-1st and DSCP-Silver-2nd shall trigger DiffServ Silver-SLA handling.
DSCP-Bronze-1st and DSCP-Bronze-2nd shall trigger DiffServ Bronze-SLA handling. 

They shall as well identify road systems: 
DSCP-Gold-1st, DSCP-Gold-2nd, DSCP-Silver-1st,DSCP-Silver-2nd,DSCP-Bronze-1st,DSCP-Bronze-2nd - built in this
sequence. Hereby each road system is based on what has been left over by the previously built road systems (in terms of
bandwidth).

Gold:  A smallest size tree of toll roads, highways, state roads, country roads.
Silver:A smallest size tree of highways, state roads, country roads.
Bronze:A smallest size tree of state roads, country roads, and highways only if no path otherwise.
 
QoS parameters (speed, packet loss rate, MTU size,..) may define the type of road.

1st and 2nd road system may be different at least  w.r.t. their kernel parts. (The kernel part be that 
center of the smallest size tree, which is used by at least m ingress/egress combinations).
Either traffic starts out with a) proper DSCP-Y-1st, resp. DSCP-Y-2nd, or b) is  changed from DSCP-Y-1st to
DSCP-Y-2nd at the rim of the kernel if some current traffic load information advises so. I prefer a) and if possible such
that any microflow will entirely take one single route.

Jing, you are mentioning two aspects, namely stability and extensibility.
Stability: 
We may toss a dice at the ingress,i.e. determine a random number Y between 0.0 and 1.0. If  
0.0<= Y < a, then we use DSCP-Y-1st, if a<= Y < 1, then we use DSCP-Y-2nd. The real number a should be such
that we avoid/dissolve some congestion and do not relocate it. At low-traffic times a is equal 1. But for the busy hour
determining value a  will be a very interesting topic. 
If any  University folks were interested in doing simulations as to determine value a for all ingress/egress combinations
and for all three SLAs, I would be happy to exchange more thoughts and details on it (so far I have always deferred it).
Especially, it would be interesting to get comparable results between what I called "Orchestrally Conducted Traffic" and
OMP.
However we would be leaving  the DiffRout-track of thoughts. Therefore we should say: this is out of scope of this thread. 
It may only be addressed by some other thread.

Extensibility:
So far I have no solution, on how to determine a smallest size tree made out of OSPF-links and EBGP/IBGP-hops.
BTW:
It seems to be appropriate to focus on  smallest size tree road systems, at least for some time, although ring and
somehow meshy road systems might also be considered. 

Can anybody contribute some  solution ? I think, it must be an identical tree of BGP-hops. Only all edge routers of the
same OSPF network must aquire the completely identical tree. Somehow:-)


Heinrich 

-----Ursprščngliche Nachricht-----
Von: shen jing [mailto:jshen@cad.zju.edu.cn]
Gesendet: Dienstag, 6. August 2002 15:04
An: Hummel Heinrich
Cc: irtf-rr@puck.nether.net; routing-discussion@ietf.org
Betreff: Re: Differentiated Routing, not only plain rambo-SPF


Hi Hummel,

As DSCP is used for packet queueing in routers,  there may be many types of  queueing mechanism for scheduling of
different classes.

As mentioned in previous message that when overflow/congestion happens along some path, the flow of the same  DSCP
could be overflowed onto other path (?) or it could be dispersed onto multiple paths computed.
This means, if we want to adapt to time-varying network status  LSA must be triggered by overflow of any queue on its
outgoing interface. Because internet traffic's self-similarity characteristics and "heavy-tailed" flow sized distribution,
  we
could not expect the network status maintains a stable status. That is,  routing behavior have to be adjusted frequently.
Right ?  CBQ or the like may adjust the resource allocated dynamically according to load on routers, how could that be
reflected ?   I think, all these factors will do harm to routing stability and extensibility, esp. when we consider
inter-AS routing.

Well, I think some time to read those paper suggested.


>
>
> Hummel, was your original proposal same like Diffserv-aware-TE. I thought
> it was different.
>
> My answer:
> DiffRout is definitively different.
>
> My motivation and my key thoughts to open this discussions have been:
> - combine the best of Intserv/MPLS and Diffserv and as a result do stateless IP forwarding but get
>      what  Intserv/MPLS are providing: Qos/BW/Policy/Traffic balancing/rerouting.
>
> - therefore construct road systems and do IP forwarding/routing also based on DSCP.
>
> - the road systems may have assigned bandwidth. This is reasonable/feasable because some traffic can really
>   be locked into some slim road system (smallest size tree, smallest ring) just like MPLS traffic can be locked into
>   some LSP. Whereas with rambo-SPF bandwidth assignment makes no sense as the sum of all
>   shortest path trees computed by all the nodes would span the entire network, i.e. spread traffic all over it.
>   The price for staying within some road system should be acceptable: Eventually, make a few hops more.
>   Based on my computations, the smallest size tree may be smaller than the avarage shortest path tree by 15-20 %.
>   So I think the detour for the packets will not be very big either.
>
> - be guided by what you can observe on daily road traffic: Especially in the U.S. there are so many ramp-based
>   road junctions, which are more impressive than any traffic light controlled junction, so that motor-cyclists may
>   jump the queue of waiting cars (=DiffServ) if the traffic light is red.
>   There are so many observations that can be made watching how the traffic is managed for cars,
>   trains, airplanes, pedestrians, etc. We all are used to it and don't discern extra smartness in it. However there is.
>
> - and I realized what is the big obstacle: Yes it is this rambo-SPF routing paradigma. It does not represent the
>   surveillant view, only the egomanic view, combined with the hope that in total you get best results because
>   "the streets are emptiest when each car takes the shortest route":-).
>
> Heinrich
>
>
>
>
>
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion

--
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************





_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug 13 09:29:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11383
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 09:29:53 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06064;
	Tue, 13 Aug 2002 09:08:20 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06037
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 09:08:18 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10664
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 09:06:58 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id PAA04103;
	Tue, 13 Aug 2002 15:08:14 +0200 (MET DST)
Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id PAA08189;
	Tue, 13 Aug 2002 15:08:14 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2656.59)
	id <PTSZJZ5P>; Tue, 13 Aug 2002 15:07:51 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B996@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'jshen@cad.zju.edu.cn'" <jshen@cad.zju.edu.cn>,
        Hummel Heinrich
	 <Heinrich.Hummel@icn.siemens.de>
Cc: irtf-rr@puck.nether.net, routing-discussion@ietf.org
Subject: AW: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 15:07:40 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="gb2312"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Jing
see my inserted comments.
Heinrich 


Hummel,

> 
> Gold:  A smallest size tree of toll roads, highways, state roads, country roads.
> Silver:A smallest size tree of highways, state roads, country roads.
> Bronze:A smallest size tree of state roads, country roads, and highways only if no path otherwise.
> 
> QoS parameters (speed, packet loss rate, MTU size,..) may define the type of road.

Do you means to restrict DSCP to be 3bits? 
HH=> No. In general we may  correlate several, e.g. m,  "gold-like" DSCPs 
          a) to their currently defined "gold-like" DiffServ functionality
          and b) to one Gold-1st road system,
    
     Furthermore, we may identify m additional and  suitable  DSCPs which shall trigger the same
     "gold-like" DiffServ functionality like above, but which are correlated to Gold-2nd road system.

   

> 
> 1st and 2nd road system may be different at least  w.r.t. their kernel parts. (The kernel part be that
> center of the smallest size tree, which is used by at least m ingress/egress combinations).
> Either traffic starts out with a) proper DSCP-Y-1st, resp. DSCP-Y-2nd, or b) is  changed from DSCP-Y-1st to
> DSCP-Y-2nd at the rim of the kernel if some current traffic load information advises so. I prefer a) and if possible such
> that any microflow will entirely take one single route.

So, that means to use alternative path for overflowed traffic?  In fact,
someone has proposed similar

method. Perhaps you are interested in the following paper:

http://www.cs.virginia.edu/~rv3s/pubs/compnet_paper.pdf 

HH=> I will go and read this paper.
     I am not surprised and I really welcome that there are others who write such papers.
     I only believe, that sqeezing/locking some traffic into e.g. some smallest size tree-road system
     enables much more effectiveness, both for the better and the worse:
     for the worse: Best-Effort-Traffic may even be handled worse, if locked into an overcrowded road system of
                    bad condition.
     for the better: Gold-traffic will be handled better, if best roads are available and if Best-Effort-Traffic is
                     kept out of the way.  

> 
>
> Stability:
> We may toss a dice at the ingress,i.e. determine a random number Y between 0.0 and 1.0. 

I think this determines when a second path is adopted for traffic
routing, in fact we do not
need to use a random number if MPLS is used. At this situation, I think
what we need is to 
monitor load on a LSP, if the load is more than 70% of the effective
bandwidth another LSP is
adpoted. If distributed routing is used ( as that of current IP
network), traffic dispersion 
have to be triggerred by heuristic method mentioned by you.

HH=> Fine.

> 
> Extensibility:
> So far I have no solution, on how to determine a smallest size tree made out of OSPF-links and EBGP/IBGP-hops.

As I think, a routing system built on time-varying network status will
do harm to both
stability and extensibility, because it could not be expected to all
routers converge to the same 
point within a short time period.

HH=> We should really ask students to program simulations and to investigate whether it will harm or improve stability. 

Some others have been working on resource management in DiffServ
networks, the page located 
at:

http://standards.ericsson.net/rmd/

In deed, I'm very interested in this idea but I think it need more
clarification.

HH=> I will read this paper, too. But again: If you have (at least)  N shortest path trees rooted at  N ingress edge router,
they will disperse traffic all over the network and it is fairly vague what bandwidth on which link shall be reserved.
Whereas if you lock all this traffic into one single  smallest size tree, you may allocate bigger BWs to fewer links.

Hope to hear from others.
HH=> Hope so, too.





-- 
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug 13 09:29:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11392
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 09:29:53 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA07605
	for routing-discussion-archive@odin.ietf.org; Tue, 13 Aug 2002 09:31:12 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06064;
	Tue, 13 Aug 2002 09:08:20 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06037
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 09:08:18 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10664
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 09:06:58 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id PAA04103;
	Tue, 13 Aug 2002 15:08:14 +0200 (MET DST)
Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id PAA08189;
	Tue, 13 Aug 2002 15:08:14 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2656.59)
	id <PTSZJZ5P>; Tue, 13 Aug 2002 15:07:51 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B996@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'jshen@cad.zju.edu.cn'" <jshen@cad.zju.edu.cn>,
        Hummel Heinrich
	 <Heinrich.Hummel@icn.siemens.de>
Cc: irtf-rr@puck.nether.net, routing-discussion@ietf.org
Subject: AW: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 15:07:40 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="gb2312"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Jing
see my inserted comments.
Heinrich 


Hummel,

> 
> Gold:  A smallest size tree of toll roads, highways, state roads, country roads.
> Silver:A smallest size tree of highways, state roads, country roads.
> Bronze:A smallest size tree of state roads, country roads, and highways only if no path otherwise.
> 
> QoS parameters (speed, packet loss rate, MTU size,..) may define the type of road.

Do you means to restrict DSCP to be 3bits? 
HH=> No. In general we may  correlate several, e.g. m,  "gold-like" DSCPs 
          a) to their currently defined "gold-like" DiffServ functionality
          and b) to one Gold-1st road system,
    
     Furthermore, we may identify m additional and  suitable  DSCPs which shall trigger the same
     "gold-like" DiffServ functionality like above, but which are correlated to Gold-2nd road system.

   

> 
> 1st and 2nd road system may be different at least  w.r.t. their kernel parts. (The kernel part be that
> center of the smallest size tree, which is used by at least m ingress/egress combinations).
> Either traffic starts out with a) proper DSCP-Y-1st, resp. DSCP-Y-2nd, or b) is  changed from DSCP-Y-1st to
> DSCP-Y-2nd at the rim of the kernel if some current traffic load information advises so. I prefer a) and if possible such
> that any microflow will entirely take one single route.

So, that means to use alternative path for overflowed traffic?  In fact,
someone has proposed similar

method. Perhaps you are interested in the following paper:

http://www.cs.virginia.edu/~rv3s/pubs/compnet_paper.pdf 

HH=> I will go and read this paper.
     I am not surprised and I really welcome that there are others who write such papers.
     I only believe, that sqeezing/locking some traffic into e.g. some smallest size tree-road system
     enables much more effectiveness, both for the better and the worse:
     for the worse: Best-Effort-Traffic may even be handled worse, if locked into an overcrowded road system of
                    bad condition.
     for the better: Gold-traffic will be handled better, if best roads are available and if Best-Effort-Traffic is
                     kept out of the way.  

> 
>
> Stability:
> We may toss a dice at the ingress,i.e. determine a random number Y between 0.0 and 1.0. 

I think this determines when a second path is adopted for traffic
routing, in fact we do not
need to use a random number if MPLS is used. At this situation, I think
what we need is to 
monitor load on a LSP, if the load is more than 70% of the effective
bandwidth another LSP is
adpoted. If distributed routing is used ( as that of current IP
network), traffic dispersion 
have to be triggerred by heuristic method mentioned by you.

HH=> Fine.

> 
> Extensibility:
> So far I have no solution, on how to determine a smallest size tree made out of OSPF-links and EBGP/IBGP-hops.

As I think, a routing system built on time-varying network status will
do harm to both
stability and extensibility, because it could not be expected to all
routers converge to the same 
point within a short time period.

HH=> We should really ask students to program simulations and to investigate whether it will harm or improve stability. 

Some others have been working on resource management in DiffServ
networks, the page located 
at:

http://standards.ericsson.net/rmd/

In deed, I'm very interested in this idea but I think it need more
clarification.

HH=> I will read this paper, too. But again: If you have (at least)  N shortest path trees rooted at  N ingress edge router,
they will disperse traffic all over the network and it is fairly vague what bandwidth on which link shall be reserved.
Whereas if you lock all this traffic into one single  smallest size tree, you may allocate bigger BWs to fewer links.

Hope to hear from others.
HH=> Hope so, too.





-- 
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug 13 09:39:19 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11720
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 09:39:19 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06957;
	Tue, 13 Aug 2002 09:25:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06933
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 09:25:13 -0400 (EDT)
Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11073
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 09:23:52 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id PAA08895;
	Tue, 13 Aug 2002 15:24:43 +0200 (MET DST)
Received: from mchh273e.demchh201e.icn.siemens.de ([139.21.200.83])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id PAA17621;
	Tue, 13 Aug 2002 15:25:03 +0200 (MET DST)
Received: by MCHH273E with Internet Mail Service (5.5.2656.59)
	id <P71RGBAB>; Tue, 13 Aug 2002 15:24:38 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B997@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'jshen@cad.zju.edu.cn'" <jshen@cad.zju.edu.cn>
Cc: "'irtf-rr@puck.nether.net'" <irtf-rr@puck.nether.net>,
        "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: AW: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 15:24:14 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="gb2312"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org


Jing,
Right this moment I looked at new email-thread on MPLS list "fast re-route merging".
What popped up in my mind:
The smallest size tree road system is, in practice, BI-DIRECTIONAL. It should be feasable to
crank back:  Either   IP-in-IP or some new TYPE information may be applied.The packet's source and destination 
address fields may be exchanged at the point of congestion. The packet may be returned to where the associated overflow road system can be entered. There, source and destination address fields have to be exchanged once again and the packet may be
forwarded with the alternate DSCP along the associated alternate road system.

Wouldn't this be a nice add-on ?

Heinrich
 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug 13 09:39:20 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11727
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 09:39:20 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA08604
	for routing-discussion-archive@odin.ietf.org; Tue, 13 Aug 2002 09:40:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06957;
	Tue, 13 Aug 2002 09:25:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06933
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 09:25:13 -0400 (EDT)
Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11073
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 09:23:52 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id PAA08895;
	Tue, 13 Aug 2002 15:24:43 +0200 (MET DST)
Received: from mchh273e.demchh201e.icn.siemens.de ([139.21.200.83])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id PAA17621;
	Tue, 13 Aug 2002 15:25:03 +0200 (MET DST)
Received: by MCHH273E with Internet Mail Service (5.5.2656.59)
	id <P71RGBAB>; Tue, 13 Aug 2002 15:24:38 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B997@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'jshen@cad.zju.edu.cn'" <jshen@cad.zju.edu.cn>
Cc: "'irtf-rr@puck.nether.net'" <irtf-rr@puck.nether.net>,
        "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: AW: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 15:24:14 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="gb2312"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org


Jing,
Right this moment I looked at new email-thread on MPLS list "fast re-route merging".
What popped up in my mind:
The smallest size tree road system is, in practice, BI-DIRECTIONAL. It should be feasable to
crank back:  Either   IP-in-IP or some new TYPE information may be applied.The packet's source and destination 
address fields may be exchanged at the point of congestion. The packet may be returned to where the associated overflow road system can be entered. There, source and destination address fields have to be exchanged once again and the packet may be
forwarded with the alternate DSCP along the associated alternate road system.

Wouldn't this be a nice add-on ?

Heinrich
 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug 13 10:00:47 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12418
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 10:00:47 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA08927;
	Tue, 13 Aug 2002 09:48:44 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA08901
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 09:48:42 -0400 (EDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [192.161.36.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11988
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 09:47:21 -0400 (EDT)
Received: from slb-av-01.boeing.com ([129.172.13.4])
	by blv-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id GAA17967;
	Tue, 13 Aug 2002 06:48:33 -0700 (PDT)
Received: from blv-hub-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id GAA02744;
	Tue, 13 Aug 2002 06:48:32 -0700 (PDT)
Received: from xch-phl-02p.ne.nos.boeing.com (xch-phl-02p.ne.nos.boeing.com [128.225.22.4])
	by blv-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id g7DDmVm19353;
	Tue, 13 Aug 2002 06:48:31 -0700 (PDT)
Received: by xch-phl-02p.ne.nos.boeing.com with Internet Mail Service (5.5.2650.21)
	id <37GW8H3G>; Tue, 13 Aug 2002 09:48:30 -0400
Message-ID: <8D6509B44ACCEB43A96E032B9C3EA0C8078A3A93@xch-ne-02.ne.nos.boeing.com>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "'Hummel Heinrich'" <Heinrich.Hummel@icn.siemens.de>
Cc: "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 09:48:30 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="gb2312"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Hummel Heinrich wrote:

> Jing,
> Right this moment I looked at new email-thread on MPLS list 
> "fast re-route merging".
> What popped up in my mind:
> The smallest size tree road system is, in practice, 
> BI-DIRECTIONAL. It should be feasable to
> crank back:  Either   IP-in-IP or some new TYPE information 
> may be applied.The packet's source and destination 
> address fields may be exchanged at the point of congestion. 
> The packet may be returned to where the associated overflow 
> road system can be entered. There, source and destination 
> address fields have to be exchanged once again and the packet may be
> forwarded with the alternate DSCP along the associated 
> alternate road system.
> 
> Wouldn't this be a nice add-on ?

I'm no expert in PNNI, but isn't this exactly what it does when it cannot meet the call setup QoS parameters along the shortest path route?

Bert

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug 13 10:00:47 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12425
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 10:00:47 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA10258
	for routing-discussion-archive@odin.ietf.org; Tue, 13 Aug 2002 10:02:07 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA08927;
	Tue, 13 Aug 2002 09:48:44 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA08901
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 09:48:42 -0400 (EDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [192.161.36.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11988
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 09:47:21 -0400 (EDT)
Received: from slb-av-01.boeing.com ([129.172.13.4])
	by blv-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id GAA17967;
	Tue, 13 Aug 2002 06:48:33 -0700 (PDT)
Received: from blv-hub-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id GAA02744;
	Tue, 13 Aug 2002 06:48:32 -0700 (PDT)
Received: from xch-phl-02p.ne.nos.boeing.com (xch-phl-02p.ne.nos.boeing.com [128.225.22.4])
	by blv-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id g7DDmVm19353;
	Tue, 13 Aug 2002 06:48:31 -0700 (PDT)
Received: by xch-phl-02p.ne.nos.boeing.com with Internet Mail Service (5.5.2650.21)
	id <37GW8H3G>; Tue, 13 Aug 2002 09:48:30 -0400
Message-ID: <8D6509B44ACCEB43A96E032B9C3EA0C8078A3A93@xch-ne-02.ne.nos.boeing.com>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "'Hummel Heinrich'" <Heinrich.Hummel@icn.siemens.de>
Cc: "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 09:48:30 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="gb2312"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Hummel Heinrich wrote:

> Jing,
> Right this moment I looked at new email-thread on MPLS list 
> "fast re-route merging".
> What popped up in my mind:
> The smallest size tree road system is, in practice, 
> BI-DIRECTIONAL. It should be feasable to
> crank back:  Either   IP-in-IP or some new TYPE information 
> may be applied.The packet's source and destination 
> address fields may be exchanged at the point of congestion. 
> The packet may be returned to where the associated overflow 
> road system can be entered. There, source and destination 
> address fields have to be exchanged once again and the packet may be
> forwarded with the alternate DSCP along the associated 
> alternate road system.
> 
> Wouldn't this be a nice add-on ?

I'm no expert in PNNI, but isn't this exactly what it does when it cannot meet the call setup QoS parameters along the shortest path route?

Bert

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug 13 10:13:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13088
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 10:13:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA09394;
	Tue, 13 Aug 2002 09:57:30 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA09360
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 09:57:27 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12229
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 09:56:07 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id PAA08803;
	Tue, 13 Aug 2002 15:57:22 +0200 (MET DST)
Received: from mchh274e.demchh201e.icn.siemens.de ([139.21.200.84])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id PAA09047;
	Tue, 13 Aug 2002 15:57:23 +0200 (MET DST)
Received: by MCHH274E with Internet Mail Service (5.5.2656.59)
	id <P83CL8J6>; Tue, 13 Aug 2002 15:56:59 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B999@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Manfredi, Albert E'" <albert.e.manfredi@boeing.com>,
        Hummel Heinrich
	 <Heinrich.Hummel@icn.siemens.de>
Cc: "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: AW: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 15:56:53 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id JAA09361
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Bert,
yes,it is similar;
but here it is about state-less IP forwarding, i.e. about forwarding the individual IP packets, without any
RSVP path and without any MPLS path.
Heinrich

-----Ursprščngliche Nachricht-----
Von: Manfredi, Albert E [mailto:albert.e.manfredi@boeing.com]
Gesendet: Dienstag, 13. August 2002 15:49
An: 'Hummel Heinrich'
Cc: 'routing-discussion@ietf.org'
Betreff: RE: AW: Differentiated Routing, not only plain rambo-SPF


Hummel Heinrich wrote:

> Jing,
> Right this moment I looked at new email-thread on MPLS list 
> "fast re-route merging".
> What popped up in my mind:
> The smallest size tree road system is, in practice, 
> BI-DIRECTIONAL. It should be feasable to
> crank back:  Either   IP-in-IP or some new TYPE information 
> may be applied.The packet's source and destination 
> address fields may be exchanged at the point of congestion. 
> The packet may be returned to where the associated overflow 
> road system can be entered. There, source and destination 
> address fields have to be exchanged once again and the packet may be
> forwarded with the alternate DSCP along the associated 
> alternate road system.
> 
> Wouldn't this be a nice add-on ?

I'm no expert in PNNI, but isn't this exactly what it does when it cannot meet the call setup QoS parameters along the shortest path route?

Bert

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug 13 10:13:58 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13094
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 10:13:58 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA11233
	for routing-discussion-archive@odin.ietf.org; Tue, 13 Aug 2002 10:15:15 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA09394;
	Tue, 13 Aug 2002 09:57:30 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA09360
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 09:57:27 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12229
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 09:56:07 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id PAA08803;
	Tue, 13 Aug 2002 15:57:22 +0200 (MET DST)
Received: from mchh274e.demchh201e.icn.siemens.de ([139.21.200.84])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id PAA09047;
	Tue, 13 Aug 2002 15:57:23 +0200 (MET DST)
Received: by MCHH274E with Internet Mail Service (5.5.2656.59)
	id <P83CL8J6>; Tue, 13 Aug 2002 15:56:59 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B999@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Manfredi, Albert E'" <albert.e.manfredi@boeing.com>,
        Hummel Heinrich
	 <Heinrich.Hummel@icn.siemens.de>
Cc: "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: AW: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 15:56:53 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id JAA09361
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Bert,
yes,it is similar;
but here it is about state-less IP forwarding, i.e. about forwarding the individual IP packets, without any
RSVP path and without any MPLS path.
Heinrich

-----Ursprščngliche Nachricht-----
Von: Manfredi, Albert E [mailto:albert.e.manfredi@boeing.com]
Gesendet: Dienstag, 13. August 2002 15:49
An: 'Hummel Heinrich'
Cc: 'routing-discussion@ietf.org'
Betreff: RE: AW: Differentiated Routing, not only plain rambo-SPF


Hummel Heinrich wrote:

> Jing,
> Right this moment I looked at new email-thread on MPLS list 
> "fast re-route merging".
> What popped up in my mind:
> The smallest size tree road system is, in practice, 
> BI-DIRECTIONAL. It should be feasable to
> crank back:  Either   IP-in-IP or some new TYPE information 
> may be applied.The packet's source and destination 
> address fields may be exchanged at the point of congestion. 
> The packet may be returned to where the associated overflow 
> road system can be entered. There, source and destination 
> address fields have to be exchanged once again and the packet may be
> forwarded with the alternate DSCP along the associated 
> alternate road system.
> 
> Wouldn't this be a nice add-on ?

I'm no expert in PNNI, but isn't this exactly what it does when it cannot meet the call setup QoS parameters along the shortest path route?

Bert

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug 13 10:16:23 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13220
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 10:16:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA10170;
	Tue, 13 Aug 2002 10:01:38 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA10137
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 10:01:34 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12374
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 10:00:14 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA14360;
	Tue, 13 Aug 2002 10:01:00 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA21622;
	Tue, 13 Aug 2002 10:01:00 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99VANC>; Tue, 13 Aug 2002 10:00:59 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632E1@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
To: "'Manfredi, Albert E'" <albert.e.manfredi@boeing.com>,
        "'Hummel Heinrich'" <Heinrich.Hummel@icn.siemens.de>
Cc: "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 10:00:51 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="gb2312"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Hummel & Bert,

  FYI-
http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04.txt

http://www.ietf.org/internet-drafts/draft-ietf-mpls-te-feed-04.txt

--
Venkata.

-> -----Original Message-----
-> From: Manfredi, Albert E [mailto:albert.e.manfredi@boeing.com]
-> Sent: Tuesday, August 13, 2002 9:49 AM
-> To: 'Hummel Heinrich'
-> Cc: 'routing-discussion@ietf.org'
-> Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
-> 
-> 
-> Hummel Heinrich wrote:
-> 
-> > Jing,
-> > Right this moment I looked at new email-thread on MPLS list 
-> > "fast re-route merging".
-> > What popped up in my mind:
-> > The smallest size tree road system is, in practice, 
-> > BI-DIRECTIONAL. It should be feasable to
-> > crank back:  Either   IP-in-IP or some new TYPE information 
-> > may be applied.The packet's source and destination 
-> > address fields may be exchanged at the point of congestion. 
-> > The packet may be returned to where the associated overflow 
-> > road system can be entered. There, source and destination 
-> > address fields have to be exchanged once again and the 
-> packet may be
-> > forwarded with the alternate DSCP along the associated 
-> > alternate road system.
-> > 
-> > Wouldn't this be a nice add-on ?
-> 
-> I'm no expert in PNNI, but isn't this exactly what it does 
-> when it cannot meet the call setup QoS parameters along the 
-> shortest path route?
-> 
-> Bert

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug 13 10:16:23 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13226
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 10:16:23 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA11320
	for routing-discussion-archive@odin.ietf.org; Tue, 13 Aug 2002 10:17:41 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA10170;
	Tue, 13 Aug 2002 10:01:38 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA10137
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 10:01:34 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12374
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 10:00:14 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA14360;
	Tue, 13 Aug 2002 10:01:00 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA21622;
	Tue, 13 Aug 2002 10:01:00 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99VANC>; Tue, 13 Aug 2002 10:00:59 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632E1@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
To: "'Manfredi, Albert E'" <albert.e.manfredi@boeing.com>,
        "'Hummel Heinrich'" <Heinrich.Hummel@icn.siemens.de>
Cc: "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 10:00:51 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="gb2312"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Hummel & Bert,

  FYI-
http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04.txt

http://www.ietf.org/internet-drafts/draft-ietf-mpls-te-feed-04.txt

--
Venkata.

-> -----Original Message-----
-> From: Manfredi, Albert E [mailto:albert.e.manfredi@boeing.com]
-> Sent: Tuesday, August 13, 2002 9:49 AM
-> To: 'Hummel Heinrich'
-> Cc: 'routing-discussion@ietf.org'
-> Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
-> 
-> 
-> Hummel Heinrich wrote:
-> 
-> > Jing,
-> > Right this moment I looked at new email-thread on MPLS list 
-> > "fast re-route merging".
-> > What popped up in my mind:
-> > The smallest size tree road system is, in practice, 
-> > BI-DIRECTIONAL. It should be feasable to
-> > crank back:  Either   IP-in-IP or some new TYPE information 
-> > may be applied.The packet's source and destination 
-> > address fields may be exchanged at the point of congestion. 
-> > The packet may be returned to where the associated overflow 
-> > road system can be entered. There, source and destination 
-> > address fields have to be exchanged once again and the 
-> packet may be
-> > forwarded with the alternate DSCP along the associated 
-> > alternate road system.
-> > 
-> > Wouldn't this be a nice add-on ?
-> 
-> I'm no expert in PNNI, but isn't this exactly what it does 
-> when it cannot meet the call setup QoS parameters along the 
-> shortest path route?
-> 
-> Bert

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug 13 10:30:13 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13796
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 10:30:13 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA10450;
	Tue, 13 Aug 2002 10:06:53 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA10422
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 10:06:52 -0400 (EDT)
Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12601
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 10:05:31 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id QAA12211;
	Tue, 13 Aug 2002 16:06:27 +0200 (MET DST)
Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id QAA14721;
	Tue, 13 Aug 2002 16:06:47 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2656.59)
	id <PTSZJ8BF>; Tue, 13 Aug 2002 16:06:24 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B99A@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Naidu, Venkata'" <Venkata.Naidu@Marconi.com>,
        "'Manfredi, Albert E'"
	 <albert.e.manfredi@boeing.com>
Cc: "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: AW: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 16:06:19 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA10423
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Venkata,
yes I know. And let me add my personal feeling:
I think Iwata's draft should become a working group draft. It is overdue.
Heinrich

-----Ursprščngliche Nachricht-----
Von: Naidu, Venkata [mailto:Venkata.Naidu@Marconi.com]
Gesendet: Dienstag, 13. August 2002 16:01
An: 'Manfredi, Albert E'; 'Hummel Heinrich'
Cc: 'routing-discussion@ietf.org'
Betreff: RE: AW: Differentiated Routing, not only plain rambo-SPF


Hummel & Bert,

  FYI-
http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04.txt

http://www.ietf.org/internet-drafts/draft-ietf-mpls-te-feed-04.txt

--
Venkata.

-> -----Original Message-----
-> From: Manfredi, Albert E [mailto:albert.e.manfredi@boeing.com]
-> Sent: Tuesday, August 13, 2002 9:49 AM
-> To: 'Hummel Heinrich'
-> Cc: 'routing-discussion@ietf.org'
-> Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
-> 
-> 
-> Hummel Heinrich wrote:
-> 
-> > Jing,
-> > Right this moment I looked at new email-thread on MPLS list 
-> > "fast re-route merging".
-> > What popped up in my mind:
-> > The smallest size tree road system is, in practice, 
-> > BI-DIRECTIONAL. It should be feasable to
-> > crank back:  Either   IP-in-IP or some new TYPE information 
-> > may be applied.The packet's source and destination 
-> > address fields may be exchanged at the point of congestion. 
-> > The packet may be returned to where the associated overflow 
-> > road system can be entered. There, source and destination 
-> > address fields have to be exchanged once again and the 
-> packet may be
-> > forwarded with the alternate DSCP along the associated 
-> > alternate road system.
-> > 
-> > Wouldn't this be a nice add-on ?
-> 
-> I'm no expert in PNNI, but isn't this exactly what it does 
-> when it cannot meet the call setup QoS parameters along the 
-> shortest path route?
-> 
-> Bert

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug 13 10:30:14 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13805
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 10:30:13 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA12515
	for routing-discussion-archive@odin.ietf.org; Tue, 13 Aug 2002 10:31:31 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA10450;
	Tue, 13 Aug 2002 10:06:53 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA10422
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 10:06:52 -0400 (EDT)
Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12601
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 10:05:31 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id QAA12211;
	Tue, 13 Aug 2002 16:06:27 +0200 (MET DST)
Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id QAA14721;
	Tue, 13 Aug 2002 16:06:47 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2656.59)
	id <PTSZJ8BF>; Tue, 13 Aug 2002 16:06:24 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B99A@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Naidu, Venkata'" <Venkata.Naidu@Marconi.com>,
        "'Manfredi, Albert E'"
	 <albert.e.manfredi@boeing.com>
Cc: "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: AW: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 16:06:19 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA10423
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Venkata,
yes I know. And let me add my personal feeling:
I think Iwata's draft should become a working group draft. It is overdue.
Heinrich

-----Ursprščngliche Nachricht-----
Von: Naidu, Venkata [mailto:Venkata.Naidu@Marconi.com]
Gesendet: Dienstag, 13. August 2002 16:01
An: 'Manfredi, Albert E'; 'Hummel Heinrich'
Cc: 'routing-discussion@ietf.org'
Betreff: RE: AW: Differentiated Routing, not only plain rambo-SPF


Hummel & Bert,

  FYI-
http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04.txt

http://www.ietf.org/internet-drafts/draft-ietf-mpls-te-feed-04.txt

--
Venkata.

-> -----Original Message-----
-> From: Manfredi, Albert E [mailto:albert.e.manfredi@boeing.com]
-> Sent: Tuesday, August 13, 2002 9:49 AM
-> To: 'Hummel Heinrich'
-> Cc: 'routing-discussion@ietf.org'
-> Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
-> 
-> 
-> Hummel Heinrich wrote:
-> 
-> > Jing,
-> > Right this moment I looked at new email-thread on MPLS list 
-> > "fast re-route merging".
-> > What popped up in my mind:
-> > The smallest size tree road system is, in practice, 
-> > BI-DIRECTIONAL. It should be feasable to
-> > crank back:  Either   IP-in-IP or some new TYPE information 
-> > may be applied.The packet's source and destination 
-> > address fields may be exchanged at the point of congestion. 
-> > The packet may be returned to where the associated overflow 
-> > road system can be entered. There, source and destination 
-> > address fields have to be exchanged once again and the 
-> packet may be
-> > forwarded with the alternate DSCP along the associated 
-> > alternate road system.
-> > 
-> > Wouldn't this be a nice add-on ?
-> 
-> I'm no expert in PNNI, but isn't this exactly what it does 
-> when it cannot meet the call setup QoS parameters along the 
-> shortest path route?
-> 
-> Bert

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug 13 10:31:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13891
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 10:31:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA10961;
	Tue, 13 Aug 2002 10:11:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA10928
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 10:10:59 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12798
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 10:09:39 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA15220;
	Tue, 13 Aug 2002 10:10:25 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA23910;
	Tue, 13 Aug 2002 10:09:51 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99VA53>; Tue, 13 Aug 2002 10:09:51 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632E2@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
To: "'Hummel Heinrich'" <Heinrich.Hummel@icn.siemens.de>,
        "'Manfredi, Albert E'" <albert.e.manfredi@boeing.com>
Cc: "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 10:09:50 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="gb2312"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Heinrich,

-> yes,it is similar;
-> but here it is about state-less IP forwarding, i.e. about 
-> forwarding the individual IP packets, without any
-> RSVP path and without any MPLS path.

  Oh! Ok...you would like to do Crankback in
  connection less IP environments?!?

  In such a case, you might find below paper interesting:
http://www.ecse.rpi.edu/Homepages/shivkuma/research/papers/te-latest.pdf

  There was some discussion in E2E list regarding
  pros & cons of this approach. I couldn't find the URL
  but I vaguely remember that the subject of the discussion
  is "EC++N" or something like that...

--
Venkata

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug 13 10:31:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13897
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 10:31:56 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA12889
	for routing-discussion-archive@odin.ietf.org; Tue, 13 Aug 2002 10:33:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA10961;
	Tue, 13 Aug 2002 10:11:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA10928
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 10:10:59 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12798
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 10:09:39 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA15220;
	Tue, 13 Aug 2002 10:10:25 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA23910;
	Tue, 13 Aug 2002 10:09:51 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99VA53>; Tue, 13 Aug 2002 10:09:51 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632E2@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
To: "'Hummel Heinrich'" <Heinrich.Hummel@icn.siemens.de>,
        "'Manfredi, Albert E'" <albert.e.manfredi@boeing.com>
Cc: "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 10:09:50 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="gb2312"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Heinrich,

-> yes,it is similar;
-> but here it is about state-less IP forwarding, i.e. about 
-> forwarding the individual IP packets, without any
-> RSVP path and without any MPLS path.

  Oh! Ok...you would like to do Crankback in
  connection less IP environments?!?

  In such a case, you might find below paper interesting:
http://www.ecse.rpi.edu/Homepages/shivkuma/research/papers/te-latest.pdf

  There was some discussion in E2E list regarding
  pros & cons of this approach. I couldn't find the URL
  but I vaguely remember that the subject of the discussion
  is "EC++N" or something like that...

--
Venkata

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug 13 10:42:00 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14339
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 10:42:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA12020;
	Tue, 13 Aug 2002 10:28:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA11992
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 10:28:40 -0400 (EDT)
Received: from kc-msxproto4.kc.umkc.edu (kc-msxproto4.kc.umkc.edu [134.193.143.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13651
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 10:27:22 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 13 Aug 2002 09:28:38 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 09:27:57 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD433161010A2979@KC-MAIL2.kc.umkc.edu>
Thread-Topic: RE: AW: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcJC1Z4vFPSSr9g/SqCEqX3boVnKXA==
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>,
        "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>
Cc: <routing-discussion@ietf.org>
X-OriginalArrivalTime: 13 Aug 2002 14:28:38.0139 (UTC) FILETIME=[B6C164B0:01C242D5]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA11993
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

> > Right this moment I looked at new email-thread on MPLS list 
> > "fast re-route merging".
> > What popped up in my mind:
> > The smallest size tree road system is, in practice, 
> > BI-DIRECTIONAL. It should be feasable to
> > crank back:  Either   IP-in-IP or some new TYPE information 
> > may be applied.The packet's source and destination 
> > address fields may be exchanged at the point of congestion. 
> > The packet may be returned to where the associated overflow 
> > road system can be entered. There, source and destination 
> > address fields have to be exchanged once again and the packet may be
> > forwarded with the alternate DSCP along the associated 
> > alternate road system.
> > 
> > Wouldn't this be a nice add-on ?
> 
> I'm no expert in PNNI, but isn't this exactly what it does 
> when it cannot meet the call setup QoS parameters along the 
> shortest path route?
 Hi, even some of NSIS and resource management functions 
looks like the same. But that doesnt mean that we dont have 
to come up something new. But a clear line between the analysis 
is essential. I am much less interested in taking MPLS into the 
picture. Of from a purely research angle, analyzing with DSCP 
alone works fine. We can introduce some sort of non-cooperative 
routing which is the default scheme for many peer to peer 
communications. A lot of heuristics based, query based, index baed 
algorithms can be done which can some day become an alternative to 
SPF. But looking from a engineering perspective, no doubt SPF will 
rule.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug 13 10:42:01 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14347
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 10:42:01 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA13436
	for routing-discussion-archive@odin.ietf.org; Tue, 13 Aug 2002 10:43:19 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA12020;
	Tue, 13 Aug 2002 10:28:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA11992
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 10:28:40 -0400 (EDT)
Received: from kc-msxproto4.kc.umkc.edu (kc-msxproto4.kc.umkc.edu [134.193.143.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13651
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 10:27:22 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 13 Aug 2002 09:28:38 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 09:27:57 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD433161010A2979@KC-MAIL2.kc.umkc.edu>
Thread-Topic: RE: AW: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcJC1Z4vFPSSr9g/SqCEqX3boVnKXA==
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>,
        "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>
Cc: <routing-discussion@ietf.org>
X-OriginalArrivalTime: 13 Aug 2002 14:28:38.0139 (UTC) FILETIME=[B6C164B0:01C242D5]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA11993
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

> > Right this moment I looked at new email-thread on MPLS list 
> > "fast re-route merging".
> > What popped up in my mind:
> > The smallest size tree road system is, in practice, 
> > BI-DIRECTIONAL. It should be feasable to
> > crank back:  Either   IP-in-IP or some new TYPE information 
> > may be applied.The packet's source and destination 
> > address fields may be exchanged at the point of congestion. 
> > The packet may be returned to where the associated overflow 
> > road system can be entered. There, source and destination 
> > address fields have to be exchanged once again and the packet may be
> > forwarded with the alternate DSCP along the associated 
> > alternate road system.
> > 
> > Wouldn't this be a nice add-on ?
> 
> I'm no expert in PNNI, but isn't this exactly what it does 
> when it cannot meet the call setup QoS parameters along the 
> shortest path route?
 Hi, even some of NSIS and resource management functions 
looks like the same. But that doesnt mean that we dont have 
to come up something new. But a clear line between the analysis 
is essential. I am much less interested in taking MPLS into the 
picture. Of from a purely research angle, analyzing with DSCP 
alone works fine. We can introduce some sort of non-cooperative 
routing which is the default scheme for many peer to peer 
communications. A lot of heuristics based, query based, index baed 
algorithms can be done which can some day become an alternative to 
SPF. But looking from a engineering perspective, no doubt SPF will 
rule.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug 13 11:05:03 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15135
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:05:02 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA13312;
	Tue, 13 Aug 2002 10:41:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA13274
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 10:41:00 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14195
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 10:39:41 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id QAA12493;
	Tue, 13 Aug 2002 16:40:55 +0200 (MET DST)
Received: from mchh274e.demchh201e.icn.siemens.de ([139.21.200.84])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id QAA05502;
	Tue, 13 Aug 2002 16:40:56 +0200 (MET DST)
Received: by MCHH274E with Internet Mail Service (5.5.2656.59)
	id <P83CL0LK>; Tue, 13 Aug 2002 16:40:31 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B99D@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Cc: routing-discussion@ietf.org
Subject: AW: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 16:40:25 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA13277
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Senthil,

Here it is about fast rerouting of IP packets by cranking back to that router where the overflow road system 
may be entered.

You are mentioning NSIS. 
NSIS is interested in two-way applications and would benefit if the two inverse directed pathes are identical.
This is automatically provided by using a smallest size tree road system.

I think the more we debate, the more usefull things we will discover:-)

Heinrich



-----Ursprüngliche Nachricht-----
Von: Ayyasamy, Senthilkumar (UMKC-Student) [mailto:saq66@umkc.edu]
Gesendet: Dienstag, 13. August 2002 16:28
An: Manfredi, Albert E; Hummel Heinrich
Cc: routing-discussion@ietf.org
Betreff: RE: AW: Differentiated Routing, not only plain rambo-SPF


> > Right this moment I looked at new email-thread on MPLS list 
> > "fast re-route merging".
> > What popped up in my mind:
> > The smallest size tree road system is, in practice, 
> > BI-DIRECTIONAL. It should be feasable to
> > crank back:  Either   IP-in-IP or some new TYPE information 
> > may be applied.The packet's source and destination 
> > address fields may be exchanged at the point of congestion. 
> > The packet may be returned to where the associated overflow 
> > road system can be entered. There, source and destination 
> > address fields have to be exchanged once again and the packet may be
> > forwarded with the alternate DSCP along the associated 
> > alternate road system.
> > 
> > Wouldn't this be a nice add-on ?
> 
> I'm no expert in PNNI, but isn't this exactly what it does 
> when it cannot meet the call setup QoS parameters along the 
> shortest path route?
 Hi, even some of NSIS and resource management functions 
looks like the same. But that doesnt mean that we dont have 
to come up something new. But a clear line between the analysis 
is essential. I am much less interested in taking MPLS into the 
picture. Of from a purely research angle, analyzing with DSCP 
alone works fine. We can introduce some sort of non-cooperative 
routing which is the default scheme for many peer to peer 
communications. A lot of heuristics based, query based, index baed 
algorithms can be done which can some day become an alternative to 
SPF. But looking from a engineering perspective, no doubt SPF will 
rule.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug 13 11:05:03 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15142
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:05:03 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA14831
	for routing-discussion-archive@odin.ietf.org; Tue, 13 Aug 2002 11:06:21 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA13312;
	Tue, 13 Aug 2002 10:41:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA13274
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 10:41:00 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14195
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 10:39:41 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id QAA12493;
	Tue, 13 Aug 2002 16:40:55 +0200 (MET DST)
Received: from mchh274e.demchh201e.icn.siemens.de ([139.21.200.84])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id QAA05502;
	Tue, 13 Aug 2002 16:40:56 +0200 (MET DST)
Received: by MCHH274E with Internet Mail Service (5.5.2656.59)
	id <P83CL0LK>; Tue, 13 Aug 2002 16:40:31 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B99D@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Cc: routing-discussion@ietf.org
Subject: AW: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 16:40:25 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA13277
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Senthil,

Here it is about fast rerouting of IP packets by cranking back to that router where the overflow road system 
may be entered.

You are mentioning NSIS. 
NSIS is interested in two-way applications and would benefit if the two inverse directed pathes are identical.
This is automatically provided by using a smallest size tree road system.

I think the more we debate, the more usefull things we will discover:-)

Heinrich



-----Ursprüngliche Nachricht-----
Von: Ayyasamy, Senthilkumar (UMKC-Student) [mailto:saq66@umkc.edu]
Gesendet: Dienstag, 13. August 2002 16:28
An: Manfredi, Albert E; Hummel Heinrich
Cc: routing-discussion@ietf.org
Betreff: RE: AW: Differentiated Routing, not only plain rambo-SPF


> > Right this moment I looked at new email-thread on MPLS list 
> > "fast re-route merging".
> > What popped up in my mind:
> > The smallest size tree road system is, in practice, 
> > BI-DIRECTIONAL. It should be feasable to
> > crank back:  Either   IP-in-IP or some new TYPE information 
> > may be applied.The packet's source and destination 
> > address fields may be exchanged at the point of congestion. 
> > The packet may be returned to where the associated overflow 
> > road system can be entered. There, source and destination 
> > address fields have to be exchanged once again and the packet may be
> > forwarded with the alternate DSCP along the associated 
> > alternate road system.
> > 
> > Wouldn't this be a nice add-on ?
> 
> I'm no expert in PNNI, but isn't this exactly what it does 
> when it cannot meet the call setup QoS parameters along the 
> shortest path route?
 Hi, even some of NSIS and resource management functions 
looks like the same. But that doesnt mean that we dont have 
to come up something new. But a clear line between the analysis 
is essential. I am much less interested in taking MPLS into the 
picture. Of from a purely research angle, analyzing with DSCP 
alone works fine. We can introduce some sort of non-cooperative 
routing which is the default scheme for many peer to peer 
communications. A lot of heuristics based, query based, index baed 
algorithms can be done which can some day become an alternative to 
SPF. But looking from a engineering perspective, no doubt SPF will 
rule.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug 13 11:12:24 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15369
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:12:24 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA14703;
	Tue, 13 Aug 2002 11:02:23 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA14676
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 11:02:21 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15031
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 11:01:02 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA20146;
	Tue, 13 Aug 2002 11:01:41 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA11474;
	Tue, 13 Aug 2002 11:01:42 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99VFN7>; Tue, 13 Aug 2002 11:01:41 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632E3@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
To: "'Hummel Heinrich'" <Heinrich.Hummel@icn.siemens.de>,
        "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Cc: routing-discussion@ietf.org,
        "'irtf-rr@puck.nether.net'"
	 <irtf-rr@puck.nether.net>
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 11:01:38 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Heinrich,
 
-> I think the more we debate, the more usefull things we will 
-> discover:-)

  Yes! you are right :) But we can't keep on discussing or
  learning things... :-)

  Average age of a person who can make significant 
  novel contribution to any field will increase in 
  future years. Next generations will definitely 
  suffer & struggle for existence in the changing 
  facets of science & technology (unless intellectual 
  power of humans increase by birth). 

  To make it crystal clear, now (in 2002) it is 
  enough to invent something new/beneficial technology,
  if we follow past work done by few Yakov Rekhters.
  But in future, an average inventor must know
  thousands of such Yakov Rekhters works. Is that 
  possible in a life span ? :)

  It is highly unlikely that a person can invent 
  something new with out complete understanding of 
  relevant past work done on any subject.

  I am really worried...

--
Venkata.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug 13 11:12:25 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15376
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:12:24 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA15272
	for routing-discussion-archive@odin.ietf.org; Tue, 13 Aug 2002 11:13:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA14703;
	Tue, 13 Aug 2002 11:02:23 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA14676
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 11:02:21 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15031
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 11:01:02 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA20146;
	Tue, 13 Aug 2002 11:01:41 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA11474;
	Tue, 13 Aug 2002 11:01:42 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99VFN7>; Tue, 13 Aug 2002 11:01:41 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632E3@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
To: "'Hummel Heinrich'" <Heinrich.Hummel@icn.siemens.de>,
        "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Cc: routing-discussion@ietf.org,
        "'irtf-rr@puck.nether.net'"
	 <irtf-rr@puck.nether.net>
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 11:01:38 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Heinrich,
 
-> I think the more we debate, the more usefull things we will 
-> discover:-)

  Yes! you are right :) But we can't keep on discussing or
  learning things... :-)

  Average age of a person who can make significant 
  novel contribution to any field will increase in 
  future years. Next generations will definitely 
  suffer & struggle for existence in the changing 
  facets of science & technology (unless intellectual 
  power of humans increase by birth). 

  To make it crystal clear, now (in 2002) it is 
  enough to invent something new/beneficial technology,
  if we follow past work done by few Yakov Rekhters.
  But in future, an average inventor must know
  thousands of such Yakov Rekhters works. Is that 
  possible in a life span ? :)

  It is highly unlikely that a person can invent 
  something new with out complete understanding of 
  relevant past work done on any subject.

  I am really worried...

--
Venkata.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug 13 11:16:20 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15603
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:16:20 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA13264;
	Tue, 13 Aug 2002 10:40:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA13236
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 10:40:54 -0400 (EDT)
Received: from kc-msxproto2.kc.umkc.edu (kc-msxproto2.kc.umkc.edu [134.193.143.159])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14175
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 10:39:36 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 13 Aug 2002 09:40:52 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 09:40:17 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD433161010A297A@KC-MAIL2.kc.umkc.edu>
Thread-Topic: RE: AW: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcJC11fNv4OkNLEeRN64Eok2XBVR/g==
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>,
        "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>,
        "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Cc: <routing-discussion@ietf.org>,
        "irtf-rr@puck.nether.net" <'irtf-rr@puck.nether.net'>
X-OriginalArrivalTime: 13 Aug 2002 14:40:52.0351 (UTC) FILETIME=[6C6140F0:01C242D7]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA13237
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit


> -> yes,it is similar;
> -> but here it is about state-less IP forwarding, i.e. about 
> -> forwarding the individual IP packets, without any
> -> RSVP path and without any MPLS path.
> 
>   Oh! Ok...you would like to do Crankback in
>   connection less IP environments?!?
> 
>   In such a case, you might find below paper interesting:
> http://www.ecse.rpi.edu/Homepages/shivkuma/research/papers/te-
> latest.pdf
 I have studied this paper. Your are mis-interpreting here. The RPI
paper is an increment to OSPF or BGP for some traffic engineering
functionalties. It doesnt require signaling whereas, diffrout 
requires signaling. Also, we are taking more from a diffserv 
point of view.
 As i told, routing in peer to peer networks and some overlay 
systems can use diffrout concept. We can explore certain non-
cooperative algorithms for an alternative to SPF. But as mentioned
before, this will not work out if we see from an engineering 
perspective. 

> 
>   There was some discussion in E2E list regarding
>   pros & cons of this approach. I couldn't find the URL
>   but I vaguely remember that the subject of the discussion
>   is "EC++N" or something like that...

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug 13 11:16:20 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15611
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:16:20 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA15745
	for routing-discussion-archive@odin.ietf.org; Tue, 13 Aug 2002 11:17:38 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA13264;
	Tue, 13 Aug 2002 10:40:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA13236
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 10:40:54 -0400 (EDT)
Received: from kc-msxproto2.kc.umkc.edu (kc-msxproto2.kc.umkc.edu [134.193.143.159])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14175
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 10:39:36 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 13 Aug 2002 09:40:52 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 09:40:17 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD433161010A297A@KC-MAIL2.kc.umkc.edu>
Thread-Topic: RE: AW: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcJC11fNv4OkNLEeRN64Eok2XBVR/g==
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>,
        "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>,
        "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Cc: <routing-discussion@ietf.org>,
        "irtf-rr@puck.nether.net" <'irtf-rr@puck.nether.net'>
X-OriginalArrivalTime: 13 Aug 2002 14:40:52.0351 (UTC) FILETIME=[6C6140F0:01C242D7]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA13237
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit


> -> yes,it is similar;
> -> but here it is about state-less IP forwarding, i.e. about 
> -> forwarding the individual IP packets, without any
> -> RSVP path and without any MPLS path.
> 
>   Oh! Ok...you would like to do Crankback in
>   connection less IP environments?!?
> 
>   In such a case, you might find below paper interesting:
> http://www.ecse.rpi.edu/Homepages/shivkuma/research/papers/te-
> latest.pdf
 I have studied this paper. Your are mis-interpreting here. The RPI
paper is an increment to OSPF or BGP for some traffic engineering
functionalties. It doesnt require signaling whereas, diffrout 
requires signaling. Also, we are taking more from a diffserv 
point of view.
 As i told, routing in peer to peer networks and some overlay 
systems can use diffrout concept. We can explore certain non-
cooperative algorithms for an alternative to SPF. But as mentioned
before, this will not work out if we see from an engineering 
perspective. 

> 
>   There was some discussion in E2E list regarding
>   pros & cons of this approach. I couldn't find the URL
>   but I vaguely remember that the subject of the discussion
>   is "EC++N" or something like that...

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug 13 11:17:08 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15677
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:17:08 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA14877;
	Tue, 13 Aug 2002 11:06:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA14842
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 11:06:32 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15184
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 11:05:13 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id RAA14105;
	Tue, 13 Aug 2002 17:06:25 +0200 (MET DST)
Received: from mchh273e.demchh201e.icn.siemens.de ([139.21.200.83])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id RAA18322;
	Tue, 13 Aug 2002 17:06:25 +0200 (MET DST)
Received: by MCHH273E with Internet Mail Service (5.5.2656.59)
	id <P71RGF08>; Tue, 13 Aug 2002 17:06:00 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B99E@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        "Naidu, Venkata" <Venkata.Naidu@Marconi.com>,
        "Manfredi, Albert E"
	 <albert.e.manfredi@boeing.com>
Cc: routing-discussion@ietf.org, irtf-rr@puck.nether.net
Subject: AW: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 17:05:54 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA14843
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

I am sorry, but there is no signalling (like RSVP, RSVP-TE, CR-LDP) for doing DiffRout.

Based on the information exchanged by the routing protocol (like OSPF) all nodes should be able to
compute the same smallest size tree which interconnects the edge routers (those with attached users or attached external interfaces), and which complies to some specific constraints (QoS/BW/Policy,eventually avoiding overlaps with other 
road systems),and which are associated to the same DSCP(s).  // plural: see my  previous email from today

But there is no signalling as to "establish the DSCP-associated road system" !!!

However,it would be a fancy but completely new task to determine and establish an MPLS-road system,
which may lock MPLS-traffic into such slim Smallest Size Tree graphs. See all my work on establishing
the "road systems for VPNs" based on elementary+ hierarchical LSPs.

Heinrich



-----Ursprüngliche Nachricht-----
Von: Ayyasamy, Senthilkumar (UMKC-Student) [mailto:saq66@umkc.edu]
Gesendet: Dienstag, 13. August 2002 16:40
An: Naidu, Venkata; Hummel Heinrich; Manfredi, Albert E
Cc: routing-discussion@ietf.org; irtf-rr@puck.nether.net
Betreff: RE: AW: Differentiated Routing, not only plain rambo-SPF



> -> yes,it is similar;
> -> but here it is about state-less IP forwarding, i.e. about 
> -> forwarding the individual IP packets, without any
> -> RSVP path and without any MPLS path.
> 
>   Oh! Ok...you would like to do Crankback in
>   connection less IP environments?!?
> 
>   In such a case, you might find below paper interesting:
> http://www.ecse.rpi.edu/Homepages/shivkuma/research/papers/te-
> latest.pdf
 I have studied this paper. Your are mis-interpreting here. The RPI
paper is an increment to OSPF or BGP for some traffic engineering
functionalties. It doesnt require signaling whereas, diffrout 
requires signaling. Also, we are taking more from a diffserv 
point of view.
 As i told, routing in peer to peer networks and some overlay 
systems can use diffrout concept. We can explore certain non-
cooperative algorithms for an alternative to SPF. But as mentioned
before, this will not work out if we see from an engineering 
perspective. 

> 
>   There was some discussion in E2E list regarding
>   pros & cons of this approach. I couldn't find the URL
>   but I vaguely remember that the subject of the discussion
>   is "EC++N" or something like that...

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug 13 11:17:09 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15683
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:17:08 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA15854
	for routing-discussion-archive@odin.ietf.org; Tue, 13 Aug 2002 11:18:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA14877;
	Tue, 13 Aug 2002 11:06:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA14842
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 11:06:32 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15184
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 11:05:13 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id RAA14105;
	Tue, 13 Aug 2002 17:06:25 +0200 (MET DST)
Received: from mchh273e.demchh201e.icn.siemens.de ([139.21.200.83])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id RAA18322;
	Tue, 13 Aug 2002 17:06:25 +0200 (MET DST)
Received: by MCHH273E with Internet Mail Service (5.5.2656.59)
	id <P71RGF08>; Tue, 13 Aug 2002 17:06:00 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B99E@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        "Naidu, Venkata" <Venkata.Naidu@Marconi.com>,
        "Manfredi, Albert E"
	 <albert.e.manfredi@boeing.com>
Cc: routing-discussion@ietf.org, irtf-rr@puck.nether.net
Subject: AW: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 17:05:54 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA14843
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

I am sorry, but there is no signalling (like RSVP, RSVP-TE, CR-LDP) for doing DiffRout.

Based on the information exchanged by the routing protocol (like OSPF) all nodes should be able to
compute the same smallest size tree which interconnects the edge routers (those with attached users or attached external interfaces), and which complies to some specific constraints (QoS/BW/Policy,eventually avoiding overlaps with other 
road systems),and which are associated to the same DSCP(s).  // plural: see my  previous email from today

But there is no signalling as to "establish the DSCP-associated road system" !!!

However,it would be a fancy but completely new task to determine and establish an MPLS-road system,
which may lock MPLS-traffic into such slim Smallest Size Tree graphs. See all my work on establishing
the "road systems for VPNs" based on elementary+ hierarchical LSPs.

Heinrich



-----Ursprüngliche Nachricht-----
Von: Ayyasamy, Senthilkumar (UMKC-Student) [mailto:saq66@umkc.edu]
Gesendet: Dienstag, 13. August 2002 16:40
An: Naidu, Venkata; Hummel Heinrich; Manfredi, Albert E
Cc: routing-discussion@ietf.org; irtf-rr@puck.nether.net
Betreff: RE: AW: Differentiated Routing, not only plain rambo-SPF



> -> yes,it is similar;
> -> but here it is about state-less IP forwarding, i.e. about 
> -> forwarding the individual IP packets, without any
> -> RSVP path and without any MPLS path.
> 
>   Oh! Ok...you would like to do Crankback in
>   connection less IP environments?!?
> 
>   In such a case, you might find below paper interesting:
> http://www.ecse.rpi.edu/Homepages/shivkuma/research/papers/te-
> latest.pdf
 I have studied this paper. Your are mis-interpreting here. The RPI
paper is an increment to OSPF or BGP for some traffic engineering
functionalties. It doesnt require signaling whereas, diffrout 
requires signaling. Also, we are taking more from a diffserv 
point of view.
 As i told, routing in peer to peer networks and some overlay 
systems can use diffrout concept. We can explore certain non-
cooperative algorithms for an alternative to SPF. But as mentioned
before, this will not work out if we see from an engineering 
perspective. 

> 
>   There was some discussion in E2E list regarding
>   pros & cons of this approach. I couldn't find the URL
>   but I vaguely remember that the subject of the discussion
>   is "EC++N" or something like that...

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug 13 11:26:59 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16172
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:26:59 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15318;
	Tue, 13 Aug 2002 11:13:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15287
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 11:13:55 -0400 (EDT)
Received: from kc-msxproto4.kc.umkc.edu (kc-msxproto4.kc.umkc.edu [134.193.143.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15409
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 11:12:36 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 13 Aug 2002 10:13:53 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 10:13:27 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C2540@KC-MAIL2.kc.umkc.edu>
Thread-Topic: AW: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcJC2wVbvBpSCzdhSq22rnYtxklySwAADolA
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>,
        "Naidu, Venkata" <Venkata.Naidu@Marconi.com>,
        "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Cc: <routing-discussion@ietf.org>, <irtf-rr@puck.nether.net>
X-OriginalArrivalTime: 13 Aug 2002 15:13:53.0543 (UTC) FILETIME=[09432970:01C242DC]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA15288
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit


> I am sorry, but there is no signalling (like RSVP, RSVP-TE, 
> CR-LDP) for doing DiffRout.

 My mistake here.. But diffrout has few goals in common with
the RPIs *BANANAS* traffic engineering framework but sometimes
complimentary too. The best suggestion might be ..why cant 
you come up with some very rough draft version.So that, we 
can be clear that we are discussing the same scheme. I have 
one picture of diffrout, some others think that as diffser-TE 
and so , it is better if we have some notes before discussion.

> 
> Based on the information exchanged by the routing protocol 
> (like OSPF) all nodes should be able to
> compute the same smallest size tree which interconnects the 
> edge routers (those with attached users or attached external 
> interfaces), and which complies to some specific constraints 
> (QoS/BW/Policy,eventually avoiding overlaps with other 
> road systems),and which are associated to the same DSCP(s).  
> // plural: see my  previous email from today
> 
> But there is no signalling as to "establish the 
> DSCP-associated road system" !!!
> 
> However,it would be a fancy but completely new task to 
> determine and establish an MPLS-road system,
> which may lock MPLS-traffic into such slim Smallest Size Tree 
> graphs. See all my work on establishing
> the "road systems for VPNs" based on elementary+ hierarchical LSPs.
> 
> Heinrich
> 
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: Ayyasamy, Senthilkumar (UMKC-Student) [mailto:saq66@umkc.edu]
> Gesendet: Dienstag, 13. August 2002 16:40
> An: Naidu, Venkata; Hummel Heinrich; Manfredi, Albert E
> Cc: routing-discussion@ietf.org; irtf-rr@puck.nether.net
> Betreff: RE: AW: Differentiated Routing, not only plain rambo-SPF
> 
> 
> 
> > -> yes,it is similar;
> > -> but here it is about state-less IP forwarding, i.e. about 
> > -> forwarding the individual IP packets, without any
> > -> RSVP path and without any MPLS path.
> > 
> >   Oh! Ok...you would like to do Crankback in
> >   connection less IP environments?!?
> > 
> >   In such a case, you might find below paper interesting:
> > http://www.ecse.rpi.edu/Homepages/shivkuma/research/papers/te-
> > latest.pdf
>  I have studied this paper. Your are mis-interpreting here. The RPI
> paper is an increment to OSPF or BGP for some traffic engineering
> functionalties. It doesnt require signaling whereas, diffrout 
> requires signaling. Also, we are taking more from a diffserv 
> point of view.
>  As i told, routing in peer to peer networks and some overlay 
> systems can use diffrout concept. We can explore certain non-
> cooperative algorithms for an alternative to SPF. But as mentioned
> before, this will not work out if we see from an engineering 
> perspective. 
> 
> > 
> >   There was some discussion in E2E list regarding
> >   pros & cons of this approach. I couldn't find the URL
> >   but I vaguely remember that the subject of the discussion
> >   is "EC++N" or something like that...
> 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug 13 11:26:59 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16179
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:26:59 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA16616
	for routing-discussion-archive@odin.ietf.org; Tue, 13 Aug 2002 11:28:17 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15318;
	Tue, 13 Aug 2002 11:13:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15287
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 11:13:55 -0400 (EDT)
Received: from kc-msxproto4.kc.umkc.edu (kc-msxproto4.kc.umkc.edu [134.193.143.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15409
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 11:12:36 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 13 Aug 2002 10:13:53 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 10:13:27 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C2540@KC-MAIL2.kc.umkc.edu>
Thread-Topic: AW: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcJC2wVbvBpSCzdhSq22rnYtxklySwAADolA
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Hummel Heinrich" <Heinrich.Hummel@icn.siemens.de>,
        "Naidu, Venkata" <Venkata.Naidu@Marconi.com>,
        "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Cc: <routing-discussion@ietf.org>, <irtf-rr@puck.nether.net>
X-OriginalArrivalTime: 13 Aug 2002 15:13:53.0543 (UTC) FILETIME=[09432970:01C242DC]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA15288
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit


> I am sorry, but there is no signalling (like RSVP, RSVP-TE, 
> CR-LDP) for doing DiffRout.

 My mistake here.. But diffrout has few goals in common with
the RPIs *BANANAS* traffic engineering framework but sometimes
complimentary too. The best suggestion might be ..why cant 
you come up with some very rough draft version.So that, we 
can be clear that we are discussing the same scheme. I have 
one picture of diffrout, some others think that as diffser-TE 
and so , it is better if we have some notes before discussion.

> 
> Based on the information exchanged by the routing protocol 
> (like OSPF) all nodes should be able to
> compute the same smallest size tree which interconnects the 
> edge routers (those with attached users or attached external 
> interfaces), and which complies to some specific constraints 
> (QoS/BW/Policy,eventually avoiding overlaps with other 
> road systems),and which are associated to the same DSCP(s).  
> // plural: see my  previous email from today
> 
> But there is no signalling as to "establish the 
> DSCP-associated road system" !!!
> 
> However,it would be a fancy but completely new task to 
> determine and establish an MPLS-road system,
> which may lock MPLS-traffic into such slim Smallest Size Tree 
> graphs. See all my work on establishing
> the "road systems for VPNs" based on elementary+ hierarchical LSPs.
> 
> Heinrich
> 
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: Ayyasamy, Senthilkumar (UMKC-Student) [mailto:saq66@umkc.edu]
> Gesendet: Dienstag, 13. August 2002 16:40
> An: Naidu, Venkata; Hummel Heinrich; Manfredi, Albert E
> Cc: routing-discussion@ietf.org; irtf-rr@puck.nether.net
> Betreff: RE: AW: Differentiated Routing, not only plain rambo-SPF
> 
> 
> 
> > -> yes,it is similar;
> > -> but here it is about state-less IP forwarding, i.e. about 
> > -> forwarding the individual IP packets, without any
> > -> RSVP path and without any MPLS path.
> > 
> >   Oh! Ok...you would like to do Crankback in
> >   connection less IP environments?!?
> > 
> >   In such a case, you might find below paper interesting:
> > http://www.ecse.rpi.edu/Homepages/shivkuma/research/papers/te-
> > latest.pdf
>  I have studied this paper. Your are mis-interpreting here. The RPI
> paper is an increment to OSPF or BGP for some traffic engineering
> functionalties. It doesnt require signaling whereas, diffrout 
> requires signaling. Also, we are taking more from a diffserv 
> point of view.
>  As i told, routing in peer to peer networks and some overlay 
> systems can use diffrout concept. We can explore certain non-
> cooperative algorithms for an alternative to SPF. But as mentioned
> before, this will not work out if we see from an engineering 
> perspective. 
> 
> > 
> >   There was some discussion in E2E list regarding
> >   pros & cons of this approach. I couldn't find the URL
> >   but I vaguely remember that the subject of the discussion
> >   is "EC++N" or something like that...
> 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug 13 11:31:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16426
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:31:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15591;
	Tue, 13 Aug 2002 11:16:55 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15533
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 11:16:53 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15533
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 11:15:33 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA21252;
	Tue, 13 Aug 2002 11:16:13 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA15774;
	Tue, 13 Aug 2002 11:16:14 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99VGL7>; Tue, 13 Aug 2002 11:16:13 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632E4@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
Cc: routing-discussion@ietf.org, irtf-rr@puck.nether.net
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 11:16:10 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Senthil,

-> > -> yes,it is similar;
-> > -> but here it is about state-less IP forwarding, i.e. about 
-> > -> forwarding the individual IP packets, without any
-> > -> RSVP path and without any MPLS path.
-> > 
-> >   Oh! Ok...you would like to do Crankback in
-> >   connection less IP environments?!?
-> > 
-> >   In such a case, you might find below paper interesting:
-> > http://www.ecse.rpi.edu/Homepages/shivkuma/research/papers/te-
-> > latest.pdf
->  I have studied this paper. Your are mis-interpreting here. The RPI
-> paper is an increment to OSPF or BGP for some traffic engineering
-> functionalties. It doesnt require signaling whereas, diffrout 
-> requires signaling. 

  Heinrich is talking about connection-less, no RSVP, no MPLS
  signaling. I just pointed a *relavent* paper. 
  
  You can find solution to any problem in multiple ways. 
 
  The problem in hand is:
  - Bypass congestion area *effectively* 
    using best of today's technologies
  - Effecient utilization of resources 
  - Fast forwarding
  - QoS (end-to-end perspective)
    etc etc

  IMO, after working for many years in MPLS & relavent technologies,
  I am convinced that MPLS will solve most of the problem we couldn't
  solve in the past *effectively*. Ofcourse, there are some issues
  with MPLS, still, I think, we can solve most of the above issues 
  very efficiently using MPLS than traditional IP routing.

  That is why I am arguing that, what ever problem in hand, can be
  solved by recent advancements in MPLS. Let us not go back to the
  past where we tried to achieve things in connection-less IP 
  environments.

  The work done by RPI guys is something similar to what Heinrich
  is discussing. Especially, section 3.1. Interested people can
  compare/contrast similar work done in the past (like above paper).

--
Venkata

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug 13 11:31:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16432
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:31:56 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA17332
	for routing-discussion-archive@odin.ietf.org; Tue, 13 Aug 2002 11:33:15 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15591;
	Tue, 13 Aug 2002 11:16:55 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15533
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 11:16:53 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15533
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 11:15:33 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA21252;
	Tue, 13 Aug 2002 11:16:13 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA15774;
	Tue, 13 Aug 2002 11:16:14 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99VGL7>; Tue, 13 Aug 2002 11:16:13 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632E4@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
Cc: routing-discussion@ietf.org, irtf-rr@puck.nether.net
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 11:16:10 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Senthil,

-> > -> yes,it is similar;
-> > -> but here it is about state-less IP forwarding, i.e. about 
-> > -> forwarding the individual IP packets, without any
-> > -> RSVP path and without any MPLS path.
-> > 
-> >   Oh! Ok...you would like to do Crankback in
-> >   connection less IP environments?!?
-> > 
-> >   In such a case, you might find below paper interesting:
-> > http://www.ecse.rpi.edu/Homepages/shivkuma/research/papers/te-
-> > latest.pdf
->  I have studied this paper. Your are mis-interpreting here. The RPI
-> paper is an increment to OSPF or BGP for some traffic engineering
-> functionalties. It doesnt require signaling whereas, diffrout 
-> requires signaling. 

  Heinrich is talking about connection-less, no RSVP, no MPLS
  signaling. I just pointed a *relavent* paper. 
  
  You can find solution to any problem in multiple ways. 
 
  The problem in hand is:
  - Bypass congestion area *effectively* 
    using best of today's technologies
  - Effecient utilization of resources 
  - Fast forwarding
  - QoS (end-to-end perspective)
    etc etc

  IMO, after working for many years in MPLS & relavent technologies,
  I am convinced that MPLS will solve most of the problem we couldn't
  solve in the past *effectively*. Ofcourse, there are some issues
  with MPLS, still, I think, we can solve most of the above issues 
  very efficiently using MPLS than traditional IP routing.

  That is why I am arguing that, what ever problem in hand, can be
  solved by recent advancements in MPLS. Let us not go back to the
  past where we tried to achieve things in connection-less IP 
  environments.

  The work done by RPI guys is something similar to what Heinrich
  is discussing. Especially, section 3.1. Interested people can
  compare/contrast similar work done in the past (like above paper).

--
Venkata

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug 13 11:32:25 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16460
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:32:24 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15943;
	Tue, 13 Aug 2002 11:20:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15918
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 11:20:14 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15805
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 11:18:55 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA21511;
	Tue, 13 Aug 2002 11:19:28 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA16746;
	Tue, 13 Aug 2002 11:19:28 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99VG4V>; Tue, 13 Aug 2002 11:19:27 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632E5@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
Cc: routing-discussion@ietf.org, irtf-rr@puck.nether.net
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 11:19:26 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

-> The best suggestion might be ..why cant 
-> you come up with some very rough draft version.So that, we 
-> can be clear that we are discussing the same scheme. I have 
-> one picture of diffrout, some others think that as diffser-TE 
-> and so , it is better if we have some notes before discussion.

  I completely agree.

--
Venkata

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From routing-discussion-admin@ietf.org  Tue Aug 13 11:38:45 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16819
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:38:44 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA16522;
	Tue, 13 Aug 2002 11:25:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA16490
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 11:25:54 -0400 (EDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [192.161.36.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16104
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 11:24:34 -0400 (EDT)
Received: from stl-av-01.boeing.com ([192.76.190.6])
	by blv-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id IAA08307;
	Tue, 13 Aug 2002 08:25:50 -0700 (PDT)
Received: from blv-hub-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id KAA20847;
	Tue, 13 Aug 2002 10:25:41 -0500 (CDT)
Received: from xch-phl-02p.ne.nos.boeing.com (xch-phl-02p.ne.nos.boeing.com [128.225.22.4])
	by blv-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id g7DFPlm21988;
	Tue, 13 Aug 2002 08:25:47 -0700 (PDT)
Received: by xch-phl-02p.ne.nos.boeing.com with Internet Mail Service (5.5.2650.21)
	id <37GW8JC5>; Tue, 13 Aug 2002 11:25:46 -0400
Message-ID: <8D6509B44ACCEB43A96E032B9C3EA0C8078A3A95@xch-ne-02.ne.nos.boeing.com>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>
Cc: routing-discussion@ietf.org
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 11:25:47 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Ayyasamy, Senthilkumar wrote:

> > I am sorry, but there is no signalling (like RSVP, RSVP-TE, 
> > CR-LDP) for doing DiffRout.
> 
>  My mistake here.. But diffrout has few goals in common with
> the RPIs *BANANAS* traffic engineering framework but sometimes
> complimentary too. The best suggestion might be ..why cant 
> you come up with some very rough draft version.So that, we 
> can be clear that we are discussing the same scheme. I have 
> one picture of diffrout, some others think that as diffser-TE 
> and so , it is better if we have some notes before discussion.

My reading of diffserv and diffrout is that even if the basic concepts don't require signaling, a signaling protocol will need to be added to make these schemes workable. In diffserv, for example, the per-hop or per-domain behavior associated with any given DSCP will only be valid within certain traffic load limits. The fact that diffserv does not address exactly how those load limits are maintained, other than to mention SLAs, does not mean that _some_ signaling scheme won't be required to make the system work.

Also, I don't believe the Iwata draft is stateless crankback? Maybe I misunderstood, and no one claimed that.

http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04.txt

If you're dealing with LSPs, you're dealing with stateful routing, no?

Bert

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug 13 11:38:45 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16827
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:38:45 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA17720
	for routing-discussion-archive@odin.ietf.org; Tue, 13 Aug 2002 11:40:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA16522;
	Tue, 13 Aug 2002 11:25:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA16490
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 11:25:54 -0400 (EDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [192.161.36.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16104
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 11:24:34 -0400 (EDT)
Received: from stl-av-01.boeing.com ([192.76.190.6])
	by blv-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id IAA08307;
	Tue, 13 Aug 2002 08:25:50 -0700 (PDT)
Received: from blv-hub-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id KAA20847;
	Tue, 13 Aug 2002 10:25:41 -0500 (CDT)
Received: from xch-phl-02p.ne.nos.boeing.com (xch-phl-02p.ne.nos.boeing.com [128.225.22.4])
	by blv-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id g7DFPlm21988;
	Tue, 13 Aug 2002 08:25:47 -0700 (PDT)
Received: by xch-phl-02p.ne.nos.boeing.com with Internet Mail Service (5.5.2650.21)
	id <37GW8JC5>; Tue, 13 Aug 2002 11:25:46 -0400
Message-ID: <8D6509B44ACCEB43A96E032B9C3EA0C8078A3A95@xch-ne-02.ne.nos.boeing.com>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>
Cc: routing-discussion@ietf.org
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 11:25:47 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Ayyasamy, Senthilkumar wrote:

> > I am sorry, but there is no signalling (like RSVP, RSVP-TE, 
> > CR-LDP) for doing DiffRout.
> 
>  My mistake here.. But diffrout has few goals in common with
> the RPIs *BANANAS* traffic engineering framework but sometimes
> complimentary too. The best suggestion might be ..why cant 
> you come up with some very rough draft version.So that, we 
> can be clear that we are discussing the same scheme. I have 
> one picture of diffrout, some others think that as diffser-TE 
> and so , it is better if we have some notes before discussion.

My reading of diffserv and diffrout is that even if the basic concepts don't require signaling, a signaling protocol will need to be added to make these schemes workable. In diffserv, for example, the per-hop or per-domain behavior associated with any given DSCP will only be valid within certain traffic load limits. The fact that diffserv does not address exactly how those load limits are maintained, other than to mention SLAs, does not mean that _some_ signaling scheme won't be required to make the system work.

Also, I don't believe the Iwata draft is stateless crankback? Maybe I misunderstood, and no one claimed that.

http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04.txt

If you're dealing with LSPs, you're dealing with stateful routing, no?

Bert

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug 13 11:43:12 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17003
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:43:11 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA16466;
	Tue, 13 Aug 2002 11:25:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA16437
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 11:25:29 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16089
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 11:24:09 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id RAA15260;
	Tue, 13 Aug 2002 17:25:22 +0200 (MET DST)
Received: from mchh247e.demchh201e.icn.siemens.de ([139.21.200.57])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id RAA28214;
	Tue, 13 Aug 2002 17:25:23 +0200 (MET DST)
Received: by MCHH247E with Internet Mail Service (5.5.2656.59)
	id <P71TYWS1>; Tue, 13 Aug 2002 17:24:59 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B9A0@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Naidu, Venkata'" <Venkata.Naidu@Marconi.com>,
        "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Cc: routing-discussion@ietf.org,
        "'irtf-rr@puck.nether.net'"
	 <irtf-rr@puck.nether.net>
Subject: AW: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 17:24:59 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA16438
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Venkata,
We have only discussed for three weeks and have just scratched a little bit on the
disadvantages of SPF. Most of it in the light that real road traffic won't be managed
based on such egocentric view. We are about to look at the existing IETF concepts and will
certainly discover a lot of things which can be improved, simplified, enabled.

Heinrich


-----Ursprüngliche Nachricht-----
Von: Naidu, Venkata [mailto:Venkata.Naidu@Marconi.com]
Gesendet: Dienstag, 13. August 2002 17:02
An: 'Hummel Heinrich'; 'Ayyasamy, Senthilkumar (UMKC-Student)';
Manfredi, Albert E
Cc: routing-discussion@ietf.org; 'irtf-rr@puck.nether.net'
Betreff: RE: AW: Differentiated Routing, not only plain rambo-SPF


Heinrich,
 
-> I think the more we debate, the more usefull things we will 
-> discover:-)

  Yes! you are right :) But we can't keep on discussing or
  learning things... :-)

  Average age of a person who can make significant 
  novel contribution to any field will increase in 
  future years. Next generations will definitely 
  suffer & struggle for existence in the changing 
  facets of science & technology (unless intellectual 
  power of humans increase by birth). 

  To make it crystal clear, now (in 2002) it is 
  enough to invent something new/beneficial technology,
  if we follow past work done by few Yakov Rekhters.
  But in future, an average inventor must know
  thousands of such Yakov Rekhters works. Is that 
  possible in a life span ? :)

  It is highly unlikely that a person can invent 
  something new with out complete understanding of 
  relevant past work done on any subject.

  I am really worried...

--
Venkata.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug 13 11:43:12 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17009
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:43:12 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA17893
	for routing-discussion-archive@odin.ietf.org; Tue, 13 Aug 2002 11:44:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA16466;
	Tue, 13 Aug 2002 11:25:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA16437
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 11:25:29 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16089
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 11:24:09 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id RAA15260;
	Tue, 13 Aug 2002 17:25:22 +0200 (MET DST)
Received: from mchh247e.demchh201e.icn.siemens.de ([139.21.200.57])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id RAA28214;
	Tue, 13 Aug 2002 17:25:23 +0200 (MET DST)
Received: by MCHH247E with Internet Mail Service (5.5.2656.59)
	id <P71TYWS1>; Tue, 13 Aug 2002 17:24:59 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B9A0@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Naidu, Venkata'" <Venkata.Naidu@Marconi.com>,
        "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Cc: routing-discussion@ietf.org,
        "'irtf-rr@puck.nether.net'"
	 <irtf-rr@puck.nether.net>
Subject: AW: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 17:24:59 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA16438
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Venkata,
We have only discussed for three weeks and have just scratched a little bit on the
disadvantages of SPF. Most of it in the light that real road traffic won't be managed
based on such egocentric view. We are about to look at the existing IETF concepts and will
certainly discover a lot of things which can be improved, simplified, enabled.

Heinrich


-----Ursprüngliche Nachricht-----
Von: Naidu, Venkata [mailto:Venkata.Naidu@Marconi.com]
Gesendet: Dienstag, 13. August 2002 17:02
An: 'Hummel Heinrich'; 'Ayyasamy, Senthilkumar (UMKC-Student)';
Manfredi, Albert E
Cc: routing-discussion@ietf.org; 'irtf-rr@puck.nether.net'
Betreff: RE: AW: Differentiated Routing, not only plain rambo-SPF


Heinrich,
 
-> I think the more we debate, the more usefull things we will 
-> discover:-)

  Yes! you are right :) But we can't keep on discussing or
  learning things... :-)

  Average age of a person who can make significant 
  novel contribution to any field will increase in 
  future years. Next generations will definitely 
  suffer & struggle for existence in the changing 
  facets of science & technology (unless intellectual 
  power of humans increase by birth). 

  To make it crystal clear, now (in 2002) it is 
  enough to invent something new/beneficial technology,
  if we follow past work done by few Yakov Rekhters.
  But in future, an average inventor must know
  thousands of such Yakov Rekhters works. Is that 
  possible in a life span ? :)

  It is highly unlikely that a person can invent 
  something new with out complete understanding of 
  relevant past work done on any subject.

  I am really worried...

--
Venkata.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug 13 11:55:07 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17454
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:55:07 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17404;
	Tue, 13 Aug 2002 11:34:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17377
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 11:34:29 -0400 (EDT)
Received: from kc-msxproto2.kc.umkc.edu (kc-msxproto2.kc.umkc.edu [134.193.143.159])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16506
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 11:33:10 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 13 Aug 2002 10:34:27 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 10:33:38 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C2542@KC-MAIL2.kc.umkc.edu>
Thread-Topic: AW: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcJC3bVj193hWy8uTAuKq0CvZcKRFwAADOMg
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Cc: <routing-discussion@ietf.org>
X-OriginalArrivalTime: 13 Aug 2002 15:34:27.0402 (UTC) FILETIME=[E8B31AA0:01C242DE]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA17378
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit


> My reading of diffserv and diffrout is that even if the basic 
> concepts don't require signaling, a signaling protocol will 
> need to be added to make these schemes workable. In diffserv, 
> for example, the per-hop or per-domain behavior associated 
> with any given DSCP will only be valid within certain traffic 
> load limits. The fact that diffserv does not address exactly 
> how those load limits are maintained, other than to mention 
> SLAs, does not mean that _some_ signaling scheme won't be 
> required to make the system work.
   The fact is: we have defined diffserv only for data plane.
so, it doent mean we dont require signaling. Some of the next
steps for diffserv arch, they 
 - have to be defined end to end.
 -  signaling mechanism to support end to end 
 - Inter-domain business models.
so my comments with respect to diffserv is that it requires
signaling. I dont know about diffrout ..only hummel has to 
tell..

http://www.packetdesign.com/publications.html has a recent 
survey paper by Brian and  Kathie. Read them to get a picture. 



> 
> Also, I don't believe the Iwata draft is stateless crankback? 
> Maybe I misunderstood, and no one claimed that.
> 
> http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04.txt
> 
> If you're dealing with LSPs, you're dealing with stateful routing, no?
> 
> Bert
> 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug 13 11:55:08 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17464
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:55:08 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA18432
	for routing-discussion-archive@odin.ietf.org; Tue, 13 Aug 2002 11:56:26 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17404;
	Tue, 13 Aug 2002 11:34:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17377
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 11:34:29 -0400 (EDT)
Received: from kc-msxproto2.kc.umkc.edu (kc-msxproto2.kc.umkc.edu [134.193.143.159])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16506
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 11:33:10 -0400 (EDT)
Received: from KC-MAIL2.kc.umkc.edu ([134.193.143.162] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 13 Aug 2002 10:34:27 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 10:33:38 -0500
Message-ID: <A29143A40AEAE3459FF829D1DD4331613C2542@KC-MAIL2.kc.umkc.edu>
Thread-Topic: AW: Differentiated Routing, not only plain rambo-SPF
Thread-Index: AcJC3bVj193hWy8uTAuKq0CvZcKRFwAADOMg
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Cc: <routing-discussion@ietf.org>
X-OriginalArrivalTime: 13 Aug 2002 15:34:27.0402 (UTC) FILETIME=[E8B31AA0:01C242DE]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA17378
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit


> My reading of diffserv and diffrout is that even if the basic 
> concepts don't require signaling, a signaling protocol will 
> need to be added to make these schemes workable. In diffserv, 
> for example, the per-hop or per-domain behavior associated 
> with any given DSCP will only be valid within certain traffic 
> load limits. The fact that diffserv does not address exactly 
> how those load limits are maintained, other than to mention 
> SLAs, does not mean that _some_ signaling scheme won't be 
> required to make the system work.
   The fact is: we have defined diffserv only for data plane.
so, it doent mean we dont require signaling. Some of the next
steps for diffserv arch, they 
 - have to be defined end to end.
 -  signaling mechanism to support end to end 
 - Inter-domain business models.
so my comments with respect to diffserv is that it requires
signaling. I dont know about diffrout ..only hummel has to 
tell..

http://www.packetdesign.com/publications.html has a recent 
survey paper by Brian and  Kathie. Read them to get a picture. 



> 
> Also, I don't believe the Iwata draft is stateless crankback? 
> Maybe I misunderstood, and no one claimed that.
> 
> http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-04.txt
> 
> If you're dealing with LSPs, you're dealing with stateful routing, no?
> 
> Bert
> 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Tue Aug 13 11:57:38 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17576
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:57:38 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17638;
	Tue, 13 Aug 2002 11:39:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17607
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 11:39:03 -0400 (EDT)
Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16746
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 11:37:44 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id RAA17652;
	Tue, 13 Aug 2002 17:38:37 +0200 (MET DST)
Received: from mchh273e.demchh201e.icn.siemens.de ([139.21.200.83])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id RAA04447;
	Tue, 13 Aug 2002 17:38:57 +0200 (MET DST)
Received: by MCHH273E with Internet Mail Service (5.5.2656.59)
	id <P71RGHGN>; Tue, 13 Aug 2002 17:38:32 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B9A1@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        "Naidu, Venkata" <Venkata.Naidu@Marconi.com>,
        "Manfredi, Albert E"
	 <albert.e.manfredi@boeing.com>
Cc: routing-discussion@ietf.org, irtf-rr@puck.nether.net
Subject: AW: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 17:38:19 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org


The best suggestion might be ..why cant 
you come up with some very rough draft version.So that, we 
can be clear that we are discussing the same scheme. I have 
one picture of diffrout, some others think that as diffser-TE 
and so , it is better if we have some notes before discussion.


Certainly. It will be my pleasure to write a draft on this topic.
The day after tomorrow I will go on vacation. So it may take a little while :-)
Heinrich     

 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Tue Aug 13 11:57:39 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17584
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:57:39 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA18550
	for routing-discussion-archive@odin.ietf.org; Tue, 13 Aug 2002 11:58:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17638;
	Tue, 13 Aug 2002 11:39:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA17607
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 11:39:03 -0400 (EDT)
Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16746
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 11:37:44 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id RAA17652;
	Tue, 13 Aug 2002 17:38:37 +0200 (MET DST)
Received: from mchh273e.demchh201e.icn.siemens.de ([139.21.200.83])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id RAA04447;
	Tue, 13 Aug 2002 17:38:57 +0200 (MET DST)
Received: by MCHH273E with Internet Mail Service (5.5.2656.59)
	id <P71RGHGN>; Tue, 13 Aug 2002 17:38:32 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B9A1@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        "Naidu, Venkata" <Venkata.Naidu@Marconi.com>,
        "Manfredi, Albert E"
	 <albert.e.manfredi@boeing.com>
Cc: routing-discussion@ietf.org, irtf-rr@puck.nether.net
Subject: AW: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 17:38:19 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org


The best suggestion might be ..why cant 
you come up with some very rough draft version.So that, we 
can be clear that we are discussing the same scheme. I have 
one picture of diffrout, some others think that as diffser-TE 
and so , it is better if we have some notes before discussion.


Certainly. It will be my pleasure to write a draft on this topic.
The day after tomorrow I will go on vacation. So it may take a little while :-)
Heinrich     

 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From daemon@optimus.ietf.org  Tue Aug 13 12:26:03 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16467
	for <routing-discussion-archive@odin.ietf.org>; Tue, 13 Aug 2002 11:32:25 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA17355
	for routing-discussion-archive@odin.ietf.org; Tue, 13 Aug 2002 11:33:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15943;
	Tue, 13 Aug 2002 11:20:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15918
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 11:20:14 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15805
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 11:18:55 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA21511;
	Tue, 13 Aug 2002 11:19:28 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA16746;
	Tue, 13 Aug 2002 11:19:28 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99VG4V>; Tue, 13 Aug 2002 11:19:27 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632E5@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
To: "'Ayyasamy, Senthilkumar  (UMKC-Student)'" <saq66@umkc.edu>,
        Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
Cc: routing-discussion@ietf.org, irtf-rr@puck.nether.net
Subject: RE: AW: Differentiated Routing, not only plain rambo-SPF
Date: Tue, 13 Aug 2002 11:19:26 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

-> The best suggestion might be ..why cant 
-> you come up with some very rough draft version.So that, we 
-> can be clear that we are discussing the same scheme. I have 
-> one picture of diffrout, some others think that as diffser-TE 
-> and so , it is better if we have some notes before discussion.

  I completely agree.

--
Venkata

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Wed Aug 14 08:54:50 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07477
	for <routing-discussion-archive@odin.ietf.org>; Wed, 14 Aug 2002 08:54:49 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA26682;
	Wed, 14 Aug 2002 08:47:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA26660
	for <routing-discussion@optimus.ietf.org>; Wed, 14 Aug 2002 08:47:57 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07222
	for <routing-discussion@ietf.org>; Wed, 14 Aug 2002 08:46:36 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id OAA10309;
	Wed, 14 Aug 2002 14:47:50 +0200 (MET DST)
Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id OAA12849;
	Wed, 14 Aug 2002 14:47:53 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2656.59)
	id <PTSZK8W2>; Wed, 14 Aug 2002 14:47:28 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B9A2@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'jshen@cad.zju.edu.cn'" <jshen@cad.zju.edu.cn>, irtf-rr@puck.nether.net
Cc: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>,
        "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: AW: AW: Differentiated Routing, not only plain rambo-SPF
Date: Wed, 14 Aug 2002 14:47:24 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id IAA26661
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Let's assume there are two Smallest Size Tree road systems X1 and X2. X2 detours/avoids the kernel links of X1.
For some source/destination node pair the total pathes may be different. Or only the section in the middle is different.
Or only a section close to the source (or close to the dest.) is different. Whatever applies:
From the point of congestion on road system X1 the packet my crankback (hereby source and dest. address are swapped)
to that first node which is also part of X2.
There  source and dest. address are swapped again,  DSCP-X1 is replaced by DSCP-X2 and the packet is  moved forward 
via X2.

Heinrich

-----Ursprščngliche Nachricht-----
Von: shen jing [mailto:jshen@cad.zju.edu.cn]
Gesendet: Mittwoch, 14. August 2002 14:21
An: irtf-rr@puck.nether.net
Cc: 'Hummel Heinrich'; 'routing-discussion@ietf.org'
Betreff: Re: AW: Differentiated Routing, not only plain rambo-SPF



The discussion you mentioned is that of congestion removement by e2e
mechanism  or by routing. Professor Crowcroft proposed a method
named ECN++ which trigger a new path that acts when ECN bit is set 
in packet header.



> 
> Heinrich,
> 
> -> yes,it is similar;
> -> but here it is about state-less IP forwarding, i.e. about
> -> forwarding the individual IP packets, without any
> -> RSVP path and without any MPLS path.
> 
>   Oh! Ok...you would like to do Crankback in
>   connection less IP environments?!?
> 
>   In such a case, you might find below paper interesting:
> http://www.ecse.rpi.edu/Homepages/shivkuma/research/papers/te-latest.pdf
> 
>   There was some discussion in E2E list regarding
>   pros & cons of this approach. I couldn't find the URL
>   but I vaguely remember that the subject of the discussion
>   is "EC++N" or something like that...
> 
> --
> Venkata
> 
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion

-- 
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423
Mobile: (0)13516813753
Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Wed Aug 14 08:54:50 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07486
	for <routing-discussion-archive@odin.ietf.org>; Wed, 14 Aug 2002 08:54:50 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA26924
	for routing-discussion-archive@odin.ietf.org; Wed, 14 Aug 2002 08:56:10 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA26682;
	Wed, 14 Aug 2002 08:47:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA26660
	for <routing-discussion@optimus.ietf.org>; Wed, 14 Aug 2002 08:47:57 -0400 (EDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07222
	for <routing-discussion@ietf.org>; Wed, 14 Aug 2002 08:46:36 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id OAA10309;
	Wed, 14 Aug 2002 14:47:50 +0200 (MET DST)
Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id OAA12849;
	Wed, 14 Aug 2002 14:47:53 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2656.59)
	id <PTSZK8W2>; Wed, 14 Aug 2002 14:47:28 +0200
Message-ID: <EF8E39AA846CD411BB9C00508B951F510514B9A2@MCHH267E>
From: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
To: "'jshen@cad.zju.edu.cn'" <jshen@cad.zju.edu.cn>, irtf-rr@puck.nether.net
Cc: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>,
        "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: AW: AW: Differentiated Routing, not only plain rambo-SPF
Date: Wed, 14 Aug 2002 14:47:24 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id IAA26661
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Let's assume there are two Smallest Size Tree road systems X1 and X2. X2 detours/avoids the kernel links of X1.
For some source/destination node pair the total pathes may be different. Or only the section in the middle is different.
Or only a section close to the source (or close to the dest.) is different. Whatever applies:
From the point of congestion on road system X1 the packet my crankback (hereby source and dest. address are swapped)
to that first node which is also part of X2.
There  source and dest. address are swapped again,  DSCP-X1 is replaced by DSCP-X2 and the packet is  moved forward 
via X2.

Heinrich

-----Ursprščngliche Nachricht-----
Von: shen jing [mailto:jshen@cad.zju.edu.cn]
Gesendet: Mittwoch, 14. August 2002 14:21
An: irtf-rr@puck.nether.net
Cc: 'Hummel Heinrich'; 'routing-discussion@ietf.org'
Betreff: Re: AW: Differentiated Routing, not only plain rambo-SPF



The discussion you mentioned is that of congestion removement by e2e
mechanism  or by routing. Professor Crowcroft proposed a method
named ECN++ which trigger a new path that acts when ECN bit is set 
in packet header.



> 
> Heinrich,
> 
> -> yes,it is similar;
> -> but here it is about state-less IP forwarding, i.e. about
> -> forwarding the individual IP packets, without any
> -> RSVP path and without any MPLS path.
> 
>   Oh! Ok...you would like to do Crankback in
>   connection less IP environments?!?
> 
>   In such a case, you might find below paper interesting:
> http://www.ecse.rpi.edu/Homepages/shivkuma/research/papers/te-latest.pdf
> 
>   There was some discussion in E2E list regarding
>   pros & cons of this approach. I couldn't find the URL
>   but I vaguely remember that the subject of the discussion
>   is "EC++N" or something like that...
> 
> --
> Venkata
> 
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion

-- 
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423
Mobile: (0)13516813753
Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Wed Aug 14 10:12:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10001
	for <routing-discussion-archive@odin.ietf.org>; Wed, 14 Aug 2002 10:12:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00304;
	Wed, 14 Aug 2002 09:57:12 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00256
	for <routing-discussion@optimus.ietf.org>; Wed, 14 Aug 2002 09:57:09 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09279
	for <routing-discussion@ietf.org>; Wed, 14 Aug 2002 09:55:47 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA15829;
	Wed, 14 Aug 2002 09:56:35 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA10152;
	Wed, 14 Aug 2002 09:56:36 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99WLVD>; Wed, 14 Aug 2002 09:56:36 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632E9@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
To: "'jshen@cad.zju.edu.cn'" <jshen@cad.zju.edu.cn>, irtf-rr@puck.nether.net
Cc: "'Hummel Heinrich'" <Heinrich.Hummel@icn.siemens.de>,
        "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: RE: [Irtf-rr] Re: AW: Differentiated Routing, not only plain ramb
	o-SPF
Date: Wed, 14 Aug 2002 09:56:33 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="gb2312"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Shen,

Please follow the thread:
http://www.postel.org/pipermail/end2end-interest/2002-April/002006.html

--
Venkata.

-> -----Original Message-----
-> From: shen jing [mailto:jshen@cad.zju.edu.cn]
-> Sent: Wednesday, August 14, 2002 8:21 AM
-> To: irtf-rr@puck.nether.net
-> Cc: 'Hummel Heinrich'; 'routing-discussion@ietf.org'
-> Subject: [Irtf-rr] Re: AW: Differentiated Routing, not only 
-> plain rambo-SPF
-> 
-> 
-> 
-> The discussion you mentioned is that of congestion removement by e2e
-> mechanism  or by routing. Professor Crowcroft proposed a method
-> named ECN++ which trigger a new path that acts when ECN bit is set 
-> in packet header.
-> 
-> 
-> 
-> > 
-> > Heinrich,
-> > 
-> > -> yes,it is similar;
-> > -> but here it is about state-less IP forwarding, i.e. about
-> > -> forwarding the individual IP packets, without any
-> > -> RSVP path and without any MPLS path.
-> > 
-> >   Oh! Ok...you would like to do Crankback in
-> >   connection less IP environments?!?
-> > 
-> >   In such a case, you might find below paper interesting:
-> > 
-> http://www.ecse.rpi.edu/Homepages/shivkuma/research/papers/te
-> -latest.pdf
-> > 
-> >   There was some discussion in E2E list regarding
-> >   pros & cons of this approach. I couldn't find the URL
-> >   but I vaguely remember that the subject of the discussion
-> >   is "EC++N" or something like that...
-> > 
-> > --
-> > Venkata
-> > 
-> > _______________________________________________
-> > routing-discussion mailing list
-> > routing-discussion@ietf.org
-> > https://www1.ietf.org/mailman/listinfo/routing-discussion
-> 
-> -- 
-> Jing Shen
-> 
-> State Key Lab of CAD&CG
-> ZheJiang University(YuQuan)
-> HangZhou, Z.J. 310027
-> P.R.China
-> 
-> Tel: +86-571-87932423
-> Mobile: (0)13516813753
-> Email: jshen@cad.zju.edu.cn
-> 
-> *************************************************************
-> *********
-> * The SunShine of life is made up of very little beams which 
-> is      *
-> *  bright all the time                                       
->         *
-> *************************************************************
-> *********
-> _______________________________________________
-> Irtf-rr mailing list
-> Irtf-rr@puck.nether.net
-> http://puck.nether.net/mailman/listinfo/irtf-rr
-> 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Wed Aug 14 10:12:58 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10010
	for <routing-discussion-archive@odin.ietf.org>; Wed, 14 Aug 2002 10:12:57 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA01448
	for routing-discussion-archive@odin.ietf.org; Wed, 14 Aug 2002 10:14:17 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00304;
	Wed, 14 Aug 2002 09:57:12 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00256
	for <routing-discussion@optimus.ietf.org>; Wed, 14 Aug 2002 09:57:09 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09279
	for <routing-discussion@ietf.org>; Wed, 14 Aug 2002 09:55:47 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA15829;
	Wed, 14 Aug 2002 09:56:35 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA10152;
	Wed, 14 Aug 2002 09:56:36 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <3W99WLVD>; Wed, 14 Aug 2002 09:56:36 -0400
Message-ID: <39469E08BD83D411A3D900204840EC557632E9@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
To: "'jshen@cad.zju.edu.cn'" <jshen@cad.zju.edu.cn>, irtf-rr@puck.nether.net
Cc: "'Hummel Heinrich'" <Heinrich.Hummel@icn.siemens.de>,
        "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: RE: [Irtf-rr] Re: AW: Differentiated Routing, not only plain ramb
	o-SPF
Date: Wed, 14 Aug 2002 09:56:33 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="gb2312"
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org

Shen,

Please follow the thread:
http://www.postel.org/pipermail/end2end-interest/2002-April/002006.html

--
Venkata.

-> -----Original Message-----
-> From: shen jing [mailto:jshen@cad.zju.edu.cn]
-> Sent: Wednesday, August 14, 2002 8:21 AM
-> To: irtf-rr@puck.nether.net
-> Cc: 'Hummel Heinrich'; 'routing-discussion@ietf.org'
-> Subject: [Irtf-rr] Re: AW: Differentiated Routing, not only 
-> plain rambo-SPF
-> 
-> 
-> 
-> The discussion you mentioned is that of congestion removement by e2e
-> mechanism  or by routing. Professor Crowcroft proposed a method
-> named ECN++ which trigger a new path that acts when ECN bit is set 
-> in packet header.
-> 
-> 
-> 
-> > 
-> > Heinrich,
-> > 
-> > -> yes,it is similar;
-> > -> but here it is about state-less IP forwarding, i.e. about
-> > -> forwarding the individual IP packets, without any
-> > -> RSVP path and without any MPLS path.
-> > 
-> >   Oh! Ok...you would like to do Crankback in
-> >   connection less IP environments?!?
-> > 
-> >   In such a case, you might find below paper interesting:
-> > 
-> http://www.ecse.rpi.edu/Homepages/shivkuma/research/papers/te
-> -latest.pdf
-> > 
-> >   There was some discussion in E2E list regarding
-> >   pros & cons of this approach. I couldn't find the URL
-> >   but I vaguely remember that the subject of the discussion
-> >   is "EC++N" or something like that...
-> > 
-> > --
-> > Venkata
-> > 
-> > _______________________________________________
-> > routing-discussion mailing list
-> > routing-discussion@ietf.org
-> > https://www1.ietf.org/mailman/listinfo/routing-discussion
-> 
-> -- 
-> Jing Shen
-> 
-> State Key Lab of CAD&CG
-> ZheJiang University(YuQuan)
-> HangZhou, Z.J. 310027
-> P.R.China
-> 
-> Tel: +86-571-87932423
-> Mobile: (0)13516813753
-> Email: jshen@cad.zju.edu.cn
-> 
-> *************************************************************
-> *********
-> * The SunShine of life is made up of very little beams which 
-> is      *
-> *  bright all the time                                       
->         *
-> *************************************************************
-> *********
-> _______________________________________________
-> Irtf-rr mailing list
-> Irtf-rr@puck.nether.net
-> http://puck.nether.net/mailman/listinfo/irtf-rr
-> 

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Wed Aug 14 12:15:37 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15293
	for <routing-discussion-archive@odin.ietf.org>; Wed, 14 Aug 2002 12:15:36 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA09344;
	Wed, 14 Aug 2002 12:06:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA01179
	for <routing-discussion@optimus.ietf.org>; Wed, 14 Aug 2002 10:03:32 -0400 (EDT)
Received: from mail.cad.zju.edu.cn (cad.zju.edu.cn [210.32.131.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA09499
	for <routing-discussion@ietf.org>; Wed, 14 Aug 2002 10:02:10 -0400 (EDT)
Received: (qmail 12116 invoked from network); 14 Aug 2002 14:08:36 -0000
Received: from unknown (HELO cad.zju.edu.cn) (210.32.131.97)
  by 210.32.131.2 with SMTP; 14 Aug 2002 14:08:36 -0000
Message-ID: <3D5A6325.3C9DB86C@cad.zju.edu.cn>
Date: Wed, 14 Aug 2002 22:03:17 +0800
From: shen jing <jshen@cad.zju.edu.cn>
Reply-To: jshen@cad.zju.edu.cn
Organization: State Key Lab of CAD&CG
X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
CC: irtf-rr@puck.nether.net,
        "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: Re: AW: AW: Differentiated Routing, not only plain rambo-SPF
References: <EF8E39AA846CD411BB9C00508B951F510514B9A2@MCHH267E>
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Hummel,

the crankback could be assumed, but the difficulty exists with when it
is triggered.

No matter how the two trees are estabilished, the network traffic is
shown to be 
self-similar, and with the increase of bandwidth*delay burst traffic
occurs frequently.

If a router react to transient overload, there may be a huge burden on
dealing with such 
operations. So, I think this mechanism may be adpoted for broken links
but not for congestion.




> 
> Let's assume there are two Smallest Size Tree road systems X1 and X2. X2 detours/avoids the kernel links of X1.
> For some source/destination node pair the total pathes may be different. Or only the section in the middle is different.
> Or only a section close to the source (or close to the dest.) is different. Whatever applies:
> >From the point of congestion on road system X1 the packet my crankback (hereby source and dest. address are swapped)
> to that first node which is also part of X2.
> There  source and dest. address are swapped again,  DSCP-X1 is replaced by DSCP-X2 and the packet is  moved forward
> via X2.
> 
> Heinrich
> 
> -----Ursprščngliche Nachricht-----
> Von: shen jing [mailto:jshen@cad.zju.edu.cn]
> Gesendet: Mittwoch, 14. August 2002 14:21
> An: irtf-rr@puck.nether.net
> Cc: 'Hummel Heinrich'; 'routing-discussion@ietf.org'
> Betreff: Re: AW: Differentiated Routing, not only plain rambo-SPF
> 
> The discussion you mentioned is that of congestion removement by e2e
> mechanism  or by routing. Professor Crowcroft proposed a method
> named ECN++ which trigger a new path that acts when ECN bit is set
> in packet header.
> 
> >
> > Heinrich,
> >
> > -> yes,it is similar;
> > -> but here it is about state-less IP forwarding, i.e. about
> > -> forwarding the individual IP packets, without any
> > -> RSVP path and without any MPLS path.
> >
> >   Oh! Ok...you would like to do Crankback in
> >   connection less IP environments?!?
> >
> >   In such a case, you might find below paper interesting:
> > http://www.ecse.rpi.edu/Homepages/shivkuma/research/papers/te-latest.pdf
> >
> >   There was some discussion in E2E list regarding
> >   pros & cons of this approach. I couldn't find the URL
> >   but I vaguely remember that the subject of the discussion
> >   is "EC++N" or something like that...
> >
> > --

-- 
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423
Mobile: (0)13516813753
Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Wed Aug 14 12:15:37 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15298
	for <routing-discussion-archive@odin.ietf.org>; Wed, 14 Aug 2002 12:15:37 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA09845
	for routing-discussion-archive@odin.ietf.org; Wed, 14 Aug 2002 12:16:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA09344;
	Wed, 14 Aug 2002 12:06:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA01179
	for <routing-discussion@optimus.ietf.org>; Wed, 14 Aug 2002 10:03:32 -0400 (EDT)
Received: from mail.cad.zju.edu.cn (cad.zju.edu.cn [210.32.131.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA09499
	for <routing-discussion@ietf.org>; Wed, 14 Aug 2002 10:02:10 -0400 (EDT)
Received: (qmail 12116 invoked from network); 14 Aug 2002 14:08:36 -0000
Received: from unknown (HELO cad.zju.edu.cn) (210.32.131.97)
  by 210.32.131.2 with SMTP; 14 Aug 2002 14:08:36 -0000
Message-ID: <3D5A6325.3C9DB86C@cad.zju.edu.cn>
Date: Wed, 14 Aug 2002 22:03:17 +0800
From: shen jing <jshen@cad.zju.edu.cn>
Reply-To: jshen@cad.zju.edu.cn
Organization: State Key Lab of CAD&CG
X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
CC: irtf-rr@puck.nether.net,
        "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: Re: AW: AW: Differentiated Routing, not only plain rambo-SPF
References: <EF8E39AA846CD411BB9C00508B951F510514B9A2@MCHH267E>
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 8bit

Hummel,

the crankback could be assumed, but the difficulty exists with when it
is triggered.

No matter how the two trees are estabilished, the network traffic is
shown to be 
self-similar, and with the increase of bandwidth*delay burst traffic
occurs frequently.

If a router react to transient overload, there may be a huge burden on
dealing with such 
operations. So, I think this mechanism may be adpoted for broken links
but not for congestion.




> 
> Let's assume there are two Smallest Size Tree road systems X1 and X2. X2 detours/avoids the kernel links of X1.
> For some source/destination node pair the total pathes may be different. Or only the section in the middle is different.
> Or only a section close to the source (or close to the dest.) is different. Whatever applies:
> >From the point of congestion on road system X1 the packet my crankback (hereby source and dest. address are swapped)
> to that first node which is also part of X2.
> There  source and dest. address are swapped again,  DSCP-X1 is replaced by DSCP-X2 and the packet is  moved forward
> via X2.
> 
> Heinrich
> 
> -----Ursprščngliche Nachricht-----
> Von: shen jing [mailto:jshen@cad.zju.edu.cn]
> Gesendet: Mittwoch, 14. August 2002 14:21
> An: irtf-rr@puck.nether.net
> Cc: 'Hummel Heinrich'; 'routing-discussion@ietf.org'
> Betreff: Re: AW: Differentiated Routing, not only plain rambo-SPF
> 
> The discussion you mentioned is that of congestion removement by e2e
> mechanism  or by routing. Professor Crowcroft proposed a method
> named ECN++ which trigger a new path that acts when ECN bit is set
> in packet header.
> 
> >
> > Heinrich,
> >
> > -> yes,it is similar;
> > -> but here it is about state-less IP forwarding, i.e. about
> > -> forwarding the individual IP packets, without any
> > -> RSVP path and without any MPLS path.
> >
> >   Oh! Ok...you would like to do Crankback in
> >   connection less IP environments?!?
> >
> >   In such a case, you might find below paper interesting:
> > http://www.ecse.rpi.edu/Homepages/shivkuma/research/papers/te-latest.pdf
> >
> >   There was some discussion in E2E list regarding
> >   pros & cons of this approach. I couldn't find the URL
> >   but I vaguely remember that the subject of the discussion
> >   is "EC++N" or something like that...
> >
> > --

-- 
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423
Mobile: (0)13516813753
Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Wed Aug 14 12:19:02 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15432
	for <routing-discussion-archive@odin.ietf.org>; Wed, 14 Aug 2002 12:19:02 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA09377;
	Wed, 14 Aug 2002 12:06:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA25059
	for <routing-discussion@optimus.ietf.org>; Wed, 14 Aug 2002 08:20:57 -0400 (EDT)
Received: from mail.cad.zju.edu.cn (cad.zju.edu.cn [210.32.131.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA06340
	for <routing-discussion@ietf.org>; Wed, 14 Aug 2002 08:19:34 -0400 (EDT)
Received: (qmail 10409 invoked from network); 14 Aug 2002 12:25:54 -0000
Received: from unknown (HELO cad.zju.edu.cn) (210.32.131.97)
  by 210.32.131.2 with SMTP; 14 Aug 2002 12:25:54 -0000
Message-ID: <3D5A4B13.4385ABBE@cad.zju.edu.cn>
Date: Wed, 14 Aug 2002 20:20:35 +0800
From: shen jing <jshen@cad.zju.edu.cn>
Reply-To: jshen@cad.zju.edu.cn
Organization: State Key Lab of CAD&CG
X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: irtf-rr@puck.nether.net
CC: "'Hummel Heinrich'" <Heinrich.Hummel@icn.siemens.de>,
        "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: Re: AW: Differentiated Routing, not only plain rambo-SPF
References: <39469E08BD83D411A3D900204840EC557632E2@vie-msgusr-01.dc.fore.com>
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 7bit


The discussion you mentioned is that of congestion removement by e2e
mechanism  or by routing. Professor Crowcroft proposed a method
named ECN++ which trigger a new path that acts when ECN bit is set 
in packet header.



> 
> Heinrich,
> 
> -> yes,it is similar;
> -> but here it is about state-less IP forwarding, i.e. about
> -> forwarding the individual IP packets, without any
> -> RSVP path and without any MPLS path.
> 
>   Oh! Ok...you would like to do Crankback in
>   connection less IP environments?!?
> 
>   In such a case, you might find below paper interesting:
> http://www.ecse.rpi.edu/Homepages/shivkuma/research/papers/te-latest.pdf
> 
>   There was some discussion in E2E list regarding
>   pros & cons of this approach. I couldn't find the URL
>   but I vaguely remember that the subject of the discussion
>   is "EC++N" or something like that...
> 
> --
> Venkata
> 
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion

-- 
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423
Mobile: (0)13516813753
Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Wed Aug 14 12:19:03 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15442
	for <routing-discussion-archive@odin.ietf.org>; Wed, 14 Aug 2002 12:19:02 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA09950
	for routing-discussion-archive@odin.ietf.org; Wed, 14 Aug 2002 12:20:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA09377;
	Wed, 14 Aug 2002 12:06:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA25059
	for <routing-discussion@optimus.ietf.org>; Wed, 14 Aug 2002 08:20:57 -0400 (EDT)
Received: from mail.cad.zju.edu.cn (cad.zju.edu.cn [210.32.131.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA06340
	for <routing-discussion@ietf.org>; Wed, 14 Aug 2002 08:19:34 -0400 (EDT)
Received: (qmail 10409 invoked from network); 14 Aug 2002 12:25:54 -0000
Received: from unknown (HELO cad.zju.edu.cn) (210.32.131.97)
  by 210.32.131.2 with SMTP; 14 Aug 2002 12:25:54 -0000
Message-ID: <3D5A4B13.4385ABBE@cad.zju.edu.cn>
Date: Wed, 14 Aug 2002 20:20:35 +0800
From: shen jing <jshen@cad.zju.edu.cn>
Reply-To: jshen@cad.zju.edu.cn
Organization: State Key Lab of CAD&CG
X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: irtf-rr@puck.nether.net
CC: "'Hummel Heinrich'" <Heinrich.Hummel@icn.siemens.de>,
        "'routing-discussion@ietf.org'" <routing-discussion@ietf.org>
Subject: Re: AW: Differentiated Routing, not only plain rambo-SPF
References: <39469E08BD83D411A3D900204840EC557632E2@vie-msgusr-01.dc.fore.com>
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 7bit


The discussion you mentioned is that of congestion removement by e2e
mechanism  or by routing. Professor Crowcroft proposed a method
named ECN++ which trigger a new path that acts when ECN bit is set 
in packet header.



> 
> Heinrich,
> 
> -> yes,it is similar;
> -> but here it is about state-less IP forwarding, i.e. about
> -> forwarding the individual IP packets, without any
> -> RSVP path and without any MPLS path.
> 
>   Oh! Ok...you would like to do Crankback in
>   connection less IP environments?!?
> 
>   In such a case, you might find below paper interesting:
> http://www.ecse.rpi.edu/Homepages/shivkuma/research/papers/te-latest.pdf
> 
>   There was some discussion in E2E list regarding
>   pros & cons of this approach. I couldn't find the URL
>   but I vaguely remember that the subject of the discussion
>   is "EC++N" or something like that...
> 
> --
> Venkata
> 
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www1.ietf.org/mailman/listinfo/routing-discussion

-- 
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423
Mobile: (0)13516813753
Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Wed Aug 14 12:19:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15468
	for <routing-discussion-archive@odin.ietf.org>; Wed, 14 Aug 2002 12:19:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA09398;
	Wed, 14 Aug 2002 12:06:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA03743
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 08:20:40 -0400 (EDT)
Received: from mail.cad.zju.edu.cn (cad.zju.edu.cn [210.32.131.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA09324
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 08:19:18 -0400 (EDT)
Received: (qmail 26435 invoked from network); 13 Aug 2002 12:25:37 -0000
Received: from unknown (HELO cad.zju.edu.cn) (210.32.131.97)
  by 210.32.131.2 with SMTP; 13 Aug 2002 12:25:37 -0000
Message-ID: <3D58F982.8ED0E4D0@cad.zju.edu.cn>
Date: Tue, 13 Aug 2002 20:20:18 +0800
From: shen jing <jshen@cad.zju.edu.cn>
Reply-To: jshen@cad.zju.edu.cn
Organization: State Key Lab of CAD&CG
X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
CC: irtf-rr@puck.nether.net, routing-discussion@ietf.org
Subject: Re: AW: Differentiated Routing, not only plain rambo-SPF
References: <EF8E39AA846CD411BB9C00508B951F510514B992@MCHH267E>
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 7bit

Hummel,

> 
> Gold:  A smallest size tree of toll roads, highways, state roads, country roads.
> Silver:A smallest size tree of highways, state roads, country roads.
> Bronze:A smallest size tree of state roads, country roads, and highways only if no path otherwise.
> 
> QoS parameters (speed, packet loss rate, MTU size,..) may define the type of road.

Do you means to restrict DSCP to be 3bits? 


> 
> 1st and 2nd road system may be different at least  w.r.t. their kernel parts. (The kernel part be that
> center of the smallest size tree, which is used by at least m ingress/egress combinations).
> Either traffic starts out with a) proper DSCP-Y-1st, resp. DSCP-Y-2nd, or b) is  changed from DSCP-Y-1st to
> DSCP-Y-2nd at the rim of the kernel if some current traffic load information advises so. I prefer a) and if possible such
> that any microflow will entirely take one single route.

So, that means to use alternative path for overflowed traffic?  In fact,
someone has proposed similar

method. Perhaps you are interested in the following paper:

http://www.cs.virginia.edu/~rv3s/pubs/compnet_paper.pdf 

> 
>
> Stability:
> We may toss a dice at the ingress,i.e. determine a random number Y between 0.0 and 1.0. 

I think this determines when a second path is adopted for traffic
routing, in fact we do not
need to use a random number if MPLS is used. At this situation, I think
what we need is to 
monitor load on a LSP, if the load is more than 70% of the effective
bandwidth another LSP is
adpoted. If distributed routing is used ( as that of current IP
network), traffic dispersion 
have to be triggerred by heuristic method mentioned by you.

> 
> Extensibility:
> So far I have no solution, on how to determine a smallest size tree made out of OSPF-links and EBGP/IBGP-hops.

As I think, a routing system built on time-varying network status will
do harm to both
stability and extensibility, because it could not be expected to all
routers converge to the same 
point within a short time period. 

Some others have been working on resource management in DiffServ
networks, the page located 
at:

http://standards.ericsson.net/rmd/

In deed, I'm very interested in this idea but I think it need more
clarification.

Hope to hear from others.





-- 
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Wed Aug 14 12:19:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15474
	for <routing-discussion-archive@odin.ietf.org>; Wed, 14 Aug 2002 12:19:28 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA09964
	for routing-discussion-archive@odin.ietf.org; Wed, 14 Aug 2002 12:20:48 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA09398;
	Wed, 14 Aug 2002 12:06:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA03743
	for <routing-discussion@optimus.ietf.org>; Tue, 13 Aug 2002 08:20:40 -0400 (EDT)
Received: from mail.cad.zju.edu.cn (cad.zju.edu.cn [210.32.131.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA09324
	for <routing-discussion@ietf.org>; Tue, 13 Aug 2002 08:19:18 -0400 (EDT)
Received: (qmail 26435 invoked from network); 13 Aug 2002 12:25:37 -0000
Received: from unknown (HELO cad.zju.edu.cn) (210.32.131.97)
  by 210.32.131.2 with SMTP; 13 Aug 2002 12:25:37 -0000
Message-ID: <3D58F982.8ED0E4D0@cad.zju.edu.cn>
Date: Tue, 13 Aug 2002 20:20:18 +0800
From: shen jing <jshen@cad.zju.edu.cn>
Reply-To: jshen@cad.zju.edu.cn
Organization: State Key Lab of CAD&CG
X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Hummel Heinrich <Heinrich.Hummel@icn.siemens.de>
CC: irtf-rr@puck.nether.net, routing-discussion@ietf.org
Subject: Re: AW: Differentiated Routing, not only plain rambo-SPF
References: <EF8E39AA846CD411BB9C00508B951F510514B992@MCHH267E>
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 7bit

Hummel,

> 
> Gold:  A smallest size tree of toll roads, highways, state roads, country roads.
> Silver:A smallest size tree of highways, state roads, country roads.
> Bronze:A smallest size tree of state roads, country roads, and highways only if no path otherwise.
> 
> QoS parameters (speed, packet loss rate, MTU size,..) may define the type of road.

Do you means to restrict DSCP to be 3bits? 


> 
> 1st and 2nd road system may be different at least  w.r.t. their kernel parts. (The kernel part be that
> center of the smallest size tree, which is used by at least m ingress/egress combinations).
> Either traffic starts out with a) proper DSCP-Y-1st, resp. DSCP-Y-2nd, or b) is  changed from DSCP-Y-1st to
> DSCP-Y-2nd at the rim of the kernel if some current traffic load information advises so. I prefer a) and if possible such
> that any microflow will entirely take one single route.

So, that means to use alternative path for overflowed traffic?  In fact,
someone has proposed similar

method. Perhaps you are interested in the following paper:

http://www.cs.virginia.edu/~rv3s/pubs/compnet_paper.pdf 

> 
>
> Stability:
> We may toss a dice at the ingress,i.e. determine a random number Y between 0.0 and 1.0. 

I think this determines when a second path is adopted for traffic
routing, in fact we do not
need to use a random number if MPLS is used. At this situation, I think
what we need is to 
monitor load on a LSP, if the load is more than 70% of the effective
bandwidth another LSP is
adpoted. If distributed routing is used ( as that of current IP
network), traffic dispersion 
have to be triggerred by heuristic method mentioned by you.

> 
> Extensibility:
> So far I have no solution, on how to determine a smallest size tree made out of OSPF-links and EBGP/IBGP-hops.

As I think, a routing system built on time-varying network status will
do harm to both
stability and extensibility, because it could not be expected to all
routers converge to the same 
point within a short time period. 

Some others have been working on resource management in DiffServ
networks, the page located 
at:

http://standards.ericsson.net/rmd/

In deed, I'm very interested in this idea but I think it need more
clarification.

Hope to hear from others.





-- 
Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, Z.J. 310027
P.R.China

Tel: +86-571-87932423

Email: jshen@cad.zju.edu.cn

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



From routing-discussion-admin@ietf.org  Thu Aug 15 18:10:12 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17938
	for <routing-discussion-archive@odin.ietf.org>; Thu, 15 Aug 2002 18:10:12 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA11863;
	Thu, 15 Aug 2002 18:01:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA11837
	for <routing-discussion@optimus.ietf.org>; Thu, 15 Aug 2002 18:01:49 -0400 (EDT)
Received: from psg.com (smmsp@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17681
	for <routing-discussion@ietf.org>; Thu, 15 Aug 2002 18:00:29 -0400 (EDT)
Received: from psg.com ([147.28.0.62] helo=127.0.0.1)
	by psg.com with esmtp (Exim 3.36 #1)
	id 17fSgf-00002z-00
	for routing-discussion@ietf.org; Thu, 15 Aug 2002 15:01:49 -0700
Date: Thu, 15 Aug 2002 15:00:23 -0700
From: Alex Zinin <zinin@psg.com>
X-Mailer: The Bat! (v1.51) Personal
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <7251331901.20020815150023@psg.com>
To: routing-discussion@ietf.org
Subject: Fwd: Re: [VRRP] VRRP Working Group Minutes
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 7bit

FYI.

-- 
Alex

This is a forwarded message
From: Alex Zinin <zinin@psg.com>
To: vrrp@ietf.org
Cc: 
Date: Thursday, August 15, 2002, 2:30:16 PM
Subject: [VRRP] VRRP Working Group Minutes

===8<==============Original message text===============
Tuesday, August 13, 2002, 2:22:28 PM, Bob Hinden wrote:
...
> Bob announced that he is planning to step down as chair for the WG. They
> are now looking for somebody to step into the role.  Contact ADs or Bob - 
> who will continue in the role until replaced.

Folks interested in running for the WG chair position, please
drop myself and Bill a message--we're starting the interview
process.

Thanks.
Alex



_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp

===8<===========End of original message text===========



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion


From daemon@optimus.ietf.org  Thu Aug 15 18:10:13 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17946
	for <routing-discussion-archive@odin.ietf.org>; Thu, 15 Aug 2002 18:10:13 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA12427
	for routing-discussion-archive@odin.ietf.org; Thu, 15 Aug 2002 18:11:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA11863;
	Thu, 15 Aug 2002 18:01:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA11837
	for <routing-discussion@optimus.ietf.org>; Thu, 15 Aug 2002 18:01:49 -0400 (EDT)
Received: from psg.com (smmsp@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17681
	for <routing-discussion@ietf.org>; Thu, 15 Aug 2002 18:00:29 -0400 (EDT)
Received: from psg.com ([147.28.0.62] helo=127.0.0.1)
	by psg.com with esmtp (Exim 3.36 #1)
	id 17fSgf-00002z-00
	for routing-discussion@ietf.org; Thu, 15 Aug 2002 15:01:49 -0700
Date: Thu, 15 Aug 2002 15:00:23 -0700
From: Alex Zinin <zinin@psg.com>
X-Mailer: The Bat! (v1.51) Personal
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <7251331901.20020815150023@psg.com>
To: routing-discussion@ietf.org
Subject: Fwd: Re: [VRRP] VRRP Working Group Minutes
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: routing-discussion-admin@ietf.org
Errors-To: routing-discussion-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
X-BeenThere: routing-discussion@ietf.org
Content-Transfer-Encoding: 7bit

FYI.

-- 
Alex

This is a forwarded message
From: Alex Zinin <zinin@psg.com>
To: vrrp@ietf.org
Cc: 
Date: Thursday, August 15, 2002, 2:30:16 PM
Subject: [VRRP] VRRP Working Group Minutes

===8<==============Original message text===============
Tuesday, August 13, 2002, 2:22:28 PM, Bob Hinden wrote:
...
> Bob announced that he is planning to step down as chair for the WG. They
> are now looking for somebody to step into the role.  Contact ADs or Bob - 
> who will continue in the role until replaced.

Folks interested in running for the WG chair position, please
drop myself and Bill a message--we're starting the interview
process.

Thanks.
Alex



_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp

===8<===========End of original message text===========



_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www1.ietf.org/mailman/listinfo/routing-discussion



