[DNSOP] RFC 7871 on Client Subnet in DNS Queries

rfc-editor@rfc-editor.org Fri, 20 May 2016 20:29 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C722512D635; Fri, 20 May 2016 13:29:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.328
X-Spam-Level:
X-Spam-Status: No, score=-108.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 sj5F4-Uh9g9Q; Fri, 20 May 2016 13:29:42 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EC8912D637; Fri, 20 May 2016 13:29:42 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8CA26180004; Fri, 20 May 2016 13:29:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160520202922.8CA26180004@rfc-editor.org>
Date: Fri, 20 May 2016 13:29:22 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/anPp-dIh1GUTZ7RQwlTAI77dLvQ>
Cc: drafts-update-ref@iana.org, dnsop@ietf.org, rfc-editor@rfc-editor.org
Subject: [DNSOP] RFC 7871 on Client Subnet in DNS Queries
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 May 2016 20:29:50 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7871

        Title:      Client Subnet in DNS Queries 
        Author:     C. Contavalli, 
                    W. van der Gaast,
                    D. Lawrence,
                    W. Kumari
        Status:     Informational
        Stream:     IETF
        Date:       May 2016
        Mailbox:    ccontavalli@google.com,
                    wilmer@google.com,
                    tale@akamai.com,
                    warren@kumari.net
        Pages:      30
        Characters: 67651
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dnsop-edns-client-subnet-08.txt

        URL:        https://www.rfc-editor.org/info/rfc7871

        DOI:        http://dx.doi.org/10.17487/RFC7871

This document describes an Extension Mechanisms for DNS (EDNS0)
option that is in active use to carry information about the network
that originated a DNS query and the network for which the subsequent
response can be cached.  Since it has some known operational and
privacy shortcomings, a revision will be worked through the IETF for
improvement.

This document is a product of the Domain Name System Operations Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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