dns-wg

Download

dns-wg@ripe.net

July 2001

2 participants
2 discussions

WG: Update, NGtrans - DNSext joint meeting, call for participation
by Thomas Trede 24 Jul '01

24 Jul '01

FYI: I think this might also be important for the DNS-WG of RIPE. Regards, Thomas Trede -----Ursprungliche Nachricht----- Von: owner-ipng(a)sunroof.eng.sun.com [mailto:owner-ipng@sunroof.eng.sun.com]Im Auftrag von Alain Durand Gesendet: Freitag, 20. Juli 2001 22:24 An: ngtrans(a)sunroof.eng.sun.com; namedroppers(a)ops.ietf.org; ipng(a)sunroof.eng.sun.com; dnsop(a)cafax.se Cc: randy(a)psg.com; tony(a)tndh.net; fink(a)es.net; Olafur Gudmundsson Betreff: Update, NGtrans - DNSext joint meeting, call for participation Correction on the previous announcement: The NGtrans/DNSext chairs would like to make a call for participation in the upcoming joint meeting. The goal of the meeting is to facilitate consensus on how IPv6 addresses are represented in DNS and related issues. This meeting requires extensive homework by participants and the chairs would like to request submission of documents for a reading list for this meeting. The output from the meeting will be draft consensus proposal. Here is non exclusive a list of relevant topics: 1 - Design tradeoffs in DNS and IPv6 (AAAA, A6, DNAME, bit string) - DNS operational considerations including DNSSEC costs in regard of address record format - DNS implementation complications due to address record format - IPv6 Remembering requirements and impact on address record format - Case for A6 - Case for AAAA - transition from ip6.int to ip6.arpa - transition from AAAA to A6 2 - tools/protocols/strategies to bridge IPv6 and IPv4 DNS resolution Anybody wishing to make a presentation should send a draft to the chairs of this meeting before July 26th 2001, 21:00 UTC (that is, 2pm PDT, 5pm EDT, 11pm MEST) - Randy Bush <randy(a)psg.com> - Alain Durand <alain.durand(a)sun.com> - Bob Fink <fink(a)es.net> - Olafur Gudmundsson <ogud(a)ogud.com> - Tony Hain <tony(a)tndh.net> Drafts not yet published by the ID editor are acceptable contributions (please include an URL). The chairs will review the list of submission, derived the actual agenda of the meeting from it and send all reading materials to the DNSext and NGtrans mailing list no later than July 27th, 21:00 UTC. The format of the meeting is going to be: - Short summary of the discussion points from the documents - Technical discussion on the relevance of the points - Technical discussion on the points from documents as measured by Rob Austein's document draft-ietf-dnsext-ipv6-dns-tradeoffs-00.txt - Brainstorming on the best way to go forward - Straw polls leading to consensus building on a plan of action - the chairs. -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to majordomo(a)sunroof.eng.sun.com --------------------------------------------------------------------

1 0

Fwd: IN-ADDR.ARPA Progress Report
by Joao Luis Silva Damas 02 Jul '01

02 Jul '01

Dear all, here I forward an announcement from ARIN regarding current progress in the maintainance of the in-addr.arpa zone. Best regards, Joao Damas RIPE NCC >From: ARIN IN-ADDR Role <inaddr(a)arin.net> >Subject: IN-ADDR.ARPA Progress Report >Message-ID: <Pine.SOL.4.05.10106291525050.10191-100000(a)ops.arin.net> > >Goal: > >Reduce the size of the IN-ADDR.ARPA zone file. This file will be reduced >in size by only containing name servers for /8 networks. > > >Completed Steps: > >Apr 2001 - Established relationships with 2 companies to provide >independent server networks for all ARIN IN-ADDR zone files. > >Jun 2001 - Released a new IN-ADDR.ARPA zone file generator to correct >existing erroneous data. > > >Next Step: > >July 9, 2001 - ARIN will begin revising the IN-ADDR.ARPA zone for those >direct /8 delegations to ARIN. These /8 zone files will be serviced by >the two ARIN nameserver networks. These changes will not affect the >performance of reverse lookup in any of the IPv4 Address space. > >Please direct any questions to inaddr(a)arin.net. > > >Ginny Listman >Director of Engineering >American Registry for Internet Numbers --

1 0