IETF Logo Mail Archive

RE: Packet number encryption

"Roni Even (A)" <roni.even@huawei.com> Mon, 05 February 2018 06:24 UTC

Return-Path: <roni.even@huawei.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B453126D74 for <quic@ietfa.amsl.com>; Sun, 4 Feb 2018 22:24:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 vvKvyIPTUO9k for <quic@ietfa.amsl.com>; Sun, 4 Feb 2018 22:24:12 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66AC5120727 for <quic@ietf.org>; Sun, 4 Feb 2018 22:24:12 -0800 (PST)
Received: from LHREML710-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 1A3387796FF31 for <quic@ietf.org>; Mon, 5 Feb 2018 06:24:09 +0000 (GMT)
Received: from DGGEMM423-HUB.china.huawei.com (10.1.198.40) by LHREML710-CAH.china.huawei.com (10.201.108.33) with Microsoft SMTP Server (TLS) id 14.3.361.1; Mon, 5 Feb 2018 06:24:09 +0000
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.214]) by dggemm423-hub.china.huawei.com ([10.1.198.40]) with mapi id 14.03.0361.001; Mon, 5 Feb 2018 14:24:04 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: Christian Huitema <huitema@huitema.net>, "quic@ietf.org" <quic@ietf.org>
Subject: RE: Packet number encryption
Thread-Topic: Packet number encryption
Thread-Index: AQHTmW31OHIMr4j8BEGT08HQjsZCKqOMgUQAgABeoYCAAAgUAIAAd3KAgAA8YgCAACPEAIAAAiYAgAOBlQCAADHCgIAACBkAgAEGFwCAAWG+cIABeXFFgAACQ6A=
Date: Mon, 05 Feb 2018 06:24:03 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD861DD5@DGGEMM506-MBX.china.huawei.com>
References: <CABkgnnVyo3MmWtVULiV=FJTnR528qfY8-OmKGWAs0bCvri-a_g@mail.gmail.com> <1F7FB3B8-A94C-4354-9944-FB09FB8DB68B@trammell.ch> <CABcZeBMbwdwyC9TxxHBLYaZKfNB-FG2wCGjqUZ_mNR-A1R47FA@mail.gmail.com> <9096e5ec-581e-875a-b1dd-bff0b05206fd@huitema.net> <CABkgnnWRQSAufwPss+qf=xAzCwRYeNNH8XLPm3yFaHxOb+ba4g@mail.gmail.com> <BF80500A-6277-45DC-8525-9C3FE138B76D@tik.ee.ethz.ch> <5A7191E0.6010003@erg.abdn.ac.uk> <5214AD93-8376-4B25-922F-AF5551CC2E95@netapp.com> <F990E064-E6F8-41A3-B791-F776C9955E15@nokia.com> <CAGD1bZab0GaZFsHwC+nw3AxxC4VusxMJ6oDanzk3dSDdWKAXdw@mail.gmail.com> <2C515BE8694C6F4B9B6A578BCAC32E2F83BA1443@MBX021-W3-CA-2.exch021.domain.local> <BY2PR15MB07757473DB9788558B902EB5CDF80@BY2PR15MB0775.namprd15.prod.outlook.com> <6E58094ECC8D8344914996DAD28F1CCD861B7F@DGGEMM506-MBX.china.huawei.com> <BY2PR15MB07758F932FBB87047ACB9D9ACDFE0@BY2PR15MB0775.namprd15.prod.outlook.com> <00f301d39e3d$f15bdf40$d4139dc0$@gmail.com> <613d29a0-5928-a41a-c4df-628c01bd6ef6@huitema.net>
In-Reply-To: <613d29a0-5928-a41a-c4df-628c01bd6ef6@huitema.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.202.244]
Content-Type: multipart/alternative; boundary="_000_6E58094ECC8D8344914996DAD28F1CCD861DD5DGGEMM506MBXchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/c8nY-iyRj44MNBtZ5bD-7an_bY4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Feb 2018 06:24:14 -0000

BTW:
This will only provide information about reorder in this network segment and not end to end which is what the requirement is for.
Roni

From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of Christian Huitema
Sent: Monday, February 05, 2018 8:14 AM
To: quic@ietf.org
Subject: Re: Packet number encryption


On 2/4/2018 6:58 PM, Roni Even wrote:
Does not it mean that the network need to identify packets  that are from the same quic connection to make such wrapping?

Not really. The network can take any slice of the input packets, assigned them a sequence number, and verify that the slice comes out the same way it went in. Or count losses, reordering, etc. Slicing by five tuple should work just fine.

-- Christian Huitema

v2.23.0 | Report a Bug | By Email