Dear Troan, I suggest below information can be added for more clarity and extension of existing draft.
1) We are considering Service Provider gateway (6RD gateway) should directly connected to IPv6 internet. In this case, using ISATAP also we can achieve same. [Better to mention analysis on ISATAP comparision in specified scenario] 2) Handling in case of 6RD gateway is not connected with IPv6 internet (another tunnel can be required in this case, may be manual). Thanks and Regards Santhosh ****************************************************************************************** This email and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained here in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this email in error, please notify the sender by phone or email immediately and delete it! ***************************************************************************************** ----- Original Message ----- From: Ole Troan <[email protected]> Date: Thursday, February 4, 2010 0:00 am Subject: [Softwires] Fwd: I-D Action:draft-ietf-softwire-ipv6-6rd-04.txt To: [email protected], [email protected] > hi, > > we've just posted an updated revision of the 6rd draft, which we > believe is ready for last call in the softwires and dhc working > groupsl. > > apart from cleaning up text the main changes are in the DHCP option, > which now includes a list of BR IPv4 addresses. (I misread RFC3396 to > allow for multiple DHCP options as a way of doing this, unfortunately > not so with the format we had. thanks to the dhc wg expers for > correcting me.) > > we have also taken out all deployment considerations which were in the > revision 03 draft. if anyone is interested in taking that work up, it > could be a separate draft in v6ops. > > the complete diff-set is available here: > http://tools.ietf.org/rfcdiff?url2=draft-ietf-softwire-ipv6-6rd-04.txt > > Best regards, > Ole > > > > ---------- Forwarded message ---------- > From: <[email protected]> > Date: Wed, Feb 3, 2010 at 4:45 PM > Subject: [Softwires] I-D Action:draft-ietf-softwire-ipv6-6rd-04.txt > To: [email protected] > Cc: [email protected] > > > 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-04.txt > Pages : 16 > Date : 2010-02-03 > > 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- > 04.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 > _______________________________________________ > Softwires mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/softwires > _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
