This HTML5 document contains 38 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
dctermshttp://purl.org/dc/terms/
n20http://localhost/temp/predkladatel/
n11http://linked.opendata.cz/resource/domain/vavai/projekt/
n6http://linked.opendata.cz/resource/domain/vavai/riv/tvurce/
n16http://linked.opendata.cz/resource/domain/vavai/subjekt/
n10http://linked.opendata.cz/ontology/domain/vavai/
n7http://linked.opendata.cz/resource/domain/vavai/vysledek/RIV%2F00216305%3A26230%2F12%3APU101896%21RIV13-MV0-26230___/
n14http://linked.opendata.cz/ontology/domain/vavai/riv/kodPristupu/
skoshttp://www.w3.org/2004/02/skos/core#
rdfshttp://www.w3.org/2000/01/rdf-schema#
n3http://linked.opendata.cz/ontology/domain/vavai/riv/
n2http://linked.opendata.cz/resource/domain/vavai/vysledek/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n4http://linked.opendata.cz/ontology/domain/vavai/riv/klicoveSlovo/
n18http://linked.opendata.cz/ontology/domain/vavai/riv/duvernostUdaju/
xsdhhttp://www.w3.org/2001/XMLSchema#
n17http://linked.opendata.cz/ontology/domain/vavai/riv/jazykVysledku/
n12http://linked.opendata.cz/ontology/domain/vavai/riv/aktivita/
n19http://linked.opendata.cz/ontology/domain/vavai/riv/druhVysledku/
n13http://linked.opendata.cz/ontology/domain/vavai/riv/obor/
n15http://reference.data.gov.uk/id/gregorian-year/

Statements

Subject Item
n2:RIV%2F00216305%3A26230%2F12%3APU101896%21RIV13-MV0-26230___
rdf:type
skos:Concept n10:Vysledek
rdfs:seeAlso
http://openwiki.uninett.no/geantcampus:ipv6_oct_2012
dcterms:description
The primary design goal for network address translation was to preserve the IPv4 address space. However, it has allowed to serve for different purposes. NAT allows to operate independent network thus preventing address renumbering when the ISP is changed. The multihoming can be easily run without BGP routing and own AS number. The main drawback is, however, breaking the end-to-end connectivity. Network engineers are usually very strictly against NAT in IPv6 protocol but lack of features in IPv6 - e.g. multihoming without BGP, brought NAT even to IPv6 networks. The presentation aims to map and test current implementations of NAT and NAT66.  The primary design goal for network address translation was to preserve the IPv4 address space. However, it has allowed to serve for different purposes. NAT allows to operate independent network thus preventing address renumbering when the ISP is changed. The multihoming can be easily run without BGP routing and own AS number. The main drawback is, however, breaking the end-to-end connectivity. Network engineers are usually very strictly against NAT in IPv6 protocol but lack of features in IPv6 - e.g. multihoming without BGP, brought NAT even to IPv6 networks. The presentation aims to map and test current implementations of NAT and NAT66. 
dcterms:title
Testing implementations of NAT66 Testing implementations of NAT66
skos:prefLabel
Testing implementations of NAT66 Testing implementations of NAT66
skos:notation
RIV/00216305:26230/12:PU101896!RIV13-MV0-26230___
n10:predkladatel
n16:orjk%3A26230
n3:aktivita
n12:P
n3:aktivity
P(VG20102015022)
n3:dodaniDat
n15:2013
n3:domaciTvurceVysledku
n6:2063395
n3:druhVysledku
n19:A
n3:duvernostUdaju
n18:S
n3:entitaPredkladatele
n7:predkladatel
n3:idSjednocenehoVysledku
174021
n3:idVysledku
RIV/00216305:26230/12:PU101896
n3:jazykVysledku
n17:eng
n3:klicovaSlova
NAT, NAT66, PAT, IPv6
n3:klicoveSlovo
n4:PAT n4:NAT66 n4:IPv6 n4:NAT
n3:kodPristupu
n14:L
n3:kontrolniKodProRIV
[EB23744B7764]
n3:mistoVydani
Helsinki
n3:objednatelVyzkumneZpravy
NEUVEDEN
n3:obor
n13:IN
n3:pocetDomacichTvurcuVysledku
1
n3:pocetTvurcuVysledku
1
n3:projekt
n11:VG20102015022
n3:rokUplatneniVysledku
n15:2012
n3:tvurceVysledku
Grégr, Matěj
n3:verzeVyzkumneZpravy
NEUVEDEN
n20:organizacniJednotka
26230