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 <[email protected]> On Behalf Of Michael Richardson > Sent: Dienstag, 24. Oktober 2023 18:16 > To: [email protected] > 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&data=05%7C01%7Csteffen.fries%40siemens.com%7Cc > 5188f121eb543ba384408dbd4acb27d%7C38ae3bcd95794fd4addab42e14 > 95d55a%7C1%7C0%7C638337610431515641%7CUnknown%7CTWFpbGZs > b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M > n0%3D%7C3000%7C%7C%7C&sdata=GV5HdCuWwIwVJB65lZ3a1BkPQG7O > AJeS%2BRLravetSNE%3D&reserved=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&data=05%7C01%7Csteffen.fries%40siemens.com%7C > c5188f121eb543ba384408dbd4acb27d%7C38ae3bcd95794fd4addab42e14 > 95d55a%7C1%7C0%7C638337610431515641%7CUnknown%7CTWFpbGZs > b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M > n0%3D%7C3000%7C%7C%7C&sdata=6uUvd9qNNYFcNSNDeRW3R7oQJjdT > %2BHvjAyEfoxZ8Pug%3D&reserved=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&data=05%7C01%7Csteffen.fries%40siemens.com%7C > c5188f121eb543ba384408dbd4acb27d%7C38ae3bcd95794fd4addab42e14 > 95d55a%7C1%7C0%7C638337610431515641%7CUnknown%7CTWFpbGZs > b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M > n0%3D%7C3000%7C%7C%7C&sdata=%2FDxO3syvCVBgtwSGPS8ujI5nNWH > Xn0aXR4EXxjTmg%2F0%3D&reserved=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&data=05%7C01%7Csteffen.fries%40siemens.com%7C > c5188f121eb543ba384408dbd4acb27d%7C38ae3bcd95794fd4addab42e14 > 95d55a%7C1%7C0%7C638337610431671874%7CUnknown%7CTWFpbGZs > b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M > n0%3D%7C3000%7C%7C%7C&sdata=r%2BuBHhUV%2B6VYT1uUbJpcDDdA > VFslRumPZyUAVgM%2FH6g%3D&reserved=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&data=05%7C01%7Csteffen.fries%40siemens.com%7C > c5188f121eb543ba384408dbd4acb27d%7C38ae3bcd95794fd4addab42e14 > 95d55a%7C1%7C0%7C638337610431671874%7CUnknown%7CTWFpbGZs > b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M > n0%3D%7C3000%7C%7C%7C&sdata=nyNgOBxIKHcTXRwVMBeSOVUUhZTya > vKI5DvlkqBVSuc%3D&reserved=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&data=05%7C01%7Csteffen.fries%40siemens.com%7C > c5188f121eb543ba384408dbd4acb27d%7C38ae3bcd95794fd4addab42e14 > 95d55a%7C1%7C0%7C638337610431671874%7CUnknown%7CTWFpbGZs > b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M > n0%3D%7C3000%7C%7C%7C&sdata=eR042VimBcUpglKKFRZR2TtiXCreK%2F > i6r9I%2FnuXkGHo%3D&reserved=0 > Need to add IANA registration for brski-pledge Probably this is redundant, and > we need to move all the discovery IANA stuff to the (new) discovery > document. > If we keep the Agent discovery of Pledge in PRM, then we need to keep the > IANA registry for the .well-known and mDNS in that document. > Much conversation dealing with lack of feedback from mediaman about > Media > Type process. There is no dependancy from discovery document about media > types, but it is a bit hidden /implicit. > > 7. > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithu > b.com%2Fanima-wg%2Fanima-brski- > prm%2Fissues%2F130&data=05%7C01%7Csteffen.fries%40siemens.com%7C > c5188f121eb543ba384408dbd4acb27d%7C38ae3bcd95794fd4addab42e14 > 95d55a%7C1%7C0%7C638337610431671874%7CUnknown%7CTWFpbGZs > b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M > n0%3D%7C3000%7C%7C%7C&sdata=96EIq6kI2hgFl6XH0cBs1WOucG07yNA > NfnFNZBOwN8k%3D&reserved=0 > product-serial-number for discovery > Suggested text is now in -01 of discovery. > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww > .ietf.org%2Farchive%2Fid%2Fdraft-ietf-anima-brski-prm-09.html%23name- > discovery-of-pledge-by- > regi&data=05%7C01%7Csteffen.fries%40siemens.com%7Cc5188f121eb543b > a384408dbd4acb27d%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C > 0%7C638337610431671874%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4 > wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000% > 7C%7C%7C&sdata=nHTCdSzqO1Wvvw8iidHim81r1QqSzfbwWq7sywRNoI8% > 3D&reserved=0 > We believe that it is okay to do **discovery** by manufacturer-specific serial > number without qualifying it with the manufacturer. While this results in > false > positives (every manufacturer has serial number 001 present), but in that > unlikely result, it is okay, because the Registrar-Agent can filter through > the > results. > > More discussion about how much we can ask for, and how will this get > integrated into supply processes. Definitely a topic for discussion at > IETF118. > > -- > Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting ) > Sandelman Software Works Inc, Ottawa and Worldwide _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
