ASN asdot notation #8475

Closed
opened 2025-12-29 20:37:11 +01:00 by adam · 7 comments
Owner

Originally created by @Serazio on GitHub (Aug 16, 2023).

NetBox version

v3.5.8

Feature type

New functionality

Proposed functionality

While adding a new ASN, it should be possible to add the ASN in asdot notation. If asdot notation is used, netbox should automatically calculate the correct asplain for that ASN.

The same should be possible for ASN ranges. Furthermore the ASDOT notation column should be possible to select in ASN ranges view

Use case

Better usability for users. No need for a asdot calculator

Database changes

No response

External dependencies

No response

Originally created by @Serazio on GitHub (Aug 16, 2023). ### NetBox version v3.5.8 ### Feature type New functionality ### Proposed functionality While adding a new ASN, it should be possible to add the ASN in asdot notation. If asdot notation is used, netbox should automatically calculate the correct asplain for that ASN. The same should be possible for ASN ranges. Furthermore the ASDOT notation column should be possible to select in ASN ranges view ### Use case Better usability for users. No need for a asdot calculator ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 20:37:11 +01:00
adam closed this issue 2025-12-29 20:37:11 +01:00
Author
Owner

@jsenecal commented on GitHub (Aug 17, 2023):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

I also had to lookup what ASDOT notation was and I'm working for a service provider so this is definitely not common knowledge or widely used as a standard.

@jsenecal commented on GitHub (Aug 17, 2023): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. **It must also include a detailed use case justifying its implementation.** If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed. I also had to lookup what ASDOT notation was and I'm working for a service provider so this is definitely not common knowledge or widely used as a standard.
Author
Owner

@ITJamie commented on GitHub (Aug 21, 2023):

One of my network engineers has requested the ability to display ASN's in ASDOT.
From our POV we would like the ASDOT number displayed on API views and ASN object views in netbox as a read only value.

Here is an example python library that can convert ASN numbers to ASDOT syntax https://github.com/tbaschak/asdot-asplain

I however don't see the value of this request of being able to ADD new asns using ASDOT notation...

@ITJamie commented on GitHub (Aug 21, 2023): One of my network engineers has requested the ability to display ASN's in ASDOT. From our POV we would like the ASDOT number displayed on API views and ASN object views in netbox as a read only value. Here is an example python library that can convert ASN numbers to ASDOT syntax https://github.com/tbaschak/asdot-asplain I however don't see the value of this request of being able to ADD new asns using ASDOT notation...
Author
Owner

@kkthxbye-code commented on GitHub (Aug 21, 2023):

From our POV we would like the ASDOT number displayed on API views

@ITJamie - What would the use be in the API? It's easily converted in whatever code is calling the API.

and ASN object views in netbox as a read only value.

Isn't this already the case or am I misunderstanding what you mean?

image

Here is an example python library that can convert ASN numbers to ASDOT syntax https://github.com/tbaschak/asdot-asplain

That code in that repo is pretty terrible. It's trivial to go asplain to asdot:

>>> asplain = 3294067295
>>> asdot = f"{asplain >> 0x10}.{asplain & 0xffff}"
>>> asdot
'50263.31327'
@kkthxbye-code commented on GitHub (Aug 21, 2023): > From our POV we would like the ASDOT number displayed on API views @ITJamie - What would the use be in the API? It's easily converted in whatever code is calling the API. > and ASN object views in netbox as a read only value. Isn't this already the case or am I misunderstanding what you mean? ![image](https://github.com/netbox-community/netbox/assets/400797/00d2d165-9c9a-4f02-869e-3a1df662897b) > Here is an example python library that can convert ASN numbers to ASDOT syntax https://github.com/tbaschak/asdot-asplain That code in that repo is pretty terrible. It's trivial to go asplain to asdot: ```python >>> asplain = 3294067295 >>> asdot = f"{asplain >> 0x10}.{asplain & 0xffff}" >>> asdot '50263.31327' ```
Author
Owner

@jeremystretch commented on GitHub (Aug 22, 2023):

Furthermore the ASDOT notation column should be possible to select in ASN ranges view

This is a separate feature request. Please open a separate issue for it.

@jeremystretch commented on GitHub (Aug 22, 2023): > Furthermore the ASDOT notation column should be possible to select in ASN ranges view This is a separate feature request. Please open a separate issue for it.
Author
Owner

@jeremystretch commented on GitHub (Sep 20, 2023):

I understand the use case here: the flexibility to input a 32-bit AS number in either ASPLAIN or ASDOT format (e.g. as 65536 or 1.0). This would require extending the relevant form field to accept either format.

I'm marking this as needs owner with the understanding that this is the scope of the FR.

(Additionally, I'll note that there is an optional ASDOT column available on the ASN lists.)

@jeremystretch commented on GitHub (Sep 20, 2023): I understand the use case here: the flexibility to input a 32-bit AS number in either ASPLAIN or [ASDOT format](https://datatracker.ietf.org/doc/html/rfc5396) (e.g. as `65536` or `1.0`). This would require extending the relevant form field to accept either format. I'm marking this as `needs owner` with the understanding that this is the scope of the FR. (Additionally, I'll note that there is an optional ASDOT column available on the ASN lists.)
Author
Owner

@github-actions[bot] commented on GitHub (Dec 20, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Dec 20, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Jan 19, 2024):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jan 19, 2024): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8475