IETF Logo Mail Archive

Re: [Isis-wg] AD review of draft-ietf-isis-mi-bis-01

Uma Chunduri <uma.chunduri@huawei.com> Mon, 20 March 2017 17:33 UTC

Return-Path: <uma.chunduri@huawei.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8509E12871F; Mon, 20 Mar 2017 10:33:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 YGioiTNXCZMV; Mon, 20 Mar 2017 10:33:44 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A005313157A; Mon, 20 Mar 2017 10:33:28 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DJF91770; Mon, 20 Mar 2017 17:33:26 +0000 (GMT)
Received: from SJCEML702-CHM.china.huawei.com (10.208.112.38) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 20 Mar 2017 17:33:25 +0000
Received: from SJCEML701-CHM.china.huawei.com ([169.254.3.8]) by SJCEML702-CHM.china.huawei.com ([169.254.4.233]) with mapi id 14.03.0235.001; Mon, 20 Mar 2017 10:33:20 -0700
From: Uma Chunduri <uma.chunduri@huawei.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, Alia Atlas <akatlas@gmail.com>, "isis-wg@ietf.org" <isis-wg@ietf.org>, "draft-ietf-isis-mi-bis@ietf.org" <draft-ietf-isis-mi-bis@ietf.org>
Thread-Topic: AD review of draft-ietf-isis-mi-bis-01
Thread-Index: AQHSn0f665ryCG8LmUWtocVGBBHHMKGZVRpQgAB6vwD//4xLIIAAjjCA///P1BCAALjygIADip3QgAADn7A=
Date: Mon, 20 Mar 2017 17:33:19 +0000
Message-ID: <25B4902B1192E84696414485F5726854018886CD@SJCEML701-CHM.china.huawei.com>
References: <CAG4d1reSNUyDZwUN1tB4zJAJcfs40618_x5DpFofr99cQc3B0g@mail.gmail.com> <43be9b6ac3fa41708303a2a352360ab4@XCH-ALN-001.cisco.com> <25B4902B1192E84696414485F572685401886050@SJCEML703-CHM.china.huawei.com> <d35ee990ce104caaad61bd389c941dc4@XCH-ALN-001.cisco.com> <25B4902B1192E84696414485F57268540188607C@SJCEML703-CHM.china.huawei.com> <66747b32bd0a4bb5a920736eca0b491a@XCH-ALN-001.cisco.com> <25B4902B1192E84696414485F57268540188611B@SJCEML703-CHM.china.huawei.com> <e37f318da16f4a5d970e42692dcbc53f@XCH-ALN-001.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.213.49.150]
Content-Type: multipart/alternative; boundary="_000_25B4902B1192E84696414485F5726854018886CDSJCEML701CHMchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.58D01267.01B2, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.3.8, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 9ec673d543c24ebf488dd370527ce8d0
Archived-At: <https://mailarchive.ietf.org/arch/msg/isis-wg/AL14eUiM6NzIzFdhAKLj1bkuUXk>
Subject: Re: [Isis-wg] AD review of draft-ietf-isis-mi-bis-01
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Mar 2017 17:33:47 -0000

Les,

Thx for the clarification.. as I indicated there was no discussion on the mailing list about this and people might have overlooked as the 01 bis draft says it “updates” erroneously.
Have no issues with the updates; but would be good to have some future guidance.
--
Uma C.

From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]
Sent: Friday, March 17, 2017 9:15 PM
To: Uma Chunduri <uma.chunduri@huawei.com<mailto:uma.chunduri@huawei.com>>; Alia Atlas <akatlas@gmail.com<mailto:akatlas@gmail.com>>; isis-wg@ietf.org<mailto:isis-wg@ietf.org>; draft-ietf-isis-mi-bis@ietf.org<mailto:draft-ietf-isis-mi-bis@ietf.org>
Subject: RE: AD review of draft-ietf-isis-mi-bis-01

Uma –

This was always intended as a replacement for RFC 6822 – it was my error to label it as an update – thanx to Alia for spotting this.

The bis draft does NOT just describe the modifications – it contains the original text of RFC 6822 plus changes – and Appendix A summarizes the changes.

There is no problem here other than I incorrectly labeled this as an update.

   Les


From: Uma Chunduri [mailto:uma.chunduri@huawei.com]
Sent: Friday, March 17, 2017 5:26 PM
To: Les Ginsberg (ginsberg); Alia Atlas; isis-wg@ietf.org<mailto:isis-wg@ietf.org>; draft-ietf-isis-mi-bis@ietf.org<mailto:draft-ietf-isis-mi-bis@ietf.org>
Subject: RE: AD review of draft-ietf-isis-mi-bis-01

Les,

>I am not aware of any requirement to have the original set of authors be authors of a bis document –

                Sorry to know this..

>and there are certainly other examples where authorship has changed.

                Not seen much in other WGs (but you will have numerous examples contrary to this)…

>And there are obvious practical reasons why authorship may change.

                The problem here is - draft currently says it “updates” 6822, but 95% of the content and spirit is same as 6822. In that case, it should have just described the appropriate changes without completely duplicating the same.
                But that was not the case. Now after ADs suggestion, if we agreed to obsolete 6822, it doesn’t sound logical to replace original authors with new set of contributors.

--
Uma C.

v2.23.0 | Report a Bug | By Email