Re: [Isis-wg] Alexey Melnikov's Discuss on draft-ietf-isis-rfc4971bis-03: (with DISCUSS and COMMENT)

Alexey Melnikov <aamelnikov@fastmail.fm> Thu, 18 August 2016 10:05 UTC

Return-Path: <aamelnikov@fastmail.fm>
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 CB3E312D8A8; Thu, 18 Aug 2016 03:05:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level:
X-Spam-Status: No, score=-2.719 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=C2B7V1IZ; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=WJLM9DpM
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 WUGqyDtbitKC; Thu, 18 Aug 2016 03:05:09 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BCCF12D899; Thu, 18 Aug 2016 03:05:09 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id CFDEC205C1; Thu, 18 Aug 2016 06:05:08 -0400 (EDT)
Received: from web5 ([10.202.2.215]) by compute6.internal (MEProxy); Thu, 18 Aug 2016 06:05:08 -0400
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-sasl-enc :x-sasl-enc; s=mesmtp; bh=sMAM5Lpslv9mnyZoug3oX+KmIXU=; b=C2B7V1 IZ76ZpenEzKBNHz359Gdqny7N9dtJX4qWYpXaGNhKMmr7bAnclgVPXf/i7n1k7N1 3chJxf60DR3E+BOK3RjTNPr01vkgv+ViLEdmG2ncHX02M5Zx8VtIqBbM55y6uOyq 9yaLfbFAgsM//wQeg8Kgl37m7f4YTTP29u7iM=
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-sasl-enc:x-sasl-enc; s=smtpout; bh=sMAM5Lpslv9mnyZ oug3oX+KmIXU=; b=WJLM9DpMwYtGR+D/n+X4yvC/+CRNpmaY4fenaDFL6UsmIpC wtm5Bhry13CWJlCpl7HaB8gBw60p2SHfhbvBV3IXZ95HNFhO5MvjFrsqqE5QTzxe HaA3Nw1KtrNkFpGJ72sOEN+oZiCYvmRRL18+LNIL833amSNPII0lhwtpHcvI=
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 9B06E96883; Thu, 18 Aug 2016 06:05:08 -0400 (EDT)
Message-Id: <1471514708.3080688.698917081.5D24276D@webmail.messagingengine.com>
X-Sasl-Enc: L9Ac+K7qY1TVphZxbZRRNdUuIsG6Z/RE8XgAHUlDsNDo 1471514708
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: Alia Atlas <akatlas@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary="_----------=_147151470830806880"; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-b25c4c74
Date: Thu, 18 Aug 2016 11:05:08 +0100
In-Reply-To: <CAG4d1re4inwF6_yQT=qKCXz=PeUQzMYBfoyPvvN60h_QJZWPDQ@mail.gmail.com>
References: <147136220282.22903.10134856216046001373.idtracker@ietfa.amsl.com> <CAG4d1rfoW_7R0qkKvLt71-P1XegGPd1CLwLtXtmTCS4N50kaQQ@mail.gmail.com> <1471364164.2609509.697007537.7E0612EB@webmail.messagingengine.com> <CAG4d1re4inwF6_yQT=qKCXz=PeUQzMYBfoyPvvN60h_QJZWPDQ@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/isis-wg/_q3Zf48N5FBE0JmNzBc3MP8P9Lw>
Cc: isis-chairs@ietf.org, Christian Hopps <chopps@chopps.org>, draft-ietf-isis-rfc4971bis@ietf.org, The IESG <iesg@ietf.org>, isis-wg@ietf.org
Subject: Re: [Isis-wg] Alexey Melnikov's Discuss on draft-ietf-isis-rfc4971bis-03: (with DISCUSS and COMMENT)
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 18 Aug 2016 10:05:11 -0000

Hi Alia,

On Tue, Aug 16, 2016, at 05:18 PM, Alia Atlas wrote:
>
>
> On Tue, Aug 16, 2016 at 12:16 PM, Alexey Melnikov
> <aamelnikov@fastmail.fm> wrote:
>> __
>> Hi Alia,
>>
>>
>> On Tue, Aug 16, 2016, at 05:03 PM, Alia Atlas wrote:
>>
>>> Hi Alexey,
>>>
>>>
>>> On Tue, Aug 16, 2016 at 11:43 AM, Alexey Melnikov
>>> <aamelnikov@fastmail.fm> wrote:
>>>
>>>>
>>>>
>>>> -----------------------------------------------------------------
>>>> -----
>>>> DISCUSS:
>>>> -----------------------------------------------------------------
>>>> -----
>>>>
>>>> I would like to get clarification on the following points before
>>>> recommending approval of this document:
>>>>
>>>> 1) How do multiple CAPABILITY TLVs from the same source treated, if
>>>>    they
>>>> have the same S and D flags, but different subTLV? Are the
>>>> cumulative? Or
>>>> this is not allowed?
>>>> I am sorry if I missed where this was described, let me know if
>>>> I did.
>>>
>>> The end of Section 3 says " Where a receiving system has two copies
>>> of a CAPABILITY TLV from the same system that have different
>>> settings for a given attribute, the procedure used to choose which
>>> copy shall be used is undefined."
>>>
>>
>> Ok, I wasn't sure that this was talking about the same thing.
>>
>> So just to double check: using multiple CAPABILITY TLVs with
>> different S and D flags is Ok (and described), but use of multiple
>> CAPABILITY TLVs with identical S and D flags is undefined as per the
>> sentence you quoted above?
>
> They have to have the same attribute - which could be a sub-TLV.

I don't think Les' answer agrees with yours.

The word "attribute" only occurs once in the document in the sentence
you quote.
Does "a given attribute" mean "a single sub-TLV" or "all sub-TLVs
included in a CAPABILITY TLV instance"?