Re: [OPS-DIR] Opsdir last call review of draft-ietf-bess-l2l3-vpn-mcast-mib-16

Mahesh Jethanandani <mjethanandani@gmail.com> Wed, 12 September 2018 23:05 UTC

Return-Path: <mjethanandani@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB1D1129C6B; Wed, 12 Sep 2018 16:05:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 oLt89vfJOcLq; Wed, 12 Sep 2018 16:04:59 -0700 (PDT)
Received: from mail-pg1-x542.google.com (mail-pg1-x542.google.com [IPv6:2607:f8b0:4864:20::542]) (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 886A9126F72; Wed, 12 Sep 2018 16:04:59 -0700 (PDT)
Received: by mail-pg1-x542.google.com with SMTP id t84-v6so1791318pgb.5; Wed, 12 Sep 2018 16:04:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=27ulScxlXCetebGonWwhspMWEkw56tRzgnELSv02ktU=; b=iusx2w5Uta68FduetUrzeVAnjUKdFhT5KyC+bcKqs5USOAmTRXLCUuX0N4Y/wNw55Z EE/LMdlc5yv1kr0JbAlNR/lf6WhAEeWvtzeiivK67IKO266ythakV83FqbCVIpAxEiAj wnPzybT9lvy6NzXSZbBYM3E5VEcR81KUnkaHgOgIBz4xA4zSEUvN5X5qms6ErJiNlzjr gEevVQrr+vOfZ4Lf5bLk4KEeTWwokkwAZQxknixvJqA+AIqUFGaAcvqvONiNtDLzSAra i0LOeD5E4c6QIjNfXNDR7IQ8BEnqzYCi9D2VT5hZnMsjFzJvKdMPYvy1+xvzU+nLc6Xs rEAg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=27ulScxlXCetebGonWwhspMWEkw56tRzgnELSv02ktU=; b=hN7V8sJJ3dBY02Q6/lM7PJ228l79kAvToFbeRNXXMzZAm/zft+cn6VLcdTln0HgKv/ qYtScaNPvjwNoIa7kY4w2tp8cRU7EP4GrFbylB3SWwmrFc+v4lp8Smx4WgOax9yLS0/h cNABkfqMW32D6vGUxMiE5O6e8vcWRxayB1b7AksbPc4l4vWaBA9CVehTSVXVzauuh47Z 7Pa3MUcIkE9IZCoIjIyT0mHR8i7L6jnbq+cy/RZ8bB2RW7XCO4ZrhXxZdwOx2NDQfqHs goG7JMkN8eJ/Ox7LST6S4DhIEfP/FJc3LupAgBB7ECEb/jRspiTrDhQyGc7NSW3UrsH4 sloA==
X-Gm-Message-State: APzg51C7pGP4+1QCob8g9uZhsek+GWrGOplF2VegOR2+QaFK/hXSFVmT 2e+XgFRwZ7+DGQLOgARPPSlAno1CpMM=
X-Google-Smtp-Source: ANB0VdZAsEVvbEDvFLcWOAt6j1DjAlNT8LRKLbvedHRw+NGIZoEUoFqh2Z1DtVYvNVFxsU4f1zxoIA==
X-Received: by 2002:a63:c20:: with SMTP id b32-v6mr4404876pgl.400.1536793498650; Wed, 12 Sep 2018 16:04:58 -0700 (PDT)
Received: from [10.2.48.47] ([208.91.2.2]) by smtp.gmail.com with ESMTPSA id c78-v6sm3049763pfc.188.2018.09.12.16.04.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Sep 2018 16:04:57 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <E9B9B3A7-F559-4FDC-9F5D-3177CD6CDE29@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_DA763489-D3D3-466A-B37A-7B644938D8B8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: [OPS-DIR] Opsdir last call review of draft-ietf-bess-l2l3-vpn-mcast-mib-16
Date: Wed, 12 Sep 2018 16:04:56 -0700
In-Reply-To: <153679314596.9420.2183167766015293671@ietfa.amsl.com>
Cc: draft-ietf-bess-l2l3-vpn-mcast-mib.all@ietf.org, ietf@ietf.org, bess@ietf.org
To: ops-dir@ietf.org
References: <153679314596.9420.2183167766015293671@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PfJmpqn_n-EVlETcdipdgoILbBo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Sep 2018 23:05:02 -0000

Arggh!

It is quite clear I do not know what I am doing, and know even less how to fix it :-(

Here is the review that I planned on posting. I do not know how to fix it in data tracker. We can worry about it later.

I have reviewed this document as part of the Operational directorate’s ongoing effort to review all IETF documents being processed by the IESG.  These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review.  Document editors and WG chairs should treat these comments just like any other last call comments.

Document reviewed:  draft-ietf-bess-l2l3-vpn-mcast-mib-16

Summary: 

Ready

Document Abstract:

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes two MIB modules which will be used by other MIB modules for monitoring and/or configuring Layer 2 and Layer 3 Virtual Private Networks that support multicast.

Comments:

The document defines a MIB for use with network management protocols. Other than whether the module is correct and useful or not, which I have little expertise in determining, there are no operating or management considerations that need to be discussed.

Thanks.

Mahesh Jethanandani
mjethanandani@gmail.com



> On Sep 12, 2018, at 3:59 PM, Mahesh Jethanandani <mjethanandani@gmail.com>; wrote:
> 
> Reviewer: Mahesh Jethanandani
> Review result: Ready
> 
> {\rtf1\ansi\ansicpg1252\cocoartf1561\cocoasubrtf600
> {\fonttbl\f0\fswiss\fcharset0 Helvetica;\f1\fmodern\fcharset0 Courier;}
> {\colortbl;\red255\green255\blue255;\red0\green0\blue0;}
> {\*\expandedcolortbl;;\cssrgb\c0\c0\c0;}
> \margl1440\margr1440\vieww10800\viewh11640\viewkind0
> \deftab720
> \pard\pardeftab720\partightenfactor0
> 
> \f0\fs24 \cf0 \expnd0\expndtw0\kerning0
> I have reviewed this document as part of the Operational
> directorate\'92s\'a0ongoing effort to review all IETF documents being processed
> by the IESG. \'a0These\'a0comments were written with the intent of improving
> the operational\'a0aspects of the IETF drafts. Comments that are not addressed
> in last call may be included in AD reviews during the IESG review. \'a0Document
> editors and\'a0WG chairs should treat these comments just like any other last
> call\'a0comments.\ \ Document reviewed:
> \'a0draft-ietf-bess-l2l3-vpn-mcast-mib-16\ \ Summary: \ \ Ready\ \ Document
> Abstract:\ \ \pard\pardeftab720\sl300\partightenfactor0 \cf2
> \outl0\strokewidth0 \strokec2 This memo defines a portion of the Management
> Information Base (MIB) for use with network management protocols in the
> Internet community. In particular, it describes two MIB modules which will be
> used by other MIB modules for monitoring and/or configuring Layer 2 and Layer 3
> Virtual Private Networks that support multicast. \f1\fs26\fsmilli13333 \
> \pard\pardeftab720\partightenfactor0
> 
> \f0\fs24 \cf0 \outl0\strokewidth0 \
> Comments:\
> \
> The document defines a MIB for use with network management protocols. Other
> than whether the module is correct and useful or not, which I have little
> expertise in determining, there are no operating or management considerations
> that need to be discussed.}
> 
> _______________________________________________
> OPS-DIR mailing list
> OPS-DIR@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-dir