Re: [alto] Need to move SSE to WGLC, but ...

"Y. Richard Yang" <yry@cs.yale.edu> Sat, 09 June 2018 19:57 UTC

Return-Path: <yang.r.yang@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 8E040130F74 for <alto@ietfa.amsl.com>; Sat, 9 Jun 2018 12:57:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.48
X-Spam-Level:
X-Spam-Status: No, score=0.48 tagged_above=-999 required=5 tests=[FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 EgpuWQTeFofF for <alto@ietfa.amsl.com>; Sat, 9 Jun 2018 12:57:28 -0700 (PDT)
Received: from mail-lf0-f52.google.com (mail-lf0-f52.google.com [209.85.215.52]) (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 60F25130E99 for <alto@ietf.org>; Sat, 9 Jun 2018 12:57:28 -0700 (PDT)
Received: by mail-lf0-f52.google.com with SMTP id o9-v6so24923008lfk.1 for <alto@ietf.org>; Sat, 09 Jun 2018 12:57:28 -0700 (PDT)
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=il4ldPFY32TGXjgLrMT0NulhJgjLCT1mxA8SPx4f0Po=; b=Lc2OGeAqcHd69jXK4PddnTdBWGpWdrSshzRehp3USCnfPGzUQBL9Xz0zUtOmCg8N5d vaTc/KuYQpZVWRSFAs63ttKMpL0Fan25IVJ+9cWVPcQXrmRWUWKVUrFO9213uMB4VjBc 44/KAP1MIY/jtnYeB5JlucbvGvHnNKsrchXhJInPAQ4IkStUHhvB0vHXqLRewxH09iCT /aOe5MB5xD5MYUAevE9try79zRlfVSiDnTLWcbWdoC5gW7i7oq61ia5a37eDp79PXi3Q PRA4l2IqWzzKaDYjwsouOTztQo3pGiBpo4+POR9Oj4Ld8cjMvfsjZ2e05E1Ft1EbIUU5 Z5cQ==
X-Gm-Message-State: APt69E1d5pZPBBhJhotd0833zMLiDV3ul32k8mieGRLCmJIbZNt73A0z mv3xT35NOiUGvfiZaeDf3NewD5uZ8Zn5vLsAd2k=
X-Google-Smtp-Source: ADUXVKKDKpDGlUa1XiSJyw4Hc8Wcxm1Sfwc489QK9Xl2dDd9f+NRwUrS3Gn8PKOkdfX7ErrhMWDsyvBdCBzdn+lwwto=
X-Received: by 2002:a2e:8605:: with SMTP id a5-v6mr5672765lji.43.1528574246385; Sat, 09 Jun 2018 12:57:26 -0700 (PDT)
MIME-Version: 1.0
References: <eff0f53c-aac0-f74d-e4cb-0e741cfe0a0b@nokia.com>
In-Reply-To: <eff0f53c-aac0-f74d-e4cb-0e741cfe0a0b@nokia.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
Date: Sat, 9 Jun 2018 15:57:14 -0400
Message-ID: <CANUuoLqqPtU5CWKC4GmOsrsUxaL+DpsS5A9FH=qOkO_z_j50PA@mail.gmail.com>
To: "Gurbani, Vijay (Nokia - US)" <vijay.gurbani@nokia.com>
Cc: IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f80127056e3aecc9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/fD_cU8gz6iJvneTfciOu_pnhy0Y>
Subject: Re: [alto] Need to move SSE to WGLC, but ...
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.26
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: Sat, 09 Jun 2018 19:57:31 -0000

Dear Vijay, Jan,

Thank you so much. It is a wonderful idea to check the WG for additional
comments on the mentioned issues. The authors will address suggestions, if
any, and then move the document forward.

Thanks!
Richard

On Fri, Jun 8, 2018 at 11:04 AM Vijay K. Gurbani <vijay.gurbani@nokia.com>
wrote:

> Folks: Jan and I would like to move SSE [1] to WGLC.
>
> Looking at the mailing list, we note that the authors are asking input
> from the WG on an issue in SSE [2].
>
> We would kindly request the WG to spend some time thinking about the
> question being asked in [2] and to chime in with some thoughts.
>
> Assuming that there is no response by next week on this, the authors can
> proceed with their default position on this, for which they have an
> articulated reason in [2].
>
> Jan and I will follow up next week and if there has not been any further
> list discussion on this, we will move the work ahead to WGLC.
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-alto-incr-update-sse/
> [2] https://www.ietf.org/mail-archive/web/alto/current/msg03684.html
>
> Thanks,
>
> - vijay
> --
> Vijay K. Gurbani / vijay.gurbani@nokia.com
> Network Data Science, Nokia Networks
> Calendar: http://goo.gl/x3Ogq
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>


-- 
-- 
 =====================================
| Y. Richard Yang <yry@cs.yale.edu>   |
| Professor of Computer Science       |
| http://www.cs.yale.edu/~yry/        |
 =====================================