[bess] Update to draft-ietf-bess-l2l3-vpn-mcast-mib-10

Hiroshi Tsunoda <tsuno@m.ieice.org> Sun, 27 August 2017 18:28 UTC

Return-Path: <dr.h.t@ieee.org>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0490132A18 for <bess@ietfa.amsl.com>; Sun, 27 Aug 2017 11:28:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ieee-org.20150623.gappssmtp.com
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 OxgBVr9j_mCo for <bess@ietfa.amsl.com>; Sun, 27 Aug 2017 11:28:33 -0700 (PDT)
Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DEBC132707 for <bess@ietf.org>; Sun, 27 Aug 2017 11:28:33 -0700 (PDT)
Received: by mail-qt0-x22e.google.com with SMTP id x36so17159226qtx.2 for <bess@ietf.org>; Sun, 27 Aug 2017 11:28:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee-org.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:from:date:message-id:subject:to:cc; bh=yc3zic7P570VrHpuH3lDTu3CLhFcm53mAUHiHoZuXAU=; b=DAIHK4NUu+XxKTV4MhTjbdPfWFHKfU1dFQ56j7LY8nWe/40yeLnWmqklTGbRIJAAdA ZEw/Bv0TxHjnQe3lRcR0p8JLKUKs3Apk11/sBMn97s08rzdPFAwZmjf3FUjB0gfz2CeD SzvK8QQFKNQ//7pq4sI9xZ/3Yu7nHk/J/0SBI4aBmRAgxhnXhisFJDHVj2IhcnsaCh0F jlxiQkhVA8o2iN1VtTG4yu01YcRO4p7xU+EZhX+kNOov96oIJuAlmBqda9bqsytqorXK EhGw+eQmRmIp//5klhew+Is1fS57bq6f12pNCJPEL4j2V+1Dvc4jZmXlrR0dQeb6BkQV w2MQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to:cc; bh=yc3zic7P570VrHpuH3lDTu3CLhFcm53mAUHiHoZuXAU=; b=h8RZkE7IGaBdyIDvmvpJfAcftHupSsmuLmm95cMIBwfHNHebOY+mXLHOUC9Z5fqUxv gYyqGSdzJI29zNhAa7/4RFtWN2hXst12w3V+gT1IdSyRV/q8A5vgCwwfU9L+p4TsKwBv 9vsDJM5+GCRXH8NTB++8GmZgH/g+Xdd/ByuxNMOdCLAZYwr4gxBVL1gmUAqtUJad37Jx jNTuVAdJiaNxM9L4C+SFycGPUO709U+oSbQivHBZAI6vSwVy3NNmB7SbjrkYuHf9y1SN as+tO4uuuVnPz5yoPKFcgpuJEqr+oe2ZbXC2aWA5M5dXXTTwbkgrhfueSGRE1Zvc+88u 2oOg==
X-Gm-Message-State: AHYfb5iH14YefITBEe3dYRu2gFzmLjWJD599vNIKe7jKs2POyrGg95eA T/2z49/gutTUCZAvi0jXQ6Ia394Tnk7W
X-Received: by 10.200.54.219 with SMTP id b27mr6979048qtc.27.1503858512533; Sun, 27 Aug 2017 11:28:32 -0700 (PDT)
MIME-Version: 1.0
Sender: dr.h.t@ieee.org
Received: by 10.140.101.177 with HTTP; Sun, 27 Aug 2017 11:27:52 -0700 (PDT)
From: Hiroshi Tsunoda <tsuno@m.ieice.org>
Date: Sun, 27 Aug 2017 20:27:52 +0200
X-Google-Sender-Auth: eeUSrI-jJHaXz3TFZWowfxjnuRI
Message-ID: <CAPbjwkwajmkSJFLxk2Fk-F4zMROv_cG95XM9oE55W0J9RZQ6qA@mail.gmail.com>
To: Glenn Mansfield Keeni <glenn@cysols.com>
Cc: Mach Chen <mach.chen@huawei.com>, "mib-doctors@ietf.org" <mib-doctors@ietf.org>, "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>, "EXT - thomas.morin@orange.com" <thomas.morin@orange.com>, Martin Vigoureux <martin.vigoureux@nokia.com>, "bess@ietf.org" <bess@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/XIiXLEa0Sm9YjgCtWCLSg3u83n4>
Subject: [bess] Update to draft-ietf-bess-l2l3-vpn-mcast-mib-10
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Aug 2017 18:28:36 -0000

Dear Glenn,

Thank you for your comments and for waiting for the update.
I posted a new revision (-10) as follows.

URL:
       https://www.ietf.org/internet-drafts/draft-ietf-bess-l2l3-vpn-mcast-mib-10.txt
Htmlized:
       https://tools.ietf.org/html/draft-ietf-bess-l2l3-vpn-mcast-mib-10
Htmlized:
       https://datatracker.ietf.org/doc/html/draft-ietf-bess-l2l3-vpn-mcast-mib-10
Diff:
       https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-l2l3-vpn-mcast-mib-10

In the new revision, the following changes are made.
 - Updated the description of following TC and objects
   in order to clarify the role of this MIB and to improve
   the readability
    -- L2L3VpnMcastProviderTunnelId
    -- l2L3VpnMcastPmsiTunnelAttributeTable
 - Removed some redundant expressions
 - Updated compliance statements

Please see the responses for your comments
in the followings.

2017-07-09 14:11 GMT+02:00 Glenn Mansfield Keeni <glenn@cysols.com>om>:
>   L2L3-VPN-MCAST-TC-MIB:112: [5] {type-without-format} warning: type
>   `L2L3VpnMcastProviderTunnelId' has no format specification
> This may be avoided by specifying a format in which the
> L2L3VpnMcastProviderTunnelId should be printed.
> Is there a preferred format? How will this be printed?
> One continuous octet string?

The size and format of TunnelID depends on Tunnel Type.
and no preferred format is exist as of now.
Therefore, I have decided to not give format specification
to L2L3VpnMcastProviderTunnelId.

> A. The l2L3VpnMcastPmsiTunnelAttributeTable needs all of the following
>    four MOs as index for its rows
>              l2L3VpnMcastPmsiTunnelAttributeFlags,
>              l2L3VpnMcastPmsiTunnelAttributeType,
>              l2L3VpnMcastPmsiTunnelAttributeLabel,
>              l2L3VpnMcastPmsiTunnelAttributeId
>    The l2L3VpnMcastPmsiTunnelAttributeId by itself is inadequate? If yes
>    please explain it to me. Or point to the text that contains the
>    explanation.
> I have been unable to confirm the above from the draft - that is very
> likely due to my lack of understanding of the l2L3VpnMcast technology.

According to Sec. 7.4.1.1 of RFC6513,
P-tunnel is identified by its type and id.
Thus, in the latest revision, the following two objects are used as
index of the table.
       l2L3VpnMcastPmsiTunnelAttributeType,
       l2L3VpnMcastPmsiTunnelAttributeId

Thanks in advance,

-- tsuno