RE: Results of IETF-conflict review for draft-williams-exp-tcp-host-id-opt-07
"Dr. Sandeep Joshi [MU - Jaipur]" <sandeep.joshi@jaipur.manipal.edu> Sat, 30 January 2016 08:31 UTC
Return-Path: <sandeep.joshi@jaipur.manipal.edu>
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 6D73F1A89EB for <ietf@ietfa.amsl.com>; Sat, 30 Jan 2016 00:31:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.228
X-Spam-Level:
X-Spam-Status: No, score=0.228 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RELAY_IS_220=2.118, SPF_PASS=-0.001, T_HK_NAME_DR=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 CR-TJugFWhHF for <ietf@ietfa.amsl.com>; Sat, 30 Jan 2016 00:31:04 -0800 (PST)
Received: from mailgate1.manipalgroup.com (mail2.manipalgroup.com [220.226.189.72]) by ietfa.amsl.com (Postfix) with ESMTP id 40AE01A1A43 for <ietf@ietf.org>; Sat, 30 Jan 2016 00:31:03 -0800 (PST)
X-WSS-ID: 0O1RBNI-05-THS-02
X-M-MSG:
X-TMWD-Spam-Summary: TS=20160130083054; ID=1; SEV=2.4.5; DFV=B2016013012; IFV=NA; AIF=B2016013012; RPD=NA; ENG=NA; RPDID=NA; CAT=NONE; CON=NONE; SIG=AAAAAAAAAAAAAAAA4FpcDQAAfQ==
Received: from webmail.manipalglobal.com (ridc-exhc02.mul.manipal.net [172.16.128.36]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailgate1.manipalgroup.com (Axway MailGate 5.3.0) with ESMTPS id 2E246DE2A0A; Sat, 30 Jan 2016 14:00:53 +0530 (IST)
Received: from RIDC-EXMB01.mul.manipal.net ([fe80::a4c8:348f:9a34:8a3b]) by RIDC-EXHC02.mul.manipal.net ([::1]) with mapi id 14.03.0248.002; Sat, 30 Jan 2016 14:00:38 +0530
From: "Dr. Sandeep Joshi [MU - Jaipur]" <sandeep.joshi@jaipur.manipal.edu>
To: Eliot Lear <lear@cisco.com>, Ted Hardie <ted.ietf@gmail.com>, Harald Alvestrand <harald@alvestrand.no>
Subject: RE: Results of IETF-conflict review for draft-williams-exp-tcp-host-id-opt-07
Thread-Topic: Results of IETF-conflict review for draft-williams-exp-tcp-host-id-opt-07
Thread-Index: AQHRWOsFn0EDhaST102+Ttjzz6jiZJ8PJssAgAQ7dACAAFz3gA==
Date: Sat, 30 Jan 2016 08:30:37 +0000
Message-ID: <7FFA4D794BA8C04A95D1CD64F828DC13011A4BD3B1@RIDC-EXMB01.mul.manipal.net>
References: <20160125231333.27786.50459.idtracker@ietfa.amsl.com> <56A897AE.9060900@alvestrand.no> <CA+9kkMC+43PFvd_ZdR4EXV6zW2+FH67dpXeghWU8NtvbB8RzOg@mail.gmail.com> <56AC7416.2000206@cisco.com>
In-Reply-To: <56AC7416.2000206@cisco.com>
Accept-Language: en-US, en-IN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.16.128.196]
Content-Type: multipart/alternative; boundary="_000_7FFA4D794BA8C04A95D1CD64F828DC13011A4BD3B1RIDCEXMB01mul_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/XLVHNEdbx6nHX7jRTwnh6vwt2K4>
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 08:31:05 -0000
Hi, Anyone can let me know our IETF group name. Sandeep Joshi From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Eliot Lear Sent: 30 January 2016 13:58 To: Ted Hardie; Harald Alvestrand Cc: IETF Subject: Re: Results of IETF-conflict review for draft-williams-exp-tcp-host-id-opt-07 Hi, On 1/27/16 4:50 PM, Ted Hardie wrote: Recent proposals discussed in the IETF have identified benefits to more distinctly identifying the hosts that are hidden behind a shared address/prefix sharing device or application-layer proxy. Analysis indicates that the use of a TCP option for this purpose can be successfully applied to some use cases. The proposals have identified benefits according to the authors, but the IETF declined to adopt them because there were far bigger downsides. This abstract gives the opposite impression, which is not exactly kosher. I agree with Ted about the abstract; that at the very least it should be reworded. Referring to the IETF needs to be fairly done in the independent series. We already have enough problems with people distinguishing IETF from independent work. However... Armchair lawyers will also note that the procedure refers to "IETF specifications". An independent-submission RFC is *not* an IETF specification. 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. This clearly does conflict with the thrust of efforts in the IETF (e.g. tcpinc). RFC 5742 is quite explicit. BCP88 itself is not a specification but a Best Current Practice, and limits its applicability to IETF, and not independent, specifications. As to whether this conflicts with "the thrust of efforts in" tcpinc, that is not what the IESG wrote. If it had written it, the justification would have to again be based on what is stated in RFC 5742, specifically in Section 3. There should be at least sufficient information to indicate what the nature of the conflict is. Having a different opinion than that of the IETF or a working group is not a justification for non-publication, but rather a justification for the existence of the ISE. In short, I believe the IESG erred procedurally, and would suggest they revisit their approach. Haralds query about attaching an IESG note seems entirely appropriate. Eliot
- Re: Results of IETF-conflict review for draft-wil… Harald Alvestrand
- Re: Results of IETF-conflict review for draft-wil… John C Klensin
- Re: Results of IETF-conflict review for draft-wil… Fernando Gont
- Re: Results of IETF-conflict review for draft-wil… Jari Arkko
- Re: Results of IETF-conflict review for draft-wil… Ted Hardie
- Re: Results of IETF-conflict review for draft-wil… Brian E Carpenter
- Re: Results of IETF-conflict review for draft-wil… Stephen Farrell
- Re: Results of IETF-conflict review for draft-wil… S Moonesamy
- Re: Results of IETF-conflict review for draft-wil… Eliot Lear
- RE: Results of IETF-conflict review for draft-wil… Dr. Sandeep Joshi [MU - Jaipur]
- Re: Results of IETF-conflict review for draft-wil… Brian E Carpenter
- Re: Results of IETF-conflict review for draft-wil… John C Klensin
- Re: Results of IETF-conflict review for draft-wil… Ted Hardie
- Re: Results of IETF-conflict review for draft-wil… Brian E Carpenter
- Re: Results of IETF-conflict review for draft-wil… Martin Stiemerling
- Re: Results of IETF-conflict review for draft-wil… Paul Hoffman
- Re: Results of IETF-conflict review for draft-wil… Stephen Farrell