IETF Logo Mail Archive

Re: [tsvwg] Ben Campbell's No Objection on draft-ietf-tsvwg-ecn-experimentation-06: (with COMMENT)

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 19 October 2017 00:48 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32CD6126B6E for <tsvwg@ietfa.amsl.com>; Wed, 18 Oct 2017 17:48:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 D5GhWl05jusk for <tsvwg@ietfa.amsl.com>; Wed, 18 Oct 2017 17:48:14 -0700 (PDT)
Received: from mail-pg0-x236.google.com (mail-pg0-x236.google.com [IPv6:2607:f8b0:400e:c05::236]) (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 53F4D13314B for <tsvwg@ietf.org>; Wed, 18 Oct 2017 17:48:14 -0700 (PDT)
Received: by mail-pg0-x236.google.com with SMTP id s2so5658070pge.10 for <tsvwg@ietf.org>; Wed, 18 Oct 2017 17:48:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=UZt3eMelQaJ651U90QzRkjUHkAh1slbXwmbgRoZwII0=; b=JkvaT7c4keJozhjSZH0HIC8koHnFtUyqf01EC7yMZyAzCy8fhhseuztICBIpcEUJ/a N6tzuoJoyZWywkHR+ET7QSvZw5z1Bc3JKZ8pvIyO164DB7db4AJIuk+60YknXEBcULAS 6ivtzN6P66R/Tmy+m9cWllKECAbJRzpkibzzvO4jkwgbUgKwglRG/oYvPjVe6e+p3IA6 w+Q8oeB2+BAjavyRV3/8YarqDrx7Ojtkqs4pu8HuwyNM++JaO4maVoUgFpxLj55wCycn VlbLjI7GGLfY+zEU5rSD0P3jP4XhebbWYaLWCbMVmScwQ6U/ZvsDKpXf5prfn8cr3AKq o+BQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=UZt3eMelQaJ651U90QzRkjUHkAh1slbXwmbgRoZwII0=; b=UcUdLp1YyY04kzJ9ixmsSuMU2szk6a1Z9XM7xRA0xnCVwuSCYgTp5gw7LeL8KMHTGx swq+IBHJd8EcNhbKqGu05m15Y3kvXXKm3kF3O+jKmq+n0Aab6zHBoB50eWVLGslWJPgw CwifYtxUH22R9e1hq0Bq9CIgsPSlh7fjrL2/aLAqaCF5Ruu1YzYKmJjcLBC03WYNnSy5 MGcWGDh57/4T7Qa2Gri1cRL4tCrCPUI1sOa5+flDcSQMf9+iKW/YJl1GQz/tD2WfAKu6 ipLE7wRxCOaatNrVr+5qJcJjMZUGAGMU/fdjiM/Cd7j8Actal3oOWHWXqxCzl/Sr9xNr /Y4w==
X-Gm-Message-State: AMCzsaXw2d8sRM1Y38D82esNsapAY90tLI/CY3TvHXZnnMmCKcidghEc Igrit9920DB+izUb5Hh7RKHNdA==
X-Google-Smtp-Source: AOwi7QC3jdsO0W4M57NG83gFmGqQy6dBAa85SpVHnNfKElCBE13gSFOvBhRfLD3aQ1aQ7J3h7l8NOA==
X-Received: by 10.98.8.88 with SMTP id c85mr16107207pfd.330.1508374093636; Wed, 18 Oct 2017 17:48:13 -0700 (PDT)
Received: from ?IPv6:2406:e007:6d3c:1:28cc:dc4c:9703:6781? ([2406:e007:6d3c:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id m9sm23485151pff.26.2017.10.18.17.48.11 for <tsvwg@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 18 Oct 2017 17:48:12 -0700 (PDT)
To: tsvwg@ietf.org
References: <150656006611.13804.15109883563794101461.idtracker@ietfa.amsl.com> <CE03DB3D7B45C245BCA0D243277949362FCE3AC7@MX307CL04.corp.emc.com> <5528580C-EBDD-4EE9-9F3E-BFAF51F617AA@fastmail.fm> <CE03DB3D7B45C245BCA0D243277949362FCE69AE@MX307CL04.corp.emc.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <f58d4f1c-bad1-ae28-51f2-ca68ca4fd44a@gmail.com>
Date: Thu, 19 Oct 2017 13:48:17 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949362FCE69AE@MX307CL04.corp.emc.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/tjXd1FvsqsvluuGI1WEjXEZQGIQ>
Subject: Re: [tsvwg] Ben Campbell's No Objection on draft-ietf-tsvwg-ecn-experimentation-06: (with COMMENT)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Oct 2017 00:48:16 -0000

On 19/10/2017 10:38, Black, David wrote:
> That's a surprise, at least to me - I'm reasonably certain that we don't want to see this sort of experimentation done via ISE stream RFCs.

Ah, but that's why it's called the "independent" stream. It's rarely used that
way, but if there's a strong case that the IETF side of the house is being
unreasonably obstructive, the Independent stream is there as a safety valve.

The IRTF stream can also approve Experimental RFCs, iirc.

However, none of this can bypass BCP 26, so the applicable IANA policy
can trump the Independent and IRTF stream, if IANA registration is
needed.

   Brian
 
> 
> Thanks, --David
> 
>> -----Original Message-----
>> From: Alexey Melnikov [mailto:aamelnikov@fastmail.fm]
>> Sent: Wednesday, October 18, 2017 2:21 PM
>> To: Black, David <david.black@emc.com>
>> Cc: Ben Campbell <ben@nostrum.com>; The IESG <iesg@ietf.org>;
>> gorry@erg.abdn.ac.uk; draft-ietf-tsvwg-ecn-experimentation@ietf.org;
>> tsvwg-chairs@ietf.org; tsvwg@ietf.org
>> Subject: Re: [tsvwg] Ben Campbell's No Objection on draft-ietf-tsvwg-ecn-
>> experimentation-06: (with COMMENT)
>>
>> On 17 Oct 2017, at 22:49, Black, David <David.Black@dell.com> wrote:
>>
>>>> Speaking of which, there are several references to requiring experimental
>> RFCs.
>>>> Are those expected to be IETF stream RFCs?
>>> [David>] Yes, independent submissions (ISE stream) RFCs are
>> Informational, and cannot be published as Experimental.
>>
>> Independent Stream RFCs can be Informational or Experimental.
>>
> 
>

v2.46.0 | Report a Bug | By Email | System Status