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

Alvaro Retana <> Thu, 09 April 2020 15:52 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D4E7C3A0AE9; Thu, 9 Apr 2020 08:52:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vLJrr75Y_U9L; Thu, 9 Apr 2020 08:52:54 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::435]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A91A53A0ADA; Thu, 9 Apr 2020 08:52:53 -0700 (PDT)
Received: by with SMTP id s8so12467547wrt.7; Thu, 09 Apr 2020 08:52:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=eArbMDPdTwyuP/Asfiln3+2b98uzuMwiMC0ASHn5lDo=; b=OFw69b0RzeBlyHNYRVclh1xl5o3t5B8IUEImHpMRB0YoRpoTvOWACeMWmtjfYiG1mU Uc+oQQPBrUALalmIORvr6w+OVQ/qBUg5K7TPufFQ2kInMsGcYMiVbdJSgNlhWNDaxLY/ SpcJPBFQS3RoEr8UsOUb6orGEaQj8gD+CbhHCsMhjLiR0BE4rhzO9YOs8KdSTyihhFqG /zr8VIuWtarSSHW4E4JJb7XnN/csh1Vj1ehpStKHczgufHCAfnYgr5aQfZa/cFSeGcOa PXZiNUhyEmITFWxN8/CWW5D9/pskUsFx46a44eI/IM9GifNMExDgfp52WG5H5l/tjilS diGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=eArbMDPdTwyuP/Asfiln3+2b98uzuMwiMC0ASHn5lDo=; b=ALGRhRA4ydnspBHu0B7l/Cno1kO4vOwIKFf4abn2LaISRnlKR0AfxHDl69ZcmixCyK 3k7oqxO9lCsSgx4Tc14TunYIXKYLeHn1GsadTcyedqZ426ii61JOHt8R+uKwvVvSucox kIgSGMKvf2aO+UghX0D6Z1sX/YGfqHRqY0qwzUrLTPmnDWgKuBCb50au9vmXet0T/5U/ s4/9gjPtA6Mj3QFNk46SoipGyLbuezeq8HUAkIwrYUZtfjgPHxOC1ZS+iVqYfi2YjV8D StlExEibhHMOPAsTzBdHlcSr9ap14WewIa1eNrg9/aQHg/Czl+BTL6kDXeoJG0kBYMY9 wpsA==
X-Gm-Message-State: AGi0PuYEIavuHco+tSxPV6BgeSwPV7Zlv9N5PUE+mnrEa9DkIumh7z+i oqIRrjsQj++hy6gDnR8Ei3cMymXaalNdx90QwdY=
X-Google-Smtp-Source: APiQypJbBpzvYKpKJxNLYebHzEQGtR0PK1tFgJVysZwOTJjmCpD1VESHGHGo233Ug59Gej9OCy878odyKJ80r77dqho=
X-Received: by 2002:adf:edd0:: with SMTP id v16mr14507405wro.113.1586447572133; Thu, 09 Apr 2020 08:52:52 -0700 (PDT)
Received: from 1058052472880 named unknown by with HTTPREST; Thu, 9 Apr 2020 08:52:51 -0700
From: Alvaro Retana <>
In-Reply-To: <>
References: <> <>
MIME-Version: 1.0
Date: Thu, 9 Apr 2020 08:52:51 -0700
Message-ID: <>
Cc: "<>" <>,,
Content-Type: multipart/alternative; boundary="000000000000fdea5005a2dd9b79"
Archived-At: <>
Subject: Re: [ieee-ietf-coord] Augmentation of ieee802-dot1q-bridge (draft-ietf-pim-igmp-mld-snooping-yang)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 09 Apr 2020 15:52:56 -0000


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.



On April 8, 2020 at 7:25:03 PM, ROBERT GROW ( wrote:


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 <> 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.




ieee-ietf-coord mailing list