This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/bcop@ripe.net/
[bcop] [BCOP-discuss] Content Providers and IPv6
- Previous message (by thread): [bcop] [BCOP-discuss] Content Providers and IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Chris Grundemann
cgrundemann at gmail.com
Tue Nov 26 00:37:53 CET 2013
On Sun, Nov 24, 2013 at 4:35 PM, Howard, Lee <lee.howard at twcable.com> wrote: > This might be useful: > https://ietf.org/doc/draft-ietf-v6ops-dc-ipv6/ > It wouldn't hurt to ask the authors if they could contribute, too. > Thanks Lee! This one's on my required reading list too: http://tools.ietf.org/html/rfc6883 ~Chris > > Lee > > From: Chris Grundemann <cgrundemann at gmail.com> > Date: Saturday, November 23, 2013 1:37 PM > To: "bcop at nanog.org" <bcop at nanog.org>, "bcop at ripe.net" <bcop at ripe.net> > Subject: [BCOP-discuss] Content Providers and IPv6 > > Hail BCOPers! > > I've had quite a bit of interest from several folks in BCOPs for > deploying IPv6 at a content provider. Who has experience in this realm? We > need a few SMEs with real experience to put this together. Please respond > if you are interested and I'll help organize the effort. > > CDNs are another (subset) area to look into as well - calling all SMEs... > > Thanks! > ~Chris > > -- > @ChrisGrundemann > http://chrisgrundemann.com > > > ------------------------------ > This E-mail and any of its attachments may contain Time Warner Cable > proprietary information, which is privileged, confidential, or subject to > copyright belonging to Time Warner Cable. This E-mail is intended solely > for the use of the individual or entity to which it is addressed. If you > are not the intended recipient of this E-mail, you are hereby notified that > any dissemination, distribution, copying, or action taken in relation to > the contents of and attachments to this E-mail is strictly prohibited and > may be unlawful. If you have received this E-mail in error, please notify > the sender immediately and permanently delete the original and any copy of > this E-mail and any printout. > -- @ChrisGrundemann http://chrisgrundemann.com -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/bcop/attachments/20131125/7371d215/attachment.html>
- Previous message (by thread): [bcop] [BCOP-discuss] Content Providers and IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ BCOP Archives ]