Browse Prior Art Database

A Method for Mitigating Namespace Collisions (RFC7304)

IP.com Disclosure Number: IPCOM000237734D
Publication Date: 2014-Jul-08
Document File: 8 page(s) / 7K

Publishing Venue

The IP.com Prior Art Database

Related People

W. Kumari: AUTHOR

Abstract

Collisions in the DNS occur in multiple ways. One common case is that an organization has used a subdomain (foo) of its primary domain (example.com) for corporate infrastructure, and then the string 'foo' is delegated as a Top-Level Domain (TLD). When an employee of the organization enters 'www.foo', is the goal to reach a machine in the internal namespace (www.foo.example.com) or the hostname 'www' in the 'foo' TLD?

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 41% of the total text.

Independent Submission                                         W. Kumari Request for Comments: 7304                                        Google Category: Informational                                        July 2014 ISSN: 2070-1721

               A Method for Mitigating Namespace Collisions

Abstract

   This document outlines a possible, but not recommended, method to    mitigate the effect of collisions in the DNS namespace by providing a    means for end users to disambiguate the conflict.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This is a contribution to the RFC Series, independently of any other    RFC stream.  The RFC Editor has chosen to publish this document at    its discretion and makes no statement about its value for    implementation or deployment.  Documents approved for publication by    the RFC Editor are not a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7304.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.

 Kumari                        Informational                     [Page 1]
 RFC 7304                DNS Collision Mitigation               July 2014

 Table of Contents

   1.  Introduction/Background . . . . . . . . . . . . . . . . . . .   2    2.  Mitigation  . . . . . . . . . . . . . . . . . . . . . . . . .   2    3.  Implementation/Disclaimers  . . . . . . . . . . . . . . . . .   3    4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3    5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction/Background

   Collisions in the DNS occur in multiple ways.  One common case is    that an organization has used a subdomain (foo) of its primary domain    (example.com) for corporate infrastructure, and then the string 'foo'    is delegated as a Top-Level Domain (TLD).  When an employee of the    organization enters 'www.foo', is the goal to reach a machine in the    internal namespace (www.foo.example.com) or the hostname 'www' in the    'foo' TLD?

   This document describe...