Re: [trill] Alexey Melnikov's Discuss on draft-ietf-trill-directory-assist-mechanisms-11: (with DISCUSS)

Alexey Melnikov <aamelnikov@fastmail.fm> Fri, 10 March 2017 15:03 UTC

Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BCD112996F; Fri, 10 Mar 2017 07:03:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.72
X-Spam-Level:
X-Spam-Status: No, score=-1.72 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, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=qAP8TcEK; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=CBerxPjc
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 rRT4WLdLTaVH; Fri, 10 Mar 2017 07:03:25 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6375012997E; Fri, 10 Mar 2017 07:03:24 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id E4D3220B3D; Fri, 10 Mar 2017 10:03:22 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Fri, 10 Mar 2017 10:03:22 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=1E5T3Ck3lUEHjPr oq0W6fiVtxHA=; b=qAP8TcEKWDTyygXUm45mzwxDcUk7WvoWc0MdJR9z+vHxvcY 4YifIPUbKogLL+ZbLA+8LO/pY7djDkE/7OgA5jhxRB/Jc9W2e6DqWls3MV5/Vk8m IcT3s0G5UCvw3G41Eyqt6CQqZANIIwpaH4ehzmIS9z8JVb6cbjGrTJNnuMGY=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=1E5T3Ck3lUEHjProq0W6fiVtxHA=; b=CBerxPjcFOG5QmLmVy5u N7VZ5nChvUD/A9f+0rs2dL3BI4qQGofM68mWPyGxcxRXf/WiyGmltQqVUvSBBIB6 RNi6zGKke1T5/r/9P91bu/10QfSV2sNKlJQpQ61Njc+Kfr8THMPM2fovlVWIIa3O fJYw7KIKFLwlrPcn6IMbkuM=
X-ME-Sender: <xms:OsDCWHVZFcW_4ul3Hyvo48-T6ko_kFkd7J00VwZWUPg92H2OrwT-0g>
X-Sasl-enc: EN7MsyL5oxQhFf3u1SDg9qB6GheVAdR75qaUgECIBCCs 1489158202
Received: from [10.234.90.71] (unknown [148.252.129.110]) by mail.messagingengine.com (Postfix) with ESMTPA id 90451244DA; Fri, 10 Mar 2017 10:03:22 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPhone Mail (13G35)
In-Reply-To: <CAF4+nEFkbsoYah_wm1F3eKQXyVvEuNcFMeoeWiMpTyKgNNHneg@mail.gmail.com>
Date: Fri, 10 Mar 2017 15:16:10 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <305DABD1-0E6E-4145-A21C-2D7BE390B7D8@fastmail.fm>
References: <148476684392.2033.546851999767154453.idtracker@ietfa.amsl.com> <CAF4+nEGP9+3kq7J3Zs1EfNJ+cP8ZCbSg5Vuc+0zvxNbrCSNJtA@mail.gmail.com> <09692183-AC90-4862-8EA9-86A176C69EF8@fastmail.fm> <CAF4+nEFkbsoYah_wm1F3eKQXyVvEuNcFMeoeWiMpTyKgNNHneg@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/uICR0BgweYw98vynNvm9UpUNn4Y>
Cc: "trill-chairs@ietf.org" <trill-chairs@ietf.org>, draft-ietf-trill-directory-assist-mechanisms@ietf.org, The IESG <iesg@ietf.org>, "shares@ndzh.com" <shares@ndzh.com>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] Alexey Melnikov's Discuss on draft-ietf-trill-directory-assist-mechanisms-11: (with DISCUSS)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Mar 2017 15:03:26 -0000

Hi Donald,

> On 2 Mar 2017, at 22:45, Donald Eastlake <d3e3e3@gmail.com> wrote:
> 
> Hi Alexey,
> 
> Version -12, just posted, is intended to resolve your DISCUSS. My
> apologies for taking so long. Could you take a look?

I cleared. Thank you for the extra text.

> Thanks,
> Donald
> ===============================
> Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> 155 Beaver Street, Milford, MA 01757 USA
> d3e3e3@gmail.com
> 
> 
>> On Thu, Jan 19, 2017 at 4:48 AM, Alexey Melnikov <aamelnikov@fastmail.fm> wrote:
>> Hi Donald,
>> 
>>> On 19 Jan 2017, at 05:16, Donald Eastlake <d3e3e3@gmail.com> wrote:
>>> 
>>> Hi Alexey,
>>> 
>>>> On Wed, Jan 18, 2017 at 2:14 PM, Alexey Melnikov <aamelnikov@fastmail.fm> wrote:
>>>> Alexey Melnikov has entered the following ballot position for
>>>> draft-ietf-trill-directory-assist-mechanisms-11: Discuss
>>>> 
>>>> When responding, please keep the subject line intact and reply to all
>>>> email addresses included in the To and CC lines. (Feel free to cut this
>>>> introductory paragraph, however.)
>>>> 
>>>> ----------------------------------------------------------------------
>>>> DISCUSS:
>>>> ----------------------------------------------------------------------
>>>> 
>>>> In Section 3.1 there is a Version field. What are the condition(s) for
>>>> bumping this version number? What backward compatibility guaranties are
>>>> expected (if any)? How would version negotiation be done?
>>> 
>>> Well, I could say that the answers to all of your questions are about
>>> the same for this Version field as they are for the RBridge Channel
>>> Header version field [RFC7178], the TRILL Header version field
>>> [RFC6325], and many other version fields in IETF protocols but you
>>> probably wouldn't consider that a very good answer.
>>> 
>>> I suppose if text was being added along this lines, it should say that
>>> the version number must be incremented for a specification that does
>>> not just specify new field values where that is allowed in version
>>> zero but cannot be correctly parsed beyond the version nibble. Since
>>> the protocol is a request/response protocol, the responder should
>>> indicate the highest version number they understand but the response
>>> must be valid in the version number specified in the request including
>>> the possibility of indicating a valid error saying that the version is
>>> not implemented. Thus all implementations of version X would need to
>>> be able to at least send such an error for all versions from 0 through
>>> X-1. Then you would add an explicit suberror code in Section 3.6.3 for
>>> unimplemented version. For a version zero implementation, that would
>>> be returned for any higher version.
>>> 
>>> However, I don't expect an incremented version number to be needed
>>> anytime soon. Was it your intent with this DISCUSS to get something
>>> like the above added to the draft?
>> 
>> Yes, exactly along the lines of your text above.
>> 
>>