ntacpeering - Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S
Subject: NTAC Peering Working Group
List archive
- From: Michael H Lambert <>
- To: " Routing WG" <>
- Subject: Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S
- Date: Thu, 30 May 2013 10:59:00 -0400
- Authentication-results: sfpop-ironport04.merit.edu; dkim=neutral (message not signed) header.i=none
Steven,
On 30 May 2013, at 10:52, Steven Wallace wrote:
> I think you've hit on something that's going to require network engineers
> to re-think certain approaches to troubleshooting. IMO, the idea of an
> in-band probe to determine the path is simply not going to be a part of the
> SDN future (I could be wrong, but that's my prediction). The good news is
> that you no longer need it. What I mean is that the controller knows the
> entire path. I would be asking for an app where the engineer can easily
> say to AL2S "what's the path for this flow" and the app responds with the
> complete path as it exists in realtime.
If there are multiple controllers, do they all contain the entire state or
are they just "cooperative"? I'm trying not to think about the old mbone
traceroute that would do a hop-by-hop query.
Michael
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, (continued)
- Message not available
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Chris Robb, 05/24/2013
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Michael H Lambert, 05/24/2013
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Grover Browning, 05/29/2013
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, John Moore, 05/29/2013
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Grover Browning, 05/30/2013
- RE: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Paul Schopis, 05/30/2013
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Grover Browning, 05/30/2013
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Chris Spears, 05/30/2013
- RE: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Paul Schopis, 05/30/2013
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Steven Wallace, 05/30/2013
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Michael H Lambert, 05/30/2013
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Steven Wallace, 05/30/2013
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Ryan Harden, 05/30/2013
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Grover Browning, 05/30/2013
- RE: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Paul Schopis, 05/30/2013
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Steven Wallace, 05/30/2013
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Michael H Lambert, 05/30/2013
- RE: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Paul Schopis, 05/30/2013
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Michael H Lambert, 05/30/2013
- RE: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Paul Schopis, 05/31/2013
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Scott Brim, 05/31/2013
- RE: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Paul Schopis, 05/30/2013
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Grover Browning, 05/30/2013
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, John Moore, 05/29/2013
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Grover Browning, 05/29/2013
- Message not available
- Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S, Darrell Newcomb, 05/30/2013
Archive powered by MHonArc 2.6.16.