Call for Participation, Workshop on Internet naming systems

IAB Chair <iab-chair@iab.org> Thu, 22 June 2017 20:53 UTC

Return-Path: <iab-chair@iab.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0BF312869B; Thu, 22 Jun 2017 13:53:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.899
X-Spam-Level:
X-Spam-Status: No, score=-2.899 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XfFyvwi7Jl46; Thu, 22 Jun 2017 13:53:20 -0700 (PDT)
Received: from thornhill.mtv.corp.google.com (unknown [IPv6:2620:0:1000:4200:9151:c8f9:67fc:ff95]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id A2C3512420B; Thu, 22 Jun 2017 13:53:20 -0700 (PDT)
To: iab@iab.org, ietf-announce@ietf.org, ietf@ietf.org
From: IAB Chair <iab-chair@iab.org>
Subject: Call for Participation, Workshop on Internet naming systems
Message-ID: <9afa1487-e1f7-8758-7ead-ab8114b822ed@iab.org>
Date: Thu, 22 Jun 2017 13:53:20 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------6467FA8D96CB5DD811613044"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/2Fnryua4hbGn_8dXvNosVywkhSM>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jun 2017 20:53:23 -0000

Call for Participation

IAB workshop on Explicit Internet Naming Systems

Internet namespaces relyon Internet connected systems sharing a common 
set of assumptions on the scope, method of resolution, and uniqueness of 
the names.    That set of assumption allowed the creation of URIs and 
other systems which presumed that you could authoritatively identify a 
service using an Internet name, a service port, and a set of 
locally-significant path elements.

There are now multiple challenges to maintaining that commonality of 
understanding.

  * Some naming systems wish to use URIs to identify both a service and
    the method of resolution used to map the name to a serving node.
      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.  Both methods are currently
    difficult and costly, and the effort thus scales poorly.
  * Users’ intentions to refer to specific names are now often expressed
    in voice input, gestures, and other methods which must be
    interpreted before being put into practice.  The systems which carry
    on that interpretation often infer which intent a user is
    expressing, and thus what name is meant, by contextual elements.
      Those systems are linked to existing systems who have no access to
    that context and which may thus return results or create security
    expectations for an unintended name.

  * Unicode allows for both combining characters and composed characters
    when local language communities have different practices.  When
    these do not have a single normalization, context is required to
    determine which to produce or assume in resolution.  How can this
    context be maintained in Internet systems?

While any of these challenges could easily be the topic of a stand-alone 
effort, this workshop seeks to explore whether there is a common set of 
root problems in the explicitness of the resolution context, heuristic 
derivation of intent, or language matching. If so, it seeks to identify 
promising areas for the development of new, more explicit naming systems 
for the Internet.

We invite position papers on this topic to be submitted by July 28, 2017 
toename@iab.org <mailto:ename@iab.org>.    Decisions on accepted 
submissions will be made by August 11, 2017.

Proposed dates for the workshop are September 28th and 29th, 2017 and 
the proposed location is in the Pacific North West of North America. 
  Finalized logistics will be announced prior to the deadline for 
submissions.

Ted Hardie

for the IAB