RFC 6593 on Service Undiscovery Using Hide-and-Go-Seek for the Domain Pseudonym System (DPS)
rfc-editor@rfc-editor.org Sun, 01 April 2012 16:05 UTC
Return-Path: <wwwrun@rfc-editor.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 7AA7911E8091 for <ietf-announce@ietfa.amsl.com>; Sun, 1 Apr 2012 09:05:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FM8QefHRTs1G for <ietf-announce@ietfa.amsl.com>; Sun, 1 Apr 2012 09:05:06 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 08EA211E808E for <ietf-announce@ietf.org>; Sun, 1 Apr 2012 09:05:06 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 36CDEB1E003; Sun, 1 Apr 2012 09:03:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6593 on Service Undiscovery Using Hide-and-Go-Seek for the Domain Pseudonym System (DPS)
From: rfc-editor@rfc-editor.org
Message-Id: <20120401160323.36CDEB1E003@rfc-editor.org>
Date: Sun, 01 Apr 2012 09:03:20 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sun, 01 Apr 2012 16:05:06 -0000
A new Request for Comments is now available in online RFC libraries. RFC 6593 Title: Service Undiscovery Using Hide-and-Go-Seek for the Domain Pseudonym System (DPS) Author: C. Pignataro, J. Clarke, G. Salgueiro Status: Experimental Stream: Independent Date: 1 April 2012 Mailbox: cpignata@cisco.com, jclarke@cisco.com, gsalguei@cisco.com Pages: 8 Characters: 16752 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-joegonzalocarlos-service-hide-n-seek-00.txt URL: http://www.rfc-editor.org/rfc/rfc6593.txt With the ubiquitous success of service discovery techniques, curious clients are faced with an increasing overload of service instances and options listed when they browse for services. A typical domain may contain web servers, remote desktop servers, printers, file servers, video content servers, automatons, Points of Presence using artificial intelligence, etc., all advertising their presence. Unsurprisingly, it is expected that some protocols and services will choose the comfort of anonymity and avoid discovery. This memo describes a new experimental protocol for this purpose utilizing the Domain Pseudonym System (DPS), and discusses strategies for its successful implementation and deployment. This document defines an Experimental Protocol for the Internet community. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC