*MACE-Dir Conference Call* June 11, 2001 *Attendees* Keith Hazelton (chair) - Wisconsin Bob Morgan - Washington Steven Carmody - Brown Renee Frost - Michigan/Internet2 Ellen Vaughan - Internet2 Tom Barton - Memphis Ryan Muldoon - Wisconsin Michael Gettes - Georgetown Paul Hill - MIT Brett Didier - PNNL Ben Chinowsky (scribe) - Internet2 *Discussion* ...Ryan will be looking at the DoDHE assembly line... - MACE-Dir Advisory Board - Keith: I was hoping Ken would be here to suggest names for Advisory Board. Board to be modeled on PKI Labs Board. Chadwick, Hedberg, Kurt Zeilenga, Mark Smith, Peter Gietz have all said yes. Having the Board will help in dealings with the rest of the world, but what do we want them to do? PKI Labs Board members love to get together and exchange ideas, but are not giving direction to the Labs effort; we probably want more active steering from our Board. Steven: of the list of items on today's agenda, which would be of interest to them? Keith: could send agenda and ask them. if Ken will be here later, let's wait for him. Michael: Mark Wilcox, formerly of N. Texas and now of WebCT, is a good prospect -- he's knowledgeable and potentially cloutful as well. - picking up the pace for the summer - Keith: Ken says, and I agree, that another deliverable fairly soon would be good. inter-week calls would be a smaller group doing more focused work. Steven: so this call would become more status reports and less of a working call Keith: to some extent, yes Steven: we need to find some structure for dealing with the volume of work here; "reach out and tap people", "extract real commitments to do something by a certain date" Keith: I agree. Happening some, e.g. Tom Barton. are people willing to help organize "a more parallelized and more intensive effort" over the summer? Tom: "I'm a fool" [i.e. yes] Keith: Shibboleth-and-eduPerson agenda item is about getting experimental attributes for Shib -- who wants to make a priority of this? Bob: [AI] Bob will coordinate MACE-Dir's Shibboleth work over the summer. Keith: how about VidMid? Michael: DoD is priority 10 for me; vidmid is 7 Steven: could we coopt a vidmid person to "worry about this for us"? Keith: I'm looking for people to step up to a "subgroup coordinator role" Michael: I don't want to be solely responsible for VidMid, but I'd be happy to share this role with Bob and Ken Keith: want owners, not pushing now because still in preferences-collecting phase. for VidMid, Tyler? Ben: my confident guess is that he'd be willing Steven: do we think Tyler could take ownership of the process, and shepherd to recommendations? Ben: we'd certainly want to ask him, but yes Bob: but he really wants help from directories people (others concur) Michael: [AI] Michael will coordinate MACE-Dir's VidMid work over the summer. Keith: GridPerson? Brett? Brett: [AI] Brett will coordinate MACE-Dir's GridPerson work over the summer. Right now priority is comparison of schema. Keith: could also be a focus for Advisory Board. DoDHE? Michael, Ryan: [AI] Michael and Ryan will coordinate MACE-Dir's DoDHE work over the summer. Keith: Chadwick's proposals -- integrating into X.521 -- fairly short term Michael: yes, but some degree of writeup involved. Keith: OK, we'll try to work that one into calls. Groups? Tom: [AI] Tom will coordinate MACE-Dir's groups work over the summer. Keith: queued agenda items? web site? Ben: [AI] Ben will get v1.0 of the MACE-Dir web site posted before the June 25 MACE-Dir call. Keith, Ryan, Ben: [AI] Keith and Ryan will send Ben content for the MACE-Dir web site; Ben will arrange for write access for Keith and Ryan; all three will be co-maintainers of the site. Keith, Ben: [AI] Keith and Ben will maintain a list of queued MACE-Dir agenda items on the MACE-Dir web site. Bob, Michael, Steven: we want the site up soon Renee: how far back into the minutes should we post? Michael: I suggest back to start of groups discussion (general agreement) Re who can update the site -- the Internet2 site is going to be directory-enabled. Steven: I'd like to get Mike LaHaye to write up this effort -- could be another chapter of the LDAP Recipe. Keith: yes, we should have an eating-our-own-dogfood agenda item on a future call. Bob: agenda item for the next call, yes. ... Keith: per Steven, what do we want to see happen MACE-Dir-wide in the next 90 days? Michael: I'd also like to hear what people's local issues are Keith: can you go first? ... Steven: one of the people in uPortal... Bob: guy from Penn State saying he was using the Howard Strauss formulas...bad idea Steven: much of the uPortal code is "more proof of concept than anything else" -- wanted to look at storing some info in LDAP -- if this guy writes code for uPortal, it's something we want to stay connected with...we want to help them succeed. making transition. Tom: I have the Penn State mail -- sent to Steven and cc'd to MACE-Dir on June 4. ... Keith: issue of what goes where in directories...relates to Michael's stitched-directories mail. Michael: attributeIntegrityInfo attribute is supposed to do much of what I described there -- rumor has it that DOD and NSA make use of it, but I haven't tracked down any details yet. ... Keith: how many objects to describe a router again? Michael: almost 3,000 Keith: rathole -- I've added it to the list of queued agenda items Steven: know of any experts in this area? a bunch of apps, each 1) wanting to see data its own way, 2) wanting to store its own data, and 3) needing to work with data common to all apps Michael: I talked to a guy from JA-SIG; there's Mark Wilcox of WebCT; "answer may be not that many people" Keith: Dirk and Scott Fullerton are main portal people here ... Steven: maybe we want to start a discussion list Tom: feasible to harvest schema extensions associated with apps -- Keith: "you got it" Tom: -- and post them on the site. allow yourself independence of attributes in case apps take different courses. Keith: it does seem like we're in the collecting and posting phase. we've got the right first idea anyway. Bob: sounds a bit too much like our effort trying to write a paper for NAC -- comes down to "what are options for apps that want to directory-enable themselves" -- I know someone who's trying to write a book on it. I'd put the VidMid stuff in this category -- it comes down to directory-enabling the gatekeeper function. [departs] Steven: several of these things can be bundled under eduPerson 1.5: Shibboleth, VidMid, GridPerson, Chadwick's stuff, institutional-researchers/registrars/IMS conversations about attributes and names for things. Keith: [AI] Keith will make a list of things to include in eduPerson 1.5. Issue of affiliations. Michael: need to get the community behind us. Keith: if you just ask the IR and registrar folks, it'll be a long wait before you get anything you can use in an app. Steven: right, we want engineering, not institutional-research-style study ... Steven: one of the Shib pilot participants is going to be leveraging Affiliation to only allow access for faculty. Keith: [AI] Keith will organize a summer-long series of additional MACE-Dir conference calls, for smaller-group discussion of more narrowly-focused topics; these calls will take place on alternate weeks from the current MACE-Dir calls, at a time to be determined. *Action Items* [AI] Bob will coordinate MACE-Dir's Shibboleth work over the summer. [AI] Michael will coordinate MACE-Dir's VidMid work over the summer. [AI] Brett will coordinate MACE-Dir's GridPerson work over the summer. [AI] Michael and Ryan will coordinate MACE-Dir's DoDHE work over the summer. [AI] Tom will coordinate MACE-Dir's groups work over the summer. [AI] Ben will get v1.0 of the MACE-Dir web site posted before the June 25 MACE-Dir call. [AI] Keith and Ryan will send Ben content for the MACE-Dir web site; Ben will arrange for write access for Keith and Ryan; all three will be co-maintainers of the site. [AI] Keith and Ben will maintain a list of queued MACE-Dir agenda items on the MACE-Dir web site. [AI] Keith will make a list of things to include in eduPerson 1.5. [AI] Keith will organize a summer-long series of additional MACE-Dir conference calls, for smaller-group discussion of more narrowly-focused topics; these calls will take place on alternate weeks from the current MACE-Dir calls, at a time to be determined.