Re: [middisc] middisc specification update

Andrew Knutsen <andrew.knutsen@bluecoat.com> Tue, 17 January 2012 23:11 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 866B121F8507 for <middisc@ietfa.amsl.com>; Tue, 17 Jan 2012 15:11:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vCEzk1qIitbO for <middisc@ietfa.amsl.com>; Tue, 17 Jan 2012 15:11:16 -0800 (PST)
Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by ietfa.amsl.com (Postfix) with ESMTP id 0ED6121F84FE for <middisc@ietf.org>; Tue, 17 Jan 2012 15:11:15 -0800 (PST)
Received: from PWSVL-EXCHTS-01.internal.cacheflow.com ([10.2.2.122]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id q0HNBBGc004024 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 17 Jan 2012 15:11:12 -0800 (PST)
Received: from [10.9.84.250] (10.2.2.106) by exchange.bluecoat.com (10.2.2.122) with Microsoft SMTP Server (TLS) id 14.1.289.1; Tue, 17 Jan 2012 15:11:06 -0800
Message-ID: <4F16000A.3070100@bluecoat.com>
Date: Tue, 17 Jan 2012 15:11:06 -0800
From: Andrew Knutsen <andrew.knutsen@bluecoat.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
References: <4E9241F7.5090406@mti-systems.com> <2AE215BDC76842F885AC7E9D34BD2CA4@davidPC> <0C53DCFB700D144284A584F54711EC580E546254@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <0C53DCFB700D144284A584F54711EC580E546254@xmb-sjc-21c.amer.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Wesley Eddy <wes@mti-systems.com>, Ron Frederick <ron.frederick@bluecoat.com>, middisc@ietf.org
Subject: Re: [middisc] middisc specification update
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: Tue, 17 Jan 2012 23:11:16 -0000

     Sorry to say I've been too busy to rework the draft.  Anantha, if 
you have time that would be fine with me.  I believe we've settled on a 
format, as proposed by Ron; its just the boilerplate/terminology 
sections that need to be re-written.

Andrew

On 1/17/2012 1:29 PM, Anantha Ramaiah (ananth) wrote:
> I hope to get something out (based on the discussions so far) before the
> IETF deadlines. I'll start looking into this very soon.  I assume we are
> talking about the -00- cutoff deadline here and the IETF page says it is
> March 5th.
> -Anantha
>
>> -----Original Message-----
>> From: middisc-bounces@ietf.org [mailto:middisc-bounces@ietf.org] On
>> Behalf Of David Harrington
>> Sent: Tuesday, January 17, 2012 12:16 PM
>> To: 'Wesley Eddy'; middisc@ietf.org
>> Subject: Re: [middisc] middisc specification update
>>
>> three months later and a new deadline is approaching.
>> Any chance of seeing progress on a draft?
>>
>> David Harrington
>> Director, IETF Transport Area
>> ietfdbh@comcast.net (preferred for ietf)
>> dbharrington@huaweisymantec.com
>> +1 603 828 1401 (cell)
>>
>>> -----Original Message-----
>>> From: middisc-bounces@ietf.org
>>> [mailto:middisc-bounces@ietf.org] On Behalf Of Wesley Eddy
>>> Sent: Sunday, October 09, 2011 5:53 PM
>>> To: middisc@ietf.org
>>> Subject: [middisc] middisc specification update
>>>
>>> Hi folks, this is a reminder that there are cut-off dates
>> approaching
>>> for draft submission prior to the next IETF meeting.  If I
>> understand
>>> correctly, Andrew has the pen and should be working on either a new
>> or
>>> updated document based on prior discussions.  If it's at all
>> possible
>>> to get that in before the relevant cut-off date, that would be very
>>> encouraging.
>>>
>>> --
>>> 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
> _______________________________________________
> middisc mailing list
> middisc@ietf.org
> https://www.ietf.org/mailman/listinfo/middisc