Re: [Fed-Talk] IPv6 for Fed agencies
Re: [Fed-Talk] IPv6 for Fed agencies
- Subject: Re: [Fed-Talk] IPv6 for Fed agencies
- From: Shawn Geddis <email@hidden>
- Date: Thu, 7 Jul 2005 13:02:05 -0400
Folks,
It is a correct statement that not all applications fully utilize the
built in support for IPv6, however, keep in mind that Mac OS X also
supports two IPv6 related configuration options.
(1) Network Preference Pane references the IPv6 Address at the bottom
which is either dynamically configured for that port or manually
configured by an administrator
(2) An IPv6 <-> IPv4 'port' configurable within 'System Preferences -
> Network'.
- Select "Network Port Configurations"
- Click "New..."
- Select Port: to be "6 to 4"
This should provide the capability of an IPv4 only service to
communicate on an IPv6 network or a n IPv6 service to communicate on
an IPv4 only network. This can be enabled and configuration remain
automatic (default) or be manually configured with a specific Relay
Address.
As noted in the Mac OS X Server - Network Services v10.4 PDF on page
124:
IPv6 Enabled Services
The following services in Mac OS X Server support IPv6 in addressing:
• DNS (BIND)
• IP Firewall
• Mail (POP/IMAP/SMTP)
• SMB/CIFS
• Web (Apache 2)
Where to Find More Information
The working group for the Internet Protocol Version 6 website is:
http://www.ipv6.org/
A group of IPv6 enthusiasts maintains a list of applications that
support IPv6 at the
website:
http://www.ipv6forum.com/navbar/links/v6apps.htm
-Shawn
___________________________________________
Shawn Geddis
Security Consulting Engineer
Apple Computer - US Federal Government
On Jul 5, 2005, at 10:09 PM, Brian Raymond wrote:
Most OSes are, and have been capable of IPv6 for a while now. The big
problem is and will continue to be infrastructure supporting IPv6
(and IPv4
gateways) and the lack of application support for IPv6 in those
which deal
with IP addresses. I haven't had any real problems with the OSS
apps I use
however commercial support has been a problem for me.
Any number of DoD programs should be able to share their
frustration with
you regarding this problem. I've personally been involved with a
handful in
which IPv6 was initially on the table but was in the end punted on
because
getting everything lined up on the COTS side proved to be too
difficult.
One example of a application which a large number of organizations
use that
doesn't support IPv6 is Exchange 2003. On the OSX side I'm personally
looking forward to IPv6 support in Darwin Streaming Server,
although it's on
the way in the short term.
- Brian
On 7/5/05 5:52 PM, "Dan O'Donnell" <email@hidden> wrote:
A magazine article last week says that OMB has mandated IPv6 for
all Federal
agencies by June 2008. That's only three years to implement such a
deep and
broad change. I know OSX 10.3 and 10.4 are capable of it, but
wonder if
anybody has done any testing of OSX with IPv6 yet?
<http://www.govexec.com/dailyfed/0605/062905tdpm2.htm>
OMB: Agencies must use advanced Internet by 2008
By Chloe Albanesius, National Journal's Technology Daily
Federal agencies must use the next-generation Internet service
known as
Internet protocol version 6 (IPv6) by June 2008, the White House
Office of
Management and Budget announced Wednesday.
The office said it would issue a policy memorandum dictating full
federal
"IPv6" compliance in an effort to spur its deployment throughout
government
agencies.
The Defense Department currently is the only federal body to have
made
strides in implementing IPv6. Due to this "lack of government-wide
progress"
and concerns about the "complexities of transition," OMB will
release a
"comprehensive transition planning guide," OMB Administrator Karen
Evans
said in written testimony for the House Government Reform Committee.
The five-point compliance guide will require agencies to familiarize
themselves with transition issues, an effort Evans described as the
"overarching challenge" of moving from the current IPv4 to IPv6.
The move
will "require many changes in the architecture of many agency
networks," as
well as "large capital investments and labor resources."
An undertaking so complex will require an agency point person to
lead and
coordinate the transition, Evans said. "This person will be
responsible for
monitoring, enforcing and reporting on the transition and
implementation of
IPv6 within the agency."
With this person in place, agencies will be charged with
developing, by the
first quarter of fiscal 2006, an inventory of existing IP-capable
equipment
and an analysis to determine the financial impact and risks of the
transition, Evans said.
"While we know that IPv6 technologies are deployed throughout the
government
... we do not know specifically which ones, how many there are, or
precisely
where they are located," she said. "For cost, the agencies must
report on
estimates for planning, infrastructure acquisition, training and risk
mitigation."
Finally, the government's Chief Information Officers Council will
be charged
with developing "more detailed IPv6 implementing guidance" by
year's end,
Evans said. The group will have to issue guidance on developing a
sequencing
plan, IPv6 integration, training materials and test plans for
compatibility.
With these efforts in place, OMB wants all agencies to use IPv6 by
June
2008, Evans said. "Setting this firm date is necessary to maintain
focus on
this important issue."
In a 41 page report released in May, the Government Accountability
Office
said that federal agencies other than the Defense Department have
yet to
plan for IPv6.
David Powner, GAO director of information technology management
issues, told
the committee that the government is behind the "8 ball" from a
leadership
perspective in implementing IPv6.
"It's clear we don't have a deadline like Y2K," Powner said.
"[But] if we
allow others to develop IPv6 before us, they'll be the ones to
develop the
killer application."
Having federal agencies work on transition efforts will help "further
increase industry activities in the United States," said John Curran,
chairman of the American Registry for Internet Numbers.
Jawad Khaki, corporate vice president for Microsoft, pushed for a
"market-based conversion to IPv6 [as] the most technologically
feasible and
least disruptive" transition process. He speculated that the
flexible nature
of IPv6 would mean that conversion activity would happen "at the
edge of the
network" with home computers, eventually moving to "encompass the
rest of
the global Internet infrastructure."
Microsoft's next operating system, dubbed Longhorn, will be "fully
IPv6-capable," Khaki said.
"To reap the benefits from IPv6 federal agencies first must begin
to plan
and develop requirements that will take full advantage of what the
new
protocol offers," committee Chairman Tom Davis said. The Virginia
Republican
expressed concern about the security and competitive risks
associated with
the IPv6 transition.
Reporter Daniel Pulliam contributed to this story.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Fed-talk mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden