starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

In ASNs list show asplain and not asdot #5956

New Issue
Closed
opened 2025-12-29 19:34:54 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:34:54 +01:00
Owner
Copy Link

Originally created by @bluikko on GitHub (Jan 18, 2022).

Originally assigned to: @DanSheps on GitHub.

NetBox version

v3.1.6

Feature type

Change to existing functionality

Proposed functionality

3.1.6 changed the /ipam/asns/ list to show 4-byte ASN as asdot.

Most people wish asdot to die and the list should show asplain. The de-facto standard is to use asplain so that should be the primary notation used in /ipam/asns/.

If asdot needs to be displayed in the table at all it could be displayed in an optional additional column. Displaying both in /ipam/asn/x/ has no drawbacks but the list definitely needs to show asplain.

Use case

It is totally backwards to force everyone to convert from asdot when using the ASNs list for anything.

Database changes

None.

External dependencies

None.

Originally created by @bluikko on GitHub (Jan 18, 2022). Originally assigned to: @DanSheps on GitHub. ### NetBox version v3.1.6 ### Feature type Change to existing functionality ### Proposed functionality 3.1.6 changed the `/ipam/asns/` list to show 4-byte ASN as asdot. Most people wish asdot to die and the list should show asplain. The de-facto standard is to use asplain so that should be the primary notation used in `/ipam/asns/`. If asdot needs to be displayed in the table at all it could be displayed in an optional additional column. Displaying both in `/ipam/asn/x/` has no drawbacks but the list definitely needs to show asplain. ### Use case It is totally backwards to force everyone to convert from asdot when using the ASNs list for anything. ### Database changes None. ### External dependencies None.
adam added the status: acceptedtype: feature labels 2025-12-29 19:34:54 +01:00
adam closed this issue 2025-12-29 19:34:54 +01:00
adam commented 2025-12-29 19:34:55 +01:00
Author
Owner
Copy Link

@bluikko commented on GitHub (Jan 18, 2022):

Forgot to link #8293 was the issue that messed it.

@bluikko commented on GitHub (Jan 18, 2022): Forgot to link #8293 was the issue that messed it.
adam commented 2025-12-29 19:34:55 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 18, 2022):

If asdot needs to be displayed in the table at all it could be displayed in an optional additional column. Displaying both in /ipam/asn/x/ has no drawbacks but the list definitely needs to show asplain.

I think it makes sense to restore the default column to rendering ASNs in the plain format, and add a second column to show ASDOT format. (Typically a user would select only one or the other to be displayed.)

@jeremystretch commented on GitHub (Jan 18, 2022): > If asdot needs to be displayed in the table at all it could be displayed in an optional additional column. Displaying both in /ipam/asn/x/ has no drawbacks but the list definitely needs to show asplain. I think it makes sense to restore the default column to rendering ASNs in the plain format, and add a second column to show ASDOT format. (Typically a user would select only one or the other to be displayed.)
adam commented 2025-12-29 19:34:55 +01:00
Author
Owner
Copy Link

@nickhilliard commented on GitHub (Jan 18, 2022):

think it makes sense to restore the default column to rendering ASNs in the plain format, and add a second column to show ASDOT format

this is why we have SDOs - to create standards so that people and systems have a common language which is universally understood. The "steadfast opposition from network engineers" relates to the fact that the issue was settled nearly 15 years ago at the ietf, and it took a long time and a lot of work to iron out all the damage that multiple representation of ASN32s caused (including asdot, asdot+, colon-separated format, and at least one or two others). Re-opening the issue in modern, clean software stacks is comparable to creating an option for displaying currency in pounds, shillings and pence 😀

It's also worth noting that asdot does not work universally (e.g. RIRs, networking stacks, etc). I.e. plenty of places where if you attempt to use asdot, it's a syntax error and will be rejected.

I get the rationale for proposing asdot as an optional parameter for only the UI, namely that there are some corner cases where it can look slightly neater, but these are corner cases relating to early asn32 assignments. In all other respects, it's a dysfunctional representation system - which is why asplain ended up as the IETF outcome.

@nickhilliard commented on GitHub (Jan 18, 2022): > think it makes sense to restore the default column to rendering ASNs in the plain format, and add a second column to show ASDOT format this is why we have SDOs - to create standards so that people and systems have a common language which is universally understood. The "steadfast opposition from network engineers" relates to the fact that the issue was settled nearly 15 years ago at the ietf, and it took a long time and a lot of work to iron out all the damage that multiple representation of ASN32s caused (including asdot, asdot+, colon-separated format, and at least one or two others). Re-opening the issue in modern, clean software stacks is comparable to creating an option for displaying currency in pounds, shillings and pence 😀 It's also worth noting that asdot does not work universally (e.g. RIRs, networking stacks, etc). I.e. plenty of places where if you attempt to use asdot, it's a syntax error and will be rejected. I get the rationale for proposing asdot as an optional parameter for only the UI, namely that there are some corner cases where it can look slightly neater, but these are corner cases relating to early asn32 assignments. In all other respects, it's a dysfunctional representation system - which is why asplain ended up as the IETF outcome.
adam commented 2025-12-29 19:34:56 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jan 18, 2022):

This will be actioned as follows:

  1. Default display will revert to ASPlain
  2. New column will be added to represent ASDOT
@DanSheps commented on GitHub (Jan 18, 2022): This will be actioned as follows: 1. Default display will revert to ASPlain 2. New column will be added to represent ASDOT
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#5956
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?