Hi all,
FYI, Today, I submitted sa46t-as, Stateless Automatic IPv4 over IPv6
Tunneling with IPv4 Address Sharing.
http://tools.ietf.org/html/draft-matsuhira-sa46t-as-00.html
Basically, this idea is the same as sa46t, and easily support IPv4
Address sharing function adding port number into the
Dear Alain, all,
In addition to the technical reasons mentioned in previous e-mails, I
would like to raise that operational issues should be also taken
into account for the provisioning of the DS-Lite AFTR reachability
information. In particular, we are considering two levels of
We've had a lot of discussion about how the FQDN might be used, perhaps in
conjunction with the contents of other options, to provision a device with the
IP address of ds-lite tunnel endpoint. I don't think I've seen formal I-D text
that specifies, for example, the two levels of indirection
On Oct 18, 2010, at 8:06 AM, mohamed.boucad...@orange-ftgroup.com
mohamed.boucad...@orange-ftgroup.com wrote:
In addition to the technical reasons mentioned in previous e-mails, I
I'm sorry, I must have missed that email. I saw a lot of talk about how the
WG consensus was for the FQDN
Hi Alain and Dave,
My we request a time slot for the below work?
https://datatracker.ietf.org/doc/draft-tsou-softwire-gwinit-6rd/
Time: 15 mins
Presenter: Tina Tsou
Thanks. Have a nice week.
Best Regards,
Qi, Cathy, Tom and Tina
http://tinatsou.weebly.com/contact.html
-Original
Hi Brain,
Brian E Carpenter 2010-10-16 Wrote:
On 2010-10-16 15:15, Dong Zhang wrote:
Hi Remi,
Please see inline.
...
Is the A:W-N:Z mapping created staticly? Or dynimicly?
Dynamically when the 6a44-C starts operation.
It then remains static until the 6a44 client or the NAT is reset.
That
A new version of I-D, draft-xu-softwire-mesh-multicast-00.txt has been
submitted
(http://tools.ietf.org/html/draft-xu-softwire-mesh-multicast-00).
Your comments are appreciated.
Abstract:
The Internet will need to support IPv4 and IPv6 packets. Both
address families and their attendent
