[Arcing] Fwd: New Version Notification for draft-stw-whatsinaname-00.txt

[Suzanne Woolf <[e-mail]>]

Hi,

See below on a new draft that attempts to help make some sense of some general challenges around naming in internet protocols. It attempts to discuss some of the questions that arise around attempting to re-use DNS protocol and domain names in contexts separate from the global public DNS database and protocol.

There seemed to be strong feeling in the ARCING BOF in BA that we needed a document that could serve as advice to protocol designers and software implementers, although it's not entirely clear where such a document should live. It's *not* intended for adoption by DNSOP; although it may ultimately include advice to DNS operators, that's not the primary purpose.

Questions: 

1. Is something like this document useful?
2. What should it cover?
3. What status should we be aiming for: Informational? BCP?

thanks,
Suzanne

Begin forwarded message:

> From: [e-mail]
> Subject: New Version Notification for draft-stw-whatsinaname-00.txt
> Date: July 8, 2016 7:37:23 PM EDT
> To: "Suzanne Woolf" <[e-mail]>
> 
> 
> A new version of I-D, draft-stw-whatsinaname-00.txt
> has been successfully submitted by Suzanne Woolf and posted to the
> IETF repository.
> 
> Name:		draft-stw-whatsinaname
> Revision:	00
> Title:		Some Considerations on the Choice of Naming in IETF Protocols
> Document date:	2016-07-08
> Group:		Individual Submission
> Pages:		11
> URL:            https://www.ietf.org/internet-drafts/draft-stw-whatsinaname-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-stw-whatsinaname/
> Htmlized:       https://tools.ietf.org/html/draft-stw-whatsinaname-00
> 
> 
> Abstract:
>   From time to time, networking protocols need to be able to name
>   things used within the protocol, and resolve the names created or
>   referenced.  It's common for protocol designers in this predicament
>   to attempt to use domain names as the starting point for their
>   systems of names, and the DNS as the starting point for name
>   resolution.
> 
>   This is completely understandable-- domain names, and DNS resolution,
>   are well-established in both the expectations of network users and
>   developers, and well-supported by fielded software.  It also has
>   significant limitations.
> 
>   This document deals principally with the questions a protocol
>   designer or software developer should ask themselves about what
>   behavior they want from the names they use in the context of a new
>   protocol or scope for names.  Depending to the answers to these
>   questions, the answer may be that domain names will not meet the
>   constraints at hand.  Future versions of this draft will provide some
>   comments on alternatives.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
>