This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] The New "organisation object" Proposal
- Previous message (by thread): [db-wg] The New "organisation object" Proposal
- Next message (by thread): [db-wg] The New "organisation object" Proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sanjaya
sanjaya at apnic.net
Thu Aug 28 09:22:49 CEST 2003
Hi all, > Specifies the ID of an organisation object. An organisation > ID is made up of 'ORG-' prefix, followed by 2 to 4 letters, > digits, a dash and is followed by the database source (in the > RIPE Whois Database this is 'RIPE'). For example: > > ORG-RT34-RIPE > > Note that all parts are mandatory, thus ORG-RT-RIPE would be > an invalid ID as it is missing the numeric part. While we understand the need for strict naming convention to avoid name disputes, may I request that the rules and convention will not be hard coded in the software but put in a customisable config file. As a user of RIPE's whois software, APNIC might want to have a slightly different naming convention & rules :-) > May be included in any other object type. It points to an > existing organisation object representing the entity that > holds the resource. The value of this attribute is the ID of > the organisation object. It is mandatory in the aut-num > objects, and inetnum and inet6num objects with > "ALLOCATED-BY-IANA", "ALLOCATED-BY-RIR", "ALLOCATED-BY-RIR > NON-PORTABLE", "ALLOCATED-BY-RIR PORTABLE" and > "ALLOCATED-BY-RIR UNSPECIFIED" values. It is optional in all > other objects, and it is single valued in all objects. As we're talking about the use of the organisation object, can we use it to show delegation path (instead of overloading the status attribute above) in a resource object (i.e. aut-num, inetnum and inet6num). For example, if querying an inetnum, you get this response: % whois 192.168.86.251 inetnum: 192.168.86.0 - 192.168.86.255 netname: EXAMPLE-NET-86 descr: Sample network registry: ORG-RIPE1-RIPE custodian: ORG-RSIS54-RIPE country: NL admin-c: JE1-RIPE tech-c: JE2-RIPE [...] source: RIPE organisation: ORG-RIPE1-RIPE org-name: RIPE NCC Operations org-type: RIR address: Singel 258 address: 1016 AB Amsterdam address: The Netherlands country: NL phone: +31 20 535 4444 fax-no: +31 20 535 4445 e-mail: ops at ripe.net admin-c: AP110-RIPE tech-c: OPS4-RIPE [...] source: RIPE organisation: ORG-RSIS54-RIPE org-name: Random Street Internet Services org-type: LIR descr: An example organisation address: Random St. address: The Netherlands phone: +31 123 4567 fax-no: +31 123 4568 e-mail: contact at example-org.net admin-c: EXAM1-RIPE tech-c: EXAM2-RIPE [...] source: RIPE person: John Example nic-hdl: JE1-RIPE [...] source: RIPE person: John Example Jr nic-hdl: JE2-RIPE [...] source: RIPE Cheers, Sanjaya ______________________________________________________________________ Senior Project Manager <sanjaya at apnic.net> Asia Pacific Network Information Centre (APNIC) Tel: +61-7-3858-3100 PO Box 2131 Milton, QLD 4064 Australia Fax: +61-7-3858-3199 ---_____________________________________________________________________ _
- Previous message (by thread): [db-wg] The New "organisation object" Proposal
- Next message (by thread): [db-wg] The New "organisation object" Proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]