- ncc-services-wg - mailman.ripe.net

Pre-PDP discussion: "Yearly list of services by RIPE"
by Richard Hartmann 02 Apr '13

02 Apr '13

Dear all, this is the fifth suggestion: RIPE will create a yearly list of all services it provides to members or the general public This list will include at least: * Name of the service * Cost in time and money of maintaining and possibly extending this service * Cost in time and money of maintaining the backend needed for this service; this is to catch stuff that relies on old and brittle infra * Number of users if applicable/traceable per year * Number of queries/transactions if applicable/traceable per year * General usefulness of the service from RIPE's POV * Status of service, such as "active, supported", "deprecated", or "scheduled for decommissioning on YYYY-MM-DD" * A suggestion for the future status of the service If in doubt, RIPE will focus less on detailed interpretation and analysis and more on giving out as many hard facts and stats as possible. Interpretation will happen on the mailing lists anyway. RIPE will implement this policy in a light-weight manner that is not a drain on resources in and as of itself.

7 14

Pre-PDP discussion: "All RIPE documents should be plain text"
by Richard Hartmann 30 Mar '13

30 Mar '13

Dear all, this is the first in a series of emails which I hope will advance into PDPs and then updated policies. Some of them are closely related, but I submit them individually so that if there are any hold-ups with a specific one, the other ones can still progress. My first suggestion is: The canonical and binding format of all documents is plain text in UTF-8 encoding. If a document can not reasonably be stored as plain text, PDF/A-1a[1] will be used. If any document exists in both plain text and PDF/A-1a, plain text is binding. Any other form is considered non-binding as soon as a plain text or PDF/A-1a variant exist. All legacy documents which are still valid or relevant to current policies will be transformed within a year of this proposal becoming policy. The reasoning behind this should be obvious: Ensure that all documents will be in the most simple-to-parse format now and forever. Richard [1] https://en.wikipedia.org/wiki/PDF/A

10 20

Pre-PDP discussion: "All PDP emails, documents and websites should come with unified diff"
by Richard Hartmann 30 Mar '13

30 Mar '13

Dear all, this is the third suggestion: All PDP-related emails, web pages, and other documents by RIPE will either carry a unified diff (diff -ruN) or directly link to a page which shows said unified diff. Other formats, like full text, old/new text, etc are encouraged as well, but the diff is the binding format in which PDPs are published, documented, and discussed. Rationale: It's needlessly hard to read and compare full or partial text dumps, forcing people to do work by themselves and for themselves which a computer could do once and for all. A XML-based format that's parse-able by new tools has been proposed as an alternative. This would mean extra work while defining the XML format, to write new tools, and cut of the extensive tools and workflows around unified diffs. The point has also been raised that word diffs may be easier to read. Quoth the manpage: Nevermerge! Show words as [-removed-] and {+added+}. Makes no attempts to escape the delimiters if they appear in the input, so the output may be ambiguous. Ironically, --word-diff in git comes with an option that allows parsing, --porcelain, which turns word-based diff back into line-based diffs: Use a special line-based format intended for script consumption. Added/removed/unchanged runs are printed in the usual unified diff format, starting with a +/-/` ` character at the beginning of the line and extending to the end of the line. Newlines in the input are represented by a tilde ~ on a line of its own. Long story short: Unified diffs are called unified diffs and universally accepted for a reason. Richard

2 2

Pre-PDP discussion: "All published documents and PDPs are maintained with git"
by Richard Hartmann 30 Mar '13

30 Mar '13

Dear all, this is the fourth suggestion: All RIPE documents are made available by means of a git repository, both via anonymous pull and via a web interface. The read-only access is open to everyone, RIPE member or not. Within RIPE, this git repository is the canonical place for all published documents. All published documents are copied from it. All PDPs will be maintained as a separate branch. Every new version of a PDP is an update within that branch. The branch will either be merged back into master or left unmerged but intact, depending on if they are accepted or not. Old documents and PDPs, if still on record, will be put into separate branches that reflect correct history. The master branch is then merged into old history, creating one single history. This will happen one year after this policy comes into effect at the latest. If the proposal "All PDP emails, documents and websites should come with unified diff" is accepted, all diffs will be generated from git. Rationale: git is here to stay, it's highly efficient, allows off-line work, and has generally won the fight for version control systems in the foreseeable future. Not relying on technical tools which were created with ever-chaning text files in mind is inefficient at best. I offer to help maintain said git repository pro bono for at least 12 months or until the history has been merged, whichever is later. Richard PS: Think of those five emails as a patchset ;)

6 26

Pre-PDP discussion: "PDPs should be renamed from YYYY-NN to RIPE-PDP-YYYY-NN-vN"
by Richard Hartmann 30 Mar '13

30 Mar '13

Dear all, this is the second suggestion: The canonical name of all PDPs will be RIPE-PDP-YYYY-NN. Updated versions will receive suffixes like Internet Drafts, i.e. -v1, -v2, -v3. Old-style PDP names of the format YYYY-NN will remain valid, but all new documentation and communication by RIPE will use the new format. Alternatively, the name of the Working Group may be embedded in all names, e.g. RIPE-PDP-APWG-YYYY-NN, or RIPE-APWG-PDP-YYYY-NN. Rationale should again be obvious: Encoding information in names is good practice. Unique names make life easier for everyone involved. If other RIRs follow suit, cross-referencing becomes easier. Rationale for keeping "PDP" in the WG option is because a WG may want to publish something other than a PDP at some point. The alternatives should be decided upon during the discussion phase of the PDP. Richard

9 13

2012-07 Draft Document and Impact Analysis will be produced (RIPE NCC Services to Legacy Internet Resource Holders)
by Emilio Madaio 28 Mar '13

28 Mar '13

Dear Colleagues, The discussion period for the proposal described in 2012-07, "RIPE NCC Services to Legacy Internet Resources Holders", has ended. A draft document and the RIPE NCC Impact Analysis will now be prepared for review. We will publish the documents shortly and we will make an announcement. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2012-07 Regards Emilio Madaio Policy Development Officer RIPE NCC

4 4

Improving Data Quality on the FTP Site
by Laura Cobley 28 Mar '13

28 Mar '13

Dear colleagues, As part of our efforts to improve data quality across the RIPE NCC, we would like to update a file within the FTP site: ftp://ftp.ripe.net/pub/stats/ripencc/membership/alloclist.txt According to our records, this file should contain a list of allocated address space held by the RIPE NCC membership. However, in addition to the expected data, the file also contains a number of references to obsoleted member accounts which no longer exist. These include, for example, accounts created for internal testing and accounts which have subsequently been renamed and therefore appear twice. We are therefore proposing a clean-up of this data so that it shows only allocated address space held by the RIPE NCC membership. Other than removing the erroneous information, the format of the data will not be changed. We plan to begin the clean-up three weeks from today (Thursday 28 March, 2013) and would be grateful for any feedback via this mailing list or sent to <ncc(a)ripe.net> before then. Kind regards, Laura Cobley RIPE NCC Customer Services Manager

3 5

Certifying of PI End User Address Space
by Andrew de la Haye 27 Mar '13

27 Mar '13

Jim, Of the three implementation options, the most straightforward is option 1, where the PI End User becomes a full member, as this requires no additional development for the RIPE NCC. Note that the additional income from this scenario would exceed any additional cost. For option 2 (going through the sponsoring LIR) and option 3 (going to the RIPE NCC directly), there is a possibility to provide an automated solution for which only PI End Users who have submitted a 2007-01 End User Assignment Agreement are eligible. This means the RIPE NCC will need to develop a solution where the following informational elements are cross-referenced with each other: a) The authoritative control over the address space (i.e. the ability to authenticate against the relevant objects in the RIPE Database) b) The End User Assignment Agreement that was submitted and verified by the RIPE NCC c) The RIPE NCC Access credentials for accessing the certification management interface Please keep in mind that in both estimates, where the actual cost falls in the given broadband depends on the amount of manual verification that is desired, which can range from random periodic audits to verification of every application by RIPE NCC staff. Also, the additional costs with smaller or larger uptake are estimated to be quite low. Option 2: A one time cost of 65 kEUR, with a running cost of 45 kEUR, based on an estimated uptake of 15% or approximately 2,500 PI End Users. Option 3: A one time cost of 70kEUR, with a running cost of 70 kEUR, based on an estimated uptake of 15% or approximately 2,500 PI End Users. Lastly, it is important to point out that as the certificate is valid for only one year, providing this service to PI End Users creates an opportunity for periodic confirmation of the 2007-01 End User Assignment Agreement, further improving the robustness of our Registry. Kind regards, Andrew de la Haye Chief Operations Officer RIPE NCC

5 6

Re: [ncc-services-wg] 2012-07: Fresh draft
by Niall O'Reilly 25 Mar '13

25 Mar '13

On 25 Mar 2013, at 09:45, Dave Wilson wrote: > Morning, Niall! > > I was just wondering if the new draft went to the co-chairs and Emilio? Yes, on 8 March. > Is there anything I can do to help? I think you just have! Thanks for asking. /Niall

2 2

Certifying of PI End User Address Space
by Andrew de la Haye 21 Mar '13

21 Mar '13

Dear colleagues, On 11 February, the RIPE NCC asked the RIPE NCC membership and the RIPE community for feedback on how to make Provider Independent (PI) End User address space eligible for resource certification (RPKI). Although we’ve received valuable input at several operator meetings and through various other communication channels, we want to emphasise the importance of your participation on this mailing list. We strongly encourage further feedback on this important issue, before the consultation period comes to a close. To summarise, the discussion so far involves three possible implementation options: 1) A PI End User becomes a RIPE NCC member 2) A PI End User requests a resource certificate through their sponsoring LIR and gets access to the ROA management system themselves, or delegates management to the sponsoring LIR 3) A PI End User requests a resource certificate directly from the RIPE NCC, without becoming a member, and obtains access to the ROA management system The feedback provided so far clearly differentiates between two groups of PI End Users: those who use the sponsoring LIR solely to request the PI resources but manage everything else themselves, and those who rely on the sponsoring LIR for everything, ranging from BGP routing to RIPE Database updates. In order to cater to both groups, the feedback so far suggests we facilitate both options 2 and 3, while option 1 will continue to remain available at all times. These options have different expected impacts on the RIPE NCC’s operations. The RIPE NCC does not expect option 1 or 2 to have a major impact, as they align with our current business practices. Option 3 would require PI End Users to have a direct contact with the RIPE NCC. As this would be a new venture for the RIPE NCC, we expect it would be the most labour intensive of the three options and would have the greatest impact in terms of resources. Some feedback has pointed out the lack of RIPE Policy on this issue. At this time, the RIPE NCC is requesting feedback on whether or not resource certification should expand beyond a RIPE NCC member service. Discussions about potential RIPE Policy, should this happen, can take place via the appropriate channels. Again, we strongly encourage your feedback before the consultation period ends on 30 March 2013, after which time the RIPE NCC Executive Board will recommend which option(s) to implement. We look forward to hearing from you. Kind regards, Andrew de la Haye Chief Operations Officer RIPE NCC

13 26