Re: [Isis-wg] [Bier] WGLC: draft-ietf-bier-isis-extensions-04

IJsbrand Wijnands <> Sat, 10 February 2018 08:49 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B8BD0127867; Sat, 10 Feb 2018 00:49:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id UJFBntk6WhQP; Sat, 10 Feb 2018 00:49:07 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5CB4E127871; Sat, 10 Feb 2018 00:49:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=1881; q=dns/txt; s=iport; t=1518252546; x=1519462146; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=IcChQdWieHlzC3uQ+qifgWkyZJ+2qFAUuDZzrwmWm2k=; b=Stqe1lcGLlpO9SeAGZWXND6Fq2mgFpU94Xl4/9amOf7A6EQ7mOr/JFc9 zjLtOvNVE9mgPl+feWYbd/cTWlsdc2+kD8AC5RqfE793oZPFlITWUbWZF 4tWLLmv5aKHntAXOPXoaTWTXzcNETL8raEZNohfxSSOZvkpW06dWDBZSG g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.46,488,1511827200"; d="scan'208";a="1932680"
Received: from (HELO ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Feb 2018 08:49:02 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id w1A8n2K9029148 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 10 Feb 2018 08:49:02 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: IJsbrand Wijnands <>
In-Reply-To: <>
Date: Sat, 10 Feb 2018 09:49:07 +0100
Cc: "" <>, " list" <>, "" <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
To: Tony Przygienda <>
X-Mailer: Apple Mail (2.2104)
Archived-At: <>
Subject: Re: [Isis-wg] [Bier] WGLC: draft-ietf-bier-isis-extensions-04
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF IS-IS working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 10 Feb 2018 08:49:09 -0000


> Ice, as you well know we ended up with a one value BAR field without a registry (you being a strong proponent of such solution if I recall correctly) which is the current draft state in IETF LC Greg initiated. 

Indeed, along with other steak holders -T.

> Yes, ideas were extended based on original private drafts which have not been initiated from my side BTW. Some draft of a draft followed from other parties (which I was part of) trying to reconcile the different asks into some kind of a workable state.  Obviously I have many such discussions juggling at any given point in time around technologies I push forward and I try to keep a lot of people invested while assuring that we don't end up with intractable balls of yarn. In this case I did not see in a timely manner any consensus that seemed mature enough to me to shake the IETF LC despite having repeatedly notifying the parties that time is not infinite here and workable consensus for many involved interests is not equivalent to having one's desires being part of imperative substratum of the technology. And in this case all was aggravated somewhat by the fact that we were talking introduction of unspecified fields reflecting  working versions of private drafts on top of an already barely specified field we have. 
> In short: since you state you're fine with the draft as it is (I omit the nits/defect I found with Les

I was always fine with the version that Greg LC'd as you rightfully state above.

>  which I assume will cause no further discussions) neither do I see any need to shake the draft further.

Good to hear!

>  Ongoing developments of the technology will be taken into future drafts  especially since we are steering towards a generous standards charter to develop BIER.