[Stackevo-discuss] draft-trammel-spud-req-01

<xavier.marjou@orange.com> Fri, 15 January 2016 14:16 UTC

Return-Path: <xavier.marjou@orange.com>
X-Original-To: stackevo-discuss@ietfa.amsl.com
Delivered-To: stackevo-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29F381B2D67 for <stackevo-discuss@ietfa.amsl.com>; Fri, 15 Jan 2016 06:16:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 7207kaiy8asK for <stackevo-discuss@ietfa.amsl.com>; Fri, 15 Jan 2016 06:16:33 -0800 (PST)
Received: from relais-inet.orange.com (relais-nor36.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BDD51ACE4B for <stackevo-discuss@iab.org>; Fri, 15 Jan 2016 06:16:32 -0800 (PST)
Received: from opfednr05.francetelecom.fr (unknown [xx.xx.xx.69]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id B1C9F180154 for <stackevo-discuss@iab.org>; Fri, 15 Jan 2016 15:16:30 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.2]) by opfednr05.francetelecom.fr (ESMTP service) with ESMTP id 8DDF320067 for <stackevo-discuss@iab.org>; Fri, 15 Jan 2016 15:16:30 +0100 (CET)
Received: from OPEXCLILM44.corporate.adroot.infra.ftgroup ([fe80::b08d:5b75:e92c:a45f]) by OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06%19]) with mapi id 14.03.0279.002; Fri, 15 Jan 2016 15:16:30 +0100
From: <xavier.marjou@orange.com>
To: "stackevo-discuss@iab.org" <stackevo-discuss@iab.org>
Thread-Topic: draft-trammel-spud-req-01
Thread-Index: AdFPnp1EE9bjVa86TL2DgpjPqB1WDA==
Date: Fri, 15 Jan 2016 14:16:29 +0000
Message-ID: <17293_1452867390_5698FF3E_17293_3174_1_7F0E3EB647223A4ABED5FF4DCFC05C8514C1629D@OPEXCLILM44.corporate.adroot.infra.ftgroup>
Accept-Language: en-GB, fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.1]
Content-Type: multipart/alternative; boundary="_000_7F0E3EB647223A4ABED5FF4DCFC05C8514C1629DOPEXCLILM44corp_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/stackevo-discuss/6aMIcldQVI7qDU-QzZV5hZg1-4M>
Subject: [Stackevo-discuss] draft-trammel-spud-req-01
X-BeenThere: stackevo-discuss@iab.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IP Stack Evolution Discussion List <stackevo-discuss.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/stackevo-discuss>, <mailto:stackevo-discuss-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stackevo-discuss/>
List-Post: <mailto:stackevo-discuss@iab.org>
List-Help: <mailto:stackevo-discuss-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/stackevo-discuss>, <mailto:stackevo-discuss-request@iab.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jan 2016 14:16:40 -0000

I have two comments regarding the "Use Cases" section:

The first use case aims at avoiding NAT keepalive by introducing a notion of session (with commands like start, ack, stop). I understand the need to have it per "flow" (i.e. based on 5-tuple), but not the need to have it per "group of packets with a flow". Is it possible to elaborate on that?

The second use case is very generic ("SPUD-aware nodes ... signal some property of the path"). Could there be a concrete example?

Cheers,
Xavier



_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.