[ncc-services-wg] Application Policy

Hi,

On Thu, May 19, 2005 at 12:21:20PM +0100, Damien - MPLS Buchaill wrote:
> Can someone advise, when submitting an application, do RIPE encourage/
> expect use of RFC1918 on internal links?
>
> I don't really want to kick off a debate on the rights and wrongs of using
> RFC1918 ! Just wondering is there an expectation to go down this route to
> conserve on address, or do RIPE assume you will use registered and allocate
> accordingly?

(Nitpicking: "RIPE" doesn't specifically do anything - "RIPE" is all of
us, and what "we" want or do not want is written down in the policy 
documents.  The RIPE NCC hostmasters enforce the policy that the community
has agreed upon.  If I write "RIPE" below, keep that in mind.)

RIPE will not mandate RFC violations - and using RFC1918 space on links
that generate externally-visible RFC1918-sourced packets (in response
to traceroute, ICMP host unreachable, etc.) is *definitely* a RFC violation.

If this is behind a NAT anyway, RIPE doesn't care.

To make sure that this is not misunderstood: RIPE does *not* mandate the
use of address translation and private/RFC1918 IPs.  It is assumed that
applicants have *considered* whether this might solve their address space
needs, and if it doesn't (any reason, including "I don't want that" is ok!),
RIPE has no problem with handing out official IP addresses.  No matter how
"important" or "unimportant" the hosts might be - one host warrants one
uniqe IP address (at least).

Gert Doering
        -- NetMaster
-- 
Total number of prefixes smaller than registry allocations:  71007  (66629)

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