Modifications to the inet6num in the RIPE Database

Dear all,

A week has passed and no comments against the proposed modifications to the 
IPv6 object have been put forward.

Therefore we take it that everyone is happy with it and will procede with the 
implementation. We expect this to be available in about two weeks.

The original message is repeated below for your reference.

Regards,
Joao Damas
DB Group
RIPE NCC


------- Begin Original Message
From: Joao Luis Silva Damas <joao at ripe.net>
Date: Thu, 04 Mar 1999 10:20:17 +0100
To:       lir-wg at ripe.net, db-wg at ripe.net
Subject:  Modifications to the inet6num in the RIPE Database

Dear all,
below are the proposed modifications to the inet6num object in the RIPE 
Database as discussed during the past RIPE Meeting.

These are mainly to bring the IPv6 object up to the IPv4 object's 
functionality.

The two suggested changes are:

- - addition of a "status" attribute with the following possible values:
  TLA, NLA and SLA.
  Syntax checks will be done so that:
  TLA is only allowed if the prefix length is 3<x<=16
  NLA is only allowed if the prefix length is 16<x<=48
  SLA is only allowed if the prefix length is 48<x<=64

- - addition of "mnt-lower" capabilities, as in the IPv4 object.

We would like to open a comment period of 1 week from today to gather input 
and proceed with implementation if there is consensus.

Regards,
Joao Damas
DB Group
RIPE NCC
------- End Original Message