[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Wg-rms] Stepping down from co-chair role
Terry,
--- Terry Manderson <terry@apnic.net> wrote:
> what do you see about secure email that is not
> appropriate?
I can use a well known cpan module to handle https
trivially without knowing multiple layers of
certificates.
I haven't found a good way to try to encypt email on
the fly with gpg or certificates. and receiving the
response means another round of decryption.
The asynchronous nature of this just makes it hard for
me. Selfish motives (like everyone else).
>
> I apologise that your interactions with the existing
> APNIC systems have
Thanks for the apology. (that has to be first from
APNIC!)
> system or that the levels of
> authorisation/authentication were causing
> some confusion or issues?
syntax and authorisation.
>
> I think that any system will have a level of
> 'learning-curve'
> regardless if it is email based or not. Can you
> clarify if your
> meetings were focused on:
> - authorisation (knowing what your maintainer can
> achieve)
> - authentication (the password/pgp key/other failed
> expectations)
> - syntactical issues (Just couldn't get the object
> "right")
the above three..
> - a lack of appropriate documentation/instruction
> by APNIC.
well.. I can't say that I love the APNIC website.. but
after some digging the docco is there.
>
> Can you elaborate on the tools that you would find
> valuable? and what
two sets of tools.
1) unix command line portable tools to do one-off
interactions
2) a perl or c/c++ library to allow hooks from a
management framework.
3) work with people like cisco on their management
interfaces that do auto push updates to APNIC.
> information you would like back from those tools on
> a success or
> failure?
precisely highlighted what failed. why it failed, and
an example of something what wouldn't fail.
and immediate feedback.. not 2 hours waiting for
greylisting to catch-up.
>
> I appreciate that you would like to interact with
> APNIC systems and
> data in a different fashion that suits your needs.
> Are you able to be
> more precise and provide a list of your
> requirements?
>
A syntax and authorisation model that is versioned and
clearly documented (and works!). So if you (APNIC)
change bits, you MUST increment the revision.. I think
in REST this is close to mandatory, In XML it is.
A window of backward compatibility, so even if you go
to version 5.2, version 5.1 will be supported on its
own URL for at least 6 months.
The other bits from the dns demo are good.
Although watching the vid again to freshen my mind,
you need to learn how to drive your mac ;-)
-Jas
--
Jas Webb
Send instant messages to your online friends http://au.messenger.yahoo.com
