Dan York

Just a guy in Vermont trying to connect all the dots...

Author's posts

Images/Photos Alone Do Not Make A Content Strategy

Thisisnotacontentstrategy

Credit: C.C. Chapman

Lately, it seems, the social media world is all abuzz about "images" in various forms. Photos, pictures... Instagram... Pinterest... infographics... plus Twitter, Facebook and Google+ all enhancing their capability to handle photos... and now this intense fascination with posting images with words and sayings on top of them!

I get it. I do. Visual storytelling is incredibly powerful. Evocative. Inspirational. Images and photos can transcend words and cut right to the emotional core of an issue. I personally enjoy photography, and you can usually find me shooting photos at events I attend. I'm sharing photos all the time into Facebook, Twitter, Google+, etc.

But...

... lately we seem to be seeing in the corporate PR / marketing / social media space a really severe case of "bright shiny object" syndrome. All over the place... large enterprises, small startups... and everyone in between.

Oooo... let's post a bunch of photos to Instagram because we'll look hip and cool! Hey, clearly we need to be pinning all the photos we can to Pinterest boards, because "everyone" is doing it! Hey, look, another new mobile app that lets us do _____ with our photos - cool! Wow, look how cool we are because we can post a photo with some pithy quote written on top of it in a funky font! And let's not even jump into the cesspool of poorly done infographics...

All of this without answering a fundamental question:

WHY?

WHY are you posting those images? Why are you using that service? How do the images help communicate your message to your audiences? How do they help get your message out? How do they facilitate sharing? How does posting the images to ______ increase your interaction with your audiences?

Now, don't get me wrong... experimentation is awesome and necessary. And I'm the last one to talk about chasing bright shiny objects... that's what I love to do (and in fact write about). Experimentation is really required if you are going to stay on top of the insane pace of new products and services appearing on a daily basis. But there is a difference between experimentation and trumpeting the fact that you are now using these services, as if the use of those services will somehow make you cooler and help you communicate better.

They might help you communicate better, and you won't know unless you experiment... but as you experiment you need to think about the why.

Ultimately these services are all tactics that need to line up with a larger strategy.

Why are you using them? Why are you posting the images you choose to post?

Do the images help educate your audiences about your products? your mission? your services?
Do they help humanize your organization and show a more personal side? or show the people behind the name?
Do they entertain or amuse people and help build your community?
Do they inspire people because of how beautiful or artistic they are?
Do they promote your brand name or social account? Will you gain more followers/fans/etc?

How does posting images to service X fit within your larger strategy? Now, maybe you are posting that LOLcat image purely as link-bait to build your followers... that's okay, just call it what it is. And this doesn't mean that every image needs to be serious and "on message" - images can certainly be posted "for fun"... and maybe that's one of the purposes they serve.

The point is that some conscious thought needs to be given to the use of images and the use of the various services... rather than just doing it "because everyone is doing it"!

As I was thinking about this, a trio of posts yesterday on this precise topic caught my eye:

First, in "Pictures With Words", C.C. Chapman provides this awesome photo that I've included here and hits the point:

If your brand is thinking about diving into this because everyone is doing it, remember that it is a tactic and not a strategy. Where does it fit into your other marketing programs and what can you do with this trend that is unique and relavent to your business? Always ask why before you do anything. Make sure it is a fit and that you are not doing it simply because everyone else is. Following the herd rarely gets you noticed.

We as a society love shiny new toys and are scared of doing the grunt work. We see other people doing things, so we have to do them. If there is a shortcut that looks like it’ll make things easier we take it.

Exactly!

Second, in "The Rise of the Junkweb and Why It’s Awesome or At Least Inevitable", Chris Brogan talks about this new love of images as the "junkweb":

It’s the Junkweb. Why “junk?” Because the original intent of the Internet was that links were gold, that searchability was key, that this ability to find anything and use resources from wherever was magic. And this new web? The web of pictures with text over them? They’re junk. They’re a dead end. The picture is the payload. They don’t lead you elsewhere. They are the stopping point, the cul de sac.

But goes on to say that maybe this is okay in our new world and that the new tools we have access to have in fact made it easier for anyone to participate and share. He concludes offering three suggestions for people to engage in the "junkweb":

1. Make interesting graphics worth sharing.
2. Make it easy to share them.
3. Evoke an emotion.

And for Chris the "why" is because this world of sharing images is where the sharing and interaction happen between "regular" people and thus is worth investigating. Good article and, as with many of Chris' posts, the comment stream is well worth a read, too.

Finally, in his AdAge column titled "The Revolution Won't Be Televised; It Will Be Instagrammed" and subtitled "Businesses That Bank on Photographic Storytelling Will Win", Steve Rubel discusses why businesses should pay attention to what is going on with the rise of visual storytelling through photography. Inadvertently aligning with Chris Brogan's "junkweb", he writes:

Visual storytelling today is blissfully cliche. Photos are deliberately over animated, over filtered and even over exposed. They ignore all the rules. Just as the proliferation of texting arguably made the written word less formal and YouTube did the same for video, the ubiquity of smartphones has changed the expectations of what's considered "good" photography.

On this last sentence my professional photography friends can definitely agree! Steve goes on to basically offer suggestions for people involved with advertising to get involved with this space. Earlier in the article, too, he makes some interesting points with regard to why photos will be more important that videos, particularly with regard to mobile devices.

He doesn't touch on the "why", though, beyond the fact that this is the "new normal" and businesses need to be embracing it.

Which goes back to my original points... WHY are you embracing the use of images? Or perhaps more HOW are you going to embrace them? How does it help you?

Are you asking these questions?


If you found this post interesting or useful, please consider either:


Have You Checked Out This Online IPv6 Training?

Are you looking to learn what IPv6 is all about?  Would you like to understand the basics of how IPv6 addresses work?  If so, the 6Deploy project has put some great video tutorials online at:

http://www.6deploy.eu/e-learning/english/

As we mention on our resource page about the training, the seven sections of the course cover the basics of IPv6, the construction of IPv6 addresses and headers, security issues, mobility/routing issues and suggestions for co-existence with IPv4.  If you have a few minutes to watch these videos, you may find them a quick way to start your learning about IPv6:

6DEPLOY training

P.S. The 6Deploy project also has a great set of IPv6 tutorials that you may find helpful.

 

Have You Checked Out This Online IPv6 Training?

Are you looking to learn what IPv6 is all about?  Would you like to understand the basics of how IPv6 addresses work?  If so, the 6Deploy project has put some great video tutorials online at:

http://www.6deploy.eu/e-learning/english/

As we mention on our resource page about the training, the seven sections of the course cover the basics of IPv6, the construction of IPv6 addresses and headers, security issues, mobility/routing issues and suggestions for co-existence with IPv4.  If you have a few minutes to watch these videos, you may find them a quick way to start your learning about IPv6:

6DEPLOY training

P.S. The 6Deploy project also has a great set of IPv6 tutorials that you may find helpful.

The post Have You Checked Out This Online IPv6 Training? appeared first on Internet Society.

Netflix Provides Excellent Technical Details Behind IPv6 Streaming Rollout

Yesterday over on the Netflix Tech Blog,  Rajiv Aggarwal and David Temkin provided an excellent view into how they enabled IPv6 support for Netflix’s video streaming.

A couple of points in the article are worth calling out. First, they encountered an issue with the immaturity of some IPv6 code:

 We found a reference leak in the IPv6 code that wasn’t apparent until you had processed 2^32 packets. Once this counter rolled over it would free active memory and cause the panic.  Because we process large amounts of traffic we noticed this almost immediately.

These are the type of “growing pains” that we should expect to see as more and more production services move over into IPv6.  Much of the IPv6-related code out there has been developed and extensively tested… but not necessarily in all the cases that actual production usage will expose.

Their rollout strategy was also interesting, in that it provided them a way to slowly ease into providing full deployment with an easy way to revert should a problem arise:

Our DNS provider enables us to resolve hostnames based on the geo-location of the caller.  We used this during testing and rollout of IPv6 by starting with a specific geographic region and then expanding.  We started with the state of California and monitored metrics for requests coming to us via IPv4 vs. IPv6.  We specifically looked for any significant dips in IPv4 traffic that wasn’t accounted for in new IPv6 traffic. In addition, we watched to see if requests arriving via IPv6 were failing in similar or different ways than those via IPv4.

As they note in the post, this DNS-based solution didn’t work perfectly, but it worked well enough for them to be able to accomplish a successful rollout.

The end result is that per at least one study they now have the second largest domain taking IPv6 traffic!

Congratulations to the entire Netflix team – and thank you, too, for providing this technical report!

Two Years Ago This Week, The Root Zone of DNS Was Signed With DNSSEC

Via a tweet from the ICANN DNS Ops team this morning, we were reminded that it was two years ago this week when the root zone of DNS was signed with DNSSEC and we could start validating the global “chain of trust” from the very beginning of the DNS tree.

As noted on www.root-dnssec.org, the timeline for the final signing of the root occurred over a one-month period:

  • June 16, 2010 – First key signing ceremony at the ICANN data center in Culpeper, Virginia.
  • July 12, 2010 – Second key signing ceremony at the ICANN data center in El Segundo, California.
  • July 15, 2010 – The signed root zone was publicly available.

Once the signed root zone was published on July 15, 2010, it made possible all the DNSSEC validation and usage that we are able to do today using the full global chain of trust.

For those interested in what was happening behind the scenes and the intense amount of security put in place around the key ceremonies, the annotated scripts for Ceremony 1 (June 16) and Ceremony 2 (July 12) make for an interesting view into the process.  The “script exceptions” at the end of each document, in particular, show the human side of the process and that even with the best of preparations sometimes things go wrong.  All in all a rather complete and interesting process.

Congratulations to all involved in the key signing two years ago! (Many of whose names appear regularly in our DNSSEC resources or DNSSEC-related blog posts.)

 

 

US Government Releases Updated IPv6 Roadmap

Last week the US Federal CIO Council released an updated version of their IPv6 planning guide/roadmap. Available as a PDF download from cio.gov, the 73-page document provides a wealth of IPv6 information to both US government agencies and also to operators, enterprises and others seeking to understand exactly what the US government is doing with IPv6.

This July 2012 document updates and replaces the 2009 version of the roadmap.  It does not specifically list what has been updated, but provides this note:

This document is the latest version of the Roadmap, and is the key guidance document for supporting Federal agencies in their achievement of the 2012 and 2014 objectives, as well as the strategic vision for beyond 2014. This document has the same foundational elements instituted in the original Roadmap, and has been updated to reflect the three years of experience (from both the public and private sectors) since original publication. The sections of the document comprise all aspects of a successful transition and now include practical experience from those directly engaged in IPv6 activities, combining programmatic (including Clinger-Cohen Act compliance), technical, cybersecurity, and Federal acquisition elements, as well as the suggested interactions with other Federally mandated technical efforts such as the Trusted Internet Connection (TIC).

True to that statement, updated references can be found throughout the document.  I found it particularly interesting to see section 1.4, “Our Business Situation,” at the beginning of the document that provided a list from a competitive point of view of what other countries around the world are doing with regard to IPv6.

The sample transition timelines starting at the bottom of page 12 may be of interest to many readers, as they lay out examples of how agencies can meet upcoming September 2012 and September 2014 deadlines. Section 4 on page 22 also outlines where US federal agencies should be in 2012 and 2014.

Readers may also find Section 6 on page 32 very useful with the ideas for transition steps. Obviously, some steps are specific to US government agencies, but the ideas behind those steps could be equally useful in other context.

All in all a very useful document for US government agencies and for others seeking to understand what a large entity needs to do to make the transition.

How To Write A DNSSEC Practice Statement (DPS)

Are you planning to start using DNSSEC with your domain – and are you planning to start signing your domain yourself? In other words, are you going to be doing all the signing on your own server and/or in your own facilities?  (Versus using a service at a DNS hosting provider that does all the DNSSEC-signing for you.)

If you are, then a good place to start your planning is with the creation of what is called a “DNSSEC Practice Statement” or more simply a “DPS”.  A DPS is a document that outlines how you are implementing DNSSEC for your domain – and what security measures you are putting in place.

Basically, it is a statement that can help other people understand whether they can trust the security you put in place.

Typically the DPS documents created so far are for Top-Level Domains (TLDs) as they have been the focus of much of the DNSSEC deployment efforts to date.  For second-level domains, very often you may be able to use the services of your DNS hosting provider to sign your domains and so a full DPS may not be needed. But if you sign your own domain, a DPS can be a useful way to plan out the security for your signing.

Regardless of what you do, the existing DPS documents make for great reading to help you understand the security you may or may not need to put in place to ensure the security and integrity of our DNSSEC operations.

The place to begin for many of you may be to take a look at this Internet-Draft that explains the rationale for creating a DPS and provides a sample framework:

http://tools.ietf.org/html/draft-ietf-dnsop-dnssec-dps-framework

Some of you who like to simply dive into examples to see how a DPS is written may want to start looking through the examples we’ve added to this page:

DNSSEC Practice Statements

In particular you may want to start with the “.SE” DPS as the folks from .SE have been very involved with creating the entire DPS framework.  As you look through the examples, you’ll see a variety of different styles and lengths, from the very simple to the very complex.

If you have 15 minutes to spare, this video from 2010 offers Anne-Marie Eklund-Löwinder from .SE explaining the value of a DPS and what should be included:

The important aspect of a DNSSEC Practice Statement is to capture in one document how you are implementing DNSSEC and how you are securing the tools, servers and other components involved with DNSSEC.  Even if you are an enterprise who might never publicly publish a DPS, writing such a document can be a very useful exercise to ensure you are planning for all the necessary aspects of using DNSSEC to sign your domain.

P.S. If you create and publish a DPS, we’re always looking for more examples to add to our DPS page. Please let us know where your DPS is located online so that we can consider adding it to the page.

LAST DAY To Participate in 3rd Annual IPv6 Deployment Survey

NRO logoAs we’ve mentioned previously, today is the last day to let your voice be heard in the 3rd annual “IPv6 Deployment Monitoring Survey” on the current and future use of IPv6. The survey is at:

https://www.surveymonkey.com/s/GlobalIPv6survey2012

It will take just a few minutes and will go far in helping the the Number Resource Organization (NRO) (an umbrella organization for the 5 Regional Internet Registries) understand how the Internet community is moving toward widespread adoption of IPv6.

If you have IPv6 deployed in your network and can spare those few minutes, it will help all of us!

Thanks!

DNSSEC Policy & Practice Statements (DPS)

Are you responsible for signing your domain with DNSSEC are are looking to understand more of what may be involved?  Are you perhaps with registry or top-level domain (TLD) operator looking to implement DNSSEC across your country-code TLD (ccTLD) or new generic TLD (gTLD)? Or are you with an enterprise seeking to understand the legal and security policies you should have in place if you are signing your own domains?

If so, a great place to start is with the idea of a “DNSSEC Practice Statement” or “DPS.”  A DPS is a document that simply lays out the policies and procedures related to DNSSEC that an organization chooses to implement.  It may be very short and simple – or very long and complex.  The idea is that a DPS can give other people an understanding of how much they can trust your DNSSEC signing.  For someone new to DNSSEC, looking at existing DPS documents can also provide a clear checklist of what you should be thinking about during your implementation.

The best way to get started may be to look at an Internet-Draft titled “A Framework for DNSSEC Policies and DNSSEC Practice Statements”

http://tools.ietf.org/html/draft-ietf-dnsop-dnssec-dps-framework

This document explains the rationale for a DPS and provides a framework for creating your own.

Alternatively, you may just want to dive into the list of DPS documents below to get an understanding of what these documents are like.  The .SE DPS may be a good place to start, primarily because the .SE team are very involved with the Internet-Draft framework document referenced above.

If you prefer to learn from a video, we have included at the end of this page a 15-minute video from training given by the OpenDNSSEC project in April 2010 where Anne-Marie Eklund-Löwinder from .SE explains the value of a DPS and the components that should be included.

A few notes about the lists below:

  • The lists contain the gTLDs, ccTLDS and RIRs for whom we can find formal DPS documents. Some of the gTLDs, ccTLDs and RIRs who do use DNSSEC are not listed because their domains/zones were signed very early in the DNSSEC rollout before the DPS framework started to become widely used. They may have other DNSSEC deployment information on their sites, but not in the form of a formal DPS.
  • The root of DNS also has multiple DPS documents but they are not explicitly listed below as the root zone is a special case with special precautions. You may find the documents to be an interesting read, though.
  • You will note in the list below that the DPS documents have several different names, but newer documents seem to be standardizing on “DNSSEC Practice Statement.”
  • These lists will continue to be updated as more DPS documents become available. Expect to see them continue to grow as more TLDs sign their domains.

If you are aware of a DPS document we should include, please let us know.


Generic Top-Level Domains (gTLDs):


Country-code Top-Level Domains (ccTLDs):


Regional Internet Registries (responsible for reverse DNS delegations, i.e. in-addr.arpa):


The video below, while from 2010, provides a good introduction to what a DPS is all about:

 

Oracle Buys Facebook-App-Maker Involver

Oracle buys involverIn an intriguing development today, Oracle announced that it will be acquiring Involver, a startup with a platform to help you rapidly build Facebook apps that work with your Facebook Pages.

I first experimented with Involver a year or two ago when I was trying to add some interactivity to a Facebook Page for my previous employer. Involver had some useful options and while the fit wasn't there with what I wanted to do, I did keep monitoring how they were evolving.

No terms of the deal were announced, although TechCrunch is naturally continuing to try to determine the cost. The TechCrunch piece also has some more information about other ways Involver has been used.

How does Involver fit with Oracle? As both the TechCrunch article and a Business Insider article note, Oracle just recently acquired Vitrue, another social media marketing/engagement platform and has made a number of other acquisitions in the "social" space. For their part, Oracle has published a presentation about Involver that shows Oracle's view of how all the pieces fit together:

Oracle and involver

Time will tell if the pieces do all fit nicely together, but in the meantime Oracle is clearly looking to be a player in helping enterprises connect with their customers over social channels.

Congrats to the Involver team and I do hope this all works out well for them - and for their customers.

P.S. Involver's Don Beck published a blog post providing their viewpoint on the acquisition.


If you found this post interesting or useful, please consider either: