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

Allow for RIR links or Github Markdown Styled Comments #215

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

Originally created by @ryanmerolle on GitHub (Jul 14, 2016).

It would make sense to RIR links to RFCs or RIR portals. Furthermore, comments could be used to further an RIR. You could just use comments instead of a new link field.

Originally created by @ryanmerolle on GitHub (Jul 14, 2016). It would make sense to RIR links to RFCs or RIR portals. Furthermore, comments could be used to further an RIR. You could just use comments instead of a new link field.
adam added the type: feature label 2025-12-29 16:19:33 +01:00
adam closed this issue 2025-12-29 16:19:33 +01:00
adam commented 2025-12-29 16:19:34 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 6, 2016):

Users should have at most a handful of RIRs defined. In 99% of cases, these will be actual RIRs and RFC 1918/6598. What additional information is worth storing about these objects?

@jeremystretch commented on GitHub (Aug 6, 2016): Users should have at most a handful of RIRs defined. In 99% of cases, these will be actual RIRs and RFC 1918/6598. What additional information is worth storing about these objects?
adam commented 2025-12-29 16:19:34 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Aug 7, 2016):

RIR object owners, contacts, admins, links, etc.

It makes sense for when cross connects or circuits from third parties that may leverage public ip space.

@ryanmerolle commented on GitHub (Aug 7, 2016): RIR object owners, contacts, admins, links, etc. It makes sense for when cross connects or circuits from third parties that may leverage public ip space.
adam commented 2025-12-29 16:19:35 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Dec 21, 2016):

I never saw your comment sorry! It only makes sense for firms that have a heavy crossconnect infrastructure where they are peering to multiple 3rd parties and need some additional metadata to validate prefixes are owned by said third party or associate prefixes to a tenant that they were not notified of.

@ryanmerolle commented on GitHub (Dec 21, 2016): I never saw your comment sorry! It only makes sense for firms that have a heavy crossconnect infrastructure where they are peering to multiple 3rd parties and need some additional metadata to validate prefixes are owned by said third party or associate prefixes to a tenant that they were not notified of.
adam commented 2025-12-29 16:19:35 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 21, 2016):

The RIR only represents the top-level owner of a prefix. So for example, ARIN or RIPE, not Widgets, Inc. NetBox supports tenancy now for tracking per-prefix ownership.

@jeremystretch commented on GitHub (Dec 21, 2016): The RIR only represents the top-level owner of a prefix. So for example, ARIN or RIPE, not Widgets, Inc. NetBox supports tenancy now for tracking per-prefix ownership.
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 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#215
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?