
From nobody Thu Mar  1 01:49:57 2018
Return-Path: <laurent.ciavaglia@nokia-bell-labs.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51FDA12711D for <anima@ietfa.amsl.com>; Thu,  1 Mar 2018 01:49:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.91
X-Spam-Level: 
X-Spam-Status: No, score=-2.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=-1, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.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 T1dYX-v4Elci for <anima@ietfa.amsl.com>; Thu,  1 Mar 2018 01:49:53 -0800 (PST)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0137.outbound.protection.outlook.com [104.47.2.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B664F1243F6 for <anima@ietf.org>; Thu,  1 Mar 2018 01:49:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector2-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Svu//4chRt8TDLBkSm5M/dHt2baho47K3mMo6xkxkJ4=; b=ERt/g+rNitQiiWGfEcVuQnrgDrj1VYE6YS2lpdVtGLXNH6J8hdt5NvA5Hr8YnW1nFyBtKo3EtatixwOrz9sV3SQtwC78B37qJm3ibks7TcWAHjI7CYDdQNQSNJcSacbLCgO2aSN1Z7NF2CP1BRNRfhwz2xkfFcRdxXnF8R4LQFM=
Received: from HE1PR0701MB2203.eurprd07.prod.outlook.com (10.168.36.134) by HE1PR0701MB2620.eurprd07.prod.outlook.com (10.168.187.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.567.6; Thu, 1 Mar 2018 09:49:49 +0000
Received: from HE1PR0701MB2203.eurprd07.prod.outlook.com ([fe80::141f:583a:cdfe:c89b]) by HE1PR0701MB2203.eurprd07.prod.outlook.com ([fe80::141f:583a:cdfe:c89b%6]) with mapi id 15.20.0567.002; Thu, 1 Mar 2018 09:49:49 +0000
From: "Ciavaglia, Laurent (Nokia - FR/Paris-Saclay)" <laurent.ciavaglia@nokia-bell-labs.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Toerless Eckert <tte@cs.fau.de>
CC: "anima@ietf.org" <anima@ietf.org>
Thread-Topic: [Anima] "professionally managed" and the reference model
Thread-Index: AQHTr0fd6cPvdbNsekSo9b5U4wiCNaO4cv0AgABVvoCAATDUgIAAl0MAgACOaJA=
Date: Thu, 1 Mar 2018 09:49:49 +0000
Message-ID: <HE1PR0701MB22035000450382804933C860E8C60@HE1PR0701MB2203.eurprd07.prod.outlook.com>
References: <f134fecd-7749-48ed-e336-657ac045d5a5@gmail.com> <03ab2d02-f7d1-4c39-40c0-d232c909a111@gmail.com> <e968de00-11cc-da4a-2e31-721cb8d0b4d2@gmail.com> <20180228155157.GA17673@faui40p.informatik.uni-erlangen.de> <ddd91d8a-d25e-d3fb-6e16-eb585d509c41@gmail.com>
In-Reply-To: <ddd91d8a-d25e-d3fb-6e16-eb585d509c41@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=laurent.ciavaglia@nokia-bell-labs.com; 
x-originating-ip: [2a01:cb04:73c:ab00:a4f7:16e6:76ce:4558]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR0701MB2620; 7:B1io1qLVDlJXhfoGUwnLZSbEKVqLuGoKhk324lIzeuNgp4GiXJwpIH2Ntdq0+YmLyqCxD363BGCu5Ki7CrAdzK9eb4JpeYGyfou+7GoAPPmgN3pa3NJPlVPDYO7kn/Bh23CN0/gmy1MhjVapNDF7cu7jJcDmZvBWJHHGqhFTicWmsm4zbxQlWXpgYWOGqYforAyR8R+GNuIJ1n1GehqZ7xjGION4ox8Qyx/N3BX+IN8Pwm5haUkc/AeAOtDYDQLG
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: f0aaf475-c3dd-4298-a1d6-08d57f59c646
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603307)(7193020); SRVR:HE1PR0701MB2620; 
x-ms-traffictypediagnostic: HE1PR0701MB2620:
x-microsoft-antispam-prvs: <HE1PR0701MB2620E3F9B97E391729DCE874E8C60@HE1PR0701MB2620.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(788757137089);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93001095)(3002001)(3231220)(11241501184)(944501226)(6055026)(6041288)(20161123564045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123562045)(6072148)(201708071742011); SRVR:HE1PR0701MB2620; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0701MB2620; 
x-forefront-prvs: 05986C03E0
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(39860400002)(39380400002)(376002)(346002)(366004)(199004)(13464003)(189003)(97736004)(2950100002)(14454004)(110136005)(105586002)(478600001)(229853002)(3280700002)(4326008)(186003)(8936002)(39060400002)(8676002)(81156014)(81166006)(68736007)(102836004)(53546011)(6506007)(6116002)(33656002)(86362001)(966005)(2906002)(316002)(5250100002)(106356001)(305945005)(6246003)(5660300001)(3660700001)(99286004)(25786009)(76176011)(7696005)(53936002)(74316002)(9686003)(2900100001)(7736002)(6436002)(55016002)(6306002)(93886005)(90052001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR0701MB2620; H:HE1PR0701MB2203.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: nokia-bell-labs.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: BjeYKINuMhZadkzJiuMXsdMrgL8F5tEkvd2P2G3YHdnAovS9cdYguHD3R+hznpOBDyYUF0Xv76nlN9AQBRMManppflPIpqR5bLRUQYhVgUXmUvn42O6BnSAhRigjTe+kK97jCwEiLVpZKowa9feygU+3pXJd+bsjZCqayowcoP0=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: nokia-bell-labs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f0aaf475-c3dd-4298-a1d6-08d57f59c646
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Mar 2018 09:49:49.7557 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2620
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/cexfWZEN3AS23KV6fpq7oCqCBL4>
Subject: Re: [Anima] "professionally managed" and the reference model
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2018 09:49:56 -0000

Hello,

Does the need to explicitly distinguish ANIMA work from HOMENET work still =
exist
If not, then why not remove/forget about this possibly contentious terminol=
ogy. (the goal would be to avoid unnecessary difficulties for ANIMA documen=
ts publication at IESG review or IETF last call stages).

FWIW, my understanding of "professionally managed" is "managed _BY_ a profe=
ssional".=20
Here the person or entity being the "professional" is providing a service (=
paid or free) to manage a given network as part of her job (or contract).=20
In the mission of her job (or contract) the professional is "external" to t=
he user of the network being managed (i.e. act as a first/third party).

* note: a homenet can well be very professionally managed in the sense that=
 it follows BCP but it does not mean it is managed by someone for which it =
is the job to do this (e.g. John Doe, who is a skilled engineer, manage its=
 homenet for himself, or manage homenets for his friends/relatives...)
** note: a homenet can well be completely unmanaged, i.e. relying exclusive=
ly on full plug-and-play mechanisms.

Best regards, Laurent.

-----Original Message-----
From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Brian E Carpenter
Sent: Thursday, March 1, 2018 1:53 AM
To: Toerless Eckert <tte@cs.fau.de>
Cc: anima@ietf.org
Subject: Re: [Anima] "professionally managed" and the reference model

in line (all IMHO):

On 01/03/2018 04:51, Toerless Eckert wrote:
> On Wed, Feb 28, 2018 at 10:40:55AM +1300, Brian E Carpenter wrote:
>> (a) Undoubtedly we will have changes to make after IETF Last Call, so=20
>> we can put this on ice until then.
>> (b) Yes, I think the text here and in RFC7575 is fine. Maybe it's the=20
>> WG charter which is wrong :-). As you know, the point was to avoid=20
>> any clash with HOMENET. But "traditionally managed" is a better=20
>> phrase than "professionally managed", I think.
>=20
> Interesting aside!
>=20
> Is a network with an SDN controller traditionally managed ?

If the SDN controller is configured by a NOC or an NMS database managed by =
the NOC, yes. I think we are talking about configured by a human in the NOC=
 when we say "traditional" or "professional".=20

> If the SDN controller uses the ACP, does this change the result ?

No. But if the SDN controller is configured by an ASA, not by a human, it's=
 autonomic.

> Long term NMS'ler would say controller/orchestrator are just fancy new=20
> words for mostly the provisioning part of NMS, but:
>=20
> Good controllers/orchestrator would also be intent based only that the=20
> rendering of the intent would not necessarily be autonomic. But then=20
> we have never IMHO well described what criteria are required to call a=20
> particular method of intent rendering autonomic.

One reason why "intent" is still a buzzword left for future study.

> Some for example would make distribution the key criteria while i=20
> would just look at the observable resilience of a function.
>=20
> To use a militaristic explanation: When doing PIM-SM, defense=20
> customers asked us what happens when the enemy shoots down the RP. And=20
> then shoot down its replacement. An so on. Now replace RP with SDN contro=
ller.
>=20
> Aka: resilient =3D able to automatically restart in one of enough places=
=20
> to make the solution survive all covered incidents.
>=20
> The "ability to shoot down anything" was btw. the original 1st=20
> requirement by DoD against Arpanet, so i would be careful to call=20
> autonomic networks non-traditional (managed). I would not know what=20
> would be more traditional than meeting this expectation for an IP network=
.

Right. That's why the GRASP draft used to contain a riff about how routing =
algorithms were the original autonomic mechanisms. If you remember, we had =
to remove that to satisfy the Routing Area people.

If ANIMA succeeds, we will have simply extended that original DARPA require=
ment.

   Brian

>=20
> Cheers
>     Toerless
>=20
>>    Brian
>>>
>>> Michael
>>>
>>>
>>>
>>> On 26/02/18 22:21, Brian E Carpenter wrote:
>>>> While looking at Pascal's ACP review, I noticed that although ANIMA=20
>>>> scope is limited by charter to "professionally managed" networks,=20
>>>> we do not mention that scope in draft-ietf-anima-reference-model.
>>>> It seems like something to be added to the Introduction.
>>>>
>>>> Comments?
>>>>
>>>> Regards
>>>>     Brian Carpenter
>>>>
>>>>
>>>> _______________________________________________
>>>> Anima mailing list
>>>> Anima@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/anima
>>>
>>> _______________________________________________
>>> Anima mailing list
>>> Anima@ietf.org
>>> https://www.ietf.org/mailman/listinfo/anima
>>>
>>
>> _______________________________________________
>> Anima mailing list
>> Anima@ietf.org
>> https://www.ietf.org/mailman/listinfo/anima
>=20

_______________________________________________
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima


From nobody Thu Mar  1 09:07:16 2018
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 558B812EBDF for <anima@ietfa.amsl.com>; Thu,  1 Mar 2018 09:07:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.959
X-Spam-Level: 
X-Spam-Status: No, score=-3.959 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 1oXPxhznISU2 for <anima@ietfa.amsl.com>; Thu,  1 Mar 2018 09:07:05 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30A9612EBCF for <anima@ietf.org>; Thu,  1 Mar 2018 09:07:05 -0800 (PST)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 4A7E158C5E0; Thu,  1 Mar 2018 18:07:00 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 2F53BB0DBDB; Thu,  1 Mar 2018 18:07:00 +0100 (CET)
Date: Thu, 1 Mar 2018 18:07:00 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: "Ciavaglia, Laurent (Nokia - FR/Paris-Saclay)" <laurent.ciavaglia@nokia-bell-labs.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, "anima@ietf.org" <anima@ietf.org>
Message-ID: <20180301170659.GB17673@faui40p.informatik.uni-erlangen.de>
References: <f134fecd-7749-48ed-e336-657ac045d5a5@gmail.com> <03ab2d02-f7d1-4c39-40c0-d232c909a111@gmail.com> <e968de00-11cc-da4a-2e31-721cb8d0b4d2@gmail.com> <20180228155157.GA17673@faui40p.informatik.uni-erlangen.de> <ddd91d8a-d25e-d3fb-6e16-eb585d509c41@gmail.com> <HE1PR0701MB22035000450382804933C860E8C60@HE1PR0701MB2203.eurprd07.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <HE1PR0701MB22035000450382804933C860E8C60@HE1PR0701MB2203.eurprd07.prod.outlook.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/rqF814s8YDrk9KluRPipae0ETZg>
Subject: Re: [Anima] "professionally managed" and the reference model
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2018 17:07:11 -0000

On Thu, Mar 01, 2018 at 09:49:49AM +0000, Ciavaglia, Laurent (Nokia - FR/Paris-Saclay) wrote:
> Hello,
> 
> Does the need to explicitly distinguish ANIMA work from HOMENET work still exist

wg chair hat

I am not sure what would have changed since we came to the conclusion.

contributor hat

I also don't look at "professionally managed" as a bad thing. I quite like it. Not
sure who thinks its contentuous. I thought the thread just had some discussion about which
factor we should mention as a reason for something.

> If not, then why not remove/forget about this possibly contentious terminology. (the goal would be to avoid unnecessary difficulties for ANIMA documents publication at IESG review or IETF last call stages).


Well, if IETF asks, my explanation is always the same:

"professionally managed" => 

needs to support networks with highly complex to manage services/policies
understood/expressed by network operations. Large scale, various technologies, etc.pp.

yada intent yada  yada self dependency yada configuration yada operator shoots himself in foot yada

== need secure inband connectivity plane which we call ACP.

which would have been designed differently if we had either a homenet (small, limited features,
fully autonomic), or if we could expect ALL existing services in routers be reimplemented
as ASA and just use GRASP as transport layer AND all the dependency graphing of one Mr. Ciavaglia ;-)

Of course "professionally managed" is not the technical term equivalent to this logic,
but its as good a explanation starter to that end that we did find so far. And i think our
drafts do capture their respective aspects of this accordingly.

Homenet too as a word is the same type of discussion starter (small, simple, no professional
management, fully autonomic). Hence "autonomic" is not the same good discussion starter
because it applies to both anima and homenet.

> FWIW, my understanding of "professionally managed" is "managed _BY_ a professional". 

> Here the person or entity being the "professional" is providing a service (paid or free) to manage a given network as part of her job (or contract). 
> In the mission of her job (or contract) the professional is "external" to the user of the network being managed (i.e. act as a first/third party).
> 
> * note: a homenet can well be very professionally managed in the sense that it follows BCP but it does not mean it is managed by someone for which it is the job to do this (e.g. John Doe, who is a skilled engineer, manage its homenet for himself, or manage homenets for his friends/relatives...)
> ** note: a homenet can well be completely unmanaged, i.e. relying exclusively on full plug-and-play mechanisms.

Sure. Just haven't seen us need to write down these terminology discussions any more
to meet our current charter than we have already done. And if i'd look at possible
next charter, i really think terminology around intent would be more important (hint hint ;-)

> Best regards, Laurent.

Thanks & Cheers
    Toerless
> 
> -----Original Message-----
> From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Brian E Carpenter
> Sent: Thursday, March 1, 2018 1:53 AM
> To: Toerless Eckert <tte@cs.fau.de>
> Cc: anima@ietf.org
> Subject: Re: [Anima] "professionally managed" and the reference model
> 
> in line (all IMHO):
> 
> On 01/03/2018 04:51, Toerless Eckert wrote:
> > On Wed, Feb 28, 2018 at 10:40:55AM +1300, Brian E Carpenter wrote:
> >> (a) Undoubtedly we will have changes to make after IETF Last Call, so 
> >> we can put this on ice until then.
> >> (b) Yes, I think the text here and in RFC7575 is fine. Maybe it's the 
> >> WG charter which is wrong :-). As you know, the point was to avoid 
> >> any clash with HOMENET. But "traditionally managed" is a better 
> >> phrase than "professionally managed", I think.
> > 
> > Interesting aside!
> > 
> > Is a network with an SDN controller traditionally managed ?
> 
> If the SDN controller is configured by a NOC or an NMS database managed by the NOC, yes. I think we are talking about configured by a human in the NOC when we say "traditional" or "professional". 
> 
> > If the SDN controller uses the ACP, does this change the result ?
> 
> No. But if the SDN controller is configured by an ASA, not by a human, it's autonomic.
> 
> > Long term NMS'ler would say controller/orchestrator are just fancy new 
> > words for mostly the provisioning part of NMS, but:
> > 
> > Good controllers/orchestrator would also be intent based only that the 
> > rendering of the intent would not necessarily be autonomic. But then 
> > we have never IMHO well described what criteria are required to call a 
> > particular method of intent rendering autonomic.
> 
> One reason why "intent" is still a buzzword left for future study.
> 
> > Some for example would make distribution the key criteria while i 
> > would just look at the observable resilience of a function.
> > 
> > To use a militaristic explanation: When doing PIM-SM, defense 
> > customers asked us what happens when the enemy shoots down the RP. And 
> > then shoot down its replacement. An so on. Now replace RP with SDN controller.
> > 
> > Aka: resilient = able to automatically restart in one of enough places 
> > to make the solution survive all covered incidents.
> > 
> > The "ability to shoot down anything" was btw. the original 1st 
> > requirement by DoD against Arpanet, so i would be careful to call 
> > autonomic networks non-traditional (managed). I would not know what 
> > would be more traditional than meeting this expectation for an IP network.
> 
> Right. That's why the GRASP draft used to contain a riff about how routing algorithms were the original autonomic mechanisms. If you remember, we had to remove that to satisfy the Routing Area people.
> 
> If ANIMA succeeds, we will have simply extended that original DARPA requirement.
> 
>    Brian
> 
> > 
> > Cheers
> >     Toerless
> > 
> >>    Brian
> >>>
> >>> Michael
> >>>
> >>>
> >>>
> >>> On 26/02/18 22:21, Brian E Carpenter wrote:
> >>>> While looking at Pascal's ACP review, I noticed that although ANIMA 
> >>>> scope is limited by charter to "professionally managed" networks, 
> >>>> we do not mention that scope in draft-ietf-anima-reference-model.
> >>>> It seems like something to be added to the Introduction.
> >>>>
> >>>> Comments?
> >>>>
> >>>> Regards
> >>>>     Brian Carpenter
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> Anima mailing list
> >>>> Anima@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/anima
> >>>
> >>> _______________________________________________
> >>> Anima mailing list
> >>> Anima@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/anima
> >>>
> >>
> >> _______________________________________________
> >> Anima mailing list
> >> Anima@ietf.org
> >> https://www.ietf.org/mailman/listinfo/anima
> > 
> 
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima
> 
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima

-- 
---
tte@cs.fau.de


From nobody Thu Mar  1 09:36:25 2018
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B75112D946 for <anima@ietfa.amsl.com>; Thu,  1 Mar 2018 09:36:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.959
X-Spam-Level: 
X-Spam-Status: No, score=-3.959 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 aXZyKTep677m for <anima@ietfa.amsl.com>; Thu,  1 Mar 2018 09:36:23 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32521120047 for <anima@ietf.org>; Thu,  1 Mar 2018 09:36:23 -0800 (PST)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 4E46258C4AF; Thu,  1 Mar 2018 18:36:19 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 34913B0DBDB; Thu,  1 Mar 2018 18:36:19 +0100 (CET)
Date: Thu, 1 Mar 2018 18:36:19 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: "Fries, Steffen" <steffen.fries@siemens.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, Michael Richardson <mcr@sandelman.ca>, "anima@ietf.org" <anima@ietf.org>
Message-ID: <20180301173619.GC17673@faui40p.informatik.uni-erlangen.de>
References: <21379.1519857984@obiwan.sandelman.ca> <451660e6-9ac2-5d44-bef9-1546baa9b6a1@gmail.com> <F8D06C29-8FCD-4406-92C3-19EEECB4482B@siemens.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F8D06C29-8FCD-4406-92C3-19EEECB4482B@siemens.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/h3PJymvNpvlaZDln47uty20i-cA>
Subject: Re: [Anima] Proposal of enhancing the BRSKI example scope with CMP
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2018 17:36:24 -0000

On Thu, Mar 01, 2018 at 06:45:27AM +0000, Fries, Steffen wrote:
> We came up with the proposal as the current title of the document gives the impression, that BRSKI would solely work with EST as it is the only example stated. As we see different use cases, which already target CMP, we thought it would be good to cover it in the base document. If the schedule of the document is that tight, then an extension in terms of a separate document might be the way to go.

Lets see, i think the WG hat is most fitting for this email, but not quite sure:

Its not only the timing, its also the complexity of a resulting document. How about we wire an RFC that descrbies both IPv4 and IPv6 together in one doc ? Would you think thats a good document structure ? The comparison may suck, but i think the resulting documents would suck even more ;-)

We already have in all our first round documents that we 
>re just finishing now the problem of scope creep and i wish we could have more modularized document structure, but i think this is a common problem of starting working groups, that if you start with many documents, especially when you're interdepending, you increase the chance of failing on a piece. 

Once we have shown success of round one with BRSKI/ACP, i think it will be a lot easier, to get variations of these themes as working group drafts, especially when there is a clear industry desire for such variations:

For once, a variation can always be less explanatory by hopefully being able to refer to
the base document (like BRSKI) for explanations and/or reuse. 

Secondly, the scope of such new documents is likely much easier to set than it was with the
original documents.

Thirdly, IMHO, such variations might not even need re-chartering as long as they can be
interpreted to do the same thing as what we've already chartered.

In the case of the ''BRSKI'' charter item, i would say that procedures for better support of 
offline device bootstrap should already be in charter. BRSKI has already some loose suggestions
in appendices. Of course, AD ultimately decides (after WG proposes ;-).

I personally do very much welcome document submissions for work in this area, even if just
to stop scope creep discussion for the BRSKI document, but i think as a WG we should not
try to accept this as a WG item before we have pushed BRSKI to IESG, but i would really like that to
happen before 102. More importantly though, it would be nice to discuss what scope specific documents
should have. We already have variations of BRSKI and vouchers coming up, and i can see
especially for supporting offline operations a lot of possible varieties.

Cheers
    Toerless

> >    Brian
> 
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima

-- 
---
tte@cs.fau.de


From nobody Thu Mar  1 12:40:55 2018
Return-Path: <steffen.fries@siemens.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 518E2131441 for <anima@ietfa.amsl.com>; Thu,  1 Mar 2018 12:40:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.92
X-Spam-Level: 
X-Spam-Status: No, score=-6.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 hZOjcLXYjChE for <anima@ietfa.amsl.com>; Thu,  1 Mar 2018 12:40:52 -0800 (PST)
Received: from david.siemens.de (david.siemens.de [192.35.17.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52C4D12FB56 for <anima@ietf.org>; Thu,  1 Mar 2018 12:40:47 -0800 (PST)
Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id w21KegFj014651 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 1 Mar 2018 21:40:42 +0100
Received: from DEFTHW99ERJMSX.ww902.siemens.net (defthw99erjmsx.ww902.siemens.net [139.22.70.135]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTPS id w21KefF4030247 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 1 Mar 2018 21:40:41 +0100
Received: from DENBGAT9ERHMSX.ww902.siemens.net (139.22.70.143) by DEFTHW99ERJMSX.ww902.siemens.net (139.22.70.135) with Microsoft SMTP Server (TLS) id 14.3.361.1; Thu, 1 Mar 2018 21:40:41 +0100
Received: from DENBGAT9EH2MSX.ww902.siemens.net ([169.254.6.65]) by DENBGAT9ERHMSX.ww902.siemens.net ([139.22.70.143]) with mapi id 14.03.0361.001; Thu, 1 Mar 2018 21:40:40 +0100
From: "Fries, Steffen" <steffen.fries@siemens.com>
To: Toerless Eckert <tte@cs.fau.de>
CC: Brian E Carpenter <brian.e.carpenter@gmail.com>, Michael Richardson <mcr@sandelman.ca>, "anima@ietf.org" <anima@ietf.org>
Thread-Topic: [Anima] Proposal of enhancing the BRSKI example scope with CMP
Thread-Index: AQHTsOX538yXpc73rE65sSHDrEmaXqO6gI4AgABvapWAAKUVgIAAREXU
Date: Thu, 1 Mar 2018 20:40:39 +0000
Message-ID: <85DA81B6-4000-40F5-95F3-15AA5FE1E279@siemens.com>
References: <21379.1519857984@obiwan.sandelman.ca> <451660e6-9ac2-5d44-bef9-1546baa9b6a1@gmail.com> <F8D06C29-8FCD-4406-92C3-19EEECB4482B@siemens.com>, <20180301173619.GC17673@faui40p.informatik.uni-erlangen.de>
In-Reply-To: <20180301173619.GC17673@faui40p.informatik.uni-erlangen.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/4C3j7zcjq6N-4rsJ6kRY3zTcvgY>
Subject: Re: [Anima] Proposal of enhancing the BRSKI example scope with CMP
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2018 20:40:54 -0000

> On 1. Mar 2018, at 18:36, Toerless Eckert <tte@cs.fau.de> wrote:
>=20
>> On Thu, Mar 01, 2018 at 06:45:27AM +0000, Fries, Steffen wrote:
>> We came up with the proposal as the current title of the document gives =
the impression, that BRSKI would solely work with EST as it is the only exa=
mple stated. As we see different use cases, which already target CMP, we th=
ought it would be good to cover it in the base document. If the schedule of=
 the document is that tight, then an extension in terms of a separate docum=
ent might be the way to go.
>=20
> Lets see, i think the WG hat is most fitting for this email, but not quit=
e sure:
>=20
> Its not only the timing, its also the complexity of a resulting document.=
 How about we wire an RFC that descrbies both IPv4 and IPv6 together in one=
 doc ? Would you think thats a good document structure ? The comparison may=
 suck, but i think the resulting documents would suck even more ;-)
>=20
Well, I see were you are heading to ;-) The intention of the proposal was n=
ot to increase the complexity of the base document. But given your example,=
 having a base document that is agnostic to the enrollment and enhancement =
documents that map an enrollment protocol would probably be ideal regarding=
 complexity. From your  statement below, I conclude that the process of doc=
ument creation and scoping can be cumbersome.  But=82 I=91m certainly not i=
n the position to argue about document structure as I=92m stepping in late.=
=20


> We already have in all our first round documents that we=20
>> re just finishing now the problem of scope creep and i wish we could hav=
e more modularized document structure, but i think this is a common problem=
 of starting working groups, that if you start with many documents, especia=
lly when you're interdepending, you increase the chance of failing on a pie=
ce.=20
>=20
> Once we have shown success of round one with BRSKI/ACP, i think it will b=
e a lot easier, to get variations of these themes as working group drafts, =
especially when there is a clear industry desire for such variations:
>=20
> For once, a variation can always be less explanatory by hopefully being a=
ble to refer to
> the base document (like BRSKI) for explanations and/or reuse.=20
This supports my impression of the base document and additional enhancement=
 documents.
>=20
> Secondly, the scope of such new documents is likely much easier to set th=
an it was with the
> original documents.
Agreed
>=20
> Thirdly, IMHO, such variations might not even need re-chartering as long =
as they can be
> interpreted to do the same thing as what we've already chartered.

> In the case of the ''BRSKI'' charter item, i would say that procedures fo=
r better support of=20
> offline device bootstrap should already be in charter. BRSKI has already =
some loose suggestions
> in appendices. Of course, AD ultimately decides (after WG proposes ;-).
Step 5 in section 2.1 in BRSKI mentions EST as example for an enrollment pr=
otocol. Based on that I assumed other enrollment protocols would in general=
 applicable as well.

> I personally do very much welcome document submissions for work in this a=
rea, even if just
> to stop scope creep discussion for the BRSKI document, but i think as a W=
G we should not
> try to accept this as a WG item before we have pushed BRSKI to IESG, but =
i would really like that to
> happen before 102.
You made it clear that finishing the base spec has the highest priority.

> More importantly though, it would be nice to discuss what scope specific =
documents
> should have. We already have variations of BRSKI and vouchers coming up, =
and i can see
> especially for supporting offline operations a lot of possible varieties.
Yes, I=91m sure there are several approaches for offline enrollment. The re=
ason for proposing a profile of CMP basically stems on its success in exist=
ing deployments for online and offline use cases in a single solution.=20

Regards
   Steffen
>=20
> Cheers
>    Toerless
>=20
>>>   Brian
>>=20
>> _______________________________________________
>> Anima mailing list
>> Anima@ietf.org
>> https://www.ietf.org/mailman/listinfo/anima
>=20
> --=20
> ---
> tte@cs.fau.de


From nobody Thu Mar  1 13:39:16 2018
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2090212FAC0 for <anima@ietfa.amsl.com>; Thu,  1 Mar 2018 13:39:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 6Nx7N5ePxh01 for <anima@ietfa.amsl.com>; Thu,  1 Mar 2018 13:39:13 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E05C12FAB8 for <anima@ietf.org>; Thu,  1 Mar 2018 13:39:12 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id DDF8120091 for <anima@ietf.org>; Thu,  1 Mar 2018 16:47:02 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B9E6980E6A for <anima@ietf.org>; Thu,  1 Mar 2018 16:39:11 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "anima\@ietf.org" <anima@ietf.org>
In-Reply-To: <F8D06C29-8FCD-4406-92C3-19EEECB4482B@siemens.com>
References: <21379.1519857984@obiwan.sandelman.ca>, <451660e6-9ac2-5d44-bef9-1546baa9b6a1@gmail.com> <F8D06C29-8FCD-4406-92C3-19EEECB4482B@siemens.com>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Thu, 01 Mar 2018 16:39:11 -0500
Message-ID: <30755.1519940351@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/vcfBaWvimdruwM1UHSla_Dx5K34>
Subject: Re: [Anima] Proposal of enhancing the BRSKI example scope with CMP
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2018 21:39:15 -0000

--=-=-=
Content-Type: text/plain


Fries, Steffen <steffen.fries@siemens.com> wrote:
    >> <brian.e.carpenter@gmail.com> wrote:
    >>
    >> On 01/03/2018 11:46, Michael Richardson wrote: ...
    >>>> Even though the BRSKI document is already advanced, we would like to
    >>>> propose to also include CMP as further example for certificate
    >>>> enrollment in BRSKI. This inclusion would make it also easier for
    >>>> other standards or frameworks to consider security bootstrapping
    >>>> based on BRSKI.
    >>>
    >>> I think that it would be very difficult to hack CMP into the BRSKI
    >>> document at this point.
    >>
    >> As a matter of principle, it seems better to get BRSKI published as
    >> quickly as possible to meet the WG milestone, and then publish any
    >> extensions as separate documents.

    > I was looking into the charter and based on the date of the initial
    > draft of the document I somehow feared that the document is already in
    > the final state. I did not find an expected timeline on when the draft
    > is expected to be finalized.

As soon I get back to the Shepherd review (sometime later tonight perhaps),
then I hope that we'll get into WGLC.

    >> It seems like a good idea to work on such extensions. But one step at
    >> a time :-).

    > We came up with the proposal as the current title of the document gives
    > the impression, that BRSKI would solely work with EST as it is the only
    > example stated. As we see different use cases, which already target
    > CMP, we thought it would be good to cover it in the base document. If
    > the schedule of the document is that tight, then an extension in terms
    > of a separate document might be the way to go.

BRSKI is an extension of EST.
Making it an extension of CMP would be a different protocol.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlqYcv8ACgkQgItw+93Q
3WVZgggAsjndmiyTOIK/C4MUD87E+vqDT8qXBWWHsdBZxL9ueZWgy3zS5x1aEk+P
YxTIMT8ihvUkRRt9dmcLN6BOUfzkUQxzWxLir6Ekb0JvvQMOoXPwgbQiikN8FIzI
xzut/TgsAR840rf+dQGcFuTezGoQAr1Quhe2ngM4umXgNElNaMUVGCaLOwruO4hh
V7CUi3Cyf/6YCxy8Y55RqBslMQk8yv9tbqyWDVfM00sgMI2hS6X+oqtFh9fgfwU+
TZZiyQ0gIoeK+XSqjT7eP4A+EmixKNGFmj7np+6Ldd45++lCZp2YJWOwSehbOYQW
unC6amCseAwx7Ka8P0IkWZOwaCdUWQ==
=s9xP
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Mar  1 14:11:00 2018
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B839012FAC7 for <anima@ietfa.amsl.com>; Thu,  1 Mar 2018 14:10:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 sGnMw0CY4T9u for <anima@ietfa.amsl.com>; Thu,  1 Mar 2018 14:10:57 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21D6C12FAC6 for <anima@ietf.org>; Thu,  1 Mar 2018 14:10:57 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 1079120091 for <anima@ietf.org>; Thu,  1 Mar 2018 17:18:47 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D4A4580BC4 for <anima@ietf.org>; Thu,  1 Mar 2018 17:10:55 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
In-Reply-To: <HE1PR0701MB22035000450382804933C860E8C60@HE1PR0701MB2203.eurprd07.prod.outlook.com>
References: <f134fecd-7749-48ed-e336-657ac045d5a5@gmail.com> <03ab2d02-f7d1-4c39-40c0-d232c909a111@gmail.com> <e968de00-11cc-da4a-2e31-721cb8d0b4d2@gmail.com> <20180228155157.GA17673@faui40p.informatik.uni-erlangen.de> <ddd91d8a-d25e-d3fb-6e16-eb585d509c41@gmail.com> <HE1PR0701MB22035000450382804933C860E8C60@HE1PR0701MB2203.eurprd07.prod.outlook.com>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Thu, 01 Mar 2018 17:10:55 -0500
Message-ID: <5318.1519942255@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/tmipTz9tY6N5Y2J8UzdmtYYbJcU>
Subject: Re: [Anima] "professionally managed" and the reference model
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2018 22:10:59 -0000

--=-=-=
Content-Type: text/plain


"Ciavaglia, Laurent (Nokia - FR/Paris-Saclay)" wrote:
    > Does the need to explicitly distinguish ANIMA work from HOMENET work
    > still exist

yes. It's not just because we want to stay out of HOMENET's hair.
It's because we have a different set of assumptions.   In ANIMA we may
reasonably say, "THERE WILL BE AN X" (which will properly run, etc.).
We assume a budget for equipment and for people, and we assume that there are
more than two people involved.   We also assume that a goal we have is to
reduce the amount of effort (and travel!) required by the most senior of the
people.

While in HOMENET, you can not postulate an X unless you can determine
who will provide it, how many will be provided, and which one will be elected
as the master-X.   HOMENET also can generally assume that the network is
relatively small: if not in number of nodes, then at least in extent.
For instance,. a rural school with 200 chromebooks and no support from a
centralized IT person falls into HOMENET.

While a boutique global ISP might have only 100 routers, two in each of 50
cities, and clearly falls into ANIMA, despite having fewer nodes than the
rural school.

At the same time, a (inter)network of rural school(s), being managed
centrally by an IT person is again, ANIMA.

    > FWIW, my understanding of "professionally managed" is "managed _BY_ a
    > professional".  Here the person or entity being the "professional" is
    > providing a service (paid or free) to manage a given network as part of
    > her job (or contract).  In the mission of her job (or contract) the
    > professional is "external" to the user of the network being managed
    > (i.e. act as a first/third party).

We argued about the term, and concluded that this term was sufficiently
inclusive that it covered Tier-1 ISPs, Residential ISPs, as well as big
and medium sized enterprises.   It's unlikely that a small enterprise would
on it's own count, unless they had outsourced their management.   We just
don't care how the profession is involved.

    > * note: a homenet can well be very professionally managed in the sense
    > that it follows BCP but it does not mean it is managed by someone for
    > which it is the job to do this (e.g. John Doe, who is a skilled
    > engineer, manage its homenet for himself, or manage homenets for his
    > friends/relatives...)  ** note: a homenet can well be completely
    > unmanaged, i.e. relying exclusively on full plug-and-play mechanisms.

So, again, in your home or mine, our home networks are likely more
professionally managed than many enterprise networks.  Am I more likely to
use ANIMA than HOMENET protocols in *MY* home?  Maybe.
That's why we didn't write "home" or "enterprise" networks.

Having said this, there is interest in trying to find a way to make BRSKI
work in a HOMENET.  The problem is that X=JRC, and how will it be provided?

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlqYem8ACgkQgItw+93Q
3WXdhQgAunnD2TZXuDyVjAn4MYGUU/1tibtEH1WukVgzALvoakS0UbKtlUvLCIJW
g0rZ2xVgDX82WC6DWFB68JM2ChrMRafcfULbxndCgTHyte/GpDDkJsp8NXOKyie2
lkgUFT27/D4suuPC/Y9FbO1/0gzzhu1V5WeIIxp0hZwfpYxv6veyLdfXIJ8DW9WZ
nOwslqnbvHbE/1rG0jhQhXwUPbP/nbpHiaa72EPIxH2RS+4vzwQ8b5ojTiRRDuRU
GJiIPDTG9mf3FFEI8mMK+JTUcr8JLy6vby/SFZYKD9oOqZVwYAc5FcEy4ADvLWUx
dtUwgpgydEZB+yM2NK0C/6kMNrlWmg==
=wOll
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Mar  1 18:18:56 2018
Return-Path: <jmh@joelhalpern.com>
X-Original-To: anima@ietf.org
Delivered-To: anima@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BF1F5127201; Thu,  1 Mar 2018 18:18:45 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <rtg-dir@ietf.org>
Cc: anima@ietf.org, ietf@ietf.org, draft-ietf-anima-autonomic-control-plane.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.73.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151995712572.15727.501156104518975926@ietfa.amsl.com>
Date: Thu, 01 Mar 2018 18:18:45 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/7lgx_lK2vmf6PS6CJdhPSQ__Rzo>
Subject: [Anima] Rtgdir telechat review of draft-ietf-anima-autonomic-control-plane-13
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2018 02:18:46 -0000

Reviewer: Joel Halpern
Review result: Ready

I have been selected as the Routing Directorate reviewer for this draft. The
Routing Directorate seeks to review all routing or routing-related drafts as
they pass through IETF last call and IESG review, and sometimes on special
request. The purpose of the review is to provide assistance to the Routing ADs.
For more information about the Routing Directorate, please see
​http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

Although these comments are primarily for the use of the Routing ADs, it would
be helpful if you could consider them along with any other IETF Last Call
comments that you receive, and strive to resolve them through discussion or by
updating the draft.

Document: draft-ietf-anima-autonomic-control-plane-13
Reviewer: Joel Halpern
Review Date: 1-March-2018
IETF LC End Date: N/A
Intended Status: Proposed Standard

Summary: I have some minor concerns about this document that I think should be
resolved before publication.

Major: N/A (Note that three comment is marked *** as they may be more
significant.)

Minor:
    The description of the ACP In the introduction should probably note that
    the addition of Management capability is beyond the definition provided in
    section 5 of RFC 7575, and is included to complete the needed set of
    functionality.

    The definition of data-plane seems to assume that all forwarding (and
    control?) in all nodes is structured in terms of VRFs.  That seems to
    overly constrain implementation architecture.  Using VRF to to describe the
    ACP functionality is a little odd, but likely defnesible.  Declaring that
    all other functionality is in VRFs seems a step too far.

    The definition of Intent in the terminology section seems to be different
    from the cited definition in the anima reference model.  "Intent" there
    seems to refer to a policy language, not an interface.

    It is unclear how the flexible policy defined in section 5 bullet 2 (about
    which nodes are ACP peer candidates) is consistent with autonomic
    operation.  It seems that the flexibility is important, so there should be
    some explanation here about how this is consonant with the stated goals.  I
    understand that the bootstrap comes from BRSKI, but I do not think that is
    where the policy comes from?

    The BNF is section 6.1.1 seems to have some oddities.  It may be that none
    of these can happen for reasons that are described elsewhere, but as
    written:
  If the local-info is empty, the localpart will be "rfcxxxx." and thus the
  domain info will be "rfcxxxx.@domain".  Is the period really required in the
  absence of the local-info If the rsub is empty, but the extensions are not
  empty, it looks like there will be two plus signs (following the optional
  acp-address) before the first extension.  Is that intended as the way to
  indicate the absence of the rsub? It also seems odd that the rsub (which is a
  domain extension) appears in the local-part of the domain information, not in
  the domain name.  Even though for hashing purposes it is concatenated, with a
  period, with the domain name.
 If these oddities are intentional, then there ought to be explanations so the
 reader is not confused.

    I presume there is not an assumption that all ULA addressed communicating
    with a node which supports the ACP will be over the ACP.  As I understand
    it, ULAs may well have other uses outside of ANIMA / the ACP.  Which leads
    to a question about how the text in 6.1.3 "If the CDP URL uses an IPv6 ULA,
    the ACP node will try to reach it via the ACP." is expected to be supported?

    The discovery text in section6.3 states that discovery should be run in
    every physical interface.  Is this intended to be restricted by policy, as
    described in section 5, bullet 2?

***    The explanation in section 6.5 on channel selection (and security
protocol selection) is worded as if the described behavior will lead to
reliable interoperation.  The text on why there are limitations (reasonable)
doe not explain why mandating dTLS support would not be a reasonable step.   (I
hope I missing something, as otherwise this is a major problem rather than
being minor.)  It is also hard to align this with the requirements in section
6.7.3.

    6.8.2.1 has text about "hop-by-hop reliable retransmission as provided for
    by TCP".  I am unable to determine what this is saying.

    If I have used section 6.10.3 properly, when the Zone-ID is 0, all nodes
    within the ULA are within a flat address space.  that does turn the address
    into an identifier.  It is, as far as I can tell from the description,
    still a locator in that packets will be routed to the node using the
    address including the node identifier.  It just means that routing has to
    work in /127 addresses.  (There is also a reference to "identifier" in
    6.10.3.1.  From the usage there, I think that the intention is that this is
    the generic "name" for the node.  Given that it is routable, it is simply
    an addresses, not an identifier or a locator.)

    The description in section 6.10 / 6.10.1 / 6.10.2 is about the schema
    identification is very confusing, and arguably a bad design.  The two
    schemas use the same schema identifier.  The difference in interpretation
    is actually provided by the last bit in the upper 64.  If these are the
    same schema, then it should not need a bit to differentiate them.  They
    should be explained as a single schema.  Which would presumably result in
    the Z bit being part of the zone / subnet field.   If they are two
    different schemas, then move the differentiation to part of the schema
    identifier (making it 3 bits).  This sort-of different but sort-of the same
    makes implementation "interesting".  Even if this is extra bit is only
    needed for schema 00b, it should be in front of the Zone / subnet, not
    after it. This leads to the obvious observation that either we need two
    bits, of which we will have 3 settings, and we will use the fourth setting
    as an extension mechanism if we ever need more formats, or we need at least
    three bits all the time because we seriously think there will be more
    formats.

    In section 6.10.5, after stating that it is not even known what the needed
    usage is for more V values, the document goes on to introduce the
    complexity of classful nodes numbers, with the leading bit indicating how
    long the node-number is.  Yes, the rest of the text in that bullet tries to
    explain why you need both sizes.  It seems like needless complexity that
    begs for mistakes in implementation.

    In section 6.11.1.11 in describing the prefix lengths, I thought that the
    point of zone addressing was to allow the use of /64 prefixes.  But it
    seems here that we will not do so ?

    Section 6.12.5 says "ACP nodes MUST NOT derive their ACP virtual interface
    IPv6 link local address from their IPv6 link local address used on the
    underlying interface".  But it does not then seem to provide any advice on
    what is expected to be used.  Is the loopback ACP supposed to be used
    somehow?  Or?

    The "configuration" description in 8.2.1 provides a nice description of
    what information is needed, and what choices are allowed.  It does NOT
    describe a method for configuring the information.  Please tune the
    introductory material.

***    Section 10.3.2 paragraph 2 says that devices should change the meaning
of "admin down" to mean "down for everything except ACP / Anima".    I can
understand why, in an autonomic network, such a state is desirable.  However,
that really should be a different state from "admin down".  Operators already
understand "admin down" as meaning that this interface will not be used for any
traffic.  Changing that is fairly drastic.  "admin limited" or "admin ACP-Only"
would seem much better than changing the meaning of "admin down".  The
justification in the text seems to be a desire to prevent an operator from
doing what he intends.  that seems backwards.  (Note that the distinction
between administrative state vs operational state, aka failed, is already well
understood.)

***    The notion in 10.3.6 that the device should refuse to disable
functionality when an authorized administrator directs such seems flatly wrong.

Editorial / Nits:
    Section 6.3, in talking about DULL GRASP refers to the grasp internet
    draft.  It refers to section 3.5.2.2.  there is no 3.5.2.2 in the grasp
    I-D.  As best I can guess the reference should be 2.5.2.

    In the various formats in section 6.10, the lowest bit of the upper 64 bits
    is mandated to be 0.  Presumably, there is some reason for doing this.  It
    would be nice to explain it.

    In section 6.10.5, in the text about how many V values are allowed, the
    text reads: "2^16 - 65536" which would be 0.  I believe that the intention
    is "2^16 (i.e. 65536)"

   Section 9.2.2 paragraph 2 begins "Group members must overall the secured". 
   While I can guess what is intended, I would prefer that were in grammatical
   English so as to avoid guessing.

    Section 10.5 provides the requirements that were met by choosing RPL for
    the routing protocol.  Likely RPL is a reasonable choice.  Since this
    section does not provide comparison or list any alternatives, I would
    suggest changing "explanation" to "motivation".


From nobody Fri Mar  2 07:13:38 2018
Return-Path: <ofriel@cisco.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1A191276AF for <anima@ietfa.amsl.com>; Fri,  2 Mar 2018 07:13:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level: 
X-Spam-Status: No, score=-14.531 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 viTCgiihmRRo for <anima@ietfa.amsl.com>; Fri,  2 Mar 2018 07:13:34 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AD9C124BAC for <anima@ietf.org>; Fri,  2 Mar 2018 07:13:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3470; q=dns/txt; s=iport; t=1520003614; x=1521213214; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Ez8dEz9MUhmO4xZY9gmgSrtfV1PIE86PnQfqC+Qrmcg=; b=aJdEyIuBafbbrwiIlNkxBQMFPCfmvycP2CR4eIdnVIoTs+wTnkC5C9Cd rYrRJ9I+G1rHHdS1zki00uwDaJD42MEXMDJK0dNxNMET8eBGUh1OoUzRt 5JEFtpTbMrrDZu2c2nLXw8b00Z+dzKwDGzgdhlWpbQszuXd2lQd7UW4n1 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DzAADraJla/4UNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYNQZnAoCo1tjXmCAoEWlC2CFQoYDYFagzECgmEhNBgBAgEBAQE?= =?us-ascii?q?BAQJrJ4UjAQEBBAEBOC0HCwUHBAIBCA4DBAEBAR4JBycLFAkIAgQBDQUIhRMQq?= =?us-ascii?q?06IY4ImBYUmgQ2BHIFXgWaDLYMuAQEDAYFXhgMEml4JAoZQiiGPAol8hywCERk?= =?us-ascii?q?BgS0BHjiBUnAVOoJDgjEcgXt3izSBGAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.47,412,1515456000"; d="scan'208";a="361000859"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Mar 2018 15:13:33 +0000
Received: from xch-rcd-011.cisco.com (xch-rcd-011.cisco.com [173.37.102.21]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id w22FDXq4008690 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 2 Mar 2018 15:13:33 GMT
Received: from xch-rcd-012.cisco.com (173.37.102.22) by XCH-RCD-011.cisco.com (173.37.102.21) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 2 Mar 2018 09:13:32 -0600
Received: from xch-rcd-012.cisco.com ([173.37.102.22]) by XCH-RCD-012.cisco.com ([173.37.102.22]) with mapi id 15.00.1320.000; Fri, 2 Mar 2018 09:13:32 -0600
From: "Owen Friel (ofriel)" <ofriel@cisco.com>
To: Toerless Eckert <tte@cs.fau.de>, Michael Richardson <mcr+ietf@sandelman.ca>
CC: "Max Pritikin (pritikin)" <pritikin@cisco.com>, "anima@ietf.org" <anima@ietf.org>, "Eliot Lear (elear)" <elear@cisco.com>
Thread-Topic: [Anima] BRSKI over 802.11
Thread-Index: AQHTpbS80kr8dImS10GyGhws45k3TKOkp4YAgAABSoCAATh3oIAAjAeAgACdrhCAAJidAIAAFaSAgBBw3KCABPxbIA==
Date: Fri, 2 Mar 2018 15:13:32 +0000
Message-ID: <7edd63c0a54c46d48735754afa2ef55e@XCH-RCD-012.cisco.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F45C7960181@nkgeml514-mbx.china.huawei.com> <b0125355-103d-a5a2-a6cb-46557b94d4e1@cisco.com> <1CD3D5E0-AFB4-426F-A065-AB1CA3203387@cisco.com> <20180214165601.GB27823@faui40p.informatik.uni-erlangen.de> <31460.1518635300@obiwan.sandelman.ca> <20180214191257.GC27823@faui40p.informatik.uni-erlangen.de> <ea5ad820e0a04fb9b9108507e06b6d91@XCH-RCD-012.cisco.com> <7255.1518732749@obiwan.sandelman.ca> <bd8cff45dcd94e279960bd1631db9bc4@XCH-RCD-012.cisco.com> <3188.1518799384@obiwan.sandelman.ca> <20180216180031.GG27823@faui40p.informatik.uni-erlangen.de> <179832fc3cae4ba0bef3f3167deda795@XCH-RCD-012.cisco.com>
In-Reply-To: <179832fc3cae4ba0bef3f3167deda795@XCH-RCD-012.cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.8.24]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/h3KVG4ocdJ3dnxDWL0vlxJWrsg0>
Subject: Re: [Anima] BRSKI over 802.11
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2018 15:13:38 -0000

Just submitted: https://datatracker.ietf.org/doc/draft-friel-brski-over-802=
dot11/


-----Original Message-----
From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Owen Friel (ofriel=
)
Sent: Tuesday 27 February 2018 11:06
To: Toerless Eckert <tte@cs.fau.de>; Michael Richardson <mcr+ietf@sandelman=
.ca>
Cc: Max Pritikin (pritikin) <pritikin@cisco.com>; anima@ietf.org; Eliot Lea=
r (elear) <elear@cisco.com>
Subject: Re: [Anima] BRSKI over 802.11

An early draft of this is now available at:

https://github.com/anima-wg/brski-over-802dot11/blob/master/brski-over-802d=
ot11.md



-----Original Message-----
From: Toerless Eckert [mailto:tte@cs.fau.de]
Sent: Friday 16 February 2018 18:01
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Owen Friel (ofriel) <ofriel@cisco.com>; Max Pritikin (pritikin) <pritik=
in@cisco.com>; Eliot Lear (elear) <elear@cisco.com>; anima@ietf.org
Subject: Re: [Anima] BRSKI over 802.11

I am not even sure we would need to come up with just one permitted option.

The two directions i see now from Owens input:

a) "enterprise" Model.

Relying on AAA server to be able to authenticate Pledges based on e.g.: EAP=
-TLS with IDevID as auth. No additional SSID needed. Should try to also ann=
ounce 802.11u GAS, but need to figure out if/how this would work in the fac=
e of multiple SSIDs supported (aka: multi-domain).

b) SSID approach
- can work without any change to 802.11 infra, just put BRSKI proxy on the =
BRSKI VLAN.
- Work without AAA, e.g.: PSK (home AP).
- multi-domain, no 802.11u support needed (unclear how ubiquitous that is).

Single domain mode where AP has only one domain offering BRSKI, BRSKI SSID =
is just called BRSKI%%, no beacon sent (called "hidden" in most UIs). Conne=
cts only to BRSKI Proxy, carries only BRKSI traffic therefore.=20

Multiple <ssid>'s on an AP, each one wanting to offer BRSKI, second and fur=
ther SSID have to be renamed to BRSKI%<ssid>. But actual SSID for BRSKI for=
 those <ssid>'s is BRSKI%<ssid>. No crypto, just connected to BRSKI Proxy.=
=20

Cheers
    Toerless

On Fri, Feb 16, 2018 at 11:43:04AM -0500, Michael Richardson wrote:
>=20
> Owen Friel (ofriel) <ofriel@cisco.com> wrote:
>     > [ofriel] I think a more comprehensive analysis of the various SSID
>     > discover options (DPP, hardcoded SSID, NAI Realm,..) and how each f=
its
>     > into the two post-SSID discovery options of (i) a new EAP-BRSKI
>     > vs. (ii) reuse of EAP-TLS (or some suitable EAP method, possibly wi=
th
>     > 2x 80.1x exchanges) is needed before any consensus on the contents =
of
>     > an ID is necessary. Unless you are suggesting than an initial ID me=
rely
>     > outlines the multiple options but makes no final recommendation
>     > yet. Happy to get started on that...
>=20
> Yes... the point of the ID would be to layout the options....
>=20
> The options-not-selected would go into an appendix of a final document=20
> to explain paths not taken.
>=20
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works=20
> -=3D IPv6 IoT consulting =3D-
>=20
>=20
>=20



> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima


--
---
tte@cs.fau.de

_______________________________________________
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima


From nobody Fri Mar  2 15:00:22 2018
Return-Path: <mcr@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84667126CC7; Fri,  2 Mar 2018 15:00:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 HiSAoXTU9Twg; Fri,  2 Mar 2018 15:00:19 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB35D126D05; Fri,  2 Mar 2018 15:00:18 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [IPv6:2607:f0b0:f:b:a11:96ff:fe01:81e0]) by relay.sandelman.ca (Postfix) with ESMTPS id 42D1E1F95A; Fri,  2 Mar 2018 23:00:11 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 868B82546; Fri,  2 Mar 2018 17:59:49 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Toerless Eckert <tte@cs.fau.de>
cc: draft-ietf-anima-bootstrapping-keyinfra@ietf.org, anima@ietf.org
In-reply-to: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de>
References: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de>
Comments: In-reply-to Toerless Eckert <tte@cs.fau.de> message dated "Wed, 14 Feb 2018 02:09:10 +0100."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 02 Mar 2018 17:59:49 -0500
Message-ID: <23390.1520031589@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/C6kwQTUP5wxEEyeYyrQBnPPKYW8>
Subject: Re: [Anima] Shepherd review draft-ietf-anima-bootstrapping-keyinfra-09
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2018 23:00:21 -0000

--=-=-=
Content-Type: text/plain


Max, please search for QUESTION.

Toerless Eckert <tte@cs.fau.de> wrote:
> 1.) Introduction
>
> a) The intro of 1. is somehat confusing to the uninitiated.
>
> Suggest the followinf replacement text for two paragraps:
>
> BRSKI provides a solution for secure zero-touch (automated) bootstrap of
> virgin (untouched) devices that are called Pledges in this document. These Pledges
> need to discover (or be discovered by) an element of the network domain to which the
> Pledge belongs to perform the bootstrap.  This element (device) is called the
> (Domain Join) Registrar.  Before any other operation, Pledge and Registrar need to
>  establish mutual trust:
>
> Then the four existing bullet points, but number them.
>
> Then followed by th following paragraph to replace the existing paragraph after
> the four bullet poins.

All done, including:

> b) It would be nice to have a paragraph mentioning the proxy as a mean to
> provide easier connectivity for Pledges (no need for full network connectivity).

Also, we have tried to always say "PKIX" certificates, since the whole
"X.509" space is decades old... Credit to IETF for keeping it alive.

> 1.1)
>
> a) "other Bootstrapping Approaches": "other" -> "prior" or "existing" ?

I'll take Prior, but I'm not crazy about the change.

> b) "_or_ that domain-specific keying material". Is this not an _and_ ?

It's an or.
It's *insecure* *OR* there is a domain-specific key.

> c) "in a costly and non-scaleable manner". "non-scaleable" may be hard to
> argue. Whole economies where built on manual labor. Might rather use
> qualifiers such as "little or not at all automated", "error-prone" and/or
> referring to physical security (.e.g: trusted pre-staging location).

Generally, any process that requires linear amount of labour (or capacity) to
be added in order to grow linearly are consider non-scalable.
Of course you can make pigs fly with enough rockets, but it does not work for
arbitrarily sized pigs.

> d) "existing mechanisms" -> "existing automated mechanisms".

okay.

> e) Paragraph 2 and following about EST: The first two sentences sound
> contradictory/conflicting. "...minimize user action..." , "details a set of
> non-autonomic bootstrapping methods". Suggest text like:

>
> "EST does reduce user actions during bootstrap but does not provide
> solutions for how the following protocol steps can be made autonomic
> (not involving user actions).

okay, slightly adapted.

> -----------------------------------------------------------------------------
> 1.3)
>
> a) The order of paragraphs is confusing. Even if the mayority of readers
> (which i don't think) would primarily be interested in class 1 devices,
> it is irritating in style and context to start with the first two
> paragraphs.
>
> I would suggest to start with existing paragraph 3, change maybe the
> sentence to "This solution (BRSKI) can support large router platforms..."
>
> Then insert the first two paragraphs after current paragraph 5. All the
> text after paragraph 5 already discusses constrained situations so
> it would nicely follow on to the first two paragraphs.

okay.

> b) paragraph 5 is confusing: What is a handoff, why would somebody
> even think to apply BRSKI in a handoff, and why is there a normative,
> capital letter SHOULD. Here is how i would write it more explanatory
> (if i understand the implied use case correctly):
>
> BRSKI could be used by nomadic or mobile devices to aquire certificates
> used as credentials to access the network at the new location. This
> is usually called handoff. Nevertheless, BRSKI is not intended for low-latency
> handoff which is usually a requirement in mobility solutions (e.g.: seamless
> handover). For these solutions BRSKI could be used to aquire keying
> material and re-use that during handover without re-initiating BRSKI
> during handover later on.
>
> (which is also implying that re-using BRSKI in nomadic environments
>  is not off the table, but not saying so explicitly because we really
>  have not thought that trough a lot).

I have adapted your paragraph replacing the one we had.

> c) It would loosen up a very long section to create three subsection headings
>
> - supported environments
> - constrained envionments
> - network access control

Done.

> -----------------------------------------------------------------------------
>
> Section 2 1)
>
> a) ..Each component is logical and may be combined with other components as necessary..
>
>     Ok. I always want the pledge to live in the same device as the MASA.
>
>     Would suggest deleting that sentence. More harm than benefit.

Hmm.   The Circuit Proxy, Domain Registrar and Certificate Authority could be
done component.  I think that we need to say something about that.

> b) I suggest to move section 2.4 up to become section 2.1) directly after the
> picture in section 2., because otherwise there is no explanaction following
> the picture.
>
> c) "The a domain" (delete a)

I think that you mean it becomes section 2.2, after the first state machine?
(c) perhaps already done.

> -----------------------------------------------------------------------------
>
> Section 2.1
>
> a) The term "Request Join" is only used here, and its IMHO not very logical
> (disclaimer: toerless: en.wikipedia.org/wiki/ESL). It sounds to me like the
> pledge says "i want to join". And also sounds as if the pledge could be
> disappointed if rejected. I would rather call it "Domain membership inquiry".
> Or if you're hooked up on the term "joining", then maybe "Join Inquiry".

QUESTION?  what do you think?
Was "Request Voucher" one of the options you were thinking about?

> Whatever best makes it clear that rejection is a perfect and important
> outcome option.
>
> b) Please see my issue section 5.1 a). If you agree with that statement, then there
> should be no "rejected" arrow in Figure 2 coming out of the "Identify"
> block.

okay, I'll deal with this in that section.

> I would also suggest that the "Bad Vendor response" arrow does not come out
> of the "Imprint" block but out of the "Request Join" block. AFAIK, this is
> an error reply to the Request Voucher, so it happens before imprinting
> (imprinting happens only when there is a vocker reply. AFAIK).

[It says, "Bad MASA response" now, just for the reader who is following]

> I don't think "Bad Vendor reply" in Figure 2 is a good term. Most logical
> to me would
> be "Error or not member". In any case, the text in section 2 below should
> mention the exact words used on the labels, the text is missing ll the
> labels on the left: "Factory reset", "Enroll Failure", "Bad Vendor
> response",...

more discussion.

> c)
>
>  Point 1 nicely explains how this is done during TLS.
>
> Likewise, Point 2 should mention that this is the "Voucher Request", and
> Point 3 should mention that it is the "Voucher Reply" - so readers can match
> up section 2.1 with the rest of the document.
>
> remove the "e.g." from "protocol, e.g. Enrollment over". Otherwise some text
> outlining when something else than EST is to be used. (see next comment).

QUESTION: I couldn't figure out what text this applies to.

> d)
>
> I am missing in the initial chapters a succinct summary how EST enrollment is optional and
>  what can be achieved with/without it, there is only some side sentences later in the
> EST sections. I would suggest to insert such an explanation here.
>
> After point 4 insert (unnumbered) paragraph:
>
> | After step 4, the pledge has received  and authenticated an explicit TA (trust anchor)
> | (pinned-domain-cert in the Voucher response). In some use cases this may be sufficient
> | and the bootstrap can be terminated here. The pledge can now use this TA to securely
> | trust domain members, but it can not securely identify itself to them as a domain member.
> | Therefore BRSKI usually proceeds with the following steps that support this via EST
> | enrollment (see also 5.5.1 for the limitations of the trust feasible through the imprint).
>
> Also maybe insert some dotted line between imprint and enroll in Figure 2 to
> highlight this distinction. Maybe with "mandatory" / "optional" (EST enroll part)
> on the right hand side

QUESTION: Max?

> -----------------------------------------------------------------------------
> Section 2.2
>
> a)
>
>  The core sentence is hard to understand because it does not spell out the
> implication of the alternatives:
>
>  At the
>  lowest security levels the MASA server can indiscriminately issue
>  vouchers.  At the highest security levels issuance of vouchers can be
>  integrated with complex sales channel integrations that are beyond
>  the scope of this document.
>
> Would suggest amending like this:
>
>  At the lowest security levels the MASA server can indiscriminately issue
>  vouchers AND LOG CLAIMS OF OWNERSHIP BY DOMAINS.  At the highest security
>  levels issuance of vouchers can be integrated with complex sales channel
>  integrations that are beyond the scope of this document BUT THAT WOULD
>  INTENT TO VERIFY ACTUAL (LEGAL) OWNERSHIP OF THE PLEDGE BY THE DOMAIN.

I split it into more sentences, but took the intent.

> b)
>
> "Vouchers provide a signed but non-encrypted communication channel
>    between the Pledge, the MASA, and the Registrar."
>
> Why is this  mentioned ? If there is a conclusion of this statement that
> is relevant to BRSKI it should be spelled out, otherwise its a detail
> belonging into voucher. I do not see how the following sentence is that
> relevant conclusion. But maybe i am too confused by the sentence structure.

I think that it explains why the voucher exists.

> Do you mean something like this:
>
> | Vouchers are signed but not encrypted. This allows registars to maintain
> | better control over pledges attached to the domains network by examining
> | and filtering Vouchers received from a MASA before sending them to the pledge.
>
> If thats the idea, i suggest to use language like i suggested because it's
> more explicit and simpler (not having to think what the relevance of
> "communication channel" is etc..).

QUESTION: I'm not sure that's the essence of the point.

> Also may warrant a note that this control does not necessarily apply to the
> case of a Cloud Registrar (see section 2.6).

The could registrar is not a BRSKI interaction.

Stopping here today.
here is a diff against -11  https://goo.gl/CpZHqd


--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJamddlAAoJEJVM4Vb9/EKQQ6IIAKBNQtaca37J4HZcKYEHuZLP
O+0fAoDboV8KB3zjMC9+DgKifqAteiSn98mzV5r9/TUoYX64A+OLQ3d90jtGfhPp
DnZaty/yVDR5nqkGFES8RnBZ8tsThU3ZGIx9q01j7ZEbM6ulFC3gUhdqB+sEntaP
KS7zHIVOH38hR1ZDbIwNlbtieIcUNzE8p00f6uOPzLO8z3zb5vQ1ClrmcQaVzHJV
HGXWcXCFoK489qviWq9ykawWPO9zxPOBWr90FVGbyj0xdcKBzuls/YyKCdmVT+Tj
wUzP81VKveVn7G/CGcM82scP5EJRj2J89tTGvXeqDMi9GMwjdFRCFX4h1lNdT7E=
=LbRl
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sat Mar  3 11:36:50 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: anima@ietf.org
Delivered-To: anima@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CC5D12008A; Sat,  3 Mar 2018 11:36:42 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: anima@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.73.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152010580233.8238.8222936105912539984@ietfa.amsl.com>
Date: Sat, 03 Mar 2018 11:36:42 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/X2tD3YFoQ5hv96DoPrXjISilW0g>
Subject: [Anima] I-D Action: draft-ietf-anima-grasp-api-01.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2018 19:36:42 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Autonomic Networking Integrated Model and Approach WG of the IETF.

        Title           : Generic Autonomic Signaling Protocol Application Program Interface (GRASP API)
        Authors         : Brian Carpenter
                          Bing Liu
                          Wendong Wang
                          Xiangyang Gong
	Filename        : draft-ietf-anima-grasp-api-01.txt
	Pages           : 26
	Date            : 2018-03-03

Abstract:
   This document is a conceptual outline of an application programming
   interface (API) for the Generic Autonomic Signaling Protocol (GRASP).
   Such an API is needed for Autonomic Service Agents (ASA) calling the
   GRASP protocol module to exchange autonomic network messages with
   other ASAs.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-anima-grasp-api/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-anima-grasp-api-01
https://datatracker.ietf.org/doc/html/draft-ietf-anima-grasp-api-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-anima-grasp-api-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sat Mar  3 11:43:55 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CB541201F2 for <anima@ietfa.amsl.com>; Sat,  3 Mar 2018 11:43:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 TRhHriNRPCk0 for <anima@ietfa.amsl.com>; Sat,  3 Mar 2018 11:43:51 -0800 (PST)
Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (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 8670312008A for <anima@ietf.org>; Sat,  3 Mar 2018 11:43:51 -0800 (PST)
Received: by mail-pf0-x22c.google.com with SMTP id y186so5481168pfb.2 for <anima@ietf.org>; Sat, 03 Mar 2018 11:43:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=tcld3YRbvGi6DYdHW4OAsWSv1AlSBSxu8aXbUafdLn8=; b=XnX3EKS5YqaC6Hp4OnzfUiIaCRUodVxapZAcnbypKkOOeVglDrMcKEA5kjtI6O55eC QdybFGz0qFlE/0OetSygp3VQ+A6A+Gg/Sq/2N3+1Ou+9bnrJ20fvnNR5wx7wi5rgEo0X ORVs2Jc9l7ylmya9KouWUa/fB4A+xi9qqsr4peTn0fGUqErvzKBVsTEAsMsSF62uFGFB hODUUdWyI5IkyQWp4r/owguvSAuJ6WBkhSs7ZYsdjF6r3PeFkVFZM2gLi/dAkQ42Z3TI Lp7XDJWSQ0VR/5RD45ZPPO6XoM1q4cTOPai/Bcip6oSVn4OJR6cAXx0Oo6ed3op+QD5P n5xQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=tcld3YRbvGi6DYdHW4OAsWSv1AlSBSxu8aXbUafdLn8=; b=beFOxRxeF4vGyd9C+Y8qQ4LnUbFCPVMY10OzA1qHBWGLpgNRBHpAUK/YPBgKgSrhq5 U0gubeyR9r8EstpyKazPUCzKTIgHYy7OKpvgGTN8BhkNHoNtF9hLKHZNPvwjByLlLGiU oH9It0OMrW01Hev0+1YerUF6N6XzT2/lgcckr+tb6y4XtGJ69b/VBKBPyXnYuPxVwSZr CJEFMHwn5UDecoSALkaVzh4whtDNU5O3pCBS2xatXZmR68BZhUipFWG2ANxYPlSXfKXi S1Ul/dH0ck6ZfVfhaCb0b+Hz8EvjVkzVVsb0/ECmh/JsxYxo7F2e6Kc99h6YRYL/x7MR USOg==
X-Gm-Message-State: APf1xPDPtRcsQzoR4aVEj7Vma/x8kfjaRvYHYybKWujAPJQj4I19Tfq6 Mk3VZdGcv0zrvHHCuK6RCFKUP4MPqOA=
X-Google-Smtp-Source: AG47ELvM8GNRyyoYdmHRI9is8hPFy53v0IMBizZo7Fmx3jC0c4z8mP3j15kehjd+VB7Zw8R8q+Gbiw==
X-Received: by 10.98.102.155 with SMTP id s27mr10080728pfj.198.1520106230826;  Sat, 03 Mar 2018 11:43:50 -0800 (PST)
Received: from [192.168.43.75] ([118.148.157.44]) by smtp.gmail.com with ESMTPSA id p72sm7025760pfa.74.2018.03.03.11.43.48 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 03 Mar 2018 11:43:50 -0800 (PST)
Sender: Brian Carpenter <becarpenter46@gmail.com>
To: anima@ietf.org
References: <152010580233.8238.8222936105912539984@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <566f157e-195e-42f2-4123-c46cc1d8abf8@gmail.com>
Date: Sun, 4 Mar 2018 08:40:47 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <152010580233.8238.8222936105912539984@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/fA-jyao6_0bhQKWdm8g9OFFxp-o>
Subject: Re: [Anima] I-D Action: draft-ietf-anima-grasp-api-01.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2018 19:43:53 -0000

Hi,

This is a minor update of the GRASP API, with editorial improvements.

We really need detailed reviews from two viewpoints:

-- the viewpoint of a C programmer
-- the viewpoint of an event-loop programmer

Regards
   Brian

On 04/03/2018 08:36, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Autonomic Networking Integrated Model and Approach WG of the IETF.
> 
>         Title           : Generic Autonomic Signaling Protocol Application Program Interface (GRASP API)
>         Authors         : Brian Carpenter
>                           Bing Liu
>                           Wendong Wang
>                           Xiangyang Gong
> 	Filename        : draft-ietf-anima-grasp-api-01.txt
> 	Pages           : 26
> 	Date            : 2018-03-03
> 
> Abstract:
>    This document is a conceptual outline of an application programming
>    interface (API) for the Generic Autonomic Signaling Protocol (GRASP).
>    Such an API is needed for Autonomic Service Agents (ASA) calling the
>    GRASP protocol module to exchange autonomic network messages with
>    other ASAs.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-anima-grasp-api/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-anima-grasp-api-01
> https://datatracker.ietf.org/doc/html/draft-ietf-anima-grasp-api-01
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-anima-grasp-api-01
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 


From nobody Sat Mar  3 11:47:47 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4FA01201F2 for <anima@ietfa.amsl.com>; Sat,  3 Mar 2018 11:47:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 0G9Pszec6WAz for <anima@ietfa.amsl.com>; Sat,  3 Mar 2018 11:47:44 -0800 (PST)
Received: from mail-pg0-x235.google.com (mail-pg0-x235.google.com [IPv6:2607:f8b0:400e:c05::235]) (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 0F82412008A for <anima@ietf.org>; Sat,  3 Mar 2018 11:47:44 -0800 (PST)
Received: by mail-pg0-x235.google.com with SMTP id m19so5192725pgn.1 for <anima@ietf.org>; Sat, 03 Mar 2018 11:47:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=TgT90tU5cQiT5jbQRxgAhnD9vgZtAK7DuZnhTjb8lLg=; b=eYO84Kw97WVNTU9zq5emNvxCzruoGlLAdbAy+GKolyxn4EcT/vCLE9F6cZIfQ8w64n Ktk7m3qfDA4NXhtkkp4/XQlfk9wFe+n3oRuRgg1WakNScvCjW8Mc0gup8qCOyFm2vjoP qfko5Zgjn2GZCBZcUfyjfmx/ACtBPCMokUdNMVAwr4INeWSjjlDC409j6eP6czHbyWog RsbCB8DdMrkl1BUWBJtvLVOz07em06K+s5d1bilspq35Ku1EbvTIvj7sZ+FKyozStpnl i0e3gTNuntDuuEfM2PxLe5iNvo2c+e5+2UXmjHt7Wn4Sv/c1u3Qg4Y8yQACDuCiNJ+/A Fkkg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=TgT90tU5cQiT5jbQRxgAhnD9vgZtAK7DuZnhTjb8lLg=; b=HPxoVDHFvSLMPL274a7fim8LjW1HA/6K3OuQr37E4XcuFifhoye3C/0CoBRUgC506b Ck0mvDj98VkmznVKYx5OQtY2FMV/GUjry+FUC05f3hGlc65LV3Gbwa2gZ0EUm6TqkCsc AQeA5tUxHycYJLgnJYLUbrOGDlAdkfudlsEJDTdqNeZ2ZZAIWwhnJD7kHEl/D1kfwzrh Z+nislmb4/trCjX83lmOMkxMldErs86KxCAd/fLncYb+vdVL0GATF4g/PsRC0GF6Qii2 xXCAOPKWdrQ5KeCWJGZpdZE8KhzTzp9HQ6IuvK0vGs1W1o6wlSd1gWMbASF4Rvun7YRp b1/Q==
X-Gm-Message-State: APf1xPDfyHAEaPomlQzWFDjEo22H66m8pbTZW3T1CL6feV3kQ1mr6th/ hTOjSeW7ZJRumQLShehPo6zFjSFZdzg=
X-Google-Smtp-Source: AG47ELt7ejb58QD7mfJf+2HVzQ5+dhIrbmGxWv4yWmxABuyv6AeBBP3BwjYnNEbXxIlddNmYWFmuzA==
X-Received: by 10.98.238.2 with SMTP id e2mr9978268pfi.68.1520106463409; Sat, 03 Mar 2018 11:47:43 -0800 (PST)
Received: from [192.168.43.75] ([118.148.157.44]) by smtp.gmail.com with ESMTPSA id e125sm14547273pgc.76.2018.03.03.11.47.41 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 03 Mar 2018 11:47:42 -0800 (PST)
Sender: Brian Carpenter <becarpenter46@gmail.com>
To: Anima WG <anima@ietf.org>
References: <152010581068.8290.15405496750913414945@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <acf8d424-ca3d-85e8-efa3-ca4ee235a5b1@gmail.com>
Date: Sun, 4 Mar 2018 08:47:37 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <152010581068.8290.15405496750913414945@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/7WnYW0BWEb-4piNDMgRhBnVnEQQ>
Subject: Re: [Anima] I-D Action: draft-carpenter-anima-asa-guidelines-04.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2018 19:47:46 -0000

Hi,

This version has several updates in response to comments at IETF100:

   Added note about simple ASAs.

   Added note about NFV/SFC services.
   (Is there a good reference for NFV?)

   Improved text about threading v event loop model

   Added section about coordination with traditional tools.

   Added appendix with example logic flow.

More review and input will be very welcome. Anybody who has written
code similar to an autonomic service agent, please have a look!

Regards
   Brian Carpenter



On 04/03/2018 08:36, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>         Title           : Guidelines for Autonomic Service Agents
>         Authors         : Brian Carpenter
>                           Laurent Ciavaglia
>                           Sheng Jiang
>                           Pierre Peloso
> 	Filename        : draft-carpenter-anima-asa-guidelines-04.txt
> 	Pages           : 21
> 	Date            : 2018-03-03
> 
> Abstract:
>    This document proposes guidelines for the design of Autonomic Service
>    Agents for autonomic networks.  It is based on the Autonomic Network
>    Infrastructure outlined in the ANIMA reference model, making use of
>    the Autonomic Control Plane and the Generic Autonomic Signaling
>    Protocol.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-carpenter-anima-asa-guidelines/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-carpenter-anima-asa-guidelines-04
> https://datatracker.ietf.org/doc/html/draft-carpenter-anima-asa-guidelines-04
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-carpenter-anima-asa-guidelines-04
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 


From nobody Sat Mar  3 11:52:13 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA8421201F2 for <anima@ietfa.amsl.com>; Sat,  3 Mar 2018 11:52:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 RWHHHxSo2Wlk for <anima@ietfa.amsl.com>; Sat,  3 Mar 2018 11:52:08 -0800 (PST)
Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (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 D76CB12008A for <anima@ietf.org>; Sat,  3 Mar 2018 11:52:08 -0800 (PST)
Received: by mail-pf0-x22d.google.com with SMTP id 68so5480404pfx.3 for <anima@ietf.org>; Sat, 03 Mar 2018 11:52:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=xdjOkMIUkRkSLjnLoeZdupUzOWgWw9KyKfdxO9c2OeA=; b=a0ozWVcDT9B0OxznWaqC9KHficzrmbNeRpopbmfZ+WnnHS2lXDEzbH30EadgspahRs 9AYBsNfMG0ykSQbqEzxs4RGRRN0Op/kplutI3SpMnU2hXydzcWzLVpMRkDJcRzAAGfno EsaV/K6Td4Ai11RZIvqSxJqisHeIGadvdphh20bKcMH9zBPPdPNOdHpfT+IAwarKMRs+ 4C5QXIb4PKApqORLXLtKOXG3gMYs4osR1EAUGilBfCK+W+MjcbOPi3NyI78gmMsSJGNy /96VA92/LgoXixYwr25ZJzNj6OxRsOsaqNYzXMtZj18tBZDz6eP0gttlFhof1UDwhXXw pkrw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=xdjOkMIUkRkSLjnLoeZdupUzOWgWw9KyKfdxO9c2OeA=; b=n/4Ccu7X2PAovH+gZFVmqUCj/oUPgQLT+kj+xxPP1tzXjquwa1hhA/Hqyfah6FEfah uX9N6WYACT2LiT/6DCK9SQRI5NpbvkaPtmfjkoUDQ7elR/GSaccEZlHhFKyeDZ0eEFl3 SMbAo+Mk/aJDP4bJdctqTc7hu+HLVfdRzpiMpUV98lxjHA8YRz7pdenHeEOgHPdYqF1d GM9/tSQdTfKWOEMK591QE6tPJPzv/AiZaZpB5q5d994i/QiqRKNZtRArX0rfxk8ITIBX +ok82+dvgObVpksO/sJPeNrSEjlKR+5avODY0PXKkWkoWh+NqKhOOII1jOrkvsVm8FWX DP4A==
X-Gm-Message-State: APf1xPBPMLnMcjfVMJVmsIHygxF3RFZ7jU6nyAVpCfFBRgE1nOA31GlJ UwVdd+j8Ez6XwaPooJKLZOigUkO2+Yk=
X-Google-Smtp-Source: AG47ELu14AnX+QWJ+imMWK1kFiYQqWw2jLX+t0KYYc1HXeLKxYa4r0yA10Agsdr+/oLKq2IVCr+xUg==
X-Received: by 10.99.165.71 with SMTP id r7mr8113462pgu.60.1520106728274; Sat, 03 Mar 2018 11:52:08 -0800 (PST)
Received: from [192.168.43.75] ([118.148.157.44]) by smtp.gmail.com with ESMTPSA id a67sm15167152pgc.6.2018.03.03.11.52.06 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 03 Mar 2018 11:52:07 -0800 (PST)
Sender: Brian Carpenter <becarpenter46@gmail.com>
To: Anima WG <anima@ietf.org>
References: <152010582437.8404.15379820327731954971@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <ea9b10d4-a39f-d2a3-3fb3-9560e0420517@gmail.com>
Date: Sun, 4 Mar 2018 08:52:01 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <152010582437.8404.15379820327731954971@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/nuCWvldURXKits_S-2eCQscsRcg>
Subject: Re: [Anima] I-D Action: draft-carpenter-anima-grasp-bulk-01.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2018 19:52:11 -0000

This has been updated according to comments received at 
IETF100 and on the list. Mainly clarifications around the
scope of applicability and failure handling. Please review
and comment.

Regards
   Brian

On 04/03/2018 08:37, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>         Title           : Transferring Bulk Data over the GeneRic Autonomic Signaling Protocol (GRASP)
>         Authors         : Brian Carpenter
>                           Sheng Jiang
>                           Bing Liu
> 	Filename        : draft-carpenter-anima-grasp-bulk-01.txt
> 	Pages           : 11
> 	Date            : 2018-03-03
> 
> Abstract:
>    This document describes how bulk data may be transferred between
>    Autonomic Service Agents via the GeneRic Autonomic Signaling Protocol
>    (GRASP).
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-carpenter-anima-grasp-bulk/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-carpenter-anima-grasp-bulk-01
> https://datatracker.ietf.org/doc/html/draft-carpenter-anima-grasp-bulk-01
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-carpenter-anima-grasp-bulk-01
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 


From nobody Sat Mar  3 21:38:22 2018
Return-Path: <mcr@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADC11124239; Sat,  3 Mar 2018 21:38:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 fPn1a_WEoT7w; Sat,  3 Mar 2018 21:38:17 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94E081200C1; Sat,  3 Mar 2018 21:38:17 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [IPv6:2607:f0b0:f:b:a11:96ff:fe01:81e0]) by relay.sandelman.ca (Postfix) with ESMTPS id 37EEE1F95D; Sun,  4 Mar 2018 05:38:15 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id D88382546; Sun,  4 Mar 2018 00:37:52 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Toerless Eckert <tte@cs.fau.de>
cc: draft-ietf-anima-bootstrapping-keyinfra@ietf.org, anima@ietf.org
In-reply-to: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de>
References: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de>
Comments: In-reply-to Toerless Eckert <tte@cs.fau.de> message dated "Wed, 14 Feb 2018 02:09:10 +0100."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sun, 04 Mar 2018 00:37:52 -0500
Message-ID: <19243.1520141872@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/2ee_M4R2hWHBoJvtb1fUDV4HPKU>
Subject: Re: [Anima] Shepherd review draft-ietf-anima-bootstrapping-keyinfra-09
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Mar 2018 05:38:21 -0000

--=-=-=
Content-Type: text/plain


I would ideally like to begin the WGLC once I've posted the revised document
and then take any of your issues that I wasn't able to resolve as last call
comments (open issues on tools or github).

Toerless Eckert <tte@cs.fau.de> wrote:
    > d)

    > I am missing in the initial chapters a succinct summary how EST
    > enrollment is optional and what can be achieved with/without it, there
    > is only some side sentences later in the EST sections. I would suggest
    > to insert such an explanation here.

    > After point 4 insert (unnumbered) paragraph:

I have added a paragraph at the end of section 4:

          After step 4, the pledge has received  and authenticated an
          explicit TA (trust anchor) (pinned-domain-cert in the Voucher
          response).  A secure transport exists between pledge and registrar,
          and it may be used for things other than enrollment into a PKI.

    > Also maybe insert some dotted line between imprint and enroll in Figure
    > 2 to highlight this distinction. Maybe with "mandatory" / "optional"
    > (EST enroll part) on the right hand side

But, in the ACP case, which we are documenting, it's not optional, so
I prefer to show the ACP case in all diagrams.

    > Section 2.3)

    > a)

    > The first paragraph is too terse and not very explanatory arguing why

okay, I'ave used your text.

    > - (Optional) authorizing pledge (by registrar) to receive certificate
    > from local CA.

Are you referring to the signed CSR?

That's signed by the private key, and does not directly involve the public
certificate part.  The "Signing of voucher-request" actually also is about
the private key too....
So I'm taking your comments, but maybe here we need to open an issue?

see: https://goo.gl/viMcAG
and: https://goo.gl/SNzWtJ

    > Please keep the "There is no requirement for a common root PKI
    > hierarchy.  Each device vendor can generate their own root
    > certificate."

Done.

    > -----------------------------------------------------------------------------
    > Section 2.3 2)

    > a) Please put the description of identification of the pledge into a
    > subsection 2.3.1 "Identification of the Pledge"

done.

    > b) I am confused about the first MUST (serialNumber) and following
    > SHOULD (HardwareModuleName).

    > The conversion rules make it clear that you want the device to be
    > uniquely identified via the serialNumber, but if that is not in the
    > certificate, then you would use the HardwareModuleName. Therefore the
    > conversion rules contradict the MUST for serialNumber.  Or else you
    > wouldn't define a fallback if it does not exist.

We really want it in the serialNumber.
We acknowledge the PKI tools suck, particularly the ones without source code,
and it's likely that some variety of creation tools will be unable to comply
or the Registrar / Certificate Authority will be unable to do the right thing.
The 30 year history of trying make PKIX thing work properly has provided
experience that says that as much as we want to write MUSTs, if we don't have
workaround documented, then things will fail.  It's sad.

    > c) The MUST/SHOULD bullet points are IMHO a duplication of the
    > conversion rules, so maybe just drop them.

I think an issue is warranteed here.

    > d) I would start the section with a sentence clearly describing what is
    > done here:

    > In the context of BRSKI, pledges are uniquely identified by a
    > "serial-number". This serial-number is used both in the "serial-number"
    > field of Voucher or Voucher requests (see section 3.) and in local
    > policies on Registrar or MASA (see section 5.).

    > The serial-number is derived from the IDevID as follows:

    > ... then add the three bullet-points.

okay, I think that I got this.

    > e) I do not see "serialNumber" attribute mentioned in rfc4514 nor
    > rfc4108. You mention "previously defined". Could you provide a
    > reference where "serialNumber" was defined ?

https://github.com/anima-wg/anima-bootstrap/issues/44

so, it's rfc4514 "string representation" format, of the RFC5280 SerialNumber
https://tools.ietf.org/html/rfc5280#section-4.1.2.2

RFC4108 has hwSerialNum, but that's point two.

I'm not sure how to clarify this well.

    > f) Please provide example of each of the three fields and how they
    > convert into serial-number. This is especially important because for
    > the average reader who has never seen a certificate (and with no actual
    > reference to e.g.: serialNumber format thats easily readable), it may
    > be hard to understand if or how something called "serialNumber" can
    > unique identify a device - aka: that it includes also the device-type
    > (unless a company only produces one type of device and somehow even the
    > name of the company can be implied).

I created issue 45.
https://github.com/anima-wg/anima-bootstrap/issues/45

    > -----------------------------------------------------------------------------
    > Section 2.3 2)

    > a) Please put the description of MASA URI into a subsection 2.3.2 "MASA
    > URI"

done.

    > b) If the following statements are correct, i would suggest to
    > integrate them into the section text to make it clearer and more
    > explicit. If not then i did not understand how it is meant to work and
    > the explanations could be approved accordingly to make it clearer:

    > - The type and format of the MASA URI indicates the protocol supported
    > by the MASA.
    > - If a MASA supports multiple protocols, multiple
    > instances of the new MASA URI can be put into the certificate.

I don't think so.
If there was a protocol that wasn't BRSKI-MASA, then it would have a new
extension defined.
QUESTION/DISCUSS.

    > - This
    > document defines the BRSKI-MASA protocol. It is indicated through a URI
    > of the form

    >    MASA URI is "https:// authority "./well-known/est".

    >   see section 5 for more explanations. (this would replace the current
    > sentence mentioning section 5).


    > c) We discussed the risk of introducing new certificate fields and
    > potential compatibility issues with existing code parsing such a
    > certificate. Which is why we went for the obfuscated email encoding of
    > the ACP information in the LDevID. It would therefore be good to have
    > an explaining sentence why the new MASA URI extension is a better
    > solution than encoding into existing attributes and safe to deploy into
    > devices.

Well, I'm not convinced we needed to do that in the ACP.
On the other hand, the open source IPsec (IKE) implementations I'm familiar with
have relatively simple DER implementations, and are easily extended.
I am aware of IPsec implementations which are total disasters in this way,
and they would no more be able to parse the obfuscated email than an extension.

    > I am not sure about the full extent of the answer, but probably IDevIDs
    > are meant to and actually used in a far smaller and newer set of
    > software than that processing arbitrary LDevIDs. Therefore the risk is
    > smaller and the clean encoding outweights the risk of compatibility
    > issues with badly written old software.

The manufacturer creates the certificates, the pledge never has to examine
it.  The registrar has to examine it, and the registrar has to be new code.
Where we get into trouble, I think, is with the PKI interfaces.

    > -----------------------------------------------------------------------------
    > Section 2.4.1) 1)

    >   "it does has network" -> "it does have network"

    > But better: "it does only require subnet (link) local connectivity to
    > the circuit proxy but no routeable IPv6/IPv6 address (exception: see
    > section 2.6)".

Already changed, but added your text.

    > -----------------------------------------------------------------------------
    > Section 2.4.2) 1)

    >   "The proxy mechanism" -> "The circuit proxy mechanism"

    >   " optional stateless mechanism" -> "optional stateless proxy
    > mechanism"

    >   add: The registrar (likely?) also needs manual configuration of
    > per-MASA credentials to contact them (see section 5.3).

okay.

    >   Q: Any case where unauthenticated BRSKI-MASA connections make sense ?

QUESTION: This seems like a non-sequitor to me.


    > -----------------------------------------------------------------------------

    > Section 2.4.3) 1)

It's 2.4.4, I think. About the Manufacturer Service.

    >   Suggest to clarify roles: separate functions: the MANDATORY ...MASA
    > including audit log, and an ADDITIONAL OPTIONAL Ownership Tracker
    > providing sales channel integration.

I don't think it's optional.

    >   Aka: reuse same terminology so readers are not confused. Maybe go
    > through text to check only "ownership tracker" and "sales channel
    > integration" are used for that part.

    > -----------------------------------------------------------------------------
    > Section 2.4.3) 1)

    > a) Expand CMC.  "authenticate any pledge" -> "authenticate (the IDevID
    > of) any pledge"

    > b) The document is still very vague on terminology to distinguish
    > between the initial bootstrap and the (optional) EST server
    > role. Please come up with a clear terminology and clearly summarize the
    > functionality required to be supported by the roles.

I think that this no longer reflectes the text?

That's today's edits are at the same rfcdiff URL, since the file is
loaded by reference:
        https://goo.gl/CpZHqd

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJam4YwAAoJEJVM4Vb9/EKQB2oIAKILa1kUvkvJM5dMjQwpyvGI
13tRxUlk3T78QdN55qgI/w+nvXdStT3W6LF4S7XEyIA7z+Vjw5e+xegvEGtE3x6I
yH84JvGnsCTc8BSKCRZV6XjtJcA6vn1BnpU6X6ubVWV2hmkt/C3yBbAmd6OgdBKW
6lVqqOHBlCOZF9E6rrE0zbdZSiOF23RYIkSsLi1r3e4pzXlX7M2K7y8U28UNjqRc
7WJ8c3zC+aScYZ7AT9KPBcTbGxj9Jeiz0EPcvUywJuficya0FOpiSBZk0JJ0aJwX
4THfw7MBhE3RSPMWKDb0/fC+OeLvx5MjqEcrUJ/QD7Xg8Y21bvsnpZP8U840f7s=
=cROH
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Mar  4 03:04:34 2018
Return-Path: <lear@cisco.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 566FC120713; Sun,  4 Mar 2018 03:04:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 5bIGgb3UkHAi; Sun,  4 Mar 2018 03:04:30 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5886120454; Sun,  4 Mar 2018 03:04:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5674; q=dns/txt; s=iport; t=1520161470; x=1521371070; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=s4/wADLVAzxfsGyrNFQO0dl4VbI4XJSi3oU5taB6x7g=; b=dRBSAP6gVSiZIQUULUpHKqwjf2vgml7cIShNFtX9xL2d1tkvlVoZfFNr 3/KH/9jzHvfAfVe0rZc9uVjToMmEG0dKLY2ScAzSeWXxPmyFyx3yP578Z Nz6IIExIy66eoxy4Sz0j9JiMxVzeGg/Da1O2wbJlnUbH/OBMn1zamdskb k=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0B8AQD20Zta/xbLJq1RChkBAQEBAQEBA?= =?us-ascii?q?QEBAQEHAQEBAQGENnAog1SLGI8FgRaUNBSCAQcDH4URAoMCNhYBAgEBAQEBAQJ?= =?us-ascii?q?rJ4UkAQQBI1YFCwtCAgJXBgEMCAEBhQ8IqEGCJ4Ryg2yCHA+FLYE0hDcpgXaBD?= =?us-ascii?q?oMuAgOBQxSDIoJiBIg3hn2LLgmEA4FvYookB4FnhDWCeIVkkVWBLiUKJyaBLDM?= =?us-ascii?q?aCBsVgn0JhEA/N4xdAQEB?=
X-IronPort-AV: E=Sophos; i="5.47,422,1515456000"; d="asc'?scan'208"; a="2416995"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Mar 2018 11:04:28 +0000
Received: from [10.61.242.48] ([10.61.242.48]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w24B4RC6031472; Sun, 4 Mar 2018 11:04:27 GMT
To: Michael Richardson <mcr+ietf@sandelman.ca>, Toerless Eckert <tte@cs.fau.de>
Cc: draft-ietf-anima-bootstrapping-keyinfra@ietf.org, anima@ietf.org
References: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de> <23390.1520031589@dooku.sandelman.ca>
From: Eliot Lear <lear@cisco.com>
Message-ID: <30a07059-ad23-7d65-fd82-c82570aa04cc@cisco.com>
Date: Sun, 4 Mar 2018 12:04:26 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <23390.1520031589@dooku.sandelman.ca>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="epDGx5sfv9dxFaPc1KFJbDdHkvK0gM80O"
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/s2mbb00r4amQ2c0tGrk47ul8zqw>
Subject: Re: [Anima] Shepherd review draft-ietf-anima-bootstrapping-keyinfra-09
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Mar 2018 11:04:32 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--epDGx5sfv9dxFaPc1KFJbDdHkvK0gM80O
Content-Type: multipart/mixed; boundary="CmqcnlDiPWHUFB52bFfpuPhEJUn5NLTm8";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>,
 Toerless Eckert <tte@cs.fau.de>
Cc: draft-ietf-anima-bootstrapping-keyinfra@ietf.org, anima@ietf.org
Message-ID: <30a07059-ad23-7d65-fd82-c82570aa04cc@cisco.com>
Subject: Re: [Anima] Shepherd review
 draft-ietf-anima-bootstrapping-keyinfra-09
References: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de>
 <23390.1520031589@dooku.sandelman.ca>
In-Reply-To: <23390.1520031589@dooku.sandelman.ca>

--CmqcnlDiPWHUFB52bFfpuPhEJUn5NLTm8
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US

Hi,

I'm not Max but I hope you won't mind me commenting in three places:


On 02.03.18 23:59, Michael Richardson wrote:

> Section 2.1
>> a) The term "Request Join" is only used here, and its IMHO not very lo=
gical
>> (disclaimer: toerless: en.wikipedia.org/wiki/ESL). It sounds to me lik=
e the
>> pledge says "i want to join". And also sounds as if the pledge could b=
e
>> disappointed if rejected. I would rather call it "Domain membership in=
quiry".
>> Or if you're hooked up on the term "joining", then maybe "Join Inquiry=
".
> QUESTION?  what do you think?
> Was "Request Voucher" one of the options you were thinking about?

I would very much prefer that we not use "Domain membership inquiry".=C2=A0=

If a change is necessary, I would prefer "Join Inquiry", to avoid
introducing ambiguities about domains.
>
>> Whatever best makes it clear that rejection is a perfect and important=

>> outcome option.
>>
>> b) Please see my issue section 5.1 a). If you agree with that statemen=
t, then there
>> should be no "rejected" arrow in Figure 2 coming out of the "Identify"=

>> block.
> okay, I'll deal with this in that section.
>
>> I would also suggest that the "Bad Vendor response" arrow does not com=
e out
>> of the "Imprint" block but out of the "Request Join" block. AFAIK, thi=
s is
>> an error reply to the Request Voucher, so it happens before imprinting=

>> (imprinting happens only when there is a vocker reply. AFAIK).
> [It says, "Bad MASA response" now, just for the reader who is following=
]
>
>> I don't think "Bad Vendor reply" in Figure 2 is a good term. Most logi=
cal
>> to me would
>> be "Error or not member". In any case, the text in section 2 below sho=
uld
>> mention the exact words used on the labels, the text is missing ll the=

>> labels on the left: "Factory reset", "Enroll Failure", "Bad Vendor
>> response",...
> more discussion.
>
>> c)
>>
>>  Point 1 nicely explains how this is done during TLS.
>>
>> Likewise, Point 2 should mention that this is the "Voucher Request", a=
nd
>> Point 3 should mention that it is the "Voucher Reply" - so readers can=
 match
>> up section 2.1 with the rest of the document.
>>
>> remove the "e.g." from "protocol, e.g. Enrollment over". Otherwise som=
e text
>> outlining when something else than EST is to be used. (see next commen=
t).
> QUESTION: I couldn't figure out what text this applies to.

I can't be sure.=C2=A0 I think Toerless may be referring to both the Diag=
ram
and the text in Section 2.1, as compared to, say, Figure 3 in Section
2.4.=C2=A0 I think the main change, IMHO is Figure 3, just to change
<---voucher--- to <---voucher reply--.

???

>
>> d)
>>
>> I am missing in the initial chapters a succinct summary how EST enroll=
ment is optional and
>>  what can be achieved with/without it, there is only some side sentenc=
es later in the
>> EST sections. I would suggest to insert such an explanation here.
>>
>> After point 4 insert (unnumbered) paragraph:
>>
>> | After step 4, the pledge has received  and authenticated an explicit=
 TA (trust anchor)
>> | (pinned-domain-cert in the Voucher response). In some use cases this=
 may be sufficient
>> | and the bootstrap can be terminated here. The pledge can now use thi=
s TA to securely
>> | trust domain members, but it can not securely identify itself to the=
m as a domain member.
>> | Therefore BRSKI usually proceeds with the following steps that suppo=
rt this via EST
>> | enrollment (see also 5.5.1 for the limitations of the trust feasible=
 through the imprint).
>>
>> Also maybe insert some dotted line between imprint and enroll in Figur=
e 2 to
>> highlight this distinction. Maybe with "mandatory" / "optional" (EST e=
nroll part)
>> on the right hand side
> QUESTION: Max?

If it is just a dotted line, ok.=C2=A0 But then use text at the beginning=
 of,
or just before, Step 5 to indicate that the step is optional.

Regards,

Eliot


--CmqcnlDiPWHUFB52bFfpuPhEJUn5NLTm8--

--epDGx5sfv9dxFaPc1KFJbDdHkvK0gM80O
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAlqb0roACgkQh7ZrRtnS
ejNm8wgApQFqNBJYj409CucfxpZHE5kmhqZRqxY1mUZj1iagBakaP5wgWDebwypA
JofcvYJyq3LosslGKAALqcWO5WMrQtpVqzqCdZ4/85fAaHpz20+uMWh5JQtoE8jZ
1Ax9F/A70TZ8K4fPNUOFPim9nM4nXUJ2AJ1sIIMKjEMgN4RSRW8IOQbOemz8k/gm
CXGUYee/gqBG16PUYumA+NDFFZexOwpn/nLF1Y38cpjoT0hjwolKaBIVMgFT981u
tgAY9BtYSpVTuIpD4XsZG/EFDrDkjn7DFe7PW+Ts+IpmvcirIc9+ovoNPAwpZUjj
aVeWENNSAzgQS8+5I33GbcpYwBZuLw==
=5T3Z
-----END PGP SIGNATURE-----

--epDGx5sfv9dxFaPc1KFJbDdHkvK0gM80O--


From nobody Sun Mar  4 10:55:57 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 275991242F7 for <anima@ietfa.amsl.com>; Sun,  4 Mar 2018 10:55:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 XqvAotTzTMXt for <anima@ietfa.amsl.com>; Sun,  4 Mar 2018 10:55:54 -0800 (PST)
Received: from mail-pg0-x22c.google.com (mail-pg0-x22c.google.com [IPv6:2607:f8b0:400e:c05::22c]) (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 172581205D3 for <anima@ietf.org>; Sun,  4 Mar 2018 10:55:54 -0800 (PST)
Received: by mail-pg0-x22c.google.com with SMTP id m19so5955574pgn.1 for <anima@ietf.org>; Sun, 04 Mar 2018 10:55:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=De4926sg84HQJKIVIruuzmVlSqmK7vDQOl/JkIGctrg=; b=qlEgj680vA5MMeESPrExy9VdtreJx4dzPLJvyJ252TETpSt1DBKVSZ4/Qibhg08gBO mbywlSD8XMLYPiR3NInZFJ5PPoeygjG2ovTwkAGOaFNpzriBZVdXVGLvsdskTripOxB0 ShEo4rKSvgwOn/GgC7CbJtkVvE5fd1Bkx4QQLBMDECWAoN90blul+mYxakp1MmEDsr7M QTGx+PkNNpVxIi7wL7LP8+anF4eQznhgm4xzQ3wnCCyjjL4tHWQ8whQWVUS6WsEt4rDB ikiX1enL1hlJC/CwNIBLfx++v1VhltOoq9Z+lYE8rw/8O/+K3qV9xB0UP7jd4KUAnfP/ GE6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=De4926sg84HQJKIVIruuzmVlSqmK7vDQOl/JkIGctrg=; b=CfrYgoAxwiW9XiXn6Z7a1QKtRz+TczLC9UnkSd6VdMAopYTAJXpsxv0ewe1qAXEKuK OK0ByQM5TN/RVHe9T6NADRb+EJ0kVE+bV8URtbyFxtf/yp4GkaZOeIZpkRkK+i0+y8by 4Oheh1aWV0qXJa0vZ3sMpHba8coDjhrnU9037260/83yjaRokhuD5gY0uzEEdydQJjj7 ACBbSjuja63hzBRpUL2mslWAGN3zekvU3cW7Gmf5MJtv3sxBRZWMUXUcNH+Eax4iP/DT Sl8NnIaItZ3l2jK8Wrv3oZGj1qhhIXL/sA8uH0VigZcAZwwnA79+SfzG9CJX8rVkNkUc /g8g==
X-Gm-Message-State: APf1xPDaGoI5VcDRIAXwKiE+H3q/WQtY/u4UmTkrD0aK55Vtux7fDGYq 1+hKS07gclUAEC8Qwr2DNOsoxgL1mnI=
X-Google-Smtp-Source: AG47ELuB//7vNztj149jtnOhpMmGb+OC7cJBswzh106W3cWncAaXRwBqfPDnHCGYJ9Rw2qEKwq1t0w==
X-Received: by 10.98.172.18 with SMTP id v18mr12792505pfe.175.1520189753307; Sun, 04 Mar 2018 10:55:53 -0800 (PST)
Received: from [192.168.43.75] ([118.148.164.145]) by smtp.gmail.com with ESMTPSA id x4sm16413795pfb.46.2018.03.04.10.55.51 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 04 Mar 2018 10:55:52 -0800 (PST)
Sender: Brian Carpenter <becarpenter46@gmail.com>
To: anima@ietf.org
References: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de> <23390.1520031589@dooku.sandelman.ca> <30a07059-ad23-7d65-fd82-c82570aa04cc@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <9143a50e-6a3e-abb2-be5f-c244f4db4d5a@gmail.com>
Date: Mon, 5 Mar 2018 07:55:48 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <30a07059-ad23-7d65-fd82-c82570aa04cc@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/0-0FTN3zsUc-jGqb_Ejej2fa30g>
Subject: Re: [Anima] Shepherd review draft-ietf-anima-bootstrapping-keyinfra-09
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Mar 2018 18:55:56 -0000

On 05/03/2018 00:04, Eliot Lear wrote:
> Hi,
>=20
> I'm not Max but I hope you won't mind me commenting in three places:
>=20
>=20
> On 02.03.18 23:59, Michael Richardson wrote:
>=20
>> Section 2.1
>>> a) The term "Request Join" is only used here, and its IMHO not very l=
ogical
>>> (disclaimer: toerless: en.wikipedia.org/wiki/ESL). It sounds to me li=
ke the
>>> pledge says "i want to join". And also sounds as if the pledge could =
be
>>> disappointed if rejected. I would rather call it "Domain membership i=
nquiry".
>>> Or if you're hooked up on the term "joining", then maybe "Join Inquir=
y".
>> QUESTION?  what do you think?
>> Was "Request Voucher" one of the options you were thinking about?
>=20
> I would very much prefer that we not use "Domain membership inquiry".=C2=
=A0
> If a change is necessary, I would prefer "Join Inquiry", to avoid
> introducing ambiguities about domains.

Yes. We have explicitly left the (tricky) issue of AN domain boundaries
and membership for later. (Recharter alert!)

   Brian

>>
>>> Whatever best makes it clear that rejection is a perfect and importan=
t
>>> outcome option.
>>>
>>> b) Please see my issue section 5.1 a). If you agree with that stateme=
nt, then there
>>> should be no "rejected" arrow in Figure 2 coming out of the "Identify=
"
>>> block.
>> okay, I'll deal with this in that section.
>>
>>> I would also suggest that the "Bad Vendor response" arrow does not co=
me out
>>> of the "Imprint" block but out of the "Request Join" block. AFAIK, th=
is is
>>> an error reply to the Request Voucher, so it happens before imprintin=
g
>>> (imprinting happens only when there is a vocker reply. AFAIK).
>> [It says, "Bad MASA response" now, just for the reader who is followin=
g]
>>
>>> I don't think "Bad Vendor reply" in Figure 2 is a good term. Most log=
ical
>>> to me would
>>> be "Error or not member". In any case, the text in section 2 below sh=
ould
>>> mention the exact words used on the labels, the text is missing ll th=
e
>>> labels on the left: "Factory reset", "Enroll Failure", "Bad Vendor
>>> response",...
>> more discussion.
>>
>>> c)
>>>
>>>  Point 1 nicely explains how this is done during TLS.
>>>
>>> Likewise, Point 2 should mention that this is the "Voucher Request", =
and
>>> Point 3 should mention that it is the "Voucher Reply" - so readers ca=
n match
>>> up section 2.1 with the rest of the document.
>>>
>>> remove the "e.g." from "protocol, e.g. Enrollment over". Otherwise so=
me text
>>> outlining when something else than EST is to be used. (see next comme=
nt).
>> QUESTION: I couldn't figure out what text this applies to.
>=20
> I can't be sure.=C2=A0 I think Toerless may be referring to both the Di=
agram
> and the text in Section 2.1, as compared to, say, Figure 3 in Section
> 2.4.=C2=A0 I think the main change, IMHO is Figure 3, just to change
> <---voucher--- to <---voucher reply--.
>=20
> ???
>=20
>>
>>> d)
>>>
>>> I am missing in the initial chapters a succinct summary how EST enrol=
lment is optional and
>>>  what can be achieved with/without it, there is only some side senten=
ces later in the
>>> EST sections. I would suggest to insert such an explanation here.
>>>
>>> After point 4 insert (unnumbered) paragraph:
>>>
>>> | After step 4, the pledge has received  and authenticated an explici=
t TA (trust anchor)
>>> | (pinned-domain-cert in the Voucher response). In some use cases thi=
s may be sufficient
>>> | and the bootstrap can be terminated here. The pledge can now use th=
is TA to securely
>>> | trust domain members, but it can not securely identify itself to th=
em as a domain member.
>>> | Therefore BRSKI usually proceeds with the following steps that supp=
ort this via EST
>>> | enrollment (see also 5.5.1 for the limitations of the trust feasibl=
e through the imprint).
>>>
>>> Also maybe insert some dotted line between imprint and enroll in Figu=
re 2 to
>>> highlight this distinction. Maybe with "mandatory" / "optional" (EST =
enroll part)
>>> on the right hand side
>> QUESTION: Max?
>=20
> If it is just a dotted line, ok.=C2=A0 But then use text at the beginni=
ng of,
> or just before, Step 5 to indicate that the step is optional.
>=20
> Regards,
>=20
> Eliot
>=20
>=20
>=20
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima
>=20


From nobody Mon Mar  5 12:22:01 2018
Return-Path: <mcr@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 436F6127419; Mon,  5 Mar 2018 12:22:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.435
X-Spam-Level: *
X-Spam-Status: No, score=1.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_SBL_CSS=3.335, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 UMX0fseQ3rYp; Mon,  5 Mar 2018 12:21:57 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2D58126CBF; Mon,  5 Mar 2018 12:21:57 -0800 (PST)
Received: from dooku.sandelman.ca (CPE788df7e17ec1-CM788df7e17ec0.cpe.net.cable.rogers.com [99.249.63.150]) by relay.sandelman.ca (Postfix) with ESMTPS id 18D5D1F95D; Mon,  5 Mar 2018 20:21:56 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 581F73386; Mon,  5 Mar 2018 15:21:32 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Toerless Eckert <tte@cs.fau.de>
cc: draft-ietf-anima-bootstrapping-keyinfra@ietf.org, anima@ietf.org
In-reply-to: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de>
References: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de>
Comments: In-reply-to Toerless Eckert <tte@cs.fau.de> message dated "Wed, 14 Feb 2018 02:09:10 +0100."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Mon, 05 Mar 2018 15:21:32 -0500
Message-ID: <1051.1520281292@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/3-nS_OHw5mSicC_D3L9vEf0EaiI>
Subject: Re: [Anima] Shepherd review draft-ietf-anima-bootstrapping-keyinfra-09
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2018 20:22:00 -0000

--=-=-=
Content-Type: text/plain


Sunday I was skiing (it didn't rain!) and this morning I was distracted by
another urgent matter, so I'll get another two hours to work on this now, and
then I'll post a new version of the draft before the deadline.

It is unlikely that I'll get through all your suggested edits, and I still
need to come back to William Atwood's comments and some followups to my
previous comments.  Sorry for so many emails: next time be more negligent :-)

Toerless Eckert <tte@cs.fau.de> wrote:
    > Section 2.4.3) 1)

    > a) Expand CMC.  "authenticate any pledge" -> "authenticate (the IDevID
    > of) any pledge"

expanded and linked to RFC5272.

    > b) The document is still very vague on terminology to distinguish
    > between the initial bootstrap and the (optional) EST server
    > role. Please come up with a clear terminology and clearly summarize the
    > functionality required to be supported by the roles.

What is the "(optional) EST server role"?
Nothing is optional in this document when operating for the ACP.
The EST server role is an EST server according 7030.

    > Here is my suggested text. If any explanation to cover this information
    > is felt to be too long for 2.4.3, please find another place but make
    > 2.4.3 refer to that place.

    > | A "Domain Join Registar and CMC" (abbreviated Domain Registrar in
    > most of the document) | serves two roles: BRSKI Bootstrap Service and
    > BRSKI enhanced EST Enrollment Service.

I don't think that there are two roles.

There is no requirement that the Join Registrar is also the EST for the
purposes of ongoing certificate renewal.  I don't know if you are speaking
about certificate lifetime management (renewal, etc.) when you say
"EST Enrollment service".  I'll assume that you mean that for the moment.

In a big network I would want the roles (bootstrap and initial certificate,
vs certificate renewal) split up.

So I don't think your text is correct; but if it is, then I don't want to
insert a bunch of text that is depth first into explaining everything when
the goal of section 2 is to go breadth first.
I opened an issue: https://github.com/anima-wg/anima-bootstrap/issues/46

    > | While not recommended, BRSKI Bootstrap Server and BRSKI enhanced
    > EST-Server can |be provided by separate servers. In this case, the
    > BRSKI Bootstrap Server must | support redirection of the Pledge after a
    > successfull requestauditlog to the | URI of a BRSKI enhanced
    > EST-Server.

no, that's not what I'm saying at all.
I would never want to redirect or reconnect after processing the voucher and
before issuing the first certificate to the pledge.  The entire "Secure
Transport" depends upon it occuring over a single TLS connection.

    > Section 2.4.4)

    > a) It would be IMHO good to move the (mayority of the) initial
    > paragraph of 5.4 into this section to explain what the scope of the
    > MASA functionality is by listing the interface services requestvoucher
    > and requestauditlog here - similar to how i proposed to summarize the
    > interfaces of the Domain Registrar above for section 2.4.3.

I have changed the text to say:

2.4.4.  Architectural component: Manufacturer Service

   The Manufacturer Service provides two logically seperate functions:
   the Manufacturer Authorized Signing Authority (MASA) described in
   Section 5.4 and Section 5.5, and an ownership tracking/auditing
   function described in Section 5.6 and Section 5.7.

    > 5.4 is not a good place to do that because it's only about
    > requestvoucher, and then after another non-maza intermezzo 5.6
    > requestauditlog is again about the MASA. So no single place summarizing
    > the MASA functionality at this level.

Section 5 is a time sequence explanation about the process.
We want from role based descriptions to time based descriptions based upon
feedback from implementers.
Section 5.6 is about pledge->JRC.

QUESTION: Max, I thought that the Voucher Status Telemetry was also to be
          relayed to the MASA?
          (I didn't implement that far yet)

    > -----------------------------------------------------------------------------

    > Section 2.4.x)

    > a) Please add subsection "Architectural Component: Key Infrastructure
    > (PKI)"

    > Suggested text (as in: this is the type of information i would like to
    > see explained here, whatever language you use):

    > | The Key Infrastructure (PKI) administers certificates for the domain
    > of concerns, | providing the trust anchor(s) for it and allowing
    > enrollment of Pledges | with domain certificates.

    > | The Domain Registrar ('s BRSKI Bootstrap service role) uses a Trust
    > Anchor (TE) | from the PKI in the BRSKI Voucher pinned-domain-cert to
    > authenticate itself to the | Pledge with the help of MASA.

I have put this text in place, but this paragraph is not quite correct.
I don't know how to fix it yet.

My text:

+2.4.5.  Architectural component: Public Key Infrastructure (PKI)
+
+   The Key Infrastructure (PKI) administers certificates for the domain
+   of concerns, providing the trust anchor(s) for it and allowing
+   enrollment of Pledges with domain certificates.
+
+   The Domain Registrar uses a Trust Anchor (TE) from the PKI in the
+   BRSKI Voucher pinned-domain-cert to authenticate itself to the Pledge
+   with the help of MASA.  (XXX fix me)
+
+   The Domain Registrar acts as an [RFC5272] Registration Authority,
+   requesting certificates for Pledges from the Key Infrastructure.
+
+   The above requirements and expectations against the Key
+   Infrastructure are unchanged from RFC7030.  This document does not
+   place any additional architectural requirements on the Public Key
+   Infrastructure.

    > b) Figure 1 labels the path to the PKI with "EST" and i remember Max to
    > repeatedly state that CAs could support EST. Nevertheless, i read in
    > RFC7030:

    > "The nature of communication between an EST server and a CA is not
    > described in this document".

So perhaps the labelling of the Domain Registrar/PKI interface shouldn't
say EST RFC 7030 afterall.

    > But then it defines the term "EST CA". So i am confused if there is an
    > actual spec stating the EST profile? of an EST CA.

You are asking for us to define what the northbound connection (well, in our
diagram, it's a southbound connection...) from the JRC to the PKI is.  What
we are trying to say is that it's not in scope, because it has no effect on
interoperation with the pledge or MASA.

The options include:
    1) CMC (RFC5272)
    2) CMP
    3) system("openssl xyz")  [it's all internal]
    4) a variety of RESTful interfaces,
        for instance https://www.digicert.com/rest-api/

I really don't think we should specify anything here because it will just be
ignored with vendors of JRCs doing whatever they need to do to get into the
customer.   On day one I expect to see (3) used a lot and others to follow.


    > -----------------------------------------------------------------------------

    > Section 2.5) 1)

    > a) If the following sentence is functionally correct, please add text
    > accordingly:

    >   Bootstrapping Pledges that have a Realtime Clock (RTC), SHOULD use it
    > to verify certificate validity.

    > b) And from my own experience, it should add:

    >   but they MUST be prepared to recognize local time failure and revert
    > to the above described mechanisms. For example when RTC battery failure
    > leads to a well-known default-time (e.g.: Jan 1 1970).

Done.


    > Section 2.5) 2)

    > a) Please move the bullet about the registrar behavior out of the
    > bullet list, maybe at the end of the section.  Even better: - rename
    > 2.5 to "Certificate Validity" - 2.5.1 "Lack of Realtime Clock in
    > Pledges - 2.5.2 "Infinite Lifetime of IDevID" (move text into 2.5.1)

okay.

    > b) Its hard to comprehend what the pargraph means to say. I think its
    > something like:

    >    According to RFC5280, IDevIDs are examples of certificates that
    > should have no well-defined expiration date. This is indicated through
    > the GeneralizedTime value of 99991231235959Z". Registrars SHOULD have a
    > configuration option to ignore IDevID lifetime values if they do not
    > conform to this recommendation.

Done.

    >    As expected, i always like an explicit example to bring it to the
    > point:

    >    For example, IDevID may have incorrect lifetime of N <= 3 years,
    > rendering replacement Pledges from storage useless after N years unless
    > registrars support this option.

Done.

    > -----------------------------------------------------------------------------
    > Section 2.6)

    > IMHO, without further text, it is unclear a) what a cloud registrar is,
    > b) why we care and c) how a solution using a cloud registrar would have
    > to be built to work.

I think that we explain why (b) well enough.
I prefer not to try to specify anything here for two reasons:

1) it's proprietary: No BRSKI is involved.
2) it's out of scope: No BRSKI is involved.
3) it's possible that it will be draft-ietf-netconf-zerotouch-20

So, I don't think your assumptions are right about who runs what.

{In my thinking about this, btw, the pledge calls home a la
netconf-zerotouch, and the vendor provided service acts as a Join Proxy to
the owners' JRC.  But, I'd want to write code and think about before
I dared document it.  Running code...}

    > If you feel this is overall too much, then maybe delete the whole
    > section 2.6 and put it into a followup document. Borderline to me. If
    > its "just" what i sugested above, its fine, if there is more to it to
    > make it work, maybe better in separate document.

No, we added this section because someone (maybe you) asked for it.

    > -----------------------------------------------------------------------------
    > Section 2.7 1)

    > a)

    >> Note that the Registrar can only select the configured MASA URL based
    >> on the trust anchor -- so vendors can only leverage this approach if
    >> they ensure a single MASA URL works for all Pledge's associated with
    >> each trust anchor.

    > I do not think this is true. A registrar could have configuration
    > policy mapping from IDevID serial-number patterns to MASA URI.

Yes, it could be more complex.
I'd rather delete that sentence than fix it.

    > Rewrite accordingly ? Let me know if you hate this approach, i had had
    > to brainstorm it for my planned yang model for ANI.

Only if this functionality is standardized :-)

    > b) I also think it might be necessary for Registrars to allow policies
    > that override MASA URIs learned from the IDevID because the longevity
    > of URIs can not always be guaranteed and the MASA may move (merger &
    > aquisitions etc.. ).

Agreed.

    > c) I am unclear from the document whether registrars may require
    > configuration to know what specific options for voucher-requests a MASA
    > supports.

> - If i understand it correctly, a registrar may use a voucher-request to
> request a voucher in the absence of the pledge (stage the voucher). This
> certainly is something not every MASA must support, so that would need to
> be configured.

The MASA must support nonce-less, unsigned voucher-requests.
You are right that we did not say that the MASA MUST do this.
I'm comfortable leaving that to some other applicability document.
  {e.g, "Use of BRSKI to bootstrap lightbulbs for underground military bunkers",
      MIL-SPEC 843.1958, by Strangelove, Sellers and George}

> - It is not clear to me if the Registrar can correctly fill out all
> Registrar voucher-requests in the presence of the pledge (aka: after
> receiving the Pledge voucher-request). See also discussion for Section
> 3. If this is not fully automatic, but may rquire Registrar configuration,
> this counfig should be mentionedhere.

Do you mean, in the absence of the pledge, or ...?

    > -----------------------------------------------------------------------------
    > Setion 3. 1)

    > So... I guess Registrars can request Vouchers for pledges before being
    > in contact with that pledge, right ?

    > If correct, the following would be less confusing to read for me:

Here is my revised text:

+   Voucher-requests are how vouchers are requested.  The semantics of
+   the vouchers are described below, in the YANG model.
+
+   A Pledge forms the "Pledge voucher-request" and submits it to the
+   Registrar.
+
+   The Registrar in turn forms the "Registrar voucher-request", and
+   submits it to the MASA server.
+
+   The "proximity-registrar-cert" leaf is used in the Pledge voucher-
+   requests.
+
+   The "prior-signed-voucher-request" leaf is be used in Registrar
+   voucher-requests to the Pledge voucher-request.  It contains the
+   encoded (signed form) of the Pledge voucher-request.
+
+   A Registar MAY also retrieve (nonceless) vouchers by sending voucher-
+   requests to the MASA.  No "prior-signed-voucher-request" leaf would
+   be included.  This can be used to retrieve vouchers for later offline
+   use.  The Registrar will need to know the serial number of the
+   pledge.  This document does not provide a mechanism for the Registrar
+   to learn that in an automated fashion.  Typically this will be done
+   via scanning of bar-code or QR-code on packaging, or via some sales
+   channel integration.


    > In any case, you need at least a forward reference for those leaf types
    > if you want to mention them without other explanations.

It's hard to reference into the YANG model text.

    > -----------------------------------------------------------------------------
    > Setion 3. 1)


    > a) Even with above concern Section 3. 1) fixed the section still does
    > not provide a good taxonomy of the different type of voucher-requests
    > and how to fully identify them because of the "may be used"...

I removed "may" to say "is".

    > b) There is no text here explaning how a registrar transforms a Pledge
    > Voucher request to a Registrar voucher request. If explained later,
    > insert a forward reference. Else. pls add text to explain.

I added some text above.

    > b) I have my doubts that the flow of the document is ideal with all the
    > yang formalisms thrown into section 3. If this is what other documents
    > do as well, fine. I for once would like it better if it was put into a
    > separate section towards the end of the document.

    > "nah, not going to happen" is an acceptable answer ;-)

"not going to happen"

    > -----------------------------------------------------------------------------
    > Setion 3.2 1)

    >  "provides voucher examples" -> "provides voucher-request examples"

okay.

Again, changes to here updated to: https://goo.gl/CpZHqd



--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJanabMAAoJEJVM4Vb9/EKQYGMIAIMLSjgyt4zR9+2piAehDYuk
kPGfQhVKLPa7T21eqIFuKYNheFJDeJ2VNhsjlci2vFoaANJnA0dALs6c23mGa4Hc
NwxiSRpQhwn+GbQVGP5SyNW5igXBvZa1qHRouCBXzeaVa2Vv65ALfP30oYEh6fsM
t61FnZE7JGaxWJGs4m6QKTYmtWDR8Ue7OmdZIU3FHcTgksyXwH1Lec4HfrO4rVpc
xEzraOXOg2Zy9d1qdn71n3K/lbojaAFTbU05A9cnN2a/rQN5rbn7pW06hgOL3lKr
yFTLCyHXhVqdsnQwFWCJjInduQdE6TvF+8beofxUEAIxVVAcM65jgAqgniyahmU=
=o1kS
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Mar  5 14:44:29 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: anima@ietf.org
Delivered-To: anima@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CFE3D12008A; Mon,  5 Mar 2018 14:44:23 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: anima@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.74.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152028986381.12884.9092671195107327813@ietfa.amsl.com>
Date: Mon, 05 Mar 2018 14:44:23 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/koh9dIiMad4IwUAY9gmgRgF_wt0>
Subject: [Anima] I-D Action: draft-ietf-anima-bootstrapping-keyinfra-12.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2018 22:44:24 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Autonomic Networking Integrated Model and Approach WG of the IETF.

        Title           : Bootstrapping Remote Secure Key Infrastructures (BRSKI)
        Authors         : Max Pritikin
                          Michael C. Richardson
                          Michael H. Behringer
                          Steinthor Bjarnason
                          Kent Watsen
	Filename        : draft-ietf-anima-bootstrapping-keyinfra-12.txt
	Pages           : 87
	Date            : 2018-03-05

Abstract:
   This document specifies automated bootstrapping of a remote secure
   key infrastructure (BRSKI) using manufacturer installed X.509
   certificate, in combination with a manufacturer's authorizing
   service, both online and offline.  Bootstrapping a new device can
   occur using a routable address and a cloud service, or using only
   link-local connectivity, or on limited/disconnected networks.
   Support for lower security models, including devices with minimal
   identity, is described for legacy reasons but not encouraged.
   Bootstrapping is complete when the cryptographic identity of the new
   key infrastructure is successfully deployed to the device but the
   established secure connection can be used to deploy a locally issued
   certificate to the device as well.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-anima-bootstrapping-keyinfra/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-anima-bootstrapping-keyinfra-12
https://datatracker.ietf.org/doc/html/draft-ietf-anima-bootstrapping-keyinfra-12

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-anima-bootstrapping-keyinfra-12


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Mar  5 14:45:57 2018
Return-Path: <mcr@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E628112EAEE; Mon,  5 Mar 2018 14:45:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Z5NxHgeCyeO0; Mon,  5 Mar 2018 14:45:38 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2017129BBF; Mon,  5 Mar 2018 14:45:11 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [209.87.249.16]) by relay.sandelman.ca (Postfix) with ESMTPS id 700B71F95D; Mon,  5 Mar 2018 22:45:10 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id B96583386; Mon,  5 Mar 2018 17:44:45 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Toerless Eckert <tte@cs.fau.de>
cc: draft-ietf-anima-bootstrapping-keyinfra@ietf.org, anima@ietf.org
In-reply-to: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de>
References: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de>
Comments: In-reply-to Toerless Eckert <tte@cs.fau.de> message dated "Wed, 14 Feb 2018 02:09:10 +0100."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Mon, 05 Mar 2018 17:44:45 -0500
Message-ID: <10097.1520289885@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/jdFeQ-5E53_jezhkgATySboY0y8>
Subject: Re: [Anima] Shepherd review draft-ietf-anima-bootstrapping-keyinfra-09
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2018 22:45:52 -0000

--=-=-=
Content-Type: text/plain


    > -----------------------------------------------------------------------------
    > Section 4. 1)

    > a.1) Suggest to change title to "Proxying Details (Plege - Proxy -
    > Registrar)" because the section does not only discuss the proxy but
    > also the aspects/reqirements of proxying relevant to Client and
    > Registrar.



    > a.2) paragraph 1: "configured on the Proxy" append: "or automatically
    > discoverded (e.g.: via GRASP, see below)

In fact, we never want it configured in an autonomic network, it should
always be discovered.

    > b) Add: This section defines a statefu proxy which is therefore called
    > a "circuit" proxy.

okay.

    > c) Simplify whole paragraph with "(In a completely autonomic
    > network...)" - this discussion is not specific to AN. E.g.:

    > Registrars are assumed to have logically a locally integrated Proxy to
    > support directly (subnet) connected Pledges - because Registrars
    > themself does not define any functions for Pledges to discover
    > them. Such a logical local proxy does not need to provide actual TCP
    > proxying (just discovery) as long as the Registrar can operate with
    > subnet (link) local addresses on the interfaces where Pledges may
    > connect to.

done

    > d) "to discovery the" -> "to discover the"

already fixed I think.

    > e) Paragraph starting with: "If the Proxy joins an Autonomic Control
    > Plane" Suggest following replacement:

    >    In the ANI, the Autonomic Control Plane (ACP) secured instance of
    > GRASP (<ref>) MUST be used for discovery of ANI Registrar ACP addresses
    > and ports by ANI Proxies.  The TCP leg of the proxy connection between
    > ANI Proxy and ANI Registrar therefore also runs across the ACP.

    >    (separate because it would apply for any GRASP learning, not only
    > ACP):

    >    If GRASP is used by proxies for discovery of Registrars (ACP or
    > not), the proxy can also learn the proxy mechanism (Circuit Proxy
    > vs. IPIP encapsulation or other)

    >    (there is no negotiation in GRASP, therefore "agreed" as in current
    > text is not a good choice of word).

okay.

    > f) "SHOULD be the same as on the registrar in order for the proxy to
    > remain stateless".  Does such a proxy makes sense when it is not
    > stateless ? Aka: should this not be a MUST instead of a SHOULD ?

I can imagine ways to not use the same port, while still avoiding
O(number-of-pledges) storage of state.  But it involves messing with
packet headers in a way that I find distasteful.  That's why I write SHOULD.


    > -----------------------------------------------------------------------------
    > Section 4. 2)

    > "In order to permit the proxy functionality to be implemented on the
    > maximum variety of devices...  with available capabilities for the
    > proxy function similar to many class 2 IoT devices"

    > This IMHO is an incorrect assumption. I am not aware of any network
    > device in ANIMAs "well managed network" charter" that would today fall
    > into class 2. I was and am often extremely annoyed how underpowered
    > control plane of multi-terrabit switches are but those too don't get
    > down to that level. Even OpenWRT small home rotuers (outside scope of
    > ANIMA) don't go below 4 MByte these days.

Yes, but I'm not talking about using the whole control plane CPU:
     -> "available capabilities for the proxy function"

we gotta fit into whatever is left over, or product management will kick our
code out next time there is a code space crunch.

As far as I can tell, due to SDN outsourcing the control protocols
(like BGP and OSPF and even), and the rest being in forwarding-element
hardware, one COULD probably get away with an OpenWRT scale CPU as the
control plane CPU for a L2/L3-aware switch with hundreds and hundreds of
ports...

    > Here are statements i could support/recommend:

    > - Registrars must support the proxy method supportable by the type of
    > proxies it needs to support. If pledges could be IoT class 2, then IPIP
    > would be a better solution for them than a CP circuit proxy. Note that
    > in ANI adopted to class 2 IoT or similar "mesh network" solutions,
    > Plege become proxies proxy and therefore IoT class 2 pledges imply also
    > the need to support IoT class 2 proxies.

So, it matters not what the pledge is.
The Pledge in this document is always doing HTTPS over TCP over Link-Local
IPv6, and never needs to know what the relay protocol is.

So, I don't agree with your paragraph here.

    > -----------------------------------------------------------------------------
    > Section 4.1 1)

    > a) "[RFC4941] temporary addresses is encouraged...."  Please remove or
    > add text explaining why. Given how a pledge is happy to spill it's
    > IDevID to everyone claiming to be a proxy i am not sure what benefit
    > privacy addresses have, and they are additional implementation work for
    > pledges, whereas link-local (permanent) addresses are always
    > required. And changing addresses makes diagnostics harder.

    >    I also am not even sure if RFC4941 is even creating additional
    > link-local (temporary) addresses. I don't even think so. And all the
    > concerns RFC4941 discusses about correlating traffic is hardly
    > applicable to what the link-local address is used for.  link local GASP
    > discovery, BRSKI-TCP, maybe later some ACP tunnell..

We had a long discussion about this at design team meetings a year plus ago,
and I tend to AGREE WITH YOU.
Note that we temporary addresses do not require any long term storage
(vs privacy enhanced stable addresses)

Our discussion, you might recall centered on the question of whether the
connection should be initiated from the JRC->Pledge (as a result of some
signal) or the other way around.  The reasoning is that the <TLS1.2 connection
reveals the ClientCertificate first.

Note that TLS1.3 will keep contents of the certificates transmitted private
against passive eavesdroppers, while TLS 1.2 will not.

If you feel strongly about removing this recommendation, I'd like to make
this a WGLC issue (in the tools issue tracker), so that we can point to the
discussion when we are asked why we aren't mandating them.

I wrote a Privacy Concern section here:

   https://tools.ietf.org/html/draft-ietf-6tisch-dtsecurity-zerotouch-join-01#section-10

tell me if you'd like to copy and paste some of that into a Privacy
Considerations section in BRSKI.

    > -----------------------------------------------------------------------------
    > Section 4.1 2)

    >> Methods SHOULD be run in parallel to avoid head of queue problems
    >> wherein an attacker running a fake proxy or registrar can operate
    >> protocol actions intentionally slowly.

    > methods == circuit proy, IPIP, ... ?  would also be recommended to try
    > different proxies in parallel, right ?

No methods refers to M_GRASP vs optional things like mDNS or IPv4.

Changes too long to post.

    > -----------------------------------------------------------------------------
    > Section 4.1 1)

    > a) The requirement to do proxy discovery via GRASP was already written
    > in 4.1. Please remove. Please use term DULL GRASP instead of just
    > GRASP.

okay.

    > I would also suggest to revisit the name of the objective. The

bikeshed.

    > Here is suggested text:

    > 180000, [ ["SRV.brski-proxy", 4, 1, "https" ], [O_IPv6_LOCATOR,

But, we didn't register a service called "brski-proxy", so that would be wrong.
I don't think we are interested in registered that name.

I didn't understand your CDDL.

    > objective-value = method
    > method = "https" ; or future methods ; CoAP not considered yet, see below

Like why would I do that?

    > -----------------------------------------------------------------------------
    > Section 4.2) 1)

    > a) Append: Therefore the "coap" method in the previous section was only
    > used for the example but is not included in the CDDL definition of the
    > GRASP objective above.

That's why I didn't include it as an example.

    > -----------------------------------------------------------------------------
    > Section 4.3) 1)

    > a) I would suggest removing this section and putting the requirement
    > into 4.1 together with the rest of the requirments.

I agree that the section is redundant.

    > Section 4.3) 1)

I guess you mean 4.4.

    > a) Suggest to move the first paragraph with requirements to section 4.1

    > b) Requirements must include:

    > ANI Registrars MUST announce their Registrar service via the ACP
    > instance of GRASP. They MUST support ANI TLS circuit Proxy and
    > therefore BRSKI across HTTPS/TLS native across the ACP. ANI Registrars
    > MAY support the IPIP proxy method by implementing IPIP tunneling for
    > their HTTPS/TLS traffic across the ACP.  ANI Proxies MUST support GRASP
    > discovery of Registrars .

okay.

    > c) The following is fixed up text for the remainder of 4.3 to solve the
    > following issues: - change of GRASP objective-name
    > (SRV.brski-registrar) and methods ("https", "https-ipip" as well as

Point not well taken.

    > coap for examples sake).
    >- changed address of registrar to be an actual ACP address

Because fda3:79a6:f6ee:0000:0200:0000:6400:0001 (I missed a zero!)
is somehow not a ULA?

    > - GRASP example was cut off/incomplete

I think only the closing ]], which is confusing because the artwork
ends with ]]>.  I've moved it into all into new files:

https://github.com/anima-wg/anima-bootstrap/blob/toerless-terminology-comments/jrcgrasp-cddl.txt

https://github.com/anima-wg/anima-bootstrap/blob/toerless-terminology-comments/jrcgrasp-example.txt

https://github.com/anima-wg/anima-bootstrap/blob/toerless-terminology-comments/proxygrasp-cddl.txt

https://github.com/anima-wg/anima-bootstrap/blob/toerless-terminology-comments/proxygrasp-example.txt

You'll find that there is a "pencil" icon on each page that lets you edit the
example or CDDL right there and send it as a pull request.

Please if you could seperate:
a) fixes to the syntax of the CBOR diag notation, or CDDL

from:
b) proposals to change any of the bits on the wire (including changing
   the name of the objective).

I'm skipping to the next section.

    >   a) The above "transport-proto /= 41" is technically an update to
    > GRASP RFC which allows only UDP / TCP. There is some process around

really?
QUESTION to Brian.

    >   c) I am not sure how we solve the problem of multiple IPIP Proxies on
    > a single LAN fighting to own h'fe80::1234. It seems to me we would have

You are solving a problem that does not exist.
You are right that IPIP is inadequately described at this point.
If only I was accepting a few dozen github pull requests rather than
this hundred page long email...

I wonder if we could remember that this is a Proposed Standard?

    >       "The Join Proxy SHOULD do a GRASP M_NEG_SYN for each interface
    > which they wish to relay traffic, as this allows the Registrar to do
    > any static tunnel configuration that may be required"

    >       Please insert implementable GRASP objective specifications for
    > this step here...

It's an error.
M_NEG_SYNC was replaced with M_FLOOD.  I've removed that.

Version -12 submitted at this point.
        https://goo.gl/Xyd5N2

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJanchdAAoJEJVM4Vb9/EKQNVEH/2DQwZRIiX4P1nKuO4m6cdQx
Qg7oWu4E0sZplh4QvjC0ak7usH/lIwXbz9+CTKdbgg/MWKNCjm7/o65cpScimZ/6
/QpofYtnlMyEQ4vh3vpgoKRnhPp2um/xMGp1P/j4esmVdmW1OKGkthN8/eX0ll8i
je5u3rgBZyRs4E5n453w9dprdH+BglSKXrzu8lwh5J8UGPTp7UYcXZdhZUyhgjuD
vB6PuPX1PbJTssidrBS+1YbtMjZ2/E2M+lNtaEwUs6cLtkqJvuNmC5hWNS5rPJmi
4fcGUJiB3MH5uMmYqbpEvdvCDjsnh5/dum14f9fJzz8WH7kXdrXHmM+T40cuCO8=
=5Vpy
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Mar  5 15:02:47 2018
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AF2612EB0F for <anima@ietfa.amsl.com>; Mon,  5 Mar 2018 15:02:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 HnnAdSAYvbs6 for <anima@ietfa.amsl.com>; Mon,  5 Mar 2018 15:02:41 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77DFE126BFD for <anima@ietf.org>; Mon,  5 Mar 2018 15:01:59 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 6A63620090 for <anima@ietf.org>; Mon,  5 Mar 2018 18:10:03 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 2D6FA80AE3 for <anima@ietf.org>; Mon,  5 Mar 2018 18:01:58 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
In-Reply-To: <152028986381.12884.9092671195107327813@ietfa.amsl.com>
References: <152028986381.12884.9092671195107327813@ietfa.amsl.com>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Mon, 05 Mar 2018 18:01:58 -0500
Message-ID: <18483.1520290918@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/0nsz9WA2193jTrJ4aS8WV5y2css>
Subject: Re: [Anima] I-D Action: draft-ietf-anima-bootstrapping-keyinfra-12.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2018 23:02:46 -0000

--=-=-=
Content-Type: text/plain


internet-drafts@ietf.org wrote:
    > A New Internet-Draft is available from the on-line Internet-Drafts
    > directories.

...
    > The IETF datatracker status page for this draft is:
    > https://datatracker.ietf.org/doc/draft-ietf-anima-bootstrapping-keyinfra/

    > There are also htmlized versions available at:
    > https://tools.ietf.org/html/draft-ietf-anima-bootstrapping-keyinfra-12
    > https://datatracker.ietf.org/doc/html/draft-ietf-anima-bootstrapping-keyinfra-12

So in case you aren't following the other thread, this version -12 represents
about 70% of Toerless' Shepherd comments (a total of 1900 lines).

Expect a -13 to be submitted when draft submissions open with the rest of the
changes and the additional comments that are in the queue.

Please note that there are multiple questions and issues being raised.
There are things that I did not accept as friendly amendments, and things
where I did not know if I agreed or not and asked QUESTION:

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlqdzGUACgkQgItw+93Q
3WXiSgf/YVTf6/XFdLEBEA96ZN3e3MdDydZZ5B8gZqx9EmSMWzsIVOxxt81xpMqC
zvdk8zPZ8od716ajG8Duqc7jeUuojgQBF1EwJs+MtLOn6szCywSyOebfyUk8NQGi
qD8ConvWH5HD/CURGI0/pL6lXz0LmEHy8rXLOEuo/wp44NWvWtUrjn8MqZIWlgC/
R2wJLcklRoeczXwdabjqZp1kuikGoW2NZ3NVGKZCParYom7MnvqYzSeqfUMUgLKE
lBGCcdVemmOBpAXnqzVI7vwLgKSTQ2hq++kyeLfO9RzXZsDopefWHIxLFS1TKg/S
6ZcE4lCFl2NeQNLaldO0JpMcQ/ntJg==
=wg68
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Mar  5 15:10:33 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 247DA126BFD for <anima@ietfa.amsl.com>; Mon,  5 Mar 2018 15:10:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 aBf86yT1Cvj8 for <anima@ietfa.amsl.com>; Mon,  5 Mar 2018 15:10:30 -0800 (PST)
Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (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 C96B4120227 for <anima@ietf.org>; Mon,  5 Mar 2018 15:10:30 -0800 (PST)
Received: by mail-pf0-x231.google.com with SMTP id q13so7928237pff.0 for <anima@ietf.org>; Mon, 05 Mar 2018 15:10:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=6qFub+8YMgQH79g2PmayFwB3zJoM4puf/nIebumO4zU=; b=UUkj919sZANQZ2vFTXJpJQzbXEf9vdG/hwzIUS8QpIyDNJNshD7jcrs0ZtqDx054iQ +vHt+UYeNtjOSPmV8yYqqDtZMOXQc9QHnqdZQWR3lJQWCk0xPrrortJdvZw92fjb0Sdd l3Sh04sLxC+5+BK61zluPDfUQOnBaN6+JO7WaigAYYNix5GZt6TWyp41xIuSyeC+CG1Z 6kL1osV2wTK696Yme2ZC12amWrpjRiLz6Gw13E93YulmMLvmVeuFvkxqvHBivfY7FKmZ s9lYBq5NFhk20kb+wM+cmSuuizDh8a/n71Td2OwUQR4wbR30+rd985aUKE0zO7r0Mngj xtfQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=6qFub+8YMgQH79g2PmayFwB3zJoM4puf/nIebumO4zU=; b=skh8uRt0Us9Fj4O0VfAbQisKCYrcuuqAfF+/QLKH7anD9FUh+oKo6py+/5hLk4j/8G DutxgGLYZkXHA0Zhv1mTFwBBQYyY27k9z0WsU5NNjrUdw5CCfA72qVKbmFJfStncoeBo M4kALxOE+lrYIc9NOeCHYlzuIW4Vin7ceA3hVpetX1fcvwSaD/m3pHMZ6TMsL197WDX1 iNtbYBPN7tx25yG9WNi2wWRdExhm0K3g3QQdf1VAeuIJhap5BVMOtsVumajanXEcszCK fKwsgdoENWZrVYMIb7aUVYG0Wg1wkIRiAXIvv3Gw0j6nGJw3E/qF3RKLzzpcBW2PIFxQ ZGuw==
X-Gm-Message-State: APf1xPBfMXzR3dZZOYxkhUpgsU1a9Jt/QgusE+vGXzZjNsZHK+QIBTi0 jmtcspY389hAq18TCXIwsW4+ocfc
X-Google-Smtp-Source: AG47ELuqe3Em2nO7eAdZrMtgWDmerse4ax0UbC37EIzH9wMqa7dsn6KQaloDGTjQ+2WL572Kz/UScw==
X-Received: by 10.99.110.131 with SMTP id j125mr13537621pgc.382.1520291430092;  Mon, 05 Mar 2018 15:10:30 -0800 (PST)
Received: from [130.216.38.95] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.38.95]) by smtp.gmail.com with ESMTPSA id y186sm26295625pfb.92.2018.03.05.15.10.28 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Mar 2018 15:10:29 -0800 (PST)
Sender: Brian Carpenter <becarpenter46@gmail.com>
To: anima@ietf.org
References: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de> <10097.1520289885@dooku.sandelman.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <fb3efc76-ed50-9e09-cf9b-c8c39492464e@gmail.com>
Date: Tue, 6 Mar 2018 12:10:28 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <10097.1520289885@dooku.sandelman.ca>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/m7B_FeO0DQOSNUJOwO3ECJKCGoM>
Subject: [Anima] Proto 41 [Shepherd review draft-ietf-anima-bootstrapping-keyinfra-09]
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2018 23:10:32 -0000

> I'm skipping to the next section.
> 
>     >   a) The above "transport-proto /= 41" is technically an update to
>     > GRASP RFC which allows only UDP / TCP. There is some process around
> 
> really?
> QUESTION to Brian.

It's an extension, which seems to me is not strictly speaking
an update. So the WG has two choices, IMHO:

1. Leave it here described as an extension, don't touch the GRASP spec.
2. Add this to the CDDL in GRASP at AUTH48, with the AD's approval.

The addition would give:

transport-proto = IPPROTO_TCP / IPPROTO_UDP / IPPROTO_IPV6
IPPROTO_TCP = 6
IPPROTO_UDP = 17
IPPROTO_IPV6 = 41

(It is not an accident that the names chosen are those used
in the socket API. Sadly, they are not maintained by IANA.)

I don't really care which solution we choose.

    Brian


From nobody Tue Mar  6 10:27:38 2018
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 458291250B8 for <anima@ietfa.amsl.com>; Tue,  6 Mar 2018 10:27:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 BrU7eDTufVep for <anima@ietfa.amsl.com>; Tue,  6 Mar 2018 10:27:34 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20968124F57 for <anima@ietf.org>; Tue,  6 Mar 2018 10:27:34 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 1A95220090; Tue,  6 Mar 2018 13:35:41 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 0866480C90; Tue,  6 Mar 2018 13:27:33 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: anima@ietf.org
In-Reply-To: <fb3efc76-ed50-9e09-cf9b-c8c39492464e@gmail.com>
References: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de> <10097.1520289885@dooku.sandelman.ca> <fb3efc76-ed50-9e09-cf9b-c8c39492464e@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Tue, 06 Mar 2018 13:27:33 -0500
Message-ID: <31207.1520360853@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/DD8zyyeOuO8Vi9mpJjJY0YVrACM>
Subject: Re: [Anima] Proto 41 [Shepherd review draft-ietf-anima-bootstrapping-keyinfra-09]
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2018 18:27:36 -0000

--=-=-=
Content-Type: text/plain


Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    >> >   a) The above "transport-proto /= 41" is technically an update to
    >> > GRASP RFC which allows only UDP / TCP. There is some process around
    >>
    >> really?
    >> QUESTION to Brian.

    > It's an extension, which seems to me is not strictly speaking
    > an update. So the WG has two choices, IMHO:

    > 1. Leave it here described as an extension, don't touch the GRASP spec.
    > 2. Add this to the CDDL in GRASP at AUTH48, with the AD's approval.

    > The addition would give:

    > transport-proto = IPPROTO_TCP / IPPROTO_UDP / IPPROTO_IPV6
    > IPPROTO_TCP = 6
    > IPPROTO_UDP = 17
    > IPPROTO_IPV6 = 41

    > (It is not an accident that the names chosen are those used
    > in the socket API. Sadly, they are not maintained by IANA.)

I guess I thought that any value from
  https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xml
was valid.

>   Note 3: The IPPROTO values are taken from the existing IANA Protocol
>   Numbers registry in order to specify TCP or UDP.  If GRASP requires
>   future values that are not in that registry, a new registry for
>   values outside the range 0..255 will be needed.

"not in that registry", and IPV6=41, is in that registry.
While there a bunch which probably are nonsense to use (e.g, PRM)
a bunch are relatively clear: SCTP, RDP, DCCP...

I believe that the answer is to move all the IPIP specification to another
document.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlqe3ZQACgkQgItw+93Q
3WUamQgAjVZUtPV910Px6PrhQt+4jD+QeX6/tzYXzgvB4HOSKnb/rtH9ORrQD3Nc
TkoVYy0KVTLe12/dTePs1VNG3Ln6sMd+y1LKN3vTUPsmRcK8eWZKgrXBl3qwabdt
vojpm6lXeLCuIw2W883xeiACmod19UYh5qn5Kz/+Mcy/PVgvfOQJX3iSWhYZPHqF
JC7OA7uNPJ6g2HPiotmgSIwCQfxEAKFYk7hvLtJ3Y9KXtluCHkOu3vRaNwkXkNtR
WCnDSH9BFb2IB+b4XY92UG8kR0ci6m9jhSqKoam5Amu/UPFyrxxdZZlNdeu93c4i
fNPJWpaNWMGp1EjkGZ6B/rZaRUbCfA==
=5+JX
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Mar  6 10:46:43 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12E9C12D778 for <anima@ietfa.amsl.com>; Tue,  6 Mar 2018 10:46:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 U8TS102uUaw0 for <anima@ietfa.amsl.com>; Tue,  6 Mar 2018 10:46:38 -0800 (PST)
Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) (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 90DDC124234 for <anima@ietf.org>; Tue,  6 Mar 2018 10:46:37 -0800 (PST)
Received: by mail-pf0-x229.google.com with SMTP id j20so9113626pfi.1 for <anima@ietf.org>; Tue, 06 Mar 2018 10:46:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=BLKcxZs8UUfUJzuHJKwNlXY036wrYSa8CmGyoTqW4xI=; b=N6EmwxiuHm3Vt+rsgtc9XE9avRQoqF7lJQroxA8rwUdeR9K5ZBrUuO2OXfKzDgwLNV wkwXC7k3Q8tBq0OBHzaLGhBUZx5nlAzffB+jQrqE//bXHiGrxJoGMyziyTi+mLgCFTFm PnkVswv+jVjpvWacNM/QwmtO8TVnVt5tr49VqwlrULw3J0h0N9Piel8u2vQr8FRpndTR s0Kw+uuJM/Ag5O28SZzehuZkHXQwiQNrH/rqMNOlt9GzW0zvtUqkVBMZQhyFaLPET5/1 tCNArOUWjwe8riJgSlFdOJFK351Ijp1E7mFQuATK7B4+JlMlYut4YymE74ww0o3h3iU4 9APA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=BLKcxZs8UUfUJzuHJKwNlXY036wrYSa8CmGyoTqW4xI=; b=tjY9uxt9rhkgGcFUj4tZGJoAsNDT/ZsmIjbBaXpFMnEQP9RibS0ar/OqSHIKoknQwT 6kLX9Fc2/XaNmnDa7zNGl45XXhVd/1gKmbJbAFAcdc6CGxG3DvIEaPWJA1Dbn875w8ua mncUXSgdiF0QroJltAflAzQe+Y5MYMjA2YmizD6V99kb7iVsSJFPIGYkbarYEvyr4/3w 7klGwQquvz8UZLNRU2CDPV+RDZTE3AF68RDFk1v/YzjL8UOEo8MhvAwC9K136XXso498 UtC4MMEkJFBUeVCj4mvpp3QoG7cQtW97vp1NT6md8ZZlVVCTWTRgPWv0CQ5CL54kpkN6 FFkQ==
X-Gm-Message-State: APf1xPDbyALmIPBeblBziJiPDOGz6j/8A5Eu8u5twfW2tR/Cv3o7kf/c dyN5dWwlTmEAsrWn2NPFJGhfOHhP
X-Google-Smtp-Source: AG47ELtFORbrOtEJVRg21nesvYjPavXinvKAJG4IXUcYJO2gfG+U7u/ip2qlmIiuRKsJbEC5PyzXJQ==
X-Received: by 10.101.97.26 with SMTP id z26mr16033983pgu.44.1520361996643; Tue, 06 Mar 2018 10:46:36 -0800 (PST)
Received: from [192.168.178.30] ([118.148.126.225]) by smtp.gmail.com with ESMTPSA id o28sm8268050pfa.62.2018.03.06.10.46.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Mar 2018 10:46:36 -0800 (PST)
Sender: Brian Carpenter <becarpenter46@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: anima@ietf.org
References: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de> <10097.1520289885@dooku.sandelman.ca> <fb3efc76-ed50-9e09-cf9b-c8c39492464e@gmail.com> <31207.1520360853@obiwan.sandelman.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <ed7c49ae-bc9f-6e0c-b603-cca448e0ca50@gmail.com>
Date: Wed, 7 Mar 2018 07:46:36 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <31207.1520360853@obiwan.sandelman.ca>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/sZErWknmwt2KpzCoo-lKjFFFfPs>
Subject: Re: [Anima] Proto 41 [Shepherd review draft-ietf-anima-bootstrapping-keyinfra-09]
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2018 18:46:40 -0000

On 07/03/2018 07:27, Michael Richardson wrote:
> 
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>     >> >   a) The above "transport-proto /= 41" is technically an update to
>     >> > GRASP RFC which allows only UDP / TCP. There is some process around
>     >>
>     >> really?
>     >> QUESTION to Brian.
> 
>     > It's an extension, which seems to me is not strictly speaking
>     > an update. So the WG has two choices, IMHO:
> 
>     > 1. Leave it here described as an extension, don't touch the GRASP spec.
>     > 2. Add this to the CDDL in GRASP at AUTH48, with the AD's approval.
> 
>     > The addition would give:
> 
>     > transport-proto = IPPROTO_TCP / IPPROTO_UDP / IPPROTO_IPV6
>     > IPPROTO_TCP = 6
>     > IPPROTO_UDP = 17
>     > IPPROTO_IPV6 = 41
> 
>     > (It is not an accident that the names chosen are those used
>     > in the socket API. Sadly, they are not maintained by IANA.)
> 
> I guess I thought that any value from
>   https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xml
> was valid.

That was certainly my thinking, but we surely didn't want to write
out the CDDL for the whole registry.
 
>>   Note 3: The IPPROTO values are taken from the existing IANA Protocol
>>   Numbers registry in order to specify TCP or UDP.  If GRASP requires
>>   future values that are not in that registry, a new registry for
>>   values outside the range 0..255 will be needed.
> 
> "not in that registry", and IPV6=41, is in that registry.
> While there a bunch which probably are nonsense to use (e.g, PRM)
> a bunch are relatively clear: SCTP, RDP, DCCP...

Yes. To my mind, an application of GRASP can choose to add any valid
protocol number to its use of GRASP.  So I think we are OK without
changing the GRASP text.

The tricky bit is if we want to add a non-IP protocol such as HTTP,
which is where we would need a new registry for values >255.
> 
> I believe that the answer is to move all the IPIP specification to another
> document.

Well, you can use 41 in BRSKI with a reference to that "Note 3" in GRASP,
I think. "As mentioned in Note 3 of the definition of the Locator IPv6 address option
in [GRASP],..."

    Brian


From nobody Tue Mar  6 12:47:26 2018
Return-Path: <michael.h.behringer@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF19612D7E4 for <anima@ietfa.amsl.com>; Tue,  6 Mar 2018 12:47:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 iYTCd8jn3qmQ for <anima@ietfa.amsl.com>; Tue,  6 Mar 2018 12:47:23 -0800 (PST)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (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 38E261270B4 for <anima@ietf.org>; Tue,  6 Mar 2018 12:47:23 -0800 (PST)
Received: by mail-wm0-x22f.google.com with SMTP id q83so727345wme.5 for <anima@ietf.org>; Tue, 06 Mar 2018 12:47:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=0aCUrFCqJke5tjR6fuOfIdKX7rDz9O8hdlI77tTo0bM=; b=YTwSltkfeuVEYWkY3/23DWAAVJ9SIgfdPRkbil9JuJ0J6Xjo4RdSQ41yLJgg5Gt5FT KCwMAJMeEq59O+nvpwJ8sz8QQzwRqvDlOJMArPxJbZE58/NLPahEur+/w1mwSD1av85j EnM7Tva9+I5z74LHivPoR/7GQZKryiZmX3gPD8t38GNwMLHa0mRpTfOWbyfa+0K6NHCR zlJgsRc4C8UQy3Gt3XVaC/BHDAgTekqfwrL/sEh39WoRtNsdfqASFC10BXs/jB3HI2YF FfrI/yCDqjukTOdxAJzymz8BGVdbHp1tr/Lw8XMEsVywA8mh3VaY10zIGyB6T7jbMgfL KPhQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=0aCUrFCqJke5tjR6fuOfIdKX7rDz9O8hdlI77tTo0bM=; b=J+h+zOTkJiXjiMEKcnGra31iO4N8aqnev2ZiwoqBlfGkbmn+G05HKwri6ckS3dptJM RA0qQ2eaup9+sXdU+UVXgsBv4SolixcbwluBL9SknFji00bpxP27sgJb74uVuneOrwPp ayT+69RvURkzzYkgr/0UaqBLr5y+OQ9VAIptTHWXkB4dvbsHAsVATS7Lq9PWK418mMdQ FViNyoEx+NKWOOrxWvHJb+JQM+viRwOqMQnGrQzPYIl1djeDqa1PAhxKYSZvYcgJ/q2s MK6PVOtQKrZAKcXwyHLQx6AkOibyPpN6g0HQUQGn90xsyhwV6hlPFI5jgudQaTkQVorJ p79g==
X-Gm-Message-State: AElRT7EQcvlpyxuaguFe3g6J48U8EKS5udG0EJ2Zm3sPCk/W5yvI8ECW s8NB0V3YAx2MAwDLVTOQZEoTw+5l
X-Google-Smtp-Source: AG47ELulYWQrxBZIhvu3cyEcKvTHoS6TYALArvHJ3SDoNAJI1NeC1UVXAG+yg6PCNHTxWWdcPdOSGw==
X-Received: by 10.28.166.201 with SMTP id p192mr11441983wme.132.1520369241428;  Tue, 06 Mar 2018 12:47:21 -0800 (PST)
Received: from [192.168.1.29] (ANice-652-1-18-241.w83-201.abo.wanadoo.fr. [83.201.29.241]) by smtp.gmail.com with ESMTPSA id 62sm16173551wrf.24.2018.03.06.12.47.20 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Mar 2018 12:47:20 -0800 (PST)
From: "Michael H. Behringer" <michael.h.behringer@gmail.com>
X-Google-Original-From: "Michael H. Behringer" <Michael.H.Behringer@gmail.com>
To: anima@ietf.org
References: <5D36713D8A4E7348A7E10DF7437A4B928182F916@NKGEML515-MBX.china.huawei.com>
Message-ID: <3b62e2d2-c8d7-a9d9-1bd3-08758a02e8b1@gmail.com>
Date: Tue, 6 Mar 2018 21:47:19 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B928182F916@NKGEML515-MBX.china.huawei.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: fr-classic
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/Ye2GVU4MApFViZ90dpYkpdP7nv8>
Subject: Re: [Anima] Call for agenda ANIMA @ IETF 101, London
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2018 20:47:25 -0000

Hi Sheng,

Not sure we need a slot for the reference model. I guess it should now 
go to the IESG, right?

Up to you. If we have time, I could do a short 10 min update. I won't be 
in person in London, but can present remotely.

Michael


On 28/02/18 06:56, Sheng Jiang wrote:
> Hi, all anima,
> We have been allocated a session of 2.5-hour for the ANIMA WG meeting 
> for IETF-101 (London) and are starting to collect agenda items for the 
> session. Please send your request for agenda by March 8th, Thursday.
> Giving that most of our chartered work items have been sent to IESG 
> for publication by the meeting, we expect short time slots for only 
> two or three of them. For this coming meeting, we would like to 
> discuss potential future ANIMA works.
> As normal, the priority among these non-charter work items would be: 
> these that have active discussion in mail list, then these have 
> submitted drafts, and topics without drafts.
> Please send us (anima-chairs at ietf.org<https://ietf.org/> 
> <http://ietf.org%3Chttps/ietf.org/%3E%29>;) requests for time slot by 
> March 8th, Thursday and include:
> Name of time slot:
> Name of draft(s):
> Time requested:
> Presenter name(s):
> More details about the IETF 101, London can be found at:
> http://www.ietf.org/meeting/101/index.html
> Again, presenters and draft authors please invoke active discussions 
> in the ANIMA list. Mail list is a very good place to discuss and reach 
> consensus on technical issues.
> Best regards,
> Toerless & Sheng
>
>
>
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima


From nobody Tue Mar  6 12:58:14 2018
Return-Path: <michael.h.behringer@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DD2712D7E8; Tue,  6 Mar 2018 12:58:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.3
X-Spam-Level: **
X-Spam-Status: No, score=2.3 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, GB_SUMOF=5, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no 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 3zhDx2-8DMVA; Tue,  6 Mar 2018 12:58:10 -0800 (PST)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (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 2FD4812D7F6; Tue,  6 Mar 2018 12:58:09 -0800 (PST)
Received: by mail-wm0-x22d.google.com with SMTP id w128so830895wmw.0; Tue, 06 Mar 2018 12:58:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=NCxYBWgz5mDni3mbiSHoqqDcArdkiDRaywd/s753KvM=; b=ZMfZIhOu1fduRxZKAnV4ryz/oJf3l0xd57Dsz2WE4hXXasijRoZg4OqjWMjJuTISSu 9LweB3AT3YmPnIYEAN5XYc88aSwb8DQs5B0I0z9uO7CrnefwTI7q2yncMzPz1BeoDIIC 1HLcV1l0hhrthXQ2jHZLLh177MCjRsUtBECo8xC6/2v6N0N44bvh5TMP7abfQVQ89rp2 LF4Wk+GdJRNQsku8M8XLr6PiybVCAw8Cn/CQQuu+xv/1owAPDaWe+r+SgKujkK3yVbuH IxVOqgJRUMdORaXzdoB9mxPwZ6RaMppUrZO6J5M/hZIEOvzmPDjaneHbP//2m42WLVjW qjGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=NCxYBWgz5mDni3mbiSHoqqDcArdkiDRaywd/s753KvM=; b=Am+wSsLLXEfI+HKhsWmekoO7mEyzd8gKMLbVAhgr705BkUiicXWINsP7IrnHsLFYj7 jFNrBglBxV/Meu4gRkcuFnleJmTlGsgqneIzvgRSxlvae4acYHTkGg5FfHaGpY/JDLvC Aa1n6lopl6Q+3Y/G7tapGKfykF2Q1mQalsXYoabvR90ob45oEMvBceyY0RRvjf6s4pNR Q4ZeBiaqBg2bF9Ey3v8uMFCHxapWX4Xtt0Y+hvM9PnUshd7R5ZGLI6ABbGwKW9HCqlmA cAc9lbn64QhICAiur/dyHG7vw+3huShIS6VJ+UkKJgcZ854iONxJVFzxHDalNdNWU7L0 Ulbg==
X-Gm-Message-State: AElRT7Hmq12zngeE4UZgIa09BB2y/ln9SnQ/5VK86/8/QUHhxLhDIgLT cCwFKufj6zO4E0ZSz0iaPwnee8Nv
X-Google-Smtp-Source: AG47ELtcmbFswWYHZRhiMqrJqQ3XmZjuIVmNhC/NQ7kfW8AzO6RMSka1FqnBYwY1u5a1g9E+u8L74Q==
X-Received: by 10.28.150.138 with SMTP id y132mr13034312wmd.104.1520369887311;  Tue, 06 Mar 2018 12:58:07 -0800 (PST)
Received: from [192.168.1.29] (ANice-652-1-18-241.w83-201.abo.wanadoo.fr. [83.201.29.241]) by smtp.gmail.com with ESMTPSA id 4sm8919003wmz.31.2018.03.06.12.58.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Mar 2018 12:58:04 -0800 (PST)
From: "Michael H. Behringer" <michael.h.behringer@gmail.com>
X-Google-Original-From: "Michael H. Behringer" <Michael.H.Behringer@gmail.com>
To: Sheng Jiang <jiangsheng@huawei.com>, "anima@ietf.org" <anima@ietf.org>
Cc: "anima-chairs@ietf.org" <anima-chairs@ietf.org>
References: <5D36713D8A4E7348A7E10DF7437A4B92818111C7@NKGEML515-MBX.china.huawei.com> <22a65bfa-8954-304d-5a65-38d9e6d98b3f@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B928182FC9F@NKGEML515-MBX.china.huawei.com>
Message-ID: <4c902661-a32d-aac2-4ed1-65e92ce028e5@gmail.com>
Date: Tue, 6 Mar 2018 21:58:03 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B928182FC9F@NKGEML515-MBX.china.huawei.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: fr-classic
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/bwRzAG23JlLcVa-Dn4dh7lJMKCo>
Subject: Re: [Anima] Review comments//RE: WGLC on draft-ietf-anima-reference-model-05 - Respond by January 22nd, 2018
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2018 20:58:13 -0000

Inline...

On 28/02/18 15:36, Sheng Jiang wrote:
> Hi Michael,
>
> Thanks for addressing my review comments. Below in lines for my further comments regarding to several points. None of them are major. So, I will start my document shepherd based on the current 06 version. It is up to you to do a quick update soon or addressing them together with the IESG review comments, which I am sure will have.
>
> Regards,
>
> Sheng
>
>> -----Original Message-----
>> From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Michael H.
>> Behringer
>> Sent: Friday, February 23, 2018 9:10 PM
>> To: Sheng Jiang <jiangsheng@huawei.com>; anima@ietf.org
>> Cc: anima-chairs@ietf.org
>> Subject: Re: [Anima] Review comments//RE: WGLC on draft-ietf-anima-
>> reference-model-05 - Respond by January 22nd, 2018
>>
>> On 18/01/18 09:59, Sheng Jiang wrote:
>>> Hi, authors of anima-reference-model,
>>>
>>> I have reviewed the draft as the document shepherd, see below
>>> comments. Overall, I feel this document is very useful and it is
>>> almost ready for be published. Please properly address my comments
>>> together with other WGLC comments you may receive. Another revised
>>> version of the document is needed to process the document further if
>>> it passed the WGLC.
>>>
>> Hi Sheng,
>>
>> First of all thanks for the thorough review. I am now finished with
>> working your comments into the draft. I am just publishing version -06.
>>
>> This version should address all your comments. I am not aware of any
>> other outstanding comments, and believe we have addressed all open issues now.
>>
>> Details below in line.
>>
>> Michael
>>
>>> General issues:
>>>
>>> 1. In section 3.1, it says “The Autonomic Control Plane (ACP) is the
>>> summary of all interactions of the Autonomic Networking
>>> Infrastructure with other nodes and services.” I’m a bit confused by this statement.
>>> In my understanding, the ACP itself is mostly a “channel”, although
>>> some ANI functions (signaling, aggregated reporting etc.) are
>>> running within the channel, they should be parallel with ACP
>>> function in the architecture view.
>>>
>>> At the same time, there are indeed some functions considered as
>>> sub-functions of the ACP, e.g. the addressing and routing, which are
>>> necessary to make the ACP runnable.
>>>
>>> So, my questions to the co-authors:
>>>
>>> 1) Do you see ACP as an individual function as I understood (mostly
>>> a channel), or a summary of a suite of functions running inside the ACP?
>>>
>>> 2) What functions are sub-functions of ACP, and what are in parallel
>>> with ACP?
>>>
>> There are really two meanings to the term "ACP". This has caused quite
>> some confusion, and I agree it needs to be nailed once and for all.
>> Thanks for raising it here.
>>
>> 1) The general term "control plane" refers to the sum of all protocols
>> that control network behaviour. Like, in a traditional network, routing protocols, etc.
>> Consequently, an "Autonomic Control Plane" is the sum of all protocols
>> that controls the behaviour of an autonomic network. In
>> draft-ietf-anima-stable- connectivity we now use the term "Generalized ACP" for this abstract concept.
>>
>> 2) In the ANIMA context, we use the term "ACP" also to describe a very
>> specific implementation of the generic concept of an "Autonomic Control Plane".
>>
>> I now cleared up the naming in the reference draft. Where we mean the
>> abstract concept (3.1 for example), I now use "GACP", where we mean
>> the implementation, I now use "ACP" and refer to the ACP draft.
>>
>> Specifically, I changed in 3.1 from ACP to GACP. And re-worded section
>> 4.6, which is all about the implementation of the ACP.
> [Sheng] My original comment implied two aspects:
> 1. As you explained, the "General" control plane vs. the "specific" implementation (ACP). So, as I understood, the ACP is an instance of GACP. I have no problem on this.
> 2. The specific ACP actually serves as a management channel for the underlay network, in this sense, the ACP could be seen as a "management plane" for the underlay network; in other words, the ACP is a "Virtual DCN(Data communication network)". Thus, there could be a summary of management functions running inside the ACP, and this summary doesn't belong to ACP itself. If you agree with it, I think this also needs to be clarified.

Yes, of course I agree with it! :-)  I'm however worried that this will 
confuse readers a lot. I suggest in this document to stick to the 
autonomic aspect of the ACP only. And in section 4.6 we already say "See 
[I-D.ietf-anima-stable-connectivity 
<https://tools.ietf.org/html/draft-ietf-anima-reference-model-06#ref-I-D.ietf-anima-stable-connectivity>] 
for uses cases for the ACP." which describes in detail what you're 
saying above. I suggest we leave it with this in the reference model.
>
>>> 2. I’m confused by the whole purpose of Section 3. The first
>>> sub-clause is describing the architecture of an Autonomic Network
>>> Element, while the rest sub-clauses (adjacency table, state machine
>>> etc.) seems more like “implementation considerations” or “procedures”.
>>> I think both are useful content, but they are in two different
>>> dimensions, maybe separate them into different sections?
>>>
>> Well, the section is about the network element. I find it quite logic
>> that you first discuss the architecture of the element, then how it
>> behaves in a network. However, I added an explanatory intro at the
>> beginning of that section to make it clearer. Thanks for pointing out
>> that this wasn't clear!
>>> 3. Some texts (e.g. paragraph 4 of Section 1) are directly bind to
>>> the WG’s charter, I’m not sure it is a good approach that an RFC
>>> normatively refer the WG charter which is dynamically changed along
>>> with the work going on in the WG. Maybe just simply re-phrase the
>>> “chartered work” as “Phase 1/near term work”, and “non-chartered” as
>>> “Phase 2 long-term”?
>>>
>> Agree that needs to be fixed. Did some editorial changes for that. The
>> sections with an (*) now start with a sentence like this:
>>       <t>... is not covered in the current implementation specifications.
>> This section is for informational purposes, for following phases of
>> standardization. </t>
>>
>> As part of that fix, I also re-worded the abstract. It now reads:
>>
>> This document describes a reference model for Autonomic Networking. It
>> defines the behaviour of an autonomic node, how the various elements
>> in an autonomic context work together, and how autonomic services can
>> use the infrastructure.
>>
>> Now, the word "charter" is no longer in the text at all.
>>
>> Comments?
>>> 4. The whole Section 7 seems too theoretical and abstract. The
>>> described concepts are valuable, I’d suggest to have more texts
>>> mapping these concepts into the ANI/AN.
>>>
>> I made the changes described above, to point out very explicitly that
>> these sections are essentially for future study. I would prefer NOT to
>> do any more editing beyond that. That should be done in a subsequent
>> document, I think.
>>> Specific comments:
>>>
>>> Section 1 Introduction
>>>
>>> - Paragraph 3 claims “This reference model allows for this hybrid
>>> approach.” I think it would be better to explain in what degree the
>>> “hybrid” could be. For example, the ANI actually doesn’t support
>>> non-autonomic nodes to join in the same domain with the autonomic
>>> nodes; thus, in this deployment level, it is not “hybrid”.
>>>
>> Good point. I added an example to explain the concept. I thought of
>> adding more, but then I think the intro would become too long.
>>> - As said in the general issues, paragraph 4 seems binding with the
>>> WG charter too much.
>>>
>> That is resolved.
>>> Section 2 The Network View
>>>
>>> - In the figure, it seems the ASAs are hierarchical, but there is no
>>> relevant texts. My understanding is that, it is reasonable to
>>> distinguish layered ASAs, e.g., some ASAs might be very fundamental,
>>> and should be the future work of the Anima WG; while most of the
>>> specific ASAs are service/scenario relevant, that might not be
>>> suitable to do them case by case in Anima.
>>>
>> Oh, it was not the intention to imply a hierarchy. Thanks for pointing
>> this out. ASAs may or may not be hierarchical. I added a sentence to
>> clarify: "ASAs may be standalone, or use other ASAs in a hierarchical way."
>>> - “The current charter of the ANIMA WG is to specify the ANI, using
>>> a few autonomic functions as use cases.” Again, I’m not sure it is
>>> good to bind the RFC to the WG charter.
>>>
>> Fixed.
>>
>>> Section 3 The Autonomic Network Element
>>>
>>> - If Figure 1 means to make the ASAs hierarchical, then it is better
>>> to be consistent in Figure 2.
>>>
>> I think this is fixed with the above text. Let me know if it is not
>> clear enough.
>>> - Nits in Figure 2
>>>
>>> Synchronization -> synchronization
>>>
>> The RFC editor will fix all the UK vs US English issues. I'll leave it
>> to them, since I'm not a native English speaker.
>>
>>> In the ANI part, the “Discovery, negotiation and synchronisation
>>> functions” looks like a sub-item of “Autonomic Node Addressing”, I
>>> guess it should be typo?
>>>
>> Good catch. Fixed.
>>
>>> - Section 3.1 “The Autonomic Networking Infrastructure (ANI) is
>>> normally built on a hop-by-hop basis.” It is true for ACP, but I
>>> don’t think it applies for all the other ANI functions, e.g.
>>> negotiation/sync signaling.
>>>
>> Note the "built". I think the sentence is correct. However, to
>> clarify, I changed "built" to "constructed". And, we're really talking ACP here.
>> I changed that as well.
>>> - Section 3.2, the first bullet point of paragraph 3 “link local
>>> discovery”, it is ambiguous that what kind information is gathered
>>> through GRASP. I think there should be some basic information
>>> gathered through ND protocol.
>>>
>> Yes, this section is a bit ambiguous, I agree. But if we want to make
>> it precise, it's going to explode the section and make it unreadable.
>> Hmmm... I think the issue is really the phrase "This is described in
>> [GRASP]". I re-phrase that to "The related standards track documents
>> (GRASP, ACP, BRSKI) describe in detail how link local discovery is used."
>>> - Section 3.2, the third bullet point: “Once the node is part of the
>>> ACP of a domain, it will use GRASP discovery [I-D.ietf-anima-grasp]
>>> to find Registrar(s) of its domain and potentially other services.”
>>> The later version of BRSKI changed to use a GRASP Flood message to
>>> actively broadcast the registrar service by the proxies in their
>>> link-local scope.
>>>
>> I removed "discovery". "It will use GRASP" is correct.
>>
>>> - Section 3.3.2, I think it would be good to briefly discuss the
>>> situation that if an enrolled node re-boot from power cut or be
>>> attached to another network, how the transition state would be? Is
>>> it the same with “Factory reset”?
>>>
>> This discussion is not specific to 3.3.2. A node can reboot at any
>> point in time. The important part is if it keeps its LDevID or not.
>>
>> But you're right. This is not mentioned anywhere... Hmmm... Thinking
>> more, this is just another transition in the state machine, for each
>> state. I'll add that, I think it makes sense.
>>
>>       "Powercycle event: The device loses all state tables, but not its
>> domain identity (LDevID). Next state: 2."
>>
>> I hope I'm not opening a can of worms here... It is possible to
>> conceive a model where a device also loses its LDevID... I think
>> that's going to be an extreme corner case, and would prefer to not even mention it here.
>> Thoughts?
> [Sheng] The added texts are good for me. But please pardon me for opening the can even a bit more:
> When one device has enrolled, maybe it is good to keep the domain certificate as well as the LDevID? In this way, the network won't suffer too much in a power outage event.
> If it is plugged into another domain, it should not be difficult to detect the abnormity.

We're saying the same thing. LDevID *is* the domain certificate. And it 
should keep that. You probably meant to say the IDevID, which it also 
keeps.

Although, my feeling is that we should not *forbid* a case where the 
LDevID (domain cert) is lost in a power outage / reboot event. While our 
current use cases would probably not behave optimally, I think there may 
be special cases in the future where this may be an option.

>
>>> Section 4 The Autonomic Networking Infrastructure
>>>
>>> - Section 4.2 Addressing, there are a list of comprehensive
>>> requirements of addressing, which are good content. It might be
>>> better if Section 4.1 Naming also include such a requirement list?
>>>
>> I think the requirements are in the section, just not in a bulleted
>> list. Frankly, I prefer not to change this at this stage of the
>> document. Let me know if we're missing a requirement.
>>
>>> - Section 4.5 “All autonomic nodes in a domain must be able to
>>> communicate with each other, and with autonomic nodes outside their
>>> own domain.” The cross-domain mechanism hasn’t be covered yet, maybe
>>> it’s better to note this feature is for “long term” work rather than
>>> “phase 1”.
>>>
>> OK, changed that to "in later phases also with ..."
>>
>>> - Section 4.6 “The totality of autonomic interactions forms the
>>> "Autonomic Control Plane". Again, it is the same as No.1 general
>>> issue as described above.
>>>
>> Changed to "The "Autonomic Control Plane" carries the control
>> protocols in an autonomic network."
>>
>>> Section 5 Security and Trust Infrastructure
>>>
>>> - Section 5.2 describes domain certificate; I think the device
>>> certificate, which is pre-set by the manufacture also needs to be
>>> mentioned.
>>>
>> Done.
>>
>>> Section 6 Autonomic Service Agents (ASA)
>>>
>>> - It might be good to reference draft-carpenter-anima-asa-guidelines?
>>>
>> Good point. Included.
>>
>>> - Section 6.3 is interesting, it actually unveils the ANI functions
>>> (except GRASP) are yet ASAs. It is no problem for me, but I have a
>>> bit concern that new readers might be confused about the “overlap/mixture”
>>> between ANI and ASAs?
>>>
>> I thought we were quite clear about that. In section 6.1 we say:
>>
>>      o  A few 'infrastructure ASAs' that use basic ANI features in support
>>         of the ANI itself, which must run in all autonomic nodes.  These
>>         are outlined in the following sections.
>>
>> I suggest we leave it at that.
>>
>>
>>> Section 7 Managing a (Partially) Autonomic Network
>>>
>>> - Section 7.6 APIs: this section are too abstract for me, I just
>>> couldn’t really get the point. It seems like a general design
>>> pattern rather than specific mechanisms related to autonomic networks.
>>>
>> I agree with you, it is fairly generic. At the same time it provides
>> some context to the APIs we use, and it's clearly marked with a (*) as
>> being phase 2. I suggest we leave it in. If folks feel strongly, I
>> think we could take out the entire section. For now I leave it.
> [Sheng] I think Section 7.6 (APIs) is related to drfat-ietf-anima-grasp-api, I couldn't exactly tell whether the GRASP API design consists with the design principles described in this section.
> If this section doesn't mean that API related work "MUST" follow the design principles, I'd suggest to add a sentence to clarify it.

Good point. I'll add that point. I think this should not stop us from 
proceeding with the IESG review, we can add that later. Can we progress 
the doc now?

thanks,
Michael

>
> Regards,
>
> Sheng
>
>>> - Section 7.7 Data Model has the similar issue as above. It explains
>>> the concept but lacks essential content related to ANI.
>>>
>> Dito. I suggest to leave it for now.
>>
>> [end of reply]
>>
>>> Thanks and regards,
>>>
>>> Sheng
>>>
>>> *From:*Anima [mailto:anima-bounces@ietf.org] *On Behalf Of *Sheng
>>> Jiang
>>> *Sent:* Tuesday, January 09, 2018 2:26 PM
>>> *To:* anima@ietf.org
>>> *Cc:* anima-chairs@ietf.org
>>> *Subject:* [Anima] WGLC on draft-ietf-anima-reference-model-05 -
>>> Respond by January 22nd, 2018
>>>
>>> Hi all,
>>>
>>> This message starts the two-week ANIMA Working Group Last Call to
>>> advance draft-ietf-anima-reference-model-05, A Reference Model for
>>> Autonomic Networking. This document's intended status is
>>> Informational. At present, there is no IPR file against this document.
>>>
>>> Please send your comments by January 22nd, 2018. If you do not feel
>>> this document should advance, please state your reasons why.
>>>
>>> Sheng JIANG is the assigned document shepherd.
>>>
>>> Regards,
>>>
>>> Sheng (co-chair, Toerless who as a co-author stayed neutral on the
>>> content side)
>>>
>>>
>>>
>>> _______________________________________________
>>> Anima mailing list
>>> Anima@ietf.org
>>> https://www.ietf.org/mailman/listinfo/anima
>> _______________________________________________
>> Anima mailing list
>> Anima@ietf.org
>> https://www.ietf.org/mailman/listinfo/anima


From nobody Tue Mar  6 17:56:27 2018
Return-Path: <jiangsheng@huawei.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F49A126BF7 for <anima@ietfa.amsl.com>; Tue,  6 Mar 2018 17:56:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.23
X-Spam-Level: 
X-Spam-Status: No, score=-4.23 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 MFCQ4lrzvYsL for <anima@ietfa.amsl.com>; Tue,  6 Mar 2018 17:56:25 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB6BF124BAC for <anima@ietf.org>; Tue,  6 Mar 2018 17:56:24 -0800 (PST)
Received: from lhreml703-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 59A2EFA9594D6 for <anima@ietf.org>; Wed,  7 Mar 2018 01:56:20 +0000 (GMT)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.382.0; Wed, 7 Mar 2018 01:56:21 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0361.001; Wed, 7 Mar 2018 09:56:14 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "Michael H. Behringer" <michael.h.behringer@gmail.com>, "anima@ietf.org" <anima@ietf.org>
Thread-Topic: [Anima] Call for agenda ANIMA @ IETF 101, London
Thread-Index: AdOwWGKd4RIaPzDgQiCbL7FRUiUiwgE8OCuAABtF9SA=
Date: Wed, 7 Mar 2018 01:56:13 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B9281835212@NKGEML515-MBX.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B928182F916@NKGEML515-MBX.china.huawei.com> <3b62e2d2-c8d7-a9d9-1bd3-08758a02e8b1@gmail.com>
In-Reply-To: <3b62e2d2-c8d7-a9d9-1bd3-08758a02e8b1@gmail.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.45.21.135]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/s4lD9_hiR8CSQoChwlXlaA4KiOs>
Subject: Re: [Anima] Call for agenda ANIMA @ IETF 101, London
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2018 01:56:26 -0000

SGksIE1pY2hhZWwsDQoNCkV2ZW4gdGhlIGRyYWZ0IHdvdWxkIGJlIHdpdGggSUVURiwgaXQgaXMg
bmVlZGVkIHRvIHJlcG9ydCB0aGUgY2hhbmdlcyB0byBXRyBzaW5jZSB0aGUgbGFzdCByZXBvcnQu
IDEwIG1pbnMgaXMgZmluZSwgcmVtb3RlIHJlcG9ydCBpcyBmaW5lLCB0b28uDQoNClJlZ2FyZHMs
DQoNClNoZW5nDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBBbmltYSBbbWFp
bHRvOmFuaW1hLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBNaWNoYWVsIEguIEJlaHJp
bmdlcg0KU2VudDogV2VkbmVzZGF5LCBNYXJjaCA3LCAyMDE4IDQ6NDcgQU0NClRvOiBhbmltYUBp
ZXRmLm9yZw0KU3ViamVjdDogUmU6IFtBbmltYV0gQ2FsbCBmb3IgYWdlbmRhIEFOSU1BIEAgSUVU
RiAxMDEsIExvbmRvbg0KDQpIaSBTaGVuZywNCg0KTm90IHN1cmUgd2UgbmVlZCBhIHNsb3QgZm9y
IHRoZSByZWZlcmVuY2UgbW9kZWwuIEkgZ3Vlc3MgaXQgc2hvdWxkIG5vdyBnbyB0byB0aGUgSUVT
RywgcmlnaHQ/DQoNClVwIHRvIHlvdS4gSWYgd2UgaGF2ZSB0aW1lLCBJIGNvdWxkIGRvIGEgc2hv
cnQgMTAgbWluIHVwZGF0ZS4gSSB3b24ndCBiZSBpbiBwZXJzb24gaW4gTG9uZG9uLCBidXQgY2Fu
IHByZXNlbnQgcmVtb3RlbHkuDQoNCk1pY2hhZWwNCg0KDQpPbiAyOC8wMi8xOCAwNjo1NiwgU2hl
bmcgSmlhbmcgd3JvdGU6DQo+IEhpLCBhbGwgYW5pbWEsDQo+IFdlIGhhdmUgYmVlbiBhbGxvY2F0
ZWQgYSBzZXNzaW9uIG9mIDIuNS1ob3VyIGZvciB0aGUgQU5JTUEgV0cgbWVldGluZyANCj4gZm9y
IElFVEYtMTAxIChMb25kb24pIGFuZCBhcmUgc3RhcnRpbmcgdG8gY29sbGVjdCBhZ2VuZGEgaXRl
bXMgZm9yIHRoZSANCj4gc2Vzc2lvbi4gUGxlYXNlIHNlbmQgeW91ciByZXF1ZXN0IGZvciBhZ2Vu
ZGEgYnkgTWFyY2ggOHRoLCBUaHVyc2RheS4NCj4gR2l2aW5nIHRoYXQgbW9zdCBvZiBvdXIgY2hh
cnRlcmVkIHdvcmsgaXRlbXMgaGF2ZSBiZWVuIHNlbnQgdG8gSUVTRyANCj4gZm9yIHB1YmxpY2F0
aW9uIGJ5IHRoZSBtZWV0aW5nLCB3ZSBleHBlY3Qgc2hvcnQgdGltZSBzbG90cyBmb3Igb25seSAN
Cj4gdHdvIG9yIHRocmVlIG9mIHRoZW0uIEZvciB0aGlzIGNvbWluZyBtZWV0aW5nLCB3ZSB3b3Vs
ZCBsaWtlIHRvIA0KPiBkaXNjdXNzIHBvdGVudGlhbCBmdXR1cmUgQU5JTUEgd29ya3MuDQo+IEFz
IG5vcm1hbCwgdGhlIHByaW9yaXR5IGFtb25nIHRoZXNlIG5vbi1jaGFydGVyIHdvcmsgaXRlbXMg
d291bGQgYmU6IA0KPiB0aGVzZSB0aGF0IGhhdmUgYWN0aXZlIGRpc2N1c3Npb24gaW4gbWFpbCBs
aXN0LCB0aGVuIHRoZXNlIGhhdmUgDQo+IHN1Ym1pdHRlZCBkcmFmdHMsIGFuZCB0b3BpY3Mgd2l0
aG91dCBkcmFmdHMuDQo+IFBsZWFzZSBzZW5kIHVzIChhbmltYS1jaGFpcnMgYXQgaWV0Zi5vcmc8
aHR0cHM6Ly9pZXRmLm9yZy8+DQo+IDxodHRwOi8vaWV0Zi5vcmclM0NodHRwcy9pZXRmLm9yZy8l
M0UlMjk+OykgcmVxdWVzdHMgZm9yIHRpbWUgc2xvdCBieSANCj4gTWFyY2ggOHRoLCBUaHVyc2Rh
eSBhbmQgaW5jbHVkZToNCj4gTmFtZSBvZiB0aW1lIHNsb3Q6DQo+IE5hbWUgb2YgZHJhZnQocyk6
DQo+IFRpbWUgcmVxdWVzdGVkOg0KPiBQcmVzZW50ZXIgbmFtZShzKToNCj4gTW9yZSBkZXRhaWxz
IGFib3V0IHRoZSBJRVRGIDEwMSwgTG9uZG9uIGNhbiBiZSBmb3VuZCBhdDoNCj4gaHR0cDovL3d3
dy5pZXRmLm9yZy9tZWV0aW5nLzEwMS9pbmRleC5odG1sDQo+IEFnYWluLCBwcmVzZW50ZXJzIGFu
ZCBkcmFmdCBhdXRob3JzIHBsZWFzZSBpbnZva2UgYWN0aXZlIGRpc2N1c3Npb25zIA0KPiBpbiB0
aGUgQU5JTUEgbGlzdC4gTWFpbCBsaXN0IGlzIGEgdmVyeSBnb29kIHBsYWNlIHRvIGRpc2N1c3Mg
YW5kIHJlYWNoIA0KPiBjb25zZW5zdXMgb24gdGVjaG5pY2FsIGlzc3Vlcy4NCj4gQmVzdCByZWdh
cmRzLA0KPiBUb2VybGVzcyAmIFNoZW5nDQo+DQo+DQo+DQo+IF9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IEFuaW1hIG1haWxpbmcgbGlzdA0KPiBBbmlt
YUBpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2FuaW1h
DQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpBbmlt
YSBtYWlsaW5nIGxpc3QNCkFuaW1hQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2FuaW1hDQo=


From nobody Wed Mar  7 00:20:15 2018
Return-Path: <michael.h.behringer@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51F97126C89 for <anima@ietfa.amsl.com>; Wed,  7 Mar 2018 00:20:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 DsPbm2PiZhN5 for <anima@ietfa.amsl.com>; Wed,  7 Mar 2018 00:20:11 -0800 (PST)
Received: from mail-wr0-x22c.google.com (mail-wr0-x22c.google.com [IPv6:2a00:1450:400c:c0c::22c]) (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 69CC3126CE8 for <anima@ietf.org>; Wed,  7 Mar 2018 00:20:11 -0800 (PST)
Received: by mail-wr0-x22c.google.com with SMTP id z12so1196451wrg.4 for <anima@ietf.org>; Wed, 07 Mar 2018 00:20:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=pXA4VJPo3rjz7DNC2NGb4/chqBWt+BLWQpEq56Nzmwk=; b=G5YDZUFSfC0qgOYKPix9epxuVxK6qsPg0X7CznU200Tq78M5IaD3eeNOUcR0dUrKr8 qw4zFRIvHliJUnWLPGP30MVJ82m6dY9YgPS6EQScv7jKw9mSNA0UJL/hYw/TgjukmkPv cgU0yKOXycPi1Ee1kJECnUswSnQwXBkE4b2u2CTnxO4Xfw5hJWT66zTExhpblPataIIH uBnbWHlAvEo21eWS/j/ZkZjaoDwUF6ejOuyRElyMQczslHf1VG3bpq5ECk2v9PB/S6Sf guX0IFBuLYQGUMPuBM6WB1/99687+1LKVuJI/TBk48yV3Vfx9GwsHDdrFOQTV9RiN0v+ CJ0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=pXA4VJPo3rjz7DNC2NGb4/chqBWt+BLWQpEq56Nzmwk=; b=JDU5lFVi0B7cOCpa+GBqy+HhcjN+7ZuuU93dqe7NgDG6j93upe9UQ9iJNAkAwfA2+a 1pwBtZDpYoWrSHYVmWqytcUEGojxLW1vZO3ogC/Hy9xIWd2bFMhLXBWS396BlDOuuP0v 2RlbYyL/rocRUQobJOaz5b30uwW4QcYQ/+N5G+LEDhB+LKb+lN26IQEgq9xr7oajqwyK 3CGovHfeUYSVimJ3SsqVDxasjXJtSgcfPfd/TPRUYotdw2Ioz5kMxRKtgjyZni4itpsM iRMJ8w3tAe+tppuI30Rw41tCkv9LcHEDJa0JcVFZ+ShiGrgs6XQ1PtG/Id6U5deZGM+h aF/Q==
X-Gm-Message-State: APf1xPC0aDPZZCQgdeQyYbyprMlt2jg6j5mS/5bJHnt3G1P2g4LsU/YJ 72hFLMLV2z9I+mE6orS4F0Ek+6oL
X-Google-Smtp-Source: AG47ELtwAzoleN2JOseo0gXOEQrJLG1KlxvoAwaNCUL5VoJrzK6VhFLCJY5H+psDtFcH2gB00DXO1g==
X-Received: by 10.223.130.194 with SMTP id 60mr19489845wrc.209.1520410809746;  Wed, 07 Mar 2018 00:20:09 -0800 (PST)
Received: from [192.168.1.29] (ANice-652-1-18-241.w83-201.abo.wanadoo.fr. [83.201.29.241]) by smtp.gmail.com with ESMTPSA id q74sm14192198wmg.11.2018.03.07.00.20.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 07 Mar 2018 00:20:09 -0800 (PST)
From: "Michael H. Behringer" <michael.h.behringer@gmail.com>
X-Google-Original-From: "Michael H. Behringer" <Michael.H.Behringer@gmail.com>
To: Sheng Jiang <jiangsheng@huawei.com>, "anima@ietf.org" <anima@ietf.org>
References: <5D36713D8A4E7348A7E10DF7437A4B928182F916@NKGEML515-MBX.china.huawei.com> <3b62e2d2-c8d7-a9d9-1bd3-08758a02e8b1@gmail.com> <5D36713D8A4E7348A7E10DF7437A4B9281835212@NKGEML515-MBX.china.huawei.com>
Message-ID: <07d68363-389e-7727-7c38-972b7ecce021@gmail.com>
Date: Wed, 7 Mar 2018 09:20:08 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B9281835212@NKGEML515-MBX.china.huawei.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: fr-classic
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/WfQ8pYWriE-igtlIFW_tP0TKAns>
Subject: Re: [Anima] Call for agenda ANIMA @ IETF 101, London
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2018 08:20:13 -0000

OK - will do it :-)

On 07/03/18 02:56, Sheng Jiang wrote:
> Hi, Michael,
>
> Even the draft would be with IETF, it is needed to report the changes to WG since the last report. 10 mins is fine, remote report is fine, too.
>
> Regards,
>
> Sheng
>
> -----Original Message-----
> From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Michael H. Behringer
> Sent: Wednesday, March 7, 2018 4:47 AM
> To: anima@ietf.org
> Subject: Re: [Anima] Call for agenda ANIMA @ IETF 101, London
>
> Hi Sheng,
>
> Not sure we need a slot for the reference model. I guess it should now go to the IESG, right?
>
> Up to you. If we have time, I could do a short 10 min update. I won't be in person in London, but can present remotely.
>
> Michael
>
>
> On 28/02/18 06:56, Sheng Jiang wrote:
>> Hi, all anima,
>> We have been allocated a session of 2.5-hour for the ANIMA WG meeting
>> for IETF-101 (London) and are starting to collect agenda items for the
>> session. Please send your request for agenda by March 8th, Thursday.
>> Giving that most of our chartered work items have been sent to IESG
>> for publication by the meeting, we expect short time slots for only
>> two or three of them. For this coming meeting, we would like to
>> discuss potential future ANIMA works.
>> As normal, the priority among these non-charter work items would be:
>> these that have active discussion in mail list, then these have
>> submitted drafts, and topics without drafts.
>> Please send us (anima-chairs at ietf.org<https://ietf.org/>
>> <http://ietf.org%3Chttps/ietf.org/%3E%29>;) requests for time slot by
>> March 8th, Thursday and include:
>> Name of time slot:
>> Name of draft(s):
>> Time requested:
>> Presenter name(s):
>> More details about the IETF 101, London can be found at:
>> http://www.ietf.org/meeting/101/index.html
>> Again, presenters and draft authors please invoke active discussions
>> in the ANIMA list. Mail list is a very good place to discuss and reach
>> consensus on technical issues.
>> Best regards,
>> Toerless & Sheng
>>
>>
>>
>> _______________________________________________
>> Anima mailing list
>> Anima@ietf.org
>> https://www.ietf.org/mailman/listinfo/anima
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima


From nobody Wed Mar  7 19:44:53 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83315126BF7 for <anima@ietfa.amsl.com>; Wed,  7 Mar 2018 19:44:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 1ArD9hiUsGYp for <anima@ietfa.amsl.com>; Wed,  7 Mar 2018 19:44:50 -0800 (PST)
Received: from mail-pg0-x236.google.com (mail-pg0-x236.google.com [IPv6:2607:f8b0:400e:c05::236]) (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 BC6041271FD for <anima@ietf.org>; Wed,  7 Mar 2018 19:44:50 -0800 (PST)
Received: by mail-pg0-x236.google.com with SMTP id l131so1762579pga.2 for <anima@ietf.org>; Wed, 07 Mar 2018 19:44:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=hP9QCQo9G0QtrIjDh4yHhQLoyUyX1SDmZggX+Dq+RNY=; b=M2gpykUh4TgcjKwSKBZP50Gtk3nGqAWNlB+S4PfvyWSI3bcXG1ID1TzXKBRq8A70Vx Vi7tBJXrSQqK65TsJR2/pGNDQuhwpqxODhCMMnLbz2CT0yy4zRZ3dDL52x12AhoZ+14C Jbc/DBPAhz3H+63QfPoa80yGHHaH86mq+nHvtjy1J0zqw4b65pA103dt2tBus5Cd0B+q Umva8YISBAwgl36rJwACEZSGB8A5R6F+cM6Vn7BYkyfMv8kAm9TeNtW5Q9Z7ZfDIHuTX BDBi7hxU3chEJSPF5fAY6MAhYES6bQvbd5xGOGoAZf60oZWmlr2IlWkHbR30V3+O4eg+ 6RUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=hP9QCQo9G0QtrIjDh4yHhQLoyUyX1SDmZggX+Dq+RNY=; b=V9YAMfL718Pawxm17h2PjHm39kORI+GyEBggKFoiZKcSMk1g1EQXIPb5///pEDLMd9 +7u6XAdFEghgSaEHWikeR7YrNkWY4El3jwWi3ffGm8KqxOJA61McgmhoIkv9DuXZkmH+ lHDOH1UjI6nl9KkvaD1/P/dXH1afr1NnrMM5osHHGvmfiF3a8dhG/qDjRRy+Gb09FtJ7 BHy43+MozyB9q7L/7RPlv4PSjvLo/cRen3bBxLJS8JE5c66c7S927EheVBs5fZiLEbVT xcraMe5mUXOIZfiXHeys4qbwehfEWc/RQYljFA2ze4HP33R4EPu/jQzSwYhXUWE6FQP1 0z+A==
X-Gm-Message-State: APf1xPBOs5HqmaxVg0FFlueBcJd+nktvIpdAOITvYofBUaYicrv8ARZ0 kQa7mrACnbCiNqq/TojMRZ+HHHu6
X-Google-Smtp-Source: AG47ELuGfP2AZUk7odzwV90fOvcb78utamFeAsG6ogBBHbSUoo7dAGYVsYr0uZMSP+NFhPLiIOxUDQ==
X-Received: by 10.99.191.15 with SMTP id v15mr19984863pgf.396.1520480690029; Wed, 07 Mar 2018 19:44:50 -0800 (PST)
Received: from [192.168.178.30] ([118.148.71.2]) by smtp.gmail.com with ESMTPSA id m1sm14576133pfi.80.2018.03.07.19.44.48 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 07 Mar 2018 19:44:49 -0800 (PST)
Sender: Brian Carpenter <becarpenter46@gmail.com>
To: Anima WG <anima@ietf.org>
References: <152028986381.12884.9092671195107327813@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <7bc91acd-0c31-4d52-16d9-41aeaf8808d2@gmail.com>
Date: Thu, 8 Mar 2018 16:44:52 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <152028986381.12884.9092671195107327813@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/Hi_XqiXtnd7lJZ48VFl4URDia6c>
Subject: [Anima] BRSKI discovery implementation report [I-D Action: draft-ietf-anima-bootstrapping-keyinfra-12.txt]
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2018 03:44:52 -0000

Hi,

I have aligned my Python demos** of the BRSKI discovery mechanisms with the -12 draft.
Here are dumps of the received flood messages, with discussion:

(1) Flood sent by the registrar as received by the proxy. This is Python output
(so the b'...' strings are hexdumps of bytes objects.)

[9, 1729214102, b'2406e00741ec000128ccdc4c97036781', 120000, [['AN_join_registrar', 5, 255, 'EST-TLS'], [103, b'2406e00741ec000128ccdc4c97036781', 6, 80]]]

Nothing serious to report here. Since the draft only defines the 'EST-TLS'
form, I haven't included any alternatives. My code could also handle announcing
IP-in-IP for example. 

Compare to the example in the draft:

   [M_FLOOD, 12340815, h'fda379a6f6ee00000200000064000001', 180000,
               ["AN_join_registrar", 4, 255, "EST-TLS"],
               [O_IPv6_LOCATOR,
                    h'fda379a6f6ee00000200000064000001', TCP, 80]]

I'd prefer to see TCP represented as IPPROTO_TCP to align with the GRASP spec.
The other differences are unimportant (my network has global IPv6 addresses
instead of ULAs, I set the 'discoverable' flag bit, and I used a different timeout).

(2) Flood sent by the proxy as received by the pledge, also Python output.

[9, 160559994, b'2406e00741ec000128ccdc4c97036781', 180000, [['AN_proxy', 5, 1, ''], [103, b'fe8000000000000028ccdc4c97036781', 6, 11805]]] 

Compare to the example in the draft:

   [M_FLOOD, 12340815, h'fe800000000000000000000000000001', 180000,
               ["AN_Proxy", 4, 1, ""],
               [O_IPv6_LOCATOR,
                    h'fe800000000000000000000000000001', 'TCP', 4443]]

Several comments:

1. The 3rd element is the 'initiator' address. The draft shows that as
a link-local. It doesn't matter too much, but my code uses a routeable
address. It's only there for disambiguation in a multi-hop flood,
which doesn't apply in this case. The address that matters is the second
one, in the locator. The packet itself is sent link-local.

2. 'TCP' shouldn't be a string, it should be IPPROTO_TCP as above.

3. The objective is defined as having a null value. Why isn't it
"EST-TLS" again?

** Code at https://github.com/becarpenter/graspy (Reggie.py, Procksy.py, Pledji.py)

Regards
   Brian


From nobody Mon Mar 12 15:42:09 2018
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5951127010; Mon, 12 Mar 2018 15:42:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.96
X-Spam-Level: 
X-Spam-Status: No, score=-3.96 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 DZx9fljB0vKJ; Mon, 12 Mar 2018 15:42:05 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A13E812702E; Mon, 12 Mar 2018 15:42:05 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 676C358C503; Mon, 12 Mar 2018 23:42:01 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4C654B0DCEB; Mon, 12 Mar 2018 23:42:01 +0100 (CET)
Date: Mon, 12 Mar 2018 23:42:01 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Sheng Jiang <jiangsheng@huawei.com>, "anima@ietf.org" <anima@ietf.org>, anima-chairs <anima-chairs@ietf.org>
Message-ID: <20180312224201.GA30866@faui40p.informatik.uni-erlangen.de>
References: <5D36713D8A4E7348A7E10DF7437A4B928182F916@NKGEML515-MBX.china.huawei.com> <e022e30e-ae95-ceea-1db1-eff55ce0d677@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <e022e30e-ae95-ceea-1db1-eff55ce0d677@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/0TvoxpDHOuvvJqVO-XInyH5epDI>
Subject: Re: [Anima] Call for agenda ANIMA @ IETF 101, London
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Mar 2018 22:42:08 -0000

Thanks, Brian

Let me know if you need a presenter, we can sync up in before
and i could present on your behalf if we do not find someone better.

Cheers
    Toerless

On Thu, Mar 01, 2018 at 02:02:37PM +1300, Brian E Carpenter wrote:
> There will be updates of these three drafts by the deadline:
> draft-ietf-anima-grasp-api
> draft-carpenter-anima-asa-guidelines
> draft-carpenter-anima-grasp-bulk
> 
> Since there are few major changes, a short slot for each is sufficient.
> Perhaps 10 minutes for asa-guidelines as there is a new example logic
> flow to describe, and 5 minutes each for the other two.
> 
> Presenters TBD. Because of the time difference, I cannot promise to
> be on MeetEcho.
> 
> Regards
>    Brian
> 
> On 28/02/2018 18:56, Sheng Jiang wrote:
> > Hi, all anima,
> > 
> > 
> > 
> > We have been allocated a session of 2.5-hour for the ANIMA WG meeting for IETF-101 (London) and are starting to collect agenda items for the session. Please send your request for agenda by March 8th, Thursday.
> > 
> > 
> > 
> > Giving that most of our chartered work items have been sent to IESG for publication by the meeting, we expect short time slots for only two or three of them. For this coming meeting, we would like to discuss potential future ANIMA works.
> > 
> > 
> > 
> > As normal, the priority among these non-charter work items would be: these that have active discussion in mail list, then these have submitted drafts, and topics without drafts.
> > 
> > 
> > 
> > Please send us (anima-chairs at ietf.org<https://ietf.org/><http://ietf.org%3Chttps/ietf.org/%3E)>;) requests for time slot by March 8th, Thursday and include:
> > 
> > Name of time slot:
> > 
> > Name of draft(s):
> > 
> > Time requested:
> > 
> > Presenter name(s):
> > 
> > 
> > 
> > More details about the IETF 101, London can be found at:
> > 
> > 
> > 
> > http://www.ietf.org/meeting/101/index.html
> > 
> > 
> > 
> > Again, presenters and draft authors please invoke active discussions in the ANIMA list. Mail list is a very good place to discuss and reach consensus on technical issues.
> > 
> > 
> > 
> > Best regards,
> > 
> > 
> > 
> > Toerless & Sheng
> > 
> > 
> > 
> > 
> > _______________________________________________
> > Anima mailing list
> > Anima@ietf.org
> > https://www.ietf.org/mailman/listinfo/anima
> > 

-- 
---
tte@cs.fau.de


From nobody Mon Mar 12 16:12:38 2018
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8ED9E126D74; Mon, 12 Mar 2018 16:12:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.96
X-Spam-Level: 
X-Spam-Status: No, score=-3.96 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 BJ1dKU7cTsIW; Mon, 12 Mar 2018 16:12:35 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2ED4124BFA; Mon, 12 Mar 2018 16:12:35 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 7024058C503; Tue, 13 Mar 2018 00:12:31 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 57275B0DCEC; Tue, 13 Mar 2018 00:12:31 +0100 (CET)
Date: Tue, 13 Mar 2018 00:12:31 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Sheng Jiang <jiangsheng@huawei.com>
Cc: "anima@ietf.org" <anima@ietf.org>, anima-chairs <anima-chairs@ietf.org>
Message-ID: <20180312231231.GB30866@faui40p.informatik.uni-erlangen.de>
References: <5D36713D8A4E7348A7E10DF7437A4B928182F916@NKGEML515-MBX.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B928182F916@NKGEML515-MBX.china.huawei.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/Wu7j5kNNC5I3afQbHBBMVYCkDQ8>
Subject: Re: [Anima] Call for agenda ANIMA @ IETF 101, London
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Mar 2018 23:12:37 -0000

Hi Sheng,

Not that many actual new draft/work-items, but lots of activity going
on, hee's what's on my contributor plate:

1. draft-ietf-anima-autonomic-control plane
  5 min IESG review update

2. draft-eckert-anima-grasp-dnssd
  <= 10 mins ?
  Update of feedback from DNS-SD WG @ IETF100 (happened after ANIMA@IETF100)
  and summary of implementation status from Brian.
  Want to ask for ANIMA WG adoption (in-charter, details that fell off BRSKI/ACP).

3. I also have a personal problem, but maybe if Max chimes in and can help,
  maybe this can also be a slot to discuss:

  I did contribute text about ANI/BRSKI to draft-nir-saag-star-01
  (just check difference between the -00 version, eas to identify the ANI text),
  outlining how ANI itself can benefit from short-lived certificates, but
  also how ANI could be a great infra to manage short-lived certificates.

  This was targeted for SAAG, but it ended up on tuesday, probably
  9:50 - 10:10 time slot in SECDISPATCH.
  
  If Max could go to secdispatch, and represent BRSKI/EST/ANI,
  that would be great, otherwise i would ask for 15 mins off from
  anima for myself.
  
  Maybe we can have at the end of the anima schedule a short slot
  to discuss possible extensions for short-lived certificates, e.g.:
  what would need to be defined on a standards doc. And whether or not
  this should be in ANIMA.

4. I did not manage to finish a -00 draft, but would very much like to
   find co-authors for a Yang model for ANI, so if there is anyone here
   interredsted in this, pls. ping me offline.

5. Alas, probably no RFC for ANIMA to report until IETF101. 
   draft-ietf-anima-stable-connectivity would have no dependencies to wait
   for, but its in RFC editor queue for 4 weeks, without feedback yet.
   As far as i was told, this is unfortunately normal before the spring meeting
   with all the leaving ADs prioritizing the stuff they wanted to get finished
   in the RFC editor queue, so wait time for RFC editor resources in this
   time slot is particularily long. (Voucher might be further along, but
   would have BRSKI dependency to wait for).

Cheers
    Toerless

On Wed, Feb 28, 2018 at 05:56:34AM +0000, Sheng Jiang wrote:
> Hi, all anima,
> 
> 
> 
> We have been allocated a session of 2.5-hour for the ANIMA WG meeting for IETF-101 (London) and are starting to collect agenda items for the session. Please send your request for agenda by March 8th, Thursday.
> 
> 
> 
> Giving that most of our chartered work items have been sent to IESG for publication by the meeting, we expect short time slots for only two or three of them. For this coming meeting, we would like to discuss potential future ANIMA works.
> 
> 
> 
> As normal, the priority among these non-charter work items would be: these that have active discussion in mail list, then these have submitted drafts, and topics without drafts.
> 
> 
> 
> Please send us (anima-chairs at ietf.org<https://ietf.org/><http://ietf.org%3Chttps/ietf.org/%3E)>;) requests for time slot by March 8th, Thursday and include:
> 
> Name of time slot:
> 
> Name of draft(s):
> 
> Time requested:
> 
> Presenter name(s):
> 
> 
> 
> More details about the IETF 101, London can be found at:
> 
> 
> 
> http://www.ietf.org/meeting/101/index.html
> 
> 
> 
> Again, presenters and draft authors please invoke active discussions in the ANIMA list. Mail list is a very good place to discuss and reach consensus on technical issues.
> 
> 
> 
> Best regards,
> 
> 
> 
> Toerless & Sheng
> 

> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima


-- 
---
tte@cs.fau.de


From nobody Mon Mar 12 16:21:33 2018
Return-Path: <pritikin@cisco.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBC47124F57; Mon, 12 Mar 2018 16:21:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level: 
X-Spam-Status: No, score=-14.531 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 5yaOkeR21V3G; Mon, 12 Mar 2018 16:21:30 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0727C124BFA; Mon, 12 Mar 2018 16:21:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5846; q=dns/txt; s=iport; t=1520896890; x=1522106490; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=towq2FQ2PHuiQYcKZQLRC3PdXtEVxLCkcxijZNXvEiY=; b=M+pN+kAt6qJUq2qJmwBxRlEXtUeUcepG4hbhujtHkCHzhz1kb6eGXaqw KhALI394PzyEUbk8TOj/oat+Suud7ps82kSgKwSb0ulvJkgFL/10edXSH hVI5RqqGkzAj35ei5WVnAN0J+0MyRHtbmVF2TPxWh/DpxbhHsirSvSUH7 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D6AADNCqda/4kNJK1TChkBAQEBAQEBA?= =?us-ascii?q?QEBAQEHAQEBAQGDIy1mbygKg0aKH41yggSBFpQyghUKGAuFAgIagwEhNBgBAgE?= =?us-ascii?q?BAQEBAQJrJ4UjAQEBAwEBARsGEToLBQsCAQgOCgICJgICAiULFRABAQQOBQmFB?= =?us-ascii?q?wgPq2uCJohjghWBDYQogi6DPCmBd4EOgUeBXAsBAQGBRQgDAQEegwgwgjIEjXK?= =?us-ascii?q?MZAkChkGGJIN8gWNOg2eDFYU0h3SCBYcoAhETAYErAR44gVJwFToqAYIYCYIpD?= =?us-ascii?q?BCBAwEGb3cBi1WBIoEYAQEB?=
X-IronPort-AV: E=Sophos;i="5.47,463,1515456000"; d="scan'208";a="83065168"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Mar 2018 23:21:29 +0000
Received: from XCH-ALN-014.cisco.com (xch-aln-014.cisco.com [173.36.7.24]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id w2CNLTM3022514 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 12 Mar 2018 23:21:29 GMT
Received: from xch-aln-013.cisco.com (173.36.7.23) by XCH-ALN-014.cisco.com (173.36.7.24) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 12 Mar 2018 18:21:28 -0500
Received: from xch-aln-013.cisco.com ([173.36.7.23]) by XCH-ALN-013.cisco.com ([173.36.7.23]) with mapi id 15.00.1320.000; Mon, 12 Mar 2018 18:21:28 -0500
From: "Max Pritikin (pritikin)" <pritikin@cisco.com>
To: Toerless Eckert <tte@cs.fau.de>
CC: Sheng Jiang <jiangsheng@huawei.com>, anima-chairs <anima-chairs@ietf.org>,  "anima@ietf.org" <anima@ietf.org>
Thread-Topic: [Anima] Call for agenda ANIMA @ IETF 101, London
Thread-Index: AdOwWGKd4RIaPzDgQiCbL7FRUiUiwgKKR7iAAABP34A=
Date: Mon, 12 Mar 2018 23:21:28 +0000
Message-ID: <A396CA6B-DFBF-4BBD-AACF-DCD51237574D@cisco.com>
References: <5D36713D8A4E7348A7E10DF7437A4B928182F916@NKGEML515-MBX.china.huawei.com> <20180312231231.GB30866@faui40p.informatik.uni-erlangen.de>
In-Reply-To: <20180312231231.GB30866@faui40p.informatik.uni-erlangen.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.155.124.56]
Content-Type: text/plain; charset="utf-8"
Content-ID: <1A7887D0AAF01D43983BA86B52D8BEB8@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/AgHyGqpKdffCm7tP8QgfeWh2ZTA>
Subject: Re: [Anima] Call for agenda ANIMA @ IETF 101, London
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Mar 2018 23:21:32 -0000

DQoNCj4gT24gTWFyIDEyLCAyMDE4LCBhdCA0OjEyIFBNLCBUb2VybGVzcyBFY2tlcnQgPHR0ZUBj
cy5mYXUuZGU+IHdyb3RlOg0KPiANCj4gDQo+IEhpIFNoZW5nLA0KPiANCj4gTm90IHRoYXQgbWFu
eSBhY3R1YWwgbmV3IGRyYWZ0L3dvcmstaXRlbXMsIGJ1dCBsb3RzIG9mIGFjdGl2aXR5IGdvaW5n
DQo+IG9uLCBoZWUncyB3aGF0J3Mgb24gbXkgY29udHJpYnV0b3IgcGxhdGU6DQo+IA0KPiAxLiBk
cmFmdC1pZXRmLWFuaW1hLWF1dG9ub21pYy1jb250cm9sIHBsYW5lDQo+ICA1IG1pbiBJRVNHIHJl
dmlldyB1cGRhdGUNCj4gDQo+IDIuIGRyYWZ0LWVja2VydC1hbmltYS1ncmFzcC1kbnNzZA0KPiAg
PD0gMTAgbWlucyA/DQo+ICBVcGRhdGUgb2YgZmVlZGJhY2sgZnJvbSBETlMtU0QgV0cgQCBJRVRG
MTAwIChoYXBwZW5lZCBhZnRlciBBTklNQUBJRVRGMTAwKQ0KPiAgYW5kIHN1bW1hcnkgb2YgaW1w
bGVtZW50YXRpb24gc3RhdHVzIGZyb20gQnJpYW4uDQo+ICBXYW50IHRvIGFzayBmb3IgQU5JTUEg
V0cgYWRvcHRpb24gKGluLWNoYXJ0ZXIsIGRldGFpbHMgdGhhdCBmZWxsIG9mZiBCUlNLSS9BQ1Ap
Lg0KPiANCj4gMy4gSSBhbHNvIGhhdmUgYSBwZXJzb25hbCBwcm9ibGVtLCBidXQgbWF5YmUgaWYg
TWF4IGNoaW1lcyBpbiBhbmQgY2FuIGhlbHAsDQo+ICBtYXliZSB0aGlzIGNhbiBhbHNvIGJlIGEg
c2xvdCB0byBkaXNjdXNzOg0KPiANCj4gIEkgZGlkIGNvbnRyaWJ1dGUgdGV4dCBhYm91dCBBTkkv
QlJTS0kgdG8gZHJhZnQtbmlyLXNhYWctc3Rhci0wMQ0KPiAgKGp1c3QgY2hlY2sgZGlmZmVyZW5j
ZSBiZXR3ZWVuIHRoZSAtMDAgdmVyc2lvbiwgZWFzIHRvIGlkZW50aWZ5IHRoZSBBTkkgdGV4dCks
DQo+ICBvdXRsaW5pbmcgaG93IEFOSSBpdHNlbGYgY2FuIGJlbmVmaXQgZnJvbSBzaG9ydC1saXZl
ZCBjZXJ0aWZpY2F0ZXMsIGJ1dA0KPiAgYWxzbyBob3cgQU5JIGNvdWxkIGJlIGEgZ3JlYXQgaW5m
cmEgdG8gbWFuYWdlIHNob3J0LWxpdmVkIGNlcnRpZmljYXRlcy4NCj4gDQo+ICBUaGlzIHdhcyB0
YXJnZXRlZCBmb3IgU0FBRywgYnV0IGl0IGVuZGVkIHVwIG9uIHR1ZXNkYXksIHByb2JhYmx5DQo+
ICA5OjUwIC0gMTA6MTAgdGltZSBzbG90IGluIFNFQ0RJU1BBVENILg0KPiANCj4gIElmIE1heCBj
b3VsZCBnbyB0byBzZWNkaXNwYXRjaCwgYW5kIHJlcHJlc2VudCBCUlNLSS9FU1QvQU5JLA0KPiAg
dGhhdCB3b3VsZCBiZSBncmVhdCwgb3RoZXJ3aXNlIGkgd291bGQgYXNrIGZvciAxNSBtaW5zIG9m
ZiBmcm9tDQo+ICBhbmltYSBmb3IgbXlzZWxmLg0KDQpJIGNhbiBnbyB0byB0aGlzICh3aWxsIGJl
IHRoZXJlIGluIHBlcnNvbikuIEnigJlsbCBoYXZlIHRvIHJlYWQgdGhlIGRyYWZ0IGFuZCBjb29y
ZGluYXRlIHdpdGggeW91IG9uIHByZXNlbnRhdGlvbiB0YWxraW5nLXBvaW50cywNCg0KLSBtYXgN
Cg0KPiANCj4gIE1heWJlIHdlIGNhbiBoYXZlIGF0IHRoZSBlbmQgb2YgdGhlIGFuaW1hIHNjaGVk
dWxlIGEgc2hvcnQgc2xvdA0KPiAgdG8gZGlzY3VzcyBwb3NzaWJsZSBleHRlbnNpb25zIGZvciBz
aG9ydC1saXZlZCBjZXJ0aWZpY2F0ZXMsIGUuZy46DQo+ICB3aGF0IHdvdWxkIG5lZWQgdG8gYmUg
ZGVmaW5lZCBvbiBhIHN0YW5kYXJkcyBkb2MuIEFuZCB3aGV0aGVyIG9yIG5vdA0KPiAgdGhpcyBz
aG91bGQgYmUgaW4gQU5JTUEuDQo+IA0KPiA0LiBJIGRpZCBub3QgbWFuYWdlIHRvIGZpbmlzaCBh
IC0wMCBkcmFmdCwgYnV0IHdvdWxkIHZlcnkgbXVjaCBsaWtlIHRvDQo+ICAgZmluZCBjby1hdXRo
b3JzIGZvciBhIFlhbmcgbW9kZWwgZm9yIEFOSSwgc28gaWYgdGhlcmUgaXMgYW55b25lIGhlcmUN
Cj4gICBpbnRlcnJlZHN0ZWQgaW4gdGhpcywgcGxzLiBwaW5nIG1lIG9mZmxpbmUuDQo+IA0KPiA1
LiBBbGFzLCBwcm9iYWJseSBubyBSRkMgZm9yIEFOSU1BIHRvIHJlcG9ydCB1bnRpbCBJRVRGMTAx
LiANCj4gICBkcmFmdC1pZXRmLWFuaW1hLXN0YWJsZS1jb25uZWN0aXZpdHkgd291bGQgaGF2ZSBu
byBkZXBlbmRlbmNpZXMgdG8gd2FpdA0KPiAgIGZvciwgYnV0IGl0cyBpbiBSRkMgZWRpdG9yIHF1
ZXVlIGZvciA0IHdlZWtzLCB3aXRob3V0IGZlZWRiYWNrIHlldC4NCj4gICBBcyBmYXIgYXMgaSB3
YXMgdG9sZCwgdGhpcyBpcyB1bmZvcnR1bmF0ZWx5IG5vcm1hbCBiZWZvcmUgdGhlIHNwcmluZyBt
ZWV0aW5nDQo+ICAgd2l0aCBhbGwgdGhlIGxlYXZpbmcgQURzIHByaW9yaXRpemluZyB0aGUgc3R1
ZmYgdGhleSB3YW50ZWQgdG8gZ2V0IGZpbmlzaGVkDQo+ICAgaW4gdGhlIFJGQyBlZGl0b3IgcXVl
dWUsIHNvIHdhaXQgdGltZSBmb3IgUkZDIGVkaXRvciByZXNvdXJjZXMgaW4gdGhpcw0KPiAgIHRp
bWUgc2xvdCBpcyBwYXJ0aWN1bGFyaWx5IGxvbmcuIChWb3VjaGVyIG1pZ2h0IGJlIGZ1cnRoZXIg
YWxvbmcsIGJ1dA0KPiAgIHdvdWxkIGhhdmUgQlJTS0kgZGVwZW5kZW5jeSB0byB3YWl0IGZvciku
DQo+IA0KPiBDaGVlcnMNCj4gICAgVG9lcmxlc3MNCj4gDQo+IE9uIFdlZCwgRmViIDI4LCAyMDE4
IGF0IDA1OjU2OjM0QU0gKzAwMDAsIFNoZW5nIEppYW5nIHdyb3RlOg0KPj4gSGksIGFsbCBhbmlt
YSwNCj4+IA0KPj4gDQo+PiANCj4+IFdlIGhhdmUgYmVlbiBhbGxvY2F0ZWQgYSBzZXNzaW9uIG9m
IDIuNS1ob3VyIGZvciB0aGUgQU5JTUEgV0cgbWVldGluZyBmb3IgSUVURi0xMDEgKExvbmRvbikg
YW5kIGFyZSBzdGFydGluZyB0byBjb2xsZWN0IGFnZW5kYSBpdGVtcyBmb3IgdGhlIHNlc3Npb24u
IFBsZWFzZSBzZW5kIHlvdXIgcmVxdWVzdCBmb3IgYWdlbmRhIGJ5IE1hcmNoIDh0aCwgVGh1cnNk
YXkuDQo+PiANCj4+IA0KPj4gDQo+PiBHaXZpbmcgdGhhdCBtb3N0IG9mIG91ciBjaGFydGVyZWQg
d29yayBpdGVtcyBoYXZlIGJlZW4gc2VudCB0byBJRVNHIGZvciBwdWJsaWNhdGlvbiBieSB0aGUg
bWVldGluZywgd2UgZXhwZWN0IHNob3J0IHRpbWUgc2xvdHMgZm9yIG9ubHkgdHdvIG9yIHRocmVl
IG9mIHRoZW0uIEZvciB0aGlzIGNvbWluZyBtZWV0aW5nLCB3ZSB3b3VsZCBsaWtlIHRvIGRpc2N1
c3MgcG90ZW50aWFsIGZ1dHVyZSBBTklNQSB3b3Jrcy4NCj4+IA0KPj4gDQo+PiANCj4+IEFzIG5v
cm1hbCwgdGhlIHByaW9yaXR5IGFtb25nIHRoZXNlIG5vbi1jaGFydGVyIHdvcmsgaXRlbXMgd291
bGQgYmU6IHRoZXNlIHRoYXQgaGF2ZSBhY3RpdmUgZGlzY3Vzc2lvbiBpbiBtYWlsIGxpc3QsIHRo
ZW4gdGhlc2UgaGF2ZSBzdWJtaXR0ZWQgZHJhZnRzLCBhbmQgdG9waWNzIHdpdGhvdXQgZHJhZnRz
Lg0KPj4gDQo+PiANCj4+IA0KPj4gUGxlYXNlIHNlbmQgdXMgKGFuaW1hLWNoYWlycyBhdCBpZXRm
Lm9yZzxodHRwczovL2lldGYub3JnLz48aHR0cDovL2lldGYub3JnJTNDaHR0cHMvaWV0Zi5vcmcv
JTNFKT47KSByZXF1ZXN0cyBmb3IgdGltZSBzbG90IGJ5IE1hcmNoIDh0aCwgVGh1cnNkYXkgYW5k
IGluY2x1ZGU6DQo+PiANCj4+IE5hbWUgb2YgdGltZSBzbG90Og0KPj4gDQo+PiBOYW1lIG9mIGRy
YWZ0KHMpOg0KPj4gDQo+PiBUaW1lIHJlcXVlc3RlZDoNCj4+IA0KPj4gUHJlc2VudGVyIG5hbWUo
cyk6DQo+PiANCj4+IA0KPj4gDQo+PiBNb3JlIGRldGFpbHMgYWJvdXQgdGhlIElFVEYgMTAxLCBM
b25kb24gY2FuIGJlIGZvdW5kIGF0Og0KPj4gDQo+PiANCj4+IA0KPj4gaHR0cDovL3d3dy5pZXRm
Lm9yZy9tZWV0aW5nLzEwMS9pbmRleC5odG1sDQo+PiANCj4+IA0KPj4gDQo+PiBBZ2FpbiwgcHJl
c2VudGVycyBhbmQgZHJhZnQgYXV0aG9ycyBwbGVhc2UgaW52b2tlIGFjdGl2ZSBkaXNjdXNzaW9u
cyBpbiB0aGUgQU5JTUEgbGlzdC4gTWFpbCBsaXN0IGlzIGEgdmVyeSBnb29kIHBsYWNlIHRvIGRp
c2N1c3MgYW5kIHJlYWNoIGNvbnNlbnN1cyBvbiB0ZWNobmljYWwgaXNzdWVzLg0KPj4gDQo+PiAN
Cj4+IA0KPj4gQmVzdCByZWdhcmRzLA0KPj4gDQo+PiANCj4+IA0KPj4gVG9lcmxlc3MgJiBTaGVu
Zw0KPj4gDQo+IA0KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCj4+IEFuaW1hIG1haWxpbmcgbGlzdA0KPj4gQW5pbWFAaWV0Zi5vcmcNCj4+IGh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vYW5pbWENCj4gDQo+IA0KPiAtLSANCj4g
LS0tDQo+IHR0ZUBjcy5mYXUuZGUNCj4gDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQo+IEFuaW1hIG1haWxpbmcgbGlzdA0KPiBBbmltYUBpZXRmLm9y
Zw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2FuaW1hDQoNCg==


From nobody Mon Mar 12 18:20:26 2018
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7808E126B6D; Mon, 12 Mar 2018 18:20:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.959
X-Spam-Level: 
X-Spam-Status: No, score=-3.959 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 bQV8iUishPO0; Mon, 12 Mar 2018 18:20:23 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E35D712704A; Mon, 12 Mar 2018 18:20:22 -0700 (PDT)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id DC59C58C503; Tue, 13 Mar 2018 02:20:17 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id BE1E3B0DCF2; Tue, 13 Mar 2018 02:20:17 +0100 (CET)
Date: Tue, 13 Mar 2018 02:20:17 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: "Max Pritikin (pritikin)" <pritikin@cisco.com>
Cc: Sheng Jiang <jiangsheng@huawei.com>, anima-chairs <anima-chairs@ietf.org>,  "anima@ietf.org" <anima@ietf.org>
Message-ID: <20180313012017.GC30866@faui40p.informatik.uni-erlangen.de>
References: <5D36713D8A4E7348A7E10DF7437A4B928182F916@NKGEML515-MBX.china.huawei.com> <20180312231231.GB30866@faui40p.informatik.uni-erlangen.de> <A396CA6B-DFBF-4BBD-AACF-DCD51237574D@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <A396CA6B-DFBF-4BBD-AACF-DCD51237574D@cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/xwDpY2pI9PoxuGDKaa5dS3h0scA>
Subject: Re: [Anima] Call for agenda ANIMA @ IETF 101, London
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2018 01:20:25 -0000

Thanks, Max.

We'll coordinate. The presentation at secdispatch will be given by
Nir, but i'd hope you can be on stage for the Q&A, especially re
either ANI/BRSKI or the logic of split horizon for the interpretation
of the short lived cert - use by apps vs. use by renewal procedures.
Thats i think the core.

And we should then ask for a 5 min slot at end of anima, so maybe you
can report back from secdispatch.

Cheers
   Toerless

On Mon, Mar 12, 2018 at 11:21:28PM +0000, Max Pritikin (pritikin) wrote:
> 
> 
> > On Mar 12, 2018, at 4:12 PM, Toerless Eckert <tte@cs.fau.de> wrote:
> > 
> > 
> > Hi Sheng,
> > 
> > Not that many actual new draft/work-items, but lots of activity going
> > on, hee's what's on my contributor plate:
> > 
> > 1. draft-ietf-anima-autonomic-control plane
> >  5 min IESG review update
> > 
> > 2. draft-eckert-anima-grasp-dnssd
> >  <= 10 mins ?
> >  Update of feedback from DNS-SD WG @ IETF100 (happened after ANIMA@IETF100)
> >  and summary of implementation status from Brian.
> >  Want to ask for ANIMA WG adoption (in-charter, details that fell off BRSKI/ACP).
> > 
> > 3. I also have a personal problem, but maybe if Max chimes in and can help,
> >  maybe this can also be a slot to discuss:
> > 
> >  I did contribute text about ANI/BRSKI to draft-nir-saag-star-01
> >  (just check difference between the -00 version, eas to identify the ANI text),
> >  outlining how ANI itself can benefit from short-lived certificates, but
> >  also how ANI could be a great infra to manage short-lived certificates.
> > 
> >  This was targeted for SAAG, but it ended up on tuesday, probably
> >  9:50 - 10:10 time slot in SECDISPATCH.
> > 
> >  If Max could go to secdispatch, and represent BRSKI/EST/ANI,
> >  that would be great, otherwise i would ask for 15 mins off from
> >  anima for myself.
> 
> I can go to this (will be there in person). I???ll have to read the draft and coordinate with you on presentation talking-points,
> 
> - max
> 
> > 
> >  Maybe we can have at the end of the anima schedule a short slot
> >  to discuss possible extensions for short-lived certificates, e.g.:
> >  what would need to be defined on a standards doc. And whether or not
> >  this should be in ANIMA.
> > 
> > 4. I did not manage to finish a -00 draft, but would very much like to
> >   find co-authors for a Yang model for ANI, so if there is anyone here
> >   interredsted in this, pls. ping me offline.
> > 
> > 5. Alas, probably no RFC for ANIMA to report until IETF101. 
> >   draft-ietf-anima-stable-connectivity would have no dependencies to wait
> >   for, but its in RFC editor queue for 4 weeks, without feedback yet.
> >   As far as i was told, this is unfortunately normal before the spring meeting
> >   with all the leaving ADs prioritizing the stuff they wanted to get finished
> >   in the RFC editor queue, so wait time for RFC editor resources in this
> >   time slot is particularily long. (Voucher might be further along, but
> >   would have BRSKI dependency to wait for).
> > 
> > Cheers
> >    Toerless
> > 
> > On Wed, Feb 28, 2018 at 05:56:34AM +0000, Sheng Jiang wrote:
> >> Hi, all anima,
> >> 
> >> 
> >> 
> >> We have been allocated a session of 2.5-hour for the ANIMA WG meeting for IETF-101 (London) and are starting to collect agenda items for the session. Please send your request for agenda by March 8th, Thursday.
> >> 
> >> 
> >> 
> >> Giving that most of our chartered work items have been sent to IESG for publication by the meeting, we expect short time slots for only two or three of them. For this coming meeting, we would like to discuss potential future ANIMA works.
> >> 
> >> 
> >> 
> >> As normal, the priority among these non-charter work items would be: these that have active discussion in mail list, then these have submitted drafts, and topics without drafts.
> >> 
> >> 
> >> 
> >> Please send us (anima-chairs at ietf.org<https://ietf.org/><http://ietf.org%3Chttps/ietf.org/%3E)>;) requests for time slot by March 8th, Thursday and include:
> >> 
> >> Name of time slot:
> >> 
> >> Name of draft(s):
> >> 
> >> Time requested:
> >> 
> >> Presenter name(s):
> >> 
> >> 
> >> 
> >> More details about the IETF 101, London can be found at:
> >> 
> >> 
> >> 
> >> http://www.ietf.org/meeting/101/index.html
> >> 
> >> 
> >> 
> >> Again, presenters and draft authors please invoke active discussions in the ANIMA list. Mail list is a very good place to discuss and reach consensus on technical issues.
> >> 
> >> 
> >> 
> >> Best regards,
> >> 
> >> 
> >> 
> >> Toerless & Sheng
> >> 
> > 
> >> _______________________________________________
> >> Anima mailing list
> >> Anima@ietf.org
> >> https://www.ietf.org/mailman/listinfo/anima
> > 
> > 
> > -- 
> > ---
> > tte@cs.fau.de
> > 
> > _______________________________________________
> > Anima mailing list
> > Anima@ietf.org
> > https://www.ietf.org/mailman/listinfo/anima
> 

-- 
---
tte@cs.fau.de


From nobody Wed Mar 14 06:44:52 2018
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C24B12D775 for <anima@ietfa.amsl.com>; Wed, 14 Mar 2018 06:44:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, T_TVD_MIME_EPI=0.01] autolearn=ham autolearn_force=no
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 ZQeBuUIRzpQq for <anima@ietfa.amsl.com>; Wed, 14 Mar 2018 06:44:48 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8857112D0C3 for <anima@ietf.org>; Wed, 14 Mar 2018 06:44:48 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 433B520091 for <anima@ietf.org>; Wed, 14 Mar 2018 09:53:22 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 0BDCD81048 for <anima@ietf.org>; Wed, 14 Mar 2018 09:44:47 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
to: anima@ietf.org
In-Reply-To: <3261.1520994236@obiwan.sandelman.ca>
References: <5086bdbc-b37a-baf6-81e0-58e361d39ea3@cisco.com> <8f2e8ff8-fc4c-73d1-5941-29fe35e4d511@cisco.com> <3261.1520994236@obiwan.sandelman.ca>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Wed, 14 Mar 2018 09:44:46 -0400
Message-ID: <24157.1521035086@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/yUZgA7Ufh9IbuDaF76vAWOXLDno>
Subject: [Anima] BRSKI -- does pledge or registrar create serial-number?
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2018 13:44:51 -0000

--=-=-=
Content-Type: text/plain


Based upon private emails about interoperation attempts, I opened:
      https://github.com/anima-wg/anima-bootstrap/issues/47

https://tools.ietf.org/html/draft-ietf-anima-bootstrapping-keyinfra-12#section-2.3.1
explains how a serial-number voucher field is derived from the IDevID fields.

It does not say which party does this. The Pledge can do it when it forms
it's voucher-request. However, if the pledge does not do so, is it valid to
send a voucher-request without a serial-number field, and assume that the
Registrar will do the same thing to find the serial-number from the IDevID?

The problem with having any entity other than the Pledge do the calculation
is that it's the Pledge that will be comparing the resulting voucher, and as
there are multiple ways to produce the serial-number, and they might not be
identical, a voucher could be issued that the Pledge can not verify.

If section 2.3.1 should be applied on the pledge, then we should perhaps say
that more clearly in that section.
The VOUCHER YANG says that the field is mandatory.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlqpJlQACgkQgItw+93Q
3WV+YAgAujXo3RNf9Z1QTeKTwGDlDhiV4COyhkBQaOarRPFYKnykmrVVTep54H9l
b7vC2PgLQr6EpmTmhUANPc0i6Id1piJybshz0H+qXjpGp4IT6eIQyXDq1rbirYhN
TptO8SABakrXR6IincsIOaX4i1SbMEYACMX1TjzUJYns4rG5W9cbkPMap8ll37u4
GFHqAL9b/20/Js65FaJdIo4Gm3fQZsepqlvTryhxnXMLmbV1GAaWMteVQvTbedNZ
l86z9f29s23+xNzjfTcx0K2ZzSy4pkVjLcVkTuvaTm4WXQnvS3MK8ArAvtiES7C/
kO8JSxRjXz8EqrmCFgzymCKTPq4Zyw==
=CSCh
-----END PGP SIGNATURE-----
--=-=-=--

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


From nobody Wed Mar 14 19:33:10 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7DE412D82F for <anima@ietfa.amsl.com>; Wed, 14 Mar 2018 19:33:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 pUkRU4fl-NkY for <anima@ietfa.amsl.com>; Wed, 14 Mar 2018 19:33:07 -0700 (PDT)
Received: from mail-pg0-x22c.google.com (mail-pg0-x22c.google.com [IPv6:2607:f8b0:400e:c05::22c]) (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 E63DD12D810 for <anima@ietf.org>; Wed, 14 Mar 2018 19:33:06 -0700 (PDT)
Received: by mail-pg0-x22c.google.com with SMTP id d1so2229649pgv.2 for <anima@ietf.org>; Wed, 14 Mar 2018 19:33:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:to:from:subject:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=Yl/Ngk96+T43gQ9wT944Ttt80W6jZrepwphf6KwZJio=; b=H3kaVHzeIX7FlnLNEv8dvI4tGucQBDt+PmvFb9wUTTdgE75jXCRlZlWNeatteG6B56 sHhK7Le0+keVk8K4/ZnFH5UnV7pFTW+md1Wb9KUzAjSTunmiuqwKyXa/QwrkoMBqq29E wuZgIbIKYxwcU4Ygy94ijLAHfTwFPhLPnUOw0BtUehDONEBHJH0T8ELM99WDZLUrnY7S bvuxymghVPzVpNCSL5LiyGKK+u1lvOYmIFX9A61gguiU6EDr0LfYwIkvgDXxgT5e18Zw 0dogyJlpzSotXXRPo8Qx+NTqxUY1jPYVHnxkHW2zXdAJr9Nk/gs2nShFidy4g5WJcyYI VuGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:to:from:subject:message-id:date :user-agent:mime-version:content-language:content-transfer-encoding; bh=Yl/Ngk96+T43gQ9wT944Ttt80W6jZrepwphf6KwZJio=; b=nrkqPT++HpNAQf24JcWX2a+U03uqAB0m2xrWlj/2HeY7lx7EbXBvbq5/h7QhsuB/w/ 5tkd2J2FVrM+GVqjCeL4dYZ3ZYMiyuGIZL2ZEq9vAgsJmUALytjkiRo9u2AFD3dYnnEk rFeKXEAHegMTpherJs5qZekdyYPHrkqeH+LjFDi27AdkyrBJKlG0WksyoDHdMVP2A4ew lFlCkrVBbhvuYVMzZ7aCht13CQW26QIiYVbZj5aIoXtLxN/tQP4vsyKCv6Y7BILFGkj9 sTXfHmcl58BJiSUIyArVs6WlzzyQZoSdgu5HJT3Uf7IprMNmwJA3trgvRXngMV5FWdJE o8rw==
X-Gm-Message-State: AElRT7F3Icg8wQPRR51ObPG84KL63AISpUPHYHMoTm7iQ7zcQMC+XkUI QTcS0EEwsD/r5Cgv5VCxaBUVMQIV
X-Google-Smtp-Source: AG47ELsd+bwc+Vvew90igz5WHUFRtC8IYsj8hovJaV4TbiXzi/MI0eTV++ABGyBPuIPpijBJ2s28Ng==
X-Received: by 10.99.145.193 with SMTP id l184mr5354021pge.394.1521081186193;  Wed, 14 Mar 2018 19:33:06 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.72.177]) by smtp.gmail.com with ESMTPSA id r9sm7805260pfg.11.2018.03.14.19.33.03 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Mar 2018 19:33:05 -0700 (PDT)
Sender: Brian Carpenter <becarpenter46@gmail.com>
To: Anima WG <anima@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <dcb61f08-781a-e6dd-fcea-127d9761b559@gmail.com>
Date: Thu, 15 Mar 2018 15:33:07 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/QrbegGRVMsto0zXtyfjbyF98_jw>
Subject: [Anima] Comments on draft-liu-anima-grasp-distribution-05
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2018 02:33:09 -0000

Hi,

Since there were a lot of updates in this version, I read it again
from the beginning. Here are my comments.

In general I think this is useful work that the WG should consider
adopting. There is definitely a requirement for something in the
space between peer-to-peer synchronization and flooding to all
autonomic nodes. The fixed size of GRASP messages also limits
information distribution at present.

> 3.2 One-to-Many Communications
> 
>    Some information exchange involve an information source and multiple
>    receivers. This scenario can be divided into two situations:
> 
>       1) When some information are relevant to all or most of the nodes
>       in the domain, the node that firstly handle the information should
>       use a mechanism to propagate it to all the other nodes.
...
>       2) A more general case is that some information is only relevant
>       to a specific group of nodes belonging to the same sub-domain or
>       sharing the same interests.

It's probably worth mentioning that there is a tradeoff here. If some
information is relevant to 50% of nodes, it is probably cheapest to
simply flood it to all nodes. If it is relevant to only 5% of nodes,
it is probably cheapest to use a pub/sub model.

> 3.3 Requirements
...
>       3) Distributed Coordination....
...
>       Obviously, purely relying
>       on instant communication model is inefficient, while a scalable,
>       common, yet distributed data layer, on which AFs can store and
>       share information in an asynchronous way, should be a better
>       choice.

This is the most interesting case (I think of it as a whiteboard, where
any ASA can read, write or erase). Doesn't it also relate to distributed
consensus mechanisms? 

Can we consider the previous case (pub/sub) to be a subset of this case,
with only one node having write/erase capability?

> 5.1 GRASP for instant communications
...
>       o  Matching condition: "Device role=IPRAN_RSG"
> 
>       o  Matching objective: "Neighbors"
> 
>       o  Action: "Forward"
> 
>    This example means: only distributing the information to the
>    neighbors who are IPRAN_RSG. 

How does the node performing the distribution know which of
its neighbours have the role IPRAN_RSG? Is there a registration
process? Is it really any different than the subscribe process
in pub/sub? ("I subscribe to IPRAN_RSG information".)

>  5.2 GRASP for asynchronous communications

Once we have the previous point solved, we can model the
asynch distribution as a selective flood to the "whiteboard"
in each node.

Having said that, I want to look back in the draft at the Event Queue
described in section 4.2.1. I'm not sure that we need it as a separate
engine from the queues implied by GRASP's existing asynchronous
operations. If you model a producer or consumer as a process using
GRASP, it will naturally need to support simultaneous asynch operations
and an event queue.

I am wondering to what extent I can model this directly over GRASP as it
exists today. My main question is mentioned above: how does a node
know which of its neighbours have a given role?

(One possible answer is that *every* node sends out a local GRASP
flood at very low frequency, stating which roles it supports.
Then every node builds a cache of its neighbours' roles. I can
make that work with GRASP today.)

Regards
    Brian


From nobody Thu Mar 15 02:37:23 2018
Return-Path: <mcr@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 576DD12D893; Thu, 15 Mar 2018 02:37:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.308
X-Spam-Level: 
X-Spam-Status: No, score=-0.308 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 c3doTgaA9w6g; Thu, 15 Mar 2018 02:37:05 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F2C312D886; Thu, 15 Mar 2018 02:37:02 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [81.128.173.187]) by relay.sandelman.ca (Postfix) with ESMTPS id D5B7F1F963; Thu, 15 Mar 2018 09:37:00 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 662E21929; Thu, 15 Mar 2018 02:31:43 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>
cc: iot-dir <iot-dir@ietf.org>, "ops-dir\@ietf.org" <ops-dir@ietf.org>, "int-dir\@ietf.org" <int-dir@ietf.org>, "draft-ietf-anima-autonomic-control-plane\@ietf.org" <draft-ietf-anima-autonomic-control-plane@ietf.org>,  "anima\@ietf.org" <anima@ietf.org>
In-reply-to: <449b7e2f10094531b325919710696754@XCH-RCD-001.cisco.com>
References: <449b7e2f10094531b325919710696754@XCH-RCD-001.cisco.com>
Comments: In-reply-to "Pascal Thubert (pthubert)" <pthubert@cisco.com> message dated "Mon, 26 Feb 2018 17:25:58 +0000."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 15 Mar 2018 06:31:43 +0000
Message-ID: <20093.1521095503@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/oSnvezW6DHcPSKuQdLCsWllhRrc>
Subject: Re: [Anima] An IOT DIR review of draft-ietf-anima-autonomic-control-plane
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2018 09:37:06 -0000

--=-=-=
Content-Type: text/plain


Thank you Pascal for for the review!

I don't think I want to respond to your specific comments, but rather
constrast some text to explain why (charter aside) we felt that we need
to leave out constrained networks.

The ACP is primarily about connecting network *service* equipment at an ISP
(or Enterprise) with the Network Operations Center for managemenet and
control.  Running SDN flows over the ACP makes a significant amount of sense.
Doing RESTconf over the ACP also makes sense.
Or just ssh in and type "conf term" and go, knowing you *can't* fat finger
something and lose your command channel.

The ACP is secondarily (today! we hope it will change) about connectivity
*among* this equipment such that the devices can interact at a meta-level.
The ACP is in some sense an "Internet of Routers", ... by routers and *for*
routers (and devices that contain switching functionality like hypervisors)

These devices otherwise do revenue generating activities like moving packets,
slicing and dicing video, running virtual machines, mining bitcoin, etc.

There is no fundamental reason why constrained networks of constrained
devices couldn't have an ACP, except for code size and energy consumption.
I.e. except for the thing that makes them constrained.

In a cabinet full of a physical hosts supporting some kind of virtualized
structure such as you might find at facebook, google, amazon, etc.  the
little bit of interaction between the Top-of-Rack switch, the service
processors (iDrac, iLO, etc.) of the systems, is significantly less than 1%
of the typical 10G+ that the cabinet probably has.
The ACP gives you a safe and secure place to bring in the sensors and
actuators in the cabinet (IP enabled power bars, etc.).  IPsec support in
a powerbar is not unknown.

To constrast this to battery-powered OpenMote scale devices.
The ACP overhead is probably 80% of the bandwidth of network.

You asked about why we have so many possible ACP technologies, but really
IPsec is the MTI.  That's partly because many are unfamiliar with IPsec and
are sure that some other "custom" solution would be better.  Grass is just
greener over there.

But in fact we actually have no other IETF standard solution that we can
actually point to.  "SSL VPN" is a marketing term, solutions are completely
vertically integrated: they don't interoperate at all.
OpenVPN an example of one, but it is a company/open-source-project, not an
RFC.   And also some would like to try MACSEC.

I think that we could get IPsec + IKEv2 (or some other similar technology)
into an OpenMote, but I'm not sure it's worthwhile, because at the end of
the day the ROI isn't that good if you eat 70% of the system doing this.

This brings me to your comments about how many parents to select and the
like.  While we don't have layer-2 ACKs in the IPsec hop-by-hop tunnels the
way that 15.4 does, but we do have IKEv2 dead-peer-detection messages.  We
will generally know quite quickly if we have lot a connection to a parent.
The occurance of an IKEv2 negotiation also provides a very strong signal of
that there is a new peer.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [







--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJaqhNPAAoJEJVM4Vb9/EKQ9lQH/RWGQcWHX8IdvaR0CQTr5hv+
HEbxczBZtSVab21boA1a1zu2KOMxIIaIYDygxguEPh28xMzNcedI4CtS8Uuyl95k
WfQ8OwX0p4pecsR8DOU1GbyCVjLlEGG/fAZ4H8+sCnuzKpD9H/TrfpfhPYhML4HX
fxR6ndzY2fbXxVXeunbBvHkPfbydW7gxLyB+whRpuqQ/zuUVkJfzoROxIZ8ki+12
cYQKCsD+Wf/Xgmvo2WDMaGnHEU+4w3LvjYbq6KZIOs6G6IYDzQJaRLme5d9UAzIn
YyUdtE7CjN9gFTXyXELF5PzPHJJRmdf0f+TfftTFp6RyVYJvoa8tOQSzpatuP20=
=i2Cr
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Mar 15 02:37:49 2018
Return-Path: <mcr@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E25A12D886 for <anima@ietfa.amsl.com>; Thu, 15 Mar 2018 02:37:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.435
X-Spam-Level: *
X-Spam-Status: No, score=1.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_SBL_CSS=3.335, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 0_VvFrt-lXkX for <anima@ietfa.amsl.com>; Thu, 15 Mar 2018 02:37:05 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99B0712D93F for <anima@ietf.org>; Thu, 15 Mar 2018 02:37:03 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [81.128.173.187]) by relay.sandelman.ca (Postfix) with ESMTPS id 36FD9201FA; Thu, 15 Mar 2018 09:37:02 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 593042069; Thu, 15 Mar 2018 02:56:33 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: Anima WG <anima@ietf.org>
In-reply-to: <7bc91acd-0c31-4d52-16d9-41aeaf8808d2@gmail.com>
References: <152028986381.12884.9092671195107327813@ietfa.amsl.com> <7bc91acd-0c31-4d52-16d9-41aeaf8808d2@gmail.com>
Comments: In-reply-to Brian E Carpenter <brian.e.carpenter@gmail.com> message dated "Thu, 08 Mar 2018 16:44:52 +1300."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 15 Mar 2018 06:56:33 +0000
Message-ID: <21591.1521096993@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/rtav8QdEOWiwCn8pVlFj9XMOTbM>
Subject: Re: [Anima] BRSKI discovery implementation report [I-D Action: draft-ietf-anima-bootstrapping-keyinfra-12.txt]
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2018 09:37:06 -0000

--=-=-=
Content-Type: text/plain


Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > I have aligned my Python demos** of the BRSKI discovery mechanisms with
    > the -12 draft.
    > Here are dumps of the received flood messages, with discussion:

    > (1) Flood sent by the registrar as received by the proxy. This is Python output
    > (so the b'...' strings are hexdumps of bytes objects.)

    > [9, 1729214102, b'2406e00741ec000128ccdc4c97036781', 120000, [['AN_join_registrar', 5, 255, 'EST-TLS'], [103, b'2406e00741ec000128ccdc4c97036781', 6, 80]]]

    > Nothing serious to report here. Since the draft only defines the 'EST-TLS'
    > form, I haven't included any alternatives. My code could also handle announcing
    > IP-in-IP for example.

    > Compare to the example in the draft:

    > [M_FLOOD, 12340815, h'fda379a6f6ee00000200000064000001', 180000,
    > ["AN_join_registrar", 4, 255, "EST-TLS"],
    > [O_IPv6_LOCATOR,
    > h'fda379a6f6ee00000200000064000001', TCP, 80]]

    > I'd prefer to see TCP represented as IPPROTO_TCP to align with the
    > GRASP spec.

I think that what I did was confuse some of the abstract and specific value.
Because things like M_FLOOD and O_IPv6_LOCATOR are symbolic representations
of numbers, while TCP was just something that I thought I could abstract
myself.

I've changed it to say IPPROTO_TCP everywhere.

    > [9, 160559994, b'2406e00741ec000128ccdc4c97036781', 180000, [['AN_proxy', 5, 1, ''], [103, b'fe8000000000000028ccdc4c97036781', 6, 11805]]]

    > Compare to the example in the draft:

    > [M_FLOOD, 12340815, h'fe800000000000000000000000000001', 180000,
    > ["AN_Proxy", 4, 1, ""],
    > [O_IPv6_LOCATOR,
    > h'fe800000000000000000000000000001', 'TCP', 4443]]

    > Several comments:

    > 1. The 3rd element is the 'initiator' address. The draft shows that as
    > a link-local. It doesn't matter too much, but my code uses a routeable
    > address. It's only there for disambiguation in a multi-hop flood,
    > which doesn't apply in this case. The address that matters is the second
    > one, in the locator. The packet itself is sent link-local.

Since it's a link-local, DULL single-hop "flood" that can never get forwarded
in any way, and the it's occuring on the "bare" wire, using any GUA (or ACP
ULA) would seem to leak information that should remain safely inside the ACP.

    > 2. 'TCP' shouldn't be a string, it should be IPPROTO_TCP as above.

Agreed.

    > 3. The objective is defined as having a null value. Why isn't it
    > "EST-TLS" again?

I'm not sure, I thought that the objective-value was what we were looking
for.  I.e. if some device is trying to find a place to backup 1GB,
then it might have an objective of "KERNEL:DUMP" with an objective-value
of 1073741824.

Since we don't care what the dimension of the objective, I thought leaving it
empty was the best thing.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [



--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJaqhkhAAoJEJVM4Vb9/EKQWKUH/2rX2uU49GzHO2wLYnwE1Ulo
Ot2H8F0mvd2zg4hJ//7d0CEOj+JfdSvIdATPXjIBCfBGZWSZhr4EE3d9+KUKH2ak
jgtBA/uadDhav1XSQBe5b7vI2r6oNMWc10fvaxQbJwRMuohtqm82IXYzX6NluoyY
qqdL0xDOzDzTri7SdtIxFCgqCwuJmruQNGlFC2QZ1pM9f1qmgayvclAAYCq8kmEM
c4mrP+3A/L3h/OFpalu5P2L8VTD80tlBnIAv7TKfhpe5ggAEX1P5rDCrPV/vb5DM
uaNVJSi6iG5eVK8ufBRJIAS/UfRjdrsCvdvTA0aAZkuYtjfn59k0trAfEInza/M=
=Qu27
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Mar 15 02:42:46 2018
Return-Path: <mcr@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DFA412D947 for <anima@ietfa.amsl.com>; Thu, 15 Mar 2018 02:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Hb2nG9kZi3CF for <anima@ietfa.amsl.com>; Thu, 15 Mar 2018 02:42:39 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62CBE12D942 for <anima@ietf.org>; Thu, 15 Mar 2018 02:42:39 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [81.128.173.187]) by relay.sandelman.ca (Postfix) with ESMTPS id 95DDB20200 for <anima@ietf.org>; Thu, 15 Mar 2018 09:37:02 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 12B7F23C3; Thu, 15 Mar 2018 04:01:29 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
to: anima@ietf.org
In-Reply-To: <3261.1520994236@obiwan.sandelman.ca>
References: <5086bdbc-b37a-baf6-81e0-58e361d39ea3@cisco.com> <8f2e8ff8-fc4c-73d1-5941-29fe35e4d511@cisco.com> <3261.1520994236@obiwan.sandelman.ca>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Thu, 15 Mar 2018 08:01:29 +0000
Message-ID: <25961.1521100889@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/bo_0RGjm3SmdlK0Y6J7L3DMVasc>
Subject: [Anima] BRSKI -- does pledge or registrar create serial-number?
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2018 09:42:42 -0000

--=-=-=
Content-Type: text/plain


Based upon private emails about interoperation attempts, I opened:
      https://github.com/anima-wg/anima-bootstrap/issues/47

https://tools.ietf.org/html/draft-ietf-anima-bootstrapping-keyinfra-12#section-2.3.1
explains how a serial-number voucher field is derived from the IDevID fields.

It does not say which party does this. The Pledge can do it when it forms
it's voucher-request. However, if the pledge does not do so, is it valid to
send a voucher-request without a serial-number field, and assume that the
Registrar will do the same thing to find the serial-number from the IDevID?

The problem with having any entity other than the Pledge do the calculation
is that it's the Pledge that will be comparing the resulting voucher, and as
there are multiple ways to produce the serial-number, and they might not be
identical, a voucher could be issued that the Pledge can not verify.

If section 2.3.1 should be applied on the pledge, then we should perhaps say
that more clearly in that section.
The VOUCHER YANG says that the field is mandatory.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlqpJlQACgkQgItw+93Q
3WV+YAgAujXo3RNf9Z1QTeKTwGDlDhiV4COyhkBQaOarRPFYKnykmrVVTep54H9l
b7vC2PgLQr6EpmTmhUANPc0i6Id1piJybshz0H+qXjpGp4IT6eIQyXDq1rbirYhN
TptO8SABakrXR6IincsIOaX4i1SbMEYACMX1TjzUJYns4rG5W9cbkPMap8ll37u4
GFHqAL9b/20/Js65FaJdIo4Gm3fQZsepqlvTryhxnXMLmbV1GAaWMteVQvTbedNZ
l86z9f29s23+xNzjfTcx0K2ZzSy4pkVjLcVkTuvaTm4WXQnvS3MK8ArAvtiES7C/
kO8JSxRjXz8EqrmCFgzymCKTPq4Zyw==
=CSCh
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Mar 15 12:35:59 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5F26126C22 for <anima@ietfa.amsl.com>; Thu, 15 Mar 2018 12:35:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 gk_AVgVUG-97 for <anima@ietfa.amsl.com>; Thu, 15 Mar 2018 12:35:56 -0700 (PDT)
Received: from mail-pg0-x22a.google.com (mail-pg0-x22a.google.com [IPv6:2607:f8b0:400e:c05::22a]) (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 E779512D77C for <anima@ietf.org>; Thu, 15 Mar 2018 12:35:55 -0700 (PDT)
Received: by mail-pg0-x22a.google.com with SMTP id l4so3148449pgp.11 for <anima@ietf.org>; Thu, 15 Mar 2018 12:35:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Me5GrPdke4fnZtCekZOV1NC0kcM+MIjt9n4kwBV8nH0=; b=Ur1DApfYlciwQZLsXh65F7lXPs5c4u7CHSgicYV8lXZijgHMGpDMFZSlKVs5Hx02wy sh8rZitE/Hay1a/2KRHEYcrXUGBQNPqkFWvsmZY+MxKVxOsIYAuwQ65HLUJuWM8qSXUJ Kkuz8puvq9NgwZdfcw/kRt3++18cXTt8R3ujJeGOZrm+B6UK69Hm2FZuuCLvRLJNQdOQ X62nY/3SFkeTxxgANPQyXSW/G6xavxGJ8DjxmLLjxTK2FX3vXp0mw3OPl71ZC6BHgEd7 S870Ky2Oq/ZdjUPsotiXTFH7H80rJLnU2KH3nqPvx01C1fuV9E3MyL3dnRkuraNig9mS 5uPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Me5GrPdke4fnZtCekZOV1NC0kcM+MIjt9n4kwBV8nH0=; b=NbHXiZUbvieKtw0y4AF2bgjZY4cbQ4QzVqVieG5atdFhSPuIOIs4cSMXqz7iXXncRG fC6GJ2tztZ1V2BmlKS/F5BTsBUMz46aciVw1z1NAFiYlApnie614b5GNCA59L7j9Uf9J YUE7vKQgbxrp8YFxHxblJ2bvAt7V8f25IUSOd+8AGYpIRfQw0LXejZQP10MsAJr0QuXE TW1x+Vy6Dm8y4ZrC6OIuzynx4hxKl9biABvbQrI03r8Vfm9VLcn0kboXVhjUx8kgdO+j uBcm6TzHCHkMb4ZQf5YlycEotGmF3PotuULbu9VWEapzh+pCkI2cdsZgbqOtc0mMHDuf CSMw==
X-Gm-Message-State: AElRT7H33LJGtslxAR+IlzWIVWdyAYddg0q8KTx4ZIO2iFq/t/5Il/r6 /AzYZ3eGCvp3mEdIBi8ChqawX9wa
X-Google-Smtp-Source: AG47ELt7nb0i3EBtkAuIIwLzfOhSrfd1kxYxPezuOsV8WCFa5egnDP84dDso3zH7K+NDSluF0blSwA==
X-Received: by 10.98.0.21 with SMTP id 21mr6348081pfa.48.1521142555121; Thu, 15 Mar 2018 12:35:55 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.72.177]) by smtp.gmail.com with ESMTPSA id m18sm10107838pgu.51.2018.03.15.12.35.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Mar 2018 12:35:54 -0700 (PDT)
Sender: Brian Carpenter <becarpenter46@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Anima WG <anima@ietf.org>
References: <152028986381.12884.9092671195107327813@ietfa.amsl.com> <7bc91acd-0c31-4d52-16d9-41aeaf8808d2@gmail.com> <21591.1521096993@dooku.sandelman.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <b314b3d8-2aad-3041-be48-18bbc01952fc@gmail.com>
Date: Fri, 16 Mar 2018 08:35:58 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <21591.1521096993@dooku.sandelman.ca>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/OsS5r8dsa1m20YtYZQJpWnxWIjY>
Subject: Re: [Anima] BRSKI discovery implementation report [I-D Action: draft-ietf-anima-bootstrapping-keyinfra-12.txt]
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2018 19:35:58 -0000

On 15/03/2018 19:56, Michael Richardson wrote:
> 
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>     > I have aligned my Python demos** of the BRSKI discovery mechanisms with
>     > the -12 draft.
>     > Here are dumps of the received flood messages, with discussion:
> 
>     > (1) Flood sent by the registrar as received by the proxy. This is Python output
>     > (so the b'...' strings are hexdumps of bytes objects.)
> 
>     > [9, 1729214102, b'2406e00741ec000128ccdc4c97036781', 120000, [['AN_join_registrar', 5, 255, 'EST-TLS'], [103, b'2406e00741ec000128ccdc4c97036781', 6, 80]]]
> 
>     > Nothing serious to report here. Since the draft only defines the 'EST-TLS'
>     > form, I haven't included any alternatives. My code could also handle announcing
>     > IP-in-IP for example.
> 
>     > Compare to the example in the draft:
> 
>     > [M_FLOOD, 12340815, h'fda379a6f6ee00000200000064000001', 180000,
>     > ["AN_join_registrar", 4, 255, "EST-TLS"],
>     > [O_IPv6_LOCATOR,
>     > h'fda379a6f6ee00000200000064000001', TCP, 80]]
> 
>     > I'd prefer to see TCP represented as IPPROTO_TCP to align with the
>     > GRASP spec.
> 
> I think that what I did was confuse some of the abstract and specific value.
> Because things like M_FLOOD and O_IPv6_LOCATOR are symbolic representations
> of numbers, while TCP was just something that I thought I could abstract
> myself.
> 
> I've changed it to say IPPROTO_TCP everywhere.

Thanks. (I have a little gripe that IANA doesn't control these names, which
are pretty much universal, but only defined in C files that float around
in cyberspace.)

> 
>     > [9, 160559994, b'2406e00741ec000128ccdc4c97036781', 180000, [['AN_proxy', 5, 1, ''], [103, b'fe8000000000000028ccdc4c97036781', 6, 11805]]]
> 
>     > Compare to the example in the draft:
> 
>     > [M_FLOOD, 12340815, h'fe800000000000000000000000000001', 180000,
>     > ["AN_Proxy", 4, 1, ""],
>     > [O_IPv6_LOCATOR,
>     > h'fe800000000000000000000000000001', 'TCP', 4443]]
> 
>     > Several comments:
> 
>     > 1. The 3rd element is the 'initiator' address. The draft shows that as
>     > a link-local. It doesn't matter too much, but my code uses a routeable
>     > address. It's only there for disambiguation in a multi-hop flood,
>     > which doesn't apply in this case. The address that matters is the second
>     > one, in the locator. The packet itself is sent link-local.
> 
> Since it's a link-local, DULL single-hop "flood" that can never get forwarded
> in any way, and the it's occuring on the "bare" wire, using any GUA (or ACP
> ULA) would seem to leak information that should remain safely inside the ACP.

That's not what the GRASP spec says:

   The 'initiator' field in the message is a globally unique IP address
   of the initiator, for the sole purpose of disambiguating the Session
   ID in other nodes.  If for some reason the initiator does not have a
   globally unique IP address, it MUST use a link-local address for this
   purpose that is highly likely to be unique, for example using
   [RFC7217].  Determination of a node's globally unique IP address is
   implementation-dependent. 

Maybe we should have mandated link-local for DULL, but we didn't.
Can we hold that as a possible GRASP erratum?

>     > 2. 'TCP' shouldn't be a string, it should be IPPROTO_TCP as above.
> 
> Agreed.
> 
>     > 3. The objective is defined as having a null value. Why isn't it
>     > "EST-TLS" again?
> 
> I'm not sure, I thought that the objective-value was what we were looking
> for.  I.e. if some device is trying to find a place to backup 1GB,
> then it might have an objective of "KERNEL:DUMP" with an objective-value
> of 1073741824.
> 
> Since we don't care what the dimension of the objective, I thought leaving it
> empty was the best thing.

That's fine if it was intentional. It would also be easy to define non-null
values later if we found them useful.

    Brian


From nobody Fri Mar 16 02:53:42 2018
Return-Path: <jiangsheng@huawei.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B59741204DA; Fri, 16 Mar 2018 02:53:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.23
X-Spam-Level: 
X-Spam-Status: No, score=-4.23 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 yaHmRsl4QE1i; Fri, 16 Mar 2018 02:53:39 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EAF612025C; Fri, 16 Mar 2018 02:53:39 -0700 (PDT)
Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id F0641C3918EC1; Fri, 16 Mar 2018 09:53:35 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.382.0; Fri, 16 Mar 2018 09:53:37 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0361.001; Fri, 16 Mar 2018 17:53:29 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "anima@ietf.org" <anima@ietf.org>
CC: "anima-chairs@ietf.org" <anima-chairs@ietf.org>
Thread-Topic: Primary ANIMA agenda @ IETF 101, London
Thread-Index: AdO9DIQmtFSiO/sdSM65k1FvzGxy1A==
Date: Fri, 16 Mar 2018 09:53:29 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B928183CBB8@NKGEML515-MBX.china.huawei.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.185.119]
Content-Type: multipart/alternative; boundary="_000_5D36713D8A4E7348A7E10DF7437A4B928183CBB8NKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/DU5nK4LoCBsowJoaPrqq97OshUY>
Subject: [Anima] Primary ANIMA agenda @ IETF 101, London
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2018 09:53:42 -0000

--_000_5D36713D8A4E7348A7E10DF7437A4B928183CBB8NKGEML515MBXchi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi, ANIMA all,



The chairs have uploaded a primary meeting agenda for our ANIMA WG sessions=
 in London, United Kingdom.



Tuesday (March 20th, 2018) 9:30-12:00, Buckingham, Morning session I

 https://datatracker.ietf.org/meeting/101/materials/agenda-101-anima/



If there is any question or request on the agenda, please let the chairs kn=
ow.



The speakers please send your slides to the chair in advance, so that we co=
uld upload them before the meeting. The slides are due before midnight on S=
unday, March 18th.



Best regards,



Sheng + Toerless



--_000_5D36713D8A4E7348A7E10DF7437A4B928183CBB8NKGEML515MBXchi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:\5B8B\4F53;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:\5B8B\4F53;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"\@\5B8B\4F53";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML \9884\8BBE\683C\5F0F Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:\5B8B\4F53;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.HTMLChar
	{mso-style-name:"HTML \9884\8BBE\683C\5F0F Char";
	mso-style-priority:99;
	mso-style-link:"HTML \9884\8BBE\683C\5F0F";
	font-family:\5B8B\4F53;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"ZH-CN" link=3D"#0563C1" vlink=3D"#954F72" style=3D"text-justi=
fy-trim:punctuation">
<div class=3D"WordSection1">
<pre style=3D"margin-bottom:7.5pt;background:white"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Times New Roman&quot;,serif;color=
:#333333">Hi, ANIMA all,<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white;font-variant-ligatures: =
normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-web=
kit-text-stroke-width: 0px;text-decoration-style: initial;text-decoration-c=
olor: initial;word-spacing:0px"><span lang=3D"EN-US" style=3D"font-size:10.=
0pt;font-family:&quot;Times New Roman&quot;,serif;color:#333333">&nbsp;<o:p=
></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white;font-variant-ligatures: =
normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-web=
kit-text-stroke-width: 0px;text-decoration-style: initial;text-decoration-c=
olor: initial;word-spacing:0px"><span lang=3D"EN-US" style=3D"font-size:10.=
0pt;font-family:&quot;Times New Roman&quot;,serif;color:#333333">The chairs=
 have uploaded a primary meeting agenda for our ANIMA WG sessions in London=
, United Kingdom.<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white;font-variant-ligatures: =
normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-web=
kit-text-stroke-width: 0px;text-decoration-style: initial;text-decoration-c=
olor: initial;word-spacing:0px"><span lang=3D"EN-US" style=3D"font-size:10.=
0pt;font-family:&quot;Times New Roman&quot;,serif;color:#333333">&nbsp;<o:p=
></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white;font-variant-ligatures: =
normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-web=
kit-text-stroke-width: 0px;text-decoration-style: initial;text-decoration-c=
olor: initial;word-spacing:0px"><span lang=3D"EN-US" style=3D"font-size:10.=
0pt;font-family:&quot;Times New Roman&quot;,serif;color:#333333">Tuesday (M=
arch 20th, 2018) 9:30-12:00, Buckingham, Morning session I&nbsp;<o:p></o:p>=
</span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white;font-variant-ligatures: =
normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-web=
kit-text-stroke-width: 0px;text-decoration-style: initial;text-decoration-c=
olor: initial;word-spacing:0px"><span lang=3D"EN-US" style=3D"font-size:10.=
0pt;font-family:&quot;Times New Roman&quot;,serif;color:#333333">&nbsp;<a h=
ref=3D"https://datatracker.ietf.org/meeting/101/materials/agenda-101-anima/=
"><span style=3D"font-size:12.0pt;font-family:&#23435;&#20307;;color:#33333=
3;text-decoration:none">https://datatracker.ietf.org/meeting/101/materials/=
agenda-101-anima/</span></a><o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white;font-variant-ligatures: =
normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-web=
kit-text-stroke-width: 0px;text-decoration-style: initial;text-decoration-c=
olor: initial;word-spacing:0px"><span lang=3D"EN-US" style=3D"font-size:10.=
0pt;font-family:&quot;Times New Roman&quot;,serif;color:#333333">&nbsp;<o:p=
></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white;font-variant-ligatures: =
normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-web=
kit-text-stroke-width: 0px;text-decoration-style: initial;text-decoration-c=
olor: initial;word-spacing:0px"><span lang=3D"EN-US" style=3D"font-size:10.=
0pt;font-family:&quot;Times New Roman&quot;,serif;color:#333333">If there i=
s any question or request on the agenda, please let the chairs know.<o:p></=
o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white;font-variant-ligatures: =
normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-web=
kit-text-stroke-width: 0px;text-decoration-style: initial;text-decoration-c=
olor: initial;word-spacing:0px"><span lang=3D"EN-US" style=3D"font-size:10.=
0pt;font-family:&quot;Times New Roman&quot;,serif;color:#333333">&nbsp;<o:p=
></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white;font-variant-ligatures: =
normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-web=
kit-text-stroke-width: 0px;text-decoration-style: initial;text-decoration-c=
olor: initial;word-spacing:0px"><span lang=3D"EN-US" style=3D"font-size:10.=
0pt;font-family:&quot;Times New Roman&quot;,serif;color:#333333">The speake=
rs please send your slides to the chair in advance, so that we could upload=
 them before the meeting. The slides are due before midnight on Sunday, Mar=
ch 18th.<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white;font-variant-ligatures: =
normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-web=
kit-text-stroke-width: 0px;text-decoration-style: initial;text-decoration-c=
olor: initial;word-spacing:0px"><span lang=3D"EN-US" style=3D"font-size:10.=
0pt;font-family:&quot;Times New Roman&quot;,serif;color:#333333">&nbsp;<o:p=
></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white;font-variant-ligatures: =
normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-web=
kit-text-stroke-width: 0px;text-decoration-style: initial;text-decoration-c=
olor: initial;word-spacing:0px"><span lang=3D"EN-US" style=3D"font-size:10.=
0pt;font-family:&quot;Times New Roman&quot;,serif;color:#333333">Best regar=
ds,<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white;font-variant-ligatures: =
normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-web=
kit-text-stroke-width: 0px;text-decoration-style: initial;text-decoration-c=
olor: initial;word-spacing:0px"><span lang=3D"EN-US" style=3D"font-size:10.=
0pt;font-family:&quot;Times New Roman&quot;,serif;color:#333333">&nbsp;<o:p=
></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white;font-variant-ligatures: =
normal;font-variant-caps: normal;orphans: 2;text-align:start;widows: 2;-web=
kit-text-stroke-width: 0px;text-decoration-style: initial;text-decoration-c=
olor: initial;word-spacing:0px"><span lang=3D"EN-US" style=3D"font-size:10.=
0pt;font-family:&quot;Times New Roman&quot;,serif;color:#333333">Sheng &#43=
; Toerless<o:p></o:p></span></pre>
<pre style=3D"margin-bottom:7.5pt;background:white"><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:&quot;Times New Roman&quot;,serif;color=
:#333333"><o:p>&nbsp;</o:p></span></pre>
</div>
</body>
</html>

--_000_5D36713D8A4E7348A7E10DF7437A4B928183CBB8NKGEML515MBXchi_--


From nobody Sun Mar 18 02:45:38 2018
Return-Path: <mcr@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85156127077 for <anima@ietfa.amsl.com>; Sun, 18 Mar 2018 02:45:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 QohCTbo1V26I for <anima@ietfa.amsl.com>; Sun, 18 Mar 2018 02:45:35 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A9331200FC for <anima@ietf.org>; Sun, 18 Mar 2018 02:45:35 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:67c:370:128:a11:96ff:fe01:81e0]) by relay.sandelman.ca (Postfix) with ESMTPS id CED621F95D; Sun, 18 Mar 2018 09:45:32 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 11BE7622; Sun, 18 Mar 2018 09:45:03 +0000 (GMT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
CC: "Brian Weis \(bew\)" <bew@cisco.com>, "Pete Beal \(pbeal\)" <pbeal@cisco.com>, "Max Pritikin \(pritikin\)" <pritikin@cisco.com>, "John Manuel \(jmanuel\)" <jmanuel@cisco.com>
In-reply-to: <EBA47702-F51F-4C5D-8240-86730427206B@cisco.com>
References: <5086bdbc-b37a-baf6-81e0-58e361d39ea3@cisco.com> <8f2e8ff8-fc4c-73d1-5941-29fe35e4d511@cisco.com> <3261.1520994236@obiwan.sandelman.ca> <31bbfaf1-3628-66c6-868e-819e978bb058@cisco.com> <27525.1521035830@obiwan.sandelman.ca> <EC89DFFF-7268-4444-AE69-96B0AD190941@cisco.com> <27386.1521102254@dooku.sandelman.ca> <EBA47702-F51F-4C5D-8240-86730427206B@cisco.com>
Comments: In-reply-to "Brian Weis (bew)" <bew@cisco.com> message dated "Thu, 15 Mar 2018 22:28:56 +0000."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sun, 18 Mar 2018 09:45:03 +0000
Message-ID: <808.1521366303@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/4c7FL_z3FUKVXPb8QizKCDcEETw>
Subject: Re: [Anima] BRSKI pledge cert/key/script stuff
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Mar 2018 09:45:36 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Brian Weis (bew) <bew@cisco.com> wrote:
    > So I=E2=80=99ve been trolling through the code, and discovered that t=
he http
    > application/* headers do not match the latest release. I also hadn=E2=
=80=99t realized
    > that the Pledge can send either "application/json=E2=80=9D (unsigned)=
 or
    > "application/voucher-cms+json=E2=80=9D (signed) vouchers. I=E2=80=99v=
e changed the
    > unsigned string to match the draft. But this raises a question:

    > If the Pledge sends an unsigned Voucher, I would expect the Registrar=
 to
    > forward it in the MASA server as the "prior-signed-voucher=E2=80=9D. =
But in fact
    > it=E2=80=99s not signed, and I see elsewhere that the Registrar is su=
pposed to
    > send it signed.  From Section 3 of -12:

    > The "prior-signed-voucher-request" leaf is be used in Registrar
    > voucher-requests to the Pledge voucher-request.  It contains the
    > encoded (signed form) of the Pledge voucher-request.

    > What is the correct behavior?

I've opened this as issue:
     https://github.com/anima-wg/anima-bootstrap/issues/48

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -=3D IPv6 IoT consulting =3D-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJarjUeAAoJEJVM4Vb9/EKQggQH/j1Lyn0R2Duxl2xFunbZPTSt
YvIMM5RHEM9t85b5RzXJ2w7wFVfnTLvnm+eTXSaQIKgBTb2CxUZyHB/hX10/J8SJ
hrQeQQovZcxb38+tsIgAG1bpzjr5pS7md00rfTNf5RSububKR1oyr5rW/jiafdcf
CUZDcc8gLE4NUavh4p8pDNAJm0bp2lrEOQjatheJjw/bvyN65nwU5X8REzNJzp49
sNujOVeTrSuDhmSrXtUPlYI7n2esC9lp2xHpFPs3rH2BPrnRWrPN4uwKa3L0vMT4
bxb696cP7m4KZlnVCgzPMfMRoY4pNBZ8JrcgTKss3Y0dGiwihJQAehTgmw4ysJk=
=3bp5
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Mar 18 02:48:22 2018
Return-Path: <mcr@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 395E5127077 for <anima@ietfa.amsl.com>; Sun, 18 Mar 2018 02:48:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 Qu0xLwvmKG0k for <anima@ietfa.amsl.com>; Sun, 18 Mar 2018 02:48:18 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 447381200FC for <anima@ietf.org>; Sun, 18 Mar 2018 02:48:18 -0700 (PDT)
Received: from dooku.sandelman.ca (dhcp-86ae.meeting.ietf.org [31.133.134.174]) by relay.sandelman.ca (Postfix) with ESMTPS id 2464E1F95D; Sun, 18 Mar 2018 09:48:17 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 8B3A1622; Sun, 18 Mar 2018 09:47:46 +0000 (GMT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
CC: "Brian Weis \(bew\)" <bew@cisco.com>, "Pete Beal \(pbeal\)" <pbeal@cisco.com>, "Max Pritikin \(pritikin\)" <pritikin@cisco.com>, "John Manuel \(jmanuel\)" <jmanuel@cisco.com>
In-reply-to: <EBA47702-F51F-4C5D-8240-86730427206B@cisco.com>
References: <5086bdbc-b37a-baf6-81e0-58e361d39ea3@cisco.com> <8f2e8ff8-fc4c-73d1-5941-29fe35e4d511@cisco.com> <3261.1520994236@obiwan.sandelman.ca> <31bbfaf1-3628-66c6-868e-819e978bb058@cisco.com> <27525.1521035830@obiwan.sandelman.ca> <EC89DFFF-7268-4444-AE69-96B0AD190941@cisco.com> <27386.1521102254@dooku.sandelman.ca> <EBA47702-F51F-4C5D-8240-86730427206B@cisco.com>
Comments: In-reply-to "Brian Weis (bew)" <bew@cisco.com> message dated "Thu, 15 Mar 2018 22:28:56 +0000."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sun, 18 Mar 2018 09:47:46 +0000
Message-ID: <1000.1521366466@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/JkeYKDRognx_RQEQjMuD2US8nb8>
Subject: Re: [Anima] BRSKI pledge cert/key/script stuff
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Mar 2018 09:48:20 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Brian Weis (bew) <bew@cisco.com> wrote:
    > Another unrelated question. What is the correct media type response f=
or
    > the authorization log? Section 5.7 doesn=E2=80=99t seem to say. I ass=
ume that the
    > response is unsigned JSON, so the http headers should say =E2=80=9Cap=
plication/json=E2=80=9D.
    > Is that right?

    > (For some reason my code has the response sent as a CMS signed object,
    > but that seems to be incorrect.)

Opened as:
       https://github.com/anima-wg/anima-bootstrap/issues/49

I think that you are correct, it should be application/json.
The results should be not be signed in any way.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -=3D IPv6 IoT consulting =3D-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJarjXCAAoJEJVM4Vb9/EKQQXsH/2atHrucpn+Kl3uqZnmdZHju
Vi+sxdjHXkyYyPUtoSHNAyYk9lgQT2ZOgfTGrcuTW5LZ616J0n79hiNWr2FHlONA
hWXci2CNTi6oiHp2uME8ucZtKRzUcYuP4JkqfidDukyKaIPdZ9OdulxYYDDcR+0/
Adr17gl2z7i//CFejeVirDSIMQzJj0XhDVuFQmtvg56YyGSQT4QkerB3qJi/WS9V
gPl/wcBoV+z5cwxROsKBOO1Ku4iLYtezjfzoL2EYQTeGbxElZT/KVCOv9QTdmv93
sdccL8MAvniFT37Rgayd2Ol0z5THfWoCMpVCxbbs5hTFqN6XGXWsmq2EIn2N34s=
=hvAj
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Mar 20 03:24:35 2018
Return-Path: <laurent.ciavaglia@nokia-bell-labs.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18CA6124319 for <anima@ietfa.amsl.com>; Tue, 20 Mar 2018 03:24:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.91
X-Spam-Level: 
X-Spam-Status: No, score=-2.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=-1, 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=nokia.onmicrosoft.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 5S-9CdADYcGM for <anima@ietfa.amsl.com>; Tue, 20 Mar 2018 03:24:32 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01on0126.outbound.protection.outlook.com [104.47.0.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E09FB1242F7 for <anima@ietf.org>; Tue, 20 Mar 2018 03:24:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector2-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=XKwcvv1aoMubHO9aVuNbxnPpvsmVJTqOqWOfeoenTJE=; b=NqzTXX/7Kl155fYEj+6Cs0lR8d1zU3fcuHZytx5ws+rq4vJ+g7I6cvXNnIDXwjHFAApUR0RcZFmgWOU+aWfcQO90ERyvQv0NLQCNr4tbnDbC3DzsZe2re6XSryliuc4VMIt5UZV7+lmC4j+boWdcQPXPGB5jEfKjCuCx4vP6O2k=
Received: from HE1PR0701MB2203.eurprd07.prod.outlook.com (10.168.36.134) by HE1PR0701MB2538.eurprd07.prod.outlook.com (10.168.129.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.609.6; Tue, 20 Mar 2018 10:24:28 +0000
Received: from HE1PR0701MB2203.eurprd07.prod.outlook.com ([fe80::65f6:49d7:ef76:6990]) by HE1PR0701MB2203.eurprd07.prod.outlook.com ([fe80::65f6:49d7:ef76:6990%4]) with mapi id 15.20.0609.009; Tue, 20 Mar 2018 10:24:28 +0000
From: "Ciavaglia, Laurent (Nokia - FR/Paris-Saclay)" <laurent.ciavaglia@nokia-bell-labs.com>
To: "anima@ietf.org" <anima@ietf.org>
Thread-Topic: Related work for draft-carpenter-anima-asa-guidelines
Thread-Index: AdPANaAvJNJkJA2lRhW/bdp52/tnag==
Date: Tue, 20 Mar 2018 10:24:28 +0000
Message-ID: <HE1PR0701MB22033E1E70EC80F3897ACC84E8AB0@HE1PR0701MB2203.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2a01:cb04:73c:ab00:8c88:28a6:3fc3:b1e1]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR0701MB2538; 7:niZdYUK8klBYaTy9GVUTk9aaLqyThYxJL+Tgu9fHa4KrLz2nfhSkEs86GXtdiPhKyDXatIsy63T5xDEuAd3EZTn3+1Vb31Aed8+1ZlL6D1R/gHEN7sCm+P8EiGLsb9QT1GRGi1aW4HOnuautywwRStfXwxedjW4C167p2W9BdCtEnvE4UOy6OfVwSCgM34ngnGZiEoaCjN/RO2Pnzc0dCR6ww1jbdtbq9rqXboUNP1ZDtp61BjvQ6srIBkru1otL
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: a14dc40e-6ac0-4f27-7136-08d58e4cc35b
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7193020); SRVR:HE1PR0701MB2538; 
x-ms-traffictypediagnostic: HE1PR0701MB2538:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=laurent.ciavaglia@nokia-bell-labs.com; 
x-microsoft-antispam-prvs: <HE1PR0701MB2538E8B416ABB4E6C1D4159FE8AB0@HE1PR0701MB2538.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(10201501046)(3231221)(11241501184)(944501309)(52105095)(6055026)(6041310)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123560045)(20161123558120)(6072148)(201708071742011); SRVR:HE1PR0701MB2538; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0701MB2538; 
x-forefront-prvs: 061725F016
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(39380400002)(39860400002)(396003)(346002)(376002)(199004)(189003)(558084003)(2906002)(5630700001)(478600001)(2501003)(790700001)(3280700002)(6116002)(2351001)(8676002)(5660300001)(14454004)(5250100002)(106356001)(1730700003)(68736007)(33656002)(6436002)(5640700003)(9326002)(55016002)(25786009)(81166006)(81156014)(53936002)(9686003)(2900100001)(54896002)(6306002)(8936002)(7696005)(3660700001)(7736002)(316002)(74316002)(6916009)(105586002)(102836004)(46003)(99286004)(186003)(86362001)(97736004)(6506007)(90052001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR0701MB2538; H:HE1PR0701MB2203.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: nokia-bell-labs.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: XNsUQgwsNZjB7ILl9lzGJRg/xUSAl3pGi7rXXuOlR2C81vxSscCzuBeALU7FuRkO0oV83ZBFDXlaMhNxBNFloSkJ7ePnon5Rr1uMTjZ2V/5TQn71+XYLPxP7tOTh/lFuh92JEWQhGXtHjh4ijxQlPGUa4ijuN0Fq8reC93XJO8TZ/OzTmKjqW+c5QWx3yCOqcZBpc6vvj2LjHuiU+I0DHkZvVO6xiympW5sIyJyC/YRsGuAfcChvUWDsFIoQWipUNxeuEROrTZQqBCGKfBKxNNfDAE0bgFQpkTs+gnRRhRDVUyGWnhLy6x1QCZvgwnsctv2omitzhipAbrX/Rz9Abw==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HE1PR0701MB22033E1E70EC80F3897ACC84E8AB0HE1PR0701MB2203_"
MIME-Version: 1.0
X-OriginatorOrg: nokia-bell-labs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: a14dc40e-6ac0-4f27-7136-08d58e4cc35b
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Mar 2018 10:24:28.8220 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2538
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/HuAM59UFXKJ78A2tjcH-6e7B-qU>
Subject: [Anima] Related work for draft-carpenter-anima-asa-guidelines
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2018 10:24:34 -0000

--_000_HE1PR0701MB22033E1E70EC80F3897ACC84E8AB0HE1PR0701MB2203_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello,

Sheng you mentioned two works we should liaise to, which could help getting=
 deployment experience.
Bing mentioned an ID but I cannot find it under the ANIMA related docs (not=
 T2TRG ones).

Could you share the pointers or contacts, please?

Thanks, Laurent.



--_000_HE1PR0701MB22033E1E70EC80F3897ACC84E8AB0HE1PR0701MB2203_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Courier New";
	font-variant:normal !important;
	color:windowtext;
	text-transform:none;
	text-decoration:none none;
	vertical-align:baseline;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Hello,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Sheng you mentioned two works we should liaise to, which c=
ould help getting deployment experience.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Bing mentioned an ID but I cannot find it under the ANIMA =
related docs (not T2TRG ones).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Could you share the pointers or contacts, please?<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Thanks, Laurent.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_HE1PR0701MB22033E1E70EC80F3897ACC84E8AB0HE1PR0701MB2203_--


From nobody Tue Mar 20 03:40:15 2018
Return-Path: <laurent.ciavaglia@nokia-bell-labs.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AD9B126CD6 for <anima@ietfa.amsl.com>; Tue, 20 Mar 2018 03:40:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level: 
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-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=nokia.onmicrosoft.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 P599mN2YNAUP for <anima@ietfa.amsl.com>; Tue, 20 Mar 2018 03:40:09 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0133.outbound.protection.outlook.com [104.47.2.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 627461242F7 for <anima@ietf.org>; Tue, 20 Mar 2018 03:40:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector2-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=P0c6sj8zyeDUrc0Y7Zglf4KRck1W8insspNi6TFuA9c=; b=bCKvzSxC/d3H5snz8sQCLLvLHiPveakWz3JLNvv5Bfnb7VnBN5JDarDYohD0xkq8d6Kt8Kw6CTfqb6EH2xVLWYt/h5Z1e2v1QlDCV0nA1RdVlH5GCsKuH63Rz6iVmr8K55aG0edUPmwii8tgNSNXjG4T40fdHQ+q03wbQbBwjNI=
Received: from HE1PR0701MB2203.eurprd07.prod.outlook.com (10.168.36.134) by HE1PR0701MB2908.eurprd07.prod.outlook.com (10.168.92.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.609.6; Tue, 20 Mar 2018 10:39:59 +0000
Received: from HE1PR0701MB2203.eurprd07.prod.outlook.com ([fe80::65f6:49d7:ef76:6990]) by HE1PR0701MB2203.eurprd07.prod.outlook.com ([fe80::65f6:49d7:ef76:6990%4]) with mapi id 15.20.0609.009; Tue, 20 Mar 2018 10:39:59 +0000
From: "Ciavaglia, Laurent (Nokia - FR/Paris-Saclay)" <laurent.ciavaglia@nokia-bell-labs.com>
To: "anima@ietf.org" <anima@ietf.org>
Thread-Topic: Comments from Alex G. on draft-carpenter-anima-asa-guidelines
Thread-Index: AdPANbZMCdQPZ8rGTyW/Fn6F6zhJ2g==
Date: Tue, 20 Mar 2018 10:39:58 +0000
Message-ID: <HE1PR0701MB22037C4685F11D0C6983451BE8AB0@HE1PR0701MB2203.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=laurent.ciavaglia@nokia-bell-labs.com; 
x-originating-ip: [2a01:cb04:73c:ab00:8c88:28a6:3fc3:b1e1]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR0701MB2908; 7:pvSLk7pSpplGo47xuUxTCU9AMATS8VHlrpp6sa05zsLkjsbwgecssdhCQM7Tp6gDVl733Okzw2XjxXADj1ban0Ihg28kPtO9ST+5L0Wd0BMwliNgd8oJIcuwse+rcrXVDfvLhzk7z79a2MCwG48sZB47wpuEZk1r9qox5ALLgUgTRzmiZg07ezVJzWP6Ia/ZnEGvmezZUR6MiCuGEU5VRfj+4jM+N6czemPywTxU3SXz2Yisr9qQWPg6SP5sI9lv
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 8fee8ac4-1323-41e1-4ca8-08d58e4eedcd
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7193020); SRVR:HE1PR0701MB2908; 
x-ms-traffictypediagnostic: HE1PR0701MB2908:
x-microsoft-antispam-prvs: <HE1PR0701MB2908914605B76A665A1E97BFE8AB0@HE1PR0701MB2908.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3231221)(11241501184)(944501244)(52105095)(3002001)(93006095)(93001095)(10201501046)(6055026)(6041310)(20161123560045)(20161123562045)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(6072148)(201708071742011); SRVR:HE1PR0701MB2908; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0701MB2908; 
x-forefront-prvs: 061725F016
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(376002)(396003)(346002)(39860400002)(39380400002)(199004)(189003)(7736002)(790700001)(97736004)(14454004)(33656002)(478600001)(106356001)(2900100001)(6116002)(105586002)(25786009)(2351001)(6436002)(53936002)(55016002)(5640700003)(186003)(2906002)(102836004)(9686003)(54896002)(6306002)(6506007)(2501003)(6916009)(316002)(46003)(9326002)(68736007)(1730700003)(3660700001)(8936002)(74316002)(81166006)(5660300001)(8676002)(81156014)(86362001)(5250100002)(5630700001)(3280700002)(59450400001)(7696005)(99286004)(90052001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR0701MB2908; H:HE1PR0701MB2203.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: nokia-bell-labs.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 0X03W8MJBGZ6wBqnaBhOygddbtwOQlKzCOmXJx4KiU6SD68UqngUklcnMJslQimFRbDyvq/BeBYHsPTfSZ3/ykW6OoIzv4+X4ZH8s1CykVPrjg+bdCL7OtrEhgx7y2HFpPF0ojhd9LY9YUjnkVHpyde86pfqjIvLXUvW8+wF9tp0fubuaWZ2Enn8CyCStgOzbdnQhu3FQnHdj5aGfe5I0TQcWfikIKq/0mpoOtfFVAv5+tFktqQWFJSxlQATmkPM/RzAE5e7rFQLu0KmN2XinhzEWTuVSmnrst17XxP+9kB1cIzkUHl7P252ebMeW59vu2o2KDX5eJYC6l87+YkMaw==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HE1PR0701MB22037C4685F11D0C6983451BE8AB0HE1PR0701MB2203_"
MIME-Version: 1.0
X-OriginatorOrg: nokia-bell-labs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 8fee8ac4-1323-41e1-4ca8-08d58e4eedcd
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Mar 2018 10:39:58.9791 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2908
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/18DVZzgx27c5wonviTEE9lKB-Qs>
Subject: [Anima] Comments from Alex G. on draft-carpenter-anima-asa-guidelines
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2018 10:40:11 -0000

--_000_HE1PR0701MB22037C4685F11D0C6983451BE8AB0HE1PR0701MB2203_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Alex,

Thanks for your comments on draft-carpenter-anima-asa-guidelines.

If I get it correctly you raised the following points:

  1.  -better describe what ASA are: rather application or network service,=
 and better describe the border between the two and implications for ASA de=
signers/developers in the draft.

I think it is an important (and not so simple) topic and worth being discus=
sed.

Would welcome views from the group.



  1.  -NFV is an important area for future networks, and more focus for ANI=
MA and ASA should be devoted.

Agreed; However, I'm not aware that NFV community is following ANIMA work a=
nd guidelines on autonomic VNF design/development. Although there are sever=
al autonomic/self-* behavior/functionality being developed in NFV.

There is clearly a gap here, and a difference in approach.



  1.  -You mentioned something about the decoupling of self-* functionality=
 (self-configuration, self-healing...)

Not sure I get fully what was your comment on this aspect. Could you clarif=
y / develop?

Thank you.
Best regards, Laurent.


--_000_HE1PR0701MB22037C4685F11D0C6983451BE8AB0HE1PR0701MB2203_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Courier New";
	font-variant:normal !important;
	color:windowtext;
	text-transform:none;
	text-decoration:none none;
	vertical-align:baseline;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:678240111;
	mso-list-type:hybrid;
	mso-list-template-ids:532475278 530848946 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:54.0pt;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:90.0pt;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:126.0pt;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:162.0pt;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:198.0pt;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:234.0pt;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:270.0pt;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:306.0pt;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:342.0pt;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Hi Alex,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Thanks for your comments on draft-carpenter-anima-asa-guid=
elines.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">If I get it correctly you raised the following points:<o:p=
></o:p></span></p>
<ol style=3D"margin-top:0cm" start=3D"1" type=3D"1">
<li class=3D"MsoListParagraph" style=3D"margin-left:18.0pt;mso-list:l0 leve=
l1 lfo1"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;">-better describe what ASA are: rather application or network service, an=
d better describe the border between the two and
 implications for ASA designers/developers in the draft.<o:p></o:p></span><=
/li></ol>
<p class=3D"MsoListParagraph" style=3D"margin-left:54.0pt"><span style=3D"f=
ont-size:10.0pt;font-family:&quot;Courier New&quot;">I think it is an impor=
tant (and not so simple) topic and worth being discussed.<o:p></o:p></span>=
</p>
<p class=3D"MsoListParagraph" style=3D"margin-left:54.0pt"><span style=3D"f=
ont-size:10.0pt;font-family:&quot;Courier New&quot;">Would welcome views fr=
om the group.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:54.0pt"><span style=3D"f=
ont-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></spa=
n></p>
<ol style=3D"margin-top:0cm" start=3D"2" type=3D"1">
<li class=3D"MsoListParagraph" style=3D"margin-left:18.0pt;mso-list:l0 leve=
l1 lfo1"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;">-NFV is an important area for future networks, and more focus for ANIMA =
and ASA should be devoted.<o:p></o:p></span></li></ol>
<p class=3D"MsoListParagraph" style=3D"margin-left:54.0pt"><span style=3D"f=
ont-size:10.0pt;font-family:&quot;Courier New&quot;">Agreed; However, I&#82=
17;m not aware that NFV community is following ANIMA work and guidelines on=
 autonomic VNF design/development. Although there are
 several autonomic/self-* behavior/functionality being developed in NFV.<o:=
p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:54.0pt"><span style=3D"f=
ont-size:10.0pt;font-family:&quot;Courier New&quot;">There is clearly a gap=
 here, and a difference in approach.
<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:54.0pt"><span style=3D"f=
ont-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></spa=
n></p>
<ol style=3D"margin-top:0cm" start=3D"3" type=3D"1">
<li class=3D"MsoListParagraph" style=3D"margin-left:18.0pt;mso-list:l0 leve=
l1 lfo1"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;">-You mentioned something about the decoupling of self-* functionality (s=
elf-configuration, self-healing&#8230;)<o:p></o:p></span></li></ol>
<p class=3D"MsoListParagraph" style=3D"margin-left:54.0pt"><span style=3D"f=
ont-size:10.0pt;font-family:&quot;Courier New&quot;">Not sure I get fully w=
hat was your comment on this aspect. Could you clarify / develop?<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Thank you.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Best regards, Laurent.</span><span lang=3D"FR"><o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_HE1PR0701MB22037C4685F11D0C6983451BE8AB0HE1PR0701MB2203_--


From nobody Tue Mar 20 11:18:31 2018
Return-Path: <mcr@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63E49127978 for <anima@ietfa.amsl.com>; Tue, 20 Mar 2018 11:18:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 D6h5opUgwxSk for <anima@ietfa.amsl.com>; Tue, 20 Mar 2018 11:18:28 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1DE5127286 for <anima@ietf.org>; Tue, 20 Mar 2018 11:18:27 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [217.138.37.114]) by relay.sandelman.ca (Postfix) with ESMTPS id 4131D1F95D for <anima@ietf.org>; Tue, 20 Mar 2018 18:18:24 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id E47B3158A; Tue, 20 Mar 2018 18:17:47 +0000 (GMT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
In-reply-to: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de>
References: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de>
Comments: In-reply-to Toerless Eckert <tte@cs.fau.de> message dated "Wed, 14 Feb 2018 02:09:10 +0100."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
X-Attribution: mcr
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 20 Mar 2018 18:17:47 +0000
Message-ID: <13940.1521569867@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/LJH9gTCQGFiGAqG7x4lyEf64ZMs>
Subject: Re: [Anima] Shepherd review draft-ietf-anima-bootstrapping-keyinfra-09 (part 4?)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2018 18:18:30 -0000

--=-=-=
Content-Type: text/plain


MAX: please look for your name.

Toerless Eckert <tte@cs.fau.de> wrote:
    > Section 5)

    > a) Suggest changing the title to "Protocol Details (Pledge - Registrar
    > - MASA / CA)"
    > to distinguish from Section 4. Might consider also to move up section

renamed.

    > b) MASA URI is "https:// authority "./well-known/est".
    > ^
    > missing a " ?

already fixed.

    > c) BRSKI-EST connections SHOULD use persistent connections
    > The intention of this guidance is to ensure the provisional TLS
    > authentication occurs only once and is properly managed.

    > This is not clear to me, please rephrase.

    > - What does "properly managed" mean ?

I no longer recall.
I think it's content-free.  It means don't throw away the connection
each time or do dumb things with your SSL context.

    > - Why would provisional TLS authentication have to occur more than once
    > without persistent connection ?

        <t>
          While EST section 3.2 does not insist upon use of HTTP 1.1
          persistent connections, BRSKI-EST connections SHOULD use persistent
          connections.  The intention of this guidance is to ensure the
          provisional TLS state occurs only once, and that the subsequent
          resolution of the provision state is not subject to a MITM attack
          during a critical phase.
        </t>

    > The first connection only retrieves the voucher, but then lets say the
    > Pledge closes the connection and builds a new one for EST
    > enrollment. On that second one it would not need to do provisional
    > authentication. /cacerts after /requestvoucher ?

I agree that it's possible to come up with a number of places in which
one could restart the TLS connection, at which point a MITM would either
be detected, or would cause a failure, but I would rather not open this door.

The pledge would have to remember the server's certificate and make sure that
it always connects to a server with the same (identical) certificate.

If the JRC is implemented in a load-balanced scenario with a front-end
*TCP* (not SSL) proxy that distributes load, then it is possible that it
would be legitimate for the different servers to have different
certificates.  As long as the voucher comes out correct, that's fine.

But, if the pledge is directed to different servers, which a non-persistent
connection could cause to occur, then the pledge will have a hard time.

What if the single server executes a planned reboot, and when it restarts, a
new (fresher) certificate has been installed?    The persistent connection
could be tuned to keep server from rebooting until that transaction is over.

Finally, the non-persistent connections could be redirected by the Join Proxy
to different JRCs!

    > d)  Q: How would BRSKI work in the absence of persistent connections or
    > in the presence of failures ? I guess each request from the pledge is a
    > standalone transaction and the pledge would just repeat them until it
    > succeeds or until a return code would indicate that the Registrar does
    > not support this step and the pledge has to terminate.

The requests from the pledge are not standalone transactions.
They are a series of connections that build towards a result.
I don't think we need to support non-persistent connection.

    > Aka: The way i see it, the reason for persistent connections is really
    > just
    > avoiding unnecessary repeated (expensive) TLS connection setup...

yes.  So, couldn't you have edited your comments then?

    > e)  "If the Registrar responds with a redirection to other web origins"

    > A reason for this rule should be written into that paragraph.
    > ... This is to minimize attacks by fake registrars trying to
    > indefinitely redirect a pledge.

MAX: I think that there are other reason as well?
MAX: Also, the pledge can't go anywhere by URL, only to where the Proxy
     directs it, so really can any redirection be accepted?
     Of course, it can do Host:

I have opened ticket: https://github.com/anima-wg/anima-bootstrap/issues/50

    > f)  "It should proceed to other discovered Registrars if there are any"

    > Pledes don't discover Registrars, the discover Proxies.
    > the Proxy can see a couple redundant Registrars.

fixed with:

            <t>
              To avoid blocking on a single erroneous Registrar the Pledge
              MUST drop the connection after 5 seconds in which there has
              been no progress on the TCP connection.
              It should proceed to
                connect to any other Registrar's via any other discovered
                Proxies if there are any.  If there were no
                other Proxies discovered, the Pledge MAY continue to wait,
                as long as it is concurrently listening for new Proxy
                announcements.
            </t>


    > f.1) "If necessary the Pledge calls the EST defined /cacerts method to
    > obtain the domain owners' CA certificate."

    > Please add an explanation when/why this is necessary. This seems to
    > contradict the statement in 5.8.1 about not doing /cacerts,/fullcmc
    > during Bootstrap but only during enrollment: "Although these
    > limitations are acceptable during initial bootstrapping"
    > (aka: "no need for /cacerts during bootstrap").

Now https://github.com/anima-wg/anima-bootstrap/issues/51

    > g)  After "This moves the BRSKI-EST TLS connection out of the provisional state." add:

    > - Afterwards the Pledge trusts this and other Registrars using the same
    > trust anchor. It MAY permit more than one redirects, but it MAY still
    > time out the registrar for further REST operations and revert to
    > another one.

We need to talk more about ticket #50.

    > - Mandatory boostrap steps conclude with Voucher Status Telementry (see
    > XXX)

done.

    > - Move "Optionally, the BRSKI- EST TLS connection can now be used for EST enrollment."
    > out of the bullet list merge wi next sentence ("The extensions...").

done.

    > h)  "In the language of RFC6125 this provides for a SERIALNUM-ID category of identifier.."

    > RFC6125 does not use the term SERIALNUM-ID and BRSKI does not use this
    > term outside of this paragraph either, so it seems redundant. The whole
    > paragraph is also quite dense,
    > so maybe rewrite/simplify the language.

We thought a lot about how one does matching of identities in PKIX
SubjectAltNames', and RFC6125 provides the best guidance.
I split the paragraph up.

    > Would suggest to also move any details o the whitelist logic
    > desccription to 5.1,
    > 5.0 is just overview. And in 5.1 you mention TLS setup uses RFC7030
    > mechanisms while in 5.0 it refers to RFC6125, so i think it would
    > become easier to write & read if tht 5.0 whitelisting stuff was moved
    > into 5.1 paragraphs refering to EST TLS setup.

Actually, I agree that 5.0 is way too detailed *IN GENERAL*
          https://github.com/anima-wg/anima-bootstrap/issues/52

    > Suggested append if you agree with it (whatever wording you like):

    > a) "nonce:  The Pledge voucher-request MUST contain" ...
    > ..."Doing so ensures Section 2.5 functionality"

    > If one just follows the reference to section 2.5, it looks contradictory:
    > "_If_ the voucher contains a nonce then the Pledge MUST confirm "

    > Please clarify, this is confusing:
    > - If the nonce is a MUST because of section 2.5, then the MUST would
    > only have to
    > apply to RTCless Pledges. But its not clear to me why... (forgot our
    > discussions,
    > and readers where never part of them, so explanation would be nice).

5.2 is about requesting a voucher, not about checking.
We decided that all voucher requests MUST have nonces, to enable noncefull
freshness, but whether or not vouchers are required to have nonces is
a manufacturer's decision.

    > - fix to "MUST NOT be reused for _MULTIPLE_ bootstrapping attempts
    > IMHO also: (especially not across repeated first bootstrap attempts
    > after power cycling).

done.

    > Section 5.3 1)

    > a) "The Registrar initiates the connection and uses the MASA URL obtained
    > as described in Section 2.7 for RFC6125 authentication of the MASA server."

    > Q: Does this mean:
    > "The Registrar initiates the connection and uses the DNS name of the
    > MASA URL obtained
    > as described in Section 2.7 for (RFC6125) authentication of the MASA
    > server certificate."

MAX, do you think we need to more this precise?
I think that we really want people to read 6125, not just guess.

    > Aka: for the less PKIX/Websecurity initiated readers like me, writing out
    > what is actually implied could make the sentence easier to parse
    > (instead of having to read more of RFC6125.

But, I want you to read 6125 rather than guess.
Or use a library (libcurl or whatever) that does the right thing.

I'll stop here, since there are a number of issues open.

https://goo.gl/8sQfkb for rfcdiff between -12 and github content.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJasVBLAAoJEJVM4Vb9/EKQWoMH/1AYLim87ApzV719YZG4Ywxm
U3nQzui/r5M+vyOaVzo/6a7Hf60/rYrqf/GbQREWtUgSfpdwdu7eMSeL0fe/ZQv/
0ZicIGNCbGua6x42y7z5fcJutHVUIyyo0Ornlf4ta+VMnWJgDFlyH7vrp/EXBNCE
/G59oVa1+e5RuSSF1ltR/vjbofafnVWVac9h71UjQm8yANEI7p1jqGta82K1VRRj
r1o9CzL3jwe1H0K1k3ECSW2j39FIQ5cEdBRlAfw3eHqBOUoGB4+yfMBDvoEYJIaU
DrvD7N3swzEsdRzVCe9/nNPVwUf7ee8p4rB389YatCUSCls4RpmkcM4MlU+eaP4=
=6dTr
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Mar 20 13:00:58 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53D96126C83 for <anima@ietfa.amsl.com>; Tue, 20 Mar 2018 13:00:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 huOO4qpu0sL9 for <anima@ietfa.amsl.com>; Tue, 20 Mar 2018 13:00:54 -0700 (PDT)
Received: from mail-pl0-x22f.google.com (mail-pl0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) (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 CA75012025C for <anima@ietf.org>; Tue, 20 Mar 2018 13:00:54 -0700 (PDT)
Received: by mail-pl0-x22f.google.com with SMTP id f5-v6so1663864plj.13 for <anima@ietf.org>; Tue, 20 Mar 2018 13:00:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=u/bFlASiiAbOLKWEI/Zvk+qnhQ29dJhUKoVsYYsUNg8=; b=PDNYdp9MSij53cEdhyiBg0vUs3s6raRPigyhhw0SWppGhBtpYumB3uBtd13KKFMT/D E3I2l2+EA6TMPrdOoU45YJr1i6AGfcKV0axhiFvtbdisGY1/FlC10SAgqYNSUt8liyhU PfpHPqtyZRd8V+gtw/M2Z24GzoWcetCDJN4c/S8vEFvRbIitapcns17h26/wIsnZW5A1 t2yeUAwNAM1vt13CyFK0gNo/riYTub7Gsdw9vN7VH0F7VWaIJJ922uXod4h4Je5iZ52K paSKxb+M1gxoNgdQYTx63lkGoZ7jynoHN7N3N9lATL6zZs4apLKdoYA2+l1fia1uXgZ4 vUkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=u/bFlASiiAbOLKWEI/Zvk+qnhQ29dJhUKoVsYYsUNg8=; b=AJxiE3nFoCxYee3Oa+S2Nqj9XmSEWvPt2jt6nrZlcB2BJUILGKfe/uqr8cY42Qotj0 jT7/fIDJMO/E9eMRLBxkMxyO3d8YuxGmQqilgqXAWa2X6yuL55kI2ugEiR1d8no4oiDs HCwISOr7YNxsZciSkknupJMq4MTcp/tFh+4rT/09iXH9Tw/CjOTqaLVLPfjDQNE9hwDJ K5Y3VSfHicIVQ+uOO/qn9kx+3XQek2QpO5ZKO7TBLLV5YNlVdMw2gF3krGt9eImjpkZn 3ngCM9GdePkEP6fpBUuLG9oqb3ogrSa5f72gIMflISgnM/w5o2Vg3prO0zpSh5wkkiLN sJwA==
X-Gm-Message-State: AElRT7HXTRMpZbprDlwJpyuYB6nJn/c19ZvuwAP6/LgFLe4HsjC18XUa RjSnmw9z7UD6/qEsex3gLajr8Q==
X-Google-Smtp-Source: AG47ELtN6rJy2Yx3XvqeplAZTS5LyoLGe5OmEeezELg3COsGH40PRE6e3np+RpX7AO2Boeuwn1mnSA==
X-Received: by 2002:a17:902:7401:: with SMTP id g1-v6mr18084230pll.4.1521576054023;  Tue, 20 Mar 2018 13:00:54 -0700 (PDT)
Received: from [192.168.178.30] (86.225.69.111.dynamic.snap.net.nz. [111.69.225.86]) by smtp.gmail.com with ESMTPSA id b18sm4695461pfi.34.2018.03.20.13.00.51 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Mar 2018 13:00:52 -0700 (PDT)
Sender: Brian Carpenter <becarpenter46@gmail.com>
To: anima@ietf.org
References: <HE1PR0701MB22037C4685F11D0C6983451BE8AB0@HE1PR0701MB2203.eurprd07.prod.outlook.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <5b0c9c0c-8661-d41f-c4d1-eb058b87f944@gmail.com>
Date: Wed, 21 Mar 2018 09:00:52 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <HE1PR0701MB22037C4685F11D0C6983451BE8AB0@HE1PR0701MB2203.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/ptkqelBW8FCvzs3y93XLn4W6fz0>
Subject: Re: [Anima] Comments from Alex G. on draft-carpenter-anima-asa-guidelines
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2018 20:00:56 -0000

On 20/03/2018 23:39, Ciavaglia, Laurent (Nokia - FR/Paris-Saclay) wrote:
> Hi Alex,
> 
> Thanks for your comments on draft-carpenter-anima-asa-guidelines.
> 
> If I get it correctly you raised the following points:
> 
>   1.  -better describe what ASA are: rather application or network service, and better describe the border between the two and implications for ASA designers/developers in the draft.
> 
> I think it is an important (and not so simple) topic and worth being discussed.
> 
> Would welcome views from the group.

Yes, these are aspects that we discussed in NMRG and also in the UCAN BOF and early
days of the WG. Probably we have most of the points scattered around in various
documents and meeting minutes, but we need to collect them in one place.

>   1.  -NFV is an important area for future networks, and more focus for ANIMA and ASA should be devoted.
> 
> Agreed; However, I'm not aware that NFV community is following ANIMA work and guidelines on autonomic VNF design/development. Although there are several autonomic/self-* behavior/functionality being developed in NFV.
> 
> There is clearly a gap here, and a difference in approach.

I couldn't find an adequate reference for NFV, which is why the drafts says
[reference needed]. I didn't find a clear definition of "microservices" either,
which is why I didn't use the term.

I think autonomic networking is a new form of network management. Is there
anything wrong with the current statement?
  "For example, the services envisaged for
   network function virtualisation [reference needed] or for service
   function chaining [RFC7665] might be managed by an ASA rather than by
   traditional configuration tools."

An ASA to manage SFC might be an interesting use case to develop.
 
>   1.  -You mentioned something about the decoupling of self-* functionality (self-configuration, self-healing...)
> 
> Not sure I get fully what was your comment on this aspect. Could you clarify / develop?

Again, I think this is a use case issue. The way these self- properties
interact is surely not the same in all cases?

    Brian


From nobody Wed Mar 21 06:50:58 2018
Return-Path: <mcr@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E768712EA87 for <anima@ietfa.amsl.com>; Wed, 21 Mar 2018 06:50:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.435
X-Spam-Level: *
X-Spam-Status: No, score=1.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_SBL_CSS=3.335, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 TdpUQne_7mDG for <anima@ietfa.amsl.com>; Wed, 21 Mar 2018 06:50:52 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 195B0127078 for <anima@ietf.org>; Wed, 21 Mar 2018 06:50:50 -0700 (PDT)
Received: from dooku.sandelman.ca (dhcp-86ae.meeting.ietf.org [31.133.134.174]) by relay.sandelman.ca (Postfix) with ESMTPS id 039631F95A for <anima@ietf.org>; Wed, 21 Mar 2018 13:50:49 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id A2A2D5BA; Wed, 21 Mar 2018 13:50:18 +0000 (GMT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 21 Mar 2018 13:50:18 +0000
Message-ID: <19572.1521640218@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/ZDFLO_pBW2d8LD7Gplc2wzhJsDQ>
Subject: [Anima] constrained voucher
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2018 13:50:54 -0000

--=-=-=
Content-Type: text/plain


Does the WG now have enough information about the Constrained Voucher work to
consider adopting it?

6tisch Working Group                                       M. Richardson
Internet-Draft                                  Sandelman Software Works
Intended status: Informational                           P. van der Stok
Expires: August 18, 2018                          vanderstok consultancy
                                                           P. Kampanakis
                                                           Cisco Systems
                                                       February 14, 2018

        Constrained Voucher Profile for Bootstrapping Protocols

       draft-richardson-anima-ace-constrained-voucher-03

Abstract

   This document defines a strategy to securely assign a pledge to an
   owner, using an artifact signed, directly or indirectly, by the
   pledge's manufacturer.  This artifact is known as a "voucher".

   This document builds upon the work in [I-D.ietf-anima-voucher],
   encoding the resulting artifact in CBOR.  Use with two signature
   technologies are described.

   Additionally, this document explains how constrained vouchers may be
   transported in the [I-D.vanderstok-ace-coap-est] protocol.



--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJasmMaAAoJEJVM4Vb9/EKQyqMIAKua6ZutPOrzAejjKHS+mUjo
nCPjxNWJxyUyvAxZaAuUHqab0LQ2HlBxN1nOAUWTk2tAOsoBVsQB28KHv8p/HECa
kX2Pb9SryJPoEusIMqupAFbAVpnwyBIML7N5c9l9MJwbNWQHN7ZZdKnKiHLkEelh
oSCd2TABre+LODqrxiYUG+fHAqCqK/rJHg+BLDEr3gWdBjJFrGIOuwjh+h3T1/ak
sbMPv0b+agmMyfaL7C43rV69SZHTlv767b8PY1mWVebQ9hc8oO8SrTz91p3kuLgz
9Bt1K8KXlpFusvipvXc95gWX/amyMnuOrwbFDFsLKDq8MG2tBxrdz+hj2fmApUg=
=BTBY
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Mar 22 03:51:42 2018
Return-Path: <Xun.Xiao@huawei.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 865D2120726 for <anima@ietfa.amsl.com>; Thu, 22 Mar 2018 03:51:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.231
X-Spam-Level: 
X-Spam-Status: No, score=-4.231 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 2NTtwSWOcG2D for <anima@ietfa.amsl.com>; Thu, 22 Mar 2018 03:51:38 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0690F1200C1 for <anima@ietf.org>; Thu, 22 Mar 2018 03:51:38 -0700 (PDT)
Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 201BACB87558F for <anima@ietf.org>; Thu, 22 Mar 2018 10:51:34 +0000 (GMT)
Received: from lhreml507-mbb.china.huawei.com ([10.201.109.48]) by lhreml706-cah.china.huawei.com ([10.201.108.47]) with mapi id 14.03.0382.000;  Thu, 22 Mar 2018 10:51:23 +0000
From: Xun Xiao <Xun.Xiao@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Anima WG <anima@ietf.org>
CC: Artur Hecker <Artur.Hecker@huawei.com>, "Liubing (Leo)" <leo.liubing@huawei.com>, Zoran Despotovic <Zoran.Despotovic@huawei.com>, Sheng Jiang <jiangsheng@huawei.com>
Thread-Topic: [Anima] Comments on draft-liu-anima-grasp-distribution-05
Thread-Index: AQHTvAYJ7jkJ7+/yykyruOIgIDWHVKPcEueQ
Date: Thu, 22 Mar 2018 10:51:23 +0000
Message-ID: <67C6AE5A0CF6AD45A8571ED3F6E802E413773A3E@lhreml507-mbb>
References: <dcb61f08-781a-e6dd-fcea-127d9761b559@gmail.com>
In-Reply-To: <dcb61f08-781a-e6dd-fcea-127d9761b559@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.221.116.224]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/2bO8eZ3xih-KXKCdi-ifqNxg-H8>
Subject: Re: [Anima] Comments on draft-liu-anima-grasp-distribution-05
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 10:51:40 -0000

Dear Brian,

Thanks for your detailed review. To your comments, after discussing among a=
ll co-authors, we put inline reply below.

BR.

-Xun Xiao on behave of Artur, Zoran ang Bing

-----Original Message-----
From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Brian E Carpenter
Sent: Thursday, March 15, 2018 3:33 AM
To: Anima WG <anima@ietf.org>
Subject: [Anima] Comments on draft-liu-anima-grasp-distribution-05

Hi,

Since there were a lot of updates in this version, I read it again from the=
 beginning. Here are my comments.

In general I think this is useful work that the WG should consider adopting=
. There is definitely a requirement for something in the space between peer=
-to-peer synchronization and flooding to all autonomic nodes. The fixed siz=
e of GRASP messages also limits information distribution at present.

[Xun, Artur, Zoran and Bing] We would appreciate, if this work could be ado=
pted as a WG document. We also appreciate that we share the same view on th=
e problem space.

[Xun, Artur, Zoran and Bing] Our main concern in this document is not just =
the (re-)statement of the requirement to reach (sub-)sets of nodes in an Au=
tonomic Domain, but rather a suggestion of a model and a simple mechanism, =
allowing to do it efficiently at different scales and in networks of differ=
ent topologies. In other words, while it would be an easy game to implement=
 such a mechanism in a very small network (any viral propagation) or in a s=
parse network ("expanding circle", as an example), it is much harder to fin=
d a cheap and scalable solution for any network. We believe that "any" netw=
ork matters, because ANIMA protocols can be seen as a "first" set of proced=
ures to be executed. It means it must work, when one simply does not know y=
et, how the network looks like.

> 3.2 One-to-Many Communications
>=20
>    Some information exchange involve an information source and multiple
>    receivers. This scenario can be divided into two situations:
>=20
>       1) When some information are relevant to all or most of the nodes
>       in the domain, the node that firstly handle the information should
>       use a mechanism to propagate it to all the other nodes.
...
>       2) A more general case is that some information is only relevant
>       to a specific group of nodes belonging to the same sub-domain or
>       sharing the same interests.

It's probably worth mentioning that there is a tradeoff here. If some infor=
mation is relevant to 50% of nodes, it is probably cheapest to simply flood=
 it to all nodes. If it is relevant to only 5% of nodes, it is probably che=
apest to use a pub/sub model.

[Xun, Artur, Zoran and Bing] We were motivated by the tradeoff when doing t=
his work. A more rigorous way is to define a nice metric on this. It should=
 reflect:
 - The size of the network or the volume of messages to be sent (or of data=
?)
 - The absolute number of nodes that want to receive it
 - Ultimately, it should also somehow reflect the speed of information prop=
agation.
 - Cost of sending that many messages from any individual node?
NOTE that simply putting a percentage is not enough, as it might be still d=
isastrous to epidemically flood messages in a very dense big network even t=
o only 5% of nodes. Flooding is in general not the top option to disseminat=
e information, even if you need to send info to all nodes (and not 'only' 5=
0% of them), let alone when it is only a small fraction of the network. The=
 thing is that flooding will send many duplicate messages and as such uses =
nodes' communication capabilities in a pretty inefficient way. Simply, floo=
ding will send data along each link. It is always better to setup a structu=
re that we can use for dissemination. With this structure, that our pub/sub=
 in fact represents, we send in total one message per node, which is much b=
etter. So our pub/sub should be seen as a systematic way to disseminate inf=
o, rather than an efficient realization of our wish to disseminate date to =
any x% of the nodes in the network. Probably, this is something to discuss =
over and over again in the group until we get full consensus in the group.


> 3.3 Requirements
...
>       3) Distributed Coordination....
...
>       Obviously, purely relying
>       on instant communication model is inefficient, while a scalable,
>       common, yet distributed data layer, on which AFs can store and
>       share information in an asynchronous way, should be a better
>       choice.

This is the most interesting case (I think of it as a whiteboard, where any=
 ASA can read, write or erase). Doesn't it also relate to distributed conse=
nsus mechanisms?=20

[Xun, Artur, Zoran and Bing] Very good, yes, why not. We would only add "..=
.the data that it's authorized to" or something like this, but in principle=
, yes.

Can we consider the previous case (pub/sub) to be a subset of this case, wi=
th only one node having write/erase capability?

[Xun, Artur, Zoran and Bing] We think autonomic networking will definitely =
require a distributed / shared data layer that facilitates information dist=
ribution. PubSub is just a model, it's not a mechanism. You can implement i=
t with different mechanisms. Whiteboard is a very particular PubSub instanc=
e (everybody is subscribed to everything, everybody is publishing at the ex=
act same location). Similarly, Blockchain would realize the PubSub model wh=
ere no one can arbitrarily modify the published information, i.e. realizing=
 as a permanent whiteboard (=3Dledger, secure log, etc).

[Xun, Artur, Zoran and Bing] Simply put, your parallel with a whiteboard sc=
enario is valid. Though, our pub/sub is a more general option, as there can=
 me many such whiteboards, and nodes that disseminate information would req=
uire some knowledge which one they should select, etc. And yes, as soon as =
we start talking about multiple nodes writing in a shared storage of any ki=
nd, we need to consider consensus/concurrency etc. issues.

> 5.1 GRASP for instant communications
...
>       o  Matching condition: "Device role=3DIPRAN_RSG"
>=20
>       o  Matching objective: "Neighbors"
>=20
>       o  Action: "Forward"
>=20
>    This example means: only distributing the information to the
>    neighbors who are IPRAN_RSG.=20

How does the node performing the distribution know which of its neighbours =
have the role IPRAN_RSG? Is there a registration process? Is it really any =
different than the subscribe process in pub/sub? ("I subscribe to IPRAN_RSG=
 information".)

[Xun, Artur, Zoran and Bing] First of all, in this example, it assumes that=
 the role of the device (i.e. IPRAN_RSG) is pre-defined, thus everyone in t=
he network may know what the role of a node is already. However, we notice =
that this will not be always the case because for different ASAs running on=
 the same node, their roles could be different. Then, how a node (or an ASA=
) can identify itself and roles of the other nodes (ASAs) will be a challen=
ge. But in principle, yes, the nodes interested in that have to 'subscribe'=
.

>  5.2 GRASP for asynchronous communications

Once we have the previous point solved, we can model the asynch distributio=
n as a selective flood to the "whiteboard"
in each node.

[Xun, Artur, Zoran and Bing] Again yes and no. It really depends on the ext=
ent the shared data layer (i.e. the whiteboard in your term) can support th=
e asynch distribution. A simple solution is that the information is simply =
forwarded through the shared data layer. A more intelligent solution is tha=
t the shared data layer delegates the information delivery in the sense tha=
t information storage and notification are autonomously done.

Having said that, I want to look back in the draft at the Event Queue descr=
ibed in section 4.2.1. I'm not sure that we need it as a separate engine fr=
om the queues implied by GRASP's existing asynchronous operations. If you m=
odel a producer or consumer as a process using GRASP, it will naturally nee=
d to support simultaneous asynch operations and an event queue.

I am wondering to what extent I can model this directly over GRASP as it ex=
ists today. My main question is mentioned above: how does a node know which=
 of its neighbours have a given role?

[Xun, Artur, Zoran and Bing] Probably only modifying GRASP is not enough. I=
t may involve introducing some new modules and capability assumptions (e.g.=
 local storage) to ANI. If an efficient and intelligent "whiteboard" can be=
 nicely realized, role identification should be easy.

(One possible answer is that *every* node sends out a local GRASP flood at =
very low frequency, stating which roles it supports.
Then every node builds a cache of its neighbours' roles. I can make that wo=
rk with GRASP today.)

[Xun, Artur, Zoran and Bing] The problem is not how a node would send such =
a message or to whom locally. The problem is that it would have to be propa=
gated, which, in a big network, would be an overkill with flooding. Actuall=
y, if you are interested in concrete numbers, there is a lot of work and em=
piric conclusions on that from GNUTELLA, which uses such a protocol with li=
mits to cut off flood storms (e.g. max. TTL and max. number of nodes that y=
ou locally send it out to). Gnutella worked (with many tricks to limit the =
inefficient search), but it could not reliably find an available piece of i=
nformation. Not sure, this is a suitable for ANIMA.

Regards
    Brian

_______________________________________________
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima


From nobody Mon Mar 26 12:11:10 2018
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85FEE127136 for <anima@ietfa.amsl.com>; Mon, 26 Mar 2018 12:11:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 Vot6XhPdpNXa for <anima@ietfa.amsl.com>; Mon, 26 Mar 2018 12:11:06 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0215E1276AF for <anima@ietf.org>; Mon, 26 Mar 2018 12:11:06 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 5D10320090; Mon, 26 Mar 2018 15:20:22 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 7A92980AF9; Mon, 26 Mar 2018 15:11:04 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
cc: Toerless Eckert <tte@cs.fau.de>
to: anima@ietf.org
In-Reply-To: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de>
References: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Mon, 26 Mar 2018 15:11:04 -0400
Message-ID: <2380.1522091464@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/qzo8u77WLlzDuplBytOHa2-sv_w>
Subject: Re: [Anima] Shepherd review draft-ietf-anima-bootstrapping-keyinfra-09
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2018 19:11:09 -0000

--=-=-=
Content-Type: text/plain


Comments on section 5, 6 and 7.



    > ----------------------------------------------------------------------
    > Section 5.4

    > a) See comment for section 2.4.4  for where i think the first paragraph
    > description should be.

There isn't a 2.4.4, so I'm not really sure I understand what you want me to do.

    > (aka: make this paragrap a summary of what the MASA interface is,
    > mentioning both requestvoucher and requestauditlog and move to 2.4.4).

    > b) The paragraph is difficult to parse and has IMHO wrong pieces.
    > - What does "simplicity" mean ?

I think it's mostly content-free.
It makes the text simpler to not have explain all of EST here.


    > - "the Registrar is not required to make use of any other EST
    > functionality when communicating with the MASA service"... what does
    > that mean.. ? Not required = but could optionally do it ?

I guess, we probably gained nothing by saying it was EST rather than a
straight RESTful web service.

I've opened issue,
     https://github.com/anima-wg/anima-bootstrap/issues/53

I think that's what you are asking here.

    > If a shared code basis is used for MASA and other EST/BRSKI defined
    > service roles (Domain Registrar, CA,...), the MASA service MUST
    > properly reject any EST functionality requests it does not wish to
    > service; a requirement that holds for any REST interface.

For me there is/was no code sharing.

    > "when the Registrar is expected to be offline" ->
    > "when the Registrar is expected to be unable to connect to a MASA"

    > Offline can be confusing because it does not explain who is not able to
    > talk with whom, and i think in both cases two of the three are still
    > expected to talk with each other (or at least that part does not
    > matter).

    > I am still confused about the "Pledge is unable to connect to the
    > Registrar" case.  Is this a case where BRSKI-EST does not happen but
    > something else (e.g.: sneakernet) between Registrar and Plege ? Please
    > add a sentence explaining what this case means.


https://github.com/anima-wg/anima-bootstrap/issues/54

    > f) "since the registrar is not known to the MASA server in advance"

    > Given how the HTTPS connection requires authentication, there is some
    > knowledge about the registrar from that, so the above sentence is
    > confusing. Whats the
    > correct statement to be made here thats takes the existance of the HTTPS
    > authentication of the Registrar to the MASA into account ?

https://github.com/anima-wg/anima-bootstrap/issues/55


    > g) Registrar revocation consistency:

    > Maybe change the lead in in this section to something like: "If the Registrar
    > uses a CA known to the MASA to make certificate revocation information
    > available
    > to the MASA, MASA SHOULD check ... of the Registrar Certificate. MASA MAY
    > limit service to Registrar where this applies to provide owners
    > protection against impacted registrar (e.g.: stolen).

okay, clarified text a bunch of text, and went back to 2.6.1 and changed
some text to put a few additional constrained on time.   I also turned the
point form into sections because they needed more detail, and so that they
can be referenced.
See:   https://goo.gl/166KTe

    > In any case a short reasoning why to do this step would be helpfull.

    > h) Pledge proximity assertion:

    > Sentence summarizing one most important attack vector reducet by
    > this. Or pointer to reference where this is explained.

I agree, we should expand this section to explain why.
  https://github.com/anima-wg/anima-bootstrap/issues/56

    > -----------------------------------------------------------------------------
    > Section 5.5

    > a) "immediately complete authentication of the provisional"

    > This sounds contradictory to the potential need to perform /cacerts first as
    > described in section 5. Add something like (potentially after
    > performing /cacerts,
    > see section 5.) ?

We opened an issue before about this. I added this to it.
   https://github.com/anima-wg/anima-bootstrap/issues/51


    > -----------------------------------------------------------------------------
    > Section 5.5.1

    > a) "which is an additional justification
    > for the recommendation to proceed with EST key management operations.
    > Once a full CA Certificate Response is obtained it is more
    > authoritative for the domain than the limited 'pinned-domain-cert'
    > response."

    > This sounds contradicting to the statement in section 5., where it sounds as if
    > provisional state is completes only after the (optional /cacerts) and cacerts
    > is part of bootstrap, whereas here it sounds as if its part of
    > enrollment only.

okay, part of issue above.


    > -----------------------------------------------------------------------------
    > Section 5.6)

    > a) "The domain is expected to provide indications to the system
    > administrators concerning device lifecycle status.  To facilitate
    > this it needs telemetry information concerning the device's status."

    > Nice language.

    > Whats missing is the IMHO quite relevant recommendation to go beyond that
    > and provide diagnostics / suggestions that could go as much as

    > "actionable recommendations in support of expedient resolution of the
    > failure".


    > Aka:
    > (Failure) Reason: "voucher certificate not valid yet".
    > Suggestion:      "Replace empty RTC battery "

    > Can we add something like Suggestion to the structure ?
    > Not sure if "suggestion" is the best word, but it would be great if we
    > can put a stake in the ground adding this to the structure. I have seen
    > too many times
    > where it took eternities to find the magic offline manual mapping from
    > a range
    > of crazy error codes (reasons) to the suggestions what to do next.

    > b)  Recommendations for how to mitigate the potential security issues
    > of diagnostics
    > would be great:

    > - Reasons could be per-device encoded, requiring vendor for further insight:
    > Reason: "error 23498y354AZRFF"
    > Suggestion: "call manufacturer"
    > - Operations after errors can be slowed down to reduce/eliminate brute force attacks

    > c)  "message is being sent" -> "message may be sent" (above example of
    > non-attack issue).

So that was the reason for the reason-context.
It's very much specific to the device.
I'm not sure what text you are suggesting here.

    > -----------------------------------------------------------------------------
    > Section 5.7)

    > a) Paragraph 1: Did we not discuss the option that the Registrar might
    > want to examine the authorization log before even forwarding the
    > voucher to the Pledge ?

Yes, but the critical thing is that it occurs prior to accepting the
certificate request from the Pledge.

    > b) It is recommended put to put some
    > ^^^^^^^^^^

    > And not even clear what it would mean if the sentence was fixed.
    > Does it mean something like: Cacheable object name could be large
    > randomn number ?

Fixed the text.


    > -----------------------------------------------------------------------------
    > Section 5.7)

    > a) The current described examples of the Audit Log are all somewhat scary,
    > a bit like "The doctor told me something bad... should i ignore it".
    > Or worse: This audit log stuff is made up by Vendors to scare us into buying
    > only manufacturer refurbished gear with a clean history bill.

    > Can we mention some simple positive examples o better sell the value of
    > the audit log,

I'm not really sure what to do with this comment.
If we are doing marketing here, perhaps you can tell me what the audience is
(Manufacturer? ISP? Enterprise? Consumer?) and what their risk profile is?

    > The biggest concern i think we will see from privacy advocats is that
    > vouchers/audit-logs are a big-brother initiative from vendors. This too might
    > be something to document counter arguments for:

No, vouchers with supply chain integration are big-brother initiatives from
vendors...   Audit logs are the way in which we avoid having to do that for
every product.

I don't know what you want me to do here.

    > -----------------------------------------------------------------------------
    > Section 5.8)

    > a) "The Pledge is also RECOMMENDED to implement the following EST
    > automation extensions"
    > add: An ANI Pledge MUST implement them.

okay.

    > b) Last paragraph: It looks as if this is in answer of my question about
    > enrolling multiple certificates. Thanks!

    > - Please put at the end of 5.8 (eg: new subsection before CoAP -
    > "enrolling multiple
    > certificates). No need to derail the core track what BRSKI does with
    > consideratations of what it can not do.

done.

    > -----------------------------------------------------------------------------
    > Section 5.8.2)

    > a) The wording of the first paragraph makes it somewhat hard to understand what point
    > it is trying to make:

    > | In some deployments its plausible that the Pledge generates a certificate
    > | request containing only identity information known to the Pledge (essentially
    > | the X.509 IDevID  information) specific identity information

    > "in other deployments the pledge magically generates a certificate request
    > including information not known to the pledge"  ???

You put the "not" in there.  We didn't.

    > -----------------------------------------------------------------------------
    > Section 5.8.4)

    > a) "The EST protocol assumes an end user" -> "RFC7030 assumes an end
    > user"

okay.

    > b) There seems to be text missing after second paragraph (before
    > discussing success/failure):

I don't understand what is it that you find missing.

    > c) " This allows for clients that wish to minimize their crypto operations
    > to simply POST this response without renegotiating the TLS session -
    > at the cost of the server not being able to accurately verify that
    > enrollment was truly successful."

    > Bullocks. First you scare off readers with "diagnostics bad" (5.6), and
    > now Pleges SHOULD just do good diagnostics (try new LDevID to see it works) ?

    > Please make the SHOULD re-negotiate a MUST and delete this last paragraph.
    > If a plege can not afford a single validation of a BRSKI certificate, its not
    > worth receiving one.

Could you please start again about this issue.
5.6 does not say diagnostics bad.
5.6 says not to tell attacking registrars too many details.

At 5.6, if there is a failure, the voucher has not been accepted, and we do
not have trust.

At 5.8, Pledge already trusts Registrar, but the certificate request has
failed, and we already have trust.  Knowing all the details is acceptable.

    > -----------------------------------------------------------------------------
    > Section 6)

    > a) Suggest Change title to eg: "Additional security options"

Why?  A common complain about BRSKI and vouchers is that it's too secure.

I have added:
      <t>
        This section is considered non-normative: use suggested methods
        MUST be detailed in specific profiles of BRSKI.  This is the
        subject for future work.
      </t>

    > - Some text (eg. first paragraph mentioning NEA) talks also about
    > additional/higher
    > security, so lower is not necessarily always true.

Which methods are higher security?
I can't find which ones you might refer to.

    > -----------------------------------------------------------------------------
    > Section 6.2)

    > a)  fix to "not involved in security considerations in this chapter"

    > Remember text in earlier sections where you claimed that yu do expect
    > fewer attacks after completion of TLS/provisional and how having trusted
    > Plege/Registar-Pledge path achieves this.

I can't parse this.

    > -----------------------------------------------------------------------------
    > Section 6.3)

    > a) MASA server -> MASA service (i may have said that in before, but you
    > can ignore

already done.

    > b) "Trust on first Use" for physical ports: suggest to modify to:
    > "trust on first use" for methods with a strong dependency on physcial
    > posession,
    > such as taking ownership via configuration on a serial console.

fixed.

    > -----------------------------------------------------------------------------

    > Section 7)

    > a) This document is extending the .well-known "est" definition. We need to
    > determine how to correctly handle this and have started to inquire.

This document extends RFC7030.
It probably needs to be marked as Updates RFC7030.
7030 does not establish an IANA registry for .well-known/est, so there are
no IANA intructions, but the most restrictive kind of RFC Standards Action,
which this document does... so I think we are just fine.

    > I suggest to add the following text to the IANA section for this:

    > | This document extends the definitions of "est" (so far defined via RFC7030) in
    > | the "https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml" registry
    > | as follows:
    > |
    > |   - add /.well-known/est/requestvoucher (see section 5.4)
    > |   - add /.well-known/est/requestauditlog (see section 5.7)


So, really, it should now have two entries in that list?

    > b) It would be good to create subsections for each registray mentioned so
    > that one can see from the table of content what registries are impacted.

Don't we already have that?
We are only creating one registry.

    > c) Probably need a summary of updates this document makes to RFC7030, the
    > easiest way would IMHO be to create a short section "Updates to RFC7030",
    > saying that all REST services introduced in this document are extensions ot
    > RFC7030 ESTE because they use the EST well-known prefix, and then point to
    > section 2.4 which with the text i proposed provides IMHO a good summary
    > of those services as used by each role (Pledge, Registrar, MASA).

I think that you do that above.

    > d) Add section to request brksi-proxy and brski-registrar to
    > IANA service name registry.

I'm still not sure I understand the why of dns-sd discovery in an ANI
environment.




--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlq5RcgACgkQgItw+93Q
3WXEwQf/W3dZm/FcT/2kdJw3nhbKNMFIicfhw9fSyeNQSwY3hJnhfUjbkTxsKf0V
D1oQkYQMPfMbthiyAMcsHK/OFm2122Ru36s4bDmBmMJiVRJbTUJipFp0WGsNeDRf
DJAdY12UJTLowQOam45ILUwZcq5Mi2NtNIwXsrEsOzPABxVrbrgagl4oSz05CYHU
tQfLJknVQ5nNh80amEWGNihoq4meHyJQMFiCTGCPvjvGdUtcLBE9/GAXwsAQEum1
GV9NFz1+FoSuIAitlem6wUswdphGUNH7eHtm8nFOukA+b/gn15+jazsEJ1NH06nL
KxZcfrLQvx0NjKhgfRfBsmPcj8ujJA==
=grJz
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Mar 26 12:30:47 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5732127337 for <anima@ietfa.amsl.com>; Mon, 26 Mar 2018 12:30:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 HS4vaffETRqA for <anima@ietfa.amsl.com>; Mon, 26 Mar 2018 12:30:45 -0700 (PDT)
Received: from mail-pg0-x233.google.com (mail-pg0-x233.google.com [IPv6:2607:f8b0:400e:c05::233]) (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 9B73A127136 for <anima@ietf.org>; Mon, 26 Mar 2018 12:30:45 -0700 (PDT)
Received: by mail-pg0-x233.google.com with SMTP id g8so7663065pgv.7 for <anima@ietf.org>; Mon, 26 Mar 2018 12:30:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=qXhOlb8PydW/GxWvGbQGmvgrzlXZ5vrpSGPmdzEr45c=; b=KjzDJgXVhRYCy2cwUM3CGj++2IrV/179M1OhXnDG2QASrzvFebO1BqNlpbKpWy0i1P 8PNpPVvuNjhEwbU2DPl3Pk8tDk3PSjlp3EskQ4adQw3d903/A/eVg9ZLqb4xeEPV3ICr npTK6z5RFdwoQjgi2u79ZS3w4+JSAgGvBrQBgpQvJ5jw0bmwdDC8Nf5aH8d/aDICcjdF YejedpzihmkHN9JDStcLAg4uSSC2DPM7Z2PA18v1ndGoXXinIE++89anF6S75ScISRtp ybvTpjp51Ex37CJrfWf3mftjY6oLoG3JzC857PjrfzDw3TcKbVjTBHr8HvTRariiCY2l NrNA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=qXhOlb8PydW/GxWvGbQGmvgrzlXZ5vrpSGPmdzEr45c=; b=tGjeHZv7zeLlMh1uQXIDBy9PxcyqLnji8gD0eZDHi6gNKNbi9hjOhU1o2pbnB7Y1Zp L5AkzxglFuoEW+89zNrer4AUE94BXJ2pACcbVA1fLpAWbASoMFLI9BpbzNvbjEn9vO4k 9QNENGyLu2qxza1I5x2McwymG2xJk6hNPt9QVBHwE/TPKPnKa3O/PJ9PB6vOsqxIb2I8 Nxsop2BPPoNcAQOdS3TL3EH2Lx7AHmfdpO2Cl0EuTXnA4k0zAL2XYwydZlEy1vGugRir u39rSXxRjoUUkW/2afBmn+Ym/U/Pv5xmFZj97AQ4fSIxCijirP1a6nZkLw9GHjdwxHz+ IWfw==
X-Gm-Message-State: AElRT7EluatgWmZqZZFagLEuaMiAqyrDmEPtkl9PEPX6KBfiOUIQtmXc zAjJchcNrV2c228HQ/RyRz4=
X-Google-Smtp-Source: AG47ELskJkCXUM6xNBhX6ylFmn675ilNxKn2NWf/jQwhHc8L1WPf7BhkId5uw2fFMZp2hyNTlaLfHQ==
X-Received: by 10.99.115.68 with SMTP id d4mr29709673pgn.145.1522092645183; Mon, 26 Mar 2018 12:30:45 -0700 (PDT)
Received: from [192.168.178.26] ([118.148.76.62]) by smtp.gmail.com with ESMTPSA id i86sm4773265pfi.28.2018.03.26.12.30.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Mar 2018 12:30:44 -0700 (PDT)
Sender: Brian Carpenter <becarpenter46@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, anima@ietf.org
Cc: Toerless Eckert <tte@cs.fau.de>
References: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de> <2380.1522091464@obiwan.sandelman.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <7212c1c6-e906-8018-6939-68552daa1b40@gmail.com>
Date: Tue, 27 Mar 2018 08:30:42 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <2380.1522091464@obiwan.sandelman.ca>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/relDR0EtrFn_xCaJqh3pqQKRcww>
Subject: [Anima] dns-sd [was Shepherd review draft-ietf-anima-bootstrapping-keyinfra-09]
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2018 19:30:47 -0000

On one point only:

On 27/03/2018 08:11, Michael Richardson wrote:
...
> 
>     > d) Add section to request brksi-proxy and brski-registrar to
>     > IANA service name registry.
> 
> I'm still not sure I understand the why of dns-sd discovery in an ANI
> environment.

That's a discussion on its own and I think it should be kept separate.
So I would leave these registrations aside for now; nobody else
is going to ask for brksi-* service names, so there's no urgency.

Once this phase is done, I hope we can discuss draft-eckert-anima-grasp-dnssd
properly in the WG, and the deeper implications.

     Brian


From nobody Mon Mar 26 12:36:13 2018
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E812127136 for <anima@ietfa.amsl.com>; Mon, 26 Mar 2018 12:36:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level: 
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 UeiycRsqqisi for <anima@ietfa.amsl.com>; Mon, 26 Mar 2018 12:36:09 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1037126CC4 for <anima@ietf.org>; Mon, 26 Mar 2018 12:36:09 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id ED5CA20090; Mon, 26 Mar 2018 15:45:26 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 0A77C812C9; Mon, 26 Mar 2018 15:36:09 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
cc: Toerless Eckert <tte@cs.fau.de>
to: anima@ietf.org
In-Reply-To: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de>
References: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Mon, 26 Mar 2018 15:36:09 -0400
Message-ID: <8048.1522092969@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/MtfrNTn3TvoBbylNNbsjMm_R0_c>
Subject: Re: [Anima] Shepherd review draft-ietf-anima-bootstrapping-keyinfra-09
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2018 19:36:12 -0000

--=-=-=
Content-Type: text/plain


Final comments/actions on Toerless' awesome review.
The -13 is coming out soon, but we have 13 issues to resolve still.

    > -----------------------------------------------------------------------------
    > Section 8)

    > a) First paragraph: Unvailable MASA is not a security but an
    > operational consideration.
    > Feel free to add "Operational considerations" section before security
    > considerations and move it there. Might want to add some more
    > considerations around
    > MASA to set context: Suggest something like:

It's due to that operational consideration that someone might want a nonceless
voucher, and therein is the security consideration.

So while I'm not oppposed to an Operational Considerations section,
it would not start with that first paragraph.

    > c) "The MASA authorization log..."

    > Not security consideration either IMHO.  Suggest to move into a new
    > "Privacy considerations"

Agreed.
MAX: when did the MASA audit log became an authorization log?
     Is this intentional?

    > -----------------------------------------------------------------------------
    > Appendix A)

    > a) Would change title to non-IPv6 or non-ANI operations:
    > b) Initial explanation:

I'm changing it to IPv4 and non-ANI operations.
I'd rather search found "IPv4"

    > Specification of BRSKI in Section 4. only covered the mechanisms for an IP6
    > Pledge (link-local IPv6 address) and Proxy options necessary for IPv6
    > and ANI.
    > It does not cover the options for non-IPv6 Pledge or non-ANI Proxies
    > (IPv4 or IPv6).

done.

    > -----------------------------------------------------------------------------
    > Appendix A.2)

    > a) Replace with:

    > A.2.  Use of DHCP

Not sure I agree. I think that DHCPv6 considerations are very different.
There are RAs, DHCPv6, as well as what kind of address will be given.
An IPv4 address is almost 100% certain to be RFC1918/NAPT, while IPv6 will not.

I don't mind adding a section on this, but I'd prefer to have a seperate
section as it needs significantly more details.

    > -----------------------------------------------------------------------------
    > Appendix B)

    > a) Use suggested service name of "_brski-proxy" in all caes where
    > "_bootstrapks"
    > is used. (see comment for section 4.1.1 for why that name is better).

Opened issue: https://github.com/anima-wg/anima-bootstrap/issues/57

    > b) After "The Pledge MAY perform DNS-based Service Discovery", new paragraph:

    > A non-ANI Proxy MAY perform DNS-based Service Discovery using unicast DNS
    > to discover Registrars searching for searching for the service
    > "_brski-registrar._tcp.local.".

okay.

    > c) "To prevent unaccceptable levels of network traffic" -> add ", when
    > using mDNS"

okay.

    > d) "received a useable IPv4 address via DHCPv4 as suggested in Appendix A" ->
    > "received a useable IP address via DHCP/DHCPv6 as suggested in Appendix
    > A.2"

see above.

    > e) "If no local bootstrapks service": Add at end of paragraph: See
    > Section 2.6 (Cloud Registrar).

done.

    > -----------------------------------------------------------------------------

    > Appendix C)

    > a) See discussion for section 4.3 above for the issues i see with
    > current IPIP
    > specification and suggestion to maybe move out of BRSKI to resolve with
    > more time.

Yes, I think that I agreed to remove it.

    > -----------------------------------------------------------------------------
    > Appendix E)

    > a) Please add a sentence how to decode Hex Certs (not keys) with utility
    > at the very top of the appendix (right now its further down in the
    > text).

I'm confused by this.
a) there are no Hex Certs, they are all base64, and they are in standard
   PEM format.
b) I never say how to decode them... so?

    > b) E.1.4: which element in the cert would become the serial-number ?

Good point, it's not in the Subject in this example.
     https://github.com/anima-wg/anima-bootstrap/issues/58

I expect to regenerate the examples at AUTH48 time, once IANA
has assigned everything.

    > c) There are no ASN1 decodings of the artefacts, Please fix.
    > If this is subject to IANA assignments, please add RFC editor note to
    > block draft progressing.

Sorry?  Which one is missing?

    > X) Applicability outside ANIMA

    > If i am not mistaken, BRSKI-MASA should be one option how a bootstrap
    > server in "draft-ietf-netconf-zerotouch" could obtain a voucher from a
    > MASA (if i understand it correctly, the mean by which such a bootstrap
    > server obtains a voucher is left open). If that is correct, then it would
    > be great to mention this in a sentence or two in an appropriate section
    > of BRSKI as a very explicit example how BRSKI can be reused outside the
    > complete ANIMA scope (also add draft-ietf-netconf-zerotouch as an
    > informational
    > reference).

I would prefer to let ietf-netconf-zerotouch do that.
Or a new document in netconf, to be done after we finish BRSKI.
Otherwise, I think we wind up with too close coupling, and cycles
in the review process.

DONE your comments.
Many issues open.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlq5S6gACgkQgItw+93Q
3WXudgf8Com/Z2xYqkr1qFhrV2ct04FoYxajGakCoNd+R9NHMS7dWDYF6gLgX4jq
cs1hMgF+wCamcJDC89Frmceit9xBe//y4M6KefcxrnZt4H0btXMfzmfDxPJnG661
uOGbm/Kz2+2+FJ8R8+GNqldNM55hxo50irJ0fev3HT6LnDfAgWRbMyr2D50Euq3f
LaLgUGzdmkyEhB8LWdYdbwyj4W0ktzv0TUoui0qihczFPSpg5D0laYe7einTv5LJ
LGtRl2R3/pCycIWRDc8QVvXkdV19Hy53TorCKjrVeAhcf26eLAaaYLvdLktKVhx2
nlj/qvZWyu1ihT3MKcMdwI6MbkcBAQ==
=c7Fw
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Mar 26 13:13:37 2018
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 360C21276AF for <anima@ietfa.amsl.com>; Mon, 26 Mar 2018 13:13:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 lVeeGHKyWJe3 for <anima@ietfa.amsl.com>; Mon, 26 Mar 2018 13:13:33 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74DB4126CC4 for <anima@ietf.org>; Mon, 26 Mar 2018 13:13:33 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 23E0520090; Mon, 26 Mar 2018 16:22:50 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 1922780B46; Mon, 26 Mar 2018 16:13:32 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: anima@ietf.org
In-Reply-To: <825bb3aa-337b-cc1b-bcc0-8c5706bc2757@gmail.com>
References: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de> <23103.1519174480@obiwan.sandelman.ca> <20180221023844.GD23498@faui40p.informatik.uni-erlangen.de> <22048.1519182010@obiwan.sandelman.ca> <20180221151529.GF23498@faui40p.informatik.uni-erlangen.de> <825bb3aa-337b-cc1b-bcc0-8c5706bc2757@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Mon, 26 Mar 2018 16:13:32 -0400
Message-ID: <16780.1522095212@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/bMuz-wsgDQi51viEPrGZnxGxGLI>
Subject: Re: [Anima] Shepherd review draft-ietf-anima-bootstrapping-keyinfra-09
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2018 20:13:35 -0000

--=-=-=
Content-Type: text/plain


Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > I definitely recommend replacing lower-case "may" in a case like
    > the one below.

Agreed.

    > Perhaps:

    >>> , and MUST NOT be
    >>> enabled unless the JRC indicates support for them

Changed.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlq5VGsACgkQgItw+93Q
3WWAZQgAmmdTHE80WhCFrWrb1xCIgogzxKw3M1mfknjRDInMRbok1w54Lzpl8PId
/3RxMA6L9OJUan6U5ylzWCtECU45wOEJ1Lln58BFGCsFkc7jxP8mLO8qVflRFAmx
Woog7t69BTULRJY4+BAnSwPMYond+y53JlKciJxyIxth7Ca/Kh9ff/7Aa4paNCQU
m+wdYBhCl0d4RNkz9DRZTs+S1cTPJuLxrIuVuQzfvl9QEGW0Fi+IwZgk9PjDp7Gt
zwzHlcR3BQhYZB8mPvTYFzp3NkMrPyZqG/VAGbdlX+QG298wCvqBA54nJ4pcGT0g
dFG//vJdvMsEb6NuWXBV/eQOVv0+Dw==
=WLrM
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Mar 26 14:47:59 2018
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7AE7127978 for <anima@ietfa.amsl.com>; Mon, 26 Mar 2018 14:47:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01, T_SPF_TEMPERROR=0.01] autolearn=ham autolearn_force=no
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 DuELsLSyRE2b for <anima@ietfa.amsl.com>; Mon, 26 Mar 2018 14:47:56 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EE9F12E8D5 for <anima@ietf.org>; Mon, 26 Mar 2018 14:47:48 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 9A1FE20090; Mon, 26 Mar 2018 17:57:05 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 4720480AF9; Mon, 26 Mar 2018 17:47:47 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: anima@ietf.org, Toerless Eckert <tte@cs.fau.de>
In-Reply-To: <7212c1c6-e906-8018-6939-68552daa1b40@gmail.com>
References: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de> <2380.1522091464@obiwan.sandelman.ca> <7212c1c6-e906-8018-6939-68552daa1b40@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Mon, 26 Mar 2018 17:47:47 -0400
Message-ID: <8731.1522100867@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/YLIriq2UMcadnQwVYWjnwUNZ3Oo>
Subject: Re: [Anima] dns-sd [was Shepherd review draft-ietf-anima-bootstrapping-keyinfra-09]
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2018 21:47:58 -0000

--=-=-=
Content-Type: text/plain


Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > On 27/03/2018 08:11, Michael Richardson wrote:
    > ...
    >>
    >> > d) Add section to request brksi-proxy and brski-registrar to
    >> > IANA service name registry.
    >>
    >> I'm still not sure I understand the why of dns-sd discovery in an ANI
    >> environment.

    > That's a discussion on its own and I think it should be kept separate.

Good, I think so as well.

    > So I would leave these registrations aside for now; nobody else
    > is going to ask for brksi-* service names, so there's no urgency.

    > Once this phase is done, I hope we can discuss
    > draft-eckert-anima-grasp-dnssd
    > properly in the WG, and the deeper implications.

I'm not sure what to do about the current statements in the appendix then.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlq5aoIACgkQgItw+93Q
3WVg7Af+J7N5m1qFw93TcYYA2BQ8KsMB7e2UUtqxZbtskCzlO3NA8fZrYQfD0oGx
NUVJKpQg95eEDEOsaQeFtvPuJipFOmC+OSXq7hSN1s9B2J7XxkBLVoofL6WsWzuH
DauWLonwG9rxzJScXNjWEia5yA9d70VshnJSNXShbmYMfNLIGup3S88COwGnDNkG
YB3iVqu7DNu6ZMstq4UkG3rErn0T1OgCmcE+Yjuqe3xwozPc6hvb398uWALv+Rd5
5mr3J+W6fkQIamDbhJlWUysKXYDLGkkXbXpOvoEPcvQfCJmIDGR0ZZmxKauOZ4yQ
TPQrnybCZlNmo/qgq24ryVglFXXOUQ==
=CPXg
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Mar 26 14:48:25 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: anima@ietf.org
Delivered-To: anima@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B476126D3F; Mon, 26 Mar 2018 14:48:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: anima@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.76.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152210089715.15269.10688079396928078671@ietfa.amsl.com>
Date: Mon, 26 Mar 2018 14:48:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/-uqTwnuezOxiaclxYYvkKFJY_vo>
Subject: [Anima] I-D Action: draft-ietf-anima-bootstrapping-keyinfra-13.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2018 21:48:17 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Autonomic Networking Integrated Model and Approach WG of the IETF.

        Title           : Bootstrapping Remote Secure Key Infrastructures (BRSKI)
        Authors         : Max Pritikin
                          Michael C. Richardson
                          Michael H. Behringer
                          Steinthor Bjarnason
                          Kent Watsen
	Filename        : draft-ietf-anima-bootstrapping-keyinfra-13.txt
	Pages           : 91
	Date            : 2018-03-26

Abstract:
   This document specifies automated bootstrapping of a remote secure
   key infrastructure (BRSKI) using manufacturer installed X.509
   certificate, in combination with a manufacturer's authorizing
   service, both online and offline.  Bootstrapping a new device can
   occur using a routable address and a cloud service, or using only
   link-local connectivity, or on limited/disconnected networks.
   Support for lower security models, including devices with minimal
   identity, is described for legacy reasons but not encouraged.
   Bootstrapping is complete when the cryptographic identity of the new
   key infrastructure is successfully deployed to the device but the
   established secure connection can be used to deploy a locally issued
   certificate to the device as well.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-anima-bootstrapping-keyinfra/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-anima-bootstrapping-keyinfra-13
https://datatracker.ietf.org/doc/html/draft-ietf-anima-bootstrapping-keyinfra-13

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-anima-bootstrapping-keyinfra-13


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Mar 26 16:19:57 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3972E126C25 for <anima@ietfa.amsl.com>; Mon, 26 Mar 2018 16:19:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 wVqyxZxYI1mw for <anima@ietfa.amsl.com>; Mon, 26 Mar 2018 16:19:54 -0700 (PDT)
Received: from mail-pl0-x229.google.com (mail-pl0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) (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 CD939126C0F for <anima@ietf.org>; Mon, 26 Mar 2018 16:19:54 -0700 (PDT)
Received: by mail-pl0-x229.google.com with SMTP id f23-v6so12921849plr.10 for <anima@ietf.org>; Mon, 26 Mar 2018 16:19:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Q/u7vLu0wUON7c03wN9zd4BWLLKkPKqbWtaAIhr9+mE=; b=muRgtgwNO6XCALdK6pwkI1C+goX/BZRL+mMJbZT6z+55bU5DcHzqMydpYE5eGYXZll yHVggQ36Cq+PVIrRgnQkVeV1jl/U+Jf4jvMPpSy3PJ/WbvGMD2p8a1fCLir6fvROK1iZ kBGTeksv9QlyfuJx7AbC6UImoUD+/7+vTSaQEd4lfqw/K2DJnIaJETkyGUJsCrA8SkRK hpBUHC9w86YmHT1Rt1TonPJoFo+efvwbINEJbgttXDxvL8LIySAJenE+qeQrxtphGXES pH5rQOiP+RiR5Xdh9dGjPCsOtSM9+PYgJZWl4ltRzIBfvBl0hSW+/1nYu+N/HW8pVSS1 fR0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Q/u7vLu0wUON7c03wN9zd4BWLLKkPKqbWtaAIhr9+mE=; b=iuhfcBg6KD8zTH6/uevjn3hVJBfDwA+V4FW9xtqi2To8MCH/RRUhbvoK0NfjhSdE33 vubh2nxfzaqlFwNAIDWxrvlOx83hftt7KSVMslZPv6YkRdJ8Td42fNP++7Hx0AUrt5Y6 dPKQ3mKAldEvP+2BIE3SsqMZLXE1r6QUBK0jJ9Nf84hBykoxf22a2Qxws54f8rzp17ay 1Vh9OA/5TrtE70hNYclVNwaN4aTGxxFgUDJqcFow8XZ0JPMjF/ntwlIy0GXD40Taay39 bzVeL6r2Pr4D9fO2p04Y8qm0TNtbUAwTCLFHK5/ACkrvJx4YElpwRTnkWJRvwo2XSakn n5Xw==
X-Gm-Message-State: AElRT7GJLVcbE5g8B9wsUIiFNx4TvLlLuMVl8weNYnIDIFT1cou9BS4M GbXsix2/Qerc0Ui6DLcwWQA=
X-Google-Smtp-Source: AG47ELvuXTVPUY+8j1EIeMTUttquznl0nXfS9ab707x2PDGVzMZ3medCuMvVZD5asMGtL/LVUHrEgg==
X-Received: by 2002:a17:902:6bca:: with SMTP id m10-v6mr35179933plt.387.1522106394344;  Mon, 26 Mar 2018 16:19:54 -0700 (PDT)
Received: from [130.216.38.155] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.38.155]) by smtp.gmail.com with ESMTPSA id o66sm35149837pfg.90.2018.03.26.16.19.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Mar 2018 16:19:53 -0700 (PDT)
Sender: Brian Carpenter <becarpenter46@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: anima@ietf.org, Toerless Eckert <tte@cs.fau.de>
References: <20180214010910.GA27823@faui40p.informatik.uni-erlangen.de> <2380.1522091464@obiwan.sandelman.ca> <7212c1c6-e906-8018-6939-68552daa1b40@gmail.com> <8731.1522100867@obiwan.sandelman.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <6d509e01-6eba-5134-8038-96e1ee2f785e@gmail.com>
Date: Tue, 27 Mar 2018 12:19:51 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <8731.1522100867@obiwan.sandelman.ca>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/yrbb17XpIWhcdiQUs4NP8sm1dUY>
Subject: Re: [Anima] dns-sd [was Shepherd review draft-ietf-anima-bootstrapping-keyinfra-09]
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2018 23:19:56 -0000

On 27/03/2018 10:47, Michael Richardson wrote:
> 
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>     > On 27/03/2018 08:11, Michael Richardson wrote:
>     > ...
>     >>
>     >> > d) Add section to request brksi-proxy and brski-registrar to
>     >> > IANA service name registry.
>     >>
>     >> I'm still not sure I understand the why of dns-sd discovery in an ANI
>     >> environment.
> 
>     > That's a discussion on its own and I think it should be kept separate.
> 
> Good, I think so as well.
> 
>     > So I would leave these registrations aside for now; nobody else
>     > is going to ask for brksi-* service names, so there's no urgency.
> 
>     > Once this phase is done, I hope we can discuss
>     > draft-eckert-anima-grasp-dnssd
>     > properly in the WG, and the deeper implications.
> 
> I'm not sure what to do about the current statements in the appendix then.

I really can't judge whether that material is sufficiently 
baked to be normative text (even under a MAY). I do have
sympathy with making BRSKI usable more generally, but I'm
not competent to judge whether this text is ready for the
standards track.

    Brian


From nobody Mon Mar 26 16:38:23 2018
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1692F1277BB for <anima@ietfa.amsl.com>; Mon, 26 Mar 2018 16:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 qEq1y6Tooaob for <anima@ietfa.amsl.com>; Mon, 26 Mar 2018 16:38:19 -0700 (PDT)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::234]) (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 634DE12778D for <anima@ietf.org>; Mon, 26 Mar 2018 16:38:19 -0700 (PDT)
Received: by mail-pf0-x234.google.com with SMTP id a11so4794393pff.8 for <anima@ietf.org>; Mon, 26 Mar 2018 16:38:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=sender:subject:references:from:to:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=UtKdJs6tImn13oo8x8wNODY8PJCNN37N06zNaRaVc54=; b=tlZv4/xQJHh319DsahnF4Pwczq3SRrhsqQat/CKTlK0SzfXykSlNT66In7EIS+bdhX 88iTE0uef1GHUETCLcqHW/Ytw6LXKbLp6Kw0nY4frGHVL8euraLDb7LAnMBmBopuTIk7 p8HRCiEAjvh/43SlfE68O3M/aCw1C1xPhthJYW5E5aCY8YoI0Qq30WYyXEuDGVmVUqcw IBKxMthDiIhmmsSdxlCEk/8T5b3gDQ62ON+Cqq9LOLFy0l2dkJZwLivhBhuxT6Hq1flB Ks4PoTTvmjaPJOREi64BmvNwQYaoDa8QEG43rC6RNYYByDaIKWXEgmjXG8M+PSvShhFc 1hpw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:references:from:to:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=UtKdJs6tImn13oo8x8wNODY8PJCNN37N06zNaRaVc54=; b=KjGzTNPcnmiGreMftGIz3HuNl5WngcaKyc/nwQmpSnL4NhCc8M0GEjXig9e6VWymSI kwiUe1kI5JQDobFG5H5Eckn61v7mRCL+2ikTPf0+EleWaEc20XqCbWqpP12Ygy4EO4j2 3e067wK/CJeyn9zJy/HXn+eDiIYlxPBN+BoCYg9X+WOgXLVagw8B363BtlU2WjWc8tqH 9a5ARSRPsQiKMC669gD+eDFvSVADtFioQ3DUOpj6o/Pv/vj3uqCNhPRgv9roCZFmvjtG itWLP06auY54YFQl9VDPAjcijoZqbdsar/cfeHLeVjzn+HMhFz3T1SdFPb+4woUW32qT Yrrw==
X-Gm-Message-State: AElRT7FVzY5p41cgNzemBFX3/xHBIjsYNcEAb73D43/mcOp5TDSQ/W5O OOlxIZLn/B73Nrmk/kfrmmzTVg==
X-Google-Smtp-Source: AG47ELvpwLGnmtMvzcMB9ZLd9yZE9e2CEK9KVsnOXTZBWfoPo/NM82s961d+qLhfxWA+5IP/3p+3pw==
X-Received: by 10.98.174.6 with SMTP id q6mr11599081pff.140.1522107498593; Mon, 26 Mar 2018 16:38:18 -0700 (PDT)
Received: from [130.216.38.155] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.38.155]) by smtp.gmail.com with ESMTPSA id r129sm37367710pfc.83.2018.03.26.16.38.16 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Mar 2018 16:38:17 -0700 (PDT)
Sender: Brian Carpenter <becarpenter46@gmail.com>
References: <152210089715.15269.10688079396928078671@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
To: Anima WG <anima@ietf.org>
Message-ID: <ab597bf0-0770-dfb8-62bd-75f0c34f7613@gmail.com>
Date: Tue, 27 Mar 2018 12:38:16 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <152210089715.15269.10688079396928078671@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/DlFb1If2EaKp9aSClJFYHNDGk1E>
Subject: Re: [Anima] I-D Action: draft-ietf-anima-bootstrapping-keyinfra-13.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2018 23:38:21 -0000

So, page 21 says:

> ... This provides an	
> earliest date which is reasonable.  Call this the current	
> reasonable date (CRD).  This value SHOULD NOT be stored in any	
> way, and applies to the current Registration attempt only.	
> Subsequent attempts MUST follow this proceedure again from	
> scratch.  The current reasonable date may only increase.

Firstly, "SHOULD NOT be stored in any way" surely means
"SHOULD NOT be permanently stored in any way", because
it must certainly be temporarily stored during the current
registration attempt.

Secondly, "The current reasonable date may only increase."
is unverifiable unless the previous CRD is stored for
comparison.

So I think the "SHOULD NOT" clause has to go. Perhaps you
mean:
  This value MUST NOT be used for any future Registration attempt.

Regards
   Brian

On 27/03/2018 10:48, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Autonomic Networking Integrated Model and Approach WG of the IETF.
> 
>         Title           : Bootstrapping Remote Secure Key Infrastructures (BRSKI)
>         Authors         : Max Pritikin
>                           Michael C. Richardson
>                           Michael H. Behringer
>                           Steinthor Bjarnason
>                           Kent Watsen
> 	Filename        : draft-ietf-anima-bootstrapping-keyinfra-13.txt
> 	Pages           : 91
> 	Date            : 2018-03-26
> 
> Abstract:
>    This document specifies automated bootstrapping of a remote secure
>    key infrastructure (BRSKI) using manufacturer installed X.509
>    certificate, in combination with a manufacturer's authorizing
>    service, both online and offline.  Bootstrapping a new device can
>    occur using a routable address and a cloud service, or using only
>    link-local connectivity, or on limited/disconnected networks.
>    Support for lower security models, including devices with minimal
>    identity, is described for legacy reasons but not encouraged.
>    Bootstrapping is complete when the cryptographic identity of the new
>    key infrastructure is successfully deployed to the device but the
>    established secure connection can be used to deploy a locally issued
>    certificate to the device as well.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-anima-bootstrapping-keyinfra/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-anima-bootstrapping-keyinfra-13
> https://datatracker.ietf.org/doc/html/draft-ietf-anima-bootstrapping-keyinfra-13
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-anima-bootstrapping-keyinfra-13
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 


From nobody Tue Mar 27 06:11:31 2018
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA4E212D95E for <anima@ietfa.amsl.com>; Tue, 27 Mar 2018 06:11:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 YuGlE8FZ4Bdf for <anima@ietfa.amsl.com>; Tue, 27 Mar 2018 06:11:28 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D7B112DA02 for <anima@ietf.org>; Tue, 27 Mar 2018 06:11:28 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7D4DA20090; Tue, 27 Mar 2018 09:20:47 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id CC98C80B01; Tue, 27 Mar 2018 09:11:26 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: Anima WG <anima@ietf.org>
In-Reply-To: <ab597bf0-0770-dfb8-62bd-75f0c34f7613@gmail.com>
References: <152210089715.15269.10688079396928078671@ietfa.amsl.com> <ab597bf0-0770-dfb8-62bd-75f0c34f7613@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Tue, 27 Mar 2018 09:11:26 -0400
Message-ID: <8412.1522156286@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/lgawH5kRJksNp5YBf_OZjxcXflM>
Subject: Re: [Anima] I-D Action: draft-ietf-anima-bootstrapping-keyinfra-13.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Mar 2018 13:11:30 -0000

--=-=-=
Content-Type: text/plain


Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > So, page 21 says:

    >> ... This provides an
    >> earliest date which is reasonable.  Call this the current
    >> reasonable date (CRD).  This value SHOULD NOT be stored in any
    >> way, and applies to the current Registration attempt only.
    >> Subsequent attempts MUST follow this proceedure again from
    >> scratch.  The current reasonable date may only increase.

    > Firstly, "SHOULD NOT be stored in any way" surely means
    > "SHOULD NOT be permanently stored in any way", because
    > it must certainly be temporarily stored during the current
    > registration attempt.

    > Secondly, "The current reasonable date may only increase."
    > is unverifiable unless the previous CRD is stored for
    > comparison.

    > So I think the "SHOULD NOT" clause has to go. Perhaps you
    > mean:
    >    This value MUST NOT be used for any future Registration attempt.

Edited as you suggest!


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlq6Qv4ACgkQgItw+93Q
3WXakggAnmmHGRo6bvYbs/HksRtjiYHDu1uhgGqnwuwjf4w6e0G4r0Y1utm/mWb0
qsm0T32t8UGvRmgGx1KHfH/21horG81B+qhmyQ1swYsWWjudewWDZbllOYUxb4SI
MfUQ/CqbMfcG/CLtAzikgEr+K/IKNumJ9zMr5Prscx/ne+5w6smuF3OD4wfGwsmV
u+jh1wkCXbqX/PTvNzcVPrtipwZgJTMa2yNIRiYIYtns4Ib2VAeLWxO5tr5d6MuY
3Vh2R+z/VRw/urtrcAtcpq1dECC699+PiUpkZG+ajAROA7Ue4dcLCAhfDqKRXlgV
X7aDfzzFPUgiwUoSpLy1bqQuHtkOKw==
=1yh4
-----END PGP SIGNATURE-----
--=-=-=--

