> > George Eddy writes :
> >From eddy(a)ISI.EDU Thu Feb 22 22:12:26 1996
> Date: Thu, 22 Feb 96 13:07:22 PST
> Posted-Date: Thu, 22 Feb 96 13:07:22 PST
> Message-Id: <9602222107.AA16189(a)kit.isi.edu>
> From: George Eddy <eddy(a)ISI.EDU>
> To: rps(a)ISI.EDU
> Subject: Internet Draft Submission
> Geographic Location Extension to Ripe-181
> 3.2 Direct and Indirect Location
>
> This method proposes the addition of a ``location'' attribute to the
> aut-num as in 3.1. This attribute could directly hold the LocString, or
> the name of a ``location'' object. The location object could be defined
> as:
>
> location: [mandatory] [single]
> loc-string: [mandatory] [single]
> descr: [optional] [multiple]
> notify: [optional] [multiple]
> mnt-by: [optional] [multiple]
> changed: [mandatory] [multiple]
> source: [mandatory] [single]
>
> Using the example in section 3.1, we would have the following:
>
> aut-num: AS8800
> location: IrvineCA
> ...
>
> and the object ``IrvineCA'' would be:
>
> location: IrvineCA
> loc-string: 33 40 10n 117 49 20w 10m
> descr: Example location object in Irvine, CA.
> notify: eddy(a)isi.edu
> mnt-by: MAINT-EXAMPLE
> changed: eddy(a)isi.edu 960220
> source: EXAMPLE
>
> The loc-name could be any string desired by the creator.
Dear Eddy,
Can two or more AS-es share the same location object?
How to coordinate the loc-name assignments. In Europe tipically there
are more then one AS within the same city. They will race
for the simple name of the city. Just like for domain names. :-/
Maybe the RIPE predefine location objects for the main cities.
Regards
Gabor