-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would prefer RIR-LIR-ALLOCATED, LIR-SUB-ALLOCATED and LIR-USER-ASSIGNED (or similar) if we must keep ALLOCATED and ASSIGNED in the descriptions. I don't think that it is immediately clear from the proposals below whether LIR-ALLOCATED is allocated by an LIR or to an LIR. Regards, Guy

-----Original Message----- From: Gert Doering [mailto:gert@space.net] Sent: Monday, July 08, 2002 1:42 PM To: leo vegoda Cc: ipv6-wg@ripe.net; lir-wg@ripe.net; db-wg@ripe.net; sig-db@apnic.net; policy-db@apnic.net; apnic-talk@apnic.net Subject: Re: [lir-wg] Discussion Summary: Status field for inet6num objects

Hi,

On Mon, Jul 01, 2002 at 06:21:24PM +0200, leo vegoda wrote:

...

The RIPE NCC needs to implement a new status attribute for the inet6num object to reflect the new policy agreed by the RIPE, ARIN and APNIC communities.

The RIPE NCC suggested the following new status attributes for the inet6num objects:

- RIR-ALLOCATED (For allocations made by an RIR to an LIR)

- LIR-ALLOCATED (For allocations made by an LIR or an LIR's downstream customer to another downstream organisation)

- ASSIGNED (For assignments made to End User sites)

I haven't seen any replies to this so far.

I want to express that I like this proposal. It doesn't introduce any new and yet-undefined terms, but makes clear what the status of a given network is.

Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 45809 (45931)

SpaceNet AG Mail: netmaster@Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299

-----BEGIN PGP SIGNATURE----- Version: PGP 7.0.1 iQA/AwUBPSmLLo3dwu/Ss2PCEQIJdQCeOKDqqTLKCuB+o3pWMj/XJ41QJMQAnROW EWRBiRI4rPpF9DRbhrxYcK0S =Rab7 -----END PGP SIGNATURE----- This e-mail is private and may be confidential and is for the intended recipient only. If misdirected, please notify us by telephone and confirm that it has been deleted from your system and any copies destroyed. If you are not the intended recipient you are strictly prohibited from using, printing, copying, distributing or disseminating this e-mail or any information contained in it. We use reasonable endeavors to virus scan all e-mails leaving the Company but no warranty is given that this e-mail and any attachments are virus free. You should undertake your own virus checking. The right to monitor e-mail communications through our network is reserved by us.