Return-Path: X-Original-To: dns-privacy@ietfa.amsl.com Delivered-To: dns-privacy@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A87DE1299BE for ; Mon, 31 Oct 2016 14:40:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 apQxvACvKqYp for ; Mon, 31 Oct 2016 14:40:21 -0700 (PDT) Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 998AA1299BC for ; Mon, 31 Oct 2016 14:40:20 -0700 (PDT) Received: by mail-lf0-x231.google.com with SMTP id f134so108433380lfg.2 for ; Mon, 31 Oct 2016 14:40:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=Ih3ONJ+JT2k3T2EyJrlmruREdf21hm0K3dP2z95gVeo=; b=fEABTrYhEGjsFCxBTDMB9EkQQ6bB6c5NxxFXQH4BID9vNTPNcMdAvqcnucyUQ+7IhR KKX3tRQ9US5oitbtBlYeJNF2OlV/jtt1FQgDs4LE9Og6KgC1OcQO7KqqVZJwXYVcAjR8 srYrjRFboso/cTjogT/yW1qfhGc55J0cfn6eLnxpXe6zQ+pYAWNvZqszukYQcHJgLqMy Z+d5zXtAw1ACSCCXJCV9yAiCV9psdl7BynH9qrvQH0E4StMhSemujLl1oMx4Jcs6mhlI WSaB8vYnNjsgirSqIKfHNiGl80PqssslT5Xp4u0cHyK6NuOhS3EA6xG1HvKWN9SjQPeJ TI+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Ih3ONJ+JT2k3T2EyJrlmruREdf21hm0K3dP2z95gVeo=; b=hjskfi660QVc16RsXGFMhWLG8y4AGKQQuG05yiGgqA5yPpf5eU2QqXJHjY6fCY/cvJ jKzeJb+03IBX5t1Jr09wpcXQSq6aCjG7giJUBEKLKYhMlvqCLxWwwLVlDrFRCbbnCCSO X2vSqOJXDe+4W8BCIfdB4NCjoORfX/LODHs4lzkPWVSuWQrRxwYK55Dkkr0hmkOcmhoi C2Tl/lhVhdygWMrOiNybmaKCzuIVoF1Ygzr64oZKNgpgwJLLIM39kj0/3YujcZahaECB PMGiT3KP27IRV+/lNLUKx4qtqno98jCR8pvxsZTg+a+EKk9cO1pxQTvfPkPyXqawTu8T 5wSQ== X-Gm-Message-State: ABUngvcd+ooHKQI6C8dbye2IKrrNJHboRJIwlzr42CD+31z0JbAsk8GR59mMMJkmEOv2JnOwOFmfIyIGMOuOOQ== X-Received: by 10.25.153.75 with SMTP id b72mr15610816lfe.112.1477950018507; Mon, 31 Oct 2016 14:40:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.114.97.9 with HTTP; Mon, 31 Oct 2016 14:40:17 -0700 (PDT) From: Alexander Mayrhofer Date: Mon, 31 Oct 2016 22:40:17 +0100 Message-ID: To: dns-privacy@ietf.org Content-Type: multipart/alternative; boundary=001a11402012d957de0540300df4 Archived-At: Subject: [dns-privacy] ENDS0 Padding Profile: Rough first draft X-BeenThere: dns-privacy@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2016 21:40:22 -0000 --001a11402012d957de0540300df4 Content-Type: text/plain; charset=UTF-8 Hi, I've posted a first rough cut of a "Padding Profile" draft, describing strategies regarding EDNS0 padding size (which we specifically did *not* address in RFC 7830): https://tools.ietf.org/html/draft-mayrhofer-dprive-padding-profile-00 It's more like a "strawman proposal" rather than a polished document in the current version, but i'm more than happy to talk about it in Seoul if we have time. See the full I-D announcement below. best, Alex A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Padding Profiles for EDNS(0) Author : Alexander Mayrhofer Filename : draft-mayrhofer-dprive-padding-profile-00.txt Pages : 6 Date : 2016-10-31 Abstract: RFC 7830 specifies the EDNS0 'Padding' option, but does not specify the amount of padding to be used in specific applications. This memo lists the possible options ("Padding Profiles"), discusses the implications of each of these options, and provides implementation guidance. The IETF datatracker status page for this draft is:https://datatracker.ietf.org/doc/draft-mayrhofer-dprive-padding-profile/ --001a11402012d957de0540300df4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

I've posted a fir= st rough cut of a "Padding Profile" draft, describing strategies = regarding EDNS0 padding size (which we specifically did *not* address in RF= C 7830):

https://tools.ietf.org/html/draft-mayrhofer-dprive-p= adding-profile-00

It's more like a "strawman prop= osal" rather than a polished document in the current version, but i= 9;m more than happy to talk about it in Seoul if we have time. See the full= I-D announcement below.

best,
Alex

= 

A New Internet-Draft is available fr=
om the on-line Internet-Drafts directories.


        Title           : Padding Profiles for EDNS(0)
        Author          : Alexander Mayrhofer
	Filename        : draft-mayrhofer-dprive-padding-profile-00.txt
	Pages           : 6
	Date            : 2016-10-31

Abstract:
   RFC 7830 specifies the EDNS0 'Padding' option, but does not spec=
ify
   the amount of padding to be used in specific applications.  This memo
   lists the possible options ("Padding Profiles"), discusses the
   implications of each of these options, and provides implementation
   guidance.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-mayrhofer-dprive-padding-p=
rofile/
--001a11402012d957de0540300df4--