IETF Logo Mail Archive

Re: [sidr] Alexey Melnikov's Discuss on draft-ietf-sidr-publication-10: (with DISCUSS and COMMENT)

Randy Bush <randy@psg.com> Sun, 05 February 2017 06:53 UTC

Return-Path: <randy@psg.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74B60129497; Sat, 4 Feb 2017 22:53:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level:
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] 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 8xmEpD0xD1bT; Sat, 4 Feb 2017 22:53:14 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 8F07A129488; Sat, 4 Feb 2017 22:53:14 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1caGhD-0000QB-6t; Sun, 05 Feb 2017 06:53:11 +0000
Date: Sun, 05 Feb 2017 15:53:07 +0900
Message-ID: <m2wpd52koc.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
In-Reply-To: <m2y3xl2m5v.wl-randy@psg.com>
References: <148442017790.24124.2732462706586628755.idtracker@ietfa.amsl.com> <20170131001321.2DFE04664F1A@minas-ithil.hactrn.net> <77892F06-8A7D-46EE-9287-8DFDEDE0545D@fastmail.fm> <m2y3xl2m5v.wl-randy@psg.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/N71XqzZ5l-jC3oG42PY69ERYsMg>
Cc: Rob Austein <sra@hactrn.net>, morrowc@ops-netman.net, sidr-chairs@ietf.org, The IESG <iesg@ietf.org>, sidr@ietf.org, draft-ietf-sidr-publication@ietf.org
Subject: Re: [sidr] Alexey Melnikov's Discuss on draft-ietf-sidr-publication-10: (with DISCUSS and COMMENT)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Feb 2017 06:53:15 -0000

>>>> 4) How can URI of the service be discovered?
>>> Out of scope, but draft-ietf-sidr-oob-setup would be one way.
>> I was thinking that defining a .well-known HTTP URI prefix would be a
>> good idea
> it rarely is.  in this case it is a really bad idea.  the services are
> not associated with the domain name; it is a coincidence.

<blush>  a friend "suggested" i be clearer.  :)

i run a publication server.  a half dozen CAs publish there.  only one
of the CAs has a domain name related to that of the publication server.

and having to futz around with the dns would be a non-useful pita while
provisioning.

to be clear, this stuff has nothing to do with bgp or the dns, unlike
92.3% of the rest of the internet :)

randy

v2.23.0 | Report a Bug | By Email