Re: [Isis-wg] review comments on draft-ietf-isis-fs-lsp-01

"Les Ginsberg (ginsberg)" <> Tue, 20 May 2014 23:11 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 71C4E1A016D for <>; Tue, 20 May 2014 16:11:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id L1PyQLUbBShc for <>; Tue, 20 May 2014 16:11:56 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 96EA41A02D8 for <>; Tue, 20 May 2014 16:11:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=5148; q=dns/txt; s=iport; t=1400627516; x=1401837116; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=vd9nfVCg+JVuNLfwRkZmHq/JAh+6e1Vsppg+dPM8MyI=; b=ZKD9Qgetook6I0xdnet+ehx0Uo9GqHJmkwvjw/ySESYC0oo6sjeObQD/ NXOVh/068HsLR63/chMSOdsF0j36laMrKKM6VViIWSSJ5OWVszMoY1Xkk l+Yv4N+GcDx71Et8PCUG1+aRv5N6iVZRp6rho7CCqEgTVEFPR6MvZOF0R Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="4.98,877,1392163200"; d="scan'208";a="45659016"
Received: from ([]) by with ESMTP; 20 May 2014 23:11:55 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id s4KNBtG5004734 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 20 May 2014 23:11:55 GMT
Received: from ([]) by ([]) with mapi id 14.03.0123.003; Tue, 20 May 2014 18:11:55 -0500
From: "Les Ginsberg (ginsberg)" <>
To: Alia Atlas <>, "" <>, "" <>
Thread-Topic: review comments on draft-ietf-isis-fs-lsp-01
Thread-Index: AQHPdHOdPcGR1eTprE6vkXUPaL8a3JtKD67Q
Date: Tue, 20 May 2014 23:11:54 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: Adrian Farrel <>, "" <>
Subject: Re: [Isis-wg] review comments on draft-ietf-isis-fs-lsp-01
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 20 May 2014 23:11:58 -0000

(Resending - including WG and Adrian)

Alia -

Thanx for your comments.

> -----Original Message-----
> From: Alia Atlas []
> Sent: Tuesday, May 20, 2014 2:37 PM
> To:;
> Subject: review comments on draft-ietf-isis-fs-lsp-01
> As a standard part of my process for evaluating drafts before starting
> IETF Last Call,
> I do a review of the draft.  This is that review.
> In general, this is a really clear and well written draft.  Thank you
> for articulating the reasons and requirements so clearly and for
> taking advantage of this opportunity to make the
> backwards-incompatible changes.
> This draft is in excellent shape and I will start the IETF Last Call
> for it - but I do have a couple specific comments below.  These can be
> handled during IETF Last Call and addressing any concerns raised
> there.
> Specific comments:
> In Sec 11, could the following text be clarified?
> " A list of the circuit scopes supported on this circuit and
>   other non-circuit flooding scopes supported.
>        R bit MUST be 0 and is ignored on receipt.
>        In a Point-Point IIH L1, L2 and domain-wide scopes MAY
>        be advertised.
>        In Level 1 LAN IIHs L1 and domain-wide scopes MAY be advertised.
>        In Level 2 LAN IIHs L2 and domain-wide scopes MAY be advertised.
> "
> For instance, does this mean that circuit scopes MAY be advertised?

An IIH is a circuit scoped PDU. It therefore is expected that if the new Scoped Flooding Support TLV is sent in an IIH that it would include the circuit scopes supported on that circuit. The language regarding L1, L2, domain-wide scopes explicitly specifies what scopes - in addition to circuit scopes - MAY be included in the three IIH PDU types. The expectation regarding circuit scope  is explicitly stated by the earlier sentence:

" A list of the circuit scopes supported on this circuit and  other non-circuit flooding scopes supported."

I think your point may be that it would be clearer to also include "circuit scopes" in the statement regarding each PDU type - something like:

<Begin revised text>
In a Point-Point IIH L1, L2, domain-wide, and circuit scopes MAY  be advertised.
In Level 1 LAN IIHs L1, domain-wide, and  circuit scopes MAY be advertised.
In Level 2 LAN IIHs L2, domain-wide, and circuit scopes MAY be advertised.
<End revised text>

If you think the revised text is clearer I have no objection.

> In a Level 1 LAN IIHs, L1 scopes MUST NOT be advertised?

Did you mean L2 scopes MUST NOT be advertised in an L1 LAN IIH? If so, yes that is the intent of listing the scopes which MAY be advertised in a given PDU. What is not specifically permitted is prohibited.

> In the IANA section, do the registries for the sub-TLVs also need to
> be extended?

The draft introduces 16 bit TLVs and 16 bit sub-TLVs - so if/when new sub-TLV registries associated w extended TLV codepoints (i.e. codepoint > 255) are required they will have to support 16 bit sub-TLV codepoints.   However, the existing sub-TLV registries (e.g. Sub-TLVs for TLV 22, 141, and 222) do NOT need to be extended. This is because those registries are associated with Standard TLVs and therefore the sub-TLV codepoints are restricted to be within the Standard sub-TLV range.

As we are not introducing any new sub-TLV registries in this document I think the existing language in the IANA section is appropriate. We could add a statement like:

"Future sub-TLV registries associated with Extended TLVs will support values in the range of 0 - 65535."

I am not sure that is necessary.


> Thanks,
> Alia