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): hierarchical route objects, part 1

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Geert Jan de Groot GeertJan.deGroot at ripe.net
Wed Jan 15 21:04:45 CET 1997

On Wed, 15 Jan 1997 10:41:07 -0800 (PST)  davidk at isi.edu wrote:
> > > - loc-string: <LocatianString>
> > 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 ...

Actually, I stole what I found in an RPS draft, hoping that it would
be compatible with other developments.

However, the draft involved is gone and I don't see this listed
in the latest RPS draft.

I guess we should pick one of the 'existing' standards and stick with it.

This is yet another good reason not to refer to stuff in internet-drafts..

Geert Jan

Previous message (by thread): RIPE-26, DB-WG, Proposed Agenda, 2nd Draft
Next message (by thread): hierarchical route objects, part 1

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]