t that it's not in scope
> for this particular draft.
In other words, more IPv4-inspired L2-tricks to maintain the illusion there
is a big-blue cable with AUI taps on it. And continued inability to see L2
switches, or creatively route around L2 failures :-)
--
Michael Richardson , Sandelman
, or
does this mean it uses L2 technologies like MACSEC to create a tunnel
for L3 packets?
i.e. does L3 multicast appear to just work because it more layer-2 tricks?
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP
OID 1.3.6.1.4.1.46930.2, but will check for both in the Registrar
for a few months. (This likely means reworking many example/test IDevIDs over
time)}
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
ganathan
>> >
>> >
>>
>> --
>> M. Ranganathan
>> ___
>> Anima mailing list
>> Anima@ietf.org
>> https://www.ietf.org/mailman/listinfo/anima
> __
guess the goal is not to
forget it, but not to go down a rathole.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman
r than rfc822Name SANs, and I don't think we
ever want more than one.
I would strongly suggest that maybe we want to do this with CBOR instead.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
added the "reviewer-agrees" label (if github allows), or at least a THUMBS UP
(which I'm sure github will allow), or you can unicast us.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Descriptio
> something about the consequences of a poor random source. It does not
> need to be a comprehensive as the section dealing with setting time.
I've expanded issue #91:
https://github.com/anima-wg/anima-bootstrap/issues/91
>
> Minor Concerns:
next email.
--
Michael Richardson ,
Max Pritikin (pritikin) wrote:
> > On Dec 11, 2018, at 3:23 PM, Michael Richardson
> > wrote:
> >
> >
> > Panos Kampanakis (pkampana) wrote:
> >> I was assuming it was mandatory in the current draft, but I was wrong. As
> >> you sugges
u agree with the key.
You don't know, so you hit ^C.
So, that's all. We don't intend to issue certificates... yet.
I'm also asking if there is some use case where the client might legitimate
need the list of trust anchors (/cacerts request) in order so that it can...?
(I couldn't think of a use case
henticated /crt and /att? We can certainly add that.
I'd like to add this.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima mailing list
Anima@ietf.org
https://www.ietf.org/m
glad that we agree that it should be consistent.
I'm not convinced it's worth having unsigned pledge requests at all.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima mailin
ething in EST-COAPS to explain that we do
not see a use case for replying to /crts and /att for clients which are not
recognized. Is 401 (4.01) or 403 (4.03) more appropriate do you think?
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sa
that it should be restricted. Partly, I'm just not sure where the
text should go, or if it needs to be said at all.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima maili
w the name of the operator.
Note that the later info probably is revealed just by doing the TLS
handshake.
I think that they should be restricted in general, but I'm concerned that
there might be some situation I've missed.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT
document that anything of the pledge requests goes
upwards.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima
Thank you Russ!
I will turn your comments into issues, attempting to de-duplicate against
what we already have.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima mailing
ed artifact
+is include in a base64 format. It is not illegal for attributes
+unknown to a registrar to be included by the pledge.
+
+
+ +-- pledge-voucher-request? binary
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
ity'
+ assertion and associated 'proximity-registrar-cert' need to be
+ verified to be correct.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima mailing list
An
ly.
My sense in writing the words was that there were more words needed.
But I didn't know what else I could nail down scope-wise, so I stopped.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima
Brian E Carpenter wrote:
>> The authors seriously believe that this will result in an attempt to
>> boil the ocean. Yes, BRSKI is exciting for many and opens many doors,
>> but in the context of the *ANIMA* Charter, we strongly think that this
>> document should leave the oceans
ams other than what your IT department
expects you to use for email.}
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima
new protocol in the form of extensions to 8366
processing. I think it also requires the Registrar to contact the OASA
(overriding the MASA URL in the IDevID), but maybe you have another idea.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
si
, leaving the IDevID also available. This seems
mechanically easy, but seems to open many issues.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@sandelman.ca http://www.s
f we do it quickly. Destinguishing between arrays of 1-element
and single-items isn't that difficult in the serializations we have.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@
t's a bug that the MASA can be used to prevent resale.
I'd love to resolve the situation, but I don't know how.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima mailing list
Anima
serial-number is pretty
critical. It goes into the certificate and the MASA uses it as it's primary
key.
So I'm not really sure how to proceed with this comment.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
De
the Reply-To.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@sandelman.ca http://www.sandelman.ca/ | ruby on rails[
--
Michael Richardson , Sandelma
t to
renew the liason process from their end.
Rüst will be speaking at the https://iotsfconference.com/.
I am also presenting, my slides are at:
http://www.sandelman.ca/SSW/talks/iotsf2018-brski/
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael
Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@sandelman.ca http://www.sandelman.ca/| ruby on rails[
--
Michael Richardson , Sandelman Software Works
-=
hi, is there any progress on this?
Additionally, I thought that I asked for an early allocation of
id-mod-MASAURLExtn2016(TBD) from the pkix(7) id-mod(0) Registry.
this is for BRSKI, section 7.2.
Michael Richardson wrote:
> WG chairs, would you please consider asking Ignas and I
ed
devices. Supply chain integration ("know your customer") is an
additional step that MASA providers and device vendors can explore.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
3, where
it turned to micromanagement...}
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima
and while we can use a private CT for now, it would be better if we could
sort this out in the next 2 or 3 weeks!
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima mai
operations if we think it's a good idea to let
the connection persist. (Caveat, we might actually want to log the telemetry
status operation, and perhaps we always return 200 for that)
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
a document
collecting experiences.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima
aying, let's not invent a problem before we understand who actually
has the problem and make sure that the people who can solve the problem
are at our table.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima
ip-to-holding-company.
Holding company leases to end user for period of time. End user identity
is never communicated back, and might be very much pseudonymous.
I'm thinking about car-rentals, hotel rooms (full of devices), ...
--
] Never tell me the odds! | ipv6
a public
IPv4 and/or IPv6 so that we can get traffic to you.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman
sed.
I guess that extension could go into this document.
If 6tisch, then it would use enhanced beacons.
If something else, TBD.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
the APIs that we need to
make it deployable.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima
nt could have better text here.
At one point we discussed an operational considerations document.
Is that really what you are asking for?
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_
to do it
correctly sooner.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima
lain things more?
We call the owner's trust controller the "Registrar", or sometimes the
Join-Registrar/Coordinator. I don't mind calling it a trust controller, but
maybe your term has a different meaning.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
.
What we are doing is making it clear that the tractor is actually owned,
and not p0wned. However, I'm not sure that BRSKI has a value for large
devices with real user interfaces. Maybe it has value for implements though.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
s
| ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@sandelman.ca http://www.sandelman.ca/| ruby on rails[
signature.asc
Description: PGP signature
___
Anima mailing l
s, we do not say how they are used.
>> This is a pretty important question and we have discussed it at
>> length. I remain concerned, but as far as I can see, we have this
>> problem already.
> if i understand correctly, it creates a new problem, nee
Brian E Carpenter wrote:
> Discussion welcome, perhaps on int-a...@ietf.org.
okay, I'll go read the document if it's relevant... but you CC'ed here is
the ACP a limited domain?
Or does ANIMA make it more practical in some way to support limited domains?
--
Michael Richard
rmative way of doing things — the conventions
> we use for this may evolve faster than the rest of the technical
> content of draft-ietf-core-sid.
I don't want a prescription either, but rather a BCP that evolves.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting
|
| 100,000 | 1,000,000,000 | Specification Required |
+-+---++
^-- seem to be too many zeros
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
internet-dra...@ietf.org wrote:
> A new version of I-D, draft-ietf-anima-constrained-voucher-02.txt has
> been successfully submitted by Michael Richardson and posted to the
> IETF repository.
> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-anima-constra
internet-dra...@ietf.org wrote:
> A new version of I-D, draft-ietf-anima-constrained-voucher-01.txt
> has been successfully submitted by Michael Richardson and posted to the
> IETF repository.
> Diff:
https://www.ietf.org/rfcdiff?url2=draft-ietf-anima
H48 after
all IANA actions. (I think some of them are already done in 8366 actually)
> (I didn’t find a ticket system active for this draft; so submitting
> this one directly to the list. I can collect further remarks in an
> email and send at some later time.)
it's on github,
Thanks for careful read that revealed this point.
I've popped your email into an issue:
https://github.com/anima-wg/anima-bootstrap/issues/71
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
em. We don't need the
> sentence as grounding for that.)
I think that the intent is to say that the ASA will have a model of itself.
I think that it would be better to say that.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sande
on,
then they probably meant to do something very specific.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@sandelman.ca http://www.sande
SKI to bootstrap the other LDevIDs, but rather the ACP for
the physical devices would provide a mechanism by which virtual routers would
be created for customers)
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Softwa
the domain, I think you mean to
say, "which interface on a node" is a member of the domain... ?)
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima mailing list
key, while constrained vouchers are
(optionally) pinned to a Raw Public Key.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@sandelman.ca http://www.sandelman.ca
ut for clarity.
okay, I'll add a note about that.
https://github.com/anima-wg/constrained-voucher/commit/6d274f13e3c553efc714c0f06c195f924ad880ff
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works|
a datacenter to find their
partners in adjacent cabinet B. Yes, there might be a 100G fiber between
them... but it might be mis-installed, and/or the lambdas might be wrong,
etc.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelma
ins registrar. E.g: verify some
> domains email, credit-card number, ... something easily
> automated and good enough to track back the bad guy with enough
> likelihood.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, S
I should post under correct name)
How to pick the PANID is not specified yet. Mostly the same as picking an
SSID.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@san
| ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@sandelman.ca http://www.sandelman.ca/| ruby on rails[
signature.asc
Description: PGP signature
___
Anima maili
odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@sandelman.ca http://www.sandelman.ca/| ruby on rails[
signature.asc
Description: PGP signature
___
etwork.
So please explain.
> On 12.07.18 17:12, Michael Richardson wrote:
> Eliot Lear wrote:
>> involved. What a manufacturer wants to avoid is a pledge joining a
>> network where the MASA just does the logging and does no validation,
>> withou
and other protocols don't just use a certificate, but they use
the related private key to sign part of the transaction.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@san
") that is different from the MASA's desire.
The MASA *is* the expression manufacturer's desire.
If the manufacturer has sales channel information that indicates the Pledge
is on the wrong network, it should not issue a voucher.
So the situation you describe makes no sense to me.
--
Michael Ri
the device a second time.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@sandelman.ca http://www.sandelman.ca/| ruby on rails[
--
Michael Richardson , Sandelman Software
This announcement can be within the same message as the ACP
> | announcement detailed in [I-D.ietf-anima-autonomic-control-plane].
> The optional IPinIP proxy as described in Appendix C requires
> the following extension to the syntax of [GRASP]:
We are removing Appendix C.
l references to IPPROTO_IPV6 from the normative text,
and also the IPPROTO_UDP, since CoAP version is another draft.
2) We used the //= notation to make it clear that transport-proto
was an extension point. We also threw in the $...
--
Michael Richardson , Sandelman Software Works
-= IPv6 Io
Brian E Carpenter wrote:
> On 20/06/2018 05:53, Michael Richardson wrote:
>>
>> Carsten Bormann wrote:
>> > 2.2.2 says:
>>
>> >> It is not an error if a name is first used with a "/=&q
d be done) to mark an extension point with a dollar
> sign:
> $transport-proto /= IPPROTO_TCP
> (See section 3.9 for more about that convention.)
Ah, interesting. thank you.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP
On 31/05/18 04:23 PM, Brian E Carpenter wrote:
On 01/06/2018 07:31, Michael Richardson wrote:
Toerless Eckert wrote:
> On Thu, May 31, 2018 at 03:07:15PM -0400, Michael Richardson wrote:
>> > I would prefer to have the simple definition "ANI == systems that
suppo
On 31/05/18 02:43 PM, Toerless Eckert wrote:
Thanks, Eliot
Good point, forgot to ask/mention this point in my previous emails.
As an ANIMA contributor, i would love for a draft/->RFC like BRSKI to
mention known existing implementations, especially open source, even if just
PoC.
I did not
On 19/06/18 11:08 AM, Michael Richardson wrote:
From our document:
transport-proto /= IPPROTO_TCP ; note this is an extensible CDDL choice
; and can be added to in subsequent
; specifications using the /= and //=
In further
ifications using the /= and //=
It is unclear in section 2.2.2 if we can say foo /= without having said
foo = 1 / 2 / 3
previously, but it seems like it should be reasonable to do in order to
indicate that implementations should expect future values.
--
Michael Richardson , Sandelman Soft
2.3 or at
>
https://www.iana.org/assignments/core-parameters/core-parameters.xhtml#content-formats
> . Can you provide a pointer to explain what this would look like?
This is between the Registrar and MASA, which is unconstrained HTTPS, not
CoAP, even in the constrained situation.
--
Mi
or so ago.
I hear your suggestion for ietf-voucher-constrained{,-request}, and
unless there is a groundswell against that, another rename will occur.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network
ative" would be the same as
> for IPinIP. Maybe its different code-paths == different ports.
I'm sorry, I don't even understand the problem.
Maybe someone else can translate for me.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Ri
ASP".
> Possibly both, because GRASP already defines
> transport-proto = IPPROTO_TCP / IPPROTO_UDP
> IPPROTO_TCP = 6
> IPPROTO_UDP = 17
Ah right.
I just don't care... someone else decide and tell me what.
--
] Never tell me the odds!
it might sit in mis-ref for a few more months, which might help
someone. Is it that useful to the IESG?
Having said that, I don't have any problem adding it, I just don't want to do
much work on it :-)
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.a
CoAP code to have DTLS underneath it was
not easy, as the OpenSSL DTLS code has some problems in it's DTLS API.
(At least, I say it does, and I did patches for it. I can't get my patches
upstream until I find a VAX to test compile them on though...)
--
] Never tell me the o
BRSKI rather than "update of GRASP".
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@sandelman.ca http://www.sandelman.ca/| ruby on rails[
Toerless Eckert wrote:
> On Thu, May 31, 2018 at 03:07:15PM -0400, Michael Richardson wrote:
>> > I would prefer to have the simple definition "ANI == systems that
support
>> > both BRSKI and ACP" in the doc itself. Threre is really no single
a
re is so that
implementations actually check the value.
> One option in this case is to include "/ IPPROTO_UDP / IPPROTO_IPV6"
> in the syntax with a specific note that they are not currently
> defined and MUST be treated as errors if received.
I prefer this to the not li
l (just working through that in ACP doc
because
> of the ongoing review of it).
okay.
> 4.1.1:
>> transport-proto = IPPROTO_TCP / IPPROTO_UDP / IPPROTO_IPV6
> The way i see it, the normative approach with TCP circuit proxy would
> always only have TCP, right, e.g.: the
Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@sandelman.ca http://www.sandelman.ca/| ruby on rails[
signature.asc
need
some clarification, if only so that they are automated correctly.
This is just a note for later on; I think we need some operating ACPs before
we can describe issues with them.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman
6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@sandelman.ca http://www.sandelman.ca/| ruby on rails[
signature.asc
Description: PGP signature
___
Anima mailing list
Anima
In other words: to not be PKCS7 compatible, but require CMS processing.
I think this is reasonable from a specification point of view, but there has
been pushback from people who have FIPS-140 libraries that they
have hard times getting updated.
--
] Never tell me the odds!
> So I think the "SHOULD NOT" clause has to go. Perhaps you
> mean:
> This value MUST NOT be used for any future Registration attempt.
Edited as you suggest!
--
Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting
Brian E Carpenter <brian.e.carpen...@gmail.com> wrote:
> On 27/03/2018 08:11, Michael Richardson wrote:
> ...
>>
>> > d) Add section to request brksi-proxy and brski-registrar to
>> > IANA service name registry.
>>
>> I
Brian E Carpenter <brian.e.carpen...@gmail.com> wrote:
> I definitely recommend replacing lower-case "may" in a case like
> the one below.
Agreed.
> Perhaps:
>>> , and MUST NOT be
>>> enabled unless the JRC indicates support for th
two in an appropriate section
> of BRSKI as a very explicit example how BRSKI can be reused outside the
> complete ANIMA scope (also add draft-ietf-netconf-zerotouch as an
> informational
> reference).
I would prefer to let ietf-netconf-zerotouch do tha
ntries in that list?
> b) It would be good to create subsections for each registray mentioned so
> that one can see from the table of content what registries are impacted.
Don't we already have that?
We are only creating one registry.
> c) Probably need a summary of updates this
uchers may be
transported in the [I-D.vanderstok-ace-coap-est] protocol.
--
Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima mailing list
Anim
e really want people to read 6125, not just guess.
> Aka: for the less PKIX/Websecurity initiated readers like me, writing out
> what is actually implied could make the sentence easier to parse
> (instead of having to read more of RFC6125.
But, I want you to read 6
should be not be signed in any way.
--
Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima
ns the
> encoded (signed form) of the Pledge voucher-request.
> What is the correct behavior?
I've opened this as issue:
https://github.com/anima-wg/anima-bootstrap/issues/48
--
Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Wo
801 - 900 of 1078 matches
Mail list logo
