About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Re: IP Address Space Assignment Procedures (ripe-72++)

  • To: (Antonio_Blasco Bonito)
  • From: (Daniel Kalchev)
  • Date: Thu, 25 Nov 93 13:11:55 EET
  • Cc:

> >   > - I think this document should briefly say something about the practice
> >   >   of splitting a block after it has been assigned.
> >   >   It is better to touch that problem here, or at least make a reference
> >   >   to another document.
> > 
> > I don't understand what you mean?
> > Do you mean splitting because of policy?
> 
> An organization may have a certain network deployment plan and requires
> a block to satisfy its requirements. After that some of those network
> numbers may be assigned to subsidiaries or partners which require different
> registrations because of policy (aut-sys, community, ...) or to differentiate
> responsabilities (admin-c, tech-c, ...). In those cases the solution
> is to split the block. This issue needs to be mentioned in the document,
> I think.

Perhaps the best approach is for such an organization to return the
"unused" address space back to the registry from where they got it.
This way it can be allocated to another organization.

Daniel Kalchev
BG-NIC



  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | Copyright Statement
RIPE.NET Homepage LIR Portal RIPE Community