Peter,
Thank you for the explanation.
So you are saying that a node might not support RSVP or RSVP-TE, but can
advertise the TE related attributes for SR purpose. When the head node
receiving the advertisement also support RSVP-TE, it might use the information
to establish the RSVP path, wh
Linda,
On 09/06/2020 16:18, Linda Dunbar wrote:
Acee and Peter,
Thank you very much for the explanation.
My fundamental question is: What problem will be encountered when a node use
the TE information on links that RSVP-TE are not enabled?
The problem is on a node where RSVP is enabled, whe
Acee and Peter,
Thank you very much for the explanation.
My fundamental question is: What problem will be encountered when a node use
the TE information on links that RSVP-TE are not enabled?
I would think that the reason that RSVP-TE is enabled per interface is because
not every interface
Hi Linda,
One more point...
On 6/9/20, 4:52 AM, "Peter Psenak" wrote:
Linda,
On 09/06/2020 02:37, Linda Dunbar wrote:
> Peter,
>
> Thank you very much for adding the extra text to explain.
>
> But SR is supposed to be transparent to all intermediate nodes. Does y
Linda,
On 09/06/2020 02:37, Linda Dunbar wrote:
Peter,
Thank you very much for adding the extra text to explain.
But SR is supposed to be transparent to all intermediate nodes. Does your draft
require a node to be specifically configured for each link to support or not
support SR or RSVP-TE?
Peter,
Thank you very much for adding the extra text to explain.
But SR is supposed to be transparent to all intermediate nodes. Does your draft
require a node to be specifically configured for each link to support or not
support SR or RSVP-TE?
In addition, there is no new attributes describ
Hi Linda,
On 01/06/2020 17:30, Linda Dunbar wrote:
Peter,
You said:
/“//the problem with existing advertisement is that RSVP-TE will use it,
even if it was not intended to be used by RSVP-TE.//”/
What is the problem if RSVP-TE use the advertisement? What specific
attributes that RSVP-TE shoul
Peter,
You said:
“the problem with existing advertisement is that RSVP-TE will use it,
even if it was not intended to be used by RSVP-TE.”
What is the problem if RSVP-TE use the advertisement? What specific attributes
that RSVP-TE shouldn’t use?
Linda Dunbar
-Original Message
Linda,
On 29/05/2020 16:52, Linda Dunbar wrote:
Peter,
You said:
/we are not defining any new attributes./
/We are allowing an existing link attributes to be used by other
applications, including, but not limited to SRTE./
What prevent a node (or an application on the node) receiving the LSA
f
Peter,
You said:
we are not defining any new attributes.
We are allowing an existing link attributes to be used by other
applications, including, but not limited to SRTE.
What prevent a node (or an application on the node) receiving the LSA from
using the attributes carried by the
Hi Linda,
On 28/05/2020 19:02, Linda Dunbar via Datatracker wrote:
Reviewer: Linda Dunbar
Review result: Not Ready
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please treat t
Reviewer: Linda Dunbar
Review result: Not Ready
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please treat these comments just
like any other last call comments.
For more inform
12 matches
Mail list logo
