
From nobody Fri Mar  1 13:18:28 2019
Return-Path: <agenda@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 E6029131243; Fri,  1 Mar 2019 13:10:15 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <anima-chairs@ietf.org>, <jiangsheng@huawei.com>
Cc: ibagdona@gmail.com, anima@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.92.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155147461593.6101.916936378354625799.idtracker@ietfa.amsl.com>
Date: Fri, 01 Mar 2019 13:10:15 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/kjsQjXCdySuFfHPUzIxx_cy-wGE>
Subject: [Anima] anima - Requested session has been scheduled for IETF 104
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Mar 2019 21:10:32 -0000

Dear Sheng Jiang,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 


    anima Session 1 (2:00 requested)
    Tuesday, 26 March 2019, Afternoon Session I 1350-1550
    Room Name: Karlin 1/2 size: 150
    ---------------------------------------------


iCalendar: https://datatracker.ietf.org/meeting/104/sessions/anima.ics

Request Information:


---------------------------------------------------------
Working Group Name: Autonomic Networking Integrated Model and Approach
Area Name: Operations and Management Area
Session Requester: Sheng Jiang

Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 80
Conflicts to Avoid: 
 First Priority: 6tisch nmrg 6lo 6man
 Second Priority: roll homenet netconf detnet
 Third Priority: cfrg saag intarea opsarea dinrg panrg


People who must be present:
  Toerless T. Eckert
  Sheng Jiang
  Ignas Bagdonas

Resources Requested:

Special Requests:
  The WG prefers to have meeting on Monday/Tuesday/Wednesday if possible.
---------------------------------------------------------


From nobody Fri Mar  1 13:34:44 2019
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 0EEE8130FB1 for <anima@ietfa.amsl.com>; Fri,  1 Mar 2019 13:34:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 UdSmW2Gm1JUH for <anima@ietfa.amsl.com>; Fri,  1 Mar 2019 13:34:29 -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 4A6F6130F65 for <anima@ietf.org>; Fri,  1 Mar 2019 13:34:29 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 526E83826B; Fri,  1 Mar 2019 16:34:27 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 93D341808; Fri,  1 Mar 2019 16:34:27 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 90BC717E3; Fri,  1 Mar 2019 16:34:27 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: anima@ietf.org, brian.e.carpenter@gmail.com
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.7+dev; 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: Fri, 01 Mar 2019 16:34:27 -0500
Message-ID: <24947.1551476067@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/iqCLgGy_bKmKUmb1jdXVCfG6AWU>
Subject: [Anima] $transport-proto in BRSKI
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Mar 2019 21:34:43 -0000

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


Brian, we have CDDL in BRSKI:

ipv6-address      = the v6 LL of the Proxy
$transport-proto /= IPPROTO_TCP   ; note this can be any value from the
                                 ; IANA protocol registry, as per
                                 ; [GRASP] section 2.9.5.1, note 3.

and we don't know why we have a $ on transport-proto.
Maybe it's a typo.

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





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

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

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlx5pWMACgkQgItw+93Q
3WW9GwgAjruRL7/Q3kOIlBGoeqlMBhhmVf2xqlnGxAry7JxPmq2NcBDxMzvHYKJ4
m9GEzfhhmTBw15NhP0Ff0DsxdvazR19XhsVX82n3yYJQwES7jlCwdg+qOl38NHd3
AsK4s1/KVcsmcQ8OygUcXUotx5aeAhZjJxYuC3b/kzUlaMqQG0HLHJQx7iZ3ZJ13
16FhhLZNuJ3O9UyVe46fzNirrrzP6mKyTeEwvTHKT/AMSJp7SwlPwlc+dhGlwGA9
m+LSmPJvnZK9WFadUWpwRdug3MV/it6GyfIStjTvEBn6xZsIMGhj6UBQhz9fuWML
ryBmTXauuqWPLDQrqiLYlbQDxuDPlg==
=Ao1P
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Mar  1 14:43:12 2019
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 BF2C5130F4C for <anima@ietfa.amsl.com>; Fri,  1 Mar 2019 14:43:10 -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 Wtk9P759ig1k for <anima@ietfa.amsl.com>; Fri,  1 Mar 2019 14:43:08 -0800 (PST)
Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (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 93981127AC2 for <anima@ietf.org>; Fri,  1 Mar 2019 14:43:08 -0800 (PST)
Received: by mail-pg1-x531.google.com with SMTP id h8so11590263pgp.6 for <anima@ietf.org>; Fri, 01 Mar 2019 14:43:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=fEv44aC85qFHOaASJSEURxZSqqYwK3AP8N2Ec0lLu+Q=; b=rs2euIZAgp1N0WFJzdxao5yzFtR3LGMADAnxkZwGS8CnxHXzuYXEoqA+/sjq6rZSNu CgF8pAiMnVhN/JCZ8EF4/hN7IlsJztxZUIB47Vt35LmY9ImlWBVuOs+tt9YMP5wsNT57 s1tlA98N4BpqcVK1FmiMkAOprO7nZgwTNM06v5iYGzipoblYvIt3GIt3oElIM88Azz85 2eVYf76P0sE/QlEMkJAesTu8WTeLgxShpLBvnGSL+K8uSWJD/OqGNUKvaY9lMAERWEZO Qza9JD6YaO9qmkJzpK39aIUxMBEurhoBEk/K1rqiuvCXRQYNjjBM9KFRE2Puyu1MwW+2 wTHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=fEv44aC85qFHOaASJSEURxZSqqYwK3AP8N2Ec0lLu+Q=; b=rvdAZ9jene6TnsDdBfz3EBqyGt9FRTrFKCVFhLv5aVni1G+kub0Togbu2aYn5iSuWf MFVKATpVnMfXptI1WBCnbyinT+Ze31pjnr4IrVBB2uDKbs8gF/hicCyFKiroM00jEk1e zBqmSkW0naldhIwhgQkMjjmdE98S64FrH7m937BYuOMFbF5X+pFj5MI7h/DyEXJUMMXS 5/1hhp5lUyIIE8B7vXWLaMR2tNbFcMACgfcGOAbCvLd1kkcUAlkYtPrrHdTik7hT2cKI KEDRLQ/uB0tfjIDFNbZ7o5wCx7UmkFCXqJXZRrzGGowYBMX5iTWtRW5aYn8i363diGvv 1BcA==
X-Gm-Message-State: AHQUAuYoQzbLEnLH5MnCg7ru9sQ6GPzurbmsUPdvcv31jmjvcxRXpCOf oFZIbnk2ZApFrX6KjIFLFD+j7szd
X-Google-Smtp-Source: AHgI3IbzBGASjmm2R4aU2STXrqLGffc0vfhB/jg4jiH8nAcp2kjwALaG3V1vFk/KirYS+WGqlOifPw==
X-Received: by 2002:aa7:8508:: with SMTP id v8mr8026807pfn.14.1551480187487; Fri, 01 Mar 2019 14:43:07 -0800 (PST)
Received: from [192.168.178.30] ([118.148.79.176]) by smtp.gmail.com with ESMTPSA id f16sm28022780pgg.20.2019.03.01.14.43.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Mar 2019 14:43:06 -0800 (PST)
To: Michael Richardson <mcr@sandelman.ca>, anima@ietf.org
References: <24947.1551476067@localhost>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <9f6549c6-46a9-6a97-48c0-422cedf33512@gmail.com>
Date: Sat, 2 Mar 2019 11:43:03 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <24947.1551476067@localhost>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/ai5cVgE_aFDC4o3dHd70FMOJBp0>
Subject: Re: [Anima] $transport-proto in BRSKI
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Mar 2019 22:43:11 -0000

On 02-Mar-19 10:34, Michael Richardson wrote:
> 
> Brian, we have CDDL in BRSKI:
> 
> ipv6-address      = the v6 LL of the Proxy
> $transport-proto /= IPPROTO_TCP   ; note this can be any value from the
>                                  ; IANA protocol registry, as per
>                                  ; [GRASP] section 2.9.5.1, note 3.
> 
> and we don't know why we have a $ on transport-proto.
> Maybe it's a typo.

I think it's a typo. As additional evidence, the comment is one space
too far to the right. Editorial fix!

    Brian


From nobody Fri Mar  1 17:09:41 2019
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 0318512DDA3 for <anima@ietfa.amsl.com>; Fri,  1 Mar 2019 17:09:40 -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 wm5mdFqwCC-a for <anima@ietfa.amsl.com>; Fri,  1 Mar 2019 17:09:38 -0800 (PST)
Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (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 198C712D4F3 for <anima@ietf.org>; Fri,  1 Mar 2019 17:09:38 -0800 (PST)
Received: by mail-pg1-x535.google.com with SMTP id 196so12228094pgf.13 for <anima@ietf.org>; Fri, 01 Mar 2019 17:09:38 -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-language:content-transfer-encoding; bh=mDuBeC94tYIJKirn7gDXk4rjOoLhTt6Mkz6EvjQyi2A=; b=PE795INmZQbM/USOakMswYKyTtIHZt+cgFrVIn8JsnHKobvpQVDaKPaaQZEFDvTNeu lX6uxNWZPNay9c4A8mem2evxLJVeZ/7twhPC2YczhaWWZ9r1UMUNX2Kd+JMo+djqgmzG 38aq5OKbbCnmBMtsvdpHTGygDypJtM93ux/zoyD/dTFHmBh0Maua7XqfOqhpZXylUCyX 5w7SrgSElPUvdDw4WmqpxjzXAY5trb5JbHpQODynjvf4v+Oh86sgnt9ugGn9MmD6yRzy m3wiy4dlFFIDyykG906CS3sz8N4+hJriruxOPl30NgizV/GR+fZS0dZ88qFVe6mDQGk5 i6DA==
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-language :content-transfer-encoding; bh=mDuBeC94tYIJKirn7gDXk4rjOoLhTt6Mkz6EvjQyi2A=; b=IIlMzAbIFsTkujziXzUC58P9rOnyBNPxC6cvfwDLzCQOflEMo11AbCPO6zTrHQkEmp KuVxQQQiNhjpQx4HchZtrCKZVpHoGLOrHgZ6yP8ORY1z1EU3s9XDpKft86MDEZ/wKFR5 1Ra7Zeu9uJ1XJfOfyS3SoMcCzLcmizg12CvBSRZihTU4AZQxT+gDYQMakkJOtlyRwi8K 4GhrxUe8IovMmj3UEOwFyI1p/zphNsW6LLNs93d/1NjehhJRNqAsTXnVwPGnwiay6iw4 53BztpTo2HjGcJl4tMVSKzkYIh4hBLgZWsNQq0wHs4qHyR06vDdZm+y3hjPtLhrU5NK0 SXEg==
X-Gm-Message-State: APjAAAXPAJWGfZH1vwggqymD+wAsla2thyLqKSktujBlJP+y9qUVHczI 2TX0CVv5KkeVMRSyXHoA+NCV9AqV
X-Google-Smtp-Source: AHgI3IYNsdUSX15V2SMPAp5nw/fdjUFA8Zo7kCavC70bh4zFXtA6PSiMTcHSCDaqSd69gn5QpcgpHQ==
X-Received: by 2002:a62:7602:: with SMTP id r2mr8509964pfc.191.1551488977162;  Fri, 01 Mar 2019 17:09:37 -0800 (PST)
Received: from [192.168.178.30] ([118.148.79.176]) by smtp.gmail.com with ESMTPSA id b6sm22433717pgl.49.2019.03.01.17.09.35 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Mar 2019 17:09:36 -0800 (PST)
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
To: Anima WG <anima@ietf.org>
References: <155148867733.6203.17876831273429823351@ietfa.amsl.com>
Message-ID: <021db7ad-7908-bf3d-b734-65fcce8a6090@gmail.com>
Date: Sat, 2 Mar 2019 14:09:34 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <155148867733.6203.17876831273429823351@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/mCZQwAWp9Rxn3XSU5HJR2UVu4T0>
Subject: [Anima] Fwd: I-D Action: draft-carpenter-limited-domains-06.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 02 Mar 2019 01:09:40 -0000

A few small updates and fixes to references. Please comment on int-area@ietf.org ; the authors are wondering about next steps for this draft.

    Brian + Bing

-------- Forwarded Message --------
Subject: I-D Action: draft-carpenter-limited-domains-06.txt
Date: Fri, 01 Mar 2019 17:04:37 -0800
From: internet-drafts@ietf.org
Reply-To: internet-drafts@ietf.org
To: i-d-announce@ietf.org


A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : Limited Domains and Internet Protocols
        Authors         : Brian Carpenter
                          Bing Liu
	Filename        : draft-carpenter-limited-domains-06.txt
	Pages           : 24
	Date            : 2019-03-01

Abstract:
   There is a noticeable trend towards network requirements, behaviours
   and semantics that are specific to a limited region of the Internet
   and a particular set of requirements.  Policies, default parameters,
   the options supported, the style of network management and security
   requirements may vary.  This document reviews examples of such
   limited domains, also known as controlled environments, and emerging
   solutions, and develops a related taxonomy.  It then briefly
   discusses the standardization of protocols for limited domains.
   Finally, it shows the needs for a precise definition of limited
   domain membership and for mechanisms to allow nodes to join a domain
   securely and to find other members, including boundary nodes.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-carpenter-limited-domains/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-carpenter-limited-domains-06
https://datatracker.ietf.org/doc/html/draft-carpenter-limited-domains-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-carpenter-limited-domains-06


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 Wed Mar  6 05:27:52 2019
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 600901277DB; Wed,  6 Mar 2019 05:27:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level: 
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 u2kAun65Ay_w; Wed,  6 Mar 2019 05:27:12 -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 19563127979; Wed,  6 Mar 2019 05:27:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3970; q=dns/txt; s=iport; t=1551878832; x=1553088432; h=from:mime-version:subject:message-id:date:to; bh=ZAJ6jGWhOiN5Vx6t6lpfBXpKMlic2tWVX4iLH2ATqtk=; b=WHrSHTke8p0sA9Dt6nNM/FcpiZSVkmrr2ATX88UJc/dgtPCln6d2eFpG tLIO3WW8Gr6vhRu8L/CUaTcZq0HyOiXjbgdeahQg0DndETJey1LXQunzx Ne8RbQc3TWPtn7Ygbbbds9xaZX10QzAIHtYl+lrzz0jTf8o9u3xCdaoNj o=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ClAADYyX9c/xbLJq1kHAEBAQQBAQc?= =?us-ascii?q?EAQGBVAQBAQsBgndxEieECIh5nyiHbggDAQEjiR43Bg0BAQMBAQMBAwJtHAy?= =?us-ascii?q?FdHUBOgMCSBcBEoMiAYF1D6sdgS+KHAoFgS8BgUiJd4F/gTgfgh8Bg0oChGs?= =?us-ascii?q?xgiYCjBiFHZJaCYRUgnWLNxmKfogxim+FX4llgm0CBAYFAhSBXSKBVjMaCBs?= =?us-ascii?q?VZQGCQT6FOopUPgMwjhUBAQ?=
X-IronPort-AV: E=Sophos;i="5.58,448,1544486400";  d="asc'?scan'208,217";a="10577222"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Mar 2019 13:27:09 +0000
Received: from [10.61.245.251] ([10.61.245.251]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x26DR8W3027087 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 6 Mar 2019 13:27:08 GMT
From: Eliot Lear <lear@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_90011D31-8FEC-41CD-824D-D9EECF95D7B2"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Message-Id: <1861142E-CA19-49FD-B84E-C8CBA827D1A0@cisco.com>
Date: Wed, 6 Mar 2019 14:27:07 +0100
To: anima@ietf.org, opsawg@ietf.org, iot-dir <iot-dir@ietf.org>, emu@ietf.org,  6tisch@ietf.org, iot-onboarding@ietf.org
X-Mailer: Apple Mail (2.3445.102.3)
X-Outbound-SMTP-Client: 10.61.245.251, [10.61.245.251]
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/3Szea_HFJyq7M8Gy3qmk-4xInvU>
Subject: [Anima] On boarding again
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 06 Mar 2019 13:27:27 -0000

--Apple-Mail=_90011D31-8FEC-41CD-824D-D9EECF95D7B2
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_CC22EA77-F876-456B-990C-1A173EF746E2"


--Apple-Mail=_CC22EA77-F876-456B-990C-1A173EF746E2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi everyone,

For those who are interested in discussing onboarding, I=E2=80=99ve =
reserved an hour on Wednesday afternoon (27 Mar) at 14:00 at the IETF in =
Karlin 3.  Since our last conversation, a few of us put a bit of an =
inventory together, regarding the mechanisms that are available.  Some =
of the questions we have Aren=E2=80=99t Quite There Yet, but at least =
the inventory is coming along.

Goal of discussion this time around  would a shared understanding of how =
these mechanisms work, what sort of commonality they have, and to =
perhaps have some notion of applicability of each.

For your entertainment, you can take a look at a table=E2=80=A6 it=E2=80=99=
s a Github table so you have to scroll a bit- see =
https://github.com/iot-onboarding/catalog/blob/master/Onboard-Table.md =
<https://github.com/iot-onboarding/catalog/blob/master/Onboard-Table.md>. =
 Feel free to issue PRs.

Also, feel free to agenda bash on iot-onboarding@ietf.org =
<mailto:iot-onboarding@ietf.org>.

Eliot

--Apple-Mail=_CC22EA77-F876-456B-990C-1A173EF746E2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
everyone,<div class=3D""><br class=3D""></div><div class=3D"">For those =
who are interested in discussing onboarding, I=E2=80=99ve reserved an =
hour on Wednesday afternoon (27 Mar) at 14:00 at the IETF in Karlin 3. =
&nbsp;Since our last conversation, a few of us put a bit of an inventory =
together, regarding the mechanisms that are available. &nbsp;Some of the =
questions we have Aren=E2=80=99t Quite There Yet, but at least the =
inventory is coming along.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Goal of discussion this time around &nbsp;would a shared =
understanding of how these mechanisms work, what sort of commonality =
they have, and to perhaps have some notion of applicability of =
each.</div><div class=3D""><br class=3D""></div><div class=3D"">For your =
entertainment, you can take a look at a table=E2=80=A6 it=E2=80=99s a =
Github table so you have to scroll a bit- see&nbsp;<a =
href=3D"https://github.com/iot-onboarding/catalog/blob/master/Onboard-Tabl=
e.md" =
class=3D"">https://github.com/iot-onboarding/catalog/blob/master/Onboard-T=
able.md</a>. &nbsp;Feel free to issue PRs.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Also, feel free to agenda bash on <a =
href=3D"mailto:iot-onboarding@ietf.org" =
class=3D"">iot-onboarding@ietf.org</a>.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Eliot</div></body></html>=

--Apple-Mail=_CC22EA77-F876-456B-990C-1A173EF746E2--

--Apple-Mail=_90011D31-8FEC-41CD-824D-D9EECF95D7B2
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQEzBAEBCAAdFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAlx/yqsACgkQh7ZrRtnS
ejOx8gf8DXTBCSH9tnZt9nQN8l7LMw3qT8prii5Fgty8s4nuxJ5RaGrRz/ZQ6lvc
MsxtTVgZ+8nore496k4bAXvwLDs3DLusZVKQ3cuQJ8iS6ywapA150T8DV21rRkLe
IRpldJ4WIitJxXWFybfoZ6hIGXK9wtRbSnH32f2pBwLgdUsqlyOQwvKSBJ+kMgqD
R/fOpHB1KFyNGVcwBlJzvnXTBMo110cJuoIurxg65kd4AtW3IKvh39CWfs04hQ0N
/1ShdYSqpJgkcg7/C/CXLuNWkPjB5Qs5+dmk4r/x55Ja7duf1B96Q7/AYCorfQNE
pcu671PMkYbaj4s1iqz4+uwlwcRBFw==
=g/OO
-----END PGP SIGNATURE-----

--Apple-Mail=_90011D31-8FEC-41CD-824D-D9EECF95D7B2--


From nobody Wed Mar  6 23:29:23 2019
Return-Path: <simon@silvair.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 EB35413136D for <anima@ietfa.amsl.com>; Wed,  6 Mar 2019 23:29:04 -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, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=silvair-com.20150623.gappssmtp.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 HACW3Goomfyu for <anima@ietfa.amsl.com>; Wed,  6 Mar 2019 23:29:03 -0800 (PST)
Received: from mail-lf1-x134.google.com (mail-lf1-x134.google.com [IPv6:2a00:1450:4864:20::134]) (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 5FCF0130E64 for <anima@ietf.org>; Wed,  6 Mar 2019 23:28:58 -0800 (PST)
Received: by mail-lf1-x134.google.com with SMTP id d26so10884503lfa.1 for <anima@ietf.org>; Wed, 06 Mar 2019 23:28:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=silvair-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VTq3TR6gOeYZSrgkmf8W6IOC1Sk6VE/HogOa9W8jWyE=; b=eBfjOzqIl/f7J8MxY1XYzpWNTLVURxJpi6+duWHQpxwnT112aeXye9/Df6dMe/rpNX hA+jWcihwiD4U6YNe+YOn+WVls/nuZR3IRd3UasKE1Qq+xY2v3nkXynTUR7mQcM077lH nA1TNlfAgb4YcdijeeHibok4Ll+mfg0cKzNbhSCt2YWs20c7xsj803sEWyFJI+MbjbzG GyvZ6IQ6IPIaKu1AG3xnFxd1MLlSK1//blZBypM1/oz/mNcAakjc4uuN16XC/Dbr1mUc WsRd/Wu1rqouVHIoDZkfGk85FLhMKIKc8O/PQTxeeKNQjyKFc7GFHED8+2DPL7TC0BbL yJLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VTq3TR6gOeYZSrgkmf8W6IOC1Sk6VE/HogOa9W8jWyE=; b=ew2xSyL6cNWIjisDLkaMcCw2U3/XmjDkOdoxsBgkdit8GDn6+diszN3rHlQDboreb1 ADxxEdXzx40H7YHqaGLUrqr6iZFi4UAM3hzm/563b0hI59+1SsQlbxRL28cGOxcfwTDG OmkVFmjxZ/asb4nvq5iCZbVeapbv2G+bUDDT4cNqTYLvBi1o5dle7wi749+RL7ofopD8 2LjDI4J36nd5iwAtbUMJmhZ8tnSve6fs2wfo/WeGBoLT/5DPFICzg/+WgnVDDIcsFDH4 WGkwPbIDgUnCl12CNm35ra58GkqICphaVS6642Z/zcLDrobpFIIqDtNdu7QomLHLASu1 3DaA==
X-Gm-Message-State: APjAAAWqAAydWT42svGDRqX/Xyd5sUXksVZ5vXVXlzT0mco9rDUlHK/m zP8VyGAZ5HqIkNXYfbBCSs0H7HIk0WDug9aKFACcxQ==
X-Google-Smtp-Source: APXvYqwt1efP+C1ndA+i/xYt5iE6cnZBB4NQ1BmKw0BS5J/zM7j3rPv2ek4e4bUREHe+KXLX7zdDi3XloR9Eu426YjY=
X-Received: by 2002:a19:f10d:: with SMTP id p13mr5613116lfh.52.1551943736148;  Wed, 06 Mar 2019 23:28:56 -0800 (PST)
MIME-Version: 1.0
References: <1861142E-CA19-49FD-B84E-C8CBA827D1A0@cisco.com>
In-Reply-To: <1861142E-CA19-49FD-B84E-C8CBA827D1A0@cisco.com>
From: =?UTF-8?Q?Szymon_S=C5=82upik?= <simon@silvair.com>
Date: Thu, 7 Mar 2019 08:28:20 +0100
Message-ID: <CABNHR1zKTSooOskkyShK=-ozSRht1akfwGNonhhgqVWC=tSt3w@mail.gmail.com>
To: Eliot Lear <lear@cisco.com>
Cc: anima@ietf.org, opsawg@ietf.org, iot-dir <iot-dir@ietf.org>, emu@ietf.org,  6tisch@ietf.org, iot-onboarding@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001ad34005837c0fcb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/dD7qK3tHdvnr75xPYRHrrywrmcU>
Subject: Re: [Anima] [Iot-onboarding] On boarding again
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Mar 2019 07:29:07 -0000

--0000000000001ad34005837c0fcb
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Eliot,

It'd be great to include Bluetooth mesh in here, as (despite sharing the
brand and the underlying radio with Bluetooth LE) it is a completely
different animal, when it comes to onboarding, authentication, security. I
will add some initial bullets for Bluetooth mesh here, hope to do this
next week.

Best

Szymon Slupik
President, CTO
+1-415-696-9111

[image: Silvair]
ul. Jasnog=C3=B3rska 44
31-358 Krak=C3=B3w
Poland

www.silvair.com

[image: Facebook] <https://www.facebook.com/meetsilvair/>   [image:
LinkedIn] <https://www.linkedin.com/company/meetsilvair/>   [image: Twitter=
]
<https://twitter.com/meetsilvair>

NOTICE TO RECIPIENT
We inform you that Silvair sp. z o.o. with its registered office in Cracow
(31-358), at Jasnog=C3=B3rska Street 44 is the controller of your personal =
data.
You can find more information about processing personal data and your
rights here
<https://silvair.com/media/filer_public/e5/ba/e5ba1ed2-84e6-47da-8277-f10df=
2eed7cc/information_on_personal_data_processing_of_representative_of_entity=
_mail_contacts_to_establish_maintain_business_relationshipsfn.pdf>.

This e-mail message and any documents accompanying it contain information
that belongs to SILVAIR. This e-mail is meant for only the intended
recipient of the transmission, and may be a communication privileged by
law, confidential and/or otherwise protected from disclosure. If you
received this e-mail in error and you are not the intended recipient, any
review, use, dissemination, distribution, or copying of this e-mail or
attachment is strictly prohibited. Please notify us immediately of the
error by return e-mail and please delete this message from your system.


On Wed, Mar 6, 2019 at 2:32 PM Eliot Lear <lear@cisco.com> wrote:

> Hi everyone,
>
> For those who are interested in discussing onboarding, I=E2=80=99ve reser=
ved an
> hour on Wednesday afternoon (27 Mar) at 14:00 at the IETF in Karlin 3.
> Since our last conversation, a few of us put a bit of an inventory
> together, regarding the mechanisms that are available.  Some of the
> questions we have Aren=E2=80=99t Quite There Yet, but at least the invent=
ory is
> coming along.
>
> Goal of discussion this time around  would a shared understanding of how
> these mechanisms work, what sort of commonality they have, and to perhaps
> have some notion of applicability of each.
>
> For your entertainment, you can take a look at a table=E2=80=A6 it=E2=80=
=99s a Github
> table so you have to scroll a bit- see
> https://github.com/iot-onboarding/catalog/blob/master/Onboard-Table.md.
> Feel free to issue PRs.
>
> Also, feel free to agenda bash on iot-onboarding@ietf.org.
>
> Eliot
> --
> Iot-onboarding mailing list
> Iot-onboarding@ietf.org
> https://www.ietf.org/mailman/listinfo/iot-onboarding
>

--0000000000001ad34005837c0fcb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Eliot,<div><br></div><div>It&#39;d be great to include =
Bluetooth mesh in here, as (despite sharing the brand and the underlying ra=
dio with Bluetooth LE) it is a completely different animal, when it comes t=
o onboarding, authentication, security. I will add some initial bullets for=
 Bluetooth mesh here, hope to do this next=C2=A0week.</div><div><br></div><=
div>Best<br clear=3D"all"><div><div dir=3D"ltr" class=3D"gmail_signature" d=
ata-smartmail=3D"gmail_signature"><div dir=3D"ltr"><p>
      <font face=3D"arial, helvetica, sans-serif">
        <span style=3D"font-size:12px;line-height:1.2;color:rgb(0,0,0);font=
-weight:700">Szymon Slupik</span><br>
        <span style=3D"font-size:12px;line-height:1.2;color:rgb(0,0,0)">Pre=
sident, CTO</span><br>
        <span style=3D"font-size:12px;line-height:1.2;color:rgb(0,0,0);whit=
e-space:pre"><a href=3D"tel:+1-415-696-9111" style=3D"line-height:1.2;color=
:rgb(0,0,0)" target=3D"_blank">+1-415-696-9111</a></span>
      </font>
    </p>
    <p>
      <font face=3D"arial, helvetica, sans-serif">
        <img style=3D"font-size:12px;line-height:1.2;color:rgb(0,0,0);font-=
weight:700;width:99px;height:36px" src=3D"https://silvair.com/media/filer_p=
ublic/3c/c1/3cc16e3b-4cc1-40a6-bf47-d983fa26e1ac/silvar_logo_198x72.png" al=
t=3D"Silvair" width=3D"99" height=3D"36"><br>
        <span style=3D"font-size:12px;line-height:1.2;color:rgb(0,0,0)">ul.=
 Jasnog=C3=B3rska 44 <br>31-358 Krak=C3=B3w <br>Poland </span><br>
      </font>
    </p>
    <p>
      <font face=3D"arial, helvetica, sans-serif">
        <a style=3D"font-size:12px;line-height:1.2;color:rgb(0,0,0)" href=
=3D"http://www.silvair.com/" target=3D"_blank">www.silvair.com</a>
      </font>
    </p>
    <p>
      <font face=3D"arial, helvetica, sans-serif">
        <a style=3D"font-size:12px;line-height:1.2;color:rgb(0,0,0);font-we=
ight:700" href=3D"https://www.facebook.com/meetsilvair/" target=3D"_blank">=
<img src=3D"https://silvair.com/media/filer_public/b9/7a/b97ad3ec-94ed-4a6e=
-af5c-a73510d93e7c/ikonki_40x40_02.png" style=3D"width:20px;height:20px" al=
t=3D"Facebook" width=3D"20" height=3D"20"></a> =C2=A0
        <a style=3D"font-size:12px;line-height:1.2;color:rgb(0,0,0);font-we=
ight:700" href=3D"https://www.linkedin.com/company/meetsilvair/" target=3D"=
_blank"><img src=3D"https://silvair.com/media/filer_public/5c/c9/5cc9663b-9=
dd8-4321-b798-a6e5c7c259af/ikonki_40x40_03.png" style=3D"width:20px;height:=
20px" alt=3D"LinkedIn" width=3D"20" height=3D"20"></a> =C2=A0
        <a style=3D"font-size:12px;line-height:1.2;color:rgb(0,0,0);font-we=
ight:700" href=3D"https://twitter.com/meetsilvair" target=3D"_blank"><img s=
rc=3D"https://silvair.com/media/filer_public/c7/ee/c7ee7006-95a3-4a1f-8b89-=
8b2074b2e74a/ikonki_40x40_01.png" style=3D"width:20px;height:20px" alt=3D"T=
witter" width=3D"20" height=3D"20"></a>
      </font>
    </p>
    <p>
      <font face=3D"arial, helvetica, sans-serif">
        <span style=3D"font-size:9.33333px;line-height:1.2;color:rgb(153,15=
3,153)">NOTICE TO RECIPIENT </span><br>
        <span style=3D"font-size:9.33333px;line-height:1.2;color:rgb(153,15=
3,153)">We
 inform you that Silvair sp. z o.o. with its registered office in Cracow
 (31-358), at Jasnog=C3=B3rska Street 44 is the controller of your personal=
=20
data. You can find more information about processing personal data and=20
your rights <a href=3D"https://silvair.com/media/filer_public/e5/ba/e5ba1ed=
2-84e6-47da-8277-f10df2eed7cc/information_on_personal_data_processing_of_re=
presentative_of_entity_mail_contacts_to_establish_maintain_business_relatio=
nshipsfn.pdf" style=3D"color:black" target=3D"_blank">here</a>. </span><br>
        <span style=3D"font-size:9.33333px;line-height:1.2;color:rgb(204,20=
4,204)">This
 e-mail message and any documents accompanying it contain information=20
that belongs to SILVAIR. This e-mail is meant for only the intended=20
recipient of the transmission, and may be a communication privileged by=20
law, confidential and/or otherwise protected from disclosure. If you=20
received this e-mail in error and you are not the intended recipient,=20
any review, use, dissemination, distribution, or copying of this e-mail=20
or attachment is strictly prohibited. Please notify us immediately of=20
the error by return e-mail and please delete this message from your=20
system.=C2=A0</span><br>
      </font>
    </p></div></div></div><br></div></div><br><div class=3D"gmail_quote"><d=
iv dir=3D"ltr" class=3D"gmail_attr">On Wed, Mar 6, 2019 at 2:32 PM Eliot Le=
ar &lt;<a href=3D"mailto:lear@cisco.com">lear@cisco.com</a>&gt; wrote:<br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex"><div style=3D"overfl=
ow-wrap: break-word;">Hi everyone,<div><br></div><div>For those who are int=
erested in discussing onboarding, I=E2=80=99ve reserved an hour on Wednesda=
y afternoon (27 Mar) at 14:00 at the IETF in Karlin 3.=C2=A0 Since our last=
 conversation, a few of us put a bit of an inventory together, regarding th=
e mechanisms that are available.=C2=A0 Some of the questions we have Aren=
=E2=80=99t Quite There Yet, but at least the inventory is coming along.</di=
v><div><br></div><div>Goal of discussion this time around =C2=A0would a sha=
red understanding of how these mechanisms work, what sort of commonality th=
ey have, and to perhaps have some notion of applicability of each.</div><di=
v><br></div><div>For your entertainment, you can take a look at a table=E2=
=80=A6 it=E2=80=99s a Github table so you have to scroll a bit- see=C2=A0<a=
 href=3D"https://github.com/iot-onboarding/catalog/blob/master/Onboard-Tabl=
e.md" target=3D"_blank">https://github.com/iot-onboarding/catalog/blob/mast=
er/Onboard-Table.md</a>.=C2=A0 Feel free to issue PRs.</div><div><br></div>=
<div>Also, feel free to agenda bash on <a href=3D"mailto:iot-onboarding@iet=
f.org" target=3D"_blank">iot-onboarding@ietf.org</a>.</div><div><br></div><=
div>Eliot</div></div>-- <br>
Iot-onboarding mailing list<br>
<a href=3D"mailto:Iot-onboarding@ietf.org" target=3D"_blank">Iot-onboarding=
@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/iot-onboarding" rel=3D"nor=
eferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/iot-onboar=
ding</a><br>
</blockquote></div>

--0000000000001ad34005837c0fcb--


From nobody Wed Mar  6 23:45:33 2019
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 13A50130ED0; Wed,  6 Mar 2019 23:45:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level: 
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 cnOE45T5EL1b; Wed,  6 Mar 2019 23:45:27 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6878F128AFB; Wed,  6 Mar 2019 23:45:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12444; q=dns/txt; s=iport; t=1551944727; x=1553154327; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=IEFvKpe321J+1v0IgPQ9KfkDmTwHR3oDwiz6lKWVrYM=; b=AXHHjOrD4PxIYaxo445EHA7l+u1RGbW7m427HzUAnPtR0c6470BL7U1Q /dhEozMRiM3bw5bdF3sVbN8WT76xQlTkBQhJxLu5xZF1ucsnCLwKTmiL8 3GWgSrald3xhtdNt1ZyY+DhrMwlCrT5Ie9TH0KcR15h6vBPbP/XwZILkS E=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A5AAD3yoBc/xbLJq1hAxwBAQEEAQE?= =?us-ascii?q?HBAEBgVIGAQELAYENWIESD0EzJ4QJiHmMRyWSMIVzFIFnCAMBARgBB4RMAoR?= =?us-ascii?q?VNQgNAQEDAQEHAQMCbRwMhUoBAQECAQEBASEmJQsFCwsHEScDAgInHxEGE4M?= =?us-ascii?q?iAYFtCA+qS4EvhC8BAwQBgQyEWg+BGxQBgUiDboRUgTWBfyaBEgwTgU5+gjo?= =?us-ascii?q?+JgEBAQeBHV0LG4JDFxqCJgKIMIFKASqBdIUdhjyMHwmEVoINaYEbhh2BVYI?= =?us-ascii?q?rGYF2KYU9gyKINJANQolpgm4CBAYFAhSBSQE1gVYzGggbFTsqAYJBCTWCbwE?= =?us-ascii?q?CgkiFFIVAPgMwjhEBAQ?=
X-IronPort-AV: E=Sophos;i="5.58,451,1544486400";  d="asc'?scan'208,217";a="10538013"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Mar 2019 07:45:23 +0000
Received: from [10.61.245.251] ([10.61.245.251]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x277jM9Q003274 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 7 Mar 2019 07:45:23 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <504E7EB5-3151-4C25-9E0D-4B8A90E7C3A5@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_9B57825A-BBDE-45E9-89EC-8D6E90D77042"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Thu, 7 Mar 2019 08:45:22 +0100
In-Reply-To: <CABNHR1zKTSooOskkyShK=-ozSRht1akfwGNonhhgqVWC=tSt3w@mail.gmail.com>
Cc: anima@ietf.org, opsawg@ietf.org, iot-dir <iot-dir@ietf.org>, emu@ietf.org,  6tisch@ietf.org, iot-onboarding@ietf.org
To: =?utf-8?Q?Szymon_S=C5=82upik?= <simon@silvair.com>
References: <1861142E-CA19-49FD-B84E-C8CBA827D1A0@cisco.com> <CABNHR1zKTSooOskkyShK=-ozSRht1akfwGNonhhgqVWC=tSt3w@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.102.3)
X-Outbound-SMTP-Client: 10.61.245.251, [10.61.245.251]
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/8Mw1NJoHnZzVCUyX_8sTBWA9xDs>
Subject: Re: [Anima] [Iot-onboarding] On boarding again
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Mar 2019 07:45:31 -0000

--Apple-Mail=_9B57825A-BBDE-45E9-89EC-8D6E90D77042
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_B4EB295A-86F9-4F34-8A76-B2A2B5222ED5"


--Apple-Mail=_B4EB295A-86F9-4F34-8A76-B2A2B5222ED5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

PRs welcome!

> On 7 Mar 2019, at 08:28, Szymon S=C5=82upik <simon@silvair.com> wrote:
>=20
> Hi Eliot,
>=20
> It'd be great to include Bluetooth mesh in here, as (despite sharing =
the brand and the underlying radio with Bluetooth LE) it is a completely =
different animal, when it comes to onboarding, authentication, security. =
I will add some initial bullets for Bluetooth mesh here, hope to do this =
next week.
>=20
> Best
> Szymon Slupik
> President, CTO
> +1-415-696-9111 <tel:+1-415-696-9111>
>=20
> ul. Jasnog=C3=B3rska 44
> 31-358 Krak=C3=B3w
> Poland
>=20
> www.silvair.com <http://www.silvair.com/>
>  <https://www.facebook.com/meetsilvair/>    =
<https://www.linkedin.com/company/meetsilvair/>    =
<https://twitter.com/meetsilvair>
> NOTICE TO RECIPIENT
> We inform you that Silvair sp. z o.o. with its registered office in =
Cracow (31-358), at Jasnog=C3=B3rska Street 44 is the controller of your =
personal data. You can find more information about processing personal =
data and your rights here =
<https://silvair.com/media/filer_public/e5/ba/e5ba1ed2-84e6-47da-8277-f10d=
f2eed7cc/information_on_personal_data_processing_of_representative_of_enti=
ty_mail_contacts_to_establish_maintain_business_relationshipsfn.pdf>.
> This e-mail message and any documents accompanying it contain =
information that belongs to SILVAIR. This e-mail is meant for only the =
intended recipient of the transmission, and may be a communication =
privileged by law, confidential and/or otherwise protected from =
disclosure. If you received this e-mail in error and you are not the =
intended recipient, any review, use, dissemination, distribution, or =
copying of this e-mail or attachment is strictly prohibited. Please =
notify us immediately of the error by return e-mail and please delete =
this message from your system.
>=20
>=20
>=20
> On Wed, Mar 6, 2019 at 2:32 PM Eliot Lear <lear@cisco.com =
<mailto:lear@cisco.com>> wrote:
> Hi everyone,
>=20
> For those who are interested in discussing onboarding, I=E2=80=99ve =
reserved an hour on Wednesday afternoon (27 Mar) at 14:00 at the IETF in =
Karlin 3.  Since our last conversation, a few of us put a bit of an =
inventory together, regarding the mechanisms that are available.  Some =
of the questions we have Aren=E2=80=99t Quite There Yet, but at least =
the inventory is coming along.
>=20
> Goal of discussion this time around  would a shared understanding of =
how these mechanisms work, what sort of commonality they have, and to =
perhaps have some notion of applicability of each.
>=20
> For your entertainment, you can take a look at a table=E2=80=A6 it=E2=80=
=99s a Github table so you have to scroll a bit- see =
https://github.com/iot-onboarding/catalog/blob/master/Onboard-Table.md =
<https://github.com/iot-onboarding/catalog/blob/master/Onboard-Table.md>. =
 Feel free to issue PRs.
>=20
> Also, feel free to agenda bash on iot-onboarding@ietf.org =
<mailto:iot-onboarding@ietf.org>.
>=20
> Eliot
> --
> Iot-onboarding mailing list
> Iot-onboarding@ietf.org <mailto:Iot-onboarding@ietf.org>
> https://www.ietf.org/mailman/listinfo/iot-onboarding =
<https://www.ietf.org/mailman/listinfo/iot-onboarding>


--Apple-Mail=_B4EB295A-86F9-4F34-8A76-B2A2B5222ED5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">PRs =
welcome!<br class=3D""><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">On 7 Mar 2019, at 08:28, Szymon S=C5=82upik =
&lt;<a href=3D"mailto:simon@silvair.com" =
class=3D"">simon@silvair.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8" =
class=3D""><div dir=3D"ltr" class=3D"">Hi Eliot,<div class=3D""><br =
class=3D""></div><div class=3D"">It'd be great to include Bluetooth mesh =
in here, as (despite sharing the brand and the underlying radio with =
Bluetooth LE) it is a completely different animal, when it comes to =
onboarding, authentication, security. I will add some initial bullets =
for Bluetooth mesh here, hope to do this next&nbsp;week.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Best<br clear=3D"all" =
class=3D""><div class=3D""><div dir=3D"ltr" class=3D"gmail_signature" =
data-smartmail=3D"gmail_signature"><div dir=3D"ltr" class=3D""><p =
class=3D"">
      <font face=3D"arial, helvetica, sans-serif" class=3D"">
        <span style=3D"font-size: 12px; line-height: 1.2; font-weight: =
700;" class=3D"">Szymon Slupik</span><br class=3D"">
        <span style=3D"font-size: 12px; line-height: 1.2;" =
class=3D"">President, CTO</span><br class=3D"">
        <span style=3D"font-size: 12px; line-height: 1.2; white-space: =
pre;" class=3D""><a href=3D"tel:+1-415-696-9111" style=3D"line-height: =
1.2;" target=3D"_blank" class=3D"">+1-415-696-9111</a></span>
      </font>
    </p><p class=3D"">
      <font face=3D"arial, helvetica, sans-serif" class=3D"">
        <img style=3D"font-size: 12px; line-height: 1.2; font-weight: =
700; width: 99px; height: 36px;" =
src=3D"https://silvair.com/media/filer_public/3c/c1/3cc16e3b-4cc1-40a6-bf4=
7-d983fa26e1ac/silvar_logo_198x72.png" alt=3D"Silvair" width=3D"99" =
height=3D"36" class=3D""><br class=3D"">
        <span style=3D"font-size: 12px; line-height: 1.2;" class=3D"">ul. =
Jasnog=C3=B3rska 44 <br class=3D"">31-358 Krak=C3=B3w <br =
class=3D"">Poland </span><br class=3D"">
      </font>
    </p><p class=3D"">
      <font face=3D"arial, helvetica, sans-serif" class=3D"">
        <a style=3D"font-size: 12px; line-height: 1.2;" =
href=3D"http://www.silvair.com/" target=3D"_blank" =
class=3D"">www.silvair.com</a>
      </font>
    </p><p class=3D"">
      <font face=3D"arial, helvetica, sans-serif" class=3D"">
        <a style=3D"font-size: 12px; line-height: 1.2; font-weight: =
700;" href=3D"https://www.facebook.com/meetsilvair/" target=3D"_blank" =
class=3D""><img =
src=3D"https://silvair.com/media/filer_public/b9/7a/b97ad3ec-94ed-4a6e-af5=
c-a73510d93e7c/ikonki_40x40_02.png" style=3D"width:20px;height:20px" =
alt=3D"Facebook" width=3D"20" height=3D"20" class=3D""></a> &nbsp;
        <a style=3D"font-size: 12px; line-height: 1.2; font-weight: =
700;" href=3D"https://www.linkedin.com/company/meetsilvair/" =
target=3D"_blank" class=3D""><img =
src=3D"https://silvair.com/media/filer_public/5c/c9/5cc9663b-9dd8-4321-b79=
8-a6e5c7c259af/ikonki_40x40_03.png" style=3D"width:20px;height:20px" =
alt=3D"LinkedIn" width=3D"20" height=3D"20" class=3D""></a> &nbsp;
        <a style=3D"font-size: 12px; line-height: 1.2; font-weight: =
700;" href=3D"https://twitter.com/meetsilvair" target=3D"_blank" =
class=3D""><img =
src=3D"https://silvair.com/media/filer_public/c7/ee/c7ee7006-95a3-4a1f-8b8=
9-8b2074b2e74a/ikonki_40x40_01.png" style=3D"width:20px;height:20px" =
alt=3D"Twitter" width=3D"20" height=3D"20" class=3D""></a>
      </font>
    </p><p class=3D"">
      <font face=3D"arial, helvetica, sans-serif" class=3D"">
        <span =
style=3D"font-size:9.33333px;line-height:1.2;color:rgb(153,153,153)" =
class=3D"">NOTICE TO RECIPIENT </span><br class=3D"">
        <span =
style=3D"font-size:9.33333px;line-height:1.2;color:rgb(153,153,153)" =
class=3D"">We
 inform you that Silvair sp. z o.o. with its registered office in Cracow
 (31-358), at Jasnog=C3=B3rska Street 44 is the controller of your =
personal=20
data. You can find more information about processing personal data and=20=

your rights <a =
href=3D"https://silvair.com/media/filer_public/e5/ba/e5ba1ed2-84e6-47da-82=
77-f10df2eed7cc/information_on_personal_data_processing_of_representative_=
of_entity_mail_contacts_to_establish_maintain_business_relationshipsfn.pdf=
" style=3D"" target=3D"_blank" class=3D"">here</a>. </span><br class=3D"">=

        <span =
style=3D"font-size:9.33333px;line-height:1.2;color:rgb(204,204,204)" =
class=3D"">This
 e-mail message and any documents accompanying it contain information=20
that belongs to SILVAIR. This e-mail is meant for only the intended=20
recipient of the transmission, and may be a communication privileged by=20=

law, confidential and/or otherwise protected from disclosure. If you=20
received this e-mail in error and you are not the intended recipient,=20
any review, use, dissemination, distribution, or copying of this e-mail=20=

or attachment is strictly prohibited. Please notify us immediately of=20
the error by return e-mail and please delete this message from your=20
system.&nbsp;</span><br class=3D"">
      </font>
    </p></div></div></div><br class=3D""></div></div><br class=3D""><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Mar =
6, 2019 at 2:32 PM Eliot Lear &lt;<a href=3D"mailto:lear@cisco.com" =
class=3D"">lear@cisco.com</a>&gt; wrote:<br class=3D""></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div style=3D"overflow-wrap: =
break-word;" class=3D"">Hi everyone,<div class=3D""><br =
class=3D""></div><div class=3D"">For those who are interested in =
discussing onboarding, I=E2=80=99ve reserved an hour on Wednesday =
afternoon (27 Mar) at 14:00 at the IETF in Karlin 3.&nbsp; Since our =
last conversation, a few of us put a bit of an inventory together, =
regarding the mechanisms that are available.&nbsp; Some of the questions =
we have Aren=E2=80=99t Quite There Yet, but at least the inventory is =
coming along.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Goal of discussion this time around &nbsp;would a shared =
understanding of how these mechanisms work, what sort of commonality =
they have, and to perhaps have some notion of applicability of =
each.</div><div class=3D""><br class=3D""></div><div class=3D"">For your =
entertainment, you can take a look at a table=E2=80=A6 it=E2=80=99s a =
Github table so you have to scroll a bit- see&nbsp;<a =
href=3D"https://github.com/iot-onboarding/catalog/blob/master/Onboard-Tabl=
e.md" target=3D"_blank" =
class=3D"">https://github.com/iot-onboarding/catalog/blob/master/Onboard-T=
able.md</a>.&nbsp; Feel free to issue PRs.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Also, feel free to agenda bash on <a =
href=3D"mailto:iot-onboarding@ietf.org" target=3D"_blank" =
class=3D"">iot-onboarding@ietf.org</a>.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Eliot</div></div>-- <br class=3D"">
Iot-onboarding mailing list<br class=3D"">
<a href=3D"mailto:Iot-onboarding@ietf.org" target=3D"_blank" =
class=3D"">Iot-onboarding@ietf.org</a><br class=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/iot-onboarding" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/iot-onboarding</a><br =
class=3D"">
</blockquote></div>
</div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_B4EB295A-86F9-4F34-8A76-B2A2B5222ED5--

--Apple-Mail=_9B57825A-BBDE-45E9-89EC-8D6E90D77042
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQEzBAEBCAAdFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAlyAzBIACgkQh7ZrRtnS
ejObNwf/S9p0ryCeM+wRvrAXLJ9Hm3eWsdS7ovMalP910xKYX2hjmVKytiyxiAIq
JJ27zw18ijEHivNd1zLzMJOgCR04v5YjlVpjGRpqwPuxSFQiRm4LLhJ8sRHrD5rv
/dYMrtEcclTkF/4fO6WFmeNhnPzsf5FJCdNNCDAfqIcRmoSIoNcDsfZ3J7xRrGTN
qy9FELTnNk41eUJ0GH98byFJvKvKpe4d6NLXo65r8CYkya6kQwARNgqXmRMAKNnn
TZoTcqi5Y2CI18XeyykkQANlwlTUrrvrjCASfzRBoLwrFSgs+pXP8ythUBujhqw1
wUjYaQs0v8hh1YX6BhwdXyWLBZdZ6w==
=BM1Z
-----END PGP SIGNATURE-----

--Apple-Mail=_9B57825A-BBDE-45E9-89EC-8D6E90D77042--


From nobody Thu Mar  7 09:31:47 2019
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 E21CE131169; Thu,  7 Mar 2019 09:31:37 -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.93.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: anima@ietf.org
Message-ID: <155197989787.24618.986261003160132316@ietfa.amsl.com>
Date: Thu, 07 Mar 2019 09:31:37 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/0mA2oEi8a3bzHBC03602WwxxRqw>
Subject: [Anima] I-D Action: draft-ietf-anima-bootstrapping-keyinfra-19.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Mar 2019 17:31:45 -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-19.txt
	Pages           : 101
	Date            : 2019-03-07

Abstract:
   This document specifies automated bootstrapping of an Autonomic
   Control Plane.  To do this a remote secure key infrastructure (BRSKI)
   is created 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-19
https://datatracker.ietf.org/doc/html/draft-ietf-anima-bootstrapping-keyinfra-19

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


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 Thu Mar  7 11:22:25 2019
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 950A3130F29 for <anima@ietfa.amsl.com>; Thu,  7 Mar 2019 11:22:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 vmUWjwEm1eKx for <anima@ietfa.amsl.com>; Thu,  7 Mar 2019 11:22:21 -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 31B00130EC6 for <anima@ietf.org>; Thu,  7 Mar 2019 11:22:21 -0800 (PST)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id A054A3826B; Thu,  7 Mar 2019 14:22:10 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 805B412E7; Thu,  7 Mar 2019 14:22:19 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 7D8B5AA4; Thu,  7 Mar 2019 14:22:19 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
CC: Ignas Bagdonas <ibagdona@gmail.com>
In-Reply-To: <155197989787.24618.986261003160132316@ietfa.amsl.com>
References: <155197989787.24618.986261003160132316@ietfa.amsl.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; 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, 07 Mar 2019 14:22:19 -0500
Message-ID: <20726.1551986539@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/Sjr2Yy1YNfUw3WVv1EqOa7Swef0>
Subject: Re: [Anima] I-D Action: draft-ietf-anima-bootstrapping-keyinfra-19.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Mar 2019 19:22:25 -0000

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


internet-drafts@ietf.org wrote:
    > 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-19.txt


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

While the 18 to 19 diff is probably of interest to those who have most
recently reviewed the document a diff against version 16 is probably most
useful to those who last read during the WGLC.
   https://www.ietf.org/rfcdiff?url1=draft-ietf-anima-bootstrapping-keyinfra-16&url2=draft-ietf-anima-bootstrapping-keyinfra-19

We believe that we dealt with all of the review comments raised during WGLC
and reviews, and we are ready to proceed to the IESG.

The reviews are at:
secdir:  https://mailarchive.ietf.org/arch/browse/anima/?gbt=1&index=NGsR9xGIL7k_j06FXkI_GBeJZMo
genart:  https://mailarchive.ietf.org/arch/msg/anima/iVg7MRMdBQBVFA5VFiksYFHchBU
iotdir:  https://mailarchive.ietf.org/arch/msg/anima/1N7AR8hqu2oIWuTFFd9OQOab8SI

The issues that were opened are at:
    https://github.com/anima-wg/anima-bootstrap/issues?utf8=%E2%9C%93&q=is%3Aissue+

In most cases, we have used the #issue notation that github (and trac, and..)
supports in order to link the diffs that we made to the issue number.

Major changes:
      1) new section 5.3: Registrar Authorization of Pledge
      2) new section 3.1: Nonceless Voucher Requests
      3) new section 8: Applicability to the Autonomic Control Plane (plus
      other details in the document)
      4) new section 9: Privacy Considerations:

   9.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  60
     9.1.  MASA audit log  . . . . . . . . . . . . . . . . . . . . .  60
     9.2.  What BRSKI-MASA reveals to the manufacturer . . . . . . .  61
     9.3.  Manufacturers and Used or Stolen Equipment  . . . . . . .  63
     9.4.  Manufacturers and Grey market equipment . . . . . . . . .  64
     9.5.  Some mitigations for meddling by manufacturers  . . . . .  64

      5) additions to Security Considerations:
           10.1.  DoS against MASA . . . . . . . . . . . . . . . . . . . .  66
           10.4.  Manufacturer Maintainance of trust anchors . . . . . . .  69


Issues that we have not dealt with using text.
If you want to re-open the ticket, please go ahead, but please also bring
some text that is in-scope for ANIMA ACP:

    https://github.com/anima-wg/anima-bootstrap/issues/112
    add discussion of each major mode of the protocol #112

        * We are focused on the proximity assertion that we think is the most
          secure version of the protocol.  We have described this in detail.
        * We have expanded discussion about the nonceless (offline) mechanism
          that vouchers can use.
        * There are some additional ways the protocol can be used, but we
          feel that they should be dealt with in other documents.

    https://github.com/anima-wg/anima-bootstrap/issues/110
    gen art issue #22: permanent vouchers... feature or bug. explain further
        * we think that further discussion about this is needed.
        * this is a "major mode" that belongs in an operational document.


    https://github.com/anima-wg/anima-bootstrap/issues/79
    security review issue 6: ship and forget not supported
        * a new major mode, which we do not support, and we don't know how.
        * it is out of scope for ANIMA.
        * we did add text that existing mechanisms (craft consoles) continue
          to be available.

    https://github.com/anima-wg/anima-bootstrap/issues/82
    security review issue 7: what if MASA always issues vouchers
        * "It is mentioned in
           section 6.4, which recommend that manufacturers should not do that. What
           are the consequences if they still do?"
        -> it's hard to say what will happen if implementers violate the protocol.
           Some other set of assumptions need to be made about how many
           violations the other components do.

    https://github.com/anima-wg/anima-bootstrap/issues/83
    security review issue 8: device refuses to be imprinted
        * we think the answer is that the customer ships it back.
        * we provide telemetry as to success, but if the device is broken,
          it's broken.

    https://github.com/anima-wg/anima-bootstrap/issues/86
    security review issue 13: individualization
        * the issue asks about the per-device step in manufacturing.
        *** we think that this is out-of-scope for ANI use ***
        * we considered talking about technology like:
          https://en.wikipedia.org/wiki/Physical_unclonable_function
          but ultimately, that's just another way to do TPM, so
          skirts the 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+93Q3WUFAlyBb2sACgkQgItw+93Q
3WVCcgf9GaFVQH97xIec1AwhM1DzWjvX1am9LqLJwsUwn4b37K2+Cvf7vZSHAITJ
VbIcRBdh2lmFLyX+cETCMRP0Q8ayQd/Ru0B583rWviArm1BeVZ3Xf3WPoo97Kqrg
l4vfeo3GjmnqkXyOnzcJxTLDWaLYfoZ0+3cG5seEequO3DNmFcjmUnoSL9Fz89wb
ufRdzXUzQE+4RcG2rq9GPnCPUTD/ZEMiqjFCpGDMlJURnEIJfYiPQz8kI6f6OEfq
lzEBjL/hXvjiiFivf+VPqkQO2r4Uhbm+bzZIVxY28YHD2uoKdJvPFhe7uzj/czO8
8sIK24OfgL994DPEIE7ou5phxbCWjQ==
=hL/D
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Mar  7 13:13:23 2019
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 2532A12D4EB for <anima@ietfa.amsl.com>; Thu,  7 Mar 2019 13:13:21 -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 iJHqR1PyLxPy for <anima@ietfa.amsl.com>; Thu,  7 Mar 2019 13:13:19 -0800 (PST)
Received: from mail-pg1-x52b.google.com (mail-pg1-x52b.google.com [IPv6:2607:f8b0:4864:20::52b]) (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 209C212F19D for <anima@ietf.org>; Thu,  7 Mar 2019 13:13:19 -0800 (PST)
Received: by mail-pg1-x52b.google.com with SMTP id 125so12009304pgc.12 for <anima@ietf.org>; Thu, 07 Mar 2019 13:13:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=aLsm+gpcsPDRElPZyHAGCsSGP6juIXQ3/U+T4NsFlGM=; b=vXSteXrsDJ+n/ACtmu0SNHnwuvq/2Kpp/VfntA9iHF4TD5gF/GVe029j25B/cNtFFL B8AI+MhVG3npMmytNVVZeuwxeF+nVwOoMAXCt5imsHSXBkImuXGJ6QCFvC0d+fs+zF0v X+eNkL7EJWquLYDUjRx81jrc3wEHntiQimOLxO1xiIHQSA+fVtpQPav0/KOdT4Y6Dqf/ nZ74Ryzosi9c1NLj4QZkHKz7Fq2mefehfICa65ctYu2C/TXNDhc8dQ5WeWhnz1VGTx1G V4Xk8vit78TaphdATUzlqcOsgT5XEc+IwVu5AeitaZVqAFHIj78gzELQTBpICzROB936 TPaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=aLsm+gpcsPDRElPZyHAGCsSGP6juIXQ3/U+T4NsFlGM=; b=iLArGLp0SdYnyxyYoYLqVGncDCadyqlkCIe05fps0+hDNAXC6RvQfUBYMxXJyf4bSe S6LV9ON16xIyVv1c1odKJhUjzTw3KAmAgqI9IKDnJ+BwUvg52AGU4u2tygjuz+dggVvM hAAaa0Gwki6m7FvuPfknhh1/cwJ4TQiydlkSMXpzxbHEHosBTCkuioSywBRRO9s8QnQi NZrv6AUbtq96UwCoxVjRfzmFPKrWEZ8x/WUcCj5eNR6+3CLmRdGFeuifCwI5U8y27tnR HqOhLUMepCmkCKSKxATxfGrKA83WXpzE5BoUOIRqEWPIlWS1p0k6ICO6jDTOWWu317fD 9A4w==
X-Gm-Message-State: APjAAAWGLEMG4nWVNAKxMTeCiLsRmhMdsyRIn2QNxk1F6wvPyZj3TztD /UucXUaTWcDZqng0q0xyrvnPrKrD
X-Google-Smtp-Source: APXvYqyVBkcKeF1Avxq2x5SF8oITnDqS1xmqSEYhLzoDmYoHUyX4tHS6LUfL8RM47AYUqKUc7tAK+w==
X-Received: by 2002:a17:902:e00d:: with SMTP id ca13mr14919336plb.206.1551993198194;  Thu, 07 Mar 2019 13:13:18 -0800 (PST)
Received: from [192.168.178.30] ([118.148.79.176]) by smtp.gmail.com with ESMTPSA id u26sm8017446pfn.166.2019.03.07.13.13.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Mar 2019 13:13:17 -0800 (PST)
To: Michael Richardson <mcr@sandelman.ca>, anima@ietf.org
References: <24947.1551476067@localhost> <9f6549c6-46a9-6a97-48c0-422cedf33512@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <bfba6194-6dcf-cab9-f20c-b1336fa48012@gmail.com>
Date: Fri, 8 Mar 2019 10:13:15 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <9f6549c6-46a9-6a97-48c0-422cedf33512@gmail.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/OHFHnoa5aBOEUCrLwsBWyDcjCXM>
Subject: Re: [Anima] $transport-proto in BRSKI
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Mar 2019 21:13:21 -0000

Sigh. I was wrong. The $ sign is legal CDDL:

> Per convention, CDDL extension points are marked with a leading
> dollar sign (types) or two leading dollar signs (groups).
[draft-ietf-cbor-cddl-07]

It isn't *required* but it shows that the item in question is expected
to be extended in future.

So either include it or don't, but at the moment there's a nit in
your text: the syntax says
> transport-proto /= IPPROTO_TCP
but the following paragraph says:
> The $transport-proto above indicates the method...

Otherwise, fwiw I'm happy with bootstrapping-keyinfra-19.

   Brian

On 02-Mar-19 11:43, Brian E Carpenter wrote:
> On 02-Mar-19 10:34, Michael Richardson wrote:
>>
>> Brian, we have CDDL in BRSKI:
>>
>> ipv6-address      = the v6 LL of the Proxy
>> $transport-proto /= IPPROTO_TCP   ; note this can be any value from the
>>                                  ; IANA protocol registry, as per
>>                                  ; [GRASP] section 2.9.5.1, note 3.
>>
>> and we don't know why we have a $ on transport-proto.
>> Maybe it's a typo.
> 
> I think it's a typo. As additional evidence, the comment is one space
> too far to the right. Editorial fix!
> 
>     Brian
> 


From nobody Thu Mar  7 22:59:30 2019
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 067901311FD; Thu,  7 Mar 2019 22:59:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 muofbax3tnCj; Thu,  7 Mar 2019 22:59:27 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 788C4130EC1; Thu,  7 Mar 2019 22:59:27 -0800 (PST)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id CE36D449E5C081B28160; Fri,  8 Mar 2019 06:59:24 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 8 Mar 2019 06:59:24 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0415.000; Fri, 8 Mar 2019 14:59:16 +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: =?gb2312?B?Q2FsbCBmb3IgYWdlbmRhIEFOSU1BIEAgSUVURiAxMDSjrCBQcmFndWU=?=
Thread-Index: AdTVSp7fUdNBEg1lSfyRueXgFJmsUw==
Date: Fri, 8 Mar 2019 06:59:16 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B929035710C@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_5D36713D8A4E7348A7E10DF7437A4B929035710CNKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/10rtb9Dh_RdG1o3qGiiVRyrhdx8>
Subject: [Anima] =?gb2312?b?Q2FsbCBmb3IgYWdlbmRhIEFOSU1BIEAgSUVURiAxMDQ=?= =?gb2312?b?o6wgUHJhZ3Vl?=
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Mar 2019 06:59:30 -0000

--_000_5D36713D8A4E7348A7E10DF7437A4B929035710CNKGEML515MBXchi_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

SGksIGFsbCBhbmltYSwNCg0KDQoNCldlIGhhdmUgYmVlbiBhbGxvY2F0ZWQgYSBzZXNzaW9uIG9m
IDItaG91ciBmb3IgdGhlIEFOSU1BIFdHIG1lZXRpbmcgZm9yIElFVEYtMTA0IChQcmFndWUpIC0g
VHVlc2RheSBhZnRlcm5vb24gc2Vzc2lvbiBJLiBXZSBhcmUgbm93IHN0YXJ0aW5nIHRvIGNvbGxl
Y3QgYWdlbmRhIGl0ZW1zIGZvciB0aGUgc2Vzc2lvbi4gUGxlYXNlIHNlbmQgeW91ciByZXF1ZXN0
IGZvciBhZ2VuZGEgYnkgTWFyY2ggMTR0aCwgVGh1cnNkYXkuDQoNCg0KDQpGb3IgdGhpcyBjb21p
bmcgbWVldGluZywgd2Ugd291bGQgbGlrZSB0byBkaXNjdXNzIHBvdGVudGlhbCBmdXR1cmUgQU5J
TUEgd29ya3MuIEFzIG5vcm1hbCwgdGhlIHByaW9yaXR5IGFtb25nIHRoZXNlIG5vbi1jaGFydGVy
IHdvcmsgaXRlbXMgd291bGQgYmU6IHRoZXNlIHRoYXQgaGF2ZSBhY3RpdmUgZGlzY3Vzc2lvbiBp
biBtYWlsIGxpc3QsIHRoZW4gdGhlc2UgaGF2ZSBzdWJtaXR0ZWQgZHJhZnRzLCBhbmQgdG9waWNz
IHdpdGhvdXQgZHJhZnRzLg0KDQoNCg0KUGxlYXNlIHNlbmQgdXMgKGFuaW1hLWNoYWlycyBhdCBp
ZXRmLm9yZzxodHRwczovL2lldGYub3JnLz4pIHJlcXVlc3RzIGZvciB0aW1lIHNsb3QgYnkgTWFy
Y2ggMTR0aCwgVGh1cnNkYXkgYW5kIGluY2x1ZGU6DQoNCg0KDQpOYW1lIG9mIHRpbWUgc2xvdDoN
Cg0KTmFtZSBvZiBkcmFmdChzKToNCg0KVGltZSByZXF1ZXN0ZWQ6DQoNClByZXNlbnRlciBuYW1l
KHMpOg0KDQoNCg0KTW9yZSBkZXRhaWxzIGFib3V0IHRoZSBJRVRGIDEwNCwgUHJhZ3VlIGNhbiBi
ZSBmb3VuZCBhdDoNCg0KDQoNCmh0dHBzOi8vd3d3LmlldGYub3JnL2hvdy9tZWV0aW5ncy8xMDQv
DQoNCg0KDQpBZ2FpbiwgcHJlc2VudGVycyBhbmQgZHJhZnQgYXV0aG9ycyBwbGVhc2UgaW52b2tl
IGFjdGl2ZSBkaXNjdXNzaW9ucyBpbiB0aGUgQU5JTUEgbGlzdC4gTWFpbCBsaXN0IGlzIGEgdmVy
eSBnb29kIHBsYWNlIHRvIGRpc2N1c3MgYW5kIHJlYWNoIGNvbnNlbnN1cyBvbiB0ZWNobmljYWwg
aXNzdWVzLg0KDQoNCg0KQmVzdCByZWdhcmRzLA0KDQoNCg0KVG9lcmxlc3MgJiBTaGVuZw0K

--_000_5D36713D8A4E7348A7E10DF7437A4B929035710CNKGEML515MBXchi_
Content-Type: text/html; charset="gb2312"
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=3Dgb2312">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:=CB=CE=CC=E5;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
	{font-family:"\@=CB=CE=CC=E5";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* 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 =D4=A4=C9=E8=B8=F1=CA=BD Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:=CB=CE=CC=E5;}
span.HTMLChar
	{mso-style-name:"HTML =D4=A4=C9=E8=B8=F1=CA=BD Char";
	mso-style-priority:99;
	mso-style-link:"HTML =D4=A4=C9=E8=B8=F1=CA=BD";
	font-family:=CB=CE=CC=E5;}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	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"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Hi, all anima,<o:p></o:p></span></pr=
e>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">We have been allocated a session of =
2-hour for the ANIMA WG meeting for IETF-104 (Prague) - Tuesday afternoon s=
ession I. We are now starting to collect agenda items for the session. Plea=
se send your request for agenda by March 14th, Thursday.<o:p></o:p></span><=
/pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">For this coming meeting, we would li=
ke to discuss potential future ANIMA works. As normal, the priority among t=
hese non-charter work items would be: these that have active discussion in =
mail list, then these have submitted drafts, and topics without drafts.<o:p=
></o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Please send us (anima-chairs at <a h=
ref=3D"https://ietf.org/"><span style=3D"color:#337AB7">ietf.org</span></a>=
) requests for time slot by March 14th, Thursday and include:<o:p></o:p></s=
pan></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Name of time slot:<o:p></o:p></span>=
</pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Name of draft(s):<o:p></o:p></span><=
/pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Time requested:<o:p></o:p></span></p=
re>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Presenter name(s):<o:p></o:p></span>=
</pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">More details about the IETF 104, Pra=
gue can be found at:<o:p></o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">https://www.ietf.org/how/meetings/10=
4/<o:p></o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Again, presenters and draft authors =
please invoke active discussions in the ANIMA list. Mail list is a very goo=
d place to discuss and reach consensus on technical issues.<o:p></o:p></spa=
n></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Best regards,<o:p></o:p></span></pre=
>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Toerless &amp; Sheng<o:p></o:p></spa=
n></pre>
</div>
</body>
</html>

--_000_5D36713D8A4E7348A7E10DF7437A4B929035710CNKGEML515MBXchi_--


From nobody Fri Mar  8 03:39:38 2019
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 B3A72127968; Fri,  8 Mar 2019 03:39:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 6IjpAUH-UiPg; Fri,  8 Mar 2019 03:39:34 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 06EC3126E5C; Fri,  8 Mar 2019 03:39:34 -0800 (PST)
Received: from lhreml709-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id C9584B56DC0F64CC57E1; Fri,  8 Mar 2019 11:39:31 +0000 (GMT)
Received: from lhreml507-mbb.china.huawei.com ([10.201.109.48]) by lhreml709-cah.china.huawei.com ([10.201.108.32]) with mapi id 14.03.0415.000;  Fri, 8 Mar 2019 11:39:21 +0000
From: Xun Xiao <Xun.Xiao@huawei.com>
To: Sheng Jiang <jiangsheng@huawei.com>, "anima@ietf.org" <anima@ietf.org>
CC: "anima-chairs@ietf.org" <anima-chairs@ietf.org>, Artur Hecker <Artur.Hecker@huawei.com>
Thread-Topic: =?iso-2022-jp?B?Q2FsbCBmb3IgYWdlbmRhIEFOSU1BIEAgSUVURiAxMDQbJEIhJBsoQiBQ?= =?iso-2022-jp?B?cmFndWU=?=
Thread-Index: AdTVSp7fUdNBEg1lSfyRueXgFJmsUwAWBVeg
Date: Fri, 8 Mar 2019 11:39:21 +0000
Message-ID: <67C6AE5A0CF6AD45A8571ED3F6E802E413864642@lhreml507-mbb>
References: <5D36713D8A4E7348A7E10DF7437A4B929035710C@NKGEML515-MBX.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B929035710C@NKGEML515-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.204.65.147]
Content-Type: multipart/alternative; boundary="_000_67C6AE5A0CF6AD45A8571ED3F6E802E413864642lhreml507mbb_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/2umnDGhN_t8uY5ZQjU97Ea9birQ>
Subject: Re: [Anima]  =?iso-2022-jp?b?Q2FsbCBmb3IgYWdlbmRhIEFOSU1BIEAgSUVURiAx?= =?iso-2022-jp?b?MDQbJEIhJBsoQiBQcmFndWU=?=
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Mar 2019 11:39:37 -0000

--_000_67C6AE5A0CF6AD45A8571ED3F6E802E413864642lhreml507mbb_
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable

Hi Sheng,

We would like to have a time slot to report the update we made for the info=
rmation-distribution draft (including updates. Thanks.


Name of time slot: Updates on Information Distribution in Autonomic Network=
ing

Name of draft(s): draft-liu-anima-grasp-distribution-10

Time requested: 10 mins

Presenter name(s): Xun Xiao and Artur Hecker

Best Regards,

Xun Xiao (=1B$B>S?W=1B(B)
Advanced Wireless Technology Lab
Munich Research Center

From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Sheng Jiang
Sent: Friday, 8 March 2019 07:59
To: anima@ietf.org
Cc: anima-chairs@ietf.org
Subject: [Anima] Call for agenda ANIMA @ IETF 104=1B$B!$=1B(B Prague


Hi, all anima,



We have been allocated a session of 2-hour for the ANIMA WG meeting for IET=
F-104 (Prague) - Tuesday afternoon session I. We are now starting to collec=
t agenda items for the session. Please send your request for agenda by Marc=
h 14th, Thursday.



For this coming meeting, we would like to discuss potential future ANIMA wo=
rks. As normal, the priority among these non-charter work items would be: t=
hese that have active discussion in mail list, then these have submitted dr=
afts, and topics without drafts.



Please send us (anima-chairs at ietf.org<https://ietf.org/>) requests for t=
ime slot by March 14th, Thursday and include:



Name of time slot:

Name of draft(s):

Time requested:

Presenter name(s):



More details about the IETF 104, Prague can be found at:



https://www.ietf.org/how/meetings/104/



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

--_000_67C6AE5A0CF6AD45A8571ED3F6E802E413864642lhreml507mbb_
Content-Type: text/html; charset="iso-2022-jp"
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=3Diso-2022-=
jp">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	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 Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:SimSun;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
p.HTML, li.HTML, div.HTML
	{mso-style-name:"HTML \9884\8BBE\683C\5F0F";
	mso-style-link:"HTML \9884\8BBE\683C\5F0F Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri",sans-serif;}
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:SimSun;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@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"EN-US" link=3D"#0563C1" vlink=3D"#954F72" style=3D"text-justi=
fy-trim:punctuation">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">Hi Sh=
eng,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">We wo=
uld like to have a time slot to report the update we made for the informati=
on-distribution draft (including updates. Thanks.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">Name of time slot: Updates on Information Distribut=
ion in Autonomic Networking<o:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">Name of draft(s): draft-liu-anima-grasp-distributio=
n-10<o:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">Time requested: 10 mins<o:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">Presenter name(s): Xun Xiao and Artur Hecker<o:p></=
o:p></span></pre>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span style=
=3D"font-size:11.0pt;color:#1F497D">Best Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span style=
=3D"font-size:11.0pt;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span style=
=3D"font-size:11.0pt;color:#1F497D">Xun Xiao (</span><span lang=3D"ZH-CN" s=
tyle=3D"font-size:11.0pt;font-family:SimSun;color:#1F497D">=1B$B>S?W=1B(B</=
span><span style=3D"font-size:11.0pt;color:#1F497D">)<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span style=
=3D"font-size:11.0pt;color:#1F497D">Advanced Wireless Technology Lab<o:p></=
o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span style=
=3D"font-size:11.0pt;color:#1F497D">Munich Research Center<o:p></o:p></span=
></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D"><o:p>=
&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><b><span st=
yle=3D"font-size:11.0pt">From:</span></b><span style=3D"font-size:11.0pt"> =
Anima [mailto:anima-bounces@ietf.org]
<b>On Behalf Of </b>Sheng Jiang<br>
<b>Sent:</b> Friday, 8 March 2019 07:59<br>
<b>To:</b> anima@ietf.org<br>
<b>Cc:</b> anima-chairs@ietf.org<br>
<b>Subject:</b> [Anima] Call for agenda ANIMA @ IETF 104</span><span lang=
=3D"ZH-CN" style=3D"font-size:11.0pt;font-family:SimSun">=1B$B!$=1B(B</span=
><span style=3D"font-size:11.0pt"> Prague<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><o:p>&nbsp;=
</o:p></p>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">Hi, all anima,<o:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">We have been allocated a session of 2-hour for the =
ANIMA WG meeting for IETF-104 (Prague) - Tuesday afternoon session I. We ar=
e now starting to collect agenda items for the session. Please send your re=
quest for agenda by March 14th, Thursday.<o:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">For this coming meeting, we would like to discuss p=
otential future ANIMA works. As normal, the priority among these non-charte=
r work items would be: these that have active discussion in mail list, then=
 these have submitted drafts, and topics without drafts.<o:p></o:p></span><=
/pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">Please send us (anima-chairs at <a href=3D"https://=
ietf.org/"><span style=3D"color:#337AB7">ietf.org</span></a>) requests for =
time slot by March 14th, Thursday and include:<o:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">Name of time slot:<o:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">Name of draft(s):<o:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">Time requested:<o:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">Presenter name(s):<o:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">More details about the IETF 104, Prague can be foun=
d at:<o:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529"><a href=3D"https://www.ietf.org/how/meetings/104/">=
https://www.ietf.org/how/meetings/104/</a><o:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">Again, presenters and draft authors please invoke a=
ctive discussions in the ANIMA list. Mail list is a very good place to disc=
uss and reach consensus on technical issues.<o:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">Best regards,<o:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">Toerless &amp; Sheng<o:p></o:p></span></pre>
</div>
</body>
</html>

--_000_67C6AE5A0CF6AD45A8571ED3F6E802E413864642lhreml507mbb_--


From nobody Fri Mar  8 10:03:12 2019
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 EDFA8131426 for <anima@ietfa.amsl.com>; Fri,  8 Mar 2019 10:03:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 d1k-PeL4fNra for <anima@ietfa.amsl.com>; Fri,  8 Mar 2019 10:03:09 -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 08CF012AF80 for <anima@ietf.org>; Fri,  8 Mar 2019 10:03:08 -0800 (PST)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id 99D1E38263; Fri,  8 Mar 2019 13:02:56 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id E0DB21C29; Fri,  8 Mar 2019 13:03:06 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id DE6A41B9D; Fri,  8 Mar 2019 13:03:06 -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: <bfba6194-6dcf-cab9-f20c-b1336fa48012@gmail.com>
References: <24947.1551476067@localhost> <9f6549c6-46a9-6a97-48c0-422cedf33512@gmail.com> <bfba6194-6dcf-cab9-f20c-b1336fa48012@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; 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: Fri, 08 Mar 2019 13:03:06 -0500
Message-ID: <5500.1552068186@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/K34VqTxFQTpWaJO--ZZhT8FmLkc>
Subject: Re: [Anima] $transport-proto in BRSKI
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Mar 2019 18:03:11 -0000

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


Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > Sigh. I was wrong. The $ sign is legal CDDL:

    >> Per convention, CDDL extension points are marked with a leading
    >> dollar sign (types) or two leading dollar signs (groups).
    > [draft-ietf-cbor-cddl-07]

    > It isn't *required* but it shows that the item in question is expected
    > to be extended in future.

    > So either include it or don't, but at the moment there's a nit in
    > your text: the syntax says
    >> transport-proto /= IPPROTO_TCP
    > but the following paragraph says:
    >> The $transport-proto above indicates the method...

    > Otherwise, fwiw I'm happy with bootstrapping-keyinfra-19.

I noticed that extra $ when reading the diff, and removed it.
I will put them all it back: I found another location where it belongs.

--
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+93Q3WUFAlyCrloACgkQgItw+93Q
3WV3Bgf+NsmvcNsFNiyMRYFKaDiEf6H4wzaNnJ6ZOLPdxbrES/sWkXHdNzOF/UOF
3UsT6ol0jFsX1IZKRlR4E/ryIyQuRz6RyOh08Jd9hE3jJko8jo/pTip4M3JfdONi
d8aLyZ1WQZEPQFfDLJw3yiAhCo9V4NFvL85PHKlm3rByYNxyK4j7QCnftNusdXE5
NxxL5I6o6sWgXxlMX8mNHM/BsPuYq4SRSg6JS5FVlDEAMjpuIf7YdU4FPhQTyWx5
SIEuE+khKAgvD1PL6YgziuFbYdqwlZ6Aq8DzoW1KVO3ztrkidoQVcaRzUOeRW7h0
9CSgFdVJ+vYwgbEMWWG5sYI/GDCO5w==
=s6fN
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sat Mar  9 05:18:41 2019
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 9E32D1279A8; Sat,  9 Mar 2019 05:18:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 OC3wMo8Q8kW0; Sat,  9 Mar 2019 05:18:38 -0800 (PST)
Received: from gecko.sbs.de (gecko.sbs.de [194.138.37.40]) (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 0D9F412796C; Sat,  9 Mar 2019 05:18:37 -0800 (PST)
Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by gecko.sbs.de (8.15.2/8.15.2) with ESMTPS id x29DIShY004216 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 9 Mar 2019 14:18:28 +0100
Received: from DEFTHW99ERLMSX.ww902.siemens.net (defthw99erlmsx.ww902.siemens.net [139.22.70.136]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTPS id x29DIRKp027278 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 9 Mar 2019 14:18:28 +0100
Received: from DEFTHW99ER0MSX.ww902.siemens.net (139.22.70.175) by DEFTHW99ERLMSX.ww902.siemens.net (139.22.70.136) with Microsoft SMTP Server (TLS) id 14.3.435.0; Sat, 9 Mar 2019 14:18:27 +0100
Received: from DENBGAT9EJ5MSX.ww902.siemens.net ([169.254.12.162]) by DEFTHW99ER0MSX.ww902.siemens.net ([139.22.70.175]) with mapi id 14.03.0435.000; Sat, 9 Mar 2019 14:18:27 +0100
From: "Fries, Steffen" <steffen.fries@siemens.com>
To: "anima@ietf.org" <anima@ietf.org>, "jiangsheng@huawei.com" <jiangsheng@huawei.com>
CC: "anima-chairs@ietf.org" <anima-chairs@ietf.org>
Thread-Topic: [Anima] Call for agenda ANIMA @ IETF 104, Prague
Thread-Index: AdTWepPKrSuPNpwNSsuu05XBytkXQQ==
Date: Sat, 9 Mar 2019 13:18:26 +0000
Message-ID: <2130DDAA-D413-47A8-8661-803EB80A553C@siemens.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_2130DDAAD41347A88661803EB80A553Csiemenscom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/cwAbJPGpbe3nGP9k0vbgOep3TyE>
Subject: Re: [Anima] Call for agenda ANIMA @ IETF 104, Prague
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 09 Mar 2019 13:18:41 -0000

--_000_2130DDAAD41347A88661803EB80A553Csiemenscom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgU2hlbmcsIGhpIFRvZXJsZXNzDQoNCkFzIGFza2VkIGVhcmxpZXIsIHdlIHdvdWxkIGxpa2Ug
dG8gaGF2ZSBhIHRpbWUgc2xvdCB0byBkaXNjdXNzIHRoZSBhc3luY2hyb25vdXMgZW5yb2xsbWVu
dCBzdXBwb3J0IGluIEJSU0tJLiBJIHdpbGwgc3VibWl0IHRoZSBjb3JyZXNwb25kaW5nIGRyYWZ0
IE1vbmRheSBsYXRlc3QuDQoNCg0KTmFtZSBvZiB0aW1lIHNsb3Q6IFN1cHBvcnQgb2YgYXN5bmNo
cm9ub3VzIGVucm9sbG1lbnQgaW4gQlJTS0kNCg0KTmFtZSBvZiBkcmFmdChzKTogZHJhZnQtZnJp
ZXMtYnJza2ktYXN5bmMtZW5yb2xsLTAwDQoNClRpbWUgcmVxdWVzdGVkOiAxMCBtaW4NCg0KUHJl
c2VudGVyIG5hbWUocyk6IFN0ZWZmZW4gRnJpZXMNCg0KDQpUaGFuayB5b3UgYW5kIGJlc3QgcmVn
YXJkcw0KU3RlZmZlbg0KDQpGcm9tOiBTaGVuZyBKaWFuZyA8amlhbmdzaGVuZ0BodWF3ZWkuY29t
PG1haWx0bzpqaWFuZ3NoZW5nQGh1YXdlaS5jb20+Pg0KU3ViamVjdDogW0FuaW1hXSBDYWxsIGZv
ciBhZ2VuZGEgQU5JTUEgQCBJRVRGIDEwNO+8jCBQcmFndWUNCkRhdGU6IDggTWFyY2ggMjAxOSBh
dCAwNzo1OToxNiBDRVQNClRvOiAiYW5pbWFAaWV0Zi5vcmc8bWFpbHRvOmFuaW1hQGlldGYub3Jn
PiIgPGFuaW1hQGlldGYub3JnPG1haWx0bzphbmltYUBpZXRmLm9yZz4+DQpDYzogImFuaW1hLWNo
YWlyc0BpZXRmLm9yZzxtYWlsdG86YW5pbWEtY2hhaXJzQGlldGYub3JnPiIgPGFuaW1hLWNoYWly
c0BpZXRmLm9yZzxtYWlsdG86YW5pbWEtY2hhaXJzQGlldGYub3JnPj4NCg0KDQpIaSwgYWxsIGFu
aW1hLA0KDQoNCg0KV2UgaGF2ZSBiZWVuIGFsbG9jYXRlZCBhIHNlc3Npb24gb2YgMi1ob3VyIGZv
ciB0aGUgQU5JTUEgV0cgbWVldGluZyBmb3IgSUVURi0xMDQgKFByYWd1ZSkgLSBUdWVzZGF5IGFm
dGVybm9vbiBzZXNzaW9uIEkuIFdlIGFyZSBub3cgc3RhcnRpbmcgdG8gY29sbGVjdCBhZ2VuZGEg
aXRlbXMgZm9yIHRoZSBzZXNzaW9uLiBQbGVhc2Ugc2VuZCB5b3VyIHJlcXVlc3QgZm9yIGFnZW5k
YSBieSBNYXJjaCAxNHRoLCBUaHVyc2RheS4NCg0KDQoNCkZvciB0aGlzIGNvbWluZyBtZWV0aW5n
LCB3ZSB3b3VsZCBsaWtlIHRvIGRpc2N1c3MgcG90ZW50aWFsIGZ1dHVyZSBBTklNQSB3b3Jrcy4g
QXMgbm9ybWFsLCB0aGUgcHJpb3JpdHkgYW1vbmcgdGhlc2Ugbm9uLWNoYXJ0ZXIgd29yayBpdGVt
cyB3b3VsZCBiZTogdGhlc2UgdGhhdCBoYXZlIGFjdGl2ZSBkaXNjdXNzaW9uIGluIG1haWwgbGlz
dCwgdGhlbiB0aGVzZSBoYXZlIHN1Ym1pdHRlZCBkcmFmdHMsIGFuZCB0b3BpY3Mgd2l0aG91dCBk
cmFmdHMuDQoNCg0KDQpQbGVhc2Ugc2VuZCB1cyAoYW5pbWEtY2hhaXJzIGF0IGlldGYub3JnPGh0
dHBzOi8vaWV0Zi5vcmcvPikgcmVxdWVzdHMgZm9yIHRpbWUgc2xvdCBieSBNYXJjaCAxNHRoLCBU
aHVyc2RheSBhbmQgaW5jbHVkZToNCg0KDQoNCk5hbWUgb2YgdGltZSBzbG90Og0KDQpOYW1lIG9m
IGRyYWZ0KHMpOg0KDQpUaW1lIHJlcXVlc3RlZDoNCg0KUHJlc2VudGVyIG5hbWUocyk6DQoNCg0K
DQpNb3JlIGRldGFpbHMgYWJvdXQgdGhlIElFVEYgMTA0LCBQcmFndWUgY2FuIGJlIGZvdW5kIGF0
Og0KDQoNCg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvaG93L21lZXRpbmdzLzEwNC8NCg0KDQoNCkFn
YWluLCBwcmVzZW50ZXJzIGFuZCBkcmFmdCBhdXRob3JzIHBsZWFzZSBpbnZva2UgYWN0aXZlIGRp
c2N1c3Npb25zIGluIHRoZSBBTklNQSBsaXN0LiBNYWlsIGxpc3QgaXMgYSB2ZXJ5IGdvb2QgcGxh
Y2UgdG8gZGlzY3VzcyBhbmQgcmVhY2ggY29uc2Vuc3VzIG9uIHRlY2huaWNhbCBpc3N1ZXMuDQoN
Cg0KDQpCZXN0IHJlZ2FyZHMsDQoNCg0KDQpUb2VybGVzcyAmIFNoZW5nDQoNCl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpBbmltYSBtYWlsaW5nIGxpc3QN
CkFuaW1hQGlldGYub3JnPG1haWx0bzpBbmltYUBpZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vYW5pbWENCg0KDQo=

--_000_2130DDAAD41347A88661803EB80A553Csiemenscom_
Content-Type: text/html; charset="utf-8"
Content-ID: <79058849A8F2514CBBF845C1407CB23C@internal.siemens.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IGRpcj0iYXV0byI+DQo8
ZGl2PkhpIFNoZW5nLCBoaSBUb2VybGVzczwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+
QXMgYXNrZWQgZWFybGllciwgd2Ugd291bGQgbGlrZSB0byBoYXZlIGEgdGltZSBzbG90IHRvIGRp
c2N1c3MgdGhlIGFzeW5jaHJvbm91cyBlbnJvbGxtZW50IHN1cHBvcnQgaW4gQlJTS0kuIEkgd2ls
bCBzdWJtaXQgdGhlIGNvcnJlc3BvbmRpbmcgZHJhZnQgTW9uZGF5IGxhdGVzdC48L2Rpdj4NCjxk
aXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgc3R5bGU9Im1hcmdpbjogMHB4OyBmb250LXN0cmV0
Y2g6IG5vcm1hbDsgbGluZS1oZWlnaHQ6IG5vcm1hbDsiPjxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5k
LWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAyNTUsIDApOyI+TmFtZSBvZiB0aW1lIHNsb3Q6IFN1cHBv
cnQgb2YgYXN5bmNocm9ub3VzIGVucm9sbG1lbnQgaW4gQlJTS0kmbmJzcDs8L3NwYW4+PC9wPg0K
PHAgc3R5bGU9Im1hcmdpbjogMHB4OyBmb250LXN0cmV0Y2g6IG5vcm1hbDsgbGluZS1oZWlnaHQ6
IG5vcm1hbDsiPjxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAy
NTUsIDApOyI+TmFtZSBvZiBkcmFmdChzKTombmJzcDs8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZTogMTJwdDsgZm9udC1mYW1pbHk6IEhlbHZldGljYTsiPmRyYWZ0LWZyaWVzLWJyc2tpLWFz
eW5jLWVucm9sbC0wMDwvc3Bhbj48L3A+DQo8cCBzdHlsZT0ibWFyZ2luOiAwcHg7IGZvbnQtc3Ry
ZXRjaDogbm9ybWFsOyBsaW5lLWhlaWdodDogbm9ybWFsOyI+PHNwYW4gc3R5bGU9ImJhY2tncm91
bmQtY29sb3I6IHJnYmEoMjU1LCAyNTUsIDI1NSwgMCk7Ij5UaW1lIHJlcXVlc3RlZDogMTAgbWlu
PC9zcGFuPjwvcD4NCjxwIHN0eWxlPSJtYXJnaW46IDBweDsgZm9udC1zdHJldGNoOiBub3JtYWw7
IGxpbmUtaGVpZ2h0OiBub3JtYWw7Ij48c3BhbiBzdHlsZT0iYmFja2dyb3VuZC1jb2xvcjogcmdi
YSgyNTUsIDI1NSwgMjU1LCAwKTsiPlByZXNlbnRlciBuYW1lKHMpOiBTdGVmZmVuIEZyaWVzPC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4mbmJzcDs8L2Rpdj4NCjxkaXY+VGhhbmsgeW91IGFuZCBi
ZXN0IHJlZ2FyZHM8L2Rpdj4NCjxkaXY+U3RlZmZlbjwvZGl2Pg0KPGJyPg0KPGJsb2NrcXVvdGUg
dHlwZT0iY2l0ZSI+DQo8ZGl2IGRpcj0ibHRyIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNs
YXNzPSIiPg0KPGRpdiBjbGFzcz0iIiBzdHlsZT0ibWFyZ2luOiAwcHg7Ij48Zm9udCBjb2xvcj0i
IzAwMDAwMCI+PHNwYW4gc3R5bGU9ImNhcmV0LWNvbG9yOiByZ2IoMCwgMCwgMCk7IGJhY2tncm91
bmQtY29sb3I6IHJnYmEoMjU1LCAyNTUsIDI1NSwgMCk7Ij48c3BhbiBjbGFzcz0iIj48YiBjbGFz
cz0iIj5Gcm9tOiZuYnNwOzwvYj48L3NwYW4+PHNwYW4gY2xhc3M9IiI+U2hlbmcgSmlhbmcgJmx0
OzxhIGhyZWY9Im1haWx0bzpqaWFuZ3NoZW5nQGh1YXdlaS5jb20iIGNsYXNzPSIiPmppYW5nc2hl
bmdAaHVhd2VpLmNvbTwvYT4mZ3Q7PGJyIGNsYXNzPSIiPg0KPC9zcGFuPjwvc3Bhbj48L2ZvbnQ+
PC9kaXY+DQo8ZGl2IGNsYXNzPSIiIHN0eWxlPSJtYXJnaW46IDBweDsiPjxmb250IGNvbG9yPSIj
MDAwMDAwIj48c3BhbiBzdHlsZT0iY2FyZXQtY29sb3I6IHJnYigwLCAwLCAwKTsgYmFja2dyb3Vu
ZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsiPjxzcGFuIGNsYXNzPSIiPjxiIGNsYXNz
PSIiPlN1YmplY3Q6Jm5ic3A7PC9iPjwvc3Bhbj48c3BhbiBjbGFzcz0iIj48YiBjbGFzcz0iIj5b
QW5pbWFdIENhbGwgZm9yIGFnZW5kYSBBTklNQSBAIElFVEYgMTA077yMIFByYWd1ZTwvYj48YnIg
Y2xhc3M9IiI+DQo8L3NwYW4+PC9zcGFuPjwvZm9udD48L2Rpdj4NCjxkaXYgY2xhc3M9IiIgc3R5
bGU9Im1hcmdpbjogMHB4OyI+PGZvbnQgY29sb3I9IiMwMDAwMDAiPjxzcGFuIHN0eWxlPSJjYXJl
dC1jb2xvcjogcmdiKDAsIDAsIDApOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAy
NTUsIDApOyI+PHNwYW4gY2xhc3M9IiI+PGIgY2xhc3M9IiI+RGF0ZTombmJzcDs8L2I+PC9zcGFu
PjxzcGFuIGNsYXNzPSIiPjggTWFyY2ggMjAxOSBhdCAwNzo1OToxNiBDRVQ8YnIgY2xhc3M9IiI+
DQo8L3NwYW4+PC9zcGFuPjwvZm9udD48L2Rpdj4NCjxkaXYgY2xhc3M9IiIgc3R5bGU9Im1hcmdp
bjogMHB4OyI+PGZvbnQgY29sb3I9IiMwMDAwMDAiPjxzcGFuIHN0eWxlPSJjYXJldC1jb2xvcjog
cmdiKDAsIDAsIDApOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAyNTUsIDApOyI+
PHNwYW4gY2xhc3M9IiI+PGIgY2xhc3M9IiI+VG86Jm5ic3A7PC9iPjwvc3Bhbj48c3BhbiBjbGFz
cz0iIj4mcXVvdDs8YSBocmVmPSJtYWlsdG86YW5pbWFAaWV0Zi5vcmciIGNsYXNzPSIiPmFuaW1h
QGlldGYub3JnPC9hPiZxdW90Ow0KICZsdDs8YSBocmVmPSJtYWlsdG86YW5pbWFAaWV0Zi5vcmci
IGNsYXNzPSIiPmFuaW1hQGlldGYub3JnPC9hPiZndDs8YnIgY2xhc3M9IiI+DQo8L3NwYW4+PC9z
cGFuPjwvZm9udD48L2Rpdj4NCjxkaXYgY2xhc3M9IiIgc3R5bGU9Im1hcmdpbjogMHB4OyI+PGZv
bnQgY29sb3I9IiMwMDAwMDAiPjxzcGFuIHN0eWxlPSJjYXJldC1jb2xvcjogcmdiKDAsIDAsIDAp
OyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAyNTUsIDApOyI+PHNwYW4gY2xhc3M9
IiI+PGIgY2xhc3M9IiI+Q2M6Jm5ic3A7PC9iPjwvc3Bhbj48c3BhbiBjbGFzcz0iIj4mcXVvdDs8
YSBocmVmPSJtYWlsdG86YW5pbWEtY2hhaXJzQGlldGYub3JnIiBjbGFzcz0iIj5hbmltYS1jaGFp
cnNAaWV0Zi5vcmc8L2E+JnF1b3Q7DQogJmx0OzxhIGhyZWY9Im1haWx0bzphbmltYS1jaGFpcnNA
aWV0Zi5vcmciIGNsYXNzPSIiPmFuaW1hLWNoYWlyc0BpZXRmLm9yZzwvYT4mZ3Q7PGJyIGNsYXNz
PSIiPg0KPC9zcGFuPjwvc3Bhbj48L2ZvbnQ+PC9kaXY+DQo8Zm9udCBjb2xvcj0iIzAwMDAwMCI+
PHNwYW4gc3R5bGU9ImNhcmV0LWNvbG9yOiByZ2IoMCwgMCwgMCk7IGJhY2tncm91bmQtY29sb3I6
IHJnYmEoMjU1LCAyNTUsIDI1NSwgMCk7Ij48YnIgY2xhc3M9IiI+DQo8L3NwYW4+PC9mb250Pg0K
PGRpdiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSIgc3R5bGU9InBhZ2U6IFdv
cmRTZWN0aW9uMTsiPg0KPHByZSBjbGFzcz0iIiBzdHlsZT0ibWFyZ2luOiAwY20gMGNtIDAuMDAw
MXB0OyI+PHNwYW4gbGFuZz0iRU4tVVMiIGNsYXNzPSIiIHN0eWxlPSJjYXJldC1jb2xvcjogcmdi
KDAsIDAsIDApOyB3aGl0ZS1zcGFjZTogbm9ybWFsOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1
NSwgMjU1LCAyNTUsIDApOyI+PGZvbnQgY29sb3I9IiMwMDAwMDAiIGZhY2U9IlVJQ1RGb250VGV4
dFN0eWxlVGFsbEJvZHkiPkhpLCBhbGwgYW5pbWEsPG86cCBjbGFzcz0iIj48L286cD48L2ZvbnQ+
PC9zcGFuPjwvcHJlPg0KPHByZSBjbGFzcz0iIiBzdHlsZT0ibWFyZ2luOiAwY20gMGNtIDAuMDAw
MXB0OyI+PHNwYW4gbGFuZz0iRU4tVVMiIGNsYXNzPSIiIHN0eWxlPSJjYXJldC1jb2xvcjogcmdi
KDAsIDAsIDApOyB3aGl0ZS1zcGFjZTogbm9ybWFsOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1
NSwgMjU1LCAyNTUsIDApOyI+PGZvbnQgY29sb3I9IiMwMDAwMDAiIGZhY2U9IlVJQ1RGb250VGV4
dFN0eWxlVGFsbEJvZHkiPiZuYnNwOzwvZm9udD48L3NwYW4+PC9wcmU+DQo8cHJlIGNsYXNzPSIi
IHN0eWxlPSJtYXJnaW46IDBjbSAwY20gMC4wMDAxcHQ7Ij48c3BhbiBsYW5nPSJFTi1VUyIgY2xh
c3M9IiIgc3R5bGU9ImNhcmV0LWNvbG9yOiByZ2IoMCwgMCwgMCk7IHdoaXRlLXNwYWNlOiBub3Jt
YWw7IGJhY2tncm91bmQtY29sb3I6IHJnYmEoMjU1LCAyNTUsIDI1NSwgMCk7Ij48Zm9udCBjb2xv
cj0iIzAwMDAwMCIgZmFjZT0iVUlDVEZvbnRUZXh0U3R5bGVUYWxsQm9keSI+V2UgaGF2ZSBiZWVu
IGFsbG9jYXRlZCBhIHNlc3Npb24gb2YgMi1ob3VyIGZvciB0aGUgQU5JTUEgV0cgbWVldGluZyBm
b3IgSUVURi0xMDQgKFByYWd1ZSkgLSBUdWVzZGF5IGFmdGVybm9vbiBzZXNzaW9uIEkuIFdlIGFy
ZSBub3cgc3RhcnRpbmcgdG8gY29sbGVjdCBhZ2VuZGEgaXRlbXMgZm9yIHRoZSBzZXNzaW9uLiBQ
bGVhc2Ugc2VuZCB5b3VyIHJlcXVlc3QgZm9yIGFnZW5kYSBieSBNYXJjaCAxNHRoLCBUaHVyc2Rh
eS48bzpwIGNsYXNzPSIiPjwvbzpwPjwvZm9udD48L3NwYW4+PC9wcmU+DQo8cHJlIGNsYXNzPSIi
IHN0eWxlPSJtYXJnaW46IDBjbSAwY20gMC4wMDAxcHQ7Ij48c3BhbiBsYW5nPSJFTi1VUyIgY2xh
c3M9IiIgc3R5bGU9ImNhcmV0LWNvbG9yOiByZ2IoMCwgMCwgMCk7IHdoaXRlLXNwYWNlOiBub3Jt
YWw7IGJhY2tncm91bmQtY29sb3I6IHJnYmEoMjU1LCAyNTUsIDI1NSwgMCk7Ij48Zm9udCBjb2xv
cj0iIzAwMDAwMCIgZmFjZT0iVUlDVEZvbnRUZXh0U3R5bGVUYWxsQm9keSI+Jm5ic3A7PC9mb250
Pjwvc3Bhbj48L3ByZT4NCjxwcmUgY2xhc3M9IiIgc3R5bGU9Im1hcmdpbjogMGNtIDBjbSAwLjAw
MDFwdDsiPjxzcGFuIGxhbmc9IkVOLVVTIiBjbGFzcz0iIiBzdHlsZT0iY2FyZXQtY29sb3I6IHJn
YigwLCAwLCAwKTsgd2hpdGUtc3BhY2U6IG5vcm1hbDsgYmFja2dyb3VuZC1jb2xvcjogcmdiYSgy
NTUsIDI1NSwgMjU1LCAwKTsiPjxmb250IGNvbG9yPSIjMDAwMDAwIiBmYWNlPSJVSUNURm9udFRl
eHRTdHlsZVRhbGxCb2R5Ij5Gb3IgdGhpcyBjb21pbmcgbWVldGluZywgd2Ugd291bGQgbGlrZSB0
byBkaXNjdXNzIHBvdGVudGlhbCBmdXR1cmUgQU5JTUEgd29ya3MuIEFzIG5vcm1hbCwgdGhlIHBy
aW9yaXR5IGFtb25nIHRoZXNlIG5vbi1jaGFydGVyIHdvcmsgaXRlbXMgd291bGQgYmU6IHRoZXNl
IHRoYXQgaGF2ZSBhY3RpdmUgZGlzY3Vzc2lvbiBpbiBtYWlsIGxpc3QsIHRoZW4gdGhlc2UgaGF2
ZSBzdWJtaXR0ZWQgZHJhZnRzLCBhbmQgdG9waWNzIHdpdGhvdXQgZHJhZnRzLjxvOnAgY2xhc3M9
IiI+PC9vOnA+PC9mb250Pjwvc3Bhbj48L3ByZT4NCjxwcmUgY2xhc3M9IiIgc3R5bGU9Im1hcmdp
bjogMGNtIDBjbSAwLjAwMDFwdDsiPjxzcGFuIGxhbmc9IkVOLVVTIiBjbGFzcz0iIiBzdHlsZT0i
Y2FyZXQtY29sb3I6IHJnYigwLCAwLCAwKTsgd2hpdGUtc3BhY2U6IG5vcm1hbDsgYmFja2dyb3Vu
ZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsiPjxmb250IGNvbG9yPSIjMDAwMDAwIiBm
YWNlPSJVSUNURm9udFRleHRTdHlsZVRhbGxCb2R5Ij4mbmJzcDs8L2ZvbnQ+PC9zcGFuPjwvcHJl
Pg0KPHByZSBjbGFzcz0iIiBzdHlsZT0ibWFyZ2luOiAwY20gMGNtIDAuMDAwMXB0OyI+PHNwYW4g
bGFuZz0iRU4tVVMiIGNsYXNzPSIiIHN0eWxlPSJjYXJldC1jb2xvcjogcmdiKDAsIDAsIDApOyB3
aGl0ZS1zcGFjZTogbm9ybWFsOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAyNTUs
IDApOyI+PGZvbnQgY29sb3I9IiMwMDAwMDAiIGZhY2U9IlVJQ1RGb250VGV4dFN0eWxlVGFsbEJv
ZHkiPlBsZWFzZSBzZW5kIHVzIChhbmltYS1jaGFpcnMgYXQgPGEgaHJlZj0iaHR0cHM6Ly9pZXRm
Lm9yZy8iIGNsYXNzPSIiPjxzcGFuIGNsYXNzPSIiPmlldGYub3JnPC9zcGFuPjwvYT4pIHJlcXVl
c3RzIGZvciB0aW1lIHNsb3QgYnkgTWFyY2ggMTR0aCwgVGh1cnNkYXkgYW5kIGluY2x1ZGU6PG86
cCBjbGFzcz0iIj48L286cD48L2ZvbnQ+PC9zcGFuPjwvcHJlPg0KPHByZSBjbGFzcz0iIiBzdHls
ZT0ibWFyZ2luOiAwY20gMGNtIDAuMDAwMXB0OyI+PHNwYW4gbGFuZz0iRU4tVVMiIGNsYXNzPSIi
IHN0eWxlPSJjYXJldC1jb2xvcjogcmdiKDAsIDAsIDApOyB3aGl0ZS1zcGFjZTogbm9ybWFsOyBi
YWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAyNTUsIDApOyI+PGZvbnQgY29sb3I9IiMw
MDAwMDAiIGZhY2U9IlVJQ1RGb250VGV4dFN0eWxlVGFsbEJvZHkiPiZuYnNwOzwvZm9udD48L3Nw
YW4+PC9wcmU+DQo8cHJlIGNsYXNzPSIiIHN0eWxlPSJtYXJnaW46IDBjbSAwY20gMC4wMDAxcHQ7
Ij48c3BhbiBsYW5nPSJFTi1VUyIgY2xhc3M9IiIgc3R5bGU9ImNhcmV0LWNvbG9yOiByZ2IoMCwg
MCwgMCk7IHdoaXRlLXNwYWNlOiBub3JtYWw7IGJhY2tncm91bmQtY29sb3I6IHJnYmEoMjU1LCAy
NTUsIDI1NSwgMCk7Ij48Zm9udCBjb2xvcj0iIzAwMDAwMCIgZmFjZT0iVUlDVEZvbnRUZXh0U3R5
bGVUYWxsQm9keSI+TmFtZSBvZiB0aW1lIHNsb3Q6PG86cCBjbGFzcz0iIj48L286cD48L2ZvbnQ+
PC9zcGFuPjwvcHJlPg0KPHByZSBjbGFzcz0iIiBzdHlsZT0ibWFyZ2luOiAwY20gMGNtIDAuMDAw
MXB0OyI+PHNwYW4gbGFuZz0iRU4tVVMiIGNsYXNzPSIiIHN0eWxlPSJjYXJldC1jb2xvcjogcmdi
KDAsIDAsIDApOyB3aGl0ZS1zcGFjZTogbm9ybWFsOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1
NSwgMjU1LCAyNTUsIDApOyI+PGZvbnQgY29sb3I9IiMwMDAwMDAiIGZhY2U9IlVJQ1RGb250VGV4
dFN0eWxlVGFsbEJvZHkiPk5hbWUgb2YgZHJhZnQocyk6PG86cCBjbGFzcz0iIj48L286cD48L2Zv
bnQ+PC9zcGFuPjwvcHJlPg0KPHByZSBjbGFzcz0iIiBzdHlsZT0ibWFyZ2luOiAwY20gMGNtIDAu
MDAwMXB0OyI+PHNwYW4gbGFuZz0iRU4tVVMiIGNsYXNzPSIiIHN0eWxlPSJjYXJldC1jb2xvcjog
cmdiKDAsIDAsIDApOyB3aGl0ZS1zcGFjZTogbm9ybWFsOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2Jh
KDI1NSwgMjU1LCAyNTUsIDApOyI+PGZvbnQgY29sb3I9IiMwMDAwMDAiIGZhY2U9IlVJQ1RGb250
VGV4dFN0eWxlVGFsbEJvZHkiPlRpbWUgcmVxdWVzdGVkOjxvOnAgY2xhc3M9IiI+PC9vOnA+PC9m
b250Pjwvc3Bhbj48L3ByZT4NCjxwcmUgY2xhc3M9IiIgc3R5bGU9Im1hcmdpbjogMGNtIDBjbSAw
LjAwMDFwdDsiPjxzcGFuIGxhbmc9IkVOLVVTIiBjbGFzcz0iIiBzdHlsZT0iY2FyZXQtY29sb3I6
IHJnYigwLCAwLCAwKTsgd2hpdGUtc3BhY2U6IG5vcm1hbDsgYmFja2dyb3VuZC1jb2xvcjogcmdi
YSgyNTUsIDI1NSwgMjU1LCAwKTsiPjxmb250IGNvbG9yPSIjMDAwMDAwIiBmYWNlPSJVSUNURm9u
dFRleHRTdHlsZVRhbGxCb2R5Ij5QcmVzZW50ZXIgbmFtZShzKTo8bzpwIGNsYXNzPSIiPjwvbzpw
PjwvZm9udD48L3NwYW4+PC9wcmU+DQo8cHJlIGNsYXNzPSIiIHN0eWxlPSJtYXJnaW46IDBjbSAw
Y20gMC4wMDAxcHQ7Ij48c3BhbiBsYW5nPSJFTi1VUyIgY2xhc3M9IiIgc3R5bGU9ImNhcmV0LWNv
bG9yOiByZ2IoMCwgMCwgMCk7IHdoaXRlLXNwYWNlOiBub3JtYWw7IGJhY2tncm91bmQtY29sb3I6
IHJnYmEoMjU1LCAyNTUsIDI1NSwgMCk7Ij48Zm9udCBjb2xvcj0iIzAwMDAwMCIgZmFjZT0iVUlD
VEZvbnRUZXh0U3R5bGVUYWxsQm9keSI+Jm5ic3A7PC9mb250Pjwvc3Bhbj48L3ByZT4NCjxwcmUg
Y2xhc3M9IiIgc3R5bGU9Im1hcmdpbjogMGNtIDBjbSAwLjAwMDFwdDsiPjxzcGFuIGxhbmc9IkVO
LVVTIiBjbGFzcz0iIiBzdHlsZT0iY2FyZXQtY29sb3I6IHJnYigwLCAwLCAwKTsgd2hpdGUtc3Bh
Y2U6IG5vcm1hbDsgYmFja2dyb3VuZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsiPjxm
b250IGNvbG9yPSIjMDAwMDAwIiBmYWNlPSJVSUNURm9udFRleHRTdHlsZVRhbGxCb2R5Ij5Nb3Jl
IGRldGFpbHMgYWJvdXQgdGhlIElFVEYgMTA0LCBQcmFndWUgY2FuIGJlIGZvdW5kIGF0OjxvOnAg
Y2xhc3M9IiI+PC9vOnA+PC9mb250Pjwvc3Bhbj48L3ByZT4NCjxwcmUgY2xhc3M9IiIgc3R5bGU9
Im1hcmdpbjogMGNtIDBjbSAwLjAwMDFwdDsiPjxzcGFuIGxhbmc9IkVOLVVTIiBjbGFzcz0iIiBz
dHlsZT0iY2FyZXQtY29sb3I6IHJnYigwLCAwLCAwKTsgd2hpdGUtc3BhY2U6IG5vcm1hbDsgYmFj
a2dyb3VuZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsiPjxmb250IGNvbG9yPSIjMDAw
MDAwIiBmYWNlPSJVSUNURm9udFRleHRTdHlsZVRhbGxCb2R5Ij4mbmJzcDs8L2ZvbnQ+PC9zcGFu
PjwvcHJlPg0KPHByZSBjbGFzcz0iIiBzdHlsZT0ibWFyZ2luOiAwY20gMGNtIDAuMDAwMXB0OyI+
PHNwYW4gbGFuZz0iRU4tVVMiIGNsYXNzPSIiIHN0eWxlPSJjYXJldC1jb2xvcjogcmdiKDAsIDAs
IDApOyB3aGl0ZS1zcGFjZTogbm9ybWFsOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1
LCAyNTUsIDApOyI+PGZvbnQgY29sb3I9IiMwMDAwMDAiIGZhY2U9IlVJQ1RGb250VGV4dFN0eWxl
VGFsbEJvZHkiPjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL2hvdy9tZWV0aW5ncy8xMDQv
IiBjbGFzcz0iIj5odHRwczovL3d3dy5pZXRmLm9yZy9ob3cvbWVldGluZ3MvMTA0LzwvYT48bzpw
IGNsYXNzPSIiPjwvbzpwPjwvZm9udD48L3NwYW4+PC9wcmU+DQo8cHJlIGNsYXNzPSIiIHN0eWxl
PSJtYXJnaW46IDBjbSAwY20gMC4wMDAxcHQ7Ij48c3BhbiBsYW5nPSJFTi1VUyIgY2xhc3M9IiIg
c3R5bGU9ImNhcmV0LWNvbG9yOiByZ2IoMCwgMCwgMCk7IHdoaXRlLXNwYWNlOiBub3JtYWw7IGJh
Y2tncm91bmQtY29sb3I6IHJnYmEoMjU1LCAyNTUsIDI1NSwgMCk7Ij48Zm9udCBjb2xvcj0iIzAw
MDAwMCIgZmFjZT0iVUlDVEZvbnRUZXh0U3R5bGVUYWxsQm9keSI+Jm5ic3A7PC9mb250Pjwvc3Bh
bj48L3ByZT4NCjxwcmUgY2xhc3M9IiIgc3R5bGU9Im1hcmdpbjogMGNtIDBjbSAwLjAwMDFwdDsi
PjxzcGFuIGxhbmc9IkVOLVVTIiBjbGFzcz0iIiBzdHlsZT0iY2FyZXQtY29sb3I6IHJnYigwLCAw
LCAwKTsgd2hpdGUtc3BhY2U6IG5vcm1hbDsgYmFja2dyb3VuZC1jb2xvcjogcmdiYSgyNTUsIDI1
NSwgMjU1LCAwKTsiPjxmb250IGNvbG9yPSIjMDAwMDAwIiBmYWNlPSJVSUNURm9udFRleHRTdHls
ZVRhbGxCb2R5Ij5BZ2FpbiwgcHJlc2VudGVycyBhbmQgZHJhZnQgYXV0aG9ycyBwbGVhc2UgaW52
b2tlIGFjdGl2ZSBkaXNjdXNzaW9ucyBpbiB0aGUgQU5JTUEgbGlzdC4gTWFpbCBsaXN0IGlzIGEg
dmVyeSBnb29kIHBsYWNlIHRvIGRpc2N1c3MgYW5kIHJlYWNoIGNvbnNlbnN1cyBvbiB0ZWNobmlj
YWwgaXNzdWVzLjxvOnAgY2xhc3M9IiI+PC9vOnA+PC9mb250Pjwvc3Bhbj48L3ByZT4NCjxwcmUg
Y2xhc3M9IiIgc3R5bGU9Im1hcmdpbjogMGNtIDBjbSAwLjAwMDFwdDsiPjxzcGFuIGxhbmc9IkVO
LVVTIiBjbGFzcz0iIiBzdHlsZT0iY2FyZXQtY29sb3I6IHJnYigwLCAwLCAwKTsgd2hpdGUtc3Bh
Y2U6IG5vcm1hbDsgYmFja2dyb3VuZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsiPjxm
b250IGNvbG9yPSIjMDAwMDAwIiBmYWNlPSJVSUNURm9udFRleHRTdHlsZVRhbGxCb2R5Ij4mbmJz
cDs8L2ZvbnQ+PC9zcGFuPjwvcHJlPg0KPHByZSBjbGFzcz0iIiBzdHlsZT0ibWFyZ2luOiAwY20g
MGNtIDAuMDAwMXB0OyI+PHNwYW4gbGFuZz0iRU4tVVMiIGNsYXNzPSIiIHN0eWxlPSJjYXJldC1j
b2xvcjogcmdiKDAsIDAsIDApOyB3aGl0ZS1zcGFjZTogbm9ybWFsOyBiYWNrZ3JvdW5kLWNvbG9y
OiByZ2JhKDI1NSwgMjU1LCAyNTUsIDApOyI+PGZvbnQgY29sb3I9IiMwMDAwMDAiIGZhY2U9IlVJ
Q1RGb250VGV4dFN0eWxlVGFsbEJvZHkiPkJlc3QgcmVnYXJkcyw8bzpwIGNsYXNzPSIiPjwvbzpw
PjwvZm9udD48L3NwYW4+PC9wcmU+DQo8cHJlIGNsYXNzPSIiIHN0eWxlPSJtYXJnaW46IDBjbSAw
Y20gMC4wMDAxcHQ7Ij48c3BhbiBsYW5nPSJFTi1VUyIgY2xhc3M9IiIgc3R5bGU9ImNhcmV0LWNv
bG9yOiByZ2IoMCwgMCwgMCk7IHdoaXRlLXNwYWNlOiBub3JtYWw7IGJhY2tncm91bmQtY29sb3I6
IHJnYmEoMjU1LCAyNTUsIDI1NSwgMCk7Ij48Zm9udCBjb2xvcj0iIzAwMDAwMCIgZmFjZT0iVUlD
VEZvbnRUZXh0U3R5bGVUYWxsQm9keSI+Jm5ic3A7PC9mb250Pjwvc3Bhbj48L3ByZT4NCjxwcmUg
Y2xhc3M9IiIgc3R5bGU9Im1hcmdpbjogMGNtIDBjbSAwLjAwMDFwdDsiPjxzcGFuIGxhbmc9IkVO
LVVTIiBjbGFzcz0iIiBzdHlsZT0iY2FyZXQtY29sb3I6IHJnYigwLCAwLCAwKTsgd2hpdGUtc3Bh
Y2U6IG5vcm1hbDsgYmFja2dyb3VuZC1jb2xvcjogcmdiYSgyNTUsIDI1NSwgMjU1LCAwKTsiPjxm
b250IGNvbG9yPSIjMDAwMDAwIiBmYWNlPSJVSUNURm9udFRleHRTdHlsZVRhbGxCb2R5Ij5Ub2Vy
bGVzcyAmYW1wOyBTaGVuZzxvOnAgY2xhc3M9IiI+PC9vOnA+PC9mb250Pjwvc3Bhbj48L3ByZT4N
CjwvZGl2Pg0KPGZvbnQgY29sb3I9IiMwMDAwMDAiPjxzcGFuIHN0eWxlPSJjYXJldC1jb2xvcjog
cmdiKDAsIDAsIDApOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2JhKDI1NSwgMjU1LCAyNTUsIDApOyI+
PHNwYW4gY2xhc3M9IiIgc3R5bGU9ImZsb2F0OiBub25lOyBkaXNwbGF5OiBpbmxpbmUgIWltcG9y
dGFudDsiPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPC9z
cGFuPjxiciBjbGFzcz0iIj4NCjxzcGFuIGNsYXNzPSIiIHN0eWxlPSJmbG9hdDogbm9uZTsgZGlz
cGxheTogaW5saW5lICFpbXBvcnRhbnQ7Ij5BbmltYSBtYWlsaW5nIGxpc3Q8L3NwYW4+PGJyIGNs
YXNzPSIiPg0KPGEgaHJlZj0ibWFpbHRvOkFuaW1hQGlldGYub3JnIiBjbGFzcz0iIj5BbmltYUBp
ZXRmLm9yZzwvYT48YnIgY2xhc3M9IiI+DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL2FuaW1hIiBjbGFzcz0iIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2FuaW1hPC9hPjwvc3Bhbj48L2ZvbnQ+PC9kaXY+DQo8L2Jsb2NrcXVvdGU+
DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxicj4NCjxkaXYgZGlyPSJsdHIiPjxicj4NCjwvZGl2
Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_2130DDAAD41347A88661803EB80A553Csiemenscom_--


From nobody Sun Mar 10 05:57:57 2019
Return-Path: <stokcons@bbhmail.nl>
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 9D429127979 for <anima@ietfa.amsl.com>; Sun, 10 Mar 2019 05:57:55 -0700 (PDT)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bbhmail.nl
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 uIsNFbyS1YBW for <anima@ietfa.amsl.com>; Sun, 10 Mar 2019 05:57:52 -0700 (PDT)
Received: from smtprelay.hostedemail.com (smtprelay0024.hostedemail.com [216.40.44.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD72D1200ED for <anima@ietf.org>; Sun, 10 Mar 2019 05:57:52 -0700 (PDT)
Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay07.hostedemail.com (Postfix) with ESMTP id 3874A181D341A for <anima@ietf.org>; Sun, 10 Mar 2019 12:57:51 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bbhmail.nl; h= mime-version:content-type:date:from:to:subject:reply-to :in-reply-to:references:message-id; s=key; bh=4bZVllIlLGXkCRKLlX Hgcew8MUL8amo0PMyisrwrH7A=; b=NXOWcDRjmkFlG+dftowaBxrQtJSYh8q30o hfWvxU8PJODTOaQxqxlm4cXELuHeKEbV4h3m9mIjLOp+qeJeet5Nm4RPL8gmtxHV mDkyurxphhvZ+tL4relDVj1tK1qyedJJHyqiuUUn3qhO8dWAWshbnNw8y+gDhP3v fCCpNFTyk=
X-Session-Marker: 73746F6B636F6E73406262686D61696C2E6E6C
X-Spam-Summary: 2, 0, 0, , d41d8cd98f00b204, stokcons@bbhmail.nl, :, RULES_HIT:41:72:152:355:379:582:602:800:960:962:967:973:983:988:989:1152:1189:1208:1212:1221:1260:1313:1314:1345:1431:1433:1434:1436:1437:1516:1517:1518:1535:1544:1571:1575:1588:1589:1592:1594:1711:1730:1776:1792:2068:2069:2198:2199:2525:2528:2553:2559:2568:2570:2631:2682:2685:2703:2741:2859:2892:2933:2937:2939:2942:2945:2947:2951:2954:3022:3352:3622:3865:3866:3867:3868:3870:3871:3872:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4119:4250:4321:4605:5007:6117:6119:6261:6298:7875:7903:8603:9025:9163:10004:10234:11658:12740:13139:13161:13200:13229:14827, 0, RBL:error, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:fn, MSBL:0, DNSBL:neutral, Custom_rules:0:0:0, LFtime:27, LUA_SUMMARY:none
X-HE-Tag: meal13_61a36602c7243
X-Filterd-Recvd-Size: 8683
Received: from mail.bbhmail.nl (imap-ext [216.40.42.5]) (Authenticated sender: webmail@stokcons@bbhmail.nl) by omf19.hostedemail.com (Postfix) with ESMTPA for <anima@ietf.org>; Sun, 10 Mar 2019 12:57:50 +0000 (UTC)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_30a27ca0ecde3f021b348484d02f7775"
Date: Sun, 10 Mar 2019 13:57:50 +0100
From: Peter van der Stok <stokcons@bbhmail.nl>
To: Anima <anima@ietf.org>
Organization: vanderstok consultancy
Reply-To: consultancy@vanderstok.org
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <155222243884.30971.6207850210437524799.idtracker@ietfa.amsl.com>
References: <155222243884.30971.6207850210437524799.idtracker@ietfa.amsl.com>
Message-ID: <87a4865c04af5dae3bb9b5792652356a@bbhmail.nl>
X-Sender: stokcons@bbhmail.nl
User-Agent: Roundcube Webmail/1.2.7
X-Originating-IP: [5.206.216.229]
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/bxAPZVxiJwJeZAJJ_Lcd9xBSWkM>
Subject: [Anima] Fwd: New Version Notification for draft-vanderstok-anima-constrained-join-proxy-01.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 10 Mar 2019 12:57:56 -0000

--=_30a27ca0ecde3f021b348484d02f7775
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

Hi Anima,

a new version has been submitted of
draft-vanderstok-anima-constrained-join-proxy.
Differences with earlier version -0 

  00 to 01

   o  Added Contributors section

   o  Adapted content-formats to est-coaps formats

   o  Aligned examples with est-coaps examples

   o  Added statefull Proxy to stateless proxy

Looking forward to discussing the draft in Prague,

Peter 

-------- Oorspronkelijk bericht -------- 

 		ONDERWERP:
 		New Version Notification for
draft-vanderstok-anima-constrained-join-proxy-01.txt

 		DATUM:
 		2019-03-10 13:53

 		AFZENDER:
 		internet-drafts@ietf.org

 		ONTVANGER:
 		"Michael Richardson" <mcr+ietf@sandelman.ca>, "Panos Kampanakis"
<pkampana@cisco.com>, "Peter van der Stok" <consultancy@vanderstok.org>

A new version of I-D,
draft-vanderstok-anima-constrained-join-proxy-01.txt
has been successfully submitted by Peter van der Stok and posted to the
IETF repository.

Name:        draft-vanderstok-anima-constrained-join-proxy
Revision:    01
Title:        Constrained Join Proxy for Bootstrapping Protocols
Document date:    2019-03-10
Group:        Individual Submission
Pages:        17
URL:           
https://www.ietf.org/internet-drafts/draft-vanderstok-anima-constrained-join-proxy-01.txt
Status:        
https://datatracker.ietf.org/doc/draft-vanderstok-anima-constrained-join-proxy/
Htmlized:      
https://tools.ietf.org/html/draft-vanderstok-anima-constrained-join-proxy-01
Htmlized:      
https://datatracker.ietf.org/doc/html/draft-vanderstok-anima-constrained-join-proxy
Diff:          
https://www.ietf.org/rfcdiff?url2=draft-vanderstok-anima-constrained-join-proxy-01

Abstract:
   This document defines a protocol to securely assign a pledge to an
   owner, using an intermediary node between pledge and owner.  This
   intermediary node is known as a "constrained-join-proxy".

   This document extends the work of [ietf-anima-bootstrapping-keyinfra]
   by replacing the Circuit-proxy by a stateless constrained join-proxy,
   that transports routing information.

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.

The IETF Secretariat
--=_30a27ca0ecde3f021b348484d02f7775
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3DUTF-8" /></head><body style=3D'font-size: 10pt; font-family: Verdana,Gen=
eva,sans-serif'>
Hi Anima,<br /><br />a new version has been submitted of draft-vanderstok-a=
nima-constrained-join-proxy.<br />Differences with earlier version -0
<p>&nbsp; 00 to 01<br /> <br /> &nbsp;&nbsp; o&nbsp; Added Contributors sec=
tion<br /> <br /> &nbsp;&nbsp; o&nbsp; Adapted content-formats to est-coaps=
 formats<br /> <br /> &nbsp;&nbsp; o&nbsp; Aligned examples with est-coaps =
examples<br /> <br /> &nbsp;&nbsp; o&nbsp; Added statefull Proxy to statele=
ss proxy<br /><br />Looking forward to discussing the draft in Prague,<br /=
><br />Peter</p>
<p>-------- Oorspronkelijk bericht --------</p>
<table border=3D"0" cellspacing=3D"0" cellpadding=3D"0">
<tbody>
<tr>
<th align=3D"right" valign=3D"baseline" nowrap=3D"nowrap">Onderwerp:</th>
<td>New Version Notification for draft-vanderstok-anima-constrained-join-pr=
oxy-01.txt</td>
</tr>
<tr>
<th align=3D"right" valign=3D"baseline" nowrap=3D"nowrap">Datum:</th>
<td>2019-03-10 13:53</td>
</tr>
<tr>
<th align=3D"right" valign=3D"baseline" nowrap=3D"nowrap">Afzender:</th>
<td>internet-drafts@ietf.org</td>
</tr>
<tr>
<th align=3D"right" valign=3D"baseline" nowrap=3D"nowrap">Ontvanger:</th>
<td>"Michael Richardson" &lt;mcr+ietf@sandelman.ca&gt;, "Panos Kampanakis" =
&lt;pkampana@cisco.com&gt;, "Peter van der Stok" &lt;consultancy@vanderstok=
=2Eorg&gt;</td>
</tr>
</tbody>
</table>
<br /><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<div class=3D"pre" style=3D"margin: 0; padding: 0; font-family: monospace">=
<br /> A new version of I-D, draft-vanderstok-anima-constrained-join-proxy-=
01.txt<br /> has been successfully submitted by Peter van der Stok and post=
ed to the<br /> IETF repository.<br /><br /> Name: &nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;draft-vanderstok-anima-constrained-join-proxy<br /> Revis=
ion: &nbsp;&nbsp;&nbsp;01<br /> Title: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;Constrained Join Proxy for Bootstrapping Protocols<br /> Document dat=
e: &nbsp;&nbsp;&nbsp;2019-03-10<br /> Group: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;Individual Submission<br /> Pages: &nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;17<br /> URL: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;<a href=3D"https://www.ietf.org/internet-drafts/draft-va=
nderstok-anima-constrained-join-proxy-01.txt" target=3D"_blank" rel=3D"nore=
ferrer">https://www.ietf.org/internet-drafts/draft-vanderstok-anima-constra=
ined-join-proxy-01.txt</a><br /> Status: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;<a href=3D"https://datatracker.ietf.org/doc/draft-vanderstok-=
anima-constrained-join-proxy/" target=3D"_blank" rel=3D"noreferrer">https:/=
/datatracker.ietf.org/doc/draft-vanderstok-anima-constrained-join-proxy/</a=
><br /> Htmlized: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"https://to=
ols.ietf.org/html/draft-vanderstok-anima-constrained-join-proxy-01" target=
=3D"_blank" rel=3D"noreferrer">https://tools.ietf.org/html/draft-vanderstok=
-anima-constrained-join-proxy-01</a><br /> Htmlized: &nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;<a href=3D"https://datatracker.ietf.org/doc/html/draft-vander=
stok-anima-constrained-join-proxy" target=3D"_blank" rel=3D"noreferrer">htt=
ps://datatracker.ietf.org/doc/html/draft-vanderstok-anima-constrained-join-=
proxy</a><br /> Diff: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-vanderstok-anim=
a-constrained-join-proxy-01" target=3D"_blank" rel=3D"noreferrer">https://w=
ww.ietf.org/rfcdiff?url2=3Ddraft-vanderstok-anima-constrained-join-proxy-01=
</a><br /><br /> Abstract:<br /> &nbsp;&nbsp;&nbsp;This document defines a =
protocol to securely assign a pledge to an<br /> &nbsp;&nbsp;&nbsp;owner, u=
sing an intermediary node between pledge and owner. &nbsp;This<br /> &nbsp;=
&nbsp;&nbsp;intermediary node is known as a "constrained-join-proxy".<br />=
<br /> &nbsp;&nbsp;&nbsp;This document extends the work of [ietf-anima-boot=
strapping-keyinfra]<br /> &nbsp;&nbsp;&nbsp;by replacing the Circuit-proxy =
by a stateless constrained join-proxy,<br /> &nbsp;&nbsp;&nbsp;that transpo=
rts routing information.<br /><br /> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;<br /><br /><br /> Please note that it may take a couple of minutes fro=
m the time of submission<br /> until the htmlized version and diff are avai=
lable at tools.ietf.org.<br /><br /> The IETF Secretariat<br /><br /></div>
</body></html>

--=_30a27ca0ecde3f021b348484d02f7775--


From nobody Mon Mar 11 03:02:19 2019
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 512C4130DE6 for <anima@ietfa.amsl.com>; Mon, 11 Mar 2019 03:02:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 8qj-eIu4lxMO for <anima@ietfa.amsl.com>; Mon, 11 Mar 2019 03:02:14 -0700 (PDT)
Received: from gecko.sbs.de (gecko.sbs.de [194.138.37.40]) (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 458E51277E7 for <anima@ietf.org>; Mon, 11 Mar 2019 03:02:14 -0700 (PDT)
Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by gecko.sbs.de (8.15.2/8.15.2) with ESMTPS id x2BA2Abw020316 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <anima@ietf.org>; Mon, 11 Mar 2019 11:02:11 +0100
Received: from DEFTHW99ERMMSX.ww902.siemens.net (defthw99ermmsx.ww902.siemens.net [139.22.70.142]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTPS id x2BA2ACS029000 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <anima@ietf.org>; Mon, 11 Mar 2019 11:02:10 +0100
Received: from DENBGAT9ERPMSX.ww902.siemens.net (139.22.70.194) by DEFTHW99ERMMSX.ww902.siemens.net (139.22.70.142) with Microsoft SMTP Server (TLS) id 14.3.435.0; Mon, 11 Mar 2019 11:02:10 +0100
Received: from DENBGAT9EJ5MSX.ww902.siemens.net ([169.254.12.162]) by DENBGAT9ERPMSX.ww902.siemens.net ([139.22.70.194]) with mapi id 14.03.0435.000; Mon, 11 Mar 2019 11:02:09 +0100
From: "Fries, Steffen" <steffen.fries@siemens.com>
To: "anima@ietf.org" <anima@ietf.org>
Thread-Topic: New Version Notification for draft-fries-anima-brski-async-enroll-00.txt
Thread-Index: AQHU1/AYt0i/05EWqUG/gaEVHFZLQqYGMhlA
Date: Mon, 11 Mar 2019 10:02:08 +0000
Message-ID: <E6C9F0E527F94F4692731382340B33781540B186@DENBGAT9EJ5MSX.ww902.siemens.net>
References: <155229792091.16909.155158627247126928.idtracker@ietfa.amsl.com>
In-Reply-To: <155229792091.16909.155158627247126928.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [139.22.70.32]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/we6q6WSGY5lmX1ak8nTUobrPcBA>
Subject: [Anima] FW: New Version Notification for draft-fries-anima-brski-async-enroll-00.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Mar 2019 10:02:18 -0000

SGVsbG8sDQoNCkp1c3QgYXMgYW4gaW5mb3JtYXRpb24sIHdlIHN1Ym1pdHRlZCB0aGUgaW5pdGlh
bCBkcmFmdCBmb3IgZGlzY3Vzc2lvbiByZWdhcmRpbmcgdGhlIGFzeW5jaHJvbm91cyBlbnJvbGxt
ZW50LiBJdCBkaXNjdXNzZXMgYSBzb2x1dGlvbiBpbiB3aGljaCB0aGUgRG9tYWluIHJlZ2lzdHJh
ciBoYXMgbm8gbm9yIHRlbXBvcmFyeSBsaW1pdGVkIGNvbm5lY3Rpdml0eSB0byBhIGJhY2tlbmQg
Zm9yIGludGVyYWN0aW9uIHdpdGggYSBQS0kgKGFuZCBwb3RlbnRpYWxseSB0aGUgTUFTQSkuDQpJ
IGFza2VkIGZvciBhIHNsb3QgaW4gdGhlIGFnZW5kYSB0byBkaXNjdXNzIHRoZSBkcmFmdCBkdXJp
bmcgdGhlIG5leHQgSUVURiBtZWV0aW5nLg0KDQpCZXN0IHJlZ2FyZHMNClN0ZWZmZW4NCg0KDQot
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogaW50ZXJuZXQtZHJhZnRzQGlldGYub3Jn
IDxpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmc+IA0KU2VudDogTW9udGFnLCAxMS4gTcOkcnogMjAx
OSAxMDo1Mg0KVG86IEVsaW90IExlYXIgPGxlYXJAY2lzY28uY29tPjsgRnJpZXMsIFN0ZWZmZW4g
KENUIFJEQSBJVFMpIDxzdGVmZmVuLmZyaWVzQHNpZW1lbnMuY29tPjsgQnJvY2toYXVzLCBIZW5k
cmlrIChDVCBSREEgSVRTIFNFQS1ERSkgPGhlbmRyaWsuYnJvY2toYXVzQHNpZW1lbnMuY29tPg0K
U3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1mcmllcy1hbmltYS1i
cnNraS1hc3luYy1lbnJvbGwtMDAudHh0DQoNCg0KQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0
LWZyaWVzLWFuaW1hLWJyc2tpLWFzeW5jLWVucm9sbC0wMC50eHQNCmhhcyBiZWVuIHN1Y2Nlc3Nm
dWxseSBzdWJtaXR0ZWQgYnkgU3RlZmZlbiBGcmllcyBhbmQgcG9zdGVkIHRvIHRoZSBJRVRGIHJl
cG9zaXRvcnkuDQoNCk5hbWU6CQlkcmFmdC1mcmllcy1hbmltYS1icnNraS1hc3luYy1lbnJvbGwN
ClJldmlzaW9uOgkwMA0KVGl0bGU6CQlTdXBwb3J0IG9mIGFzeW5jaHJvbm91cyBFbnJvbGxtZW50
IGluIEJSU0tJDQpEb2N1bWVudCBkYXRlOgkyMDE5LTAzLTExDQpHcm91cDoJCUluZGl2aWR1YWwg
U3VibWlzc2lvbg0KUGFnZXM6CQkxOA0KVVJMOiAgICAgICAgICAgIGh0dHBzOi8vd3d3LmlldGYu
b3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1mcmllcy1hbmltYS1icnNraS1hc3luYy1lbnJvbGwt
MDAudHh0DQpTdGF0dXM6ICAgICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2Mv
ZHJhZnQtZnJpZXMtYW5pbWEtYnJza2ktYXN5bmMtZW5yb2xsLw0KSHRtbGl6ZWQ6ICAgICAgIGh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1mcmllcy1hbmltYS1icnNraS1hc3luYy1l
bnJvbGwtMDANCkh0bWxpemVkOiAgICAgICBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2Rv
Yy9odG1sL2RyYWZ0LWZyaWVzLWFuaW1hLWJyc2tpLWFzeW5jLWVucm9sbA0KDQoNCkFic3RyYWN0
Og0KICAgVGhpcyBkb2N1bWVudCBkaXNjdXNzZXMgdGhlIGVuaGFuY2VtZW50IG9mIGF1dG9tYXRl
ZCBib290c3RyYXBwaW5nIG9mDQogICBhIHJlbW90ZSBzZWN1cmUga2V5IGluZnJhc3RydWN0dXJl
IChCUlNLSSkgdG8gb3BlcmF0ZSBpbiBkb21haW5zDQogICBmZWF0dXJpbmcgbm8gb3Igb25seSB0
aW1lbHkgbGltaXRlZCBjb25uZWN0aXZpdHkgdG8gYmFja2VuZCBzZXJ2aWNlcw0KICAgb2ZmZXJp
bmcgZW5yb2xsbWVudCBmdW5jdGlvbmFsaXR5IGxpa2UgYSBQdWJsaWMgS2V5IEluZnJhc3RydWN0
dXJlDQogICAoUEtJKS4gIEluIHRoZSBjb250ZXh0IG9mIGRlcGxveWluZyBuZXcgZGV2aWNlcyB0
aGUgZGVzaWduIG9mIEJSU0tJDQogICBhbGxvd3MgZm9yIG9ubGluZSAoc3luY2hyb25vdXMgb2Jq
ZWN0IGV4Y2hhbmdlKSBhbmQgb2ZmbGluZQ0KICAgaW50ZXJhY3Rpb25zIChhc3luY2hyb25vdXMg
b2JqZWN0IGV4Y2hhbmdlKSB3aXRoIGEgbWFudWZhY3R1cmVyJ3MNCiAgIGF1dGhvcml6YXRpb24g
c2VydmljZS4gIEl0IHV0aWxpemVzIGEgc2VsZi1jb250YWluZWQgdm91Y2hlciB0bw0KICAgdHJh
bnNwb3J0IHRoZSBkb21haW4gY3JlZGVudGlhbHMgYXMgYSBzaWduZWQgb2JqZWN0IHRvIGVzdGFi
bGlzaCBhbg0KICAgaW5pdGlhbCB0cnVzdCBiZXR3ZWVuIHRoZSBwbGVkZ2UgYW5kIHRoZSBkZXBs
b3ltZW50IGRvbWFpbi4gIFRoZQ0KICAgY3VycmVudGx5IHN1cHBvcnRlZCBlbnJvbGxtZW50IHBy
b3RvY29sIGZvciByZXF1ZXN0IGFuZCBkaXN0cmlidXRpb24NCiAgIG9mIGRlcGxveW1lbnQgZG9t
YWluIHNwZWNpZmljIGRldmljZSBjZXJ0aWZpY2F0ZXMgcHJvdmlkZXMgb25seQ0KICAgbGltaXRl
ZCBzdXBwb3J0IGZvciBhc3luY2hyb25vdXMgUEtJIGludGVyYWN0aW9ucy4gIFRoaXMgbWVtbw0K
ICAgbW90aXZhdGVzIHN1cHBvcnQgb2Ygc2VsZi1jb250YWluZWQgb2JqZWN0cyBhbHNvIGZvciBj
ZXJ0aWZpY2F0ZQ0KICAgbWFuYWdlbWVudCBieSB1c2luZyBhbiBhYnN0cmFjdCBub3RhdGlvbiB0
byBhbGxvdyBvZmYtc2l0ZSBvcGVyYXRpb24NCiAgIG9mIFBLSSBzZXJ2aWNlcywgd2l0aCBvbmx5
IGxpbWl0ZWQgY29ubmVjdGl2aXR5IHRvIHRoZSBwbGVkZ2UNCiAgIGRlcGxveW1lbnQgZG9tYWlu
LiAgVGhpcyBhZGRyZXNzZXMgc3BlY2lmaWNhbGx5IHNjZW5hcmlvcywgaW4gd2hpY2gNCiAgIHRo
ZSBkZXBsb3ltZW50IGRvbWFpbiBvZiBhIHBsZWRnZSBkb2VzIG5vdCBwZXJmb3JtIHRoZSBmaW5h
bA0KICAgYXV0aG9yaXphdGlvbiBvZiBhIGNlcnRpZmljYXRpb24gcmVxdWVzdCBhbmQgcmF0aGVy
IGRlbGVnYXRlcyB0aGlzDQogICBkZWNpc2lvbiB0byBhbiBvcGVyYXRvciBiYWNrZW5kLiAgVGhl
IGdvYWwgaXMgdG8gZW5hYmxlIHRoZSB1c2FnZSBvZg0KICAgZXhpc3RpbmcgYW5kIHBvdGVudGlh
bGx5IG5ldyBQS0kgcHJvdG9jb2xzIHN1cHBvcnRpbmcgc2VsZi0NCiAgIGNvbnRhaW5tZW50IGZv
ciBjZXJ0aWZpY2F0ZSBtYW5hZ2VtZW50Lg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgDQoN
Cg0KUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBtaW51dGVzIGZyb20g
dGhlIHRpbWUgb2Ygc3VibWlzc2lvbiB1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlm
ZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KDQpUaGUgSUVURiBTZWNyZXRhcmlh
dA0KDQo=


From nobody Mon Mar 11 03:04:04 2019
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 014A4130F3C; Mon, 11 Mar 2019 03:04:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 g_qbQaP6Hufh; Mon, 11 Mar 2019 03:03:59 -0700 (PDT)
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 7976F130F34; Mon, 11 Mar 2019 03:03:59 -0700 (PDT)
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 x2BA3rIk026457 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 11 Mar 2019 11:03:53 +0100
Received: from DEFTHW99ERGMSX.ww902.siemens.net (defthw99ergmsx.ww902.siemens.net [139.22.70.132]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTPS id x2BA3dl4008800 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 11 Mar 2019 11:03:52 +0100
Received: from DENBGAT9EJ5MSX.ww902.siemens.net ([169.254.12.162]) by DEFTHW99ERGMSX.ww902.siemens.net ([139.22.70.132]) with mapi id 14.03.0435.000; Mon, 11 Mar 2019 11:03:46 +0100
From: "Fries, Steffen" <steffen.fries@siemens.com>
To: "anima@ietf.org" <anima@ietf.org>, "jiangsheng@huawei.com" <jiangsheng@huawei.com>
CC: "anima-chairs@ietf.org" <anima-chairs@ietf.org>
Thread-Topic: [Anima] Call for agenda ANIMA @ IETF 104, Prague
Thread-Index: AdTWepPKrSuPNpwNSsuu05XBytkXQQBdvSsQ
Date: Mon, 11 Mar 2019 10:03:46 +0000
Message-ID: <E6C9F0E527F94F4692731382340B33781540B1AB@DENBGAT9EJ5MSX.ww902.siemens.net>
References: <2130DDAA-D413-47A8-8661-803EB80A553C@siemens.com>
In-Reply-To: <2130DDAA-D413-47A8-8661-803EB80A553C@siemens.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [139.22.70.32]
Content-Type: multipart/alternative; boundary="_000_E6C9F0E527F94F4692731382340B33781540B1ABDENBGAT9EJ5MSXw_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/Fe4yt8JJyXtQHXshd5oBycFkKbo>
Subject: Re: [Anima] Call for agenda ANIMA @ IETF 104, Prague
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Mar 2019 10:04:02 -0000

--_000_E6C9F0E527F94F4692731382340B33781540B1ABDENBGAT9EJ5MSXw_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgU2hlbmcsIGhpIFRvZXJsZXNzLA0KDQpCYXNlZCBvbiB0aGUgc3VibWl0dGVkIGRyYWZ0LCBo
ZXJlIGEgc21hbGwgdXBkYXRlIGZvciB0aGUgYWdlbmRhIHJlcXVlc3QgKG5hbWUgZW5oYW5jZW1l
bnQgb2YgdGhlIGRyYWZ0KToNCg0KTmFtZSBvZiB0aW1lIHNsb3Q6IFN1cHBvcnQgb2YgYXN5bmNo
cm9ub3VzIGVucm9sbG1lbnQgaW4gQlJTS0kNCk5hbWUgb2YgZHJhZnQocyk6IGRyYWZ0LWZyaWVz
LWFuaW1hLWJyc2tpLWFzeW5jLWVucm9sbC0wMA0KVGltZSByZXF1ZXN0ZWQ6IDEwIG1pbg0KUHJl
c2VudGVyIG5hbWUocyk6IFN0ZWZmZW4gRnJpZXMNCg0KQmVzdCByZWdhcmRzDQpTdGVmZmVuDQoN
CkZyb206IEFuaW1hIDxhbmltYS1ib3VuY2VzQGlldGYub3JnPiBPbiBCZWhhbGYgT2YgW2V4dF0g
RnJpZXMsIFN0ZWZmZW4NClNlbnQ6IFNhbXN0YWcsIDkuIE3DpHJ6IDIwMTkgMTQ6MTgNClRvOiBh
bmltYUBpZXRmLm9yZzsgamlhbmdzaGVuZ0BodWF3ZWkuY29tDQpDYzogYW5pbWEtY2hhaXJzQGll
dGYub3JnDQpTdWJqZWN0OiBSZTogW0FuaW1hXSBDYWxsIGZvciBhZ2VuZGEgQU5JTUEgQCBJRVRG
IDEwNCwgUHJhZ3VlDQoNCkhpIFNoZW5nLCBoaSBUb2VybGVzcw0KDQpBcyBhc2tlZCBlYXJsaWVy
LCB3ZSB3b3VsZCBsaWtlIHRvIGhhdmUgYSB0aW1lIHNsb3QgdG8gZGlzY3VzcyB0aGUgYXN5bmNo
cm9ub3VzIGVucm9sbG1lbnQgc3VwcG9ydCBpbiBCUlNLSS4gSSB3aWxsIHN1Ym1pdCB0aGUgY29y
cmVzcG9uZGluZyBkcmFmdCBNb25kYXkgbGF0ZXN0Lg0KDQoNCk5hbWUgb2YgdGltZSBzbG90OiBT
dXBwb3J0IG9mIGFzeW5jaHJvbm91cyBlbnJvbGxtZW50IGluIEJSU0tJDQoNCk5hbWUgb2YgZHJh
ZnQocyk6IGRyYWZ0LWZyaWVzLWJyc2tpLWFzeW5jLWVucm9sbC0wMA0KDQpUaW1lIHJlcXVlc3Rl
ZDogMTAgbWluDQoNClByZXNlbnRlciBuYW1lKHMpOiBTdGVmZmVuIEZyaWVzDQoNClRoYW5rIHlv
dSBhbmQgYmVzdCByZWdhcmRzDQpTdGVmZmVuDQoNCg0KRnJvbTogU2hlbmcgSmlhbmcgPGppYW5n
c2hlbmdAaHVhd2VpLmNvbTxtYWlsdG86amlhbmdzaGVuZ0BodWF3ZWkuY29tPj4NCg0KU3ViamVj
dDogW0FuaW1hXSBDYWxsIGZvciBhZ2VuZGEgQU5JTUEgQCBJRVRGIDEwNO+8jCBQcmFndWUNCg0K
RGF0ZTogOCBNYXJjaCAyMDE5IGF0IDA3OjU5OjE2IENFVA0KDQpUbzogImFuaW1hQGlldGYub3Jn
PG1haWx0bzphbmltYUBpZXRmLm9yZz4iIDxhbmltYUBpZXRmLm9yZzxtYWlsdG86YW5pbWFAaWV0
Zi5vcmc+Pg0KDQpDYzogImFuaW1hLWNoYWlyc0BpZXRmLm9yZzxtYWlsdG86YW5pbWEtY2hhaXJz
QGlldGYub3JnPiIgPGFuaW1hLWNoYWlyc0BpZXRmLm9yZzxtYWlsdG86YW5pbWEtY2hhaXJzQGll
dGYub3JnPj4NCg0KDQoNCg0KSGksIGFsbCBhbmltYSwNCg0KDQoNCldlIGhhdmUgYmVlbiBhbGxv
Y2F0ZWQgYSBzZXNzaW9uIG9mIDItaG91ciBmb3IgdGhlIEFOSU1BIFdHIG1lZXRpbmcgZm9yIElF
VEYtMTA0IChQcmFndWUpIC0gVHVlc2RheSBhZnRlcm5vb24gc2Vzc2lvbiBJLiBXZSBhcmUgbm93
IHN0YXJ0aW5nIHRvIGNvbGxlY3QgYWdlbmRhIGl0ZW1zIGZvciB0aGUgc2Vzc2lvbi4gUGxlYXNl
IHNlbmQgeW91ciByZXF1ZXN0IGZvciBhZ2VuZGEgYnkgTWFyY2ggMTR0aCwgVGh1cnNkYXkuDQoN
Cg0KDQpGb3IgdGhpcyBjb21pbmcgbWVldGluZywgd2Ugd291bGQgbGlrZSB0byBkaXNjdXNzIHBv
dGVudGlhbCBmdXR1cmUgQU5JTUEgd29ya3MuIEFzIG5vcm1hbCwgdGhlIHByaW9yaXR5IGFtb25n
IHRoZXNlIG5vbi1jaGFydGVyIHdvcmsgaXRlbXMgd291bGQgYmU6IHRoZXNlIHRoYXQgaGF2ZSBh
Y3RpdmUgZGlzY3Vzc2lvbiBpbiBtYWlsIGxpc3QsIHRoZW4gdGhlc2UgaGF2ZSBzdWJtaXR0ZWQg
ZHJhZnRzLCBhbmQgdG9waWNzIHdpdGhvdXQgZHJhZnRzLg0KDQoNCg0KUGxlYXNlIHNlbmQgdXMg
KGFuaW1hLWNoYWlycyBhdCBpZXRmLm9yZzxodHRwczovL2lldGYub3JnLz4pIHJlcXVlc3RzIGZv
ciB0aW1lIHNsb3QgYnkgTWFyY2ggMTR0aCwgVGh1cnNkYXkgYW5kIGluY2x1ZGU6DQoNCg0KDQpO
YW1lIG9mIHRpbWUgc2xvdDoNCg0KTmFtZSBvZiBkcmFmdChzKToNCg0KVGltZSByZXF1ZXN0ZWQ6
DQoNClByZXNlbnRlciBuYW1lKHMpOg0KDQoNCg0KTW9yZSBkZXRhaWxzIGFib3V0IHRoZSBJRVRG
IDEwNCwgUHJhZ3VlIGNhbiBiZSBmb3VuZCBhdDoNCg0KDQoNCmh0dHBzOi8vd3d3LmlldGYub3Jn
L2hvdy9tZWV0aW5ncy8xMDQvDQoNCg0KDQpBZ2FpbiwgcHJlc2VudGVycyBhbmQgZHJhZnQgYXV0
aG9ycyBwbGVhc2UgaW52b2tlIGFjdGl2ZSBkaXNjdXNzaW9ucyBpbiB0aGUgQU5JTUEgbGlzdC4g
TWFpbCBsaXN0IGlzIGEgdmVyeSBnb29kIHBsYWNlIHRvIGRpc2N1c3MgYW5kIHJlYWNoIGNvbnNl
bnN1cyBvbiB0ZWNobmljYWwgaXNzdWVzLg0KDQoNCg0KQmVzdCByZWdhcmRzLA0KDQoNCg0KVG9l
cmxlc3MgJiBTaGVuZw0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCkFuaW1hIG1haWxpbmcgbGlzdA0KQW5pbWFAaWV0Zi5vcmc8bWFpbHRvOkFuaW1hQGll
dGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9hbmltYQ0KDQoN
Cg==

--_000_E6C9F0E527F94F4692731382340B33781540B1ABDENBGAT9EJ5MSXw_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6Ik1TIEdvdGhpYyI7DQoJcGFub3NlLTE6MiAxMSA2IDkgNyAyIDUgOCAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2Ut
MToyIDQgNSAzIDUgNCA2IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJy
aTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQt
ZmFtaWx5OkNvbnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIgMiA0IDMgMiA0O30NCkBmb250
LWZhY2UNCgl7Zm9udC1mYW1pbHk6IlxATVMgR290aGljIjsNCglwYW5vc2UtMToyIDExIDYgOSA3
IDIgNSA4IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlVJQ1RGb250VGV4dFN0eWxl
VGFsbEJvZHk7DQoJcGFub3NlLTE6MCAwIDAgMCAwIDAgMCAwIDAgMDt9DQovKiBTdHlsZSBEZWZp
bml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXtt
YXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBl
cmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNv
cmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQN
Cgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRp
b246dW5kZXJsaW5lO30NCnByZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxl
LWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1hcmdpbjowY207DQoJbWFyZ2luLWJv
dHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIg
TmV3Ijt9DQpwLm1zb25vcm1hbDAsIGxpLm1zb25vcm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21z
by1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJn
aW4tcmlnaHQ6MGNtOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0
OjBjbTsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNl
cmlmO30NCnNwYW4uSFRNTFByZWZvcm1hdHRlZENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IkhUTUwg
UHJlZm9ybWF0dGVkIENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUt
bGluazoiSFRNTCBQcmVmb3JtYXR0ZWQiOw0KCWZvbnQtZmFtaWx5OkNvbnNvbGFzO30NCnNwYW4u
RW1haWxTdHlsZTIxDQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFt
aWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7DQoJZm9udC13ZWlnaHQ6
bm9ybWFsOw0KCWZvbnQtc3R5bGU6bm9ybWFsOw0KCXRleHQtZGVjb3JhdGlvbjpub25lIG5vbmU7
fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1z
aXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7
DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24x
DQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4
bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94
bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2
OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFw
ZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkRFIiBsaW5r
PSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5IaSBTaGVuZywgaGkgVG9lcmxlc3MsIDxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjojMUY0
OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9y
OiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkJhc2VkIG9uIHRoZSBzdWJtaXR0
ZWQgZHJhZnQsIGhlcmUgYSBzbWFsbCB1cGRhdGUgZm9yIHRoZSBhZ2VuZGEgcmVxdWVzdCAobmFt
ZSBlbmhhbmNlbWVudCBvZiB0aGUgZHJhZnQpOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6IzFGNDk3RDtt
c28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjojMUY0
OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5OYW1lIG9mIHRpbWUgc2xvdDogU3VwcG9y
dCBvZiBhc3luY2hyb25vdXMgZW5yb2xsbWVudCBpbiBCUlNLSQ0KPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xv
cjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5OYW1lIG9mIGRyYWZ0KHMpOiBk
cmFmdC1mcmllcy1hbmltYS1icnNraS1hc3luYy1lbnJvbGwtMDA8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9y
OiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPlRpbWUgcmVxdWVzdGVkOiAxMCBt
aW48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9ImNvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMi
PlByZXNlbnRlciBuYW1lKHMpOiBTdGVmZmVuIEZyaWVzPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjojMUY0
OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9y
OiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkJlc3QgcmVnYXJkczxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iY29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+U3RlZmZlbjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJs
dWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0i
Ym9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQg
MGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFuZz0iRU4tVVMi
PkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyI+IEFuaW1hICZsdDthbmltYS1ib3Vu
Y2VzQGlldGYub3JnJmd0Ow0KPGI+T24gQmVoYWxmIE9mIDwvYj5bZXh0XSBGcmllcywgU3RlZmZl
bjxicj4NCjxiPlNlbnQ6PC9iPiBTYW1zdGFnLCA5LiBNw6RyeiAyMDE5IDE0OjE4PGJyPg0KPGI+
VG86PC9iPiBhbmltYUBpZXRmLm9yZzsgamlhbmdzaGVuZ0BodWF3ZWkuY29tPGJyPg0KPGI+Q2M6
PC9iPiBhbmltYS1jaGFpcnNAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFtBbmlt
YV0gQ2FsbCBmb3IgYWdlbmRhIEFOSU1BIEAgSUVURiAxMDQsIFByYWd1ZTxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IaSBTaGVuZywgaGkgVG9l
cmxlc3M8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+QXMgYXNrZWQgZWFybGllciwgd2Ugd291bGQgbGlrZSB0byBoYXZlIGEgdGltZSBzbG90IHRv
IGRpc2N1c3MgdGhlIGFzeW5jaHJvbm91cyBlbnJvbGxtZW50IHN1cHBvcnQgaW4gQlJTS0kuIEkg
d2lsbCBzdWJtaXQgdGhlIGNvcnJlc3BvbmRpbmcgZHJhZnQgTW9uZGF5IGxhdGVzdC48bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgc3R5bGU9Im1hcmdpbjowY207bWFyZ2luLWJv
dHRvbTouMDAwMXB0O2ZvbnQtc3RyZXRjaDogbm9ybWFsIj5OYW1lIG9mIHRpbWUgc2xvdDogU3Vw
cG9ydCBvZiBhc3luY2hyb25vdXMgZW5yb2xsbWVudCBpbiBCUlNLSSZuYnNwOzxvOnA+PC9vOnA+
PC9wPg0KPHAgc3R5bGU9Im1hcmdpbjowY207bWFyZ2luLWJvdHRvbTouMDAwMXB0O2ZvbnQtc3Ry
ZXRjaDogbm9ybWFsIj5OYW1lIG9mIGRyYWZ0KHMpOiZuYnNwOzxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmIj5k
cmFmdC1mcmllcy1icnNraS1hc3luYy1lbnJvbGwtMDA8L3NwYW4+PG86cD48L286cD48L3A+DQo8
cCBzdHlsZT0ibWFyZ2luOjBjbTttYXJnaW4tYm90dG9tOi4wMDAxcHQ7Zm9udC1zdHJldGNoOiBu
b3JtYWwiPlRpbWUgcmVxdWVzdGVkOiAxMCBtaW48bzpwPjwvbzpwPjwvcD4NCjxwIHN0eWxlPSJt
YXJnaW46MGNtO21hcmdpbi1ib3R0b206LjAwMDFwdDtmb250LXN0cmV0Y2g6IG5vcm1hbCI+UHJl
c2VudGVyIG5hbWUocyk6IFN0ZWZmZW4gRnJpZXM8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhhbmsgeW91IGFuZCBiZXN0IHJlZ2FyZHM8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlN0ZWZmZW48
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGJyPg0KPGJyPg0K
PG86cD48L286cD48L3A+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJn
aW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1
LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
Yj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPkZyb206Jm5ic3A7PC9zcGFuPjwvYj48c3BhbiBz
dHlsZT0iY29sb3I6YmxhY2siPlNoZW5nIEppYW5nICZsdDs8YSBocmVmPSJtYWlsdG86amlhbmdz
aGVuZ0BodWF3ZWkuY29tIj5qaWFuZ3NoZW5nQGh1YXdlaS5jb208L2E+Jmd0Ozxicj4NCjxicj4N
Cjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxiPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+U3ViamVjdDombmJzcDtbQW5pbWFdIENh
bGwgZm9yIGFnZW5kYSBBTklNQSBAIElFVEYgMTA0PC9zcGFuPjwvYj48Yj48c3BhbiBzdHlsZT0i
Zm9udC1mYW1pbHk6JnF1b3Q7TVMgR290aGljJnF1b3Q7O2NvbG9yOmJsYWNrIj7vvIw8L3NwYW4+
PC9iPjxiPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+IFByYWd1ZTwvc3Bhbj48L2I+PHNwYW4g
c3R5bGU9ImNvbG9yOmJsYWNrIj48YnI+DQo8YnI+DQo8L3NwYW4+PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iY29sb3I6
YmxhY2siPkRhdGU6Jm5ic3A7PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPjgg
TWFyY2ggMjAxOSBhdCAwNzo1OToxNiBDRVQ8YnI+DQo8YnI+DQo8L3NwYW4+PG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0i
Y29sb3I6YmxhY2siPlRvOiZuYnNwOzwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNr
Ij4mcXVvdDs8YSBocmVmPSJtYWlsdG86YW5pbWFAaWV0Zi5vcmciPmFuaW1hQGlldGYub3JnPC9h
PiZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFuaW1hQGlldGYub3JnIj5hbmltYUBpZXRmLm9y
ZzwvYT4mZ3Q7PGJyPg0KPGJyPg0KPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj5DYzom
bmJzcDs8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+JnF1b3Q7PGEgaHJlZj0i
bWFpbHRvOmFuaW1hLWNoYWlyc0BpZXRmLm9yZyI+YW5pbWEtY2hhaXJzQGlldGYub3JnPC9hPiZx
dW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFuaW1hLWNoYWlyc0BpZXRmLm9yZyI+YW5pbWEtY2hh
aXJzQGlldGYub3JnPC9hPiZndDs8YnI+DQo8YnI+DQo8L3NwYW4+PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PGJy
Pg0KPGJyPg0KPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwcmU+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtVSUNURm9udFRleHRTdHlsZVRhbGxCb2R5
JnF1b3Q7LHNlcmlmO2NvbG9yOmJsYWNrIj5IaSwgYWxsIGFuaW1hLDwvc3Bhbj48bzpwPjwvbzpw
PjwvcHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90
O1VJQ1RGb250VGV4dFN0eWxlVGFsbEJvZHkmcXVvdDssc2VyaWY7Y29sb3I6YmxhY2siPiZuYnNw
Ozwvc3Bhbj48bzpwPjwvbzpwPjwvcHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O1VJQ1RGb250VGV4dFN0eWxlVGFsbEJvZHkmcXVvdDssc2VyaWY7
Y29sb3I6YmxhY2siPldlIGhhdmUgYmVlbiBhbGxvY2F0ZWQgYSBzZXNzaW9uIG9mIDItaG91ciBm
b3IgdGhlIEFOSU1BIFdHIG1lZXRpbmcgZm9yIElFVEYtMTA0IChQcmFndWUpIC0gVHVlc2RheSBh
ZnRlcm5vb24gc2Vzc2lvbiBJLiBXZSBhcmUgbm93IHN0YXJ0aW5nIHRvIGNvbGxlY3QgYWdlbmRh
IGl0ZW1zIGZvciB0aGUgc2Vzc2lvbi4gUGxlYXNlIHNlbmQgeW91ciByZXF1ZXN0IGZvciBhZ2Vu
ZGEgYnkgTWFyY2ggMTR0aCwgVGh1cnNkYXkuPC9zcGFuPjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJl
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VUlDVEZvbnRUZXh0
U3R5bGVUYWxsQm9keSZxdW90OyxzZXJpZjtjb2xvcjpibGFjayI+Jm5ic3A7PC9zcGFuPjxvOnA+
PC9vOnA+PC9wcmU+DQo8cHJlPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6
JnF1b3Q7VUlDVEZvbnRUZXh0U3R5bGVUYWxsQm9keSZxdW90OyxzZXJpZjtjb2xvcjpibGFjayI+
Rm9yIHRoaXMgY29taW5nIG1lZXRpbmcsIHdlIHdvdWxkIGxpa2UgdG8gZGlzY3VzcyBwb3RlbnRp
YWwgZnV0dXJlIEFOSU1BIHdvcmtzLiBBcyBub3JtYWwsIHRoZSBwcmlvcml0eSBhbW9uZyB0aGVz
ZSBub24tY2hhcnRlciB3b3JrIGl0ZW1zIHdvdWxkIGJlOiB0aGVzZSB0aGF0IGhhdmUgYWN0aXZl
IGRpc2N1c3Npb24gaW4gbWFpbCBsaXN0LCB0aGVuIHRoZXNlIGhhdmUgc3VibWl0dGVkIGRyYWZ0
cywgYW5kIHRvcGljcyB3aXRob3V0IGRyYWZ0cy48L3NwYW4+PG86cD48L286cD48L3ByZT4NCjxw
cmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtVSUNURm9udFRl
eHRTdHlsZVRhbGxCb2R5JnF1b3Q7LHNlcmlmO2NvbG9yOmJsYWNrIj4mbmJzcDs8L3NwYW4+PG86
cD48L286cD48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWls
eTomcXVvdDtVSUNURm9udFRleHRTdHlsZVRhbGxCb2R5JnF1b3Q7LHNlcmlmO2NvbG9yOmJsYWNr
Ij5QbGVhc2Ugc2VuZCB1cyAoYW5pbWEtY2hhaXJzIGF0IDxhIGhyZWY9Imh0dHBzOi8vaWV0Zi5v
cmcvIj5pZXRmLm9yZzwvYT4pIHJlcXVlc3RzIGZvciB0aW1lIHNsb3QgYnkgTWFyY2ggMTR0aCwg
VGh1cnNkYXkgYW5kIGluY2x1ZGU6PC9zcGFuPjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VUlDVEZvbnRUZXh0U3R5bGVU
YWxsQm9keSZxdW90OyxzZXJpZjtjb2xvcjpibGFjayI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+
PC9wcmU+DQo8cHJlPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7
VUlDVEZvbnRUZXh0U3R5bGVUYWxsQm9keSZxdW90OyxzZXJpZjtjb2xvcjpibGFjayI+TmFtZSBv
ZiB0aW1lIHNsb3Q6PC9zcGFuPjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VUlDVEZvbnRUZXh0U3R5bGVUYWxsQm9keSZx
dW90OyxzZXJpZjtjb2xvcjpibGFjayI+TmFtZSBvZiBkcmFmdChzKTo8L3NwYW4+PG86cD48L286
cD48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVv
dDtVSUNURm9udFRleHRTdHlsZVRhbGxCb2R5JnF1b3Q7LHNlcmlmO2NvbG9yOmJsYWNrIj5UaW1l
IHJlcXVlc3RlZDo8L3NwYW4+PG86cD48L286cD48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtVSUNURm9udFRleHRTdHlsZVRhbGxCb2R5JnF1
b3Q7LHNlcmlmO2NvbG9yOmJsYWNrIj5QcmVzZW50ZXIgbmFtZShzKTo8L3NwYW4+PG86cD48L286
cD48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVv
dDtVSUNURm9udFRleHRTdHlsZVRhbGxCb2R5JnF1b3Q7LHNlcmlmO2NvbG9yOmJsYWNrIj4mbmJz
cDs8L3NwYW4+PG86cD48L286cD48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxl
PSJmb250LWZhbWlseTomcXVvdDtVSUNURm9udFRleHRTdHlsZVRhbGxCb2R5JnF1b3Q7LHNlcmlm
O2NvbG9yOmJsYWNrIj5Nb3JlIGRldGFpbHMgYWJvdXQgdGhlIElFVEYgMTA0LCBQcmFndWUgY2Fu
IGJlIGZvdW5kIGF0Ojwvc3Bhbj48bzpwPjwvbzpwPjwvcHJlPg0KPHByZT48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1VJQ1RGb250VGV4dFN0eWxlVGFsbEJvZHkm
cXVvdDssc2VyaWY7Y29sb3I6YmxhY2siPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcHJlPg0K
PHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1VJQ1RGb250
VGV4dFN0eWxlVGFsbEJvZHkmcXVvdDssc2VyaWY7Y29sb3I6YmxhY2siPjxhIGhyZWY9Imh0dHBz
Oi8vd3d3LmlldGYub3JnL2hvdy9tZWV0aW5ncy8xMDQvIj5odHRwczovL3d3dy5pZXRmLm9yZy9o
b3cvbWVldGluZ3MvMTA0LzwvYT48L3NwYW4+PG86cD48L286cD48L3ByZT4NCjxwcmU+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtVSUNURm9udFRleHRTdHlsZVRh
bGxCb2R5JnF1b3Q7LHNlcmlmO2NvbG9yOmJsYWNrIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48
L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtV
SUNURm9udFRleHRTdHlsZVRhbGxCb2R5JnF1b3Q7LHNlcmlmO2NvbG9yOmJsYWNrIj5BZ2Fpbiwg
cHJlc2VudGVycyBhbmQgZHJhZnQgYXV0aG9ycyBwbGVhc2UgaW52b2tlIGFjdGl2ZSBkaXNjdXNz
aW9ucyBpbiB0aGUgQU5JTUEgbGlzdC4gTWFpbCBsaXN0IGlzIGEgdmVyeSBnb29kIHBsYWNlIHRv
IGRpc2N1c3MgYW5kIHJlYWNoIGNvbnNlbnN1cyBvbiB0ZWNobmljYWwgaXNzdWVzLjwvc3Bhbj48
bzpwPjwvbzpwPjwvcHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFt
aWx5OiZxdW90O1VJQ1RGb250VGV4dFN0eWxlVGFsbEJvZHkmcXVvdDssc2VyaWY7Y29sb3I6Ymxh
Y2siPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1VJQ1RGb250VGV4dFN0eWxlVGFsbEJvZHkmcXVv
dDssc2VyaWY7Y29sb3I6YmxhY2siPkJlc3QgcmVnYXJkcyw8L3NwYW4+PG86cD48L286cD48L3By
ZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtVSUNU
Rm9udFRleHRTdHlsZVRhbGxCb2R5JnF1b3Q7LHNlcmlmO2NvbG9yOmJsYWNrIj4mbmJzcDs8L3Nw
YW4+PG86cD48L286cD48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtVSUNURm9udFRleHRTdHlsZVRhbGxCb2R5JnF1b3Q7LHNlcmlmO2NvbG9y
OmJsYWNrIj5Ub2VybGVzcyAmYW1wOyBTaGVuZzwvc3Bhbj48bzpwPjwvbzpwPjwvcHJlPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj5fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCkFuaW1hIG1haWxpbmcgbGlz
dDxicj4NCjxhIGhyZWY9Im1haWx0bzpBbmltYUBpZXRmLm9yZyI+QW5pbWFAaWV0Zi5vcmc8L2E+
PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9hbmlt
YSI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9hbmltYTwvYT48L3NwYW4+
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9ibG9ja3F1
b3RlPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_E6C9F0E527F94F4692731382340B33781540B1ABDENBGAT9EJ5MSXw_--


From nobody Mon Mar 11 04:30:40 2019
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 F38EC130FCB; Mon, 11 Mar 2019 04:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 6wQcj6PCVbdW; Mon, 11 Mar 2019 04:30:36 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 105621200D8; Mon, 11 Mar 2019 04:30:36 -0700 (PDT)
Received: from LHREML714-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id C2D0129AA9F8602E64F7; Mon, 11 Mar 2019 11:30:33 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 11 Mar 2019 11:30:33 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0415.000; Mon, 11 Mar 2019 19:30:25 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "Fries, Steffen" <steffen.fries@siemens.com>, "anima@ietf.org" <anima@ietf.org>
CC: "anima-chairs@ietf.org" <anima-chairs@ietf.org>
Thread-Topic: [Anima] Call for agenda ANIMA @ IETF 104, Prague
Thread-Index: AdTWepPKrSuPNpwNSsuu05XBytkXQQBdvSsQAAMFYAA=
Date: Mon, 11 Mar 2019 11:30:25 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B929037F986@NKGEML515-MBX.china.huawei.com>
References: <2130DDAA-D413-47A8-8661-803EB80A553C@siemens.com> <E6C9F0E527F94F4692731382340B33781540B1AB@DENBGAT9EJ5MSX.ww902.siemens.net>
In-Reply-To: <E6C9F0E527F94F4692731382340B33781540B1AB@DENBGAT9EJ5MSX.ww902.siemens.net>
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_5D36713D8A4E7348A7E10DF7437A4B929037F986NKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/DTKZewl9TBOZtsyke3VDmszI9Go>
Subject: Re: [Anima] Call for agenda ANIMA @ IETF 104, Prague
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Mar 2019 11:30:39 -0000

--_000_5D36713D8A4E7348A7E10DF7437A4B929037F986NKGEML515MBXchi_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGksIFN0ZWZmZW4sDQoNCkkgY2FuIGNvbmZpcm0geW91ciByZXF1ZXN0LiBUaGUgY2hhaXJzIHdv
dWxkIGFsbG9jYXRlIHRpbWUgYWNjb3JkaW5nIHRvIHRoZSBhcHBsaWNhdGlvbiBzaXR1YXRpb24g
YW5kIHByaW9yaXR5IHBvbGljeS4NCg0KUmVnYXJkcywNCg0KU2hlbmcNCg0KRnJvbTogRnJpZXMs
IFN0ZWZmZW4gW21haWx0bzpzdGVmZmVuLmZyaWVzQHNpZW1lbnMuY29tXQ0KU2VudDogTW9uZGF5
LCBNYXJjaCAxMSwgMjAxOSA2OjA0IFBNDQpUbzogYW5pbWFAaWV0Zi5vcmc7IFNoZW5nIEppYW5n
IDxqaWFuZ3NoZW5nQGh1YXdlaS5jb20+DQpDYzogYW5pbWEtY2hhaXJzQGlldGYub3JnDQpTdWJq
ZWN0OiBSRTogW0FuaW1hXSBDYWxsIGZvciBhZ2VuZGEgQU5JTUEgQCBJRVRGIDEwNCwgUHJhZ3Vl
DQoNCkhpIFNoZW5nLCBoaSBUb2VybGVzcywNCg0KQmFzZWQgb24gdGhlIHN1Ym1pdHRlZCBkcmFm
dCwgaGVyZSBhIHNtYWxsIHVwZGF0ZSBmb3IgdGhlIGFnZW5kYSByZXF1ZXN0IChuYW1lIGVuaGFu
Y2VtZW50IG9mIHRoZSBkcmFmdCk6DQoNCk5hbWUgb2YgdGltZSBzbG90OiBTdXBwb3J0IG9mIGFz
eW5jaHJvbm91cyBlbnJvbGxtZW50IGluIEJSU0tJDQpOYW1lIG9mIGRyYWZ0KHMpOiBkcmFmdC1m
cmllcy1hbmltYS1icnNraS1hc3luYy1lbnJvbGwtMDANClRpbWUgcmVxdWVzdGVkOiAxMCBtaW4N
ClByZXNlbnRlciBuYW1lKHMpOiBTdGVmZmVuIEZyaWVzDQoNCkJlc3QgcmVnYXJkcw0KU3RlZmZl
bg0KDQpGcm9tOiBBbmltYSA8YW5pbWEtYm91bmNlc0BpZXRmLm9yZzxtYWlsdG86YW5pbWEtYm91
bmNlc0BpZXRmLm9yZz4+IE9uIEJlaGFsZiBPZiBbZXh0XSBGcmllcywgU3RlZmZlbg0KU2VudDog
U2Ftc3RhZywgOS4gTcOkcnogMjAxOSAxNDoxOA0KVG86IGFuaW1hQGlldGYub3JnPG1haWx0bzph
bmltYUBpZXRmLm9yZz47IGppYW5nc2hlbmdAaHVhd2VpLmNvbTxtYWlsdG86amlhbmdzaGVuZ0Bo
dWF3ZWkuY29tPg0KQ2M6IGFuaW1hLWNoYWlyc0BpZXRmLm9yZzxtYWlsdG86YW5pbWEtY2hhaXJz
QGlldGYub3JnPg0KU3ViamVjdDogUmU6IFtBbmltYV0gQ2FsbCBmb3IgYWdlbmRhIEFOSU1BIEAg
SUVURiAxMDQsIFByYWd1ZQ0KDQpIaSBTaGVuZywgaGkgVG9lcmxlc3MNCg0KQXMgYXNrZWQgZWFy
bGllciwgd2Ugd291bGQgbGlrZSB0byBoYXZlIGEgdGltZSBzbG90IHRvIGRpc2N1c3MgdGhlIGFz
eW5jaHJvbm91cyBlbnJvbGxtZW50IHN1cHBvcnQgaW4gQlJTS0kuIEkgd2lsbCBzdWJtaXQgdGhl
IGNvcnJlc3BvbmRpbmcgZHJhZnQgTW9uZGF5IGxhdGVzdC4NCg0KDQpOYW1lIG9mIHRpbWUgc2xv
dDogU3VwcG9ydCBvZiBhc3luY2hyb25vdXMgZW5yb2xsbWVudCBpbiBCUlNLSQ0KDQpOYW1lIG9m
IGRyYWZ0KHMpOiBkcmFmdC1mcmllcy1icnNraS1hc3luYy1lbnJvbGwtMDANCg0KVGltZSByZXF1
ZXN0ZWQ6IDEwIG1pbg0KDQpQcmVzZW50ZXIgbmFtZShzKTogU3RlZmZlbiBGcmllcw0KDQpUaGFu
ayB5b3UgYW5kIGJlc3QgcmVnYXJkcw0KU3RlZmZlbg0KDQpGcm9tOiBTaGVuZyBKaWFuZyA8amlh
bmdzaGVuZ0BodWF3ZWkuY29tPG1haWx0bzpqaWFuZ3NoZW5nQGh1YXdlaS5jb20+Pg0KU3ViamVj
dDogW0FuaW1hXSBDYWxsIGZvciBhZ2VuZGEgQU5JTUEgQCBJRVRGIDEwNO+8jCBQcmFndWUNCkRh
dGU6IDggTWFyY2ggMjAxOSBhdCAwNzo1OToxNiBDRVQNClRvOiAiYW5pbWFAaWV0Zi5vcmc8bWFp
bHRvOmFuaW1hQGlldGYub3JnPiIgPGFuaW1hQGlldGYub3JnPG1haWx0bzphbmltYUBpZXRmLm9y
Zz4+DQpDYzogImFuaW1hLWNoYWlyc0BpZXRmLm9yZzxtYWlsdG86YW5pbWEtY2hhaXJzQGlldGYu
b3JnPiIgPGFuaW1hLWNoYWlyc0BpZXRmLm9yZzxtYWlsdG86YW5pbWEtY2hhaXJzQGlldGYub3Jn
Pj4NCg0KDQpIaSwgYWxsIGFuaW1hLA0KDQoNCg0KV2UgaGF2ZSBiZWVuIGFsbG9jYXRlZCBhIHNl
c3Npb24gb2YgMi1ob3VyIGZvciB0aGUgQU5JTUEgV0cgbWVldGluZyBmb3IgSUVURi0xMDQgKFBy
YWd1ZSkgLSBUdWVzZGF5IGFmdGVybm9vbiBzZXNzaW9uIEkuIFdlIGFyZSBub3cgc3RhcnRpbmcg
dG8gY29sbGVjdCBhZ2VuZGEgaXRlbXMgZm9yIHRoZSBzZXNzaW9uLiBQbGVhc2Ugc2VuZCB5b3Vy
IHJlcXVlc3QgZm9yIGFnZW5kYSBieSBNYXJjaCAxNHRoLCBUaHVyc2RheS4NCg0KDQoNCkZvciB0
aGlzIGNvbWluZyBtZWV0aW5nLCB3ZSB3b3VsZCBsaWtlIHRvIGRpc2N1c3MgcG90ZW50aWFsIGZ1
dHVyZSBBTklNQSB3b3Jrcy4gQXMgbm9ybWFsLCB0aGUgcHJpb3JpdHkgYW1vbmcgdGhlc2Ugbm9u
LWNoYXJ0ZXIgd29yayBpdGVtcyB3b3VsZCBiZTogdGhlc2UgdGhhdCBoYXZlIGFjdGl2ZSBkaXNj
dXNzaW9uIGluIG1haWwgbGlzdCwgdGhlbiB0aGVzZSBoYXZlIHN1Ym1pdHRlZCBkcmFmdHMsIGFu
ZCB0b3BpY3Mgd2l0aG91dCBkcmFmdHMuDQoNCg0KDQpQbGVhc2Ugc2VuZCB1cyAoYW5pbWEtY2hh
aXJzIGF0IGlldGYub3JnPGh0dHBzOi8vaWV0Zi5vcmcvPikgcmVxdWVzdHMgZm9yIHRpbWUgc2xv
dCBieSBNYXJjaCAxNHRoLCBUaHVyc2RheSBhbmQgaW5jbHVkZToNCg0KDQoNCk5hbWUgb2YgdGlt
ZSBzbG90Og0KDQpOYW1lIG9mIGRyYWZ0KHMpOg0KDQpUaW1lIHJlcXVlc3RlZDoNCg0KUHJlc2Vu
dGVyIG5hbWUocyk6DQoNCg0KDQpNb3JlIGRldGFpbHMgYWJvdXQgdGhlIElFVEYgMTA0LCBQcmFn
dWUgY2FuIGJlIGZvdW5kIGF0Og0KDQoNCg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvaG93L21lZXRp
bmdzLzEwNC8NCg0KDQoNCkFnYWluLCBwcmVzZW50ZXJzIGFuZCBkcmFmdCBhdXRob3JzIHBsZWFz
ZSBpbnZva2UgYWN0aXZlIGRpc2N1c3Npb25zIGluIHRoZSBBTklNQSBsaXN0LiBNYWlsIGxpc3Qg
aXMgYSB2ZXJ5IGdvb2QgcGxhY2UgdG8gZGlzY3VzcyBhbmQgcmVhY2ggY29uc2Vuc3VzIG9uIHRl
Y2huaWNhbCBpc3N1ZXMuDQoNCg0KDQpCZXN0IHJlZ2FyZHMsDQoNCg0KDQpUb2VybGVzcyAmIFNo
ZW5nDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KQW5p
bWEgbWFpbGluZyBsaXN0DQpBbmltYUBpZXRmLm9yZzxtYWlsdG86QW5pbWFAaWV0Zi5vcmc+DQpo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2FuaW1hDQoNCg0K

--_000_5D36713D8A4E7348A7E10DF7437A4B929037F986NKGEML515MBXchi_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk65a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0K
QGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiTVMgR290aGljIjsNCglwYW5vc2UtMToyIDExIDYg
OSA3IDIgNSA4IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgi
Ow0KCXBhbm9zZS0xOjIgNCA1IDMgNSA0IDYgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZh
bWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZh
Y2UNCgl7Zm9udC1mYW1pbHk6IlxA5a6L5L2TIjsNCglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEg
MSAxO30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6VUlDVEZvbnRUZXh0U3R5bGVUYWxsQm9k
eTsNCglwYW5vc2UtMTowIDAgMCAwIDAgMCAwIDAgMCAwO30NCkBmb250LWZhY2UNCgl7Zm9udC1m
YW1pbHk6IlxATVMgR290aGljIjsNCglwYW5vc2UtMToyIDExIDYgOSA3IDIgNSA4IDIgNDt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNvbnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIg
MiA0IDMgMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNv
Tm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAw
MXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2Vy
aWY7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7
DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwg
c3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29s
b3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcA0KCXttc28tc3R5bGUt
cHJpb3JpdHk6OTk7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBj
bTsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowY207DQoJZm9u
dC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseTrlrovkvZM7fQ0KcHJlDQoJe21zby1zdHlsZS1w
cmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRNTCDpooTorr7moLzlvI8gQ2hhciI7DQoJ
bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEwLjBwdDsN
Cglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCnNwYW4uSFRNTENoYXINCgl7bXNvLXN0eWxl
LW5hbWU6IkhUTUwg6aKE6K6+5qC85byPIENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsN
Cgltc28tc3R5bGUtbGluazoiSFRNTCDpooTorr7moLzlvI8iOw0KCWZvbnQtZmFtaWx5OiJDb3Vy
aWVyIE5ldyI7fQ0KcC5tc29ub3JtYWwwLCBsaS5tc29ub3JtYWwwLCBkaXYubXNvbm9ybWFsMA0K
CXttc28tc3R5bGUtbmFtZTptc29ub3JtYWw7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJ
bWFyZ2luLXJpZ2h0OjBjbTsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4t
bGVmdDowY207DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fu
cy1zZXJpZjt9DQpwLkhUTUxQcmVmb3JtYXR0ZWQsIGxpLkhUTUxQcmVmb3JtYXR0ZWQsIGRpdi5I
VE1MUHJlZm9ybWF0dGVkDQoJe21zby1zdHlsZS1uYW1lOiJIVE1MIFByZWZvcm1hdHRlZCI7DQoJ
bXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1hcmdpbjowY207DQoJ
bWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6
IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5IVE1MUHJlZm9ybWF0dGVkQ2hhcg0KCXttc28t
c3R5bGUtbmFtZToiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCI7DQoJZm9udC1mYW1pbHk6
Q29uc29sYXM7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjINCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7
DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6IzFGNDk3RDsNCglm
b250LXdlaWdodDpub3JtYWw7DQoJZm9udC1zdHlsZTpub3JtYWw7DQoJdGV4dC1kZWNvcmF0aW9u
Om5vbmUgbm9uZTt9DQpzcGFuLkVtYWlsU3R5bGUyNA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25h
bC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjojMUY0
OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZv
bnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIu
MHB0Ow0KCW1hcmdpbjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2LldvcmRTZWN0
aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5
XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4N
CjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlv
dXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286
c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJaSC1D
TiIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEi
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTAuNXB0O2NvbG9yOiMxRjQ5N0QiPkhpLCBTdGVmZmVuLDxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjEwLjVwdDtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTox
MC41cHQ7Y29sb3I6IzFGNDk3RCI+SSBjYW4gY29uZmlybSB5b3VyIHJlcXVlc3QuIFRoZSBjaGFp
cnMgd291bGQgYWxsb2NhdGUgdGltZSBhY2NvcmRpbmcgdG8gdGhlIGFwcGxpY2F0aW9uIHNpdHVh
dGlvbiBhbmQgcHJpb3JpdHkgcG9saWN5LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtj
b2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6
IzFGNDk3RCI+UmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6IzFG
NDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2NvbG9yOiMxRjQ5N0Qi
PlNoZW5nPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2NvbG9yOiMxRjQ5N0QiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1s
ZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0K
PGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3Bh
ZGRpbmc6My4wcHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4g
bGFuZz0iRU4tVVMiPkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyI+IEZyaWVzLCBT
dGVmZmVuIFttYWlsdG86c3RlZmZlbi5mcmllc0BzaWVtZW5zLmNvbV0NCjxicj4NCjxiPlNlbnQ6
PC9iPiBNb25kYXksIE1hcmNoIDExLCAyMDE5IDY6MDQgUE08YnI+DQo8Yj5Ubzo8L2I+IGFuaW1h
QGlldGYub3JnOyBTaGVuZyBKaWFuZyAmbHQ7amlhbmdzaGVuZ0BodWF3ZWkuY29tJmd0Ozxicj4N
CjxiPkNjOjwvYj4gYW5pbWEtY2hhaXJzQGlldGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJF
OiBbQW5pbWFdIENhbGwgZm9yIGFnZW5kYSBBTklNQSBAIElFVEYgMTA0LCBQcmFndWU8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkRFIj5IaSBTaGVuZywgaGkgVG9lcmxlc3MsIDxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iY29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5CYXNl
ZCBvbiB0aGUgc3VibWl0dGVkIGRyYWZ0LCBoZXJlIGEgc21hbGwgdXBkYXRlIGZvciB0aGUgYWdl
bmRhIHJlcXVlc3QgKG5hbWUgZW5oYW5jZW1lbnQgb2YgdGhlIGRyYWZ0KTo8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImNvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iY29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+TmFtZSBvZiB0
aW1lIHNsb3Q6IFN1cHBvcnQgb2YgYXN5bmNocm9ub3VzIGVucm9sbG1lbnQgaW4gQlJTS0kNCjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iY29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+TmFt
ZSBvZiBkcmFmdChzKTogZHJhZnQtZnJpZXMtYW5pbWEtYnJza2ktYXN5bmMtZW5yb2xsLTAwPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5UaW1l
IHJlcXVlc3RlZDogMTAgbWluPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0
LWxhbmd1YWdlOkVOLVVTIj5QcmVzZW50ZXIgbmFtZShzKTogU3RlZmZlbiBGcmllczxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iY29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5CZXN0
IHJlZ2FyZHM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6
RU4tVVMiPlN0ZWZmZW48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRp
dj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBw
dDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxz
cGFuIGxhbmc9IkVOLVVTIj5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiPiBBbmlt
YSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFuaW1hLWJvdW5jZXNAaWV0Zi5vcmciPmFuaW1hLWJvdW5j
ZXNAaWV0Zi5vcmc8L2E+Jmd0Ow0KPGI+T24gQmVoYWxmIE9mIDwvYj5bZXh0XSBGcmllcywgU3Rl
ZmZlbjxicj4NCjxiPlNlbnQ6PC9iPiBTYW1zdGFnLCA5LiBNw6RyeiAyMDE5IDE0OjE4PGJyPg0K
PGI+VG86PC9iPiA8YSBocmVmPSJtYWlsdG86YW5pbWFAaWV0Zi5vcmciPmFuaW1hQGlldGYub3Jn
PC9hPjsgPGEgaHJlZj0ibWFpbHRvOmppYW5nc2hlbmdAaHVhd2VpLmNvbSI+DQpqaWFuZ3NoZW5n
QGh1YXdlaS5jb208L2E+PGJyPg0KPGI+Q2M6PC9iPiA8YSBocmVmPSJtYWlsdG86YW5pbWEtY2hh
aXJzQGlldGYub3JnIj5hbmltYS1jaGFpcnNAaWV0Zi5vcmc8L2E+PGJyPg0KPGI+U3ViamVjdDo8
L2I+IFJlOiBbQW5pbWFdIENhbGwgZm9yIGFnZW5kYSBBTklNQSBAIElFVEYgMTA0LCBQcmFndWU8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gbGFuZz0iREUiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJERSI+SGkgU2hlbmcsIGhpIFRvZXJsZXNz
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gbGFuZz0iREUiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkRFIj5BcyBhc2tlZCBlYXJs
aWVyLCB3ZSB3b3VsZCBsaWtlIHRvIGhhdmUgYSB0aW1lIHNsb3QgdG8gZGlzY3VzcyB0aGUgYXN5
bmNocm9ub3VzIGVucm9sbG1lbnQgc3VwcG9ydCBpbiBCUlNLSS4gSSB3aWxsIHN1Ym1pdCB0aGUg
Y29ycmVzcG9uZGluZyBkcmFmdCBNb25kYXkgbGF0ZXN0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkRFIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBzdHlsZT0ibWFyZ2lu
OjBjbTttYXJnaW4tYm90dG9tOi4wMDAxcHQ7Zm9udC1zdHJldGNoOiBub3JtYWwiPjxzcGFuIGxh
bmc9IkRFIj5OYW1lIG9mIHRpbWUgc2xvdDogU3VwcG9ydCBvZiBhc3luY2hyb25vdXMgZW5yb2xs
bWVudCBpbiBCUlNLSSZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIHN0eWxlPSJtYXJn
aW46MGNtO21hcmdpbi1ib3R0b206LjAwMDFwdDtmb250LXN0cmV0Y2g6IG5vcm1hbCI+PHNwYW4g
bGFuZz0iREUiPk5hbWUgb2YgZHJhZnQocyk6Jm5ic3A7PC9zcGFuPjxzcGFuIGxhbmc9IkRFIiBz
dHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYiPmRyYWZ0
LWZyaWVzLWJyc2tpLWFzeW5jLWVucm9sbC0wMDwvc3Bhbj48c3BhbiBsYW5nPSJERSI+PG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgc3R5bGU9Im1hcmdpbjowY207bWFyZ2luLWJvdHRvbTouMDAw
MXB0O2ZvbnQtc3RyZXRjaDogbm9ybWFsIj48c3BhbiBsYW5nPSJERSI+VGltZSByZXF1ZXN0ZWQ6
IDEwIG1pbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIHN0eWxlPSJtYXJnaW46MGNtO21hcmdp
bi1ib3R0b206LjAwMDFwdDtmb250LXN0cmV0Y2g6IG5vcm1hbCI+PHNwYW4gbGFuZz0iREUiPlBy
ZXNlbnRlciBuYW1lKHMpOiBTdGVmZmVuIEZyaWVzPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iREUiPiZuYnNwOzxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkRFIj5UaGFuayB5b3UgYW5kIGJlc3QgcmVnYXJkczxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkRFIj5TdGVmZmVuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkRFIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1
LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFy
Z2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxiPjxzcGFuIGxhbmc9IkRFIiBz
dHlsZT0iY29sb3I6YmxhY2siPkZyb206Jm5ic3A7PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJERSIg
c3R5bGU9ImNvbG9yOmJsYWNrIj5TaGVuZyBKaWFuZyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmppYW5n
c2hlbmdAaHVhd2VpLmNvbSI+amlhbmdzaGVuZ0BodWF3ZWkuY29tPC9hPiZndDs8L3NwYW4+PHNw
YW4gbGFuZz0iREUiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PGI+PHNwYW4gbGFu
Zz0iREUiIHN0eWxlPSJjb2xvcjpibGFjayI+U3ViamVjdDombmJzcDtbQW5pbWFdIENhbGwgZm9y
IGFnZW5kYSBBTklNQSBAIElFVEYgMTA0PC9zcGFuPjwvYj48Yj48c3BhbiBzdHlsZT0iZm9udC1m
YW1pbHk6JnF1b3Q7TVMgR290aGljJnF1b3Q7O2NvbG9yOmJsYWNrIj7vvIw8L3NwYW4+PC9iPjxi
PjxzcGFuIGxhbmc9IkRFIiBzdHlsZT0iY29sb3I6YmxhY2siPiBQcmFndWU8L3NwYW4+PC9iPjxz
cGFuIGxhbmc9IkRFIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxiPjxzcGFuIGxh
bmc9IkRFIiBzdHlsZT0iY29sb3I6YmxhY2siPkRhdGU6Jm5ic3A7PC9zcGFuPjwvYj48c3BhbiBs
YW5nPSJERSIgc3R5bGU9ImNvbG9yOmJsYWNrIj44IE1hcmNoIDIwMTkgYXQgMDc6NTk6MTYgQ0VU
PC9zcGFuPjxzcGFuIGxhbmc9IkRFIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxi
PjxzcGFuIGxhbmc9IkRFIiBzdHlsZT0iY29sb3I6YmxhY2siPlRvOiZuYnNwOzwvc3Bhbj48L2I+
PHNwYW4gbGFuZz0iREUiIHN0eWxlPSJjb2xvcjpibGFjayI+JnF1b3Q7PGEgaHJlZj0ibWFpbHRv
OmFuaW1hQGlldGYub3JnIj5hbmltYUBpZXRmLm9yZzwvYT4mcXVvdDsgJmx0OzxhIGhyZWY9Im1h
aWx0bzphbmltYUBpZXRmLm9yZyI+YW5pbWFAaWV0Zi5vcmc8L2E+Jmd0Ozwvc3Bhbj48c3BhbiBs
YW5nPSJERSI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48Yj48c3BhbiBsYW5nPSJE
RSIgc3R5bGU9ImNvbG9yOmJsYWNrIj5DYzombmJzcDs8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkRF
IiBzdHlsZT0iY29sb3I6YmxhY2siPiZxdW90OzxhIGhyZWY9Im1haWx0bzphbmltYS1jaGFpcnNA
aWV0Zi5vcmciPmFuaW1hLWNoYWlyc0BpZXRmLm9yZzwvYT4mcXVvdDsgJmx0OzxhIGhyZWY9Im1h
aWx0bzphbmltYS1jaGFpcnNAaWV0Zi5vcmciPmFuaW1hLWNoYWlyc0BpZXRmLm9yZzwvYT4mZ3Q7
PC9zcGFuPjxzcGFuIGxhbmc9IkRFIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gbGFu
Zz0iREUiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cHJlPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VUlDVEZvbnRUZXh0U3R5bGVUYWxs
Qm9keSZxdW90OyxzZXJpZjtjb2xvcjpibGFjayI+SGksIGFsbCBhbmltYSw8L3NwYW4+PHNwYW4g
bGFuZz0iREUiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1VJQ1RGb250VGV4dFN0eWxlVGFsbEJvZHkmcXVv
dDssc2VyaWY7Y29sb3I6YmxhY2siPiZuYnNwOzwvc3Bhbj48c3BhbiBsYW5nPSJERSI+PG86cD48
L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1m
YW1pbHk6JnF1b3Q7VUlDVEZvbnRUZXh0U3R5bGVUYWxsQm9keSZxdW90OyxzZXJpZjtjb2xvcjpi
bGFjayI+V2UgaGF2ZSBiZWVuIGFsbG9jYXRlZCBhIHNlc3Npb24gb2YgMi1ob3VyIGZvciB0aGUg
QU5JTUEgV0cgbWVldGluZyBmb3IgSUVURi0xMDQgKFByYWd1ZSkgLSBUdWVzZGF5IGFmdGVybm9v
biBzZXNzaW9uIEkuIFdlIGFyZSBub3cgc3RhcnRpbmcgdG8gY29sbGVjdCBhZ2VuZGEgaXRlbXMg
Zm9yIHRoZSBzZXNzaW9uLiBQbGVhc2Ugc2VuZCB5b3VyIHJlcXVlc3QgZm9yIGFnZW5kYSBieSBN
YXJjaCAxNHRoLCBUaHVyc2RheS48L3NwYW4+PHNwYW4gbGFuZz0iREUiPjxvOnA+PC9vOnA+PC9z
cGFuPjwvcHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZx
dW90O1VJQ1RGb250VGV4dFN0eWxlVGFsbEJvZHkmcXVvdDssc2VyaWY7Y29sb3I6YmxhY2siPiZu
YnNwOzwvc3Bhbj48c3BhbiBsYW5nPSJERSI+PG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJl
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VUlDVEZvbnRUZXh0
U3R5bGVUYWxsQm9keSZxdW90OyxzZXJpZjtjb2xvcjpibGFjayI+Rm9yIHRoaXMgY29taW5nIG1l
ZXRpbmcsIHdlIHdvdWxkIGxpa2UgdG8gZGlzY3VzcyBwb3RlbnRpYWwgZnV0dXJlIEFOSU1BIHdv
cmtzLiBBcyBub3JtYWwsIHRoZSBwcmlvcml0eSBhbW9uZyB0aGVzZSBub24tY2hhcnRlciB3b3Jr
IGl0ZW1zIHdvdWxkIGJlOiB0aGVzZSB0aGF0IGhhdmUgYWN0aXZlIGRpc2N1c3Npb24gaW4gbWFp
bCBsaXN0LCB0aGVuIHRoZXNlIGhhdmUgc3VibWl0dGVkIGRyYWZ0cywgYW5kIHRvcGljcyB3aXRo
b3V0IGRyYWZ0cy48L3NwYW4+PHNwYW4gbGFuZz0iREUiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJl
Pg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1VJQ1RG
b250VGV4dFN0eWxlVGFsbEJvZHkmcXVvdDssc2VyaWY7Y29sb3I6YmxhY2siPiZuYnNwOzwvc3Bh
bj48c3BhbiBsYW5nPSJERSI+PG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VUlDVEZvbnRUZXh0U3R5bGVUYWxs
Qm9keSZxdW90OyxzZXJpZjtjb2xvcjpibGFjayI+UGxlYXNlIHNlbmQgdXMgKGFuaW1hLWNoYWly
cyBhdCA8YSBocmVmPSJodHRwczovL2lldGYub3JnLyI+aWV0Zi5vcmc8L2E+KSByZXF1ZXN0cyBm
b3IgdGltZSBzbG90IGJ5IE1hcmNoIDE0dGgsIFRodXJzZGF5IGFuZCBpbmNsdWRlOjwvc3Bhbj48
c3BhbiBsYW5nPSJERSI+PG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VUlDVEZvbnRUZXh0U3R5bGVUYWxsQm9k
eSZxdW90OyxzZXJpZjtjb2xvcjpibGFjayI+Jm5ic3A7PC9zcGFuPjxzcGFuIGxhbmc9IkRFIj48
bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LWZhbWlseTomcXVvdDtVSUNURm9udFRleHRTdHlsZVRhbGxCb2R5JnF1b3Q7LHNlcmlmO2Nv
bG9yOmJsYWNrIj5OYW1lIG9mIHRpbWUgc2xvdDo8L3NwYW4+PHNwYW4gbGFuZz0iREUiPjxvOnA+
PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQt
ZmFtaWx5OiZxdW90O1VJQ1RGb250VGV4dFN0eWxlVGFsbEJvZHkmcXVvdDssc2VyaWY7Y29sb3I6
YmxhY2siPk5hbWUgb2YgZHJhZnQocyk6PC9zcGFuPjxzcGFuIGxhbmc9IkRFIj48bzpwPjwvbzpw
Pjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWls
eTomcXVvdDtVSUNURm9udFRleHRTdHlsZVRhbGxCb2R5JnF1b3Q7LHNlcmlmO2NvbG9yOmJsYWNr
Ij5UaW1lIHJlcXVlc3RlZDo8L3NwYW4+PHNwYW4gbGFuZz0iREUiPjxvOnA+PC9vOnA+PC9zcGFu
PjwvcHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90
O1VJQ1RGb250VGV4dFN0eWxlVGFsbEJvZHkmcXVvdDssc2VyaWY7Y29sb3I6YmxhY2siPlByZXNl
bnRlciBuYW1lKHMpOjwvc3Bhbj48c3BhbiBsYW5nPSJERSI+PG86cD48L286cD48L3NwYW4+PC9w
cmU+DQo8cHJlPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VUlD
VEZvbnRUZXh0U3R5bGVUYWxsQm9keSZxdW90OyxzZXJpZjtjb2xvcjpibGFjayI+Jm5ic3A7PC9z
cGFuPjxzcGFuIGxhbmc9IkRFIj48bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtVSUNURm9udFRleHRTdHlsZVRh
bGxCb2R5JnF1b3Q7LHNlcmlmO2NvbG9yOmJsYWNrIj5Nb3JlIGRldGFpbHMgYWJvdXQgdGhlIElF
VEYgMTA0LCBQcmFndWUgY2FuIGJlIGZvdW5kIGF0Ojwvc3Bhbj48c3BhbiBsYW5nPSJERSI+PG86
cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1mYW1pbHk6JnF1b3Q7VUlDVEZvbnRUZXh0U3R5bGVUYWxsQm9keSZxdW90OyxzZXJpZjtjb2xv
cjpibGFjayI+Jm5ic3A7PC9zcGFuPjxzcGFuIGxhbmc9IkRFIj48bzpwPjwvbzpwPjwvc3Bhbj48
L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtV
SUNURm9udFRleHRTdHlsZVRhbGxCb2R5JnF1b3Q7LHNlcmlmO2NvbG9yOmJsYWNrIj48YSBocmVm
PSJodHRwczovL3d3dy5pZXRmLm9yZy9ob3cvbWVldGluZ3MvMTA0LyI+aHR0cHM6Ly93d3cuaWV0
Zi5vcmcvaG93L21lZXRpbmdzLzEwNC88L2E+PC9zcGFuPjxzcGFuIGxhbmc9IkRFIj48bzpwPjwv
bzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZh
bWlseTomcXVvdDtVSUNURm9udFRleHRTdHlsZVRhbGxCb2R5JnF1b3Q7LHNlcmlmO2NvbG9yOmJs
YWNrIj4mbmJzcDs8L3NwYW4+PHNwYW4gbGFuZz0iREUiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJl
Pg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1VJQ1RG
b250VGV4dFN0eWxlVGFsbEJvZHkmcXVvdDssc2VyaWY7Y29sb3I6YmxhY2siPkFnYWluLCBwcmVz
ZW50ZXJzIGFuZCBkcmFmdCBhdXRob3JzIHBsZWFzZSBpbnZva2UgYWN0aXZlIGRpc2N1c3Npb25z
IGluIHRoZSBBTklNQSBsaXN0LiBNYWlsIGxpc3QgaXMgYSB2ZXJ5IGdvb2QgcGxhY2UgdG8gZGlz
Y3VzcyBhbmQgcmVhY2ggY29uc2Vuc3VzIG9uIHRlY2huaWNhbCBpc3N1ZXMuPC9zcGFuPjxzcGFu
IGxhbmc9IkRFIj48bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtVSUNURm9udFRleHRTdHlsZVRhbGxCb2R5JnF1
b3Q7LHNlcmlmO2NvbG9yOmJsYWNrIj4mbmJzcDs8L3NwYW4+PHNwYW4gbGFuZz0iREUiPjxvOnA+
PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQt
ZmFtaWx5OiZxdW90O1VJQ1RGb250VGV4dFN0eWxlVGFsbEJvZHkmcXVvdDssc2VyaWY7Y29sb3I6
YmxhY2siPkJlc3QgcmVnYXJkcyw8L3NwYW4+PHNwYW4gbGFuZz0iREUiPjxvOnA+PC9vOnA+PC9z
cGFuPjwvcHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZx
dW90O1VJQ1RGb250VGV4dFN0eWxlVGFsbEJvZHkmcXVvdDssc2VyaWY7Y29sb3I6YmxhY2siPiZu
YnNwOzwvc3Bhbj48c3BhbiBsYW5nPSJERSI+PG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJl
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7VUlDVEZvbnRUZXh0
U3R5bGVUYWxsQm9keSZxdW90OyxzZXJpZjtjb2xvcjpibGFjayI+VG9lcmxlc3MgJmFtcDsgU2hl
bmc8L3NwYW4+PHNwYW4gbGFuZz0iREUiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iREUiIHN0eWxlPSJjb2xvcjpibGFjayI+X19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQpBbmltYSBtYWls
aW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJtYWlsdG86QW5pbWFAaWV0Zi5vcmciPkFuaW1hQGlldGYu
b3JnPC9hPjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu
Zm8vYW5pbWEiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vYW5pbWE8L2E+
PC9zcGFuPjxzcGFuIGxhbmc9IkRFIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwv
YmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gbGFuZz0iREUiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJERSI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_5D36713D8A4E7348A7E10DF7437A4B929037F986NKGEML515MBXchi_--


From nobody Mon Mar 11 04:31:40 2019
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 5DB96129AA0; Mon, 11 Mar 2019 04:31:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 loNBPNvHeoZs; Mon, 11 Mar 2019 04:31:36 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 ED21F1200D8; Mon, 11 Mar 2019 04:31:35 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 53819A5A6C6C9521D7E3; Mon, 11 Mar 2019 11:31:34 +0000 (GMT)
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 11 Mar 2019 11:31:26 +0000
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml701-chm.china.huawei.com (10.201.108.50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Mon, 11 Mar 2019 11:31:26 +0000
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml701-chm.china.huawei.com (10.201.108.50) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1591.10 via Frontend Transport; Mon, 11 Mar 2019 11:31:26 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0415.000; Mon, 11 Mar 2019 19:31:10 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Xun Xiao <Xun.Xiao@huawei.com>, "anima@ietf.org" <anima@ietf.org>
CC: "anima-chairs@ietf.org" <anima-chairs@ietf.org>, Artur Hecker <Artur.Hecker@huawei.com>
Thread-Topic: =?gb2312?B?Q2FsbCBmb3IgYWdlbmRhIEFOSU1BIEAgSUVURiAxMDSjrCBQcmFndWU=?=
Thread-Index: AdTVSp7fUdNBEg1lSfyRueXgFJmsUwAWBVegAJbLiDA=
Date: Mon, 11 Mar 2019 11:31:10 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B929037F998@NKGEML515-MBX.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B929035710C@NKGEML515-MBX.china.huawei.com> <67C6AE5A0CF6AD45A8571ED3F6E802E413864642@lhreml507-mbb>
In-Reply-To: <67C6AE5A0CF6AD45A8571ED3F6E802E413864642@lhreml507-mbb>
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_5D36713D8A4E7348A7E10DF7437A4B929037F998NKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/-Tq7yEoqKAr8pcQ2StAEiX8sEx0>
Subject: Re: [Anima]  =?gb2312?b?Q2FsbCBmb3IgYWdlbmRhIEFOSU1BIEAgSUVURiAxMDQ=?= =?gb2312?b?o6wgUHJhZ3Vl?=
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Mar 2019 11:31:39 -0000

--_000_5D36713D8A4E7348A7E10DF7437A4B929037F998NKGEML515MBXchi_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

SGksIFhpYW8sDQoNCkkgY2FuIGNvbmZpcm0geW91ciByZXF1ZXN0LiBUaGUgY2hhaXJzIHdvdWxk
IGFsbG9jYXRlIHRpbWUgYWNjb3JkaW5nIHRvIHRoZSBhcHBsaWNhdGlvbiBzaXR1YXRpb24gYW5k
IHByaW9yaXR5IHBvbGljeS4NCg0KUmVnYXJkcywNCg0KU2hlbmcNCg0KRnJvbTogWHVuIFhpYW8N
ClNlbnQ6IEZyaWRheSwgTWFyY2ggMDgsIDIwMTkgNzozOSBQTQ0KVG86IFNoZW5nIEppYW5nIDxq
aWFuZ3NoZW5nQGh1YXdlaS5jb20+OyBhbmltYUBpZXRmLm9yZw0KQ2M6IGFuaW1hLWNoYWlyc0Bp
ZXRmLm9yZzsgQXJ0dXIgSGVja2VyIDxBcnR1ci5IZWNrZXJAaHVhd2VpLmNvbT4NClN1YmplY3Q6
IFJFOiBDYWxsIGZvciBhZ2VuZGEgQU5JTUEgQCBJRVRGIDEwNKOsIFByYWd1ZQ0KDQpIaSBTaGVu
ZywNCg0KV2Ugd291bGQgbGlrZSB0byBoYXZlIGEgdGltZSBzbG90IHRvIHJlcG9ydCB0aGUgdXBk
YXRlIHdlIG1hZGUgZm9yIHRoZSBpbmZvcm1hdGlvbi1kaXN0cmlidXRpb24gZHJhZnQgKGluY2x1
ZGluZyB1cGRhdGVzLiBUaGFua3MuDQoNCg0KTmFtZSBvZiB0aW1lIHNsb3Q6IFVwZGF0ZXMgb24g
SW5mb3JtYXRpb24gRGlzdHJpYnV0aW9uIGluIEF1dG9ub21pYyBOZXR3b3JraW5nDQoNCk5hbWUg
b2YgZHJhZnQocyk6IGRyYWZ0LWxpdS1hbmltYS1ncmFzcC1kaXN0cmlidXRpb24tMTANCg0KVGlt
ZSByZXF1ZXN0ZWQ6IDEwIG1pbnMNCg0KUHJlc2VudGVyIG5hbWUocyk6IFh1biBYaWFvIGFuZCBB
cnR1ciBIZWNrZXINCg0KQmVzdCBSZWdhcmRzLA0KDQpYdW4gWGlhbyAo0KTRuCkNCkFkdmFuY2Vk
IFdpcmVsZXNzIFRlY2hub2xvZ3kgTGFiDQpNdW5pY2ggUmVzZWFyY2ggQ2VudGVyDQoNCkZyb206
IEFuaW1hIFttYWlsdG86YW5pbWEtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFNoZW5n
IEppYW5nDQpTZW50OiBGcmlkYXksIDggTWFyY2ggMjAxOSAwNzo1OQ0KVG86IGFuaW1hQGlldGYu
b3JnPG1haWx0bzphbmltYUBpZXRmLm9yZz4NCkNjOiBhbmltYS1jaGFpcnNAaWV0Zi5vcmc8bWFp
bHRvOmFuaW1hLWNoYWlyc0BpZXRmLm9yZz4NClN1YmplY3Q6IFtBbmltYV0gQ2FsbCBmb3IgYWdl
bmRhIEFOSU1BIEAgSUVURiAxMDSjrCBQcmFndWUNCg0KDQpIaSwgYWxsIGFuaW1hLA0KDQoNCg0K
V2UgaGF2ZSBiZWVuIGFsbG9jYXRlZCBhIHNlc3Npb24gb2YgMi1ob3VyIGZvciB0aGUgQU5JTUEg
V0cgbWVldGluZyBmb3IgSUVURi0xMDQgKFByYWd1ZSkgLSBUdWVzZGF5IGFmdGVybm9vbiBzZXNz
aW9uIEkuIFdlIGFyZSBub3cgc3RhcnRpbmcgdG8gY29sbGVjdCBhZ2VuZGEgaXRlbXMgZm9yIHRo
ZSBzZXNzaW9uLiBQbGVhc2Ugc2VuZCB5b3VyIHJlcXVlc3QgZm9yIGFnZW5kYSBieSBNYXJjaCAx
NHRoLCBUaHVyc2RheS4NCg0KDQoNCkZvciB0aGlzIGNvbWluZyBtZWV0aW5nLCB3ZSB3b3VsZCBs
aWtlIHRvIGRpc2N1c3MgcG90ZW50aWFsIGZ1dHVyZSBBTklNQSB3b3Jrcy4gQXMgbm9ybWFsLCB0
aGUgcHJpb3JpdHkgYW1vbmcgdGhlc2Ugbm9uLWNoYXJ0ZXIgd29yayBpdGVtcyB3b3VsZCBiZTog
dGhlc2UgdGhhdCBoYXZlIGFjdGl2ZSBkaXNjdXNzaW9uIGluIG1haWwgbGlzdCwgdGhlbiB0aGVz
ZSBoYXZlIHN1Ym1pdHRlZCBkcmFmdHMsIGFuZCB0b3BpY3Mgd2l0aG91dCBkcmFmdHMuDQoNCg0K
DQpQbGVhc2Ugc2VuZCB1cyAoYW5pbWEtY2hhaXJzIGF0IGlldGYub3JnPGh0dHBzOi8vaWV0Zi5v
cmcvPikgcmVxdWVzdHMgZm9yIHRpbWUgc2xvdCBieSBNYXJjaCAxNHRoLCBUaHVyc2RheSBhbmQg
aW5jbHVkZToNCg0KDQoNCk5hbWUgb2YgdGltZSBzbG90Og0KDQpOYW1lIG9mIGRyYWZ0KHMpOg0K
DQpUaW1lIHJlcXVlc3RlZDoNCg0KUHJlc2VudGVyIG5hbWUocyk6DQoNCg0KDQpNb3JlIGRldGFp
bHMgYWJvdXQgdGhlIElFVEYgMTA0LCBQcmFndWUgY2FuIGJlIGZvdW5kIGF0Og0KDQoNCg0KaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvaG93L21lZXRpbmdzLzEwNC8NCg0KDQoNCkFnYWluLCBwcmVzZW50
ZXJzIGFuZCBkcmFmdCBhdXRob3JzIHBsZWFzZSBpbnZva2UgYWN0aXZlIGRpc2N1c3Npb25zIGlu
IHRoZSBBTklNQSBsaXN0LiBNYWlsIGxpc3QgaXMgYSB2ZXJ5IGdvb2QgcGxhY2UgdG8gZGlzY3Vz
cyBhbmQgcmVhY2ggY29uc2Vuc3VzIG9uIHRlY2huaWNhbCBpc3N1ZXMuDQoNCg0KDQpCZXN0IHJl
Z2FyZHMsDQoNCg0KDQpUb2VybGVzcyAmIFNoZW5nDQo=

--_000_5D36713D8A4E7348A7E10DF7437A4B929037F998NKGEML515MBXchi_
Content-Type: text/html; charset="gb2312"
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=3Dgb2312">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:=CB=CE=CC=E5;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
	{font-family:"\@=CB=CE=CC=E5";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"MS PGothic";
	panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
	{font-family:"\@MS PGothic";
	panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* 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;
	mso-fareast-language:JA;}
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 =D4=A4=C9=E8=B8=F1=CA=BD Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:JA;}
span.HTMLChar
	{mso-style-name:"HTML =D4=A4=C9=E8=B8=F1=CA=BD Char";
	mso-style-priority:99;
	mso-style-link:"HTML =D4=A4=C9=E8=B8=F1=CA=BD";
	font-family:=CB=CE=CC=E5;}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
	{mso-style-name:"HTML Preformatted";
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:JA;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@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">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Hi, Xia=
o,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">I can c=
onfirm your request. The chairs would allocate time according to the applic=
ation situation and priority policy.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Regards=
,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Sheng</=
span><span lang=3D"EN-US" style=3D"color:#1F497D;mso-fareast-language:ZH-CN=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D;mso-fare=
ast-language:ZH-CN"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><b><span la=
ng=3D"EN-US" style=3D"font-size:11.0pt;mso-fareast-language:ZH-CN">From:</s=
pan></b><span lang=3D"EN-US" style=3D"font-size:11.0pt;mso-fareast-language=
:ZH-CN"> Xun Xiao
<br>
<b>Sent:</b> Friday, March 08, 2019 7:39 PM<br>
<b>To:</b> Sheng Jiang &lt;jiangsheng@huawei.com&gt;; anima@ietf.org<br>
<b>Cc:</b> anima-chairs@ietf.org; Artur Hecker &lt;Artur.Hecker@huawei.com&=
gt;<br>
<b>Subject:</b> RE: Call for agenda ANIMA @ IETF 104</span><span style=3D"f=
ont-size:11.0pt;font-family:&quot;MS PGothic&quot;,sans-serif;mso-fareast-l=
anguage:ZH-CN">=A3=AC</span><span lang=3D"EN-US" style=3D"font-size:11.0pt;=
mso-fareast-language:ZH-CN"> Prague<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;color=
:#1F497D">Hi Sheng,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;color=
:#1F497D">We would like to have a time slot to report the update we made fo=
r the information-distribution draft (including updates. Thanks.<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Name of time slot: Updates on Inform=
ation Distribution in Autonomic Networking<o:p></o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Name of draft(s): draft-liu-anima-gr=
asp-distribution-10<o:p></o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Time requested: 10 mins<o:p></o:p></=
span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Presenter name(s): Xun Xiao and Artu=
r Hecker<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;color:#1F497D">Best Regards,<o:p></o:p=
></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;color:#1F497D"><o:p>&nbsp;</o:p></span=
></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;color:#1F497D">Xun Xiao (</span><span =
style=3D"font-size:11.0pt;font-family:=CB=CE=CC=E5;color:#1F497D;mso-fareas=
t-language:ZH-CN">=D0=A4=D1=B8</span><span lang=3D"EN-US" style=3D"font-siz=
e:11.0pt;color:#1F497D">)<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;color:#1F497D">Advanced Wireless Techn=
ology Lab<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US" style=3D"font-size:11.0pt;color:#1F497D">Munich Research Center<=
o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><b><span la=
ng=3D"EN-US" style=3D"font-size:11.0pt">From:</span></b><span lang=3D"EN-US=
" style=3D"font-size:11.0pt"> Anima [<a href=3D"mailto:anima-bounces@ietf.o=
rg">mailto:anima-bounces@ietf.org</a>]
<b>On Behalf Of </b>Sheng Jiang<br>
<b>Sent:</b> Friday, 8 March 2019 07:59<br>
<b>To:</b> <a href=3D"mailto:anima@ietf.org">anima@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:anima-chairs@ietf.org">anima-chairs@ietf.org</=
a><br>
<b>Subject:</b> [Anima] Call for agenda ANIMA @ IETF 104</span><span style=
=3D"font-size:11.0pt;font-family:=CB=CE=CC=E5;mso-fareast-language:ZH-CN">=
=A3=AC</span><span lang=3D"EN-US" style=3D"font-size:11.0pt"> Prague<o:p></=
o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal" align=3D"left" style=3D"text-align:left"><span lang=
=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Hi, all anima,<o:p></o:p></span></pr=
e>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">We have been allocated a session of =
2-hour for the ANIMA WG meeting for IETF-104 (Prague) - Tuesday afternoon s=
ession I. We are now starting to collect agenda items for the session. Plea=
se send your request for agenda by March 14th, Thursday.<o:p></o:p></span><=
/pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">For this coming meeting, we would li=
ke to discuss potential future ANIMA works. As normal, the priority among t=
hese non-charter work items would be: these that have active discussion in =
mail list, then these have submitted drafts, and topics without drafts.<o:p=
></o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Please send us (anima-chairs at <a h=
ref=3D"https://ietf.org/"><span style=3D"color:#337AB7">ietf.org</span></a>=
) requests for time slot by March 14th, Thursday and include:<o:p></o:p></s=
pan></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Name of time slot:<o:p></o:p></span>=
</pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Name of draft(s):<o:p></o:p></span><=
/pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Time requested:<o:p></o:p></span></p=
re>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Presenter name(s):<o:p></o:p></span>=
</pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">More details about the IETF 104, Pra=
gue can be found at:<o:p></o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529"><a href=3D"https://www.ietf.org/how/=
meetings/104/">https://www.ietf.org/how/meetings/104/</a><o:p></o:p></span>=
</pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Again, presenters and draft authors =
please invoke active discussions in the ANIMA list. Mail list is a very goo=
d place to discuss and reach consensus on technical issues.<o:p></o:p></spa=
n></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Best regards,<o:p></o:p></span></pre=
>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529"><o:p>&nbsp;</o:p></span></pre>
<pre style=3D"background:white"><span lang=3D"EN-US" style=3D"font-size:9.0=
pt;font-family:Consolas;color:#212529">Toerless &amp; Sheng<o:p></o:p></spa=
n></pre>
</div>
</div>
</body>
</html>

--_000_5D36713D8A4E7348A7E10DF7437A4B929037F998NKGEML515MBXchi_--


From nobody Mon Mar 11 08:26:31 2019
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 C97711279AD; Mon, 11 Mar 2019 08:26:29 -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.93.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: anima@ietf.org
Message-ID: <155231798978.23195.12461781808596333317@ietfa.amsl.com>
Date: Mon, 11 Mar 2019 08:26:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/HdjiMbXNcTOtT0iFUOmdyj1jj1E>
Subject: [Anima] I-D Action: draft-ietf-anima-autonomic-control-plane-19.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Mar 2019 15:26:30 -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           : An Autonomic Control Plane (ACP)
        Authors         : Toerless Eckert
                          Michael H. Behringer
                          Steinthor Bjarnason
	Filename        : draft-ietf-anima-autonomic-control-plane-19.txt
	Pages           : 153
	Date            : 2019-03-11

Abstract:
   Autonomic functions need a control plane to communicate, which
   depends on some addressing and routing.  This Autonomic Management
   and Control Plane should ideally be self-managing, and as independent
   as possible of configuration.  This document defines such a plane and
   calls it the "Autonomic Control Plane", with the primary use as a
   control plane for autonomic functions.  It also serves as a "virtual
   out-of-band channel" for Operations Administration and Management
   (OAM) communications over a network that provides automatically
   configured hop-by-hop authenticated and encrypted communications via
   automatically configured IPv6 even when the network is not
   configured, or misconfigured.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-anima-autonomic-control-plane/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-anima-autonomic-control-plane-19
https://datatracker.ietf.org/doc/html/draft-ietf-anima-autonomic-control-plane-19

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-anima-autonomic-control-plane-19


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 11 08:32:17 2019
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 41673131171; Mon, 11 Mar 2019 08:32:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 bIfwnmwUQqgQ; Mon, 11 Mar 2019 08:31:56 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A38C21200B3; Mon, 11 Mar 2019 08:31:52 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 25EE2548859; Mon, 11 Mar 2019 16:31:45 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 122A8440036; Mon, 11 Mar 2019 16:31:45 +0100 (CET)
Date: Mon, 11 Mar 2019 16:31:45 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Eric Rescorla <ekr@rtfm.com>
Cc: The IESG <iesg@ietf.org>, anima-chairs@ietf.org, draft-ietf-anima-autonomic-control-plane@ietf.org, Sheng Jiang <jiangsheng@huawei.com>, anima@ietf.org
Message-ID: <20190311153144.74vwtv4a22vmfcuk@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <153316779818.21822.14156274165395996235.idtracker@ietfa.amsl.com>
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/JnPr_Duf081Fp2HE8ow_jy8iwXw>
Subject: Re: [Anima] Eric Rescorla's Discuss on draft-ietf-anima-autonomic-control-plane-16: (with DISCUSS and COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Mar 2019 15:32:08 -0000

Thanks Eric, inline

This file is: https://github.com/anima-wg/autonomic-control-plane/blob/master/draft-ietf-anima-autonomic-control-plane/16-eric-rescorla-reply.txt

The following inline answers to your discuss have been integrated
into -19 of the draft which i just submitted. It also includes the
feedback to the comments by Eric and Ben. I was backlogged, and
after your review of -16 i had first responded to other reviewers
with -16/-17.

Note that this includes a hopefully more comprehensive section 6.1.3 explaining the Trust Anchor details required for the ACP, resulting from the variety of discuss of the reviewers on this topic.

Bens and Erics review where very good and comprehensive but alas
didn't make it easy for me to answer to them as quickly as i would have
wanted to. Unfortunately, i also had to go back and forth between
them, so i couldn't create a separate checkpoint version
showing ONLY changes for each of them. So the following diffs are
hopefully useful:

-18 to -19: Changes made for Ben and Eric

http://tools.ietf.org//rfcdiff?url1=https://tools.ietf.org/id/draft-ietf-anima-autonomic-control-plane-18.txt&url2=https://tools.ietf.org/id/draft-ietf-anima-autonomic-control-plane-19.txt

Note that this includes a hopefully more comprehensive section 6.1.3 explaining the Trust Anchor details required for the ACP, resulting from the variety of discuss of the reviewers on this topic.

-16 to -19: Changes since your last review (includes Alissa Coopers review)

http://tools.ietf.org//rfcdiff?url2=https://tools.ietf.org/id/draft-ietf-anima-autonomic-control-plane-16.txt&url2=https://tools.ietf.org/id/draft-ietf-anima-autonomic-control-plane-19.txt

Cheers
    Toerless

On Wed, Aug 01, 2018 at 04:56:38PM -0700, Eric Rescorla wrote:
> Eric Rescorla has entered the following ballot position for
> draft-ietf-anima-autonomic-control-plane-16: Discuss
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-anima-autonomic-control-plane/
> 
> 
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> Rich version of this review at:
> https://mozphab-ietf.devsvcdev.mozaws.net/D9959
> 
> 
> I found this document extremely hard to follow due to a large number
> of grammar errors. It really needs a very thorough copy-edit pass,
> which I believe is beyond the RFC-editor's usual process. Ideally, the
> WG would do this.
> 
> 
> DETAIL
> S 6.1.1.
> >      each other.  See Section 6.1.2.  Acp-domain-name SHOULD be the FQDN
> >      of a DNS domain owned by the operator assigning the certificate.
> >      This is a simple method to ensure that the domain is globally unique
> >      and collision of ACP addresses would therefore only happen due to ULA
> >      hash collisions.  If the operator does not own any FQDN, it should
> >      choose a string (in FQDN format) that intends to be equally unique.
> 
> These rules do not seem to be strong enough. Unless you have disjoint
> trust anchors, there is a potential for cross-domain attac.

Yes, two independent operators would use their own separate trust anchors.

If you are are owning the PKI root for multiple independent ACP networks,
you COULD also establish a process by which you validate that there is no
SHA256 hash collision between the different ACP domain names that want
to use your one trust anchor.

So, i am not sure what your point is.

> S 6.1.2.
> >      See section 4.2.1.6 of [RFC5280] for details on the subjectAltName
> >      field.
> >   
> >   6.1.2.  ACP domain membership check
> >   
> >      The following points constitute the ACP domain membership check of a
> 
> What is the relationship of these rules to the existing 5280 rules?

Note that there where already i hope good improvements in this text from -16
you reviewed to -18.

The first three bullet points are meant to summarise what we understand to be
the standard certificate verification rules for another entity (Bob). Use
ACP trust anchor and some proof of posession mechanism for the private key
(as in e.g.: TLS), verify Bobs cert is in its lifetime. 

It is not clear to me if RFC5280 is normative for this as i could not find
a single section i could point to as a reference.  I welcome suggestions
to shorten those rules by referring to prior established rules for the
same. This text was based on suggestions from the BRSKI authors who are more
experts on PKI.

Bullet item four mandates support for CRL / OCSP if used in the certificate.
Likewise: Better text welcome.

The fifts bullet item is the only new requirement. The ACP information
field must be present, syntactically correct and have the same acp-domain-name
field as the local node performing the ACP domain membership check.

> S 6.1.2.
> >   
> >      o  The peer has proved ownership of the private key associated with
> >         the certifictes public key.
> >   
> >      o  The peer's certificate is signed by one of the trust anchors
> >         associated with the ACP domain certificate.
> 
> So you don't allow chaining? It seems later that you say you do, but
> this language prohibits it.

No, that was an oversight. Changed second bullet to:

The peer's certificate passes certificate path validation as defined in [RFC5280] against one of the Trust Anchors associated with the ACP nodes ACP domain certificate (see <xref target="trust-points"/> below)

Better text suggestion welcome if this is correct.

> S 6.1.3.1.
> >      The objective value "SRV.est" indicates that the objective is an
> >      [RFC7030] compliant EST server because "est" is an [RFC6335]
> >      registered service name for [RFC7030].  Future backward compatible
> >      extensions/alternatives to [RFC7030] may be indicated through
> >      objective-value.  Future non-backward compatible certificate renewal
> >      options must use a different objective-name.
> 
> EST runs over HTTPS. What is the certificate that the server presents?

I could add text like:

The EST server MUST present a certificate that
is passing ACP domain membership check (<xref target="certcheck"/>) in its HTTPS 
(<xref target="RFC7540"/>) connection setup.

But i am actually not sure this is required, so i would rather like to do it
only when we understand it is. The way i understand it, there really does
not need to be transport layer security for certificate renewal because
the client can verify the certificate on its own merit. AFAIK,
draft-ietf-acme-star leverages that for example to provide certs from 
arbitrary caches.

The situation may be different for BRSKI, and likely the EST server can also
be the BRSKI server, but that would still make it better to describe
rewuirements against the server cert in BRSKI rather than in ACP if it
doesn't matter in the EST renewal case. 

> S 6.4.
> >      information in the ACP Adjacency table.
> >   
> >      The ACP is by default established exclusively between nodes in the
> >      same domain.  This includes all routing subdomains.  Appendix A.7
> >      explains how ACP connections across multiple routing subdomains are
> >      special.
> 
> I must be missing something, but how do you know what the routing
> domain is of an ACP node? I don't see it in the message above. Is it
> in some common header?

The routing subdomain is indicated via the ACP domain information field
in the certificate, but it is ignored during step 4 of the ACP domain membership
check hence resulting in above text that the ACP is built across all
routing-subdomains. It only serves to assign different address prefixes
within the same ACP network right now.

> S 6.5.
> >   
> >      o  Once the first secure channel protocol succeeds, the two peers
> >         know each other's certificates because they must be used by all
> >         secure channel protocols for mutual authentication.  The node with
> >         the lower Node-ID in the ACP address becomes Bob, the one with the
> >         higher Node-ID in the certificate Alice.
> 
> A ladder diagram would really help me here, because I'm confused about
> the order of events.

Can not figure out how to RFC-ASCII'fy a ladder diagram with the two
parallel connection setups, so i rather added the following more explicit
list of steps as a picture after the example. Hope this suffices to
answer your request.

| [1]    Node 1 sends GRASP AN_ACP message to announce itself
| 
| [2]    Node 2 sends GRASP AN_ACP message to announce itself
| 
| [3]    Node 2 receives [1] from Node 1
| 
| [4:C1] Because of [3], Node 2 starts as initiator on its
|        preferred secure channel protocol towards Node 1.
|        Connection C1.
| 
| [5]    Node 1 receives [2] from Node 2
| 
| [6:C2] Because of [5], Node 1 starts as initiator on its
|        preferred secure channel protocol towards Node 2.
|        Connection C2.
| 
| [7:C1] Node1 and Node2 have authenticated each others
|        certificate on connection C1 as valid ACP peers.
| 
| [8:C1] Node 1 certificate has lower ACP Node-ID than  Node2,
|        therefore Node 1 considers itself Bob and Node 2 Alice
|        on connection C1. Connection setup C1 is completed.
| 
| [9]    Node 1 (Bob)) refrains from attempting any further secure
|        channel connections to Node 2 (Alice) as learned from [2]
|        because it knows from [8:C1] that it is Bob relative
|        to Node 1.
| 
| [10:C2] Node1 and Node2 have authenticated each others
|        certificate on connection C2 (like [7:C1]).
| 
| [11:C2] Node 2 certificate has lower ACP Node-ID than  Node2,
|         therefore Node 1 considers itself Bob and Node 2 Alice
| 	on connection C1, but they also identify that C2 is to the
| 	same mutual peer as their C1, so this has no further impact.
| 
| [12:C2] Node 1 (Alice) closes C1. Because of [8:C1], Node 2 (Bob)
|         expected this.
| 
| [13]    Node 1 (Alice) and Node 2 (Bob) start data transfer across
|         C2, which makes it become a secure channel for the ACP.
| 
> As I understand it, Alice and Bob are both flooding their AN_ACP
> objectives. So, Alice sees Bob's and starts trying to connect to Bob.
> But Bob may not have Alice's objective, right? So, in the case you
> describe below, she just has to wait for it before she can try the
> remaining security protocols?

A node can initiate and complete in parallel any number of secure
channel protocol to a candidate peer (from which it has received
a AN_ACP GRASP objective). But as soon as one of those connection
succeeds and the node know it is "Bob" on the connection (because
of the comparison with the peers certificates ACP domain information field),
it will stop trying new connections to that peers IPv6 link-local address,
and its Alice's choice to figure out which of the potentially
parallel established connections to close and which to continue.

Aka: The logic is intended to be as simple as possible and secure.
The Alice/Bob self selection is secure because it is based on what
is learned from successfull secure channel setup.

> I note that you have no downgrade defense on the meta-negotiation
> between the protocols, so an attacker could potentially force you down
> to the weakest joint protocol. Why did you not provide a defense here?

Remember that the goal of this process is the negotiation to select
one of potentially multiple completely disjoint secure channel
protocols. Such as DTLS vs. IPsec.  And attempting to avoid he ned
to a network wide MTI protocol because we only use these protocols
for peer-to-peer and not every two nodes in the network need to be able to
directly peer with each other (you won't connect an IoT gateway to
an Internet backbone core-router).

One approach we thought of to allow negotiation of "the best" crypto
mutually supported would be to have a two-stage negotiation, e.g.:
first build some TLS connection and negotiate the next-stage, IPsec or DTLS.
But that would make thast first stage a network-wide MTI and run into
the risk that that protocols crypto becomes the weakest link. I actually
had that option in an earlier version of the draft and the WG and IETF
reviewers didn't like this double complexity, so it was removed.

If i have a man-in-the-middle, i also don't think eve such a two-stage
would work. I could negotiate what i think is the better crypto option
(let's say DTLS) all day long, but if the MiTM simply filters all DTLS
and only lets through IPsec, what can i do ?

> S 6.7.1.1.
> >      To run ACP via IPsec natively, no further IANA assignments/
> >      definitions are required.  An ACP node that is supporting native
> >      IPsec MUST use IPsec security setup via IKEv2, tunnel mode, local and
> >      peer link-local IPv6 addresses used for encapsulation.  It MUST then
> >      support ESP with AES256 for encryption and SHA256 hash and MUST NOT
> >      permit weaker crypto options.
> 
> This is not sufficient to guarantee interop. Also, this is an odd
> cipher suite chioice.
> 
>     Why are you requiring AES-256 rather than AES-128?

In all the implementations i was involved in we did not find hardware
that did not support AES-256, but there where platforms that could
not go higher, so this looked like the highest crypto safe length
to support common hardware crypto.

>     Why aren't you requiring AES-GCM?

Thanks. The need to specify this level of detail was not raised in before.
I have replaces AES256 with AES-256-GCM (rfc4106).

>     Why aren't you requiring specific key establishment methods (e.g.,
> ECDHE with P-256...)

Added. 

If the text is still insufficient in your opinion, i would welcome suggested
text that you consider to be a good recommendation, or at least the
set of parameters that we missed to specifiy. 

> S 6.7.2.
> >   
> >      To run ACP via UDP and DTLS v1.2 [RFC6347] a locally assigned UDP
> >      port is used that is announced as a parameter in the GRASP AN_ACP
> >      objective to candidate neighbors.  All ACP nodes supporting DTLS as a
> >      secure channel protocol MUST support AES256 encryption and MUST NOT
> >      permit weaker crypto options.
> 
> This is not sufficiently specific to guarantee interoperability. Which
> cipher suites? Also, why are you requiring AES-256 and not AES-128?

Removed AES-256 notion.

The reason for AES-256 was to be aligned with the IPsec requirements,
but of course, our expectation is that DTLS would be a SW implementation, so
this is not necessarily a good choice. Although i think the lowest common
denominator for DTLS is 128 ?

In any case, i changed the text to be equivalent to RFC8310 section 9. This
is the RFC thast you suggested me to leverge some time ago in email:

| All ACP nodes supporting DTLS as a secure channel protocol MUST
| adhere to the DTLS implementation recommendations and security
| considerations of <xref target="rfc7525"/> except with respect
| to the DTLS version. ACP nodes supporting DTLS MUST implement only
| DTLS 1.2 or later.  For example, implementing DTLS-1.3
| (<xref target="I-D.ietf-tls-dtls13"/>) is also an option.

The other MUST/SHOULD from RFC8310 section 9 did not seem to be relevant 
for our purposes.

> S 6.7.3.
> >   
> >      A baseline ACP node MUST support IPsec natively and MAY support IPsec
> >      via GRE.  A constrained ACP node that can not support IPsec MUST
> >      support DTLS.  An ACP node connecting an area of constrained ACP
> >      nodes with an area of baseline ACP nodes MUST therefore support IPsec
> >      and DTLS and supports threefore the baseline and constrained profile.
> 
> These MTIs do not provide interop between constrained and baseline
> nodes, because a baseline node might do IPsec and the constrained node
> DTLS.

Yes. 6.5.  Channel Selection:

I improved the text of this paragraph also for this review (example
was not as strong in before):

<t>Not all type of ACP nodes can or need to connect directly to each other or are able to support or prefer all possible secure channel mechanisms.  For example, code space limited IoT devices may only support DTLS because that code exists already on them for end-to-end security, but high-end core routers may not want to support DTLS because they can perform IPsec in accelerated hardware but would need to support DTLS in an underpowered CPU forwarding path shared with critical control plane operations. This is not a deployment issue for a single ACP across these type of nodes as long as there are also appropriate gateway ACP nodes that support sufficiently many secure channel mechanisms to allow interconnecting areas of ACP nodes with a more constrained set of secure channel protocols. On the edge between IoT areas and high-end core networks, general-purpose routers that act as those gateways and that can support a variety of secure channel protocols is the norm already.</t>

Aka: there is no MTI and no need for an MTI because we don't need end-to-end
security for ACP secure channels but only hop-by-hop,  and we define
different profiles in "ACP Secure Channel Requirements" (6.7.3)

> S 6.10.2.
> >         hash of the routing subdomain SHOULD NOT be assumed by any ACP
> >         node during normal operations.  The hash function is only executed
> >         during the creation of the certificate.  If BRSKI is used then the
> >         BRSKI registrar will create the domain information field in
> >         response to the EST Certificate Signing Request (CSR) Attribute
> >         Request message by the pledge.
> 
> you need to lay out the security assumptions here. It's not difficult
> to create a new domain with the same 40bit hash.

If you don't attempt to do this, the chance for this to happen is a lot
lower than winning the lottery, so it would have to be a suicidal operator.

Prepended before that paragraph:

| When creating a new routing-subdomain for an existing autonomic network,
| it MUST be ensured, that rsub is selected so the resulting hash of the
| routing-subdomain does not collide with the hash of any pre-existing
| routing-subdomains of the autonomic network. This ensures that ACP
| addresses created by registrars for different routing subdomains do not
| collide with each others.

And appended after that paragraph:

| Establishing connectivity between different autonomic networks
| (different acp-domain-name) is outside the scope of this specification.
| If it is being done through future extensions, then the rsub of all
| routing-subdomains across those autonomic networks need to be selected
| so their hashes do not collide. For example a large cooperation with its
| own private Trust Anchor may want to create different autonomic networks
| that initially should not be able to connect but where the option to do
| so should be kept open. When taking this future possibility into account,
| it is easy to always select rsub so that no collisions happen.</t>

> If you have a private
> CA, this probably isn't an issue, but if you are sharing a public CA,
> it would allow me to produce a domain with other people's addresses.

The following is the pre-existing text from 6.1.3 intended
to cover this:

   Trust Points for ACP domain certificates must be trusted to sign
   certificates with valid ACP domain information fields only for
   trusted ACP registrars of that domain.  This can be achieved by using
   Trust Anchors private to the owner of the ACP domain or potentially
   through appropriate contractual agreements between the involved
   parties.  Public CA without such obligations and guarantees can not
   be used.

   A single owner can operate multiple independent ACP domains from the
   same set of private trust anchors (CAs).  When the ACP Registrars are
   trusted not to permit certificates with incorrect ACP information
   fields to be signed. ...

Let me know if you think more elaboration is required.

> S 8.1.1.
> >      configured to be put into the ACP VRF.  The ACP is then accessible to
> >      other (NOC) systems on such an interface without those systems having
> >      to support any ACP discovery or ACP channel setup.  This is also
> >      called "native" access to the ACP because to those (NOC) systems the
> >      interface looks like a normal network interface (without any
> >      encryption/novel-signaling).
> 
> This seems pretty unclear. Is the idea that you connect natively to
> the ACP Connect node and then it forwards your packets over the ACP?

Yes. No secure channel used, needs to be explicitly configured. Expects
appropriate physical security. Limited to one L3 subnet hop, so typically
an ACP edge node co-located via an ethernet cable to e.g.: an SDN
controller in a room with physcial access control.

> Does that mean they need to be GRASP or whatever? I think that's what
> you are saying below.

ACP has two type of GRASP instances, ACP grasp and secure channel
autoconfig DULL GRASP.

ACP GRASP runs over those interfaces like it runs over ACP interfaces
constructed across secure channels. But there is no DULL GRASP neighbor
discovery, as thats only needed to construct ACP secure channels.

Not sure how to improve text to make it easier readable. Suggestions welcome.

> S 8.1.5.
> >      interface is physically protected from attacks and that the connected
> >      Software or NMS Hosts are equally trusted as that on other ACP nodes.
> >      ACP edge nodes SHOULD have options to filter GRASP messages in and
> >      out of ACP connect interfaces (permit/deny) and MAY have more fine-
> >      grained filtering (e.g., based on IPv6 address of originator or
> >      objective).
> 
> Given that this is an important security requirement, it seems like it
> should be a normative requirement that it be filtered.

This is not a security requirement but an administrative policy filtering
requirement. You assume the servers you allow to connect to an ACP connect
network to be trusted. They may just not provide flexible filtering of
the services they offer so the network device can add that through above
mentioned policy filtering of the GRASP announcements.

> S 9.1.
> >      same trust anchor, a re-merge will be smooth.
> >   
> >      Merging two networks with different trust anchors requires the trust
> >      anchors to mutually trust each other (for example, by cross-signing).
> >      As long as the domain names are different, the addressing will not
> >      overlap (see Section 6.10).
> 
> Why does it require the *trust anchors* to trust each other? Can't the
> endpoints just have the union of the trust anchors.
> 
> This is way underspecified for actual implementation.

Yepp. goes back to version 6 of the doc, before i started to refine the text
from a more declarative to a more implementable level of detail. Overlooked
so far by me when i started write down all the PKI details. Replaced with:

| Merging two networks with different trust anchors requires the ACP nodes
| to trust the union of Trust Anchors.  As long as the routing-subdomain
| hashes are different, the addressing will not overlap (see <xref target="addressing"/>).
| Note that the complete mechanisms to merge networks is out of scope of
| this specification.

Btw: this is already the start of informative text again (post normative).

> S 10.2.1.
> >      registrar can rely on the ACP and use Proxies to reach the candidate
> >      ACP node, therefore allowing minimum pre-existing (auto-)configured
> >      network services on the candidate ACP node.  BRSKI defines the BRSKI
> >      proxy, a design that can be adopted for various protocols that
> >      Pledges/candidate ACP nodes could want to use, for example BRSKI over
> >      CoAP (Constrained Application Protocol), or proxying of Netconf.
> 
> I am finding it very difficult to work out the security properties of
> this mechanism and the security considerations do not help. What can a
> malicious registrar do? For that matter, you say "uncoordinated", so
> does that mean anyone in the ACP can just decide to be a registrar?

The uncoordinated refers to the fact that each ACP registrar creates the
ACP domain informatin field, thereby assigning an ACP address to a pledge
for which it enrolls the certificate. The ACP addressing schemes are designed
so that each ACP registrar can do this without having to coordinate with
other ACP registrars or another central entity. Therefore the only central
entity required is some hopefully pre-existing, PKI CA/sub-CA infra that
doesn't have to know about ACP specifics at all.

This section is already informal, and in a presentation i tried to show
how even a person could be a registrar, aka: no formal need of ACP for
it to be software. Hence the very protocol unspecific definition.

I added the following paragraph to the end of 6.10.7(.0) which is the normative
part for ACP registrar to hopefully answer the security question sufficiently:

| ACP registrars are PKI registration authorities (RA) enhanced with
| the handling of the ACP domain certificate specific fields. They
| request certificates for ACP nodes from a Certificate Authority
| through any appropriate mechanism (out of scope in this document,
| but required to be BRSKI for ANI registrars). Only nodes that
| are trusted to be compliant with the requirements against registrar
| described in this section must be given the necessary credentials
| to perform this RA function, such as credentials for the BRSKI
| connection to the CA for ANI registrars.

And to Security considerations:

| Every ACP registrar is criticial infrastructure that needs to be hardened against attacks similar to a CA. A malicious registrar can enroll enemy plegdes to an ACP network or break ACP routing by duplicate ACP address assignment to pledges via their ACP domain certificates.

> S 11.
> >   
> >   11.  Security Considerations
> >   
> >      An ACP is self-protecting and there is no need to apply configuration
> >      to make it secure.  Its security therefore does not depend on
> >      configuration.
> 
> This is not true. You need to configure the trust anchor and the
> domain name.

Changed to:

| After seeding an ACP by configuring at least one ACP registrar with routing-subdomain and a CA, an ACP is self-protecting and there is no need to apply configuration to make it secure (typically the ACP Registrar doubles as EST server for certificate renewal).

Originally the idea was to consider ACP registrar/EST server part of the BRSKI effort in ANIMA, hence the simpler original statement. But it turned out to be illogical to describe all the ACP specifics of ACP registrars in BRSKI if we wanted to make it reuseable without ACP.

> S 11.
> >         all products.
> >   
> >      There is no prevention of source-address spoofing inside the ACP.
> >      This implies that if an attacker gains access to the ACP, it can
> >      spoof all addresses inside the ACP and fake messages from any other
> >      node.
> 
> You need to be clear that the security is just group security and that
> any compromised ACP node compromises the entire system.

Right. Ben had more points about the insufficiency of the security considerations
text, so i expanded the point here with several paragraphs.

A bit too long to paste here. Starts and ends with the follwing, easy to see in rfcdiff:

| The ACP It is designed to enable automation of current network management and future autonomic peer-peer/distributed network automation. ...
...
| Higher layer service built using ACP domain certificates should not solely rely on undifferentiated group security....

> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> S 1.
> >      possibilities that where considered not to be appropriate for
> >      standardization in this document but were considered important to
> >      document.
> >   
> >      The ACP provides secure IPv6 connectivity, therefore it can not only
> >      be used as the secure connectivity for self-management as required
> 
> Nit: this would be clearer as "can be used not only"

Thanks.

> S 2.
> >         equally be used in simple ANI networks (with no other Autonomic
> >         Functions) or completely by itself.
> >   
> >      ACP address:  An IPv6 address assigned to the ACP node.  It is stored
> >         in the domain information field of the ->"ACP domain certificate"
> >         ().
> 
> Something wrong here.

See note on top of Section 2 introduced in -17, its about the XML
xref's. If RFC-editor can't help, we'll fix manually (reference containing () ).

> S 2.
> >   
> >      domain information (field):  An rfc822Name information element (e.g.,
> >         field) in the domain certificate in which the ACP relevant
> >         information is encoded: the domain name and the ACP address.
> >   
> >      ACP Loopback interface:  The Loopback interface in the ACP VRF that
> 
> Please expand VRF on first use.

Done (pre -19).

> S 2.
> >         routing and forwarding in the node other than the ACP VRF.  In a
> >         simple ACP or ANI node, the Data-Plane is typically provisioned
> >         non-autonomic, for example manually (including across the ACP) or
> >         via SDN controllers.  In a fully Autonomic Network node, the Data-
> >         Plane is managed autonomically via Autonomic Functions and Intent.
> >         Note that other (non-ANIMA) RFC use the Data-Plane to refer to
> 
> Nit: RFCs

Done.

> S 4.
> >             protocols of the ANI.  Clients of the ACP MUST NOT be tied to
> >             a particular application or transport protocol.
> >   
> >      ACP5:  The ACP MUST provide security: Messages coming through the ACP
> >             MUST be authenticated to be from a trusted node, and SHOULD
> >             (very strong SHOULD) be encrypted.
> 
> Why isn't this a MUST? Once you have done the key setup, the
> encryption is very cheap.

This is the section describing the input requirements into the specification
of the ACP (charter didn't allow a separate requirements document). It is
 not the actual normative requirement for the ACP described in section 6 (there
it is a MUST for encryption).

Various reasons for customers not wanting encryption: regulation (e.g.: finance networks
auditing), inability to support HW enryption at speeds/cost-point needed (e.g.:
data-center).  Hop-by-hop encryption to protect infrastructure is something completely
different from end-to-end encryption wrt. cost. We don't even have a good idea
how much performance for transit traffic we need across ACP nodes. if yo want to
build across the ACP more intelligent network automation you may want to pull a lot
of telemetry across it.

Alas, we had to conclude that for the start it would be too much work to
include all necessary work to make those requirements work, so this base
ACP specification has the MUST in the normative part. Solutions for different
markets for whom this is not appropriate would be different anyhow. Finance
regulations could result in networks effectively uses message integrity but
not encryption, whereas DC might use a lower security model.. 

> S 4.
> >      between nodes, but only GRASP connectivity.  Nevertheless, because
> >      ACP also intends to support non-AN networks, it it is crucial to
> >      support IPv6 layer connectivity across the ACP to support any
> >      transport and application layer protocols.
> >   
> >      Th eACP operates hop-by-hop, because this interaction can be built on
> 
> Nit: The ACP

Done.

> S 6.1.1.
> >      hash collisions.  If the operator does not own any FQDN, it should
> >      choose a string (in FQDN format) that intends to be equally unique.
> >   
> >      "routing-subdomain" is the autonomic subdomain that is used to
> >      calculate the hash for the ULA Global ID of the ACP address of the
> >      node.  "rsub" is optional; its syntax is defined in this document,
> 
> This section about the hash isn't clear without referencing some
> future section.

Added reference to section defining the use of ULA (addressing section).

> S 6.1.1.
> >      In this specification, the "acp-address" field is REQUIRED, but
> >      future variations (see Appendix A.8) may use local information to
> >      derive the ACP address.  In this case, "acp-address" could be empty.
> >      Such a variation would be indicated by an appropriate "extension".
> >      If "acp-address" is empty, and "rsub" is empty too, the "local-part"
> >      will have the format "rfcSELF + + extension(s)".  The two plus
> 
> Are these spaces part of local-part? They appear to be forbidden by
> the ABNF

No, spaces where just meant for visualization, but obviously confusing. Removed spaces.

> S 6.1.1.
> >      The subjectAltName / rfc822Name encoding of the ACP domain name and
> >      ACP address is used for the following reasons:
> >   
> >      o  It should be possible to share the LDevID with other uses beside
> >         the ACP.  Therefore, the information element required for the ACP
> >         should be encoded so that it minimizes the possibility of creating
> 
> Is this really not normative?

No. We can not use the ACP spec to force any non-ACP function on a router to
share the ACP certificate. We can just design the ACP certificate content so
that it would not conflict with the content required for other uses and hope that
this eliminates an important limiter to minimizing the number of redundant
certificates a router needs to maintain across various functions.

(If there are good reasons for different certs, they are not "redundant" ;-)

> S 6.1.3.5.
> >      protocols used by the ACP registrars.
> >   
> >      Please refer to Section 6.10.7 for explanations about ACP registrars
> >      and vouchers as used in the following text.
> >   
> >      When BRSKI is used (aka: on ACP nodes that are ANI nodes), the re-
> 
> I think you mean "i.e.", not "aka".

Thanks.

> S 6.1.3.5.
> >      certificate or the IDevID, the re-enrolling candidate ACP node SHOULD
> >      authenticate the BRSKI registrar during TLS connection setup based on
> >      its existing trust anchor/certificate chain information associated
> >      with its old ACP certificate.  The re-enrolling candidate ACP node
> >      SHOULD only request a voucher from the BRSKI registrar when this
> >      authentication fails during TLS connection setup.
> 
> This is all pretty hard to understand without having read BRSKI

Updated lead in text to say:

<t>Please refer to <xref target="acp-registrars"/> and <xref target="I-D.ietf-anima-bootstrapping-keyinfra"/>
for explanations about ACP registrars and vouchers as used in the following text.
When ACP is intended to be used without BRSKI, the details about BRSKI and
vouchers in the following text can be skipped.</t>

> S 6.1.3.6.
> >   
> >      An ACP domain certificate is called failing in this document, if/when
> >      the ACP node can determine that it was revoked (or explicitly not
> >      renewed), or in the absence of such explicit local diagnostics, when
> >      the ACP node fails to connect to other ACP nodes in the same ACP
> >      domain using its ACP certificate.  For connection failures to
> 
> I don't understand the thing on the other side of this "or". I'm
> supposed to conclude based on some remote diagnostic that my cert is
> bad>

This is primarily a definition, independent of who makes the assertion.
Could be the node itself, could be a registrar

Depends on capabilities of secure channel protocols, the node may be able
to self-diagnose. For example if the secure channel protocol allows to
authenticate the peer as a valid domain peer but the connection setup
still fails because the peer does not accout our certificate.

Isn't there also in some secure channel mechanism a way to receive revocation
lists ? That would be an explicit way to learn our certificate has failed
(revocation is a failure).

> S 6.1.3.6.
> >      or any of its signing certificates could have been revoked or may
> >      have expired, but the ACP node can not self-diagnose this condition
> >      directly.  Revocation information or clock synchronization may only
> >      be available across the ACP, but the ACP node can not build ACP
> >      secure channels because ACP peers reject the ACP node's domain
> >      certificate.
> 
> Is the idea here that I'm supposed to inspect the TLS alerts?

Secure channels considered right now are IPsec and DTLS. I don't even know
what TLS alerts provide, but if they are supported via DTLS and provide
useful diagnosis for this condition, it might be useful to mention.
Any pointer to what a TLS alert can tell me ?

> S 6.3.
> >      dependencies, including ACP.  Please ensure that references to I-
> >      D.ietf-anima-grasp that include section number references (throughout
> >      this document) will be updated in case any last-minute changes in
> >      GRASP would make those section references change.
> >   
> >      DULL GRASP is a limited subset of GRASP intended to operate across an
> 
> Please expand DULL

Done.

> S 6.4.
> >   
> >      o  ACP connections across domains with different Certificate
> >         Authorities (CA) could establish a common ACP by installing the
> >         alternate domains' CA into the trusted anchor store.  This is an
> >         executive management action that could easily be accomplished
> >         through the control channel created by the ACP.
> 
> How would you know if other domains had a given CA?

This future intent stuff was moved into A.8 by Alissa's review.  Says for example:

<t>If each domain has its own source of Intent, then the Intent would simply have to
allow adding the peer domains trust anchors (CA) and domain names to the ACP domain membership check
(<xref target="certcheck"/>) so that nodes from those other domains are accepted as ACP peers.</t>

Aka: inject the other domains info into network wide intent. Which we haven't defined. Hence A.8.
(not really difficult to do though, we have a draft for Intent distribution).

> 
> S 6.5.
> >      version 1.2", see [RFC6347]) because that code exists already on them
> >      for end-to-end security, but low-end in-ceiling L2 switches may only
> >      want to support Media Access Control Security (MacSec, see 802.1AE
> >      ([MACSEC]) because that is also supported in their chips.  Only a
> >      flexible gateway device may need to support both of these mechanisms
> >      and potentially more.
> 
> Why are you mentioning MACSEC? Your negotiation syntax doesn't support
> it.

Added:

Note that MacSec is not required by any profiles of the ACP in this specification but just mentioned as a likely next interesting secure channel protocol.

(MacSec might be the only encryption we could get into data centers ;-)

> S 6.5.
> >      version 2", see [RFC7296].  It is now up to Alice to decide how to
> >      proceed.  Even if the IPsec connection from Bob succeeded, Alice
> >      might prefer another secure protocol over IPsec (e.g., FOOBAR), and
> >      try to set that up with Bob.  If that preference of Alice succeeds,
> >      she would close the IPsec connection.  If no better protocol attempt
> >      succeeds, she would keep the IPsec connection.
> 
> When would you get partial failrues?

The text does not mention partial failures. Can you please rephrase your question ?

> S 6.7.1.2.
> >      support IPsec transport mode with next protocol equal to GRE (47)
> >      followed by the offer for native IPsec as described above (because
> >      that option is mandatory to support).
> >   
> >      If IKEv2 initiator and responder support GRE, it will be selected.
> >      The version of GRE to be used must the according to [RFC7676].
> 
> See above interop comments.

See above answer to above interop comment.

> S 6.7.3.
> >      An ACP secure channel MUST immediately be terminated when the
> >      lifetime of any certificate in the chain used to authenticate the
> >      neighbor expires or becomes revoked.  Note that this is not standard
> >      behavior in secure channel protocols such as IPsec because the
> >      certificate authentication only influences the setup of the secure
> >      channel in these protocols.
> 
> How does this interact with reissue? I am supposed to reconnect?

Yes. I have actually not managed to insight into whether we can maintain
an IPsec connection without interrupting its data-plane when one of
the peers has to renew its certificate (is that what you call reissue ?).

I hope this is possible, otherwise we have to reconsider how strong we want to
make the termination of secure channels. If i wanted to build an ACP
with short-term certificates valid for 30 minutes and effectively
get renewed every 20 minutes, i do not want to have interruption of ACP secure
channels every 20 minutes.

> 
> S 6.8.2.
> >           Figure 7: ACP as security and transport substrate for GRASP
> >   
> >      GRASP unicast messages inside the ACP always use the ACP address.
> >      Link-local ACP addresses must not be used inside objectives.  GRASP
> >      unicast messages inside the ACP are transported via TLS 1.2
> >      ([RFC5246]) connections with AES256 encryption and SHA256.  Mutual
> 
> Again, why AES256/SHA256?

Longest key length we now to be widely supported in HW. Changed to AES-256-GCM.

Any better recommendations welcome.

> S 6.8.2.1.
> >      original objective in GRASP when it is a MITM and act as an
> >      application level proxy.  This of course requires that the
> >      compromised ACP node understand the semantics of the GRASP
> >      negotiation to an extent that allows it to proxy it without being
> >      detected, but in an ACP environment this is quite likely public
> >      knowledge or even standardized.
> 
> Just to make sure I'm clear: you would know you were talking to A and
> not B (because the certificate) so that would be of some use, right?

TLS avoids easy MITM active attacks. It does not eliminate complex
MITM acive attacks if your communication does not have a specific known
identity of the peer (such as a domain name where the certificate validates
the domain). Or another mean to distinguish it from an imposter.

 The original autonomic networking goal is that any node could
start any type of service, and the client just connects to a node offering
the service. In such an application environment, an onpath compromised
node could not only take over the role of a service provider but also
do MITM between two other nodes.

My brain hurts trying to figure out an example where the compromised node
would actually create more havoc by being such a MITM instead of just
being an imposter of a service provided or service consumed ;-)

Luckily these are questions to the next layer of services on top of te
ACP. Here we just wanted to describe what the ACP (including ACP GRASP)
infra can and what it can not provide.

> S 6.8.2.1.
> >      encryption.  Future work optimizations could avoid this but it is
> >      unclear how beneficial/feasible this is:
> >   
> >      o  The security considerations for GRASP change against attacks from
> >         non-ACP (e.g., "outside") nodes: TLS is subject to reset attacks
> >         while secure channel protocols may be not (e.g., IPsec is not).
> 
> I don't think the distinction here is between "secure channel" and
> "TLS"; usually I would call TLS a secure channel protocol. Maybe
> "secure transport" or "L3"?
> 
> Note that QUIC would not have this problem.

How about TLS 1.3 ?

> S 6.12.5.
> >      the same.  The difference happens when Bob and Carol receive their
> >      packet.  If they use ACP point-to-point virtual interfaces, their
> >      GRASP instance would forward the packet from Alice to each other as
> >      part of the GRASP flooding procedure.  These packets are unnecessary
> >      and would be discarded by GRASP on receipt as duplicates (by use of
> >      the GRASP Session ID).  If Bob and Charly's ACP would emulate a
> 
> Charly? Do you mean Carol?

Fixed by Bens review.

> S 7.1.
> >      create ACP point-to-point virtual interfaces for these secure
> >      channels.
> >   
> >   7.  ACP support on L2 switches/ports (Normative)
> >   
> >   7.1.  Why
> 
> This hed could be better.

Changed to: Why (Benefits of ACP on L2 switches)

> S 8.1.1.
> >      explicit configuration.  To support connections to adjacent non-ACP
> >      nodes, an ACP node must support "ACP connect" (sometimes also called
> >      "autonomic connect"):
> >   
> >      "ACP connect" is a function on an autonomic node that is called an
> >      "ACP edge node".  With "ACP connect", interfaces on the node can be
> 
> This sentence is confusing.  Perhaps first explain what an edge node
> is and then say ACP connect is a function of it.

Changed to:

"ACP connect" is an interfacel level configured workaround for connection of trusted non-ACP nodes to the ACP. The ACP node on which ACP connect is configured is called an "ACP edge node". With ACP connect, the ACP is accessible from those non-ACP nodes (such as NOC systems) on such an interface without those non-ACP nodes having to support any ACP discovery or ACP channel setup.

> S 8.1.2.
> >      only even more trusted software components will get access to both
> >      the ACP virtual subnet and the Data-Plane (because those ACP users
> >      could leak traffic between ACP and Data-Plane).  This trust could be
> >      established for example through cryptographic means such signed
> >      software packages.  The specification of these mechanisms is subject
> >      to future work.
> 
> This all seems pretty handwavingly speculative. I would remove it

Why ? This is going on everywhere already inside data centers for example
in reorchestrated service provider pops where instead of plugging together
physical systems, VNF/NFV are orchestrated into trusted software based
network infrastructure. You're replacing the people operator verifying the
integrity/authenticity of physcial components with a software system doing the same.

> S 8.1.4.
> >      legacy NMS Hosts that support only one IP interface.
> >   
> >      To provide a single subnet into both ACP and Data-Plane, the ACP Edge
> >      node needs to de-multiplex packets from NMS hosts into ACP VRF and
> >      Data-Plane.  This is sometimes called "VRF select".  If the ACP VRF
> >      has no overlapping IPv6 addresses with the Data-Plane (as it should),
> 
> Does this mean it should have no overlapping addresses or it should
> have overlapping addresses? The text here is kind of unclear though I
> believe from context it is "should have no"

Replaced with "it should have no overlapping addresses"

> S 9.2.2.
> >      under attack.
> >   
> >   9.2.2.  From the inside
> >   
> >      The security model of the ACP is based on trusting all members of the
> >      group of nodes that do receive an ACP domain certificate for the same
> 
> Nit: "receive", not "do receive"

Thanks

> S 10.2.3.
> >      Even when such a malicious ACP registrar is detected, resolving the
> >      problem may be difficult because it would require identifying all the
> >      wrong ACP domain certificates assigned via the ACP registrar after it
> >      was was compromised.  And without additional centralized tracking of
> >      assigned certificates there is no way to do this - assuming one can
> >      not retrieve this information from the .
> 
> from the .?

vi fumble. remove from " - assuming".

> S 10.2.4.
> >      In situations, where either of the above two limitations are an
> >      issue, ACP registrars could also be sub-CAs.  This removes the need
> >      for connectivity to a root-CA whenever an ACP node is enrolled, and
> >      reduces the need for connectivity of such an ACP registrar to a root-
> >      CA to only those times when it needs to renew its own certificate.
> >      The ACP registrar would also now use its own (sub-CA) certificate to
> 
> When you say "sub CA" do you mean "intermediate"?

I hope i am not fumbling on terminology. In the example given we only
need a chain of two CA, a root CA and another CA below it. I have most
often heard the term sub-CA used to describe this. I hope the description
applies more generically to any chain of two CA even if the actual hierarchy
is longer, therefore i didn't use "assigning CA", which is what i heard
to be the term for the leaf CA.

"intermediate" sounds as if one is talking about at least three tiers of CA.

Happy to take guidance if the termins to use should be improved.

> S 10.3.2.1.
> >      provides also a high level of security because it only permits ACP/
> >      ANI operations which are both well secured.  Ultimately, it is
> >      subject to security review for the deployment whether "admin down" is
> >      a feasible replacement for "physical down".
> >   
> >      The need to trust into the security of ACP/ANI operations need to be
> 
> "trust into" is not grammatical

Removed "into"

> S 10.3.4.
> >      whether or not to set "ACP/ANI enable".
> >   
> >      The goal of automatically setting "ACP/ANI enable" on interfaces
> >      (native or not) is to eliminate unnecessary "touches" to the node to
> >      make its operation as much as possible "zero-touch" with respect to
> >      ACP/ANI.  If there are "unavoidable touches" such a creating/
> 
> such as

Thanks

> S 10.3.5.
> >      parameters on SIM card shipped to remote location), then the default
> >      should be to enable ACP/ANI.
> >   
> >   10.3.5.  Node Level ACP/ANI enable
> >   
> >      A node level command "ACP/ANI enable [up-if-only]" enables ACP or ANI
> 
> I got lost here. In what context does this command exist?

"node level" (Cisco IOS calls this "global configuration mode").

> S 10.3.5.1.
> >   
> >      Automatically setting "ANI enable" on brownfield nodes where the
> >      operator is unaware of it could also be a critical security issue
> >      depending on the vouchers used by BRKSI on these nodes.  An attacker
> >      could claim to be the owner of these devices and create an ACP that
> >      the attacker has access/control over.  In network where the operator
> 
> "In networks"

Gracias.

> S 10.3.6.
> >   
> >      Disabling ANI/ACP by undoing "ACP/ANI enable" is a risk for the
> >      reliable operations of the ACP if it can be executed by mistake or
> >      unauthorized.  This behavior could be influenced through some
> >      additional property in the certificate (e.g., in the domain
> >      information extension field) subject to future work: In an ANI
> 
> This also seems handwavy.

I disagree. Encoding desired operational parameters into the certificates
is a simple to understand concept. In this case its a binary flag.

The problem is mostly how far we want to drive (ab)-using the certificate
as a carrier for configuration (which the ACP domain information field really
is). Theoretical the answer is simple: Only for config you really can't do
via other configuration mechanisms available after enrolment.
And for this particular functionality i am not 100% sure how to judge it.

> S 15.2.
> >      because it is not quite clear yet what exactly the implications are
> >      to make GRASP flooding depend on RPL DODAG convergence and how
> >      difficult it would be to let GRASP flooding access the DODAG
> >      information.
> >   
> >   A.6.  Extending ACP channel negotiation (via GRASP)
> 
> This section seems like it's entirely speculative. I recommend
> removing it.

This was for aforementioned dual stage secure channel negotiation. Given
how it came up in this discussion, i am curious to learn what you think
abou this option compared to the mechanism we have specified not in the
standards text. If there are simple reasons to rule out this type
of dual stage negotiation being useful in the future, i am happy to
remove, otherwise i would love to not loose the cycles invested into the
text (if we ever would want to finish it).

> That said, I don't really understand the rationale for multiple
> concurrent security protocols. If you have clear UDP on the network
> (and you must or none of this works), then you can do DTLS and IKEv2,
> so you should be able to have one side decide which to negotiate and
> negotiate that. Why does this not work?

Are you saying i would use a dual stage mechanism, where the first
stage is clear text ? The problem with that is that that UDP protocol
is additional attack surface. Thats why my initial proposal was this
dual-stage secure negotiation. But as mentioned initially, the first
stage becomes the lowest common denominator.

> S 15.2.
> >   
> >      If multiple independent networks choose the same domain name but had
> >      their own CA, these would not form a single ACP domain because of CA
> >      mismatch.  Therefore there is no problem in choosing domain names
> >      that are potentially also used by others.  Nevertheless it is highly
> >      recommended to use domain names that one can have high probability to
> 
> Are these normative?

Strange how you seem to be listing these under a section 15.2.

This text is in -16 from appendix A.7, so Informative (all of appendix).

> S 15.2.
> >      If different domains have different CAs, they should start to trust
> >      each other by intent injected into both domains that would add the
> >      other domains CA as a trust point during the ACP connection setup -
> >      and then following up with the previous point of inter-domain
> >      connections across domains with the same CA (e.g., GRASP
> >      negotiation).
> 
> This all seems speculative (and hard to analyze at this state of
> handwaving). I suggest removal.

The purpose of appendix A is to capture in an informative fashion the status
of the work that the WG invested solving problems we would have liked to solve (or
that the WG was very interested in discussing) - but which did not result
in output that allowed normative specification.

In the case of exchanging trust anchors/domain-names i think this is really
not difficult to finish: You need to be have roles in certs indicating specific
ACP nodes (like registrars) are trusted intent originators, then you sign a
piece of configuration in whatever format you like (YANG+transport encoding)
with such a cert, flood it via ACP/GRASP (we have draft for that), and
e voila extended trust anchors/permissible ACP domain names. 

> S 15.2.
> >      other domains CA as a trust point during the ACP connection setup -
> >      and then following up with the previous point of inter-domain
> >      connections across domains with the same CA (e.g., GRASP
> >      negotiation).
> >   
> >   A.8.  Adopting ACP concepts for other environments
> 
> I would also remove this appendix.

There was interest from multiple WG members to have these explanations written
and included in the output of the WG. 

Just as a reminder: While the ADs seeding the ANIMA WG where very much focussed
in producing standards track output to create immediate product applicability,
 ANIMA is still an OPS WG and hence discussings about applicability to market segments
sould be a core interest of work output, and the ACP as specified in this specification,
as good as it is, can not yet make all market segments happy, but future work with
in comparison limited modifications could expand the ACP applicability. At least
that is our hope that we try to express in this section.

Thank you so much for your thorough review!


From nobody Mon Mar 11 08:32:41 2019
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 565CE13117D; Mon, 11 Mar 2019 08:32:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.801
X-Spam-Level: 
X-Spam-Status: No, score=0.801 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_SUMOF=5, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 5SnbMc6ROKPZ; Mon, 11 Mar 2019 08:32:22 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09A84131151; Mon, 11 Mar 2019 08:32:22 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 76E01548342; Mon, 11 Mar 2019 16:32:14 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 71515440036; Mon, 11 Mar 2019 16:32:14 +0100 (CET)
Date: Mon, 11 Mar 2019 16:32:14 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, draft-ietf-anima-autonomic-control-plane@ietf.org, Sheng Jiang <jiangsheng@huawei.com>, anima-chairs@ietf.org, anima@ietf.org
Message-ID: <20190311153214.c3l62vqgniuqllsf@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <153316981032.22048.6996271018423269893.idtracker@ietfa.amsl.com>
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/ccaIV7GX5m2JAqpV8f4EI4Sh6AY>
Subject: Re: [Anima] Benjamin Kaduk's Discuss on draft-ietf-anima-autonomic-control-plane-16: (with DISCUSS and COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Mar 2019 15:32:34 -0000

Thanks Benjamin,

This file is: https://github.com/anima-wg/autonomic-control-plane/blob/master/draft-ietf-anima-autonomic-control-plane/16-ben-kaduk-reply.txt

The following inline answers to your discuss have been integrated
into -19 of the draft which i just submitted. It also includes the
feedback to the comments by Eric and Ben. I was backlogged, and
after your review of -16 i had first responded to other reviewers
with -16/-17.

Note that this includes a hopefully more comprehensive section 6.1.3 explaining the Trust Anchor details required for the ACP, resulting from the variety of discuss of the reviewers on this topic.

Bens and Erics review where very good and comprehensive but alas
didn't make it easy for me to answer to them as quickly as i would have
wanted to. Unfortunately, i also had to go back and forth between
them, so i couldn't create a separate checkpoint version
showing ONLY changes for each of them. So the following diffs are
hopefully useful:

-18 to -19: Changes made for Ben and Eric

http://tools.ietf.org//rfcdiff?url1=https://tools.ietf.org/id/draft-ietf-anima-autonomic-control-plane-18.txt&url2=https://tools.ietf.org/id/draft-ietf-anima-autonomic-control-plane-19.txt

-16 to -19: Changes since your last review (includes Alissa Coopers review)

http://tools.ietf.org//rfcdiff?url1=https://tools.ietf.org/id/draft-ietf-anima-autonomic-control-plane-16.txt&url2=https://tools.ietf.org/id/draft-ietf-anima-autonomic-control-plane-19.txt

Cheers
    Toerless

On Wed, Aug 01, 2018 at 05:30:10PM -0700, Benjamin Kaduk wrote:
> Benjamin Kaduk has entered the following ballot position for
> draft-ietf-anima-autonomic-control-plane-16: Discuss
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-anima-autonomic-control-plane/
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> This is a really exciting protocol to read about -- the prospect of
> dropping a bunch of just-manufactured devices in place, spinning up a
> registrar (and maybe a MASA), and getting a control plane like magic is
> pretty impressive.

Thanks ;-)

>   That said, I don't believe that this document is ready
> to publish as-is.  I have a list of specific points below for discussion,
> but it may be more effective to strip down the document a lot (providing a
> well-defined core protocol and leaving out speculative future work, along
> the lines of Alissa's comments) and only then start to work on specific
> rough spots.

Thanks. I hope that the fixes to the document done in response to you
and other reviewers feedback will satisfy you.

Let me give you some IMHO good technical arguments for the necessity of
the size of the document. there are also other charter and process arguments
but maybe better taken offline to explain. 

- You review was for -16 for -17/18, document already restructured
  all speculative text into appendix A. All text in A is not unsolicited
  but results of discuss/questions in the WG for this doc. 

- Section 10 (operations) is IMHO mandatory to be main text. ANIMA is an OPS
  group, and overall about operational simplification, so the node-local
  behavior is crucial to achieve this. Not only the interop affecting aspects
  (normative sections). IMHO, this section is not speculative.

- Stripping down the document further would create an incomplete,
  and IMHO  undeployable solution.

- The doc grew in the last 5..6 version by inheriting more text from what
  ACP authors originally considered to be part o BRSKI document, but it turned
  out to be logically better for ACP (as it's not needed in BRSKI only deployment
  without ACP). In hindishgt we should have started with more documents to
  split up the work (see comments on charter). IMHO too late now.

> In particular, in its current form, it's not clear to me why this document
> is targeting the standards-track -- there are lots of places where
> determinations of what works best or how to do some things is left for
> future work.

Futures in the normative text where only mentioned in few places IMHO.
I did another pass through the document attempting to eliminate all mentions
of futures from the normative text and most of the operational section 10.
If future is mentioned in the normative text, it is to explicitly
point out planned points of extensibility required to kepp backward compatibility.
GRASP objectives, "ext" ACP information field and the like. I think this is
standard IETF standard practice (like "reserved" fields in other protocols).
The choice of the word "future" to explain those extensibility interfaces
actually made it easy to find them in the text...

So, IMHO, all the functionality written into the normative parts as of -19
are really mandatory to support the best understood deployment scenarios well.

> Are there lots of implementations or consumers clamoring for
> this stuff that it makes sense to go for PS as opposed to Experimental (so
> as to figure out what works and nail down a slimmer protocol for the
> standards track)?

I definitely have worked with a quite a few number of customers
interested in this technology and using pre-standards versions of it,
asking for it to be standardized. As mentioned before, i also don't
think there are optoinal pieces in the normative part that are experimental
and not well enough understood from implementation/deployment experience.

This is really mostly a a way to stitch together well known techniques and
protocols (secure connections, separate VRF across a network, certificate
management) and easily automated IPv6 addressing schemes. Add a fairly
small standard track target negotion protocol (GRASP).

Alas, there is a good amount of complexity in stitching these pieces together
so everything becomes self-configuring and secure. 

> I see in A.4 that the choice of RPL was motivated by
> experience with a pre-standard version of ACP; it would have been great to
> hear more about those deployments in an Implementation Status section (per
> RFC 7942) or the Shepherd writeup.

Yes. There is a lot of experience gained from pre-standard vendor production code
running in customer networks, only modified/enhanced in places
where the authors of the ACP draft and/or the WG felt that that
pre-standard implementation does not meet standards track expectations.
There is also open source code experience through an Open Daylight project
nd other ongoing open source linux work.

When i as the shepherd for BRSKI asked the authors for a section of implementation
experience, they punted it back to me and it ended up in the shepherd writeup.
Given how you where concerned about the document size as well, i would therefore
rather go with the shepherd writeup approach for ACP as well. The main
difference is the use of GRASP in the standards version versus a vendor
 specific protocol for signaling and service discovery of the ACP.

You can get a good detail overview of the functionality of the commercial implementation
by looking up BRKSDN-2047 on cisco.com (requires to register an account)
or less detailled info googling "Cisco IOS Autonomic Networking" documentation.

> I also think the document needs to be more clear about what security
> properties it does or does not intend to provide: we hear in the abstract
> and introduction that ACP will be "secure" (and similar platitudes are
> repeated throughout)

Agreed, there should not be platitudes. But i am not sure that a global
substitute of "secure" with "public key certificate authenticated and encrypted"
would make the document any more readable, so i welcome explicit suggestions
where specifically you think the text has platitudes and i will do my
best to eliminate them. Note also that the introduction section is 
somewhat vague beause its pretty much the "requirement specification" for
the ACP and it reflects really what operators would express. The normative
section is then filling those vague requirements with working specification
(Charter/ADs did not want us to write separate requirements documents).

> but we don't really get a sense of the specifics
> until Section 4, with ACP5.  This has a MUST for authenticated and "SHOULD
> (very strong SHOULD)" be encrypted.

This is one of those non-normative places where requirements are described.
This already went through some changes since -16 and now has only lower
case should/must so it can't be confused as rfc2119 and introductory text
 to clearly explain how it describes requirements against the normative part 
of the doc and how the normative part meets and exceeds these requirments.

> But text elsewhere in the document
> seems to be using "secure" to also mean encrypted, and there is even one
> place that flatly asserts that "ACP mandates the use of encryption".  This
> internal inconsistency needs to be resolved, at a minimum, and ideally the
> intended posture more clearly conveyed.  (It's also not really stated under
> what cases encryption would not be used, so that the "very strong SHOULD"
> could not be a MUST.)

Check if you think there is still an inconsistency. Section 4. is requirements
which are "strong should". The normative section has MUST against implementations
of this specification as a response. So, this should vbe perfectly alignet.

The normative MUST of the spec is what we know the IETF security review
expects the solution to provide (and what the authors believe to be required
too btw). The "strong should" of the section 4 requirements reflects on the
fact that many operators do actually not care about the security as much as
we would like them to because they believe to operate in physically secure
enough environments (datacententers or the like).

> Section 3.2 claims that the ACP provides "additional security" for
> bootstrap mechanisms due to the hop-by-hop encryption.  But in what sense
> is actual additional security gained?  Against an attacker with what
> capabilities?  If there is security gain from such hop-by-hop encryption,
> doesn't that point to a weakness in the bootstrap scheme?

Replaced with:

> The ACP also provides additional security for any bootstrap mechanism, because it can provide encrypted discovery (via ACP GRASP) of registrars or other bootstrap servers by bootstrap proxies connecting to nodes that are to be bootstrapped and the ACP encryption hides the identities of the communicating entities (pledge and registrar), making it more difficult to learn which network node might be attackable. The ACP domain certificate can also be used to end-to-end encrypt the bootstrap communication between such proxies and server.  Note that bootstrapping here includes not only the first step that can be provided by BRSKI (secure keys), but also later stages where configuration is bootstrapped.

Aka: You can't observe by observing network traffic who is talkking to whom to "spot the pledge" or "spot the registrar"

> I think there needs to be some justification of why rfc822Name is chosen
> over a more conventional structure in the otherName portion of the
> subjectAltName, which is explicitly designed to be extensible.

There is a comprehensive reasoning for the choice of rfc822Name in 6.1.1
that had us conclude this is the safest bet of the options we understand.

Also added:

<t>The element should not require additional ASN.1 en/decoding, because it is unclear if all, especially embedded devices certificate libraries would support extensible ASN.1 functionality.</t>

For otherName, i am worried about something like this:

> Currently OpenSSL doesn't display any otherName values. It can't know the precise meaning of that field in general because the format could be totally arbitrary. At best it could asn1parse the contents.

Aka: We wanted to use a field where we know every implementation supports
but that is also not conflicting with other pre-existing uses.
We did not want to rely on additional ASN.1 parsing of its content, because
embedded implementations might have fixed parsers. Thats why we choose a
a simple non-ASN.1 encoding of a field we know is always supported but
never used for actual network functionality so it can not conflict. And
if anything else uses already this field, you would actually see emails
to an address because the format we choose is a working rfc822name

> The requirement in Section 6.1.2 for CRL and OCSP checks seem impossible to
> satisfy for a greenfield node without non-ACP connectivity, as it must join
> the ACP domain (and supposedly validate the CRL and OCSP validity before
> doing so) before establishing an ACP link with its peer, but cannot
> validate anything with no connectivity.

ACP is not concerned with greenfield nodes, thats BRSKIs job or any other
solution that provision the certificates. So the ACP node will already
have a working cert. But there is definitely the issue that an ACP node
may not have access to current CRL or OCSP responder.

I added the following to the end of that text:

| This rule has to be skipped for ACP secure channel peer authentication 
| when the node has no ACP or non-ACP connectivity to a CDP or OCSP responder
| and only expired CRL information.

This still leaves the quagmire problem that a node connects to only
one other ACP node, then it retrieves a CRL through the ACP connection
across that node, and then it learns that that peer nodes certificate
was revoked. There is a new paragraph outlining that too (close ACP
connection, retry periodically. peer could be happy and receive a new cert.).

> Throughout, the document seems to implicitly conflate authentication with
> authorization.  I understand that the main authorization check is just the
> domain membership test in Section 6.1.2; nonetheless, as a pedagogical
> matter I cannot support propagating their conflation.

There are about 37 places in the document where the word authentication
is used to refer to something which is probably formally correctly
authentication and authorization. This formal precision was not asked
before in any other review, and i think also it would make the document
less readible if i went through all places and replaced authentication
with authentication and authorization. Primarily because in my understanding
that this conflation is pretty common practice for brevity when there really
is no configurable authorization policy but when that logic is what i would
call hard-coded - as i think it is in the case of the ACP (or rather this spec,
i could see that followup work might want to introduce actually configurable
authorization policies via intent).

For example i have not seen any text about web browsers
that said that the authentication of the web browsers certificate
authorizes the browser to display some cool looking icon and skip
bothering the user with all type of warnings. Even though i hope this
would be an appropriate use of the word authorization.

So. could i negotiate you down to the following one paragraph added to the
end of 6.1.2:

        <t> Formally, the ACP domain membership check includes both the authentication of the peers certificate (steps 1...4) and a check authorizing this node and the peer to establish an ACP connection and/or any other secure connection across ACP or data plane end to end. Step 5 authorizes to build any non-ACP secure connection between members of the same ACP domain, step 5 and 6 are required to build an ACP secure channe. For brevity, the remainder of this document refers to this process only as authentication and instead of as authentication and authorization.</t>

If not then i would welcome expllicit text proposal or at least a strategy
what to do about those 37 text places.

> In a few places, the MTI cryptographic mechanisms are under-specified,
> whether the cipher mode for IKE or the TLS ciphersuites.  I have attempted
> to note these locations in my section-by-section comments.

Thanks. See below. Should also have been fixed through Erics review.

> Section 6.11.1.14 places a normative ("SHOULD") requirement on the RPL
> root, but if I understand correctly the RPL root is automatically
> determined within the ACP, and thus the operator does not a priori know
> which node will become the RPL root.  Am I misunderstanding, or is this
> effectively placing this requirement on all ACP nodes?

More or less, yes. Packet counter on the default route to a null interface for example,
maybe a HW register for the last thus discarded packets destination address,
allowing at least sampling of such addresses. Thats what i was thinking
of suggesting if i ever manage to move on from this spec to the YANG model for
the ACP. 

I am sure we could reduce requirements by differentiating between nodes
that should never become root, but that would lead to even more text
lamenting about ad-hoc type of ACP setups. Besides, its a SHOULD and even
low-end IoT devices using CPU forwarding would have no issue implementing this.

> The IANA considerations specifically do register SRV.est in the GRASP
> Objective Names Table, and then follows up with a paragraph that this is
> only a "proposed update".  I don't know if there's actually anything
> problematic here, but the document does need clarity on what is proposed
> for future work and what is to be done now.

Ok, how about this changed paragraph. Hopefully its explaining it better.
If not, then please ask what you do not understand and once you understand,
please suggest text:

t>Explanation: This document chooses the initially strange looking format "SRV.&lt;service-name>" because these objective names would be in line with potential future simplification of the GRASP objective registry. Today, every name in the GRASP objective registry needs to be explicitly allocated with IANA. In the future, this type of objective names could considered to be automatically registered in that registry for the same service for which &lt;service-name> is registered according to <xref target="RFC6335"/>. This explanation is solely informational and has no impact on the requested registration.</t>

> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Some high-level comments that do not quite meet DISCUSS criteria appear
> below, followed by section-by-section inline comments.  My apologies for
> not splitting them between substantive and editorial, but I don't think I
> have enough time left before the telechat to do that and finish the other
> reviews I have remaining.

Sure. No worries.

> The whole premise of the ACP is for it to be almost entirely autonomic and not
> require external configuration.  But some pieces/functionality do require
> explicit configuration (e.g., manual ACP addresses, configured remote ACP
> neighbors, etc.), so I would have liked to see a section discussing what
> sort of interface might be used to inject manual configuration into the
> otherwise autonomic system.  Would this be done using ACP control messages
> from an NMS using an ACP connect node, or an out-of-band (serial)
> management port, or something else?

Ok, added at the end of the operations chapter 10 a new section 10.4.
"Configuration and the ACP (summary)"

This is all restatements i think of what should already have transpired via
various parts of the document, but i can easy see how one would want to
search in the document for something like ACP and configuation.

Let me know what you think. If not sufficient, please ask if you don't
understand something, else pls. propose text.

> I think the document needs to be more clear about its stance towards
> constrained nodes: DTLS is supported (along with IKEv2+IPSEC), supposedly
> for the benefit of constrained nodes, but then the more heavyweight TLS is
> required for several operations within the ACP itself.

Right.

I added to applicability section 1.1:

| Support for constrained devices in this specification is opportunistic, but not complete, because the reliable transport for GRASP (see <xref target="GRASP-substrate"/> only specifies TCP/TLS).

The text afterwards already points to A.9 where i modified the main
missing steps to get rid of TLS/TCP with future work:

| Hop-by-hop reliability for ACP GRASP messages could be made
| to support protocols like DTLS by adding the same type of
| negotiation as defined in this document for ACP secure channel protocol negotiation.
| End-to-end GRASP connections can be made to select their transport protocol
| in future extensions of the ACP meant to better support constrained devices by
| indicating the supported transport protocols (e.g.: TLS/DTLS) via GRASP parameters
| of the GRASP objective through which the transport endpoint is discovered.<

Opportunistic means that it was important for us to have a second useful
secure channel protocol beside IPsec to be able to have an actual case for a
secure channel selection mechanism and the fact that we do not need
a network wide MTI protocol for that because secure channels are hop-by-hop only.
Any further work for DTLS-only nodes would IMHO better be suited to a future
 constrained ACP profile document.

> Section 1
> 
>    of the ACP (after all the details have been defined), Section 10
>    provides operational recommendations, Appendix A provides additional
>    explanations and describes additional details or future work
>    possibilities that where considered not to be appropriate for
> 
> nit: s/where/were/

fixed pre 19.

>    [...] The ACP can
>    be implemented and operated without any other components of autonomic
>    networks, except for the GRASP protocol which it leverages.
> 
> This could probably benefit from being disambiguated between the single
> ACP-wide GRASP instance and the DULL GRASP used for link-local
> flooding/discovery.

Added:

 ACP relies on per-link DULL GRASP (see <xref target="discovery-grasp"/>) to autodiscover ACP neighbors, and includes the ACP GRASP instance to provide service discovery for clients of the ACP (see <xref target="GRASP"/>) including for its own maintenance of ACP certificates

> Section 1.1
> 
>    [...] The ACP can operate equally on
>    layer 3 equipment and on layer 2 equipment such a bridges (see
>    Section 7).  The encryption mechanism used by the ACP is defined to
> 
> nit: such as

thanks

>    be negotiable, therefore it can be extended to environments with
>    different encryption protocol preferences.  The minimum
>    implementation requirements in this document attempt to achieve
>    maximum interoperability by requiring support for few options: IPsec,
>    DTLS - depending on type of device.
> 
> nit: This last sentence could be reworded for clarity, "[...] requiring
> support for multiple options (IPsec and DTLS), depending on the type of
> device."

Thanks.
Had to spell out DTLS as this was introducing the term, so slightly different:

The minimum implementation requirements in this document attempt to achieve maximum interoperability by requiring support for multiple options depending on the type of device: IPsec, see <xref target="RFC4301"/>, and datagram Transport Layer Security version 1.2 (DTLS), see <xref target="RFC6347"/>).</t>

> Section 2
> 
>    ACP address:  An IPv6 address assigned to the ACP node.  It is stored
>       in the domain information field of the ->"ACP domain certificate"
>       ().
> 
> nit: The "->" and "()" seem like artifacts from an editor also usable for
> source code?  ("->" also appears in "ACP domain"'s definition, and both
> appear in the "in band (managemnet) definition and the "(virtual)
> out-of-band network" definition.)

There is a longer rant to the RFC-editor about this since -17 in the text [RFC-editor:...].
 xrefs to hanging style word definitions et.al. Will fix when doc gets
to RFC editor. They may have simpler means to do this than the limited XML
we have.

>    EST:  "Enrollment over Secure Transport" ([RFC7030]).  IETF standard
>       protocol for enrollment of a node with an LDevID.  BRSKI is based
>       on EST.
> 
> RFC 7030 is only Proposed Standard, so "standards-track protocol"
> seems more appropriate.

thanks.

>    (virtual) out-of-band network:  An out-of-band network is a secondary
>       network used to manage a primary network.  The equipment of the
>       primary network is connected to the out-of-band network via
>       dedicated management ports on the primary network equipment.
>       Serial (console) management ports where historically most common,
> 
> nit: s/where/were/

fixed pre-19.

> Please use the actual RFC 8174 instead of attempting to reproduce (but not
> exactly) its updated boilerplate.

fixed pre-19.

> Section 4
> 
>    ACP4:  The ACP MUST be generic.  Usable by all the functions and
>           protocols of the ANI.  Clients of the ACP MUST NOT be tied to
>           a particular application or transport protocol.
> 
> nit: The second sentence is only a sentence fragment.

fixed pre-19:
The ACP _MUST_ be generic, that is it MUST be usable by all the functions and protocols of the ANI.

>    ACP5:  The ACP MUST provide security: Messages coming through the ACP
>           MUST be authenticated to be from a trusted node, and SHOULD
>           (very strong SHOULD) be encrypted.
> 
> authenticated as coming from a trusted node, or authenticated to be
> from a specific node, which is known to be trusted?

Hah. The requirement was defined in the beginning of the WG to be as
written and it was not more specific. We worked the solution off of it.
We choose to use hop-by hop authentication/encryption because it
provides better infrastructure protection, but this does not mean that
an end-to-end authentication/encryption would not also be a possible
solution against the requirement either, so i would like to not be more
specific here - because i am thinking of proposing that alternative in
future work: The op-by-hop encryption provides best infrastructure
security, but as already mentioned, hardware may have problems, so
we could have future work defining ACP variations with just end-to-end
encryption (more limited in infrastructure and perpass protection).

Aka: no change done now.

> Also, maybe "MUST, except for [...]" is better than "very strong
> SHOULD".  (What are the execptional cases where plaintext is allowed?)
> Integrity protection of authenticated traffic may be worth mentioning
> explicitly.

Hope its clear from my prior explanation that this section describes the
operator requirements input into the development of the ACP solution and
not the output (deleted charter limitation rant). 
> 
>    Th eACP operates hop-by-hop, because this interaction can be built on
> 
> nit: s/Th eACP/The ACP/

thanks

> Section 5
> 
>    3.  For each node in the candidate peer list, it authenticates that
>        node and negotiates a mutually acceptable channel type.
> 
> There seems to be an implicit step in here, "confirms that the node is
> authorized to be a part of the same ACP domain".  Presumably this is usally
> the "ACP domain membership check" of Section 6.1.2; a forward reference
> seems in order.

ack.

> Section 6.1.1
> 
> It's slightly jarring to use ABNF to specify the contents of an
> ASN.1 field.

See earlier discuss in this mail and text added text to justify it.

(admittedly i am also a fan of the good old human readable
 "Simple Something Protocol" approach of the IETF of distant times,
  so please also take my age into consideration ;-)
 
> hex-dig is case-insensitive; is that intended?

Hmm. Not, its specified in the following line as case sensitive:

hex-dig = DIGIT / "a" / "b" / "c" / "d" / "e" / "f"

DIGIT was predefined ABNF, couldn't find any hex, didn't find a
reason why case insensitivity would be a lot of help here...

> "acp-address" seems under-specified and maybe over-constrained, in
> that it does not say how to get what digits to put there, and in
> that limiting to 32 hex digits may prevent the use of alternative
> ACP address schemes in the future, as is suggested as a possibility
> in the body text.

You do not need to create a new encoding if you pick an unused
type field in the ACP address. COming up with new encodings
in the ACP domain information field is orthogonal:

  rfcSELF.0++XXYABC1234567@new-acp-domain.com [1]
  rfcNEXTwhaeverelse@new-acp-domain.com

Those are the two extensibility options we already have:
[1] is backward compatible with this ACP spec and the
strange string is some form of indicating an address. Existing
nodes would think that nodes does not have an ACP address (0).
[2] would just change the key field and be able to copy everything
it likes about the current format, and change everything it doesnt like.

What type of ABNF improvement would you propose to make
extensiblity even better ?

>    [...] If the operator does not own any FQDN, it should
>    choose a string (in FQDN format) that intends to be equally unique
> 
> I don't know if it's worth cautioning against making up fake
> TLD-equivalents, given how this has bitten people as new TLDs come
> online.

I'll be happy to add a reference if theres any good text to point to,
but would not want to dare wasting space on suggestions how to best not
get caught with something that can always be a problem.

The acp-domain name only becomes security relevant within
a single PKI root, otherwise it is just human diagnostics, so the problem is
IMHO not big. As long as you don't name your ACP domain
"acp.example.com" or whatever domain names are mentioned as examples
in documentation.

> I'm not sure that "people implementing our stuff have an easier
> time" is a great reason to stuff randomly-shaped stuff into an
> existing hole, especially when there's this nice otherName-shaped
> hole available right next to it.

If you want to propose text for the ASN.1 encoding of ACP domain
information, we could let the WG decide. So far the WG did agree
on the rfc822 option, and i wouldn't even know how to define the
ASN.1 in a way i would feel safe to not have overlooked any possible
issue - any ASN.1 expert around with free time ?

As said: If it was me, i would still prefer to not use ASN.1 for the
internal encoding due to risk of non-extensibility of existing low-end
parsers and more limited diagnostic to humans.

>    o  The format of the rfc822Name is chosen so that an operator can set
>       up a mailbox called   rfcSELF@<domain> that would receive emails
>       sent towards the rfc822Name of any node inside a domain.  This is
>       possible because in many modern mail systems, components behind a
>       "+" character are considered part of a single mailbox.  In other
>       words, it is not necessary to set up a separate mailbox for every
>       ACP node, but only one for the whole domain.
> 
> This is effectively codifying that foo+bar@baz === foo@baz in email
> addresses, which perhaps merits some broader discussion (especially in the
> context of security issues when different providers disagree about whether
> local components of email addresses differing after a '+' are the same or
> not!).

We had a pretty broad discussion asking folks if they where aware of
email addresses in certificates of network devices ever being used
for something automatically (aka: not through visual inspection by a human),
and nobody had an example. Thats why we felt it was quite safe to choose
the rfc822 format. The use of "+" then was just opportunistically using
what might be the best use of existing practices, but without expecation
that this would actually be ever used.

> Section 6.1.2
> 
>   o  The peer's certificate is signed by one of the trust anchors
>       associated with the ACP domain certificate.
> 
> This seems to preclude having a PKI structure that is common in the web
> world, of a highly secure, offline trust anchor that only certifies
> intermediate CA certificates, with the intermediates certifying end-entity
> certificates.  Perhaps the intention is that the peer's certificate chains
> to such a trust anchor?

Indeed, thats what we want.

Fixed already for Erics review:

   3:   The peer's certificate passes certificate path validation as
      defined in [RFC5280] against the Trust Anchor associated with the
      ACP nodes ACP domain certificate (see Section 6.1.3 below).

Hopefully this is correct text. If there is a better way to say it, proposed
text would be higly welcome.

>    o  The peers certificate has a syntactically valid domain information
>       field (subjectAltName / rfc822Name)  and the domain name in that
>       peers domain information field is the same as in this ACP node
>       certificate.
> 
> Is this supposed to be an exact byte-for-byte match, or is some form of
> insensivity allowed that would require normalization/canonicalization prior
> to comparison?

Added "(lowercase normalized)" to the comparison requirement for the acp-domain-name.

> Section 6.1.3
> 
> I had noted (in my local notes) on the -13 that using the ACP address and
> only storing one EST server makes for a single point of failure; the
> situation seems somewhat improved in the -16 in that the remebmered value
> is used as the first attempt for renewal, but presumably with GRASP
> announcement as a fallback there is less of a single point of failure.

Yes. that seemed like a good compromise. Stickyness to prior registar
is meant to ease diagnostics in hopefully many cases and maybe speed up
the process.

> Section 6.1.3.1
> 
> Does the example need a comma after 255 to indicate the absent
> objective-value?

I don't think so in my interpretation of CDDL. We had a couple of reviews
from folks who should know CDDL better, nobody brought this up. Hope
they are reading this mail.

>  (Also, putting the example after the CDDL might help the
> reader know what they're looking at.)

If i get another voice for that order i'll change it (you are the first one to
voice this preference). Personally (as what probably is lazy reading, i always
like it better to see an example first, before being dragged into a
full specification/format-explanation. Most likely i only want to read
up some details from the spec because i can already guess most of it from
the example.

> The "formal CDDL definition" of flood-message seems somewhat
> informal at times, e.g,. for loop-count.

Its not meant to be informal.
Any other place in the definition where you think it is too informal ?

The strong choice of 255 for TTL is based on not knowing how large
the network is and no means defined to figure out automatically how large it is.
When we get to defining a YANG model, i'd make it a parameter if being forced
to, but from a decade of experience with TTL scoping in IP multicast
i certainly would like to avoid it.

Let me know if you think any of scuh explanation needs to be added to the
text or what else you don't like.

> Using both "[t]he objective value" and an "objective-value" field for
> different things is needlessly confusing; can the body text be clarified
> somewhat about the value "SRV.est"?

That was a bug on my behalf. SRV.est is called the objective name in GRASP.
Fixed.

> Can "negligbile traffic" be quantified?

No. Its in the eye of the beholder (network admin). 30...60 seconds is used
in all typical protocols i remember and will be fine for all non-low bitrate
networks. Once you get into lower bitrates (below 1 Mbps ?) i would expect
operators may find 30...60 seconds not negligible.

Aka: this would have to be configurable until we have enough experience
to define an automatic distributed backpressure mechanism like in RTCP RRs
multicast reports (this is not a question of the SRV.est reports alone
but the sum of all flooded service reports IMHO).

> Section 6.1.3.3
> 
>    [...] If the CDP URL uses an IPv6 address (ULA address when using
>    the addressing rules specified in this document), the ACP node will
>    connect to the CDP via the ACP.
>
> Seems to be duplicated?

vi fumble. thanks.

>    HTTPs connections.  The connecting ACP node SHOULD verify that the
>    CDP certificate used during the HTTPs connection has the same ACP
>    address as indicated in the CDP URL of the nodes ACP domain
>    certificate
> 
> Presumably only if the CDP URL listed an IPv6 address.
> (Also, nit: full stop at end of sentence.)

added: if the CDP URL uses an IPv6 address.o
fixed nit.

> Section 6.1.3.4
> 
> A reference to draft-ietf-acme-star and/or draft-nir-saag-star might be
> useful to inform the reader of related work.  (Note that the latter was not
> adopted by the LAMPS WG yet, with the indication that some changes were
> needed before it would be appropriate for adoption.)

Thanks. Added a "see also draft-ietf-acme-star".

> Section 6.2
> 
>    [...] An ACP node MUST
>    maintain this adjacency table up to date.
> 
> Up to date on what timescale?

Removed "up to date". Does this resolve your comment ?

>    The adjacency table MAY contain information about the validity and
>    trust of the adjacent ACP node's certificate.  However, subsequent
>    steps MUST always start with authenticating the peer.
> 
> Also verifying that it is authorized for the operation in question?

Replaced "start with..." by
"start with the ACP domain membership check against the peer (see <xref target="certcheck"/>)"

> Section 6.3
> 
>    The result of the discovery is the IPv6 link-local address of the
>    neighbor as well as its supported secure channel protocols (and non-
>    standard port they are running on).  It is stored in the ACP
>    Adjacency Table, see Section 6.2 which then drives the further
>    building of the ACP to that neighbor.
> 
> nit: "see section 6.2" is probably better in parentheses, but if commas
> are used, they need to be both before and after it.

Fixed.

> Section 6.4
> 
>    o  Build the ACP across all domains that have a common parent domain.
>       For example ACP nodes with domain "example.com", nodes of
>       "example.com", "access.example.com", "core.example.com" and
>       "city.core.example.com" could all establish one single ACP.
> 
> If this wasn't an example it sounds like it'd need to reference the
> public suffix list?

Please check out the text as it was changed from other -16 review,
the whole intent section (because is futures) is now appendix A.8.

Aka: this is more about mutual agreement of two domains to trust each other
and coming up with appropriate means to share trust anchor (aka: not easy).

If you don't mind elaborate about public list, i am interested if
that would be a simpler solution.

> Section 6.5
> 
>    o  An ACP node may choose to attempt initiate the different feasible
> 
> nit: to attempt to initiate

Done.

> Section 6.6
> 
> "Exponential backoff" requires the base of the exponent to be specified in
> order to be well-defined.  (An base of, e.g., 1.0000001 is hardly any
> backoff at all, over our normal timescales.)

There is no unspoken verbal default of 2 ?
Which scheme doesn't use 2 ? ;-))

Fixed to: 

"...default is exponential base 2 backoff with a minimum..."

> Section 6.7.1.1
> 
>    [...] It MUST then
>    support ESP with AES256 for encryption and SHA256 hash and MUST NOT
>    permit weaker crypto options.
> 
> That does not fully specify cryptographic parameters for
> communication security, e.g., CTR vs. CBC vs. GCM mode of AES.
> (Similarly in Section 6.7.1.2.)

Same comment from Eric. Proposed text:

It MUST then support ESP with AES-256-GCM (<xref target="RFC4106"/>) for encryption and SHA256 hash and MUST NOT permit weaker crypto options. Key establishment MUST support ECDHE with P-256.

I have only been able to vet a little bit, but i hope we're on solid
ground not limiting the amount of current HW crypto by the choice of GCM
but rather even improve HW acceleration support by choosing it as the MTI.

Let me know if there are any other forgotten parameters. Sugggestest
MTI choice highly welcome. Guidance is simply the currently likely
most widely HW accelerated supported option meeting common security
level expectations (yes i know thats hard to quantify).

>    In terms of IKEv2, this means the initiator will offer to support
>    IPsec tunnel mode with next protocol equal 41 (IPv6).
> 
> nit: "equal to"

fixed.

>    ESP is used because ACP mandates the use of encryption for ACP secure
>    channels.
> 
> I thought this was only a "very strong SHOULD", not mandatory.
> (Similarly in Section 6.7.1.2.)

Should be clear by now. We changed from SHOULD to MUST a couple of
versions ago, because the only way to avoid downgrade attacks if we
permit unencrypted is to come up with some domain certificate extension
allowing null-crypto, and if there are really enough markets
(data center etc.) wanting this, its easily done in a followup
document.

> Section 6.7.1.2
> 
> (Lots of this section duplicates 6.7.1.1 and could be consolidated into
> the toplevel 6.7.1.)

really just the one paragraph specifying the crypto parameters,
all the other text in the two sections is different. Given how
confusing all these IPsec options can be (transport vs. tunnel for example),
i felt it was easier to keep the options clearly apart to avoid falling
victim to readers/reviewers assuming some parameters could be same when its not.

>    If IKEv2 initiator and responder support GRE, it will be selected.
>    The version of GRE to be used must the according to [RFC7676].
> 
> nit: the grammar in the last sentence is weird; maybe "must be determined
> according to"?

Thanks. Done.

> Section 6.7.2
> 
>    To run ACP via UDP and DTLS v1.2 [RFC6347] a locally assigned UDP
>    port is used that is announced as a parameter in the GRASP AN_ACP
>    objective to candidate neighbors.  All ACP nodes supporting DTLS as a
>    secure channel protocol MUST support AES256 encryption and MUST NOT
>    permit weaker crypto options.
> 
> You should specify actual ciphersuite, signature, and hash
> algorithms.

Trying to outsource to prior work (rfc7525) after discuss with eric earlier.
Text is now:

<t>All ACP nodes supporting DTLS as a secure channel protocol MUST
adhere to the DTLS implementation recommendations and security considerations of <xref target="RFC7525"/> except with respect to the DTLS version. ACP nodes supporting DTLS MUST implement only DTLS 1.2 or later.  For example, implementing DTLS-1.3 (<xref target="I-D.ietf-tls-dtls13"/>) is also an option.</t>

> Section 6.7.3
> 
> I would recommend calling out the "terminate channel when certificate
> expires" behavior again in the security considerations, as it would be
> surpirsing to readers expecting the "standard" behavior.

Added to security section:

<t>Because ACP secure channels can be long lived, but certificates used may be short lived, secure channels, for example built via IPsec, need to be terminated when peer certificates expire. See <xref target="Profiles"/>.</t>

>    nodes with an area of baseline ACP nodes MUST therefore support IPsec
>    and DTLS and supports threefore the baseline and constrained profile.
> 
> nit: s/threefore/therefore/

Previously fixed.

> Section 6.8.2
> 
> The figure does not really aid my understanding absent some
> additional explanation.

Hmm. hard to understand what specific explanations you would require.
There already is a lot of explanation. Can you maybe ask specific
questions that would help me write the fitting explanations ?

>    GRASP unicast messages inside the ACP always use the ACP address.
>    Link-local ACP addresses must not be used inside objectives.  GRASP
> 
> Link-local *ACP* addresses, or IPv6 ones?

Changed to "Link-local addresses from the ACP VRF". 

We did phrase the term "ACP address" to only refer to the certificate
provided ULA IPv6 address (assigned on loopbacks) to make the
terminology easy for operators/users. The don't even need to think
any more about the VRF. The implementer on the other hand will know
about the VRF, and for them the term "ACP address" may be referring
to any address of the ACP VRF. So we need to be careful in
terminology here. So i think calling out ACP VRF explicitly does that.

>    [...] GRASP
>    unicast messages inside the ACP are transported via TLS 1.2
>    ([RFC5246]) connections with AES256 encryption and SHA256.
> 
> Same comment as before about ciphersuite/etc. 

Hmm. I think Eric missed this one ;-)

TBD: Could you recommend a good equivalent to rfc7525 to refer to for a
good TLS 1.2 profile that i could refer to

> Also, TLS or DTLS (noting
> that constrained devices are assumed to only implement DTLS)?

Yes, see note abbout "opportunistic" but not complete support for
constrained devices in the applicability section 1.1 that i mentioned.
The spec is not sufficient for constrained device, it only specifies
those aspects we understand and wanted to include.

Right now IMHO we have not enough participants experts for constrained
devices in the effort to really be sure that we have a sufficient solution
for specific type of constrained devices.

One problem are the end-to-end connections. We need for example
EST via DTLS, or rather via CoAP ? ACME ? for cert renewal, and once
 we're happy with that, we can figure out if we'd get away with the same 
type of mods for GRASP unicast connections. DTLS has some strage partial 
reliability if i remember correctly, so we may need application level 
transaction retries, and i don't think that GRASP has gone through that
analysis either.

> Also, TLS 1.3 is in the RFC Editor's queue; is there work underway
> to adapt to it?

No plan right now. Router software is so slow to update so we'd easily
create big implementation hurdles short term.

Given how TLS for GRASP is only defense against attacks from inside the
ACP (secure channel IPsec/DTLS protect against attacks from outside).

I am actually also not a fan of the certificate hiding of TLS 1.3 for
the use-case inside the ACP. If i have traffic going across the
internet i definitely want TLS 1.3 against perpass, but if i am
a single domain network operator running an IPsec hop-by-hop encrypted
management network inside of which there is TLS between my network
devices, then tracing of domain certificates may be my last easy
report for diagnostics and troubleshooting.

>    [...] TLS and TLS connections for GRASP in the ACP use the IANA assigned
>    TCP port for GRASP (7107).
> 
> Is one of those supposed to be DTLS?  Is the IANA-assigned port
> assigned for both TCP and UDP?

Fixed to TCP and TLS - we only use TLS for end-to-end inside ACP,
for single-hop we use TCP because there is nothing gained by TLS
over the underlying single-hop IPsec/DTLS encryption.

Yes, port is assigned for TCP and UDP by GRASP but not mentioned
here because - see above discussion - there is more to resolve than
just saying "use DTLS" to make embedded devices completely happy.

> Section 6.8.2.1
> 
> As a side note, I don't mind seeing discussion about potential future work
> to avoid the double authentication/encryption, but my intuition is that
> it's not really worth pursuing.

Yes, i primarily wrote this to ensure the insight isn't lost.
The encryption hardware is struggling with is the hop-by-hop one because
it needs to scale with the amount of transit traffic. authentication
is IMHO not an issue to duplicate.

> Section 6.10.1
> 
>    o  Addresses in the ACP are not considered sensitive on privacy
>       grounds because ACP nodes are not expected to be end-user devices.
>
> I feel like this claim requires additional justification.

Added:

All ACP nodes are in one (potentially federated) administrative domain.
They are are assumed to be to be candidate hosts of ACP traffic
amongst each other or transit thereof. There are no transit nodes
less privileged to know about the identity of other hosts in the ACP.

> Section 6.10.3.1
> 
>    A node knowing it is in a zone MUST also use that Zone-ID != 0
>    address in GRASP locator fields. [...]
> 
> What does "also" mean here?  Is this another requiment being placed on a
> node that knows it is in a zone, or must this node use both the zone-id==0
> and the zone-id!=0 addresses in GRASP locator fields (i.e., duplicating all
> such)?

Just bad english. removed "also".

> Section 6.10.5
> 
>    o  V: Virtualization bit: Values 0 and 1 are assigned in the same way
>       as in the Zone-ID sub-scheme.
> 
> There is not a single 'V bit' -- the V field is either 8 or 16 bits long --
> so saying "in the same way" is confusing.

changed to:

V: Virtualization field: 8 or 16 bit. Values 0 and 1 are assigned in the same way as in the Zone-ID sub-scheme, the other values are for further use by the node.

> I believe that the intent is to
> distinguish between "zero" and "not-zero", with the zero value meaning the
> same as the zero bit in the Zone-ID sub-scheme.  That is, the final bit
> need not be 1 to indicate a "virtual" usage.  Or do I misunderstand?

Right. The sentence just means to express that any semantic we assign
to values 0 and 1 in the zone addressing scheme should equally apply
to values 0 and 1 in the Vlong addressing scheme, leaving the remaining
8/16 bit - 2 values up for further use by the node.

> Section 6.10.7.3
> 
>    In a simple allocation scheme, an ACP registrar remembers
>    persistently across reboots for its currently used Registrar-ID and
>    for each addressing scheme (zone with Subnet-ID 0, Vlong with /112,
>    Vlong with /120), the next Node-Number available for allocation and
>    increases it after successful enrollment to an ACP node.  In this
>    simple allocation scheme, the ACP registrar would not recycle ACP
>    address prefixes from no longer used ACP nodes.
> 
> It's probably better to say "increments it during successful enrollment"
> since if the registrar crashed right after issuing a certificate but before
> incrementing the next available node-number, it would issue a duplicate
> when it came back up.

Done.

You'd probably want to have another bit on persistent storage saying
allocation pending, so that if you crash and see that bit on recovery, you
know that you don't know if the number got successfully enrolled and you
have to skip it to be sure you don't do duplicate allocation.

Don't think we want to take all the fun of figuring out the best scheme
from implementers. This is more focussed to operators to understand
enough that they can operate it confidentially.

> Section 6.10.7.4
> 
>    [...] Even when the renewing/rekeying ACP registrar is not
>    the same as the one that enrolled the prior ACP certificate.  See
>    Section 10.2.4 for an example.  ACP address information SHOULD also
>    be maintained even after an ACP certificate did expire or failed.
>    See Section 6.1.3.5 and Section 6.1.3.6.
> 
> Both the first and the last sentence quoted have grammar nits; the former
> is a sentence fragment (perhaps "This holds even when [...]"), and the
> second has inconsistent verb tense (perhapse "expired or failed").

another case of editor looses, vi wins.

Split into two hopefully now correct sentences/paragaphs:

<t>ACP address information SHOULD be maintained even when the renewing/rekeying 
ACP registrar is not the same as the one that enrolled the prior ACP certificate. 
See <xref target="sub-ca"/> for an example.</t>

<t>ACP address information SHOULD also be maintained even after an ACP
certificate did expire or failed. See <xref target="domcert-re-enroll"/>
and <xref target="domcert-failing"/>.</t>

> Section 6.11
> 
>    All routing updates are automatically secured in transit as the
>    channels of the autonomic control plane are by default secured, and
>    this routing runs only inside the ACP.
> 
> Again, I thought encryption was only "very strong SHOULD".

That point is resolve (MUST).

> If this "secured" only was intended to refer to authentication (and
> presumably implicitly integrity protection), then "by default" is
> not needed, since the latter protection is mandatory.

I changed "by default secured" to "encrypted" to make the sentence
easier to digest.

> Section 6.11.1.1
> 
>    In summary, the profile chosen for RPL is one that expects a fairly
>    reliable network reasonably fast links so that RPL convergence will
>    be triggered immediately upon recognition of link failure/recovery.
> 
> Is there a missing "with" in here, or something else in order to get
> it to parse?

Fixed in prior version.

>    [...] This the same
>    behavior as that of other IGPs that do not have the Data-Plane
>    options as RPL.
> 
> Is this suppposed to be ", as is the case for RPL"?  (Also, "This is"?)

Changed to:
This is the same behavior as that of other IGPs that do not have the Data-Plane options of RPL.

> In general, this section has an unclear overall structure/organization and
> several instances of strange grammar/wording.  The RFC Editor will be of
> some help with the latter, but generally is unwilling to take the
> initiative to make the sorts of changes needed to address the former.

This was a collaboration between Pascal Thubert and I. I think all the wrong
grammar is from me and all the right technical RPL details from Pascal ;-))

If this looks like a strange collection of tidbits, this was the pieces
of information that i felt to be unique to RPL and not known by developers or
operators who are otherwise knowledgable of IGP routing.

Having said this: Please re-read the section, i did another thorough re-read
and changed a lot of text for better readability.

> Section 6.11.1.7
> 
>    Local Repair: As soon as link breakage is detected, send No-Path DAO
>    for all the targets that where reachable only via this link.  As soon
> 
> nit: s/where/were

Ack.

> Section 6.11.1.9
> 
> Please don't treat "security" as some single black-box concept; there are
> gradiations within it and different attributes that can be relevant.  For
> example, here we would probably say something like "Because the ACP links
> already include provisions for confidentiality and integrity protection,
> their usage at the RPL layer would be redundant, and so RPL security is not
> used".  I guess the RPL security bits needed for per-participant
> authentication (as opposed to a group key) are not entirely in place yet,
> so it's hard to claim that RPL security would do much better than even
> hop-by-hop ACP security measures.

Thanks. Inserted your suggested text.

Myself, i would have gone with a rant about the ACP trying to eliminate the need to
waste several years of everybodies time to reinvent for each network distributed
protocol its own unique security mechanisms, but thats obviously not necessarily
the most prudent option to quickly pass through IESG. At least not when talking
about existing protocols ;-)

> Section 6.11.1.12-14
> 
> These sections do not match up with the template entries I see in
> draft-ietf-roll-applicability-template-09; can you explain the discrepancy?

TBD: I think these where details usually not covered by the RPL profile
but that we felt necessary to add for the case of the ACP.

> Section 6.12.5
> 
> I'm confused about the "ACP multi-access virtual interface" -- is
> this only for the initial "link-local" flooding/discovery?
> Otherwise, aren't the ACP secure channels inherently two-party?  I
> don't think I understand what the multi-access benefit is, since my
> understanding was that RPL was running on top of these link-local
> secure channels.

The secure channels are just that: packet transport. They are not interfaces
with IPv6 addresses on them recognized by IPv6 forwarding or an IPv6
routing protocol as an L3 subnet. So we need to define how we add a "virtual"
interface on top of the secure channel and how to operate it.

If you just do a 1:1 mapping between p2p secure channels and interfaces,
you will end up on a LAN with a full mesh of p2p L3 subnet virtual
interfaces. Which is primarily an issue when you want to flood. Like
RPL and GRASP do. You get a message from one neighbors p2p interface and
you send it back to all the other neighbors p2p interfaces. Which doesn't
break things, its just inefficient.

Thats why for an optimized implementation, you create a single "LAN" like
virtual subnet across all the secure channels to neighbors on the same
underlying L2 LAN. Then you can send L3 multicast into that multipoint
subnet, and the virtual subnet driver replicates those packets into
all the p2p secure channels, and the receiver won't loop back
packets unnecessarily.

This optimization technique is done in several network solutions.
Somehow its always a vendor technique, so i couldn't find a good reference
RFC to describe this (outside of something very specialized that didn't
seem right to reference). So i ended up having to write a lot of the
mechanism here ;-(

> Section 6.12.5
> 
>    The ACP virtual interface IPv6 link local address can be derived from
>    any appropriate local mechanism such as node local EUI-48 or EUI-64
>    ("EUI" stands for "Extended Unique Identifier").  It MUST NOT depend
>    on something that is attackable from the Data-Plane such as the IPv6
>    link-local address of the underlying physical interface, which can be
>    attacked by SLAAC, or parameters of the secure channel encapsulation
>    header that may not be protected by the secure channel mechanism.
> 
> Is this the same EUI that might be used on the Data-Plane like the MAC
> address of the physical interface?

Yes. But MAC address seems to be a slang term, some review had me use
to EUI terminology if i remember correctly.

> nit: s/Charly/Carol/

Done.

> Section 7.2
> 
>    The description in the previous paragraph was specifically meant to
>    illustrate that on hybrid L3/L2 devices that are common in
>    enterprise, IoT and broadband aggregation, there is only the GRASP
>    packet extraction (by Ethernet address) and GRASP link-local
>    multicast per L2-port packet injection that has to consider L2 ports
>    at the hardware forwarding level.  The remaining operations are
>    purely ACP control plane and setup of secure channels across the L3
>    interface.  This hopefully makes support for per-L2 port ACP on those
>    hybrid devices easy.
> 
> Have you talked to any hardware manufacturers that would be able to remove
> the "hopefully" from this statement?

Yes.  This judgement comes primarily from me investigating the (non-)complexity to
support "per port L2 ACP" on a few ranges of L2/L3 switches hardware at my previous
employer and my background and comparison to the complexity of hardware support 
for IGMP/MLD(L3)+IGMP/MLD(L2), signaling and forwarding entries.

>    A generic issue with ACP in L2 switched networks is the interaction
>    with the Spanning Tree Protocol.  Ideally, the ACP should be built
>    also across ports that are blocked in STP so that the ACP does not
>    depend on STP and can continue to run unaffected across STP topology
>    changes (where re-convergence can be quite slow).  The above
>    described simple implementation options are not sufficient for this.
>    Instead they would simply have the ACP run across the active STP
>    topology and the ACP would equally be interrupted and re-converge
>    with STP changes.
> 
> This "Instead" is a little unclear, perhaps "They fail because the ACP
> simply runs across the active STP topology [...]"?

Didn't read well, yes. Moved last paragraph to the front and fixed up sentences
so it reads easier.

<t>A generic issue with ACP in L2 switched networks is the interaction with the Spanning Tree
Protocol.  Without further L2 enhancements, the ACP would run only across the active STP 
topology and the ACP would be interrupted and re-converge with STP changes.
Ideally, ACP peering should be built also across ports that are blocked in STP so
that the ACP does not depend on STP and can continue to run unaffected across STP topology
changes, where re-convergence can be quite slow.  The above described simple implementation
options are not sufficient to achieve this.</t>

> Section 8.1.1
> 
>    The ACP connect interface must be (auto-)configured with an IPv6
>    address prefix.  Is prefix SHOULD be covered by one of the (ULA)
>    prefix(es) used in the ACP.  If using non-autonomic configuration, it
>    SHOULD use the ACP Manual Addressing Sub-Scheme (Section 6.10.4).
> 
> I'm confused in what case ACP connect would be used with autonomic
> configuration (and thus why the qualification is needed on the SHOULD).
> I thought the whole thing was premised on the presence of a NMS that does
> not implement ACP.

Changed to:

  <t>An ACP connect interface SHOULD use an IPv6 address/prefix
from the ACP Manual Addressing Sub-Scheme (<xref target="manual-scheme"/>), letting the operator configure for example only the Subnet-ID and having the node automatically assign the remaining part of the prefix/address.  It SHOULD NOT use a prefix that is also routed outside the ACP so that the addresses clearly indicate whether it is used inside the ACP or not.</t>

>    In the simple case where the ACP uses only one ULA prefix and all ACP
>    connect subnets have prefixes covered by that ULA prefix, NMS hosts
>    can rely on [RFC6724]
> 
> Please include some exposition on the property being provided instead of
> just citing the RFC.

Improved the salient two sentences:

NMS hosts can rely on <xref target="RFC6724"/> to determine longest match prefix routes towards its different interfaces, ACP and data-plane. With RFC6724, The NMS host will select the ACP connect interface for all addresses in the ACP because any ACP destination address is longest matched by the address on the ACP connect interface. 

>    ACP Edge Nodes MUST only forward IPv6 packets received from an ACP
>    connect interface into the ACP that has an IPv6 address from the ACP
>    prefix assigned to this interface (sometimes called "RPF filtering").
> 
> This sentence is hard to parse as to what the "that has" restriction
> applies to.  I think it's supposed to be that you only forward (IPv6 packets
> with a source address from the ACP prefix) into the ACP, right?

I have a genetic disorder for long sentences. Its called german genes
and upbringing.  See Mark Twain *sigh*

Changed to:

<t> When an ACP Edge node receives a packet from an ACP connect interface, it
MUST only forward it into the ACP if it has an IPv6 source address from that interface.
 This is sometimes called "RPF filtering".

(somehow i can't shorten it, but hopefully its easier to read).

>    To limit the security impact of ACP connect, nodes supporting it
>    SHOULD implement a security mechanism to allow configuration/use of
>    ACP connect interfaces only on nodes explicitly targeted to be
>    deployed with it (such as those physically secure locations like a
>    NOC).  For example, the certificate of such node could include an
>    extension required to permit configuration of ACP connect interfaces.
> 
> I think this would be better as "[...] could include a specific extension,
> and that extension would be required to be present in order to permit
> configuration [...]".  But who would enforce this requirement -- the ACP
> implementation on the node that is compromised?  That does not seem to
> provide the desired security property.  This also falls into Alissa's
> comment about "future work".

Yes, this was already changed in -17 for Alissa as follows:

  To limit the security impact of ACP connect, nodes supporting it
   SHOULD implement a security mechanism to allow configuration/use of
   ACP connect interfaces only on nodes explicitly targeted to be
   deployed with it (those in physically secure locations such as a
   NOC).  For example, the registrar could disable the ability to enable
   ACP connect on devices during enrollment and that property could only
   be changed through re-enrollment.  See also Appendix A.10.5.

Appendix A.10.5 (futures) describes how one could do role assignments
enabling this type of behavior. 

Wrt compromised nodes that you mention: Lets ignore the attack of
running unauthorized code, thats a different discussion and when
you have that attack succeeding, you don't need to worry about ACP connect anyhow.

Instead, the role assignment described in the current -19 text can IMHO very well
protect against the most important attack, which is the ability to configure anything
on the compromised device. 

> Section 8.2.1
> 
> I think you need to include a reference for ABNF.

Thought we only do this the first time we encounter ?
Up in the GRASP objective section.

> Section 9.1
> 
>       [...] Since the revocation check is only
>       done at the establishment of a new security association, existing
>       ones are not automatically torn down.  If an immediate disconnect
>       is required, existing sessions to a freshly revoked node can be
>       re-set.
> 
> How would the revoked node's peers know to perform such a re-set?  This
> would seem to require some signaling protocol at revocation time.

Yes. I think this is part of the original informative text, like a requirement
that we wrote into the spec before getting to the normative part. I think
we never tried to solve this hidden requirement ("benefit"), primarily
because the authors (and brski authors) became more and more fans of
short lived certificates over CRL/OCSP because it minimizes the total number of protocols
required and doesn't seem to increase the overall signaling vs. periodically
refreshed OCSP or CRL.

So, with that background, here is my proposed rewrite of the paragraph:

<t>The ACP tracks the validity of peer certificates and tears down ACP secure channels when a peer certificate has expired. When short-lived certificates with lifetimes in the order of OCS
P/CRL refresh times are used, then this allows for removal of invalid peers (whose certificate was not renewed) at
similar speeds as when using OCSP/CRL. The same benefit can be achieved when using CRL/OCSP,  periodically refresh
ing the revocation information and also tearing down ACP secure channels when the peers (long-lived) certificate is revoked. There is no requirement against ACP implementations to require this enhancement though to keep the mandatory implementations simpler.</t>

So, this is just me of course trying to promote the short-lived cert option and
keeping ACP implementations constrained complex.

There may be established policies in IETF PKI to continue demanding all the
same benefits when using the more complex CRL/OCSP approach, in which case
i'd have to probably remove the last sentence and also add an appropriate
reqiurement to tear down upon CRL/OCSP refresh to the normative text.

>    After a network partition, a re-merge will just establish the
>    previous status, certificates can be renewed, the CRL is available,
>    and new nodes can be enrolled everywhere.  Since all nodes use the
>    same trust anchor, a re-merge will be smooth.
> 
> I believe this document has described schemes where not all nodes use the
> same trust anchor [for signing their LDevID], so maybe this should be
> "trust anchor(s)" plural?

Done.

>    Merging two networks with different trust anchors requires the trust
>    anchors to mutually trust each other (for example, by cross-signing).
>    As long as the domain names are different, the addressing will not
>    overlap (see Section 6.10).
> 
> Subject to the risk of a 40-bit collision in SHA256!  While not necessarily
> a critical flaw at this time, the limitation should probably be mentioned.

Right. Added: except for the low probability of a 40-bit hash collision in SHA256.

Alas the nice web pages where you could "register" your ULA prefix went
away 2 yers ago. I had them mentioned in earlier versions of the doc.

Btw: there is nothing limiting AXCP to ULA. If there was a simple
"pay with credit card to get a /48 prefix" service, we'd probably have
included a configurable prefix option. But i don't even know how expensive
such a prefix would be these days.

> Section 9.2.1
> 
> I think you need informative references to all the listed protocols that
> the ACP could serve as protection for.

Done.

> % remote attacks are impossible
> 
> Remote attacks to DoS by resource consumption the nodes involved would
> still work fine, so "impossible" is probably overstating it.

refined sentence to:

remote attacks from the data-plane are impossible as long as the data plane has no facilities to remotely sent IPv6 link-local packets. The only exception are ACP connected interfaces which require higher physical protection.

The point is that the only way to get into the ACP is through the link-local addresses of the ACP secure channels and it should be impossible to do that remotely. 

> Section 9.2.2
> 
> I expected to see something about the importance of being able to detect a
> compromised node and revoke its certificate.  Ideally this could be
> automated (with the detecting node providing proof of compromise in some
> fashion), though the details of that would probably be hard to get right.

Note that the -18 already had changes to 9.2.2 fixing some text, but i
also created a new appendix A.10.8 in response to your wish. I am not
sure if it highlights enough what you have in mind, and i am sure its
not what folks wanting more autonomic networks would prefer, but IMHO the
most likely short-term valuable direction is to focus on eliminating all
the local options to break into a network devices through credential abuse
and configuration change that can't be rectified. Or else: Maximize
the options to recover a node remotely from attackers before going to the
option of giving it up by kicking it off the network.

Would love to hear your thoughts on this.

> Section 9.3
> 
> "independent of configuration" is in conflict with the discussion of
> configuring ACP connect, configured remote ACP neighbors, etc.

Yes. i added (intended to be) independent of configuration.

Hope i don't need to add more explanations to the fact that we need
to distinguish between functionality we can fully automate without
config and the aspects where we do not yet have such a solution.
In most networks, ACP is fully autonomic except for a few (redundant)
registars with ACP connect, so the real benefit is larger than
what the draft may make it look like.

> Section 10.2.2
> 
>       For BRSKI or other mechanisms using vouchers: Parameters to
>       determine how to retrieve vouchers for specific type of secure
>       bootstrap candidate ACP nodes (such as MASA URLs), unless this
>       information is automatically learned such as from the LDevID of
>       candidate ACP nodes (as defined in BRSKI).
>
> I thought the LDevID was essentially synonymous with "ACP domain
> certificate" in this document, so I can't understand what this means
> (unless IDevID was intended).

Yes, typo. IDevID was meant. The voucher RFC defined a MASA URL option.
Fixed.

> Section 10.2.3
> 
>    [...] And without additional centralized tracking of
>    assigned certificates there is no way to do this - assuming one can
>    not retrieve this information from the .
> 
> Missing the end of the sentence?

Fixed in prior version (just removed the part starting from -, it was trash).

> Section 10.2.4
> 
>    Or let it expire and not renew it, when the certificate of the sub-CA
>    is appropriately short-lived.
> 
> This sort of sentiment has been highly controversial in other contexts
> (e.g., draft-nir-saag-star).  (Also, that's a sentence fragment.)

Fixed sentence intro: Alternatively one can let it expire and not renew it...

Wrt to controversy of short lived certificate: From my memory participating
in the effort as a co-author, the controversy is about not having working
automated certificate renewal systems where it is feasible to set cert
expiry times to the same time-scale are refresh/polling of CRL/OCSP updates.
Which seems to be typically in the order of minutes (15 minutes... 30 minutes).
With ACP+EST we feel very confident that the overall complexity of short lived
cert renewal is overall actually lower than CRL/OCSP polling. 

>    Therefore ACP domain membership for an ACP node enrolled from a
>    compromised ACP registrar will fail.
> 
> >From a compromised *and detected* registrar.

Fixed.

> Section 10.3.x
> 
> This whole section feels more like a sketch of an idea than a
> well-specified model or protocol.  It might be better if spun off into a
> separate document, with time spent to produce (e.g.) a YANG module or state
> machines for devices in various states.

This is based on operatsional experience gained from the commercial implementation
and extrapolating from here. Its certainly true that i would want to go overboard
in specificity in an informal text like this, because its a lot easier to nail
down details in a YANG model. I think it would be good to have this conceptual
description out in the field, so that we can get more people think about it
before finalizing a YANG model in a separate document.

I have no strong opinion about outsourcing this into a separate document
except that i have also heard WG participants wanting to have this information
in the ACP document. And it would be somewhat breaking the documentation
in a strange place. If you feel strongly about this, i would  suggest to
break out the whole section 10 into an ACP operational model document
as long as its clear that nobody would start raising the expectation that
the main ACP specification must have a normative reference to the new operational
document (but only an informational one)- because i really would like
to finish an ACP RFC, and i can already see how we're open the floodgates
for a lot more operation text when we move 10 into a separate document.

> Section 10.3.5.1
> 
>    [...] Automatic enablement of ACP/ANI in networks
>    where the operator does not only not want ACP/ANI but where he likely
>    never even heard of it could be quite irritating to him.  Especially
>    when "down" behavior is changed to "admin down".
> 
> The behavior mentioned in this last sentence really ought to be called out
> more clearly in the previous section as changing the semantics of existing
> administrative controls.

Not quite clear which section you mean, can you propose what text to insert
where ?  There is a lot of text in the earlier part of 10.3 discussing the
pro/cons of down vs. admin down.

> Section 10.3.7
> 
> The control names indicated within double quotes are mostly incomplete
> references; it seems better to say, e.g., """the "up-if-only" option for
> node-level ACP/ANI enablement""".

Not sure i completely understood what you meant. Pls. check.

Changed to for example: If the "up-if-only" option of that command is not selected,...

> Section 11
> 
>    An ACP is self-protecting and there is no need to apply configuration
>    to make it secure.  Its security therefore does not depend on
>    configuration.
> 
> It seems like there are some higher-level/potentially "external"
> configurations needed, including but not limited to: setting up the
> registrar, definng the Intent, assigning a ULA to use for the domain,
> policy for the CA issuing domain certificates, and any interaction with
> external systems that is needed.  (That is, a fully autonomous system would
> be totally self-contained, and thereby not of much use to the humans
> involved!)

Let me explain how us authors cam up with that statement.
Here is how simple/autonomic ANI (ACP+BRSKI) can be with existing spec alone:

|  -> Select an ANI server-router.
|     Configure "autonomic-network-server <domain-name>"
|               "autonomic-connect ethernet 1/1"
|  
|  -> Plug together a network of greenfield routers (no config, fresh from factory)
|     BRSKI bootstraps all routers, ACP comes up. No data-plane whatsoever.
|  
|  -> Connect management station to server-router ethernet 1/1
|     Manage / provision network through ACP using ssh/netconf/whatever
|  
|  Under the hood, server-router config simply creates an autonomic registrar
|  and a CA with self-signed root cert, allocates ULA prefix from domain-name,
|  an registers any greenfield devices registering. Then these devices
|  hop-by-hop create ACP.
|  
|  The CLI of a commercial ANI implementation is very similar and as simple.
 
Does this give you a better sense of the reasoning behing the statement made ?

As you said, if the operator wants more policies, he has to configure them,
but anything configured is either outside of scope of ACP (CA policies),
or it is explicitly from section 8 "support for Non-ACP components".

Alas, its hard to see the simplicity possible in the product when ony
reading the spec that specifies all the gory details of what happens
under the hood and of course needs to spend more on the difficult / non-autonomic
pieces than the main part which is simple and autonomic.

With hat being said, here is the rewritten initial statement to be hopefully
more precise:

   <t>After seeding an ACP by configuring at least one ACP registrar with routing-subdomain and a CA, an ACP is self-protecting and there is no need to apply configuration to make it secure.  Its security therefore does not depend on configuration. This does not include workarounds for non-autonomic components as explained in <xref target="workarounds"/>.

> "correct operation" to me usually means "this system is behaving as
> expected", but I think the intended usage here is more like "being operated
> and managed correctly".  I don't know if I'm enough of an outlier to make
> it not worth changing the text.

You did not give a reference for this concern. I could only find the following
text at the end of the security section:

| Fundamentally, security depends on correct operation, implementation and architecture.  Autonomic approaches such as the ACP largely eliminate the dependency on correct operation;

So i changed this as follows:

| <t>Fundamentally, security depends on avoiding operator and network operations automation mistakes, implementation and architecture.  Autonomic approaches such as the ACP largely eliminate operator mistakes and make it easier to recover from network operations mistakes. Implementation and architectural mistakes are still possible, as in all networking technologies.</t>

> I would like to see more text about the scope of damage that a compromised
> ACP node can do, and suggesting detection/remediation measures.

Ok, i have revisited and rewritten salient text about this in the security section
starting with "The ACP It is designed to enable automation of current network management and future autonomic peer-peer/distributed network automation" - up to above paragraph (Fundamentally...)

Please review. I hope it correctly captures the high-level aspect of the problem.

Most fundamentally: We started designing ACP against the expectation of future fully autonomic networks being very much an extrapolation of todays fully distributed services in networks (like routing) therefore having simple group-security. We did along te way recognize the growing interest in automation for entralized network manaement where it is simple to assign two clases of roles. Both of these models are easily realized with the ACP, but the more generic model encompassing a variety of more flexible authorization and role options is IMHO still open.

> Section 12
> 
>    Note that the objective format "SRV.<service-name>" is intended to be
>    used for any <service-name> that is an [RFC6335] registered service
>    name.  This is a proposed update to the GRASP registry subject to
>    future work and only mentioned here for informational purposed to
>    explain the unique format of the objective name.
> 
> I'm confused about what this is actually trying to say.  It sounds like it
> is actually registering SRV.est (in the previous paragraph), but following
> that up by saying that this isn't actually a real registered service name
> yet, and we're just registering the objective name proactively for future
> work?  If so, that does not seem like the correct thing to do.

I think this was answered by me on top of this mail.
We are registering a real service name. We just explain that we want to
simplify the future IANA registration process and hence we use service
names whose template format indicates rfc6335 pre-registered service-names

> Section A.2
> 
>    [...] This requires only that the BRSKI
>    registrar honors expired domain certificates and that the pledge
>    first attempts to perform TLS authentication for BRSKI bootstrap with
>    its expired domain certificate - and only reverts to its IDevID when
>    this fails.
> 
> The "first" is unclear -- perhaps "that the pledge attempts to perform TLS
> authentication for BRSKI bootstrap using its expired domain certificate
> before falling back to attempting to use its IDevID for BRSKI"?

Done. Thanks.

> Section A.4
> 
>       [...] RPL also has other scalability improvements,
>       such as selecting only a subset of peers instead of all possible
>       ones, and trickle support for information synchronization.
> 
> (But trickle support is not used in the ACP profile of RPL.)

Removed.

> Section A.8
> 
> This discussion of reusing preexisting MAC addresses violates the claim
> that the ACP-internal addresses are not guessable from the data plane.

True. I inserted this text on behalf of use cases brought to us authors,
which i think are primarily inside what those customers call physcially
secure environments, so i think derived work might be happy to compromise
more on security to improve ease of diagnostics.

If you ask me:

This documents security is really the best security we can do for the
original core use case of full autonomic peer-to-peer distributed
automation. All the follow-on work will either try to improve security
for more structured role-based automation and/or reduce security for
specific market segments to accelerate adoption.

----

Thanks a lot for your really very thorough and thoughtfull review.
I hope my answers are satisfactory and we can move forward with the
document.


From nobody Mon Mar 11 08:34:08 2019
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 9B068131111; Mon, 11 Mar 2019 08:34:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 RD_BGEngeuzC; Mon, 11 Mar 2019 08:34:00 -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 ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8621B128B01; Mon, 11 Mar 2019 08:34:00 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 204C2548859; Mon, 11 Mar 2019 16:33:56 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 1B856440036; Mon, 11 Mar 2019 16:33:56 +0100 (CET)
Date: Mon, 11 Mar 2019 16:33:56 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Sheng Jiang <jiangsheng@huawei.com>
Cc: Xun Xiao <Xun.Xiao@huawei.com>, "anima@ietf.org" <anima@ietf.org>, "anima-chairs@ietf.org" <anima-chairs@ietf.org>, Artur Hecker <Artur.Hecker@huawei.com>
Message-ID: <20190311153356.6s5tvlm5gb2yf2af@faui48f.informatik.uni-erlangen.de>
References: <5D36713D8A4E7348A7E10DF7437A4B929035710C@NKGEML515-MBX.china.huawei.com> <67C6AE5A0CF6AD45A8571ED3F6E802E413864642@lhreml507-mbb> <5D36713D8A4E7348A7E10DF7437A4B929037F998@NKGEML515-MBX.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B929037F998@NKGEML515-MBX.china.huawei.com>
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/MHPOanEEsr9byZ5l0gzBxTevx4E>
Subject: Re: [Anima] Call for agenda ANIMA @ IETF 104?? Prague
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Mar 2019 15:34:07 -0000

ACP update slot pls.

On Mon, Mar 11, 2019 at 11:31:10AM +0000, Sheng Jiang wrote:
> Hi, Xiao,
> 
> I can confirm your request. The chairs would allocate time according to the application situation and priority policy.
> 
> Regards,
> 
> Sheng
> 
> From: Xun Xiao
> Sent: Friday, March 08, 2019 7:39 PM
> To: Sheng Jiang <jiangsheng@huawei.com>; anima@ietf.org
> Cc: anima-chairs@ietf.org; Artur Hecker <Artur.Hecker@huawei.com>
> Subject: RE: Call for agenda ANIMA @ IETF 104?? Prague
> 
> Hi Sheng,
> 
> We would like to have a time slot to report the update we made for the information-distribution draft (including updates. Thanks.
> 
> 
> Name of time slot: Updates on Information Distribution in Autonomic Networking
> 
> Name of draft(s): draft-liu-anima-grasp-distribution-10
> 
> Time requested: 10 mins
> 
> Presenter name(s): Xun Xiao and Artur Hecker
> 
> Best Regards,
> 
> Xun Xiao (????)
> Advanced Wireless Technology Lab
> Munich Research Center
> 
> From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Sheng Jiang
> Sent: Friday, 8 March 2019 07:59
> To: anima@ietf.org<mailto:anima@ietf.org>
> Cc: anima-chairs@ietf.org<mailto:anima-chairs@ietf.org>
> Subject: [Anima] Call for agenda ANIMA @ IETF 104?? Prague
> 
> 
> Hi, all anima,
> 
> 
> 
> We have been allocated a session of 2-hour for the ANIMA WG meeting for IETF-104 (Prague) - Tuesday afternoon session I. We are now starting to collect agenda items for the session. Please send your request for agenda by March 14th, Thursday.
> 
> 
> 
> 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/>) requests for time slot by March 14th, Thursday and include:
> 
> 
> 
> Name of time slot:
> 
> Name of draft(s):
> 
> Time requested:
> 
> Presenter name(s):
> 
> 
> 
> More details about the IETF 104, Prague can be found at:
> 
> 
> 
> https://www.ietf.org/how/meetings/104/
> 
> 
> 
> 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 Mon Mar 11 10:44:18 2019
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 E485C1277D8; Mon, 11 Mar 2019 10:44:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level: 
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 U8ykd5gT1jAX; Mon, 11 Mar 2019 10:44:09 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A01A5131192; Mon, 11 Mar 2019 10:44:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12158; q=dns/txt; s=iport; t=1552326248; x=1553535848; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=miKi4Y05+fmsnNKGBmSl/nXSMgjeP6Xmh13aYaCbVGg=; b=fv6wqAV5z9IMRjw2pbzOV5K1g8Pxkn0LoaB0oYjx3R5Flen8td/PAEQ9 mONsaL7j4/a5mJWFYsMe47Ik6wFzDMi973TfCc55f6Pqozcn+38cRnNeI V5H2NeQnbI07YumSSFmwBmqusWyhkj9FbfvGJJ/RICS5N+czGxOZf5JFG o=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A3AAA9noZc/xbLJq1kGwEBAQEDAQE?= =?us-ascii?q?BBwMBAQGBVAMBAQELAYENgWpxEieECYh5jGGSM4duCAMBARgBCoRJAoRcNwY?= =?us-ascii?q?NAQEDAQEHAQMCbRwMhUoBAQEBAgEBARsGCkELBQsLGCoCAicwBhODIgGBbQg?= =?us-ascii?q?PsCeBL4QwAYEUhF0PgS8BgUiJe4F/gTgfgkyBQYFdAQGBQQEBgygxgiYDigi?= =?us-ascii?q?GaEySZQmEWYJ4izsZgXlYhQ6LW4M5jSSJdIJuAgQGBQIVgV0igVYzGggbFTs?= =?us-ascii?q?qAYINATMJNYFkiGqFQD4DMI4Cgj4BAQ?=
X-IronPort-AV: E=Sophos;i="5.58,468,1544486400";  d="asc'?scan'208,217";a="10677532"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 11 Mar 2019 17:44:05 +0000
Received: from ams3-vpn-dhcp7163.cisco.com (ams3-vpn-dhcp7163.cisco.com [10.61.91.250]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x2BHi3hx011500 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 11 Mar 2019 17:44:04 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <9BC436CD-D22C-419B-A16E-7D7C81AC12B0@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_9EF4E1C1-EDF1-4B1C-8162-462A4728E59D"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Mon, 11 Mar 2019 18:44:02 +0100
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B929035710C@NKGEML515-MBX.china.huawei.com>
Cc: "anima@ietf.org" <anima@ietf.org>, "anima-chairs@ietf.org" <anima-chairs@ietf.org>
To: Sheng Jiang <jiangsheng@huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B929035710C@NKGEML515-MBX.china.huawei.com>
X-Mailer: Apple Mail (2.3445.102.3)
X-Outbound-SMTP-Client: 10.61.91.250, ams3-vpn-dhcp7163.cisco.com
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/84MHCHZ6OJn9V0nxf0GT7UQfQwo>
Subject: Re: [Anima]  =?utf-8?q?Call_for_agenda_ANIMA_=40_IETF_104=EF=BC=8C_Pr?= =?utf-8?q?ague?=
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Mar 2019 17:44:18 -0000

--Apple-Mail=_9EF4E1C1-EDF1-4B1C-8162-462A4728E59D
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_DFB98FF2-B41A-4737-B8B2-8F2EC07CBB33"


--Apple-Mail=_DFB98FF2-B41A-4737-B8B2-8F2EC07CBB33
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Sheng Jiang,

I think we had a lengthy conversation about BRSKI next steps, and that =
we should expect to spend some time on this in ANIMA.  I think I count =
at least four drafts that are worth considering, and Michael might have =
more in mind:

Draft-vanderstock-anima-constrained-join-proxy
Draft-lear-eap-teap-brski
Draft-ietf-6tisch-{=E2=80=A6}
Draft-fries-anima-brski-async-enroll

How would you like to organise that conversation?

Eliot


> On 8 Mar 2019, at 07:59, Sheng Jiang <jiangsheng@huawei.com> wrote:
>=20
> Hi, all anima,
>=20
> We have been allocated a session of 2-hour for the ANIMA WG meeting =
for IETF-104 (Prague) - Tuesday afternoon session I. We are now starting =
to collect agenda items for the session. Please send your request for =
agenda by March 14th, Thursday.
>=20
> 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.
>=20
> Please send us (anima-chairs at ietf.org <https://ietf.org/>) requests =
for time slot by March 14th, Thursday and include:
>=20
> Name of time slot:
> Name of draft(s):
> Time requested:
> Presenter name(s):
>=20
> More details about the IETF 104, Prague can be found at:
>=20
> https://www.ietf.org/how/meetings/104/
>=20
> 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.
>=20
> Best regards,
>=20
> Toerless & Sheng
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima


--Apple-Mail=_DFB98FF2-B41A-4737-B8B2-8F2EC07CBB33
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Sheng Jiang,<div class=3D""><br class=3D""></div><div class=3D"">I think =
we had a lengthy conversation about BRSKI next steps, and that we should =
expect to spend some time on this in ANIMA. &nbsp;I think I count at =
least four drafts that are worth considering, and Michael might have =
more in mind:</div><div class=3D""><br class=3D""></div><div =
class=3D""><ul class=3D"MailOutline"><li =
class=3D"">Draft-vanderstock-anima-constrained-join-proxy</li><li =
class=3D"">Draft-lear-eap-teap-brski</li><li =
class=3D"">Draft-ietf-6tisch-{=E2=80=A6}</li><li =
class=3D"">Draft-fries-anima-brski-async-enroll</li></ul><div =
class=3D""><br class=3D""></div></div><div class=3D"">How would you like =
to organise that conversation?</div><div class=3D""><br =
class=3D""></div><div class=3D"">Eliot</div><div class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 8 Mar 2019, at 07:59, Sheng Jiang &lt;<a =
href=3D"mailto:jiangsheng@huawei.com" =
class=3D"">jiangsheng@huawei.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D"">
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312" =
class=3D"">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)" =
class=3D"">
<style class=3D""><!--
/* Font Definitions */
@font-face
	{font-family:=E5=AE=8B=E4=BD=93;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
	{font-family:"\@=E5=AE=8B=E4=BD=93";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* 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 =E9=A2=84=E8=AE=BE=E6=A0=BC=E5=BC=8F Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:=E5=AE=8B=E4=BD=93;}
span.HTMLChar
	{mso-style-name:"HTML =E9=A2=84=E8=AE=BE=E6=A0=BC=E5=BC=8F =
Char";
	mso-style-priority:99;
	mso-style-link:"HTML =E9=A2=84=E8=AE=BE=E6=A0=BC=E5=BC=8F";
	font-family:=E5=AE=8B=E4=BD=93;}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
..MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	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]-->

<div lang=3D"ZH-CN" link=3D"#0563C1" vlink=3D"#954F72" =
style=3D"text-justify-trim:punctuation" class=3D"">
<div class=3D"WordSection1">
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D"">Hi, all anima,<o:p class=3D""></o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" class=3D"">We=
 have been allocated a session of 2-hour for the ANIMA WG meeting for =
IETF-104 (Prague) - Tuesday afternoon session I. We are now starting to =
collect agenda items for the session. Please send your request for =
agenda by March 14th, Thursday.<o:p class=3D""></o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D"">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.<o:p =
class=3D""></o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D"">Please send us (anima-chairs at <a href=3D"https://ietf.org/" =
class=3D""><span style=3D"color:#337AB7" class=3D"">ietf.org</span></a>) =
requests for time slot by March 14th, Thursday and include:<o:p =
class=3D""></o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D"">Name of time slot:<o:p class=3D""></o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D"">Name of draft(s):<o:p class=3D""></o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D"">Time requested:<o:p class=3D""></o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D"">Presenter name(s):<o:p class=3D""></o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D"">More details about the IETF 104, Prague can be found at:<o:p =
class=3D""></o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" class=3D""><a=
 href=3D"https://www.ietf.org/how/meetings/104/" =
class=3D"">https://www.ietf.org/how/meetings/104/</a><o:p =
class=3D""></o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D"">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.<o:p =
class=3D""></o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D"">Best regards,<o:p class=3D""></o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></pre>
<pre style=3D"background:white" class=3D""><span lang=3D"EN-US" =
style=3D"font-size:9.0pt;font-family:Consolas;color:#212529" =
class=3D"">Toerless &amp; Sheng<o:p class=3D""></o:p></span></pre>
</div>
</div>

_______________________________________________<br class=3D"">Anima =
mailing list<br class=3D""><a href=3D"mailto:Anima@ietf.org" =
class=3D"">Anima@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/anima<br =
class=3D""></div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_DFB98FF2-B41A-4737-B8B2-8F2EC07CBB33--

--Apple-Mail=_9EF4E1C1-EDF1-4B1C-8162-462A4728E59D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQEzBAEBCAAdFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAlyGnmIACgkQh7ZrRtnS
ejPDvggAwhiggPkL9O854SgYrfNw2n427AolOxod4DI2azGFKK7oDP07UbqmgL3A
GnAjIKfzpwWPSYESfRLZbDBF1LIoANj6Ue5IqZS2BIXthOyvtAcsALVesbLP/XEZ
po6vTCXT+SZ7BGUBCJjHyI76fENOMeNLjBvDfvtCuvRw39UOqcCfIhAWIhcxbWxu
KaLvGLmcOWcWT3p7J8QjzNL4rsNsiz3019UEXgyEniY7bq2Pbf5+cEU5XcV6SDQY
KecFkir/qN3sWpN2U8UR3WTdKDcIS2GIFjKw21P72UStF5SW4TuWKfC4JmiZDlaJ
c/ssjME3oXc+7Mh1KhLPQBBPJL4KFQ==
=vYv6
-----END PGP SIGNATURE-----

--Apple-Mail=_9EF4E1C1-EDF1-4B1C-8162-462A4728E59D--


From nobody Mon Mar 11 12:34:49 2019
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 8037C131047; Mon, 11 Mar 2019 12:34:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 VyzYpy9Xa6Co; Mon, 11 Mar 2019 12:34:47 -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 E6093126D00; Mon, 11 Mar 2019 12:34:46 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id 6D20338263; Mon, 11 Mar 2019 15:34:30 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 32C4AA3A; Mon, 11 Mar 2019 15:34:45 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 30297797; Mon, 11 Mar 2019 15:34:45 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Eliot Lear <lear@cisco.com>
cc: Sheng Jiang <jiangsheng@huawei.com>, "anima-chairs\@ietf.org" <anima-chairs@ietf.org>, "anima\@ietf.org" <anima@ietf.org>
In-Reply-To: <9BC436CD-D22C-419B-A16E-7D7C81AC12B0@cisco.com>
References: <5D36713D8A4E7348A7E10DF7437A4B929035710C@NKGEML515-MBX.china.huawei.com> <9BC436CD-D22C-419B-A16E-7D7C81AC12B0@cisco.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; 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, 11 Mar 2019 15:34:45 -0400
Message-ID: <18611.1552332885@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/g8IRtQrWoOOfnRm6LTPF_ycJTO4>
Subject: Re: [Anima]  =?utf-8?q?Call_for_agenda_ANIMA_=40_IETF_104=EF=BC=8C__P?= =?utf-8?q?rague?=
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Mar 2019 19:34:48 -0000

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


Eliot Lear <lear@cisco.com> wrote:
    > I think we had a lengthy conversation about BRSKI next steps, and tha=
t we
    > should expect to spend some time on this in ANIMA. I think I count at=
 least
    > four drafts that are worth considering, and Michael might have more i=
n mind:

    > * Draft-vanderstock-anima-constrained-join-proxy
    > * Draft-lear-eap-teap-brski
    > * Draft-ietf-6tisch-{=E2=80=A6}

    > * Draft-fries-anima-brski-async-enroll
{Eliot: Does this document include Oskar's requirements?}

Additional documents that call on BRSKI:

* draft-richardson-anima-smarkaklink (formerly draft-richardson-anima-smart=
pledge)
   -> I have revised slides, and I walk to talka bout them.
      I believe that it solves draft-fries-anima-brski-async-enroll as well,
      but I haven't read the entire document yet.

* draft-reddy-dprive-bootstrap-dns-server
* draft-boucadair-dots-server-discovery
  --> some details are still TBD.

=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-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlyGuFQACgkQgItw+93Q
3WXT+wgAob9jXwNfeVLHitpwkBwmQg90e6hEfjGHWwDDuTsWxepmwcDgFzQ5a/H6
qBFw8va64Xf+kBOCDkgzWHB4LdmU/bcqoCHIoyCueVked984GBZsxrJyXk33Ul4M
JCg+9e2qnTEDAcyLcncweW3KadgAO7zw25QUdzfqCfaAhROdPDRd3Biifevv1KsP
iCytNB7z3pVzNHoxwJOERXkz4ZxGedTgzjhXmezltGtV+MGuCzPzR5AxPJSFgXY9
kXHf3E3L38EPzWSGxyJ24cEkhy3YVh62s+xJ44L5TDE92DLW4zSHGgebyYV/Hcxy
tnOVPwDHJ6BG1nThXqiymTImsMJd3Q==
=tYdT
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Mar 11 18:55:01 2019
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 4DF131311EA; Mon, 11 Mar 2019 18:54:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 iMQxc_Npf51T; Mon, 11 Mar 2019 18:54:45 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 BF63B12D550; Mon, 11 Mar 2019 18:54:44 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 8CDB67BF77AAA7A66BAA; Tue, 12 Mar 2019 01:54:42 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 12 Mar 2019 01:54:41 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0415.000; Tue, 12 Mar 2019 09:54:37 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, Eliot Lear <lear@cisco.com>
CC: "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "anima@ietf.org" <anima@ietf.org>
Thread-Topic: =?utf-8?B?W0FuaW1hXSBDYWxsIGZvciBhZ2VuZGEgQU5JTUEgQCBJRVRGIDEwNO+8jCBQ?= =?utf-8?Q?rague?=
Thread-Index: AdTVSp7fUdNBEg1lSfyRueXgFJmsUwCpFaIAAAPd4oAAHPP14A==
Date: Tue, 12 Mar 2019 01:54:37 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B9290384DBB@NKGEML515-MBX.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B929035710C@NKGEML515-MBX.china.huawei.com> <9BC436CD-D22C-419B-A16E-7D7C81AC12B0@cisco.com> <18611.1552332885@localhost>
In-Reply-To: <18611.1552332885@localhost>
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: 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/D09dNnbStxSGwhTGT3wq4wymlb4>
Subject: Re: [Anima]  =?utf-8?q?Call_for_agenda_ANIMA_=40_IETF_104=EF=BC=8C_Pr?= =?utf-8?q?ague?=
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Mar 2019 01:54:50 -0000

SGksIEVsaW90ICYgTWljaGFlbCBSLg0KDQpUaGFua3MgZm9yIHlvdXIgZW1haWwuIEkgY29uZmly
bSB5b3VyIHJlcXVlc3QgYW5kIGFsc28gdGhlIHByaW9yaXR5IG9mIEJSU0tJIHJlbGV2YW50IGRp
c2N1c3Npb24uIEl0IHdvdWxkIGZvbGxvdyBqdXN0IGFmdGVyIHRoZSBXRyBkb2N1bWVudHMgdXBk
YXRlIGFuZCBXRyByZS1jaGFydGVyaW5nIHVuc2NyYW1ibGluZy4gQWN0dWFsbHksIEkgYWdyZWUg
dGhlIGRpc2N1c3Npb24gb2YgQlJTS0kgbmV4dCBzdGVwcyBpcyBwYXJ0IG9mIFdHIHJlY2hhcnRl
ci4gV2UgY291bGQgc2tpcCB0aGUgQlJTS0kgcGFydCBpbiB0aGUgcmUtY2hhcnRlcmluZyB1bnNj
cmFtYmxpbmcuDQoNClJlZ2FyZHMsDQoNClNoZW5nDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdl
LS0tLS0NCj4gRnJvbTogTWljaGFlbCBSaWNoYXJkc29uIFttYWlsdG86bWNyK2lldGZAc2FuZGVs
bWFuLmNhXQ0KPiBTZW50OiBUdWVzZGF5LCBNYXJjaCAxMiwgMjAxOSAzOjM1IEFNDQo+IFRvOiBF
bGlvdCBMZWFyIDxsZWFyQGNpc2NvLmNvbT4NCj4gQ2M6IFNoZW5nIEppYW5nIDxqaWFuZ3NoZW5n
QGh1YXdlaS5jb20+OyBhbmltYS1jaGFpcnNAaWV0Zi5vcmc7DQo+IGFuaW1hQGlldGYub3JnDQo+
IFN1YmplY3Q6IFJlOiBbQW5pbWFdIENhbGwgZm9yIGFnZW5kYSBBTklNQSBAIElFVEYgMTA077yM
IFByYWd1ZQ0KPiANCj4gDQo+IEVsaW90IExlYXIgPGxlYXJAY2lzY28uY29tPiB3cm90ZToNCj4g
ICAgID4gSSB0aGluayB3ZSBoYWQgYSBsZW5ndGh5IGNvbnZlcnNhdGlvbiBhYm91dCBCUlNLSSBu
ZXh0IHN0ZXBzLCBhbmQgdGhhdCB3ZQ0KPiAgICAgPiBzaG91bGQgZXhwZWN0IHRvIHNwZW5kIHNv
bWUgdGltZSBvbiB0aGlzIGluIEFOSU1BLiBJIHRoaW5rIEkgY291bnQgYXQgbGVhc3QNCj4gICAg
ID4gZm91ciBkcmFmdHMgdGhhdCBhcmUgd29ydGggY29uc2lkZXJpbmcsIGFuZCBNaWNoYWVsIG1p
Z2h0IGhhdmUgbW9yZSBpbg0KPiBtaW5kOg0KPiANCj4gICAgID4gKiBEcmFmdC12YW5kZXJzdG9j
ay1hbmltYS1jb25zdHJhaW5lZC1qb2luLXByb3h5DQo+ICAgICA+ICogRHJhZnQtbGVhci1lYXAt
dGVhcC1icnNraQ0KPiAgICAgPiAqIERyYWZ0LWlldGYtNnRpc2NoLXvigKZ9DQo+IA0KPiAgICAg
PiAqIERyYWZ0LWZyaWVzLWFuaW1hLWJyc2tpLWFzeW5jLWVucm9sbA0KPiB7RWxpb3Q6IERvZXMg
dGhpcyBkb2N1bWVudCBpbmNsdWRlIE9za2FyJ3MgcmVxdWlyZW1lbnRzP30NCj4gDQo+IEFkZGl0
aW9uYWwgZG9jdW1lbnRzIHRoYXQgY2FsbCBvbiBCUlNLSToNCj4gDQo+ICogZHJhZnQtcmljaGFy
ZHNvbi1hbmltYS1zbWFya2FrbGluayAoZm9ybWVybHkNCj4gZHJhZnQtcmljaGFyZHNvbi1hbmlt
YS1zbWFydHBsZWRnZSkNCj4gICAgLT4gSSBoYXZlIHJldmlzZWQgc2xpZGVzLCBhbmQgSSB3YWxr
IHRvIHRhbGthIGJvdXQgdGhlbS4NCj4gICAgICAgSSBiZWxpZXZlIHRoYXQgaXQgc29sdmVzIGRy
YWZ0LWZyaWVzLWFuaW1hLWJyc2tpLWFzeW5jLWVucm9sbCBhcyB3ZWxsLA0KPiAgICAgICBidXQg
SSBoYXZlbid0IHJlYWQgdGhlIGVudGlyZSBkb2N1bWVudCB5ZXQuDQo+IA0KPiAqIGRyYWZ0LXJl
ZGR5LWRwcml2ZS1ib290c3RyYXAtZG5zLXNlcnZlcg0KPiAqIGRyYWZ0LWJvdWNhZGFpci1kb3Rz
LXNlcnZlci1kaXNjb3ZlcnkNCj4gICAtLT4gc29tZSBkZXRhaWxzIGFyZSBzdGlsbCBUQkQuDQo+
IA0KPiAtLQ0KPiBNaWNoYWVsIFJpY2hhcmRzb24gPG1jcitJRVRGQHNhbmRlbG1hbi5jYT4sIFNh
bmRlbG1hbiBTb2Z0d2FyZSBXb3JrcyAgLT0NCj4gSVB2NiBJb1QgY29uc3VsdGluZyA9LQ0K


From nobody Mon Mar 11 21:00:36 2019
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 C2DFA130E6D; Mon, 11 Mar 2019 21:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 EV_1eJUUUOQO; Mon, 11 Mar 2019 21:00:18 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 AC764130EB1; Mon, 11 Mar 2019 21:00:18 -0700 (PDT)
Received: from LHREML714-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 96A0854FB838259EDA2F; Tue, 12 Mar 2019 04:00:16 +0000 (GMT)
Received: from lhreml703-chm.china.huawei.com (10.201.108.52) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 12 Mar 2019 04:00:16 +0000
Received: from lhreml703-chm.china.huawei.com (10.201.108.52) by lhreml703-chm.china.huawei.com (10.201.108.52) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Tue, 12 Mar 2019 04:00:16 +0000
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml703-chm.china.huawei.com (10.201.108.52) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1591.10 via Frontend Transport; Tue, 12 Mar 2019 04:00:15 +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.0415.000; Tue, 12 Mar 2019 12:00:04 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Toerless Eckert <tte@cs.fau.de>
CC: Xun Xiao <Xun.Xiao@huawei.com>, "anima@ietf.org" <anima@ietf.org>, "anima-chairs@ietf.org" <anima-chairs@ietf.org>, Artur Hecker <Artur.Hecker@huawei.com>
Thread-Topic: [Anima] Call for agenda ANIMA @ IETF 104?? Prague
Thread-Index: AQHU2B/gBXTLajmLt02ejk6Akkdnu6YHX8rg
Date: Tue, 12 Mar 2019 04:00:04 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B9290384FBF@NKGEML515-MBX.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B929035710C@NKGEML515-MBX.china.huawei.com> <67C6AE5A0CF6AD45A8571ED3F6E802E413864642@lhreml507-mbb> <5D36713D8A4E7348A7E10DF7437A4B929037F998@NKGEML515-MBX.china.huawei.com> <20190311153356.6s5tvlm5gb2yf2af@faui48f.informatik.uni-erlangen.de>
In-Reply-To: <20190311153356.6s5tvlm5gb2yf2af@faui48f.informatik.uni-erlangen.de>
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: 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/UeZwVhE8w5zDM_ofjli3CynL3k4>
Subject: Re: [Anima] Call for agenda ANIMA @ IETF 104?? Prague
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Mar 2019 04:00:22 -0000

Hi, Toerless,

Your request is noted.

Regards,

Sheng

> -----Original Message-----
> From: Toerless Eckert [mailto:tte@cs.fau.de]
> Sent: Monday, March 11, 2019 11:34 PM
> To: Sheng Jiang <jiangsheng@huawei.com>
> Cc: Xun Xiao <Xun.Xiao@huawei.com>; anima@ietf.org; anima-chairs@ietf.org=
;
> Artur Hecker <Artur.Hecker@huawei.com>
> Subject: Re: [Anima] Call for agenda ANIMA @ IETF 104?? Prague
>=20
> ACP update slot pls.
>=20
> On Mon, Mar 11, 2019 at 11:31:10AM +0000, Sheng Jiang wrote:
> > Hi, Xiao,
> >
> > I can confirm your request. The chairs would allocate time according to=
 the
> application situation and priority policy.
> >
> > Regards,
> >
> > Sheng
> >
> > From: Xun Xiao
> > Sent: Friday, March 08, 2019 7:39 PM
> > To: Sheng Jiang <jiangsheng@huawei.com>; anima@ietf.org
> > Cc: anima-chairs@ietf.org; Artur Hecker <Artur.Hecker@huawei.com>
> > Subject: RE: Call for agenda ANIMA @ IETF 104?? Prague
> >
> > Hi Sheng,
> >
> > We would like to have a time slot to report the update we made for the
> information-distribution draft (including updates. Thanks.
> >
> >
> > Name of time slot: Updates on Information Distribution in Autonomic
> Networking
> >
> > Name of draft(s): draft-liu-anima-grasp-distribution-10
> >
> > Time requested: 10 mins
> >
> > Presenter name(s): Xun Xiao and Artur Hecker
> >
> > Best Regards,
> >
> > Xun Xiao (????)
> > Advanced Wireless Technology Lab
> > Munich Research Center
> >
> > From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Sheng Jiang
> > Sent: Friday, 8 March 2019 07:59
> > To: anima@ietf.org<mailto:anima@ietf.org>
> > Cc: anima-chairs@ietf.org<mailto:anima-chairs@ietf.org>
> > Subject: [Anima] Call for agenda ANIMA @ IETF 104?? Prague
> >
> >
> > Hi, all anima,
> >
> >
> >
> > We have been allocated a session of 2-hour for the ANIMA WG meeting for
> IETF-104 (Prague) - Tuesday afternoon session I. We are now starting to c=
ollect
> agenda items for the session. Please send your request for agenda by Marc=
h
> 14th, Thursday.
> >
> >
> >
> > For this coming meeting, we would like to discuss potential future ANIM=
A
> works. As normal, the priority among these non-charter work items would b=
e:
> 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/>) requests f=
or time
> slot by March 14th, Thursday and include:
> >
> >
> >
> > Name of time slot:
> >
> > Name of draft(s):
> >
> > Time requested:
> >
> > Presenter name(s):
> >
> >
> >
> > More details about the IETF 104, Prague can be found at:
> >
> >
> >
> > https://www.ietf.org/how/meetings/104/
> >
> >
> >
> > 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
>=20
> > _______________________________________________
> > Anima mailing list
> > Anima@ietf.org
> > https://www.ietf.org/mailman/listinfo/anima


From nobody Mon Mar 11 22:41:08 2019
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 488F6130ECE; Mon, 11 Mar 2019 22:41:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 Jl9X0v8xd5Md; Mon, 11 Mar 2019 22:41:04 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE791130EE6; Mon, 11 Mar 2019 22:41:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3037; q=dns/txt; s=iport; t=1552369264; x=1553578864; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=AIjXdsqdlAzMKz08VxfAs5kkagfLUwGPi/vXEaOS7Lc=; b=ESY4CtY086c4N2vTekQ575OeUS1+6zNu43HbW5O1wUzi35U36oZZ5/yD Wkdjgb4+12QqWNQACH/qEUMDEjZhhu9Y/5bmsNRPerOJjP7BRwp0IW52w ViNUF2gcvtA4vCiIofLayEK409z24cv2J4VuZsBw9VHl7ECSMLBQQpZdV I=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADAACMRYdc/xbLJq1kGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUQQBAQEBAQsBgWWBYiESJ4QKiBpfjEAlmCoUgWcIAwE?= =?us-ascii?q?BgXeCdQKEXDQJDQEBAwEBCQEDAm0ohUoBAQEDAR0GBFIFBwQLEQQBAQEnAwI?= =?us-ascii?q?CRgkIBhODIgGBbQiwNHwzhUWEcQ+BLwGBSIl7gX+BOAwTgkyBQYMNARIBCYM?= =?us-ascii?q?gMYImA4oMhzSSaQmEWo43GYF5iS6IFIM5iFOOTYJuAgQGBQIVgUc4ZXEzGgg?= =?us-ascii?q?bFWUBgkE+gWSBCwEHjRc+AzCOBYI+AQE?=
X-IronPort-AV: E=Sophos;i="5.58,469,1544486400";  d="asc'?scan'208";a="10629321"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 12 Mar 2019 05:41:01 +0000
Received: from ams3-vpn-dhcp7163.cisco.com (ams3-vpn-dhcp7163.cisco.com [10.61.91.250]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x2C5f0Ui012277 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 12 Mar 2019 05:41:01 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <B91131F7-1BF0-4658-A006-2438239A6915@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_B552BC60-3432-4030-8EB7-3C3942BE1A75"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Tue, 12 Mar 2019 06:40:59 +0100
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B9290384DBB@NKGEML515-MBX.china.huawei.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "anima@ietf.org" <anima@ietf.org>
To: Sheng Jiang <jiangsheng@huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B929035710C@NKGEML515-MBX.china.huawei.com> <9BC436CD-D22C-419B-A16E-7D7C81AC12B0@cisco.com> <18611.1552332885@localhost> <5D36713D8A4E7348A7E10DF7437A4B9290384DBB@NKGEML515-MBX.china.huawei.com>
X-Mailer: Apple Mail (2.3445.102.3)
X-Outbound-SMTP-Client: 10.61.91.250, ams3-vpn-dhcp7163.cisco.com
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/5CTmk1Hc_M0iD_JC-qk5Egn_ij8>
Subject: Re: [Anima]  =?utf-8?q?Call_for_agenda_ANIMA_=40_IETF_104=EF=BC=8C_Pr?= =?utf-8?q?ague?=
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Mar 2019 05:41:06 -0000

--Apple-Mail=_B552BC60-3432-4030-8EB7-3C3942BE1A75
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Sheng,

> On 12 Mar 2019, at 02:54, Sheng Jiang <jiangsheng@huawei.com> wrote:
>=20
> Hi, Eliot & Michael R.
>=20
> Thanks for your email. I confirm your request and also the priority of =
BRSKI relevant discussion. It would follow just after the WG documents =
update and WG re-chartering unscrambling. Actually, I agree the =
discussion of BRSKI next steps is part of WG recharter. We could skip =
the BRSKI part in the re-chartering unscrambling.

Thank you.  I think this is an important aspect of the recharter.

Eliot


>=20
> Regards,
>=20
> Sheng
>=20
>> -----Original Message-----
>> From: Michael Richardson [mailto:mcr+ietf@sandelman.ca]
>> Sent: Tuesday, March 12, 2019 3:35 AM
>> To: Eliot Lear <lear@cisco.com>
>> Cc: Sheng Jiang <jiangsheng@huawei.com>; anima-chairs@ietf.org;
>> anima@ietf.org
>> Subject: Re: [Anima] Call for agenda ANIMA @ IETF 104=EF=BC=8C Prague
>>=20
>>=20
>> Eliot Lear <lear@cisco.com> wrote:
>>> I think we had a lengthy conversation about BRSKI next steps, and =
that we
>>> should expect to spend some time on this in ANIMA. I think I count =
at least
>>> four drafts that are worth considering, and Michael might have more =
in
>> mind:
>>=20
>>> * Draft-vanderstock-anima-constrained-join-proxy
>>> * Draft-lear-eap-teap-brski
>>> * Draft-ietf-6tisch-{=E2=80=A6}
>>=20
>>> * Draft-fries-anima-brski-async-enroll
>> {Eliot: Does this document include Oskar's requirements?}
>>=20
>> Additional documents that call on BRSKI:
>>=20
>> * draft-richardson-anima-smarkaklink (formerly
>> draft-richardson-anima-smartpledge)
>>   -> I have revised slides, and I walk to talka bout them.
>>      I believe that it solves draft-fries-anima-brski-async-enroll as =
well,
>>      but I haven't read the entire document yet.
>>=20
>> * draft-reddy-dprive-bootstrap-dns-server
>> * draft-boucadair-dots-server-discovery
>>  --> some details are still TBD.
>>=20
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works  =
-=3D
>> IPv6 IoT consulting =3D-


--Apple-Mail=_B552BC60-3432-4030-8EB7-3C3942BE1A75
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQEzBAEBCAAdFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAlyHRmsACgkQh7ZrRtnS
ejOTqQgAyG+0AHHeDsV199jCbD56XsKR6kL8d5nVqek8HQ8vzYER7+wOqbBl6q9E
XUnDZRjqOCPcAfzkE6n5QKZDNXUza9LFAOsSrh9d1fSsNTZS+HFdu1H7aGtyYxsi
PS4D6bOKdNl3ZvubvnX+X+klYu+xgbiqx7K6v+TOJWfovZ20AW3jAm0Asuh6ycja
G8inDP9GkvvmAA1hXluY7hwZZ1wBav1Sw9Kq6yHNwlaGuekJGPWr1ADh7YhTQ5fi
jGJADwTHHqfnz5gtFnkjD7bBvXZDcS9EJ7Y9poqkwQ0SOURS74CVpM0IyGJAidA1
xaI6Wg2zVYVMm+LH8piFLlBSK1CLfA==
=vl7u
-----END PGP SIGNATURE-----

--Apple-Mail=_B552BC60-3432-4030-8EB7-3C3942BE1A75--


From nobody Tue Mar 12 01:23:22 2019
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 D8635130EEE; Tue, 12 Mar 2019 01:23:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 rRSeG_Iif1BB; Tue, 12 Mar 2019 01:23:19 -0700 (PDT)
Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) (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 AB793130E64; Tue, 12 Mar 2019 01:23:17 -0700 (PDT)
Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id x2C8N6G8020858 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 12 Mar 2019 09:23:06 +0100
Received: from DEFTHW99ERIMSX.ww902.siemens.net (defthw99erimsx.ww902.siemens.net [139.22.70.134]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTPS id x2C8N5tZ006950 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 12 Mar 2019 09:23:05 +0100
Received: from DENBGAT9ERQMSX.ww902.siemens.net (139.22.70.196) by DEFTHW99ERIMSX.ww902.siemens.net (139.22.70.134) with Microsoft SMTP Server (TLS) id 14.3.435.0; Tue, 12 Mar 2019 09:23:05 +0100
Received: from DENBGAT9EJ5MSX.ww902.siemens.net ([169.254.12.162]) by DENBGAT9ERQMSX.ww902.siemens.net ([139.22.70.196]) with mapi id 14.03.0435.000; Tue, 12 Mar 2019 09:23:04 +0100
From: "Fries, Steffen" <steffen.fries@siemens.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, Eliot Lear <lear@cisco.com>
CC: "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "anima@ietf.org" <anima@ietf.org>, Sheng Jiang <jiangsheng@huawei.com>
Thread-Topic: =?utf-8?B?W0FuaW1hXSAgQ2FsbCBmb3IgYWdlbmRhIEFOSU1BIEAgSUVURiAxMDTvvIwg?= =?utf-8?Q?_Prague?=
Thread-Index: AQHU2EGDXhh8Vqa1ZkGSLtFc5SijyKYHpodw
Date: Tue, 12 Mar 2019 08:23:03 +0000
Message-ID: <E6C9F0E527F94F4692731382340B33781540E0CA@DENBGAT9EJ5MSX.ww902.siemens.net>
References: <5D36713D8A4E7348A7E10DF7437A4B929035710C@NKGEML515-MBX.china.huawei.com> <9BC436CD-D22C-419B-A16E-7D7C81AC12B0@cisco.com> <18611.1552332885@localhost>
In-Reply-To: <18611.1552332885@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [139.22.70.47]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/b1Wf9RhV7mfoLUAD0gePDyEpwD4>
Subject: Re: [Anima]  =?utf-8?q?Call_for_agenda_ANIMA_=40_IETF_104=EF=BC=8C__P?= =?utf-8?q?rague?=
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Mar 2019 08:23:21 -0000

SGkgTWljaGFlbCwgaGkgRWxpb3QsDQoNCj4gRWxpb3QgTGVhciA8bGVhckBjaXNjby5jb20+IHdy
b3RlOg0KPiAgICAgPiBJIHRoaW5rIHdlIGhhZCBhIGxlbmd0aHkgY29udmVyc2F0aW9uIGFib3V0
IEJSU0tJIG5leHQgc3RlcHMsIGFuZCB0aGF0IHdlDQo+ICAgICA+IHNob3VsZCBleHBlY3QgdG8g
c3BlbmQgc29tZSB0aW1lIG9uIHRoaXMgaW4gQU5JTUEuIEkgdGhpbmsgSSBjb3VudCBhdCBsZWFz
dA0KPiAgICAgPiBmb3VyIGRyYWZ0cyB0aGF0IGFyZSB3b3J0aCBjb25zaWRlcmluZywgYW5kIE1p
Y2hhZWwgbWlnaHQgaGF2ZSBtb3JlIGluIG1pbmQ6DQo+IA0KPiAgICAgPiAqIERyYWZ0LXZhbmRl
cnN0b2NrLWFuaW1hLWNvbnN0cmFpbmVkLWpvaW4tcHJveHkNCj4gICAgID4gKiBEcmFmdC1sZWFy
LWVhcC10ZWFwLWJyc2tpDQo+ICAgICA+ICogRHJhZnQtaWV0Zi02dGlzY2gte+KApn0NCj4gDQo+
ICAgICA+ICogRHJhZnQtZnJpZXMtYW5pbWEtYnJza2ktYXN5bmMtZW5yb2xsDQo+IHtFbGlvdDog
RG9lcyB0aGlzIGRvY3VtZW50IGluY2x1ZGUgT3NrYXIncyByZXF1aXJlbWVudHM/fQ0KPiANCj4g
QWRkaXRpb25hbCBkb2N1bWVudHMgdGhhdCBjYWxsIG9uIEJSU0tJOg0KPiANCj4gKiBkcmFmdC1y
aWNoYXJkc29uLWFuaW1hLXNtYXJrYWtsaW5rIChmb3JtZXJseSBkcmFmdC1yaWNoYXJkc29uLWFu
aW1hLXNtYXJ0cGxlZGdlKQ0KPiAgICAtPiBJIGhhdmUgcmV2aXNlZCBzbGlkZXMsIGFuZCBJIHdh
bGsgdG8gdGFsa2EgYm91dCB0aGVtLg0KPiAgICAgICBJIGJlbGlldmUgdGhhdCBpdCBzb2x2ZXMg
ZHJhZnQtZnJpZXMtYW5pbWEtYnJza2ktYXN5bmMtZW5yb2xsIGFzIHdlbGwsDQo+ICAgICAgIGJ1
dCBJIGhhdmVuJ3QgcmVhZCB0aGUgZW50aXJlIGRvY3VtZW50IHlldC4NCkkganVzdCByZWFkIGFj
cm9zcyBkcmFmdC1yaWNoYXJkc29uLWFuaW1hLXNtYXJrYWtsaW5rIGFuZCB0byBteSB1bmRlcnN0
YW5kaW5nIGl0IGZvY3VzZXMgb24gdGhlIHZvdWNoZXIgZXhjaGFuZ2UgaW4gc2l0dWF0aW9ucyB3
aGVyZSB0aGUgZG9tYWluIHJlZ2lzdHJhciBpcyBvbmx5IHRlbXBvcmFyeSBhdmFpbGFibGUuIFRo
ZSB2b3VjaGVyIGV4Y2hhbmdlIGlzIGN1cnJlbnRseSBvbmx5IHRvdWNoZWQgIGluIGRyYWZ0LWZy
aWVzLWFuaW1hLWJyc2tpLWFzeW5jLWVucm9sbCBmb3IgdGhlIHZvdWNoZXIgZXhjaGFuZ2UsIHdo
aWxlIHRoZSBtYWluIGZvY3VzIGlzIG9uIHRoZSBjZXJ0aWZpY2F0aW9uIHJlcXVlc3QvcmVzcG9u
c2UgZXhjaGFuZ2UuIEl0IGlzIGJhc2VkIG9uIGEgc2VsZi1jb250YWluZWQgb2JqZWN0IGJpbmRp
bmcgdGhlIGluaXRpYWwgcGxlZGdlIGF1dGhlbnRpY2F0aW9uIHRvIHRoZSBjZXJ0aWZpY2F0aW9u
IHJlcXVlc3QgYWxsb3dpbmcgdG8gcGVyZm9ybSB0aGUgYXV0aG9yaXphdGlvbiBvZiB0aGUgY2Vy
dGlmaWNhdGlvbiByZXF1ZXN0IGluIGEgZGlmZmVyZW50IGNvbXBvbmVudCB0aGFuIGEgbG9jYWwg
ZG9tYWluIHJlZ2lzdHJhci4gSW4gdGhhdCBhc3BlY3QgaXQgaGFzIGEgZGlmZmVyZW50IHNjb3Bl
IHRoYW4gZHJhZnQtcmljaGFyZHNvbi1hbmltYS1zbWFya2FrbGluay4gDQoNCkJlc3QgcmVnYXJk
cw0KU3RlZmZlbg0KDQoNCg0KPiANCj4gKiBkcmFmdC1yZWRkeS1kcHJpdmUtYm9vdHN0cmFwLWRu
cy1zZXJ2ZXINCj4gKiBkcmFmdC1ib3VjYWRhaXItZG90cy1zZXJ2ZXItZGlzY292ZXJ5DQo+ICAg
LS0+IHNvbWUgZGV0YWlscyBhcmUgc3RpbGwgVEJELg0KPiANCj4gLS0NCj4gTWljaGFlbCBSaWNo
YXJkc29uIDxtY3IrSUVURkBzYW5kZWxtYW4uY2E+LCBTYW5kZWxtYW4gU29mdHdhcmUgV29ya3Mg
IC09IElQdjYgSW9UIGNvbnN1bHRpbmcgPS0NCg==


From nobody Tue Mar 12 14:24:43 2019
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 8ADBE1240D3 for <anima@ietfa.amsl.com>; Tue, 12 Mar 2019 14:24:41 -0700 (PDT)
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 UNoJ1N3mVTFR for <anima@ietfa.amsl.com>; Tue, 12 Mar 2019 14:24:39 -0700 (PDT)
Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) (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 B7115127873 for <anima@ietf.org>; Tue, 12 Mar 2019 14:24:39 -0700 (PDT)
Received: by mail-pf1-x430.google.com with SMTP id n22so2753849pfa.3 for <anima@ietf.org>; Tue, 12 Mar 2019 14:24:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=xkH8wIJPAdO0rvAmPg2vDfT/0gdEMClz/lAzDRWs1yM=; b=HbryFROdSM9qdSWApluuoenLm/hvroPs9/gCcivC0+DKXeun5QNKnGBHeO+SxtqTwv Ne+p1Nir6R5i0XHQWvUkmTB/92WcSladTDZeGZXtFXQ2wSEBihe5RvGr9MjSN2fs6gt7 OJlIi5AW2KcRmoT4xjaZqF2YBNCqdr0DXKrnFXq5D9lPSrOsbUJUaax0e2iluxs9VMk6 ALkCx5SIfXvVYkKGail9RqDi2QxVuugBBm63Qt7iHh3BfmSfzy6cXUA8WZY18xILcJiB Gtgk+Flvci6l2kq2LAj196Fm2rnsP9DJash+EAXuT3+9hxCFId8mFg5gUyudOAwhFHZH 2oZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=xkH8wIJPAdO0rvAmPg2vDfT/0gdEMClz/lAzDRWs1yM=; b=QFqgkZWpfm6Nn2owkqDTPtv7+wfElbRTEDGZl4yOl0VnzujfB4E5259Vt1/xrdJSVo capPvRNItaQatX9d4MaRNyMTS8SO4pX6SridHaAW8pCjIM70/MuuEtRAIvfLGsP3UTwG F5Ek4bfn9lGLfJk83guJhAWqxqncc8bw5QHi54loo7xhC4wCBjfSVb758GJLJLugJLKe nfhffpR6X6l2ebl2uw0GfmbqgVWGPPe6PkOtzJOgyL6C1c441Sxcf59etN6UF8oEhOLz Be4ueE+u0uDxFg2kfLDWBSI1MWdJ/LVJwqTQ6ZdC0xuNWu/OtjX7MTkQdJR0J3Cuo2az Z3/g==
X-Gm-Message-State: APjAAAWagOhVqT+BrK/YYnoXrKQnG77CPYChaUoyOIPzu3ZMXi1yf9+Y oJoiNqJbVKrG0RSXRfkXRgZ0Fz4z
X-Google-Smtp-Source: APXvYqyibWD7AsU0E0tl/Dwt5oGL1v1tJVAOArgioMX41PQHLxXfAuthy5Qd6VvAl4uDF6MG39EMRA==
X-Received: by 2002:a63:1260:: with SMTP id 32mr37242885pgs.278.1552425878696;  Tue, 12 Mar 2019 14:24:38 -0700 (PDT)
Received: from [130.216.36.127] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.36.127]) by smtp.gmail.com with ESMTPSA id c13sm27115825pfm.34.2019.03.12.14.24.36 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Mar 2019 14:24:38 -0700 (PDT)
To: Anima WG <anima@ietf.org>
References: <155229792081.16909.926731018863391018@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <0a80e773-0b4a-6f31-25a7-d533e6c20596@gmail.com>
Date: Wed, 13 Mar 2019 10:24:36 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3
MIME-Version: 1.0
In-Reply-To: <155229792081.16909.926731018863391018@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/x-AcrdS9BYdXWnuoKoGLjoXtPUs>
Subject: Re: [Anima] I-D Action: draft-fries-anima-brski-async-enroll-00.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Mar 2019 21:24:41 -0000

Hi,

Since I won't be in Prague, I'd like to express strong support
for this work. I do have one question. Is the following use
case also valid? (I see the "Building automation" case as a
subset of this case, not to mention all kinds of industrial
control systems.)

3.2.5.  Infrastructure isolation policy

This refers to any case in which network infrastructure is
normally isolated from the Internet as a matter of policy,
most likely for security reasons. In such a case, limited
access to external PKI resources will be allowed in
carefully controlled short periods of time, for example
when a batch of new devices are deployed, but impossible
at other times.

Regards
   Brian Carpenter

On 11-Mar-19 22:52, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>         Title           : Support of asynchronous Enrollment in BRSKI
>         Authors         : Steffen Fries
>                           Hendrik Brockhaus
>                           Eliot Lear
> 	Filename        : draft-fries-anima-brski-async-enroll-00.txt
> 	Pages           : 18
> 	Date            : 2019-03-11
> 
> Abstract:
>    This document discusses the enhancement of automated bootstrapping of
>    a remote secure key infrastructure (BRSKI) to operate in domains
>    featuring no or only timely limited connectivity to backend services
>    offering enrollment functionality like a Public Key Infrastructure
>    (PKI).  In the context of deploying new devices the design of BRSKI
>    allows for online (synchronous object exchange) and offline
>    interactions (asynchronous object exchange) with a manufacturer's
>    authorization service.  It utilizes a self-contained voucher to
>    transport the domain credentials as a signed object to establish an
>    initial trust between the pledge and the deployment domain.  The
>    currently supported enrollment protocol for request and distribution
>    of deployment domain specific device certificates provides only
>    limited support for asynchronous PKI interactions.  This memo
>    motivates support of self-contained objects also for certificate
>    management by using an abstract notation to allow off-site operation
>    of PKI services, with only limited connectivity to the pledge
>    deployment domain.  This addresses specifically scenarios, in which
>    the deployment domain of a pledge does not perform the final
>    authorization of a certification request and rather delegates this
>    decision to an operator backend.  The goal is to enable the usage of
>    existing and potentially new PKI protocols supporting self-
>    containment for certificate management.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-fries-anima-brski-async-enroll/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-fries-anima-brski-async-enroll-00
> https://datatracker.ietf.org/doc/html/draft-fries-anima-brski-async-enroll-00
> 
> 
> 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 12 15:34:30 2019
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 2920412426E for <anima@ietfa.amsl.com>; Tue, 12 Mar 2019 15:34:28 -0700 (PDT)
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 2EIlPFwzYUF0 for <anima@ietfa.amsl.com>; Tue, 12 Mar 2019 15:34:25 -0700 (PDT)
Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (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 AAA251200D7 for <anima@ietf.org>; Tue, 12 Mar 2019 15:34:25 -0700 (PDT)
Received: by mail-pg1-x530.google.com with SMTP id k11so2887936pgb.8 for <anima@ietf.org>; Tue, 12 Mar 2019 15:34:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=b0TMdAM/iYMdGmKGcTNToNdeEcfhNa5B2oKwtf9GZw8=; b=JOa8/f93jbBK4c/yaF5qx03PSTEABbUkhrdjTWmz9PudYSFuxWNWvQh+DrN9v2FUDa l15bUwgtMMpU4yACZnsvIpb9JyZER+X3+8ZgAe7/UNo/MKDTw8g7pIchJ/fDkoqnOZGa XdNt6cgWVnpkQx7ROsmMDhYsjVFV4obnAYD5OshTl+pCuEoZ6maiHfLFFrRuJ4hmNum2 cdsT9nf40p/ov7pDy1DxjC2/ERYrHMcG5mzXNJTnY5pV9qblI72xBSwZZCo89snL6xki 7vhS6CLLE70NHY9u8mxNCD+LBXbcj0Pt7s8mPY3ktFGmO7VA2SgiS1M8pjjOPf978WId +9bA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=b0TMdAM/iYMdGmKGcTNToNdeEcfhNa5B2oKwtf9GZw8=; b=VEMFosL46WFGOoMJtA202j3jkn6/Og4pXNiO6M6tTqODLtltNbYJolV0Z8Bmeow/NF ilIVAHW/QpVpXj3VJIsklKl4SRs15IxEbLv2obFEgMNoQqCwkSWDC1kiDI6JakTfDUmy AsdjbLyzq597GS8Ns0K7ULsaB3ZK/zHdeMgUC1PaVgEZqZjFniL15mOKFixLXS6BxLq0 qwiSJFyEh6ggIjtxI8d75cBVFIzlq/Uxrcsa6WVPNiXSZEaD6Cd8OkqlEK0ozXOdb9CL 4CpV9eerEaZHLlL2Qp5qrYDNOQwrHBrTl1oqGfwriXSV5ElxCHvtE64tztl25nRDdCFh Gsmw==
X-Gm-Message-State: APjAAAWXUUKD7A3sIdJBgSMDd7VDM19xuwYfFamGmzPFB+HRNDbGCCSn hToUvIL9zs62QUhUnd0UfCgAaS7t
X-Google-Smtp-Source: APXvYqw7R2/MtTMV5HGKFt5kLtdBNeIuRCZ0P22jea7VuUS9IcGetIsdLBnbapQaIMuDnx/Sx5N92Q==
X-Received: by 2002:a63:ff0f:: with SMTP id k15mr9593614pgi.301.1552430064719;  Tue, 12 Mar 2019 15:34:24 -0700 (PDT)
Received: from [130.216.36.127] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.36.127]) by smtp.gmail.com with ESMTPSA id x23sm33742011pfe.0.2019.03.12.15.34.23 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Mar 2019 15:34:24 -0700 (PDT)
To: Anima WG <anima@ietf.org>
References: <155232623058.23130.9458868928214722923@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <bd1ab925-1777-b6ba-e21b-b93953a0a305@gmail.com>
Date: Wed, 13 Mar 2019 11:34:22 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3
MIME-Version: 1.0
In-Reply-To: <155232623058.23130.9458868928214722923@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/hvN5aYOrzdAuI7BI-gIRaTwbDak>
Subject: Re: [Anima] I-D Action: draft-richardson-anima-smarkaklink-00.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Mar 2019 22:34:28 -0000

Hi,

This is interesting (technically out of scope for
"professionally managed" networks, perhaps).

> 5.3.  Connect to BRSKI join network
...
> Receipt of an answer confirms that the
>    ESSID is correct and present.

Or a forged clone? If you are relying on the AR's IID
value for this, perhaps you need to specify that it must
be a pseudo-random value per RFC8064. Even so, there must
be a residual risk of a forgery.

...
>  (XXX - not using GRASP here.  Could use GRASP, but QR code is better)

You could use GRASP, but the AR is not a real registrar yet, so
IMHO it MUST NOT support the "AN_join_registrar" objective.
I think you'd need a short-lived "AN_adolescent_registrar"
objective, and you'd still need to check the link-local address,
so there would really be no advantage.

> 5.12.  Adolescent Registrar (AR) grows up
...
>    The AR is now considered a full registrar.  The AR now takes on the
>    role of Registrar.

Presumably at this point it does support GRASP "AN_join_registrar"?

Regards
   Brian Carpenter

On 12-Mar-19 06:43, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>         Title           : BRSKI enrollment of with disconnected Registrars -- smarkaklink
>         Authors         : Michael Richardson
>                           Jacques Latour
>                           Faud Khan
>                           Abhishek Joshi
> 	Filename        : draft-richardson-anima-smarkaklink-00.txt
> 	Pages           : 22
> 	Date            : 2019-03-11
> 
> Abstract:
>    This document details the mechanism used for initial enrollment using
>    a smartphone of a BRSKI Registrar system.
> 
>    There are two key differences in assumption from
>    [I-D.ietf-anima-bootstrapping-keyinfra]: that the intended registrar
>    has Internet, and that the Pledge has no user-interface.
> 
>    This variation on BRSKI is intended to be used in the situation where
>    the registrar device is new out of the box and is the intended
>    gateway to the Internet (such as a home gateway), but has not yet
>    been configured.  This work is also intended as a transition to the
>    Wi-Fi Alliance work on the Device Provisioning Protocol (DPP).
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-richardson-anima-smarkaklink/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-richardson-anima-smarkaklink-00
> https://datatracker.ietf.org/doc/html/draft-richardson-anima-smarkaklink-00
> 
> 
> 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 12 18:32:31 2019
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 814C512797A for <anima@ietfa.amsl.com>; Tue, 12 Mar 2019 18:32:30 -0700 (PDT)
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 trtP9w8Fs_MK for <anima@ietfa.amsl.com>; Tue, 12 Mar 2019 18:32:28 -0700 (PDT)
Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) (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 4B514127887 for <anima@ietf.org>; Tue, 12 Mar 2019 18:32:28 -0700 (PDT)
Received: by mail-pf1-x435.google.com with SMTP id i20so188269pfo.6 for <anima@ietf.org>; Tue, 12 Mar 2019 18:32:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=4scpR5vg23O7L2MEJ+qOeJrczBizZ4ous4Nzt/+lREE=; b=mVtCvNe55oOkfIiIKPeI97zodk2qWmFpRCDo/B6xayQzWKCTSDNCnlDAaOZlSpamT1 Uf8GTC3a7i0irzAhN/FCHz1e448KaT+Qpq7641Ydum/Z1FF/7fNVvGjp5KGxCi0DXHyC ECwQr255WKc8AtMxJ7YHt27WJatwN7H7eCoX01xauOKgpwJm75x5LcPokvu3tjPn6Zrb ZSUcv0LrKeB2UZ76SB1IlMQKDo7nkCCoSY3cKyBLfH4kmij5bL6UPczFYmvi8uEbVLA9 yRdRu8ASBpb5Pvj1ewYql4Ef/lq2F1CuKrQ1J2MQO6IIAuFw++INq1L47Z/WbFUedM/R qqAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=4scpR5vg23O7L2MEJ+qOeJrczBizZ4ous4Nzt/+lREE=; b=WmrJ9k0DQScOfI3LJu16NncB8kzGMcWEnRCoJNvOazIIE7YL4cNFXfpiXg+NDoXdsb qDZDJhmZM+GgonXrfhCrQUVRDcsrMyWDNzXoyZfuqIeYHU5bJsMEvsdBU9fMG0wmOlcO C87JHvzRLc4CVTJz+LPPyY1idsoOebYtzVzvgjUQoB0UU7kjyvlSdG8hl2DDdnOndJeW Y4zt3ju1dzl30uergSRDu+p4syE0tVVc8deouprkH+EeBCmg/l6VQTeB8EvPVbsB/Aez jgGkltZKcBC9gZukkZHVasnX0F09WTwnkipJqVR3vvD/zhxSvLepa4EWpz+J0j0l3qhW wT2A==
X-Gm-Message-State: APjAAAWHDjOPxpvVRn/tBSO5UF3j1M104mwmWh1ll4Y+10AotRVq6bTJ nhTGDh6m3XxHKyL+bDFBAtn85gPP
X-Google-Smtp-Source: APXvYqwd3CziC4ypDiSCiufYTznwGIFhXVTyC/4WK+L/PInwFguQAv/zcWBfQzgw79h1WMcuH00gPA==
X-Received: by 2002:a62:17d4:: with SMTP id 203mr40906085pfx.244.1552440747291;  Tue, 12 Mar 2019 18:32:27 -0700 (PDT)
Received: from [130.216.36.127] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.36.127]) by smtp.gmail.com with ESMTPSA id z15sm15152883pfn.30.2019.03.12.18.32.25 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Mar 2019 18:32:26 -0700 (PDT)
To: Anima WG <anima@ietf.org>
References: <155233457198.23138.2195313755590276544@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <7e94ddab-a450-7997-d375-f1e2bd1ed481@gmail.com>
Date: Wed, 13 Mar 2019 14:32:24 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3
MIME-Version: 1.0
In-Reply-To: <155233457198.23138.2195313755590276544@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/ZKi3g0AkKDVGMByF2PLjwifb1yc>
Subject: Re: [Anima] I-D Action: draft-bernardos-anima-fog-monitoring-00.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Mar 2019 01:32:30 -0000

Hi,

Firstly, I don't understand what value the word "fog" adds.
As far as I can see, it could simply be deleted throughout
without changing the meaning of the text.

Also, the term "NFVO" is used without definition. I'm guessing that
it might mean Network Function Virtualisation Orchestrator, but the
concept of NFV is pretty vague anyway.

Do the references to SFC specifically refer to RFC8300 etc.? If not,
what do they refer to?

The mapping to the ANI doesn't seem quite right to me yet. Firstly,
there are no security considerations (seems to be a common problem
for IoT). Can we assume that you expect to use a BRSKI type of
procedure and then a layer 3 ACP? Or do you propose an alternative
form of ACP?

Then, the operations like Mcast discovery (fog_node_ID, scope)
shown in Figure 4 are not really GRASP operations. The discovery
target in GRASP is not a node; in fact you don't know who the
other nodes are in advance.

If you want all nodes to know where the controller is, the
controller should periodically flood (GRASP M_FLOOD) its 
own objective (including its properties) to all nodes.

If you want the individual nodes to register with the
controller, you'd need to design a negotiation objective
supported by the controller and all other nodes. You'd make
it a negotiation objective so that the node could send info
to the controller, and the controller could send an answer
back. Using GRASP's ability to carry JSON-like objects,
all your suggested options like NODERADIO etc. are trivial
to support. (I'm not even sure that IANA registration is
needed.)

Can you try to explain the *requirements* that Fig 2
covers, because it really isn't clear.

> When a fog node bootstraps, such as nodes A and B in the figure,
> they start sending multicast discovery messages within a given
> scope, 

Firstly, why is that the node's job? I would have expected this to
be done by the controller or the orchestrator?

Secondly, what you describe doesn't fit with the GRASP model.
As mentioned, GRASP discovers objectives, not nodes. If there
is an objective called, say, "Manufacturer" and you issued an
M_DISCOVER for "Manufacturer" with value "Huawei", that would
work.

> All-resources within a topological network distance (e.g.,
>          number of hops)

We can do that in GRASP using the loop-count feature (which
also functions as a hop-count in discovery) but it's a little
tricky.

> All-resources within a geographical location.

I guess we could do that with an objective called "Location",
but the location value would have to be announced by the
controller/orchestrator. I don't see the value of this,
because by definition you can only reach nodes in the
same ACP.

> The discovery messages are multicast within the scope, reaching
> all the nodes that compose the specified fog resources.  This can
> be done for example using well defined IPv6 multicast addresses,
> specified for each of the different scopes.  This signaling is
> based on GRASP.  Different IPv6 multicast addresses need to be
> defined to reach each different scope,

That doesn't work. GRASP uses link-local multicast and does its
own relaying between links. You limit the scope by setting the
GRASP loop-count.

> o  In response to multicast fog discovery messages, the fog
>    monitoring controller replies with unicast information messages.

As mentioned above, it's more natural in GRASP for the controller
to flood its information. It's simpler for the individual node
that way.

I have a suggestion for you. Try to model all the operations you want
to define using the GRASP prototype. It's a nice project for a good
student who can write Python. Everything you need to know is at
https://github.com/becarpenter/graspy/blob/master/graspy.pdf

>       Note that registration to multiple fog monitoring controller
>       instances could also be possible if a fog node wants to belong to
>       several fog domains at the same time (but note that how the
>       orchestration of the same resource is done by multiple
>       orchestrators is not covered by this invention).

Overlapping domains are not currently supported by GRASP.

Also, that word "invention"??? Are we going to see an IPR disclosure soon?

Regards
   Brian Carpenter

On 12-Mar-19 09:02, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>         Title           : Autonomic setup of fog monitoring agents
>         Authors         : Carlos J. Bernardos
>                           Alain Mourad
> 	Filename        : draft-bernardos-anima-fog-monitoring-00.txt
> 	Pages           : 11
> 	Date            : 2019-03-11
> 
> Abstract:
>    The concept of fog computing has emerged driven by the Internet of
>    Things (IoT) due to the need of handling the data generated from the
>    end-user devices.  The term fog is referred to any networked
>    computational resource in the continuum between things and cloud.  In
>    fog computing, functions can be stiched together composing a service
>    function chain.  These functions might be hosted on resources that
>    are inherently heterogeneous, volatile and mobile.  This means that
>    resources might appear and disappear, and the connectivity
>    characteristics between these resources may also change dynamically.
>    This calls for new orchestration solutions able to cope with dynamic
>    changes to the resources in runtime or ahead of time (in anticipation
>    through prediction) as opposed to today's solutions which are
>    inherently reactive and static or semi-static.
> 
>    A fog monitoring solution can be used to help predicting events so an
>    action can be taken before an event actually takes place.  This
>    solution is composed of agents running on the fog nodes plus a
>    controller hosted at another device (running in the infrastructure or
>    in another fog node).  Since fog environments are inherently volatile
>    and extremely dynamic, it is convenient to enable the use of
>    autonomic technologies to autonomously set-up the fog monitoring
>    platform.  This document aims at presenting this use case as well as
>    specifying how to use GRASP as needed in this scenario.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-bernardos-anima-fog-monitoring/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-bernardos-anima-fog-monitoring-00
> https://datatracker.ietf.org/doc/html/draft-bernardos-anima-fog-monitoring-00
> 
> 
> 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 12 18:37:03 2019
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 53B84127887; Tue, 12 Mar 2019 18:37:01 -0700 (PDT)
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 BJrzPx0axwJE; Tue, 12 Mar 2019 18:36:59 -0700 (PDT)
Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (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 2912B126CAD; Tue, 12 Mar 2019 18:36:59 -0700 (PDT)
Received: by mail-pg1-x529.google.com with SMTP id v12so322308pgq.1; Tue, 12 Mar 2019 18:36:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Vn9QG8A+6tCT+AMYnXws3j3Lzc5YzbH8KoUX516y5oM=; b=NDJrueYJ8RRHOSEeS3h42b+DFBe1P6PEZvjzRcSxNKh8HyuU+zGLpxRqNv8AfUWI0p 5lfot2BGJPxdsXuBluHBdCwECiygdo2mxLH9onrqzFekQd72qbPFMR1ng0nU67TDcP+r hwFP6vopE6/p661sMBH1V7ErgCZhWRx9UO+Vk4ZV+bb4wDnlcC+fSzcIiup4ZCIa+Ut8 MsX/YzZitFIX7PT0otYKsMqfK2jJfnMB5E29ebqBZmlZfKVaVEUP6m2wUPewDII6jvTV j50LvdtJ50WJvH+VPmiz2MjnShJ2qR8mfgdLJB81tMXs0xC6BtPH27roxUSSCxlFckLm piNA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Vn9QG8A+6tCT+AMYnXws3j3Lzc5YzbH8KoUX516y5oM=; b=ntceGQp0MlIfumyPndg2QRRcfjPLoPLtESHkTk1oXrZj2KGK8P3834kYgIH8nCqT+T Vf2pTJbxy5ZpwPGUS+ks8RVJ03m6vcFqHUf5AwrSS/pDL732aBTRZx+tjgvMvfM8YSTW E5lq+HjUUw8/ahuNdmxdLTfLJcgydocw67N3Z0uIDFeV/bkWaEBgfkekcCrfaHJLgmv/ X8VPs0sGzvW8Tbc/t+XCqfI2gCQvfZ9kSLFdE9EgItgud13CNf2sI1Lp4kAuK7uIDxeJ OMuuG4bUrC5mTPOk14SB1YCvwyhpLedeKErt+Z5sSOXgpq92q+sIDJ7WIwOteO0+Shdv jnrA==
X-Gm-Message-State: APjAAAWCP5ZrwaLa7nH+bCDHGY9/tnCL2iBRuo6Axryb4UDvkCQ/q8P4 8DWLc9TzCHi/0yVDPN1znCoZsr2b
X-Google-Smtp-Source: APXvYqxzhMpuxl3ZCNDBImEKcOrt6uFsfQ/gt1Pt+1yEy3c7Y2JylyNerjNxJu1odkwwpGHcdJAJ8Q==
X-Received: by 2002:a63:8441:: with SMTP id k62mr35771564pgd.219.1552441018300;  Tue, 12 Mar 2019 18:36:58 -0700 (PDT)
Received: from [130.216.36.127] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.36.127]) by smtp.gmail.com with ESMTPSA id k22sm14612934pfi.90.2019.03.12.18.36.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Mar 2019 18:36:57 -0700 (PDT)
To: Sheng Jiang <jiangsheng@huawei.com>, "anima@ietf.org" <anima@ietf.org>
Cc: "anima-chairs@ietf.org" <anima-chairs@ietf.org>
References: <5D36713D8A4E7348A7E10DF7437A4B929035710C@NKGEML515-MBX.china.huawei.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <a7f7a188-69c0-04b9-73db-ab08ffab9b09@gmail.com>
Date: Wed, 13 Mar 2019 14:36:55 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3
MIME-Version: 1.0
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B929035710C@NKGEML515-MBX.china.huawei.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/yR5qwdbbfpxwmx0kelxo-elcnuU>
Subject: Re: [Anima]  =?utf-8?q?Call_for_agenda_ANIMA_=40_IETF_104=EF=BC=8C_Pr?= =?utf-8?q?ague?=
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Mar 2019 01:37:01 -0000

Confirming this request on the list:

15 minutes for draft-carpenter-anima-l2acp-scenarios-00

Scenarios and requirements for Autonomic Control Planes
(ACPs) constructed and secured at Layer 2.

Speaker: Bing Liu (remote)

Regards
   Brian Carpenter

On 08-Mar-19 19:59, Sheng Jiang wrote:
> Hi, all anima,
> 
> 
> 
> We have been allocated a session of 2-hour for the ANIMA WG meeting for IETF-104 (Prague) - Tuesday afternoon session I. We are now starting to collect agenda items for the session. Please send your request for agenda by March 14th, Thursday.
> 
> 
> 
> 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/>) requests for time slot by March 14th, Thursday and include:
> 
> 
> 
> Name of time slot:
> 
> Name of draft(s):
> 
> Time requested:
> 
> Presenter name(s):
> 
> 
> 
> More details about the IETF 104, Prague can be found at:
> 
> 
> 
> https://www.ietf.org/how/meetings/104/
> 
> 
> 
> 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 12 18:46:02 2019
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 331AA12705F; Tue, 12 Mar 2019 18:46:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 IzKLg8Vl-_yk; Tue, 12 Mar 2019 18:45:58 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 7FAB7126CAD; Tue, 12 Mar 2019 18:45:58 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 5A4A99D58A189A21A528; Wed, 13 Mar 2019 01:45:56 +0000 (GMT)
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 13 Mar 2019 01:45:55 +0000
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml701-chm.china.huawei.com (10.201.108.50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Wed, 13 Mar 2019 01:45:55 +0000
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml701-chm.china.huawei.com (10.201.108.50) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1591.10 via Frontend Transport; Wed, 13 Mar 2019 01:45:55 +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.0415.000; Wed, 13 Mar 2019 09:45:52 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "anima@ietf.org" <anima@ietf.org>
CC: "anima-chairs@ietf.org" <anima-chairs@ietf.org>
Thread-Topic: =?utf-8?B?W0FuaW1hXSBDYWxsIGZvciBhZ2VuZGEgQU5JTUEgQCBJRVRGIDEwNO+8jCBQ?= =?utf-8?Q?rague?=
Thread-Index: AdTVSp7fUdNBEg1lSfyRueXgFJmsUwDr5CSAABEOBnA=
Date: Wed, 13 Mar 2019 01:45:51 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B9290388E8D@NKGEML515-MBX.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B929035710C@NKGEML515-MBX.china.huawei.com> <a7f7a188-69c0-04b9-73db-ab08ffab9b09@gmail.com>
In-Reply-To: <a7f7a188-69c0-04b9-73db-ab08ffab9b09@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.111.185.119]
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/rfztyXuCPtCx180fqIvfH7xsB7s>
Subject: Re: [Anima]  =?utf-8?q?Call_for_agenda_ANIMA_=40_IETF_104=EF=BC=8C_Pr?= =?utf-8?q?ague?=
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Mar 2019 01:46:00 -0000

VGhhbmtzLCBCcmlhbiAmIEJpbmcuDQoNCllvdXIgcmVxdWVzdCBpcyBub3RlZC4NCg0KU2hlbmcN
Cg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBCcmlhbiBFIENhcnBlbnRl
ciBbbWFpbHRvOmJyaWFuLmUuY2FycGVudGVyQGdtYWlsLmNvbV0NCj4gU2VudDogV2VkbmVzZGF5
LCBNYXJjaCAxMywgMjAxOSA5OjM3IEFNDQo+IFRvOiBTaGVuZyBKaWFuZyA8amlhbmdzaGVuZ0Bo
dWF3ZWkuY29tPjsgYW5pbWFAaWV0Zi5vcmcNCj4gQ2M6IGFuaW1hLWNoYWlyc0BpZXRmLm9yZw0K
PiBTdWJqZWN0OiBSZTogW0FuaW1hXSBDYWxsIGZvciBhZ2VuZGEgQU5JTUEgQCBJRVRGIDEwNO+8
jCBQcmFndWUNCj4gDQo+IENvbmZpcm1pbmcgdGhpcyByZXF1ZXN0IG9uIHRoZSBsaXN0Og0KPiAN
Cj4gMTUgbWludXRlcyBmb3IgZHJhZnQtY2FycGVudGVyLWFuaW1hLWwyYWNwLXNjZW5hcmlvcy0w
MA0KPiANCj4gU2NlbmFyaW9zIGFuZCByZXF1aXJlbWVudHMgZm9yIEF1dG9ub21pYyBDb250cm9s
IFBsYW5lcw0KPiAoQUNQcykgY29uc3RydWN0ZWQgYW5kIHNlY3VyZWQgYXQgTGF5ZXIgMi4NCj4g
DQo+IFNwZWFrZXI6IEJpbmcgTGl1IChyZW1vdGUpDQo+IA0KPiBSZWdhcmRzDQo+ICAgIEJyaWFu
IENhcnBlbnRlcg0KPiANCj4gT24gMDgtTWFyLTE5IDE5OjU5LCBTaGVuZyBKaWFuZyB3cm90ZToN
Cj4gPiBIaSwgYWxsIGFuaW1hLA0KPiA+DQo+ID4NCj4gPg0KPiA+IFdlIGhhdmUgYmVlbiBhbGxv
Y2F0ZWQgYSBzZXNzaW9uIG9mIDItaG91ciBmb3IgdGhlIEFOSU1BIFdHIG1lZXRpbmcgZm9yDQo+
IElFVEYtMTA0IChQcmFndWUpIC0gVHVlc2RheSBhZnRlcm5vb24gc2Vzc2lvbiBJLiBXZSBhcmUg
bm93IHN0YXJ0aW5nIHRvIGNvbGxlY3QNCj4gYWdlbmRhIGl0ZW1zIGZvciB0aGUgc2Vzc2lvbi4g
UGxlYXNlIHNlbmQgeW91ciByZXF1ZXN0IGZvciBhZ2VuZGEgYnkgTWFyY2gNCj4gMTR0aCwgVGh1
cnNkYXkuDQo+ID4NCj4gPg0KPiA+DQo+ID4gRm9yIHRoaXMgY29taW5nIG1lZXRpbmcsIHdlIHdv
dWxkIGxpa2UgdG8gZGlzY3VzcyBwb3RlbnRpYWwgZnV0dXJlIEFOSU1BDQo+IHdvcmtzLiBBcyBu
b3JtYWwsIHRoZSBwcmlvcml0eSBhbW9uZyB0aGVzZSBub24tY2hhcnRlciB3b3JrIGl0ZW1zIHdv
dWxkIGJlOg0KPiB0aGVzZSB0aGF0IGhhdmUgYWN0aXZlIGRpc2N1c3Npb24gaW4gbWFpbCBsaXN0
LCB0aGVuIHRoZXNlIGhhdmUgc3VibWl0dGVkIGRyYWZ0cywNCj4gYW5kIHRvcGljcyB3aXRob3V0
IGRyYWZ0cy4NCj4gPg0KPiA+DQo+ID4NCj4gPiBQbGVhc2Ugc2VuZCB1cyAoYW5pbWEtY2hhaXJz
IGF0IGlldGYub3JnPGh0dHBzOi8vaWV0Zi5vcmcvPikgcmVxdWVzdHMgZm9yIHRpbWUNCj4gc2xv
dCBieSBNYXJjaCAxNHRoLCBUaHVyc2RheSBhbmQgaW5jbHVkZToNCj4gPg0KPiA+DQo+ID4NCj4g
PiBOYW1lIG9mIHRpbWUgc2xvdDoNCj4gPg0KPiA+IE5hbWUgb2YgZHJhZnQocyk6DQo+ID4NCj4g
PiBUaW1lIHJlcXVlc3RlZDoNCj4gPg0KPiA+IFByZXNlbnRlciBuYW1lKHMpOg0KPiA+DQo+ID4N
Cj4gPg0KPiA+IE1vcmUgZGV0YWlscyBhYm91dCB0aGUgSUVURiAxMDQsIFByYWd1ZSBjYW4gYmUg
Zm91bmQgYXQ6DQo+ID4NCj4gPg0KPiA+DQo+ID4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvaG93L21l
ZXRpbmdzLzEwNC8NCj4gPg0KPiA+DQo+ID4NCj4gPiBBZ2FpbiwgcHJlc2VudGVycyBhbmQgZHJh
ZnQgYXV0aG9ycyBwbGVhc2UgaW52b2tlIGFjdGl2ZSBkaXNjdXNzaW9ucyBpbiB0aGUNCj4gQU5J
TUEgbGlzdC4gTWFpbCBsaXN0IGlzIGEgdmVyeSBnb29kIHBsYWNlIHRvIGRpc2N1c3MgYW5kIHJl
YWNoIGNvbnNlbnN1cyBvbg0KPiB0ZWNobmljYWwgaXNzdWVzLg0KPiA+DQo+ID4NCj4gPg0KPiA+
IEJlc3QgcmVnYXJkcywNCj4gPg0KPiA+DQo+ID4NCj4gPiBUb2VybGVzcyAmIFNoZW5nDQo+ID4N
Cj4gPg0KPiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQo+ID4gQW5pbWEgbWFpbGluZyBsaXN0DQo+ID4gQW5pbWFAaWV0Zi5vcmcNCj4gPiBodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2FuaW1hDQo+ID4NCg==


From nobody Tue Mar 12 20:20:55 2019
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 56B8D127A73; Tue, 12 Mar 2019 20:20:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 BmNuyju9Yo1r; Tue, 12 Mar 2019 20:20:44 -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 1F36D12D7EA; Tue, 12 Mar 2019 20:20:44 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id 31EFC3808A; Tue, 12 Mar 2019 23:20:26 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id DB6CDACA; Tue, 12 Mar 2019 23:20:42 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id D8F5883B; Tue, 12 Mar 2019 23:20:42 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Fries\, Steffen" <steffen.fries@siemens.com>
cc: Eliot Lear <lear@cisco.com>, "anima-chairs\@ietf.org" <anima-chairs@ietf.org>, "anima\@ietf.org" <anima@ietf.org>, Sheng Jiang <jiangsheng@huawei.com>
In-Reply-To: <E6C9F0E527F94F4692731382340B33781540E0CA@DENBGAT9EJ5MSX.ww902.siemens.net>
References: <5D36713D8A4E7348A7E10DF7437A4B929035710C@NKGEML515-MBX.china.huawei.com> <9BC436CD-D22C-419B-A16E-7D7C81AC12B0@cisco.com> <18611.1552332885@localhost> <E6C9F0E527F94F4692731382340B33781540E0CA@DENBGAT9EJ5MSX.ww902.siemens.net>
X-Mailer: MH-E 8.6; nmh 1.7+dev; 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, 12 Mar 2019 23:20:42 -0400
Message-ID: <10469.1552447242@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/_WE3CEVZ9GzQe9w0gxdT1GDpJhc>
Subject: Re: [Anima]  =?utf-8?q?Call_for_agenda_ANIMA_=40_IETF_104=EF=BC=8C_Pr?= =?utf-8?q?ague?=
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Mar 2019 03:20:53 -0000

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


Fries, Steffen <steffen.fries@siemens.com> wrote:
    >> Eliot Lear <lear@cisco.com> wrote:
    >> > I think we had a lengthy conversation about BRSKI next steps, and =
that we
    >> > should expect to spend some time on this in ANIMA. I think I count=
 at least
    >> > four drafts that are worth considering, and Michael might have mor=
e in mind:
    >>
    >> > * Draft-vanderstock-anima-constrained-join-proxy
    >> > * Draft-lear-eap-teap-brski
    >> > * Draft-ietf-6tisch-{=E2=80=A6}
    >>
    >> > * Draft-fries-anima-brski-async-enroll
    >> {Eliot: Does this document include Oskar's requirements?}
    >>
    >> Additional documents that call on BRSKI:
    >>
    >> * draft-richardson-anima-smarkaklink (formerly draft-richardson-anim=
a-smartpledge)
    -> I have revised slides, and I walk to talka bout them.
    >> I believe that it solves draft-fries-anima-brski-async-enroll as wel=
l,
    >> but I haven't read the entire document yet.

    > I just read across draft-richardson-anima-smarkaklink and to my
    > understanding it focuses on the voucher exchange in situations where
    > the domain registrar is only temporary available. The voucher exchange

My focus on writing it is bootstrapping a registrar.
As such, the protocol flow does not include direct access to a registrar.
Oskar shared your requirements with me, and I think that we accomodate it in
the same protocol.

    > different component than a local domain registrar. In that aspect it
    > has a different scope than draft-richardson-anima-smarkaklink.

I think this discussion should be interesting!

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


=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-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlyIdwoACgkQgItw+93Q
3WV4jggAvTA8RDaKXpJIyjcWCnp0HWambQiNoKxXVE0a9CINNjULrJysvomIGd5t
N97a+k8MrDBd2cD+CApkF+YdRPHU0A26czAnLfsQ3aTXHOWO6Ql2NMcnYYSYUKbz
MPb9zM+Km2lP2nmB8lZVEVcYO4JcKPedkJYSmeL4/xWUTbuhokQCnh8qMIFUSfWW
VJlwhkvJrChYQ0Zlsi7RKLGnSUrKXjvViBEg/itnl5CPZ2l7qhh+4uTlzlhNDhEF
nFJsu2HyG956YeXtXvErGSNOFhUTD5TCUhB3nPBAYFLfdtpqIgGHelyFz5mLH8q3
zXagIyz+aQfkHVyIP4082Xm5JOkC0w==
=/WdW
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Mar 12 20:49:21 2019
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 271BD127970; Tue, 12 Mar 2019 20:49:20 -0700 (PDT)
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 BgZKTR_3S9j1; Tue, 12 Mar 2019 20:49:17 -0700 (PDT)
Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) (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 42733127598; Tue, 12 Mar 2019 20:49:17 -0700 (PDT)
Received: by mail-pf1-x430.google.com with SMTP id j5so408875pfa.2; Tue, 12 Mar 2019 20:49:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=eYSZxEXiVv8bBB93081JMXu0qiqbaE2YPrE37xPZyPg=; b=qxKCc0MvsHyn/aKIam0MD2nwU5LlVYD041/JoqPo8yYUydg/cvG7xFLCyKcQn3ZJuc qYh/zVEBs0Sh+DSWaaMTPLlFIZBeGy4A7nfIgiIIaPGOf33CpAPdPnyjCxxv2K0/Nr52 txm9303dpONsETkXBr+3iChtGinsXzdSup3MVbEmT+gGq+XWwLyuppPXTnD2PV0ciqkE 8rY3A0gmpcFyAouDJsQt8hOW0LMx+uCjCp52TZ5r9OXU/wF3JqG/pjP5VgdkEM/+YQhi ygEQgRNPkA2JsF15FBW3jnKp3N3WM7Lukewf76beSkuHIKZOx4dsPwMktZQqA9GqQymA /Zdg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=eYSZxEXiVv8bBB93081JMXu0qiqbaE2YPrE37xPZyPg=; b=Mv/eVSUlGAE2FqRC1rYfo0hTG5Kv2n38Lfah6HI2c0okwzAdIJlVg2bn/EE5Yydwj6 m5mYUccnr0RU+d/hxYdx012HbJnxPwQr2D1AA+X48TyUoQJUZBVOwz18fWca06i43idE oEVimBxFCGXrOCovMvIajT9JtUcM4TsRMHpvsHuwRA8TnlXxGN3HaQe1gponxVq5NINp NE+GI0dA4K850UHGT5uKOacJC+E46QCGC8xCItc28IlQbyg5VZedeQRCVYWJi4l61VaA 1JbQP6tQXWifSMip7NS2pCO4sDinqweXBwd00roh2tlQrFtr7RCFjcXj0s3JubAg8hvc CHjA==
X-Gm-Message-State: APjAAAXw/qtfANZJY11iTdnBNiKDwK4YvVOZaHhFz08Gs5AtvLpKyKXi Ufz3GTTVQBE9vDih9Og8pl8=
X-Google-Smtp-Source: APXvYqzU/hX46uVqQsD+LZZWS7s6q30+e8aVu83uyf5zobmVb3DBkf6rSQjp3TIzLiH0pe0ILzYn1w==
X-Received: by 2002:a17:902:e3:: with SMTP id a90mr42344361pla.45.1552448956569;  Tue, 12 Mar 2019 20:49:16 -0700 (PDT)
Received: from [192.168.178.30] (211.231.69.111.dynamic.snap.net.nz. [111.69.231.211]) by smtp.gmail.com with ESMTPSA id d26sm13960488pfn.86.2019.03.12.20.49.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Mar 2019 20:49:15 -0700 (PDT)
To: Michael Richardson <mcr+ietf@sandelman.ca>, "Fries, Steffen" <steffen.fries@siemens.com>
Cc: "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "anima@ietf.org" <anima@ietf.org>, Eliot Lear <lear@cisco.com>, Sheng Jiang <jiangsheng@huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B929035710C@NKGEML515-MBX.china.huawei.com> <9BC436CD-D22C-419B-A16E-7D7C81AC12B0@cisco.com> <18611.1552332885@localhost> <E6C9F0E527F94F4692731382340B33781540E0CA@DENBGAT9EJ5MSX.ww902.siemens.net> <10469.1552447242@localhost>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <332043fc-5c18-3a0a-c1cb-a689c2a5db8d@gmail.com>
Date: Wed, 13 Mar 2019 16:49:13 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3
MIME-Version: 1.0
In-Reply-To: <10469.1552447242@localhost>
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/PoGqVYjvMBpzkZHeQd-iFpRn4CE>
Subject: Re: [Anima]  =?utf-8?q?Call_for_agenda_ANIMA_=40_IETF_104=EF=BC=8C_Pr?= =?utf-8?q?ague?=
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Mar 2019 03:49:20 -0000

On 13-Mar-19 16:20, Michael Richardson wrote:
>=20
> Fries, Steffen <steffen.fries@siemens.com> wrote:
>     >> Eliot Lear <lear@cisco.com> wrote:
>     >> > I think we had a lengthy conversation about BRSKI next steps, =
and that we
>     >> > should expect to spend some time on this in ANIMA. I think I c=
ount at least
>     >> > four drafts that are worth considering, and Michael might have=
 more in mind:
>     >>
>     >> > * Draft-vanderstock-anima-constrained-join-proxy
>     >> > * Draft-lear-eap-teap-brski
>     >> > * Draft-ietf-6tisch-{=E2=80=A6}
>     >>
>     >> > * Draft-fries-anima-brski-async-enroll
>     >> {Eliot: Does this document include Oskar's requirements?}
>     >>
>     >> Additional documents that call on BRSKI:
>     >>
>     >> * draft-richardson-anima-smarkaklink (formerly draft-richardson-=
anima-smartpledge)
>     -> I have revised slides, and I walk to talka bout them.
>     >> I believe that it solves draft-fries-anima-brski-async-enroll as=
 well,
>     >> but I haven't read the entire document yet.
>=20
>     > I just read across draft-richardson-anima-smarkaklink and to my
>     > understanding it focuses on the voucher exchange in situations wh=
ere
>     > the domain registrar is only temporary available. The voucher exc=
hange
>=20
> My focus on writing it is bootstrapping a registrar.
> As such, the protocol flow does not include direct access to a registra=
r.
> Oskar shared your requirements with me, and I think that we accomodate =
it in
> the same protocol.
>=20
>     > different component than a local domain registrar. In that aspect=
 it
>     > has a different scope than draft-richardson-anima-smarkaklink.
>=20
> I think this discussion should be interesting!

Having read both, I believe they address different scenarios at the
moment. Explain to me how you'd add a new batch of a few hundred widgets
to a building services network at 3 a.m. Sunday morning using smarkalink.=

I thought that was pretty clear using brski-async-enroll. On the other
hand I don't see Joe Average Citizen using brski-async-enroll to set
up a new CE and small office network.

Maybe we can get the goals and scenarios clear.

   Brian


From nobody Wed Mar 13 02:56:54 2019
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 02B10130EC6 for <anima@ietfa.amsl.com>; Wed, 13 Mar 2019 02:56:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 qhG43PQyPkxQ for <anima@ietfa.amsl.com>; Wed, 13 Mar 2019 02:56:49 -0700 (PDT)
Received: from thoth.sbs.de (thoth.sbs.de [192.35.17.2]) (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 50C55130EBF for <anima@ietf.org>; Wed, 13 Mar 2019 02:56:49 -0700 (PDT)
Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id x2D9ukVZ007431 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 13 Mar 2019 10:56:46 +0100
Received: from DEFTHW99ERNMSX.ww902.siemens.net (defthw99ernmsx.ww902.siemens.net [139.22.70.141]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTPS id x2D9uhcb007748 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 13 Mar 2019 10:56:46 +0100
Received: from DENBGAT9EJ5MSX.ww902.siemens.net ([169.254.12.162]) by DEFTHW99ERNMSX.ww902.siemens.net ([139.22.70.141]) with mapi id 14.03.0435.000; Wed, 13 Mar 2019 10:56:45 +0100
From: "Fries, Steffen" <steffen.fries@siemens.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: Anima WG <anima@ietf.org>
Thread-Topic: [Anima] I-D Action: draft-fries-anima-brski-async-enroll-00.txt
Thread-Index: AQHU2RoHrCAOjXKsL0OjnXiC6nw+1KYJU+2+
Date: Wed, 13 Mar 2019 09:56:44 +0000
Message-ID: <98C2599D-5332-48E8-9291-9797952E36B3@siemens.com>
References: <155229792081.16909.926731018863391018@ietfa.amsl.com>, <0a80e773-0b4a-6f31-25a7-d533e6c20596@gmail.com>
In-Reply-To: <0a80e773-0b4a-6f31-25a7-d533e6c20596@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
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/0ezjXkAvZTuhYisnYOXPRlhTEBQ>
Subject: Re: [Anima] I-D Action: draft-fries-anima-brski-async-enroll-00.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Mar 2019 09:56:53 -0000

Hi Brian,

> Since I won't be in Prague, I'd like to express strong support
> for this work.
Thank you.=20
> I do have one question. Is the following use
> case also valid? (I see the "Building automation" case as a
> subset of this case, not to mention all kinds of industrial
> control systems.)
>=20
> 3.2.5.  Infrastructure isolation policy
>=20
> This refers to any case in which network infrastructure is
> normally isolated from the Internet as a matter of policy,
> most likely for security reasons. In such a case, limited
> access to external PKI resources will be allowed in
> carefully controlled short periods of time, for example
> when a batch of new devices are deployed, but impossible
> at other times.
>=20
That sound for me like a valid use case which we can also state in the next=
 version. Honestly, I was thinking on use cases, which lack the technical c=
apability to alway stay online like the once stated in the draft. But yes, =
policy driven isolation is another perfectly fine use case. Thank you for b=
ringing that up.=20

Best regards
Steffen=20

> Regards
>   Brian Carpenter
>=20
>> On 11-Mar-19 22:52, internet-drafts@ietf.org wrote:
>>=20
>> A New Internet-Draft is available from the on-line Internet-Drafts direc=
tories.
>>=20
>>=20
>>        Title           : Support of asynchronous Enrollment in BRSKI
>>        Authors         : Steffen Fries
>>                          Hendrik Brockhaus
>>                          Eliot Lear
>>    Filename        : draft-fries-anima-brski-async-enroll-00.txt
>>    Pages           : 18
>>    Date            : 2019-03-11
>>=20
>> Abstract:
>>   This document discusses the enhancement of automated bootstrapping of
>>   a remote secure key infrastructure (BRSKI) to operate in domains
>>   featuring no or only timely limited connectivity to backend services
>>   offering enrollment functionality like a Public Key Infrastructure
>>   (PKI).  In the context of deploying new devices the design of BRSKI
>>   allows for online (synchronous object exchange) and offline
>>   interactions (asynchronous object exchange) with a manufacturer's
>>   authorization service.  It utilizes a self-contained voucher to
>>   transport the domain credentials as a signed object to establish an
>>   initial trust between the pledge and the deployment domain.  The
>>   currently supported enrollment protocol for request and distribution
>>   of deployment domain specific device certificates provides only
>>   limited support for asynchronous PKI interactions.  This memo
>>   motivates support of self-contained objects also for certificate
>>   management by using an abstract notation to allow off-site operation
>>   of PKI services, with only limited connectivity to the pledge
>>   deployment domain.  This addresses specifically scenarios, in which
>>   the deployment domain of a pledge does not perform the final
>>   authorization of a certification request and rather delegates this
>>   decision to an operator backend.  The goal is to enable the usage of
>>   existing and potentially new PKI protocols supporting self-
>>   containment for certificate management.
>>=20
>>=20
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-fries-anima-brski-async-enroll/
>>=20
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-fries-anima-brski-async-enroll-00
>> https://datatracker.ietf.org/doc/html/draft-fries-anima-brski-async-enro=
ll-00
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of submis=
sion
>> until the htmlized version and diff are available at tools.ietf.org.
>>=20
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>=20
>> _______________________________________________
>> 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
>>=20
>=20
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima


From nobody Thu Mar 14 23:51:47 2019
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 462F513107B for <anima@ietfa.amsl.com>; Thu, 14 Mar 2019 23:51:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 IqolHNtRkcJZ for <anima@ietfa.amsl.com>; Thu, 14 Mar 2019 23:51:43 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 CB137127887 for <anima@ietf.org>; Thu, 14 Mar 2019 23:51:42 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id D6CC047919F1A2A91EF3; Fri, 15 Mar 2019 06:51:40 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 15 Mar 2019 06:51:39 +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.0415.000; Fri, 15 Mar 2019 14:51:28 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Toerless Eckert <tte@cs.fau.de>, Toerless Eckert <toerless.eckert@huawei.com>
CC: "anima@ietf.org" <anima@ietf.org>
Thread-Topic: Potential Milestones for ANIMA new charter
Thread-Index: AdTa+jwafGdRprrVRti8bHBG3GkyuA==
Date: Fri, 15 Mar 2019 06:51:27 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B929038B9FA@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_5D36713D8A4E7348A7E10DF7437A4B929038B9FANKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/n5ThbrrKy501JU_YbjrQB0Bi6y8>
Subject: [Anima] Potential Milestones for ANIMA new charter
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 15 Mar 2019 06:51:45 -0000

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

Hi, Toerless,

I am working on the charter text. It is not difficult to categetied the wor=
k items into 4 classes: ANI+, ASA, BRSKI, Use cases. I am intending to put =
NOCs into ANI+. I will send you a reword version on next Monday.

For milestones, giving that we have a long document waiting list as long as=
 20. It would not sufficient to satisfy everyone for just 5 milestones by s=
aying everyone should have no more than one document through. We would face=
 more than 10 individuals asking for adoption. Anyway, here are my choice f=
or the first 5:

ASA Lifecycle (Lucent)
ASA guideline (Brian C)
GRASP Distribution (Bing Liu)
Constrained Join Proxy for Bootstrapping Protocols (Michael R.)
+ One BRSKI document

This would looks good when we face IESG. Then, we may able to adopt 2 or 3 =
more document out of written milestones, I guess. But it would looks bad if=
 we have more than 10 WG document parallel. PS: we still have 7 WG document=
s showing now, though 3 of them passed IESG review and waiting by MISREF - =
ACP!

Cheers,

Sheng

--_000_5D36713D8A4E7348A7E10DF7437A4B929038B9FANKGEML515MBXchi_
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:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:\5B8B\4F53;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"\7EAF\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:\5B8B\4F53;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.Char
	{mso-style-name:"\7EAF\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\7EAF\6587\672C;
	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;}
/* List Definitions */
@list l0
	{mso-list-id:21907192;
	mso-list-type:hybrid;
	mso-list-template-ids:-1206616824 67698697 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0FC;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:18.0pt;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F06E;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:42.0pt;
	text-indent:-21.0pt;
	font-family:Wingdings;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F075;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:63.0pt;
	text-indent:-21.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F06C;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:84.0pt;
	text-indent:-21.0pt;
	font-family:Wingdings;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F06E;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:105.0pt;
	text-indent:-21.0pt;
	font-family:Wingdings;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F075;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:126.0pt;
	text-indent:-21.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F06C;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:147.0pt;
	text-indent:-21.0pt;
	font-family:Wingdings;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F06E;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:168.0pt;
	text-indent:-21.0pt;
	font-family:Wingdings;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F075;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:189.0pt;
	text-indent:-21.0pt;
	font-family:Wingdings;}
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"ZH-CN" link=3D"#0563C1" vlink=3D"#954F72" style=3D"text-justi=
fy-trim:punctuation">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi, Toerless,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I am working on the charter tex=
t. It is not difficult to categetied the work items into 4 classes: ANI&#43=
;, ASA, BRSKI, Use cases. I am intending to put NOCs into ANI&#43;. I will =
send you a reword version on next Monday.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">For milestones, giving that we =
have a long document waiting list as long as 20. It would not sufficient to=
 satisfy everyone for just 5 milestones by saying everyone should have no m=
ore than one document through. We would
 face more than 10 individuals asking for adoption. Anyway, here are my cho=
ice for the first 5:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">ASA Lifecycle (Lucent)<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">ASA guideline (Brian C)<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">GRASP Distribution (Bing Liu)<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Constrained Join Proxy for Boot=
strapping Protocols (Michael R.)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&#43; One BRSKI document<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">This would looks good when we f=
ace IESG. Then, we may able to adopt 2 or 3 more document out of written mi=
lestones, I guess. But it would looks bad if we have more than 10 WG docume=
nt parallel. PS: we still have 7 WG
 documents showing now, though 3 of them passed IESG review and waiting by =
MISREF &#8211; ACP!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Sheng<o:p></o:p></span></p>
</div>
</body>
</html>

--_000_5D36713D8A4E7348A7E10DF7437A4B929038B9FANKGEML515MBXchi_--


From nobody Fri Mar 15 08:18:13 2019
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 B87B3128678 for <anima@ietfa.amsl.com>; Fri, 15 Mar 2019 08:18:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level: 
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 f_pJ3KK48gnZ for <anima@ietfa.amsl.com>; Fri, 15 Mar 2019 08:18:09 -0700 (PDT)
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 7F8CC129A85 for <anima@ietf.org>; Fri, 15 Mar 2019 08:18:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13250; q=dns/txt; s=iport; t=1552663083; x=1553872683; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=wevSjTK0QJIhLWRvqYtJXsyS+VH/0MEz/+516VeT6og=; b=TCmW226ujBHe3dZd9UEJ9bthbBnX5uEmCEPwvechsGC7KfdoeQZK0E6T 39MaVo9SJdQY78q/IGrSlSWih7p73k6gMztEhhO6LZd6NX1CnKjc6l92w NnLSfL62dAVpwTDHr+PKzp280r/ByAneU7SXpwTPy5SkU7oaiQRtfMhNc w=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DnAADfwItc/xbLJq1kGwEBAQEDAQE?= =?us-ascii?q?BBwMBAQGBZYEOU4EXUDMnhAuIe4xPkjuHcQgDAQEYAQqESQKEcjgSAQEDAQE?= =?us-ascii?q?JAQMCbRwMhUoBAQEDAQEBIUsLBQsLGCcDAgInHxEGE4MiAYFtCA+rfIEvhUa?= =?us-ascii?q?EXgoFgS+BSYoBgX+BEScfgh4ugx4BAYRrMYImA5FOknwJhGGOQhmLDIhEmwq?= =?us-ascii?q?CcAIEBgUCFYFeITSBIjMaCBsVOyoBgkE+ik6FQD4DMI57AQE?=
X-IronPort-AV: E=Sophos;i="5.58,482,1544486400";  d="asc'?scan'208,217";a="10764614"
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-SEED-SHA; 15 Mar 2019 15:18:01 +0000
Received: from [10.61.219.192] ([10.61.219.192]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x2FFI0SB026888 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 15 Mar 2019 15:18:00 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <20E1F3B4-EE2F-4BFA-B9EB-7EE576BF9547@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_28FA3381-196E-43A9-95C7-97BD8190B8F1"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Fri, 15 Mar 2019 16:17:58 +0100
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B929038B9FA@NKGEML515-MBX.china.huawei.com>
Cc: Toerless Eckert <tte@cs.fau.de>, Toerless Eckert <toerless.eckert@huawei.com>, "anima@ietf.org" <anima@ietf.org>
To: Sheng Jiang <jiangsheng@huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B929038B9FA@NKGEML515-MBX.china.huawei.com>
X-Mailer: Apple Mail (2.3445.102.3)
X-Outbound-SMTP-Client: 10.61.219.192, [10.61.219.192]
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/iHxOThFKV-XChCEQ2rUKLFEooH8>
Subject: Re: [Anima] Potential Milestones for ANIMA new charter
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 15 Mar 2019 15:18:12 -0000

--Apple-Mail=_28FA3381-196E-43A9-95C7-97BD8190B8F1
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_C0670009-9D53-483B-BE6E-8A80761E505A"


--Apple-Mail=_C0670009-9D53-483B-BE6E-8A80761E505A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Sheng,

Forgive me, but I believe that the charter text above the milestones =
needs a touch up.  I also see somewhere around six drafts worth of BRSKI =
work coming down the pike on their own.  They are:

draft-ietf-anima-constrained-voucher
draft-ietf-anima-contrained-voucher
draft-fries-anima-brski-async-enroll
draft-lear-eap-teap-brski
draft-vanderstok-anima-constrained-join-proxy
draft-richardson-anima-smarkarklink

And I expect that draft-lear-brski-pop will live to see another day.

Now it may be the right thing to split off this work into a separate WG, =
or it may be the right thing to continue in ANIMA.  I expect that some =
of the above can also consolidate, but there=E2=80=99s still a lot of =
work to be done, and cramming all of that into one draft would be =
inadvisable ;-)

Eliot

> On 15 Mar 2019, at 07:51, Sheng Jiang <jiangsheng@huawei.com> wrote:
>=20
> Hi, Toerless,
>=20
> I am working on the charter text. It is not difficult to categetied =
the work items into 4 classes: ANI+, ASA, BRSKI, Use cases. I am =
intending to put NOCs into ANI+. I will send you a reword version on =
next Monday.
>=20
> For milestones, giving that we have a long document waiting list as =
long as 20. It would not sufficient to satisfy everyone for just 5 =
milestones by saying everyone should have no more than one document =
through. We would face more than 10 individuals asking for adoption. =
Anyway, here are my choice for the first 5:
>=20
> ASA Lifecycle (Lucent)
> ASA guideline (Brian C)
> GRASP Distribution (Bing Liu)
> Constrained Join Proxy for Bootstrapping Protocols (Michael R.)
> + One BRSKI document
>=20
> This would looks good when we face IESG. Then, we may able to adopt 2 =
or 3 more document out of written milestones, I guess. But it would =
looks bad if we have more than 10 WG document parallel. PS: we still =
have 7 WG documents showing now, though 3 of them passed IESG review and =
waiting by MISREF =E2=80=93 ACP!
>=20
> Cheers,
>=20
> Sheng
> _______________________________________________
> Anima mailing list
> Anima@ietf.org <mailto:Anima@ietf.org>
> https://www.ietf.org/mailman/listinfo/anima =
<https://www.ietf.org/mailman/listinfo/anima>

--Apple-Mail=_C0670009-9D53-483B-BE6E-8A80761E505A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Sheng,<div class=3D""><br class=3D""></div><div class=3D"">Forgive me, =
but I believe that the charter text above the milestones needs a touch =
up. &nbsp;I also see somewhere around six drafts worth of BRSKI work =
coming down the pike on their own. &nbsp;They are:</div><div =
class=3D""><br class=3D""></div><div class=3D""><ul =
class=3D"MailOutline"><li =
class=3D"">draft-ietf-anima-constrained-voucher</li><li =
class=3D"">draft-ietf-anima-contrained-voucher</li><li =
class=3D"">draft-fries-anima-brski-async-enroll</li><li =
class=3D"">draft-lear-eap-teap-brski</li><li =
class=3D"">draft-vanderstok-anima-constrained-join-proxy</li><li =
class=3D"">draft-richardson-anima-smarkarklink</li></ul></div><div =
class=3D""><br class=3D""></div><div class=3D""><div>And I expect that =
draft-lear-brski-pop will live to see another day.</div><div><br =
class=3D""></div><div>Now it may be the right thing to split off this =
work into a separate WG, or it may be the right thing to continue in =
ANIMA. &nbsp;I expect that some of the above can also consolidate, but =
there=E2=80=99s still a lot of work to be done, and cramming all of that =
into one draft would be inadvisable ;-)</div><div><br =
class=3D""></div><div>Eliot</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On 15 Mar 2019, at 07:51, Sheng =
Jiang &lt;<a href=3D"mailto:jiangsheng@huawei.com" =
class=3D"">jiangsheng@huawei.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><div style=3D"margin: 0cm 0cm 0.0001pt; =
text-align: justify; font-size: 10.5pt; font-family: Calibri, =
sans-serif;" class=3D""><span lang=3D"EN-US" class=3D"">Hi, =
Toerless,<o:p class=3D""></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; text-align: justify; font-size: 10.5pt; font-family: =
Calibri, sans-serif;" class=3D""><span lang=3D"EN-US" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; text-align: justify; font-size: 10.5pt; font-family: Calibri, =
sans-serif;" class=3D""><span lang=3D"EN-US" class=3D"">I am working on =
the charter text. It is not difficult to categetied the work items into =
4 classes: ANI+, ASA, BRSKI, Use cases. I am intending to put NOCs into =
ANI+. I will send you a reword version on next Monday.<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
text-align: justify; font-size: 10.5pt; font-family: Calibri, =
sans-serif;" class=3D""><span lang=3D"EN-US" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; text-align: justify; font-size: 10.5pt; font-family: Calibri, =
sans-serif;" class=3D""><span lang=3D"EN-US" class=3D"">For milestones, =
giving that we have a long document waiting list as long as 20. It would =
not sufficient to satisfy everyone for just 5 milestones by saying =
everyone should have no more than one document through. We would face =
more than 10 individuals asking for adoption. Anyway, here are my choice =
for the first 5:<o:p class=3D""></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; text-align: justify; font-size: 10.5pt; font-family: =
Calibri, sans-serif;" class=3D""><span lang=3D"EN-US" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; text-align: justify; font-size: 10.5pt; font-family: Calibri, =
sans-serif;" class=3D""><span lang=3D"EN-US" class=3D"">ASA Lifecycle =
(Lucent)<o:p class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; text-align: justify; font-size: 10.5pt; font-family: Calibri, =
sans-serif;" class=3D""><span lang=3D"EN-US" class=3D"">ASA guideline =
(Brian C)<o:p class=3D""></o:p></span></div><div style=3D"margin: 0cm =
0cm 0.0001pt; text-align: justify; font-size: 10.5pt; font-family: =
Calibri, sans-serif;" class=3D""><span lang=3D"EN-US" class=3D"">GRASP =
Distribution (Bing Liu)<o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: =
10.5pt; font-family: Calibri, sans-serif;" class=3D""><span lang=3D"EN-US"=
 class=3D"">Constrained Join Proxy for Bootstrapping Protocols (Michael =
R.)<o:p class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; text-align: justify; font-size: 10.5pt; font-family: Calibri, =
sans-serif;" class=3D""><span lang=3D"EN-US" class=3D"">+ One BRSKI =
document<o:p class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; text-align: justify; font-size: 10.5pt; font-family: Calibri, =
sans-serif;" class=3D""><span lang=3D"EN-US" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; text-align: justify; font-size: 10.5pt; font-family: Calibri, =
sans-serif;" class=3D""><span lang=3D"EN-US" class=3D"">This would looks =
good when we face IESG. Then, we may able to adopt 2 or 3 more document =
out of written milestones, I guess. But it would looks bad if we have =
more than 10 WG document parallel. PS: we still have 7 WG documents =
showing now, though 3 of them passed IESG review and waiting by MISREF =
=E2=80=93 ACP!<o:p class=3D""></o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; text-align: justify; font-size: 10.5pt; font-family: =
Calibri, sans-serif;" class=3D""><span lang=3D"EN-US" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; text-align: justify; font-size: 10.5pt; font-family: Calibri, =
sans-serif;" class=3D""><span lang=3D"EN-US" class=3D"">Cheers,<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
text-align: justify; font-size: 10.5pt; font-family: Calibri, =
sans-serif;" class=3D""><span lang=3D"EN-US" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; text-align: justify; font-size: 10.5pt; font-family: Calibri, =
sans-serif;" class=3D""><span lang=3D"EN-US" class=3D"">Sheng<o:p =
class=3D""></o:p></span></div></div><span style=3D"caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">Anima mailing list</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"mailto:Anima@ietf.org" style=3D"color: rgb(149, 79, 114); =
text-decoration: underline; font-family: Helvetica; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">Anima@ietf.org</a><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/anima" style=3D"color: =
rgb(149, 79, 114); text-decoration: underline; font-family: Helvetica; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" =
class=3D"">https://www.ietf.org/mailman/listinfo/anima</a></div></blockquo=
te></div><br class=3D""></div></body></html>=

--Apple-Mail=_C0670009-9D53-483B-BE6E-8A80761E505A--

--Apple-Mail=_28FA3381-196E-43A9-95C7-97BD8190B8F1
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQEzBAEBCAAdFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAlyLwiYACgkQh7ZrRtnS
ejNjWAf/Tb3YmdWDyT4061hZeiz5T5Mxx3x8ciQ/J+NKYBxZeLD5JBkB477SLXec
ESgw/zuTaq6kBfsW8whQ6OP7vUVNEFjMJzn2b6K4jDtNmVMHAW8K3s15Kyg24GUE
6xQn++559F+RJA7m2XQg0LSZjNUxGXScpBhBjJH5j59FWE0Ho3OfDx5nxlndhk/n
CT3bzoDjyruQHTXOi6MnKJgFGMUGnpwX6MGP2J6tnbjIch6gCdH5k45c3aHa7uW4
0zRAvD+XsodRUXBSrGwnDxggJuGjwZepuKZAUaVRYlowDgYRGZqOfdDw76+TVfpi
zpf5Krd3+IBQSr3HF9C/S1TTysLykA==
=BPb1
-----END PGP SIGNATURE-----

--Apple-Mail=_28FA3381-196E-43A9-95C7-97BD8190B8F1--


From nobody Fri Mar 15 17:56:44 2019
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 DB2FE12D110 for <anima@ietfa.amsl.com>; Fri, 15 Mar 2019 17:56:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 x7k3V1A2G20P for <anima@ietfa.amsl.com>; Fri, 15 Mar 2019 17:56:41 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 C350012787F for <anima@ietf.org>; Fri, 15 Mar 2019 17:56:40 -0700 (PDT)
Received: from lhreml709-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id A4D042243AC5FACE7C30; Sat, 16 Mar 2019 00:56:37 +0000 (GMT)
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sat, 16 Mar 2019 00:56:37 +0000
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml701-chm.china.huawei.com (10.201.108.50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Sat, 16 Mar 2019 00:56:36 +0000
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml701-chm.china.huawei.com (10.201.108.50) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1591.10 via Frontend Transport; Sat, 16 Mar 2019 00:56:36 +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.0415.000; Sat, 16 Mar 2019 08:56:27 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Eliot Lear <lear@cisco.com>
CC: Toerless Eckert <tte@cs.fau.de>, Toerless Eckert <toerless.eckert@huawei.com>, "anima@ietf.org" <anima@ietf.org>
Thread-Topic: [Anima] Potential Milestones for ANIMA new charter
Thread-Index: AdTa+jwafGdRprrVRti8bHBG3GkyuAABPs0AACP5BIA=
Date: Sat, 16 Mar 2019 00:56:26 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B929038CF2A@NKGEML515-MBX.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B929038B9FA@NKGEML515-MBX.china.huawei.com> <20E1F3B4-EE2F-4BFA-B9EB-7EE576BF9547@cisco.com>
In-Reply-To: <20E1F3B4-EE2F-4BFA-B9EB-7EE576BF9547@cisco.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.171.209]
Content-Type: multipart/alternative; boundary="_000_5D36713D8A4E7348A7E10DF7437A4B929038CF2ANKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/8XYwYqZt4QE8qLhXrRxF0RoFcpo>
Subject: Re: [Anima] Potential Milestones for ANIMA new charter
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 16 Mar 2019 00:56:44 -0000

--_000_5D36713D8A4E7348A7E10DF7437A4B929038CF2ANKGEML515MBXchi_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGksIEVsaW90LA0KDQpBcyB5b3Uga25vdywgdGhlIGNoYXJ0ZXIgdGV4dCBpcyBkaWZmZXJlbnQg
ZnJvbSB0aGUgbWlsZXN0b25lcy4gSW4gY2hhcnRlciB0ZXh0LCB3ZSB3aWxsIGhhdmUgYSBwYXJh
Z3JhcGggdG8gZGVzY3JpYmUgdGhlIEJSU0tJIHJlbGV2YW50IHdvcmtzLiBJbiBwcmluY2lwbGUs
IGFsbCBCUlNLSSB3b3JrcywgZXZlbiB0aG9zZSBoYXZlIG5vdCBiZWVuIG1lbnRpb25lZCwgd291
bGQgYmUgY292ZXJlZC4gU28sIEJSU0tJIHdvcmtzLCBubyBtYXR0ZXIgdGhleSBhcmUgbGlzdGVk
IGFzIG1pbGVzdG9uZXMgb3Igbm90LCBhcmUgaW4gV0cgc2NvcGUuDQoNCk1pbGVzdG9uZXMgYXJl
IHRoZXNlIHdvcmsgaXRlbXMgdGhhdCBXRyBNVVNUIGRlbGl2ZXIgaW4gYSBsaW1pdGVkIHRpbWUs
IHNheSBhIHllYXIgb3Igb25lIGFuZCBoYWxmIHllYXJzLiBTbywgYXMgV0cgY2hhaXJzLCB3ZSB3
b3VsZCBsaWtlIHRvIGhhdmUgYSBzaG9ydGVyIGxpc3QgZm9yIGVhY2ggcGVyaW9kLCBmb3Igd2hp
Y2ggZXZlcnkgd29yayBpdGVtIGhhcyBlbm91Z2ggZW5lcmd5IHRvIGNvbXBsZXRlIGluIHRpbWUu
IFRoaXMgaXMgYWxzbyBJRVNHIHdvdWxkIGxpa2UgdG8gc2VlLiBXZSBjb3VsZCBlYXNpbHkgYWRk
IG1pbGVzdG9uZXMgbGF0ZXIgd2hlbiB0aGUgV0cgaGFkIHNob3duIGVub3VnaCBpbnRlcmVzdHMg
YW5kIGVuZXJneSBmb3IgbmV3IGluLXNjb3BlIHdvcmtzLg0KDQrigJwrIE9uZSBCUlNLSSBkb2N1
bWVudOKAnSBtZWFucyBuZXdseSBhZG9wdCBvbmUgbW9yZSBCUlNLSSBkb2N1bWVudC4gVGhlIHJl
YXNvbiB0aGF0IHdlIGRvIG5vdCB3YW50IHRvbyBtYW55IG5ldyBCUlNLSSBkb2N1bWVudCBpbW1l
ZGlhdGVseSBpcyB0aGF0IHRoZSBXRyBuZWVkIGVuZXJneSB0byBndWFyYW50ZWUgdGhlIGN1cnJl
bnQgYWRvcHRlZCBCUlNLSSB3b3JrcywgaW5jbHVkaW5nIHRoZSBtYWluIEJSU0tJIGRvY3VtZW50
IGFuZCBjb25zdHJhaW5lZCB2b3VjaGVyLCB0byBiZSBjb21wbGV0ZWQgYXMgc29vbiBhcyBwb3Nz
aWJsZSB3aXRoIGhpZ2ggcXVhbGl0eS4NCg0KUmVnYXJkcywNCg0KU2hlbmcNCg0KRnJvbTogRWxp
b3QgTGVhciBbbWFpbHRvOmxlYXJAY2lzY28uY29tXQ0KU2VudDogRnJpZGF5LCBNYXJjaCAxNSwg
MjAxOSAxMToxOCBQTQ0KVG86IFNoZW5nIEppYW5nIDxqaWFuZ3NoZW5nQGh1YXdlaS5jb20+DQpD
YzogVG9lcmxlc3MgRWNrZXJ0IDx0dGVAY3MuZmF1LmRlPjsgVG9lcmxlc3MgRWNrZXJ0IDx0b2Vy
bGVzcy5lY2tlcnRAaHVhd2VpLmNvbT47IGFuaW1hQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW0Fu
aW1hXSBQb3RlbnRpYWwgTWlsZXN0b25lcyBmb3IgQU5JTUEgbmV3IGNoYXJ0ZXINCg0KSGkgU2hl
bmcsDQoNCkZvcmdpdmUgbWUsIGJ1dCBJIGJlbGlldmUgdGhhdCB0aGUgY2hhcnRlciB0ZXh0IGFi
b3ZlIHRoZSBtaWxlc3RvbmVzIG5lZWRzIGEgdG91Y2ggdXAuICBJIGFsc28gc2VlIHNvbWV3aGVy
ZSBhcm91bmQgc2l4IGRyYWZ0cyB3b3J0aCBvZiBCUlNLSSB3b3JrIGNvbWluZyBkb3duIHRoZSBw
aWtlIG9uIHRoZWlyIG93bi4gIFRoZXkgYXJlOg0KDQoNCiAgKiAgIGRyYWZ0LWlldGYtYW5pbWEt
Y29uc3RyYWluZWQtdm91Y2hlcg0KICAqICAgZHJhZnQtaWV0Zi1hbmltYS1jb250cmFpbmVkLXZv
dWNoZXINCiAgKiAgIGRyYWZ0LWZyaWVzLWFuaW1hLWJyc2tpLWFzeW5jLWVucm9sbA0KICAqICAg
ZHJhZnQtbGVhci1lYXAtdGVhcC1icnNraQ0KICAqICAgZHJhZnQtdmFuZGVyc3Rvay1hbmltYS1j
b25zdHJhaW5lZC1qb2luLXByb3h5DQogICogICBkcmFmdC1yaWNoYXJkc29uLWFuaW1hLXNtYXJr
YXJrbGluaw0KDQpBbmQgSSBleHBlY3QgdGhhdCBkcmFmdC1sZWFyLWJyc2tpLXBvcCB3aWxsIGxp
dmUgdG8gc2VlIGFub3RoZXIgZGF5Lg0KDQpOb3cgaXQgbWF5IGJlIHRoZSByaWdodCB0aGluZyB0
byBzcGxpdCBvZmYgdGhpcyB3b3JrIGludG8gYSBzZXBhcmF0ZSBXRywgb3IgaXQgbWF5IGJlIHRo
ZSByaWdodCB0aGluZyB0byBjb250aW51ZSBpbiBBTklNQS4gIEkgZXhwZWN0IHRoYXQgc29tZSBv
ZiB0aGUgYWJvdmUgY2FuIGFsc28gY29uc29saWRhdGUsIGJ1dCB0aGVyZeKAmXMgc3RpbGwgYSBs
b3Qgb2Ygd29yayB0byBiZSBkb25lLCBhbmQgY3JhbW1pbmcgYWxsIG9mIHRoYXQgaW50byBvbmUg
ZHJhZnQgd291bGQgYmUgaW5hZHZpc2FibGUgOy0pDQoNCkVsaW90DQoNCg0KT24gMTUgTWFyIDIw
MTksIGF0IDA3OjUxLCBTaGVuZyBKaWFuZyA8amlhbmdzaGVuZ0BodWF3ZWkuY29tPG1haWx0bzpq
aWFuZ3NoZW5nQGh1YXdlaS5jb20+PiB3cm90ZToNCg0KSGksIFRvZXJsZXNzLA0KDQpJIGFtIHdv
cmtpbmcgb24gdGhlIGNoYXJ0ZXIgdGV4dC4gSXQgaXMgbm90IGRpZmZpY3VsdCB0byBjYXRlZ2V0
aWVkIHRoZSB3b3JrIGl0ZW1zIGludG8gNCBjbGFzc2VzOiBBTkkrLCBBU0EsIEJSU0tJLCBVc2Ug
Y2FzZXMuIEkgYW0gaW50ZW5kaW5nIHRvIHB1dCBOT0NzIGludG8gQU5JKy4gSSB3aWxsIHNlbmQg
eW91IGEgcmV3b3JkIHZlcnNpb24gb24gbmV4dCBNb25kYXkuDQoNCkZvciBtaWxlc3RvbmVzLCBn
aXZpbmcgdGhhdCB3ZSBoYXZlIGEgbG9uZyBkb2N1bWVudCB3YWl0aW5nIGxpc3QgYXMgbG9uZyBh
cyAyMC4gSXQgd291bGQgbm90IHN1ZmZpY2llbnQgdG8gc2F0aXNmeSBldmVyeW9uZSBmb3IganVz
dCA1IG1pbGVzdG9uZXMgYnkgc2F5aW5nIGV2ZXJ5b25lIHNob3VsZCBoYXZlIG5vIG1vcmUgdGhh
biBvbmUgZG9jdW1lbnQgdGhyb3VnaC4gV2Ugd291bGQgZmFjZSBtb3JlIHRoYW4gMTAgaW5kaXZp
ZHVhbHMgYXNraW5nIGZvciBhZG9wdGlvbi4gQW55d2F5LCBoZXJlIGFyZSBteSBjaG9pY2UgZm9y
IHRoZSBmaXJzdCA1Og0KDQpBU0EgTGlmZWN5Y2xlIChMdWNlbnQpDQpBU0EgZ3VpZGVsaW5lIChC
cmlhbiBDKQ0KR1JBU1AgRGlzdHJpYnV0aW9uIChCaW5nIExpdSkNCkNvbnN0cmFpbmVkIEpvaW4g
UHJveHkgZm9yIEJvb3RzdHJhcHBpbmcgUHJvdG9jb2xzIChNaWNoYWVsIFIuKQ0KKyBPbmUgQlJT
S0kgZG9jdW1lbnQNCg0KVGhpcyB3b3VsZCBsb29rcyBnb29kIHdoZW4gd2UgZmFjZSBJRVNHLiBU
aGVuLCB3ZSBtYXkgYWJsZSB0byBhZG9wdCAyIG9yIDMgbW9yZSBkb2N1bWVudCBvdXQgb2Ygd3Jp
dHRlbiBtaWxlc3RvbmVzLCBJIGd1ZXNzLiBCdXQgaXQgd291bGQgbG9va3MgYmFkIGlmIHdlIGhh
dmUgbW9yZSB0aGFuIDEwIFdHIGRvY3VtZW50IHBhcmFsbGVsLiBQUzogd2Ugc3RpbGwgaGF2ZSA3
IFdHIGRvY3VtZW50cyBzaG93aW5nIG5vdywgdGhvdWdoIDMgb2YgdGhlbSBwYXNzZWQgSUVTRyBy
ZXZpZXcgYW5kIHdhaXRpbmcgYnkgTUlTUkVGIOKAkyBBQ1AhDQoNCkNoZWVycywNCg0KU2hlbmcN
Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpBbmltYSBt
YWlsaW5nIGxpc3QNCkFuaW1hQGlldGYub3JnPG1haWx0bzpBbmltYUBpZXRmLm9yZz4NCmh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vYW5pbWENCg0K

--_000_5D36713D8A4E7348A7E10DF7437A4B929038CF2ANKGEML515MBXchi_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7
fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTrlrovkvZM7DQoJcGFub3NlLTE6MiAxIDYgMCAz
IDEgMSAxIDEgMTt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0K
CXBhbm9zZS0xOjIgNCA1IDMgNSA0IDYgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls
eTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6IlxA5a6L5L2TIjsNCglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAx
O30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBk
aXYuTXNvTm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZv
bnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk65a6L5L2TO30NCmE6bGluaywgc3Bhbi5Nc29I
eXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1k
ZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93
ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29y
YXRpb246dW5kZXJsaW5lO30NCnNwYW4uRW1haWxTdHlsZTE3DQoJe21zby1zdHlsZS10eXBlOnBl
cnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5
N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtY29tcG9z
ZTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0
O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQt
c2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0
Ow0KCW1hcmdpbjo3Mi4wcHQgOTAuMHB0IDcyLjBwdCA5MC4wcHQ7fQ0KZGl2LldvcmRTZWN0aW9u
MQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQovKiBMaXN0IERlZmluaXRpb25zICovDQpAbGlzdCBs
MA0KCXttc28tbGlzdC1pZDo5NjUyODIyNTY7DQoJbXNvLWxpc3QtdGVtcGxhdGUtaWRzOjEyNTQw
MjgzMjY7fQ0KQGxpc3QgbDA6bGV2ZWwxDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxl
dDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjM2LjBwdDsNCglt
c28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglt
c28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBs
MDpsZXZlbDINCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10
ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOjcyLjBwdDsNCgltc28tbGV2ZWwtbnVtYmVyLXBv
c2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCgltc28tYW5zaS1mb250LXNpemU6
MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJbXNvLWJpZGktZm9udC1mYW1p
bHk6IlRpbWVzIE5ldyBSb21hbiI7fQ0KQGxpc3QgbDA6bGV2ZWwzDQoJe21zby1sZXZlbC1udW1i
ZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1z
dG9wOjEwOC4wcHQ7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5k
ZW50Oi0xOC4wcHQ7DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpX
aW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw0DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1
bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjE0NC4wcHQ7
DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7
DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0K
QGxpc3QgbDA6bGV2ZWw1DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28t
bGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjE4MC4wcHQ7DQoJbXNvLWxldmVs
LW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJbXNvLWFuc2kt
Zm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2
ZWw2DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrv
gqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjIxNi4wcHQ7DQoJbXNvLWxldmVsLW51bWJlci1wb3Np
dGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJbXNvLWFuc2ktZm9udC1zaXplOjEw
LjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw3DQoJe21zby1s
ZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxl
dmVsLXRhYi1zdG9wOjI1Mi4wcHQ7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0K
CXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250
LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw4DQoJe21zby1sZXZlbC1udW1iZXIt
Zm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9w
OjI4OC4wcHQ7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50
Oi0xOC4wcHQ7DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpXaW5n
ZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw5DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxl
dDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjMyNC4wcHQ7DQoJ
bXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJ
bXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0Kb2wN
Cgl7bWFyZ2luLWJvdHRvbTowY207fQ0KdWwNCgl7bWFyZ2luLWJvdHRvbTowY207fQ0KLS0+PC9z
dHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVk
aXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28g
OV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJl
ZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9o
ZWFkPg0KPGJvZHkgbGFuZz0iWkgtQ04iIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRp
diBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+SGksIEVsaW90LDxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5B
cyB5b3Uga25vdywgdGhlIGNoYXJ0ZXIgdGV4dCBpcyBkaWZmZXJlbnQgZnJvbSB0aGUgbWlsZXN0
b25lcy4gSW4gY2hhcnRlciB0ZXh0LCB3ZSB3aWxsIGhhdmUgYSBwYXJhZ3JhcGggdG8gZGVzY3Jp
YmUgdGhlIEJSU0tJIHJlbGV2YW50IHdvcmtzLiBJbg0KIHByaW5jaXBsZSwgYWxsIEJSU0tJIHdv
cmtzLCBldmVuIHRob3NlIGhhdmUgbm90IGJlZW4gbWVudGlvbmVkLCB3b3VsZCBiZSBjb3ZlcmVk
LiBTbywgQlJTS0kgd29ya3MsIG5vIG1hdHRlciB0aGV5IGFyZSBsaXN0ZWQgYXMgbWlsZXN0b25l
cyBvciBub3QsIGFyZSBpbiBXRyBzY29wZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Qi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+TWlsZXN0b25lcyBhcmUgdGhl
c2Ugd29yayBpdGVtcyB0aGF0IFdHIE1VU1QgZGVsaXZlciBpbiBhIGxpbWl0ZWQgdGltZSwgc2F5
IGEgeWVhciBvciBvbmUgYW5kIGhhbGYgeWVhcnMuIFNvLCBhcyBXRyBjaGFpcnMsIHdlIHdvdWxk
IGxpa2UgdG8gaGF2ZQ0KIGEgc2hvcnRlciBsaXN0IGZvciBlYWNoIHBlcmlvZCwgZm9yIHdoaWNo
IGV2ZXJ5IHdvcmsgaXRlbSBoYXMgZW5vdWdoIGVuZXJneSB0byBjb21wbGV0ZSBpbiB0aW1lLiBU
aGlzIGlzIGFsc28gSUVTRyB3b3VsZCBsaWtlIHRvIHNlZS4gV2UgY291bGQgZWFzaWx5IGFkZCBt
aWxlc3RvbmVzIGxhdGVyIHdoZW4gdGhlIFdHIGhhZCBzaG93biBlbm91Z2ggaW50ZXJlc3RzIGFu
ZCBlbmVyZ3kgZm9yIG5ldyBpbi1zY29wZSB3b3Jrcy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTox
MC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMx
RjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+4oCcJiM0MzsgT25l
IEJSU0tJIGRvY3VtZW504oCdIG1lYW5zIG5ld2x5IGFkb3B0IG9uZSBtb3JlIEJSU0tJIGRvY3Vt
ZW50LiBUaGUgcmVhc29uIHRoYXQgd2UgZG8gbm90IHdhbnQgdG9vIG1hbnkgbmV3IEJSU0tJIGRv
Y3VtZW50IGltbWVkaWF0ZWx5IGlzIHRoYXQNCiB0aGUgV0cgbmVlZCBlbmVyZ3kgdG8gZ3VhcmFu
dGVlIHRoZSBjdXJyZW50IGFkb3B0ZWQgQlJTS0kgd29ya3MsIGluY2x1ZGluZyB0aGUgbWFpbiBC
UlNLSSBkb2N1bWVudCBhbmQgY29uc3RyYWluZWQgdm91Y2hlciwgdG8gYmUgY29tcGxldGVkIGFz
IHNvb24gYXMgcG9zc2libGUgd2l0aCBoaWdoIHF1YWxpdHkuPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPlJlZ2FyZHMs
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQt
c2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOiMxRjQ5N0QiPlNoZW5nPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9y
ZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQgMGNtIDBjbSAwY20iPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+RnJv
bTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiBFbGlvdCBMZWFyIFtt
YWlsdG86bGVhckBjaXNjby5jb21dDQo8YnI+DQo8Yj5TZW50OjwvYj4gRnJpZGF5LCBNYXJjaCAx
NSwgMjAxOSAxMToxOCBQTTxicj4NCjxiPlRvOjwvYj4gU2hlbmcgSmlhbmcgJmx0O2ppYW5nc2hl
bmdAaHVhd2VpLmNvbSZndDs8YnI+DQo8Yj5DYzo8L2I+IFRvZXJsZXNzIEVja2VydCAmbHQ7dHRl
QGNzLmZhdS5kZSZndDs7IFRvZXJsZXNzIEVja2VydCAmbHQ7dG9lcmxlc3MuZWNrZXJ0QGh1YXdl
aS5jb20mZ3Q7OyBhbmltYUBpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW0FuaW1h
XSBQb3RlbnRpYWwgTWlsZXN0b25lcyBmb3IgQU5JTUEgbmV3IGNoYXJ0ZXI8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFu
Zz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5IaSBTaGVuZyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIGxhbmc9IkVOLVVTIj5Gb3JnaXZlIG1lLCBidXQgSSBiZWxpZXZlIHRoYXQgdGhlIGNoYXJ0
ZXIgdGV4dCBhYm92ZSB0aGUgbWlsZXN0b25lcyBuZWVkcyBhIHRvdWNoIHVwLiAmbmJzcDtJIGFs
c28gc2VlIHNvbWV3aGVyZSBhcm91bmQgc2l4IGRyYWZ0cyB3b3J0aCBvZiBCUlNLSSB3b3JrIGNv
bWluZyBkb3duIHRoZSBwaWtlIG9uIHRoZWlyIG93bi4gJm5ic3A7VGhleSBhcmU6PG86cD48L286
cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
bGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
Cjx1bCB0eXBlPSJkaXNjIj4NCjxsaSBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87bXNvLWxpc3Q6bDAgbGV2
ZWwxIGxmbzEiPg0KPHNwYW4gbGFuZz0iRU4tVVMiPmRyYWZ0LWlldGYtYW5pbWEtY29uc3RyYWlu
ZWQtdm91Y2hlcjxvOnA+PC9vOnA+PC9zcGFuPjwvbGk+PGxpIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bztt
c28tbGlzdDpsMCBsZXZlbDEgbGZvMSI+DQo8c3BhbiBsYW5nPSJFTi1VUyI+ZHJhZnQtaWV0Zi1h
bmltYS1jb250cmFpbmVkLXZvdWNoZXI8bzpwPjwvbzpwPjwvc3Bhbj48L2xpPjxsaSBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0
b20tYWx0OmF1dG87bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzEiPg0KPHNwYW4gbGFuZz0iRU4tVVMi
PmRyYWZ0LWZyaWVzLWFuaW1hLWJyc2tpLWFzeW5jLWVucm9sbDxvOnA+PC9vOnA+PC9zcGFuPjwv
bGk+PGxpIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzttc28tbGlzdDpsMCBsZXZlbDEgbGZvMSI+DQo8c3Bh
biBsYW5nPSJFTi1VUyI+ZHJhZnQtbGVhci1lYXAtdGVhcC1icnNraTxvOnA+PC9vOnA+PC9zcGFu
PjwvbGk+PGxpIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzttc28tbGlzdDpsMCBsZXZlbDEgbGZvMSI+DQo8
c3BhbiBsYW5nPSJFTi1VUyI+ZHJhZnQtdmFuZGVyc3Rvay1hbmltYS1jb25zdHJhaW5lZC1qb2lu
LXByb3h5PG86cD48L286cD48L3NwYW4+PC9saT48bGkgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21zby1s
aXN0OmwwIGxldmVsMSBsZm8xIj4NCjxzcGFuIGxhbmc9IkVOLVVTIj5kcmFmdC1yaWNoYXJkc29u
LWFuaW1hLXNtYXJrYXJrbGluazxvOnA+PC9vOnA+PC9zcGFuPjwvbGk+PC91bD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPkFuZCBJIGV4cGVjdCB0aGF0IGRyYWZ0LWxlYXItYnJz
a2ktcG9wIHdpbGwgbGl2ZSB0byBzZWUgYW5vdGhlciBkYXkuPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5Ob3cgaXQgbWF5IGJlIHRoZSByaWdodCB0aGlu
ZyB0byBzcGxpdCBvZmYgdGhpcyB3b3JrIGludG8gYSBzZXBhcmF0ZSBXRywgb3IgaXQgbWF5IGJl
IHRoZSByaWdodCB0aGluZyB0byBjb250aW51ZSBpbiBBTklNQS4gJm5ic3A7SSBleHBlY3QgdGhh
dCBzb21lIG9mIHRoZSBhYm92ZSBjYW4gYWxzbyBjb25zb2xpZGF0ZSwgYnV0IHRoZXJl4oCZcyBz
dGlsbCBhIGxvdCBvZiB3b3JrIHRvIGJlDQogZG9uZSwgYW5kIGNyYW1taW5nIGFsbCBvZiB0aGF0
IGludG8gb25lIGRyYWZ0IHdvdWxkIGJlIGluYWR2aXNhYmxlIDstKTxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+RWxpb3Q8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyI+PGJyPg0KPGJyPg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9
Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPk9uIDE1IE1hciAyMDE5LCBhdCAwNzo1MSwg
U2hlbmcgSmlhbmcgJmx0OzxhIGhyZWY9Im1haWx0bzpqaWFuZ3NoZW5nQGh1YXdlaS5jb20iPmpp
YW5nc2hlbmdAaHVhd2VpLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
dGV4dC1hbGlnbjpqdXN0aWZ5O3RleHQtanVzdGlmeTppbnRlci1pZGVvZ3JhcGgiPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LHNhbnMtc2VyaWYiPkhpLCBUb2VybGVzcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0idGV4dC1hbGlnbjpqdXN0aWZ5O3RleHQtanVz
dGlmeTppbnRlci1pZGVvZ3JhcGgiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXpl
OjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZuYnNw
OzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJ0ZXh0
LWFsaWduOmp1c3RpZnk7dGV4dC1qdXN0aWZ5OmludGVyLWlkZW9ncmFwaCI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZiI+SSBhbSB3b3JraW5nIG9uIHRoZSBjaGFydGVyIHRleHQuIEl0IGlz
IG5vdCBkaWZmaWN1bHQgdG8gY2F0ZWdldGllZCB0aGUgd29yayBpdGVtcyBpbnRvIDQgY2xhc3Nl
czogQU5JJiM0MzssDQogQVNBLCBCUlNLSSwgVXNlIGNhc2VzLiBJIGFtIGludGVuZGluZyB0byBw
dXQgTk9DcyBpbnRvIEFOSSYjNDM7LiBJIHdpbGwgc2VuZCB5b3UgYSByZXdvcmQgdmVyc2lvbiBv
biBuZXh0IE1vbmRheS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0idGV4dC1hbGlnbjpqdXN0aWZ5O3RleHQtanVzdGlmeTppbnRlci1pZGVvZ3JhcGgi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJ0ZXh0LWFsaWduOmp1c3RpZnk7dGV4dC1q
dXN0aWZ5OmludGVyLWlkZW9ncmFwaCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+Rm9y
IG1pbGVzdG9uZXMsIGdpdmluZyB0aGF0IHdlIGhhdmUgYSBsb25nIGRvY3VtZW50IHdhaXRpbmcg
bGlzdCBhcyBsb25nIGFzIDIwLiBJdCB3b3VsZCBub3Qgc3VmZmljaWVudA0KIHRvIHNhdGlzZnkg
ZXZlcnlvbmUgZm9yIGp1c3QgNSBtaWxlc3RvbmVzIGJ5IHNheWluZyBldmVyeW9uZSBzaG91bGQg
aGF2ZSBubyBtb3JlIHRoYW4gb25lIGRvY3VtZW50IHRocm91Z2guIFdlIHdvdWxkIGZhY2UgbW9y
ZSB0aGFuIDEwIGluZGl2aWR1YWxzIGFza2luZyBmb3IgYWRvcHRpb24uIEFueXdheSwgaGVyZSBh
cmUgbXkgY2hvaWNlIGZvciB0aGUgZmlyc3QgNTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0idGV4dC1hbGlnbjpqdXN0aWZ5O3RleHQtanVzdGlmeTpp
bnRlci1pZGVvZ3JhcGgiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZuYnNwOzxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJ0ZXh0LWFsaWdu
Omp1c3RpZnk7dGV4dC1qdXN0aWZ5OmludGVyLWlkZW9ncmFwaCI+PHNwYW4gbGFuZz0iRU4tVVMi
IHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZiI+QVNBIExpZmVjeWNsZSAoTHVjZW50KTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJ0ZXh0LWFsaWduOmp1c3RpZnk7dGV4dC1qdXN0
aWZ5OmludGVyLWlkZW9ncmFwaCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+QVNBIGd1
aWRlbGluZSAoQnJpYW4gQyk8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0idGV4dC1hbGlnbjpqdXN0aWZ5O3RleHQtanVzdGlmeTppbnRlci1pZGVvZ3Jh
cGgiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPkdSQVNQIERpc3RyaWJ1dGlvbiAoQmlu
ZyBMaXUpPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
InRleHQtYWxpZ246anVzdGlmeTt0ZXh0LWp1c3RpZnk6aW50ZXItaWRlb2dyYXBoIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmIj5Db25zdHJhaW5lZCBKb2luIFByb3h5IGZvciBCb290c3Ry
YXBwaW5nIFByb3RvY29scyAoTWljaGFlbCBSLik8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0idGV4dC1hbGlnbjpqdXN0aWZ5O3RleHQtanVzdGlmeTpp
bnRlci1pZGVvZ3JhcGgiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiYjNDM7IE9uZSBC
UlNLSSBkb2N1bWVudDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJ0ZXh0LWFsaWduOmp1c3RpZnk7dGV4dC1qdXN0aWZ5OmludGVyLWlkZW9ncmFwaCI+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9InRleHQtYWxpZ246anVzdGlmeTt0ZXh0LWp1
c3RpZnk6aW50ZXItaWRlb2dyYXBoIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5UaGlz
IHdvdWxkIGxvb2tzIGdvb2Qgd2hlbiB3ZSBmYWNlIElFU0cuIFRoZW4sIHdlIG1heSBhYmxlIHRv
IGFkb3B0IDIgb3IgMyBtb3JlIGRvY3VtZW50IG91dCBvZiB3cml0dGVuDQogbWlsZXN0b25lcywg
SSBndWVzcy4gQnV0IGl0IHdvdWxkIGxvb2tzIGJhZCBpZiB3ZSBoYXZlIG1vcmUgdGhhbiAxMCBX
RyBkb2N1bWVudCBwYXJhbGxlbC4gUFM6IHdlIHN0aWxsIGhhdmUgNyBXRyBkb2N1bWVudHMgc2hv
d2luZyBub3csIHRob3VnaCAzIG9mIHRoZW0gcGFzc2VkIElFU0cgcmV2aWV3IGFuZCB3YWl0aW5n
IGJ5IE1JU1JFRiDigJMgQUNQITxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJ0ZXh0LWFsaWduOmp1c3RpZnk7dGV4dC1qdXN0aWZ5OmludGVyLWlkZW9n
cmFwaCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+Jm5ic3A7PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9InRleHQtYWxpZ246anVzdGlmeTt0
ZXh0LWp1c3RpZnk6aW50ZXItaWRlb2dyYXBoIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
Ij5DaGVlcnMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9InRleHQtYWxpZ246anVzdGlmeTt0ZXh0LWp1c3RpZnk6aW50ZXItaWRlb2dyYXBoIj48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0idGV4dC1hbGlnbjpqdXN0aWZ5O3RleHQtanVzdGlm
eTppbnRlci1pZGVvZ3JhcGgiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPlNoZW5nPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQpBbmlt
YSBtYWlsaW5nIGxpc3Q8YnI+DQo8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxhIGhyZWY9Im1h
aWx0bzpBbmltYUBpZXRmLm9yZyI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZl
dGljYSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiM5NTRGNzIiPkFuaW1hQGlldGYub3JnPC9zcGFu
PjwvYT48L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtI
ZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+PGJyPg0KPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVT
Ij48YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2FuaW1hIj48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6Izk1NEY3MiI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9hbmlt
YTwvc3Bhbj48L2E+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+
DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_5D36713D8A4E7348A7E10DF7437A4B929038CF2ANKGEML515MBXchi_--


From nobody Sat Mar 16 00:34:10 2019
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 C0495130E94 for <anima@ietfa.amsl.com>; Sat, 16 Mar 2019 00:34:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, 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 HoNehjQWUFB2 for <anima@ietfa.amsl.com>; Sat, 16 Mar 2019 00:34:06 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76D2412D7F8 for <anima@ietf.org>; Sat, 16 Mar 2019 00:34:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9104; q=dns/txt; s=iport; t=1552721645; x=1553931245; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=EcYv+R3lCYP29vVtz7x9R3ilwlgY3LhJgzgB6a2qiZE=; b=iUTJHr4B5D9G8dMKF6g3brCnJNqJWVkwthb7nn5l05yf/Td4LDAk1WUF 82mjHZXDEVs/gdXRXhyWfvecIEkvso0qDhNsVcRrmz/wXCma2ti/KcVBR vBixOHVfnT+s4TET7R51KnYjSAthe0QZrXu+a9kbdDaQCgbIX3J1cOaI+ o=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AUAAAHpoxc/xbLJq1kGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBVAIBAQEBCwGBDViBYjMnhAuIe4xQkjuHcQgDAQGEbAKEcjc?= =?us-ascii?q?GDQEBAwEBCQEDAm0ohUoBAQEDASNWBQsLGCoCAlcGE4MiAYFtCKsIgS+FRoR?= =?us-ascii?q?eD4EvAYFIigGBf4ERJx+CHi6EWoMxMYImA4oyhx2SfgmEYYZ7h0gZiw2IR5s?= =?us-ascii?q?NgnACBAYFAhWBXSKBVjMaCBsVOyoBgkE+gm8BAo0cPgMwjCOCTQEB?=
X-IronPort-AV: E=Sophos;i="5.58,485,1544486400";  d="asc'?scan'208,217";a="10718700"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 16 Mar 2019 07:34:03 +0000
Received: from [10.61.249.212] ([10.61.249.212]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x2G7Y11a025817 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 16 Mar 2019 07:34:02 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <8E246F43-EAAC-4D4B-B441-DE07D9ED8DA4@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_9AF57F1D-93B0-4EEC-8502-0ED26C48E267"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Sat, 16 Mar 2019 08:34:00 +0100
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B929038CF2A@NKGEML515-MBX.china.huawei.com>
Cc: Toerless Eckert <tte@cs.fau.de>, Toerless Eckert <toerless.eckert@huawei.com>, "anima@ietf.org" <anima@ietf.org>
To: Sheng Jiang <jiangsheng@huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B929038B9FA@NKGEML515-MBX.china.huawei.com> <20E1F3B4-EE2F-4BFA-B9EB-7EE576BF9547@cisco.com> <5D36713D8A4E7348A7E10DF7437A4B929038CF2A@NKGEML515-MBX.china.huawei.com>
X-Mailer: Apple Mail (2.3445.102.3)
X-Outbound-SMTP-Client: 10.61.249.212, [10.61.249.212]
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/tZAEP0lwsfc8NuMHFNePxuG3IVU>
Subject: Re: [Anima] Potential Milestones for ANIMA new charter
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 16 Mar 2019 07:34:08 -0000

--Apple-Mail=_9AF57F1D-93B0-4EEC-8502-0ED26C48E267
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_84F8F722-9F8A-4B47-A299-D1CE6499BA49"


--Apple-Mail=_84F8F722-9F8A-4B47-A299-D1CE6499BA49
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Sheng,

> On 16 Mar 2019, at 01:56, Sheng Jiang <jiangsheng@huawei.com> wrote:
>=20
> Hi, Eliot,
>=20
> As you know, the charter text is different from the milestones. In =
charter text, we will have a paragraph to describe the BRSKI relevant =
works. In principle, all BRSKI works, even those have not been =
mentioned, would be covered. So, BRSKI works, no matter they are listed =
as milestones or not, are in WG scope.

Thanks.  That=E2=80=99s what I was aiming at.  Are you looking for some =
proposed text?


>=20
> Milestones are these work items that WG MUST deliver in a limited =
time, say a year or one and half years. So, as WG chairs, we would like =
to have a shorter list for each period, for which every work item has =
enough energy to complete in time. This is also IESG would like to see. =
We could easily add milestones later when the WG had shown enough =
interests and energy for new in-scope works.
>=20
> =E2=80=9C+ One BRSKI document=E2=80=9D means newly adopt one more =
BRSKI document. The reason that we do not want too many new BRSKI =
document immediately is that the WG need energy to guarantee the current =
adopted BRSKI works, including the main BRSKI document and constrained =
voucher, to be completed as soon as possible with high quality.
>=20

I think we=E2=80=99re coming close to needing a bit of a work plan for =
just the BRSKI documents alone.  That is- it=E2=80=99s not just how many =
documents but which ones, in order to accomplish which functions.  At =
this point, I am presuming that the base document is just about done.  =
The constrained-voucher doc looks like it needs to get pushed over the =
finish line.  And then, it seems to me our chartering discussion might =
do well to focus down a bit on what is needed for different operating =
environments, so as to help sort overlap in drafts with an understanding =
of who wants to commit what code.

Eliot

--Apple-Mail=_84F8F722-9F8A-4B47-A299-D1CE6499BA49
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Sheng,<br class=3D""><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">On 16 Mar 2019, at 01:56, Sheng Jiang &lt;<a =
href=3D"mailto:jiangsheng@huawei.com" =
class=3D"">jiangsheng@huawei.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: =E5=AE=8B=E4=BD=93;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125);" class=3D"">Hi, Eliot,<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: =E5=AE=8B=E4=BD=93;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125);" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0cm 0cm =
0.0001pt; font-size: 12pt; font-family: =E5=AE=8B=E4=BD=93;" =
class=3D""><span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125);" class=3D"">As you know, =
the charter text is different from the milestones. In charter text, we =
will have a paragraph to describe the BRSKI relevant works. In =
principle, all BRSKI works, even those have not been mentioned, would be =
covered. So, BRSKI works, no matter they are listed as milestones or =
not, are in WG scope.</span></div></div></div></blockquote><div><br =
class=3D""></div>Thanks. &nbsp;That=E2=80=99s what I was aiming at. =
&nbsp;Are you looking for some proposed text?</div><div><br =
class=3D""></div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"WordSection1" style=3D"page: =
WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; =
font-family: =E5=AE=8B=E4=BD=93;" class=3D""><span lang=3D"EN-US" =
style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125);" class=3D""><o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: =
=E5=AE=8B=E4=BD=93;" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
10.5pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: =E5=AE=8B=E4=BD=93;" =
class=3D""><span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125);" class=3D"">Milestones are =
these work items that WG MUST deliver in a limited time, say a year or =
one and half years. So, as WG chairs, we would like to have a shorter =
list for each period, for which every work item has enough energy to =
complete in time. This is also IESG would like to see. We could easily =
add milestones later when the WG had shown enough interests and energy =
for new in-scope works.<o:p class=3D""></o:p></span></div><div =
style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: =
=E5=AE=8B=E4=BD=93;" class=3D""><span lang=3D"EN-US" style=3D"font-size: =
10.5pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" =
class=3D""><o:p class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: =
0cm 0cm 0.0001pt; font-size: 12pt; font-family: =E5=AE=8B=E4=BD=93;" =
class=3D""><span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125);" class=3D"">=E2=80=9C+ One =
BRSKI document=E2=80=9D means newly adopt one more BRSKI document. The =
reason that we do not want too many new BRSKI document immediately is =
that the WG need energy to guarantee the current adopted BRSKI works, =
including the main BRSKI document and constrained voucher, to be =
completed as soon as possible with high quality.<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0cm 0cm 0.0001pt; =
font-size: 12pt; font-family: =E5=AE=8B=E4=BD=93;" class=3D""><span =
lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125);" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div></div></div></blockquote><br =
class=3D""></div><div>I think we=E2=80=99re coming close to needing a =
bit of a work plan for just the BRSKI documents alone. &nbsp;That is- =
it=E2=80=99s not just how many documents but which ones, in order to =
accomplish which functions. &nbsp;At this point, I am presuming that the =
base document is just about done. &nbsp;The constrained-voucher doc =
looks like it needs to get pushed over the finish line. &nbsp;And then, =
it seems to me our chartering discussion might do well to focus down a =
bit on what is needed for different operating environments, so as to =
help sort overlap in drafts with an understanding of who wants to commit =
what code.</div><div><br class=3D""></div><div>Eliot</div></body></html>=

--Apple-Mail=_84F8F722-9F8A-4B47-A299-D1CE6499BA49--

--Apple-Mail=_9AF57F1D-93B0-4EEC-8502-0ED26C48E267
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQEzBAEBCAAdFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAlyMpugACgkQh7ZrRtnS
ejOZPggA0Sb2DmJQJGc/bUJGbdF1YJAMjX59xIzQBf43jT9BqXrzWRf3DXLkcdBG
SzU+OedPD54bFUiKC7sypZM99VyuTEdXtaP+73zM5C8v6pMf3u1vDsehKMwHtN0V
2oKgesM/1ZE+uLi0LriYBDkh38YK9LYC0hjW0PbNFKAZlrlztak4mC/DMSqdeHuE
UWHiQICXHCrbR1HdYCPRSS/nV3C/l4xrXl19sLx0IWNdeWzLXhZFaKXl8nITKhJU
f7QPVNe6V/2sDK+Y6EUvT8fwOP2mOzMtKKCjR4r/fvc0GFFWy9p5sqSuWFrWAgBd
vK0lNUy2u4HJpkP6iv1U3mCmACkmng==
=goHp
-----END PGP SIGNATURE-----

--Apple-Mail=_9AF57F1D-93B0-4EEC-8502-0ED26C48E267--


From nobody Sat Mar 16 14:04:13 2019
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 89957127962 for <anima@ietfa.amsl.com>; Sat, 16 Mar 2019 14:04:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 bdK9bTdas5YN for <anima@ietfa.amsl.com>; Sat, 16 Mar 2019 14:04:08 -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 60DDB1275F3 for <anima@ietf.org>; Sat, 16 Mar 2019 14:04:08 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 63B3D3826B; Sat, 16 Mar 2019 17:03:44 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 91020B9A; Sat, 16 Mar 2019 17:04:06 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 8E8FB989; Sat, 16 Mar 2019 17:04:06 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Eliot Lear <lear@cisco.com>
cc: Sheng Jiang <jiangsheng@huawei.com>, Toerless Eckert <tte@cs.fau.de>, Toerless Eckert <toerless.eckert@huawei.com>, "anima\@ietf.org" <anima@ietf.org>
In-Reply-To: <8E246F43-EAAC-4D4B-B441-DE07D9ED8DA4@cisco.com>
References: <5D36713D8A4E7348A7E10DF7437A4B929038B9FA@NKGEML515-MBX.china.huawei.com> <20E1F3B4-EE2F-4BFA-B9EB-7EE576BF9547@cisco.com> <5D36713D8A4E7348A7E10DF7437A4B929038CF2A@NKGEML515-MBX.china.huawei.com> <8E246F43-EAAC-4D4B-B441-DE07D9ED8DA4@cisco.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; 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: Sat, 16 Mar 2019 17:04:06 -0400
Message-ID: <8786.1552770246@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/vRPRAfux0G4CpWoxNSSpxGRBu7E>
Subject: Re: [Anima] Potential Milestones for ANIMA new charter
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 16 Mar 2019 21:04:10 -0000

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


Eliot Lear <lear@cisco.com> wrote:
    > I think we=E2=80=99re coming close to needing a bit of a work plan fo=
r just the BRSKI
    > documents alone. That is- it=E2=80=99s not just how many documents bu=
t which ones, in
    > order to accomplish which functions. At this point, I am presuming th=
at the
    > base document is just about done.

Yes, In theory it's back in the ADs' hands to put in the IESG queue.
I hope that the three reviews will be enough; but I suspect that there will
be a bunch of mis-understandings from some quarters that will need to get
resolved.

    > The constrained-voucher doc looks like it
    > needs to get pushed over the finish line.

Yes.  The EST-COAPS part is done, the voucher part is done.
There are some hangups with references in CORE (SID stuff) that is going to
MISSREF badly once we get into the RFC editor queue.

    > And then, it seems to me our
    > chartering discussion might do well to focus down a bit on what is ne=
eded for
    > different operating environments, so as to help sort overlap in draft=
s with
    > an understanding of who wants to commit what code.

1) I think we will need to write some contrasting use case documents.
2) We will need some additional real-world experience.

=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-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlyNZMYACgkQgItw+93Q
3WUzYAgAm2TRptG67dMNixl+Ms9FLUo9DGsqY0p18FEK8GFqp8lVFlLKRsoFCZVx
oV0PEC6CiZI3VZWPFTSElIXIdz+X3WibdrXYmedV96YuX93SEGWlrfLFNRmGAuUG
X23MYBnryjg3mLNjZO9Hb9w0D4rvxIuZ1CW+vEaTVHjOhmOPH1YUUycJrb6pkphU
E/iBET2K3N52RvN9gZ3aQgCgHxrDNlgjztg7MI0asRhCO2SV5riAeWTxZBCMzM9u
toqGXuXpp2D9GMfsAE9NEZmR6yxPYHheE3FsYqOyclw12S34rX2xS8H3DPmK3i9S
+Z1XV0cEc8uWDUieTWmp/IHf9hFIUg==
=A5CM
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Mar 17 20:29:26 2019
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 DF40F130EAB; Sun, 17 Mar 2019 20:29:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 LIGfD-JmdT-e; Sun, 17 Mar 2019 20:29:22 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 4AC6F127287; Sun, 17 Mar 2019 20:29:22 -0700 (PDT)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 84256BEB4EDCF8D47B7F; Mon, 18 Mar 2019 03:29:20 +0000 (GMT)
Received: from lhreml705-chm.china.huawei.com (10.201.108.54) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 18 Mar 2019 03:29:19 +0000
Received: from lhreml705-chm.china.huawei.com (10.201.108.54) by lhreml705-chm.china.huawei.com (10.201.108.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Mon, 18 Mar 2019 03:29:20 +0000
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml705-chm.china.huawei.com (10.201.108.54) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1591.10 via Frontend Transport; Mon, 18 Mar 2019 03:29:19 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0415.000; Mon, 18 Mar 2019 11:29:16 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "anima@ietf.org" <anima@ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>, "consultancy@vanderstok.org" <consultancy@vanderstok.org>
CC: "anima-chairs@ietf.org" <anima-chairs@ietf.org>
Thread-Topic: Primary ANIMA Agenda for IETF104
Thread-Index: AdTdObvLNNPGxfONQYycr+YuT3ewhQ==
Date: Mon, 18 Mar 2019 03:29:15 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B929038D395@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_5D36713D8A4E7348A7E10DF7437A4B929038D395NKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/-jbcZcZ215AXALWiTE5rexKB76c>
Subject: [Anima] Primary ANIMA Agenda for IETF104
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 18 Mar 2019 03:29:24 -0000

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

Hi, ANIMA,

The below is the link to our primary ANIMA agenda. It is a subject to be ch=
anged.

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

Please no hesitate to contact the chair for any miss or mistake.

PS, Michael R. & Peter, I am fine to move your WG documents, BRSKI and Cons=
trained Voucher into the BRSKI relevant work sub-session with the same time=
 length. In that way, you may save some time for other relevant discussion =
you want.

Regards,

Sheng


--_000_5D36713D8A4E7348A7E10DF7437A4B929038D395NKGEML515MBXchi_
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:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
	{font-family:SimSun;
	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;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.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">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi, ANIMA,<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The below is the link to our pr=
imary ANIMA agenda. It is a subject to be changed.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">https://datatracker.ietf.org/me=
eting/104/materials/agenda-104-anima<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Please no hesitate to contact t=
he chair for any miss or mistake.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">PS, Michael R. &amp; Peter, I a=
m fine to move your WG documents, BRSKI and Constrained Voucher into the BR=
SKI relevant work sub-session with the same time length. In that way, you m=
ay save some time for other relevant discussion
 you want.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Sheng<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_5D36713D8A4E7348A7E10DF7437A4B929038D395NKGEML515MBXchi_--


From nobody Mon Mar 18 03:20:54 2019
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 4DC92130ECE; Mon, 18 Mar 2019 03:20:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 qMrrdyIf0iZy; Mon, 18 Mar 2019 03:20:50 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 AFAAE130E16; Mon, 18 Mar 2019 03:20:49 -0700 (PDT)
Received: from LHREML710-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 2E860A1D47E9EA019368; Mon, 18 Mar 2019 10:20:47 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by LHREML710-CAH.china.huawei.com (10.201.108.33) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 18 Mar 2019 10:20:46 +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.0415.000; Mon, 18 Mar 2019 18:20:38 +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: Latest draft charter text of ANIMA
Thread-Index: AdTdczFSD7JWU1MpTVyITKi7F85EjQ==
Date: Mon, 18 Mar 2019 10:20:37 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B929038D5EC@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_5D36713D8A4E7348A7E10DF7437A4B929038D5ECNKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/6MudzCkPgnUOJzBdiW9LxD5q8Pw>
Subject: [Anima] Latest draft charter text of ANIMA
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 18 Mar 2019 10:20:53 -0000

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

Hi, Anima,
Please find the latest draft charter text below. Actually, the chairs made =
all the draft writing open for all the time. Versions are shared in ANIMA w=
iki at the first time. You can access from datatracker-anima -> additional =
URLs -> Wiki -> 2019 Rechartering
This current version is a lightweight improvement from 01-03 (accessible fr=
om datatracker-anima -> charter), which is uploaded by our responsible AD I=
gnas in Feb 13th, 2019.
Regards,
Sheng
2.0.5 Draft charter (Sheng)
Proposed 2nd Charter for ANIMA Working Group
The Autonomic Networking Integrated Model and Approach (ANIMA) working grou=
p develops and maintains specifications and documentation for interoperable=
 protocols and procedures for automated network management and control of n=
etworks that are developed, built and operated by professionals.
The vision is a network that configures, heals, optimizes and protects itse=
lf. The strategy is the incremental introduction of components to smoothly =
evolve existing and new networks accordingly.
ANIMA work will rely on the framework described in draft-ietf-anima-referen=
ce-model. Work not related to this framework is welcome for review, but WG =
adoption of such work requires explicit rechartering. The three areas of th=
e framework are (1) the Autonomic Networking Infrastructure (ANI), (2) Auto=
nomic Functions (AF) built from software modules called Autonomic Service A=
gents (ASA) and (3) Intent.
The ANI is specified through prior ANIMA work. It is composed of the Autono=
mic Control Plane (ACP), Bootstrap over Secure Key Infrastructures (BRSKI) =
including Vouchers, and the Generic Autonomic Signaling Protocol (GRASP). A=
NIMA will work on closing gaps and extended ANI and its components.
ANIMA will start to define AFs to enable service automation in networks; it=
 will also work on generic aspects of ASA including design guidelines and l=
ifecycle management including coordination and dependency management.
ANIMA will not work on Intent or machine learning and other AI techniques w=
ithout explicit rechartering.
ANIMA will coordinate with other IETF and IRTF groups. It will rely on NMRG=
 to define the next steps for Intent.
Acceptance of work items by the WG will be scheduled/throttled so that cont=
ributors can target them to enter WG last call after not more than 4 IETF m=
eeting cycles.
Proposed work items include but are not limited to:

  *   Works extending ANI, including variation of ANI deployment (e.g. in v=
irtualization or compounding environment), information and signaling distri=
bution within an AN, ANI OAMP interfaces (Operations, Administration, Manag=
ement, Provisioning), e.g. YANG models, interaction with YANG-based mechani=
sms, defining the domain boundary and membership management of the domain, =
and etc.

  *   Works regarding to generic Autonomic Service Agents, including design=
 and implementer guidelines for ASAs, life cycle management, authorization =
and coordination of ASA, and etc.

  *   BRSKI relevant works, including proxies, enrollment, adaptions over v=
arious network protocols, variations of voucher formats, and etc.

  *   Generic use cases of Autonomic Network and new GRASP extensions/optio=
ns for them, including but not limited to bulk transfer, DNS-SD interworkin=
g, autonomic resource management,autonomic SLA assurance, autonomic multi-t=
enant management, autonomic network measurement, and etc.

  *   Integration with Network Operations Centers (NOCs), including autonom=
ic discovery/connectivity to NOC, YANG-based ANI/ASA management by the NOC =
and reporting and reporting AF from node to NOC.


--_000_5D36713D8A4E7348A7E10DF7437A4B929038D5ECNKGEML515MBXchi_
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:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* 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;}
h2
	{mso-style-priority:9;
	mso-style-link:"\6807\9898 2 Char";
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:18.0pt;
	font-family:SimSun;
	font-weight:bold;}
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
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:SimSun;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.2Char
	{mso-style-name:"\6807\9898 2 Char";
	mso-style-priority:9;
	mso-style-link:"\6807\9898 2";
	font-family:SimSun;
	font-weight:bold;}
.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;}
/* List Definitions */
@list l0
	{mso-list-id:81806235;
	mso-list-template-ids:-1884244946;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1
	{mso-list-id:491332182;
	mso-list-template-ids:-928247546;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2
	{mso-list-id:828133845;
	mso-list-template-ids:748867844;}
@list l2:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l2:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l2:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l2:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l3
	{mso-list-id:1028605437;
	mso-list-template-ids:1496090374;}
@list l3:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l3:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l3:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l3:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l3:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l3:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l3:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l3:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l3:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4
	{mso-list-id:2134782117;
	mso-list-template-ids:-1375673738;}
@list l4:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l4:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l4:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l4:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
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"ZH-CN" link=3D"#0563C1" vlink=3D"#954F72" style=3D"text-justi=
fy-trim:punctuation">
<div class=3D"WordSection1">
<p class=3D"MsoNormal" align=3D"left" style=3D"mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto;text-align:left;background:white">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif;color:black">Hi, Anima,<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto;text-align:left;background:white">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif;color:black">Please find the latest draft charter text below=
. Actually, the chairs made all the draft writing open for all the time. Ve=
rsions are shared in ANIMA wiki at the first time.
 You can access from datatracker-anima -&gt; additional URLs -&gt; Wiki -&g=
t; 2019 Rechartering<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto;text-align:left;background:white">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif;color:black">This current version is a lightweight improveme=
nt from 01-03 (accessible from datatracker-anima -&gt; charter), which is u=
ploaded by our responsible AD Ignas in Feb 13th,
 2019.<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto;text-align:left;background:white">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif;color:black">Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto;text-align:left;background:white">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif;color:black">Sheng<o:p></o:p></span></p>
<div style=3D"mso-element:para-border-div;border:none;border-bottom:solid #=
DDDDDD 1.0pt;padding:0cm 0cm 1.0pt 0cm;background:white">
<p class=3D"MsoNormal" align=3D"left" style=3D"mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto;text-align:left;background:white;border:none;padding=
:0cm">
<b><span lang=3D"EN-US" style=3D"font-size:12.0pt;font-family:&quot;Arial&q=
uot;,sans-serif;color:black;letter-spacing:-.2pt">2.0.5 Draft charter (Shen=
g)<o:p></o:p></span></b></p>
</div>
<p class=3D"MsoNormal" align=3D"left" style=3D"mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto;text-align:left;background:white">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif;color:black">Proposed 2nd Charter for ANIMA Working Group<o:=
p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto;text-align:left;background:white">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif;color:black">The Autonomic Networking Integrated Model and A=
pproach (ANIMA) working group develops and maintains specifications and doc=
umentation for interoperable protocols and procedures
 for automated network management and control of networks that are develope=
d, built and operated by professionals.<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto;text-align:left;background:white">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif;color:black">The vision is a network that configures, heals,=
 optimizes and protects itself. The strategy is the incremental introductio=
n of components to smoothly evolve existing and
 new networks accordingly.<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto;text-align:left;background:white">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif;color:black">ANIMA work will rely on the framework described=
 in draft-ietf-anima-reference-model. Work not related to this framework is=
 welcome for review, but WG adoption of such work
 requires explicit rechartering. The three areas of the framework are (1) t=
he Autonomic Networking Infrastructure (ANI), (2) Autonomic Functions (AF) =
built from software modules called Autonomic Service Agents (ASA) and (3) I=
ntent.<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto;text-align:left;background:white">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif;color:black">The ANI is specified through prior ANIMA work. =
It is composed of the Autonomic Control Plane (ACP), Bootstrap over Secure =
Key Infrastructures (BRSKI) including Vouchers,
 and the Generic Autonomic Signaling Protocol (GRASP). ANIMA will work on c=
losing gaps and extended ANI and its components.<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto;text-align:left;background:white">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif;color:black">ANIMA will start to define AFs to enable servic=
e automation in networks; it will also work on generic aspects of ASA inclu=
ding design guidelines and lifecycle management
 including coordination and dependency management.<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto;text-align:left;background:white">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif;color:black">ANIMA will not work on Intent or machine learni=
ng and other AI techniques without explicit rechartering.<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal" align=3D"left" style=3D"mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto;text-align:left;background:white">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif;color:black">ANIMA will coordinate with other IETF and IRTF =
groups. It will rely on NMRG to define the next steps for Intent.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto;text-align:left;background:white">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif;color:black">Acceptance of work items by the WG will be sche=
duled/throttled so that contributors can target them to enter WG last call =
after not more than 4 IETF meeting cycles.<o:p></o:p></span></p>
<p class=3D"MsoNormal" align=3D"left" style=3D"mso-margin-top-alt:auto;mso-=
margin-bottom-alt:auto;text-align:left;background:white">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif;color:black">Proposed work items include but are not limited=
 to:<o:p></o:p></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:black;mso-margin-top-alt:auto;mso-ma=
rgin-bottom-alt:auto;text-align:left;mso-list:l0 level1 lfo1;background:whi=
te">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif">Works extending ANI, including variation of ANI deployment =
(e.g. in virtualization or compounding environment), information and signal=
ing distribution within an AN, ANI OAMP interfaces
 (Operations, Administration, Management, Provisioning), e.g. YANG models, =
interaction with YANG-based mechanisms, defining the domain boundary and me=
mbership management of the domain, and etc.<o:p></o:p></span></li></ul>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:black;mso-margin-top-alt:auto;mso-ma=
rgin-bottom-alt:auto;text-align:left;mso-list:l4 level1 lfo2;background:whi=
te">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif">Works regarding to generic Autonomic Service Agents, includ=
ing design and implementer guidelines for ASAs, life cycle management, auth=
orization and coordination of ASA, and etc.<o:p></o:p></span></li></ul>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:black;mso-margin-top-alt:auto;mso-ma=
rgin-bottom-alt:auto;text-align:left;mso-list:l3 level1 lfo3;background:whi=
te">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif">BRSKI relevant works, including proxies, enrollment, adapti=
ons over various network protocols, variations of voucher formats, and etc.=
<o:p></o:p></span></li></ul>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:black;mso-margin-top-alt:auto;mso-ma=
rgin-bottom-alt:auto;text-align:left;mso-list:l2 level1 lfo4;background:whi=
te">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif">Generic use cases of Autonomic Network and new GRASP extens=
ions/options for them, including but not limited to bulk transfer, DNS-SD i=
nterworking, autonomic resource management,autonomic
 SLA assurance, autonomic multi-tenant management, autonomic network measur=
ement, and etc.<o:p></o:p></span></li></ul>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"color:black;mso-margin-top-alt:auto;mso-ma=
rgin-bottom-alt:auto;text-align:left;mso-list:l1 level1 lfo5;background:whi=
te">
<span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Verdana&qu=
ot;,sans-serif">Integration with Network Operations Centers (NOCs), includi=
ng autonomic discovery/connectivity to NOC, YANG-based ANI/ASA management b=
y the NOC and reporting and reporting AF from
 node to NOC.<o:p></o:p></span></li></ul>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_5D36713D8A4E7348A7E10DF7437A4B929038D5ECNKGEML515MBXchi_--


From nobody Mon Mar 18 08:23:04 2019
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 7F98012D827 for <anima@ietfa.amsl.com>; Mon, 18 Mar 2019 08:23:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 uK0JKZWPfi9X for <anima@ietfa.amsl.com>; Mon, 18 Mar 2019 08:23:00 -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 27D0A128701 for <anima@ietf.org>; Mon, 18 Mar 2019 08:23:00 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id D202F38263 for <anima@ietf.org>; Mon, 18 Mar 2019 11:22:33 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id A031A22F3; Mon, 18 Mar 2019 11:22:58 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 9DC47440 for <anima@ietf.org>; Mon, 18 Mar 2019 11:22:58 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "anima\@ietf.org" <anima@ietf.org>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B929038D395@NKGEML515-MBX.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B929038D395@NKGEML515-MBX.china.huawei.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; 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, 18 Mar 2019 11:22:58 -0400
Message-ID: <32057.1552922578@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/6Q3h8TxsqQQNem6X4PrbEM_8W7Q>
Subject: Re: [Anima] Primary ANIMA Agenda for IETF104
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 18 Mar 2019 15:23:03 -0000

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


Sheng Jiang <jiangsheng@huawei.com> wrote:
    > The below is the link to our primary ANIMA agenda. It is a subject to be
    > changed.

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

    > Please no hesitate to contact the chair for any miss or mistake.

    > PS, Michael R. & Peter, I am fine to move your WG documents, BRSKI and
    > Constrained Voucher into the BRSKI relevant work sub-session with the
    > same time length. In that way, you may save some time for other
    > relevant discussion you want.

yes, that's a good idea.  I don't need 10 minutes for BRSKI status update.
5 minutes will do.
We can't have a substantive conversation about it in ten minutes anyway.
I'd sure like to see some replies to my email last week (BCC'ed to the
reviewers) about the -19 document.

3.    Potential New Charter Unscrambling - 30 min
14:20 - 14:50, by co-chairs

Perhaps we could subdivide this item into three sub-items so that we can
be sure to get through it?  Could Toerless post his slides sooner?
Is the intent for it to be mostly mic line?

--
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+93Q3WUFAlyPt9IACgkQgItw+93Q
3WWVkwgAlKnVCNUnM+LwFbTuCh5eWC7mbLbd49GWfD1Mwx7M7cPxPgp3mzFjWtKi
sZ38hn3c7cdCJntmSBX7lNGWVTJ9c/8F/+5JJZB+IGlMOD9ivIZGajPaLhYiuyMc
GKtp5XUuQyySBJebYO64nbnNwWIXgd3mr2yuOXW7zfWUk1ZLNSEr8zQqWpUhI/bu
LTWeGi7YN0zM2y4uQfdGP5ccRxc/9ccIDLVm2YjCLeNaVm7qVbs3sy/opcig7dCQ
HcfQE+LqKR3N0ZqgRKYVlp+TSiNd5OTIAlSaUMRQ/0hHYsE617J9WqeUYPeAdBsK
MgfoYp/sSftzDUhiqDwIugtfiUtS+A==
=qFRn
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Mar 18 09:57:19 2019
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 739CE131101 for <anima@ietfa.amsl.com>; Mon, 18 Mar 2019 09:57:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 x0K-OcO8VRhE for <anima@ietfa.amsl.com>; Mon, 18 Mar 2019 09:57:16 -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 0D1A7130E00 for <anima@ietf.org>; Mon, 18 Mar 2019 09:57:16 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 99CC538263; Mon, 18 Mar 2019 12:56:49 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 7AC0B22F3; Mon, 18 Mar 2019 12:57:14 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 78464440; Mon, 18 Mar 2019 12:57:14 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "anima\@ietf.org" <anima@ietf.org>, Ignas Bagdonas <ibagdona@gmail.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B929038D5EC@NKGEML515-MBX.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B929038D5EC@NKGEML515-MBX.china.huawei.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; 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, 18 Mar 2019 12:57:14 -0400
Message-ID: <21884.1552928234@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/pbEvCErQhJeQHOOyiMjeVaJH0O4>
Subject: Re: [Anima] Latest draft charter text of ANIMA
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 18 Mar 2019 16:57:19 -0000

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


Sheng Jiang <jiangsheng@huawei.com> wrote:
    > Please find the latest draft charter text below.. Actually, the chairs
    > made all the draft writing open for all the time. Versions are shared
    > in ANIMA

Thank you for posting this.
Some comments below.

    > 2.0.5 Draft charter (Sheng)

    > Proposed 2nd Charter for ANIMA Working Group

    > The Autonomic Networking Integrated Model and Approach (ANIMA) working
    > group
    > develops and maintains specifications and documentation for interoperable
    > protocols and procedures for automated network management and control of
    > networks that are developed, built and operated by professionals.

    > The vision is a network that configures, heals, optimizes and protects
    > itself. The strategy is the incremental introduction of components to
    > smoothly evolve existing and new networks accordingly.

    > ANIMA work will rely on the framework described in
    > draft-ietf-anima-reference-model. Work not related to this framework is
    > welcome for review, but WG adoption of such work requires explicit
    > rechartering. The three areas of the framework are (1) the Autonomic
    > Networking Infrastructure (ANI), (2) Autonomic Functions (AF) built from
    > software modules called Autonomic Service Agents (ASA) and (3) Intent.


    > The ANI is specified through prior ANIMA work. It is composed of the
    > Autonomic Control Plane (ACP), Bootstrap over Secure Key Infrastructures
    > (BRSKI) including Vouchers, and the Generic Autonomic Signaling Protocol
    > (GRASP). ANIMA will work on closing gaps and extended ANI and its components.

    > ANIMA will start to define AFs to enable service automation in
    > networks; it will also work on generic aspects of ASA including design
    > guidelines and
    > lifecycle management including coordination and dependency management.

I think that this is a good set of goals, and I'd like to see AFs built,
but I'm not seeing them.  I am pleased to have a place in which to extend
BRSKI, but I feel that it's a *distraction* to the goal of getting the AFs
built.  I've said this before, and I'm prepared to be in the rough here.

What I'd ideally like to see is:

1) some place for enrollment work -- including BRSKI.

2) a way to finish and revise the ANI work.   This may need rather some
   kind of lightweight industrial forum to push interoperability testing
   leading to Updates to documents presently in the queue or already
   published.

3) a way to get AFs brought out.  Maybe an IRTF RG, maybe something else.

While not properly the business of the IETF, I don't think that (3)
can get much traction until there is a way to bring up a (virtual) ANI
on a bunch of VMs or cheap equipment in research labs.
Having ANI is like Web 1.0... the real value doesn't come until 2.0.

So one thought is, provided that (1) can be satisfied some other way,
is to suspend (not shutdown) ANIMA rather than recharter it.  I recognize
that such an action might have negative consequences to how various
people are able to participate.

--
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+93Q3WUFAlyPzeoACgkQgItw+93Q
3WXRFQf+LsDMS0ja8UfMKzDkSNEjq4s6p/Cj+w/YMpGJSEALYyKTKfBFV0PW8f31
J90auRae46xs2qwiZX+QhkGcZosCIvifOYB9HegWQdoj4iO+X/lzk57zqXeAG8rT
QCwlSO9J21uySm6qk4WNEZ2qH6rw59oNmVNdrBCtJJrQmx2+TLjJAwupYf2SB8b5
tp19/YSY/Z74KiVv/hu1kZbprodH/3f7ou8mcOAak+sk740mj/PAfSdxkqgyybzh
52zdLul324+DGT9RlEpTkdTJshP+0TjcFbUwFbPqAhAT0Pf8x7b7OR9KJF7u8GDh
FQldGFpSN8c8mLfgUjyqWR6sKljdNw==
=GziL
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Mar 18 18:05:46 2019
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 7643D130E69 for <anima@ietfa.amsl.com>; Mon, 18 Mar 2019 18:05:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 p6aj9xhKJgJ8 for <anima@ietfa.amsl.com>; Mon, 18 Mar 2019 18:05:43 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 C7512124B0C for <anima@ietf.org>; Mon, 18 Mar 2019 18:05:42 -0700 (PDT)
Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id E3FBCE4C0E075E1CB35C for <anima@ietf.org>; Tue, 19 Mar 2019 01:05:40 +0000 (GMT)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 19 Mar 2019 01:05:40 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0415.000; Tue, 19 Mar 2019 09:05:32 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "anima@ietf.org" <anima@ietf.org>, Ignas Bagdonas <ibagdona@gmail.com>
Thread-Topic: [Anima] Latest draft charter text of ANIMA
Thread-Index: AdTdczFSD7JWU1MpTVyITKi7F85Ejf//6sYA//8ArYA=
Date: Tue, 19 Mar 2019 01:05:32 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B929038D8E5@NKGEML515-MBX.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B929038D5EC@NKGEML515-MBX.china.huawei.com> <21884.1552928234@localhost>
In-Reply-To: <21884.1552928234@localhost>
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: 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/uavOJrB9n4_8RXvzTNr2Dq697Lk>
Subject: Re: [Anima] Latest draft charter text of ANIMA
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Mar 2019 01:05:44 -0000

In lines.

Sheng

> -----Original Message-----
> From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Michael Richards=
on
>     > ANIMA will start to define AFs to enable service automation in
>     > networks; it will also work on generic aspects of ASA including des=
ign
>     > guidelines and
>     > lifecycle management including coordination and dependency
> management.
>=20
> I think that this is a good set of goals, and I'd like to see AFs built, =
but I'm not
> seeing them. =20

This is in the scope. Whether the WG participants come up with good AFs, we=
 will see. Actually, we saw some AFs came together with use cases. What we =
are not sure is the balance between specific AFs for narrow usage or generi=
c AFs that can be reused in many scenarios.

> What I'd ideally like to see is:
>=20
> 1) some place for enrollment work -- including BRSKI.

It is already in the proposed work items: BRSKI relevant works, including p=
roxies, "enrollment", adaptions over various network protocols, variations =
of voucher formats, and etc.

> 2) a way to finish and revise the ANI work.   This may need rather some
>    kind of lightweight industrial forum to push interoperability testing
>    leading to Updates to documents presently in the queue or already
>    published.

We believe this is covered. Maybe the word "Works extending ANI" needs be r=
evised? Any suggestion?

> 3) a way to get AFs brought out.  Maybe an IRTF RG, maybe something else.

Generic ASAs that can be reused in multiple scenarios are already in the sc=
ope. We are not sure about the dedicated ASAs. They may come up with specif=
ic use cases. We need to discuss them case by case when we see them. How to=
 arouse people to work on AFs/ASAs is another topic. It is out of the discu=
ssion of WG charter, I believe.

Sheng

> While not properly the business of the IETF, I don't think that (3) can g=
et much
> traction until there is a way to bring up a (virtual) ANI on a bunch of V=
Ms or cheap
> equipment in research labs.
> Having ANI is like Web 1.0... the real value doesn't come until 2.0.
>=20
> So one thought is, provided that (1) can be satisfied some other way, is =
to
> suspend (not shutdown) ANIMA rather than recharter it.  I recognize that =
such
> an action might have negative consequences to how various people are able=
 to
> participate.
>=20
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works  -=
=3D
> IPv6 IoT consulting =3D-
>=20
>=20


From nobody Mon Mar 18 18:12:33 2019
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 DC21D1277D8 for <anima@ietfa.amsl.com>; Mon, 18 Mar 2019 18:12:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 Ao6vdb8itdn5 for <anima@ietfa.amsl.com>; Mon, 18 Mar 2019 18:12:30 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 DEC44124B0C for <anima@ietf.org>; Mon, 18 Mar 2019 18:12:29 -0700 (PDT)
Received: from LHREML714-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id EACBEA95F5B2E6DE6AAC for <anima@ietf.org>; Tue, 19 Mar 2019 01:12:27 +0000 (GMT)
Received: from lhreml703-chm.china.huawei.com (10.201.108.52) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 19 Mar 2019 01:12:27 +0000
Received: from lhreml703-chm.china.huawei.com (10.201.108.52) by lhreml703-chm.china.huawei.com (10.201.108.52) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Tue, 19 Mar 2019 01:12:27 +0000
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml703-chm.china.huawei.com (10.201.108.52) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1591.10 via Frontend Transport; Tue, 19 Mar 2019 01:12:27 +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.0415.000; Tue, 19 Mar 2019 09:12:20 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "anima@ietf.org" <anima@ietf.org>
Thread-Topic: [Anima] Primary ANIMA Agenda for IETF104
Thread-Index: AdTdObvLNNPGxfONQYycr+YuT3ewhQAIa2QAACUf3/A=
Date: Tue, 19 Mar 2019 01:12:20 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B929038D909@NKGEML515-MBX.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B929038D395@NKGEML515-MBX.china.huawei.com> <32057.1552922578@localhost>
In-Reply-To: <32057.1552922578@localhost>
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: 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/E3qiFfWuOoIBUT0BHqBn8eFUmFw>
Subject: Re: [Anima] Primary ANIMA Agenda for IETF104
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Mar 2019 01:12:32 -0000

>     > PS, Michael R. & Peter, I am fine to move your WG documents, BRSKI =
and
>     > Constrained Voucher into the BRSKI relevant work sub-session with t=
he
>     > same time length. In that way, you may save some time for other
>     > relevant discussion you want.
>=20
> yes, that's a good idea.  I don't need 10 minutes for BRSKI status update=
.
> 5 minutes will do.

I will change the order in the draft agenda, but not re-allocate the time l=
ength. You guys are welcome to shorten, not elongate, your own presentation=
. In that way, we can have more time to discuss at the end of sub-session.

> We can't have a substantive conversation about it in ten minutes anyway.
> I'd sure like to see some replies to my email last week (BCC'ed to the
> reviewers) about the -19 document.
>=20
> 3.    Potential New Charter Unscrambling - 30 min
> 14:20 - 14:50, by co-chairs
>=20
> Perhaps we could subdivide this item into three sub-items so that we can =
be sure
> to get through it?  Could Toerless post his slides sooner?
> Is the intent for it to be mostly mic line?

Yes, mic line would be part of it. The WG should have chance to comment. Ho=
wever, giving the proposed charter has been baked for a long while. This ma=
y end up soon. Let's see.

Regards,

Sheng

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


From nobody Mon Mar 18 23:20:09 2019
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 845531310C6 for <anima@ietfa.amsl.com>; Mon, 18 Mar 2019 23:20:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level: 
X-Spam-Status: No, score=-0.499 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, RCVD_IN_SORBS_WEB=1.5, SPF_PASS=-0.001, URIBL_BLOCKED=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 gj0hK7snBOLk for <anima@ietfa.amsl.com>; Mon, 18 Mar 2019 23:20:06 -0700 (PDT)
Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (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 DC0591277CE for <anima@ietf.org>; Mon, 18 Mar 2019 23:20:05 -0700 (PDT)
Received: by mail-pf1-x432.google.com with SMTP id r15so10236659pfn.9 for <anima@ietf.org>; Mon, 18 Mar 2019 23:20:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=lQJ8rdnErUHDZEAmdFfZyOVENEdWVWffFvdaEGfoyLg=; b=kKsAScWqpzs1we9ZJ4G4NtFHLuz2pk8qG5JALA7N5a4ZW4HuRGxbjrZ7dd8djMiyt9 Ighyox3L1bqbJsQM2+4yNzMaMntdY5yDerOoPnSkqw4EOjRCuTrtZMOX8ZgndpkQ10i2 5blwH8H+tkjf0Qa+HgiaDg3J7O9Azitp1UR1CBbEjBypTMDbF4gba0/PUauc/jNnMWR0 oZStg1pk9yyisp0yrmP436zcDAlWSnGTRQ8wOv14a85EXEtkslBdGSyur1BG9cNlZ7Fz MheC9OlkOrQzrlFY5L78t5Hn9sJd8ehiP39EkL0g6dC911Rrw0M4gOCjR97nyxC1wuMF PS1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=lQJ8rdnErUHDZEAmdFfZyOVENEdWVWffFvdaEGfoyLg=; b=sB3mA6wMDf51JJuhyCIf2z6OxQYMgbhPeSfVoXYu1Ur4NpCbZG+J960dnwDCpJkpvc Jb+5NlsY8qXsXPvlFzDy2wCwf5JkFCLy42/qSluimELsfojySPuv9ZjNLtE3hdHWqzk5 92qihgg4sMjYMmZNeCeXh/WK64MUz66ncq+P+2pM1mS7pvvzYWI+ea03NTb5lO4qPDrK VQm0TvaUovV+PEu2QRHuOBjlplIPLY5XZpURGuS8RI6YSbDmWmppmUj6Zk9xmXRh8qU/ 2Qw3AwDhlowoB14tEirSigo6IJe/0y9MYd/BjKiBRhWKjNE0xkSmj9/cyDWT5yBj3Q0l OsHA==
X-Gm-Message-State: APjAAAX+Kj4uoBVA2tudGEJJANDiilhYzUSWm4bgyCfKt/2dbPa6xmP5 aXGkn3WdnpIzvd7qOWwEe8E=
X-Google-Smtp-Source: APXvYqyOLpL+qyZNb0l7hUwPfVUZR/1a0lfhIWYtul+SQyUAh+kxL+QyRxElR6LtgoI9pVXOnZ2jdg==
X-Received: by 2002:a65:614f:: with SMTP id o15mr291543pgv.383.1552976405410;  Mon, 18 Mar 2019 23:20:05 -0700 (PDT)
Received: from [172.27.1.22] ([220.101.53.114]) by smtp.gmail.com with ESMTPSA id d3sm14652234pfc.125.2019.03.18.23.20.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Mar 2019 23:20:04 -0700 (PDT)
To: Sheng Jiang <jiangsheng@huawei.com>, Michael Richardson <mcr+ietf@sandelman.ca>, "anima@ietf.org" <anima@ietf.org>, Ignas Bagdonas <ibagdona@gmail.com>
References: <5D36713D8A4E7348A7E10DF7437A4B929038D5EC@NKGEML515-MBX.china.huawei.com> <21884.1552928234@localhost> <5D36713D8A4E7348A7E10DF7437A4B929038D8E5@NKGEML515-MBX.china.huawei.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <af236e06-727e-ccb8-8eb5-f752a6d87fff@gmail.com>
Date: Tue, 19 Mar 2019 19:20:01 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3
MIME-Version: 1.0
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B929038D8E5@NKGEML515-MBX.china.huawei.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/dVGTaz8dJBSHH0JrAAVro3zz_yg>
Subject: Re: [Anima] Latest draft charter text of ANIMA
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Mar 2019 06:20:07 -0000

Hi,

(FYI a direct link to the draft charter is:
 https://trac.ietf.org/trac/anima/wiki/Recharter2019 )

One in line comment...

On 19-Mar-19 14:05, Sheng Jiang wrote:
> In lines.
> 
> Sheng
> 
>> -----Original Message-----
>> From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Michael Richardson
>>     > ANIMA will start to define AFs to enable service automation in
>>     > networks; it will also work on generic aspects of ASA including design
>>     > guidelines and
>>     > lifecycle management including coordination and dependency
>> management.
>>
>> I think that this is a good set of goals, and I'd like to see AFs built, but I'm not
>> seeing them.  
> 
> This is in the scope. Whether the WG participants come up with good AFs, we will see. Actually, we saw some AFs came together with use cases. What we are not sure is the balance between specific AFs for narrow usage or generic AFs that can be reused in many scenarios.
> 
>> What I'd ideally like to see is:
>>
>> 1) some place for enrollment work -- including BRSKI.
> 
> It is already in the proposed work items: BRSKI relevant works, including proxies, "enrollment", adaptions over various network protocols, variations of voucher formats, and etc.
> 
>> 2) a way to finish and revise the ANI work.   This may need rather some
>>    kind of lightweight industrial forum to push interoperability testing
>>    leading to Updates to documents presently in the queue or already
>>    published.
> 
> We believe this is covered. Maybe the word "Works extending ANI" needs be revised? Any suggestion?
> 
>> 3) a way to get AFs brought out.  Maybe an IRTF RG, maybe something else.
> 
> Generic ASAs that can be reused in multiple scenarios are already in the scope. We are not sure about the dedicated ASAs. They may come up with specific use cases. We need to discuss them case by case when we see them. How to arouse people to work on AFs/ASAs is another topic. It is out of the discussion of WG charter, I believe.

Well, many IETF WGs have attached implementation efforts (QUIC is a current
example). I agree that they are not IETF work officially, but it's often the
same people - working under open source rules, not IETF rules. That needs to
be discussed in a side meeting, perhaps (unfortunately I won't be in Prague,
so I can't help with that).

I will take the liberty of reminding people that there is already one 
open source platform for implementing demonstration ASAs and AFs. I'm a
little surprised there hasn't been more interest in it. It needs a secure
ACP, but nobody has given me one of those yet, so it runs insecure
apart from normal firewall protection.

https://github.com/becarpenter/graspy (start with the README and graspy.pdf)

    Brian

> Sheng
> 
>> While not properly the business of the IETF, I don't think that (3) can get much
>> traction until there is a way to bring up a (virtual) ANI on a bunch of VMs or cheap
>> equipment in research labs.
>> Having ANI is like Web 1.0... the real value doesn't come until 2.0.
>>
>> So one thought is, provided that (1) can be satisfied some other way, is to
>> suspend (not shutdown) ANIMA rather than recharter it.  I recognize that such
>> an action might have negative consequences to how various people are able to
>> participate.
>>
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works  -=
>> IPv6 IoT consulting =-
>>
>>
> 
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima
> 


From nobody Mon Mar 25 08:50:46 2019
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 261341203D6; Mon, 25 Mar 2019 08:50:39 -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.94.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: anima@ietf.org
Message-ID: <155352903908.29069.2113930394305731119@ietfa.amsl.com>
Date: Mon, 25 Mar 2019 08:50:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/cUdhLY4ud7I7vq5HOubiTrTD3RQ>
Subject: [Anima] I-D Action: draft-ietf-anima-constrained-voucher-03.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 25 Mar 2019 15:50:39 -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           : Constrained Voucher Artifacts for Bootstrapping Protocols
        Authors         : Michael Richardson
                          Peter van der Stok
                          Panos Kampanakis
	Filename        : draft-ietf-anima-constrained-voucher-03.txt
	Pages           : 27
	Date            : 2019-03-25

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 [RFC8366], 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.ietf-ace-coap-est] protocol.


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

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-anima-constrained-voucher-03
https://datatracker.ietf.org/doc/html/draft-ietf-anima-constrained-voucher-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-anima-constrained-voucher-03


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 25 08:57:28 2019
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 482E11203EB for <anima@ietfa.amsl.com>; Mon, 25 Mar 2019 08:57:27 -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 uGDV6iCeWcPK for <anima@ietfa.amsl.com>; Mon, 25 Mar 2019 08:57:24 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B70AD1203E3 for <anima@ietf.org>; Mon, 25 Mar 2019 08:57:24 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [IPv6:2607:f0b0:f:68:d5b0:7d49:45f1:6ec]) by relay.sandelman.ca (Postfix) with ESMTPS id 45FEE1F45B for <anima@ietf.org>; Mon, 25 Mar 2019 15:57:22 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id F3ECD1BDB; Mon, 25 Mar 2019 16:57:22 +0100 (CET)
From: Michael Richardson <mcr@sandelman.ca>
To: anima@ietf.org
In-reply-to: <155352903908.29069.2113930394305731119@ietfa.amsl.com>
References: <155352903908.29069.2113930394305731119@ietfa.amsl.com>
Comments: In-reply-to internet-drafts@ietf.org message dated "Mon, 25 Mar 2019 08:50:39 -0700."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <20700.1553529442.1@dooku.sandelman.ca>
Date: Mon, 25 Mar 2019 16:57:22 +0100
Message-ID: <20701.1553529442@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/KPemxCaES7wl0Zn7AP2GYUYqowc>
Subject: Re: [Anima] I-D Action: draft-ietf-anima-constrained-voucher-03.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 25 Mar 2019 15:57:27 -0000

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 : Constrained Voucher Artifacts for Bootstrapping
    > Protocols Authors : Michael Richardson Peter van der Stok Panos
    > Kampanakis Filename : draft-ietf-anima-constrained-voucher-03.txt Pages

I have slightly rushed to post this -03.
The examples are not updated as much as I'd like, and I have three more
issues from Esko to deal with.

However, at the Fairhair BRSKI interop (outside-IETF-)meeting today, we
discovered some significant confusion due to the mistake of swapping the
examples, and so that needed to be fixed sooner.

And the ID had expired.

Chairs, my appologies for not having yet sent slides on this document.

--
]               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 Mon Mar 25 12:33:23 2019
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 0034412003E for <anima@ietfa.amsl.com>; Mon, 25 Mar 2019 12:33:22 -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 scRdX1YtvU8R for <anima@ietfa.amsl.com>; Mon, 25 Mar 2019 12:33:19 -0700 (PDT)
Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) (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 AF19012001B for <anima@ietf.org>; Mon, 25 Mar 2019 12:33:19 -0700 (PDT)
Received: by mail-pl1-x62d.google.com with SMTP id k2so422653plt.3 for <anima@ietf.org>; Mon, 25 Mar 2019 12:33:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:references:to:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=zzheZmvySmIGZiIcYpb8ulhxh9Fy7shDWtbHJHI6nKs=; b=pPf+En6KNjlf62aXYQj7JSjC8yhkOE/fBNJbC0ahBbiie54nXxKm+GzfudGQnpC/Vs YVx2mm8gT1NUTbSGrj7cZo555aMZo3T5rPcfsvu2/Eqo/z7Ap5L3HU0/4HF10ftvW8g5 WxS0JpyEVXzzn6CaXfk04GwVW+iChseO8trS2A70KB2M/q2JHlDe5yuupnW+MZTZFr1q 41oOOxJURd3eR5EsPBAN/gCRdVyxUMgc8f5PdkJMW50p3x7j6b68meDxjp3oXoCActSJ pMlcnOgyZF0L/DbwLGw1ka9JCzpQWYhLfZYmXlmZ+/h+8wdxp/6BU+QHNYoWKabPl+a4 g9OQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:references:to:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=zzheZmvySmIGZiIcYpb8ulhxh9Fy7shDWtbHJHI6nKs=; b=hxvvoKqf6SzCWT0aJGSPuspS2/EaOxcerLDv2xipSPKmV7mFS3IzC6Q7GvL8wOwV0/ M0qxOy6FuVxtUkxBIRm5IoeAZxQg1mtNBPtcFh78D3q6F+ypcZ0Od1TagH+eGOtv0+yO AEpv4RMOXgFvUwCku5eOXaeOZKDuja0ybT5zJO/hgjMaPsGA7/3DpAYsqThq7iNbCSzl 2JrfkQnpDzk9A5IoCAG9jcrg8XdWpWavYV8u3O470I0Scf1uR/M1UTUHPEWyQ7lDETiZ Y9LzX/EwLb6ddIJaaRtdP4dxwBW8Ic6XFOIv03mQ/iR3iVDFIGKy7Lb2mWhrERo1sX5m G+Jg==
X-Gm-Message-State: APjAAAUf8sNHLiYlbf/Rx2kBZXsq0xUhLEzqVbr4yVYN/9IURQnAXzO7 /BlHEZjsQwfi+KfTZUEzbi6GD81L
X-Google-Smtp-Source: APXvYqwjE3pbq4od2u7hjlA6gf5kTOJY8Pa+lmXHnp0BAatot5UTaAk2tfHFrzVHjIsp/CEErY+60A==
X-Received: by 2002:a17:902:8643:: with SMTP id y3mr26663912plt.195.1553542398827;  Mon, 25 Mar 2019 12:33:18 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.72.95]) by smtp.gmail.com with ESMTPSA id b26sm21914962pfi.92.2019.03.25.12.33.16 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 Mar 2019 12:33:17 -0700 (PDT)
References: <155351766967.28964.6517259833650041915.idtracker@ietfa.amsl.com>
To: Anima WG <anima@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
X-Forwarded-Message-Id: <155351766967.28964.6517259833650041915.idtracker@ietfa.amsl.com>
Message-ID: <13112375-6f33-db09-955f-0419ce9dad70@gmail.com>
Date: Tue, 26 Mar 2019 08:33:14 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.0
MIME-Version: 1.0
In-Reply-To: <155351766967.28964.6517259833650041915.idtracker@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/bHjgB4BmjNcOomepBZysrJfLuVA>
Subject: [Anima] Fwd: [Cbor] Protocol Action: 'Concise data definition language (CDDL): a notational convention to express CBOR and JSON data structures' to Proposed Standard (draft-ietf-cbor-cddl-08.txt)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 25 Mar 2019 19:33:22 -0000

Hi,

FYI this announcement is good news for ANIMA. It satisfies one of the
two missing references for the GRASP RFC. The other one is the ACP draft.
(For details see https://www.rfc-editor.org/cluster_info.php?cid=C325)

   Brian

-------- Forwarded Message --------
Subject: [Cbor] Protocol Action: 'Concise data definition language (CDDL): a notational convention to express CBOR and JSON data structures' to Proposed Standard (draft-ietf-cbor-cddl-08.txt)
Date: Mon, 25 Mar 2019 05:41:09 -0700
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
CC: cbor@ietf.org, The IESG <iesg@ietf.org>, alexey.melnikov@isode.com, barryleiba@computer.org, cbor-chairs@ietf.org, draft-ietf-cbor-cddl@ietf.org, rfc-editor@rfc-editor.org

The IESG has approved the following document:
- 'Concise data definition language (CDDL): a notational convention to
   express CBOR and JSON data structures'
  (draft-ietf-cbor-cddl-08.txt) as Proposed Standard

This document is the product of the Concise Binary Object Representation
Maintenance and Extensions Working Group.

The IESG contact persons are Adam Roach, Alexey Melnikov and Ben Campbell.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-cbor-cddl/




Technical Summary

   This document proposes a notational convention to express CBOR data
   structures (RFC 7049).  Its main goal is to provide an easy and
   unambiguous way to express structures for protocol messages and data
   formats that use CBOR or JSON.

Working Group Summary

  The CBOR working group has been working on the CDDL definition for about
  a year, and has had productive, healthy discussion that's led to the
  current document.  There is quite wide deployment of CBOR and a lot of
  interesting in the definition language that's proposed here.  As is
  typical, we had a core set of maybe half a dozen very active
  participants, with quite a few others chiming in occasionally.  The
  document shepherd thinks the interest and contribution has been robust.

  There are no significant disagreements that remain, and there's solid
  working group consensus on what's here now.  There have been
  disagreements about how to represent particular things, but they have
  been cleanly resolved and none are important to note here.  I'll call out
  the latest one, as it's just come up: at the end of working group last
  call, Jim Schaad raised an issue on the mailing list about an ambiguity
  that affects automated parser generation.  After discussion on the
  working group telechat, Carsten proposed text that clarifies that syntax
  alone may not always be sufficient to understand the meaning of a name,
  and that semantics of the name must be understood.

Document Quality

   Multiple existing IETF documents are already using CDDL for specifying wire encodings.
   There are several implementations of CBOR parsers/generators.

Personnel

   Barry Leiba is the document shepherd and
   Alexey Melnikov is the responsible AD.

_______________________________________________
CBOR mailing list
CBOR@ietf.org
https://www.ietf.org/mailman/listinfo/cbor


From nobody Sat Mar 30 12:38:53 2019
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 6CD2312024E for <anima@ietfa.amsl.com>; Sat, 30 Mar 2019 12:38:51 -0700 (PDT)
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 Xm3aln5e-kcq for <anima@ietfa.amsl.com>; Sat, 30 Mar 2019 12:38:49 -0700 (PDT)
Received: from mail-pf1-x42b.google.com (mail-pf1-x42b.google.com [IPv6:2607:f8b0:4864:20::42b]) (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 B08C812025A for <anima@ietf.org>; Sat, 30 Mar 2019 12:38:49 -0700 (PDT)
Received: by mail-pf1-x42b.google.com with SMTP id e24so2582608pfi.12 for <anima@ietf.org>; Sat, 30 Mar 2019 12:38:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:references:to:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=I4ALb1JUnPFqLiY8SsA87oqhi6IZHQC0BnB+3Vl5WXs=; b=Im8/RqQm/rgfbmFHJZGchLOiaZoZ11ETjG8ObGx7m6pKYWlHCz6EvmHSMwRnqZP8Dd wF4e0CEoz/QfQd9Bp9U3/cOxdULX6QbHX6Bi5lWo6XGPISkPxohDVoMdwAX/d+mTWDdH QzWzeNji2CXVYSCV6hIiQMYMAYfDbdpLPiIgk9PansVl0zZxE8igccIEBr6smqA1Gh6d LCi7McY7a8Vw+ruCn4gVra5KoQq2FQdtKwAGXVE7QjNOpBloQ6qAR4WJGMOPVP6W65Z8 cqY5BkXqOKDrrDuxL27GZQnIgimBklJaX7mGoxL87kAobe1abHKvD7vWgofN1U6VIRfs a9rw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:references:to:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=I4ALb1JUnPFqLiY8SsA87oqhi6IZHQC0BnB+3Vl5WXs=; b=kCynxuHOGvShLe6U0ObQcqeOwxpfCUkAfyORxxF3AotDfoUvcbGuq1J8k+4fYuankU 5clfkZyYNFmSDqH9dk3n165N74OSzmal6yVW5H/u1Vgd2LK6cLgmqZDhaIxMKQNjnPHF RhwtMTJTgI7LVouPfej760QhrVMPfD2kQM2zMSJkbaZOclHAtqzmRitoigf5LmtAwUWq ghp4u3lgugYIguyJnH63cab3SItrwnnO4qiHzy5IOfAPiPMQlnoMgvsW36bW8cp72wfT 4k+0i8MWVRD5ydjWkJAHst2TNP8u34kLlmXPu8LtH3J5HGvRAl4ECY5UukwdcjkmQHn+ kJLg==
X-Gm-Message-State: APjAAAWiY417t1l3lsMNIZyYN6nGw2pE5jj9dDc/btav99SOlOKaz1YU qjC28s582Tlw46mZWxz7YjO9IqT1
X-Google-Smtp-Source: APXvYqxjegGdRsUZ0zPu0E/nASzYNStVLQfirFYG9GK6gendzK4fHdWtSXRpBP9EZWixK16lZVWYfQ==
X-Received: by 2002:a62:1e06:: with SMTP id e6mr54097961pfe.168.1553974729080;  Sat, 30 Mar 2019 12:38:49 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.72.95]) by smtp.gmail.com with ESMTPSA id f87sm13455001pff.56.2019.03.30.12.38.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 30 Mar 2019 12:38:47 -0700 (PDT)
References: <CAATsVbYKgrXSoz1jJ7f9W6-wi-iajo3ktYEQJXrqMrRi=tVhiA@mail.gmail.com>
To: Anima WG <anima@ietf.org>
Cc: Warren Kumari <warren@kumari.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Forwarded-Message-Id: <CAATsVbYKgrXSoz1jJ7f9W6-wi-iajo3ktYEQJXrqMrRi=tVhiA@mail.gmail.com>
Message-ID: <b6b43bdc-07e8-df67-7c7a-2e1bda3e5781@gmail.com>
Date: Sun, 31 Mar 2019 08:38:46 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <CAATsVbYKgrXSoz1jJ7f9W6-wi-iajo3ktYEQJXrqMrRi=tVhiA@mail.gmail.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/MJL9QrLR9T4da-GeIPo8NkMyZbM>
Subject: [Anima] Fwd: Re: [OPSAWG] "Secure Device Install" - draft-wkumari-opsawg-sdi
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
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, 30 Mar 2019 19:38:51 -0000

It seems to me that BRSKI folk might have some comments on https://tools.=
ietf.org/html/draft-wkumari-opsawg-sdi

   Brian

-------- Forwarded Message --------
Subject: 	Re: [OPSAWG] "Secure Device Install" - draft-wkumari-opsawg-sdi=

Date: 	Sat, 30 Mar 2019 10:16:18 +0100
From: 	Bill Fenner <fenner@fenron.com>
To: 	Warren Kumari <warren@kumari.net>
CC: 	OPSAWG <opsawg@ietf.org>



Hi Warren,

The idea is interesting.=C2=A0 I definitely like the idea of having a lig=
htweight mechanism for this - certainly customers have been asking for "s=
ecure no touch provisioning", whatever that means.=C2=A0 I'd like to thro=
w out a couple of things for discussion:

1. Vendors (speaking as one) don't necessarily want it to be easy to find=
 out what serial numbers we've built.=C2=A0 You may say "well change your=
 serial number allocation", but, we have a whole logistics team that has =
way more input to that.=C2=A0 Also see=C2=A0https://en.wikipedia.org/wiki=
/German_tank_problem <https://en.wikipedia..org/wiki/German_tank_problem>=
 .

2. If we create an identifier divorced from the serial number (e.g., a UU=
ID) to avoid problem 1, we still need to provide that identifier to the c=
ustomer somehow. The serial number is nice because it's written on the de=
vice, so you can tell which one you've got when you have a stack of 150 t=
hat you just received.=C2=A0 Perhaps there can be a service provided by t=
he vendor that performs the dynamic mapping, but then that service is vul=
nerable to the dictionary attack to discover serial numbers (or needs to =
have countermeasures).

3. The vendor is now responsible for maintaining the public key until the=
 user needs it.=C2=A0 Sure, storage is cheap, sure, I can back it up on G=
oogle Cloud, but that's still a new burden on the vendor (no matter how l=
ight weight it sounds).

=C2=A0 Bill


