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.

Sign up for GitHub

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

Jump to bottom

Parsing issue: invalid unicode characters in mnt-by in RIPE #52

Closed
mxsasha opened this issue Jul 6, 2018 · 5 comments
Closed

Parsing issue: invalid unicode characters in mnt-by in RIPE #52

mxsasha opened this issue Jul 6, 2018 · 5 comments
Assignees
@job

Comments

@mxsasha
Copy link
Collaborator

mxsasha commented Jul 6, 2018 

route:          192.170.96.0/19
descr:          Hewlett-Packard Company
origin:         AS7430
mnt-by:           AS1889-MNT
mnt-routes:     COLT-UK
changed:        unread@ripe.net 20000101
created:        2009-05-28T14:19:14Z
last-modified:  2016-01-14T07:07:02Z
source:         RIPE
remarks:        ****************************
remarks:        * THIS OBJECT IS MODIFIED
remarks:        * Please note that all data that is generally regarded as personal
remarks:        * data has been removed from this object.
remarks:        * To view the original object, please query the RIPE Database at:
remarks:        * http://www.ripe.net/whois
remarks:        ****************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ERROR: Invalid name:   AS1889-MNT: contains invalid characters, does not start with a letter, or does not end in a letter/digit

=======================================

route:          176.52.224.0/20
descr:                     armorconnectic
origin:         AS49112
mnt-by:                 ARMORCONNECTIC-MNT
created:        2016-06-09T09:39:51Z
last-modified:  2016-06-09T09:39:51Z
source:         RIPE
remarks:        ****************************
remarks:        * THIS OBJECT IS MODIFIED
remarks:        * Please note that all data that is generally regarded as personal
remarks:        * data has been removed from this object.
remarks:        * To view the original object, please query the RIPE Database at:
remarks:        * http://www.ripe.net/whois
remarks:        ****************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ERROR: Invalid name:         ARMORCONNECTIC-MNT: contains invalid characters, does not start with a letter, or does not end in a letter/digit

=======================================

route:          185.147.232.0/22
descr:                     armorconnectic
origin:         AS49112
mnt-by:                 ARMORCONNECTIC-MNT
created:        2016-06-09T09:39:52Z
last-modified:  2016-06-09T09:39:52Z
source:         RIPE
remarks:        ****************************
remarks:        * THIS OBJECT IS MODIFIED
remarks:        * Please note that all data that is generally regarded as personal
remarks:        * data has been removed from this object.
remarks:        * To view the original object, please query the RIPE Database at:
remarks:        * http://www.ripe.net/whois
remarks:        ****************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ERROR: Invalid name:         ARMORCONNECTIC-MNT: contains invalid characters, does not start with a letter, or does not end in a letter/digit

=======================================

route:          185.147.228.0/22
descr:                     capaix-connectic
origin:         AS49540
mnt-by:                 CAPAIX-CONNECTIC-MNT
created:        2016-06-09T09:39:52Z
last-modified:  2016-06-09T09:39:52Z
source:         RIPE
remarks:        ****************************
remarks:        * THIS OBJECT IS MODIFIED
remarks:        * Please note that all data that is generally regarded as personal
remarks:        * data has been removed from this object.
remarks:        * To view the original object, please query the RIPE Database at:
remarks:        * http://www.ripe.net/whois
remarks:        ****************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ERROR: Invalid name:         CAPAIX-CONNECTIC-MNT: contains invalid characters, does not start with a letter, or does not end in a letter/digit

=======================================

route:          185.147.148.0/22
descr:                     memonet
origin:         AS49083
mnt-by:                FR-MEMONET-MNT
created:        2016-06-09T09:39:52Z
last-modified:  2016-06-09T09:39:52Z
source:         RIPE
remarks:        ****************************
remarks:        * THIS OBJECT IS MODIFIED
remarks:        * Please note that all data that is generally regarded as personal
remarks:        * data has been removed from this object.
remarks:        * To view the original object, please query the RIPE Database at:
remarks:        * http://www.ripe.net/whois
remarks:        ****************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ERROR: Invalid name:        FR-MEMONET-MNT: contains invalid characters, does not start with a letter, or does not end in a letter/digit

=======================================

mntner:         Neutrinet-MNT
admin-c:        DUMY-RIPE
upd-to:         unread@ripe.net
auth:           MD5-PW $1$SaltSalt$DummifiedMD5HashValue.   # Real value hidden for security
mnt-by:         Neutrinet-MNT
mnt-by:            Gitoyen-NCC
created:        2014-04-15T13:48:34Z
last-modified:  2017-04-02T19:51:55Z
source:         RIPE
remarks:        ****************************
remarks:        * THIS OBJECT IS MODIFIED
remarks:        * Please note that all data that is generally regarded as personal
remarks:        * data has been removed from this object.
remarks:        * To view the original object, please query the RIPE Database at:
remarks:        * http://www.ripe.net/whois
remarks:        ****************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ERROR: Invalid name:    Gitoyen-NCC: contains invalid characters, does not start with a letter, or does not end in a letter/digit
@mxsasha mxsasha added this to the IRRDv4 phase 1 milestone Jul 6, 2018
@job
Copy link
Member

job commented Aug 6, 2018

emailed RIPE NCC and asked them to clean this up

@mxsasha
Copy link
Collaborator Author

mxsasha commented Sep 25, 2018

Route 192.170.96.0/19 has been fixed, the others have not.

@mxsasha mxsasha mentioned this issue Dec 3, 2018
Closed
@mxsasha mxsasha removed this from the IRRDv4 phase 1 milestone Dec 18, 2018
@mxsasha
Copy link
Collaborator Author

mxsasha commented Dec 18, 2018

I have moved this out of the IRRd phase 1 project/milestone, as it's not relevant for phase 1 delivery anymore.

@job
Copy link
Member

job commented Dec 27, 2019

Followed up again with RIPE NCC, they track this in DB-1382

mntner: Neutrinet-MNT still contains invalid information.

@mxsasha
Copy link
Collaborator Author

mxsasha commented Apr 27, 2020

This seems fixed.

@mxsasha mxsasha closed this as completed Apr 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@job job

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mxsasha @job