Re: [Anima] [COSE] [Rats] cose+cbor vs cwt in MIME types

possible. So +cwt is better than +cose+cbor, even though +cose+cbor is a superset of +cwt. (Every CWT is a COSE object) I'm not even sure that +cose+cbor ever makes sense, since +cose implies +cbor. But, +cose+gzip might make sense in some context. -- Michael Richardson. o O ( I

Re: [Anima] [COSE] [Rats] cose+cbor vs cwt in MIME types

has a non-specific handler that would like to decode as much as possible. For instance, wireshark/tcpdump, or your favourite software IDE. I have just sent requests to media-types for +cwt and +cose to go through Expert Review. -- Michael Richardson. o O ( IPv6 IøT consulting )

[Anima] registration for +cose

: IESG (I was writing an ID for this, then realized that application/cose was already a thing, and that all we needed was a suffix, which is Expert Review) -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc

Re: [Anima] [COSE] [Rats] cose+cbor vs cwt in MIME types

> we register the "+cose" suffix with IANA. My reading is that we can have +cose for the cost of an Expert Review. application/cose is already registered. My next message is about that. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Ri

Re: [Anima] [COSE] [Rats] cose+cbor vs cwt in MIME types

at voucher+ysig is meaningful (or accurate) for us, because we also COSE sign it, which not every YANG-SID use will do. So I just don't know what to do, but I think we what have done is wrong. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottaw

Re: [Anima] [COSE] [Rats] cose+cbor vs cwt in MIME types

dditional context. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP signature ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima

Re: [Anima] [COSE] [Rats] cose+cbor vs cwt in MIME types

ide the signed part. So, if we'd call it application/eat+cwt, then we ought also call it application/voucher+ysid It seems that we ought to have registered +ysid in RFC9254. Can we do it in draft-ietf-core-sid-20? -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Sof

Re: [Anima] zerotier setup

Michael Richardson wrote: > Contact me for the network ID, after installing it, you do: > pippin-[~] mcr 10015 %sudo zerotier-cli join dbCOFFEE12345678 Actually, I had only setup "pippin" in host mode, and not in L2-bridged mode for the rest of my IETF HackVPN VLAN.

[Anima] zerotier setup

57:39.616159 IP 10.10.209.41.9993 > 209.87.249.16.20410: UDP, length 122 Contact me for the network ID, after installing it, you do: pippin-[~] mcr 10015 %sudo zerotier-cli join dbCOFFEE12345678 -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ot

Re: [Anima] [Rats] cose+cbor vs cwt in MIME types

Michael Richardson wrote: > COSE CHAIRS: can we have 5 minutes for this discussion? > I guess I can make two slides tomorrow and get Thomas to co-author them. I guess we didn't get any time at COSE. https://github.com/anima-wg/voucher/blob/main/presentations/ietf116-cose-mime-c

Re: [Anima] [Rats] cose+cbor vs cwt in MIME types

Smith, Ned wrote: > Does it belong with the "EAT Media Types" topic, or is it a separate topic? Well, it's not a RATS topic, it's a COSE topic. ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima

Re: [Anima] [Rats] cose+cbor vs cwt in MIME types

;> On Mon, Mar 13, 2023 at 5:49 PM Michael Richardson >> mcr+i...@sandelman.ca<mailto:mcr+i...@sandelman.ca> wrote: >> > Thomas Fossati thomas.foss...@arm.com<mailto:thomas.foss...@arm.com> wrote: >> > > I have commented on your respective i

Re: [Anima] I-D Action: draft-ietf-anima-grasp-distribution-07.txt

hat implementation, and see if any of the proposed other users are interested in the solution. Otherwise, my advice to the chairs is that there is no audience for this innovation, and we should not go through the expense/effort of publishing it. -- Michael Richardson , Sandelman Software

Re: [Anima] I-D Action: draft-ietf-anima-grasp-distribution-07.txt

this helps. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- *I*LIKE*TRAINS* signature.asc Description: PGP signature ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima

[Anima] cose+cbor vs cwt in MIME types

Thomas Fossati wrote: > I have commented on your respective issue trackers. I saw, but I think that this requires some cross-WG discussion and consensus, and I think that the COSE WG should tell us what to do. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consult

Re: [Anima] I-D Action: draft-ietf-anima-grasp-distribution-07.txt

Has anyone implemented for any of the use cases given in section 3? -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- signature.asc Description: PGP signature ___ Anima mailing list Anima@ietf.org https://www.ietf.org

Re: [Anima] ANIMA@IETF116: Call for agenda items

Hi, topics that I guess I'm the hook for: 1) rfc8366bis: summary of the wrapping up of YANG [3 min + 10 min questions] 2) plans for interop testing going forward from IETF116 [5min] 3) masa and registrar considerations documents [5 minutes each] -- Michael Richardson. o O ( IPv6 IøT

Re: [Anima] [lamps] lamps(/anima): another struggle related to CSR attr, draft-ietf-lamps-rfc7030-csrattrs-01 and draft-ietf-anima-brski-prm

... It's often this bloat that becomes really annoying when running protocols on challenged networks. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP signature __

Re: [Anima] [core] [Cbor] CDDL Model for YANG-SID (draft-ietf-core-sid)

name-rfc-8366 Thank you... but the YANG still went through your brain, not a tool :-) So, I'm still concerned that the content might be wrong in some way that deceives our brains. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and World

Re: [Anima] [Cbor] [core] CDDL Model for YANG-SID (draft-ietf-core-sid)

Carsten Bormann wrote: > On 2023-02-25, at 22:52, Carsten Bormann wrote: >> >>> RFC8366. >> >> Good idea. Let’s see when I get to it… > Examples don’t validate. Yes, I know that the base64 isn't valid. I guess we should have made it valid base64, even if it was

Re: [Anima] [core] CDDL Model for YANG-SID (draft-ietf-core-sid)

ant to keep the YANG anymore. A huge huge huge amount of effort on our part, for almost zero benefit. We didn't really have CDDL 8 years ago, so we had no clear alternative when we started, but I sure wouldn't go down the YANG path again. -- Michael Richardson. o O ( IPv6 IøT consulting

[Anima] WGLC comments on brski-cloud, and Re: I-D Action: draft-ietf-anima-rfc8366bis-06.txt

fusing to reviewers. It might also be better to change rfc8366bis from a document that obsoletes RFC8366, to one that just Updates (Amends) the RFC8366's YANG, and has no other text. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- signature.asc Description: PGP sig

Re: [Anima] changes for CORE-SID and SX:structure in draft-ietf-anima-rfc8366bis-04 and -05

r constraint also > agent-provided-proximity-registrar-pubk and > agent-provided-proximity-registrar-pubk-sha256 - agent-sign-cert: for Esko, should we? -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- signature.asc Descript

Re: [Anima] WGLC for draft-ietf-anima-brski-prm-06, ends Feb. 15th, 2023

draft-ietf-opsawg-service-assurance-architecture draft-ietf-opsawg-service-assurance-yang 8366 doesn't have a lot of explanation actually, outside of the YANG module. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- si

Re: [Anima] WGLC for draft-ietf-anima-brski-prm-06, ends Feb. 15th, 2023

ed a major issue by catching this now. Andy has weighed in to both tell us we don't have to do it this way, and also to say that we do have to do that. I conclude that we have not had enough review from sufficiently invested YANG experts. -- Michael Richardson , Sandelman Software Works -= IPv6

Re: [Anima] WGLC for draft-ietf-anima-brski-prm-06, ends Feb. 15th, 2023

actually just being wrong. None of us are really generating code from the YANG, so we aren't seeing the failures. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- signature.asc Description: PGP signature ___ Anima mai

Re: [Anima] WGLC for draft-ietf-anima-brski-prm-06, ends Feb. 15th, 2023

that I won't do. > If you do not feel this document should advance, please state > your reasons why So, as much as I'd like it to advance, I don't think it can advance until we agree what to do with the YANG. -- Michael Richardson , Sandelman Software Works -= I

Re: [Anima] New Version Notification for draft-ietf-anima-rfc8366bis-05.txt

Michael Richardson wrote: > I see that I still have RFC8792 wrapping in the voucher-request YANG, while I > did fix that for the voucher YANG. I did patches for pyang to sort the SID values everywhere, but I don't consitently use that version pyang, so the values didn't get

Re: [Anima] New Version Notification for draft-ietf-anima-rfc8366bis-05.txt

internet-dra...@ietf.org wrote: > Html: https://www.ietf.org/archive/id/draft-ietf-anima-rfc8366bis-05.html > Diff: https://author-tools.ietf.org/iddiff?url2=draft-ietf-anima-rfc8366bis-05 Hi, Toerless asked for a clear Changes since RFC8366 section. I've added that

[Anima] changes for CORE-SID and SX:structure in draft-ietf-anima-rfc8366bis-04 and -05

| ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works|IoT architect [ ] m...@sandelman.ca http://www.sandelman.ca/| ruby on rails [ -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc,

Re: [Anima] [netmod] 答复: CORE-SID and SX:structure and draft-ietf-anima-rfc8366bis-01.txt

Andy Bierman wrote: >> Fengchong (frank) wrote: >> > Hi Michael, >> > You can use augment-structure to extend a yang structure. >> >> You can't use augment-structure to extend in-place an existing yang >> structure >> Augment-structure produces a new structure with a

Re: [Anima] [core] CORE-SID and SX:structure and draft-ietf-anima-rfc8366bis-03.txt

Michael Richardson wrote: > * I will merge in the changes to ietf-voucher and ietf-voucher-request from > draft-ietf-anima-constrained-voucher. At which point, the document title > will *really really* be wrong, since it won't even contain the voucher, > just const

Re: [Anima] 答复: [netmod] CORE-SID and SX:structure and draft-ietf-anima-rfc8366bis-01.txt

ng YANG modules with new attributes. We have to revise > 8366 each time we want extend things. This email details the work to > make that occur. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Descr

Re: [Anima] [core] CORE-SID and SX:structure and draft-ietf-anima-rfc8366bis-01.txt

Michael Richardson wrote: >> A diff from the previous version is available at: >> https://author-tools.ietf.org/iddiff?url2=draft-ietf-anima-rfc8366bis-01 > * I have revised the ietf-voucher YANG module to use sx:structure (RFC8971) > rather than YANG-DATA

[Anima] CORE-SID and SX:structure and draft-ietf-anima-rfc8366bis-01.txt

thought is that we change our mind about making this a Obsoletes, and go back to making this document an Updates:, but I am still stting on the fence for this. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signa

Re: [Anima] how should join proxy react to multiple registrars

> Are there any protocol or standard implications? I don't think so, but I > wanted to check. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP signature __

[Anima] how should join proxy react to multiple registrars

. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP signature ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima

Re: [Anima] [Technical Errata Reported] RFC8995 (7263)

r > information (e.g., what the proposed long-term resolution is) if that > is helpful. If have consensus for the next text, then I think the RFC-editor site can do the patch process, though, when we mark it as verified. -- Michael Richardson. o O ( IPv6 IøT consulting )

Re: [Anima] [Technical Errata Reported] RFC8995 (7263)

Esko Dijk wrote: > The proposed text still needs some work here; I would urge the WG not > to accept this in current form. That said, using normative language in > this specific part certainly helps to clarify the requirements for > implementers. So, I agree, but "Hold for

Re: [Anima] [Technical Errata Reported] RFC8995 (7263)

editor.org/errata/eid7263 > -- > Type: Technical > Reported by: Rufus Buschart Agreed. Please mark as hold for document update. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa

Re: [Anima] Yangdoctors early review of draft-ietf-anima-brski-prm-05

> get this, 8366bis would have to use sx:structure, and then an 8995bis > would have to use sx:augment-structure. But, I think that sx:augment-structure, if done by "B", and then done in a different document by "C" would result in duplicate data nodes if "D&q

Re: [Anima] Yangdoctors early review of draft-ietf-anima-brski-prm-05

, but we want to be sure we are really doing it wrong. >> Do you have an opinion about whether there is just a bug in pyang's SID.py? >> Or is there something else missing in the YANG? > Yes this is missing in pyang. I have asked the authors of the sid > plugin to h

Re: [Anima] FW: New Liaison Statement, "LS on the initiation of the new work item Y.AN-Arch-fw: "Architecture Framework for Autonomous Networks""

ON/liaison-2022-12-02-itu-t-sg-13-ietf-ls-on-the-initiation-of-the-new-work-item-yan-arch-fw-architecture-framework-for-autonomous-networks-attachment-1.docx An editable version of the same email. I don't understand why people do this. -- Michael Richardson. o O ( IPv6 IøT

Re: [Anima] Yangdoctors early review of draft-ietf-anima-brski-prm-05

it wrong. Do you have an opinion about whether there is just a bug in pyang's SID.py? Or is there something else missing in the YANG? -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP signature ___

Re: [Anima] [netmod] mcr's YANG question raised during the ANIMA WG session

quot;, refined the rules for some leaves. It's not clear to me that we can do this using sx:structure, and I think that augment-structure has the same failings as "augment" had. I would very much like to have a wider discussion of this. -- Michael Richardson. o O ( IPv6 IøT consulting

Re: [Anima] [netmod] mcr's YANG question raised during the ANIMA WG session

nd easily accessible form, i.e. as > compilable YANG modules on github. Glad it helped, if I could have presented it better, let me know. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP signatu

Re: [Anima] how to process RFC8791 examples

wrote: > You should run it with "--tree-print-structures". Thanks. That makes sense. I admit that much of my pyang use is cargo culted from one draft to another. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa

[Anima] sids not allocated for sx_structure/RFC8791.

tool. However: https://github.com/mbj4668/pyang/issues/716 there was some confusion, but it seems that SIDs were generated for groupings. I don't know if I need to re-introduce deeper groupings, I don't think so. I have opened: https://github.com/mbj4668/pyang/issues/835 -- Michael

Re: [Anima] [netmod] mcr's YANG question raised during the ANIMA WG session

Probably converting to RFC8791 is also a good thing. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP signature ___ Anima mailing list Anima@ietf.or

[Anima] how to process RFC8791 examples

don't see any clear difference. So how do I get the tree structure printed from the examples in RFC8791? -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP

Re: [Anima] Opsdir last call review of draft-ietf-anima-constrained-join-proxy-09

have also changed the MTI. There is a diff in the DT, and I wonder if you'd take a look at that and give us your opinion. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- signature.asc Description: PGP signature ___ Anima ma

Re: [Anima] [netmod] mcr's YANG question raised during the ANIMA WG session

uping for module D1"; container module-D1-things { uses vA:module-A-grouping; uses vB:module-B-grouping; uses vC1:module-C1-grouping; leaf attribute-D-Delta { type binary; description "Delta"; } } } The file practice2.sh uses

Re: [Anima] [netmod] mcr's YANG question raised during the ANIMA WG session

could just add the the groupings that they need. I'm trying this now. -- 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

Re: [Anima] 2nd WGLC for draft-ietf-anima-constrained-join-proxy-12, ends September 20th 2022

getting here... > wiki / github - where would you think we could best collect them better than > here in email ? Here in email, and in an agenda item for a future IETF. Some working groups have a "freezer" draft. -- Michael Richardson , Sandelman Software Works

Re: [Anima] 2nd WGLC for draft-ietf-anima-constrained-join-proxy-12, ends September 20th 2022

> proxy/registar with too much data, especially when using (radio) networks > with regulatory limitations on the volume permitted per sender (such as > 1% duty-cycle per hour limitatios). Yes. But, let's not boil the ocean. It's a PS. We need to finish it so that we can deploy

[Anima] constrained-join-proxy registration of BRSKI_JP

should also be cited for the objective values "BRSKI_RJP" defined in {{graspregistrardiscovery}}. (I don't know why we had to write "without quotes", but we and IANA did) -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =-

Re: [Anima] [core] ANIMA constrained-join proxy revision to use CoAP

Uri-Path is the name of the CoAP option that I would like permission to omit. -- 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

Re: [Anima] [core] ANIMA constrained-join proxy revision to use CoAP

urce name I agree, but I don't see the value in adding bytes to the wire. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- signature.asc Description: PGP signature ___ Anima mailing list Anima@ietf.org https://www.ietf

[Anima] constrained-join-proxy registration of BRSKI_JP

in the Grasp Parameter registry. This document should also be cited for the objective values "BRSKI_JP" defined in {{graspregistrardiscovery}}. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- signature.asc Description: PGP signature ___

Re: [Anima] [core] ANIMA constrained-join proxy revision to use CoAP

t's okay: learning a bit of CoAP is not that hard. You don't have to be an expert on it. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- signature.asc Description: PGP signature ___ Anima mailing list Anima@ietf.org http

Re: [Anima] [core] ANIMA constrained-join proxy revision to use CoAP

ct to, right ? No. The CoAP that the Pledge sends is inside the DTLS. The CoAP that we are discussing is added by the Join Proxy. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- signature.asc Description: PGP signature ___ A

Re: [Anima] [core] ANIMA constrained-join proxy revision to use CoAP

Toerless Eckert wrote: > Can we make sure that the text does explain why the field is not > inclueded, and explain that the packet MUST be rejected if it was > included ? Why should we reject if it is included? > Seems like: > Field is not included and would cause rejection

Re: [Anima] [core] ANIMA constrained-join proxy revision to use CoAP

ve to > the next step. So, no Uri-Path option is equivalent to /? -- 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

Re: [Anima] [core] ANIMA constrained-join proxy revision to use CoAP

o that :-) > I'm not 100% sure if for a resource at the root (/), one Uri-Path > Option with 0 length is needed or if 0 Uri-Path Options can be used. > Or if both methods would be valid. I'm hoping that Carsten or Christian will express an opinion. -- Michael Richardson , San

Re: [Anima] [core] ANIMA constrained-join proxy revision to use CoAP

Esko Dijk wrote: >> The Proxy-Scheme option is set to "coap". Do I even need this? > I don't think we can use the Proxy-Scheme (or the Proxy-Uri) Option If we don't need it, then GREAT, that's six bytes we save. -- Michael Richardson , Sandelman Software

[Anima] ANIMA constrained-join proxy revision to use CoAP

that going to be a problem, and is POST still the right method? Appendix A has some details on the CoAP header, which I'd like a review. Did I even get it halfway right? -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =-

Re: [Anima] Example where CoAP is used as relay protocol for Join Proxy

For IPR reasons, I have avoided reading the source code. I have the white paper open, but I haven't finished reading it, and likely won't before the ID deadline. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- signature.asc De

Re: [Anima] 2nd WGLC for draft-ietf-anima-constrained-join-proxy-12, ends September 20th 2022 / 6.1.1. Discovery example fix?

the rt=brski resource must be > present. Otherwise, no interoperability. > Note that the JP won't care about the details of the /rv, /vs, /es > resources. It just needs Registrar address and port. Agreed. -- ] Never tell me the odds! | ipv6

Re: [Anima] 2nd WGLC for draft-ietf-anima-constrained-join-proxy-12, ends September 20th 2022

assume that this Registrar will be alive on that IP address > forever. So it needs to rediscover in case the original discovery > information expired. If rediscovery fails, it will not forward traffic > anymore to the old IP address. GRASP makes this timeout pretty cl

Re: [Anima] 2nd WGLC for draft-ietf-anima-constrained-join-proxy-12, ends September 20th 2022

turn) in order to establish trust, and then you can say, "off hours", which certainly doesn't help the DoS problem. That's one reason why EST/RFC7030 has this 202 status process. The enrollment that started at 5:06pm on Friday is waiting for a human to com

Re: [Anima] 2nd WGLC for draft-ietf-anima-constrained-join-proxy-12, ends September 20th 2022

of' ED> 6.1.1 ED> The coaps+jpy scheme is registered is defined -> is registered and defined ? ED> 6.1.2 ED> Figure 6: Example of Registrar announcing two services -> isn't it 3 services here? 3 ports are advertised. ED> 9.2 ED> The text contains &qu

Re: [Anima] Call for agenda items/attendance ANIMA @ IETF 115 / agenda request constrained-voucher

function? I suggest that you record a demo/screencast to youtube and share link. That avoids much of the demo-effect, and avoids the time pressure. Not that there is also a happy-hack hour on Monday as part of the hackathon. -- Michael Richardson , Sandelman Software Works -= IPv6 Io

Re: [Anima] KIRA – A Scalable ID-based Routing Architecture for Control Planes

I'm interested in this as well, but it might be better to have a separate virtual interim with ROLL, ANIMA people invited, and fewer conflicts. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- signature.asc Description: PGP signature

Re: [Anima] Call for agenda items/attendance ANIMA @ IETF 115

I need ten minutes to talk about the current resolution for join-proxy of the "jpy" situation. There are probably other updates that I need to do, but that is the one occupying my time right now. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software

Re: [Anima] [IANA #1229125] expert review for draft-ietf-anima-constrained-join-proxy (core-parameters)

to the ANIMA (and CORE) ML later tonight to explain the discussion on Wednesday. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP signature ___ Anima

[Anima] ace-ake-auth updates for latest EDHOC principles

old to whom? Also, the URL for the MASA is ideally very very short :-) -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP signature ___ Anima mailing

Re: [Anima] 2nd WGLC for draft-ietf-anima-constrained-join-proxy-12, ends September 20th 2022

Okay, thank you. I'll crunch through your comments on Friday. ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima

Re: [Anima] Review of ANIMA BRSKI-AE draft

what are the essential pieces, and then maybe make two or three smaller diagrams that would work. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- signature.asc Description: PGP signature ___ Anima mailing list Anima

[Anima] comments on anima-brski-prm

Certificate. It actually should have the cmcRA EKU set, so it's not just an ordinary LDevID. Am I missing something here? Hope to talk to you all on Tuesday evening. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- signature.asc Description: PGP signature

Re: [Anima] discovery of Registrar by stateless Join-Proxy (was Re: [core] Join-proxy information in the RD (Re: CoRE WG Virtual Interim 2022-09-14))

in proxy? In section 6.2.1 it discovers transport, but > I suppose at a later step it will want to discover a path for a > concrete resources (dunno, maybe an rt=brski.es or brski.rv), where > would it currently learn that? > These lines might be a good starting point to

[Anima] discovery of Join-Proxy/Registrar by pledge (was Re: [core] Join-proxy information in the RD (Re: CoRE WG Virtual Interim 2022-09-14))

ld be nice if we could get back: ;ct=287 as well, but I don't know how/if we can ask for rt=est* as well as rt=brski* in a single operation. This is in section 6.1.1 of the -12. Maybe we just don't need brski.jp *AT ALL* The Join Proxy should answer as if it was the Registrar, with coaps:

[Anima] discovery of Registrar by stateless Join-Proxy (was Re: [core] Join-proxy information in the RD (Re: CoRE WG Virtual Interim 2022-09-14))

at least, I want to. > I think that "JP may implement either, JR MUST support both" would be > better.. I did put that into my presentation for 114. It's possible we didn't implement that conclusion into the ID. -- Michael Richardson , Sandelman Software Works -=

Re: [Anima] ACP RPL profile and dynamics

> incremented under catastrophic events", therefore I was under the > impression global repair would only be done in extreme circumstances, > and not periodically. A link going down in an ISP is probably a catastrophic event. Maybe the text needs adjustment. --

Re: [Anima] ACP RPL profile and dynamics

a good question, and I assumed that global route repair would occur periodically, and whenever the NOC found that it couldn't reach some nodes. There is probably a gap in knowledge/experience here. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richar

Re: [Anima] ACP RPL profile and dynamics

case I would be grateful if someone can > point me to the relevant code sections. unstrung is certainly lacking in this area. I would be happy to talk about how to extend it in the right areas. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- signature.asc D

[Anima] MUD for (Virtual) RFC8995 Registrar Appliances -- register a port number?

to write a MUD ACL that permits connection to any host on a particular port. My reading of RFC8519 is that yes, one can have a l4.tcp ACL without having an l3 ACL. So, to make that workable, we'd at least need a registered port. -- Michael Richardson. o O ( IPv6 IøT consulting

Re: [Anima] session-id as epoch-id (was: Re: Signing GRASP objectives [Was: Extending GRASP messages and signing GRASP multicasts])

he "slow" path. I'd argue for always checking signatures if they are there before flooding. If it's too expensive, then I think that I'd rather lower the strength of the signature until it's cheap enough. If it's a thing that has security critical information, then if some ASA finds

Re: [Anima] session-id as epoch-id (was: Re: Signing GRASP objectives [Was: Extending GRASP messages and signing GRASP multicasts])

st with the Epoch distributor to re-initialize one's state. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP signature ___ Anima mailing list Anima@

Re: [Anima] Consolidated floods [was Signing GRASP objectives]

about dams on wikipedia) -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP signature ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima

Re: [Anima] ACP vs. Data plane Re: Signing GRASP objectives [Was: Extending GRASP messages and signing GRASP multicasts]

analytics > engines that attempt to measure network health. ACP or not... I come back to SHIM6, MPTCP or QUIC/MASQUE. Initiate the connection over ACP addresses, but then discover some higher bandwidth IP addresses and prefer them for the bulk transfers. -- Michael Richardson. o O (

Re: [Anima] Signing GRASP objectives [Was: Extending GRASP messages and signing GRASP multicasts]

at many. at least ~50 bytes per message, given a 32-byte EcDSA signature. That's still a 20:1 ratio though, and nothing to sneeze at. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Descript

Re: [Anima] Signing GRASP objectives [Was: Extending GRASP messages and signing GRASP multicasts]

Toerless Eckert wrote: > On Wed, Aug 24, 2022 at 08:33:43PM -0400, Michael Richardson wrote: >> >> Brian E Carpenter wrote: > I need to >> understand epochs a bit better. I wonder whether an epoch > boundary >> should define when sessi

Re: [Anima] Signing GRASP objectives [Was: Extending GRASP messages and signing GRASP multicasts]

lete session-ids to detect repetition, > but needs to age out that cache somehow. My code does that with a > simple LRU but that isn't ideal. That's totally a good idea. is: https://www.ietf.org/archive/id/draft-ietf-rats-architecture-21.html#name-example-3-epoch-id-based-pa hel

Re: [Anima] Signing GRASP objectives [Was: Extending GRASP messages and signing GRASP multicasts]

> What I don’t understand is why the signature then needs to be encoded > as part of the objective. Why can’t I sign a combination of objectives > that are only valid as that combination? I think it could go somewhere else, but I'd like to first understand an example of this co

Re: [Anima] Signing GRASP objectives [Was: Extending GRASP messages and signing GRASP multicasts]

M_FLOOD objectives for use during a flood ) -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP signature ___ Anima mailing list Anima@ietf.org https

Re: [Anima] Signing GRASP objectives [Was: Extending GRASP messages and signing GRASP multicasts]

g track. Should we be discussing > signing GRASP objectives, rather than messages? That might better fit the goals. Probably we should have started with a few use cases. > In many ways, that would be much easier to design and retro-fit. cool. -- Michael Richardson. o

Re: [Anima] remote attestation Epoch ID distribution in IPv6 and GRASP

ajor manufacturers? (I first saw this from Brocade in 2010, but I never saw it actually work) In either case, this is where the Epoch ID comes into play to me. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signatur

Re: [Anima] Extending GRASP messages and signing GRASP multicasts

ssue, and that we can leverage the BRSKI enrollment process to get any application specific keys that we need. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP signature ___

[Anima] remote attestation Epoch ID distribution in IPv6 and GRASP

eems quite good. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide signature.asc Description: PGP signature ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima

Re: [Anima] I-D Action: draft-ietf-anima-constrained-join-proxy-12.txt

CC to core@ I think that scheme registrations go to media-types@ ML, but I have to verify. I wonder how much justification the document needs to have, vs how much just needs to be in the email. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Otta

<    1   2   3   4   5   6   7   8   9   10   >