IETF Logo Mail Archive

Re: Packet number encryption

Roberto Peon <fenix@fb.com> Wed, 31 January 2018 23:26 UTC

Return-Path: <prvs=5569f91bb8=fenix@fb.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 62A9E12D777 for <quic@ietfa.amsl.com>; Wed, 31 Jan 2018 15:26:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=KivhHl+l; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=hmAHY65b
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 9AaQGZf8vtaK for <quic@ietfa.amsl.com>; Wed, 31 Jan 2018 15:26:09 -0800 (PST)
Received: from mx0a-00082601.pphosted.com (mx0b-00082601.pphosted.com [67.231.153.30]) (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 4FEE3124234 for <quic@ietf.org>; Wed, 31 Jan 2018 15:26:09 -0800 (PST)
Received: from pps.filterd (m0001255.ppops.net [127.0.0.1]) by mx0b-00082601.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w0VNMHPp017500; Wed, 31 Jan 2018 15:26:01 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=facebook; bh=2spqMCw+8CykhxKFQNNg7SEEiAsbTWcawaU1IdWYFeo=; b=KivhHl+l5KoQ5tvWxWf10hUtsl2LU94XPWxi0jDrFKTEbUGgkX0wKP/4Mbt4DivxwXMS pG82QUgjazKml8hx1rkWghlZlAJl65vwHt1XvZ+6kt1eaBLDmMqmtlPEJhn9AJKHWPx5 U9eM1Z0zSY0UZRqKodIwwa0cTQ9/X5AQrPc=
Received: from mail.thefacebook.com ([199.201.64.23]) by mx0b-00082601.pphosted.com with ESMTP id 2fuk5uhgkq-3 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 31 Jan 2018 15:26:01 -0800
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (192.168.54.28) by o365-in.thefacebook.com (192.168.16.16) with Microsoft SMTP Server (TLS) id 14.3.361.1; Wed, 31 Jan 2018 15:25:54 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=2spqMCw+8CykhxKFQNNg7SEEiAsbTWcawaU1IdWYFeo=; b=hmAHY65bpuQzRU7omRRg2ijxoVCMTjsFhADfDmWzY0YNUrxFCWI+5jwGM7mxxrGgwn7RTaymXzOj8zhUnbeOfMHezYJW6Qza1ikz0F9vb84eUpJtAy4XJDLIM2LpqIP1UeD3GCX58+F2/FDCB2Q4KUAvmWniyb5FuF3J13T8PPU=
Received: from BY2PR15MB0775.namprd15.prod.outlook.com (10.164.171.11) by BY2PR15MB0278.namprd15.prod.outlook.com (10.163.64.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.444.14; Wed, 31 Jan 2018 23:25:51 +0000
Received: from BY2PR15MB0775.namprd15.prod.outlook.com ([10.164.171.11]) by BY2PR15MB0775.namprd15.prod.outlook.com ([10.164.171.11]) with mapi id 15.20.0444.016; Wed, 31 Jan 2018 23:25:51 +0000
From: Roberto Peon <fenix@fb.com>
To: Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>, Martin Thomson <martin.thomson@gmail.com>
CC: Brian Trammell <ietf@trammell.ch>, Eric Rescorla <ekr@rtfm.com>, QUIC WG <quic@ietf.org>, Christian Huitema <huitema@huitema.net>
Subject: Re: Packet number encryption
Thread-Topic: Packet number encryption
Thread-Index: AQHTmW3+HjM5RmHWDkij9J5s6UBSSaOMgUQAgABeoYCAAAgUAIAAd3KAgAA8YgCAAIDjAA==
Date: Wed, 31 Jan 2018 23:25:51 +0000
Message-ID: <827BA6F8-5CA8-420A-B18B-60D8BC134A46@fb.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>
In-Reply-To: <BF80500A-6277-45DC-8525-9C3FE138B76D@tik.ee.ethz.ch>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2620:10d:c090:200::4:1bde]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BY2PR15MB0278; 20:UjFohEE71S+Fp0ioUtuyv/syyrL7biy7c9kaAN3vpHuQJUjdvOKSGaLcwf5KUbgUTU/8bGyp2tsWCUOSsNGvlcuqBvQYHpeTi58WCZsvfCWCeJ8SjOJ2dzdPhqy+VF04iesic3sz9IwPUmtExt1WTDSclAQCBy1x9M39Qtb7A/o=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 9068f64c-635e-46f5-4d2a-08d56901f7ce
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:BY2PR15MB0278;
x-ms-traffictypediagnostic: BY2PR15MB0278:
x-microsoft-antispam-prvs: <BY2PR15MB02782A513839F3D4972EB34FCDFB0@BY2PR15MB0278.namprd15.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(85827821059158);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(8121501046)(5005006)(3231101)(11241501184)(2400082)(944501161)(3002001)(93006095)(93001095)(10201501046)(6041288)(20161123564045)(20161123562045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(6072148)(201708071742011); SRVR:BY2PR15MB0278; BCL:0; PCL:0; RULEID:; SRVR:BY2PR15MB0278;
x-forefront-prvs: 056929CBB8
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(39380400002)(396003)(366004)(376002)(346002)(51444003)(189003)(199004)(36756003)(316002)(6436002)(6486002)(33656002)(229853002)(2906002)(4326008)(53936002)(3480700004)(6246003)(6512007)(59450400001)(86362001)(7736002)(105586002)(14454004)(53546011)(8676002)(478600001)(5660300001)(106356001)(7116003)(102836004)(39060400002)(186003)(6116002)(76176011)(25786009)(3660700001)(97736004)(8936002)(83716003)(54906003)(82746002)(81166006)(2900100001)(2950100002)(3280700002)(68736007)(110136005)(99286004)(81156014)(305945005)(93886005)(6506007)(77096007)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR15MB0278; H:BY2PR15MB0775.namprd15.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: fb.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: ZDZC03BVSX1JOe1peiAV/mAy9Vy/tTIhDMvPfAl8dLtPImsmjYMxx9TwyqOoduSwzPN9VFw3f+tahE4ndN6I9w==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <A89781925366E947993723E37D69B74A@namprd15.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 9068f64c-635e-46f5-4d2a-08d56901f7ce
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Jan 2018 23:25:51.4294 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR15MB0278
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-31_11:, , signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/9rQ2tykd5W2SDYuGWjDZ7_XPhpU>
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: Wed, 31 Jan 2018 23:26:11 -0000

There are two obvious goals/benefits:
1) Slow/prevent ossification.
2) Raise the barrier higher for tracking/flow correlating.

If we have multiple CIDs (which are valid on more than one 5-tuple) and “multipath” (one could imagine switching between a bunch of IPv6 addresses which go to the same hosts) we can require a higher storage baseline before traffic can be correlated. This is where I believe #2 really comes into play. 

#1 is nothing to sneeze at: experience with TCP has shown very real harm from having things which allow sequencing of packets in the clear (unable to roll out changes which should have been compatible). To me, this is the primary use-case: maintaining future flexibility.

-=R

On 1/30/18, 11:45 PM, "QUIC on behalf of Mirja Kühlewind" <quic-bounces@ietf.org on behalf of mirja.kuehlewind@tik.ee.ethz.ch> wrote:

    
    
    > Am 31.01.2018 um 04:08 schrieb Martin Thomson <martin.thomson@gmail.com>:
    > 
    > On Wed, Jan 31, 2018 at 8:00 AM, Christian Huitema <huitema@huitema.net> wrote:
    >>> (1) An unprivileged on-path device that sees a packet from a flow that is
    >>> migrated on purpose by an endpoint (i.e., due to connection migration or
    >>> multipath) should not be able to associate that packet to the prior flow.
    >> 
    >> Yes.
    > 
    > Agreed.  This remains the primary target.  I don't think that there
    > are any negatives with this design with respect to this use case (or
    > at least I found nothing in Brian's email on this point).
    
    If that is the goal, I think the complexity of the proposed solution is not justified. Just select a new random offset when you migrate but increase the packet number monotonously otherwise to support manageability.
    
    I’m really concerned about complexity here. Even though this scheme is not very complex, any complexity is a potential source for future implementation errors which can also led to restrictions in what changes can be deploy with future versions. Making a protocol as simple as possible and thereby the spec as easy understandable as possible is also key for deployment. If we add complexity here without making it clear what the goal or additional benefit is of the complexity, I think that is just wrong.
    
    My 2c.
    Mirja

v2.23.0 | Report a Bug | By Email