IETF Logo Mail Archive

Re: Results of IETF-conflict review for draft-williams-exp-tcp-host-id-opt-07

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 30 January 2016 19:10 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 4F5681A8775 for <ietf@ietfa.amsl.com>; Sat, 30 Jan 2016 11:10:35 -0800 (PST)
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, SPF_PASS=-0.001] 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 TNebl76jEkAE for <ietf@ietfa.amsl.com>; Sat, 30 Jan 2016 11:10:33 -0800 (PST)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::234]) (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 CF0791A8773 for <ietf@ietf.org>; Sat, 30 Jan 2016 11:10:33 -0800 (PST)
Received: by mail-pf0-x234.google.com with SMTP id x125so60531821pfb.0 for <ietf@ietf.org>; Sat, 30 Jan 2016 11:10:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=kWviEjeeJA01KZ/UStJl6wlIkeiXAyk1MEm5xWuKkAw=; b=J98lnPESUVAyJHEE4lKuuvXDFsFRE8sOHg/Vwf2iRYNkRal6vyiLT067Wk1xAz1qA7 +4+1PoYOU1yV5l8ICB2zbU9nEfL+r7+qDwWRhh3PpU5BaPvXlbaMWbeL3jJ9+HQv+0jM KLAKwAtzOCcCYvyefgJpADF9iLrd/mdHlGCe422gNm/gtnllWq0nnBESHqAkBYfsscF/ l5Csz8YNnUGMsIzn7IBF3ruRw4ajH6Xl8IXF2Tl8q/0PObz/1D9F/V4sMUC8i4nrWCvq Tt7WETPNzvCIjGkyogatnVgMjCVKM4nS34h2vb7TrMa51rFjLBKpRxk+HtlGif81W+ym KQdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=kWviEjeeJA01KZ/UStJl6wlIkeiXAyk1MEm5xWuKkAw=; b=ght2+pnGL7QcgIbYe39hwZTu5haqRV7r6IgCPnhh2BpSb8Ji87MPpf5qSRr0fpKpAv KBdcXd6WlYeVUGJaFQtGLah336xEcNUyygGU0HgMyGqzt6nqnmAB8rdvSG5XghbT30le WPJQUDtPeNiDTTLodkB08MpKuMTnc6Jg5mzsBteHdw2Aktr9ebdOYmbyt+9vS2luh4fT cIHkEfjKijS72TJ6BUGq8NrC0DZotpjsKH0YoEf5ctcGrt8ZjG2VNph2ZIB7e2Px3UWH ZZWkue88u51otIsxIKOdzmppuqzpe8kaFnvjqRRuB2+6PobrYCYeDNX7Em/Spqu7/hEC T7xw==
X-Gm-Message-State: AG10YOTzrlyHR6jiI1Y4DQur4q4F5E5zteoS8bX90e6qfgu/jrmOlORPgEkuqL+BkQTB0w==
X-Received: by 10.98.64.132 with SMTP id f4mr19462112pfd.159.1454181033493; Sat, 30 Jan 2016 11:10:33 -0800 (PST)
Received: from ?IPv6:2406:e007:40ed:1:28cc:dc4c:9703:6781? ([2406:e007:40ed:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id q20sm6289546pfa.70.2016.01.30.11.10.29 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 30 Jan 2016 11:10:31 -0800 (PST)
Subject: Re: Results of IETF-conflict review for draft-williams-exp-tcp-host-id-opt-07
To: Eliot Lear <lear@cisco.com>, Ted Hardie <ted.ietf@gmail.com>, Harald Alvestrand <harald@alvestrand.no>
References: <20160125231333.27786.50459.idtracker@ietfa.amsl.com> <56A897AE.9060900@alvestrand.no> <CA+9kkMC+43PFvd_ZdR4EXV6zW2+FH67dpXeghWU8NtvbB8RzOg@mail.gmail.com> <56AC7416.2000206@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56AD0AB5.60206@gmail.com>
Date: Sun, 31 Jan 2016 08:10:45 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56AC7416.2000206@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/sN8P68vCi1vzhm-jjwnWB8JYYCs>
Cc: IETF <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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 30 Jan 2016 19:10:35 -0000

Ted,

On 30/01/2016 21:28, Eliot Lear wrote:
...
> On 1/27/16 4:50 PM, Ted Hardie wrote:
...
>> ​Yes, and we have historically said that publishing things in
>> the ISE stream when they counter IETF specifications can
>> only be done when the IESG deems there to be no conflict
>> with IETF specifications.

Not so. What the community has said (in RFC 4846) is that such a conflict
is a legitimate ground for the IESG to object to publication, with the IETF
procedures around this documented in BCP 92. It is then the ISE's prerogative
to decide whether to publish or not, after reviewing the IESG's objection
and any other relevant input.

That includes, but is not limited to, input from the Editorial Board, of which
I am a member.

   Brian

v2.23.0 | Report a Bug | By Email