Re: [alto] SSE final touches

"Vijay K. Gurbani" <vijay.gurbani@nokia.com> Mon, 19 March 2018 03:38 UTC

To: "Y. Richard Yang" <yry@cs.yale.edu>, Jan Seedorf <ietf@j-f-s.de>
Cc: IETF ALTO <alto@ietf.org>
References: <CANUuoLqaWxkXddVJ5jmvEP4a2OC3mN43L8YmPGnmeDKAyW1=sA@mail.gmail.com> <1fd9305f-ae9b-914d-ad25-2d112f92e9f4@j-f-s.de> <CANUuoLryigrC7QSZbB1Sf7iaciCOH=FvjfkxHPtJ4zFRSsq82Q@mail.gmail.com>
From: "Vijay K. Gurbani" <vijay.gurbani@nokia.com>
Organization: Network Data Science, Applications and Analytics
Message-ID: <afd6f5e7-047b-a92a-3949-71ccafa20385@nokia.com>
Date: Sun, 18 Mar 2018 22:38:02 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CANUuoLryigrC7QSZbB1Sf7iaciCOH=FvjfkxHPtJ4zFRSsq82Q@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Received-SPF: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 19 Mar 2018 03:38:13.1349 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 63cbccda-3d5d-499c-268f-08d58d4ad86a
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6PR0702MB3624
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/t-bkvAM1sYfoc1KowB_VFs7ll18>
Subject: Re: [alto] SSE final touches
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.22
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, 19 Mar 2018 03:38:20 -0000

I think that is a wise decision.  One can continue adding bits and
pieces to the protocol ad infinitum.  Best to get what we have out
and let the implementations and needs then guide us towards whether
multipart update will serve a substantive community.  If it does,
I suspect that willing hands will rise to scratch that particular
itch.

>From my understanding, nothing is preventing the update of multiple
objects, just that with the current constructs, they have to be done
serially instead of in parallel.

Cheers,

On 03/18/2018 12:16 PM, Y. Richard Yang wrote:
> Jan,
> 
> The authors had a very extensive discussion again. We have decided to
> support only single-object ALTO resources, and leave multipart, which
> can be a nice feature to support composition without the need of
> accumulating all objects into a single object, as future work. We edited
> a few sentences to make clear.
> 
> Thanks a lot for the guidance!

- vijay
--
Vijay K. Gurbani / vijay.gurbani@nokia.com
Network Data Science, Nokia Networks
Calendar: http://goo.gl/x3Ogq

[alto] SSE final touches Y. Richard Yang
Re: [alto] SSE final touches Jan Seedorf
Re: [alto] SSE final touches Y. Richard Yang
Re: [alto] SSE final touches Vijay K. Gurbani
Re: [alto] SSE final touches Jan Seedorf
Re: [alto] SSE final touches Y. Richard Yang