IETF Logo Mail Archive

Re: [DNSOP] Fwd: HTTPSSVC record draft

Ray Bellis <ray@bellis.me.uk> Mon, 08 July 2019 21:26 UTC

Return-Path: <ray@bellis.me.uk>
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 5E2341202A3 for <dnsop@ietfa.amsl.com>; Mon, 8 Jul 2019 14:26:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=portfast.net
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 gAMYPS6Iq3pz for <dnsop@ietfa.amsl.com>; Mon, 8 Jul 2019 14:26:52 -0700 (PDT)
Received: from mail.portfast.net (mail.portfast.net [IPv6:2a03:9800:20:1::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 907E4120086 for <dnsop@ietf.org>; Mon, 8 Jul 2019 14:26:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=portfast.net; s=dkim; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=FRe8bQA9dC0xXLpynSeUK0ElaCqqAfK4XzkTH68g8mQ=; b=L/jqM+Me3DmjTqsHRX+Ovjw2Si N5TUNw9d6m5PXq5iKGnLBEsKcA/YYFBkmu938gTLeqdsR7yHAWDhxguddf5k09Lszk0mtgfJj9oHs aWM45P88S7BcDU1qnEzpp1FnlD+heO6mLd3kSl926wQ99zGiujx2VRGcJYikzc/rl1Uw=;
Received: from [88.212.170.135] (port=64444 helo=Rays-MacBook-Pro.local) by mail.portfast.net ([188.246.200.9]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1hkb9t-0000uZ-Pg (Exim 4.89) (return-path <ray@bellis.me.uk>); Mon, 08 Jul 2019 21:26:49 +0000
To: Erik Nygren <erik+ietf@nygren.org>
Cc: IETF DNSOP WG <dnsop@ietf.org>
References: <CAKC-DJikByP+wX-GoD6ntpUWTbr6ioJzB4i8nGQL4NtPWePL3g@mail.gmail.com> <ae353a56-efe5-ce5d-1786-465fc0195071@bellis.me.uk> <CAKC-DJhaZoC2eNH8kP80Dfe-CnsOnRg6A6XDD7pWhwYdx8x7tA@mail.gmail.com>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <e90d08d5-4327-b349-eb03-92d7868f7780@bellis.me.uk>
Date: Mon, 08 Jul 2019 22:26:49 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <CAKC-DJhaZoC2eNH8kP80Dfe-CnsOnRg6A6XDD7pWhwYdx8x7tA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/hapx1AspW-smyCMvzMJ_mBH_0l8>
Subject: Re: [DNSOP] Fwd: HTTPSSVC record draft
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: Mon, 08 Jul 2019 21:27:02 -0000


On 08/07/2019 22:17, Erik Nygren wrote:

> For DNSOP folks, and ANAME proponents in-particular,
> I/we are especially interested in understanding if this would address
> enough of the customer use-cases driving ANAME were major
> browsers to implement support for HTTPSSVC, or would any
> limitations here cause problems there?

I'm personally not aware of any specific use-cases for ANAME that aren't 
  "I want to use my CDN's hostname alias but CNAME's rules prevent it".

That's not to say there aren't any, but if there are, I don't know what 
they are.

kind regards,

Ray

v2.23.0 | Report a Bug | By Email