[OIX-DDP] OIX-1 Updates for Review

[Richard Laager]

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>