
From nobody Wed Jul  1 13:56:09 2020
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 182E43A0D70; Wed,  1 Jul 2020 13:56:03 -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: 7.6.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: anima@ietf.org
Message-ID: <159363696301.1694.14970467680230111407@ietfa.amsl.com>
Date: Wed, 01 Jul 2020 13:56:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/_Fy-5VWRzazFUGh9Cf2vRPWYrnk>
Subject: [Anima] I-D Action: draft-ietf-anima-autonomic-control-plane-26.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: Wed, 01 Jul 2020 20:56:03 -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-26.txt
	Pages           : 162
	Date            : 2020-07-01

Abstract:
   Autonomic functions need a control plane to communicate, which
   depends on some addressing and routing.  This Autonomic 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-26
https://datatracker.ietf.org/doc/html/draft-ietf-anima-autonomic-control-plane-26

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


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 Wed Jul  1 14:01:04 2020
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 4425E3A0D74; Wed,  1 Jul 2020 14:01:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.153
X-Spam-Level: 
X-Spam-Status: No, score=-0.153 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, 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 E9c9gfuWS6Pp; Wed,  1 Jul 2020 14:00:50 -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 AB1963A0CA9; Wed,  1 Jul 2020 14:00:17 -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 282C9548068; Wed,  1 Jul 2020 23:00:11 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 22215440043; Wed,  1 Jul 2020 23:00:11 +0200 (CEST)
Date: Wed, 1 Jul 2020 23:00:11 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Russ Housley <housley@vigilsec.com>
Cc: draft-ietf-anima-autonomic-control-plane.ad@ietf.org, anima@ietf.org, Ben Kaduk <kaduk@mit.edu>, Eric Vyncke <evyncke@cisco.com>, rwilton@cisco.com, barryleiba@computer.org
Message-ID: <20200701210011.GV13952@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C71BDB46-A15A-48EC-BC4D-68CA9A7C1DFB@vigilsec.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/kZ7DJ_m6x0nNSleJ-6CbkrovU8c>
Subject: Re: [Anima] Russ/Ben: Re: Russ Housley's review of draft-ietf-autonomic-control-plane-25
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, 01 Jul 2020 21:01:04 -0000

Thanks Russ

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

Hope this closes all open issues with you and Ben.

Details below.

Cheers
    Toerless

On Wed, Jun 24, 2020 at 02:17:08PM -0400, Russ Housley wrote:
> Toerless:
> 
> > On Fri, Mar 20, 2020 at 05:12:52PM -0400, Russ Housley wrote:
> >> 
> >> The document defines Enrollment:
> >> 
> >>   Enrollment:  The process where a node presents identification (for
> >>      example through keying material such as the private key of an
> >>      IDevID) to a network and acquires a network specific identity such
> >>      as an LDevID and trust anchors such as Certificate Authority (CA)
> >>      certificates.
> >> 
> >> First, an annoyance.  CA = Certification Authority (not Certificate Authority).  This applies to an earlier definition and many other places as well.
> > 
> > [fun excourse]
> > 
> > In my defense, i grew up in a town with a dialect:
> > 
> > google: site:cisco.com "certificate   authority" -> 59,700
> > google: site:cisco.com "certification authority" ->  8,580
> > 
> > Also: 
> > 
> > https://en.wikipedia.org/wiki/Certificate_authority
> > 
> > grep -il "ertification authorit" rfc*.txt    | wc -> 272 (#RFCs)
> > grep -il "ertificate authorit" rfc*.txt      | wc -> 136 (#RFCs)
> > 
> > grep -il "ertification authorit" rfc8???.txt | wc -> 38 (#RFCs)
> > grep -il "ertificate authorit" rfc8???.txt   | wc -> 13 (#RFCs)
> > 
> > ratio is getting better for your side... a bit.
> > 
> > Does RFC editor have a negative list of wrong words ?
> > RFC editor abbreviation lists only the correct term.
> > 
> > [/fun excourse]
> > 
> > Fixed.
> 
> Thank you.  Many people get it wrong, but X.509 and RFC 5280 (as well as the earlier versions in RFC 2459 and RFC 3280) all use "certification authority".

That should tell you something about how many people read the actual
normative references.

> >> IDevID and LDevID are certificates.  In this context, enrollment should be using an IDevID for authentication in order to get a LDevID.
> > 
> > That was the intention of the text.
> > 
> > Pls. check fixed text for CA, Enrollment, root CA, and TA, i hope they are better now.
> 
> CA: It says "A CA uses its own certificate to sign the certificates it issues."
> 
> This is not correct.  The CA signs with the private key, and the relying party used the public key in the CA certificate to check the signature.

Hopefully ficed with thi:

A CA uses its private key to sign the certificates it issues, relying parties use the public key in the CA certificate to validate the signature.

> Enrollment: I think it would help the reader to say "IDevID certificate" and "LDevID certificate"

I could never figure out authoritatively if IDevID/LDevID are equivalent to a certificate or,
as i think is the case with TA/CA the entity holding the certificate. Given how i think
you are suggesting the later meaning, i have changed not only the enrollment text but
all the text to say LDevID/IDevID certificate to be consistent. Hope that is right.

> Root CA: I do not understand the purpose of "()" in the old text or the new text.

Limitation of XML creating useful links. There is a note to RFC editor at beginning of section 2
to fix this in final text. Haven't fond another draft ever tried to have links between
these hanging style definitions, but one oy ACP reviewers asked for such links.

> TA: Please point to RFC 5280, Section 6.1.1, item (d).  It says:
> 
> """
>       (d)  trust anchor information, describing a CA that serves as a
>            trust anchor for the certification path.  The trust anchor
>            information includes:
> 
>          (1)  the trusted issuer name,
> 
>          (2)  the trusted public key algorithm,
> 
>          (3)  the trusted public key, and
> 
>          (4)  optionally, the trusted public key parameters associated
>               with the public key.
> 
>       The trust anchor information may be provided to the path
>       processing procedure in the form of a self-signed certificate.
>       When the trust anchor information is provided in the form of a
>       certificate, the name in the subject field is used as the trusted
>       issuer name and the contents of the subjectPublicKeyInfo field is
>       used as the source of the trusted public key algorithm and the
>       trusted public key.  The trust anchor information is trusted
>       because it was delivered to the path processing procedure by some
>       trustworthy out-of-band procedure.  If the trusted public key
>       algorithm requires parameters, then the parameters are provided
>       along with the trusted public key.
> """

Fixed to:

<t hangText="TA:" anchor="ta-def">"Trust Anchor". A Trust Anchor is an entity that is trusted for the purpose of certificate validation. Trust Anchor Information such as self-signed certificate(s) of the Trust Anchor is configured into the ACP node as part of Enrollment. See <xref target="RFC5280"/>, Section 6.1.1.

> > I apologize, but this is a bit of a riddle to me because i could not find text that looks like a definition of "trust anchor" in rfc5280 and your concern above also does not explain exactly how the ACP text does not comply with such an "definition".
> > 
> > Are you taking offense in conflating trust anchor and trust anchor information ?
> > That seems to be a common issue in other documents, eg. in 5280:
> > 
> > "When the trust anchor is provided in the form of a self-signed certificate"
> > 
> > "When trust anchor information" ?
> > 
> > In any case, in lack of a better pointe to an RFC, the ACP text now uses the X.509 text to define trust anchor and i tried to go through the text and distinguish between TA and TA information as good as i could.
> > 
> > If there are still concern about this point, i would appreciate if you could be more specific as to what exactly is still wrong and provide suggested text fixes.
> 
> I made a suggestion above.  Certification path validation depends on the TA name, public key algorithm, and public key, and it may also depend on parameters associated with the algorithm.

If the current text is not ok. please explicitly suggest replacement text.

> >> Section 6.1:
> >> 
> >> - The text uses the word "trust" in a vague way.  It should say what they are trusted to do, and what they are trusted to not do.
> >> 
> >> - The test says:
> >> 
> >>   An ACP node MUST
> >>   have a Local Device IDentity certificate (LDevID) and a Trust Anchor
> >>   (TA) consisting of a certificate (chain) used to sign the LDevID of
> >>   all ACP domain members.
> >> 
> >> This does not seem accurate to me in several ways.  Most importantly, a TA is not c certifications path or chain.
> > 
> > Fixed to: To trust another ACP member node with access to the ACP Domain, each ACP member requires
> > keying material: An ACP node MUST have a Local Device IDentity certificate (LDevID),
> > henceforth called the ACP Domain Certificate and information about one or more Trust Anchor (TA)
> > as required for the ACP domain membership check (<xref target="certcheck"/>)
> > 
> > { Please suggest better text if this is still not good enough}.
> 
> Why not point to Section 6 of RFC 5280 for validation of the LDevID to the configured trust anchor?

Hah!, because Bens hitting me over the head with the word "trust" is the better fix and o must have overlooked this instance.

To /trust/ -> authenticate and authorize another ACP member node with...

Aka: the text isn't only about trust. And rule 2 of the certcheck is then the one pointing to 5820 section 6.

> >> Section 6.1.1:
> >> 
> >> - s/X.509/X.509v3/
> > 
> > fixed.
> 
> Thank you.
> 
> > 
> >> - What does "All elements are [RFC5280] compliant??? mean?
> > 
> > removed.
> > 
> > It was just meant to be unnecessary duplicaction of initial sentence from same section:
> > "ACP domain certificates MUST be [RFC5280] compliant X.509v3 certificates"
> 
> Okay.
> 
> > 
> >> - MUST do both RSA and ECC? I think this is too simplistic.  I do not expect devices to have both kinds of private key, but they need to handle both kinds of public key.  This seems to be where the transition paragraph is going, but it is not very clear.
> > 
> > Changed:
> > 
> > "ACP nodes MUST support RSA and Elliptic Curve (ECC) public keys in ACP certificates"
> > 
> > to
> > 
> > "ACP nodes MUST support handling ACP certificates with RSA public keys and ACP certificates with Elliptic Curve (ECC) public keys"
> > 
> > Hope i was guessing right what you are aluding to, if now, then explicit text suggestions are always welcome.
> 
> Section 6.1.1 looks okay to me.
> 
> > 
> >> - I do not understand the wording about ECC curves that MUST be supported.  Normally I see a single curve that MUST be supported for interoperability and and others that SHOULD be supported.  The "or better" wording is really unclear.  Also, each of the curves has a specific key length associated with it.
> > 
> > In the ACP we have any-to-any connectivity and hence any-any mutual cert authentication, so i felt it to be prudent to support some good range of cert key sizes to ensure interoperability across a wide range of equipment within a single ACP - but also exclude key sizes that we feel are unnecessarily weak, such as RSA with less than 2048 bits.
> > 
> > I changed the two paragraphs now to the following three:
> > 
> > ---
> > <t>ACP nodes MUST support handling ACP certificates, TA certificates and certificate chain certificates (henceforth just called certificates in this section) with RSA public keys and certificates with Elliptic Curve (ECC) public keys. Certificates with ECC keys MUST indicate to be Elliptic Curve Diffie-Hellman capable (ECDH) if X.509 v3 keyUsage and extendedKeyUsage are included in the certificate.</t>
> > 
> > <t>ACP nodes MUST NOT support certificates with RSA public keys of less than 2048 bits. They MUST support certificates with RSA public keys with 2048 bits and SHOULD support longer RSA keys. ACP nodes MUST support certificates with ECC public keys using NIST P-256, P-384 and P-521 curves.</t>
> > 
> > <t>ACP nodes MUST support SHA-256, SHA-384, SHA-512 signatures for certificates with RSA key and the same RSA signatures plus ECDSA signatures for certificates with ECC key.</t>
> > ---
> > 
> > I don't understand whether your note about the key length of the curves is an indication of missing text. When i first reviewed with Ben, i had to enter the curves because thats as specific as necessary AFAIK, but given how the key length is implied, i wouldn't understand why i would need to write those down. I don't remember that i have seen that being done either in other RFCs i read through.
> > 
> > In any case, specific text suggestions always welcome in case this text is not sufficient.
> 
> I was expecting you to make one of the curves MUST and the others SHOULD. Making all three curves MUST is okay with me, but it will increase implementation size.

<t>ACP nodes MUST NOT support certificates with RSA public keys of less than 2048 bit modulus or curves with group order of less than 256 bit. They MUST support certificates with RSA public keys with 2048 bit modulus and MAY support longer RSA keys. They MUST support certificates with ECC public keys using NIST P-256 curves and SHOULD support P-384 and P-521 curves.</t>

Seems like 256 bit curve are somewhat better than 2048 bit modulus and cost in RSA goes up faster,
so this text is reducing RSA requirement even more and therefore hopefully reducing implementation
requirements by making higher ones MAY so as to encourage preferring ECC over RSA when going higher
bit numbres  of security.

> Likewise, I was expecting you to make one of the hash functions MUST and the others SHOULD.

Fixed to:

ACP nodes MUST support SHA-256 and SHOULD support SHA-384, SHA-512 signatures...

> >> - I would really like to see some clarity about digital signature vs. key establishment.  The two are jumbled together is a way that is difficult to figure out.  One way to read it is that digital signature is required, but key establishment is optional.  I am not sure that is the intent.
> > 
> > I may not understand what you mean with "key establishment".
> 
> ECDH is used for key establishment, not digital signature.
> 
> RSA can be used for both key establishment and digital signature if the key usage bits allow.
> 
> > 
> > The first two paragraphs talk about the requirements to handle public key in the certificate
> > including permitted minimum key-length for RSA.  Is that what you call "key establishment" ?
> > 
> > The third paragraph talks about requirements against the signatures in the certificates.
> > 
> > The idea is to have the necessary and sufficient text for all ACP nodes to be
> > able to authenticte each other wrt. to their certificate.
> 
> My comment was about the ECDH sentence.

Ok, i hope i am interpreting what i hear from you correctly: I moved the
ECDH sentence after all the text about digital signature aspects and authentication and beofre
the "any other fields". Hope this structures it better. 

> >> - The TLS reference should point to TLS 1.3 (not TLS 1.2).
> > 
> > The MTI for the ACP is TLS 1.2, TLS 1.3 is SHOULD because of the need for
> > lowest common denominator in more embedded device space moving very slowly
> > from TLS 1.2 to TLS 1.3.  See e.g.: 6.8.2. Also note that TLS profile
> > for ACP is quite close to TLS 1.3 wrt. crypto requirements.
> 
> The please be specific:  ... TLS 1.2 [RFC5246].

Done.

> >> Section 6.1.2:
> >> 
> >> - Using rfc822name seems wrong to me.  Assigning another name type seems preferable, even if it has the same syntax.  The semantics are different.  This is the approach used in RFC 4556 for the Kerberos Principal Name.
> > 
> > Can you point me to any specifc RFC text that actually prohibits what we want to do ?
> > 
> > I was reading through the RFCs (forgot number now) that i think defined the
> > encodings, and i could not find anything that would prohibit to use the existing
> > rfc822name for a name that is a valid rfc822name.
> > 
> > It would also be good if you review and address the bullet points 2.1 ... 2.6 and
> > 3.1 ... 3.5 in section 6.1.2. These points explain and justify the choice
> > of rfc822name.
> > 
> > For example, points 2.1 , 2.4 and 2.5 would be closest in addressing your semantic concern.
> 
> I firmly believe that this use of rfc822name is harmful.  Please do not do it.

Thanks a lot for having the discussion on the phone, that helped a lot to speed
up the conclusion.  And thanks a lot to Barry to also swing by. I am budging over your
combined opposition. Lets hope i have the time to bring the discuss back to the
IETF after we are done with ACP, because i think there is a fundamental
evolution of email addresses we should consider better. I do agree that what
you and Barry represented is a very traditional and "ecossystem-safe" interpretation,
 and i am sorry that i really did not get to understand that point through the email thread
discussions up to this week.

So, as discussed offline, all the changes for otherName rfc822Name -> otherName / AcpNodeName
are now in this revision, all the 822Name benefit etc text (including public CA verification
of ACP rfc822Name via ACME SMIME) are now removed (*sob* *sob* ;-).

>From our offline discussion, i changed the name to AcpNodeName after Michael Richardson
said we should not make the name itself more extensible because we could always get additional
otherName OIDs when we have aditional Names to support (thanks, Michael).

I didn't include the idea to use URN because i think we can always define 
in an add-on-document that backend systems could always map the otherName / AcpNodeName
to e.g.: "urn:ietf:params:acp:node:<AcpNodeName>" if they primarily want
to manage names that have URIs. The only reason why we would have wanted to
discuss URN in this doc would be as an alternative in the certificate itself,
and i think not enough people have thought about this alternative, so it
would come with less past experience.

> >> - The document claims that "subjectAlName / otherName" will not be able to be supported because it uses a field that is not mandatory.  I do not think that this is a very big deal.  The otherName definition is:
> >> 
> >>   OtherName ::= SEQUENCE {
> >>        type-id    OBJECT IDENTIFIER,
> >>        value      [0] EXPLICIT ANY DEFINED BY type-id }
> > 
> >> So, the "extra" processing is parse past the type and length for the SEQUENCE, perform an exact match to the constant value of the object identifier, parse past the type and length of the value.  For example, when using the python ASN.1 library for the certificate processing, the additional code is tiny.  After this, the parsing of the string is exactly the same.  In fact, it might be possible to define a format that is even easier to parse if it did not have to look like an email address.  Since this "extra" is so small, I think we should not use rfc822name in this context.
> > 
> > This is addressed in for example point 3.2 in 6.1.2. The ASN.1 libraries available in 
> > embedded systems do not necessarily provide the ability to be extended. They may
> > often come from embedded system OS vendors or third parties.
> > 
> > Also see points 2.2 and 2.3 of 6.1.2: There is a whole backend and diagnostic infrastructure that needs to be extended when introducing new types to decode the new field. This is highly undesirable for easy operationalization.
> 
> I believe that otherName would be better here.  You have made the syntax align with rfc822name, but the semantics are aligned.
[semantics are _not_ aligned... ?]

water under the bridge.

> >> Section 6.1.3:
> >> 
> >> - validity period checking (in step 1) is part of path validation (in step 3).
> > 
> > Sigh... hope i fixed all the references to the rule numbers in the document
> > after eliminating this step 1 and mentioning how it is included in what is
> > now step 2.
> 
> Within Item 3:
> 
> s/CDP/CRLDP/ or /CRL Distribution Point (CRLDP)/
> 
> s/communicate CRL or OCSP check/communicate a CRL or perform an OCSP check/

thanks
replaced all CDP instances with CRLDP exept the ones where it means Cisco Discovery Protocol ;-)
(Hadn't even notices that issue in before, other documents where using CDP abbreviation).

> >> - In step 4, revocation checking allowed to be initially skipped, but the wording is concerning since the check is in a MUST statement.  Then, the checking takes place when communications are established.  I assume some cache is used, otherwise the connection works for a short while, then shuts down, over and over and over.
> > 
> > Hopefully fixed.
> > 
> > Pls. check the reworded text. I conditioned the MUST
> > with a "when availalable" and changed the secondary MUST to lower case as they
> > just explain the mechanism.
> > 
> > Wrt to the up/down issue you mention: It seems cleat that one must periodically
> > re-try a connection to another peer because it could have received a new
> > certificate.
> > 
> > If the connection is torn down at any point in time because of newly learned
> > CRL/OCSP information, it also seems clear the connection needs to be torn down.
> > 
> > I do not understand all possible connection setup protocols, but from
> > what i understand, a negative CRL or OCSP information will not change back
> > to positive in the future, so a connection torn down once because of
> > a particular certificate would need to be retried later up to the
> > point that the signaling gets to the same certificate, at which point in
> > time it would fail. 
> > 
> > Aka: with caching of OCSP/CRL results, the connection would still be probed
> > periodically, but would not be brought up again until there is a new cert.
> > 
> > Is there anything of these explanations you would like to see written
> > down ? Or that are wrong ?
> 
> The previous step allows the CRL check and OCSP check to be skipped if communication is not available.  When the communication is established, is a CRL check or OCSP check performed?  What happens if the check fails?

Prepended explicit text for retrying CRL/OCSP check:

<t>Retries to learn revocation via OCSP/CRL SHOULD be made using the same backoff as described in <xref target="neighbor_verification"/>. If and when the ACP node then learns ...

When check fails, connection to that neighbor is closed even if that means disconnecting one's
self from the network. But re-attempt to connect to support the case that neighbor
gets better certificate in the meantime. That text was already there.

> Of course, I strongly disagree with the use of rfc822name here, but that was not really the point of this comment.

bridge now getting flooded by water under it ;-)

> >> Section 6.1.4:
> >> 
> >> - Please use the terms from RFC 5280.  That is, use "trust anchor" not "root-CA".
> > 
> > a) While trying to do this, it seemed to me as if the word "trust point" that
> > was also used in the text was also redundant. So i hopefully correctly
> > eliminated it and replaced it with TA.
> > 
> > b) Given how rfc7030 in 4.1.3 also refers to Root CA, and equaly
> > the BRSKI draft in several places, and also rfc8572, aka: all the
> > documents that this ACP relates to, i wonder what the rule of thumb is when
> > it is appropriate to use root CA as a term and when not... I don't want
> > to be the first RFC of all the ones that the ACP builds on or relates
> > to that is NOT using the term... without understanding why ACP should be
> > the only one not using it...
> > 
> > There are similarily few occurrances of "root CA" as in those other documents...
> 
> I think your definitions now make it clear that a Root CA is a trust anchor.  That is essentially the approach taken in RFC 7030 as well.

The way i read RFC7030, root CA is just a term you use for a TA
when you want to renew the TA cert/public-key-pair without having to
rely on another TA, e.g. RFC4210 procedures. Whether the TA
only has self-signed certs or whether its certs are also signed
by some even higher level up TA' is irrelevant in this case,
 because for the purpose of the renewal procedure those TA' 
certs are not assumed to be useable, but only mutual signatures between
the different TA certificates of this "root CA" (OldWithOld,
OldWithNew, NewWithOld, and NewWithNew, WhateverWithWhatever).

I hope i got that right. The ACP text uses root CA only as one example
for a TA ("TA is a root CA") in one place, and i changed the definition to this:

<t hangText="root CA:">"root Certification Authority". A <xref target="ca-def" format="title">->"CA"</xref> for which the root CA Key update procedures of <xref target="RFC7030"/>, Section 4.4 can be applied.</xref>.  

Should hopefully make sense given how RFC7030 renewal is mandatory for ACP.

> Russ

Thanks for all the review again, hope we're getting non-asymptotically closer to the finish line here ;-)

Cheers
    Toerless

> > 
> > Just wondering.
> > 
> > Thanks a lot for the review, and apoligies for my delay.
> > 
> > Cheers
> >    Toerless
> >> 
> >> Russ

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


From nobody Wed Jul  1 14:17:52 2020
Return-Path: <housley@vigilsec.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 6F9AE3A0DA6 for <anima@ietfa.amsl.com>; Wed,  1 Jul 2020 14:17:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 NrsTUPASyBx1 for <anima@ietfa.amsl.com>; Wed,  1 Jul 2020 14:17:45 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E775D3A0DAC for <anima@ietf.org>; Wed,  1 Jul 2020 14:17:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 79743300B7E for <anima@ietf.org>; Wed,  1 Jul 2020 17:17:42 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id EjGtnlrPOWfs for <anima@ietf.org>; Wed,  1 Jul 2020 17:17:30 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (pool-72-66-113-56.washdc.fios.verizon.net [72.66.113.56]) by mail.smeinc.net (Postfix) with ESMTPSA id 4CAA4300B3B; Wed,  1 Jul 2020 17:17:30 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20200701210011.GV13952@faui48f.informatik.uni-erlangen.de>
Date: Wed, 1 Jul 2020 17:17:31 -0400
Cc: draft-ietf-anima-autonomic-control-plane.ad@ietf.org, Anima WG <anima@ietf.org>, Ben Kaduk <kaduk@mit.edu>, Eric Vyncke <evyncke@cisco.com>, "Rob Wilton (rwilton)" <rwilton@cisco.com>, Barry Leiba <barryleiba@computer.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4B7F805A-CC80-42FF-8447-EE3C57461BF5@vigilsec.com>
References: <20200701210011.GV13952@faui48f.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3445.104.14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/r59nWsxMKFI968uMpKIgaBXp6Eg>
Subject: Re: [Anima] Russ/Ben: Re: Russ Housley's review of draft-ietf-autonomic-control-plane-25
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, 01 Jul 2020 21:17:50 -0000

Toerless:

Thank you.  I am pleased to see this move in this direction.

Section 6.1.2 should still indicate that the otherName appears in the =
SubjectAltName extension.  In the edits, that seems to have gotten lost.

After providing place holder values for IANA1 and IANA2, I compiled the =
ASN.1 module.  It compiles without errors!

Russ



> On Jul 1, 2020, at 5:00 PM, Toerless Eckert <tte@cs.fau.de> wrote:
>=20
> Thanks Russ
>=20
> =
http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=3Dhttps://tools.ietf=
.org/id/draft-ietf-anima-autonomic-control-plane-25.txt&url2=3Dhttps://too=
ls.ietf.org/id/draft-ietf-anima-autonomic-control-plane-26.txt
>=20
> Hope this closes all open issues with you and Ben.
>=20
> Details below.
>=20
> Cheers
>    Toerless
>=20
> On Wed, Jun 24, 2020 at 02:17:08PM -0400, Russ Housley wrote:
>> Toerless:
>>=20
>>> On Fri, Mar 20, 2020 at 05:12:52PM -0400, Russ Housley wrote:
>>>>=20
>>>> The document defines Enrollment:
>>>>=20
>>>>  Enrollment:  The process where a node presents identification (for
>>>>     example through keying material such as the private key of an
>>>>     IDevID) to a network and acquires a network specific identity =
such
>>>>     as an LDevID and trust anchors such as Certificate Authority =
(CA)
>>>>     certificates.
>>>>=20
>>>> First, an annoyance.  CA =3D Certification Authority (not =
Certificate Authority).  This applies to an earlier definition and many =
other places as well.
>>>=20
>>> [fun excourse]
>>>=20
>>> In my defense, i grew up in a town with a dialect:
>>>=20
>>> google: site:cisco.com "certificate   authority" -> 59,700
>>> google: site:cisco.com "certification authority" ->  8,580
>>>=20
>>> Also:=20
>>>=20
>>> https://en.wikipedia.org/wiki/Certificate_authority
>>>=20
>>> grep -il "ertification authorit" rfc*.txt    | wc -> 272 (#RFCs)
>>> grep -il "ertificate authorit" rfc*.txt      | wc -> 136 (#RFCs)
>>>=20
>>> grep -il "ertification authorit" rfc8???.txt | wc -> 38 (#RFCs)
>>> grep -il "ertificate authorit" rfc8???.txt   | wc -> 13 (#RFCs)
>>>=20
>>> ratio is getting better for your side... a bit.
>>>=20
>>> Does RFC editor have a negative list of wrong words ?
>>> RFC editor abbreviation lists only the correct term.
>>>=20
>>> [/fun excourse]
>>>=20
>>> Fixed.
>>=20
>> Thank you.  Many people get it wrong, but X.509 and RFC 5280 (as well =
as the earlier versions in RFC 2459 and RFC 3280) all use "certification =
authority".
>=20
> That should tell you something about how many people read the actual
> normative references.
>=20
>>>> IDevID and LDevID are certificates.  In this context, enrollment =
should be using an IDevID for authentication in order to get a LDevID.
>>>=20
>>> That was the intention of the text.
>>>=20
>>> Pls. check fixed text for CA, Enrollment, root CA, and TA, i hope =
they are better now.
>>=20
>> CA: It says "A CA uses its own certificate to sign the certificates =
it issues."
>>=20
>> This is not correct.  The CA signs with the private key, and the =
relying party used the public key in the CA certificate to check the =
signature.
>=20
> Hopefully ficed with thi:
>=20
> A CA uses its private key to sign the certificates it issues, relying =
parties use the public key in the CA certificate to validate the =
signature.
>=20
>> Enrollment: I think it would help the reader to say "IDevID =
certificate" and "LDevID certificate"
>=20
> I could never figure out authoritatively if IDevID/LDevID are =
equivalent to a certificate or,
> as i think is the case with TA/CA the entity holding the certificate. =
Given how i think
> you are suggesting the later meaning, i have changed not only the =
enrollment text but
> all the text to say LDevID/IDevID certificate to be consistent. Hope =
that is right.
>=20
>> Root CA: I do not understand the purpose of "()" in the old text or =
the new text.
>=20
> Limitation of XML creating useful links. There is a note to RFC editor =
at beginning of section 2
> to fix this in final text. Haven't fond another draft ever tried to =
have links between
> these hanging style definitions, but one oy ACP reviewers asked for =
such links.
>=20
>> TA: Please point to RFC 5280, Section 6.1.1, item (d).  It says:
>>=20
>> """
>>      (d)  trust anchor information, describing a CA that serves as a
>>           trust anchor for the certification path.  The trust anchor
>>           information includes:
>>=20
>>         (1)  the trusted issuer name,
>>=20
>>         (2)  the trusted public key algorithm,
>>=20
>>         (3)  the trusted public key, and
>>=20
>>         (4)  optionally, the trusted public key parameters associated
>>              with the public key.
>>=20
>>      The trust anchor information may be provided to the path
>>      processing procedure in the form of a self-signed certificate.
>>      When the trust anchor information is provided in the form of a
>>      certificate, the name in the subject field is used as the =
trusted
>>      issuer name and the contents of the subjectPublicKeyInfo field =
is
>>      used as the source of the trusted public key algorithm and the
>>      trusted public key.  The trust anchor information is trusted
>>      because it was delivered to the path processing procedure by =
some
>>      trustworthy out-of-band procedure.  If the trusted public key
>>      algorithm requires parameters, then the parameters are provided
>>      along with the trusted public key.
>> """
>=20
> Fixed to:
>=20
> <t hangText=3D"TA:" anchor=3D"ta-def">"Trust Anchor". A Trust Anchor =
is an entity that is trusted for the purpose of certificate validation. =
Trust Anchor Information such as self-signed certificate(s) of the Trust =
Anchor is configured into the ACP node as part of Enrollment. See <xref =
target=3D"RFC5280"/>, Section 6.1.1.
>=20
>>> I apologize, but this is a bit of a riddle to me because i could not =
find text that looks like a definition of "trust anchor" in rfc5280 and =
your concern above also does not explain exactly how the ACP text does =
not comply with such an "definition".
>>>=20
>>> Are you taking offense in conflating trust anchor and trust anchor =
information ?
>>> That seems to be a common issue in other documents, eg. in 5280:
>>>=20
>>> "When the trust anchor is provided in the form of a self-signed =
certificate"
>>>=20
>>> "When trust anchor information" ?
>>>=20
>>> In any case, in lack of a better pointe to an RFC, the ACP text now =
uses the X.509 text to define trust anchor and i tried to go through the =
text and distinguish between TA and TA information as good as i could.
>>>=20
>>> If there are still concern about this point, i would appreciate if =
you could be more specific as to what exactly is still wrong and provide =
suggested text fixes.
>>=20
>> I made a suggestion above.  Certification path validation depends on =
the TA name, public key algorithm, and public key, and it may also =
depend on parameters associated with the algorithm.
>=20
> If the current text is not ok. please explicitly suggest replacement =
text.
>=20
>>>> Section 6.1:
>>>>=20
>>>> - The text uses the word "trust" in a vague way.  It should say =
what they are trusted to do, and what they are trusted to not do.
>>>>=20
>>>> - The test says:
>>>>=20
>>>>  An ACP node MUST
>>>>  have a Local Device IDentity certificate (LDevID) and a Trust =
Anchor
>>>>  (TA) consisting of a certificate (chain) used to sign the LDevID =
of
>>>>  all ACP domain members.
>>>>=20
>>>> This does not seem accurate to me in several ways.  Most =
importantly, a TA is not c certifications path or chain.
>>>=20
>>> Fixed to: To trust another ACP member node with access to the ACP =
Domain, each ACP member requires
>>> keying material: An ACP node MUST have a Local Device IDentity =
certificate (LDevID),
>>> henceforth called the ACP Domain Certificate and information about =
one or more Trust Anchor (TA)
>>> as required for the ACP domain membership check (<xref =
target=3D"certcheck"/>)
>>>=20
>>> { Please suggest better text if this is still not good enough}.
>>=20
>> Why not point to Section 6 of RFC 5280 for validation of the LDevID =
to the configured trust anchor?
>=20
> Hah!, because Bens hitting me over the head with the word "trust" is =
the better fix and o must have overlooked this instance.
>=20
> To /trust/ -> authenticate and authorize another ACP member node =
with...
>=20
> Aka: the text isn't only about trust. And rule 2 of the certcheck is =
then the one pointing to 5820 section 6.
>=20
>>>> Section 6.1.1:
>>>>=20
>>>> - s/X.509/X.509v3/
>>>=20
>>> fixed.
>>=20
>> Thank you.
>>=20
>>>=20
>>>> - What does "All elements are [RFC5280] compliant??? mean?
>>>=20
>>> removed.
>>>=20
>>> It was just meant to be unnecessary duplicaction of initial sentence =
from same section:
>>> "ACP domain certificates MUST be [RFC5280] compliant X.509v3 =
certificates"
>>=20
>> Okay.
>>=20
>>>=20
>>>> - MUST do both RSA and ECC? I think this is too simplistic.  I do =
not expect devices to have both kinds of private key, but they need to =
handle both kinds of public key.  This seems to be where the transition =
paragraph is going, but it is not very clear.
>>>=20
>>> Changed:
>>>=20
>>> "ACP nodes MUST support RSA and Elliptic Curve (ECC) public keys in =
ACP certificates"
>>>=20
>>> to
>>>=20
>>> "ACP nodes MUST support handling ACP certificates with RSA public =
keys and ACP certificates with Elliptic Curve (ECC) public keys"
>>>=20
>>> Hope i was guessing right what you are aluding to, if now, then =
explicit text suggestions are always welcome.
>>=20
>> Section 6.1.1 looks okay to me.
>>=20
>>>=20
>>>> - I do not understand the wording about ECC curves that MUST be =
supported.  Normally I see a single curve that MUST be supported for =
interoperability and and others that SHOULD be supported.  The "or =
better" wording is really unclear.  Also, each of the curves has a =
specific key length associated with it.
>>>=20
>>> In the ACP we have any-to-any connectivity and hence any-any mutual =
cert authentication, so i felt it to be prudent to support some good =
range of cert key sizes to ensure interoperability across a wide range =
of equipment within a single ACP - but also exclude key sizes that we =
feel are unnecessarily weak, such as RSA with less than 2048 bits.
>>>=20
>>> I changed the two paragraphs now to the following three:
>>>=20
>>> ---
>>> <t>ACP nodes MUST support handling ACP certificates, TA certificates =
and certificate chain certificates (henceforth just called certificates =
in this section) with RSA public keys and certificates with Elliptic =
Curve (ECC) public keys. Certificates with ECC keys MUST indicate to be =
Elliptic Curve Diffie-Hellman capable (ECDH) if X.509 v3 keyUsage and =
extendedKeyUsage are included in the certificate.</t>
>>>=20
>>> <t>ACP nodes MUST NOT support certificates with RSA public keys of =
less than 2048 bits. They MUST support certificates with RSA public keys =
with 2048 bits and SHOULD support longer RSA keys. ACP nodes MUST =
support certificates with ECC public keys using NIST P-256, P-384 and =
P-521 curves.</t>
>>>=20
>>> <t>ACP nodes MUST support SHA-256, SHA-384, SHA-512 signatures for =
certificates with RSA key and the same RSA signatures plus ECDSA =
signatures for certificates with ECC key.</t>
>>> ---
>>>=20
>>> I don't understand whether your note about the key length of the =
curves is an indication of missing text. When i first reviewed with Ben, =
i had to enter the curves because thats as specific as necessary AFAIK, =
but given how the key length is implied, i wouldn't understand why i =
would need to write those down. I don't remember that i have seen that =
being done either in other RFCs i read through.
>>>=20
>>> In any case, specific text suggestions always welcome in case this =
text is not sufficient.
>>=20
>> I was expecting you to make one of the curves MUST and the others =
SHOULD. Making all three curves MUST is okay with me, but it will =
increase implementation size.
>=20
> <t>ACP nodes MUST NOT support certificates with RSA public keys of =
less than 2048 bit modulus or curves with group order of less than 256 =
bit. They MUST support certificates with RSA public keys with 2048 bit =
modulus and MAY support longer RSA keys. They MUST support certificates =
with ECC public keys using NIST P-256 curves and SHOULD support P-384 =
and P-521 curves.</t>
>=20
> Seems like 256 bit curve are somewhat better than 2048 bit modulus and =
cost in RSA goes up faster,
> so this text is reducing RSA requirement even more and therefore =
hopefully reducing implementation
> requirements by making higher ones MAY so as to encourage preferring =
ECC over RSA when going higher
> bit numbres  of security.
>=20
>> Likewise, I was expecting you to make one of the hash functions MUST =
and the others SHOULD.
>=20
> Fixed to:
>=20
> ACP nodes MUST support SHA-256 and SHOULD support SHA-384, SHA-512 =
signatures...
>=20
>>>> - I would really like to see some clarity about digital signature =
vs. key establishment.  The two are jumbled together is a way that is =
difficult to figure out.  One way to read it is that digital signature =
is required, but key establishment is optional.  I am not sure that is =
the intent.
>>>=20
>>> I may not understand what you mean with "key establishment".
>>=20
>> ECDH is used for key establishment, not digital signature.
>>=20
>> RSA can be used for both key establishment and digital signature if =
the key usage bits allow.
>>=20
>>>=20
>>> The first two paragraphs talk about the requirements to handle =
public key in the certificate
>>> including permitted minimum key-length for RSA.  Is that what you =
call "key establishment" ?
>>>=20
>>> The third paragraph talks about requirements against the signatures =
in the certificates.
>>>=20
>>> The idea is to have the necessary and sufficient text for all ACP =
nodes to be
>>> able to authenticte each other wrt. to their certificate.
>>=20
>> My comment was about the ECDH sentence.
>=20
> Ok, i hope i am interpreting what i hear from you correctly: I moved =
the
> ECDH sentence after all the text about digital signature aspects and =
authentication and beofre
> the "any other fields". Hope this structures it better.=20
>=20
>>>> - The TLS reference should point to TLS 1.3 (not TLS 1.2).
>>>=20
>>> The MTI for the ACP is TLS 1.2, TLS 1.3 is SHOULD because of the =
need for
>>> lowest common denominator in more embedded device space moving very =
slowly
>>> from TLS 1.2 to TLS 1.3.  See e.g.: 6.8.2. Also note that TLS =
profile
>>> for ACP is quite close to TLS 1.3 wrt. crypto requirements.
>>=20
>> The please be specific:  ... TLS 1.2 [RFC5246].
>=20
> Done.
>=20
>>>> Section 6.1.2:
>>>>=20
>>>> - Using rfc822name seems wrong to me.  Assigning another name type =
seems preferable, even if it has the same syntax.  The semantics are =
different.  This is the approach used in RFC 4556 for the Kerberos =
Principal Name.
>>>=20
>>> Can you point me to any specifc RFC text that actually prohibits =
what we want to do ?
>>>=20
>>> I was reading through the RFCs (forgot number now) that i think =
defined the
>>> encodings, and i could not find anything that would prohibit to use =
the existing
>>> rfc822name for a name that is a valid rfc822name.
>>>=20
>>> It would also be good if you review and address the bullet points =
2.1 ... 2.6 and
>>> 3.1 ... 3.5 in section 6.1.2. These points explain and justify the =
choice
>>> of rfc822name.
>>>=20
>>> For example, points 2.1 , 2.4 and 2.5 would be closest in addressing =
your semantic concern.
>>=20
>> I firmly believe that this use of rfc822name is harmful.  Please do =
not do it.
>=20
> Thanks a lot for having the discussion on the phone, that helped a lot =
to speed
> up the conclusion.  And thanks a lot to Barry to also swing by. I am =
budging over your
> combined opposition. Lets hope i have the time to bring the discuss =
back to the
> IETF after we are done with ACP, because i think there is a =
fundamental
> evolution of email addresses we should consider better. I do agree =
that what
> you and Barry represented is a very traditional and "ecossystem-safe" =
interpretation,
> and i am sorry that i really did not get to understand that point =
through the email thread
> discussions up to this week.
>=20
> So, as discussed offline, all the changes for otherName rfc822Name -> =
otherName / AcpNodeName
> are now in this revision, all the 822Name benefit etc text (including =
public CA verification
> of ACP rfc822Name via ACME SMIME) are now removed (*sob* *sob* ;-).
>=20
> =46rom our offline discussion, i changed the name to AcpNodeName after =
Michael Richardson
> said we should not make the name itself more extensible because we =
could always get additional
> otherName OIDs when we have aditional Names to support (thanks, =
Michael).
>=20
> I didn't include the idea to use URN because i think we can always =
define=20
> in an add-on-document that backend systems could always map the =
otherName / AcpNodeName
> to e.g.: "urn:ietf:params:acp:node:<AcpNodeName>" if they primarily =
want
> to manage names that have URIs. The only reason why we would have =
wanted to
> discuss URN in this doc would be as an alternative in the certificate =
itself,
> and i think not enough people have thought about this alternative, so =
it
> would come with less past experience.
>=20
>>>> - The document claims that "subjectAlName / otherName" will not be =
able to be supported because it uses a field that is not mandatory.  I =
do not think that this is a very big deal.  The otherName definition is:
>>>>=20
>>>>  OtherName ::=3D SEQUENCE {
>>>>       type-id    OBJECT IDENTIFIER,
>>>>       value      [0] EXPLICIT ANY DEFINED BY type-id }
>>>=20
>>>> So, the "extra" processing is parse past the type and length for =
the SEQUENCE, perform an exact match to the constant value of the object =
identifier, parse past the type and length of the value.  For example, =
when using the python ASN.1 library for the certificate processing, the =
additional code is tiny.  After this, the parsing of the string is =
exactly the same.  In fact, it might be possible to define a format that =
is even easier to parse if it did not have to look like an email =
address.  Since this "extra" is so small, I think we should not use =
rfc822name in this context.
>>>=20
>>> This is addressed in for example point 3.2 in 6.1.2. The ASN.1 =
libraries available in=20
>>> embedded systems do not necessarily provide the ability to be =
extended. They may
>>> often come from embedded system OS vendors or third parties.
>>>=20
>>> Also see points 2.2 and 2.3 of 6.1.2: There is a whole backend and =
diagnostic infrastructure that needs to be extended when introducing new =
types to decode the new field. This is highly undesirable for easy =
operationalization.
>>=20
>> I believe that otherName would be better here.  You have made the =
syntax align with rfc822name, but the semantics are aligned.
> [semantics are _not_ aligned... ?]
>=20
> water under the bridge.
>=20
>>>> Section 6.1.3:
>>>>=20
>>>> - validity period checking (in step 1) is part of path validation =
(in step 3).
>>>=20
>>> Sigh... hope i fixed all the references to the rule numbers in the =
document
>>> after eliminating this step 1 and mentioning how it is included in =
what is
>>> now step 2.
>>=20
>> Within Item 3:
>>=20
>> s/CDP/CRLDP/ or /CRL Distribution Point (CRLDP)/
>>=20
>> s/communicate CRL or OCSP check/communicate a CRL or perform an OCSP =
check/
>=20
> thanks
> replaced all CDP instances with CRLDP exept the ones where it means =
Cisco Discovery Protocol ;-)
> (Hadn't even notices that issue in before, other documents where using =
CDP abbreviation).
>=20
>>>> - In step 4, revocation checking allowed to be initially skipped, =
but the wording is concerning since the check is in a MUST statement.  =
Then, the checking takes place when communications are established.  I =
assume some cache is used, otherwise the connection works for a short =
while, then shuts down, over and over and over.
>>>=20
>>> Hopefully fixed.
>>>=20
>>> Pls. check the reworded text. I conditioned the MUST
>>> with a "when availalable" and changed the secondary MUST to lower =
case as they
>>> just explain the mechanism.
>>>=20
>>> Wrt to the up/down issue you mention: It seems cleat that one must =
periodically
>>> re-try a connection to another peer because it could have received a =
new
>>> certificate.
>>>=20
>>> If the connection is torn down at any point in time because of newly =
learned
>>> CRL/OCSP information, it also seems clear the connection needs to be =
torn down.
>>>=20
>>> I do not understand all possible connection setup protocols, but =
from
>>> what i understand, a negative CRL or OCSP information will not =
change back
>>> to positive in the future, so a connection torn down once because of
>>> a particular certificate would need to be retried later up to the
>>> point that the signaling gets to the same certificate, at which =
point in
>>> time it would fail.=20
>>>=20
>>> Aka: with caching of OCSP/CRL results, the connection would still be =
probed
>>> periodically, but would not be brought up again until there is a new =
cert.
>>>=20
>>> Is there anything of these explanations you would like to see =
written
>>> down ? Or that are wrong ?
>>=20
>> The previous step allows the CRL check and OCSP check to be skipped =
if communication is not available.  When the communication is =
established, is a CRL check or OCSP check performed?  What happens if =
the check fails?
>=20
> Prepended explicit text for retrying CRL/OCSP check:
>=20
> <t>Retries to learn revocation via OCSP/CRL SHOULD be made using the =
same backoff as described in <xref target=3D"neighbor_verification"/>. =
If and when the ACP node then learns ...
>=20
> When check fails, connection to that neighbor is closed even if that =
means disconnecting one's
> self from the network. But re-attempt to connect to support the case =
that neighbor
> gets better certificate in the meantime. That text was already there.
>=20
>> Of course, I strongly disagree with the use of rfc822name here, but =
that was not really the point of this comment.
>=20
> bridge now getting flooded by water under it ;-)
>=20
>>>> Section 6.1.4:
>>>>=20
>>>> - Please use the terms from RFC 5280.  That is, use "trust anchor" =
not "root-CA".
>>>=20
>>> a) While trying to do this, it seemed to me as if the word "trust =
point" that
>>> was also used in the text was also redundant. So i hopefully =
correctly
>>> eliminated it and replaced it with TA.
>>>=20
>>> b) Given how rfc7030 in 4.1.3 also refers to Root CA, and equaly
>>> the BRSKI draft in several places, and also rfc8572, aka: all the
>>> documents that this ACP relates to, i wonder what the rule of thumb =
is when
>>> it is appropriate to use root CA as a term and when not... I don't =
want
>>> to be the first RFC of all the ones that the ACP builds on or =
relates
>>> to that is NOT using the term... without understanding why ACP =
should be
>>> the only one not using it...
>>>=20
>>> There are similarily few occurrances of "root CA" as in those other =
documents...
>>=20
>> I think your definitions now make it clear that a Root CA is a trust =
anchor.  That is essentially the approach taken in RFC 7030 as well.
>=20
> The way i read RFC7030, root CA is just a term you use for a TA
> when you want to renew the TA cert/public-key-pair without having to
> rely on another TA, e.g. RFC4210 procedures. Whether the TA
> only has self-signed certs or whether its certs are also signed
> by some even higher level up TA' is irrelevant in this case,
> because for the purpose of the renewal procedure those TA'=20
> certs are not assumed to be useable, but only mutual signatures =
between
> the different TA certificates of this "root CA" (OldWithOld,
> OldWithNew, NewWithOld, and NewWithNew, WhateverWithWhatever).
>=20
> I hope i got that right. The ACP text uses root CA only as one example
> for a TA ("TA is a root CA") in one place, and i changed the =
definition to this:
>=20
> <t hangText=3D"root CA:">"root Certification Authority". A <xref =
target=3D"ca-def" format=3D"title">->"CA"</xref> for which the root CA =
Key update procedures of <xref target=3D"RFC7030"/>, Section 4.4 can be =
applied.</xref>. =20
>=20
> Should hopefully make sense given how RFC7030 renewal is mandatory for =
ACP.
>=20
>> Russ
>=20
> Thanks for all the review again, hope we're getting non-asymptotically =
closer to the finish line here ;-)
>=20
> Cheers
>    Toerless
>=20
>>>=20
>>> Just wondering.
>>>=20
>>> Thanks a lot for the review, and apoligies for my delay.
>>>=20
>>> Cheers
>>>   Toerless
>>>>=20
>>>> Russ
>=20
> --=20
> ---
> tte@cs.fau.de


From nobody Wed Jul  1 15:13:47 2020
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 6E4CE3A0E61; Wed,  1 Jul 2020 15:13:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.87
X-Spam-Level: 
X-Spam-Status: No, score=-0.87 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, 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 9qPJ8fru1eAE; Wed,  1 Jul 2020 15:13:43 -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 A92763A0E5E; Wed,  1 Jul 2020 15:13:41 -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 6C41E548441; Thu,  2 Jul 2020 00:13:35 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 62D57440043; Thu,  2 Jul 2020 00:13:35 +0200 (CEST)
Date: Thu, 2 Jul 2020 00:13:35 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Russ Housley <housley@vigilsec.com>
Cc: draft-ietf-anima-autonomic-control-plane.ad@ietf.org, Anima WG <anima@ietf.org>, Ben Kaduk <kaduk@mit.edu>, Eric Vyncke <evyncke@cisco.com>, "Rob Wilton (rwilton)" <rwilton@cisco.com>, Barry Leiba <barryleiba@computer.org>
Message-ID: <20200701221335.GA60049@faui48f.informatik.uni-erlangen.de>
References: <20200701210011.GV13952@faui48f.informatik.uni-erlangen.de> <4B7F805A-CC80-42FF-8447-EE3C57461BF5@vigilsec.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B7F805A-CC80-42FF-8447-EE3C57461BF5@vigilsec.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/_-O4Ky6VRxEvG7fTx7Db14gbYMY>
Subject: Re: [Anima] Russ/Ben: Re: Russ Housley's review of draft-ietf-autonomic-control-plane-25
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, 01 Jul 2020 22:13:47 -0000

On Wed, Jul 01, 2020 at 05:17:31PM -0400, Russ Housley wrote:
> Toerless:
> 
> Thank you.  I am pleased to see this move in this direction.
> 
> Section 6.1.2 should still indicate that the otherName appears in the SubjectAltName extension.  In the edits, that seems to have gotten lost.

Ack. Next version. The explanations already say it.

> After providing place holder values for IANA1 and IANA2, I compiled the ASN.1 module.  It compiles without errors!

Great.

Funnily, the internationalized email address otherName RFC8398 was 
the best / newest template ;-)

Cheers
   Toerless
> 
> Russ
> 
> 
> 
> > On Jul 1, 2020, at 5:00 PM, Toerless Eckert <tte@cs.fau.de> wrote:
> > 
> > Thanks Russ
> > 
> > http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://tools.ietf.org/id/draft-ietf-anima-autonomic-control-plane-25.txt&url2=https://tools.ietf.org/id/draft-ietf-anima-autonomic-control-plane-26.txt
> > 
> > Hope this closes all open issues with you and Ben.
> > 
> > Details below.
> > 
> > Cheers
> >    Toerless
> > 
> > On Wed, Jun 24, 2020 at 02:17:08PM -0400, Russ Housley wrote:
> >> Toerless:
> >> 
> >>> On Fri, Mar 20, 2020 at 05:12:52PM -0400, Russ Housley wrote:
> >>>> 
> >>>> The document defines Enrollment:
> >>>> 
> >>>>  Enrollment:  The process where a node presents identification (for
> >>>>     example through keying material such as the private key of an
> >>>>     IDevID) to a network and acquires a network specific identity such
> >>>>     as an LDevID and trust anchors such as Certificate Authority (CA)
> >>>>     certificates.
> >>>> 
> >>>> First, an annoyance.  CA = Certification Authority (not Certificate Authority).  This applies to an earlier definition and many other places as well.
> >>> 
> >>> [fun excourse]
> >>> 
> >>> In my defense, i grew up in a town with a dialect:
> >>> 
> >>> google: site:cisco.com "certificate   authority" -> 59,700
> >>> google: site:cisco.com "certification authority" ->  8,580
> >>> 
> >>> Also: 
> >>> 
> >>> https://en.wikipedia.org/wiki/Certificate_authority
> >>> 
> >>> grep -il "ertification authorit" rfc*.txt    | wc -> 272 (#RFCs)
> >>> grep -il "ertificate authorit" rfc*.txt      | wc -> 136 (#RFCs)
> >>> 
> >>> grep -il "ertification authorit" rfc8???.txt | wc -> 38 (#RFCs)
> >>> grep -il "ertificate authorit" rfc8???.txt   | wc -> 13 (#RFCs)
> >>> 
> >>> ratio is getting better for your side... a bit.
> >>> 
> >>> Does RFC editor have a negative list of wrong words ?
> >>> RFC editor abbreviation lists only the correct term.
> >>> 
> >>> [/fun excourse]
> >>> 
> >>> Fixed.
> >> 
> >> Thank you.  Many people get it wrong, but X.509 and RFC 5280 (as well as the earlier versions in RFC 2459 and RFC 3280) all use "certification authority".
> > 
> > That should tell you something about how many people read the actual
> > normative references.
> > 
> >>>> IDevID and LDevID are certificates.  In this context, enrollment should be using an IDevID for authentication in order to get a LDevID.
> >>> 
> >>> That was the intention of the text.
> >>> 
> >>> Pls. check fixed text for CA, Enrollment, root CA, and TA, i hope they are better now.
> >> 
> >> CA: It says "A CA uses its own certificate to sign the certificates it issues."
> >> 
> >> This is not correct.  The CA signs with the private key, and the relying party used the public key in the CA certificate to check the signature.
> > 
> > Hopefully ficed with thi:
> > 
> > A CA uses its private key to sign the certificates it issues, relying parties use the public key in the CA certificate to validate the signature.
> > 
> >> Enrollment: I think it would help the reader to say "IDevID certificate" and "LDevID certificate"
> > 
> > I could never figure out authoritatively if IDevID/LDevID are equivalent to a certificate or,
> > as i think is the case with TA/CA the entity holding the certificate. Given how i think
> > you are suggesting the later meaning, i have changed not only the enrollment text but
> > all the text to say LDevID/IDevID certificate to be consistent. Hope that is right.
> > 
> >> Root CA: I do not understand the purpose of "()" in the old text or the new text.
> > 
> > Limitation of XML creating useful links. There is a note to RFC editor at beginning of section 2
> > to fix this in final text. Haven't fond another draft ever tried to have links between
> > these hanging style definitions, but one oy ACP reviewers asked for such links.
> > 
> >> TA: Please point to RFC 5280, Section 6.1.1, item (d).  It says:
> >> 
> >> """
> >>      (d)  trust anchor information, describing a CA that serves as a
> >>           trust anchor for the certification path.  The trust anchor
> >>           information includes:
> >> 
> >>         (1)  the trusted issuer name,
> >> 
> >>         (2)  the trusted public key algorithm,
> >> 
> >>         (3)  the trusted public key, and
> >> 
> >>         (4)  optionally, the trusted public key parameters associated
> >>              with the public key.
> >> 
> >>      The trust anchor information may be provided to the path
> >>      processing procedure in the form of a self-signed certificate.
> >>      When the trust anchor information is provided in the form of a
> >>      certificate, the name in the subject field is used as the trusted
> >>      issuer name and the contents of the subjectPublicKeyInfo field is
> >>      used as the source of the trusted public key algorithm and the
> >>      trusted public key.  The trust anchor information is trusted
> >>      because it was delivered to the path processing procedure by some
> >>      trustworthy out-of-band procedure.  If the trusted public key
> >>      algorithm requires parameters, then the parameters are provided
> >>      along with the trusted public key.
> >> """
> > 
> > Fixed to:
> > 
> > <t hangText="TA:" anchor="ta-def">"Trust Anchor". A Trust Anchor is an entity that is trusted for the purpose of certificate validation. Trust Anchor Information such as self-signed certificate(s) of the Trust Anchor is configured into the ACP node as part of Enrollment. See <xref target="RFC5280"/>, Section 6.1.1.
> > 
> >>> I apologize, but this is a bit of a riddle to me because i could not find text that looks like a definition of "trust anchor" in rfc5280 and your concern above also does not explain exactly how the ACP text does not comply with such an "definition".
> >>> 
> >>> Are you taking offense in conflating trust anchor and trust anchor information ?
> >>> That seems to be a common issue in other documents, eg. in 5280:
> >>> 
> >>> "When the trust anchor is provided in the form of a self-signed certificate"
> >>> 
> >>> "When trust anchor information" ?
> >>> 
> >>> In any case, in lack of a better pointe to an RFC, the ACP text now uses the X.509 text to define trust anchor and i tried to go through the text and distinguish between TA and TA information as good as i could.
> >>> 
> >>> If there are still concern about this point, i would appreciate if you could be more specific as to what exactly is still wrong and provide suggested text fixes.
> >> 
> >> I made a suggestion above.  Certification path validation depends on the TA name, public key algorithm, and public key, and it may also depend on parameters associated with the algorithm.
> > 
> > If the current text is not ok. please explicitly suggest replacement text.
> > 
> >>>> Section 6.1:
> >>>> 
> >>>> - The text uses the word "trust" in a vague way.  It should say what they are trusted to do, and what they are trusted to not do.
> >>>> 
> >>>> - The test says:
> >>>> 
> >>>>  An ACP node MUST
> >>>>  have a Local Device IDentity certificate (LDevID) and a Trust Anchor
> >>>>  (TA) consisting of a certificate (chain) used to sign the LDevID of
> >>>>  all ACP domain members.
> >>>> 
> >>>> This does not seem accurate to me in several ways.  Most importantly, a TA is not c certifications path or chain.
> >>> 
> >>> Fixed to: To trust another ACP member node with access to the ACP Domain, each ACP member requires
> >>> keying material: An ACP node MUST have a Local Device IDentity certificate (LDevID),
> >>> henceforth called the ACP Domain Certificate and information about one or more Trust Anchor (TA)
> >>> as required for the ACP domain membership check (<xref target="certcheck"/>)
> >>> 
> >>> { Please suggest better text if this is still not good enough}.
> >> 
> >> Why not point to Section 6 of RFC 5280 for validation of the LDevID to the configured trust anchor?
> > 
> > Hah!, because Bens hitting me over the head with the word "trust" is the better fix and o must have overlooked this instance.
> > 
> > To /trust/ -> authenticate and authorize another ACP member node with...
> > 
> > Aka: the text isn't only about trust. And rule 2 of the certcheck is then the one pointing to 5820 section 6.
> > 
> >>>> Section 6.1.1:
> >>>> 
> >>>> - s/X.509/X.509v3/
> >>> 
> >>> fixed.
> >> 
> >> Thank you.
> >> 
> >>> 
> >>>> - What does "All elements are [RFC5280] compliant??? mean?
> >>> 
> >>> removed.
> >>> 
> >>> It was just meant to be unnecessary duplicaction of initial sentence from same section:
> >>> "ACP domain certificates MUST be [RFC5280] compliant X.509v3 certificates"
> >> 
> >> Okay.
> >> 
> >>> 
> >>>> - MUST do both RSA and ECC? I think this is too simplistic.  I do not expect devices to have both kinds of private key, but they need to handle both kinds of public key.  This seems to be where the transition paragraph is going, but it is not very clear.
> >>> 
> >>> Changed:
> >>> 
> >>> "ACP nodes MUST support RSA and Elliptic Curve (ECC) public keys in ACP certificates"
> >>> 
> >>> to
> >>> 
> >>> "ACP nodes MUST support handling ACP certificates with RSA public keys and ACP certificates with Elliptic Curve (ECC) public keys"
> >>> 
> >>> Hope i was guessing right what you are aluding to, if now, then explicit text suggestions are always welcome.
> >> 
> >> Section 6.1.1 looks okay to me.
> >> 
> >>> 
> >>>> - I do not understand the wording about ECC curves that MUST be supported.  Normally I see a single curve that MUST be supported for interoperability and and others that SHOULD be supported.  The "or better" wording is really unclear.  Also, each of the curves has a specific key length associated with it.
> >>> 
> >>> In the ACP we have any-to-any connectivity and hence any-any mutual cert authentication, so i felt it to be prudent to support some good range of cert key sizes to ensure interoperability across a wide range of equipment within a single ACP - but also exclude key sizes that we feel are unnecessarily weak, such as RSA with less than 2048 bits.
> >>> 
> >>> I changed the two paragraphs now to the following three:
> >>> 
> >>> ---
> >>> <t>ACP nodes MUST support handling ACP certificates, TA certificates and certificate chain certificates (henceforth just called certificates in this section) with RSA public keys and certificates with Elliptic Curve (ECC) public keys. Certificates with ECC keys MUST indicate to be Elliptic Curve Diffie-Hellman capable (ECDH) if X.509 v3 keyUsage and extendedKeyUsage are included in the certificate.</t>
> >>> 
> >>> <t>ACP nodes MUST NOT support certificates with RSA public keys of less than 2048 bits. They MUST support certificates with RSA public keys with 2048 bits and SHOULD support longer RSA keys. ACP nodes MUST support certificates with ECC public keys using NIST P-256, P-384 and P-521 curves.</t>
> >>> 
> >>> <t>ACP nodes MUST support SHA-256, SHA-384, SHA-512 signatures for certificates with RSA key and the same RSA signatures plus ECDSA signatures for certificates with ECC key.</t>
> >>> ---
> >>> 
> >>> I don't understand whether your note about the key length of the curves is an indication of missing text. When i first reviewed with Ben, i had to enter the curves because thats as specific as necessary AFAIK, but given how the key length is implied, i wouldn't understand why i would need to write those down. I don't remember that i have seen that being done either in other RFCs i read through.
> >>> 
> >>> In any case, specific text suggestions always welcome in case this text is not sufficient.
> >> 
> >> I was expecting you to make one of the curves MUST and the others SHOULD. Making all three curves MUST is okay with me, but it will increase implementation size.
> > 
> > <t>ACP nodes MUST NOT support certificates with RSA public keys of less than 2048 bit modulus or curves with group order of less than 256 bit. They MUST support certificates with RSA public keys with 2048 bit modulus and MAY support longer RSA keys. They MUST support certificates with ECC public keys using NIST P-256 curves and SHOULD support P-384 and P-521 curves.</t>
> > 
> > Seems like 256 bit curve are somewhat better than 2048 bit modulus and cost in RSA goes up faster,
> > so this text is reducing RSA requirement even more and therefore hopefully reducing implementation
> > requirements by making higher ones MAY so as to encourage preferring ECC over RSA when going higher
> > bit numbres  of security.
> > 
> >> Likewise, I was expecting you to make one of the hash functions MUST and the others SHOULD.
> > 
> > Fixed to:
> > 
> > ACP nodes MUST support SHA-256 and SHOULD support SHA-384, SHA-512 signatures...
> > 
> >>>> - I would really like to see some clarity about digital signature vs. key establishment.  The two are jumbled together is a way that is difficult to figure out.  One way to read it is that digital signature is required, but key establishment is optional.  I am not sure that is the intent.
> >>> 
> >>> I may not understand what you mean with "key establishment".
> >> 
> >> ECDH is used for key establishment, not digital signature.
> >> 
> >> RSA can be used for both key establishment and digital signature if the key usage bits allow.
> >> 
> >>> 
> >>> The first two paragraphs talk about the requirements to handle public key in the certificate
> >>> including permitted minimum key-length for RSA.  Is that what you call "key establishment" ?
> >>> 
> >>> The third paragraph talks about requirements against the signatures in the certificates.
> >>> 
> >>> The idea is to have the necessary and sufficient text for all ACP nodes to be
> >>> able to authenticte each other wrt. to their certificate.
> >> 
> >> My comment was about the ECDH sentence.
> > 
> > Ok, i hope i am interpreting what i hear from you correctly: I moved the
> > ECDH sentence after all the text about digital signature aspects and authentication and beofre
> > the "any other fields". Hope this structures it better. 
> > 
> >>>> - The TLS reference should point to TLS 1.3 (not TLS 1.2).
> >>> 
> >>> The MTI for the ACP is TLS 1.2, TLS 1.3 is SHOULD because of the need for
> >>> lowest common denominator in more embedded device space moving very slowly
> >>> from TLS 1.2 to TLS 1.3.  See e.g.: 6.8.2. Also note that TLS profile
> >>> for ACP is quite close to TLS 1.3 wrt. crypto requirements.
> >> 
> >> The please be specific:  ... TLS 1.2 [RFC5246].
> > 
> > Done.
> > 
> >>>> Section 6.1.2:
> >>>> 
> >>>> - Using rfc822name seems wrong to me.  Assigning another name type seems preferable, even if it has the same syntax.  The semantics are different.  This is the approach used in RFC 4556 for the Kerberos Principal Name.
> >>> 
> >>> Can you point me to any specifc RFC text that actually prohibits what we want to do ?
> >>> 
> >>> I was reading through the RFCs (forgot number now) that i think defined the
> >>> encodings, and i could not find anything that would prohibit to use the existing
> >>> rfc822name for a name that is a valid rfc822name.
> >>> 
> >>> It would also be good if you review and address the bullet points 2.1 ... 2.6 and
> >>> 3.1 ... 3.5 in section 6.1.2. These points explain and justify the choice
> >>> of rfc822name.
> >>> 
> >>> For example, points 2.1 , 2.4 and 2.5 would be closest in addressing your semantic concern.
> >> 
> >> I firmly believe that this use of rfc822name is harmful.  Please do not do it.
> > 
> > Thanks a lot for having the discussion on the phone, that helped a lot to speed
> > up the conclusion.  And thanks a lot to Barry to also swing by. I am budging over your
> > combined opposition. Lets hope i have the time to bring the discuss back to the
> > IETF after we are done with ACP, because i think there is a fundamental
> > evolution of email addresses we should consider better. I do agree that what
> > you and Barry represented is a very traditional and "ecossystem-safe" interpretation,
> > and i am sorry that i really did not get to understand that point through the email thread
> > discussions up to this week.
> > 
> > So, as discussed offline, all the changes for otherName rfc822Name -> otherName / AcpNodeName
> > are now in this revision, all the 822Name benefit etc text (including public CA verification
> > of ACP rfc822Name via ACME SMIME) are now removed (*sob* *sob* ;-).
> > 
> > From our offline discussion, i changed the name to AcpNodeName after Michael Richardson
> > said we should not make the name itself more extensible because we could always get additional
> > otherName OIDs when we have aditional Names to support (thanks, Michael).
> > 
> > I didn't include the idea to use URN because i think we can always define 
> > in an add-on-document that backend systems could always map the otherName / AcpNodeName
> > to e.g.: "urn:ietf:params:acp:node:<AcpNodeName>" if they primarily want
> > to manage names that have URIs. The only reason why we would have wanted to
> > discuss URN in this doc would be as an alternative in the certificate itself,
> > and i think not enough people have thought about this alternative, so it
> > would come with less past experience.
> > 
> >>>> - The document claims that "subjectAlName / otherName" will not be able to be supported because it uses a field that is not mandatory.  I do not think that this is a very big deal.  The otherName definition is:
> >>>> 
> >>>>  OtherName ::= SEQUENCE {
> >>>>       type-id    OBJECT IDENTIFIER,
> >>>>       value      [0] EXPLICIT ANY DEFINED BY type-id }
> >>> 
> >>>> So, the "extra" processing is parse past the type and length for the SEQUENCE, perform an exact match to the constant value of the object identifier, parse past the type and length of the value.  For example, when using the python ASN.1 library for the certificate processing, the additional code is tiny.  After this, the parsing of the string is exactly the same.  In fact, it might be possible to define a format that is even easier to parse if it did not have to look like an email address.  Since this "extra" is so small, I think we should not use rfc822name in this context.
> >>> 
> >>> This is addressed in for example point 3.2 in 6.1.2. The ASN.1 libraries available in 
> >>> embedded systems do not necessarily provide the ability to be extended. They may
> >>> often come from embedded system OS vendors or third parties.
> >>> 
> >>> Also see points 2.2 and 2.3 of 6.1.2: There is a whole backend and diagnostic infrastructure that needs to be extended when introducing new types to decode the new field. This is highly undesirable for easy operationalization.
> >> 
> >> I believe that otherName would be better here.  You have made the syntax align with rfc822name, but the semantics are aligned.
> > [semantics are _not_ aligned... ?]
> > 
> > water under the bridge.
> > 
> >>>> Section 6.1.3:
> >>>> 
> >>>> - validity period checking (in step 1) is part of path validation (in step 3).
> >>> 
> >>> Sigh... hope i fixed all the references to the rule numbers in the document
> >>> after eliminating this step 1 and mentioning how it is included in what is
> >>> now step 2.
> >> 
> >> Within Item 3:
> >> 
> >> s/CDP/CRLDP/ or /CRL Distribution Point (CRLDP)/
> >> 
> >> s/communicate CRL or OCSP check/communicate a CRL or perform an OCSP check/
> > 
> > thanks
> > replaced all CDP instances with CRLDP exept the ones where it means Cisco Discovery Protocol ;-)
> > (Hadn't even notices that issue in before, other documents where using CDP abbreviation).
> > 
> >>>> - In step 4, revocation checking allowed to be initially skipped, but the wording is concerning since the check is in a MUST statement.  Then, the checking takes place when communications are established.  I assume some cache is used, otherwise the connection works for a short while, then shuts down, over and over and over.
> >>> 
> >>> Hopefully fixed.
> >>> 
> >>> Pls. check the reworded text. I conditioned the MUST
> >>> with a "when availalable" and changed the secondary MUST to lower case as they
> >>> just explain the mechanism.
> >>> 
> >>> Wrt to the up/down issue you mention: It seems cleat that one must periodically
> >>> re-try a connection to another peer because it could have received a new
> >>> certificate.
> >>> 
> >>> If the connection is torn down at any point in time because of newly learned
> >>> CRL/OCSP information, it also seems clear the connection needs to be torn down.
> >>> 
> >>> I do not understand all possible connection setup protocols, but from
> >>> what i understand, a negative CRL or OCSP information will not change back
> >>> to positive in the future, so a connection torn down once because of
> >>> a particular certificate would need to be retried later up to the
> >>> point that the signaling gets to the same certificate, at which point in
> >>> time it would fail. 
> >>> 
> >>> Aka: with caching of OCSP/CRL results, the connection would still be probed
> >>> periodically, but would not be brought up again until there is a new cert.
> >>> 
> >>> Is there anything of these explanations you would like to see written
> >>> down ? Or that are wrong ?
> >> 
> >> The previous step allows the CRL check and OCSP check to be skipped if communication is not available.  When the communication is established, is a CRL check or OCSP check performed?  What happens if the check fails?
> > 
> > Prepended explicit text for retrying CRL/OCSP check:
> > 
> > <t>Retries to learn revocation via OCSP/CRL SHOULD be made using the same backoff as described in <xref target="neighbor_verification"/>. If and when the ACP node then learns ...
> > 
> > When check fails, connection to that neighbor is closed even if that means disconnecting one's
> > self from the network. But re-attempt to connect to support the case that neighbor
> > gets better certificate in the meantime. That text was already there.
> > 
> >> Of course, I strongly disagree with the use of rfc822name here, but that was not really the point of this comment.
> > 
> > bridge now getting flooded by water under it ;-)
> > 
> >>>> Section 6.1.4:
> >>>> 
> >>>> - Please use the terms from RFC 5280.  That is, use "trust anchor" not "root-CA".
> >>> 
> >>> a) While trying to do this, it seemed to me as if the word "trust point" that
> >>> was also used in the text was also redundant. So i hopefully correctly
> >>> eliminated it and replaced it with TA.
> >>> 
> >>> b) Given how rfc7030 in 4.1.3 also refers to Root CA, and equaly
> >>> the BRSKI draft in several places, and also rfc8572, aka: all the
> >>> documents that this ACP relates to, i wonder what the rule of thumb is when
> >>> it is appropriate to use root CA as a term and when not... I don't want
> >>> to be the first RFC of all the ones that the ACP builds on or relates
> >>> to that is NOT using the term... without understanding why ACP should be
> >>> the only one not using it...
> >>> 
> >>> There are similarily few occurrances of "root CA" as in those other documents...
> >> 
> >> I think your definitions now make it clear that a Root CA is a trust anchor.  That is essentially the approach taken in RFC 7030 as well.
> > 
> > The way i read RFC7030, root CA is just a term you use for a TA
> > when you want to renew the TA cert/public-key-pair without having to
> > rely on another TA, e.g. RFC4210 procedures. Whether the TA
> > only has self-signed certs or whether its certs are also signed
> > by some even higher level up TA' is irrelevant in this case,
> > because for the purpose of the renewal procedure those TA' 
> > certs are not assumed to be useable, but only mutual signatures between
> > the different TA certificates of this "root CA" (OldWithOld,
> > OldWithNew, NewWithOld, and NewWithNew, WhateverWithWhatever).
> > 
> > I hope i got that right. The ACP text uses root CA only as one example
> > for a TA ("TA is a root CA") in one place, and i changed the definition to this:
> > 
> > <t hangText="root CA:">"root Certification Authority". A <xref target="ca-def" format="title">->"CA"</xref> for which the root CA Key update procedures of <xref target="RFC7030"/>, Section 4.4 can be applied.</xref>.  
> > 
> > Should hopefully make sense given how RFC7030 renewal is mandatory for ACP.
> > 
> >> Russ
> > 
> > Thanks for all the review again, hope we're getting non-asymptotically closer to the finish line here ;-)
> > 
> > Cheers
> >    Toerless
> > 
> >>> 
> >>> Just wondering.
> >>> 
> >>> Thanks a lot for the review, and apoligies for my delay.
> >>> 
> >>> Cheers
> >>>   Toerless
> >>>> 
> >>>> Russ
> > 
> > -- 
> > ---
> > tte@cs.fau.de

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


From nobody Wed Jul  1 15:47:37 2020
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 3AE9D3A0EDF for <anima@ietfa.amsl.com>; Wed,  1 Jul 2020 15:47:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 NIMIr0-yRJlD for <anima@ietfa.amsl.com>; Wed,  1 Jul 2020 15:47:34 -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 6D06C3A0EDA for <anima@ietf.org>; Wed,  1 Jul 2020 15:47:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 46D93389CE for <anima@ietf.org>; Wed,  1 Jul 2020 18:44:45 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id OBywmfnBzfcs for <anima@ietf.org>; Wed,  1 Jul 2020 18:44:44 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id AD9F5389CD for <anima@ietf.org>; Wed,  1 Jul 2020 18:44:44 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9F3AF62C for <anima@ietf.org>; Wed,  1 Jul 2020 18:47:32 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
In-Reply-To: <159363696301.1694.14970467680230111407@ietfa.amsl.com>
References: <159363696301.1694.14970467680230111407@ietfa.amsl.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512; protocol="application/pgp-signature"
Date: Wed, 01 Jul 2020 18:47:32 -0400
Message-ID: <12080.1593643652@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/18ux7afYlx4bLyck-r9RyNIaRMo>
Subject: [Anima] AcpNodeName -- Re: I-D Action: draft-ietf-anima-autonomic-control-plane-26.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, 01 Jul 2020 22:47:36 -0000

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


As I understand the diff, AcpNodeName seems to be a new extension,
not a SubjectAltName extension, but an extension?

I found it difficult, reading RFC5912 to figure out where id-on was located,
and I had to go into
  https://www.iana.org/assignments/smi-numbers/smi-numbers.xml#smi-numbers-1.3.6.1.5.5.7.0
to see.

Throughout 5912, we have:
  id-pkix  OBJECT IDENTIFIER  ::=
      {iso(1) identified-organization(3) dod(6) internet(1) security(5)
      mechanisms(5) pkix(7)}

while ACP says:

   id-pkix
    FROM PKIX1Explicit-2009
      { iso(1) identified-organization(3) dod(6) internet(1) security(5)
      mechanisms(5) pkix(7) id-mod(0) id-mod-pkix1-explicit-02(51) } ;

and while I understand that these are "local" variables, it does make
figuring stuff out difficult.  May I request that the above link
(smi-numbers.xml ) go into a comment?  maybe that's not often done.

The IANA section is a bit of a clearer pointer, but I sure wish we'd point
people straight at the the place we mean by URL.

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




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

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

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl79EoQACgkQgItw+93Q
3WUcyAf+IwO/ot3l1r04NrejUL/j3r6ozqIL0LasTe5Eu1R+yDudiPZkb1P8z9tr
ub2Wsy8mhdbp2QobiwEWFHeBS9KCi+mn6zXw57awR8a6MvSUbWFns3tNBrbA8L4i
BDy2P34p1PIlnwqWAomPjT73HSsNNRhB/0hVGqgSJFCD0E4RGkH9rROCWX4hMo4n
1qJW/y9VlkbAM2f3TkjWikaIVXJp8IHoAX41JQGGLWf8Z8J90lujTdAYZoAJOZUJ
ZA/7/Yzv9byEmiHNdJ4x4W1soi3GvYUsV3vNQBMoZJjwnLMGgDSAd70jHyAskVYP
r5HcebgkcSEc0KjYd84PpkwcsLkb2A==
=H1+p
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Jul  1 15:58:15 2020
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 BDBB33A0F20 for <anima@ietfa.amsl.com>; Wed,  1 Jul 2020 15:58:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 E6DIjpPTK7oA for <anima@ietfa.amsl.com>; Wed,  1 Jul 2020 15:58:12 -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 325CD3A0F1E for <anima@ietf.org>; Wed,  1 Jul 2020 15:58:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 2A8EC389CE for <anima@ietf.org>; Wed,  1 Jul 2020 18:55:23 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id wingDQdAdlHo for <anima@ietf.org>; Wed,  1 Jul 2020 18:55:22 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 9F29E389CD for <anima@ietf.org>; Wed,  1 Jul 2020 18:55:22 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 927D862C for <anima@ietf.org>; Wed,  1 Jul 2020 18:58:10 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
In-Reply-To: <159363696301.1694.14970467680230111407@ietfa.amsl.com>
References: <159363696301.1694.14970467680230111407@ietfa.amsl.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512; protocol="application/pgp-signature"
Date: Wed, 01 Jul 2020 18:58:10 -0400
Message-ID: <14763.1593644290@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/XxQVaGW-I87IMMHyHAL9E2PbKuY>
Subject: [Anima] use of CRLs in I-D Action: draft-ietf-anima-autonomic-control-plane-26.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, 01 Jul 2020 22:58:14 -0000

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


the diff for 6.1.5.3.  Certificate Revocation Lists (CRLs)
fixes some TLAs, but continues to seem to recommend long-lived certificates with CRLs.
I think that CRLs are not useful, and we should not use them.

6.1.3 is clear that OCSP/CRLs may not be available when connecting!

I think that use of STAR (https://datatracker.ietf.org/doc/rfc8739/ )
Short-Term, Automatically Renewed is the best recommendation!

If we have to do OCSP (via https://datatracker.ietf.org/doc/rfc4806/ )
then we nodes can download their staple and provide it when connecting.
New nodes can get this using the Join Proxy.

Perhaps this needs to be in a new document at this point.

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




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

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

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl79FQIACgkQgItw+93Q
3WUgEwgAlUdSVVo/Fxu1mG6jZhfdIOlhPCbHgL9dpCCQHrccSB+TqQ2F9S3jc4A6
7G40YbF//JB6rGOOpXspEHJf35f8lW8/9J5e47qkPHEChrGPtqMKzWFnMBLwwMXe
qcuugl6mKWuyibjWZCs3UHYHGoLlHVHZ7A+jcuf9xKneYRGvSYGYJaycOCP2WJkf
RHaHQApNxTAXo+VvjBGa6/xLahQuWdRlMvT+HsXxFFkTrpkuppfrXJahzuEnjGIm
TCp52zsFcH4LMS0ovcVdbnRQsUcBcat455RJNS3QT2sJyapmVA0GAxq39MhpF8S9
Y7oEf2QBKfOert1ezyJyfdYDKSC+5w==
=7Cfn
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Jul  1 16:24:29 2020
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 E2D1D3A11C5; Wed,  1 Jul 2020 16:24:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 4g8yVmTIeuJW; Wed,  1 Jul 2020 16:24:27 -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 018183A10D6; Wed,  1 Jul 2020 16:24:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id A42D2389CE; Wed,  1 Jul 2020 19:21:37 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id W_Ls6eBM8aOB; Wed,  1 Jul 2020 19:21:37 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 1579D389CD; Wed,  1 Jul 2020 19:21:37 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 0C91162C; Wed,  1 Jul 2020 19:24:25 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Toerless Eckert <tte@cs.fau.de>, draft-ietf-anima-autonomic-control-plane.ad@ietf.org, Ben Kaduk <kaduk@mit.edu>, Eric Vyncke <evyncke@cisco.com>, Anima WG <anima@ietf.org>
In-Reply-To: <20200701221335.GA60049@faui48f.informatik.uni-erlangen.de>
References: <20200701210011.GV13952@faui48f.informatik.uni-erlangen.de> <4B7F805A-CC80-42FF-8447-EE3C57461BF5@vigilsec.com> <20200701221335.GA60049@faui48f.informatik.uni-erlangen.de>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512; protocol="application/pgp-signature"
Date: Wed, 01 Jul 2020 19:24:25 -0400
Message-ID: <21449.1593645865@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/OOFMT0TQz6fNtWHvQCl1cuNZHNQ>
Subject: Re: [Anima] Russ/Ben: Re: Russ Housley's review of draft-ietf-autonomic-control-plane-25
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, 01 Jul 2020 23:24:29 -0000

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


Toerless Eckert <tte@cs.fau.de> wrote:
    >> After providing place holder values for IANA1 and IANA2, I compiled
    >> the ASN.1 module.  It compiles without errors!

Is it worth asking for early allocation?
I'd like to write code now, and I hate putting my PEN into the code to make
it work.

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




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

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

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl79GygACgkQgItw+93Q
3WWuNgf+M17LSdB4l90XAcdzR89kOAH74wdfbvLTwx6B4zNKfR2DnHwZY7VpJmeG
8yU2qNENfUfDldxQr2L41/un5fcV6Kz/sctAylyG3CJKSmyICETbe1DOkpzPDmST
6lsjRBsBxCbLilGHZD9zSZ/W5LomISDiOOtTh48+rpYaZmuUbgs/sFDzskolZURn
LjFXEHqCa+vOHsSkf8FfXD6J0hS0ekQcAxGDqAhcBocSseNNIjseJqUnOXZiOSYX
uM1P0JEgDrkwNE1d4FVFSwwxQHh4g2ELXUCHvT6B6cESWszWCQ1p88rmWPOeIw3k
8Z9sanYklqprtfFPfwfIIEaHP2Xdfg==
=QpfV
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Jul  1 16:30:05 2020
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 D909D3A120E for <anima@ietfa.amsl.com>; Wed,  1 Jul 2020 16:29:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level: 
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, 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 jnI4Pry3xJ6N for <anima@ietfa.amsl.com>; Wed,  1 Jul 2020 16:29:57 -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 944F73A1202 for <anima@ietf.org>; Wed,  1 Jul 2020 16:29:56 -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 61841548068; Thu,  2 Jul 2020 01:29:51 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 530D2440043; Thu,  2 Jul 2020 01:29:51 +0200 (CEST)
Date: Thu, 2 Jul 2020 01:29:51 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: anima@ietf.org
Message-ID: <20200701232951.GB60049@faui48f.informatik.uni-erlangen.de>
References: <159363696301.1694.14970467680230111407@ietfa.amsl.com> <12080.1593643652@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <12080.1593643652@localhost>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/urdjJO3TNa3PD6_gY1TJLpEJjDQ>
Subject: Re: [Anima] AcpNodeName -- Re: I-D Action: draft-ietf-anima-autonomic-control-plane-26.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, 01 Jul 2020 23:30:03 -0000

On Wed, Jul 01, 2020 at 06:47:32PM -0400, Michael Richardson wrote:
> 
> As I understand the diff, AcpNodeName seems to be a new extension,
> not a SubjectAltName extension, but an extension?

No, i think this is why Russ was adament to have subjectAltName
mentioned. It is just a new otherName and can therefore theoretically
be used everywhere a GeneralName can be used. It MUST be in a
subjectAltName / otherName to name the subject. It _could_ be
in IssuerAltName if for example an ACP node is a subCA etc. pp.

It could be used in IDr / IDi in IPsec too.

> I found it difficult, reading RFC5912 to figure out where id-on was located,
> and I had to go into
>   https://www.iana.org/assignments/smi-numbers/smi-numbers.xml#smi-numbers-1.3.6.1.5.5.7.0
> to see.
> 
> Throughout 5912, we have:
>   id-pkix  OBJECT IDENTIFIER  ::=
>       {iso(1) identified-organization(3) dod(6) internet(1) security(5)
>       mechanisms(5) pkix(7)}
> 
> while ACP says:
> 
>    id-pkix
>     FROM PKIX1Explicit-2009
>       { iso(1) identified-organization(3) dod(6) internet(1) security(5)
>       mechanisms(5) pkix(7) id-mod(0) id-mod-pkix1-explicit-02(51) } ;

i took pretty much the whole ASN.1 block from RFC8398,
given how nobody was jumping forward to suggest writing the ASN.1 code.
This RFC looked like the newest/best template for a new string type otherName.

> and while I understand that these are "local" variables, it does make
> figuring stuff out difficult.  May I request that the above link
> (smi-numbers.xml ) go into a comment?  maybe that's not often done.

Can you pls. suggest explicit text, because i am just winging this ASN.1 stuff
by stealing text from prior RFCs.

> The IANA section is a bit of a clearer pointer, but I sure wish we'd point
> people straight at the the place we mean by URL.

Suggest text, or pull request pls.

I just tried to stay on the safe side, dong what prior RFCs did. Pasting
a Title into Google is typically a better way to find stuff than hoping
URLs don't change, although IANA is prety stable (never try URL with any
vendor WWW server ;-).

Cheers
    Toerless

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


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


From nobody Wed Jul  1 16:41:09 2020
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 570573A11E3 for <anima@ietfa.amsl.com>; Wed,  1 Jul 2020 16:41:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.87
X-Spam-Level: 
X-Spam-Status: No, score=-0.87 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, 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 tl4-2nvoTUMp for <anima@ietfa.amsl.com>; Wed,  1 Jul 2020 16:41:06 -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 1AB7C3A11C9 for <anima@ietf.org>; Wed,  1 Jul 2020 16:41:05 -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 75A16548068; Thu,  2 Jul 2020 01:41:00 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 6D358440043; Thu,  2 Jul 2020 01:41:00 +0200 (CEST)
Date: Thu, 2 Jul 2020 01:41:00 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: anima@ietf.org
Message-ID: <20200701234100.GC60049@faui48f.informatik.uni-erlangen.de>
References: <159363696301.1694.14970467680230111407@ietfa.amsl.com> <14763.1593644290@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <14763.1593644290@localhost>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/XfKpxstbht99JjSFZ117lICTaco>
Subject: Re: [Anima] use of CRLs in I-D Action: draft-ietf-anima-autonomic-control-plane-26.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, 01 Jul 2020 23:41:08 -0000

On Wed, Jul 01, 2020 at 06:58:10PM -0400, Michael Richardson wrote:
> 
> the diff for 6.1.5.3.  Certificate Revocation Lists (CRLs)
> fixes some TLAs, but continues to seem to recommend long-lived certificates with CRLs.

The need to diligently document support for CRL/OCSP was done on
behalf of securiy reviews. It is not meant to be a recommendation.
There is mentioning of short-lived certificates in a few places in the
doc.

> I think that CRLs are not useful, and we should not use them.

I think we agree.

> 6.1.3 is clear that OCSP/CRLs may not be available when connecting!
> 
> I think that use of STAR (https://datatracker.ietf.org/doc/rfc8739/ )
> Short-Term, Automatically Renewed is the best recommendation!

In general yes, but the STAR use cases typically do not take into
account  connectivity problems that are longer than the lifetime of
a cert, whereas for the ACP this might be a problem.

With CRL/OCSP, it seems as if we could define the details under
loss of connectivity through these mentioned rules. This seems
like an easily acceptable solution for the proponents of CRL/OCSP
because they couldn't come up with a better solution and its their
technology.

When we are talking about expiry of short lived certs we would be
talking about pootentially authenticating expired certs under
limited network connectivity. Thats quite new and the proponents
of CRL/OCSP would drag along the argument much longer.

> If we have to do OCSP (via https://datatracker.ietf.org/doc/rfc4806/ )
> then we nodes can download their staple and provide it when connecting.
> New nodes can get this using the Join Proxy.
> 
> Perhaps this needs to be in a new document at this point.

Yepp.  I think to remember that MaxP was thinking of suggesting to
talk about dealing with expired certs for our cases in i think LAMPS too
but longer ago...

Cheers
    Toerless


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


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


From nobody Wed Jul  1 17:30:42 2020
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 7B8D03A1259 for <anima@ietfa.amsl.com>; Wed,  1 Jul 2020 17:30:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 M82kqZ05aTGd for <anima@ietfa.amsl.com>; Wed,  1 Jul 2020 17:30:38 -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 A57723A1258 for <anima@ietf.org>; Wed,  1 Jul 2020 17:30:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 56882389CD; Wed,  1 Jul 2020 20:27:49 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id u7f_Q3i1KgIv; Wed,  1 Jul 2020 20:27:48 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id A346F389B6; Wed,  1 Jul 2020 20:27:48 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id A4E0350E; Wed,  1 Jul 2020 20:30:36 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Toerless Eckert <tte@cs.fau.de>, anima@ietf.org
In-Reply-To: <20200701234100.GC60049@faui48f.informatik.uni-erlangen.de>
References: <159363696301.1694.14970467680230111407@ietfa.amsl.com> <14763.1593644290@localhost> <20200701234100.GC60049@faui48f.informatik.uni-erlangen.de>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512; protocol="application/pgp-signature"
Date: Wed, 01 Jul 2020 20:30:36 -0400
Message-ID: <4988.1593649836@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/-ftDr5tHLIcdj5DWH41LjAbhpt0>
Subject: Re: [Anima] use of CRLs in I-D Action: draft-ietf-anima-autonomic-control-plane-26.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, 02 Jul 2020 00:30:41 -0000

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


Toerless Eckert <tte@cs.fau.de> wrote:
    > The need to diligently document support for CRL/OCSP was done on
    > behalf of securiy reviews. It is not meant to be a recommendation.
    > There is mentioning of short-lived certificates in a few places in the
    > doc.

I didn't see an RFC8739 reference.  Oh. It's I-D.ietf-acme-star.
Your section 6.1.5.4 suggests CRLs are unnecessary when the lifetime is on
the order of hours,  while RFC8739 is less specific about what is short.
I think that a certificate lifetime on the order of a week would probably be
workable.

But, I think think we should get implementation experience.

    >> I think that CRLs are not useful, and we should not use them.

    > I think we agree.

Good.

    >> 6.1.3 is clear that OCSP/CRLs may not be available when connecting!
    >>
    >> I think that use of STAR (https://datatracker.ietf.org/doc/rfc8739/ )
    >> Short-Term, Automatically Renewed is the best recommendation!

    > In general yes, but the STAR use cases typically do not take into
    > account  connectivity problems that are longer than the lifetime of
    > a cert, whereas for the ACP this might be a problem.

yes, but the solution is to find a Join Proxy, reach out to the Registrar and
renew the certificate using the LDevID one has.
STAR even went into some detail about how one could renew expired
certificates, I think. (I recall a discussion, but I'd have to check the
document again)

    >> If we have to do OCSP (via https://datatracker.ietf.org/doc/rfc4806/ )
    >> then we nodes can download their staple and provide it when connecting.
    >> New nodes can get this using the Join Proxy.
    >>
    >> Perhaps this needs to be in a new document at this point.

    > Yepp.  I think to remember that MaxP was thinking of suggesting to
    > talk about dealing with expired certs for our cases in i think LAMPS too
    > but longer ago...

yes, the document wound up in ACME, and I think they did a good job, although
it is proscriptive for ACME only, while our end-client interface is assumed
to be EST.

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




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

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

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl79KqwACgkQgItw+93Q
3WW7Bwf/dZ5tSnWE6VgFph5ryT7wOgrF6rlGAu4e2A2zZ9HLtLgL9HjBo9+ULqGh
xDGfCEz8mWZAH40F6zM8LSf2MmVNw7a7xtz2l21PhBUERVjOTOmBJOH3CF0Y7ocO
8HrsiPAb1g1OixAOTHN2w4Twe8FcTNZOX7ByNE3LK1ilIfyaRuR3olyuWUO1XSy2
9jU4WBv4vzyUV4F8UcQkpoGSEnV/WE36FdkLd9vCBzjKOY75IxLBFJlDlZAk7ytW
aVTtePJWFuJLoNhn32kM7ceAkD7qobSZCSJDMFNIX5sHzvJHiwU7rhwLhE4/aJfG
tNYKVpMq06T6OWcUokTKxmNwxF4etg==
=f1XN
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Jul  2 05:55:11 2020
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 A87743A084B; Thu,  2 Jul 2020 05:55:05 -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: 7.7.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: anima@ietf.org
Message-ID: <159369450564.27936.11918522329746807159@ietfa.amsl.com>
Date: Thu, 02 Jul 2020 05:55:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/Xdd8ylq4_pA_pqMSMgwldMnJoMk>
Subject: [Anima] I-D Action: draft-ietf-anima-autonomic-control-plane-27.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, 02 Jul 2020 12:55:06 -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-27.txt
	Pages           : 162
	Date            : 2020-07-02

Abstract:
   Autonomic functions need a control plane to communicate, which
   depends on some addressing and routing.  This Autonomic 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-27
https://datatracker.ietf.org/doc/html/draft-ietf-anima-autonomic-control-plane-27

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


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 Jul  2 06:09:50 2020
Return-Path: <noreply@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 B20693A0977; Thu,  2 Jul 2020 06:09:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?=C3=89ric_Vyncke_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-anima-autonomic-control-plane@ietf.org, anima-chairs@ietf.org,  anima@ietf.org, Sheng Jiang <jiangsheng@huawei.com>, jiangsheng@huawei.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.7.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?=C3=89ric_Vyncke?= <evyncke@cisco.com>
Message-ID: <159369538970.29573.13285427447389377274@ietfa.amsl.com>
Date: Thu, 02 Jul 2020 06:09:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/PenKrxLJ6NGoaLCVauovvd4aZsU>
Subject: [Anima] =?utf-8?q?=C3=89ric_Vyncke=27s_Yes_on_draft-ietf-anima-a?= =?utf-8?q?utonomic-control-plane-27=3A_=28with_COMMENT=29?=
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, 02 Jul 2020 13:09:50 -0000

Éric Vyncke has entered the following ballot position for
draft-ietf-anima-autonomic-control-plane-27: Yes

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/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks to the authors and the ANIMA WG and the numerous reviewers for this document.

After my own review late 2019, I think that the document is ready to be published.




From nobody Thu Jul  2 06:29:31 2020
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 14E5E3A00B0; Thu,  2 Jul 2020 06:29:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.871
X-Spam-Level: 
X-Spam-Status: No, score=-0.871 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779] 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 v-UZkjWfzSBa; Thu,  2 Jul 2020 06:29:28 -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 D0F1B3A00AD; Thu,  2 Jul 2020 06:29:27 -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 C3E2F548011; Thu,  2 Jul 2020 15:29:22 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id BED76440043; Thu,  2 Jul 2020 15:29:22 +0200 (CEST)
Date: Thu, 2 Jul 2020 15:29:22 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: anima@ietf.org
Cc: "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "Rob Wilton (rwilton)" <rwilton@cisco.com>, housley@vigilsec.com
Message-ID: <20200702132922.GA11404@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/NmjGa8Iy3IZwT_W-HphP40sCCZY>
Subject: [Anima] ANIMA-WG: pls chime in: early allocation for otherName code points (draft-ietf-anima-autonomic-control-plane)
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, 02 Jul 2020 13:29:30 -0000

Dear WG (ACP author head/hat on)

ACP Revision -26 introduced a new otherName / AcpNodeName encoding for the ACP Domain Information
(now call AcpNodeName / acp-node-name). Michael Richardson (and potentially other) implementors
would like to update implementation to use this new encoding for interop testing,
which requires allocation of two IANA code points (technically i think only one is
required for the implementation, but the toolchain would require both if i understand it
correctly).

The early allocation process RFC7120 requires to vet the community for interest in the
early allocation, so pls. chime in with a +1, or if you must a -1 and explanation.

I'll do a +1 from the authors side.

The remaining requirements of RFC7120 for early allocations are AFAIK met.

Thanks!
    Toerless


From nobody Thu Jul  2 06:41:21 2020
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 C28113A07ED; Thu,  2 Jul 2020 06:41:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level: 
X-Spam-Status: No, score=-9.601 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, DKIM_VALID_EF=-0.1, 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 0mgPyB-TrEJH; Thu,  2 Jul 2020 06:41:17 -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 D4F933A07E5; Thu,  2 Jul 2020 06:41:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1280; q=dns/txt; s=iport; t=1593697277; x=1594906877; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=0oPNAdindKHqmmzixUQSjjinqQKSWZGc4RLkROqHCho=; b=PgUUXG9PxdOHhuwXhoA6oF0irveXMpU9aXs80nRu+8E9CedXv/ua/6W4 Kx6hhGFTdtHnhHwoQ+OBNFPTeyeuQB6hBTC2kfzFw9l04dCjjlvYYitfx Ei3c2HaGzib55WJD/xnn/pyHExoEQYQps4t5TuWtMh57lX1XChy8NzD25 c=;
X-IronPort-AV: E=Sophos;i="5.75,304,1589241600"; d="scan'208";a="27551850"
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; 02 Jul 2020 13:41:15 +0000
Received: from ams3-vpn-dhcp5065.cisco.com (ams3-vpn-dhcp5065.cisco.com [10.61.83.200]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 062DfE0m005946 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 2 Jul 2020 13:41:14 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Eliot Lear <lear@cisco.com>
In-Reply-To: <20200702132922.GA11404@faui48f.informatik.uni-erlangen.de>
Date: Thu, 2 Jul 2020 15:41:14 +0200
Cc: anima@ietf.org, "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "Rob Wilton (rwilton)" <rwilton@cisco.com>, housley@vigilsec.com
Content-Transfer-Encoding: quoted-printable
Message-Id: <91A85F2F-D9D7-4D64-8672-50DF942A063C@cisco.com>
References: <20200702132922.GA11404@faui48f.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-Outbound-SMTP-Client: 10.61.83.200, ams3-vpn-dhcp5065.cisco.com
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/sJnla7VLjMo_SKSlmFrpTuceW2s>
Subject: Re: [Anima] ANIMA-WG: pls chime in: early allocation for otherName code points (draft-ietf-anima-autonomic-control-plane)
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, 02 Jul 2020 13:41:19 -0000

I have no objection.  My only caution is that otherName is poorly =
supported in the open source tool sets, but that is something we could =
conceivably work on.

Eliot

> On 2 Jul 2020, at 15:29, Toerless Eckert <tte@cs.fau.de> wrote:
>=20
> Dear WG (ACP author head/hat on)
>=20
> ACP Revision -26 introduced a new otherName / AcpNodeName encoding for =
the ACP Domain Information
> (now call AcpNodeName / acp-node-name). Michael Richardson (and =
potentially other) implementors
> would like to update implementation to use this new encoding for =
interop testing,
> which requires allocation of two IANA code points (technically i think =
only one is
> required for the implementation, but the toolchain would require both =
if i understand it
> correctly).
>=20
> The early allocation process RFC7120 requires to vet the community for =
interest in the
> early allocation, so pls. chime in with a +1, or if you must a -1 and =
explanation.
>=20
> I'll do a +1 from the authors side.
>=20
> The remaining requirements of RFC7120 for early allocations are AFAIK =
met.
>=20
> Thanks!
>    Toerless
>=20
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima


From nobody Thu Jul  2 06:57:14 2020
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 B656A3A081B; Thu,  2 Jul 2020 06:57:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level: 
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, 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 TIohOnaYKO71; Thu,  2 Jul 2020 06:57:12 -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 988973A0819; Thu,  2 Jul 2020 06:57:11 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id BA70C54843F; Thu,  2 Jul 2020 15:57:06 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id B4BB1440043; Thu,  2 Jul 2020 15:57:06 +0200 (CEST)
Date: Thu, 2 Jul 2020 15:57:06 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Eliot Lear <lear@cisco.com>
Cc: anima@ietf.org, "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "Rob Wilton (rwilton)" <rwilton@cisco.com>, housley@vigilsec.com
Message-ID: <20200702135706.GB11404@faui48f.informatik.uni-erlangen.de>
References: <20200702132922.GA11404@faui48f.informatik.uni-erlangen.de> <91A85F2F-D9D7-4D64-8672-50DF942A063C@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <91A85F2F-D9D7-4D64-8672-50DF942A063C@cisco.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/i-d-pG3DZgDbqPe4Z9WuEZD2EjU>
Subject: Re: [Anima] ANIMA-WG: pls chime in: early allocation for otherName code points (draft-ietf-anima-autonomic-control-plane)
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, 02 Jul 2020 13:57:14 -0000

On Thu, Jul 02, 2020 at 03:41:14PM +0200, Eliot Lear wrote:
> I have no objection.  My only caution is that otherName is poorly supported in the open source tool sets, but that is something we could conceivably work on.

Thanks, i would count it towards the need for experimentation.

If there is explicit feedback that otherName will be less well implementable/deployable
than URI / "urn:ietf:params:acp:node:<AcpNodeName>", then i would at this
stage of the process probably still rather start a second 3 page normative
RFC that specifies the use of the URN Name for ACP as an alternative,
because after 6 years it would be a nice change not to further drag our
heels on the first ACP RFC.

Cheers
    Toerless

> Eliot
> 
> > On 2 Jul 2020, at 15:29, Toerless Eckert <tte@cs.fau.de> wrote:
> > 
> > Dear WG (ACP author head/hat on)
> > 
> > ACP Revision -26 introduced a new otherName / AcpNodeName encoding for the ACP Domain Information
> > (now call AcpNodeName / acp-node-name). Michael Richardson (and potentially other) implementors
> > would like to update implementation to use this new encoding for interop testing,
> > which requires allocation of two IANA code points (technically i think only one is
> > required for the implementation, but the toolchain would require both if i understand it
> > correctly).
> > 
> > The early allocation process RFC7120 requires to vet the community for interest in the
> > early allocation, so pls. chime in with a +1, or if you must a -1 and explanation.
> > 
> > I'll do a +1 from the authors side.
> > 
> > The remaining requirements of RFC7120 for early allocations are AFAIK met.
> > 
> > Thanks!
> >    Toerless
> > 
> > _______________________________________________
> > Anima mailing list
> > Anima@ietf.org
> > https://www.ietf.org/mailman/listinfo/anima

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


From nobody Thu Jul  2 10:24:49 2020
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 463593A0C1B for <anima@ietfa.amsl.com>; Thu,  2 Jul 2020 10:24:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 arbsBr3bZgbg for <anima@ietfa.amsl.com>; Thu,  2 Jul 2020 10:24:36 -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 5AD483A0B4F for <anima@ietf.org>; Thu,  2 Jul 2020 10:24:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 75DEA389CB for <anima@ietf.org>; Thu,  2 Jul 2020 13:21:46 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id qytObwPU2qdx for <anima@ietf.org>; Thu,  2 Jul 2020 13:21:45 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 8C513389BB for <anima@ietf.org>; Thu,  2 Jul 2020 13:21:45 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 2B7995C5 for <anima@ietf.org>; Thu,  2 Jul 2020 13:24:34 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
In-Reply-To: <20200702132922.GA11404@faui48f.informatik.uni-erlangen.de>
References: <20200702132922.GA11404@faui48f.informatik.uni-erlangen.de>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512; protocol="application/pgp-signature"
Date: Thu, 02 Jul 2020 13:24:34 -0400
Message-ID: <23958.1593710674@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/EIzcrM09JJmT7T-_Vz4IxEi5GhM>
Subject: Re: [Anima] ANIMA-WG: pls chime in: early allocation for otherName code points (draft-ietf-anima-autonomic-control-plane)
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, 02 Jul 2020 17:24:48 -0000

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


Toerless Eckert <tte@cs.fau.de> wrote:
    > would like to update implementation to use this new encoding for interop testing,
    > which requires allocation of two IANA code points (technically i think only one is
    > required for the implementation, but the toolchain would require both if i understand it
    > correctly).

If you use an ASN1 compiler for this, then yes.

If one does library calls to code that already processes otherName, then just
the IANA2 OID is needed, but I'm all for asking for both.

    > The early allocation process RFC7120 requires to vet the community for interest in the
    > early allocation, so pls. chime in with a +1, or if you must a -1 and explanation.

    > I'll do a +1 from the authors side.

    > The remaining requirements of RFC7120 for early allocations are AFAIK met.

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




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

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

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl7+GFEACgkQgItw+93Q
3WVMkQf/RH1xgDsJ6Fdn8cKHkra17dCZTgqKurs4c6TuxPYFPAjs4TgiFf9iHgPt
oTgi1Ne76ZqK8jiNfdGhWHQdlhvLyZ3wezsd/jUv8mqxH7cHyQ4aW/FmD229hARX
j3n6ALMIrz//aAzht682CSuAkwYnQKNFT7uwYXl9CdDo1TE/Qjv0fgwwch+a5fVH
kHKkIMpP9RYUk2KEjPtHTKqOiDkVjrVVqmIvVD+JtcIUTm4cRUH/teg0eaOaph8T
+g3v7Bg/SdZmggUmfw2Ik90+IpDXs+hR7XdL5w/8uCZuPZnDXRYaKxSxJgBgKnTg
1J42BJY7zDnghw3aDJ46UFK7n1JhAw==
=706y
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Jul  2 10:29:12 2020
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 850A73A0B0B for <anima@ietfa.amsl.com>; Thu,  2 Jul 2020 10:29:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 uoK9Qfz9hvR1 for <anima@ietfa.amsl.com>; Thu,  2 Jul 2020 10:29:09 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E6E53A0B05 for <anima@ietf.org>; Thu,  2 Jul 2020 10:29:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 192C5389CF for <anima@ietf.org>; Thu,  2 Jul 2020 13:26:20 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id exrh8T1NXeI8 for <anima@ietf.org>; Thu,  2 Jul 2020 13:26:19 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 4F7C9389BB for <anima@ietf.org>; Thu,  2 Jul 2020 13:26:19 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id EDD5C5C5 for <anima@ietf.org>; Thu,  2 Jul 2020 13:29:07 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
In-Reply-To: <91A85F2F-D9D7-4D64-8672-50DF942A063C@cisco.com>
References: <20200702132922.GA11404@faui48f.informatik.uni-erlangen.de> <91A85F2F-D9D7-4D64-8672-50DF942A063C@cisco.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512; protocol="application/pgp-signature"
Date: Thu, 02 Jul 2020 13:29:07 -0400
Message-ID: <25042.1593710947@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/KAGbfLLnuleNzqKfIKVj0uYgVmw>
Subject: Re: [Anima] ANIMA-WG: pls chime in: early allocation for otherName code points (draft-ietf-anima-autonomic-control-plane)
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, 02 Jul 2020 17:29:12 -0000

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


Eliot Lear <lear=40cisco.com@dmarc.ietf.org> wrote:
    > I have no objection.  My only caution is that otherName is poorly
    > supported in the open source tool sets, but that is something we could
    > conceivably work on.

I disagree!
otherName is adequately supported (if poorly documented) in openssl.cnf for our purposes.
Creating otherName SAN extensions from library interface is fully supported.

The openssl x509 -text output program does not know how to format arbitrary
otherName text, so it just says <unsupported>.

Here is an proprietary otherName that I created awhile ago, implemented in ruby:

      # the OID: 1.3.6.1.4.1.46930.1 is a Private Enterprise Number OID:
      #    iso.org.dod.internet.private.enterprise . SANDELMAN=46930 . 1
      @idevid.add_extension(extension_factory.create_extension(
                              "subjectAltName",
                              sprintf("otherName:1.3.6.1.4.1.46930.1;UTF8:%s",
                                      self.sanitized_eui64),
                              false))

The hardest part was figuring out the ";UTF8:" part, as I had to read the C
code underneath to learn how that worked.
(false, is I think, whether it is critical)

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




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

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

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl7+GWMACgkQgItw+93Q
3WXczAf/W2/YcF37SPd0nOkI5qqhB1J0oaMK4UO66kihMxJPBiguPUwVxYyBQGuM
HXos6pC0HXY0RzeLaMBokvnAEOFjXGfTArsnVt0g4xG8cJ1/C7eJbVavM7nwAZQ/
HmpQIA/UGtBtB8RnedEpSy49teU0++nDNK5uR0XqIZ+ioQauRjmauvQtwIrWQR1y
fycoknp0ZKbcaeLCvoAkB4qUhKDZdx0olWFQCybJSG+YDKp0XyfQaIxVrdea4e+L
CEyInV78vAfWu9VfEXsILIt7jV+BJgD+W0STGPvyYHq+14+KNWA8b20SdRGJjqSe
72/tPGrlHA/E1i040VxhlGBkWQhIJg==
=y5Mc
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Jul  2 10:52:03 2020
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 ED7D93A0775 for <anima@ietfa.amsl.com>; Thu,  2 Jul 2020 10:52:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level: 
X-Spam-Status: No, score=-9.601 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, DKIM_VALID_EF=-0.1, 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 D61LzhJeGI_s for <anima@ietfa.amsl.com>; Thu,  2 Jul 2020 10:52:00 -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 49CB23A076C for <anima@ietf.org>; Thu,  2 Jul 2020 10:52:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2791; q=dns/txt; s=iport; t=1593712320; x=1594921920; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=0C0J6INCZ4j5fH0sevBpOiZ48FsftnaBLc6CnJJM550=; b=Hom4qt8Irlpr/G/Anrrmmu9xjB5IZQWdgkUL+uJbHFt1Psh3vxA0ib8D uHJHzWoDbZhJ5tTZswmVjUGtjEPHw/OVnLl9NCrhGqdXGeBSppjYSDcfE Vj8lE2kZKXxIF8d3EvxCiitBIfJLgao0iHS+eT9eLqzRxOwIRvFd5J6NB w=;
X-Files: signature.asc : 488
X-IPAS-Result: =?us-ascii?q?A0BqAAAHHv5e/xbLJq1fGQEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?RIBAQEBAQEBAQEBAQGCCoNtASASLIQxiQGIFJwEBAcBAQEJAwEBLwQBAYFTg?= =?us-ascii?q?nQCgh0lOBMCAwEBAQMCAwEBAQEFAQEBAgEGBG2FZ4VuAQEBAQIBI1YFCwsYI?= =?us-ascii?q?wcCAlcGE4MmAYJcIKkIdoEyhVGFGxCBOAGBUosvggCBOByCTT6CXASEczOCL?= =?us-ascii?q?QSaNJpWgmaDBoEnlR0DHYJzjisnjVisaINRAgQGBQIVgWoigVYzGggbFWUBg?= =?us-ascii?q?j4+EhkNjioXFI4SPwMwAjUCBgEHAQEDCY9dAQE?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.75,305,1589241600";  d="asc'?scan'208";a="25181950"
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-SEED-SHA; 02 Jul 2020 17:51:56 +0000
Received: from [10.61.241.120] ([10.61.241.120]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 062Hpttx026387 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 2 Jul 2020 17:51:56 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <FEA3EA3B-5F2D-4B2D-8F64-1BD19B6E3B9D@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_F3AD4E91-0F64-46DF-AC16-CAE5AA1754EB"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Thu, 2 Jul 2020 19:51:54 +0200
In-Reply-To: <25042.1593710947@localhost>
Cc: anima@ietf.org
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <20200702132922.GA11404@faui48f.informatik.uni-erlangen.de> <91A85F2F-D9D7-4D64-8672-50DF942A063C@cisco.com> <25042.1593710947@localhost>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-Outbound-SMTP-Client: 10.61.241.120, [10.61.241.120]
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/Qp7vjU7ROba0vdDKkfoyQCxcOEc>
Subject: Re: [Anima] ANIMA-WG: pls chime in: early allocation for otherName code points (draft-ietf-anima-autonomic-control-plane)
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, 02 Jul 2020 17:52:02 -0000

--Apple-Mail=_F3AD4E91-0F64-46DF-AC16-CAE5AA1754EB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On 2 Jul 2020, at 19:29, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:
>=20
> Signed PGP part
>=20
> Eliot Lear <lear=3D40cisco.com@dmarc.ietf.org> wrote:
>> I have no objection.  My only caution is that otherName is poorly
>> supported in the open source tool sets, but that is something we =
could
>> conceivably work on.
>=20
> I disagree!
> otherName is adequately supported (if poorly documented) in =
openssl.cnf for our purposes.
> Creating otherName SAN extensions from library interface is fully =
supported.
>=20
> The openssl x509 -text output program does not know how to format =
arbitrary
> otherName text, so it just says <unsupported>.

Whereas for a URI it will actually provide you the URI.  Also, if the =
otherName is at all complex, the openssl.cnf file is entirely =
counter-intuitive.  This having been said, one needn=E2=80=99t write to =
OpenSSL=E2=80=99s limitations.

Eliot

>=20
> Here is an proprietary otherName that I created awhile ago, =
implemented in ruby:
>=20
>      # the OID: 1.3.6.1.4.1.46930.1 is a Private Enterprise Number =
OID:
>      #    iso.org.dod.internet.private.enterprise . SANDELMAN=3D46930 =
. 1
>      @idevid.add_extension(extension_factory.create_extension(
>                              "subjectAltName",
>                              =
sprintf("otherName:1.3.6.1.4.1.46930.1;UTF8:%s",
>                                      self.sanitized_eui64),
>                              false))
>=20
> The hardest part was figuring out the ";UTF8:" part, as I had to read =
the C
> code underneath to learn how that worked.
> (false, is I think, whether it is critical)
>=20
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -=3D IPv6 IoT consulting =3D-
>=20
>=20
>=20
>=20
>=20


--Apple-Mail=_F3AD4E91-0F64-46DF-AC16-CAE5AA1754EB
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-----

iQEzBAEBCAAdFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAl7+HroACgkQh7ZrRtnS
ejOIcwf/brhX8fB8+DfMxVmk6mVIngPTvEnEARLkQooMKO2ah4LUZGvCeu8Z8hFC
Wxo2ZP9F91ZIcLEN9R+kGiop7iX8Hc7sJpxZ3tr2TvfVvpry5hbB8yEi3wb/j9ez
Xk1/OUp4QR7snKJAnOswGyoTJX8dvANQhQ1qdW56o+PIDd9VlCRJwqktD/fAWMjv
mHWkxABl7L6qL58vQ5UyaC8H3FdF+/fCO6ykzglpzPlI3u1250huRLdHruM/cL5i
VvZRzBGRveaFQt8yvtS+S3Umbbts41xLs5eW0a9sDPG5K/EILoJWWr2S0BDin54u
q3JRbsLNLU1nlptsdz5sGfWfeoGKWQ==
=Ie8o
-----END PGP SIGNATURE-----

--Apple-Mail=_F3AD4E91-0F64-46DF-AC16-CAE5AA1754EB--


From nobody Thu Jul  2 13:43:43 2020
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 68B623A0AC5 for <anima@ietfa.amsl.com>; Thu,  2 Jul 2020 13:43:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.87
X-Spam-Level: 
X-Spam-Status: No, score=-0.87 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, 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 Ql7bboImrNGD for <anima@ietfa.amsl.com>; Thu,  2 Jul 2020 13:43:39 -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 1D4E93A0ABE for <anima@ietf.org>; Thu,  2 Jul 2020 13:43:38 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 277F554843F; Thu,  2 Jul 2020 22:43:34 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 2269F440043; Thu,  2 Jul 2020 22:43:34 +0200 (CEST)
Date: Thu, 2 Jul 2020 22:43:34 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: anima@ietf.org
Message-ID: <20200702204334.GA43996@faui48f.informatik.uni-erlangen.de>
References: <20200702132922.GA11404@faui48f.informatik.uni-erlangen.de> <91A85F2F-D9D7-4D64-8672-50DF942A063C@cisco.com> <25042.1593710947@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <25042.1593710947@localhost>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/6DauiY_TyQeFRZIPKT4grAjj2VQ>
Subject: Re: [Anima] ANIMA-WG: pls chime in: early allocation for otherName code points (draft-ietf-anima-autonomic-control-plane)
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, 02 Jul 2020 20:43:41 -0000

UTF8 ? ;-))

AcpNodeName ::= IA5String (SIZE (1..MAX))

To keep the encoding simple, there is no consideration for
internationalized acp-domain-names.  The acp-node-name is not
intended for end user consumption...


On Thu, Jul 02, 2020 at 01:29:07PM -0400, Michael Richardson wrote:
> 
> Eliot Lear <lear=40cisco.com@dmarc.ietf.org> wrote:
>     > I have no objection.  My only caution is that otherName is poorly
>     > supported in the open source tool sets, but that is something we could
>     > conceivably work on.
> 
> I disagree!
> otherName is adequately supported (if poorly documented) in openssl.cnf for our purposes.
> Creating otherName SAN extensions from library interface is fully supported.
> 
> The openssl x509 -text output program does not know how to format arbitrary
> otherName text, so it just says <unsupported>.
> 
> Here is an proprietary otherName that I created awhile ago, implemented in ruby:
> 
>       # the OID: 1.3.6.1.4.1.46930.1 is a Private Enterprise Number OID:
>       #    iso.org.dod.internet.private.enterprise . SANDELMAN=46930 . 1
>       @idevid.add_extension(extension_factory.create_extension(
>                               "subjectAltName",
>                               sprintf("otherName:1.3.6.1.4.1.46930.1;UTF8:%s",
>                                       self.sanitized_eui64),
>                               false))
> 
> The hardest part was figuring out the ";UTF8:" part, as I had to read the C
> code underneath to learn how that worked.
> (false, is I think, whether it is critical)
> 
> --
> 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


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


From nobody Thu Jul  2 13:57:59 2020
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 F1DBD3A0B57; Thu,  2 Jul 2020 13:57:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, 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 Iee_vepqM7Y0; Thu,  2 Jul 2020 13:57:56 -0700 (PDT)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (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 8300D3A0B4F; Thu,  2 Jul 2020 13:57:56 -0700 (PDT)
Received: by mail-pg1-x532.google.com with SMTP id w2so13231012pgg.10; Thu, 02 Jul 2020 13:57:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=+R9xKzSnjsWJt+Qy/+pS95nhEIQyRAiJVSr2CQihFww=; b=vCiR7viU5fh6FwC9Bm+M9dz4IZ7qKgk9WWAXY8YTfa0HpqoLfjrbZrQ9gZp5MB048p PcrlGn2sxunAZKctuY8CdyzDy7zz07p22XLdumnWOAQFu8hfoQSTZ6zIj81/5zHDiG8Q w4DO8eDi75XfLLnVSLWR1KQWacvq0ZqPaWEvlp4fExSpeNM2F81ohWNGCxSEwjVIW/kB LHvx6hFnN0yRHNBpr2j8LZ5WxX48/eRLr+Y6QDwd7IL4XbCUNIZ2CSipdozLnJL0+PaN 9ezFtXj33ibtu+RG4UetChm6o6skA2aMo2EdIP00lJY6X5k93ce0r0dapwctvc9cOupA GzFQ==
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:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=+R9xKzSnjsWJt+Qy/+pS95nhEIQyRAiJVSr2CQihFww=; b=smMkIox+Uq7YtWthbMmts0l9bi1N8bL9UkEDJQOlDxYtiA8sv6896IeQFwIfN4waba ftvNWHl0T5FfQm1K0j6xW1uihyrKc8kGuLsFPZgxMEKG2E9Ds5wRYZ5nUCqJaCbsX2dh zgmo/pOJcaV0mJM4eVqps2r5kZOI1FsG7ZAadsCrCsm05wfU4th5CwSQFDvXe4TqstGT mS8JPiEyB2JOsBDsWeZj7Q6FTy8+PvuY3FGBFimpWrQTrroqu4xJa6fuhqgyUTyNoVWX gKGPQseAADBzqzquP9e8Z58I/o3mpmgYWyasQ0DEZhFy7fC66Nd8E5zWG7GZHx6V0a3H 5UNg==
X-Gm-Message-State: AOAM532zYlptd7ayk1FbbsWXukBxOiv0Gfr2BvmA6rKMntIVYkgWKP0a 1U3H61We2VIsfveqjEj4ssE=
X-Google-Smtp-Source: ABdhPJyzO1beDH5MZc5ddcbd4kYiXlwGv/kIt7vb+wZEzmZyAlg4GXqxTJwyCcHhF8jmJqVbVf7jXA==
X-Received: by 2002:a62:a510:: with SMTP id v16mr31476179pfm.154.1593723475960;  Thu, 02 Jul 2020 13:57:55 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.139.172]) by smtp.gmail.com with ESMTPSA id q24sm9327888pgg.3.2020.07.02.13.57.53 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Jul 2020 13:57:55 -0700 (PDT)
To: Toerless Eckert <tte@cs.fau.de>, anima@ietf.org
Cc: "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "Rob Wilton (rwilton)" <rwilton@cisco.com>, housley@vigilsec.com
References: <20200702132922.GA11404@faui48f.informatik.uni-erlangen.de>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <148562ab-3a22-1e47-8a35-80c05e05cb84@gmail.com>
Date: Fri, 3 Jul 2020 08:57:50 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <20200702132922.GA11404@faui48f.informatik.uni-erlangen.de>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/Mj1EMkdXlWQRX6x5S69PD3UxmFY>
Subject: Re: [Anima] ANIMA-WG: pls chime in: early allocation for otherName code points (draft-ietf-anima-autonomic-control-plane)
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, 02 Jul 2020 20:57:58 -0000

Yes please. We have a need for implementations ASAP, however long this spends in the RFC queue.

Regards
   Brian Carpenter

On 03-Jul-20 01:29, Toerless Eckert wrote:
> Dear WG (ACP author head/hat on)
> 
> ACP Revision -26 introduced a new otherName / AcpNodeName encoding for the ACP Domain Information
> (now call AcpNodeName / acp-node-name). Michael Richardson (and potentially other) implementors
> would like to update implementation to use this new encoding for interop testing,
> which requires allocation of two IANA code points (technically i think only one is
> required for the implementation, but the toolchain would require both if i understand it
> correctly).
> 
> The early allocation process RFC7120 requires to vet the community for interest in the
> early allocation, so pls. chime in with a +1, or if you must a -1 and explanation.
> 
> I'll do a +1 from the authors side.
> 
> The remaining requirements of RFC7120 for early allocations are AFAIK met.
> 
> Thanks!
>     Toerless
> 
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima
> .
> 


From nobody Thu Jul  2 16:46:45 2020
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 0140D3A086C for <anima@ietfa.amsl.com>; Thu,  2 Jul 2020 16:46:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 xIaMmpEFRief for <anima@ietfa.amsl.com>; Thu,  2 Jul 2020 16:46:41 -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 842503A082D for <anima@ietf.org>; Thu,  2 Jul 2020 16:46:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 5F968389D4; Thu,  2 Jul 2020 19:43:51 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id nYE8BveNC-p8; Thu,  2 Jul 2020 19:43:50 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 9E56C389C7; Thu,  2 Jul 2020 19:43:50 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 8251B5C5; Thu,  2 Jul 2020 19:46:39 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Toerless Eckert <tte@cs.fau.de>, anima@ietf.org
In-Reply-To: <20200702204334.GA43996@faui48f.informatik.uni-erlangen.de>
References: <20200702132922.GA11404@faui48f.informatik.uni-erlangen.de> <91A85F2F-D9D7-4D64-8672-50DF942A063C@cisco.com> <25042.1593710947@localhost> <20200702204334.GA43996@faui48f.informatik.uni-erlangen.de>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512; protocol="application/pgp-signature"
Date: Thu, 02 Jul 2020 19:46:39 -0400
Message-ID: <26790.1593733599@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/oku_bo0JGPe1-zxZPZNLqemDpJ8>
Subject: Re: [Anima] ANIMA-WG: pls chime in: early allocation for otherName code points (draft-ietf-anima-autonomic-control-plane)
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, 02 Jul 2020 23:46:44 -0000

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


Toerless Eckert <tte@cs.fau.de> wrote:
    > UTF8 ? ;-))

    > AcpNodeName ::= IA5String (SIZE (1..MAX))

    >> # the OID: 1.3.6.1.4.1.46930.1 is a Private Enterprise Number OID:
    >> #    iso.org.dod.internet.private.enterprise . SANDELMAN=46930 . 1
    >> @idevid.add_extension(extension_factory.create_extension(
    >> "subjectAltName",
    >> sprintf("otherName:1.3.6.1.4.1.46930.1;UTF8:%s",
    >> self.sanitized_eui64),
    >> false))

I think it's just:

 @idevid.add_extension(extension_factory.create_extension(
    "subjectAltName",
    sprintf("otherName:1.3.6.1.4.1.46930.1;IA5STRING:%s",
    self.sanitized_eui64),
    false))

Although I think "IA5" and "IA5STRING" are equvivalent here.

    >> The hardest part was figuring out the ";UTF8:" part, as I had to read the C
    >> code underneath to learn how that worked.
    >> (false, is I think, whether it is critical)

The table is at: openssl/crypto/asn1/asn1_gen.c.  If it's in a document
somewhere, I never found it.

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




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

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

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl7+cd8ACgkQgItw+93Q
3WXbIwgArjnrYMV1V/mhCwPR1dBiYupESPEw/5PMlXdgbhBfB/hgtuUeaLsqJqrW
CWcdKXU57vurpWNI3FnAxwhJ4RE1WiBl8JMCh5BXOqjftS44tXFulh/o1ndWhtKO
1WOYH11ZbF0wb8o3+HkC7mCnHKjWIcHqlfN1C4qyVWzz53qxAgvKN3i9cDWrG283
11o3KcVTrW6Hgtc+WpTKAgX/fUPJI70VjC2FoF+t8InsoxrARLESbyhmMPkLY+pG
noiA3PY1LQOjikMwTu+ASx9OTa2DC/FqNO7AxGl4ZWp5ghhoT+6aFBOtSaDjODnF
5GEnSWq5XYf/tT0NgFxisjKd7CWx5Q==
=CDKz
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Jul  2 17:23:45 2020
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 B432C3A0B26; Thu,  2 Jul 2020 17:21:39 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <jiangsheng@huawei.com>, <anima-chairs@ietf.org>
Cc: anima@ietf.org, rwilton@cisco.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.7.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <159373569972.29538.948445045376303761@ietfa.amsl.com>
Date: Thu, 02 Jul 2020 17:21:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/D4dDF-Cd54ysOnFJu9_dSAdT4CA>
Subject: [Anima] anima - Requested session has been scheduled for IETF 108
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, 03 Jul 2020 00:21:48 -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 (1:40 requested)
    Thursday, 30 July 2020, Session I 1100-1240
    Room Name: Room 3 size: 3
    ---------------------------------------------


iCalendar: https://datatracker.ietf.org/meeting/108/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):  100 Minutes
Number of Attendees: 60
Conflicts to Avoid: 
 Chair Conflict: bier pim mboned 6man 6lo 6tisch ace
 Technology Overlap: emu netconf homenet roll
 Key Participant Conflict: nmrg panrg dinrg opsarea intarea saag cfrg detnet





People who must be present:
  Toerless T. Eckert
  Sheng Jiang
  Robert Wilton

Resources Requested:

Special Requests:
  
---------------------------------------------------------



From nobody Fri Jul  3 01:53:17 2020
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 90AD13A0ADC; Fri,  3 Jul 2020 01:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 ZaD4jVsxgSH9; Fri,  3 Jul 2020 01:53:14 -0700 (PDT)
Received: from gw-eagle1.siemens.com (gw-eagle1.siemens.com [194.138.20.72]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24A8F3A0AD8; Fri,  3 Jul 2020 01:53:14 -0700 (PDT)
Received: from mail1.dc4ca.siemens.de (mail1.dc4ca.siemens.de [139.25.224.78]) by gw-eagle1.siemens.com (Postfix) with ESMTPS id 536B64F0053; Fri,  3 Jul 2020 10:53:12 +0200 (CEST)
Received: from DEMCHDC89ZA.ad011.siemens.net (demchdc89za.ad011.siemens.net [139.25.226.105]) by mail1.dc4ca.siemens.de (Postfix) with ESMTPS id 011A0157C2F3A; Fri,  3 Jul 2020 10:53:10 +0200 (CEST)
Received: from DEMCHDC8A1A.ad011.siemens.net (139.25.226.107) by DEMCHDC89ZA.ad011.siemens.net (139.25.226.105) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Fri, 3 Jul 2020 10:53:10 +0200
Received: from DEMCHDC8A1A.ad011.siemens.net ([139.25.226.107]) by DEMCHDC8A1A.ad011.siemens.net ([139.25.226.107]) with mapi id 15.01.1979.003;  Fri, 3 Jul 2020 10:53:10 +0200
From: "Fries, Steffen" <steffen.fries@siemens.com>
To: Toerless Eckert <tte@cs.fau.de>, "anima@ietf.org" <anima@ietf.org>
CC: "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "Rob Wilton (rwilton)" <rwilton@cisco.com>, "housley@vigilsec.com" <housley@vigilsec.com>
Thread-Topic: [Anima] ANIMA-WG: pls chime in: early allocation for otherName code points (draft-ietf-anima-autonomic-control-plane)
Thread-Index: AQHWUHTLWqNXoLGQ9kirevsjZmJYvqj1i/2g
Date: Fri, 3 Jul 2020 08:53:10 +0000
Message-ID: <c77c9966be17425bb12813a4fe7527c6@siemens.com>
References: <20200702132922.GA11404@faui48f.informatik.uni-erlangen.de>
In-Reply-To: <20200702132922.GA11404@faui48f.informatik.uni-erlangen.de>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [144.145.220.66]
x-tm-snts-smtp: 622BE8CDDD860C5B4BDEA66DE7DDE97E698F7E96F9C2D89045652DD09AA37AC92000:8
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/OOTa5x1PPP5PUO5pGT-ztlGoPIU>
Subject: Re: [Anima] ANIMA-WG: pls chime in: early allocation for otherName code points (draft-ietf-anima-autonomic-control-plane)
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, 03 Jul 2020 08:53:16 -0000

+1=20

I consider going with otherNames for the ACP domain the safe way. Taking in=
teractions with existing infrastructures into account may lead to potential=
 misinterpretations of using other fields as the discussion has shown. Havi=
ng a distinct allocation is more clear.=20

Best regards
Steffen

> -----Original Message-----
> From: Anima <anima-bounces@ietf.org> On Behalf Of Toerless Eckert
> Sent: Donnerstag, 2. Juli 2020 15:29
> To: anima@ietf.org
> Cc: anima-chairs@ietf.org; Rob Wilton (rwilton) <rwilton@cisco.com>;
> housley@vigilsec.com
> Subject: [Anima] ANIMA-WG: pls chime in: early allocation for otherName
> code points (draft-ietf-anima-autonomic-control-plane)
>=20
> Dear WG (ACP author head/hat on)
>=20
> ACP Revision -26 introduced a new otherName / AcpNodeName encoding
> for the ACP Domain Information (now call AcpNodeName / acp-node-name).
> Michael Richardson (and potentially other) implementors would like to
> update implementation to use this new encoding for interop testing, which
> requires allocation of two IANA code points (technically i think only one=
 is
> required for the implementation, but the toolchain would require both if =
i
> understand it correctly).
>=20
> The early allocation process RFC7120 requires to vet the community for
> interest in the early allocation, so pls. chime in with a +1, or if you m=
ust a -1
> and explanation.
>=20
> I'll do a +1 from the authors side.
>=20
> The remaining requirements of RFC7120 for early allocations are AFAIK met=
.
>=20
> Thanks!
>     Toerless
>=20
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima


From nobody Fri Jul  3 06:16:15 2020
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 9BDCB3A0AFE; Fri,  3 Jul 2020 06:16:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 xkG8JudB6pTZ; Fri,  3 Jul 2020 06:16:12 -0700 (PDT)
Received: from gw-eagle1.siemens.com (gw-eagle1.siemens.com [194.138.20.72]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA6053A0AFD; Fri,  3 Jul 2020 06:16:11 -0700 (PDT)
Received: from mail2.dc4ca.siemens.de (mail2.dc4ca.siemens.de [139.25.224.94]) by gw-eagle1.siemens.com (Postfix) with ESMTPS id 0A00D4F0078; Fri,  3 Jul 2020 15:16:08 +0200 (CEST)
Received: from DEMCHDC89XA.ad011.siemens.net (demchdc89xa.ad011.siemens.net [139.25.226.103]) by mail2.dc4ca.siemens.de (Postfix) with ESMTPS id E2F0714BE9AFE; Fri,  3 Jul 2020 15:16:07 +0200 (CEST)
Received: from DEMCHDC8A1A.ad011.siemens.net (139.25.226.107) by DEMCHDC89XA.ad011.siemens.net (139.25.226.103) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Fri, 3 Jul 2020 15:16:07 +0200
Received: from DEMCHDC8A1A.ad011.siemens.net ([139.25.226.107]) by DEMCHDC8A1A.ad011.siemens.net ([139.25.226.107]) with mapi id 15.01.1979.003;  Fri, 3 Jul 2020 15:16:07 +0200
From: "Fries, Steffen" <steffen.fries@siemens.com>
To: Sheng Jiang <jiangsheng@huawei.com>, Anima WG <anima@ietf.org>
CC: "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "Rob Wilton (rwilton)" <rwilton@cisco.com>
Thread-Topic: Adoption call for draft-fries-anima-brski-async-enroll-03, ends July 1st 2020
Thread-Index: AdZFUcOGlfvPowoQSbyiu0kg7sJTWQL6e0+A
Date: Fri, 3 Jul 2020 13:16:07 +0000
Message-ID: <26d3a391695746baa73d44bd3eccf937@siemens.com>
References: <f8c2df730dad489d88303c6d8682caee@huawei.com>
In-Reply-To: <f8c2df730dad489d88303c6d8682caee@huawei.com>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [139.21.146.185]
x-tm-snts-smtp: 8F1FCC17BA9A7260D25395E16D04A68126CE81CCA56FCFDBA4FFDD9891DBD2302000:8
Content-Type: multipart/alternative; boundary="_000_26d3a391695746baa73d44bd3eccf937siemenscom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/0V-Ead_FFmg2nzT9dD5oi1CWURA>
Subject: Re: [Anima] Adoption call for draft-fries-anima-brski-async-enroll-03, ends July 1st 2020
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, 03 Jul 2020 13:16:14 -0000

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

Hello Sheng, hello Toerless,

As the WG adoption call passed, I would like to ask what the next steps are=
?
On the mailing list I saw positive votes and no objection, which is a good =
sin from my understanding.

Please let me know how we proceed, as we plan to provide an update of the d=
raft in the next couple of days.

Best regards
Steffen


From: Anima <anima-bounces@ietf.org> On Behalf Of Sheng Jiang
Sent: Donnerstag, 18. Juni 2020 11:28
To: Anima WG <anima@ietf.org>
Cc: anima-chairs@ietf.org; Rob Wilton (rwilton) <rwilton@cisco.com>
Subject: [Anima] Adoption call for draft-fries-anima-brski-async-enroll-03,=
 ends July 1st 2020

Hi, ANIMAer,


This message starts a two-week adoption call, it ends on July 1st, 2020.



draft-fries-anima-brski-async-enroll-03 has been presented to the WG for a =
long while and the WG showed good interest and had discussions. The draft i=
s now clearly in scope of ANIMA charter 2 that was adopted around IETF106. =
The authors asked for adoption of the document. Giving the dependent BRSKI =
has passed the IESG evaluation, the chairs feel that it may be the right ti=
me to call the adoption.



We therefore are asking the ANIMA working group for adoption of the followi=
ng work:



Title:    Support of asynchronous Enrollment in BRSKI

Name:     draft-fries-anima-brski-async-enroll-03

Authors:  S. Fries, H. Brockhaus and E. Lear

URL:      https://datatracker.ietf.org/doc/draft-fries-anima-brski-async-en=
roll/



This document is intended to become a standards track ANIMA WG document.



Please express your support or rejection. If you think this document should=
 _not_ be adopted, please also explicitly indicate the reasons.



Regards,



Sheng


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@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;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
.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">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hello Sheng, hello Toerless,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">As the WG adoption call passed, I would like to ask =
what the next steps are?
<o:p></o:p></p>
<p class=3D"MsoNormal">On the mailing list I saw positive votes and no obje=
ction, which is a good sin from my understanding.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Please let me know how we proceed, as we plan to pro=
vide an update of the draft in the next couple of days.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best regards<o:p></o:p></p>
<p class=3D"MsoNormal">Steffen <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div 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"><b>From:</b> Anima &lt;anima-bounces@ietf.org&gt; <b=
>On Behalf Of </b>
Sheng Jiang<br>
<b>Sent:</b> Donnerstag, 18. Juni 2020 11:28<br>
<b>To:</b> Anima WG &lt;anima@ietf.org&gt;<br>
<b>Cc:</b> anima-chairs@ietf.org; Rob Wilton (rwilton) &lt;rwilton@cisco.co=
m&gt;<br>
<b>Subject:</b> [Anima] Adoption call for draft-fries-anima-brski-async-enr=
oll-03, ends July 1st 2020<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi, ANIMAer,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">This message starts a two-week adoption call, it en=
ds on July 1st, 2020.<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">draft-fries-anima-brski-async-enroll-03 has been pr=
esented to the WG for a long while and the WG showed good interest and had =
discussions. The draft is now clearly in scope of ANIMA charter 2 that was =
adopted around IETF106. The authors asked for adoption of the document. Giv=
ing the dependent BRSKI has passed the IESG evaluation, the chairs feel tha=
t it may be the right time to call the adoption.<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 therefore are asking the ANIMA working group for=
 adoption of the following work:<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">Title:&nbsp;&nbsp;&nbsp; Support of asynchronous En=
rollment in BRSKI<o:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">Name:&nbsp;&nbsp;&nbsp;&nbsp; draft-fries-anima-brs=
ki-async-enroll-03<o:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">Authors:&nbsp; S. Fries, H. Brockhaus and E. Lear<o=
:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">URL:&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;</span><span sty=
le=3D"color:black"><a href=3D"https://datatracker.ietf.org/doc/draft-fries-=
anima-brski-async-enroll/">https://datatracker.ietf.org/doc/draft-fries-ani=
ma-brski-async-enroll/</a></span><span style=3D"font-size:9.0pt;font-family=
:Consolas;color:#212529"><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">This document is intended to become a standards tra=
ck ANIMA WG document.<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 express your support or rejection. If you th=
ink this document should _not_ be adopted, please also explicitly indicate =
the reasons.<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">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">Sheng<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_26d3a391695746baa73d44bd3eccf937siemenscom_--


From nobody Sat Jul  4 18:00:04 2020
Return-Path: <jmh@joelhalpern.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 987D83A12D8; Sat,  4 Jul 2020 18:00:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 0FabEFsnLmrC; Sat,  4 Jul 2020 18:00:00 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 A5C213A12D7; Sat,  4 Jul 2020 17:59:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 49zr2l3MHKz1ns2W; Sat,  4 Jul 2020 17:59:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1593910799; bh=MAlsCuTurex4AemjxPGz9G8qOAm6UfBT57TGYwa3K9I=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=IHIt5teSLKlyAoOBMZccfLgUp2qA0XyOOPqy7EbVqqxvBN3309B63g1mqJ+jiRbls HKdL90szkU5F4wUjNo194WPjQENrxIS/m2PVmpq4/T9iZqbXDwLnXohTNvJy9dgxmH 7VXzxRAfI+oYPHnm9aW5A/7g6vBqUxLIojU6iSy8=
X-Quarantine-ID: <Hxi0wz5gwXIA>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 49zr2j52G5z1nt7c; Sat,  4 Jul 2020 17:59:57 -0700 (PDT)
To: Toerless Eckert <tte@cs.fau.de>
Cc: rtg-dir@ietf.org, last-call@ietf.org, draft-ietf-anima-autonomic-control-plane.all@ietf.org, anima@ietf.org, evyncke@cisco.com, rwilton@cisco.com
References: <20200624023521.GB41244@faui48f.informatik.uni-erlangen.de>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <565d95b0-8066-d180-0749-e8940819932f@joelhalpern.com>
Date: Sat, 4 Jul 2020 20:59:57 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <20200624023521.GB41244@faui48f.informatik.uni-erlangen.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/pMIkeOTnUyNwdU5W9MFOecIkclo>
Subject: Re: [Anima] Rtgdir last call review of draft-ietf-anima-autonomic-control-plane-24
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, 05 Jul 2020 01:00:03 -0000

My apologies for the delay in responding to these comments.
The changes seem to nicely address all of my comments.  I hope that I 
will recall this well enough to avoid introducing triple-jeopardy by 
accident.  (Having said that, it appears that my pushing on some of 
these issues a second time contributed to your finding good resolutions 
of the issues.)

On the 7.2 comments, my primary comment was a mistake on my part.  The 
only configuration required is the same configuration that is required 
for ACP nodes, namely turning on ACP.  (Which may or may not be a 
default setting, but is clearly a configurable behavior.)

On the comment about a corner case, I was looking for text saying 
roughly "An L2 node that supports ACP and is enabled to participate 
SHOULD do so on all its L2 interfaces.  I grant this is not a big deal. 
My concern is if the L2 link selection is a partial / proper subset of 
the intended L3 adjacencies, problems could easily result due to traffic 
not arriving at all desired places.

Thank you,
Joel

On 6/23/2020 10:35 PM, Toerless Eckert wrote:
> Thanks a lot, Joel
> 
> Personal diff with just the fixes for you, otherwise feel free to compare -25 against
> -25, it has more fixes for Russ Housley and IPsec proto detail enhancements/fixes.
> 
> http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://raw.githubusercontent.com/anima-wg/autonomic-control-plane/0caa400fd1c554ece49fddc7dabe8140195aa5bf/draft-ietf-anima-autonomic-control-plane/draft-ietf-anima-autonomic-control-plane.txt&url2=https://raw.githubusercontent.com/anima-wg/autonomic-control-plane/ae9e6cd856ab2706e8b38cc2552f2e77f6b676a5/draft-ietf-anima-autonomic-control-plane/draft-ietf-anima-autonomic-control-plane.txt
> 
> Cheers
>      toerless
> 
> On Thu, Apr 09, 2020 at 07:16:16PM -0700, Joel Halpern via Datatracker wrote:
>> Reviewer: Joel Halpern
>> Review result: Not Ready
>>
>> Hello,
>>
>> I have been selected as the Routing Directorate reviewer for this draft. The
>> Routing Directorate seeks to review all routing or routing-related drafts as
>> they pass through IETF last call and IESG review, and sometimes on special
>> request. The purpose of the review is to provide assistance to the Routing ADs.
>> For more information about the Routing Directorate, please see
>> ???http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir
>>
>> Although these comments are primarily for the use of the Routing ADs, it would
>> be helpful if you could consider them along with any other IETF Last Call
>> comments that you receive, and strive to resolve them through discussion or by
>> updating the draft.
>>
>> Document: draft-ietf-anima-autonomic-control-plane-24.txt
>> Reviewer: Joel Halpern
>> Review Date: 9-April-2020
>> IETF LC End Date: N/A
>> Intended Status: Proposed Standard
>>
>> Summary:
>>      I have two major concern about this document that I think should be
>>      resolved before publication.  The are also a number of minor items that
>>      warrant attention.
>>
>> Comments:
>>
>> While quite long, the draft is significantly improved from earlier versions.
>> It does provide significant explanation of its design choices, which is helpful
>> and appreciated.  Sometimes this seems to end up more as marketing or promotion
>> instead of explanation, but this is mostly harmless.
> 
> Any pointers to specific text that sounds to be too marketing wise
> always welcome. Happy to review that. I thought i had eliminated all
> the ones... i did see myself.
> 
>> In particular, I would like to thank the authors and editors for the addition
>> of section 9.3 and its careful discussion of the many issues there.
> 
> Thank you.
> 
>> Major Issues:
>>
>>      Section 6.10.3.1 on the use of Zone-IDs seems, from the material in A.10.1,
>>      to be dependent upon either configuration (which ACP is supposed to avoid)
>>      or completely unspecified magic.  Having an addressing and routing scheme
>>      standardized that is impossible to use seems at variance with appropriate
>>      practice.  It would be fine to say that provision is made for non-zero
>>      Zone-IDs in the hope that future work can find ways to scale further using
>>      this.  But pretending it is well-defined, but not actually defining it,
>>      seems unacceptable.
> 
> You brought up this issue in your -13 review and we had a longer thread about
> it which ended in i think this statement of yours:
> 
> | <8d2d0b06-0982-53a3-0ce0-38a465f58bed@joelhalpern.com>
> | My perspective is that I would have preferred to see the system designed such
> | that when Zones are needed, they can be added in a way that does not assume
> | system-wide knowledge of the layout choices.
> |
> | I think you could have achieved that.  I understand that the working group
> | didn't do that.  And beause it is the WG decision, I can live with it.  I wish
> | it were better.
> 
> No protection against double jeopardy in IETF ?
> Maybe its a good thing except for expediency of completion of the draft,
> because i had to rethink the issue again, and while it took a while i
> hope the result is especially good to help with initial ACP adoption
> challenges:
> 
> The included text in the discussion up to -24 is now also in my opinion not very
> useful, it also had technical issues.
> The core issue that was combination of your ask for complete removal
> of the ACP zone address scheme and the (bad) solution of attempting to guess
> at a future way how to provide the final full benefits for the zone address
> scheme in 6.10.3.1. And that guesswork in 6.10.3.1 was not good, which is
> why 6.10.3.1 is now gone in -25.
> 
> [Side note: I think i have the zone solution for a future RFC kinda worked out:
> we would have some manual or autonomic zone edges, grasp announcements within each
> zone announcing the Zone-ID and then nodes with ACP-Zone addresses that
> attach into a zone would update the Zone-ID of their ACP address accordingly.
> E-voila: zone-mobility by updating the zone-id field]
> 
> However, the main disconnect was that this longer term goal alone is not
>   good reason to keep Zone-ID. Instead the main reason to keep it was and is
> the ability to support better partial and incremental adoption of ACP,
> and for that one we do actually have good pre-standard implementation
> experience.
> 
> But i didn't want this in the normative part of the spec, and i either
> didn't get the idea that it could go into the operational part (section 9),
> or i felt such text would be too difficult or too much subject to additional
> review attacks.
> 
> But given how i think it is really an important option for initial
> deployments of ACP in large networks, i finally wrote that, it is
> now a new section 9.4. Pls check it out.
> 
>>      Section 6.12.5.1 on loopback interface is factually wrong.
>>      It conflates one particular form of loopback interface with
>>      the definition of loopback interfaces.
>>
>>      This also leads to the error in the definition section (see
>>      minor comment below).
> 
> Let me move this here so we can have a cohesive discussion about that section.
> 
>>      6.12.5.1 refers to the ACP addresses as node addresses.  Technically, the
>>      IPv6 architecture requires that all addresses are associated with
>>      interfaces rather than nodes.  I would prefer that this draft not
>>      needlessly claim to violate that.
> 
> In practice the term node address is often used, maybe less
> in RFC, but more in practice. And its often done
> interchangably with loopback addresses because without changing
> the actual IPv6 functionality, loopback interfaces are the
> main way to achieve the function operators typically associate
> with a node address.
> 
> Be that as it may, i have tried to end the rewrite of the section
> with a paragraph that is trying to bring the use of the word "Node"
> in-line with the way RFC8402 does it.
> 
>>     (Loopback Interfaces were used long before RFC 4291,
> 
> Yepp, was just bad english to connect something that was meant to be
> read in he context of IPv4 with an example about IPv6.
> 
>>      and on routers were often used for external communication.  This was itself
>>      a repurposing of the original loopback interface, 127.0.0.1, which was
>>      indeed for internal use.)
> 
> Yepp.
> 
> So, i ended up rewriting the whole section also because EricV asked
> in his review earlier this year if it would not be better to use a new
> term instead of loopback.
> 
> Whe i reviewed existing normaive references it became clear to me that
> loopback is actually a very good logical name for the function we
> need for addresses we want to behave as what non-dogmatic people
> would call a node address. So i hope the explanation in the new
> text for loopback to well justify the naming choice.
> 
> I have also added a bullet list for justifying the loopback address
> use. Really nothing new, but common operational practice, alas, i
> wasn't able to find a list like this in other docs and this
> is an ongoing reason for questions from readers of ACP that do not
> have a background in running IP router networks.
> 
> So hopefully, while this point too took me a lot of time to
> rewrite, it is all for the better.
> 
>> Minor Issues:
>>
>>     It seems distinctly unfortunate that the definition for Data Plane in
>>     section 2 explicitly states that this definition is different from that used
>>     in other work, including other routing work.  This seems a recipe for both
>>     confusion and mis-communication among technologists.
> 
> Actually, IMHO the term data-plane has always been badly defined in the
> face of the inline-signaling model of IP networks. Are IGP/BGP signaling
> packets data-plane or control-plane ? How about routers connecting via
> L2 unbeknownst to them and their STP packets ? Even if you have an
> opininon, do you have a normative RFC to support your definition ?
> What is the difference between data and forwarding plane ?
> 
> Don't answer... rethoric questions...
> 
> I have replaced two existing paragraphs in the intro with the following
> text that explains the terminology better and shows how in the vision
> of autonomic networks the term is very logical, and that it is just
> existing non-autonomous networks in which there is more to the data-plane
> than what you might expect, but i think that is perfectly fine, especially
> when considering the layering example from above, where one layers (L2, ethernet)
> control and forwarding plane are just considered to be part of a higher layers
> data-plane.
> 
> New text:
> <t>In a fully autonomic network node without legacy control or management functions/protocols, the Data-Plane would be for example just a forwarding plane for "Data" IPv6 packets, aka: packets that are not forwarded by the ACP itself because they are control or management plane packets. In such networks/nodes, there would be no non-autonomous control or non-autonomous management plane. Routing protocols for example would be built inside the ACP as so-called autonomous functions via autonomous service agents, leveraging the ACPs functions instead of implementing them seperately for each protocol: discovery, automaticically established authenticated and encrypted local and distant peer connectivity for control and managemenet traffic and common control/management protocol session and presentation functions.</t>
> 
> <t>When the ACP is added to henceforth so-called non-autonomous nodes that have non-autonomous management plane and/or control plane functions, the ACP instead is best abstracted as a special Virtual Routing and Forwarding (VRF) instance (or virtual router) and the complete pre-existing non-autonomous management and/or control plane is considered to be part of the Data-Plane to avoid introduction of more complex, new terminology only for this case. Like the forwarding plane for "Data" packets, the non-autonomous control and management plane functions can then be managed/used via the ACP. This terminology is consistent with pre-existing documents such as <xref target="RFC8368">"/>.</t>
> 
> <t>In both instances (autonomous and non-autonomous nodes), the ACP is built such that it is operating in the absene of the Data-Plane, and in the case of existing non-autonomous (management, control) components in the Data-Plane also in th
> e presence of any (mis-)configuration thereof.</t>
> /New text
> 
>>     In the definition of in-band management in section 2, please remove the
>>     commentary text on putative fragility.   (I actually agree it has some
>>     fragility.  The discussion does not belong here.  This is a definition.)
>>     The promotional material may be warranted, if jarring, in other parts of the
>>     documents.  Not in the definitions please.
> 
> Ok, i stripped down explanatory text for out-of-band network in terminology
> and instead pimped what you would call "marketing" about it in the introduction section. Easy to find in diff.
> 
> Always happy to get explicit suggestions for how to reduce what you think
> is "jarring". The ability of ACP to even avoid a single case of sending
> out a tech person to a remote site due to misconfigurations is IMHO
> the bigest single use-case benefit in talks with customers, so i think it deserves
> good factual representation and i can not see where the text goes beyond
> that. I am happy if any positive pitching is called "marketing", but
> i definitely do not want anything to be "jarring".
> 
>>      The definition of a loopback interface in section 2 is wrong.  It claims
>>      that loopbacks transmit no external traffic.   They send and receive lots
>>      of external traffic.  They merely do so by forwarding the traffic
>>      internally to other interfaces.  The traffic is external.  The particular
>>      step of the transmission, if implemented naively, is internal.
> 
> Fixed.
> 
>>      If we are going to define ACP as a virtual out of band network, I would
>>      suggest separating the terms into two definitions. One for true out  of
>>      band networks (distinct physical links, switches, and ports), and then a
>>      definition for virtual out of band network which describes the ACP
>>      approximation which creates independence from configuration, but not
>>      independence from the physical links.
> 
> Done.
> 
> [ Note: I am btw. not worried about the link-sharing as a career limiting move
>    for ACP, as soon as there is sufficient link redundancy (2 links eliminate 99% of issues).
> 
>    The actual HW design of the nodes to maximize ACP value is more interesting.
>    I had slides about that in a research conference workshop some years back, e.g.: applying
>    concepts such as BMC so that you can use the common HW diag functions
>    you typically expect from OOB support. ]
> 
>>      Section 5, bullet 2, talks about a policy as to which peers ACP
>>      communication should be established.  It would be helpful if this gave a
>>      reference or indication as to where such policies would come from.  Given
>>      the emphasis on zero touch, I presume they are not configured on the node?
>>      (This issues was in my review of -13.)
> 
> Original -13 thread here:
> 
> | >>      It is unclear how the flexible policy defined in section 5 bullet 2 (about
> | >>      which nodes are ACP peer candidates) is consistent with autonomic
> | >>      operation.  It seems that the flexibility is important, so there should be
> | >>      some explanation here about how this is consonant with the stated goals.  I
> | >>      understand that the bootstrap comes from BRSKI, but I do not think that is
> | >>      where the policy comes from?
> | >
> | > Would rather not like to add more suggestive text, and thats at best what
> | > i could add. The default policy is the best "autonomic" behavior we know how
> | > to make work: aka: try to connect ACP to all neighbors you can discover. And
> | > we have only defined with DULL GRASP how to find subnet adjacent neighbors.
> | >
> | > The main reason to mention policy is so that there is some leeway to do
> | > more or even (sigh) less than all direct neighbors.
> 
> Double jeopardy ?
> 
> I actually did not bother to fix up the intro section since taking the editor pen
> from Michael. I had kept the "policy" in there as a reminder of Intent to be
> done in the future, but given how we deprioritized
> intent in charter, i felt more happy now than during 13 to fix this.
> 
> Alas, it turns out i also found other points in the overview lacking
> clarity and consistency with the normative sections, so the changes
> here got larger, but hopefully all for the better. Please check.
> 
>>      Bullet 4 of section 6.1.3 on checking certificates against the CRL / OCSP
>>      would seem to be better reworded.  I believe the intended requirements i
>>      that IF there is ACP connectivity to the CRL / OCSP source, then it should
>>      be verified.  But that absence of such connectivity should not prevent
>>      association formation.  (As, if I have read it wright, otherwise we could
>>      deadlock the startup process.)
> 
> Pls. check the full diff vs. -24 for this, because that fix is in the commit i did for
> Russ Housley before i worked on your review. If you don't like that text either, pls
> suggest better wording, its a bit of a tricky language problem i think, which a native
> speaker might master easier.
> 
>>      In the example in section 6.5 on Channel selection, in steps 7:C1 and
>>      11:C2, Node 1 concludes that it is Bob.  However, in steps 12 and 13, the
>>      text refers to Node1 (Alice).  This seems inconsistent.
> 
> Yikes. How could that have slipped me. Thanks a lot.
>>
>>      Section 6.7.1 makes an assertion about the lack of need for MTI of security
>>      mechanisms.  The earlier explanation was well done and seems sound.  This
>>      shorter one seems wrong, since without MTI there is no good way to know
>>      what ones neighbors may implement.  I suggest simply removing this text and
>>      replacing it with a backwards reference to the earlier description.  (The
>>      rest of the section is useful and clear.)
> 
> Done.
> 
>>      In 6.10.3,  ACP Zone Addressing Sub-Scheme, the text claims that when zone
>>      IDs of 0 are used, the addresses are identifiers, and when non-zero IDs
>>      aere used, they are locators.  Since in either case the addresses are used
>>      for packet forwarding, and the addressing information is propagated in the
>>      routing protocol (RPL), this seems to be a misuse of the locator /
>>      identifier distinction.  And a misuse for no purpose as the distinction is
>>      not relevant to the document.  (This odd use of "identifier continues in
>>      section 6.10.3.1.  Identifier is not a synonym of "flat".  Just say "flat".)
> 
> Hey, i didn't come up with all this confusing an probably wrong understanding
> of locator or identifier, i just fell into the trap of trying to use these terms ;-))
> 
> This is removed now. Hope i found all places. Only locartors left should be
> about GRASP.
> 
> Is there even any agreed upon distinction ? To me, identifier/locator are just
> two roles an address can have based on who is using it for what purpose.
> They're not exclusive to each other IMHO.
> 
>>      The assertion about looping packets in the later portion of 6.11.1.1 is
>>      over-stated.  There are other routing protocols that avoid looping-till-ttl
>>      without changing the data plane header.
> 
>>      I suggest removing the gratuitous     comparison with other routing protocols.
> 
> Well... it was IMHO not gratuitous, it was just bad text.
> 
> The intent was not to make the solution sound better than other routing protocols,
> but rather to explain how it is not far worse than other routing protocols given
> the absence of the RPI (RPL Packet Information).
> 
> The text was not good because it only indirectly addressed what
> it intended to describe by just talking about TTL looping. I have replaced this
> paragraph by two paragraphs that hopefully better capture the intent:
> 
> [snip]
>      <t>
>        In RPL profiles where RPL Packet Information (RPI, see <xref target="rpl-Data-Plane"/>)
>        is present, it is also used to trigger reconvergence when misrouted, for example looping, packets
>        are recognized because of their RPI data. This helps to minimize RPL signaling traffic
>        especially in networks without stable topology and slow links.
>      </t>
>        
>      <t>
>        The ACP RPL profile instead relies on quick reconverging the DODAG by
>        recognizing link state change (down/up) and triggering reconvergence signaling
>        as described in <xref target="rpl-dodag-repair"/>.  Since links in the ACP
>        are assumed to be mostly reliable (or have link layer protection against loss)
>        and because there is no stretch according to <xref target="rpl-dodag-repair"/>,
>        loops caused by loss of RPL routing protocol signaling packets should be exceedingly rare.</t>
>      </t>
> [/snip]
> 
> Hope this is an adequate answer to close this point.
> 
> I now have no text about TTL expiry because that is a difficult qualitative
> comparison for which there is IMHO not enough data on evidence: The
> reconvergence with RPL in the ACP profile may be somewhat slower than
> the most common sub-50 msec LFA in SP networks or subsecond SPF-IGP
> fast convergence common in most other networks in scope of ACP ("well manageg,
> aka: private enterprise etc. networks), but the total amount of traffic
> across the ACP will likely be orders of magnitude less than that on the
> Data Plane where the SPF-IGP runs.
> 
> I think convergence with the profile should be 50 msec (link change discovery
> plus O(max-pathlength) * per-node RPL processing latency, but i think
> this is too much analysis for a spec, so no text.
> 
>>      Section 7.2 (L2 DULL GRASP) seems to be doing something quite useful.  I
>>      think I see how it would work.  The need for some configuration on some
>>      switches seems inevitable and acceptable.
> 
> Hmm.. there is no intent to require configuration. What specifically
> do you think of ?
> 
> The goal is really to support ACP in complete L2-only networks, except that
> the ACP itself is of course L3.
> 
> One core part of the text is explaining how ACP can be supported
> on the most limited L2 hardware where it can work. Aka: withough changing
> the actual L2 HW forwarding, but just by punting GRASP packets so they
> are not flooded by L2.
> 
>>      I think there is one corner
>>      case that should be avoided, as it seems likely to create significant
>>      complexity for little or no benefit.  It seems to me that a switch that is
>>      capable of participating in the ACP should either participate in the ACP on
>>      all its physical ports, or should not participate in the ACP at all.  I
>>      would not be surprised if that was the WG intent.  But I could not find the
>>      text that says this.  (Apologies if it is there and I missed it.)
> 
> Not sure why you specifically think this is an issue for devices
> operating at L2.
> 
> I have seen all type of weird problems. For example: How do you
> enable autodiscovery of ACP neighbors across the 10Gbps backbone
> interfaces of a router/switch for broadband if those interfaces
> are initially disabled by software because the user is expected
> to first enter an additional license key to use those interfaces....
> 
> Sorry, randomn example. Maybe rephrase your point with an example
> why you think it deserve additional text ? Suggest additional text ?
> 
>>
>>      Section 9 starts by saying it is informational.  But the first paragraph
>>      says that some of the content is "necessary" for correct operation.  Thus,
>>      it seems that some of the content is normative?   (I am not sure, but I
>>      think the "necessary" material relates to what is needed to be a registrar?)
> 
> The first paragraph does not say "correct operation", and i think
> to remember that i word smithed that paragraph quite
> a bit to walk the thin line: you can not build an ACP without
> understanding this section and follow its advice to
> the extend you deem appropriate or feasible, but we can also not
> normatively standardize what is in this section.
> 
> Some things will hopefully gt standardized via future
> yang model RFC. That stuff is just not standardized beause
> it does not meet the formal bar.
> 
> Most of the stuff is talking about variety of options
> deemed to be necessary or beneficial in various
> situations. Doing even the Yang stuff for the subset
> people will agree to is a lot of work.
> 
> protecting the ACP from operator
> misconfiguration is IMHO necessary. I wouldn't even dare
> to begin guessing what details could get standardized for
> that. Yang models for new interface states would certainly
> be another 5++ year discusion in IETF. better to start
> these things with vendor proprietary Yang models and learn.
> 
> I know from personal experience that you can not successfully
> deploy without humunguous amount of diagnostic as long as
> you have buggy implementations, especially when fitting
> into exising router OS, incurring a lot of unforeseen
> limitations. Very difficult to standardize because its
> all about interaction with the non-autonomic stuff unless
> you can severely isolate ACP in your platform design.
> 
> If you do not understand the discussions about registrars,
> you will have a hard time getting a working support
> backend system for the registars.
> 
> Aka: necessary does not mean standardizable.
> 
>> Nits:
>>      The second and third paragraphs of section 6.11.1.1 on RPL start with
>>      duplicated text, and then go on to say different (complementary) things.
>>      There is no need for the repetition.
> 
> Right. I reworked the overview to remove duplicates, also structured
> into two subsections to highlight the two key themes of the profile
> (single instance and convergence).
> 
>>      The rank factor in 6.11.1.6 of 100 megabits as the boundary seems a fairly
>>      arbitrary choice.  It may be that an arbitrary choice was needed.  Could
>>      something be said?  In particular, if someone looks at this 5 years from
>>      now, it may seem quite confusing.
> 
> In german, rule of thumb is called "pi times thumb", obviously much more
> accurate than just thumb ;-)
> 
> I added the following paragraph:
> 
>          <t>This is a simple rank differentiation between typical "low speed"
>          or "IoT" links that commonly max out at 100 Mbps and typical
>          infrastructure links with speeds of 1 Gbps or higher. Given how
>          the path selection for the ACP focusses only on reachability but
>          not on path cost optimization, no attempts at finer grained path
>          optimization are made. </t>
> 
> Heard a nice summary about the new ieee work about the future of 10 Mbps
> ethernet over twisted pair, so i think the cut point at 100 Mbps
> may actually be quite a good one. aka: with just two values i don't
> know how we could do better.
> 
> Aain, thanks a lot for the review.
> 
> Toerless
> 


From nobody Sun Jul  5 18:37:05 2020
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 D9B783A0D35; Sun,  5 Jul 2020 18:37:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, 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 Fc-2JwqkC-iT; Sun,  5 Jul 2020 18:37:02 -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 DDF113A0D34; Sun,  5 Jul 2020 18:37:01 -0700 (PDT)
Received: from lhreml727-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 7A8DCAA1FDA99BFEAE37; Mon,  6 Jul 2020 02:36:59 +0100 (IST)
Received: from nkgeml705-chm.china.huawei.com (10.98.57.154) by lhreml727-chm.china.huawei.com (10.201.108.78) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 6 Jul 2020 02:36:58 +0100
Received: from nkgeml708-chm.china.huawei.com (10.98.57.160) by nkgeml705-chm.china.huawei.com (10.98.57.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 6 Jul 2020 09:36:56 +0800
Received: from nkgeml708-chm.china.huawei.com ([10.98.57.160]) by nkgeml708-chm.china.huawei.com ([10.98.57.160]) with mapi id 15.01.1913.007; Mon, 6 Jul 2020 09:36:56 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Anima WG <anima@ietf.org>, "draft-fries-anima-brski-async-enroll@ietf.org" <draft-fries-anima-brski-async-enroll@ietf.org>
CC: "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "Rob Wilton (rwilton)" <rwilton@cisco.com>, Toerless Eckert <tte@cs.fau.de>
Thread-Topic: Result//RE: Adoption call for draft-fries-anima-brski-async-enroll-03, ends July 1st 2020
Thread-Index: AdZTNUHiWNwtHKUuTIOyxr7F47dsig==
Date: Mon, 6 Jul 2020 01:36:56 +0000
Message-ID: <546cd06329ef4a37b14d2948130a383c@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.108.235.253]
Content-Type: multipart/alternative; boundary="_000_546cd06329ef4a37b14d2948130a383chuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/tomDQKOgf5IrBPGkp529ZdQqjcQ>
Subject: [Anima] Result//RE: Adoption call for draft-fries-anima-brski-async-enroll-03, ends July 1st 2020
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, 06 Jul 2020 01:37:04 -0000

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

Hi, ANIMAer,

We have received supports for this adoption and has no objection. Consequen=
tly, the chairs consider the documents pass the adoption call. The authors =
shall resubmit this document with draft-ietf-anima-*, and the chairs shall =
approve it. The authors please continue to refine the document and invoke W=
G discussion.

Thanks and regards,

Sheng

From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Sheng Jiang
Sent: Thursday, June 18, 2020 5:28 PM
To: Anima WG <anima@ietf.org>
Cc: anima-chairs@ietf.org; Rob Wilton (rwilton) <rwilton@cisco.com>
Subject: [Anima] Adoption call for draft-fries-anima-brski-async-enroll-03,=
 ends July 1st 2020

Hi, ANIMAer,


This message starts a two-week adoption call, it ends on July 1st, 2020.



draft-fries-anima-brski-async-enroll-03 has been presented to the WG for a =
long while and the WG showed good interest and had discussions. The draft i=
s now clearly in scope of ANIMA charter 2 that was adopted around IETF106. =
The authors asked for adoption of the document. Giving the dependent BRSKI =
has passed the IESG evaluation, the chairs feel that it may be the right ti=
me to call the adoption.



We therefore are asking the ANIMA working group for adoption of the followi=
ng work:



Title:    Support of asynchronous Enrollment in BRSKI

Name:     draft-fries-anima-brski-async-enroll-03

Authors:  S. Fries, H. Brockhaus and E. Lear

URL:      https://datatracker.ietf.org/doc/draft-fries-anima-brski-async-en=
roll/



This document is intended to become a standards track ANIMA WG document.



Please express your support or rejection. If you think this document should=
 _not_ be adopted, please also explicitly indicate the reasons.



Regards,



Sheng


--_000_546cd06329ef4a37b14d2948130a383chuaweicom_
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: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;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML \9884\8BBE\683C\5F0F Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
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:"Courier New";}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle20
	{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">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi, ANIMAer,<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">We have received suppo=
rts for this adoption and has no objection. Consequently, the chairs consid=
er the documents pass the adoption call. The authors shall resubmit this do=
cument with draft-ietf-anima-*, and
 the chairs shall approve it. The authors please continue to refine the doc=
ument and invoke WG discussion.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks and regards,<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Sheng<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></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"><b>From:</b> Anima [mailto:anima-bounces@ietf.org] <=
b>On Behalf Of
</b>Sheng Jiang<br>
<b>Sent:</b> Thursday, June 18, 2020 5:28 PM<br>
<b>To:</b> Anima WG &lt;anima@ietf.org&gt;<br>
<b>Cc:</b> anima-chairs@ietf.org; Rob Wilton (rwilton) &lt;rwilton@cisco.co=
m&gt;<br>
<b>Subject:</b> [Anima] Adoption call for draft-fries-anima-brski-async-enr=
oll-03, ends July 1st 2020<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi, ANIMAer,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">This message starts a two-week adoption call, it en=
ds on July 1st, 2020.<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">draft-fries-anima-brski-async-enroll-03 has been pr=
esented to the WG for a long while and the WG showed good interest and had =
discussions. The draft is now clearly in scope of ANIMA charter 2 that was =
adopted around IETF106. The authors asked for adoption of the document. Giv=
ing the dependent BRSKI has passed the IESG evaluation, the chairs feel tha=
t it may be the right time to call the adoption.<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 therefore are asking the ANIMA working group for=
 adoption of the following work:<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">Title:&nbsp;&nbsp;&nbsp; Support of asynchronous En=
rollment in BRSKI<o:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">Name:&nbsp;&nbsp;&nbsp;&nbsp; draft-fries-anima-brs=
ki-async-enroll-03<o:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">Authors:&nbsp; S. Fries, H. Brockhaus and E. Lear<o=
:p></o:p></span></pre>
<pre style=3D"background:white"><span style=3D"font-size:9.0pt;font-family:=
Consolas;color:#212529">URL:&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;</span><a href=
=3D"https://datatracker.ietf.org/doc/draft-fries-anima-brski-async-enroll/"=
>https://datatracker.ietf.org/doc/draft-fries-anima-brski-async-enroll/</a>=
<span style=3D"font-size:9.0pt;font-family:Consolas;color:#212529"><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">This document is intended to become a standards tra=
ck ANIMA WG document.<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 express your support or rejection. If you th=
ink this document should _not_ be adopted, please also explicitly indicate =
the reasons.<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">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">Sheng<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_546cd06329ef4a37b14d2948130a383chuaweicom_--


From nobody Mon Jul  6 00:07:38 2020
Return-Path: <noreply@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 4121E3A08B7; Mon,  6 Jul 2020 00:07:36 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Sheng Jiang via Datatracker <noreply@ietf.org>
To: <rwilton@cisco.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.7.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: jiangsheng@huawei.com, anima-chairs@ietf.org, Sheng Jiang <jiangsheng@huawei.com>, iesg-secretary@ietf.org, anima@ietf.org
Message-ID: <159401925624.11282.3956020372824732239@ietfa.amsl.com>
Date: Mon, 06 Jul 2020 00:07:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/36vSYnK2V9KzmSqzhmPiJiddDc0>
Subject: [Anima] Publication has been requested for draft-ietf-anima-grasp-api-06
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, 06 Jul 2020 07:07:36 -0000

Sheng Jiang has requested publication of draft-ietf-anima-grasp-api-06 as Informational on behalf of the ANIMA working group.

Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-anima-grasp-api/



From nobody Mon Jul  6 09:14:33 2020
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 BBDBF3A17E7 for <anima@ietfa.amsl.com>; Mon,  6 Jul 2020 09:14:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level: 
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, 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 UVCvLm0I4vPm for <anima@ietfa.amsl.com>; Mon,  6 Jul 2020 09:14: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 ADC653A17B5 for <anima@ietf.org>; Mon,  6 Jul 2020 09:13:58 -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 CF016548068; Mon,  6 Jul 2020 18:13:52 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id C8406440043; Mon,  6 Jul 2020 18:13:52 +0200 (CEST)
Date: Mon, 6 Jul 2020 18:13:52 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: jiangsheng@huawei.com
Cc: rwilton@cisco.com, warren@kumari.net, anima@ietf.org
Message-ID: <20200706161352.GA12228@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/X3h4AUHg2sMdyatpkZAliOhJEMs>
Subject: [Anima] Sheng: Pls. request AD approval for IANA early allocation of code points for draft-ietf-anima-autonomic-control-plane
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, 06 Jul 2020 16:14:31 -0000

Dear Sheng,

I have tried to whip up below the necessary information for the WG chair to AD approval request
according to RFC7120. As the non-author co-chair, please check if you approve and proceed accordingly.

Thanks
   Toerless (for the authors of draft-ietf-anima-autonomic-control-plane)

---

From: jiangsheng@huawei.com
To: rwilton@cisco.com, warren@kumari.net
Cc: anima@ietf.org
Subject: OPS-ADs: request for IANA early allocation of codepoints for draft-ietf-anima-autonomic-control-plane

Dear Rob, Warren

For the ANIMA chairs, i hereby request your approval according to RFC7120, section 3.1, point 4,
for IANA early allocation of the below described 2 code points to be assigned to
draft-ietf-anima-autonomic-control-plane.

According to RFC7120, section 3.1, point 2, the conditions for early allocation are met.

Code point (1)
 Registry: https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-1.3.6.1.5.5.7.0
 Requested Description: id-mod-anima-acpnodename-2020
 RFC7120, section 2 conditions for early allocation:
  (a) "Specification Required", will be published as RFC
      Expert: Russ Housley
  (b) specification adequately described in 
      draft-ietf-anima-autonomic-control-plane-27, section 6.1.2/6.1.2.1
  (c) Specification is stable:
      No backward compatibility issue introduced by this code-point.
  (d) Request by implementors for interop testing and question to WG
      has determined that there is sufficient interest in the community
      for early allocation.
 No depletion issue in this registry
      

Code point (2)
 Registry: https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-1.3.6.1.5.5.7.8
 Description: id-mod-anima-acpnodename-2020
 Requested Description: id-on-AcpNodeName
  (a) "Specification Required", will be published as RFC
      Expert: Russ Housley
  (b) specification adequately described in 
      draft-ietf-anima-autonomic-control-plane-27, section 6.1.2/6.1.2.1
  (c) Specification is stable: N/A:
      N/A: No prior approved spec for this functionality.
      Prior draft proposed code point (rfc822Name):
      - Not used in production deployments:
      - Rejected by IESG for > 1 year,
      - Backward compatibility undesirable by IESG, WG and draft authors (undesirable complexity).
  (d) Request by implementors for interop testing and question to WG
      has determined that there is sufficient interest in the community
      for early allocation.
 No depletion issue in this registry

For the ANIMA chairs
    Sheng Jiang


From nobody Mon Jul  6 11:29:00 2020
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 D27A73A080F; Mon,  6 Jul 2020 11:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level: 
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, 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 VXOibyvq4ARU; Mon,  6 Jul 2020 11:28:46 -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 D4D213A07F9; Mon,  6 Jul 2020 11:28:45 -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 B2479548442; Mon,  6 Jul 2020 20:28:39 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id A9786440043; Mon,  6 Jul 2020 20:28:39 +0200 (CEST)
Date: Mon, 6 Jul 2020 20:28:39 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: rtg-dir@ietf.org, last-call@ietf.org, draft-ietf-anima-autonomic-control-plane.all@ietf.org, anima@ietf.org, evyncke@cisco.com, rwilton@cisco.com
Message-ID: <20200706182839.GB12228@faui48f.informatik.uni-erlangen.de>
References: <20200624023521.GB41244@faui48f.informatik.uni-erlangen.de> <565d95b0-8066-d180-0749-e8940819932f@joelhalpern.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <565d95b0-8066-d180-0749-e8940819932f@joelhalpern.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/puRA4tvzxzTVwYKyAwvJrPhfKGc>
Subject: Re: [Anima] Rtgdir last call review of draft-ietf-anima-autonomic-control-plane-24
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, 06 Jul 2020 18:28:58 -0000

Thanks, Joel,

Wrt L2: Always good to explicitly suggest text when that's what you're after.

Not sure why i didn't include this sentence. I guess i didn't even had the
idea that one cuold enable/dible ACP separately on different L2 ports ;-)

Cheers
    Toerless

On Sat, Jul 04, 2020 at 08:59:57PM -0400, Joel M. Halpern wrote:
> My apologies for the delay in responding to these comments.
> The changes seem to nicely address all of my comments.  I hope that I will
> recall this well enough to avoid introducing triple-jeopardy by accident.
> (Having said that, it appears that my pushing on some of these issues a
> second time contributed to your finding good resolutions of the issues.)
> 
> On the 7.2 comments, my primary comment was a mistake on my part.  The only
> configuration required is the same configuration that is required for ACP
> nodes, namely turning on ACP.  (Which may or may not be a default setting,
> but is clearly a configurable behavior.)
> 
> On the comment about a corner case, I was looking for text saying roughly
> "An L2 node that supports ACP and is enabled to participate SHOULD do so on
> all its L2 interfaces.  I grant this is not a big deal. My concern is if the
> L2 link selection is a partial / proper subset of the intended L3
> adjacencies, problems could easily result due to traffic not arriving at all
> desired places.
> 
> Thank you,
> Joel
> 
> On 6/23/2020 10:35 PM, Toerless Eckert wrote:
> > Thanks a lot, Joel
> > 
> > Personal diff with just the fixes for you, otherwise feel free to compare -25 against
> > -25, it has more fixes for Russ Housley and IPsec proto detail enhancements/fixes.
> > 
> > http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://raw.githubusercontent.com/anima-wg/autonomic-control-plane/0caa400fd1c554ece49fddc7dabe8140195aa5bf/draft-ietf-anima-autonomic-control-plane/draft-ietf-anima-autonomic-control-plane.txt&url2=https://raw.githubusercontent.com/anima-wg/autonomic-control-plane/ae9e6cd856ab2706e8b38cc2552f2e77f6b676a5/draft-ietf-anima-autonomic-control-plane/draft-ietf-anima-autonomic-control-plane.txt
> > 
> > Cheers
> >      toerless
> > 
> > On Thu, Apr 09, 2020 at 07:16:16PM -0700, Joel Halpern via Datatracker wrote:
> > > Reviewer: Joel Halpern
> > > Review result: Not Ready
> > > 
> > > Hello,
> > > 
> > > I have been selected as the Routing Directorate reviewer for this draft. The
> > > Routing Directorate seeks to review all routing or routing-related drafts as
> > > they pass through IETF last call and IESG review, and sometimes on special
> > > request. The purpose of the review is to provide assistance to the Routing ADs.
> > > For more information about the Routing Directorate, please see
> > > ???http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir
> > > 
> > > Although these comments are primarily for the use of the Routing ADs, it would
> > > be helpful if you could consider them along with any other IETF Last Call
> > > comments that you receive, and strive to resolve them through discussion or by
> > > updating the draft.
> > > 
> > > Document: draft-ietf-anima-autonomic-control-plane-24.txt
> > > Reviewer: Joel Halpern
> > > Review Date: 9-April-2020
> > > IETF LC End Date: N/A
> > > Intended Status: Proposed Standard
> > > 
> > > Summary:
> > >      I have two major concern about this document that I think should be
> > >      resolved before publication.  The are also a number of minor items that
> > >      warrant attention.
> > > 
> > > Comments:
> > > 
> > > While quite long, the draft is significantly improved from earlier versions.
> > > It does provide significant explanation of its design choices, which is helpful
> > > and appreciated.  Sometimes this seems to end up more as marketing or promotion
> > > instead of explanation, but this is mostly harmless.
> > 
> > Any pointers to specific text that sounds to be too marketing wise
> > always welcome. Happy to review that. I thought i had eliminated all
> > the ones... i did see myself.
> > 
> > > In particular, I would like to thank the authors and editors for the addition
> > > of section 9.3 and its careful discussion of the many issues there.
> > 
> > Thank you.
> > 
> > > Major Issues:
> > > 
> > >      Section 6.10.3.1 on the use of Zone-IDs seems, from the material in A.10.1,
> > >      to be dependent upon either configuration (which ACP is supposed to avoid)
> > >      or completely unspecified magic.  Having an addressing and routing scheme
> > >      standardized that is impossible to use seems at variance with appropriate
> > >      practice.  It would be fine to say that provision is made for non-zero
> > >      Zone-IDs in the hope that future work can find ways to scale further using
> > >      this.  But pretending it is well-defined, but not actually defining it,
> > >      seems unacceptable.
> > 
> > You brought up this issue in your -13 review and we had a longer thread about
> > it which ended in i think this statement of yours:
> > 
> > | <8d2d0b06-0982-53a3-0ce0-38a465f58bed@joelhalpern.com>
> > | My perspective is that I would have preferred to see the system designed such
> > | that when Zones are needed, they can be added in a way that does not assume
> > | system-wide knowledge of the layout choices.
> > |
> > | I think you could have achieved that.  I understand that the working group
> > | didn't do that.  And beause it is the WG decision, I can live with it.  I wish
> > | it were better.
> > 
> > No protection against double jeopardy in IETF ?
> > Maybe its a good thing except for expediency of completion of the draft,
> > because i had to rethink the issue again, and while it took a while i
> > hope the result is especially good to help with initial ACP adoption
> > challenges:
> > 
> > The included text in the discussion up to -24 is now also in my opinion not very
> > useful, it also had technical issues.
> > The core issue that was combination of your ask for complete removal
> > of the ACP zone address scheme and the (bad) solution of attempting to guess
> > at a future way how to provide the final full benefits for the zone address
> > scheme in 6.10.3.1. And that guesswork in 6.10.3.1 was not good, which is
> > why 6.10.3.1 is now gone in -25.
> > 
> > [Side note: I think i have the zone solution for a future RFC kinda worked out:
> > we would have some manual or autonomic zone edges, grasp announcements within each
> > zone announcing the Zone-ID and then nodes with ACP-Zone addresses that
> > attach into a zone would update the Zone-ID of their ACP address accordingly.
> > E-voila: zone-mobility by updating the zone-id field]
> > 
> > However, the main disconnect was that this longer term goal alone is not
> >   good reason to keep Zone-ID. Instead the main reason to keep it was and is
> > the ability to support better partial and incremental adoption of ACP,
> > and for that one we do actually have good pre-standard implementation
> > experience.
> > 
> > But i didn't want this in the normative part of the spec, and i either
> > didn't get the idea that it could go into the operational part (section 9),
> > or i felt such text would be too difficult or too much subject to additional
> > review attacks.
> > 
> > But given how i think it is really an important option for initial
> > deployments of ACP in large networks, i finally wrote that, it is
> > now a new section 9.4. Pls check it out.
> > 
> > >      Section 6.12.5.1 on loopback interface is factually wrong.
> > >      It conflates one particular form of loopback interface with
> > >      the definition of loopback interfaces.
> > > 
> > >      This also leads to the error in the definition section (see
> > >      minor comment below).
> > 
> > Let me move this here so we can have a cohesive discussion about that section.
> > 
> > >      6.12.5.1 refers to the ACP addresses as node addresses.  Technically, the
> > >      IPv6 architecture requires that all addresses are associated with
> > >      interfaces rather than nodes.  I would prefer that this draft not
> > >      needlessly claim to violate that.
> > 
> > In practice the term node address is often used, maybe less
> > in RFC, but more in practice. And its often done
> > interchangably with loopback addresses because without changing
> > the actual IPv6 functionality, loopback interfaces are the
> > main way to achieve the function operators typically associate
> > with a node address.
> > 
> > Be that as it may, i have tried to end the rewrite of the section
> > with a paragraph that is trying to bring the use of the word "Node"
> > in-line with the way RFC8402 does it.
> > 
> > >     (Loopback Interfaces were used long before RFC 4291,
> > 
> > Yepp, was just bad english to connect something that was meant to be
> > read in he context of IPv4 with an example about IPv6.
> > 
> > >      and on routers were often used for external communication.  This was itself
> > >      a repurposing of the original loopback interface, 127.0.0.1, which was
> > >      indeed for internal use.)
> > 
> > Yepp.
> > 
> > So, i ended up rewriting the whole section also because EricV asked
> > in his review earlier this year if it would not be better to use a new
> > term instead of loopback.
> > 
> > Whe i reviewed existing normaive references it became clear to me that
> > loopback is actually a very good logical name for the function we
> > need for addresses we want to behave as what non-dogmatic people
> > would call a node address. So i hope the explanation in the new
> > text for loopback to well justify the naming choice.
> > 
> > I have also added a bullet list for justifying the loopback address
> > use. Really nothing new, but common operational practice, alas, i
> > wasn't able to find a list like this in other docs and this
> > is an ongoing reason for questions from readers of ACP that do not
> > have a background in running IP router networks.
> > 
> > So hopefully, while this point too took me a lot of time to
> > rewrite, it is all for the better.
> > 
> > > Minor Issues:
> > > 
> > >     It seems distinctly unfortunate that the definition for Data Plane in
> > >     section 2 explicitly states that this definition is different from that used
> > >     in other work, including other routing work.  This seems a recipe for both
> > >     confusion and mis-communication among technologists.
> > 
> > Actually, IMHO the term data-plane has always been badly defined in the
> > face of the inline-signaling model of IP networks. Are IGP/BGP signaling
> > packets data-plane or control-plane ? How about routers connecting via
> > L2 unbeknownst to them and their STP packets ? Even if you have an
> > opininon, do you have a normative RFC to support your definition ?
> > What is the difference between data and forwarding plane ?
> > 
> > Don't answer... rethoric questions...
> > 
> > I have replaced two existing paragraphs in the intro with the following
> > text that explains the terminology better and shows how in the vision
> > of autonomic networks the term is very logical, and that it is just
> > existing non-autonomous networks in which there is more to the data-plane
> > than what you might expect, but i think that is perfectly fine, especially
> > when considering the layering example from above, where one layers (L2, ethernet)
> > control and forwarding plane are just considered to be part of a higher layers
> > data-plane.
> > 
> > New text:
> > <t>In a fully autonomic network node without legacy control or management functions/protocols, the Data-Plane would be for example just a forwarding plane for "Data" IPv6 packets, aka: packets that are not forwarded by the ACP itself because they are control or management plane packets. In such networks/nodes, there would be no non-autonomous control or non-autonomous management plane. Routing protocols for example would be built inside the ACP as so-called autonomous functions via autonomous service agents, leveraging the ACPs functions instead of implementing them seperately for each protocol: discovery, automaticically established authenticated and encrypted local and distant peer connectivity for control and managemenet traffic and common control/management protocol session and presentation functions.</t>
> > 
> > <t>When the ACP is added to henceforth so-called non-autonomous nodes that have non-autonomous management plane and/or control plane functions, the ACP instead is best abstracted as a special Virtual Routing and Forwarding (VRF) instance (or virtual router) and the complete pre-existing non-autonomous management and/or control plane is considered to be part of the Data-Plane to avoid introduction of more complex, new terminology only for this case. Like the forwarding plane for "Data" packets, the non-autonomous control and management plane functions can then be managed/used via the ACP. This terminology is consistent with pre-existing documents such as <xref target="RFC8368">"/>.</t>
> > 
> > <t>In both instances (autonomous and non-autonomous nodes), the ACP is built such that it is operating in the absene of the Data-Plane, and in the case of existing non-autonomous (management, control) components in the Data-Plane also in th
> > e presence of any (mis-)configuration thereof.</t>
> > /New text
> > 
> > >     In the definition of in-band management in section 2, please remove the
> > >     commentary text on putative fragility.   (I actually agree it has some
> > >     fragility.  The discussion does not belong here.  This is a definition.)
> > >     The promotional material may be warranted, if jarring, in other parts of the
> > >     documents.  Not in the definitions please.
> > 
> > Ok, i stripped down explanatory text for out-of-band network in terminology
> > and instead pimped what you would call "marketing" about it in the introduction section. Easy to find in diff.
> > 
> > Always happy to get explicit suggestions for how to reduce what you think
> > is "jarring". The ability of ACP to even avoid a single case of sending
> > out a tech person to a remote site due to misconfigurations is IMHO
> > the bigest single use-case benefit in talks with customers, so i think it deserves
> > good factual representation and i can not see where the text goes beyond
> > that. I am happy if any positive pitching is called "marketing", but
> > i definitely do not want anything to be "jarring".
> > 
> > >      The definition of a loopback interface in section 2 is wrong.  It claims
> > >      that loopbacks transmit no external traffic.   They send and receive lots
> > >      of external traffic.  They merely do so by forwarding the traffic
> > >      internally to other interfaces.  The traffic is external.  The particular
> > >      step of the transmission, if implemented naively, is internal.
> > 
> > Fixed.
> > 
> > >      If we are going to define ACP as a virtual out of band network, I would
> > >      suggest separating the terms into two definitions. One for true out  of
> > >      band networks (distinct physical links, switches, and ports), and then a
> > >      definition for virtual out of band network which describes the ACP
> > >      approximation which creates independence from configuration, but not
> > >      independence from the physical links.
> > 
> > Done.
> > 
> > [ Note: I am btw. not worried about the link-sharing as a career limiting move
> >    for ACP, as soon as there is sufficient link redundancy (2 links eliminate 99% of issues).
> > 
> >    The actual HW design of the nodes to maximize ACP value is more interesting.
> >    I had slides about that in a research conference workshop some years back, e.g.: applying
> >    concepts such as BMC so that you can use the common HW diag functions
> >    you typically expect from OOB support. ]
> > 
> > >      Section 5, bullet 2, talks about a policy as to which peers ACP
> > >      communication should be established.  It would be helpful if this gave a
> > >      reference or indication as to where such policies would come from.  Given
> > >      the emphasis on zero touch, I presume they are not configured on the node?
> > >      (This issues was in my review of -13.)
> > 
> > Original -13 thread here:
> > 
> > | >>      It is unclear how the flexible policy defined in section 5 bullet 2 (about
> > | >>      which nodes are ACP peer candidates) is consistent with autonomic
> > | >>      operation.  It seems that the flexibility is important, so there should be
> > | >>      some explanation here about how this is consonant with the stated goals.  I
> > | >>      understand that the bootstrap comes from BRSKI, but I do not think that is
> > | >>      where the policy comes from?
> > | >
> > | > Would rather not like to add more suggestive text, and thats at best what
> > | > i could add. The default policy is the best "autonomic" behavior we know how
> > | > to make work: aka: try to connect ACP to all neighbors you can discover. And
> > | > we have only defined with DULL GRASP how to find subnet adjacent neighbors.
> > | >
> > | > The main reason to mention policy is so that there is some leeway to do
> > | > more or even (sigh) less than all direct neighbors.
> > 
> > Double jeopardy ?
> > 
> > I actually did not bother to fix up the intro section since taking the editor pen
> > from Michael. I had kept the "policy" in there as a reminder of Intent to be
> > done in the future, but given how we deprioritized
> > intent in charter, i felt more happy now than during 13 to fix this.
> > 
> > Alas, it turns out i also found other points in the overview lacking
> > clarity and consistency with the normative sections, so the changes
> > here got larger, but hopefully all for the better. Please check.
> > 
> > >      Bullet 4 of section 6.1.3 on checking certificates against the CRL / OCSP
> > >      would seem to be better reworded.  I believe the intended requirements i
> > >      that IF there is ACP connectivity to the CRL / OCSP source, then it should
> > >      be verified.  But that absence of such connectivity should not prevent
> > >      association formation.  (As, if I have read it wright, otherwise we could
> > >      deadlock the startup process.)
> > 
> > Pls. check the full diff vs. -24 for this, because that fix is in the commit i did for
> > Russ Housley before i worked on your review. If you don't like that text either, pls
> > suggest better wording, its a bit of a tricky language problem i think, which a native
> > speaker might master easier.
> > 
> > >      In the example in section 6.5 on Channel selection, in steps 7:C1 and
> > >      11:C2, Node 1 concludes that it is Bob.  However, in steps 12 and 13, the
> > >      text refers to Node1 (Alice).  This seems inconsistent.
> > 
> > Yikes. How could that have slipped me. Thanks a lot.
> > > 
> > >      Section 6.7.1 makes an assertion about the lack of need for MTI of security
> > >      mechanisms.  The earlier explanation was well done and seems sound.  This
> > >      shorter one seems wrong, since without MTI there is no good way to know
> > >      what ones neighbors may implement.  I suggest simply removing this text and
> > >      replacing it with a backwards reference to the earlier description.  (The
> > >      rest of the section is useful and clear.)
> > 
> > Done.
> > 
> > >      In 6.10.3,  ACP Zone Addressing Sub-Scheme, the text claims that when zone
> > >      IDs of 0 are used, the addresses are identifiers, and when non-zero IDs
> > >      aere used, they are locators.  Since in either case the addresses are used
> > >      for packet forwarding, and the addressing information is propagated in the
> > >      routing protocol (RPL), this seems to be a misuse of the locator /
> > >      identifier distinction.  And a misuse for no purpose as the distinction is
> > >      not relevant to the document.  (This odd use of "identifier continues in
> > >      section 6.10.3.1.  Identifier is not a synonym of "flat".  Just say "flat".)
> > 
> > Hey, i didn't come up with all this confusing an probably wrong understanding
> > of locator or identifier, i just fell into the trap of trying to use these terms ;-))
> > 
> > This is removed now. Hope i found all places. Only locartors left should be
> > about GRASP.
> > 
> > Is there even any agreed upon distinction ? To me, identifier/locator are just
> > two roles an address can have based on who is using it for what purpose.
> > They're not exclusive to each other IMHO.
> > 
> > >      The assertion about looping packets in the later portion of 6.11.1.1 is
> > >      over-stated.  There are other routing protocols that avoid looping-till-ttl
> > >      without changing the data plane header.
> > 
> > >      I suggest removing the gratuitous     comparison with other routing protocols.
> > 
> > Well... it was IMHO not gratuitous, it was just bad text.
> > 
> > The intent was not to make the solution sound better than other routing protocols,
> > but rather to explain how it is not far worse than other routing protocols given
> > the absence of the RPI (RPL Packet Information).
> > 
> > The text was not good because it only indirectly addressed what
> > it intended to describe by just talking about TTL looping. I have replaced this
> > paragraph by two paragraphs that hopefully better capture the intent:
> > 
> > [snip]
> >      <t>
> >        In RPL profiles where RPL Packet Information (RPI, see <xref target="rpl-Data-Plane"/>)
> >        is present, it is also used to trigger reconvergence when misrouted, for example looping, packets
> >        are recognized because of their RPI data. This helps to minimize RPL signaling traffic
> >        especially in networks without stable topology and slow links.
> >      </t>
> >      <t>
> >        The ACP RPL profile instead relies on quick reconverging the DODAG by
> >        recognizing link state change (down/up) and triggering reconvergence signaling
> >        as described in <xref target="rpl-dodag-repair"/>.  Since links in the ACP
> >        are assumed to be mostly reliable (or have link layer protection against loss)
> >        and because there is no stretch according to <xref target="rpl-dodag-repair"/>,
> >        loops caused by loss of RPL routing protocol signaling packets should be exceedingly rare.</t>
> >      </t>
> > [/snip]
> > 
> > Hope this is an adequate answer to close this point.
> > 
> > I now have no text about TTL expiry because that is a difficult qualitative
> > comparison for which there is IMHO not enough data on evidence: The
> > reconvergence with RPL in the ACP profile may be somewhat slower than
> > the most common sub-50 msec LFA in SP networks or subsecond SPF-IGP
> > fast convergence common in most other networks in scope of ACP ("well manageg,
> > aka: private enterprise etc. networks), but the total amount of traffic
> > across the ACP will likely be orders of magnitude less than that on the
> > Data Plane where the SPF-IGP runs.
> > 
> > I think convergence with the profile should be 50 msec (link change discovery
> > plus O(max-pathlength) * per-node RPL processing latency, but i think
> > this is too much analysis for a spec, so no text.
> > 
> > >      Section 7.2 (L2 DULL GRASP) seems to be doing something quite useful.  I
> > >      think I see how it would work.  The need for some configuration on some
> > >      switches seems inevitable and acceptable.
> > 
> > Hmm.. there is no intent to require configuration. What specifically
> > do you think of ?
> > 
> > The goal is really to support ACP in complete L2-only networks, except that
> > the ACP itself is of course L3.
> > 
> > One core part of the text is explaining how ACP can be supported
> > on the most limited L2 hardware where it can work. Aka: withough changing
> > the actual L2 HW forwarding, but just by punting GRASP packets so they
> > are not flooded by L2.
> > 
> > >      I think there is one corner
> > >      case that should be avoided, as it seems likely to create significant
> > >      complexity for little or no benefit.  It seems to me that a switch that is
> > >      capable of participating in the ACP should either participate in the ACP on
> > >      all its physical ports, or should not participate in the ACP at all.  I
> > >      would not be surprised if that was the WG intent.  But I could not find the
> > >      text that says this.  (Apologies if it is there and I missed it.)
> > 
> > Not sure why you specifically think this is an issue for devices
> > operating at L2.
> > 
> > I have seen all type of weird problems. For example: How do you
> > enable autodiscovery of ACP neighbors across the 10Gbps backbone
> > interfaces of a router/switch for broadband if those interfaces
> > are initially disabled by software because the user is expected
> > to first enter an additional license key to use those interfaces....
> > 
> > Sorry, randomn example. Maybe rephrase your point with an example
> > why you think it deserve additional text ? Suggest additional text ?
> > 
> > > 
> > >      Section 9 starts by saying it is informational.  But the first paragraph
> > >      says that some of the content is "necessary" for correct operation.  Thus,
> > >      it seems that some of the content is normative?   (I am not sure, but I
> > >      think the "necessary" material relates to what is needed to be a registrar?)
> > 
> > The first paragraph does not say "correct operation", and i think
> > to remember that i word smithed that paragraph quite
> > a bit to walk the thin line: you can not build an ACP without
> > understanding this section and follow its advice to
> > the extend you deem appropriate or feasible, but we can also not
> > normatively standardize what is in this section.
> > 
> > Some things will hopefully gt standardized via future
> > yang model RFC. That stuff is just not standardized beause
> > it does not meet the formal bar.
> > 
> > Most of the stuff is talking about variety of options
> > deemed to be necessary or beneficial in various
> > situations. Doing even the Yang stuff for the subset
> > people will agree to is a lot of work.
> > 
> > protecting the ACP from operator
> > misconfiguration is IMHO necessary. I wouldn't even dare
> > to begin guessing what details could get standardized for
> > that. Yang models for new interface states would certainly
> > be another 5++ year discusion in IETF. better to start
> > these things with vendor proprietary Yang models and learn.
> > 
> > I know from personal experience that you can not successfully
> > deploy without humunguous amount of diagnostic as long as
> > you have buggy implementations, especially when fitting
> > into exising router OS, incurring a lot of unforeseen
> > limitations. Very difficult to standardize because its
> > all about interaction with the non-autonomic stuff unless
> > you can severely isolate ACP in your platform design.
> > 
> > If you do not understand the discussions about registrars,
> > you will have a hard time getting a working support
> > backend system for the registars.
> > 
> > Aka: necessary does not mean standardizable.
> > 
> > > Nits:
> > >      The second and third paragraphs of section 6.11.1.1 on RPL start with
> > >      duplicated text, and then go on to say different (complementary) things.
> > >      There is no need for the repetition.
> > 
> > Right. I reworked the overview to remove duplicates, also structured
> > into two subsections to highlight the two key themes of the profile
> > (single instance and convergence).
> > 
> > >      The rank factor in 6.11.1.6 of 100 megabits as the boundary seems a fairly
> > >      arbitrary choice.  It may be that an arbitrary choice was needed.  Could
> > >      something be said?  In particular, if someone looks at this 5 years from
> > >      now, it may seem quite confusing.
> > 
> > In german, rule of thumb is called "pi times thumb", obviously much more
> > accurate than just thumb ;-)
> > 
> > I added the following paragraph:
> > 
> >          <t>This is a simple rank differentiation between typical "low speed"
> >          or "IoT" links that commonly max out at 100 Mbps and typical
> >          infrastructure links with speeds of 1 Gbps or higher. Given how
> >          the path selection for the ACP focusses only on reachability but
> >          not on path cost optimization, no attempts at finer grained path
> >          optimization are made. </t>
> > 
> > Heard a nice summary about the new ieee work about the future of 10 Mbps
> > ethernet over twisted pair, so i think the cut point at 100 Mbps
> > may actually be quite a good one. aka: with just two values i don't
> > know how we could do better.
> > 
> > Aain, thanks a lot for the review.
> > 
> > Toerless
> > 

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


From nobody Mon Jul  6 16:14:05 2020
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 DFB813A0BE3 for <anima@ietfa.amsl.com>; Mon,  6 Jul 2020 16:14:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.87
X-Spam-Level: 
X-Spam-Status: No, score=-0.87 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, 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 CM5lXAfZUi4J for <anima@ietfa.amsl.com>; Mon,  6 Jul 2020 16:14:01 -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 5EE143A0BDF for <anima@ietf.org>; Mon,  6 Jul 2020 16:14:01 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id DC64E548011; Tue,  7 Jul 2020 01:13:55 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id D3AB9440043; Tue,  7 Jul 2020 01:13:55 +0200 (CEST)
Date: Tue, 7 Jul 2020 01:13:55 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: anima@ietf.org
Message-ID: <20200706231355.GA54492@faui48f.informatik.uni-erlangen.de>
References: <159363696301.1694.14970467680230111407@ietfa.amsl.com> <14763.1593644290@localhost> <20200701234100.GC60049@faui48f.informatik.uni-erlangen.de> <4988.1593649836@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4988.1593649836@localhost>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/1DPbF-YGqdn9k3rqiuIoBb2K3gg>
Subject: Re: [Anima] use of CRLs in I-D Action: draft-ietf-anima-autonomic-control-plane-26.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, 06 Jul 2020 23:14:04 -0000

On Wed, Jul 01, 2020 at 08:30:36PM -0400, Michael Richardson wrote:
> 
> Toerless Eckert <tte@cs.fau.de> wrote:
>     > The need to diligently document support for CRL/OCSP was done on
>     > behalf of securiy reviews. It is not meant to be a recommendation.
>     > There is mentioning of short-lived certificates in a few places in the
>     > doc.
> 
> I didn't see an RFC8739 reference.  Oh. It's I-D.ietf-acme-star.
> Your section 6.1.5.4 suggests CRLs are unnecessary when the lifetime is on
> the order of hours,  while RFC8739 is less specific about what is short.

2.3 days is one number i found in the RFC.

IMHO RFC8739 is not a relevant comparison for ACP (and i am not only
saying this because otherName killed our ability to use ACME CA with
RFC822 names ;-):

Unless i am missing something, ACP/EST renewal of certs is already the
same "lightweight" renewal that RFC8739 introduces for ACME.

In addition for ANI nodes, we always have re-enrollment via BRSKI/MASA.

Aka: ultimately, the question is whether/how we should deal with
expired certs under incomplete reachability. Max already said that
it should be perfectly fine for EST to accept expired certs as
a valid credential for renewal, that was just never top of mind when
EST was developed, and it certainly would cause hesitation at first
by IETF security review should that be added. 

I for once had to regularily re-activate enterprise WFH VPN clients
that where switched off  for months, then users sent me email, and
i had to go to the VPN server and configure "ignore lifetime for this cert",
so the VPN client would renew its cert.

> I think that a certificate lifetime on the order of a week would probably be
> workable.

I think that if you want to get rid of CRL/OCSP then you need to
get down to reaction time at the order of revocation, which i think
can be as little as 30 minutes. I think its not a problem to do that,
its just far off the beaten track people feel offended to think about
it. There are a lot of network operations aliveness operations at
a 30 seconds interval for every node (aliveness ping). Doing a simple
cert re-signing once every 30 minutes isn't worse IMHO.

> But, I think think we should get implementation experience.

Sure, but there are a lot long-term issues that can happen, sometimes
folks take yeas in deployments to figure out probems with cert lifetime
management, hence the theoretical discussion is useful here too.

>     >> I think that CRLs are not useful, and we should not use them.
> 
>     > I think we agree.
> 
> Good.
> 
>     >> 6.1.3 is clear that OCSP/CRLs may not be available when connecting!
>     >>
>     >> I think that use of STAR (https://datatracker.ietf.org/doc/rfc8739/ )
>     >> Short-Term, Automatically Renewed is the best recommendation!
> 
>     > In general yes, but the STAR use cases typically do not take into
>     > account  connectivity problems that are longer than the lifetime of
>     > a cert, whereas for the ACP this might be a problem.
> 
> yes, but the solution is to find a Join Proxy, reach out to the Registrar and
> renew the certificate using the LDevID one has.
> STAR even went into some detail about how one could renew expired
> certificates, I think. (I recall a discussion, but I'd have to check the
> document again)

Exactly, but that i think was also why the general purpose STAR document
didn't progress in LAMPS. But i forgot all the generic issues there,
i think to remember they are not an issue for ANI/ACP though, but
obviously that would have to be probed by going to LAMPS with a more
constrained EST renewal with expired certs discussion.

>     >> If we have to do OCSP (via https://datatracker.ietf.org/doc/rfc4806/ )
>     >> then we nodes can download their staple and provide it when connecting.
>     >> New nodes can get this using the Join Proxy.
>     >>
>     >> Perhaps this needs to be in a new document at this point.
> 
>     > Yepp.  I think to remember that MaxP was thinking of suggesting to
>     > talk about dealing with expired certs for our cases in i think LAMPS too
>     > but longer ago...
> 
> yes, the document wound up in ACME, and I think they did a good job, although
> it is proscriptive for ACME only, while our end-client interface is assumed
> to be EST.

Yepp. The comparison is probably that doing in ACME the revalidation of
ownership of (domain/email) name is as complex as going through BRSKI/MASA,
whereas doing just EST renewal, worst case via join-proxy (if cert is
expired) is exactly what RFC8739 does for ACME.

Cheers
    Toerless

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



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


From nobody Mon Jul  6 21:14:47 2020
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 C75E93A0778 for <anima@ietfa.amsl.com>; Mon,  6 Jul 2020 21:14:43 -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, RCVD_IN_MSPIKE_H2=-0.001, 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 nwRm8UjJh-l0 for <anima@ietfa.amsl.com>; Mon,  6 Jul 2020 21:14: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 B9EED3A077A for <anima@ietf.org>; Mon,  6 Jul 2020 21:14:41 -0700 (PDT)
Received: from lhreml739-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id DCE97F29C06031B4D57E; Tue,  7 Jul 2020 05:14:39 +0100 (IST)
Received: from nkgeml705-chm.china.huawei.com (10.98.57.154) by lhreml739-chm.china.huawei.com (10.201.108.189) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Tue, 7 Jul 2020 05:14:39 +0100
Received: from nkgeml708-chm.china.huawei.com (10.98.57.160) by nkgeml705-chm.china.huawei.com (10.98.57.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Tue, 7 Jul 2020 12:14:36 +0800
Received: from nkgeml708-chm.china.huawei.com ([10.98.57.160]) by nkgeml708-chm.china.huawei.com ([10.98.57.160]) with mapi id 15.01.1913.007; Tue, 7 Jul 2020 12:14:36 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Toerless Eckert <tte@cs.fau.de>
CC: "rwilton@cisco.com" <rwilton@cisco.com>, "warren@kumari.net" <warren@kumari.net>, "anima@ietf.org" <anima@ietf.org>
Thread-Topic: Sheng: Pls. request AD approval for IANA early allocation of code points for draft-ietf-anima-autonomic-control-plane
Thread-Index: AQHWU7B/6GvGyxxos0i0BRH4OFe5F6j7gX0A
Date: Tue, 7 Jul 2020 04:14:36 +0000
Message-ID: <6843a17c7c794095b1ce87d202ab8b77@huawei.com>
References: <20200706161352.GA12228@faui48f.informatik.uni-erlangen.de>
In-Reply-To: <20200706161352.GA12228@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.108.235.253]
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/xRya-duMpNPtv0tNKSvzYBLcmfE>
Subject: Re: [Anima] Sheng: Pls. request AD approval for IANA early allocation of code points for draft-ietf-anima-autonomic-control-plane
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, 07 Jul 2020 04:14:46 -0000

Hi, Toerless, Rob and Warren,

I conform ANIMA WG would like to ask the IANA early allocation for draft-ie=
tf-anima-autonomic-control-plane. Please help for the follow-up procedure.

Thanks and best regards,

Sheng (as document shepherd with ANIMA chair hat)=20

> -----Original Message-----
> From: Toerless Eckert [mailto:tte@cs.fau.de]
> Sent: Tuesday, July 7, 2020 12:14 AM
> To: Sheng Jiang <jiangsheng@huawei.com>
> Cc: rwilton@cisco.com; warren@kumari.net; anima@ietf.org
> Subject: Sheng: Pls. request AD approval for IANA early allocation of cod=
e
> points for draft-ietf-anima-autonomic-control-plane
>=20
> Dear Sheng,
>=20
> I have tried to whip up below the necessary information for the WG chair =
to
> AD approval request according to RFC7120. As the non-author co-chair,
> please check if you approve and proceed accordingly.
>=20
> Thanks
>    Toerless (for the authors of draft-ietf-anima-autonomic-control-plane)
>=20
> ---
>=20
> From: jiangsheng@huawei.com
> To: rwilton@cisco.com, warren@kumari.net
> Cc: anima@ietf.org
> Subject: OPS-ADs: request for IANA early allocation of codepoints for dra=
ft-
> ietf-anima-autonomic-control-plane
>=20
> Dear Rob, Warren
>=20
> For the ANIMA chairs, i hereby request your approval according to RFC7120=
,
> section 3.1, point 4, for IANA early allocation of the below described 2 =
code
> points to be assigned to draft-ietf-anima-autonomic-control-plane.
>=20
> According to RFC7120, section 3.1, point 2, the conditions for early allo=
cation
> are met.
>=20
> Code point (1)
>  Registry: https://www.iana.org/assignments/smi-numbers/smi-
> numbers.xhtml#smi-numbers-1.3.6.1.5.5.7.0
>  Requested Description: id-mod-anima-acpnodename-2020  RFC7120, section
> 2 conditions for early allocation:
>   (a) "Specification Required", will be published as RFC
>       Expert: Russ Housley
>   (b) specification adequately described in
>       draft-ietf-anima-autonomic-control-plane-27, section 6.1.2/6.1.2.1
>   (c) Specification is stable:
>       No backward compatibility issue introduced by this code-point.
>   (d) Request by implementors for interop testing and question to WG
>       has determined that there is sufficient interest in the community
>       for early allocation.
>  No depletion issue in this registry
>=20
>=20
> Code point (2)
>  Registry: https://www.iana.org/assignments/smi-numbers/smi-
> numbers.xhtml#smi-numbers-1.3.6.1.5.5.7.8
>  Description: id-mod-anima-acpnodename-2020  Requested Description: id-
> on-AcpNodeName
>   (a) "Specification Required", will be published as RFC
>       Expert: Russ Housley
>   (b) specification adequately described in
>       draft-ietf-anima-autonomic-control-plane-27, section 6.1.2/6.1.2.1
>   (c) Specification is stable: N/A:
>       N/A: No prior approved spec for this functionality.
>       Prior draft proposed code point (rfc822Name):
>       - Not used in production deployments:
>       - Rejected by IESG for > 1 year,
>       - Backward compatibility undesirable by IESG, WG and draft authors
> (undesirable complexity).
>   (d) Request by implementors for interop testing and question to WG
>       has determined that there is sufficient interest in the community
>       for early allocation.
>  No depletion issue in this registry
>=20
> For the ANIMA chairs
>     Sheng Jiang


From nobody Tue Jul  7 02:29:30 2020
Return-Path: <rwilton@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 3D37B3A0827 for <anima@ietfa.amsl.com>; Tue,  7 Jul 2020 02:29:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.598
X-Spam-Level: 
X-Spam-Status: No, score=-9.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 header.b=igfml/8I; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=BDkqesqA
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 waDE04xfjPoU for <anima@ietfa.amsl.com>; Tue,  7 Jul 2020 02:29:26 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74D083A0895 for <anima@ietf.org>; Tue,  7 Jul 2020 02:29:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4178; q=dns/txt; s=iport; t=1594114166; x=1595323766; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Z4CmxwnvB457g+xxBrJRcxy6Z8WyHpqtTqAMZp8PzAY=; b=igfml/8IPhtZqzmbw5KIn5Hs1aZxKm1nvTPenlFb7x+MqJjthrGuddql bbeTavwJUQlaljN3ji7yGRMa2wQ3Ogm6gHSYH382sGN5no2St4Q7T3Ddg WPZkOLj3cJexYqgeZe+q+ewQE0RnH9vDQYS4SKDMUg2tqOQT6rFRcygRc I=;
IronPort-PHdr: =?us-ascii?q?9a23=3AVfZtABEoGTqodHct1z7h0Z1GYnJ96bzpIg4Y7I?= =?us-ascii?q?YmgLtSc6Oluo7vJ1Hb+e401QGbXZjS9P9FzeHRtvOoVW8B5MOHt3YPONxJWg?= =?us-ascii?q?QegMob1wonHIaeCEL9IfKrCk5yHMlLWFJ/uX3uN09TFZX+elTNr3z05jkXSV?= =?us-ascii?q?3zMANvLbHzHYjfx828y+G1/cjVZANFzDqwaL9/NlO4twLU48IXmoBlbK02z0?= =?us-ascii?q?jE?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ApAADBPwRf/5NdJa1gGgEBAQEBAQE?= =?us-ascii?q?BAQEDAQEBARIBAQEBAgIBAQEBQIE5AgEBAQELAYFRUQdvWC8sCoduA41LmFq?= =?us-ascii?q?BQoEQA1ULAQEBDAEBIwoCBAEBhEcCgiYCJDcGDgIDAQELAQEFAQEBAgEGBG2?= =?us-ascii?q?FWwyFbgEBAQQSKAYBASkOAQsEAgEIEQQBAR8FBAcyFAkIAgQBDQUIDA6DBYJ?= =?us-ascii?q?LAy4BDp1aAoE5iGF0gTSDAQEBBYMngW4Ygg4DBoE4AYJohX2EBBqBQT+BEUO?= =?us-ascii?q?CHy4+axkBgn48g0eCLYdih22MQZh/CoJcmWqCc4kwknqRWp5hAgQCBAUCDgE?= =?us-ascii?q?BBYFpI4FWcBWDJFAXAg2OHjeDOoUUhUJ0NwIGCAEBAwl8jlQBgRABAQ?=
X-IronPort-AV: E=Sophos;i="5.75,323,1589241600"; d="scan'208";a="794111554"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 07 Jul 2020 09:29:24 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by rcdn-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id 0679TOTg020133 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 7 Jul 2020 09:29:24 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 7 Jul 2020 04:29:24 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 7 Jul 2020 05:29:23 -0400
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Tue, 7 Jul 2020 04:29:23 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=LXLXRM3OurNpnw6uoGOV+sNYy26uh+fryRmcOzuLwA1NHk6ATUtRrvpS0QqyeJYQ/1IIFzlC479b0+0LhuVfDzXkVZfDkuURv8BJQxD8Grh5dEm5xpowERx8qVX4qhwrci1w6dbC51ML0GwLW26i5hpQP+ftu2zpN2ZZgCtnRXZbsU1n4OTglp7lC/yC05h9cJARHtiUo5I2APRM5uly4Tv+w5ctYaAoB3pLIIX+IBbXBz6o/rodAlphaT50jbCK36Vt9voeUJM24x2/B9UNdEELtvyxdH6vgBVqe1HNksGXcp+LuXtuZrqdDorrz6fZx1WS3g0c1Wht+U0M2xYXIA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SDdBB8HeVyo3ES027i5SSgFWoS7axfaw9rwWSUpeGY8=; b=ajtuCedrPw351xDNhqAD7l0eodPjmKJOZyvHpyq9OMOa/gy8g/hnuqksNo/jZ9X63Yt2D5f6StCja57DrlO9XlHd8r+HEAaVVaErhlSrrsTjmaEA3gnyyIYpKA4qQhLoDR/gM1LyqDAPzj9gutGniYqWeOZne8xLx8VsJdSOxH9IcWaAD3HUe7reya9KkYrpmE7M4xLPk4Yue3eThTCSvuUV2IQQesdRl61Um6+qvXIS8Hv2MMnIxVyE1mx1iDO1tura8LA0u63dvDg4NbtSRpbk+DixTUTlVjtV2Yfu54LsoZLDcukXn/NWONHj4mmz23aV43FSny9HTNldDdf0eg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SDdBB8HeVyo3ES027i5SSgFWoS7axfaw9rwWSUpeGY8=; b=BDkqesqAfGXfcxZZtEmhtDpmhitwL6coZ4ZuFPTs/tuku42IiBGA0YV9jfwuPXrv8r4kqJpEqZwTCYH0ONqAJbacN23twAslWvUK0O7m8EXXW8ggcfzzTymLJTjH3W4Qw4JuuIvZCx6atZy0xXB/ft8BMbDhRSlFtkGpmnbhHRY=
Received: from MN2PR11MB4366.namprd11.prod.outlook.com (2603:10b6:208:190::17) by BL0PR11MB2900.namprd11.prod.outlook.com (2603:10b6:208:31::33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3153.22; Tue, 7 Jul 2020 09:29:21 +0000
Received: from MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::e9d4:79b5:aef1:be18]) by MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::e9d4:79b5:aef1:be18%5]) with mapi id 15.20.3153.029; Tue, 7 Jul 2020 09:29:21 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Sheng Jiang <jiangsheng@huawei.com>, Toerless Eckert <tte@cs.fau.de>, "warren@kumari.net" <warren@kumari.net>
CC: "anima@ietf.org" <anima@ietf.org>
Thread-Topic: Sheng: Pls. request AD approval for IANA early allocation of code points for draft-ietf-anima-autonomic-control-plane
Thread-Index: AQHWU7B9HQGahuc/1kKlV2+VzySh0Kj7gt4AgABUUyA=
Date: Tue, 7 Jul 2020 09:29:21 +0000
Message-ID: <MN2PR11MB436686ADAD1B4BA8A70555FDB5660@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <20200706161352.GA12228@faui48f.informatik.uni-erlangen.de> <6843a17c7c794095b1ce87d202ab8b77@huawei.com>
In-Reply-To: <6843a17c7c794095b1ce87d202ab8b77@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;huawei.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [64.103.40.24]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 236f444f-bb65-4540-71a8-08d822583ae8
x-ms-traffictypediagnostic: BL0PR11MB2900:
x-microsoft-antispam-prvs: <BL0PR11MB2900337F8A2302821884C0D5B5660@BL0PR11MB2900.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0457F11EAF
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: YbssLmDLiGIvjkgnyd/otTI1qob/+mKJTtfxdOvfxfDDiPRyNSl2js+nOECbyLkGPGUPxUaKlX5SofO7iq2Nj4dkchlV8U8flt4hjX0iAYrtBwHSQiSGlAjax/WZ4wyMZV9wBNmd9pyniJVNaF7zvA3Jaw+2eLC+fWA93lWSWX5eduzCW2Yr1hn2LgJjDVFTkwPo+cT9nCZ3urQUDEBQr9FaSRWLGfumabPxjXxPijqjcp9dAzDxogFptMflZHIQ67soXhLcQWW8cubZLaztAdUzXrb4qr3K/AivSWHdbbxb9479E+FNnY0Ylzjd91vRDC0DSwaOAP2ObAp+kGpPiTX/x4yoKa51xkemQeSsf7wCLZHmq/qrXIrXgepJqPFmXlOhQ/ZqPTEzGJOekb+zZQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MN2PR11MB4366.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(366004)(136003)(396003)(346002)(376002)(39860400002)(64756008)(66446008)(66946007)(966005)(66476007)(4326008)(6506007)(53546011)(2906002)(66556008)(7696005)(83380400001)(26005)(5660300002)(186003)(33656002)(8936002)(478600001)(76116006)(52536014)(9686003)(71200400001)(316002)(8676002)(55016002)(110136005)(86362001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: eWKe0jWkRSvCyjb/koA8Ectq2AW9JlOBd/2Pf/PKQGjQxHO0dTh0wjdwih2a2PZNZs3Z27+pTzY+2793K99IRtxk3wETn5I6SAFUkkYh3zlSo5t41YtusDZZtGotDNE8cPCJKpW+yghng/m1/8kWCrabsIJTTQ9GVOlx+pEDr/ue7WpidVkMxCyZEApWZtFdpQLrXgqFJisnn3Z7CZseyX4ZvCwOO/befW16YjTtfSYe5BT+ovgGmdnWO9BErs6NFQ4KlkqSeVY7mfJbvocVUhj0vhs3njljhCYAGk5QkGQ2eonOCzFyYf62UJa9vM4+zCOfjqloIK0JQ2oNWyXYRk3rl59eya2NpVejbPS8MnL2QHrGLMi/oi/STTqkmWSdtpHTTACE/NOnBKSxBI8tiN6lcD4wGTwruBO1x7Kdy6GH3H21/sRxPXyDBLPOi1crvkLwz0SNYS/Oshc7r4tvOcaYGNnzpTNBU41XMt3JSVQ=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MN2PR11MB4366.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 236f444f-bb65-4540-71a8-08d822583ae8
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Jul 2020 09:29:21.1924 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: pXThPjQX3JurmA40GPDOn4wqeg4/hsPM4aoM3wemtmlruKVeUIeFFLkk6UN5p0A5tO5EUYnyiiSHJCZTKAx4bA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR11MB2900
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.15, xch-rcd-005.cisco.com
X-Outbound-Node: rcdn-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/lpkxTrFWOnvo_khhQ-G7wx8oEzs>
Subject: Re: [Anima] Sheng: Pls. request AD approval for IANA early allocation of code points for draft-ietf-anima-autonomic-control-plane
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, 07 Jul 2020 09:29:29 -0000

I approve this request for IANA early allocation.

Warren, am I right to assume that the next step is for Sheng or Toerless (a=
s WG chairs) to make a request via https://www.iana.org/form/protocol-assig=
nment?

Regards,
Rob


> -----Original Message-----
> From: Sheng Jiang <jiangsheng@huawei.com>
> Sent: 07 July 2020 05:15
> To: Toerless Eckert <tte@cs.fau.de>
> Cc: Rob Wilton (rwilton) <rwilton@cisco.com>; warren@kumari.net;
> anima@ietf.org
> Subject: RE: Sheng: Pls. request AD approval for IANA early allocation of
> code points for draft-ietf-anima-autonomic-control-plane
>=20
> Hi, Toerless, Rob and Warren,
>=20
> I conform ANIMA WG would like to ask the IANA early allocation for draft-
> ietf-anima-autonomic-control-plane. Please help for the follow-up
> procedure.
>=20
> Thanks and best regards,
>=20
> Sheng (as document shepherd with ANIMA chair hat)
>=20
> > -----Original Message-----
> > From: Toerless Eckert [mailto:tte@cs.fau.de]
> > Sent: Tuesday, July 7, 2020 12:14 AM
> > To: Sheng Jiang <jiangsheng@huawei.com>
> > Cc: rwilton@cisco.com; warren@kumari.net; anima@ietf.org
> > Subject: Sheng: Pls. request AD approval for IANA early allocation of
> code
> > points for draft-ietf-anima-autonomic-control-plane
> >
> > Dear Sheng,
> >
> > I have tried to whip up below the necessary information for the WG chai=
r
> to
> > AD approval request according to RFC7120. As the non-author co-chair,
> > please check if you approve and proceed accordingly.
> >
> > Thanks
> >    Toerless (for the authors of draft-ietf-anima-autonomic-control-
> plane)
> >
> > ---
> >
> > From: jiangsheng@huawei.com
> > To: rwilton@cisco.com, warren@kumari.net
> > Cc: anima@ietf.org
> > Subject: OPS-ADs: request for IANA early allocation of codepoints for
> draft-
> > ietf-anima-autonomic-control-plane
> >
> > Dear Rob, Warren
> >
> > For the ANIMA chairs, i hereby request your approval according to
> RFC7120,
> > section 3.1, point 4, for IANA early allocation of the below described =
2
> code
> > points to be assigned to draft-ietf-anima-autonomic-control-plane.
> >
> > According to RFC7120, section 3.1, point 2, the conditions for early
> allocation
> > are met.
> >
> > Code point (1)
> >  Registry: https://www.iana.org/assignments/smi-numbers/smi-
> > numbers.xhtml#smi-numbers-1.3.6.1.5.5.7.0
> >  Requested Description: id-mod-anima-acpnodename-2020  RFC7120, section
> > 2 conditions for early allocation:
> >   (a) "Specification Required", will be published as RFC
> >       Expert: Russ Housley
> >   (b) specification adequately described in
> >       draft-ietf-anima-autonomic-control-plane-27, section 6.1.2/6.1.2.=
1
> >   (c) Specification is stable:
> >       No backward compatibility issue introduced by this code-point.
> >   (d) Request by implementors for interop testing and question to WG
> >       has determined that there is sufficient interest in the community
> >       for early allocation.
> >  No depletion issue in this registry
> >
> >
> > Code point (2)
> >  Registry: https://www.iana.org/assignments/smi-numbers/smi-
> > numbers.xhtml#smi-numbers-1.3.6.1.5.5.7.8
> >  Description: id-mod-anima-acpnodename-2020  Requested Description: id-
> > on-AcpNodeName
> >   (a) "Specification Required", will be published as RFC
> >       Expert: Russ Housley
> >   (b) specification adequately described in
> >       draft-ietf-anima-autonomic-control-plane-27, section 6.1.2/6.1.2.=
1
> >   (c) Specification is stable: N/A:
> >       N/A: No prior approved spec for this functionality.
> >       Prior draft proposed code point (rfc822Name):
> >       - Not used in production deployments:
> >       - Rejected by IESG for > 1 year,
> >       - Backward compatibility undesirable by IESG, WG and draft author=
s
> > (undesirable complexity).
> >   (d) Request by implementors for interop testing and question to WG
> >       has determined that there is sufficient interest in the community
> >       for early allocation.
> >  No depletion issue in this registry
> >
> > For the ANIMA chairs
> >     Sheng Jiang


From nobody Tue Jul  7 06:46:02 2020
Return-Path: <warren@kumari.net>
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 39DCA3A0CC9 for <anima@ietfa.amsl.com>; Tue,  7 Jul 2020 06:45:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, 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=kumari-net.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 OTye9UE61O2A for <anima@ietfa.amsl.com>; Tue,  7 Jul 2020 06:45:57 -0700 (PDT)
Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (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 ED0AF3A0CC8 for <anima@ietf.org>; Tue,  7 Jul 2020 06:45:56 -0700 (PDT)
Received: by mail-lf1-x12f.google.com with SMTP id s16so19262522lfp.12 for <anima@ietf.org>; Tue, 07 Jul 2020 06:45:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3mki/Xq2X0ks/uItUpEDvIGYqbXamnDDrYuiS/K4fNU=; b=1tOxQ5ceczGsid4S2yk1ys2EyKC1Myr75XrvqKVMJIgOjsdkUwMCs537mp6+U12RAp iG3aXRtw6alQFQ+69xiLI9w7KXaHKfAGC/i/8GKLEcXgcBIw9NLXcHJDMi1MH1CKb+EP iEl9L3gQoeCdJ5g9gFBhpsv0Z7uqIILGT/OSHDzP1v9FytbEa1tCSLIEs2fBG5th1VX6 8/oVGAiWD1qcJ5JJo1epn8kTjK0ILFVoVmOxNBxgkNyIYkA2Ul2uiTjn2MFFBDU9z0mn RlOX4RZnsLW2T2xCG4VC84gzQsp0TxCqBcc4zW5om3qNAuR/BIVswFNllEHcS8eneRoc zRSA==
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=3mki/Xq2X0ks/uItUpEDvIGYqbXamnDDrYuiS/K4fNU=; b=LH0LbN7W395JygkJGkFz5lGFeebTORA2/SZPEUtW4Ao5NQh5cBL1DH6YoMJJVKFS2K 3K0LRy/EKw92TBU+jmQkjRBJ5Z0isqbv+IF5jkIT7nPqAADFS2d07dm5i4lfQh+3yVui KrK+nFc+z4mZKzVPzmpuOup6AkdrfDjJ1Eqkp5oF02AdJBnYWlEmuyZjJ5WpIX6oElmH RiATnovD2LA4PiUmNr+yyCh7h7mi34wkPYe8BK+9T5c5toWROpE2rwx5LR3x3YAxtNx2 /O0ClShlURzwjSle8MCuwae6cF7m4R9XG/5gde+ihLfEjcpoNFij8jFZItImh7qEhTDK Glgw==
X-Gm-Message-State: AOAM531cRCoKS+iiFVotHY/We40dtRdVFbMgKddqaDsizY/f0tiqzggt g2UOgVUyLeeyG5/iQylNi3o9jBR2uRhRVg9ih/wpog==
X-Google-Smtp-Source: ABdhPJwmjvc+TdB5yCfQ/z4kbL9rnFA/rMILHUds+gtx5ckBjZNjhInEKjjNnAWm5NwFFwnM9PkqIUtlI132Tt+MXaI=
X-Received: by 2002:ac2:5962:: with SMTP id h2mr32611470lfp.66.1594129554360;  Tue, 07 Jul 2020 06:45:54 -0700 (PDT)
MIME-Version: 1.0
References: <20200706161352.GA12228@faui48f.informatik.uni-erlangen.de> <6843a17c7c794095b1ce87d202ab8b77@huawei.com> <MN2PR11MB436686ADAD1B4BA8A70555FDB5660@MN2PR11MB4366.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB436686ADAD1B4BA8A70555FDB5660@MN2PR11MB4366.namprd11.prod.outlook.com>
From: Warren Kumari <warren@kumari.net>
Date: Tue, 7 Jul 2020 09:45:18 -0400
Message-ID: <CAHw9_iLBj-x+Sxzc0e5zmBS_eFQOQtOKHPcP7C_+U-Ztai-53Q@mail.gmail.com>
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>
Cc: Sheng Jiang <jiangsheng@huawei.com>, Toerless Eckert <tte@cs.fau.de>,  "anima@ietf.org" <anima@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/Aay94MlUNMSQs2CjtQSgcVcu0tc>
Subject: Re: [Anima] Sheng: Pls. request AD approval for IANA early allocation of code points for draft-ietf-anima-autonomic-control-plane
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, 07 Jul 2020 13:45:59 -0000

On Tue, Jul 7, 2020 at 5:29 AM Rob Wilton (rwilton) <rwilton@cisco.com> wrote:
>
> I approve this request for IANA early allocation.
>
> Warren, am I right to assume that the next step is for Sheng or Toerless (as WG chairs) to make a request via https://www.iana.org/form/protocol-assignment?

Yup, that should work.

I've previously just emailed iana@iana.org, but the above link does
seem like a better option - you get tracking, it provides the
information in a more clear form, etc.

Toerless - you have previously done one of these (thread: "AD approval
request for early allocation for id-ct-animaCBORVoucher") - I'd
suggest just repeating whatever you did then, as it seemed to work :-)

Thanks,
W

>
> Regards,
> Rob
>
>
> > -----Original Message-----
> > From: Sheng Jiang <jiangsheng@huawei.com>
> > Sent: 07 July 2020 05:15
> > To: Toerless Eckert <tte@cs.fau.de>
> > Cc: Rob Wilton (rwilton) <rwilton@cisco.com>; warren@kumari.net;
> > anima@ietf.org
> > Subject: RE: Sheng: Pls. request AD approval for IANA early allocation of
> > code points for draft-ietf-anima-autonomic-control-plane
> >
> > Hi, Toerless, Rob and Warren,
> >
> > I conform ANIMA WG would like to ask the IANA early allocation for draft-
> > ietf-anima-autonomic-control-plane. Please help for the follow-up
> > procedure.
> >
> > Thanks and best regards,
> >
> > Sheng (as document shepherd with ANIMA chair hat)
> >
> > > -----Original Message-----
> > > From: Toerless Eckert [mailto:tte@cs.fau.de]
> > > Sent: Tuesday, July 7, 2020 12:14 AM
> > > To: Sheng Jiang <jiangsheng@huawei.com>
> > > Cc: rwilton@cisco.com; warren@kumari.net; anima@ietf.org
> > > Subject: Sheng: Pls. request AD approval for IANA early allocation of
> > code
> > > points for draft-ietf-anima-autonomic-control-plane
> > >
> > > Dear Sheng,
> > >
> > > I have tried to whip up below the necessary information for the WG chair
> > to
> > > AD approval request according to RFC7120. As the non-author co-chair,
> > > please check if you approve and proceed accordingly.
> > >
> > > Thanks
> > >    Toerless (for the authors of draft-ietf-anima-autonomic-control-
> > plane)
> > >
> > > ---
> > >
> > > From: jiangsheng@huawei.com
> > > To: rwilton@cisco.com, warren@kumari.net
> > > Cc: anima@ietf.org
> > > Subject: OPS-ADs: request for IANA early allocation of codepoints for
> > draft-
> > > ietf-anima-autonomic-control-plane
> > >
> > > Dear Rob, Warren
> > >
> > > For the ANIMA chairs, i hereby request your approval according to
> > RFC7120,
> > > section 3.1, point 4, for IANA early allocation of the below described 2
> > code
> > > points to be assigned to draft-ietf-anima-autonomic-control-plane.
> > >
> > > According to RFC7120, section 3.1, point 2, the conditions for early
> > allocation
> > > are met.
> > >
> > > Code point (1)
> > >  Registry: https://www.iana.org/assignments/smi-numbers/smi-
> > > numbers.xhtml#smi-numbers-1.3.6.1.5.5.7.0
> > >  Requested Description: id-mod-anima-acpnodename-2020  RFC7120, section
> > > 2 conditions for early allocation:
> > >   (a) "Specification Required", will be published as RFC
> > >       Expert: Russ Housley
> > >   (b) specification adequately described in
> > >       draft-ietf-anima-autonomic-control-plane-27, section 6.1.2/6.1.2.1
> > >   (c) Specification is stable:
> > >       No backward compatibility issue introduced by this code-point.
> > >   (d) Request by implementors for interop testing and question to WG
> > >       has determined that there is sufficient interest in the community
> > >       for early allocation.
> > >  No depletion issue in this registry
> > >
> > >
> > > Code point (2)
> > >  Registry: https://www.iana.org/assignments/smi-numbers/smi-
> > > numbers.xhtml#smi-numbers-1.3.6.1.5.5.7.8
> > >  Description: id-mod-anima-acpnodename-2020  Requested Description: id-
> > > on-AcpNodeName
> > >   (a) "Specification Required", will be published as RFC
> > >       Expert: Russ Housley
> > >   (b) specification adequately described in
> > >       draft-ietf-anima-autonomic-control-plane-27, section 6.1.2/6.1.2.1
> > >   (c) Specification is stable: N/A:
> > >       N/A: No prior approved spec for this functionality.
> > >       Prior draft proposed code point (rfc822Name):
> > >       - Not used in production deployments:
> > >       - Rejected by IESG for > 1 year,
> > >       - Backward compatibility undesirable by IESG, WG and draft authors
> > > (undesirable complexity).
> > >   (d) Request by implementors for interop testing and question to WG
> > >       has determined that there is sufficient interest in the community
> > >       for early allocation.
> > >  No depletion issue in this registry
> > >
> > > For the ANIMA chairs
> > >     Sheng Jiang



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Tue Jul  7 07:25:09 2020
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 A51FE3A0D18 for <anima@ietfa.amsl.com>; Tue,  7 Jul 2020 07:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.164
X-Spam-Level: 
X-Spam-Status: No, score=-0.164 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, 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 TnqDFsnP1kxb for <anima@ietfa.amsl.com>; Tue,  7 Jul 2020 07:25:05 -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 77DB63A0CE0 for <anima@ietf.org>; Tue,  7 Jul 2020 07:25:05 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 2820F548440; Tue,  7 Jul 2020 16:25:00 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 229B4440043; Tue,  7 Jul 2020 16:25:00 +0200 (CEST)
Date: Tue, 7 Jul 2020 16:25:00 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: IANA General Enquiries via RT <iana-questions@iana.org>
Cc: Warren Kumari <warren@kumari.net>, "Rob Wilton (rwilton)" <rwilton@cisco.com>, Sheng Jiang <jiangsheng@huawei.com>, "anima@ietf.org" <anima@ietf.org>, Russ Housley <housley@vigilsec.com>
Message-ID: <20200707142500.GZ13952@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/ucsrv8BvRm2W51Pp2-3LbRll_jw>
Subject: Re: [Anima] [IANA #1173842] early assignments for draft-ietf-anima-autonomic-control-plane
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, 07 Jul 2020 14:25:08 -0000

Dear IANA

In followup to subject early allocation request:

RFC7120 justifications:
  https://mailarchive.ietf.org/arch/msg/anima/X3h4AUHg2sMdyatpkZAliOhJEMs

AD Approval for early allocation:
  https://mailarchive.ietf.org/arch/msg/anima/lpkxTrFWOnvo_khhQ-G7wx8oEzs/

Registry expert feedback (Russ Housley):
 https://mailarchive.ietf.org/arch/msg/anima/r59nWsxMKFI968uMpKIgaBXp6Eg/
 (corect use of registry. mentioned missing word in text was fixed
  in latest version of draft).

Cheers
    Toerless

On Tue, Jul 07, 2020 at 02:08:59PM +0000, tte@cs.fau.de wrote:
> 
> Contact Name:
> Toerless Eckert
> 
> Contact Email:
> tte@cs.fau.de
> 
> Type of Assignment:
> Early allocation of 2 SMI-number registry code points according to RFC7120 to be assigned to draft-ietf-anima-autonomic-control-plane 
> 
> Registry:
> 1) https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-1.3.6.1.5.5.7.0
>   id-mod-anima-acpnodename-2020
> 2) https://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-numbers-1.3.6.1.5.5.7.8
>   id-mod-anima-acpnodename-2020
> 
> See first two request paragraphs of IANA section of document
> 
> Description:
> Early implementations, interop testing. RFC7120 process was followed, approval by rwilton@cisco.com today (AD for responsible WG)
> 
> Additional Info:
> Will CC you on mail with AD approval.


From nobody Tue Jul  7 12:28:51 2020
Return-Path: <iana-shared@icann.org>
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 499543A09D3 for <anima@ietfa.amsl.com>; Tue,  7 Jul 2020 12:28:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level: 
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, 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 8NVIpGGyQNTr for <anima@ietfa.amsl.com>; Tue,  7 Jul 2020 12:28:48 -0700 (PDT)
Received: from smtp01.icann.org (smtp01.icann.org [192.0.33.81]) (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 153713A09B8 for <anima@ietf.org>; Tue,  7 Jul 2020 12:28:48 -0700 (PDT)
Received: from request4.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp01.icann.org (Postfix) with ESMTP id DCF9CE012D; Tue,  7 Jul 2020 19:28:47 +0000 (UTC)
Received: by request4.lax.icann.org (Postfix, from userid 48) id D9692203C1; Tue,  7 Jul 2020 19:28:47 +0000 (UTC)
RT-Owner: amanda.baber
From: "Amanda Baber via RT" <iana-prot-param@iana.org>
Reply-To: iana-prot-param@iana.org
In-Reply-To: <rt-4.4.3-18048-1594132337-1419.1173842-37-0@icann.org>
References: <RT-Ticket-1173842@icann.org> <20200707142500.GZ13952@faui48f.informatik.uni-erlangen.de> <rt-4.4.3-18048-1594132337-1419.1173842-37-0@icann.org>
Message-ID: <rt-4.4.3-18048-1594150127-1191.1173842-37-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1173842
X-Managed-BY: RT 4.4.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: amanda.baber@icann.org
To: tte@cs.fau.de
CC: warren@kumari.net, rwilton@cisco.com, jiangsheng@huawei.com, housley@vigilsec.com, anima@ietf.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Tue, 07 Jul 2020 19:28:47 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/A0HkDjO1BXJVcpb_xMyFqcAp7B8>
Subject: [Anima] [IANA #1173842] Request for Assignment (smi-numbers, draft-ietf-anima-autonomic-control-plane)
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: Tue, 07 Jul 2020 19:28:49 -0000

Hi Toerless, all,

We've added the following early allocation to the SMI Security for PKIX Module Identifier (1.3.6.1.5.5.7.0) registry:

97	id-mod-anima-acpnodename-2020 (TEMPORARY - registered 2020-07-07, expires 2021-07-07)	[draft-ietf-anima-autonomic-control-plane-27]

We've also added the following early allocation to the SMI Security for PKIX Other Name Forms (1.3.6.1.5.5.7.8) registry:

10	id-on-AcpNodeName (TEMPORARY - registered 2020-07-07, expires 2021-07-07)	[draft-ietf-anima-autonomic-control-plane-27]

Please see
https://www.iana.org/assignments/smi-numbers

If the document hasn't been approved by the IESG by May 2021, we'll contact you about renewing for another year.

Best regards,

Amanda Baber
Lead IANA Services Specialist

On Tue Jul 07 14:32:17 2020, tte@cs.fau.de wrote:
> Dear IANA
> 
> In followup to subject early allocation request:
> 
> RFC7120 justifications:
>   https://mailarchive.ietf.org/arch/msg/anima/X3h4AUHg2sMdyatpkZAliOhJEMs
> 
> AD Approval for early allocation:
>   https://mailarchive.ietf.org/arch/msg/anima/lpkxTrFWOnvo_khhQ-
> G7wx8oEzs/
> 
> Registry expert feedback (Russ Housley):
>  https://mailarchive.ietf.org/arch/msg/anima/r59nWsxMKFI968uMpKIgaBXp6Eg/
>  (corect use of registry. mentioned missing word in text was fixed
>   in latest version of draft).
> 
> Cheers
>     Toerless
> 
> On Tue, Jul 07, 2020 at 02:08:59PM +0000, tte@cs.fau.de wrote:
> >
> > Contact Name:
> > Toerless Eckert
> >
> > Contact Email:
> > tte@cs.fau.de
> >
> > Type of Assignment:
> >  Early allocation of 2 SMI-number registry code points according to
> > RFC7120 to be assigned to draft-ietf-anima-autonomic-control-plane
> >
> > Registry:
> > 1) https://www.iana.org/assignments/smi-numbers/smi-
> > numbers.xhtml#smi-numbers-1.3.6.1.5.5.7.0
> >   id-mod-anima-acpnodename-2020
> > 2) https://www.iana.org/assignments/smi-numbers/smi-
> > numbers.xhtml#smi-numbers-1.3.6.1.5.5.7.8
> >   id-mod-anima-acpnodename-2020
> >
> > See first two request paragraphs of IANA section of document
> >
> > Description:
> > Early implementations, interop testing. RFC7120 process was followed,
> > approval by rwilton@cisco.com today (AD for responsible WG)
> >
> > Additional Info:
> > Will CC you on mail with AD approval.


From nobody Tue Jul  7 17:27:31 2020
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 2CEF13A0CA4 for <anima@ietfa.amsl.com>; Tue,  7 Jul 2020 17:27:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level: 
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, 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 GFKKL_vB_C9j for <anima@ietfa.amsl.com>; Tue,  7 Jul 2020 17:27:27 -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 C3A813A0CA3 for <anima@ietf.org>; Tue,  7 Jul 2020 17:27:26 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 327EA548442; Wed,  8 Jul 2020 02:27:20 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 250CC440043; Wed,  8 Jul 2020 02:27:20 +0200 (CEST)
Date: Wed, 8 Jul 2020 02:27:20 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Amanda Baber via RT <iana-prot-param@iana.org>
Cc: warren@kumari.net, rwilton@cisco.com, jiangsheng@huawei.com, housley@vigilsec.com, anima@ietf.org
Message-ID: <20200708002720.GA13657@faui48f.informatik.uni-erlangen.de>
References: <RT-Ticket-1173842@icann.org> <20200707142500.GZ13952@faui48f.informatik.uni-erlangen.de> <rt-4.4.3-18048-1594132337-1419.1173842-37-0@icann.org> <rt-4.4.3-18048-1594150127-1191.1173842-37-0@icann.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <rt-4.4.3-18048-1594150127-1191.1173842-37-0@icann.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/CGElnhNU_mO-Vt22kQKScSYmO8Y>
Subject: Re: [Anima] [IANA #1173842] Request for Assignment (smi-numbers, draft-ietf-anima-autonomic-control-plane)
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, 08 Jul 2020 00:27:29 -0000

Thank you very much, Amanda!

On Tue, Jul 07, 2020 at 07:28:47PM +0000, Amanda Baber via RT wrote:
> Hi Toerless, all,
> 
> We've added the following early allocation to the SMI Security for PKIX Module Identifier (1.3.6.1.5.5.7.0) registry:
> 
> 97	id-mod-anima-acpnodename-2020 (TEMPORARY - registered 2020-07-07, expires 2021-07-07)	[draft-ietf-anima-autonomic-control-plane-27]
> 
> We've also added the following early allocation to the SMI Security for PKIX Other Name Forms (1.3.6.1.5.5.7.8) registry:
> 
> 10	id-on-AcpNodeName (TEMPORARY - registered 2020-07-07, expires 2021-07-07)	[draft-ietf-anima-autonomic-control-plane-27]
> 
> Please see
> https://www.iana.org/assignments/smi-numbers
> 
> If the document hasn't been approved by the IESG by May 2021, we'll contact you about renewing for another year.
> 
> Best regards,
> 
> Amanda Baber
> Lead IANA Services Specialist
> 
> On Tue Jul 07 14:32:17 2020, tte@cs.fau.de wrote:
> > Dear IANA
> > 
> > In followup to subject early allocation request:
> > 
> > RFC7120 justifications:
> >   https://mailarchive.ietf.org/arch/msg/anima/X3h4AUHg2sMdyatpkZAliOhJEMs
> > 
> > AD Approval for early allocation:
> >   https://mailarchive.ietf.org/arch/msg/anima/lpkxTrFWOnvo_khhQ-
> > G7wx8oEzs/
> > 
> > Registry expert feedback (Russ Housley):
> >  https://mailarchive.ietf.org/arch/msg/anima/r59nWsxMKFI968uMpKIgaBXp6Eg/
> >  (corect use of registry. mentioned missing word in text was fixed
> >   in latest version of draft).
> > 
> > Cheers
> >     Toerless
> > 
> > On Tue, Jul 07, 2020 at 02:08:59PM +0000, tte@cs.fau.de wrote:
> > >
> > > Contact Name:
> > > Toerless Eckert
> > >
> > > Contact Email:
> > > tte@cs.fau.de
> > >
> > > Type of Assignment:
> > >  Early allocation of 2 SMI-number registry code points according to
> > > RFC7120 to be assigned to draft-ietf-anima-autonomic-control-plane
> > >
> > > Registry:
> > > 1) https://www.iana.org/assignments/smi-numbers/smi-
> > > numbers.xhtml#smi-numbers-1.3.6.1.5.5.7.0
> > >   id-mod-anima-acpnodename-2020
> > > 2) https://www.iana.org/assignments/smi-numbers/smi-
> > > numbers.xhtml#smi-numbers-1.3.6.1.5.5.7.8
> > >   id-mod-anima-acpnodename-2020
> > >
> > > See first two request paragraphs of IANA section of document
> > >
> > > Description:
> > > Early implementations, interop testing. RFC7120 process was followed,
> > > approval by rwilton@cisco.com today (AD for responsible WG)
> > >
> > > Additional Info:
> > > Will CC you on mail with AD approval.

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


From nobody Tue Jul  7 18:48:07 2020
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 AC76B3A0D48 for <anima@ietfa.amsl.com>; Tue,  7 Jul 2020 18:48:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 yllNmqumLFX9 for <anima@ietfa.amsl.com>; Tue,  7 Jul 2020 18:48:03 -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 213CA3A0D05 for <anima@ietf.org>; Tue,  7 Jul 2020 18:48:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 14EC83899E; Tue,  7 Jul 2020 21:45:07 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id glf2avSzbnjZ; Tue,  7 Jul 2020 21:45:06 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 74D4F3899D; Tue,  7 Jul 2020 21:45:06 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id E87A9A0B; Tue,  7 Jul 2020 21:47:59 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org, Benjamin Kaduk <kaduk@mit.edu>
X-Attribution: mcr
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512; protocol="application/pgp-signature"
Date: Tue, 07 Jul 2020 21:47:59 -0400
Message-ID: <8942.1594172879@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/TiAVZxP3T6FL9PhI2FjgEt8uNO4>
Subject: [Anima] ACP RPL root
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, 08 Jul 2020 01:48:05 -0000

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


Ben, is this DISCUSS comment still alive?

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

In LLNs, it is common to designate a specific, high-capacity node as the RPL
root.

In particular, in non-storing mode, the RPL root has to keep a RIB and FIB
for every single node, while the other nodes need only three to five FIB
entries to keep track of parents and active children.

We are using storing mode, so every node already has to have the capacity to
have a RIB and FIB on the order of the number of ACP nodes.
This is not arduous for an Enterprise or ISP class router.
That's the major cost of being the root: the root has to have a complete
table. (But, in storing mode, we only have next-hop, not the full path)

As originally envisioned, the automonic network should be self-forming and
self-healing, which means that partitions of the network should recognize
that there is no root, and choose one.  That level of autonomy is not
reached in this document, or in the ANIMA architecture. In fact, that
level of autonomy got spun off as the SUPA WG.

So, yes, in theory, all ACP nodes could be the RPL root, and when they do,
they need to install blackhole route for ULA space fd00::/10 in order to
prevent loops.  This shouldn't be a big deal.

The RPL DODOG root will in mature situations be the ACP registrar,
and while the market is less mature, in an router designated as the
ACP-connect.

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

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

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

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl8FJc8ACgkQgItw+93Q
3WUhoAf/bl9BVElcKnXgXCdKDVaaYEifmcWztR5cM6NlUtCpLjVR59zuPGcv+9Zb
EhJFNAFOMUIPaRZsHz7scE617+HH+l/3GmJP1jJmBTB4+boJC+rzZ8SR4/wxamBK
dFCwYeumG6RnXGxVhvRn6qLqi5nuIzVKrIgut+4cAwONtdcNWRNrOEUkl4xErhYH
hsSumxwlY05qjM8OD0JllvSsA43w+X3E5AarkkmhFzzHHD+nY/JUG3zr3ATIGeR7
wJ9Rbv3ohbMyK36nuJxTmNdsiWLvy7llOvkI2ux0UBO36Shkh86eeRCIQYfaajne
/dIl91XwHt7SD8oIkproVhEG0FO9iQ==
=S6hg
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Jul  7 19:21:39 2020
Return-Path: <kaduk@mit.edu>
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 EFDA73A0FCC for <anima@ietfa.amsl.com>; Tue,  7 Jul 2020 19:21:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level: 
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5bFguylRbaY0 for <anima@ietfa.amsl.com>; Tue,  7 Jul 2020 19:21:32 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 79D163A0FA1 for <anima@ietf.org>; Tue,  7 Jul 2020 19:21:32 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 0682LRWL026969 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 7 Jul 2020 22:21:30 -0400
Date: Tue, 7 Jul 2020 19:21:26 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: anima@ietf.org
Message-ID: <20200708022126.GC16335@kduck.mit.edu>
References: <8942.1594172879@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8942.1594172879@localhost>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/s82u_el8GOhgwF_IAqVWCArJskc>
Subject: Re: [Anima] ACP RPL root
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, 08 Jul 2020 02:21:37 -0000

On Tue, Jul 07, 2020 at 09:47:59PM -0400, Michael Richardson wrote:
> 
> Ben, is this DISCUSS comment still alive?

>From memory, I think it's been resolved.

I'm sure that a discuss about whether/how the RPL root is automatically
determined got resolved for *some* document, but am not 100% sure if it was
this one or one of the 6TiSCH ones.  In any case, the discussions that
preceded that resolution also served to educate me about some of the finer
points that I had completely missed with my original comment, and that
education (combined with your description below) convinced me that there's
not a (certainly discuss-level, and probably not any) issue here.

-Ben

> > 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?
> 
> In LLNs, it is common to designate a specific, high-capacity node as the RPL
> root.
> 
> In particular, in non-storing mode, the RPL root has to keep a RIB and FIB
> for every single node, while the other nodes need only three to five FIB
> entries to keep track of parents and active children.
> 
> We are using storing mode, so every node already has to have the capacity to
> have a RIB and FIB on the order of the number of ACP nodes.
> This is not arduous for an Enterprise or ISP class router.
> That's the major cost of being the root: the root has to have a complete
> table. (But, in storing mode, we only have next-hop, not the full path)
> 
> As originally envisioned, the automonic network should be self-forming and
> self-healing, which means that partitions of the network should recognize
> that there is no root, and choose one.  That level of autonomy is not
> reached in this document, or in the ANIMA architecture. In fact, that
> level of autonomy got spun off as the SUPA WG.
> 
> So, yes, in theory, all ACP nodes could be the RPL root, and when they do,
> they need to install blackhole route for ULA space fd00::/10 in order to
> prevent loops.  This shouldn't be a big deal.
> 
> The RPL DODOG root will in mature situations be the ACP registrar,
> and while the market is less mature, in an router designated as the
> ACP-connect.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-



From nobody Thu Jul  9 12:02:56 2020
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 E17A23A0E7B for <anima@ietfa.amsl.com>; Thu,  9 Jul 2020 12:02:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gnaV6H7XVpUK for <anima@ietfa.amsl.com>; Thu,  9 Jul 2020 12:02:42 -0700 (PDT)
Received: from gw-eagle1.siemens.com (gw-eagle1.siemens.com [194.138.20.72]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 721BD3A0F19 for <anima@ietf.org>; Thu,  9 Jul 2020 12:02:17 -0700 (PDT)
Received: from mail2.dc4ca.siemens.de (mail2.dc4ca.siemens.de [139.25.224.94]) by gw-eagle1.siemens.com (Postfix) with ESMTPS id 393774F004E; Thu,  9 Jul 2020 21:02:15 +0200 (CEST)
Received: from DEMCHDC89YA.ad011.siemens.net (demchdc89ya.ad011.siemens.net [139.25.226.104]) by mail2.dc4ca.siemens.de (Postfix) with ESMTPS id 7F90314D1CB75; Thu,  9 Jul 2020 21:02:13 +0200 (CEST)
Received: from DEMCHDC8A1A.ad011.siemens.net (139.25.226.107) by DEMCHDC89YA.ad011.siemens.net (139.25.226.104) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Thu, 9 Jul 2020 21:02:13 +0200
Received: from DEMCHDC8A1A.ad011.siemens.net ([139.25.226.107]) by DEMCHDC8A1A.ad011.siemens.net ([139.25.226.107]) with mapi id 15.01.1979.003;  Thu, 9 Jul 2020 21:02:13 +0200
From: "Fries, Steffen" <steffen.fries@siemens.com>
To: "jiangsheng@huawei.com" <jiangsheng@huawei.com>, Toerless Eckert <tte@cs.fau.de>
CC: "anima@ietf.org" <anima@ietf.org>
Thread-Topic: Rquest for a timeslot slot for the ANIMA WG meeting at IETF 108
Thread-Index: AdZWI3NiZiraoI8pShODmV2yRpsXVQ==
Date: Thu, 9 Jul 2020 19:02:13 +0000
Message-ID: <9a55c0e3eacf4063a339bf22f0b19a74@siemens.com>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [144.145.220.65]
x-tm-snts-smtp: 8E9E97769E8273AF4AD8B4D9B7AFF9C58F23B4FBBA5EDF48D0F68B67BDC8D4942000:8
Content-Type: multipart/related; boundary="_004_9a55c0e3eacf4063a339bf22f0b19a74siemenscom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/e215FW1SvL7CmAYSIyGXcPoMRVw>
Subject: [Anima] Rquest for a timeslot slot for the ANIMA WG meeting at IETF 108
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, 09 Jul 2020 19:02:51 -0000

--_004_9a55c0e3eacf4063a339bf22f0b19a74siemenscom_
Content-Type: multipart/alternative;
 boundary="_000_9a55c0e3eacf4063a339bf22f0b19a74siemenscom_"

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

Hi Toerless, hi Sheng,

Sorry for jumping forward as you haven't send out the agenda request email.=
 I will be not available in the next two weeks, hence my early email regard=
ing a slot in the agenda.
I'm currently preparing the submission of the draft-ietf-anima-brski-async-=
enroll-00 after the WG adoption beginning of the week. I would already incl=
ude refinements based on the feedback we got before submitting the updated =
version (probably tomorrow. I would like to use the slot in the WG meeting =
to discuss the changes and the next steps.

Name of time slot: Support of asynchronous enrollment in BRSKI
Name of draft(s): draft-ietf-anima-brski-async-enroll-00
Time requested: 15 min
Presenter name(s): Steffen Fries

Best regards
Steffen

--
Steffen Fries
Siemens AG
Corporate Technology
Research in Digitalization and Automation
Cybersecurity Technology
CT RDA CST
Otto-Hahn-Ring 6
81739 Muenchen, Germany
Tel.: +49 89 780-522928
Fax: +49 89 636-48000
mailto:steffen.fries@siemens.com
www.siemens.com/ingenuityforlife<https://siemens.com/ingenuityforlife>
[cid:image001.gif@01D65602.F785C230]
Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Jim Hagemann=
 Snabe; Managing Board: Joe Kaeser, Chairman, President and Chief Executive=
 Officer; Roland Busch, Klaus Helmrich, Cedrik Neike, Ralf P. Thomas; Regis=
tered offices: Berlin and Munich, Germany; Commercial registries: Berlin Ch=
arlottenburg, HRB 12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322


--_000_9a55c0e3eacf4063a339bf22f0b19a74siemenscom_
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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi Toerless, hi Sheng,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Sorry for jumping forward as you haven&#8217;t send =
out the agenda request email. I will be not available in the next two weeks=
, hence my early email regarding a slot in the agenda.
<o:p></o:p></p>
<p class=3D"MsoNormal">I&#8217;m currently preparing the submission of the =
draft-ietf-anima-brski-async-enroll-00 after the WG adoption beginning of t=
he week. I would already include refinements based on the feedback we got b=
efore submitting the updated version (probably
 tomorrow. I would like to use the slot in the WG meeting to discuss the ch=
anges and the next steps. &nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Name of time slot: Support of asynchronous enrollmen=
t in BRSKI
<o:p></o:p></p>
<p class=3D"MsoNormal">Name of draft(s): draft-ietf-anima-brski-async-enrol=
l-00<o:p></o:p></p>
<p class=3D"MsoNormal">Time requested: 15 min<o:p></o:p></p>
<p class=3D"MsoNormal">Presenter name(s): Steffen Fries<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best regards<o:p></o:p></p>
<p class=3D"MsoNormal">Steffen<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,sans=
-serif">--<br>
Steffen Fries<br>
Siemens AG<br>
Corporate Technology<br>
Research in Digitalization and Automation<br>
Cybersecurity Technology<br>
CT RDA CST<br>
Otto-Hahn-Ring 6<br>
81739 Muenchen, Germany <br>
Tel.: &#43;49 89 780-522928<br>
Fax: &#43;49 89 636-48000<br>
</span><a href=3D"mailto:steffen.fries@siemens.com"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:blue">mailto:steffe=
n.fries@siemens.com</span></a><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,sans-serif"><br>
</span><a href=3D"https://siemens.com/ingenuityforlife"><span style=3D"font=
-size:10.0pt;font-family:&quot;Arial&quot;,sans-serif;color:blue">www.sieme=
ns.com/ingenuityforlife</span></a><span style=3D"font-size:10.0pt;font-fami=
ly:&quot;Arial&quot;,sans-serif"><br>
<img border=3D"0" width=3D"240" height=3D"87" style=3D"width:2.5in;height:.=
9062in" id=3D"Picture_x0020_1" src=3D"cid:image001.gif@01D65602.F785C230"><=
br>
</span><span style=3D"font-size:8.0pt;font-family:&quot;Arial&quot;,sans-se=
rif">Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Jim Hag=
emann Snabe; Managing Board: Joe Kaeser, Chairman, President and Chief Exec=
utive Officer; Roland Busch, Klaus Helmrich,
 Cedrik Neike, Ralf P. Thomas; Registered offices: Berlin and Munich, Germa=
ny; Commercial registries: Berlin Charlottenburg, HRB 12300, Munich, HRB 66=
84; WEEE-Reg.-No. DE 23691322</span><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_9a55c0e3eacf4063a339bf22f0b19a74siemenscom_--

--_004_9a55c0e3eacf4063a339bf22f0b19a74siemenscom_
Content-Type: image/gif; name="image001.gif"
Content-Description: image001.gif
Content-Disposition: inline; filename="image001.gif"; size=3536;
 creation-date="Thu, 09 Jul 2020 19:02:12 GMT";
 modification-date="Thu, 09 Jul 2020 19:02:12 GMT"
Content-ID: <image001.gif@01D65602.F785C230>
Content-Transfer-Encoding: base64

R0lGODlh8ABXAPcAAAAAAP///4HMzr7i49Pt7tLr7ACcnQCbnACamwCZmgCYmQCXmACWlwCVlgCU
lQCTlACSkwCRkgCQkQCPkACOjwCNjgCMjQCLjACKiwCJigCIiQCHiACGhwCFhgCEhQCBhACDhACC
gwCBggCAgQB/gAB+fwB9fgB8fQB5egB3eABzdAKZmgSamwabnAecnQibnQycnQ6foBGfoEW0tVm2
t1+/wIXOz6DX2AaWlgidnQibmwyVlQ2eng6dnQ+fnxKgoBOZmBaiohijoxqkpBmdnRumphykpB6l
pSCmpiKfnyWoqC6rqy2mpjCvrzqzszuwsD20tD2ysTqpqUCysj+srEW3t0a3t0e1tUi2tkq3t0mw
sE24t0y1tU+7ukyzslK6ulW7u1a8u1e8vFi8u1q+vlq7u1y5uWbCwmvExHHFxXnMy3bIyHvLyn3L
y37MzIHOzoLOzYLNzYLJyYjQ0I3R0ZHS0o7OzpvV1Z7Y2KHZ2aDX16Xb26fc26fc3Kbb26TY2Krd
3a3e3a/f37Ph4a3a2rbi4rrk5Lnj47bf37vi4r7l5cXo6MPm5sjo6NDs7NDr69Ls7NDp6dbv79Xu
7tvx8dju7t3y8t3x8d/y8uHz8+P09OLz8+Hy8uv6+uLx8ef19e/7++v39+/5+e74+PH6+vL6+vH5
+fX7+/f8/Pr+/vr9/fn8/P7///3+/nXIxrbl47rk48zr6tPu7dTu7djw7+T19OP08+Ly8ff8+/39
/fr6+vj4+Pf39/X19fLy8u3t7erq6ubm5uHh4d/f39zc3Nra2tXV1dHR0c/Pz8rKysXFxcLCwr29
vbe3t7Ozs7CwsK2trampqaWlpaOjo6CgoJubm5OTk42NjYqKioWFhYKCgn19fXp6enZ2dnJycm9v
b21tbWpqamZmZmJiYl5eXlpaWlVVVVJSUk1NTUhISEVFRT8/Pzk5OTc3NzIyMjExMS0tLSoqKiYm
JiIiIh8fHxwcHBkZGRUVFRMTEw4ODgoKCggICAcHBwMDAwEBAf///yH5BAEAAP8ALAAAAADwAFcA
AAj/AAMIHEiwoMGDCBMqXMiwocOHECNKnEixosWLGDNq3Mixo8ePIEOKHEmypMmTKFOqXMmypcuX
MGPKnEmzps2bOHPq3Mmzp8+fQIMKHUq0qNGjSJMqXcq0qdOnUKNKnUq1qtWrWLNq3cq1q9evYMOK
HUu2rNmzaNOqXcu2bUdKiQAFUlQpFcFVmjTV2jRqIKtPemsJHlxL0yZUAkttGnyrFEJVngQbPjUQ
1abAhAXb+jRw1OJatzoVPHW5ViuDnAYEAnQIkmO3FfVQgXAhA4YKD4CgGbgIAoMEGsQMLPUjQoLj
yI8vqDBIYBwNyCcgQejkwnEFF/YMPERhQfLkEoSo/xIIBnoCBztsEQR0AUICTAQFaXFgAQMGCxB2
1IA9kQwJDQ1QsAEHG2BwQhADMXLBBBCMsMVApLCAAQQPSFDBhRdiQAIgArExAgQgQhACHwZhYgGD
EEQAQh4DFbKBBBROgOGFHygwXgBZfEhhCV0QtAcI7V0ykBoidODABBoQqKEC/EWEhwkNICCBEVuQ
cYUSHPxwWgCLRNCAAhuEMZwMEiigwHcJLNdcAHFsYOaZHEBhUBodJGDmAhhoJ9AhFTBwJpoTiEee
m2Y+EEEtAwGCQQQKwBeAISBAcMAEMmBBRhZKWKDAlk02hEQGCWRQRkGQCHJjl1+GOWaZGpyRyauw
cv+CGJtuLmBmAxNMQlArLkzwJp56BsAnAwtYUAesr3KiCSuDvpmABz0KpCijjkZR5wVTrEIQJYHM
2ulCprDAKAeuKIQqmGImRqYCHrihUJsJMNDAcSCoQVAgbn6pALDb9blABmsiBMYGCTQwL32OSLto
owL9QAGYY3xL0SktlLlABGbEgtC5qqpbZgdsvLuBA0gE4R4FQdwYQBMZPHDED8Tm2S+xGQii0MAL
tGArAiBYoTC1Ag1RgZkUeKGIxBJNAQIC8XYwAQ2MGMRxugGUsu4GaJQiytaijKJymxV0EQcGdnJg
cwC0TPCADnTI0AC/e/p7wR1abz2KKcwOekENWID/2kAFCfexsKM1jMA0mBZogQjSD8mSQQYInOmA
BxVooTFvXqK76r4t+MDD5zDsEHCbFEQRCgsPJNBBtDV4kIEYoTzwtsxx+6mAC55/vgMS3g68wRqU
ZLAAz1UEEMjgAtWCgwd2No0BFYUw3tAgQIRAAXINeIDBG5inSrXVZRowQQgglP+BCngMRPp0Z9T5
wAOUxUABB7GoIsHswQ6rwAEXkF8+ChWgzKA08CAncKBgFygFLTIANIE4IgkfGNpxGNCBDaRBegwB
RRqI0IELnElKI7iDQKa2OQcMIQpPSOETpBA152yAAkYIgCPclAAQDGISHJhADgJACS/BTVh9UgAD
/5SAwhRKIQsqG5gGZhAASGiAAQjoQBocUYEGCoQVckjCBjTgHQQ84ATuwuBCcGEHJnAgAgcIlQxO
Q0KPKQBkIqPAEQRSBAskIAJLWMIEPHCGADTCh7QDIs3OJrAtXkEgUDjgAlZQgxZYkSB3kEIGJpDG
CTiAM2JkyB2A8AAFyA4+bazaujiwhjjOMQB0YB4CUnQx+PwRfzPDUx9uZkiBzCIDv5lXCyDAMIQE
ggiMUoAGOJRJhswBBApwQAOEFErwsSuMCCHdEZiliQg44E0baIJAXvnDYS1AA9FLiBIPKZAqME8B
X+KloxDyig7YKgOzLOZAFDEAAQoEF1ywjgV4MP+eZq4rAzWQxCQGOtAChMKFcsxbFupkJg74YZuA
zJ+/KjAHgRJ0EgQQ4DgHQgsLXNNM6hwhIkxRkDN4EESUkOdAsnACGSwhC1+YQRAmgIAFmCBkXMpc
x0RZpjQ1wAFABWoIbIDQaQrEEBogWgwGws1A6i9ePw0qBDIAiwGSUyBkWBpIe4kGFPRgCVf4AhaO
8LAEmIAMKh2IGEowgQtoYIsTWMAFSnBVRlTRASCIVtVe4NEGVEgCgAVsCQQgkDaAAANByFsAlIAB
BYQAp1yq4gM4wCKBFCIDEFAmBAILWAp44BAC6QIIPDCFbZ0IqBRwgCUEsgYTSMACb9VAdypQgiX/
aCutAVgDB9w6oC1agAl1IIiCJPAAETxIIBHCwPuWy1wREDUAbBCBBn6gWDikQHuZ4M0FYOSBygbA
RRFgLnMjsAFDCGQLIghBFEoqAgpZ4AFCCkAdNADb3m7gAkmQA24H0gpaJOIGdZhDHf7QCIOc4hGO
cEQksiuQVhAAwQmOcIQjcdAAfCISj5AEQUpBCEKYdyAHTvAj+pIYCEtYwo94TSYiEYn4+iUSInaE
yiwxgDwEmA56aOF+d8zjHvv4x0AOspCHTOQiG5krvnhHN2ACDWlAxBrT6AgwiswMAMhjJdJghkCA
AYB7PGQbAADANiAijG0YYyDMaMZA0gEAbhDZ/xoAyMZKtAEAZwTAGwBIhkO4bI5nyPkh9QAAMQYC
jTYHwBkAMEc6gjFkNiuDJcpARgDy0Y+HhAMAw4hIMgDwjYI4I8r24IdAeiHkXABAH7mgCDSWkREA
lMMhueAHPSRSDkEfhBgACEeRiwGAdAhkHfXwxUF+QQ5sIEPYAdjFOuhhD2sIBB3kOIgz1CyQTAfA
F9HQRTDofA5oHIMgvEiGLgqiDABEoyG6+IVATD3rg1QDAFoWCDP0/ONnAEAbAfhFmAMQjHO4WSDL
AMA73HHvAOgiHvUARj90jQwA7EMg2KA2L8J8GmEAYMnUAEA1ghFmeazDHvAYdCvgAYBHE4TO1v+A
BjOWYY56jDkA0sBGLqzhjnZ4g9TGAAA4BtILbXw7AOvIh0CQoY55yKMbnNrxNQDwjAC8exmtCHPJ
A4DrK4sDAKwuNDvY4Q2BfAMAZ7ZHmB8tDQB0PQD3cHUAwGHuOwNA3eQAwLjX4WpeGJwa57CHPk5d
j32E+epdv3Q+cp0MX6Ta3tQYCDoAMA1iXBoA6ogHAIRO9134+NLCCECtnaEPcdgb3yTnRdnnEQBj
pH3RAoGzPoIhD3Y0Q+BO1/gw5MEPAGAjAOYAQOa/Pu6Ao0MdsB81PQCw+HdMeR4AsDueA7B0APx8
IHBmdQC+7g9fCKMfVt5G2eFRDno42cdsFoj/5HstfgAU4xwAwEff2UEOdnx9HseAhjveEXcAtJvO
1wjAO/6+C8jH3s72JmmlV3+DtisB0A/iIBBxlwxVB3QAAA0GEQ15pnn4QHDj1nDnpnkAkIBAlnsC
MQ36sA4DoQvk0GnUYA29oA+dJ2zHoA73EA+6tnbowCnYYA/fdg3Udg3mcBrgkIHoEGVbBgDRZhDH
YHsDEQ7+AADwoG7x8HAGoQvroA/4AAC+8G7ClnHPNw79gA7coA3d0HQ7RgwZmG8K0Q5qRxCWtxBT
ZhBJt24DQXeMZhABB4QCUQwml2+ZhxDZ0A2W1wvZkHl0pm4DsQzigA7n0A1ndmR1CAAEx4EircFx
54AQr0dtGvF1pKaICqELADAOAQAA+TcS40CFCJFzdJgRX5dqmJgQtRYA5RZvIpFoCmEO36cRGbeG
qWgQ/edmXyeIIXF1dncSunANeXiLBfF6mTYP+DASveCJxCgT9iYQAJB4IiEP8NCMMqEL7HAO96AO
I8EN/jBu1hgTuTAO/yYS1GCL4ZiO6riO7NiO7viO8BiP8jiP9FiP9niP+JiP+riP/NiP/viP+xUQ
ADs=

--_004_9a55c0e3eacf4063a339bf22f0b19a74siemenscom_--


From nobody Thu Jul  9 14:48:03 2020
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 4FCE73A08E7 for <anima@ietfa.amsl.com>; Thu,  9 Jul 2020 14:48:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level: 
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, 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 dKyUzfXXvrbL for <anima@ietfa.amsl.com>; Thu,  9 Jul 2020 14:47:58 -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 121DD3A07A8 for <anima@ietf.org>; Thu,  9 Jul 2020 14:47:57 -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 F3393548441; Thu,  9 Jul 2020 23:47:52 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id EAC2F440043; Thu,  9 Jul 2020 23:47:52 +0200 (CEST)
Date: Thu, 9 Jul 2020 23:47:52 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: "Fries, Steffen" <steffen.fries@siemens.com>
Cc: "jiangsheng@huawei.com" <jiangsheng@huawei.com>, "anima@ietf.org" <anima@ietf.org>
Message-ID: <20200709214752.GA57118@faui48f.informatik.uni-erlangen.de>
References: <9a55c0e3eacf4063a339bf22f0b19a74@siemens.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9a55c0e3eacf4063a339bf22f0b19a74@siemens.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/nmijSux46V_Zwf3q1t4d9-6azQk>
Subject: Re: [Anima] Rquest for a timeslot slot for the ANIMA WG meeting at IETF 108
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, 09 Jul 2020 21:48:00 -0000

Thanks Steffen. added.

On Thu, Jul 09, 2020 at 07:02:13PM +0000, Fries, Steffen wrote:
> Hi Toerless, hi Sheng,
> 
> Sorry for jumping forward as you haven't send out the agenda request email. I will be not available in the next two weeks, hence my early email regarding a slot in the agenda.
> I'm currently preparing the submission of the draft-ietf-anima-brski-async-enroll-00 after the WG adoption beginning of the week. I would already include refinements based on the feedback we got before submitting the updated version (probably tomorrow. I would like to use the slot in the WG meeting to discuss the changes and the next steps.
> 
> Name of time slot: Support of asynchronous enrollment in BRSKI
> Name of draft(s): draft-ietf-anima-brski-async-enroll-00
> Time requested: 15 min
> Presenter name(s): Steffen Fries
> 
> Best regards
> Steffen
> 
> --
> Steffen Fries
> Siemens AG
> Corporate Technology
> Research in Digitalization and Automation
> Cybersecurity Technology
> CT RDA CST
> Otto-Hahn-Ring 6
> 81739 Muenchen, Germany
> Tel.: +49 89 780-522928
> Fax: +49 89 636-48000
> mailto:steffen.fries@siemens.com
> www.siemens.com/ingenuityforlife<https://siemens.com/ingenuityforlife>
> [cid:image001.gif@01D65602.F785C230]
> Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Jim Hagemann Snabe; Managing Board: Joe Kaeser, Chairman, President and Chief Executive Officer; Roland Busch, Klaus Helmrich, Cedrik Neike, Ralf P. Thomas; Registered offices: Berlin and Munich, Germany; Commercial registries: Berlin Charlottenburg, HRB 12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322
> 



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


From nobody Thu Jul  9 20:07:26 2020
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 CAB703A0C63; Thu,  9 Jul 2020 20:07:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, 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 KmY_ZoxF2Ymn; Thu,  9 Jul 2020 20:07:22 -0700 (PDT)
Received: from mail-pf1-x443.google.com (mail-pf1-x443.google.com [IPv6:2607:f8b0:4864:20::443]) (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 557503A0C64; Thu,  9 Jul 2020 20:07:22 -0700 (PDT)
Received: by mail-pf1-x443.google.com with SMTP id a14so1909603pfi.2; Thu, 09 Jul 2020 20:07:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:subject:organization:to:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=lrqaFB/mVHyObGjfKIfAxYHsi5OdV1aBLXMUejAYfEw=; b=IcTwaDJ7/cxUljEiOce65JFkgwu05/POtPXw6qJgBdNWUi7/nNL3PdcIzKUKefIODT 1S9xHu/8crPsMudmGNHwFXQIhqb9CEhBmBbr9cnnyOYpRGB7FX34x84EF+WxTSy/xdvq 4X1DG/4lGVaADx28VrBFw2ZoZZcY8oXNcirZBQvdsWbwFo8o2ww3kx3IS6Ee1G+TSBNY x/T1qbc4ZtmCu+A2eGADA//msXvyWwWe5YEna3AE7mRxti8HPTjUG2YrEMS7w7TjGN1n vWDHC0s9cbI8T3n1YQvAP4nuXP9E3a6G5UKoqMd55dOup8hjDV4HM+5Mv882F5dC+IOe rZ4w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:organization:to:message-id:date :user-agent:mime-version:content-language:content-transfer-encoding; bh=lrqaFB/mVHyObGjfKIfAxYHsi5OdV1aBLXMUejAYfEw=; b=BMAR/5oZpGTAdRk0J8IYroDOH//uPW8Dhv7jNmiIP6l99vZMspkeYdeOP7vxjNJ/I3 MIa+Ndro++OeSonhqrvyqeucEfNTmnEOtlGGxf56vD8V/IvHGSDXwZOYd+psD61jqRJ7 Sj8jWGPocdEnMqYKHFE+7oTGeQM0A8ycnQ0MOQLADD5kX0Ze+3Y9wWJ6Eip+3ZGotS6c JWVPEgXQLtfUei0Nkod3ud2hL9AutKOOEL6v+okr8VuGEDXluPyXe7u5wCLwt5SH+aJg wnTmm726wweNfB6yJvkUbIJnBRx7uj7u6ld/xdtjePaC60yFBV3OjIV3+Vps3OJ0ArQh /SVg==
X-Gm-Message-State: AOAM530xwQPyzDYcwzrMLky9AXmiIgxaSJsEQUf9LmAB3fgCZxHJiXCU XOI6sxar/vWA5Ox9b9C/2puWRnGw
X-Google-Smtp-Source: ABdhPJw3NAluqFWYgT6Ze6V9upPOhNvA3UOvvA4ERTgxKzv5ROcfUNCZxB1pLG+sdA7Cofizijybyw==
X-Received: by 2002:a63:7054:: with SMTP id a20mr54895481pgn.17.1594350441282;  Thu, 09 Jul 2020 20:07:21 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.132.13]) by smtp.gmail.com with ESMTPSA id a16sm3970580pgj.27.2020.07.09.20.07.19 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Jul 2020 20:07:20 -0700 (PDT)
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
To: Anima WG <anima@ietf.org>, draft-ietf-anima-autonomic-control-plane.all@ietf.org
Message-ID: <48c611ca-ded6-ea5a-732d-4940022f717f@gmail.com>
Date: Fri, 10 Jul 2020 15:07:16 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/C91ZVcnC1ji60W-Prp2aWyWDb1k>
Subject: [Anima] Minor nits in ACP examples (draft-ietf-anima-autonomic-control-plane-27)
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, 10 Jul 2020 03:07:24 -0000

Following a request from Toerless, I've carefully checked the example GRASP
messages in draft-ietf-anima-autonomic-control-plane-27.

Firstly Figure 3: GRASP SRV.est example. There are two nits:

(1) The ULA address is short by one hex digit.
(2) The GRASP objective lacks a value; for correct message syntax, we need a null value.
(This is 'any' in the CDDL syntax, which effectively makes it an extension point).

OLD:

        [M_FLOOD, 12340815, h'fd89b714f3db0000200000064000001', 210000,
            [["SRV.est", 4, 255 ],
            [O_IPv6_LOCATOR,
                 h'fd89b714f3db0000200000064000001', IPPROTO_TCP, 443]]
        ]

NEW:

        [M_FLOOD, 12340815, h'fd89b714f3db00002000000640000001', 210000,
            [["SRV.est", 4, 255, null ],
            [O_IPv6_LOCATOR,
                 h'fd89b714f3db00002000000640000001', IPPROTO_TCP, 443]]
        ]

Once serialized and CBORed, the actual message payload would be
0x85091a00bc4e4f50fd89b714f3db000020000006400000011a000334508284675352562e6573740418fff684186750fd89b714f3db00002000000640000001061901bb

Second, Figure 5: GRASP AN_ACP example. There is one nit and one quibble.

1) There's a missing comma between two elements
2) It's against the GRASP spec to have the same session ID in two different flood messages.
So I believe we should change the session ID for this example.

OLD:

       [M_FLOOD, 12340815, h'fe80000000000000c0011001feef0000', 210000,
         [["AN_ACP", 4, 1, "IKEv2" ],
          [O_IPv6_LOCATOR,
               h'fe80000000000000c0011001feef0000', IPPROTO_UDP, 15000]]
         [["AN_ACP", 4, 1, "DTLS" ],
          [O_IPv6_LOCATOR,
               h'fe80000000000000c0011001feef0000', IPPROTO_UDP, 17000]]
       ]

NEW:

       [M_FLOOD, 43215108, h'fe80000000000000c0011001feef0000', 210000,
         [["AN_ACP", 4, 1, "IKEv2" ],
          [O_IPv6_LOCATOR,
               h'fe80000000000000c0011001feef0000', IPPROTO_UDP, 15000]],
         [["AN_ACP", 4, 1, "DTLS" ],
          [O_IPv6_LOCATOR,
               h'fe80000000000000c0011001feef0000', IPPROTO_UDP, 17000]]
       ]

Once serialized and CBORed, the actual message payload would be
0x86091a0293690450fe80000000000000c0011001feef00001a00033450828466414e5f414350040165494b45763284186750fe80000000000000c0011001feef000011193a98828466414e5f41435004016444544c5384186750fe80000000000000c0011001feef000011194268

Running code:

At https://github.com/becarpenter/graspy, you can find ACPcontainer-v27-examples.py, which generates GRASP floods for these two precise examples, but of course with new pseudo-random Session IDs each time, and genuine IPv6 addresses. ACPnewby.py demonstrates how a new ACP node will receive and decode the examples. Incidentally, the ACPnewby code hasn't changed since October 2017.

Regards
   Brian Carpenter


From nobody Fri Jul 10 00:28:50 2020
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 983553A0E85; Fri, 10 Jul 2020 00:28:48 -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: 7.7.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: anima@ietf.org
Message-ID: <159436612857.4549.12674051868134556506@ietfa.amsl.com>
Date: Fri, 10 Jul 2020 00:28:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/88KgedoZBZ9bMaG4GMWCsZN8xNA>
Subject: [Anima] I-D Action: draft-ietf-anima-brski-async-enroll-00.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: Fri, 10 Jul 2020 07:28:49 -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           : Support of asynchronous Enrollment in BRSKI (BRSKI-AE)
        Authors         : Steffen Fries
                          Hendrik Brockhaus
                          Eliot Lear
	Filename        : draft-ietf-anima-brski-async-enroll-00.txt
	Pages           : 35
	Date            : 2020-07-10

Abstract:
   This document describes enhancements of bootstrapping a remote secure
   key infrastructure (BRSKI) to also operate in domains featuring no or
   only timely limited connectivity between involved components.  It
   addresses connectivity to backend services supporting enrollment like
   a Public Key Infrastructure (PKI) and also to the connectivity
   between pledge and registrar.  For this it enhances the use of
   authenticated self-contained objects in BRSKI also for request and
   distribution of deployment domain specific device certificates.  The
   defined approach is agnostic regarding the utilized enrollment
   protocol allowing the application of existing and potentially new
   certificate management protocols.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-anima-brski-async-enroll/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-anima-brski-async-enroll-00
https://datatracker.ietf.org/doc/html/draft-ietf-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/



From nobody Fri Jul 10 00:40:05 2020
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 977893A0E84 for <anima@ietfa.amsl.com>; Fri, 10 Jul 2020 00:40:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 pPqcGt5yhS4Z for <anima@ietfa.amsl.com>; Fri, 10 Jul 2020 00:40:01 -0700 (PDT)
Received: from gw-eagle1.siemens.com (gw-eagle1.siemens.com [194.138.20.72]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84BA13A0E82 for <anima@ietf.org>; Fri, 10 Jul 2020 00:40:01 -0700 (PDT)
Received: from mail2.dc4ca.siemens.de (mail2.dc4ca.siemens.de [139.25.224.94]) by gw-eagle1.siemens.com (Postfix) with ESMTPS id D3AB44F000E for <anima@ietf.org>; Fri, 10 Jul 2020 09:39:59 +0200 (CEST)
Received: from DEMCHDC8A0A.ad011.siemens.net (demchdc8a0a.ad011.siemens.net [139.25.226.106]) by mail2.dc4ca.siemens.de (Postfix) with ESMTPS id CF92714D31735 for <anima@ietf.org>; Fri, 10 Jul 2020 09:39:59 +0200 (CEST)
Received: from DEMCHDC8A1A.ad011.siemens.net (139.25.226.107) by DEMCHDC8A0A.ad011.siemens.net (139.25.226.106) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Fri, 10 Jul 2020 09:39:59 +0200
Received: from DEMCHDC8A1A.ad011.siemens.net ([139.25.226.107]) by DEMCHDC8A1A.ad011.siemens.net ([139.25.226.107]) with mapi id 15.01.1979.003;  Fri, 10 Jul 2020 09:39:59 +0200
From: "Fries, Steffen" <steffen.fries@siemens.com>
To: "anima@ietf.org" <anima@ietf.org>
Thread-Topic: New Version Notification for draft-ietf-anima-brski-async-enroll-00.txt
Thread-Index: AQHWVovDv41rxIdde0a4PfZNeN7gRakAbOJA
Date: Fri, 10 Jul 2020 07:39:59 +0000
Message-ID: <6d97fc3fd7074243944dee7319cfbee0@siemens.com>
References: <159436612878.4549.16244632802362802533@ietfa.amsl.com>
In-Reply-To: <159436612878.4549.16244632802362802533@ietfa.amsl.com>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [144.145.220.66]
x-tm-snts-smtp: 3D9A08D034FA54F92C412844A1272A3A63EA1A904D5D90D495510462D85A4D982000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/HWG77OlPVp0zBxuyR4vvfMMU62I>
Subject: [Anima] FW: New Version Notification for draft-ietf-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: Fri, 10 Jul 2020 07:40:04 -0000

SGVsbG8sDQoNCkkganVzdCBzdWJtaXR0ZWQgdGhlIHVwZGF0ZWQgdmVyc2lvbiBvZiB0aGUgQlJT
S0ktQUUgZHJhZnQgYXMgV0cgZHJhZnQuDQoNCkluIHRoZSBzdWJtaXR0ZWQgdmVyc2lvbiB3ZSBh
bHJlYWR5IGluY2x1ZGVkIHVwZGF0ZXMgYW5kIGZ1cnRoZXIgcmV2aXNlZCB0aGUgdGV4dCBiYXNl
ZCBvbiBjb21tZW50cyB3ZSByZWNlaXZlZCBkdXJpbmcgdGhlIGFkb3B0aW9uIGNhbGwuIA0KV2Ug
d291bGQgbGlrZSB0byBkaXNjdXNzIHRoZSBjaGFuZ2VzIGR1cmluZyB0aGUgbmV4dCBBTklNQSBX
RyBtZWV0aW5nLiANCg0KVGhlIGNoYW5nZXMgY29tcHJpc2UgbW9zdGx5IGVkaXRvcmlhbCBjaGFu
Z2VzIHJlbGF0ZWQgdG8gcmVzdHJ1Y3R1cmluZywgIHNpbXBsaWZpY2F0aW9ucyBvZiBkZXNjcmlw
dGlvbnMgYW5kIHN0cmlwcGluZyBvZiByZXBsaWNhdGVkIGluZm9ybWF0aW9uIGZyb20gQlJTS0ku
IEEgcHJvcG9zYWwgaXMgaW5jbHVkZWQgaW4gdGhlIGRyYWZ0IGZvciBoYW5kbGluZyBkaXNjb3Zl
cnkgb2YgZW5yb2xsbWVudCBlbmRwb2ludHMgYXQgYSBkb21haW4gcmVnaXN0cmFyIGFzIG91dGxp
bmVkIGluIHRoZSBpbmRpdmlkdWFsIHN1Ym1pc3Npb24uIFdlIHdvdWxkIGxpa2UgdG8gdXNlIHNv
bWUgdGltZSBpbiB0aGUgbmV4dCBBTklNQSBXRyBtZWV0aW5nIHRvIGRpc2N1c3MvcmVmaW5lIHRo
ZXNlIHdpdGggdGhlIFdHIGFuZCBhbHNvIGRpc2N1c3MgdGhlIG5leHQgc3RlcHMgZm9yIHRoZSBk
b2N1bWVudC4gDQoNClRoZSBmb2xsb3dpbmcgbGlzdCBzdW1tYXJpemVzIHRoZSBjaGFuZ2VzIGZy
b20gaW5kaXZpZHVhbCB2ZXJzaW9uIDAzIC0+IElFVEYgZHJhZnQgMDA6DQoNCiAgIG8gIEluY2x1
c2lvbiBvZiBkaXNjb3Zlcnkgb3B0aW9ucyBvZiBlbnJvbGxtZW50IGVuZHBvaW50cyBhdCB0aGUN
CiAgICAgIGRvbWFpbiByZWdpc3RyYXIgYmFzZWQgb24gd2VsbC1rbm93biBlbmRwb2ludHMgaW4g
U2VjdGlvbiA1LjMgYXMNCiAgICAgIHJlcGxhY2VtZW50IG9mIHNlY3Rpb24gNS4xLjMgaW4gdGhl
IGluZGl2aWR1YWwgZHJhZnQuICBUaGlzIGlzDQogICAgICBpbnRlbmRlZCB0byBzdXBwb3J0IGJv
dGggdXNlIGNhc2VzIGluIHRoZSBkb2N1bWVudC4gIEFuDQogICAgICBpbGx1c3RyYXRpdmUgZXhh
bXBsZSBpcyBwcm92aWRlZC4NCg0KICAgbyAgTWlzc2luZyBkZXRhaWxzIHByb3ZpZGVkIGZvciB0
aGUgZGVzY3JpcHRpb24gYW5kIGNhbGwgZmxvdyBpbg0KICAgICAgcGxlZGdlLWFnZW50IHVzZSBj
YXNlIFNlY3Rpb24gNS4yLCBlLmcuIHRvIGFjY29tbW9kYXRlDQogICAgICBkaXN0cmlidXRpb24g
b2YgQ0EgY2VydGlmaWNhdGVzLg0KDQogICBvICBVcGRhdGVkIENNUCBleGFtcGxlIGluIFNlY3Rp
b24gNiB0byB1c2UgbGlnaHR3ZWlnaHQgQ01QIGluc3RlYWQgb2YNCiAgICAgIENNUCwgYXMgdGhl
IGRyYWZ0IGFscmVhZHkgcHJvdmlkZXMgdGhlIG5lY2Vzc2FyeSAvLndlbGwta25vd24NCiAgICAg
IGVuZHBvaW50cy4NCg0KICAgbyAgUmVxdWlyZW1lbnRzIGRpc2N1c3Npb24gbW92ZWQgdG8gc2Vw
YXJhdGUgc2VjdGlvbiBpbiBTZWN0aW9uIDQuDQogICAgICBTaG9ydGVuZWQgZGVzY3JpcHRpb24g
b2YgcHJvb2Ygb2YgaWRlbnRpdHkgYmluZGluZyBhbmQgbWFwcGluZyB0bw0KICAgICAgZXhpc3Rp
bmcgcHJvdG9jb2xzLg0KDQogICBvICBSZW1vdmFsIG9mIGNvcGllZCBjYWxsIGZsb3dzIGZvciB2
b3VjaGVyIGV4Y2hhbmdlIGFuZCByZWdpc3RyYXINCiAgICAgIGRpc2NvdmVyeSBmbG93IGZyb20g
W0ktRC5pZXRmLWFuaW1hLWJvb3RzdHJhcHBpbmcta2V5aW5mcmFdIGluDQogICAgICBzZWN0aW9u
IDUuMSB0byBhdm9pZCBkb3VibGluZyBvciB0ZXh0IG9yIGluY29uc2lzdGVuY2llcy4NCg0KICAg
byAgUmV3b3JrZWQgYWJzdHJhY3QgYW5kIGludHJvZHVjdGlvbiB0byBiZSBtb3JlIGNyaXNwIHJl
Z2FyZGluZyB0aGUNCiAgICAgIHRhcmdldGVkIHNvbHV0aW9uLiAgU2V2ZXJhbCBzdHJ1Y3R1cmFs
IGNoYW5nZXMgaW4gdGhlIGRvY3VtZW50IHRvDQogICAgICBoYXZlIGEgYmV0dGVyIGRpc3RpbmN0
aW9uIGJldHdlZW4gcmVxdWlyZW1lbnRzLCB1c2UgY2FzZQ0KICAgICAgZGVzY3JpcHRpb24sIGFu
ZCBzb2x1dGlvbiBkZXNjcmlwdGlvbiBhcyBzZXBhcmF0ZSBzZWN0aW9ucy4NCiAgICAgIEhpc3Rv
cnkgbW92ZWQgdG8gYXBwZW5kaXguDQoNCkJlc3QgcmVnYXJkcw0KU3RlZmZlbg0KDQotLS0tLU9y
aWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIDxpbnRl
cm5ldC1kcmFmdHNAaWV0Zi5vcmc+IA0KU2VudDogRnJlaXRhZywgMTAuIEp1bGkgMjAyMCAwOToy
OQ0KVG86IEZyaWVzLCBTdGVmZmVuIChDVCBSREEgQ1NUKSA8c3RlZmZlbi5mcmllc0BzaWVtZW5z
LmNvbT47IEVsaW90IExlYXIgPGxlYXJAY2lzY28uY29tPjsgQnJvY2toYXVzLCBIZW5kcmlrIChD
VCBSREEgQ1NUIFNFQS1ERSkgPGhlbmRyaWsuYnJvY2toYXVzQHNpZW1lbnMuY29tPg0KU3ViamVj
dDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1pZXRmLWFuaW1hLWJyc2tpLWFz
eW5jLWVucm9sbC0wMC50eHQNCg0KDQpBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQtaWV0Zi1h
bmltYS1icnNraS1hc3luYy1lbnJvbGwtMDAudHh0DQpoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3Vi
bWl0dGVkIGJ5IFN0ZWZmZW4gRnJpZXMgYW5kIHBvc3RlZCB0byB0aGUgSUVURiByZXBvc2l0b3J5
Lg0KDQpOYW1lOgkJZHJhZnQtaWV0Zi1hbmltYS1icnNraS1hc3luYy1lbnJvbGwNClJldmlzaW9u
OgkwMA0KVGl0bGU6CQlTdXBwb3J0IG9mIGFzeW5jaHJvbm91cyBFbnJvbGxtZW50IGluIEJSU0tJ
IChCUlNLSS1BRSkNCkRvY3VtZW50IGRhdGU6CTIwMjAtMDctMTANCkdyb3VwOgkJYW5pbWENClBh
Z2VzOgkJMzUNClVSTDogICAgICAgICAgICBodHRwczovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1k
cmFmdHMvZHJhZnQtaWV0Zi1hbmltYS1icnNraS1hc3luYy1lbnJvbGwtMDAudHh0DQpTdGF0dXM6
ICAgICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1hbmlt
YS1icnNraS1hc3luYy1lbnJvbGwvDQpIdG1saXplZDogICAgICAgaHR0cHM6Ly90b29scy5pZXRm
Lm9yZy9odG1sL2RyYWZ0LWlldGYtYW5pbWEtYnJza2ktYXN5bmMtZW5yb2xsLTAwDQpIdG1saXpl
ZDogICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvaHRtbC9kcmFmdC1pZXRm
LWFuaW1hLWJyc2tpLWFzeW5jLWVucm9sbA0KDQoNCkFic3RyYWN0Og0KICAgVGhpcyBkb2N1bWVu
dCBkZXNjcmliZXMgZW5oYW5jZW1lbnRzIG9mIGJvb3RzdHJhcHBpbmcgYSByZW1vdGUgc2VjdXJl
DQogICBrZXkgaW5mcmFzdHJ1Y3R1cmUgKEJSU0tJKSB0byBhbHNvIG9wZXJhdGUgaW4gZG9tYWlu
cyBmZWF0dXJpbmcgbm8gb3INCiAgIG9ubHkgdGltZWx5IGxpbWl0ZWQgY29ubmVjdGl2aXR5IGJl
dHdlZW4gaW52b2x2ZWQgY29tcG9uZW50cy4gIEl0DQogICBhZGRyZXNzZXMgY29ubmVjdGl2aXR5
IHRvIGJhY2tlbmQgc2VydmljZXMgc3VwcG9ydGluZyBlbnJvbGxtZW50IGxpa2UNCiAgIGEgUHVi
bGljIEtleSBJbmZyYXN0cnVjdHVyZSAoUEtJKSBhbmQgYWxzbyB0byB0aGUgY29ubmVjdGl2aXR5
DQogICBiZXR3ZWVuIHBsZWRnZSBhbmQgcmVnaXN0cmFyLiAgRm9yIHRoaXMgaXQgZW5oYW5jZXMg
dGhlIHVzZSBvZg0KICAgYXV0aGVudGljYXRlZCBzZWxmLWNvbnRhaW5lZCBvYmplY3RzIGluIEJS
U0tJIGFsc28gZm9yIHJlcXVlc3QgYW5kDQogICBkaXN0cmlidXRpb24gb2YgZGVwbG95bWVudCBk
b21haW4gc3BlY2lmaWMgZGV2aWNlIGNlcnRpZmljYXRlcy4gIFRoZQ0KICAgZGVmaW5lZCBhcHBy
b2FjaCBpcyBhZ25vc3RpYyByZWdhcmRpbmcgdGhlIHV0aWxpemVkIGVucm9sbG1lbnQNCiAgIHBy
b3RvY29sIGFsbG93aW5nIHRoZSBhcHBsaWNhdGlvbiBvZiBleGlzdGluZyBhbmQgcG90ZW50aWFs
bHkgbmV3DQogICBjZXJ0aWZpY2F0ZSBtYW5hZ2VtZW50IHByb3RvY29scy4NCg0KICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIA0KDQoNClBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBjb3Vw
bGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24gdW50aWwgdGhlIGh0bWxp
emVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZy4NCg0K
VGhlIElFVEYgU2VjcmV0YXJpYXQNCg0KDQo=


From nobody Fri Jul 10 00:51:43 2020
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 4C9F83A07D1; Fri, 10 Jul 2020 00:51:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, 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 6HqFBBh40mPs; Fri, 10 Jul 2020 00:51:40 -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 B1D783A07C5; Fri, 10 Jul 2020 00:51:39 -0700 (PDT)
Received: from lhreml710-chm.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 2F0233D785317F2F2350; Fri, 10 Jul 2020 08:51:38 +0100 (IST)
Received: from nkgeml707-chm.china.huawei.com (10.98.57.157) by lhreml710-chm.china.huawei.com (10.201.108.61) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Fri, 10 Jul 2020 08:51:37 +0100
Received: from nkgeml708-chm.china.huawei.com (10.98.57.160) by nkgeml707-chm.china.huawei.com (10.98.57.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Fri, 10 Jul 2020 15:51:34 +0800
Received: from nkgeml708-chm.china.huawei.com ([10.98.57.160]) by nkgeml708-chm.china.huawei.com ([10.98.57.160]) with mapi id 15.01.1913.007; Fri, 10 Jul 2020 15:51:34 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "anima@ietf.org" <anima@ietf.org>
CC: "anima-chairs@ietf.org" <anima-chairs@ietf.org>, Toerless Eckert <tte@cs.fau.de>
Thread-Topic: Call for agenda ANIMA @ IETF 108, online
Thread-Index: AdZWjt52t5MTQcBDTV+EWVYg6H3Sig==
Date: Fri, 10 Jul 2020 07:51:34 +0000
Message-ID: <12ed9e0beafe415fb3e6df59bb74c85e@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.108.235.253]
Content-Type: multipart/alternative; boundary="_000_12ed9e0beafe415fb3e6df59bb74c85ehuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/4_OkPr7lFRF0mp1UNOUff8yM-JM>
Subject: [Anima] Call for agenda ANIMA @ IETF 108, online
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, 10 Jul 2020 07:51:41 -0000

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

SGksIGFsbCBhbmltYSwNCg0KDQoNCldlIGhhdmUgYmVlbiBhbGxvY2F0ZWQgYSBzZXNzaW9ucyBv
ZiAxIGhvdXIgNDAgbWludXRlcyBmb3IgdGhlIEFOSU1BIFdHIG1lZXRpbmcgZm9yIElFVEYtMTA4
IChvbmxpbmUpLiBJdCBpcyBvbiBUaHVyc2RheSwgSnVseSAzMCwgMjAyMKOsIDExOjAwLTEyOjQw
IChVVEMpLiBXZSBhcmUgbm93IHN0YXJ0aW5nIHRvIGNvbGxlY3QgYWdlbmRhIGl0ZW1zIGZvciB0
aGUgc2Vzc2lvbi4gUGxlYXNlIHNlbmQgeW91ciByZXF1ZXN0IGZvciBhZ2VuZGEgYnkgSnVseSAy
MXRoLCBUdWVzZGF5LCB0byBhbmltYS1jaGFpcnNAaWV0Zi5vcmcgYW5kIGJvdGggY2hhaXJzJyBl
bWFpbC4gUGxlYXNlIG5vdGUgdGhhdCBlbWFpbCB0byBhIHNpbmdsZSBjaGFpciBtYXkgY2F1c2Ug
c2luZ2xlLXBvaW50IGZhaWx1cmUuDQoNCg0KDQpBcyBub3JtYWwsIHRoZSBwcmlvcml0eSBhbW9u
ZyB0aGVzZSBub24tY2hhcnRlciB3b3JrIGl0ZW1zIHdvdWxkIGJlOiB0aGVzZSB0aGF0IGhhdmUg
YWN0aXZlIGRpc2N1c3Npb24gaW4gbWFpbCBsaXN0LCB0aGVuIHRoZXNlIGhhdmUgc3VibWl0dGVk
IGRyYWZ0cywgYW5kIHRvcGljcyB3aXRob3V0IGRyYWZ0cy4NCg0KDQoNClBsZWFzZSBzZW5kIHVz
IChhbmltYS1jaGFpcnMgYXQgaWV0Zi5vcmcpIHJlcXVlc3RzIGZvciB0aW1lIHNsb3QgYnkgSnVs
eSAyMXRoLCBUdWVzZGF5IGFuZCBpbmNsdWRlOg0KDQoNCg0KTmFtZSBvZiB0aW1lIHNsb3Q6DQoN
Ck5hbWUgb2YgZHJhZnQocyk6DQoNClRpbWUgcmVxdWVzdGVkOg0KDQpQcmVzZW50ZXIgbmFtZShz
KToNCg0KDQoNCk1vcmUgZGV0YWlscyBhYm91dCB0aGUgSUVURiAxMDggY2FuIGJlIGZvdW5kIGF0
Og0KDQoNCg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvaG93L21lZXRpbmdzLzEwOC8NCg0KDQoNCkFn
YWluLCBwcmVzZW50ZXJzIGFuZCBkcmFmdCBhdXRob3JzIHBsZWFzZSBpbnZva2UgYWN0aXZlIGRp
c2N1c3Npb25zIGluIHRoZSBBTklNQSBsaXN0LiBNYWlsIGxpc3QgaXMgYSB2ZXJ5IGdvb2QgcGxh
Y2UgdG8gZGlzY3VzcyBhbmQgcmVhY2ggY29uc2Vuc3VzIG9uIHRlY2huaWNhbCBpc3N1ZXMuDQoN
Cg0KDQpCZXN0IHJlZ2FyZHMsDQoNCg0KDQpTaGVuZyArIFRvZXJsZXNzDQoNCg==

--_000_12ed9e0beafe415fb3e6df59bb74c85ehuaweicom_
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<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:Consolas;
	panose-1:2 11 6 9 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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
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:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
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:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@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">
<div class=3D"WordSection1">
<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 </span><span style=3D"font-s=
ize:9.0pt;font-family:=CB=CE=CC=E5;color:#212529">a</span><span style=3D"fo=
nt-size:9.0pt;font-family:Consolas;color:#212529"> sessions of 1 hour 40 mi=
nutes for the ANIMA WG meeting for IETF-108 (online). It is on Thursday, Ju=
ly 30, 2020</span><span lang=3D"ZH-CN" style=3D"font-size:9.0pt;font-family=
:=CB=CE=CC=E5;color:#212529">=A3=AC</span><span lang=3D"ZH-CN" style=3D"fon=
t-size:9.0pt;font-family:Consolas;color:#212529"> </span><span style=3D"fon=
t-size:9.0pt;font-family:Consolas;color:#212529">11:00-12:40 </span><span s=
tyle=3D"font-size:9.0pt;font-family:=CB=CE=CC=E5;color:#212529">(</span><sp=
an style=3D"font-size:9.0pt;font-family:Consolas;color:#212529">UTC). We ar=
e now starting to collect agenda items for the session. Please send your re=
quest for agenda by July 21th, Tuesday, to anima-chairs@ietf.org and both c=
hairs' email. Please note that email to a single chair may cause single-poi=
nt failure.<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">As normal, the priority among these non-charter wor=
k items would be: these that have active discussion in mail list, then thes=
e 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 ietf.org) requests =
for time slot by July 21th, Tuesday 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 108 can be found 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">https://www.ietf.org/how/meetings/108/<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">Sheng &#43; Toerless<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_12ed9e0beafe415fb3e6df59bb74c85ehuaweicom_--


From nobody Fri Jul 10 02:18:22 2020
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 3F3463A0F35 for <anima@ietfa.amsl.com>; Fri, 10 Jul 2020 02:18:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level: 
X-Spam-Status: No, score=-9.601 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, DKIM_VALID_EF=-0.1, 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 fhUMfU2wwGvM for <anima@ietfa.amsl.com>; Fri, 10 Jul 2020 02:18:19 -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 A68A43A0F30 for <anima@ietf.org>; Fri, 10 Jul 2020 02:18:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=771; q=dns/txt; s=iport; t=1594372698; x=1595582298; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=SY0l9bDO6M65/ncQyS7R6ignSlWLxSIn+ZZsJbfcDeA=; b=hOZSLThbIx+4q/TquKVoRopj4zNzBQNd+yub+cepFHOwgyALckXnYSU7 XDtQKbsbszoi7xE+yvu6Z+1LDyurfJCFIXuqZTa9Rl7R4h+7tw6G5yRWu LlPul3uxJoI39irS0/CyqRNmIJdnzNB4Egnsj3US2wPDikCgdRFsme7B5 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DeAAAEMQhf/xbLJq1gHAEBAQEBAQc?= =?us-ascii?q?BARIBAQQEAQFAgTkEAQELAYNsASASLI00h3ElnAgLAQEBDAEBLwQBAYRNAoI?= =?us-ascii?q?XJTcGDgIDAQELAQEFAQEBAgEGBG2FZ4VvAQEBAQIBOj0CBQsLGC5XBhODJoJ?= =?us-ascii?q?dIKo5dIE0hVGFDIE4AYhshB6CAIE4DBCCTT6EPYNJgi0EtReCZ4MGlkwDHYJ?= =?us-ascii?q?zjjCOA5NJmTaDUgIEBgUCFYFpJIFXMxoIGxVlAYI+PhIZDY5VjhI/AzA3AgY?= =?us-ascii?q?IAQEDCZAMAQE?=
X-IronPort-AV: E=Sophos;i="5.75,335,1589241600"; d="scan'208";a="27739536"
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; 10 Jul 2020 09:18:14 +0000
Received: from [10.61.203.151] ([10.61.203.151]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 06A9IElZ011851 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 10 Jul 2020 09:18:14 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Eliot Lear <lear@cisco.com>
In-Reply-To: <6d97fc3fd7074243944dee7319cfbee0@siemens.com>
Date: Fri, 10 Jul 2020 11:18:13 +0200
Cc: "anima@ietf.org" <anima@ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B5BBA569-2EA6-4048-9898-224542B12956@cisco.com>
References: <159436612878.4549.16244632802362802533@ietfa.amsl.com> <6d97fc3fd7074243944dee7319cfbee0@siemens.com>
To: "Fries, Steffen" <steffen.fries@siemens.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-Outbound-SMTP-Client: 10.61.203.151, [10.61.203.151]
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/DiXNoKnrK2d7tHQ5JK2EafQRoEY>
Subject: Re: [Anima] New Version Notification for draft-ietf-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: Fri, 10 Jul 2020 09:18:20 -0000

Hi everyone,

As Steffen has just noted, we have posted a WG draft.  I want highlight =
one aspect:

> On 10 Jul 2020, at 09:39, Fries, Steffen <steffen.fries@siemens.com> =
wrote:
>=20
>   o  Inclusion of discovery options of enrollment endpoints at the
>      domain registrar based on well-known endpoints in Section 5.3 as
>      replacement of section 5.1.3 in the individual draft.  This is
>      intended to support both use cases in the document.  An
>      illustrative example is provided.

This change as currently written would update basic BRSKI, and therefore =
deserves a lot of discussion.  If we want to go the route in the draft, =
and if it is not too late, I would get the change into the draft before =
the RFC comes out.

Eliot


From nobody Fri Jul 10 11:30:16 2020
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 0DD0A3A084C for <anima@ietfa.amsl.com>; Fri, 10 Jul 2020 11:30:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.87
X-Spam-Level: 
X-Spam-Status: No, score=-0.87 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, 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 qjO3HtKShdFT for <anima@ietfa.amsl.com>; Fri, 10 Jul 2020 11:30:12 -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 63D1E3A0870 for <anima@ietf.org>; Fri, 10 Jul 2020 11:29:59 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 0D6B154843F for <anima@ietf.org>; Fri, 10 Jul 2020 20:29:56 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 0527C440043; Fri, 10 Jul 2020 20:29:56 +0200 (CEST)
Date: Fri, 10 Jul 2020 20:29:55 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: anima@ietf.org
Message-ID: <20200710182955.GU42197@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/E1HwBp_yrwdGvoTOVSSHsXnr_aI>
Subject: [Anima] ANIMA: PLS read: Re: OPS ADs Hours
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, 10 Jul 2020 18:30:14 -0000

See below:
Due to Codi, there will only be an OPS AD hour if folks are interested to have topics they want to
discuss, so please send any requests directly to:

To: "Rob Wilton (rwilton)" <rwilton@cisco.com>, Warren Kumari <warren@kumari.net>
Cc: "ops-ads@ietf.org" <ops-ads@ietf.org>

Cheers
    Toerless

On Fri, Jul 10, 2020 at 05:38:42PM +0000, Rob Wilton (rwilton) wrote:
> Ops-area chairs,
> 
> Please may you relay the following message on to your WGs:
> 
> ---
> 
> Warren and I appreciate that the current COVID situation is tricky for everyone.  Added to that, I am also a new AD and many of you may not know me.
> 
> Normally at the IETF meetings you have the opportunity to find us during the week if you have anything informal to discuss, but in the current climate that isn't so easy.
> 
> Hence, if you have something that you would like to discuss with Warren and I, then we will happily schedule OPS ADs Hours, possibly during the scheduled IETF 108 week, or at another time if that isn't practical.
> 
> We will only schedule based on any requests that we receive by the end of next week (Friday 17th July, 23:59 UTC).
> 
> Please reply directly back to Warren and I, copying ops-ads, if you have something that you wish to discuss with us at this time.
> 
> Regards,
> Rob (and Warren)

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


From: Toerless Eckert <tte@cs.fau.de>
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>
Cc: "ops-chairs@ietf.org" <ops-chairs@ietf.org>,
	Warren Kumari <warren@kumari.net>,
	"ops-ads@ietf.org" <ops-ads@ietf.org>
Bcc: 
Subject: Re: OPS ADs Hours
Reply-To: 
In-Reply-To: <MN2PR11MB43663BD6D721650C34E06338B5650@MN2PR11MB4366.namprd11.prod.outlook.com>

On Fri, Jul 10, 2020 at 05:38:42PM +0000, Rob Wilton (rwilton) wrote:
> Ops-area chairs,
> 
> Please may you relay the following message on to your WGs:
> 
> ---
> 
> Warren and I appreciate that the current COVID situation is tricky for everyone.  Added to that, I am also a new AD and many of you may not know me.
> 
> Normally at the IETF meetings you have the opportunity to find us during the week if you have anything informal to discuss, but in the current climate that isn't so easy.
> 
> Hence, if you have something that you would like to discuss with Warren and I, then we will happily schedule OPS ADs Hours, possibly during the scheduled IETF 108 week, or at another time if that isn't practical.
> 
> We will only schedule based on any requests that we receive by the end of next week (Friday 17th July, 23:59 UTC).
> 
> Please reply directly back to Warren and I, copying ops-ads, if you have something that you wish to discuss with us at this time.
> 
> Regards,
> Rob (and Warren)


From nobody Fri Jul 10 13:46:22 2020
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 20C393A09E8 for <anima@ietfa.amsl.com>; Fri, 10 Jul 2020 13:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, 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 xwSQdurVfMVH for <anima@ietfa.amsl.com>; Fri, 10 Jul 2020 13:46:15 -0700 (PDT)
Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) (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 10F903A097E for <anima@ietf.org>; Fri, 10 Jul 2020 13:46:14 -0700 (PDT)
Received: by mail-pg1-x52a.google.com with SMTP id d4so3034716pgk.4 for <anima@ietf.org>; Fri, 10 Jul 2020 13:46:14 -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=k+rmicXF/KnLMIrCJPCl6VDgTti99UJ/0W7Atb8blww=; b=vMQqy1iAHe7/ZC3NYQtrjlvEbpxH+OYNemA+/TU2pJAwb8nIATDJNUHJHVb3MniZ3y m7uxzuXSiwtbXGK1rVoeb8fV3mv2EV0hE0j3X+hIc/5pKa3rUJwLUwug1pmBoaTe+RhD fzJrHEMmasMhXOfC6YZSuf4ICwIVo/q6fyFUsOvjUmufX76ZgYo0pt25fIX+aW8QxT9h X/slZrz5oZ52OIVFjUGbvqb/MCziaxM2wGjPnDPQM8qzOmvKDqntInrlq4M8HMWzNVAI aE+oBcF0YXzOM0zO4taqeHQPFkbT2BWl6B/Xh+2e/KmHQhqJniSzB7ID1P6eRtl4jMcH tAMw==
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=k+rmicXF/KnLMIrCJPCl6VDgTti99UJ/0W7Atb8blww=; b=m5mngftDd3SwNPFNRxZhJTKPa7ETHFPgWS3T0gaaJtAfYRbP6XlaxSzx+7TGhuWDsM ypVkP8LLDbRhaw+IN92H+cECMbZrXYTk7TPHHL6DDCO5sGLlFNs/e8DBgnV7UZsbtaBX PhEWaJh81UVViB305JA7LGrep90eB9+yle+uimPSXoGt9P3FXZDLs933SczCs6qnjcIE HmnPTN5BGQbssG43Vec+e/0T7dpTo7fPGE6i6LBPWD4ixoIylhUYB8OzXZyCEKQZI7Nq C+0Qp8TLk9vb9lageZj8OLvRvM4iN6+oUeQ2atI+ltWjCKJEs1s2wDHPMqdHTAsjm1WA Wa3w==
X-Gm-Message-State: AOAM530ykDtF6WuZrm1JkznxpaGLErsiwJc6zatmIvR6G1qBoPAxJqmj yNJwnC0x9QMeefr0RqTP2FnFiGTU
X-Google-Smtp-Source: ABdhPJygih9idJVhzb545UXuRrES4T0+fMgCE80gruEpJ6OittT/RZL3atxPb1Xk8L0X/jGfON8VaA==
X-Received: by 2002:a63:1f11:: with SMTP id f17mr58258893pgf.217.1594413974121;  Fri, 10 Jul 2020 13:46:14 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.132.13]) by smtp.gmail.com with ESMTPSA id g6sm6943267pfr.129.2020.07.10.13.46.11 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Jul 2020 13:46:13 -0700 (PDT)
To: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, "Fries, Steffen" <steffen.fries@siemens.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "anima@ietf.org" <anima@ietf.org>
References: <159436612878.4549.16244632802362802533@ietfa.amsl.com> <6d97fc3fd7074243944dee7319cfbee0@siemens.com> <B5BBA569-2EA6-4048-9898-224542B12956@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <dd6abb14-2cee-2244-5947-3f25dbc95c00@gmail.com>
Date: Sat, 11 Jul 2020 08:46:09 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <B5BBA569-2EA6-4048-9898-224542B12956@cisco.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/nccDXLXsLthaWfbbvCDwLJ9o47E>
Subject: Re: [Anima] New Version Notification for draft-ietf-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: Fri, 10 Jul 2020 20:46:21 -0000

Eliot,

On 10-Jul-20 21:18, Eliot Lear wrote:
> Hi everyone,
> 
> As Steffen has just noted, we have posted a WG draft.  I want highlight one aspect:
> 
>> On 10 Jul 2020, at 09:39, Fries, Steffen <steffen.fries@siemens.com> wrote:
>>
>>   o  Inclusion of discovery options of enrollment endpoints at the
>>      domain registrar based on well-known endpoints in Section 5.3 as
>>      replacement of section 5.1.3 in the individual draft.  This is
>>      intended to support both use cases in the document.  An
>>      illustrative example is provided.
> 
> This change as currently written would update basic BRSKI, and therefore deserves a lot of discussion.  If we want to go the route in the draft, and if it is not too late, I would get the change into the draft before the RFC comes out.

I can't parse that sentence. Get "the change" into which draft? Before which RFC comes out?

If this extends BRSKI, or varies BRSKI, will it need an Updates: <BRSKI RFC number> tag?

   Brian


From nobody Mon Jul 13 09:54:31 2020
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 14D873A1746; Mon, 13 Jul 2020 09:54:21 -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: 7.8.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: anima@ietf.org
Message-ID: <159465926103.20425.5236454792193110254@ietfa.amsl.com>
Date: Mon, 13 Jul 2020 09:54:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/h-Gswh1dFPJr3kn2S5bGm5DmlTE>
Subject: [Anima] I-D Action: draft-ietf-anima-constrained-voucher-08.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, 13 Jul 2020 16:54:26 -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-08.txt
	Pages           : 41
	Date            : 2020-07-13

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 as an extension to 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-08
https://datatracker.ietf.org/doc/html/draft-ietf-anima-constrained-voucher-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-anima-constrained-voucher-08


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 Tue Jul 14 20:03:06 2020
Return-Path: <noreply@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 5FB513A0DD0; Tue, 14 Jul 2020 20:03:00 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-anima-autonomic-control-plane@ietf.org, anima-chairs@ietf.org,  anima@ietf.org, Sheng Jiang <jiangsheng@huawei.com>, jiangsheng@huawei.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.8.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <159478218035.5567.5331512017107084574@ietfa.amsl.com>
Date: Tue, 14 Jul 2020 20:03:00 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/6JH6eSTKBLYmgTGZdJXUpkNXUKo>
Subject: [Anima] Roman Danyliw's Discuss on draft-ietf-anima-autonomic-control-plane-27: (with DISCUSS and COMMENT)
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: Wed, 15 Jul 2020 03:03:00 -0000

Roman Danyliw has entered the following ballot position for
draft-ietf-anima-autonomic-control-plane-27: 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:
----------------------------------------------------------------------

** As normative behavior is specific for BRSKI (e.g., Section 6.1.5 and
6.1.5.5), please make it a normative reference

** Figure 2’s definition of acp-address is ‘acp-address = 32HEXLC | "0"’.  The
following text references a 32HEXDIG but that isn’t in the definition of
acp-address.

-- Section 6.1.2.  ‘Nodes complying with this specification MUST be able to
receive their ACP address through the domain certificate, in which case their
own ACP domain certificate MUST have the 32HEXDIG "acp-address" field.’

-- Section 6.1.3.  ‘The candidate peer certificate's acp-node-name has a
non-empty acp-address field (either 32HEXDIG or 0, according to Figure 2).’

** Precision in bounding the cipher selection.

-- Section 6.7.2.  Per “Symmetric encryption for the transmission of secure
channel data MUST use encryption schemes considered to be security wise equal
to or better than AES256”, which property of AES-256 is being considered for
this assessment?

-- Section 6.8.2.  Per “TLS for GRASP MUST offer
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 and
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 and MUST NOT offer options with less
than 256bit AES or less than SHA384”, please state this more precisely.

-- Is it that AES-128 shouldn’t be used or that that AES-256 has a certain key
strength to which to adhere to?

-- Is it that SHA-224 or SHA256 shouldn’t be used (staying in the SHA-2 family)
or is it a certain number of bits of security ?

** The text specifies the need for physical controls.  Please be more specific
on the appropriate degree of that physical control or how that decision should
be made; and explicitly explain threat of concern.

-- Section 8.1.1.  “Thus, the ACP connect interface and NOC systems connected
to it needs to be physically controlled/secured.”

-- Section 8.1.5.  “… the ACP connect link and the nodes connecting to it must
be in a contiguous secure   environment, hence assuming there can be no
physical attack against the devices.”

** (“discuss discuss”) Section 8.1.2.  What is the normative behavior being
specified in this section?  Specifically, what is the additional or more
restrictive behavior for the circumstance is where an ACP node is virtualized.

** Section 8.2.1.  (I’m no ABNF expert …) Per the ABNF in Figure 17, the “//=”
notation isn’t valid.  I think you want:

OLD
     method //= [ "DTLS",    port ]

NEW
     method =/ [ "DTLS",    port ]

** Section 10.2.1.  Per “An attacker will not be able to join the ACP unless
having a valid domain certificate, also packet injection and sniffing traffic
will not be possible due to the security provided by the encryption protocol.”,
please be clearer:

-- on path attacker = no packet injection
-- on path attacker = only traffic analysis when sniffing
-- compromised node = can inject traffic

** Section 11.  Per “an ACP is self-protecting and there is no need to apply
configuration to make it secure”, if this assertion is going to be made:

-- please specify the security services/properties in a normative section (not
in the informative text in Section 10).

-- please also be clear on what configuration is being referenced.

** Section 11.  Per the list of factors on which ACP depends, it seems like the
following are missing:

-- the security properties of the enrollment protocol

-- that the security considerations of EST and BRSKI apply (or if not, why not)


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

(Preliminary ballot.  Need to double check that all of ekr's discusses were
cleared)

The style of explaining the design choice after describing an element of the
protocol was informative and helpful.  Thanks.

The this document has undergone a significant amount of security review.  Thank
you for incorporating all of this feedback.

** Section 6.  It doesn’t seem appropriate to call a protocol “indestructible”
unless you are going to enumerate the resiliency properties more precisely –
“many inadvertent changes” is vague.

** Section 6.  Per “An ACP node can be … or any other IP a capable node”,
should this be “IPv6 capable node”?

** Section 6.1.1.  Per “… it is beneficial to copy the device identifying
fields of the node's IDevID certificate into the ACP domain certificate …”, is
there a ACP-recommended approach for that?

** Section 6.1.3.1. Per “In the absence of implementing a secured mechanism,
such an ACP node MAY use a current time learned in an insecured fashion in the
ACP domain membership check.”, please be clearer on how this current time is
learned in the domain membership check.

** Section 6.1.5.  Per “ACP nodes SHOULD be able to remember the IPv6 locator
parameters ...”, what happens if they don’t remember?

** Section 6.1.5.3.  Per “The connecting ACP node SHOULD verify that the CRLDP
certificate used during the HTTPs connection has the same ACP address as
indicated in the CRLDP URL …”, why is this not a MUST?

** Section 6.1.5.5.  Per “An ACP node may determine that its ACP domain
certificate has expired … [i]n this case, the ACP node SHOULD convert to a role
of a re-enrolling candidate ACP node”, what is the alternative if it wants to
connect back to the network?  Shouldn’t this be a MUST?

** Section 6.5.  It seems misplaced to describe MacSec as an option for channel
security even when it is not a profiled in this document.

** Section 6.7.2. Per “Signaling of TA certificates may not be appropriate when
the deployment is relying on a security model when the TA certificate content
is considered confidential”, where is the requirement to signal TA certificates
discussed.  How would this selection of signaling a TA work?  The entire
paragraph prior seemed to explicitly discuss that the TA doesn’t need to be
shared.

** Section 6.7.2.  Per “When introducing the profile for security association
protocol …”, I recommend being clearer to whom you are providing this advice. 
This seems to for operators of ACP infrastructure technology (not
implementers/vendors of ACP technology)

** Section 6.7.3.  Per “The ACP usage of IPsec and IKEv2 mandates a profile
with a narrow set of options of the current standards-track usage guidance for
IPsec    [RFC8221] and IKEv2 [RFC8247]”, should there be normative wording use
(MUST) instead of a “mandates”?

** Section 6.7.3.1.1.  Per ENCR_CHACHA20_POLY1305, “[t]herefore this algorithm
is only recommended”, shouldn’t it read as RECOMMENDED?

** Section 6.7.3.1.2.  Per “[RFC8247] provides a baseline recommendation for
mandatory to   implement ciphers, integrity checks, pseudo-random-functions and
Diffie-Hellman mechanisms.  Those recommendations, and the recommendations of
subsequent documents apply well to the ACP.”, it seems like normative language
should be used to adhered to.

** Section 6.10.7.3.  The paragraph/sentence starting with “ACP registrars that
are aware of can use …” doesn’t parse.  The guidance isn’t clear as a result.

** Section 6.10.7.3.  Per “In a simple allocation scheme, an ACP registrar
remembers persistently across reboots …”, what’s the recover step if it loses
that state?

** Section 6.11.1.1.2.  Not clear what “DODAG Information Objects (DIOs) SHOULD
be sent 2 .. 3 times” means – can “2 .. 3” please be clarified.

** Section 6.11.1.1.2.  A mechanism for failed ACP detected using a secure
channel protocol is noted for IPSec (with IKEv2 Dead Peer Detection).  What is
the equivalent for DTLS?

** Section 9.  The section notes that Section 9.1 is “derived from diagnostic
of a commercially available ACP implementation”.  The shepherd report from
03/2019 notes that there are no implementations of ACP.  If this is documented
somewhere, it would be very compelling to cite it.

** Section 9.1. Per “The basic diagnostics [sic] is support of (yang) data
models representing the complete (auto-)configuration and operational state of
all components …”, are these YANG models defined?  Are there references?

** Section 9.3.1.  Per “Whenever this document refers to enabling an interface
for ACP … it only requires to permit [sic] the interface …”, this seems like
normative behavior in an informative section.

** Section 9.3.2.  That this is an information section is noted.  It would
benefit from describing what precisely can and cannot be done in the three
states proposed – up, down and admin down.

** Section 9.3.2.1.  What is the proposed threat that using admin down is
intended to mitigate?  Under what circumstance should it be invoked?

** Section 9.3.2.1.  Per ‘"Admin down" state as described above provides also a
high level of security because it only permits ACP/ANI operations which are
both well secured”, to what is the “both” referring? I suspect this is
editorial (but just in case, noting here).

** Section 10.2.2.  Per “For example, management plane functions (transport
ports) should only be reachable from the ACP but not the Data-Plane”, this
seems like good guidance.  Is there a reason not to upgrade this informative
statement and put it the Security Considerations as normative guidance?

** Section 10.2.2.  Per “Protection across all potential attack vectors is
typically easier to do in devices whose software is designed from the ground up
with security in mind than with legacy software based systems where the ACP is
added on as another feature”, no argument on the general principle.  However,
as it relates to ACP:

--what’s an example of the legacy software?

-- as noted in the shepherd report from 03/2019, there are no implementations,
so is there reason to believe that this is going to put on “legacy” platforms?

** Section 10.2.2.  Per “As explained above, traffic across the ACP SHOULD
still …”, is RFC2119 language really intended in this informative section?

** Section 11.  Per “Security can be compromised by implementation errors
(bugs), as in all products”, given the generic nature of this statement,
couldn’t it also be a configuration error in the product too?

** Section 11.  Per “Higher layer service built using ACP domain certificates
should not rely on undifferentiated group security …” is there a reason not to
make this a normative SHOULD?

** Editorial

-- Recommend being consistent on either “ACP domain certificates” or “ACP
certificates”

-- Section 1.  Editorially.  The two sentences “Section 7 defines normative how
to …” and “Section 8 explain normative how …” don’t parse as the adjective
normative needs a noun to modify.

-- Section 6.1.4.  Editorial.  s/These requirements can be achieved by using TA
private/These requirements can be achieved by using a TA private/

-- Section 6.2.  Editorial. s/does intentionally not/intentionally does not/

-- Section 6.5.  Editorial.  Per “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.”, does not parse.

-- Section 6.10.7.  Per “ACP registrars are responsible to enroll candidate ACP
nodes with ACP domain certificates and associated trust point(s)”, is a trust
point the same thing as a trust anchor?    If so, I recommend being consistent.
 If not, then please define it.

-- Section 6.11.1.  Please make draft-ietf-roll-applicability-template a
reference.

-- Section 6.11.1.5.  Editorially.  It might be worth framing the path metric
in the form of sentence.

-- Section 11. s/enemy plegdes/rogue pledges/

-- Section 11. Per “Fundamentally, security depends on avoid operator and
network automation mistakes …”, this paragraph is not actionable.  Recommend
removal.

** Typos
Section 1.  Typo. s/parth/path/
Section 1.  Typo. s/seperately/separately/
Section 1.  Typo. s/automaticically/ automatically/
Section 1.  Typo. s/managemenet/ management/
Section 1.  Typo. s/absene/absence/
Section 1.1.  Typo. s/solution:/solution/
Section 2.  Typo. s/netork/network/
Section 2.  Typo. s/physcially/physically/
Section 5.  Typo. s/(see (see/(see/
Section 5. Typo. s/loopack/loopback/
Section 6.1.1.  Typo. s/e.g.:signing/e.g., signing/
Section 6.1.1.  Typo. s/signalled/signaled/g
Section 6.1.1.  Typo. s/bei/by/
Section 6.1.2.  Typo. s/simpy/simply/
Section 6.1.2.  Typo. s/readible/readable/
Section 6.1.2.  Typo. s/Adresses/Addresses/
Section 6.1.2.  Typo. s/manadatory/mandatory/
Section 6.1.2. Typo. s/inapproprite/inappropriate/
Section 6.1.3.1.  Typo. s/as as/as/
Section 6.1.3.1.  Typo. /insecured/insecure/
Section 6.1.3.1.  Typo. s/likley/likely/
Section 6.2. Typo. s/IKEv2 has am/IKEv2 has an/
Section 6.7.2.  Typo. s/successfull/successful/
Section 6.7.3.1.1.  Typo.  s/superceed/superseded/
(I stopped documenting spelling errors at Section 6.7.3.1.1.  Please run a
spell checker before handing this off to the RFC Editor)




From nobody Wed Jul 15 05:33:48 2020
Return-Path: <hendrik.brockhaus@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 428FA3A0528 for <anima@ietfa.amsl.com>; Wed, 15 Jul 2020 05:33:46 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=siemens.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eZWXFlKYVSDb for <anima@ietfa.amsl.com>; Wed, 15 Jul 2020 05:33:45 -0700 (PDT)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60054.outbound.protection.outlook.com [40.107.6.54]) (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 BC2303A043E for <anima@ietf.org>; Wed, 15 Jul 2020 05:33:44 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=X69K0V60DqDkaT86dsKI8icNfw0bxDQdmpASOis6pv8NAuc7lqcr3buMC1mGRNSNSLKoBtRt/QMxhtdqPu234kNDoLBL0gJKV2FIGGQjoOUyf7hgK2uhGxNMkQsz12938OUFJLNYswuHmROJKjUMglZTQLEZd2/li0bue6BmofQBoh/GklBdpUNLU04H/8+PxrliomEqFxeWbp+gZ0ddNjbfMeZ7MLfzjBINE4xzuRPs/orDH6ziFBUMBeTK7RYUMuQ126QWjYF8f4P9b5RqxMkD9XMd520gF9gNplIpcrdp479DdvbL/4LWWoahir0KgOuQc0cJ6Peh3giwn09exw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=XM6QtwBtllbovEca6MurSnWb/ALC4YKVCkBUoX52Ejg=; b=Nx5BaYx1WJXl56YSt7M0iA9qe8l1ZHVU4yC+W/hCv33oPwz0hIP5dy3GuET9c/O1eESbvfiVL4Zm9rXnKzVAxDkb66xnpS3nvkme3KuwHzkwbnsIKzW23uEje3S6PwlXhWOItuRfE1d+Mwwhhldg79CQzezLuDGW3PX9+CjGPSK1nszreZrE7UoF2GQbrlqsClzPcrqJjK82dk0Yx9HReZfEgpD3KlUllcchMWnDdbRaoVT9PZ4adxxFVMmwfRJ1rZ8axdBoNDMIE507RvLksXd6mfIqM4h/1OtkkUkxH7JOC3yjc3Ty8MmmXHDLoar61wHkbr4yVcTJ3NxhXzW7aA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=siemens.com; dmarc=pass action=none header.from=siemens.com; dkim=pass header.d=siemens.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=siemens.onmicrosoft.com; s=selector1-siemens-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=XM6QtwBtllbovEca6MurSnWb/ALC4YKVCkBUoX52Ejg=; b=EcH5Zj1w76ihKchpPutVipY/oPIw2WDD9e/43OocTKjAGJ/LVbjSoX4rEH6qRnuextfiRheg3U/s8/VA+4pSLwSrajpN/40bfR+2f/zV5ZEaM5+M86t1s0BS/XHAZC25txr7ybs6zQXT69SlZn0PT+0SKagGuUk7ssBDdrtE9PQ=
Received: from AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:208:184::10) by AM0PR10MB2099.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:208:4b::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3174.22; Wed, 15 Jul 2020 12:33:42 +0000
Received: from AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM ([fe80::c5d3:8347:4ebd:93da]) by AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM ([fe80::c5d3:8347:4ebd:93da%3]) with mapi id 15.20.3174.026; Wed, 15 Jul 2020 12:33:42 +0000
From: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: Michael Richardson <mcr+ietf@sandelman.ca>, "anima@ietf.org" <anima@ietf.org>, Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, "steffen.fries@siemens.com" <steffen.fries@siemens.com>
Thread-Topic: [Anima] New Version Notification for draft-ietf-anima-brski-async-enroll-00.txt
Thread-Index: AQHWVovD3/f7GG2qMkCXcZv5EQ+aBqkAbYiAgAAbc4CAAMA0gIAHToTQ
Date: Wed, 15 Jul 2020 12:33:42 +0000
Message-ID: <AM0PR10MB315321BA8AA5B3A3E479C123FE7E0@AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM>
References: <159436612878.4549.16244632802362802533@ietfa.amsl.com> <6d97fc3fd7074243944dee7319cfbee0@siemens.com> <B5BBA569-2EA6-4048-9898-224542B12956@cisco.com> <dd6abb14-2cee-2244-5947-3f25dbc95c00@gmail.com>
In-Reply-To: <dd6abb14-2cee-2244-5947-3f25dbc95c00@gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-document-confidentiality: NotClassified
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=siemens.com;
x-originating-ip: [165.225.200.181]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 8eb821d8-4fa0-431b-e444-08d828bb4f1b
x-ms-traffictypediagnostic: AM0PR10MB2099:
x-ld-processed: 38ae3bcd-9579-4fd4-adda-b42e1495d55a,ExtAddr
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <AM0PR10MB2099FA1E6B21981A1A5ED4E3FE7E0@AM0PR10MB2099.EURPRD10.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: EHZJYoB4SYUWEtmp8vhk5XLKkgYiM9RfHcGDZZ4Wm8ajifRuWmsWwdHuEyYTQCe9dkXW2IXgHAg8z0gLbOmkEgXhdCRN1lRs6pfQpqV+tq8Mfqly5Y8BGwNrYbOyI7UTX2bkFAJ/2aqYfQ6gslwj5sgSVFrb2czopVTg0eo6BkMN3QMDYMc9saG2XJyFoqxUdwIEBSgNi+aDmpHA2UzVQRIM7kthhjM+sSXLBMO5mlwsGnnyaYE+xekMwogsWRWcQ005smi6eEb5tsysNE+uYySuGBX/hqhuZ2mG6r6U+ncmLgunccMUTBTxVve8cJLfXcvyIde/odN6rMdVn0yJWA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(136003)(376002)(396003)(39860400002)(366004)(346002)(8936002)(86362001)(4326008)(33656002)(54906003)(478600001)(8676002)(83380400001)(7696005)(5660300002)(66946007)(186003)(26005)(6506007)(55236004)(66476007)(66446008)(15650500001)(66556008)(64756008)(316002)(9686003)(6916009)(55016002)(53546011)(71200400001)(2906002)(52536014)(76116006)(107886003); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: Y2+ayIzzMjNqFJYDOdZ24febLFKiWyBm7/gk5OzPKUDVQL6opm32S2H2HKGXQDGT9Y/pxPqTdq2I7Csx6ZdlTBFUAJ6xVNt/RbRzA2LkOVy/LaHosm1RGoHPRlHdGlaGIVBnwnGo2vNDJPTg3q1vBxOpUhmqkoS3dB3+hYpRiq6/EW7WgpJ/OT02vPlBOIkoh6QqgPDbwyB1NnGbRdTg9E/athphBb1lk9yHtODvTsoQ1IPwtXpvQnvPXSnK8P4bxBGIvvsIUCdoRHm67yCIZVkC5YiUbnuRxYkXa0wLbr3/GY1IOEeVWMKa1xUDvCTzN2iIfvXbSqyznJq9crgDB7FKjfqqUmTpldPZshurZkXk5C/K36r0FusGg5vuWVUh+K0CGnMHG/zg4KkQgf0XgieHPlAE4EVl5C6L4hDKRxZhIw+s+42MKfmQq+EdUoKXw2zNPLzLGBeQn7Yv/vJnRL0Okx/ARE0fgo5psh5iDAQFNZ+AVcNnHRPa42rkQJIw
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: siemens.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 8eb821d8-4fa0-431b-e444-08d828bb4f1b
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Jul 2020 12:33:42.3212 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 38ae3bcd-9579-4fd4-adda-b42e1495d55a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Ma7h0t1bshmu7/xkURUH0UvFdMjplASQqOTNb9H2BoOZ3u7cWxVcy+MeUh/bnfpsRmph3eg7m1AP4oMWAJ9LP+qAHLTzsLcxA/IA8c8NZ/U=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR10MB2099
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/MQkNXJJjMkP0nqKlNEaxDZ94RgI>
Subject: Re: [Anima] New Version Notification for draft-ietf-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, 15 Jul 2020 12:33:46 -0000

Brian

> Von: Anima <anima-bounces@ietf.org> Im Auftrag von Brian E Carpenter
> Gesendet: Freitag, 10. Juli 2020 22:46
>=20
> Eliot,
>=20
> On 10-Jul-20 21:18, Eliot Lear wrote:
> > Hi everyone,
> >
> > As Steffen has just noted, we have posted a WG draft.  I want highlight=
 one
> aspect:
> >
> >> On 10 Jul 2020, at 09:39, Fries, Steffen <steffen.fries@siemens.com> w=
rote:
> >>
> >>   o  Inclusion of discovery options of enrollment endpoints at the
> >>      domain registrar based on well-known endpoints in Section 5.3 as
> >>      replacement of section 5.1.3 in the individual draft.  This is
> >>      intended to support both use cases in the document.  An
> >>      illustrative example is provided.
> >
> > This change as currently written would update basic BRSKI, and therefor=
e
> deserves a lot of discussion.  If we want to go the route in the draft, a=
nd if it is
> not too late, I would get the change into the draft before the RFC comes =
out.
>=20
> I can't parse that sentence. Get "the change" into which draft? Before wh=
ich
> RFC comes out?

The change would be on the MASA URI extension as specified in BRSKI section=
 2.3.2. To become enrollment protocol agnostic, we propose to change from /=
est to /brski for the voucher exchange.
The idea is to leave definition of the URI for the enrollment with the resp=
ective RFCs, e.g., /est from RFC7030.  Define the /.well-known/brski for th=
e paths /requestvoucher, /voucher_status, and /requestauditlog (and possibl=
y also /enrollstatus) specifically specified in BRSKI.

Hendrik=20


From nobody Fri Jul 17 15:10:42 2020
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 F15863A0972; Fri, 17 Jul 2020 15:10:40 -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, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 nJnsw_YXM7Jn; Fri, 17 Jul 2020 15:10:39 -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 BDCDD3A08B9; Fri, 17 Jul 2020 15:10:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 40D45389AC; Fri, 17 Jul 2020 18:07:35 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Mo4FrNKUFxU8; Fri, 17 Jul 2020 18:07:34 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 29D7F389AB; Fri, 17 Jul 2020 18:07:34 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id AC92824C; Fri, 17 Jul 2020 18:10:36 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Tero Kivinen <kivinen@iki.fi>, ipsec@ietf.org, anima@ietf.org, draft-ietf-anima-autonomic-control-plane@ietf.org
In-Reply-To: <24336.33964.354779.953171@fireball.acr.fi>
References: <7EDA9264-8007-4221-9A0D-D967C9AD8BD9@gmail.com> <0b8001d5ecad$79ce7ad0$6d6b7070$@gmail.com> <alpine.LRH.2.21.2002261504240.27113@bofh.nohats.ca> <0c9e01d5ed4c$2353f5a0$69fbe0e0$@gmail.com> <20200619145112.GA47906@faui48f.informatik.uni-erlangen.de> <alpine.LRH.2.22.394.2006191126200.32638@bofh.nohats.ca> <24142.1592760359@localhost> <24309.64229.308771.733097@fireball.acr.fi> <20200626161053.GQ41244@faui48f.informatik.uni-erlangen.de> <24315.37346.143409.46224@fireball.acr.fi> <20200630202812.GF13952@faui48f.informatik.uni-erlangen.de> <24336.33964.354779.953171@fireball.acr.fi>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512; protocol="application/pgp-signature"
Date: Fri, 17 Jul 2020 18:10:36 -0400
Message-ID: <6871.1595023836@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/-djTE9UgkDJgbQ9XRYrh_ch0Sh8>
Subject: Re: [Anima] [IPsec] Troubleshooting IPsec peer certs (was: Re: IPsec profile feedback wanted (draft autonomic control) plane)
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, 17 Jul 2020 22:10:41 -0000

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


Tero Kivinen <kivinen@iki.fi> wrote:
    Tero> Note, that initiator might not have any certificate from CA1 or CA2,
    Tero> it might actually use completely different CAs, i.e., the list of
    Tero> certificate authorities can be asymmetric.

    Toerless> Good explanation. So, whats the most simple example for this ?
    Toerless> I have a single VPN but multiple geographic headends and
    Toerless> there is an obfuscated logic what certs each headends accepts,
    Toerless> so i do have multiple and certreq helps me to choose ?

    > I would assume most common case will be when certificates are being
    > renewed in non-compatible way. I.e., you initially have rsa certs for
    > both client and server, then someone decides rsa is weak, and we must
    > move to ecdsa in the future. They will first install new TA certs on
    > the some servers (lets say they have 1000 of those, and they do not
    > want to do all of them immediately). Now some of the servers do have
    > TA1, and some have both TA1, and TA2.

I am not really following this discussion very well.
I'm not sure if this is general advice or ACP specific advince.

In the case that you describe (RSA->ECDSA),  I think that we would sign TA1
with TA2, or vice-versa. (probably one and then the other a month later).
We can feed/update the trust anchors when certificates are renewed, or we can
use draft-ietf-netconf-trust-anchors to change things (the advantages of
having really good security for in-band management)

I prefer relatively short expiries for certificates in the ACP because <STAR reasons>.
I think that all systems have to support both RSA and ECDSA for a big
overlapping period.  I don't think this is a problem.

I think that there is not a problem having a RSA key (TA1) sign an ECDSA EE cert.
I know that I've done it, but I know that some think it uncool.

    > Next clients needs to get new certificates from TA2. This process can
    > m^Htake months, as it is possible that some of the clients are not
    > connecting to the server for long time.

That's true in general, particularly for remote access situations, but ACP
nodes are mostly always reachable.  If they get turned off and put in a box,
then when they return, they have a valid certificate, or they have to
bootstrap again, and that's okay.

    > If you have client which has only TA1, there is no problem, it can
    > connect to any server which still supports TA1. If you have client
    > which has both TA1, and TA2, and it connects to old server which only
    > supports TA1, it needs to recognize this and use TA1 in that case. If
    > it connects to server using both TA1, and TA2, it most likely wants to
    > prefer TA2, as that is the direction the transition is going, so TA2
    > should be preferred if both are supported.

    > When all servers have been updated to support both TA1, and TA2, then
    > there is no longer issues, as now all clients which do have TA2, use
    > it for all servers, and those which have not yet updated to TA1, still
    > use that.

You are imagining a period of time where we are installing the trust anchors,
and I don't see it has to be like that.

Have TA1 sign TA2 as a sub-CA, and then pass out TA1->TA2->EE(ecdsa) chain to the
new nodes.  Once this is done for all nodes, you can drop TA1.
In reality, there are probably at least an extra level of CA, possibly two.

Do you think that I should include this situation into draft-richardson-registrar-operational-considerations?

    > So the idea is to allow iterative updating of the system, without the
    > need of flag days or configuration settings to specify things. I.e.,
    > IKEv2 will automatically detect which TA is supposed to be used, and
    > use it.

Agreed.

    >> The full name of a node was so far an rfc822Name, now i need to
    >> fix it to become what i think is going to be a GeneralName,
    >> and hence it might best be to signal IDi/IDr as ID_DER_ASN1_GN

    > Note, that the IDi and IDr are what is matched against the IPsec
    > policy, i.e., nothing in the certificate will cause policy to be
    > selected, only IDi and IDr does that. After IDi and IDr identifies the
    > suitable policy, we can go and match the information in the policy
    > against the certificate. That policy might include information like
    > how to match the certificate subject alt name or subject name to
    > identity or information in the policy.

So, we've been forced to use otherName, and this will cause new code in some
of the IKEv2 daemon that we need to use :-(

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

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

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

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl8SIdwACgkQgItw+93Q
3WXDrAf+KARlPwJFjiNO8Kf3vQuYaDzeMTs1ypYxHSRQGZQumL58n4GEbr48QUpb
hbi7Kb6JEyYAKt+pmNsqdxttylGMbhFOhJdctucuAJ3syou8QnJFMyWvowA9uZo7
MRztmClo5IcFG79DBgmr8vP8kKtPa+FwoTKJZwkk/rGy0zLPANLvi7pWTwpYskI3
aii7Nwwv2ouS5W51cs7pewTE6f8gEtji18XiaKblJ/4j7Ir3xy50afczPFeGVVtB
v2lmxMeA2FSy0uSH3nfh3pc/A0xTvjRfoSgfn2MQzhtoeFbzLEKn3gjhed6Eonq+
1eb/c1NqeY3JRzp4lclFjz4KEEwoRA==
=YxUi
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Jul 20 20:54:45 2020
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 AAE643A1387; Mon, 20 Jul 2020 20:54:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, 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 itS-IdnJUuhB; Mon, 20 Jul 2020 20:54:40 -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 EA2C43A0DCF; Mon, 20 Jul 2020 20:54:39 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id E6585548011; Tue, 21 Jul 2020 05:54:34 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id DE9B5440043; Tue, 21 Jul 2020 05:54:34 +0200 (CEST)
Date: Tue, 21 Jul 2020 05:54:34 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Sheng Jiang <jiangsheng@huawei.com>
Cc: "anima@ietf.org" <anima@ietf.org>, "anima-chairs@ietf.org" <anima-chairs@ietf.org>
Message-ID: <20200721035434.GA5003@faui48f.informatik.uni-erlangen.de>
References: <12ed9e0beafe415fb3e6df59bb74c85e@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <12ed9e0beafe415fb3e6df59bb74c85e@huawei.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/Aavbw2vU7vXNMdiq3f_8qc3qfko>
Subject: [Anima] ANIMA: Reminder: Re: Call for agenda ANIMA @ IETF 108, online
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, 21 Jul 2020 03:54:43 -0000

Reminder. Please bring forward for any agenda items you want to see.!

Thanks
    Toerless

On Fri, Jul 10, 2020 at 07:51:34AM +0000, Sheng Jiang wrote:
> Hi, all anima,
> 
> 
> 
> We have been allocated a sessions of 1 hour 40 minutes for the ANIMA WG meeting for IETF-108 (online). It is on Thursday, July 30, 2020?? 11:00-12:40 (UTC). We are now starting to collect agenda items for the session. Please send your request for agenda by July 21th, Tuesday, to anima-chairs@ietf.org and both chairs' email. Please note that email to a single chair may cause single-point failure.
> 
> 
> 
> 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) requests for time slot by July 21th, Tuesday and include:
> 
> 
> 
> Name of time slot:
> 
> Name of draft(s):
> 
> Time requested:
> 
> Presenter name(s):
> 
> 
> 
> More details about the IETF 108 can be found at:
> 
> 
> 
> https://www.ietf.org/how/meetings/108/
> 
> 
> 
> 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,
> 
> 
> 
> Sheng + Toerless
> 

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


From nobody Tue Jul 21 04:00:43 2020
Return-Path: <kivinen@iki.fi>
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 1506E3A0A4F; Tue, 21 Jul 2020 04:00:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iki.fi
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 0uB6dn_Ow6is; Tue, 21 Jul 2020 04:00:38 -0700 (PDT)
Received: from lahtoruutu.iki.fi (lahtoruutu.iki.fi [IPv6:2a0b:5c81:1c1::37]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AC543A0A4D; Tue, 21 Jul 2020 04:00:36 -0700 (PDT)
Received: from fireball.acr.fi (fireball.kivinen.iki.fi [IPv6:2001:1bc8:100d::2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: kivinen) by lahtoruutu.iki.fi (Postfix) with ESMTPSA id F27731B00093; Tue, 21 Jul 2020 14:00:30 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=lahtoruutu;  t=1595329233; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=fW4MRMERSVmCRkP0QlaUl3AwOvRUTMqZYp34H7s3rGQ=; b=QflMue2Zz4S+qKMtI2JInlwLLvH8kVTwXLXfiIbHQW5bInPaVt+fHJLNfpw/ZDI6Vp1YUf cEIJEyZ0czwlu+ZiNpn7kIlFpKPFZYjmir3UsGayvqboJo/FDh+7ArC3fcTX//Hmgua5yh 5TEJUtHQ7eCAMJo4lP+kecpKcxY1wjKt80dLV3YjhoFTlt93nME1/AihlP1kZBPoO74Jkx UA5JLuFwWQKhp2/nI5jZDrmF9WIWG2WmRBe56/nT2tcr3y03B8ahZRDXwbWK5CGHmUKpgs ge8njqVom4niCRlUJ8P3zoGEqXCVICYTduAxrhk36lH4f0dj30jXQYpO2UUJiw==
Received: by fireball.acr.fi (Postfix, from userid 15204) id AEF5225C11CC; Tue, 21 Jul 2020 14:00:30 +0300 (EEST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <24342.51918.664855.708819@fireball.acr.fi>
Date: Tue, 21 Jul 2020 14:00:30 +0300
From: Tero Kivinen <kivinen@iki.fi>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: ipsec@ietf.org, anima@ietf.org, draft-ietf-anima-autonomic-control-plane@ietf.org
In-Reply-To: <6871.1595023836@localhost>
References: <7EDA9264-8007-4221-9A0D-D967C9AD8BD9@gmail.com> <0b8001d5ecad$79ce7ad0$6d6b7070$@gmail.com> <alpine.LRH.2.21.2002261504240.27113@bofh.nohats.ca> <0c9e01d5ed4c$2353f5a0$69fbe0e0$@gmail.com> <20200619145112.GA47906@faui48f.informatik.uni-erlangen.de> <alpine.LRH.2.22.394.2006191126200.32638@bofh.nohats.ca> <24142.1592760359@localhost> <24309.64229.308771.733097@fireball.acr.fi> <20200626161053.GQ41244@faui48f.informatik.uni-erlangen.de> <24315.37346.143409.46224@fireball.acr.fi> <20200630202812.GF13952@faui48f.informatik.uni-erlangen.de> <24336.33964.354779.953171@fireball.acr.fi> <6871.1595023836@localhost>
X-Mailer: VM 8.2.0b under 26.3 (x86_64--netbsd)
X-Edit-Time: 13 min
X-Total-Time: 12 min
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=lahtoruutu; t=1595329233; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=fW4MRMERSVmCRkP0QlaUl3AwOvRUTMqZYp34H7s3rGQ=; b=S2KU7u3zyu+tSlBEG/8uLwKCJht9TbFIrNjqM31ygxCU6HqeR11N1ogHUaKxD/TNaMgevv 1lxX5BqFCDi3x0bpIqixgaeP86Zr62Cbr0r58JfsTbafd2GGml6uGxotdMmNj7B5t1ccN3 jtniKfOSEFHxTyjwaEw9z7ULmIe+osv+GsyljJSBKT58/+HE7S28ENGgIeiyxNkilecq3K 3FbRmxFwrbv8bKrCacDK+ndp94GSuJ1Kl+OVISkUt2ZHA4CMk5rQAWElVqKfx9FxbD4EJD UJ5d7FciR5ayc3Ne25NRKPRJ5Y7y9MSE8S5YTn6f42LamPsR18O4PG6pgrih4Q==
ARC-Seal: i=1; s=lahtoruutu; d=iki.fi; t=1595329233; a=rsa-sha256; cv=none; b=WzuPtvO3O+N/R/V81Ixka+crVTgUmqAuy9rgVvb42D8A4aFcIgLPSTv2uUTL+KyeNcveDd eJXxLtVhzxOeNIVHei2q9a7KtvqdWRAqs2IwaPQJf6q7WleTkI712p6TKE4HDUDvHz3WXG 6tlhMCdKBjaJtAI/xlf3wX5I1g/Vq2Hs4dVFb8HkwhCxRVK0PS+VOPFXqmCa4d+tnSt4Xf Thzzw0A+00Fr/mP2mpz05nX4q3aVg5g2MBB5RGS3uQiTszWzsClhoHYJW5gmn0TK43Xp5W T/QGle+HRzlFmgrj4Cs952rM8mTrAUCScf2D/jvITzzvtVOwZbTsTa6Znnq8tA==
ARC-Authentication-Results: i=1; ORIGINATING; auth=pass smtp.auth=kivinen smtp.mailfrom=kivinen@iki.fi
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/0wHc_0kGaCYmY7Aa98gOuDbfQSc>
Subject: Re: [Anima] [IPsec] Troubleshooting IPsec peer certs (was: Re: IPsec profile feedback wanted (draft autonomic control) plane)
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, 21 Jul 2020 11:00:41 -0000

Michael Richardson writes:
> I am not really following this discussion very well.
> I'm not sure if this is general advice or ACP specific advince.

This discussion was not ACP specific, this was just generic reasons
why CERTREQ etc are usuful in general. Anyways I think most ACP cases
do not need CERTREQ, but on the other hand there might be cases where
it is still useful there, and thats why I would hate to see profile
that forbits its use. I.e., it is fine to say in profile, that
CERTREQs might not be needed, but saying that they should/must not be
sent is bad idea. 

> In the case that you describe (RSA->ECDSA),  I think that we would sign TA1
> with TA2, or vice-versa. (probably one and then the other a month later).
> We can feed/update the trust anchors when certificates are renewed, or we can
> use draft-ietf-netconf-trust-anchors to change things (the advantages of
> having really good security for in-band management)

If you have proper management, then you can do almost instanteneous
changes, but CERTREQ allows you do do similar things even when you do
not have any kind of management system configuring devices, with much
longer overlaps in configuration. 

> I prefer relatively short expiries for certificates in the ACP
> because <STAR reasons>. I think that all systems have to support
> both RSA and ECDSA for a big overlapping period. I don't think this
> is a problem.
> 
> I think that there is not a problem having a RSA key (TA1) sign an
> ECDSA EE cert. I know that I've done it, but I know that some think
> it uncool.

Sometimes the problem is that there are devices there which do not
support ECDSA at all, which means you are stuck with RSA for both root
and EE for all devices. With CERTREQ some parts of the network can
start use full ECDSA TA and EE and still interoperate with those
devices which support both and get the "coolness" factor of not using
RSA at all :-)

Other similar cases comes when you merge authorization domains
together, i.e., two companies merge and they both had their own CAs
before, and not all devices support both CAs, so you need to pick
correct certificate one when talking to one or another device. 

> You are imagining a period of time where we are installing the trust anchors,
> and I don't see it has to be like that.
> 
> Have TA1 sign TA2 as a sub-CA, and then pass out TA1->TA2->EE(ecdsa)
> chain to the new nodes. Once this is done for all nodes, you can
> drop TA1. In reality, there are probably at least an extra level of
> CA, possibly two.
> 
> Do you think that I should include this situation into draft-richardson-registrar-operational-considerations?

The text I provided earlier was just general IPsec case, I have not
checked out situation in this specific case, so I cannot comment on
that before I read that document... 

>     >> The full name of a node was so far an rfc822Name, now i need to
>     >> fix it to become what i think is going to be a GeneralName,
>     >> and hence it might best be to signal IDi/IDr as ID_DER_ASN1_GN
> 
>     > Note, that the IDi and IDr are what is matched against the IPsec
>     > policy, i.e., nothing in the certificate will cause policy to be
>     > selected, only IDi and IDr does that. After IDi and IDr identifies the
>     > suitable policy, we can go and match the information in the policy
>     > against the certificate. That policy might include information like
>     > how to match the certificate subject alt name or subject name to
>     > identity or information in the policy.
> 
> So, we've been forced to use otherName, and this will cause new code in some
> of the IKEv2 daemon that we need to use :-(

No, you are not forced to use anything. Your ID could be KEY_ID with
just random 128-bit binary blob, and you could find your policy entry
based on that. Then in the policy entry there might be information
what should be present in the certificate, or even just hash of the
raw public key (which could be also be sent inside the certificate in
some cases).

IDi and IDr are used to find the policy, policy information is used to
verify that the authorization information provided are correct. That
information usually includes trust anchors, and information what
should be in the certificate signed by those trust anchors.
-- 
kivinen@iki.fi


From nobody Tue Jul 21 04:40:20 2020
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 BFB5D3A00E4; Tue, 21 Jul 2020 04:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level: 
X-Spam-Status: No, score=-9.601 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, DKIM_VALID_EF=-0.1, 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 0QWZdlc2Fs-S; Tue, 21 Jul 2020 04:40:17 -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 6CD3C3A00B0; Tue, 21 Jul 2020 04:40:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1923; q=dns/txt; s=iport; t=1595331616; x=1596541216; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=BR717rJ3E06D0/ueAvJM577bfuPODRmDRPBSXChHJq0=; b=TZrzqVvEADbLhuurhrrP8qP3vZc4uV+U/HrcRheMOIFYxEzvwcPNDVwn 5fCLLXiC2u5qFFMBha/WozR9uvy2QS0R0bXPoTUFri40KcopelaCDMQhc 7AcqAQ1aB2IeocrG2hMzoCCqfzdu/wWs9/p8+u7QuOp5QgnDbyrbKYdtG Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AKAQAR0xZf/xbLJq1gGwEBAQEBAQE?= =?us-ascii?q?BBQEBARIBAQEDAwEBAUCBSoMZVAEgEiyNNIgTmiCBaQsBAQEMAQEYCwwEAQG?= =?us-ascii?q?ETAKCGyU4EwIDAQELAQEFAQEBAgEGBG2FXAyFcQEBAQMBAQEbHTQLBQsLDgo?= =?us-ascii?q?uJzAGE4MmAYJcIA+rSXSBNIQ7AYYIBoE4AYhYhDOCAIE4HIJNPoEEgVgBAYE?= =?us-ascii?q?qARECASCDSYItBI8piiSbeoJngwiWWwMegnqJPoR+jhKFP6dvg1ICBAYFAhW?= =?us-ascii?q?BaiNncDMaCBsVOyoBggoBMz4SGQ2ONohthUEDPwMwNwIGCAEBAwmQMwEB?=
X-IronPort-AV: E=Sophos;i="5.75,378,1589241600"; d="scan'208";a="28065800"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 21 Jul 2020 11:40:12 +0000
Received: from [10.61.224.235] ([10.61.224.235]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 06LBeBXd022275 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 21 Jul 2020 11:40:12 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: Eliot Lear <lear@cisco.com>
In-Reply-To: <20200721035434.GA5003@faui48f.informatik.uni-erlangen.de>
Date: Tue, 21 Jul 2020 13:40:11 +0200
Cc: Sheng Jiang <jiangsheng@huawei.com>, "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "anima@ietf.org" <anima@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <CA50D621-B014-4D30-8DCE-2A06DEC6460B@cisco.com>
References: <12ed9e0beafe415fb3e6df59bb74c85e@huawei.com> <20200721035434.GA5003@faui48f.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
X-Outbound-SMTP-Client: 10.61.224.235, [10.61.224.235]
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/jZ7y5yj_WWC9NaKS2cBx648Z87E>
Subject: Re: [Anima] ANIMA: Reminder: Re: Call for agenda ANIMA @ IETF 108, online
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, 21 Jul 2020 11:40:19 -0000

Hi Toerless,

The co-authors would like to have a few minutes to talk about BRSKI-AE.  =
I think 10 ought to do.

Thanks,

Eliot

> On 21 Jul 2020, at 05:54, Toerless Eckert <tte@cs.fau.de> wrote:
>=20
> Reminder. Please bring forward for any agenda items you want to see.!
>=20
> Thanks
>    Toerless
>=20
> On Fri, Jul 10, 2020 at 07:51:34AM +0000, Sheng Jiang wrote:
>> Hi, all anima,
>>=20
>>=20
>>=20
>> We have been allocated a sessions of 1 hour 40 minutes for the ANIMA =
WG meeting for IETF-108 (online). It is on Thursday, July 30, 2020?? =
11:00-12:40 (UTC). We are now starting to collect agenda items for the =
session. Please send your request for agenda by July 21th, Tuesday, to =
anima-chairs@ietf.org and both chairs' email. Please note that email to =
a single chair may cause single-point failure.
>>=20
>>=20
>>=20
>> 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
>>=20
>>=20
>> Please send us (anima-chairs at ietf.org) requests for time slot by =
July 21th, Tuesday and include:
>>=20
>>=20
>>=20
>> Name of time slot:
>>=20
>> Name of draft(s):
>>=20
>> Time requested:
>>=20
>> Presenter name(s):
>>=20
>>=20
>>=20
>> More details about the IETF 108 can be found at:
>>=20
>>=20
>>=20
>> https://www.ietf.org/how/meetings/108/
>>=20
>>=20
>>=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
>>=20
>>=20
>> Best regards,
>>=20
>>=20
>>=20
>> Sheng + Toerless
>>=20
>=20
> --=20
> ---
> tte@cs.fau.de
>=20
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima


From nobody Tue Jul 21 07:54:35 2020
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 6AD573A09DE; Tue, 21 Jul 2020 07:54:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 AqdsqLpbuG_g; Tue, 21 Jul 2020 07:54:28 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C0653A09DD; Tue, 21 Jul 2020 07:54:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id B0B1938A1E; Tue, 21 Jul 2020 10:34:01 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id S53sxJWtEzh0; Tue, 21 Jul 2020 10:34:00 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 2AF0E38A1A; Tue, 21 Jul 2020 10:34:00 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 6C3C03F; Tue, 21 Jul 2020 10:54:25 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Tero Kivinen <kivinen@iki.fi>, ipsec@ietf.org, anima@ietf.org
In-Reply-To: <24342.51918.664855.708819@fireball.acr.fi>
References: <7EDA9264-8007-4221-9A0D-D967C9AD8BD9@gmail.com> <0b8001d5ecad$79ce7ad0$6d6b7070$@gmail.com> <alpine.LRH.2.21.2002261504240.27113@bofh.nohats.ca> <0c9e01d5ed4c$2353f5a0$69fbe0e0$@gmail.com> <20200619145112.GA47906@faui48f.informatik.uni-erlangen.de> <alpine.LRH.2.22.394.2006191126200.32638@bofh.nohats.ca> <24142.1592760359@localhost> <24309.64229.308771.733097@fireball.acr.fi> <20200626161053.GQ41244@faui48f.informatik.uni-erlangen.de> <24315.37346.143409.46224@fireball.acr.fi> <20200630202812.GF13952@faui48f.informatik.uni-erlangen.de> <24336.33964.354779.953171@fireball.acr.fi> <6871.1595023836@localhost> <24342.51918.664855.708819@fireball.acr.fi>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512; protocol="application/pgp-signature"
Date: Tue, 21 Jul 2020 10:54:25 -0400
Message-ID: <21070.1595343265@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/4W3jtX2Wg0blm9xXkJLKLmX53p8>
Subject: Re: [Anima] [IPsec] Troubleshooting IPsec peer certs (was: Re: IPsec profile feedback wanted (draft autonomic control) plane)
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, 21 Jul 2020 14:54:31 -0000

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


Tero Kivinen <kivinen@iki.fi> wrote:
    >> I am not really following this discussion very well.
    >> I'm not sure if this is general advice or ACP specific advince.

    > This discussion was not ACP specific, this was just generic reasons
    > why CERTREQ etc are usuful in general. Anyways I think most ACP cases
    > do not need CERTREQ, but on the other hand there might be cases where
    > it is still useful there, and thats why I would hate to see profile
    > that forbits its use. I.e., it is fine to say in profile, that
    > CERTREQs might not be needed, but saying that they should/must not be
    > sent is bad idea.

I hope that at no point do we forbid the use of anything.
A peer might not expect it/do anything.
The important part is that we say what pieces we *do* require.
There is one more revision of ACP coming out on Monday, and I hope that is
the last one that the IESG will approve on the next telechat.

    >> In the case that you describe (RSA->ECDSA),  I think that we would sign TA1
    >> with TA2, or vice-versa. (probably one and then the other a month later).
    >> We can feed/update the trust anchors when certificates are renewed, or we can
    >> use draft-ietf-netconf-trust-anchors to change things (the advantages of
    >> having really good security for in-band management)

    > If you have proper management, then you can do almost instanteneous
    > changes, but CERTREQ allows you do do similar things even when you do
    > not have any kind of management system configuring devices, with much
    > longer overlaps in configuration.

I think that proper management will probably not be in revision 1 of products.
However, a killer-use-case for the ACP is for SDN control channels, so I
could be wrong.

    >> I prefer relatively short expiries for certificates in the ACP
    >> because <STAR reasons>. I think that all systems have to support
    >> both RSA and ECDSA for a big overlapping period. I don't think this
    >> is a problem.
    >>
    >> I think that there is not a problem having a RSA key (TA1) sign an
    >> ECDSA EE cert. I know that I've done it, but I know that some think
    >> it uncool.

    > Sometimes the problem is that there are devices there which do not
    > support ECDSA at all, which means you are stuck with RSA for both root
    > and EE for all devices. With CERTREQ some parts of the network can
    > start use full ECDSA TA and EE and still interoperate with those
    > devices which support both and get the "coolness" factor of not using
    > RSA at all :-)

I think that we say that we will tolerate RSA :-)
So you are right: there could be devices which do not do ECDSA on day one,
and in which case, you can't switch the keys at all.

    > Other similar cases comes when you merge authorization domains
    > together, i.e., two companies merge and they both had their own CAs
    > before, and not all devices support both CAs, so you need to pick
    > correct certificate one when talking to one or another device.

Yes, this is an important case.

    >> So, we've been forced to use otherName, and this will cause new code in some
    >> of the IKEv2 daemon that we need to use :-(

    > No, you are not forced to use anything. Your ID could be KEY_ID with

No, the ACP document has been forced to use otherName in it's
certificates. That's nothing to do with IPsec/IKEv2.
But, that that's what IKEv2 will have to deal with.


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




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

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

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl8XAaAACgkQgItw+93Q
3WWDbwf+Ox6bVwyB9gewn1K+dFyTb2sOKTUNZVuUWV7L7AleuuD0ayk4LpJ8kB40
5eGQzhfOHvgdTv39LSSwW+OWEaG8QFZPEJloIDOOv0tXgsaOliPdvHDNmUdu2wuP
1c3bC7yhj4mgFOpSrjdjXkqzd0S3dMWe7ZUSOLEXx9GAt6LKeD3DzGB+tBdVd4eq
lQVxOUIJ/yGeSjvEL4UkF3yJDOAqtlNzZ0yD6MJArEQgujClM6ulSE9/po5aYRTW
AyyKbu6jTWKrU7IoOH5gmMBDiIXM7a7MNVtyQliUswnjNFBoOBE3wCEWNrN/nI9x
sz33JeBVVMj0FlVzamS7JDMtY1eXfQ==
=hGwh
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Jul 21 16:51:27 2020
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 677693A0843 for <anima@ietfa.amsl.com>; Tue, 21 Jul 2020 16:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 vFnEpZATHWCU for <anima@ietfa.amsl.com>; Tue, 21 Jul 2020 16:51:23 -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 995A53A0840 for <anima@ietf.org>; Tue, 21 Jul 2020 16:51:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id D746F38A26; Tue, 21 Jul 2020 19:30:56 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ul8KyqCGH_55; Tue, 21 Jul 2020 19:30:56 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 261F6389D0; Tue, 21 Jul 2020 19:30:56 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id BA3E4A8; Tue, 21 Jul 2020 19:51:21 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
CC: "Fries\, Steffen" <steffen.fries@siemens.com>, "Brockhaus\, Hendrik" <hendrik.brockhaus@siemens.com>, max pritikin <pritikin@cisco.com>, Eliot Lear <lear@cisco.com>
In-Reply-To: <a26f70c7dc5145b581f71ece3106529b@siemens.com>
References: <4a3b24b3737f4dcbbf3154c89d9c8200@siemens.com> <17250.1594397451@localhost> <a26f70c7dc5145b581f71ece3106529b@siemens.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512; protocol="application/pgp-signature"
Date: Tue, 21 Jul 2020 19:51:21 -0400
Message-ID: <26733.1595375481@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/1yZkQH8x1xsSsgF5Cfp3ZPjpgVg>
Subject: [Anima] last minute changes to BRSKI to do endpoint discovery
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, 21 Jul 2020 23:51:25 -0000

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


The BRSKI-AE authors have suggested that in order to make BRSKI more
easily extendable that prior to using the /.well-known/est end points (both RFC7030
ones and bootstrapping-keyinfra ones), that the pledge should ask for
/.well-known/brski, to get back a list.

The thread ending at https://mailarchive.ietf.org/arch/msg/anima/MQkNXJJjMkP0nqKlNEaxDZ94RgI
alludes to this, but the current -03 document does not include this proposal,
because it would need to go into BRSKI itself.

   REQ: GET /.well-known/brski

   RES: Content-Type: application/link-format   {see RFC6690}
     </brski/voucherrequest>,ct=voucher-cms+json
     </brski/voucher_status>,ct=json
     </brski/requestauditlog>,ct=json
     </brski/enrollstatus>,ct=json

     </est/cacerts>;ct=pkcs7-mime
     </est/cacerts>;ct=pkcs7-mime
     </est/simpleenroll>;ct=pkcs7-mime
     </est/simplereenroll>;ct=pkcs7-mime
     </est/fullcmc>;ct=pkcs7-mime
     </est/serverkeygen>;ct= pkcs7-mime
     </est/csrattrs>;ct=pkcs7-mime

      </cmp/initialization>;ct=pkixcmp
     </cmp/certification>;ct=pkixcmp
     </cmp/keyupdate>;ct=pkixcmp
     </cmp/p10>;ct=pkixcmp
     </cmp/getCAcert>;ct=pkixcmp
     </cmp/getCSRparam>;ct=pkixcmp

This is already done in draft-ietf-ace-coap-est-18, BTW.
But, it asks /.well-known/core?rt=ace.est rather than /.well-known/brski.

At this point, we are waiting for ACP document to be approved by the IESG.
Assuming that our AD was amenable, I think that this could be snuck in before
ACP is approved.   This email does not include my opinion, as it has not yet
been formed.

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

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

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

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl8Xf3kACgkQgItw+93Q
3WUvbAgAobDNhkGNSjL7cwcMrtT9WLzymLYb8Me6lPsPFclvZm79VQd+d5dxI9BV
t5O+BTVMqs9UbPhpCCgfLZXHtc9q2AbXqEA5YYNB0U7SEoDbj95iwKshl8jGVhYX
MBYJgYOVki31SZAoQ9u393x6zIjYup1eTbmNy34vXZ+SZDtkx5s6jmZzO4obLg0S
VHnitp46RpoguwIre7FKJlW/WPXb1naqnOmo0z9XqgYIQ0nzYlJVMUXOl1XPg0rX
QOYUS7H8498MtFxw/PwJXi+Yyp8NURBToFjYJCxHJHDmYH/46+grVCJ2eMIWzTIn
r9cyeIErANswB6eg7tOUOECnD8ifpw==
=2IQ7
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Jul 21 18:43:08 2020
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 DE2003A0816 for <anima@ietfa.amsl.com>; Tue, 21 Jul 2020 18:43:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, 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 Q3g39ALUEq7v for <anima@ietfa.amsl.com>; Tue, 21 Jul 2020 18:43:04 -0700 (PDT)
Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) (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 3C90F3A0814 for <anima@ietf.org>; Tue, 21 Jul 2020 18:43:04 -0700 (PDT)
Received: by mail-pj1-x102f.google.com with SMTP id f16so340181pjt.0 for <anima@ietf.org>; Tue, 21 Jul 2020 18:43:04 -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=cmPdqmc55Hyl7mUe2xuShSzKpsdHeT4AM8B9KUd21uc=; b=kMm/BGS1sH7yZ+SHyR8DHNBrr3I9lx4WfSQmwgvWJxgmMl8xBlH0+CrMIMruAsGY2E W+r1clddwOpKchvTZSq/9CCvOdMIdr89vLnVcu04I0JXUEP25bce8vt1Cayx+EGad+84 BBAwaKj8RdGgV0nx99zxumbZAYJcMGb+xAc/8wPc8xm87jxAOcllXsWTqqE3escCq6hP WXKpZJNwmDMJllb/qp9Mfsr/O8Ic2Em4VIip6Daa27sJJMdDKlt7mZpc355vDqUxUtem IZcV1r/6UWKfc/3LuKwKHcgTMWna28sTTn2OURk6Ge60dHBJwqVvwFYbOjcEeTxsyrJA +2Gw==
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=cmPdqmc55Hyl7mUe2xuShSzKpsdHeT4AM8B9KUd21uc=; b=n0RpPJs4upLBHzsW65lhyBgD/fRE90jpXt6qmFTibm5WxRM8wpZYU+kcA7ixYaZrGT fRBO0s4BGZPtKfKioWLHLXDuX/CKngEUeCUm+yFuYZ85xcM9gLkA0UBSbVSKR2dAVcRc /kPX6yZvC+ObP2xH1MJteGPUGrIL2ZThz/cNV/EKgz+FkVkpnVskapygco+UHQ8x7btC 4mXWpFvSroFNGO33rb76vdRJjgT/KNOEfQGJ7OcynmwX7jOY7/RuAC5Zu3VcbNMHIp25 7trN9V3v71FyTmc+nm+gxAtvSKYxkDjBjlI5H2VllL+vrQMcWbdGcMvDTifz+frw4Or3 2o1g==
X-Gm-Message-State: AOAM533y8exMQDP+1p9em9iTIOVwhN18HzxvuBJLAh6PYHmcbsJkIGIQ 6Wrx9dWmBJEoK4bBQ0kcmZ/Tj6mV
X-Google-Smtp-Source: ABdhPJwz3EwwTnwhGWcNNTwDQX93en4qRTPWz0Fpdioqbpe+UtMoEyKOwzRdy5U8JSaRNMOlkkpjQw==
X-Received: by 2002:a17:90a:de8d:: with SMTP id n13mr7233996pjv.95.1595382183378;  Tue, 21 Jul 2020 18:43:03 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.139.192]) by smtp.gmail.com with ESMTPSA id e6sm21801157pfh.176.2020.07.21.18.43.01 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Jul 2020 18:43:02 -0700 (PDT)
To: anima@ietf.org
References: <4a3b24b3737f4dcbbf3154c89d9c8200@siemens.com> <17250.1594397451@localhost> <a26f70c7dc5145b581f71ece3106529b@siemens.com> <26733.1595375481@localhost>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <41316bee-c858-27ab-30d7-4c6b1d6bdc0c@gmail.com>
Date: Wed, 22 Jul 2020 13:43:00 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <26733.1595375481@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/4WZGMfCL0z1tld0KjXxoCRkUplk>
Subject: Re: [Anima] last minute changes to BRSKI to do endpoint discovery
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, 22 Jul 2020 01:43:06 -0000

No technical objection from me.

It isn't just the AD who decides though, is it? It's a substantive change.
That means, according to my Policy Wonk's Handbook, a brief WGLC, a brief
IETF LC, and another run at the IESG agenda.

If that's the case, I'd suggest another approach (either a future short RFC
that updates the BRSKI RFC, or make BRSKI-AE formally update the BRSKI RFC).

Regards
   Brian

On 22-Jul-20 11:51, Michael Richardson wrote:
> 
> The BRSKI-AE authors have suggested that in order to make BRSKI more
> easily extendable that prior to using the /.well-known/est end points (both RFC7030
> ones and bootstrapping-keyinfra ones), that the pledge should ask for
> /.well-known/brski, to get back a list.
> 
> The thread ending at https://mailarchive.ietf.org/arch/msg/anima/MQkNXJJjMkP0nqKlNEaxDZ94RgI
> alludes to this, but the current -03 document does not include this proposal,
> because it would need to go into BRSKI itself.
> 
>    REQ: GET /.well-known/brski
> 
>    RES: Content-Type: application/link-format   {see RFC6690}
>      </brski/voucherrequest>,ct=voucher-cms+json
>      </brski/voucher_status>,ct=json
>      </brski/requestauditlog>,ct=json
>      </brski/enrollstatus>,ct=json
> 
>      </est/cacerts>;ct=pkcs7-mime
>      </est/cacerts>;ct=pkcs7-mime
>      </est/simpleenroll>;ct=pkcs7-mime
>      </est/simplereenroll>;ct=pkcs7-mime
>      </est/fullcmc>;ct=pkcs7-mime
>      </est/serverkeygen>;ct= pkcs7-mime
>      </est/csrattrs>;ct=pkcs7-mime
> 
>       </cmp/initialization>;ct=pkixcmp
>      </cmp/certification>;ct=pkixcmp
>      </cmp/keyupdate>;ct=pkixcmp
>      </cmp/p10>;ct=pkixcmp
>      </cmp/getCAcert>;ct=pkixcmp
>      </cmp/getCSRparam>;ct=pkixcmp
> 
> This is already done in draft-ietf-ace-coap-est-18, BTW.
> But, it asks /.well-known/core?rt=ace.est rather than /.well-known/brski.
> 
> At this point, we are waiting for ACP document to be approved by the IESG.
> Assuming that our AD was amenable, I think that this could be snuck in before
> ACP is approved.   This email does not include my opinion, as it has not yet
> been formed.
> 
> --
> 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 Wed Jul 22 00:59:28 2020
Return-Path: <hendrik.brockhaus@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 6DEEB3A0F7A for <anima@ietfa.amsl.com>; Wed, 22 Jul 2020 00:59: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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=siemens.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tHOkf3-FZPkj for <anima@ietfa.amsl.com>; Wed, 22 Jul 2020 00:59:26 -0700 (PDT)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-eopbgr40041.outbound.protection.outlook.com [40.107.4.41]) (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 AEE943A0F79 for <anima@ietf.org>; Wed, 22 Jul 2020 00:59:25 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OSeZeawXg9c6txhbMrhQbZD/Kjh6JvI2UJmjWhvdv99mwmjMNPkmuGdSbLkbVO5xGswGSxwWlENhOU11Br+IsiNS72YRmPS71BQNbPHTzSPkpsFNNbknvpQbxdLxDhbFcOIKkcRoIeo3gp1thMhYjnBO7PohHFJptzUGb5fEteDVkA8MSBYuxsk3ZoorQajWIuNG92rgbga6VKHD5BJxME5/6xQY4oPiLgeF4YTpBQ5kakig6gFquN/mxEaOUsmgswyjZqIo5UM2t/x88eCeok89q65x8RPwVCyQ6MWJoxFvazcRQVXoPpGX8qqlTt+MGFdhbKdkiaofkHs3mcyeng==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=IVa/NHennqdxaJjZ92yAFohQpqn1cQbEtflmJauhOyU=; b=SfJv03X0Zlvqn6xRWjuWg/Zeu1VpQxy2FWE0G9QSeTnEB/5OM0eT+w7yOsPLHPM3f76DcmHwFk4KLQc8DEP5yDWmAJU1GY8wwjSkBt+KNGh5AvPRSVZfuRG0/Mj71uf29NGqFg+Vt/MCw4oY6Z2o4BsoNchOdzMAbuNjKQdYgDnTjLYIE88uLrRuRm88beaA6dPAv/kh822yVgKHK3jD1Zxat2kqaOe0Qnhs2gUIuUw/noko5erpaPJxDN7nFTNrkTG7XzY51efqCtvdTbU+vHZ5t1IenqKtiC/XX5Hyy8f3GKPtnAFFXu8DDz8WUTX3BTxo/bKzFJug5UdN4H7sQA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=siemens.com; dmarc=pass action=none header.from=siemens.com; dkim=pass header.d=siemens.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=siemens.onmicrosoft.com; s=selector1-siemens-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=IVa/NHennqdxaJjZ92yAFohQpqn1cQbEtflmJauhOyU=; b=J2vbyKjkq+vG9dZsj7aDtpMchJzpTklV+pq3SH7a8ciu3PIBZJQ8DSMKUspodHWdjspMpvbl17kV05MKAsJeG5efrtPGZrl6KneCrjD8ok/gub/EOGy/ig8B0KDCbQRrYHBwqrC4EC487wT1wtUlI+gJyP94+Wufy1wBJU6DaYw=
Received: from AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:208:184::10) by AM0PR10MB3457.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:20b:154::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3216.22; Wed, 22 Jul 2020 07:59:23 +0000
Received: from AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM ([fe80::288b:3b52:cf90:8fc0]) by AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM ([fe80::288b:3b52:cf90:8fc0%9]) with mapi id 15.20.3195.028; Wed, 22 Jul 2020 07:59:23 +0000
From: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "anima@ietf.org" <anima@ietf.org>
CC: "steffen.fries@siemens.com" <steffen.fries@siemens.com>, max pritikin <pritikin@cisco.com>, Eliot Lear <lear@cisco.com>
Thread-Topic: last minute changes to BRSKI to do endpoint discovery
Thread-Index: AQHWX7nZh6IHFyMmykeXnoOiF6WViqkTOqpA
Date: Wed, 22 Jul 2020 07:59:22 +0000
Message-ID: <AM0PR10MB3153F5AA4119DBDDB97F6D06FE790@AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM>
References: <4a3b24b3737f4dcbbf3154c89d9c8200@siemens.com> <17250.1594397451@localhost> <a26f70c7dc5145b581f71ece3106529b@siemens.com> <26733.1595375481@localhost>
In-Reply-To: <26733.1595375481@localhost>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ActionId=4a95e6e6-4b56-475b-8ec2-00001ca802c2; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ContentBits=0; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Enabled=true; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Method=Standard; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Name=restricted-default; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SetDate=2020-07-22T07:52:34Z;  MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SiteId=38ae3bcd-9579-4fd4-adda-b42e1495d55a;
x-document-confidentiality: NotClassified
authentication-results: sandelman.ca; dkim=none (message not signed) header.d=none;sandelman.ca; dmarc=none action=none header.from=siemens.com;
x-originating-ip: [165.225.200.158]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: d64d7c74-eb38-480f-1f34-08d82e15257a
x-ms-traffictypediagnostic: AM0PR10MB3457:
x-ld-processed: 38ae3bcd-9579-4fd4-adda-b42e1495d55a,ExtAddr
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <AM0PR10MB34573DD350D381F45CC6F5D4FE790@AM0PR10MB3457.EURPRD10.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: VH7DjA670hDvoeD/c/NL54Lr8HKwltVHGM0mnJdtZy9i0jTCHUAlq8qhRWXAFoxCJw7f47467ns9lRwCvNF1M2+b8MeD21xx1dwYgJDwQiseegl1277HiwsM+R772ZwGtD8cYxseWysyiGE/9CJGIf2uQuumOECKgyh/LQPwvW4sxFXkMCjAm7s3AniZI2zvkPwkKsUtzTPYbwtkv91cAWlBwuhs8liWQfryZ4WS8hP/a80vOEDCBEsRTRj0AqnruKJ3tKm4eTTQtfyVw8dSZvP5ZKOmHPX6ltaqBdoiEwxP4KPqUAtEVTvxBTD5RrpB6To4Ra5m7UPwGsHZcIghgUBAkDHFFQtzn5amhLYaHyZkcC3Sv3++7H6zYbUBgMziDtRWL+9GsOu1Geoeh6EyTg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(346002)(136003)(366004)(376002)(396003)(39860400002)(52536014)(8676002)(186003)(83380400001)(6506007)(316002)(71200400001)(2906002)(26005)(5660300002)(478600001)(966005)(8936002)(66476007)(66946007)(55236004)(76116006)(7696005)(66556008)(9686003)(55016002)(110136005)(54906003)(86362001)(4326008)(64756008)(33656002)(66446008); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: r8v8c9+5zMTd7lepZaow0CKQaFYi+Hzp2kbA0/AtNO+r+KNk9d5WbbLR+A1twnVxLcgTlcUdqke3jmwVKB3wTZxsZmZeOG6H6DB8gWl329WH6/KkScmzYF6Op/xyz3AT7UMaVTNrmwQk7pnIj1aajBKOgxbigaudM5LZq4nngLnn5knBap2zGMxHuy7aFeP+VFYTHFdVsgydmU6vffDro5oD8I9edl0/91LydfgZQQh6RVFly8WHvW0OE2l0p2UldoutUoTtK87b1czF8q9uvDWSwHrUD7TzGBN0HblEBEpTwgiEWxjjCZk0yw1O9gL1c5B78yNYcXOsF5cO9dfHxYtBFT6LxqoTQHC8X4lDcI4YAhw3l3U2+aWIIKGX3qvfxIPrrjCDmBt8LpqVx9fTl/U3u0n6dRtRDA72GX/eIn5lC38thadQbC6drK4bzTpZR1dCvqxP8QH35anOqfFpH6DXHKebuArJi+UQWqBv/i43uCAM1Ji8COHJ3MfY1rVa
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: siemens.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: d64d7c74-eb38-480f-1f34-08d82e15257a
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jul 2020 07:59:22.6714 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 38ae3bcd-9579-4fd4-adda-b42e1495d55a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: UFHedrOyrZQcrtMENujD9U9khduIDD56Wm5CgS2svqHh04z4SiHuRcPT8Yu/4OWxNmJlv6zcaO3aJhMMZPJnZ6QbffD7uUUMcfkPpintmjQ=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR10MB3457
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/cmw0Ks1Ry9x__MmitLwPJxN-rEw>
Subject: Re: [Anima] last minute changes to BRSKI to do endpoint discovery
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, 22 Jul 2020 07:59:27 -0000

> Von: Michael Richardson <mcr+ietf@sandelman.ca>
>=20
>=20
> The BRSKI-AE authors have suggested that in order to make BRSKI more easi=
ly
> extendable that prior to using the /.well-known/est end points (both RFC7=
030
> ones and bootstrapping-keyinfra ones), that the pledge should ask for /.w=
ell-
> known/brski, to get back a list.
>=20
> The thread ending at
> https://mailarchive.ietf.org/arch/msg/anima/MQkNXJJjMkP0nqKlNEaxDZ94RgI
> alludes to this, but the current -03 document does not include this propo=
sal,
> because it would need to go into BRSKI itself.

I would appreciate to use /.well-known/brski for the endpoints specified in=
 BRSKI and use /.well-known/est for those specified in RFC7030.
This offers more flexibility for future extensions like BSKI-AE.

- Hendrik

>=20
>    REQ: GET /.well-known/brski
>=20
>    RES: Content-Type: application/link-format   {see RFC6690}
>      </brski/voucherrequest>,ct=3Dvoucher-cms+json
>      </brski/voucher_status>,ct=3Djson
>      </brski/requestauditlog>,ct=3Djson
>      </brski/enrollstatus>,ct=3Djson
>=20
>      </est/cacerts>;ct=3Dpkcs7-mime
>      </est/cacerts>;ct=3Dpkcs7-mime
>      </est/simpleenroll>;ct=3Dpkcs7-mime
>      </est/simplereenroll>;ct=3Dpkcs7-mime
>      </est/fullcmc>;ct=3Dpkcs7-mime
>      </est/serverkeygen>;ct=3D pkcs7-mime
>      </est/csrattrs>;ct=3Dpkcs7-mime
>=20
>       </cmp/initialization>;ct=3Dpkixcmp
>      </cmp/certification>;ct=3Dpkixcmp
>      </cmp/keyupdate>;ct=3Dpkixcmp
>      </cmp/p10>;ct=3Dpkixcmp
>      </cmp/getCAcert>;ct=3Dpkixcmp
>      </cmp/getCSRparam>;ct=3Dpkixcmp
>=20
> This is already done in draft-ietf-ace-coap-est-18, BTW.
> But, it asks /.well-known/core?rt=3Dace.est rather than /.well-known/brsk=
i.
>=20
> At this point, we are waiting for ACP document to be approved by the IESG=
.
> Assuming that our AD was amenable, I think that this could be snuck in be=
fore
> ACP is approved.   This email does not include my opinion, as it has not =
yet
> been formed.
>=20
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works  -
> =3D IPv6 IoT consulting =3D-


From nobody Wed Jul 22 03:43:54 2020
Return-Path: <laurent.ciavaglia@nokia.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 420283A053E; Wed, 22 Jul 2020 03:43:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U_1MJJQKhNXv; Wed, 22 Jul 2020 03:43:50 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20092.outbound.protection.outlook.com [40.107.2.92]) (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 7F4DF3A05E2; Wed, 22 Jul 2020 03:43:50 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZlTzx5j1KW1PE8AeAeGqfs4WPF6OXhHCUZZAPFGfi0gcXdN2/sy2flxKIoEL2E59XR4AGAv8gvgGtf0KBLO4SzbQ59iTvpn+QT6j0DmUr6V5QP5B1/P6pJTMEdx+vp/TwDLv3Dc5OPTWzUz2imgD9RnpiSSX5EXHxxW+glXJKr2tkWDgwQkcED2a4L+1PlkQaTztgWglbLtGbGB4NaN8X4j2iCcHhrvRyqoveIgCHaNrn5tdW7cjecAECOKftqrfbOx6Nox5s5Nxd2+ViEZPc1vzuGLKjaf9Hytav/Aa2snbb/RCh4XY3TYRQt4nWLL4PlMdtCibH6R6fYTW7asjOA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=FFNHl3zYPliqSeQ7V417xpRIOAIr/69M1UJ+if3J30U=; b=hu+G40wlVLof1NjFNPhYUoMx50CkWo+2WhNnhfGQjRQ8oPjk+d9cfl5bbwoy66sg/9l2r54OONoNkBH9cLgcGPqzmE7tpmtlt2yPJUo1N6+al0fey4IDqfZxhk3va8WdPPqLPTVys1uz5UYroKRrPDguFyfbU0erZC91nkaQY3m1RrlRjWO/Qh0bTnePI8bxWZyokEutaqicxxsHJbEUJGPzwZnXT4LfCIOcKVRONB1MLm8nZmS5QCGC6ya8mO4v5JznWbHsHDEcRQjrG4fzjalowv6A7ACe8Ni1kaeMOGrCiozPlKPLcIMUjdrXDShhEdWiYvJG7ge0qcNrbNLIsg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nokia.com; dmarc=pass action=none header.from=nokia.com; dkim=pass header.d=nokia.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=FFNHl3zYPliqSeQ7V417xpRIOAIr/69M1UJ+if3J30U=; b=Rk3/HcL4WvvotJluCDQyoFS6jYh9aKSMA84wl/zQDw5BfwcBxOr5Kl7fYead4WlKtOGrQIBhfAYvsA4lSvLclyiKe2JEnRBsg1zEwzgwpQWWsfpDjom9f4pRwT/zvT88gGn27eCBOPh2XNirtGYe55OheVzMI7o1oLQrHjrOheU=
Received: from PR3PR07MB6826.eurprd07.prod.outlook.com (2603:10a6:102:7f::20) by PR3PR07MB6585.eurprd07.prod.outlook.com (2603:10a6:102:61::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3216.17; Wed, 22 Jul 2020 10:43:47 +0000
Received: from PR3PR07MB6826.eurprd07.prod.outlook.com ([fe80::185a:5961:e542:6566]) by PR3PR07MB6826.eurprd07.prod.outlook.com ([fe80::185a:5961:e542:6566%7]) with mapi id 15.20.3216.020; Wed, 22 Jul 2020 10:43:47 +0000
From: "Ciavaglia, Laurent (Nokia - FR/Paris-Saclay)" <laurent.ciavaglia@nokia.com>
To: Toerless Eckert <tte@cs.fau.de>, Sheng Jiang <jiangsheng@huawei.com>
CC: "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "anima@ietf.org" <anima@ietf.org>, "Brian E Carpenter (brian.e.carpenter@gmail.com)" <brian.e.carpenter@gmail.com>
Thread-Topic: [Anima] ANIMA: Reminder: Re: Call for agenda ANIMA @ IETF 108, online
Thread-Index: AdZWjt52t5MTQcBDTV+EWVYg6H3SigIg8bAAAECFfRA=
Date: Wed, 22 Jul 2020 10:43:47 +0000
Message-ID: <PR3PR07MB6826F89764A22BF2F9950853F3790@PR3PR07MB6826.eurprd07.prod.outlook.com>
References: <12ed9e0beafe415fb3e6df59bb74c85e@huawei.com> <20200721035434.GA5003@faui48f.informatik.uni-erlangen.de>
In-Reply-To: <20200721035434.GA5003@faui48f.informatik.uni-erlangen.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: cs.fau.de; dkim=none (message not signed) header.d=none;cs.fau.de; dmarc=none action=none header.from=nokia.com;
x-originating-ip: [176.130.37.253]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 70061007-1553-4702-316c-08d82e2c1d51
x-ms-traffictypediagnostic: PR3PR07MB6585:
x-microsoft-antispam-prvs: <PR3PR07MB65854308644FA03E524A14D7F3790@PR3PR07MB6585.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:2887;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: kvnggy86AxHmHW8gN6IKxbliaClC6aP23pxJrrRRSQBbnW/kW7kizo17amSy60NSLkHiDJzMFi6aKTzciwV035ecSxejZweyfEpsdHuF3NH55cKkqftwX+o3z6rvx7Q79aLa8AGKmR5B0yqK6sZou9oHHliJZi+rBHazBBrtGiLTriSTcuMiT2k/bSAz4NP6sYg77px6T/qQfmEjtPWkVX8U2kGdIJsq8VQUmXSykjW3QpSa7+DzpKTmgZElEpUJRFoccO4k/8TtjIGEr2wwIIqiLb0i+hM06XyZ8vf2LJ0/+8tBp1EEY7Mr21dfkjQld9wFNmOueSXLpa7yzlpfVYmKTsmRh5eC+ZlRAXDKMrytWbnUFOvervlXNA4xLwMluSgLX1x8jB27UOvtuJW5ng==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:PR3PR07MB6826.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(136003)(39860400002)(376002)(346002)(366004)(396003)(86362001)(2906002)(5660300002)(316002)(33656002)(76116006)(66446008)(66556008)(54906003)(52536014)(478600001)(110136005)(66476007)(26005)(64756008)(186003)(8676002)(53546011)(6506007)(966005)(4326008)(9686003)(7696005)(71200400001)(83380400001)(55016002)(8936002)(66946007); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: 9FDrbYcOnpdRTBevJT+NV9+DrngJEL6CBBOrI+jt0XDn0T289u9kzjIVPrTvwuqWtdJvZIn1DSpPnJhQg6oEo6h5fY9PbYGKw0v3LB8bKQ6TB4QQ4uw4NFkqy/DuB0wAIxs9ZuYph0VTQcSIntlayc0rxs4/xEHxFUqZjpler9zEK4708gxkaFdGRaCLs6q1ekgGxMWZVi5yTxT0cpItL1Z3G0kAkQZ+3rmkaA6s6+m+pPR4SaTmop9SyIFDWiEmqTsArSrwhxnGDKP47G3CKPpt4bHnZMMXWi2FWIrRBkOyDskHn13GBav0mRaWsI3FKngyrKbMKaXmdK/LqoICSxB96YU5TIeTutjM7j8TrNnhGuh3vbKiQAEen+SwzO70pHfpVdt2v67McBw5Zx/a+o0R/SUul+T54fjeuYAhVsqMi52Meesji11H6VAnaijHvXXAQb+DnJ3WL+C7EeeOuE7e2TtNQ1p27G4FVgR3ulDgXtmIsEGTAsxEAWA7WhUR
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: PR3PR07MB6826.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 70061007-1553-4702-316c-08d82e2c1d51
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jul 2020 10:43:47.4221 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: jdxUiiYpq9MmjMKZWsC+tSGap46Ku2r0Br0+NMu3QdPVq4v1suNKNw6njNFE7R2hZ8hyzbjQgYh0Y2pSK16VVSmkx7R0JQ1Nwfg3VHh1SNA=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PR3PR07MB6585
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/TzDXiUtgEt-aPjt-md5hXW_8JaA>
Subject: Re: [Anima] ANIMA: Reminder: Re: Call for agenda ANIMA @ IETF 108, online
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, 22 Jul 2020 10:43:52 -0000

Dear ANIMA WG Chairs,

We'd like to ask for a short slot on draft-carpenter-anima-asa-guidelines.
The main purpose is to present the status of the I-D (no change, stable ver=
sion) and ask for WG document adoption.

Best regards,=20
-Laurent

> -----Original Message-----
> From: Anima <anima-bounces@ietf.org> On Behalf Of Toerless Eckert
> Sent: Tuesday, July 21, 2020 05:55
> To: Sheng Jiang <jiangsheng@huawei.com>
> Cc: anima-chairs@ietf.org; anima@ietf.org
> Subject: [Anima] ANIMA: Reminder: Re: Call for agenda ANIMA @ IETF 108,
> online
>=20
> Reminder. Please bring forward for any agenda items you want to see.!
>=20
> Thanks
>     Toerless
>=20
> On Fri, Jul 10, 2020 at 07:51:34AM +0000, Sheng Jiang wrote:
> > Hi, all anima,
> >
> >
> >
> > We have been allocated a sessions of 1 hour 40 minutes for the ANIMA WG
> meeting for IETF-108 (online). It is on Thursday, July 30, 2020?? 11:00-
> 12:40 (UTC). We are now starting to collect agenda items for the session.
> Please send your request for agenda by July 21th, Tuesday, to anima-
> chairs@ietf.org and both chairs' email. Please note that email to a singl=
e
> chair may cause single-point failure.
> >
> >
> >
> > 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) requests for time slot by Jul=
y
> 21th, Tuesday and include:
> >
> >
> >
> > Name of time slot:
> >
> > Name of draft(s):
> >
> > Time requested:
> >
> > Presenter name(s):
> >
> >
> >
> > More details about the IETF 108 can be found at:
> >
> >
> >
> > https://www.ietf.org/how/meetings/108/
> >
> >
> >
> > 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,
> >
> >
> >
> > Sheng + Toerless
> >
>=20
> --
> ---
> tte@cs.fau.de
>=20
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima


From nobody Wed Jul 22 08:59:31 2020
Return-Path: <noreply@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 6729B3A0978; Wed, 22 Jul 2020 08:59:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-anima-autonomic-control-plane@ietf.org, anima-chairs@ietf.org,  anima@ietf.org, Sheng Jiang <jiangsheng@huawei.com>, jiangsheng@huawei.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.9.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <159543356634.12174.1810847008018096885@ietfa.amsl.com>
Date: Wed, 22 Jul 2020 08:59:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/0r5ifh2g1zVsZfreZTzWixm0gwY>
Subject: [Anima] Benjamin Kaduk's No Record on draft-ietf-anima-autonomic-control-plane-27: (with COMMENT)
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: Wed, 22 Jul 2020 15:59:27 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-anima-autonomic-control-plane-27: No Record

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/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Moving back to No Record as an intermediate state, to note that the
issues in the Discuss position I filed on the -19 have all been resolved.
(My review of the -27 remains in progress.)

Thank you for the extensive efforts you put in to respond to the previous
rounds of feedback!  I especially appreciate that you were able to continue
discussions with Russ and Barry (and others) even when I myself was not
being particularly responsive due to other pressing issues.




From nobody Thu Jul 23 04:53:52 2020
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 F3BB63A07F0; Thu, 23 Jul 2020 04:53:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.118
X-Spam-Level: 
X-Spam-Status: No, score=-1.118 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, 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 TQfgix-ho3t8; Thu, 23 Jul 2020 04:53:48 -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 A427B3A0991; Thu, 23 Jul 2020 04:53:41 -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 617EC5485D2; Thu, 23 Jul 2020 13:53:36 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 596E8440043; Thu, 23 Jul 2020 13:53:36 +0200 (CEST)
Date: Thu, 23 Jul 2020 13:53:36 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Tero Kivinen <kivinen@iki.fi>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, ipsec@ietf.org, anima@ietf.org
Message-ID: <20200723115336.GA30549@faui48f.informatik.uni-erlangen.de>
References: <alpine.LRH.2.22.394.2006191126200.32638@bofh.nohats.ca> <24142.1592760359@localhost> <24309.64229.308771.733097@fireball.acr.fi> <20200626161053.GQ41244@faui48f.informatik.uni-erlangen.de> <24315.37346.143409.46224@fireball.acr.fi> <20200630202812.GF13952@faui48f.informatik.uni-erlangen.de> <24336.33964.354779.953171@fireball.acr.fi> <6871.1595023836@localhost> <24342.51918.664855.708819@fireball.acr.fi> <21070.1595343265@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <21070.1595343265@localhost>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/eTvnaaLgS-Jpnkq3SzjWKGFO5hw>
Subject: [Anima] Tero: Re: [IPsec] Troubleshooting IPsec peer certs (was: Re: IPsec profile feedback wanted (draft autonomic control) plane)
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, 23 Jul 2020 11:53:51 -0000

On Tue, Jul 21, 2020 at 10:54:25AM -0400, Michael Richardson wrote:
>     > Sometimes the problem is that there are devices there which do not
>     > support ECDSA at all, which means you are stuck with RSA for both root
>     > and EE for all devices. With CERTREQ some parts of the network can
>     > start use full ECDSA TA and EE and still interoperate with those
>     > devices which support both and get the "coolness" factor of not using
>     > RSA at all :-)
> 
> I think that we say that we will tolerate RSA :-)
> So you are right: there could be devices which do not do ECDSA on day one,
> and in which case, you can't switch the keys at all.

I don't think this issue applies to ACP because both RSA and ECC / ECDSA
certificates are mandatory. Please check draft-ietf-anima-autonomic-control-plane-27,
section 6.1.1. I hope this should be sufficient, if not, then any text
fixes welcome.

Remember that ACP is not only summetric (no dedicated client/servers), but
also greenfield: aka: no need to think about IN THIS REVISION OF ACP about
legacy compatibility. IF/WHEN in the future we do provide update/extensions
to ACP, THEN we may get into considerations for two generations of nodes
talking to each other.

>     > Other similar cases comes when you merge authorization domains
>     > together, i.e., two companies merge and they both had their own CAs
>     > before, and not all devices support both CAs, so you need to pick
>     > correct certificate one when talking to one or another device.
> 
> Yes, this is an important case.

Right now, draft-ietf-anima-autonomic-control-plane-27 does only specify to still
send a certificate, even if a CERTREQ was received from the peer, and no certificate
would match the TA in the CERTREQ. We discussed how this was for diagnostics.
See section 6.7.3.1.2.

There is nothing in the current ACP text to say whether or not to send CERTREQ
right now. Given how the ACP just provides a refinement profile in section
6.7.3.1.2. on top of RFC8247, and given how RFC8247 does not mention CERTREQ,
that leaves is with a "MAY send CERTREQ" (i paraphrase) from RFC7296 section
3.8.

The domain merge is also of interest in ACP, so we could add a stronger
requirement against CERTREQ, but given how the documents we reference
(RFC8247/RFC7296), i am a bit suspicious about doing so. If CERTREQ is
so useful in non-ACP use caes, why is there no stronger than MAY in RFC7296
or RFC8247 ? Oversight in those IKEv2 RFCs ? Or are there some downsides
coming with it ?

I don't think i will add suc a requirement in this ACP spec because it
may be necessary to make the merge case work, but it is not sufficient,
and the set of components sufficient to support that use case is is
beyond the scope of this ACP base spec.

To give a hint: We only mandate use of EST, and if i wanted to support
a merge, or in general any use case where CERTREQ was useful, then i would
need to have nodes that would have two or more certs and CERTREQ is a
way to pick one of those multiple certs. And EST to the best of my
understandig does not allow to hand out more than one cert to a single
node. At least thats what i remember from having asked the quesrtion a few
times over the last 5 years.

We can still make merge work through extension documents, even without
fixing that EST limitation itself through other extensions of ACP, but
i think we would want a discuss first whether to rater do that or fix EST.

Or someone comes around and tells me this time that EST can be somehow
tricked to provide multiple certs to a single node.

>     >> So, we've been forced to use otherName, and this will cause new code in some
>     >> of the IKEv2 daemon that we need to use :-(
> 
>     > No, you are not forced to use anything. Your ID could be KEY_ID with
> 
> No, the ACP document has been forced to use otherName in it's
> certificates. That's nothing to do with IPsec/IKEv2.
> But, that that's what IKEv2 will have to deal with.

Actually, the ACP text currently says to use ID_IPV6_ADDR, but given how
the name of the ACP node is now an otherName, we _could_ signal it
via ID_DER_ASN1_GN, but IMHO ID_IPV6_ADDR is better.

Cheers
    Toerless

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



> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec


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


From nobody Thu Jul 23 05:13:21 2020
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 2F3A13A09E9; Thu, 23 Jul 2020 05:13:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.118
X-Spam-Level: 
X-Spam-Status: No, score=-1.118 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, 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 uwGgr3Y8IwlX; Thu, 23 Jul 2020 05:13:12 -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 B23763A09E4; Thu, 23 Jul 2020 05:13:11 -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 A580B548442; Thu, 23 Jul 2020 14:13:06 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 9EDB4440043; Thu, 23 Jul 2020 14:13:06 +0200 (CEST)
Date: Thu, 23 Jul 2020 14:13:06 +0200
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, anima-chairs@ietf.org, anima@ietf.org, Sheng Jiang <jiangsheng@huawei.com>
Message-ID: <20200723121306.GB30549@faui48f.informatik.uni-erlangen.de>
References: <159543356634.12174.1810847008018096885@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <159543356634.12174.1810847008018096885@ietfa.amsl.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/ms4zTcHfqIc8HOf_PUKbrxx9TPk>
Subject: Re: [Anima] Benjamin Kaduk's No Record on draft-ietf-anima-autonomic-control-plane-27: (with 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: Thu, 23 Jul 2020 12:13:14 -0000

Thanks, Ben

If another run should have you find other issues, just
remember that proposed text to fix the issue is always he best way forward
at this stage.

Cheers
    Toerless

On Wed, Jul 22, 2020 at 08:59:26AM -0700, Benjamin Kaduk via Datatracker wrote:
> Benjamin Kaduk has entered the following ballot position for
> draft-ietf-anima-autonomic-control-plane-27: No Record
> 
> 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/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Moving back to No Record as an intermediate state, to note that the
> issues in the Discuss position I filed on the -19 have all been resolved.
> (My review of the -27 remains in progress.)
> 
> Thank you for the extensive efforts you put in to respond to the previous
> rounds of feedback!  I especially appreciate that you were able to continue
> discussions with Russ and Barry (and others) even when I myself was not
> being particularly responsive due to other pressing issues.
> 
> 

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


From nobody Thu Jul 23 20:46:33 2020
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 84F183A09A9 for <anima@ietfa.amsl.com>; Thu, 23 Jul 2020 20:46:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 RCeDU_CqzrNh for <anima@ietfa.amsl.com>; Thu, 23 Jul 2020 20:46:29 -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 8838D3A09A3 for <anima@ietf.org>; Thu, 23 Jul 2020 20:46:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 87EF0389F7; Thu, 23 Jul 2020 23:26:00 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id PzjOh6ixDQgU; Thu, 23 Jul 2020 23:25:59 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7386D389E0; Thu, 23 Jul 2020 23:25:59 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 08B679A; Thu, 23 Jul 2020 23:46:27 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Brockhaus\, Hendrik" <hendrik.brockhaus@siemens.com>, "anima\@ietf.org" <anima@ietf.org>, "steffen.fries\@siemens.com" <steffen.fries@siemens.com>, max pritikin <pritikin@cisco.com>, Eliot Lear <lear@cisco.com>
In-Reply-To: <AM0PR10MB3153F5AA4119DBDDB97F6D06FE790@AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM>
References: <4a3b24b3737f4dcbbf3154c89d9c8200@siemens.com> <17250.1594397451@localhost> <a26f70c7dc5145b581f71ece3106529b@siemens.com> <26733.1595375481@localhost> <AM0PR10MB3153F5AA4119DBDDB97F6D06FE790@AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512; protocol="application/pgp-signature"
Date: Thu, 23 Jul 2020 23:46:27 -0400
Message-ID: <6971.1595562387@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/DxVSOIfUBs6-T_l9C9E3R-kYwR0>
Subject: Re: [Anima] last minute changes to BRSKI to do endpoint discovery
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, 24 Jul 2020 03:46:32 -0000

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


Brockhaus, Hendrik <hendrik.brockhaus@siemens.com> wrote:
    >> The thread ending at
    >> https://mailarchive.ietf.org/arch/msg/anima/MQkNXJJjMkP0nqKlNEaxDZ94RgI
    >> alludes to this, but the current -03 document does not include this proposal,
    >> because it would need to go into BRSKI itself.

    > I would appreciate to use /.well-known/brski for the endpoints
    > specified in BRSKI and use /.well-known/est for those specified in
    > RFC7030.
    > This offers more flexibility for future extensions like BSKI-AE.

Such a change would be large to BRSKI.

Brian suggests making this an update.
But, I think it would cause market confusion if we published an RFC with
/.well-known/est/requestvoucher, and then said, "no sorry, no we meant
/.well-known/brski/requestvoucher"

Would there be pledge implementations that would try one and then the other?
I will say that I'm *NOT* keen on including the Resource Link GET, but I can
tolerate it.


I think that we'd need to:
  1) blessing of our AD.
  2) pull document out of RFC-editor queue.
  3) revise it, do a WGLC on revision.
  4) get AD to put it back in queue.

The ROLL WG did this for a document last year when we realized that a new
document obsoleted some of the recommendations.  It took longer than planned,
but that was partly because the other document had to settle a bit.
I think we could do this in the time for the 2nd WGLC and about four days.



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




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

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

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl8aWZIACgkQgItw+93Q
3WWfQgf+J8fKdDjYcbv6Cx9PRMYDeJu0GBoI+c4XME/TiXx/g/2ug97C1y4byP5u
fxE+JDsFV90jupOpp7mvER3jCTyUSzTVGF6p1tpZ77+/niHDOOdMsOupuxAlwfF8
dgVdDochbqNI1lVbrXKXKvAbUrcI91fESqB7viEKd/sbKiLLG+u9FlzV31XgNSbR
Jl5qrzRf8UPjI6OfY6X8JyThdxSeZLg48bVx8YBT5BtBEX3aGhKRS6XLDRR6wzki
MtvGv5mJ5VhvVkEMDTdfnxbTqqszWUsyjsq1xMjUJEkh9qvem5FuFDGN74shFPvF
G5EXD1lTSzDUjtPxBut/x4CUC2vVNA==
=ppqX
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sat Jul 25 21:53:49 2020
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 897193A0AE4 for <anima@ietfa.amsl.com>; Sat, 25 Jul 2020 21:53:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, 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 aauRHL6hwZpC for <anima@ietfa.amsl.com>; Sat, 25 Jul 2020 21:53:45 -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 E9EB03A0AE2 for <anima@ietf.org>; Sat, 25 Jul 2020 21:53:44 -0700 (PDT)
Received: by mail-pl1-x62d.google.com with SMTP id b9so6459934plx.6 for <anima@ietf.org>; Sat, 25 Jul 2020 21:53:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:references:to:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=fKn5BEz9ojHeZ98AoUCSiil3/rtBHjUKH+QAjC0JPA8=; b=BkffBvcWlzUnljmcXdfrivjq/iVI0Fa/qIxZKeCPDBVO5ZpUMdZ358O3nIh4otQXk/ S6SCKAeFNm1TlhZFzHT0HRXdzJnBSolcA1tir2RTiLhjCcE213lxl7h20DTuHb13+ZAW 848VMNfyQSVTd0nxAM/2s7apHLsCCmZZdHD1yXY5qUrF/th2oVzHSNw25YkItOQVgwnL p5bSMCkdmmpsbF9PUEh2We2Pf5FKn8JvZZ/SYoyMoBbakX5+sfusli4DtInn3ygfnS13 f/hAcNyheDM6+MWUqJyQbUPzDXDYUutcxs0vusNRVzPFsSjD6hs1S3RViaC0MV72UU0d QnsA==
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:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=fKn5BEz9ojHeZ98AoUCSiil3/rtBHjUKH+QAjC0JPA8=; b=Qh1XK5hgjrxO0T8YYYeWKz8yjwfi4/3lyRzUSkDOMjdTIwJDMxuKqQej1LQMhUABUh fzoGsahWyqvyJHCD2meZXmNyP3sagM2EreLZ3d209Sfmo4br7LqxnTH/fhRzKKKwrr+i 3lGHOvD/Jf7q3ccPe+jeu3OjoyVxWxS5TeUGfMyjuDYroqSKBUKfMd3fCjDGHyeORsHG /5JLEcnieCgod0nnezddQyu2pniIOCCS0gqBucfOhsjqUEhC8KbfA/WbmvMPPPPMQ/wH 8xHFM0iF2aEpmKjB/6xqrQZn2xXvRCD/Eel7PICGO1BzSWl3XrvwHp0znlnGye7WpnHt orMw==
X-Gm-Message-State: AOAM531H/zTc2RTIIXC6EvZNPFhQuwe6a+hy+5E0KT9a/tbWFf8fgAIp HJ3Bsj+aSyvVuE7MjbeWBTsZRaT9
X-Google-Smtp-Source: ABdhPJzoqq/rlanjO2iTXAqF6HeWWYKdaz0g6GOpi6nRpr8FJJceLl+/rV6haexMwyuACWPujRSH1Q==
X-Received: by 2002:a17:902:ea8c:: with SMTP id x12mr789962plb.60.1595739224139;  Sat, 25 Jul 2020 21:53:44 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.139.192]) by smtp.gmail.com with ESMTPSA id q7sm11158773pfn.23.2020.07.25.21.53.42 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 25 Jul 2020 21:53:43 -0700 (PDT)
References: <159573875486.18377.8979475359746431653@ietfa.amsl.com>
To: Anima WG <anima@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Forwarded-Message-Id: <159573875486.18377.8979475359746431653@ietfa.amsl.com>
Message-ID: <9beb2b46-8a08-1d45-1f1b-3bd50283fe20@gmail.com>
Date: Sun, 26 Jul 2020 16:53:39 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <159573875486.18377.8979475359746431653@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/EhU01AQkN2tlVdU-vTwoklxRxEI>
Subject: [Anima] Fwd: I-D Action: draft-carpenter-anima-asa-guidelines-09.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, 26 Jul 2020 04:53:47 -0000

This is a minor update - a few extra words on authorization of ASAs,
and editorial fixes.

   Brian + co-authors

-------- Forwarded Message --------
Subject: I-D Action: draft-carpenter-anima-asa-guidelines-09.txt
Date: Sat, 25 Jul 2020 21:45:54 -0700
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           : Guidelines for Autonomic Service Agents
        Authors         : Brian Carpenter
                          Laurent Ciavaglia
                          Sheng Jiang
                          Pierre Peloso
	Filename        : draft-carpenter-anima-asa-guidelines-09.txt
	Pages           : 26
	Date            : 2020-07-25

Abstract:
   This document proposes guidelines for the design of Autonomic Service
   Agents for autonomic networks, as a contribution to describing an
   autonomic ecosystem.  It is based on the Autonomic Network
   Infrastructure outlined in the ANIMA reference model, using the
   Autonomic Control Plane and the Generic Autonomic Signaling Protocol.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-carpenter-anima-asa-guidelines/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-carpenter-anima-asa-guidelines-09
https://datatracker.ietf.org/doc/html/draft-carpenter-anima-asa-guidelines-09

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-carpenter-anima-asa-guidelines-09


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 Sun Jul 26 14:11:32 2020
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 50A6E3A148B; Sun, 26 Jul 2020 14:11:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 QqbbWxTfy5Gg; Sun, 26 Jul 2020 14:11:29 -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 A9D8A3A1489; Sun, 26 Jul 2020 14:11:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 00B5638A5C; Sun, 26 Jul 2020 16:50:57 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id EDBP3VnBxzrF; Sun, 26 Jul 2020 16:50:55 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id EDE3638A5A; Sun, 26 Jul 2020 16:50:54 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 03C691AA; Sun, 26 Jul 2020 17:11:25 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Sheng Jiang <jiangsheng@huawei.com>
cc: "anima@ietf.org" <anima@ietf.org>, "Owen Friel (ofriel)" <ofriel@cisco.com>, "anima-chairs@ietf.org" <anima-chairs@ietf.org>, Toerless Eckert <tte@cs.fau.de>
In-Reply-To: <12ed9e0beafe415fb3e6df59bb74c85e@huawei.com>
References: <12ed9e0beafe415fb3e6df59bb74c85e@huawei.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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: text/plain; charset="us-ascii"
Content-ID: <23189.1595797884.1@localhost>
Date: Sun, 26 Jul 2020 17:11:24 -0400
Message-ID: <23191.1595797884@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/yRxuzxLKKuLDRlrZCjsi9s_LVMk>
Subject: Re: [Anima] Call for agenda ANIMA @ IETF 108, online
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, 26 Jul 2020 21:11:31 -0000

Name of time slot:      brski-cloud
Name of draft(s):       draft-friel-anima-brski-cloud-02
Time requested:         10min
Presenter name(s):      Michael Richardson


From nobody Sun Jul 26 14:14:03 2020
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 6D0643A1492; Sun, 26 Jul 2020 14:13:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 QvO1BiNhHxqu; Sun, 26 Jul 2020 14:13:58 -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 02E623A1491; Sun, 26 Jul 2020 14:13:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id F15A338A5C; Sun, 26 Jul 2020 16:53:25 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 94G2RG1u4ViM; Sun, 26 Jul 2020 16:53:25 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 23CD038A5A; Sun, 26 Jul 2020 16:53:25 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 2E2A81AA; Sun, 26 Jul 2020 17:13:55 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Sheng Jiang <jiangsheng@huawei.com>
cc: "anima@ietf.org" <anima@ietf.org>, "anima-chairs@ietf.org" <anima-chairs@ietf.org>, Toerless Eckert <tte@cs.fau.de>
In-Reply-To: <12ed9e0beafe415fb3e6df59bb74c85e@huawei.com>
References: <12ed9e0beafe415fb3e6df59bb74c85e@huawei.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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: text/plain; charset="us-ascii"
Content-ID: <23726.1595798035.1@localhost>
Date: Sun, 26 Jul 2020 17:13:55 -0400
Message-ID: <23727.1595798035@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/_9d05eIKSnHYi1HtLsEPuWia2SM>
Subject: Re: [Anima] Call for agenda ANIMA @ IETF 108, online
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, 26 Jul 2020 21:14:00 -0000

Name of time slot:      *-considerations document structure
Name of draft(s):       draft-richardson-anima-masa-considerations,
                        draft-richardson-anima-registrar-considerations,
                        draft-richardson-secdispatch-idevid-considerations
Time requested:         7 min
Presenter name(s):      Michael Richardson

Please note that there is a conflict with secdispatch, so I need to be after
the first 30min.



From nobody Sun Jul 26 14:34:01 2020
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 16E723A149B for <anima@ietfa.amsl.com>; Sun, 26 Jul 2020 14:33:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 PnB89RfrFAEK for <anima@ietfa.amsl.com>; Sun, 26 Jul 2020 14:33:57 -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 635A93A1495 for <anima@ietf.org>; Sun, 26 Jul 2020 14:33:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id A86D138A5C; Sun, 26 Jul 2020 17:13:25 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id mNmKzTpXW-Ch; Sun, 26 Jul 2020 17:13:25 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 2B31738A5A; Sun, 26 Jul 2020 17:13:25 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 38E3C1AA; Sun, 26 Jul 2020 17:33:55 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
to: "Brockhaus\, Hendrik" <hendrik.brockhaus@siemens.com>, "anima\@ietf.org" <anima@ietf.org>
In-Reply-To: <6971.1595562387@localhost>
References: <4a3b24b3737f4dcbbf3154c89d9c8200@siemens.com> <17250.1594397451@localhost> <a26f70c7dc5145b581f71ece3106529b@siemens.com> <26733.1595375481@localhost> <AM0PR10MB3153F5AA4119DBDDB97F6D06FE790@AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM> <6971.1595562387@localhost>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512; protocol="application/pgp-signature"
Date: Sun, 26 Jul 2020 17:33:55 -0400
Message-ID: <28226.1595799235@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/IezsflZqYdJi0O_vHRHfcnCbY_o>
Subject: Re: [Anima] last minute changes to BRSKI to do endpoint discovery
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, 26 Jul 2020 21:33:59 -0000

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


Would BRSKI-AE want to do CoAPS instead of HTTPS?
Or in addition to HTTPS?

I propose to leave base HTTPS BRSKI as-is, and then do whatever renames you
like by merging BRSKI-AE into constrained-voucher, and all all of the
asynchronous efforts over CoAP.

This has the interesting possibilities of supporting BRSKI-AE CoAP over BTLE,
NFC, and SMS. (not necessarily with an IP layer)

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




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

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

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl8d9sIACgkQgItw+93Q
3WWMfwf/VINaSzUvJYzB+d/xWgHtRyKmVioc9vec0EobWjkoR643eKdyqb65rCCg
maq4IrG2RKk5RXnNghHxGNPTzhOsoYXvJnx1nYOIEjelLD8CIcU64ZQ9evXWoOG4
+Z28kEiUVTHminSG8gDWY8oi526foYPNMJCmb7RmWIPRzeI/azMn2VV8iq0QEqBQ
PW318fqnYMlMAZz4TaGQzbdqc4wC2dcets4ZrMnFnZY3MZV9PEaZRwQEVRBdYtdH
dV2SSkFCTBAI5T4e4QTPLF2tn8rFf3VaDMLuw479o5wzmbT3G5n9aSNK2uvoGa3e
WdTlk6X824GztUZbMcHfAABgQah3uw==
=PQUr
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Jul 26 15:19:59 2020
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 707A23A0898 for <anima@ietfa.amsl.com>; Sun, 26 Jul 2020 15:19:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Level: 
X-Spam-Status: No, score=-2.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, 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 DWCh4se8dfBp for <anima@ietfa.amsl.com>; Sun, 26 Jul 2020 15:19:46 -0700 (PDT)
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 7C0703A0B22 for <anima@ietf.org>; Sun, 26 Jul 2020 15:19:45 -0700 (PDT)
Received: by mail-pg1-x52b.google.com with SMTP id g67so8306224pgc.8 for <anima@ietf.org>; Sun, 26 Jul 2020 15:19:45 -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=En9DkVb1JRwLfpObWSZaoCJdRM4YcpvZF2oN5X/9Y/g=; b=jxs4l5Gj6Klj12IOx1DrHvNfzvW9Jpc0TU4+4ykoK9RH93JAfkfGfKfpAAlaxoV3HJ 2crj64sd/jKAm6hB3jYsaPiVCs75fNK+VxRKAQLpQN7bSliHa05KIQfASB9LgilHRdOf 0Vi1TxC1DqvtWG5YgW37RMJUp+NrfoIwU2bIDFiHP8AeTo3cx7UR71DRVQaRs1nEgmQg QrIdL579AwTtjTEFjaT5AutA2PpFAnMF1xGYzpJrT/OVb2Dg6d8umKvJO/Qz9vmhf0vY erOHf4ATjrPQna8iGcmU/zAu3OfAn85hm/qS5gz+ctCfA7XgUkL6dbXs8T5SuEu2e9OL J5UQ==
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=En9DkVb1JRwLfpObWSZaoCJdRM4YcpvZF2oN5X/9Y/g=; b=Vu0Ibb/Ey+MtGLkBZXDEhb1AOKsk6LVWFh9GEPP5XYrdb5hfoW43fgJv7XfUWUdhom 9M2UIHG/s9rDT+fzc1a1isqQgB1lXg8CnvTe1JWlQqUnd+MpUo77EbrLHDabiXl9GzEB l7cF4lhoM31g50nREbHJXqmSluo5zl/JFYeuRlwpYdE98KCqa77fAkgqbkrJq8Ipkba7 MYtACiQAd9En9iQ6tzxpSvs2LNwnGxR8W08GCCT4gp2E0eCmD6brx3Q2Sk+yAIaxZR2x CjBArzmO76r2Vvdd8mbTMPjYL43zpY0QQy6Teb1ccuttauDY06zSdeKNJ2tcx9x5AJ1s s9Dg==
X-Gm-Message-State: AOAM5303/3Wn+MV+cnLCGg6fkQYUC8OHL6HIjGzrdKSY2AXey+KJgDPf 1igXaHYsReq/VLj8wKJV15SoWPly
X-Google-Smtp-Source: ABdhPJxQKJyb+rPuH/sNttjJJhio9tK+/LbGFbWGlDWTt7CGhOMz4rw2BlaIDXBqC8daum1VDUo+nA==
X-Received: by 2002:aa7:8e90:: with SMTP id a16mr17081240pfr.84.1595801984729;  Sun, 26 Jul 2020 15:19:44 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.139.192]) by smtp.gmail.com with ESMTPSA id gn5sm11827802pjb.23.2020.07.26.15.19.43 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 26 Jul 2020 15:19:44 -0700 (PDT)
To: anima@ietf.org
References: <4a3b24b3737f4dcbbf3154c89d9c8200@siemens.com> <17250.1594397451@localhost> <a26f70c7dc5145b581f71ece3106529b@siemens.com> <26733.1595375481@localhost> <AM0PR10MB3153F5AA4119DBDDB97F6D06FE790@AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM> <6971.1595562387@localhost> <28226.1595799235@localhost>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <dffda67d-42c5-bf86-e395-504f400c0293@gmail.com>
Date: Mon, 27 Jul 2020 10:19:41 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <28226.1595799235@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/snt1Kb-IZ8AugnaxZ_nV6XjcKts>
Subject: Re: [Anima] last minute changes to BRSKI to do endpoint discovery
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, 26 Jul 2020 22:19:50 -0000

Yes. It's important to make extensions but only after freezing the base
RFCs. 

Regards
   Brian Carpenter

On 27-Jul-20 09:33, Michael Richardson wrote:
> 
> Would BRSKI-AE want to do CoAPS instead of HTTPS?
> Or in addition to HTTPS?
> 
> I propose to leave base HTTPS BRSKI as-is, and then do whatever renames you
> like by merging BRSKI-AE into constrained-voucher, and all all of the
> asynchronous efforts over CoAP.
> 
> This has the interesting possibilities of supporting BRSKI-AE CoAP over BTLE,
> NFC, and SMS. (not necessarily with an IP layer)
> 
> --
> 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 Sun Jul 26 18:50:49 2020
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 606063A15DD for <anima@ietfa.amsl.com>; Sun, 26 Jul 2020 18:50:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 Q-Fivr-GsLhL for <anima@ietfa.amsl.com>; Sun, 26 Jul 2020 18:50:43 -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 366273A15DC for <anima@ietf.org>; Sun, 26 Jul 2020 18:50:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 513F838A62 for <anima@ietf.org>; Sun, 26 Jul 2020 21:30:11 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 3SY70n4jBJDu for <anima@ietf.org>; Sun, 26 Jul 2020 21:30:10 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 08EA438A61 for <anima@ietf.org>; Sun, 26 Jul 2020 21:30:10 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 22C571AA for <anima@ietf.org>; Sun, 26 Jul 2020 21:50:40 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
In-Reply-To: <159580250482.3724.5712671711646203180@ietfa.amsl.com>
References: <159580250482.3724.5712671711646203180@ietfa.amsl.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512; protocol="application/pgp-signature"
Date: Sun, 26 Jul 2020 21:50:40 -0400
Message-ID: <28284.1595814640@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/wDR6Snfrifo_aRK8hjwxP0FIMks>
Subject: [Anima] draft-richardson-anima-l2-friendly-acp-00
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, 27 Jul 2020 01:50:46 -0000

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


internet-drafts@ietf.org wrote:
    > Name:		draft-richardson-anima-l2-friendly-acp
    > Title:		Autonomic Control Plane challenges for Layer-Two Switched Networks
    > Status:         https://datatracker.ietf.org/doc/draft-richardson-anima-l2-friendly-acp/

    > Abstract:
    > This document details the challenges with building an Autonomic
    > Control Plane on Campus/Enterprise networks which are built out of
    > layer-two (Ethernet) switched technologies.

    > This document does not propose a specific solution as yet, but
    > details a number of possibilities, and what it would take to
    > standardize each possibility.

Hi, I have marked this document as replacing the previous document, richardson-anima-ipv6-lldp.
This document is now more of a requirements discussion.

Joel Halpern has pointed just now in email that it appears to be work that
the IEEE should do.  He may be right.  In which case, this may be a
requirements document to send through a liason.

On the other hand, this is basically an IPv6-over-FOO document, and we have
historically done those.

At this point, please take section 4 (Possibilities) as open thoughts.

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

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

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

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl8eMu8ACgkQgItw+93Q
3WVuWQf+P0wi7Zz7eb3WnRTF7mszGp6+R9bYEyowXBSBcaDVJNpxBWFe8YQfW73y
+XGm6t48i2rXnMAo82gP7tbVrCQNJfZMM6fxp17d1MASt02Z3aRlFHUt91P/v2pR
nF5lcGjlLl9oCy0eJSrFLt7khPgn1iPiDWjjzQXNPzECqXAEIqDO6Q0bx1rIpEoN
lz0iCKqb5kKgzqak4z9A/+jvQOjWAxV2X3ppfFOXnk9O+NvGULJ2YPTrcDzIfe4h
Z9HH1Tj2RY+on5xOmQS8rnuzJ8eXXQPxWuiIe7sQrLfQ/pSXqiH/XHq/3z/X7inI
vyvrLVxc0GYsNNJyKgY4Uoq/oAM6AQ==
=K7vI
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Jul 26 22:41:41 2020
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 950753A16E6 for <anima@ietfa.amsl.com>; Sun, 26 Jul 2020 22:41:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 gIAo_4CjKvcl for <anima@ietfa.amsl.com>; Sun, 26 Jul 2020 22:41:37 -0700 (PDT)
Received: from gw-eagle2.siemens.com (gw-eagle2.siemens.com [194.138.20.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DAE83A16E4 for <anima@ietf.org>; Sun, 26 Jul 2020 22:41:37 -0700 (PDT)
Received: from mail1.dc4ca.siemens.de (mail1.dc4ca.siemens.de [139.25.224.78]) by gw-eagle2.siemens.com (Postfix) with ESMTPS id B020946800B; Mon, 27 Jul 2020 07:41:34 +0200 (CEST)
Received: from DEMCHDC8A0A.ad011.siemens.net (demchdc8a0a.ad011.siemens.net [139.25.226.106]) by mail1.dc4ca.siemens.de (Postfix) with ESMTPS id 467CD15C6636F; Mon, 27 Jul 2020 07:41:33 +0200 (CEST)
Received: from DEMCHDC8A1A.ad011.siemens.net (139.25.226.107) by DEMCHDC8A0A.ad011.siemens.net (139.25.226.106) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Mon, 27 Jul 2020 07:41:33 +0200
Received: from DEMCHDC8A1A.ad011.siemens.net ([139.25.226.107]) by DEMCHDC8A1A.ad011.siemens.net ([139.25.226.107]) with mapi id 15.01.1979.003;  Mon, 27 Jul 2020 07:41:33 +0200
From: "Fries, Steffen" <steffen.fries@siemens.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>, "anima@ietf.org" <anima@ietf.org>, "max pritikin" <pritikin@cisco.com>, Eliot Lear <lear@cisco.com>
Thread-Topic: AW: last minute changes to BRSKI to do endpoint discovery
Thread-Index: AQHWX7nZAFTFfGkZ50WeAMpw9tqZsKkTGwkAgALeAICABPcmQA==
Date: Mon, 27 Jul 2020 05:41:33 +0000
Message-ID: <4b900e875bea48e685d430dac3af74c8@siemens.com>
References: <4a3b24b3737f4dcbbf3154c89d9c8200@siemens.com> <17250.1594397451@localhost> <a26f70c7dc5145b581f71ece3106529b@siemens.com> <26733.1595375481@localhost> <AM0PR10MB3153F5AA4119DBDDB97F6D06FE790@AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM> <6971.1595562387@localhost>
In-Reply-To: <6971.1595562387@localhost>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [144.145.220.66]
x-tm-snts-smtp: A6FFAC3F26B48943EFD7A70B05461D7F8F36EBAC626EE07AD93E7D60B0D078CA2000:8
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/rtyvH8y_msGI7j-T9gE7SUFDupM>
Subject: Re: [Anima] last minute changes to BRSKI to do endpoint discovery
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, 27 Jul 2020 05:41:40 -0000

Hi Michael,

> From: Michael Richardson <mcr+ietf@sandelman.ca>
>     > I would appreciate to use /.well-known/brski for the endpoints
>     > specified in BRSKI and use /.well-known/est for those specified in
>     > RFC7030.
>     > This offers more flexibility for future extensions like BSKI-AE.
>=20
> Such a change would be large to BRSKI.
>=20
> Brian suggests making this an update.
> But, I think it would cause market confusion if we published an RFC with
> /.well-known/est/requestvoucher, and then said, "no sorry, no we meant
> /.well-known/brski/requestvoucher"
>=20
> Would there be pledge implementations that would try one and then the
> other?
> I will say that I'm *NOT* keen on including the Resource Link GET, but I =
can
> tolerate it.
The intention was not to include the discovery mechanism right away into BR=
SKI. It was rather the question to rename the BRSKI defined endpoints to /.=
well-known/brski to underline, that the voucher exchange is independent fro=
m the chosen enrollment protocol. The discovery should be done in BRSKI-AE,=
 which should update the base specification then. I understand, that we sho=
uld not state /.well-known/est and the immediately update it afterwards to =
/.well-known/brski . That would look awkward. If we just rename the endpoin=
ts in BRSKI, would that cause such a large change?=20

Best regards
Steffen


>=20
>=20
> I think that we'd need to:
>   1) blessing of our AD.
>   2) pull document out of RFC-editor queue.
>   3) revise it, do a WGLC on revision.
>   4) get AD to put it back in queue.
>=20
> The ROLL WG did this for a document last year when we realized that a new
> document obsoleted some of the recommendations.  It took longer than
> planned, but that was partly because the other document had to settle a b=
it.
> I think we could do this in the time for the 2nd WGLC and about four days=
.
>=20
>=20
>=20
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -=3D IPv6 IoT consulting =3D-
>=20
>=20


From nobody Mon Jul 27 13:26:54 2020
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 AB0513A0985 for <anima@ietfa.amsl.com>; Mon, 27 Jul 2020 13:26:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, 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 jGxRH_gSs-Ol for <anima@ietfa.amsl.com>; Mon, 27 Jul 2020 13:26:50 -0700 (PDT)
Received: from mail-pg1-x543.google.com (mail-pg1-x543.google.com [IPv6:2607:f8b0:4864:20::543]) (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 451853A098E for <anima@ietf.org>; Mon, 27 Jul 2020 13:26:50 -0700 (PDT)
Received: by mail-pg1-x543.google.com with SMTP id t6so10585704pgq.1 for <anima@ietf.org>; Mon, 27 Jul 2020 13:26:50 -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=Poz1xo7nnmy5+p3mvLIT0/qlolNc4uwFZisfHgTrJw8=; b=f7+xvjaWPcoZaaOGo7RoWI8e7jU5tcIqI83MAHnW/HTwcbnX7sxz/zFhuefHIuYgBy eNZ0tglAr93XJKG7OWuFXrHrjQ3zy5MVDSYS6ccBUFxmN8QsRTj5dXn5EFce1IPTtOvl jr7xbgSa4K6JBhVYgXcOgajMNUq28DuBCO7ve3DTrJbrgAMCYFf4aTNDSdFIM0xozb+n +84pr2fLlRXZYL/tXT4b6g3kCPCVDBBKdF6smOS2aD8cqeZV1YecJwVW3cHSMMwG9yEO +ywD1bkGe+Z+YqVpU68odtmIFkP8VoXBF8ROGOuC+h6g4n+sCjazD7iGm1ZW6pat1HmE mNOA==
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=Poz1xo7nnmy5+p3mvLIT0/qlolNc4uwFZisfHgTrJw8=; b=g2pJcdnRssiqqV9jjq6mYIHoh0wUMeUuJj3tXNFG0St8DN2plU/gLx35A8no+JOt/c brcOKRA05v2wt7dLEtUoUcFROXn1GLX+dCPCcRTMKVcf/WFTsU16m4Iujuo6aZN3CUQY kUJuepZOAA0ZKluQADlkzkpalhvZYFMSD4zsk/cTJUjX2Yw1RKAYXbKCt2BJ+m+uA9UA K2AX/eeoREGwmUK9uz/5Vb0gILepU1ozPsAivATuQWaVk2cGUfXPLh6q5hDwx0s996Ce WQkoW6DNjAysKgrv/8nEuuQah6iMD0JbXCX52k9U/TMCgpVGwuZBcNZJToNA+6YNfve9 rvIQ==
X-Gm-Message-State: AOAM5317GRo6cv1YRSzPLEMLts6jhBcCFOfWWpFd1czCWRLPz+XMiyBm Ckef8UM5+V6dv8ElFGlyZTA=
X-Google-Smtp-Source: ABdhPJxZXEzwBLyiu4iTg3O9Vrbbm8oBM/Nwt9mO17KERYCYiis5grGtK0wP4kF6p5T1fOWF3C+XLw==
X-Received: by 2002:a63:9201:: with SMTP id o1mr19130486pgd.99.1595881609745;  Mon, 27 Jul 2020 13:26:49 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.139.192]) by smtp.gmail.com with ESMTPSA id d37sm15876859pgd.18.2020.07.27.13.26.46 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Jul 2020 13:26:48 -0700 (PDT)
To: "Fries, Steffen" <steffen.fries@siemens.com>, Michael Richardson <mcr+ietf@sandelman.ca>, "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>, "anima@ietf.org" <anima@ietf.org>, max pritikin <pritikin@cisco.com>, Eliot Lear <lear@cisco.com>
References: <4a3b24b3737f4dcbbf3154c89d9c8200@siemens.com> <17250.1594397451@localhost> <a26f70c7dc5145b581f71ece3106529b@siemens.com> <26733.1595375481@localhost> <AM0PR10MB3153F5AA4119DBDDB97F6D06FE790@AM0PR10MB3153.EURPRD10.PROD.OUTLOOK.COM> <6971.1595562387@localhost> <4b900e875bea48e685d430dac3af74c8@siemens.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <173a8001-bee3-4a88-1289-d80ea35cde40@gmail.com>
Date: Tue, 28 Jul 2020 08:26:45 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <4b900e875bea48e685d430dac3af74c8@siemens.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/0N0bytWbzYpPsY0Qezg-7TvkDsE>
Subject: Re: [Anima] last minute changes to BRSKI to do endpoint discovery
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, 27 Jul 2020 20:26:53 -0000

On 27-Jul-20 17:41, Fries, Steffen wrote:
> Hi Michael,
> 
>> From: Michael Richardson <mcr+ietf@sandelman.ca>
>>     > I would appreciate to use /.well-known/brski for the endpoints
>>     > specified in BRSKI and use /.well-known/est for those specified in
>>     > RFC7030.
>>     > This offers more flexibility for future extensions like BSKI-AE.
>>
>> Such a change would be large to BRSKI.
>>
>> Brian suggests making this an update.
>> But, I think it would cause market confusion if we published an RFC with
>> /.well-known/est/requestvoucher, and then said, "no sorry, no we meant
>> /.well-known/brski/requestvoucher"

I meant that the update would say
"please *add* /.well-known/brski/requestvoucher"

An extension, not an amendment (draft-kuehlewind-update-tag).

   Brian

>>
>> Would there be pledge implementations that would try one and then the
>> other?
>> I will say that I'm *NOT* keen on including the Resource Link GET, but I can
>> tolerate it.
> The intention was not to include the discovery mechanism right away into BRSKI. It was rather the question to rename the BRSKI defined endpoints to /.well-known/brski to underline, that the voucher exchange is independent from the chosen enrollment protocol. The discovery should be done in BRSKI-AE, which should update the base specification then. I understand, that we should not state /.well-known/est and the immediately update it afterwards to /.well-known/brski . That would look awkward. If we just rename the endpoints in BRSKI, would that cause such a large change? 
> 
> Best regards
> Steffen
> 
> 
>>
>>
>> I think that we'd need to:
>>   1) blessing of our AD.
>>   2) pull document out of RFC-editor queue.
>>   3) revise it, do a WGLC on revision.
>>   4) get AD to put it back in queue.
>>
>> The ROLL WG did this for a document last year when we realized that a new
>> document obsoleted some of the recommendations.  It took longer than
>> planned, but that was partly because the other document had to settle a bit.
>> I think we could do this in the time for the 2nd WGLC and about four days.
>>
>>
>>
>> --
>> 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 Tue Jul 28 08:29:58 2020
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 B59233A0E3D; Tue, 28 Jul 2020 08:29:54 -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: 7.10.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: anima@ietf.org
Message-ID: <159595019469.29767.12981919363989007687@ietfa.amsl.com>
Date: Tue, 28 Jul 2020 08:29:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/_2ZHTDWcHW2l2pBgwuYwUws_AQw>
Subject: [Anima] I-D Action: draft-ietf-anima-autonomic-control-plane-28.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: Tue, 28 Jul 2020 15:29:55 -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-28.txt
	Pages           : 166
	Date            : 2020-07-28

Abstract:
   Autonomic functions need a control plane to communicate, which
   depends on some addressing and routing.  This Autonomic 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-28
https://datatracker.ietf.org/doc/html/draft-ietf-anima-autonomic-control-plane-28

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


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 Tue Jul 28 08:38:01 2020
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 CE6833A0DCC; Tue, 28 Jul 2020 08:37:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.412
X-Spam-Level: 
X-Spam-Status: No, score=-0.412 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, 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 WgJ5e9_QnKzK; Tue, 28 Jul 2020 08:37:47 -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 3F9873A0DFA; Tue, 28 Jul 2020 08:37:45 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 3E22F548440; Tue, 28 Jul 2020 17:37:39 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 35527440043; Tue, 28 Jul 2020 17:37:39 +0200 (CEST)
Date: Tue, 28 Jul 2020 17:37:39 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Roman Danyliw <rdd@cert.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-anima-autonomic-control-plane@ietf.org, anima-chairs@ietf.org, anima@ietf.org, Sheng Jiang <jiangsheng@huawei.com>
Message-ID: <20200728153739.GI1772@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <159478218035.5567.5331512017107084574@ietfa.amsl.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/YBKI4SlXvkCcv3scs9stRipUfn8>
Subject: Re: [Anima] Roman Danyliw's Discuss on draft-ietf-anima-autonomic-control-plane-27: (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: Tue, 28 Jul 2020 15:37:52 -0000

Thanks a lot, Roman, very helpfull review.

Diff:

http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=3Dhttps://tools.ietf.=
org/id/draft-ietf-anima-autonomic-control-plane-27.txt&url2=3Dhttps://tools=
=2Eietf.org/id/draft-ietf-anima-autonomic-control-plane-28.txt

Inline

On Tue, Jul 14, 2020 at 08:03:00PM -0700, Roman Danyliw via Datatracker wro=
te:
> Roman Danyliw has entered the following ballot position for
> draft-ietf-anima-autonomic-control-plane-27: Discuss
>=20
> 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.)
>=20
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.

Btw: WG members asked me how to determine if reviews like your raise
up to the level of a DISCUSS or just to the level of very good editorial fe=
edback.

As an author, i am not interested in that meta-discussion, but with the root
cause for the concern, which is the timely closure of the DISCUSS.

To that end, the authors think all DISCUSS worthy points raised have been r=
esolved or
satisfatory answered and would therefore hope for a timely closure of the D=
ISCUSS ;-))

> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-anima-autonomic-control-plane/
>=20
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>=20
> ** As normative behavior is specific for BRSKI (e.g., Section 6.1.5 and
> 6.1.5.5), please make it a normative reference

Hmmm... Right. At an earlier stage, we intentionally downgraded BRSKI
=66rom normative to informational, when we started to rewrite ACP so its
clear how to implement it with non-BRSKI registrars and BRSKI became
fully optional.

Resolution:

I have changed BRSKI to normative.

Let me know if informative wold still be corect given the optional naure of=
 BRSKI for ACP.


> ** Figure 2???s definition of acp-address is ???acp-address =3D 32HEXLC |=
 "0"???.  The
> following text references a 32HEXDIG but that isn???t in the definition of
> acp-address.
>=20
> -- Section 6.1.2.  ???Nodes complying with this specification MUST be abl=
e to
> receive their ACP address through the domain certificate, in which case t=
heir
> own ACP domain certificate MUST have the 32HEXDIG "acp-address" field.???
>=20
> -- Section 6.1.3.  ???The candidate peer certificate's acp-node-name has a
> non-empty acp-address field (either 32HEXDIG or 0, according to Figure 2)=
=2E???

Resolution:

Thank you so much. Embarrassing inconsistant edit in -23 to move from
32HEXDIG to lower case 32HEXLC. Fixed.

> ** Precision in bounding the cipher selection.
>=20
> -- Section 6.7.2.  Per ???Symmetric encryption for the transmission of se=
cure
> channel data MUST use encryption schemes considered to be security wise e=
qual
> to or better than AES256???, which property of AES-256 is being considere=
d for
> this assessment?

Key strength.

Resolution:

=2E.. considered to be security wise equal to or better than 256 bit key st=
rength, such as AES256

> -- Section 6.8.2.  Per ???TLS for GRASP MUST offer
> TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 and
> TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 and MUST NOT offer options with l=
ess
> than 256bit AES or less than SHA384???, please state this more precisely.

Also  key strength.

Resolution:

MUST NOT offer options with less than 256 bit symmetric key strength or has=
h strength of less han SHA384

> -- Is it that AES-128 shouldn???t be used or that that AES-256 has a cert=
ain key
> strength to which to adhere to?
>=20
> -- Is it that SHA-224 or SHA256 shouldn???t be used (staying in the SHA-2=
 family)
> or is it a certain number of bits of security ?

Note:

If my proposed text does not fix it according to what a security expert wou=
ld
write, could you be so kind and propose text ? This polishing of security s=
entences
has been going on a lot, mostly because i do not get proposed better text b=
ut
just rejections of the text i attempt to write after reading a lot of
security RFCs, and probably wastig a lot of time in the process.

> ** The text specifies the need for physical controls.  Please be more spe=
cific
> on the appropriate degree of that physical control or how that decision s=
hould
> be made; and explicitly explain threat of concern.
>=20
> -- Section 8.1.1.  ???Thus, the ACP connect interface and NOC systems con=
nected
> to it needs to be physically controlled/secured.???

Resolution:=20

<t>Physical controlled/secured means that attackers can gain no access to t=
he physical device hosting the ACP Edge Node, the physical interfaces and l=
inks providing the ACP connect link nor the physical equipment constituing =
the NOC Device. In a simple case, ACP Edge node and NOC Device are co-locat=
ed in a physcially access controlled room, such as a NOC, to which attacker=
s can not gain physical access to.</t>

> -- Section 8.1.5.  ?????? the ACP connect link and the nodes connecting t=
o it must
> be in a contiguous secure   environment, hence assuming there can be no
> physical attack against the devices.???

Resolution:

Text replaced with:

See <xref target=3D"acp-connect"/>.

Aka: removed text,
replaced with pointer to above enhanced text so as not to duplicate the exp=
lanatory text.

> ** (???discuss discuss???) Section 8.1.2.  What is the normative behavior=
 being
> specified in this section?  Specifically, what is the additional or more
> restrictive behavior for the circumstance is where an ACP node is virtual=
ized.

Resolution:=20

No text change, but following explanation:

The difference is that in the case of two physcial devices conneced with
a non-encrypted link, the effort of "physical security"/access-control is
a problem/requirement that makes ACP-connect a "workaround", because
the overhead of physical security is higher than that of a cryptographically
secured channel between the ACP nodes.

When ACP-Edge-Router and NOC-Device are just e.g.: two VMs running on the
same device, and the ACP connect link is a virtual linux bridge link,
then this is not a workaround anymore but a good solution because:

a) There is no need for physical security anymore (locked room, authenticate
   people who get access, etc. pp)

b) it does not have to be set up manually (bysically create access protected
   room, wire up two devices), but can be orchestrated automatically by
   software.

c) The remaining security problem of how to ensure that all the software
   components within the systems are protected against attack, including
   the virtual link between the NOC software component and the ACP Edge node
   sotware component is no different than securing the software on any
   ACP node.

I was hoping the text was making this clear. If there is additional text
you want to propose for the document to support this explanation, pls. do s=
o,
but i already felt the existing tex was a good, more compact representation
of what i elaborated above. If that is not the case, then it is easier
for someone like you (reader) than me to suggest text that could be better
understood.

> ** Section 8.2.1.  (I???m no ABNF expert ???) Per the ABNF in Figure 17, =
the ???//=3D???
> notation isn???t valid.  I think you want:
>=20
> OLD
>      method //=3D [ "DTLS",    port ]
>=20
> NEW
>      method =3D/ [ "DTLS",    port ]

Resolution: fixed text

Thanks a lot. No idea how this happened. Maybe i was confused with CDDL... =
Too many
formal languages all slightly different *sigh*

> ** Section 10.2.1.  Per ???An attacker will not be able to join the ACP u=
nless
> having a valid domain certificate, also packet injection and sniffing tra=
ffic
> will not be possible due to the security provided by the encryption proto=
col.???,
> please be clearer:
>=20
> -- on path attacker =3D no packet injection
> -- on path attacker =3D only traffic analysis when sniffing

Resolution:

Proposed fixed text:

                       <t>Attacker will not be able to join the ACP unless =
they have a valid ACP domain certificate. On-path attackers without a valid=
 ACP domain certificate can not inject packets into the ACP due to ACP secu=
re channels. They can also not decrypt ACP traffic except if they can crack=
 the encryption. They can attempt behavioral traffic analysis on the encryp=
ted ACP traffic.</t>

> -- compromised node =3D can inject traffic

Actually, we aim higher.

Resolution:

<t>The degree to which compromised ACP nodes can impact the ACP depends on =
the implementation of the ACP nodes and their impairment. When an attacker =
has only gained administrative privileges to configure ACP nodes remotely, =
the attacker can disrupt the ACP only through one of the few configuration =
options to disable it, see <xref target=3D"enabling-acp"/>, or by configuri=
ng of non-autonomic ACP options if those are supported on the impaired ACP =
nodes, see <xref target=3D"workarounds"/>. Injecting or ectracting traffic =
into/from an impaired ACP node is only possible when an impaired ACP node s=
upports ACP connect (see <xref target=3D"ACPconnect"/>) and the attacker ca=
n control traffic into/from one of the ACP nodes interfaces, such as by hav=
ing physical access to the ACP node.</t>

This should be a fair assessment. Of course this is not inclusive of attacks
against aspects of the node which are outside the AP spec.=20

[ Note that there are of course ideas for extension work to overcome these =
issues. ]

> ** Section 11.  Per ???an ACP is self-protecting and there is no need to =
apply
> configuration to make it secure???, if this assertion is going to be made:

Proposed rewrite of this paragraph:

<t>A set of ACP nodes with ACP certificates for the same ACP domain and wit=
h ACP functionaliy enabled is automatically "self-building": The ACP is aut=
omatically established between neighboring ACP nodes. It is also "self-prot=
ecting": The ACP secure channels are authenticated and encrypted.</t>

Aka: removed reference to registrar etc... (see explanation below), and "no=
 configuration required".
Primarily because "no configuration required" is somewhat duplicate from "a=
utomatically".

>=20
> -- please specify the security services/properties in a normative section=
 (not
> in the informative text in Section 10).

Statements of high level security properties do IMHO not have to be normati=
ve
text because they are an assessment, not a definition. I think this is quit=
e common
for security consideration sections from what i read in other RFCs. The def=
initions
of protocol machinery and properties of data objects like certificates to a=
chieve=20
those claimed properties on the other hand have to be normative, and they a=
re -
in section 6.

>=20
> -- please also be clear on what configuration is being referenced.
>=20

Much easier to remove as done above. I was thinking of the typical config
that would be required to create an ACP on a non-ACP device, e.g.:
VRF (lite), virtual/loopback interfaces, IPv6 addressing, IPSec config, RPL=
 routing config,
but not enough value IMHO to elaborate about this here.

Of course, not 100% the same, non-autonomic nodes would not have the new
GRASP protocol for discovery. But for the rest, you could get pretty cloe
on an existing non-ACP capable router through config. After all thats the
idea of ANIMA being in OPS - reuse what we have experience with.

> ** Section 11.  Per the list of factors on which ACP depends, it seems li=
ke the
> following are missing:
>=20
> -- the security properties of the enrollment protocol
>=20
> -- that the security considerations of EST and BRSKI apply (or if not, wh=
y not)

Resolution:=20

No change, but the following explanations:

The ACP is explicitly defined to be a set of nodes with ACP domain certific=
ates,
enrollment/BRSKI is really out of scope. Normative ACP nodes start their ex=
istance
with an ACP cert. How they got it is part of a prior life. BRSKI security p=
roperties
are covered in BRSKI draft.

I struggled long how to well define registrars given that ACP does not mand=
ate/
specify any specific protocol.  The solution in the document is that there =
is only
a very abstract definition of the normative requirements against registrars=
 in 6.10.7,
pretty much simple requirements against the resulting certificates such as =
registrar MUST
NOT assign same addresses to multiple nodes for example.=20

Think of a registrar abstractely as this:=20

https://datatracker.ietf.org/meeting/102/materials/slides-102-dinrg-dinrg-a=
nima-toerless-eckert-00
Slide 10

While funny, its not far away from a possible reality of a network operator
being a registrar, provisioning ACP certificates manually into ACP nodes,=
=20
and performing all the backend operations (CA, MASA, adressing database).

BRSKI is of course the ANIMA preferred enrollment protocol, and if it is us=
ed, an ACP
node is called an ANI node (ACP+BRSKI). Section 3.2 makes the security prop=
erty
of the ACP for any such bootstrap protocol. For example in communities outs=
ide
of ANIMA, NetConf ZeroTouch might be preferred over BRSKI.

The only mandatory ACP part of your above list is EST ONLY for renewal of c=
ertificates,
an that of course is specified in the normative section.

The BRSKI draft itself defines how it integrates with ACP (GRASP objective =
etc.).

Hope this answers satisfactory the concern.

>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> (Preliminary ballot.  Need to double check that all of ekr's discusses we=
re
> cleared)
>=20
> The style of explaining the design choice after describing an element of =
the
> protocol was informative and helpful.  Thanks.
>=20
> The this document has undergone a significant amount of security review. =
 Thank
> you for incorporating all of this feedback.

Thanks. If the feedack from the security reviewers would have included more
proposed text it would have been faster. Maybe i wouldn't have learned as m=
uch
about security as i did this way, but it was kinda painfull for the WG beca=
use
it was lengthy.

> ** Section 6.  It doesn???t seem appropriate to call a protocol ???indest=
ructible???
> unless you are going to enumerate the resiliency properties more precisel=
y ???
> ???many inadvertent changes??? is vague.

ACP is not a protocol. Its a system and node-wide design with the goal to
be "indestructible". Obviously, this is a name-calling to summarize a wide =
range
of benefits, hence it is in parenthesis.

Proposed text:

<t>This section describes the components and steps to set up an ACP and hig=
hlights the key properties which make it "indestructible" against most chan=
ges to the Data-Plane, including misconfigurations of routing, addressing, =
NAT, firewall or any other traffic policy filters that inadvertently or oth=
erwise unavoidably would also impact the management plane traffic, such as =
the actual operator CLI session or controller NetConf session through which=
 the configuration changes to the data-plane are executed. Physical misconf=
iguration of wiring between ACP nodes will also not break the ACP as long a=
s there is a transitive path between ACP nodes, the ACP should be able to r=
ecover given that it automatically operates across all interfaces of a ACP =
nodes. Attacks against the network via incorrect routing or addressing info=
rmation for the data-plane will not impact the ACP. Even impaired ACP nodes=
 will have a significantly reduced attack surface against malicious misconf=
iguration because only very limited ACP or interface up/down configuration =
can affect the ACP, and pending on their specific designs these type of att=
acks could also be eliminated. See more in <xref target=3D"enabling-acp"/> =
and <xref target=3D"security"/>.</t>

> ** Section 6.  Per ???An ACP node can be ??? or any other IP a capable no=
de???,
> should this be ???IPv6 capable node????

Fixed.

I was coming from practical experience, where devices are sold as IPv4 only
for price/market differentiation. Those devices could typically easily add =
the
IPv6-only ACP even though the Data-Plane was IPv4 only. I hope by now those
sales/marketing models are not possible anymore ;-)

> ** Section 6.1.1.  Per ?????? it is beneficial to copy the device identif=
ying
> fields of the node's IDevID certificate into the ACP domain certificate ?=
?????, is
> there a ACP-recommended approach for that?

No, because its part of what the registrar does, and even though ANIMA
defines BRSKI to be the preferred registrar protocol, ACP itself and to be=
=20
be widely reuseable describes registrar behavior as abstract as possible.

For example, IETF also has NetConf zerotouch, which could be used=20
or any proprietary mechanism. Its IMHO easy in all cases given how the expe=
ctation
is that the registrar needs to knows the pledges IDevID to securely identif=
y=20
the pledge, and in all protocols i have seen, the registrar is in
the position to make sure the pledges pledges certificate has components in=
 it that
are needed. For BRSKI this is specified in BRSKI.

> ** Section 6.1.3.1. Per ???In the absence of implementing a secured mecha=
nism,
> such an ACP node MAY use a current time learned in an insecured fashion i=
n the
> ACP domain membership check.???, please be clearer on how this current ti=
me is
> learned in the domain membership check.

Proposed text:

<t>Current time MAY for example be learned via NTP (<xref target=3D"RFC5905=
"/>)
over the same link-local IPv6 addresses used for the ACP from neighboring A=
CP nodes.
ACP nodes that that do provide NTP insecure over their link-local addresses=
 SHOULD
primarily run NTP across the ACP and provide NTP time across the ACP only
when they have a secure time source. Details for such NTP procedures are be=
yond the
scope of this specification.</t>

There is obviously a chicken&egg problem: If you have a bunch of cheap no-R=
TC
routers waking up from total power faillure and trying to get together agai=
n,
the best outcome to have is to build ACP  like it is Jan 1 1970. If at least
one of those devices does have an RTC, it would start NTP across the ACP
and the others would sync to it.=20

The details of all of this are another extension RFC to ACP, although
i guess it can become quite convoluted to describe the autoconfig and all
corner cases. Hence i tried to avoid going down this path in this doc too m=
uch.

The text above is roughly what i've used in practice with enterprise IPsec
VPN setups where alas a lot of spoke routers didn't hve RTC.

> ** Section 6.1.5.  Per ???ACP nodes SHOULD be able to remember the IPv6 l=
ocator
> parameters ...???, what happens if they don???t remember?

ACP is meant to support many, even uncoordinated registrars. That is why
the addressing scheme has a registrar-ID in the client addresses so that
registrars can independently of each other assign ACP addresses to clients =
via
their certs without conflicting with each other.

If you only do renewal via EST then it is purely a simplification of diagno=
stic that
you are doing renewal always with the registrar you originally got your cert
=66rom. The renewal would easily be the same going to any other registrar, =
but
the logs on the registrar would then not nicely have only the info about
the clients that they initially enrolled.

When clients expire their certs and need to re-enroll, it gets harder to
get the same ACP address again if you do not go to the same original regist=
rar.
There is text for that later in the doc explaining how registrars can still
attempt to honor the original cert ACP address, but this functionality
is probably something we need anothre extension document for with LAMPS
involved (registrars honoring expired certs for the purpose of renewal).

Changing ACP address under such circumstances is fine for ACP itself, but
more work for a backend system having to track such change of addresses
(having to keep track of e.g.: IDevID and changing LDevID/ACP-address).

> ** Section 6.1.5.3.  Per ???The connecting ACP node SHOULD verify that th=
e CRLDP
> certificate used during the HTTPs connection has the same ACP address as
> indicated in the CRLDP URL ??????, why is this not a MUST?

Unlike non-CRL setups, i have no practical deployment experience with CRL.
To the best of my understanding, the content of a CRL itself is protected
such that you can have it relayed through e.g.: caches or the like.
Hence the additional address is just another layer of security whose
added value vs the additional limitations for deployability it may bring are
unclear. Hence a SHOULD.

Eg.: In one example, i had to build an ACP connect through IPv6/IPv4 NAT
because some backend in customers NOC did not support IPv6.

> ** Section 6.1.5.5.  Per ???An ACP node may determine that its ACP domain
> certificate has expired ??? [i]n this case, the ACP node SHOULD convert t=
o a role
> of a re-enrolling candidate ACP node???, what is the alternative if it wa=
nts to
> connect back to the network?  Shouldn???t this be a MUST?

This goes back to above mentioned IMHO more desirable, but not yet
not documented or well enough discussed option of simply permitting=20
renewal instead of re-enrollment with an expired cert. Logically the
argument for that is that the lifetime in a cert does not necessarily have =
to
be a limiter to the registrar+CA renewal operations because that is
not a normal "use" of the certificate, and that is whats to be imited by
the lifetime.=20

When i was operating an enterprise VPN headend for a while i recurringly
had the eperience that long-time switched off VPN spokes where reactivated,
then the user asked in email why his VPN router does not work, and then
in the absence of better options i had to disable lifetime checks for
this cert on the headend temporarily to get renewal working. (obviuosly, th=
e phone
call was the additional attestation for the node with the expired cert to
be assumed to be still "trusted").

Re-enrollment can vary widely in complexity based on the registrar
used - even with BRSKI, there are lot of MASA options, So it can be
ACP career limiting for specific type of registrars if this was a MUST.

There is one specifically preferred option which would have to go into a
followup document, which is to use BRSKI and BRSKI proxy together with
the expired cert to renew. This exactly would only involve the registrar
having to honor the expired cert, but not the ACP. So its not really
re-enrolling (which would use the IDevID and MASA), but it would use the BR=
SKI
enrollment infra (BRSKI-proxy).

> ** Section 6.5.  It seems misplaced to describe MacSec as an option for c=
hannel
> security even when it is not a profiled in this document.

I disagree. It is IMHO important to provide important fundamental explanati=
ons of the
extension points of the ACP architecture, and that is most easily done thro=
ugh examples.

MacSec is a highly desirable extension option because it is the most widely=
 cross-platform
HW-accelerated encryption option, so it is a good example to use in a sente=
nce.

Remember, this is an OPS area system specification where operational
and architecture aspects are important. Also we where asked not to have a s=
eparate
architecture document by the initial AD to the WG.

> ** Section 6.7.2. Per ???Signaling of TA certificates may not be appropri=
ate when
> the deployment is relying on a security model when the TA certificate con=
tent
> is considered confidential???, where is the requirement to signal TA cert=
ificates
> discussed.  How would this selection of signaling a TA work?  The entire
> paragraph prior seemed to explicitly discuss that the TA doesn???t need t=
o be
> shared.

The previous paragraph to the one you are citing explicitly says:

| Nevertheless, for use with ACP secure channel setup,
| there SHOULD be the option to include the TA certificate in the signaling
| to aid troubleshooting, see <xref target=3D"ta-troubleshoot"/>.

I had exhaustive discussions about this on the ipsec mailing list to derive=
 at
the acceptable option, whose details are in the IPsec section of the ACP
(aka: including the TA in the signalled IKEv2 messages without having to
 extend IKEv2, but just relying on permissible existing IKEv2 options).

> ** Section 6.7.2.  Per ???When introducing the profile for security assoc=
iation
> protocol ??????, I recommend being clearer to whom you are providing this=
 advice.=20
> This seems to for operators of ACP infrastructure technology (not
> implementers/vendors of ACP technology)

Actually it is definition of extension point requirements for implementers,
so i am sad to learn it is misreadable as an operator related text.

Proposed fix:

<t>When specifying additional security association protocol for ACP secure =
channel use beyond those covered in this document, protocol options SHOULD =
be eliminated that are not necessary to support devices that are expected t=
o be able to support the ACP.

> ** Section 6.7.3.  Per ???The ACP usage of IPsec and IKEv2 mandates a pro=
file
> with a narrow set of options of the current standards-track usage guidanc=
e for
> IPsec    [RFC8221] and IKEv2 [RFC8247]???, should there be normative word=
ing use
> (MUST) instead of a ???mandates????

The actual normative (rfc2119) requirements of the IPsec profile are later =
in the section.
This initial text gives just the overview.

Saying something like "you MUST comply with the normative requirements
described later on in this text" would be only confusing and not helpfull.

> ** Section 6.7.3.1.1.  Per ENCR_CHACHA20_POLY1305, ???[t]herefore this al=
gorithm
> is only recommended???, shouldn???t it read as RECOMMENDED?

Again avoiding IMHO unhelpfull duplication of rfc2119 language. The normati=
ve requirement was
earlier in the section:

| ENCR_CHACHA20_POLY1305 SHOULD be supported at equal or higher performance
| than ENCR_AES_GCM_16. If that performance is not feasible, it MAY be supp=
orted.

The paragraph you mention is explanation of that prior normative requiremen=
t.

> ** Section 6.7.3.1.2.  Per ???[RFC8247] provides a baseline recommendatio=
n for
> mandatory to   implement ciphers, integrity checks, pseudo-random-functio=
ns and
> Diffie-Hellman mechanisms.  Those recommendations, and the recommendation=
s of
> subsequent documents apply well to the ACP.???, it seems like normative l=
anguage
> should be used to adhered to.

Oops. With the rewrite of this section in the last revisions, the MUST 8247
actually vanished. Great catch.

The text above is introduction, the proposed fix is after that paragraph:

| ACP Nodes supporting IKEv2 MUST comply with <xref target=3D"RFC8247"/> am=
ended by
| the following requirements which constitute a policy statement as permitt=
ed by
| <xref target=3D"RFC8247"/>.

> ** Section 6.10.7.3.  The paragraph/sentence starting with ???ACP registr=
ars that
> are aware of can use ?????? doesn???t parse.  The guidance isn???t clear =
as a result.

Apologies. trash left fixing the sentence. Fixed text and added explanation:

ACP registrars that are aware of the IDevID certificate of a candidate ACP =
device...

=2E.. The PID for example could identify type of
devices allowing for specialized ASA requiring multiple addresses or non-au=
tonomic VMs for
services and those nodes could receive Vlong sub-address scheme ACP address=
es.</t>

> ** Section 6.10.7.3.  Per ???In a simple allocation scheme, an ACP regist=
rar
> remembers persistently across reboots ??????, what???s the recover step i=
f it loses
> that state?

Proposed added text:

<t>If allocated addresses can not be remembered by registrars, then
it is necessary to either use a new value for the Register-ID field
in the ACP addresses, or determine allocated ACP addresses from polling the
ACP network nodes.  Non-tracked ACP addresses can be reclaimed by revoking
or not renewing their certificates and instead handing out new certificate
with new addresses (for example with a new Registrar-ID value). Note that
such strategies may require coordination amongst registrars.</t>

> ** Section 6.11.1.1.2.  Not clear what ???DODAG Information Objects (DIOs=
) SHOULD
> be sent 2 .. 3 times??? means ??? can ???2 .. 3??? please be clarified.

proposed fix:

SHOULD be sent 2 or 3 times

(actual value 2 or 3 left for experimentation, this seems to be a necessary=
 and sufficient
 range from similar protocol experiences).

> ** Section 6.11.1.1.2.  A mechanism for failed ACP detected using a secure
> channel protocol is noted for IPSec (with IKEv2 Dead Peer Detection).  Wh=
at is
> the equivalent for DTLS?

Good question. If you know someone who could suggest an equivalent, please
bring her in. Given how this is a performance optimization, i don't think
we need to bother too much. I hope we can learn from implementation/deploym=
ent
experience (i only hve that for IPsec) and then write update text later with
such refinements.

> ** Section 9.  The section notes that Section 9.1 is ???derived from diag=
nostic
> of a commercially available ACP implementation???.  The shepherd report f=
rom
> 03/2019 notes that there are no implementations of ACP.  If this is docum=
ented
> somewhere, it would be very compelling to cite it.

I have deleted that sentence again.  This was not appropriate for the RFC,
we can discuss this on the list or offline.

> ** Section 9.1. Per ???The basic diagnostics [sic] is support of (yang) d=
ata
> models representing the complete (auto-)configuration and operational sta=
te of
> all components ??????, are these YANG models defined?  Are there referenc=
es?

Changed to:

Basic standardized diagnostics would require support for (yang) models ...

Wrt to the question: The existing components used by ACP should have YANG m=
odels
given how long they have been in use, but they don't necessarily seem to ha=
ve them.
Eg there as some IPSECME targeted draft like draft-tran-ipsecme-yang-01.txt=
, not
sure why that died, one could maybe use rfc8049 to represent the VRF for AC=
P (not sure),
there is an initial dradt for RPL (draft-ietf-roll-mpl-yang-02). From talki=
ng
to Kent Watson, the situation for certificates looks better, e.g.:
draft-ietf-netconf-trust-anchors.

Once we have these ACP/GRASP/BRSKI specification RFCs out, we'll be looking=
 for interested
Yang geeks to help with ACP/GRASP yang models. The existing spec intends
to be an informal starting point towards such future  yang work, but there
will no more detailling of what is or is not available in IETF yang world.
Thts a job by itself best done fofr an acp yang rfc. I have some work i
started from 3 years ago lying around...=20

> ** Section 9.3.1.  Per ???Whenever this document refers to enabling an in=
terface
> for ACP ??? it only requires to permit [sic] the interface ??????, this s=
eems like
> normative behavior in an informative section.

What is the purpose of the [sic] notation ?

IETF does not allow to raise normative requirements against informal operat=
or
interface decription, which is what this section is. I guess that would
require a formal CLI model which we don't have.  Hence the normative
requirements could only come from a YANG model.

Hence this section is informational. It is also good to not formalize a nor=
mative
operator interface without first having enough experience collected IMHO.

> ** Section 9.3.2.  That this is an information section is noted.  It would
> benefit from describing what precisely can and cannot be done in the three
> states proposed ??? up, down and admin down.

Hmm... i think it says everything it can say, except... see your following =
point.

> ** Section 9.3.2.1.  What is the proposed threat that using admin down is
> intended to mitigate?  Under what circumstance should it be invoked?

Great. I remember we went several times through this text especially with r=
outing
directorate, but nobody noticed that the simple core example was not explic=
itly
written down. Instead we had good discuss about the proposed how
(separartion of down insto adin-down/physcial down). Which is a good reason
too not to have this section normative yet. But i digress.

I added the following paragraph to the section. The configuration summary s=
ection
actually already summarizes this core reason as well, but it really needs t=
o be in this section.

<t>One of the common problems of remote management is for the operator or S=
DN controller to cut its own connectivity to the remote node by a configura=
tion impacting its own management connection into the node. The ACP itself =
should have no dedicated configuration other than aforementioned enablement=
 of the ACP on brownfield ACP nodes. This leaves configuration that can not=
 distinguish between ACP and Data-Plane as sources of configuration mistake=
s as these commands will impact the ACP even though they should only impact=
 the Data-Plane. The one ubiquitous type of commands that do this on many t=
ype of routers are interface "down" commands/configurations. When such a co=
mmand applied on the interface through which the ACP provides access for re=
mote management it would cut the remote management connection through the A=
CP because (as outlined above), the "down" commands typically impact the ph=
ysical layer too and not only the Data-Plane services.</t>

<t>To provide ACP/ANI resilience against such operator misconfiguration, ...

> ** Section 9.3.2.1.  Per ???"Admin down" state as described above provide=
s also a
> high level of security because it only permits ACP/ANI operations which a=
re
> both well secured???, to what is the ???both??? referring? I suspect this=
 is
> editorial (but just in case, noting here).

Added sentence in before for more missing explanation:

<t>An example of non-ACP but ANI traffic that should be permitted to pass e=
ven in "admin-down" state is BRSKI enrollment traffic between BRSKI pledge =
and a BRSKI proxy.</t>

Now the answer to your question is that the "both" in the sentence you ask
about refers to ACP/ANI (both ACP and ANI).  If this is not good english, p=
ls. let me know.

> ** Section 10.2.2.  Per ???For example, management plane functions (trans=
port
> ports) should only be reachable from the ACP but not the Data-Plane???, t=
his
> seems like good guidance.  Is there a reason not to upgrade this informat=
ive
> statement and put it the Security Considerations as normative guidance?

Give it time. We're in round 1:

Existing router management plane host stacks may have severe issues separat=
ing
out access by VRF context. I remember some of the per-VRF SMI work.

Enterprise operators may have severe issues with this short-term. For examp=
le,
the typical solution would be for network admins to have to VPN back into s=
ome
headend from where the ACP is accessible. That is a lot of pain especially =
when
you are trying to troubleshoot locally and the headend is remote.

To make future network admin staff work not more convoluted because of ACP,
but actually more secure AND easier, we need some easily useable ACP-access=
 method
for e.g. network admin notebooks. Given how i at times had 4 VPNs on my not=
ebook
and at most 2 VPN would work at the same time, i am not sure if this docume=
nts
IPsec spec would be good for operator notebooks. But maybe an ACP acces met=
hod
via 802.1x... TBD.

> ** Section 10.2.2.  Per ???Protection across all potential attack vectors=
 is
> typically easier to do in devices whose software is designed from the gro=
und up
> with security in mind than with legacy software based systems where the A=
CP is
> added on as another feature???, no argument on the general principle.  Ho=
wever,
> as it relates to ACP:

Changed text "security in mind" -> "ACP in mind".

I think there a initiatives looking at secure devices, but thats not the
same as stricter isolation between ACP and the rest of the system.

> --what???s an example of the legacy software?

I had a presentation about designs for ACP a few years back in an IEEE conf=
erence
touching those aspects.

To me, legacy is probably most router software infra today, where you
would need to implement ACP as one of many VRFs that the software may alrea=
dy
already support as part of e.g.: L3VPN or similar services.=20

Non-legacy is something where the router is actually a VM or container=20
running on a hypervisor. And ACP would be part of the hypervisor (e.g.: lin=
ux). Or
where ACP does not even run on the same CPU/FPE as the router, but=20
on e.g.: BMC HW/software (OpenBoot etc..). Lots of interesting design
choices possible.

> -- as noted in the shepherd report from 03/2019, there are no implementat=
ions,
> so is there reason to believe that this is going to put on ???legacy??? p=
latforms?

Lets use different mail threads to discuss this.

> ** Section 10.2.2.  Per ???As explained above, traffic across the ACP SHO=
ULD
> still ??????, is RFC2119 language really intended in this informative sec=
tion?

Fixed to lower case. Thanks.

> ** Section 11.  Per ???Security can be compromised by implementation erro=
rs
> (bugs), as in all products???, given the generic nature of this statement,
> couldn???t it also be a configuration error in the product too?

;-) Not really because the claim of ACP is that all the core parts of ACP
have no configuration. See section 9.5.=20

Given how more than 50% of the whole document to me feel like talking about
security, i do have a hard time figuring out a mandatory logic of what belo=
ngs into
section 11. My solution  was that it is a mixture of important summaries and
then tidbits that didn't have a better place to be explained.

Given how the topic of configuration and misconfiguration of ACP was exhaus=
tively
discussed in prior sections, i didn't feel the need to add it here again.

But always happy to consider proposed text.

> ** Section 11.  Per ???Higher layer service built using ACP domain certif=
icates
> should not rely on undifferentiated group security ?????? is there a reas=
on not to
> make this a normative SHOULD?

section 11 is not normative, and actual normative requirements for new stuff
across the ACP is something that was not in charter when we defined this do=
cument,
aka: i wouldn't have a logical place in this doc for this beside as a gener=
al
security considerartion.

Writing normative about ASA IMHO just became possible after recharter of WG=
 last
year, so i would want to put normative requirements about this probably int=
o ASA=20
docs we are starting to write.

> ** Editorial
>=20
> -- Recommend being consistent on either ???ACP domain certificates??? or =
???ACP
> certificates???

ACP certificates.

> -- Section 1.  Editorially.  The two sentences ???Section 7 defines norma=
tive how
> to ?????? and ???Section 8 explain normative how ?????? don???t parse as =
the adjective
> normative needs a noun to modify.

Fixed by putting (normative) at the end of the sentences.

> -- Section 6.1.4.  Editorial.  s/These requirements can be achieved by us=
ing TA
> private/These requirements can be achieved by using a TA private/

fixed

> -- Section 6.2.  Editorial. s/does intentionally not/intentionally does n=
ot/

fixed

> -- Section 6.5.  Editorial.  Per ???Note that MacSec is not required by a=
ny
> profiles of the ACP in this specification but just mentioned as a likely =
next
> interesting secure channel protocol.???, does not parse.

Fixed by separating sentences: Instead, MacSec is mentioned as ...
>=20
> -- Section 6.10.7.  Per ???ACP registrars are responsible to enroll candi=
date ACP
> nodes with ACP domain certificates and associated trust point(s)???, is a=
 trust
> point the same thing as a trust anchor?    If so, I recommend being consi=
stent.
>  If not, then please define it.

Oops. how did that slip through. Thought i had fied all points to be anchor=
s.
Fixed now.

> -- Section 6.11.1.  Please make draft-ietf-roll-applicability-template a
> reference.

Already in -27.

> -- Section 6.11.1.5.  Editorially.  It might be worth framing the path me=
tric
> in the form of sentence.

Fixed to:
Use Hopcount according to xref target=3D"RFC6551"
>=20
> -- Section 11. s/enemy plegdes/rogue pledges/

Was already fixed in -27 to "malicious registrar"
(on prior reviewer suggestion i think)

> -- Section 11. Per ???Fundamentally, security depends on avoid operator a=
nd
> network automation mistakes ??????, this paragraph is not actionable.  Re=
commend
> removal.

Fixed with proposed replacement paragraph:

<t>Operators and provisioning software developers need to be aware of how t=
he provisioning/configuration of network devices impacts the ability of the=
 operator / provisioning software to remotely access the network nodes. By =
using the ACP, most of the issues  of configuration/provisioning caused los=
s of connectivity for remote provisioning/configuration will be eliminated,=
 see <xref target=3D"self-creation"/>. Only few exceptions such as explicit=
 physical interface down configuration will be left <xref target=3D"admin-d=
own"/>.</t>

First sentence should now be actionable to operators/developers.
Second summarizes benefits of ACP. Third gives example of limitations.

Core value proposition of ACP hence useful to not just eliminate in securit=
y section
(assuming certain readers will primarily read security section).=20

This answers the actionable point. whether or not misconfiguration
that makes a network become unmanage is a security issue, i can't judge,
because i am not sure i know a precise definition of "security"


> ** Typos
> Section 1.  Typo. s/parth/path/
> Section 1.  Typo. s/seperately/separately/
> Section 1.  Typo. s/automaticically/ automatically/
> Section 1.  Typo. s/managemenet/ management/
> Section 1.  Typo. s/absene/absence/
> Section 1.1.  Typo. s/solution:/solution/
> Section 2.  Typo. s/netork/network/
> Section 2.  Typo. s/physcially/physically/
> Section 5.  Typo. s/(see (see/(see/
> Section 5. Typo. s/loopack/loopback/
> Section 6.1.1.  Typo. s/e.g.:signing/e.g., signing/
> Section 6.1.1.  Typo. s/signalled/signaled/g
> Section 6.1.1.  Typo. s/bei/by/
> Section 6.1.2.  Typo. s/simpy/simply/
> Section 6.1.2.  Typo. s/readible/readable/
> Section 6.1.2.  Typo. s/Adresses/Addresses/
> Section 6.1.2.  Typo. s/manadatory/mandatory/
> Section 6.1.2. Typo. s/inapproprite/inappropriate/
> Section 6.1.3.1.  Typo. s/as as/as/
> Section 6.1.3.1.  Typo. /insecured/insecure/
> Section 6.1.3.1.  Typo. s/likley/likely/
> Section 6.2. Typo. s/IKEv2 has am/IKEv2 has an/
> Section 6.7.2.  Typo. s/successfull/successful/
> Section 6.7.3.1.1.  Typo.  s/superceed/superseded/
> (I stopped documenting spelling errors at Section 6.7.3.1.1.  Please run a
> spell checker before handing this off to the RFC Editor)

Sorry for this editorial trouble. I was hoping that you would not
spend time on this. Yes, of course i will do a more thorough check
before RFC editor. My excuse for not doing it on every rev is
quite lame, but i have not found a spell checker that remembers
all the non-standard words correctly, so a few changes in a 160 page docume=
nt
is terrible each time...

Thanks so much for the excellent review! Please consider removing the
discuss.

Cheers
    Toerless


From nobody Wed Jul 29 03:51:01 2020
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 6EEAC3A0878; Wed, 29 Jul 2020 03:50:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, 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 JXzschzDt72r; Wed, 29 Jul 2020 03:50: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 849083A0881; Wed, 29 Jul 2020 03:50:54 -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 98C88548048; Wed, 29 Jul 2020 12:50:49 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 8DA92440043; Wed, 29 Jul 2020 12:50:49 +0200 (CEST)
Date: Wed, 29 Jul 2020 12:50:49 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: "Ciavaglia, Laurent (Nokia - FR/Paris-Saclay)" <laurent.ciavaglia@nokia.com>
Cc: Sheng Jiang <jiangsheng@huawei.com>, "anima-chairs@ietf.org" <anima-chairs@ietf.org>, "anima@ietf.org" <anima@ietf.org>, "Brian E Carpenter (brian.e.carpenter@gmail.com)" <brian.e.carpenter@gmail.com>
Message-ID: <20200729105049.GA36451@faui48f.informatik.uni-erlangen.de>
References: <12ed9e0beafe415fb3e6df59bb74c85e@huawei.com> <20200721035434.GA5003@faui48f.informatik.uni-erlangen.de> <PR3PR07MB6826F89764A22BF2F9950853F3790@PR3PR07MB6826.eurprd07.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <PR3PR07MB6826F89764A22BF2F9950853F3790@PR3PR07MB6826.eurprd07.prod.outlook.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/T4lR9Vu_TuMeuFy_jWr_fciKuBc>
Subject: Re: [Anima] ANIMA: Reminder: Re: Call for agenda ANIMA @ IETF 108, online
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, 29 Jul 2020 10:51:00 -0000

Ack. Please send slides in email or via datatracker

On Wed, Jul 22, 2020 at 10:43:47AM +0000, Ciavaglia, Laurent (Nokia - FR/Paris-Saclay) wrote:
> Dear ANIMA WG Chairs,
> 
> We'd like to ask for a short slot on draft-carpenter-anima-asa-guidelines.
> The main purpose is to present the status of the I-D (no change, stable version) and ask for WG document adoption.
> 
> Best regards, 
> -Laurent
> 
> > -----Original Message-----
> > From: Anima <anima-bounces@ietf.org> On Behalf Of Toerless Eckert
> > Sent: Tuesday, July 21, 2020 05:55
> > To: Sheng Jiang <jiangsheng@huawei.com>
> > Cc: anima-chairs@ietf.org; anima@ietf.org
> > Subject: [Anima] ANIMA: Reminder: Re: Call for agenda ANIMA @ IETF 108,
> > online
> > 
> > Reminder. Please bring forward for any agenda items you want to see.!
> > 
> > Thanks
> >     Toerless
> > 
> > On Fri, Jul 10, 2020 at 07:51:34AM +0000, Sheng Jiang wrote:
> > > Hi, all anima,
> > >
> > >
> > >
> > > We have been allocated a sessions of 1 hour 40 minutes for the ANIMA WG
> > meeting for IETF-108 (online). It is on Thursday, July 30, 2020?? 11:00-
> > 12:40 (UTC). We are now starting to collect agenda items for the session.
> > Please send your request for agenda by July 21th, Tuesday, to anima-
> > chairs@ietf.org and both chairs' email. Please note that email to a single
> > chair may cause single-point failure.
> > >
> > >
> > >
> > > 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) requests for time slot by July
> > 21th, Tuesday and include:
> > >
> > >
> > >
> > > Name of time slot:
> > >
> > > Name of draft(s):
> > >
> > > Time requested:
> > >
> > > Presenter name(s):
> > >
> > >
> > >
> > > More details about the IETF 108 can be found at:
> > >
> > >
> > >
> > > https://www.ietf.org/how/meetings/108/
> > >
> > >
> > >
> > > 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,
> > >
> > >
> > >
> > > Sheng + Toerless
> > >
> > 
> > --
> > ---
> > tte@cs.fau.de
> > 
> > _______________________________________________
> > Anima mailing list
> > Anima@ietf.org
> > https://www.ietf.org/mailman/listinfo/anima

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


From nobody Wed Jul 29 03:55:55 2020
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 6548B3A08B3; Wed, 29 Jul 2020 03:55:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, 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 UkERchfbFqma; Wed, 29 Jul 2020 03:55:52 -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 38FB53A0886; Wed, 29 Jul 2020 03:55: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 4459D548048; Wed, 29 Jul 2020 12:55:47 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 3E245440043; Wed, 29 Jul 2020 12:55:47 +0200 (CEST)
Date: Wed, 29 Jul 2020 12:55:47 +0200
From: Toerless Eckert <tte@cs.fau.de>
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>
Message-ID: <20200729105547.GB36451@faui48f.informatik.uni-erlangen.de>
References: <12ed9e0beafe415fb3e6df59bb74c85e@huawei.com> <20200721035434.GA5003@faui48f.informatik.uni-erlangen.de> <CA50D621-B014-4D30-8DCE-2A06DEC6460B@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA50D621-B014-4D30-8DCE-2A06DEC6460B@cisco.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/OtSqJTtDOe9NHSGRDcbv53a9RKg>
Subject: Re: [Anima] ANIMA: Reminder: Re: Call for agenda ANIMA @ IETF 108, online
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, 29 Jul 2020 10:55:55 -0000

Please send slides or upload to data tracker

On Tue, Jul 21, 2020 at 01:40:11PM +0200, Eliot Lear wrote:
> Hi Toerless,
> 
> The co-authors would like to have a few minutes to talk about BRSKI-AE.  I think 10 ought to do.
> 
> Thanks,
> 
> Eliot
> 
> > On 21 Jul 2020, at 05:54, Toerless Eckert <tte@cs.fau.de> wrote:
> > 
> > Reminder. Please bring forward for any agenda items you want to see.!
> > 
> > Thanks
> >    Toerless
> > 
> > On Fri, Jul 10, 2020 at 07:51:34AM +0000, Sheng Jiang wrote:
> >> Hi, all anima,
> >> 
> >> 
> >> 
> >> We have been allocated a sessions of 1 hour 40 minutes for the ANIMA WG meeting for IETF-108 (online). It is on Thursday, July 30, 2020?? 11:00-12:40 (UTC). We are now starting to collect agenda items for the session. Please send your request for agenda by July 21th, Tuesday, to anima-chairs@ietf.org and both chairs' email. Please note that email to a single chair may cause single-point failure.
> >> 
> >> 
> >> 
> >> 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) requests for time slot by July 21th, Tuesday and include:
> >> 
> >> 
> >> 
> >> Name of time slot:
> >> 
> >> Name of draft(s):
> >> 
> >> Time requested:
> >> 
> >> Presenter name(s):
> >> 
> >> 
> >> 
> >> More details about the IETF 108 can be found at:
> >> 
> >> 
> >> 
> >> https://www.ietf.org/how/meetings/108/
> >> 
> >> 
> >> 
> >> 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,
> >> 
> >> 
> >> 
> >> Sheng + Toerless
> >> 
> > 
> > -- 
> > ---
> > tte@cs.fau.de
> > 
> > _______________________________________________
> > Anima mailing list
> > Anima@ietf.org
> > https://www.ietf.org/mailman/listinfo/anima

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


From nobody Wed Jul 29 05:27:25 2020
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 07B863A0A12 for <anima@ietfa.amsl.com>; Wed, 29 Jul 2020 05:27:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.118
X-Spam-Level: 
X-Spam-Status: No, score=-1.118 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, 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 0n63vcCNvdcK for <anima@ietfa.amsl.com>; Wed, 29 Jul 2020 05:27:21 -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 E12DA3A0B3B for <anima@ietf.org>; Wed, 29 Jul 2020 05:27:12 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id B1C165485D2 for <anima@ietf.org>; Wed, 29 Jul 2020 14:27:08 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id A9D4F440043; Wed, 29 Jul 2020 14:27:08 +0200 (CEST)
Date: Wed, 29 Jul 2020 14:27:08 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: anima@ietf.org
Message-ID: <20200729122708.GC36451@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/I1RqlK_KU6tFXPNXFEU98FHRiQw>
Subject: [Anima] IETF108 ANIMA WG meeting - logistics - agenda - win a pizza and more
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, 29 Jul 2020 12:27:24 -0000

1. See below for current agenda. If you had send a request and it is not on the
   agenda, pls. chime in now.

2. So far we have only received slides from Steffen for BRSKI-AE, pls. send your slides or
   better yet, upload to datatracker yourself.

3. Please step forward if you are willing to take notes (email to anima-chairs@ietf.org)
   PLEASE STEP FORWARD WHEN YOU ARE WILLING TO TAKE NOTES
   I WILL FIGURE OUT HOW TO SEND YOU A PIZZA, WHEREEVER YOU ARE
   Thank you !! Thank you !!

4. If you plan to present:
   Join before session to check your audio
   Feel free to send to anima-chairs@ietf.org a way to contact you
   in case the room has problems while you are presenting.
   Example: phone# or anything else that would interrupt you when you are presenting, but it is actually not working

   (Non-working presenters where recurring problem in other IETF108 session and it took presenters
    sometimes > 10 minutes to figure out by themselves they where talking into the void).

Cheers
    Toerless

---------------------------------------
What: ANIMA

When: 11:00 - 12:40 Thursday Session I

Where: Room 3

Slot: Administrivia  - scribes, minutes, etc.
Presenters Chairs - Sheng / Toerlessl
Time: 10 minutes

Slot: Update on ACP
Presenter: Toerless Eckert
Draft: https://datatracker.ietf.org/doc/draft-ietf-anima-autonomic-control-plane/
Time: 15 minutes

Slot: Update on ASA guidelines
Presenter: Laurent Ciavaglia
Draft: https://datatracker.ietf.org/doc/draft-carpenter-anima-asa-guidelines
Notes: Asking for adoption call
Time: 10 minutes

Slot: Support of asynchronous enrollment in BRSKI
Presenter: S. Fries, E. Lear
Draft: https://datatracker.ietf.org/doc/draft-ietf-anima-brski-async-enroll/
Notes: Discuss /.well-known/brski at end of this slot
Notes: Michael has conflict can only start presenting after 30 mins into time slot
Notes: hence trying to have slots ordered accordingly
Time: 10 minutes

Slot: brski-cloud
Presenter: Michael Richardson       
Draft: https://datatracker.ietf.org/doc/draft-friel-anima-brski-cloud/
Time: 10min

Slot: *-considerations document structure
Presenter: Michael Richardson
Draft: https://datatracker.ietf.org/doc/draft-richardson-anima-voucher-delegation/
Draft: https://datatracker.ietf.org/doc/draft-richardson-anima-masa-considerations/
Draft: https://datatracker.ietf.org/doc/draft-richardson-anima-registrar-considerations/
Notes: Ask room who has read drafts (no tool for that... try humming)
Notes: Adoption call after IETF 
Time: 15 minutes

Open Mic


From nobody Wed Jul 29 11:29:12 2020
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 510CD3A0E02; Wed, 29 Jul 2020 11:29:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, 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 NgK4Prl0Qt6D; Wed, 29 Jul 2020 11:29:08 -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 03A203A0DFE; Wed, 29 Jul 2020 11:29:07 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 8CA92548048; Wed, 29 Jul 2020 20:29:03 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 7EFD7440043; Wed, 29 Jul 2020 20:29:03 +0200 (CEST)
Date: Wed, 29 Jul 2020 20:29:03 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: draft-ietf-anima-grasp-distribution@ietf.org
Cc: anima@ietf.org
Message-ID: <20200729182903.GI1772@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/WcMbtNcFEiPnMNBlNfLZvmcoc7M>
Subject: [Anima] Update on draft-ietf-anima-grasp-distribution ?
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, 29 Jul 2020 18:29:11 -0000

Dear draft-ietf-anima-grasp-distribution authors

I have not seen a request for giving an update on subject WG draft. 
Pls let us know what the status of the doc is, either in writing,
or tomorrow at the WG meeting, i will mention it during WG chair slot.

Thanks!
    Toerless


From nobody Wed Jul 29 14:05:05 2020
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 47FFD3A0E5C; Wed, 29 Jul 2020 14:05:03 -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, RCVD_IN_MSPIKE_H2=-0.001, 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 OZZnS6yks9hb; Wed, 29 Jul 2020 14:05:00 -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 5A9D53A0F18; Wed, 29 Jul 2020 14:04:36 -0700 (PDT)
Received: from lhreml739-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id BEFA6E455371B9764514; Wed, 29 Jul 2020 22:04:33 +0100 (IST)
Received: from fraeml744-chm.china.huawei.com (10.206.15.225) by lhreml739-chm.china.huawei.com (10.201.108.189) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Wed, 29 Jul 2020 22:04:33 +0100
Received: from fraeml737-chm.china.huawei.com (10.206.15.218) by fraeml744-chm.china.huawei.com (10.206.15.225) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Wed, 29 Jul 2020 23:04:33 +0200
Received: from fraeml737-chm.china.huawei.com ([10.206.15.218]) by fraeml737-chm.china.huawei.com ([10.206.15.218]) with mapi id 15.01.1913.007;  Wed, 29 Jul 2020 23:04:33 +0200
From: Xun Xiao <Xun.Xiao@huawei.com>
To: Toerless Eckert <tte@cs.fau.de>, "draft-ietf-anima-grasp-distribution@ietf.org" <draft-ietf-anima-grasp-distribution@ietf.org>
CC: "anima@ietf.org" <anima@ietf.org>
Thread-Topic: Update on draft-ietf-anima-grasp-distribution ?
Thread-Index: AQHWZdYu0vmsZ+2dyU+EkkwehtQidakfCt6A
Date: Wed, 29 Jul 2020 21:04:32 +0000
Message-ID: <116de96ec91a4f48932b564988142fb4@huawei.com>
References: <20200729182903.GI1772@faui48f.informatik.uni-erlangen.de>
In-Reply-To: <20200729182903.GI1772@faui48f.informatik.uni-erlangen.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.48.221.130]
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/BXMQiReZgQ77AXfTI65sP-0J2MY>
Subject: Re: [Anima] Update on draft-ietf-anima-grasp-distribution ?
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, 29 Jul 2020 21:05:04 -0000

Dear ANIMA chair,

We were still editing it and now we want to provide a relatively complete v=
ersion integrating 'draft-carpenter-anima-grasp-bulk-05'. That's why we did=
 not send any request of a session.

Best Regards,

Xun Xiao (=1B$B>S?W=1B(B)
Advanced Wireless Technology Lab
Munich Research Center
Huawei Technologies Co.,Ltd.

-----Original Message-----
From: Toerless Eckert [mailto:tte@cs.fau.de]=20
Sent: Wednesday, July 29, 2020 8:29 PM
To: draft-ietf-anima-grasp-distribution@ietf.org
Cc: anima@ietf.org
Subject: Update on draft-ietf-anima-grasp-distribution ?

Dear draft-ietf-anima-grasp-distribution authors

I have not seen a request for giving an update on subject WG draft.=20
Pls let us know what the status of the doc is, either in writing, or tomorr=
ow at the WG meeting, i will mention it during WG chair slot.

Thanks!
    Toerless


From nobody Thu Jul 30 08:46:16 2020
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 780B53A0AC3 for <anima@ietfa.amsl.com>; Thu, 30 Jul 2020 08:46:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level: 
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, 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 160FDYY2Wc3R for <anima@ietfa.amsl.com>; Thu, 30 Jul 2020 08:46:12 -0700 (PDT)
Received: from gw-eagle2.siemens.com (gw-eagle2.siemens.com [194.138.20.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FA9A3A0ABD for <anima@ietf.org>; Thu, 30 Jul 2020 08:46:12 -0700 (PDT)
Received: from mail2.dc4ca.siemens.de (mail2.dc4ca.siemens.de [139.25.224.94]) by gw-eagle2.siemens.com (Postfix) with ESMTPS id 87677468014; Thu, 30 Jul 2020 17:46:10 +0200 (CEST)
Received: from DEMCHDC8A2A.ad011.siemens.net (demchdc8a2a.ad011.siemens.net [139.25.226.108]) by mail2.dc4ca.siemens.de (Postfix) with ESMTPS id 49B141511CF94; Thu, 30 Jul 2020 17:46:10 +0200 (CEST)
Received: from DEMCHDC8A1A.ad011.siemens.net (139.25.226.107) by DEMCHDC8A2A.ad011.siemens.net (139.25.226.108) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2044.4; Thu, 30 Jul 2020 17:46:09 +0200
Received: from DEMCHDC8A1A.ad011.siemens.net ([139.25.226.107]) by DEMCHDC8A1A.ad011.siemens.net ([139.25.226.107]) with mapi id 15.01.1979.003;  Thu, 30 Jul 2020 17:46:09 +0200
From: "Fries, Steffen" <steffen.fries@siemens.com>
To: Michael Richardson <mcr@sandelman.ca>, Eliot Lear <lear@cisco.com>, "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>, Toerless Eckert <tte@cs.fau.de>
CC: "anima@ietf.org" <anima@ietf.org>
Thread-Topic: Handling of endpoint path names (from BRSKI-AE discussion today)
Thread-Index: AdZmfbkJ/iBKc9n1QAWzDvrnlpnz3w==
Content-Class: 
Date: Thu, 30 Jul 2020 15:46:09 +0000
Message-ID: <3f2d1790efb44ac39405a23dc592dd89@siemens.com>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Enabled=true; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SetDate=2020-07-30T15:46:05Z;  MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Method=Standard; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Name=restricted-default; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SiteId=38ae3bcd-9579-4fd4-adda-b42e1495d55a; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ActionId=c15637ac-96a8-4787-9bee-3af6edd47582; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ContentBits=0
document_confidentiality: Restricted
x-originating-ip: [139.21.146.185]
x-tm-snts-smtp: 2F45A1E04F9BF1E72A9A25D370AE0347B26E90E6C1A8EF7548BAF4B339DB226E2000:8
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/jjusQdqzS3G4WbczolCxF0_YmQQ>
Subject: [Anima] Handling of endpoint path names (from BRSKI-AE discussion today)
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, 30 Jul 2020 15:46:15 -0000

Hi,

Based on the discussion of splitting up the voucher handling endpoint namin=
g issues from BRSKI-AE today, I just wanted to ensure I got the way forward=
 right.=20
>From the Etherpad discussion I understood Michael that he would not be too =
happy with having a BRSKI update right after BRSKI publication as RFC. I th=
ink finalizing the discussion on the list was advised.

What we discussed in the WG meeting was to have a separate short document, =
basically defining a renaming or alternatively an alias for the current end=
points, which allows to keep the current implementations as is.=20
Hence, the draft would relate to all of the endpoints defined in section 5 =
of BRSKI for the domain registrar facing the pledge (and potentially also t=
he MASA), which are:=20
/.well-known/est/requestvoucher	used by pledge to registrar but also from r=
egistrar to MASA
/.well-known/est/voucher_status	used by pledge to registrar
/.well-known/est/requestauditlog	used by registrar to MASA
/.well-known/est/enrollstatus		used by pledge to registrar

>From Toerless I understood that he would like to not change the current dra=
ft as it is already in the final state and rather provide an update as sepa=
rate document.
>From Michael I understood he would not be keen on having a fast update for =
the BRSKI document. At least not for a renaming of the defined endpoints. A=
lso the IESG may view this as too fast.=20
Eliot stated that there are already implementations out there that utilize =
the /est approach. So having aliases could be one way of dealing with it, b=
ut this would double the endpoints at least for the four stated ones above.=
=20

Both approaches have there merits. Having the endpoints distinct from the b=
eginning allows a clearer separation of the functionalities, for the pledge=
 and for server side handling. Specifically if we later on allow for altern=
ative enrollment protocols in BRSKI-AE and define the discovery approach, i=
t will lead to less confusion to align the naming with the corresponding fu=
nctionality. From that perspective, my gut feeling would be that an integra=
tion into base BRSKI may be more appropriate. On the contrary, it will slow=
 down the process, but somebody stated that there are examples that these c=
hanges have been also done in the past and could be done fast.=20

What do you suggest as way forward?=20

Best regards
Steffen


--
Steffen Fries
Siemens AG, Corporate Technology
mailto:steffen.fries@siemens.com


From nobody Thu Jul 30 09:06:19 2020
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 DD7203A0B5D for <anima@ietfa.amsl.com>; Thu, 30 Jul 2020 09:06:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level: 
X-Spam-Status: No, score=-9.601 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, DKIM_VALID_EF=-0.1, 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 93TW9V86-lBP for <anima@ietfa.amsl.com>; Thu, 30 Jul 2020 09:06:15 -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 1CB063A0B57 for <anima@ietf.org>; Thu, 30 Jul 2020 09:06:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3104; q=dns/txt; s=iport; t=1596125175; x=1597334775; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=XFZFhSr/NNI3ZnTK501FjpItdyuglIBUv9bFnBE5DOc=; b=dUKvOU2Qiuw/wWl5nPEEDObDt+Agi7ZnDz8/tCkRRPXo+9Vnt4MzKksH 9wBiH9S5018TzXBSQYDxqAcQTQMqI/3xhm0Kdy5SVgshW3d4l4+XLi6ZM Oo0Yvzykr8lTuMvucPYClbVH7v67LKQR/qZiFzC8UOaTKy254VofB9aan Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DBBQDR7iJf/xbLJq1gHAEBAQEBAQc?= =?us-ascii?q?BARIBAQQEAQFAgUqDbQEgEiyENYkBh3MlnA0LAQEBDAEBLwQBAYRMAoIvJTg?= =?us-ascii?q?TAgMBAQsBAQUBAQECAQYEbYVohXEBAQEDASNWBQsLGAICIwMCAkYRBhODJoJ?= =?us-ascii?q?dIK95doEyilWBDiqJCIQfggCBEScMEIJNPoQlGIMWM4ItBJAFpgKCaYMKlnU?= =?us-ascii?q?DHoJ7jlCOKZQJmV+DVgIEBgUCFYFqI4FXMxoIGxU7KgGCPj4SGQ2caD8DMDc?= =?us-ascii?q?CBgEHAQEDCZBYAQE?=
X-IronPort-AV: E=Sophos;i="5.75,415,1589241600"; d="scan'208";a="28294910"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 30 Jul 2020 16:06:11 +0000
Received: from [10.61.162.138] ([10.61.162.138]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 06UG6AdC006689 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 30 Jul 2020 16:06:10 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: Eliot Lear <lear@cisco.com>
In-Reply-To: <3f2d1790efb44ac39405a23dc592dd89@siemens.com>
Date: Thu, 30 Jul 2020 18:06:09 +0200
Cc: Michael Richardson <mcr@sandelman.ca>, "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>, Toerless Eckert <tte@cs.fau.de>, "anima@ietf.org" <anima@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2ABF0BD6-8084-46C4-8E96-4772582BDA01@cisco.com>
References: <3f2d1790efb44ac39405a23dc592dd89@siemens.com>
To: "Fries, Steffen" <steffen.fries@siemens.com>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
X-Outbound-SMTP-Client: 10.61.162.138, [10.61.162.138]
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/EmjnCxeu0V_LKtfxhNIQ1Kny5Ao>
Subject: Re: [Anima] Handling of endpoint path names (from BRSKI-AE discussion today)
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, 30 Jul 2020 16:06:18 -0000

Steffen

I enjoyed today=E2=80=99s discussion.  My suggestion is a short document =
that does not CHANGE endpoints but simply creates new ones that have the =
same functionality as the old ones.  That doesn=E2=80=99t require an =
=E2=80=9CUpdates=E2=80=9D header, and based on that I think you might =
even keep these in the same document.  Would people be ok with that?

Eliot

> On 30 Jul 2020, at 17:46, Fries, Steffen <steffen.fries@siemens.com> =
wrote:
>=20
> Hi,
>=20
> Based on the discussion of splitting up the voucher handling endpoint =
naming issues from BRSKI-AE today, I just wanted to ensure I got the way =
forward right.=20
> =46rom the Etherpad discussion I understood Michael that he would not =
be too happy with having a BRSKI update right after BRSKI publication as =
RFC. I think finalizing the discussion on the list was advised.
>=20
> What we discussed in the WG meeting was to have a separate short =
document, basically defining a renaming or alternatively an alias for =
the current endpoints, which allows to keep the current implementations =
as is.=20
> Hence, the draft would relate to all of the endpoints defined in =
section 5 of BRSKI for the domain registrar facing the pledge (and =
potentially also the MASA), which are:=20
> /.well-known/est/requestvoucher	used by pledge to registrar but =
also from registrar to MASA
> /.well-known/est/voucher_status	used by pledge to registrar
> /.well-known/est/requestauditlog	used by registrar to MASA
> /.well-known/est/enrollstatus		used by pledge to registrar
>=20
> =46rom Toerless I understood that he would like to not change the =
current draft as it is already in the final state and rather provide an =
update as separate document.
> =46rom Michael I understood he would not be keen on having a fast =
update for the BRSKI document. At least not for a renaming of the =
defined endpoints. Also the IESG may view this as too fast.=20
> Eliot stated that there are already implementations out there that =
utilize the /est approach. So having aliases could be one way of dealing =
with it, but this would double the endpoints at least for the four =
stated ones above.=20
>=20
> Both approaches have there merits. Having the endpoints distinct from =
the beginning allows a clearer separation of the functionalities, for =
the pledge and for server side handling. Specifically if we later on =
allow for alternative enrollment protocols in BRSKI-AE and define the =
discovery approach, it will lead to less confusion to align the naming =
with the corresponding functionality. =46rom that perspective, my gut =
feeling would be that an integration into base BRSKI may be more =
appropriate. On the contrary, it will slow down the process, but =
somebody stated that there are examples that these changes have been =
also done in the past and could be done fast.=20
>=20
> What do you suggest as way forward?=20
>=20
> Best regards
> Steffen
>=20
>=20
> --
> Steffen Fries
> Siemens AG, Corporate Technology
> mailto:steffen.fries@siemens.com
>=20


From nobody Thu Jul 30 09:11:51 2020
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 7C5A43A0BCB for <anima@ietfa.amsl.com>; Thu, 30 Jul 2020 09:11:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.118
X-Spam-Level: 
X-Spam-Status: No, score=-1.118 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, 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 TexM52xi4uN6 for <anima@ietfa.amsl.com>; Thu, 30 Jul 2020 09:11:47 -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 6AACB3A0BEF for <anima@ietf.org>; Thu, 30 Jul 2020 09:11:47 -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 9FFFA548440; Thu, 30 Jul 2020 18:11:42 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 9A0F9440043; Thu, 30 Jul 2020 18:11:42 +0200 (CEST)
Date: Thu, 30 Jul 2020 18:11:42 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: "Fries, Steffen" <steffen.fries@siemens.com>
Cc: Michael Richardson <mcr@sandelman.ca>, Eliot Lear <lear@cisco.com>, "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>, "anima@ietf.org" <anima@ietf.org>
Message-ID: <20200730161142.GB62130@faui48f.informatik.uni-erlangen.de>
References: <3f2d1790efb44ac39405a23dc592dd89@siemens.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3f2d1790efb44ac39405a23dc592dd89@siemens.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/WH1iknAQXy_6EcoyPsYyZTd610E>
Subject: Re: [Anima] Handling of endpoint path names (from BRSKI-AE discussion today)
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, 30 Jul 2020 16:11:50 -0000

Thanks Steffen

Maybe here is a good logic:

The short document would not need to be an Update as long as we do not want to eliminate
the old /est URLs. 

Aliasing should be easy enough. The main goal of the small document would the be to be
what Michael called an Extension as the bassis for for that does not expect to to demand
EST. Like BRSKI-AE. And the reason for not doing this solely in BRSKI-AE might be
that such other document migth not want to reference all of BRSKI-AE.

I am just making this up as i go as proposals of waht would give us the smoothest rides
hrough the process with the only difference to the likely position of BRSKI-AE authors
being that i would also like to think about the smooth ride for other BRSKI extension documents.

Lets hope others will have even better opinions on the thread.

Cheers
    Toerless

On Thu, Jul 30, 2020 at 03:46:09PM +0000, Fries, Steffen wrote:
> Hi,
> 
> Based on the discussion of splitting up the voucher handling endpoint naming issues from BRSKI-AE today, I just wanted to ensure I got the way forward right. 
> >From the Etherpad discussion I understood Michael that he would not be too happy with having a BRSKI update right after BRSKI publication as RFC. I think finalizing the discussion on the list was advised.
> 
> What we discussed in the WG meeting was to have a separate short document, basically defining a renaming or alternatively an alias for the current endpoints, which allows to keep the current implementations as is. 
> Hence, the draft would relate to all of the endpoints defined in section 5 of BRSKI for the domain registrar facing the pledge (and potentially also the MASA), which are: 
> /.well-known/est/requestvoucher	used by pledge to registrar but also from registrar to MASA
> /.well-known/est/voucher_status	used by pledge to registrar
> /.well-known/est/requestauditlog	used by registrar to MASA
> /.well-known/est/enrollstatus		used by pledge to registrar
> 
> >From Toerless I understood that he would like to not change the current draft as it is already in the final state and rather provide an update as separate document.
> >From Michael I understood he would not be keen on having a fast update for the BRSKI document. At least not for a renaming of the defined endpoints. Also the IESG may view this as too fast. 
> Eliot stated that there are already implementations out there that utilize the /est approach. So having aliases could be one way of dealing with it, but this would double the endpoints at least for the four stated ones above. 
> 
> Both approaches have there merits. Having the endpoints distinct from the beginning allows a clearer separation of the functionalities, for the pledge and for server side handling. Specifically if we later on allow for alternative enrollment protocols in BRSKI-AE and define the discovery approach, it will lead to less confusion to align the naming with the corresponding functionality. From that perspective, my gut feeling would be that an integration into base BRSKI may be more appropriate. On the contrary, it will slow down the process, but somebody stated that there are examples that these changes have been also done in the past and could be done fast. 
> 
> What do you suggest as way forward? 
> 
> Best regards
> Steffen
> 
> 
> --
> Steffen Fries
> Siemens AG, Corporate Technology
> mailto:steffen.fries@siemens.com

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


From nobody Thu Jul 30 09:32:22 2020
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 66E2B3A03ED for <anima@ietfa.amsl.com>; Thu, 30 Jul 2020 09:32:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.118
X-Spam-Level: 
X-Spam-Status: No, score=-1.118 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, 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 kBoxZAZx8pWk for <anima@ietfa.amsl.com>; Thu, 30 Jul 2020 09:32:16 -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 9C0A13A0141 for <anima@ietf.org>; Thu, 30 Jul 2020 09:32:16 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id E9951548068; Thu, 30 Jul 2020 18:32:11 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id DD02C440043; Thu, 30 Jul 2020 18:32:11 +0200 (CEST)
Date: Thu, 30 Jul 2020 18:32:11 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Eliot Lear <lear@cisco.com>
Cc: "Fries, Steffen" <steffen.fries@siemens.com>, Michael Richardson <mcr@sandelman.ca>, "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>, "anima@ietf.org" <anima@ietf.org>
Message-ID: <20200730163211.GC62130@faui48f.informatik.uni-erlangen.de>
References: <3f2d1790efb44ac39405a23dc592dd89@siemens.com> <2ABF0BD6-8084-46C4-8E96-4772582BDA01@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2ABF0BD6-8084-46C4-8E96-4772582BDA01@cisco.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/VtoqBjBjGLMnuAan6Ix4DIPCdg8>
Subject: Re: [Anima] Handling of endpoint path names (from BRSKI-AE discussion today)
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, 30 Jul 2020 16:32:19 -0000

On Thu, Jul 30, 2020 at 06:06:09PM +0200, Eliot Lear wrote:
> Steffen
> 
> I enjoyed today???s discussion.  My suggestion is a short document that does not CHANGE endpoints but simply creates new ones that have the same functionality as the old ones.  That doesn???t require an ???Updates??? header, and based on that I think you might even keep these in the same document.  Would people be ok with that?

Right. So the question is keep it in the document or put it into a separate
small one. The small one would allow other derivative work not to have to
have BRSKI-AE as a normative reference, which may be better if its got nothing
to do with BRSKI-AE.

I guess we can delay the decision up to the point when we do see such other
derivative work coming up, and then decide whether to separate out the
new /brski naming from the doc. As long as there is no such additional doc,
we keep things in BRSKI-AE as they are right now.

Cheers
    Toerless

> Eliot
> 
> > On 30 Jul 2020, at 17:46, Fries, Steffen <steffen.fries@siemens.com> wrote:
> > 
> > Hi,
> > 
> > Based on the discussion of splitting up the voucher handling endpoint naming issues from BRSKI-AE today, I just wanted to ensure I got the way forward right. 
> > From the Etherpad discussion I understood Michael that he would not be too happy with having a BRSKI update right after BRSKI publication as RFC. I think finalizing the discussion on the list was advised.
> > 
> > What we discussed in the WG meeting was to have a separate short document, basically defining a renaming or alternatively an alias for the current endpoints, which allows to keep the current implementations as is. 
> > Hence, the draft would relate to all of the endpoints defined in section 5 of BRSKI for the domain registrar facing the pledge (and potentially also the MASA), which are: 
> > /.well-known/est/requestvoucher	used by pledge to registrar but also from registrar to MASA
> > /.well-known/est/voucher_status	used by pledge to registrar
> > /.well-known/est/requestauditlog	used by registrar to MASA
> > /.well-known/est/enrollstatus		used by pledge to registrar
> > 
> > From Toerless I understood that he would like to not change the current draft as it is already in the final state and rather provide an update as separate document.
> > From Michael I understood he would not be keen on having a fast update for the BRSKI document. At least not for a renaming of the defined endpoints. Also the IESG may view this as too fast. 
> > Eliot stated that there are already implementations out there that utilize the /est approach. So having aliases could be one way of dealing with it, but this would double the endpoints at least for the four stated ones above. 
> > 
> > Both approaches have there merits. Having the endpoints distinct from the beginning allows a clearer separation of the functionalities, for the pledge and for server side handling. Specifically if we later on allow for alternative enrollment protocols in BRSKI-AE and define the discovery approach, it will lead to less confusion to align the naming with the corresponding functionality. From that perspective, my gut feeling would be that an integration into base BRSKI may be more appropriate. On the contrary, it will slow down the process, but somebody stated that there are examples that these changes have been also done in the past and could be done fast. 
> > 
> > What do you suggest as way forward? 
> > 
> > Best regards
> > Steffen
> > 
> > 
> > --
> > Steffen Fries
> > Siemens AG, Corporate Technology
> > mailto:steffen.fries@siemens.com
> > 

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


From nobody Thu Jul 30 10:14:18 2020
Return-Path: <hendrik.brockhaus@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 920E43A0F25 for <anima@ietfa.amsl.com>; Thu, 30 Jul 2020 10:14:15 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=siemens.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ASkJOGYLVPC8 for <anima@ietfa.amsl.com>; Thu, 30 Jul 2020 10:14:13 -0700 (PDT)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60055.outbound.protection.outlook.com [40.107.6.55]) (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 0B25B3A0EC3 for <anima@ietf.org>; Thu, 30 Jul 2020 10:14:09 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Sfpm+ibCrjbBu9wsEbMzZKdQeZIgHXXx9oZl7IusoXUnI5CYdUiTeNSkyQ5LztihlPvMoj77Ao3R0TB1PbWb4UYHLeB5erxrbuMlBOCpZz08zRMFPnf5WZLp3OL5lK73t9rbJoPYts0StXj5aZqrfEKcagghCNJRmaPkovxB+vlmjYDFPzt/ZIMa+F29/ObbT2VZnRkahL+/AlBm9B0FvBteOKX7xQLor+HXfyGX3V5AX7W/0nlOySwim60l+mpMr5NmBgFOHcd26mvBFKVSdSptY1kVJDwBXA8T1EzsfAnixXTawdyoISswEVjkSIdKZlNHndGwIZGn0Kec0vsR4w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Znyg4gOkenD03iZSbVPtIqbIVEMKksv4eGkZxTL3WXg=; b=IoM64d/Fcji6/UltRtfMZd77MxuqioaQcOPngrly3cuW82qNr6bXDRh/DDQFFBRSDGJ4x04/N6ZeNJbJjxrThv+mqPWcMWCnhVNtyBbyqqO/V31qbgxNoWFiAF9R41Q2EB6sr+xMYZkxyvjgu8+oashcmuodmJtJ7fDQRnk6CYaN/3aJj2oKiyNsJFN47OGveWZT/KP9rPy9TwD9zD4LooFfwM92GN4VfBuLaSgTtN1ORHHBRij7+uF1p6xTIW+lzq+WO/aVulHWYXiOliaoUY/XVxxfW7ppgePIioLZM1wwa1rcvRJwyk3bvd5HZgzszhJfN+sJsQJJILTeAVBbuQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=siemens.com; dmarc=pass action=none header.from=siemens.com; dkim=pass header.d=siemens.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=siemens.onmicrosoft.com; s=selector1-siemens-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Znyg4gOkenD03iZSbVPtIqbIVEMKksv4eGkZxTL3WXg=; b=c4aKzIalHxpK9BMIL9r7+ELM9jL4Dc6wugboCJJW9zPIoIXKUWAk7Gl5Ph59HpRwgP+yhXHeZTtb26NwkWI6kJRz3kP2oIfkYMDFnHiEjZLiSui13LnWxZ+e+/DA5n7ObZmR5Za/Qgx5N+vR/TFWLKLLKrCMUXpha4hKoT0sr/0=
Received: from DB8PR10MB3162.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:10:112::10) by DB8PR10MB3130.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:10:f9::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3239.16; Thu, 30 Jul 2020 17:14:07 +0000
Received: from DB8PR10MB3162.EURPRD10.PROD.OUTLOOK.COM ([fe80::4155:d977:e100:6be8]) by DB8PR10MB3162.EURPRD10.PROD.OUTLOOK.COM ([fe80::4155:d977:e100:6be8%2]) with mapi id 15.20.3239.018; Thu, 30 Jul 2020 17:14:07 +0000
From: "Brockhaus, Hendrik" <hendrik.brockhaus@siemens.com>
To: Toerless Eckert <tte@cs.fau.de>
CC: "steffen.fries@siemens.com" <steffen.fries@siemens.com>, Michael Richardson <mcr@sandelman.ca>, "anima@ietf.org" <anima@ietf.org>, Eliot Lear <lear@cisco.com>
Thread-Topic: Handling of endpoint path names (from BRSKI-AE discussion today)
Thread-Index: AQHWZo79rZ1/3jVW+kuZRNM0r6HX+akgWvpA
Content-Class: 
Date: Thu, 30 Jul 2020 17:14:07 +0000
Message-ID: <DB8PR10MB31628CAD0634A031B19C3AD6FE710@DB8PR10MB3162.EURPRD10.PROD.OUTLOOK.COM>
References: <3f2d1790efb44ac39405a23dc592dd89@siemens.com> <2ABF0BD6-8084-46C4-8E96-4772582BDA01@cisco.com> <20200730163211.GC62130@faui48f.informatik.uni-erlangen.de>
In-Reply-To: <20200730163211.GC62130@faui48f.informatik.uni-erlangen.de>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Enabled=true; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SetDate=2020-07-30T17:14:06Z;  MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Method=Standard; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_Name=restricted-default; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_SiteId=38ae3bcd-9579-4fd4-adda-b42e1495d55a; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ActionId=03300553-8f21-45eb-830a-aa358ef1af00; MSIP_Label_a59b6cd5-d141-4a33-8bf1-0ca04484304f_ContentBits=0
document_confidentiality: Restricted
authentication-results: cs.fau.de; dkim=none (message not signed) header.d=none;cs.fau.de; dmarc=none action=none header.from=siemens.com;
x-originating-ip: [195.145.170.189]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 7bb3e57e-c763-4a70-161b-08d834abf7f4
x-ms-traffictypediagnostic: DB8PR10MB3130:
x-ld-processed: 38ae3bcd-9579-4fd4-adda-b42e1495d55a,ExtAddr
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <DB8PR10MB313055386D653F6D5D4FFB30FE710@DB8PR10MB3130.EURPRD10.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 6qCOeybvEekwl4OwUPk3UwgGT/MPytDT7scH7ukvvxvHFc9NeUKldfKRR1cUtptmsiAGSxrKiSvBwQcoLdHLiadujhmlknIZ67ENLRmyVEb+IVqrrm0MCXypBn1Hw866YTC3VyOUHbbHWaD1gE5Ds0dGGql06JViUyx8fepjtdLCxgmvIipq0HimC3Oymh7hTdDktBasJM9VvBz7gYOj1TY84OFvPhfdFlKSkDKnKd57OLr+ekvpbEF2F6gVOToWYOP9NYsKgW+85TQWXfm6634XqGj/pTqwJhrVB5XyJkp8UpxsmUoYNU5K7YdZVRKvgbdJASpebvVxDH3iHTP4gXoWp6azY7rL/20RwJRTNvsuVNGOwzorkXLYufbBtdba
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DB8PR10MB3162.EURPRD10.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(366004)(39860400002)(346002)(396003)(136003)(376002)(83380400001)(4326008)(66574015)(7696005)(8936002)(316002)(9686003)(52536014)(71200400001)(86362001)(55016002)(6506007)(53546011)(54906003)(5660300002)(26005)(66446008)(33656002)(76116006)(478600001)(6916009)(8676002)(2906002)(186003)(66946007)(66556008)(64756008)(66476007)(166863002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: 20x+S7gZvKYcpKtlCueb5oF7FKWqpnN+yT5HPY6XIyy/pt/x8U5ItV9QQOedddCFyyYvDYq0U+04rMuKFB5O3pW5XZNqW32s/dFfJqnN0f7ZkztVRgbpmZcm4EQCSMsnHnBwgqgyBIwWAaT6wzx3PGCVDbmELS4zbUJP/FC17vTa/z+fls/i/4328c2hxhUrd+F5hzOj1dip1gvR5AURi0vE1IN9iIliWWdxwg53nLoZiHQ/ZuP+9Oj9c9A168cTzKa6Dqc+kBA1sTIB9RlaNg07D9ftitpAp48MHoqDcUQaVD1ATtl1d9usdv57xpcs8SFTvt4SXjgR3oJTB5/RPJWJ+R7Mc35ebiOLZOwyFUIBjYo/FxIAu0DxuY0MU2Mj1MCM+JHB0IHwkK/BYImO3XyYQF9Zc8qi7117ZU9yam4rcKB3zbn6iApajkMgwTdbDUYIdk0n2qMPXA+ozkyHwZ5LLcZY5uLm/xdCwEOVgPPLFexG220bkRtNUzaILIiLs50qMLvJAoBBhRYYsbHY0QhQJVy8Zo5ar+ouhgBYwuQhs6boXrAgY9pGtxeZyWBpm+PGFsMtRefKFIYbgpSWfCfj66b0Z/Nji1sz+GYVAjJcz7bPzmCLJwriIeABBU1x3fDPbYDNBmkm90cwHexGbQ==
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: siemens.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DB8PR10MB3162.EURPRD10.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 7bb3e57e-c763-4a70-161b-08d834abf7f4
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Jul 2020 17:14:07.6079 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 38ae3bcd-9579-4fd4-adda-b42e1495d55a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: fzD/R3XJMqijCViPoYv8KQt51pvUtaJ/yVq894Ufv9+l2FmsI0924XjMJMHGRNGrc1SPUtIhFzLBPGEZDUUzrNkETvl5xCyhnYaGokKoMg0=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB8PR10MB3130
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/moE_l_YHt2QO6Lt58pNlM-InSME>
Subject: Re: [Anima] Handling of endpoint path names (from BRSKI-AE discussion today)
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, 30 Jul 2020 17:14:17 -0000

Toerless

I have one question to better make up my mind.
How long do you thing would the change to the BRSKI document delay the appr=
oval process?=20
Finally this change is quite easy to explain. And from my point of view, do=
ing this change to BRSKI before approval, would be, from a standardization =
point of view, the clearest solution.

Hendrik

> -----Urspr=FCngliche Nachricht-----
> Von: Toerless Eckert <tte@cs.fau.de>
> Gesendet: Donnerstag, 30. Juli 2020 18:32
> An: Eliot Lear <lear@cisco.com>
> Cc: Fries, Steffen (CT RDA CST) <steffen.fries@siemens.com>; Michael
> Richardson <mcr@sandelman.ca>; Brockhaus, Hendrik (CT RDA CST SEA-DE)
> <hendrik.brockhaus@siemens.com>; anima@ietf.org
> Betreff: Re: Handling of endpoint path names (from BRSKI-AE discussion to=
day)
>=20
> On Thu, Jul 30, 2020 at 06:06:09PM +0200, Eliot Lear wrote:
> > Steffen
> >
> > I enjoyed today???s discussion.  My suggestion is a short document that=
 does
> not CHANGE endpoints but simply creates new ones that have the same
> functionality as the old ones.  That doesn???t require an ???Updates??? h=
eader,
> and based on that I think you might even keep these in the same document.
> Would people be ok with that?
>=20
> Right. So the question is keep it in the document or put it into a separa=
te small
> one. The small one would allow other derivative work not to have to have
> BRSKI-AE as a normative reference, which may be better if its got nothing=
 to do
> with BRSKI-AE.
>=20
> I guess we can delay the decision up to the point when we do see such oth=
er
> derivative work coming up, and then decide whether to separate out the ne=
w
> /brski naming from the doc. As long as there is no such additional doc, w=
e keep
> things in BRSKI-AE as they are right now.
>=20
> Cheers
>     Toerless
>=20
> > Eliot
> >
> > > On 30 Jul 2020, at 17:46, Fries, Steffen <steffen.fries@siemens.com> =
wrote:
> > >
> > > Hi,
> > >
> > > Based on the discussion of splitting up the voucher handling endpoint
> naming issues from BRSKI-AE today, I just wanted to ensure I got the way
> forward right.
> > > From the Etherpad discussion I understood Michael that he would not b=
e
> too happy with having a BRSKI update right after BRSKI publication as RFC=
. I
> think finalizing the discussion on the list was advised.
> > >
> > > What we discussed in the WG meeting was to have a separate short
> document, basically defining a renaming or alternatively an alias for the
> current endpoints, which allows to keep the current implementations as is=
.
> > > Hence, the draft would relate to all of the endpoints defined in sect=
ion 5 of
> BRSKI for the domain registrar facing the pledge (and potentially also th=
e
> MASA), which are:
> > > /.well-known/est/requestvoucher	used by pledge to registrar but also
> from registrar to MASA
> > > /.well-known/est/voucher_status	used by pledge to registrar
> > > /.well-known/est/requestauditlog	used by registrar to MASA
> > > /.well-known/est/enrollstatus		used by pledge to registrar
> > >
> > > From Toerless I understood that he would like to not change the curre=
nt
> draft as it is already in the final state and rather provide an update as=
 separate
> document.
> > > From Michael I understood he would not be keen on having a fast updat=
e
> for the BRSKI document. At least not for a renaming of the defined endpoi=
nts.
> Also the IESG may view this as too fast.
> > > Eliot stated that there are already implementations out there that ut=
ilize
> the /est approach. So having aliases could be one way of dealing with it,=
 but
> this would double the endpoints at least for the four stated ones above.
> > >
> > > Both approaches have there merits. Having the endpoints distinct from=
 the
> beginning allows a clearer separation of the functionalities, for the ple=
dge and
> for server side handling. Specifically if we later on allow for alternati=
ve
> enrollment protocols in BRSKI-AE and define the discovery approach, it wi=
ll lead
> to less confusion to align the naming with the corresponding functionalit=
y. From
> that perspective, my gut feeling would be that an integration into base B=
RSKI
> may be more appropriate. On the contrary, it will slow down the process, =
but
> somebody stated that there are examples that these changes have been also
> done in the past and could be done fast.
> > >
> > > What do you suggest as way forward?
> > >
> > > Best regards
> > > Steffen
> > >
> > >
> > > --
> > > Steffen Fries
> > > Siemens AG, Corporate Technology
> > > mailto:steffen.fries@siemens.com
> > >
>=20
> --
> ---
> tte@cs.fau.de


From nobody Thu Jul 30 13:59:15 2020
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 4CFFE3A0CB9 for <anima@ietfa.amsl.com>; Thu, 30 Jul 2020 13:59:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, 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 24dqSZBNAO0K for <anima@ietfa.amsl.com>; Thu, 30 Jul 2020 13:59:09 -0700 (PDT)
Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) (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 D49533A0CBE for <anima@ietf.org>; Thu, 30 Jul 2020 13:59:09 -0700 (PDT)
Received: by mail-pj1-x102f.google.com with SMTP id t15so5684562pjq.5 for <anima@ietf.org>; Thu, 30 Jul 2020 13:59:09 -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=NpSZelfnD1bFYVkW4qpzVeGhP5ZzEXwieap53GuuDtg=; b=SQ7s2KsPT5ZqUTkEvU5TsVGzB5PWyiyaHkp9eBO5ElXZ/Nsdh4RfhQqt2yRL4SYUmm YLTblncwCluHSmlPBX7CY/ms8CG4qKf0kMbcDIY5J98O7LIDtZhtqjuIlMel5MXtiOE+ 4v+h+TKaSIwkhr3MYrycjcouGbPORhCrk1deByUhByS2JdSZbwmPGaUX2tx9idqsFGJC Uj1WEy0FrDpPbLZHFkaGdYAvoWGIgANrxWLH5lwRsPtOhCO6C0rtUnJXLZXTDvSc2RyY bbxK7ke6brI0Tvy0v+GcoLL07sZ4nZmkTHGVde9kRpoP19RqzbZj0sG8gpnKhfnhqGmG SeCg==
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=NpSZelfnD1bFYVkW4qpzVeGhP5ZzEXwieap53GuuDtg=; b=kiWN/wtsX6VvKAIgX1YZ3VCf8d3HmFE4xPATXnS+1eBtJCaxBe0V4lpyueDRPmlMrM RMQ4V4CII/WvfqjuhbzUSZK41GuDwQquNcdx4cYB56hAvP1szryiSNQ/PBN9ViwhSOKh Holy89MfX/musHOxuk3I3HKwN/idhAtF62QEG1itqoLI0i45hWvHjU4CdBt1h69NFDV8 ZMLACPh4Iiq7v6xWF0qWQx/16cwNVQ1QuOZ/NR0hCtcr4jse/9d8BDYvJ8cR7J5Nkedk VZRcmuM0PTq/khJ33IhHiicL9HFwfRmVH9XpJfz1h2KIlEJcwSCAqvflIb0NKPd/ML/E PpIA==
X-Gm-Message-State: AOAM532XsPVvH64/weaJvVvXtUTYPEsKU6YwUuzo8MKXlA5UKojhy7Rz ecci6OLY6uQT8RN79pYU/svVtclodZ0=
X-Google-Smtp-Source: ABdhPJxnGle9oAB8C4Ph4eEempxdEol03s3/vOL4W3pL7vPYsCzjJZXV0iDeSecLiAbgw5TY4x3Z3Q==
X-Received: by 2002:a63:7802:: with SMTP id t2mr669615pgc.421.1596142748859; Thu, 30 Jul 2020 13:59:08 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.139.192]) by smtp.gmail.com with ESMTPSA id w2sm6487266pjt.19.2020.07.30.13.59.07 for <anima@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Jul 2020 13:59:08 -0700 (PDT)
To: anima@ietf.org
References: <3f2d1790efb44ac39405a23dc592dd89@siemens.com> <2ABF0BD6-8084-46C4-8E96-4772582BDA01@cisco.com> <20200730163211.GC62130@faui48f.informatik.uni-erlangen.de> <DB8PR10MB31628CAD0634A031B19C3AD6FE710@DB8PR10MB3162.EURPRD10.PROD.OUTLOOK.COM>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <a9c1fe8a-29a7-5cf6-6672-b82b0c5bb275@gmail.com>
Date: Fri, 31 Jul 2020 08:59:05 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <DB8PR10MB31628CAD0634A031B19C3AD6FE710@DB8PR10MB3162.EURPRD10.PROD.OUTLOOK.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/3Ov2s8XxQ6pnQMp6PTd9_yDc-D0>
Subject: Re: [Anima] Handling of endpoint path names (from BRSKI-AE discussion today)
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, 30 Jul 2020 20:59:14 -0000

On 31-Jul-20 05:14, Brockhaus, Hendrik wrote:
> Toerless
>=20
> I have one question to better make up my mind.
> How long do you thing would the change to the BRSKI document delay the =
approval process?=20

That is utterly unpredictable. Since this is a real technical change, we'=
d need the chairs
to formally establish WG consensus and then, as far as I can tell, we hav=
e invalidated the
IETF Last Call and so we're back to that and a Security Area review etc. =
After recent
experience, I have no idea whatever how long that would take.

So I *strongly* believe that we should make a separate document. It's an =
extension, not
a change, so it really doesn't need an Updates: tag.

   Brian

> Finally this change is quite easy to explain. And from my point of view=
, doing this change to BRSKI before approval, would be, from a standardiz=
ation point of view, the clearest solution.
>=20
> Hendrik
>=20
>> -----Urspr=C3=BCngliche Nachricht-----
>> Von: Toerless Eckert <tte@cs.fau.de>
>> Gesendet: Donnerstag, 30. Juli 2020 18:32
>> An: Eliot Lear <lear@cisco.com>
>> Cc: Fries, Steffen (CT RDA CST) <steffen.fries@siemens.com>; Michael
>> Richardson <mcr@sandelman.ca>; Brockhaus, Hendrik (CT RDA CST SEA-DE)
>> <hendrik.brockhaus@siemens.com>; anima@ietf.org
>> Betreff: Re: Handling of endpoint path names (from BRSKI-AE discussion=
 today)
>>
>> On Thu, Jul 30, 2020 at 06:06:09PM +0200, Eliot Lear wrote:
>>> Steffen
>>>
>>> I enjoyed today???s discussion.  My suggestion is a short document th=
at does
>> not CHANGE endpoints but simply creates new ones that have the same
>> functionality as the old ones.  That doesn???t require an ???Updates??=
? header,
>> and based on that I think you might even keep these in the same docume=
nt.
>> Would people be ok with that?
>>
>> Right. So the question is keep it in the document or put it into a sep=
arate small
>> one. The small one would allow other derivative work not to have to ha=
ve
>> BRSKI-AE as a normative reference, which may be better if its got noth=
ing to do
>> with BRSKI-AE.
>>
>> I guess we can delay the decision up to the point when we do see such =
other
>> derivative work coming up, and then decide whether to separate out the=
 new
>> /brski naming from the doc. As long as there is no such additional doc=
, we keep
>> things in BRSKI-AE as they are right now.
>>
>> Cheers
>>     Toerless
>>
>>> Eliot
>>>
>>>> On 30 Jul 2020, at 17:46, Fries, Steffen <steffen.fries@siemens.com>=
 wrote:
>>>>
>>>> Hi,
>>>>
>>>> Based on the discussion of splitting up the voucher handling endpoin=
t
>> naming issues from BRSKI-AE today, I just wanted to ensure I got the w=
ay
>> forward right.
>>>> From the Etherpad discussion I understood Michael that he would not =
be
>> too happy with having a BRSKI update right after BRSKI publication as =
RFC.. I
>> think finalizing the discussion on the list was advised.
>>>>
>>>> What we discussed in the WG meeting was to have a separate short
>> document, basically defining a renaming or alternatively an alias for =
the
>> current endpoints, which allows to keep the current implementations as=
 is.
>>>> Hence, the draft would relate to all of the endpoints defined in sec=
tion 5 of
>> BRSKI for the domain registrar facing the pledge (and potentially also=
 the
>> MASA), which are:
>>>> /.well-known/est/requestvoucher	used by pledge to registrar but also=

>> from registrar to MASA
>>>> /.well-known/est/voucher_status	used by pledge to registrar
>>>> /.well-known/est/requestauditlog	used by registrar to MASA
>>>> /.well-known/est/enrollstatus		used by pledge to registrar
>>>>
>>>> From Toerless I understood that he would like to not change the curr=
ent
>> draft as it is already in the final state and rather provide an update=
 as separate
>> document.
>>>> From Michael I understood he would not be keen on having a fast upda=
te
>> for the BRSKI document. At least not for a renaming of the defined end=
points.
>> Also the IESG may view this as too fast.
>>>> Eliot stated that there are already implementations out there that u=
tilize
>> the /est approach. So having aliases could be one way of dealing with =
it, but
>> this would double the endpoints at least for the four stated ones abov=
e.
>>>>
>>>> Both approaches have there merits. Having the endpoints distinct fro=
m the
>> beginning allows a clearer separation of the functionalities, for the =
pledge and
>> for server side handling. Specifically if we later on allow for altern=
ative
>> enrollment protocols in BRSKI-AE and define the discovery approach, it=
 will lead
>> to less confusion to align the naming with the corresponding functiona=
lity. From
>> that perspective, my gut feeling would be that an integration into bas=
e BRSKI
>> may be more appropriate. On the contrary, it will slow down the proces=
s, but
>> somebody stated that there are examples that these changes have been a=
lso
>> done in the past and could be done fast.
>>>>
>>>> What do you suggest as way forward?
>>>>
>>>> Best regards
>>>> Steffen
>>>>
>>>>
>>>> --
>>>> Steffen Fries
>>>> Siemens AG, Corporate Technology
>>>> mailto:steffen.fries@siemens.com
>>>>
>>
>> --
>> ---
>> tte@cs.fau.de
>=20
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima
>=20

