Re: [Anima-bootstrap] [Anima] Concise version of BRSKI

"Max Pritikin (pritikin)" <> Tue, 23 May 2017 16:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C4E65129B71; Tue, 23 May 2017 09:30:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Status: No, score=-14.523 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 skUEKiRoPh5a; Tue, 23 May 2017 09:30:41 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 97EFE1293D9; Tue, 23 May 2017 09:30:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=6068; q=dns/txt; s=iport; t=1495557041; x=1496766641; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Vxx3tIH1aLg+3pH2FlrKecy05hMZAMlzEgosJ46AKnE=; b=iswy0hJcRfHlasBExnDHuZxCQIchvPIn1SFdb8Us+a0FyHE7Yu2lwAWU w2Wy4WsyZjHPiTJ88Za720Cm+P8n5hNcIS6apN8Sw09iVDiGDsZT4n2Gi T0s1N8+VRtB3Fl0p0iV++m6ddfW+frGj+yXpyL4GkGs0VgvQQwkcNrJ2y 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.38,382,1491264000"; d="scan'208";a="30919956"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-SHA; 23 May 2017 16:30:40 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id v4NGUev8018035 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 23 May 2017 16:30:40 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 23 May 2017 11:30:39 -0500
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Tue, 23 May 2017 11:30:39 -0500
From: "Max Pritikin (pritikin)" <>
To: Toerless Eckert <>
CC: anima-bootstrap <>, Anima WG <>, "" <>
Thread-Topic: [Anima-bootstrap] [Anima] Concise version of BRSKI
Thread-Index: AQHStW9CstO2wlN3FUyI3JGtr7rg8aHLNO2AgACAfICANtU1AIAAIiiA
Date: Tue, 23 May 2017 16:30:39 +0000
Message-ID: <>
References: <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Anima-bootstrap] [Anima] Concise version of BRSKI
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mailing list for the bootstrap design team of the ANIMA WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 23 May 2017 16:30:44 -0000

> On May 23, 2017, at 8:28 AM, Toerless Eckert <> wrote:
> It is quite frustrating to see the bootstrap draft be handled in a way that is impossible
> to track:
> - it would have been better not to crearte anothrer branch that you can only be aware 
>  of by having seen this email

As previously requested this thread was sent to the anima working group mailing list rather than the now deprecated bootstrap mailer. Not sure how else to communicate status. 

The up to date document is available via the github repository. This is in alignment with multiple conversations at ietf and was the subject of a BoF at the Chicago IETF. If you have concerns about how git might work within a working group process flow i’ll bet the authors of or would be interested in the feedback. I suggest raising your concerns on the ietf-and-github mailing list to ensure they’re addressed as part of that broader effort. 

> - If you use a new branch, it would be great if you would have updated the IETF anima bootstrap wiki page
>  with this information.
> - for the sake of the non-git experts amongst us, it would be great to also indicate some
>  command how to retrieve this branch. I for once tried:
>  git clone -b concise includes a dropdown to select the branch if you just want to look at the specific files. Using this for example the pre06 version from the concise branch is available here: 
One way to determine which branch has the most activity is to look here:

>  and that totally did not work.

Using -b worked for me. Not sure what you did wrong then. 

>  So as of right now i am lost in how i should review this version of the document.

Thanks for joining the meeting today and voicing your concerns. To help we’ll push the 06 version of the doc to give you a better reference for generating feedback. 

- max

> Toerless
> On Tue, Apr 18, 2017 at 05:07:18PM +0000, Max Pritikin (pritikin) wrote:
>> Peter,
>> The current text is wordy and repetitive and says things more than once <grin>. Primary focus is to remove repetitive text, tighten remaining text, and consolidate normative statements. 
>> As an initial example the -05 draft has 3 main sections:
>> 	architectural overview
>> 	functional overview (contains design considerations discussions)
>> 	protocol details
>> The initial ???concise??? branch commit moves the functional overview to the appendix. Subsequent commits are resolving normative texts that were in there by moving needed bits back into the protocol discussion. You can follow along via the git repository here:
>> There was a comment that the design considerations are useful and might be appropriate to keep here or in another document. At the moment I don???t have a formulated position on that.  
>> - max
>>> On Apr 18, 2017, at 3:27 AM, peter van der Stok <> wrote:
>>> Hi Max,
>>> excellent idea. I looked at the present version, and there is still a lot of text.
>>> Where in the text do you want to reduce more? What is the end-objective?
>>> And will this become the final document, or is it a study that will be used later for editing the final document?
>>> Peter
>>> Max Pritikin (pritikin) schreef op 2017-04-15 00:34:
>>>> For those of you tracking the git repository please note the existence
>>>> of a new branch. As warned I???m significantly reducing the text. This
>>>> work is going on in the branch ???concise???.
>>>> _______________________________________________
>>>> Anima mailing list
>> _______________________________________________
>> Anima-bootstrap mailing list
> -- 
> ---
> _______________________________________________
> Anima-bootstrap mailing list