Les,
> You need to allow that not everything in the world is identified by an
IP/IPv6 address.
Thought we are talking about WAN networks here and not about the world :)
> assign a common anycast address on all nodes.
First not all nodes need to participate here. At most ABRs.
Then if you
Robert –
You need to allow that not everything in the world is identified by an IP/IPv6
address.
If you want an IP address shared by all nodes in an area there is already a
mean of doing that: assign a common anycast address on all nodes.
The value add (if there is any) of an Area SID is that
Hi Les,
Well I am talking about IP routable identifier which I can place on the
front of the packet and which can assure that the packet will arrive at
given area.
Then Area SID becomes analogy of Node SID :)
Thx
On Mon, Aug 3, 2020 at 7:40 PM Les Ginsberg (ginsberg)
wrote:
> Robert –
>
>
>
Hi Tony,
If I am not mistaken that additional overhead would only need to happen on
participating in this game ABRs. If so I think this is worthwhile.
> Well, that becomes an anycast tunnel endpoint
Endpoint ? Not midpoint ? Or better sort of ski lift transit point with
embedded direction in
Robert –
Both OSPF and IS-IS have area identifiers which are advertised.
Why would we need to invent another identifier for an area?
Les
From: Robert Raszuk
Sent: Monday, August 03, 2020 10:31 AM
To: Les Ginsberg (ginsberg)
Cc: bruno.decra...@orange.com; tony...@tony.li; lsr@ietf.org
Hi Robert,
> How about we first define an "Area Prefix" (IP address being a property of an
> area) then assign SID to it ?
That’s effectively what Bruno is proposing. It adds some additional
configuration and management overhead. Do you think it’s worthwhile?
> How odd it may sound I
Hi Acee,
> [Acee] I know you guys have all thought about this a lot more than myself.
> However, I’d envisioned this new Area SID as taking one to the closest entry
> to the abstracted area. The next SID in the stack would either take you to a
> destination inside the area or would use the
*Les,*
*> But currently the draft is defining a SID which is NOT associated with a
prefix.*
+
> *But if the proposal is to use a SID associated with a prefix then I see
no need to invent a new SID advertisement.*
How about we first define an "Area Prefix" (IP address being a property of
an area)
From: Lsr on behalf of "Les Ginsberg (ginsberg)"
Date: Monday, August 3, 2020 at 12:32 PM
To: Bruno Decraene , Tony Li
Cc: "lsr@ietf.org"
Subject: Re: [Lsr] New Version Notification for
draft-ietf-lsr-isis-area-proxy-02.txt
Bruno –
Inline.
From: bruno.decra...@orange.com
Sent: Monday,
Bruno –
Inline.
From: bruno.decra...@orange.com
Sent: Monday, August 03, 2020 8:52 AM
To: Les Ginsberg (ginsberg) ; tony...@tony.li
Cc: lsr@ietf.org
Subject: RE: [Lsr] New Version Notification for
draft-ietf-lsr-isis-area-proxy-02.txt
Les,
From: Les Ginsberg (ginsberg)
Les,
From: Les Ginsberg (ginsberg) [mailto:ginsb...@cisco.com]
Sent: Monday, August 3, 2020 5:22 PM
To: DECRAENE Bruno TGI/OLN ; tony...@tony.li
Cc: lsr@ietf.org
Subject: RE: [Lsr] New Version Notification for
draft-ietf-lsr-isis-area-proxy-02.txt
Bruno –
The concept of “Area SID” – at least
Bruno –
The concept of “Area SID” – at least to me – is “please forward to any node in
the Area advertising the Area SID”.
You, however, seem to be asking for either:
a)The node originating the Proxy LSP to advertise a Node SID for a loopback
address on that node
OR
b)The node originating
Hi Tony,
From: Tony Li [mailto:tony1ath...@gmail.com] On Behalf Of tony...@tony.li
Subject: Re: [Lsr] New Version Notification for
draft-ietf-lsr-isis-area-proxy-02.txt
Hi Bruno,
Thank you for the clarification.
[Bruno] You are very welcome. Thank you for listening.
I understand completely
13 matches
Mail list logo
