On 05/08/2014 19:08, Daniel Suchy wrote:
In general I think NCC has enough budged to support multiple input interfaces and keep *everyone* confortable, even some input method seems to be "legacy".
The RIPE NCC also needs to keep its admin costs under control.
And I don't think it's hard in this case.
I don't have enough information to make a judgement about this, but would note in passing that many of the legacy systems I deal with are troublesome to maintain - much more troublesome than non legacy systems.
The "minority" using email interface is still large enough to support email requests. Also there should be some operational issues with portal/API interface and then is fine to have another way to submit request (even it's processed later), as traditional email can be easily queued...
Even I'm using portal preferably for majority of changes, I would like to have fall-back option.
We will continue to have fall back to the LIR portal. I'm in favour of dumping the email based templates in favour of an API based system, but we need the API based system to be in place for a while to allow time for people to migrate over. If the consultation ends on Oct 1, with phaseout planned for end Dec 2014, then that's 3 months for everyone to migrate over, which isn't long enough. Could you support them for at least 6-12 months after the API system is introduced? Nick