- DG-IDoT - mailman.kantarainitiative.org

iic
by Salvatore D'Agostino 07 Aug '15

07 Aug '15

1 0

Info for IDoT
by Frank.Mildner＠telekom.de 07 Aug '15

07 Aug '15

Dear all, Attached an overview of the global classification and nomenclature landscape in healthcare from GS1, for your information without any comments from my part ;) Hear you soon Mit freundlichen Grüßen / Viele Grüße / Best Regards Frank Mildner DEUTSCHE TELEKOM AG T-Labs (Research & Innovation) Dipl.-Ing. Frank Mildner Deutsche-Telekom-Allee 7, 64295 Darmstadt +4961515834747 (Tel.) +496151899838 (Fax) E-Mail: frank.mildner(a)telekom.de www.telekom.com<http://www.telekom.com/> Erleben, was verbindet. Die gesetzlichen Pflichtangaben finden Sie unter: www.telekom.com/pflichtangaben<http://www.telekom.com/pflichtangaben> Grosse Veränderungen fangen klein an - Ressourcen schonen und nicht jede E-Mail drucken. Von: dg-idot-bounces(a)kantarainitiative.org [mailto:dg-idot-bounces@kantarainitiative.org] Im Auftrag von Friese, Ingo Gesendet: Freitag, 7. August 2015 10:33 An: dg-idot(a)kantarainitiative.org Betreff: Re: [DG-IDoT] IDoT TeleCon I hope you are all doing well. I'd like to remind you that our next IDoT-call is coming up today. Today I want to give an update and discuss with you the Liaison request of IEEE P2413 (IoT Architecture WG)! I'm looking forward to talking to you! Best regards Ingo Date and Time * Friday, August 7th, at 7am PT (time chart)<http://www.timeanddate.com/worldclock/fixedtime.html?msg=IDoT+Conf+Call&iso…> * Voice: Skype: +99051000000481 or US +1-805-309-2350<tel:%2B1-805-309-2350> / Alternate Toll +1 (714) 551-9842<tel:%2B1%20%28714%29%20551-9842> (international dial-in lines<http://kantarainitiative.org/confluence/x/KYC_/>), room code 613-2898# * (Turbobridge call options<https://www.turbobridge.com/join.html>)

1 0

Common identity standard
by Ranjan Jain (ranjain) 28 Jul '15

28 Jul '15

Hey y¹all, Hope everyone is doing well. Just wanted to bounce a question which I¹m consistently getting asked around Identity, IoT perspective. Is there any industry standard in place or in works which can be used as a common standard across multiple identities. What I mean by this is that humans have SSN as an identity while a thermostat may have serial number while a network device may have a Mac ID as their identity. So, while individually they all have their own identity standard, when in the IoT world, all these entities start interacting with each other, how do we translate one identity into another or how will one identity interact with another identity in a standards way? Thanks Ranjan Ranjan Jain ARCHITECT.IT Information Technology ranjain(a)cisco.com Phone: +1 408 853 4396 Mobile: +1 408 627 9538 Cisco Systems, Inc. 400 East Tasman Drive San Jose California 95134 United States Cisco.com <http://www.cisco.com/> Think before you print. This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

12 31

NSTIC GSMA pilot and e-sim
by Salvatore D'Agostino 24 Jul '15

24 Jul '15

http://www.gsma.com/personaldata/mobile-connect http://www.engadget.com/2015/07/16/apple-samsung-e-sim/ Ingo, here are the mobile related things I mentioned on the call today. Sal Salvatore D'Agostino IDmachines LLC 1264 Beacon Street, #5 Brookline, MA 02446 USA http://www.idmachines.com <http://www.idmachines.com/> http://idmachines.blogspot.com <http://idmachines.blogspot.com/> @idmachines +1 617.201.4809 ph +1 617.812.6495 fax

1 0

Canceled: IDoT conf call
by Ingo.Friese＠telekom.de 08 Jul '15

08 Jul '15

Dear All, Unfortunately I have to cancel our Conf Call this week! Hope to hear you Friday the 24th of July! Best Ingo Dear all, I’d like to invite you to our biweekly IDoT call. Date and Time Date: Friday Time: 07:00 PT | 10:00 ET | 16:00 CEST * Dial-in Details Skype: +99051000000481 US Dial-In: +1-805-309-2350 Alternate Toll +1 (714) 551-9842 International Numbers: http://kantarainitiative.org/confluence/x/KYC_/ Conference ID: 613-2898 The following commands may be used participants during the conference call:+ *0 Plays menu of Keypad Commands *3 Promote to Host (if non-host) *5 Raise your hand *6 Mute yourself (toggle on/off) *# Private roll call of participants \ Mute music-on-hold (toggle on/off) TurboPhone (beta): https://www.turbobridge.com/join.html Works with Internet Explorer on Windows only SIP Access (using IP phone or soft phone) sip:bridge@turbobridge.com SIP URL details: https://www.turbobridge.com/help/Index.html?context=180

1 0

Start a new activity within IDoT DG
by Ingo.Friese＠telekom.de 18 Jun '15

18 Jun '15

Dear IDoT DG member, I'd like to start a new activity within our group. Here is my suggestion: Inspired by the document "Security Guidance for Early Adopters of the Internet of Things (IoT)" of CSA (Cloud Security Alliance) I'd like to see a similar document for "Identity Management in IoT", maybe not that detailed but in the same style. How to proceed: We all are from different companies with experiences from different industry sectors. All you have to do is to post your piece of recommendation or topic to the list or directly to our website. I gave an example by describing "Identifier vs. Addresses" (very often people asked me ...when we give every device in the world an IPv6 address all our problems are solved, right?....so I had to explain that just to have addresses is not enough) See below this mail or under this link: http://kantarainitiative.org/confluence/display/IDoT/Concepts+of+Identity+w… So, I'd like to encourage you to send few sentences about what you have experienced. Step by step we compile a whole document, a kind of "How to", "best practice"....somethings that is helpful and is interesting to read. Background: We started this group by looking for white spots in terms of identity. Here we have a paper and slide set givinga first overview. Then we had a look at discovery. But since we are a group with many different members this topic was not of interest for a significant number of members. On the other hand I'm not sure if it needs the 102nd architecture for IoT to develop. This is in many cases a theoretical work. I'd like to see a nice paper that is not that big, explaining the basics of identity in the IoT. Developer or other interested parties should take advantage of the paper and it should be kind of fun to read it. Hope you join me in this activity. Possible other topics could be: - Keep data processing local (privacy, roundtrip times) - Real time conditions (if needed) (authorization, authentication have to be fast) - Devices and relationships - Identities of different protocols - Smart authentication - Keep track of former transactions (block chain) - Proof of knowledge - .......etc My example: ################################## Addresses are not Identifier There is a fundamental difference between addresses and identifier of devices. Addresses determine the communication endpoint within a certain system. For example in the Internet Protocol an IP address is needed to establish a socket, a connection between devices. Identifiers can be understood as a dedicated, publicly known attribute or name for an identity, a person or a device. Typically, identifiers are valid within a specific domain. In the classic Web we have a Domain Name Service (DNS) mapping human readable Uniform Resource Identifier (URI) to IP-addresses. A browser for example resolves a website URI www.telekom.com<http://www.telekom.com> first. The actual connection between the browser and the Web server is then established by using the returned IP-address. There are several advantages in separating addresses and identifier. An IoT system or any kind of communication software could use addresses directly in theory but software updates become necessary if network interfaces or sensors break and need to be replaced. A mapping between identifier and addresses allows also a layer of indirection. This enables configurations like many identifiers pointing to one address. The address is only resolved when a certain condition is fulfilled. #################################################### Kind regards Ingo Friese Deutsche Telekom AG T-Labs (Research & Innovation) Dipl.-Ing. Ingo Friese Winterfeldtstr. 21, 10781 Berlin +4930835358148 (Phone) +49391580216849 (Fax) E-Mail: ingo.friese(a)telekom.de www.telekom.com<http://www.telekom.com/> Life is for sharing. You can find the obligatory information on www.telekom.com/compulsory-statement<http://www.telekom.com/compulsory-statement> Big changes start small - conserve resources by not printing every e-mail.

6 9

IDoT TeleCon
by Ingo.Friese＠telekom.de 12 Jun '15

12 Jun '15

Dear All, I hope you are all doing well. I'd like to remind you that our next IDoT-call is coming up today. I'm looking forward to talking to you! Best regards Ingo Date and Time * Friday, June 12th, at 7am PT (time chart)<http://www.timeanddate.com/worldclock/fixedtime.html?msg=IDoT+Conf+Call&iso…> * Voice: Skype: +99051000000481 or US +1-805-309-2350<tel:%2B1-805-309-2350> / Alternate Toll +1 (714) 551-9842<tel:%2B1%20%28714%29%20551-9842> (international dial-in lines<http://kantarainitiative.org/confluence/x/KYC_/>), room code 613-2898# * (Turbobridge call options<https://www.turbobridge.com/join.html>)

1 0

issues to dail in
by Ingo.Friese＠telekom.de 29 May '15

29 May '15

Hi I have issues to login, but hold on I'm still trying;-) Best Ingo

1 0

Canceled: IDoT conf call
by Ingo.Friese＠telekom.de 12 May '15

12 May '15

Due to a bank holiday. I’d like to cancel our IDoT conf call this week. Best Ingo

1 0

csa guidance on iot
by Salvatore D'Agostino 09 May '15

09 May '15

https://downloads.cloudsecurityalliance.org/whitepapers/Security_Guidance_fo r_Early_Adopters_of_the_Internet_of_Things.pdf have a good weekend, Sal

1 0

ADEPT paper
by j stollman 17 Apr '15

17 Apr '15

All, Attached is the ADEPT paper I mentioned on today's call. I also include another long paper which points out several issues with blockchain technology. For much of the paper, the author creates straw man and then picks them apart. But he also raises some real points that are informative. Jeff --------------------------------- Jeff Stollman stollman.j(a)gmail.com 1 202.683.8699 Truth never triumphs — its opponents just die out. Science advances one funeral at a time. Max Planck

2 1

IDoT conf call
by Ingo.Friese＠telekom.de 17 Apr '15

17 Apr '15

Dear all, I’d like to invite you to our biweekly IDoT call. Date and Time Date: Friday Time: 07:00 PT | 10:00 ET | 16:00 CEST * Dial-in Details Skype: +99051000000481 US Dial-In: +1-805-309-2350 Alternate Toll +1 (714) 551-9842 International Numbers: http://kantarainitiative.org/confluence/x/KYC_/ Conference ID: 613-2898 The following commands may be used participants during the conference call:+ *0 Plays menu of Keypad Commands *3 Promote to Host (if non-host) *5 Raise your hand *6 Mute yourself (toggle on/off) *# Private roll call of participants \ Mute music-on-hold (toggle on/off) TurboPhone (beta): https://www.turbobridge.com/join.html Works with Internet Explorer on Windows only SIP Access (using IP phone or soft phone) sip:bridge@turbobridge.com SIP URL details: https://www.turbobridge.com/help/Index.html?context=180

1 0

IDoT DG TeleCOn
by Ingo.Friese＠telekom.de 17 Apr '15

17 Apr '15

Dear All, I hope you are all doing well. I’d like to remind you that our next IDoT-call is coming up today. I’m looking forward to talking to you! PS: It looks that there is a temporary time difference btw. European and American Summer time. We start 8pm PT. Best regards, Ingo Date and Time * Friday, March 20th, at 8am PT (time chart)<http://www.timeanddate.com/worldclock/fixedtime.html?msg=IDoT+Conf+Call&iso…> * Voice: Skype: +99051000000481 or US +1-805-309-2350<tel:%2B1-805-309-2350> / Alternate Toll +1 (714) 551-9842<tel:%2B1%20%28714%29%20551-9842> (international dial-in lines<http://kantarainitiative.org/confluence/x/KYC_/>), room code 613-2898# * (Turbobridge call options<https://www.turbobridge.com/join.html>) Agenda Smart discovery document, SXSW report AOB Kind regards Ingo Friese Deutsche Telekom AG T-Labs (Research & Innovation) Dipl.-Ing. Ingo Friese Winterfeldtstr. 21, 10781 Berlin +4930835358148<tel:%2B4930835358148> (Phone) +49391580216849<tel:%2B49391580216849> (Fax) E-Mail: ingo.friese(a)telekom.de<mailto:ingo.friese@telekom.de> www.telekom.com<http://www.telekom.com/> Life is for sharing. DEUTSCHE TELEKOM AG Supervisory Board: Prof. Dr. Ulrich Lehner (Chairman) Board of Management: René Obermann (Chairman), Reinhard Clemens, Niek Jan van Damme, Timotheus Höttges, Dr. Thomas Kremer, Claudia Nemat, Prof. Dr. Marion Schick Commercial register: Amtsgericht Bonn HRB 6794 Registered office: Bonn Big changes start small – conserve resources by not printing every e-mail. _______________________________________________ DG-IDoT mailing list DG-IDoT(a)kantarainitiative.org<mailto:DG-IDoT@kantarainitiative.org> http://kantarainitiative.org/mailman/listinfo/dg-idot

2 3

Personal Discovery Service
by Ingo.Friese＠telekom.de 16 Apr '15

16 Apr '15

Hi, I had a look at the discussion about personal discovery service within UMA. In fact we have a similar challenge in IDoT discussion group. We are about to describe a "smart" discovery service that can find objects by using relationships and context. The problem is: if someone asks the right questions he can gain a lot of personalor critical information. So we need a kind of authorization mechanism that controls "who is entitled to see/find which devices". Ingo From: wg-uma-bounces(a)kantarainitiative.org [mailto:wg-uma-bounces@kantarainitiative.org] On Behalf Of Justin Richer Sent: Donnerstag, 16. April 2015 05:42 To: George Fletcher Cc: wg-uma(a)kantarainitiative.org UMA Subject: Re: [WG-UMA] Personal Discovery Service I like that response for webfinger, but I think it's going to be something that UMA in general is going to have to deal with. UMA makes a lot of assumptions about how the API is set up, including that the initial call with no access token always returns an error. I think we can do better than that. Another bullet for UMA 2.0. :) (I'm trying to compile a list.) - Justin On Apr 14, 2015, at 9:34 AM, George Fletcher <george.fletcher(a)teamaol.com<mailto:george.fletcher@teamaol.com>> wrote: Great though Justin. You're right that its difficult to return public data and a pointer to how to get more data. However, in the unauthenticated webfinger case, you could return a link relation to the user's AS as this is pretty much public anyway and possibly a property that indicates that the discovery service is UMA protected. Thanks, George On 4/14/15 10:01 AM, Justin Richer wrote: I almost really like this. The one thing that I'd want out of a flow like this is public discovery information returned from the unauthenticated webfinger call in addition to the pointer to the AS. That way if a client is able to act on the public information it doesn't need to go through the authorization steps, but if it needs more access then it can step up. This is a common enough API pattern and it's something that I think UMA doesn't do very well at, currently. - Justin On Apr 13, 2015, at 1:18 PM, George Fletcher <george.fletcher(a)teamaol.com<mailto:george.fletcher@teamaol.com>> wrote: So I have a sequence diagram for combining webfinger and UMA. I'll embed and attach the image to this email and I can share the web sequence diagram text if anyone is interested. I'd really appreciate it if someone could validate this flow and make sure I didn't miss anything obvious. It doesn't cover every possible case of UMA but it should cover the default/normal flow. That said, there are still lots of things to consider such as should there be a relation based taxonomy within a vertical to make discovering different kinds of endpoints easier? How to represent a discoverable endpoint as a resource set? If the UMA AS and Discovery endpoint are the same server, should there be a way for the discovery flow to return an RPT to simplify things for callers? <webfinger+uma.png> Thanks, George -- Chief Architect AIM: gffletch Identity Services Engineering Work: george.fletcher(a)teamaol.com<mailto:george.fletcher@teamaol.com> AOL Inc. Home: gffletch(a)aol.com<mailto:gffletch@aol.com> Mobile: +1-703-462-3494 Blog: http://practicalid.blogspot.com<http://practicalid.blogspot.com/> Office: +1-703-265-2544 Twitter: http://twitter.com/gffletch <webfinger+uma.png>_______________________________________________ WG-UMA mailing list WG-UMA(a)kantarainitiative.org<mailto:WG-UMA@kantarainitiative.org> http://kantarainitiative.org/mailman/listinfo/wg-uma -- Chief Architect AIM: gffletch Identity Services Engineering Work: george.fletcher(a)teamaol.com<mailto:george.fletcher@teamaol.com> AOL Inc. Home: gffletch(a)aol.com<mailto:gffletch@aol.com> Mobile: +1-703-462-3494 Blog: http://practicalid.blogspot.com<http://practicalid.blogspot.com/> Office: +1-703-265-2544 Twitter: http://twitter.com/gffletch

1 0

interesting example off how law impacts iot
by Salvatore D'Agostino 27 Mar '15

27 Mar '15

So think of the implications of this. You have a drone flying down the road, gopro on your head while biking or a camera pointed at your front yard, cop pulls over speeder issues ticket in your camera's field of fiew, you just broke the law. (and maybe a year in jail), yikes. http://www.govtech.com/public-safety/Rules-for-Viewing-Police-Videos-in-Texa s-Depend-on-Who-is-Holding-the-Camera.html Salvatore D'Agostino IDmachines LLC 1264 Beacon Street, #5 Brookline, MA 02446 USA http://www.idmachines.com <http://www.idmachines.com/> http://idmachines.blogspot.com <http://idmachines.blogspot.com/> @idmachines +1 617.201.4809 ph +1 617.812.6495 fax

1 0

blog on iot
by Salvatore D'Agostino 26 Mar '15

26 Mar '15

http://www.computer.org/web/sensing-iot/content?g=53926943 <http://www.computer.org/web/sensing-iot/content?g=53926943&type=article&url Title=defining-the-internet-of-things&lf1=1241255974b275116052083b39045350> &type=article&urlTitle=defining-the-internet-of-things&lf1=1241255974b275116 052083b39045350 nice pic about wearables. Salvatore D'Agostino IDmachines LLC 1264 Beacon Street, #5 Brookline, MA 02446 USA http://www.idmachines.com <http://www.idmachines.com/> http://idmachines.blogspot.com <http://idmachines.blogspot.com/> @idmachines +1 617.201.4809 ph +1 617.812.6495 fax

1 0

Cloud Security Alliance Guidance IoT
by Salvatore D'Agostino 26 Mar '15

26 Mar '15

https://interact.cloudsecurityalliance.org/index.php/iot/Iot_Early_Guidance Maybe we could comment as a DG? Open to individuals in any case.T Salvatore D'Agostino IDmachines LLC 1264 Beacon Street, #5 Brookline, MA 02446 USA http://www.idmachines.com <http://www.idmachines.com/> http://idmachines.blogspot.com <http://idmachines.blogspot.com/> @idmachines +1 617.201.4809 ph +1 617.812.6495 fax

2 1

Fwd: story of interest
by j stollman 25 Mar '15

25 Mar '15

All, Perhaps there is an identity solution applicable to IoT already in development. This approach uses blockchain and is funded by some major VCs. http://www.coindesk.com/onename-raises-seed-funding-fuel-decentralized-iden… -- Jeff Stollman stollman.j(a)gmail.com 1 202.683.8699 Truth never triumphs — its opponents just die out. Science advances one funeral at a time. Max Planck

4 4

ISSA Journal - IDoT: Security & Privacy Challenges
by Simon Moffatt 25 Mar '15

25 Mar '15

Hi group This is a basic paper I had published in this months Information Systems Security Association Journal that focused on the privacy and security issues of the internet of things, with obviously a heavy lean on the identity of things. Comments welcome :-) Regards Simon -- ForgeRock <http://www.forgerock.com> *Simon Moffatt* Mob: +44 7903 347 240 Skype: simon.moffatt @simonmoffatt

4 4

news and interesting material
by Ingo.Friese＠telekom.de 24 Mar '15

24 Mar '15

Dear All, I put news and interesting material discussed during our last call to our web site. https://kantarainitiative.org/confluence/display/IDoT/Repository+for+backgr… Best Ingo

1 0

Use case submission
by Scott Shorter 24 Mar '15

24 Mar '15

Hello IRM WG, As promised on the last call, here are some use cases that I had sent to the Kantara Idenity of Things discussion group last year, dusted off and repackaged as IRM use cases. Sorry I can't attend the call today, but hopefully the contribution is helpful. Catch you next time. - Scott -- ============================================================== *Scott Shorter, Principal Security Engineer* Electrosoft *–* Fueling Customer Success Through Outstanding Value and Trust! *Woman-Owned, Minority-Owned Small Business | ISO 9001 | CMMI Level 2 * 1893 Metro Center Drive; Ste 228; Reston, VA 20190 (703) 437-9451 x21 (office); (240) 994-7793 (cell) sshorter(a)electrosoft-inc.com (Email); http://www.electrosoft-inc.com (Web) ==============================================================

1 0

NIST publication of timing issues that might have impact on IOT
by Ross Foard 20 Mar '15

20 Mar '15

Intro from the document. Our fast-approaching future of driverless cars and “smart” electrical grids will depend on billions of linked devices making decisions and communicating with split-second precision to prevent highway collisions and power outages. But a new report <http://www.nist.gov/manuscript-publication-search.cfm?pub_id=917942>* released by the National Institute of Standards and Technology (NIST) warns that this future could be stalled by our lack of effective methods to marry computers and networks with timing systems. http://www.nist.gov/pml/div688/timing-031915.cfm We have addressed some of these issues in the past in industrial controls systems (with real time OS) and (telecom infrastructure) with PTP (precision time protocol). -- Ross Foard (703) 728-1543 (cell) rfoard(a)gmail.com <https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=rfoard@gmail.com>

2 1

NISTIR 7823
by Scott Shorter 20 Mar '15

20 Mar '15

Hi all, As discussed on the call, here's the news I mentioned about NIST IR 7823: This month, the National Institute of Standards and Technology (NIST) published the final form of a document that Scott Shorter from Electrosoft coauthored with NIST scientist Michaela Iorga <http://www.nist.gov/itl/csd/iorga-michaela.cfm>. NIST Interagency Report (NISTIR) 7823, entitled “Advanced Metering Infrastructure Smart Meter Upgradeability Test Framework.” NISTIR 7823 provides test methods for determining compliance with the voluntary industry standards on firmware upgradeability published by the National Electrical Manufacturers Association (NEMA). The NEMA standard provides functional and security requirements for smart meters, upgrade management systems to upgrade firmware in a secure manner. NEMA SG-AMI 1-2009 <http://www.nema.org/Standards/Pages/Requirements-for-Smart-Meter-Upgradeabi…> was published 2009-09-25 to “[define] requirements for smart meter firmware upgradeability in the context of an advanced metering infrastructure system for industry stakeholders such as regulators, utilities and vendors.” It is currently distributed as part of NEMA's Smart Meter Standards Package <http://www.nema.org/Standards/Pages/Smart-Meter-Package.aspx> which is billed as requirements and guidance on electricity meteric within the United States. The test framework we developed is a very comprehensive test method for a fairly weakly specified standard, and in light of updated NIST guidance on protection of BIOS it is overdue for an update. Scott Shorter will be blogging this month on the topic of firmware upgradeability as a security feature, the ways that security feature can be abused, and recommended security considerations for when the firmware upgradeability standard is revisited, whether as an update by NEMA or if adopted as an ANSI C.12 standard. - Scott -- ============================================================== *Scott Shorter, Principal Security Engineer* Electrosoft *–* Fueling Customer Success Through Outstanding Value and Trust! *Woman-Owned, Minority-Owned Small Business | ISO 9001 | CMMI Level 2 * 1893 Metro Center Drive; Ste 228; Reston, VA 20190 (703) 437-9451 x21 (office); (240) 994-7793 (cell) sshorter(a)electrosoft-inc.com (Email); http://www.electrosoft-inc.com (Web) ==============================================================

1 0

Re: [DG-IDoT] [WG-IRM] Laws of Relationships
by Ian Glazer 09 Mar '15

09 Mar '15

And here I was going to propose "The Immutable and Universal True Commandments of Identity Relationship Management" :-) Totally agree with this thread. I like the idea of "principles" as a way of talking about this work. For those of you who have seen my talks on the subject have observed, I've really struggled with language that feels right. Talk to everyone tomorrow, i On Mon, Mar 9, 2015 at 6:12 AM, Robin Wilton <wilton(a)isoc.org> wrote: > As someone who attacked Kim’s Laws for the hubris of the label, I share > the concern. > > An alternative might be “Principles”… > > R > > Robin Wilton > Technical Outreach Director - Identity and Privacy > Internet Society > > email: wilton(a)isoc.org > Phone: +44 705 005 2931 > Twitter: @futureidentity > > On 8 Mar 2015, at 16:21, Salvatore D'Agostino <sal(a)idmachines.com> wrote: > > Yes, don’t disagree but I don’t think that is where the title is coming > from. I think the whole point was to play off of Kim’s “Laws” and say > there are new ones in play. There is a certain ring to laws and benefits > in terms of capturing audience. It probably gets more attention than > Design Requirements for Relationship Management. This is an initial work > and of even more interest to me is the mutability of the requirements as a > topic in play as opposed to the title of the document as a whole. One of > the things we may find is that the permutations of relationships mean that > even laws/requirements may need a bit of if, then. Among our next steps is > taking the document apart, ideally law by law but overall is fine too as we > look to reconstitute the “laws”. > > We can put this in play on Tuesday, will get an agenda out and look > forward to getting together then. Don’t forget to follow @irmwg and join > the linkedin group and contribute to the conversation there as well. > > Good balance of the weekend to all, > > Sal > > *From:* Susan Morrow [mailto:susan.morrow@avocosecure.com > <susan.morrow(a)avocosecure.com>] > *Sent:* Sunday, March 08, 2015 1:56 AM > *To:* j stollman > *Cc:* Salvatore D'Agostino; dg-idot(a)kantarainitiative.org > *Subject:* Re: [DG-IDoT] Laws of Relationships > > I agree with you Jeff and brought up the same issue about being immutable. > It also precludes the acceptance of fuzziness in relationships too. > I suppose the use of the word 'law' in technology has a different meaning > than the use of it in sciences like physics and chemistry. > > Susan > > > On 8 Mar 2015, at 05:35, j stollman <stollman.j(a)gmail.com> wrote: > > Ever since Kim Cameron's Laws of Identity, the industry seems to gravitate > towards the use of the term "Laws". But I think what this document really > is is a specification of design requirements for a new system(s) capable of > meeting the objectives stated in the introduction. > > I have no particular agita over these design requirements. But I feel > that framing them properly as design requirements, rather than laws, offers > flexibility to design alternative systems that may select only a subset or > explicitly violate one or more laws. At this early stage I prefer this > flexibility to the immutable sound of "Laws." > > Jeff > > On Fri, Mar 6, 2015 at 8:57 PM, Salvatore D'Agostino <sal(a)idmachines.com> > wrote: > Here is the link I mentioned, we also have a twitter handle for the group > of @irmwg and use the same for a hashtag #irmwg. > > > https://kantarainitiative.org/wp-content/uploads/2015/03/Kantara-Initiative… > > Other Kantara reports are here: > https://kantarainitiative.org/reports-recommendations/ > > Enjoy the weekend. > > Sal > > Salvatore D'Agostino > IDmachines LLC > 1264 Beacon Street, #5 > Brookline, MA 02446 > USA > http://www.idmachines.com > http://idmachines.blogspot.com > @idmachines > +1 617.201.4809 ph > +1 617.812.6495 fax > > > > _______________________________________________ > DG-IDoT mailing list > DG-IDoT(a)kantarainitiative.org > http://kantarainitiative.org/mailman/listinfo/dg-idot > > > > -- > Jeff Stollman > stollman.j(a)gmail.com > 1 202.683.8699 > > Truth never triumphs — its opponents just die out. > Science advances one funeral at a time. > Max Planck > > _______________________________________________ > DG-IDoT mailing list > DG-IDoT(a)kantarainitiative.org > http://kantarainitiative.org/mailman/listinfo/dg-idot > > _______________________________________________ > WG-IRM mailing list > WG-IRM(a)kantarainitiative.org > http://kantarainitiative.org/mailman/listinfo/wg-irm > > > > _______________________________________________ > WG-IRM mailing list > WG-IRM(a)kantarainitiative.org > http://kantarainitiative.org/mailman/listinfo/wg-irm > > -- Ian Glazer Senior Director, Identity +1 202 255 3166 @iglazer <https://twitter.com/iglazer>

1 0

Re: [DG-IDoT] [WG-IRM] Laws of Relationships
by Susan Morrow Avoco Secure 09 Mar '15

09 Mar '15

Perfect word From: Robin Wilton [mailto:wilton@isoc.org] Sent: 09 March 2015 10:12 To: Salvatore D'Agostino Cc: Susan Morrow; j stollman; wg-irm(a)kantarainitiative.org; dg-idot(a)kantarainitiative.org Subject: Re: [WG-IRM] [DG-IDoT] Laws of Relationships As someone who attacked Kim's Laws for the hubris of the label, I share the concern. An alternative might be "Principles". R Robin Wilton Technical Outreach Director - Identity and Privacy Internet Society email: wilton(a)isoc.org Phone: +44 705 005 2931 Twitter: @futureidentity On 8 Mar 2015, at 16:21, Salvatore D'Agostino <sal(a)idmachines.com> wrote: Yes, don't disagree but I don't think that is where the title is coming from. I think the whole point was to play off of Kim's "Laws" and say there are new ones in play. There is a certain ring to laws and benefits in terms of capturing audience. It probably gets more attention than Design Requirements for Relationship Management. This is an initial work and of even more interest to me is the mutability of the requirements as a topic in play as opposed to the title of the document as a whole. One of the things we may find is that the permutations of relationships mean that even laws/requirements may need a bit of if, then. Among our next steps is taking the document apart, ideally law by law but overall is fine too as we look to reconstitute the "laws". We can put this in play on Tuesday, will get an agenda out and look forward to getting together then. Don't forget to follow @irmwg and join the linkedin group and contribute to the conversation there as well. Good balance of the weekend to all, Sal From: Susan Morrow [ <mailto:susan.morrow@avocosecure.com> mailto:susan.morrow@avocosecure.com] Sent: Sunday, March 08, 2015 1:56 AM To: j stollman Cc: Salvatore D'Agostino; <mailto:dg-idot@kantarainitiative.org> dg-idot(a)kantarainitiative.org Subject: Re: [DG-IDoT] Laws of Relationships I agree with you Jeff and brought up the same issue about being immutable. It also precludes the acceptance of fuzziness in relationships too. I suppose the use of the word 'law' in technology has a different meaning than the use of it in sciences like physics and chemistry. Susan On 8 Mar 2015, at 05:35, j stollman < <mailto:stollman.j@gmail.com> stollman.j(a)gmail.com> wrote: Ever since Kim Cameron's Laws of Identity, the industry seems to gravitate towards the use of the term "Laws". But I think what this document really is is a specification of design requirements for a new system(s) capable of meeting the objectives stated in the introduction. I have no particular agita over these design requirements. But I feel that framing them properly as design requirements, rather than laws, offers flexibility to design alternative systems that may select only a subset or explicitly violate one or more laws. At this early stage I prefer this flexibility to the immutable sound of "Laws." Jeff On Fri, Mar 6, 2015 at 8:57 PM, Salvatore D'Agostino < <mailto:sal@idmachines.com> sal(a)idmachines.com> wrote: Here is the link I mentioned, we also have a twitter handle for the group of @irmwg and use the same for a hashtag #irmwg. <https://kantarainitiative.org/wp-content/uploads/2015/03/Kantara-Initiative -IRM-Laws-of-Relationship-Final-Report-v1.0.pdf> https://kantarainitiative.org/wp-content/uploads/2015/03/Kantara-Initiative- IRM-Laws-of-Relationship-Final-Report-v1.0.pdf Other Kantara reports are here: <https://kantarainitiative.org/reports-recommendations/> https://kantarainitiative.org/reports-recommendations/ Enjoy the weekend. Sal Salvatore D'Agostino IDmachines LLC 1264 Beacon Street, #5 Brookline, MA 02446 USA <http://www.idmachines.com/> http://www.idmachines.com <http://idmachines.blogspot.com/> http://idmachines.blogspot.com @idmachines <tel:%2B1%20617.201.4809> +1 617.201.4809 ph <tel:%2B1%20617.812.6495> +1 617.812.6495 fax _______________________________________________ DG-IDoT mailing list <mailto:DG-IDoT@kantarainitiative.org> DG-IDoT(a)kantarainitiative.org <http://kantarainitiative.org/mailman/listinfo/dg-idot> http://kantarainitiative.org/mailman/listinfo/dg-idot -- Jeff Stollman <mailto:stollman.j@gmail.com> stollman.j(a)gmail.com 1 202.683.8699 Truth never triumphs - its opponents just die out. Science advances one funeral at a time. Max Planck _______________________________________________ DG-IDoT mailing list <mailto:DG-IDoT@kantarainitiative.org> DG-IDoT(a)kantarainitiative.org <http://kantarainitiative.org/mailman/listinfo/dg-idot> http://kantarainitiative.org/mailman/listinfo/dg-idot _______________________________________________ WG-IRM mailing list <mailto:WG-IRM@kantarainitiative.org> WG-IRM(a)kantarainitiative.org <http://kantarainitiative.org/mailman/listinfo/wg-irm> http://kantarainitiative.org/mailman/listinfo/wg-irm

1 0