Skip to Content.
Sympa Menu

ntacpeering - Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S

Subject: NTAC Peering Working Group

List archive

Re: [2013-l3-architecture] FOR DISCUSSION: IP over AL2S


Chronological Thread 
  • 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




Archive powered by MHonArc 2.6.16.

Top of Page