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

Alia Atlas <akatlas@gmail.com> Tue, 16 August 2016 16:03 UTC

Return-Path: <akatlas@gmail.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 C7E4512D121; Tue, 16 Aug 2016 09:03:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.699
X-Spam-Level:
X-Spam-Status: No, score=-102.699 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, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 httaSJ0DZkOK; Tue, 16 Aug 2016 09:03:23 -0700 (PDT)
Received: from mail-qt0-x232.google.com (mail-qt0-x232.google.com [IPv6:2607:f8b0:400d:c0d::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEA3E12B069; Tue, 16 Aug 2016 09:03:23 -0700 (PDT)
Received: by mail-qt0-x232.google.com with SMTP id w38so37260982qtb.0; Tue, 16 Aug 2016 09:03:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=dTq5ZD6AbXb7ljnWy32TKAwBFAblYbScaO5/5eMyyWA=; b=A7SQEtbjJvnM/+gvWYa5CMFxBK16TW5zwG5b+Ts6BpEB0FT4H306M0tQXXpS2tk2Z2 Y+Zr/v8EZdu50R7f4F6DbO/zDbZOcGY4DZ+T1F7q60QD51VV4iGnT/WMTVbB03R9fPHZ HAUETaJz+BqX7iD8y65Y7OHKebhdZVCmxt0LPXd9Y7esA/Ty5AI6R3u56XUUGtb4fYx/ A8TF7fSQUvpdtJVc0VzE3xHXOULAPb2AU+VCOjLvBcwAs3n8t6j40i15GL9eSeuAL4le 4Ovg6ERK07Jt2HxX30GzINMY7d8GbsjmM35nJZbl06sSjL6V4a/T/XCSmPmmzIkpt8Wl 4iJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=dTq5ZD6AbXb7ljnWy32TKAwBFAblYbScaO5/5eMyyWA=; b=ZQmIxMogo9IHI8imE8XWfqYZHBL4JZDGfYRHCM3jWsWxsfW7B3GkbhAQYfxd+3QRW5 i8toD3DkAMnZ/un9gs5eOlD8hlhKbJQD5olwUQYIY89pY27eBy5zMOyQZMyN5ZZSerzK hQNgtMfQ6kC5nZZ/NmlKsItlRzAfDSL+jkfgUiYHxFo3JaY1VoiB+RYUINLAr12v2/Gy apBLr9y5Bthp2YVFkmVvNdpq9BJO7HaSTXRjAycpahDPYktq7p+m27RcdoHta2ijiR3B goIRVbL+DIpDQpirltUW8vfh38cO3vc63OTU77jn3X9VU3A8gTiNPDOVHo98lnG1jpmL FW3w==
X-Gm-Message-State: AEkooutxNShkjVx2IaEmAoiJOkJ9ICSdMhkBQnLsRopJDa3pxrCUqS1eo++Wf/MjxpLJpMplRfXolFZIZzqsVw==
X-Received: by 10.237.47.1 with SMTP id l1mr40157598qtd.124.1471363402806; Tue, 16 Aug 2016 09:03:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.52.193 with HTTP; Tue, 16 Aug 2016 09:03:22 -0700 (PDT)
In-Reply-To: <147136220282.22903.10134856216046001373.idtracker@ietfa.amsl.com>
References: <147136220282.22903.10134856216046001373.idtracker@ietfa.amsl.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Tue, 16 Aug 2016 12:03:22 -0400
Message-ID: <CAG4d1rfoW_7R0qkKvLt71-P1XegGPd1CLwLtXtmTCS4N50kaQQ@mail.gmail.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Content-Type: multipart/alternative; boundary=94eb2c1252f2f5bdb8053a327cce
Archived-At: <https://mailarchive.ietf.org/arch/msg/isis-wg/p8q8bKOkXABZGnvyXo9cfRF0tb8>
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" <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: Tue, 16 Aug 2016 16:03:26 -0000

Hi Alexey,

On Tue, Aug 16, 2016 at 11:43 AM, Alexey Melnikov <aamelnikov@fastmail.fm>
wrote:

> Alexey Melnikov has entered the following ballot position for
> draft-ietf-isis-rfc4971bis-03: 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.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-isis-rfc4971bis/
>
>
>
> ----------------------------------------------------------------------
> 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."

This bis is to update the handling for IPv6; there was no discussion about
changing the basic details (such as this)
in the updated version.

2) In Section 4, 1st sentence: how can this specification have
> requirements on implementation that don't support this extension? If this
> behaviour is already prescribed by another specification, then you should
> not use RFC 2118 keyword and you should reference the relevant
> specification.
>

RFC1195 says
"   Any codes in a received PDU that are not recognised shall be ignored
   and, for those packets which are forwarded (specifically Link State
   Packets), passed on unchanged."

A reference would be fine - but this is basic well-known behavior for IS-IS.
The authors may have more details.



> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Should subTLVs have an IANA registry? Or is there an existing one
> already?
>

It's already there -
http://www.iana.org/assignments/isis-tlv-codepoints/isis-tlv-codepoints.xhtml#isis-tlv-codepoints-242
but it does look like an updated reference to rfc4971bis would be a good
idea.

Regards,
Alia


>
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www.ietf.org/mailman/listinfo/isis-wg
>