Re: [Anima] summary of design team meeting, 2023-10-24
Fries, Steffen wrote: > Thank you for the minutes. Very good to keep track of the discussion. > Some of the issues discussed yesterday have been addressed by comments > and commits already. My goal here is not to just list open issues, but all issues that were discussed. So if readers come to the linked issues and find them closed/merged, they should just know that we are making progress. Or they should protest/disagree. -- 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
Re: [Anima] summary of design team meeting, 2023-10-24
Hi Michael, Thank you for the minutes. Very good to keep track of the discussion. Some of the issues discussed yesterday have been addressed by comments and commits already. Best regards Steffen > -Original Message- > From: Anima On Behalf Of Michael Richardson > Sent: Dienstag, 24. Oktober 2023 18:16 > To: anima@ietf.org > Subject: [Anima] summary of design team meeting, 2023-10-24 > > > To help with the WG keeping abreast of issues resolved by the (BRSKI) design > team, we will post a summary of issues worked on during the Tuesday > meetings. > To remind everyone is welcome to join the design team meetings which are > most > Tuesdays at 11am Eastern at whereby.com/sandelman. There are calendar > invites in the archives. > There will be design team meeting on Oct.31 or Nov. 7. > We will resume on Nov.14, and I will resend an invite for that date. > > Who: Toerless, Michael, Steffen, Thomas, Matthias, Marco Calipari. > > 1. > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithu > b.com%2Fanima-wg%2Fanima-brski- > prm%2Fissues%2F79=05%7C01%7Csteffen.fries%40siemens.com%7Cc > 5188f121eb543ba384408dbd4acb27d%7C38ae3bcd95794fd4addab42e14 > 95d55a%7C1%7C0%7C638337610431515641%7CUnknown%7CTWFpbGZs > b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M > n0%3D%7C3000%7C%7C%7C=GV5HdCuWwIwVJB65lZ3a1BkPQG7O > AJeS%2BRLravetSNE%3D=0 > discovery of registrar with BRSKI-PRM function set > > (one realization is that there will be Registrar/Registrar-Agent > communication/configuration which likely will go beyond the standards we > are defining. We have no experience here, and there will need to be > experiments with running code before we can have standardization here. > i.e. a Registrar and Registrar-Agent are part of a single product offering) > > 2. > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithu > b.com%2Fanima-wg%2Fanima-brski- > prm%2Fissues%2F106=05%7C01%7Csteffen.fries%40siemens.com%7C > c5188f121eb543ba384408dbd4acb27d%7C38ae3bcd95794fd4addab42e14 > 95d55a%7C1%7C0%7C638337610431515641%7CUnknown%7CTWFpbGZs > b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M > n0%3D%7C3000%7C%7C%7C=6uUvd9qNNYFcNSNDeRW3R7oQJjdT > %2BHvjAyEfoxZ8Pug%3D=0 > "registrar-agent signatures" check consistent use closed with text in section > 6.3.6 > > 3. > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithu > b.com%2Fanima-wg%2Fanima-brski- > prm%2Fissues%2F116=05%7C01%7Csteffen.fries%40siemens.com%7C > c5188f121eb543ba384408dbd4acb27d%7C38ae3bcd95794fd4addab42e14 > 95d55a%7C1%7C0%7C638337610431515641%7CUnknown%7CTWFpbGZs > b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M > n0%3D%7C3000%7C%7C%7C=%2FDxO3syvCVBgtwSGPS8ujI5nNWH > Xn0aXR4EXxjTmg%2F0%3D=0 > Security Considerations - nonce explanation closed, everyone happy with text > > 4. > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithu > b.com%2Fanima-wg%2Fanima-brski- > prm%2Fissues%2F117=05%7C01%7Csteffen.fries%40siemens.com%7C > c5188f121eb543ba384408dbd4acb27d%7C38ae3bcd95794fd4addab42e14 > 95d55a%7C1%7C0%7C638337610431671874%7CUnknown%7CTWFpbGZs > b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M > n0%3D%7C3000%7C%7C%7C=r%2BuBHhUV%2B6VYT1uUbJpcDDdA > VFslRumPZyUAVgM%2FH6g%3D=0 > Security Considerations - Misuse of Registrar-Agent Credentials nothing > changed in the text, agreed that description was good enough. > issue closed. > > 5. > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithu > b.com%2Fanima-wg%2Fanima-brski- > prm%2Fissues%2F128=05%7C01%7Csteffen.fries%40siemens.com%7C > c5188f121eb543ba384408dbd4acb27d%7C38ae3bcd95794fd4addab42e14 > 95d55a%7C1%7C0%7C638337610431671874%7CUnknown%7CTWFpbGZs > b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M > n0%3D%7C3000%7C%7C%7C=nyNgOBxIKHcTXRwVMBeSOVUUhZTya > vKI5DvlkqBVSuc%3D=0 > "domain/site" terminology definition and consistent usage We had a long > discussion about whether or not the term "site" needs to be go into the > document. Does it mean the same as "domain" or not? > It has been in slides, and often was used to refer to the multiple > "downstairs" > sites. We also discussed that "site" is a place where multicast DNS works > (which is kinda of standing the defintion on its head) We think we will remove > all references to site, and try to emphasize the nomadic connectivity of the > Registrar-Agent using some new term. > > 6. > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithu > b.com%2Fanima-wg%2Fanima-brski- > prm%2Fissues%2F129=05%7C01%7Csteffen.fries%40siemens.com%7C > c5188f121eb543ba384408dbd4acb27d%7C38ae3bcd95794fd4addab42e14 > 95d55a%7C1%7C0%7C638337610431671874%7CUnknown%7CTWFpbGZs > b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M > n0%3D%7C3000%7C%7C%7C=eR042VimBcUpglKKFRZR2TtiXCreK%2F > i6r9I%2FnuXkGHo%3D=0 > Need to add IANA registration for brski-pledge
Re: [Anima] Initial Call for agenda discussion / items ANIMA@IETF118 Prague (was: anima - New Meeting Session Request for IETF 118)
Dear Chairs, I would like to ask for the a time slot for my updated individual draft. Topic/Title:Update on BRSKI-CLE: A Certificateless Enrollment framework in BRSKI Name of Presenter(s): Lei YAN Length of time requested: 10 min Name of draft(s) discussed: draft-yan-anima-BRSKI-CLE-01 Best regards Lei YAN -Original Message- From: Anima On Behalf Of Esko Dijk Sent: Tuesday, September 19, 2023 9:11 PM To: anima-cha...@ietf.org; anima@ietf.org Subject: Re: [Anima] Initial Call for agenda discussion / items ANIMA@IETF118 Prague (was: anima - New Meeting Session Request for IETF 118) I'd like to present the update of draft-ietf-anima-constrained-voucher: -22 ; and status / remaining open issues. (This will be published prior to the IETF meeting.) 5 minutes would be ok, 10 minutes better if we have the time ;) Esko -Original Message- From: Anima On Behalf Of Fries, Steffen Sent: Thursday, September 14, 2023 14:58 To: Toerless Eckert ; anima@ietf.org Cc: anima-cha...@ietf.org; rwil...@cisco.com Subject: Re: [Anima] Initial Call for agenda discussion / items ANIMA@IETF118 Prague (was: anima - New Meeting Session Request for IETF 118) Hi Toreless, I would like to ask for the following slots in the IETF 118 meeting: Topic/TitleBRSKI-AE Status Update Name of Presenter(s) David von Oheimb Length of time requested 5 min If applicable: name of draft(s) discussed: draft-ietf-anima-brski-ae-06 (version 06 to be submitted) Topic/TitleJWS-voucher Status Update Name of Presenter(s)Thomas Werner/ Steffen Fries Length of time requested 5 min If applicable: name of draft(s) discussed: draft-ietf-anima-jws-voucher-09 Topic/TitleBRSKI-PRM Status Update Name of Presenter(s) Steffen Fries Length of time requested 10 min If applicable: name of draft(s) discussed: draft-ietf-anima-brski-prm-10 (version 10 to be submitted) Best regards Steffen > -Original Message- > From: Anima On Behalf Of Toerless Eckert > Sent: Thursday, September 14, 2023 1:12 AM > To: anima@ietf.org > Cc: anima-cha...@ietf.org; rwil...@cisco.com > Subject: [Anima] Initial Call for agenda discussion / items > ANIMA@IETF118 Prague (was: anima - New Meeting Session Request for > IETF 118) > > Dear ANIMA WG, > > This time, we wanted to ask for agenda items for ANIMA@IETF118 early > enough that we can accordingly ask for a fitting slot length. The > window for requesting WG slots closes on 09-22 23:59 UTC. > > For now, we have requested a one hour slot based on feedback from our > AD and others who ae trying to ensure that IETF in-person meeting time > is spent mostly on discussions that can only be had in-person, > especially given the ever growing number of WGs. > > Given how we are making good working progress with most our adopted > BRSKI WG items on our weekly online meetings (to the extend they are > not on back-burner because of serialization/dependencies), we think > for those WG items one hour will suffice at IETF118, so that is the current > request. > > If you have additional work you would like to see discussed, please > start discuss it on the list, so that we can consider extending the WG > meeting time request for > IETF118 as then needed. > > Cheers > Toerless - for the chairs > > On Wed, Sep 13, 2023 at 04:05:47PM -0700, IETF Meeting Session Request > Tool wrote: > > > > > > A new meeting session request has just been submitted by Toerless > > Eckert, a Chair of the ANIMA Working Group. > > > > > > - > > Working Group Name: Autonomic Networking Integrated Model and > Approach > > Area Name: Operations and Management Area Session Requester: > > Toerless Eckert > > > > > > Number of Sessions: 1 > > Length of Session(s): 1 Hour > > Number of Attendees: 40 > > Conflicts to Avoid: > > Chair conflict: detnet bier 6man intarea pim v6ops iabopen > > Technology overlap: emu netconf mboned Key participant conflict: > > nmrg opsarea intarea saag > > > > > > > > > > Participants who must be present: > > Michael Richardson > > > > Resources Requested: > > > > Special Requests: > > China remote attendance friendly time would be lovely (the earlier > > in the day, the better). One co-chair likely attending remotely > > - > > > > -- > --- > t...@cs.fau.de > > ___ > Anima mailing list > Anima@ietf.org > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww > .ietf.org%2Fmailman%2Flistinfo%2Fanima=05%7C01%7Csteffen.fries% > 40siemens.com%7C610b34f12fc2405a350308dbb4aed160%7C38ae3bcd95 >
