[dns-wg] NCC reverse delegation criteria

Recently, a discussion regarding the checks performed by the NCC before
reverse delegation is made came up on the members-discuss list.  It was
concluded that this should be discussed here rather than there.

The members archive might not be available to all, so I'll try to
summarize. Please add your take on summary if you find mine lacking.

The questioned practice was that the NCC rejects the delegation request
if the target server is found to be an open recursor.

Some participants argued that this is not a technical problem, and some
said yes it is.

Some held that the NCC has no authority blocking a request, but it was
argued that every delegation is subject to RFC 1591 responsibilites. 

For starters, are the delegation requirements described somewhere? 

Best regards, 
-- 
Måns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE           SA0XLR            +46 705 989668
In 1962, you could buy a pair of SHARKSKIN SLACKS, with a "Continental
Belt," for $10.99!!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: </ripe/mail/archives/dns-wg/attachments/20190610/77b404f3/attachment.sig>