IETF Logo Mail Archive

Re: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib read-only

Muly Ilan <muly_i@rad.com> Tue, 04 February 2014 14:49 UTC

Return-Path: <muly_i@rad.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8ED661A0124 for <mpls@ietfa.amsl.com>; Tue, 4 Feb 2014 06:49:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.124
X-Spam-Level:
X-Spam-Status: No, score=-2.124 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_MISMATCH_COM=0.311, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 LCk5mVdPRmbj for <mpls@ietfa.amsl.com>; Tue, 4 Feb 2014 06:49:12 -0800 (PST)
Received: from rad.co.il (mailrelay01-ib1.rad.com [94.188.133.165]) by ietfa.amsl.com (Postfix) with ESMTP id 796561A0100 for <mpls@ietf.org>; Tue, 4 Feb 2014 06:49:11 -0800 (PST)
Received: from Internal Mail-Server by MailRelay01 (envelope-from muly?i@rad.com) with RC4-SHA encrypted SMTP; 4 Feb 2014 16:48:57 +0200
Received: from EXRAD6.ad.rad.co.il (2002:c072:18be::c072:18be) by exrad6.ad.rad.co.il (2002:c072:18be::c072:18be) with Microsoft SMTP Server (TLS) id 15.0.775.38; Tue, 4 Feb 2014 16:49:06 +0200
Received: from EXRAD6.ad.rad.co.il ([fe80::f157:6202:5fc8:a4f0]) by exrad6.ad.rad.co.il ([fe80::f157:6202:5fc8:a4f0%12]) with mapi id 15.00.0775.031; Tue, 4 Feb 2014 16:49:06 +0200
From: Muly Ilan <muly_i@rad.com>
To: Loa Andersson <loa@pi.nu>, "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib read-only
Thread-Index: AQHPIXYk24FW4ft2EUCWup+uSeelLJqlK3Gw
Date: Tue, 04 Feb 2014 14:49:06 +0000
Message-ID: <60814a444d6343b5bc3eab5bbe181a3f@exrad6.ad.rad.co.il>
References: <52F08ED9.5050509@pi.nu>
In-Reply-To: <52F08ED9.5050509@pi.nu>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.114.24.190]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A010203.52F0FDE3.00FB, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 (Unknown)
Cc: "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, "draft-ietf-mpls-tp-te-mib@tools.ietf.org" <draft-ietf-mpls-tp-te-mib@tools.ietf.org>
Subject: Re: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib read-only
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 04 Feb 2014 14:49:13 -0000

Oppose.

In our implementation we need read-write/read-create access for the TE and LSR extensions.

Specifically, the new functionality provided by mplsIdGlobalId, mplsIdNodeId and mplsTunnelExtNodeConfigTable can only be realized by read-write/read-create objects.

Regards,

Muly Ilan

-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
Sent: Tuesday, February 04, 2014 8:55 AM
To: mpls@ietf.org
Cc: mpls-chairs@tools.ietf.org; draft-ietf-mpls-tp-te-mib@tools.ietf.org
Subject: [mpls] seeking consensus on making draft-ietf-mpls-tp-te-mib read-only

Working Group,

We have just recalled draft-ietf-mpls-tp-te-mib from the IESG to the working group for more work. We have a series of comments that are mostly for clarification. However the main reason for recalling the document is that there is one point where we need to confirm working group consensus.

The IETF, the working group and the MIB Doctors are today very reluctant to produce read-write MIB modules. The current draft is read-write for a few objects, this is based on a consensus call for an earlier discussion, however the consensus call was not clear. It can be taken to mean both that we want to go with read-write objects and that we want to see read-only. Is it clear that it has been interpreted differently by different individuals.

The authors and chairs have discussed the issue and we have a rough consensus that we want the MIB module(s) to be read-only.

We therefore are asking the working group if this is OK for the MIB
module(s) in the current document. Please indicate Support or Oppose for this MIB (draft-ietf-mpls-tp-te-mib) to be read-only.

Please send your comments to the working group mailing list before February 18, 2014.

Loa
for the MPLS wg chairs
-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

v2.23.0 | Report a Bug | By Email