IETF Logo Mail Archive

Re: [DNSOP] ANAME in answer or additional section [issue #62]

"Michael J. Sheldon" <msheldon@godaddy.com> Tue, 11 June 2019 17:07 UTC

Return-Path: <msheldon@godaddy.com>
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 B5F61120094 for <dnsop@ietfa.amsl.com>; Tue, 11 Jun 2019 10:07:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=secureservernet.onmicrosoft.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 YJ9PAfm7oJ0J for <dnsop@ietfa.amsl.com>; Tue, 11 Jun 2019 10:07:04 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-eopbgr770134.outbound.protection.outlook.com [40.107.77.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 067C2120019 for <dnsop@ietf.org>; Tue, 11 Jun 2019 10:07:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=secureservernet.onmicrosoft.com; s=selector2-secureservernet-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=da7fKbKG2E6GzaHE6VmUlfWe7y6arrR0bM+XQCUt4yI=; b=IxTgk3dxQ5+8f40TT0OUlmvoG17XQo1lsQ4ly6loojkVJta3dxM+j4xU8IcQ7YjAp/1nYKLgd8ttmhIUQ71FyijviXNgk1Hrsu8mkTC3rc8YNbrEdPRxDbpxcxHJoY7htvzcH9f6a3lVYvnvxioEFGAictBUROT+ewIkNzMXuq4=
Received: from BYAPR02MB5190.namprd02.prod.outlook.com (20.177.124.15) by BYAPR02MB5895.namprd02.prod.outlook.com (20.179.63.225) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1965.15; Tue, 11 Jun 2019 17:07:02 +0000
Received: from BYAPR02MB5190.namprd02.prod.outlook.com ([fe80::589e:65df:84a:cd26]) by BYAPR02MB5190.namprd02.prod.outlook.com ([fe80::589e:65df:84a:cd26%6]) with mapi id 15.20.1965.017; Tue, 11 Jun 2019 17:07:01 +0000
From: "Michael J. Sheldon" <msheldon@godaddy.com>
To: "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: [DNSOP] ANAME in answer or additional section [issue #62]
Thread-Index: AQHVIDAvL1wCJyUZOU6gSyDKCF7wN6aWaPYAgABG0QA=
Date: Tue, 11 Jun 2019 17:07:00 +0000
Message-ID: <d21bcab2-736b-408d-5f88-3394c4c05124@godaddy.com>
References: <3b136e34-7ec0-e144-2c2a-0885185ec2b1@pletterpet.nl> <CA+nkc8CtGiykZU5fWRrvo5q1fFixk-udads=uEGKrmALYvuTaA@mail.gmail.com>
In-Reply-To: <CA+nkc8CtGiykZU5fWRrvo5q1fFixk-udads=uEGKrmALYvuTaA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2600:8800:2800:6f1:8b00:36db:61c6:bf6]
x-clientproxiedby: BY5PR03CA0008.namprd03.prod.outlook.com (2603:10b6:a03:1e0::18) To BYAPR02MB5190.namprd02.prod.outlook.com (2603:10b6:a03:68::15)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=msheldon@godaddy.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 56a6dd14-48f3-4407-a21a-08d6ee8f37ae
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:BYAPR02MB5895;
x-ms-traffictypediagnostic: BYAPR02MB5895:
x-microsoft-antispam-prvs: <BYAPR02MB5895D726C1468CBBB4698EC5DBED0@BYAPR02MB5895.namprd02.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 006546F32A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(346002)(136003)(396003)(366004)(376002)(5383002)(189003)(199004)(229853002)(2616005)(1730700003)(81156014)(186003)(53546011)(8676002)(5660300002)(64756008)(256004)(66946007)(14444005)(73956011)(66446008)(66556008)(66476007)(2906002)(6116002)(102836004)(81166006)(36756003)(46003)(8936002)(11346002)(446003)(14454004)(478600001)(305945005)(486006)(86362001)(31686004)(476003)(4744005)(2501003)(25786009)(6512007)(6486002)(68736007)(6246003)(6436002)(6916009)(99286004)(5640700003)(386003)(6506007)(52116002)(31696002)(76176011)(71190400001)(2351001)(71200400001)(7736002)(53936002)(316002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR02MB5895; H:BYAPR02MB5190.namprd02.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: godaddy.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: EYch1hmtt64k/fF/tSGkCWjN5cd4uf+9qNbg9Uoa4ugBa1gYDF+l3D6YMQjCNbARKXBrMPCip44nLsS5dA27MLbSRvmE320tu47PrlkZrYWVvuKgrLNSUbShR3UVRDjCoMEfn6+rk6goYwQUstfztc9azq+IjDcAT97T8kYTCNCufEHx/JalOtDTR/Lwf/nubrl+YBPA0idGI97nO3EAKZ9AiydB7ODQQAfvGO24F5qXZD73pVzoZJD5x0bvVcrLQKwcD3TDjvpheubHYhJVhdYBmqAtKvjWVUIjVQpQ38REWlZKNekUmLMkCis6w/em5MhpZ/j2iguPXZ1Cb0MhIT5n0oZJzCWQ6g6PFLu5bgkxEIuHxdSdCKr9b+UyofK8eEWk2lqfbEpojv1RY+D8yBsmZkvEJBw59t1ZEnHo/Kk=
Content-Type: text/plain; charset="utf-8"
Content-ID: <2F44FC3A61B6B64F9992D00D58416B0A@namprd02.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: godaddy.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 56a6dd14-48f3-4407-a21a-08d6ee8f37ae
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Jun 2019 17:07:01.3642 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: d5f1622b-14a3-45a6-b069-003f8dc4851f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: msheldon@godaddy.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR02MB5895
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/wucXyQjv7Fu5BDiqDQKS-gUKq_8>
Subject: Re: [DNSOP] ANAME in answer or additional section [issue #62]
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Jun 2019 17:07:07 -0000

On 6/11/19 5:53 AM, Bob Harold wrote:
> 
> If the camel was not already overloaded, then a cautious approach might
> be to put it in the additional section, *unless* there was a capability
> signal in the request that indicated that the requester would understand
> ANAME, or at least not have a problem if it were in the answer section. 
>  I am guessing that the capability signal would be some EDNS option, or
> perhaps an EDNS version.  Is that reasonable?

An EDNS capabililty signal would allow the ANAME to be sent in the
answer bare, no accompanying A/AAAA needed.

In absence of that signal, the authoritative *could* return the ANAME in
the additional, but not sure if there would be much value to it,
assuming the signal was standard behaviour.

-- 
Michael Sheldon
Dev-DNS Services
GoDaddy.com

v2.23.0 | Report a Bug | By Email