Re: [tsvwg] Last Call: <draft-ietf-tsvwg-port-use-06.txt> (Recommendations for Transport Port Number Uses) to Best Current Practice

gorry@erg.abdn.ac.uk Mon, 19 January 2015 09:02 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 015C61AD355; Mon, 19 Jan 2015 01:02:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.545
X-Spam-Level:
X-Spam-Status: No, score=-3.545 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 jxNxEuLZ-x5n; Mon, 19 Jan 2015 01:02:29 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 834181AD338; Mon, 19 Jan 2015 01:02:27 -0800 (PST)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 875B51B00537; Mon, 19 Jan 2015 09:02:12 +0000 (GMT)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Mon, 19 Jan 2015 09:02:16 -0000
Message-ID: <cb46e9b1a7aafed84df6177bb63462b8.squirrel@erg.abdn.ac.uk>
In-Reply-To: <CAKKJt-eBYdFsvweoLY3k8WzuN2kTXALonGdzwbepdXORT7PmZQ@mail.gmail.com>
References: <20141208235619.4442.37821.idtracker@ietfa.amsl.com> <54A990F4.9040509@isode.com> <54B95EDC.9000905@isi.edu> <54B9639F.7020905@isode.com> <54B965F9.6090704@isi.edu> <691f86d47ca683d48ab707d12e999534.squirrel@erg.abdn.ac.uk> <CE03DB3D7B45C245BCA0D243277949362E5919@MX104CL02.corp.emc.com> <CAKKJt-eBYdFsvweoLY3k8WzuN2kTXALonGdzwbepdXORT7PmZQ@mail.gmail.com>
Date: Mon, 19 Jan 2015 09:02:16 -0000
Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-port-use-06.txt> (Recommendations for Transport Port Number Uses) to Best Current Practice
From: gorry@erg.abdn.ac.uk
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/oxAMxTeuxA4txo2mLCx1z_ZVGyI>
X-Mailman-Approved-At: Tue, 20 Jan 2015 07:57:49 -0800
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "Black, David" <david.black@emc.com>, Alexey Melnikov <alexey.melnikov@isode.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jan 2015 09:02:31 -0000

I submitted a new shepherd writeup, based on this and what I found on the
list.

Gorry

> David and Gorry,
>
> On Sat, Jan 17, 2015 at 5:10 PM, Black, David <david.black@emc.com> wrote:
>
>> > >> My concerns is that BCP are commonly used by ADs to enforce
>> compliance.
>> > >> So I am wondering why this document is not just Informational?
>> > >
>> > > AFAIR, the WG wanted it to be BCP to be a stronger recommendation to
>> > > protocol designers than would be an Informational doc.
>> > >
>> > Yes the document was marked BCP on 2011-01-26 after WG discussion and
>> > advice from our ADs, but this was not based on offering advice to IANA
>> (as
>> > in RFC 6335), but rather guidance to protocol and applications
>> designers
>> > needing to use transport ports.
>>
>> I concur with Gorry's summary, and believe that BCP status is
>> appropriate.
>> I suggest teeing this concern (whether BCP vs. Informational is the
>> right
>> status for this sort of guidance document) up to the IESG for a
>> decision.
>>
>> In its ordinary English (dictionary) meaning, "best current practice"
>> certainly applies to this draft.  OTOH, the IETF notion of BCP has a
>> rather specific meaning and some definite implications in practice.
>> FWIW,
>> Alexey is not the only person who's made note of that concern wrt this
>> draft.
>>
>> In my view, the IESG owns the decision (and decision criteria) on what
>> should vs. should not be a BCP.  I think we should expand the draft
>> writeup
>> to note this concern (BCP vs. Informational status) as one that needs
>> IESG
>> attention and ask our ADs to ensure that it does get suitable IESG
>> attention.
>>
>> Much as I prefer to resolve open issues before IESG Evaluation, in this
>> case,
>> I think the IESG needs to make a decision, and it is within reason for
>> us
>> to
>> ask them to do so ;-).
>>
>> Thanks,
>> --David (as Gorry's tsvwg WG co-chair)
>>
>
>
> That sounds exactly right. I'll wait until you are happy with the shepherd
> writeup before I proceed.
>
> Spencer
>