IETF Logo Mail Archive

Re: [middisc] closure of the middisc list

"Knutsen, Andrew" <andrew.knutsen@bluecoat.com> Sat, 23 February 2013 22:50 UTC

Return-Path: <andrew.knutsen@bluecoat.com>
X-Original-To: middisc@ietfa.amsl.com
Delivered-To: middisc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E29021F8E3A for <middisc@ietfa.amsl.com>; Sat, 23 Feb 2013 14:50:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.266
X-Spam-Level:
X-Spam-Status: No, score=-3.266 tagged_above=-999 required=5 tests=[AWL=-0.666, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5j46FhykMOBd for <middisc@ietfa.amsl.com>; Sat, 23 Feb 2013 14:50:47 -0800 (PST)
Received: from plsvl-mailgw-01.bluecoat.com (plsvl-mailgw-01.bluecoat.com [199.91.133.11]) by ietfa.amsl.com (Postfix) with ESMTP id 485F121F8E1E for <middisc@ietf.org>; Sat, 23 Feb 2013 14:50:46 -0800 (PST)
Received: from pwsvl-exchts-03.internal.cacheflow.com (pwsvl-exchts-03.bluecoat.com [10.2.2.160]) by plsvl-mailgw-01.bluecoat.com (Postfix) with ESMTP id 0397D81A0A3; Sat, 23 Feb 2013 14:58:42 -0900 (AKST)
Received: from PWSVL-EXCMBX-04.internal.cacheflow.com ([fe80::c596:c77:dd67:b72d]) by pwsvl-exchts-03.internal.cacheflow.com ([fe80::a508:17dc:1550:e9f6%12]) with mapi id 14.01.0355.002; Sat, 23 Feb 2013 14:50:45 -0800
From: "Knutsen, Andrew" <andrew.knutsen@bluecoat.com>
To: "Mani Ramasamy (mani)" <mani@cisco.com>, Wesley Eddy <wes@mti-systems.com>, "Mahdavi, Jamshid" <jamshid.mahdavi@bluecoat.com>
Thread-Topic: [middisc] closure of the middisc list
Thread-Index: AQHN7gZoJkNJRcyZVkqKlI8ATneWQ5hAuhcAgAAOl4CAANHugIATAP2AgBBJNICAAAT8gIAABZwAgABMBACAAM/egIAiSHKs
Date: Sat, 23 Feb 2013 22:50:44 +0000
Message-ID: <974FE049BD0F2E4188567FAD99DEF0331E801629@pwsvl-excmbx-04.internal.cacheflow.com>
References: <50ECC3EF.1020405@mti-systems.com> <CAFZUbhfVGwZQLA+cn_MKoM1GLHBddxGTnOfwtksPWs4+P2p0hg@mail.gmail.com> <CD6E74FCC0FE024BB73C6B483F6706FE0FC0FCD3@xmb-rcd-x07.cisco.com>, <D4D47BCFFE5A004F95D707546AC0D7E91F5D2AA9@SACEXCMBX06-PRD.hq.netapp.com> <D22144CF-6E2B-40F0-9DF1-8EF551B93D17@cisco.com> <510B1D7B.1080704@mti-systems.com> <DF29671EFBFC454E984F5A1AD4834F491E79F54E@pwsvl-excmbx-04.internal.cacheflow.com> <510B265E.6060003@mti-systems.com>, <CD6E74FCC0FE024BB73C6B483F6706FE0FC60D2F@xmb-rcd-x07.cisco.com>, <CD6E74FCC0FE024BB73C6B483F6706FE0FC62DB3@xmb-rcd-x07.cisco.com>
In-Reply-To: <CD6E74FCC0FE024BB73C6B483F6706FE0FC62DB3@xmb-rcd-x07.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [199.91.133.85]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "middisc@ietf.org" <middisc@ietf.org>
Subject: Re: [middisc] closure of the middisc list
X-BeenThere: middisc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussions on TCP option for middlebox discovery." <middisc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/middisc>, <mailto:middisc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/middisc>
List-Post: <mailto:middisc@ietf.org>
List-Help: <mailto:middisc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/middisc>, <mailto:middisc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Feb 2013 22:50:48 -0000

   What is the next step for this?  I think we've reached consensus...  Do we have an option to publish as more than a draft?

Andrew

________________________________________
From: middisc-bounces@ietf.org [middisc-bounces@ietf.org] on behalf of Mani Ramasamy (mani) [mani@cisco.com]
Sent: Friday, February 01, 2013 11:16 AM
To: Wesley Eddy; Mahdavi, Jamshid
Cc: middisc@ietf.org
Subject: Re: [middisc] closure of the middisc list

New version has been posted with the suggested updates.


http://www.ietf.org/internet-drafts/draft-ananth-middisc-tcpopt-02.txt

Wes,
    Please let us know if anything else is needed to take this forward.

Thanks.

________________________________________
From: middisc-bounces@ietf.org [middisc-bounces@ietf.org] on behalf of Mani Ramasamy (mani)
Sent: Thursday, January 31, 2013 10:52 PM
To: Wesley Eddy; Mahdavi, Jamshid
Cc: middisc@ietf.org
Subject: Re: [middisc] closure of the middisc list

Great. Thanks Wes and Jamshid!

Will update and post a new draft tomorrow.

Mani.



-----Original Message-----
From: Wesley Eddy [mailto:wes@mti-systems.com]
Sent: Thursday, January 31, 2013 6:20 PM
To: Mahdavi, Jamshid
Cc: Mani Ramasamy (mani); middisc@ietf.org
Subject: Re: [middisc] closure of the middisc list

On 1/31/2013 9:00 PM, Mahdavi, Jamshid wrote:
> I had made some minor comments on the wording (MUST, SHOULD) which I believe we wanted advice from the AD on so Mani knew whether to accept it.
>
> I also had suggested one very minor change to the content which I hope Mani is ok with accepting.
>
> Let me know if you need that email resent.
>
> Otherwise, very happy!
>


Regarding the 2119 wording, I (personally) prefer your rewording of it, since those "requirements" are kind of just the design principles that were aimed for and (as you note) not protocol conformance requirements.  However, there are many RFCs that do use 2119 capitalized words for requirements statements, and there are mixed opinions about it, even in the IESG ... so, it would be passable either way.  That said, I suspect it will be smoother sailing if your suggested rewordings are applied :).

--
Wes Eddy
MTI Systems
_______________________________________________
middisc mailing list
middisc@ietf.org
https://www.ietf.org/mailman/listinfo/middisc
_______________________________________________
middisc mailing list
middisc@ietf.org
https://www.ietf.org/mailman/listinfo/middisc

v2.23.0 | Report a Bug | By Email