From 6f512208b10fefa5bd30084fe000594c10b3f12c Mon Sep 17 00:00:00 2001
From: Brian Pescatore <bpescato@amazon.com>
Date: Fri, 19 Jun 2026 21:31:58 +0000
Subject: [PATCH] Add maxReceivedBgpRoutePrefixesIpv6 to L3BaseGuidance schema

- Add optional IPv6 BGP route prefix limit field (maxReceivedBgpRoutePrefixesIpv6)
- Make maxReceivedBgpRoutePrefixes required and clarify as IPv4
- Make asnRanges, vlanRanges, mtuRanges required
- IPv6 field falls back to the IPv4 value when omitted
---
 .../schemas/connection.yaml                   | 21 ++++++++++++++++++-
 1 file changed, 20 insertions(+), 1 deletion(-)

diff --git a/connection-coordinator/schemas/connection.yaml b/connection-coordinator/schemas/connection.yaml
index 4ee5d23..de9d814 100644
--- a/connection-coordinator/schemas/connection.yaml
+++ b/connection-coordinator/schemas/connection.yaml
@@ -192,13 +192,32 @@ L3BaseGuidance:
       type: array
     maxReceivedBgpRoutePrefixes:
       description: |-
-        Maximum number of BGP route prefixes accepted by the connection.
+        Required. Maximum number of IPv4 BGP route prefixes accepted by the
+        connection.
 
         While not negotiated between providers, providers must be aware that if
         more BGP route prefixes are announced, protocol behavior will be
         undefined.
       format: int32
       type: integer
+    maxReceivedBgpRoutePrefixesIpv6:
+      description: |-
+        Optional. Maximum number of IPv6 BGP route prefixes accepted by the
+        connection.
+
+        While not negotiated between providers, providers must be aware that if
+        more BGP route prefixes are announced, protocol behavior will be
+        undefined.
+
+        If this field is omitted, the value of maxReceivedBgpRoutePrefixes is
+        also used as the IPv6 value.
+      format: int32
+      type: integer
+  required:
+  - asnRanges
+  - vlanRanges
+  - mtuRanges
+  - maxReceivedBgpRoutePrefixes
   type: object
 
 ASNRange: