[Anima] IANA considerations for BRSKI/GRASP objective-value
https://github.com/anima-wg/constrained-voucher/pull/272/files Hi, we had some discussion on the list a few weeks ago about the lack of a IANA registry for the GRASP AN_PROXY and AN_join_registrar objective's objective-value. RFC8994 defines AN_PROXY, and RFC8995 (section 4.4.1) uses it like: [M_FLOOD, 12340815, h'fe81', 18, [["AN_Proxy", 4, 1, ""<-OBJECTIVEVALUE], [O_IPv6_LOCATOR, h'fe81', IPPROTO_TCP, 4443]]] with: objective-value = any ; none and we were a bit imprecise that "none" meant empty string, rather than CBOR null! constrained-voucher (cBRSKI) needs to extend this value to include: "DTLS-EST" while constrained-join-proxy uses it. RFC8995 defines AN_join_registrar (section 4.3) as: [M_FLOOD, 51804321, h'fda379a6f6ee02006401', 18, [["AN_join_registrar", 4, 255, "EST-TLS"], [O_IPv6_LOCATOR, h'fda379a6f6ee02006401', IPPROTO_TCP, 8443]]] objective-value = text ; name of the supported protocol. ; e.g., "EST-TLS" for RFC 7030. (after https://www.rfc-editor.org/errata/eid7576 is applied) constrained-voucher (cBRSKI) needs to extend this value to include: "BRSKI_JP" while constrained-join-proxy then extends this to include "BRSKI_RJP" (see: https://github.com/anima-wg/constrained-join-proxy/pull/46 ) we also seem to have "CMP" as a value, which I think that brski-ae will need to register, but which I don't think we do yet. One thing that I'm unsure about is whether there should be additional columns in the Registry. Specifically, we have changes in the $transport-proto for both, which can vary from IPPROTO_TCP in RFC8995, to IPPROTO_UDP for the coap methods. Should that be in the table too? -- 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] Esko: Re: Moving draft-ietf-anima-brski-cloud-06 forward
On 12-Aug-23 02:12, Esko Dijk wrote: I believe it's better for everybody if this is done by the authors. But the authors may not see the relevant issues. Only a picky reviewer might see them ;-) Ideally there should be more than 1 WG reviewer that reads everything in detail to find the nits. Yes, and when I was a gen-art reviewer I would try to do this, but that is really too late in the process. Also some drafts were so bad that I ended up saying that the draft should be sent back to the WG for that reason. However, fixing incorrect English is not a very interesting job. Professional copy editors are paid to do it. Brian -Original Message- From: Brian E Carpenter Sent: Wednesday, August 9, 2023 22:40 To: Esko Dijk ; Toerless Eckert ; Michael Richardson Cc: anima@ietf.org Subject: Re: [Anima] Esko: Re: Moving draft-ietf-anima-brski-cloud-06 forward (we can apply the lazy-fix policy and let IESG find them ;-) ) A bit off topic, but that is *not* the IESG's job. Unfortunately the IESG often wastes time on this rather than sending it on to the RFC Editor, whose job it is. I believe it's better for everybody if this is done by the authors. Regards Brian On 10-Aug-23 03:33, Esko Dijk wrote: I did check just now - the review comments were addressed. I added a few new text issues in the issue tracker #42 to #46 (https://github.com/anima-wg/brski-cloud/issues) and a request to change one more item for #32. This is based on reading the new text and re-reading the old. These are things I feel that the WG needs to fix before proceeding with the document, to avoid reviewer's confusion further down the line. Overall, I also found there's still many typos and word omissions that could be fixed before moving this document forward to IESG. Not sure if that's needed (we can apply the lazy-fix policy and let IESG find them ;-) ) I could also send a PR with fixes but that might delay the process. Let me know if this PR is desired or not! Esko -Original Message- From: Toerless Eckert Sent: Friday, July 28, 2023 19:50 To: Esko Dijk Cc: Michael Richardson ; anima@ietf.org Subject: Esko: Re: [Anima] Moving draft-ietf-anima-brski-cloud-06 forward Esko: I was just checking -07, it looks as if your open review concerns should have been successfully answered. Would you mind acknowledging, please ?! Thanks Toerless On Wed, Jul 26, 2023 at 01:58:22PM -0400, Michael Richardson wrote: Owen Friel \(ofriel\) wrote: > Thanks Esko, I just merged a PR to address these: > https://github.com/anima-wg/brski-cloud/issues/40 Thanks, Owen now posted -07: https://author-tools.ietf.org/iddiff?url1=draft-ietf-anima-brski-cloud-06=draft-ietf-anima-brski-cloud-07=--html -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
Re: [Anima] Esko: Re: Moving draft-ietf-anima-brski-cloud-06 forward
If someone can tell me when the document is ready technically, I volunteer to do an editing pass for "typos and word omissions", and anything else that I catch. Either I will need a txt/pdf version of the document (for which I will produce a separate text file containing my suggested changes), or I will need someone to teach me how to edit the source from Github, and push the result back. Bill On 8/11/2023 11:57 AM, Michael Richardson wrote: Esko Dijk wrote: > I did check just now - the review comments were addressed. I added a > few new text issues in the issue tracker #42 to #46 > (https://github.com/anima-wg/brski-cloud/issues) and a request to > change one more item for #32. This is based on reading the new text > and re-reading the old. These are things I feel that the WG needs to > fix before proceeding with the document, to avoid reviewer's confusion > further down the line. I went through them, ad there is now a PR against brski-cloud. > Overall, I also found there's still many typos and word omissions that > could be fixed before moving this document forward to IESG. Not sure if > that's needed (we can apply the lazy-fix policy and let IESG find them hah. Let's not. -- Michael Richardson. o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide Attention This email originates from outside the concordia.ca domain. // Ce courriel provient de l'extérieur du domaine de concordia.ca ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima -- Dr. J.W. Atwood, Eng. tel: +1 (514) 848-2424 x3046 Distinguished Professor Emeritus fax: +1 (514) 848-2830 Department of Computer Science and Software Engineering Concordia University ER 1234 email:william.atw...@concordia.ca 1455 de Maisonneuve Blvd. Westhttp://users.encs.concordia.ca/~bill Montreal, Quebec Canada H3G 1M8 ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
Re: [Anima] Esko: Re: Moving draft-ietf-anima-brski-cloud-06 forward
Esko Dijk wrote: > I did check just now - the review comments were addressed. I added a > few new text issues in the issue tracker #42 to #46 > (https://github.com/anima-wg/brski-cloud/issues) and a request to > change one more item for #32. This is based on reading the new text > and re-reading the old. These are things I feel that the WG needs to > fix before proceeding with the document, to avoid reviewer's confusion > further down the line. I went through them, ad there is now a PR against brski-cloud. > Overall, I also found there's still many typos and word omissions that > could be fixed before moving this document forward to IESG. Not sure if > that's needed (we can apply the lazy-fix policy and let IESG find them hah. Let's not. -- 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] Esko: Re: Moving draft-ietf-anima-brski-cloud-06 forward
> I believe it's better for everybody if this is done by the authors. But the authors may not see the relevant issues. Only a picky reviewer might see them ;-) Ideally there should be more than 1 WG reviewer that reads everything in detail to find the nits. -Original Message- From: Brian E Carpenter Sent: Wednesday, August 9, 2023 22:40 To: Esko Dijk ; Toerless Eckert ; Michael Richardson Cc: anima@ietf.org Subject: Re: [Anima] Esko: Re: Moving draft-ietf-anima-brski-cloud-06 forward > (we can apply the lazy-fix policy and let IESG find them ;-) ) A bit off topic, but that is *not* the IESG's job. Unfortunately the IESG often wastes time on this rather than sending it on to the RFC Editor, whose job it is. I believe it's better for everybody if this is done by the authors. Regards Brian On 10-Aug-23 03:33, Esko Dijk wrote: > I did check just now - the review comments were addressed. I added a few new > text issues in the issue tracker #42 to #46 > (https://github.com/anima-wg/brski-cloud/issues) and a request to change one > more item for #32. > This is based on reading the new text and re-reading the old. These are > things I feel that the WG needs to fix before proceeding with the document, > to avoid reviewer's confusion further down the line. > > Overall, I also found there's still many typos and word omissions that could > be fixed before moving this document forward to IESG. Not sure if that's > needed (we can apply the lazy-fix policy and let IESG find them ;-) ) > I could also send a PR with fixes but that might delay the process. Let me > know if this PR is desired or not! > > Esko > > -Original Message- > From: Toerless Eckert > Sent: Friday, July 28, 2023 19:50 > To: Esko Dijk > Cc: Michael Richardson ; anima@ietf.org > Subject: Esko: Re: [Anima] Moving draft-ietf-anima-brski-cloud-06 forward > > Esko: I was just checking -07, it looks as if your open review concerns > should have been > successfully answered. Would you mind acknowledging, please ?! > > Thanks > Toerless > > On Wed, Jul 26, 2023 at 01:58:22PM -0400, Michael Richardson wrote: >> >> Owen Friel \(ofriel\) wrote: >> > Thanks Esko, I just merged a PR to address these: >> > https://github.com/anima-wg/brski-cloud/issues/40 Thanks, Owen >> >> now posted -07: >> >> https://author-tools.ietf.org/iddiff?url1=draft-ietf-anima-brski-cloud-06=draft-ietf-anima-brski-cloud-07=--html >> >> >> -- >> Michael Richardson. o O ( IPv6 IøT consulting ) >> Sandelman Software Works Inc, Ottawa and Worldwide > > ___ > Anima mailing list > Anima@ietf.org > https://www.ietf.org/mailman/listinfo/anima ___ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
[Anima] August 15 design team cancelled
The Tuesday August 15 meeting has been cancelled because it's a german public holiday. -- 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
