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/dns-wg@ripe.net/
[dns-wg] WG Agenda for RIPE50
- Previous message (by thread): [dns-wg] WG Agenda for RIPE50
- Next message (by thread): [dns-wg] WG Agenda for RIPE50
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Koch
pk at DENIC.DE
Thu May 5 18:30:23 CEST 2005
Roy Arends wrote: > <proto police hat on> <protopolice division="internal affairs"> > There is no such thing as in-bailiwick glue or out of bailiwick glue. > > The term "GLUE RECORDS" is defined in rfc-1033 (yeah, dusted off): That's probably using illegal evidence, 1033 has no formal status. </protopolice> > If the name server host for a particular domain is itself inside the > domain, then a 'glue' record will be needed. A glue record is an A > (address) RR that specifies the address of the server. Glue records > are only needed in the server delegating the domain, not in the > domain itself. > > in-bailiwick glue is a pleonasm while out-of-bailiwick glue is an > oxymoron. There are different glue policies in place. DE is using a strict one (matching your definition above), while COM/NET apply a less strict (in fact IIRC even a combined one). The paragraph cited above is correct, but it doesn't limit glue to that case. But this is all only about differentiating between servers below the delegating or the delegated domain. The presentation is in fact about "trustworthy additional information". But let's wait until tomorrow ... -Peter
- Previous message (by thread): [dns-wg] WG Agenda for RIPE50
- Next message (by thread): [dns-wg] WG Agenda for RIPE50
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]