Hi, Robert: PUA covers both the intra-area and inter-area scenarios. For inter-area scenario, it covers the situation that the next-hop is reachable via one ABR but unreachable via another ABR. For such situation, BGP nexthop tracking, route withdraw or aggregate withdraw will not work.
> On Sep 7, 2020, at 11:43 PM, Shraddha Hegde > wrote: > > Peter, > > > Thanks for the conclusion on adding L-bit clarification in the > draft-ietf-lsr-flex-algo. > > Snip to open comments. > >> Note that earlier versions of this document did not mandate use of >> ASLA TLVs and hence may
Hi, the new version includes the following changes: 1. section 10 - removed the END.OP and END.OPT behaviors from the table. These SIDs have been removed from the ietf-6man-spring-srv6-oam, where they have been defined. Also removed reference to ietf-6man-spring-srv6-oam in section 10. 2.
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Link State Routing WG of the IETF. Title : IS-IS Extension to Support Segment Routing over IPv6 Dataplane Authors : Peter Psenak
Flex-algo application MUST be able to encode flex-algo link attributes using valid ASLA for flex-algo. Flex-algo application MUST be able to decode flex-algo link attributes using valid ASLA for flex-algo. A valid IS-IS ASLA may be encoded with L-bit SET or UNSET. The setting of L-bit is a
Hi Peter, > From: Peter Psenak [mailto:ppse...@cisco.com] > > Hi Bruno, > > please see inline: > > On 07/09/2020 17:31, bruno.decra...@orange.com wrote: > > Hi Peter, > > > >> From: Lsr [mailto:lsr-boun...@ietf.org] On Behalf Of Peter Psenak > >> Sent: Thursday, September 3, 2020 9:55 AM > >>
Hi Bruno, please see inline: On 07/09/2020 17:31, bruno.decra...@orange.com wrote: Hi Peter, From: Lsr [mailto:lsr-boun...@ietf.org] On Behalf Of Peter Psenak Sent: Thursday, September 3, 2020 9:55 AM Hi Shraddha, On 03/09/2020 05:39, Shraddha Hegde wrote: Peter, In order to make the
Hi Shraddha, when documents get adopted by the WG when they are still subject to changes. Based on WG feedback and implementation experience the drafts evolve to the point where they are considered mature and stable. Then they are ready to become RFCs and be used as the standard definition to