[Ietf-not43] Comments on draft-ietf-crisp-iris-areg-02.txt

[George Michaelson]

On Tue, 24 Jun 2003 17:19:52 -0400 Andrew Newton <anewton at ecotroph.net> wrote:
> 
> >>3.2.2 <ipv4Network> Result
> >>
> >>[...]
> >>   o  One of <directAllocation>, <directAssignment>, or <reassigned>
> >>      signifying the assignment and allocation status of the network.
> > 
> > 
> > Currently, ARIN has additional network types. Perhaps it should be 
> > reworded to not be limited:
> >     o The assignment or allocation status of the network such as
> >       <directAllocation>, <directAssignment> or <reassigned>.
> 
> Listing out all the possibilities helps the client do localization.  It 
> doesn't have to be limited to these three though.  Is there a list of 
> all the types?
> 
> > Also, the terminology PA and PI are used in conjunction with the network 
> > type at some of the RIRs. You may want to consider their use as well.
> 
> Is there a pointer to their meaning for those of us less educated?
> 
 
Andy, this is a very bad space to be defining 'ENUMERATED' type values for. The
status is a matter of policy, within each RIR region, and is dynamic: it changes
in the 3-5 year timeframe. It would be a mistake to lock into RFC status
specific values for this kind of field, its not really in IETF definitional
space.

If its not possible to take a DB schema approach, and define this as being a
keyword-value restricted element, where the value set is locally defined, in
some external process, then I would suggest it might be best left as a simple
string type, with no applied 'business logic' on it.

PI and PA are actually deprecated terms. We now refer to ALLOCATED PORTABLE and
ALLOCATED NON-PORTABLE and ASSIGNED PORTABL and ASSIGNED NON-PORTABLE but this
is a matrix of values, and there are emerging changes in both RIPE and APNIC
region.

cheers
	-George