Re: [middisc] middisc specification update

"Anantha Ramaiah (ananth)" <ananth@cisco.com> Wed, 18 January 2012 02:03 UTC

Return-Path: <ananth@cisco.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 443B81F0C4B for <middisc@ietfa.amsl.com>; Tue, 17 Jan 2012 18:03:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 HgJqsze7FgSW for <middisc@ietfa.amsl.com>; Tue, 17 Jan 2012 18:03:33 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 8D5681F0C3F for <middisc@ietf.org>; Tue, 17 Jan 2012 18:03:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ananth@cisco.com; l=3330; q=dns/txt; s=iport; t=1326852213; x=1328061813; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=9K4XbYRcI0t1fQmFpIFBBQ6h2lCEdw8INHNGx2u+8LQ=; b=P2sIUcEDZjg4lhNkiDniRLlCnrT0+Bg+4Wn3+6hAdZomMGV89JcdjjjP vdnYgpU7D8ZiOAe4U2A+vya/EH7pG20SK9XemSnLhoAkYl/4s032DvM9F T5Yeg+oNVOrtH97T2uNCNjNFIhg0PxrK+Dx3MoEbhfgpOyRHW6UWJ5/tm I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AroAADooFk+rRDoI/2dsb2JhbABBA50NjzeBBoEFgXIBAQEEAQEBDwEdCjQLDAQCAQgRBAEBAQoGFwEGASYfCQgBAQQTCBqHYJkUAZ5SBIktMwIBAUIEBAEDBwEBAw4FAQIBAQgBAQEDPQwKGjCBaCEFAw0QAgMCAQEDAQEDFgEBAQIJgj5jBIg7nzg
X-IronPort-AV: E=Sophos;i="4.71,526,1320624000"; d="scan'208";a="25723301"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 18 Jan 2012 02:03:31 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q0I23VaU032387; Wed, 18 Jan 2012 02:03:31 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 17 Jan 2012 18:03:31 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 17 Jan 2012 18:03:30 -0800
Message-ID: <0C53DCFB700D144284A584F54711EC580E546389@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <4F16000A.3070100@bluecoat.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [middisc] middisc specification update
Thread-Index: AczVbVFXcDU24JEuR3WSPkOJ1G/a6wAFjCSg
References: <4E9241F7.5090406@mti-systems.com> <2AE215BDC76842F885AC7E9D34BD2CA4@davidPC> <0C53DCFB700D144284A584F54711EC580E546254@xmb-sjc-21c.amer.cisco.com> <4F16000A.3070100@bluecoat.com>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: Andrew Knutsen <andrew.knutsen@bluecoat.com>
X-OriginalArrivalTime: 18 Jan 2012 02:03:31.0275 (UTC) FILETIME=[607811B0:01CCD585]
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: Wed, 18 Jan 2012 02:03:34 -0000

Andrew,

Well, I think the summary was that :-

- we needed to re-write the draft considerably, esp, the motivation and
scope, followed by the method (option format) which was agreed upon,
then add notes on interoperability, remove irrelevant text etc.,

Anyways, let me take a first cut and once ready will post it and then we
can have more reviews etc., (of course all these to be done before the
cut off)

I'll start working on it after sometime in the middle or end of next
week. [ I hope to get more free time after getting over some tight
internal deadlines]

-Anantha

> -----Original Message-----
> From: Andrew Knutsen [mailto:andrew.knutsen@bluecoat.com]
> Sent: Tuesday, January 17, 2012 3:11 PM
> To: Anantha Ramaiah (ananth)
> Cc: David Harrington; Wesley Eddy; middisc@ietf.org; Ron Frederick
> Subject: Re: [middisc] middisc specification update
> 
> 
>      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