All

What are you looking for?

All
Projects
Results
Organizations

Quick search

  • Projects supported by TA ČR
  • Excellent projects
  • Projects with the highest public support
  • Current projects

Smart search

  • That is how I find a specific +word
  • That is how I leave the -word out of the results
  • “That is how I can find the whole phrase”

RFC 8987 DHCPv6 Prefix Delegating Relay Requirements

The result's identifiers

  • Result code in IS VaVaI

    <a href="https://www.isvavai.cz/riv?ss=detail&h=RIV%2F46747885%3A24220%2F21%3A00008450" target="_blank" >RIV/46747885:24220/21:00008450 - isvavai.cz</a>

  • Result on the web

    <a href="https://rfc-editor.org/rfc/rfc8987.txt" target="_blank" >https://rfc-editor.org/rfc/rfc8987.txt</a>

  • DOI - Digital Object Identifier

    <a href="http://dx.doi.org/10.17487/RFC8987" target="_blank" >10.17487/RFC8987</a>

Alternative languages

  • Result language

    angličtina

  • Original language name

    RFC 8987 DHCPv6 Prefix Delegating Relay Requirements

  • Original language description

    This document describes operational problems that are known to occur when using DHCPv6 relays with prefix delegation. These problems can prevent successful delegation and result in routing failures. To address these problems, this document provides necessary functional requirements for operating DHCPv6 relays with prefix delegation. It is recommended that any network operator using DHCPv6 prefix delegation with relays ensure that these requirements are followed on their networks. Document is result of international cooperation and has been published as international standard containing necessary requirements needed for successful prefix delegation. This is essential for working IPv6 connectivity and it might help to ease process of migration between legacy IPv4 protocol to modern IPv6 protocol. Due to this, it has potential to impact the whole industry of Internet Service Providers (ISP). Now a vendors of devices acting in role of DHCPv6 relay do have single document with guidance how to properly implement such function in standard way. As it is written in standard track of Internet Engineering Task Force it is freely accessible for everyone so every vendor can make intercompatible solution.

  • Czech name

  • Czech description

Classification

  • Type

    O - Miscellaneous

  • CEP classification

  • OECD FORD branch

    10201 - Computer sciences, information science, bioinformathics (hardware development to be 2.2, social aspect to be 5.8)

Result continuities

  • Project

  • Continuities

    I - Institucionalni podpora na dlouhodoby koncepcni rozvoj vyzkumne organizace

Others

  • Publication year

    2021

  • Confidentiality

    S - Úplné a pravdivé údaje o projektu nepodléhají ochraně podle zvláštních právních předpisů