This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[policy-announce] 2016-02 New Policy Proposal (Resource Authentication Key ( RAK ) code for third party authentication)
- Next message (by thread): [policy-announce] 2016-03 New Policy Proposal (Locking Down the Final /8 Policy)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco Schmidt
mschmidt at ripe.net
Mon May 2 14:12:32 CEST 2016
Dear colleagues,
A new RIPE Policy Proposal 2016-02, "Resource Authentication Key ( RAK )
code for third party authentication"
has been made and is now available for discussion.
The proposal aims to allow all number resources, in exacts and more
specifics,
to be authenticated via an date expiring API-key.
You can find the full proposal at:
https://www.ripe.net/participate/policies/proposals/2016-02
We encourage you to review this proposal and send your comments to
<ncc-services-wg at ripe.net> before 31 May 2016.
Regards,
Marco Schmidt
Policy Development Officer
RIPE NCC
- Next message (by thread): [policy-announce] 2016-03 New Policy Proposal (Locking Down the Final /8 Policy)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]