; Shraddha
Hegde ; Ketan Talaulikar (ketant)
; Joel M. Halpern
Subject: Re: [spring] Spring protection - determining applicability
Cheng and all,
A few short comments.
1. I support the idea to mark some IGP Prefix SIDs as "not bypassable"
2. I think that, while such marking
f.org; Robert Raszuk; ext-andrew.als...@liquidtelecom.com;
Shraddha Hegde; Ketan Talaulikar (ketant); Joel M. Halpern
Subject: Re: [spring] Spring protection - determining applicability
Hi Sasha and Martin,
Many thanks for your input. I fully agree with your point of we need to
consider to advertise the ability
; ext-andrew.als...@liquidtelecom.com <
> andrew.als...@liquidtelecom.com>; Shraddha Hegde ;
> Ketan Talaulikar (ketant) ; Joel M.
> Halpern
> *Subject:* Re: [spring] Spring protection - determining applicability
>
>
>
> A few thoughts from my (operator's) PoV:
>
ix SIDs. If there was a desire for it, an
>> IGP extension would be required (there is none in progress AFAIK). Note
>> that this results in doubling the prefix SID scale (global labels) in the
>> network. So I would not go about this trivially.
>>
>>
>>
>>
>>
&g
t;
> Thanks,
>
> Ketan
>
>
>
> *From:* Robert Raszuk
> *Sent:* 14 August 2020 23:04
> *To:* Ketan Talaulikar (ketant)
> *Cc:* Alexander Vainshtein ; Joel M.
> Halpern ; Shraddha Hegde ;
> ext-andrew.als...@liquidtelecom.com ;
> spring@ietf.org
> *Subject:* Re: [sp
nt)
> *Cc:* Alexander Vainshtein ; Joel M.
> Halpern ; Shraddha Hegde ;
> ext-andrew.als...@liquidtelecom.com ;
> spring@ietf.org
> *Subject:* Re: [spring] Spring protection - determining applicability
>
>
>
> Hi Ketan,
>
>
>
> While I completely agree with you
t; *Sent:* 14 August 2020 20:24
> *To:* Ketan Talaulikar (ketant) ; Joel M. Halpern <
> j...@joelhalpern.com>; Shraddha Hegde ;
> ext-andrew.als...@liquidtelecom.com ;
> Robert Raszuk
> *Cc:* spring@ietf.org
> *Subject:* Re: [spring] Spring protection - determining applicability
>
>
w.als...@liquidtelecom.com ; Robert
Raszuk
Cc: spring@ietf.org
Subject: Re: [spring] Spring protection - determining applicability
Ketan, and all,
I have stated that, IMHO and FWIW, both Adj-SIDs and Prefix SIDs that are
advertised with PHP can ONLY represent topological instructions in SR-MPLS -
be
, 2020, 16:23
*To:* Alexander Vainshtein; Joel M. Halpern; Shraddha Hegde;
ext-andrew.als...@liquidtelecom.com; Robert Raszuk
*Cc:* spring@ietf.org
*Subject:* RE: [spring] Spring protection - determining applicability
NOTICE
xander Vainshtein; Joel M. Halpern; Shraddha Hegde;
ext-andrew.als...@liquidtelecom.com; Robert Raszuk
Cc: spring@ietf.org
Subject: RE: [spring] Spring protection - determining applicability
NOTICE: This email was received from an EXTERNAL
ietf.org<mailto:spring@ietf.org>
Subject: Re: [spring] Spring protection - determining applicability
Hi All,
I would like to share a different perspective on this.
First, thanks to Joel for bringing up the discussion. Clearly we need a
well-defined applicability statement for determining appl
14, 2020, 15:00
To: Joel M. Halpern; Alexander Vainshtein; Shraddha Hegde;
ext-andrew.als...@liquidtelecom.com; Robert Raszuk
Cc: spring@ietf.org
Subject: Re: [spring] Spring protection - determining applicability
Hi All,
I would like to share a different perspective on this.
First, thanks t
liquidtelecom.com
; Robert Raszuk
Cc: spring@ietf.org; Joel M. Halpern
Subject: Re: [spring] Spring protection - determining applicability
There are, as far as I can tell, a number of ways to address this family of
related questions.
What struck me, and prompted the starting question, was that non
:* ext-andrew.als...@liquidtelecom.com
; Robert Raszuk
*Cc:* spring@ietf.org; Joel M. Halpern
*Subject:* Re: [spring] Spring protection - determining applicability
All,
This is a very interesting discussion and thanks to Joel for starting
this discussion. IMO, when there are strict requirements of av
/?include_text=1
Thanks
Zhibo
-Original Message-
From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Joel M. Halpern
Sent: Monday, August 3, 2020 7:51 AM
To: spring@ietf.org
Subject: [spring] Spring protection - determining applicability
(WG Chair hat Off, this is merely a note from
2-39266302
Cell: +972-549266302
Email: alexander.vainsht...@ecitele.com
From: spring On Behalf Of Shraddha Hegde
Sent: Tuesday, August 4, 2020 9:41 AM
To: ext-andrew.als...@liquidtelecom.com ;
Robert Raszuk
Cc: spring@ietf.org; Joel M. Halpern
Subject: Re: [spring] Spring protection - dete
Sent: Tuesday, August 4, 2020 12:14 PM
To: Joel M. Halpern ; Robert Raszuk
Cc: spring@ietf.org
Subject: Re: [spring] Spring protection - determining applicability
Hi Joel and All,
I think TE path should be coupled with end to end protection. It is not prudent
to allow node or link protection in
ng@ietf.org<mailto:spring@ietf.org>
Subject: Re: [spring] Spring protection - determining applicability
Is this a common use case ie. "but rather - which nodes / network segments it
can never touch or flow through."
If so perhaps its time to define notion of negative-SID ie. lis
fowarding
scenarios rather than TE or policy paths.
Best Regards,
Zhenqiang Li
li_zhenqi...@hotmail.com
From: Joel M. Halpern
Date: 2020-08-04 02:35
To: Robert Raszuk
CC: spring@ietf.org
Subject: Re: [spring] Spring protection - determining applicability
(Since the thread has gotten long enough
@ietf.org
Subject: Re: [spring] Spring protection - determining applicability
Hi Andrew,
thank you for your expedient response. I understand why operators are using
S-BFD to monitor the continuity of p2p SR-MPLS tunnel. But I'd note that S-BFD
does not support monitoring of multicast trees,
awbacks of the
> protection mechanisms we are forced to use at this point
>
>
>
> Andrew
>
>
>
>
>
> *From:* Greg Mirsky
> *Sent:* Tuesday, 4 August 2020 01:40
> *To:* Andrew Alston
> *Cc:* Joel M. Halpern ; Robert Raszuk <
> rob...@raszuk.net>
Raszuk
Sent: Tuesday, 4 August 2020 01:27
To: Andrew Alston
Cc: Joel M. Halpern ; spring@ietf.org
Subject: Re: [spring] Spring protection - determining applicability
Is this a common use case ie. "but rather – which nodes / network segments it
can never touch or flow through."
If so p
: Andrew Alston
Cc: Joel M. Halpern ; Robert Raszuk ;
spring@ietf.org
Subject: Re: [spring] Spring protection - determining applicability
Hi Andrew,
would such requirements support using e2e protection?
Regards,
Greg
On Mon, Aug 3, 2020 at 2:46 PM Andrew Alston
mailto:andrew.als
;
> > > The scenarios in which differentiation between “topological” and
> > > “service” instructions is broken are indeed problematic. E.g.,
> > consider
> > > the use case in which a Node SID in the ERO of a SR-TE path
> > identifies a
> > > node that a
>
>
> Andrew
>
>
>
>
>
> *From:* spring *On Behalf Of *Joel M. Halpern
> *Sent:* Monday, 3 August 2020 21:36
> *To:* Robert Raszuk
> *Cc:* spring@ietf.org
> *Subject:* Re: [spring] Spring protection - determining applicability
>
>
>
> (Since the thread h
+1
Thanks,
Jim Uttaro
From: spring On Behalf Of Andrew Alston
Sent: Monday, August 03, 2020 5:46 PM
To: Joel M. Halpern ; Robert Raszuk
Cc: spring@ietf.org
Subject: Re: [spring] Spring protection - determining applicability
So –
One of the use cases, in fact, some very major
combine
> topological
> > and service instructions thus breaking the differentiation
> between the two.
> >
> > I am not sure if usage of such “combined” SIDs could be prevented
> or at
> > least discouraged.
> >
> > If not, providing an ability to identify s
vainsht...@ecitele.com
<mailto:alexander.vainsht...@ecitele.com>
>
> -Original Message-
> From: spring mailto:spring-boun...@ietf.org>> On Behalf Of Mach Chen
> Sent: Monday, August 3, 2020 6:30 AM
> To: Joel M. Halpern mailto:j...@joel
t; and service instructions thus breaking the differentiation between the
> two.
> >
> > I am not sure if usage of such “combined” SIDs could be prevented or at
> > least discouraged.
> >
> > If not, providing an ability to identify such SIDs in the advertisement
>
6302
Cell: +972-549266302
Email: alexander.vainsht...@ecitele.com
-Original Message-
From: spring On Behalf Of Mach Chen
Sent: Monday, August 3, 2020 6:30 AM
To: Joel M. Halpern ; spring@ietf.org
Subject: Re: [spring] Spring protection - determining applicability
Hi Joel,
I think this is a go
n Behalf Of Mach Chen
Sent: Monday, August 3, 2020 6:30 AM
To: Joel M. Halpern ; spring@ietf.org
Subject: Re: [spring] Spring protection - determining applicability
Hi Joel,
I think this is a good point that may not be discussed in the past. And
I also don't think there is a "can be bypa
[mailto:spring-boun...@ietf.org] On Behalf Of Mach Chen
Sent: Monday, August 3, 2020 11:30 AM
To: Joel M. Halpern ; spring@ietf.org
Subject: Re: [spring] Spring protection - determining applicability
Hi Joel,
I think this is a good point that may not be discussed in the past. And I also
don't
tisement
mechanisms would be useful IMHO.
My 2c,
Sasha
Office: +972-39266302
Cell: +972-549266302
Email: alexander.vainsht...@ecitele.com
-Original Message-
From: spring On Behalf Of Mach Chen
Sent: Monday, August 3, 2020 6:30 AM
To: Joel M. Halpern ; spring@ietf.org
Subjec
AM
> To: spring@ietf.org
> Subject: [spring] Spring protection - determining applicability
>
> (WG Chair hat Off, this is merely a note from a slightly confused WG
> participant.)
>
> I have been reading the various repair drafts, and the various networks
> programming a
(WG Chair hat Off, this is merely a note from a slightly confused WG
participant.)
I have been reading the various repair drafts, and the various networks
programming and service programming draft, and I am trying to figure out
one aspect of the combination.
How does a node that is doing som
35 matches
Mail list logo
