The DNS Root Name service are a critical part of the Internet
architecture. The protocol and deployment requirements expected to
be implemented for the DNS root name services are defined in this
document. Operational requirements are out of scope. This document
obsoletes and reclassifies RFC2870 as Historic.

This paper describes the Postellation DTN (e.g. Bundle protocol) implementation, which has been written as highly portable running on Windows, Linux, MacOSX as well as embedded real-time operating systems such as RTEMS and others. The paper shows the key differences of this implementation, such as how the real- time streaming is achieved, as well as the automated network attachment mechanism. For example, a use-case scenario is to have IP devices on spacecraft on-board, running typical IP/HTTP-based applications such as an IP-HTTP based streaming camera, then a DTN node gatewaying the IP trafic from the spacecraft to the Earth through the DTN space network. A DTN node on Earth then gateways the trafic to the IP network on Earth. This streaming trafic is deployed transparently for both the spacecraft and Earth IP apps, while traversing a DTN network.

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.

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 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 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.

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.

Using Unicode codepoints in protocol strings requires preparation of the string. This document describes the Precis Protocol Framework that prepares various classes of strings used in protocol elements. A protocol specification chooses a class of strings and then implements the corresponding preparation steps described in this document. This document is based on the IDNAbis approach. It obsoletes the Stringprep algorithm.

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. A new approach different from Stringprep/Nameprep is used for a revision of IDN. The Stringprep profiles need to be updated or a replacement of Stringprep need to be designed. This document summarizes the findings of the current usage of Stringprep and identifies directions for a new Stringprep replacement protocol.

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 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 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.

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.

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 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).

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.

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.

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.

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.

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.

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 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 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 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 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.

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.

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 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.

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 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 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 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.

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.

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.

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.