Re: [mpls] Review of draft-ietf-mpls-tp-linear-protection-mib-11

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 16 January 2017 19:48 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27AD3129648; Mon, 16 Jan 2017 11:48:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 601uLLV2s-fh; Mon, 16 Jan 2017 11:48:36 -0800 (PST)
Received: from mail-pg0-x234.google.com (mail-pg0-x234.google.com [IPv6:2607:f8b0:400e:c05::234]) (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 668BD1299E1; Mon, 16 Jan 2017 11:48:36 -0800 (PST)
Received: by mail-pg0-x234.google.com with SMTP id 14so17808577pgg.1; Mon, 16 Jan 2017 11:48:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=6b0QG/jMw+ViFyU/90bTWq9rgEjUt0nvJRzuXuLMK4k=; b=XMpadas3dGlOa1xLe1K8IGAYzlZg/5EPpESlsTgmC3JsLa4vg4S+bCa+bj+Rmt0fFW ZQiR2SaIqbUDp/qUGEOBnU8q+Ww0OLg65UnNBqg1nitfVt7Rdt3xYskAy6XBs1v8IQF1 +MqSS2GCiiY5WNDnVGr6D1nnMSEzfg8CHQxB3YuNcHid4PU7pt4Td6pecI0vaD9oMdxU TSW9l2419KErj+AecRTRykwRXfyRZh/rFj3u0iMb346OGwnv1hKzUSIdxdcTKeqJutPO 0G5FGqhiM99hQ4hG9ZyMKh8Z1sgx9I4wye/Voh8s8uv1vmK1L0Y1SzEXnoKu06xjp9e1 PD9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=6b0QG/jMw+ViFyU/90bTWq9rgEjUt0nvJRzuXuLMK4k=; b=KNnyjH7MHSVXRQvW+F2UiFR48LhHYbJ0d1ZCQnWzYU2ZCyYOgMDnxFfOcQnxHePV/v DS6sf1i6oXbXjAMZN+5+rSmm/CGnZKwSnfwcvULvoqGm1LuhZeunIdGVihYNp7eDSyJv pt2P6ABaIcgu2BiKmn2mfeLazTmKIy8Ordj6pL1fSXfl3jKwxloeJylb0xO1sTdFUzn6 IfoZdVYEliX3DFJvnOn30Srnpa4RZ5/MUWQ3kC+/g5I8+O9RBBx8j0C7Ye7reo72I7Ro ZjnxlgGTMxwj/T6a23GJL9pdJM0D8OlVeEKI7Gj71Hb44QefJT9GgMMOaz3p6rslEPbt 8OvA==
X-Gm-Message-State: AIkVDXKfuFxYWSTdeF21pDvAc3jNvRGikrnhq7zk2W1YDo4c3dVVZJNBVWKmjNs6ccbGeA==
X-Received: by 10.99.127.71 with SMTP id p7mr41753821pgn.125.1484596115775; Mon, 16 Jan 2017 11:48:35 -0800 (PST)
Received: from ?IPv6:2406:e007:4961:1:28cc:dc4c:9703:6781? ([2406:e007:4961:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id u82sm48787854pfd.7.2017.01.16.11.48.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Jan 2017 11:48:35 -0800 (PST)
To: "BRUNGARD, DEBORAH A" <db3546@att.com>, Benoit Claise <bclaise@cisco.com>, Loa Andersson <loa@pi.nu>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148451784736.3226.15889507299394185360.idtracker@ietfa.amsl.com> <a35bfb84-091b-a408-9a53-0b6dbd5cd003@pi.nu> <54feb39c-0e5b-9c12-0ae2-d5757316c9c3@cisco.com> <F64C10EAA68C8044B33656FA214632C85DE45354@MISOUT7MSGUSRDE.ITServices.sbc.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <9ce42a7d-64d3-4003-93ee-9119afc78283@gmail.com>
Date: Tue, 17 Jan 2017 08:48:31 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <F64C10EAA68C8044B33656FA214632C85DE45354@MISOUT7MSGUSRDE.ITServices.sbc.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/UzTNrBdBt7Zio-XQmgWlRCzlH2I>
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Review of draft-ietf-mpls-tp-linear-protection-mib-11
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jan 2017 19:48:38 -0000

Fair enough.

Regards
   Brian

On 17/01/2017 08:13, BRUNGARD, DEBORAH A wrote:
> Thanks Benoit-
> 
> As Loa confirmed, we don't see this as an update. It's aligned with how we have been doing the MPLS-TP work e.g. RFC7697 has the same wording.
> 
> Thanks Brian for the careful review-
> Deborah
> 
> 
>> -----Original Message-----
>> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Benoit Claise
>> Sent: Monday, January 16, 2017 2:35 AM
>> To: Loa Andersson <loa@pi.nu>nu>; Brian Carpenter
>> <brian.e.carpenter@gmail.com>om>; gen-art@ietf.org
>> Cc: mpls@ietf.org
>> Subject: Re: [mpls] Review of draft-ietf-mpls-tp-linear-protection-mib-11
>>
>> Loa, Brian,
>>> Brian, et.al.,
>>>
>>> We could of course update 3812 (and 3813), though this would probably
>>> lead to another discussion on what updates means.
>>>
>>> What is refereed to is that there is now another preferred method for
>>> configuration - netconf/yang. In fact this draft doe not change 3812 or
>>> propose a change, so there can not be an update. The document is just
>>> noting that there is a change in the environment, and that for the time
>>> being it will use RFC 3812 as specified.
>>>
>>> Maybe Benoit have a take on this?
>> No strong views on updating RFC 3812, but the text in the intro section
>> and the read-only conformance statement (WriteUp mentions: The MIB
>> module has a read-only conformance statement so that vendors and/or
>> network operators can choose to implement/operate the MIB module as
>> read-only.) do the job IMO.
>>
>> Regards, Benoit
>>>
>>> /Loa
>>>
>>> On 2017-01-16 06:04, Brian Carpenter wrote:
>>>> Reviewer: Brian Carpenter
>>>> Review result: Ready with Issues
>>>>
>>>> Gen-ART Last Call review of
>>>> draft-ietf-mpls-tp-linear-protection-mib-11
>>>>
>>>> I am the assigned Gen-ART reviewer for this draft. The General Area
>>>> Review Team (Gen-ART) reviews all IETF documents being processed
>>>> by the IESG for the IETF Chair.  Please treat these comments just
>>>> like any other last call comments.
>>>>
>>>> For more information, please see the FAQ at
>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>
>>>> Document: draft-ietf-mpls-tp-linear-protection-mib-11.txt
>>>> Reviewer: Brian Carpenter
>>>> Review Date: 2017-01-16
>>>> IETF LC End Date: 2017-01-26
>>>> IESG Telechat date:
>>>>
>>>> Summary: Ready with minor issues
>>>> --------
>>>>
>>>> Comment:
>>>> --------
>>>>
>>>> I have not reviewed most details of the MIB module itself. As usual,
>>>> I trust the MIB Doctors.
>>>>
>>>> "We know of a handful of implementations (or intent to implement)."
>>>> Good. It would have been nice to see an Implementation Status section
>>>> under RFC 6982.
>>>>
>>>> Minor issues:
>>>> -------------
>>>>
>>>>    At the time of writing, Simple Network Management Protocol (SNMP)
>>>> SET
>>>>    is no longer recommended as a way to configure MPLS networks as
>>>> was
>>>>    described in RFC 3812 [RFC3812].
>>>>
>>>> RFC3812 is explicit that it should be used for configuration:
>>>>
>>>>    This MIB module should be used in conjunction with the
>>>>    companion document [RFC3813] for MPLS based traffic engineering
>>>>    configuration and management.
>>>>
>>>> RFC3812 has not been formally updated or obsoleted. Therefore, it
>>>> seems
>>>> to me that the present draft should formally update RFC3812 in this
>>>> respect.
>>>>
>>>> Does the same issue apply to RFC3813, whose Abstract also states that
>>>> it is used to configure an LSR?
>>>>
>>>
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>