teas

Summary

This session covered the status of various working group documents, ongoing liaison activities, and potential new work areas. Key topics included the progress of several YANG modeling drafts, the "enhanced VPN" discussion, scalability considerations for NRPs, and alignment between network slicing realization and application drafts. Decisions were made on how to proceed with some documents, and action items were assigned to address open issues.

Key Discussion Points

Working Group Document Status: A detailed review of the progress of various drafts, including those nearing working group last call, those already in the RFC editor queue, and those requiring further work. Special attention was given to documents related to ACTN, network slicing, and YANG models.
Enhanced VPN Discussion: A poll was conducted regarding renaming "enhanced VPN" to "NRP-based VPN". The results were inconclusive, leading to a decision to continue the discussion on the mailing list.
VN Type in VN YANG Model: A discussion on whether to explicitly specify the VN type in the VN YANG model, with suggestions to analyze use cases to inform the decision.
URI Format in VN YANG Model: Issues related to URI formatting in JSON examples were discussed, along with a request for assistance in providing valid JSON examples.
RSC 8776bis Updates: Discussions on whether to include a summary of changes in an appendix and how to handle path loss metrics and full LSP routing configuration.
Traffic Engineering LSP YANG Model: The document is under working group last call and encouraged further reviews.
NBI YANG Model: A discussion around the the Topology and AC issues and if per cost support should be added.
NRP Scalability Considerations: A discussion on the scalability of NRPs, including control and data plane aspects, and a call for a scalable deconstruction section in related drafts.
Network Slice Authorization Draft: The document now has clear scopes with the other related draft with fixed.
Network Slice Application Draft: Agreement to include examples of mapping for further clarity in the specification.
NIPI API Model: Updates was presented and guidance was request from chairs to move on to the working group adoption.

Decisions and Action Items

Enhanced VPN Naming: The discussion on renaming "enhanced VPN" to "NRP-based VPN" will continue on the mailing list.
VN Type in VN YANG Model: Analyze use cases in regards to the use cases.
RSC 8776bis Updates: Need to update based on the MPS and then proceed with Last Call.
NBI YANG Model: Incorporate additional documentation for support on per cost.
NBI API Model: The documentation should be completed and clarified before moving forward.

Next Steps

Authors to address the open issues identified for the discussed drafts.
Working group to review documents nearing last call and provide feedback.
Continue discussions on the mailing list for topics like "enhanced VPN" naming and scaling considerations.
Working group to coordinate with other SDOs, such as 3GPP and ORAN, through ongoing liaison activities.
Chair to plan additional meetings to address remaining topics.

Session Date/Time: 10 Nov 2023 14:30

teas

Summary

This meeting covered several drafts related to traffic engineering, network slicing, and topology models. Discussions focused on customer topology intents for network slices, leveraging the TE Topology model for non-TE applications, an MPLS-TE topology model, and bandwidth availability in the context of microwave topologies. A final presentation covered BGP extensions for SR policy in relation to NRP. Several working group adoption polls were taken.

Key Discussion Points

Customer Topology Intent for Network Slices:
- Motivation is for customers to express desired slice service topology for realization and operation hints.
- The goal is to provide hints on how to realize the slice, not to control the slice.
- Concerns were raised about the necessity of prior topology information, mapping customized topologies, the expressiveness of connectivity constructs, and the sufficiency of existing models.
- The draft aims to address similar requirements as ACTN type 2, but with a topology model that includes SLAs.
- It was clarified that the model is complementary to slice service models, not a replacement.
- Resource isolation and reservation aspects were discussed, potentially relating to network resource partitioning using NRPs.
- Referenced RFC 8453 (ACTN/VBN) for historical context.
TE Topology Model for Non-TE Applications:
- The goal is to highlight the applicability of a subset of the TE Topology model for non-TE applications, particularly in network slicing.
- Addressing gaps in RFC 85765 with features from RFC 8795.
- Addressed the concern about the size and complexity of the TE Topology model by emphasizing the optional nature of many attributes.
- Discussed methods for augmenting existing models with TE Topology profiles.
- Addressed the issue of how clients can determine the implemented topology profile on the server.
MPLS-TE Topology Model:
- Focuses on identifying gaps in the MPLS-TE YANG model needed to manage MPLS-TE network slices.
- Aims to augment the packet topology model with MPLS-TE specific aspects.
- Aligned the model with RFC 776's BICS (Behavior, Information, Context, Structure) model.
- Improved the abstract based on feedback.
- Open issues include clarifying that MPLS-TE is a subset of MPLS, supporting MPLS multi-domain, and adding the MPLS label in the record.
Bandwidth Availability:
- Presents a generic bandwidth availability module extracted from a microwave topology draft.
- Aim is to understand what bandwidth availability means across technologies and how it ties to topologies.
- Intended as informational, providing bandwidth status, and not enforcement.
- Discussed reporting bandwidth availability in microwave links, considering weather conditions.
- Considered other areas for YANG bandwidth availability modeling, potentially M&A, TVR, or RAW (Debt Net).
BGP Extensions for SR Policy:
- Addresses associating an NRP ID with an SR policy candidate path via BGP.
- Defines a new NRP sub-TLV in the BGP tunnel encapsulation attribute.
- Discussed operational considerations, including consistency between SR policies and NRPs.
- Scalability considerations were added, analyzing the impact of increasing the number of NRPs on BGP signaling.

Decisions and Action Items

Customer Topology Intent for Network Slices:
- Action: Refine the draft, address pending comments, and review the draft focusing on hints for validation.
- Decision: Further discussion is needed before working group adoption can be considered.
TE Topology Model for Non-TE Applications:
- Action: Remove geolocation from the draft and reference the standalone RFC instead.
- Decision: Consider making the draft an informational document.
MPLS-TE Topology Model:
- Decision: Assess this model for working group adoption, based on the generally positive feedback.
Bandwidth Availability:
- Action: Scott will contact relevant mailing lists to discuss potentially adopting a single generic radio related YANG model.
- Action: Contact Rob (from ops area) for AD input.
BGP Extensions for SR Policy:
- Action: Monitor IDR working group adoption.

Next Steps

Continue discussion on mailing lists for all drafts.
Address open issues and comments.
Coordinate with other working groups as needed.
Determine the appropriate venue for bandwidth availability modeling in YANG.
Revisit working group adoption for drafts after further revisions and discussions.