IETF Logo Mail Archive

Re: [dtn] working group last call on draft-ietf-dtn-bpbis

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 15 March 2017 23:06 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: dtn@ietfa.amsl.com
Delivered-To: dtn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDEF8129C2B for <dtn@ietfa.amsl.com>; Wed, 15 Mar 2017 16:06:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level:
X-Spam-Status: No, score=-4.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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=cs.tcd.ie
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 HTmDpdoLQUya for <dtn@ietfa.amsl.com>; Wed, 15 Mar 2017 16:06:13 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FA4F129C67 for <dtn@ietf.org>; Wed, 15 Mar 2017 16:06:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id C18BFBE38; Wed, 15 Mar 2017 23:06:08 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q4nP_bFE5Jx8; Wed, 15 Mar 2017 23:06:07 +0000 (GMT)
Received: from [10.87.48.75] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 4A621BE2F; Wed, 15 Mar 2017 23:06:07 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1489619167; bh=69a/2+lDIOsxjH/EyeNG+4ZkUqxYSu/neHaVzauReRE=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=1qqjsvj2a8DLE9fNCdMwgSy72+rn1APZhPxzgBycGGfC5bg728ELVB9kViV0Vdpki jy0vkbRy4/RHr1HGj82+ZkxhC8SLzAtLexTymV/MR3hqPcnCCjdx+bETdKSmi2CA0I mNtLaSIjPxhwuQeHflwYvyjekjE4VhB/5JUm3IcU=
To: Carsten Bormann <cabo@tzi.org>
References: <44B4919D-4283-4FDD-91E5-1EE5288D50AC@viagenie.ca> <b573e87b-e62b-56b6-7b89-6bcbde86dd82@cs.tcd.ie> <56D2A818-8EA5-4F51-AED4-2E7E27CC7538@tzi.org>
Cc: dtn <dtn@ietf.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <553366ff-2599-2ce4-0dfd-f4cbf6d9f17c@cs.tcd.ie>
Date: Wed, 15 Mar 2017 23:06:06 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <56D2A818-8EA5-4F51-AED4-2E7E27CC7538@tzi.org>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="7WmkM8FEqgDfLaVs8XhoxXC4pVMJu5701"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/c2cnMZJrJRnfWgUHbXs0w8wom6c>
Subject: Re: [dtn] working group last call on draft-ietf-dtn-bpbis
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <dtn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtn>, <mailto:dtn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn/>
List-Post: <mailto:dtn@ietf.org>
List-Help: <mailto:dtn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtn>, <mailto:dtn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Mar 2017 23:06:17 -0000


On 15/03/17 22:47, Carsten Bormann wrote:
> Will the IETF deprecate RFC 3986 and point to the WHATWG web page
> instead?

I certainly hope not and would argue strongly against any
proposal to do that.

I also don't think it's likely as we generally prefer stable
references and the whatwg thing is not that. While their
approach may be suitable for browsers and how those use URLs,
it'd not work for the many other things that refer to 3986.

But this isn't the right list for that squabble probably:-)

Cheers,
S.

v2.23.0 | Report a Bug | By Email