[UA-discuss] FW: Call for Participation: IAB workshop on Explicit Internet Naming Systems

[Mark Svancarek]

LOL, you are right.  July, not June.  Thanks.

From: ua-discuss-bounces at icann.org [mailto:ua-discuss-bounces at icann.org] On Behalf Of Andrew Sullivan
Sent: Tuesday, June 27, 2017 2:05 PM
To: UA-discuss at icann.org
Subject: Re: [UA-discuss] FW: Call for Participation: IAB workshop on Explicit Internet Naming Systems

The deadline is a month away, no?

--
Andrew Sullivan
Please excuse my clumbsy thums.

On Jun 27, 2017, at 17:00, Mark Svancarek via UA-discuss <ua-discuss at icann.org<mailto:ua-discuss at icann.org>> wrote:
Here’s a clarification of the problem statement.
I don’t think I have a position on this that I could have written up in time for the position paper deadline tomorrow.
Suggestions or concerns?

From: Ted Hardie [mailto:ted.ietf at gmail.com]
Sent: Tuesday, June 27, 2017 12:25 AM
To: Mark Svancarek <marksv at microsoft.com<mailto:marksv at microsoft.com>>
Subject: Re: Call for Participation: IAB workshop on Explicit Internet Naming Systems


On Mon, Jun 26, 2017 at 1:31 PM, Mark Svancarek <marksv at microsoft.com<mailto:marksv at microsoft.com>> wrote:
Ted, What are real world some examples of this?
 Because there is no common facility for varying the resolution method in the URI structure, those naming systems must either mint new URI schemes for each resolution service or infer the resolution method from a reserved name or pattern.
 The most recent example in the IETF came up in the reservation of .onion.  The system envisioned there uses the TOR system for node resolution, rather than the DNS.  Reserving that name was a very long process in which a lot of discussion was needed, and it is clear the model does not scale well.  One other option considered was minting URI schemes like https-tor://tor-node/, but they would need a new scheme for every application wanting to use the resolution (so email, xmpp, etc. would each need to be created and deployed).  Getting deployment of those was seen to be even harder.
I hope this example helps illustrate the problem,
regards,
Ted

Ted

From: Peter Constable
Sent: Monday, June 26, 2017 8:31 AM
To: Shawn Steele <Shawn.Steele at microsoft.com<mailto:Shawn.Steele at microsoft.com>>; Mark Svancarek <marksv at microsoft.com<mailto:marksv at microsoft.com>>
Subject: FW: Call for Participation: IAB workshop on Explicit Internet Naming Systems

You’ve probably seen this, but just in case…

From: Unicore [mailto:unicore-bounces at unicode.org] On Behalf Of Lisa Moore via Unicore
Sent: Sunday, June 25, 2017 8:25 PM
To: unicore at unicode.org<mailto:unicore at unicode.org>
Subject: Fwd: Call for Participation: IAB workshop on Explicit Internet Naming Systems


For anyone who might be interested, please check the info at the IAB link below.

Thanks,

Lisa


-------- Forwarded Message --------
Subject:

Call for Papers

Date:

Sun, 25 Jun 2017 04:29:33 -0700

From:

Ted Hardie <ted.ietf at gmail.com><mailto:ted.ietf at gmail.com>

To:

lisa at unicode.org<mailto:lisa at unicode.org>, Michel SUIGNARD <michel at suignard.com><mailto:michel at suignard.com>


Hi Lisa, Michel,
I mentioned to each of you the workshop that the IAB is planning; the CFP is now out:

https://www.iab.org/2017/06/22/call-for-participation-iab-workshop-on-explicit-internet-naming-systems/<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iab.org%2F2017%2F06%2F22%2Fcall-for-participation-iab-workshop-on-explicit-internet-naming-systems%2F&data=02%7C01%7Cpetercon%40microsoft.com%7Cf42f8b49ab374ca4bdcf08d4bc43745d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636340445285877390&sdata=yPwib235anETep5SHHdnLronBI1RZvyi3h7KqE7I7fs%3D&reserved=0>
I'd be happy for you to circulate it to folks in the Unicode world who might be able to contribute.
regards,
Ted

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ua-discuss/attachments/20170627/4cccbc18/attachment.html>