IETF Logo Mail Archive

Re: [alto] Chair review of draft-ietf-alto-incr-update-sse-17

Vijay Gurbani <vijay.gurbani@gmail.com> Tue, 07 January 2020 16:33 UTC

Return-Path: <vijay.gurbani@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48B53120847; Tue, 7 Jan 2020 08:33:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 VdDHUIXUTuve; Tue, 7 Jan 2020 08:33:35 -0800 (PST)
Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E16F120823; Tue, 7 Jan 2020 08:33:35 -0800 (PST)
Received: by mail-ed1-x531.google.com with SMTP id v28so64712edw.12; Tue, 07 Jan 2020 08:33:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yMTABgynJRWhEM0F6H74FakUO8vwthixJ/8MHcwgeT8=; b=hRXDAAy1bhYSZJu33JriVOGZ1ILN1DOaGDVgGG664OC9IGdrC+0MCZD2Nq2PSph44r t3pWHAxo4PxnNF2/+5u6zG6zGiRA0w3USPpBuZ4U1UWdjDaRhEt7lIioUYODR7Xv7wsO beCIfDYsQdpkXJvQ3wanr1Ap0xlwmmkpD6LGKHNfSwqXUofRI8W3pn/j0lGuo4UIHL49 c1hyQ8IHGkRborU7Bm8nnxizq19HcezOQaSk/B/dr6BcLR6wdkKAe1PGOWljjGRaJHyr fWSHlYlbt0us6Tga+BMHY2/JY3l3eqWOUShaBGU8Fno88wQaa4Ad3PU4j8Jfzs14ysg1 r/og==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=yMTABgynJRWhEM0F6H74FakUO8vwthixJ/8MHcwgeT8=; b=pOASUXCJJb2Sw7GKQR0j0V0uV6dbHFZnd8QwUxAdarrq8x4/YM7oEJ00gb8u16ZDRm 3Q5OYSY5IhREuIotiuGWQFjV4IZLihwxQtO+dgnDXU80QnrbOqw7WNm3EgsDsNXxUkeg U4qRXgQliQlZ5hdvQdBGtxRFht9rgRLT0owp/adjgxEfd49upioW2jViD4AA6xCZL62D vlJXL4akmLGDemnqblEc2nlWGXUHBr/y0unnLHXBEm79nHu1c0Mp5lSQAdPBF8ewGWRw z80qDofBOEVmsKawSXgI7+zQBy71NQfompcn0IrS8DWq7L0qAYP56Lc4DxGNG4dfbGxj pkQQ==
X-Gm-Message-State: APjAAAVd1SoZGWfazIBuVm9Q3Rg/oBGpV9C6Eg7eXro/nUxbBuKJ3lbZ MCJs8xW20oy/FhFIkvSZ0ldJXdKaUCW87uIgofQ=
X-Google-Smtp-Source: APXvYqwKyULZbt5Du5OjKrkCOTIBJRsBrR31jJ8b1BulWsJxg1sDbiFoiZWS03vyQ+xyzTdlYBDQ1zKwTueB8vvIzCs=
X-Received: by 2002:a17:906:1c89:: with SMTP id g9mr281570ejh.114.1578414813919; Tue, 07 Jan 2020 08:33:33 -0800 (PST)
MIME-Version: 1.0
References: <CAMMTW_KOHEfE7AojeviUdUVqmDLmJQ97+hUeoMKj1A0wwAzY6w@mail.gmail.com> <CAEDarXKPD7x35GRFiYgMy2jnq5NsfYumDR4K5DbQz_AhJHKeig@mail.gmail.com> <2a1f25f3-65ca-4343-a0a5-0d387840ff19@inet.tu-berlin.de> <CAMMTW_JhJw65fczkEVBaQ3fRfn+JzNbZQWjcfP1eavOWHgRn3w@mail.gmail.com> <1704dd78-aa52-7235-1d25-25648ab776ab@benocs.com>
In-Reply-To: <1704dd78-aa52-7235-1d25-25648ab776ab@benocs.com>
From: Vijay Gurbani <vijay.gurbani@gmail.com>
Date: Tue, 07 Jan 2020 10:35:06 -0600
Message-ID: <CAMMTW_KKrLAMS=GyLyQygUnOw=sRDe+rig99OFmTd5knAFL9MQ@mail.gmail.com>
To: Hans Seidel <hseidel@benocs.com>
Cc: Ingmar Poese <ingmar@inet.tu-berlin.de>, draft-ietf-alto-incr-update-sse@ietf.org, IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004abd13059b8f56d5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/FLXAesXBlVCOy80-zmFBuh0mhyo>
Subject: Re: [alto] Chair review of draft-ietf-alto-incr-update-sse-17
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2020 16:33:38 -0000

Dear Hans: Thank you for your email.  At this point, I am interested in
getting as much information about the implementation of the Internet-Draft
as possible in preparation for moving the work ahead in the WG.  Certainly,
I will be happy to allocate you some agenda time in Vancouver to document
any lessons learned on implementing alto-sse.  If you are interested,
please let me know.

If anyone else on the list has any implementation of alto-sse, please let
me know as well.

Thanks,
- vijay

On Tue, Jan 7, 2020 at 10:26 AM Hans Seidel <hseidel@benocs.com> wrote:

> Hi Vijay,
>
> let me answer this question for Ingmar. Currently implemented is the JSON
> merge patch feature. JSON patch is on our roadmap. We aim for a release
> that is fully compatible with the latest draft prior to the Vancouver IETF
> which I also plan to attend. Once the RFC is published, we are going to use
> SSE in production with our partners.
>
> If you or somebody on the list has an ALTO implementation and is
> interested in running tests, feel free to contact us.
>
> If you like to know more, feel free to ask. We also happily give further
> insights in our SSE implementation, or our ALTO implementation in general
> in Vancouver. If you or the list is interested in specific parts, please
> let us know and we prepare some slides for Vancouver.
>

v2.23.0 | Report a Bug | By Email