RE: PPP ext for IPv6 dns address
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: PPP ext for IPv6 dns address
Hi,
This is a very good question, more details can be found in this draft
that is currently in RFC Ed. queue:
http://www.ietf.org/internet-drafts/draft-ietf-dnsop-ipv6-dns-configurat
ion-06.txt
Also see: RA-based mechanism (personal submission):
http://www.ietf.org/internet-drafts/draft-jeong-dnsop-ipv6-dns-discovery
-05.txt
Furthermore, many OS'es (e.g. Symbian, according to my understanding
also Microsoft, ...) implement well-known site-local addresses (as a
last resort mechanism) for IPv6 DNS discovery, see e.g.:
http://www.tahi.org/conformance/ct-profile-host/dd/DDWellKnown.html
fec0:000:0000:ffff::1
fec0:000:0000:ffff::2
fec0:000:0000:ffff::3
This is the expired draft:
http://www.ietf.org/proceedings/03mar/I-D/draft-ietf-ipv6-dns-discovery-
07.txt
BR,
Juha Wiljakka
________________________________
From: ipv6-bounces at ietf.org [mailto:ipv6-bounces at ietf.org] On
Behalf Of ext Vincent Lubet
Sent: 12 September, 2005 21:59
To: Tiago Duarte (Ext_PDM&FC LDA)
Cc: ipv6 at ietf.org
Subject: Re: PPP ext for IPv6 dns address
On Sep 12, 2005, at 11:37 AM, Tiago Duarte (Ext_PDM&FC LDA)
wrote:
I was looking into the RFCs for the PPP extension that
allow the server to include IPv6 DNS addresses on the PPP response.
I found out that there was a draft,
draft-ietf-pppext-ipv6-dns-addr-01.txt, that proposes this option. But
this draft was droped.
Is there any solution to pass DNS addresses to the
client without using DHCPv6? Is there any option for PPP that could be
used?
You should be able to use neighbor discovery on the PPP link
although it's not as simple as using IPV6CP.
Vincent
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 at ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.