um resumodo grupode# trabalho# source#packetrou7ng#in ...ceptro.br/spring_overview_nic.pdf ·...
TRANSCRIPT
Um resumo do Grupo de Trabalho Source Packet Rou7ng in Networking (spring)
Carlos Campana [email protected]
O obje7vo deste encontro • Passar um resumo do spring WG – charter, processo, documentos
• Preparação para par7cipação presencial ou remota na próxima reunião do spring WG no IETF 91-‐ em São Paulo – 13 de novembro às 17:00 – outros hubs na região (San7ago, Caracas, Cidade do México, Montevidéu)
O IETF • Internet Engineering Task Force • Formado em janeiro de 1986
– Começa a par7r das a7vidades do governo dos Estados Unidos relacionadas com a ARPANET
– Internet Configura7on Control Board (ICCB) (1979) e Internet Ac7vi7es Board (1983)
• Não foi considerado com algo importante durante muito tempo – bom!!! • Pessoas e não empresas • Um grupo único, auto-‐organizado, informal, orientado a inicia7vas (feitas por
voluntários) bo`om-‐up
“We reject kings, presidents and vo4ng. We believe in rough consensus and running code.” Dave Clark (1992)
Missão • Iden7ficar problemas técnicos e operacionais urgentes na Internet e
propor soluções. • Especificar o desenvolvimento ou u7lização de protocolos e de uma
arquitetura de curto prazo para resolver problemas técnicos para a Internet.
• Fazer recomendações ao IESG (Internet Engineering Steering Group) em relação à padronização e ao uso de protocolos na Internet.
• Facilitar a transferência de tecnologia do IRTF (Internet Research Task Force) para a comunidade a7va da Internet.
• Fornecer um fórum para troca de informações na comunidade da Internet entre fornecedores, usuários, pesquisadores, empresários e gestores de rede
• ...ac7vi7es focused on suppor7ng, upda7ng and maintaining the IETF standards development process. General Area (gen)
• ubiquitous applica7on protocols (e.g., email, HTTP, FTP) and protocols used for Internet infrastructure Applica7ons (app)
• ...IP layer (both IPv4 and IPv6), DNS, mobility, VPNs and pseudowires..., and various link layer technologies. Internet (int)
• Network Management, AAA, and various opera7onal issues facing the Internet such as DNS opera7ons, IPv6 opera7ons, opera7onal security and Rou7ng opera7ons.
Opera7ons & Management (ops)
• ...develops protocols and architectures for delay-‐sensi7ve interpersonal communica7ons...
Real-‐7me Applica7ons and Infrastructure (rai)
• ...responsible for ensuring con7nuous opera7on of the Internet rou7ng system... Rou7ng (rtg)
• ...focused on security protocols...services: integrity, authen7ca7on, non-‐repudia7on, confiden7ality, and access control...key management is also vital.
Security (sec)
• ...works on mechanisms related to end-‐to-‐end data transport... Transport Services (tsv)
Áreas do IETF
Reuniões do IETF Reuniões Recentes • 88th IETF
– November 3-‐8, 2013 – Vancouver, BC, Canada
• 89th IETF – March 2-‐7, 2014 – London, England
• 90th IETF – July 20-‐25, 2014 – Toronto, ON, Canada
Próximas Reuniões • 91st IETF
– November 9-‐14, 2014 – Honolulu, HI, USA
• 92nd IETF – March 22-‐27, 2015 – Dallas, TX, USA
• 95rd IETF – April 3-‐8, 2016 – Buenos Aires, Argen7na (target
loca7on) 3 vezes por ano, não são conferências
Uma sessão de um WG • Se reúnem durante algumas horas nas reuniões do IETF – a maior parte do trabalho acontece na lista – é preciso ler dos I-‐Ds e a lista antes de uma sessão – conselho: escutar e ler as discussões antes de falar
• São transmi7das (one-‐way) e gravadas • Se assinam as folhas azuis
Como par7cipar no IETF? • Entre numa lista de discussão • Acompanhe o que está acontecendo • ..comece a contribuir!!
Monitor
List Par7cipa7on
Authorship
Mee7ng A`endance
Leadership Posi7on
h`ps://www.iev.org/mailman/lis7nfo/spring h`p://www.iev.org/mee7ng/91/remote-‐par7cipa7on.html
O que vale é o mérito técnico das contribuições
O processo de padronização
10
Internet Draws (ID)
Discussion in a WG
WG sends IESG request to publish an ID ‘when
ready’
AD review 2-‐week IETF-‐wide Last-‐
Call IESG review publica7on
as RFC
spring – como começou? • BOF em Berlim – IETF 87 – 29 de julho de 2013 • Stacked Tunnels for Source Rou7ng – status • Casos de uso, discussão • Segment Rou7ng , Source Rou7ng, Source Packet Rou7ng
in Networking • Definição do charter (obje7vos, ações, especificação) • Criação do WG – 25 de outubro de 2013 – sob a área de
rou7ng (rtg) • Chairs: Alvaro Retana e John Scudder
spring WG Charter The ability for a node to specify a forwarding path, other than the normal shortest path, that a par7cular packet will traverse, benefits a number of network func7ons... Source-‐based rou7ng mechanisms... In the context of this charter, 'source' means 'the point at which the explicit route is imposed'. The SPRING working group will define procedures that will allow a node to steer a packet along an explicit route using informa7on a`ached to the packet and without the need for per-‐path state informa7on to be held at transit nodes. The ini7al data planes that will be considered are MPLS and IPv6.
h`p://datatracker.iev.org/wg/spring/charter/
WG Charter (2) There is an assumed trust model such that any node imposing an explicit route on a packet is assumed to be allowed to do so, however administra7ve and trust boundaries may strip explicit routes from a packet. For each data plane technology that SPRING specifies, a security analysis must be provided showing how protecTon is provided against an aUacker disrupTng the network.. ...
WG Charter (3) SPRING should avoid modifica7on to exis7ng data planes that would make them incompa7ble with exis7ng deployments. Where possible, exis7ng control and management plane protocols must be used within exis7ng architectures to implement the SPRING func7on. Any modificaTon of or extension...must be carried out in the working groups responsible for the architecture, data plane, or control or management plane protocol..in co-‐ordinaTon with this working group, but may be done in this working group aZer agreement...
WG Charter (4) The SPRING working group is chartered for the following list of items:
– Iden7fica7on and evalua7on of use cases for SPRING. These use cases must include a defini7on of the data plane for the environment in which they are to be deployed.
– Defini7on of requirements for any new data plane encodings and procedures, required to implement the use cases. Such procedures must include the necessary security considera7ons.
– Defini7on of requirements and if necessary any new control plane mechanism needed to enable the use cases.
– Defini7on of requirements and if necessary management plane mechanisms needed to manage and operate a SPRING enabled network.
The SPRING working group will not work on any mechanisms for use in networks that forward IPv4 packets.
WG Charter (5) Milestones • ✓Jul 2014 One or more documents describing SPRING use cases. • Nov 2014 SpecificaTon of a high-‐level abstract architecture for SPRING. • Dec 2014 Requirements for modifica7ons if any to MPLS architecture to support SPRING use cases. • Jan 2015 Requirements for modifica7ons if any to IPv6 architecture to support SPRING use cases. • Mar 2015 Specifica7on of any required new procedures to support SPRING use cases. • Jul 2015 One or more data plane extension requirements documents, including documen7ng the impact
on exis7ng deployments of the exis7ng data planes. • Jul 2015 One or more control protocol extensions requirements documents. • Jul 2015 Management requirements document. • Nov 2015 Specify the OAM mechanisms needed to support SPRING. • Nov 2015 Document inter-‐working and co-‐existence between the new procedures and the exis7ng
signalling and rou7ng protocols. • Jan 2016 Inter-‐operability reports pertaining to the implementa7on of extensions suppor7ng SPRING. • Feb 2016 Recharter or close WG.
h`p://datatracker.iev.org/wg/spring/documents/
Draws a7vos • Casos de Uso: 3 draws foram adotados (WG documents)
• Arquitetura: Chamada para adoção para 2 draws
Casos de uso • draw-‐iev-‐spring-‐problem-‐statement-‐02 • draw-‐iev-‐spring-‐ipv6-‐use-‐cases-‐01 • draw-‐iev-‐spring-‐resiliency-‐use-‐cases-‐00
spring IPv6: mo7vação • MPLS pode não estar presente em todo lugar – Falta de suporte em alguns segmentos da rede – Escolha de projeto
• MPLS pode não estar pronto para redes IPv6-‐only – draw-‐iev-‐mpls-‐ipv6-‐only-‐gap
Casos de uso: resiliência • Path protec7on • Unmanaged local protec7on – Next-‐hop – Shortest path
• Managed local protec7on – Next-‐hop – Shortest path
Arquitetura • draw-‐filsfils-‐spring-‐segment-‐rou7ng-‐04 • draw-‐filsfils-‐spring-‐segment-‐rou7ng-‐mpls-‐03