contractual relationship requirement for end users implementation update policy proposal 2007-01

12
Contractual Relationship Requirement for End Users Implementation update policy proposal 2007-01

Upload: timothy-cannon

Post on 18-Jan-2018

218 views

Category:

Documents


0 download

DESCRIPTION

Arne Kiessling, RIPE 61 Resources Assigned Under the New Policy 3

TRANSCRIPT

Page 1: Contractual Relationship Requirement for End Users Implementation update policy proposal 2007-01

Contractual Relationship Requirement for End UsersImplementation update policy proposal

2007-01

Page 2: Contractual Relationship Requirement for End Users Implementation update policy proposal 2007-01

Arne Kiessling, RIPE 61 2

Policy Background• “The intention of this policy document is to ensure that

the RIPE NCC (…) can confirm that the End User exists, continues to exist and that they continue to fulfil their obligations to comply with the original assignment conditions.”

• Phase One (new assignments):- Implemented 3 March 2009- 7624 independent Internet resources assigned under the new policy since then

Page 3: Contractual Relationship Requirement for End Users Implementation update policy proposal 2007-01

Arne Kiessling, RIPE 61

Resources Assigned Under the New Policy

3

IPv4 PI, 3550

AS Numbers, 3812

IPv6 PI and IXP, 239IPv4 Anycast, 11

IPv6 Anycast, 14

Page 4: Contractual Relationship Requirement for End Users Implementation update policy proposal 2007-01

Arne Kiessling, RIPE 61

Phase Two - Existing Assignments• “(..) a contractual relationship must be put in place for

End Users of provider independent number resources which were previously assigned (..)”

• Amount of resources: 26,940

• Phase Two started in May 2009- Deadline extended several times- Final deadline: 31 December 2010

4

Page 5: Contractual Relationship Requirement for End Users Implementation update policy proposal 2007-01

Arne Kiessling, RIPE 61

Feedback for Resources Covered by Phase Two

5

Feedback received (24209)

Feedback missing (2731)

Page 6: Contractual Relationship Requirement for End Users Implementation update policy proposal 2007-01

Arne Kiessling, RIPE 61

Phase Two Resource Status

6

My Infrastructure, 5913

Not My End User, 6774

My End User (without docs), 2844

My End User(with docs), 3475

My End User (approved docs),

5203

My End User, 11522

Page 7: Contractual Relationship Requirement for End Users Implementation update policy proposal 2007-01

Arne Kiessling, RIPE 61

Phase Three – “Orphaned Assignments”• Directly contact End Users that have not entered into

a contract with a sponsoring LIR or the RIPE NCC

• Draft procedure document sent to RIPE NCC Services WG mailing list and announced on ripe.net in August

• No comments or feedback received from community yet

7

Page 8: Contractual Relationship Requirement for End Users Implementation update policy proposal 2007-01

Arne Kiessling, RIPE 61

Resources to be Considered in Phase Three

8

Not My End User, 6774

Feedback missing, 2731

My End User (without docs), 2844

Page 9: Contractual Relationship Requirement for End Users Implementation update policy proposal 2007-01

Arne Kiessling, RIPE 61

Phase Three – Contact End Users• “Registration data (range, contact information, status

etc.) must be correct at all times (i.e. they have to be maintained).”

• Contact based on registration data in the RIPE Database using different levels of contact details

• Contact method: by email

9

Page 10: Contractual Relationship Requirement for End Users Implementation update policy proposal 2007-01

Arne Kiessling, RIPE 61

Phase Three - Process• Contacting End User in batches, prioritised by resource

visibility in global routing table• Resource visibility: current, recent (< 12 months), old

(> 12 months)• End Users will be directed to an online form to provide

feedback regarding resource usage, holdership etc.• Monitoring activity on online forms and keeping logs• Manual follow-up by RIPE NCC

10

Page 11: Contractual Relationship Requirement for End Users Implementation update policy proposal 2007-01

Arne Kiessling, RIPE 61

Phase Three – Resource de-registration• 3 months after initially contacting the End User, de-

registration procedure will start if there is no response from End User

• No contract three months after response de-registration procedure starts

For further questions, remarks or suggestions contact us:

<[email protected]>

11

Page 12: Contractual Relationship Requirement for End Users Implementation update policy proposal 2007-01

Questions?