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

S Moonesamy <sm+ietf@elandsys.com> Fri, 29 January 2016 23:41 UTC

Return-Path: <sm@elandsys.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 F13861ACED1 for <ietf@ietfa.amsl.com>; Fri, 29 Jan 2016 15:41:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level:
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.001, T_DKIM_INVALID=0.01] autolearn=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 M7lI6OZdFmKE for <ietf@ietfa.amsl.com>; Fri, 29 Jan 2016 15:41:08 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 299C71ACED0 for <ietf@ietf.org>; Fri, 29 Jan 2016 15:41:08 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.227.87.201]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id u0TNembZ005794 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Jan 2016 15:41:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1454110863; x=1454197263; bh=+R+5sZAZSUzi9dHQsCY7ay2T6tBkIxewBkRUgFFjg04=; h=Date:To:From:Subject:In-Reply-To:References; b=U2zntVBpizHV0kkQ9aIeaelpJkKgnyYwd6JGvb6K/zoZ78nMrMlLJbjzihptibzO2 D4pgcrfM0xV/bB75ellfo7us1WwhpO1RhoIMbk4mtxx2n7El4W7EKIx9dLlKJOGvW/ MXqd+t/KjULMzNqnvI1DdSirgmclQuE2Hqq77zfU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1454110863; x=1454197263; i=@elandsys.com; bh=+R+5sZAZSUzi9dHQsCY7ay2T6tBkIxewBkRUgFFjg04=; h=Date:To:From:Subject:In-Reply-To:References; b=hx593Gqzc5I8uEcmK8vwVjd8rzTZ5d59+XAQqImA9EmD+nNMYRLmxT+eixTBhMN1s RYMjNA2KeBkinlxoJ3PfHO2BbmcygcazFHevEOj3XIbC0jIt1Bq5GJwl89SMCMb14+ W0wOYEO9WvyHJkFWthlugKFo9mK3RYJ0nAnQHfyo=
Message-Id: <6.2.5.6.2.20160129143347.0dd33700@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 29 Jan 2016 15:22:51 -0800
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Results of IETF-conflict review for draft-williams-exp-tcp-host-id-opt-07
In-Reply-To: <56A93AEA.2080304@cs.tcd.ie>
References: <20160125231333.27786.50459.idtracker@ietfa.amsl.com> <56A897AE.9060900@alvestrand.no> <C2338AA69B074ACA5E89DFD4@JcK-HP8200.jck.com> <56A91DFC.70105@gmail.com> <56A93AEA.2080304@cs.tcd.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/npz4cw5rCxbPay-mtJQ7vg3NGsw>
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: Fri, 29 Jan 2016 23:41:09 -0000

Hi Stephen,
At 13:47 27-01-2016, Stephen Farrell wrote:
>Actually, if people do find that sufficiently enlightening
>or find it generates more questions, it'd be good to let
>the IESG know eithr way, in case we miss stuff in crafting
>a response (or to save us confusing matters more by trying
>to clarify by adding words:-).
>
>When I scanned the history, I think it did more or less
>cover what I recall of the discussions (though that's easier
>for me of course since I was part of 'em). The only missing
>bit of info is that the IESG and ISE have arranged to have a
>chat about all of our expectations for "returning items and
>5742 review." We've had a couple of those recently, (one
>that was easy-peasy and then this one:-), and people were a
>bit confused about the right way to handle stuff. That chat
>is planned to happen @ IETF95.

I am on the Independent Submissions Editorial Board.  The following 
is my opinion.

There are two points in the Conflict Review:

   (a) draft-williams-exp-tcp-host-id-opt-07 violates IETF procedures about
      pervasive monitoring (RFC 7258)

   (b) This work is related to IETF work done in the INTAREA WG.

BCP 188 does not apply to the Independent Stream as it would apply to 
a document in the IETF Stream.  The Conflict Review note is skimpy on 
the details.  As I don't know the right way to handle this stuff I 
thought that it would be better to have a conversation with you.  I 
would consider what is in RFC 4846 if I review the draft.  There is, 
for example: "

    'the [IESG] evaluation should focus exclusively on conflicts or
     confusion with IETF process and attempts to subvert ("end run")
     working group activities.'

Is it appropriate to DNP an Independent Stream draft because the IESG 
or the IETF does not agree to publication of the technical 
specification?  That would raise questions about the meaning of the 
word "Independent".

Regards,
S. Moonesamy