Switch to Memorandum rather than Provisional. Link to GEP-3949 for the Mesh resource, and define that the API will be different GEPs.

Signed-off-by: Flynn <[email protected]>

Author: kflynn

geps/gep-3792/index.md

@@ -1,10 +1,17 @@
 # GEP-3792: Out-of-Cluster Gateways
 
 * Issue: [#3792](https://github.com/kubernetes-sigs/gateway-api/issues/3792)
-* Status: Provisional
+* Status: Memorandum
 
 (See [status definitions](../overview.md#gep-states).)
 
+The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
+"SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this
+document are to be interpreted as described in BCP 14 ([RFC8174]) when, and
+only when, they appear in all capitals, as shown here.
+
+[RFC8174]: https://www.rfc-editor.org/rfc/rfc8174
+
 ## User Story
 
 **[Chihiro] and [Ian] want a way for out-of-cluster Gateways to be able to
@@ -19,6 +26,10 @@ cluster, for various reasons which are out of the scope of this GEP. [Chihiro]
 and [Ian] want to be able to use these out-of-cluster proxies effectively and
 safely, though they recognize that this may require additional configuration.
 
+This GEP defines the problems that need to be solved to allow out-of-cluster
+Gateways (OCGs) to usefully participate in a GAMMA-compliant in-cluster mesh.
+The API to actually solve these problems will be defined in a future GEP.
+
 [Chihiro]: https://gateway-api.sigs.k8s.io/concepts/roles-and-personas/#chihiro
 [Ian]: https://gateway-api.sigs.k8s.io/concepts/roles-and-personas/#ian
 [Ana]: https://gateway-api.sigs.k8s.io/concepts/roles-and-personas/#ana
@@ -227,39 +238,23 @@ the same configuration, or you'll need to provide a single Route with multiple
 
 ## API
 
-Most of the API work for this GEP is TBD at this point, but there are two
+The API for OCG support will be defined in future GEPs, but there are a two
 important points to note:
 
-First, Gateway API has never defined a Mesh resource because, to date, it's
-never been clear what would go into it. This may be the first configuration
-item that causes us to need a Mesh resource.
+1. Gateway API has never defined a Mesh resource because, to date, it's never
+   been clear what would go into it. With the conformance work in progress and
+   with OCG support desired, we clearly will need a Mesh resource. The Mesh
+   resource is defined in [GEP-3949](../gep-3949/index.md).
 
-Second, since the API should affect only Gateway API resources, it is not a
-good candidate for policy attachment. It is likely to be much more reasonable
-to simply provide whatever extra configuration we need inline in the Gateway
-or Mesh resources.
+2. Since the API should affect only Gateway API resources, it is not a good
+   candidate for policy attachment. It is likely to be much more reasonable to
+   simply provide whatever extra configuration we need inline in the Gateway
+   or Mesh resources.
 
 ## Graduation Criteria
 
 In addition to the [general graduation
-criteria](../concepts/versioning.md#graduation-criteria), this GEP must also
-guarantee that **all four** of the problems listed above need resolutions, and
-must have implementation from at least two different Gateways and two
-different meshes.
-
-### Gateway for Ingress (North/South)
-
-### Gateway For Mesh (East/West)
-
-## Conformance Details
-
-#### Feature Names
-
-This GEP will use the feature name `MeshOffClusterGateway`, under the
-assumption that we will indeed need a Mesh resource.
-
-### Conformance tests
-
-## Alternatives
-
-## References
+criteria](../concepts/versioning.md#graduation-criteria), before any GEP
+defining an API for OCG support graduates to Standard it MUST also demonstrate
+a resolution to **all four** of the problems listed, and it MUST have
+implementation from at least two different Gateways and two different meshes.

geps/gep-3792/metadata.yaml

@@ -20,10 +20,14 @@ relationships:
   extendedBy: {}
   # seeAlso indicates other GEPs that are relevant in some way without being
   # covered by an existing relationship.
-  seeAlso: {}
+  seeAlso:
+  - number: 3949
+    name: Mesh Resource
+    description: Defines the Mesh resource for managing service mesh configurations.
 # references is a list of hyperlinks to relevant external references.
 # It's intended to be used for storing GitHub discussions, Google docs, etc.
-references: {}
+references:
+  - https://www.rfc-editor.org/rfc/rfc8174
 # featureNames is a list of the feature names introduced by the GEP, if there
 # are any. This will allow us to track which feature was introduced by which GEP.
 # This is the value added to supportedFeatures and the conformance tests, in string form.