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]/
NIC handle writeup
- Previous message (by thread): NIC handle writeup
- Next message (by thread): NIC handle writeup
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Joe Abley
jabley at clear.co.nz
Thu Sep 24 11:40:21 CEST 1998
On Thu, Sep 24, 1998 at 09:24:32AM +0000, David Kessens wrote: > > Example > > example: KH1 at ARIN.NET > > KH1 is local identifier ARIN.NET is global registry identifier (last > part of domain name can possibly be omitted) I would suggest that KH1 at ARIN is less confusing than KH1 at ARIN.NET, unless e-mail to kh1 at arin.net will actually be forwarded to the appropriate real e-mail address of kh1. I presume this will not be the case, since the registries are not in the business of forwarding mail. Using the whole domain name would help scripts identify appropriate resources for queries (e.g. whois.ARIN.NET in this example), but since we seem to be moving towards every registry mirroring every other registry, this seems less important. Either way, it seems important to standardise on one or the other. The InterNIC assigned me JA39 a long time ago, and I continue to use it in the APNIC registry. What should this be now? JA39 at APNIC.NET? JA39 at INTERNIC.NET? I think these migration issues deserve further treatment. My $0.02, Joe -- Joe Abley <jabley at clear.co.nz> Tel +64 9 912-4065, Fax +64 9 912-5008 Network Architect, CLEAR Net http://www.clear.net.nz/
- Previous message (by thread): NIC handle writeup
- Next message (by thread): NIC handle writeup
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]