From m4rtntns at gmail.com Mon Dec 5 16:54:02 2011 From: m4rtntns at gmail.com (Martin T) Date: Mon, 5 Dec 2011 17:54:02 +0200 Subject: "org:" field in person object Message-ID: In person object template, there is an "org:" field: martint at T60:~> whois --version Version 4.7.5. Report bugs to . martint at T60:~> whois -h whois.ripe.net -t person | grep org org: [optional] [multiple] [inverse key] martint at T60:~> As I understand, this is for organization object(?). In which case this is needed? So far I have never seen a person object with "org:" specified.. regards, martin From m4rtntns at gmail.com Mon Dec 5 17:01:52 2011 From: m4rtntns at gmail.com (Martin T) Date: Mon, 5 Dec 2011 18:01:52 +0200 Subject: best practice for "changed:" field Message-ID: As I understand, in RIPE database every object has a mandatory "changed" field. There can be multiple "changed" fields. Is it a good practice to keep all the changes made to the object? What are the advantages and disadvantages? regards, martin From shane at time-travellers.org Mon Dec 5 18:06:16 2011 From: shane at time-travellers.org (Shane Kerr) Date: Mon, 05 Dec 2011 18:06:16 +0100 Subject: best practice for "changed:" field In-Reply-To: References: Message-ID: <1323104778.2111.33.camel@shane-desktop> Martin, On Mon, 2011-12-05 at 18:01 +0200, Martin T wrote: > As I understand, in RIPE database every object has a mandatory > "changed" field. There can be multiple "changed" fields. Is it a good > practice to keep all the changes made to the object? What are the > advantages and disadvantages? The "changed:" attribute is for your own purposes, as I understand it. So, if you don't care about the history of changes, then you can keep only a single "changed:" line. If you want a full history, then you can add a new "changed:" line with every update. The drawback here is that you can end up with a very big object, of course. And of course you can remove some changes based on whatever rule you want; for example if you don't care about changes more than a year old, or only want to keep the last 5 changes. -- Shane From m4rtntns at gmail.com Tue Dec 6 11:10:31 2011 From: m4rtntns at gmail.com (Martin T) Date: Tue, 6 Dec 2011 12:10:31 +0200 Subject: which attributes support inverse search? Message-ID: Hi, which attributes inRIPE database are inverse searchable? I know one can use "origin"(for example "whois -Brh whois.ripe.net -i origin AS3249") and "person", but are there other practically usable attributes, which support inverse search? regards, martin From denis at ripe.net Tue Dec 6 11:30:25 2011 From: denis at ripe.net (Denis Walker) Date: Tue, 06 Dec 2011 11:30:25 +0100 Subject: which attributes support inverse search? In-Reply-To: References: Message-ID: <4EDDEEC1.9040600@ripe.net> Dear Martin There is a RIPE Database Queries Reference Chart that shows you all the inverse searchable attributes. You will find this and other very useful documentation on many aspects of the RIPE Database here: http://www.ripe.net/data-tools/support/documentation regards Denis Walker Business Analyst RIPE NCC Database Group On 6/12/11:50 11:10 AM, Martin T wrote: > Hi, > > which attributes inRIPE database are inverse searchable? I know one > can use "origin"(for example "whois -Brh whois.ripe.net -i origin > AS3249") and "person", but are there other practically usable > attributes, which support inverse search? > > > regards, > martin > > From thor.kottelin at turvasana.com Tue Dec 6 11:42:48 2011 From: thor.kottelin at turvasana.com (Thor Kottelin) Date: Tue, 6 Dec 2011 12:42:48 +0200 Subject: "org:" field in person object In-Reply-To: References: Message-ID: > -----Original Message----- > From: Martin T [mailto:m4rtntns at gmail.com] > Sent: Monday, December 05, 2011 5:54 PM > To: db-help at ripe.net > In person object template, there is an "org:" field: > As I understand, this is for organization object(?). Yes. > In which case > this is needed? The query reference manual has the following information: 'This attribute may appear in any object type. It points to an existing organisation object representing the entity that holds the resource, (in the cases where the RIPE Database object represents an Internet resource). In other objects, it can be used to specify the business relations. The value of this attribute is the ID of the organisation object.' > So far I have never seen a person object with > "org:" > specified.. Here is an example: http://apps.db.ripe.net/whois/lookup/ripe/person-role/TK1136-RIPE.html. -- Thor Kottelin http://www.anta.net/ From m4rtntns at gmail.com Thu Dec 8 16:45:02 2011 From: m4rtntns at gmail.com (Martin T) Date: Thu, 8 Dec 2011 17:45:02 +0200 Subject: RIPE and DNS delegations for provider independent addresses Message-ID: In case "companyA" has /24 provider independent network allocated by RIPE, which has RIPE NCC as a first maintainer and "companyA" maintainer object as a second maintainer, then is "companyA" able to delegate reverse DNS queries to the DNS server it prefers? Or should "companyA" contact RIPE NCC in order to get reverse delegation(http://www.ripe.net/data-tools/dns/reverse-dns) done? In addition, if I know the provider independent IP address, then is it possible to view the delegated DNS server using the whois.ripe.net database? So far I have used "dig +trace -x I.I.P.P" and followed the chain of delegations. regards, martin From m4rtntns at gmail.com Thu Dec 15 02:40:40 2011 From: m4rtntns at gmail.com (Martin T) Date: Thu, 15 Dec 2011 03:40:40 +0200 Subject: creating inet6num objects in RIPE database for customer IPv6 networks Message-ID: I work in a company where we have been very strict with documenting and creating inetnum objects in RIPE database for IPv4 addresses, which we have allocated to our customers(from /31 networks to /24). However, for IPv6 we have only created inet6num object to our huge /32 IPv6 network, but none of the customer allocations(usually /48) are documented in RIPE database. Should one do this? Is this mandatory? In addition, as I have understood, one might get into trouble if he doesn't document it's IPv4 addresses in RIPE(lose it's allocation)- does the same apply to IPv6 addresses as well? I mean might we lose our /32 IPv6 network if we proceed with current practise and not register customer IPv6 allocations in RIPE database? regards, martin From thor.kottelin at turvasana.com Fri Dec 30 15:14:11 2011 From: thor.kottelin at turvasana.com (Thor Kottelin) Date: Fri, 30 Dec 2011 16:14:11 +0200 Subject: Digest intervals Message-ID: Due to low traffic, db-help digests are being sent very infrequently. As an example, the one I received today contained messages posted on 6, 8 and 15 December. This problem can be fixed by setting the mailing list software to send digests at least once a day whenever there are messages. Would you like the RIPE NCC to make such a change? -- Thor Kottelin http://www.anta.net/