RE: WGLC for BFD base MIB and TC - ends November 8

"Nobo Akiya (nobo)" <nobo@cisco.com> Mon, 11 November 2013 23:15 UTC

Return-Path: <nobo@cisco.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1626C21E809C for <rtg-bfd@ietfa.amsl.com>; Mon, 11 Nov 2013 15:15:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.556
X-Spam-Level:
X-Spam-Status: No, score=-10.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aN8+6zU7obcn for <rtg-bfd@ietfa.amsl.com>; Mon, 11 Nov 2013 15:15:34 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id E3C4311E80D9 for <rtg-bfd@ietf.org>; Mon, 11 Nov 2013 15:15:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3376; q=dns/txt; s=iport; t=1384211734; x=1385421334; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=d7ecQN1f1D+r8CBSaYY8WsMUi/nR0Xu9xd5Yejpc2SU=; b=X5mAo2XCDJVYAaZ0G4vO9knZ1aJ1xR5Yd4W4cEGvsQgOy+2adpCBu2FD Vljd5ABSGrev7Gs0cRYBnXB9+VR56MtQb/HyLsc7rfEI07w4Etet3f2yo uiDEE0ImwZI1IO1fv5CvE23Y9LwEENmVCecHTfjmzAQn/YTZKo7sHPDmu Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFAIxkgVKtJXHB/2dsb2JhbABZgmYhOFO/FoE9FnSCJQEBAQQdHTQLDAQCAQgRBAEBAQoLCQkHMhQJCAIEAQ0FCAEQh2gBDL5NjGaBNIEYMQIFBgSDFoEQA5QuhRCQW4MmgXE5
X-IronPort-AV: E=Sophos;i="4.93,680,1378857600"; d="scan'208";a="283452969"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-6.cisco.com with ESMTP; 11 Nov 2013 23:15:33 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id rABNFXtI027417 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 11 Nov 2013 23:15:33 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0123.003; Mon, 11 Nov 2013 17:15:32 -0600
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, Jeffrey Haas <jhaas@pfrc.org>
Subject: RE: WGLC for BFD base MIB and TC - ends November 8
Thread-Topic: WGLC for BFD base MIB and TC - ends November 8
Thread-Index: AQHO0Owjc7oH/6Jq4EuHfR8yKojndJofizEAgAE2acA=
Date: Mon, 11 Nov 2013 23:15:32 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941DEE18E5@xmb-aln-x01.cisco.com>
References: <20131024190612.GN17538@pfrc> <DF6057A3-735A-41C6-A6CE-A6D473F3E1B2@cisco.com>
In-Reply-To: <DF6057A3-735A-41C6-A6CE-A6D473F3E1B2@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [161.44.213.104]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-bfd>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Nov 2013 23:15:39 -0000

Hi,

Nits have been addressed, and new IDs have been posted (1 taken care of).

http://tools.ietf.org/html/draft-ietf-bfd-mib-15
http://tools.ietf.org/html/draft-ietf-bfd-tc-mib-03

Jeff, if would like me to engage MIB doctors (2), then please let me know. Otherwise I'll assume that you will.

-Nobo
(for BFD base/TC MIB authors)

> -----Original Message-----
> From: rtg-bfd-bounces@ietf.org [mailto:rtg-bfd-bounces@ietf.org] On
> Behalf Of Carlos Pignataro (cpignata)
> Sent: Sunday, November 10, 2013 5:29 PM
> To: Jeffrey Haas
> Cc: rtg-bfd@ietf.org
> Subject: Re: WGLC for BFD base MIB and TC - ends November 8
> 
> BFDers,
> 
> The BFD co-chairs asked me to gauge consensus on this WG Last Call for
> draft-ietf-bfd-mib-14 and draft-ietf-bfd-tc-mib-02. The WGLC ended this
> past Friday.
> 
> In my view, there is good support for these two documents, including from
> implementors, and consensus to move forward and be sent to the IESG.
> 
> Before that, the following needs to be taken into account:
> 1. Fix the Nits identified by idnits [1] [2] 2. Ask the OPS ADs for a MIB Doctor
> review [3] ("after the Working Group Last Call and before the IETF Last Call")
> 
> Thanks,
> 
> - Carlos.
> 
> [1] http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-ietf-bfd-
> mib-14.txt
> [2] http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-ietf-bfd-tc-
> mib-02.txt
> [3] http://www.ietf.org/iesg/directorate/mib-doctors.html
> 
> 
> On Oct 24, 2013, at 3:06 PM, Jeffrey Haas <jhaas@pfrc.org> wrote:
> 
> > This email is to initiate working group last call on the BFD MIB and
> > Textual-Convention documents:
> >
> > http://tools.ietf.org/html/draft-ietf-bfd-mib-14
> > http://tools.ietf.org/html/draft-ietf-bfd-tc-mib-02
> >
> > The last call will complete on November 8, the end of IETF week.  Time
> > will be available during the Vancouver IETF BFD session to discuss
> > last call comments.
> >
> > I will be serving as document shepherd (RFC 4858) for this WGLC.
> >
> > Due to the small nature of the BFD working group and the fact that
> > both working group chairs have contributed to the documents, we have
> > gotten Carlos Pignataro (cpignata@cisco.com) to volunteer to serve as
> > an independent party to gauge working group consensus.
> >
> > In order to facilitate the transparency of this WGLC, please remember
> > to send all comments to the working group mailing list.
> >
> > As is often the case with MIB documents, implementations typically do
> > not exist for the final form of the document.  Typically enterprise
> > MIBs are implemented at some point in the document life cycle and then
> > later the implementor will revise to match the published RFC,
> > including OID code-points assigned by IANA.  Reviewers examining the
> > MIB against deployed implementations are requested to bear in mind
> > implementability of the final document vs. existence proof of the running
> code.
> >
> > Finally, note that no IPR polling has been done for these documents.
> > MIBs, being IETF data models of things that themselves may have IPR,
> > tend not to have IPR against them.  However, if someone is aware of
> > IPR against these documents, please state it for the WG.
> >
> > -- Jeff (for the chairs)