Thursday, October 9, 2014

ISATAP



ISATAP is the Intra-Site Automatic Tunnel Addressing Protocol which supports automatic deployment of IPv6 in IPv4 sites.

ISATAP specifies the operation of IPv6 and the IPv6 Neighbor Discovery (ND) protocol over a specific link layer (that being IPv4 used as a link layer for IPv6) and is therefore an "IPv6-over-foo" specification.

ISATAP is essentially just a Non-Broadcast Multiple Access (NBMA) variant of 6over4 [RFC2529]. As of March 2008, ISATAP has been re-published as an informational-category RFC [RFC5214] which obsoletes the previous experimental-category version [RFC4214]. A development history of RFC4214 is on the ISATAP Issue Tracker Page As of April 2008, ISATAP is implemented in the Linux operating system kernel, beginning with linux-2.6.25. ISATAP is also implemented in other widely-deployed systems including Microsoft Windows (XP, Vista, 7, 8), cisco IOS, 6WIND 6WINDGate, and FreeBSD/KAME. An ISATAP client application for both Linux and Android systems is now available here.

 ISATAP hosts use IPv6 StateLess Address Auto Configuration (SLAAC) by sending a unicast Router Solicitation (RS) message to an ISATAP router which then returns a unicast Router Advertisement (RA) message. This stateless operation is sufficient for many client-initiated IPv6 applications but does not support true native IPv6 operation. A new system called Asymmetric Extended Route Optimization (AERO) has therefore been developed based on the ISATAP NBMA model. Like ISATAP, AERO is an "ipv6-over-foo" document and specifies the operation of IPv6 and IPv6 ND over AERO links. Unlike ISATAP, AERO is stateful and requires the use of the IPv6 neighbor cache on AERO interfaces. AERO nodes also use the DHCPv6 Prefix Delegation service to obtain native IPv6 prefixes. The benefits of the AERO approach include 1) use of fully-native IPv6 addresses, 2) persistent IPv6 addresses and/or prefixes that never change, 3) mobilitiy support, 4) router-to-router tunneling, 5) mobile routers, 6) path MTU robustness, and many others.

Source:  http://www.isatap.org/

Tuesday, April 22, 2014

Office Online with Chromebook

As the name implies, Office Online is Microsoft’s suite of Office apps available online. Like how Google Docs connects to Google Drive, Office Online connects to Microsoft’s own cloud storage service, OneDrive. OneDrive is available to anyone who has a Microsoft Live account, and comes with 7 GB for free. This is less than Google’s 15 GB, but is still enough for basic files.
Office Online home page
Office Online home page
Office Online comes with many of Microsoft’s Office programs:
  • Word
  • Powerpoint
  • Excel
  • OneNote
  • Outlook.com is integrated with the service, also
It also comes with a calendar and address book for your personal use. The Office Online apps look like the current edition of Microsoft Office, with the tile look for the toolbar and tabs for different topics. Compared to the original Office suite, this version is very slimmed down, missing tools that you may be used to in the regular Office programs. However, people who pay for Office 365 will see many more features in Office Online, and it will be even closer to the downloadable version.
FROM:
 http://www.muktware.com/2014/04/google-docs-vs-office-online-best-office-chromebooks/26062

"One Windows"

With Threshold, my sources say, there could be three primary SKUs: A "modern" consumer SKU; a traditional/PC SKU; and a traditional enterprise SKU.  (SKU actually stands for stock-keeping unit, for those wondering.)

The modern (i.e., Metro-Style/Windows Store) consumer SKU would be focused on WinRT apps. (WinRT, in this case, refers to the API set at the heart of Windows, not the current Windows RT operating system that runs on ARM.) It may end up targeting ARM- and Intel-based devices both. It would be updated frequently by Microsoft through the Windows Store.
This SKU supposedly wouldn't be optimized to run Win32 apps. However, my contact said there's the possibility that on some PC-like form factors, there may be a "desktop" that is more easily navigable for keyboard/mouse users.
This modern SKU would be the SKU for Windows Phones, ARM-based Windows tablets/PCs, phablets and other kinds of tablets. Some PCs also may run this SKU, providing Microsoft with a more head-to-head competitor to Chromebooks, as these machines would be more secure and locked down (thanks to the way Microsoft built the WinRT/Windows Store model).
The modern SKU is what has previously been rumored as a forthcoming Microsoft hybrid Windows Phone OS/Windows RT operating system.

A more traditional consumer SKU would be aimed at the current PC market. This SKU would include a desktop and be customized so that mouse/keyboard users will be able to continue to have some semblance of productivity and familiarity with Windows. This SKU also would be updated regularly and often through the Windows Store.
There also will likely be some kind of traditional Enterprise SKU, according to my contacts, that would include all the usual business bells and whistles, like support for Win32 apps via a Desktop environment, support for group policy, device management and more. This SKU would be aimed primarily at traditional PCs, tablets and other devices and also allow users to run "Modern"/Windows Store apps.

The Enterprise SKU might end up being for volume licensees only. This might be a SKU that doesn't update frequently/constantly through the Windows Store. Instead, it might be subject to IT policies/approvals, making enterprise users who don't want silent, automatic updates a lot happier. Microsoft Windows chief Terry Myerson hinted at something like this during his recent Credit Suisse tech conference appearance.
There will likely be some additional device-specific Windows "Threshold" SKUs for embedded devices and usages, such as point-of-sale terminals, kiosks, etc., given that the Embedded team is now part of Myerson's organization.  But these SKUs won't be offered directly to consumers or business users directly.
Microsoft is attempting to straddle a fence here and continue to advance Windows as a "modern" mobile platform, while not disenfranchising their huge existing base. The big takeaway here is there may be more concessions coming to folks who felt like Windows 8 went too far in turning Windows into a touch-first, tablet-centric operating system. To me, this is a welcome furthering of the changes that began more conservatively last year with the re-emergence of the Start button and allowance of boot to desktop by default.

Update: Here are a couple of related tidbits, courtesy of sources of Windows SuperSite's Paul Thurrott. Thurrott said he's hearing the revised Desktop will allow users to run multiple Metro appson the Desktop. That'd mean windows comes back to Windows. Plus, he's hearing the Start Menu might return, too, supplementing the currently Start-Menuless Start Button -- another plus for those struggling with the current Windows 8.x navigation scheme.
FROM:
http://www.zdnet.com

"Threshold"

It turns out the Microsoft codename for that wave of deliverables is "Threshold."
A couple of my contacts have confirmed that Microsoft Executive Vice President Terry Myerson recently mentioned the Threshold codename in an internal email about plans for his unified operating-system engineering group.
If all goes according to early plans, Threshold will include updates to all three OS platforms (Xbox One, Windows and Windows Phone) that will advance them in a way to share even more common elements.
(The codename Threshold, for those wondering, derives from the planet around which the first halo ring orbited in the original Halo game launched back in 2001. Threshold joins "Cortana," Microsoft's answer to Siri, as yet another codename with its origins in the Xbox franchise.)
From what I've heard, Threshold doesn't refer to a single Windows OS -- not even the expected, converged hybrid comprised of the Windows Phone OS and Windows RT. Instead, the codename refers to the wave of operating systems across Windows-based phones, devices and gaming consoles.
The Xbox One OS, Windows 8.x OS and Windows Phone 8 OS already share a common Windows NT core. As we've heard before, Microsoft is working to deliver a single app store across its myriad Windows platforms. Company officials also are laboring to make the developer toolset for all three of these platforms more similar.

But Threshold will add another level of commonality across Microsoft's various Windows-based platforms, sources said. With the Threshold wave, Microsoft plans to support the same core set of "high value activities" across platforms. These high-value activities include expression/documents (Office, and the coming "Remix" digital storytelling app, I'd think); decision making/task completion (Bing, I'd assume); IT management (Intune and Workplace Join, perhaps?) and "serious fun."
CEO Steve Ballmer mentioned this concept of high-value activities at back in July when he announced Microsoft's cross-company reorg to make the company more focused around its new "One Microsoft" mission.
Before Microsoft gets to Threshold, the company is on track to deliver an update to Windows 8.1 (known as Windows 8.1 Update 1) around the same time that it delivers Windows Phone "Blue" (Windows Phone 8.1). That's supposedly happening in the spring 2014/Q2 2014 timeframe, from what my sources have said.
I've asked Microsoft officials if they'd confirm any of this information about Threshold. No word back so far.
Update: A Microsoft spokesperson said the company had no comment on "rumors and speculation."
FROM:
http://www.zdnet.com