Re: [ieee-ietf-coord] Augmentation of ieee802-dot1q-bridge (draft-ietf-pim-igmp-mld-snooping-yang)

Bob:

I’m adding the authors (and the chairs of the pim WG) who would have a much
better clue about what you’re pointing out than me.

As far as I can see, this is the relevant text:

  import ieee802-dot1q-bridge {
    prefix "dot1q";
  }
…
  augment "/dot1q:bridges/dot1q:bridge" {
…
  augment "/dot1q:bridges/dot1q:bridge"+
    "/dot1q:component/dot1q:bridge-vlan/dot1q:vlan" {

I may of course be completely misunderstanding your point.

Thanks!

Alvaro.

On April 8, 2020 at 7:25:03 PM, ROBERT GROW (bobgrow@cox.net) wrote:

Alvaro:

The management arcs to be used certainly has to be understood.  If the urn
arcs use the ieee root we definitely need additional coordination both with
any IEEE subgroups included in the urn and I expect the RAC will be
interested also.

—Bob Grow

On Apr 8, 2020, at 3:33 PM, Alvaro Retana <aretana.ietf@gmail.com> wrote:

Mostly FYI…

The pim WG has been working on a YANG model to configure and manage
IGMP/MLD snooping devices [1].  The draft has passed WGLC and has been sent
to the IESG for publication — I am the responsible AD and we’re waiting for
the authors to address my comments before moving into IESG Evaluation.

The new module (ietf-igmp-mld-snooping) augments ieee802-dot1q-bridge to
enable snooping on a bridge, or a specific VLAN.

This is the first YANG module that I process which augments an IEEE module,
so I’m sending this note just in case there’s some type of additional
coordination needed.  Please let me know.

Thanks!!

Alvaro.

[1] https://datatracker.ietf.org/doc/draft-ietf-pim-igmp-mld-snooping-yang/

_______________________________________________
ieee-ietf-coord mailing list
ieee-ietf-coord@ietf.org
https://www.ietf.org/mailman/listinfo/ieee-ietf-coord