| line |
stmt |
bran |
cond |
sub |
pod |
time |
code |
|
1
|
|
|
|
|
|
|
package Net::Whois::Object::Mntner; |
|
2
|
|
|
|
|
|
|
|
|
3
|
1
|
|
|
1
|
|
86028
|
use strict; |
|
|
1
|
|
|
|
|
12
|
|
|
|
1
|
|
|
|
|
33
|
|
|
4
|
1
|
|
|
1
|
|
6
|
use warnings; |
|
|
1
|
|
|
|
|
1
|
|
|
|
1
|
|
|
|
|
37
|
|
|
5
|
1
|
|
|
1
|
|
6
|
use base qw/Net::Whois::Object/; |
|
|
1
|
|
|
|
|
2
|
|
|
|
1
|
|
|
|
|
608
|
|
|
6
|
|
|
|
|
|
|
|
|
7
|
|
|
|
|
|
|
####################################################################################### |
|
8
|
|
|
|
|
|
|
# The following lines where auto-generated by 'perl whois_to_attribute.pl Mntner' |
|
9
|
|
|
|
|
|
|
|
|
10
|
|
|
|
|
|
|
# % This is the RIPE Database query service. |
|
11
|
|
|
|
|
|
|
# % The objects are in RPSL format. |
|
12
|
|
|
|
|
|
|
# % |
|
13
|
|
|
|
|
|
|
# % The RIPE Database is subject to Terms and Conditions. |
|
14
|
|
|
|
|
|
|
# % See http://www.ripe.net/db/support/db-terms-conditions.pdf |
|
15
|
|
|
|
|
|
|
# |
|
16
|
|
|
|
|
|
|
# mntner: [mandatory] [single] [primary/lookup key] |
|
17
|
|
|
|
|
|
|
# descr: [optional] [multiple] [ ] |
|
18
|
|
|
|
|
|
|
# org: [optional] [multiple] [inverse key] |
|
19
|
|
|
|
|
|
|
# admin-c: [mandatory] [multiple] [inverse key] |
|
20
|
|
|
|
|
|
|
# tech-c: [optional] [multiple] [inverse key] |
|
21
|
|
|
|
|
|
|
# upd-to: [mandatory] [multiple] [inverse key] |
|
22
|
|
|
|
|
|
|
# mnt-nfy: [optional] [multiple] [inverse key] |
|
23
|
|
|
|
|
|
|
# auth: [mandatory] [multiple] [inverse key] |
|
24
|
|
|
|
|
|
|
# remarks: [optional] [multiple] [ ] |
|
25
|
|
|
|
|
|
|
# notify: [optional] [multiple] [inverse key] |
|
26
|
|
|
|
|
|
|
# mnt-by: [mandatory] [multiple] [inverse key] |
|
27
|
|
|
|
|
|
|
# created: [generated] [single] [ ] |
|
28
|
|
|
|
|
|
|
# last-modified: [generated] [single] [ ] |
|
29
|
|
|
|
|
|
|
# source: [mandatory] [single] [ ] |
|
30
|
|
|
|
|
|
|
# |
|
31
|
|
|
|
|
|
|
# % This query was served by the RIPE Database Query Service version 1.99 (HEREFORD) |
|
32
|
|
|
|
|
|
|
# |
|
33
|
|
|
|
|
|
|
# |
|
34
|
|
|
|
|
|
|
__PACKAGE__->attributes( 'primary', [ 'mntner' ] ); |
|
35
|
|
|
|
|
|
|
__PACKAGE__->attributes( 'mandatory', [ 'mntner', 'admin_c', 'upd_to', 'auth', 'mnt_by', 'source' ] ); |
|
36
|
|
|
|
|
|
|
__PACKAGE__->attributes( 'optional', [ 'descr', 'org', 'tech_c', 'mnt_nfy', 'remarks', 'notify', 'created', 'last_modified' ] ); |
|
37
|
|
|
|
|
|
|
__PACKAGE__->attributes( 'single', [ 'mntner', 'created', 'last_modified', 'source' ] ); |
|
38
|
|
|
|
|
|
|
__PACKAGE__->attributes( 'multiple', [ 'descr', 'org', 'admin_c', 'tech_c', 'upd_to', 'mnt_nfy', 'auth', 'remarks', 'notify', 'mnt_by' ] ); |
|
39
|
|
|
|
|
|
|
|
|
40
|
|
|
|
|
|
|
# End of auto-generated lines |
|
41
|
|
|
|
|
|
|
####################################################################################### |
|
42
|
|
|
|
|
|
|
|
|
43
|
|
|
|
|
|
|
=head1 NAME |
|
44
|
|
|
|
|
|
|
|
|
45
|
|
|
|
|
|
|
Net::Whois::Object::Mntner - an object representation of the RPSL Mntner block |
|
46
|
|
|
|
|
|
|
|
|
47
|
|
|
|
|
|
|
=head1 DESCRIPTION |
|
48
|
|
|
|
|
|
|
|
|
49
|
|
|
|
|
|
|
Objects in the RIPE Database may be protected using Mntner (pronounced |
|
50
|
|
|
|
|
|
|
"maintainer") objects. A Mntner object specifies authentication |
|
51
|
|
|
|
|
|
|
information required to authorise creation, deletion or modification |
|
52
|
|
|
|
|
|
|
of the objects protected by the Mntner. |
|
53
|
|
|
|
|
|
|
|
|
54
|
|
|
|
|
|
|
Objects are protected by a Mntner, if they contain a reference to the Mntner |
|
55
|
|
|
|
|
|
|
in the object. This is done by including a mnt-by attribute. Other |
|
56
|
|
|
|
|
|
|
attributes offer hierarchical protection. The mnt-by attribute is mandatory |
|
57
|
|
|
|
|
|
|
in all object types. Most users set the mnt-by value in a Mntner to |
|
58
|
|
|
|
|
|
|
reference itself. |
|
59
|
|
|
|
|
|
|
|
|
60
|
|
|
|
|
|
|
=head1 METHODS |
|
61
|
|
|
|
|
|
|
|
|
62
|
|
|
|
|
|
|
=head2 B |
|
63
|
|
|
|
|
|
|
|
|
64
|
|
|
|
|
|
|
Constructor for the Net::Whois::Object::Mntner class |
|
65
|
|
|
|
|
|
|
|
|
66
|
|
|
|
|
|
|
=cut |
|
67
|
|
|
|
|
|
|
|
|
68
|
|
|
|
|
|
|
sub new { |
|
69
|
1
|
|
|
1
|
1
|
5
|
my ( $class, @options ) = @_; |
|
70
|
|
|
|
|
|
|
|
|
71
|
1
|
|
|
|
|
3
|
my $self = bless {}, $class; |
|
72
|
1
|
|
|
|
|
12
|
$self->_init(@options); |
|
73
|
|
|
|
|
|
|
|
|
74
|
1
|
|
|
|
|
4
|
return $self; |
|
75
|
|
|
|
|
|
|
} |
|
76
|
|
|
|
|
|
|
|
|
77
|
|
|
|
|
|
|
=head2 B |
|
78
|
|
|
|
|
|
|
|
|
79
|
|
|
|
|
|
|
Accessor to the mntner attribute. |
|
80
|
|
|
|
|
|
|
Accepts an optional mntner value to be added to the mntner array, |
|
81
|
|
|
|
|
|
|
always return the current mntner. |
|
82
|
|
|
|
|
|
|
|
|
83
|
|
|
|
|
|
|
The unique name of a mntner object. APNIC recommends the following formats: |
|
84
|
|
|
|
|
|
|
|
|
85
|
|
|
|
|
|
|
Maintainer for resource registrations: |
|
86
|
|
|
|
|
|
|
|
|
87
|
|
|
|
|
|
|
-- |
|
88
|
|
|
|
|
|
|
|
|
89
|
|
|
|
|
|
|
EXAMPLE |
|
90
|
|
|
|
|
|
|
MAINT-WF-SPARKYNET |
|
91
|
|
|
|
|
|
|
|
|
92
|
|
|
|
|
|
|
=head2 B |
|
93
|
|
|
|
|
|
|
|
|
94
|
|
|
|
|
|
|
Accessor to the descr attribute. |
|
95
|
|
|
|
|
|
|
Accepts an optional descr line to be added to the descr array, |
|
96
|
|
|
|
|
|
|
always return the current descr array. |
|
97
|
|
|
|
|
|
|
|
|
98
|
|
|
|
|
|
|
A short description of the mntner object and the name of the organization |
|
99
|
|
|
|
|
|
|
associated with it. |
|
100
|
|
|
|
|
|
|
|
|
101
|
|
|
|
|
|
|
=head2 B |
|
102
|
|
|
|
|
|
|
|
|
103
|
|
|
|
|
|
|
Accessor to the org attribute. |
|
104
|
|
|
|
|
|
|
Accepts an optional org value to be added to the org array, |
|
105
|
|
|
|
|
|
|
always return the current org array. |
|
106
|
|
|
|
|
|
|
|
|
107
|
|
|
|
|
|
|
The organisation this object is bound to. |
|
108
|
|
|
|
|
|
|
|
|
109
|
|
|
|
|
|
|
=head2 B |
|
110
|
|
|
|
|
|
|
|
|
111
|
|
|
|
|
|
|
Accessor to the admin_c attribute. |
|
112
|
|
|
|
|
|
|
Accepts an optional contact to be added to the admin_c array, |
|
113
|
|
|
|
|
|
|
always return the current admin_c array. |
|
114
|
|
|
|
|
|
|
|
|
115
|
|
|
|
|
|
|
The NIC-handle of an on-site contact Person object. As more than one |
|
116
|
|
|
|
|
|
|
person often fulfills a role function, there may be more than one admin_c |
|
117
|
|
|
|
|
|
|
listed. |
|
118
|
|
|
|
|
|
|
|
|
119
|
|
|
|
|
|
|
An administrative contact (admin_c) must be someone who is |
|
120
|
|
|
|
|
|
|
physically located at the site of the network. |
|
121
|
|
|
|
|
|
|
|
|
122
|
|
|
|
|
|
|
=head2 B |
|
123
|
|
|
|
|
|
|
|
|
124
|
|
|
|
|
|
|
Accessor to the tech_c attribute. |
|
125
|
|
|
|
|
|
|
Accepts an optional contact to be added to the tech_c array, |
|
126
|
|
|
|
|
|
|
always return the current tech_c array. |
|
127
|
|
|
|
|
|
|
|
|
128
|
|
|
|
|
|
|
The NIC-handle of a technical contact Person or Role object. As more than |
|
129
|
|
|
|
|
|
|
one person often fulfills a role function, there may be more than one tech_c |
|
130
|
|
|
|
|
|
|
listed. |
|
131
|
|
|
|
|
|
|
|
|
132
|
|
|
|
|
|
|
A technical contact (tech_c) must be a person responsible for the |
|
133
|
|
|
|
|
|
|
day-to-day operation of the network, but does not need to be |
|
134
|
|
|
|
|
|
|
physically located at the site of the network. |
|
135
|
|
|
|
|
|
|
|
|
136
|
|
|
|
|
|
|
=head2 B |
|
137
|
|
|
|
|
|
|
|
|
138
|
|
|
|
|
|
|
Accessor to the upd_to attribute. |
|
139
|
|
|
|
|
|
|
Accepts an optional upd_to value to be added to the upd_to array, |
|
140
|
|
|
|
|
|
|
always return the current upd_to array. |
|
141
|
|
|
|
|
|
|
|
|
142
|
|
|
|
|
|
|
The upd_to attribute specifies the email address to be notified when an |
|
143
|
|
|
|
|
|
|
attempt to update an object protected by this Mntner is unsuccessful. |
|
144
|
|
|
|
|
|
|
|
|
145
|
|
|
|
|
|
|
=head2 B |
|
146
|
|
|
|
|
|
|
|
|
147
|
|
|
|
|
|
|
Accessor to the mnt_nfy attribute. |
|
148
|
|
|
|
|
|
|
Accepts an optional mnt_nfy value to be added to the mnt_nfy array, |
|
149
|
|
|
|
|
|
|
always return the current mnt_nfy array. |
|
150
|
|
|
|
|
|
|
|
|
151
|
|
|
|
|
|
|
The mnt_nfy attribute specifies the email address to be notified when an |
|
152
|
|
|
|
|
|
|
object protected by this Mntner is successfully updated. |
|
153
|
|
|
|
|
|
|
|
|
154
|
|
|
|
|
|
|
=head2 B |
|
155
|
|
|
|
|
|
|
|
|
156
|
|
|
|
|
|
|
Accessor to the auth attribute. |
|
157
|
|
|
|
|
|
|
Accepts an optional auth value to be added to the auth array, |
|
158
|
|
|
|
|
|
|
always return the current auth array. |
|
159
|
|
|
|
|
|
|
|
|
160
|
|
|
|
|
|
|
The auth attribute defines an authentication scheme to be used. . Any of |
|
161
|
|
|
|
|
|
|
the current authentication schemes used by the RIPE Database are allowed. |
|
162
|
|
|
|
|
|
|
|
|
163
|
|
|
|
|
|
|
=head2 B |
|
164
|
|
|
|
|
|
|
|
|
165
|
|
|
|
|
|
|
Accessor to the remarks attribute. |
|
166
|
|
|
|
|
|
|
Accepts an optional remark to be addedt to the remarks array, |
|
167
|
|
|
|
|
|
|
always return the current remarks array. |
|
168
|
|
|
|
|
|
|
|
|
169
|
|
|
|
|
|
|
General remarks. May include a URL or email address. |
|
170
|
|
|
|
|
|
|
|
|
171
|
|
|
|
|
|
|
=head2 B |
|
172
|
|
|
|
|
|
|
|
|
173
|
|
|
|
|
|
|
Accessor to the notify attribute. |
|
174
|
|
|
|
|
|
|
Accepts an optional notify value to be added to the notify array, |
|
175
|
|
|
|
|
|
|
always return the current notify array. |
|
176
|
|
|
|
|
|
|
|
|
177
|
|
|
|
|
|
|
The email address to which notifications of changes to this object should |
|
178
|
|
|
|
|
|
|
be sent. |
|
179
|
|
|
|
|
|
|
|
|
180
|
|
|
|
|
|
|
=head2 B |
|
181
|
|
|
|
|
|
|
|
|
182
|
|
|
|
|
|
|
Accessor to the mnt_by attribute. |
|
183
|
|
|
|
|
|
|
Accepts an optional mnt_by value to be added to the mnt_by array, |
|
184
|
|
|
|
|
|
|
always return the current mnt_by array. |
|
185
|
|
|
|
|
|
|
|
|
186
|
|
|
|
|
|
|
Lists a registered Mntner used to authorize and authenticate changes to |
|
187
|
|
|
|
|
|
|
this object. |
|
188
|
|
|
|
|
|
|
|
|
189
|
|
|
|
|
|
|
Most users set the mnt-by value in a Mntner to reference itself. |
|
190
|
|
|
|
|
|
|
|
|
191
|
|
|
|
|
|
|
=head2 B |
|
192
|
|
|
|
|
|
|
|
|
193
|
|
|
|
|
|
|
Accessor to the auth_override attribute. |
|
194
|
|
|
|
|
|
|
Accepts an optional auth_override, always return the current auth_override. |
|
195
|
|
|
|
|
|
|
|
|
196
|
|
|
|
|
|
|
Routing Policy System Security specification defines an auth_override attribute |
|
197
|
|
|
|
|
|
|
in the Mntner object template. Together with referral-by attribute, they allow |
|
198
|
|
|
|
|
|
|
for a Mntner to be modified if it becomes unresponsive. |
|
199
|
|
|
|
|
|
|
As this is not part of the core functionality of the RIPE Database, |
|
200
|
|
|
|
|
|
|
it has not been implemented in the current version of the database. |
|
201
|
|
|
|
|
|
|
|
|
202
|
|
|
|
|
|
|
=head2 B |
|
203
|
|
|
|
|
|
|
|
|
204
|
|
|
|
|
|
|
Accessor to the referral_by attribute. |
|
205
|
|
|
|
|
|
|
Accepts an optional referral_by, always return the current referral_by. |
|
206
|
|
|
|
|
|
|
|
|
207
|
|
|
|
|
|
|
Routing Policy System Security specification defines an auth_override attribute |
|
208
|
|
|
|
|
|
|
in the Mntner object template. Together with referral-by attribute, they allow |
|
209
|
|
|
|
|
|
|
for a Mntner to be modified if it becomes unresponsive. |
|
210
|
|
|
|
|
|
|
As this is not part of the core functionality of the RIPE Database, |
|
211
|
|
|
|
|
|
|
it has not been implemented in the current version of the database. |
|
212
|
|
|
|
|
|
|
|
|
213
|
|
|
|
|
|
|
=head2 B |
|
214
|
|
|
|
|
|
|
|
|
215
|
|
|
|
|
|
|
Accessor to the changed attribute. |
|
216
|
|
|
|
|
|
|
Accepts an optional changed value to be added to the changed array, |
|
217
|
|
|
|
|
|
|
always return the current changed array. |
|
218
|
|
|
|
|
|
|
|
|
219
|
|
|
|
|
|
|
The email address of who last updated the database object and the date it |
|
220
|
|
|
|
|
|
|
occurred. |
|
221
|
|
|
|
|
|
|
|
|
222
|
|
|
|
|
|
|
Every time a change is made to a database object, this attribute will show |
|
223
|
|
|
|
|
|
|
the email address of the person who made those changes. |
|
224
|
|
|
|
|
|
|
Please use the address format specified in RFC 822 - Standard for |
|
225
|
|
|
|
|
|
|
the Format of ARPA Internet Text Message and provide the date |
|
226
|
|
|
|
|
|
|
format using one of the following two formats: YYYYMMDD or YYMMDD. |
|
227
|
|
|
|
|
|
|
|
|
228
|
|
|
|
|
|
|
=head2 B |
|
229
|
|
|
|
|
|
|
|
|
230
|
|
|
|
|
|
|
Accessor to the source attribute. |
|
231
|
|
|
|
|
|
|
Accepts an optional source, always return the current source. |
|
232
|
|
|
|
|
|
|
|
|
233
|
|
|
|
|
|
|
The name of the database from which the data was obtained. |
|
234
|
|
|
|
|
|
|
|
|
235
|
|
|
|
|
|
|
=head2 B |
|
236
|
|
|
|
|
|
|
|
|
237
|
|
|
|
|
|
|
Accessor to the country attribute. |
|
238
|
|
|
|
|
|
|
Accepts an optional value, always return the current 'country'. |
|
239
|
|
|
|
|
|
|
Two letter ISO 3166 code of the country or economy where the admin-c is based. |
|
240
|
|
|
|
|
|
|
|
|
241
|
|
|
|
|
|
|
Please use UPPERCASE letters. |
|
242
|
|
|
|
|
|
|
|
|
243
|
|
|
|
|
|
|
=head2 B |
|
244
|
|
|
|
|
|
|
|
|
245
|
|
|
|
|
|
|
Accessor to the abuse_mailbox attribute. |
|
246
|
|
|
|
|
|
|
Accepts an optional abuse_mailbox value to be added to the abuse_mailbox array, |
|
247
|
|
|
|
|
|
|
always return the current abuse_mailbox array. |
|
248
|
|
|
|
|
|
|
|
|
249
|
|
|
|
|
|
|
=cut |
|
250
|
|
|
|
|
|
|
|
|
251
|
|
|
|
|
|
|
1; |