March 2004 - db-wg - mailman.ripe.net

RE: [db-wg] proposal: haiku object
by Titley, Nigel 08 Mar '04

08 Mar '04

Whilst agreeing that the limerick is possibly restricted in its metrical form, I cannot agree with the statement that it is restricted to humorous subjects, and hence at least one of the objections to its general use is fallacious. That the metrical scheme has considerable flexibility is illustrated by the many examples received by the secret Working Group which do not conform to this supposed limitation. My solution to the lack of alternative metrical objects would simply be to redefine all poetry as limericks. I feel that this would be a far more acceptable solution, and also involves less work for the RIPE NCC. Also it has the merit of offering increased employment opportunities for poets, who would see their services called upon to rewrite all existing poetry in the limerick form. Nigel -- Nigel Titley Peering Coordinator, FLAG Telecom +44 20 7478 9579 ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

2 1

RE: [db-wg] proposal: haiku object
by Wilfried Woeber, UniVie/ACOnet 08 Mar '04

08 Mar '04

>I can fully understand, that you prefer a more generic solution. However, >the remarks: field idea is IMHO not a very good solution. Just read the >mails in the abuse-c threads about abuse contact information in remark: >fields of inet(6)num objects... I agree, this is a very important aspect, and we should get it right this time!! >One advantage of my haiku object is, that its definition is - more or >less - a copy of existing limerick object. Again, a very important aspect: limit the impact on the large number of scripts which have to parse these objects on a regular basis! >The whois client as PIM application. I'm curious, what the database >administration is going to say about that... May I humbly suggest that the proponents of such an object come back with a draft write-up (ripe document format preferred) by 31 of March (maybe -0/+1 day :-)? This would allow scheduling a discussion topic for the May meeting in the DB-WG. Cordially, (your WG Chair) _________________________________:_____________________________________ Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Universitaetsstrasse 7 : Fax: +43 1 4277 - 9 140 A-1010 Vienna, Austria, Europe : RIPE-DB: WW144, PGP keyID 0xF0ACB369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ the street finds its own use for technology...

1 0

RE: [db-wg] proposal: haiku object
by TAYON, Julien 08 Mar '04

08 Mar '04

Robert S. Plaul <mailto:robert@plaul.de> wrote: > Proposal for Adding a Haiku Object to the RIPE Database > > Requirement: > > System Administrators and other users of the RIPE Database need some > avocation beside their exhausting work with ip address space > assignments, routing and other occupations concerning database > objects which have to be taken seriously. The existing limerick > object provides such avocation but obviously has some limitations: > [...] > > Solution: > ... Even Though I fully agree with the need for a haiku object, because I am not sure of my limmericks (LIM-ROSE LIM-FRIENDS LIM-STRESS) I don't think the creation of an haiku object -per se- might be the solution. Mayhaps can we reuse the limerick objects and use the remarks field with one of the possible value : HAIKU, for haiku SONNET for such PROSE for freestyle poetry .... Therefore not only would we satisfy : - sysadmin that like well labelled object for easier retrieval, - poets for increasing their potentiality, - RIPE dba for not chaging the actual object. And if an object was to be created I would propose on the model of limerick object whois -t poem poem: [mandatory] [single] [primary/look-up key] descr: [optional] [multiple] [ ] text: [mandatory] [multiple] [ ] admin-c: [mandatory] [multiple] [inverse key] author: [mandatory] [multiple] [inverse key] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] type: [mandatory] [single] [ ] mnt-by: [mandatory] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ] Where type would be one of the folllowing : LIMERICK, PROSE, QUATRAIN, SONNET, HAIKU, ASCII-ART ... Such a solution would broadly sataisfy any sysadmin wanting to express his art freely. For managers I would propose a MEMO object too. Because, the whois DB might be the fully legitimate place for such a thing, the last place where you are gonna search for such an abomination. ;) Regards, Julien Tayon

3 2

proposal: haiku object
by Robert S. Plaul 08 Mar '04

08 Mar '04

Proposal for Adding a Haiku Object to the RIPE Database Requirement: System Administrators and other users of the RIPE Database need some avocation beside their exhausting work with ip address space assignments, routing and other occupations concerning database objects which have to be taken seriously. The existing limerick object provides such avocation but obviously has some limitations: - The limerick has to have a fixed aabba rhyme scheme which restricts the creative genius of the author in an inadequate manner. It has to be admitted that this restriction can be considered as a challenge, but for spontaneous poetical outbreaks the fixed specifications and the great length of five lines are more debilitating than inspiring. - The limerick has to be humorous. While there is nothing wrong about funny poems, there are always moments in a System Administrators' life, when there is just not the need for jokes. Deeper insights into the meaning of life and other more or less important things are said to have come to people's minds while working with internet protocols. These insights should be given the opportunity to be put into a poetic form and as such into the RIPE database for the enlightenment of like-minded people. - Even System Administrators and other users of the RIPE Database need some variety, at least when writing poems. There is a need for another poem object beside the existing limerick object. Solution: The haiku ist a traditional Japanese poetic form without the restrictions of the limerick described before. It has no rhyme scheme and no measure encumbering the author. The only formal requirement (which is not even mandatory) is the segmentation into three lines of 5, 7 and 5 units each, which are usually understood as syllables in languages other than Japanese. Haikus don't have to be humorous, in fact the traditional Japanese haiku is not humorous at all.[1] Haikus have attracted attention in the IT world already some time ago. Mentionable appearances include the Salon Magazines's Haiku Error Message Contest[2] and the ActiveState Perl Haiku Contest[3]. Although there are also voices condemning the joke haiku (and proposing the limerick as an adequate poetic form)[4], the old Japanese poem still has its right to exist, even and particularly in the world of computer professionals. People occupied with servers, routing and internet protocols at large tend to have an own kind of humor not comparable to the stupid corny jokes told in the world outside. Besides the humorous aspects of computer adminstration, the haiku empowers computer professionals to turn their insights into other aspects of computer adminstration or even life to poetry. The haiku object as described below gives System Administrators and other users of the RIPE Database the opportunity to share their thoughts and feelings put into haikus with like-minded people. [1] http://en.wikipedia.org/wiki/Haiku [2] http://archive.salon.com/21st/chal/1998/02/10chal2.html [3] http://aspn.activestate.com/ASPN/Perl/Haiku/ [4] http://www.phenry.org/junkdrawer/haiku/ The haiku class: The haiku object represents a poem that usually has three lines with 5, 7 and 5 units. In languages other than Japanese units are generally applied as syllables. There is no rhyme scheme at all. haiku: [mandatory] [single] [primary/look-up key] descr: [optional] [multiple] [ ] text: [mandatory] [multiple] [ ] admin-c: [mandatory] [multiple] [inverse key] author: [mandatory] [multiple] [inverse key] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [mandatory] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ] The content of the attributes of the haiku class are defined below: haiku Specifies the title of the haiku. HK-<string> <string> can include alphanumeric characters, and "_" and "-" characters. descr A short decription related to the object. A sequence of ASCII characters. text Text of the haiku. There are no fixed rules about the subject or form of the haiku although there are some traditional conventions. Further information about this Japanese poetic form can be found at <http://en.wikipedia.org/wiki/Haiku>. A sequence of ASCII characters. admin-c References an on-site administrative contact. From 2 to 4 characters optionally followed by up to 5 digits optionally followed by a source specification. The first digit must not be "0". Source specification starts with "-" followed by source name up to 9-character length. author References a haiku author. From 2 to 4 characters optionally followed by up to 5 digits optionally followed by a source specification. The first digit must not be "0". Source specification starts with "-" followed by source name up to 9-character length. remarks Contains remarks. A sequence of ASCII characters. notify Specifies the e-mail address to which notifications of changes to an object should be sent. An e-mail address as defined in RFC 2822. mnt-by Specifies the identifier of a registered mntner object used for authorisation of operations performed with the object that contains this attribute. Made up of letters, digits, the character underscore "_", and the character hyphen "-"; the first character of a name must be a letter, and the last character of a name must be a letter or a digit. The following words are reserved by RPSL, and they can not be used as names: any as-any rs-any peeras and or not atomic from to at action accept announce except refine networks into inbound outbound Names starting with certain prefixes are reserved for certain object types. Names starting with "as-" are reserved for as set names. Names starting with "rs-" are reserved for route set names. Names starting with "rtrs-" are reserved for router set names. Names starting with "fltr-" are reserved for filter set names. Names starting with "prng-" are reserved for peering set names. Names starting with "irt-" are reserved for irt names. Names starting with "lim-" and "hk-" are reserved for limericks and haikus respectively. changed Specifies who submitted the update, and when the object was updated. An e-mail address as defined in RFC 2822, followed by a date in the format YYYYMMDD. source Specifies the registry where the object is registered. Should be "RIPE" for the RIPE Database. Made up of letters, digits, the character underscore "_", and the character hyphen "-"; the first character of a registry name must be a letter, and the last character of a registry name must be a letter or a digit. -- RSP-RIPE

3 3

FYI: Cleanup of domain objects.
by Olaf M. Kolkman 04 Mar '04

04 Mar '04

Dear Colleagues, Excuxes for the duplicate messages. During the third week of March we will perform the cleanup as described in section B of the "Domain Cleanup Proposal"[1]. Users affected by this cleanup were contacted during the first week of January 2004[2]. Once the domain object cleanup has been finished, the RIPE NCC provisioning system will be migrated to generate reverse zones from the whois database. We will proceed with that around the last week of March 2004. This change should be transparent. A small notification will be sent to the dns-wg mailing list. The next step of the RDNS project [3] will be the introduction of the "mnt-domain:" attribute. More information about this introduction will be sent to the ncc-services-wg and dns-wg mailing lists by the end of March 2004. Please reply to me in private or to the <dns-wg(a)ripe.net> mailing list if you have any questions or comments. --Olaf Kolkman New Projects RIPE NCC [1] http://www.ripe.net/ripe/mail-archives/db-wg/2003/msg00738.html [2] The set of people contacted was larger than the set of people actually affected by the cleanup see http://www.ripe.net/ripe/mail-archives/db-wg/2004/msg00086.html for details. [3] http://www.ripe.net/reverse/rdns-project/

1 0

Minutes for DB WG RIPE 47
by Titley, Nigel 02 Mar '04

02 Mar '04

Folks, Please find attached the final minutes for the DB WG session. All comments received (thanks Leo), have been folded in. Best regards Nigel -- Nigel Titley Peering Coordinator, FLAG Telecom +44 20 7478 9579 ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. You should not copy it or use it for any purpose nor disclose the contents to any other person. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. ********************************************************************** This message has been scanned for viruses by MailControl - www.mailcontrol.com

1 0