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]/
RIPE-26, DB-WG, Proposed Agenda, 2nd Draft
- Previous message (by thread): RIPE-26, DB-WG, Proposed Agenda, 2nd Draft
- Next message (by thread): RIPE-26, DB-WG, Proposed Agenda, 2nd Draft
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
davidk at isi.edu
davidk at isi.edu
Wed Jan 15 19:41:07 CET 1997
Chris, > Chris Fletcher writes : > > David Kessens writes : > > - loc-string: <LocatianString> > > > > LocationString contains the coordinates of the IPv6 sites location. > > Multiple location strings can be proovided on different lines for sites > > that have multiple locations in the area. > > > > Syntax: > > > > Somebody can give me a pointer for the RFC standard > > > > Example (for now): > > > > loc-string: 33 40 10n 117 49 20w 10m > > The DNS LOC RR is defined in RFC1876. Thanks. It seems that I now have two pointers (somebody at the 6bone list gave me a pointer to RFC1712) to two different RFCs that do something simular but not exactly the same :-(. However, it looks like RFC1876 is a better choice ... David K. ---
- Previous message (by thread): RIPE-26, DB-WG, Proposed Agenda, 2nd Draft
- Next message (by thread): RIPE-26, DB-WG, Proposed Agenda, 2nd Draft
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]