Sitemap
A list of all the posts and pages found on the site. For you robots out there is an XML version available for digesting as well.
Pages
Posts
Future Blog Post
Published:
This post will show up by default. To disable scheduling of future posts, edit config.yml
and set future: false
.
Blog Post number 4
Published:
This is a sample blog post. Lorem ipsum I can’t remember the rest of lorem ipsum and don’t have an internet connection right now. Testing testing testing this blog post. Blog posts are cool.
Blog Post number 3
Published:
This is a sample blog post. Lorem ipsum I can’t remember the rest of lorem ipsum and don’t have an internet connection right now. Testing testing testing this blog post. Blog posts are cool.
Blog Post number 2
Published:
This is a sample blog post. Lorem ipsum I can’t remember the rest of lorem ipsum and don’t have an internet connection right now. Testing testing testing this blog post. Blog posts are cool.
Blog Post number 1
Published:
This is a sample blog post. Lorem ipsum I can’t remember the rest of lorem ipsum and don’t have an internet connection right now. Testing testing testing this blog post. Blog posts are cool.
projects
Design and implementation of an In-Network Load-aware Fast Rerouting mechanism
Failures in communication networks affect the quality of the services running on the end-hosts. Although some applications may tolerate a certain delay to resolve the failure, others are highly latency-dependent and need fast solutions for traffic rerouting. Fast Rerouting (FRR) is a mechanism used to quickly reroute traffic upon failures completely in the dataplane. Although there are several works related to FRR, there is no current solution that considers the status of the network to define the backup paths. In this work, we benefit from the In-network computing and programmability to design and implement a mechanism entirely in the dataplane to define backup paths based on the load of the network. The mechanism should be aware of the status of the links in terms of, e.g., end-to-end latency to set the best backup paths. Upon a failure, our solution must fast reroute the traffic to such paths without the control plane help. We will develop the mechanism totally in the dataplane by using P4 and evaluate it using real minimalist scenarios as well as simulations.
Balanceamento de carga utilizando caminhos múltiplos no roteamento de pacotes IP na Internet
Este projeto propõe o desenvolvimento de um extensão ao protocolo BGP, de modo a permitir o balanceamento de carga do tráfego utilizando caminhos múltiplos no roteamento de pacotes IP na Internet.
Uso do HMAC para troca de mensagens seguras numa rede IPv6
Este trabalho propõe o desenvolvimento de um extensão aos protocolos IPv6 e NDP, de modo a permitir um processo de troca de mensagens NDP mais seguro, utilizando algoritmos de hash para identificar e autenticar os nós numa rede IPv6 sem utilizar algoritmos de criptografía assimétricos.
GT-ACTIONS: Ambiente Computacional para Tratamento de Incidentes com Ataques de Negação de Serviço
O projeto visa conceber uma plataforma computacional denominada ACTIONS, para identificação e tratamento em tempo real de ataques Distribuídos de Negação de Serviço (DDoS - Distributed Denial of Service). Além disso, devido à grande capacidade de mudança dos ataques DDoS, que assumem novas características, pretende-se desenvolver uma metodologia para adequar rapidamente os algoritmos para o tratamento de novas versões de ataques.
publications
Paper Title Number 1
Published in Journal 1, 2009
This paper is about the number 1. The number 2 is left for future work.
Recommended citation: Your Name, You. (2009). "Paper Title Number 1." Journal 1. 1(1). http://academicpages.github.io/files/paper1.pdf
Paper Title Number 2
Published in Journal 1, 2010
This paper is about the number 2. The number 3 is left for future work.
Recommended citation: Your Name, You. (2010). "Paper Title Number 2." Journal 1. 1(2). http://academicpages.github.io/files/paper2.pdf
Paper Title Number 3
Published in Journal 1, 2015
This paper is about the number 3. The number 4 is left for future work.
Recommended citation: Your Name, You. (2015). "Paper Title Number 3." Journal 1. 1(3). http://academicpages.github.io/files/paper3.pdf
Paper Title Number 4
Published in GitHub Journal of Bugs, 2024
This paper is about fixing template issue #693.
Recommended citation: Your Name, You. (2024). "Paper Title Number 3." GitHub Journal of Bugs. 1(3). http://academicpages.github.io/files/paper3.pdf
talks
Talk 1 on Relevant Topic in Your Field
Published:
This is a description of your talk, which is a markdown files that can be all markdown-ified like any other post. Yay markdown!
Conference Proceeding talk 3 on Relevant Topic in Your Field
Published:
This is a description of your conference proceedings talk, note the different field in type. You can put anything in this field.
teaching
Switching Technologies
Undergraduate - Computer Network, Federal Institute of Paraiba, CSTRC, 2024
- Link layer (Ethernet)
- Virtual Local Area Network (VLAN)
- Spanning Tree Protocol (STP)
- Etherchannel
- Security in computer network
Data Security
Undergraduate - Systems for the Internet, Federal Institute of Paraiba, CSTSI, 2024
- Information security
- Hash functions
- Cryptography foundations
- Symmetric cryptography
- Asymmetric cryptography
- Public Key Infrastructure
- Transport Layer Security
Computer Network
Master - Information Technology, Federal Institute of Paraiba, Master IT, 2024
- Computer networks foundations
- Software defined network
- Data plane programmability
- Simulation and experimentation