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
Finish RPSL parser #9
Milestone
Comments
mxsasha
added a commit
that referenced
this issue
May 10, 2018
mxsasha
added a commit
that referenced
this issue
May 10, 2018
mxsasha
added a commit
that referenced
this issue
May 11, 2018
mxsasha
added a commit
that referenced
this issue
May 11, 2018
@job is there a readable authoritative place in IRRD where we can see what the current attribute definitions are, so we can do a consistency check with our current ones? Here's the set we have now:
|
mxsasha
added a commit
that referenced
this issue
May 11, 2018
mxsasha
added a commit
that referenced
this issue
May 11, 2018
mxsasha
added a commit
that referenced
this issue
May 11, 2018
mxsasha
added a commit
that referenced
this issue
May 14, 2018
mxsasha
added a commit
that referenced
this issue
May 14, 2018
mxsasha
added a commit
that referenced
this issue
May 15, 2018
mxsasha
added a commit
that referenced
this issue
May 15, 2018
As RFC 2622 says: All the set name components of an hierarchical name has to be of the same type. For example, the following names are valid: AS1:AS-CUSTOMERS, AS1:RS-EXPORT:AS2, RS-EXCEPTIONS:RS-BOGUS
mxsasha
added a commit
that referenced
this issue
May 15, 2018
Parsing already worked for having one certif: line per line in the key, but was broken when using line continuation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
of an hierarchical name has to be of the same type. For example, the
following names are valid: AS1:AS-CUSTOMERS, AS1:RS-EXPORT:AS2, RS-
EXCEPTIONS:RS-BOGUS."
See also #27
The text was updated successfully, but these errors were encountered: