From cgrundemann at oix.org  Fri Apr 11 10:04:13 2025
From: cgrundemann at oix.org (Chris Grundemann)
Date: Fri, 11 Apr 2025 10:04:13 -0600
Subject: [OIX-DDP] OIX-1 Updates for Review
Message-ID: <E53D5E27-4697-440C-8589-A3079B7BC864@getmailspring.com>

Hail OIX DDP!

We are very pleased to share with you a set of potential updates to the OIX-1 standard, proposed by the OIX-1 (IX) Committee based on community feedback.
Please find the redlines attached. This mailing list is the place for comments, questions, objections, and support of these changes. Please reply here - and feel free to encourage other interested parties to do the same.
For now, let's keep the conversation focused on the proposed changes. We will open up discussion for additional changes in the future.
Thanks!
~Chris
(Chair, OIX)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.swcp.com/pipermail/oix-ddp/attachments/20250411/8b34de0b/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DDP-OIX-1-Redline-V3.1.pdf
Type: application/octet-stream
Size: 385128 bytes
Desc: not available
URL: <http://mailman.swcp.com/pipermail/oix-ddp/attachments/20250411/8b34de0b/attachment-0001.obj>

From john.osmon at gmail.com  Fri Apr 11 10:38:44 2025
From: john.osmon at gmail.com (John Osmon)
Date: Fri, 11 Apr 2025 10:38:44 -0600
Subject: [OIX-DDP] OIX-1 Updates for Review
In-Reply-To: <E53D5E27-4697-440C-8589-A3079B7BC864@getmailspring.com>
References: <E53D5E27-4697-440C-8589-A3079B7BC864@getmailspring.com>
Message-ID: <CAF7eHWjYoHJeLyy3dKgzhoLmBj1-39MTsV5EwW4G8zCHbec1UA@mail.gmail.com>

The change from Open-IX to OIX has brought many changes.  This is a great
first step in bringing all of our standards up to date.

I recommend we adopt this draft, and move forward with bringing other OIX
standards to a similar position.

John
(Treasurer, OIX)

On Fri, Apr 11, 2025 at 10:04?AM Chris Grundemann <cgrundemann at oix.org>
wrote:

> Hail OIX DDP!
>
> We are very pleased to share with you a set of potential updates to the
> OIX-1 standard, proposed by the OIX-1 (IX) Committee based on community
> feedback.
>
> Please find the redlines attached. This mailing list is the place for
> comments, questions, objections, and support of these changes. Please reply
> here - and feel free to encourage other interested parties to do the same.
>
> For now, let's keep the conversation focused on the proposed changes. We
> will open up discussion for additional changes in the future.
>
> Thanks!
> ~Chris
> (Chair, OIX)
>
> [image: Sent from Mailspring]
>
> --
> You received this message because you are subscribed to the Google Groups
> "stewards" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to stewards+unsubscribe at oix.org.
> To view this discussion visit
> https://groups.google.com/a/oix.org/d/msgid/stewards/E53D5E27-4697-440C-8589-A3079B7BC864%40getmailspring.com
> <https://groups.google.com/a/oix.org/d/msgid/stewards/E53D5E27-4697-440C-8589-A3079B7BC864%40getmailspring.com?utm_medium=email&utm_source=footer>
> .
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.swcp.com/pipermail/oix-ddp/attachments/20250411/1c90c302/attachment.htm>

From rlaager at wiktel.com  Fri Apr 11 16:58:39 2025
From: rlaager at wiktel.com (Richard Laager)
Date: Fri, 11 Apr 2025 17:58:39 -0500
Subject: [OIX-DDP] OIX-1 Updates for Review
In-Reply-To: <E53D5E27-4697-440C-8589-A3079B7BC864@getmailspring.com>
References: <E53D5E27-4697-440C-8589-A3079B7BC864@getmailspring.com>
Message-ID: <76faa5b2-6877-4699-8ec2-b694965516fd@wiktel.com>

I don't know exactly why I joined this list. MICE isn't OIX certified or 
anything. But since I got this and read it, I figured I'd pass along 
these comments.

Some notes, in the order they appear in the document. Most of these are 
typographical. The ones that are more than typographical are in bold.

  * Page 7 has musts and shoulds that are not all caps and bold like the
    rest.
  * *$100,000 as a maximum annual revenue for "community supported"
    excludes MICE. And yet, the revenue that MICE takes in just barely
    covers replacing the switching infrastructure every few years as
    needed. We are still relying on donated labor, etc. I'm not sure
    what "community supported" status means, so maybe this doesn't matter.*
  * Physical Interface: There is a "MUST not". You should search for
    those and make them all "MUST NOT" and bold.
  * *Physical Interface:I'm not sure why you disallow speed negotiation.
    If an IX is offering copper, what is wrong with that? (I have no dog
    in this fight. MICE doesn't and I don't personally care.)*
  * Physical Interface: Not requiring any specific Ethernet speed is
    good. I saw some comments today from people who said that requiring
    1G was a problem for them.
  * Route Server: "a unique" was correct; the change "an unique" is wrong.
  * Route Server: 2 should start with "That" and "IP" should be capitalized.
  * Route Server: 3 should probably remove the second "that", add a
    comma, and s/onto/to/, so it reads "?That rather than honoring the
    NO-EXPORT community, it ??MUST?? pass that? ?community to the
    connected member / participant."
  * Route Server: In 4, capitalize ip, add periods at the end of "d",
    "e", and "i(i)".
  * Route Server: In "4(i)(ii)", I think "black holing" should be one word.
  * Route Server: editing errors in the "MUST publish the route server
    setup" bit, specifically "on a website available". It was probably
    fine as written originally, "on a publicly available website" which
    matches everything else like that.
  * *You give a sample ACL for BGP culling, but is that actually listed
    as a requirement anywhere? It should be at least a SHOULD to use
    that for maintenance.*

-- 
Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.swcp.com/pipermail/oix-ddp/attachments/20250411/163426db/attachment.htm>