Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Current serial number for some databases is not exposed #181

Closed
job opened this issue Jan 28, 2019 · 4 comments
Closed

Current serial number for some databases is not exposed #181

job opened this issue Jan 28, 2019 · 4 comments
Assignees
Milestone

Comments

@job
Copy link
Member

job commented Jan 28, 2019

Perhaps related to how some of the data sources are set up, but I'd expect to see 186 instead of the current output. Or phrased differently, how can we query for the current serial of any source?

hanna:~ job$ whois -h irrd01.ip.gin.ntt.net '!jRPKI'
A9
RPKI:N:-
C
@job
Copy link
Member Author

job commented Jan 28, 2019

Config for source RPKI is in #180

@mxsasha
Copy link
Collaborator

mxsasha commented Jan 28, 2019

This depends on what we consider the current serial. There's two different concepts of first/last serial in IRRd. First question, what do you actually do with the !j output?

@job
Copy link
Member Author

job commented Jan 28, 2019 via email

@mxsasha mxsasha self-assigned this Jan 29, 2019
@mxsasha mxsasha added this to the IRRD 4.0.0 milestone Jan 29, 2019
@mxsasha
Copy link
Collaborator

mxsasha commented Jan 30, 2019

This is fixed, but note that the serials provided by !j now do not correlate to which serials are available over NRTM (that was the original behaviour).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants