[Nsi-wg] Summarization of ERO discussion

[John MacAuley]

Guys,

Two questions:

1. Should we not include a an example where we model an originating and end "user" domain such that we need to start with a ".out" endpoint?

2. Do we want to make this technology safe, or just sold the bi-directional point-to-point solution at the moment?  Should we look at point to multi-point, etc.?

John.
 
On 2012-06-06, at 9:50 AM, Jerry Sobieski wrote:

> Hi Chin-
> 
> I think your slides blend two separate issues:   EROS; and Resolving loop path ambiguity of bidirectional STPs. 
> The path ambiguity is a artifact of loops in the inter-domain topology, not EROs.
> I have added two slides to your deck (see attached) that explain my point.   
> 
> We can discuss at the call
> Jerry
> 
> On 6/6/12 3:34 AM, Chin Guok wrote:
>> 
>> Hi all, 
>> 
>> Sorry for not getting this out sooner. 
>> 
>> There has been some discussion in a smaller group on how to resolve the ambiguity of EROs that use bi-directional STPs.  I've tried to capture the proposed solutions from the discussion and present them in the attached slide deck.  I apologize to the folks in the discussion if I misrepresented your proposals, please feel free to make corrections. 
>> 
>> Thanks. 
>> 
>> - Chin 
>> 
>> 
>> _______________________________________________
>> nsi-wg mailing list
>> nsi-wg at ogf.org
>> https://www.ogf.org/mailman/listinfo/nsi-wg
> <NSI-CS_EROs-v2 JS.pptx>_______________________________________________
> nsi-wg mailing list
> nsi-wg at ogf.org
> https://www.ogf.org/mailman/listinfo/nsi-wg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ogf.org/pipermail/nsi-wg/attachments/20120607/59aa2e7a/attachment.html>