(Taking this offlist – BCC the WG) Jaideep –
From a standards perspective I have provided you with what I know. To characterize this as something which can cause “serious routing issues” is an exaggeration. Given that the same system ID cannot be used on more than one router, at worst if you were in a deployment where an implementation did not accept a systemid of 0000, all you would need to do is modify the config of a single router. Assigning a systemid which has no relationship to the identity of the equipment/configuration of the node isn’t practical – I don’t think any thoughtful network manager would ever do such a thing. In my view you have lost perspective on this issue. Les From: Jaideep Choudhary <jaideepchoudhar...@gmail.com> Sent: Tuesday, June 14, 2022 9:57 PM To: Les Ginsberg (ginsberg) <ginsb...@cisco.com> Cc: Tony Li <tony...@tony.li>; supp...@ietf.org; lsr@ietf.org Subject: Re: [Lsr] [rt5.ietf.org #7080] System ID in ISIS Hi Les, Thanks for the quick response. I also could not find anywhere in the standard documentation stating that SYS ID of 0000.0000.0000 in IS-IS as invalid nor is there any restriction to how to calculate the SYS ID. Yes, there are recommendations to use MAC or IP address to calculate the SYS ID , so it remains unique in a routing domain, but couldn't be found anywhere in the standard documentation, if SYS ID must be derived from these addresses only. Having said that, in most of the cases, there would be very less probability of SYS ID of 0000.0000.0000 being configured in a production environment (as you also mentioned), but still, as there is no such explicit restriction (in the standards ISO10589 or RFC 3784) to not to use SYS ID: 0, so it can still be used as a valid SYS ID in the devices where it is allowed to configure the NET/SYSTEM ID manually. So in that case if some device the setting of SYS ID being 0 is considered as invalid or illegal, that can cause some serious routing issues in a single area multi vendor setup in ISIS. So, can we say that from Standards perspective SYS ID: 0000.0000.0000 is a legal setting ? Regards Jaideep On Tue, Jun 14, 2022 at 9:59 PM Les Ginsberg (ginsberg) <ginsb...@cisco.com<mailto:ginsb...@cisco.com>> wrote: Jaideep – I am not aware that any standard formally defines a system-id of 0000.0000.0000 as invalid. If there is, it would be an ISO specification – but a perusal of ISO 10589, ISO 8348, and ISO 7498 did not yield any such statement. (I would be happy to be corrected if someone has a reference.) From a practical standpoint, the lack of agreement on this by all implementations should not represent a significant concern. Schemes which automatically populate the system-id are typically based on the MAC address of some NIC on the box. Another common strategy is to use the zero filled IP address of some loopback. In either case all zeros will not be the result. In cases where the systemid is explicitly configured, it is easy enough NOT to use all 0’s. HTH Les From: Lsr <lsr-boun...@ietf.org<mailto:lsr-boun...@ietf.org>> On Behalf Of Jaideep Choudhary Sent: Tuesday, June 14, 2022 8:00 AM To: Tony Li <tony...@tony.li<mailto:tony...@tony.li>> Cc: supp...@ietf.org<mailto:supp...@ietf.org>; lsr@ietf.org<mailto:lsr@ietf.org> Subject: Re: [Lsr] [rt5.ietf.org<http://rt5.ietf.org> #7080] System ID in ISIS Hi Tony, I am not looking for technical support, but looking for IETF's perspective regarding the system id in IS-IS. As per the RFC 3784 there is no mention about any invalid value in a system id. Can you please confirm whether there is any such restriction to not to use a SYS ID of 0000.0000.0000 as per IETF standards ? If this mailing address is not appropriate for answering this query, can you suggest/redirect me to the correct team from IETF ? Thanks. Regards Jaideep On Tue, Jun 14, 2022, 20:19 Tony Li <tony...@tony.li<mailto:tony...@tony.li>> wrote: Hi, Neither of these mailing lists are appropriate for technical support. Please contact your vendors directly. Tony On Jun 14, 2022, at 12:12 AM, Jaideep Choudhary <jaideepchoudhar...@gmail.com<mailto:jaideepchoudhar...@gmail.com>> wrote: Hi Team, I would like to know, whether in IS-IS, a system id can be 0000.0000.0000 or it is an invalid value for sys I'd ? As per ISO 10589 a system id can be of 1 to 8 bytes long, but doesn't mention explicitly whether SYS ID of 0000.0000.0000 could be invalid. Also as per RFC 3784, it says System id is typically of 6 bytes, but doesn't talk about any invalid option. The reason I am asking this is that Juniper defines a SYS ID of 0000.0000.0000 as invalid. https://www.juniper.net/documentation/us/en/software/junos/is-is/topics/concept/is-is-routing-overview.html This can cause issues in inter-operability as some vendors like Cisco doesn't define a SYS-ID of 0000.0000.0000 as invalid. I would appreciate your response on this. Regards Jaideep Choudhary On Mon, 13 Jun, 2022, 11:08 pm Cindy Morgan via RT, <supp...@ietf.org<mailto:supp...@ietf.org>> wrote: Hi Jaideep, You have reached the IETF Secretariat, which is the administrative branch of the IETF, and as such, we are not qualified to answer your technical questions. You might have better luck if you try posing your question to the Link State Routing (LSR) Working Group (https://datatracker.ietf.org/wg/lsr/about/). LSR was formed by merging the ISIS and OSPF WGs and assigning all their existing adopted work at the time of chartering to LSR. Their mailing list address is lsr@ietf.org<mailto:lsr@ietf.org>. Best regards, Cindy On Mon Jun 13 10:10:54 2022, jaideepchoudhar...@gmail.com<mailto:jaideepchoudhar...@gmail.com> wrote: Hi Team, I would like to know, whether in IS-IS, a system id can be 0000.0000.0000 or it is an invalid value for sys I'd ? As per ISO 10589 a system id can be of 1 to 8 bytes long, but doesn't mention explicitly whether SYS ID of 0000.0000.0000 could be invalid. Also as per RFC 3784, it says System id is typically of 6 bytes, but doesn't talk about any invalid option. The reason I am asking this is that Juniper defines a SYS ID of 0000.0000.0000 as invalid. https://www.juniper.net/documentation/us/en/software/junos/is-is/topics/concept/is-is-routing-overview.html This can cause issues in inter-operability as some vendors like Cisco doesn't define a SYS-ID of 0000.0000.0000 as invalid. I would appreciate your response on this. Regards Jaideep Choudhary _______________________________________________ Lsr mailing list Lsr@ietf.org<mailto:Lsr@ietf.org> https://www.ietf.org/mailman/listinfo/lsr
_______________________________________________ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
