Hello,

I would be interested to know how traceroute from an IPv4 and IPV6 hosts
behind a CPE would work on 6rd in general and specifically with IPv4/IPv6
anycast addresses. I would be interested on actual details on source
addresses used for answers, what happens if different answers for the same
TTL traverse different BRs coming back based on the stateless nature, etc.

If there is an impact on the current way a client and an admin interprets
results, that should be documented.

Not sure if this was already discussed on the list. Given the widespread use
of traceroute as a diagnostic tool shouldn't at least some of these details
be covered on the draft?

In ds-lite there is a little discussion on that but given the stateful
nature of NAT that would be a different topic.

Regards,

Reinaldo


On 2/22/10 11:45 AM, "[email protected]" <[email protected]>
wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Softwires Working Group of the IETF.
> 
> 
> Title           : IPv6 via IPv4 Service Provider Networks "6rd"
> Author(s)       : M. Townsley, O. Troan
> Filename        : draft-ietf-softwire-ipv6-6rd-07.txt
> Pages           : 18
> Date            : 2010-02-22
> 
> This document specifies an automatic tunneling mechanism tailored to
> advance deployment of IPv6 to end users via a Service Provider's IPv4
> network infrastructure.  Key aspects include automatic IPv6 prefix
> delegation to sites, stateless operation, simple provisioning, and
> service which is equivalent to native IPv6 at the sites which are
> served by the mechanism.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-softwire-ipv6-6rd-07.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.

_______________________________________________
Softwires mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/softwires

Reply via email to