About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Policy Proposals
search  
     
RIPE Navigation Ends
green dot Current Policy Proposals
green dot Archived Policy Proposals
green dot Subscribe to the Policy-Announce List
green dot Policy Proposal Template
green dot Policy Development Process Info (PDF)
RIPE NCC Navigation Ends
Next Section

RIPE Policy Proposal 2005-04

Number:
2005-04
Policy Proposal Name:
IPv6 Address Allocation and Assignment Policy - definition for "End-Site"
Author:
spacer
Eric Schmidt

+49 441 234 4592
Deutsche Telekom AG
Proposal Version:
1.0
Submission Date:
10 July 2005
Current Status :
Withdrawn
Suggested WG for Discussion and Publication:
Address Policy
Proposal Type:
Modify
Policy Term:
Permanent
Policy Document to be Affected:
ripe-267: "IPv6 Address Allocation and Assignment Policy".
Draft RIPE Document:
N/A
Summary of Proposal:

There are various terms for "end-site" in the IPv6 allocation and assignment policy and the RFC3177. We need to have a finally definition for "end-site" to establish clear internal assignment policies.

Draft Policy Text

a.Current:

2.9. End Site
An End Site is defined as an End User (subscriber) who has a business relationship with a service provider that involves:

that service provider assigning address space to the End User that service provider providing transit service for the End User to other sites that service provider carrying the End User's traffic that service provider advertising an aggregate prefix route that contains the End User's assignment.

b.New:

2.9 End Site

End-Site defines a customer´s network with an own link to the ISP. The customer could run various networks on different locations (e.g. multiple branches). As long as the networks are all independent and have no internal connection, each network is defined as a single end-site. If the networks have internal connection and only one common link to the ISP, these networks are summarised to one end-site.

2.9a

A customer is an End User (subscriber) who has a business relationship with a service provider that involves:

that service provider assigning address space to the End User that service provider providing transit service for the End User to other sites that service provider carrying the End User's traffic that service provider advertising an aggregate prefix route that contains the End User's assignment.

Rationale:
a.Arguments supporting the proposal

At last we will have a concrete definition for end-site. There are a lot of discussions even in different RIR regions and as far as i know non of this has reached an conclusion.

The rfc3177 defines end site as single edge networks, this is pretty close to my proposal and i think it is easier to update a RIPE Policy than an rfc.

This question was discussed in the IPv6 maillist before and it looks like that this definition could get a majority approval.

In the IPv6 End User Site Assignment Request Form (ripe-308) the requester has to confirm that he read the policy document. It is hard for a customer to understand these improper terms.

This proposal should not be combined with the /48 /56 discussion which is on at the moment. It´s just a matter of definition

b.Arguments opposing the proposal
I can´t see anything against this .....

 



 

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