Re: [MIB-DOCTORS] [bess] Benjamin Kaduk's No Objection on draft-ietf-bess-mvpn-mib-11: (with COMMENT)

Hiroshi Tsunoda <tsuno@m.ieice.org> Sat, 15 September 2018 02:20 UTC

Return-Path: <dr.h.t@ieee.org>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D07D1130E6D for <mib-doctors@ietfa.amsl.com>; Fri, 14 Sep 2018 19:20:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.66
X-Spam-Level:
X-Spam-Status: No, score=-1.66 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ieee.org
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 2tuf6_Ve2VSL for <mib-doctors@ietfa.amsl.com>; Fri, 14 Sep 2018 19:20:48 -0700 (PDT)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 E10FB1277D2 for <mib-doctors@ietf.org>; Fri, 14 Sep 2018 19:20:47 -0700 (PDT)
Received: by mail-lj1-x22c.google.com with SMTP id j19-v6so8935545ljc.7 for <mib-doctors@ietf.org>; Fri, 14 Sep 2018 19:20:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee.org; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=jR8UCl4EyREKxMI94aWdxa1XIjJjn2OKsw7r0HQmf6E=; b=UI5upPJ08jXjTnUzj3GrW9kwSl3cCsNhKi8xIt7UOYwKvrJsGEGAPZoa+SKCRPzycU gbaZ0wTkJHtPf81U6UYw03eiL4mC367AaTgue8EClm1NlbSazQf/740nd6WIrfcwGjJS rZ9BxUenmIngaOAZ2nzCoj3RhrtU6smZdkki8=
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:in-reply-to:references:from :date:message-id:subject:to:cc; bh=jR8UCl4EyREKxMI94aWdxa1XIjJjn2OKsw7r0HQmf6E=; b=aD8+Ha3B2iHdY2AfPb5UTGRZiWsOQwNf6lbFaHkidc+fULt8gwigOqaC20NZ5pI74R zm2X73bVJTflPjXpKOnFUQ4qgNVQZmTt2x342VOJ+yhWlljdm8ppOuCmEJRJAtvewXwf fcoWtGgCeTIcNMwLuGJpMVdxnt6UXQTlGUZ2Z5qiYWOaX8w1d3mCj54I5fPV3w42wIAf KM1Rr4vXa36J8XtzccLa/e+hwtnFadWHWSe1BEfSQ1l0uMvAvJEkzSbQbiUa2kCILTaJ rAU04NztBWe16oXZ7tEoBa9MkRzBlaiWgZOos5ov9DndsM9P5IvizNiY3P8v0hwAD99K QUgA==
X-Gm-Message-State: APzg51CqCZoxtAbsImb2OTvVO52xReM1y6gtgIQ8qWWaEnyO6JXS2OoK FvZdZ/dXj/LtgX/TaFLSnttSMHcHPc5jJHK+aZHBUt63jdM=
X-Google-Smtp-Source: ANB0VdamzAK7xmUkMs9bRmUNsiUzi7WxBOtsTJ5+5ojQbQQemV9VYVtK2QQs50m86oig3s7Nk/i47bRKK89+2zf2VAc=
X-Received: by 2002:a2e:9698:: with SMTP id q24-v6mr4988376lji.35.1536978045756; Fri, 14 Sep 2018 19:20:45 -0700 (PDT)
MIME-Version: 1.0
Sender: dr.h.t@ieee.org
Received: by 2002:a2e:760c:0:0:0:0:0 with HTTP; Fri, 14 Sep 2018 19:20:05 -0700 (PDT)
In-Reply-To: <99bfd3a1-eba7-f0ad-2aef-776f2c8fb471@cysols.com>
References: <153671698701.17065.13377651669195105482.idtracker@ietfa.amsl.com> <99bfd3a1-eba7-f0ad-2aef-776f2c8fb471@cysols.com>
From: Hiroshi Tsunoda <tsuno@m.ieice.org>
Date: Sat, 15 Sep 2018 11:20:05 +0900
X-Google-Sender-Auth: ZdDVMpOOEPYwZGIavnuCYo2Oahk
Message-ID: <CAPbjwkyRObThorf6DqeGtEwLPsgoPj4o85AMQKD0tPZybsN-Gg@mail.gmail.com>
To: Glenn Mansfield Keeni <glenn@cysols.com>
Cc: bess@ietf.org, "mib-doctors@ietf.org" <mib-doctors@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mib-doctors/Oq6_ek1jUalJdqXbspUY_VVY70s>
Subject: Re: [MIB-DOCTORS] [bess] Benjamin Kaduk's No Objection on draft-ietf-bess-mvpn-mib-11: (with COMMENT)
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Sep 2018 02:20:50 -0000

Dear Glenn,

Thank for your advice on the the Security Considerations section.
I am going to revise that section along with your advice.

-- tsuno

2018-09-15 11:07 GMT+09:00 Glenn Mansfield Keeni <glenn@cysols.com>;:
> Dear Tsuno,
>      I agree with Benjamin Kaduk's comment on the Security
> Considerations section. I understand the following sentence copied
> verbatim from The Security Guidelines for IETF MIB modules
>  >>     Some of the readable objects in this MIB module (i.e., objects
>  >>     with a MAX-ACCESS other than not-accessible) may be considered
>  >>     sensitive or vulnerable in some network environments.
> is causing the confusion. The scope of the readable objects restricted
> to "objects with a MAX-ACCESS other than not-accessible" is inadequate
> here.
>
> Please change the "i.e" to "e.g.". That will clear the confusion and
> make the statement accurate.
>
> Glenn
>
>
> On 2018/09/12 10:49, Benjamin Kaduk wrote:
>>
>> Benjamin Kaduk has entered the following ballot position for
>> draft-ietf-bess-mvpn-mib-11: No Objection
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-mib/
>>
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> A general comment that we've been making on lots of documents in this
>> space is that it would be nice to be in a place where the acronym "VPN"
>> implies transport encryption.  It's unclear that it's appropriate to
>> request
>> changes to this specific document toward that end, though.
>>
>> Perhaps I'm confused, but "mvpnAdvtPeerAddr" appears in the security
>> considerations in the list of address-related objects that may have
>> privacy/security impact.  That list is predicated on being "objects with a
>> MAX-ACCESS other than not-accessible", but all the instances of
>> mvpnAdvtPeerAddr I found in the body text were marked as not-accessible.
>> Similarly for mvpnMrouteCmcastGroupAddr, mvpnMrouteCmcastSourceAddrs,
>> mvpnMrouteNextHopGroupAddr, mvpnMrouteNextHopSourceAddrs, and
>> mvpnMrouteNextHopAddr.  (Incidentally, why ar mvpnMrouteCmcastSourceAddrs
>> and mvpnMrouteNextHopSourceAddrs plural with the final 's'?)
>>
>> Perhaps using subsections to separate the various tables' descriptions
>> would aid readability.
>>
>>
>> _______________________________________________
>> BESS mailing list
>> BESS@ietf.org
>> https://www.ietf.org/mailman/listinfo/bess
>>
>
> _______________________________________________
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess