Re: [Isis-wg] draft-ietf-isis-auto-conf

["Les Ginsberg (ginsberg)" <[e-mail]>]

Alexander -

I am not sure why you did not send your comments to the WG list as well.  I have added the WG alias as this may be of interest to other folks in the WG.
Inline.

> -----Original Message-----
> From: Alexander Okonnikov [mailto:[e-mail]]
> Sent: Friday, March 24, 2017 5:09 AM
> To: [e-mail]
> Subject: draft-ietf-isis-auto-conf
> 
> Hi authors,
> 
> 
> Per procedure of protocol operation in start-up mode, router generates its
> LSP#0. Isn't it better to modify procedure such that start-up router will
> suppress generation of its LSP#0 (and omitting its LSP entry in its CSNP), until
> it will obtain full database, and will check presence of duplicate system ID. If
> duplicate system ID is present in the network (LSP with the same system ID,
> but S-bit clear), start-up router will perform change of its system ID. If its
> system ID is unique, it is advertising its LSP#0 into network. With current
> procedure there is possibility for traffic disruption, when LSP of existing
> router with the same system ID will being replaced by LSP of start-up router
> (the same case when two routers with the same system ID in regular IS-IS
> are present in the network).
> 
[Les:] As we have defined the S-bit(Startup) in the Fingerprint TLV and the tie-breaking rules in case of duplicate system-ids  favor the router NOT in startup mode we accomplish the same thing - and also handle the possible case when two routers who come up at roughly the same time have duplicate system-ids - which would have to be handled even we followed your suggestion as eventually the new routers have to send their first LSP.

> Also, the draft doesn't specify when pseudonode LSP should be generated
> (in case of start-up router is on broadcast link and is chosen to be DIS). Per
> current procedure, start-up router is not generating pseudonode LSP. But, in
> case it is DIS from point of view of other routers on the same LAN, previous
> DIS will purge its pseudonode LSP.
> Each other router will calculate start-up router as a new DIS. It also could be
> cause of disruption (absence of pseudonode LSP from new DIS).
> Hence, proposal is to start-up router to set its LAN priority to lowest value
> (0). The draft also could specify that for routers operating in non-start-up
> mode, LAN priority should not be less than 1. Once start-up router has
> finished its start-up mode, it could increase its LAN priority to
> configured/default value.
> 
[Les:] As per the base protocol (ISO10589) a router cannot declare itself DIS until it has at least one neighbor established on the LAN. As duplicate system-id detection via hellos prevents adjacencies from coming up in the event of a duplicate system-id, normal procedures regarding election of DIS can be safely used. Also the base protocol rules about new DIS pseudo-node LSP generation and purging of the pseudo-node LSPs generated by the old DIS can be safely used. 

Clever implementers find ways to avoid the disruption associated w DIS change when a new router comes up by using "make-before-break" logic.

   Les

> 
> Thank you.
> 
> 
> BR,
> 
> Alexander