RE: Gen-ART review of draft-ietf-bfd-mib-18

"Nobo Akiya (nobo)" <nobo@cisco.com> Tue, 29 April 2014 19:06 UTC

Return-Path: <nobo@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCCAC1A097F; Tue, 29 Apr 2014 12:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.152
X-Spam-Level:
X-Spam-Status: No, score=-110.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] 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 0md08NaBolkX; Tue, 29 Apr 2014 12:06:49 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) by ietfa.amsl.com (Postfix) with ESMTP id 17CE41A0792; Tue, 29 Apr 2014 12:06:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2317; q=dns/txt; s=iport; t=1398798408; x=1400008008; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=JAJOJ90lUsDTAnSqJwPDqTxu8hZxx9IW/Tk7n3KX5EQ=; b=iAyNGn3Splg/6W1CjJUmWX+XA4CuHDDyf1kUBFL+OE+eUpqmqGhuVTa9 liuwxMygUc3LzG0IeXWksZ5r1bVy+VLjkiIR5E9g9n5e9nWVIQlyCR5Yy EB5PA45xKigZSyjjSR65yzrbeZk+CFOm023YfvnGefnsDbg7lh8/3GWqS g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjwHAC/3X1OtJV2b/2dsb2JhbABZgmUhT1EGxQ+BJhZ0giUBAQEEOj8MBAIBCBEEAQEBChQJBzIUCQgBAQQBDQUIAYg4AQcFyTMXjh4xBwaDHoEVBJpMkSaDMYIr
X-IronPort-AV: E=Sophos;i="4.97,952,1389744000"; d="scan'208";a="39747614"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-3.cisco.com with ESMTP; 29 Apr 2014 19:06:47 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s3TJ6ljS015380 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 29 Apr 2014 19:06:47 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Tue, 29 Apr 2014 14:06:47 -0500
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: "Black, David" <david.black@emc.com>, Jeffrey Haas <jhaas@pfrc.org>
Subject: RE: Gen-ART review of draft-ietf-bfd-mib-18
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-18
Thread-Index: Ac9i7PyERuk5jZsyQOKSHRHy2Ij/LwAG2CxAABnaMYAAHWa2AAABXuyAAAM2hqA=
Date: Tue, 29 Apr 2014 19:06:46 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941E11775C@xmb-aln-x01.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C437CE3@MX15A.corp.emc.com> <CECE764681BE964CBE1DFF78F3CDD3941E114938@xmb-aln-x01.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712076C437EA9@MX15A.corp.emc.com> <20140429145824.GR1256@pfrc> <8D3D17ACE214DC429325B2B98F3AE712076C437F73@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076C437F73@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.86.244.77]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JUdbstD7A-9QcsobCxKVDK1Sd3Q
Cc: "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>, "Zafar Ali (zali)" <zali@cisco.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 29 Apr 2014 19:06:51 -0000

Hi David,

BFD-MIB-19 with suggested text has just been published.

URL:            http://www.ietf.org/internet-drafts/draft-ietf-bfd-mib-19.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-bfd-mib/
Htmlized:       http://tools.ietf.org/html/draft-ietf-bfd-mib-19
Diff:           http://www.ietf.org/rfcdiff?url2=draft-ietf-bfd-mib-19

Thanks again!

-Nobo

> -----Original Message-----
> From: Black, David [mailto:david.black@emc.com]
> Sent: Tuesday, April 29, 2014 11:38 AM
> To: Jeffrey Haas
> Cc: Nobo Akiya (nobo); tnadeau@lucidvision.com; Zafar Ali (zali); General
> Area Review Team (gen-art@ietf.org); rtg-bfd@ietf.org; ietf@ietf.org; Black,
> David
> Subject: RE: Gen-ART review of draft-ietf-bfd-mib-18
> 
> Jeff - could you work w/Nobo to get the word "historical" included in the
> MIB draft as a characterization of BFD version 0 ?  For example, the following
> text could be added to the introduction:
> 
>    because the BFD version 0 protocol is primarily of historical interest
>    by comparison to the widespread deployment of the BFD version 1
> protocol.
> 
> Thanks,
> --David
> 
> 
> > -----Original Message-----
> > From: Jeffrey Haas [mailto:jhaas@pfrc.org]
> > Sent: Tuesday, April 29, 2014 10:58 AM
> > To: Black, David
> > Cc: Nobo Akiya (nobo); tnadeau@lucidvision.com; Zafar Ali (zali);
> > General Area Review Team (gen-art@ietf.org); rtg-bfd@ietf.org;
> > ietf@ietf.org
> > Subject: Re: Gen-ART review of draft-ietf-bfd-mib-18
> >
> > On Tue, Apr 29, 2014 at 02:00:05AM -0400, Black, David wrote:
> > > With respect to the MIB, this concern is a nit, so I'm ok with going
> > > ahead
> > without
> > > making this change ...
> > >
> > > ... However ...
> > >
> > > Your WG chairs and AD should be concerned that this significant flaw
> > > in BFD version 0 (justifying a "SHOULD NOT use" recommendation) is
> > undocumented.
> >
> > And also un-RFCed.
> >
> > It was a "work in progress" that never fully saw the light of full
> > deployment.  Vendors very quickly moved to version 1 which fixed a
> > critical issue in the state machine.  If any version 0 survives, it's
> > historical and likely to be a source of operational agony rather than a
> useful feature.
> >
> > -- Jeff