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]/

Modifications to the inet6num in the RIPE Database

Previous message (by thread): [Fwd: FAILED:]
Next message (by thread): Modifications to the inet6num in the RIPE Database

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Joao Luis Silva Damas joao at ripe.net
Thu Mar 4 10:20:17 CET 1999

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

Previous message (by thread): [Fwd: FAILED:]
Next message (by thread): Modifications to the inet6num in the RIPE Database

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]