[anti-abuse-wg] RIPE assignment-size attribute

Forwarded from another list with the poster's consent

Marco makes sense as usual.  And this is something that any whois
client should have no problem getting.

One of the major problems in v6 related blocking is figuring out just
how large a cidr to block - this helps.

-- 
Suresh Ramasubramanian (ops.lists at gmail.com)




-----Original Message-----
From: Marco d'Itri [mailto:md at Linux.IT]
Sent: 11 February 2011 08:35
To: [REMOVED]
Subject: RIPE assignment-size attribute

  This new value allows for the creation of inet6num objects indicating
  these are aggregated End User assignments, using the "assignment-size"
  attribute to indicate the size of the individual End User assignments
  in this aggregate.

IOW, this DB feature allows to know how large a user-wide blacklisting
should be.

----- Forwarded message from emadaio at ripe.net -----

From: emadaio at ripe.net
To: policy-announce at ripe.net
Cc: ipv6-wg at ripe.net, address-policy-wg at ripe.net, db-wg at ripe.net
Reply-To: ipv6-wg at ripe.net
Subject: [ipv6-wg] 2010-06 Proposal Accepted (Registration Requirements for
	IPv6 End User Assignments)


Dear Colleagues,

Consensus has been reached, and the proposal described in 2010-06 has
been accepted by the RIPE community.

The updated policy "IPv6 Address Allocation and Assignment Policy" is
available at:

   http://www.ripe.net/ripe/docs/ripe-512

The new policy "Value of the "status:" and "assignment-size:"
attributes in inet6num objects for sub-assigned PA space" is available
at:

   http://www.ripe.net/ripe/docs/ripe-513



You can find the full proposal at:

   http://www.ripe.net/ripe/policies/proposals/2010-06

Thank you for your input.

Regards

Emilio Madaio
Policy Development Officer
RIPE NCC

----- End forwarded message -----

-- 
ciao,
Marco