RFC 7830 on The EDNS(0) Padding Option

rfc-editor@rfc-editor.org Tue, 10 May 2016 22:52 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 E8F1C12D120; Tue, 10 May 2016 15:52:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.898
X-Spam-Level:
X-Spam-Status: No, score=-107.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996, 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 LxRK_g5_xi0T; Tue, 10 May 2016 15:52:56 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52D8712B00A; Tue, 10 May 2016 15:52:56 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 59FB1180004; Tue, 10 May 2016 15:52:02 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7830 on The EDNS(0) Padding Option
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160510225202.59FB1180004@rfc-editor.org>
Date: Tue, 10 May 2016 15:52:02 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/s0gBmSWnnQQZycNXCx90y3f9xlQ>
Cc: drafts-update-ref@iana.org, dns-privacy@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 10 May 2016 22:52:58 -0000

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

        
        RFC 7830

        Title:      The EDNS(0) Padding Option 
        Author:     A. Mayrhofer
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2016
        Mailbox:    alex.mayrhofer.ietf@gmail.com
        Pages:      5
        Characters: 9520
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dprive-edns0-padding-03.txt

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

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

This document specifies the EDNS(0) "Padding" option, which allows
DNS clients and servers to pad request and response messages by a
variable number of octets.

This document is a product of the DNS PRIVate Exchange Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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