This presentation describes the NAT64 framework, solution and Viagénie's NAT64 implementation on OpenBSD as a patch to the PF packet filter, on Linux as a patch to Netfilter, and the DNS64 implementation as patches to Unbound and Bind.

A multihomed host receives node configuration information from each of its provisioning domain. Some configuration objects are global to the node, some are local to the interface. Various issues arise when multiple conflicting node-scoped configuration objects are received on multiple interfaces. Similar situations also happen with single interface host connected to multiple networks. This document describes these issues.

The ISACC IPv6 Task Group was formed in June 2009 to provide advice to the Canadian government on IPv6 deployment in Canada. This document is the final report of the working group.

This document defines the vCard data format for representing and exchanging a variety of information about an individual (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.).

This document defines the XML schema of the vCard data format.

The CCSDS Cross-Support Transfer Services Area has been handling the Space Link Identifiers registry as a document. This presentation discusses how to convert the document into a managed Space Assigned Numbers Authority(SANA) registry. This presentation is discussed during the CSTS-SLS CCSDS meeting.

A multihomed host receives node configuration information from each of its provisioning domain. Some configuration objects are global to the node, some are local to the interface. Various issues arise when multiple conflicting node-scoped configuration objects are received on multiple interfaces. Similar situations also happen with single interface host connected to multiple networks. This document describes these issues.

The CCSDS Space Assigned Numbers Authority(SANA) is operated by Viagénie under contract. SANA services is introduced to the CCSDS community during the CCSDS plenary.

The DTNRG research group has defined many protocols such as Bundle Protocol and Licklider. The specifications of these protocols contain fields that are subject to a registry. For the purpose of its research work, the group created adhoc registries. As the specifications are stable and have multiple interoperable implementations, the group would like to handoff the registries to IANA for official custidy. This document describes the actions needed to be executed by IANA.

IPv6 a été conçu en 1996 suite à une étude prévoyant le manque d'adresses IPv4 autour de 2010. Le déploiement d'IPv6 jusqu'à maintenant a été minimal, même si la plupart des systèmes d'exploitation dont Linux, FreeBSD, Windows, MacOSX, les produits commerciaux routeurs et les applications principales supportent IPv6 souvent depuis belle lurette. Cependant, les adresses IPv4 deviennent rares et très bientôt épuisées. Plusieurs grands fournisseurs, tels que Google, supportent maintenant IPv6. Certains gouvernements se sont positionnés sur cette technologie. La présentation fera l'état de la situation globalement et localement. Elle discutera des impacts pour les individus, les professionnels en informatique, les entreprises et les fournisseurs Internet. Évidemment, des exemples pratiques Linux et autres seront présentés. La présentation se veut très interactive et les questions seront bienvenues durant toute la présentation.

Invité à l'inauguration de la task Force Ipv6 d'Algérie, M.Blanchet présente les activités d'IPv6 au Canada, dont particulièrement les résultats du groupe de travail ISACC IPv6.

This presentation describes the NAT64 network experiment done during IETF 77 in Anaheim using Viagénie implementations (http://ecdysis.viagenie.ca). It shows various issues, statistics and findings of the experiment.

The DTNRG research group has defined many protocols such as Bundle Protocol and Licklider. The specifications of these protocols contain fields that are subject to a registry. For the purpose of its research work, the group created adhoc registries[DTNRGREG]. As the specifications are stable and have multiple interoperable implementations, the group would like to handoff the registries to IANA for official custidy. This document describes the actions needed to be executed by IANA.

The ISACC IPv6 Task Group was formed in June 2009 to provide advice to the Canadian government on IPv6 deployment in Canada. This is the presentation of the final report of the working group.

This presentation describes the NAT64 framework, solution and Viagénie's NAT64 implementation on OpenBSD as a patch to the PF packet filter and the DNS64 implementation as patches to Unbound and Bind.

A multihomed host receives node configuration information from each of its provisioning domain. Some configuration objects are global to the node, some are local to the interface. Various issues arise when multiple conflicting node-scoped configuration objects are received on multiple interfaces. Similar situations also happen with single interface host connected to multiple networks. This document describes these issues.

This document defines the XML schema of the vCard data format.

This document defines the vCard data format for representing and exchanging a variety of information about an individual (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.).

This document adds IPv6 support to Traversal Using Relays around NAT (TURN). IPv6 support in TURN includes IPv4-to-IPv6, IPv6-to-IPv6, and IPv6-to-IPv4 relaying. This document defines the REQUESTED- ADDRESS-FAMILY attribute for TURN. The REQUESTED-ADDRESS-FAMILY attribute allows a client to explicitly request the address type the TURN server will allocate (e.g., an IPv4-only node may request the TURN server to allocate an IPv6 address).

This specification defines an extension of Traversal Using Relays around NAT (TURN), a relay protocol for NAT traversal, to allow a TURN client to request TCP allocations, and defines new requests and indications for the TURN server to open and accept TCP connections with the client's peers. TURN and this extension both purposefully restrict the ways in which the relayed address can be used. In particular, it prevents users from running general purpose servers from ports obtained from the TURN server.

Using Unicode codepoints in protocol strings requires preparation of the string. Internationalized Domain Names(idn) initial work defined and used Stringprep and Nameprep. Other protocols have defined Stringprep profiles. New approach different from Stringprep/Nameprep is used for a revision of IDN. This document summarize the characteristics of both approach and provides guidance to protocol designers for handling internationalized strings.

A tunnel broker with the Tunnel Setup Protocol (TSP) enables the establishment of tunnels of various inner protocols, such as IPv6 or IPv4, inside various outer protocols packets, such as IPv4, IPv6, or UDP over IPv4 for IPv4 NAT traversal. The control protocol (TSP) is used by the tunnel client to negotiate the tunnel with the broker. A mobile node implementing TSP can be connected to both IPv4 and IPv6 networks whether it is on IPv4 only, IPv4 behind a NAT, or on IPv6 only. A tunnel broker may terminate the tunnels on remote tunnel servers or on itself. This document describes the TSP within the model of the tunnel broker model.

This document adds IPv6 support to Traversal Using Relays around NAT (TURN). IPv6 support in TURN includes IPv4-to-IPv6, IPv6-to-IPv6, and IPv6-to-IPv4 relaying. This document defines the REQUESTED- ADDRESS-FAMILY attribute for TURN. The REQUESTED-ADDRESS-FAMILY attribute allows a client to explicitly request the address type the TURN server will allocate (e.g., an IPv4-only node may request the TURN server to allocate an IPv6 address).

Delivered to the Internet Engineering Task Force(IETF) vCardDAV working group, this presentation describes the changes to the vCard specification as well as its current status.

This presentation is used by Marc Blanchet, co-chair of the Internet Engineering Task Force(IETF) vCardDAV working group, to report on the status of the working group and to set the agenda of the meeting.

Delivered to the Internet Engineering Task Force(IETF) vCardDAV working group, this presentation describes the vCard to XML mapping specification.

3GPP and IETF held a joint workshop on IPv6 deployment, hosted by China Mobile. This presentation describes the NAT64 framework, solution and Viagénie's implementation. It also compares NAT64 with other IPv6 transition technologies.

The ISACC IPv6 Task Group was formed in June 2009 to provide advice to the Canadian government on IPv6 deployment in Canada. This presentation provides an update on the works of the task group and lists the 7 recommendations made by the group.

The purpose of this document is to define the Space Assigned Numbers Authority(SANA), its role, responsibilities, policies and procedures within the CCSDS.

The CCSDS Space Assigned Numbers Authority(SANA) working group is about to conclude its initial mandate to define the SANA function within CCSDS. This presentation describes the SANA function to the CCSDS community. It was presented during the CCSDS plenary.

A multihomed host receives node configuration information from each of its access networks. Some configuration objects are global to the node, some are local to the interface. Various issues arise when multiple conflicting node-scoped configuration objects are received on multiple interfaces. Similar situations also happen with single interface host connected to multiple networks. This document describes these issues.

This document defines the XML schema of the vCard data format.

This document defines the vCard data format for representing and exchanging a variety of information about an individual (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.).

This specification defines an extension of Traversal Using Relays around NAT (TURN), a relay protocol for NAT traversal, to allows a TURN client to request TCP allocations, and defines new requests and indications for the TURN server to open and accept TCP connections with the client's peers. TURN and this extension both purposefully restrict the ways in which the relayed address can be used. In particular, it prevents users from running general purpose servers from ports obtained from the STUN server.

A multihomed host receives node configuration information from each of its access networks. Some configuration objects are global to the node, some are local to the interface. Various issues arise when multiple conflicting node-scoped configuration objects are received on multiple interfaces. Similar situations also happen with single interface host connected to multiple networks. This document describes these issues.

This document adds IPv6 support to Traversal Using Relays around NAT (TURN). IPv6 support in TURN includes IPv4-to-IPv6, IPv6-to-IPv6, and IPv6-to-IPv4 relaying. This document defines the REQUESTED- ADDRESS-FAMILY attribute for TURN. The REQUESTED-ADDRESS-FAMILY attribute allows a client to explicitly request the address type the TURN server will allocate (e.g., an IPv4-only node may request the TURN server to allocate an IPv6 address).

Interactive Connectivity Establishment (ICE) defines a mechanism for NAT traversal for multimedia communication protocols based on the offer/answer model of session negotiation. ICE works by providing a set of candidate transport addresses for each media stream, which are then validated with peer-to-peer connectivity checks based on Session Traversal Utilities for NAT (STUN). ICE provides a general framework for describing candidates, but only defines UDP-based transport protocols. This specification extends ICE to TCP-based media, including the ability to offer a mix of TCP and UDP-based candidates for a single stream.

This presentation was requested by Cluecon organizers to give some basic information on how to setup IPv6 networks. It shows configs for most OS, routers and PBX and gives practical advice to deploy IPv6.

Delivered to the Internet Engineering Task Force(IETF) vCardDAV working group, this presentation describes the changes to the vCard specification as well as its current status.

This presentation describes the issues found while implementing DNS64 as part of Viagenie's Ecdysis project, consisting of an opensource NAT64 implementation.

Delivered to the Internet Engineering Task Force(IETF) vCardDAV working group, this presentation describes the vCard to XML mapping specification.

This presentation is used by Marc Blanchet, co-chair of the Internet Engineering Task Force(IETF) vCardDAV working group, to report on the status of the working group and to set the agenda of the meeting.

This document defines the vCard data format for representing and exchanging a variety of information about an individual (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.).

This document defines the XML schema of the vCard data format.

This specification defines an extension of Traversal Using Relays around NAT (TURN), a relay protocol for NAT traversal, to allows a TURN client to request TCP allocations, and defines new requests and indications for the TURN server to open and accept TCP connections with the client's peers. TURN and this extension both purposefully restrict the ways in which the relayed address can be used. In particular, it prevents users from running general purpose servers from ports obtained from the STUN server.

Petit introduction sur les noms de domaines internationalisés.

A multihomed host receives node configuration information from each of its access networks. Some configuration objects are global to the node, some are local to the interface. Various issues arise when multiple conflicting node-scoped configuration objects are received on multiple interfaces. Similar situations also happen with single interface host connected to multiple networks. This document describes these issues.

Simon Perreault présente les enjeux de sécurité liés au déploiement de la téléphonie IP en entreprise. Cette présentation a été donnée dans le cadre des petits-déjeuners conférence de l'Institut de sécurité de l'information du Québec (ISIQ).

This document defines the XML schema of the vCard data format.

This document defines the vCard data format for representing and exchanging a variety of information about an individual (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.).

The purpose of this document is to define the Space Assigned Numbers Authority(SANA), its role, responsibilities, policies and procedures within the CCSDS.

Presented at the Multiple Interfaces (MIF) BOF meeting, this presentation describes the issues that arise when a host has multiple interfaces.

This presentation describes the updates made to the TURN-TCP specification.

Delivered to the Internet Engineering Task Force(IETF) vCardDAV working group, this presentation describes the changes to the vCard specification as well as its current status.

This presentation is used by Marc Blanchet, co-chair of the Internet Engineering Task Force(IETF) vCardDAV working group, to report on the status of the working group and to set the agenda of the meeting.

This document defines the vCard data format for representing and exchanging a variety of information about an individual (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.).

This specification defines an extension of Traversal Using Relays around NAT (TURN), a relay protocol for NAT traversal, to allows a TURN client to request TCP allocations, and defines new requests and indications for the TURN server to open and accept TCP connections with the client's peers. TURN and this extension both purposefully restrict the ways in which the relayed address can be used. In particular, it prevents users from running general purpose servers from ports obtained from the STUN server.

Cette présentation fait un rappel sur IPv6 pour ensuite discuter du port de Asterisk et Freeswitch à IPv6. Enfin, la problématique de traverser des NATs et firewalls est discutée.

A multi-homed host receives node configuration information from each of its access networks. Some configuration objects are global to the node, some are local to the interface. Various issues arise when multiple configuration objects that are global to the node are received on the many interfaces the multi-homed host has. This document describes these issues.

Delivered to the Internet Engineering Task Force(IETF) vCardDAV working group, This presentation describes the proposed vCard to XML mapping specification.

Delivered to the Internet Engineering Task Force(IETF) vCardDAV working group, this presentation describes changes to the vCard specification as well as its current status.

This presentation is used by Marc Blanchet, co-chair of the Internet Engineering Task Force(IETF) vCardDAV working group, to report on the status of the working group and to set the agenda of the meeting.

This document defines the XML schema of the vCard data format.

The purpose of this document is to define the Space Assigned Numbers Authority(SANA), its role and responsibilities within the CCSDS.

This document defines the vCard data format for representing and exchanging a variety of information about an individual (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.).

This document defines the vCard data format for representing and exchanging a variety of information about an individual (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.).

The purpose of this document is to define the Space Assigned Numbers Authority(SANA), its role and responsibilities within the Consultative Committee for Space Data Systems (CCSDS).

One of the major impediments to deploying Asterisk is the omnipresence of network address translators (NATs) and firewalls. As evidenced by the success of peer-to-peer VoIP, transparent and automatic NAT and firewall traversal is an extremely desirable feature. This presentation describes STUN, TURN, and ICE: three protocols being standardized by the IETF which work together to either punch holes through NATs and firewalls or, when end-to-end connectivity is not an option, to work around them via a third-party relay. How they work, what problems they solve, and how Asterisk makes use of them is answered. A demonstration of Viagénie's implementation is also given.

This presentation describes the problems related to NAT and firewalls when deploying VoIP. It then details the STUN, TURN and ICE protocols and the solutions used to solve these issues. The STUN-TURN server developed by Viagénie is also discussed.

This presentation announces the porting of Freeswitch to IPv6. It also describes the lessons learned while porting VoIP applications to IPv6.

Delivered to the Internet Engineering Task Force(IETF) vCardDAV working group, this presentation describes the changes to the vCard specification as well as its current status.

This presentation is used by Marc Blanchet, co-chair of the Internet Engineering Task Force(IETF) vCardDAV working group, to report on the status of the working group and to set the agenda of the meeting.

This document defines the vCard data format for representing and exchanging a variety of information about an individual (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.).

This document defines the vCard data format for representing and exchanging a variety of information about an individual (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.).

A tunnel broker with the Tunnel Setup Protocol (TSP) enables the establishment of tunnels of various inner protocols, such as IPv6 or IPv4, inside various outer protocols packets, such as IPv4, IPv6 or UDP over IPv4 for IPv4 NAT traversal. The control protocol (TSP) is used by the tunnel client to negotiate the tunnel with the broker. A mobile node implementing TSP can be connected to both IPv4 and IPv6 networks whether it is on IPv4 only, IPv4 behind a NAT or on IPv6 only. A tunnel broker may terminate the tunnels on remote tunnel servers or on itself. This document describes the TSP protocol within the model of the tunnel broker model.

This document defines the vCard data format for representing and exchanging a variety of information about an individual (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.).

This document is a compilation of special IPv6 addresses defined in other RFCs. It can be used as a checklist of invalid routing prefixes for developing filtering policies for routes and IP packets. It does not discuss addresses that are assigned to operators and users through the Regional Internet Registries. This memo provides information for the Internet community.

This document defines the vCard data format for representing and exchanging a variety of information about an individual (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.).

This presentation is used by Marc Blanchet, co-chair of the Internet Engineering Task Force(IETF) vCardDAV working group, to report on the status of the working group and to set the agenda of the meeting.

Delivered to the Internet Engineering Task Force(IETF) vCardDAV working group, this presentation describes a CardDAV server implementation, as well as certain issues found with the specifications.

Delivered to the Internet Engineering Task Force(IETF) vCardDAV working group, this presentation presents the changes to the vCard specification as well as its current status.

Cette présentation discute de l'avancement des noms de domaines internationalisés.

Cette présentation montre comment l'Internet Engineering Task Force(IETF) fonctionne et le processus pour l'établissement des normes et standards des protocoles de l'Internet.

This document defines the vCard data format for representing and exchanging a variety of information about an individual (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.).

This document defines the vCard data format for representing and exchanging a variety of information about an individual (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.).

This document describes the global and other specialized IPv6 address blocks. It does not address IPv6 address space assigned to operators and users through the Regional Internet Registries. These descriptions are useful for route and IP filtering, for documentation and other purposes.

Cette présentation discute de l'opportunité de déployer IPv6 dans les réseaux d'enseignement et de recherche.

This document describes the global and other specialized IPv6 address blocks.It does not address IPv6 address space assigned to operators and users through the Regional Internet Registries. These descriptions are useful for route and IP filtering, for documentation and other purposes.

This document describes the global and other specialized IPv6 address blocks.It does not address IPv6 address space assigned to operators and users through the Regional Internet Registries. These descriptions are useful for route and IP filtering, for documentation and other purposes.

This document describes the global and other specialized IPv6 address blocks.It does not address IPv6 address space assigned to operators and users through the Regional Internet Registries. These descriptions are useful for route and IP filtering, for documentation and other purposes.

This document describes the global and other specialized IPv6 address blocks.It does not address IPv6 address space assigned to operators and users through the Regional Internet Registries. These descriptions are useful for route and IP filtering, for documentation and other purposes.

Presentation of draft-ietf-v6ops-routing-guidelines-01.txt to IETF IPv6 Operations working group (v6ops).

Marc Blanchet presents the work of porting and running Asterisk over IPv6. The presentation was part of an Asterisk session chaired by Kevin Fleming of Digium.

The IPv6 Forum, along with Viagenie, Stealth Communications and CounterPath Solutions, today announced that a series of successful VoIP calls over IPv6 has been carried out, marking an important advancement in worldwide interoperability among VoIP technologies using IPv6.

The VoIP calls, connecting Viagenie in Canada and Consulintel in Spain, were conducted using the CounterPath eyeBeam(tm) softphone through the IPv6 version of Asterisk(r), ported by Viagenie, a consulting and R and D firm in advanced IP networking. The Asterisk-IPv6 server was located on Stealth Communications Voice Peering Fabric (VPF) network.

Asterisk is the most popular and extensible open source telephone system in the world, offering flexibility, functionality and features not available in advanced, high-end (high-cost) proprietary business systems. Asterisk is a complete IP PBX (private branch exchange) for businesses, and can be downloaded for free.

Asterisk-IPv6 shows the power of VoIPv6 by avoiding all issues regarding NAT traversal when using IPv4. The presence of NAT for VoIPv4 results in users issues, such as non-connecting calls, one-way audio, non-working DTMF. Asterisk-IPv6 solves all these issues and also brings, together with IPv6, true IP mobility, security and autoconfiguration of VoIPv6 phones, states Marc Blanchet, President of Viagenie.

Marc Blanchet presents how to use internationalized domain names(idn) with Firefox 2.0. Idn are very popular in Asia Pacific region due to the fact that asian scripts are far different than ASCII, the default character set for domain names.

This presentation shows the work of porting and running Asterisk over IPv6. IPv6 has more presence in the Asia Pacific region and showed interest on using VoIP over IPv6 using Asterisk.

Tutorial "Asterisk Primer" aimed towards helping people to fast start with Asterisk, the open-source VoIP PBX.

Une introduction au Domain Name System, aux noms de domaines internationalisés et à IPv6 lors d'une rencontre de l'Internet Society-section de Québec et l'Internet Corporation for Assigned Names and Numbers (ICANN) à Montréal.

This presentation describes the port of Asterisk to IPv6.

Presentation of draft-blanchet-v6ops-routing-guidelines-01 to IETF IPv6 Operations working group (v6ops).

Cette présentation est un cours sur la structure de l'Internet Engineering Task Force(IETF) et l'établissement des normes de l'Internet. Offert au début du congrès de l'IETF, le cours vise les nouveaux participants à l'IETF. Le matériel utilisé est une traduction par Marc Blanchet de la présentation de Scott Bradner sur le sujet.

This presentation is a short primer on IPv6 for sensor networks.

Presentation of draft-blanchet-v6ops-routing-guidelines-01 to IETF IPv6 Operations working group (v6ops).

Guidelines on how to handle IPv6 routes are needed for operators of networks, either providers or enterprises. This document is a followup on RFC2772 work but for the production IPv6 Internet. RFC2772 becomes historic.

A tunnel broker with the Tunnel Setup Protocol (TSP) enables the establishment of tunnels of various inner protocols, such as IPv6 or IPv4, inside various outer protocols packets, such as IPv4, IPv6 or UDP over IPv4 for IPv4 NAT traversal. The control protocol (TSP) is used by the tunnel client to negotiate the tunnel with the broker. A mobile node implementing TSP can be connected to both IPv4 and IPv6 networks whether it is on IPv4 only, IPv4 behind a NAT or on IPv6 only. A tunnel broker may terminate the tunnels on remote tunnel servers or on itself. This document describes the TSP protocol within the model of the tunnel broker model.