[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: IPv6 Host Configuration of Recursive DNS Server



Two points:

1) In the disadvantage of DHCPv6 section, you ought to mention that
there is a ensure that the DHCP server always returns an up-to-date
value for the address of the preferred recursive DNS server. In large
networks, this is not trivial: the notion of which server is closest
depends on routing configuration and on server status, all of which are
dynamic. In contrast, the anycast approach guarantees that the request
will reach the closest server.

2) In the unmanaged case, you wrongly assume that case C is "like case
A". In fact, it is more like case B: if a gateway provides IPv6
connectivity by managing tunnels, then it is also supposed to provide
access to a recursive DNS server.

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf
Of
> Jaehoon Paul Jeong
> Sent: Sunday, June 06, 2004 8:57 PM
> To: dnsop@lists.uoregon.edu
> Cc: V6OPS WG; DHC WG; IPv6 DNS Configuration; IPv6 WG
> Subject: Re: IPv6 Host Configuration of Recursive DNS Server
> 
> Hi all,
> 
> For 1 week, there have been no comments on our IPv6 DNS Configuraion.
>
http://www.adhoc.6ants.net/~paul/publications/ietf-internet-draft/draft-
> ietf-dnsop-ipv6-dns-configuration-00.txt
> 
> Does it mean that there is no problem about this draft and it is ok to
> request WGLC? :-)
> 
> Paul
> 
> ----- Original Message -----
> From: "Jaehoon Paul Jeong" <paul@etri.re.kr>
> To: <dnsop@lists.uoregon.edu>
> Cc: "IPv6 DNS Configuration" <dnsop-v6conf@nominum.com>
> Sent: Thursday, June 03, 2004 2:38 PM
> Subject: Re: IPv6 Host Configuration of Recursive DNS Server
> 
> 
> > There is some problem of  column alignment at our draft.
> > You can find a fixed version at the following site:
> >  http://www.adhoc.6ants.net/~paul/publications/ietf-internet-
> draft/draft-ietf-dnsop-ipv6-dns-configuration-00.txt
> >
> > Thanks.
> >
> > Paul
> >
> > ----- Original Message -----
> > From: "Jaehoon Paul Jeong" <paul@etri.re.kr>
> > To: <dnsop@lists.uoregon.edu>
> > Cc: "IPv6 DNS Configuration" <dnsop-v6conf@nominum.com>
> > Sent: Thursday, June 03, 2004 10:10 AM
> > Subject: IPv6 Host Configuration of Recursive DNS Server
> >
> >
> > > Hello DNSOP members,
> > >
> > > As you know, a new draft has been published for IPv6 Host
> Configuration of DNS Server Information Approaches:
> > >  http://www.ietf.org/internet-drafts/draft-ietf-dnsop-ipv6-dns-
> configuration-00.txt
> > >
> > > For a long time, DNS Discovery has been discussed at both IPv6 and
> DNSOP working groups.
> > > The long discussion seems to be resolved through this draft.
> > >
> > > In this draft, three approaches are suggested: (a) RA option, (b)
> DHCPv6 option, and
> > > (c) Well-known anycast addresses for Recursive DNS Servers.
> > > We, authors, used "DNS Configuration" instead of "DNS Discovery"
> because recursive DNS server address is
> > > only configured in IPv6 host, not generating DNS server address
like
> in IPv6 address autoconfiguration.
> > >
> > > This draft focuses on describing the attributes of three
approaches
> and suggesting four applicable scenarios:
> > > (a) ISP network, (b) Enterprise network, (c) 3GPP network, (d)
> Unmanaged network.
> > >
> > > Through your review and comments, this will be published as
> Informational RFC according to our milestones.
> > > IMHO, if necessary, the drafts of two other approaches except
DHCPv6
> option will be developed into separate RFCs.
> > >
> > > Thanks.
> > >
> > > Paul,
> > > IPv6 DNS Configuration Design Team.
> > >
> > > ------------------------------------------------------
> > > Jaehoon Paul Jeong (Research Engineer)
> > > TEL. +82-42-860-1664
> > > Mobile +82-16-711-1765
> > > 161 Gajeong-dong Yuseong-gu, Daejeon 305-350, Korea
> > > NGI Standardization Research Team/PEC/ETRI
> > > Homepage: http://www.adhoc.6ants.net/~paul
> > >
> >