The IPv6 Business Information Exchange is a free service to the business community provided by Inside Products. The goal is to facilitate exchange of technical information needed to implement IPv6 in networks both large and small. If there are facilities that are not yet provided by the IPv6 protocol, we will approach the IETF or other bodies for clarification or enhancements. To view the current Internet-Drafts submitted to the IETF, please click HERE.
You may suggest a new topic for discussion by emailing firstname.lastname@example.org. When we receive topics, we will try to get industry authorities to address the questions as well as providing a forum to discuss the topics within the group.
March 31, 2015
IETF 92 Update: IPv6 Business Information Exchange (BIE)
A recap of the IETF 92 meeting. We will be presenting our draft for enhanced performance and diagnostic metrics (IPPM Considerations for the IPv6 PDM header ) at the IPPM working group session.
This draft is co-authored by Nalini Elkins - Inside Products, Inc., Mike Ackermann - Blue Cross Blue Shield of Michigan, and Rob Hamilton - Chemical Abstracts Service.
Google IPv6 statistics show IPv6 traffic to Google of over 6%. This is expected to double in 2015.
In this webcast, we will present our proposal and bring you up to date on the latest activities at the IETF. You may wish to view information on our IPv6 Problem Finder or IPv6 consulting. To arrange for an IPv6 class at your site, please contact us at email@example.com.
July 16, 2013 : report on the last IETF meeting in July. Shumon Huque of the University of Pennsylvania discussed their experience with IPv6 at U Penn.
IPv6 has been deployed in major parts of the University of Pennsylvania's campus network since 2005. Besides network infrastructure, several key application services are IPv6 enabled, including a variety of Web (HTTP) servers, DNS, NTP, XMPP, and others. This session will include a discussion of why the university deployed IPv6, what problems were encountered, what worked well, what problems remain, and what they would do differently.
We reviewed the draft RFC which we presented to the v6Ops working group. You may see that HERE.