nd faulty node happens to be doing what you hoped it
might and forwarding “works”. But there is no way for you to know what faulty
node is actually doing. So all this speculation about which choice might result
in the “best behavior” is like playing the lottery.
Why would we want to do
bout inconsistency in the
SRGB ranges advertised by _one_ node. I’m not sure to see your “startup
scenario” nor the “merge network scenario”. Could you please elaborate?
Thanks,
Bruno
From: Henderickx, Wim (Wim) [mailto:wim.henderi...@alcatel-lucent.com]
Sent: Wednesday, January 06, 2016
I also don’t see the big value add on this draft from what we have. Given it
introduces backward compatibility issues from existing
implementation/deployments I don’t see why we should proceed with this work in
the WG.
On 09/11/15 10:11, "spring on behalf of Les Ginsberg (ginsberg)"
Support and not aware of IPR related to this draft
On 22/07/15 15:17, "mpls on behalf of John G.Scudder" wrote:
>Dear WG,
>
>As we discussed at our meeting yesterday, working group adoption has been
>requested for
I tend to agree that proposal 2 is for migration, so would vote for option 2.
From: spring on behalf of Pushpasis Sarkar
Date: Friday 31 July 2015 07:37
To: Stephane Litkowski, spring@ietf.orgmailto:spring@ietf.org
Subject: Re: [spring] Modeling SRGB configuration for draft-ietf-spring-sr-yang
support
On 22/07/15 15:15, spring on behalf of John G.Scudder
spring-boun...@ietf.org on behalf of j...@juniper.net wrote:
Dear WG,
As we discussed at our meeting yesterday, working group adoption has been
requested for draft-filsfils-spring-segment-routing-central-epe. Please reply
to
In the OSPF/ISIS drafts on SR we scoped an algorithm field which could be used
for this purpose. So besides shortest path you could use a different algorithm.
From: Veerendranatha Reddy Vallem
veerendranath...@huawei.commailto:veerendranath...@huawei.com
Date: Sunday 28 September 2014 08:15
To:
let me know if my understanding is wrong .
Whether we can use multiple algorithms to represent same Node SID ?
Regards,
Veerendranath
From: Henderickx, Wim (Wim) [mailto:wim.henderi...@alcatel-lucent.com]
Sent: 28 September 2014 14:29
To: Veerendranatha Reddy Vallem; spring@ietf.orgmailto:spring
,
Veerendranath
From: Henderickx, Wim (Wim) [mailto:wim.henderi...@alcatel-lucent.com]
Sent: 28 September 2014 14:53
To: Veerendranatha Reddy Vallem; spring@ietf.orgmailto:spring@ietf.org
Subject: Re: [spring] Regarding SID/Lable distributed by IGPs
At this stage we defined the solution such that a given
I support adoption as a co-author. The document is complete to be adopted as WG
doc
From: Alvaro Retana (aretana) aret...@cisco.commailto:aret...@cisco.com
Date: Wednesday 24 September 2014 15:07
To: spring@ietf.orgmailto:spring@ietf.org
spring@ietf.orgmailto:spring@ietf.org
Cc:
I’m not aware of undisclosed IPR.
From: Alvaro Retana (aretana) aret...@cisco.commailto:aret...@cisco.com
Date: Wednesday 24 September 2014 15:07
To:
draft-filsfils-spring-segment-routing-m...@tools.ietf.orgmailto:draft-filsfils-spring-segment-routing-m...@tools.ietf.org
I support adopting the draft as co-author. The draft describes the architecture
well
From: Alvaro Retana (aretana) aret...@cisco.commailto:aret...@cisco.com
Date: Wednesday 24 September 2014 15:01
To: spring@ietf.orgmailto:spring@ietf.org
spring@ietf.orgmailto:spring@ietf.org
Cc:
12 matches
Mail list logo