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

"Y. Richard Yang" <yry@cs.yale.edu> Mon, 11 June 2018 22:50 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 004E612F1A5 for <alto@ietfa.amsl.com>; Mon, 11 Jun 2018 15:50:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.421
X-Spam-Level:
X-Spam-Status: No, score=-1.421 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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] 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 q0TNXI5GfTu1 for <alto@ietfa.amsl.com>; Mon, 11 Jun 2018 15:50:52 -0700 (PDT)
Received: from mail-lf0-f54.google.com (mail-lf0-f54.google.com [209.85.215.54]) (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 258791274D0 for <alto@ietf.org>; Mon, 11 Jun 2018 15:50:52 -0700 (PDT)
Received: by mail-lf0-f54.google.com with SMTP id o9-v6so33045232lfk.1 for <alto@ietf.org>; Mon, 11 Jun 2018 15:50:52 -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=pU7ACr1TpWd8wqiKWyX7P3bTc69ZKym7ZadkL9LZUGU=; b=tVp9EPeaWxPrjDsoxDBL/qEfm4M9sAhaSFP+O62DK4Q4pdWqv7/VFjpu7hBfBwG10w 1a+qnvc/oGCFO+nLiyK0p1xE6OwBmeNELUqLC3und7biTNFsU0O9SABR06TTH5mcrANp YkKqHLNWBUI/8hU9BA9Uhu8g3jAutMrAfYlCD7thdLGkNpnWF2leXSL/jiEXKnGhWSAF tPE/8x3snfCr/pr6TaWLgicklnzk2QNEmNoBeYBjxjaq0HLzTmq0VQ76PeZKCWKLgC1g Z4emAdFsf3q6my7Ix4DGysDHX58eM6RYF1dm/6kWlq1OvGzkoSwd8ilxZuyAx0ap2qCy REtQ==
X-Gm-Message-State: APt69E0K5zLA/7StolbrbCoY6djT2Fa1zAIEHFc44JNdGG4+KnzDJ9qa asGjkxBM0Hd8vrxUC2T5Y1NSqNwlzsj+pYrU3nU=
X-Google-Smtp-Source: ADUXVKL/M2y6sALoljY1BCNaQuQOJ/9n4H5RoaFdKTJYAgd/o6O0an7rexR/gjqo8lnhu3glWgDlUWmZFnFOec+TPsE=
X-Received: by 2002:a2e:cf:: with SMTP id e76-v6mr662244lji.82.1528757450349; Mon, 11 Jun 2018 15:50:50 -0700 (PDT)
MIME-Version: 1.0
References: <eff0f53c-aac0-f74d-e4cb-0e741cfe0a0b@nokia.com> <CANUuoLqqPtU5CWKC4GmOsrsUxaL+DpsS5A9FH=qOkO_z_j50PA@mail.gmail.com> <BLUPR02MB12020D622905ED35146439E6B5780@BLUPR02MB1202.namprd02.prod.outlook.com> <083fe4a0-cb0a-090b-b1cd-ded0bb968d23@nokia.com>
In-Reply-To: <083fe4a0-cb0a-090b-b1cd-ded0bb968d23@nokia.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
Date: Mon, 11 Jun 2018 18:50:39 -0400
Message-ID: <CANUuoLohgNJTsEuurgXX=+bJP0Ee75RNYHRy4UBCSZ2sW6YsxA@mail.gmail.com>
To: "Gurbani, Vijay (Nokia - US)" <vijay.gurbani@nokia.com>
Cc: Chan Dawn <dawn_chen_f@hotmail.com>, IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c6a0b4056e659433"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/1g9rfqc5_G3Yh7-7VNSfD6LBkC4>
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: Mon, 11 Jun 2018 22:50:56 -0000

Hi Vijay, all


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

> Dawn: Yes, pipelining is another good reason to send the response in
> the update stream control service.
>
> This, and the other reasons I indicate in a different thread [1]
> makes me prefer option 2.
>
>
+1

Richard


> [1] https://www.ietf.org/mail-archive/web/alto/current/msg03687.html
>
> Cheers,
>
> On 06/11/2018 03:47 AM, Dawn Chan wrote:
> > Hi Vijay,
> >
> > Thanks for the reply, it is a good point that the result should also be
> sent in the update stream service.
> >
> > Besides, there is another point that the result should also be sent in
> the update stream service. If the server process requests asynchronously,
> when it receives the request from the client and insert it in its queue, it
> will first send a response back to the client; and after the server
> successfully processed the request, it will send a reply via the update
> stream service. This case requires the server to indicate the state of the
> “remove” operation in the reply. A simple attribute “state” with type JSON
> boolean in the UpdateStream ControlEvent can solve the concern. If "state"
> is false, the operation fails; if "state" is true, the operation succeeds.
> >
> > object {
> >         [String control-uri;]
> >         [Boolean state;]
> >         [String remove<1..*>;]
> > } UpdateStreamControlEvent;
> >
> > This is my idea for option 2.
> >
> > Wish to hear opinions from others in the group.
> >
> > Best Wishes,
> > Dawn
> >
> > ________________________________________
> > From: alto <alto-bounces@ietf.org> on behalf of Y. Richard Yang <
> yry@cs.yale.edu>
> > Sent: Sunday, June 10, 2018 3:57:14 AM
> > To: Gurbani, Vijay (Nokia - US)
> > Cc: IETF ALTO
> > Subject: Re: [alto] Need to move SSE to WGLC, but ...
> >
> > 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<mailto: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<mailtolto:
> vijay.gurbani@nokia.com>
> > Network Data Science, Nokia Networks
> > Calendar: http://goo.gl/x3Ogq
> >
> > _______________________________________________
> > alto mailing list
> > alto@ietf.org<mailto:alto@ietf.org>
> > https://www.ietf.org/mailman/listinfo/alto
> >
> >
> > --
> > --
> >  =====================================
> > | Y. Richard Yang <yry@cs.yale.edu<mailto:yry@cs.yale.edu>>   |
> > | Professor of Computer Science       |
> > | http://www.cs.yale.edu/~yry/        |
> >  =====================================
> >
>
> - vijay
> --
> Vijay K. Gurbani / vijay.gurbani@nokia.com
> Network Data Science, Nokia Networks
> Calendar: http://goo.gl/x3Ogq
>


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