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

"Rob Wilton (rwilton)" <rwilton@cisco.com> Wed, 15 April 2020 14:02 UTC

Return-Path: <rwilton@cisco.com>
X-Original-To: ieee-ietf-coord@ietfa.amsl.com
Delivered-To: ieee-ietf-coord@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B98F23A08CB; Wed, 15 Apr 2020 07:02:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.599
X-Spam-Level:
X-Spam-Status: No, score=-9.599 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, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=Mh+y7FlZ; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=jddbmrH5
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KPNTLdGFjxU3; Wed, 15 Apr 2020 07:02:33 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 448B23A08E5; Wed, 15 Apr 2020 07:02:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=44210; q=dns/txt; s=iport; t=1586959348; x=1588168948; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=SGvI/hugYFEhPY7YyYa4RAxm7I3Xl2B7U5+rr3Bn6cg=; b=Mh+y7FlZ9mr26VHN+PS2GO1ooj6c40OxprlKxLb0A6cIdXSxO71CPQZf P6FWKHOCnUccO5m0u3dJImXDDd8Fwy6B0PTQi71CvE6uTsyT5DtdmruOm mB9halG2AZx4wf8SZEEuTWyyRqnDkueXr0a6+SWUR//mD4sJ5bXnftAp3 E=;
IronPort-PHdr: =?us-ascii?q?9a23=3AQC5gtBdhF6LT5wcWrMW08Co6lGMj4e+mNxMJ6p?= =?us-ascii?q?chl7NFe7ii+JKnJkHE+PFxlwGRD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFn?= =?us-ascii?q?pnwd4TgxRmBceEDUPhK/u/dTM7GNhFUndu/mqwNg5eH8OtL1A=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ASAAB5E5de/4gNJK1mGgEBAQEBAQE?= =?us-ascii?q?BAQMBAQEBEQEBAQICAQEBAYFoBAEBAQELAYEkLyQsBWxYIAQLKgqEEoNGA4p?= =?us-ascii?q?pgl+Jco4ygS6BJANQBAoBAQEMAQEYAQoKAgQBAYREAheBbSQ1CA4CAwEBCwE?= =?us-ascii?q?BBQEBAQIBBQRthVYMhXABAQEBAwEBEBEKEwEBLAsBDwIBCBEEAQEhAQYDAgI?= =?us-ascii?q?CHwYLFAkIAgQBDQUIGoMFgX5NAy4BAwujSgKBOYhidYEygwABAQWBRkGDHg0?= =?us-ascii?q?Lgg4DBoE4AYJiiVMagUE/gRFDgU9+PoIeSQEBAgEBgWMrCYJcMoItkSCGDSS?= =?us-ascii?q?KI452MkkKgkKHfosShGCCVIhGkRSPXIk3gj6QXwIEAgQFAg4BAQWBUwE3gUE?= =?us-ascii?q?PB3AVO4JpUBgNkTQkDBcVgzuFFIVBdAKBJ40MAYEPAQE?=
X-IronPort-AV: E=Sophos;i="5.72,387,1580774400"; d="scan'208,217";a="463737543"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 15 Apr 2020 14:02:27 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by alln-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 03FE2Q6M009774 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 15 Apr 2020 14:02:26 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 15 Apr 2020 09:02:26 -0500
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 15 Apr 2020 10:02:25 -0400
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 15 Apr 2020 09:02:25 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=gDnpcRGsYkoACkmqaXM6Y3RtyDeUZCd8spI6sdCl67iRZKS7gUvth1zVM7wJFeJu0fjVSLDn4bIVSWCapL8yUjeoOGJtLQow6V5/StwmZs2rgY5iZDHB7eCSuYvTrPI38p8svz0W1+NCho+uXqvlwNdZY+OzWPupHFqknaIUqVhXoTWRaPNFQtBf+czmb2MVhHUflenYoG95hQuQ4ywmvugR2vl4oGOfLSpUA8xxbMn8n0mlkcZ2E8o2vjYrNQUSySCc47+KtjeJ7Aybl/reJtVAzMHR0wnP7TChHlLKnSs4LxIVOPyIhRY+w4m62BKTYj2Dn+a6EFARuHQYVDBezA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SGvI/hugYFEhPY7YyYa4RAxm7I3Xl2B7U5+rr3Bn6cg=; b=EMTwiQNrgoAIIIt7/cDL0zFOl+PP4fPHDvOYUl74USrCPyXY4rgIkFD3zun+GIGnL2dudNl0dLSY5IrEWPGqIoa6wIjzEOsP/11xclxWJi0fAW+YFXWDYZwJFQ2ZIz72qo2xttqnwSVILVMcXQp3tNLlR49IWGapXOIRBfjoms8JolcENIwJMjjzftZMg6uRehrFR2OEquu42N9f2gc6JeEwx//6b0soBc/K9KoXgiChCNKmUzrOh2hUnrdTPKGJrvhdZJLfMZ/4Fh2iwXruzab1SIM2mCWJe6InU+xz4ChrkCkMtfTniPW3aexgBvjXSj5HNirOHqKzUSeqonq6KQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SGvI/hugYFEhPY7YyYa4RAxm7I3Xl2B7U5+rr3Bn6cg=; b=jddbmrH5rcTOXS8AAyXjUAa7Dt+aM8EtQWoW+RHHmqUErGxTZlCgkX+p+JbCsqhfiXmcC65oaSWt0eKWwkj5h+LguFb4182EPO2zzq38uBjy2kdCGx++YN84CKWqfnsZ88SRPwvOX1GsoI6AudCu/7SnCPxL1UNYhLn3wCbdXPA=
Received: from MN2PR11MB4366.namprd11.prod.outlook.com (2603:10b6:208:190::17) by MN2PR11MB4565.namprd11.prod.outlook.com (2603:10b6:208:26a::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2900.26; Wed, 15 Apr 2020 14:02:24 +0000
Received: from MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::3:2164:a8e2:33b3]) by MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::3:2164:a8e2:33b3%5]) with mapi id 15.20.2900.028; Wed, 15 Apr 2020 14:02:24 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Scott Mansfield <scott.mansfield=40ericsson.com@dmarc.ietf.org>, "ROBERT GROW" <bobgrow@cox.net>, Alvaro Retana <aretana.ietf@gmail.com>
CC: "draft-ietf-pim-igmp-mld-snooping-yang@ietf.org" <draft-ietf-pim-igmp-mld-snooping-yang@ietf.org>, "pim-chairs@ietf.org" <pim-chairs@ietf.org>, "<ieee-ietf-coord@ietf.org>" <ieee-ietf-coord@ietf.org>
Thread-Topic: [ieee-ietf-coord] Augmentation of ieee802-dot1q-bridge (draft-ietf-pim-igmp-mld-snooping-yang)
Thread-Index: AQHWDfXM3A5N3Gfi80CJZD0Mh72fi6hv3euAgAEUAoCAACg/AIAB0P+AgAdSv+A=
Date: Wed, 15 Apr 2020 14:02:24 +0000
Message-ID: <MN2PR11MB43660C47BD01D8A5C92D9DCEB5DB0@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <CAMMESsyKhw5XKjDJiQVzp4QVjzR76EQrfz8Y6z3-Rt3k+XMOog@mail.gmail.com> <0CABE8C1-86F8-4E6B-8DCD-7CF28E9C7FBA@cox.net> <CAMMESsxANYX9TEYHaOHfzzB=EmiBzj77UdaOXJ9KZcunAcTOHQ@mail.gmail.com> <6191A5AC-9780-4913-BA24-625142CBE0E7@cox.net> <BL0PR1501MB41300ED16575C60585AED2738BDE0@BL0PR1501MB4130.namprd15.prod.outlook.com>
In-Reply-To: <BL0PR1501MB41300ED16575C60585AED2738BDE0@BL0PR1501MB4130.namprd15.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rwilton@cisco.com;
x-originating-ip: [82.15.79.32]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0a8eeac8-baf4-4a11-8321-08d7e1459fb7
x-ms-traffictypediagnostic: MN2PR11MB4565:
x-microsoft-antispam-prvs: <MN2PR11MB45657C2B9A912D2361B8F3D3B5DB0@MN2PR11MB4565.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0374433C81
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MN2PR11MB4366.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(10009020)(4636009)(396003)(346002)(136003)(39860400002)(376002)(366004)(7696005)(86362001)(76116006)(71200400001)(9686003)(55016002)(4326008)(8676002)(186003)(81156014)(478600001)(5660300002)(53546011)(54906003)(33656002)(26005)(6506007)(966005)(64756008)(66476007)(52536014)(66446008)(110136005)(8936002)(66556008)(316002)(2906002)(66946007); DIR:OUT; SFP:1101;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: NccRLJWseJFjjfTQ0Sb+9nOqf/6Z5TKp00u8RpjPZ2dNCWjDqRC+5xZ2GQ7N+OmVGBkFvvaLOy4zgDaq5fChDNc+UcSUyvCTWYZ1vKrNenwRsmu+tusLb0G8r775ZFhezCTE2pBjNX6jSt+0V/DIiXLL4LmEIatbWqYdTi1BZLvRgORSgOKxO4ImG0xrs98JL+3qiDn9WZXFXgnPTqqVEGFfrNx/NMQccEZp4RL8puoYEJitrUqIFsV1g/CHiA1y3Ve8lTCSjs918ftcGGid3GCWiXx7/OfiRgq5qUWx4SrDtAvXnViaPpCkbme+L/TPfR1QSzftc48Qoc8+D1otcpI6A8Ikplfnp2ruZ/otoKAMn9uGLRd80GHY/JEvnEHwzT/8z+DxP68JrjpBAvlfud1AO3AO5X0eh6lfMaq/yLlYIQSYQ/upR1Ejk8IrzwaZMtxOc3+8LLWwAHOHQFQF9fmoBOSVmMeGiBNSP3VdqXi0FjlTsnwZ4UYXMSCIPXeSQpUfHL9jt8nZb6qWNs788Q==
x-ms-exchange-antispam-messagedata: 30aAeelWmr61o6/4WGwCt/0Sp6bZk7rqdWAJRcUj2C5TsVYRV1qc9mjTwceMLYLWKKYXwvzAO689t1cwRW98EEvWOqFuVTfLiueL7EOkEznkPfcqK6Xzp6VmMNzLhv3z4/SotKR67WQcL7J98GRF6Q==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR11MB43660C47BD01D8A5C92D9DCEB5DB0MN2PR11MB4366namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 0a8eeac8-baf4-4a11-8321-08d7e1459fb7
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Apr 2020 14:02:24.2842 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Dc7sdF1J6JEDVw2WdUTjg/wMXYPyQtO1rBMvw9l2/rkiXSejvKnfYDagPAKMryo57VoNrILoxnwANA+SBa01ng==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4565
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.11, xch-aln-001.cisco.com
X-Outbound-Node: alln-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/CrmvWX3Pf56D_baV9P6e7KOUPNA>
Subject: Re: [ieee-ietf-coord] Augmentation of ieee802-dot1q-bridge (draft-ietf-pim-igmp-mld-snooping-yang)
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <ieee-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ieee-ietf-coord/>
List-Post: <mailto:ieee-ietf-coord@ietf.org>
List-Help: <mailto:ieee-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2020 14:02:36 -0000

+1 to Scott’s comments.

The actual augmentations appear to be:

   augment /dot1q:bridges/dot1q:bridge:
       +--rw igmp-snooping-instance?   igmp-snooping-instance-ref
      +--rw mld-snooping-instance?    mld-snooping-instance-ref

   augment /dot1q:bridges/dot1q:bridge/dot1q:component/dot1q:bridge-vlan/dot1q:vlan:
       +--rw igmp-snooping-instance?   igmp-snooping-instance-ref
       +--rw mld-snooping-instance?    mld-snooping-instance-ref

My presumption is that IEEE/802.1 would be unlikely to define the identifiers “igmp-snooping-instance” and “ld-snooping-instance” and so the risk of using the same name in IEEE would seem to be pretty small?  And Scott has already pointed out that not a protocol issue anyway, just undesirable from a model usability POV.

Regards,
Rob


From: ieee-ietf-coord <ieee-ietf-coord-bounces@ietf.org> On Behalf Of Scott Mansfield
Sent: 10 April 2020 23:01
To: ROBERT GROW <bobgrow@cox.net>et>; Alvaro Retana <aretana.ietf@gmail.com>
Cc: draft-ietf-pim-igmp-mld-snooping-yang@ietf.org; pim-chairs@ietf.org; <ieee-ietf-coord@ietf.org> <ieee-ietf-coord@ietf.org>
Subject: Re: [ieee-ietf-coord] Augmentation of ieee802-dot1q-bridge (draft-ietf-pim-igmp-mld-snooping-yang)

The issue related to namespace is documented in RFC7950…

<snip section 4.2.8>
   If a module augments another module, the XML elements that are added
   to the encoding are in the namespace of the augmenting module.  For
   example, if the above augmentation were in a module with prefix
   "other", the XML would look like:

   XML Encoding Example:

     <user>
       <name>alicew</name>
       <full-name>Alice N. Wonderland</full-name>
       <class>drop-out</class>
       <other:uid>1024</other:uid>
     </user>

   The "augment" statement is covered in Section 7.17<https://tools.ietf.org/html/rfc7950#section-7.17>17>.
</snip section 4.2.8>

It would be best if names of nodes in different augmentations didn’t conflict because then the tree would be easier to understand.  But it isn’t required.

So, bottom line, there isn’t any impact on the IEEE URN or namespace.

Regards,
-scott.

From: ieee-ietf-coord <ieee-ietf-coord-bounces@ietf.org<mailto:ieee-ietf-coord-bounces@ietf.org>> On Behalf Of ROBERT GROW
Sent: Thursday, April 9, 2020 2:17 PM
To: Alvaro Retana <aretana.ietf@gmail.com<mailto:aretana.ietf@gmail.com>>
Cc: <ieee-ietf-coord@ietf.org<mailto:ieee-ietf-coord@ietf.org>> <ieee-ietf-coord@ietf.org<mailto:ieee-ietf-coord@ietf.org>>; pim-chairs@ietf.org<mailto:pim-chairs@ietf.org>; draft-ietf-pim-igmp-mld-snooping-yang@ietf.org<mailto:draft-ietf-pim-igmp-mld-snooping-yang@ietf.org>
Subject: Re: [ieee-ietf-coord] Augmentation of ieee802-dot1q-bridge (draft-ietf-pim-igmp-mld-snooping-yang)

Alvaro:

I haven’t looked at your draft so was responding in general, not in specifics for snooping.  Both IEEE and IETF folk need to be comfortable with maintaining unique YANG management arcs.

For YANG and SNMP, we received an IEEE root assignment.  Within IEEE, extending one of those arcs is a self administered registry, the rules for which are specified in IEEE Std 802.  The YANG rules are in IEEE Std 802d-2017.  A snippet from 802c:

For example, in IEEE Std 802.1Q, a URN value for use in a YANG model would take the following form: urn:ieee:std:802.1Q:yang:{resourceIdentifier}
Or in IEEE Std 802.11, a URN value for use in a YANG model would take the following form: urn:ieee:std:802.11:yang:{resourceIdentifier}
This allows each IEEE standard to define management arcs within their standard.  This relies on IEEE standards being given a unique number, but those numbers are obviously only unique with IEEE, not necessarily globally unique.  When a different standard uses the root arc (like the 802.1Q example quoted and assigns its own resourceIdentifier, the possibility of non unique strings being defined in two different standards gets significantly worse than it is for the one standard.

We simply need to make sure we maintain unique names, and how to document it if there are common roots.  Then decide if that approach needs to be documented in IEEE Std 802.

—Bob


On Apr 9, 2020, at 8:52 AM, Alvaro Retana <aretana.ietf@gmail.com<mailto:aretana.ietf@gmail.com>> wrote:

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<mailto: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<mailto: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<mailto:ieee-ietf-coord@ietf.org>
https://www.ietf.org/mailman/listinfo/ieee-ietf-coord

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