Session Date/Time: 07 Nov 2024 09:30

6man

Summary

The 6man working group meeting covered a range of topics, including updates on existing RFCs and drafts, and presentations of new work. Key discussions centered on security considerations for various proposals, particularly regarding extension headers and potential vulnerabilities. Decisions included requests for working group last calls on several drafts, and action items were assigned to authors to incorporate feedback and further refine their proposals.

Key Discussion Points

6724 Update: Ted Lemon raised concerns about the impact of the stub router bit on source address selection, suggesting potential damage if preferred. Action: Ted Lemon to investigate and provide feedback to the list.
IPV6 Server Definition Option: Ron presented an experimental RFC for a new destination option for VPN services. Discussion focused on validating the new extension header, security considerations related to potential injection, and the scope of deployment within limited domains.
Deprecation of Router Alert Option: Ron presented a draft to deprecate the router alert option. Discussion covered potential impact on existing protocols like RSVPTE and MLD, with concerns raised regarding the continued permissibility of router alert usage and security implications.
Carrying Natural Resource Information in IPV6 Extension Headers: Jadeung presented updates on a draft for carrying network resource information. Discussion revolved around terminology alignment with the TIS working group, specifically the use of "network resource partition selector" versus "network resource partition ID," and the impact on MPLS data plane interoperability.
Improving Robustness of Slack to Flash Renumbering Events: Richard presented a draft to improve Slack's robustness. Concerns were raised regarding the removal of the two-hour minimum valid lifetime, potential security risks, and the need for clearer wording on configuration change notifications.
Link-Local Address Changes During Renumbering: Lorenzo presented a draft to address link-local address changes. Discussion focused on implementation challenges, the impact of multiple RAs, and source address selection behavior.
IPV6 Node Requirements: Tim presented an update on the IPV6 node requirements document. Discussion covered type C host requirements, support for DHCPv6, and the challenges of multi-homing support.
The IDEA Reflection Utility: Ron presented a draft for a diagnostic tool. Concerns were raised about the security implications of publicly accessible NATS.
IP Parcels and Advanced Jumbos: Fred presented a draft for IP parcels with extended length field. The proposal was met with skepticism due to concerns on GRO, as well as issues with POSMTU on the internet.

Decisions and Action Items

6724 Update: Advance after review of Ted Lemon's comments.
IPV6 Server Definition Option: Request for working group last call. Ron to address security concerns and incorporate feedback.
Deprecation of Router Alert Option: Request for working group last call. Ron to clarify the abstract and appendix, addressing concerns about existing implementations and permissible usage.
Carrying Natural Resource Information in IPV6 Extension Headers: Chairs to discuss with TIS chairs and consider a joint working group last call after checking with TIS.
Improving Robustness of Slack to Flash Renumbering Events: Richard to add text explaining the rationale for removing the two-hour minimum valid lifetime and the evaluation of associated risks, address the comments about undefined and shoulds, and improve wording on configuration change notifications.
Link-Local Address Changes During Renumbering: Authors to merge this draft with the Slack Renum draft.
IPV6 Node Requirements: Chair will issue an adoption call. Authors to address DHCPv6 requirements, multi-homing and rule 55, and the 5175 flags option.
The IDEA Reflection Utility: Determine the best approach based on further discussion and feedback from the list.
IP Parcels and Advanced Jumbos: Acknowledge the presenter and suggest he participate in the related boff sessions.

Next Steps

Authors to incorporate feedback and revise drafts as needed.
Chairs to initiate working group last calls for selected drafts.
Chairs to coordinate with other working groups (TIS) on related topics.
Continue discussion on the mailing list for unresolved issues.