Ole, I just noted that the reference to RFC 5569, that Mark noted when I last met with him, has been missed in the first sentence, and in the acknowledgements section.
The sentence he had agreed on was: "The original idea and the name of the mechanism (6rd) specified in this document is described in [RFC 5569], a recommended background reading which details a successful commercial "rapid deployment" of the 6rd. Is it possible to have this sentence back in? Nothing else noted (at least after a first glance). Best regards, RD Le 3 févr. 2010 à 16:59, Ole Troan a écrit : > 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
