rtgwg Meeting Minutes

Summary

The RTGWG meeting at IETF 115 covered updates on several drafts including QSCN model, SRv6 path protection, SRv6 midpoint protection, Generalized IPv6 Tunnel, and Blockchain applications in routing. The meeting also included a presentation and discussion on the SCION architecture. Discussions focused on technical details, interactions with other working groups (SPRING, 6MAN), and potential applicability of the proposed solutions.

Key Discussion Points

QSCN Model Updates: Discussion centered on clarifying the correlation of filters and their operation within classifiers and policy models. Young doctor comments addressed regarding inline classification.
SRv6 Path Protection: The draft was reviewed in LSR but concerns were raised about the lack of SPRING review. The presenter clarified the intent is to address service protection. Key issue is whether it can be progressed within the group or should be taken to other working groups.
SRv6 Egress Protection: Concerns were raised regarding the PSD Sid and its interaction with SPRING. Discussions highlighted the need for further clarity on the impact of the proposed Sid type and backwards compatibility. Concerns also about interaction with c-seed. The group agreed to continue the discussion on the mailing list.
SRv6 Midpoint Protection: The presenter mentioned changes made to the draft following review comments. However, participants highlighted the need for further discussion within SPRING and 6MAN regarding the modifications and potential loop scenarios.
Generalized IPv6 Tunnel: A new tunnel encapsulation was proposed. Concerns were raised about the necessity of defining new encapsulations and the potential for duplication of work done in other working groups like MPLS. Stakeholder feedback from MPLS and NVO needed.
Blockchain Applications: The presentation explored potential uses of blockchain technology in routing protocols, particularly BGP. Suggestions included secure storage of configuration files and policy enforcement. Concerns were raised about the speed of blockchain and its suitability for control loops. Discussion of potential use cases focusing on proving ownership of address prefixes.
SCION Architecture: An update on the SCION architecture was presented, including recently published internet drafts. The need for detailed service specifications and interworking with existing internet infrastructure was emphasized.

Decisions and Action Items

SRv6 Path Protection: Authors to ensure the document is reviewed by the SPRING working group and address their comments.
SRv6 Egress Protection: Authors to initiate discussions in SPRING and 6MAN about the PSD Sid and its implications. Authors to investigate interactions with c-seed.
SRv6 Midpoint Protection: Authors to address comments raised, send an updated version of the draft to SPRING for review, and clarify the interaction with the IGV before convergence.
Generalized IPv6 Tunnel: Authors to consult with the MPLS and NVO communities to gather feedback on the proposal and its potential impact.
Blockchain Applications: Authors to identify a specific focus for the work and provide more concrete details.

Next Steps

Authors of drafts to address comments and feedback received during the meeting.
Drafts to be circulated to relevant working groups (SPRING, 6MAN) for review and discussion.
Further discussion on mailing lists to resolve open issues and questions.

Session Date/Time: 10 Nov 2022 13:00

rtgwg

Summary

The Routing Working Group (rtgwg) meeting featured a series of presentations on topics ranging from network configuration management using machine learning, routing on service addresses, scalable ID-based routing architecture, faster failure detection in IP networks, service deployment using SRv6, and network computing operation. The discussions covered technical aspects, potential challenges, and future directions of each presented work.

Key Discussion Points

Self-Defined Network Assimilation (SNA):
- Automating the process of introducing heterogeneous network devices into a centralized Software-Defined Network (SDN).
- Using machine learning to understand network configuration menus and infer mappings between vendor device models and a unified model.
- Addressing challenges of menu formal heterogeneity, errors, and ambiguities in menus, and bridging the heterogeneity between configuration models.
- Alternative approach of using YANG models for configuration consistency.
Routing on Service Addresses:
- Transitioning from locator-based addressing to an addressing scheme that represents services.
- Replacing DNS resolution with on-path discovery using a shim overlay.
- Use cases included CDN interconnect, subscriber distribution, and multi-homed/multi-domain services.
- Utilizing service announcements with traffic steering constraints.
Scalable ID-Based Routing Architecture (Kira):
- Providing self-organized, robust control plane connectivity for large-scale networks.
- Using an ID-based routing protocol with source routing on top of any link layer.
- Employing a path ID-based forwarding tier to eliminate source routing overhead.
- Implementation and simulation results in topologies up to 200,000 nodes.
Faster Failure Detection in IP Networks:
- Accelerating failure detection for high-performance applications such as IP-based NVMe and cloud computing.
- Leveraging network devices to detect link or network failures and synchronize failure information.
- Notifying local access endpoints through subscription-based mechanisms.
- Discussion on potential performance bottlenecks and the potential for denial of service attacks.
SRv6 for Service Deployment:
- Presenting service deployment using SRv6 (Segment Routing IPv6) policy and its controller in a backbone network.
- A use case example using an Agricultural Bank in China.
- Discussed limitations, where all presented features can potentially be implemented with other technologies that are already available.
SRv6 Intelligent Steering:
- Proposing grouping of SR policies to enhance traffic management during failures.
- Introducing an intelligent steering unit to dynamically switch traffic between policy groups based on network conditions.
Network Computing Operation:
- Offloading compute tasks to network devices (programmable switches) for improved system performance.
- Using a generic sync header to specify data aggregation operations and routing to appropriate processing locations.
- Utilizing service function chaining (SFC) as an example tunneling mechanism.

Decisions and Action Items

Authors to update drafts based on feedback received.
Presenters to share information on the mailing list to continue the discussions.
The WG chairs will help to find the proper place for the "Network Computing Operation" draft.

Next Steps

Authors to revise drafts based on the discussions.
Further discussion to occur on the mailing lists.
Possible presentation of updated material at the next IETF meeting.